Patent Description:
Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems, (e.g., a Long Term Evolution (LTE) system, a New Radio (NR) system, a 5th Generation (<NUM>) system, etc.). A wireless multiple-access communications system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).

As wireless communication technology advances, the bandwidth usage of wireless communications systems becomes increasingly flexible. For example, some wireless communications systems may employ a wide band channel access scheme, in which communications with UEs are scheduled within different portions of a channel according to radio frequency (RF) chain capabilities of the UEs, bandwidths supported by the UEs, and/or other considerations. In such a case, different UEs may support different bandwidths of a channel (e.g., a wide band channel). A particular UE may support a particular sub-band of the channel based at least in part on categories or capabilities of the particular UE (e.g., according to a maximum bandwidth supported by the particular UE or a range of frequencies in which the particular UE can communicate). For example, operations of the particular UE may be confined within the particular sub-band. Additionally, or alternatively, the particular UE may be associated with at least one RF chain. Moreover, a UE may be reconfigured from a first sub-band to a second sub-band dynamically and/or on as short a time scale as possible to enable power savings and adequate usage of spectrum.

However, a scheduling entity may not know wireless capabilities or characteristics (e.g., supported bandwidths, RF chain configurations, reconfiguration times, and/or the like) of the UEs for which the scheduling entity is to manage communications, which may hamper the ability of the scheduling entity to take advantage of the advances in flexible bandwidth usage described above. Therefore, it may be advantageous to a scheduling entity (e.g., a network device of the wireless communications system, such as a base station or a UE) to efficiently obtain information identifying the wireless capabilities of UEs associated with the scheduling entity, and to obtain information relating to the wireless capabilities and/or one or more channels associated with the scheduling entity. For example, when a UE supports a particular sub-band using multiple RF chains, it may be advantageous for scheduling purposes to know an RF chain capability of the UE (e.g., so that single-carrier orthogonal frequency division multiplexing (OFDM) and phase continuity can be properly configured in view of the RF chain capability). As another example, it may be advantageous to the scheduling entity to know a length of time associated with reconfiguration of a UE from a first bandwidth to a second bandwidth so that the scheduling entity can properly schedule reconfiguration of the UE.

Furthermore, when UEs are associated with different channel bandwidths, a traditional approach to synchronization signaling (e.g., using a synchronization channel broadcasted in a center frequency of the channel) may not work for all of the UEs. For example, a UE may not be capable of communicating on the center frequency of the channel, which may render the synchronization signaling unusable to the UE.

Still further, the increasingly flexible usage of bandwidth may mean that traditional reference signaling approaches are no longer effective or efficient for identification of channel measurements. For example, a scheduling entity may need channel measurements for many different sub-bands or channels, and UEs may not simultaneously be operating in all of the sub-bands or channels when the channel measurements are needed. This may lead to gaps in channel measurement.

Prior art document <NPL> relates to details of narrow band-internet of things (NB-IoT) synchronization signal design.

Prior art document <NPL> relates to a placement of NB-IoT carrier in in-band and guard-band operation modes.

Prior art document <NPL> relates to issues highlighted by RAN4 with respect to the NB-IoT channel raster design and to addressing aspects with respect to the channel design in in-band and guard band scenarios.

Prior art document <CIT> relates to techniques for minimizing the loss of radio signals transmitted on and/or received from serving cells in a multi-carrier system by selectively adapting the time instance at which a wireless terminal: (<NUM>) changes its radio frequency, RF, bandwidth or activates a second RF chain or any additional RF chain for measuring on one or more secondary serving cells, and/or (<NUM>) performs setup or release of one or more secondary serving cells. An example method, implemented in a radio network node, comprises determining a scheduling instance during which a wireless terminal is expected to be scheduled on at least one cell; and, determining a timing at which to send a setup or release command for at least one secondary cell such that the requested set up or release procedure does not coincide with the scheduling instance.

The claimed invention is defined by the independent claims.

These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements").

It is noted that while aspects may be described herein using terminology commonly associated with <NUM> and/or <NUM> wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as <NUM> and later, including New Radio (NR) technologies (e.g., a New Radio (NR) shared spectrum (SS) system (SS-NR)).

<FIG> illustrates an example of a wireless communications system <NUM>. The wireless communications system <NUM> includes base stations <NUM>, user equipment (UEs) <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> operates over a shared spectrum. The shared spectrum may be unlicensed or partially licensed to one or more network operators. Access to the spectrum may be limited and may be controlled by a separate coordination entity. In some examples, the wireless communications system <NUM> may be a Long Term Evolution (LTE) or LTE-Advanced network. In yet other examples, the wireless communications system <NUM> may be a millimeter wave (mmW) system, a new radio (NR) system, a <NUM> system, or any other successor system to LTE.

Each base station <NUM> may provide communication coverage for a respective geographic coverage area <NUM>. Communication links <NUM> shown in wireless communications system <NUM> may include uplink (UL) transmissions from a UE <NUM> to a base station <NUM>, or downlink (DL) transmissions, from a base station <NUM> to a UE <NUM>. A UE <NUM> may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE <NUM> may also be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a personal electronic device, a handheld device, a personal computer, a wireless local loop (WLL) station, an Internet of things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, an appliance, an automobile, or the like.

