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

Abstract

In summary, the various embodiments of this disclosure relate to wireless communication. In some embodiments, a Reduced Capability User Equipment (RedCap UE) can transmit capability information to a base station, indicating the reduced capabilities of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication. The RedCap UE can receive HD-FDD configuration information from the base station for HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information. The RedCap UE can communicate by transmitting or receiving data during HD-FDD communication, at least partially based on the HD-FDD configuration information. Numerous other embodiments are described.

Description

[Technical Field]

[0001] In general, the various aspects of this disclosure relate to wireless communication and to technologies and apparatuses for providing configuration and signaling support for half-duplex frequency division duplex (HD-FDD) operation for Reduced Capability User Equipment (RedCap UE). [Previous Technology]

[0002] Wireless communication systems are widely deployed to provide various telecommunications services such as telephone, video, data, communications, and broadcasting. Typical wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / Advanced LTE is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard released by the 3rd Generation Partnership Project (3GPP).

[0003] A wireless network may include multiple base stations (BSs) capable of supporting communication for multiple user equipment (UEs). UEs may communicate with BSs via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmitter-Receiver Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. NR (which can also be referred to as 5G) is an enhancement set of the LTE mobile standard released by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM)) on the uplink (UL), thereby better supporting mobile broadband internet access, as well as 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. [Summary of the Invention]

[0005] In some embodiments, a simplified capability user equipment (RedCap UE) for wireless communication includes a memory and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: transmit capability information to a base station, the capability information indicating the simplified capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; receive from the base station HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and perform communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information.

[0006] In some embodiments, a method of wireless communication performed by a RedCap UE includes: transmitting capability information to a base station, the capability information indicating a simplified capability of the RedCap UE associated with performing HD-FDD communication; receiving from the base station HD-FDD configuration information for performing HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and performing communication by transmitting or receiving data during the HD-FDD communication, based at least partially on the HD-FDD configuration information.

[0007] In some embodiments, 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 to: transmit capability information to a base station, the capability information indicating the RedCap UE's simplified capabilities associated with performing HD-FDD communication; receive from the base station HD-FDD configuration information for performing HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and communicate by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information.

[0008] In some embodiments, an apparatus for wireless communication includes: a component for transmitting capability information to a base station, the capability information indicating a simplified capability of the apparatus associated with performing HD-FDD communication; a component for receiving HD-FDD configuration information from the base station for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and a component for communicating by transmitting or receiving data during the HD-FDD communication, based at least partially on the HD-FDD configuration information.

[0009] In some embodiments, a base station for wireless communication includes a memory and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receive capability information from a RedCap UE, the capability information indicating the RedCap UE's simplified capabilities associated with performing HD-FDD communication; transmit to the RedCap UE HD-FDD configuration information for performing HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and perform communication by transmitting or receiving data during HD-FDD communication, at least partially based on the HD-FDD configuration information.

[0010] In some embodiments, a method of wireless communication performed by a base station includes: receiving capability information from a RedCap UE, the capability information indicating a simplified capability of the RedCap UE associated with performing HD-FDD communication; transmitting to the RedCap UE HD-FDD configuration information for performing HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and performing communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information.

[0011] In some embodiments, 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 to: receive capability information from a RedCap UE, the capability information indicating the RedCap UE's simplified capabilities associated with performing HD-FDD communication; transmit to the RedCap UE HD-FDD configuration information for performing HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and perform communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information.

[0012] In some embodiments, an apparatus for wireless communication includes: a component for receiving capability information from a RedCap UE, the capability information indicating the RedCap UE’s simplified capabilities associated with performing HD-FDD communication; a component for transmitting to the RedCap UE HD-FDD configuration information for performing HD-FDD communication with a base station, the HD-FDD configuration information being at least partially based on the capability information; and a component for communicating by transmitting or receiving data during HD-FDD communication, based at least partially on the HD-FDD configuration information.

[0013] In general, the various types include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and specifications and as shown by the drawings and specifications.

[0014] The foregoing has provided a fairly broad overview of the features and technical advantages of the examples according to this disclosure in order to better understand the following detailed description. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and operation) and the associated advantages will be better understood when considered in conjunction with the drawings, based on the following description. Each drawing in the drawings is provided for illustrative and descriptive purposes and is not intended to define a limitation on the scope of the claims.

Implementation Method

[0021] Various forms of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these forms are provided so that this disclosure will be thorough and complete and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will understand that the scope of this disclosure is intended to cover any form of this disclosure disclosed herein, whether implemented independently of or in combination with any other form of this disclosure. For example, an apparatus or a method may be implemented using any number of the forms set forth herein. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than or different from the various forms of this disclosure set forth herein. It should be understood that any form of this disclosure disclosed herein may be embodied by one or more elements of a claim.

[0022] Various devices and technologies will now be used to describe several aspects of a telecommunications system. These devices and technologies will be described in detail below and illustrated in the accompanying drawings, using various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such an element is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0023] It should be noted that although the present document may use terms commonly associated with 5G or NR radio access technology (RAT) to describe various forms, the forms of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0024] Figure 1 is a diagram illustrating examples of various forms of a wireless network 100 according to this disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, as well as other examples. The wireless network 100 may include multiple 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 a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), Access Point, Transmitter-Receiver Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0025] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. A picocell can cover a relatively small geographic area and can allow unrestricted access by UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macrocell can be referred to as a macro BS. A BS for a picocell can be referred to as a pico BS. A BS for a femtocell can be referred to as a femtocell BS or a home BS. In the example shown in Figure 1, BS 110a can be a macro BS for macrocell 102a, BS 110b can be a pico BS for picocell 102b, and BS 110c can be a femtocell BS for femtocell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB” and “cell” are used interchangeably in this document.

[0026] In some configurations, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some configurations, BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

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

[0028] Wireless network 100 can be a heterogeneous network comprising different types of BSs (such as macro BS, pico BS, femto BS, repeater BS, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and repeater BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0029] The network controller 130 can be coupled to a group of BSs and can provide coordination and control for these BSs. The network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other directly or indirectly via wireless or wired backhaul.

[0030] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smartphone), 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, a camera, a gaming device, a small laptop, a smart laptop, a thin and light laptop, a medical device or equipment, a biometric sensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), an entertainment device (e.g., a music or video device, or a satellite radio unit, etc.), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0031] Some UEs can 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, which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links, for example. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components and / or memory components. In some cases, the processor components and memory components can be coupled together. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0032] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0033] In some configurations, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols) and / or mesh networks. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described herein as being performed by base station 110.

[0034] The device of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the device of the wireless network 100 can communicate using an operating band with a first frequency range (FR1) (which can span from 410 MHz to 7.125 GHz), and / or can communicate using an operating band with a second frequency range (FR2) (which can span from 24.25 GHz to 52.6 GHz). The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency bands. Although a portion of FR1 is greater than 6 GHz, FR1 is generally referred to as the “below 6 GHz” band. Similarly, FR2 is generally referred to as the “millimeter wave” band, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) recognized as a “millimeter wave” band by the International Telecommunication Union (ITU). Therefore, unless otherwise explicitly stated, it should be understood that the terms "below 6 GHz" and the like (if used herein) can broadly refer to frequencies below 6 GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., above 7.125 GHz). Similarly, unless otherwise explicitly stated, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., below 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0035] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0036] Figure 2 is a diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to various embodiments of the present disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein generally, T ≥ 1 and R ≥ 1.

[0037] At base station 110, transmit processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for the UE based at least in part on the Channel Quality Indicator (CQI) received from each UE, process (e.g., code and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, permission and / or upper-layer signaling), and provide burden symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, burden symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can (e.g., for OFDM) process its respective output symbol stream to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t respectively.

[0038] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can (e.g., for OFDM) further process the input sample to obtain received symbols. MIMO detector 256 can obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data slot 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine the Reference Signal Received Power (RSRP) parameter, Received Signal Strength Indicator (RSSI) parameter, Reference Signal Received Quality (RSRQ) parameter, and / or Channel Quality Indicator (CQI) parameter, as well as other parameters. In some cases, one or more components of the UE 120 may be included in the housing.

[0039] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include one or more devices, such as those in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0040] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included in the following: one or more antenna panels, antenna groups, antenna element sets and / or antenna arrays, and other examples. Antenna panels, antenna groups, antenna element sets and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets and / or antenna arrays may include one or more antenna elements coupled to one or more transmitting and / or receiving components (such as one or more components of FIG. 2).

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

