WO2024036503A1 - Procédé et appareil de transmission de liaison montante - Google Patents

Procédé et appareil de transmission de liaison montante Download PDF

Info

Publication number
WO2024036503A1
WO2024036503A1 PCT/CN2022/112979 CN2022112979W WO2024036503A1 WO 2024036503 A1 WO2024036503 A1 WO 2024036503A1 CN 2022112979 W CN2022112979 W CN 2022112979W WO 2024036503 A1 WO2024036503 A1 WO 2024036503A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
pucch resource
information
uci
harq
Prior art date
Application number
PCT/CN2022/112979
Other languages
English (en)
Inventor
Wei Ling
Yi Zhang
Bingchao LIU
Chenxi Zhu
Lingling Xiao
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2022/112979 priority Critical patent/WO2024036503A1/fr
Publication of WO2024036503A1 publication Critical patent/WO2024036503A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK

Definitions

  • Embodiments of the present application generally relate to wireless communication technology, especially to a method and an apparatus of uplink (UL) transmission, e.g., physical uplink control channel (PUCCH) transmission.
  • UL uplink
  • PUCCH physical uplink control channel
  • Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, broadcasts, and so on.
  • Wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power) .
  • Examples of wireless communication systems may include fourth generation (4G) systems, such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may also be referred to as new radio (NR) systems.
  • 4G systems such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may also be referred to as new radio (NR) systems.
  • Multi-transmit-receive point (TRP) /panel transmission has been introduced into NR since release 16 (Rel-16) .
  • UE user equipment
  • multi-panel simultaneous uplink transmission there are still a mass of issues on uplink transmission to be solved.
  • WID work item description
  • MIMO multiple-input multiple-output
  • FR frequency range
  • M-TRP multi-TRP
  • CPE customer premises equipment
  • FWA fixed wireless access
  • the total number of layers is up to four across all panels and total number of codewords is up to two across all panels, considering single downlink control information (DCI) and multi-DCI based multi-TRP operation.
  • DCI downlink control information
  • multi-DCI based multi-TRP operation considering single downlink control information (DCI) and multi-DCI based multi-TRP operation.
  • common beam framework specified in Rel-17 will be extended for multiple panel simultaneous UL transmission in Rel-18. That is, up to 2 common beams will be indicated for multi-panel simultaneous UL transmission, and a PUCCH resource can be transmitted with one or two common beams.
  • at most two non-overlapping PUCCH resources may be transmitted on a slot according to some multiplexing rules or dropping rules, which may be related to uplink control information (UCI) priority of a PUCCH resource.
  • UCI uplink control information
  • two overlapping PUCCH resources with different beams can be selected if UE supports simultaneous UL transmission with multiple panels.
  • uplink transmission e.g., UCI multiplexing on PUCCH resource (s) can be enhanced considering multiple panel simultaneous UL transmission to increase efficiency of UCI transmission over PUCCH.
  • One objective of the embodiments of the present application is to provide a technical solution of uplink transmission, especially, a method and an apparatus of uplink transmission, e.g., PUCCH transmission in the scenario of multiple panel simultaneous UL transmission.
  • Some embodiments of the present application provide an apparatus of uplink transmission, e.g., UE, which may include: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receive information indicating one or more PUCCH resources which are expected to be transmitted on a slot; and determine a number of PUCCH resources to be transmitted on the slot from at least one PUCCH resource determined according to the one or more PUCCH resources and an UCI multiplexing mode, wherein the number of PUCCH resources is equal to or smaller than a configured or predefined maximum number and there is no overlapping PUCCH resources associated with a same beam in the number of PUCCH resources.
  • Some other embodiments of the present application provide a method of uplink transmission, which may include: receiving information indicating one or more PUCCH resources which are expected to be transmitted on a slot; and determining a number of PUCCH resources to be transmitted on the slot from at least one PUCCH resource determined according to the one or more PUCCH resources and an UCImultiplexing mode, wherein the number of PUCCH resources is equal to or smaller than a configured or predefined maximum number and there is no overlapping PUCCH resources associated with a same beam in the number of PUCCH resources.
  • one resourceSetToAddModList is configured for PUCCH resource configuration, and one PUCCH resource associated with a beam of the one or more PUCCH resources carrying hybrid automatic repeat request-acknowledge (HARQ-ACK) information with corresponding downlink control information (DCI) is overlapping with at least one other PUCCH resource carrying other UCI information associated with the beam of the one or more PUCCH resources, the at least one PUCCH resource includes a PUCCH resource for multiplexing the HARQ-ACK information and the other UCI information.
  • HARQ-ACK hybrid automatic repeat request-acknowledge
  • the PUCCH resource is determined from a PUCCH resource set determined from the resourceSetToAddModList according to a total bit number of the HARQ-ACK information and the other UCI information, and in the case that the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList and a total number of PUCCH resources associated with the beam in the first PUCCH resource set is larger than 8, the PUCCH resource for multiplexing the HARQ-ACK information and the other UCI information is determined from all PUCCH resources associated with the beam in the first PUCCH resource set according to a PUCCH resource indicator (PRI) field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI and a control resource set (CORESET) of the last DCI corresponding to the HARQ-ACK information with corresponding DCI; otherwise, the PUCCH resource for multiplexing the HARQ-ACK information and the other UCI information is determined from all PUCCH resources associated with the beam in the PUCCH resource set
  • one resourceSetToAddModList is configured for PUCCH resource configuration, and a PUCCH resource of the at least one PUCCH resource carries HARQ-ACK information with corresponding DCI associated with a beam
  • the PUCCH resource is determined from a PUCCH resource set determined from the resourceSetToAddModList according to a total bit number of the HARQ-ACK information, wherein, in the case that the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList and a total number of PUCCH resources associated with the beam in the first PUCCH resource set is larger than 8, the PUCCH resource is determined from all PUCCH resources associated with the beam in the first PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI and a CORESET of the last DCI corresponding to the HARQ-ACK information with corresponding DCI
  • the UCI multiplexing mode is separate UCI multiplexing
  • two resourceSetToAddModLists are configured for PUCCH resource configuration, and one PUCCH resource associated with a beam of the one or more PUCCH resources carrying HARQ-ACK information with corresponding DCI is overlapping with at least one other PUCCH resource associated with the beam of the one or more PUCCH resources carrying other UCI information
  • the at least one PUCCH resource includes a PUCCH resource for multiplexing the HARQ-ACK information and the other UCI information
  • the PUCCH resource is determined from a PUCCH resource set associated with the beam determined from a resourceSetToAddModList associated with the beam of the two resourceSetToAddModLists according to a total bit number of the HARQ-ACK information and the other UCI information
  • the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList associated with the beam and a total number of PUCCH resources in the first
  • the PUCCH resource is determined from a PUCCH resource set associated with the beam determined from a resourceSetToAddModList associated with the beam of the two resourceSetToAddModList according to a total bit number of the number of the HARQ-ACK information, wherein in the case that the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList associated with the beam and a total number of PUCCH resources in the first PUCCH resource set is larger than 8, the PUCCH resource is determined from all PUCCH resources in the first PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI and a CORESET of the last
  • one SPS-PUCCH-AN-List is configured, and a PUCCH resource of the at least one PUCCH resource carries UCI information only including HARQ-ACK information bits in response to a plurality of semi persistent scheduling (SPS) physical downlink shared channel (PDSCH) receptions associated with a beam or only including HARQ-ACK information bits in response to one or more SPS PDSCH receptions associated with a beam and schedule request (SR) associated with the beam
  • the PUCCH resource is determined from all PUCCH resources associated with the beam of the SPS-PUCCH-AN-List according to a total number of bits of the UCI information.
  • the UCI multiplexing mode is separate UCI multiplexing
  • two SPS-PUCCH-AN-Lists are configured, and a PUCCH resource of the at least one PUCCH resource carries UCI information only including HARQ-ACK information bits in response to a plurality of SPS PDSCH receptions associated with a beam or only including HARQ-ACK information bits in response to one or more SPS PDSCH receptions associated with a beam and SR associated with the beam
  • the PUCCH resource is determined from all PUCCH resources of a SPS-PUCCH-AN-List associated with the beam of the two SPS-PUCCH-AN-Lists according to a total number of bits of the UCI information.
  • one multi-CSI-PUCCH-ResourceList is configured, and a) a plurality of PUCCH resources associated with a beam of the one or more PUCCH resources carrying a plurality of CSI reports are overlapping on the slot where UCI information includes the plurality of CSI reports or b) at least one PUCCH resource associated with a beam of the one or more PUCCH resources carrying at least one CSI report and at least one other PUCCH resource associated with the beam carrying at least one of HARQ-ACK information bits in response to at least one SPS PDSCH reception or SR information bits are overlapping on the slot where the UCI information includes the at least one CSI report and the at least one of HARQ-ACK information or SR information, the at least one PUCCH resource includes a PUCCH resource for multiplexing the UCI information, wherein, the PUCCH resource is determined from all PUCCH resources associated with the beam of the multi-
  • the UCI multiplexing mode is separate UCI multiplexing
  • two multi-CSI-PUCCH-ResourceLists are configured, and a) a plurality of PUCCH resources associated with a beam of the one or more PUCCH resources carrying a plurality of CSI reports are overlapping on the slot where UCI information includes the plurality of CSI reports or b) at least one PUCCH resource associated with a beam of the one or more PUCCH resources carrying at least one CSI report and at least one other PUCCH resource associated with the beam carrying at least one of HARQ-ACK information bits in response to at least one SPS PDSCH reception or SR information bits are overlapping on the slot where the UCI information includes the at least one CSI report and the at least one of HARQ-ACK information or SR information, the at least one PUCCH resource includes a PUCCH resource for multiplexing the UCI information, wherein, the PUCCH resource is determined from all PUCCH resources of a multi-CSI-
  • the at least one PUCCH resource is at most 4 PUCCH resources associated with two beams determined after the separate UCI multiplexing, and each beam is associated with at most 2 PUCCH resources of the at most 4 PUCCH resources
  • the number of PUCCH resources to be transmitted is determined from the at most 4 PUCCH resources is according to a highest UCI priority of each of the at most 4 PUCCH resources.
  • determining a number of PUCCH resources to be transmitted on the slot from the at least one PUCCH resource includes: determining a first PUCCH resource corresponding to a CSI report with a highest priority in the case that the UE is not provided multi-CSI-PUCCH-ResourceList or PUCCH resources for transmissions of CSI reports associated with a beam do not overlap on the slot, in the case that there is a first set of PUCCH resource on the slot not overlapping with the first PUCCH resource, determining a second PUCCH resource corresponding to a CSI report with a highest priority from the first set of PUCCH resources; in the case that there is a second set of PUCCH resource on the slot overlapping with the first PUCCH resource while associated with another beam different from the first PUCCH resource,
  • determining a number of PUCCH resources to be transmitted from the at least one PUCCH resource includes: determining a first PUCCH resource corresponding to a CSI report with a highest priority in the case that the UE is not provided multi-CSI-PUCCH-ResourceList or PUCCH resources for transmissions of CSI reports associated with a beam do not overlap on the slot, in the case that there is a first set of PUCCH resources on the slot not overlapping with the first PUCCH resource, determining a second PUCCH resource corresponding to a CSI report with a highest priority from the first set of PUCCH resources; in the case that there is a second set of PUCCH resources on the slot overlapping with the first PUCCH resource while associated with another beam different from the first PUCCH resource, determining
  • the UCI multiplexing mode is separate UCI multiplexing.
  • ackNackFeedbackMode is configured as separate and two CORESETPoolIndex values are configured
  • a PUCCH resource carrying HARQ-ACK information with corresponding DCI associated with different CORESETPoolIndex values are not expected to be overlapped.
  • a radio access network (RAN) node which may include: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: transmit information indicating one or more PUCCH resources which are expected to be transmitted on a slot; and receive a number of PUCCH resources, wherein the number of PUCCH resource is determined from at least one PUCCH resource determined based on the one or more PUCCH resources and an UCI mode in a UE side and is equal to or smaller than a configured or predefined maximum number, and there is no overlapping PUCCH resources associated with a same beam in the number of PUCCH resources.
  • RAN radio access network
  • Embodiments of the present application provide a technical solution of uplink transmission, enhancing PUCCH transmission in scenarios of multiple panel simultaneous UL transmission and increasing efficiency of UL transmission, especially in common beam framework, and thus will facilitate the implementation of NR.
  • FIG. 1 is a schematic diagram illustrating an exemplary wireless communication system according to an embodiment of the present application.
  • FIG. 2 illustrates a flow chart of a method of uplink transmission according to some embodiments of the present application.
  • FIG. 3 illustrates a block diagram of an apparatus of uplink transmission according to some embodiments of the present application.
  • FIG. 4 illustrates a block diagram of an apparatus of uplink transmission according to some other embodiments of the present application.
  • FIG. 1 illustrates a schematic diagram of an exemplary wireless communication system 100 according to some embodiments of the present application.
  • the wireless communication system 100 includes at least one BS 101 and at least one UE 102.
  • the wireless communication system 100 includes one BS 101 and two UE 102 (e.g., a UE 102a and UE 102b) for illustrative purpose.
  • UE 102a and UE 102b e.g., a UE 102a and UE 102b
  • FIG. 1 a specific number of BSs and UEs are illustrated in FIG. 1 for simplicity, it is contemplated that the wireless communication system 100 may include more or less BSs and UEs in some other embodiments of the present application.
  • the wireless communication system 100 is compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the BS 101 may communicate with a core network (CN) node (not shown) , e.g., a mobility management entity (MME) or a serving gateway (S-GW) , a mobility management function (AMF) or a user plane function (UPF) etc. via an interface.
  • CN core network
  • MME mobility management entity
  • S-GW serving gateway
  • AMF mobility management function
  • UPF user plane function
  • a BS also be referred to as an access point, an access terminal, a base, a macro cell, a node-B, an enhanced node B (eNB) , a gNB, a home node-B, a relay node, or a device, or described using other terminology used in the art.
  • a BS may also refer to as a radio access network (RAN) node.
  • RAN radio access network
  • Each BS may serve a number of UE (s) within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • Neighbor BSs may communicate with each other as necessary, e.g., during a handover procedure for a UE.
  • a BS 101 may be configured with one TRP (or panel) , i.e., in a single-TRP scenario or more TRPs (or panels) , i.e., a multi-TRP scenario. That is, one or more TRPs are associated with the BS 101.
  • a TRP can act like a small BS.
  • a single TRP can be used to serve one or more UE 103 under the control of a BS 101.
  • a TRP may be referred to as different terms, which may be represented by a TCI state index or CORESETPoolIndex value etc. It should be understood that the TRP (s) (or panel (s) ) configured for the BS 101 may be transparent to a UE 102.
  • Two TRPs can have the same cell ID (identity or index) or different cell IDs.
  • Two TRPs can communicate with each other by a backhaul link.
  • a backhaul link may be an ideal backhaul link or a non-ideal backhaul link. Latency of the ideal backhaul link may be deemed as zero, and latency of the non-ideal backhaul link may be tens of milliseconds and much larger, e.g. on the order of tens of milliseconds, than that of the ideal backhaul link.
  • the UE 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • the UE may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE may include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the UE may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • At most two non-overlapping PUCCH resources can be transmitted on a slot.
  • at least one short PUCCH resource is included except that each of the two PUCCH resources carries at least HARQ-ACK information (or HARQ-ACK, or HARQ-ACK information bits) , which means two long PUCCH resources can be transmitted on a slot.
  • a short PUCCH resource it refers to a PUCCH resource including PUCCH format 0 or PUCCH format 2 (or PUCCH resource with PUCCH format 0 or PUCCH format 2) , which may have a duration of 1 to 2 symbols.
  • a long PUCCH resource refers to a PUCCH resource including PUCCH format 1, PUCCH format 3 or PUCCH format 4 (or PUCCH resource with PUCCH format 1, PUCCH format 3 or PUCCH format 4) , which may have a duration of 4 to 14 symbols.
  • multi-CSI-PUCCH-ResourceList In the case that there are PUCCH resources carrying only CSI reports (each PUCCH resource carrying one CSI report) on a slot, if multi-CSI-PUCCH-ResourceList is not configured, at most two non-overlapping PUCCH resources will be selected to be transmitted while at most 1 long PUCCH resource is selected; while, if multi-CSI-PUCCH-ResourceList is configured, one PUCCH resource from the multi-CSI-PUCCH-ResourceList will be selected according to the total CSI payload size on the slot.
  • multi-CSI-PUCCH-ResourceList when one or more PUCCH resources carrying CSI reports overlap with at least one PUCCH resource carrying at least one of: HARQ-ACK information bits in response to at least one SPS PDSCH reception or SR (hereafter, HARQ-ACK of SPS PDSCH/SR) , one PUCCH resource will be selected from the multi-CSI-PUCCH-ResourceList according to the UCI information bits of the CSI reports and HARQ-ACK of SPS PDSCH/SR.
  • a new PUCCH resource (same or different from the overlapped PUCCH resources) will be determined according to the total UCI bits of HARQ-ACK information and UCIs on the other PUCCH resource (s) and the PRI field.
  • a PUCCH resource will be selected from the SPS-PUCCH-AN-List according to the UCI payload size (bit number) .
  • multiple panel simultaneous UL transmission will be discussed, which may be supported for S-DCI and M-DCI based M-TRP.
  • (PUCCH+PUCCH) will be supported for M-DCI based M-TRP. Therefore, two overlapping PUCCH resources associated with different panels/TRPs can be transmitted simultaneously.
  • common beam framework will be applied for multiple panel simultaneous UL transmission if it is supported.
  • a beam it can also be represented in various manners, e.g., TCI state, spatial domain filter, or a reference signal etc.
  • One PUCCH resource can be indicated to be associated with one common beam based on common beam framework, and thus, two PUCCH resources associated with two different common beams can be identified to be associated with two panels/TRPs respectively.
  • UCI multiplexing on PUCCH resources can be performed per TRP.
  • a new PUCCH resource may be determined according to the total payload size of the multiplexed UCI. Therefore, it is possible that when multiplexing UCI on different PUCCH resources associated with one panel/TRP, a new PUCCH resource associated with the other panel/TRP is determined according to the legacy multiplexing rule. Therefore, legacy UCI multiplexing rule must be enhanced when UCI multiplexing is performed per TRP.
  • a UE can only transmit at most two PUCCH resources on a slot where only two long PUCCH resources are supported if each of the two PUCCH resources carries at least HARQ-ACK information; otherwise, at least one short PUCCH resource will be included in two selected PUCCH resources.
  • the related PUCCH transmission capability of the UE will be enhanced or unchanged when UCI multiplexing per TRP is performed has not been discussed yet. How to select the transmitted PUCCH resources after UCI multiplexing per TRP should also be solved.
  • embodiments of the present application propose a technical solution of uplink transmission, which specifies an enhanced UCI multiplexing rule, and also improve selection (or determination) of the PUCCH resources to be transmitted after UCI multiplexing per TRP.
  • FIG. 2 illustrates a flow chart of a method of uplink transmission according to some embodiments of the present application.
  • a UE in a remote side or UE side
  • a RAN node e.g., a gNB in a network side (or BS side)
  • the method implemented in the remote side and that implemented in the network side can be separately implemented and incorporated by other apparatus with similar functions.
  • no transmission or reception failure is considered in the illustrated embodiments of the present application.
  • the network side e.g., a gNB will transmit information indicating one or more PUCCH resources which are expected to be transmitted on a slot in step 201.
  • the gNB may configure one or more PUCCH resources to be transmitted on a slot for the UE by RRC signaling, e.g., one or more PUCCH resources for one or more CSI reports to be transmitted on a slot, or for HARQ-ACK information in response to one or more SPS PDSCH to be transmitted on a slot, or for SR to be transmitted on a slot.
  • the gNB may schedule one or more PUCCH resources to be transmitted on a slot for the UE by DCI, e.g., one or more PUCCH resources for HARQ-ACK information with corresponding DCI.
  • the one or more PUCCH resources may include PUCCH resources for different types of UCI by RRC signaling and/or DCI, e.g., at least one PUCCH resource for at least one CSI report, and/or at least one PUCCH for HARQ-ACK of SPS PDSCH/SR, and/or least one PUCCH for HARQ-ACK information with corresponding DCI.
  • UE supports multiple panel simultaneous UL transmission.
  • the UE can simultaneously transmit multiple PUCCH resources with different beams according to a RRC parameter or UE’s capability report. If it is indicated by the RRC parameter, the UE must report that it is capable to perform multi-panel simultaneous UL transmission firstly.
  • the UE will receive the information indicating the one or more PUCCH resources which are expected to be transmitted on a slot.
  • the UE will determine a number of PUCCH resources to be transmitted on the slot from at least one PUCCH resource, which is determined according to the one or more PUCCH resources and an UCI multiplexing mode.
  • the gNB will receive the number of PUCCH resources in step 205 (only PUCCH transmission is considered without considering conflict with other UL resources; otherwise, the number of PUCCH resources received in the network side may be part of all of the number of PUCCH resources determined in the UE side) .
  • the number of PUCCH resources is equal to or smaller than a maximum number, e.g., N max , which may be configured, e.g., by RRC signalling or predefined in 3GPP specification.
  • N max a maximum number
  • N max can be configured or predefined to be not smaller than 2 and not larger than 4.
  • UCI multiplexing mode two UCI multiplexing modes, e.g., separate UCI multiplexing mode (UCI multiplexing per TRP) or joint UCI multiplexing mode (joint UCI multiplexing for both two TRPs) will be illustrated in embodiments of the present application.
  • a UE may be configured with one of the two UCI multiplexing modes, e.g., by RRC or is fixed with one mode of the two UCI multiplexing modes according to some other configurations such as ackNackFeedbackMode etc.
  • ackNackFeedbackMode ackNackFeedbackMode etc.
  • Rel-16 multi-DCI based multi-TRP there are two modes for HARQ-ACK feedback, i.e., separate feedback mode and joint feedback mode.
  • the UCI multiplexing mode is separate UCI multiplexing. That is, UE is not expected to be configured or fixed as joint UCI multiplexing if ackNackFeedbackMode is separate and two CORESETPoolIndex values are configured.
  • Scenario 1 Separate UCI multiplexing mode-UCI multiplexing per TRP
  • a PUCCH resource can be associated with a beam which is associated with a TRP.
  • a PUCCH resource is associated with one common beam which is associated with a TRP, which can be indicated by a DCI, a media access control (MAC) control element (CE) or RRC signaling. All PUCCH resources associated with the same beam on a slot will be selected to perform the UCI multiplexing.
  • MAC media access control
  • CE control element
  • Case 1-1 UCI at least including HARQ-ACK information with corresponding DCI
  • - is not provided coresetPoolIndex or is provided coresetPoolIndex with a value of 0 for first CORESETs on active DL BWPs of serving cells, and
  • coresetPoolIndex with a value of 1 for second CORESETs on active DL BWPs of the serving cells
  • one resourceSetToAddModList is configured for PUCCH resource configuration.
  • An exemplary resourceSetToAddModList may include at most 4 PUCCH resource sets associated with two CORESETPoolIndex values (TRPs) , which are configured for HARQ-ACK information with corresponding DCI on a bandwidth part (BWP) of a cell for a UE.
  • TRPs CORESETPoolIndex values
  • BWP bandwidth part
  • Each PUCCH resource set includes PUCCH resources associated with different beams (each beam associated with a TRP) , e.g., PUCCH resources associated with a first beam of two common beams and PUCCH resources associated with a second beam of the two common beams.
  • a PUCCH resource (same or different from a PUCCH resource expected to be transmitted indicated by the network side) for carrying HARQ-ACK information with corresponding DCI associated with a beam (e.g., one of two common beams) can be determined from a PUCCH resource set determined from the resourceSetToAddModList according to a total bit number of the HARQ-ACK information. For each beam, at most one PUCCH resource for carrying HARQ-ACK information with corresponding DCI can be determined.
  • the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList and a total number of PUCCH resources associated with the beam in the first PUCCH resource set is larger than 8
  • the PUCCH resource is determined from all PUCCH resources associated with the beam in the first PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI and CORESET of the last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • the PUCCH resource is determined from all PUCCH resources associated with the beam in the PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • the PUCCH resource carrying HARQ-ACK information with corresponding DCI associated with a beam may overlap with other PUCCH resource (s) carrying other UCI information on a slot.
  • the PUCCH resource carrying HARQ-ACK information with corresponding DCI associated with a beam may overlap with at least one PUCCH resource carrying CSI report associated with the same beam on a slot, or overlap with at least one PUCCH resource carrying HARQ-ACK of SPS PDSCH and/or SR associated with the same beam on a slot, or overlap with at least one PUCCH resource carrying CSI report associated with the same beam and at least one PUCCH resource carrying HARQ-ACK of SPS PDSCH and/or SR associated with the same beam on a slot.
  • a PUCCH resource associated with the beam (same or different from the overlapped PUCCH resources) will be determined from a PUCCH resource set determined from the resourceSetToAddModList according to a total bit number of the HARQ-ACK information and the other UCI information.
  • the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList and a total number of PUCCH resources associated with the beam in the first PUCCH resource set is larger than 8
  • the PUCCH resource for multiplexing the HARQ-ACK information and the other UCI information is determined from all PUCCH resources associated with the beam in the first PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI and a CORESET of the last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • the PUCCH resource for multiplexing the HARQ-ACK information and the other UCI information is determined from all PUCCH resources associated with the beam in the PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • At most 8 PUCCH resources can be configured for a PUCCH resource set except for the first PUCCH resource set, and the PRI field has at most 3 bits to indicate one PUCCH resource from a PUCCH resource set.
  • the PRI field has at most 3 bits to indicate one PUCCH resource from a PUCCH resource set.
  • two resourceSetToAddModLists can be configured for PUCCH resource configuration.
  • two resourceSetToAddModLists each indicating at most 4 PUCCH resource sets for HARQ-ACK information with corresponding DCI per CORESETPoolIndex value (TRP) can be configured for a UE on a BWP of a cell. Since each common beam is associated with one CORESETPoolIndex value in M-DCI based M-TRP, each PUCCH resource set configured for a UE is associated with one common beam.
  • a PUCCH resource (same or different from a PUCCH resource expected to be transmitted indicated by the network side) for carrying HARQ-ACK information with corresponding DCI associated with a beam (e.g., one of two common beams) can be determined from a PUCCH resource set determined from a resourceSetToAddModList associated with the beam of the two resourceSetToAddModLists according to a total bit number of the HARQ-ACK information. For each beam, at most one PUCCH resource for carrying HARQ-ACK information with corresponding DCI can be determined.
  • the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList associated with the beam (e.g., the first beam) and a total number of PUCCH resources in the first PUCCH resource set is larger than 8
  • the PUCCH resource is determined from all PUCCH resources in the first PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI and a CORESET of the last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • the PUCCH resource is determined from all PUCCH resources in the PUCCH resource set associated with the beam according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • a PUCCH resource associated with the beam (same or different from the overlapped PUCCH resources) will be determined from a PUCCH resource set determined from a resourceSetToAddModList associated with the beam of the two resourceSetToAddModLists according to a total bit number of the HARQ-ACK information and the other UCI information.
  • the PUCCH resource set is a first PUCCH resource set determined from the resourceSetToAddModList associated with the beam and a total number of PUCCH resources in the first PUCCH resource set is larger than 8
  • the PUCCH resource is determined from all PUCCH resources in the first PUCCH resource set according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI and a CORESET of the last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • the PUCCH resource is determined from all PUCCH resources in the PUCCH resource set associated with the beam according to a PRI field in a last DCI corresponding to the HARQ-ACK information with corresponding DCI.
  • the corresponding RRC configuration of PUCCH in TS38.331 can be updated, e.g., as follows:
  • resourceSetToAddModList1 and resourceSetToReleaseList1 are associated with CORESETPoolIndex 0 which is associated with a first common beam
  • resourceSetToAddModList2 and resourceSetToReleaseList2 are associated with CORESTPoolIndex 1 which is associated with the second common beam.
  • a PUCCH resource for carrying HARQ-ACK information with corresponding DCI associated with a beam can be determined from a resourceSetToAddModList associated with the beam (e.g., resourceSetToAddModList1 associated with the first beam) of the two resourceSetToAddModLists, i.e., resourceSetToAddModList1 and esourceSetToAddModList2 according to the total bit number of the HARQ-ACK information.
  • resourceSetToAddModList1 may still use the same expression in legacy specification, i.e., resourceSetToAddModList.
  • the "resourceSetToAddModList" in the RRC configuration is only one specific configuration instance and should not be interpreted into only one resourceSetToAddModList being configured.
  • UCI information bits represented by O UCI , which include HARQ-ACK information bits in response to one or more SPS PDSCH receptions and SR (if any) associated with a same common beam will be determined firstly.
  • the UCI information to be determined include: HARQ-ACK information bits in response to one or more SPS PDSCH receptions, which are associated with one common beam according to the activated DCI of the SPS PDSCH; and SR (if any) associated with one common beam according to the common beam of a PUCCH resource configured for the SR.
  • one SPS-PUCCH-AN-List is configured.
  • a PUCCH resource (same or different from a PUCCH resource expected to be transmitted indicated by the network side) associated with the beam can be determined from all PUCCH resources associated with the beam of the SPS-PUCCH-AN-List according to a total number of bits of the UCI information.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained (or determined) from the first entry of all entries indicating the PUCCH resources associated with the same common beam in the SPS-PUCCH-AN-List, if O UCI ⁇ 2 including 1 or 2 HARQ-ACK information bits and a positive or negative SR on one SR transmission occasion if transmission of HARQ-ACK information and SR occurs simultaneously.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained from the second entry of all entries indicating the PUCCH resources associated with the same common beam in SPS-PUCCH-AN-List, if 2 ⁇ O UCI ⁇ N 1, SPS where N 1, SPS is either provided by maxPayloadSize obtained from the second entry in SPSPUCCH-AN-List or is otherwise equal to 1706.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained from the third entry of all entries indicating the PUCCH resources associated with the same common beam in SPS-PUCCH-AN-List, if N 1,SPS ⁇ O UCI ⁇ N 2, SPS where N 2, SPS is either provided by maxPayloadSize obtained from the third entry in SPS-PUCCH-AN-List or is otherwise equal to 1706.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained from the fourth entry of all entries indicating the PUCCH resources associated with the same common beam in SPS-PUCCH-AN-List, if N 2,SPS ⁇ O UCI ⁇ N 3, SPS where N 3, SPS is equal to 1706.
  • 8 PUCCH resources are configured in an exemplary SPS-PUCCH-AN-List, wherein the first 4 PUCCH resources in the SPS-PUCCH-AN-List are associated with a first common beam, and the last 4 PUCCH resources in the SPS-PUCCH-AN-List are associated with a second common beam. Then, if O UCI UCI information bits which only include HARQ-ACK of SPS PDSCH and SR (if any) associated with the first common beam, the first PUCCH resource in the SPS-PUCCH-AN-List is determined if O UCI ⁇ 2 because it is the first PUCCH resource associated with the first common beam in the SPS-PUCCH-AN-List.
  • the fifth PUCCH resource in the SPS-PUCCH-AN-List is determined if O UCI ⁇ 2 because it is the first PUCCH resource associated with the second common beam in the SPS-PUCCH-AN-List.
  • two SPS-PUCCH-AN-Lists are configured.
  • a PUCCH resource (same or different from a PUCCH resource expected to be transmitted indicated by the network side) can be determined from all PUCCH resources of a SPS-PUCCH-AN-List associated with the beam of the two SPS-PUCCH-AN-Lists according to a total number of bits of the UCI information.
  • each of the two SPS-PUCCH-AN-Lists are associated with one CORESETPoolIndex value of two CORESETPoolIndex values.
  • All PUCCH resources in each SPS-PUCCH-AN-List are associated with one CORESETPoolIndex value and further associated with one same common beam because one common beam is associated with one CORESETPoolIndex value in M-DCI based M-TRP.
  • the UE can determine a PUCCH resource for O UCI UCI information bits only including HARQ-ACK of SPS PDSCH and SR (if any) associated with a common beam as follows.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained from the first entry in a SPS-PUCCH-AN-List associated with the same common beam if O UCI ⁇ 2 including 1 or 2 HARQ-ACK information bits and a positive or negative SR on one SR transmission occasion if transmission of HARQ-ACK information and SR occurs simultaneously.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained from the second entry in a SPS-PUCCH-AN-List associated with the same common beam, if provided, if 2 ⁇ O UCI ⁇ N 1, SPS where N 1, SPS is either provided by maxPayloadSize obtained from the second entry in sps-PUCCH-AN-List or is otherwise equal to 1706.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained from the third entry in a SPS-PUCCH-AN-List associated with the same common beam, if N 1, SPS ⁇ O UCI ⁇ N 2, SPS where N 2, SPS is either provided by maxPayloadSize obtained from the third entry in sps-PUCCH-AN-List or is otherwise equal to 1706.
  • the PUCCH resource for carrying the HARQ-ACK of SPS PDSCH and SR (if any) will be obtained from the fourth entry in a SPS-PUCCH-AN-List associated with the same common beam, if N 2, SPS ⁇ O UCI ⁇ N 3, SPS where N 3, SPS is equal to 1706.
  • the corresponding RRC configuration of PUCCH in TS38.331 can be updated, e.g., as follows:
  • sps-PUCCH-AN-List1-r16 is associated with CORESETPoolIndex 0 (first TRP) which is associated with a first common beam
  • sps-PUCCH-AN-List2 is associated with CORESTPoolIndex 1 (second TRP) which is associated with the second common beam.
  • O UCI UCI information bits are associated with the first common beam and CORESETPoolIndex 0
  • a PUCCH resource on sps-PUCCH-AN-List1-r16 will be selected according to O UCI UCI information bits.
  • a PUCCH resource on sps-PUCCH-AN-List2 will be selected according to O UCI UCI information bits.
  • Case 1-3 UCI including CSI report (s) and HARQ-ACK of SPS PDSCH and/or SR if any
  • the UCI to be multiplexed on a slot associated with a beam includes CSI report (s) and HARQ-ACK of SPS PDSCH and/or SR (if any) associated with a beam.
  • CSI report s
  • HARQ-ACK of SPS PDSCH and/or SR if any
  • a plurality of PUCCH resources associated with a beam carrying a plurality of CSI reports are overlapping on the slot, wherein the UCI information includes the plurality of CSI reports.
  • At least one PUCCH resource associated with a beam carrying at least one CSI report and at least one other PUCCH resource associated with the beam carrying HARQ-ACK of SPS PDSCH and/or SR are overlapping on the slot, wherein the UCI information includes the at least one CSI report and the HARQ-ACK of SPS PDSCH and/or SR.
  • one multi-CSI-PUCCH-ResourceList is configured.
  • a PUCCH resource associated with the beam will be determined from all PUCCH resources associated with the beam of the multi-CSI-PUCCH-ResourceList according to a total bit number of the UCI information.
  • the maximum number of PUCCH resources configured in the multi-CSI-PUCCH-ResourceList may be increased to ensure the flexibility of UCI multiplexing per TRP/panel.
  • 4 PUCCH resources can be configured in multi-CSI-PUCCH-ResourceList where the first two PUCCH resources are associated with the first common beam, and the last 2 PUCCH resources are associated with the second common beam. If the multiplexed UCI bits are associated with the first common beam, then the first or second PUCCH resource is determined according to the UCI bits for the UCI multiplexing. If the multiplexed UCI bits are associated with the second common beam, then the third or fourth PUCCH resource is determined according to the UCI bits for the UCI multiplexing.
  • two multi-CSI-PUCCH-ResourceLists are configured.
  • a PUCCH resource associated with a beam will be determined from all PUCCH resources of a multi-CSI-PUCCH-ResourceList associated with the beam of the two multi-CSI-PUCCH-ResourceLists.
  • the corresponding RRC configuration of PUCCH in TS38.331 can be updated, e.g., as follows:
  • multi-CSI-PUCCH-ResourceList1 and multi-CSI-PUCCH-ResourceList2 are associated with CORESETPoolIndex 0 and 1 respectively, and they are further associated with the first and second common beam.
  • 2 PUCCH resources are configured per multi-CSI-PUCCH-ResourceList. If the multiplexed UCI bits are associated with the first common beam, then the first or second PUCCH resource from multi-CSI-PUCCH-ResourceList1 is determined according to the UCI bits for the UCI multiplexing. If the multiplexed UCI bits are associated with the second common beam, then the first or second PUCCH resource from multi-CSI-PUCCH-ResourceList2 is determined according to the UCI bits for the UCI multiplexing.
  • multi-CSI-PUCCH-ResourceList1 may still use the same expression in legacy specification, i.e., multi-CSI-PUCCH-ResourceList.
  • legacy specification i.e., multi-CSI-PUCCH-ResourceList.
  • multi-CSI-PUCCH-ResourceList the "multi-CSI-PUCCH-ResourceList" in the RRC configuration is only one specific configuration instance and should not be interpreted into only one multi-CSI-PUCCH-ResourceList being configured.
  • At least one PUCCH resource will be determined by the UE based on the one or more PUCCH resources indicated by the network side, which are expected to be transmitted on a slot. In some other scenarios, there may be no multiplexing is need.
  • the at least one PUCCH resource may be the one or more PUCCH resources indicated by the network side.
  • at most two non-overlapping PUCCH resources per TRP will be determined which means at most 2 non-overlapping PUCCH resources associated with one common beam will be determined, wherein, at most one long PUCCH resource can be determined.
  • N max PUCCH resources will be selected (or determined) from the at most 4 PUCCH resources.
  • the N max PUCCH resources are selected according to the highest UCI priority of each of the PUCCH resources (e.g., at most 4 PUCCH resources) after the separate UCI multiplexing.
  • An exemplary priority order of different types of UCI is: priority of HARQ-ACK information (HARQ-ACK with corresponding DCI and other HARQ-ACK information) is larger than that of SR, and priority of SR is larger than that of CSI report. If a PUCCH resource carrying multiple types of UCI, then the priority of the PUCCH resource is determined by the highest priority of the multiple types of UCI on the PUCCH resource. If two or more PUCCH resources have the same highest priority of the multiple types of UCIs, then the priority of the two or more PUCCH resources will be further determined in various manners.
  • the priority of the two or more PUCCH resources will be further determined by the second priority of the multiple types of UCIs on each PUCCH resource and so on.
  • the priority of the two or more PUCCH resources will be further determined by its associated CORSETPoolIndex value or its associated beam. For example, the PUCCH resource associated with CORESETPoolIndex 0 (the first TRP) or the first common beam will have a higher priority than CORESETPoolIndex 1 (the second TRP) or the second common beam.
  • legacy UCI multiplexing procedures can be reused for joint UCI multiplexing in the case of multi-panel simultaneous UL transmission. For example, if a UE is configured with multiple PUCCH resources on a slot to transmit CSI reports, then a first PUCCH resource is determined according to a CSI report with the highest priority, and a second PUCCH resource which is not overlapping with the first PUCCH resource is determined according to the priority and PUCCH format as follows according to TS 38.214.
  • the UE determines a first resource corresponding to a CSI report with the highest priority [6, TS 38.214]
  • the UE determines a CSI report with the highest priority, among the CSI reports with corresponding resources from the remaining resources, and a corresponding second resource as an additional resource for CSI reporting
  • the UE determines a CSI report with the highest priority, among the CSI reports with corresponding resources from the remaining resources, and a corresponding second resource as an additional resource for CSI reporting.
  • Embodiments of the present application enhance the selection of the second PUCCH resource carrying CSI report when UE supports multi-panel simultaneous UL transmission.
  • the second PUCCH resource can be selected from the overlapping PUCCH resources of the first PUCCH resource while associated with a different common beam of the first PUCCH resource in the common beam frame.
  • At most 2 PUCCH resources can be determined for CSI reports as follows, wherein zero or one (at most one) of the at most 2 PUCCH resources are long PUCCH resource.
  • a first PUCCH resource corresponding to a CSI report with the highest priority will be determined.
  • a third PUCCH resource corresponding to a CSI report with the highest priority will be determined from the first set of PUCCH resources, wherein at most one PUCCH resource of the first PUCCH resource and the third PUCCH resource is a long PUCCH resource.
  • the first PUCCH resource is a long PUCCH resource with PUCCH format 3 or 4
  • the third PUCCH resource will be a short PUCCH resource with PUCCH format 2
  • the first PUCCH resource is a short PUCCH resource with PUCCH format 2
  • the third PUCCH resource will be a long PUCCH resource with PUCCH format 3 or 4.
  • a fourth PUCCH resource corresponding to a CSI report with the highest priority will be determined from the second set of PUCCH resource on the slot.
  • at most one of the first PUCCH resource and the fourth PUCCH resource is a long PUCCH resource.
  • the fourth PUCCH resource will be a short PUCCH resource with PUCCH format 2; and if the first PUCCH resource is a short PUCCH resource with PUCCH format 2, the fourth PUCCH resource will be a long PUCCH resource with PUCCH format 3 or 4.
  • a PUCCH resource with a higher priority from the third PUCCH resource and the fourth PUCCH resource will be determined as the second PUCCH resource to be transmitted on the slot.
  • At most 2 PUCCH resources can be determined for CSI reports as follows, wherein zero, or one or both (at most two) of the at most 2 PUCCH resources are long PUCCH resource.
  • a first PUCCH resource corresponding to a CSI report with the highest priority will be determined in the case that the UE is not provided multi-CSI-PUCCH-ResourceList or PUCCH resources for transmissions of CSI reports associated with a beam do not overlap on the slot.
  • a third PUCCH resource corresponding to a CSI report with the highest priority will be determined from the first set of PUCCH resources, wherein at most one of the first PUCCH resource and the third PUCCH resource is a long PUCCH resource.
  • the first PUCCH resource is a long PUCCH resource with PUCCH format 3 or 4
  • the third PUCCH resource will be a short PUCCH resource with PUCCH format 2
  • the first PUCCH resource is a short PUCCH resource with PUCCH format 2
  • the third PUCCH resource will be a long PUCCH resource with PUCCH format 3 or 4.
  • a fourth PUCCH resource corresponding to a CSI report with the highest priority will be determined from the second set of PUCCH resource on the slot.
  • Both the first PUCCH resource and the fourth PUCCH resource can be long PUCCH resource, e.g., with PUCCH format 3 or 4.
  • a PUCCH resource with a higher priority from the third PUCCH resource and the fourth PUCCH resource will be determined as the second PUCCH resource to be transmitted on the slot.
  • ackNackFeedbackMode is configured as "separate" in M-DCI based M-TRP where two different CORESETPoolIndex values are configured, the HARQ-ACK corresponding to different CORESETPoolIndex values will be transmitted by different PUCCH resources.
  • the scheduling limitation of PUCCHs carrying HARQ-ACK information with corresponding DCI will be as the same as legacy specification, wherein PUCCHs carrying HARQ-ACK information with corresponding DCI associated with different CORESETPoolIndex values (different TRPs) are not expected to be overlapped if ackNackFeedbackMode is set to "separate, " even if the UE supports multi-panel simultaneous UL transmission.
  • UE is not expected to be configured or fixed as joint UCI multiplexing if ackNackFeedbackMode is set "separate" and two CORESETPoolIndex values are configured, which means that UE is expected to configured or fixed as separate UCI multiplexing. Accordingly, there is no scheduling limitation of PUCCHs carrying HARQ-ACK information with corresponding DCI as legacy specification when UE supports multi-panel simultaneous UL transmission.
  • embodiments of the present application also propose an apparatus of uplink transmission.
  • FIG. 3 illustrates a block diagram of an apparatus of uplink transmission 300 according to some embodiments of the present application.
  • the apparatus 300 may include at least one non-transitory computer-readable medium 301, at least one receiving circuitry 302, at least one transmitting circuitry 304, and at least one processor 306 coupled to the non-transitory computer-readable medium 301, the receiving circuitry 302 and the transmitting circuitry 304.
  • the at least one processor 306 may be a CPU, a DSP, a microprocessor etc.
  • the apparatus 300 may be a RAN node, e.g., a gNB or a remote apparatus, e.g., UE configured to perform a method illustrated in the above or the like.
  • the at least one processor 306, transmitting circuitry 304, and receiving circuitry 302 are described in the singular, the plural is contemplated unless a limitation to the singular is explicitly stated.
  • the receiving circuitry 302 and the transmitting circuitry 304 can be combined into a single device, such as a transceiver.
  • the apparatus 300 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 301 may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to the network apparatus as described above.
  • the computer-executable instructions when executed, cause the processor 306 interacting with receiving circuitry 302 and transmitting circuitry 304, so as to perform the steps with respect to the RAN node or network apparatus, e.g., a gNB as depicted above.
  • the non-transitory computer-readable medium 301 may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to the UE as described above.
  • the computer-executable instructions when executed, cause the processor 306 interacting with receiving circuitry 302 and transmitting circuitry 304, so as to perform the steps with respect to the UE as illustrated above.
  • FIG. 4 is a block diagram of an apparatus of uplink transmission according to some other embodiments of the present application.
  • the apparatus 400 may include at least one processor 402 and at least one transceiver 404 coupled to the at least one processor 402.
  • the transceiver 404 may include at least one separate receiving circuitry 406 and transmitting circuitry 404, or at least one integrated receiving circuitry 406 and transmitting circuitry 404.
  • the at least one processor 402 may be a CPU, a DSP, a microprocessor etc.
  • the processor when the apparatus 400 is a remote apparatus, e.g., a UE, the processor is configured to: receive information indicating one or more PUCCH resources which are expected to be transmitted on a slot; and determine a number of PUCCH resources to be transmitted on the slot from at least one PUCCH resource determined according to the one or more PUCCH resources and an UCI multiplexing mode, wherein the number of PUCCH resources is equal to or smaller than a configured or predefined maximum number and there is no overlapping PUCCH resources associated with a same beam in the number of PUCCH resources.
  • the processor may be configured to: transmit information indicating one or more PUCCH resources which are expected to be transmitted on a slot; and receive a number of PUCCH resources, wherein the number of PUCCH resource is determined from at least one PUCCH resource determined based on the one or more PUCCH resources and an UCI mode in a UE side and is equal to or smaller than a configured or predefined maximum number, and there is no overlapping PUCCH resources associated with a same beam in the number of PUCCH resources.
  • the method according to embodiments of the present application can also be implemented on a programmed processor.
  • the controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device capable of implementing the flowcharts shown in the figures may be used to implement the processor functions of this application.
  • an embodiment of the present application provides an apparatus, including a processor and a memory. Computer programmable instructions for implementing a method are stored in the memory, and the processor is configured to perform the computer programmable instructions to implement the method.
  • the method may be a method as stated above or other method according to an embodiment of the present application.
  • An alternative embodiment preferably implements the methods according to embodiments of the present application in a non-transitory, computer-readable storage medium storing computer programmable instructions.
  • the instructions are preferably executed by computer-executable components preferably integrated with a network security system.
  • the non-transitory, computer-readable storage medium may be stored on any suitable computer readable media such as RAMs, ROMs, flash memory, EEPROMs, optical storage devices (CD or DVD) , hard drives, floppy drives, or any suitable device.
  • the computer-executable component is preferably a processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device.
  • an embodiment of the present application provides a non-transitory, computer-readable storage medium having computer programmable instructions stored therein.
  • the computer programmable instructions are configured to implement a method as stated above or other method according to an embodiment of the present application.
  • the terms “includes, “ “including, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.
  • the term “another” is defined as at least a second or more.
  • the terms “having, “ and the like, as used herein, are defined as “including. "

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente demande concernent un procédé et un appareil de transmission de liaison montante. Un procédé donné à titre d'exemple inclut : la réception d'informations indiquant une ou plusieurs ressources PUCCH dont la transmission sur un créneau est attendue; et la détermination d'un nombre de ressources PUCCH à transmettre sur le créneau parmi au moins une ressource PUCCH déterminée selon la ou les ressources PUCCH et un mode de multiplexage UCI, le nombre de ressources PUCCH étant égal ou inférieur à un nombre maximal configuré ou prédéfini et il n'y a pas de ressources PUCCH de chevauchement associées à un même faisceau dans le nombre de ressources PUCCH.
PCT/CN2022/112979 2022-08-17 2022-08-17 Procédé et appareil de transmission de liaison montante WO2024036503A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/112979 WO2024036503A1 (fr) 2022-08-17 2022-08-17 Procédé et appareil de transmission de liaison montante

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/112979 WO2024036503A1 (fr) 2022-08-17 2022-08-17 Procédé et appareil de transmission de liaison montante

