WO2021109115A1 - Configuration de période de trame fixe pour bande passante d'écoute avant transmission - Google Patents

Configuration de période de trame fixe pour bande passante d'écoute avant transmission Download PDF

Info

Publication number
WO2021109115A1
WO2021109115A1 PCT/CN2019/123614 CN2019123614W WO2021109115A1 WO 2021109115 A1 WO2021109115 A1 WO 2021109115A1 CN 2019123614 W CN2019123614 W CN 2019123614W WO 2021109115 A1 WO2021109115 A1 WO 2021109115A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidths
listen
talk
frame
base station
Prior art date
Application number
PCT/CN2019/123614
Other languages
English (en)
Inventor
Changlong Xu
Jing Sun
Xiaoxia Zhang
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2019/123614 priority Critical patent/WO2021109115A1/fr
Publication of WO2021109115A1 publication Critical patent/WO2021109115A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/0006—Assessment of spectral gaps suitable for allocating digitally modulated signals, e.g. for carrier allocation in cognitive radio
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA

Definitions

  • the following relates generally to wireless communications and more specifically to a fixed frame period (FFP) configuration for listen-before-talk (LBT) bandwidths.
  • FFP fixed frame period
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • a UE and a base station may communicate on resources of an unlicensed band (e.g., NR unlicensed (NR-U) frequency bands) .
  • the resources of the unlicensed band may be shared amongst multiple UEs (e.g., and multiple base stations) , such that a UE may contend for one or more of these shared resources to communicate with the base station (e.g., performing contention-based procedures, such as a contention based random access procedure) .
  • Efficient techniques are desired for enabling communications between the UE and the base station on the resources of the unlicensed band.
  • the present disclosure relates to methods, systems, devices, and apparatuses that support a fixed frame period (FFP) configuration for listen-before-talk (LBT) bandwidths.
  • FFP fixed frame period
  • LBT listen-before-talk
  • the described techniques provide for a user equipment (UE) and a base station to identify a bandwidth part (BWP) for communications between the UE and the base station and to identify multiple LBT bandwidths in the BWP (e.g., based on the BWP being above a threshold size, such as 20 megahertz (MHz) ) .
  • the UE and the base station may determine respective frame configurations (e.g.
  • each of the frame configurations may indicate same or different frame periods (e.g., FFPs) , same or different frame offsets (e.g., from a start of a frame for the BWP) , or both for each of the multiple LBT bandwidths.
  • the base station may determine and configure the frame configurations and then transmit an indication of the frame configurations to the UE (e.g., via radio resource control (RRC) signaling) .
  • RRC radio resource control
  • the UE and the base station may determine control resource set (CORESET) configurations for each of the multiple LBT bandwidths, where the CORESET configurations include a period and offset for corresponding CORESETs in COTs of each of the multiple LBT bandwidths.
  • CORESET control resource set
  • each of the CORESETs may be aligned in time or may have different offsets with respect to each of the other CORESETs.
  • the base station may transmit an indication of the CORESET configurations to the UE (e.g., via RRC signaling) .
  • guard bands may exist between two adjacent LBT bandwidths of the multiple LBT bandwidths.
  • the base station may transmit an indication of the guard band or an absence of the guard band to the UE.
  • the UE may identify whether a guard band is present or not based on detecting a signal on each of two adjacent LBT bandwidths, where if a signal is detected on both adjacent LBT bandwidths, the UE may determine a guard band is absent (e.g., any frequency resources located between the two adjacent LBT bandwidths are available for use) .
  • a method of wireless communications implemented by a UE may include identifying, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identifying a set of LBT bandwidths within the BWP, determining frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicating with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identify a set of LBT bandwidths within the BWP, determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the apparatus may include means for identifying, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identifying a set of LBT bandwidths within the BWP, determining frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicating with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • a non-transitory computer-readable medium storing code for wireless communications implemented by a UE is described.
  • the code may include instructions executable by a processor to identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identify a set of LBT bandwidths within the BWP, determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the determining the frame configurations for each of the set of LBT bandwidths may include operations, features, means, or instructions for receiving, from the base station, an indication of the frame configurations for each of the set of LBT bandwidths.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining an offset from a start of a frame of the BWP, a period length, an idle duration, or a combination thereof for each of the set of LBT bandwidths based on the received indication of the frame configurations.
  • each of the set of LBT bandwidths may have a same period length and a different offset from the start of the frame of the BWP, each of the set of LBT bandwidths may have a different period length and a same offset from the start of the frame of the BWP, or each of the set of LBT bandwidths may have a different period length and a different offset from the start of the frame of the BWP.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the indication of the frame configurations via RRC signaling.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a guard band is present between two of the set of LBT bandwidths based on a first LBT bandwidth of the two of the set of LBT bandwidths being idle, having a failed LBT procedure, or a combination thereof.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the base station, an indication of the guard band or an absence of the guard band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for detecting a signal on each of two adjacent LBT bandwidths of the set of LBT bandwidths, and identifying that a guard band between the two adjacent LBT bandwidths is not present based on the detected signal on each of the two adjacent LBT bandwidths.
  • the signal may include a physical downlink control channel (PDCCH) , a synchronization signal (SS) block, a physical broadcast channel (PBCH) , remaining minimum system information (RMSI) , a group common PDCCH (GC-PDCCH) , a physical downlink shared channel (PDSCH) , or a combination thereof.
  • PDCCH physical downlink control channel
  • SS synchronization signal
  • PBCH physical broadcast channel
  • RMSI remaining minimum system information
  • GC-PDCCH group common PDCCH
  • PDSCH physical downlink shared channel
  • the frame configurations may include a COT and an idle time.
  • a method of wireless communications implemented by a UE is described.
  • the method may include identifying, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identifying a set of LBT bandwidths within the BWP, determining CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and monitoring for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identify a set of LBT bandwidths within the BWP, determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • the apparatus may include means for identifying, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identifying a set of LBT bandwidths within the BWP, determining CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and monitoring for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • a non-transitory computer-readable medium storing code for wireless communications implemented by a UE is described.
  • the code may include instructions executable by a processor to identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station, identify a set of LBT bandwidths within the BWP, determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the base station, the CORESET configurations for each of the set of LBT bandwidths.
  • CORESETs for each of the set of LBT bandwidths may be aligned in time.
  • the offset associated with the CORESET may be different from a frame offset associated with the at least one of the set of LBT bandwidths.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying that a CORESET occurs during an idle time of an LBT bandwidth of the set of LBT bandwidths and refraining from decoding the CORESET based on identifying that the CORESET occurs during the idle time.
  • a method of wireless communications implemented by a base station may include identifying, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identifying a set of LBT bandwidths within the BWP, determining frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicating with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identify a set of LBT bandwidths within the BWP, determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicate with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the apparatus may include means for identifying, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identifying a set of LBT bandwidths within the BWP, determining frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicating with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • a non-transitory computer-readable medium storing code for wireless communications implemented by a base station is described.
  • the code may include instructions executable by a processor to identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identify a set of LBT bandwidths within the BWP, determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof, and communicate with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the determining the frame configurations for each of the set of LBT bandwidths may include operations, features, means, or instructions for determining an offset from a start of a frame of the BWP, a period length, an idle duration, or a combination thereof for each of the set of LBT bandwidths.
  • each of the set of LBT bandwidths may have a same period length and a different offset from the start of the frame of the BWP, each of the set of LBT bandwidths may have a different period length and a same offset from the start of the frame of the BWP, or each of the set of LBT bandwidths may have a different period length and a different offset from the start of the frame of the BWP.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining to allocate a guard band between two of the set of LBT bandwidths based on a first LBT bandwidth of the two LBT bandwidths being idle, having a failed LBT procedure, or a combination thereof.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the UE, an indication of the guard band or an absence of the guard band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of the frame configurations via RRC signaling.
  • the frame configurations may include a COT and an idle time.
  • a method of wireless communications implemented by a base station may include identifying, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identifying a set of LBT bandwidths within the BWP, determining CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and transmitting, to the UE, downlink control information within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identify a set of LBT bandwidths within the BWP, determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and transmit, to the UE, downlink control information within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • the apparatus may include means for identifying, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identifying a set of LBT bandwidths within the BWP, determining CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and transmitting, to the UE, downlink control information within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • a non-transitory computer-readable medium storing code for wireless communications implemented by a base station is described.
  • the code may include instructions executable by a processor to identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE, identify a set of LBT bandwidths within the BWP, determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof, and transmit, to the UE, downlink control information within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the UE, the CORESET configurations for each of the set of LBT bandwidths.
  • CORESETs for each of the set of LBT bandwidths may be aligned in time.
  • FIG. 1 illustrates an example of a system for wireless communications that supports a fixed frame period (FFP) configuration for listen-before-talk (LBT) bandwidths in accordance with aspects of the present disclosure.
  • FFP fixed frame period
  • LBT listen-before-talk
  • FIG. 2 illustrates an example of a wireless communications system that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIGs. 3 and 4 illustrate examples of frame structures that support an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIG. 5 illustrates an example of a control resource set (CORESET) configuration that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • CORESET control resource set
  • FIGs. 6 and 7 illustrate examples of process flows that support an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIGs. 8 and 9 show block diagrams of devices that support an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIG. 10 shows a block diagram of a user equipment (UE) communications manager that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • UE user equipment
  • FIG. 11 shows a diagram of a system including a device that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIGs. 12 and 13 show block diagrams of devices that support an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIG. 14 shows a block diagram of a base station communications manager that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIG. 15 shows a diagram of a system including a device that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FIGs. 16 through 22 show flowcharts illustrating methods that support an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • FBE Frame Based Equipment
  • NR New Radio
  • NR-U New Radio
  • UE user equipment
  • FFP fixed frame period
  • UE transmissions within an FFP can occur if downlink signals or channels within the FFP are detected (e.g., a physical downlink control channel (PDCCH) , a synchronization signal (SS) block, a physical broadcast channel (PBCH) , an SS/PBCH block (SSB) , remaining minimum system information (RMSI) , a group common PDCCH (GC-PDCCH) , a physical shared control channel (PDSCH) , etc. ) .
  • the UE may detect if the downlink signals or channels are occurring within a bandwidth part (BWP) based on the information for the FFP provided by the base station.
  • BWP bandwidth part
  • the BWP may be divided into multiple listen-before-talk (LBT) bandwidths.
  • LBT listen-before-talk
  • FFP structures e.g., different frame configurations
  • each LBT bandwidth may have a different offset from a start of a frame for the BWP (e.g., different starting points) , a different period, a different idle duration, or a combination thereof.
  • each LBT bandwidth may have an FFP structure with a same period and a different offset, a different period and a same offset, or a different period and a different offset.
  • a guard band may exist between each LBT bandwidth but may not be needed in some cases.
  • a UE may need to maintain a guard band between each LBT bandwidth if one LBT bandwidth is idle or one LBT bandwidth has a failed LBT; otherwise, the guard band may be used.
  • the UE may determine whether to maintain a guard band or not based on an explicit indication from the base station or by detecting whether the two adjacent LBT bandwidths have signaling (e.g., if both adjacent LBT bandwidths are active, the UE can combine them into a single aggregated bandwidth, but if one of the LBT bandwidths is not active, the UE may maintain a guard band between the adjacent LBT bandwidths) .
  • control resource sets (CORESETs) in each LBT bandwidth may be determined by the UE and the base station.
  • independent multiple CORESETs may be configured (e.g., by the base station) , where each CORESET corresponds to each LBT bandwidth.
  • CORESET locations in a time domain may be defined for each LBT bandwidth.
  • CORESET parameters other than a starting point in a frequency domain may be identical for each LBT bandwidth, different offsets of the CORESETs in the time domain may be used for each LBT bandwidth (e.g., configured by RRC with a fixed pattern) , the starting point of the CORESETs may be aligned for each LBT bandwidth, or a combination thereof.
  • the UE may ignore a CORESET location that occurs in the idle period.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Additionally, aspects of the disclosure are illustrated by an additional wireless communications system, frame structure examples, a CORESET configuration example, and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to an FFP configuration for LBT bandwidths.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.
  • ultra-reliable e.g., mission critical
  • the base stations 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may be devices in different forms or having different capabilities.
  • the base stations 105 and the UEs 115 may wirelessly communicate via one or more communication links 125.
  • Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base station 105 may establish one or more communication links 125.
  • the coverage area 110 may be an example of a geographic area over which a base station 105 and a UE 115 may support the communication of signals according to one or more radio access technologies.
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, the base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment) , as shown in FIG. 1.
  • network equipment e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment
  • the base stations 105 may communicate with the core network 130, or with one another, or both.
  • the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an S1, N2, N3, or other interface) .
  • the base stations 105 may communicate with one another over the backhaul links 120 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations 105) , or indirectly (e.g., via core network 130) , or both.
  • the backhaul links 120 may be or include one or more wireless links.
  • One or more of the base stations 105 described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a Home NodeB, a Home eNodeB, or other suitable terminology.
  • a base transceiver station a radio base station
  • an access point a radio transceiver
  • a NodeB an eNodeB (eNB)
  • eNB eNodeB
  • a next-generation NodeB or a giga-NodeB either of which may be referred to as a gNB
  • gNB giga-NodeB
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the base stations 105 may wirelessly communicate with one another via one or more communication links 125 over one or more carriers.
  • the term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • BWP bandwidth part
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN) ) and may be positioned according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode where initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode where a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
  • the communication links 125 shown in the wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions from a base station 105 to a UE 115.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some aspects the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a number of determined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the base stations 105, the UEs 115, or both
  • the wireless communications system 100 may include base stations 105 or UEs 115 that support simultaneous communications via carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT- S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT- S-OFDM discrete Fourier transform spread OFDM
  • a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related.
  • the number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) .
  • a wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams) , and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, where a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots.
  • each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing.
  • Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., the number of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed on a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed on a downlink carrier, in one aspect, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a CORESET
  • a control region for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier.
  • One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • a base station 105 may be movable and therefore provide communication coverage for a moving geographic coverage area 110.
  • different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105.
  • the overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105.
  • the wireless communications system 100 may include, in one aspect, a heterogeneous network in which different types of the base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • the base stations 105 may have similar frame timings, and transmissions from different base stations 105 may be approximately aligned in time.
  • the base stations 105 may have different frame timings, and transmissions from different base stations 105 may, in some aspects, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications.
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions) .
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT) , mission critical video (MCVideo) , or mission critical data (MCData) .
  • MCPTT mission critical push-to-talk
  • MCVideo mission critical video
  • MCData mission critical data
  • Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • One or more UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of a base station 105.
  • Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105 or be otherwise unable to receive transmissions from a base station 105.
  • groups of the UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs 115 without the involvement of a base station 105.
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to the network operators IP services 150.
  • the operators IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • Some of the network devices may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC) .
  • Each access network entity 140 may communicate with the UEs 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs) .
  • Each access network transmission entity 145 may include one or more antenna panels.
  • various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station 105) .
  • the wireless communications system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors.
  • the transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the base stations 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA) .
  • Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a base station 105 or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations.
  • a base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a UE 115 attempting to access a wireless network may perform an initial cell search by detecting a primary synchronization signal (PSS) from a base station 105.
  • PSS primary synchronization signal
  • the UE 115 may then receive a secondary synchronization signal (SSS) .
  • SSS secondary synchronization signal
  • the SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell.
  • the SSS may also enable detection of a duplexing mode and a cyclic prefix length.
  • Some systems, such as TDD systems may transmit an SSS but not a PSS. Both the PSS and the SSS may be located in the central 62 and 72 subcarriers of a carrier, respectively.
  • a base station 105 may transmit synchronization signals (e.g., PSS SSS, and the like) using multiple beams in a beam-sweeping manner through a cell coverage area.
  • PSS, SSS, and/or broadcast information e.g., a PBCH
  • PSS, SSS, and/or broadcast information may be transmitted within different SS blocks on respective directional beams, where one or more SS blocks may be included within an SS burst.
  • the UE 115 may receive a master information block (MIB) , which may be transmitted in the PBCH.
  • the MIB may contain system bandwidth information, an SFN, and a physical hybrid access request (HARQ) indicator channel (PHICH) configuration.
  • the UE 115 may receive one or more system information blocks (SIBs) .
  • SIBs system information blocks
  • a SIB1 may contain cell access parameters and scheduling information for other SIBs. Decoding the SIB1 may enable the UE 115 to receive a SIB2.
  • the SIB2 may contain RRC configuration information related to random access channel (RACH) procedures, paging, PUCCH, physical uplink shared channel (PUSCH) , power control, sounding reference signal (SRS) , and cell barring.
  • a UE 115 may decode the MIB, SIB1 and SIB2 prior to accessing the network.
  • the MIB may be transmitted on PBCH and may utilize the first 4 OFDMA symbols of the second slot of the first subframe of each radio frame. It may use the middle 6 resource blocks (RBs) (e.g., 72 subcarriers) in the frequency domain.
  • RBs resource blocks
  • the MIB carries a few important pieces of information for UE initial access, including downlink channel bandwidth in term of RBs, PHICH configuration (duration and resource assignment) , and SFN.
  • the UE 115 may try different phases of a scrambling code until it gets a successful cyclic redundancy check (CRC) check.
  • the phase of the scrambling code (0, 1, 2 or 3) may enable the UE 115 to identify which of the four repetitions has been received.
  • the UE 115 may determine the current SFN by reading the SFN in the decoded transmission and adding the scrambling code phase.
  • the UE 115 may receive the one or more SIBs. Different SIBs may be defined according to the type of system information conveyed.
  • SIB1 includes access information, including cell identity information, and it may indicate whether a UE 115 is allowed to camp on a cell.
  • SIB1 also includes cell selection information (or cell selection parameters) .
  • SIB1 includes scheduling information for other SIBs.
  • SIB2 may be scheduled dynamically according to information in SIB1 and may include access information and parameters related to common and shared channels. The periodicity of SIB2 can be set to 8, 16, 32, 64, 128, 256 or 512 radio frames.
  • the UE 115 may perform a random access procedure (e.g., a two-step RACH procedure, a four-step RACH procedure, etc. )
  • an available bandwidth of frequencies for the communications may be split into BWPs that are subsets of the available bandwidth of frequencies.
  • a BWP may be a bandwidth where the UE 115 can transmit and/or receive information.
  • a maximum number of four (4) BWPs may be configured for the UE 115.
  • the UE 115 may monitor a single, active BWP at a time (e.g., on a PCell) . Additionally, on an SCell, the UE 115 may have multiple active BWPs at a given time.
  • a carrier may be split into the one or more BWPs based on the size of the carrier exceeding a bandwidth threshold (e.g., greater than 20 MHz) .
  • Each of the BWPs may further include one or more sub-channels (e.g., subbands) , where each sub-channel is a same bandwidth (e.g., 20 MHz) . Accordingly, each BWP may vary in size (e.g., in multiples of 20 MHz) based on the number of sub-channels located in each.
  • the BWPs and corresponding sub-channels may be part of a shared (e.g., unlicensed or shared licensed, such as NR-U) radio frequency (RF) spectrum for which one or more wireless devices (e.g., base stations 105 and UEs 115) contend.
  • a base station 105 may determine which sub-channels are available for communications with other wireless devices based on an LBT procedure that indicates if on-going communications are present on each of the sub-channels.
  • a UE 115 may perform an LBT (e.g., an LBT procedure, a clear channel assessment (CCA) , etc. ) based on communicating with base station 105 in an unlicensed band (e.g., unlicensed frequency band, NR-U, etc. ) .
  • the LBT may include the UE 115 listening to uplink resources (e.g., indicated by an uplink grant from the base station 105) for transmitting one or more uplink signals to determine whether the channel is clear before attempting to transmit on the uplink resources.
  • the UE 115 may refrain from transmitting the uplink signals.
  • the UE 115 may determine the LBT is successful and may proceed with transmitting the uplink signals.
  • wireless communications system 100 may support an FBE operation to allocate resources in the unlicensed band for a wireless communication device (e.g., a UE 115, a base station 105, etc. ) to contend for the resources. Accordingly, the resources may be allocated in a consistent manner based on the FBE operation to allow the wireless communication devices to know when and where the resources occur in the unlicensed band (e.g., within a frame) .
  • a base station 105 operates as an initiating device for the FBE operation
  • a UE 115 may be provided information by the base station 105 on one or more FFPs configured for the FBE operation and starting positions of the FFPs.
  • the base station 105 may transmit an indication of the FFP and the starting positions of the FFPs (e.g., FFP configuration, frame configuration, etc. ) to the UE 115 (e.g., via a SIB, a SIBx, etc. ) .
  • the FFP configuration may be included in a SIB1.
  • the FFP configuration may be signaled for a UE 115 with UE-specific RRC signaling.
  • transmissions from the UE 115 within an FFP can occur if downlink signals or channels within the FFP are detected (e.g., PDCCHs, SSBs, PBCHs, RMSI, GC-PDCCHs, PDSCHs, etc. ) .
  • a GC-PDCCH configuration may apply to one or more UEs 115 in an idle mode.
  • the BWP may be divided into multiple LBT bandwidths. Conventionally, each of the LBT bandwidths may be aligned to a same configured FFP that is indicated as described above.
  • a CORESET configuration may be determined for a serving cell with a carrier bandwidth greater than an LBT bandwidth.
  • a CORESET may be confined within an LBT bandwidth, and a search space set configuration associated with the CORESET may have multiple monitoring locations in the frequency domain (per LBT bandwidth) .
  • a base station 105 transmits a PDCCH or PDSCH on a single BWP if a CCA is successful at the base station 105 for the whole BWP, one or more CORESETs may not be confined within an LBT bandwidth.
  • a search space set configuration associated with multiple monitoring locations in the frequency domain e.g., a search space set associated with a CORESET confined within an LBT bandwidth
  • PRBs physical RBs allocated by a parameter in the CORESET configuration indicating frequency resources (e.g., frequencyDomainResources parameter) may be confined within one LBT bandwidth within the BWP corresponding to the CORESET.
  • each of the one or more monitoring locations in the frequency domain may correspond to (and be confined within) an LBT bandwidth and may have a frequency domain resource allocation pattern that is replicated from a pattern configured in the CORESET.
  • CORESET parameters other than a frequency domain resource allocation pattern may be identical for each of the one or more monitoring locations in the frequency domain.
  • a frequency domain location for a CORESET may be determined based on a subcarrier spacing (SCS) of the LBT bandwidth that includes the CORESET.
  • SCS subcarrier spacing
  • an RB level offset from ⁇ 0, 1, 2, 3 ⁇ for the CORESET may be indicated in a PDCCH (e.g., a pdcch-ConfigSIB1 message) .
  • a PDCCH e.g., a pdcch-ConfigSIB1 message
  • an RB level offset from ⁇ 10, 12, 14, 16 ⁇ for the CORESET may be indicated in a PDCCH (e.g., the pdcch-ConfigSIB1 message) .
  • a wireless communication device may determine where the CORESET is located in the LBT bandwidth within the frequency domain (e.g., in the BWP) .
  • the above described techniques for determining the FFP configuration and the frequency location of a CORESET confined within an LBT bandwidth may not support efficient techniques for communications between a UE 115 and a base station 105.
  • techniques may be desired to indicate different FFP configurations (e.g., frame configurations) for each LBT bandwidth. For the determination and indication of the frequency location of a CORESET within an LBT bandwidth, resources used in the time domain may need to be indicated as well.
  • Wireless communications system 100 may support efficient techniques for a UE 115 and a base station 105 to determine respective frame configurations (e.g., frame offsets, period lengths, idle durations, etc., of an FFP) for each of one or more LBT bandwidths configured within a BWP. Subsequently, the UE 115 and the base station 105 may communicate within one or more channel occupancy times (COTs) of the one or more LBT bandwidths based on the frame configurations.
  • COTs channel occupancy times
  • the UE 115 and the base station 105 may determine CORESET configurations (e.g., time and frequency allocations of the CORESETs) for each of the one or more LBT bandwidths, where the CORESET configurations include a length and offset for corresponding CORESETs in COTs of each of the one or more LBT bandwidths.
  • CORESET configurations e.g., time and frequency allocations of the CORESETs
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • wireless communications system 200 may implement aspects of wireless communications system 100.
  • Wireless communications system 200 may include a base station 105-a and a UE 115-a, which may be examples of base stations 105 and UEs 115, respectively, as described above with reference to FIG. 1.
  • base station 105-a and UE 115-a may communicate on resources of a carrier 205.
  • carrier 205 may include resources in an unlicensed band (e.g., NR-U communications) , and the resources may be divided into one or more BWPs 215 as described above.
  • unlicensed band e.g., NR-U communications
  • base station 105-a and UE 115-a may use an FBE operation to indicate which resources of carrier 205 are available for contention.
  • base station 105-a may transmit a frame configuration 210 to UE 115-a to indicate information about an FFP to be used for the FBE operation.
  • base station 105-b (e.g., acting as an initiating device for the FBE operation) may indicate a period length and a starting position of the FFP for a whole BWP 215 used for communication between UE 115-a and base station 105-a.
  • the FFP may provide a fixed duration and location for UEs 115 and/or base stations 105 to contend for resources for subsequent communications.
  • the total frequency of carrier 205 may be split into at least a first BWP 215-a and a second BWP 215-b, and the second BWP 215-b may be used for the FBE operation with the FFP and communications between base station 105-a and UE 115-a.
  • BWP 215-b may be larger than a single LBT bandwidth 220 (e.g., greater than 20 MHz) , and, as such, BWP 215-b may be divided into multiple LBT bandwidths 220.
  • BWP 215-b may include a first LBT bandwidth 220-a, a second LBT bandwidth 220-b, and a third LBT bandwidth 220-c.
  • BWPs 215 and three (3) LBT bandwidths 220 While two (2) BWPs 215 and three (3) LBT bandwidths 220 are shown in the example of wireless communications system 200, a greater or fewer number of BWPs 215 and LBT bandwidths 220 may be configured for communications between UE 115-a and base station 105-a.
  • the LBT bandwidths 220 may be used by a wireless communication device (e.g., UE 115-a) attempting to communicate in BWP 215-b, and rather than attempting to detect a signal across the entirety of BWP 215-b to determine whether resources of BWP 215-b are available for subsequent communications, the wireless communication device may monitor subsets of BWP 215-b through the LBT bandwidths 220 (e.g., using a category 2 (cat2) LBT, a one shot LBT, etc. ) .
  • a wireless communication device e.g., UE 115-a
  • the wireless communication device may monitor subsets of BWP 215-b through the LBT bandwidths 220 (e.g., using a category 2 (cat2) LBT, a one shot LBT, etc. ) .
  • the wireless communication device may be able to use portions of BWP 215-b rather than invalidating the entire BWP 215-b based on detecting a signal in a portion of the BWP 215-b.
  • These signals may include PDCCHs, SSBs, PBCHs, RMSI, GC-PDCCHs, PDSCHs, or other downlink signals transmitted by base station 105-aon resources of BWP 215-b.
  • base station 105-a may indicate respective FFP configurations (e.g., frame configurations, FFP structures, etc. ) for different LBT bandwidths 220 in frame configuration 210.
  • frame configuration 210 may indicate different starting points, different periods (e.g., period length) , different idle durations, or a combination thereof for an FFP specific to each LBT bandwidth 220.
  • the different starting periods for each of the FFP configurations in each LBT bandwidth 220 may be indicated via a frame offset value, which corresponds to a time offset (e.g., number of seconds/milliseconds, a number of symbols, etc. ) after a start of an overall FFP configuration for BWP 215-b.
  • the idle duration e.g., an idle period
  • the idle duration may be determined based on a minimum from a regulation for the FFP, and longer idle periods may not be configured, in some cases.
  • base station 105-a may transmit frame configuration 210 with the information for the respective FFP configurations for the different LBT bandwidths 220 via RRC signaling.
  • the FFP configurations for each of the LBT bandwidths 220 may include a same period (e.g., 1ms, 2ms, 2.5ms, 4ms, 10ms, etc. ) and a different offset (e.g., different starting point) , different periods and a same offset, or different periods and different offsets.
  • a guard band may be configured between two adjacent LBT bandwidths 220.
  • a guard band may not always be needed, and the resources used as a guard band between the adjacent LBT bandwidths 220 may be used for communications between UE 115-a and base station 105-a rather than being unavailable.
  • the guard band may be used for communications if both side subbands can be used. That is, if both LBT bandwidths 220 on either side of the guard band are available (e.g., if both LBT bandwidths 220 are determined to be available after corresponding LBT procedures are performed on the LBT bandwidths 220) , the guard band may be determined to also be available.
  • resource utilization of BWP 215-b may be similar to a carrier aggregation (CA) configuration, and available resources may be underutilized.
  • CA carrier aggregation
  • uplink and downlink directions may be the same across subbands (e.g., LBT bandwidths 220) for utilizing the guard band.
  • the guard band may be maintained if one subband is idle or one subband has a failed LBT (e.g., if at least one LBT bandwidth 220 on either side of the guard band is occupied by a different transmitter or idle) . Otherwise, the guard band may be used (e.g., both LBT bandwidths 220 on either side of the guard band are available and active) . In some cases, base station 105-a may explicitly indicate the LBT bandwidths 220 and whether guard bands are used between two adjacent LBT bandwidths 220 or if no guard bands are used between two adjacent LBT bandwidths 220.
  • UE 115-a may deduce whether a guard band is used between two adjacent LBT bandwidths 220 based on receiving downlink signals (e.g., PDCCHs, SSBs, PBCHs, RMSI, GC-PDCCHs, PDSCHs, etc. ) on both of the adjacent LBT bandwidths 220.
  • downlink signals e.g., PDCCHs, SSBs, PBCHs, RMSI, GC-PDCCHs, PDSCHs, etc.
  • CORESET locations may be configured and determined in each LBT bandwidth 220, including a time domain allocation of the CORESET locations.
  • base station 105-a e.g., a network device, the network, etc.
  • CORESET locations in time domain may be configured in each LBT bandwidth 220 (e.g., different offsets for each CORESET in each LBT bandwidth 220, all CORESETs have a starting point aligned across the LBT bandwidths 220, etc. ) , and a frequency domain allocation for the CORESETs may follow the techniques as described above with reference to FIG. 1.
  • UE 115-a may communicate with base station 105-a.
  • UE 115-a may use the FFP configurations to identify when and where to detect downlink signals from base station 105-ain each LBT bandwidth 220 to then be able to communicate with base station 105-a.
  • UE 115-a may use the FFP configurations to allocate the resources of each LBT bandwidth 220 for subsequent communications with base station 105-a (e.g., not only for performing LBT procedures to then determine if the LBT bandwidth 220 is available for communication) .
  • UE 115-a may identify when and where base station 105-a may transmit downlink control information (DCI) in a CORESET within an LBT bandwidth 220 based on the LBT configurations.
  • DCI downlink control information
  • FIG. 3 illustrates an example of a frame structure 300 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • frame structure 300 may implement aspects of wireless communications systems 100 and/or 200.
  • a UE 115 and a base station 105 may use frame structure 300 for communications based on different FFP structures for different LBT bandwidths.
  • Frame structure 300 may include one or more LBT bandwidths 305 of a BWP as described above with reference to FIGs. 1 and 2 (e.g., the BWP is greater than a threshold size, such as 20 MHz, and the BWP is divided into multiple LBT bandwidths 305) .
  • the BWP may include a first LBT bandwidth 305-a, a second LBT bandwidth 305-b, and a third LBT bandwidth 305-a.
  • each LBT bandwidth 305 may include a respective FFP 310 that includes a COT 315 and an idle period 320.
  • the COTs 315 may be used for any communications between the UE 115 and the base station 105 for the FFP 310, and the idle periods 320 (e.g., idle durations) may be used as idle times for the communications between the UE 115 and the base station 105, where the UE 115 or the base station 105 does not expect to receive any signaling from the other wireless communication device. While three (3) LBT bandwidths 305 are shown in the example of frame structure 300, a greater or fewer number of LBT bandwidths 305 may be configured for communications between the UE 115 and the base station 105.
  • frame structure 300 may include a frame starting position 325 that represents a starting point for the BWP that includes the multiple LBT bandwidths 305.
  • the base station 105 may indicate an FFP for the entire BWP that includes a starting point (e.g., frame starting position 325) and a period length of the FFP for the BWP.
  • the FFPs 310 for the LBT bandwidths 305 may go until an end of the frame for the BWP.
  • the length of the idle periods 320 may be given as a percentage of the overall FFP 310.
  • the FFPs 310 may be repeated every frame within the BWP.
  • frame structure 300 may include same periods (e.g., same lengths for FFPs 310) but different offsets for each FFP configuration in each LBT bandwidth 305.
  • each FFP configuration may include a same period length in each LBT bandwidth 305 (e.g., a duration of FFP 310) , but a first FFP configuration for first LBT bandwidth 305-amay have a first starting point 330-a, a second FFP configuration for second LBT bandwidth 305-b may have a second starting point 330-b, and a third FFP configuration for third LBT bandwidth 305-c may have a third starting point 330-c.
  • the different starting points 330 of each FFP configuration for the respective LBT bandwidths 305 may be indicated as corresponding offset values for each FFP configuration with respect to frame starting position 325 (e.g., a starting frame or beginning of the BWP) .
  • idle periods may be avoided in the BWP (e.g., a scheduler, such as the base station 105 can avoid holes of concurrent idle periods across the entire BWP) .
  • frame structure 300 may be used for uplink rate matching for resources of the BWP.
  • these different FFP configurations for the respective LBT bandwidths 305 may be used for low latency traffic (e.g., URLLC traffic) operations because no large instance where no traffic can be served may exist (e.g., no big holes where no traffic can be served are present) based on avoiding the idle periods across the entire BWP.
  • a guard band 335 may be configured or present between two adjacent LBT bandwidths 305.
  • a first guard band 335-a may exist between first LBT bandwidth 305-a and second LBT bandwidth 305-b
  • a second guard band 335-b may exist between second LBT bandwidth 305-b and third LBT bandwidth 305-c.
  • the guard band 335 may be maintained (e.g., the guard band 335 is used and observed) if one LBT bandwidth 305 is idle or one LBT bandwidth 305 has a failed LBT. Otherwise, the guard band 335 may be used for communications, where the guard band 335 is determined to be absent (e.g., both LBT bandwidths 305 on either side of the guard band 335 are available and active) .
  • FIG. 4 illustrates an example of a frame structure 400 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • frame structure 400 may implement aspects of wireless communications systems 100 and/or 200.
  • a UE 115 and a base station 105 may use frame structure 400 for communications based on different FFP structures for different LBT bandwidths.
  • Frame structure 400 may include one or more LBT bandwidths 405 of a BWP as described above with reference to FIGs. 1-3 (e.g., the BWP is greater than a threshold size, such as 20 MHz, and the BWP is divided into multiple LBT bandwidths 405) .
  • the BWP may include a first LBT bandwidth 405-a, a second LBT bandwidth 405-b, and a third LBT bandwidth 405-a.
  • each LBT bandwidth 405 may include a respective FFP 410 that includes a COT 415 and an idle period 420 as described above with reference to FIG. 3.
  • three (3) LBT bandwidths 405 are shown in the example of frame structure 400, a greater or fewer number of LBT bandwidths 405 may be configured for communications between the UE 115 and the base station 105.
  • frame structure 400 may include a frame starting position 425 that represents a starting point for the BWP that includes the multiple LBT bandwidths 405.
  • the base station 105 may indicate an FFP for the entire BWP that includes a starting point (e.g., frame starting position 425) and a period length of the FFP for the BWP.
  • the FFPs 410 for the LBT bandwidths 405 may go until an end of the frame for the BWP.
  • the length of the idle periods 420 may be given as a percentage of the overall FFP 310.
  • the FFPs 410 may be repeated every frame within the BWP.
  • frame structure 400 may include different periods (e.g., variable FFPs 410) and a same offset (e.g., a same starting point 430) .
  • each FFP configuration may include a different period length in each LBT bandwidth 405, where a first FFP configuration for first LBT bandwidth 405-a may have a first FFP 410-a, a second FFP configuration for second LBT bandwidth 405-b may have a second FFP 410-b, and a third FFP configuration for third LBT bandwidth 405-c may have a third FFP 410-c.
  • each idle period 420 is shown as being a same duration in each of the FFPs 410, the durations may vary based on the length of the FFP 410. As described above with reference to FIG. 2, the length of the idle periods 420 may be given as a percentage of the length of the FFP 410, so the longer or shorter the length of the FFP 410 may correspond to a longer or shorter idle period 420.
  • LBT bandwidths 405 may be used for sending SSBs (e.g., more SSB opportunities within a COT) .
  • validation of physical RACH (PRACH) resources may occur over a longer period (e.g., at the cost of longer idle periods 420 based on the length of the idle periods 420 being a percentage of the FFP 410 length) in that LBT bandwidth 405 (e.g., a subband of the BWP) , but other LBT bandwidths 405 (e.g., other subbands) may be faster to validate (e.g., because of possible repetition across different COTs) .
  • the FFP configurations in each LBT bandwidth 405 may include different periods and different offsets.
  • a guard band 435 may be configured or present between two adjacent LBT bandwidths 405.
  • a first guard band 435-a may exist between first LBT bandwidth 405-a and second LBT bandwidth 405-b
  • a second guard band 435-b may exist between second LBT bandwidth 405-b and third LBT bandwidth 405-c.
  • the guard band 435 may be maintained (e.g., the guard band 435 is used and observed) if one LBT bandwidth 405 is idle or one LBT bandwidth 405 has a failed LBT. Otherwise, the guard band 435 may be used for communications, where the guard band 435 is determined to be absent (e.g., both LBT bandwidths 405 on either side of the guard band 435 are available and active) .
  • FIG. 5 illustrates an example of a CORESET configuration 500 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • CORESET configuration 500 may implement aspects of wireless communications systems 100 and/or 200.
  • a UE 115 and a base station 105 may use CORESET configuration 500 for communications based on different CORESET locations for different LBT bandwidths.
  • CORESET configuration 500 may include one or more LBT bandwidths 505 of a BWP as described above with reference to FIGs. 1-4 (e.g., the BWP is greater than a threshold size, such as 20 MHz, and the BWP is divided into multiple LBT bandwidths 505) .
  • the BWP may include a first LBT bandwidth 505-a, a second LBT bandwidth 505-b, and a third LBT bandwidth 505-a.
  • each LBT bandwidth 505 may include a respective FFP 510 that includes a COT 515 and an idle period 520 as described above with reference to FIGs. 3 and 4.
  • three (3) LBT bandwidths 505 are shown in the example of CORESET configuration 500, a greater or fewer number of LBT bandwidths 505 may be configured for communications between the UE 115 and the base station 105.
  • one or more CORESETs 540 may be configured (e.g., CORESET configurations) for each LBT bandwidth 505.
  • independent multiple CORESETs 540 may be configured for each LBT bandwidth 505, where each CORESET 540 corresponds to each LBT bandwidth 505.
  • each CORESET 540 may not be related with respect to frequency, time, or both.
  • locations in the time domain for each CORESET 540 may be configured for each LBT bandwidth 505.
  • the CORESET location in the frequency resources of each LBT bandwidth 505 may be indicated via PDCCH as indicated above with reference to FIG. 1.
  • the CORESETs 540 in each LBT bandwidth 505 may be mirrored from one LBT bandwidth 505 to another, such that the CORESET parameters other than a starting point in frequency domain may be identical for each LBT bandwidth 505.
  • a first CORESET 540 for first LBT bandwidth 505-a may have a first starting point 530-a
  • a second CORESET 540 for second LBT bandwidth 505-b may have a second starting point 530-b
  • a third CORESET 540 for third LBT bandwidth 505-c may have a third starting point 530-c.
  • the different starting points 530 of each CORESET 540 for the respective LBT bandwidths 505 may be indicated as corresponding offset values for each CORESET 540 with respect to a frame starting position 525 (e.g., a starting frame or beginning of the BWP) .
  • the different offsets of the CORESETs 540 may be indicated via RRC signaling (e.g., with a fixed pattern) .
  • a duration of an FFP 510 may be indicated for each LBT bandwidth 505, as well as a duration of the CORESETs 540. That is, CORESET 540 may occur anywhere within FFP 510 as the starting point 530 may be configured independently of FFP 510.
  • the starting points 530 of the CORESETs 540 may be aligned for each LBT bandwidth 505 (e.g., each CORESET 540 begins at a same point offset from the frame starting position 525) .
  • the UE 115 may determine to refrain from decoding the CORESET 540. In one aspect, during an idle period 520 for a given FFP associated with a given LBT bandwidth 505, the UE 115 may automatically ignore corresponding CORESET 540 locations that land in the idle period 520.
  • a guard band 535 may be configured or present between two adjacent LBT bandwidths 505.
  • a first guard band 535-a may exist between first LBT bandwidth 505-a and second LBT bandwidth 505-b
  • a second guard band 535-b may exist between second LBT bandwidth 505-b and third LBT bandwidth 505-c.
  • the guard band 535 may be maintained (e.g., the guard band 535 is used and observed) if one LBT bandwidth 505 is idle or one LBT bandwidth 505 has a failed LBT. Otherwise, the guard band 535 may be used for communications, where the guard band 535 is determined to be absent (e.g., both LBT bandwidths 505 on either side of the guard band 535 are available and active) .
  • FIG. 6 illustrates an example of a process flow 600 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • process flow 600 may implement aspects of wireless communications systems 100 and/or 200.
  • Process flow 600 may include a base station 105-b and a UE 115-b, which may be examples of base stations 105 and UEs 115, respectively, as described above with reference to FIGs. 1-5.
  • the operations between UE 115-b and base station 105-b may be performed in different orders or at different times. Certain operations may also be left out of the process flow 600, or other operations may be added to the process flow 600. It is to be understood that while UE 115-b and base station 105-b are shown performing a number of the operations of process flow 600, any wireless device may perform the operations shown.
  • UE 115-b and base station 105-b may identify, in a shared radio frequency spectrum, a BWP configured for communications between UE 115-b and base station 105-b.
  • UE 115-b and base station 105-b may identify a set of LBT bandwidths within the BWP.
  • UE 115-b and base station 105-b may determine frame configurations (e.g., FFP configurations) for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof. Additionally, the frame configurations may include a COT and an idle time. In some cases, base station 105-b may determine an offset from a start of a frame of the BWP, a period length, an idle duration, or a combination thereof for each of the set of LBT bandwidths.
  • frame configurations e.g., FFP configurations
  • the frame configurations may include a COT and an idle time.
  • base station 105-b may determine an offset from a start of a frame of the BWP, a period length, an idle duration, or a combination thereof for each of the set of LBT bandwidths.
  • UE 115-b may receive, from base station 105-b, an indication of the frame configurations for each of the set of LBT bandwidths.
  • UE 115-b may receive the indication of the frame configurations via RRC signaling.
  • UE 115-b may determine an offset from a start of a frame of the BWP, a period length, an idle duration, or a combination thereof for each of the set of LBT bandwidths based on the received indication of the frame configurations.
  • each of the set of LBT bandwidths may have a same period length and a different offset from the start of the frame of the BWP, each of the set of LBT bandwidths may have a different period length and a same offset from the start of the frame of the BWP, or each of the set of LBT bandwidths may have a different period length and a different offset from the start of the frame of the BWP.
  • UE 115-b and base station 105-b may determine whether a guard band is present or not between two adjacent LBT bandwidths.
  • UE 115-b and base station 105-b may determine a guard band is present between two of the set of LBT bandwidths based on a first LBT bandwidth of the two of the set of LBT bandwidths being idle, having a failed LBT procedure, or a combination thereof.
  • base station 105-b may determine to allocate a guard band between two of the set of LBT bandwidths based on a first LBT bandwidth of the two LBT bandwidths being idle, having a failed LBT procedure, or a combination thereof.
  • UE 115-b may receive, from base station 105-b, an indication of the guard band or an absence of the guard band.
  • UE 115-b may detect a signal on each of two adjacent LBT bandwidths of the set of LBT bandwidths and may identify that a guard band between the two adjacent LBT bandwidths is not present based on the detected signal on each of the two adjacent LBT bandwidths.
  • the signal may include a PDCCH, an SS block (e.g., an SSB) , a PBCH, RMSI, a GC-PDCCH, a PDSCH, or a combination thereof.
  • UE 115-b and base station 105-b may communicate within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • FIG. 7 illustrates an example of a process flow 700 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • process flow 700 may implement aspects of wireless communications systems 100 and/or 200.
  • Process flow 700 may include a base station 105-c and a UE 115-c, which may be examples of base stations 105 and UEs 115, respectively, as described above with reference to FIGs. 1-6.
  • the operations between UE 115-c and base station 105-c may be performed in different orders or at different times. Certain operations may also be left out of the process flow 700, or other operations may be added to the process flow 700. It is to be understood that while UE 115-c and base station 105-c are shown performing a number of the operations of process flow 700, any wireless device may perform the operations shown.
  • UE 115-c and base station 105-c may identify, in a shared radio frequency spectrum, a BWP configured for communications between UE 115-c and base station 105-c.
  • UE 115-c and base station 105-c may identify a set of LBT bandwidths within the BWP.
  • UE 115-c and base station 105-c may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration comprises a period, an offset, or a combination thereof.
  • CORESETs for each of the set of LBT bandwidths may be aligned in time.
  • the offset associated with the CORESET may be different from a frame offset associated with the at least one of the set of LBT bandwidths.
  • UE 115-c may receive, from base station 105-c, the CORESET configurations for each of the set of LBT bandwidths.
  • UE 115-c may monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • base station 105-c may transmit, to UE 115-c, DCI within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • UE 115-c may identify that a CORESET occurs during an idle time of an LBT bandwidth of the set of LBT bandwidths and may refrain from decoding the CORESET based on identifying that the CORESET occurs during the idle time.
  • FIG. 8 shows a block diagram 800 of a device 805 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the device 805 may be an example of aspects of a UE 115 as described herein.
  • the device 805 may include a receiver 810, a UE communications manager 815, and a transmitter 820.
  • the device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an FFP configuration for LBT bandwidths, etc. ) . Information may be passed on to other components of the device 805.
  • the receiver 810 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the receiver 810 may utilize a single antenna or a set of antennas.
  • the UE communications manager 815 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station. Additionally, the UE communications manager 815 may identify a set of LBT bandwidths within the BWP. In some cases, the UE communications manager 815 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof. Subsequently, the UE communications manager 815 may communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the UE communications manager 815 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station. Additionally, the UE communications manager 815 may identify a set of LBT bandwidths within the BWP. In some cases, the UE communications manager 815 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof. Subsequently, the UE communications manager 815 may monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations. The UE communications manager 815 may be an example of aspects of the UE communications manager 1110 described herein.
  • the UE communications manager 815 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the UE communications manager 815, or its sub-components may be executed by a general-purpose processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • the UE communications manager 815 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the UE communications manager 815, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the UE communications manager 815, or its sub-components may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • I/O input/output
  • the transmitter 820 may transmit signals generated by other components of the device 805.
  • the transmitter 820 may be collocated with a receiver 810 in a transceiver module.
  • the transmitter 820 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the transmitter 820 may utilize a single antenna or a set of antennas.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the device 905 may be an example of aspects of a device 805, or a UE 115 as described herein.
  • the device 905 may include a receiver 910, a UE communications manager 915, and a transmitter 950.
  • the device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 910 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an FFP configuration for LBT bandwidths, etc. ) . Information may be passed on to other components of the device 905.
  • the receiver 910 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the receiver 910 may utilize a single antenna or a set of antennas.
  • the UE communications manager 915 may be an example of aspects of the UE communications manager 815 as described herein.
  • the UE communications manager 915 may include a BWP identifier 920, an LBT bandwidths identifier 925, a frame configuration component 930, a COT communicator 935, a CORESET configuration component 940, and a CORESET monitoring component 945.
  • the UE communications manager 915 may be an example of aspects of the UE communications manager 1110 described herein.
  • the BWP identifier 920 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station.
  • the LBT bandwidths identifier 925 may identify a set of LBT bandwidths within the BWP.
  • the frame configuration component 930 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof.
  • the COT communicator 935 may communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the CORESET configuration component 940 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof.
  • the CORESET monitoring component 945 may monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • the transmitter 950 may transmit signals generated by other components of the device 905.
  • the transmitter 950 may be collocated with a receiver 910 in a transceiver module.
  • the transmitter 950 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the transmitter 950 may utilize a single antenna or a set of antennas.
  • FIG. 10 shows a block diagram 1000 of a UE communications manager 1005 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the UE communications manager 1005 may be an example of aspects of a UE communications manager 815, a UE communications manager 915, or a UE communications manager 1110 described herein.
  • the UE communications manager 1005 may include a BWP identifier 1010, an LBT bandwidths identifier 1015, a frame configuration component 1020, a COT communicator 1025, a frame configuration indication receiver 1030, a guard band determination component 1035, a CORESET configuration component 1040, and a CORESET monitoring component 1045.
  • Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the BWP identifier 1010 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station.
  • the LBT bandwidths identifier 1015 may identify a set of LBT bandwidths within the BWP.
  • the frame configuration component 1020 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof.
  • the frame configurations may include a COT and an idle time.
  • the COT communicator 1025 may communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the CORESET configuration component 1040 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof. In some aspects, the CORESET configuration component 1040 may receive, from the base station, the CORESET configurations for each of the set of LBT bandwidths. In some cases, the CORESETs for each of the set of LBT bandwidths may be aligned in time. Additionally or alternatively, for at least one of the set of LBT bandwidths, the offset associated with the CORESET may be different from a frame offset associated with the at least one of the set of LBT bandwidths.
  • the CORESET monitoring component 1045 may monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations. In some aspects, the CORESET monitoring component 1045 may identify that a CORESET occurs during an idle time of an LBT bandwidth of the set of LBT bandwidths and may refrain from decoding the CORESET based on identifying that the CORESET occurs during the idle time.
  • the frame configuration indication receiver 1030 may receive, from the base station, an indication of the frame configurations for each of the set of LBT bandwidths. In some aspects, the frame configuration indication receiver 1030 may determine an offset from a start of a frame of the BWP, a period length, an idle duration, or a combination thereof for each of the set of LBT bandwidths based on the received indication of the frame configurations. Additionally, the frame configuration indication receiver 1030 may receive the indication of the frame configurations via RRC signaling.
  • each of the set of LBT bandwidths may have a same period length and a different offset from the start of the frame of the BWP, each of the set of LBT bandwidths may have a different period length and a same offset from the start of the frame of the BWP, or each of the set of LBT bandwidths may have a different period length and a different offset from the start of the frame of the BWP.
  • the guard band determination component 1035 may determine a guard band is present between two of the set of LBT bandwidths based on a first LBT bandwidth of the two of the set of LBT bandwidths being idle, having a failed LBT procedure, or a combination thereof. In some aspects, the guard band determination component 1035 may receive, from the base station, an indication of the guard band or an absence of the guard band.
  • the guard band determination component 1035 may detect a signal on each of two adjacent LBT bandwidths of the set of LBT bandwidths and may identify that a guard band between the two adjacent LBT bandwidths is not present based on the detected signal on each of the two adjacent LBT bandwidths.
  • the signal may include a PDCCH, an SS block, a PBCH, RMSI, a GC-PDCCH, a PDSCH, or a combination thereof.
  • FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the device 1105 may be an example of or include the components of device 805, device 905, or a UE 115 as described herein.
  • the device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a UE communications manager 1110, an I/O controller 1115, a transceiver 1120, an antenna 1125, memory 1130, and a processor 1140. These components may be in electronic communication via one or more buses (e.g., bus 1145) .
  • buses e.g., bus 1145
  • the UE communications manager 1110 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station. Additionally, the UE communications manager 1110 may identify a set of LBT bandwidths within the BWP. In some cases, the UE communications manager 1110 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof. Subsequently, the UE communications manager 1110 may communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the UE communications manager 1110 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station. Additionally, the UE communications manager 1110 may identify a set of LBT bandwidths within the BWP. In some cases, the UE communications manager 1110 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof. Subsequently, the UE communications manager 1110 may monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • the I/O controller 1115 may manage input and output signals for the device 1105.
  • the I/O controller 1115 may also manage peripherals not integrated into the device 1105.
  • the I/O controller 1115 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1115 may utilize an operating system such as or another known operating system.
  • the I/O controller 1115 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1115 may be implemented as part of a processor.
  • a user may interact with the device 1105 via the I/O controller 1115 or via hardware components controlled by the I/O controller 1115.
  • the transceiver 1120 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1120 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1120 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1125. However, in some cases the device may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1130 may include random-access memory (RAM) and read-only memory (ROM) .
  • the memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1130 may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the processor 1140 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU) , a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1140 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1140.
  • the processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting an FFP configuration for LBT bandwidths) .
  • the code 1135 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1135 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 12 shows a block diagram 1200 of a device 1205 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the device 1205 may be an example of aspects of a base station 105 as described herein.
  • the device 1205 may include a receiver 1210, a base station communications manager 1215, and a transmitter 1220.
  • the device 1205 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an FFP configuration for LBT bandwidths, etc. ) . Information may be passed on to other components of the device 1205.
  • the receiver 1210 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the receiver 1210 may utilize a single antenna or a set of antennas.
  • the base station communications manager 1215 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE. Additionally, the base station communications manager 1215 may identify a set of LBT bandwidths within the BWP. In some cases, the base station communications manager 1215 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof. Subsequently, the base station communications manager 1215 may communicate with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the base station communications manager 1215 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE. Additionally, the base station communications manager 1215 may identify a set of LBT bandwidths within the BWP. In some cases, the base station communications manager 1215 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof. Subsequently, the base station communications manager 1215 may transmit, to the UE, DCI within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations. The base station communications manager 1215 may be an example of aspects of the base station communications manager 1510 described herein.
  • the base station communications manager 1215 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the base station communications manager 1215, or its sub-components may be executed by a general-purpose processor, a DSP, an ASIC, a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • code e.g., software or firmware
  • the functions of the base station communications manager 1215, or its sub-components may be executed by a general-purpose processor, a DSP, an ASIC, a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • the base station communications manager 1215 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the base station communications manager 1215, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the base station communications manager 1215, or its sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • the transmitter 1220 may transmit signals generated by other components of the device 1205.
  • the transmitter 1220 may be collocated with a receiver 1210 in a transceiver module.
  • the transmitter 1220 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the transmitter 1220 may utilize a single antenna or a set of antennas.
  • FIG. 13 shows a block diagram 1300 of a device 1305 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the device 1305 may be an example of aspects of a device 1205, or a base station 105 as described herein.
  • the device 1305 may include a receiver 1310, a base station communications manager 1315, and a transmitter 1350.
  • the device 1305 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1310 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an FFP configuration for LBT bandwidths, etc. ) . Information may be passed on to other components of the device 1305.
  • the receiver 1310 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the receiver 1310 may utilize a single antenna or a set of antennas.
  • the base station communications manager 1315 may be an example of aspects of the base station communications manager 1215 as described herein.
  • the base station communications manager 1315 may include a BWP identification component 1320, an LBT bandwidths identification component 1325, a frame configuration determination component 1330, a frame configuration communication component 1335, a CORESET determination component 1340, and a CORESET transmitter 1345.
  • the base station communications manager 1315 may be an example of aspects of the base station communications manager 1510 described herein.
  • the BWP identification component 1320 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE.
  • the LBT bandwidths identification component 1325 may identify a set of LBT bandwidths within the BWP.
  • the frame configuration determination component 1330 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof.
  • the frame configuration communication component 1335 may communicate with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the CORESET determination component 1340 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof.
  • the CORESET transmitter 1345 may transmit, to the UE, downlink control information within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • the transmitter 1350 may transmit signals generated by other components of the device 1305.
  • the transmitter 1350 may be collocated with a receiver 1310 in a transceiver module.
  • the transmitter 1350 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the transmitter 1350 may utilize a single antenna or a set of antennas.
  • FIG. 14 shows a block diagram 1400 of a base station communications manager 1405 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the base station communications manager 1405 may be an example of aspects of a base station communications manager 1215, a base station communications manager 1315, or a base station communications manager 1510 described herein.
  • the base station communications manager 1405 may include a BWP identification component 1410, an LBT bandwidths identification component 1415, a frame configuration determination component 1420, a frame configuration communication component 1425, a guard band allocation component 1430, a CORESET determination component 1435, and a CORESET transmitter 1440.
  • Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the BWP identification component 1410 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE.
  • the LBT bandwidths identification component 1415 may identify a set of LBT bandwidths within the BWP.
  • the frame configuration determination component 1420 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof. In some aspects, the frame configuration determination component 1420 may determine an offset from a start of a frame of the BWP, a period length, an idle duration, or a combination thereof for each of the set of LBT bandwidths. Additionally, the frame configuration determination component 1420 may transmit an indication of the frame configurations via RRC signaling.
  • each of the set of LBT bandwidths may have a same period length and a different offset from the start of the frame of the BWP, each of the set of LBT bandwidths may have a different period length and a same offset from the start of the frame of the BWP, or each of the set of LBT bandwidths may have a different period length and a different offset from the start of the frame of the BWP.
  • the frame configurations may include a COT and an idle time.
  • the frame configuration communication component 1425 may communicate with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the CORESET determination component 1435 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof. In some aspects, the CORESET determination component 1435 may transmit, to the UE, the CORESET configurations for each of the set of LBT bandwidths. In some cases, the CORESETs for each of the set of LBT bandwidths may be aligned in time.
  • the CORESET transmitter 1440 may transmit, to the UE, downlink control information within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • the guard band allocation component 1430 may determine to allocate a guard band between two of the set of LBT bandwidths based on a first LBT bandwidth of the two LBT bandwidths being idle, having a failed LBT procedure, or a combination thereof. In some aspects, the guard band allocation component 1430 may transmit, to the UE, an indication of the guard band or an absence of the guard band.
  • FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the device 1505 may be an example of or include the components of device 1205, device 1305, or a base station 105 as described herein.
  • the device 1505 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a base station communications manager 1510, a network communications manager 1515, a transceiver 1520, an antenna 1525, memory 1530, a processor 1540, and an inter-station communications manager 1545. These components may be in electronic communication via one or more buses (e.g., bus 1550) .
  • buses e.g., bus 1550
  • the base station communications manager 1510 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE. Additionally, the base station communications manager 1510 may identify a set of LBT bandwidths within the BWP. In some cases, the base station communications manager 1510 may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof. Subsequently, the base station communications manager 1510 may communicate with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the base station communications manager 1510 may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE. Additionally, the base station communications manager 1510 may identify a set of LBT bandwidths within the BWP. In some cases, the base station communications manager 1510 may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof. Subsequently, the base station communications manager 1510 may transmit, to the UE, DCI within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • the network communications manager 1515 may manage communications with the core network (e.g., via one or more wired backhaul links) . In one aspect, the network communications manager 1515 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the transceiver 1520 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1520 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1520 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1525. However, in some cases the device may have more than one antenna 1525, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1530 may include RAM, ROM, or a combination thereof.
  • the memory 1530 may store computer-readable code 1535 including instructions that, when executed by a processor (e.g., the processor 1540) cause the device to perform various functions described herein.
  • a processor e.g., the processor 1540
  • the memory 1530 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1540 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1540 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 1540.
  • the processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1530) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting an FFP configuration for LBT bandwidths) .
  • the inter-station communications manager 1545 may manage communications with other base station 105 and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. In one aspect, the inter-station communications manager 1545 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some aspects, the inter-station communications manager 1545 may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between base stations 105.
  • the code 1535 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1535 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1535 may not be directly executable by the processor 1540 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the operations of method 1600 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1600 may be performed by a UE communications manager as described with reference to FIGs. 8 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station.
  • the operations of 1605 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1605 may be performed by a BWP identifier as described with reference to FIGs. 8 through 11.
  • the UE may identify a set of LBT bandwidths within the BWP.
  • the operations of 1610 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1610 may be performed by an LBT bandwidths identifier as described with reference to FIGs. 8 through 11.
  • the UE may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof.
  • the operations of 1615 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1615 may be performed by a frame configuration component as described with reference to FIGs. 8 through 11.
  • the UE may communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the operations of 1620 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1620 may be performed by a COT communicator as described with reference to FIGs. 8 through 11.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the operations of method 1700 may be implemented by a UE 115 or its components as described herein. In one aspect, the operations of method 1700 may be performed by a UE communications manager as described with reference to FIGs. 8 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station.
  • the operations of 1705 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1705 may be performed by a BWP identifier as described with reference to FIGs. 8 through 11.
  • the UE may identify a set of LBT bandwidths within the BWP.
  • the operations of 1710 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1710 may be performed by an LBT bandwidths identifier as described with reference to FIGs. 8 through 11.
  • the UE may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof.
  • the operations of 1715 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1715 may be performed by a frame configuration component as described with reference to FIGs. 8 through 11.
  • the UE may receive, from the base station, an indication of the frame configurations for each of the set of LBT bandwidths.
  • the operations of 1720 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1720 may be performed by a frame configuration indication receiver as described with reference to FIGs. 8 through 11.
  • the UE may communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the operations of 1725 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1725 may be performed by a COT communicator as described with reference to FIGs. 8 through 11.
  • FIG. 18 shows a flowchart illustrating a method 1800 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the operations of method 1800 may be implemented by a UE 115 or its components as described herein. In one aspect, the operations of method 1800 may be performed by a UE communications manager as described with reference to FIGs. 8 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station.
  • the operations of 1805 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1805 may be performed by a BWP identifier as described with reference to FIGs. 8 through 11.
  • the UE may identify a set of LBT bandwidths within the BWP.
  • the operations of 1810 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1810 may be performed by an LBT bandwidths identifier as described with reference to FIGs. 8 through 11.
  • the UE may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof.
  • the operations of 1815 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1815 may be performed by a frame configuration component as described with reference to FIGs. 8 through 11.
  • the UE may determine a guard band is present between two of the set of LBT bandwidths based on a first LBT bandwidth of the two of the set of LBT bandwidths being idle, having a failed LBT procedure, or a combination thereof.
  • the operations of 1820 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1820 may be performed by a guard band determination component as described with reference to FIGs. 8 through 11.
  • the UE may communicate with the base station within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the operations of 1825 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1825 may be performed by a COT communicator as described with reference to FIGs. 8 through 11.
  • FIG. 19 shows a flowchart illustrating a method 1900 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the operations of method 1900 may be implemented by a UE 115 or its components as described herein. In one aspect, the operations of method 1900 may be performed by a UE communications manager as described with reference to FIGs. 8 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station.
  • the operations of 1905 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1905 may be performed by a BWP identifier as described with reference to FIGs. 8 through 11.
  • the UE may identify a set of LBT bandwidths within the BWP.
  • the operations of 1910 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1910 may be performed by an LBT bandwidths identifier as described with reference to FIGs. 8 through 11.
  • the UE may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof.
  • the operations of 1915 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1915 may be performed by a CORESET configuration component as described with reference to FIGs. 8 through 11.
  • the UE may monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • the operations of 1920 may be performed according to the methods described herein. In some aspects, aspects of the operations of 1920 may be performed by a CORESET monitoring component as described with reference to FIGs. 8 through 11.
  • FIG. 20 shows a flowchart illustrating a method 2000 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the operations of method 2000 may be implemented by a UE 115 or its components as described herein. In one aspect, the operations of method 2000 may be performed by a UE communications manager as described with reference to FIGs. 8 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may identify, in a shared radio frequency spectrum, a BWP configured for communications between the UE and a base station.
  • the operations of 2005 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2005 may be performed by a BWP identifier as described with reference to FIGs. 8 through 11.
  • the UE may identify a set of LBT bandwidths within the BWP.
  • the operations of 2010 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2010 may be performed by an LBT bandwidths identifier as described with reference to FIGs. 8 through 11.
  • the UE may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof.
  • the operations of 2015 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2015 may be performed by a CORESET configuration component as described with reference to FIGs. 8 through 11.
  • the UE may receive, from the base station, the CORESET configurations for each of the set of LBT bandwidths.
  • the operations of 2020 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2020 may be performed by a CORESET configuration component as described with reference to FIGs. 8 through 11.
  • the UE may monitor for a CORESET in one or more of the set of LBT bandwidths based on the CORESET configurations.
  • the operations of 2025 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2025 may be performed by a CORESET monitoring component as described with reference to FIGs. 8 through 11.
  • FIG. 21 shows a flowchart illustrating a method 2100 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the operations of method 2100 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 2100 may be performed by a base station communications manager as described with reference to FIGs. 12 through 15.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE.
  • the operations of 2105 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2105 may be performed by a BWP identification component as described with reference to FIGs. 12 through 15.
  • the base station may identify a set of LBT bandwidths within the BWP.
  • the operations of 2110 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2110 may be performed by an LBT bandwidths identification component as described with reference to FIGs. 12 through 15.
  • the base station may determine frame configurations for each of the set of LBT bandwidths, where each frame configuration includes a frame period, a frame offset, or a combination thereof.
  • the operations of 2115 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2115 may be performed by a frame configuration determination component as described with reference to FIGs. 12 through 15.
  • the base station may communicate with the UE within one or more COTs on one or more of the set of LBT bandwidths based on the frame configurations for the one or more of the set of LBT bandwidths.
  • the operations of 2120 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2120 may be performed by a frame configuration communication component as described with reference to FIGs. 12 through 15.
  • FIG. 22 shows a flowchart illustrating a method 2200 that supports an FFP configuration for LBT bandwidths in accordance with aspects of the present disclosure.
  • the operations of method 2200 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 2200 may be performed by a base station communications manager as described with reference to FIGs. 12 through 15.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may identify, in a shared radio frequency spectrum, a BWP configured for communications between the base station and a UE.
  • the operations of 2205 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2205 may be performed by a BWP identification component as described with reference to FIGs. 12 through 15.
  • the base station may identify a set of LBT bandwidths within the BWP.
  • the operations of 2210 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2210 may be performed by an LBT bandwidths identification component as described with reference to FIGs. 12 through 15.
  • the base station may determine CORESET configurations for each of the set of LBT bandwidths, where each CORESET configuration includes a period, an offset, or a combination thereof.
  • the operations of 2215 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2215 may be performed by a CORESET determination component as described with reference to FIGs. 12 through 15.
  • the base station may transmit, to the UE, downlink control information within a CORESET in one of the set of LBT bandwidths based on the CORESET configurations.
  • the operations of 2220 may be performed according to the methods described herein. In some aspects, aspects of the operations of 2220 may be performed by a CORESET transmitter as described with reference to FIGs. 12 through 15.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. In one aspect, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
  • a list of items indicates an inclusive list such that, in one aspect, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. In one aspect, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs de communication sans fil. Un équipement utilisateur (UE) et une station de base peuvent identifier une partie de bande passante (BWP) pour des communications entre l'UE et la station de base, la BWP comprenant de multiples bandes passantes d'écoute avant de parler (LBT). Par la suite, l'UE et la station de base peuvent déterminer des configurations de trame respectives (par exemple, des décalages, des longueurs de période, etc.) pour chacune des multiples bandes passantes LBT et peut communiquer dans un ou plusieurs intervalles d'occupation de canal des multiples bandes passantes LBT sur la base des configurations de trame. Également ou alternativement, l'UE et la station de base peuvent déterminer un ensemble de configurations de ressources de commande (CORESET) pour chacune des multiples bandes passantes LBT, les configurations CORESET comprenant une période et un décalage pour des CORESET correspondants dans les COT de chacune des multiples bandes passantes LBT. Dans certains cas, des bandes de garde peuvent exister entre deux bandes passantes LBT adjacentes des multiples bandes passantes LBT.
