WO2022087619A1

WO2022087619A1 - .prioritization and multiplexing pucch and pusch for cross-carrier transmission

Info

Publication number: WO2022087619A1
Application number: PCT/US2021/071971
Authority: WO
Inventors: Debdeep CHATTERJEE; Toufiqul Islam; Sergey PANTELEEV; Salvatore TALARICO
Original assignee: Intel Corporation
Priority date: 2020-10-22
Filing date: 2021-10-21
Publication date: 2022-04-28
Also published as: CN115868235A

Abstract

A user equipment (UE) configurable to support simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers in accordance with uplink (UL) carrier aggregation (CA). The UE may encode a PUCCH for simultaneous transmission with a PUSCH on the different carriers when the PUCCH is scheduled to overlap with the PUSCH regardless of their priorities.

Description

PRIORITIZATION AND MULTIPLEXING PUCCH AND PUSCH FOR CROSS-CARRIER TRANSMISSION

PRIORITY CLAIM

[0001] This application claims priority to United States Provisional Patent Application Serial No. 63/104,433 filed October 22, 2020 [reference number AD3326-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 5Gnew radio (NR) (or 5G-NR) networks. Some embodiments relate to simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers. Some embodiments relate to inter-band carrier aggregation (CA). Some embodiments relate to prioritization and multiplexing of uplink control and data for cross-carrier transmission.

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 5GNR systems has increased. The penetration of mobile devices (i.e., user equipment (UEs)) in modem society has continued to drive demand for a wide variety of networked devices in many disparate environments. 5GNR 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 3 GPP LTE- Advanced with additional potential new radio 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. [0004] In 5G NR networks, different services may be supported in a carrier or serving cell. A UE may support one or more service types. If communication of more than one service type with varying reliability and latency requirements can be made in a carrier/serving cell, it is possible that scheduled/configured resource for transmission of a first service type may overlap with resource for transmission of a second service type for a given UE. This is particularly an issue when in uplink (UL) carrier aggregation, when an UL control channel overlaps with an UL data channel on a different carrier. Thus, there are general needs for systems and methods that address overlap and handling collisions.

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0006] FIG. IB and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some embodiments.

[0007] FIG. 2 is a functional block diagram of a wireless communication device in accordance with some embodiments.

DETAILED DESCRIPTION

[0008] 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.

[0009] Some embodiments are directed to a user equipment (UE) configurable to support simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers in accordance with uplink (UL) carrier aggregation (CA). In these embodiments, the UE may encode radio-resource control (RRC) signalling for transmission to a generation Node B (gNB). The RRC signalling may indicate a UE capability for supporting the simultaneous PUCCH and PUSCH transmission over different carriers in uplink. In these embodiments, the UE may decode signalling received from the gNB that configures the UE for the simultaneous PUCCH and PUSCH transmission over different carriers. The different carriers may comprise a first carrier and a second carrier. The UE may encode a PUCCH for simultaneous transmission with a PUSCH on the different carriers when the PUCCH is scheduled to overlap with the PUSCH. The PUCCH may be encoded to carry control channel information on the first carrier and the PUSCH may be encoded to carry data channel information for transmission on the second carrier. These embodiments are discussed in more detail below.

[0010] In some of these embodiments, a UE with inter-band CA capability may be RRC configured within the same PUCCH group for simultaneous PUCCH/PUSCH transmission of different PHY priorities over different cells. In some embodiments, a dynamic indication may be used. These embodiments are discussed in more detail below.

[0011] In these embodiments, the PUCCH may be transmitted over another channel, in parallel with the PUSCH, to prevent a collision and to provide increased flexibility in handling collisions and increased reliability. In some of these embodiments, when the UE has been configured by the gNB for simultaneous PUCCH and PUSCH transmission over different carriers, the UE may refrain from multiplexing the PUCCH on the PUSCH on the same carrier when the PUCCH is scheduled to overlap the PUSCH.

[0012] In some embodiments, the PUCCH has a first priority and the PUSCH has a second priority. In these embodiments, when the UE has been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers, the UE may encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers regardless of the priorities. When the priorities are different, the UE may refrain from dropping a transmission of a channel having a lower priority comprising one of the PUCCH or the PUSCH.

[0013] In some embodiments, when the PUCCH carries high priority uplink control information (UCI) (e.g., a high priority HARQ-ACK), the PUCCH and PUSCH may be transmitted on the different carriers even when the PUSCH has a lower priority.