Publications (1)

Publication Number Publication Date
WO2024036503A1 true WO2024036503A1 (fr) 2024-02-22

Family

ID=89940372

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/112979 WO2024036503A1 (fr) 2022-08-17 2022-08-17 Procédé et appareil de transmission de liaison montante

Country Status (1)

Country Link
WO (1) WO2024036503A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324786A1 (en) * 2017-05-05 2018-11-08 Nokia Technologies Oy Resource determination for uplink control channel for wireless networks
WO2021022519A1 (fr) * 2019-08-07 2021-02-11 Lenovo (Beijing) Limited Appareil et procédé de multiplexage uci dans des ressources pucch pour de multiples trps
WO2022067865A1 (fr) * 2020-10-02 2022-04-07 Apple Inc. Traitement de collisions dans le sens montant pour une opération avec plusieurs points d'émission-réception

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324786A1 (en) * 2017-05-05 2018-11-08 Nokia Technologies Oy Resource determination for uplink control channel for wireless networks
WO2021022519A1 (fr) * 2019-08-07 2021-02-11 Lenovo (Beijing) Limited Appareil et procédé de multiplexage uci dans des ressources pucch pour de multiples trps
WO2022067865A1 (fr) * 2020-10-02 2022-04-07 Apple Inc. Traitement de collisions dans le sens montant pour une opération avec plusieurs points d'émission-réception

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Maintenance on SPS PDSCH", 3GPP DRAFT; R1-2101178, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 19 January 2021 (2021-01-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051971396 *

