[go: up one dir, main page]

WO2021046833A1 - Transmission de canal de commande de liaison montante physique pour des porteuses de liaison montante multiplexées par répartition dans le temps - Google Patents

Transmission de canal de commande de liaison montante physique pour des porteuses de liaison montante multiplexées par répartition dans le temps Download PDF

Info

Publication number
WO2021046833A1
WO2021046833A1 PCT/CN2019/105814 CN2019105814W WO2021046833A1 WO 2021046833 A1 WO2021046833 A1 WO 2021046833A1 CN 2019105814 W CN2019105814 W CN 2019105814W WO 2021046833 A1 WO2021046833 A1 WO 2021046833A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink
slot
pucch
carriers
carrier
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/105814
Other languages
English (en)
Inventor
Chenxi HAO
Bo Chen
Chao Wei
Yu Zhang
Hao Xu
Peter Gaal
Wanshi Chen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2019/105814 priority Critical patent/WO2021046833A1/fr
Publication of WO2021046833A1 publication Critical patent/WO2021046833A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • 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) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or 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/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • 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—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • aspects of the present disclosure relate generally to wireless communication, and more particularly to techniques for physical uplink control channel transmission for time division multiplexed uplink carriers.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (for example, bandwidth, transmit power, etc. ) .
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single-carrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) .
  • LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • UMTS Universal Mobile Telecommunications System
  • a wireless communication network may include a number of base stations (BSs) that can support communication for a number of user equipments (UEs) .
  • a user equipment (UE) may communicate with a base station (BS) via the downlink (DL) and uplink (UL) .
  • the DL (or forward link) refers to the communication link from the BS to the UE
  • the UL (or reverse link) refers to the communication link from the UE to the BS.
  • a BS may be referred to as a NodeB, an LTE evolved nodeB (eNB) , a gNB, an access point (AP) , a radio head, a transmit receive point (TRP) , a New Radio (NR) BS, a 5G NodeB, or the like.
  • eNB LTE evolved nodeB
  • AP access point
  • TRP transmit receive point
  • NR New Radio
  • NR which also may be referred to as 5G
  • 5G is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • the method may include receiving information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers, receiving information configuring a physical uplink control channel (PUCCH) on one or more of the multiple uplink carriers, and determining an uplink slot for a PUCCH transmission based at least in part on the uplink slot pattern and the information configuring the PUCCH.
  • PUCCH physical uplink control channel
  • the PUCCH may be configured on only one uplink carrier of the multiple uplink carriers, and determining the uplink slot for the PUCCH transmission may include identifying a scheduled slot for the PUCCH transmission on the one uplink carrier based at least in part on the information configuring the PUCCH, determining that the scheduled slot for the PUCCH transmission is an invalid slot based at least in part on the uplink slot pattern, and delaying the PUCCH transmission until a next valid uplink slot on the one uplink carrier, with the uplink slot for the PUCCH transmission corresponding to the next valid uplink slot on the one uplink carrier.
  • the PUCCH transmission may be delayed until the next valid uplink slot on the one uplink carrier based at least in part on the scheduled slot for the PUCCH transmission not having a scheduled physical uplink shared channel (PUSCH) transmission on another one of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission.
  • PUSCH physical uplink shared channel
  • the PUCCH may be configured on only a first uplink carrier of the multiple uplink carriers, and determining the uplink slot for the PUCCH transmission may include identifying a scheduled slot for the PUCCH transmission on the first uplink carrier based at least in part on the information configuring the PUCCH, determining that the scheduled slot for the PUCCH transmission on the first uplink carrier is an invalid slot based at least in part on the uplink slot pattern, and determining that the scheduled slot on the first uplink carrier has a PUSCH transmission occasion on a second uplink carrier of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission, with content to be carried in the PUCCH transmission transmitted by the PUSCH on the second uplink carrier.
  • the information configuring the PUCCH may include a timing for the PUCCH transmission that is indicated via one or more of a radio resource control (RRC) message or downlink control information (DCI) .
  • RRC radio resource control
  • DCI downlink control information
  • the timing may be related to an uplink transmission of one or more of a hybrid automatic repeat request (HARQ) associated with a physical downlink shared channel (PDSCH) transmission, a channel state information (CSI) report, or a scheduling request.
  • HARQ hybrid automatic repeat request
  • PDSCH physical downlink shared channel
  • CSI channel state information
  • the multiple uplink carriers include a first uplink carrier associated with a time division duplexing (TDD) configuration and one or more second uplink carriers associated with one or more of a supplemental uplink (SUL) configuration, a frequency division duplexing (FDD) configuration, or another TDD configuration.
  • TDD time division duplexing
  • SUL supplemental uplink
  • FDD frequency division duplexing
  • the UE may include a memory and one or more processors operatively coupled to the memory.
  • the memory and the one or more processors may be configured to receive information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers; receive information configuring a PUCCH on one or more of the multiple uplink carriers; and determine an uplink slot for a PUCCH transmission based at least in part on the uplink slot pattern and the information configuring the PUCCH.
  • the apparatus may include means for means for receiving information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers; means for receiving information configuring a PUCCH on one or more of the multiple uplink carriers; and means for determining an uplink slot for a PUCCH transmission based at least in part on the uplink slot pattern and the information configuring the PUCCH.
  • the method may include transmitting, to a UE, information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers; transmitting, to the UE, information configuring a PUCCH on one or more of the multiple uplink carriers; and identifying an uplink slot to receive a PUCCH transmission from the UE based at least in part on the uplink slot pattern and the information configuring the PUCCH.
  • the PUCCH may be configured on only one uplink carrier of the multiple uplink carriers, and identifying the uplink slot to receive the PUCCH transmission may include identifying a scheduled slot for the PUCCH transmission on the one uplink carrier based at least in part on the information configuring the PUCCH, determining that the scheduled slot for the PUCCH transmission is an invalid slot based at least in part on the uplink slot pattern, and identifying a next valid uplink slot on the one uplink carrier as the uplink slot in which to receive the PUCCH transmission from the UE.
  • the PUCCH transmission may be received in the next valid uplink slot on the one uplink carrier based at least in part on the scheduled slot for the PUCCH transmission not having a scheduled PUSCH transmission on another one of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission.
  • the PUCCH may be configured on only a first uplink carrier of the multiple uplink carriers, and identifying the uplink slot to receive the PUCCH transmission may include identifying a scheduled slot for the PUCCH transmission on the first uplink carrier based at least in part on the information configuring the PUCCH, determining that the scheduled slot for the PUCCH transmission on the first uplink carrier is an invalid slot based at least in part on the uplink slot pattern, and determining that the scheduled slot on the first uplink carrier has a PUSCH transmission occasion on a second uplink carrier of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission, with content to be carried in the PUCCH transmission transmitted by the PUSCH on the second uplink carrier.
  • the PUCCH may be configured on at least a first uplink carrier and a second uplink carrier among the multiple uplink carriers, and identifying the uplink slot to receive the PUCCH transmission may include identifying a scheduled slot for the PUCCH transmission based at least in part on the information configuring the PUCCH and identifying, among the first uplink carrier and the second uplink carrier, an uplink carrier that has a valid uplink slot in the scheduled slot for the PUCCH transmission based at least in part on the uplink slot pattern, with the uplink slot for the PUCCH transmission corresponding to the valid uplink slot on the determined uplink carrier.
  • the information configuring the PUCCH may include a timing for the PUCCH transmission that is indicated via one or more of an RRC message or DCI.
  • the timing may be related to an uplink transmission of one or more of a HARQ associated with a PDSCH transmission, a CSI report, or a scheduling request.
  • the multiple uplink carriers may include a first uplink carrier associated with a TDD configuration and one or more second uplink carriers associated with one or more of an SUL configuration, an FDD configuration, or another TDD configuration.
  • the base station may include a memory and one or more processors operatively coupled to the memory.
  • the memory and the one or more processors may be configured to transmit, to a UE, information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers; transmit, to the UE, information configuring a PUCCH on one or more of the multiple uplink carriers; and identify an uplink slot to receive a PUCCH transmission from the UE based at least in part on the uplink slot pattern and the information configuring the PUCCH.
  • the apparatus may include means for means for transmitting, to a UE, information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers; means for transmitting, to the UE, information configuring a PUCCH on one or more of the multiple uplink carriers; and means for identifying an uplink slot to receive a PUCCH transmission from the UE based at least in part on the uplink slot pattern and the information configuring the PUCCH.
  • Figure 1 is a block diagram conceptually illustrating an example of a wireless network.
  • Figure 2 is a block diagram conceptually illustrating an example of a base station in communication with a UE in a wireless network.
  • Figure 3A is a block diagram conceptually illustrating an example of a frame structure in a wireless network.
  • Figure 4 is a block diagram conceptually illustrating an example slot format with a normal cyclic prefix.
  • Figure 5 is a diagram conceptually illustrating an example of a downlink (DL) -centric slot.
  • Figure 6 is a diagram conceptually illustrating an example of an uplink (UL) -centric slot.
  • FIGS 7A–7D are diagrams illustrating examples of physical uplink control channel transmission (PUCCH) for time division multiplexed uplink carriers.
  • PUCCH physical uplink control channel transmission
  • Figure 8 is a diagram illustrating an example process performed, for example, by a user equipment.
  • Figure 9 is a diagram illustrating an example process performed, for example, by a base station.
  • the described implementations may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards, including any of the IEEE 802.11 standards, the standard, code division multiple access (CDMA) , frequency division multiple access (FDMA) , time division multiple access (TDMA) , Global System for Mobile communications (GSM) , GSM/General Packet Radio Service (GPRS) , Enhanced Data GSM Environment (EDGE) , Terrestrial Trunked Radio (TETRA) , Wideband-CDMA (W-CDMA) , Evolution Data Optimized (EV-DO) , 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High Speed Packet Access (HSPA) , High Speed Downlink Packet Access (HSDPA) , High Speed Uplink Packet Access (HSUPA) , Evolved High Speed Packet Access (HSPA+) , Long Term Evolution (LTE) , AMPS, or other known signals that are used
  • Time division multiplexing (TDM) techniques may be used in connection with an uplink carrier aggregation mode to enable a UE to perform uplink transmission across multiple component carriers.
  • the multiple component carriers may include a primary uplink carrier and one or more secondary uplink carriers, and a TDM pattern may be defined such that the UE can transmit on only one uplink carrier at a time (such as in a particular symbol or slot) .
  • TDM techniques may be used in connection with the uplink carrier aggregation mode because certain bands operating at high frequencies may have a shorter coverage range compared to other bands operating at relatively lower frequencies (such as the 3.5 gigahertz (GHz) frequency band operating in time division duplexing (TDD) mode exhibiting about 9 decibels (dB) coverage loss, compared to the 2.1 GHz band, which includes an uplink frequency band that is paired with a downlink frequency band operating in frequency division duplexing (FDD) mode) .
  • GHz gigahertz
  • TDD time division duplexing
  • FDD frequency division duplexing
  • carrier aggregation techniques that support concurrent or simultaneous transmission via multiple component carriers are associated with bottlenecks due to increased UE implementation complexity because the UE has to operate on multiple frequencies simultaneously.
  • the UE can only use one transmit antenna in each frequency band, creating further bottlenecks.
  • a UE located near the center or median of the cell may be scheduled on the high band to exploit the larger available bandwidth on the high band, and in other uplink slots, the UE located near the center or median of the cell may be scheduled on the low band to enable fast hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback as there may be more uplink resources available in the low band.
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • TDM for uplink carriers may be implemented in a supplemental uplink (SUL) mode or in a TDM carrier aggregation mode.
  • SUL supplemental uplink
  • a UE may be configured with two uplink carriers (such as a TDD carrier and an SUL carrier) and one downlink carrier (such as the TDD carrier) , and the UE may be permitted to operate on only one uplink carrier at a time (such as in a particular symbol or slot) .
  • the UE can be scheduled for uplink transmission on either uplink carrier in an arbitrary symbol or slot.
  • the SUL mode can support one transmit antenna on each uplink carrier with substantially no switching time between uplink carriers, or the SUL mode can support two transmit antennas on the primary uplink carrier (such as the TDD carrier) and one transmit antenna on the SUL carrier, with a small switching time between carriers (such as 35, 70, or 140 microseconds) .
  • the SUL mode can only be configured in a co-sited case, where both uplink carriers are from the base station because there is only one downlink carrier.
  • the UE may be configured with two uplink carriers (such as a TDD carrier and an FDD uplink carrier) and two downlink carriers (such as the TDD carrier and an FDD downlink carrier paired with the FDD uplink carrier) , and the UE may be permitted to operate on only one uplink carrier at a time, according to a semi-static or dynamic TDM pattern.
  • each uplink carrier may be associated with a different reference downlink carrier (such as for indicating a timing advance (TA) or power control to be used on the corresponding uplink carrier) .
  • TA timing advance
  • the TDM carrier aggregation mode offers better performance (such as more flexible power control or increased reliability, compared to SUL, because there are two downlink carriers) and more flexible deployment because TDM carrier aggregation can be implemented in co-sited or distributed base station architectures.
  • a physical uplink control channel may be configured to carry uplink control information from a UE to a base station, such as HARQ-ACK feedback for a physical downlink shared channel (PDSCH) transmission, a periodic or semi-periodic channel state information (CSI) report, or a scheduling request.
  • PDSCH physical downlink shared channel
  • CSI channel state information
  • PUCCH resources may be configured on only one carrier (such as either a primary cell (PCell) or a secondary cell (SCell) ) , meaning that a PUCCH can only be transmitted on one carrier even in cases where a UE is configured with multiple uplink carriers.
  • a PUCCH transmission occasion which refers to an uplink slot in which to transmit a PUCCH resource, can be determined based on a HARQ timing associated with the PDSCH transmission, or a radio resource control (RRC) configuration associated with a periodic or semi-periodic CSI report, or a scheduling request, among other possible examples.
  • RRC radio resource control
  • downlink control information (DCI) scheduling the PDSCH transmission may indicate the HARQ timing for indicating an ACK or a NACK for the PDSCH transmission (such as an uplink slot in which the UE is to transmit the ACK or NACK) .
  • the UE may identify the corresponding PUCCH resource in the uplink slot indicated by the HARQ timing in order to transmit the ACK or NACK.
  • RRC signaling can be used to configure an uplink slot and a periodicity for a UE to transmit a CSI report to a base station.
  • the uplink slot in which the UE is to transmit the PUCCH may be an invalid uplink slot.
  • different semi-static uplink slot configurations may be defined to improve UE performance in different locations or regions within a cell.
  • a first TDM pattern defined for cell center UEs may assign one or more uplink slots to an uplink carrier operating at a higher frequency, to enable the UE to perform high rate transmissions, and the uplink carrier operating at the lower frequency may remain available to enable the cell center UEs to perform a fast HARQ transmission to provide an ACK or NACK for a PDSCH transmission received on the higher frequency band.
  • a second TDM pattern defined for cell edge UEs may assign one or more uplink slots to the uplink carrier operating at the lower frequency to address coverage issues.
  • the uplink slot in which the UE is to transmit the PUCCH (such as on the lower frequency band) may coincide with an uplink slot that is scheduled on another carrier (such as the higher frequency band in the cell center TDM pattern) , which may cause the PUCCH transmission occasion to be missed because TDM techniques only permit a UE to operate on only one uplink carrier at a time.
  • some aspects described herein provide techniques and apparatuses for rescheduling a PUCCH transmission occasion that may be missed, such as when an uplink slot for the PUCCH transmission on one uplink carrier coincides with an uplink slot scheduled on another uplink carrier.
  • the techniques and apparatuses described herein improve reliability of PUCCH transmissions by rescheduling a missed PUCCH transmission occasion in a next valid uplink slot, thus reducing a delay in transmitting uplink control information such as HARQ-ACK feedback for downlink data, a periodic or semi-periodic channel state information (CSI) report, or a scheduling request.
  • uplink control information such as HARQ-ACK feedback for downlink data, a periodic or semi-periodic channel state information (CSI) report, or a scheduling request.
  • CSI channel state information
  • a PUCCH transmission occasion that is scheduled during an invalid uplink slot on one uplink carrier can be included in (sometimes referred to as “piggybacked onto” ) a physical uplink shared channel (PUSCH) transmission on another uplink carrier that has a valid uplink slot during the slot in which the PUCCH transmission occasion is scheduled, thus further reducing the delay in transmitting the uplink control information.
  • the techniques and apparatuses described herein provide the further advantage of enabling a PUCCH to be configured on multiple uplink carriers, which allows the UE to dynamically select the uplink carrier for the PUCCH transmission (such as based on which uplink carrier has a valid uplink slot in the slot in which the PUCCH is to be transmitted) .
  • FIG. 1 is a block diagram conceptually illustrating an example of a wireless network 100.
  • the wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network.
  • Wireless network 100 may include a number of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities.
  • a BS is an entity that communicates with user equipment (UEs) and also may be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB) , an access point, a transmit receive point (TRP) , or the like.
  • Each BS may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a BS, a BS subsystem serving this coverage area, or a combination thereof, depending on the context in which the term is used.
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof.
  • a macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs having association with the femto cell (for example, UEs in a closed subscriber group (CSG) ) .
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • a BS 110a may be a macro BS for a macro cell 102a
  • a BS 110b may be a pico BS for a pico cell 102b
  • a BS 110c may be a femto BS for a femto cell 102c.
  • a BS may support one or multiple (for example, three) cells.
  • Wireless network 100 also may include relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (for example, a BS or a UE) and send a transmission of the data to a downstream station (for example, a UE or a BS) .
  • a relay station also may be a UE that can relay transmissions for other UEs.
  • a relay station 110d may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d.
  • a relay station also may be referred to as a relay BS, a relay base station, a relay, etc.
  • Wireless network 100 may be a heterogeneous network that includes BSs of different types, for example, macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100.
  • macro BSs may have a high transmit power level (for example, 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (for example, 0.1 to 2 Watts) .
  • a network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs.
  • Network controller 130 may communicate with the BSs via a backhaul.
  • the BSs also may communicate with one another, for example, directly or indirectly via a wireless or wireline backhaul.
  • UEs 120 may be dispersed throughout wireless network 100, and each UE may be stationary or mobile.
  • a UE also may be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc.
  • a UE may be a cellular phone (for example, a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (for example, smart ring, smart bracelet) ) , an entertainment device (for example, a music or video device, or a satellite radio) , a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
  • PDA personal digital assistant
  • WLL wireless local loop
  • Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a base station, another device (for example, remote device) , or some other entity.
  • a wireless node may provide, for example, connectivity for or to a network (for example, a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
  • Some UEs may be considered Internet-of-Things (IoT) devices or may be implemented as NB-IoT (narrowband internet of things) devices.
  • Some UEs may be considered a Customer Premises Equipment (CPE) .
  • UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, similar components, or a combination thereof.
  • access to the air interface may be scheduled, where a scheduling entity (for example, a base station) allocates resources for communication among some or all devices and equipment within the scheduling entity’s service area or cell.
  • a scheduling entity for example, a base station
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity.
  • Base stations are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (for example, one or more other UEs) . In this example, the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication.
  • a UE may function as a scheduling entity in a peer-to-peer (P2P) network, in a mesh network, or another type of network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
  • P2P peer-to-peer
  • mesh network UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (for example, without using a base station 110 as an intermediary to communicate with one another) .
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or similar protocol) , a mesh network, or similar networks, or combinations thereof.
  • V2X vehicle-to-everything
  • the UE 120 may perform scheduling operations, resource selection operations, as well as other operations described elsewhere herein as being performed by the base station 110.
  • FIG 2 is a block diagram conceptually illustrating an example 200 of a base station 110 in communication with a UE 120.
  • base station 110 and UE 120 may respectively be one of the base stations and one of the UEs in wireless network 100 of Figure 1.
  • Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T ⁇ 1 and R ⁇ 1.
  • a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (for example, encode and modulate) the data for each UE based at least in part on the MCS (s) selected for the UE, and provide data symbols for all UEs.
  • MCS modulation and coding schemes
  • CQIs channel quality indicators
  • the transmit processor 220 also may process system information (for example, for semi-static resource partitioning information (SRPI) , etc. ) and control information (for example, CQI requests, grants, upper layer signaling, etc. ) and provide overhead symbols and control symbols.
  • system information for example, for semi-static resource partitioning information (SRPI) , etc.
  • control information for example, CQI requests, grants, upper layer signaling, etc.
  • the transmit processor 220 also may generate reference symbols for reference signals (for example, the cell-specific reference signal (CRS) ) and synchronization signals (for example, the primary synchronization signal (PSS) and secondary synchronization signal (SSS) ) .
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (for example, for OFDM, etc. ) to obtain an output sample stream.
  • Each modulator 232 may further process (for example, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
  • the synchronization signals can be generated with location encoding to convey additional information.
  • antennas 252a through 252r may receive the downlink signals from base station 110 or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.
  • Each demodulator 254 may condition (for example, filter, amplify, downconvert, and digitize) a received signal to obtain input samples.
  • Each demodulator 254 may further process the input samples (for example, for OFDM, etc. ) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (for example, demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller or processor (controller/processor) 280.
  • a channel processor may determine reference signal received power (RSRP) , received signal strength indicator (RSSI) , reference signal received quality (RSRQ) , channel quality indicator (CQI) , etc.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSRQ reference signal received quality
  • CQI channel quality indicator
  • one or more components of UE 120 may be included in a housing.
  • the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120.
  • Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller or processor (i.e., controller/processor) 240.
  • the base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244.
  • the network controller 130 may include communication unit 294, a controller or processor (i.e., controller/processor) 290, and memory 292.
  • the controller/processor 240 of base station 110, the controller/processor 280 of UE 120, or any other component (s) of Figure 2 may perform one or more techniques associated with physical uplink control channel (PUCCH) transmission for time division multiplexed uplink carriers, as described in more detail elsewhere herein.
  • the controller/processor 240 of base station 110, the controller/processor 280 of UE 120, or any other component (s) (or combinations of components) of Figure 2 may perform or direct operations of, for example, the process 800 of Figure 8, the process 900 of Figure 9, or other processes as described herein.
  • the memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively.
  • a scheduler 246 may schedule UEs for data transmission on the downlink, the uplink, or a combination thereof.
  • the stored program codes when executed by the controller/processor 280 or other processors and modules at UE 120, may cause the UE 120 to perform operations described with respect to the process 800 of Figure 8 or other processes as described herein.
  • the stored program codes when executed by the controller/processor 240 or other processors and modules at base station 110, may cause the base station 110 to perform operations described with respect to the process 900 of Figure 9 or other processes as described herein.
  • a scheduler 246 may schedule UEs for data transmission on the downlink, the uplink, or a combination thereof.
  • UE 120 may include means for receiving information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers, means for receiving information configuring a PUCCH on one or more of the multiple uplink carriers, means for determining an uplink slot for a PUCCH transmission based at least in part on the uplink slot pattern and the information configuring the PUCCH, or the like, or combinations thereof.
  • such means may include one or more components of UE 120 described in connection with Figure 2.
  • base station 110 may include means for transmitting, to the UE 120, information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers, means for transmitting, to the UE 120, information configuring a PUCCH on one or more of the multiple uplink carriers, means for identifying an uplink slot to receive a PUCCH transmission from the UE based at least in part on the uplink slot pattern and the information configuring the PUCCH, or the like, or combinations thereof.
  • such means may include one or more components of base station 110 described in connection with Figure 2.
  • While blocks in Figure 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components.
  • the functions described with respect to the transmit processor 264, the receive processor 258, the TX MIMO processor 266, or another processor may be performed by or under the control of controller/processor 280.
  • FIG. 3A is a block diagram conceptually illustrating an example frame structure 300 in a wireless network.
  • frame structure 300 may be for FDD in the wireless network, which may include a 5G NR wireless network or another type of wireless network.
  • the transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames (sometimes referred to as frames) .
  • Each radio frame may have a predetermined duration (for example, 10 milliseconds (ms) ) and may be partitioned into a set of Z (Z ⁇ 1) subframes (for example, with indices of 0 through Z-1) .
  • Each subframe may have a predetermined duration (for example, 1 ms) and may include a set of slots (for example, 2 m slots per subframe are shown in Figure 3A, where m is a numerology used for a transmission, such as 0, 1, 2, 3, 4, or the like) .
  • Each slot may include a set of L symbol periods.
  • each slot may include fourteen symbol periods (for example, as shown in Figure 3A) , seven symbol periods, or another number of symbol periods.
  • the subframe may include 2L symbol periods, where the 2L symbol periods in each subframe may be assigned indices of 0 through 2L–1.
  • a scheduling unit for the FDD may frame-based, subframe-based, slot-based, symbol-based, or the like.
  • a wireless communication structure may refer to a periodic time-bounded communication unit defined by a wireless communication standard or protocol. Additionally, or alternatively, different configurations of wireless communication structures than those shown in Figure 3A may be used.
  • the base station may transmit the PSS, the SSS, the PBCH, or a combination thereof in accordance with a synchronization communication hierarchy (for example, a synchronization signal (SS) hierarchy) including multiple synchronization communications (for example, SS blocks) , as described below in connection with Figure 3B.
  • a synchronization communication hierarchy for example, a synchronization signal (SS) hierarchy
  • multiple synchronization communications for example, SS blocks
  • Figure 3B is a block diagram conceptually illustrating an example SS hierarchy in a wireless network.
  • the example SS hierarchy may be an example of a synchronization communication hierarchy.
  • the SS hierarchy may include an SS burst set, which may include a plurality of SS bursts (identified as SS burst 0 through SS burst B-1, where B is a maximum number of repetitions of the SS burst that may be transmitted by the base station) .
  • the SS burst set shown in Figure 3B is an example of a synchronization communication set, and other synchronization communication sets may be used in connection with the techniques described herein.
  • the SS block shown in Figure 3B is an example of a synchronization communication, and other synchronization communications may be used in connection with the techniques described herein.
  • an SS block includes resources that carry the PSS, the SSS, the PBCH, or other synchronization signals (for example, a tertiary synchronization signal (TSS) ) or synchronization channels.
  • TSS tertiary synchronization signal
  • multiple SS blocks are included in an SS burst, and the PSS, the SSS, or the PBCH may be the same across each SS block of the SS burst.
  • a single SS block may be included in an SS burst.
  • the SS block may be at least four symbol periods in length, where each symbol carries one or more of the PSS (for example, occupying one symbol) , the SSS (for example, occupying one symbol) , or the PBCH (for example, occupying two symbols) .
  • the symbols of an SS block are consecutive, as shown in Figure 3B. In some aspects, the symbols of an SS block are non-consecutive. Similarly, in some aspects, one or more SS blocks of the SS burst may be transmitted in consecutive radio resources (for example, consecutive symbol periods) during one or more slots. Additionally, or alternatively, one or more SS blocks of the SS burst may be transmitted in non-consecutive radio resources.
  • the SS bursts may have a burst period, whereby the SS blocks of the SS burst are transmitted by the base station according to the burst period. In other words, the SS blocks may be repeated during each SS burst.
  • the SS burst set may have a burst set periodicity, whereby the SS bursts of the SS burst set are transmitted by the base station according to the fixed burst set periodicity. In other words, the SS bursts may be repeated during each SS burst set.
  • the base station may transmit system information, such as system information blocks (SIBs) on a physical downlink shared channel (PDSCH) in certain slots.
  • SIBs system information blocks
  • the base station may transmit control information/data on a physical downlink control channel (PDCCH) in C symbol periods of a slot, where B may be configurable for each slot.
  • the base station may transmit traffic data or other data on the PDSCH in the remaining symbol periods of each slot.
  • Figure 4 is a block diagram conceptually illustrating an example slot format 410 with a normal cyclic prefix.
  • the available time frequency resources may be partitioned into resource blocks.
  • Each resource block may cover a set of subcarriers (for example, 12 subcarriers) in one slot and may include a number of resource elements.
  • Each resource element may cover one subcarrier in one symbol period (for example, in time) and may be used to send one modulation symbol, which may be a real or complex value.
  • An interlace structure may be used for each of the downlink and uplink for FDD in certain telecommunications systems (for example, NR) .
  • Q interlaces with indices of 0 through Q –1 may be defined, where Q may be equal to 4, 6, 8, 10, or some other value.
  • Each interlace may include slots that are spaced apart by Q frames.
  • interlace q may include slots q, q + Q, q + 2Q, etc., where q ⁇ ⁇ 0, ..., Q –1 ⁇ .
  • a UE may be located within the coverage of multiple BSs. One of these BSs may be selected to serve the UE. The serving BS may be selected based at least in part on various criteria such as received signal strength, received signal quality, path loss, or the like, or combinations thereof. Received signal quality may be quantified by a signal-to-noise-and-interference ratio (SNIR) , or a reference signal received quality (RSRQ) , or some other metric.
  • SNIR signal-to-noise-and-interference ratio
  • RSRQ reference signal received quality
  • the UE may operate in a dominant interference scenario in which the UE may observe high interference from one or more interfering BSs.
  • New Radio may refer to radios configured to operate according to a new air interface (for example, other than Orthogonal Frequency Divisional Multiple Access (OFDMA) -based air interfaces) or fixed transport layer (for example, other than Internet Protocol (IP) ) .
  • NR may utilize OFDM with a CP (herein referred to as cyclic prefix OFDM or CP-OFDM) or SC-FDM on the uplink, may utilize CP-OFDM on the downlink and include support for half-duplex operation using TDD.
  • OFDM Orthogonal Frequency Divisional Multiple Access
  • IP Internet Protocol
  • NR may, for example, utilize OFDM with a CP (herein referred to as CP-OFDM) or discrete Fourier transform spread orthogonal frequency-division multiplexing (DFT-s-OFDM) on the uplink, may utilize CP-OFDM on the downlink and include support for half-duplex operation using TDD.
  • NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (for example, 80 megahertz (MHz) and beyond) , millimeter wave (mmW) targeting high carrier frequency (for example, 60 gigahertz (GHz) ) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, or mission critical targeting ultra reliable low latency communications (URLLC) service.
  • eMBB Enhanced Mobile Broadband
  • mmW millimeter wave
  • mMTC massive MTC
  • URLLC ultra reliable low latency communications
  • NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 60 or 120 kilohertz (kHz) over a 0.1 millisecond (ms) duration.
  • Each radio frame may include 40 slots and may have a length of 10 ms. Consequently, each slot may have a length of 0.25 ms.
  • Each slot may indicate a link direction (for example, DL or UL) for data transmission and the link direction for each slot may be dynamically switched.
  • Each slot may include DL/UL data as well as DL/UL control data.
  • NR may support a different air interface, other than an OFDM-based interface.
  • NR networks may include entities such as central units or distributed units.
  • FIG. 5 is a diagram conceptually illustrating an example 500 of a DL-centric slot or wireless communication structure.
  • the DL-centric slot may include a control portion 502.
  • the control portion 502 may exist in the initial or beginning portion of the DL-centric slot.
  • the control portion 502 may include various scheduling information or control information corresponding to various portions of the DL-centric slot.
  • the control portion 502 may be a physical DL control channel (PDCCH) , as indicated in Figure 5.
  • PDCH physical DL control channel
  • control portion 502 may include legacy PDCCH information, shortened PDCCH (sPDCCH) information) , a control format indicator (CFI) value (for example, carried on a physical control format indicator channel (PCFICH) ) , one or more grants (for example, downlink grants, uplink grants, etc. ) , or the like.
  • legacy PDCCH information shortened PDCCH (sPDCCH) information
  • CFI control format indicator
  • PCFICH physical control format indicator channel
  • grants for example, downlink grants, uplink grants, etc.
  • the DL-centric slot also may include a DL data portion 504.
  • the DL data portion 504 may sometimes be referred to as the payload of the DL-centric slot.
  • the DL data portion 504 may include the communication resources utilized to communicate DL data from the scheduling entity (for example, UE or BS) to the subordinate entity (for example, UE) .
  • the DL data portion 504 may be a physical DL shared channel (PDSCH) .
  • PDSCH physical DL shared channel
  • the DL-centric slot also may include an UL short burst portion 506.
  • the UL short burst portion 506 may sometimes be referred to as an UL burst, an UL burst portion, a common UL burst, a short burst, an UL short burst, a common UL short burst, a common UL short burst portion, or various other suitable terms.
  • the UL short burst portion 506 may include one or more reference signals.
  • the UL short burst portion 506 may include feedback information corresponding to various other portions of the DL-centric slot.
  • the UL short burst portion 506 may include feedback information corresponding to the control portion 502 or the data portion 504.
  • Non-limiting examples of information that may be included in the UL short burst portion 506 include an ACK signal (for example, a PUCCH ACK, a PUSCH ACK, an immediate ACK) , a NACK signal (for example, a PUCCH NACK, a PUSCH NACK, an immediate NACK) , a scheduling request (SR) , a buffer status report (BSR) , a HARQ indicator, a channel state indication (CSI) , a channel quality indicator (CQI) , a sounding reference signal (SRS) , a demodulation reference signal (DMRS) , PUSCH data, or various other suitable types of information.
  • the UL short burst portion 506 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests, and various other suitable types of information.
  • the end of the DL data portion 504 may be separated in time from the beginning of the UL short burst portion 506.
  • This time separation may sometimes be referred to as a gap, a guard period, a guard interval, or various other suitable terms.
  • This separation provides time for the switch-over from DL communication (for example, reception operation by the subordinate entity (for example, UE) ) to UL communication (for example, transmission by the subordinate entity (for example, UE) ) .
  • DL communication for example, reception operation by the subordinate entity (for example, UE)
  • UL communication for example, transmission by the subordinate entity (for example, UE)
  • FIG. 6 is a diagram conceptually illustrating an example 600 of a UL-centric slot or wireless communication structure.
  • the UL-centric slot may include a control portion 602.
  • the control portion 602 may exist in the initial or beginning portion of the UL-centric slot.
  • the control portion 602 in Figure 6 may be similar to the control portion 502 described above with reference to Figure 5.
  • the UL-centric slot also may include an UL long burst portion 604.
  • the UL long burst portion 604 may sometimes be referred to as the payload of the UL-centric slot.
  • the UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (for example, UE) to the scheduling entity (for example, UE or BS) .
  • the control portion 602 may be a physical DL control channel (PDCCH) .
  • PDCCH physical DL control channel
  • the end of the control portion 602 may be separated in time from the beginning of the UL long burst portion 604.
  • This time separation may sometimes be referred to as a gap, guard period, guard interval, or various other suitable terms.
  • This separation provides time for the switch-over from DL communication (for example, reception operation by the scheduling entity) to UL communication (for example, transmission by the scheduling entity) .
  • the UL-centric slot also may include an UL short burst portion 606.
  • the UL short burst portion 606 in Figure 6 may be similar to the UL short burst portion 506 described above with reference to Figure 5, and may include any of the information described above in connection with Figure 5.
  • the foregoing is merely one example of an UL-centric wireless communication structure, and alternative structures having similar features may be used without necessarily deviating from the aspects described herein.
  • two or more subordinate entities may communicate with each other using sidelink signals.
  • Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, or various other suitable applications.
  • a sidelink signal may refer to a signal communicated from one subordinate entity (for example, UE1) to another subordinate entity (for example, UE2) without relaying that communication through the scheduling entity (for example, UE or BS) , even though the scheduling entity may be utilized for scheduling or control purposes.
  • the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum) .
  • a wireless communication structure such as a frame, may include both UL-centric slots and DL-centric slots.
  • the ratio of UL-centric slots to DL-centric slots in a frame may be dynamically adjusted based at least in part on the amount of UL data and the amount of DL data that are transmitted. For example, if there is more UL data, then the ratio of UL-centric slots to DL-centric slots may be increased. Conversely, if there is more DL data, then the ratio of UL-centric slots to DL-centric slots may be decreased.
  • Figures 7A–7D are diagrams illustrating examples 700 of semi-static slot configuration for time division multiplexed uplink carriers.
  • a UE such as a UE 120
  • a base station such as a base station 110
  • the base station may be associated with a cell in which multiple uplink carriers are configured and time division multiplexed with one another, whereby the UE can perform transmission via one uplink carrier at a time (such as within a particular symbol or slot) .
  • the multiple uplink carriers may be configured in a supplemental uplink (SUL) mode or a time division multiplexing carrier aggregation mode.
  • SUL Supplemental uplink
  • the multiple uplink carriers may include a first uplink carrier operating in a time division duplexing (TDD) mode (such as in the 3.5 GHz frequency band) and a second uplink carrier operating in frequency division duplexing (FDD) mode (such as in the 2.1 GHz frequency band) or an SUL mode.
  • TDD time division duplexing
  • FDD frequency division duplexing
  • SUL SUL mode
  • the multiple uplink carriers may be associated with different base stations, different TRPs associated with a single base station, or the like.
  • the base station may transmit, and the UE may receive, information to configure the multiple uplink carriers that are time division multiplexed with one another and information configuring a PUCCH on one or more of the multiple uplink carriers.
  • the information configuring the multiple uplink carriers may include an uplink slot pattern to be applied across the multiple uplink carriers.
  • the uplink slot pattern may indicate one or more symbols or slots in a first uplink carrier (such as a TDD carrier) that are to be used for downlink communication, for uplink communication, or for switching from downlink to uplink communication.
  • a TDM configuration permits the UE to transmit on only one uplink carrier at a time (such as in a particular symbol or slot)
  • one or more slots on a second uplink carrier may be invalid slots, due to coinciding with one or more symbols or slots in the first uplink carrier that are to be used for uplink communication.
  • the first uplink carrier may correspond to a TDD carrier that has a wide bandwidth and serves as an uplink and a downlink carrier
  • the second uplink carrier may correspond to a narrow bandwidth SUL carrier or an FDD uplink carrier that is paired with an FDD downlink carrier (the FDD downlink carrier is not illustrated for brevity)
  • the configuration of the multiple uplink carriers may vary in other cases, and the particular configuration illustrated in Figures 7A–7D are for illustration purposes only.
  • the multiple uplink carriers may include a first TDD carrier on a high-frequency band and a second TDD carrier on a low-frequency band.
  • the primary uplink carrier may correspond to the high-frequency band or the low-frequency band.
  • the second uplink carrier is an SUL carrier
  • the information configuring the PUCCH may indicate one or more of the multiple uplink carriers that are to be used for PUCCH transmissions.
  • the PUCCH may be configured on only a primary uplink carrier (such as an SUL carrier, an FDD UL carrier, or another low-frequency carrier) to enable fast HARQ-ACK feedback for a PDSCH transmission received on a secondary carrier (such as a high-frequency TDD carrier) , uplink transmission of a periodic or semi-periodic CSI report, or uplink transmission of a scheduling request.
  • a primary uplink carrier such as an SUL carrier, an FDD UL carrier, or another low-frequency carrier
  • a secondary carrier such as a high-frequency TDD carrier
  • the PUCCH may be configured on the primary uplink carrier and a secondary uplink carrier (such as the high-frequency TDD carrier) to provide the UE with more flexibility in determining an uplink slot and/or uplink carrier to use for a PUCCH transmission.
  • a secondary uplink carrier such as the high-frequency TDD carrier
  • the high-frequency carrier may be configured as the primary uplink carrier and the low-frequency carrier may be configured as the secondary uplink carrier.
  • the low-frequency SUL or FDD UL carrier may refer to the primary uplink carrier and to the high-frequency TDD carrier as the secondary uplink carrier
  • the high-frequency TDD carrier may be configured as the primary uplink carrier
  • the low-frequency SUL or FDD UL carrier may be configured as the secondary uplink carrier.
  • the UE may determine an uplink slot for a PUCCH transmission based on the uplink slot pattern indicated by the base station and the information received from the base station to configure the PUCCH. Furthermore, as shown by reference number 714, the base station also may identify an uplink slot in which to receive the PUCCH transmission from the UE based on the uplink slot pattern and the PUCCH configuration. For example, in some aspects, radio resource control (RRC) signaling can be used to configure the uplink slot and a periodicity for a UE to transmit, to the base station, a PUCCH carrying a CSI report.
  • RRC radio resource control
  • downlink control information (DCI) scheduling a PDSCH transmission may indicate a HARQ timing for indicating an ACK or a NACK for the PDSCH transmission (such as an uplink slot in which the UE is to transmit the ACK or NACK) .
  • the UE and the base station may identify the PUCCH resource in the appropriate uplink slot, which may enable the UE to transmit the PUCCH in the appropriate uplink slot and enable the base station to receive the PUCCH in the appropriate uplink slot.
  • the UE may receive a PDSCH transmission on the secondary (TDD) carrier in a first slot, and DCI scheduling the PDSCH transmission may indicate a HARQ timing for a PUCCH carrying an ACK or a NACK for the PDSCH transmission.
  • the HARQ timing may indicate that the PUCCH is to be transmitted in a next uplink slot on the primary (SUL or FDD UL) uplink carrier, following the slot in which the PDSCH transmission is received.
  • the UE can transmit the PUCCH in the next (valid) slot following the HARQ timing.
  • the UE may transmit, and the base station may receive, the PUCCH carrying the HARQ-ACK for the PDSCH transmission in the next uplink slot on the primary uplink carrier subsequent to the PDSCH transmission.
  • the UE may receive a PDSCH transmission associated with a HARQ timing that causes the PUCCH transmission to be scheduled during an invalid uplink slot.
  • the HARQ timing may similarly indicate that the PUCCH is to be transmitted in a next uplink slot on the primary uplink carrier, following the slot in which the PDSCH transmission is received.
  • the uplink slot corresponding to the HARQ timing is assigned to the secondary uplink carrier, which does not have a PUCCH configuration.
  • the TDM pattern (or slot pattern) permits the UE to transmit on only one uplink carrier in a particular symbol or slot, the UE cannot transmit, and the base station cannot receive, the PUCCH carrying the HARQ-ACK for the PDSCH transmission in the next (scheduled) uplink slot subsequent to the PDSCH transmission.
  • the UE and the base station may employ various techniques to determine the uplink slot in which the PUCCH is to be transmitted.
  • FIGS 7A-7D show the case where a PUCCH transmission is scheduled for a HARQ-ACK that includes information to indicate an ACK or a NACK for a PDSCH transmission (illustrated as “A/N” in Figures 7A-7D)
  • Similar issues may arise for a periodic or semi-periodic CSI report, a scheduling request, or other uplink control information that may be scheduled via RRC or other suitable signaling (such as in any arbitrary uplink slot) .
  • Figure 7B illustrates one particular technique that the UE and the base station may employ to determine the uplink slot in which to reschedule a missed PUCCH transmission occasion.
  • Figure 7B illustrates an example in which the PUCCH is configured on only one uplink carrier (such as the primary uplink carrier operating at a lower frequency in the illustrated example) .
  • the PUCCH transmission that is scheduled during an invalid uplink slot on the primary uplink carrier may be delayed until a next valid uplink slot on the primary uplink carrier.
  • the UE and the base station may identify the scheduled slot for the PUCCH transmission based on a timing that is indicated via RRC signaling (such as for a CSI report) or DCI (such as for a HARQ-ACK associated with a PDSCH transmission) , and delay or postpone the PUCCH transmission until a next valid uplink slot on the primary uplink carrier, if the scheduled slot for the PUCCH transmission is determined to be an invalid slot based on the TDM slot pattern to be applied across the primary and secondary uplink carriers.
  • RRC signaling such as for a CSI report
  • DCI such as for a HARQ-ACK associated with a PDSCH transmission
  • Figure 7C illustrates another technique that the UE and the base station may employ to determine the uplink slot in which to reschedule a missed PUCCH transmission occasion in cases where the PUCCH is configured on only one uplink carrier (such as the primary uplink carrier operating at a lower frequency in the illustrated example) .
  • the UE and the base station may determine whether a PUSCH is to be transmitted in the scheduled uplink slot on the other (secondary) uplink carrier.
  • the PUCCH transmission may be included in (or “piggybacked onto” ) the PUSCH transmission in the other uplink carrier. Otherwise, as shown by reference number 732, the PUCCH transmission that is scheduled during the invalid uplink slot may be delayed until a next valid uplink slot in the primary uplink carrier, in a similar manner as shown in Figure 7B.
  • Figure 7D illustrates another particular technique that the UE and the base station may employ to determine the uplink slot in which to reschedule a missed PUCCH transmission occasion.
  • Figure 7D illustrates an example in which the PUCCH is configured on multiple uplink carriers (such as the primary uplink carrier and one or more secondary uplink carriers) .
  • the UE and the base station may determine an uplink slot in which the PUCCH is to be transmitted, and the PUCCH transmission may be scheduled on either the primary uplink carrier or the secondary uplink carrier depending on which uplink carrier has a valid uplink slot in the slot when the PUCCH is to be transmitted. For example, as shown by reference number 740, the PUCCH transmission may be performed on the primary uplink carrier because the uplink slot in which the PUCCH transmission is to be performed is valid on the primary uplink carrier.
  • another PUCCH transmission may be scheduled at a time that corresponds to an invalid uplink slot on the primary uplink carrier (due to the uplink slot pattern assigning the uplink slot to the secondary uplink carrier) .
  • the PUCCH transmission may be performed on the secondary uplink carrier because the uplink slot in which the PUCCH transmission is to be performed is valid on the secondary uplink carrier.
  • the UE transmits the PUCCH on a first uplink carrier in slot n if the uplink slot pattern assigns the uplink to the first uplink carrier in slot n.
  • the UE transmits the PUCCH on the second uplink carrier in slot n.
  • the PUCCH is configured on multiple uplink carriers, delays associated with having to delay or postpone a PUCCH scheduled during an invalid slot may be substantially reduced or eliminated because the PUCCH can be transmitted in the scheduled slot on whichever uplink carrier has the valid uplink slot.
  • configuring the PUCCH on multiple uplink carriers may ensure that the PUCCH can be transmitted according to the scheduled timing.
  • FIG. 8 is a diagram illustrating an example process 800 performed, for example, by a UE, in accordance with various aspects of the present disclosure.
  • Example process 800 is an example where a UE, such as the UE 120, performs operations associated with PUCCH transmission for time division multiplexed uplink carriers.
  • the process 800 may include receiving information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers (block 810) .
  • the UE such as using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller/processor 280
  • the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers.
  • the process 800 may include receiving information configuring a PUCCH on one or more of the multiple uplink carriers (block 820) .
  • the UE such as using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller/processor 280
  • the process 800 may include determining an uplink slot for a PUCCH transmission based at least in part on the uplink slot pattern and the information configuring the PUCCH (block 830) .
  • the UE (such as using controller/processor 280) may determine an uplink slot for a PUCCH transmission based at least in part on the uplink slot pattern and the information configuring the PUCCH, as described above.
  • the process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the PUCCH is configured on only one uplink carrier of the multiple uplink carriers, and determining the uplink slot for the PUCCH transmission includes identifying a scheduled slot for the PUCCH transmission on the one uplink carrier based at least in part on the information configuring the PUCCH, determining that the scheduled slot for the PUCCH transmission is an invalid slot based at least in part on the uplink slot pattern, and delaying the PUCCH transmission until a next valid uplink slot on the one uplink carrier, with the uplink slot for the PUCCH transmission corresponding to the next valid uplink slot on the one uplink carrier.
  • the PUCCH transmission is delayed until the next valid uplink slot on the one uplink carrier based at least in part on the scheduled slot for the PUCCH transmission not having a scheduled PUSCH transmission on another one of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission.
  • the PUCCH is configured on only a first uplink carrier of the multiple uplink carriers, and determining the uplink slot for the PUCCH transmission includes identifying a scheduled slot for the PUCCH transmission on the first uplink carrier based at least in part on the information configuring the PUCCH, determining that the scheduled slot for the PUCCH transmission on the first uplink carrier is an invalid slot based at least in part on the uplink slot pattern, and determining that the scheduled slot on the first uplink carrier has a PUSCH transmission occasion on a second uplink carrier of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission, with content to be carried in the PUCCH transmission transmitted by the PUSCH on the second uplink carrier.
  • the information configuring the PUCCH includes a timing for the PUCCH transmission that is indicated via one or more of an RRC message or DCI.
  • the timing is related to an uplink transmission of one or more of a HARQ associated with a PDSCH transmission, a CSI report, or a scheduling request.
  • the multiple uplink carriers include a first uplink carrier associated with a TDD configuration and one or more second uplink carriers associated with one or more of an SUL configuration, an FDD configuration, or another TDD configuration.
  • Figure 8 shows example blocks of the process 800
  • the process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 8. Additionally, or alternatively, two or more of the blocks of the process 800 may be performed in parallel.
  • FIG. 9 is a diagram illustrating an example process 900 performed, for example, by a base station, in accordance with various aspects of the present disclosure.
  • Example process 900 is an example where a base station, such as the base station 110, performs operations associated with PUCCH transmission for time division multiplexed uplink carriers.
  • the process 900 may include transmitting, to a UE, information configuring multiple uplink carriers that are time division multiplexed with one another, where the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers (block 910) .
  • the base station (such as using controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234) may transmit, to a UE, information configuring multiple uplink carriers that are time division multiplexed with one another, as described above.
  • the information configuring the multiple uplink carriers includes an uplink slot pattern to be applied across the multiple uplink carriers.
  • the process 900 may include transmitting, to the UE, information configuring a PUCCH on one or more of the multiple uplink carriers (block 920) .
  • the base station (such as using controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234) may transmit, to the UE, information configuring a PUCCH on one or more of the multiple uplink carriers, as described above.
  • the process 900 may include identifying an uplink slot to receive a PUCCH transmission from the UE based at least in part on the uplink slot pattern and the information configuring the PUCCH (block 930) .
  • the base station (such as using controller/processor 240) may identify an uplink slot to receive a PUCCH transmission from the UE based at least in part on the uplink slot pattern and the information configuring the PUCCH, as described above.
  • the process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the PUCCH transmission is received in the next valid uplink slot on the one uplink carrier based at least in part on the scheduled slot for the PUCCH transmission not having a scheduled PUSCH transmission on another one of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission.
  • the PUCCH is configured on only a first uplink carrier of the multiple uplink carriers, and identifying the uplink slot to receive the PUCCH transmission includes identifying a scheduled slot for the PUCCH transmission on the first uplink carrier based at least in part on the information configuring the PUCCH, determining that the scheduled slot for the PUCCH transmission on the first uplink carrier is an invalid slot based at least in part on the uplink slot pattern, and determining that the scheduled slot on the first uplink carrier has a PUSCH transmission occasion on a second uplink carrier of the multiple uplink carriers that has a valid uplink slot in the scheduled slot for the PUCCH transmission, with content to be carried in the PUCCH transmission transmitted by the PUSCH on the second uplink carrier.
  • the PUCCH is configured on at least a first uplink carrier and a second uplink carrier among the multiple uplink carriers, and identifying the uplink slot to receive the PUCCH transmission includes identifying a scheduled slot for the PUCCH transmission based at least in part on the information configuring the PUCCH and identifying, among the first uplink carrier and the second uplink carrier, an uplink carrier that has a valid uplink slot in the scheduled slot for the PUCCH transmission based at least in part on the uplink slot pattern, with the uplink slot for the PUCCH transmission corresponding to the valid uplink slot on the determined uplink carrier.
  • the information configuring the PUCCH includes a timing for the PUCCH transmission that is indicated via one or more of an RRC message or DCI.
  • the multiple uplink carriers include a first uplink carrier associated with a TDD configuration and one or more second uplink carriers associated with one or more of an SUL configuration, an FDD configuration, or another TDD configuration.
  • Figure 9 shows example blocks of the process 900
  • the process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 9. Additionally, or alternatively, two or more of the blocks of the process 900 may be performed in parallel.
  • the term “component” is intended to be broadly construed as hardware, firmware, or a combination of hardware and software.
  • a processor is implemented in hardware, firmware, or a combination of hardware and software.
  • the phrase “based on” is intended to be broadly construed to mean “based at least in part on. ”
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
  • a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
  • “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c.
  • the hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single-or multi-chip processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
  • a general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine.
  • a processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • particular processes and methods may be performed by circuitry that is specific to a given function.
  • the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents thereof, or in any combination thereof.
  • aspects of the subject matter described in this specification also can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a computer storage media for execution by, or to control the operation of, data processing apparatus.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program from one place to another.
  • a storage media may be any available media that may be accessed by a computer.
  • such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer.
  • Disk and disc includes compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine readable medium and computer-readable medium, which may be incorporated into a computer program product.

Landscapes

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

Abstract

Cette invention fournit des systèmes, des procédés et des appareils destinés à une transmission de canal de commande de liaison montante physique (PUCCH) pour des porteuses de liaison montante multiplexées par répartition dans le temps. Selon un aspect, une occasion de transmission de PUCCH manquée peut être replanifiée dans un créneau de liaison montante valide suivant, réduisant ainsi un retard dans la transmission d'informations de commande de liaison montante. Selon certains aspects, une occasion de transmission de PUCCH planifiée pendant un créneau de liaison montante invalide sur une porteuse de liaison montante peut être incluse dans une transmission de canal partagé de liaison montante physique (PUSCH) sur une autre porteuse de liaison montante comprenant un créneau de liaison montante valide dans le créneau lorsque l'occasion de transmission de PUCCH est planifiée, réduisant ainsi en outre les retards dans la transmission des informations de commande de liaison montante. Selon certains aspects, de multiples porteuses de liaison montante peuvent comprendre une configuration de PUCCH, qui permet à l'UE de sélectionner dynamiquement la porteuse de liaison montante pour la transmission de PUCCH (par exemple sur la base de laquelle la porteuse de liaison montante comprend un créneau de liaison montante valide dans le créneau lorsque le PUCCH doit être transmis).
PCT/CN2019/105814 2019-09-13 2019-09-13 Transmission de canal de commande de liaison montante physique pour des porteuses de liaison montante multiplexées par répartition dans le temps Ceased WO2021046833A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/105814 WO2021046833A1 (fr) 2019-09-13 2019-09-13 Transmission de canal de commande de liaison montante physique pour des porteuses de liaison montante multiplexées par répartition dans le temps

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/105814 WO2021046833A1 (fr) 2019-09-13 2019-09-13 Transmission de canal de commande de liaison montante physique pour des porteuses de liaison montante multiplexées par répartition dans le temps

Publications (1)

Publication Number Publication Date
WO2021046833A1 true WO2021046833A1 (fr) 2021-03-18

Family

ID=74866965

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/105814 Ceased WO2021046833A1 (fr) 2019-09-13 2019-09-13 Transmission de canal de commande de liaison montante physique pour des porteuses de liaison montante multiplexées par répartition dans le temps

Country Status (1)

Country Link
WO (1) WO2021046833A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022147687A1 (fr) * 2021-01-06 2022-07-14 Zte Corporation Procédé et dispositif de détermination de pucch de livre de codes harq-ack retardé
WO2022206932A1 (fr) * 2021-03-31 2022-10-06 Essen Innovation Company Limited Procédé de communication sans fil, équipement utilisateur et station de base
WO2022226864A1 (fr) * 2021-04-29 2022-11-03 Qualcomm Incorporated Évitement d'interférence dans des communications en duplex intégral

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019027989A2 (fr) * 2017-08-01 2019-02-07 Qualcomm Incorporated Définition et mappage de ressources de canal de contrôle de liaison montante à un équipement d'utilisateur
WO2019099709A1 (fr) * 2017-11-15 2019-05-23 Idac Holdings, Inc. Procédés pour accès en liaison montante supplémentaire dans des systèmes de communication sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019027989A2 (fr) * 2017-08-01 2019-02-07 Qualcomm Incorporated Définition et mappage de ressources de canal de contrôle de liaison montante à un équipement d'utilisateur
WO2019099709A1 (fr) * 2017-11-15 2019-05-23 Idac Holdings, Inc. Procédés pour accès en liaison montante supplémentaire dans des systèmes de communication sans fil

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
APPLE INC.: "Updated summary of enhancements to single Tx switched uplink for EN- DC", 3GPP DRAFT; R1-1903761 SUMMARY OF ENHANCEMENTS TO SINGLE TX SWITCHED UPLINK FOR EN-DC -V4, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, Greece; 20190225 - 20190301, 3 March 2019 (2019-03-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051691009 *
LG ELECTRONICS: "Summary of TDD Common aspects", 3GPP DRAFT; R1-1807527 SUMMARY OF TDD COMMON ASPECTS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Busan, Korea; 20180521 - 20180525, 24 May 2018 (2018-05-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051442826 *
ZTE, SANECHIPS: "Discussion on single TX transmission and solution", 3GPP DRAFT; R2-1712281 DISCUSSION ON SINGLE TX TRANSMISSION AND SOLUTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, Nevada; 20171201, 17 November 2017 (2017-11-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051371385 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022147687A1 (fr) * 2021-01-06 2022-07-14 Zte Corporation Procédé et dispositif de détermination de pucch de livre de codes harq-ack retardé
WO2022206932A1 (fr) * 2021-03-31 2022-10-06 Essen Innovation Company Limited Procédé de communication sans fil, équipement utilisateur et station de base
WO2022226864A1 (fr) * 2021-04-29 2022-11-03 Qualcomm Incorporated Évitement d'interférence dans des communications en duplex intégral

Similar Documents

Publication Publication Date Title
US11350416B2 (en) Physical uplink control channel repetition configuration
US10917226B2 (en) Techniques and apparatuses for time division multiplexing for dual-rat communication
US12016032B2 (en) Communicating multiple transport formats in a slot with full-duplex
US11172430B2 (en) Uplink control channel resource allocation
US11601933B2 (en) Techniques and apparatuses for slot-based and non-slot-based scheduling in 5G
CN115243361A (zh) 系统信息速率匹配
CN112106308A (zh) 用于确定与信道状态信息参考信号(csi-rs)有关的上行链路传输时间线的技术和装置
US11012913B2 (en) User equipment capability-based transition
WO2021046833A1 (fr) Transmission de canal de commande de liaison montante physique pour des porteuses de liaison montante multiplexées par répartition dans le temps
EP3753333A1 (fr) Mise à jour d'une fonction de hachage d'un canal physique de commande de liaison descendante
US11678373B2 (en) Multiplexing channel state information reports in multiple transmit-receive point (TRP) scenarios
WO2021042315A1 (fr) Configuration de format de créneau pour des modes de multiplexage par répartition dans le temps
WO2020019101A1 (fr) Utilisation d'une région de commande pour une transmission en liaison descendante
US11044064B2 (en) Determining hybrid automatic repeat request (HARQ) processes for multi-transmit receive point (TRP)
US20210068106A1 (en) Decoding of semi-persistent scheduling occasions
KR102672868B1 (ko) 랜덤 액세스 절차 메시지들에 대한 리소스 할당
WO2021047293A1 (fr) Configuration semi-statique de créneaux pour porteuses de liaison montante multiplexées par répartition dans le temps
US11259334B2 (en) Code-block-based communication for random access channel
US10856284B2 (en) Resource allocation for a short transmission time interval (STTI) system

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19945292

Country of ref document: EP

Kind code of ref document: A1