Bandwidth part (BWP) configuration with a shared partial configuration for non-terrestrial networks (NTNs)

A method for wireless communication performed by a user equipment (UE) includes receiving a first message comprising a configuration for reconstructing a bandwidth part (BWP) for a network entity. The BWP may be used on a non-terrestrial beam of a non-terrestrial entity. The method also includes reconstructing a BWP of the BWPs based on the configuration. The method further includes switching from a current BWP to the reconstructed BWP to communicate with the network entity, e.g., non-terrestrial entity.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communications, and more particularly to techniques and apparatuses for bandwidth part (BWP) configuration with a shared partial configuration for non-terrestrial networks (NTNs).

BACKGROUND

A wireless communications network may include a number of base stations (BSs) that can support communications 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 communications link from the BS to the UE, and the uplink (or reverse link) refers to the communications link from the UE to the BS. As will be described in more detail, a BS may be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, and/or the like.

SUMMARY

According to aspects of the present disclosure, a method performed by a user equipment (UE) receives a first message that includes a configuration for reconstructing a bandwidth part (BWP) for a network device. The method also reconstructs the BWP based on the configuration. The method further switches from a current BWP to the reconstructed BWP to communicate with the network device.

In other aspects of the present disclosure, an apparatus for wireless communications performed by a user equipment (UE) includes a processor and memory coupled with the processor. Instructions stored in the memory are operable, when executed by the processor, to cause the apparatus to receive a first message that includes a configuration to reconstruct a bandwidth part (BWP) for a network device. The apparatus can also reconstruct the BWP based on the configuration. The apparatus can further switch from a current BWP to the reconstructed BWP to communicate with the network device.

In other aspects of the present disclosure, a user equipment (UE) includes means for receiving a first message comprising a configuration for reconstructing a bandwidth part (BWP) for network device. The UE also includes means for reconstructing the BWP based on the configuration. The UE further includes means for switching from a current BWP to the reconstructed BWP to communicate with the network device.

In other aspects of the present disclosure, a non-transitory computer-readable medium with program code recorded thereon is disclosed. The program code is executed by a user equipment (UE) and includes program code to receive a first message that includes a configuration to reconstruct a bandwidth part (BWP) for a network device. The UE also includes program code to reconstruct the BWP based on the configuration. The further includes program code to switch from a current BWP to the reconstructed BWP to communicate with the network device y.

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

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully below 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, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure, 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. 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. It should be understood that any aspect of the disclosure disclosed may be embodied by one or more elements of a claim.

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

In some cases, a user equipment (UE) and a non-terrestrial entity may transmit control information or data messages using one or more beams associated with one or more bandwidth parts (BWPs). In some examples, the non-terrestrial entity may be a satellite or a high altitude platform station (HAPS). In one example, the non-terrestrial entity and the UE may be thousands of kilometers apart. Due to the distance between the non-terrestrial entity and the UE, a transmission from the non-terrestrial entity may degrade due to, for example, atmospheric effects, interference from other radio frequency sources, signal attenuation due to vegetation or structures, and the like. Due to the mobility of the non-terrestrial entity and/or signal degradation, the UE may frequently switch beams. In some cases, for each beam, one or more BWPs may be configured to accommodate different UE capabilities.

The BWP configurations may be signaled to the UE during a cell search operation. The BWP configuration may provide one or more downlink beam parameters, such as frequency location and bandwidth, a subcarrier spacing, cyclic prefix duration, cell specific downlink control channel resources (e.g., control resource set (CORSET) zero, search space zero), and/or a time-domain resource allocation for a downlink shared channel (e.g., a starting time and duration for a physical downlink shared channel (PDSCH)). The BWP configuration may provide an uplink shared channel configuration (e.g., time-domain resource allocation patterns), as well as similar uplink beam parameters. Additionally, the BWP configuration may configure multiple options for a parameter. The selection or activation of a particular option may be provided via control signaling, such as downlink control information (DCI), a medium access control (MAC) control element (CE), or radio resource control (RRC) signaling. That is, the BWP configuration may configure multiple time-domain resource allocation patterns for downlink shared channels, and one of the configured time-domain resource allocation patterns may be selected via DCI signaling.

The multiple BWP configurations may increase signaling and increase resources used by the UE. Therefore, it is desirable to improve BWP configuration signaling. According to aspects of the present disclosure, a UE receives a configuration for reconstructing a bandwidth part (BWP) of multiple BWPs of a non-terrestrial entity. The configuration for reconstructing the BWP may be referred to as a BWP configuration. The UE may reconstruct one of the BWPs based on the BWP configuration. Furthermore, the UE may switch from a current BWP to the reconstructed BWP to communicate with the non-terrestrial entity. The BWP configuration may be received in a radio resource control (RRC) message or a system information block (SIB) message.

In some cases, the BWP configuration may be an initial BWP configuration. For example, the network entity may configure an initial downlink BWP and/or an initial uplink BWP. In some other cases, the BWP configuration (e.g., including a downlink BWP or an uplink BWP configuration) may correspond to a reference BWP. In still other cases, the BWP configuration may correspond to a shared partial BWP configuration. The shared partial BWP configuration may include a shared common part and a shared dedicated part.