At least some of the base stations <NUM> (e.g., which may be an example of an evolved NodeB (eNB) or an access node controller (ANC)) may interface with the core network <NUM> through backhaul links <NUM> (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communication with the UEs <NUM>. In various examples, the base stations <NUM> may communicate, either directly or indirectly (e.g., through core network <NUM>), with each other over backhaul links <NUM> (e.g., X1, X2, etc.), which may be wired or wireless communication links.

Each base station <NUM> may also communicate with a number of UEs <NUM> through a number of other base stations <NUM>, where base station <NUM> may be an example of a smart radio head. In alternative configurations, various functions of each base station <NUM> may be distributed across various base stations <NUM> (e.g., radio heads and access network controllers) or consolidated into a single base station <NUM>.

In some examples, the wireless communications system <NUM> may be time-synchronized. In this way, different network operating entities may each operate at different time intervals within a frame of time, with each network operating entity being time-synchronized with other network operating entities. Traditionally (e.g., in an LTE network), a UE <NUM> attempting to access wireless communications system <NUM> may perform an initial cell search by detecting a primary synchronization signal (PSS) from a base station <NUM>. The PSS may enable synchronization of slot timing and may indicate a physical layer identity value. The UE <NUM> may then receive a secondary synchronization signal (SSS). The SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell. The SSS may also enable detection of a duplexing mode and a cyclic prefix length. Some systems, such as time division duplexing (TDD) systems, may transmit an SSS but not a PSS. Both the PSS and the SSS may be located in a central portion of a carrier, respectively.

In some aspects, such as aspects described herein, the base station <NUM> may transmit a synchronization signal on a single frequency of a channel (e.g., a single frequency for an entire channel) that may be located in a central portion of the channel, or may be located elsewhere in the channel. Additionally, or alternatively, as described elsewhere herein, the base station <NUM> may transmit one or more synchronization signals in multiple, different sub-bands or sub-channels that may be used by UEs with narrow RF chain capabilities or supported bandwidths.

After receiving the synchronization signal or the one or more synchronization signals (e.g., the PSS and SSS, or another synchronization signal), the UE <NUM> may receive a master information block (MIB), which may be transmitted in the physical broadcast channel (PBCH). The MIB may contain system bandwidth information, a system frame number (SFN), and a Physical Hybrid-ARQ Indicator Channel (PHICH) configuration. After decoding the MIB, the UE <NUM> may receive one or more system information blocks (SIBs). For example, SIB1 may contain cell access parameters and scheduling information for other SIBs. Decoding SIB1 may enable the UE <NUM> to receive SIB2. SIB2 may contain RRC configuration information related to random access channel (RACH) procedures, paging, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, sounding reference signal (SRS) (e.g., one or more SRSs to be transmitted by one or more antennas of the UE <NUM>), and cell barring.

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

<FIG> illustrates an example of an access network <NUM> that shares network resources, such as bandwidth of a wide band channel of an NR or <NUM> system. Access network <NUM> may include a base station <NUM>-b-<NUM>, a base station <NUM>-b-<NUM>, a UE <NUM>-b-<NUM>, and a UE <NUM>-b-<NUM>, which may be examples of the corresponding devices described with reference to <FIG>. Base station <NUM>-b-<NUM> and base station <NUM>-b-<NUM> may communicate with UEs <NUM> or other wireless devices within their respective coverage areas <NUM> and <NUM> based at least in part on allocating sub-bands or sub-channels of a channel to the UEs <NUM> according to RF chain capabilities or supported bandwidths of the UEs <NUM> and/or other factors. In some examples, access network <NUM> is operated by multiple network operating entities (e.g., network operators), and the different network operating entities may share wireless spectrum (e.g., unlicensed spectrum).

Base station <NUM>-b-<NUM> may be operated by one or more network operating entities. For example, base station <NUM>-b-<NUM> may be operated by a first network operating entity to communicate with UE <NUM>-b-<NUM> via communication link <NUM>, and base station <NUM>-b-<NUM> may be operated by a second network operating entity to communicate with UE <NUM>-b-<NUM> via communication link <NUM>. In some aspects, base station <NUM>-b-<NUM> may coordinate communications between UE <NUM>-b-<NUM> and UE <NUM>-b-<NUM>.

Base station <NUM>-b-<NUM> may also be operated by one or more network operating entities. In some examples, base station <NUM>-b-<NUM> is operated by a third network operating entity to communicate with UE <NUM>-b-<NUM> via communication link <NUM>. In this example, UE <NUM>-b-<NUM> may be configured to operate with both the second and third network operating entities. The coordination at UE <NUM>-b-<NUM> of communications between base station <NUM>-b-<NUM> and base station <NUM>-b-<NUM> may be based on a partitioned and allocated time scale between the second and third network operators.

Access to the access network <NUM>, the portioning and allocation of the resources, and/or the synchronization of the network operating entities may be controlled by a central coordinator (e.g., a spectrum access system (SAS)). In some examples, the partition and classification of resources may be autonomously determined based on the number of network operating entities. Synchronization between the network operating entities may occur explicitly through centralized signaling. Additionally or alternatively, the entities may employ a self-synchronization scheme based on "network-listening" where the wireless nodes (e.g., base stations <NUM>) from different network operating entities listen to each other and determine a timing synchronization accordingly.

<FIG> shows a block diagram of a design of base station <NUM> and UE <NUM>, which may be one of the base stations and one of the UEs in <FIG>. Base station <NUM> may be equipped with T antennas 334a through 334t, and UE <NUM> may be equipped with R antennas 352a through 352r, where in general T ≥ <NUM> and R ≥ <NUM>.

At base station <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on CQIs received from the UE, process (e.g., encode and modulate) the data for each UE based on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor <NUM> may also process system information (e.g., for SRPI, etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. Transmit processor <NUM> may also generate reference symbols for reference signals (e.g., the CRS) and synchronization signals (e.g., the PSS and SSS, and/or a synchronization signal associated with a <NUM> or NR system). A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 332a through 332t. T downlink signals from modulators 332a through 332t may be transmitted via T antennas 334a through 334t, respectively. According to certain aspects described in more detail below, the synchronization signals may be simultaneously transmitted on multiple, different frequencies of a channel associated with base station <NUM> (e.g., using multiple, different antennas <NUM>).

At UE <NUM>, antennas 352a through 352r may receive the downlink signals from base station <NUM> and/or other base stations and may provide received signals to demodulators (DEMODs) 354a through 354r, respectively. Each demodulator <NUM> may condition (e.g., filter, amplify, downconvert, and digitize) its received signal to obtain input samples. A MIMO detector <NUM> may obtain received symbols from all R demodulators 354a through 354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A channel processor may determine RSRP, RSSI, RSRQ, CQI, etc..

On the uplink, at UE <NUM>, a transmit processor <NUM> may receive and process data from a data source <NUM> and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, etc.) from controller/processor <NUM>. Processor <NUM> may also generate reference symbols for one or more reference signals. In some aspects, the one or more reference signals may include multiple reference signals to be simultaneously transmitted by UE <NUM>. In some aspects, the data from the data source <NUM> may include information identifying RF chain capabilities or supported bandwidths of UE <NUM> and/or parameters relating to RF chain capabilities or supported bandwidths of the UE <NUM>. The symbols from transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by modulators 354a through 354r (e.g., for SC-FDM, OFDM, etc.), and transmitted to base station <NUM>.

Controllers/processors <NUM> and <NUM> and/or any other component(s) in <FIG> may direct the operation at base station <NUM> and UE <NUM>, respectively, to perform techniques presented herein for synchronization, scheduling, bandwidth allocation, and reference signal transmission. For example, processor <NUM> and/or other processors and modules at base station <NUM>, may perform or direct operations of base station <NUM> to perform techniques presented herein for synchronization, scheduling, bandwidth allocation, and reference signal transmission. For example, controller/processor <NUM> and/or other controllers/processors and modules at UE <NUM> may perform or direct process <NUM> shown in <FIG>, process <NUM> shown in <FIG>, and/or process <NUM> shown in <FIG>. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. A scheduler <NUM> may schedule UEs for data transmission on the downlink and/or uplink (e.g., based at least in part on RF chain capabilities or supported bandwidths and/or parameters relating to RF chain capabilities or supported bandwidths of the UEs).

The wireless communications system may support hybrid automatic retransmission request (HARQ) for data transmission on the downlink and uplink. For HARQ, a transmitter (e.g., a base station) may send one or more transmissions of a packet until the packet is decoded correctly by a receiver (e.g., a UE) or some other termination condition is encountered. For synchronous HARQ, all transmissions of the packet may be sent in subframes of a single interlace. For asynchronous HARQ, each transmission of the packet may be sent in any subframe.

A UE may be located within the coverage of multiple base stations. One of these base stations may be selected to serve the UE. The serving base station may be selected based on various criteria, such as received signal strength, received signal quality, pathloss, etc. Received signal quality may be quantified by a signal-to-noise-and-interference ratio (SINR), or a reference signal received quality (RSRQ), or some other metric. The UE may operate in a dominant interference scenario in which the UE may observe high interference from one or more interfering base stations.

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

NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. <NUM> beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. <NUM>), 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> over a <NUM> duration. The sub-carriers or component carriers may be scheduled or provisioned for UEs <NUM> based at least in part on RF chain capabilities or supported bandwidths of the UEs <NUM> and/or parameters relating to the RF chain capabilities. These RF chain capabilities or supported bandwidths and/or parameters may be signaled by the UEs <NUM> to the base station <NUM>. Each radio frame may consist of <NUM> subframes with a length of <NUM>. Consequently, each subframe may have a length of <NUM>. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be as described in more detail below with respect to <FIG>.

