Uplink control information multiplexing for physical uplink shared channel repetition in full-duplex communication

Abstract

Some aspects of the present disclosure provide techniques for multiplexing uplink control information on a physical uplink shared channel in full duplex mode. An example method that may be performed by a UE includes receiving, from a network entity, scheduling information, the scheduling information scheduling transmission of a first full duplex (FD) slot of a plurality of uplink (UL) data channel repetitions and uplink control information (UCI), the FD slot including a UL subband for the UL transmission and a DL subband for the downlink (DL) transmission, multiplexing the first UL data channel repetition with the UCI to form a multiplexed transmission, and transmitting the multiplexed transmission in the FD slot.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to U.S. patent application Ser. No. 17 / 684,994, filed Mar. 2, 2022, the entire contents of which are incorporated by reference herein.

[0002] Aspects of the present disclosure relate to wireless communications, and more specifically, to techniques for multiplexing uplink control information on a physical uplink shared channel in full-duplex communications. [Background technology]

[0003] 2. Description of Related Art

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, broadcast, or other similar types of services. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing the available wireless communication system resources with those users.

[0004]

[0004] Although wireless communication systems have made great technological advances over the years, challenges remain. For example, complex and dynamic environments may still attenuate or block signals between wireless transmitters and wireless receivers. Thus, there remains a desire to improve the technical performance of wireless communication systems, including, for example, improving the speed and data carrying capacity of communication, improving the efficiency of use of the shared communication medium, reducing the power used by the transmitter and receiver while performing communication, improving the reliability of wireless communication, avoiding redundant transmission and / or reception and associated processing, improving the coverage area of ​​wireless communication, increasing the number and types of devices that can access the wireless communication system, improving the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, and the like. Thus, further improvements in wireless communication systems are needed to overcome the aforementioned technical challenges and others. Summary of the Invention

[0005]

[0005] One aspect provides a method of wireless communication by a user equipment (UE), the method generally including receiving, from a network entity, scheduling information, the scheduling information scheduling transmission of a first uplink (UL) data channel iteration of a plurality of uplink (UL) data channel iterations and uplink control information (UCI) in a first full duplex (FD) slot of a plurality of slots, the FD slot including a UL subband for the UL transmission and a DL subband for the downlink (DL) transmission, multiplexing the first UL data channel iteration with the UCI to form a multiplexed transmission, and transmitting the multiplexed transmission in the FD slot.

[0006]

[0006] Another aspect provides a method for wireless communication by a user equipment (UE), the method generally including receiving, from a network entity, scheduling information, the scheduling information scheduling transmission of a first uplink (UL) data channel repeat of a plurality of UL data channel repeats and uplink control information (UCI), the first UL data channel repeat being scheduled to extend across a slot boundary between a first slot of the plurality of slots and a second slot of the plurality of slots, such that a first portion of the first UL data channel repeat is scheduled to occur in the first slot and a second portion of the first UL data channel repeat is scheduled to occur in the second slot, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat, and transmitting at least the first UL data channel repeat based on the one or more actions related to the multiplexing.

[0007] Another aspect provides a method of wireless communication by a network entity. The method generally includes transmitting, to a user equipment (UE), scheduling information, the scheduling information scheduling transmission of a first uplink (UL) data channel iteration of a plurality of UL data channel iterations and uplink control information (UCI) in a first full-duplex (FD) slot of a plurality of slots, the FD slot including a UL subband for the UL transmission and a downlink (DL) subband for the DL transmission, receiving in the FD slot a multiplexed transmission including the first UL data channel iteration and the UCI, and demultiplexing the UCI from the multiplexed transmission.

[0008]

[0008] Another aspect provides a method of wireless communication by a network entity. The method generally includes transmitting, to a user equipment (UE), scheduling information, the scheduling information scheduling transmission of a first uplink (UL) data channel iteration of a plurality of UL data channel iterations and uplink control information (UCI), the first UL data channel iteration being scheduled to extend across a slot boundary between a first slot of the plurality of slots and a second slot of the plurality of slots, such that a first portion of the first UL data channel iteration is scheduled to occur in the first slot and a second portion of the first UL data channel iteration is scheduled to occur in the second slot, receiving, in the first slot or the second slot, a multiplexed transmission including at least the first UL data channel iteration and the UCI, and demultiplexing the UCI from the multiplexed transmission.

[0009]

[0009] Other aspects provide an apparatus operable, configured or otherwise adapted to perform the above-mentioned method and methods described elsewhere herein, a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the above-mentioned method and methods described elsewhere herein, a computer program product embodied on a computer-readable storage medium comprising code for performing the above-mentioned method and methods described elsewhere herein, and an apparatus comprising means for performing the above-mentioned method and methods described elsewhere herein. By way of example, the apparatus may comprise a processing system, a device having a processing system, or processing systems cooperating over one or more networks.

[0010]

[0010] The following description and the annexed drawings set forth certain features for purposes of illustration. [Brief description of the drawings]

[0011]

[0011] The accompanying drawings illustrate certain features of the various aspects described herein and should not be considered as limiting the scope of the disclosure. [Figure 1]

[0012] 1 illustrates an exemplary wireless communication network. [Diagram 2]

[0013] 1 illustrates an exemplary split base station architecture. [Diagram 3]

[0014] 1 illustrates aspects of an exemplary base station and exemplary user equipment. [Figure 4A]

[0015] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4B] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4C] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4D] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 5A]

[0016] 1 illustrates different FD use cases within a wireless communication network. [Figure 5B] 1 illustrates different FD use cases within a wireless communication network. [Figure 5C] 1 illustrates different FD use cases within a wireless communication network. [Figure 6A]

[0017] 1 illustrates an exemplary slot format that includes at least one subband full duplex slot. [Figure 6B] 1 illustrates an exemplary slot format that includes at least one subband full duplex slot. [Figure 7A]

[0018] 1 illustrates different embodiments of physical uplink shared channel (PUSCH) repetition; [Figure 7B]1 illustrates different embodiments of physical uplink shared channel (PUSCH) repetition; [Figure 8]

[0019] 1 illustrates a process flow for communication in a network between a UE and a network entity. [Figure 9]

[0020] 1 illustrates an example slot format including at least one SBFD slot and transmission by a UE transmitting a PUSCH with Type-A repetition, according to an aspect of the disclosure. [Figure 10]

[0021] 1 illustrates a process flow for communication in a network between a UE and a network entity. [Figure 11A]

[0022] 1 illustrates an example slot format including an SBFD slot and a transmission by a UE transmitting a PUSCH with Type-B repetition, according to an aspect of the disclosure. [Figure 11B] 1 illustrates an example slot format including an SBFD slot and a transmission by a UE transmitting a PUSCH with Type-B repetition, according to an aspect of the disclosure. [Figure 11C] 1 illustrates an example slot format including an SBFD slot and a transmission by a UE transmitting a PUSCH with Type-B repetition, according to an aspect of the disclosure. [Figure 12]

[0023] A method of wireless communication is shown. [Figure 13]

[0024] A method of wireless communication is shown. [Figure 14]

[0025] A method of wireless communication is shown. [Figure 15]

[0026] A method of wireless communication is shown. [Figure 16]

[0027] 1 illustrates aspects of an exemplary communications device. [Figure 17]

[0028] 1 illustrates aspects of an exemplary communications device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012]

[0029] Aspects of the present disclosure provide an apparatus, a method, a processing system, and a computer-readable medium for multiplexing uplink control information (UCI) on physical uplink shared channels (PUSCHs) in full duplex (FD) mode.

[0013]

[0030] Sub-band full duplex (SBFD) refers to wireless communications capable of simultaneous uplink (UL) and downlink (DL) transmissions on sub-bands of a communications bandwidth during a particular time period. In full-duplex (FD) mode, the UL FD resource in an SBFD slot may be smaller than the frequency resource of a legacy uplink slot (also referred to herein as a U-slot). A UE may transmit one or more copies of a physical uplink shared channel (PUSCH), referred to herein as a PUSCH repetition(s), in response to control signals from the network (e.g., downlink control information (DCI) from a network entity). PUSCH repetitions may improve the reliability of communications from the UE. It may be desirable for a UE transmitting with PUSCH repetitions in a system implementing SBFD to adapt some transmissions to FD resources that vary across the uplink and SBFD slots.

[0014]

[0031] Aspects of the present disclosure provide techniques for a UE operating in an SBFD communication system to adapt multiplexing of uplink control information (UCI) with a physical uplink shared channel (PUSCH). In some aspects of the present disclosure, the UE may determine whether and how much UCI to drop when multiplexing UCI with PUSCH during a slot or symbol in FD mode. In some aspects, the UE may determine during which slot or symbol UCI to multiplex with PUSCH based on whether PUSCH is scheduled to be transmitted during the slot or symbol in FD mode. In some aspects of the present disclosure, the UE may split UCI such that a first portion of UCI is transmitted using a first repetition of PUSCH and a second portion of UCI is transmitted using a second repetition of PUSCH.

[0015]

[0032] As described herein, accommodating multiplexing of UCI and PUSCH in an FD communications system can improve the latency of the communications system since a UE implementing the described techniques can transmit UCI more quickly and reliably than previously known techniques operating in an FD communications system.

[0016] Introduction to wireless communication networks

[0033] The techniques and methods described herein can be used for a variety of wireless communication networks. Although aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may be applicable to other communication systems and standards not explicitly mentioned herein.

[0017]

[0034] FIG. 1 illustrates an example of a wireless communication network 100 in which aspects described herein may be implemented.

[0018]

[0035] Generally, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes), which are generally, for example, logical entities associated with communication devices and / or communication functions associated with communication devices. For example, the various functions of the network, as well as the various devices associated with and interacting with the network, may be considered network entities.

[0019]

[0036] In the illustrated example, the wireless communication network 100 includes a base station (BS) 102, a user equipment (UE) 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and a 5G Core (5G Core, 5GC) network 190, which interoperate to provide communication services over various communication links, including wired and wireless links.

[0020]

[0037] 1 illustrates various exemplary UEs 104, which may more generally include a mobile phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an internet of things (IoT) device, an always on (AON) device, an edge processing device, or other similar devices. The UEs 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, or the like.

[0021]

[0038] The BS 102 communicates wirelessly with the UE 104 via a communication link 120. The communication link 120 between the BS 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the BS 102, and / or downlink (DL) (also referred to as forward link) transmissions from the BS 102 to the UE 104. The communication link 120 may use Multiple-Input and Multiple-Output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0022]

[0039] 1 illustrates various exemplary BSs 102, which may more generally include a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a transmit / receive point, etc. Each of the BSs 102 may provide communication coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell and may overlap in some cases (e.g., a small cell 102′ may have a coverage area 110′ that overlaps with a coverage area 110 of a macro cell). A BS may provide communication coverage for, for example, a macrocell (covering a relatively large geographic area), a picocell (covering a relatively smaller geographic area, such as a sports stadium), a femtocell (covering a relatively smaller geographic area (e.g., a home)), and / or other types of cell.

[0023]

[0040] Although the BS 102 is shown in various aspects as a unified communications device, the BS 102 may be implemented in various configurations. For example, one or more components of a base station may be distributed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, to name a few. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., the BS 102) may include components located in a single physical location or components located in various physical locations. In an embodiment in which a base station includes components located in various physical locations, the various components may each perform functions such that the various components collectively achieve similar functionality as a base station located in a single physical location. In some aspects, a base station that includes components located at different physical locations may be referred to as a split radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. Figure 2 illustrates and describes an example split base station architecture.

[0024]

[0041] Different BSs 102 in the wireless communication network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and 5G. For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G new radio (NR) or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) via a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0025]

[0042] The wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, the subdivision is effected based on wavelength and frequency, where the frequencies may also be referred to as carriers, subcarriers, frequency channels, tones, or subbands. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 600 MHz to 6 GHz, which is often (interchangeably) referred to as "sub-6 GHz." Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 26 to 41 GHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). Base stations (e.g., mmWave base stations such as BS 180) configured to communicate using mmWave / near-mmWave radio frequency bands may utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0026]

[0043] The communication link 120 between the BS 102 and, for example, the UE 104 may pass one or more carriers that may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and other MHz) and may be aggregated in various manners. The carriers may or may not be adjacent to each other. The allocation of carriers may also be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than UL).

[0027]

[0044] Communications using higher frequency bands may have higher path loss and shorter range compared to lower frequency communications. Thus, some base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with the UE 104 to improve path loss and range. For example, the BS 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182′. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182″. The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions 182″. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182′. The BS 180 and the UE 104 may then perform beam training to determine the best receive and transmit directions for each of the BS 180 and the UE 104. In particular, the transmit and receive directions for the BS 180 may or may not be the same. Similarly, the transmit and receive directions for the UE 104 may or may not be the same.

[0028]

[0045] The wireless communication network 100 further includes a Wi-Fi access point (AP) 150 in communication with a Wi-Fi station (STA) 152 via a communication link 154, for example, in the 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0029]

[0046] Particular UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).

[0030]

[0047] The EPC 160 may include various functional components, including, in the illustrated example, a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0031]

[0048] Generally, user Internet Protocol (IP) packets are forwarded through a Serving Gateway 166, which itself is connected to a PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming services, and / or other IP services.

[0032]

[0049] The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions and may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN) and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to BSs 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start / stop) and collecting eMBMS related charging information.

[0033]

[0050] The 5GC 190 may include various functional components, including an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196.

[0034]

[0051] The AMF 192 is a control node that handles signaling between the UE 104 and the 5GC 190. The AMF 192 provides, for example, quality of service (QoS), flow and session management.

[0035]

[0052] Internet Protocol (IP) packets are forwarded through UPF 195, which connects to IP services 197 and provides UE IP address allocation and other functions for 5GC 190. IP services 197 may include, for example, Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0036]

[0053] In various aspects, the network entities or network nodes may be implemented as aggregate base stations, as distributed base stations, as integrated access and backhaul (IAB) nodes, as relay nodes, as sidelink nodes, to name a few.

[0037]

[0054] 2 illustrates an exemplary split base station 200 architecture. The split base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with the core network 220 via a backhaul link or indirectly with the core network 220 via one or more split base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both). The CUs 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 240 simultaneously.

[0038]

[0055] Each of the units, i.e., CU 210, DU 230, RU 240, quasi-RT RIC 225, non-RT RIC 215, and SMO framework 205, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Furthermore, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit or transmit signals via a wireless transmission medium to one or more of the other units.

[0039]

[0056] In some aspects, the CU 210 may host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and the like. Each control function may implement an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 210 may be implemented to communicate with the DU 230, as necessary, for network control and signaling.

[0040]

[0057] The DU 230 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may correspond to a 3G Partnership Project (3GPP)-compliant 3GPP ... rdDepending at least in part on a functional division such as that defined by the Third Generation Partnership Project (3GPP), the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 230 may further host one or more lower PHY layers. Each layer (or module) may implement an interface configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0041]

[0058] The lower layer functions may be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division such as a lower layer functional division. In such an architecture, the RU(s) 240 may be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU(s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0042]

[0059] The SMO framework 205 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, the CU 210, the DU 230, the RU 240, and the quasi-RT RIC 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0043]

[0060] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the quasi-RT RIC 225 (e.g., via an A1 interface). The quasi-RT RIC 225 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and action via one or more CUs 210, one or more DUs 230, or both, and interfaces connecting the O-eNB to the quasi-RT RIC 225 (e.g., via an E2 interface).

[0044]

[0061] In some implementations, the non-RT RIC 215 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 225. Such information may be utilized by the quasi-RT RIC 225 or may be received at the SMO framework 205 or the non-RT RIC 215 from non-network data sources or from network functions. In some embodiments, the non-RT RIC 215 or the quasi-RT RIC 225 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 215 may employ the AI / ML models to monitor long-term trends and patterns regarding performance and take corrective action via the SMO framework 205 (e.g., reconfiguration via O1) or via the creation of RAN management policies (e.g., A1 policies).

[0045]

[0062] FIG. 3 illustrates an example aspect of the BS 102 and UE 104.

[0046]

[0063] Generally, the BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively 334), transceivers 332a-t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, the BS 102 can transmit and receive data between the BS 102 and the UE 104. The BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communications.

[0047]

[0064] Generally, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-r (collectively 352), transceivers 354a-r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 362) and wireless reception of data (e.g., data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0048]

[0065] For an example downlink transmission, the BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control signals from a controller / processor 340. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. In some examples, the data may be for a physical downlink shared channel (PDSCH).

[0049]

[0066] The transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0050]

[0067] A transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) in transceivers 332a-t. Each modulator in transceivers 332a-t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a-t may be transmitted via antennas 334a-t, respectively.

[0051]

[0068] To receive downlink transmissions, the UE 104 includes antennas 352a-352r, which can receive downlink signals from the BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in the transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0052]

[0069] A MIMO detector 356 may obtain received symbols from all demodulators in the transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols and provide decoded data for the UE 104 to a data sink 360 and provide decoded control information to the controller / processor 380.

[0053]

[0070] For an example uplink transmission, the UE 104 further includes a transmit processor 364 that can receive and process data (e.g., for a PUSCH) from a data source 362 and control information (e.g., for a physical uplink control channel (PUCCH)) from a controller / processor 380. The transmit processor 364 can also generate reference symbols for a reference signal (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM, etc.), and transmitted to the BS 102.

[0054]

[0071] At the BS 102, the uplink signals from the UE 104 may be received by antennas 334a-t, processed by demodulators in transceivers 332a-t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information transmitted by the UE 104. The receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to a controller / processor 340.

[0055]

[0072] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0056]

[0073] A scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0057]

[0074] In various aspects, the BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data from the data source 312, the scheduler 344, the memory 342, the transmit processor 320, the controller / processor 340, the TX MIMO processor 330, the transceivers 332a-t, the antennas 334a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from the antennas 334a-t, the transceivers 332a-t, the RX MIMO detector 336, the controller / processor 340, the receive processor 338, the scheduler 344, the memory 342, and other aspects described herein.

[0058]

[0075] In various aspects, the UE 104 may similarly be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data from the data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antennas 352a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from the antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and other aspects described herein.

[0059]

[0076] In some aspects, the processor may be configured to perform various operations, such as those associated with the methods described herein, to transmit (output) data to or receive (obtain) data from another interface configured to transmit or receive data, respectively.

[0060]

[0077] 4A, 4B, 4C, and 4D illustrate aspects of data structures for a wireless communication network, such as wireless communication network 100 of FIG.

[0061]

[0078] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe in a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of a DL channel in a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe in a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of a UL channel in a 5G subframe.

[0062]

