Patent Description:
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, etc.). 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).

3GPP Tdoc R1-<NUM> discloses that for different partial bands, the different sounding bandwidth and granularity can be discussed for increasing the sounding flexibility. To realize fast sounding for gNB's flexible scheduling, SRS hopping scheme in and between multiple partial bands can be made in one slot. When SRS hopping is made between multiple partial bands, SRS in one hop can be transmitted in one partial band for good PAPR property, including when UE is not capable of simultaneous transmission in partial bands in a CC.

3GPP TR <NUM> V1. <NUM> states regarding UE transmission bandwidth configuration adaptation that the following observations were obtained for transition time specifically in terms of RF aspects: - For intra-band operation, at least for below <NUM>, the transition time can be up to <NUM> if the centre frequency is the same before and after the transmission bandwidth configuration adaptation. - For intra-band operation, at least for below <NUM>, the transition time is <NUM>-<NUM> if the centre frequency is different before and after the transmission bandwidth configuration adaptation. - For inter-band operation, at least for below <NUM>, the transition time can be up to <NUM>.

3GPP TS <NUM> V14. <NUM> states that If frequency hopping of the sounding reference signal is not enabled (i.e., bhop ≥ BSRS), the frequency position index nb remains constant (unless re-configured) and is defined by <MAT> where the parameter nRRC is given by higher-layer parameters freqDomainPosition and freqDomainPosition-ap for periodic and each configuration of aperiodic transmission, respectively.

At least one of the above objects is attained by the invention defined in the appended independent claims. Advantageous embodiments are covered by the appended dependent claims.

Each of the figures is provided for the purpose of illustration and description.

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.

Techniques and apparatus described herein relate to managing sounding reference signal (SRS) transmissions in a bandwidth part. Transmission bandwidth may be increased in order to meet the demand for the increase of the transmission speed (e.g., downlink and uplink) of a wireless communication network. For example, new radio (NR), which may also be referred to as <NUM>, is a set of enhancements to the Long-Term Evolution (LTE) mobile standard promulgated by the Third Generation Partnership Project (3GPP), may support wider bandwidth than previous wireless communication standards (e.g., LTE). As the bandwidth of a component carrier of a cell increases, one or more bandwidth parts may be configured for the bandwidth of the component carrier of the cell. A bandwidth part may include a group of resource blocks (e.g., a group of resource blocks (PRBs)) and bandwidth parameters (e.g., sub-carrier spacing and/or cyclic prefix (CP)). For example, one or more bandwidth parts may be assigned to a user equipment (UE) for communication. In an example, a UE may configure a bandwidth part having a bandwidth that is less than a bandwidth of a component carrier of a cell, and the UE may configure communications over the bandwidth part (and not the remaining bandwidth or bandwidth parts of the component carrier of the cell). Additional bandwidth values may be needed in order to support the wider bandwidth of the component carrier of the cell for the NR or <NUM> radio access technology (RAT). Also, additional bandwidth parameters (e.g., SRS bandwidth configurations and/or bandwidth offset values) may be needed to support the bandwidth parts of the component carrier of the cell. Techniques described herein relate to the management of such bandwidth parts and SRS transmissions using the bandwidth parts, and/or the like.

Various aspects are described more fully hereinafter with reference to the accompanying drawings.

<FIG> is a block diagram conceptually illustrating an example <NUM> of a wireless communication system and an access network, the example <NUM> according to the claimed invention. The wireless communication system and the access network may be an LTE network or some other wireless network, such as a <NUM> or NR network.

In the example shown in <FIG>, a BS <NUM> may be a macro BS for a macro cell, a pico cell <NUM>, and a femto cell.

A network that includes both small cell and macro cells may be known as a heterogeneous network. The base stations <NUM> / UEs <NUM> may use spectrum up to YMHz (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. Allocation of component carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

The MBMS Gateway <NUM> may be used to distribute MBMS traffic to the base stations <NUM> belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), or some other suitable terminology. The base station <NUM> provides an access point to the EPC <NUM> for a UE <NUM>. Examples of UEs <NUM> include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a toaster, or any other similar functioning device. Some of the UEs <NUM> may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, etc.).

One or more of the above types of UEs <NUM> may configure communications on one or more bandwidth parts of a component carrier of a cell that is less than a full bandwidth of the component carrier of the cell, and may communicate with base station <NUM> using the one or more bandwidth parts, as described in more detail elsewhere herein. The base station <NUM> identifies one or more bandwidth parts of the component carrier of the cell for the UE <NUM> to communicate with the base station <NUM>. Each of the one or more bandwidth parts of the component carrier of the cell may include a SRS bandwidth configuration and bandwidth offset value. The base station <NUM> transmits the SRS bandwidth configuration and the bandwidth offset value, for each of the bandwidth parts that are configured for the UE, to the UE. The UE <NUM> may receive a SRS bandwidth configuration an a bandwidth offset value for each of the one or more bandwidth parts to communicate with base station <NUM>, as described in more detail elsewhere herein.

Any number of wireless networks may be deployed in a given geographic area. Each wireless network may support one or more RATs and may operate on one or more frequencies.

Thus, in a wireless communication network with a scheduled access to timefrequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.

<FIG> is a diagram <NUM> illustrating an example of a DL frame structure. <FIG> is a diagram <NUM> illustrating an example of channels within the DL frame structure. <FIG> is a diagram <NUM> illustrating an example of an UL frame structure. <FIG> is a diagram <NUM> illustrating an example of channels within the UL frame structure. These diagrams are regarded useful for understanding the invention. A frame (<NUM>) may be divided into <NUM> equally sized subframes. For example, each subframe of a first RAT (e.g., <NUM> wireless communication system) may include two consecutive time slots. In another example, each subframe of a second RAT (e.g., NR/<NUM> wireless communication system) may include one or more (e.g., two consecutive) scheduling units. A resource grid may be used to represent the two-time slots, each time slot including one or moretime concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)). For a normal cyclic prefix, an RB may contain <NUM> consecutive subcarriers in the frequency domain and <NUM> consecutive symbols (for DL, OFDM symbols; for UL, SC-FDMA symbols) in the time domain, for a total of <NUM> REs. For an extended cyclic prefix, an RB may contain <NUM> consecutive subcarriers in the frequency domain and <NUM> consecutive symbols in the time domain, for a total of <NUM> REs.

As illustrated in <FIG>, some of the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include cell-specific reference signals (CRS) (also sometimes called common RS) of a first RAT (e.g., <NUM> wireless communication system), UE-specific reference signals (UE-RS), and channel state information reference signals (CSI-RS). <FIG> illustrates CRS for antenna ports <NUM>, <NUM>, <NUM>, and <NUM> (indicated as R<NUM>, R<NUM>, R<NUM>, and R<NUM>, respectively), UE-RS for antenna port <NUM> (indicated as R<NUM>), and CSI-RS for antenna port <NUM> (indicated as R).

