TW202232911A - Configuration and signaling support for half-duplex frequency division duplex operation of reduced-capability user equipments - Google Patents

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a reduced-capability user equipment (RedCap UE) may transmit, to a base station, capability information indicating reduced capabilities of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communication. The RedCap UE may receive, from the base station, HD-FDD configuration information for conducting the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information. The RedCap UE may communicate, by transmitting data or receiving data during the HD-FDD communication, based at least in part on the HD-FDD configuration information. Numerous other aspects are described.

Description

Configuration and signaling support for half-duplex frequency division duplex operation for reduced-capacity UEs

In general, aspects of the present disclosure relate to wireless communications and to configurations and information for providing half-duplex frequency division duplex (HD-FDD) operation for reduced capability user equipment (RedCap UEs). Supported technologies and equipment.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, communications, and broadcasting. Typical wireless communication systems may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources (eg, bandwidth, transmit power, etc.). Examples of such multiple access techniques include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems , Single Carrier Frequency Division Multiple Access (SC-FDMA) system, Time Division - Synchronous Code Division Multiple Access (TD-SCDMA) system and Long Term Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) operational standard promulgated by the 3rd Generation Partnership Project (3GPP).

A wireless network may include multiple base stations (BSs) capable of supporting communications for multiple user equipments (UEs). The UE may communicate with the BS via downlink and uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in greater detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Head, Transmit Receive Point (TRP), New Radio (NR) BS, 5G Node B, or the like.

The above multiple access techniques have been employed in various telecommunication standards to provide a common agreement that enables different user equipment to communicate on a city, national, regional, and even global level. NR (which may also be referred to as 5G) is a set of enhancements to the LTE mobile standard published by 3GPP. NR is designed by increasing spectral efficiency, reducing cost, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) , use CP-OFDM and/or SC-FDM (eg, also known as discrete Fourier transform spread spectrum OFDM (DFT-s-OFDM)) on the uplink (UL) for better integration with other open standards, This provides better support for mobile broadband Internet access, as well as support for beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR, and other radio access technologies remain useful.

In some aspects, a reduced capability user equipment for wireless communication (RedCap UE) includes memory and one or more processors operatively coupled to the memory, the memory and the one or more processes The device is configured to: transmit capability information to the base station indicating the reduced capability of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communication; receive from the base station for HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information is based at least in part on the capability information; and based at least in part on the HD-FDD configuration information, by Data is transmitted or received to communicate during this HD-FDD communication.

In some aspects, a method of wireless communication performed by a RedCap UE includes transmitting capability information to a base station, the capability information indicating a reduced capability of the RedCap UE associated with conducting HD-FDD communications; from the base station receiving HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information based at least in part on the capability information; and based at least in part on the HD-FDD configuration information , communicate by transmitting or receiving data during the HD-FDD communication.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a RedCap UE, cause The RedCap UE performs the following operations: transmits capability information to the base station indicating the reduced capabilities of the RedCap UE associated with conducting HD-FDD communications; receives from the base station for conducting the HD-FDD communication with the base station HD-FDD configuration information for FDD communications, the HD-FDD configuration information being based at least in part on the capability information; and based at least in part on the HD-FDD configuration information, by transmitting during the HD-FDD communication data or receive data to communicate.

In some aspects, an appliance for wireless communication includes: means for transmitting capability information to a base station, the capability information indicating a reduced capability of the appliance associated with conducting HD-FDD communications; means for a base station to receive HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and for being based at least in part on the capability information HD-FDD configuration information, a component that communicates by transmitting or receiving data during the HD-FDD communication.

In some aspects, a base station for wireless communication includes memory and one or more processors operatively coupled to the memory, the memory and the one or more processors configured to: from The RedCap UE receives capability information indicating the reduced capability of the RedCap UE associated with HD-FDD communication; transmits the HD-FDD configuration for the HD-FDD communication with the base station to the RedCap UE information, the HD-FDD configuration information is based at least in part on the capability information; and based at least in part on the HD-FDD configuration information, communicating by transmitting data or receiving data during the HD-FDD communication.

In some aspects, a method of wireless communication performed by a base station includes: receiving capability information from a RedCap UE, the capability information indicating a reduced capability of the RedCap UE associated with conducting HD-FDD communications; to the RedCap UE transmitting HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and based at least in part on the HD-FDD configuration information , communicate by transmitting or receiving data during the HD-FDD communication.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause The base station performs the following operations: receives capability information from the RedCap UE, the capability information indicating the reduced capability of the RedCap UE associated with conducting HD-FDD communication; transmits to the RedCap UE for conducting the HD-FDD communication with the base station HD-FDD configuration information for FDD communications, the HD-FDD configuration information being based at least in part on the capability information; and based at least in part on the HD-FDD configuration information, by transmitting during the HD-FDD communication data or receive data to communicate.

In some aspects, an apparatus for wireless communication includes: means for receiving capability information from a RedCap UE, the capability information indicating a reduced capability of the RedCap UE associated with conducting HD-FDD communications; means for the RedCap UE to transmit HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and for being based at least in part on the capability information HD-FDD configuration information, a component that communicates by transmitting or receiving data during the HD-FDD communication.

In general, aspects include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, Base stations, wireless communication devices and/or processing systems.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages are described below. The conception and specific example disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The nature of the concepts disclosed herein, both in their organization and method of operation, and associated advantages, will be better understood from the following description when considered in conjunction with the drawings. Each drawing in the drawings is provided for the purposes of illustration and description, and not as a definition of limitations on the scope of the claims.

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

Several aspects of telecommunications systems will now be presented with reference to various appliances and techniques. These apparatus and techniques will be described in the following detailed description and illustrated in the accompanying drawings by means of various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements") out. These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

It should be noted that while terms commonly associated with 5G or NR Radio Access Technology (RAT) may be used herein to describe aspects, aspects of the present disclosure may apply to other RATs, such as 3G RAT, 4G RAT and/or post-5G RAT (eg, 6G).

1 is a diagram illustrating an example of a wireless network 100 in accordance with various aspects of the present disclosure. Wireless network 100 may be or include elements of a 5G (NR) network and/or an LTE network, among other examples. Wireless network 100 may include a plurality of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit reception point (TRP), and the like. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of a BS and/or a BS subsystem serving that coverage area, depending on the context in which the term is used.