[0079] A wireless communication system may utilize orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) on the uplink and downlink. Such a system may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers (e.g., as shown in FIGS. 4B and 4D). Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and in the time domain with SC-FDM.

[0063]

[0080] The wireless communication frame structure may be frequency division duplex (FDD) where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. The wireless communication frame structure may also be time division duplex (TDD) where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.

[0064]

[0081] In Figures 4A and 4C, the wireless communication frame structure is TDD, D is DL, U is UL, and X is flexible for use between DL / UL. The UE may be configured with the slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). In the illustrated example, a 10 ms frame is divided into ten equally sized 1 ms subframes. Each subframe may include one or multiple time slots. In some examples, each slot may include 7 or 14 symbols depending on the slot configuration. A subframe may also include a minislot, which generally has fewer symbols than an entire slot. Other wireless communication technologies may have different frame configurations and / or different channels.

[0065]

[0082] In general, the number of slots in a subframe is based on the slot configuration and numerology. In slot configuration 0, the different numerologies (μ) 0-5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. In slot configuration 1, the different numerologies 0-2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. Subcarrier spacing and symbol length / duration are functions of numerology. Subcarrier spacing is 2 μ×15 kHz, where μ is a numerology from 0 to 5. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz, and numerology μ=5 has a subcarrier spacing of 480 kHz. The symbol length / period is inversely proportional to the subcarrier spacing. Figures 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol period is approximately 16.67 μs.

[0066]

[0083] A resource grid may be used to represent the frame structure, as shown in Figures 4A, 4B, 4C, and 4D. Each time slot includes resource blocks (RBs) (also referred to as physical RBs (PRBs)), spanning 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0067]

[0084] As shown in Figure 4A, some of the REs carry reference (pilot) signals (RS) for UEs (e.g., UE 104 in Figures 1 and 3). The RSs may include demodulation RSs (DMRSs) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0068]

[0085] 4B shows an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs), each CCE containing 9 RE Groups (REGs), each REG containing 4 consecutive REs within one OFDM symbol.

[0069]

[0086] A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE (e.g., 104 in Figures 1 and 3) to determine subframe / symbol timing and physical layer identification information.

[0070]

[0087] A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identity and the timing of the radio frame.

[0071]

[0088] Based on the physical layer identity and the group number of the physical layer cell identity, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the above-mentioned DMRS. A physical broadcast channel (PBCH) carrying a master information block (MIB) may be logically grouped with a PSS and an SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and a system frame number (SFN). A physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0072]

[0089] As shown in FIG. 4C, some of the REs carry DMRS (denoted as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE 104 may also transmit a Sounding Reference Signal (SRS). The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb configuration, and the UE may transmit the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0073]

[0090] 4D shows an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be arranged as shown. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic retransmission request (HARQ) ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0074] Aspects Related to Multiplexing UCI on PUSCH in FD Mode

[0091] 5A, 5B, and 5C illustrate different FD use cases in a wireless communication network, such as wireless communication network 100. For example, FIG. 5A illustrates a first FD use case involving transmission between one UE 502 and two base stations (or multiple transmission reception points, mTRPs), BS 504 and BS 506. In some cases, UE 502 may represent UE 104 of FIG. 1, and BSs 504, 506 may represent BS 102 of FIG. 1. As shown, UE 502 may simultaneously receive DL transmission 508 from BS 506 and transmit UL transmission 510 to BS 506. In some cases, DL transmission 508 and UL transmission 510 may be performed using different antenna panels to facilitate simultaneous transmission and reception.

[0075]

[0092] A second FD use case involving two different UEs and one BS is shown in Figure 5B. As shown, a UE 502 can receive a DL transmission 508 from a BS 504 while another UE 512 can simultaneously transmit a UL transmission 510 to the BS 504. Thus, in this example, the BS 504 is engaged in simultaneous uplink and downlink communication.

[0076]

[0093] A third FD use case involving one BS and one UE is shown in Figure 5C. As shown, the UE 502 can receive a DL transmission 508 from the BS 504 and can simultaneously transmit a UL transmission 510 to the BS 504. As mentioned above, such simultaneous reception / transmission by the UE 502 can be facilitated by different antenna panels.

[0077]

[0094] Table 1 below shows various example scenarios in which each of the FD use cases can be used.

[0078] [Table 1]

[0079]

[0095] As shown, when FD capability is disabled in both the base station and the UE, the baseline 5G behavior can be used (e.g., half-duplex (HD) communication). When FD capability is disabled in the BS but enabled in the UE, the UE can operate according to a first exemplary FD use case shown in FIG. 5A, in which the UE can simultaneously communicate with two different TRPs using two different antenna panels (e.g., simultaneous UL and DL transmissions). When FD is enabled in the BS but disabled in the UE (e.g., the UE is not FD-capable), the BS can operate according to a second exemplary FD use case shown in FIG. 5B, in which the BS can simultaneously communicate with two different UEs using two different antenna panels (e.g., simultaneous UL and DL transmissions). Finally, when FD is enabled in both the BS and the UE, the BS and the UE can operate according to a third exemplary FD use case shown in FIG. 5C, in which the BS and the UE can simultaneously communicate with each other on UL and DL, and each of the BS and the UE uses a different antenna panel for UL and DL transmissions.

[0080]

[0096] FD communications can be facilitated by the use of frequency division multiplexing (FDM) or spatial division multiplexing (SDM). In FDM, simultaneous UL and DL transmissions can be transmitted in the same time resource, but on separate frequency bands separated by guard bands. In SDM, simultaneous UL and DL transmissions can be transmitted on the same time and frequency resource, but spatially separated into different directional transmit beams. Such FD communications are in contrast to HD communications, which use time division multiplexing (TDM), in which UL and DL transmissions are scheduled on the same or different frequency resources, but different time resources.

[0081]

[0097] In some cases, a user equipment (UE) may be scheduled to transmit uplink data on a physical uplink shared channel (PUSCH). A base station (BS) may schedule an uplink transmission on the PUSCH by sending a downlink control information (DCI) containing a dynamic grant (DG) to the UE, or may send a radio resource control (RRC) signaling containing a configured grant (CG) to the UE.

[0082]

[0098] The DG may include an indication of one or more time and frequency resources for transmitting an uplink transmission on the PUSCH. In some cases, the one or more time and frequency resources may be aperiodic and may be assigned to a UE for a particular uplink transmission. Thus, when another uplink transmission needs to be scheduled for the UE, the BS may send another dynamic grant with additional scheduling information for this other uplink transmission. Conversely, the CG assigns a UE a periodic set of time and frequency resources that can be shared with multiple other UEs. For example, the base station may send a CG that assigns resources to multiple UEs, and the UEs may randomly utilize the resources when they have data to transmit.

[0083]

[0099] In some situations, the UE may have uplink (UL) control information (UCI) to transmit when the UE is scheduled to transmit a PUSCH. In such a case, the UE may multiplex the UCI with other data in the PUSCH transmission. When multiplexing UCI and PUSCH, the UE may use a parameter β, which is the maximum percentage of REs allocated for PUSCH that can be utilized to carry UCI on the PUSCH. offset It can be composed of:

[0084]

[0100] Dynamic and semi-static β offsetBoth the semi-static and the β offset The indication may be applied by the network using a fallback DCI for UL allocation, in which case β with the fallback DCI offset The set of semi-static β is reused for HARQ-ACK and CSI transmission using CG. offset Semi-static beta associated with instructions offset The value is the dynamic beta offset Beta associated with instructions offset The value may be different.

[0085]

[0101] The network (e.g., a network entity such as a base station) uses Radio Resource Control (RRC) signaling to offset A set of values ​​can be constructed. Each β offset The value set can include multiple entries, each corresponding to a UCI type. The UCI type can include two-part CSI (e.g., CSI part 1 and CSI part 2) and hybrid automatic repeat request (HARQ) acknowledgement (ACK) information. offset The set of values ​​is β offset As a basis for determining the set of values, a set of values ​​provided in a legacy system (eg, long-term evolution (LTE)) can be used.

[0086]

[0102] In some cases, when HARQ-ACK information is piggybacked on (e.g., transmitted via) a PUSCH transmitted by a user equipment (UE), three β offset Values ​​can be defined as a set corresponding to the following cases: O ACK <= 2 [3]≦O ACK ≦

[11] , or O ACK >

[11] In the formula, O ACK represents the number of HARQ-ACK bits in the PUSCH.

[0087]

[0103] In some cases, when CSI is piggybacked on the PUSCH transmitted by the UE, four β offset A set of values ​​is defined. For example, the number of bits in CSI part 1 may be defined as follows: O CSI_part1 ≦

[11] , or O CSI_part1 >

[11] On the other hand, the number of bits in CSI part 2 can be defined as follows: O CSI_part2 ≦

[11] , or O CSI_part2 >

[11] In the formula, O CSI_part1 represents the number of CSI part 1 bits in the PUSCH, and O CSI_part2 represents the number of CSI part 2 bits. When CSI is piggybacked on the PUSCH transmitted by the UE, 2 bits in the physical downlink control channel (PDCCH) are used to determine the number of β offset An index into a set of values ​​can be dynamically indicated.

[0088]

[0104] The UE selects dynamic β for UL allocation. offset and if configured (e.g., by a network entity) with a non-fallback DCI, β offset Four sets of values ​​can be configured for HARQ-ACK and CSI, respectively. In this case, the two bits in the non-fallback DCI are β offset It can indicate one of four sets of values.

[0089]

[0105] β offset One table of values ​​can be used for HARQ-ACK, but offset A separate table of values ​​may be used for both CSI parts 1 and 2. Both tables may contain, for example, 32 entries. In one embodiment, β for HARQ-ACK isoffset The table of values ​​may reuse 16 entries from tables used in legacy wireless systems (e.g., LTE Table 8.6.3-1 in 36.213). Other entries in the table are unused and may be marked as reserved. In another embodiment, the β offset The table of values ​​reuses 16 entries from tables used in legacy wireless systems (e.g., LTE Table 8.6.3-3 in 36.213) and can include the additional values ​​8, 10, 12.625, 15.875, and 20. Other unused entries in this example table can be marked as reserved.

[0090]

[0106] In some cases, the modulated HARQ-ACK symbol may be mapped to REs around the demodulation reference signal (DMRS) symbol(s). The modulated HARQ-ACK symbol may be mapped starting on the first available non-DMRS symbol after the first DMRS symbol(s), regardless of the number of DMRS symbols in the PUSCH transmission. CSI Part 1 and CSI Part 2 may be mapped starting on the first available non-DMRS symbol, regardless of the number of DMRS symbols in the PUSCH transmission.

[0091]

[0107] If the PUSCH is punctured by the HARQ-ACK, CSI Part 1 may be mapped starting after the RE reserved for carrying the HARQ-ACK symbol. CSI Part 1 information (e.g., bits) may not be mapped to the RE reserved for carrying the HARQ-ACK information. CSI Part 2 may not be mapped to the RE carrying the CSI Part 1 information. CSI Part 2 information and PUSCH information may be mapped to the RE reserved for the HARQ-ACK information.

[0092]

[0108] When the PUSCH rate is matched by the HARQ-ACK, the HARQ-ACK may be mapped first, followed by CSI Part 1. CSI Part 1 and CSI Part 2 may not be mapped to the HARQ-ACK RE.

[0093]

[0109] When scheduled, the UE may transmit uplink data in a transport block (TB) on the PUSCH. In some cases, to improve data transmission coverage of the uplink transmission, the UE may repeat transmission of a TB across multiple slots, known as a PUSCH repetition. In some cases, one TB may be transmitted in one slot, and multiple copies (e.g., repetitions) of the TB may be transmitted across multiple slots. The multiple copies / repetitions of the TB may be transmitted using different redundancy versions (RVs).

[0094]

[0110] In some aspects, performance can be improved by transmitting one TB on time resources in multiple slots. In other words, a single TB may be spread across multiple slots, reducing the modulation and coding scheme (MCS) (e.g., code rate) associated with the TB. The reduced code rate results in improved reliability associated with the data transmission. Channel coverage can be improved by repeating the same data (possibly with different RVs) in multiple TBs, allowing a receiver (e.g., BS) to combine the TBs for data decoding.

[0095]

[0111] Different types of PUSCH repetition may be used, such as PUSCH repetition type A and PUSCH repetition type B. Both PUSCH repetition types may be applicable to DG scheduled and CG scheduled PUSCH.

[0096]

[0112] Figures 6A and 6B show example slot formats that include at least one sub-band full duplex (SBFD) slot, with Figure 6A being from the perspective of a BS that can support full duplex communication within the slot, and Figure 6B being from the perspective of a UE that is only capable of half duplex communication within the slot.

[0097]

[0113] The slot format 600 of FIG. 6A includes a downlink slot 602 that can be used by a BS to transmit downlink information to a UE. As shown, the downlink slot 602 includes a downlink subband 604 that spans an entire bandwidth portion (BWP) 606. Additionally, as shown, the slot format 600 of FIG. 6A includes an uplink slot 608 that can be used by a UE to transmit uplink information to a BS. As shown, the uplink slot 608 includes an uplink subband 610 that spans the entire BWP 606. Additionally, as shown, the slot format 600 includes multiple SBFD slots 612 that can be used by a BS to transmit downlink information to a UE and receive uplink information from a UE. As shown, each SBFD slot 612 includes an uplink subband 614 that spans only a portion of the BWP 606. Additionally, each SBFD slot 612 includes a downlink subband 616 and a downlink subband 618, each of which spans a different portion of the BWP 606. Although the uplink subband 614, the downlink subband 616, and the downlink subband 618 are shown as spanning the entire SBFD slot 612, the uplink subband 614, the downlink subband 616, and the downlink subband 618 within the SBFD slot 612 may be allocated with per-symbol granularity.

[0098]

[0114] As mentioned above, the BS may be able to utilize the slot format 600 shown in FIG. 6A for full-duplex communication in the SBFD slot 612, but the UE may in some cases only be capable of half-duplex communication in the SBFD slot 612. For example, as shown in FIG. 6B, the UE may only be able to receive downlink information from the BS via downlink subbands 616 and 618 in the SBFD slot 612A. Similarly, in the SBFD slots 612B and 612C, the UE may only be able to transmit uplink information to the BS via uplink subband 614. In some cases, the uplink subband 614 may have a size of less than 50 PRBs, but there may be cases where it may be greater than 50 PRBs.

[0099]

[0115] FIG. 7A illustrates an example of a PUSCH repetition type A. The symbols illustrated in FIG. 7A may be configured for downlink (labeled "D"), for uplink (labeled "U"), or as special or flexible symbols (labeled "X") that can be designated as either downlink or uplink. In some cases, the BS may indicate to the UE the number of repetitions K to be applied to the PUSCH. If the number of repetitions K is greater than 1, the same start and length indicator (indicated by start and length indicator value (SLIV)) may be applied across K consecutive slots. The SLIV indicates the start symbol and length of the PUSCH. For example, the DCI 702 may indicate a SLIV for a PUSCH transmission 790, such as a start symbol 740 having a length L of 4 symbols (e.g., S=8), as illustrated in FIG. 7A. As illustrated, the PUSCH may be transmitted based on the same SLIV in each of the K consecutive slots. For example, as shown, repetition 0 of the PUSCH TB may be transmitted in a segment in slot n, and repetition 1 of the PUSCH TB may be transmitted in a segment in slot n+1. As used herein, a segment generally refers to a group of consecutive uplink configuration symbols or a group of consecutive downlink configuration symbols, as shown in Figures 7A and 7B.

[0100]

[0116] The UE may transmit the PUSCH according to repetition type B. PUSCH repetition type B may support nominal repetition within a slot and allow crossing of slot boundaries. The network may dynamically change the PUSCH repetition type and the corresponding number of repetitions using DCI. For repetition type B, each nominal repetition may be transmitted consecutively with the same consecutive symbols.

[0101]

[0117] FIG. 7B illustrates one example of a PUSCH repetition type B. The symbols illustrated in FIG. 7B may be configured for the downlink (labeled "D"), for the uplink (labeled "U"), or as special or flexible symbols (labeled "X") that can be designated as either the downlink or the uplink. As illustrated, the repetition of the PUSCH TB may be within a slot or across slots. For example, the PUSCH may cross a slot boundary, such as the boundary between slots n and n+1 illustrated in FIG. 7B.

[0102]

[0118] In some aspects, a dynamic indication of the number of repetitions may be implemented. That is, the DCI 702 may indicate a SLIV for the PUSCH TB repetition. For example, a start in symbol (S=8) may be indicated with K=2 repetitions as shown. More generally, the DCI 702 may indicate that K nominal repetitions, each having a nominal length L, may be transmitted consecutively starting from the symbol 740 (S=8), where S and L are given by the SLIV. Thus, as shown in FIG. 7B, repetition 0 may be transmitted in a segment in slot n, and repetition 1 may be transmitted in segments in slot n and slot n+1, where the segments are consecutive. Furthermore, although FIGS. 7A and 7B show exemplary uplink / downlink (U / D) symbol interaction and SLIV configurations for ease of understanding, any U / D symbol interaction or SLIV configuration may be used. As shown for nominal repetition 1 in FIG. 7B, the nominal repetition may include more than one actual repetition if the nominal repetition crosses a slot boundary. An actual repetition is an actual transmission by a transmitting device (e.g., a UE) and may not occur if the symbol on which the actual repetition occurs is not valid for transmission by the device. For example, if the first two symbols of slot n+1 in Figure 7B were downlink-only symbols, the UE would not transmit the actual repetition 2 shown in Figure 7B, but would instead transmit on the next two symbols available for uplink transmission (e.g., the uplink symbols labeled "U" in Figure 7B, or the special or flexible symbols labeled "X" in Figure 7B).

[0103]

[0119] In some cases, the UE may transmit both a PUSCH with repetition type B and a physical uplink control channel (PUCCH) with HARQ-ACK information and / or channel state information (CSI). The PUCCH may be transmitted on a single slot that overlaps with a PUSCH transmission in one or more slots. The UE may expect that all actual repetitions of the PUSCH that overlap with a PUCCH transmission meet a certain multiplexing condition for multiplexing the HARQ-ACK and / or CSI information. The UE may multiplex the HARQ-ACK and / or CSI information in the earliest actual PUSCH repetition of the PUSCH transmission that overlaps with the PUCCH transmission and includes more than one symbol. The UE may not expect the cases where all actual repetitions that overlap with a PUCCH transmission do not include more than one symbol.

[0104]

[0120] To calculate the number of coded modulation symbols per layer for PUSCH with repetition type B, offset Values ​​can be specified assuming nominal resources. For example, the number of coded modulation symbols per layer for CSI part 1 transmission can be found according to Equation 1 below. In Equation 1, M actual (l) denotes the available RE for symbol "l". For CSI Part 1 transmission on actual repetitions of PUSCH with repetition type B on uplink shared channel (UL-SCH), the number of coded modulation symbols per layer for CSI Part 1 transmission is

