Resource muting for uplink transmissions

Abstract

A user equipment (UE) operating in a new radio (NR) network may be configured for transmission of a physical uplink shared channel (PUSCH) with uplink (UL) resource muting via a PUSCH configuration (PUSCH-Config) information element that indicates a muting resource. A downlink configuration information (DCI) format scheduling the PUSCH may include an uplink muting indicator that indicates that muting is to be applied to the scheduled PUSCH. The UE may apply UL resource muting to the scheduled PUSCH in accordance with the PUSCH-Config and the uplink muting indicator. UL resource muting may be applied in one or two symbols of the muting resource. When a symbol is muted in the even numbered subcarriers, the muted symbol on the even numbered subcarriers is not used in the PUSCH. When the symbol is muted in the odd numbered subcarriers, the muted symbol on the odd numbered subcarriers is not used in the PUSCH.

Description

AG2532-PCT 1884.Q72WO1 RESOURCE MUTING FOR UPLINK TRANSMISSIONS PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No.63 / 675,110, filed July 24, 2024 [reference number AG2532-Z] which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks. Some embodiments relate to sixth-generation (6G) networks. BACKGROUND

[0003] Mobile communications have evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. With the increase in different types of devices communicating with various network devices, usage of 3GPP 5G NR systems has increased. The penetration of mobile devices (user equipment or UEs) in modern society has continued to drive demand for a wide variety of networked devices in many disparate environments.5G NR wireless systems are forthcoming and are expected to enable even greater speed, connectivity, and usability, and are expected to increase throughput, coverage, and robustness and reduce latency and operational and capital expenditures.5G-NR networks will continue to evolve based on 3GPP LTE-Advanced with additional potential new radioAG2532-PCT 1884.Q72WO1 access technologies (RATs) to enrich people’s lives with seamless wireless connectivity solutions delivering fast, rich content and services. As current cellular network frequency is saturated, higher frequencies, such as millimeter wave (mmWave) frequency, can be beneficial due to their high bandwidth. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG.1 illustrates an architecture of a network, in accordance with some embodiments.

[0005] FIG.2 illustrates an example of cross-link interference for a dynamic Time Division Duplex (TDD) system, in accordance with some embodiments.

[0006] FIG.3 illustrates a procedure for UCI multiplexing on a physical uplink shared channel (PUSCH) with muting resources, in accordance with some embodiments.

[0007] FIG.4 illustrates an example of collision handling between a physical uplink control channel (PUCCH) and a PUSCH with muting resources, in accordance with some embodiments.

[0008] FIG.5 illustrates an example of a resource block configured with muting resources, in accordance with some embodiments.

[0009] FIG.6 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments. DETAILED DESCRIPTION

[0010] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.AG2532-PCT 1884.Q72WO1

[0011] Embodiments are directed to a user equipment (UE) that may operate in a new radio (NR) network. The UE may be configured for transmission of a physical uplink shared channel (PUSCH) with uplink (UL) resource muting via a PUSCH configuration (PUSCH-Config) information element that indicates a muting resource. A downlink configuration information (DCI) format scheduling the PUSCH may include an uplink muting indicator that indicates that muting is to be applied to the scheduled PUSCH. The UE may apply UL resource muting to the scheduled PUSCH in accordance with the PUSCH-Config and the uplink muting indicator. UL resource muting may be applied in one or two symbols of the muting resource. When a symbol is muted in the even numbered subcarriers, the muted symbol on the even numbered subcarriers is not used in the PUSCH. When the symbol is muted in the odd numbered subcarriers, the muted symbol on the odd numbered subcarriers is not used in the PUSCH. These embodiments, as well as others, are described in more detail below.

[0012] FIG.1 illustrates an architecture of a network in accordance with some embodiments. The network 140A is shown to include user equipment (UE) 101 and UE 102. The UE 101 and UE 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and / or wireless communications interface. The UE 101 and UE 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0013] Any of the radio links described herein (e.g., as used in the network 140A or any other illustrated network) may operate according to any exemplary radio communication technology and / or standard.

[0014] LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE- Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing theAG2532-PCT 1884.Q72WO1 bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

[0015] Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).

[0016] Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0017] In some embodiments, any of the UE 101 and UE 102 can comprise an Internet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some embodiments, any of the UE 101 and UE 102 can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

[0018] In some embodiments, any of the UE 101 and UE 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.AG2532-PCT 1884.Q72WO1

[0019] The UE 101 and UE 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UE 101 and UE 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0020] In an aspect, the UE 101 and UE 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0021] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0022] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g.,AG2532-PCT 1884.Q72WO1 terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some embodiments, the RAN nodes 111 and 112 can be transmission / reception points (TRPs). In instances when the RAN nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro-RAN node, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node.

[0023] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UE 101 and UE 102. In some embodiments, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the RAN nodes 111 and / or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.

[0024] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an S1 interface 113. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this aspect, the S1 interface 113 is split into two parts: the S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the S1-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0025] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-relatedAG2532-PCT 1884.Q72WO1 information to support the network entities handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0026] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0027] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 and UE 102 via the CN 120.

[0028] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-AG2532-PCT 1884.Q72WO1 CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.

[0029] In some embodiments, the communication network 140A can be an IoT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is the narrowband-IoT (NB-IoT).

[0030] An NG system architecture can include the RAN 110 and a 5G network core (5GC). In these embodiments, the RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network or 5GC) can include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG- C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

[0031] In some embodiments, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some embodiments, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture. In some embodiments, any of the UEs or base stations described in connection with FIG.1 can be configured to perform the functionalities described herein.

[0032] Some embodiments relate to PUSCH resource muting in a 5G NR (New Radio) network. In these embodiments, certain time-frequency resources allocated for the Physical Uplink Shared Channel (PUSCH) are intentionally not used for transmission by the UE. One reason for PUSCH resource muting is to avoid interference with other signals or channels that might be transmitted in the same time-frequency resources. For example, if a neighboring cell is using certain resources for critical control signaling, mutingAG2532-PCT 1884.Q72WO1 those resources in the PUSCH allocation prevents interference. In some embodiments, the muting pattern may be signaled to the UE through higher layer signaling or can be semi-statically configured. When resources are muted, the UE doesn't transmit on those specific resource elements (REs) within its allocated PUSCH transmission, creating holes in the transmission pattern. This is unlike rate matching, where the data is adapted to fit around unavailable resources. With muting, the resources are allocated but then selectively not used.