The BS may provide communication coverage for macro cells, pico cells, femto cells, and/or another type of cell. A macro cell may cover a relatively large geographic area (eg, several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femtocell may cover a relatively small geographic area (eg, a residence) and may allow restricted access by UEs associated with the femtocell (eg, UEs in a Closed Subscriber Group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto for femto cell 102c BS. The BS may support one or more (eg, three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB" and "cell" are used interchangeably herein.

In some aspects, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and/or with one or more of the wireless networks 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network BSs or network nodes (not shown) are interconnected.

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

The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, and the like. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100 . For example, macro BSs may have high transmit power levels (eg, 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (eg, 0.1 to 2 watts).

The network controller 130 may be coupled to a set of BSs and may provide coordination and control for the BSs. The network controller 130 may communicate with the BS via the backhaul. The BSs may also communicate with each other directly or indirectly via wireless or wired backhaul.

UEs 120 (eg, 120a, 120b, 120c) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, or the like. The UE may be a cellular phone (eg, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, Cameras, Gaming Devices, Small Notebooks, Smart Notebooks, Thin and Light Notebooks, Medical Devices or Equipment, Biometric Sensors/Devices, Wearable Devices (Smart Watches, Smart Clothing, Smart Glasses, Smart Wrists) Bands, smart jewelry (eg, smart rings, smart bracelets, etc.), entertainment devices (eg, music or video devices, or satellite radio units, etc.), vehicle components or sensors, smart meters/sensors , industrial manufacturing equipment, global positioning system devices, or any other suitable device configured to communicate via wireless or wired media.

Some UEs may be considered Machine Type Communication (MTC) or Evolved or Enhanced Machine Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags that can communicate with a base station, another device (eg, a remote device), or some other entity . A wireless node may provide a connection to or to a network (eg, a wide area network such as the Internet or a cellular network), eg, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, and/or may be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE 120 may be included within a housing that houses components of UE 120, such as processor components and/or memory components. In some aspects, the processor component and the memory component can be coupled together. For example, a processor component (eg, one or more processors) and a memory component (eg, memory) can be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

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

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

Devices of wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various classes, frequency bands, channels, etc. based on frequency or wavelength. For example, devices of wireless network 100 may communicate using an operating frequency band having a first frequency range (FR1), which may span from 410 MHz to 7.125 GHz, and/or may use a second frequency range (FR2), which It can communicate across the operating frequency band from 24.25 GHz to 52.6 GHz). The frequency between FR1 and FR2 is sometimes referred to as the mid-band frequency. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, FR2 is often referred to as the "millimeter wave" band, although it is distinct from the very high frequency (EHF) band (30 GHz–300 GHz) that is identified as a "millimeter wave" band by the International Telecommunication Union (ITU). Accordingly, unless expressly stated otherwise, it should be understood that the terms "sub-6 GHz" and the like (if used herein) can broadly refer to frequencies below 6 GHz, frequencies within FR1, and/or mid-band frequencies (eg, greater than 7.125 GHz). Similarly, unless expressly stated otherwise, it should be understood that the terms "millimeter wave" and the like (if used herein) may broadly refer to frequencies within the EHF band, frequencies within the FR2 and/or mid-band frequencies (eg, less than 24.25 GHz). It is envisioned that the frequencies included in FR1 and FR2 may be modified and the techniques described herein are applicable to those modified frequency ranges.

As noted above, Figure 1 is provided as an example. Other examples may differ from the example described with respect to FIG. 1 .

2 is a diagram illustrating an example 200 of base station 110 in wireless network 100 communicating with UE 120 in accordance with various aspects of the present disclosure. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general, T > 1 and R > 1.

At base station 110, transmit processor 220 may receive data for one or more UEs from data source 212, selecting one for each UE based at least in part on a channel quality indicator (CQI) received from the UE or multiple modulation and coding schemes (MCSs) that process (eg, encode and modulate) data for each UE based at least in part on the MCS selected for that UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (eg, for semi-static resource partitioning information (SRPI)) and control information (eg, CQI requests, grants, and/or upper layer signaling), and provide burden symbols and control symbols. The transmit processor 220 may also generate signals for reference signals (eg, cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (eg, primary synchronization signals (PSS) or secondary synchronization signals (SSS) )) reference symbols. A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (eg, precoding) on data symbols, control symbols, burden symbols, and/or reference symbols, if applicable, and may T output symbol streams are provided to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective stream of output symbols (eg, for OFDM) to obtain a stream of output samples. Each modulator 232 may further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

At UE 120, antennas 252a through 252r may receive downlink signals from base station 110 and/or other base stations, and may provide the received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (eg, filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (eg, for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. Receive processor 258 may process (eg, demodulate and decode) the detected symbols, provide decoded data for UE 120 to data slot 260 , and provide decoded control information to controller/processor 280 and system information. The term "controller/processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and/or channel quality indicator (CQI) parameters, among other examples. In some aspects, one or more components of UE 120 may be included in a housing.

The network controller 130 may include a communication unit 294 , a controller/processor 290 and a memory 292 . The network controller 130 may include, for example, one or more devices in the core network. The network controller 130 may communicate with the base station 110 via the communication unit 294 .

Antennas (eg, antennas 234a-234t and/or antennas 252a-252r) may include or may be included within one or more antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays, and other examples. Antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, sets of antenna elements, and/or arrays of antennas may include sets of coplanar antenna elements and/or sets of non-coplanar antenna elements. Antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays may include antenna elements within a single housing and/or antenna elements within multiple housings. Antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays may include one or more antenna elements coupled to one or more transmit and/or receive components, such as one or more of the components of FIG. 2 .

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information from controller/processor 280 (eg, to include RSRP, RSSI, RSRQ, and/or CQI) Report). Transmit processor 264 may also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be precoded by TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (eg, for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110 . In some aspects, the UE 120 modulator and demodulator (eg, MOD/DEMOD 254 ) may be included in the UE 120 modem. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252 , modulator and/or demodulator 254 , MIMO detector 256 , receive processor 258 , transmit processor 264 , and/or TX MIMO processor 266 . The transceiver may be used by a processor (eg, controller/processor 280 ) and memory 282 to perform aspects of any of the methods described herein (eg, as described with reference to FIGS. 3-7 ).

At base station 110, uplink signals from UE 120 and other UEs may be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 , to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide decoded data to data slot 239 and decoded control information to controller/processor 240 . Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244 . Base station 110 may include scheduler 246 to schedule UE 120 for downlink and/or uplink communications. In some aspects, the modulator and demodulator of base station 110 (eg, MOD/DEMOD 232 ) may be included in the modem of base station 110 . In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna 234 , modulator and/or demodulator 232 , MIMO detector 236 , receive processor 238 , transmit processor 220 and/or TX MIMO processor 230 . The transceiver may be used by a processor (eg, controller/processor 240 ) and memory 242 to perform aspects of any of the methods described herein (eg, as described with reference to FIGS. 3-7 ).

Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other components in FIG. 2 may perform configuration and signaling support related to providing HD-FDD operation for RedCap UEs one or more techniques, as described in greater detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of FIG. 2 may perform or direct, for example, process 400 of FIG. 4, process 500 of FIG. 5, and/or Operation of other processes as described herein. Memories 242 and 282 may store data and programming codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (eg, code and/or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and/or UE 120 (eg, directly, or after compilation, translation, and/or interpretation), may cause one or more The processor, UE 120, and/or base station 110 perform or direct operations such as process 400 of FIG. 4, process 500 of FIG. 5, and/or other processes as described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, and/or interpreting instructions, among other examples.

In some aspects, a reduced capability user equipment (RedCap UE) (eg, UE 120) includes means for transmitting capability information to the base station, the capability information indicating that the RedCap UE and the RedCap UE are half-duplexed ( Reduced capabilities associated with HD-FDD) communications; means for receiving, from a base station, HD-FDD configuration information for HD-FDD communications with the base station, the HD-FDD configuration information being based at least in part on capabilities information; and/or means for communicating by transmitting or receiving data during HD-FDD communications based at least in part on HD-FDD configuration information. The means for a RedCap UE to perform the operations described herein may include, for example, an antenna 252, a demodulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a modulator 254, a controller /One or more of processor 280 or memory 282.

In some aspects, the RedCap UE includes: means for receiving group common downlink control information (GC-DCI) via a downlink carrier common to a group of RedCap UEs including the RedCap UE, the GC-DCI indicates The respective uplink carrier index and downlink carrier index to be used by the RedCap UE.

In some aspects, the RedCap UE includes: means for receiving a GC-DCI via a downlink carrier common to a group of RedCap UEs (including the RedCap UE), the GC-DCI indicating GC-DCI from among the plurality of slot patterns, The respective slot modes to be used by the RedCap UE for HD-FDD communication and the effective duration associated with the utilization of the respective slot modes.

In some aspects, the base station (BS 110) includes means for receiving capability information from the RedCap UE, the capability information indicating the reduction of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communication capability; means for transmitting, to a RedCap UE, HD-FDD configuration information for HD-FDD communication with a base station, the HD-FDD configuration information being based at least in part on the capability information; or for use at least in part A component that communicates by transmitting or receiving data during HD-FDD communication based on HD-FDD configuration information. Means for a base station to perform the operations described herein may include, for example, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller /One or more of processor 240, memory 242, or scheduler 246.

Although the blocks in FIG. 2 are shown as distinct components, the functions described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and/or TX MIMO processor 266 may be performed by or under the control of controller/processor 280.

As noted above, Figure 2 is provided as an example. Other examples may differ from the example described with respect to FIG. 2 .

A base station may conduct data communication with a plurality of UEs in a network such as an LTE network and/or a 5G/NR network. Data communications may include downlink communications from the base station to the plurality of UEs and uplink communications from the plurality of UEs to the base station. The plurality of UEs may include regular UEs and/or RedCap UEs. RedCap UEs may include reduced capabilities relative to those included in conventional UEs. For example, RedCap UEs may include fewer transmit antennas and/or fewer receive antennas relative to conventional UEs. RedCap UEs may also have less stringent latency and throughput (eg, bit rate) requirements than conventional UEs. Furthermore, RedCap UEs can be designed for efficient power consumption. Examples of RedCap UEs may include video surveillance devices, industrial devices (such as pressure sensors, humidity sensors, etc.) and/or wearable devices (such as smart watches, smart wristbands, etc.). Examples of conventional UEs may include cellular phones (eg, smart phones), laptop computers, tablet devices, and the like.

A plurality of UEs may operate in full-duplex frequency division duplex (FD-FDD) mode for FD-FDD communication, which may involve transmitting and receiving data in parallel. For example, a UE among the plurality of UEs may transmit uplink communications via an uplink carrier and receive downlink communications via a downlink carrier in parallel.

During FD-FDD communication, the UE can observe the threshold insertion loss amount. In one example, the UE may observe a threshold amount of link cross-interference between uplink and downlink carriers used to communicate (eg, transmit and/or receive) data in parallel, resulting in a threshold insertion loss amount. To communicate data in the presence of a threshold amount of insertion loss, the UE may consume a threshold amount of power. It may be impractical for RedCap UEs to consume a threshold amount of power per transmission and per reception because RedCap UEs may be designed for efficient power consumption and may benefit from techniques to reduce power consumption. Therefore, RedCap UEs may not be able to operate adequately in FD-FDD mode.

Furthermore, the BS may not take into account the reduced capabilities of RedCap UEs when configuring parameters for operating in FD-FDD mode. For example, the BS may not take into account that the RedCap UE may consume a higher amount of BS resources compared to the regular UE. In one example, since the RedCap UE may include fewer receive antennas, the BS may have to repeat the transmission of the downlink communication to enable the RedCap UE to adequately receive the downlink communication. Without considering the reduced capabilities, the BS can configure the parameters to equally apply to regular UEs and RedCap UEs. In other words, the BS may handle data communications with RedCap UEs in a similar manner as the BS handles data communications with regular UEs. Therefore, when communicating with the RedCap UE, the BS may fail to repeat the transmission of the downlink communication so that the RedCap UE can adequately receive the downlink communication. Therefore, the data communication between the base station and the RedCap UE may experience interruption or stoppage.

Various aspects of the techniques and apparatus described herein may provide configuration and signaling support for HD-FDD operation for RedCap UEs. In some aspects, the BS may configure the operation of the RedCap UE in HD-FDD mode for HD-FDD communication with the BS. In HD-FDD mode, at a given time, the RedCap UE may transmit uplink communications via the uplink carrier, or may receive downlink communications via the downlink carrier. Therefore, the link cross-interference between the uplink carrier and the downlink carrier can be avoided, and the power consumption of the RedCap UE can be reduced. Additionally, RedCap UEs may avoid including duplexers utilized when operating in FD-FDD mode, thereby reducing costs associated with designing RedCap UEs. Furthermore, the BS may configure parameters associated with HD-FDD operation based at least in part on the reduced capabilities of the RedCap UEs, thereby enabling the BS to handle data communications with RedCap UEs differently than the BS may handle data communications with regular UEs data communication. Therefore, when communicating with the RedCap UE, the BS can sufficiently repeat the transmission of the downlink communication so that the RedCap UE can sufficiently receive the downlink communication, and the data communication between the BS and the RedCap UE can continue without interruption. Such configuration and signaling support may enable the BS to adequately communicate with RedCap UEs in HD-FDD communication as well as with regular UEs in FD-FDD communication.

In some aspects, the RedCap UE may transmit capability information to the base station, the capability information indicating the reduced capability of the RedCap UE associated with conducting HD-FDD communications, the indication of the reduced capability being used to indicate switches and filters to replace duplexers; receiving HD-FDD configuration information from the base station for HD-FDD communication with the base station; and based at least in part on the configuration information, by transmitting during the HD-FDD communication data or receive data to communicate. In some aspects, configuration information may be mapped to system information (SI), radio resource control (RRC) messages, medium access control control elements (MAC CE), or dynamic grant (DG) communications.

3 is a diagram illustrating an example 300 associated with providing configuration and signaling support for HD-FDD operation for RedCap UEs in accordance with various aspects of the present disclosure. FIG. 3 shows UE 120 and BS 110 communicating data in an LTE network or a 5G/NR network. In some aspects, UE 120 may be a RedCap UE and may have reduced capabilities compared to conventional UEs. Data communications may include downlink communications from BS 110 to UE 120 and may include uplink communications from UE 120 to BS 110 .

As indicated by numeral 310, the BS 110 may transmit configuration information before, at the beginning, and/or during the initiation of the data communication, and the UE 120 may receive the configuration information. In some aspects, the configuration information may include an indication of one or more configuration parameters, eg, used by the UE 120 to configure the UE 120 for data communication. In some aspects, UE 120 may receive configuration information via BS 110 for system information broadcast by the UE. In some aspects, UE 120 may receive configuration information from a device other than BS 110 (eg, from another base station). In some aspects, UE 120 may receive configuration information via, eg, a control channel (eg, a physical downlink control channel (PDCCH)) between UE 120 and BS 110 . This may be via RRC signaling, MAC signaling (eg, MAC CE), downlink control information (DCI) signaling, or a combination thereof (eg, RRC configuration for a set of values for a parameter and communication for selected values of a parameter). DCI indication) to transmit configuration information.

As shown by reference numeral 320, UE 120 may transmit and BS 110 may receive capability information indicating the reduced capabilities of UE 120. In some aspects, the capability information may indicate that the design of the UE 120 does not include duplexers and/or that the duplexers have been replaced by switches and filters; that the UE 120 includes, for example, fewer receive antennas than conventional UEs; UE 120 is subject to less stringent latency and throughput (eg, bit rate) requirements than conventional UEs; and/or UE 120 is designed for efficient power consumption.

BS 110 may transmit and UE 120 may receive HD associated with configuring UE 120 to operate in HD-FDD mode for half-duplex communication with BS 110, as shown at 330 based at least in part on the reception capability information. - FDD configuration information. In HD-FDD mode, the UE 120 may be configured to transmit uplink communications via the uplink carrier or receive downlink communications via the downlink carrier (also referred to as HD-FDD communications) at a given time . Based at least in part on the HD-FDD configuration information, UE 120 may configure UE 120 to operate in an HD-FDD mode for HD-FDD communications, as indicated by reference numeral 340 . As indicated by numeral 350, UE 120 may communicate data (eg, by transmitting data or receiving data) based at least in part on the HD-FDD configuration information.

In some aspects, HD-FDD configuration information may include and/or indicate information associated with operating in HD-FDD mode. For example, the HD-FDD configuration information may indicate HD-FDD parameters to be used by UE 120 for HD-FDD communication. In some aspects, the HD-FDD configuration information may indicate index information associated with one or more carriers to be used by UE 120 for HD-FDD communications. The index information may include, for example, a downlink carrier index associated with a downlink carrier configured to carry downlink communications from the BS 110 to the UE 120 . In some aspects, the index information may indicate that the downlink carrier is to be used by UE 120 to receive downlink communications from BS 110 . The index information may also include, for example, an uplink carrier index associated with an uplink carrier configured to carry uplink communications from UE 120 to BS 110 . In some aspects, the index information may indicate that the uplink carrier is to be used by UE 120 to transmit uplink communications to BS 110 . In some aspects, the uplink and/or downlink carriers may be semi-statically configured such that the uplink and/or downlink carriers are within a certain number of time slots or within a certain number of signals The frame is still available for UE 120 to utilize. In other words, the availability of semi-statically configured carriers may not change between time slots or between frames.

In some aspects, the index information may be included in a common information element (eg, HD-FDD-UL- DL-ConfigurationCommon). In some aspects, the index information may be included in a dedicated information element (eg, HD-FDD-UL-DL-ConfigDedicated) received via dedicated RRC messages, MAC CE communications, or DG communications. In some aspects, UE 120 may receive the dedicated information element at a different time (eg, individually) relative to the time at which UE 120 may receive the common information element. In some aspects, UE 120 may receive the dedicated information element at substantially the same time (eg, jointly) as the common information element. When the index information is received via a dedicated RRC message, the index information may be exclusively applied to the UE 120 . Based at least in part on receiving the index information, UE 120 may transmit uplink communications to BS 110 using the uplink carrier associated with the indicated uplink carrier index during HD-FDD communications. Similarly, UE 120 may receive downlink communications from BS 110 during HD-FDD communications utilizing the downlink carrier associated with the indicated downlink carrier index based at least in part on receiving the index information.

In some aspects, the HD-FDD configuration information may include slot mode information associated with HD-FDD communications. The slot pattern information may indicate, for example, one or more types of slot patterns that indicate one or more time and frequency resource mappings for a particular set of contiguous slots or a set of particular contiguous symbols configured for one or more carriers . For example, the slot pattern information may include a first slot pattern that includes one or more types of slot patterns that indicate a first set of consecutive slots or a first set of slots for configuration on the downlink carrier. One or more joint time and frequency resource mappings for a contiguous set of symbols. Similarly, the slot pattern information may include a second slot pattern including one or more types of slot patterns indicating a second set of consecutive slots for configuration on the uplink carrier or One or more joint time and frequency resource mappings for the second set of consecutive symbols. The slot pattern information may also include a third slot pattern indicating one or more types of slot patterns for use on the uplink carrier, downlink carrier and/or as a protection configuration One or more joint time and frequency resource mappings for the third set of consecutive time slots or the third set of consecutive symbols.

In some aspects, the specific set of consecutive slots and/or the specific set of consecutive symbols may be flexible resources configured for utilization by UE 120 during HD-FDD communications. In some aspects, the common information element and/or the dedicated information element may include a pattern information element (eg, HD-FDD-UL-DL-Pattern) for indicating slot pattern information and/or flexible resources. When included within the common information element, the configuration of flexible resources may be associated with cell-specific (eg, BS 110-specific) HD-FDD communications. When included within the dedicated information element, the configuration of flexible resources may be UE-specific (eg, UE 120-specific) HD-FDD communications.

In some aspects, the slot pattern information may include periodicity information indicating a first periodicity associated with the first slot pattern, a second periodicity associated with the second slot pattern, or a third periodicity associated with the second slot pattern The third periodicity associated with the slot pattern. When the UE 120 is capable of transmitting uplink communications to the BS 110 using flexible uplink resources, a period among the first periodicity, the second periodicity, and/or the third periodicity may indicate a transmission period and be related to the occurrence of the transmission period linked mode. Furthermore, when the UE 120 is capable of receiving downlink communications from the BS 110 using flexible downlink resources, the periodicity may indicate a reception period and a pattern associated with the occurrence of the reception period. Based at least in part on the periodic information, UE 120 may utilize flexible resources for HD-FDD communications according to the periodic information.

In some aspects, the slot pattern information may include reference numbering scheme information, which may indicate a utilized subcarrier spacing type among a plurality of available subcarrier spacing types. For example, the reference numbering scheme information may indicate a first reference numbering scheme (eg, a first subcarrier spacing type) used in association with a first slot pattern, a second reference numbering scheme used in association with a second slot pattern scheme (eg, second subcarrier spacing type), and/or a third reference numbering scheme (eg, third subcarrier spacing type) used in association with the third slot pattern. Based at least in part on the reference numbering scheme information, UE 120 may utilize the reference numbering scheme for HD-FDD communications according to the reference numbering scheme information.

In some aspects, the slot mode information may include ordering information indicating the ordering of the first slot mode, the second slot mode, and/or the third slot mode in the time domain. The ordering information may indicate the order in which one or more of the first slot pattern, the second slot pattern, or the third slot pattern are ordered in the time domain for use by the UE 120 . The ordering information may indicate the arrangement of the first slot pattern, the second slot pattern and/or the third slot pattern in the time domain. For example, the slot patterns may be ordered chronologically (such as 1, 3, 2, 1, 3, 2; 3, 1, 2, 1, 3, 2, among other examples) (eg, where 1 represents the first slot mode, 2 for the second slot mode, and 3 for the third slot mode). Based at least in part on the ordering information, the UE 120 may utilize one or more of these slot patterns for HD-FDD communications according to the ordering information.

In some aspects, the slot pattern information may include monitoring information associated with UE 120 monitoring PDCCH occasions associated with one or more of the slot patterns. For example, the monitoring information may indicate a first PDCCH monitoring occasion associated with a first slot pattern, a second PDCCH monitoring occasion associated with a second slot pattern, and/or a third PDCCH associated with a third slot pattern Monitor timing. Based at least in part on the monitoring information, the UE 120 may monitor PDCCH occasions associated with one or more of the slot patterns during HD-FDD communications according to the monitoring information.

In some aspects, the slot mode information may indicate bandwidth portion (BWP) configuration information associated with a bandwidth portion configured for utilization in association with one or more of the slot modes. For example, the BWP configuration information may indicate a first BWP configuration configured for uplink BWP and downlink BWP utilized in association with a first slot mode, configured for use with a second slot mode A second BWP configuration for the uplink BWP and downlink BWP utilized in association with the mode, and/or configured for the uplink BWP and downlink BWP utilized in association with the third slot mode The third BWP configuration. Based at least in part on the BWP configuration information, the UE 120 may utilize the configured uplink BWP and/or downlink BWP for HD-FDD communication according to the BWP configuration information.

In some aspects, the slot mode information may be included in a common information element received via SI communications or MAC CE communications that are broadcast or multicast to the group of UEs including UE 120 . In some aspects, slot mode information may be included in dedicated information elements received via dedicated RRC messages, MAC CE or DG communications. In some aspects, a dedicated information element may be received alone or in conjunction with a common information element that includes slot mode information.

In some aspects, a group of RedCap UEs including UE 120 may share a particular downlink carrier. In this case, the RedCap UE group can dynamically receive the GC-DCI via a specific downlink carrier. The GC-DCI may indicate the respective slot modes associated with the slot mode information to be used by the RedCap UEs included in the group for HD-FDD communication, respectively. In some aspects, the GC-DCI may also indicate the respective valid durations associated with the utilization of the respective slot patterns by the RedCap UEs included in the group. Furthermore, the GC-DCI may indicate the respective uplink carrier index and/or the respective downlink carrier index to be used by the RedCap UEs included in the group for HD-FDD communication, respectively. In some aspects, the dynamically indicated respective uplink carrier index and/or respective downlink carrier index may temporarily or semi-permanently override the flexibility of the uplink carrier and/or downlink carrier configuration.

In some aspects, the HD-FDD configuration information may indicate that the UE 120 is associated with switching from using the downlink carrier to using the uplink carrier or switching from using the uplink carrier to using the downlink carrier. protection period. The guard period may be associated with a time window in which the delay spread component of the previous symbol arrives before the start of the next symbol. In some aspects, the HD-FDD communication may be a Type A HD-FDD communication, and the duration of the guard period may be a symbol-level guard period. In other words, the duration of the guard period may be associated with the duration of one or more symbols.

In some aspects, the duration of the guard period may be longer than the maximum delay associated with HD-FDD communications. In some aspects, the minimum duration of the guard period (eg, a duration of two symbols) may be associated with the subcarrier spacing associated with the uplink carrier and/or downlink carrier used for HD-FDD communications Associated. In some aspects, the minimum duration of the guard period (eg, the duration of two symbols) may be the same as the active uplink BWP and/or active downlink that are actively used by UE 120 for HD-FDD communications The subcarrier spacing associated with the BWP is associated. The subcarrier spacing may be specified in a specification, and the UE 120 may decide the subcarrier spacing based at least in part on such specification. In some aspects, the guard period may be associated with flexible resources (eg, time slots and/or symbols) associated with the time slot pattern (which is associated with the time slot pattern information) configured for HD-FDD communication associated with the use of .

In some aspects, UE 120 may not receive HD-FDD configuration information including the uplink carrier index and/or the downlink carrier index. Furthermore, UE 120 may not be configured to monitor dynamic slot format indication (SFI), which may be signaled via GC-DCI. In this case, UE 120 may rely on UE-specific DCI for link direction decisions.

In some aspects, UE 120 is capable of operating in FD-FDD mode for FD-FDD communication with BS 110 . In this case, UE 120 may be configured to switch to operate in HD-FDD mode for HD-FDD communication with BS 110. In some aspects, UE 120 may switch from operating in FD-FDD mode to operating in HD-FDD mode when UE 120 must communicate with BS 110 less than a threshold amount of data.

In some aspects, BS 110 may support UEs operating in HD-FDD mode and UEs operating in FD-FDD mode. In this case, BS 110 may configure HD-FDD power control parameters for UEs operating in HD-FDD mode and FD-FDD power control parameters for UEs operating in FD-FDD mode. In some aspects, UE 120 may utilize HD-FDD power control parameters to transmit uplink communications to BS 110 during HD-FDD communications. Uplink communications may include communications transmitted via a physical random access channel (PRACH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), and/or a sounding reference signal (SRS).

The HD-FDD power control parameters may be based, at least in part, on uplink transmission characteristics inherent to UE 120 when conducting HD-FDD communications. Such transmission characteristics may include reduced insertion loss, improved power efficiency, reduced peak transmission power, and/or increased reference sensitivity. In some aspects, the transmission characteristics may be indicated by a degraded measure (eg, noise coefficient) imparted by the receive and/or transmit circuitry of the UE 120 to the signal-to-noise ratio. In some aspects, based at least in part on the reduced degradation of SNR imparted by receive and/or transmit circuitry included in UE 120 compared to a UE in FD-FDD communication (RedCap UE or regular UE), the UE 120 may have improved transmission characteristics in HD-FDD communication. In some aspects, the receive circuitry and/or transmit circuitry included in UE 120 may introduce a reduced amount of noise to the SNR based at least in part on avoiding link cross-interference as compared to a UE in FD-FDD communication.

In some aspects, BS 110 may transmit HD-FDD power control parameters, and UE 120 may receive HD-FDD power control parameters, the HD-FDD power control parameters including an offset for receiving the target power, The offset of the maximum output power of the state and/or the scaling factor or offset of the reference signal power used in the path loss estimation. HD-FDD power control parameters may also include enhanced granularity, range and/or power control adjustment status associated with transmit power control commands and transmit power rises. UE 120 may decide the transmit power for transmitting uplink communications to BS 110 based, at least in part, on a formula specified in the specification, the formula involving HD-FDD power control parameters. In some aspects, HD-FDD power control parameters may assist in controlling the transmit power utilized by UE 120, thereby reducing power consumption associated with transmitting uplink communications.

In some aspects, the HD-FDD configuration information may include performing radio resource management (RRM) procedures, radio link monitoring (RLM) procedures, and/or cellular positioning and beam management with the UE 120 in HD-FDD communications Process (BM process) associated measurement and reporting parameters. The RRM procedure may be associated with UE 120 performing RRM measurements associated with cell selection procedures, cell reselection procedures, and/or handover procedures. The RLM procedure may be associated with UE 120 monitoring a downlink carrier (eg, PDCCH) to assist in determining a metric of quality associated with downlink communications received via the downlink carrier. BM procedures may be associated with UE 120 deciding a transmit beam for transmitting uplink communications and/or a receive beam for receiving downlink communications based at least in part on the location of UE 120 within a cell associated with BS 110 , the transmit beam enables BS 110 to adequately receive uplink communications and/or the receive beam enables UE 120 to adequately receive downlink communications.

In some aspects, the measurement and reporting parameters may be based, at least in part, on a reduced capability of UE 120 to operate in HD-FDD mode. For example, UE 120 may have an increased reference sensitivity level based at least in part on avoiding link cross-interference. Based at least in part on the increased reference sensitivity level, the measurement and reporting parameters may include a particular level of accuracy associated with UE 120 performing RRM procedures, RLM procedures, and/or BM procedures. Furthermore, based at least in part on a particular level of accuracy, the measurement and reporting parameters may include an extended periodicity associated with the frequency with which the UE 120 will perform RRM procedures, RLM procedures, and/or BM procedures. In some aspects, the measurement and reporting parameters may be configured based at least in part on the slot mode (eg, as described above). In some aspects, the measurement and reporting parameters may be configured based at least in part on the BWP. In some aspects, the measurement and reporting parameters may indicate a list of measurement objects, reporting configurations, measurement identifications, quantity configurations, or measurement gap configurations associated with UE 120 performing RRM procedures, RLM procedures, and/or BM procedures. The measurement object may indicate the parameters to be measured and reported by the UE 120, the reporting configuration may indicate the configuration associated with the measurement and reporting parameters, the quantity configuration may indicate the quantity of the parameter to be measured and reported, and the measurement gap configuration may Indicates the duration and/or periodicity associated with the measurement and reporting parameters.

In some aspects, UE 120 and/or BS 110 may handle the UE's handover to continue HD-FDD communications with neighboring BSs, eg, associated with neighboring cells. In this case, the BS 110 may indicate whether the neighboring BS supports UEs operating in HD-FDD mode. When BS 110 indicates that neighbor BSs do not support UEs operating in HD-FDD mode, UE 120 may avoid performing RRM procedures, RLM procedures, and/or BM procedures unnecessarily in conjunction with neighboring BSs.

By utilizing the parameters discussed herein for half-duplex operation of RedCap UEs, link cross-interference between uplink and downlink carriers can be avoided, and power consumption of RedCap UEs can be reduced. Additionally, RedCap UEs may avoid including duplexers utilized when operating in FD-FDD mode, thereby reducing costs associated with designing RedCap UEs. Furthermore, when communicating with the RedCap UEs, the BS can repeat the transmission of downlink communications sufficiently to enable the RedCap UEs to adequately receive the downlink communications, and data communications between the BS and the RedCap UEs can continue uninterrupted.

As noted above, Figure 3 is provided as an example. Other examples may differ from the example described with respect to FIG. 3 .

FIG. 4 is a diagram illustrating an example process 400 performed, for example, by reduced-capable user equipment, in accordance with various aspects of the present disclosure. Example process 400 is an example in which a reduced-capable user equipment (eg, reduced-capable user equipment 120) performs operations associated with providing configuration and signaling support for HD-FDD operation for RedCap UEs.

As shown in FIG. 4, in some aspects, process 400 may include transmitting capability information to a base station, the capability information indicating a reduced redcap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communications. Ability (Block 410). For example, a RedCap UE (eg, using transmit component 604 depicted in FIG. 6 ) can transmit capability information to a base station that indicates which RedCap UE is associated with conducting half-duplex frequency division duplex (HD-FDD) communications Streamlined capabilities, as described above.

As further shown in FIG. 4, in some aspects, process 400 can include receiving, from a base station, HD-FDD configuration information for HD-FDD communication with the base station, the HD-FDD configuration information being at least in part Based on capability information (block 420). For example, a RedCap UE (eg, using receive component 602 depicted in FIG. 6 ) can receive HD-FDD configuration information, at least in part, from a base station for HD-FDD communication with the base station based on capability information, as described above.

As further shown in FIG. 4, in some aspects, process 400 may include communicating by transmitting or receiving data during HD-FDD communication based at least in part on the HD-FDD configuration information (block 430). For example, a RedCap UE (eg, using transmit component 604 and/or receive component 602 depicted in FIG. 6 ) can transmit data or receive data during HD-FDD communications based at least in part on HD-FDD configuration information. Communicate as described above.

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

In a first aspect, the HD-FDD configuration information includes index information associated with one or more carriers to be used for HD-FDD communication, the index information indicating: the index of the downlink carrier associated with the downlink carrier configured to carry the downlink transmission from the base station to the RedCap UE during HD-FDD communications; and with the uplink from one or more of the carriers Index of the uplink carrier associated with the link carrier that is configured to carry uplink transmissions from the RedCap UE to the base station during HD-FDD communications.

In the second aspect (alone or in combination with the first aspect), one or more carriers are semi-statically configured for HD-FDD communication.

In a third aspect (either alone or in combination with one or more of the first aspect and the second aspect), the index information is included in the group of UEs including RedCap UEs via broadcast or multicast In the common information element received in the SI communication or MAC CE communication.

In a fourth aspect (either alone or in combination with one or more of the first to third aspects), the indexing information is included in a dedicated RRC message, MAC CE or DG communication received via dedicated RRC messages. Of the information elements, exclusive information elements are received individually or in conjunction with common information elements including index information.

In a fifth aspect (either alone or in combination with one or more of the first to fourth aspects), the HD-FDD configuration information includes time slot mode information that includes One or more of the following: a first slot pattern including one or more times indicating a first set of consecutive slots or symbols for configuration on the downlink carrier and one or more types of time slot patterns for frequency resource mapping; a second time slot pattern including one indicating a second consecutive time slot or set of symbols for configuration on the uplink carrier one or more types of time slot patterns for mapping of or more time and frequency resources; or a third time slot pattern including indications for configuring on the uplink carrier, on the downlink carrier configuration, or one or more types of slot patterns of one or more time and frequency resource mappings for a third contiguous set of slots or symbols that are at least one of the guard period configurations.

In a sixth aspect (alone or in combination with one or more of the first to fifth aspects), the slot pattern information includes one or more of the following: Periodic information , the periodicity information indicates the first periodicity associated with the first slot pattern, the second periodicity associated with the second slot pattern, or the third periodicity associated with the third slot pattern; refer to numbering scheme information indicating a first reference numbering scheme associated with a first slot pattern, a second reference numbering scheme associated with a second slot pattern, or a a third reference numeral scheme; ordering information indicating the arrangement of the first slot pattern, the second slot pattern or the third slot pattern in the time domain; monitoring information indicating the relationship between the first slot pattern and the first slot pattern the associated first PDCCH monitoring occasion, the second PDCCH monitoring occasion associated with the second slot pattern, or the third PDCCH monitoring occasion associated with the third slot pattern; or BWP configuration information, the BWP configuration Information indicating a first BWP configuration of uplink BWPs and downlink BWPs associated with the first slot mode, a second BWP set of uplink BWPs and downlink BWPs associated with the second slot mode state, or a third BWP configuration of the uplink BWP and downlink BWP associated with the third slot mode.

In a seventh aspect (either alone or in combination with one or more of the first to sixth aspects), the slot mode information is included in the information via broadcast or multicast to UEs including RedCap In the common information element received in the SI communication or MAC CE communication of the UE group.

In an eighth aspect (either alone or in combination with one or more of the first to seventh aspects), slot mode information is included in the reception via dedicated RRC messages, MAC CE or DG communications Of the exclusive information elements of , the exclusive information elements are received alone or in conjunction with a common information element that includes slot mode information.

In a ninth aspect (either alone or in combination with one or more of the first to eighth aspects), process 400 includes via a downlink common to a group of RedCap UEs including RedCap UEs The carrier receives a GC-DCI indicating the respective uplink carrier index and downlink carrier index to be utilized by these RedCap UEs.

In a tenth aspect (either alone or in combination with one or more of the first to ninth aspects), process 400 includes via a downlink common to a group of RedCap UEs including RedCap UEs The carrier receives a GC-DCI indicating a respective slot mode from the plurality of slot modes to be used by the RedCap UE for HD-FDD communication and a valid duration associated with the utilization of the respective slot mode time.

In the eleventh aspect (either alone or in combination with one or more of the first to tenth aspects), the HD-FDD configuration information indicates and switches from utilizing the downlink carrier to utilizing The guard period associated with the uplink carrier, or the guard period associated with switching from utilizing the uplink carrier to utilizing the downlink carrier.

In the twelfth aspect (either alone or in combination with one or more of the first to eleventh aspects), the HD-FDD configuration information indicates a A guard period associated with utilizing the uplink carrier, or a guard period associated with switching from utilizing the uplink carrier to utilizing the downlink carrier, the duration of the guard period relative to being actively used for HD-FDD communications The subcarrier spacing associated with the active uplink BWP or active downlink BWP.

In the thirteenth aspect (either alone or in combination with one or more of the first to twelfth aspects), the HD-FDD configuration information indicates a A guard period associated with utilizing the uplink carrier, or a guard period associated with switching from utilizing the uplink carrier to utilizing the downlink carrier, associated with utilizing the time slot pattern configured for HD-FDD communication associated flexible time slots or flexible symbols.

In the fourteenth aspect (either alone or in combination with one or more of the first to thirteenth aspects), the HD-FDD configuration information includes the information to be used by the RedCap UE in the HD-FDD Power control parameters for uplink communications are conveyed during FDD communications.

In the fifteenth aspect (either alone or in combination with one or more of the first to fourteenth aspects), the HD-FDD configuration information includes the information to be communicated by the RedCap UE in HD-FDD Power control parameters during transmission of PRACH, PUCCH, PUSCH and/or SRS based at least in part on reduced insertion loss, improved power efficiency associated with RedCap UEs when conducting HD-FDD communications , improved UE receive sensitivity or reduced peak transmit power.

In the sixteenth aspect (either alone or in combination with one or more of the first to fifteenth aspects), the HD-FDD configuration information includes information to be communicated by the RedCap UE in HD-FDD power control parameters utilized during the period including offset for received target power, offset for UE-configured maximum output power, scaling factor or offset for reference signal power in path loss estimation Shifts, or enhanced granularity, range, and power control adjustment states associated with transmit power control commands and transmit power rises.

In the seventeenth aspect (either alone or in combination with one or more of the first to sixteenth aspects), the HD-FDD configuration information Measurement and reporting parameters associated with RRM procedures, RLM procedures, or BM procedures performed during the communication, based at least in part on the slot mode configuration, bandwidth, and bandwidth associated with the RedCap UE during HD-FDD communication Partial (BWP) configuration, reduced insertion loss, improved power efficiency or improved UE receive sensitivity.

In the eighteenth aspect (either alone or in combination with one or more of the first to seventeenth aspects), the HD-FDD configuration information Measurement and reporting parameters associated with the RRM process, RLM process or BM process performed during the communication, these measurement and reporting parameters indicating the measurement object, reporting configuration, measurement identification, quantity associated with performing the RRM process, RLM process or BM process A list of configurations or measurement gap configurations.

In the nineteenth aspect (either alone or in combination with one or more of the first to eighteenth aspects), the HD-FDD configuration information includes a cell selection process to be combined with the RedCap UE , measurement and reporting parameters associated with the RRM measurement performed by the cell reselection process or the handover process.

In the twentieth aspect (alone or in combination with one or more of the first to nineteenth aspects), the HD-FDD configuration information is via SI, RRC message, MAC CE or DG communication received.

In the twenty-first aspect (either alone or in combination with one or more of the first to twentieth aspects), the capability information indicates that the duplexing of the RedCap UE is replaced by switches and filters device.

Although FIG. 4 shows example blocks of process 400, in some aspects process 400 may include additional blocks, fewer blocks, different blocks, or in a different manner than those depicted in FIG. 4 Arranged blocks. Additionally or alternatively, two or more of the blocks of process 400 may be performed in parallel.

5 is a diagram illustrating an example process 500, eg, performed by a base station, in accordance with various aspects of the present disclosure. Example process 500 is an example in which a base station (eg, BS 110) performs operations associated with providing configuration and signaling support for HD-FDD operation of RedCap UEs.

As shown in FIG. 5 , in some aspects, process 500 may include receiving capability information from a RedCap UE, the capability information indicating a reduced size of the RedCap UE associated with conducting Half-Duplex Frequency Division Duplex (HD-FDD) communications Ability (Block 510). For example, a base station (eg, using receive component 702 depicted in FIG. 7 ) can receive capability information from a reduced capability user equipment (RedCap UE) that indicates that the RedCap UE and the RedCap UE perform half-duplex frequency division duplex (HD) - Reduced capabilities associated with FDD) communications, as described above.

As further shown in FIG. 5, in some aspects, process 500 can include transmitting, at least in part, HD-FDD configuration information to the RedCap UE for HD-FDD communication with the base station Based on capability information (block 520). For example, the base station (eg, using transmit component 704 depicted in FIG. 7 ) can transmit HD-FDD configuration information, at least in part, to the RedCap UE for HD-FDD communication with the base station based on capability information, as described above.

As further shown in FIG. 5, in some aspects, process 500 may include communicating by transmitting or receiving data during HD-FDD communication based at least in part on the HD-FDD configuration information (block 530). For example, a base station (eg, using transmit component 704 and/or receive component 702 depicted in FIG. 7 ) can transmit data or receive data during HD-FDD communications based at least in part on HD-FDD configuration information. Communicate as described above.

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

Although FIG. 5 shows example blocks of process 500, in some aspects process 500 may include additional blocks, fewer blocks, different blocks, or in a different manner than those depicted in FIG. 5 Arranged blocks. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

6 is a block diagram of an example appliance 600 for wireless communication. Appliance 600 may be a RedCap UE (eg, UE 120 ), or a RedCap UE may include appliance 600 . In some aspects, appliance 600 includes a receive component 602 and a transmit component 604, which can communicate with each other (eg, via one or more bus bars and/or one or more other components). As shown, the appliance 600 can communicate with another appliance 606 (eg, a UE, a base station, or another wireless communication device) using a receive component 602 and a transmit component 604 . As further shown, appliance 600 may include decision component 608, as well as one or more of other examples.

In some aspects, appliance 600 may be configured to perform one or more of the operations described herein in connection with FIG. 3 . Additionally or alternatively, appliance 600 may be configured to perform one or more of the processes described herein, such as process 400 of FIG. 4 . In some aspects, the appliance 600 and/or one or more components shown in FIG. 6 may include one or more components of the RedCap UE described above in connection with FIG. 2 . Additionally or alternatively, one or more of the components shown in FIG. 6 may be implemented within one or more of the components described above in connection with FIG. 2 . Additionally or alternatively, one or more components of the set of components may be implemented, at least in part, as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

The receiving component 602 can receive communications from the appliance 606, such as reference signals, control information, data communications, or combinations thereof. Receiving component 602 may provide received communications to one or more other components of appliance 600 . In some aspects, receiving component 602 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, among other examples, on received communications) ), and the processed signal may be provided to one or more other components of appliance 606 . In some aspects, receiving component 602 can include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or combinations thereof of the RedCap UE described above in connection with FIG. 2 .

The transmit component 604 can transmit communications to the appliance 606, such as reference signals, control information, data communications, or a combination thereof. In some aspects, one or more other components of appliance 606 can generate communications and can provide the generated communications to transmitting component 604 for transmission to appliance 606 . In some aspects, transmit component 606 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog, multiplexing, interleaving, mapping or encoding, among other examples) on the generated communications, and can convert the processed The signal is transmitted to appliance 606 . In some aspects, transmit component 604 can include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or the like of the RedCap UE described above in connection with FIG. 2 . combination. In some aspects, transmit component 604 can be co-located with receive component 602 in a transceiver.

Transmit component 604 can transmit capability information to the base station, the capability information indicating a reduced capability of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communications. The receiving component 602 can receive, from the base station, HD-FDD configuration information for HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information. Receive component 602 and/or transmit component 604 can communicate by transmitting data or receiving data during HD-FDD communications based at least in part on HD-FDD configuration information.

Receiving component 602 can receive a GC-DCI via a downlink carrier common to a group of RedCap UEs (including RedCap UEs), the GC-DCI indicating a respective uplink carrier index and downlink to be utilized by the RedCap UEs carrier index.

Receiving component 602 can receive, via a downlink carrier common to a group of RedCap UEs (including RedCap UEs), a GC-DCI indicating that from a plurality of slot patterns to be used by RedCap UEs for HD-FDD communications and the effective duration associated with utilizing the respective slot mode.

The determining component 608 can determine, for example, information to be included in capability information communicated to the base station. Additionally, the determining component 608 can determine the information received in the HD-FDD configuration information. Additionally, decision component 608 can decide data to communicate in HD-FDD communications.

The number and arrangement of components shown in Figure 6 are provided as examples. Indeed, there may be additional, fewer, different, or differently arranged components than those shown in FIG. 6 . Furthermore, two or more components shown in FIG. 6 may be implemented within a single component, or a single component shown in FIG. 6 may be implemented as multiple distributed components. Additionally or alternatively, one set(s) of components shown in FIG. 6 may perform one or more functions described as being performed by another set of components shown in FIG. 6 .

7 is a block diagram of an example appliance 700 for wireless communication. Appliance 700 may be a base station (eg, BS 110 ), or a base station may include appliance 700 . In some aspects, the appliance 700 includes a receive component 702 and a transmit component 704, which can communicate with each other (eg, via one or more bus bars and/or one or more other components). As shown, the appliance 700 can communicate with another appliance 706, such as a UE, a base station, or another wireless communication device, using a receive component 702 and a transmit component 704. As further shown, appliance 700 may include one or more of decision component 708, as well as other examples.

In some aspects, appliance 700 may be configured to perform one or more of the operations described herein in connection with FIG. 3 . Additionally or alternatively, appliance 700 may be configured to perform one or more of the processes described herein, such as process 500 of FIG. 5 . In some aspects, the appliance 700 and/or one or more components shown in FIG. 7 may include one or more components of the base station described above in connection with FIG. 2 . Additionally or alternatively, one or more of the components shown in FIG. 7 may be implemented within one or more of the components described above in connection with FIG. 2 . Additionally or alternatively, one or more components of a set of components may be implemented, at least in part, as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

The receiving component 702 can receive communications from the appliance 706, such as reference signals, control information, data communications, or combinations thereof. Receiving component 702 may provide the received communication to one or more other components of appliance 700 . In some aspects, receiving component 702 can perform signal processing (eg, filtering, amplifying, demodulating, analog-to-digital, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, and others) on received communications example), and the processed signal may be provided to one or more other components of appliance 706. In some aspects, receive component 702 can include one or more of the antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or combinations thereof of the base station described above in connection with FIG. 2 .

The transmit component 704 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the appliance 706 . In some aspects, one or more other components of appliance 706 can generate communications and can provide the generated communications to transmitting component 704 for transmission to appliance 706 . In some aspects, transmit component 704 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog, multiplexing, interleaving, mapping or encoding, among other examples) on the generated communications, and can convert the processed The signal is sent to appliance 706 . In some aspects, transmit component 704 can include one or more of the antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or the like of the base station described above in connection with FIG. 2 . combination. In some aspects, transmit component 704 can be co-located with receive component 702 in a transceiver.