[0105]

number

[0106] and is determined as follows:

[0107]

number

[0108]

[0121] In formula 1, O CSI-1 is the number of bits in CSI part 1. In some cases, O CSI-1 If ≧360, then L CSI-1 = 11, otherwise L CSI-1 is the number of cyclic redundancy check (CRC) bits determined for CSI part 1. Additionally, in Equation 1,

[0109]

number

[0110] Furthermore, C UL-SCH is the number of code blocks for the UL-SCH of the PUSCH transmission. In some cases, if the DCI format for scheduling the PUSCH transmission includes a code block group transmission information (CBGTI) field indicating that the UE should not transmit the rth code block, K r = 0, otherwise K r is the r-th code block size for the UL-SCH of the PUSCH transmission.

[0111]

number

[0112] is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers,

[0113]

number

[0114] is the number of subcarriers in OFDM symbol l that carry a phase tracking reference signal (PTRS) in a PUSCH transmission. In addition, in Equation 1, Q'ACK is the number of layer-wise coded modulation symbols for HARQ-ACK transmitted on the PUSCH when the number of HARQ-ACK information bits is greater than 2, and when the number of HARQ-ACK information bits is less than or equal to 2 bits,

[0115]

number

[0116] where:

[0117]

number

[0118] is used for PUSCH transmission.

[0119]

number

[0120] is the number of resource elements reserved for potential HARQ-ACK transmissions in OFDM symbol l for

[0121]

number

[0122] In PUSCH transmission,

[0123]

number

[0124] is the number of resource elements that can be used for transmission of UCI in OFDM symbol l,

[0125]

number

[0126] is the total number of OFDM symbols for the PUSCH, including all OFDM symbols used for the DMRS. In some cases, for any OFDM symbol carrying a DMRS for the PUSCH,

[0127]

number

[0128] In addition, possibly for any OFDM symbol that does not carry a DMRS for PUSCH,

[0129]

number

[0130] Furthermore, in Equation 1, α is a scaling coefficient configured by the upper layer parameter “scaling”.

[0131] In some implementations, the UE may limit the resources allowed for UCI. The limit may be indicated by a scaling or adjustment factor (e.g., α). The scaling or adjustment factor is applied to limit the number of resource elements allocated to UCI on PUSCH scheduled by DCI. In some cases, the scaling factor may not be applied to PUSCH scheduled by DCI format 0_2. The scaling value may be indicated, for example, as "f0p5" corresponding to a scaling factor of 0.5, "f0p65" corresponding to a scaling factor of 0.65, etc.

[0132] In some implementations, the UE may drop CSI part 2 on a PUSCH with repetition type B. When a UE is scheduled to transmit a transport block on a PUSCH using repetition type B multiplexed with a CSI report(s), the part 2 CSI may be omitted according to Equation 2 below. For example, CSI part 2 may be omitted if:

[0133]

number

[0134] If greater than.

[0135]

[0124] Part 2 CSI

[0136]

number

[0137] Starting with the lowest priority level, level by level may be omitted (from the PUSCH) until the lowest priority level is reached such that: (i.e., Equation 2 is satisfied):

[0138]

[0125] When the UE transmits a PUSCH with repetition type B, the UE may determine an invalid symbol for a PUSCH with repetition type B transmission. For repetition type B, the UE may exclude invalid symbols (e.g., DL dedicated symbols) according to a slot format before the transmission of the actual repetition. The invalid symbols for a PUSCH with repetition type B may include DL dedicated symbols and other symbols that the network (e.g., a network entity) has configured as invalid for the UE to use for transmission. The UE may determine a symbol as an invalid symbol for a PUSCH repetition type B transmission when the symbol is a DL symbol semi-statically configured by RRC parameters including tdd-UL-DL-ConfigurationCommon, which is cell-specific, and tdd-UL-DLConfigurationDedicated, which is UE-specific. The UE may also determine a symbol as an invalid symbol for a PUSCH repetition type B transmission when the symbol is an invalid symbol configured by an RRC information element (IE), such as invalidSymbolPattern.

[0139] When implementing PUSCH repetition type B, the UE may receive a DCI to schedule aperiodic CSI report(s). The UE may also receive a DCI to activate semi-persistent CSI report(s) on the PUSCH without a transport block indication indicated in the CSI request field of the DCI. When the UE receives a DCI to schedule aperiodic CSI report(s) on the PUSCH without a transport block or to activate semi-persistent CSI report(s), the nominal number of repetitions may be assumed to be 1 by the UE regardless of the value of numberOfRepetitions indicated by the DCI.

[0140]

[0127] When a UE is scheduled by a DCI to transmit PUSCH repetition type B without a transport block and with aperiodic or semi-persistent CSI report(s), as indicated by a CSI request field in the DCI, the first nominal repetition is expected to be the same as the first actual repetition.

[0141]

[0128] When the UE is scheduled to transmit a PUSCH repetition type B carrying semi-persistent CSI report(s) without a corresponding PDCCH after CSI reporting is activated on the PUSCH by the "CSI request" field in the DCI received by the UE, the first nominal repetition may be omitted if the first nominal repetition is not the same as the first actual repetition (e.g., one or more symbols are invalid for the UE to transmit). Other conditions may also cause the UE to omit the first nominal repetition.

[0142] For PUSCH repetition type B, when a UE is scheduled to transmit a transport block and aperiodic CSI report(s) on the PUSCH by the CSI request field on the DCI, the CSI report(s) may only be multiplexed on the first actual repetition. Additional actual repetitions of the PUSCH may carry uplink data and / or other uplink control information. In this case, the UE may not expect the first actual repetition to have a single symbol duration.

[0143] In FD mode, the UL FD resource (e.g., RE in UL subband) in the SBFD slot may be smaller than the frequency resource of the legacy uplink slot (also referred to herein as U-slot). As mentioned above, the UE may occasionally transmit one or more copies of a PUSCH transmission, referred to herein as PUSCH repetition(s), in response to control signals from the network (e.g., downlink control information (DCI) from a network entity). PUSCH repetitions may improve the reliability of communications from the UE.

[0144]

[0131] However, this smaller allocation of frequency resources in the SBFD slot compared to the legacy uplink slot may cause problems when determining how to multiplex the UCI with the PUSCH using the techniques described above. For example, as described above, Equation 1 can be used to determine the number of coded modulation symbols per layer for CSI Part 1. However, Equation 1 is based on the legacy uplink slot and does not take into account the reduced number of frequency resources in the SBFD slot. Thus, determining the coded modulation symbols according to Equation 1 may result in the UE determining more coded modulation symbols for UCI (e.g., CSI) in some cases than there are available resources in the SBFD for carrying the UCI. Furthermore, the reduced number of frequency resources in the SBFD slot may cause problems when determining whether CSI Part 2 information needs to be omitted.

[0145]

[0132] Thus, aspects of the present disclosure provide techniques to help resolve these issues when UCI is multiplexed with PUSCH Type A and Type B repetitions in a system that uses both legacy uplink slots and SBFD slots.

[0146] In an aspect of the disclosure, a technique for determining data to multiplex and / or drop / omit when transmitting a PUSCH with Type A or Type B repetitions when the slots in which the repetitions are being transmitted have different amounts of uplink frequency resources in a communication system implementing SBFD. The technique provided may include determining a factor β that can be used to determine an amount of transmission resources to be used to carry control information in a transmission or repetition. As used herein, β is an example of an offset factor as described herein.

[0147]

[0134] An aspect of the present disclosure provides a technique for multiplexing UCI in a PUSCH transmitted according to a CG and in a PUSCH transmitted according to a DG.

[0148] Exemplary Operation of Entities in a Communications Network

[0135] Figure 8 illustrates a process flow 800 for communication in a network entity 802 and a user equipment (UE) 804. In some aspects, the network entity 802 may be an example of the BS 102 illustrated and described with respect to Figures 1 and 3, or the separate BS described with respect to Figure 2. Similarly, the UE 804 may be an example of the UE 104 illustrated and described with respect to Figures 1 and 3. However, in other aspects, the UE 804 may be another type of wireless communication device, and the network entity 802 may be another type of network entity or network node, such as those described herein. The network entity 802 and the UE 804 may communicate over a Uu interface.

[0149] The UE 804 receives 806 scheduling information from the network entity 802. The scheduling information schedules transmission of a first uplink (UL) data channel repetition of a plurality of UL data channel repetitions and uplink control information (UCI) in a first full duplex (FD) slot of a plurality of slots, the FD slot including a UL subband for the UL transmission and a downlink (DL) subband for the DL transmission. In some cases, the first UL data channel repetition may include a PUSCH type A repetition.

[0150]

[0137] At 808, the UE 804 multiplexes the first UL data channel repetition with uplink control information (UCI) to form a multiplexed transmission.

[0151]

[0138] At 810, the UE 804 transmits the multiplexed transmission in the FD slot.

[0152] According to aspects of the present disclosure, when the UE 804 is scheduled to transmit a PUSCH with repetition type A, the UE 804 may calculate the number of coding symbols to use for UCI in the PUSCH in the SBFD slot based on a value of β configured by the network (e.g., a network entity such as a base station). The UE 804 may then perform multiplexing using the calculated number of coding symbols, at 808. Variations of β described herein (e.g., β HARQ-ACK,U , β CSI-1,U , β CSI-2,U , β HARQ-ACK,SBFD , β CSI-1,SBFD , and β CSI-2,SBFD ) is an example of an offset value described herein. In such an aspect, the number of coding symbols may be further constrained by the total number of available (e.g., configured for uplink transmission and not otherwise disabled) REs in the SBFD slot. Thus, to transmit CSI part 1 (CSI-1),

[0153]

number

[0154] The number of coding symbols, denoted as , can be calculated as follows:

[0155]

number

[0156] During the ceremony, M sc,nominal represents the number of available REs in the U slot in which the repetition is transmitted, M sc,actual represents the number of available REs in the SBFD slot in which the repetition is transmitted.

[0157]

[0140] Since the multiplexing in 808 may be performed using the calculated number of coding symbols, the multiplexing may be considered to be performed based on one or more of the offset values ​​(e.g., β) that may be associated with non-FD slots of the multiple slots. In addition, the multiplexing in 808 may include, for example, determining the number of REs for multiplexing the UCI. In some cases, the number of REs may be constrained by the total number of REs available in the FD slot (related to the UL bandwidth of the slot), so the multiplexing in 808 may further be based on the bandwidth associated with the first UL data channel iteration.

[0158] FIG. 9 illustrates an example slot format 900 including at least one SBFD slot and a transmission by a UE 804 transmitting a PUSCH having type A repetition, according to an aspect of the disclosure. The slot format 900 of FIG. 9 includes a downlink slot 902 that can be used by the network entity 802 to transmit downlink information to the UE 804. As shown, the downlink slot 902 includes a downlink subband 904 that spans the BWP 906. Additionally, as shown, the slot format 900 of FIG. 9 includes uplink slots 908 and 909 that can be used by the UE 804 to transmit uplink information to the network entity 802. As shown, the uplink slots 908 and 909 each include an uplink subband 910 that spans the BWP 906. Additionally, as shown, the slot format 900 includes multiple SBFD slots 912 that can be used by the network entity 802 to transmit downlink information to the UE 804, as well as receive uplink information from the UE. As shown, each SBFD slot 912 includes an uplink subband 914 that spans only a portion of the BWP 906. In addition, each SBFD slot 912 includes a downlink subband 916 and a downlink subband 918, each of which spans a different portion of the BWP 906. Although the uplink subband 914, the downlink subband 916, and the downlink subband 918 are shown as each spanning the entire SBFD slot 912, the uplink subband 914, the downlink subband 916, and the downlink subband 918 within the SBFD slot 912 may be assigned with per-symbol granularity.

[0159]

[0142] Time and frequency resources 930, 932, and 934 in the slot format 900 are allocated for PUSCH repetitions. The UE 804 may transmit a nominal repetition 0 of the PUSCH in the time and frequency resource 930, a nominal repetition 1 of the PUSCH in the time and frequency resource 932, and a nominal repetition 2 of the PUSCH in the time and frequency resource 934. The UCI that the UE transmits multiplexed with the PUSCH may be carried in the time and frequency resource 940. The time and frequency resource 942 may be used for some or all of the UCI according to aspects of the present disclosure. As mentioned above, the UE 804 multiplexes the UCI with the PUSCH in the time and frequency resource 932, and the UE 804 may determine the number of REs to use for the UCI (represented at 942) based on the bandwidth of the uplink subband 914 of the slot.

[0160] In an aspect of the present disclosure, a UE 804 transmitting a PUSCH with repetition type A may omit (e.g., drop or discard) CSI part 2 instead of multiplexing it with the PUSCH. When a UE 804 is scheduled to transmit a transport block on a PUSCH using repetition type A multiplexed with a CSI report(s), it may omit CSI part 2 if:

[0161]

number

[0162] If it is greater than 1 (i.e., CSI part 2 is omitted such that equation 2 above is satisfied).

[0163]

[0144] More generally, when a PUSCH is scheduled for an FD slot and the UL subband of the FD slot does not include sufficient REs for a portion of the first type of information, the UE 804 may omit at least a portion of the first type of information in the UCI (e.g., CSI Part 2) instead of multiplexing that portion with the PUSCH. In an aspect of the present disclosure, when omitting a portion of the first type of information in the UCI, the omitting may be performed based on a priority level associated with the first type of information. For example, the CSI Part 2 information may be multiplexed based on a priority level (i.e., a priority level) where the number of REs required to carry the remaining level of CSI Part 2 information is less than or equal to the number of REs available for CSI Part 2 information (i.e., a priority level where the number of REs required to carry the remaining level of CSI Part 2 information is less than or equal to the number of REs available for CSI Part 2 information, as discussed above).

[0164]

number

[0165] You can omit levels starting from the lowest level and proceeding level by level until you reach the priority level below.

[0166] In an aspect of the present disclosure, a UE 804 transmitting a PUSCH with repetition type A may calculate the number of coding symbols to use for UCI in a PUSCH in an SBFD slot based on a value of β that depends on the type of UCI and whether the UCI is being transmitted in a U slot or an SBFD slot. For example, the network entity 802 ... HARQ-ACK,U , β CSI-1,U , β CSI-2,U , β HARQ-ACK,SBFD , β CSI-1,SBFD , and β CSI-2,SBFDIn such an embodiment, the number of coding symbols "Q" that can be used in a UL or SBFD slot can be calculated according to the formula described herein by using the corresponding value of β, and the multiplexing in 808 can be performed based on the calculated number of coding symbols, and therefore based on the type of UCI and the type of slot. HARQ-ACK,U , β CSI-1,U , β CSI-2,U is the corresponding value for the FD slot, β HARQ-ACK,SBFD , β CSI-1,SBFD , and β CSI-2,SBFD For example, if the UE 804 has CSI part 1 to transmit in the SBFD slot, the UE may

[0167]

number

[0168] We can set ∑ i = 1 ⁢ ... i = 1 ⁢ ⁢ ⁢ ⁢ i ⁢ ⁢ ⁢ ⁢ ( 1 ⁢ ⁢ ) ⁢ and calculate the number of coding symbols for CSI part 1 transmission according to the formula above.

[0169]

number

[0170] In some aspects, the UE also calculates two scaling or adjustment factors, α U and α SBFD and α U is used in the above equation 4 to determine the number of coding symbols for the transmission of UCI in U slots, and α SBFD is used in Equation 4 above to determine the number of coding symbols for the transmission of UCI in the SBF slot. U and α SBFDAn adjustment factor such as may be used to limit the number of resource elements allocated to UCI on a PUSCH for a PUSCH scheduled by a DCI format other than DCI format 0_2.