<FIG> illustrates an example of various channels within a DL subframe of a frame. The physical control format indicator channel (PCFICH) is within symbol <NUM> of slot <NUM>, and carries a control format indicator (CFI) that indicates whether the physical downlink control channel (PDCCH) occupies <NUM>, <NUM>, or <NUM> symbols (<FIG> illustrates a PDCCH that occupies <NUM> symbols). The PDCCH carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. A UE may be configured with a UE-specific enhanced PDCCH (ePDCCH) that also carries DCI. The ePDCCH may have <NUM>, <NUM>, or <NUM> RB pairs (<FIG> shows two RB pairs, each subset including one RB pair). The physical hybrid automatic repeat request (ARQ) (HARQ) indicator channel (PHICH) is also within symbol <NUM> of slot <NUM> and carries the HARQ indicator (HI) that indicates HARQ acknowledgement (ACK) / negative ACK (NACK) feedback based on the physical uplink shared channel (PUSCH). The primary synchronization channel (PSCH) may be within symbol <NUM> of slot <NUM> within subframes <NUM> and <NUM> of a frame. The PSCH carries a primary synchronization signal (PSS) that is used by a UE <NUM> to determine subframe/symbol timing and a physical layer identity. The secondary synchronization channel (SSCH) may be within symbol <NUM> of slot <NUM> within subframes <NUM> and <NUM> of a frame. The SSCH carries a secondary synchronization signal (SSS) that is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSCH and SSCH to form a synchronization signal (SS) block. The MIB provides a number of RBs in the DL system bandwidth, a PHICH configuration, and a system frame number (SFN).

As illustrated in <FIG>, some of the REs carry demodulation reference signals (DM-RS) for channel estimation at the base station. For example, the UE may additionally transmit sounding reference signals (SRS) in the last symbol of a subframe in a first RAT (e.g., <NUM> wireless communication system). In another example, the UE may transmit sounding reference signals (SRS) based at least in part on SRS resource allocation by a base station in a second RAT (e.g., NR/<NUM> wireless communication system).

<FIG> illustrates an example of various channels within an UL subframe of a frame. A physical random-access channel (PRACH) may be within one or more subframes within a frame based on the PRACH configuration. The PRACH may include six consecutive RB pairs within a subframe. The PRACH allows the UE to perform initial system access and achieve UL synchronization. A physical uplink control channel (PUCCH) may be located on edges of the UL system bandwidth.

In some aspects, a UE may configure one or more bandwidth parts on a subset of slots, frames, subframes, and/or the like, as described in more detail elsewhere herein.

The diagram is regarded useful for understanding the invention.

Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.

<FIG> is a diagram <NUM> illustrating a base station <NUM> in communication with a UE <NUM>. This illustration is regarded useful for understanding the invention. Referring to <FIG>, the base station <NUM> may transmit a beamformed signal to the UE <NUM> in one or more of the directions 402a, 402b, 402c, 402d, 402e, 402f, <NUM>, <NUM>. The UE <NUM> may receive the beamformed signal from the base station <NUM> in one or more receive directions 404a, 404b, 404c, 404d. The UE <NUM> may also transmit a beamformed signal to the base station <NUM> in one or more of the directions 404a-404d. The base station <NUM> may receive the beamformed signal from the UE <NUM> in one or more of the receive directions 402a-<NUM>.

While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communication systems, such as NR or <NUM> technologies.

In aspects, NR may utilize OFDM with a CP (herein referred to as cyclic prefix OFDM or CP-OFDM) and/or SC-FDM on the uplink, may utilize CP-OFDM on the downlink and include support for half-duplex operation using time division duplexing (TDD). NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g., <NUM> megahertz (MHz) and beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., <NUM> gigahertz (GHz)), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) service.