The receiving component 702 can receive capability information from a RedCap UE, the capability information indicating a reduced capability of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communications. Transmitting component 704 can transmit HD-FDD configuration information to the RedCap UE for HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information. The receive component 702 and/or the transmit component 704 can communicate by transmitting data or receiving data during HD-FDD communications based at least in part on the HD-FDD configuration information.

The determining component 708 can determine, for example, information to include in capability information received by the base station. Additionally, the determining component 708 can determine the information to be transmitted in the HD-FDD configuration information. Additionally, decision component 708 can decide data to communicate in HD-FDD communications.

The number and arrangement of components shown in Figure 7 are provided as examples. In practice, there may be additional, fewer, different, or differently arranged components than those shown in FIG. 7 . Furthermore, two or more components shown in FIG. 7 may be implemented within a single component, or a single component shown in FIG. 7 may be implemented as multiple distributed components. Additionally or alternatively, one set of component(s) shown in FIG. 7 may perform one or more functions described as being performed by another set of components shown in FIG. 7 .

The following provides an overview of various aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a reduced capability user equipment (RedCap UE), comprising: transmitting capability information to a base station, the capability information indicating that the RedCap UE performs half-duplex frequency division duplexing (HD) with - Reduced capabilities associated with FDD) communications; receiving from the base station HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capabilities information; and communicating by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information.