[0033] In some embodiments, a UE, such as UE 101 or UE 102, may be configured for transmission of a PUSCH with uplink (UL) resource muting. In these embodiments, the UE may decode radio resource control (RRC) signalling comprising a physical uplink shared channel (PUSCH) configuration information element (PUSCH-Config) for a PUSCH with uplink (UL) resource muting. The PUSCH-Config may indicate the muting resource. The UE may also decode a downlink configuration information (DCI) format scheduling the PUSCH. The DCI format may include an uplink muting indicator that indicates muting is to be applied to the scheduled PUSCH. In these embodiments, the UE may apply UL resource muting to the scheduled PUSCH in accordance with the PUSCH-Config and the uplink muting indicator.

[0034] In these embodiments, the UE may apply UL resource muting in one or two symbols of the muting resource. When the UL resource muting is applied in a symbol, the symbol is muted in either even numbered subcarriers or odd numbered subcarriers. When the symbol is muted in the even numbered subcarriers, the muted symbol on the even numbered subcarriers is not used in the PUSCH. When the symbol is muted in the odd numbered subcarriers, the muted symbol on the odd numbered subcarriers is not used in the PUSCH. These embodiments are discussed in more detail below.

[0035] FIG.2 illustrates an example of cross-link interference for a dynamic Time Division Duplex (TDD) system, in accordance with some embodiments. TDD is now widely used in commercial NR deployments, where the time domain resource is split between downlink and uplink symbols. In NR, TDD UL / DL configuration can be semi-statically configured by gNB via tdd- UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. In addition, dynamic TDD was introduced in the NR. In this case, gNB mayAG2532-PCT 1884.Q72WO1 dynamically allocate UL and DL resources in order to match the instantaneous traffic conditions for UL and DL transmissions, respectively, which can help in maximizing resource utilization and improving the UE throughput. However, without coordination between gNBs, certain cross link interference (CLI) may occur in dynamic TDD systems, especially when considering that two gNBs from different operators are transmitting in the same frequency band.

[0036] Because of the different transmission directions among neighboring gNB at a given time, two types of CLI can be observed under dynamic TDD operation: UE-to-UE interference 222 and gNB-to-gNB interference 224. For UE-to-UE interference 222, CLI arises when a DL transmission 214 of a serving gNB interferes with the UL transmission 212 of a UE from neighboring gNB. Furthermore, for gNB-to-gNB interference 224, CLI is generated when a DL transmission 214 of a neighboring gNB interferes with the UL transmission 212 of a UE from a serving gNB.

[0037] For gNB-to-gNB interference, some resource elements (RE) in the allocated physical uplink shared channel (PUSCH) may be muted so as to allow the gNB to estimate the covariance matrix of cross link interference based on the muted REs in the UL resources. When minimum mean square error- interference rejection combining (MMSE-IRC) receiver is employed at the gNB, the gNB-to-gNB interference can be mitigated, thereby improving the uplink performance.

[0038] For resource muting for uplink transmission, rate-matching is performed for the PUSCH transmission around the muted resources. In this case, when uplink control information (UCI) is multiplexed on PUSCH, certain mechanisms may need to be defined to determine the number of resources for UCI transmissions on PUSCH.

[0039] Embodiments disclosed herein are directed to resource muting for uplink transmissions. Some of these embodiments are directed to UCI resource determination for uplink resource muting and PUSCH transmission with uplink resource muting in case of cancellation indication (CI). These embodiments are disclosed in more detail herein.

[0040] UCI resource determination for uplink resource mutingAG2532-PCT 1884.Q72WO1

[0041] As mentioned above, for gNB-to-gNB interference, some resource elements (RE) in the allocated physical uplink shared channel (PUSCH) may be muted so as to allow the gNB to estimate the covariance matrix of cross link interference based on the muted REs in the UL resources. When minimum mean square error-interference rejection combining (MMSE-IRC) receiver is employed at the gNB receiver, the impact on gNB-to-gNB interference can be reduced, thereby improving the uplink performance.

[0042] For resource muting for uplink transmission, rate-matching is performed for the PUSCH transmission around the muted resources. In this case, when uplink control information (UCI) is multiplexed on PUSCH, certain mechanisms may need to be defined to determine the amount of resources for UCI transmissions on PUSCH.

[0043] Embodiments of UCI resource determination for uplink resource muting are provided as follows:

[0044] In some embodiments, a UE may be configured by higher layers (e.g., via dedicated RRC signalling) to apply PUSCH resource muting for a PUSCH that may overlap with configured or indicated resources for muting. In some embodiments, the UE may be configured to apply PUSCH resource muting on a per UL BWP basis. Alternatively, the UE may be configured to apply PUSCH resource muting on a per UL carrier basis.

[0045] In some embodiments, a set of resource elements (RE) in time and frequency domain may be configured for the muting resource for uplink transmission by higher layers via radio resource control (RRC) signalling or dynamically indicated in the downlink control information (DCI) or a combination thereof.

[0046] In some embodiments, more than one set of REs in time and / or frequency domain may be configured by RRC signalling, where one field in the DCI may be used to indicate one set from the more than one set of REs for the muting resources. In some embodiments, as a further extension, the resources that are allocated for physical random access channel (PRACH) occasions and / or MsgA physical uplink shared channel (PUSCH) occasions for 2-step RACH may be defined as a default muting resource for other uplink channels / signals.AG2532-PCT 1884.Q72WO1

[0047] In some embodiments, when a PUSCH transmission and / or a physical uplink control channel (PUCCH) transmission overlaps with the muting resource in the time and frequency domain, UE does not transmit the PUSCH or PUCCH on the muted resource in the time and frequency, respectively.

[0048] In some embodiments, when a PUCCH transmission overlaps with the muting resource in the time and frequency domain, UE may ignore the muting resource and transmit the PUCCH in accordance with the configured or allocated resource. In one alternative, the overlap of PUCCH with the muting resource is checked before multiplexing of PUCCH and PUSCH, if any. In another alternative, the overlap of PUCCH with the muting resource is checked after resolving the overlapping for of PUCCH and PUSCH, if any.