[0171] According to an aspect of the present disclosure, β[β HARQ-ACK、U , β CSI-1,U , β CSI-2,U , β HARQ-ACK、SBFD , β CSI-1、SBFD , β CSI-2、SBFD A herein described set of values ​​for β may be configured to the UE 804 via RRC signaling, or a subset of the values ​​may be configured via RRC signaling, and the UE may receive information in the DCI that can be used by the UE to determine others of the values. The scheduling information received by the UE at 806 may include, for example, information received in the DCI. When the UE 804 is transmitting a configured grant type 1 (CG-1) PUSCH, the UE does not receive a DCI that schedules the PUSCH, and the UE may be configured via RRC signaling with all of the herein described set of values ​​for β. The scheduling information received by the UE at 806 may include, for example, information received via RRC signaling.

[0172] In an embodiment of the present disclosure, β[β HARQ-ACK、U , β CSI-1,U , β CSI-2,U , β HARQ-ACK、SBFD , β CSI-1、SBFD , β CSI-2、SBFDA subset of the herein described set of values ​​for [β] may be configured on the UE 804 via RRC signaling, and the UE may receive information in a DCI that can be used by the UE to determine others of the values. The scheduling information received by the UE at 806 may include, for example, information received in a DCI. When the UE 804 is transmitting a configured grant type 2 (CG-2) PUSCH or a DG PUSCH, the DCI received by the UE (i.e., a DCI that may be an example of scheduling information received by the UE at 806 that triggers or schedules a PUSCH) may include, for example, [β HARQ-ACK、U、 β CSI-1,U , β CSI-2,U ], and the UE may indicate one or more values ​​of the value(s) indicated in the DCI [β HARQ-ACK、U、 β CSI-1,U , β CSI-2,U ] to [β HARQ-ACK、SBFD , β CSI-1、SBFD、 β CSI-2、SBFD A set of rules may be followed to derive the value of ]. The scheduling information received by the UE at 806 may include, for example, a configured grant for a CG-2 PUSCH or DCI.

[0173] According to an aspect of the present disclosure, β[β HARQ-ACK,U , β CSI-1,U , β CSI-2,U , β HARQ-ACK,SBFD , β CSI-1,SBFD , β CSI-2,SBFD A subset of the herein described set of values ​​for [β] may be received in a DCI by the UE, and the UE may be configured (e.g., via RRC signaling) with a set of one or more delta values ​​that the UE can use to calculate others of the values. The DCI may carry scheduling information received by the UE at 806, for example. When the UE 804 is transmitting a configured grant type 2 (CG-2) PUSCH or a DG PUSCH, the DCI received by the UE (i.e., the DCI that triggers or schedules the PUSCH) may include [βHARQ-ACK,U , β CSI-1,U , β CSI-2,U ], and the UE may indicate one or more values ​​of [β HARQ-ACK,SBFD , β CSI-1,SBFD , β CSI-2,SBFD The scheduling information received by the UE at 806 may include, for example, configured grants for CG-2 PUSCH or DCI.

[0174] In an embodiment of the present disclosure, β[β HARQ-ACK,U , β CSI-1,U , β CSI-2,U , β HARQ-ACK,SBFD , β CSI-1,SBFD , β CSI-2,SBFD A described set of values ​​for β can be indicated to the UE 804 via a DCI. The DCI can, for example, carry the scheduling information received by the UE at 806. For example, the format of the DCI can be OFFSET Additional bits may be included in the field (e.g., 4 or 6 bits instead of 2) or additional fields may be included, where the additional bits or fields are [β HARQ-ACK、U , β CSI-1,U β CSI-2,U , β HARQ-ACK、SBFD , β CSI-1、SBFD , β CSI-2、SBFD In another embodiment, the UE 804 may indicate a set of values ​​for β OFFSET UE 804 receiving the DCI indicating HARQ-ACK、U , β CSI-1,U , β CSI-2,U , β HARQ-ACK、SBFD , β CSI-1、SBFD , β CSI-2、SBFD ], so that β OFFSET From the value of β U and β SBFD The following table shows the mapping of [β HARQ-ACK、U , β CSI-1,U , β CSI-2,U , β HARQ-ACK、SBFD , β CSI-1、SBFD , βCSI-2、SBFD β to indicate the value of OFFSET 1 shows an example of a mapping indicator.

[0175] [Table 2]

[0176]

[0150] Figure 10 illustrates a process flow 1000 for communication in a network between a network entity 1002 and a user equipment (UE) 1004. In some aspects, the network entity 1002 may be an example of the BS 102 illustrated and described with respect to Figures 1 and 3, or the separate BS described with respect to Figure 2. Similarly, the UE 1004 may be an example of the UE 104 illustrated and described with respect to Figures 1 and 3. However, in other aspects, the UE 1004 may be another type of wireless communication device, and the network entity 1002 may be another type of network entity or network node, such as those described herein. The network entity 1002 and the UE 1004 may communicate over a Uu interface.

[0177]

[0151] The UE 1004 receives 1006 scheduling information from the network entity 1002. The scheduling information schedules transmission of a first uplink (UL) data channel repetition of a plurality of UL data channel repetitions and uplink control information (UCI), the first UL data channel repetition being scheduled to extend across a slot boundary between a first slot of the plurality of slots and a second slot of the plurality of slots, such that a first portion of the first UL data channel repetition is scheduled to occur in the first slot, and a second portion of the first UL data channel repetition is scheduled to occur in the second slot. In aspects of the present disclosure, the UL data channel repetition may be referred to as a nominal repetition, and the portion of the UL data channel repetition may be referred to as an actual repetition. In some cases, the UL data channel repetition may include a PUSCH type B repetition.

[0178]

[0152] At 1008, the UE 1004 takes one or more actions related to multiplexing the UCI with the first UL data channel repetition.

[0179]

[0153] At 1010, the UE 1004 transmits at least a first UL data channel repetition based on one or more actions related to multiplexing.

[0180] According to aspects of the present disclosure, a UE 1004 transmitting a PUSCH having a repetition type B may determine, based on a bandwidth available for transmission of the PUSCH during the first actual repetition, an amount of UCI data, if any, to multiplex with the PUSCH on the first actual repetition. Determining an amount of UCI data to multiplex with the PUSCH on the first actual repetition based on a bandwidth available for transmission of the PUSCH during the first actual repetition is an example of the UE taking one or more actions at 1008.

[0181]

[0155] In previously known techniques, a UE 1004 transmitting a PUSCH with repetitions multiplexes UCI with the PUSCH on the first actual repetition having a length greater than one symbol.

[0182] In an aspect of the disclosure, when the UE 1004 transmits a PUSCH having a repetition type B and the first actual repetition is in a non-FD slot (e.g., a U slot), the UE 1004 may multiplex UCI with the PUSCH on the first actual repetition, but when the first actual repetition is in a SBFD slot, the UE 1004 may determine whether to multiplex UCI on the first actual repetition based on the available bandwidth of the first actual repetition being greater than a threshold percentage of the bandwidth of the nominal repetition in the U slot or based on the total number of available resources for UCI. Thus, taking one or more actions at 1008 may be based on the slot type associated with the first slot in which the first portion of the first UL data channel repetition is scheduled being a non-FD slot (e.g., a SBFD slot).

[0183] 11A illustrates an example slot format 1100 including an SBFD slot 1112 and a transmission by a UE 1004 transmitting a PUSCH with type-B repetition, according to an aspect of the disclosure. The slot format 1100 of FIG. 11A includes an uplink slot 1108 that can be used by the UE 1004 to transmit uplink information to the network entity 1002. As shown, the uplink slot 1108 includes an uplink subband 1110 that spans the entire BWP 1106. Additionally, as shown, the slot format 1100 includes an SBFD slot 1112 that can be used by the network to transmit downlink information to the UE 1004 as well as receive uplink information from the UE. As shown, the SBFD slot 1112 includes an uplink subband 1114 that spans only a portion of the BWP 1106. In addition, SBFD slot 1112 includes downlink subband 1116 and downlink subband 1118, each spanning a different portion of BWP 1106. Although uplink subband 1114, downlink subband 1116, and downlink subband 1118 are shown as spanning the entire SBFD slot 1112, uplink subband 1114, downlink subband 1116, and downlink subband 1118 within SBFD slot 1112 may be assigned with per-symbol granularity.

[0184] A first nominal repetition, a nominal repetition of PUSCH, includes time and frequency resources 1130 and 1132. The first nominal repetition includes a first actual repetition including the time and frequency resource 1130 and a second actual repetition including the time and frequency resource 1132. According to an aspect of the present disclosure, since the first actual repetition falls in an uplink slot 1108 (e.g., a non-FD slot), the UE determines to multiplex UCI 1140 with the PUSCH in the time and frequency resource 1130. Thus, the UE 1004 determining to multiplex the UCI 1140 with the PUSCH in the time and frequency resources 1130 may be an example of the UE 1004 taking one or more actions at 1008, and transmitting a PUSCH with the UCI 1140 multiplexed in the time and frequency resources 1130 may be an example of the UE 1004 transmitting at least a first UL data channel repetition based on the one or more actions related to the multiplexing at 1010.

[0185] 11B illustrates an example slot format 1150 including an SBFD slot 1152 and a transmission by a UE 1004 transmitting a PUSCH with type-B repetition, according to an aspect of the disclosure. The slot format 1150 of FIG. 11B includes an uplink slot 1158 that can be used by the UE to transmit uplink information to the network entity 1002. As shown, the uplink slot 1158 includes an uplink subband 1160 that spans the entire BWP 1156. Additionally, as shown, the slot format 1150 includes an SBFD slot 1152 that can be used by the network to transmit downlink information to the UE and receive uplink information from the UE. As shown, the SBFD slot 1152 includes an uplink subband 1164 that spans only a portion of the BWP 1156. Additionally, the SBFD slot 1152 includes a downlink subband 1166 and a downlink subband 1168, each of which spans a different portion of the BWP 1156. Although uplink subband 1164, downlink subband 1166, and downlink subband 1168 are shown spanning the entire SBFD slot 1152, uplink subband 1164, downlink subband 1166, and downlink subband 1168 within the SBFD slot 1152 may be assigned with per-symbol granularity.

[0186]

[0160] The time and frequency resources 1170 and 1172 in the slot format 1150 are allocated for PUSCH repetitions. The UE 1004 may transmit a nominal repetition 0 of the PUSCH, which includes an actual repetition 0 in the time and frequency resource 1170 and an actual repetition 1 in the time and frequency resource 1172. The UCI that the UE transmits multiplexed with the PUSCH may be carried in the time and frequency resource 1174. Since the first actual repetition falls in the SBFD slot 1152, according to an aspect of the present disclosure, the UE determines not to multiplex the UCI with the PUSCH in the time and frequency resource 1170 based on the available bandwidth of the first actual repetition in the time and frequency resource 1170 being less than a threshold percentage of the bandwidth of the nominal repetition in the U slot (e.g., the bandwidth of the time and frequency resource 1172). Instead, the UE multiplexes the UCI in the time and frequency resources 1174 with the PUSCH in the time and frequency resources 1172. Thus, determining to multiplex the UCI in the time and frequency resources 1174 with the PUSCH in the time and frequency resources 1172 may be an example of the UE 1004 taking one or more actions at 1008, and transmitting the PUSCH with the UCI multiplexed in the time and frequency resources 1172 may be an example of the UE 1004 transmitting at least a first UL data channel repetition based on the one or more actions related to the multiplexing at 1010.

[0187]

[0161] According to an aspect of the present disclosure, when the UE 1004 transmits a PUSCH having repetition type B, the UE may multiplex the UCI over two repetitions by splitting the UCI by type (e.g., ACK / NACK and CSI) and multiplexing the first type of UCI with the PUSCH in the first repetition and multiplexing the second type of UCI with the PUSCH in the second repetition.

[0188] 11C illustrates an example slot format 1180 and a transmission by a UE 1004 transmitting a PUSCH with type B repetition, according to an aspect of the disclosure. The slot format 1180 of FIG. 11C includes a UL slot 1185 and a SBFD slot 1182. As shown, the SBFD slot 1182 includes an uplink subband 1184 and downlink subbands 1186 and 1188. Time and frequency resources 1190 and 1192 in the slot format 1180 are allocated for PUSCH repetition. The UE may transmit a nominal repetition 0 of the PUSCH, which includes an actual repetition 0 in the time and frequency resource 1190 and an actual repetition 1 in the time and frequency resource 1192. A first type of UCI (e.g., ACK / NACK) that the UE 1004 transmits multiplexed with the PUSCH may be carried in a time and frequency resource 1194 in the SBFD slot 1182. A second type of UCI (e.g., CSI) that the UE transmits multiplexed with the PUSCH may be carried in time and frequency resources 1196 in the UL slot 1185. Thus, determining to multiplex the first type of UCI with the PUSCH in time and frequency resources 1194 and the second type of UCI with the PUSCH in time and frequency resources 1196 may be an example of the UE 1004 taking one or more actions at 1008, and transmitting a PUSCH with the first type of UCI multiplexed in time and frequency resources 1190 may be an example of the UE 1004 transmitting at least a first UL data channel repetition based on the one or more actions related to the multiplexing at 1010.

[0189] In an aspect of the present disclosure, when a UE 1004 transmitting a PUSCH with repetition type B also has UCI to transmit, the UE may multiplex ACK / NACK and CSI Part 1 on the first actual repetition of the PUSCH, and if the number of available resources (e.g., REs) in the first actual repetition is sufficient for CSI Part 2 information (also referred to as CSI-2), the UE also multiplexes CSI Part 2 information with the PUSCH on the first actual repetition. If the number of available resources in the first actual repetition is limited and a dropping rule is applied to CSI-2 information, the UE may multiplex CSI-2 information with the PUSCH in the actual repetition that has the maximum amount of resources available to carry CSI-2. More generally, when the total number of resources available in the first portion of the first UL data channel repeat for UCI is less than a threshold number of resources, taking one or more actions at 1008 may include splitting the UCI into a first portion and a second portion, multiplexing the first portion of the UCI with the first portion of the first UL data channel repeat in the FD slot, and multiplexing the second portion of the UCI with the second portion of the first UL data channel repeat in the second slot, and transmitting at 1010 may include transmitting the first portion of the UCI multiplexed with the first portion of the UL data channel repeat in the FD slot, and transmitting the second portion of the UCI multiplexed with the second portion of the UL data channel repeat in the second slot. In one embodiment, the first portion of the UCI may include hybrid automatic repeat request (HARQ) acknowledgment information (e.g., ACK / NACK) and the second portion of the UCI may include channel state information (CSI) feedback. In another example, the first part of the UCI may include HARQ acknowledgment information and a first part of channel state information (CSI) feedback (e.g., CSI part 1), and the second part of the UCI may include a second part of the CSI feedback (e.g., CSI part 2).

[0190] According to aspects of the present disclosure, the number of available resources in an actual iteration may be determined by one or more offset values ​​[β HARQ-ACK,U , β CSI-1,U , β CSI-2,U , β HARQ-ACK,SBFD , β CSI-1,SBFD , β CSI-2,SBFD ], a total number of REs associated with the UL subband of the first slot, and a bandwidth associated with the first UL data channel iteration. Thus, taking one or more actions of 1008 may be based on the one or more offset values, a total number of REs associated with the UL subband of the first slot, and a bandwidth associated with the first UL data channel iteration.

[0191] In an aspect of the present disclosure, when a UE 1004 transmitting a PUSCH with repetition type B also has UCI to transmit, the UE may multiplex the UCI (e.g., ACK / NACK and CSI) on an actual repetition that has the largest amount of resources available to carry the UCI. When a first actual repetition of a nominal repetition occurs in an FD slot and a second actual repetition occurs in a non-FD slot, the UE may multiplex the UCI on the second actual repetition (e.g., as shown in FIG. 11B), which may be an example of taking one or more actions of 1008 based on at least one of a bandwidth associated with the first portion of the first UL data channel repetition or a total number of resources available in the first portion of the first UL data channel repetition for UCI.

[0192] According to aspects of the disclosure, taking one or more actions at 1008 can be based on a bandwidth associated with the first portion of the first UL data channel repeat. In these aspects, when a bandwidth associated with the first portion of the first UL data channel repeat in an FD slot is equal to or greater than a threshold percentage of a bandwidth of a second UL data channel repeat in a non-FD slot, taking one or more actions at 1008 can include multiplexing the UCI (e.g., UCI in time and frequency resource 1194 of FIG. 11C ) with the first portion of the first UL data channel repeat (e.g., in time and frequency resource 1190 of FIG. 11C ) in the FD slot (e.g., SBFD slot 1182 of FIG. 11C ), and transmitting at 1010 can include transmitting the UCI multiplexed with the first portion of the UL data channel repeat in the FD slot. And when the bandwidth associated with the first portion of the first UL data channel repeat in the FD slot is less than a threshold percentage of the bandwidth of the second UL data channel repeat in the non-FD slot, taking one or more actions at 1008 may include not multiplexing the UCI with the first portion of the first UL data channel repeat (e.g., in the time and frequency resource 1170 of FIG. 11B) in the FD slot (e.g., in the SBFD slot 1152 of FIG. 11B), and transmitting at 1010 may include transmitting the first portion of the UL data channel repeat in the FD slot without the UCI.

[0193] In aspects of the disclosure, taking one or more actions at 1008 can be based on a total number of resources available in the first portion of the first UL data channel repeat for UCI. In these aspects, when the total number of resources available in the first portion of the first UL data channel repeat for UCI is equal to or greater than a threshold number of resources (e.g., as shown in FIG. 11A or FIG. 11C), taking one or more actions at 1008 can include multiplexing the UCI (e.g., in the time and frequency resource 1194 of FIG. 11C) with the first portion of the first UL data channel repeat (e.g., in the time and frequency resource 1190 of FIG. 11C) in the FD slot (e.g., in the SBFD slot 1182 of FIG. 11C), and transmitting at 1010 can include transmitting the UCI multiplexed with the first portion of the UL data channel repeat in the FD slot. And when the total number of resources associated with the first portion of the first UL data channel repetition in the FD slot is less than the threshold number of resources, taking one or more actions at 1008 may include not multiplexing the UCI with the first portion of the first UL data channel repetition (e.g., in the time and frequency resource 1170 of FIG. 11B) in the FD slot (e.g., in the SBFD slot 1152 of FIG. 11B), and transmitting at 1010 may include transmitting the first portion of the UL data channel repetition in the FD slot without the UCI.

[0194] According to aspects of the present disclosure, when the UE 1004 transmitting a PUSCH having repetition type B also has UCI including HARQ acknowledgement information, CSI Part 1, and CSI Part 2 to transmit, taking one or more actions at 1008 may include the UE 1104 omitting some or all of the CSI Part 2 from multiplexing with the first portion of the UL data channel repeat and multiplexing the remaining UCI with the first portion of the UL data channel repeat. For example, when the number of resources available for UCI in the first portion of the first UL data channel repeat is not sufficient to transmit all of CSI Part 2 in the first portion of the first UL data channel repeat, taking one or more actions at 1008 may include omitting some or all of the CSI Part 2 information from multiplexing with the first portion of the first UL data channel repeat and multiplexing the HARQ acknowledgement information, CSI Part 1, and the remaining of CSI Part 2 with the first portion of the first UL data channel repeat. As previously mentioned, CSI Part 2 may be dropped or omitted based on the priority level of CSI Part 2.

[0195]

[0169] In an aspect of the present disclosure, the UE 1004 may determine whether to drop (e.g., not transmit) the UCI based on the value of α, where α may be an example of an adjustment factor described herein that varies depending on the type of UCI and / or whether the slot or symbol for transmission is an SBFD slot or symbol.

[0196]

[0170] According to an aspect of the present disclosure, the UE 1004 can determine a value of α (e.g., an adjustment factor) to use in calculating the number of symbols available for transmission of UCI multiplexed with the PUSCH based on whether the PUSCH is scheduled for transmission in an SBFD slot or SBFD symbol.

[0197] In aspects of the disclosure, the UE 1004 may determine a value of α to use in calculating the number of symbols available for transmission of UCI multiplexed with the PUSCH based on the type of UCI (e.g., ACK / NACK, CSI part 1, or CSI part 2) when the PUSCH is scheduled for transmission in an SBFD slot or SBFD symbol. Since multiplexing the UCI with the PUSCH may be based on the number of resources available for transmission of the UCI, taking one or more actions at 1008 may be based on the value of α determined by the UE.

[0198]

[0172] According to an aspect of the present disclosure, a UE 1004 transmitting a PUSCH on an SBFD slot (also referred to herein as a "D+U" slot) having both a downlink portion and an uplink portion may be restricted from multiplexing some UCI with the PUSCH in the D+U slot.

[0199] In aspects of the present disclosure, since the D+U slots may be very useful for carrying latency-sensitive information, the UE 1004 may multiplex only latency-sensitive UCI in the PUSCH scheduled for transmission in the D+U slots. Thus, in these cases, the UE 1004 may decide not to multiplex periodic or semi-persistent (P / SP) CSI reports with the PUSCH scheduled in the D+U slots. Thus, the UE 1004 may transmit only P / SP CSI reports in the U slots. The UE may multiplex aperiodic CSI (A-CSI) reports and ACK / NACK with the PUSCH in the D+U slots, since the A-CSI and ACK / NACK may be considered latency-sensitive. More generally, taking one or more actions at 1008 may be based on one or more rules associated with the latency requirements of different types of information included in the UCI. For example, the network standard may include one or more rules that may specify that a first type of information (e.g., HARQ acknowledgement information or A-CSI report) included in the UCI is allowed to be multiplexed with a first portion of the first UL data channel repeat in the FD slot, and a second type of information (e.g., CSI Part 1 or semi-persistently scheduled CSI report) and a third type of information (e.g., CSI Part 2 or periodic CSI report) included in the UCI are not allowed to be multiplexed with the first UL data channel repeat in the FD slot. In this example, taking one or more actions at 1008 may include omitting the second type of information and the third type of information included in the UCI from being multiplexed with the first portion of the first UL data channel repeat in the FD slot, and multiplexing the first type of information included in the UCI with the first portion of the first UL data channel repeat in the FD slot.

[0200] According to aspects of the present disclosure, a dropping rule applicable to UCI may be defined for D+U slots. For example, the UE 1004 may only multiplex ACK / NACK with the PUSCH scheduled for transmission in the D+U slot, and other types of UCI may not be multiplexed with the PUSCH scheduled for transmission in the D+U slot. In another embodiment, the UE 1004 may only multiplex ACK / NACK and CSI Part 1 with the PUSCH scheduled for transmission in the D+U slot, and CSI Part 2 may not be multiplexed with the PUSCH scheduled for transmission in the D+U slot.

[0201] Exemplary Operation of User Equipment FIG. 12 illustrates a method 1200 of wireless communication by a UE, such as the UE 104 of FIGS.

[0202]

[0176] Method 1200 starts at 1202 with receiving scheduling information from a network entity, the scheduling information scheduling transmission of a first full duplex (FD) slot of a plurality of uplink (UL) data channel repetitions and uplink control information (UCI) in a first FD slot of a plurality of slots, the FD slot including a UL subband for the UL transmission and a downlink (DL) subband for the DL transmission.

[0203]

[0177] The method 1200 then proceeds to step 1204, where it multiplexes the first UL data channel repetition with the UCI to form a multiplexed transmission.

[0204]

[0178] The method 1200 then proceeds to step 1206, where the multiplexed transmission is transmitted in the FD slot.

[0205]

[0179] Various aspects relate to the method 1200, including the following aspects.

[0206]

[0180] In one aspect, multiplexing the first UL data channel repetition with UCI to form a multiplexed transmission for transmission in an FD slot is based on one or more offset values ​​associated with non-FD slots of the multiple slots used to determine the number of resource elements (REs) for multiplexing the UCI in the first UL data channel repetition.

[0207]

[0181] In some aspects, the method 1200 further includes determining a number of REs for multiplexing the UCI based on one or more offset values ​​associated with the non-FD slot, and multiplexing the first UL data channel repeat with the UCI includes multiplexing the determined number of REs for the UCI with the first UL data channel repeat to form a multiplexed transmission.

[0208]

[0182] In some aspects, determining the number of REs for multiplexing the UCI is further based on the total number of REs associated with the UL subband of the FD slot and the bandwidth associated with the first UL data channel iteration.

[0209]

[0183] In some aspects, each of the one or more offset values ​​is associated with a different type of information in the UCI.

[0210]

[0184] In some aspects, the method 1200 further includes omitting at least a portion of the first type of information in the UCI from being multiplexed with the first UL data channel repetition when the UL subband of the FD slot does not include sufficient REs for a portion of the first type of information based on a total number of REs associated with the UL subband of the FD slot and a number of REs associated with the first type of information.

[0211]

[0185] In some aspects, omitting a portion of the first type of information is based on a priority level associated with the portion of the first type of information.

[0212]

[0186] In one aspect, multiplexing the first UL data channel repetition with UCI to form a multiplexed transmission for transmission in an FD slot is based on a first set of offset values ​​used to determine a number of resource elements (REs) for multiplexing the UCI in the first UL data channel repetition, the first set of offset values ​​being associated with the FD slot and different from a second set of offset values ​​associated with the non-FD slot.

[0213]

[0187] In some aspects, the first set of offset values ​​associated with the first FD slot includes different offset values ​​for different types of information in the UCI.

[0214]

[0188] In some aspects, a first set of offset values ​​associated with an FD slot depends on the total number of resource elements (REs) in the UL subband of the FD slot, and a second set of offset values ​​associated with a non-FD slot depends on the total number of REs in the UL subband of the non-FD slot.

[0215]

[0189] In some aspects, the method 1200 further includes determining a number of REs for multiplexing the UCI based on a first set of offset values ​​associated with the FD slot, and multiplexing the first UL data channel repeat with the UCI includes multiplexing the determined number of REs for the UCI with the first UL data channel repeat to form a multiplexed transmission.

[0216] In some aspects, determining the number of REs for multiplexing the UCI is further based on a total number of REs associated with the UL subband of the non-FD slot, In some aspects, determining the number of REs for multiplexing the UCI is further based on an adjustment factor that limits the number of REs available for UCI in the first FD slot.

[0217]

[0191] In some aspects, the scheduling information includes a first type of configured grant received from a network entity via radio resource control (RRC) signaling, and the method 1200 further includes receiving a first set of offset values ​​and a second set of offset values ​​from the network entity via the RRC signaling.

[0218]

[0192] In some aspects, the scheduling information includes a second type of configured grant received in downlink control information (DCI) via a physical downlink control channel (PDCCH) from the network entity, or the scheduling information includes a dynamic grant received in downlink control information (DCI) via the physical downlink control channel (PDCCH) from the network entity.

[0219]

[0193] In some aspects, the DCI further includes one of the first set of offset values ​​or the second set of offset values ​​associated with a non-FD slot.

[0220]

[0194] In some aspects, the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method 1200 further includes deriving the first set of offset values ​​associated with the FD slots based on the second set of offset values ​​associated with the non-FD slots and one or more rules in the wireless standard.

[0221]

[0195] In some aspects, the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method 1200 further includes receiving a delta value via radio resource control (RRC) signaling from a network entity, and deriving the first set of offset values ​​associated with the FD slots by applying the delta value to an offset value in the second set of offset values ​​associated with the non-FD slots.

[0222]

[0196] In some aspects, the DCI further includes a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0223]

[0197] In some aspects, the DCI indicates, via more than two bits, a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0224] In one aspect, the method 1200, or any aspect related thereto, may be performed by an apparatus such as a communications device 1600 of Figure 16 that includes various components operable, configured, or adapted to perform the method 1200. Communications device 1600 is described in further detail below.

[0225]

[0199] It should be noted that FIG. 12 is merely one example of a method, and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0226] FIG. 13 illustrates a method 1300 of wireless communication by a UE, such as the UE 104 of FIGS.

[0227]

[0201] Method 1300 begins at 1302 with receiving scheduling information from a network entity, the scheduling information scheduling transmission of a first uplink (UL) data channel repeat of a plurality of UL data channel repeats and uplink control information (UCI), the first UL data channel repeat being scheduled to extend across a slot boundary between a first slot of the plurality of slots and a second slot of the plurality of slots, such that a first portion of the first UL data channel repeat is scheduled to occur in the first slot and a second portion of the first UL data channel repeat is scheduled to occur in the second slot.

[0228]

[0202] The method 1300 then proceeds to step 1304, where it takes one or more actions related to multiplexing the UCI with the first UL data channel repetition.

[0229]

[0203] The method 1300 then proceeds to step 1306, where at least the first UL data channel repetition is transmitted based on one or more actions related to multiplexing.

[0230]

[0204] Various aspects relate to the method 1300, including the following aspects.

[0231]

[0205] In one aspect, taking one or more actions related to multiplexing UCI with the first UL data channel repeat is based on a slot type associated with the first slot in which the first portion of the first UL data channel repeat is scheduled.

[0232]

[0206] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel repeat is scheduled includes a non-full duplex (FD) slot, and taking one or more actions related to multiplexing the UCI with the first UL data channel repeat includes multiplexing the UCI with the first portion of the first UL data channel repeat based on the slot type associated with the first slot in which the first portion of the first UL data channel repeat is scheduled being a non-FD slot.

[0233]

[0207] In some aspects, multiplexing the UCI with the first portion of the first UL data channel repeat is further based on one or more offset values ​​associated with the non-FD slots used to determine the number of resource elements (REs) for multiplexing the UCI with the first portion of the first UL data channel repeat.

[0234]

[0208] In some aspects, multiplexing the UCI with the first portion of the first UL data channel repeat further includes determining a number of REs for multiplexing the UCI based on one or more offset values ​​associated with the non-FD slot, a total number of REs associated with the UL subbands of the first slot, and a bandwidth associated with the first UL data channel repeat, and multiplexing the determined number of REs for the UCI with the first portion of the first UL data channel repeat.

[0235]

[0209] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel repeat is scheduled includes a full duplex (FD) slot, and taking one or more actions related to multiplexing the UCI with the first UL data channel repeat is further based on at least one of a bandwidth associated with the first portion of the first UL data channel repeat or a total number of resources available in the first portion of the first UL data channel repeat for the UCI.

[0236]

[0210] In some aspects, when a bandwidth associated with a first portion of a first UL data channel repeat in an FD slot is greater than or equal to a threshold percentage of a bandwidth of a second UL data channel repeat in a non-FD slot, taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes multiplexing UCI with the first portion of the first UL data channel repeat in the FD slot, and transmitting at least the first UL data channel repeat includes transmitting UCI multiplexed with the first portion of the UL data channel repeat in the FD slot.

[0237]

[0211] In some aspects, when a bandwidth associated with a first portion of the first UL data channel repeat in an FD slot is less than a threshold percentage of the bandwidth of a second UL data channel repeat in a non-FD slot, taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes not multiplexing UCI with the first portion of the first UL data channel repeat in the FD slot, and transmitting at least the first UL data channel repeat includes transmitting the first portion of the UL data channel repeat in the FD slot without the UCI.

[0238]

[0212] In some aspects, when the total number of resources available in the first portion of the first UL data channel repeat for UCI is greater than or equal to a threshold number of resources, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat includes multiplexing the UCI with the first portion of the first UL data channel repeat in an FD slot, and transmitting at least the first UL data channel repeat includes transmitting the UCI multiplexed with the first portion of the UL data channel repeat in the FD slot.

[0239]

[0213] In some aspects, when the total number of resources available in the first portion of the first UL data channel repeat for UCI is less than a threshold number of resources, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat includes multiplexing the UCI with the first portion of the first UL data channel repeat in an FD slot, and transmitting at least the first UL data channel repeat includes transmitting the UCI multiplexed with the first portion of the UL data channel repeat in the FD slot.

[0240]

[0214] In some aspects, when the total number of resources available in the first portion of the first UL data channel repeat for UCI is less than a threshold number of resources, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat includes splitting the UCI into a first portion and a second portion, multiplexing the first portion of the UCI with the first portion of the first UL data channel repeat in an FD slot, and multiplexing the second portion of the UCI with the second portion of the first UL data channel repeat in a second slot, and transmitting at least the first UL data channel repeat includes transmitting the first portion of the UCI multiplexed with the first portion of the UL data channel repeat in the FD slot, and transmitting the second portion of the UCI multiplexed with the second portion of the UL data channel repeat in the second slot.

[0241]

[0215] In some aspects, a first portion of the UCI includes hybrid automatic repeat request (HARQ) acknowledgement information and a second portion of the UCI includes channel state information (CSI) feedback.

[0242]

[0216] In some aspects, a total number of resources available for UCI in the first portion of the first UL data channel repeat is less than the number of resources available in the second portion of the first UL data channel repeat, and taking one or more actions related to multiplexing the UCI with the first UL data channel repeat includes multiplexing the UCI with the second portion of the first UL data channel repeat, and transmitting at least the first UL data channel repeat includes transmitting the UCI multiplexed with the second portion of the first UL data channel repeat in the second slot.

[0243]

[0217] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled includes a full duplex (FD) slot, and the UCI includes at least a first portion including a first type of information and a second portion including a second type of information.

[0244]

[0218] In some aspects, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat based on the FD slot in which the first portion of the first UL data channel repeat is scheduled includes omitting a second portion of the UCI including the second type of information from being multiplexed with the first portion of the first UL data channel repeat, and multiplexing the first portion of the UCI including the first type of information with the first portion of the first UL data channel repeat.

[0245]

[0219] In some aspects, the method 1300 further includes determining a number of resources available for UCI in the first portion of the first UL data channel iteration based on the adjustment factor.

[0246]

[0220] In some aspects, the adjustment factor is specific to an FD slot, including the FD slot in which the first portion of the first UL data channel iteration is scheduled, and is different from the adjustment factor associated with a non-FD slot.

[0247]

[0221] In some aspects, the adjustment factor is specific to the second type of information in the UCI and to FD slots, including the FD slot in which the first portion of the first UL data channel iteration is scheduled, and is different from the adjustment factor associated with non-FD slots and the adjustment factor associated with other types of information in the UCI.

[0248]

[0222] In some aspects, based on the adjustment factor, the number of resources available for UCI in the first portion of the first UL data channel repeat is not sufficient to transmit the second portion of the UCI in the first portion of the first UL data channel repeat, and taking one or more actions related to multiplexing the UCI with the first UL data channel repeat includes omitting the second portion of the UCI including the second type of information from being multiplexed with the first portion of the first UL data channel repeat, and multiplexing the first portion of the UCI including the first type of information with the first portion of the first UL data channel repeat.

[0249]

[0223] In some aspects, based on the adjustment factor, the number of resources available for UCI in the first portion of the first UL data channel repeat is sufficient to transmit a second portion of the UCI in the first portion of the first UL data channel repeat, and taking one or more actions related to multiplexing the UCI with the first UL data channel repeat includes multiplexing the first portion of the UCI including the first type of information and the second portion of the UCI including the second type of information with the first portion of the first UL data channel repeat.

[0250]

[0224] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled includes a full duplex (FD) slot, and taking one or more actions related to multiplexing the UCI with the first UL data channel iteration is based on one or more rules associated with latency requirements of different types of information included in the UCI.

[0251]

[0225] In some aspects, the UCI includes a first type of information associated with a first latency requirement and a second type of information associated with a second latency requirement, and the one or more rules specify that the first type of information included in the UCI associated with the first latency requirement is permitted to be multiplexed with a first portion of the first UL data channel repetition in an FD slot, and that the second type of information included in the UCI associated with the second latency requirement is not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0252]

[0226] In some aspects, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat based on one or more rules includes omitting a second type of information included in the UCI from being multiplexed with a first portion of the first UL data channel repeat in the FD slot, and multiplexing a first type of information included in the UCI with the first portion of the first UL data channel repeat in the FD slot.

[0253]

[0227] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled includes a full duplex (FD) slot, the UCI includes a first type of information, a second type of information, and a third type of information, and taking one or more actions related to multiplexing the UCI with the first UL data channel iteration is based on one or more rules associated with different types of information included in the UCI.

[0254]

[0228] In some aspects, the one or more rules specify that a first type of information included in a UCI is permitted to be multiplexed with a first portion of a first UL data channel repetition in an FD slot, and that a second type of information and a third type of information included in an associated UCI are not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0255]

[0229] In some aspects, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat based on one or more rules includes omitting the second type information and the third type information included in the UCI from being multiplexed with the first portion of the first UL data channel repeat in the FD slot, and multiplexing the first type information included in the UCI with the first portion of the first UL data channel repeat in the FD slot.

[0256]

[0230] In some aspects, the one or more rules specify that a first type of information and a second type of information included in the UCI are permitted to be multiplexed with a first portion of a first UL data channel repetition in an FD slot, and that a third type of information included in the associated UCI is not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0257]