[0042] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can 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 communication. In some embodiments, modulators and demodulators (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some embodiments, base station 110 includes transceivers. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220 and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform various forms of any of the methods described herein (e.g., as described with reference to Figures 3-7).

[0043] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform one or more techniques associated with providing configuration and signaling support for HD-FDD operation of RedCap UE, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform or direct the operation of, for example, process 400 of FIG. 4, process 500 of FIG. 5, and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some embodiments, memory 242 and / or memory 282 may include non-transitory computer-readable media storing one or more instructions (e.g., 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 (e.g., directly, or after compilation, translation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or instruct operations such as process 400 of FIG. 4, process 500 of FIG. 5, and / or other processes as described herein. In some cases, the execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions, among other examples.

[0044] In some embodiments, a Reduced Capability User Equipment (RedCap UE) (e.g., UE 120) includes: components for transmitting capability information to a base station, the capability information indicating the reduced capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; components for receiving HD-FDD configuration information from the base station for performing HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and / or components for communicating by transmitting or receiving data during HD-FDD communication, at least partially based on the HD-FDD configuration information. Components for the RedCap UE to perform the operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receiver processor 258, transmitter processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0045] In some configurations, the RedCap UE includes: a component for receiving group common downlink control information (GC-DCI) via a downlink carrier shared by the RedCap UE group (including the RedCap UE), wherein the GC-DCI indicates the respective uplink carrier index and downlink carrier index to be used by the RedCap UE.

[0046] In some configurations, the RedCap UE includes: a component for receiving GC-DCI via a downlink carrier shared by the RedCap UE group (including the RedCap UE), wherein the GC-DCI indicates a particular time slot mode from a plurality of time slot modes to be used by the RedCap UE for HD-FDD communication and an effective duration associated with the use of the particular time slot mode.

[0047] In some embodiments, the base station (BS 110) includes: components for receiving capability information from the RedCap UE, the capability information indicating the RedCap UE's simplified capabilities associated with performing half-duplex frequency division duplex (HD-FDD) communication; components for transmitting HD-FDD configuration information to the RedCap UE for HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; or components for communicating by transmitting or receiving data during HD-FDD communication, at least partially based on the HD-FDD configuration information. Components for the base station to perform the operations described herein may include, for example, one or more of the following: transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

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

[0049] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0050] The base station can communicate data with a plurality of UEs in networks such as LTE networks and / or 5G / NR networks. Data communication may include downlink communication from the base station to the plurality of UEs and uplink communication from the plurality of UEs to the base station. The plurality of UEs may include conventional UEs and / or RedCap UEs. RedCap UEs may include streamlined capabilities compared to those included in conventional UEs. For example, RedCap UEs may include fewer transmit antennas and / or fewer receive antennas compared to conventional UEs. RedCap UEs may also have less stringent latency and throughput (e.g., bit rate) requirements compared to conventional UEs. Furthermore, RedCap UEs may 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 smartwatches, smart wristbands, etc.). Examples of conventional UEs may include cellular phones (e.g., smartphones), laptops, tablets, etc.

[0051] Multiple UEs can operate in full-duplex frequency division duplex (FD-FDD) mode to perform FD-FDD communication, which may involve transmitting and receiving data in parallel. For example, one of the multiple UEs can transmit uplink communication via an uplink carrier and receive downlink communication via a downlink carrier in parallel.

[0052] During FD-FDD communication, the UE can observe a threshold insertion loss. In one example, the UE can observe a threshold link cross-interference between the uplink and downlink carriers used for parallel transmission (e.g., transmission and / or reception) of data, resulting in a threshold insertion loss. To transmit data in the presence of threshold insertion loss, the UE can consume a threshold power. For a RedCap UE, consuming a threshold power for each transmission and each reception may be impractical, as RedCap UEs may be designed for efficient power consumption and may benefit from power-saving techniques. Therefore, RedCap UEs may not be able to operate adequately in FD-FDD mode.

[0053] Furthermore, when configuring parameters for operation in FD-FDD mode, the BS may not have considered the simplification capabilities of the RedCap UE. For example, the BS may not have considered that the RedCap UE may consume more BS resources compared to a regular UE. In one example, because the RedCap UE may include fewer receive antennas, the BS may have to repeat downlink communication transmissions to ensure that the RedCap UE can fully receive downlink communication. Without considering simplification capabilities, the BS can configure parameters to be applied equally to both the regular UE and the RedCap UE. In other words, the BS can handle data communication with the RedCap UE in a similar way to how it handles data communication with a regular UE. Therefore, when communicating with the RedCap UE, the BS may fail to repeat downlink communication transmissions to ensure that the RedCap UE can fully receive downlink communication. As a result, data communication between the base station and the RedCap UE may experience interruptions or stoppages.

[0054] Various versions of the techniques and apparatus described herein can provide configuration and signaling support for HD-FDD operation of RedCap UEs. In some versions, the BS can configure the RedCap UE to operate in HD-FDD mode for HD-FDD communication with the BS. In HD-FDD mode, at a given time, the RedCap UE can transmit uplink communication via an uplink carrier or receive downlink communication via a downlink carrier. Therefore, link cross-interference between uplink and downlink carriers can be avoided, and the power consumption of the RedCap UE can be reduced. In addition, the RedCap UE can avoid including a duplexer used in FD-FDD mode operation, thereby reducing the cost associated with designing the RedCap UE. Furthermore, the BS can configure parameters associated with HD-FDD operation based at least in part on the streamlined capabilities of the RedCap UE, thereby enabling the BS to handle data communication with the RedCap UE in a manner different from how the BS handles data communication with a conventional UE. Therefore, when communicating with a RedCap UE, the BS can sufficiently repeat downlink communication transmissions to ensure the RedCap UE can adequately receive downlink communication, and data communication between the BS and the RedCap UE can continue uninterrupted. This configuration and signaling support enables the BS to communicate effectively with RedCap UEs performing HD-FDD communication as well as with conventional UEs performing FD-FDD communication.

[0055] In some configurations, the RedCap UE may perform the following operations: transmit capability information to a base station, the capability information indicating the RedCap UE's simplified capabilities associated with HD-FDD communication, the indication of simplified capabilities being used to indicate the replacement of the duplexer with switches and filters; receive HD-FDD configuration information from the base station for HD-FDD communication with the base station; and communicate, at least in part, based on the configuration information, by transmitting or receiving data during HD-FDD communication. In some configurations, the configuration information may be mapped to System Information (SI), Radio Resource Control (RRC) messages, Media Access Control Element (MAC CE), or Dynamic Grant (DG) communication.

[0056] Figure 3 is a diagram illustrating example 300 of various configurations according to this disclosure associated with providing configuration and signaling support for HD-FDD operation of a RedCap UE. Figure 3 shows UE 120 and BS 110 communicating data in an LTE network or a 5G / NR network. In some configurations, UE 120 may be a RedCap UE and may have streamlined capabilities compared to a conventional UE. Data communication may include downlink communication from BS 110 to UE 120 and may include uplink communication from UE 120 to BS 110.

[0057] As indicated by reference numeral 310, BS 110 may transmit configuration information before, at the beginning, and / or during data communication, and UE 120 may receive the configuration information. In some configurations, the configuration information may include indications of one or more configuration parameters, for example, for UE 120 to use in configuring data communication. In some configurations, UE 120 may receive the configuration information via system information broadcast to UE by BS 110. In some configurations, UE 120 may receive the configuration information from a device other than BS 110 (e.g., from another base station). In some configurations, UE 120 may receive the configuration information via, for example, a control channel between UE 120 and BS 110 (e.g., a physical downlink control channel (PDCCH)). Configuration information can be transmitted via RRC signaling, MAC signaling (e.g., MAC CE), downlink control information (DCI) signaling, or a combination thereof (e.g., RRC configuration for a set of values ​​for a parameter and DCI indication for a selected value of a parameter).

[0058] As indicated by reference numeral 320, UE 120 can transmit and BS 110 can receive capability information indicating the simplified capabilities of UE 120. In some cases, the capability information may indicate that: UE 120 is designed without a duplexer and / or the duplexer has been replaced by switches and filters; UE 120 includes, for example, fewer receive antennas compared to a conventional UE; UE 120 is subjected to less stringent latency and throughput (e.g., bit rate) requirements compared to a conventional UE; and / or UE 120 is designed for efficient power consumption.

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

[0060] In some configurations, the HD-FDD configuration information may include and / or indicate information associated with operation 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 configurations, the HD-FDD configuration information may indicate index information associated with one or more carriers to be used by UE 120 for HD-FDD communication. The index information may include, for example, a downlink carrier index associated with a downlink carrier configured to carry downlink communication from BS 110 to UE 120. In some configurations, the index information may indicate that the downlink carrier is to be used by UE 120 to receive downlink communication from BS 110. The index information may also include, for example, an uplink carrier index associated with an uplink carrier configured to carry uplink communication from UE 120 to BS 110. In some configurations, index information can indicate that the uplink carrier is to be used by UE 120 to transmit uplink communication to BS 110. In some configurations, the uplink and / or downlink carriers can be semi-statically configured so that the uplink and / or downlink carriers remain available for UE 120 to use within a specific number of time slots or frames. In other words, the availability of a semi-statically configured carrier may not change between time slots or frames.