PCT/CN2019/123614 2019-12-06 2019-12-06 Configuration de période de trame fixe pour bande passante d'écoute avant transmission WO2021109115A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/123614 WO2021109115A1 (fr) 2019-12-06 2019-12-06 Configuration de période de trame fixe pour bande passante d'écoute avant transmission

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/123614 WO2021109115A1 (fr) 2019-12-06 2019-12-06 Configuration de période de trame fixe pour bande passante d'écoute avant transmission

Publications (1)

Publication Number Publication Date
WO2021109115A1 true WO2021109115A1 (fr) 2021-06-10

Family

ID=76221083

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/123614 WO2021109115A1 (fr) 2019-12-06 2019-12-06 Configuration de période de trame fixe pour bande passante d'écoute avant transmission

Country Status (1)

Country Link
WO (1) WO2021109115A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022257123A1 (fr) * 2021-06-11 2022-12-15 Qualcomm Incorporated Invalidation de bloc de signal de synchronisation pour un mode d'équipement à base de trame (fbe)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109076597A (zh) * 2018-08-10 2018-12-21 北京小米移动软件有限公司 Fbe的数据传输方法、装置及存储介质
CN109314967A (zh) * 2018-09-06 2019-02-05 北京小米移动软件有限公司 数据传输方法、设备及装置
US20190141742A1 (en) * 2017-11-09 2019-05-09 Hua Zhou Random Access Procedure
CN110100400A (zh) * 2019-03-20 2019-08-06 北京小米移动软件有限公司 信道检测机制的确定方法、装置、设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190141742A1 (en) * 2017-11-09 2019-05-09 Hua Zhou Random Access Procedure
CN109076597A (zh) * 2018-08-10 2018-12-21 北京小米移动软件有限公司 Fbe的数据传输方法、装置及存储介质
CN109314967A (zh) * 2018-09-06 2019-02-05 北京小米移动软件有限公司 数据传输方法、设备及装置
CN110100400A (zh) * 2019-03-20 2019-08-06 北京小米移动软件有限公司 信道检测机制的确定方法、装置、设备及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Frame structure for NR-U", 3GPP DRAFT; R1-1812974 FRAME STRUCTURE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Spokane, USA; 20181112 - 20181116, 11 November 2018 (2018-11-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051554953 *
VIVO: "Discussion on the channel access procedures", 3GPP DRAFT; R1-1910204, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051789009 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022257123A1 (fr) * 2021-06-11 2022-12-15 Qualcomm Incorporated Invalidation de bloc de signal de synchronisation pour un mode d'équipement à base de trame (fbe)