[0231] In some aspects, taking one or more actions related to multiplexing the UCI with the first UL data channel repeat based on one or more rules includes omitting the third type of information included in the UCI from being multiplexed with the first portion of the first UL data channel repeat in the FD slot, and multiplexing the first type of information and the second type of information included in the UCI with the first portion of the first UL data channel repeat in the FD slot.

[0258] In one aspect, the method 1300, or any aspect related thereto, may be performed by an apparatus such as a communications device 1700 of Figure 17 that includes various components operable, configured, or adapted to perform the method 1300. The communications device 1700 is described in further detail below.

[0259]

[0233] It should be noted that FIG. 13 is merely one example of a method, and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0260] Exemplary Operation of a Network Entity

[0234] FIG. 14 illustrates a method 1400 of wireless communication by a network entity, such as the BS 102 of FIGS. 1 and 3, or a separate BS as described with respect to FIG.

[0261]

[0235] The method 1400 starts at 1402 by transmitting scheduling information to a user equipment (UE), the scheduling information scheduling transmission of a first full duplex (FD) slot of a plurality of uplink (UL) data channel repetitions and uplink control information (UCI) in a first FD slot of a plurality of slots, the FD slot including a UL subband for the UL transmission and a downlink (DL) subband for the DL transmission.

[0262]

[0236] The method 1400 then proceeds to step 1404, where a multiplexed transmission including the first UL Data Channel repetition and UCI is received in an FD slot.

[0263]

[0237] The method 1400 then proceeds to step 1406, where it demultiplexes the UCI from the multiplexed transmission.

[0264]

[0238] In some aspects, demultiplexing the UCI from the multiplexed transmission is based on one or more offset values ​​associated with non-FD slots of the multiple slots used to determine the number of resource elements (REs) for multiplexing the UCI in the first UL data channel iteration.

[0265] In some aspects, the method 1400 further includes determining a number of REs for multiplexing the UCI based on the one or more offset values ​​associated with the non-FD slots. In some aspects, demultiplexing the UCI from the multiplexed transmission includes demultiplexing the determined number of REs for the UCI from the multiplexed transmission.

[0266]

[0240] In some aspects, determining the number of REs for multiplexing the UCI is further based on the total number of REs associated with the UL subband of the FD slot and the bandwidth associated with the first UL data channel iteration.

[0267]

[0241] In some aspects, each of the one or more offset values ​​is associated with a different type of information in the UCI.

[0268]

[0242] In some aspects, the method 1400 further includes determining, based on a total number of REs associated with the UL subband of the FD slot and a number of REs associated with the first type of information, that a portion of the first type of information in the UCI is omitted from the multiplexed transmission when the UL subband of the FD slot does not include sufficient REs for the portion of the first type of information.

[0269]

[0243] In some aspects, demultiplexing the UCI from the multiplexed transmission is based on a first set of offset values ​​used to determine a number of resource elements (REs) for multiplexing the UCI in a first UL data channel iteration, the first set of offset values ​​being associated with FD slots and differing from a second set of offset values ​​associated with non-FD slots.

[0270]

[0244] In some aspects, the first set of offset values ​​associated with the first FD slot includes different offset values ​​for different types of information in the UCI.