[0014] In some embodiments, when the PUCCH is scheduled to overlap with the PUSCH, the UE may determine whether to encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers or multiplex the PUCCH on the PUSCH on the same carrier. In these embodiments, the UE may apply conditions or rules to determine whether to transmit the PUCCH and PUSCH simultaneous on different carrier or to multiplex the PUCCH on the PUSCH on the same carrier.

[0015] In some embodiments, the signalling from the gNB that configures the UE for the simultaneous PUCCH and PUSCH transmission over different carriers may comprise a downlink control information (DCI) format. The DCI format may include an indicator to indicate to the UE whether encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers or to multiplex the PUCCH on the PUSCH on the same carrier, when the PUCCH is scheduled to overlap with the PUSCH. In some embodiments, the indicator may be used to enable or disable simultaneous PUCCH and PUSCH transmission over different carriers, although the scope of the embodiments is not limited in this respect.

[0016] In some embodiments, the DCI format may comprise at least one of an uplink grant scheduling the PUSCH and a downlink grant scheduling a PDSCH that triggers an HARQ-ACK for transmission in the PUCCH.

[0017] In some embodiments, the UE may be configured to support the simultaneous PUCCH and PUSCH transmission over different carriers for interband carrier aggregation (CA). In these embodiments, the first and the second carriers (i.e. , component carriers (CCs) may be in different bands and may be aggregated. In some embodiments, the signalling indicating the UE capability indicates UE support for uplink (UL) carrier aggregation (CA) and UE support for FR1 and FR2 differentiation, although the scope of the embodiments is not limited in this respect.

[0018] In some embodiments, when the UE has not been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers (e.g., either the UE does not support simultaneous PUCCH and PUSCH transmission over different carriers or the UE has not indicated support for simultaneous PUCCH and PUSCH transmission over different carriers), the UE may multiplex a UCI from the PUCCH on the PUSCH on a same carrier when the PUCCH is scheduled to overlap the PUSCH when the UCI comprising HARQ-ACK. In these embodiments, the UE may drop the scheduled PUCCH transmission. In these embodiments, the PUCCH and PUSCH may be multiplexed for transmission on a same carrier, resolving any potential for a collision. In some embodiments when the PUCCH carries high priority UCI (e.g., a high priority HARQ-ACK), the PUCCH may be multiplexed on the same carrier as the PUSCH and the PUSCH may be dropped when the PUSCH is lower priority, although the scope of the embodiments is not limited in this respect.

[0019] In some embodiments, the UE may include a baseband processor and memory configured to store the signalling received from the gNB. In some of these embodiments, the UE may be configured for transmission using two or more antennas. These embodiments are discussed in more detail below.

[0020] Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry to perform operations to configure a user equipment (UE) to support simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers in accordance with uplink (UL) carrier aggregation (CA). These embodiments are described in more detail below.

[0021] Some embodiments are directed to generation Node B (gNB). In these embodiments, the gNB may decode radio-resource control (RRC) signalling from a user equipment (UE) that indicates a UE capability for supporting the simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers in accordance with uplink (UL) carrier aggregation (CA). In these embodiments, the gNB may encode signalling for transmission to the UE to configure the UE for the simultaneous PUCCH and PUSCH transmission over different carriers. The gNB may decode a PUCCH and a PUSCH. The PUCCH and PUSCH may be simultaneously received on the different carriers when the PUCCH is scheduled to overlap with the PUSCH. The PUCCH may be encoded to carry control channel information on the first carrier and the PUSCH may be encoded to carry data channel information for transmission on the second carrier. These embodiments are described in more detail below.

[0022] In some of these embodiments, the PUCCH may have a first priority and the PUSCH has a second priority. In these embodiments, when the UE has been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers, the gNB may decode the PUCCH and the PUSCH. The PUCCH and PUSCH may be simultaneously received from the UE on the different carriers regardless of the priorities. In these embodiments, when the PUCCH carries high priority uplink control information (UCI), the PUCCH and PUSCH are received from the UE on the different carriers including when the PUSCH has a lower priority than the PUCCH. These embodiments are described in more detail below.

[0023] In some embodiments, when the gNB has not configured the UE for the simultaneous PUCCH and PUSCH transmission over different carriers, the gNB may decode a UCI that is multiplexed on the PUSCH on a same carrier when the PUCCH is scheduled to overlap the PUSCH. These embodiments are described in more detail below.

[0024] FIG. 1 A illustrates an architecture of a network in accordance with some embodiments. The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 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 UEs 101 and 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.

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

[0026] 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 the bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

[0027] 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).