The BWP configuration may be for a first non-terrestrial beam from the non-terrestrial entity. In some aspects, the non-terrestrial entity is currently serving the UE via the first non-terrestrial beam. In other aspects, the non-terrestrial entity is currently serving the UE via a second non-terrestrial beam, and the first non-terrestrial beam is one of multiple non-terrestrial beams of the non-terrestrial entity. In another configuration, the non-terrestrial entity is not serving the UE at a time when the BWP configuration is received.

The UE may also receive an indication for transforming the BWP based on the shared partial BWP configuration and one or more parameters independent of the shared partial BWP configuration. The transformation may include a frequency offset. In one example, the BWP is reconstructed by applying the frequency offset to a frequency of the shared partial BWP configuration.

As described, the UE may receive multiple BWP configurations. In one implementation, the shared partial BWP configuration is one shared partial BWP configuration of multiple shared BWP configurations. Each of the multiple shared partial BWP configurations is associated with a unique identifier. The UE may receive an identifier identifying the shared partial BWP configuration.

In one implementation, the UE switches to the reconstructed BWP before expiration of a timer. The timer may include a first value when the current BWP and the reconstructed BWP have a same shared partial BWP configuration. Additionally, the timer may include a second value when the current BWP and the reconstructed BWP have different shared partial BWP configurations. The first value is equal to or less than the second value. A value of the timer may be based on one or more information elements of the shared partial BWP configuration of the reconstructed BWP, whether the switch from the current BWP to the reconstructed BWP is an intra-beam switch or an inter-beam switch, and a UE capability.

As an example, the BSs110(shown as BS110a, BS110b, BS110c, and BS110d) and the core network130may exchange communications via backhaul links132(e.g., S1, etc.). Base stations110may communicate with one another over other backhaul links (e.g., X2, etc.) either directly or indirectly (e.g., through core network130).

The core network130may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations110or access node controllers (ANCs) may interface with the core network130through backhaul links132(e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UEs120. In some configurations, various functions of each access network entity or base station110may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station110).

One or more UEs120may establish a packet data unit (PDU) session for a network slice. In some cases, the UE120may select a network slice based on an application or subscription service. By having different network slices serving different applications or subscriptions, the UE120may improve its resource utilization in the wireless network100, while also satisfying performance specifications of individual applications of the UE120. In some cases, the network slices used by UE120may be served by an AMF (not shown inFIG.1) associated with one or both of the base station110or core network130. In addition, session management of the network slices may be performed by a session management session (SMF).

The UEs120may include a bandwidth part (BWP) module140. For brevity, only one UE120dis shown as including the BWP module140. The BWP module140may receive a first message comprising a configuration for reconstructing a bandwidth part (BWP) of a number of BWPs for a network device, such as a non-terrestrial entity. The BWP module140may also reconstruct a BWP of the number of BWPs based the configuration. The BWP module140may further switch from a current BWP to the reconstructed BWP to communicate with the network device.