[0271]

[0245] In some aspects, a first set of offset values ​​associated with an FD slot depends on the total number of resource elements (REs) of the UL subband of the FD slot, and a second set of offset values ​​associated with a non-FD slot depends on the total number of REs of the UL subband of the non-FD slot.

[0272]

[0246] In some aspects, the method 1400 further includes determining a number of REs for multiplexing the UCI based on a first set of offset values ​​associated with the FD slot, and demultiplexing the UCI from the multiplexed transmission includes demultiplexing the determined number of REs for the UCI from the multiplexed transmission.

[0273]

[0247] In some aspects, determining the number of REs for multiplexing the UCI may be further based on the total number of REs associated with the UL subband of the non-FD slot.

[0274]

[0248] In some aspects, determining the number of REs for multiplexing the UCI is further based on an adjustment factor that limits the number of REs available for the UCI in the first FD slot.

[0275]

[0249] In some aspects, the scheduling information includes a first type of configured grant transmitted to the UE via radio resource control (RRC) signaling, and the method further includes transmitting a first set of offset values ​​and a second set of offset values ​​to the UE via the RRC signaling.

[0276] In some aspects, the scheduling information includes a second type of configured grant transmitted in downlink control information (DCI) to the UE via a physical downlink control channel (PDCCH). In some aspects, the scheduling information includes a dynamic grant transmitted in downlink control information (DCI) to the UE via a physical downlink control channel (PDCCH).

[0277]

[0251] In some aspects, the DCI further includes one of the first set of offset values ​​or the second set of offset values ​​associated with non-FD slots.

[0278]

[0252] In some aspects, the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method further includes deriving the first set of offset values ​​associated with the FD slots based on the second set of offset values ​​associated with the non-FD slots and one or more rules in the wireless standard.

[0279]

[0253] In some aspects, the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method further includes transmitting the delta values ​​to the UE via radio resource control (RRC) signaling, and deriving the first set of offset values ​​associated with the FD slots by applying the delta values ​​to offset values ​​in the second set of offset values ​​associated with the non-FD slots.

[0280]

[0254] In some aspects, the DCI further includes a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0281]

[0255] In some aspects, the DCI indicates, via more than two bits, a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0282]

[0256] It should be noted that FIG. 14 is merely one example of a method, and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0283]

[0257] FIG. 15 illustrates a method 1500 of wireless communication by a network entity, such as the BS 102 of FIGS. 1 and 3, or a separate BS as described with respect to FIG.

[0284]

[0258] Method 1500 begins at 1502 with transmitting scheduling information to a user equipment (UE), the scheduling information scheduling transmission of a first uplink (UL) data channel repeat of a plurality of UL data channel repeats and uplink control information (UCI), the first UL data channel repeat being scheduled to extend across a slot boundary between a first slot of the plurality of slots and a second slot of the plurality of slots, such that a first portion of the first UL data channel repeat is scheduled to occur in the first slot and a second portion of the first UL data channel repeat is scheduled to occur in the second slot.

[0285]

[0259] The method 1500 then proceeds to step 1504, where a multiplexed transmission is received in the first slot or the second slot, the multiplexed transmission including at least the first UL Data Channel repeat and UCI.

[0286]

[0260] The method 1500 then proceeds to step 1506, where it demultiplexes the UCI from the multiplexed transmission.

[0287]

[0261] In some aspects, demultiplexing the UCI from the multiplexed transmission is based on a slot type associated with a first slot in which a first portion of a first UL data channel repetition is scheduled.

[0288] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled comprises a non-full duplex (FD) slot. In some aspects, demultiplexing the UCI from the multiplexed transmission includes demultiplexing the UCI from the multiplexed transmission based on the slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled being a non-FD slot.

[0289]

[0263] In some aspects, demultiplexing the UCI from the multiplexed transmission is further based on one or more offset values ​​associated with the non-FD slots used to determine the number of resource elements (REs) for multiplexing the UCI with the first portion of the first UL data channel repetition.

[0290]

[0264] In some aspects, demultiplexing the UCI from the multiplexed transmission further includes determining a number of REs for multiplexing the UCI based on one or more offset values ​​associated with the non-FD slot, a total number of REs associated with the UL subband of the first slot, and a bandwidth associated with the first UL data channel iteration, and demultiplexing the determined number of REs for the UCI from the multiplexed transmission.

[0291] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel repeat is scheduled comprises a full-duplex (FD) slot. In some aspects, the demultiplexing of the UCI from the multiplexed transmission is further based on at least one of a bandwidth associated with the first portion of the first UL data channel repeat or a total number of resources available in the first portion of the first UL data channel repeat for the UCI.

[0292]

[0266] In some aspects, when a bandwidth associated with a first portion of a first UL data channel repetition in an FD slot is greater than or equal to a threshold percentage of a bandwidth of a second UL data channel repetition in a non-FD slot, demultiplexing the UCI from the multiplexed transmission includes demultiplexing the UCI from the multiplexed transmission in the FD slot, and receiving the multiplexed transmission includes receiving the multiplexed transmission in the FD slot.

[0293]

[0267] In some aspects, when a bandwidth associated with a first portion of a first UL data channel iteration in an FD slot is less than a threshold percentage of a bandwidth of a second UL data channel iteration in a non-FD slot, demultiplexing the UCI from the multiplexed transmission includes demultiplexing the UCI from the multiplexed transmission in the non-FD slot, and receiving the multiplexed transmission includes receiving the multiplexed transmission in the non-FD slot.

[0294]

[0268] In some aspects, when the total number of resources available in the first portion of the first UL data channel iteration for UCI is greater than or equal to a threshold number of resources, demultiplexing the UCI from the multiplexed transmission includes demultiplexing the UCI from the multiplexed transmission in an FD slot, and receiving the multiplexed transmission includes receiving the multiplexed transmission in an FD slot.

[0295]

[0269] In some aspects, when the total number of resources available in the first portion of the first UL data channel iteration for UCI is less than a threshold number of resources, demultiplexing the UCI from the multiplexed transmission includes demultiplexing the UCI from the multiplexed transmission in an FD slot, and receiving the multiplexed transmission includes receiving the multiplexed transmission in an FD slot.

[0296]

[0270] In some aspects, when the total number of resources available in the first portion of the first UL data channel repeat for UCI is less than a threshold number of resources, demultiplexing the UCI from the multiplexed transmission includes demultiplexing a first portion of the UCI from the first portion of the first UL data channel repeat in an FD slot and demultiplexing a second portion of the UCI from the second portion of the first UL data channel repeat in a second slot, and receiving the multiplexed transmission includes receiving the first portion of the UL data channel repeat in the FD slot and receiving the second portion of the UL data channel repeat in the second slot.

[0297]

[0271] In some aspects, a first portion of the UCI includes hybrid automatic repeat request (HARQ) acknowledgement information and a second portion of the UCI includes channel state information (CSI) feedback.

[0298]

[0272] In some aspects, the first part of the UCI includes hybrid automatic repeat request (HARQ) acknowledgment information and a first part of channel state information (CSI) feedback, and the second part of the UCI includes a second part of the CSI feedback.

[0299]

[0273] In some aspects, when the total number of resources available for UCI in the first portion of the first UL data channel repeat is less than the number of resources available in the second portion of the first UL data channel repeat, demultiplexing the UCI from the multiplexed transmission includes demultiplexing the UCI from the second portion of the first UL data channel repeat, and receiving the multiplexed transmission includes receiving the multiplexed transmission in the second slot.

[0300]

[0274] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled includes a full duplex (FD) slot, and the UCI includes at least a first portion including a first type of information and a second portion including a second type of information.

[0301]

[0275] In some aspects, demultiplexing the UCI from the multiplexed transmission based on the FD slot in which the first portion of the first UL data channel repeat is scheduled includes demultiplexing a first portion of the UCI including a first type of information from the first portion of the first UL data channel repeat.

[0302]

[0276] In some aspects, the method 1500 further includes determining a number of resources available for UCI in the first portion of the first UL data channel iteration based on the adjustment factor.

[0303]

[0277] In some aspects, the adjustment factor is specific to an FD slot, including the FD slot in which the first portion of the first UL data channel iteration is scheduled, and is different from the adjustment factor associated with a non-FD slot.

[0304]

[0278] In some aspects, the adjustment factor is specific to the second type of information in the UCI and to FD slots, including the FD slot in which the first portion of the first UL data channel iteration is scheduled, and is different from the adjustment factors associated with non-FD slots and adjustment factors associated with other types of information in the UCI.

[0305]

[0279] In some aspects, based on the adjustment factor, the number of resources available for UCI in the first portion of the first UL data channel iteration is not sufficient to transmit a second portion of the UCI in the first portion of the first UL data channel iteration, and demultiplexing the UCI from the multiplexed transmission includes demultiplexing a first portion of the UCI including the first type of information from the first portion of the first UL data channel iteration.

[0306]

[0280] In some aspects, based on the adjustment factor, the number of resources available for UCI in the first portion of the first UL data channel iteration is sufficient to transmit a second portion of the UCI in the first portion of the first UL data channel iteration, and demultiplexing the UCI from the multiplexed transmission includes demultiplexing, from the first portion of the first UL data channel iteration, a first portion of the UCI including the first type of information and a second portion of the UCI including the second type of information.

[0307]

[0281] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled includes a full duplex (FD) slot, and demultiplexing the UCI from the multiplexed transmission is based on one or more rules associated with latency requirements of different types of information included in the UCI.

[0308]

[0282] In some aspects, the UCI includes a first type of information associated with a first latency requirement and a second type of information associated with a second latency requirement, and the one or more rules specify that the first type of information included in the UCI associated with the first latency requirement is permitted to be multiplexed with a first portion of the first UL data channel repetition in an FD slot, and that the second type of information included in the UCI associated with the second latency requirement is not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0309]

[0283] In some aspects, demultiplexing the UCI from the multiplexed transmission based on one or more rules includes demultiplexing a first type of information included in the UCI with a first portion of a first UL data channel repetition in the FD slot.

[0310]

[0284] In some aspects, a slot type associated with the first slot in which the first portion of the first UL data channel iteration is scheduled includes a full duplex (FD) slot, the UCI includes a first type of information, a second type of information, and a third type of information, and demultiplexing the UCI from the multiplexed transmission is based on one or more rules associated with the different types of information included in the UCI.

[0311]

[0285] In some aspects, the one or more rules specify that a first type of information included in a UCI is permitted to be multiplexed with a first portion of a first UL data channel repetition in an FD slot, and that a second type of information and a third type of information included in an associated UCI are not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0312]

[0286] In some aspects, demultiplexing the UCI from the multiplexed transmission based on one or more rules includes demultiplexing a first type of information included in the UCI from a first portion of a first UL data channel repetition in the FD slot.

[0313]

[0287] In some aspects, the one or more rules specify that a first type of information and a second type of information included in the UCI are permitted to be multiplexed with a first portion of a first UL data channel repetition in an FD slot, and that a third type of information included in the UCI is not permitted to be multiplexed with the first UL data channel repetition in an FD slot.

[0314]

[0288] In some aspects, demultiplexing the UCI from the multiplexed transmission based on one or more rules includes demultiplexing a first type of information and a second type of information included in the UCI from a first portion of a first UL data channel repetition in the FD slot.

[0315]

[0289] It should be noted that FIG. 15 is merely one example of a method, and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0316] Exemplary Communication Devices

[0290] Figure 16 illustrates an aspect of an example communications device 1600. In some aspects, the communications device 1600 is user equipment, such as the UE 104 described above with respect to Figures 1 and 3.

[0317] The communications device 1600 includes a processing system 1602 coupled to a transceiver 1608 (e.g., a transmitter and / or a receiver). The transceiver 1608 is configured to transmit and receive signals for the communications device 1600 via an antenna 1610, such as various signals as described herein. The processing system 1602 can be configured to perform processing functions for the communications device 1600, including processing signals to be received and / or transmitted by the communications device 1600.

[0318] The processing system 1602 includes one or more processors 1620. In various aspects, the one or more processors 1620 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380 as described with respect to FIG. 3. The one or more processors 1620 are coupled to a computer-readable medium / memory 1630 via a bus 1606. In some aspects, the computer-readable medium / memory 1630 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1620, cause the one or more processors 1620 to perform the method 1200 or 1300 described with respect to FIG. 12 and FIG. 13, respectively, or any aspects related thereto. It should be noted that a reference to a processor performing a function of the communication device 1600 can include one or more processors performing that function of the communication device 1600.

[0319]

[0293] In the illustrated embodiment, computer readable medium / memory 1630 stores code (e.g., executable instructions) for receiving 1631, code for multiplexing 1632, code for transmitting 1633, code for determining 1634, code for omitting 1635, code for deriving 1636, code for taking one or more actions 1637, and code for splitting 1638. Processing of codes 1631-1638 may cause communications device 1600 to perform methods 1200 or 1300 described with respect to Figures 12 and 13, respectively, or any aspect related thereto.

[0320]

[0294] The one or more processors 1620 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 1630, including a circuit for receiving 1621, a circuit for multiplexing 1622, a circuit for transmitting 1623, a circuit for determining 1624, a circuit for skipping 1625, a circuit for deriving 1626, a circuit for taking one or more actions 1627, and a circuit for dividing 1628. Processing in the circuits 1621-1628 may cause the communications device 1600 to perform the method 1200 or 1300 described with respect to Figures 12 and 13, respectively, or any aspect related thereto.

[0321] Various components of the communications device 1600 may provide means for performing the methods 1200 or 1300 described with respect to Figures 12 and 13, respectively, or any aspects related thereto. For example, the means for transmitting, sending, or outputting for transmission may include the transceiver 354 and / or antenna(s) 352 of the UE 104 shown in Figure 3, and / or the transceiver 1608 and antenna 1610 of the communications device 1600 of Figure 16. The means for receiving or obtaining may include the transceiver 354 and / or antenna(s) 352 of the UE 104 shown in Figure 3, and / or the transceiver 1608 and antenna 1610 of the communications device 1600 of Figure 16.

[0322]

[0296] Figure 17 illustrates aspects of an exemplary communications device. In some aspects, the communications device 1700 is a network entity, such as the BS 102 described above with respect to Figures 1 and 3, or a separate BS as described with respect to Figure 2.

[0323] The communications device 1700 includes a processing system 1702 coupled to a transceiver 1708 (e.g., a transmitter and / or a receiver) and / or a network interface 1712. The transceiver 1708 is configured to transmit and receive signals for the communications device 1700 via an antenna 1710, such as various signals as described herein. The network interface 1712 is configured to obtain and transmit signals for the communications device 1700 via a communications link(s), such as a backhaul link, a midhaul link, and / or a fronthaul link as described herein, such as with respect to FIG. 2. The processing system 1702 can be configured to perform processing functions for the communications device 1700, including processing signals to be received and / or transmitted by the communications device 1700.

[0324] The processing system 1702 includes one or more processors 1720. In various aspects, the one or more processors 1720 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340 as described with respect to FIG. 3. The one or more processors 1720 are coupled to a computer-readable medium / memory 1730 via a bus 1706. In some aspects, the computer-readable medium / memory 1730 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1720, cause the one or more processors 1720 to perform the method 1400 or 1500 described with respect to FIG. 14 and FIG. 15, respectively, or any aspects related thereto. It should be noted that a reference to a processor of the communication device 1700 performing a function may include one or more processors of the communication device 1700 performing the function.

[0325] In the illustrated embodiment, computer readable medium / memory 1730 stores code (e.g., executable instructions) for transmitting 1731, code for receiving 1732, code for demultiplexing 1733, code for determining 1734, and code for deriving 1735. Processing of codes 1731-1733 may cause communications device 1700 to perform methods 1400 or 1500 described with respect to Figures 14 and 15, respectively, or any aspect related thereto.

[0326]

[0300] The one or more processors 1720 include circuits configured to implement (e.g., execute) codes stored in a computer-readable medium / memory 1730, including a circuit for transmitting 1721, a circuit for receiving 1722, a circuit for demultiplexing 1723, a circuit for determining 1724, and a circuit for deriving 1725. Processing in the circuits 1721-1723 may cause the communications device 1700 to perform the method 1400 or 1500 described with respect to Figures 14 and 15, respectively, or any aspect related thereto.

[0327] Various components of the communication device 1700 may provide means for performing the method 1400 or 1500 described with respect to Figures 14 and 15, respectively, or any aspect related thereto. The means for transmitting, sending, or outputting for transmission may include the transceiver 332 and / or antenna(s) 334 of the BS 102 shown in Figure 3, and / or the transceiver 1708 and antenna 1710 of the communication device 1700 of Figure 17. The means for receiving or obtaining may include the transceiver 332 and / or antenna(s) 334 of the BS 102 shown in Figure 3, and / or the transceiver 1708 and antenna 1710 of the communication device 1700 of Figure 17.

[0328] Example clauses

[0302] Implementation examples are described in the following numbered clauses.

[0329]

[0303] Clause 1: A method of wireless communication by a user equipment (UE), comprising: receiving, from a network entity, scheduling information, the scheduling information scheduling transmission of a first UL data channel repetition of a plurality of uplink (UL) data channel repetitions and uplink control information (UCI) in a first full duplex (FD) slot of a plurality of slots, the FD slot including a UL subband for the UL transmission and a DL subband for the downlink (DL) transmission; multiplexing the first UL data channel repetition with the UCI to form a multiplexed transmission; and transmitting the multiplexed transmission in the FD slot.

[0330]

[0304] Clause 2: The method described in clause 1, wherein multiplexing the first UL data channel repetition with UCI to form a multiplexed transmission for transmission in an FD slot is based on one or more offset values ​​associated with non-FD slots among a plurality of slots, which are used to determine the number of resource elements (REs) for multiplexing the UCI in the first UL data channel repetition.

[0331]

[0305] Clause 3: The method of clause 2, further comprising determining a number of REs for multiplexing the UCI based on one or more offset values ​​associated with the non-FD slot, and wherein multiplexing the first UL data channel repetition with the UCI comprises multiplexing the determined number of REs for the UCI with the first UL data channel repetition to form a multiplexed transmission.

[0332]

[0306] Clause 4: The method described in clause 3, wherein determining the number of REs for multiplexing UCI is further based on the total number of REs associated with the UL subband of the FD slot and the bandwidth associated with the first UL data channel iteration.

[0333]

[0307] Clause 5: The method of clause 4, wherein each of the one or more offset values ​​is associated with a different type of information in the UCI.

[0334]

[0308] Clause 6: The method described in clause 5, further comprising omitting at least a portion of the first type of information in the UCI from being multiplexed with the first UL data channel repetition when the UL subband of the FD slot does not include sufficient REs for a portion of the first type of information based on the total number of REs associated with the UL subband of the FD slot and the number of REs associated with the first type of information.