[0049] In some embodiments, when a sounding reference signal (SRS) transmission overlaps with the muting resource in the time and frequency domain, UE does not transmit the SRS on the muted resource in the time and frequency. In some embodiments, when an SRS transmission overlaps with the muting resources in the time and frequency domain, UE cancels the SRS transmission in the overlapped symbols. Yet In some embodiments, when an SRS transmission overlaps with the muting resource in the time and frequency domain, UE may ignore the muting resource and transmit the SRS in accordance with the configured or allocated resource.

[0050] In some embodiments, in the time domain, a set of symbols in a slot and / or a set of slots in a frame may be configured for the muting resources. In some embodiments, the symbol index or a bitmap on the symbol index in a slot or start and length indicator value (SLIV) for the indication of symbol index in a slot may be configured for indicating the muting resource in the time domain.

[0051] In these embodiments, when a bitmap is used for muting resource indication, the length of the bitmap is the number of symbols in a slot. In one example, for a slot with 14 symbols, bitmap with length of 14 may be configured to indicate the symbol index for the muting resource, where bit “0” in the bitmap may be used to indicate that the symbol in the slot is not muted, while bit “1” in the bitmap may be used to indicate that the symbol in the slot is muted. For the case of normal cyclic prefix (NCP), the bitmap of length 14 symbols may beAG2532-PCT 1884.Q72WO1 used and for the case of extended cyclic prefix (ECP), the bitmap of length 12 symbols may be used.

[0052] In some embodiments, a slot offset with respect to a predefined frame and / or subframe index, e.g., System Frame Number (SFN) #0 of the serving cell, and a periodicity may be configured for the muting resource in the time domain. In some embodiments, a bitmap on the slot index in a frame or a TDD configuration periodicity may be configured for the muting resource in the time domain. In this case, the length of the bitmap may be determined as the number of slots in a frame or a TDD configuration periodicity.

[0053] In some embodiments, in the time domain, one or more symbol index(es) may be provided to the UE for PUSCH resource muting via higher layer configuration (e.g., dedicated RRC signalling) and / or indicated via a combination of higher layer configuration and dynamic indication, where the symbol index(es) are defined with respect to the time domain resource allocation (TDRA) of a scheduled or configured PUSCH that is identified as impacted by UL resource muting. In this case, a UE may first determine a PUSCH as impacted by UL resource muting and subsequently, apply rate-matching around the muting resources in the symbols with index(es) with respect to the starting symbol of the PUSCH. In some embodiments, a PUSCH may be identified as impacted by UL resource muting if it occurs in a slot that is identified to have UL muting resources for PUSCH. The identification of the slots with UL muting resources for PUSCH may be achieved via higher layer signalling (e.g., dedicated RRC signalling) using one or more of: bitmap over a number of slots and / or subframes and / or radio frames, or a slot-offset and periodicity with respect to a SFN #0 of the serving cell. In some of these embodiments, a PUSCH may be identified as impacted by UL resource muting based on indication in the scheduling DCI format or the DCI format activating a Type 2 CG PUSCH or as configured for Type 1 or Type 2 configured PUSCH.

[0054] In some embodiments, in the time domain, one or more symbol index(es) for PUSCH resource muting is / are provided to a UE separately for PUSCH mapping Types A and B respectively. Further, for PUSCH mapping Type A, the one or more symbol index(es) for PUSCH resource muting is / are identified with respect to the slot boundary. For PUSCH mapping Type B, theAG2532-PCT 1884.Q72WO1 one or more symbol index(es) for PUSCH resource muting is / are identified with respect to the starting symbol of a scheduled or configured PUSCH. In this case, a UE may first determine a PUSCH as impacted by UL resource muting and subsequently, apply rate-matching around the muting resources in the symbols with index(es) with respect to the starting symbol of the slot if the PUSCH is with mapping type A and with respect to starting symbol of the PUSCH if the PUSCH is with mapping type B. In some embodiments, a PUSCH may be identified as impacted by UL resource muting if it occurs in a slot that is identified to have UL muting resources for PUSCH. The identification of the slots with UL muting resources for PUSCH may be achieved via higher layer signalling (e.g., dedicated RRC signalling) using one or more of: bitmap over a number of slots and / or subframes and / or radio frames, or a slot-offset and periodicity with respect to a SFN #0 of the serving cell. In some of these embodiments, a PUSCH may be identified as impacted by UL resource muting based on indication in the scheduling DCI format or the DCI format activating a Type 2 CG PUSCH or as configured for Type 1 or Type 2 configured PUSCH.

[0055] In some embodiments, for PUSCH with mapping type B, in case multiple PUSCHs with mapping type B are scheduled and / or configured within a slot, a UE may be configured and / or indicated to apply resource muting to all the affected PUSCHs in the slot. Alternatively, in case multiple PUSCHs are scheduled and / or configured within a slot, a maximum of the first k PUSCHs in the slot may be impacted by muting resources, where the value of k may be specified or determined as part of UE capability. In some embodiments, k = 1.

[0056] In some embodiments, for a PUSCH with mapping type B that is impacted by UL resource muting, a UE may not expect to be provided with an UL muting resource corresponding to the first symbol of the PUSCH. In some embodiments, for a PUSCH with mapping type A that is impacted by UL resource muting, a UE may not expect to be provided with an UL muting resource corresponding to the third and fourth symbols of the slot with an impacted PUSCH.

[0057] Further, if a UE is configured with additional DMRS symbols for PUSCH, for an impacted PUSCH with mapping type A, the UE may not expect to be provided with an UL muting resource corresponding to the symbols in aAG2532-PCT 1884.Q72WO1 slot to which an additional DMRS symbol is to be mapped for PUSCH mapping type A.

[0058] Further, if a UE is configured with additional DMRS symbols for PUSCH, for an impacted PUSCH with mapping type B, the UE may not expect to be provided with an UL muting resource corresponding to the symbols within the PUSCH duration to which an additional DMRS symbol is to be mapped for PUSCH mapping type B.

[0059] Alternatively, if UL muting resources are identified to collide with PUSCH DMRS or UL PTRS symbols for a scheduled or configured PUSCH, a UE may ignore the UL muting resources and transmit PUSCH and / or PUSCH DMRS and / or UL PTRS in the affected symbols or apply the UL muting to the next available PUSCH symbol. For one or more of the above embodiments, in case the number of configured or indicated symbols for PUSCH resource muting is more than one, the symbols are consecutive in time and are no more than two symbols, although the scope of the embodiments is not limited in this respect.