Multi-layer transmissions with multiple streams per UE may be supported. NR networks may include entities, such as central units or distributed units.

The RAN may include a central unit (CU) and distributed units (DUs). A NR base station (e.g., base station <NUM>, gNB, <NUM> Node B, Node B, transmit receive point (TRP), access point (AP)) may correspond to one or multiple base stations. 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, transmission or reception on multiple antennas (e.g., MIMO or advanced receivers), or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases, DCells may not transmit synchronization signals-in some cases, DCells may transmit SS. NR base stations may transmit downlink signals to UEs (e.g., UEs <NUM>) indicating the cell type. Based on the cell type indication, the UE may communicate with a NR base station. For example, the UE may determine NR base stations to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

The ANC <NUM> may be a central unit (CU) of the distributed RAN <NUM>. The backhaul interface to neighboring next generation access nodes (NG-ANs) may terminate at the ANC <NUM>. The ANC <NUM> may include one or more TRPs <NUM> (which may also be referred to as base stations, BSs, NR BSs, Node Bs, <NUM> NBs, APs, gNB, or some other term).

The TRPs <NUM> may be connected to one ANC (ANC <NUM>) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, the TRP <NUM> may be connected to more than one ANC. A TRP <NUM> may include one or more antenna ports. The TRPs <NUM> may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE based at least in part on RF chain capabilities or supported bandwidths of the UE. In some aspects, the TRPs <NUM> may be configured to indicate that the UE is to simultaneously transmit reference signals on multiple, different frequencies using multiple antennas of the UE, which may permit the TRPs <NUM> to determine channel conditions on the multiple, different frequencies.

For example, cooperation may be preset within a TRP <NUM> and/or across TRPs <NUM> via the ANC <NUM>.

The PDCP, RLC, MAC protocol may be adaptably placed at the ANC <NUM> or TRP <NUM>.

According to certain aspects, a base station may include a central unit (CU) (e.g., ANC <NUM>) and/or one or more distributed units (e.g., one or more TRPs <NUM>).

The C-CU <NUM> may be centrally deployed.

The C-RU <NUM> may be closer to the network edge.

The DU <NUM> may be located at edges of the network with radio frequency (RF) functionality.

The control portion <NUM> may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe, and/or may identify one or more reference signals to be simultaneously transmitted by the UE. In some configurations, the control portion <NUM> may identify a bandwidth allocation of one or more sub-bands or sub-channels of a channel.

The DL data portion <NUM> may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or base station) to the subordinate entity (e.g., UE).

The DL-centric subframe may also include a common UL portion <NUM>. The common UL portion <NUM> may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion <NUM> may include feedback information corresponding to various other portions of the DL-centric subframe. For example, the common UL portion <NUM> may include feedback information corresponding to the DL data portion <NUM> and/or the control portion <NUM>. Nonlimiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion <NUM> may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), RF chain capabilities of the UE, parameters relating to RF chain capabilities of the UE, and various other suitable types of information.

As illustrated in <FIG>, the end of the DL data portion <NUM> may be separated in time from the beginning of the common UL portion <NUM>. The foregoing is merely one example of a DL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

<FIG> is a diagram <NUM> showing an example of an UL-centric subframe. The UL-centric subframe may include a control portion <NUM>. The control portion <NUM> may exist in the initial or beginning portion of the UL-centric subframe. The control portion <NUM> in <FIG> may be similar to the control portion <NUM> described above with reference to <FIG>. In some aspects, the control portion <NUM> may be a physical DL control channel (PDCCH).

The UL-centric subframe may also include an UL data portion <NUM>. The UL data portion <NUM> may sometimes be referred to as the payload of the UL-centric subframe. The UL data portion <NUM> may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or base station).

As illustrated in <FIG>, the end of the control portion <NUM> may be separated in time from the beginning of the UL data portion <NUM>.

The UL-centric subframe may also include a common UL portion <NUM>. The common UL portion <NUM> in <FIG> may be similar to the common UL portion <NUM> described above with reference to <FIG>. The common UL portion <NUM> may additionally or alternatively include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), RF chain capabilities, supported bandwidths, and various other suitable types of information. The foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

In one example, a frame may include both UL centric subframes and DL centric subframes. In this example, the ratio of UL centric subframes to DL subframes in a frame may be dynamically adjusted based on the amount of UL data and the amount of DL data that are transmitted. For example, if there is more UL data, then the ratio of UL centric subframes to DL subframes may be increased. Conversely, if there is more DL data, then the ratio of UL centric subframes to DL subframes may be decreased. Additionally, or alternatively, bandwidth allocation of the UE may be increased or decreased based on the ratio and/or quantity of UL centric subframes to DL centric subframes.

<FIG> and <FIG> illustrate examples <NUM> of bandwidth resource allocation for UEs in a wireless communication network, in accordance with aspects of the present disclosure.

As shown in <FIG>, a base station (e.g., base station <NUM>) may identify a channel to be provided to one or more UEs (e.g., UEs <NUM>). In some aspects, the channel may include a channel of a <NUM> or NR system. In such aspects, the channel may include licensed spectrum (e.g., the LTE spectrum and/or another licensed part of the radio frequency spectrum), unlicensed spectrum (e.g., WiFi spectrum, unlicensed LTE spectrum, millimeter band spectrum, short wave spectrum, and/or another part of the radio frequency spectrum), or a combination of licensed spectrum and unlicensed spectrum.

As further shown, the channel may be divided into two or more sub-bands. For example, the two or more sub-bands may be equal in bandwidth, or may be unequal in bandwidth (as shown). The base station may provision sub-bands (e.g., bandwidth) of the channel based at least in part on various factors or parameters, such as uplink or downlink traffic to be provided within the channel, priority of the uplink or downlink traffic, channel quality of the channel, capabilities of the base station and/or UEs connected with the base station, categories of the UEs connected with the base station, or the like. As one possible example, a sub-band may have a minimum size of approximately <NUM>. Other examples of sub-band size are possible, and may be implemented in practice. For example, the base station may increase or decrease a bandwidth of a sub-band, may combine multiple sub-bands to form a single sub-band, or the like.

As shown in <FIG>, sub-bands (e.g., also referred to herein as sub-channels or portions) of the channel may be provisioned or allocated for UEs <NUM>. As shown by reference number <NUM>, a first portion of the channel is allocated for downlink traffic to UE <NUM>-<NUM>. As shown by reference number <NUM>, part of the portion of the channel allocated for downlink traffic to UE <NUM>-<NUM> is also allocated for uplink traffic from UE <NUM>-<NUM>. In some aspects, the UE <NUM>-<NUM> may support any channel bandwidth (e.g., any channel bandwidth down to a particular granularity that may be defined by a specification).