A single component carrier bandwidth of <NUM> may be supported. NR resource blocks may span <NUM> sub-carriers with a sub-carrier bandwidth of <NUM> kilohertz (kHz) over a <NUM> duration. Each radio frame may include <NUM> subframes with a length of <NUM>. Consequently, each subframe may have a length of <NUM>. Each subframe may indicate a link direction (e.g., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include downlink/uplink (DL/UL) data as well as DL/UL control data.

The RAN may include a central unit (CU) and distributed units (DUs). A NR BS (e.g., gNB, <NUM> Node B, Node B, transmit receive point (TRP), access point (AP)) may correspond to one or multiple BSs. NR cells can be configured as access cells (ACells) or data only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some examples, DCells may not transmit synchronization signals. In some examples, DCells may transmit synchronization signals. NR BSs may transmit downlink signals to UEs indicating the cell type. Based at least in part on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based at least in part on the indicated cell type.

<FIG> are diagrams illustrating example scenarios associated with one or more bandwidth parts configuration. These example scenarios are not covered by the claimed invention.

New Radio (NR) supports the use of multiple different numerologies (e.g., <NUM>, <NUM>, <NUM>, <NUM>, and/or the like) and multiple different slot durations (e.g., <NUM>, <NUM>, <NUM>, and/or the like). Furthermore, a wideband bandwidth (e.g., a system bandwidth and/or the like) in NR may be up to <NUM> (e.g., for the sub-<NUM> frequency band), up to <NUM> (e.g., for a frequency band above <NUM>), and/or the like. In some cases, there may be scenarios where a UE only monitors or is only served with a subset of the wideband bandwidth. This subset of the wideband bandwidth may be referred to as a bandwidth part (BWP). The UE may be configured with at least one downlink bandwidth part and/or one uplink bandwidth part. Also, the UE may be configured with resources for different purposes (e.g., downlink, uplink, uplink beamforming). In an example, the UE may be configured with SRS resources and the SRS resources configuration may be signaled to the UE periodically, semipersistently, or aperiodically (e.g., signaled in downlink control information (DCI)).

In an example useful for understanding the invention, as shown in <FIG>, an example diagram <NUM> may illustrate a component carrier <NUM> that may span a wideband bandwidth, and a bandwidth part (BWP) <NUM> may span a portion of the component carrier <NUM>. For example, the bandwidth part <NUM> may be less than the component carrier <NUM> due to a UE capability, such as a reduced UE bandwidth capability. As a more specific example, the UE may be an NB-IoT UE with a limited bandwidth capability.

The BWP <NUM> may be configured with a plurality of SRS bandwidth configurations. For example, the base station may identify a SRS bandwidth configuration from the plurality of SRS bandwidth configurations for the BWP <NUM>. The SRS bandwidth configuration of the BWP <NUM> may be component carrier specific or cell specific for all UEs that are served by the BWP <NUM>. For example, the identified SRS bandwidth configuration may be transmitted to all UEs served by the BWP <NUM>. In an example, different plurality of SRS bandwidth configurations may be configured for BWP <NUM> based at least in part on a bandwidth of the BWP <NUM>. In an example, as shown in Table <NUM>, the BWP <NUM> may be configured with a set of plurality of SRS bandwidth configurations ( <MAT>) and each of the plurality of SRS bandwidth configurations ( <MAT>) may include different bandwidth values (MSRS). The different bandwidth values (MSRS) may indicate a number of resource blocks (e.g., physical resource blocks) configured for SRS transmissions by the UE. Table <NUM>, BWP <NUM> configured with uplink bandwidth of <MAT>.

In another example, as shown in Table <NUM>, the BWP <NUM> may be configured with different set of plurality of SRS bandwidth configurations ( <MAT>) than the BWP <NUM> in Table <NUM>. Also, each of the plurality of SRS bandwidth configurations ( <MAT>) in Table <NUM> may include different bandwidth values (MSRS) than the bandwidth values (MSRS) of the SRS bandwidth configurations ( <MAT>) shown in Table <NUM>. Table <NUM>, BWP <NUM> configured with uplink bandwidth of <MAT>.

In another example useful for understanding the invention, and as shown in <FIG>, an example diagram <NUM> may illustrate a component carrier <NUM> that may span a wideband bandwidth, a first bandwidth part (BWP1) <NUM> may span a portion of the component carrier <NUM>, and a second bandwidth part (BWP2) <NUM> may span a portion of the first bandwidth part <NUM>. In this case, the first bandwidth part <NUM> may represent a UE bandwidth capability, and the second bandwidth part <NUM> may represent a bandwidth to be monitored by or served to the UE. For example, the UE may be capable of communicating over the entire first bandwidth part <NUM>, but may be configured to communicate only in the second bandwidth part <NUM> (e.g., for a time period) to conserve battery power. In this case, the UE may be capable of transitioning between a full bandwidth configuration, where the UE monitors or is served on the first bandwidth part <NUM>, and a bandwidth part configuration where the UE monitors or is served on the second bandwidth part <NUM>. For example, the UE may transition to the full bandwidth configuration when the UE is scheduled to transmit or receive data (e.g., a threshold amount of data), and may transition to the bandwidth part configuration to conserve battery power when the UE is not scheduled to transmit or receive data.

In a further example useful for understanding the invention, and as shown in <FIG>, an example diagram <NUM> may illustrate a component carrier <NUM> that may span a wideband bandwidth, which may be partitioned into multiple bandwidth parts, for example, a first bandwidth part (BWP1) <NUM> and a second bandwidth part (BWP2) <NUM>. The first and second bandwidth parts <NUM>, <NUM> may each span a portion of the component carrier <NUM>. In some aspects, different bandwidth parts may be associated with different numerologies, such as <NUM>, <NUM>, <NUM>, <NUM>, and/or the like. Additionally, or alternatively, a guard band <NUM> (e.g., a gap) may be configured between different bandwidth parts to reduce interference between bandwidth parts and/or numerologies.

In yet another example useful for understanding the invention, and as shown in <FIG>, an example diagram <NUM> may illustrate a component carrier <NUM> that may span a wideband bandwidth, which may be partitioned into multiple bandwidth parts, for example, a first bandwidth part (BWP <NUM>) <NUM> and a second bandwidth part (BWP <NUM>) <NUM>. Further, the component carrier <NUM> may include a third bandwidth part (BWP <NUM>) <NUM> not used by the UE. For example, the first bandwidth part <NUM> and the second bandwidth part <NUM> may be associated with the same network operator, and/or may be used to support intra-band carrier aggregation, while the third bandwidth part <NUM> may be associated with a different network operator and/or may not be used for carrier aggregation. In some implementations, a synchronization signal (SS) block (e.g., which includes one or more of a PSS, an SSS, a PBCH, and/or the like) may be transmitted on one bandwidth part, and may include information for multiple bandwidth parts to conserve network resources.

Other examples are possible and may differ from what was described relating to <FIG>.

While different types of bandwidth parts are described in connection with the scenarios of <FIG>, techniques according to the claimed invention appended below relate to configuring a SRS bandwidth configuration and a bandwidth offset value for each of the bandwidth parts. For example, a UE may be configured with a bandwidth part (e.g., BWP2 <NUM>), of a component carrier, which may correspond to BWP1 <NUM>. Additionally, or alternatively, the UE may be configured with one or more bandwidth parts (e.g., BWP1 <NUM> and/or BWP <NUM><NUM>) for multiple component carriers, such as in the carrier aggregation scenario described above in connection with <FIG>.

As discussed above, one or more bandwidth parts may be assigned to the UE for communication with the base station. For example, the UE may transmit SRS to the base station using the configured one or more bandwidth parts for a first RAT (e.g., NR or <NUM>). For example, a plurality of SRS bandwidth configurations may be configured for each of the one or more bandwidth parts. Each of the plurality of SRS bandwidth configurations may include different set of bandwidth values. The plurality of bandwidth values of each of the plurality of SRS bandwidth configurations may indicate a bandwidth and/or a number of resource blocks (e.g., physical resource blocks (PRBs)) configured for SRS transmission by the UEs served by the bandwidth part.

The base station may identify a SRS bandwidth configuration from the plurality of SRS bandwidth configurations for each of the one or more bandwidth parts. The SRS bandwidth configuration may be component carrier specific or cell specific for all UEs served by the bandwidth part. For example, the SRS bandwidth configuration configured for the bandwidth part may be transmitted to all UEs that are served by the bandwidth part. In an example, all UEs served by a first bandwidth part may be configured with a SRS bandwidth configuration <NUM> and all UEs served by a second bandwidth part may be configured with a SRS bandwidth configuration <NUM>. In other examples, different SRS bandwidth configurations may be configured for different UEs served by the bandwidth part. In an example, a first UE served by a first bandwidth part may be configured with a SRS bandwidth configuration <NUM> and a second UE served by the first bandwidth part may be configured with a SRS bandwidth configuration <NUM>. The SRS bandwidth configuration configured for each bandwidth parts may be based at least in part on a number of bandwidth parts configured for the component carrier and/or a bandwidth of a bandwidth part of the component carrier. For example, different RATs (e.g., <NUM>, <NUM>, NR wireless communication systems) may support different uplink system bandwidth, and based at least in part on the different uplink system bandwidth, different SRS bandwidth configurations may be identified. Different RATs (e.g., <NUM>, <NUM>, NR wireless communication systems) may support different SRS bandwidth configurations that may be compatible with each other.

In an example, a first RAT (e.g., <NUM> wireless communication system) may support a first plurality of uplink system bandwidths (e.g., <NUM>, <NUM>, <NUM> and/or <NUM>). A first plurality of SRS bandwidth configurations may be configured for each of the first uplink system bandwidths of the first RAT. For example, the first plurality of SRS bandwidth configurations may include a plurality of bandwidth values to support different first uplink system bandwidths of the first RAT. A second RAT (e.g., NR/<NUM> wireless communication system) may support a second plurality of uplink bandwidth parts (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM>). A second plurality of SRS bandwidth configurations may be configured for each of the second uplink system bandwidth parts of the second RAT. For example, the second plurality of SRS bandwidth configurations may include a plurality of bandwidth values to support different second uplink system bandwidths of the second RAT. In an example, in order to achieve system compatibility between the first RAT and the second RAT, SRS bandwidth configurations of the first RAT may be supported by the second RAT. In another example, in order rot achieve system compatibility between the first RAT and the second RAT, the SRS bandwidth configurations of the second RAT may be configured based at least in part on the SRS bandwidth configurations of the first RAT.

As discussed above, in order to achieve system compatibility between the first RAT and the second RAT, SRS bandwidth configurations of the first RAT may be supported by the second RAT. As shown below, a first RAT (e.g., <NUM> wireless communication system) may include a first plurality of bandwidth values for different SRS bandwidth configurations of the first RAT to support a first plurality of uplink system bandwidths. The SRS bandwidth configurations for the first RAT may include different set of the first plurality of bandwidth values. <MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>; - for example, an uplink system bandwidth of approximately <NUM> (e.g., spanning between <NUM> RBs to <NUM> RBs) may include a set of possible bandwidth values of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM>. <MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM> - for example, an uplink system bandwidth of approximately <NUM> (e.g., spanning between <NUM> RBs to <NUM> RBs) may include a set of possible bandwidth values of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM>. <MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM> - for example, an uplink system bandwidth of approximately <NUM> (e.g., spanning between <NUM> RBs to <NUM> RBs) may include a set of possible bandwidth values of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM>. <MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM> - for example, an uplink system bandwidth of approximately <NUM> (e.g., spanning between <NUM> RBs to <NUM> RBs) may include a set of possible bandwidth values of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM>.

As shown above, the first RAT may support uplink system bandwidth of approximately <NUM> (e.g., <NUM> PRBs). In an example, as shown below, a second RAT (e.g., NR/<NUM> wireless communication system) may include a second set of possible bandwidth values for different SRS bandwidth configurations of the second RAT to support different uplink system bandwidths. The second plurality of SRS bandwidth configurations may include a second plurality of bandwidth values. <MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM><MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM><MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM><MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM> <MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM><MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM><MAT> <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>.

As show above, the second RAT (e.g., NR/<NUM> wireless communication system) may support uplink system bandwidth part of approximately <NUM>. In order to achieve system compatibility, the second RAT (e.g., NR/<NUM> wireless communication system) may adopt the SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system) for the system bandwidths that are supported by both the first RAT (e.g., <NUM> wireless communication system) and the second RAT (e.g., NR/<NUM> wireless communication system).