In some aspects, two or more UEs120(e.g., shown as UE120aand UE120e) may communicate directly using one or more sidelink channels (e.g., without using a base station110as an intermediary to communicate with one another). For example, the UEs120may 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 UE120may perform scheduling operations, resource selection operations, and/or other operations described elsewhere as being performed by the base station110. For example, the base station110may configure a UE120via downlink control information (DCI), radio resource control (RRC) signaling, a media access control-control element (MAC-CE) or via system information (e.g., a system information block (SIB).

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

FIG.2shows a block diagram of a design200of the base station110and UE120, which may be one of the base stations and one of the UEs inFIG.1. The base station110may be equipped with T antennas234athrough234t, and UE120may be equipped with R antennas252athrough252r, where in general T≥1 and R≥1.

At the UE120, antennas252athrough252rmay receive the downlink signals from the base station110and/or other base stations and may provide received signals to demodulators (DEMODs)254athrough254r, respectively. Each demodulator254may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator254may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols. A MIMO detector256may obtain received symbols from all R demodulators254athrough254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor258may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE120to a data sink260, and provide decoded control information and system information to a controller/processor280. 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 the UE120may be included in a housing.

On the uplink, at the UE120, a transmit processor264may receive and process data from a data source262and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from the controller/processor280. Transmit processor264may also generate reference symbols for one or more reference signals. The symbols from the transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by modulators254athrough254r(e.g., for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to the base station110. At the base station110, the uplink signals from the UE120and other UEs may be received by the antennas234, processed by the demodulators254, detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by the UE120. The receive processor238may provide the decoded data to a data sink239and the decoded control information to a controller/processor240. The base station110may include communications unit244and communicate to the core network130via the communications unit244. The core network130may include a communications unit294, a controller/processor290, and a memory292.

The controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with bandwidth part (BWP) reconstruction based on a received BWP configuration as described in more detail elsewhere. For example, the controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, the process ofFIG.7and/or other processes as described. Memories242and282may store data and program codes for the base station110and UE120, respectively. A scheduler246may schedule UEs for data transmission on the downlink and/or uplink.

In some aspects, the UE120may include means for receiving a first message comprising a configuration for reconstructing a bandwidth part (BWP) of a number of BWPs for a first non-terrestrial beam of an non-terrestrial entity; means for reconstructing a BWP of the number of BWPs based the configuration; and means for switching from a current BWP to the reconstructed BWP to communicate with the non-terrestrial entity. Such means may include one or more components of the UE120described in connection withFIG.2.

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

FIG.3is a diagram illustrating an example of a wireless communications system300that supports one or more bandwidth part (BWP) configurations for communication networks, in accordance with aspects of the present disclosure. In some examples, the wireless communications system300may implement aspects of the wireless network100described with respect toFIG.1. The wireless communications system300may include a network entity320and a UE315, which may be an example of a UE120as described with respect toFIG.1. The network entity320may be a non-terrestrial entity, such as a satellite or a high-altitude platform station (HAPS). Alternatively, the network entity320may be a base station, such as the base station110described with respect toFIG.1. As such, the wireless communications system300may be an example of a non-terrestrial network (NTN), a terrestrial network, or a combination of an NTN and a terrestrial network.

In some wireless communication environments, beam switching may be frequent relative to other environments. In some cases, as illustrated inFIG.3, a network entity320may communicate with a UE315via a beam330, which may be a directional beam. The beam330may have a beam footprint335(e.g., a coverage area of the beam330). For example, the network entity320may communicate with the UE315via a first beam330-a. Additionally, or alternatively, the network entity320may use a second beam330-bor a third beam330-cfor communications. The UE315may, in some examples, derive a beam footprint shape (e.g., hexagonal, circular, elliptical, or the like) based on the shape and structure of the antenna associated with the beam330. In some other examples, the UE315may derive a beam size based on one or more power levels associated with the beam330. The shape and size of the beam footprint335may depend on the distance of the transmitting device (e.g., network entity320) from the surface of the Earth, the transmitting angle, and the like. Further, footprints that are adjacent may have different shapes and sizes dependent on the transmission angle and distance of the transmitting device. In some cases, the beam footprints335may overlap. The beam footprint335may be small relative to the speed of the network entity320. In some other examples, the frequency of beam switching may depend on the mobility of the UE315and/or the mobility of the UE315in combination with movement of a base station.

The network entity320may configure each beam330from a satellite (not shown) as a cell with an initial BWP per beam (e.g., an initial uplink BWP, an initial downlink BWP, or an uplink BWP and downlink BWP pair). Each pattern of the beam footprint335inFIG.3may represent a different initial BWP. In some cases, each beam330may be associated with one or more BWPs in addition to the initial BWP, which the UE315and the network entity320may use to communicate. The network (e.g., network entity320) may signal to the UE315which BWP to utilize as the beam footprints335move or the UE315moves.

In some cases, one or more BWPs may be configured for a non-terrestrial beam330(e.g., satellite beam) for each UE315. Each beam330may be configured with an initial uplink bandwidth part and an initial downlink bandwidth part. Each beam330may also be configured with a default uplink bandwidth part and a default downlink bandwidth part for a UE315. Additional bandwidth parts may be configured for each satellite beam330. As noted, the network entity320may configure BWPs in a beam330for the UE315. The UE315may switch BWPs during a BWP switching operation, such as an inter-beam switch or an intra-beam switch. For inter-beam switching, a UE315may switch from a BWP in a first beam330-ato a BWP in a second beam330-b. For example, if the UE315moves from a beam footprint335associated with first beam330-ato a beam footprint335associated with the second beam330-b, the UE may switch from a BWP in the first beam330-ato a BWP in the second beam330-b. For intra-beam BWP switching, a UE315may switch from a BWP to a different BWP in the same beam330. For example, if the UE315performs a BWP switching operation without leaving the beam footprint335associated with the first beam330-a, the UE315may switch from a BWP associated with the first beam330-ato another BWP associated with the first beam330-a. In some examples, the network entity320may configure the one or more beams330as a single cell. In other examples, the network entity320may configure the one or more beams330as separate cells or as multiple cells. That is, each cell may include one or more beams330corresponding to beam footprints335.

In some examples, the UE315may determine a beam330to use for communication based on monitoring for a broadcast message from the satellite. For example, the satellite may broadcast one or more synchronization signal blocks (SSBs) to one or more UEs315. The UE315may detect an SSB, which may include a master information block (MIB), a system information block (SIB) (e.g., a first type of SIB (SIB1)), or both. The UE315may decode the MIB to identify one or more parameters that may be used to detect and decode the SIB1. For example, the one or more parameters may include a bandwidth, a control resource set (CORESET), a search space, other parameters related to resource allocation, or a combination associated with the SIB1. In some examples, the SIB1 may include location information (e.g., a pointer) corresponding to a second type of SIB (SIB2). The SIB2 may include one or more configurations for BWPs associated with a beam330used for communication with the network entity320. Additionally or alternatively, the UE315may receive RRC signaling indicating the one or more configurations for the BWPs associated with the beam330.

Due to the high mobility of the UE315relative to the network entity320, the UE315may frequently switch BWPs associated with one or more beams330. As illustrated inFIG.3, the UE315may traverse seven different beam footprints335, and may perform multiple BWP switching operations based on traversing the beam footprints335. For example, the UE315may perform a BWP switching operation to switch from BWPs associated with the first beam330-a, second beam330-b, or both, based on a BWP configuration and the trajectory of the UE315. Additionally, or alternatively, the UE315may switch to a different cell based on traversing the beam footprints335. For example, the beam footprints335associated with the first beam330-a, second beam330-b, and third beam330-cmay be associated with a first cell, however the other beam footprints335may be associated with different cells. Additionally or alternatively, beam footprints335associated with the first beam330-a, second beam330-b, and third beam330-cmay be associated with different cells.

In some cases, a UE315may switch beams330within a coverage area of a network entity320or when moving from a first coverage area to a second coverage area. For example, the UE315may move from a beam footprint335associated with the first beam330-ato a beam footprint335associated with the second beam330-b. In such examples, the UE315may be communicating with the network entity320on a second BWP, and may switch from the first beam330-ato the second beam330-bupon crossing into the beam footprint335for the second beam330-b. Because of the beam switch, the UE315may also switch from the second BWP to a first BWP. Similarly, the UE315may switch from the second beam330-bto another beam330. The beam switch may be a result of movement by the UE315, movement or handover by a network entity320, or a combination thereof. In some examples, the UE315may switch from the first beam330-ato the second beam330-bbased on a beam selection or beam refinement procedure, or based on detected interference or degraded signal quality on the first beam330-a.

In some cases, the UE315may use multiple BWP configurations corresponding to BWPs associated with a new beam in a BWP switching procedure, which may cause high signaling volume and inefficient resource allocation at the UE315(e.g., due to BWP configuration signaling). In some examples, the UE315may receive one or more configurations for BWPs from a network entity320(e.g., after performing a beam switching operation from the first beam330-ato the second beam330-b). The UE315may receive BWP configurations corresponding to BWPs in the first beam330-a, BWPs in a different beam330, such as the second beam330-b, or BWPs in a beam330from a different network entity320. The BWP configuration may include a frequency shift (e.g., based on a reference BWP) or a time delay associated with the BWP switching procedure.

FIG.4illustrates an example of a wireless communications system400that supports bandwidth part (BWP) configuration for wireless communication networks in accordance with aspects of the present disclosure. In some examples, the wireless communications system400may implement aspects of the wireless network100, wireless communications system300, or both. The wireless communications system400may include a network entity420, a UE415, beams430, beam footprints435, and communication links425. The network entity420may be an example of the network entity320as described with respect toFIG.3. The wireless communications system400may be an example of a non-terrestrial network (NTN), a terrestrial network, or a combination of an NTN and a terrestrial network.

In some cases, a coverage area410of the network entity420may include multiple beam footprints435corresponding to one or more beams430configured at the network entity420for communicating with one or more UEs415. For example, the network entity420may use multiple antennas (not shown) to form one or more beams430(e.g., narrow beams) for communication with one or more UEs415. The beams430may operate on different frequency intervals (e.g., different BWPs) to reduce interference among the beams430. That is, a first beam430-amay operate using different BWPs than a second beam430-b. In some examples, the network entity420may communicate with the UE415via one or more communication links425using the beams430. For example, the network entity420may transmit a message including control information to the UE415via a communication link425-a, which may be used for downlink communications, while the UE415and the network entity420may communicate using a communication link425-b, which may be used for uplink or downlink communications. The network entity420and the UE415may use the first beam430-afor both uplink and downlink communications.

The network entity420and the UE415may be thousands of kilometers apart, and it may take some time for electromagnetic waves to propagate over the distance between the network entity420and the UE415. The propagation delay for NTNs may be many orders of magnitude larger than the propagation delay for terrestrial networks. By way of example, the network entity420may be in an orbit, such as low Earth orbit, medium Earth orbit, other non-geostationary Earth orbit, or geostationary Earth orbit. In any of these examples, the network entity420may be many thousands of kilometers from Earth, and therefore may be thousands of kilometers from the UE415. The distance that a transmission travels may result in substantial signal degradation due to, for example, atmospheric effects, interference from other radio frequency sources, signal attenuation due to vegetation or structures, and the like.

Further, due to the high mobility of the UE415relative to the network entity420, the UE415may frequently switch BWPs associated with one or more beams430. For example, the UE415may perform a BWP switching operation to switch from BWPs associated with the first beam430-a, second beam430-b, or both based on a BWP configuration440. In some examples, the BWP configuration440may include information such as a frequency location and bandwidth, a subcarrier spacing, a cyclic prefix duration, a control resource set (CORESET), a search space for a downlink control channel (e.g., a physical downlink control channel (PDCCH)), a time-domain resource allocation for a downlink shared channel (e.g., a starting time and duration for a physical downlink shared channel (PDSCH)), or a combination. The information in the BWP configuration440may take up a relatively large number of bits in a message. In some cases, the UE415may use multiple BWP configurations440corresponding to BWPs associated with a new beam in the beam switching procedure, which may cause high signaling volume and inefficient resource allocation at the UE415(e.g., due to BWP configuration signaling in cell search operations).

In some examples, the UE415may receive one or more configurations for BWPs from a network entity420(e.g., after performing a beam switching operation from the first beam430-ato the second beam430-b). For example, the UE415may receive a BWP configuration440from the network entity420via the communication link425-a. The UE415may receive BWP configurations corresponding to BWPs in the first beam430-a, BWPs in a different beam430, such as the second beam430-b, or BWPs in a beam430from a different network entity420. The network entity420may send the bandwidth part configuration440using a SIB1, another SIB, or an RRC message, for example.

In some cases, the BWPs may be initial BWPs. For example, the network entity420may configure multiple initial downlink BWPs, multiple initial uplink BWPs, or both for each cell, where each cell may include one or more beams430. Each beam430may share an initial downlink BWP, an initial uplink BWP, or both with another beam430. For example, the second beam430-bmay share initial BWPs with a third beam430-cwith relatively low interference (e.g., because the second beam430-band third beam430-care relatively far apart).

In some cases, the BWP configuration440may include a BWP configuration440for each BWP associated with the second beam430-b. In some other cases, the BWP configuration440(e.g., including a downlink BWP or an uplink BWP configuration) may correspond to a reference BWP. In some cases, the reference BWP may be within the first beam430-a. For example, a downlink BWP, an uplink BWP, or both, of the first beam430-amay be configured with reference to another downlink BWP, another uplink BWP, or both, of the first beam430-a. Additionally, or alternatively, the reference BWP may be within a different beam430(e.g., second beam430-b). In some cases, the different beam may be from the network entity420or another network entity420. That is, one or more BWPs associated with the first beam430-afrom the network entity420may be configured with reference to another BWP associated with a beam430from a different network entity420. In some examples, the network entity420may determine a downlink BWP has information elements (IEs) that are the same as IEs corresponding to a reference downlink BWP. The network entity420may refrain from transmitting the IEs to the UE415in the BWP configuration440and may indicate an identifier of the reference downlink BWP, and may additionally indicate which IEs are the same.

In some other cases, the BWP configuration440(e.g., including a downlink BWP or an uplink BWP configuration) may correspond to a shared partial BWP.

As described above, a UE and a non-terrestrial entity may transmit control information or data messages using one or more beams associated with one or more bandwidth parts (BWPs). In some examples, the non-terrestrial entity may be an example of a satellite or a high altitude platform station (HAPS). Due to the distance between the non-terrestrial entity and the UE, a transmission from the non-terrestrial entity may be degraded. Due to beam degradation, a UE may switch satellite beams, perform an intra-beam BWP transition, or an inter-beam BWP transition.

As described above, each beam of a non-terrestrial entity, such as satellite beams, maps to a cell. In non-terrestrial networks (NTN), a satellite may use multiple antennas to form multiple narrow beams. As described, the beams (e.g., satellite beams) may operate on disjointed frequency intervals (e.g., different BWPs) to mitigate interference among the satellite beams.

FIG.5Ais a block diagram illustrating an example of a cell configuration, according to aspects of the present disclosure. As shown inFIG.5A, each beam may be configured as a separate cell (shown as Cell 0-Cell 7 inFIG.5A). Each cell corresponds to one BWP of multiple BWPs (shown as BWP1-BWP4 inFIG.5A).FIG.5Bis a block diagram illustrating another example of a cell configuration, according to aspects of the present disclosure. As shown inFIG.5B, the beams may be configured as a group of cells (shown as Cell 0 and Cell 1 inFIG.5B). Each cell corresponds to one BWP of multiple BWPs (shown as BWP1-BWP4 inFIG.5B).FIG.5Cis a block diagram illustrating another example of a cell configuration, according to aspects of the present disclosure. As shown inFIG.5C, the beams may be configured as one cell (shown as Cell 0 inFIG.5C). Each cell corresponds to one BWP of multiple BWPs (shown as BWP1-BWP4 inFIG.5C). InFIGS.5A-5C, each cell has a beam footprint502. For each satellite beam, more than one BWP may be configured within the frequency interval. For example, multiple BWPs may be configured to accommodate different UE capabilities.

In addition to, or alternate from, switching due to beam degradation, a UE may perform a switch due to non-terrestrial entity mobility (e.g., movement of a satellite). That is, due to non-terrestrial entity mobility, a UE may switch satellite beams, perform an intra-beam BWP transition, or an inter-beam BWP transition. Therefore, the UE may be configured with multiple BWP configurations to enable switching.

One or more BWP configurations may be signaled to the UE. In some cases, a BWP configuration configures multiple parameters. The selection or activation of a particular parameter may be indicated via control signaling, such as downlink control information (DCI), a medium access control (MAC) control element (CE), or radio resource control (RRC) signaling. For example, the BWP configuration may configure multiple time-domain resource allocation patterns for downlink shared channels, and one of the configured time-domain resource allocation patterns may be selected via DCI signaling.

As described, the multiple BWP configurations may increase signaling and increase resources used by the UE. Therefore, it is desirable to improve BWP configuration signaling. Aspects of the present disclosure reduce BWP configuration signaling by providing a message including a BWP configuration for reconstructing a BWP.

According to aspects of the present disclosure, a UE receives a configuration for reconstructing a BWP of a beam for a non-terrestrial entity. The configuration for reconstructing the BWP may be referred to as a BWP configuration. The BWP configuration may be a shared partial BWP configuration, a reference BWP configuration, or an initial BWP configuration. The shared partial BWP configuration is described in more detail below. The reference configuration refers to the BWP being configured based on a difference from a complete configuration of a reference BWP. The initial BWP configuration refers to configuring from scratch.

The UE may reconstruct a BWP of the multiple BWPs based on the BWP configuration. Furthermore, the UE may switch from a current BWP to the reconstructed BWP to communicate with the non-terrestrial entity. The BWP configuration may be received in a radio resource control (RRC) message or a system information block (SIB) message, for example.

The BWP configuration may be for a first non-terrestrial beam from the non-terrestrial entity. In one configuration, the non-terrestrial entity is currently serving the UE via the first non-terrestrial beam. In another configuration, the non-terrestrial entity is currently serving the UE via a second non-terrestrial beam, and the first non-terrestrial beam is one of multiple non-terrestrial beams of the non-terrestrial entity. In another configuration, the non-terrestrial entity is not serving the UE at a time when the BWP configuration is received. For example, the beam may be from another satellite.

In some implementations, the BWP configuration is a shared partial BWP configuration. The shared partial BWP configuration may provide one or more downlink beam parameters and uplink beam parameters. For example, a downlink (DL) BWP parameter (e.g., configuration) may include a frequency location and a bandwidth, a subcarrier spacing (SCS), a cyclic prefix (CP) duration, a control resource set (CORSET) indication, and a search space indication. Uplink (UL) BWP parameters may include, for example, a frequency location and a bandwidth, a subcarrier spacing, a cyclic prefix duration, cell specific uplink control channel resources, and an uplink shared channel configuration.

According to aspects of the present disclosure, the shared partial BWP configuration may be a building block for configuring one or more BWPs for the UE. The BWP may be configured as a combination of the shared partial BWP configuration, one or more parameters that were not included in the shared partial BWP configuration, and/or a transformation.

In some implementations, the transformation may include a frequency offset applied to a frequency location and bandwidth configuration indicated in the shared partial BWP configuration.FIG.6is a diagram illustrating an example of applying a frequency offset to a frequency location and bandwidth configuration, according to aspects of the present disclosure. As shown inFIG.6, a frequency (shown as F0) and a bandwidth (shown as B) are obtained from the shared BWP configuration. A first bandwidth part602is based on the shared BWP configuration. A frequency offset (shown as F_offset) is applied to the frequency (F0) to obtain a transformed frequency. A second BWP604is derived from the shared BWP configuration and the frequency offset.

In some configurations, the shared partial BWP configuration is associated with an identifier. Multiple shared partial BWP configurations may be configured for a UE. The network may identify which shared partial BWP configuration should be used by signaling the identifier.

In some implementations, the shared partial BWP configuration may be a combination of a shared common part and a shared dedicated part. The shared common part (e.g., shared among BWPs) is split from a common part of the shared partial BWP configuration that is unique to a BWP (e.g., not shared among BWPs). The shared dedicated part is split from a dedicated part of the shared partial BWP configuration unique to the BWP.

For a downlink BWP configuration, the shared common part may include, for example, a frequency location and bandwidth, a subcarrier spacing, a cyclic prefix duration, a downlink control channel resources (e.g., CORESET zero), and/or a search space configuration (e.g., search space zero). The shared common part that may be unique to the UE may include time-domain resource allocation patterns for downlink shared channels (e.g., physical downlink shared channels (PDSCHs)). The shared dedicated part may include the semi-persistent scheduling (SPS) configuration or the UE specific control channel resources. The shared dedicated part unique to the UE may include a radio link monitoring configuration.

For an uplink BWP configuration, the shared common part may include, a frequency location and bandwidth, a subcarrier spacing, cyclic prefix duration, or cell specific uplink control channel (e.g., physical uplink control channel (PUCCH)) resources. The shared common part unique to the BWP may include random access parameters. The shared dedicated part may include a shared uplink channel (e.g., physical uplink shared channel (PUSCH) configuration. The shared dedicated part unique to the BWP may include a sounding reference signal (SRS) configuration.

As described above, the shared partial BWP configuration may be associated with an identifier. In this case, the network configures a particular shared partial BWP configuration by signaling an identifier. Additionally, the shared partial BWP configuration may comprise a common part and a dedicated part. TABLE 1 provides examples of identifiers (IDs) for information elements for a downlink BWP configuration. As shown in TABLE 1, the IDs may include a BWP identifier (shown as bwp-Id), a shared common downlink part (shown as bwp-Common-shared-Id), a unique common downlink part (shown as bwp-Common), a shared dedicated part (shown as bwp-Dedicated-shared-Id), and a unique dedicated part (shown as bwp-Dedicated).

In TABLE 1, BWP-DownlinkCommon-Shared-Id is an identifier for an information element (BWP-DownlinkCommon-Shared) that defines information elements included in the shared common part. Additionally, BWP-DownlinkDedicated-Shared-Id is an identifier for an information element (BWP-DownlinkDedicated-Shared) that defines information elements included in the shared dedicated part. BWP-DownlinkCommon-Not-shared defines information elements that are not included in the information elements corresponding to BWP-DownlinkCommon-Shared. In some examples, the ID BWP-Common-Shared-Id is not included in the BWP configuration. In this example, this BWP-DownlinkCommon-Not-shared reduces to BWP-DownlinkCommon.

In some implementations, a timing threshold is associated with two BWPs for BWP switching operations. The timing threshold may be referred to as a BWP switch delay. In these implementations, the switch (e.g., transformation) from a first BWP to a second BWP should occur before expiration of the timing threshold. A value of the timing threshold may be set to a first value if the UE switches between two BWPs that have a same partial BWP configuration. The value of the timing threshold may be set to a second value if the UE switches between two BWPs that have different shared partial BWP configurations. The first value may be less than or equal to the second value. The value of the timing threshold may also depend on information elements included in the shared partial BWP configuration. The value of the timing threshold may also depend on whether a beam of the first BWP is different from the beam of the second BWP (e.g., whether a BWP switch is intra-beam or inter-beam). The value of the timing threshold may further depend on UE capability.

As indicated above,FIGS.3-6are provided as examples. Other examples may differ from what is described with respect toFIGS.3-6.

FIG.7is a diagram illustrating an example process700performed, for example, by a UE, in accordance with various aspects of the present disclosure. The process700is an example of bandwidth part (BWP) configuration with a shared partial configuration for non-terrestrial networks (NTNs).

As shown inFIG.7, in some aspects, the process700may include receiving a first message comprising a configuration for reconstructing a bandwidth part (BWP) for a network device (block702). For example, the UE (e.g., using the antenna252, DEMOD/MOD254, MIMO detector256, receive processor258, controller/processor280, and/or memory282) may receive the first message. The network device may be a non-terrestrial entity and the BWP may be used for a first non-terrestrial beam of the non-terrestrial entity. The configuration may indicate a transformation of the BWP. The BWP configuration may be a shared partial BWP configuration, which may include a shared common part and a shared dedicated part. The configuration may also be a reference BWP configuration or an initial BWP configuration. The shared partial BWP configuration may provide one or more downlink beam parameters and uplink beam parameters. For example, a downlink (DL) BWP parameter (e.g., configuration) may include a frequency location and a bandwidth, a subcarrier spacing (SCS), a cyclic prefix (CP) duration, a control resource set (CORSET) indication, and a search space indication. Uplink (UL) BWP parameters may include, for example, a frequency location and a bandwidth, a subcarrier spacing, a cyclic prefix duration, cell specific uplink control channel resources, and an uplink shared channel configuration.

As shown inFIG.7, in some aspects, the process700may include reconstructing the BWP based on the configuration (block704). For example, the UE (e.g., using the antenna252, DEMOD/MOD254, MIMO detector256, TX MIMO processor266, receive processor258, transmit processor264, controller/processor280, and/or memory282) may reconstruct the BWP based on the configuration. The BWP may be configured as a combination of the shared partial BWP configuration, one or more parameters that were not included in the shared partial BWP configuration, and/or a transformation.

In some aspects, the process700may include switching from a current BWP to the reconstructed BWP to communicate with the network device (block706). For example, the UE (e.g., using the antenna252, DEMOD/MOD254, MIMO detector256, TX MIMO processor266, receive processor258, transmit processor264, controller/processor280, and/or memory282) may switch from a current BWP to the reconstructed BWP to communicate with the non-terrestrial entity. For example, the switch may occur as a result of beam degradation, or due to non-terrestrial entity mobility (e.g., movement of a satellite). That is, due to non-terrestrial entity mobility, a UE may switch satellite beams, perform an intra-beam BWP transition, or an inter-beam BWP transition. The UE may be configured with multiple BWP configurations to enable the switching.

Implementation examples are described in the following numbered clauses.1. A method for wireless communication performed by a user equipment (UE), comprising:receiving a first message comprising a configuration for reconstructing a bandwidth part (BWP) for a network device;reconstructing the BWP based on the configuration; andswitching from a current BWP to the reconstructed BWP to communicate with the network device.2. The method of clause 1, further comprising:receiving an indication for transforming the configuration, which is a shared partial BWP configuration; andreceiving at least one parameter independent of the shared partial BWP configuration.3. The method of clause 1 or 2, in which the indication for transforming comprises a frequency offset, and reconstructing the BWP comprises applying the frequency offset to a frequency of the shared partial BWP configuration.4. The method of any of the preceding clauses, in which the shared partial BWP configuration comprises a shared common part and a shared dedicated part.5. The method of any of the preceding clauses, in which the configuration comprises a shared partial BWP configuration, a reference BWP configuration, or an initial BWP configuration.6. The method of any of the preceding clauses, in which:the configuration is a shared partial BWP configuration; and the BWP is one BWP of a plurality of BWPs.7. The method of any of the preceding clauses, in which the configuration is a shared partial BWP configuration comprising:a downlink (DL) BWP configuration comprising a DL frequency location and a bandwidth for a shared partial DL BWP, a first subcarrier spacing, a first cyclic prefix duration, a control resource set (CORSET) indication, and a search space indication; andan uplink (UL) BWP configuration comprising an UL frequency location and a bandwidth for a shared partial UL BWP, a second subcarrier spacing, a second cyclic prefix duration, cell specific UL control channel resources, and an uplink shared channel configuration.8. The method of any of the preceding clauses, in which:the configuration is one shared partial BWP configuration of a plurality of shared BWP configurations; andeach one of the plurality of shared partial BWP configurations is associated with a unique identifier; and the method further comprises receiving the unique identifier for identifying the one shared partial BWP configuration.9. The method of any of the preceding clauses, further comprising switching to the reconstructed BWP before expiration of a timer.10. The method of any of the preceding clauses, in which the timer comprises:a first value when the current BWP and the reconstructed BWP have a same shared partial BWP configuration; ora second value when the current BWP and the reconstructed BWP have different shared partial BWP configurations, the first value being equal to or less than the second value.11. The method of any of the preceding clauses, in which a value of the timer is further based on at least one of information elements of the shared partial BWP configuration of the reconstructed BWP, whether switching from the current BWP to the reconstructed BWP is an intra-beam switch or an inter-beam switch, a UE capability, or a combination thereof.12. The method of any of the preceding clauses, in which the network device comprises a non-terrestrial entity and the BWP is used on a first non-terrestrial beam of the non-terrestrial entity.13. The method of any of the preceding clauses, in which:the non-terrestrial entity is currently serving the UE via the first non-terrestrial beam;the non-terrestrial entity is currently serving the UE via a second non-terrestrial beam and the first non-terrestrial beam is one of a plurality of non-terrestrial beams of the non-terrestrial entity; orthe non-terrestrial entity is not serving the UE at a time when the first message is received.14. The method of any of the preceding clauses, in which the non-terrestrial entity comprises a high-altitude platform station (HAPS) or a satellite.15. The method of any of the preceding clauses, in which the first message comprises a radio resource control (RRC) message or a system information block (SIB) message.16. An apparatus for wireless communications performed by a user equipment (UE), comprising:a processor,memory coupled with the processor; andinstructions stored in the memory and operable, when executed by the processor, to cause the apparatus:to receive a first message comprising a configuration to reconstruct a bandwidth part (BWP) for a network device;to reconstruct the BWP based on the configuration; andto switch from a current BWP to the reconstructed BWP to communicate with the network device.17. The apparatus of clause 16, in which the processor causes the apparatus:to receive an indication to transform the configuration, which is a shared partial BWP configuration; andto receive at least one parameter independent of the shared partial BWP configuration.18. The apparatus of clause 16 or 17, in which:the indication for transforming comprises a frequency offset; andthe processor causes the apparatus to reconstruct the BWP by applying the frequency offset to a frequency of the shared partial BWP configuration.19. The apparatus of any of the clauses 16-18, in which the shared partial BWP configuration comprises a shared common part and a shared dedicated part.20. The apparatus of any of the clauses 16-19, in which the configuration comprises a shared partial BWP configuration, a reference BWP configuration, or an initial BWP configuration.21. The apparatus of any of the clauses 16-20, in which:the configuration is a shared partial BWP configuration; andthe BWP is one BWP of a plurality of BWPs.22. The apparatus of any of the clauses 16-21, in which the configuration is a shared partial BWP configuration comprising:a downlink (DL) BWP configuration comprising a DL frequency location and a bandwidth for a shared partial DL BWP, a first subcarrier spacing, a first cyclic prefix duration, a control resource set (CORSET) indication, and a search space indication; andan uplink (UL) BWP configuration comprising an UL frequency location and a bandwidth for a shared partial UL BWP, a second subcarrier spacing, a second cyclic prefix duration, cell specific UL control channel resources, and an uplink shared channel configuration.23. The apparatus of any of the clauses 16-22, in which:the configuration is one shared partial BWP configuration of a plurality of shared BWP configurations;each one of the plurality of shared partial BWP configurations is associated with a unique identifier; andthe processor causes the apparatus to receive the unique identifier to identify the one shared partial BWP configuration.24. The apparatus of any of the clauses 16-23, in which the processor causes the apparatus to switch to the reconstructed BWP before expiration of a timer.25. The apparatus of any of the clauses 16-24, in which the timer comprises:a first value when the current BWP and the reconstructed BWP have a same shared partial BWP configuration; ora second value when the current BWP and the reconstructed BWP have different shared partial BWP configurations, the first value being equal to or less than the second value.26. The apparatus of any of the clauses 16-25, in which a value of the timer is further based on at least one of information elements of the shared partial BWP configuration of the reconstructed BWP, whether switching from the current BWP to the reconstructed BWP is an intra-beam switch or an inter-beam switch, a UE capability, or a combination thereof.27. The apparatus of any of the clauses 16-26, in which the network device comprises a non-terrestrial entity and the BWP is used on a first non-terrestrial beam of the non-terrestrial entity.28. The apparatus of any of the clauses 16-27, in which:the non-terrestrial entity is currently serving the UE via the first non-terrestrial beam;the non-terrestrial entity is currently serving the UE via a second non-terrestrial beam and the first non-terrestrial beam is one of a plurality of non-terrestrial beams of the non-terrestrial entity; orthe non-terrestrial entity is not serving the UE at a time when the first message is received.29. The apparatus of any of the clauses 16-28, in which the non-terrestrial entity comprises a high-altitude platform station (HAPS) or a satellite.30. The apparatus of any of the clauses 16-29, in which the first message comprises a radio resource control (RRC) message or a system information block (SIB) message.

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