[0060] In some embodiments, a UE may be configured with UL resource muting patterns spanning one or more symbols (e.g., one or two symbols), and the number of consecutive symbols for UL resource muting for an impacted may be determined by the UE based on one or more of the following: duration of the PUSCH, PUSCH mapping type, MCS for the PUSCH, code-rate of the PUSCH (without considering muting resources), physical layer priority of the PUSCH. For example, when muting resources of one and two symbols are configured to a UE, a UE may assume application of one-symbol muting resource for a PUSCH with duration less than N symbols, and two-symbol muting resource for a PUSCH with duration greater than or equal to N symbols, where, e.g., N = 4.

[0061] In the frequency domain, a set of subcarriers, and / or a set of physical resource blocks (PRB) can be configured for the muting resources. In some embodiments, when a comb structure is used for the muting resource, a comb offset or a bitmap on the comb offset may be used to indicate the muting resource in the frequency domain. For example, for comb size two (comb-2) for muting resource, the comb offset of either 0 or 1 may be configured via higher layers or indicated to a UE.AG2532-PCT 1884.Q72WO1

[0062] In some embodiments, the set of PRBs for the muting resources can be configured in accordance with the frequency domain resource allocation type 0 or type 1 or type 2 for the PUSCH transmission. Further, the muting resources for the uplink transmission may be configured per uplink bandwidth part (BWP).

[0063] In some embodiments, when a muting pattern is configured or indicated for a UE, and when a PUCCH overlaps with a PUSCH in the time domain, the UE performs the collision handling between the PUCCH and PUSCH first. In case when UE determines that the UCI is multiplexed on the PUSCH, the UE performs the resource muting on PUSCH in accordance with the configured and / or indicated muting resources. In some embodiments, the muting pattern may include the case when a full symbol is muted for the uplink transmission.

[0064] FIG.3 illustrates a procedure for UCI multiplexing on a PUSCH with muting resources, in accordance with some embodiments. In operation 202, the UE may determine a set of resource elements (RE) for muting resources for uplink transmission. The set of REs for muting resource can be configured by higher layers via RRC signaling and / or dynamically indicated in the DCI or a combination thereof. In operation 204, the UE may determine that a PUCCH overlaps with a PUSCH transmission in time domain and would multiplex UCI on the PUSCH. In operation 206, the UE may determine the number of UCI resources on PUSCH excluding the muting resources. In operation 208, the UE may transmit the UCI on PUSCH in accordance with the determined UCI resources and the muting resources.

[0065] In some embodiments, when a muting pattern is configured or indicated for a UE, and when a PUCCH overlaps with a PUSCH in the time domain, the UE performs the resource muting on PUSCH in accordance with the configured and / or indicated muting resources first.

[0066] Further, if the resulting PUSCH transmission does not overlap with the PUCCH in the time domain, the UE transmits the PUSCH and PUCCH separately without performing UCI multiplexing on PUSCH. If the resulting PUSCH transmission overlaps with the PUCCH in the time domain, the UE performs the collision handling between the PUCCH and the resulting PUSCH.AG2532-PCT 1884.Q72WO1 In some embodiments, the muting pattern may include the case when a full symbol is muted for the uplink transmission.

[0067] FIG.4 illustrates an example of collision handling between PUCCH and PUSCH with muting resources, in accordance with some embodiments. As illustrated in FIG.4, symbols #0 through #9 are allocated for PUSCH transmission 402, symbols #8 and #9 are configured as muting resources, and symbols #8 to #11 are allocated for PUCCH transmission 404. In these embodiments, the UE may first determine the actually transmitted resources for the PUSCH in accordance with the muting resources. As the resulting PUSCH does not overlap with PUCCH, the UE transmits the resulting PUSCH and PUCCH, respectively.

[0068] In some embodiments, in case of UCI multiplexing on PUSCH, the number of resources for UCI transmission may be determined in accordance with the allocated resource for PUSCH transmission, excluding the muting resource for uplink transmission.