As shown above, the second RAT (e.g., NR/<NUM> wireless communication system) may support system bandwidths that may not be supported by the first RAT (e.g., <NUM> wireless communication system). The SRS bandwidth configurations of the second RAT may include one or more bandwidth values to support the system bandwidth of the second RAT (e.g., NR/<NUM> wireless communication system), and not supported by the first RAT (e.g., <NUM> wireless communication system). For example, the bandwidth values of the SRS bandwidth configurations of the second RAT may be configured based at least in part on the bandwidth values of the SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system) in order to achieve system compatibility. For example, the SRS bandwidth configurations of the second RAT (e.g., NR/<NUM> wireless communication system) may include a plurality of bandwidth values that are based at least in part on the bandwidth values of the SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system). In an example, the plurality of bandwidth values of the SRS bandwidth configurations of the second RAT (e.g., NR/<NUM> wireless communication system) may be a multiple of an integer (e.g., <NUM>-<NUM>) or a power of an integer (e.g., <NUM>n) of the plurality of bandwidth values of the SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system).

In the example SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system) and the second RAT (e.g., NR/<NUM> wireless communication system) shown above, system bandwidths of approximately, <NUM>, <NUM> and/or <NUM> are supported by the second RAT (e.g., NR/<NUM> wireless communication system) and not by the first RAT (e.g., <NUM> wireless communication system). However, in order to achieve system compatibility, the SRS bandwidth configurations for system bandwidths are the supported by the second RAT (e.g., NR/<NUM> wireless communication system), and not by the first RAT (e.g., <NUM> wireless communication system), may include bandwidth values from the first RAT (e.g., <NUM> wireless communication system) and/or bandwidth values that are multiple of an integer or a power of an integer (e.g., <NUM>n) of the bandwidth value of the first RAT (e.g., <NUM> wireless communication system). In an example, for system bandwidth of <NUM>, that is supported by the second RAT (e.g., NR/<NUM> wireless communication system), and not by the first RAT (e.g., <NUM> wireless communication system), the SRS bandwidth configurations may include a plurality of bandwidth values (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM>) that are supported by the first RAT (e.g., <NUM> wireless communication system). Also, the SRS bandwidth configurations may include bandwidth values (e.g., <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM>) that are multiple of an integer or a power of an integer (e.g., <NUM>n) of the plurality of bandwidth values (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM>) that are supported by the first RAT (e.g., <NUM> wireless communication system). For example, the bandwidth value <NUM> of the second RAT (e.g., NR/<NUM> wireless communication system) is a multiple of <NUM> or a power of <NUM><NUM> of the bandwidth value <NUM> of the first RAT (e.g., <NUM> wireless communication system). In another example, the bandwidth value <NUM> of the second RAT (e.g., NR/<NUM> wireless communication system) is a multiple of <NUM> or a power of <NUM><NUM> of the bandwidth value <NUM> of the first RAT (e.g., <NUM> wireless communication system). In other examples, the bandwidth value <NUM> of the second RAT (e.g., NR/<NUM> wireless communication system) is a multiple of <NUM> or a power of <NUM><NUM> of the bandwidth value <NUM> of the first RAT (e.g., <NUM> wireless communication system).

The SRS bandwidth configurations of the second RAT (e.g., NR/<NUM> wireless communication system) may include bandwidth values that may not multiples of an integer of the bandwidth values of the SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system). For example, the bandwidth part of the second RAT (e.g., NR/<NUM> wireless communication system) may have a bandwidth based at least in part on a number of bandwidth part configured for a component carrier and/or a bandwidth of a bandwidth part of the component carrier. In an example, the second RAT (e.g., NR/<NUM> wireless communication system) may be configured with system bandwidth of <NUM>. As shown above, the SRS bandwidth configuration for a <NUM> system bandwidth of the second RAT (e.g., NR/<NUM> wireless communication system) may include a bandwidth value of <NUM>. The bandwidth value of <NUM> of the second RAT is not a multiple of an integer or a power of an integer of the bandwidth values of the SRS bandwidth configurations for the first RAT (e.g., <NUM> wireless communication system). Other example of bandwidth values (e.g., <NUM>, <NUM>, and/or <NUM>) may be used for a wideband component carrier (e.g., a bandwidth of <NUM>).

In order to support frequency hopping operation by the UE, the bandwidth values of the SRS bandwidth configurations may be selected to be approximately multiple of or a power of an integer (e.g., <NUM> or <NUM>) smaller than of the maximum bandwidth value of the SRS bandwidth configurations. Continuing from the example above, the SRS bandwidth configurations of the second RAT (e.g., NR/<NUM> wireless communication system) may include a bandwidth value of <NUM> which is half (e.g., <NUM> times smaller or <NUM> bandwidth parts for frequency hopping) of the maximum bandwidth value of <NUM> in order to support frequency hopping by the UEs. For a SRS bandwidth configuration having a maximum bandwidth value of <NUM>, a quarter (e.g., <NUM> times smaller or <NUM> bandwidth parts for frequency hopping) of the maximum bandwidth value of <NUM> would be a bandwidth value of <NUM>. However, bandwidth value of <NUM> is not support by the SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system).

In order to achieve frequency hopping for a partial band, two approximately equal bandwidth values from the first RAT (e.g., <NUM> wireless communication system) may be configured for the SRS bandwidth configurations of the second RAT (e.g., NR/<NUM> wireless communication system). Continuing from the example discussed above, a SRS bandwidth configuration may have a maximum bandwidth value of <NUM>, a quarter (e.g., <NUM> times smaller or <NUM> bandwidth parts for frequency hopping) of the maximum bandwidth value of <NUM> would be a bandwidth value of <NUM>. However, bandwidth value of <NUM> is not support by the bandwidth values of the SRS bandwidth configurations of the first RAT (e.g., <NUM> wireless communication system). In this case, two approximately equal bandwidth values (e.g., bandwidth values <NUM> and <NUM>) of the first RAT (e.g., <NUM> wireless communication system) that are closest to bandwidth value <NUM> may be configured for each of the bandwidth parts. In an example, when two approximately equal bandwidth values are configured for the SRS bandwidth configurations of the bandwidth parts of the second RAT (e.g., NR/<NUM> wireless communication system), the two approximately equal bandwidth values may be configured for each bandwidth parts based at least in part on an alignment of the bandwidth parts within the component carrier. In an example, the first bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value of <NUM>, the second bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value <NUM>, the third bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value of <NUM> and the fourth bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value of <NUM>. In another example, the first bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value of <NUM>, the second bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value of <NUM>, the third bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value of <NUM> and the fourth bandwidth part may be configured with an SRS bandwidth configuration having a bandwidth value of <NUM>.

As shown below in Tables <NUM>-<NUM>, examples of various bandwidth values for a SRS bandwidth configuration that may be configured for different bandwidth parts configurations in the second RAT (e.g., NR/<NUM> wireless communication system). The bandwidth values may be configured as multiple of or a power of an integer (e.g., <NUM>) for different bandwidth parts configurations.

