WO2021159286A1

WO2021159286A1 - Cross-bwp frequency hopping

Info

Publication number: WO2021159286A1
Application number: PCT/CN2020/074796
Authority: WO
Inventors: Jing Dai; Chao Wei; Min Huang
Original assignee: Qualcomm Incorporated
Priority date: 2020-02-12
Filing date: 2020-02-12
Publication date: 2021-08-19

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; receive a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and communicate according to the resource allocation. Numerous other aspects are provided.

Description

CROSS-BWP FREQUENCY HOPPING

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for cross-bandwidth part (BWP) frequency hopping.

BACKGROUND

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 (e.g., bandwidth, transmit power, and/or the like) . Examples of such 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 (3GPP) .

A wireless communication network may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs) . A user equipment (UE) may communicate with a base station (BS) via the downlink and uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, a gNB, an access point (AP) , a radio head, a transmit receive point (TRP) , a New Radio (NR) BS, a 5G Node B, and/or the like.

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate on a municipal, national, regional, and even global level. New Radio (NR) , which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP) . 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 orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL) , using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink (UL) , as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

SUMMARY

In some aspects, a method of wireless communication, performed by a user equipment (UE) , may include receiving a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; receiving a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping (FH) indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and communicating according to the resource allocation.

In some aspects, a method of wireless communication, performed by a base station (BS) , may include transmitting, to a UE, a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and transmitting, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.

In some aspects, a UE for wireless communication 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 receive a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; receive a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and communicate according to the resource allocation.

In some aspects, a base station for wireless communication 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 transmit, to a UE, a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and transmit, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.

In some aspects, a 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: receive a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; receive a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and communicate according to the resource allocation.

In some aspects, a 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: transmit, to a UE, a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and transmit, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.

In some aspects, an apparatus for wireless communication may include means for receiving a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; means for receiving a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and means for communicating according to the resource allocation.

In some aspects, an apparatus for wireless communication may include means for transmitting, to a UE, a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and means for transmitting, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a block diagram conceptually illustrating an example of a wireless communication network, in accordance with various aspects of the present disclosure.

Fig. 2 is a block diagram conceptually illustrating an example of a base station in communication with a UE in a wireless communication network, in accordance with various aspects of the present disclosure.

Fig. 3 is a diagram illustrating an example of frequency hopping, in accordance with various aspects of the present disclosure.

Figs. 4 and 5 are diagrams illustrating examples of cross-bandwidth part frequency hopping, in accordance with various aspects of the present disclosure.

Fig. 6 is a diagram illustrating an example process performed, for example, by a user equipment, in accordance with various aspects of the present disclosure.

Fig. 7 is a diagram illustrating an example process performed, for example, by a base station, in accordance with various aspects of the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

It should be noted that while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.

Fig. 1 is a diagram illustrating a wireless network 100 in which aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include a number of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with user equipment (UEs) and may also be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB) , an access point, a transmit receive point (TRP) , and/or the like. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, 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, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., 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 (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG) ) . 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. In the example shown in Fig. 1, 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, and a BS 110c may be a femto BS for a femto cell 102c. A BS may support one or multiple (e.g., three) cells. The terms “eNB” , “base station” , “NR BS” , “gNB” , “TRP” , “AP” , “node B” , “5G NB” , and “cell” may be used interchangeably herein.

In some aspects, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some aspects, the BSs may be interconnected to one another and/or 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, and/or the like using any suitable transport network.

Wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS) . A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in Fig. 1, a relay station 110d may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, and/or the like.

Wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 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 may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.

UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like. A UE may be a cellular phone (e.g., 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 (e.g., smart ring, smart bracelet) ) , an entertainment device (e.g., 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.

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, and/or the like, that may communicate with a base station, another device (e.g., remote device) , or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE) . UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, and/or the like.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, and/or the like. A frequency may also be referred to as a carrier, a frequency channel, and/or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another) . For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like) , a mesh network, and/or the like. In this case, the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.

As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

