WO2021253213A1

WO2021253213A1 - Method and apparatus for wireless communication using different device capabilities for control channel and data channel

Info

Publication number: WO2021253213A1
Application number: PCT/CN2020/096287
Authority: WO
Inventors: Chao Wei; Jing LEI; Hwan Joon Kwon
Original assignee: Qualcomm Incorporated
Priority date: 2020-06-16
Filing date: 2020-06-16
Publication date: 2021-12-23

Abstract

Aspects of the present disclosure provide methods and devices for wireless communication using different device capabilities for a control channel and a data channel. A user equipment (UE) can transmit a UE capability report that indicates a first communication capability and a second communication capability. The second communication capability provides at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability. The UE can receive control information from a base station via a control channel according to the first communication capability, and communicate user data with the base station via a data channel corresponding to the control information according to the second communication capability.

Description

METHOD AND APPARATUS FOR WIRELESS COMMUNICATION USING DIFFERENT DEVICE CAPABILITIES FOR CONTROL CHANNEL AND DATA CHANNEL

TECHNICAL FIELD

The technology discussed below relates generally to wireless communication systems, and more particularly, to method and apparatus for wireless communication using different device capabilities for a control channel and a data channel.

INTRODUCTION

Fifth-generation (5G) New Radio (NR) wireless networks can support various types of wireless devices, for example, enhanced mobile broadband (eMBB) devices, ultra-reliable and low-latency communication (URLLC) devices, vehicle-to-everything (V2X) devices, etc. These devices have different capabilities and latency requirements. NR networks are scalable and can be deployed in different ways to meet various requirements, including peak throughput, latency, reliability, efficiency, and cost. Some NR communication devices have reduced capability that can lower the cost and/or complexity of the device. Examples of reduced capability devices include wearables, industrial wireless sensor networks, surveillance cameras, etc. Reduced capability devices may be called NR-Light devices in the 3rd Generation Partnership Project (3GPP) NR specifications. NR-Light devices may have smaller bandwidth capabilities, reduced number of antennas, and/or relaxed signal processing and monitoring requirements, as compared to other types of NR devices. However, a reduced capability (RedCap) wireless device may have reduced frequency diversity in communicating control and data information, limited aggregation level of a control channel, and smaller signal coverage. As the demand for mobile broadband access continues to increase, research and development continue to advance RedCap devices for wireless communication.

BRIEF SUMMARY OF SOME EXAMPLES

The following presents a summary of one or more aspects of the present disclosure, in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure, and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a form as a prelude to the more detailed description that is presented later.

One aspect of the present disclosure provides a method of wireless communication. A base station configures a control channel for transmitting control information to a user equipment (UE) . The base station transmits the control information to the UE via the control channel according to a first communication capability of the UE. The base station communicates user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE. The second communication capability provides at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability.

Another aspect of the present disclosure provides a method of wireless communication at a user equipment (UE) . The UE transmits a UE capability report to a base station. The capability report indicates a first communication capability and a second communication capability of the UE. The second communication capability provides at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability. The UE receives control information from the base station via a control channel according to the first communication capability. The UE can communicate user data with the base station via a data channel corresponding to the control information according to the second communication capability.

Another aspect of the present disclosure provides a base station for wireless communication. The base station includes a communication interface configured to communicate with a user equipment (UE) , a memory, and a processor operatively coupled with the communication interface and the memory. The processor and the memory are configured to configure a control channel for transmitting control information to the UE. The processor and the memory are configured to transmit the control information to the UE via the control channel according to a first communication capability of the UE. The processor and the memory are configured to communicate user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE. The second communication capability provides at least one of a smaller channel bandwidth or fewer RF chains than the first communication capability.

Another aspect of the disclosure provides a user equipment (UE) for wireless communication. The UE includes a communication interface configured to communicate with a base station, a memory, and a processor operatively coupled with the communication interface and the memory. The processor and the memory are configured to transmit a UE capability report to the base station. The UE capability report indicates a first communication capability and a second communication capability of the UE. The second communication capability provides at least one of a smaller channel bandwidth or fewer RF chains than the first communication capability. The processor and the memory are further configured to receive control information from the base station via a control channel according to the first communication capability. The processor and the memory are further configured to communicate user data with the base station via a data channel corresponding to the control information according to the second communication capability.

Another aspect of the disclosure provides a base station for wireless communication. The base station includes means for configuring a control channel for transmitting control information to a user equipment (UE) . The base station further includes means for transmitting the control information to the UE via the control channel according to a first communication capability of the UE. The base station further includes means for communicating user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE. The second communication capability provides at least one of a smaller channel bandwidth or fewer RF chains than the first communication capability.

Another aspect of the disclosure provides a user equipment (UE) for wireless communication. The UE includes means for transmitting a UE capability report to a base station. The UE capability report indicates a first communication capability and a second communication capability. The second communication capability provides at least one of a smaller channel bandwidth or fewer RF chains than the first communication capability. The UE further includes means for receiving control information from the base station via a control channel according to the first communication capability. The UE further includes means for communicating user data with the base station via a data channel corresponding to the control information according to the second communication capability.

Another aspect of the present disclosure provides a computer-readable storage medium comprising executable code. The code causes a base station to configure a control channel for transmitting control information to a user equipment (UE) . The code further causes the base station to transmit the control information to the UE via the control channel according to a first communication capability of the UE. The code further causes the base station to communicate user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE. The second communication capability provides at least one of a smaller channel bandwidth or fewer RF chains than the first communication capability.

Another aspect of the present disclosure provides a computer-readable storage medium comprising executable code. The code causes a user equipment (UE) to transmit a UE capability report to a base station. The UE capability report indicates a first communication capability and a second communication capability of the UE. The second communication capability provides at least one of a smaller channel bandwidth or fewer RF chains than the first communication capability. The code further causes the UE to receive control information from the base station via a control channel according to the first communication capability. The code further causes the UE to communicate user data with the base station via a data channel corresponding to the control information according to the second communication capability.

These and other aspects of the invention will become more fully understood upon a review of the detailed description, which follows. Other aspects, features, and embodiments will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary embodiments in conjunction with the accompanying figures. While features may be discussed relative to certain embodiments and figures below, all embodiments can include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments discussed herein. In similar fashion, while exemplary embodiments may be discussed below as device, system, or method embodiments it should be understood that such exemplary embodiments can be implemented in various devices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a wireless communication system according to some aspects of the present disclosure.

FIG. 2 is a conceptual illustration of a radio access network according to some aspects of the present disclosure.

FIG. 3 is a schematic illustration of an organization of wireless resources in an air interface utilizing orthogonal frequency divisional multiplexing (OFDM) according to some aspects of the present disclosure.

FIG. 4 is a schematic illustration of wireless communication between a UE and a scheduling entity using different communication capabilities according to some aspects of the present disclosure.

FIG. 5 is a schematic illustration RF bandwidth adaptation across slots for receiving a control channel and a data channel according to some aspects of the disclosure.

FIG. 6 is a schematic illustration of signaling UE capability information according to some aspects of the disclosure.

FIG. 7 is a drawing illustrating exemplary data channel frequency locations and narrow bands within a bandwidth part.

FIG. 8 is a flow chart illustrating a process for determining a slot bandwidth for a reduced capability device according to some aspects of the disclosure.

FIG. 9 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity according to some aspects of the disclosure.