<FIG> is a diagram illustrating an example of <NUM> a bandwidth offset for bandwidth parts according to the claimed invention. As shown in <FIG>, a bandwidth part <NUM> (BWP1) <NUM> may be configured to serve a UE. The BWP1 <NUM> may span a bandwidth having <NUM> resource blocks (e.g., physical resource blocks (PRBs)). For BWP1 <NUM> that span a bandwidth of <NUM> PRBs, <NUM> PRBs may be available for SRS transmission by the UEs. As show in <FIG>, a number of resource blocks (e.g., <NUM> PRBs) from two ends of the BWP1 <NUM> may be configured to transmit channel information (e.g., PUCCH) and not configured for SRS transmissions.

Also shown in <FIG>, a second BWP (BWP <NUM>) <NUM> and a third BWP (BWP <NUM>) <NUM> may span a portion of the BWP <NUM><NUM>. As shown, each of the BWP <NUM><NUM> and the BWP <NUM><NUM> may span <NUM> resource blocks (e.g., PRBs). As discussed above, a number of resource blocks (e.g., <NUM> PRBs) may not be configured for SRS transmissions and therefore a bandwidth offset value may be configured for each of the bandwidth parts in order to align the operation of UEs served by the BWP <NUM><NUM>, BWP <NUM><NUM> and BPW <NUM><NUM>. For example, in order to align the operation of UEs served by BWP <NUM><NUM> and BWP <NUM><NUM> with BWP <NUM><NUM>, BWP <NUM><NUM> and BWP <NUM><NUM> may be configured with <NUM> resource blocks (e.g., PRBs) each for SRS transmissions. As shown in <FIG>, different bandwidth parts may have different a starting point for SRS transmissions. For example, BWP <NUM><NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., because of the <NUM> PRBs offset within BWP <NUM><NUM>), while resource blocks <NUM>-<NUM> (e.g., <NUM> PRBs within BWP <NUM><NUM>) are not configured for SRS transmission in order to align with operations by UEs served by the BWP <NUM><NUM>. BWP <NUM><NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., <NUM> PRB offset within BWP <NUM><NUM>), while resource blocks <NUM>-<NUM> (e.g., <NUM> PRBs within BWP <NUM><NUM>) are not configured for SRS transmission in order to align with operations by UEs served by the BWP <NUM><NUM>. As illustrated, each bandwidth parts may be configured with different bandwidth offset value to inform the UE of a start point within the bandwidth parts for SRS transmissions. According to the invention, the bandwidth offset value indicates a number of offset resource blocks (e.g., PRBs) from an edge of the bandwidth part to start SRS transmissions by the UEs. According to the above example, BWP <NUM><NUM> may be configured with a bandwidth offset value of <NUM>, while BWP <NUM><NUM> may be configured with a bandwidth offset value of <NUM>.

<FIG> is a diagram illustrating an example of <NUM> a bandwidth offset for bandwidth parts according to the claimed invention. As shown in <FIG>, a first bandwidth part (BWP1) <NUM> may span a bandwidth having <NUM> resource blocks (PRBs), a second bandwidth part (BWP2) <NUM> and a third bandwidth part (BWP <NUM>) <NUM> may span a portion of the first bandwidth part (BWP <NUM>) <NUM>, a fourth bandwidth part (BWP <NUM>) <NUM> and a fifth bandwidth part (BWP <NUM>) <NUM> may span a portion of the second bandwidth part (BWP <NUM>) <NUM>, and a sixth bandwidth part (BWP <NUM>) <NUM> and a seventh bandwidth part (BWP <NUM>) <NUM> span a portion of the third bandwidth part (BPW <NUM>) <NUM>. Similar to description above of <FIG>, each of the bandwidth parts shown in <FIG>, is configured with a bandwidth offset value within each of the bandwidth parts to indicate to the UE a starting point for SRS transmissions. For example, BWP <NUM><NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., <NUM> PRBs offset within BWP <NUM><NUM>), while resource blocks <NUM>-<NUM> (e.g., <NUM> PRBs within BWP <NUM><NUM>) are not configured for SRS transmission in order to align with operations by UEs served by the BWP <NUM><NUM>. BWP <NUM><NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., <NUM> PRB offset within BWP <NUM><NUM>), while resource blocks <NUM>-<NUM> (e.g., <NUM> PRBs within BWP <NUM><NUM>) are not configured for SRS transmissions in order to align with operations by UEs served by the BWP <NUM><NUM>.

As shown in <FIG>, the fourth bandwidth part (BWP <NUM>) <NUM>, the fifth bandwidth part (BWP <NUM>) <NUM>, the sixth bandwidth part (BWP <NUM>) <NUM> and the seventh bandwidth part (BWP <NUM>) <NUM> may be configured to have a bandwidth that span <NUM> resource blocks (e.g., PRBs). Each of the bandwidth parts (e.g., the fourth bandwidth part (BWP <NUM>) <NUM>, the fifth bandwidth part (BWP <NUM>) <NUM>, the sixth bandwidth part (BWP <NUM>) <NUM> and the seventh bandwidth part (BWP <NUM>) <NUM>) may be configured to have different bandwidth offset values to align with operations of UEs served by different bandwidth parts (e.g., the first bandwidth part (BWP <NUM>) <NUM>, the second bandwidth part (BWP <NUM>) <NUM> and the third bandwidth part (BWP <NUM>) <NUM>). In an example, the fourth bandwidth part (BWP <NUM>) <NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., <NUM> PRBs offset within BWP <NUM><NUM>), while resource blocks <NUM>-<NUM> (e.g., <NUM> PRBs within BWP <NUM><NUM>) are not configured for SRS transmission in order to align with operations of UEs served by the first bandwidth part (BWP <NUM>) <NUM> and/or the second bandwidth part (BWP <NUM>) <NUM>. BWP <NUM><NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., <NUM> PRBs offset within BWP <NUM><NUM>), while resource blocks <NUM>-<NUM> (e.g., <NUM> PRBs within BWP <NUM><NUM>) are not configured for SRS transmission in order to align with operations of UEs served by the first bandwidth part (BWP <NUM>) <NUM> and/or the second bandwidth part (BWP <NUM>) <NUM>. BWP <NUM><NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., <NUM> PRBs offset within BWP <NUM><NUM>), in order to align with operations by UEs served by the first bandwidth part (BWP <NUM>) <NUM>, the second bandwidth part (BWP2) <NUM> and/or the third bandwidth part (BWP <NUM>) <NUM>. In an example, the SRS transmission may be configured to have a <NUM>-contiguous resource block (e.g., PRBs) granularity, therefore in order to align the operation of UEs served by the third bandwidth part (BWP <NUM>) <NUM>, with UEs served by the seventh bandwidth part (BWP <NUM>) <NUM>, BWP <NUM><NUM> may be configured for SRS transmission starting at resource block <NUM> (e.g., <NUM> PRBs offset within BWP <NUM><NUM>). Also, resource blocks <NUM>-<NUM> (e.g., <NUM> PRBs within BWP <NUM><NUM>) of the seventh bandwidth part (BWP <NUM>) <NUM> are not configured for SRS transmission in order to align with UEs served by the first bandwidth part (BWP <NUM>) <NUM> and/or the third bandwidth part (BWP <NUM>) <NUM>.