[0061] In some configurations, the index information may be included in a common information element (e.g., HD-FDD-UL-DL-ConfigurationCommon) received via System Information (SI) communication or MAC CE communication to a group of UEs including UE 120. In some configurations, the index information may be included in a dedicated information element (e.g., HD-FDD-UL-DL-ConfigDedicated) received via a dedicated RRC message, MAC CE communication, or DG communication. In some configurations, UE 120 may receive the dedicated information element at a different time relative to the time when UE 120 can receive the common information element (e.g., individually). In some configurations, UE 120 may receive the dedicated information element at substantially the same time as the common information element (e.g., jointly). When the index information is received via a dedicated RRC message, the index information may be specific to UE 120. Based at least in part on the received index information, UE 120 can transmit uplink communication to BS 110 during HD-FDD communication using an uplink carrier associated with the indicated uplink carrier index. Similarly, based at least in part on the received index information, UE 120 can receive downlink communication from BS 110 during HD-FDD communication using a downlink carrier associated with the indicated downlink carrier index.

[0062] In some configurations, HD-FDD configuration information may include time slot pattern information associated with HD-FDD communication. The time slot pattern information may indicate, for example, one or more types of time slot patterns that indicate one or more time and frequency resource mappings for a specific coherent set of time slots or a specific coherent set of symbols configured for one or more carriers. For example, the time slot pattern information may include a first time slot pattern comprising one or more types of time slot patterns that indicates one or more joint time and frequency resource mappings for a first coherent set of time slots or a first coherent set of symbols configured on a downlink carrier. Similarly, the time slot pattern information may include a second time slot pattern comprising one or more types of time slot patterns that indicates one or more joint time and frequency resource mappings for a second coherent set of time slots or a second coherent set of symbols configured on an uplink carrier. The slot pattern information may also include a third slot pattern, which indicates one or more types of slot patterns that indicate one or more joint time and frequency resource mappings for a third coherent set of slots or a third coherent set of symbols on the uplink carrier, downlink carrier and / or as a protection configuration.

[0063] In some configurations, a specific coherent set of time slots and / or a specific coherent set of symbols may be flexible resources configured for use by UE 120 during HD-FDD communication. In some configurations, common information elements and / or dedicated information elements may include pattern information elements (e.g., HD-FDD-UL-DL-Pattern) for indicating time slot pattern information and / or flexible resources. When included in a common information element, the configuration of flexible resources may be associated with cell-specific (e.g., BS 110-specific) HD-FDD communication. When included in a dedicated information element, the configuration of flexible resources may be UE-specific (e.g., UE 120-specific) HD-FDD communication.

[0064] In some configurations, the slot pattern information may include periodicity information indicating a first periodicity associated with a first slot pattern, a second periodicity associated with a second slot pattern, or a third periodicity associated with a third slot pattern. When UE 120 is able to transmit uplink communication to BS 110 using flexible uplink resources, the period among the first, second, and / or third periodicities may indicate the transmission period and the pattern associated with the occurrence of the transmission period. Furthermore, when UE 120 is able to receive downlink communication from BS 110 using flexible downlink resources, the periodicity may indicate the reception period and the pattern associated with the occurrence of the reception period. At least in part based on the periodicity information, UE 120 may utilize flexible resources for HD-FDD communication according to the periodicity information.

[0065] In some configurations, the slot mode information may include reference digital scheme information, which may indicate the subcarrier spacing type used among a plurality of available subcarrier spacing types. For example, the reference digital scheme information may indicate a first reference digital scheme (e.g., a first subcarrier spacing type) used associated with a first slot mode, a second reference digital scheme (e.g., a second subcarrier spacing type) used associated with a second slot mode, and / or a third reference digital scheme (e.g., a third subcarrier spacing type) used associated with a third slot mode. Based at least in part on the reference digital scheme information, the UE 120 may perform HD-FDD communication using the reference digital scheme.

[0066] In some configurations, the time slot pattern information may include ordering information indicating the order of the first, second, and / or third time slot patterns in the time domain. The ordering information may indicate the order in which one or more of the first, second, or third time slot patterns are ordered in the time domain for use by the UE 120. For example, the time slot patterns may be ordered sequentially in time (such as 1, 3, 2, 1, 3, 2; 3, 1, 2, 1, 3, 2, and other examples) (e.g., where 1 represents the first time slot pattern, 2 represents the second time slot pattern, and 3 represents the third time slot pattern). Based at least in part on the ordering information, the UE 120 may utilize one or more of these time slot patterns for HD-FDD communication.

[0067] In some configurations, the slot pattern information may include monitoring information associated with the UE 120 monitoring the PDCCH timings associated with one or more slot patterns. For example, the monitoring information may indicate a first PDCCH monitoring timing associated with a first slot pattern, a second PDCCH monitoring timing associated with a second slot pattern, and / or a third PDCCH monitoring timing associated with a third slot pattern. Based at least in part on the monitoring information, the UE 120 may monitor the PDCCH timings associated with one or more slot patterns during HD-FDD communication.

[0068] In some configurations, the slot mode information may indicate bandwidth portion (BWP) configuration information associated with the bandwidth portion configured for use in association with one or more slot modes in the slot modes. For example, the BWP configuration information may indicate a first BWP configuration configured for uplink and downlink BWPs used in association with a first slot mode, a second BWP configuration configured for uplink and downlink BWPs used in association with a second slot mode, and / or a third BWP configuration configured for uplink and downlink BWPs used in association with a third slot mode. Based at least in part on the BWP configuration information, the UE 120 may perform HD-FDD communication using the configured uplink BWPs and / or downlink BWPs according to the BWP configuration information.

[0069] In some configurations, time slot pattern information may be included in common information elements received via SI communication or MAC CE communication broadcast or multicast to a UE group including UE 120. In some configurations, time slot pattern information may be included in dedicated information elements received via dedicated RRC messages, MAC CE, or DG communication. In some configurations, dedicated information elements may be received alone or in conjunction with common information elements including time slot pattern information.

[0070] In some configurations, a RedCap UE group including UE 120 may share a specific downlink carrier. In this case, the RedCap UE group may dynamically receive GC-DCI via the specific downlink carrier. GC-DCI may indicate the respective time slot modes to be used by the RedCap UEs included in the group for HD-FDD communication, associated with time slot mode information. In some configurations, GC-DCI may also indicate the respective effective duration associated with the utilization of the respective time slot modes by the RedCap UEs included in the group. Furthermore, GC-DCI may indicate the respective uplink carrier index and / or respective downlink carrier index to be used by the RedCap UEs included in the group for HD-FDD communication. In some configurations, the dynamically indicated respective uplink carrier index and / or respective downlink carrier index may temporarily or semi-persistently overwrite the flexible configuration of the uplink carrier and / or downlink carrier.

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

[0072] In some configurations, the duration of the guard period may be longer than the maximum delay associated with HD-FDD communication. In some configurations, the minimum duration of the guard period (e.g., the duration of two symbols) may be associated with the subcarrier spacing associated with the uplink and / or downlink carriers used for HD-FDD communication. In some configurations, the minimum duration of the guard period (e.g., the duration of two symbols) may be associated with the subcarrier spacing associated with the active uplink BWP and / or active downlink BWP actively used by UE 120 for HD-FDD communication. The subcarrier spacing may be specified in the specification, and UE 120 may determine the subcarrier spacing at least in part based on such a specification. In some configurations, the guard period may be associated with the utilization of flexible resources (e.g., time slots and / or symbols) associated with the time slot mode configured for HD-FDD communication (which is associated with time slot mode information).

[0073] In some configurations, UE 120 may not receive HD-FDD configuration information including uplink carrier index and / or downlink carrier index. Furthermore, UE 120 may not be configured to monitor Dynamic Slot Format Indicator (SFI), which may be signaled via GC-DCI. In this case, UE 120 may rely on UE-specific DCI for link direction determination.

[0074] In some configurations, UE 120 can operate in FD-FDD mode to communicate with BS 110 via FD-FDD. In this case, UE 120 can be configured to switch to operating in HD-FDD mode to communicate with BS 110 via HD-FDD. In some configurations, when UE 120 needs to communicate less than a threshold amount of data with BS 110, UE 120 can switch from operating in FD-FDD mode to operating in HD-FDD mode.

[0075] In some configurations, BS 110 can support UEs operating in HD-FDD mode and UEs operating in FD-FDD mode. In this case, BS 110 can 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 configurations, UE 120 can use HD-FDD power control parameters to transmit uplink communication to BS 110 during HD-FDD communication. Uplink communication may include communication transmitted via the Physical Random Access Channel (PRACH), Physical Uplink Control Channel (PUCCH), Physical Uplink Common Channel (PUSCH), and / or Sound Reference Signal (SRS).