[0028] 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.

[0029] In some embodiments, any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. In some embodiments, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB- loT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT 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 loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0030] In some embodiments, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0031] The UEs 101 and 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), aNextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 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.

[0032] In an aspect, the UEs 101 and 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 Sidehnk Broadcast Channel (PSBCH).

[0033] 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).

[0034] 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., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some embodiments, the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication 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 111, 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 112.

[0035] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 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 nodes 111 and/or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node. [0036] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI 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 (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0037] 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-related 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.

[0038] The S-GW 122 may terminate the SI 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-3 GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0039] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 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 131 A, 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 UEs 101 and 102 via the CN 120.

[0040] 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 anon-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- 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.

[0041] In some embodiments, the communication network 140 A can be an loT network or a 5G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). [0042] An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 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.

[0043] 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.

[0044] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments. Referring to FIG. IB, there is illustrated a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)Zhome subscriber server (HSS) 146. The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The SMF 136 can be configured to set up and manage various sessions according to network policy. The UPF 134 can be deployed in one or more configurations according to the desired service type. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0045] In some embodiments, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some embodiments, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator. [0046] In some embodiments, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0047] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0048] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0049] In some embodiments, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsl) not shown in FIG. 1C can also be used.

[0050] In some embodiments, any of the UEs or base stations described in connection with FIGS. 1A-1C can be configured to perform the functionalities described herein.

[0051] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network/system that targets to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich content and services.

[0052] Rel-15 NR systems are designed to operate on the licensed spectrum. The NR-unlicensed (NR-U), a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.

[0053] Different services may be supported in a carrier or serving cell. NR UE may support one or more service types. If communication of more than one service type with varying reliability and latency requirements can be made in a carrier/serving cell, it is possible that scheduled/configured resource for transmission of a first service type may overlap with resource for transmission of a second service type for a given UE. In order to handle collision and prioritize more urgent transmission, Rel-16 specification allows for scheduling or configuring resource for a transmission of either high or low priority where the priority level is indicated to the UE. A configured UE may transmit ‘high’ priority transmission and drop the ‘low’ priority transmission in UL in case of an overlap. However, always dropping ‘low’ priority transmission may be quite detrimental for spectral efficiency and UE perceived throughput for the Tow’ priority transmission which may potentially carry high payload control information of one or multiple carrier.

[0054] In Rel-15, in UL carrier aggregation, when UL control channel (PUCCH) overlaps with a UL data channel (PUSCH) on a different carrier, the PUCCH is multiplexed on the PUSCH. This may not always be desirable, such as PUCCH duration can be long and PUSCH duration can be short, and consequently coverage of PUCCH can be impacted. Moreover, if both the PUCCH and the PUSCH are of high priority (e.g., both requiring high reliability and/or low latency) multiplexing them in a same carrier may not be beneficial for PUCCH reliability in some occasions, since a limited resource within the PUSCH can be allocated for piggybacking UL control information (UCI). To alleviate this problem, simultaneous PUCCH and PUSCH transmission over multiple carriers can be considered, without multiplexing them into a carrier. Moreover, this feature may also facilitate reduced dropping of low priority transmission, in the event of overlap of low and high priority transmission across multiple carriers.

[0055] In this disclosure, we discuss different aspects of handling collisions when PUCCH and PUSCH transmission overlaps across different carriers. We provide methods for identifying the conditions and rules to determine when to multiplex into a carrier and when to transmit over different carriers, when such options are available. The provided solution may also be applicable to PUCCH and PUCCH collisions across different carrier as applicable.

[0056] Simultaneous PUCCH and PUSCH transmissions over different carriers is not supported in NR yet.

[0057] This disclosure describes:

[0058] Conditions/rules to determine whether to multiplex the overlapping transmissions or transmit simultaneously over different carriers [0059] Explicit or implicit rules can be configured, or explicit/implicit indication can be provided to determine UE behavior

[0060] Embodiments may enhance system spectral efficiency and protect reliability of high priority channel.

