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
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W74/00—Wireless channel access
  • H04W74/002—Transmission of channel access control information
  • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/18—Management of setup rejection or failure
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/50—Allocation or scheduling criteria for wireless resources
  • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria

Definitions

• aspects of the present disclosure relate generally to wireless communication and more particularly to techniques for channel congestion measurement.
• Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
• Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (for example, bandwidth, transmit power, etc.).
• multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single -carrier frequency-division multiple access (SC- FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE).
• LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).
• UMTS Universal Mobile Telecommunications System
• a wireless communication network may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs).
• UE user equipment
• a user equipment (UE) may communicate with a base station (BS) via the downlink (DL) and uplink (UL).
• the DL (or forward link) refers to the communication link from the BS to the UE
• the UL (or reverse link) refers to the communication link from the UE to the BS.
• a BS may be referred to as aNodeB, an LTE evolved nodeB (eNB), a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a New Radio (NR) BS, or a 5G NodeB.
• eNB LTE evolved nodeB
• AP access point
• AP access point
• R transmit receive point
• NR New Radio
• NR which also may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP).
• 3GPP Third Generation Partnership Project
• NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDM with a cyclic prefix (CP) (CP-OFDM) on the DF, using CP-OFDM or SC-FDM (for example, also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the UF (or a combination thereof), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
• CP-OFDM OFDM with a cyclic prefix
• SC-FDM for example, also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)
• MIMO multiple-input multiple-output
• the method may include performing a set of listen-before-talk (FBT) procedures to access an unlicensed spectrum; determining an FBT metric associated with a result of the set of FBT procedures; and selectively triggering a recovery procedure based on the FBT metric satisfying an FBT metric threshold.
• FBT listen-before-talk
• selectively triggering the recovery procedure includes at least one of triggering one or more a radio link failure (RTF) related procedures, performing a recovery action, or reporting the FBT metric to a base station (BS).
• the FBT metric is an FBT failure metric.
• determining the FBT metric includes determining that an FBT failure occurs for an FBT procedure of the set of FBT procedures based on a failure to transmit on an uplink transmission instance.
• the uplink transmission instance is at least one of a physical uplink shared channel (PUSCH) transmission, a physical uplink control channel (PUCCH) transmission, or a physical random access channel (PRACH) transmission, or a sounding reference signal (SRS) transmission.
• PUSCH physical uplink shared channel
• PUCCH physical uplink control channel
• PRACH physical random access channel
• SRS sounding reference signal
• the FBT metric is incremented for each failure to transmit on an uplink transmission instance. In some aspects, the FBT metric is incremented based on whether at least one failure to transmit on an uplink transmission instance occurs during a threshold period of time. In some aspects, the FBT metric is incremented based on a ratio of uplink transmission failures to uplink attempts during a threshold period of time. In some aspects, the FBT metric is incremented based on a threshold quantity of uplink transmission failures occurring during a threshold period of time. In some aspects, a threshold period of time associated with identifying an FBT failure associated with the FBT metric is ended and the FBT failure is not determined based on a threshold quantity of successful uplink transmissions occurring during the threshold period of time.
• the LBT metric is incremented based on whether at least one uplink transmission failure occurs during an evaluation period that includes a uplink transmission. In some aspects, the LBT metric is incremented based on a quantity of uplink transmission failures during the evaluation period. In some aspects, the LBT metric is incremented based on whether a quantity of uplink transmission failures during the evaluation period satisfies an uplink transmission failure threshold. In some aspects, an LBT failure associated with the LBT metric is not determined when a quantity of successful uplink transmissions satisfies an uplink transmission threshold during the evaluation period. In some aspects, the LBT metric is incremented based on an occurrence of a scheduled uplink transmission.
• the scheduled uplink transmission includes at least one uplink transmission instance and is at least one of an uplink grant, a PUCCH, or an uplink channel.
• the LBT metric is incremented based on an uplink transmission failure occurring for each uplink transmission instance of the scheduled uplink transmission. In some aspects, the LBT metric is incremented based on whether an uplink transmission failure occurs in an uplink burst or a channel occupancy time. In some aspects, the LBT metric is incremented based on the uplink transmission failure occurring for each uplink transmission instance of the uplink burst or the channel occupancy time.
• the LBT metric is at least one of an absolute metric representing at least one LBT failure in a measurement interval, a ratio metric representing a ratio of LBT failures to occasions during which an LBT failure can occur in the measurement interval, an absolute metric representing a threshold quantity of LBT failures occurring in the measurement interval, or an absolute metric representing a quantity of LBT failures occurring in the measurement interval.
• the measurement interval is at least one of a set of slots, a set of mini-slots, a set of occasions in a single slot, or a set of uplink grants in a channel occupancy time or uplink burst.
• the LBT metric is on a per-LBT type basis.
• the LBT metric includes a first LBT metric for category-4 LBT and a second LBT metric for category-2 LBT.
• the first LBT metric and the second LBT metric are weighted equally for determining whether the LBT metric satisfies the LBT metric threshold.
• selectively triggering the recovery procedure includes triggering the recovery procedure based on the first LBT metric satisfying a first threshold or the second LBT metric satisfying a second threshold.
• a first weight is applied to the first LBT metric and a second weight is applied to the second LBT metric for determining whether the LBT metric satisfies the LBT metric threshold.
• At least one of the first weight or the second weight is determined based on at least one of a ratio of busy slots of a corresponding channel to a total quantity of slots of the corresponding channel, an initial LBT counter value, a congestion window size, or a channel access priority class.
• the LBT metric includes a first LBT metric for outside acquired channel occupancy time (COT) LBT and a second LBT metric for inside acquired COT LBT.
• the LBT metric is sub-band-specific or common to a plurality of sub-bands. In some aspects, the LBT metric is determined based on at least one of an LBT failure on one or more sub-bands, an LBT success on one or more sub-bands, or an LBT failure on a single sub-band. In some aspects, the LBT metric relates to a secondary cell, and selectively triggering the recovery procedure includes transmitting a report to indicate that the LBT metric satisfies the LBT metric threshold for the secondary cell.
• the report includes information identifying at least one of the LBT metric, a measurement report for the secondary cell, a COT metric, or a received signal strength indicator (RSSI) for the secondary cell.
• the LBT metric is at least one of a metric relating to a quantity of LBT failures, a metric relating to a channel busy state as a result of LBT failure, or a metric relating to an amount of data missed as a result of LBT failure.
• the LBT metric relates to a first bandwidth part.
• selectively triggering the recovery procedure includes performing a bandwidth part switch from the first bandwidth part to a second bandwidth part.
• the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part.
• the method may include transmitting, to a serving cell, a reporting message indicating triggering of the bandwidth part switch.
• the reporting message is at least one of a radio resource control (RRC) message, a medium access control (MAC) message, or a physical layer message.
• the reporting message includes information identifying at least one of a bandwidth part switch triggering event, or a quantity of LBT failures.
• the method may include transmitting, to a serving cell, a reporting message after the bandwidth part switch, and the reporting message may be a random access channel (RACH) message.
• RRC radio resource control
• MAC medium access control
• the method may include transmitting, to a serving cell, a reporting message after the bandwidth part switch, and the reporting message may be a random access channel
• the UE may include memory and one or more processors operatively coupled to the memory.
• the memory and the one or more processors may be configured to perform a set of LBT procedures to access an unlicensed spectrum; determine an LBT metric associated with a result of the set of LBT procedures; and selectively trigger a recovery procedure based on the LBT metric satisfying an LBT metric threshold.
• the non-transitory computer-readable medium may store one or more instructions for wireless communication.
• the one or more instructions when executed by one or more processors of a UE, may cause the one or more processors to perform a set of LBT procedures to access an unlicensed spectrum;
• the apparatus may include means for performing a set of LBT procedures to access an unlicensed spectrum; means for determining an LBT metric associated with a result of the set of LBT procedures; and means for selectively triggering a recovery procedure based on the LBT metric satisfying an LBT metric threshold.
• the method may include configuring, for a UE on a first bandwidth part, a second bandwidth part to enable a bandwidth part switch for the UE and in connection with an LBT metric, where the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part; and receiving a reporting message indicating a trigger of the bandwidth part switch by the UE after the LBT metric satisfies a threshold.
• the BS may include memory and one or more processors operatively coupled to the memory.
• the memory and the one or more processors may be configured to configure, for a UE on a first bandwidth part, a second bandwidth part to enable a bandwidth part switch for the UE and in connection with an LBT metric, where the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part; and receive a reporting message indicating a trigger of the bandwidth part switch by the UE after the LBT metric satisfies a threshold.
• the reporting message is at least one of a RRC message, a MAC message, or a physical layer message.
• the reporting message includes information identifying at least one of a bandwidth part switch triggering event, or a quantity of LBT failures.
• the method may include receiving a RACH message after the bandwidth part switch
• the non-transitory computer-readable medium may store one or more instructions for wireless communication.
• the one or more instructions when executed by one or more processors of a BS, may cause the one or more processors to configure, for a UE on a first bandwidth part, a second bandwidth part to enable a bandwidth part switch for the UE and in connection with an LBT metric, where the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part; and receive a reporting message indicating a trigger of the bandwidth part switch by the UE after the LBT metric satisfies a threshold.
• the apparatus may include means for configuring, for a UE on a first bandwidth part, a second bandwidth part to enable a bandwidth part switch for the UE and in connection with an LBT metric, where the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part; and means for receiving a reporting message indicating a trigger of the bandwidth part switch by the UE after the LBT metric satisfies a threshold.
• aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless
• Figure 1 is a block diagram conceptually illustrating an example of a wireless network.
• FIG. 2 is a block diagram conceptually illustrating an example of a base station (BS) in communication with a user equipment (UE) in a wireless network.
• BS base station
• UE user equipment
• Figures 3A-3E are diagrams illustrating examples of channel congestion management.
• Figure 4 is a diagram illustrating an example process performed, for example, by a UE.
• Figure 5 is a diagram illustrating an example process performed, for example, by a BS.
• the described implementations may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards, including any of the IEEE 802.11 standards, the Bluetooth ® standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), lxEV-DO, EV-DO Rev A, EV-DO Rev B, High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE), AMPS
• CDMA code division multiple access
• FDMA frequency division multiple access
• TDMA time division multiple access
• GSM Global System for
• Some wireless communication frequency ranges may be reserved for unlicensed spectrum.
• different operators or technologies may use different portions of the unlicensed spectrum concurrently.
• Multiple operators may deploy, for example NR networks, Wi-Fi networks, or LTE networks, at a single location using the unlicensed spectrum for communication.
• each operator or technology may operate at a common location and use a common set of frequency bands, but remain disassociated from other operators or other technologies.
• a first BS operated by a first operator may not coordinate with a second BS operated by a second operator.
• a single operator may deploy multiple ad-hoc cells without a central entity to coordinate the plurality of the ad-hoc cells.
• a first BS operated by an operator and a second BS operated by the same operator may lack central coordination via a central entity.
• a UE may perform a contention-based access procedure. For example, the UE may perform a listen- before-talk, or listen-before-transmit, (LBT) procedure to obtain access to communication resources.
• the LBT procedure may be a category type 2 LBT procedure (Cat-2 LBT) for fixed duration sensing or a category 4 LBT procedure (Cat-4 LBT) with a variable duration sensing where the variable duration is based on priority class and a back off period when the UE detects interference.
• the UE may experience an LBT failure when the UE fails to transmit an uplink transmission during an uplink transmission instance.
• an interfering node such as another UE
• the interfering node may transmit transmissions that interfere with uplink transmissions of the UE.
• the UE may perform multiple successive LBT procedures.
• a UE may determine an LBT metric based on the LBT failures, such as an absolute quantity of LBT failures, a quantity of LBT failures within a particular measurement period, whether the particular measurement period includes a threshold quantity of LBT failures, a ratio of uplink transmission failures to successful uplink transmissions in connection with an LBT procedure, and other possible types of LBT metrics.
• an LBT metric threshold is satisfied, the UE may trigger a recovery action, such as triggering a radio link failure (RLF)-related action, reporting of the LBT metric to a BS, or a bandwidth part switch.
• RLF radio link failure
• the UE may avoid preemptively triggering the recovery action when an interfering node causes a relatively large quantity of LBT failures within a relatively short period of time.
• the UE may reduce network signaling, relative to performing the recovery action, in a situation where the recovery action is unnecessary as a result of the LBT failures being temporary and localized to the relatively short period of time.
• the UE may enable switching to another bandwidth part with reduced interference, thereby improving network performance and UE performance.
• FIG. 1 is a block diagram conceptually illustrating an example of a wireless network 100.
• the wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network.
• Wireless network 100 may include a number of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities.
• a BS is an entity that communicates with user equipment (UEs) and also may be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB), an access point, or a transmit receive point (TRP).
• Each BS may provide communication coverage for a particular geographic area.
• the term“cell” can refer to a coverage area of a BS, a BS subsystem serving this coverage area, or a combination thereof, depending on the context in which the term is used.
• a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof.
• a macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
• a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
• a femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs having association with the femto cell (for example, UEs in a closed subscriber group (CSG)).
• CSG closed subscriber group
• a BS for a macro cell may be referred to as a macro BS.
• a BS for a pico cell may be referred to as a pico BS.
• a BS for a femto cell may be referred to as a femto BS or a home BS.
• a BS 110a may be a macro BS for a macro cell 102a
• a BS 110b may be a pico BS for a pico cell 102b
• a BS 110c may be a femto BS for a femto cell 102c.
• a BS may support one or multiple (for example, three) cells.
• the terms“eNB”,“base station”, “NR BS”,“gNB”,“TRP”,“AP”,“node B”,“5G NB”, and“cell” may be used interchangeably herein.
• a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS.
• the BSs may be interconnected to one another as well as to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection, a virtual network, or a combination thereof using any suitable transport network.
• Wireless network 100 also may include relay stations.
• a relay station is an entity that can receive a transmission of data from an upstream station (for example, a BS or a UE) and send a transmission of the data to a downstream station (for example, a UE or a BS).
• a relay station also may be a UE that can relay transmissions for other UEs.
• a relay station 1 lOd may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d.
• a relay station also may be referred to as a relay BS, a relay base station, a relay, etc.
• Wireless network 100 may be a heterogeneous network that includes BSs of different types, for example, macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100.
• macro BSs may have a high transmit power level (for example, 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (for example, 0.1 to 2 Watts).
• a network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs. Network controller 130 may communicate with the BSs via a backhaul. The BSs also may communicate with one another, for example, directly or indirectly via a wireless or wireline backhaul.
• UEs 120 may be dispersed throughout wireless network 100, and each UE may be stationary or mobile.
• a UE also may be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc.
• a UE may be a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (for example, smart ring, smart bracelet)), an entertainment device (for example, a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
• PDA personal digital assistant
• WLL wireless local loop
• Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
• MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a base station, another device (for example, remote device), or some other entity.
• a wireless node may provide, for example, connectivity for or to a network (for example, a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
• Some UEs may be considered Intemet-of-Things (IoT) devices or may be implemented as NB-IoT (narrowband internet of things) devices.
• Some UEs may be considered a Customer Premises Equipment (CPE).
• a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components, memory components, similar components, or a combination thereof.
• any number of wireless networks may be deployed in a given geographic area.
• Each wireless network may support a particular RAT and may operate on one or more frequencies.
• a RAT also may be referred to as a radio technology, an air interface, etc.
• a frequency also may be referred to as a carrier, a frequency channel, etc.
• Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
• NR or 5G RAT networks may be deployed.
• access to the air interface may be scheduled, where a scheduling entity (for example, a base station) allocates resources for communication among some or all devices and equipment within the scheduling entity’s service area or cell.
• a scheduling entity for example, a base station
• the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity.
• Base stations are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (for example, one or more other UEs). In this example, the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication.
• a UE may function as a scheduling entity in a peer-to-peer (P2P) network, in a mesh network, or another type of network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
• P2P peer-to-peer
• mesh network UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
• a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
• two or more UEs 120 may communicate directly using one or more side link channels (for example, without using a base station 110 as an intermediary to communicate with one another).
• the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (which may include a vehicle-to- vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or similar protocol), a mesh network, or similar networks, or combinations thereof.
• V2X vehicle-to-everything
• the UE 120 may perform scheduling operations, resource selection operations, as well as other operations described elsewhere herein as being performed by the base station 110.
• FIG. 2 is a block diagram conceptually illustrating an example 200 of a base station 110 in communication with a UE 120.
• the base station 110 and the UE 120 may respectively be one of the base stations and one of the UEs in wireless network 100 of Figure 1.
• Base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.
• a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on channel quality indicators (CQIs) received from the UE, process (for example, encode and modulate) the data for each UE based on the MCS(s) selected for the UE, and provide data symbols for all UEs.
• MCS modulation and coding schemes
• CQIs channel quality indicators
• the transmit processor 220 also may process system information (for example, for semi-static resource partitioning information (SRPI), etc.) and control information (for example, CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols.
• system information for example, for semi-static resource partitioning information (SRPI), etc.
• control information for example, CQI requests, grants, upper layer signaling, etc.
• the transmit processor 220 also may generate reference symbols for reference signals (for example, the cell-specific reference signal (CRS)) and synchronization signals (for example, the primary synchronization signal (PSS) and secondary synchronization signal (SSS)).
• a transmit (TX) multiple-input multiple -output (MIMO) processor 230 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t.
• Each modulator 232 may process a respective output symbol stream (for example, for OFDM, etc.) to obtain an output sample stream.
• Each modulator 232 may further process (for example, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
• T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
• the synchronization signals can be generated with location encoding to convey additional information.
• antennas 252a through 252r may receive the downlink signals from the base station 110 or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.
• Each demodulator 254 may condition (for example, filter, amplify, downconvert, and digitize) a received signal to obtain input samples.
• Each demodulator 254 may further process the input samples (for example, for OFDM, etc.) to obtain received symbols.
• a MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
• a receive processor 258 may process (for example, demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller or processor (controller/processor) 280.
• a channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc.
• RSRP reference signal received power
• RSSI received signal strength indicator
• RSRQ reference signal received quality indicator
• CQI channel quality indicator
• one or more components of the UE 120 may be included in a housing.
• a transmit processor 264 may receive and process data from a data source 262 and control information (for example, for reports including RSRP, RSSI, RSRQ, CQI, etc.) from controller/processor 280. Transmit processor 264 also may generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (for example, for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110.
• control information for example, for reports including RSRP, RSSI, RSRQ, CQI, etc.
• Transmit processor 264 also may generate reference symbols for one or more reference signals.
• the symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (for example, for DFT-s-OFDM, CP-OFDM, etc.), and transmitted
• the uplink signals from the UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
• Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller or processor (i.e., controller/processor) 240.
• the base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244.
• the network controller 130 may include communication unit 294, a controller or processor (i.e.,
• controller/processor 290, and memory 292.
• Controller/processor 240 of the base station 110, controller/processor 280 of the UE 120, or any other component(s) of Figure 2 may perform one or more techniques associated with channel congestion measurement, as described in more detail elsewhere herein.
• controller/processor 240 of the base station 110, controller/processor 280 of the UE 120, or any other component(s) (or combinations of components) of Figure 2 may perform or direct operations of, for example, a process 400 of Figure 4, a process 500 of Figure 5, or other processes as described herein.
• Memories 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively.
• a scheduler 246 may schedule UEs for data transmission on the downlink, the uplink, or a combination thereof.
• the UE 120 may include means for performing a set of listen- before-talk (FBT) procedures to access an unlicensed spectrum, means for determining an FBT metric associated with a result of the set of FBT procedures, means for selectively triggering a recovery procedure based on the FBT metric satisfying an FBT metric threshold, or combinations thereof.
• FBT listen- before-talk
• such means may include one or more components of the UE 120 described in connection with Figure 2.
• the base station 110 may include means for configuring the second bandwidth part to enable the bandwidth part switch for a user equipment (UE) and in connection with a listen-before-talk (FBT) metric, where the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part, means for receiving a reporting message indicating the trigger of the bandwidth part switch by a UE after the FBT metric satisfies a threshold, or combinations thereof.
• such means may include one or more components of the base station 110 described in connection with Figure 2.
• FIGS. 3A-3E are diagrams illustrating examples 300 of channel congestion measurement. As shown in Figure 3A, the examples 300 include a UE 120, one or more BSs 110, and one or more other UEs 120.
• the UE 120 may perform a set of LBT procedures to attempt to access unlicensed spectrum resources of the BSs 110.
• the UE 120 may perform an LBT procedure within a channel occupancy time (COT) or outside of a COT.
• the UE 120 may perform the set of LBT procedures using a set of different frequency bands or using a set of different channel types.
• the UE 120 may perform a first LBT procedure on a first frequency using a physical random access channel (PRACH), a second LBT procedure on a second frequency using a physical uplink control channel (PUCCH), or a third LBT procedure on a third frequency using a physical uplink shared channel (PUSCH).
• PRACH physical random access channel
• PUCCH physical uplink control channel
• PUSCH physical uplink shared channel
• the UE 120 may perform one or more successful LBT procedures. For example, the UE 120 may successfully transmit an uplink communication associated with the LBT procedure and may classify the LBT procedure as a success. Additionally, or alternatively, the UE 120 may unsuccessfully transmit an uplink communication associated with the LBT procedure and may classify the LBT procedure as a failure. In this case, the UE 120 may unsuccessfully transmit the uplink communication based on, for example, another UE 120 performing an LBT procedure to attempt LBT-based access to unlicensed spectrum resources.
• the UE 120 may experience a plurality of failures within a threshold period of time. For example, during a burst set of transmissions, the UE 120 may fail each transmission of the burst set based on another UE 120 acquiring a channel on which the UE 120 is attempting to transmit.
• the UE 120 may determine an LBT metric based on results of the set of LBT procedures. For example, the UE 120 may determine a quantity of LBT failures and increment the LBT metric by the quantity of LBT failures. In this case, the UE 120 may count each instance of an uplink transmission independently for determining an LBT failure. For example, when the UE 120 is not able to transmit on an uplink transmission instance as a result of an LBT failure, the UE 120 may count an LBT failure and increment the LBT metric. In this case, the UE 120 may determine that a transmission is not completed based at least in part on expiration of a failure detection timer, and may increment a counter.
• an uplink transmission instance may include a PUSCH transmission instance, a PUCCH transmission instance, a PRACH transmission instance, or another type of uplink channel transmission instance.
• the UE 120 may count an LBT failure for each PUSCH of the plurality of PUSCHs that the UE 120 fails to transmit.
• the UE 120 may reset a counter of LBT failures. For example, based at least in part on expiration of a failure detection timer (without detection of a failure), reconfiguration of the failure detection timer, or reconfiguration of the counter, UE 120 may reset the counter of LBT failures to an initial value (0).
• the UE 120 may set a timer, such as a prohibit timer, and may determine the LBT metric based on one or more LBT failures or LBT successes within a period of time tracked by the timer.
• a timer may track a set of periods during which uplink transmission instances may occur.
• the UE 120 may determine an LBT failure for the particular period and may increment the LBT metric.
• the UE 120 may determine an LBT success for the particular period and may not increment the LBT metric.
• the UE 120 may start the prohibit timer based on an LBT failure occurring. For example, the UE 120 may start the prohibit timer to determine whether an uplink transmission success occurs within a threshold period of time of an uplink transmission failure. In this case, the UE 120 may stop the prohibit timer after a threshold period of time (and determine that an LBT failure has occurred) or after an uplink transmission success within the threshold period of time (and determine that an LBT success has occurred). In this case, each threshold time period results in the UE 120 determining a single LBT failure or success for an entire time period, rather than a plurality of LBT failures for a plurality of failed uplink transmission instances in the time period.
• the UE 120 may increment the LBT metric based on a quantity of uplink failures during a threshold time period associated with the prohibit timer. For example, the UE 120 may increment the LBT metric by a ratio of uplink transmission failures to total uplink transmission attempts during the threshold time period. Additionally, or alternatively, the UE 120 may increment the LBT metric based on whether a quantity of uplink transmission failures satisfies a threshold. For example, rather than determining an LBT failure when all uplink transmission attempts of a particular time period are failures, the UE 120 may determine an LBT failure when a threshold quantity of uplink transmission attempts are failures.
• the UE 120 may determine an LBT failure for the first time period but may not determine an LBT failure for the third time period. Additionally, or alternatively, the UE 120 may stop the prohibit timer and determine an LBT success based on a threshold quantity of successful uplink transmissions occurring during a threshold period of time, and may determine the LBT metric based on a quantity of LBT successes. In some cases, the prohibit timer may be associated with uplink transmission success periods rather than uplink transmission failure periods.
• the UE 120 may use a set of evaluation periods to determine whether to increment an LBT metric based on an LBT failure.
• the UE 120 may divide a period of time into a set of equal sized evaluation periods and a single LBT result (an LBT failure or an LBT success) may be determined for each evaluation period.
• the UE 120 may determine an LBT failure for periods 1 and 5 (in which unsuccessful uplink transmission occurs and no successful uplink transmission occurs), an LBT success for periods 2 and 3 (in which at least one successful uplink transmission occurs), and no result for period 4 (in which neither a successful nor unsuccessful uplink transmission occurs).
• the evaluation periods may have different sizes or may overlap in time.
• the UE 120 may increment the LBT metric by a fraction of uplink transmission failures to total uplink transmission attempts for each evaluation period. Additionally, or alternatively, the UE 120 may determine an LBT failure for a particular evaluation period when a quantity of uplink transmission failures satisfies a threshold quantity. Additionally, or alternatively, the UE 120 may determine an LBT success for a particular evaluation period when a quantity of uplink transmission successes satisfies a threshold. In some aspects, the UE 120 may determine the LBT failure or success when a minimum quantity of LBT failures or success is observed. Lor example, the UE 120 may forgo incrementing an LBT metric when only a single uplink transmission failure occurs in a single uplink
• the UE 120 may determine the LBT metric based on a scheduled uplink transmission.
• the UE 120 may receive a set of downlink control information (DCIs) including information identifying uplink grants, PUSCH transmission instances, or other uplink channel transmissions.
• DCIs downlink control information
• the UE 120 may determine an LBT failure and increment the LBT metric when the UE 120 is unable to successfully perform an uplink transmission during any instance scheduled by the DCI.
• the UE 120 may determine an LBT failure and increment an LBT metric based on each uplink transmission attempt being a failure.
• the UE 120 may determine an LBT success based on at least one uplink transmission being successful. Additionally, or alternatively, the UE 120 may determine the LBT metric based on other determinations in relation to the scheduled uplink transmission, such as based on a ratio of uplink transmission failures to uplink transmission successes or based on a threshold quantity of uplink transmission failures or uplink transmission successes.
• the UE 120 may determine the LBT metric based on an uplink transmission burst set or COT. Lor example, as shown in Ligure 3E and by reference number 315-4, the UE 120 may attempt to transmit during a plurality of uplink transmission bursts or COTs. In this case, the UE 120 may determine an LBT failure and may increment the LBT metric when each uplink transmission attempt in an uplink transmission burst or COT is a failure. In contrast, the UE 120 may determine an LBT success when at least one uplink transmission attempt in an uplink transmission burst or COT is a success.
• the UE 120 may determine the LBT metric based on other determinations in relation to an uplink burst or COT, such as incrementing the LBT metric by a ratio of uplink transmission failures to uplink transmission successes or determining the LBT metric based on a threshold quantity of uplink transmission failures or uplink transmission successes in an uplink burst or COT.
• the UE 120 may determine the LBT metric based on an uplink transmission start point. For example, the UE 120 may determine an LBT success and increment the LBT metric when the UE 120 is able to successfully perform an uplink transmission at any available uplink transmission start point. Additionally, or alternatively, the UE 120 may increment an LBT metric by a ratio of a quantity of start points at which the UE 120 unsuccessfully attempted to perform an uplink transmission to a total quantity of start points. Additionally, or alternatively, the UE 120 may determine an LBT success and increment the LBT metric when a threshold percentage or quantity of start points are associated with unsuccessful uplink transmission attempts.
• the UE 120 may determine the LBT metric on a slot basis, a mini-slot basis, or an uplink grant basis. For example, the UE 120 may determine an LBT success and increment an LBT metric based on using a plurality of start points within a single slot, a plurality of start points within an uplink grant or uplink burst or a COT, a plurality of slots within an uplink grant or an uplink burst or a COT, or a plurality of uplink grants within an uplink burst or a COT.
• the UE 120 may determine a plurality of different LBT metrics.
• the UE 120 may determine a first LBT metric for category 2 LBT (Cat-2 LBT) based uplink transmission attempts and a second LBT metric for category 4 LBT (Cat-4 LBT) based uplink transmission attempts.
• the UE 120 may determine the first LBT metric for uplink transmission attempts within an acquired COT and the second LBT metric for uplink transmission attempts outside of an acquired COT. Additionally, or alternatively, the UE 120 may determine the first LBT metric for a first sub-band and the second LBT metric for a second sub-band.
• the UE 120 may perform Cat-4 LBT on a primary sub-band of the first sub-band and the second sub-band, and Cat-2 LBT on a secondary sub-band of the first sub-band and the second sub-band. Additionally, or alternatively, the UE 120 may perform Cat- 4 LBT on both the first sub-band and the second sub-band.
• the UE 120 may determine the LBT metric based on a UE capability. For example, when a UE capability of the UE 120 enables transmission on a subset of sub-bands, the UE 120 may determine an LBT success when a Cat-4 LBT or Cat-2 LBT is successful on a first subset of sub-bands and unsuccessful on a second subset of sub bands. In contrast, for a different capability, when the UE 120 is only able to perform uplink transmission when an LBT procedure is successful on each sub-band, the UE 120 may determine an LBT failure if Cat-2 LBT or Cat-4 LBT is unsuccessful on any sub-band. In some aspects, the UE 120 may determine a different LBT metric for each sub-band or a common LBT metric for a plurality of sub-bands.
• the UE 120 may selectively trigger a recovery procedure based on the LBT metric.
• the UE 120 may communicate with the BS 110 to trigger a radio link failure (RLL)-based recovery action, a bandwidth part switch, or another type of recovery action.
• RLL radio link failure
• the UE 120 may determine to trigger the recovery procedure based on the LBT metric satisfying a threshold.
• a threshold an LBT metric representing a quantity of LBT failures may exceed an absolute threshold
• an LBT metric representing a ratio of unsuccessful uplink transmission attempts to uplink transmission opportunities may satisfy a ratio threshold over a threshold period of time, or another type of threshold may be satisfied.
• the UE 120 may determine that a threshold is satisfied based on one or more of a plurality of LBT metrics. Lor example, the UE 120 may determine that an equally weighted combination of a Cat-4 LBT metric and a Cat-2 LBT metric exceeds a combined threshold.
• the UE 120 may determine that a Cat-4 LBT metric satisfies a first threshold or a Cat-2 LBT metric satisfies a second threshold. In this case, the UE 120 may report the Cat-4 LBT metric, the Cat-2 LBT metric, or a combination of the Cat-2 LBT metric and the Cat-4 LBT metric when triggering the recovery procedure. Additionally, or alternatively, the UE 120 may determine that a particular sub-band LBT metric satisfies a threshold, and may trigger the recovery procedure.
• the UE 120 may apply different weights to the Cat-2 LBT metric and the Cat-4 LBT metric when combining the Cat-2 LBT metric and the Cat-4 LBT metric when determining whether a combined threshold is satisfied.
• the UE 120 may apply weights based on a percentage of time each channel for Cat-2 LBT or Cat-4 LBT is sensed to be busy based on uplink transmission failures, an initial LBT counter value, a congestion window size, or a channel access priority class.
• the UE 120 may trigger a bandwidth part switch.
• the UE 120 may switch from a first bandwidth part on which the UE 120 is operating to a second bandwidth part configured by a BS 110, which is a serving cell for the UE 120.
• the UE 120 may switch to a bandwidth part that is not an initial access bandwidth part or a default bandwidth part.
• the UE 120 may switch from a relatively narrow bandwidth initial access bandwidth part to a relatively broad bandwidth different bandwidth part.
• the UE 120 may perform a random access channel (RACH) procedure after a bandwidth part switch (and without indicating the bandwidth part switch to the BS 110 at an earlier time).
• RACH random access channel
• the UE 120 may transmit a message to the BS 110 indicating the bandwidth part switch.
• the UE 120 may transmit a radio resource control (RRC), medium access control (MAC), or physical layer message to indicate the bandwidth part switch.
• RRC radio resource control
• MAC medium access control
• the UE 120 may include information indicating that the bandwidth part switch is based on the LBT metric satisfying a threshold or information identifying a quantity of LBT failures.
• the UE 120 may transmit a message indicating that the LBT metric satisfies a threshold. For example, when the UE 120 determines that the LBT metric is satisfied on a secondary cell rather than on a primary cell, the UE 120 may indicate to the BS 110 that the LBT metric is satisfied and may avoid triggering an RLF-based recovery action. In this case, the UE 120 may indicate that an LBT failure has occurred, may identify the LBT failure metric, may perform a network measurement and provide a measurement report for the secondary cell, or may include other metrics, such as a COT metric or a received signal strength indicator (RSSI).
• RSSI received signal strength indicator
• FIG. 4 is a diagram illustrating an example process 400 performed, for example, by a UE.
• the example process 400 shows where a UE, such as the UE 120, performs operations associated with channel congestion measurement.
• the process 400 may include performing a set of LBT procedures to access an unlicensed spectrum (block 410).
• the UE (using receive processor 258, transmit processor 264, controller/processor 280, or memory 282) may perform a set of LBT procedures to access an unlicensed spectrum.
• the UE may include an interface to perform the set of LBT procedures.
• the process 400 may include determining an LBT metric associated with a result of the set of LBT procedures (block 420).
• the UE using receive processor 258, transmit processor 264, controller/processor 280, or memory 282 may determine an LBT metric associated with a result of the set of LBT procedures.
• the UE may include an interface to determine the LBT metric.
• the process 400 may include selectively triggering a recovery procedure based on the LBT metric satisfying an LBT metric threshold (block 430).
• the UE (using receive processor 258, transmit processor 264, controller/processor 280, or memory 282) may selectively trigger a recovery procedure based on the LBT metric satisfying an LBT metric threshold.
• the UE may include an interface to selectively trigger the recovery procedure.
• the process 400 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
• selectively triggering the recovery procedure includes at least one of triggering one or more a RLF related procedures, performing a recovery action, or reporting the LBT metric to a BS.
• the LBT metric is an LBT failure metric.
• determining the LBT metric includes determining that an LBT failure occurs for an LBT procedure of the set of LBT procedures based on a failure to transmit on an uplink transmission instance.
• the uplink transmission instance is at least one of a PUSCH transmission, a PUCCH transmission, or a PRACH transmission, or a SRS transmission.
• the LBT metric is incremented for each failure to transmit on an uplink transmission instance.
• the LBT metric is incremented based on whether at least one failure to transmit on an uplink transmission instance occurs during a threshold period of time.
• the LBT metric is incremented based on a ratio of uplink transmission failures to uplink attempts during a threshold period of time.
• the LBT metric is incremented based on a threshold quantity of uplink transmission failures occurring during a threshold period of time.
• a threshold period of time associated with identifying an LBT failure associated with the LBT metric is ended and the LBT failure is not determined based on a threshold quantity of successful uplink transmissions occurring during the threshold period of time.
• the LBT metric is incremented based on whether at least one uplink transmission failure occurs during an evaluation period that includes a uplink transmission. [0093] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the LBT metric is incremented based on a quantity of uplink transmission failures during the evaluation period.
• the LBT metric is incremented based on whether a quantity of uplink transmission failures during the evaluation period satisfies an uplink transmission failure threshold.
• an LBT failure associated with the LBT metric is not determined when a quantity of successful uplink transmissions satisfies an uplink transmission threshold during the evaluation period.
• the LBT metric is incremented based on an occurrence of a scheduled uplink transmission.
• the scheduled uplink transmission includes at least one uplink transmission instance and is at least one of an uplink grant, a PUCCH, or an uplink channel.
• the LBT metric is incremented based on an uplink transmission failure occurring for each uplink transmission instance of the scheduled uplink transmission.
• the LBT metric is incremented based on whether an uplink transmission failure occurs in an uplink burst or a channel occupancy time.
• the LBT metric is incremented based on the uplink transmission failure occurring for each uplink transmission instance of the uplink burst or the channel occupancy time.
• the LBT metric is at least one of an absolute metric representing at least one LBT failure in a measurement interval, a ratio metric representing a ratio of LBT failures to occasions during which an LBT failure can occur in the measurement interval, an absolute metric representing a threshold quantity of LBT failures occurring in the measurement interval, or an absolute metric representing a quantity of LBT failures occurring in the measurement interval.
• the measurement interval is at least one of a set of slots, a set of mini-slots, a set of occasions in a single slot, or a set of uplink grants in a channel occupancy time or uplink burst.
• the LBT metric is on a per-LBT type basis.
• the LBT metric includes a first LBT metric for category -4 LBT and a second LBT metric for category-2 LBT.
• the first LBT metric and the second LBT metric are weighted equally for determining whether the LBT metric satisfies the LBT metric threshold.
• selectively triggering the recovery procedure includes triggering the recovery procedure based on the first LBT metric satisfying a first threshold or the second LBT metric satisfying a second threshold.
• a first weight is applied to the first LBT metric and a second weight is applied to the second LBT metric for determining whether the LBT metric satisfies the LBT metric threshold.
• at least one of the first weight or the second weight is determined based on at least one of a ratio of busy slots of a corresponding channel to a total quantity of slots of the corresponding channel, an initial LBT counter value, a congestion window size, or a channel access priority class.
• the LBT metric includes a first LBT metric for outside acquired COT LBT and a second LBT metric for inside acquired COT LBT.
• the LBT metric is sub-band-specific or common to a plurality of sub-bands.
• the LBT metric is determined based on at least one of an LBT failure on one or more sub-bands, an LBT success on one or more sub-bands, or an LBT failure on a single sub-band.
• the LBT metric relates to a secondary cell, and selectively triggering the recovery procedure includes transmitting a report to indicate that the LBT metric satisfies the LBT metric threshold for the secondary cell.
• the report includes information identifying at least one of the LBT metric, a measurement report for the secondary cell, a COT metric, or a RSSI for the secondary cell.
• the LBT metric is at least one of a metric relating to a quantity of LBT failures, a metric relating to a channel busy state as a result of LBT failure, or a metric relating to an amount of data missed as a result of LBT failure.
• the LBT metric relates to a first bandwidth part.
• selectively triggering the recovery procedure includes performing a bandwidth part switch from the first bandwidth part to a second bandwidth part.
• the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part.
• the process 400 may include transmitting, to a serving cell, a reporting message indicating triggering of the bandwidth part switch.
• the reporting message is at least one of a RRC message, a MAC message, or a physical layer message.
• the reporting message includes information identifying at least one of a bandwidth part switch triggering event, or a quantity of LBT failures.
• the process 400 may include transmitting, to a serving cell, a reporting message after the bandwidth part switch, and the reporting message may be a RACH message.
• Figure 4 shows example blocks of the process 400
• the process 400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 4. Additionally, or alternatively, two or more of the blocks of the process 400 may be performed in parallel.
• FIG. 5 is a diagram illustrating an example process 500 performed, for example, by a BS.
• the example process 500 shows where a BS, such as the BS 110, performs operations associated with channel congestion measurement.
• the process 500 may include configuring, for a UE on a first bandwidth part, a second bandwidth part to enable a bandwidth part switch for the UE and in connection with an LBT metric, where the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part (block 510).
• the BS (using transmit processor 220, receive processor 238, controller/processor 240, or memory 242) may configure, for a UE on a first bandwidth part, a second bandwidth part to enable a bandwidth part switch for the UE and in connection with an LBT metric.
• the second bandwidth part is different from an initial access bandwidth part or a default bandwidth part.
• the BS may include an interface to configure the second bandwidth part.
• the process 500 may include receiving a reporting message indicating a trigger of the bandwidth part switch by a UE after the LBT metric satisfies a threshold (block 520).
• the BS (using transmit processor 220, receive processor 238, controller/processor 240, or memory 242) may receive a reporting message indicating a trigger of the bandwidth part switch by a UE after the LBT metric satisfies a threshold.
• the BS may include an interface to receive the reporting message.
• the process 500 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
• the reporting message is at least one of a RRC message, a MAC message, or a physical layer message.
• the reporting message includes information identifying at least one of a bandwidth part switch triggering event, or a quantity of LBT failures.
• the process 500 may include receiving a RACH message after the bandwidth part switch.
• Figure 5 shows example blocks of the process 500
• the process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 5. Additionally, or alternatively, two or more of the blocks of the process 500 may be performed in parallel.
• the term“component” is intended to be broadly construed as hardware, firmware, or a combination of hardware and software.
• a processor is implemented in hardware, firmware, or a combination of hardware and software.
• the phrase“based on” is intended to be broadly construed to mean“based at least in part [00130]
• satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold.
• a phrase referring to“at least one of’ a list of items refers to any combination of those items, including single members.
• “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c.
• the hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi -chip 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 herein.
• a general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine.
• a processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
• particular processes and methods may be performed by circuitry that is specific to a given function.
• the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents thereof, or in any combination thereof.
• aspects of the subject matter described in this specification also can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a computer storage media for execution by, or to control the operation of, data processing apparatus.
• Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program from one place to another.
• a storage media may be any available media that may be accessed by a computer.
• such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer.
• Disk and disc includes compact disc (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 should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine readable medium and computer-readable medium, which may be incorporated into a computer program product.

Landscapes

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

Priority Applications (8)

Applications Claiming Priority (4)

Publications (1)

Family

ID=73017067

Family Applications (1)

Country Status (11)

Cited By (2)

Families Citing this family (11)

Family Cites Families (34)

• 2020
  • 2020-02-18 US US16/793,853 patent/US11497054B2/en active Active
  • 2020-03-13 JP JP2021564338A patent/JP7619962B2/ja active Active
  • 2020-03-13 TW TW109108365A patent/TWI831942B/zh active
  • 2020-03-13 EP EP20718048.0A patent/EP3963922B1/en active Active
  • 2020-03-13 KR KR1020217034587A patent/KR102586731B1/ko active Active
  • 2020-03-13 BR BR112021021045A patent/BR112021021045A2/pt unknown
  • 2020-03-13 AU AU2020267110A patent/AU2020267110B2/en active Active
  • 2020-03-13 PH PH1/2021/552398A patent/PH12021552398A1/en unknown
  • 2020-03-13 SG SG11202110455YA patent/SG11202110455YA/en unknown
  • 2020-03-13 CN CN202080030344.0A patent/CN113767659B/zh active Active
  • 2020-03-13 WO PCT/US2020/022643 patent/WO2020222919A1/en not_active Ceased

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events