FIG. 10 is a flow chart illustrating an exemplary process for wireless communication at a scheduling entity using different device capabilities for a control channel and a data channel according to some aspects of the disclosure.

FIG. 11 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity according to some aspects of the disclosure.

FIG. 12 is a flow chart illustrating an exemplary process for wireless communication at a scheduled entity using different device capabilities for a control channel and a data channel in accordance with some aspects of the present disclosure

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) . It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitution.

Aspects of the present disclosure provide methods and devices for wireless communication using different device capabilities for a control channel and a data channel. In some aspects, a reduced capability device may use a narrower bandwidth and/or fewer antennas for a data channel than a control channel.

The various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards. Referring now to FIG. 1, as an illustrative example without limitation, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By virtue of the wireless communication system 100, the UE 106 may be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.

The RAN 104 may implement any suitable wireless communication technology or technologies to provide radio access to the UE 106. As one example, the RAN 104 may operate according to 3 ^rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G. As another example, the RAN 104 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. The 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

As illustrated, the RAN 104 includes a plurality of base stations 108. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE. In different technologies, standards, or contexts, a base station may variously be referred to by those skilled in the art as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.

The radio access network 104 is further illustrated supporting wireless communication for multiple mobile apparatuses. A mobile apparatus may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS) , 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 (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be an apparatus (e.g., a mobile apparatus) that provides a user with access to network services.

Within the present document, a “mobile” apparatus need not necessarily have a capability to move, and may be stationary. The term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies. UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of a mobile apparatus include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an “Internet of things” (IoT) . A mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc. A mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc. A mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc. Still further, a mobile apparatus may provide for connected medicine or telemedicine support, e.g., health care at a distance. Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data.

Wireless communication between a RAN 104 and a UE 106 may be described as utilizing an air interface. Examples of the UE 106 include enhanced mobile broadband (eMBB) , ultra-reliable and low-latency communication (URLLC) , and reduced capability devices. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmission. In accordance with certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108) . Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. In accordance with further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 106) .

In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity 108.

Base stations 108 are not the only entities that may function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .

As illustrated in FIG. 1, a scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly, the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., a grant) , synchronization or timing information, or other control information from another entity in the wireless communication network such as the scheduling entity 108.

In general, base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between a base station 108 and the core network 102. Further, in some examples, a backhaul network may provide interconnection between the respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.

The core network 102 may be a part of the wireless communication system 100, and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC) . In other examples, the core network 102 may be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.

FIG. 2 is a conceptual illustration of a radio access network (RAN) 200 according to some aspects of the disclosure. In some examples, the RAN 200 may be the same as the RAN 104 described above and illustrated in FIG. 1. The geographic area covered by the RAN 200 may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station. FIG. 2 illustrates

macrocells

202, 204, and 206, and a small cell 208, each of which may include one or more sectors (not shown) . A sector is a sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector. In a cell that is divided into sectors, the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.

In FIG. 2, two base stations 210 and 212 are shown in

cells

202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables. In the illustrated example, the

cells

202, 204, and 126 may be referred to as macrocells, as the

base stations

210, 212, and 214 support cells having a large size. Further, a base station 218 is shown in the small cell 208 (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc. ) which may overlap with one or more macrocells. In this example, the cell 208 may be referred to as a small cell, as the base station 218 supports a cell having a relatively small size. Cell sizing can be done according to system design as well as component constraints.

It is to be understood that the radio access network 200 may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell. The

base stations

210, 212, 214, 218 provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the

base stations

210, 212, 214, and/or 218 may be the same as the base station/scheduling entity 108 described above and illustrated in FIG. 1.

FIG. 2 further includes a quadcopter or drone 220, which may be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station such as the quadcopter 220.

Within the RAN 200, the cells may include UEs that may be in communication with one or more sectors of each cell. Further, each

base station

210, 212, 214, 218, and 220 may be configured to provide an access point to a core network 102 (see FIG. 1) for all the UEs in the respective cells. For example,

UEs

222 and 224 may be in communication with base station 210;

UEs

226 and 228 may be in communication with base station 212;

UEs

230 and 232 may be in communication with base station 214 by way of RRH 216; UE 234 may be in communication with base station 218; and UE 236 may be in communication with mobile base station 220. In some examples, the

UEs

222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and/or 242 may be the same as the UE/scheduled entity 106 described above and illustrated in FIG. 1.

In some examples, a mobile network node (e.g., quadcopter 220) may be configured to function as a UE. For example, the quadcopter 220 may operate within cell 202 by communicating with base station 210.

In a further aspect of the RAN 200, sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) may communicate with each other using peer to peer (P2P) or sidelink signals 227 without relaying that communication through a base station (e.g., base station 212) . In a further example, UE 238 is illustrated communicating with UEs 240 and 242. Here, the UE 238 may function as a scheduling entity or a primary sidelink device, and UEs 240 and 242 may function as a scheduled entity or a non-primary (e.g., secondary) sidelink device. In still another example, a UE may function as a scheduling entity in a device-to-device (D2D) , peer-to-peer (P2P) , or vehicle-to-vehicle (V2V) network, and/or in a mesh network. In a mesh network example, UEs 240 and 242 may optionally communicate directly with one another in addition to communicating with the scheduling entity 238. Thus, in a wireless communication system with scheduled access to time–frequency resources and having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources.

In the RAN 200, the ability for a UE to communicate while moving, independent of its location, is referred to as mobility. The various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of an access and mobility management function (AMF, not illustrated, part of the core network 102 in FIG. 1) , which may include a security context management function (SCMF) that manages the security context for both the control plane and the user plane functionality, and a security anchor function (SEAF) that performs authentication.

In various aspects of the disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE’s connection from one radio channel to another) . In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if signal quality from a neighboring cell exceeds that from the serving cell for a given amount of time, the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell. For example, UE 224 (illustrated as a vehicle, although any suitable form of UE may be used) may move from the geographic area corresponding to its serving cell 202 to the geographic area corresponding to a neighbor cell 206. When the signal strength or quality from the neighbor cell 206 exceeds that of its serving cell 202 for a given amount of time, the UE 224 may transmit a reporting message to its serving base station 210 indicating this condition. In response, the UE 224 may receive a handover command, and the UE may undergo a handover to the cell 206.

In a network configured for UL-based mobility, UL reference signals from each UE may be utilized by the network to select a serving cell for each UE. In some examples, the

base stations

210, 212, and 214/216 may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs) , unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH) ) . The

UEs

222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal. The uplink pilot signal transmitted by a UE (e.g., UE 224) may be concurrently received by two or more cells (e.g., base stations 210 and 214/216) within the radio access network 200. Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214/216 and/or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the radio access network 200, the network may continue to monitor the uplink pilot signal transmitted by the UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds that of the signal strength or quality measured by the serving cell, the network 200 may handover the UE 224 from the serving cell to the neighboring cell, with or without informing the UE 224.

Although the synchronization signal transmitted by the

base stations

210, 212, and 214/216 may be unified, the synchronization signal may not identify a particular cell, but rather may identify a zone of multiple cells operating on the same frequency and/or with the same timing. The use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network may be reduced.

In various implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides for exclusive use of a portion of the spectrum, generally by virtue of a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides for shared use of a portion of the spectrum without need for a government-granted license. While compliance with some technical rules is generally still required to access unlicensed spectrum, generally, any operator or device may gain access. Shared spectrum may fall between licensed and unlicensed spectrum, wherein technical rules or limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs. For example, the holder of a license for a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with suitable licensee-determined conditions to gain access.