Different bandwidth values for SRS bandwidth configurations may be configured for each of the bandwidth parts (e.g., the fourth bandwidth part (BWP <NUM>) <NUM>, the fifth bandwidth part (BWP <NUM>) <NUM>, the sixth bandwidth part (BWP <NUM>) <NUM> and the seventh bandwidth part (BWP <NUM>) <NUM>) based at least in part on the bandwidth offset value and/or an alignment of operations of UEs served by different bandwidth parts (e.g., the first bandwidth part (BWP <NUM>) <NUM>, the second bandwidth part (BWP <NUM>) <NUM> and the third bandwidth part (BWP <NUM>) <NUM>). In an example, because the fourth bandwidth part (BWP <NUM>) <NUM> may have a bandwidth that span <NUM> resource blocks (e.g., PRBs), the maximum bandwidth value for the SRS bandwidth configuration that can be configured for bandwidth part (BWP <NUM>) <NUM> may be bandwidth value <NUM> (e.g., <NUM> PRBs). However, the fourth bandwidth part (BWP <NUM>) <NUM> may be configured with a bandwidth offset value of <NUM> (e.g., <NUM> PRBs offset within the fourth bandwidth part (BWP) <NUM><NUM>), thus a maximum number of bandwidth values that may be available for SRS transmissions is <NUM>. Bandwidth value of <NUM> may not be included in the possible bandwidth values of the SRS bandwidth configurations and the next available bandwidth value that is part of the possible bandwidth values of the SRS bandwidth configurations may be the bandwidth value of <NUM>. Thus, the bandwidth part (BWP <NUM>) <NUM> may be configured with an SRS bandwidth configuration having a maximum bandwidth value of <NUM>. In another example, the fifth bandwidth part (BWP <NUM>) <NUM> may be configured with a bandwidth offset value of <NUM> (e.g., <NUM> PRBs offset within the fifth bandwidth part (BWP <NUM>) <NUM>)), a SRS bandwidth configuration having a bandwidth value of <NUM> may be configured for the fifth bandwidth part (BWP <NUM>) <NUM>. In an example, the sixth bandwidth part (BWP <NUM>) <NUM> may be configured with a bandwidth offset value of <NUM> (e.g., <NUM> PRB offset within the sixth bandwidth part (BWP <NUM>) <NUM>), an SRS bandwidth configuration having a bandwidth value of <NUM> may be configured for the sixth bandwidth part (BWP <NUM>) <NUM>. In another example, the seventh bandwidth part (BWP <NUM>) <NUM> may be configured with a bandwidth offset value of <NUM> (e.g., <NUM> PRB offset within the seventh bandwidth part (BWP <NUM>) <NUM>) and a <NUM> PRB (e.g., <NUM>-<NUM> PRBs of the seventh bandwidth part (BWP <NUM>) <NUM>) offset at an edge of the seventh bandwidth part (BWP <NUM>) <NUM>, an SRS bandwidth configuration having a bandwidth value of <NUM> may be configured for the seventh bandwidth part (BWP <NUM>) <NUM>.

<FIG> is a diagram illustrating an example <NUM> of managing SRS transmission in a bandwidth part according to the claimed invention. As shown in <FIG>, a UE <NUM> may communicate with a base station <NUM>. In some aspects, the UE <NUM> may correspond to one or more UEs described elsewhere herein, such as UE <NUM> and/or the like. Additionally, or alternatively, the base station <NUM> may correspond to one or more base stations described elsewhere herein, such as the base station <NUM> and/or the like.

As shown by reference number <NUM>, the base station <NUM> may identify one or more bandwidth parts of a component carrier of a cell to be allocated to serve the UE <NUM>. The base station <NUM> may inform the UE <NUM> of the one or more bandwidth part configured to serve the UE <NUM>. In some aspects, the number of bandwidth parts may be configured by the base station <NUM> per component carrier (sometimes referred to herein as a CC) to serve the UE <NUM>. For example, the UE <NUM> may be configured with a number of bandwidth parts on a single CC (e.g., a single bandwidth part, two non-contiguous bandwidth parts, and/or the like). Additionally, or alternatively, the number of bandwidth parts may apply across component carriers used by the UE <NUM>. For example, the UE <NUM> may be configured with a number of bandwidth parts across all component carriers (e.g., a single bandwidth part across all component carriers, two bandwidth parts across all component carriers, and/or the like).

As described above in connection with <FIG>, the bandwidth part may be less than a bandwidth of a component carrier, and the UE <NUM> may configure communications over the bandwidth part for SRS transmissions. In another example, the bandwidth part may span the full bandwidth of a component carrier, and the UE <NUM> may be capable of transitioning between a full bandwidth configuration, where the UE <NUM> may communicate (e.g., transmits or receives information) over an entire bandwidth of the component carrier, and a bandwidth part configuration where the UE <NUM> may communicate over less than the entire bandwidth of the component carrier.

Additionally, or alternatively, the base station <NUM> may identify a number of bandwidth parts and/or a number of CCs allocated to the UE <NUM>. In some aspects, the base station <NUM> may identify one or more bandwidth part parameters associated with the one or more bandwidth parts. For example, the one or more bandwidth part parameters may include a SRS bandwidth configuration, a bandwidth offset value and/or other bandwidth part parameters described herein. The base station <NUM> may transmit the one or more bandwidth part parameters to the UE <NUM>. Additionally, or alternatively, the UE <NUM> and the base station <NUM> may negotiate the one or more bandwidth part parameters.

For example, the UE <NUM> may indicate one or more requested bandwidth part parameters to the base station <NUM>, and the base station <NUM> may indicate one or more bandwidth part parameters to be used by the UE <NUM> during configuration of the one or more bandwidth parts. In some aspects, the base station <NUM> may confirm a bandwidth part parameter requested by the UE <NUM>. In some aspects, the base station <NUM> may override a bandwidth part parameter requested by the UE <NUM>. A bandwidth part parameter may include, for example, a SRS bandwidth configuration, a bandwidth offset value, a bandwidth for a bandwidth part, a number of bandwidth parts per component carrier, a number of bandwidth parts across component carriers, a numerology for a bandwidth part, and/or the like. In this way, bandwidth parts may be flexibly configured.

As shown by reference number <NUM>, the base station1102 may identify one or more bandwidth parts on one or more component carriers allocated to the UE <NUM>. The base station <NUM> may transmit information of the one or more bandwidth parts to the UE <NUM>. As an example, and as shown in by reference number <NUM>, the UE <NUM> may configure the one or more bandwidth parts for uplink communication (e.g., SRS transmissions) based at least in part on the received bandwidth part parameters (e.g., a SRS bandwidth configuration and/or a bandwidth offset value) of the one or more bandwidth parts. In this case, the UE <NUM> may transmit one or more communications to the base station <NUM> (e.g., a sounding reference signal (SRS), uplink control information, uplink data, and/or the like) on the configured bandwidth part(s). In some aspects, the number of bandwidth parts (e.g., for uplink communications) allocated to the UE <NUM> is based at least in part on a number of uplink control channels configured for the UE <NUM> (e.g., a number of PUCCHs configured for the UE <NUM>, a configuration of a PUCCH group for the UE <NUM>, and/or the like). For example, if the UE <NUM> is configured with a single PUCCH (e.g., on the primary CC), then the UE <NUM> may configure a single bandwidth part for uplink communications (e.g., on the primary CC). As another example, if the UE <NUM> is configured with two PUCCHs (e.g., one on the primary CC and one on a primary secondary CC), then the UE <NUM> may be configured two bandwidth parts for uplink communication (e.g., one on the primary CC and one on a primary secondary CC). In some aspects, the UE <NUM> may signal a UE capability regarding a number of supported uplink control channels (e.g., single PUCCH, dual PUCCH, and/or the like), and may be instructed by and/or may negotiate with the base station <NUM> to determine the number of bandwidth parts to be configured based at least in part on the UE capability.