[0069] In some embodiments, the amount of Hybrid ARQ (Automatic Repeat request acknowledgement (HARQ-ACK) resource on PUSCH with UL- SCH for PUSCH transmission with muting resources may be determined as follows: For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as , is determined as follows:where - is the number of HARQ-ACK bits;AG2532-PCT 1884.Q72WO1 - if , ; otherwise is the number of CRC bits for HARQ-ACK; - ; - is the number of code blocks for UL-SCH of the PUSCH transmission; - if the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE shall not transmit the -th code block, =0; otherwise, is the -th code block size for UL-SCH of the PUSCH transmission; - is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; -is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission; -is the number of subcarriers in OFDM symbol that are not used in the PUSCH transmission; -is the number of resource elements that can be used for transmission of UCI in OFDM symbolin the PUSCH transmission andis the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; - for any OFDM symbol that carries DMRS of the PUSCH,; - for any OFDM symbol that does not carry DMRS of the PUSCH,- for any OFDM symbol that includes the resource elements that are not used for the PUSCH transmission,; - is configured by higher layer parameter scaling;AG2532-PCT 1884.Q72WO1 - is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission.

[0070] In some embodiments, the amount of HARQ-ACK resource on PUSCH without UL-SCH for PUSCH transmission with muting resources may be determined as follows: For HARQ-ACK transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as , is determined as follows:where - is the number of HARQ-ACK bits; -, ; otherwise is the number of CRC bits for HARQ-ACK .; - ; - is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; - is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission; -is the number of subcarriers in OFDM symbol that are not used in the PUSCH transmission; - is the number of resource elements that can be used for transmission of UCI in OFDM symbolin the PUSCH transmission and is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; - for any OFDM symbol that carries DMRS of the PUSCH, ;AG2532-PCT 1884.Q72WO1 - for any OFDM symbol that does not carry DMRS of the PUSCH,- for any OFDM symbol that includes the resource elements that are not used for the PUSCH transmission,- is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission; - is the code rate of the PUSCH; - is the modulation order of the PUSCH; - is configured by higher layer parameter scaling.

[0071] In some embodiments, the above embodiments can also apply for the case of HARQ-ACK resource on TBoMS with UL-SCH, and HARQ-ACK resource on PUSCH using repetition type B with UL-SCH. In some embodiments, the above examples for HARQ-ACK can be straightforwardly extended to the other UCI types, including CSI part 1, CSI part 2, CG-UCI, HARQ-ACK and CG-UCI, UTO-UCI.

[0072] PUSCH transmission with uplink resource muting in case of cancellation indication

[0073] Embodiments of PUSCH transmission with uplink resource muting in case of cancellation indication (CI) are provided as follows:

[0074] In some embodiments, in case of uplink cancellation indication, when a muting pattern is configured or indicated, the UE first performs muting on the PUSCH transmission in accordance with the muting pattern.

[0075] If the resulting PUSCH transmission does not overlap the indicated resource from the uplink cancellation indication, the UE transmits the resulting PUSCH. If the resulting PUSCH transmission overlaps with the indicated resource from the uplink cancellation indication, the UE cancels the resulting PUSCH, subject to the specified processing timeline. In someAG2532-PCT 1884.Q72WO1 embodiments, the muting pattern may include the case when a full symbol is muted for the uplink transmission.

[0076] In some embodiments, in case of uplink cancellation indication, UE first determines whether to transmit the PUSCH in accordance with the indicated resource from the uplink cancellation indication, regardless of the muting pattern that is configured or indicated.

[0077] If the PUSCH overlaps with the indicated resource from the uplink cancellation indication, the UE cancels the PUSCH transmission. If the PUSCH does not overlap with the indicated resource from the uplink cancellation indication, the UE then performs muting on the PUSCH transmission in accordance with the muting pattern. In some embodiments, the muting pattern may include the case when a full symbol is muted for the uplink transmission.

[0078] In some embodiments, for PUSCH transmission with repetition, if at least one of the PUSCH repetitions overlaps with the muting resource, the muting is applied to each PUSCH repetition. In this case, same muting pattern may be applied for each PUSCH repetition.

[0079] In some embodiments, for PUSCH transmission with repetition, if at least one of the PUSCH repetitions does not overlap with the muting resource, the muting is not applied to the PUSCH repetition.

[0080] In some embodiments, for PUSCH transmission with repetition, if the first PUSCH repetition overlaps with the muting resource, the muting is applied to each PUSCH repetition. In this case, the same muting pattern in the first slot is applied for each PUSCH repetition. If the first PUSCH repetition does not overlap with the muting resource, the muting is not applied to the PUSCH repetitions.

[0081] In some embodiments, for transport block processing over multiple slots (TBoMS) on PUSCH, if TBoMS transmission in a slot overlaps with the muting resource, the muting is applied to the TBoMS transmission in each slot. In this case, same muting pattern may be applied for each PUSCH repetition.AG2532-PCT 1884.Q72WO1

[0082] In some embodiments, if TBoMS transmission in a slot does not overlap with the muting resource, the muting is not applied to the TBoMS transmission in each slot.

[0083] In some embodiments, if TBoMS transmission in the first slot overlaps with the muting resource, the muting is applied to the TBoMS transmission in each slot. In this case, the same muting pattern in the first slot is applied to the TBoMS transmission in each slot. Further, if the TBoMS transmission in the first slot does not overlap with the muting resource, the muting is not applied to the TBoMS transmission in each slot.

[0084] In some embodiments, transport block size (TBS) for TBoMS transmission may be determined in accordance with the total number of available resource elements (RE) in the number of slots for TBoMS transmission, excluding the overlapped muting resource in the number of slots. In some embodiments, TBS for TBoMS transmission may be determined in accordance with the available number of REs in the first slot and the number of slots for TBoMS transmission, excluding the overlapped muting resource in the first slot.

[0085] Transmission Power aspects

[0086] In some embodiments, when a UE is configured with a muting resource which mutes particular resource elements in a symbol but does not mute the whole symbol, the UE applies transmit power control to these symbols so that the resulting total power is the same as it would be without muting. As a result, the power spectrum density on the non-muted symbols is increased compared to the symbols without muting.

[0087] Alternatively, the UE may apply transmit power control so that the power spectrum density on the non-muted symbols is equal to the power spectrum density on the symbols without muting, and the total transmit power is reduces compared to the symbols without muting.

[0088] FIG.5 illustrates an example of a physical resource block (PRB) configured with muting resources, in accordance with some embodiments. In these embodiments, muting may be applied to a corresponding PUSCH transmission in the one or two symbol(s) configured in the muting resource. When resource muting is applied in a symbol, either even or odd sub-carriers ofAG2532-PCT 1884.Q72WO1 the frequency resource of the PUSCH are available and the other sub-carriers are not used for the PUSCH transmission. In the example illustrated in FIG.5, a UE may be allocated with symbols #1, #2, #3, #4, #5 and #6 for a PUSCH transmission. In this example, the muting resource is in symbols #3 and #4 and in the even subcarriers. In FIG.5, resource elements (REs) that comprise the muting resources are shaded. In these embodiments, the UE would transmit the PUSCH in the non-shaded REs. In other words, the PUSCH is transmitted on all the non-shaded resource elements in the figure (i.e., the PUSCH is transmitted on symbol numbers #1, #2, #5 and #6 on all subcarriers and on symbol numbers #3 and #4 on only the odd subcarriers.

[0089] It should be noted that FIG.5 only illustrates a single physical resource block as the same would apply to other PRBs of the PUSCH transmission. In these embodiments, UCI data may be encoded for transmission on the non-muted resource illustrated as the non-shaded REs in FIG.5.

[0090] In these embodiments, the UE may be configured for transmission of a PUSCH with uplink (UL) resource muting with radio resource control (RRC) signalling comprising a physical uplink shared channel (PUSCH) configuration information element (PUSCH-Config). The PUSCH-Config may indicate the muting resource. The UE may also decode a downlink configuration information (DCI) format scheduling the PUSCH. The DCI format may include an uplink muting indicator that indicates muting is to be applied to the scheduled PUSCH. In these embodiments, the UE may apply UL resource muting to the scheduled PUSCH in accordance with the PUSCH-Config and the uplink muting indicator.

[0091] In these embodiments, the UE may apply UL resource muting in one or two symbols of the muting resource. When the UL resource muting is applied in a symbol, the symbol is muted in either even numbered subcarriers or odd numbered subcarriers. When the symbol is muted in the even numbered subcarriers, the muted symbol on the even numbered subcarriers is not used in the PUSCH. When the symbol is muted in the odd numbered subcarriers, the muted symbol on the odd numbered subcarriers is not used in the PUSCH. In some embodiments, the PUSCH-Config may indicate that the UL muting resource may be configured with up to two symbol positions in a slot.AG2532-PCT 1884.Q72WO1

[0092] In some embodiments, when uplink control information (UCI) comprising a HARQ-ACK transmission is to be multiplexed on the PUSCH, theUE may calculate a number of resource elements (MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol; determine a number of mutedsubcarriersin the OFDM symbol in the PUSCH; and calculate anumber of coded modulation symbols per layer for the HARQ-ACKtransmission (Q′ ) using the number of resource elements (MUCI ACKsc(l)) that can be used for transmission of the UCI in an OFDM symbol.

[0093] In these embodiments, for an OFDM symbol that does not carry a demodulation reference symbol (DMRS), the number of resource elements(MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol maybe reduced by number of muted subcarriers ( ).

[0094] In some embodiments, for an OFDM symbol that does not carry aDMRS, the number of resource elements (MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol may be equal to a numbersubcarriers comprising a scheduled bandwidth of the PUSCHminus aPT-RSnumber of subcarriers in the OFDM symbol that carries a PTRS (M sc ( l ) ) andthe number of muted subcarriers (subtracted from.

[0095] In some embodiments, for an OFDM symbol that carries a UDMRS, the number of resource elements (MCI sc(l)) that can be used fortransmission of the UCI in an OFDM symbol may be equal to zero (M sc= 0 ).

[0096] In some embodiments, to apply the UL resource muting to the scheduled PUSCH that includes uplink control information (UCI), the UE may calculate a number of coded modulation symbols based on scheduled resources of the PUSCH excluding the muting resource and may transmit the PUSCH on the scheduled resources without transmitting on the muting resource. These embodiments employ a rate-matching approach in which the UCI or data size is determined based on the total allocated resource minus the muted resource, and then encoded bits are mapped to the resources that comprise the total allocated resource minus the muted resource.AG2532-PCT 1884.Q72WO1

[0097] Some other embodiments may employ a puncturing based approach in which the UCI or data size is determined based on the total allocated resource (which includes the muted resource). In these embodiments, the encoded bits are mapped to resources that comprise the total allocated resource minus the muted resource.

[0098] In some embodiments, for uplink control information (UCI) comprising a channel state information (CSI) transmission to be multiplexed on the PUSCH, the UE may calculate a number of coded modulation symbols perlayer for the CSI transmission using a number of resource elements (MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol; and determine anumber of muted subcarriers ( ) in the OFDM symbol in the PUSCH.

[0099] In some embodiments, for an OFDM symbol that does not carry a UCDMRS, the number of resource elements (MI sc(l)) that can be used for transmission of the UCI in an OFDM symbol may be reduced by a number ofmuted subcarriers

[0100] Some embodiments are directed to a computer-readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation new radio (NR) network.

[0101] Some embodiments are directed to a generation Node B (gNB) configured for operation in a new radio (NR) network. In these embodiments, the gNB may encode radio resource control (RRC) signalling for transmission to a user equipment (UE). The RRC signalling may comprise a physical uplink shared channel (PUSCH) configuration information element (PUSCH-Config) to configure the UE for a PUSCH with uplink (UL) resource muting. The gNB may also encode a downlink configuration information (DCI) format for transmission to the UE scheduling the PUSCH. The DCI format may include an uplink muting indicator that indicates muting is to be applied to the scheduled PUSCH. In these embodiments, the PUSCH-Config may indicate a muting resource. In some of these embodiments, the UL resource muting may be configured in one or two symbols of the muting resource.

[0102] FIG.6 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments. WirelessAG2532-PCT 1884.Q72WO1 communication device 600 may be suitable for use as a UE or gNB configured for operation in a 5G NR or 6G network. Some embodiments are directed to an apparatus of a UE or gNB comprising processing circuitry and memory configured for operation in a 5G NR or 6G network.

[0103] The wireless communication device 600 may include communications circuitry 602 and a transceiver 610 for transmitting and receiving signals to and from other communication devices using one or more antennas 601. The communications circuitry 602 may include circuitry that can operate the physical layer (PHY) communications and / or medium access control (MAC) communications for controlling access to the wireless medium, and / or any other communications layers for transmitting and receiving signals. The wireless communication device 600 may also include processing circuitry 606 and memory 608 arranged to perform the operations described herein. In some embodiments, the communications circuitry 602 and the processing circuitry 606 may be configured to perform operations detailed in the above figures, diagrams, and flows.

[0104] In accordance with some embodiments, the communications circuitry 602 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 602 may be arranged to transmit and receive signals. The communications circuitry 602 may also include circuitry for modulation / demodulation, upconversion / downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 606 of the wireless communication device 600 may include one or more processors. In other embodiments, two or more antennas 601 may be coupled to the communications circuitry 602 arranged for sending and receiving signals. The memory 608 may store information for configuring the processing circuitry 606 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 608 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 608 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media,AG2532-PCT 1884.Q72WO1 optical storage media, flash-memory devices and other storage devices and media.

[0105] In some embodiments, the wireless communication device 600 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and / or transmit information wirelessly.

[0106] In some embodiments, the wireless communication device 600 may include one or more antennas 601. The antennas 601 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting device.

[0107] In some embodiments, the wireless communication device 600 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0108] Although the wireless communication device 600 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-AG2532-PCT 1884.Q72WO1 frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the wireless communication device 600 may refer to one or more processes operating on one or more processing elements.

[0109] Examples: 1. A system and method of wireless communication for a fifth generation (5G) or new radio (NR) system: Determined, by a UE, a set of a set of resource elements (RE) for muting resources for uplink transmission; Determined, by the UE, that a physical uplink control channel (PUCCH) overlaps with a physical uplink shared channel (PUSCH) transmission in time domain and would multiplex uplink control information (UCI) on the PUSCH; Determined, by the UE, the number of UCI resources on PUSCH wherein PUSCH excludes the muting resources. Transmitted, by the UE, UCI on PUSCH in accordance with the determined UCI resources and the muting resources 2. The method of example 1, wherein a set of resource elements (RE) in time and frequency domain may be configured for the muting resource for uplink transmission by higher layers via radio resource control (RRC) signalling or dynamically indicated in the downlink control information (DCI) or a combination thereof 3. The method of example 1, wherein when a PUSCH transmission and / or a physical uplink control channel (PUCCH) transmission overlaps with the muting resource in the time and frequency domain, UE does not transmit the PUSCH or PUCCH on the muted resource in the time and frequency, respectivelyAG2532-PCT 1884.Q72WO1 4. The method of example 1, wherein when a PUCCH transmission overlaps with the muting resource in the time and frequency domain, UE may ignore the muting resource and transmit the PUCCH in accordance with the configured or allocated resource 5. The method of example 1, wherein when a sounding reference signal (SRS) transmission overlaps with the muting resource in the time and frequency domain, UE does not transmit the SRS on the muted resource in the time and frequency 6. The method of example 1, wherein when an SRS transmission overlaps with the muting resources in the time and frequency domain, UE drops or cancels the SRS transmission in the overlapped symbols 7. The method of example 1, wherein in the time domain, a set of symbols in a slot and / or a set of slots in a frame may be configured for the muting resources 8. The method of example 1, wherein the symbol index or a bitmap on the symbol index in a slot or start and length indicator value (SLIV) for the indication of symbol index in a slot may be configured for indicating the muting resource in the time domain 9. The method of example 1, wherein when a bitmap is used for muting resource indication, the length of the bitmap is the number of symbols in a slot 10. The method of example 1, wherein slot offset and periodicity may be configured for the muting resource in the time domain 11. The method of example 1, wherein in the frequency domain, a set of subcarriers, and / or a set of physical resource blocks (PRB) can be configured for the muting resourcesAG2532-PCT 1884.Q72WO1 12. The method of example 1, wherein when a comb structure is used for the muting resource, a comb offset or a bitmap on the comb offset may be used to indicate the muting resource in the frequency domain 13. The method of example 1, wherein when a muting pattern is configured or indicated for a UE, and when a PUCCH overlaps with a PUSCH in the time domain, the UE performs the collision handling between the PUCCH and PUSCH first; wherein when UE determines that the UCI is multiplexed on the PUSCH, the UE performs the resource muting on PUSCH in accordance with the configured and / or indicated muting resources. 14. The method of example 1, wherein when a muting pattern is configured or indicated for a UE, and when a PUCCH overlaps with a PUSCH in the time domain, the UE performs the resource muting on PUSCH in accordance with the configured and / or indicated muting resources first 15. The method of example 1, wherein if the resulting PUSCH transmission does not overlap with the PUCCH in the time domain, the UE transmits the PUSCH and PUCCH separately without performing UCI multiplexing on PUSCH; If the resulting PUSCH transmission overlaps with the PUCCH in the time domain, the UE performs the collision handling between the PUCCH and the resulting PUSCH. 16. The method of example 1, wherein in case of UCI multiplexing on PUSCH, the number of resources for UCI transmission may be determined in accordance with the allocated resource for PUSCH transmission, excluding the muting resource for uplink transmissionAG2532-PCT 1884.Q72WO1 17. The method of example 1, wherein in case of uplink cancellation indication, when a muting pattern is configured or indicated, the UE first performs muting on the PUSCH transmission in accordance with the muting pattern; If the resulting PUSCH transmission does not overlap the indicated resource from the uplink cancellation indication, the UE transmits the resulting PUSCH. If the resulting PUSCH transmission overlaps with the indicated resource from the uplink cancellation indication, the UE cancels the resulting PUSCH, subject to the specified processing timeline. 18. The method of example 1, wherein in case of uplink cancellation indication, UE first determines whether to transmit the PUSCH in accordance with the indicated resource from the uplink cancellation indication, regardless of the muting pattern that is configured or indicated; if the PUSCH overlaps with the indicated resource from the uplink cancellation indication, the UE cancels the PUSCH transmission. If the PUSCH does not overlap with the indicated resource from the uplink cancellation indication, the UE then performs muting on the PUSCH transmission in accordance with the muting pattern 19. The method of example 1, wherein when a UE is configured with a muting resource which mutes particular resource elements in a symbol but does not mute the whole symbol, the UE applies transmit power control to these symbols so that the resulting total power is the same as it would be without muting 20. The method of example 1, wherein the UE may apply transmit power control so that the power spectrum density on the non-muted symbols is equal to the power spectrum density on the symbols without muting.

[0110] The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. TheAG2532-PCT 1884.Q72WO1 following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

AG2532-PCT 1884.Q72WO1 CLAIMS What is claimed is:

1. An apparatus for a user equipment (UE) configured for operation in a new radio (NR) network, the apparatus comprising: processing circuitry; and memory, wherein the processing circuitry is configured to: decode radio resource control (RRC) signalling comprising a physical uplink shared channel (PUSCH) configuration information element (PUSCH- Config) for a PUSCH with uplink (UL) resource muting, decode a downlink configuration information (DCI) format scheduling the PUSCH, the DCI format including an uplink muting indicator that indicates muting is to be applied to the scheduled PUSCH; and apply UL resource muting to the scheduled PUSCH in accordance with the PUSCH-Config and the uplink muting indicator, wherein the PUSCH-Config indicates a muting resource.

2. The apparatus of claim 1, wherein when uplink control information (UCI) comprising a Hybrid ARQ (Automatic Repeat request acknowledgement (HARQ-ACK) transmission is to be multiplexed on the PUSCH, the processing circuitry is configured to: UC calculate a number of resource elements (MI sc(l)) that can be used for transmission of the UCI in an OFDM symbol; determine a number of muted subcarriersin the OFDMsymbol in the PUSCH; and calculate a number of coded modulation symbols per layer for theHARQ-ACK transmission (Qusing the number of resource elementsM UCI(sc(l)) that can be used for transmission of the UCI in an OFDM symbol, wherein for an OFDM symbol that does not carry a demodulation UCIreference symbol (DMRS), the number of resource elements (M sc(l)) that canAG2532-PCT 1884.Q72WO1 be used for transmission of the UCI in an OFDM symbol is reduced by numberof muted subcarriers (3. The apparatus of claim 2, wherein for an OFDM symbol that does not Ucarry a DMRS, the number of resource elements (MCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol is equal to a number subcarrierscomprising a scheduled bandwidth of the PUSCHminus a number ofPsubcarriers in the OFDM symbol that carries a PTRS (MT-RS sc ( l ) ) and thenumber of muted subcarriers () subtracted from.

4. The apparatus of claim 2, wherein for an OFDM symbol that carries a MRS, the number of resource elements (MUCIDsc(l)) that can be used fortransmission of the UCI in an OFDM symbol is equal to zero= 0 ).

5. The apparatus of claim 1, wherein to apply the UL resource muting to the scheduled PUSCH that includes uplink control information (UCI), the processing circuitry is configured to: calculate a number of coded modulation symbols based on scheduled resources of the PUSCH excluding the muting resource; and configure the UE to transmit the PUSCH on the scheduled resources without transmitting on the muting resource.

6. The apparatus of claim 1, wherein the processing circuitry is configured to apply the UL resource muting in one or two symbols of the muting resource.

7. The apparatus of claim 6, wherein when the UL resource muting is applied in a symbol, the symbol is muted in either even numbered subcarriers or odd numbered subcarriers, wherein when the symbol is muted in the even numbered subcarriers, the muted symbol on the even numbered subcarriers is not used in the PUSCH, andAG2532-PCT 1884.Q72WO1 wherein when the symbol is muted in the odd numbered subcarriers, the muted symbol on the odd numbered subcarriers is not used in the PUSCH.

8. The apparatus of claim 6, wherein the PUSCH-Config indicates that the muting resource is configured with up to two symbol positions in a slot.

9. The apparatus of claim 1, wherein for uplink control information (UCI) comprising a channel state information (CSI) transmission to be multiplexed on the PUSCH, the processing circuitry is configured to: calculate a number of coded modulation symbols per layer for the CSItransmission using a number of resource elements (MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol and a number of muted subcarriersthe OFDM symbol in the PUSCH10. The apparatus of claim 9, wherein for an OFDM symbol that does notcarry a DMRS, the number of resource elements (MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol is reduced by a number of mutedsubcarriers11. A computer-readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a new radio (NR) network, wherein the processing circuitry is configured to: decode radio resource control (RRC) signalling comprising a physical uplink shared channel (PUSCH) configuration information element (PUSCH- Config) for a PUSCH with uplink (UL) resource muting, decode a downlink configuration information (DCI) format scheduling the PUSCH, the DCI format including an uplink muting indicator that indicates muting is to be applied to the scheduled PUSCH; and apply UL resource muting to the scheduled PUSCH in accordance with the PUSCH-Config and the uplink muting indicator, wherein the PUSCH-Config indicates a muting resource.AG2532-PCT 1884.Q72WO1 12. The computer-readable storage medium of claim 11, wherein the processing circuitry is configured to apply the UL resource muting in one or two symbols of the muting resource.

13. The computer-readable storage medium of claim 12, wherein when the UL resource muting is applied in a symbol, the symbol is muted in either even numbered subcarriers or odd numbered subcarriers, wherein when the symbol is muted in the even numbered subcarriers, the muted symbol on the even numbered subcarriers is not used in the PUSCH, and wherein when the symbol is muted in the odd numbered subcarriers, the muted symbol on the odd numbered subcarriers is not used in the PUSCH.

14. The computer-readable storage medium of claim 12, wherein the PUSCH-Config indicates that the UL muting resource is configured with up to two symbol positions in a slot.

15. The computer-readable storage medium of claim 12, wherein when uplink control information (UCI) comprising a Hybrid ARQ (Automatic Repeat request acknowledgement (HARQ-ACK) transmission is to be multiplexed on the PUSCH, the processing circuitry is configured to: alculate a number of resource elements (MUCI csc(l)) that can be used for transmission of the UCI in an OFDM symbol; determine a number of muted subcarriers) in the OFDMsymbol in the PUSCH; and calculate a number of coded modulation symbols per layer for theHARQ-ACK transmission (Q A′CK ) using the number of resource elementsM UCI(sc(l)) that can be used for transmission of the UCI in an OFDM symbol, wherein for an OFDM symbol that does not carry a demodulationreference symbol (DMRS), the number of resource elements (MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol is reduced by numberof muted subcarriers (AG2532-PCT 1884.Q72WO1 16. The computer-readable storage medium of claim 15, wherein for an OFDM symbol that does not carry a DMRS, the number of resource elements(MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol is equal to a number subcarriers comprising a scheduled bandwidth of the PUSCHminus a number of subcarriers in the OFDM symbol that carries aPT-RPTRS (MS sc ( l ) ) and the number of muted subcarriers) subtractedfrom.

17. The computer-readable storage medium of claim 15, wherein for anOFDM symbol that carries a DMRS, the number of resource elements (MUCI sc(l)) that can be used for transmission of the UCI in an OFDM symbol is equal tozero18. An apparatus for a generation Node B (gNB) configured for operation in a new radio (NR) network, the apparatus comprising: processing circuitry; and memory, wherein the processing circuitry is configured to: encode radio resource control (RRC) signalling for transmission to a user equipment (UE), the RRC signalling comprising a physical uplink shared channel (PUSCH) configuration information element (PUSCH-Config) to configure the UE for a PUSCH with uplink (UL) resource muting, encode a downlink configuration information (DCI) format for transmission to the UE, the DCI format scheduling the PUSCH, the DCI format including an uplink muting indicator that indicates muting is to be applied to the scheduled PUSCH, wherein the PUSCH-Config indicates a muting resource.

19. The apparatus of claim 18, wherein the UL resource muting is configured in one or two symbols of the muting resource.AG2532-PCT 1884.Q72WO1 20. The apparatus of claim 19, wherein when the UL resource muting is to be applied in a symbol, the symbol is muted in either even numbered subcarriers or odd numbered subcarriers, wherein when the symbol is muted in the even numbered subcarriers, the muted symbol on the even numbered subcarriers is not used in the PUSCH, and wherein when the symbol is muted in the odd numbered subcarriers, the muted symbol on the odd numbered subcarriers isa not used in the PUSCH.

Images