In some aspects, as shown by reference number <NUM>, the portions of the channel allocated for downlink traffic and uplink traffic of UE <NUM> may be equal, as for UE <NUM>-<NUM>. In some aspects, a portion of the channel allocated for downlink traffic to a particular UE <NUM> may not overlap a portion of the channel allocated for uplink traffic from the particular UE <NUM>. In some aspects, different UEs <NUM> may support different bandwidths or maximum RF chain capabilities (e.g., <NUM>, <NUM>, etc.). These different UEs <NUM> may nevertheless be provisioned within the same channel, thus improving versatility of the NR or <NUM> system and efficiency of spectrum usage. In some aspects, all control and data operations of a UE <NUM> may be confined within the bandwidth allotted to the UE <NUM>.

In some aspects, UE <NUM> may include two or more radio frequency (RF) chains for transmitting or receiving communications within the channel. In such aspects, the base station <NUM> may allocate respective portions of the bandwidth of the channel for each of the two or more RF chains. For example, each RF chain may be allotted a respective portion of the bandwidth of the channel. In some aspects, the portions of the channel allotted for each RF chain may be equal in bandwidth. In some aspects, the portions of the channel allotted for each RF chain may have different bandwidths (e.g., based on traffic conditions, channel conditions, channel availability, etc.). In some aspects, the bandwidth allotted to the UEs <NUM> and/or RF chains of the UEs <NUM> may be reconfigured (e.g., dynamically) based at least in part on needs of the UEs <NUM>, channel conditions, or the like, to enable power savings and more efficient spectrum use. In this way, the base station may more efficiently allocate network resources and may dynamically adapt to bandwidth needs of the base station and/or the UEs.

Other examples are possible and may differ from what was described above in connection with FIGs. 10A and 10B.

<FIG> illustrate examples <NUM> of synchronization signaling, communication scheduling, and reconfiguration of allocated bandwidth resources in a wireless communication network, in accordance with aspects of the present disclosure.

As shown in <FIG>, and by reference number <NUM>, a base station <NUM> may transmit a synchronization signal (shown in <FIG> as "sync signal"). As shown, the synchronization signal may include information to be used by UE <NUM> to synchronize (e.g., connect, camp, etc.) with base station <NUM> (e.g., cell identity information, frame timing information, etc.). In some aspects, the synchronization signal may include information similar to the information included in a PSS or an SSS, as described in more detail in connection with <FIG>. In some aspects, the synchronization signal may be implemented at a particular subframe and/or slot of a frame transmitted by the base station <NUM>. For example, the particular subframe and/or slot may be a same subframe and/or slot that carries an LTE synchronization signal. Additionally, or alternatively, the synchronization signal may be transmitted in a different subframe or slot than an LTE synchronization signal.

As shown by reference number <NUM>, the synchronization signal may be transmitted at a single frequency and/or within a single sub-band (e.g., one synchronization signal per channel, at the center of the channel or elsewhere within the channel). For example, a specification may define the single frequency and/or the single sub-band, and UEs <NUM> may be configured to receive the synchronization signal at the single frequency and/or the single sub-band. In some aspects, the single frequency and/or the single sub-band may not include a frequency center of the channel, which enables UEs <NUM> that do not support the frequency center of the channel to receive the synchronization signal, thereby improving bandwidth versatility of the base station <NUM> and/or the UEs <NUM>. Further, using the single frequency and/or the sub-band may conserve resources of the base station <NUM>, as compared to transmitting synchronization signals on multiple, different frequencies or sub-bands. In some aspects, the base station <NUM> may transmit synchronization signals on multiple, different frequencies or sub-bands of a channel, which permits UEs <NUM> that are configured to receive synchronization signals on different sub-bands (e.g., UEs <NUM> with smaller RF chain capabilities) to synchronize with the base station <NUM>. As shown, the UEs <NUM>-<NUM> and <NUM>-<NUM> may receive the synchronization signal.

As shown by reference number <NUM>, the UEs <NUM> may provide information identifying RF chain capabilities of the UEs <NUM> to the base station <NUM> based at least in part on receiving the synchronization signal. An RF chain capability may identify a bandwidth on which a UE <NUM> is capable of transmitting and/or receiving network traffic or configured to transmit and/or receive network traffic. The base station <NUM> may schedule communications with the UE <NUM> based at least on part on the RF chain capability of the UE <NUM>, as described in more detail in connection with FIG. 11B, below.

In some aspects, as shown by reference number <NUM>, the UEs <NUM> may be associated with different RF chain capabilities. As shown by reference number <NUM>, in some aspects, a UE <NUM> may report an RF chain capability with regard to one or more parameters, such as RF configuration information of the UE <NUM> (e.g., an advanced receiver parameter). Here, the UE <NUM>-<NUM> may be associated with an RF chain capability of <NUM> when using <NUM>-antenna reception (e.g., 2Rx), and an RF chain capability of <NUM> when using <NUM>-antenna reception (e.g., 4Rx). For example, UE <NUM>-<NUM> may require more processor resources to perform 4Rx than 2Rx, so the RF chain capability of the UE <NUM>-<NUM> when performing 4Rx may be less than the RF chain capability of the UE <NUM>-<NUM> when performing 2Rx.

In some aspects, the information identifying the RF chain capabilities and/or parameters associated with the RF chain capabilities may be provided via a particular bandwidth. For example, the particular bandwidth may include a bandwidth within which control signaling is performed, irrespective of a bandwidth configuration of the UE <NUM> at a given time. In some aspects, the particular bandwidth may be defined based at least in part on a specification. Additionally, or alternatively, the particular bandwidth may be configured by the network (e.g., a scheduling entity) according to capabilities of the UE <NUM>.

As shown by reference number <NUM>, a UE <NUM> may report a total RF chain capability, a contiguous RF chain capability, and/or information identifying an RF chain capability distribution of the UE <NUM>. Here, the UE <NUM>-<NUM> may be associated with a total RF chain capability of <NUM> and an RF chain capability distribution of <NUM>/<NUM>/<NUM>. The RF chain capability distribution may indicate that the UE <NUM>-<NUM> is capable of receiving or transmitting data via three bandwidth allotments of <NUM>, <NUM>, and <NUM>, respectively.

As shown by reference number <NUM>, the UEs <NUM> may provide information identifying a bandwidth reconfiguration time. For example, the base station <NUM> may reconfigure provisioning of one or more sub-bands of the channel based at least in part on uplink or downlink traffic and/or other factors. In such a case, a UE <NUM> may take a particular amount of time to reconfigure from a first bandwidth provisioned by the base station <NUM> to a second bandwidth provisioned by the base station <NUM>. The bandwidth reconfiguration time may identify the particular length of time. Here, the UE <NUM>-<NUM> signals that UE <NUM>-<NUM> can reconfigure in <NUM>, and the UE <NUM>-<NUM> signals that the UE <NUM>-<NUM> can reconfigure in <NUM>. In some aspects, the UEs <NUM> may provide information identifying the RF chain capabilities and/or the parameters associated with the RF chain capabilities via a physical control channel (e.g., PUCCH, PUSCH, or uplink control channel). Additionally, or alternatively, the UEs <NUM> may provide the information identifying the RF chain capabilities and/or the parameters associated with the RF chain capabilities via a higher-level channel, such as a channel associated with the radio resource control (RRC) layer.