[0061] The following embodiments are presented from the context of overlap of PUCCH and PUSCH over different carriers, however solutions may also be applicable to when PUCCH and PUCCH overlap in different carriers. The solutions include licensed or unlicensed spectrum, FDD or TDD or flexible duplex system frame structures. PUCCH transmission may contain UCI such as one or more of: SR, HARQ-ACK, CSI. According to Rell5, if one or more PUCCHs carrying UCI such as HARQ-ACK and/or CSI overlap with PUSCH, the UCIs can be multiplexed onto PUSCH and PUCCH can be dropped. PUSCH transmission can be based on dynamic UL grant or without UL grant, e.g., configured grant. PUCCH or PUSCH transmission can be of high or low priority. If no priority is configured or indicated, then the transmission may be regarded with low priority.

[0062] As highlighted in the above, option of transmitting over another channel instead of multiplexing on a single channel in the event of an overlap provides more flexibility in handling collision and in some cases, multiplexing of different channels of same or different priority may not performed, and instead they are transmitted in parallel in different carriers. For example, if there is a collision of high priority PUCCH in a first carrier and low priority PUCCH or low priority PUSCH in a second carrier, high priority transmission can be made in first carrier, whereas low priority transmissions can be made in another carrier, without multiplexing, and this may not only improve reliability of high priority transmission but also avoid dropping of low priority transmission. In the context of the disclosure, overlap implies two or more transmission overlap at least 1 symbol in time. Overlapping PUCCH and PUSCH transmission in different carriers may belong to same or different PUCCH group. The following embodiments consider a UE supporting UL carrier aggregation (CA). One or more of the following features may include inter-band CA and/or intra-band CA. Inter-band and intra-band may also be called inter-frequency and intra-frequency respectively. UE may indicate via capability signaling for support of one or more of the features below for intra-band and/or inter-band CA. Capability signaling for support of one or more of the following features for intra-band and inter-band CA can be joint/together/combined or separate. Moreover, capability signaling may include support of one or more of the features in FR1 and/or FR2. UE may indicate FR1 and FR2 differentiation with respect to support of one or more features.

[0063] UE may receive or transmit control information or data which may be of low or high priority. There is a chance resources of low and high priority transmission may overlap, and UE may need to prioritize the transmission of high priority. For example, resources of PUCCH carrying high priority HARQ-ACK may overlap with that of low priority PUSCH for a UE, UE configured with intra-UE prioritization feature may transmit HARQ-ACK and drop PUSCH. Intra-UE prioritization/multiplexing according to Rel-16 implies that if there is overlap with two UL channels of different priority, UE may drop the low priority channel and would only multiplex if they are of same priority. This may include the case of overlapping transmissions in different carriers within a PUCCH group. Rel-17 intra-UE prioritization/multiplexing supports multiplexing of information of different priority such as it could multiplex UCI of PUCCH onto the overlapping PUSCH even if they are of different priority and this may include not only overlap within a carrier but also within a PUCCH group, e.g., PUCCH and PUSCH transmission resources can be in different carriers but within a PUCCH group. UE may be configured with either Rel-16 intra-UE prioritization feature or Rel-17 intra-UE pri oritization/ multipl exing feature.

[0064] In one embodiment, if there is an overlap of PUCCH and PUSCH transmissions in different carrier, UE may always transmit simultaneous PUSCH and PUCCH transmissions regardless of the priority of the involved PUCCH and PUSCH. In one example, UE may indicate a capability to support this feature. In another example, UE may be configured by higher layer RRC signaling to apply simultaneous PUSCH and PUCCH transmissions over different carriers when there is overlap. In one example, when such configuration is provided, option of simultaneous transmissions over different carriers may take precedence over other configurations if provided such as intra-UE prioritization/multiplexing. This implies UE would transmit PUCCH and PUSCH over different carriers, instead of either multiplexing UCI onto PUSCH or dropping the low priority channel, either PUCCH or PUSCH.