Fig. 2 shows a block diagram of a design 200 of base station 110 and UE 120, which may be one of the base stations and one of the UEs in Fig. 1. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T ≥ 1 and R ≥ 1.

At base station 110, 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 at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS (s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS) ) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS) ) . A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/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 (e.g., for OFDM and/or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., 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. According to various aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information.

At UE 120, antennas 252a through 252r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM and/or the like) 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 (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a 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) , and/or the like. In some aspects, one or more components of UE 120 may be included in a housing.

On the uplink, at UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from controller/processor 280. Transmit processor 264 may also 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 (e.g., for DFT-s-OFDM, CP-OFDM, and/or the like) , and transmitted to base station 110. At base station 110, the uplink signals from 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 UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240. Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244. Network controller 130 may include communication unit 294, controller/processor 290, and memory 292.

Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with cross-bandwidth part (BWP) frequency hopping (FH) , as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 600 of Fig. 6, process 700 of Fig. 7, and/or other processes as described herein.

Memories

242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station 110 and/or the UE 120, may perform or direct operations of, for example, process 600 of Fig. 6, process 700 of Fig. 7, and/or other processes as described herein. A scheduler 246 may schedule UEs for data transmission on the downlink and/or uplink.

In some aspects, UE 120 may include means for receiving a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BW, means for receiving a resource allocation for a communication, wherein the resource allocation includes a cross-BWP FH indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP, means for communicating according to the resource allocation, and/or the like. In some aspects, such means may include one or more components of UE 120 described in connection with Fig. 2, such as controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and/or the like.

In some aspects, base station 110 may include means for transmitting, to a UE, a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP, means for transmitting, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP FH indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP, and/or the like. In some aspects, such means may include one or more components of base station 110 described in connection with Fig. 2, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and/or the like.

As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

Fig. 3 is a diagram illustrating an example 300 of frequency hopping, in accordance with various aspects of the present disclosure.

As shown, a UE (e.g., UE 120 shown in Fig. 1) may communicate on a currently active downlink (DL) BWP (referred to as a “source” DL BWP) 305. Downlink control information (DCI) 310 may be carried in a physical downlink control channel (PDCCH) 315, which may occupy one or more of the first three symbols of the slot in which it is transmitted. As shown by reference number 320, the DCI 310 may schedule a physical downlink shared channel (PDSCH) communication 325 to trigger a dynamic BWP switch to a target BWP 330. In some aspects, the BWP switch may be configured by including a target BWP identifier (ID) in a BWP ID field of the DCI. Similarly, a PDCCH may carry another kind of DCI for scheduling an UL BWP switch for a physical uplink shared channel (PUSCH) communication.

As shown, the resource allocation is in the target BWP 330. Frequency hopping (FH) may be supported within the target BWP 330. As shown, the PDSCH communication 325 may hop, within the target DL BWP 330 between a first frequency domain resource allocation 335 and a second frequency domain allocation 340. The hop may occur after each slot, as shown, and may be triggered to begin after an RF retuning gap 345, during which the UE retunes to the target DL BWP 330. The retuning gap 345 may be disposed within a slot before the starting slot of the scheduled communication. In some cases, the UE is not able to transmit or receive any signals during a BWP switch delay.

Frequency hopping (FH) technology has been developed for new radio (NR) primarily for premium UEs such as those configured for enhanced mobile broadband (eMBB) , and other similarly-capable technologies such as ultra reliable low latency communications (URLLC) , broadcasting and multicasting in vehicle to everything (V2X) communications, and/or the like. Due to the capability of the UEs, NR specifications restrict UEs from transmitting PUSCH or PUCCH outside of an active ( “source” ) uplink (UL) BWP and from receiving PDSCH outside an active ( “source” ) downlink (DL) BWP. PUSCH and PUCCH with FH is limited to occur within an active BWP.