Additionally, or alternatively, the UE <NUM> may configure the one or more bandwidth parts for downlink communication. In this case, the UE <NUM> may receive one or more communications from the base station <NUM> (e.g., a reference signal, a page, downlink control information, downlink data, and/or the like) on the configured bandwidth part(s). In some aspects, the number of bandwidth parts (e.g., for downlink communications) allocated to the UE <NUM> may be based at least in part on a number of uplink control channels configured for the UE <NUM>, as described above. For example, if the UE <NUM> is configured with a single PUCCH group, then the UE <NUM> may configure a single bandwidth part for downlink communications. As another example, if the UE <NUM> is configured with multiple PUCCH groups (e.g., two PUCCH groups), then the UE <NUM> may be configured with up to one bandwidth part, per PUCCH group, for downlink communications.

As described above, in some aspects, the UE <NUM> may configure the one or more bandwidth parts based at least in part on an indication from the base station <NUM>. For example, the base station <NUM> may indicate SRS resources, a SRS bandwidth configuration for each of the or more bandwidth parts and/or a bandwidth offset value. In this case, the UE <NUM> may transmit an acknowledgement (ACK) or a negative acknowledgement (NACK) to confirm receipt or failed receipt, respectively, of the indication. In some aspects, the UE <NUM> may receive the indication from the base station <NUM> via a downlink data channel (e.g., a PDSCH). In this case, the UE <NUM> may transmit an ACK using a HARQ response to the indication received via the downlink data channel. In some aspects, the UE <NUM> may not receive the indication from the base station <NUM> via a downlink data channel. For example, the UE <NUM> may receive the indication from the base station <NUM> via downlink control information (DCI) (e.g., via an explicit indication in DCI that carries a scheduling assignment and/or a grant, via an explicit indication in DCI that does not carry a scheduling assignment and/or a grant, via an implicit indication indicated by the presence of DCI, and/or the like), via a media access control (MAC) control element (CE), via radio resource control (RRC) signaling, and/or the like. In this case, the UE <NUM> may transmit an explicit ACK as an explicit response to the indication (e.g., an explicit response to the DCI, the MAC CE, and/or the like). In some aspects, the indication is at least one of an activation or a deactivation of at least one of the one or more bandwidth parts. In this way, the base station <NUM> can confirm whether the UE <NUM> is to be configured according to a configuration indication by the base station <NUM>.

As shown by reference number <NUM>, the UE <NUM> and the base station <NUM> may communicate using the one or more CCs, which may include communicating on the one or more bandwidth parts configured on the one or more CCs (e.g., on the uplink and/or the downlink, as described above). In some aspects, the UE <NUM> may configure SRS transmission on one or more bandwidth parts based at least in part on the SRS bandwidth configuration and/or the bandwidth offset value of each of the one or more bandwidth parts. The UE <NUM> may transmit the SRS within the one or more bandwidth parts allocated to the UE.

Other examples are possible and may differ from what was described in connection with <FIG>.

<FIG> is a diagram illustrating an example UE <NUM> for managing SRS transmissions in a bandwidth part according to the claimed invention. An implementation of UE <NUM> may include a variety of components, some of which have already been described above, but including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and communication component <NUM><NUM><NUM> to enable one or more of the functions described herein. Further, the one or more processors <NUM>, modem <NUM>, memory <NUM>, transceiver <NUM>, RF front end <NUM> and one or more antennas <NUM>, may be configured to support voice and/or data calls (simultaneously or non-simultaneously) in one or more radio access technologies.

In an aspect, the one or more processors <NUM> can include one or more modems <NUM> that uses one or more modem processors. The various functions related to communication component <NUM><NUM><NUM> may be included in modem <NUM> and/or processors <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver <NUM>. In other aspects, some of the features of the one or more processors <NUM> and/or modem <NUM> associated with communication component <NUM><NUM><NUM> may be performed by transceiver <NUM>.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM><NUM> or communication component <NUM><NUM><NUM> and/or one or more of its subcomponents being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random-access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a nontransitory computer-readable storage medium that stores one or more computerexecutable codes defining communication component <NUM><NUM><NUM> and/or one or more of its subcomponents, and/or data associated therewith, when UE <NUM> is operating at least one processor <NUM> to execute communication component <NUM><NUM><NUM> and/or one or more of its subcomponents.

Receiver <NUM> may include hardware, firmware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). In an aspect, receiver <NUM> may receive signals transmitted by at least one base station <NUM> (as shown in <FIG>). Additionally, receiver <NUM> may process such received signals, and may obtain measurements of the signals, such as, but not limited to, Ec/Io, SNR, RSRP, RSSI, etc. Transmitter <NUM> may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium).

Moreover, in an aspect, UE <NUM> may include RF front end <NUM>, which may operate in communication with one or more antennas <NUM> and transceiver <NUM> for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one base station <NUM> (as shown in <FIG>) or wireless transmissions transmitted by UE <NUM>.

In an aspect, RF front end <NUM> may use one or more switches <NUM> to select a LNA <NUM> and its specified gain value based on a desired gain value for an application.

In an aspect, each PA <NUM> may have a minimum and maximum gain values. In an aspect, RF front end <NUM> may use one or more switches <NUM> to select a PA <NUM> and its specified gain value based on a desired gain value for an application.

In an aspect, transceiver may be tuned to operate at specified frequencies such that UE <NUM> can communicate with, for example, one or more base stations <NUM> or one or more cells associated with one or more base stations <NUM> (as shown in <FIG>).

In an aspect, the modem configuration can be based on the mode of the modem <NUM> and the frequency band in use.

Communication component <NUM><NUM><NUM> of UE <NUM> may include a bandwidth part determiner <NUM><NUM><NUM> that enables UE <NUM> and base station <NUM> to determine how the wideband CC, e.g., the system bandwidth, can be configured to exchange signaling.

For instance, in one implementation, bandwidth part determiner <NUM><NUM><NUM> is configured to take into account a value (e.g., frequency range, such as <NUM>) of the system bandwidth, a minimum UE RF bandwidth capability (or reference capability) that is supported by base station <NUM> (e.g., a channel bandwidth of <NUM>), and an RF bandwidth capability of UE <NUM> (e.g., a maximum channel bandwidth that UE <NUM> can support), and thereby determine a UE-specific set of bandwidth parts (e.g., one or more portions of the system bandwidth) that will be used as channels or component carriers for exchanging communications. Different UEs <NUM> with different RF bandwidth capabilities may thus have differently configured UE-specific set of bandwidth parts. For example, the bandwidth part determiner <NUM> may identify one or more bandwidth parts allocated to serve the UE <NUM>.

Further, bandwidth part controller <NUM> configured to work with the modem <NUM> and/or other components of UE <NUM> to ensure signaling is based on UE-specific set of bandwidth parts allocated for each UE <NUM>. For example, the bandwidth part controller <NUM><NUM> may configure the one or more bandwidth parts based at least in part on SRS bandwidth configurations and/or bandwidth offset values for each of the one or more bandwidth parts. The bandwidth part controller <NUM><NUM> may control transmissions (e.g., uplink transmissions and downlink transmissions) by the UE <NUM>. In an example, the bandwidth part controller <NUM> may control SRS transmissions by the UE <NUM> using the one or more bandwidth parts allocated to the UE. For example, the bandwidth party controller <NUM> may identify a SRS bandwidth configuration and/or bandwidth offset value of one or more bandwidth parts allocated to the UE.

In further alternatives, communication component <NUM> of UE <NUM> may include one or more additional components to manage or control other signaling or configuration of the UE-specific set of bandwidth parts. Examples of such other components may include components managing one or more of synchronization channels and signaling, rate matching, bandwidth part aggregation, random sequence generation and usage, and configuration and interoperability of UE-specific set of bandwidth parts with channel quality channels and signaling.