[0076] When performing HD-FDD communication, the HD-FDD power control parameters may be at least partially based on the inherent uplink transmission characteristics of the UE 120. Such transmission characteristics may include reduced insertion loss, improved power efficiency, reduced peak transmission power, and / or improved reference sensitivity. In some cases, the transmission characteristics may be indicated by a measure (e.g., noise factor) of the degradation of the signal-to-noise ratio imparted by the receiving and / or transmitting circuitry of the UE 120. In some cases, compared to a UE performing FD-FDD communication (RedCap UE or conventional UE), the UE 120 may have improved transmission characteristics when performing HD-FDD communication, at least partially based on the reduced SNR degradation imparted by the receiving and / or transmitting circuitry included in the UE 120. In some cases, compared to a UE performing FD-FDD communication, the receiving and / or transmitting circuitry included in the UE 120 may introduce reduced noise to the SNR, at least partially based on avoiding link cross-interference.

[0077] In some configurations, BS 110 can transmit HD-FDD power control parameters, and UE 120 can receive HD-FDD power control parameters, which include offsets for receiving target power, offsets for the maximum output power configured by the UE, and / or scaling factors or offsets for the reference signal power in path loss estimation. HD-FDD power control parameters may also include enhanced granularity, range, and / or power control adjustment states associated with transmit power control commands and transmit power increases. UE 120 can determine the transmission power used to transmit uplink communication to BS 110 based at least in part on a formula specified in the specification, which relates to the HD-FDD power control parameters. In some configurations, the HD-FDD power control parameters can assist in controlling the transmission power utilized by UE 120, thereby reducing power consumption associated with transmitting uplink communication.

[0078] In some configurations, HD-FDD configuration information may include measurement and reporting parameters associated with the UE 120 performing Radio Resource Management (RRM), Radio Link Monitoring (RLM), and / or Cellular Location and Beam Management (BM) procedures during HD-FDD communication. The RRM procedure may be associated with the UE 120 performing RRM measurements associated with cell selection, cell reselection, and / or handover procedures. The RLM procedure may be associated with the UE 120 monitoring downlink carriers (e.g., PDCCH) to assist in determining metrics related to the quality of downlink communication received via the downlink carrier. The BM procedure may be associated with the UE 120 determining, at least in part, the transmit beam for transmitting uplink communication and / or the receive beam for receiving downlink communication based on the UE 120's location within the cell associated with the BS 110, wherein the transmit beam enables the BS 110 to adequately receive uplink communication and / or the receive beam enables the UE 120 to adequately receive downlink communication.

[0079] In some configurations, the measurement and reporting parameters may be at least partially based on the streamlined capabilities of UE 120 operating in HD-FDD mode. For example, UE 120 may have an enhanced reference sensitivity level, at least partially based on avoiding link cross-interference. Based at least partially on the enhanced reference sensitivity level, the measurement and reporting parameters may include a specific accuracy level associated with UE 120 performing RRM, RLM, and / or BM procedures. Furthermore, based at least partially on the specific accuracy level, the measurement and reporting parameters may include extended periodicity associated with the frequency utilized by UE 120 to perform the RRM, RLM, and / or BM procedures. In some configurations, the measurement and reporting parameters may be at least partially based on time slot mode configuration (e.g., as described above). In some configurations, the measurement and reporting parameters may be at least partially based on BWP configuration. In some configurations, the measurement and reporting parameters can indicate a list of measurement objects, reporting configurations, measurement identifiers, quantity configurations, or measurement gap configurations associated with the UE 120 performing the RRM, RLM, and / or BM procedures. Measurement objects can indicate the parameters to be measured and reported by the UE 120, reporting configurations can indicate the configurations associated with the measurement and reporting parameters, quantity configurations can indicate the number of parameters to be measured and reported, and measurement gap configurations can indicate the duration and / or periodicity associated with the measurement and reporting parameters.

[0080] In some configurations, UE 120 and / or BS 110 can handle UE handover to continue HD-FDD communication with, for example, a neighboring BS associated with a neighboring cell. In this case, BS 110 can indicate whether the neighboring BS supports the UE operating in HD-FDD mode. When BS 110 indicates that the neighboring BS does not support the UE operating in HD-FDD mode, UE 120 can avoid unnecessarily involving the neighboring BS to perform RRM, RLM, and / or BM procedures.

[0081] By utilizing the parameters for half-duplex operation of the RedCap UE discussed herein, link cross-interference between the uplink and downlink carriers can be avoided, and the power consumption of the RedCap UE can be reduced. Furthermore, the RedCap UE can avoid the need for a duplexer used in FD-FDD mode operation, thereby reducing the costs associated with designing the RedCap UE. In addition, when communicating with the RedCap UE, the BS can fully repeat downlink communication transmissions so that the RedCap UE can fully receive downlink communication, and data communication between the BS and the RedCap UE can continue uninterrupted.

[0082] As noted above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0083] Figure 4 is a diagram illustrating an example process 400 performed, for example, by a Reduced Capability User Equipment (RCA) according to various forms of this disclosure. Example process 400 is an example in which a RCA (e.g., RCA 120) performs operations associated with providing configuration and signaling support for HD-FDD operation for RedCap UEs.

[0084] As shown in FIG4, in some embodiments, process 400 may include transmitting capability information to a base station, the capability information indicating the simplified capabilities of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication (block 410). For example, the RedCap UE (e.g., using the transmitter component 604 depicted in FIG6) may transmit capability information to a base station, the capability information indicating the simplified capabilities of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication, as described above.

[0085] As further shown in FIG4, in some configurations, process 400 may include: receiving HD-FDD configuration information from a base station for HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on capability information (block 420). For example, a RedCap UE (e.g., using the receiving component 602 depicted in FIG6) may receive HD-FDD configuration information from a base station for HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on capability information, as described above.

[0086] As further shown in FIG4, in some cases, process 400 may include: communicating by transmitting or receiving data during HD-FDD communication, at least in part based on HD-FDD configuration information (block 430). For example, a RedCap UE (e.g., using the transmit component 604 and / or receive component 602 depicted in FIG6) may communicate by transmitting or receiving data during HD-FDD communication, at least in part based on HD-FDD configuration information, as described above.

[0087] Process 400 may include additional patterns, such as any single pattern or any combination thereof described below and / or in conjunction with one or more other patterns described elsewhere herein.

[0088] In the first state, 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: a downlink carrier index associated with a downlink carrier from one or more carriers, the downlink carrier being configured to carry downlink transmission from the base station to the RedCap UE during HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more carriers, the uplink carrier being configured to carry uplink transmission from the RedCap UE to the base station during HD-FDD communication.

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

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

[0091] In the fourth state (either alone or in combination with one or more states from the first to the third state), the index information is included in a dedicated information element received via a dedicated RRC message, MAC CE or DG communication, the dedicated information element being received alone or in conjunction with a common information element that includes the index information.

[0092] In the fifth state sample (alone or in combination with one or more of the first to fourth state samples), the HD-FDD configuration information includes time slot pattern information, which includes one or more of the following: a first time slot pattern, which includes one or more types of time slot patterns indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on a downlink carrier; a second time slot pattern, which includes one or more types of time slot patterns indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on an uplink carrier; or a third time slot pattern, which includes one or more types of time slot patterns indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on an uplink carrier, configured on a downlink carrier, or configured as a guard period.

[0093] In the sixth state sample (either alone or in combination with one or more of the first to fifth state samples), the slot pattern 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 third periodicity associated with the third slot pattern; reference digit scheme information indicating a first reference digit scheme associated with the first slot pattern, a second reference digit scheme associated with the second slot pattern, or a third reference digit scheme associated with the third slot pattern; and sequencing information indicating the first slot pattern, The arrangement of the second or third time slot mode in the time domain; monitoring information indicating the first PDCCH monitoring timing associated with the first time slot mode, the second PDCCH monitoring timing associated with the second time slot mode, or the third PDCCH monitoring timing associated with the third time slot mode; or BWP configuration information indicating the first BWP configuration of the uplink and downlink BWP associated with the first time slot mode, the second BWP configuration of the uplink and downlink BWP associated with the second time slot mode, or the third BWP configuration of the uplink and downlink BWP associated with the third time slot mode.

[0094] In the seventh state sample (either alone or in combination with one or more of the first to sixth state samples), the time slot pattern information is included in a common information element received via SI communication or MAC CE communication broadcast or multicast to a UE group including the RedCap UE.

[0095] In the eighth state (either alone or in combination with one or more states from the first to the seventh state), the slot pattern information is included in a dedicated information element received via a dedicated RRC message, MAC CE or DG communication, the dedicated information element being received alone or in conjunction with a common information element that includes the slot pattern information.

[0096] In the ninth state sample (either alone or in combination with one or more of the first to eighth state samples), process 400 includes: receiving a GC-DCI via a downlink carrier shared by the RedCap UE group including the RedCap UE, the GC-DCI indicating the respective uplink carrier index and downlink carrier index to be used by these RedCap UEs.