In use cases involving reduced capability UEs (referred to as “NR-light” UEs) , many capabilities are not efficient or cost-effective. NR-light devices may include, for example, wearables (e.g., smart watches, and/or the like) , industrial wireless sensor networks (IWSNs) , surveillance cameras, and/or the like. In NR-light use cases, throughput, latency, and reliability requirements may be relaxed to achieve greater efficiency (e.g., with respect to power consumption, system overhead, and/or the like) and cost improvements.

NR-light UEs may have a single receiving antenna. Additionally, or alternatively, one of the reduced capabilities for NR-light UEs is a reduced maximum bandwidth (BW) support. NR has been developed with the requirement that UEs support maximal channel BWs defined for the band. NR-light UEs may have a smaller bandwidth capability such as, for example, 10 or 20 MHz in Frequency Range 1 (FR1) . For an NR-light UE with a reduced maximum BW, intra-BWP UL FH may have limited diversity gain. For DL, having a single antenna may cause diversity loss.

In some aspects, cross-BWP FH techniques described herein may enable an NR-light UE (and/or a premium NR UE) to increase diversity, thereby compensating for the loss of diversity due to reduced maximum BW capability, having a single receiving antenna, and/or the like. In some aspects, the cross-BWP FH techniques include slot bundling in which successive slots are bundled for each BWP hop to reduce RF retuning and improve channel estimation and phase tracking. Signaling for cross-BWP FH techniques described herein may be provided within DCI, thereby minimizing overhead in implementing aspects of the techniques described herein.

As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with respect to Fig. 3.

Fig. 4 is a diagram illustrating an example 400 of cross-BWP frequency hopping, in accordance with various aspects of the present disclosure. As shown in Fig. 4, a BS 110 and a UE 120 may communicate with one another.

As shown by reference number 405, the BS 110 may transmit, and the UE 120 may receive, a configuration message indicating a companion BWP 410 of a source BWP 415. The configuration message may indicate a companion BWP ID corresponding to the companion BWP 410, where the companion BWP ID is different than a source BWP ID corresponding to the source BWP 415. In some aspects, the configuration message may be a radio resource control (RRC) message.

In some aspects, a set of configuration parameters associated with the source BWP 415 may be identical to a set of configuration parameters associated with the companion BWP 410. The set of configuration parameters may indicate a subcarrier spacing (SCS) , a cyclic prefix (CP) , a bandwidth (BW) , and/or the like. In some aspects, a time-domain resource allocation configuration associated with the source BWP 415 is identical to a time-domain resource allocation configuration associated with the companion BWP 410. The time-domain resource allocation configuration may include a slot offset, a start and length indicator value (SLIV) indicating a symbol location within a slot, and/or the like.

As shown by reference number 420, the BS 110 may transmit, and the UE 120 may receive, a resource allocation for a communication. The resource allocation may include a cross-BWP FH indication. The cross-BWP FH indication may indicate that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP 415 and at least one hop corresponding to the companion BWP 410. In some aspects, the resource allocation may indicate a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop and a second half of the plurality of slots corresponding to a second hop. The first hop may correspond to the source BWP 415 or the companion BWP 410 and the second hop may correspond to the other of the source BWP 415 or the companion BWP 410.

As shown in Fig. 4, the cross-BWP FH indication may be carried in downlink control information (DCI) 425. In some aspects, the cross-BWP FH indication may be indicated by a companion BWP ID 430 in a BWP ID field 435 of the DCI 425. In some aspects, the cross-BWP FH may be indicated by an indication of a physical uplink control channel (PUCCH) resource for hybrid automatic repeat request (HARQ) feedback. The indication of the PUCCH resource may be included in DCI for scheduling a physical downlink shared channel (PDSCH) . In some aspects, the cross-BWP FH indication may be transmitted, via a physical downlink control channel (PDCCH) occasion, in one or more symbols of a slot. The one or more symbols may include at least one symbol that is not one of three starting symbols of the slot.

As shown by reference number 440, the UE 120 may communicate according to the resource allocation. The communication may include a downlink communication on a PDSCH or an uplink communication on a physical uplink shared channel (PUSCH) .