The air interface in the RAN 200 may utilize one or more duplexing algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions. Full duplex means both endpoints can simultaneously communicate with one another. Half duplex means only one endpoint can send information to the other at a time. In a wireless link, a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies. Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD) . In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g., several times per slot.

In order for transmissions over the radio access network 200 to obtain a low block error rate (BLER) while still achieving very high data rates, channel coding may be used. That is, wireless communication may generally utilize a suitable error correcting block code. In a typical block code, an information message or sequence is split up into code blocks (CBs) , and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. Exploitation of this redundancy in the encoded information message can improve the reliability of the message, enabling correction for any bit errors that may occur due to the noise or channel condition.

In 5G New Radio (NR) specifications, user data may be coded in various manners. Some data can be coded using quasi-cyclic low-density parity check (LDPC) with two different base graphs: one base graph is used for large code blocks and/or high code rates, while the other base graph is used otherwise. Control information and the physical broadcast channel (PBCH) may be coded using Polar coding, based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching. Aspects of the present disclosure may be implemented utilizing any suitable channel coding techniques. Various implementations of scheduling entities 108 and scheduled entities 106 may include suitable hardware and capabilities (e.g., an encoder, a decoder, and/or a CODEC) to utilize one or more of these channel codes for wireless communication.

The air interface in the RAN 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices. For example, 5G NR specifications provide multiple access for UL transmissions from

UEs

222 and 224 to base station 210, and for multiplexing for DL transmissions from base station 210 to one or

more UEs

222 and 224, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) . In addition, for UL transmissions, 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA) ) . However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA) , code division multiple access (CDMA) , frequency division multiple access (FDMA) , sparse code multiple access (SCMA) , resource spread multiple access (RSMA) , or other suitable multiple access schemes. Further, multiplexing DL transmissions from the base station 210 to UEs 222 and 224 may be provided utilizing time division multiplexing (TDM) , code division multiplexing (CDM) , frequency division multiplexing (FDM) , orthogonal frequency division multiplexing (OFDM) , sparse code multiplexing (SCM) , or other suitable multiplexing schemes.

Various aspects of the present disclosure will be described with reference to an OFDM waveform, schematically illustrated in FIG. 3. It should be understood by those of ordinary skill in the art that the various aspects of the present disclosure may be applied to a DFT-s-OFDMA waveform in substantially the same way as described herein below. That is, while some examples of the present disclosure may focus on an OFDM link for clarity, it should be understood that the same principles may be applied as well to DFT-s-OFDMA waveforms.

Within the present disclosure, a frame refers to a predetermined duration (e.g., 10 ms) for wireless transmissions, with each frame consisting of 10 subframes of 1 ms each. On a given carrier, there may be one set of frames in the UL, and another set of frames in the DL. Referring now to FIG. 3, an expanded view of an exemplary subframe 302 is illustrated, showing an OFDM resource grid 304. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application may vary from the example described here, depending on any number of factors. Here, time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers or tones.

The resource grid 304 may be used to schematically represent time–frequency resources for a given antenna port. That is, in a MIMO implementation with multiple antenna ports available, a corresponding multiple number of resource grids 304 may be available for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE, which is 1 subcarrier × 1 symbol, is the smallest discrete part of the time–frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as the RB 308 entirely corresponds to a single direction of communication (either transmission or reception for a given device) .

A UE generally utilizes only a subset of the resource grid 304. An RB may be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme or order chosen for the air interface, the higher the data rate for the UE.

In this illustration, the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302, with some subcarriers illustrated above and below the RB 308. In a given implementation, the subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Further, in this illustration, the RB 308 is shown as occupying less than the entire duration of the subframe 302, although this is merely one possible example.

A bandwidth part (BWP) is a subset of contiguous common PRBs. In an NR network, a UE can be configured with up to four BWPs in the uplink or four BWPs in the downlink. An additional four BWPs can be configured in a supplementary uplink. Only one BWP in the UL and one in the DL may be active at a given time, and a UE receives the PDSCH or PDCCH in an active BWP. BWP configuration parameters include numerology, frequency location, bandwidth, and control resource set (CORESET) . A CORESET is a set of physical resources (e.g., REs 306) and a set of parameters that are used to carry the PDCCH in a BWP. The CORESET can span a bandwidth smaller than the bandwidth of the BWP. Each BWP can be configured differently with its own signal characteristic, enabling more efficient use of the spectrum and more efficient use of power. For example, using a BWP with a narrower bandwidth can reduce the energy requirement than using a BWP with a wider bandwidth.

Each subframe 302 (e.g., a 1 ms subframe) may consist of one or multiple adjacent slots. In the example shown in FIG. 3, one subframe 302 includes four slots 310, as an illustrative example. In some examples, a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots having a shorter duration (e.g., 1, 2, 4, or 7 OFDM symbols) . These mini-slots may in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs.

An expanded view of one of the slots 310 illustrates the slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry control channels (e.g., PDCCH) , and the data region 314 may carry data channels (e.g., PDSCH or PUSCH) . Of course, a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. The simple structure illustrated in FIG. 3 is merely exemplary in nature, and different slot structures may be utilized, and may include one or more of each of the control region (s) and data region (s) .

Although not illustrated in FIG. 3, the various REs 306 within an RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 may also carry pilots or reference signals. These pilots or reference signals may provide for a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channels within the RB 308.

In a DL transmission, the transmitting device (e.g., the scheduling entity 108) may allocate one or more REs 306 (e.g., within a control region 412) to carry DL control information 114 in one or more physical downlink control channels (PDCCHs) and higher layer data in one or more physical downlink shared channels (PDSCHs) to one or more scheduled entities 106 (e.g., UE) . In addition, DL REs may be allocated to carry DL physical signals, such as a primary synchronization signal (PSS) ; a secondary synchronization signal (SSS) ; demodulation reference signals (DM-RS) ; phase-tracking reference signals (PT-RS) ; channel-state information reference signals (CSI-RS) ; etc.

The synchronization signals PSS and SSS (collectively referred to as SS) , and in some examples, the PBCH, may be transmitted in an SS block that includes 4 consecutive OFDM symbols, numbered via a time index in increasing order from 0 to 3. In the frequency domain, the SS block may extend over 240 contiguous subcarriers, with the subcarriers being numbered via a frequency index in increasing order from 0 to 239. Of course, the present disclosure is not limited to this specific SS block configuration. Other nonlimiting examples may utilize greater or fewer than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit a PBCH; and/or may utilize nonconsecutive symbols for an SS block, within the scope of the present disclosure.

The PDCCH may carry downlink control information (DCI) for one or more UEs in a cell. This can include, but is not limited to, power control commands, scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions.

In an UL transmission, a transmitting device (e.g., a scheduled entity 106 or UE) may utilize one or more REs 306 to carry UL control information 118 (UCI) . The UCI can originate from higher layers via one or more UL control channels, such as a physical uplink control channel (PUCCH) , a physical random access channel (PRACH) , etc., to the scheduling entity 108. Further, UL REs may carry UL physical signals that generally do not carry information originating from higher layers, such as demodulation reference signals (DM-RS) , phase-tracking reference signals (PT-RS) , sounding reference signals (SRS) , etc. In some examples, the control information 118 may include a scheduling request (SR) , i.e., a request for the scheduling entity 108 to schedule uplink transmissions. Here, in response to the SR transmitted on the control channel 118, the scheduling entity 108 may transmit downlink control information 114 that may schedule resources for uplink packet transmissions.

