METHOD AND DEVICE FOR LONG TERM EVOLUTION OPERATION IN THE UNLICENSED AND SHARED SPECTRUM FOR CLOUD RADIO ACCESS NETWORKS
The C-RAN system optimizes LTE operations in unlicensed spectrum by using a timer-based retransmission strategy and dynamic frequency selection to address latency and spectrum access uncertainties, enhancing efficiency and flexibility in cloud radio access networks.
Patent Information
- Application Number
- DE102019103265
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-05-07
- Filing Date
- 2019-02-11
- Publication Date
- 2024-11-07
- Estimated Expiration
- 2039-02-11
AI Technical Summary
Existing cloud radio access networks (C-RAN) face challenges in efficiently operating LTE technologies in unlicensed and shared spectrum due to communication latency between layers and uncertainty in spectrum access, particularly with non-ideal fronthaul latency, which affects the implementation of Licensed Assisted Access (LAA) and other unlicensed LTE technologies.
The system and method involve configuring a baseband unit (BBU) to support non-guaranteed bit rate traffic on unlicensed cells and guaranteed bit rates on licensed cells, implementing a timer-based retransmission strategy for failed packets, and using dynamic frequency selection and Listen Before Talk (LBT) processes to optimize data transmission in unlicensed bands, with a control unit (CU) managing the fronthaul interface to minimize latency and maximize transport efficiency.
This approach enhances the flexibility and efficiency of LTE operations in unlicensed spectrum by reducing latency and improving spectrum utilization, allowing for real-time system performance optimization and cost-effective upgrades in C-RANs, while ensuring fair coexistence with other wireless technologies.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present application claims priority to U.S. Provisional Patent Application No. 62 / 628,538, entitled METHOD AND APPARATUS FOR LTE OPERATION IN UNLICENSED AND SHARED SPECTRUM FOR CLOUD RADIO ACCESS NETWORKS, filed February 9, 2018, which is incorporated herein by reference in its entirety.
[0002] The present invention also claims priority to U.S. Provisional Patent Application No. 62 / 659,546, entitled METHOD AND APPARATUS FOR LTE OPERATION IN UNLICENSED AND SHARED SPECTRUM FOR CLOUD RADIO ACCESS NETWORKS, filed April 18, 2018, which is incorporated herein by reference in its entirety.
[0003] The present invention also claims priority to U.S. Provisional Patent Application No. 62 / 668,012, entitled METHOD AND APPARATUS FOR LICENSED-ASSISTED ACCESS (LAA) FOR CLOUD RAN AND FOR MULTI-LAA CELLS, filed May 7, 2018, which is incorporated herein by reference in its entirety. BACKGROUND OF REVELATION 1. Area of Revelation
[0004] The present disclosure relates to systems and methods for radio access networks. 2. Description of the related art
[0005] Traditionally, radio access networks (RANs) were built using an integrated unit that processed the entire RAN. The RAN network typically uses application-specific hardware for processing, making them difficult to upgrade and evolve. As future networks evolve toward massive network densification to accommodate increased capacity demands, there is a growing need to reduce the capital and operational costs of RAN deployment and make the solution scalable and easy to upgrade.
[0006] Cloud-based radio access networks (C-RAN) are networks where a significant part of the RAN layer processing is performed in a central unit (CU), also known as the baseband unit (BBU), located in the cloud on commercial off-the-shelf servers, while the critical RF and real-time functions can be processed in the remote radio unit (RRU) or the distributed unit (DU).
[0007] Traditional RANs implement the protocol stack (e.g., physical layer (PHY), medium access control (MAC), radio link control (RLC), and packet data convergence control (PDCP) layers) at the base station (also referred to as the eNodeB or eNB). In Cloud RAN, various radio functions are distributed between the RRU and the baseband unit (BBU). RRUs are implemented locally on-premises, while the BBU is virtualized in the cloud, which could be hundreds of kilometers away from the RRU. A single BBU (or vRAN) can control multiple RRUs at different locations.
[0008] Cloud RAN provides centralization and virtualization of RAN networks, resulting in benefits such as (a) operational cost reduction due to consolidating resources and operating the network on general-purpose hardware, thereby achieving economies of scale, (b) performance improvements due to better fault management, (c) remote network upgradability and management, and (d) easier migration for adding new features and easier transition from 4G to 5G networks.
[0009] In conventional Long-Term Evolution (LTE) operation in licensed bands, mobile network operators have the exclusive right to use the spectrum. They thus have complete control over termination, resource allocation, and spectrum access. With the development of new radio technologies and the exponential increase in demand for wireless communications over the past decade, there has been interest in recent years in extending LTE technologies to operate in unlicensed and shared spectrum. This has occurred particularly after the FCC opened new bands for unlicensed / shared operation in the 5 GHz UNII and other bands. Publication WO 2017 / 206 102 A1 describes a method and apparatus for implementing LBT in a distributed RRU-BBU architecture.US 2017 / 0 318 594 A1 discloses a wireless device that receives configuration parameters indicating a logical channel allocation restriction. Additionally, WO 2017 / 135 077 A1 discloses a terminal device for performing an uplink transmission based on an uplink authorization. SUMMARY OF REVELATION
[0010] The present disclosure provides embodiments of a system, method, and apparatus for LTE operation in the unlicensed bands, wherein a BBU is configured to terminate non-guaranteed bit rate (non-GBR) traffic on unlicensed cells and guaranteed bit rate (GBR) traffic on licensed cells. The BBU is also configured to terminate priority classes 3 and 4 on unlicensed cells, while terminating priority classes 1 and 2 on licensed cells.
[0011] The present disclosure also provides embodiments of a system and method for LTE operation in the unlicensed bands in the Cloud RAN framework, wherein a BBU at the Radio Link Control (RLC) layer is configured to retransmit failed packets originally transmitted on the unlicensed band on a licensed band.
[0012] The present disclosure further provides embodiments of a system and method, wherein a BBU is configured to set a timer based on an end-to-end latency requirement of the traffic and attempt transmission on an unlicensed band. After the timer expires, the BBU may be configured to retransmit the failed packets on licensed bands. The timer threshold may be set based on the expected duration for a packet to be received at the UE, including the expected fronthaul latency, the expected Listen Before Talk (LBT) latency, and other parameters.
[0013] The present disclosure still further provides a system and method for LTE operation in the unlicensed bands in which a dynamic frequency selection (DFS) process is triggered by an LBT failure.
[0014] In one embodiment, the present disclosure provides a method and system and apparatus therefor, comprising: Transmitting, from a lower layer of a baseband unit (BBU) to a layer of a remote radio unit (RRU) over a fronthaul interface, a data transmission at a destination subframe agreed between the BBU and the RRU, wherein the data is sent a number of milliseconds before the RRU performs a Listen Before Talk (LBT) step for the data, wherein a control unit (CU) of the BBU is configured to set a timer based on an end-to-end latency requirement of the data traffic and is configured to attempt the transmission on an unlicensed band.
[0015] In the embodiment, the CU may be further configured to: Transferred, from the CU, an amount corresponding to the RRU buffer depth (B RU) of the data at a CU transmission time threshold at which the CU must transmit the data to the RRU so that it is transmitted over the air (OTA) at Tstart (CUT th ); Transmit, for the destination subframe, an LBT-PDSCH (Physical Downlink Shared Channel) request to the RRU; Determine whether an LBT-PDSCH response is received from the RRU at the CU; Determine whether the LBT-PDSCH response is successful and, If the LBT-PDSCH response is successful, incrementing a CU transmission start time (T start ) to set a buffer depth of the RRU (T start = T start + B RU ) or Reset the LBT step if the received LBT-PDSCH response is unsuccessful.
[0016] In the embodiment, the CU may be further configured to: Incrementing the CU transmission start time (T start) to increase the buffer depth of the RRU (T start = T start + B RU ) if the LBT-PDSCH response from the RRU is determined to be successful; Determine whether the remaining data is less than the RRU buffer depth (B RU ) and, if this is the case, transfer the remaining data to the RRU at the CU transmission time threshold CUT th , or if not, transfer only the B RU -data volume to the RRU. If the CU detects that the LBT-PDSCH response from the RRU is not received at the CU, the CU is further configured to: Determine whether a current time is a latest time at which the CU is expected to receive the LBT-PDSCH response from the RRU (T NOW = LBT TH ); if yes, update the time at which the data should be transferred OTA (OTA T start = T start + [B RU]), and continue to determine whether the LBT-PDSCH response from the RRU is not received at the CU. If the CU determines that the current time is not the latest time at which the CU is expected to receive the LBT-PDSCH response from the RRU (T NOW = LBT TH ), the CU may further be configured to: Determine whether the current time is equal to the CU transmission time threshold CUT th and: if so, transferring data worth B RU ; or if not, re-determine whether the LBT-PDSCH response has been received.
[0017] In the embodiment, the RRU can be configured for the following: Determine whether an LBT-PDSCH (Physical Downlink Shared Channel) request is transmitted by the CU; Starting an LBT spectrum sensing when the LBT PDSCH request is received from the CU; Determine whether an LBT timer for the LBT spectrum acquisition has expired; and if the LBT timer has expired, send a failure message to the CU and terminate the LBT process, or if the LBT timer has not expired, determine that a current time has a start time (T start ) and whether no channel has been acquired; and if no channel has been acquired, increment the Tstart by x(T start = T start + x) and proceed with the LBT spectrum acquisition. The RRU may be further configured to: Determine whether a channel has been acquired at time Tacq; and if no channel has been acquired, discard all expired symbols from a buffer of the RRU and buffer any newly received data and proceed with the LBT spectrum acquisition. The RRU may be further configured to: if the channel has been acquired, send an LBT-PDSCH success message to the CU; Sending a reservation signal OTA to the T start ; Sending the buffered data OTA and updating T start as (T start = T start + B RU ); Determine whether the buffered data is less than the buffer depth of RRU B RU and, if yes, continue sending the buffered data OTA, and if the remaining buffered data is not less than the buffer depth of RRU B RU , sending the remaining buffered data OTA and performing a data reception check.
[0018] In one embodiment, the present disclosure provides a system comprising: a baseband unit (BBU) configured to calculate average utilization levels of all valid channel combinations and to select a channel with the minimum utilization level when the difference between the two lowest average utilization levels is greater than a threshold.
[0019] In one embodiment, the present disclosure provides a method for an eNB and a system and apparatus therefor, comprising: Selecting a cell to be added to a user equipment (UE) using a weighted sum of factors, wherein selecting comprises checking a plurality of cell loads of both licensed and unlicensed cells according to a criterion; Testing a plurality of channel gains of both licensed and unlicensed cells according to the criterion; if all licensed channels are busy, use unlicensed channels for new UEs, and Switching between licensed and unlicensed channels based on UE capabilities. The criterion can be selected from criteria including the following: Determining whether a load of a licensed cell is less than a previously defined threshold, wherein the Enb adds the licensed cell to the UE if the load of the licensed cell is less than the previously defined threshold; and Determining whether the difference between the load of the licensed cell and the load of an unlicensed cell is less than a previously defined threshold, wherein the Enb adds the licensed cell to the UE if the difference between the load of the licensed cell and the load of the unlicensed cell is less than the previously defined threshold.
[0020] In one embodiment, the present disclosure provides a system comprising: a remote radio unit (RRU) configured to operate on an optimal channel to be used from an unlicensed band, wherein the RRU is configured to perform periodic measurements of channels and report these measurements to a control unit (CU) of a baseband unit (BBU); and wherein the CU is configured to use the measurements to select the optimal channel to be used and reconfigure the RRU to use the selected optimal channel. The CU may be configured to issue instructions for dynamic frequency selection in accordance with Ro(fc*)≥Roth or P¯(fc*)≥Pth used to select an optimal channel based on the RRU measurements.
[0021] In one embodiment, the present disclosure provides a system comprising: a baseband unit (BBU) comprising a control unit (CU) configured to send a pilot message to a remote radio unit (RRU) prior to a data link time to compensate for fronthaul latency; and wherein the RRU is configured to respond to the BBU with messages indicating a time at which the RRU can receive the pilot message; and wherein the CU is configured to adjust a transmission rate to the RRU based on the buffer size at the RRU and the fronthaul latency.
[0022] In one embodiment, the present disclosure provides a method and system and apparatus therefor, comprising: Transmitting, from a lower layer of a baseband unit (BBU) to a layer of a remote radio unit (RRU) via a fronthaul interface, a Discovery Reference Signal (DRS) transmission; wherein a control unit (CU) of the BBU is configured to: Sending the DRS signal at a time DRS th,1 or at a time DRS th,2 ; Sending an LBT-DRS request on a target subframe for a Listen Before Talk (LBT) acquisition and Determine whether a Discovery Measurement Timing Configuration (DMTC) offset time has elapsed; and if so, send the DRS transmission.
[0023] In the embodiment, the CU may be further configured to: If the CU determines whether the Discovery Measurement Timing Configuration (DMTC) offset time has not elapsed, determine whether a current time DRS th,1 or DRS th,2 is (Tnow = DRS th,1 or T now = DRS th,2 ?); and if so, send the DRS. The CU can also be configured to: if the CU determines that the current time is not the DRS time th,1 or the time DRS th,2 is (T now = DRS th,1 or T now = DRS th,2 ?), Determine whether the RRU has received an LBT DRS request; and if not, determine whether the DMTC offset time has elapsed and continue the DRS transmission; If the CU determines that the RRU has received the LBT DRS request, determine whether the result is successful and, if so, terminate the DRS transmission; If the CU determines that the LBD DRS request was unsuccessful, determine whether the DMTC offset time has expired and continue with the DRS transmission process.
[0024] In the embodiment, the RRU may be configured to: Determine whether the DRS has been received and, if so, buffer the DRS; if the DRS has not been received, continue listening for the DRS; if the DRS is buffered, determine whether the RRU has received an LBT DRS request from the CU and, If yes, determine whether the discovery measurement time window (DMTC) offset time has elapsed, and if so, terminate the process. The RRU can be configured to: If the DMTC offset time has not elapsed, determine whether a new DRS has been received; if not, start an LBT spectrum acquisition at a configured time; If a new DRS has been received, clear the existing buffered DRS and buffer a new DRS, and start the LBT spectrum acquisition at the configured time. The RRU can be further configured to: determine whether the LBT spectrum acquisition is successful; if not, send an LBT DRS failure message to the CU; determine whether the DMTC offset time has elapsed; if so, send an LBT DRS success message to the CU; and send the DRS over an air interface to the target device. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Non-limiting and non-exhaustive embodiments are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise indicated. For a better understanding, reference is made to the following detailed description, which should be read in conjunction with the accompanying drawings. Fig. Figure 1 is an example of a C-RAN system architecture and a functional fronthaul split. Fig. Figure 2 shows 8 options for splitting between a BBU and an RRU. Fig. 3 are different embodiments of an intra-PHY split option. The Fig. 4-10 are embodiments of data transmission supported by licensed-assisted access (LAA). Fig.11 is an embodiment of message transmission between a lower layer split CU and an RRU. Fig. 12 is an embodiment of message transmission between a lower layer split CU and an RRU. Fig. 13 is a flowchart for one embodiment of a Physical Downlink Shared Channel (PDSCH) transmission algorithm for a CU. The Fig. 14A-14B are flow diagrams for one embodiment of a PDSCH transmission algorithm for an RRU. The Fig. Figures 15-18 show examples of fronthaul normal subframe (SF) support. Fig. Figure 19 shows examples of PDSCH transmission support. Fig. 20 is a flowchart for one embodiment of a Discovery Reference Signal (DRS) transmission algorithm for a CU. Fig.21 is a flowchart for one embodiment of a DRS transmission algorithm for an RRU. Fig. Figure 22 shows an example of a DRS transmission for LBT. Fig. 23 is a flowchart for one embodiment of a DRS transmission algorithm for an RU. Fig. 24 is an example of a DRS transmission for LBT. Fig. 25 is an embodiment for assigning LAA and non-LAA capable user equipment (UE) to licensed and unlicensed component carriers (CCs). Fig. 26 is an embodiment of a configuration and method for adjusting the fronthaul rate. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0026] Reference is made to the 3GPP (Third Generation Partnership Project) system according to embodiments of the present disclosure. This application uses abbreviations, terms, and technologies defined in accordance with the 3GPP (Third Generation Partnership Project) technology standards, including the following standards and definitions. The 3GPP technical specifications (TS) and technical reports (TR), which are incorporated herein by reference, define the following related terms and architectural reference models. Abbreviations
[0027] 3GPP: Third Generation Partnership Project ARQ: Automatic Repeat Request BBU: Baseband Unit BPSK: Binary Phase Shift Keying CA: Carrier Aggregation CBRS: Citizens Broadband Radio Services CC: Component Carrier CCA: Clear Channel Assessment CCE: Control Channel Element(s) CMS: Centralized Management System CoMP: coordinated transmission at multiple base stations (Coordinated multipoint transmission) COTS: mass-produced (commercial off-the-shelf) CP: Cyclic prefix CQI: Channel Quality Indicator C-RAN: Cloud Radio Access Network CRC: Cyclic Redundancy Checking CRS: Cell-Specific Reference Signal CSAT: Carrier-sense adaptive transmission CSI: Channel State Information CSI-RS: Channel state information - reference signal CU / lls-CU: Central Unit. In this document, CU and lls-CU are used interchangeably and refer to the central unit or processing unit in the cloud that communicates with a RU / RRU (Radio Unit / Remote Radio Unit). DCI: Downlink Control Indicator DFS: Dynamic Frequency Selection DM-RS: Demodulation - reference signal DRS: Discovery Reference Signals DMTC: Discovery Measurement Timing Configuration DL: Downlink DU: Distribution Unit EPC: LTE core structure (Evolved Packet Core) E-UTRA: LTE air interface (Evolved Universal Terrestrial Radio Access) eNB: Evolved Node B FDD: Frequency Division Duplex FEC: Forward Error Correction FFT: Fast Fourier Transform iFFT: Inverse Fast Fourier Transform ISM radio bands (Industrial, Scientific and Medical Radio Bands) HARQ: Hybrid Automatic Repeat Request HARQI: Hybrid Automatic Repeat Request Information IoT: Internet of Things JP: joint processing JR: Joint Reception KPI: Key Performance Indicator LAA: Licensed-Assisted Access LBT: Listen Before Talk lls: lower-layer split LCM: Life Cycle Management LTE: Long Term Evolution LTE-A: LTE Advanced MAC: Media Access Control MBSFN: Multicast Broadcast Single-Frequency Network MCOT: Maximum Channel Occupancy Time MCS: Modulation and Coding Scheme MIB: Master Information Block MIMO: Use of multiple transmit and receive points (multiple input, multiple output) MMSE-IRC: Minimum Mean Square Error - Interference Rejection Combining MMSE-MRC: Minimum Mean Square Error - Maximum-Ratio Combining mmWave: millimeter wave MNO: Mobile Network Operator NR: New Radio OAM: Operation and Management OSS: Operator Service System OTA: over the air interface (Over The Air) PBCH: Physical broadcast channel PCFICH: Physical Control Format Indicator Channel PDCCH: Physical Downlink Control Channel PDCP: Packet Data Convergence Protocol PDSCH: Physical Downlink Shared Channel PHICH: Physical Hybrid ARQ Indicator Channel PHY: Bitübertragungsschicht (Physical Layer) LPHY: untere Bitübertragungsschicht (Lower Physical Layer) UPHY: obere Bitübertragungsschicht (Upper Physical Layer) PNF: Physical Network Function P-SS: Primary Synchronization Signal PUCCH: Physical Uplink Control Channel PUSCH: Physical Uplink Shared Channel QAM: Quadratur-Amplituden-Modulation QPSK: Vierphasen-Modulation (Quadrature Phase Shift Keying) RACH: Random Access Channel PRACH: Physical Random Access Channel REST API: Representational State Transfer Application Programming Interface RF: Radio Frequency Interface RI: Rank Indicator RLC: Radio Link Control RRC: Radio Resource Control RRM: Radio Resource Management RU / RRU: Radio Unit / Remote Radio Unit. In this document, RU and RRU are used synonymously. RS: Reference Signal RSSI: Received Signal Strength Indicator SCell: Secondary Cell SF: Subframe SFN: System Frame Number SIMO: Single Input, Multiple Output SINR: Signal-to-Interference-Plus-Noise Ratio SON: self-organizing network SRS: Sounding Reference Signal S-SS: Secondary Synchronization Signal TB: Transport Block (Transport Block) TTI: Transmission Time Interval TDD: Time Division Duplex TPC: Transmission Power Control UCI: Uplink Control Information UE: User Equipment UL: Uplink UL DMRS: Uplink Demodulation Reference Signal ULSCH: Uplink Shared Channel UNII radio band: Unlicensed National Information Infrastructure radio band (UNII Radio Band) vBBU: Virtualized Baseband Unit VNF: Virtual Network Function
[0028] The present disclosure provides embodiments of systems, apparatus, and methods for LTE operation in unlicensed and shared spectrum for Cloud RANs, such as Licensed Assisted Access (LAA), MulteFire, Citizens Broadband Radio Services (CBRS), and the like.
[0029] The present disclosure relates to wireless data transmission over the air (OTA) using PDSCH transmission. However, it should be understood that the same procedures / methods apply to other channels / signals (e.g., reference signals, control channels, and the like) multiplexed using PDSCH.
[0030] Fig.Figure 1 is an example of a C-RAN system architecture 100 and a functional fronthaul split 101 for the Cloud RAN 100, comprising a central unit (CU) 102 containing a BBU 103 or BBU pools 103 and one or more distributed units (DU) 104, including an RRU / RU. The BBU pools 103 may be interconnected with other BBU pools and connected to the EPC (Evolved Packet Core) network 106 via an S1 interface. The RRUs 105 connect a user equipment (UE) 107 to the network.
[0031] To enable the RRU 105 to operate and access unlicensed / shared spectrum, various embodiments of modules are integrated into the Cloud RAN and configured for functions such as carrier selection, listen-before-talk (LBT), dynamic frequency selection (DFS), reference signal transmission (e.g., discovery reference signal or DRS), and the like.
[0032] Embodiments as described herein address the challenges of enabling LTE technologies in unlicensed bands due to the fact that the separation between different LTE layers can lead to communication latency between layers going into the BBU 103 and those going into the RRU 105. The uncertainty regarding spectrum access due to the execution of spectrum sensing, especially in combination with the fronthaul latency in the BBU 103-RRU 105 connection, poses another problem for C-RAN. One of the primary limitations with LAA is that an RRU 105 is configured to acquire spectrum immediately after LBT success (i.e., within a 9 µs sensing window) to prevent other Wi-Fi / eNBs from using the channel.Embodiments as described here address the fronthaul latency (from a few hundred microseconds to a few milliseconds) for implementing LAA in C-RANs.
[0033] The present disclosure provides embodiments of systems, methods, and devices for enabling LTE operation in unlicensed / shared spectrum through a lower layer split (Intra-PHY, MAC-PHY, and the like) between the CU 102 and the DUs 104. These embodiments maximize transport efficiency and enable the flexibility to support many of the features required for virtualization and commercialization of C-RAN technology. While the present disclosure describes embodiments for using unlicensed spectrum for LTE operation for C-RAN, various embodiments are also applicable to licensed LTE operation for C-RAN. Various embodiments are also applicable to unlicensed LTE operation for conventional RANs as well as C-RANs.
[0034] In traditional LTE networks, the LTE functionalities and the LTE protocol stack layers are located in the eNB small cell deployed on-premises. There are several advantages of the C-RAN solution (i.e., splitting the BBU 103 and the RRU) compared to traditional LTE networks.
[0035] C-RAN provides Mobile Network Operators (MNOs) with the flexibility to optimize system performance in real time by varying various configuration and system parameters using the cloud-based infrastructure.
[0036] With the emergence of new wireless technologies and standards, MNOs must upgrade their eNB small cells, which is typically associated with high costs. With C-RAN, most LTE functions in the BBU 103 can be software-based, which can be easily upgraded as new wireless technologies emerge. This significantly reduces upgrade costs.
[0037] Having a software-based BBU 103 in the cloud has other advantages, such as the flexibility to add new services and the significant reduction in operational and administrative costs (OAM).
[0038] To enable the C-RAN solution, the LTE functionalities must be split between the BBU 103 in the cloud and the RRU 105 on-premises.
[0039] 3GPP has defined in TR 38.801 V14.0.0 (2017-03) 8 options for the distribution between the BBU 103 and the RRU 105 as described in Fig. 2, where each set of arrows indicates the division between the layers in the CU 102 on the right and the DU 104 on the left: Option 1 -RRC is in CU 102. PDCP, RLC, MAC, physical layer and RF are in DU 104. Option 2 RRC and PDCP are located in the central unit. RLC, MAC, physical layer, and RF are located in DU 104. Option 3 (Intra-RLC Split) Low RLC (a subfunction of RLC), MAC, physical layer, and RF are located in the distributed unit. PDCP and high RLC (the other subfunction of RLC) are located in the CU 102. Option 4 (RLC-MAC split) MAC, physical layer, and RF are located in the distributed unit. PDCP and RLC are located in CU 102. Option 5 (Intra-MAC Split) -RF, physical layer and part of the MAC layer (e.g. HARQ) are in the DU 104. The upper layer is in the CU 102. Option 6 (MAC-PHY split) -Physical layer and RF are in the DU 104. The upper layers are in the CU 102. Option 7 (Intra-PHY Split) Part of the physical layer and RF functions are in the DU 104. The upper layers are in the CU 102. Option 8 (PHY-RF split) -The RF functionality is in the DU 104 and the upper layer is in the CU 102.
[0040] There are several factors that influence the selection of the fronthaul split option.
[0041] Bandwidth: Different split options have different bandwidth requirements, which ultimately plays a role in determining the fronthaul design. For example, Option 8 (PHY-RF split) places very high demands on fronthaul bandwidth, which can result in higher resource consumption and higher transport sizing costs (link capacity, equipment, and the like). On the other hand, one of the advantages of Option 5 (Intra-MAC split) is that it reduces the bandwidth required for fronthaul.
[0042] Latency: In the LTE protocol stack, the split between the BBU 103 and the RRU 105 influences the latency. For example, a split between L3 and L2 in Option 1 has very low latency requirements. This split option is useful for handling some cases of edge computing or low-latency usage, where the user data must be close to the transmission point. Another example is the split option 3 within the RLC layer. The split in Option 3-1 is more latency-sensitive than the split with ARQ in DU 104, because retransmissions are subject to transport network latency over a split transport network. In contrast, Option 3-2 is insensitive to the transport network latency between CU 102 and DU 104. In the split option 5 (Intra-MAC), time-critical functions are located in the Low-MAC sublayer, which includes the functions with stringent delay requirements (e.g.,HARQ) or functions where performance is proportional to latency (e.g., radio channel and signal measurements from the PHY, Random Access Control). This division helps reduce delay requirements at the fronthaul interface. In contrast, Option 8 places very high demands on fronthaul latency, which can lead to limitations on network deployments in terms of network topology and available transport options.
[0043] Implementation costs: Higher splits typically have higher implementation costs compared to lower splits, as lower splits allow for more virtualization. For example, in split option 8, separating RF and PHY allows for pooling PHY resources, which can enable more cost-effective sizing of the PHY layer. Separating RF and PHY allows operators to share RF components, which can reduce system and site costs. Conversely, high fronthaul bandwidth requirements result in higher resource consumption and higher transport sizing costs (link capacity, equipment, etc.).
[0044] Other factors include virtualization benefits, fronthaul interface complexity, expansion flexibility, compute power, and storage requirements.
[0045] While the present disclosure provides the standardization of split option 7 (i.e., intra-PHY split) as an example to illustrate the detailed aspects, the present disclosure is not limited to the example of split option 7, and the present disclosure is intended to include other split options mentioned above (e.g., split options 5, 6, and 8). Option 7 (Intra-PHY Split)
[0046] Multiple implementations of this option are possible, including asymmetric configurations that independently provide benefits for different suboptions for UL and DL (e.g., Option 7-1 is used for UL and Option 7-2 is used for DL). A compression technique may be able to reduce the required transport bandwidth between the DU 104 and the CU 102.
[0047] For the UL, FFT and CP removal are located in the DU 104. The remaining functions are located in the CU 103.
[0048] On the downlink, iFFT and CP addition are located in DU 104. The rest of the PHY is located in CU 103.
[0049] Fig. Figure 3 illustrates various embodiments of the Intra-PHY Split Option 7 and the associated benefits.
[0050] Options 7-1, 7-2 and 7-3 have the following in common: Options 7-1, 7-2, and 7-3 enable centralized traffic aggregation of NR and E-UTRA transmission points. They can also facilitate traffic load management between NR and E-UTRA transmission points.
[0051] These options are expected to reduce fronthaul throughput requirements.
[0052] Centralized scheduling is possible because the MAC is located in the CU 102 (e.g., CoMP). Joint processing (both transmit and receive) is also possible with these options because the MAC is located in the CU 102. Option 7-1Description:
[0053] In the UL, the FFT, CP removal and, if applicable, PRACH filtering functions are located in the DU 104, while the remaining PHY functions are located in the CU 102.
[0054] In the DL, the iFFT and CP addition functions are located in the DU 104, the rest of the PHY functions are located in the CU 102.
[0055] Option 7-1 also allows the implementation of advanced receivers. Option 7-2Description:
[0056] In the UL, the functions FFT, CP removal, resource demapping and, if necessary, pre-filtering are located in the DU 104, while the remaining PHY functions are located in the CU 102.
[0057] In the DL, the iFFT, CP addition, resource mapping, and precoding functions are located in the DU 104, while the remaining PHY functions are located in the CU 102.
[0058] Option 7-2 enables the optimal use of advanced receivers. Option 7-3 (DL only)
[0059] Description:
[0060] Only the encoder is located in the CU 102 and the rest of the PHY functions are located in the DU 104.
[0061] This option can reduce fronthaul requirements in terms of data throughput at baseband bit rates because the payload for Option 7-3 is encoded data.
[0062] For the purposes of the present disclosure, the prior art technology does not provide technological solutions addressing, among other things, the configuration of the fronthaul interface between the UPHY and the LPHY in Sharing Option 7. The present disclosure describes embodiments that enable LTE operation in unlicensed and shared spectrum for C-RANs. LAA
[0063] Carrier aggregation (CA) with at least one SCell operating in the unlicensed spectrum is referred to as LAA. While the present disclosure describes embodiments for LAA technology, embodiments are also applicable to other unlicensed spectrum technologies, such as multifire, CBRS spectrum, and the like. Therefore, with LAA, the configured set of serving cells for a UE includes at least one SCell operating in the unlicensed spectrum according to the Type 3 frame structure, also referred to as an LAA SCell. Unless otherwise stated, LAA SCells function as regular SCells.
[0064] The 5150-5925 MHz band, or parts thereof, is / are potentially available for licensed-assisted access to unlicensed operations. This represents a significant amount of spectrum that operators can use to expand their service offerings in licensed bands. The above range can be operated under a license-free scheme or ISM, but must be shared with existing mobile services and other established services.
[0065] The quality of service provided by a licensed scheme cannot therefore be achieved. Therefore, unlicensed access is considered complementary and, given the increasing demand for wireless broadband access, does not reduce the need for additional allocations for licensed operations. Different regulatory requirements apply to different regions and bands, as described in 3GPP TR 36.889 V13.0.0 (2015-06), which is incorporated herein by reference. 3GPP provides specifications that can work for all regions. LAA configuration
[0066] Embodiments of an LAA configuration are described.
[0067] LAA provides a unified global solution framework that enables compliance with all regional regulatory requirements. A unified global solution framework for LAA is defined, where appropriate, to ensure that LAA can be operated in accordance with all regional regulatory requirements. Furthermore, the LAA design should be sufficiently configurable to enable efficient operation in different geographical regions. LAA configurations ideally aim for fair coexistence with existing Wi-Fi networks, so that they do not impact Wi-Fi services in terms of throughput and latency more than an additional Wi-Fi network on the same carrier. The LAA configuration ideally aims for fair coexistence between LAA networks provided by different operators, so that the LAA networks can achieve comparable performance in terms of throughput and latency. LAA functionalitiesListen-before-talk (Clear Channel Assessment).
[0068] The listen-before-talk (LBT) procedure is defined as a mechanism by which a user device performs a clear channel assessment (CCA) before using the channel. CCA uses, at a minimum, energy sensing to determine the presence or absence of other signals on a channel, thus determining whether a channel is occupied or clear. European and Japanese regulations mandate the use of LBT in the unlicensed bands. In addition to regulatory requirements, carrier sensing via LBT is a way to fairly share the unlicensed spectrum and is therefore a feature of fair and friendly operation in the unlicensed spectrum within a single global solution framework.
[0069] Discontinuous transmission on a carrier with a limited maximum transmission time.
[0070] In unlicensed spectrum, channel availability cannot always be guaranteed. Furthermore, certain regions, such as Europe and Japan, prohibit continuous transmission and limit the maximum duration of a transmission burst in unlicensed spectrum. Therefore, discontinuous transmission with a limited maximum transmission duration is a required functionality for LAA.
[0071] Dynamic frequency selection for radar avoidance in specific bands / regions.
[0072] Dynamic Frequency Selection (DFS) is a legal requirement for some frequency bands, e.g. to detect interference from radar systems and avoid co-channel operation with these systems by selecting a different carrier on a relatively slow time scale. Carrier selection
[0073] Since there is a large available range of unlicensed spectrum, LAA nodes must perform carrier selection to select low-interference carriers and achieve good coexistence with other deployments in the unlicensed spectrum. Transmit power control
[0074] Transmit Power Control (TPC) is a legal requirement in some regions, which requires the transmitter to be able to reduce the transmit power by 3 dB or 6 dB compared to the maximum nominal transmit power. RRM measurements including cell identification
[0075] Radio Resource Management (RRM) measurements, including cell identification, enable mobility between SCells and robust operation in the unlicensed area.
[0076] Automatic Gain Control (AGC) adjustment, coarse synchronization, fine frequency / time estimation at least for demodulation, channel state information (CSI) measurement, including channel and interference.
[0077] These are used to perform RRM measurements and to successfully receive information on the unlicensed band. Discovery Reference Signal (DRS)
[0078] TS 36.211 V14.3.0 (2017-06) describes DRS as supporting the switching on / off of small cells, with secondary CCs being able to be switched off, except for periodic DRS transmission. DRS is used by the UE to perform mobility measurements and maintain synchronization. The signals that comprise DRS include the PSS, the SSS, the CRS, and, if applicable, the CSI-RS.
[0079] The UE is configured with a Discovery Measurement Timing (DMTC) configuration, which is a time window during which the UE can expect to receive the DRS.
[0080] Although a DRS event can occur anywhere in the DMTC, the UE can assume that the DRS is transmitted by a given cell such that the duration between consecutive DRS transmissions is fixed (e.g., 40, 80, or 160 milliseconds).
[0081] LBT requirements in some regions may allow the DRS to be transmitted as a short control transfer without LBT (however, this is not permitted in some regions, e.g. Japan).
[0082] DRS are also used in LAA (which precedes CCA) and form the basis for radio resource management, including cell identification.
[0083] When applying LBT to DRS transmissions, there may be some cases where the DRS cannot be transmitted periodically (e.g., DRS transmitted on a cell in licensed spectrum). The following two options can then be considered for the DRS design for LAA. 1) Under LBT, DRS is transmitted at a fixed time position in the configured DMTC. 2) Under LBT, the DRS may be transmitted at at least one of different time positions in the configured DMTC.
[0084] Two cases for DRS transmission. Case 1:
[0085] If the DRS is transmitted together with the PDSCH: it is automatically subject to LBT CAT 4.
[0086] Simultaneous transmission (or multiplexing) of a DRS and a PDSCH is only possible in subframes 0 and 5. Case 2:
[0087] If the DRS is not part of a transmission burst, the DRS must be preceded by a 25 µs spanning CCA (ie LBT CAT 2).
[0088] Because the exact time at which the DRS is transmitted depends on the CCA, the detection signal can move in time, and the device must detect whether a DRS is being transmitted or not before basing measurements on it. This is not required in licensed spectrum.
[0089] In traditional RANs (or upper-layer splits), where the MAC, scheduler, PHY, and RF are all located in the same box, the RRU 105 competes for spectrum using LBT techniques. Once the LBT is successful, the PHY informs the scheduler / MAC of the target subframe / slot where transmission begins. The scheduler / MAC, in turn, sends the data to be transmitted OTA. The RRU 105 then transmits this data OTA. It can be seen that there is traditionally very little or no communication latency between the lower layers. Regarding the present disclosure, there is no work related to the implementation of unlicensed LTE technologies for lower-layer splits. As can be seen, embodiments can also be applied to other unlicensed LTE technologies, such as MulteFire and CBRS.
[0090] Fig. 4 shows a shading code that can be used in the following Fig. 4-10 is used. A prerequisite for supporting LAA in C-RAN with non-ideal fronthaul is that the BBU 103 is forced to send the scheduled data to the RRU 105 in advance. The reason for this is that the RRU 105 should acquire the channel (and send the data OTA) immediately after the spectrum sensing is completed (within 9 µs). Due to the presence of reference signals, data originating from the BBU 103 is TTI-specific (i.e., data transmitted in the TTI is a function of the specific TTI index). However, the BBU 103 does not know the specific TTI at which the RRU 105 starts transmitting, as this depends on several random variables, such as the number of eNBs and Wi-Fi APs sharing the spectrum, the LBT result, interference channels, and the like.
[0091] In the Fig.Figures 4-10 describe embodiments of methods for addressing the non-ideal LAA support described above. Let MCOT = N ms (e.g., N = 8 ms for priority classes 3 and 4 when Wi-Fi is allowed to use the channel. The RRU 105 only transmits for, for example, 7 ms, since the first subframe is typically wasted sending reservation signals after LBT success. Assume no partial subframes). While the following figures use N = 8 as an example, the embodiments are not limited to any particular priority class or MCOT duration.
[0092] It should also be noted that some of the following exemplary embodiments apply not only to data transmission, but also to DRS transmission. The DRS duration is much shorter than for data (approximately 12 OFDM symbols < 1 ms). Embodiment 1:
[0093] Fig.Figure 5 shows an embodiment in which the L2 (BBU) sends N - 1 ms data to the LPHY (RRU) via the fronthaul interface. These data are assembled based on the assumption that the OTA transmission only starts on a specific, predefined subframe. In this example, the start of the data transmission occurs, for example, on subframe 0, but both the BBU 103 and the RRU 105 can agree on any other subframe index.
[0094] This data is sent a few milliseconds before the RRU 105 is scheduled to perform the LBT. For example, the BBU 103 may send the data to the RRU 105 30 ms before the LBT process begins for that specific data.
[0095] In each LTE frame, the RRU 105 competes for the channel at the beginning of the subframe preceding the target subframe for data transmission. In this example, the RRU 105 competes in subframe 9 of each frame.
[0096] If the RRU 105 gains access before the end of subframe 9, it next sends a reservation signal until the end of subframe 9 and then transmits the N - 1 subframes OTA.
[0097] If RRU 105 does not receive access before the end of subframe 9, it remains silent and competes again on the following 9th subframe.
[0098] Exemplary advantages of the embodiment include a simple scheduler design, with a fixed amount of scheduled data and no subframe dropping. Another advantage is optimized operation when no other technology is sharing the spectrum, as fewer subframes are wasted.
[0099] In another aspect of the embodiment, the method can be applied to DRS transmission. The DRS position is fixed to a specific subframe (e.g., subframe 0 in each DMTC period). The BBU 103 sends the DRS signal to the RRU 105 one or two subframes before the terminated subframe (e.g., subframe 8). The RRU 105 contends for the channel at the preceding subframe (e.g., subframe 9). If the channel is idle, the RRU 105 transmits the DRS signals, for example, at subframe 0. If the channel is busy, the RRU 105 skips the DRS transmission and contends for the channel again after DMTC. Embodiment 2:
[0100] Fig.Figure 6 shows an embodiment in which L2 in the BBU 103 sends data, for example, 10 ms worth, to the LPHY in the RRU 105 via the fronthaul interface. The RRU 105 contends for the channel as soon as it receives the DL data in any subframe (i.e., no restrictions on the subframe used for LBT).
[0101] After the RRU 105 gains channel access, it drops the 10 - N + 1 subframes that do not overlap with the OTA transmission and transmits the remaining N - 1 subframes. For example, if the RRU 105 receives LBT while idle on subframe 7 (assuming N = 8), the RRU drops 3 subframes (subframes 5, 6, and 7) and transmits on subframes 8, 9, 0, 1, 2, 3, and 4.
[0102] An RLC layer is configured to handle dropped subframes and retransmit them on licensed carriers.
[0103] For example, an exemplary advantage of the embodiment is that the RRU 105 competes for the channel at any given time, therefore there is no latency in spectrum acquisition and higher spectrum efficiency is achieved.
[0104] In another aspect of the embodiment, assuming MCOT = 10 ms (as an example), BBU 103 sends 10 ms worth of data to RRU 105. RRU 105 contends for the channel at any given time as soon as it receives the data from BBU 103. RRU 105 then reorganizes the data based on the subframe at which it gains access to the channel. For example, if RRU 105 begins transmitting on subframe 3 (as an example), it appends the data scheduled for subframes 0, 1, and 2 to the end of the MCOT. In this case, RRU 105 transmits subframes 3-9, then subframes 0, 1, and 2. Embodiment 3:
[0105] Fig.7 shows an embodiment which is a modification of Embodiment 2.
[0106] The RRU 105 drops 3 subframes (assuming N = 8) for each frame based on the LBT success time. In Embodiment 3, the RRU 105 has queued these subframes in a buffer. The RRU 105 then recontest for a smaller MCOT (to transmit the dropped subframes) whenever an opportunity arises (e.g., no data in the RRU 105's buffer, no strict latency requirements for regular data in the RRU 105's buffer, and the like). Because the queued data (left over from previous frames) is assembled for transmission on specific subframes, the RRU 105 can use the proxy / reservation signal to block the channel until the target time occurs.
[0107] The RRU 105 places dropped subframes into a corresponding OTA subframe for correct positioning of reference signals and a PDCCH CCE index. Furthermore, the RRU 105 can block the channel between subframes based on the subframe index of the remaining data. If data is present in the RRU 105 buffer, the RRU 105 can aggregate the dropped subframes and transmit them as soon as subframes can be aggregated into a single MCOT (or in a transmission with a shorter duration than the MCOT). The RRU 105 can maintain two buffers: one for traditional data and another for aggregated subframes.
[0108] An exemplary advantage of the embodiment is, among other things, that the RRU 105 competes for the channel at any given time, thus achieving zero latency in spectrum acquisition and greater spectrum efficiency. Another exemplary advantage is the reduced likelihood of dropped subframes. Embodiment 4
[0109] Fig. Figure 8 shows an embodiment where the reference signals are generated in the RRU 105 instead of the BBU 103. L2 (BBU 103) transmits only PDSCH to L1 (RRU 105), with all resource elements (REs) for reference signals (PSS / SSS / CRS, and the like) empty. The RRU 105 assembles these reference signals based on the time it gains access to the channel.
[0110] An exemplary advantage of the embodiment is high spectrum efficiency (no latency for measurement, no dropped subframes). Embodiment 5
[0111] Fig. 9 shows an embodiment which is a modification of Embodiment 2.
[0112] The RRU 105 applies more intelligence when dropping subframes from a transmission burst. The BBU 103 sends 10 ms of data to the RRU 105 via the fronthaul interface (for example). The RRU 105 transmits data from transmission bursts in a continuous manner, dropping one subframe for LBT each time. In this case, if a channel is available, only one subframe is dropped, and the RLC overhead is reduced. If the channel is busy, the RRU 105 drops the subframes that were terminated during the LBT process (in Fig. 6, the RRU 105 drops subframes 5-9, for example. Data dropped at the RRU 105 can be recovered through RLC retransmissions triggered by UE RLC NACKs. RLC retransmissions are always performed on a licensed primary cell. Embodiment 6
[0113] Fig. Figure 10 shows an embodiment where it is assumed that the fronthaul delay is known and is 10 ms.
[0114] The expected time required to gain access to the channel is estimated, i.e., the LBT delay profile, as explained below. Multiple copies (e.g., 3 copies) of the TBs for the MCOT duration are sent to the RRU 105 based on the delay profile (most likely delays). The RRU 105 maintains the multiple copies in different queues. Based on the actual time at which access to the channel is gained, the RRU 105 selects the correct queue and sends the data to the UE. The RRU 105 updates the BBU 103 regarding the selected copy so that the BBU 103 knows when to expect the HARQ ACK (note that the HARQ ACK does not have a process number).
[0115] Note that the BBU 103 receives the RRU 105 update (i.e., which copy was transmitted) before the corresponding HARQ-ACK reaches the MAC at the BBU 103 from the licensed bearer (which is transmitted 4 ms after data reception at the UE). This is assumed that the fronthaul delay variance is very small.
[0116] In various embodiments, this configuration and method can be used for low traffic cases (a small number of UEs with low usage) or applications (e.g., IoT).
[0117] An exemplary advantage of the embodiment is high spectrum efficiency. LBT delay profile.First: Offline phase:
[0118] An LBT delay profile can be empirically estimated offline for different environments and interference conditions (e.g., number of neighboring Wi-Fi STAs, indoor versus outdoor, etc.). For each delay profile, there is a LUT for the number of replicas and delay taps (e.g., 3 replicas at n - 2, n, and n + 2, where n is the subframe index based on the expected online LBT delay).
[0119] Second: Online phase, history-based assessment:
[0120] During boot-up, the RRU 105 executes the LBT code internally (i.e., listens to the medium without actually transmitting) and obtains an estimate of the actual LBT delay. Measurements are signaled to the BBU. Periodically, and for low-traffic scenarios, the RRU 105 repeats the measurements and reports them to the BBU. Transfer phase:
[0121] The RRU 105 checks the operating conditions and selects the appropriate delay profile, number of copies and delay taps. Embodiment 7
[0122] Embodiment 7 is a modification of Embodiment 6. Instead of sending multiple copies of the same data with different transmission start times, the vBBU 103 can send different data streams with different transmission start times to the RRU 105. After gaining access to the channel, the RRU 105 selects the stream that best matches the starting TTI. After performing the selection process, the RRU 105 reports the selected data stream to the vBBU 103. Whenever a data stream becomes outdated, the vBBU 103 is also updated. The vBBU 103 updates its scheduling plan based on the RRU 105 reports and reschedules the expired data streams at the RRU 105 for new LAA transmissions. Once the packets have exceeded a certain delay threshold (waiting for transmission on unlicensed spectrum), they are retransmitted by the RLC layer on the licensed band. Embodiment 8
[0123] In Embodiment 8, the TTI-dependent bits are first modified at the RRU 105. Then, the LBT delay is estimated. A single transmission (MCOT) is sent to the RRU 105 based on the best estimate. Along with the transmission, pointers to the TTI-dependent bits are sent to the RRU 105, or modifications required to the RRU 105 for different start times based on the LBT delay profile are sent. The RRU 105 then contends for the medium using LBT and waits for the idle result.
[0124] Once an idle result is received, the RRU 105 either (a) transmits the received MCOT as is (if the LBT delay estimate is accurate) or (b) modifies the TTI-dependent bits based on the pointers sent by the vBBU 103 to account for the change in the MCOT's starting TTI (if any). The RRU 105 sends an update report to the vBBU 103 regarding the changes made to the RRU 105.
[0125] In the following embodiment, the following sections refer to the XRAN-FH.CUS.0-v01.00.02 (2018-04-04) standard, which is incorporated herein by reference in its entirety, with the section headings applying to Chapter 5, C-Layer Protocol. 5.3.2 LAA command transfer procedure
[0126] The LAA command transfer procedure is used to exchange C-layer messages between the ILS CU and the RU. The primary purpose of these messages is to support the LAA function in the RU / ILS CU. 5.3.2.1 LBT procedure
[0127] The LBT procedure is used to configure the RU with the parameters required to perform LBT prior to the PDSCH or DRS OTA transmission. The RU must report the outcome of the LBT process (either success or failure) in the notification message.
[0128] In contrast to licensed spectrum, where the RU can continuously transmit data or reference signals OTA, the RU in unlicensed spectrum can only transmit discontinuous data bursts (of MCOT length) or periodic DRS signals. In an embodiment as described in Fig.As shown in Figure 11, an "LBT_DL_CONFIG.request" message 10 is sent once before each OTA transmission on the LAA SCell. This includes both DRS and PDSCH (i.e., MCOT burst) transmissions. The RU responds to each LBT_DL_CONFIG.request message 10 with the "LBT_DL.indication" message 12, which contains the LBT result.
[0129] For the DRS signal, the lls-CU first configures the RU with the DRS parameters (DMTC period and DMTC offset) via the M-layer.
[0130] Before each DRS period, the ILS CU sends the LBT_DL_CONFIG.request message and the DRS signal. The RU performs LBT and transmits the DRS signal OTA. The RU must then send the LBT_DL.indication message.
[0131] The DRS signal can be transmitted over the fronthaul interface similar to other reference signals such as PSS / SSS / CRS.
[0132] The following describes message fields and messaging settings related to Fig. 11 are described. 5.4 Elements for the C-layer protocol 5.4.1 General
[0133] C-layer messages are encapsulated using a two-layer header approach. The first layer has a common eCPRI header and corresponding fields used to specify the message type, while the second layer is an application layer containing the required fields for control and synchronization. Within the application layer, a "section" defines the characteristics of U-layer data to be transmitted or received by a beam, using a pattern ID. A Type 7 LAA section is supported in the C-layer for LAA messages. LAA messages, communicated in both directions between the ILS CU and the RU, enable LBT for PDSCH / DRS transmission. Initial carrier selection and dynamic frequency selection (DFS) are enabled by communicating a few messages between the ILS CU and the RU using the management plane (M-layer).
[0134] Table 1 describes the section types supported in the C layer. Table 1 Section type Target scenario Notes 0 Unused resource blocks or symbols in downlink or uplink Indicates to the RU that certain resource blocks or symbols are not being used (idle periods, guard periods). Likewise, there are no associated U-layer messages with IQ data for this section type. The purpose is to inform the RU that transmissions can be paused during the specified idle interval, e.g., to conserve power or to provide an interval for calibration. 1 Most DL / UL radio channels Here, "most" refers to channels that do not require a time or frequency offset, as is needed for channels with mixed numerology 2 Reserved for future use 3 PRACH channels and channels with mixed numerology Channels that require time or frequency offsets, or channels with a different numerology than the nominal SCS values 4 Reserved for future use 5 UE termination information (UE ID assignment to section) Provides termination information to the UE IDs 6 Channel information Sends UE-specific channel information from the lls-CU to the RU 7 LAA Messages communicated in both directions between the lls-CU and the RU to enable LBT for PDSCH / DRS transmission, initial carrier selection, and dynamic frequency selection (DFS) 8-255 Reserved for future use
[0135] The section type 7 fields used to support LAA are as follows: ▪ Common header fields ▪ dataDirection (data direction (gNB Tx / Rx)) field: 1 bit ▪ payloadVersion (payload version) field: 3 bits • Value = “1” should be set (1st protocol version for user data and time reference format) ▪ filterIndex (filter index) field: 4 bits ▪ frameld (frame identifier) field: 8 bits ▪ subframeId (subframe identifier) field: 4 bits ▪ slotID (slot identifier) field: 6 bits ▪ startSymbolid (start symbol identifier) field: 6 bits ▪ numberOfsections (number of sections) field: 8 bits ▪ sectionType field: 8 bits • Value = “7” should be set ▪ reserved (reserved for future use) field: 8 bits ▪ Section fields sectionId (Section ID) field: 16 bits
[0136] A value = “0” should be used for LBT_DL_CONFIG.request 10 be set: LBT_PDSCH_REQ ▪ handle (an unclear handling returned in the LBT_PDSCH_RSP) field: 16 bits ▪ deferFactor (deferral factor when measuring slots, as described in 3GPP TS 36.213 section 15.1.1) field: 3 bits ▪ backoffCounter (LBT backoff counter when measuring slots, as described in 3GPP TS 36.213 section 15.1.1) field: 10 bits ▪ offset (LBT start time in microseconds from the start of the subframe terminated in this message) field: 10 bits ▪ MCOT (LTE TXOP duration in subframes) field: 4 bits ▪ txopSfnSfEnd (SFN / SF where TXOP must end) field: 12 bits ▪ IbtMode (Part of the multi-carrier support. Indicates whether the full LBT process is carried or a partial LBT process is carried (Multi-carrier Mode B according to 3GPP TS 36.213 section 15.1.5.2)) field: 1 bit: • 0 - full LBT (regular LBT) • 1 - partial LBT (look back 25 µs before transmission, as specified in 3GPP TS 36.213 section 15.1.5.2)
[0137] A value = "1" should be set for LBT_DL_CONFIG.request 10: LBT_DRS_REQ ▪ handle (an unclear handling returned in the LBT_PDSCH_RSP) field: 16 bits ▪ offset (LBT start time in microseconds from the start of the subframe terminated in this message) field: 10 bits ▪ sfnSfEnd (SFN / SF at which the DRS window must end) field: 12 bits ▪ IbtMode (Part of the multi-carrier support. Indicates whether the full LBT process is carried or a partial LBT process is carried (Multi-carrier Mode B according to 3GPP TS 36.213 section 15.1.5.2)) field: 1 bit: • 0 - full LBT (regular LBT) • 1 - partial LBT (look back 25 µs before transmission, as specified in 3GPP TS 36.213 section 15.1.5.2) ▪ reserved (reserved for future use) field: 1 bit
[0138] A value = “2” should be set for LBT_DL.indication 12: LBT_PDSCH_RSP ▪ handle (an unclear handling returned in the LBT_PDSCH_RSP) field: 16 bits ▪ IbtResult (LBT result from SFN / SF) field: 1 bit • 0 - SUCCESS - indicates that the channel was successfully acquired • FAILURE - indicates that the channel could not be acquired at the end of SFN / SF ▪ lteTxopSymbols (Actual LTE TXOP in symbols. Valid if LBT result = SUCCESS) field: 14 bits ▪ initialPartialSF (Specifies whether the first SF in the LBT process is complete or partial) field: 1 bit • 0 - full SF (two slots, 14 symbols) • 1 - partial SF (second slot only, the last 7 symbols)
[0139] A value = “3” should be set for LBT_DL.indication 12: LBT_DRS_RSP ▪ handle (an unclear handling returned in the LBT_PDSCH_RSP) field: 16 bits ▪ IbtResult (LBT result from SFN / SF) field: 1 bit • 0 - SUCCESS - indicates that DRS is being sent • 1 - FAILURE - indicates that DRS is not sent ▪ reserved (reserved for future use) field: 7 bits 5.4.5 Coding of information elements - Application layer, sections
[0140] Descriptions and coding of information elements of the above fields are as follows: 5.4.5.19 handle
[0141] Description: This parameter provides a marker that is included in the configuration request message (e.g., LBT_PDSCH_REQ, LBT_DRS_REQ) sent by the lls CU to the RU and returned in the corresponding response message (e.g., LBT_PDSCH_RSP, LBT_DRS_RSP). Value range: {0000 0000 0000 00006-1111 1111 1111 1111b} Type: unsigned integer. Field length: 16 bits. 5.4.5.20 deferFactor (deferral factor)
[0142] Description: Shift factor for slot measurement, as described in 3GPP TS 36.213, Section 15.1.1. This parameter is used for LBT CAT 4 and can take one of three values: {1, 3, 7} based on the priority class. Four priority classes are defined in 3GPP TS 36.213. Value range: {001b, 011b, 111b} or {1, 3, 7} in decimal system. Type: unsigned integer. Field length: 3 bits. 5.4.5.21 backoffCounter (Backoff counter)
[0143] Description: LBT backoff counter when measuring slots, as described in 3GPP TS 36.213, Section 15.1.1. This parameter is used for LBT CAT 4 and can take one of nine values: {3, 7, 15, 31, 63, 127, 255, 511, 1023} based on the priority class. Four priority classes are defined in 3GPP TS 36.213. Value range: {3, 7, 15, 31, 63, 127, 255, 511, 1023} in decimal notation. Type: unsigned integer. Field length: 10 bits. 5.4.5.22 offset
[0144] Description: LBT start time in microseconds from the beginning of the subframe terminated by this message. Value range: {00 0000 00006 - 11 1110 0111b} or {0 - 999} in decimal system Type: unsigned integer. Field length: 10 bits. 5.4.4.23 MCOT (Maximum Channel Occupancy Time)
[0145] Description: LTE TXOP duration in subframes, as described in 3GPP TS 36.213, Section 15.1.1. This parameter can take one of four values: {2, 3, 8, 10} based on the priority class. Four priority classes are defined in 3GPP TS 36.213. Value range: {0010, 0011, 1000, 1010} or {2, 3, 8, 10} in decimal system. Type: unsigned integer. Field length: 4 bits. 5.4.5.24 txopSfnSfEnd (TXOP-SFN / SF-End)
[0146] Description: SFN / SF where TXOP must end Value range: SFN: {0000 0000b - 1111 1111b} or {0 - 255} in decimal system, SF: {0000 - 1001} or {0 - 9} in decimal system. Type: unsigned integer. Field length: 12 bits. 5.4.5.25 IbtMode (LBT mode)
[0147] Description: Part of the multi-carrier support. Specifies whether a full LBT process is carried or a partial LBT process is carried (multi-carrier mode B according to 3GPP TS 36.213, section 15.1.5.2). 0 - full LBT (regular LBT). 1 - partial LBT (lookback 25 µs before transmission, as specified in 3GPP TS 36.213, section 15.1.5.2). Value range: {0, 1} Type: unsigned integer. Field length: 1 bit. 5.4.5.26 sfnSfEnd (SFN / SF end)
[0148] Description: SFN / SF where the DRS window must end Value range: SFN: {0000 0000b - 1111 1111b} or {0 - 255} in decimal system, SF: {0000b - 1001b} or {0 - 9} in decimal system. Type: unsigned integer. Field length: 12 bits. 5.4.5.27 IbtResult (LBT result)
[0149] Description: LBT result of SFN / SF. 0 - SUCCESS - indicates that the channel was successfully acquired. 1 - FAILURE - indicates that the channel could not be acquired by the end of the SFN / SF. Value range: {0,1} Type: unsigned integer. Field length: 1 bit. 5.4.5.28 lteTxopSymbols (LTE TXOP symbols)
[0150] Description: Actual LTE TXOP in symbols. Valid if LBT result = SUCCESS. Value range: For LTE, {00 0000 0000 1110b - 00 0000 1000 1100b} or {14 - 140 symbols} in decimal. Type: unsigned integer. Field length: 14 bits. 5.4.5.29 initialPartialSF (Initial Partial SF)
[0151] Description: Specifies whether the initial SF in the LBT process is full or partial. 0 - full SF (two slots, 14 symbols). 1 - partial SF (second slot only, last 7 symbols). Value range: {0, 1} Type: unsigned integer. Field length: 1 bit. Carrier selection (dynamic frequency selection)
[0152] Because LAA uses unlicensed spectrum for communication, shared with Wi-Fi and other technologies, the RRU 105 must select the best channel to use from the unlicensed band (e.g., UNII band or band 46). This process must be performed initially (carrier selection) and periodically (dynamic frequency selection).
[0153] In another embodiment, as in Fig.As shown in Figure 12, a channel selection and DFS procedure is used by the RU to report initial and periodic RRU 105 channel measurements 14 to the ILS CU 102. Based on the received measurements and other statistics collected during operation, the ILS CU 102 may send a cell reconfig message 16 to reconfigure the LAA SCell with a new unlicensed channel to operate on. The RRU 105 acknowledges 18 receipt of the cell reconfiguration message. In the embodiment, for initial carrier selection (i.e., prior to the OTA transmission), the procedure may be executed once. After starting the OTA transmission, this procedure may be executed periodically, as configured by the M layer.
[0154] To select the best channel, the RRU 105 performs periodic measurements and reports these measurements to the BBU 103. Various measurements can be performed by the RRU 105, such as calculating the average RSSI, the utilization rate, and the like.
[0155] The BBU 103 uses these measurements to select the “optimal” channel to use and then reconfigures the RRU 105 with the new selected channel.
[0156] The BBU 103 receives two metrics from the LPHY in the RRU 105 for each channel f c ∈ A, where A is the set of channels in the unlicensed band (e.g. A = [5,745, 5,765, ..., 5,825) if the selected band is the UNII-3, which has five channels):
[0157] Capacity utilization rate R o (f c ): Percentage of the ON time of the total measurement time (e.g. 100 ms).
[0158] Average RSSI P(f c): Average RSSI over the entire measurement period.
[0159] Next, the present disclosure explains how L3 in the BBU 103 initially selects the unlicensed channel(s) on which to operate, and further explains how dynamic frequency selection (DFS) is periodically performed to reselect the best channel(s) while minimizing service disruption.
[0160] The present disclosure first describes the case of a single LAA-SCell and then moves to the case of multiple cells. Single LAA-SCellInitial carrier selection
[0161] The selected channel fc* can be calculated using the following methods. For illustrative purposes, it is assumed that the BBU / RRU uses the UNII-3 band, which consists of five channels: fc*={argminfc∈A{Ro(fC1),Ro(fc2),…,Ro(fc5)},if (Ro(fcmin+1)−Ro(fcmin))>RoThGapargminfc∈A{P¯(fcmin),P¯(fcmin+1)},else
[0162] There are fc*min+1 the immediate f c with a higher utilization rate or RSSI than the minimum and RoThGap is the threshold difference between the utilization levels (e.g. RedThGap=20% ) Dynamic frequency selection
[0163] Embodiments of dynamic frequency selection (DFS) configurations and methods are described to avoid frequent frequency hopping.
[0164] In one embodiment (1), the DFS period is increased to a larger number (e.g., 10 s) and the main equation is applied (i.e., selecting the best channel in each DFS period).
[0165] In another embodiment (2), the RRU 105 continues to use the same channel until Ro(fc*)≥Roth or P(f c ) ≥ p th . Once one of the conditions is met, the BBU 103 is configured to use instructions for DFS in accordance with Ro(fc*)≥Roth or P(f c ) ≥ p th and selects the best channel based on the measurements of the RRU 105.
[0166] In another embodiment, the system operates in a similar manner to the previous embodiment (2), but instead adding a constraint on the LBT delay. Specifically, the RRU 105 continues to use the same (initially selected) channel until the average LBT delay exceeds a predefined threshold. After this condition is met, the BBU 103 operates using instructions for DFS according to Ro(fc*)≥Roth or P(f c ) ≥ p thand selects the best channel based on the measurements of the RRU 105.
[0167] Embodiments of configurations and methods in which the DFS period is a configurable parameter that can be changed by the BBU 103 based on channel availability are described.
[0168] Measurements could be performed continuously by sniffers in the RRU 105.
[0169] In one embodiment (1): the RRU 105 reports a summary of measurements averaged over a period of time. In this embodiment, the RRU 105 collects measurements locally for a period of time, processes them, and sends the final metrics to the BBU 103, which is to make a decision about which channel to use. An exemplary advantage of this embodiment is that it reduces fronthaul overhead. The embodiment also adds more processing to the RRU 105.
[0170] In one embodiment (2): the RRU 105 continuously reports individual measurements to the BBU 103.
[0171] In an embodiment (3): the BBU 103 adapts the measurement reporting procedure based on the traffic, the processing capabilities of the RRU 105, and the like. Carrier aggregation (two or more LAA-SCells)
[0172] Embodiments of carrier aggregation for a plurality of LAA-SC cells are described.
[0173] As can be seen, 3GPP TS 36.300 V14.3.0 (2017-06) specifies a standard restriction that states: “If the absence of IEEE802.11n / 11ac devices sharing the carrier cannot be guaranteed in the long term (e.g., due to the level of regulation) and if, for this version, the maximum number of unlicensed channels on which E-UTRAN can transmit simultaneously is equal to or less than 4, the maximum frequency spacing between any two carrier center frequencies on which LAA-SCell transmissions are performed should be less than or equal to 62 MHz. The UE must support the frequency spacing according to TS 36.133
[21] .” Consequently, combinations between 4 adjacent channels are allowed.
[0174] An embodiment of channel selection for the LAA-CA case is described using the example of BBU / RRU using the UNII-3 band. The UNII-3 band consists of five channels, as shown in Table 1 below.
[0175] Based on the 3GPP TS 36.300 restriction specified above, the BBU / RRU may have limited combinations available when performing CA for unlicensed cells. For example, based on the example shown in Table 2, all two-channel combinations are allowed except for the pair (149, 165). For illustrative purposes, the above channels are described using channel indices 1, 2, ..., 5.
[0176] The selected channels fc* and fc** can be calculated as follows: (fc',fc")={argminfc∈A{(Ro(fc1)+Ro(fc2)2),(Ro(fc1)+Ro(fc3)2),⋯(Ro(fc1)+Ro(fcS)2)},if (Ro¯(fcmin+1,f'cmin+1),Ro¯(fcmin,f'cmin))>RoThGapargminfc∈A{P¯arg(fcmin,f'cmin),P¯avg(fcmin+1,f'cmin+1)},else
[0177] The BBU 103 then calculates the average utilization levels of all valid channel combinations. If the difference between the two lowest average utilization levels is greater than a threshold, the BBU 103 selects the channel with the minimum utilization level.
[0178] Otherwise, the BBU 103 proceeds to a second comparison level where it selects the channel with the minimum average RSSI (from the two channels with the lowest utilization levels). Cell addition for LAA-capable UEs
[0179] Embodiments for cell addition for LAA-capable UEs are described.
[0180] One challenge facing LAA-enabled eNBs in a C-RAN architecture or in traditional RANs is cell addition for LAA-enabled UEs, including cases where both licensed and unlicensed cells are available. As described here, licensed spectrum is more reliable than unlicensed spectrum because operators have exclusive rights to use it, unlike unlicensed spectrum, which is shared between different technologies. However, licensed spectrum is scarce and expensive, while unlicensed spectrum is abundant and free.
[0181] Embodiments are described that address cell addition in licensed and unlicensed spectrum for LAA-capable UEs. One embodiment, as described herein, enables the eNB (or the BBU 103 in the C-RAN architecture) to select the best cell to add to the UE based on various metrics, such as load in the cell, channel state information (CSI), UE capabilities, and the like. For simplicity, embodiments are described that assume the eNB is attempting to add a second (licensed or unlicensed) cell to a UE that is already attached to the eNB using the licensed primary cell.
[0182] In one embodiment, the eNB considers a weighted sum of the following factors while selecting the cell to be added to the UE. In another embodiment, the process begins with a first step (i.e., loads in the cell) and then considers a second step (i.e., channel gains) only if the first step leads to an indeterminate decision (e.g., values close to the thresholds).
[0183] In one embodiment (1), the eNB first checks the cell loads of both licensed and unlicensed cells. One criterion determines whether the load in a licensed cell is less than a predefined threshold (e.g., 70%), and the eNB adds the licensed cell to the UE. The reason for this selection is that licensed cells are more reliable than unlicensed cells and should be used whenever they are available. Another criterion can determine whether the difference between the load in the licensed and unlicensed cells is less than a predefined threshold (e.g., both cells have comparable loads, e.g., within 20%), and the eNB adds the licensed cell to the UE. Otherwise, the unlicensed cell is added to the UE.
[0184] Next, (2) the eNB checks the channel gains of both the licensed and unlicensed cells and follows similar criteria as described above (1) when selecting the cell to be added to the UE.
[0185] If all licensed channels are loaded, then (3) the unlicensed channels can be used for new UEs requiring more data throughput. At this point, the periodic switching of UEs between licensed and unlicensed channels is performed taking into account the UE capabilities (i.e., legacy load versus Rel. 13-capable UEs). LBT parameter update
[0186] A characteristic of LTE in unlicensed bands (e.g., LAA) is the dependency between the LBT parameters (e.g., contention window) and the UE HARQ response. The RRU 105 must vary the contention window parameters based on the LBT Category 4 rules (e.g., doubling the contention window for each collision).
[0187] In C-RAN systems, the LBT parameters are sent from the BBU 103 to the RRU 105 for each MCOT. This causes a problem for systems with non-zero fronthaul latency, because the BBU 103 must pre-send the LBT parameters to the RRU 105 before the HARQ even reaches the BBU. Several embodiments are configured to address this problem.
[0188] In one embodiment, a false NACK message is used to update LBT parameters. In this embodiment, the RRU 105 updates the LBT parameters (e.g., the contention window) assuming a false NACK is received from the UE. For example, and for priority class 3, the RRU 105 uses CW ~ [0,15] for the 1st attempt, [0,31] for the 2nd attempt, and [0,63] for the > 3rd attempt until the current data stream ends.
[0189] In one embodiment, a HARQ ACK estimation message is based on the number of freeze times (N FT ) during the LBT. In the embodiment, the RRU 105 estimates the HARQ response internally based on the number of timer freeze times during the LBT. For example, if N FT ≤ 1, HARQ ACK is assumed, otherwise HARQ NACK is assumed.
[0190] In one embodiment, a false NACK message is used for LBT parameter updates until a first HARQ ACK / NACK is received. In this embodiment (assuming priority class 3), the RRU 105 uses CW ~ [0,15] for the 1st attempt, [0,31] for the 2nd attempt, and [0,63] for the > 3rd attempt. Once the first HARQ ACK / NACK message is received at the BBU 103, the LBT parameters are updated in a delayed manner (due to fronthaul latency). This method is well suited for cases where there is a high correlation of the HARQ ACK / NACK result between neighboring MCOTs.
[0191] In the following embodiments, the following sections refer, among other things, to the XRAN-FH.CUS.0-v01.00.02 (2018-04-04) standard, which is incorporated herein by reference in its entirety.
[0192] RU / lls-CU messages are described in Table 3. Table 3 function RU / IIs-CU message Direction of the message Layer xRAN Scheduling RU RU capability request downstream M Initial handshake (Ils-CU requests regarding RU capability) RU Capability Info (Supporting LAA, No. LAA SCells, upstream M After each RU capability request message configuration maximum RU buffer size in symbols (per CC), RU processing time, supported bands, supported BW, etc.) RU Config (Number of LAA SCells, For each LAA CC: {DMTC Period, DMTC Offset, Initial Band, Total Carrier Selection Measurement Duration, DFS Measurement Reporting Period, LBT Timer}) downstream M After each RU capability update. If necessary, to reconfigure the RU with new parameters (e.g., measurement periods, etc.). Carrier selection and DFS startMeasurements: (Carrier selection or DFS) downstream M Lls-CU commands the RU to start the measurements stopMeasurements (only for DFS) downstream M Lls-CU orders the RU to stop the measurements RU measurements upstream M After the RU has finished scanning all channels in the configured band cellConfig / Reconfig downstream M After the Ils-CU has received the RU measurements and if a new channel needs to be configured cellReconfigACK upstream M After the RU receives the cell reconfiguration message LBT_DL_CONFIG. request: LBT_PDSCH_REQ downstream C Before each MCOT to reach the RU at / before the target SFN / SF for measurement LBT LBT_DL_CONFIG. request: LBT_DRS_REQ downstream C Before each DRS to reach the RU at / before the target SFN / SF for measurement LBT_DL.indication: LBT_PDSCH_RSP upstream C After each LBT for PDSCH (successful result or failure result if timer expires) LBT_DL.indication: LBT_DRS_RSP upstream C After each LBT for DRS (successful result or failure result if channel is busy) bufferError (overflow or underflow) upstream C If the received data at the RU is larger than the RU buffer size or the buffer is empty at the destination transmission time
[0193] While the disclosure describes in the examples given below that messages can be communicated between the ILS-CU and the RU via the management layer (M-layer), it should be appreciated and understood that this can also be done via the control layer (C-layer). It should also be understood that these messages can also be transmitted between the RU and the DU 104, or the RU and the CU 102, or the RU and the ILS-CU 102, depending on the C-RAN split used. Message details:
[0194] RU Capability Request (Management Layer or M-Layer): The lls-CU 102 sends a message to the RU requesting it to report its capabilities.
[0195] RU Capability Info (M-Layer): The RU responds to the Capability Request message with its capabilities, such as whether it supports LAA or not, the number of LAA cells it can support, the maximum buffer size per component carrier (CC), the RU processing time, the supported bands, the supported bandwidths, and the like.
[0196] RU Config: The lls-CU configures the RU with the required parameters, such as the number of LAA CCs, and the like. It also configures the RU for each unlicensed CC with the required parameters, such as the DMTC period, the DMTC offset, the default band to operate on, the default total measurement duration of the carrier selection, the default DFS measurement reporting period, the LBT timer, measurements to be performed (e.g., utilization level, average RSSI), and the like. It should be noted that other similar parameters could be added to the RU configuration message to help configure the RU with the default / required parameters. This can be sent initially (in the initial RU configuration) or during operation to reconfigure the RU.
[0197] Start Measurements: The lls-CU commands the RU to start measurements for either carrier selection or DFS. This can be indicated by a single bit. The Start Measurement message also includes the bands and specific channels that need to be scanned or measured (e.g., by sending the carrier frequency in kHz or the EARFCN: Evolved-UTRA Absolute Radio Frequency No.). It also includes the total measurement duration (in the case of carrier selection) or the measurement reporting period (in the case of DF). It can also include the type of measurements to be performed (e.g., load factor, average RSSI, and the like). It can also contain any other information the RU needs to perform the measurements.
[0198] Stop Measurements: The lls CU commands the RU to stop the DFS measurements.
[0199] RU Measurements: The RU reports the measurements to the ILS CU for each band and channel configured in the Start Measurement message. The reported measurements are performed for the identified measurement types (e.g., utilization rate and average RSSI, etc.).
[0200] A value = “n” should be set for RRU measurements ▪ bandNumber (3GPP band number) field: 8 bits ▪ carrierFrequencyKHz (carrier frequency in KHz) field: 32 bits ▪ averageRSSI (average RSSI) field: 8 bits ▪ occupancyRatio field: 8 bits ▪ carrierFrequencyKHz (carrier frequency in KHz) field: 32 bits ▪ averageRSSI (average RSSI) field: 8 bits ▪ occupancyRatio field: 8 bits...
[0201] A value = “n” should be set for cell reconfig 16 ▪ carrierFrequencyKHz (carrier frequency in KHz) field: 32 bits
[0202] A value = “n” should be set for cell reconfig ACK 18 ▪ ack (Acknowledgment) field: 1 bit bandNumber (Band Number) Description: 3GPP band number. Value range: {0000 0000b - 1111 1111b} Type: unsigned integer. Field length: 8 bits. carrierFrequencyKHz (carrier frequency in KHz)
[0203] Description: Carrier frequency in kHz when measurements are performed. The upper limit is 52.6 GHz. Value range: {0 - 52600} in decimal system. Type: unsigned integer. Field length: 16 bits. averageRSSI (average RSSI)
[0204] Description: Average RSSI of the channel specified in the carrierFrequencyKHz parameter over the measurement period. Value range: {0000 0000b - 1111 1111b} or {0 dBm to -127 dBm} in decimal system. Type: signed integer. Field length: 8 bits. occupancy ratio Description: Percent of the ON duration of the total measurement duration (e.g. 100 ms) Value range: {0000 0000b - 0110 0100b} or {0 - 100} in decimal system. Type: unsigned integer. Field length: 8 bits. Utilization level of the carrier frequency R o (f c ): Ro(fc)=TONTON+TOFF ack (acknowledgment) Description: Acknowledgment 18 for receipt of cell reconfig message 16. Value range: {0,1} Type: unsigned integer. Field length: 1 bit. Definitions / Assumptions:General assumptions
[0205] D ow : Maximum one-way fronthaul latency (e.g. up to 500 µs).
[0206] P CU : Maximum lls-CU processing time (reading a C-layer message from an upstream RU, MAC processing, sending the downstream U-layer data) (e.g.: up to 1 ms).
[0207] P RU : Maximum RU processing time (sending an upstream C-layer message, receiving downstream U-layer data, transmitting U-layer data OTA) (e.g.: up to 1 ms).
[0208] B RU : RU buffer depth (for LAA), limited to an integer number of OFDM symbols in µs (up to 140 symbols (e.g., MCOT)). This corresponds to the minimum amount of data that must be buffered at the RU. This parameter could be less than or equal to the actual RU buffer size sent in the LAA RU capability info.
[0209] Each RU must satisfy the following equation: BRU≥2×Dow+PCU+PRU
[0210] Expired Symbol: Symbol where the current time at the RU exceeds its target transmission time (i.e. SFN / SF) OTA.
[0211] Assumption of a normal (partially filled) SF: T start is the start of the transmission time, which occurs at the first SF (slot) boundary encountered by the RU after starting the LBT CAT 4 process. It is initially known to the CU 102 (since it sends the LBT start time) and can be updated in real time based on the LBT result and communication between the lls CU and the RU.
[0212] LBT_DL.indication Threshold (LBT_DL.indication-Threshold) (LBT th ): The latest time at which the lls-CU is expected to receive the LBT_DL.indication message from the RU. BRU≥2×Dow+PCU+PRU
[0213] CU 103 Transmission time threshold (CUT th): The time at which the lls-CU must send the data to the RU, the OTA at time T start should be transferred CUTth=Tstart−(PRU+Dow+PCU) x={1ms, Normal SF0.5ms, Partially filled SF Guidelines for LAA implementation in Cloud RAN:
[0214] The RU should have a buffer that satisfies the following equation: BRU≥2×Dow+PCU+PRU
[0215] The lls CU should avoid buffer overflow or underflow at the RU.
[0216] The lls-CU should only store data worth B for each individual transfer. RU send to the RU.
[0217] The lls-CU should only use P to receive the data at the RU RU before the actual OTA transmission time at the RU.
[0218] The RU should avoid buffer overflow or underflow at the RU.
[0219] The RU should flush its buffer (by dropping any expired symbols) as soon as any symbol has expired (i.e., the current time is greater than the symbol's scheduled time).
[0220] The RU should immediately send an LBT success message to the lls-CU once the channel has been acquired.
[0221] For LBT CAT 4, the ILS CU can configure the RU (via the M-layer) with the LBT CAT 4 duration threshold (e.g., 8 ms). After this threshold is exceeded, the RU sends an LBT failure message to the ILS CU, which in turn sends back a new LBT configuration request (config request). The RU can then restart the LBT CAT 4 process.
[0222] The data signal can be received at the RU before or after the LBT_PDSCH_REQ.
[0223] The lls-CU can send a new LBT configuration message for each LBT message, or it can receive multiple LBT messages (with failure results) and send a new LBT configuration message when it receives an LBT message with a success result. At this point, it resets the LBT phase and starts a new one with a new LBT configuration message. In general, the LBT message could be sent after each measurement period (e.g., every 9 microseconds), or it could be sent only for the success result (i.e., after acquiring the channel).
[0224] Fig. 13 is a flowchart illustrating a PDSCH transmission algorithm for a CU 102. After a start block 200, the CU 102 sends a B RU -Data volume to the RRU at CUT ththat is to be transmitted OTA. At block 202, for the target SFN / SF, the CU 102 sends an LBT_PDSCH_REQ request. At block 203, the CU 102 determines whether the LBT_PDSCH_RSP response from the RU is received at the CU. If the response indicates a successful result, the CU 102 determines at block 204 whether the LBT_PDSCH_RSP response is successful. If not (e.g., LBT timer expired), the LBT process is reset at block 205, and at block 210, the CU 102 terminates the transmission. If the LBT_PDSCH_RSP response from the RU is successful (Success) at block 204, the CU 102 increments T at block 206. start by the buffer depth T start = T start + B RU . At block 207, the CU 102 also determines whether the remaining data is less than the buffer depth of the RU B RU If this is the case, the CU 102 sends the remaining data to the RU at CUT at block 209 th. If the remaining data is not less than the buffer depth of RU B RU , the CU 102 sends only data worth B at block 208 RU to the RU.
[0225] If the CU 102 determines at block 203 that the LBT_PDSCH_RSP response was not received from the RU, the CU 102 determines at block 211 whether the current time is the latest time the lls-CU is expected to receive the LBT_DL.indication message from the RU, T NOW = LBT TH If this is the case, the lls-CU 102 updates the time at which data should be transmitted OTA, T start = T start + [B RU], and returns to block 203 to wait for the LBT_PDSCH_RSP response and continue the process from there ([a]: is the limit of the number "a" to the next x, where x is 1 ms for a normal SF and 0.5 ms for a partially filled SF). If this is not the case, the CU 102 determines at block 213 whether the current time is equal to the transmission time threshold CUT th the CU is 102. If so, the CU sends data worth B at block 214 RU If not, the CU 102 then returns to block 203 to determine whether the LBT_PDSCH_RSP response was received and continues the process from there.
[0226] The Fig.14A-14B are a flowchart for a PDSCH transmission algorithm for an RU. After a start block 300, the RU determines at block 301 whether data is being received. If not, the RU continues to check to determine whether data is being received. If the RU determines that data is being received, the RU determines at block 302 whether the amount of data c is greater than buffer B. RU of the RU. If so, the RU sends an error message to the CU at block 303. If the data volume does not exceed the RU's buffer, the RU buffers the data at block 304.
[0227] At block 305, the RU determines whether it has received an LBT_PDSCH_REQ request from the CU. If it confirms at block 306 that the request has been received, the RU starts an LBT CAT 4 spectrum acquisition. At block 307, the RU determines whether the LBT CAT 4 timer has expired. If so, at block 308, the RU sends a failure message to the CU (LBT_PDSCH_RSP: failure outcome) and terminates the process at block 319. If at block 307, the LBT CAT timer has not expired, at block 309, the RU determines whether the current time is the start time and whether the channel is not acquired. If so, at block 310, the RU increments the T start at x, T start = T start+ x and returns to block 306 to continue the LBT CAT 4 spectrum acquisition. If not, the RU determines at block 311 whether a channel is acquired at Tacq. If the channel is not acquired, the RU discards all expired symbols from the buffer and buffers any new received data at block 312. The RU then returns to block 306 to continue the LBT CAT 4 spectrum acquisition.
[0228] If the channel is acquired at block 311, the RU sends a success message to the CU at block 313 (LBT_PDCH_RSP: success outcome). At block 314, the RU sends a reservation signal OTA to the T START At block 315, the RU sends the buffered data OTA. At block 316, the RU updates T start as T start = T start + B RU . At block 317, the RU also determines whether the received data is less than the buffer depth of RU B RUIf this is the case, the RU continues to send the buffered data OTA at block 318. The process ends at block 319. If the remaining data is not less than the buffer depth of the RU B RU , the RU returns to block 315 to send buffered data OTA and performs the data reception check again at block 317.
[0229] Fig. 15 is a shading code for a RU spectrum acquisition (dots) reservation signal (diagonal lines) and sending data OTA (horizontal lines) used in the Fig. 15-19, 22 and 24 is used.
[0230] The Fig. 15-18 are an embodiment and examples dealing with fronthaul normal SF support as described above in the Fig. 13-15B. Assumptions for the following examples are: 2 × D ow : 5 symbols duration P CU : 1 symbol duration (divided between UL and DL processing) PRU : 1 symbol duration (divided between UL and DL processing) B RU : Data worth 1 slot Normal CP
[0231] As you can see, the parameters do not have to be an integer number of OFDM symbols. This is assumed only for simplicity. Embodiment 1Example 1:
[0232] Fig. 15 is an embodiment in which the LBT is less than one subframe. Example 2
[0233] Fig. 16 is an embodiment in which the LBT is more than one subframe. Example 3
[0234] Fig. 17 is an embodiment in which the LBT is less than one slot. Example 4
[0235] Fig. 18 is an embodiment in which the LBT is more than one slot. Embodiment 2
[0236] Fig.19 is another embodiment and examples of PDSCH transmission (with the options of normal and partially filled SFs) support as described above in the Fig. 13-14B. The assumptions for the following examples are as follows: Restriction: B¯RU≥Dow+PCU+PRU
[0237] CU Transmission time threshold (CUT th ): The time at which the lls-CU must send the data to the RU that is at time T start OTA should be transmitted CUTth=Tstart−(PRU+Dow+PCU)
[0238] A variant of the first embodiment is that the lls-CU continuously transmits the data to the RU in data blocks of B RU starting at the time CUT th and with period B RU stream until it receives the LBT_PDSCH_RSP with a success result.
[0239] At this point, the lls-CU calculates the number of remaining symbols to be transmitted until the end of the MCOT.
[0240] The lls-CU continues streaming the B RU Data blocks with period B RU until the end of the MCOT.
[0241] The RU follows the same algorithm as in embodiment 1. The B RU must, however, be replaced by B RU be replaced.
[0242] An exemplary advantage of Embodiment 2 is that it has a smaller RU buffer constraint than Embodiment 1. Example 4
[0243] Fig. 19 shows an embodiment in which the LBT is longer than one subframe. DRS transmission
[0244] Regarding DRS transmission, it should be noted that: • PSS / SSS that are part of a DRS can occur outside subframes 0 and 5. • CRS / CSI-RS / PSS / SSS do not vary with the subframe number, but are left unchanged across subframes 0-4 (referred to as DRS_v1) and 5-9 (DRS_v2). • The DRS transmission (from the CU to the RU) can be executed once at the beginning (e.g. during initial configuration or at the first DRS transmission time) and can optionally be sent in each DRS period (from the CU to the RU).
[0245] Assumption: The OTA transmission of the DRS starts at the SF boundaries. It should be understood that the proposed method can be adapted and applied to allow the DRS transmission start time at any OFDM symbol. The same concept can be used for both cases.
[0246] The DRS signal can be received before or after the LBT_DRS_REQ. DRSth,1=SF0−(PRU+Dow+PCU) DRSth,2=SF5−(PRU+Dow+PCU) SF0: The launch of SF 0 SF5: The launch of SF 5
[0247] At DRS th,1 the lls-CU sends DRS_v1 (ie which is to be transmitted within the SFs 0-4).
[0248] At DRS th,2 the lls-CU sends DRS_v2 (ie which is to be transmitted within the SFs 5-9).
[0249] Optional: The lls-CU can send a new LBT_DRS_REQ (with the new acquisition parameters) for each failure result it receives.
[0250] Optional: The RU can generate the reference signals (e.g. DRS) locally and keep them in its buffer.
[0251] Optional: The ILS CU can send the reference signals to the RU once during initial configuration. The RU can store them in buffers and use them accordingly.
[0252] An LBT message with a failure result could be sent for each measurement period. DRS transmission algorithm
[0253] Fig.Figure 20 is a flowchart illustrating a DRS transmission algorithm for a CU. After a start block 400, the CU sends a corresponding DRS at block 401. th,1 or DRS th,2 At block 402, at the target SFN / SF for the measurement, the CU sends an LBT_DRS_REQ request. At block 403, the CU determines whether the DMTC offset time has expired (this can happen automatically at the RU and the ILS CU, or the ILS CU can send a notification message to the RU to stop the DRS transmission process). If this is the case, the CU terminates the process at block 408. If not, the system determines at block 404 whether the current time DRS th,1 or DRS th,2 is (T now = DRS th,1 or T now = DRS th,2If yes, the CU sends the corresponding DRS at block 405. If not, the CU determines whether the RU has received the LBT_DRS_RSP response at block 406. If not, the CU returns to block 403 to determine whether the DMTC offset time has expired and continues with the process. If the RU has received the request, the CU determines whether the result is successful at block 407 and terminates the process at block 408 if so. If not, the CU returns to block 403 to determine whether the DMTC offset time has expired to continue the process.
[0254] As will be seen, the DRS transmission algorithm for the lls-CU is the same as for an RU configured for and performing a 25 µs acquisition, as described below with respect to Fig. 21, or for an RU configured for and performing LBT CAT 4 acquisition as described below with respect to Fig. 22 is shown.
[0255] Fig. Figure 21 is a flowchart for one embodiment of a DRS transmission algorithm for an RU performing a 25 µs acquisition. After a start block 500, the RU determines whether a DRS is received at block 501, and if so, buffers the DRS at block 502. If the DRS is not received, the RU continues listening for the DRS.
[0256] After the DRS is buffered, the RU determines at block 503 whether it has received an LBT_DRS_REQ request from the CU. If so, the RU determines at block 504 whether the DMTC offset time has expired. If so, the RU terminates the process at block 512. If not, the RU determines at block 505 whether a new DRS has been received. If not, the RU starts the LBT spectrum acquisition (25 µs) at a configured time at block 507. If a new DRS has been received, the RU discards existing DRS buffered at block 502 at block 506 and buffers the new DRS. Then, at block 507, the RU starts the LBT spectrum acquisition (25 µs) at the configured time.
[0257] At block 508, the RU determines whether the LBT spectrum acquisition was successful. If not, at block 509, the RU sends a failure outcome (LBT_DRS_RSP), and the RU returns to block 504 to determine whether the DMTC offset time has expired and continues the process. If so, at block 510, the RU sends a success outcome (LBT_DRS_RSP), and at block 511, the RU sends the DRS OTA to the target device(s). Block 512 terminates the process. Example 5:
[0258] Fig. Figure 22 is an example of DRS - 25 µs LBT, as shown in the flowcharts of the Fig. 20-21 is shown.
[0259] Fig.Figure 23 is a flowchart illustrating a DRS transmission algorithm for an RU. After a start block 600, the RU determines at block 601 whether a DRS is received, and if so, buffers the DRS at block 602. If the DRS is not received, the RU continues listening for the DRS. If not, the RU determines at block 603 whether an LBT_DRS_REQ request has been received. If not, the RU continues listening and determines if the request has been received. If so, the RU determines at block 605 whether the DMTC offset time has elapsed. If so, the RU terminates the process at block 614. If not, the RU determines at block 605 whether a new DRS has been received. If not, the RU starts the LBT CAT acquisition at a configured time at block 607. When a new DRS has been received, at block 606 the RU removes existing DRS buffered in block 502 and buffers the new DRS.Then, at block 607, the RU starts the LBT CAT acquisition at the configured time.
[0260] At block 608, the RU determines whether the LBT CAT4 timer has expired. If so, the RU sends a failure outcome message (LBT_DRS_RSP) at block 609 and terminates the process at block 614. If not, the RU determines whether a channel has been acquired at block 610. If not, the RU returns to block 604 to determine whether the DMTC offset time has elapsed and continues the process from there.
[0261] If a channel is acquired at block 610, the RU sends a success outcome (LBT_DRS_RSP) at block 611, and at block 612, the RU sends the reservation signal (OTA) to the target device up to the SF boundary. At block 613, at the SF boundary, the RU sends the DRS (OTA). Block 614 terminates the process. Example 6:
[0262] Fig.24 is an example of DRS - LBT CAT 4 according to the procedure of Fig. 20 and Fig. 23.
[0263] Multi-cell LAA: Assigning LAA- and non-LAA-capable UEs to a Cloud RAN solution that supports carrier aggregation between multiple licensed and unlicensed component carriers (CCs).
[0264] Fig. 25 is an embodiment for assigning LAA and non-LAA capable UEs to licensed and unlicensed component carriers (CCs).
[0265] Tables 5-7 show a summary of UNII bands: Table 5 E-UTRA operation UNII band UL / DL frequency range (GHz) Number of 20 MHz channels DFS / TPC band 46a UNII-1 5,15 - 5,25 4 not required 46b UNII-2A 5,25 - 5,35 4 required for radar 46c UNII-2C 5,47 - 5,725 12 required for radar 46d UNII-3 5,725 - 5,85 5 not required UNII-4 5,85 - 5,925 N / A (mainly used for DSRC / ITS) not required Table 6 UNII-1 channel number Carrier frequency (MHz) 36 5180 40 5200 44 5220 48 5240 Table 7 UNII-3 channel number Carrier frequency (MHz) 149 5745 153 5765 157 5785 161 5805 165 5825
[0266] 3GPP TS 36.300 V15.1.0 (2018-04-03) describes a specification limitation when aggregating multiple LAA cells: "If the absence of IEEE802.11n / 11ac carrier-sharing devices cannot be guaranteed in the long term (e.g., due to the level of regulation), and if, for this version, the maximum number of unlicensed channels on which E-UTRAN can transmit simultaneously is equal to or less than 4, the maximum frequency spacing between any two carrier center frequencies on which LAA-SCell transmissions are performed should be less than or equal to 62 MHz. The UE must support the frequency spacing according to TS 36.133
[21] ."
[0267] For illustrative purposes, some assumptions are made in the following description regarding the number of LAA cells, supported bands, and the like. Those of ordinary skill in the art will appreciate that the following methods can be generalized in such a way that these assumptions are not required. However, these assumptions are made for illustrative purposes (and to provide examples) only and not to limit the described exemplary methods.
[0268] Band combinations for 3 and 4 LAA cells are shown below (as an example). For simplicity and illustration, only bands that do not require radar coexistence (i.e., UNII-1 and UNII-3) are described and shown below in Table 8. Table 8 3 unlicensed LAA cells 4 unlicensed LAA cells 3 UNII-1 4 UNII-1 2 UNII-1 + 1 UNII-2A 3 UNII-1 + 1 UNII-2A 1 UNII-1 + 2 UNII-2A 2 UNII-1 + 2 UNII-2A 3 UNII-2A 1 UNII-1 + 3 UNII-2A 3 UNII-2C 4 UNII-2A 2 UNII-2C + 1 UNII-3 4 UNII-2C 1 UNII-2C + 2 UNII-3 3 UNII-2C + 1 UNII-3 3 UNII-3 2 UNII-2C + 2 UNII-3 1 UNII-2C + 3 UNII-3 4 UNII-3
[0269] The following algorithm assumes that the CA combination between licensed and unlicensed bands is supported by the UE based on 3GPP TS 36.104 V15.2.0 (2018-04-06). The ILS CU can filter the bands supported by the RU to the CA combinations supported by 3GPP.
[0270] Algorithm 1: 11s CU / RU handshake algorithm for initial channel selection (M-layer).
[0271] During initial configuration, the RU informs the ILS CU about its capabilities. This includes whether or not it supports LAA, the maximum number of LAA CCs it can support, the RU buffer size per CC, the supported bands on the RU (e.g., 46a, 46d), supported bandwidths, and the like.
[0272] Based on the supported bands, the lls-CU commands the RU to start measurements for these bands (e.g., to scan band 46a (UNII-1) and band 46d (UNII-3 band only)).
[0273] In the “startMeasurements” message, the lls-CU informs the RU about the band numbers, the carrier frequency of the channels and the total measurement duration.
[0274] The RU calculates the average RSSI and utilization level for each channel and sends the measurements back to the lls-CU.
[0275] The lls-CU lists all "valid" available combinations of unlicensed bands based on the RU capabilities (e.g., the lls-CU can select either the UNII-1 or the UNII-3 band to operate on if only these two bands are supported, i.e., 3 or 4 CCs in UNII-1 or 3 or 4 CCs in UNII-3). As an example (nk)=n!(n−k)+!k! for n = 4 channels (UNII-1 band only) and k=3 CCs→(43)=4 Combination. The RU may ONLY select valid combinations.
[0276] As another example for n=5 channels and k=3 CC there are 10 Combinations. 3 of these are invalid: 149 / 153 / 157 149 / 153 / 161 149 / 153 / 165 ** invalid 149 / 157 / 161 149 / 157 / 165 ** invalid 149 / 161 / 165 ** invalid 153 / 157 / 161 153 / 157 / 165 153 / 161 / 165 157 / 161 / 165
[0277] Based on the received measurements, the ILS-CU calculates the average RSSI and utilization levels for various band combinations, as shown below. As an example, for 4 CCs, the ILS-CU averages the measurements (RSSI and utilization levels) for the 4 channels in a single combination. Table 9 Band combination index Example for 4 CCs (if only UNII-1 and 3 are supported) average RSSI over 4 CCs Capacity utilization over 4 CCs Capacity utilization ranking (1: best) exceeded capacity utilization threshold selected combination 1 36 / 40 / 44 / 48 2 Yes 2 149 / 153 / 157 / 161 1 Yes selected 3 153 / 157 / 161 / 165 3 Table 10 Band combination index Example for 3 CCs (if only UNII-1 and 3 are supported) average RSSI over 3 CCs Capacity utilization over 3 CCs Capacity utilization ranking (1: best) exceeded capacity utilization threshold selected combination 1 36 / 40 / 44 5 Yes 2 36 / 40 / 48 3 Yes selected 3 36 / 44 / 48 4 Yes 4 40 / 44 / 48 6 5 149 / 153 / 157 11 6 149 / 153 / 161 1 Yes 7 149 / 157 / 161 10 8 153 / 157 / 161 7 9 153 / 157 / 165 9 10 153 / 161 / 165 2 Yes 11 157 / 161 / 165 8
[0278] The lls-CU ranks the band combinations based on their utilization levels.
[0279] The lls-CU filters the combinations based on a utilization threshold (i.e., generating a set of combinations with utilization levels below a previously defined threshold, for example, 20%).
[0280] The lls-CU selects the band combination with the minimum RSSI from the filtered set (i.e., combinations with a utilization level below the utilization level threshold). Algorithm 2: DFS algorithm for MultiCell (M-layer)
[0281] The RU periodically collects measurements regarding the supported unlicensed bands and sends these measurements to the lls-CU based on the configuration parameters in the initial handshake (e.g., DFS measurement reporting period).
[0282] These measurements can be triggered by a "startMeasurements" message (which includes the bands to be scanned, the carrier frequencies of the channels and the measurement reporting period) and stopped by a "stopMeasurements" message.
[0283] For each measurement report, the lls-CU repeats Algorithm 1 by calculating the average parameters across the channels of a single band combination, ranking them based on the utilization levels, filtering the set based on the previously defined threshold, and selecting the best combination based on the minimum average RSSI.
[0284] In an example implementation of the algorithm, the DFS measurement reporting period can be adjusted by the ILS CU based on how quickly frequency hopping is permitted. For example, the ILS CU can only allow DFS 1-4 times per day to minimize service disruption.
[0285] In another exemplary implementation of the algorithm, the lls-CU can switch band combinations only if the difference between the average RSSI of the currently used combination and the minimum average RSSI (after the DFS measurement) is larger than a previously defined threshold.
[0286] In another exemplary implementation of the algorithm, the lls-CU can switch band combinations only if the difference between the utilization level of the currently used combination and the minimum utilization level (according to the DFS measurement) is greater than a previously defined threshold.
[0287] In another exemplary implementation of the algorithm, the lls-CU can switch band combinations only if the difference between the average RSSI of the currently used combination and the minimum average RSSI (according to the DFS measurement) is greater than a previously defined threshold or if the difference between the utilization level of the currently used combination and the minimum utilization level (according to the DFS measurement) is greater than a previously defined threshold. Algorithm 3: Allocation of UEs to licensed / unlicensed cells. Part 1: Initial allocation:
[0288] Classify UEs into two groups: LAA-capable UEs and non-LAA-capable UEs. Assigning non-LAA-capable UEs to licensed CCs.
[0289] Assigning LAA-capable UEs to licensed CCs until the load of the licensed cells reaches a maximum threshold (Licensed CC usage threshold: LCU th ) (e.g. LCU th = 70%).
[0290] If LAA-capable UEs are still unassigned while the maximum threshold of all licensed CCs is reached, assign LAA-capable UEs to unlicensed CCs (based on Algorithm 3.1 described below). Part 2: Real-time operation and optimization:
[0291] For each new UE, if the UE is not LAA-capable, assign it to a licensed CC (this may lead to an increase in the utilization of licensed CCs, but this can be resolved with periodic redistribution of LAA-capable UEs). If the UE is LAA-capable, assign it to an unlicensed CC (based on Algorithm 3.1).
[0292] For each period T alloc (e.g. T alloc= 60 min), the lls-CU distributes all LAA-capable UEs to licensed and unlicensed channels with the following objectives: Reducing the use of licensed CCs at the LCU th .
[0293] Optimal allocation of LAA-capable UEs to unlicensed CCs based on the reported CQI of the respective UE. Balancing the load on all CCs.
[0294] The periodic redistribution of LAA-capable UEs is similar to the initial allocation.
[0295] Assign LAA-capable UEs to licensed CCs until the load of the licensed cells reaches a maximum threshold (threshold of utilization by licensed CCs): LCU th ) reached (e.g. LCU th = 70% usage).
[0296] If LAA-capable UEs are still unassigned while the maximum threshold of all licensed CCs is reached, assign LAA-capable UEs to unlicensed CCs (based on Algorithm 3.1).
[0297] T alloc should be based on the deviation from LCU th be adjusted. With increasing use of the licensed CCs, T alloc to avoid blocking non-LAA-capable UEs from licensed CCs.
[0298] Algorithm 3.1: Assignment of LAA-capable UEs to unlicensed CCs after reaching LCU th for the licensed CCs.
[0299] If the number of unlicensed CCs is one, assign all LAA-capable UEs to the unlicensed CC.
[0300] If the number of unlicensed CCs is ≥ 1:
[0301] Forming a matrix for the utility function of LAA-capable UEs for different unlicensed CCs. There are four parameters that influence UE assignment to unlicensed CCs (i.e., the utility function): • Cell load • UE Channel Gain (or CQI) • DFS measurements: Capacity utilization • DFS measurements: average RSSI
[0302] The simplified utility function for a user (i) who uses CC (j) works can be represented as follows: Uij=(1−Rof)∗PSj∗B∗log(1+PTj∗|hij|2NoB+Ij)
[0303] This includes: - R oj the last reported load factor (obtained from the carrier selection / DFS measurements) for the unlicensed CC j. This takes channel congestion into account. - P sj the probability of the user's termination via channel (j). This takes into account the cell load. P sj = 1 / N Uj , where N Uj is the current number of UEs being added to CC j. - B: Channel bandwidth. - P Ti the transmission power of the RU via CC j. - h ij the channel gain of the UE (i) over CC j assuming that the reciprocal CSI at the RU is known. - N o the noise power spectral density at the UE (which is assumed to be constant across all UEs when no information is available). - I j The approximate external interference at the UE (e.g., from neighboring Wi-Fi access points and the like). This can be derived from the last RSSI value reported by the RU during channel measurement (i.e., for carrier selection / DFS). This is based on the assumption that the external interference per CC is uniform between the RU and UEs.
[0304] It will be clear to one of ordinary skill in the art that other utility functions that represent the above-mentioned parameters (or any other parameters that affect the performance of the UEs) can also be used to model the allocation problem. Table 11 CC1 CC2 ... CCu U1 U 11 U 12 U 1u U2 U21 U 22 U 2u ... ... To U m1 U m2 U mu Solution 1: Iterative Hungarian method:
[0305] An example solution is to use a modified version of the Hungarian method. The Hungarian method can be used to solve assignment problems in polynomial time 0(n 3 ) to solve.
[0306] Goal: to maximize the sum of the utility functions while maintaining the same load balance on all unlicensed CCs.
[0307] Step X: Create a submatrix from the original matrix with a number of UEs equal to the number of unlicensed CCs. This is the cost matrix (with negative benefits).
[0308] Solve the assignment problem using the regular Hungarian method (now each UE of the sub-matrix is assigned to a single unlicensed CC and each unlicensed CC receives a single UE from the sub-matrix).
[0309] Remove the rows from the original matrix that correspond to the UEs already assigned to unlicensed CCs. Name this new matrix the original matrix. Continue with step X.Solution 2:
[0310] Another exemplary solution that should lead to higher overall benefits but will not maintain a comparable burden balance between unlicensed CCs is as follows: Step Y: Iterate over the UEs in the original matrix.
[0311] Selecting the unlicensed CC that yields the maximum utility function for each UE.
[0312] Check whether the selected CC has reached its maximum allowable load (can be defined as a function of the number of UEs previously).
[0313] If so, remove the CC column from the original matrix. Name this new matrix the original matrix. Continue with step Y. If no, continue with step Y. Adjusting the fronthaul transmission rate
[0314] In C-RANs, the BBU 103 pre-transmits data packets to the RRU 105 to compensate for fronthaul latency. This fronthaul latency is a function of several factors, including the physical distance between the BBU 103 and the RRU 105, the transport network, network congestion, and the like.
[0315] One challenge faced by C-RANs (both for licensed and unlicensed spectrum) is determining the number of data packets that need to be transmitted from the BBU 103 to the RRU 105 to avoid buffer overflow and buffer underflow at the RRU. Typically, a single BBU 103 can support multiple RRUs.
[0316] Fig. 26 is an embodiment of a configuration and method for adjusting the fronthaul rate, which is described as follows. 1) After the RRU 105 boots up, the BBU 103 sends several pilot messages to the RRU 105, each containing a timestamp for the transmission time (at the BBU 103). 2) The RRU 105 responds with a response message to each pilot message, and each response includes the time at which the RRU 105 can receive the pilot message. 3) Based on the buffer size at the RRU 105 and the fronthaul latency, the BBU 103 adjusts the transmission rate to the RRU 105 (this is different from the OTA transmission rate).
[0317] The first pilot / response messages exchanged between the BBU 103 and the RRU 105 capture the latency due to the physical distance between the BBU 103 and the RRU 105, the transport network latency, and other fixed parameters that introduce a fixed latency. 4) To cover other dynamic changes in fronthaul latency, the RRU 105 periodically sends the buffer status to the BBU 103. 5) The BBU 103 and the RRU 105 periodically exchange the pilot / response messages to refine the estimated fronthaul latency. 6) The BBU 103 adjusts the fronthaul transmission rate based on the fronthaul latency and the buffer size of the RRU 105. 7) If the fronthaul latency increases, the BBU 103 can increase the fronthaul transmission rate for a short period to compensate for this delay and then return it to normal. The same applies in reverse. The same applies to the buffer size of the RRU 105. 8) For LAA, a similar concept (used for varying fronthaul latency) can be applied for varying LBT delay. a. The LBT delay is defined as the amount of time required by the RRU 105 to acquire the spectrum for transmitting specific data packets. b. The LBT delay may vary based on various metrics such as network density, traffic priority class, traffic magnitude, and the like. c. Varying LBT latency plays a crucial role in determining the buffer size of the RRU 105. d. The BBU 103 adjusts the fronthaul transmission rate based on the LBT latency in a similar manner to the fronthaul latency.
[0318] Systems and components thereof for carrying out embodiments of the present disclosure may include a central processing unit (CPU) or any other processor. The input unit may include a receiver, a transceiver, or any other means for receiving. The output unit may include a transmitter, a transceiver, or any other means for transmitting. The input unit and the output unit of the device may be functionalities that run on the processor of the device, or alternatively, may be separate functional components. They may also be implemented as integrated transceivers. The input unit and the output unit may, for example,They can be implemented as physical transmitters / transceivers for sending / receiving data over an interface, as routing units for sending / receiving data packets in a PS (packet-switched) network, or as any suitable combination thereof. Systems and components thereof can also exchange information via internal interfaces.
[0319] Each component can be configured to process various data inputs and control the input unit and the output unit. Each component can further include a memory. The memory can be used to store code for executing the methods according to the examples of the present embodiments.
[0320] One of ordinary skill in the art will recognize that the architecture of the systems described herein are non-limiting examples illustrating at least a portion of at least one embodiment. As such, more or fewer components may be employed and / or arranged differently without departing from the scope of the innovations described herein.
[0321] The Third Generation Partnership Project (3GPP) technology standards and reports referred to herein, each of which is incorporated by reference in its entirety, include: 3GPP TR 38.801 V14.0.0 (2017-03) 3GPP TR 36.889 V13.0.0 (2015-06) 3GPP TS 36.211 V14.3.0 (2017-06) 3GPP TS 36.300 V15.1.0 (2018-04-03) XRAN-FH.CUS.0-v01.00.02 (2018-04-04) 3GPP TS 36.213 V15.1.0 (2018-03)
Claims
[1] Method comprising: Transmitting from a lower layer of a baseband unit (BBU) to a layer of a remote radio unit (RRU) via a fronthaul interface a data transmission on a destination subframe agreed between the BBU and the RRU, wherein the data is sent a number of milliseconds before the RRU performs an LBT (Listen Before Talk) step for the data, wherein a control unit (CU) of the BBU is configured to set a timer based on an end-to-end latency requirement of the data traffic and is configured to attempt transmission in an unlicensed band. [2] The method of claim 1, wherein the CU is further configured to: Transfer, from the CU, an amount of data corresponding to the RRU buffer depth (B RU) at a CU transmission time threshold at which the CU must transmit the data to the RRU so that it can be received at T start transmitted over the air (OTA) (CUT th ); Transmit, for the destination subframe, an LBT Physical Downlink Shared Channel (PDSCH) request to the RRU; Determine whether an LBT-PDSCH response is received from the RRU at the CU; Determine whether the LBT-PDSCH response is successful; and If the LBT PDSCH response is successful, incrementing a CU transmission start time (T start ) to set a buffer depth of the RRU (T start. = T start + B RU ), or Reset the LBT step if the received LBT-PDSCH response is unsuccessful. [3] The method of claim 2, wherein the CU is further configured to: Incrementing the CU transmission start time (T start ) to the buffer depth of the RRU (T start. = T start+ B RU ) if the LBT-PDSCH response from the RRU is determined to be successful; Determine whether the remaining data is less than the RRU buffer depth (B RU ); and if this is the case, transfer the remaining data to the RRU at the CU transmission time threshold CUT th , or if not, transfer only data set B RU to the RRU. [4] The method of claim 3, wherein, if the CU determines that the LBT-PDSCH response from the RRU is not received at the CU, the CU is further configured to: Determine whether a current time is a latest time at which the CU is expected to receive the LBT-PDSCH response from the RRU (T NOW = LBT TH ); if yes, update the time at which the data should be transferred OTA (OTA Tstart.=Tstart+⌈BRU⌉); and Continue to determine if the LBT-PDSCH response from the RRU is not received at the CU. [5] The method of claim 3, wherein if the CU determines that the current time is not the latest time at which the CU is expected to receive the LBT-PDSCH response from the RRU (T NOW = LBT TH ), the CU is further configured to: Determine whether the current time is equal to the CU transmission time threshold CUT th is, and: if so, transferring data worth B RU ; or if not, return to determine whether the LBT-PDSCH response was received. [6] The method of claim 1, wherein the RRU is configured to: Determine whether an LBT Physical Downlink Shared Channel (PDSCH) request is being transmitted by the CU; Starting an LBT spectrum acquisition when the LBT PDSCH request is received from the CU; Determine whether an LBT spectrum acquisition timer has expired; and if the LBT timer has expired, send a failure message to the CU and terminate the LBT process; or if the LBT timer has not expired, determine that a current time has a start time (T start ) and whether no channel has been acquired, and if no channel has been acquired, increment the T start by x(T start = T start + x) and continue LBT spectrum acquisition. [7] The method of claim 6, wherein the RRU is further configured to: Determine whether a channel has been acquired at time Tacq, and if no channel has been acquired, discarding all expired symbols from a buffer of the RRU and buffering all newly received data and Proceed with LBT spectrum acquisition. [8] The method of claim 7, wherein the RRU is further configured to: if the channel has been acquired, sending an LBT-PDSCH success message to the CU; Sending a reservation signal OTA to T start ; Sending the buffered data OTA and updating T start as T start = T start + B RU ; Determine whether the buffered data is less than the buffer depth of RRU B RU , and if so, continue sending the buffered data OTA, and if the remaining buffered data is not less than the buffer depth of RRU B RU , sending the remaining buffered data OTA and performing a data reception check. [9] System comprising: a baseband unit (BBU) comprising a control unit (CU) configured to send a pilot message to a remote radio unit (RRU) prior to a data link time to compensate for fronthaul latency; and wherein the RRU is configured to respond to the BBU with messages specifying a time at which the RRU can receive the pilot message, and wherein the CU is configured to adapt a transmission rate to the RRU based on the buffer size at the RRU and the fronthaul latency. [10] Method comprising: Transmitting, from a lower layer of a baseband unit (BBU) to a layer of a remote radio unit (RRU) via a fronthaul interface, a Discovery Reference Signal (DRS) transmission, wherein a control unit (CU) of the BBU is configured to: Sending the DRS signal at a time DRSth,1 or a point in time DRS th,2 ; Sending an LBT-DRS request to a target subframe for a Listen Before Talk (LBT) acquisition; and Determine whether a Discovery Measurement Timing Configuration (DMTC) offset time has passed; and if so, send the DRS transmission. [11] The method of claim 10, wherein the CU is further configured to: If the CU determines whether the Discovery Measurement Timing Configuration (DMTC) offset time has not passed, determine whether a current time DRS th,1 or DRS th,2 . is (T now = DRS th,1 or T now = DRS th,2 ?); and if so, send the DRS. [12] The method of claim 11, wherein the CU is further configured to: if the CU determines that a current time is not the DRS time th,1 or the time DRS th,2 is (T now = DRS th,1 or Tnow = DRS th,2 ?), Determine whether the RRU has received an LBT-DRS request, and if not, determine whether the DMTC offset time has expired and continue with the DRS transmission; If the CU determines that the RRU has received the LBT DRS request, determine whether the result is successful and, if so, terminate the DRS transmission; If the CU determines that the LBD DRS request was unsuccessful, determine whether the DMTC offset time has expired and continue with the DRS transmission process. [13] The method of claim 10, wherein the RRU is configured to: Determine whether the DRS is received and, if so, buffer the DRS; if the DRS is not received, continue listening for the DRS; if the DRS is buffered, determine whether the RRU has received an LBT DRS request from the CU; and If yes, determine whether the discovery measurement time window (DMTC) offset time has expired, and if yes, terminate the process. [14] The method of claim 13, wherein the RRU is configured to: if the DMTC offset time has not elapsed, determine whether no new DRS has been received; if not, start an LBT spectrum acquisition at a configured time; when a new DRS has been received, dropping the existing buffered DRS and buffering a new DRS; and Start LBT spectrum acquisition at a configured time. [15] The method of claim 14, wherein the RRU is configured to: Determine whether the LBT spectrum acquisition is successful; if not, send an LBT-DRS failure response to the CU; Determine whether the DMTC offset time has passed; if yes, send an LBT-DRS success response to the CU and Sending the DRS over an air interface to the target device.
Citation Information
Patent Citations
Method and apparatus for LTE operation in unlicensed and shared spectrum for cloud radio access networks
US62628538P0
Method and apparatus for LTE operation in unlicensed and shared spectrum for cloud radio access networks
US62659546P0
Method and Apparatus for licensed-assisted access (LAA) for CLOUD RAN and for multi-LAA cells
US62668012P0
Resource Allocation in a Wireless Device
US20170318594A1
Terminal device and method
WO2017135077A1