[0065] In another embodiment, if there is an overlap of PUCCH and PUSCH transmissions in different carriers, UE may transmit low priority PUCCH (PUSCH) in one carrier and high priority PUSCH (PUCCH) in a different carrier. In one example of the embodiment, UE may only multiplex channels of same priority in one carrier and transmit different priority channel(s) in another carrier. For example, low priority HARQ-ACK and/or CSI can be multiplexed onto an overlapping low priority PUSCH in one carrier and another overlapping high priority HARQ-ACK may be transmitted in another carrier. In one example, UE may indicate a capability to support this feature. In another example, UE may be configured by higher layer RRC signaling to apply simultaneous PUSCH and PUCCH transmissions over different carriers when there is overlap and they are of different priority. In one example, when such configuration is provided, option of simultaneous transmissions over different carriers may take precedence over other configurations if provided such as intra- UE prioritization/multiplexing. This implies UE would transmit PUCCH and PUSCH over different carriers when they are of different priority, instead of either multiplexing UCI onto PUSCH or dropping the low priority channel, either PUCCH or PUSCH.

[0066] In yet another embodiment, an explicit indication can be provided to the UE in a field in the DCI to determine whether to transmit PUSCH and PUCCH simultaneously over different carriers or multiplex UCI onto PUSCH and drop the PUCCH. In one example, the DCI can be the UL grant scheduling the PUSCH , such as format 0 1 or 0 2. In another example, the DCI can be a DL grant, such as format 1 1 or 1 2, for scheduling a PDSCH which triggers a HARQ-ACK for transmission in a PUCCH. In one example, the field in the DCI may only be present if the UE supports UL CA and/or is configured with intra- UE prioritization/multiplexing. In one example, if both DCIs include the field, UE follows the last indication prior to overlap of PUCCH and PUSCH. Alternatively, the explicit indication can be provided in PUCCH resource configuration or HARQ-ACK codebook configuration or configuration of configured-grant PUSCH. In another example, the indication can be provided in a UE specific field in a group-common DCI. In one example, the explicit indication may only apply if there is overlap of PUCCH and PUSCH transmissions of different priority in different carriers. Alternatively, the explicit indication may apply regardless of the priority of the associated overlapping PUCCH and PUSCH. In one example, presence of the explicit indication in a field in DCI may or may not be dependent on whether UE is configured with Rel-16 or Rel-17 intra-UE prioritization/multiplexing feature. In another example, explicit indication may not only indicate the UE to transmit over multiple carriers simultaneously but also indicate which carrier to transmit where the carrier indication may apply to PUCCH or PUSCH. In one example, the indication may comprise 1 bit, which if ‘0’ may disable simultaneous transmission feature, and if ‘1’ may enable the feature, or vice versa. [0067] In one embodiment, if there is an overlap of PUCCH and PUSCH transmissions in different carriers, UE may identify whether to transmit PUSCH and PUCCH simultaneously over different carriers or multiplex UCI onto PUSCH and drop the PUCCH based on some implicit rules or conditions. For example,

[0068] If last symbols of overlapping transmissions are same or within X

> 1 symbols based on a given numerology, they can be multiplexed, otherwise they can be transmitted simultaneously. X can be specified or configured for a given UE.

[0069] If Long PUCCH or PUCCH with sub-slot or slot-based repetition overlaps with PUSCH, UCI to be transmitted on the PUCCH may not be multiplexed onto the PUSCH.

[0070] If the overlapping channels are of similar length, such as both are contained in same sub-slot or same slot, they can be multiplexed and transmitted in a carrier, otherwise they are transmitted simultaneously in different carriers. This feature can be useful for intra-band CA. This is because overlapping transmissions of different length may cause phase distortions when the signals are received. In one example, for intra-band CA, simultaneous transmission of PUCCH and PUSCH over different carriers may only be allowed if they are of low priority.

[0071] In one embodiment, if UE has power limitation, UE may not perform simultaneous PUCCH and PUSCH transmissions over multiple carriers and instead, transmit over one carrier. In one example, UE may only transmit the PUCCH or PUSCH of high priority and drop the low priority PUCCH or PUSCH transmission. In another example, UE may multiplex UCI of PUCCH onto PUSCH and drop the PUCCH. In yet another example, UE may only multiplex UCI of PUCCH onto PUSCH if one or more of the overlapping transmissions are of high priority. In one example, UE may apply this behavior if the UE is configured with intra-UE prioritization/multiplexing.

[0072] In another embodiment, a certain beta offset configuration can be used for PUSCH if the UE supports simultaneous PUCCH and PUSCH transmission which maybe different than the beta offset configuration used by the UE when low priority (high priority) UCI is multiplexed onto high priority (low priority) PUSCH. For example, if the UE support UL CA and not perform multiplexing of different priority information/channel, UE could use legacy beta offset configuration from Rell5, instead of using a beta offset configuration based on priority of the channels involved in the collision.