Aspect 2: The method of Aspect 1, wherein the HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication, the index information indicating: A downlink carrier index associated with a downlink carrier of one or more carriers that is configured to carry downlink transmissions from the base station to the RedCap UE during the HD-FDD communication and an uplink carrier index associated with an uplink carrier from the one or more carriers configured to carry from the RedCap UE to the base station during the HD-FDD communication uplink transmission.

Aspect 3: The method of any of Aspects 1-2, wherein the one or more carriers are semi-statically configured for the HD-FDD communication.

Aspect 4: The method of any of Aspects 1-3, wherein the index information is included in a system information (SI) communication or media access via broadcast or multicast to the group of UEs including the RedCap UEs Control Control Element (MAC CE) communication received in the Common Information Element.

Aspect 5: The method of any one of Aspects 1-4, wherein the index information is included in a message via a dedicated Radio Resource Control (RRC) message, a Medium Access Control Control Element (MAC CE), or a Dynamic Grant (DG) ) of the exclusive information elements received by the communication, the exclusive information elements are received individually or in conjunction with the common information elements including the index information.

Aspect 6: The method of any one of Aspects 1-5, wherein the HD-FDD configuration information includes time slot mode information, and the time slot mode information includes one or more of the following: first A slot pattern comprising one or more types of time and frequency resource mappings indicating one or more time and frequency resource mappings for a first set of consecutive slots or symbols configured on the downlink carrier a slot pattern; a second slot pattern comprising one or more time and frequency resource mappings indicative of a second contiguous slot or set of symbols configured on the uplink carrier or multiple types of slot patterns; or a third slot pattern including instructions for configuring on the uplink carrier, configuring on the downlink carrier, or as a guard period group One or more types of slot patterns for mapping of one or more time and frequency resources of a third consecutive set of slots or symbols for at least one of the states.

