WO2020041269A1 - Gestion de collision pour transmissions d'informations de commande de liaison montante - Google Patents

Gestion de collision pour transmissions d'informations de commande de liaison montante Download PDF

Info

Publication number
WO2020041269A1
WO2020041269A1 PCT/US2019/047205 US2019047205W WO2020041269A1 WO 2020041269 A1 WO2020041269 A1 WO 2020041269A1 US 2019047205 W US2019047205 W US 2019047205W WO 2020041269 A1 WO2020041269 A1 WO 2020041269A1
Authority
WO
WIPO (PCT)
Prior art keywords
uci
priority
slot
pucch
base station
Prior art date
Application number
PCT/US2019/047205
Other languages
English (en)
Inventor
Gang Xiong
Yushu Zhang
Original Assignee
Intel Corporation
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 Intel Corporation filed Critical Intel Corporation
Publication of WO2020041269A1 publication Critical patent/WO2020041269A1/fr

Links

Classifications

    • 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
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • 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
    • 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/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • aspects pertain to wireless communications. Some aspects relate to wireless networks including 3 GPP (Third Generation Partnership Project) networks, 3 GPP LTE (Long Term Evolution) networks, 3 GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks and 5G-LTE networks. Other aspects are directed to systems and methods for handling collisions between uplink control information (UCI) transmissions. More specifically, aspects are directed to mechanisms for collision handling between single-slot / multi -slot channel state information (CSI) transmissions on physical uplink control channels (PUCCHs) or physical uplink shared channels (PUSCHs).
  • UCI uplink control information
  • PUCCHs physical uplink control channels
  • PUSCHs physical uplink shared channels
  • 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.
  • RATs new radio access technologies
  • mmWave millimeter wave
  • LTE operation in the unlicensed spectrum includes (and is not limited to) the LTE operation in the unlicensed spectrum via dual connectivity (DC), or DC-based LAA, and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without requiring an“anchor” in the licensed spectrum, called MulteFire.
  • MulteFire combines the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments.
  • Such enhanced operations can include techniques for collision handling between single-slot / multi-slot UCI transmissions, such as CSI transmissions on
  • FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.
  • FIG. 1B and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. 2 illustrates a timeline check for multiplexing of PUCCH and PUSCII, in accordance with some aspects.
  • FIG. 3 illustrates dropping of a CSI report with lower priority in overlapped slots, in accordance with some aspects.
  • FIG. 4 illustrates dropping of a CSI report with lower priority in overlapped slots and after overlapped slots, in accordance with some aspects.
  • FIG. 5 illustrates an exampl e of handling a colli sion between multiple non-overlapping single-slot and multi -slot PUCCH transmissions, in accordance with some aspects.
  • FIG. 6 illustrates another example of handling a collision between multiple non-overlapping single-slot and multi -slot PUCCH transmissions, in accordance with some aspects.
  • FIG. 7 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects.
  • eNB evolved Node-B
  • gNB new generation Node-B
  • AP access point
  • STA wireless station
  • MS mobile station
  • UE user equipment
  • FIG. 1 A illustrates an architecture of a network in accordance with some aspects.
  • 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.
  • PDAs Personal Data Assistants
  • 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.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • LTE and LTE-Advanced are standards for wireless
  • 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.
  • carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.
  • aspects 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 (ESA) 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).
  • ESA Licensed Shared Access
  • SAS Spectrum Access System
  • Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multi carrier (FBMC), OF DMA, etc.) and in particular 3 GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.
  • any of the UEs 101 and 102 can comprise an
  • any of the UEs 101 and 102 can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB-IoT
  • FeNB-IoT Further Enhanced
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • eMTC enhanced MTC
  • FeMTC enhanced MTC
  • the UEs 101 and 102 may be configured to connect, e.g., communi cati vely couple, with a radio access network (RAN) 110.
  • the RAN 1 10 may be, for example, an Evolved Universal Mobile T el ecommuni cati on s System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile T el ecommuni cati on s System
  • E-UTRAN Evolved Universal Mobile T el ecommuni cati on s System
  • NG RAN NextGen 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 Tel ecom m uni cati ons System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to- Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Tel ecom m uni cati ons System
  • LTE Long
  • 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 si delink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point
  • 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.
  • WiFi® wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • These access nodes 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).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNBs Next Generation NodeBs
  • 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).
  • the communication nodes 111 and 1 12 can be transmission/reception points (TRPs)
  • TRPs transmission/reception points
  • the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs)
  • one or m ore 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 1 1 1, and one or more RAN nodes for providing femtocells or pi cocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.
  • LP low power
  • any of the R AN nodes 1 1 1 and 1 12 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 1 12 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.
  • RNC radio network controller
  • any of the nodes 1 11 and/or 112 can be a new generation node-B (gNB), an evolved node-B (eNB), or another type of RAN node.
  • gNB new generation node-B
  • eNB evolved node-B
  • the RAN 1 10 is shown to be communi cati v el y coupled to a core network (CN) 120 via an Sl interface 113.
  • 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. 1 B-1 I).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S l interface 1 13 is split into two parts: the Sl-U interface 1 14, which carries traffic data between the RAN nodes 1 1 1 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 1 1 1 and 112 and MMEs 121
  • the CN 120 comprises the MMEs 121 , the S-GW
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related
  • 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.
  • the HSS 124 can provide support for
  • the S-GW 122 may terminate the Sl interface 113 towards the
  • 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.
  • 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.
  • 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.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • 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, P IT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
  • VoIP Voice-over- Internet Protocol
  • P IT sessions P IT sessions
  • group communication sessions social networking services, etc.
  • 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.
  • PCRF Policy and Charging Rules Function
  • IP -CAN IP Access Network
  • HPLMN Home PCRF
  • V-PCRF Visited PCRF
  • VPN Visited Public Land Mobile Network
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140 A can be an IoT network.
  • One of the current enablers of IoT is the narrowband-IoT (NB-IoT).
  • a NG system architecture can include the RAN 1 10 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
  • the AMF access and mobility function
  • UPF user plane function
  • the AMF and the UPF can be communi cati vel y coupled to the gNBs and the NG-eNBs via NG interfaces.
  • 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.
  • the NG system architecture can use reference points between various nodes as provided by 3 GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12).
  • TS Technical Specification
  • 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.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • 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.
  • 5GC 5G core
  • 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)/home 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 sendees.
  • DN data network
  • 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 a network policy.
  • the UPF 134 can be deployed in one or more configurations according to a 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).
  • 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).
  • IMS IP multimedia subsystem
  • CSCFs call session control functions
  • 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. 1B), 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 aspects 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.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
  • the UDMZHSS 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.
  • FIG. IB illustrates the following reference points: Nl (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), Nl 1 (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. IE can also be used.
  • FIG. 1C illustrates a 5G system architecture 140C and a service- based representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 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.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 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), a Nudm 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 158 A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the a service-based interface exhibited by the
  • short PUCCH (PUCCFI formats 0 and 2) can span 1 or 2 symbols and long PUCCH (PUCCH formats 1, 3 and 4) can span from 4 to 14 symbols within a slot.
  • long PUCCH may span multiple slots to further enhance the coverage.
  • two short PUCCHs as well as short PUCCFI and long PUCCFI can be multiplexed in a TDM manner in a same slot.
  • uplink control information (UCI) can be carried by PUCCH or PUSCH.
  • UCI may include a scheduling request (SR), a hybrid automatic repeat request - ackn owl edgem ent (HARQ-ACK) feedback, a channel state information (CSI) report.
  • the CSI report may include a channel quality indicator (CQI), a pre-coding matrix indicator (PMI), a CSI resource indicator (CRI), and a rank indicator (RI) and/or beam related information (e g., Ll-RSRP (layer 1- reference signal received power)).
  • CQI channel quality indicator
  • PMI pre-coding matrix indicator
  • CRI rank indicator
  • Ll-RSRP layer 1- reference signal received power
  • the UE may multiplex all UCIs on either one PUCCH or one PUSCH, using the existing UCI multiplexing rule, if both of the following conditions are satisfied (as illustrated in diagram 200 of FIG. 2):
  • the UE If at least one pair of overlapping channels does not meet the above timeline requirements, the UE consider it is an error case for all UL channels in the group of overlapping channels. In this case, the UE behavior is not specified in a 3 GPP TS document.
  • FIG. 2 illustrates a timeline check for multiplexing of PUCCH and PUSCH, in accordance with some aspects.
  • FIG. 2 illustrates a diagram 200 of one example of a timeline check for multiplexing of PUCCH and PUSCH.
  • the above timeline requirement is satisfied.
  • the PUCCH carrying the HARQ-ACK feedback is dropped and HARQ-ACK feedback is piggybacked on the PUSCH
  • a long PUCCH with multiple slot duration can be used to carry HARQ-ACK feedback in order to improve the link budget and extend the coverage.
  • multi -slot PUCCH can be used to carry CSI report and SR to improve the coverage for other UCI types.
  • certain multiplexing rule needs to be defined to ensure alignment between the gNB and the UE.
  • Techniques disclosed herein include techniques for collision handling between singl e- sl ot/ mul ti -sl ot CSI PUCCHs, such as multiplexing single-slot and/or multi-slot PUCCH carrying CSI reports, multiplexing single- slot and/or multi-slot PUCCH/PUSCH carrying mixed UCI types, and handling collision between multiple non-overlapping single-slot and multi-slot PUCCH.
  • the UCI when a single slot PUCCH overlaps with multi - slot PUSCH repetition in a slot, if the above timeline requirement is met for the overlapped slot, the UCI may be multiplexed on PUSCH in the overlapped slot; otherwise, it may be considered as an error case for the overlapped slot.
  • the PUSCH may be dropped without deferral in overlapping slots if the timeline requirement within the overlapping slots is met; otherwise; it may be considered as an error case for overlapping slots.
  • multi -slot PUCCH can be used to carry CSI report and SR to improve the coverage for other UCI types.
  • certain multiplexing rules may be defined to ensure alignment between gNB and UE.
  • PUCCH carrying CSI reports are provided hereinbelow.
  • a single slot or a multi-slot PUCCH carrying a first CSI report overlaps with a single slot or a multi -slot PUCCH repetition carrying a second CSI report in a slot
  • the timeline requirement is satisfied for the overlapped slot
  • the UE is not provided high layer parameter multi-CSI-PUCCH-ResourceList
  • the CSI report with lower priority is dropped in the overlapped slot and the UE transmits the PUCCH carrying CSI with higher priority; otherwise it is considered as an error case for the overlapped slot.
  • the timeline requirement (as discussed in connection with FIG. 2) may not need to be satisfied in the overlapped slot for PUCCH carrying CSI report.
  • the UE may drop the CSI report with lower priority regardless of whether the UE is not provided high layer parameter multi-CSI-PUCCH-ResourceList.
  • a single slot or a multi-slot PUCCH carrying a first CSI report overlaps with single slot or multi - slot PUCCH repetition carrying a second CSI report in a slot
  • the UE multiplexes the CSI reports in a PUCCH which is selected based on capacity of configured PUCCH resource and combined CSI payload size.
  • the same principle can be applied for the case when a single-slot/multi-slot PUCCH carrying periodic and/or semi -persistent CSI report overlaps with a single-slot/multi-slot PUSCH carrying aperiodic CSI (A-CSI) report. More specifically, the UE may drop the CSI report with lower priority and transmit the CSI report with higher priority, i.e., A-CSI report on PUSCH in the overlapped slot.
  • A-CSI periodic CSI
  • dropping may apply for all the PUCCH or PUSCH transmi ssions carrying a CSI report with lower priority, which is not limited to the overlapped slot.
  • the UE may only drop the PUCCH carrying a CSI report with a lower priority in the slots including and after the overlapped slot.
  • FIG. 3 illustrates a diagram 300 of dropping a CSI report with lower priority in overlapped slots, in accordance with some aspects.
  • CSI #2 report has lower priority than CSI #1
  • UE would drop PUCCH carrying CSI #2 in the overlapped slots.
  • FIG. 4 illustrates a diagram 400 of dropping a CSI report with lower priority in overlapped slots and after overlapped slots, in accordance with some aspects.
  • the UE would drop the PUCCH carrying CSI #2 including, and after, the overlapped slots.
  • the UE may prioritize the UCI type with the following order (where“>” indicates“higher priority than”): dynamic HARQ-ACK feedback > SR > CSI report with higher priority > CSI report with lower priority > SPS HARQ-ACK feedback.
  • the dropping may apply for all the PUCCH or PUSCH transmission the UCI with lower priority or only the overlapped slot or the slots including and after the overlapped slots.
  • the UE may transmit the SR on PUCCH with earliest starting symbol/slot or with lowest SR ID on the overlapped slot.
  • the dropping may apply for all the PUCCH carrying SR or only the overlapped slot or the slots including and after the overlapped slots.
  • the UE within a PUCCH group, when a single slot or a multi-slot PUCCH carrying a first UCI type overlaps with a single slot or a multi-slot PUCCH repetition carrying a second UCI type in a slot, if the timeline requirement is satisfied for the overlapped slot, the UE would multiplex UCI on a single PUCCH/PUSCH in the overlapped slot in accordance with a multiplexing rule (e.g., as may be defined in a 3 GPP TS).
  • a multiplexing rule e.g., as may be defined in a 3 GPP TS.
  • the overlapped slots when multiple non- overlapping single-slot PUCCHs overlap with multi-slot PUCCH with repetition, if the timeline requirement is satisfied, all the UCIs on multiple non- overlapping single-slot PUCCHs are multiplexed in a single PUCCH resource.
  • the UCI on the multi-slot PUCCH is dropped and all the UCIs on the determined single slot PUCCH can be transmitted; otherwise, all the UCIs on the determined single slot PUCCH may be dropped and the UCI on the multi -slot PUCCH is transmitted.
  • a priority rule can be defined as follows: FLARQ-
  • FIG. 5 illustrates a diagram 500 of an example handling a collision between multiple non-overlapping single-slot and multi-slot PUCCH transmissions, in accordance with some aspects.
  • UCI#2 has higher priority than UCI#l.
  • UCI#2 and #3 are first multiplexed on a single PUCCH resource, and given that UCI#2 has higher priority than UCI#1, UCI#l on multi-slot PUCCH is dropped in the overlapped slot and a single slot PUCCH carrying UCI#2 and #2 is transmitted.
  • FIG. 6 illustrates a diagram 600 of another example handling a collision between multiple non-overlapping single-slot and multi-slot PUCCH transmissions, in accordance with some aspects.
  • the priority order is UCI#2 > UCI#l > UCI#3. In this case, only UCI#2 is transmitted and the other UCIs are dropped in the overlapped slot.
  • a system and method of wireless communication for a 5G or NR system includes, determined by UE, a multiplexing rule when a multiple-slot physical uplink control channel (PUCCH) carrying a first uplink control information (UCI) type overlaps with single-slot or multiple-slot PUCCH or physical uplink shared channel (PIJSCH) carrying a second UCI type.
  • the UE may transmit one of the first and second UCI type in a single PUCCH or PUSCH resource in the overlapped slot(s) if the timeline requirement is satisfied for the overlapped slot in accordance with the priority order of the first and second UCI type.
  • the first UCI type may be same or different from the second UCI type.
  • the first and second UCI type may include hybrid automatic repeat request - acknowledgement (HARQ-ACK), scheduling request (SR) and channel state information (CSI) report.
  • HARQ-ACK hybrid automatic repeat request - acknowledgement
  • SR scheduling request
  • CSI channel state information
  • a single slot or a multi-slot PUCCH carrying a first CSI report overlaps with single slot or multi - slot PUCCH repetition carrying a second CSI report in a slot
  • the UE always drops the CSI report with lower priority regardless of whether UE is not provided high layer parameter multi -CSI-PUCCH-ResourceList.
  • a single slot or a multi-slot PUCCH carrying a first CSI report overlaps with a single slot or a multi-slot PUCCH repetition carrying a second CSI report in a slot, if the timeline requirement is satisfied for the overlapped slot and if the UE is provided high layer parameter multi-CSI-PUCCH-
  • the UE multiplexes the CSI reports in a PUCCH which is selected based on capacity of configured PUCCH resource and combined CSI payload size.
  • dropping may apply for all the PUCCH or PUSCH transmission carrying CSI report with lower priority, which is not limited to the overlapped slot.
  • the UE would only drop the PUCCH carrying CSI report with lower priority in the slots including and after the overlapped slot.
  • the UE when a single slot or a multi -slot PUCCH carrying a first UCI type overlaps with single slot or multi -slot PUCCH repetition carrying a second UCI type in a slot, if the timeline requirement is satisfied for the overlapped slot, the UE would prioritize the UCI type with the following order: dynamic HARQ-ACK > SR > CSI report with higher priority > CSI report with lower priority > SPS HARQ-ACK feedback [0079]
  • the HE when a single slot or a multi-slot PUCCH carrying a first SR overlaps with single slot or multi-slot PUCCH repetition carrying a second SR in a slot, the HE would transmit the SR on a PUCCH with earliest starting symbol/slot or with lowest SR ID on the overlapped slot
  • the UE within a PUCCH group, when a single slot or a multi-slot PUCCH carrying a first UCI type overlaps with a single slot or a multi-slot PUCCH repetition carrying a second UCI type in a slot, if the timeline requirement is satisfied for the overlapped slot, the UE would multiplex UCI on a single PUCCH/PUSCH in the overlapped slot in accordance with the multiplexing rule which is defined current specification.
  • the overlapped slots when multiple non- overlapping single-slot PUCCHs overlap with multi-slot PUCCH with repetition, if the timeline requirement is satisfied, all the UCIs on multiple non overlapping single-slot PUCCHs are multiplexed in a single PUCCH resource.
  • the UCI on the multi-slot PUCCH is dropped and all the UCIs on the determined single slot PUCCH is transmitted; otherwise, all the UCIs on the determined single slot PUCCH is dropped and the UCI on multi-slot PUCCH is transmitted.
  • the overlapped slots when multiple non-overlapping single slot PUCCHs overlap with multi-slot PUCCH with repetition, if the timeline requirement is satisfied, only the UCI with the highest priority is transmitted and other UCIs are dropped.
  • FIG. 7 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a next generation Node-B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects and to perform one or more of the techniques disclosed herein.
  • the communication device 700 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • Circuitry e.g., processing circuitry
  • circuitry is a collection of circuits implemented intangible entities of the device 700 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating. In an example, the hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired).
  • the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructi ons of the specific operation.
  • variably connected physical components e.g., execution units, transistors, simple circuits, etc.
  • machine-readable medium e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.
  • the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa.
  • the instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation.
  • the machine-readable medium el ements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating.
  • any of the physi cal components may be used in more than one member of more than one circuitry.
  • execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the device 700 follow.
  • the device 700 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 700 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments.
  • the communication device 700 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the communication device 700 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single
  • communication device is illustrated, the term "communication device” shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.
  • cloud computing software as a service
  • SaaS software as a service
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device-readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • the software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Communication device 700 may include a hardware processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 704, a static memory 706, and mass storage 707 (e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus) 708.
  • a hardware processor 702 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 704 e.g., main memory 704
  • static memory 706 e.g., hard drive, tape drive, flash storage, or other block or storage devices
  • the communication device 700 may further include a display device 710, an alphanumeric input device 712 (e.g., a keyboard), and a user interface (UI) navigation device 714 (e.g., a mouse).
  • UI user interface
  • the display device 710, input device 712 and UI navigation device 714 may be a touchscreen display.
  • the communication device 700 may additionally include a signal generation device 718 (e.g., a speaker), a network interface device 720, and one or more sensors 721, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • GPS global positioning system
  • the communication device 700 may include an output controller 728, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc ).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc ).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 707 may include a communication device- readable medium 722, on which is stored one or more sets of data structures or instructions 724 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 702, the m ain memory 704, the static memory 706, and/or the mass storage 707 may be, or include (completely or at least partially), the device- readable medium 722, on which is stored the one or more sets of data structures or instructions 724, embodying or utilized by any one or more of the techniques or functions described herein.
  • one or any combination of the hardware processor 702, the main memory 704, the static memory 706, or the mass storage 716 may constitute the device-readable medium 722.
  • communication device-readable medium 722 is illustrated as a single medium, the term "communication device-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 724.
  • the term "communication device-readable medium” is inclusive of the terms“machine-readable medium” or“computer-readable medium”, and may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions 724) for execution by the communication device 700 and that cause the communication device 700 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media.
  • communication device-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g.,
  • communication device-readable media may include n on-transitory
  • communication device-readable media may include communication device-readable media that is not a transitory propagating signal.
  • the instructions 724 may further be transmitted or received over a communications network 726 using a transmission medium via the network interface device 720 utilizing any one of a number of transfer protocols.
  • the network interface device 720 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 726.
  • the network interface device 720 may include a plurality of antennas to wirelessly communicate using at least one of single-input-multiple-output (SIMO), MIMO, or multiple-input- single-output (MISO) techniques.
  • SIMO single-input-multiple-output
  • MISO multiple-input- single-output
  • the network interface device 720 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 700, and includes digital or analog communications signals or another intangible medium to facilitate
  • a transmission medium in the context of this disclosure is a device-readable medium.