[0073] In yet another embodiment, UE supporting UL CA may receive an indication in a DCI, such as in DL grant DCI format 1 1, 1 2, to identify which carrier to select within a PUCCH group for HARQ-ACK transmission. This may be beneficial if there is a PUSCH transmission in a first carrier and NW would like to avoid multiplexing HARQ-ACK on the PUSCH in the first carrier. Instead, a second carrier can be indicated where HARQ-ACK transmission can be simultaneously made. This may not only reduce latency in transmission but also protect reliability of HARQ-ACK, e.g., if it is of high priority. In one example, within a PUCCH group, a primary PUCCH (which is first carrier in the above example) carrier and a secondary PUCCH (e.g., second carrier in the example above) carrier may be configured. If the dynamic carrier switching indicator field is absent in the DCI, UE would use the primary PUCCH carrier for HARQ-ACK transmission. If the field is present, either of the two carriers can be indicated which provides more flexibility in handling overlap of transmissions of different priority. In one example, if second carrier is indicated, the resource for PUCCH transmission can be explicitly indicated in the DCI and/or obtained from higher layer configuration or as a combination of both.

[0074] In one embodiment, simultaneous transmission of PUCCH and PUSCH over different carriers may require same spatial relation (e.g., use same spatial domain transmission filter) or TCI state or beam association between the PUCCH and PUSCH, such as DMRS of PUCCH, if present, and DMRS of PUSCH may share same spatial relation or TCI state or beam index. In one example, higher layer parameter spatialRelationlnfo containing the ID of a reference 'ssblndex' or ‘csi-RS-Index ‘, UE may use the same spatial domain transmission filter used for reception of SS/PBCH block or CSI-RS, respectively, for transmission of PUCCH and PUSCH. In another example, the spatial relation information can be signaled in the DCI which can be used for transmission of PUCCH and/or PUSCH simultaneously over different carriers. In one example, use of same spatial relation for simultaneous transmission of PUCCH and PUSCH over different carrier may be assumed at least for intraband CA. In one example, this constraint may only be applicable if UE has one transmission panel.

[0075] FIG. 2 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments. Wireless communication device 200 may be suitable for use as a UE or gNB configured for operation in a 5GNR network.

[0076] The communication device 200 may include communications circuitry 202 and a transceiver 210 for transmitting and receiving signals to and from other communication devices using one or more antennas 201. The communications circuitry 202 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 communication device 200 may also include processing circuitry 206 and memory 208 arranged to perform the operations described herein. In some embodiments, the communications circuitry 202 and the processing circuitry 206 may be configured to perform operations detailed in the above figures, diagrams, and flows.

[0077] In accordance with some embodiments, the communications circuitry 202 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 202 may be arranged to transmit and receive signals. The communications circuitry 202 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 206 of the communication device 200 may include one or more processors. In other embodiments, two or more antennas 201 may be coupled to the communications circuitry 202 arranged for sending and receiving signals. The memory 208 may store information for configuring the processing circuitry 206 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 208 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 208 may include a computer-readable storage device, read-only memory (ROM), randomaccess memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

[0078] In some embodiments, the communication device 200 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.

[0079] In some embodiments, the communication device 200 may include one or more antennas 201. The antennas 201 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.

[0080] In some embodiments, the communication device 200 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.

[0081] Although the communication device 200 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-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 communication device 200 may refer to one or more processes operating on one or more processing elements. [0082] Examples:

[0083] Example 1 a method of NR UL wireless communication, the method comprising: transmitting by the UE, capability of supporting simultaneous PUCCH and PUSCH transmissions over different carriers; receiving by the UE, a first configuration, which configures the UE for simultaneous PUCCH and PUSCH transmissions over different carriers; receiving by the UE, a first resource for HARQ-ACK transmission in a PUCCH in a first carrier; receiving by the UE, a second resource for a PUSCH transmission in a second carrier, where first and second resources overlap; and transmitting by the UE, the PUCCH and PUSCH simultaneously over different carriers, without multiplexing or dropping PUCCH or PUSCH.

[0084] Example 2 may include the method of example 1 or some other example herein, where the first configuration is provided by higher layer RRC signaling.