[0335]

[0309] Clause 7: The method of clause 6, wherein omitting a portion of the first type of information is based on a priority level associated with the portion of the first type of information.

[0336]

[0310] Clause 8: The method of clause 1, wherein multiplexing a first UL data channel repetition with UCI to form a multiplexed transmission for transmission in an FD slot is based on a first set of offset values ​​used to determine a number of resource elements (REs) for multiplexing the UCI in the first UL data channel repetition, the first set of offset values ​​being associated with FD slots and different from a second set of offset values ​​associated with non-FD slots.

[0337]

[0311] Clause 9: The method of clause 8, wherein a first set of offset values ​​associated with the first FD slot includes different offset values ​​for different types of information in the UCI.

[0338]

[0312] Clause 10: The method described in clause 8, wherein a first set of offset values ​​associated with FD slots depends on the total number of resource elements (REs) of the UL subband of the FD slot, and a second set of offset values ​​associated with non-FD slots depends on the total number of REs of the UL subband of the non-FD slot.

[0339]

[0313] Clause 11: A method according to any one of clauses 8 to 10, further comprising determining a number of REs for multiplexing the UCI based on a first set of offset values ​​associated with the FD slot, and wherein multiplexing the first UL data channel repetition with the UCI comprises multiplexing the determined number of REs for the UCI with the first UL data channel repetition to form a multiplexed transmission.

[0340]

[0314] Clause 12: The method according to clause 11, wherein determining the number of REs for multiplexing the UCI is further based on the total number of REs associated with the UL subband of the non-FD slot.

[0341]

[0315] Clause 13: The method according to clause 11, wherein determining the number of REs for multiplexing the UCI is further based on an adjustment factor that limits the number of REs available for the UCI in the first FD slot.

[0342]

[0316] Clause 14: A method according to any one of clauses 8 to 13, wherein the scheduling information includes a configured grant of a first type received from a network entity via Radio Resource Control (RRC) signaling, and the method further includes receiving a first set of offset values ​​and a second set of offset values ​​from the network entity via RRC signaling.

[0343]

[0317] Clause 15: A method according to any one of clauses 8 to 13, wherein the scheduling information includes a configured grant of a second type received in downlink control information (DCI) via a physical downlink control channel (PDCCH) from a network entity, or the scheduling information includes a dynamic grant received in downlink control information (DCI) via the physical downlink control channel (PDCCH) from a network entity.

[0344]

[0318] Clause 16: The method of clause 15, wherein the DCI further includes one of a first set of offset values ​​or a second set of offset values ​​associated with the non-FD slots.

[0345]

[0319] Clause 17: The method described in Clause 15, wherein the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method further includes deriving the first set of offset values ​​associated with the FD slots based on the second set of offset values ​​associated with the non-FD slots and one or more rules in the wireless standard.

[0346]

[0320] Clause 18: The method described in Clause 15, wherein the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method further includes receiving delta values ​​from a network entity via Radio Resource Control (RRC) signaling, and deriving a first set of offset values ​​associated with the FD slots by applying the delta values ​​to offset values ​​in the second set of offset values ​​associated with the non-FD slots.

[0347]

[0321] Clause 19: The method of clause 15, wherein the DCI further includes a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0348]

[0322] Clause 20: The method described in clause 19, wherein the DCI indicates, via more than two bits, a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0349]

[0323] Clause 21: A method of wireless communication by a user equipment (UE), comprising: receiving from a network entity scheduling information, the scheduling information scheduling transmission of a first uplink (UL) data channel repeat of a plurality of UL data channel repeats and uplink control information (UCI), the first UL data channel repeat being scheduled to extend across a slot boundary between a first slot of the plurality of slots and a second slot of the plurality of slots, such that a first portion of the first UL data channel repeat is scheduled to occur in the first slot and a second portion of the first UL data channel repeat is scheduled to occur in the second slot; taking one or more actions related to multiplexing the UCI with the first UL data channel repeat; and transmitting at least the first UL data channel repeat based on the one or more actions related to the multiplexing.

[0350]

[0324] Clause 22: The method described in clause 21, wherein taking one or more actions related to multiplexing UCI with a first UL data channel repeat is based on a slot type associated with a first slot in which a first portion of the first UL data channel repeat is scheduled.

[0351]

[0325] Clause 23: The method of clause 22, wherein a slot type associated with a first slot in which a first portion of the first UL data channel repeat is scheduled includes a non-full duplex (FD) slot, and taking one or more actions related to multiplexing a UCI with the first UL data channel repeat includes multiplexing a UCI with the first portion of the first UL data channel repeat based on the slot type associated with the first slot in which a first portion of the first UL data channel repeat is scheduled being a non-FD slot.

[0352]

[0326] Clause 24: The method described in clause 23, wherein multiplexing the UCI with the first part of the first UL data channel repetition is further based on one or more offset values ​​associated with a non-FD slot used to determine the number of resource elements (REs) for multiplexing the UCI with the first part of the first UL data channel repetition.

[0353]

[0327] Clause 25: The method of clause 24, wherein multiplexing the UCI with the first portion of the first UL data channel repeat further includes determining a number of REs for multiplexing the UCI based on one or more offset values ​​associated with the non-FD slot, a total number of REs associated with the UL subband of the first slot, and a bandwidth associated with the first UL data channel repeat, and multiplexing the determined number of REs for the UCI with the first portion of the first UL data channel repeat.

[0354]

[0328] Clause 26: The method of clause 22, wherein a slot type associated with the first slot in which the first portion of the first UL data channel repeat is scheduled includes a full duplex (FD) slot, and taking one or more actions related to multiplexing UCI with the first UL data channel repeat is further based on at least one of a bandwidth associated with the first portion of the first UL data channel repeat or a total number of resources available in the first portion of the first UL data channel repeat for UCI.

[0355]

[0329] Clause 27: The method of clause 26, wherein when a bandwidth associated with a first portion of a first UL data channel repeat in an FD slot is greater than or equal to a threshold percentage of a bandwidth of a second UL data channel repeat in a non-FD slot, taking one or more actions related to multiplexing UCI with a first UL data channel repeat includes multiplexing UCI with the first portion of the first UL data channel repeat in the FD slot, and transmitting at least the first UL data channel repeat includes transmitting UCI multiplexed with the first portion of the UL data channel repeat in the FD slot.

[0356]

[0330] Clause 28: The method of clause 27, wherein when a bandwidth associated with a first portion of a first UL data channel repeat in an FD slot is less than a threshold percentage of a bandwidth of a second UL data channel repeat in a non-FD slot, taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes not multiplexing UCI with the first portion of the first UL data channel repeat in the FD slot, and transmitting at least the first UL data channel repeat includes transmitting the first portion of the UL data channel repeat in the FD slot without UCI.

[0357]

[0331] Clause 29: The method of clause 26, wherein when the total number of resources available in the first portion of the first UL data channel repeat for UCI is greater than or equal to a threshold number of resources, taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes multiplexing UCI with the first portion of the first UL data channel repeat in an FD slot, and transmitting at least the first UL data channel repeat includes transmitting UCI multiplexed with the first portion of the UL data channel repeat in an FD slot.

[0358]

[0332] Clause 30: The method of clause 29, wherein when the total number of resources available in the first portion of the first UL data channel repeat for UCI is less than a threshold number of resources, taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes multiplexing UCI with the first portion of the first UL data channel repeat in an FD slot, and transmitting at least the first UL data channel repeat includes transmitting UCI multiplexed with the first portion of the UL data channel repeat in an FD slot.

[0359]

[0333] Clause 31: The method of clause 29, wherein when the total number of resources available in the first part of the first UL data channel repeat for UCI is less than a threshold number of resources, taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes splitting the UCI into a first part and a second part, multiplexing the first part of the UCI with the first part of the first UL data channel repeat in an FD slot, and multiplexing the second part of the UCI with the second part of the first UL data channel repeat in a second slot, and transmitting at least the first UL data channel repeat includes transmitting the first part of the UCI multiplexed with the first part of the UL data channel repeat in the FD slot, and transmitting the second part of the UCI multiplexed with the second part of the UL data channel repeat in the second slot.

[0360]

[0334] Clause 32: The method according to clause 31, wherein a first part of the UCI includes hybrid automatic repeat request (HARQ) acknowledgement information and a second part of the UCI includes channel state information (CSI) feedback.

[0361]

[0335] Clause 33: The method described in clause 31, wherein a first part of the UCI includes hybrid automatic repeat request (HARQ) acknowledgement information and a first part of channel state information (CSI) feedback, and a second part of the UCI includes a second part of the CSI feedback.

[0362]

[0336] Clause 34: The method of clause 26, wherein when the total number of resources available in the first part of the first UL data channel repeat for UCI is less than the number of resources available in the second part of the first UL data channel repeat, taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes multiplexing UCI with the second part of the first UL data channel repeat, and transmitting at least the first UL data channel repeat includes transmitting UCI multiplexed with the second part of the first UL data channel repeat in a second slot.

[0363]

[0337] Clause 35: The method described in clause 22, wherein a slot type associated with a first slot in which a first portion of a first UL data channel iteration is scheduled includes a full duplex (FD) slot, and the UCI includes at least a first portion including a first type of information and a second portion including a second type of information.

[0364]

[0338] Clause 36: The method of clause 35, wherein taking one or more actions related to multiplexing UCI with the first UL data channel repeat based on the FD slot in which the first part of the first UL data channel repeat is scheduled includes omitting multiplexing the second part of the UCI including the second type of information with the first part of the first UL data channel repeat, and multiplexing the first part of the UCI including the first type of information with the first part of the first UL data channel repeat.

[0365]

[0339] Clause 37: The method of clause 35, further comprising determining a number of resources available for UCI in the first portion of the first UL data channel iteration based on the adjustment factor.

[0366]

[0340] Clause 38: The method described in clause 37, wherein the adjustment factor is specific to an FD slot, including the FD slot in which the first portion of the first UL data channel iteration is scheduled, and is different from the adjustment factor associated with a non-FD slot.

[0367]

[0341] Clause 39: The method described in clause 37, wherein the adjustment factor is specific to the second type of information in the UCI and to FD slots including the FD slot in which the first part of the first UL data channel iteration is scheduled, and is different from the adjustment factor associated with the non-FD slots and the adjustment factor associated with other types of information in the UCI.

[0368]

[0342] Clause 40: The method of clause 37, wherein based on an adjustment factor, the number of resources available for UCI in the first part of the first UL data channel repeat is not sufficient to transmit the second part of the UCI in the first part of the first UL data channel repeat, and taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes omitting the second part of the UCI including the second type of information from being multiplexed with the first part of the first UL data channel repeat, and multiplexing the first part of the UCI including the first type of information with the first part of the first UL data channel repeat.

[0369]

[0343] Clause 41: The method of clause 37, wherein based on the adjustment factor, the number of resources available for UCI in the first part of the first UL data channel repeat is sufficient to transmit the second part of the UCI in the first part of the first UL data channel repeat, and taking one or more actions related to multiplexing UCI with the first UL data channel repeat includes multiplexing the first part of the UCI including a first type of information and the second part of the UCI including a second type of information with the first part of the first UL data channel repeat.

[0370]

[0344] Clause 42: The method described in clause 22, wherein a slot type associated with a first slot in which a first portion of a first UL data channel iteration is scheduled comprises a full duplex (FD) slot, and taking one or more actions related to multiplexing UCI with the first UL data channel iteration is based on one or more rules associated with latency requirements of different types of information contained in the UCI.

[0371]

[0345] Clause 43: The method described in clause 42, wherein the UCI includes a first type of information associated with a first latency requirement and a second type of information associated with a second latency requirement, and one or more rules specify that the first type of information included in the UCI associated with the first latency requirement is permitted to be multiplexed with a first portion of the first UL data channel repetition in the FD slot, and that the second type of information included in the UCI associated with the second latency requirement is not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0372]

[0346] Clause 44: The method of clause 43, wherein taking one or more actions related to multiplexing the UCI with the first UL data channel repeat based on one or more rules includes omitting a second type of information included in the UCI from being multiplexed with a first portion of the first UL data channel repeat in the FD slot, and multiplexing a first type of information included in the UCI with the first portion of the first UL data channel repeat in the FD slot.

[0373]

[0347] Clause 45: The method described in clause 22, wherein a slot type associated with a first slot in which a first portion of a first UL data channel repetition is scheduled comprises a full duplex (FD) slot, the UCI comprises a first type of information, a second type of information, and a third type of information, and taking one or more actions related to multiplexing the UCI with the first UL data channel repetition is based on one or more rules associated with different types of information included in the UCI.

[0374]

[0348] Clause 46: The method described in clause 45, wherein one or more rules specify that a first type of information included in a UCI is permitted to be multiplexed with a first part of a first UL data channel repetition in an FD slot, and that a second type of information and a third type of information included in an associated UCI are not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0375]

[0349] Clause 47: The method of clause 46, wherein taking one or more actions related to multiplexing the UCI with the first UL data channel repetition based on one or more rules includes omitting the second type information and the third type information included in the UCI from being multiplexed with the first portion of the first UL data channel repetition in the FD slot, and multiplexing the first type information included in the UCI with the first portion of the first UL data channel repetition in the FD slot.

[0376]

[0350] Clause 48: The method described in clause 45, wherein one or more rules specify that a first type of information and a second type of information included in the UCI are permitted to be multiplexed with a first part of a first UL data channel repetition in an FD slot, and that a third type of information included in the UCI is not permitted to be multiplexed with the first UL data channel repetition in an FD slot.

[0377]

[0351] Clause 49: The method of clause 48, wherein taking one or more actions related to multiplexing the UCI with the first UL data channel repeat based on one or more rules includes omitting a third type of information included in the UCI from being multiplexed with a first portion of the first UL data channel repeat in the FD slot, and multiplexing the first type of information and the second type of information included in the UCI with the first portion of the first UL data channel repeat in the FD slot.

[0378]

[0352] Clause 50: A method of wireless communication by a network entity, comprising: transmitting to a user equipment (UE) scheduling information, the scheduling information scheduling transmission of a first full duplex (FD) slot of a plurality of slots, a first UL data channel iteration of a plurality of uplink (UL) data channel iterations, and uplink control information (UCI), the FD slot including a UL subband for the UL transmission and a downlink (DL) subband for the DL transmission; receiving in the FD slot a multiplexed transmission including the first UL data channel iteration and the UCI; and demultiplexing the UCI from the multiplexed transmission.

[0379]

[0353] Clause 51: The method described in clause 50, wherein demultiplexing UCI from a multiplexed transmission is based on one or more offset values ​​associated with non-FD slots among a plurality of slots used to determine the number of resource elements (REs) for multiplexing UCI in a first UL data channel repetition.

[0380]

[0354] Clause 52: The method described in clause 51, further comprising determining a number of REs for multiplexing UCI based on one or more offset values ​​associated with the non-FD slots, and demultiplexing UCI from the multiplexed transmission comprises demultiplexing the determined number of REs for UCI from the multiplexed transmission.

[0381]

[0355] Clause 53: The method described in clause 52, wherein determining the number of REs for multiplexing UCI is further based on the total number of REs associated with the UL subband of the FD slot and the bandwidth associated with the first UL data channel iteration.

[0382]

[0356] Clause 54: The method of clause 53, wherein each of the one or more offset values ​​is associated with a different type of information in the UCI.

[0383]

[0357] Clause 55: The method described in clause 54, further comprising determining, based on the total number of REs associated with the UL subband of the FD slot and the number of REs associated with the first type of information, that a portion of the first type of information in the UCI is omitted from the multiplexed transmission when the UL subband of the FD slot does not include sufficient REs for a portion of the first type of information.

[0384]

[0358] Clause 56: The method described in clause 50, wherein demultiplexing UCI from a multiplexed transmission is based on a first set of offset values ​​used to determine a number of resource elements (REs) for multiplexing UCI in a first UL data channel repetition, the first set of offset values ​​being associated with FD slots and different from a second set of offset values ​​associated with non-FD slots.

[0385]

[0359] Clause 57: The method of clause 56, wherein a first set of offset values ​​associated with the first FD slot includes different offset values ​​for different types of information in the UCI.

[0386]

[0360] Clause 58: The method described in clause 56, wherein a first set of offset values ​​associated with FD slots depends on the total number of resource elements (REs) in the UL subband of the FD slot, and a second set of offset values ​​associated with non-FD slots depends on the total number of REs in the UL subband of the non-FD slot.

[0387]

[0361] Clause 59: A method according to any one of clauses 56 to 58, further comprising determining a number of REs for multiplexing the UCI based on a first set of offset values ​​associated with the FD slot, and demultiplexing the UCI from the multiplexed transmission comprises demultiplexing the determined number of REs for the UCI from the multiplexed transmission.

[0388]

[0362] Clause 60: The method according to clause 59, wherein determining the number of REs for multiplexing the UCI is further based on a total number of REs associated with the UL subband of the non-FD slot.

[0389]

[0363] Clause 61: The method according to clause 59, wherein determining the number of REs for multiplexing the UCI is further based on an adjustment factor that limits the number of REs available for the UCI in the first FD slot.

[0390]

[0364] Clause 62: A method according to any one of clauses 56 to 61, wherein the scheduling information includes a configured grant of a first type transmitted to the UE via radio resource control (RRC) signaling, and the method further includes transmitting a first set of offset values ​​and a second set of offset values ​​to the UE via RRC signaling.

[0391]

[0365] Clause 63: A method according to any one of clauses 56 to 61, wherein the scheduling information includes a configured grant of a second type that is transmitted to the UE in downlink control information (DCI) via a physical downlink control channel (PDCCH), or the scheduling information includes a dynamic grant that is transmitted to the UE in downlink control information (DCI) via the physical downlink control channel (PDCCH).

[0392]

[0366] Clause 64: The method of clause 63, wherein the DCI further includes one of a first set of offset values ​​or a second set of offset values ​​associated with the non-FD slots.

[0393]

[0367] Clause 65: The method described in Clause 63, wherein the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method further includes deriving the first set of offset values ​​associated with the FD slots based on the second set of offset values ​​associated with the non-FD slots and one or more rules in the wireless standard.

[0394]

[0368] Clause 66: The method described in Clause 63, wherein the DCI further includes a second set of offset values ​​associated with the non-FD slots, and the method further includes transmitting the delta value to the UE via radio resource control (RRC) signaling, and deriving the first set of offset values ​​associated with the FD slots by applying the delta value to the offset values ​​in the second set of offset values ​​associated with the non-FD slots.