Landscapes

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

Abstract

L'invention concerne un appareil d'un équipement d'utilisateur (UE) comprenant des circuits de traitement. En vue de configurer l'UE pour des communications de nouvelle radio (NR) en utilisant l'agrégation de porteuses composantes (CC), les circuits de traitement servent à décoder des informations de configuration en provenance d'une station de base. Les informations de configuration planifient de multiples transmissions d'informations de commande de liaison montante (UCI) sur de multiples canaux de commande de liaison montante physique (PUCCH) correspondants dans un groupe de PUCCH associé à l'agrégation de CC. Une première UCI associée à une première ressource temporelle dans un premier PUCCH des multiples PUCCH est déterminée. Une deuxième UCI associée à une deuxième ressource temporelle dans un deuxième PUCCH des multiples PUCCH est déterminée. Les première et deuxième ressources temporelles se chevauchent dans au moins un créneau. L'une parmi la première UCI et la deuxième UCI est sélectionnée pour une transmission à la station de base en se basant au moins sur un type d'UCI associé à des informations de commande dans la première UCI et la deuxième UCI.
PCT/US2019/047205 2018-08-20 2019-08-20 Gestion de collision pour transmissions d'informations de commande de liaison montante WO2020041269A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201862720036P 2018-08-20 2018-08-20
US62/720,036 2018-08-20
US201862731612P 2018-09-14 2018-09-14
US62/731,612 2018-09-14