UL control information may also include hybrid automatic repeat request (HARQ) feedback such as an acknowledgment (ACK) or negative acknowledgment (NACK) , channel state information (CSI) , or any other suitable UL control information. HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC) . If the integrity of the transmission confirmed, an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.

In addition to control information, one or more REs 306 (e.g., within the data region 314) may be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH) ; or for an UL transmission, a physical uplink shared channel (PUSCH) .

In order for a UE to gain initial access to a cell, the RAN may provide system information (SI) characterizing the cell. This system information may be provided utilizing minimum system information (MSI) , and other system information (OSI) . The MSI may be periodically broadcast over the cell to provide the most basic information required for initial cell access, and for acquiring any OSI that may be broadcast periodically or sent on-demand. In some examples, the MSI may be provided over two different downlink channels. For example, the PBCH may carry a master information block (MIB) , and the PDSCH may carry a system information block type 1 (SIB1) . In the art, SIB1 may be referred to as the remaining minimum system information (RMSI) .

OSI may include any SI that is not broadcast in the MSI. In some examples, the PDSCH may carry a plurality of SIBs, not limited to SIB1, discussed above. Here, the OSI may be provided in these SIBs, e.g., SIB2 and above.

The channels or carriers described above and illustrated in FIGs. 1 and 3 are not necessarily all the channels or carriers that may be utilized between a scheduling entity 108 and scheduled entities 106, and those of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

These physical channels described above are generally multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TB) . The transport block size (TBS) , which may correspond to a number of bits of information, may be a controlled parameter, based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

Reduced Capability UE

Aspects of the present disclosure are directed to wireless devices with reduced capability. A reduced capability (RedCap) UE (e.g., NR-Light device) is less capable than a non-RedCap device (e.g., regular UE, eMBB UE) in one or more capabilities for wireless communication, for example, a maximum supported bandwidth, a number of receive (Rx) chains, processing power, and/or control channel monitoring requirement. A RedCap UE can have higher efficiency and reduced cost as compared to a regular wireless device.

Reduction of the maximum bandwidth and/or quantity of Rx antennas can result in coverage reduction for a RedCap UE as compared to a regular UE. Reducing UE communication bandwidth may also result in lower frequency diversity in control and data channels. Further, UE bandwidth reduction may also limit the possible aggregation level of the control channel (e.g., PDCCH) . Reduction of the number of Rx antennas or branches may result in lower coverage due to lower receiver processing gain and reduced Rx diversity. In general, reducing the number of Rx antennas can have more impact on the control channel than the data channel because the data channel can use HARQ retransmission to recover the loss of data. Reduction of UE bandwidth also needs to consider the coexistence with legacy UE, and the UE’s bandwidth needs to be at least as wide as a default CORESET (e.g., CORESET0) for the control channel. However, the RedCap UE may not need as much bandwidth for the data channel.

Use of Different Communication Capabilities for Control Channel and Data Channel

In some aspects of the present disclosure, a UE can use different communication capabilities for a control channel (e.g., PDCCH) and a data channel (e.g., PDSCH or PUSCH) . Examples of communication capabilities include communication bandwidth and quantity of receive (Rx) chains or antennas. FIG. 4 is a drawing illustrating wireless communication between a UE 106 and a scheduling entity 108 (e.g., a base station or gNB) using different communication capabilities for a control channel and a data channel. In one aspect, the UE may receive the control channel 402 (e.g., PDCCH) using a first number of RF chains (e.g., 2 Rx antennas) , and receive the data channel 404 (e.g., PDSCH) using a second number of RF chains (e.g., 1 Rx antenna) . The UE may use a wider bandwidth for the control channel than the data channel. For example, the control channel bandwidth can be as wide as a BWP or CORESET, and the data channel bandwidth can be narrower than a BWP.

Antenna Switching for Data Channel

In some aspects, a UE can switch the Rx antenna for receiving the data channel (e.g., PDSCH) while the UE may receive the control channel using two Rx antennas. For example, the UE can switch a single Rx antenna between two Rx antennas to receive the data channel transmission. Antenna switching can provide a spatial diversity gain for receiving the data channel. In one aspect, the UE can dynamically switch the Rx antenna for receiving the data channel based on the DCI or a predefined pattern. In one example, the scheduling entity can use a 1-bit field in the DCI to indicate which Rx antenna is used for receiving the scheduled PDSCH. In one aspect, the UE can dynamically switch the Rx antenna for receiving the data channel based on configuration information received in the DCI. In one aspect, the UE can switch the Rx antenna based on a slot index for the PDSCH transmission. In one example, the UE may use a first Rx antenna for odd-numbered slots and a second Rx antenna for even-numbered slots. In one aspect, the UE can switch the Rx antenna based on UE feedback. For example, the UE can measure the channels using different Rx antennas based on the DL reference signals (e.g., CSI-RS) , and provide a measurement report to the scheduling entity. Then the scheduling entity may indicate the Rx antenna switching pattern to the UE.

Bandwidth Adaption for Control Channel and Data Channel

FIG. 5 is a drawing illustrating RF bandwidth adaptation across slots for receiving a control channel and a data channel according to some aspects of the disclosure. A UE can use a first RF bandwidth for slots 502 that are used for receiving or monitoring a control channel (e.g., PDCCH) , and a second RF bandwidth for slots 504 that are used for a data channel (e.g., PDSCH) . The second bandwidth is smaller than the first bandwidth. Using a smaller RF or slot bandwidth for a data channel can reduce UE’s power consumption due to lower baseband processing requirements, e.g., post-FFT data buffering and receiver processing. In one aspect, the first bandwidth (control bandwidth) for the control channel can be as wide as a bandwidth part (BWP) , and the second bandwidth (data bandwidth) can be based on UE capability. For example, the data bandwidth can be selected to provide sufficient bandwidth for a maximum transport block size (TBS) that can be indicated in the UE capability report.

In one aspect, the UE may signal or report multiple maximum bandwidth capabilities, for example, a maximum control bandwidth for use with the control channel and a maximum data bandwidth for use with the data channel. FIG. 6 is a drawing illustrating a procedure for signaling UE capability information including multiple maximum bandwidth capabilities. Referring to FIG. 6, the scheduling entity 108 (e.g., BS or gNB) can transmit a UE capability enquiry message 602 to the UE 106 or scheduled entity. For example, the scheduling entity may transmit the UE capability enquiry message using radio resource control (RRC) signaling. In response, the UE can transmit UE capability information 604 to the scheduling entity. In one aspect, the UE may transmit the UE capability information 604 using RRC signaling. In one example, the UE capability information can include different maximum bandwidth capabilities for the control channel and data channel, respectively. In another example, the capability information can include a maximum transport block size (TBS) for the data channel supported by the UE and based on it the maximum bandwidth for the data channel can be derived. Then, the scheduling entity can configure (block 606) the BWP bandwidth based on the signaled maximum bandwidth for the control channel, and configure the maximum bandwidth for the data channel. In some aspects, the control channel and data channel may be in the same BWP or different BWPs.