[0097] In the tenth state sample (either alone or in combination with one or more of the first to ninth state samples), process 400 includes: receiving a GC-DCI via a downlink carrier shared by the RedCap UE group including the RedCap UE, the GC-DCI indicating the individual time slot modes from a plurality of time slot modes to be used by the RedCap UE for HD-FDD communication and the effective duration associated with the use of the individual time slot modes.

[0098] In the eleventh state (either alone or in combination with one or more states from the first to the tenth state), the HD-FDD configuration information indicates the protection period associated with switching from using a downlink carrier to using an uplink carrier, or the protection period associated with switching from using an uplink carrier to using a downlink carrier.

[0099] In the twelfth state (either alone or in combination with one or more states from the first to the eleventh state), the HD-FDD configuration information indicates a protection period associated with a switch from using a downlink carrier to using an uplink carrier, or a protection period associated with a switch from using an uplink carrier to using a downlink carrier, the duration of which is related to the subcarrier interval associated with the active uplink BWP or the active downlink BWP that is actively used for HD-FDD communication.

[0100] In the thirteenth state (either alone or in combination with one or more states from the first to the twelfth state), the HD-FDD configuration information indicates a protection period associated with a switch from using a downlink carrier to using an uplink carrier, or a protection period associated with a switch from using an uplink carrier to using a downlink carrier, which is associated with a flexible time slot or flexible symbol associated with the time slot mode configured for HD-FDD communication.

[0101] In the fourteenth state (either alone or in combination with one or more states from the first to the thirteenth state), the HD-FDD configuration information includes power control parameters to be used by the RedCap UE to transmit uplink communication during HD-FDD communication.

[0102] In the fifteenth state sample (either alone or in combination with one or more of the first to fourteenth state samples), the HD-FDD configuration information includes power control parameters to be used by the RedCap UE for the transmission of PRACH, PUCCH, PUSCH and / or SRS during HD-FDD communication. These power control parameters are at least in part based on reduced insertion loss, improved power efficiency, improved UE receiver sensitivity or reduced peak transmission power associated with the RedCap UE during HD-FDD communication.

[0103] In the sixteenth state sample (either alone or in combination with one or more of the first to fifteenth state samples), the HD-FDD configuration information includes power control parameters to be used by the RedCap UE during HD-FDD communication. These power control parameters include offsets for receiving target power, offsets for the maximum output power configured by the UE, scaling factors or offsets for the reference signal power in path loss estimation, or enhancement granularity, range, and power control adjustment status associated with transmit power control commands and transmit power increases.

[0104] In the seventeenth state sample (either alone or in combination with one or more of the first to sixteenth state samples), the HD-FDD configuration information includes measurement and reporting parameters associated with the RRM, RLM, or BM procedures to be performed by the RedCap UE during HD-FDD communication. These measurement and reporting parameters are based at least in part on the time slot mode configuration, bandwidth portion (BWP) configuration, reduced insertion loss, improved power efficiency, or improved UE receiver sensitivity associated with the RedCap UE during HD-FDD communication.

[0105] In the eighteenth state sample (either alone or in combination with one or more of the first to seventeenth state samples), the HD-FDD configuration information includes measurement and reporting parameters associated with the RRM, RLM, or BM procedures to be performed by the RedCap UE during HD-FDD communication. These measurement and reporting parameters indicate a list of measurement objects, reporting configurations, measurement identifiers, quantity configurations, or measurement gap configurations associated with performing the RRM, RLM, or BM procedures.

[0106] In the nineteenth state sample (either alone or in combination with one or more of the first to eighteenth state samples), the HD-FDD configuration information includes measurement and reporting parameters associated with the RRM measurements to be performed by the RedCap UE in conjunction with the cell selection process, cell reselection process, or handover process.

[0107] In the twentieth state (either alone or in combination with one or more states from the first to the nineteenth state), the HD-FDD configuration information is received via SI, RRC messages, MAC CE or DG communication.

[0108] In the twenty-first state (either alone or in combination with one or more states from the first to the twentieth state), the capability information indicates that the duplexer of the RedCap UE is replaced by a switch and a filter.

[0109] Although Figure 4 shows an example block of process 400, in some versions, process 400 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 4. Alternatively, two or more blocks of process 400 may be performed in parallel.

[0110] Figure 5 is a diagram illustrating, for example, an example process 500 performed by a base station according to various states of the present disclosure. Example process 500 is an example in which a base station (e.g., BS 110) performs operations associated with providing configuration and signaling support for HD-FDD operation of RedCap UE.

[0111] As shown in FIG5, in some configurations, process 500 may include: receiving capability information from a RedCap UE, the capability information indicating the RedCap UE's simplified capabilities associated with performing half-duplex frequency division duplex (HD-FDD) communication (block 510). For example, a base station (e.g., using the receiver component 702 depicted in FIG7) may receive capability information from a simplified capability user equipment (RedCap UE), the capability information indicating the RedCap UE's simplified capabilities associated with performing half-duplex frequency division duplex (HD-FDD) communication, as described above.

[0112] As further shown in FIG5, in some configurations, process 500 may include: transmitting HD-FDD configuration information for HD-FDD communication with a base station to the RedCap UE, the HD-FDD configuration information being at least partially based on capability information (block 520). For example, the base station (e.g., using the transmit component 704 depicted in FIG7) may transmit HD-FDD configuration information for HD-FDD communication with the base station to the RedCap UE, the HD-FDD configuration information being at least partially based on capability information, as described above.

[0113] As further shown in FIG5, in some configurations, process 500 may include: communicating by transmitting or receiving data during HD-FDD communication, at least in part based on HD-FDD configuration information (block 530). For example, a base station (e.g., using the transmitting component 704 and / or receiving component 702 depicted in FIG7) may communicate by transmitting or receiving data during HD-FDD communication, at least in part based on HD-FDD configuration information, as described above.

[0114] Process 500 may include additional patterns, such as any single pattern or any combination thereof described below and / or in conjunction with one or more other patterns described elsewhere herein.

[0115] Although Figure 5 shows an example block of process 500, in some versions, process 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 5. Alternatively, two or more blocks of process 500 may be performed in parallel.

[0116] Figure 6 is a block diagram of an example device 600 for wireless communication. Device 600 may be a RedCap UE (e.g., UE 120), or a RedCap UE may include device 600. In some embodiments, device 600 includes a receiving component 602 and a transmitting component 604, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 600 may use the receiving component 602 and the transmitting component 604 to communicate with another device 606 (e.g., a UE, a base station, or another wireless communication device). As further shown, device 600 may include a determining component 608 and one or more of the other components in other examples.

[0117] In some embodiments, appliance 600 may be configured to perform one or more operations described herein in conjunction with FIG. 3. Alternatively, appliance 600 may be configured to perform one or more processes described herein, such as process 400 of FIG. 4. In some embodiments, 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 conjunction with FIG. 2. Alternatively, one or more components shown in FIG. 6 may be implemented within one or more components described above in conjunction with FIG. 2. Alternatively, one or more components in the set of components may be implemented at least partially 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 that component.

[0118] Receiver 602 may receive communications from appliance 606, such as reference signals, control information, data communications, or combinations thereof. Receiver 602 may provide the received communications to one or more other components of appliance 600. In some embodiments, receiver 602 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of appliance 606. In some embodiments, receiver 602 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the RedCap UE described above in conjunction with FIG2.

[0119] Transmitter 604 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 606. In some embodiments, one or more other components of device 606 can generate communications and provide the generated communications to transmitter 604 for transmission to device 606. In some embodiments, transmitter 606 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples), and can transmit the processed signals to device 606. In some embodiments, transmitter 604 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof of the RedCap UE described above in conjunction with FIG. 2. In some embodiments, transmitter 604 may be co-located with receiver 602 in a transceiver.

[0120] Transmitter 604 can transmit capability information to the base station, indicating the simplified capabilities of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication. Receiver 602 can receive HD-FDD configuration information from the base station for HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information. Receiver 602 and / or transmitter 604 can communicate by transmitting or receiving data during HD-FDD communication, based at least partially on the HD-FDD configuration information.

[0121] The receiving component 602 can receive GC-DCI via a downlink carrier shared by the RedCap UE group (including RedCap UEs), the GC-DCI indicating the respective uplink carrier index and downlink carrier index to be used by the RedCap UE.

[0122] The receiving component 602 can receive a GC-DCI via a downlink carrier shared by the RedCap UE group (including the RedCap UE), the GC-DCI indicating the individual time slot mode to be used by the RedCap UE for HD-FDD communication from a plurality of time slot modes and the effective duration associated with the use of the individual time slot mode.

[0123] The decision component 608 can determine, for example, the information to be included in the capability information transmitted to the base station. Furthermore, the decision component 608 can determine the information received in the HD-FDD configuration information. Additionally, the decision component 608 can determine the data to be transmitted during HD-FDD communication.