As shown in <FIG>, and by reference number <NUM>, the base station <NUM> may schedule and/or demodulate communications with the UEs <NUM>-<NUM> and <NUM>-<NUM> based at least in part on the RF chain capabilities of the UEs <NUM>-<NUM> and <NUM>-<NUM>. As shown by reference number <NUM>, the base station <NUM> may schedule communications on portions of the channel for uplink and/or downlink communication with the UEs <NUM>-<NUM> and <NUM>-<NUM>. Here, the base station <NUM> schedules communications on approximately equal portions of the channel for UEs <NUM>-<NUM> and <NUM>-<NUM>. In some aspects, the base station <NUM> may schedule communications on unequal sub-bands or portions of the channel UEs <NUM>. For example, the base station <NUM> may schedule communications on sub-bands of the channel based at least in part on the RF chain capability distribution of UE <NUM>-<NUM>. Additionally, or alternatively, the base station <NUM> may determine whether UE <NUM>-<NUM> is to receive downlink traffic using a 2Rx configuration or a 4Rx configuration, and may schedule communications with the UE <NUM>-<NUM> appropriately (e.g., may schedule communications on a <NUM> band when the UE <NUM>-<NUM> is to use a 2Rx configuration, and may schedule communications on a <NUM> band when the UE <NUM>-<NUM> is to use a 4Rx configuration).

As shown in <FIG>, and by reference number <NUM>, the base station <NUM> may determine that high priority traffic is scheduled for transmission to UE <NUM>-<NUM>. Accordingly, the base station <NUM> may reconfigure the scheduled bandwidth distribution associated with the UEs <NUM>-<NUM> and <NUM>-<NUM>.

As shown by reference number <NUM>, the base station <NUM> may provide configuration information to the UEs <NUM> to enable reconfiguration of operating bandwidths of the UEs <NUM> according to the scheduled bandwidth distribution. The configuration information may identify updated scheduling information indicating that the UEs <NUM> are to be reconfigured from first bandwidths, scheduled as shown in <FIG>, to new bandwidths that are determined based at least in part on the high-priority traffic scheduled for transmission to UE <NUM>-<NUM>. In some aspects, the base station <NUM> may provide the configuration information via a physical control channel (e.g., a downlink control channel, such as PDCCH). Additionally, or alternatively, the base station <NUM> may provide the configuration information via a higher-level channel, such as a channel associated with the radio resource control (RRC) layer.

As further shown, the base station <NUM> provides the configuration information to UE <NUM>-<NUM> at a time T = -<NUM>, which matches the bandwidth reconfiguration time provided by the UE <NUM>-<NUM> in connection with <FIG>, above. As shown, the base station <NUM> provides the configuration information to the UE <NUM>-<NUM> at a time T = -<NUM>, which matches the bandwidth reconfiguration time provided by the UE <NUM>-<NUM> in connection with <FIG>, above. In this way, the base station <NUM> permits the UEs <NUM>-<NUM> and <NUM>-<NUM> to be reconfigured to the new bandwidths or updated scheduling information simultaneously, thus improving performance of the base station <NUM> and the UEs <NUM>-<NUM> and <NUM>-<NUM>.

In some aspects, the base station <NUM> may provide the configuration information to the UEs <NUM> simultaneously, and may provide information indicating a time at which the UEs <NUM> are to be reconfigured, which may cause simultaneous reconfiguration of the UEs <NUM>. Additionally, or alternatively, the base station <NUM> may perform implicit signaling through resource allocation. For example, the base station <NUM> may determine that the UEs <NUM> are capable of reconfiguring within a threshold length of time (e.g., a length time shorter than a time gap between reception, by the UEs <NUM>, of uplink control information and/or downlink control information and transmission or reception of data on the new bandwidths). In such a case, the base station <NUM> may reallocate the bandwidths to the new bandwidths without transmitting the configuration information to the UEs <NUM>. The UEs <NUM> may reconfigure to the new bandwidths based at least in part on receiving uplink control information or downlink control information identifying the new bandwidths, and may transmit or receive the data on the new bandwidths. In this way, the base station <NUM> reconfigures the bandwidths associated with the UEs <NUM> "on the fly," which reduces time and network overhead associated with reconfiguring the UEs <NUM>.

As shown by reference number <NUM>, the base station <NUM> increases an uplink/downlink bandwidth of the UE <NUM>-<NUM>, and decreases an uplink/downlink bandwidth of the UE <NUM>-<NUM>. Assume that the UEs <NUM>-<NUM> and <NUM>-<NUM> perform reconfiguration operations to receive or transmit traffic within the reconfigured uplink/downlink bandwidths. In this way, the base station <NUM> dynamically reconfigures the channel to provide traffic to UEs <NUM>-<NUM> and <NUM>-<NUM>, which improves utilization of network resources and improves performance of UEs <NUM>-<NUM> and <NUM>-<NUM>.

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

<FIG> illustrates an example <NUM> of synchronization signaling, communication scheduling, and reconfiguration of allocated bandwidth resources in a wireless communication network, in accordance with aspects of the present disclosure.

As shown in <FIG>, and by reference number <NUM>, a base station <NUM> may configure uplink MIMO with regard to particular sub-bands of a channel (e.g., sub-bands <NUM>, <NUM>, <NUM>, and <NUM>). To configure the uplink MIMO, the base station <NUM> may determine channel quality values for the particular sub-bands based on causing a UE <NUM> to transmit sounding reference signals (SRSs) on the particular sub-bands. For example, <NUM> and/or NR systems (e.g., <NUM> and/or NR systems associated with higher frequencies) may be implemented using TDD and/or channel reciprocity, and may rely on SRSs transmitted by the UE <NUM> to perform channel measurements outside the sub-channel on which traffic associated with the UE <NUM> is scheduled.

As shown by reference number <NUM>, the particular sub-bands of the channel do not overlap bandwidth of a data uplink or downlink that is allocated to the UE <NUM>. As further shown, the UE <NUM> is a <NUM>-antenna UE <NUM>, indicating that the UE <NUM> is capable of simultaneously transmitting SRSs on four frequencies.

As shown by reference number <NUM>, the base station <NUM> may provide, to the UE <NUM>, scheduling information indicating that the UE <NUM> is to transmit the SRSs within the particular sub-bands. As shown by reference number <NUM>, the UE <NUM> transmits the SRSs within the particular sub-bands. Notably, the particular sub-bands are not associated with bandwidth of a data uplink or downlink of the UE <NUM>, which permits the base station <NUM> to determine the channel quality conditions for bands of the channel that are not allocated to UEs <NUM>. Assume that the base station <NUM> receives the SRSs on the particular sub-bands.

As shown by reference number <NUM>, the base station <NUM> may use reference information, determined using the SRSs (e.g., channel quality information, channel noise information, etc.) to configure an uplink MIMO operation of the base station <NUM>. In this way, the base station <NUM> causes the UE <NUM> to provide SRSs for portions of the channel that are not allocated to the UE <NUM>, which improves versatility and efficiency of testing channel quality, for example, in higher-frequency <NUM> and/or NR systems that use TDD and/or channel reciprocity.