In one aspect, the network (e.g., scheduling entity) may indicate whether a narrow data channel bandwidth configuration is used only for unicast communication or both unicast and broadcast communication. For example, the network may transmit an indication using RRC and/or DCI signaling. An example of unicast transmission is a PDSCH scrambled by a specific identifier, for example, Cell Radio Network Temporary Identifier (C-RNTI) . Examples of broadcast transmission are system information (SI) messages (e.g., SIB1) . For example, if the network indicates that the narrow data channel bandwidth is only used for unicast communication, the UE can use a wide bandwidth for receiving broadcast transmission (e.g., SIB1 and SI massages) on the PDSCH.

In one aspect, the network or scheduling entity can dynamically change the frequency resource location or resource allocation of the data channel when the data channel bandwidth is smaller than that of the BWP in which the data channel is located. That means the frequency location of a data channel within a BWP may not be fixed and can be different in different slots. FIG. 7 is a drawing illustrating various data channel locations in frequency within a BWP 700. The BWP 700 may be divided into three narrow bands (NB0, NB1, and NB2) , each having a bandwidth equal to the maximum data channel bandwidth supported by a RedCap UE. In one example, the scheduling entity can configure the data channel frequency location to be one of the three

frequency locations

702, 704, and 706 within NB1. In one example, the scheduling entity can dynamically change the data channel frequency location using grants (e.g., UL or DL grants in DCI) with a total bandwidth or resource block (RB) span not exceeding the configured maximum data channel bandwidth. In one example, the FDRA (FD resource allocation) field size in the DCI can be based on the configured maximum bandwidth for the data channel instead of the bandwidth of the BWP to reduce the DCI payload.

In one aspect, when the scheduling entity configures a narrow data channel bandwidth within a BWP that has a wider bandwidth, the scheduling entity may configure the UE to perform frequency hopping across the BWP or in a frequency range in a pre-configured pattern to obtain frequency diversity. For example, a data channel transmission (e.g., PUSCH or PDSCH) can hop between three

frequency locations

702, 704, and 706 in NB1.

FIG. 8 is a flow chart illustrating a process for determining a slot bandwidth for RedCap device according to some aspects of the disclosure. In one example, a scheduling entity 108 may communicate with a scheduled entity 106 (e.g., UE) using time slots (e.g., NR slots) similar to the slot 310 described above in relation to FIG. 3. At decision block 802, a scheduling entity may determine if a slot is used for control channel transmission (e.g., PDCCH) and/or data channel transmission (e.g., PDSCH/PUSCH) . At block 804, if the slot is used for control channel transmission to a scheduled entity (e.g., UE) , the scheduling entity can set the slot or RF bandwidth to be the same as the large BWP bandwidth or control channel bandwidth configured for the scheduled entity. At block 806, if the slot is used for data channel transmission only, the scheduling entity can set the slot or RF bandwidth to be the same as the data channel bandwidth configured for the scheduled entity. As discussed above, the data channel bandwidth can be narrower than the control channel bandwidth. In the slot configured with the narrow data channel bandwidth, the UE is not required to receive a signal from the scheduling entity out of the narrower data channel bandwidth.

CSI-RS bandwidth configuration

In one aspect, the scheduling entity can transmit channel-state information reference signals (CSI-RS) using different bandwidths, for example, in different slots. In one example, the scheduling entity can transmit CSI-RS that has a bandwidth equal to a BWP bandwidth to facilitate frequency-selective scheduling or frequency hopping. In one example, the scheduling entity can transmit CSI-RS that has a smaller bandwidth equal to the narrow data channel bandwidth to reduce power consumption at the UE. In one aspect, when the CSI-RS transmission overlaps with a narrow bandwidth data channel in a slot, the scheduling entity can configure the CSI-RS to use the narrower data channel bandwidth in that slot.

RF Retuning Consideration in Data Channel Resource Allocation

In one aspect, the scheduled entity (e.g., UE) can perform radio frequency (RF) retuning to facilitate the use of different RF bandwidths for channel and data channels in different slots or different frequency locations within a BWP for the data channel. Referring to FIG. 7, The scheduled entity can be configured to communicate using a data channel in one or more of the narrow bands. Five exemplary narrow data channels (e.g.,

data channels

702, 704, 706, 708, and 710) are illustrated in FIG. 7. When the UE switches among these data channels, the UE may need to perform RF tuning of its RF circuit.

To reduce the need for RF returning, a BWP can be divided into multiple narrow bands (e.g., NB0, NB1, and NB2 in FIG. 7) . Each narrow band may have a bandwidth equal to the maximum data channel bandwidth that can be supported by the UE or scheduled entity without RF retuning. If the allocated frequency resources of a data channel are all within a narrow band (e.g., NB1) , the center frequency of the data channel may be set as the center frequency of the narrow band in which the data channel is located. Therefore, the UE can switch among data channels (e.g.,

data channels

702, 704, and 706) within a narrow band without RF returning. If the resource allocation for a data channel (e.g., data channel 710) spans across two narrow bands (e.g., NB0 and NB1) , the center frequency of the data channel may be set as the center frequency location of the frequency resources of the data channel. In a slot with a control channel transmission, the center frequency of the control channel may be set as the center of the BWP or the CORESET in which the control channel is located. When the UE performs RF retuning between slots, a time gap may be present between the time slots to provide sufficient time for retuning the UE’s RF chains, for example, if the slots have different RF bandwidths.

FIG. 9 is a block diagram illustrating an example of a hardware implementation for a scheduling entity 900 employing a processing system 914. In one example, the scheduling entity 900 may be a base station (e.g., gNB) as illustrated in any one or more of FIGs. 1, 2, and/or 4.

The scheduling entity 900 may be implemented with a processing system 914 that includes one or more processors 904. Examples of processors 904 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. In various examples, the scheduling entity 900 may be configured to perform any one or more of the functions described herein. That is, the processor 904, as utilized in a scheduling entity 900, may be used to implement any one or more of the processes and procedures described and illustrated in FIGs. 4–8 and 10.

In this example, the processing system 914 may be implemented with a bus architecture, represented generally by the bus 902. The bus 902 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 914 and the overall design constraints. The bus 902 communicatively couples together various circuits including one or more processors (represented generally by the processor 904) , a memory 905, and computer-readable media (represented generally by the computer-readable medium 906) . The bus 902 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. A bus interface 908 provides an interface between the bus 902 and a transceiver 910. The transceiver 910 provides a communication interface or means for communicating with various other apparatus over a transmission medium. For example, the transceiver 910 may have one or more RF chains coupled to antennas 911 for transmitting and receiving wireless signals. Depending upon the nature of the apparatus, a user interface 912 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 912 is optional, and may be omitted in some examples, such as a base station.

In some aspects of the disclosure, the processor 904 may include circuitry configured for various functions, including, wireless communication using different device capabilities adapted for control and data channels. For example, the circuitry may be configured to implement one or more of the functions described in relation to FIGs. 4–8 and 10.

In one aspect, the processor 904 may include a bandwidth adaptation circuit 940. The bandwidth adaptation circuit 940 alone or with other circuits can perform various functions to configure, set, and control the bandwidths used for a control channel (e.g., PDCCH) and a data channel (e.g., PUSCH/PDSCH) . In one example, the bandwidth adaptation circuit 940 may configure different bandwidths for the control channel and data channel such that the data channel may use a smaller bandwidth than the control channel.