[0124] The number and arrangement of components shown in Figure 6 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 6. Furthermore, two or more components shown in Figure 6 may be implemented within a single component, or a single component shown in Figure 6 may be implemented as multiple distributed components. Alternatively or concurrently, one or more groups of components shown in Figure 6 may perform one or more functions described as being performed by another group of components shown in Figure 6.

[0125] Figure 7 is a block diagram of an example device 700 for wireless communication. Device 700 may be a base station (e.g., BS 110), or a base station may include device 700. In some embodiments, device 700 includes a receiving component 702 and a transmitting component 704, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 700 can use the receiving component 702 and the transmitting component 704 to communicate with another device 706 (such as a UE, a base station, or another wireless communication device). As further shown, device 700 may include a determining component 708 and one or more of the other components in other examples.

[0126] In some embodiments, appliance 700 may be configured to perform one or more operations described herein in conjunction with FIG. 3. Alternatively, appliance 700 may be configured to perform one or more processes described herein, such as process 500 of FIG. 5. In some embodiments, 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 conjunction with FIG. 2. Alternatively, one or more components shown in FIG. 7 may be implemented within one or more components described above in conjunction with FIG. 2. Alternatively, one or more components of a set of components may be implemented at least partially 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.

[0127] Receiver 702 may receive communications from appliance 706, such as reference signals, control information, data communications, or combinations thereof. Receiver 702 may provide the received communications to one or more other components of appliance 700. In some embodiments, receiver 702 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of appliance 706. In some embodiments, receiver 702 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof from the base station described above in conjunction with FIG2.

[0128] Transmitting component 704 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 706. In some embodiments, one or more other components of device 706 can generate communications and provide the generated communications to transmitting component 704 for transmission to device 706. In some embodiments, transmitting component 704 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples), and can transmit the processed signals to device 706. In some embodiments, transmitting component 704 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof from the base station described above in conjunction with FIG. 2. In some embodiments, transmitting component 704 may be co-located with receiving component 702 in a transceiver.

[0129] The receiving component 702 can receive capability information from the RedCap UE, which indicates the RedCap UE's simplified capabilities associated with performing half-duplex frequency division duplex (HD-FDD) communication. The transmitting component 704 can transmit HD-FDD configuration information to the RedCap UE for HD-FDD communication with the base station, which is at least partially based on the capability information. The receiving component 702 and / or the transmitting component 704 can communicate by transmitting or receiving data during HD-FDD communication, based at least partially on the HD-FDD configuration information.

[0130] The decision component 708 can determine, for example, the information included in the capability information received by the base station. Furthermore, the decision component 708 can determine the information to be transmitted in the HD-FDD configuration information. Additionally, the decision component 708 can determine the data to be transmitted during HD-FDD communication.

[0131] The number and arrangement of components shown in Figure 7 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 7. Furthermore, two or more components shown in Figure 7 may be implemented within a single component, or a single component shown in Figure 7 may be implemented as multiple distributed components. Alternatively or concurrently, one or more groups of components shown in Figure 7 may perform one or more functions described as being performed by another group of components shown in Figure 7.

[0132] The following provides an overview of the various forms of this disclosure:

[0133] State 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 the reduced capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; receiving from the base station HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and performing communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information.

[0134] State 2: The method of State 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 one or more carriers, the downlink carrier being configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more carriers, the uplink carrier being configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication.

[0135] State 3: The method of any one of States 1-2, wherein the one or more carriers are semi-statically configured for the HD-FDD communication.

[0136] State 4: The method of any one of States 1-3, wherein the index information is included in a common information element received via System Information (SI) communication or Media Access Control Element (MAC CE) communication to a UE group including the RedCap UE.

[0137] State 5: The method of any one of States 1-4, wherein the index information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, a media access control element (MAC CE) or dynamic permission (DG) communication, the dedicated information element being received alone or in conjunction with a common information element that includes the index information.

[0138] State 6: The method of any one of States 1-5, wherein the HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, the first time slot mode including one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier; a second time slot mode, the second time slot mode including one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier; or a third time slot mode, the third time slot mode including one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

[0139] State 7: The method of any one of States 1-6, wherein the slot pattern information includes one or more of the following: periodicity information, which indicates 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 third slot pattern; reference digit scheme information, which indicates a first reference digit scheme associated with the first slot pattern, a second reference digit scheme associated with the second slot pattern, or a third reference digit scheme associated with the third slot pattern; and sorting information, which indicates the first slot pattern, the second slot pattern, or the third slot pattern. The time-domain arrangement of the three time slot modes; monitoring information indicating the first PDCCH monitoring timing associated with the first time slot mode, the second PDCCH monitoring timing associated with the second time slot mode, or the third PDCCH monitoring timing associated with the third time slot mode; or bandwidth portion (BWP) configuration information indicating the first BWP configuration of the uplink BWP and downlink BWP associated with the first time slot mode, the second BWP configuration of the uplink BWP and downlink BWP associated with the second time slot mode, or the third BWP configuration of the uplink BWP and downlink BWP associated with the third time slot mode.

[0140] State 8: The method of any one of States 1-7, wherein the slot pattern information is included in a common information element received via System Information (SI) communication or Media Access Control Element (MAC CE) communication to a UE group including the RedCap UE.

[0141] State 9: The method of any one of States 1-8, wherein the slot pattern information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, MAC CE or dynamic permission (DG) communication, the dedicated information element being received alone or in conjunction with a common information element that includes the slot pattern information.

[0142] State 10: The method of any one of States 1-9 further includes: via a downlink carrier reception group common downlink control information (GC-DCI) shared by the RedCap UE group including the RedCap UE, the GC-DCI indicating the respective uplink carrier index and downlink carrier index to be used by the RedCap UE.

[0143] State 11: The method of any one of States 1-10 further includes: via a downlink carrier receive group common downlink control information (GC-DCI) shared by the RedCap UE group including the RedCap UE, the GC-DCI indicating each time slot mode from a plurality of time slot modes to be used by the RedCap UE for the HD-FDD communication and the effective duration associated with the use of the respective time slot mode.

[0144] State 12: The method of any one of States 1-11, wherein the HD-FDD configuration information indicates a protection period associated with switching from using a downlink carrier to using an uplink carrier, or a protection period associated with switching from using an uplink carrier to using a downlink carrier.

[0145] State 13: The method of any one of States 1-12, wherein the HD-FDD configuration information indicates a protection period associated with switching from using a downlink carrier to using an uplink carrier, or a protection period associated with switching from using an uplink carrier to using a downlink carrier, the duration of which is related to the subcarrier spacing associated with the active uplink BWP or the active downlink BWP used for the HD-FDD communication.

[0146] State 14: The method of any one of States 1-13, wherein the HD-FDD configuration information indicates a protection period associated with switching from using a downlink carrier to using an uplink carrier, or a protection period associated with switching from using an uplink carrier to using a downlink carrier, the protection period being associated with a flexible time slot or flexible symbol associated with the time slot mode configured for the HD-FDD communication.

[0147] State 15: The method of any one of States 1-14, wherein the HD-FDD configuration information includes power control parameters to be used by the RedCap UE to transmit uplink communication during the HD-FDD communication.

[0148] State 16: The method of any one of States 1-15, wherein the HD-FDD configuration information includes power control parameters to be used by the RedCap UE for transmission of the Physical Random Access Channel (PRACH), Physical Uplink Control Channel (PUCCH), Physical Uplink Common Channel (PUSCH), and / or Sound Reference Signal (SRS) during the HD-FDD communication, the power control parameters being at least in part based on reduced insertion loss, improved power efficiency, improved UE receiver sensitivity, or reduced peak transmission power associated with the RedCap UE during the HD-FDD communication.

[0149] State 17: The method of any one of States 1-16, wherein the HD-FDD configuration information includes power control parameters to be used by the RedCap UE during the HD-FDD communication, the power control parameters including an offset for receiving target power, an offset for the maximum output power configured by the UE, a scaling factor or offset for the reference signal power in path loss estimation, or an enhancement granularity, range, and power control adjustment state associated with transmit power control commands and transmit power increases.

[0150] State 18: The method of any one of States 1-17, wherein the HD-FDD configuration information includes measurement and reporting parameters associated with a radio resource management (RRM) process, radio link monitoring (RLM) process, or cellular positioning and beam management (BM process) process to be performed by the RedCap UE during the HD-FDD communication, the measurement and reporting parameters being at least in part based on the time slot mode configuration, bandwidth portion (BWP) configuration, reduced insertion loss, improved power efficiency, or improved UE receiver sensitivity associated with the RedCap UE during the HD-FDD communication.

[0151] State 19: The method of any one of States 1-18, wherein the HD-FDD configuration information includes measurement and reporting parameters associated with the radio resource management (RRM) process, radio link monitoring (RLM) process, or cellular positioning and beam management (BM) process to be performed by the RedCap UE during the HD-FDD communication, the measurement and reporting parameters indicating a list of measurement objects, reporting configurations, measurement identifiers, quantity configurations, or measurement gap configurations associated with performing the RRM process, the RLM process, or the BM process.