In some aspects, cross-BWP FH techniques described herein may enable an NR-light UE (and/or a premium NR UE) to increase diversity. In some aspects, the cross-BWP FH techniques include slot bundling in which successive slots are bundled for each BWP hop to reduce RF retuning and improve channel estimation and phase tracking. Signaling for cross-BWP FH techniques described herein may be provided within DCI, thereby minimizing overhead in implementing aspects of the techniques described herein.

As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.

Fig. 5 is a diagram illustrating an example 500 of cross-BWP frequency hopping, in accordance with various aspects of the present disclosure. As shown in Fig. 5, a BS 110 and a UE 120 may communicate with one another.

As shown by reference number 505, the BS 110 may transmit, and the UE 120 may receive, a configuration message indicating a companion BWP ID (shown as “comp. BWP ID” ) corresponding to a companion BWP of a source BWP, where the companion BWP ID is different than a source BWP ID corresponding to the source BWP. In some aspects, the configuration message may be an RRC message. The companion BWP and the source BWP may be similarly configured, as explained above in connection with Fig. 4.

As shown by reference number 510, the BS 110 may transmit, and the UE 120 may receive, a resource allocation for a communication. The resource allocation may include a cross-BWP FH indication. As shown, the cross-BWP FH indication may be carried in DCI 515 and may be indicated by a companion BWP ID 520 (shown as “comp. BWP ID” ) in a BWP ID field 525 of the DCI 515.

The cross-BWP FH indication may indicate a configured FH pattern of a plurality of FH patterns. In some aspects, as shown in Fig. 5, the resource allocation may indicate a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop 530 and a second half of the plurality of slots corresponding to a second hop 535. The plurality of FH patterns may include a first FH pattern 540 in which the first hop 530 corresponds to the source BWP 545 and the second hop corresponds to the companion BWP 550. The plurality of FH patterns may include a second FH pattern 555 in which the first hop 530 corresponds to the companion BWP 550 and the second hop 535 corresponds to the source BWP 545.

As shown in Fig. 5, the configured FH pattern may be indicated, in DCI 515, by a joint coding of the BWP ID field 525 and a FH flag bit 560. In some aspects, the first FH pattern 540 may be indicated by a combination of a BWP ID field 525 value equal to the companion BWP ID 520 and a first FH flag bit 560 value. The first FH flag bit 560 value may be “0. ” The second FH pattern 555 may be indicated by a combination of a BWP ID field 525 value equal to the companion BWP ID 520 and a second FH flag bit 560 value. The second FH flag bit 560 value may be “1. ”

In some aspects, the FH flag bit 560 may be a virtual-resource-block-to-physical-resource-block (VRB-to-PRB) mapping bit of a DCI for scheduling a PDSCH. In some aspects, the configured FH pattern may be indicated by a value of a starting slot index of a scheduled multi-slot communication. An even value of the starting slot index may indicate the first FH pattern 540 and an odd value of the starting slot index may indicate the second FH pattern 555.

As shown by reference number 565, the UE 120 may communicate according to the resource allocation. The communication may include a downlink communication on a PDSCH and/or an uplink communication on a PUSCH. As is further shown in Fig. 5, an RF retuning gap 570 between each hop may occupy a portion of the first slot in which the next hop occurs.

In some aspects, the configured FH pattern may be the first FH pattern 540 and the UE 120 may transmit and/or receive at least one signal during a period of time between an end of a PDCCH communication carrying the cross-BWP FH indication and a start of a scheduled shared channel communication (e.g., a PDSCH communication, a PUSCH communication, and/or the like) . In some aspects, the configured FH pattern may be the second FH pattern 555 and the UE may transmit and/or receive at least one signal during a period of time between an end of a PDCCH communication carrying the cross-BWP FH indication and a start of a starting slot of a shared channel communication scheduled by the PDCCH communication (e.g., a PDSCH communication, a PUSCH communication, and/or the like) .