In one aspect, the processor 904 may include a communication circuit 942. The communication circuit 942 alone or with other circuits perform various functions for wireless communication between the scheduling entity and one or more scheduled entities (e.g., UEs) . In one example, the communication circuit 942 may perform various functions used to transmit control information to a scheduled entity using a first device capability. In one example, the communication circuit 942 may perform various functions used to transmit or receive user data or traffic to/from a scheduled entity (e.g., UE) using a second device capability that is different from the first device capability.

The processor 904 is responsible for managing the bus 902 and general processing, including the execution of software stored on the computer-readable medium 906. The software, when executed by the processor 904, causes the processing system 914 to perform the various functions described below for any particular apparatus. The computer-readable medium 906 and the memory 905 may also be used for storing data that is manipulated by the processor 904 when executing software.

One or more processors 904 in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium 906. The computer-readable medium 906 may be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip) , an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (e.g., a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. The computer-readable medium 906 may reside in the processing system 914, external to the processing system 914, or distributed across multiple entities including the processing system 914. The computer-readable medium 906 may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

In one or more examples, the computer-readable storage medium 906 may include software configured for various functions, including, wireless communication using different device capabilities for control and data channels. For example, the software may be configured to implement one or more of the functions described in relation to FIGs. 4–8 and 10.

In one aspect, the software may include bandwidth adaptation instructions 952. The bandwidth adaptation instructions can cause the scheduling entity 900 to perform various functions to configure, set, and control the bandwidths used for a control channel (e.g., PDCCH) and a data channel (e.g., PUSCH/PDSCH) . In one example, the bandwidth adaptation instructions 952 may cause the scheduling entity to configure different bandwidths for the control channel and data channel. In one example, the data channel may use a smaller bandwidth than the control channel.

In one aspect, the software may include communication instructions 954. The communication instructions 954 can cause the scheduling entity 900 to perform various functions for wireless communication between the scheduling entity and one or more scheduled entities. In one example, the communication instructions 954 may cause the scheduling entity 900 to perform various functions to transmit control information to a scheduled entity. In one example, the communication instructions 954 may cause the scheduling entity 900 to perform various functions to transmit or receive user data or traffic to/from a scheduled entity (e.g., UE) .

FIG. 10 is a flow chart illustrating an exemplary process 1000 for wireless communication at a scheduling entity with a scheduled entity using different communication capabilities for a control channel and a data channel in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process 1000 may be carried out by the scheduling entity 900 illustrated in FIG. 9. In some examples, the process 1000 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At block 1002, a scheduling entity 108 (e.g., gNB) can configure a control channel for transmitting control information to a UE or scheduled entity. In one example, the scheduling entity may use the communication circuit 942 to allocate DL resources (e.g., REs 306 in a control region 312 or CORESET) for the control channel (e.g., PDCCH) . The DL resources may be in a search space or CORSET in which the UE will monitor for the control channel transmission in a slot. In one aspect, the scheduling entity can broadcast a system information block (SIB) or configuration that includes various PDCCH configuration information, including the search space, bandwidth, CORESET, BWP, and various PDCCH parameters.

At block 1004, the scheduling entity can transmit control information to the UE via the configured control channel according to a first communication capability of the UE. In one aspect, the UE can use different communication capabilities for the control channel and data channel. A communication capability may include a communication bandwidth (e.g., RF bandwidth) and a number of RF chains (e.g., Rx antennas) . In one example, the scheduling entity may use the communication circuit 942 to transmit the control information via the transceiver 910.

At block 1006, the scheduling entity can communicate user data or traffic with the UE via a data channel corresponding to the control channel according to a second communication capability of the UE. In one example, the scheduling entity may use the communication circuit 942 to transmit user data (e.g., PDSCH) or receive user data (e.g., PUSCH) via the transceiver 910. In one aspect, the second communication capability provides at least one of a smaller bandwidth (e.g., RF bandwidth) or fewer RF chains (e.g., Rx antennas) than the first communication capability. In one example, the data channel has a smaller bandwidth than the control channel. In one example, the UE uses fewer antennas (e.g., a single Rx antenna) to receive the user data from the data channel and more antennas (e.g., two Rx antennas) to receive the control information from the control channel.

FIG. 11 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary scheduled entity 1100 employing a processing system 1114. In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system 1114 that includes one or more processors 1104. For example, the scheduled entity 1100 may be a user equipment (UE) as illustrated in any one or more of FIGs. 1, 2, and/or 4.

The processing system 1114 may be substantially the same as the processing system 914 illustrated in FIG. 9, including a bus interface 1108, a bus 1102, memory 1105, a processor 1104, and a computer-readable medium 1106. Furthermore, the scheduled entity 1100 may include a user interface 1112 and a transceiver 1110 substantially similar to those described above in FIG. 9. The transceiver 1110 may include one or more RF chains coupled to antennas 1111) . That is, the processor 1104, as utilized in a scheduled entity 1100, may be used to implement any one or more of the processes described and illustrated in FIGs. 4–8 and 12.

In some aspects of the disclosure, the processor 1104 may include circuitry configured for various functions, including, wireless communication using different device capabilities adapted for control and data channels. In one aspect, the processor 1104 may include a bandwidth adaptation circuit 1140. The bandwidth adaptation circuit 1140 alone or with other circuits can perform various functions to configure, set, and control the bandwidth used for a control channel (e.g., PDCCH) and a data channel (e.g., PUSCH/PDSCH) . In one example, the bandwidth adaptation circuit 1140 may configure different bandwidths for the control channel and data channel such that the data channel may use a smaller bandwidth than the control channel.

In one aspect, the processor 1104 may include a communication circuit 1142. The communication circuit 1142 alone or with other circuitry can perform various functions for wireless communication between the scheduled entity and a scheduling entity. In one example, the communication circuit 1142 may perform various functions used to receive control information from a scheduling entity. In one example, the communication circuit 1142 may perform various functions used to transmit or receive user data or traffic to/from a scheduling entity.

In one or more examples, the computer-readable storage medium 1106 may include software configured for various functions, including, wireless communication using different device capabilities adapted for control and data channels. For example, the software may be configured to implement one or more of the functions described in relation to FIGs. 4–8 and 12.

In one aspect, the software may include bandwidth adaptation instructions 1152. The bandwidth adaptation instructions can cause the scheduled entity 1100 to perform various functions to configure, set, and control the bandwidth used for a control channel (e.g., PDCCH) and a data channel (e.g., PUSCH/PDSCH) . In one example, the bandwidth adaptation instructions 1152 may cause the scheduled entity to use different bandwidths for the control channel and data channel such that the data channel may have a smaller bandwidth than the control channel.

In one aspect, the software may include communication instructions 1154. The communication instructions 1154 can cause the scheduled entity 1100 to perform various functions for wireless communication between the scheduled entity and a scheduling entity. In one example, the communication instructions 1154 may cause the scheduled entity 1100 to perform various functions to receive control information from a scheduling entity. In one example, the communication instructions 1154 may cause the scheduled entity 1100 to perform various functions to transmit or receive user data to/from a scheduling entity.