Publications (1)

Publication Number Publication Date
WO2020041269A1 true WO2020041269A1 (fr) 2020-02-27

Family

ID=69591102

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/047205 WO2020041269A1 (fr) 2018-08-20 2019-08-20 Gestion de collision pour transmissions d'informations de commande de liaison montante

Country Status (1)

Country Link
WO (1) WO2020041269A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3726912A4 (fr) * 2018-01-12 2020-12-23 Huawei Technologies Co., Ltd. Procédé de transmission d'informations de commande de liaison montante, dispositif de réseau d'accès, et dispositif terminal
WO2021231176A1 (fr) * 2020-05-15 2021-11-18 Qualcomm Incorporated Détermination de facteurs permettant de diviser des informations d'état de positionnement (psi) entre des informations de commande de liaison montante (uci) et des éléments de commande de contrôle d'accès au support (mac-ce)
CN113677032A (zh) * 2020-05-13 2021-11-19 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN114079553A (zh) * 2020-08-19 2022-02-22 维沃移动通信有限公司 上行传输方法、设备及可读存储介质
US20220086866A1 (en) * 2019-04-05 2022-03-17 Qualcomm Incorporated Timeline considerations for intra-ue multiplexing
WO2022213260A1 (fr) * 2021-04-06 2022-10-13 Apple Inc. Transmission en liaison montante avec répétitions
CN115333699A (zh) * 2021-05-11 2022-11-11 大唐移动通信设备有限公司 信道处理方法、装置及存储介质
WO2024011339A1 (fr) * 2022-07-11 2024-01-18 Qualcomm Incorporated Transmissions simultanées de canal de commande de liaison montante physique
CN113677032B (zh) * 2020-05-13 2024-05-24 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130121302A1 (en) * 2010-07-26 2013-05-16 Lg Electronics Inc. Method and device for transmitting control information

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130121302A1 (en) * 2010-07-26 2013-05-16 Lg Electronics Inc. Method and device for transmitting control information

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Remaining details on NR PUCCH", R1-1808673, 3GPP TSG RAN WG1 MEETING #94, 11 August 2018 (2018-08-11), Gothenburg, Sweden, XP051516048 *
CATT: "Corrections to UCI feedback procedures", R1- 1809713, 3GPP TSG RAN WG1 MEETING #94, 17 August 2018 (2018-08-17), Gothenburg, Sweden, XP051517063 *
HUAWEI ET AL.: "Remaining issues for physical uplink control channel", RL-1808103, 3GPP TSG RAN WG1 MEETING #94, 11 August 2018 (2018-08-11), Gothenburg, Sweden, XP051515505 *
ZTE ET AL.: "Remaining issues on NR PUCCH", R1-1808207, 3GPP TSG RAN WG1 MEETING #94, 11 August 2018 (2018-08-11), Gothenburg, Sweden, XP051515592 *

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10966234B2 (en) 2018-01-12 2021-03-30 Huawei Technologies Co., Ltd. Uplink control information transmission method, access network device, and terminal device
EP3726912A4 (fr) * 2018-01-12 2020-12-23 Huawei Technologies Co., Ltd. Procédé de transmission d'informations de commande de liaison montante, dispositif de réseau d'accès, et dispositif terminal
US11419135B2 (en) 2018-01-12 2022-08-16 Huawei Technologies Co., Ltd. Uplink control information transmission method, access network device, and terminal device
US20220086866A1 (en) * 2019-04-05 2022-03-17 Qualcomm Incorporated Timeline considerations for intra-ue multiplexing
US11844101B2 (en) * 2019-04-05 2023-12-12 Qualcomm Incorporated Timeline considerations for intra-UE multiplexing
CN113677032A (zh) * 2020-05-13 2021-11-19 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN113677032B (zh) * 2020-05-13 2024-05-24 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
WO2021231176A1 (fr) * 2020-05-15 2021-11-18 Qualcomm Incorporated Détermination de facteurs permettant de diviser des informations d'état de positionnement (psi) entre des informations de commande de liaison montante (uci) et des éléments de commande de contrôle d'accès au support (mac-ce)
US11924801B2 (en) 2020-05-15 2024-03-05 Qualcomm Incorporated Determining factors for splitting positioning state information (PSI) between uplink control information (UCI) and medium access control control elements (MAC-CE)
WO2022037508A1 (fr) * 2020-08-19 2022-02-24 维沃移动通信有限公司 Procédé et dispositif de transmission en liaison montante, et support de stockage lisible
CN114079553A (zh) * 2020-08-19 2022-02-22 维沃移动通信有限公司 上行传输方法、设备及可读存储介质
CN114079553B (zh) * 2020-08-19 2023-02-21 维沃移动通信有限公司 上行传输方法、设备及可读存储介质
WO2022213260A1 (fr) * 2021-04-06 2022-10-13 Apple Inc. Transmission en liaison montante avec répétitions
CN115333699A (zh) * 2021-05-11 2022-11-11 大唐移动通信设备有限公司 信道处理方法、装置及存储介质
WO2024011339A1 (fr) * 2022-07-11 2024-01-18 Qualcomm Incorporated Transmissions simultanées de canal de commande de liaison montante physique