Similar Documents

Publication Publication Date Title
JP5987231B2 (ja) 拡張物理ダウンリンク制御チャネル（ｅＰＤＣＣＨ）における改善
CN112602283A (zh) 用于下行链路控制信道的下行链路指派
CN111971925A (zh) 配置带宽部分
CN112219413A (zh) 通过多种无线电接入类型进行的v2x通信
CN114008955A (zh) 对用于混合自动重传请求过程的新数据指示符进行响应
CN112567874A (zh) 基于空闲信道评估的带宽部分配置
US20220286235A1 (en) Dynamic Retransmission Configuration
KR20210048490A (ko) 상향 신호의 송신 방법 및 디바이스
US10904713B2 (en) Enhancing group communication services
CN112655268A (zh) 消息3缓冲区中的媒体访问控制协议数据单元
US20140045507A1 (en) Code rate adaptation in wireless communication systems
US9722719B2 (en) Method of handling HARQ resource in TDD system and related communication device
US11159290B2 (en) Device and method for handling a sounding reference signal transmission
WO2017033091A1 (fr) Retard d'activation pour scell (cellule secondaire) de canal pucch en fonction d'une réponse de liaison montante
US20140045508A1 (en) Code rate adaptation in wireless communication systems
US9160475B2 (en) Method of handling HARQ resource in TDD system and related communication device
WO2023050402A1 (fr) Procédé et appareil de détermination de faisceau
WO2024036503A1 (fr) Procédé et appareil de transmission de liaison montante
WO2023283876A1 (fr) Procédé et appareil de transmission en liaison montante
WO2024073945A1 (fr) Procédé et appareil de détermination de faisceau
WO2024031536A1 (fr) Procédé et appareil de transmission de liaison montante
WO2023216233A1 (fr) Procédé et appareil de détermination de valeur associée à un élément d'antenne
US20240267922A1 (en) Method and apparatus for physical uplink control channel (pucch) transmission
US20230345504A1 (en) Device and Method for Handling a Multi-cell Scheduling
WO2024007245A1 (fr) Procédé et appareil d'adaptation dynamique d'éléments spatiaux

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22955285

Country of ref document: EP

Kind code of ref document: A1