Aspect 7: The method of any one of Aspects 1-6, wherein the slot pattern information includes one or more of the following: periodic information indicating a relationship with the first time slot a first periodicity associated with the pattern, a second periodicity associated with the second slot pattern, or a third periodicity associated with the third slot pattern; reference numbering scheme information, the reference numbering scheme information indicating a first reference numbering scheme associated with the first slot pattern, a second reference numbering scheme associated with the second slot pattern, or a third reference numbering scheme associated with the third slot pattern; Sorting information, the sorting information indicates the arrangement of the first slot mode, the second slot mode or the third slot mode in the time domain; monitoring information, the monitoring information indicates that the first slot mode is associated with the first PDCCH monitoring occasion, the second PDCCH monitoring occasion associated with the second slot pattern, or the third PDCCH monitoring occasion associated with the third slot pattern; or bandwidth part (BWP) configuration information, The BWP configuration information indicates a first BWP configuration of uplink BWP and downlink BWP associated with the first slot mode, uplink BWP and downlink associated with the second slot mode The second BWP configuration of the BWP, or the third BWP configuration of the uplink BWP and downlink BWP associated with the third slot mode.

Aspect 8: The method of any of Aspects 1-7, wherein the slot mode information is included in a system information (SI) communication or media via broadcast or multicast to the group of UEs including the RedCap UEs Access Control Element (MAC CE) communication received in the Common Information Element.