Similar Documents

Publication Publication Date Title
US11825560B2 (en) Physical sidelink feedback channel (PSFCH) transmission and reception in new radio (NR) systems
US11570757B2 (en) Sidelink collision avoidance, HARQ feedback, and CSI acquisition
US11563545B2 (en) HARQ-ACK transmission and retransmission in wireless communication systems
US11956782B2 (en) Resource allocation and processing behaviors for NR V2X sidelink communications
CN112970310B (zh) 已发布资源的集成接入和回传移动终端信令
CN113748725B (zh) Iab网络中的资源分配
WO2020041269A1 (fr) Gestion de collision pour transmissions d'informations de commande de liaison montante
US11792891B2 (en) Multiplexing capability signaling for integrated access and backhaul (IAB) nodes
US11457511B2 (en) Enhanced downlink semi-persistent scheduling (SPS)
US20200366419A1 (en) Physical structure for sidelink control channel transmission in two stages
US20210126816A1 (en) Sounding reference signal (srs) transmission with bandwidth part (bwp) switching
US20200374860A1 (en) Physical sidelink control channel (pscch) signaling for multiple transmission time interval (tti) transmissions
EP3871459A1 (fr) Signalisation non stricte de ressources dans des réseaux à accès et raccordement intégrés (iab)
WO2020069174A1 (fr) Indication de capacité d'équipement utilisateur destinée à un transfert intercellulaire à connectivité multiple
WO2020092359A1 (fr) Améliorations de demandes d'ordonnancement pour des réseaux 5g
WO2020068648A1 (fr) Connectivité multiple à l'aide d'un multiplexage par répartition dans le temps
WO2020092348A1 (fr) Conception de ssb hors grille dans des réseaux iab
EP3796731B1 (fr) Priorisation améliorée de subventions pour nouvelle radio (nr)
US11653338B2 (en) Guard symbols (Ng) tables generation for co-located IAB DU/MT resource transition
US11956646B2 (en) Enhancements for uplink beam operations
EP3854143A1 (fr) Transfert intercellulaire conditionnel dans des réseaux sans fil
WO2023049096A1 (fr) Multiplexage d'informations de commande de liaison montante (uci) pour opérations à multiples points de transmission-réception (m-trp)
US11997620B2 (en) Off-raster SSB design in IAB networks
CN117480845A (zh) 用于多发送接收点（m-trp）操作的上行链路控制信息（uci）复用
JP2024520284A (ja) 第５世代（５Ｇ）新無線（ＮＲ）ネットワークにおける動作のために構成されたユーザ機器（ＵＥ）用の装置、第５世代（５Ｇ）新無線（ＮＲ）ネットワークにおける動作のために構成されたユーザ機器（ＵＥ）の処理回路による実行のためのコンピュータプログラム、および、第５世代（５Ｇ）新無線（ＮＲ）ネットワークにおける動作のために構成されたｇノードＢ（ｇＮＢ）用の装置

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: 19851746

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19851746

Country of ref document: EP

Kind code of ref document: A1