Similar Documents

Publication Publication Date Title
EP3977805B1 (fr) Association de faisceau pendant des procédures d'accès aléatoire
CN110999494A (zh) 使用多个载波的随机接入信道过程
US11224076B2 (en) Random access channel procedure selection scheme
US11284434B2 (en) Inter-cell coordination of random access channel transmission
US11889546B2 (en) Beam refinement techniques for random access communications
US11375539B2 (en) Listen-before-talk for uplink transmissions using multiple subbands
US11825514B2 (en) Repetitive random access transmissions
US11979912B2 (en) Signaling of transmission parameters
US20220408348A1 (en) Early indication of new radio-light dedicated system information
WO2020198980A1 (fr) Préambule au mappage de signaux de référence de démodulation pour procédures d'accès aléatoire
CN115004813A (zh) 用于无线通信系统的跨载波调度技术
WO2021109115A1 (fr) Configuration de période de trame fixe pour bande passante d'écoute avant transmission
US11716766B2 (en) Exposure-dependent random access channel procedure selection
US11882591B2 (en) Two-step random access channel configuration period
WO2021057841A1 (fr) Configuration d'accès aléatoire inter-porteuses
WO2021139523A1 (fr) Transmission de commande d'avance temporelle dans des informations de commande de liaison descendante pour la suspension d'un groupe de cellules secondaires
US20230370240A1 (en) Network indication of full-duplex capability
WO2023184334A1 (fr) Améliorations de réponse pour plusieurs procédures d'accès aléatoire
US20230080801A1 (en) Listen before talk techniques for wireless communications systems
US20220417997A1 (en) Random-access occasion selection for reduced-capability user equipment
WO2021203356A1 (fr) Entrelacement de ressources de commande pour des communications en bande de 6 ghz
WO2022266997A1 (fr) Sélection d'occasion d'accès aléatoire pour équipement utilisateur à capacité réduite
WO2022251067A1 (fr) Techniques de planification pour une transmission de rétroaction de liaison montante

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19954984

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19954984

Country of ref document: EP

Kind code of ref document: A1