Aspect 9: The method of any of Aspects 1-8, wherein the slot mode information is included in dedicated information received via dedicated Radio Resource Control (RRC) messages, MAC CE, or Dynamic Grant (DG) communications element, the exclusive information element is received alone or in conjunction with a common information element that includes the slot mode information.

Aspect 10: The method of any of Aspects 1-9, further comprising: receiving group common downlink control information (GC-DCI) via a downlink carrier common to the group of RedCap UEs including the RedCap UE, The GC-DCI indicates the respective uplink carrier index and downlink carrier index to be utilized by the RedCap UE.

Aspect 11: The method of any of Aspects 1-10, further comprising: receiving group common downlink control information (GC-DCI) via a downlink carrier common to the group of RedCap UEs including the RedCap UE, The GC-DCI indicates a respective slot mode from the plurality of slot modes to be used by the RedCap UE for the HD-FDD communication and a valid duration associated with utilization of the respective slot mode.

Aspect 12: The method of any of Aspects 1-11, wherein the HD-FDD configuration information indicates a guard period associated with switching from utilizing the downlink carrier to utilizing the uplink carrier, or Utilize the uplink carrier to switch to utilizing the guard period associated with the downlink carrier.

Aspect 13: The method of any of Aspects 1-12, wherein the HD-FDD configuration information indicates a guard period associated with switching from utilizing the downlink carrier to utilizing the uplink carrier, or Switching from the uplink carrier to the downlink carrier is associated with a guard period, the duration of which is associated with the active uplink BWP or active downlink BWP that is actively used for the HD-FDD communication The subcarrier spacing is correlated.

Aspect 14: The method of any of Aspects 1-13, wherein the HD-FDD configuration information indicates a guard period associated with switching from utilizing a downlink carrier to utilizing an uplink carrier, or Utilize the uplink carrier to switch to utilizing the downlink carrier associated guard period associated with utilizing the flexible time slot or flexible symbol associated with the time slot pattern configured for the HD-FDD communication.

Aspect 15: The method of any of Aspects 1-14, wherein the HD-FDD configuration information includes power control parameters to be used by the RedCap UE to transmit uplink communications during the HD-FDD communications .

Aspect 16: The method of any of Aspects 1-15, wherein the HD-FDD configuration information includes a Physical Random Access Channel (PRACH) to be used by the RedCap UE during the HD-FDD communication, Power control parameters for the transmission of Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH) and/or Sounding Reference Signal (SRS) based at least in part on the HD-FDD being performed of reduced insertion loss, increased power efficiency, increased UE receive sensitivity, or reduced peak transmit power associated with the RedCap UE when communicating.

Aspect 17: The method of any of Aspects 1-16, wherein the HD-FDD configuration information includes power control parameters to be utilized by the RedCap UE during the HD-FDD communication, the power control parameters including Offset for received target power, offset for UE-configured maximum output power, scaling factor or offset for reference signal power in pathloss estimation, or associated with transmit power control commands and transmit power rise Associated enhanced granularity, range, and power control adjustment status.

Aspect 18: The method of any of Aspects 1-17, wherein the HD-FDD configuration information includes radio resource management (RRM) procedures to be performed by the RedCap UE during the HD-FDD communication, Measurement and reporting parameters associated with radio link monitoring (RLM) procedures or cellular positioning and beam management procedures (BM procedures) based at least in part on being associated with the RedCap UE while conducting the HD-FDD communication connected time slot mode configuration, bandwidth part (BWP) configuration, reduced insertion loss, improved power efficiency or improved UE receive sensitivity.

Aspect 19: The method of any of Aspects 1-18, wherein the HD-FDD configuration information includes radio resource management (RRM) procedures to be performed by the RedCap UE during the HD-FDD communication, Measurement and reporting parameters associated with radio link monitoring (RLM) procedures or cellular positioning and beam management procedures (BM procedures) indicating measurements associated with performing the RRM procedure, the RLM procedure, or the BM procedure List of objects, report configuration, measurement ID, quantity configuration or measurement gap configuration.

Aspect 20: The method of any of Aspects 1-19, wherein the HD-FDD configuration information includes correlations to RRM measurements to be performed by the RedCap UE in conjunction with a cell selection procedure, a cell reselection procedure, or a handover procedure linked measurement and reporting parameters.

Aspect 21: The method of any one of Aspects 1-20, wherein the HD-FDD configuration information is via system information (SI), radio resource control (RRC) information, media access control control element (MAC) CE) or Dynamic Grant (DG) communications are received.

Aspect 22: The method of any of Aspects 1-21, wherein the capability information indicates that the RedCap UE's duplexer is replaced by a switch and a filter.

Aspect 23: An apparatus for wireless communication at a device, comprising: a processor; memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the processor to The appliance performs the method of one or more of Aspects 1-22.

Aspect 24: An apparatus for wireless communication comprising memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform as in Aspect 1- The method of one or more aspects of 22.

Aspect 25: An apparatus for wireless communication comprising at least one means for performing the method of one or more of Aspects 1-22.

Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the methods of one or more of Aspects 1-22.

Aspect 27: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that when executed by one or more processors of a device The apparatus is caused to perform the method of one or more of Aspects 1-22.