[0152] State 20: The method of any one of States 1-19, 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 the cell selection process, cell reselection process or handover process.

[0153] State 21: The method of any one of States 1-20, wherein the HD-FDD configuration information is received via System Information (SI), Radio Resource Control (RRC) message, Media Access Control Element (MAC CE) or Dynamic Grant (DG) communication.

[0154] State 22: The method of any one of States 1-21, wherein the capability information indicates that the duplexer of the RedCap UE is replaced by a switch and a filter.

[0155] Style 23: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in one or more of the styles 1-22.

[0156] Style 24: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform a method as described in one or more of the styles 1-22.

[0157] Style 25: An apparatus for wireless communication, comprising at least one component for performing a method of one or more of the styles 1-22.

[0158] Format 26: A non-transitory computer-readable medium storing code for wireless communication, the code containing instructions executable by a processor to perform methods of one or more formats as in Formats 1-22.

[0159] State 27: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions containing one or more instructions which, when executed by one or more processors of a device, cause the device to perform a method of one or more states as in states 1-22.

[0160] Sample 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 the reduced capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; transmitting to the RedCap UE HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and performing communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information.

[0161] State 29: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method as in State 28.

[0162] State 30: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method as described in State 28.

[0163] Style 31: An apparatus for wireless communication, comprising at least one component for performing the method as described in style 28.

[0164] Format 32: A non-transitory computer-readable medium storing code for wireless communication, the code containing instructions executable by a processor to perform the method as described in Format 28.

[0165] State 33: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions containing one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method as described in State 28.

[0166] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the various forms to the precise forms disclosed. Modifications and variations may be made in accordance with the foregoing disclosure, or modifications and variations may be derived from practice with the various forms.

[0167] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or any other name, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, and other examples. As used herein, processors are implemented using hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented using various forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not a limitation on the variety. Therefore, this paper describes the operation and behavior of the system and / or method without referencing any specific software code. It is to be understood that the software and hardware may be designed to implement the system and / or method based at least in part on the description herein.

[0168] As used herein, depending on the context, satisfying a threshold can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0169] Even if a specific combination of features is described in the claims and / or disclosed in the specification, such combinations are not intended to limit the disclosure of each variant. In fact, many features can be combined in a manner not specifically described in the claims and / or disclosed in the specification. Although each subsidiary claim listed below may depend directly on only one claim, the disclosure of each variant includes a combination of each subsidiary claim with every other claim in the set of claims. As used herein, the phrase “at least one of” in the 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 cover a, b, c, ab, ac, bc, and abc, and any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0170] None of the elements, actions, or instructions used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items referenced in conjunction with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” Where only one item is anticipated, 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, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or” unless otherwise expressly stated (e.g., if used in conjunction with “any” or “only one of”). [Simplified Explanation of the Diagram]

[0015] In order to fully understand the above-described features of this disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various embodiments (some of which are shown in the accompanying drawings). However, it should be noted that the accompanying drawings only show certain typical embodiments of this disclosure and are therefore not intended to limit the scope of this disclosure, as other equally valid embodiments are permissible. The same symbols in different drawings can identify the same or similar elements.

[0016] Figure 1 is a diagram illustrating examples of various types of wireless networks according to the present disclosure.

[0017] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network of various forms according to the present disclosure.

[0018] Figure 3 is a diagram illustrating examples of configuration and signaling support associated with various forms of the present disclosure for providing half-duplex frequency division duplex (HD-FDD) operation for RedCap User Equipment (RedCap UE).

[0019] Figures 4-5 are illustrations of example processes associated with providing configuration and signaling support for HD-FDD operation of RedCap UE according to various states of this disclosure.

[0020] Figures 6-7 are illustrations of example devices associated with providing configuration and signaling support for HD-FDD operation of RedCap UEs according to various states of this disclosure.

Claims

1. A simplified capability user equipment (RedCap UE) for wireless communication, comprising: a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: transmit capability information to a base station, the capability information indicating the simplified capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; receive from the base station HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and perform communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

2. As in request item 1's RedCap UE, where, The one or more carriers are semi-statically configured for this HD-FDD communication.

3. As in request item 1, RedCap UE, where, The index information is included in a common information element received via System Information (SI) communications or Media Access Control Element (MAC CE) communications to a group of UEs that includes the RedCap UE.

4. As in request item 1, RedCap UE, where, The index information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, a media access control element (MAC CE), or a dynamic permission (DG) communication, which is received alone or in conjunction with a common information element that includes the index information.

5. As in request item 1, RedCap UE, where, The slot pattern 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 third periodicity associated with the third slot pattern; reference digit scheme information, indicating a first reference digit scheme associated with the first slot pattern, a second reference digit scheme associated with the second slot pattern, or a third reference digit scheme associated with the third slot pattern; and sorting information, indicating the arrangement of the first slot pattern, the second slot pattern, or the third slot pattern in the time domain. Monitoring information, which indicates the first PDCCH monitoring timing associated with the first time slot mode, the second PDCCH monitoring timing associated with the second time slot mode, or the third PDCCH monitoring timing associated with the third time slot mode; or bandwidth portion (BWP) configuration information, which indicates the first BWP configuration of the uplink BWP and downlink BWP associated with the first time slot mode, the second BWP configuration of the uplink BWP and downlink BWP associated with the second time slot mode, or the third BWP configuration of the uplink BWP and downlink BWP associated with the third time slot mode.

6. As in request item 1's RedCap UE, where, The slot pattern information is included in a common information element received via System Information (SI) communication or Media Access Control Element (MAC CE) communication to a group of UEs including the RedCap UE.

7. As in request item 1's RedCap UE, where, The slot pattern information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, MAC CE, or dynamic permission (DG) communication, which is received either alone or in conjunction with a common information element that includes the slot pattern information.

8. As in request item 1, RedCap UE, where, The one or more processors are further configured to: receive group common downlink control information (GC-DCI) shared by the RedCap UE group including the RedCap UE, the GC-DCI indicating the respective uplink carrier index and downlink carrier index to be used by the RedCap UE.

9. As in request item 1's RedCap UE, where, The one or more processors are further configured to: via a group common downlink control information (GC-DCI) shared by the RedCap UE group including the RedCap UE, the GC-DCI indicating the individual time slot modes from a plurality of time slot modes to be used by the RedCap UE for the HD-FDD communication and the effective duration associated with the use of the individual time slot modes.

10. As in request item 1's RedCap UE, where, The HD-FDD configuration information indicates the protection period associated with switching from using a downlink carrier to using an uplink carrier, or the protection period associated with switching from using an uplink carrier to using a downlink carrier.

11. As in request item 1's RedCap UE, where, The HD-FDD configuration information indicates a protection period associated with switching from using a downlink carrier to using an uplink carrier, or a protection period associated with switching from using an uplink carrier to using a downlink carrier. The duration of this protection period 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.

12. As in request item 1's RedCap UE, where, The HD-FDD configuration information indicates a protection period associated with a switch from using a downlink carrier to using an uplink carrier, or a protection period associated with a switch from using an uplink carrier to using a downlink carrier, which is associated with a flexible time slot or flexible symbol associated with the time slot mode configured for the HD-FDD communication.

13. As in request item 1's RedCap UE, where, The HD-FDD configuration information includes power control parameters that the RedCap UE will use to transmit uplink communication during the HD-FDD communication.

14. As in request item 1's RedCap UE, where, The HD-FDD configuration information includes power control parameters to be used by the RedCap UE for transmission of the Physical Random Access Channel (PRACH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), and / or Sound Reference Signal (SRS) during the HD-FDD communication. These power control parameters are at least in part based on reduced insertion loss, improved power efficiency, improved UE receiver sensitivity, or reduced peak transmission power associated with the RedCap UE during the HD-FDD communication.

15. As in request item 1's RedCap UE, where, The HD-FDD configuration information includes power control parameters to be used by the RedCap UE during HD-FDD communication. These power control parameters include offsets for target power reception, offsets for maximum output power configured by the UE, scaling factors or offsets for reference signal power in path loss estimation, or enhancement granularity, range, and power control adjustment status associated with transmit power control commands and transmit power increases.

16. As in request item 1's RedCap UE, where, The HD-FDD configuration information includes measurement and reporting parameters associated with the radio resource management (RRM), radio link monitoring (RLM), or cellular positioning and beam management (BM) procedures to be performed by the RedCap UE during the HD-FDD communication. These measurement and reporting parameters are at least in part based on the time slot mode configuration, bandwidth portion (BWP) configuration, reduced insertion loss, improved power efficiency, or improved UE receiver sensitivity associated with the RedCap UE during the HD-FDD communication.