[0085] Example 3 may include the method of example 1 or some other example herein, where HARQ-ACK is of high priority and PUSCH is of low priority.

[0086] Example 4 may include the method of example 1 or some other example herein, where receiving by the UE a DCI which enables simultaneous transmission of PUCCH and PUSCH over different carriers.

[0087] Example 5 may include the method of example 1 or some other example herein, where the simultaneous transmission of PUCCH and PUSCH is only supported for inter-band CA.

[0088] Example 6 may include a method of a UE, the method comprising: encoding, for transmission to a gNB, an indication of a capability of supporting simultaneous PUCCH and PUSCH transmissions over different carriers; receiving configuration information for simultaneous PUCCH and PUSCH transmissions over different carriers; receiving a first resource for HARQ-ACK transmission in a PUCCH in a first carrier; receiving a second resource for a PUSCH transmission in a second carrier, wherein the first and second resources overlap; and encoding the PUCCH and the PUSCH for simultaneously transmission over the respective first and second carriers.

[0089] Example 7 may include the method of example 6 or some other example herein, wherein the configuration information is received via RRC signaling.

[0090] 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. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus for a user equipment (UE), the apparatus comprising: processing circuitry; and memory, the UE configurable to support simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers in accordance with uplink (UL) carrier aggregation (CA), the processing circuitry is configured to: encode radio-resource control (RRC) signalling for transmission to a generation Node B (gNB), the RRC signalling indicating a UE capability for supporting the simultaneous PUCCH and PUSCH transmission over different carriers in uplink; decode signalling received from the gNB that configures the UE for the simultaneous PUCCH and PUSCH transmission over different carriers, the different carriers comprising a first carrier and a second carrier; and encode a PUCCH for simultaneous transmission with a PUSCH on the different carriers when the PUCCH is scheduled to overlap with the PUSCH, the PUCCH encoded to carry control channel information on the first carrier, the PUSCH encoded to carry data channel information for transmission on the second carrier.

2. The apparatus of claim 1, wherein the PUCCH has a first priority and the PUSCH has a second priority, and wherein when the UE has been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers, the processing circuitry is configured to: encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers regardless of the priorities; and when the priorities are different, refrain from dropping a transmission of a channel having a lower priority comprising one of the PUCCH or the PUSCH.

26

3. The apparatus of claim 2, wherein when the PUCCH carries high priority uplink control information (UCI), the PUCCH and PUSCH are transmitted on the different carriers including when the PUSCH has a lower priority.

4. The apparatus of claim 2 wherein when the PUCCH is scheduled to overlap with the PUSCH, the processing circuitry is configured to determine whether to encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers or multiplex the PUCCH on the PUSCH on the same carrier.

5. The apparatus of claim 2 wherein the signalling from the gNB that configures the UE for the simultaneous PUCCH and PUSCH transmission over different carriers comprises a downlink control information (DCI) format, the DCI format including an indicator to indicate to the UE whether encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers or to multiplex the PUCCH on the PUSCH on the same carrier, when the PUCCH is scheduled to overlap with the PUSCH.

6. The apparatus of claim 5, wherein the DCI format comprises at least one of: an uplink grant scheduling the PUSCH; and a downlink grant scheduling a PDSCH that triggers an HARQ-ACK for transmission in the PUCCH.

7. The apparatus of claim 2, wherein the UE is configured to support the simultaneous PUCCH and PUSCH transmission over different carriers for interband carrier aggregation (CA), and wherein the first and the second carriers are in different bands and are aggregated.

8. The apparatus of claim 7, wherein the signalling indicating the UE capability indicates UE support for uplink (UL) carrier aggregation (CA), and UE support for FR1 and FR2 differentiation.

9. The apparatus of claim 2, wherein when the UE has not been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers, the processing circuitry is configured to: multiplex a UCI from the PUCCH on the PUSCH on a same carrier when the PUCCH is scheduled to overlap the PUSCH; and drop the scheduled PUCCH transmission.

10. The apparatus of claim 1, wherein the processing circuitry comprises a baseband processor, wherein the memory is configured to store the signalling received from the gNB, and wherein the UE is configured for transmission using two or more antennas.