[0395]

[0369] Clause 67: The method of clause 63, wherein the DCI further includes a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0396]

[0370] Clause 68: The method described in clause 67, wherein the DCI indicates, via more than two bits, a first set of offset values ​​associated with FD slots and a second set of offset values ​​associated with non-FD slots.

[0397]

[0371] Clause 69: A method of wireless communication by a network entity, comprising: transmitting to a user equipment (UE) scheduling information, the scheduling information scheduling transmission of a first uplink (UL) data channel repeat of a plurality of UL data channel repeats and uplink control information (UCI), the first UL data channel repeat being scheduled to extend across a slot boundary between a first slot of the plurality of slots and a second slot of the plurality of slots, such that a first portion of the first UL data channel repeat is scheduled to occur in the first slot and a second portion of the first UL data channel repeat is scheduled to occur in the second slot; receiving in the first slot or the second slot a multiplexed transmission including at least the first UL data channel repeat and the UCI; and demultiplexing the UCI from the multiplexed transmission.

[0398]

[0372] Clause 70: The method of clause 69, wherein demultiplexing UCI from a multiplexed transmission is based on a slot type associated with a first slot in which a first portion of a first UL data channel repetition is scheduled.

[0399]

[0373] Clause 71: The method of clause 70, wherein a slot type associated with a first slot in which a first portion of a first UL data channel iteration is scheduled comprises a non-full duplex (FD) slot, and demultiplexing UCI from the multiplexed transmission includes demultiplexing UCI from the multiplexed transmission based on the slot type associated with the first slot in which a first portion of a first UL data channel iteration is scheduled being a non-FD slot.

[0400]

[0374] Clause 72: The method of clause 71, wherein demultiplexing the UCI from the multiplexed transmission is further based on one or more offset values ​​associated with non-FD slots used to determine the number of resource elements (REs) for multiplexing the UCI with the first portion of the first UL data channel repetition.

[0401]

[0375] Clause 73: The method of clause 72, wherein demultiplexing UCI from the multiplexed transmission further includes determining a number of REs for multiplexing UCI based on one or more offset values ​​associated with the non-FD slot, a total number of REs associated with the UL subband of the first slot, and a bandwidth associated with the first UL data channel iteration, and demultiplexing the determined number of REs for UCI from the multiplexed transmission.

[0402]

[0376] Clause 74: The method of clause 70, wherein a slot type associated with the first slot in which the first portion of the first UL data channel repeat is scheduled comprises a full duplex (FD) slot, and demultiplexing the UCI from the multiplexed transmission is further based on at least one of a bandwidth associated with the first portion of the first UL data channel repeat or a total number of resources available in the first portion of the first UL data channel repeat for UCI.

[0403]

[0377] Clause 75: The method described in clause 74, wherein when a bandwidth associated with a first portion of a first UL data channel repetition in an FD slot is greater than or equal to a threshold percentage of a bandwidth of a second UL data channel repetition in a non-FD slot, demultiplexing UCI from a multiplexed transmission includes demultiplexing UCI from a multiplexed transmission in an FD slot, and receiving a multiplexed transmission includes receiving a multiplexed transmission in an FD slot.

[0404]

[0378] Clause 76: The method of clause 75, wherein when a bandwidth associated with a first portion of a first UL data channel repetition in an FD slot is less than a threshold percentage of a bandwidth of a second UL data channel repetition in a non-FD slot, demultiplexing UCI from a multiplexed transmission includes demultiplexing UCI from a multiplexed transmission in a non-FD slot, and receiving a multiplexed transmission includes receiving a multiplexed transmission in a non-FD slot.

[0405]

[0379] Clause 77: The method described in Clause 74, wherein when the total number of resources available in the first portion of the first UL data channel iteration for UCI is greater than or equal to a threshold number of resources, demultiplexing UCI from the multiplexed transmission includes demultiplexing UCI from the multiplexed transmission in an FD slot, and receiving the multiplexed transmission includes receiving the multiplexed transmission in an FD slot.

[0406]

[0380] Clause 78: The method described in Clause 77, wherein when the total number of resources available in the first portion of the first UL data channel iteration for UCI is less than a threshold number of resources, demultiplexing UCI from the multiplexed transmission includes demultiplexing UCI from the multiplexed transmission in an FD slot, and receiving the multiplexed transmission includes receiving the multiplexed transmission in an FD slot.

[0407]

[0381] Clause 79: The method of clause 77, wherein when the total number of resources available in the first part of the first UL data channel repeat for UCI is less than a threshold number of resources, demultiplexing the UCI from the multiplexed transmission includes demultiplexing a first part of the UCI from the first part of the first UL data channel repeat in an FD slot and demultiplexing a second part of the UCI from the second part of the first UL data channel repeat in a second slot, and receiving the multiplexed transmission includes receiving the first part of the UL data channel repeat in the FD slot and receiving the second part of the UL data channel repeat in the second slot.

[0408]

[0382] Clause 80: The method according to clause 79, wherein a first part of the UCI includes hybrid automatic repeat request (HARQ) acknowledgement information and a second part of the UCI includes channel state information (CSI) feedback.

[0409]

[0383] Clause 81: The method described in clause 79, wherein a first part of the UCI includes hybrid automatic repeat request (HARQ) acknowledgement information and a first part of channel state information (CSI) feedback, and a second part of the UCI includes a second part of the CSI feedback.

[0410]

[0384] Clause 82: The method described in Clause 74, wherein when the total number of resources available in the first portion of the first UL data channel repeat for UCI is less than the number of resources available in the second portion of the first UL data channel repeat, demultiplexing UCI from the multiplexed transmission includes demultiplexing UCI from the second portion of the first UL data channel repeat, and receiving the multiplexed transmission includes receiving the multiplexed transmission in the second slot.

[0411]

[0385] Clause 83: The method of clause 70, wherein a slot type associated with a first slot in which a first portion of a first UL data channel iteration is scheduled includes a full duplex (FD) slot, and the UCI includes at least a first portion including a first type of information and a second portion including a second type of information.

[0412]

[0386] Clause 84: The method described in clause 83, wherein demultiplexing UCI from a multiplexed transmission based on the FD slot in which the first portion of the first UL data channel repetition is scheduled includes demultiplexing a first portion of UCI including a first type of information from the first portion of the first UL data channel repetition.

[0413]

[0387] Clause 85: The method of clause 83, further comprising determining a number of resources available for UCI in the first portion of the first UL data channel iteration based on the adjustment factor.

[0414]

[0388] Clause 86: The method described in clause 85, wherein the adjustment factor is specific to an FD slot, including an FD slot in which the first portion of the first UL data channel iteration is scheduled, and is different from the adjustment factor associated with a non-FD slot.

[0415]

[0389] Clause 87: The method described in clause 85, wherein the adjustment factor is specific to the second type of information in the UCI and to FD slots including the FD slot in which the first part of the first UL data channel iteration is scheduled, and is different from the adjustment factor associated with the non-FD slots and the adjustment factor associated with other types of information in the UCI.

[0416]

[0390] Clause 88: The method of clause 85, wherein based on an adjustment factor, the number of resources available for UCI in the first part of the first UL data channel repetition is not sufficient to transmit a second part of UCI in the first part of the first UL data channel repetition, and demultiplexing UCI from the multiplexed transmission includes demultiplexing a first part of UCI including a first type of information from the first part of the first UL data channel repetition.

[0417]

[0391] Clause 89: The method of clause 85, wherein based on an adjustment factor, the number of resources available for UCI in the first part of the first UL data channel repeat is sufficient to transmit a second part of UCI in the first part of the first UL data channel repeat, and demultiplexing the UCI from the multiplexed transmission includes demultiplexing a first part of UCI including a first type of information and a second part of UCI including a second type of information from the first part of the first UL data channel repeat.

[0418]

[0392] Clause 90: The method described in Clause 70, wherein a slot type associated with a first slot in which a first portion of a first UL data channel iteration is scheduled comprises a full duplex (FD) slot, and demultiplexing of the UCI from the multiplexed transmission is based on one or more rules associated with latency requirements of different types of information contained in the UCI.

[0419]

[0393] Clause 91: The method described in Clause 90, wherein the UCI includes a first type of information associated with a first latency requirement and a second type of information associated with a second latency requirement, and one or more rules specify that the first type of information included in the UCI associated with the first latency requirement is permitted to be multiplexed with a first portion of the first UL data channel repetition in the FD slot, and that the second type of information included in the UCI associated with the second latency requirement is not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0420]

[0394] Clause 92: The method described in clause 91, wherein demultiplexing UCI from a multiplexed transmission based on one or more rules includes demultiplexing a first type of information contained in the UCI using a first portion of a first UL data channel repetition in the FD slot.

[0421]

[0395] Clause 93: The method described in clause 70, wherein a slot type associated with a first slot in which a first portion of a first UL data channel iteration is scheduled comprises a full duplex (FD) slot, the UCI comprises a first type of information, a second type of information, and a third type of information, and demultiplexing of the UCI from the multiplexed transmission is based on one or more rules associated with different types of information included in the UCI.

[0422]

[0396] Clause 94: The method described in clause 93, wherein one or more rules specify that a first type of information included in a UCI is permitted to be multiplexed with a first part of a first UL data channel repetition in an FD slot, and that a second type of information and a third type of information included in an associated UCI are not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0423]

[0397] Clause 95: The method described in clause 94, wherein demultiplexing UCI from a multiplexed transmission based on one or more rules includes demultiplexing a first type of information contained in the UCI from a first portion of a first UL data channel repetition in an FD slot.

[0424]

[0398] Clause 96: The method described in clause 93, wherein one or more rules specify that a first type of information and a second type of information included in the UCI are permitted to be multiplexed with a first part of a first UL data channel repetition in an FD slot, and that a third type of information included in the UCI is not permitted to be multiplexed with the first UL data channel repetition in the FD slot.

[0425]

[0399] Clause 97: The method described in clause 96, wherein demultiplexing UCI from a multiplexed transmission based on one or more rules includes demultiplexing a first type of information and a second type of information contained in the UCI from a first portion of a first UL data channel repetition in an FD slot.

[0426]

[0400] Clause 98: An apparatus comprising: a memory having executable instructions; and a processor configured to execute the executable instructions to cause the apparatus to perform a method according to any one of clauses 1 to 97.

[0427]

[0401] Clause 99: An apparatus comprising means for carrying out the method described in any one of clauses 1 to 97.

[0428]

[0402] Clause 100: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of the device, cause the device to perform a method according to any one of clauses 1 to 97.

[0429]

[0403] Clause 101: A computer program product embodied on a computer-readable storage medium comprising code for performing the method according to any one of clauses 1 to 97.

[0430] Additional Considerations

[0404] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The embodiments described herein are not intended to limit the scope, applicability, or aspects described in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of the elements described without departing from the scope of the disclosure. Various embodiments may omit, substitute, or add various steps or components as appropriate. For example, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some embodiments may be combined in some other embodiments. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. Furthermore, the scope of the disclosure is intended to encompass apparatuses or methods that are implemented using other structures, functions, or structures and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0431]

[0405] The various example logic blocks, modules, and circuits described in connection with this disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0432]

[0406] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. By way of example, "at least one of a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).

[0433]

[0407] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, electing, establishing, and the like.

[0434]

[0408] The methods disclosed herein include one or more actions for achieving the method. The actions of the methods may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Furthermore, various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. These means may include various hardware and / or software component(s) including, but not limited to, circuits, application specific integrated circuits (ASICs), or processors, and / or various hardware and / or software module(s).

[0435]

[0409] The following claims are not intended to be limited to the embodiments set forth herein, but are to be accorded the full scope consistent with the language of the claims. Within the claims, reference to an element by the singular is not intended to mean "only one" unless expressly stated as such, but rather "one or more." Unless otherwise expressly stated, the term "several" refers to one or more. Claim elements are not to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase "means for." All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims.

Claims

1. 1. A method of wireless communication by a user equipment (UE), comprising: from a network entity, scheduling information; the scheduling information schedules transmission of a plurality of uplink (UL) data channel repetitions in a plurality of slots, including a full duplex (FD) slot; the scheduling information schedules a first UL data channel repetition of the plurality of UL data channel repetitions and uplink control information (UCI) in the FD slot; the FD slot includes a UL subband for UL transmission and a downlink (DL) subband for DL ​​transmission; receiving scheduling information; multiplexing the first UL data channel repetition with the UCI in a Physical Uplink Shared Channel (PUSCH) to form a multiplexed transmission, wherein the multiplexing of the first UL data channel repetition with the UCI to form the multiplexed transmission for transmission in the FD slot is based on one or more offset values ​​associated with non-FD slots of the plurality of slots that are used to determine a number of resource elements (REs) for carrying the UCI in the PUSCH, the one or more offset values ​​each representing a maximum percentage of REs allocated for PUSCH that can be utilized to carry the UCI in the PUSCH; transmitting the multiplexed transmission in the FD slot; A method comprising:

2. 2. The method of claim 1, further comprising: determining the number of REs for multiplexing the UCI based on the one or more offset values ​​associated with the non-FD slot; and wherein multiplexing the first UL data channel repetition with the UCI comprises multiplexing the determined number of REs for the UCI with the first UL data channel repetition to form the multiplexed transmission.

3. 3. The method of claim 2, wherein determining the number of REs for multiplexing the UCI is further based on a total number of REs associated with the UL subband of the FD slot and a bandwidth associated with the first UL data channel repetition.

4. The method of claim 3 , wherein each of the one or more offset values ​​is associated with a different type of information in the UCI.

5. 5. The method of claim 4, further comprising: omitting at least the portion of the first type of information in the UCI from being multiplexed with the first UL data channel repetition when the UL subband of the FD slot does not include enough REs for a portion of the first type of information based on the total number of REs associated with the UL subband of the FD slot and a number of REs associated with first type information.

6. The method of claim 5 , wherein omitting the portion of the first type of information is based on a priority level associated with the portion of the first type of information.

7. An apparatus for wireless communication by a user equipment (UE), comprising: a memory having executable instructions; Executing the executable instructions to cause the UE to: from a network entity, scheduling information; the scheduling information schedules transmission of a plurality of uplink (UL) data channel repetitions in a plurality of slots, including a full duplex (FD) slot; the scheduling information schedules a first UL data channel repetition of the plurality of UL data channel repetitions and uplink control information (UCI) in the FD slot; the FD slot includes a UL subband for UL transmission and a downlink (DL) subband for DL ​​transmission; receiving scheduling information; multiplexing the first UL data channel repetition with the UCI on a physical uplink shared channel (PUSCH) to form a multiplexed transmission; transmitting the multiplexed transmission in the FD slot; one or more processors individually or collectively configured as follows: wherein the one or more processors are individually or collectively configured to cause the UE to multiplex the first UL data channel repetition with the UCI to form the multiplexed transmission for transmission in the FD slot(s) based on one or more offset values ​​associated with non-FD slots of the plurality of slots used to determine a number of resource elements (REs) for carrying the UCI in the PUSCH, the one or more offset values ​​each representing a maximum percentage of REs allocated for PUSCH that may be utilized to carry the UCI in the PUSCH.

8. the one or more processors are further configured, individually or collectively, to cause the UE to determine the number of REs for multiplexing the UCI based on the one or more offset values ​​associated with the non-FD slot; to multiplex the first UL data channel repetition with the UCI, the one or more processors are further configured, individually or collectively, to cause the UE to multiplex the determined number of REs for the UCI with the first UL data channel repetition to form the multiplexed transmission.

8. The apparatus of claim 7.

9. 9. The apparatus of claim 8, wherein the one or more processors are individually or collectively configured to cause the UE to determine the number of REs for multiplexing the UCI further based on a total number of REs associated with the UL subband of the FD slot and a bandwidth associated with the first UL data channel iteration.

10. The method of claim 9, wherein each of the one or more offset values ​​is associated with a different type of information in the UCI.

11. The method of claim 10, wherein the one or more processors are further configured, individually or collectively, to cause the UE to omit multiplexing at least the portion of the first type of information in the UCI with the first UL data channel iteration when the UL subband of the FD slot does not contain sufficient REs for a portion of the first type of information based on the total number of REs associated with the UL subband of the FD slot and the number of REs associated with first type information.

12. The method of claim 11, wherein the one or more processors are further configured, individually or collectively, to cause the UE to omit the portion of the first type of information based on a priority level associated with the portion of the first type of information.

13. A computer-readable medium comprising processor-executable instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to perform a method according to any one of claims 1 to 6.

14. A method of wireless communication by a network entity, comprising: A user equipment (UE) is provided with scheduling information, the scheduling information schedules transmission of a plurality of uplink (UL) data channel repetitions in a plurality of slots, including a full duplex (FD) slot; the scheduling information schedules a first UL data channel repetition of the plurality of UL data channel repetitions and uplink control information (UCI) in the FD slot; the FD slot includes a UL subband for UL transmission and a downlink (DL) subband for DL ​​transmission; transmitting scheduling information; receiving a multiplexed transmission in the FD slot, the multiplexed transmission comprising the first UL Data Channel repetition and the UCI on a Physical Uplink Shared Channel (PUSCH); demultiplexing the UCI from the multiplexed transmission based on one or more offset values ​​associated with non-FD slots among the plurality of slots used to determine a number of resource elements (REs) for carrying the UCI in the PUSCH, the one or more offset values ​​each representing a maximum percentage of REs allocated for the PUSCH that can be utilized to carry the UCI in the PUSCH; A method comprising:

15. An apparatus for wireless communication by a network entity, comprising: a memory having executable instructions; Executing the executable instructions to cause the network entity to: A user equipment (UE) is provided with scheduling information, the scheduling information schedules transmission of a plurality of uplink (UL) data channel repetitions in a plurality of slots, including a full duplex (FD) slot; the scheduling information schedules a first UL data channel repetition of the plurality of UL data channel repetitions and uplink control information (UCI) in the FD slot; the FD slot includes a UL subband for UL transmission and a downlink (DL) subband for DL ​​transmission; Send scheduling information; receiving a multiplexed transmission in the FD slot, wherein the multiplexed transmission comprises the first UL Data Channel repetition and the UCI on a Physical Uplink Shared Channel (PUSCH); demultiplexing the UCI from the multiplexed transmission; one or more processors individually or collectively configured as follows: wherein the one or more processors are individually or collectively configured to cause the network entity to demultiplex the UCI from the multiplexed transmission based on one or more offset values ​​associated with non-FD slots among the plurality of slots that are used to determine a number of resource elements (REs) for carrying the UCI in the PUSCH, the one or more offset values ​​each representing a maximum percentage of REs allocated for the PUSCH that can be utilized to carry the UCI in the PUSCH.

Images