17. As in request item 1's RedCap UE, where, The HD-FDD configuration information includes measurement and reporting parameters associated with the Radio Resource Management (RRM), Radio Link Monitoring (RLM), or Cellular Location and Beam Management (BM) procedures to be performed by the RedCap UE during HD-FDD communication. These measurement and reporting parameters indicate a list of measurement objects, reporting configurations, measurement identifiers, quantity configurations, or measurement gap configurations associated with performing the RRM, RLM, or BM procedures.

18. As in request item 1's RedCap UE, where, The HD-FDD configuration information includes measurement and reporting parameters associated with RRM measurements to be performed by the RedCap UE in conjunction with the cell selection process, cell reselection process, or handover process.

19. As in request item 1's RedCap UE, where, The HD-FDD configuration information is received via System Information (SI), Radio Resource Control (RRC) messages, Media Access Control Element (MAC CE), or Dynamic Grant (DG) communications.

20. As in request item 1's RedCap UE, where, This capability information indicates that the duplexer of the RedCap UE should be replaced by a switch and filter.

21. 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 the reduced capabilities of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; receiving from the base station HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and performing communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

22. As in request item 21, wherein, The one or more carriers are semi-statically configured for this HD-FDD communication.

23. As in request item 21, wherein, The index information is included in a common information element received via System Information (SI) communications or Media Access Control Element (MAC CE) communications to a group of UEs that includes the RedCap UE.

24. As in request item 21, wherein, The index information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, a media access control element (MAC CE), or a dynamic permission (DG) communication, which is received alone or in conjunction with a common information element that includes the index information.

25. As in request item 21, wherein, The slot pattern 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 third periodicity associated with the third slot pattern; reference digit scheme information, indicating a first reference digit scheme associated with the first slot pattern, a second reference digit scheme associated with the second slot pattern, or a third reference digit scheme associated with the third slot pattern; and sorting information, indicating the arrangement of the first slot pattern, the second slot pattern, or the third slot pattern in the time domain. Monitoring information, which indicates the first PDCCH monitoring timing associated with the first time slot mode, the second PDCCH monitoring timing associated with the second time slot mode, or the third PDCCH monitoring timing associated with the third time slot mode; or bandwidth portion (BWP) configuration information, which indicates the first BWP configuration of the uplink BWP and downlink BWP associated with the first time slot mode, the second BWP configuration of the uplink BWP and downlink BWP associated with the second time slot mode, or the third BWP configuration of the uplink BWP and downlink BWP associated with the third time slot mode.

26. As in request item 21, wherein, The slot pattern information is included in a common information element received via System Information (SI) communication or Media Access Control Element (MAC CE) communication to a group of UEs including the RedCap UE.

27. As in request item 21, wherein, The slot pattern information is included in a dedicated information element received via a dedicated radio resource control (RRC) message, MAC CE, or dynamic permission (DG) communication, which is received either alone or in conjunction with a common information element that includes the slot pattern information.

28. The method of claim 21 further includes: using a group common downlink control information (GC-DCI) shared by the RedCap UE group including the RedCap UE, the GC-DCI indicating the respective uplink carrier index and downlink carrier index to be used by the RedCap UE.

29. The method of claim 21 further includes: via a group common downlink control information (GC-DCI) shared by a group of RedCap UEs including the RedCap UE, the GC-DCI indicating individual time slot modes from a plurality of time slot modes to be used by the RedCap UE for the HD-FDD communication and the effective duration associated with the use of the individual time slot modes.

30. As in request item 21, wherein, The HD-FDD configuration information indicates the protection period associated with switching from using a downlink carrier to using an uplink carrier, or the protection period associated with switching from using an uplink carrier to using a downlink carrier.

31. As in request item 21, wherein, The HD-FDD configuration information indicates a protection period associated with switching from using a downlink carrier to using an uplink carrier, or a protection period associated with switching from using an uplink carrier to using a downlink carrier. The duration of this protection period 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.

32. As in request item 21, wherein, The HD-FDD configuration information indicates a protection period associated with a switch from using a downlink carrier to using an uplink carrier, or a protection period associated with a switch from using an uplink carrier to using a downlink carrier, which is associated with a flexible time slot or flexible symbol associated with the time slot mode configured for the HD-FDD communication.

33. As in request item 21, wherein, The HD-FDD configuration information includes power control parameters that the RedCap UE will use to transmit uplink communication during the HD-FDD communication.

34. As in request item 21, wherein, The HD-FDD configuration information includes power control parameters to be used by the RedCap UE for transmission of the Physical Random Access Channel (PRACH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), and / or Sound Reference Signal (SRS) during the HD-FDD communication. These power control parameters are at least in part based on reduced insertion loss, improved power efficiency, improved UE receiver sensitivity, or reduced peak transmission power associated with the RedCap UE during the HD-FDD communication.

35. As in request item 21, wherein, The HD-FDD configuration information includes power control parameters to be used by the RedCap UE during HD-FDD communication. These power control parameters include offsets for target power reception, offsets for maximum output power configured by the UE, scaling factors or offsets for reference signal power in path loss estimation, or enhancement granularity, range, and power control adjustment status associated with transmit power control commands and transmit power increases.

36. As in request item 21, wherein, The HD-FDD configuration information includes measurement and reporting parameters associated with the radio resource management (RRM), radio link monitoring (RLM), or cellular positioning and beam management (BM) procedures to be performed by the RedCap UE during the HD-FDD communication. These measurement and reporting parameters are at least in part based on the time slot mode configuration, bandwidth portion (BWP) configuration, reduced insertion loss, improved power efficiency, or improved UE receiver sensitivity associated with the RedCap UE during the HD-FDD communication.

37. As in request item 21, wherein, The HD-FDD configuration information includes measurement and reporting parameters associated with the Radio Resource Management (RRM), Radio Link Monitoring (RLM), or Cellular Location and Beam Management (BM) procedures to be performed by the RedCap UE during HD-FDD communication. These measurement and reporting parameters indicate a list of measurement objects, reporting configurations, measurement identifiers, quantity configurations, or measurement gap configurations associated with performing the RRM, RLM, or BM procedures.

38. As in request item 21, 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 the cell selection process, cell reselection process, or handover process.

39. As in request item 21, wherein, The HD-FDD configuration information is received via System Information (SI), Radio Resource Control (RRC) messages, Media Access Control Element (MAC CE), or Dynamic Grant (DG) communications.

40. As in request item 21, wherein, This capability information indicates that the duplexer of the RedCap UE should be replaced by a switch and filter.

41. 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: transmit capability information to a base station, the capability information indicating the reduced capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; receive from the base station HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and communicate by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

42. An apparatus for wireless communication, comprising: means for transmitting capability information to a base station, the capability information indicating a simplified capability of the apparatus associated with performing half-duplex frequency division duplex (HD-FDD) communication; means for receiving HD-FDD configuration information from the base station for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and means for communicating by transmitting or receiving data during the HD-FDD communication, based at least partially on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

43. A base station for wireless communication, comprising: a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receive capability information from a Reduced Capability User Equipment (RedCap UE), the capability information indicating the Reduced Capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; transmit to the RedCap UE HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and perform communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

44. 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 capabilities of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; transmitting to the RedCap UE HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and performing communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

45. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions, which, when executed by one or more processors of a base station, cause the base station to: receive capability information from a Reduced Capability User Equipment (RedCap UE), the capability information indicating the reduced capability of the RedCap UE associated with performing half-duplex frequency division duplex (HD-FDD) communication; transmit to the RedCap UE HD-FDD configuration information for performing the HD-FDD communication with the base station, the HD-FDD configuration information being at least partially based on the capability information; and perform communication by transmitting or receiving data during the HD-FDD communication, at least partially based on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

46. ​​An apparatus 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 performing half-duplex frequency division duplex (HD-FDD) communication; means for transmitting to the RedCap UE HD-FDD configuration information for performing the HD-FDD communication with a base station, the HD-FDD configuration information being at least partially based on the capability information; and means for communicating by transmitting or receiving data during the HD-FDD communication, based at least partially on the HD-FDD configuration information, wherein... The HD-FDD configuration information includes index information associated with one or more carriers to be used for the HD-FDD communication. This index information indicates: a downlink carrier index associated with a downlink carrier from one or more of the carriers, configured to carry downlink transmission from the base station to the RedCap UE during the HD-FDD communication; and an uplink carrier index associated with an uplink carrier from one or more of the carriers, configured to carry uplink transmission from the RedCap UE to the base station during the HD-FDD communication. The HD-FDD configuration information includes time slot mode information, which includes one or more of the following: a first time slot mode, which includes one or more types of time slot modes indicating one or more time and frequency resource mappings for a first coherent time slot or symbol set configured on the downlink carrier. A second time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for a second coherent time slot or symbol set configured on the uplink carrier, or a third time slot mode, comprising one or more types of time slot modes indicating one or more time and frequency resource mappings for at least one of a third coherent time slot or symbol set configured on the uplink carrier, configured on the downlink carrier, or configured as a guard period.

Images