FIG. 12 is a flow chart illustrating an exemplary process 1200 for wireless communication using different device capabilities for a control channel and a data channel in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process 1200 may be carried out by the scheduled entity 1100 illustrated in FIG. 11. In some examples, the process 1200 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At block 1202, the scheduled entity (e.g., UE) can transmit a UE capability report to a scheduling entity (e.g., a base station) . The UE capability report informs the scheduling entity on the scheduled entity’s communication capabilities, for example, including UE category, supported RF bandwidths, frequencies, and quantity of RF chains. In one aspect, the UE capability report may indicate that the scheduled entity can communicate with the scheduling entity using a first communication capability for a control channel and a second communication capability for a data channel. In one aspect, the second communication capability provides at least one of a smaller channel bandwidth or fewer RF chains (e.g., Rx antennas) than the first communication capability. In one example, the scheduled entity may use the first communication capability for a PDCCH and the second communication capability for a data channel (e.g., PDSCH or PUSCH) . In one example, the scheduled entity may use the communication circuit 1142, transceiver 1110, and antennas 1111 to transmit the UE capability report to the scheduling entity.

At block 1204, the scheduled entity can receive control information from the scheduling entity via a control channel according to the first communication capability. For example, the scheduled entity may use the communication circuit 1142 and transceiver 1110 to receive a PDCCH carrying DCI. According to the first communication capability, the scheduled entity may use a wide channel bandwidth and multiple Rx antennas to receive the control information. The wide bandwidth may be the same as the bandwidth of a BWP or CORESET in which the control channel is received.

At block 1206, the scheduled entity can communicate user data with the scheduling entity via a data channel corresponding to the control information according to the second communication capability. In one example, the scheduled entity may use the communication circuit 1142, transceiver 1110, and antenna 1111 to transmit user data (PUSCH) to the scheduling entity. In one example, the scheduled entity may use the communication circuit 1142, transceiver 1110, and antenna 1111 to receive user data (PDSCH) from the scheduling entity. The scheduled entity may use fewer antennas (e.g., a single Rx antenna) to transmit/receive data to/from the data channel than the control channel.

In one configuration, the apparatus 900 for wireless communication includes means for configuring a control channel for transmitting control information to a UE; means for transmitting the control information to the UE via the control channel according to a first communication capability of the UE; and means for communicating user data with the UE via a data channel corresponding to the control channel according to a second communication capability of the UE. The second communication capability provides at least one of a smaller bandwidth or fewer Rx antennas than the first communication capability.

In one aspect, the aforementioned means may be the processor 904 shown in FIG. 9 configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.

Of course, in the above examples, the circuitry included in the processor 904 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 906, or any other suitable apparatus or means described in any one of the FIGs. 1, 2, and/or 4, and utilizing, for example, the processes and/or algorithms described herein in relation to FIGs. 4–8 and 10.

In one configuration, the apparatus 1100 for wireless communication includes means for transmitting, to a scheduling entity, a UE capability report comprising a first communication capability and a second communication capability, the second communication capability provides at least one of a smaller bandwidth or fewer Rx antennas than the first communication capability; means for receiving, from the scheduling entity, control information via a control channel according to the first communication capability; and means for communicating user data with the scheduling entity via a data channel corresponding to the control channel according to the second communication capability.

In one aspect, the aforementioned means may be the processor1104 shown in FIG. 11 configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.

Of course, in the above examples, the circuitry included in the processor 1104 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 1106, or any other suitable apparatus or means described in any one of the FIGs. 1, 2, and/or 4, and utilizing, for example, the processes and/or algorithms described herein in relation to FIGs. 4–8 and/or 12.

Several aspects of a wireless communication network have been presented with reference to an exemplary implementation. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE) , the Evolved Packet System (EPS) , the Universal Mobile Telecommunication System (UMTS) , and/or the Global System for Mobile (GSM) . Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2) , such as CDMA2000 and/or Evolution-Data Optimized (EV-DO) . Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Ultra-Wideband (UWB) , Bluetooth, and/or other suitable systems. The actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

Within the present disclosure, the word “exemplary” is used to mean “serving as an example, instance, or illustration. ” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. The term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another-even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object. The terms “circuit” and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure.

One or more of the components, steps, features and/or functions illustrated in FIGs. 1–12 may be rearranged and/or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from novel features disclosed herein. The apparatus, devices, and/or components illustrated in FIGs. 1–12 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware.

It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Unless specifically stated otherwise, the term “some” refers to one or more. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

A method of wireless communication, comprising:

configuring a control channel for transmitting control information to a user equipment (UE) ;

transmitting the control information to the UE via the control channel according to a first communication capability of the UE; and

communicating user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability.
The method of claim 1, further comprising:

receiving UE capability information comprising a maximum control bandwidth of the control channel and a maximum data bandwidth of the data channel,

wherein the maximum data bandwidth is based on a maximum transport block size (TBS) supported by the UE.
The method of claim 2, further comprising:

transmitting a configuration of a bandwidth part (BWP) to the UE, wherein a bandwidth of the BWP is based on the maximum control bandwidth; and

communicating the user data within the bandwidth part.
The method of claim 3, wherein communicating the user data comprises:

changing a frequency location associated with the data channel from a first frequency to a second frequency within the bandwidth part.
The method of claim 3, wherein communicating the user data comprises:

communicating the user data using one or more narrow bands among a plurality of narrow bands included in the bandwidth part, each narrow band having a bandwidth equal to the maximum data bandwidth.
The method of claim 2, wherein communicating the user data comprises:

communicating the user data in a first bandwidth part that is different from a second bandwidth part associated with the control channel, wherein a bandwidth of the first bandwidth part is based on the maximum data bandwidth.
The method of claim 1, wherein communicating the user data comprises:

indicating whether the second communication capability is used for unicast communication or for both unicast and broadcast communication.
The method of claim 1, further comprising:

determining a first radio frequency (RF) bandwidth of a first slot according to a maximum bandwidth of the control channel if the first slot is configured for monitoring the control channel;

determining a second RF bandwidth of a second slot according to a maximum bandwidth of the data channel if the second slot is configured for monitoring the data channel without the control channel; and

communicating with the UE using the first slot for the control channel, followed by the second slot for the data channel.
The method of claim 1, further comprising:

transmitting a configuration of channel-state information reference signals (CSI-RS) , wherein a bandwidth of the CSI-RS is independent of a bandwidth of the data channel.
A method of wireless communication at a user equipment (UE) , comprising:

transmitting, to a base station, a UE capability report indicating a first communication capability and a second communication capability of the UE, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability;

receiving, from the base station, control information via a control channel according to the first communication capability; and

communicating user data with the base station via a data channel corresponding to the control information according to the second communication capability.
The method of claim 10, wherein the UE capability report comprises a maximum control bandwidth of the control channel and a maximum data bandwidth of the data channel, wherein the maximum data bandwidth is based on a maximum transport block size (TBS) supported by the UE.
The method of claim 11, further comprising:

receiving a configuration of a bandwidth part (BWP) , wherein a bandwidth of the BWP is based on the maximum control bandwidth; and

communicating the user data within the bandwidth part.
The method of claim 12, wherein communicating the user data comprises:

changing a frequency location associated with the data channel from a first frequency to a second frequency within the bandwidth part.
The method of claim 12, wherein communicating the user data comprises:

communicating the user data using one or more narrow bands among a plurality of narrow bands included in the bandwidth part, each narrow band having a bandwidth equal to the maximum data bandwidth.
The method of claim 11, wherein communicating the user data comprises:

communicating the user data in a first bandwidth part that is different from a second bandwidth part associated with the control channel, wherein a bandwidth of the first bandwidth part is based on the maximum data bandwidth.
The method of claim 10, wherein communicating the user data comprises:

receiving an indication on whether the second communication capability is used for unicast communication or for both unicast and broadcast communication.
The method of claim 10, further comprising:

determining a first radio frequency (RF) bandwidth of a first slot according to a maximum bandwidth of the control channel if the first slot is configured for monitoring the control channel;

determining a second RF bandwidth of a second slot according to a maximum bandwidth of the data channel if the second slot is configured for monitoring the data channel without the control channel; and

communicating with the base station using the first slot for the control channel, followed by the second slot for the data channel.
The method of claim 17, further comprising:

performing RF retuning in a time gap between the first slot and the second slot if the first RF bandwidth is different from the second RF bandwidth.
The method of claim 10, further comprising:

receiving a configuration of channel-state information reference signals (CSI-RS) , wherein a bandwidth of the CSI-RS is independent of a bandwidth of the data channel.
The method of claim 10, wherein communicating the user data comprises:

switching a receive antenna among a plurality of antennas when receiving the user data.
A base station for wireless communication, comprising:

a communication interface configured to communicate with a user equipment (UE) ;

a memory; and

a processor operatively coupled with the communication interface and the memory,

wherein the processor and the memory are configured to:

configure a control channel for transmitting control information to the UE;

transmit the control information to the UE via the control channel according to a first communication capability of the UE; and

communicate user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability.
The base station of claim 21, wherein the processor and the memory are further configured to:

receive UE capability information comprising a maximum control bandwidth of the control channel and a maximum data bandwidth of the data channel,

wherein the maximum data bandwidth is based on a maximum transport block size (TBS) supported by the UE.
The base station of claim 22, wherein the processor and the memory are further configured to:

transmit a configuration of a bandwidth part (BWP) to the UE, wherein a bandwidth of the BWP is based on the maximum control bandwidth; and

communicate the user data within the bandwidth part.
The base station of claim 23, wherein to communicate the user data, the processor and the memory are further configured to:

change a frequency location associated with the data channel from a first frequency to a second frequency within the bandwidth part.
The base station of claim 23, wherein to communicating the user data, the processor and the memory are further configured to:

communicate the user data using one or more narrow bands among a plurality of narrow bands included in the bandwidth part, each narrow band having a bandwidth equal to the maximum data bandwidth.
The base station of claim 22, wherein to communicate the user data, the processor and the memory are further configured to:

communicate the user data in a first bandwidth part that is different from a second bandwidth part associated with the control channel, wherein a bandwidth of the first bandwidth part is based on the maximum data bandwidth.
The base station of claim 21, wherein to communicate the user data, the processor and the memory are further configured to:

indicate whether the second communication capability is used for unicast communication or for both unicast and broadcast communication.
The base station of claim 21, wherein the processor and the memory are further configured to:

determine a first radio frequency (RF) bandwidth of a first slot according to a maximum bandwidth of the control channel if the first slot is configured for monitoring the control channel;

determine a second RF bandwidth of a second slot according to a maximum bandwidth of the data channel if the second slot is configured for monitoring the data channel without the control channel; and

communicate with the UE using the first slot for the control channel, followed by the second slot for the data channel.
The base station of claim 21, wherein the processor and the memory are further configured to:

transmit a configuration of channel-state information reference signals (CSI-RS) , wherein a bandwidth of the CSI-RS is independent of a bandwidth of the data channel.
A user equipment (UE) for wireless communication, comprising:

a communication interface configured to communicate with a base station;

a memory; and

a processor operatively coupled with the communication interface and the memory,

wherein the processor and the memory are configured to:

transmit, to the base station, a UE capability report indicating a first communication capability and a second communication capability of the UE, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability;

receive, from the base station, control information via a control channel according to the first communication capability; and

communicate user data with the base station via a data channel corresponding to the control information according to the second communication capability.
The UE of claim 30, wherein the UE capability report comprises a maximum control bandwidth of the control channel and a maximum data bandwidth of the data channel, wherein the maximum data bandwidth is based on a maximum transport block size (TBS) supported by the UE.
The UE of claim 31, wherein the processor and the memory are further configured to:

receive a configuration of a bandwidth part (BWP) , wherein a bandwidth of the BWP is based on the maximum control bandwidth; and

communicate the user data within the bandwidth part.
The UE of claim 32, wherein to communicate the user data, the processor and the memory are further configured to:

change a frequency location associated with the data channel from a first frequency to a second frequency within the bandwidth part.
The UE of claim 32, wherein to communicate the user data, the processor and the memory are further configured to:

communicate the user data using one or more narrow bands among a plurality of narrow bands included in the bandwidth part, each narrow band having a bandwidth equal to the maximum data bandwidth.
The UE of claim 31, wherein to communicate the user data, the processor and the memory are further configured to:

communicate the user data in a first bandwidth part that is different from a second bandwidth part associated with the control channel, wherein a bandwidth of the first bandwidth part is based on the maximum data bandwidth.
The UE of claim 30, wherein to communicate the user data, the processor and the memory are further configured to:

receive an indication on whether the second communication capability is used for unicast communication or for both unicast and broadcast communication.
The UE of claim 30, wherein the processor and the memory are further configured to:

determine a first radio frequency (RF) bandwidth of a first slot according to a maximum bandwidth of the control channel if the first slot is configured for monitoring the control channel;

determine a second RF bandwidth of a second slot according to a maximum bandwidth of the data channel if the second slot is configured for monitoring the data channel without the control channel; and

communicate with the base station using the first slot for the control channel, followed by the second slot for the data channel.
The UE of claim 37, wherein the processor and the memory are further configured to:

perform RF retuning in a time gap between the first slot and the second slot if the first RF bandwidth is different from the second RF bandwidth.
The UE of claim 30, wherein the processor and the memory are further configured to:

receive a configuration of channel-state information reference signals (CSI-RS) , wherein a bandwidth of the CSI-RS is independent of a bandwidth of the data channel.
The UE of claim 30, wherein to communicate the user data, the processor and the memory are further configured to:

switch a receive antenna among a plurality of antennas when receiving the user data.
A base station for wireless communication, comprising:

means for configuring a control channel for transmitting control information to a user equipment (UE) ;

means for transmitting the control information to the UE via the control channel according to a first communication capability of the UE; and

means for communicating user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability.
A user equipment (UE) for wireless communication, comprising:

means for transmitting, to a base station, a UE capability report indicating a first communication capability and a second communication capability, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability;

means for receiving, from the base station, control information via a control channel according to the first communication capability; and

means for communicating user data with the base station via a data channel corresponding to the control information according to the second communication capability.
A computer-readable storage medium comprising executable code for causing a base station to:

configure a control channel for transmitting control information to a user equipment (UE) ;

transmit the control information to the UE via the control channel according to a first communication capability of the UE; and

communicate user data with the UE via a data channel corresponding to the control information according to a second communication capability of the UE, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability.
A computer-readable storage medium comprising executable code for causing a user equipment (UE) to:

transmit, to a base station, a UE capability report indicating a first communication capability and a second communication capability, the second communication capability providing at least one of a smaller channel bandwidth or fewer radio frequency (RF) chains than the first communication capability;

receive, from the base station, control information via a control channel according to the first communication capability; and

communicate user data with the base station via a data channel corresponding to the control information according to the second communication capability.