<FIG> is a diagram illustrating an example base station <NUM> of managing SRS transmissions in a bandwidth part according to the claimed invention. An implementation of base station <NUM> may include a variety of components, some of which have already been described above, but including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and communication component <NUM> to enable one or more of the functions described herein.

Communication component <NUM> of base station <NUM> may include a bandwidth part determiner <NUM> that enables the base station <NUM> to determine how the wideband CC, e.g., the system bandwidth, can be configured to exchange signaling.

For instance, in one implementation, bandwidth part determiner <NUM> is configured to take into account a value (e.g., frequency range, such as <NUM>) of the system bandwidth, a minimum UE RF bandwidth capability (or reference capability) that is supported by base station <NUM> (e.g., a channel bandwidth of <NUM>), and an RF bandwidth capability of UE <NUM> (e.g., a maximum channel bandwidth that UE <NUM> can support), and thereby determine a UE-specific set of bandwidth parts (e.g., one or more portions of the system bandwidth) that will be used as channels or component carriers for exchanging communications. The bandwidth part determiner <NUM> may identify one or more bandwidth parts to be allocated to the UE <NUM>. Different UEs <NUM> with different RF bandwidth capabilities may thus have differently configured different UE-specific set of bandwidth parts.

Further, bandwidth part controller <NUM> is configured to work with modem <NUM> and/or other components of base station <NUM> to ensure signaling is based on UE-specific set of bandwidth parts allocated for each UE <NUM>. The bandwidth part controller <NUM> identify SRS bandwidth configurations and/or bandwidth offset values associated with each of the one or more bandwidth parts allocated to the UE <NUM>.

In further alternatives, communication component <NUM> of base station <NUM> may include one or more additional components to manage or control other signaling or configuration of the UE-specific set of bandwidth parts. Examples of such other components may include components managing one or more of synchronization channels and signaling, rate matching, bandwidth part aggregation, random sequence generation and usage, and configuration and interoperability of UE-specific set of bandwidth parts with channel quality channels and signaling.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE according to the claimed invention. Example process <NUM> is an example where a UE (e.g., UE <NUM>, UE <NUM>, and/or the like) performs SRS transmission in one or more bandwidth parts.

As shown in <FIG>, process <NUM> includes identifying one or more bandwidth parts of a component carrier of a cell allocated to a user equipment (block <NUM>). For example, the UE may identify a number of bandwidth parts allocated to the UE, as described above in connection with <FIG>. In some aspects, the number of bandwidth parts applies per component carrier used by the UE or across component carriers used by the UE. In an example, the bandwidth part determiner <NUM><NUM><NUM> may identify one or more bandwidth parts of a component carrier of a cell allocated to a user equipment.

As also shown in <FIG>, process <NUM> includes receiving a SRS bandwidth configuration for each of the one or more bandwidth parts (block <NUM>). The UE receives a SRS bandwidth configuration for each of the one or more bandwidth parts on one or more component carriers allocated by the UE. For example, the SRS bandwidth configuration may include a plurality of bandwidth values for transmitting SRS by the UE. In an example, at least one of the plurality of bandwidth values may include a first bandwidth value associated with a first RAT and a second bandwidth value associated with a second RAT. The UE receives a bandwidth offset value for each of the one or more bandwidth parts allocated by the UE. In an example, the bandwidth part controller <NUM><NUM> may receive a SRS bandwidth configuration for each of the one or more bandwidth parts.

As further shown in <FIG>, process <NUM> includes transmitting a SRS based at least in part on the SRS bandwidth configuration (block <NUM>). For example, the UE may configure SRS transmissions on the one or more bandwidth parts based at least in part on the SRS bandwidth configuration. Alternatively, or additionally, the UE may configure SRS transmission on the one or more bandwidth parts based at least in part on the bandwidth offset value. The UE may transmit the SRS to the base station. In an example, the bandwidth part controller <NUM><NUM> may configure a SRS based at least in part on the SRS bandwidth configuration. The transmitter <NUM> may transmit the SRS.

In some aspects, the one or more bandwidth parts are configured for downlink communications. In some aspects, the one or more bandwidth parts are configured for uplink communications. In some aspects, the UE may determine one or more numerologies corresponding to the one or more bandwidth parts. In some aspects, one or more requested bandwidth part parameters are indicated to a base station. In some aspects, the one or more requested bandwidth part parameters include at least one of: a SRS bandwidth configuration, a bandwidth offset value, a requested bandwidth for a bandwidth part of the one or more bandwidth parts, a requested number of bandwidth parts per component carrier or across component carriers, a requested numerology for a bandwidth part of the one or more bandwidth parts, or some combination thereof.

<FIG> is a diagram illustrating another example process <NUM> performed, for example, by a base station according to the claimed invention. Example process <NUM> is another example where a base station (e.g., BS <NUM>, BS <NUM>, and/or the like) performs SRS transmissions on one or more bandwidth parts.

As shown in <FIG>, process <NUM> includes identifying one or more bandwidth parts of a component carrier of a cell to be allocated to a UE (block <NUM>). For example, the base station may identify one or more component carriers of a cell. The base station may identify one or more bandwidth parts for each of the one or more component carriers of the cell. The base station may identify one or more bandwidth parts from each of the one or more component carriers of the cell to be allocated to the UE. In an example, the bandwidth part determination <NUM> may identify one or more bandwidth parts of a component carrier of a cell to be allocated to a UE.

As also shown in <FIG>, process <NUM> includes identifying a SRS bandwidth configuration for each of the one or more bandwidth parts (block <NUM>). For example, the base station may identify the SRS bandwidth configuration for each of the one or more bandwidth parts of the one or more component carriers of the cell. The SRS bandwidth configuration may include at least of bandwidth values and at least one set of the plurality of bandwidth values include a first bandwidth value of a first radio access technology (RAT) and a second bandwidth value of a second radio access technology (RAT). The base station identifies a bandwidth offset value for each of the one or more bandwidth parts of the one or more component carriers of the cell. In an example, the bandwidth part controller <NUM> may identify a SRS bandwidth configuration for each of the one or more bandwidth parts.

As further shown in <FIG>, process <NUM> include transmitting the SRS bandwidth configuration to the UE (block <NUM>). For example, the base station may transmit the SRS bandwidth configuration for each of the one or more bandwidth parts to the UE. The base station transmits the bandwidth offset value for each of the one or more bandwidth parts to the UE. In an example, the transmitter <NUM> may transmit the SRS bandwidth configuration to the UE.

In some aspects, the base station may determine a numerology corresponding to the full bandwidth configuration. In some aspects, a numerology, corresponding to the full bandwidth configuration, is signaled in association with scheduling on a data channel or a control channel. In some aspects, a first numerology corresponding to the full bandwidth configuration is different from a second numerology corresponding to the bandwidth part configuration.

Even though particular combinations of features are disclosed in the specification, these combinations are not intended to limit the disclosure. In fact, many of these features may be combined in ways not specifically disclosed in the specification.

Claim 1:
A method, the method performed by an apparatus and comprising:
identifying one or more bandwidth parts of a component carrier of a cell to be allocated to a user equipment, UE;
identifying a sounding reference signal, SRS, bandwidth configuration for each of the one or more bandwidth parts;
identifying a bandwidth offset value for each of the one or more bandwidth parts, the bandwidth offset value indicates a number of resource blocks from an edge of the respective of the one or more bandwidth parts to start SRS transmissions by the UE; and
transmitting the SRS bandwidth configuration and the bandwidth offset value to the UE.