In some aspects, cross-BWP FH techniques described herein may enable an NR-light UE (and/or a premium NR UE) to increase diversity. In some aspects, the cross-BWP FH techniques include slot bundling in which successive slots are bundled for each BWP hop to reduce RF retuning and improve channel estimation and phase tracking. Signaling for cross-BWP FH techniques, including FH pattern selection, described herein may be provided within DCI, thereby minimizing overhead in implementing aspects of the techniques described herein.

As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 600 is an example where the UE (e.g., UE 120 and/or the like) performs operations associated with cross-BWP frequency hopping.

As shown in Fig. 6, in some aspects, process 600 may include receiving a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP (block 610) . For example, the UE (e.g., using receive processor 258, controller/processor 280, memory 282, and/or the like) may receive a configuration message indicating a companion BWP of a source BWP, as described above. In some aspects, the configuration message indicates a companion BWP ID corresponding to the companion BWP. In some aspects, the companion BWP ID is different than a source BWP ID corresponding to the source BWP.

As further shown in Fig. 6, in some aspects, process 600 may include receiving a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping (FH) indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP (block 620) . For example, the UE (e.g., using receive processor 258, controller/processor 280, memory 282, and/or the like) may receive a resource allocation for a communication, as described above. In some aspects, the resource allocation includes a cross-BWP FH indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP.

As further shown in Fig. 6, in some aspects, process 600 may include communicating according to the resource allocation (block 630) . For example, the UE (e.g., using receive processor 258, transmit processor 264, controller/processor 280, memory 282, and/or the like) may communicate according to the resource allocation, as described above.

Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the communication comprises at least one of a downlink communication on a PDSCH or an uplink communication on a PUSCH.

In a second aspect, alone or in combination with the first aspect, the cross-BWP FH indication is carried in DCI.

In a third aspect, alone or in combination with one or more of the first and second aspects, the cross-BWP FH indication is indicated by a companion BWP ID in a BWP ID field of the DCI.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the cross-BWP FH is indicated by an indication of a PUCCH resource for HARQ feedback, and the indication of the PUCCH resource is included in DCI for scheduling a PDSCH.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the cross-BWP FH indication is transmitted, via a PDCCH occasion, in one or more symbols of a slot, the one or more symbols comprising at least one symbol that is not one of three starting symbols of the slot.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the configuration message comprises an RRC message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a set of configuration parameters associated with the source BWP is identical to a set of configuration parameters associated with the companion BWP, the set of configuration parameters associated with the source BWP indicating at least one of: an SCS, a CP, a BW, or a combination thereof.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a time-domain resource allocation configuration associated with the source BWP is identical to a time-domain resource allocation configuration associated with the companion BWP.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the time-domain resource allocation configuration of the source BWP comprises at least one of a slot offset, a start and length indicator value (SLIV) indicating a symbol location within a slot, or a combination thereof.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the resource allocation indicates a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop and a second half of the plurality of slots corresponding to a second hop, the first hop corresponds to the source BWP or the companion BWP, and the second hop corresponds to the other of the source BWP or the companion BWP.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the cross-BWP FH indication further indicates a configured FH pattern of a plurality of FH patterns.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the resource allocation indicates a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop and a second half of the plurality of slots corresponding to a second hop, and the plurality of FH patterns comprises: a first FH pattern in which the first hop corresponds to the source BWP and the second hop corresponds to the companion BWP; and a second FH pattern in which the first hop corresponds to the companion BWP and the second hop corresponds to the source BWP.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the configured FH pattern is indicated, in DCI, by a joint coding of a BWP ID field and a FH flag bit.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the first FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and a first FH flag bit value; or the second FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and a second FH flag bit value.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the first FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and an FH flag bit value; or the second FH pattern is indicated by a combination of a BWP ID field value equal to the source BWP ID and the FH flag bit value.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the FH flag bit is a virtual-resource-block-to-physical-resource-block (VRB-to-PRB) mapping bit for scheduling a PDSCH.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the configured FH pattern is indicated by a value of a starting slot index of a scheduled multi-slot communication.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, an even value of the starting slot index indicates the first FH pattern and an odd value of the starting slot index indicates the second FH pattern.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the configured FH pattern is the first FH pattern, the method further comprising transmitting and/or receiving at least one signal during a period of time between an end of a PDCCH communication carrying the cross-BWP FH indication and a start of a scheduled shared channel communication, the scheduled shared channel communication comprising at least one of a PDSCH and a PUSCH.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the configured FH pattern is the second FH pattern, the method further comprising transmitting and/or receiving at least one signal during a period of time between an end of a PDCCH communication carrying the cross-BWP FH indication and a start of a starting slot of a shared channel communication scheduled by the PDCCH communication, the scheduled shared channel communication comprising at least one of a PDSCH and a physical uplink shared channel PUSCH.