<FIG> is a flow chart of a method <NUM> for wireless communication. The method <NUM> may be performed by a base station (e.g., the base station <NUM> of <FIG>) or a UE (e.g., the UE <NUM> of <FIG>).

At <NUM>, the base station may identify a channel that supports communications with a plurality of UEs. In some aspects, the channel may include a channel of a <NUM> or NR system. In some aspects, the channel may include sub-bands of bandwidth to be used to receive and/or transmit data of the UEs. For example, the base station may provision one or more particular sub-bands or particular sub-channels to each of the UEs for communication with the base station. In some aspects, the UEs may support different bandwidths on the channel. At least two UEs, of the plurality of UEs, may support different bandwidths on the channel.

At <NUM>, the base station may identify one or more sub-channels of the channel based at least in part on different RF chain capabilities of the plurality of UEs. For example, the base station may identify a set of sub-channels on which each of the UEs is capable of receiving a synchronization signal, and may identify the set of sub-channels as the one or more sub-channels. In some aspects, the one or more sub-channels may not overlap a particular sub-channel within which communications with the UEs are scheduled.

At <NUM>, the base station may transmit at least two synchronization signals in the one or more sub-channels of the channel. For example, the base station may transmit at least two synchronization signals in one or more sub-channels (e.g., one or more sub-bands of the channel). At least one sub-channel, of the one or more sub-channels, may not be centered in the channel. For example, the at least one sub-channel may not be located at a frequency center of the channel to permit each UE of the plurality of UEs to receive a synchronization signal on respective supported bandwidths of the plurality of UEs. In some aspects, the base station may transmit a single synchronization signal at a particular frequency, sub-channel, or bandwidth. In some aspects, the base station may transmit a plurality of synchronization signals at a plurality of different frequencies, sub-channels, and/or bandwidths. In such aspects, at least two sub-channels, of the plurality of sub-channels, may not overlap with each other.

At <NUM>, the base station may receive information identifying a particular RF chain capability associated with a particular UE. For example, UEs, of the plurality of UEs, may provide information identifying respective RF chain capabilities of the UEs. The RF chain capabilities may identify supported bandwidths, retuning capabilities, and/or the like. The base station may use the RF chain capabilities to schedule communications with the UEs, as described in more detail below.

In some aspects, an uplink communication associated with a particular UE, of the plurality of UEs, is associated with a first bandwidth of the channel, and a downlink communication associated with the particular UE is associated with a second bandwidth of the channel, wherein the first bandwidth is different than the second bandwidth. In some aspects, a bandwidth associated with a particular UE, of the plurality of UEs, is split between at least two sub-channels of the one or more sub-channels, wherein the at least two sub-channels are not adjacent.

At <NUM>, the base station may schedule communications with the particular UE in a particular sub-channel based at least in part on the particular RF chain capability. For example, the base station may schedule communications with the particular UE (and/or other UEs of the plurality of UEs) based at least in part on the particular RF chain capability associated with the particular UE. In some aspects, the base station may allocate uplink or downlink resources for the plurality of UEs based at least in part on the respective RF chain capabilities. Additionally, or alternatively, the base station may determine an amount of time associated with switching bandwidths based at least in part on the RF chain capabilities, and may schedule communications with the particular UE based at least in part on the amount of time.

Although <FIG> shows example blocks of a method of wireless communication, in some aspects, the method may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those shown in <FIG>. Additionally, or alternatively, two or more blocks shown in <FIG> may be performed in parallel. Additionally, or alternatively, dashed outlines of certain blocks of <FIG> may indicate that the action or operation corresponding to the blocks is optional, and may or may not be performed by the base station in connection with process <NUM>.

<FIG> is another flow chart of a method <NUM> for wireless communication. The method <NUM> may be performed by a base station (e.g., the base station <NUM> of <FIG>) or a UE (e.g., the UE <NUM> of <FIG>).

At <NUM>, the base station may receive, from a UE, information identifying an RF chain capability of the UE and at least one parameter related to the RF chain capability. The RF chain capability may include, for example, a total bandwidth capability of the UE, one or more respective bandwidth capabilities of one or more RF chains of the UE, and/or a contiguous bandwidth capability of the UE. For example, a particular RF chain capability may indicate that the UE includes four RF chains associated with a total bandwidth capability of <NUM>, may identify respective RF chain bandwidth capabilities of <NUM>, <NUM>, <NUM>, and <NUM> associated with the four RF chains, and/or may identify a contiguous bandwidth capability of <NUM>. The at least one parameter may identify information relating to the RF chain capability. For example, the at least one more parameter may identify a MIMO configuration of the UE, an advanced receiver configuration of the UE, and/or the like. In some aspects, the RF chain capability may identify a total bandwidth capability, and the at least one parameter may identify one or more respective bandwidth capabilities of one or more RF chains, a maximum contiguous bandwidth capability, a bandwidth capability distribution, or the like.

Additionally, or alternatively, the at least one parameter may identify a length of time associated with reconfiguration of the UE from a first bandwidth to a second bandwidth, a quantity of subframes and/or slots associated with reconfiguration of the UE from the first bandwidth to the second bandwidth, or the like. In such a case, the base station may use the at least one parameter to cause the UE to perform a switch from the first bandwidth to the second bandwidth at a particular time based at least in part on signaling, at an earlier time that precedes the particular time by the length of time, that the UE is to perform the switch to the second bandwidth. Additionally, or alternatively, the base station may use the at least one parameter to cause the UE to perform a switch from the first bandwidth to the second bandwidth at a particular time based at least in part on signaling that the UE is to perform the switch at the particular time. Additionally, or alternatively, the base station may use the at least one parameter to cause the UE to perform a switch from the first bandwidth to the second bandwidth at a particular time based at least in part on providing the second bandwidth to the UE at the particular time (e.g., when the UE is capable of dynamically reconfiguring bandwidth of the UE).

In some aspects, the information identifying the RF chain capability may identify a plurality of RF chain capabilities. In such a case, the at least one parameter may identify respective configurations, of a UE, corresponding to the plurality of RF chain capabilities. For example, the at least one parameter may indicate that a first RF chain capability when an advanced receiver is active on the UE, and may indicate a second RF chain capability when the advanced receiver is inactive.

At <NUM>, the base station may use the information (e.g., the information identifying the RF chain capability of the UE and the at least one parameter related to the RF chain capability) to schedule communications with the UE or to demodulate communications with the UE. In some aspects, the base station may schedule communications with the UE in a particular sub-channel of the channel based at least in part on the information. For example, a bandwidth of the particular sub-channel may correspond to (e.g., may be equal to) the RF chain capability of the UE.

At <NUM>, the base station may schedule communications with regard to a plurality of UEs based at least in part on respective RF chain capabilities of the plurality of UEs. For example, in some aspects, the information may relate to a plurality of UEs, and may identify respective RF chain capabilities of the plurality of UEs. In such a case, the base station may schedule communications with regard to the plurality of UEs based at least in part on the respective RF chain capabilities of the plurality of UEs. In some aspects, the base station may schedule the communications based at least in part on one or more of availability of part of or all of a channel associated with the plurality of UEs, power usage of one or more of the plurality of UEs, or a quantity of data associated with a buffer of one or more of the plurality of UEs.