11. A non-transitory computer-readable storage medium that stores instructions for execution by processing circuitry to perform operations to configure a user equipment (UE) to support simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers in accordance with uplink (UL) carrier aggregation (CA), the processing circuitry is configured to: encode radio-resource control (RRC) signalling for transmission to a generation Node B (gNB), the RRC signalling indicating a UE capability for supporting the simultaneous PUCCH and PUSCH transmission over different carriers in uplink; decode signalling received from the gNB that configures the UE for the simultaneous PUCCH and PUSCH transmission over different carriers, the different carriers comprising a first carrier and a second carrier; and encode a PUCCH for simultaneous transmission with a PUSCH on the different carriers when the PUCCH is scheduled to overlap with the PUSCH, the PUCCH encoded to carry control channel information on the first carrier, the PUSCH encoded to carry data channel information for transmission on the second carrier.

12. The non-transitory computer-readable storage medium of claim 11, wherein the PUCCH has a first priority and the PUSCH has a second priority, and wherein when the UE has been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers, the processing circuitry is configured to: encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers regardless of the priorities; and when the priorities are different, refrain from dropping a transmission of a channel having a lower priority comprising one of the PUCCH or the PUSCH.

13. The non-transitory computer-readable storage medium of claim 12, wherein when the PUCCH carries high priority uplink control information (UCI), the PUCCH and PUSCH are transmitted on the different carriers including when the PUSCH has a lower priority.

14. The non-transitory computer-readable storage medium of claim 12 wherein when the PUCCH is scheduled to overlap with the PUSCH, the processing circuitry is configured to determine whether to encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers or multiplex the PUCCH on the PUSCH on the same carrier.

15. The non-transitory computer-readable storage medium of claim 12 wherein the signalling from the gNB that configures the UE for the simultaneous PUCCH and PUSCH transmission over different carriers comprises a downlink control information (DCI) format, the DCI format including an indicator to indicate to the UE whether encode the PUCCH for simultaneous transmission with the PUSCH on the different carriers or to multiplex the PUCCH on the PUSCH on the same carrier, when the PUCCH is scheduled to overlap with the PUSCH.

16. The non-transitory computer-readable storage medium of claim 15, wherein the DCI format comprises at least one of: an uplink grant scheduling the

29 PUSCH; and a downlink grant scheduling a PDSCH that triggers an HARQ- ACK for transmission in the PUCCH.

17. The non-transitory computer-readable storage medium of claim 12, wherein the UE is configured to support the simultaneous PUCCH and PUSCH transmission over different carriers for inter-band carrier aggregation (CA), and wherein the first and the second carriers are in different bands and are aggregated.

18. The non-transitory computer-readable storage medium of claim 12, wherein when the UE has not been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers, the processing circuitry is configured to: multiplex a UCI from the PUCCH on the PUSCH on a same carrier when the PUCCH is scheduled to overlap the PUSCH; and drop the scheduled PUCCH transmission.

19. An apparatus for a generation Node B (gNB), the apparatus comprising: processing circuitry; and memory, the processing circuitry is configured to: decode radio-resource control (RRC) signalling from a user equipment (UE), the RRC signalling indicating a UE capability for supporting the simultaneous physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission over different carriers in accordance with uplink (UL) carrier aggregation (CA); encode signalling for transmission to the UE to configure the UE for the simultaneous PUCCH and PUSCH transmission over different carriers, the different carriers comprising a first carrier and a second carrier; and decode a PUCCH and a PUSCH, the PUCCH and PUSCH simultaneously received on the different carriers when the PUCCH is scheduled to overlap with the PUSCH, the PUCCH encoded to carry control channel information on the first carrier, the PUSCH encoded to carry data channel information for transmission on the second carrier,

30 wherein the PUCCH has a first priority and the PUSCH has a second priority, and wherein when the UE has been configured by the gNB for the simultaneous PUCCH and PUSCH transmission over different carriers, the processing circuitry is configured to: decode the PUCCH and the PUSCH, the PUCCH and PUSCH simultaneously received from the UE on the different carriers regardless of the priorities, wherein when the PUCCH carries high priority uplink control information (UCI), the PUCCH and PUSCH are received from the UE on the different carriers including when the PUSCH has a lower priority than the PUCCH.

20. The apparatus of claim 19, wherein when the gNB has not configured the UE for the simultaneous PUCCH and PUSCH transmission over different carriers, the processing circuitry is configured to decode a UCI that is multiplexed on the PUSCH on a same carrier when the PUCCH is scheduled to overlap the PUSCH.

31