Although Fig. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a BS, in accordance with various aspects of the present disclosure. Example process 700 is an example where the BS (e.g., BS 110 and/or the like) performs operations associated with cross-BWP frequency hopping.

As shown in Fig. 7, in some aspects, process 700 may include transmitting, to a UE, a configuration message indicating a companion BWP of a source BWP, wherein the configuration message indicates a companion BWP ID corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP (block 710) . For example, the BS (e.g., using transmit processor 220, controller/processor 240, memory 242, and/or the like) may transmit, to a UE, a configuration message indicating a companion BWP of a source BWP, as described above. In some aspects, the configuration message indicates a companion BWP ID corresponding to the companion BWP. In some aspects, the companion BWP ID is different than a source BWP ID corresponding to the source BWP.

As further shown in Fig. 7, in some aspects, process 700 may include transmitting, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping (FH) indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP (block 720) . For example, the BS (e.g., using transmit processor 220, controller/processor 240, memory 242, and/or the like) may transmit, to the UE, a resource allocation for a communication, as described above. In some aspects, the resource allocation includes a cross-BWP FH indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.

Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the communication comprises at least one of a downlink communication on a PDSCH, or an uplink communication on a PUSCH.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the time-domain resource allocation configuration of the source BWP comprises at least one of a slot offset, a SLIV indicating a symbol location within a slot, or a combination thereof.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the configured FH pattern is indicated, in DCI) by a joint coding of a BWP ID field and a FH flag bit.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the FH flag bit is a VRB-to-PRB mapping bit for scheduling a PDSCH.

Although Fig. 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and/or a combination of hardware and software.

As used herein, 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, not equal to the threshold, and/or the like.

It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code-it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “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, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like) , and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

Claims

A method of wireless communication performed by a user equipment (UE) , comprising:

receiving a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP;

receiving a resource allocation for a communication, wherein the resource allocation includes a cross-bandwidth part (BWP) frequency hopping (FH) indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and

communicating according to the resource allocation.
The method of claim 1, wherein the communication comprises at least one of a downlink communication on a physical downlink shared channel (PDSCH) , or an uplink communication on a physical uplink shared channel (PUSCH) .
The method of claim 1, wherein the cross-BWP FH indication is carried in downlink control information (DCI) .
The method of claim 3, wherein the cross-BWP FH indication is indicated by a companion BWP identifier (ID) in a BWP ID field of the DCI.
The method of claim 1, wherein the cross-BWP FH is indicated by an indication of a physical uplink control channel (PUCCH) resource for hybrid automatic repeat request (HARQ) feedback, and wherein the indication of the PUCCH resource is included in downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) .
The method of claim 1, wherein the cross-BWP FH indication is transmitted, via a physical downlink control channel (PDCCH) occasion, in one or more symbols of a slot, the one or more symbols comprising at least one symbol that is not one of three starting symbols of the slot.
The method of claim 1, wherein the configuration message comprises a radio resource control (RRC) message.
The method of claim 1, wherein a set of configuration parameters associated with the source BWP is identical to a set of configuration parameters associated with the companion BWP, the set of configuration parameters associated with the source BWP indicating at least one of:

a subcarrier spacing (SCS) ,