<FIG> is another flow chart of a method for wireless communication. The method <NUM> may be performed by a base station (e.g., the base station <NUM> of <FIG>) or a UE (e.g., the UE <NUM> of <FIG>).

At <NUM>, the base station may indicate to a UE to transmit reference signals based at least in part on two or more sub-bands of the UE being associated with an uplink MIMO configuration. For example, a UE may have an uplink MIMO configuration, meaning that the UE may be capable of simultaneously transmitting a plurality of reference signals on respective sub-bands or sub-channels of a plurality of antennas associated with the uplink MIMO configuration. The base station may provide scheduling information indicating that the UE is to transmit the reference signals on the respective sub-bands or sub-channels. In such a case, the respective sub-bands or sub-channels may correspond to frequencies associated with the uplink MIMO configuration of the base station.

At <NUM>, the base station may receive the reference signals simultaneously transmitted by a plurality of antennas of a UE. For example, a plurality of antennas of a UE may simultaneously transmit reference signals (e.g., SRSs). The base station may receive the reference signals. In some aspects, the base station may use the reference signals to determine channel quality in the respective sub-bands or sub-channels in which the reference signals are transmitted. In this way, by configuring a single UE to transmit a plurality of reference signals, the base station improves efficiency of determining channel information.

At <NUM>, the base station may schedule the UE to transmit a reference signal in at least one sub-band of a channel wherein the at least one sub-band is different from a sub-band being used by the UE for data transmission. The at least one sub-band may correspond to one or more of the respective sub-bands or sub-channels described in connection with block <NUM>, above. By causing the UE to transmit one or more reference signals in the at least one sub-band, the base station improves versatility of the reference signaling process. Furthermore, the base station enables simultaneous testing of multiple different sub-bands, such as sub-bands not associated with a data connection to a UE, which improves accuracy and utility of testing information derived from the reference signals.

Although <FIG> shows example blocks of a method of wireless communication, in some aspects, the method may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those shown in <FIG>. Additionally, or alternatively, two or more blocks shown in <FIG> may be performed in parallel.

<FIG> is a conceptual data flow diagram illustrating the data flow between different modules/means/components in an example apparatus <NUM>. In some aspects, the apparatus <NUM> may be a base station (e.g., which may correspond to the base station <NUM> of <FIG>). In some aspects, the apparatus <NUM> may be a UE (e.g., which may correspond to the UE <NUM> of <FIG>). As shown, the apparatus <NUM> may include a reception component <NUM>, a scheduling component <NUM>, a signaling component <NUM>, an identifying component <NUM>, and a transmission component <NUM>.

The reception component <NUM> may receive data <NUM>, which may include information from a UE (e.g., which may correspond to the UE <NUM> of <FIG>). For example, the reception component <NUM> may receive information described in connection with <FIG> and/or <FIG>, such as information associated with an RF chain capability of the UE, reference signals transmitted by the UE, or the like. As shown, the reception component <NUM> may provide data <NUM> (e.g., which may be processed by the reception component <NUM>) as output to the scheduling component <NUM> (e.g., as data <NUM>).

The scheduling component <NUM> may receive data <NUM> from the reception component <NUM>. Based at least in part on data <NUM>, the scheduling component <NUM> may schedule communications with the UE and/or reference signals to be transmitted by the UE.

The reception component <NUM> may provide data <NUM> to the identifying component <NUM>. The data <NUM> may identify different RF chain capabilities of a plurality of UEs. The identifying component <NUM> may identify a channel that supports communications with the plurality of UEs. The identifying component <NUM> may provide data <NUM>, identifying the channel, to the scheduling component <NUM>. The scheduling component <NUM> may identify at least one synchronization signal to be transmitted on the channel by the base station based at least in part on the data <NUM>.

The scheduling component <NUM> may provide data <NUM> to the signaling component <NUM>. The data <NUM> may identify scheduling information, reference signals to be transmitted by the UE, and/or a synchronization signal to be transmitted by the base station. In some aspects, the signaling component <NUM> may determine, based on the data <NUM>, that the base station is to signal that the UE is to perform a switch from a first bandwidth to the second bandwidth. The signaling component <NUM> may provide data <NUM> to the transmission component <NUM>. The data <NUM> may identify the scheduling information, the reference signals to be transmitted by the UE, and/or the synchronization signal, and the transmission component <NUM> may use data <NUM> to interact with the UE.

The apparatus <NUM> may include additional components that perform each of the blocks of the algorithm in the aforementioned flow charts of <FIG>. As such, each block in the aforementioned flow charts of <FIG> may be performed by a component, and the apparatus <NUM> may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a non-transitory computer-readable medium for implementation by a processor, or some combination thereof.

<FIG> is a diagram illustrating an example of a hardware implementation <NUM> for an apparatus <NUM>' employing a processing system <NUM>. In some aspects, the apparatus <NUM>' may be a base station (e.g., which may correspond to the base station <NUM> of <FIG>). In some aspects, the apparatus <NUM>' may be a UE (e.g., which may correspond to the UE <NUM> of <FIG>).

The processing system <NUM> may be implemented with a bus architecture, represented generally by a bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits, including one or more processors and/or hardware modules, represented by a processor <NUM>, a computer-readable medium / memory <NUM>, a transceiver <NUM>, one or more antennas <NUM>, and the components <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception component <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission component <NUM>, and based at least in part on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM>. The components may be software modules running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the BS <NUM> and may include the memory <NUM> and/or at least one of the transmit processor <NUM>, the receive processor <NUM>, and the controller/processor <NUM>.

In one configuration, the apparatus <NUM>' for wireless communication includes means for identifying a channel that supports communications with a plurality of UEs, means for identifying one or more sub-channels of the channel based at least in part on different RF chain capabilities of the plurality of UEs, means for transmitting at least two synchronization signals in one or more sub-channels of the channel, means for receiving information identifying an RF chain capability of the UE and at least one parameter related to the RF chain capability, means for receiving information identifying a particular RF chain capability associated with a particular UE, means for using the information to schedule communications with the UE or to demodulate communications with the UE, means for scheduling communications with regard to the plurality of UEs based at least in part on respective RF chain capabilities of the plurality of UEs, means for indicating to a UE to transmit reference signals based at least in part on two or more sub-bands of the UE being associated with an uplink MIMO configuration, means for receiving reference signals simultaneously transmitted by a plurality of antennas of the UE, and/or means for scheduling the UE to transmit a reference signal in a particular sub-band of a channel that is different than a sub-band being used by the UE for data transmission. The aforementioned means may be one or more of the aforementioned modules of the apparatus <NUM> and/or the processing system <NUM> of the apparatus <NUM>' configured to perform the functions recited by the aforementioned means. As described supra, the processing system <NUM> may include the transmit processor <NUM>, the receive processor <NUM>, and/or the controller/processor <NUM>. As such, in one configuration, the aforementioned means may be the transmit processor <NUM>, the receive processor <NUM>, and/or the controller/processor <NUM> configured to perform the functions recited by the aforementioned means.