Aspect 28: A method of wireless communication performed by a base station, comprising: receiving capability information from a reduced capability user equipment (RedCap UE), the capability information indicating that the RedCap UE performs half-duplex frequency division duplex (HD) with - a reduced capability associated with FDD) communication; transmits to the RedCap UE HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and communicating by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information.

Aspect 29: An apparatus for wireless communication at a device, comprising: a processor; memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the processor to The appliance performs the method as in Section 28.

Aspect 30: An apparatus for wireless communication comprising memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform as in Aspect 28 method.

Aspect 31: An apparatus for wireless communication comprising at least one means for performing the method of Aspect 28.

Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of Aspect 28.

Aspect 33: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that when executed by one or more processors of a device The device is caused to perform the method of aspect 28.

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

As used herein, the term "component" is intended to be broadly interpreted as hardware and/or a combination of hardware and software. Whether referred to as software, firmware, intermediate software, microcode, hardware description language, or otherwise, "software" should 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 and/or functions, and other examples. As used herein, a processor is implemented in hardware and/or in a combination of hardware and software. It will be apparent that the systems and/or methods described herein may be implemented in different forms of hardware and/or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Accordingly, the operation and behavior of systems and/or methods are described herein without reference to specific software code, it being understood that software and hardware may be designed to implement systems and/or methods based at least in part on the descriptions herein. or method.

As used herein, depending on the context, satisfying a threshold may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, or the like.

Even if specific combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of each aspect. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent request item listed below may directly depend on only one request item, the disclosure of various aspects includes each dependent request item in combination with every other request item in the set of request items. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to encompass a, b, c, a-b, a-c, b-c, and a-b-c, and any combination with multiples of the same elements (eg, a-a, a-a-a, a-a-b , a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c and c-c-c or any other ordering of a, b and c).

None of the elements, acts, or instructions used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items, and can be used interchangeably with "one or more." Also, as used herein, the article "the" is intended to include the item or items referenced in conjunction with the article "the", and can be used interchangeably with "one or more." Furthermore, as used herein, the terms "collection" and "group" are intended to include one or more items (eg, related items, unrelated items, or a combination of related items and unrelated items), and may be combined with "one or more items" "" is used interchangeably. Where only one item is expected, the phrase "only one" or similar language is used. Furthermore, as used herein, the terms "has," "have," "having," etc. are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on" unless expressly stated otherwise. Also, as used herein, the term "or" when used in a series is intended to be inclusive, and unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of"), Otherwise can be used interchangeably with "and/or".

100: Wi-Fi 102a: Macro cell 102b: pico cell 102c: Femtocell 110:BS (Base Station) 110a: Macro BS (Base Station) 110b: Pico BS (Base Station) 110c: Femto BS (Base Station) 110d: Relay BS (Base Station) 120: UE (User Equipment) 120a, 120b, 120c, 120d, 120e: UE (User Equipment) 130: Network Controller 200: Example 212, 262: data source 220, 264: transmit processor 230, 266: Transmit (TX) Multiple Input Multiple Output (MIMO) Processor 232a to 232t: Modulator (MOD) 234a to 234t, 252a to 252r: Antenna 236, 256: MIMO detector 238, 258: Receiver processor 239, 260: data slot 240, 280, 290: Controller/Processor 242, 282, 292: memory 244, 294: communication unit 246: Scheduler 254a to 254r: Demodulator (DEMOD) 300: Example 310, 320, 330, 340, 350: Labels 400, 500: Process 410, 420, 430, 510, 520, 530: Blocks 600, 700: Appliances 602, 702: Receive components 604, 704: Launch components 606, 706: Appliances 608, 708: Determine components

In order that the above-described features of the present disclosure may be understood in detail, a more detailed description of the invention briefly summarized above may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same symbols in different drawings may identify the same or similar elements.

1 is a diagram illustrating an example of a wireless network in accordance with various aspects of the present disclosure.

2 is a diagram illustrating an example of a base station in a wireless network communicating with user equipment (UE) in accordance with various aspects of the present disclosure.

3 is a diagram illustrating configuration and signaling support associated with providing half-duplex frequency division duplex (HD-FDD) operation for reduced capability user equipment (RedCap UE) in accordance with various aspects of the present disclosure. Illustration of an example.

4-5 are diagrams illustrating example processes associated with providing configuration and signaling support for HD-FDD operation for RedCap UEs in accordance with various aspects of the present disclosure.

6-7 are diagrams illustrating example appliances associated with providing configuration and signaling support for HD-FDD operation for RedCap UEs in accordance with various aspects of the present disclosure.

110: BS (Base Station)

120: UE (User Equipment)

300: Example

310, 320, 330, 340, 350: Labels

Claims (50)