a cyclic prefix (CP) ,

a bandwidth (BW) , or

a combination thereof.
The method of claim 1, wherein a time-domain resource allocation configuration associated with the source BWP is identical to a time-domain resource allocation configuration associated with the companion BWP.
The method of claim 1, wherein the time-domain resource allocation configuration of the source BWP comprises at least one of a slot offset, a start and length indicator value (SLIV) indicating a symbol location within a slot, or a combination thereof.
The method of claim 1, wherein the resource allocation indicates a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop and a second half of the plurality of slots corresponding to a second hop, wherein the first hop corresponds to the source BWP or the companion BWP, and wherein the second hop corresponds to the other of the source BWP or the companion BWP.
The method of claim 1, wherein the cross-BWP FH indication further indicates a configured FH pattern of a plurality of FH patterns.
The method of claim 12, wherein the resource allocation indicates a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop and a second half of the plurality of slots corresponding to a second hop, and wherein the plurality of FH patterns comprises:

a first FH pattern in which the first hop corresponds to the source BWP and the second hop corresponds to the companion BWP; and

a second FH pattern in which the first hop corresponds to the companion BWP and the second hop corresponds to the source BWP.
The method of claim 13, wherein the configured FH pattern is indicated, in downlink control information (DCI) , by a joint coding of a BWP identifier (ID) field and a FH flag bit.
The method of claim 14, wherein the first FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and a first FH flag bit value; or wherein the second FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and a second FH flag bit value.
The method of claim 14, wherein the first FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and an FH flag bit value; or wherein the second FH pattern is indicated by a combination of a BWP ID field value equal to the source BWP ID and the FH flag bit value.
The method of claim 14, wherein the FH flag bit is a virtual-resource-block-to-physical-resource-block (VRB-to-PRB) mapping bit for scheduling a physical downlink shared channel (PDSCH) .
The method of claim 13, wherein the configured FH pattern is indicated by a value of a starting slot index of a scheduled multi-slot communication.
The method of claim 18, wherein an even value of the starting slot index indicates the first FH pattern and an odd value of the starting slot index indicates the second FH pattern.
The method of claim 13, wherein the configured FH pattern is the first FH pattern, the method further comprising transmitting and/or receiving at least one signal during a period of time between an end of a physical downlink control channel (PDCCH) communication carrying the cross-BWP FH indication and a start of a scheduled shared channel communication, the scheduled shared channel communication comprising at least one of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) .
The method of claim 13, wherein the configured FH pattern is the second FH pattern, the method further comprising transmitting and/or receiving at least one signal during a period of time between an end of a physical downlink control channel (PDCCH) communication carrying the cross-BWP FH indication and a start of a starting slot of a shared channel communication scheduled by the PDCCH communication, the scheduled shared channel communication comprising at least one of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) .
A method of wireless communication performed by a base station (BS) , comprising:

transmitting, to a user equipment (UE) , a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and

transmitting, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping (FH) indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.
The method of claim 22, wherein the communication comprises at least one of a downlink communication on a physical downlink shared channel (PDSCH) , or an uplink communication on a physical uplink shared channel (PUSCH) .
The method of claim 22, wherein the cross-BWP FH indication is carried in downlink control information (DCI) .
The method of claim 24, wherein the cross-BWP FH indication is indicated by a companion BWP identifier (ID) in a BWP ID field of the DCI.
The method of claim 22, wherein the cross-BWP FH is indicated by an indication of a physical uplink control channel (PUCCH) resource for hybrid automatic repeat request (HARQ) feedback, and wherein the indication of the PUCCH resource is included in downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) .
The method of claim 22, wherein the cross-BWP FH indication is transmitted, via a physical downlink control channel (PDCCH) occasion, in one or more symbols of a slot, the one or more symbols comprising at least one symbol that is not one of three starting symbols of the slot.
The method of claim 22, wherein the configuration message comprises a radio resource control (RRC) message.
The method of claim 22, wherein a set of configuration parameters associated with the source BWP is identical to a set of configuration parameters associated with the companion BWP, the set of configuration parameters associated with the source BWP indicating at least one of：