<FIG> is another flow chart of a method <NUM> for wireless communication. The method <NUM> may be performed by a wireless communication device (e.g., the UE <NUM> of <FIG>).

At <NUM>, the wireless communication device may transmit RF chain information identifying an RF chain capability of the wireless communication device and at least one parameter related to the RF chain capability. For example, the wireless communication device may transmit RF chain information identifying an RF chain capability of the wireless communication device. In some aspects, the wireless communication device may transmit at least one parameter associated with the RF chain capability. For example, in some aspects, the RF chain capability is one of a plurality of RF chain capabilities identified by the RF chain information, and the at least one parameter identifies respective multiple-input multiple-output (MIMO) configurations corresponding to the plurality of RF chain capabilities. In some aspects, the RF chain information may identify a bandwidth capability of the wireless communication device. In some aspects, the RF chain information may be transmitted on a particular bandwidth that is narrower than a communication bandwidth of the wireless communication device.

In some aspects, the at least one parameter may identify one or more of a length of time associated with reconfiguration of the wireless communication device from a first bandwidth to a second bandwidth, or a quantity of subframes and/or slots associated with reconfiguration of the wireless communication device from the first bandwidth to the second bandwidth.

At <NUM>, the wireless communication device may receive scheduling information identifying a particular sub-channel of a channel, wherein the channel supports communications with a plurality of wireless communication devices based at least in part on respective RF chain capabilities of the plurality of wireless communication devices. For example, the wireless communication device may receive scheduling information from a base station. The scheduling information may identify a particular sub-channel of a channel. The channel may support communications with the plurality of wireless communication devices (e.g., including the wireless communication device) based at least in part on respective RF chain capabilities of the plurality of wireless communication devices.

At <NUM>, the wireless communication device may communicate on the particular sub-channel based at least in part on the scheduling information. In some aspects, the wireless communication device may perform a switch from the first bandwidth to the second bandwidth at a particular time. The switch may be based at least in part on one or more of signaling, at an earlier time that precedes the particular time by the length of time, that indicates that the wireless communication device is to perform the switch to the second bandwidth, signaling that indicates that the wireless communication device is to perform the switch at the particular time, or receiving, by the wireless communication device, an allocation of the second bandwidth at the particular time when the wireless communication device is capable of dynamically reconfiguring bandwidth of the wireless communication device.

<FIG> is a conceptual data flow diagram illustrating the data flow between different modules/means/components in an example apparatus <NUM>. In some aspects, the apparatus <NUM> may be a wireless communication device (e.g., which may correspond to the UE <NUM> of <FIG>). In some aspects, the apparatus <NUM> may be a UE (e.g., which may correspond to the UE <NUM> of <FIG>). As shown, the apparatus <NUM> may include a reception component <NUM>, a communicating component <NUM>, and a transmission component <NUM>.

The reception component <NUM> may receive data <NUM>, which may include scheduling information identifying a particular sub-channel of a channel. In some aspects, the data <NUM> may be based at least in part on information transmitted by transmission component <NUM>, as described in more detail below. For example, the reception component <NUM> may receive information described in connection with <FIG>, <FIG>, and/or <FIG>, such as scheduling information indicating a bandwidth allocation and/or a manner in which to communicate with regard to the bandwidth allocation, or the like. As shown, the reception component <NUM> may provide data <NUM> (e.g., which may be processed by the reception component <NUM>) as output to the communicating component <NUM> (e.g., as data <NUM>).

The communicating component <NUM> may receive data <NUM> from the reception component <NUM>. Based at least in part on data <NUM>, the communicating component <NUM> may communicate on the particular sub-channel. In some aspects, the communicating component <NUM> may provide data <NUM> to the transmission component <NUM> to be transmitted to a wireless communication device <NUM> (e.g., an eNB <NUM> and/or the like) based at least in part on the data <NUM>.

In some aspects, the transmission component <NUM> may provide data <NUM> to the wireless communication device <NUM>. For example, the data <NUM> may include RF chain information identifying an RF chain capability of the apparatus <NUM> and at least one parameter related to the RF chain capability. In such a case, the wireless communication device <NUM> may generate data <NUM> based at least in part on the data <NUM>.

The apparatus <NUM> may include additional components that perform each of the blocks of the algorithm in the aforementioned flow charts of <FIG> and/or <NUM>. As such, each block in the aforementioned flow charts of <FIG> and/or <NUM> may be performed by a component, and the apparatus <NUM> may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a non-transitory computer-readable medium for implementation by a processor, or some combination thereof.

<FIG> is a diagram illustrating an example of a hardware implementation <NUM> for an apparatus <NUM>' employing a processing system <NUM>. In some aspects, the apparatus <NUM>' may be a UE (e.g., which may correspond to the UE <NUM> of <FIG>).

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception component <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission component <NUM>, and based at least in part on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM>, and/or <NUM>. The components may be software modules running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the UE <NUM> and may include the memory <NUM> and/or at least one of the transmit processor <NUM>, the receive processor <NUM>, and the controller/processor <NUM>.

In one configuration, the apparatus <NUM>' for wireless communication includes means for identifying a channel that supports communications with a plurality of UEs, means for transmitting at least one synchronization signal in one or more sub-channels of the channel, means for receiving information identifying an RF chain capability of the UE and at least one parameter related to the RF chain capability, means for using the information to schedule communications with the UE or to demodulate communications with the UE, means for receiving reference signals simultaneously transmitted by a plurality of antennas of a UE, and/or means for scheduling the UE to transmit a reference signal in a particular sub-band of a channel that is different than a sub-band within which the UE communicates. The aforementioned means may be one or more of the aforementioned modules of the apparatus <NUM> and/or the processing system <NUM> of the apparatus <NUM>' configured to perform the functions recited by the aforementioned means. As described supra, the processing system <NUM> may include the transmit processor <NUM>, the receive processor <NUM>, and the controller/processor <NUM>. As such, in one configuration, the aforementioned means may be the transmit processor <NUM>, the receive processor <NUM>, and the controller/processor <NUM> configured to perform the functions recited by the aforementioned means.

It is understood that the specific order or hierarchy of blocks in the processes / flow charts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flow charts may be rearranged.

Claim 1:
A method of wireless communication, comprising:
identifying, by a network device (<NUM>), a channel that supports communications with a plurality of user equipments (<NUM>), UEs,
wherein at least two UEs, of the plurality of UEs, support different bandwidths (<NUM>, <NUM>) on the channel;
transmitting, by the network device, at least two synchronization signals (<NUM>) to the at least two UEs,
wherein the at least two UEs do not support a bandwidth at a frequency center of the channel, and
wherein at least one synchronization signal, of the at least two synchronization signals, is transmitted in one or more sub-channels (<NUM>) of the channel that are not located at the frequency center of the channel; and
receiving information identifying a particular RF chain capability, of respective RF chain capabilities, associated with a particular UE of the plurality of UEs,
scheduling, by the network device, communications with regard to the plurality of UEs based at least in part on the respective radio frequency, RF, chain capabilities (<NUM>) of the plurality of UEs, wherein scheduling the communications comprises:
scheduling communications with the particular UE in a particular sub-channel of the channel based at least in part on the particular RF chain capability.