A reduced capability user equipment (RedCap UE) for wireless communication, comprising: memory; and One or more processors operatively coupled to the memory, the memory and the one or more processors configured to: transmitting capability information to the base station, the capability information indicating the reduced capability of the RedCap UE associated with conducting Half-Duplex Frequency Division Duplex (HD-FDD) communications; receiving from the base station HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information based at least in part on the capability information; and Communication is performed by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information. The RedCap UE of claim 1, wherein the HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication, the index information indicating: a downlink carrier index associated with a downlink carrier from the one or more carriers configured to carry downlink from the base station to the RedCap UE during the HD-FDD communication link transmission, and an uplink carrier index associated with an uplink carrier from the one or more carriers configured to carry uplink from the RedCap UE to the base station during the HD-FDD communication link transmission. The RedCap UE of claim 2, wherein the one or more carriers are semi-statically configured for the HD-FDD communication. The RedCap UE of claim 2, wherein the index information is included in the reception via a System Information (SI) communication or a Media Access Control Control Element (MAC CE) communication that is broadcast or multicast to the UE group that includes the RedCap UE in the common information element of . The RedCap UE of claim 2, wherein the index information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, a medium access control control element (MAC CE), or a dynamic grant (DG) communication, The exclusive information element is received alone or in conjunction with a common information element that includes the index information. The RedCap UE of claim 2, wherein the HD-FDD configuration information includes time slot mode information, and the time slot mode information includes one or more of the following: a first slot pattern comprising one or more types of time and frequency resource mappings indicative of one or more time and frequency resource mappings for a first set of contiguous slots or symbols configured on the downlink carrier time slot mode, A second slot pattern that includes one or more types of time and frequency resource mappings indicative of one or more time and frequency resource mappings for a second set of contiguous slots or symbols configured on the uplink carrier the slot mode of , or A third slot pattern including a third time slot pattern indicating at least one of configuration on the uplink carrier, configuration on the downlink carrier, or as a guard period configuration One or more types of slot patterns for one or more time and frequency resource mappings of consecutive slots or sets of symbols. The RedCap UE of claim 6, wherein the time slot mode information includes one or more of the following: periodicity information indicating a first periodicity associated with the first slot pattern, a second periodicity associated with the second slot pattern, or a periodicity associated with the third slot pattern the third periodicity; reference numbering scheme information indicating a first reference numbering scheme associated with the first slot pattern, a second reference numbering scheme associated with the second slot pattern, or a third slot pattern a third reference numeral scheme associated with the mode; sorting information, the sorting information indicating the arrangement of the first slot mode, the second slot mode or the third slot mode in the time domain; Monitoring information indicating a first PDCCH monitoring occasion associated with the first slot pattern, a second PDCCH monitoring occasion associated with the second slot pattern, or a second PDCCH monitoring occasion associated with the third slot pattern the third PDCCH monitoring occasion; or Bandwidth Part (BWP) configuration information indicating a first BWP configuration of uplink BWP and downlink BWP associated with the first slot mode, associated with the second slot mode The second BWP configuration of the uplink BWP and the downlink BWP, or the third BWP configuration of the uplink BWP and the downlink BWP associated with the third slot pattern. The RedCap UE of claim 6, wherein the slot mode information is included in a System Information (SI) communication or a Media Access Control Control Element (MAC CE) that is broadcast or multicast to the UE group that includes the RedCap UE In the common information element received by the communication. The RedCap UE of claim 6, wherein the slot mode information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, MAC CE or dynamic grant (DG) communication, the dedicated information element alone received either locally or in conjunction with a common information element that includes the slot mode information. The RedCap UE of claim 1, wherein the one or more processors are further configured to: Receive Group Common Downlink Control Information (GC-DCI) via a downlink carrier common to the group of RedCap UEs including the RedCap UE, the GC-DCI indicating the respective uplink carrier index to be utilized by the RedCap UE and the downlink carrier index. The RedCap UE of claim 1, wherein the one or more processors are further configured to: Receive group common downlink control information (GC-DCI) via a downlink carrier common to the group of RedCap UEs that includes the RedCap UE, the GC-DCI indicating that from a plurality of slot patterns to be used by the RedCap UE A respective slot mode of the HD-FDD communication and a valid duration associated with utilization of the respective slot mode. The RedCap UE of claim 1, wherein the HD-FDD configuration information indicates a guard period associated with switching from using a downlink carrier to using an uplink carrier, or switching from using an uplink carrier to using a downlink carrier The guard period associated with the link carrier. The RedCap UE of claim 1, wherein the HD-FDD configuration information indicates a guard period associated with switching from using a downlink carrier to using an uplink carrier, or switching from using an uplink carrier to using a downlink carrier A guard period associated with a link carrier, the duration of which is related to the subcarrier spacing associated with the active uplink BWP or active downlink BWP that is actively used for the HD-FDD communication. The RedCap UE of claim 1, wherein the HD-FDD configuration information indicates a guard period associated with switching from using a downlink carrier to using an uplink carrier, or switching from using an uplink carrier to using a downlink carrier A guard period associated with the link carrier that is associated with utilizing flexible slots or flexible symbols associated with the slot mode configured for this HD-FDD communication. The RedCap UE of claim 1, wherein the HD-FDD configuration information includes power control parameters to be used by the RedCap UE to transmit uplink communications during the HD-FDD communications. The RedCap UE of claim 1, wherein the HD-FDD configuration information includes a physical random access channel (PRACH), a physical uplink control channel (PUCCH) to be used by the RedCap UE during the HD-FDD communication , Power control parameters for the transmission of the Physical Uplink Shared Channel (PUSCH) and/or Sounding Reference Signal (SRS), the power control parameters being based, at least in part, on data associated with the RedCap UE during the HD-FDD communication Reduced insertion loss, improved power efficiency, improved UE receive sensitivity or reduced peak transmit power. The RedCap UE of claim 1, wherein the HD-FDD configuration information includes power control parameters to be utilized by the RedCap UE during the HD-FDD communication, the power control parameters including an offset for receiving target power, Offset for UE-configured maximum output power, scaling factor or offset for reference signal power in pathloss estimation, or enhanced granularity, range, and Power control adjustment status. The RedCap UE of claim 1, wherein the HD-FDD configuration information includes Radio Resource Management (RRM) procedures, Radio Link Monitoring (RLM) procedures to be performed by the RedCap UE during the HD-FDD communication, or Measurement and reporting parameters associated with cellular positioning and beam management procedures (BM procedures) based at least in part on the slot mode configuration, bandwidth associated with the RedCap UE during the HD-FDD communication Partial (BWP) configuration, reduced insertion loss, improved power efficiency or improved UE receive sensitivity. The RedCap UE of claim 1, wherein the HD-FDD configuration information includes Radio Resource Management (RRM) procedures, Radio Link Monitoring (RLM) procedures to be performed by the RedCap UE during the HD-FDD communication, or Measurement and reporting parameters associated with cellular positioning and beam management procedures (BM procedures), the measurement and reporting parameters indicating measurement objects associated with performing the RRM procedure, the RLM procedure or the BM procedure, report configuration, measurement identification, List of quantity configuration or measurement gap configuration. The RedCap UE of claim 1, wherein the HD-FDD configuration information includes measurement and reporting parameters associated with RRM measurements to be performed by the RedCap UE in conjunction with a cell selection procedure, a cell reselection procedure, or a handover procedure. The RedCap UE of claim 1, wherein the HD-FDD configuration information is communicated via System Information (SI), Radio Resource Control (RRC) message, Media Access Control Control Element (MAC CE) or Dynamic Grant (DG) received. The RedCap UE of claim 1, wherein the capability information indicates that the duplexer of the RedCap UE is replaced by switches and filters. A method of wireless communication performed by a reduced capability user equipment (RedCap UE), comprising: transmitting capability information to the base station, the capability information indicating the reduced capability of the RedCap UE associated with conducting Half-Duplex Frequency Division Duplex (HD-FDD) communications; receiving from the base station HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information based at least in part on the capability information; and Communication is performed by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information. The method of claim 23, wherein the HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication, the index information indicating: a downlink carrier index associated with a downlink carrier from the one or more carriers configured to carry downlink from the base station to the RedCap UE during the HD-FDD communication link transmission, and an uplink carrier index associated with an uplink carrier from the one or more carriers configured to carry uplink from the RedCap UE to the base station during the HD-FDD communication link transmission. The method of claim 24, wherein the one or more carriers are semi-statically configured for the HD-FDD communication. The method of claim 24, wherein the index information is included in a system information (SI) communication or a Media Access Control Control Element (MAC CE) communication that is broadcast or multicast to a UE group including the RedCap UE. in the common information element. The method of claim 24, wherein the index information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, a medium access control control element (MAC CE), or a dynamic grant (DG) communication, the Exclusive information elements are received individually or in conjunction with common information elements that include the index information. The method of claim 24, wherein the HD-FDD configuration information includes time slot mode information, the time slot mode information including one or more of the following: a first slot pattern comprising one or more types of time and frequency resource mappings indicative of one or more time and frequency resource mappings for a first set of contiguous slots or symbols configured on the downlink carrier time slot mode, A second slot pattern that includes one or more types of time and frequency resource mappings indicative of one or more time and frequency resource mappings for a second set of contiguous slots or symbols configured on the uplink carrier the slot mode of , or A third slot pattern including a third time slot pattern indicating at least one of configuration on the uplink carrier, configuration on the downlink carrier, or as a guard period configuration One or more types of slot patterns for one or more time and frequency resource mappings of consecutive slots or sets of symbols. The method of claim 28, wherein the slot mode information includes one or more of the following: periodicity information indicating a first periodicity associated with the first slot pattern, a second periodicity associated with the second slot pattern, or a periodicity associated with the third slot pattern the third periodicity; reference numbering scheme information indicating a first reference numbering scheme associated with the first slot pattern, a second reference numbering scheme associated with the second slot pattern, or a third slot pattern a third reference numeral scheme associated with the mode; sorting information, the sorting information indicating the arrangement of the first slot mode, the second slot mode or the third slot mode in the time domain; Monitoring information indicating a first PDCCH monitoring occasion associated with the first slot pattern, a second PDCCH monitoring occasion associated with the second slot pattern, or a second PDCCH monitoring occasion associated with the third slot pattern the third PDCCH monitoring occasion; or Bandwidth Part (BWP) configuration information indicating a first BWP configuration of uplink BWP and downlink BWP associated with the first slot mode, associated with the second slot mode The second BWP configuration of the uplink BWP and the downlink BWP, or the third BWP configuration of the uplink BWP and the downlink BWP associated with the third slot pattern. The method of claim 28, wherein the slot mode information is included in a system information (SI) communication or a medium access control control element (MAC CE) communication via broadcast or multicast to the group of UEs including the RedCap UEs in the received common information element. The method of claim 28, wherein the slot mode information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, MAC CE or dynamic grant (DG) communication, the dedicated information element alone or received in conjunction with a common information element that includes the slot mode information. The method of claim 23, further comprising: Receive Group Common Downlink Control Information (GC-DCI) via a downlink carrier common to the group of RedCap UEs including the RedCap UE, the GC-DCI indicating the respective uplink carrier index to be utilized by the RedCap UE and the downlink carrier index. The method of claim 23, further comprising: Receive group common downlink control information (GC-DCI) via a downlink carrier common to the group of RedCap UEs that includes the RedCap UE, the GC-DCI indicating that from a plurality of slot patterns to be used by the RedCap UE A respective slot mode of the HD-FDD communication and a valid duration associated with utilization of the respective slot mode. The method of claim 23, wherein the HD-FDD configuration information indicates a guard period associated with switching from using a downlink carrier to using an uplink carrier, or switching from using an uplink carrier to using a downlink carrier The guard period associated with the channel carrier. The method of claim 23, wherein the HD-FDD configuration information indicates a guard period associated with switching from using a downlink carrier to using an uplink carrier, or switching from using an uplink carrier to using a downlink carrier A guard period associated with a channel carrier, the duration of the guard period being related to the subcarrier spacing associated with the active uplink BWP or active downlink BWP that is actively used for the HD-FDD communication. The method of claim 23, wherein the HD-FDD configuration information indicates a guard period associated with switching from using a downlink carrier to using an uplink carrier, or switching from using an uplink carrier to using a downlink carrier A guard period associated with the channel carrier, the guard period being associated with utilizing the flexible time slot or flexible symbol associated with the time slot mode configured for the HD-FDD communication. The method of claim 23, wherein the HD-FDD configuration information includes power control parameters to be used by the RedCap UE to transmit uplink communications during the HD-FDD communications. The method of claim 23, wherein the HD-FDD configuration information includes a physical random access channel (PRACH), a physical uplink control channel (PUCCH), a physical random access channel (PRACH), a physical uplink control channel (PUCCH), Power control parameters for transmission of Physical Uplink Shared Channel (PUSCH) and/or Sounding Reference Signal (SRS) based at least in part on reductions associated with the RedCap UE while conducting the HD-FDD communication insertion loss, improved power efficiency, improved UE receive sensitivity or reduced peak transmit power. The method of claim 23, wherein the HD-FDD configuration information includes power control parameters to be utilized by the RedCap UE during the HD-FDD communication, the power control parameters including an offset for receiving target power, Offset from UE-configured maximum output power, scaling factor or offset for reference signal power in pathloss estimation, or enhanced granularity, range, and power associated with transmit power control commands and transmit power rises Controls the adjustment state. The method of claim 23, wherein the HD-FDD configuration information includes radio resource management (RRM) procedures, radio link monitoring (RLM) procedures, or cellular procedures to be performed by the RedCap UE during the HD-FDD communication Measurement and reporting parameters associated with positioning and beam management procedures (BM procedures) based at least in part on the slot mode configuration, bandwidth portion associated with the RedCap UE during the HD-FDD communication (BWP) configuration, reduced insertion loss, improved power efficiency or improved UE receive sensitivity. The method of claim 23, wherein the HD-FDD configuration information includes radio resource management (RRM) procedures, radio link monitoring (RLM) procedures, or cellular procedures to be performed by the RedCap UE during the HD-FDD communication Measurement and reporting parameters associated with positioning and beam management procedures (BM procedures), the measurement and reporting parameters indicating measurement objects, report configurations, measurement identifiers, quantities associated with performing the RRM procedure, the RLM procedure or the BM procedure A list of configurations or measurement gap configurations. The method of claim 23, wherein the HD-FDD configuration information includes measurement and reporting parameters associated with RRM measurements to be performed by the RedCap UE in conjunction with a cell selection procedure, a cell reselection procedure, or a handover procedure. The method of claim 23, wherein the HD-FDD configuration information is received via system information (SI), radio resource control (RRC) messages, media access control control elements (MAC CE), or dynamic grant (DG) communications of. The method of claim 23, wherein the capability information indicates that the RedCap UE's duplexer is replaced by switches and filters. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: One or more instructions that, when executed by one or more processors of a reduced capability user equipment (RedCap UE), cause the RedCap UE to: transmitting capability information to the base station, the capability information indicating the reduced capability of the RedCap UE associated with conducting Half-Duplex Frequency Division Duplex (HD-FDD) communications; receiving from the base station HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information based at least in part on the capability information; and Communication is performed by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information. An appliance for wireless communication, comprising: means for transmitting capability information to a base station, the capability information indicating the reduced capability of the appliance associated with conducting half-duplex frequency division duplex (HD-FDD) communications; means for receiving, from the base station, HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and Means for communicating by transmitting or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information. A base station for wireless communication, comprising: memory; and One or more processors operatively coupled to the memory, the memory and the one or more processors configured to: receiving capability information from a reduced capability user equipment (RedCap UE), the capability information indicating the reduced capability of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communications; transmitting, to the RedCap UE, HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and Communication is performed by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information. A method of wireless communication performed by a base station, comprising: receiving capability information from a reduced capability user equipment (RedCap UE), the capability information indicating the reduced capability of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communications; transmitting, to the RedCap UE, HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and Communication is performed by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: One or more instructions that, when executed by one or more processors of a base station, cause the base station to: receiving capability information from a reduced capability user equipment (RedCap UE), the capability information indicating the reduced capability of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communications; transmitting, to the RedCap UE, HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and Communication is performed by transmitting data or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information. An appliance for wireless communication, comprising: means for receiving capability information from a reduced capability user equipment (RedCap UE), the capability information indicating the reduced capability of the RedCap UE associated with conducting half-duplex frequency division duplex (HD-FDD) communication; means for transmitting, to the RedCap UE, HD-FDD configuration information for the HD-FDD communication with the base station, the HD-FDD configuration information being based at least in part on the capability information; and Means for communicating by transmitting or receiving data during the HD-FDD communication based at least in part on the HD-FDD configuration information.

Images