a subcarrier spacing (SCS) ,

a cyclic prefix (CP) ,

a bandwidth (BW) , or

a combination thereof.
The method of claim 22, wherein a time-domain resource allocation configuration associated with the source BWP is identical to a time-domain resource allocation configuration associated with the companion BWP.
The method of claim 30, wherein the time-domain resource allocation configuration of the source BWP comprises at least one of a slot offset, a start and length indicator value (SLIV) indicating a symbol location within a slot, or a combination thereof.
The method of claim 22, wherein the resource allocation indicates a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop and a second half of the plurality of slots corresponding to a second hop, wherein the first hop corresponds to the source BWP or the companion BWP, and wherein the second hop corresponds to the other of the source BWP or the companion BWP.
The method of claim 22, wherein the cross-BWP FH indication further indicates a configured FH pattern of a plurality of FH patterns.
The method of claim 33, wherein the resource allocation indicates a plurality of slots for the communication, a first half of the plurality of slots corresponding to a first hop and a second half of the plurality of slots corresponding to a second hop, and

wherein the plurality of FH patterns comprises:

a first FH pattern in which the first hop corresponds to the source BWP and the second hop corresponds to the companion BWP; and

a second FH pattern in which the first hop corresponds to the companion BWP and the second hop corresponds to the source BWP.
The method of claim 34, wherein the configured FH pattern is indicated, in downlink control information (DCI) , by a joint coding of a BWP identifier (ID) field and a FH flag bit.
The method of claim 35, wherein the first FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and a first FH flag bit value; or wherein the second FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and a second FH flag bit value.
The method of claim 35, wherein the first FH pattern is indicated by a combination of a BWP ID field value equal to the companion BWP ID and an FH flag bit value; or wherein the second FH pattern is indicated by a combination of a BWP ID field value equal to the source BWP ID and the FH flag bit value.
The method of claim 35, wherein the FH flag bit is a virtual-resource-block-to-physical-resource-block (VRB-to-PRB) mapping bit for scheduling a physical downlink shared channel (PDSCH) .
The method of claim 34, wherein the configured FH pattern is indicated by a value of a starting slot index of a scheduled multi-slot communication.
The method of claim 39, wherein an even value of the starting slot index indicates the first FH pattern and an odd value of the starting slot index indicates the second FH pattern.
A user equipment (UE) for wireless communication, comprising:

a memory; and

one or more processors operatively coupled to the memory, the memory and the one or more processors configured to:

receive a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP;

receive a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and

communicate according to the resource allocation.
A base station (BS) for wireless communication, comprising:

a memory; and

one or more processors operatively coupled to the memory, the memory and the one or more processors configured to:

transmit, to a user equipment (UE) , a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and

transmit, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.
A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising:

one or more instructions that, when executed by one or more processors of a user equipment (UE) , cause the one or more processors to:

receive a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP;

receive a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and

communicate according to the resource allocation.
A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising:

one or more instructions that, when executed by one or more processors of a base station (BS) , cause the one or more processors to:

transmit, to a user equipment (UE) , a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and

transmit, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.
An apparatus for wireless communication, comprising:

means for receiving a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP;

means for receiving a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to a source BWP and at least one hop corresponding to a companion BWP; and

means for communicating according to the resource allocation.
An apparatus for wireless communication, comprising:

means for transmitting, to a user equipment (UE) , a configuration message indicating a companion bandwidth part (BWP) of a source BWP, wherein the configuration message indicates a companion BWP identifier (ID) corresponding to the companion BWP, wherein the companion BWP ID is different than a source BWP ID corresponding to the source BWP; and

means for transmitting, to the UE, a resource allocation for a communication, wherein the resource allocation includes a cross-BWP frequency hopping indication that indicates that a frequency-domain resource allocation for the communication includes at least one hop corresponding to the source BWP and at least one hop corresponding to the companion BWP.