WO2021035392A1 - Techniques pour des transmissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci) - Google Patents

Techniques pour des transmissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci) Download PDF

Info

Publication number
WO2021035392A1
WO2021035392A1 PCT/CN2019/102257 CN2019102257W WO2021035392A1 WO 2021035392 A1 WO2021035392 A1 WO 2021035392A1 CN 2019102257 W CN2019102257 W CN 2019102257W WO 2021035392 A1 WO2021035392 A1 WO 2021035392A1
Authority
WO
WIPO (PCT)
Prior art keywords
preemption indication
uci
node
pusch
data
Prior art date
Application number
PCT/CN2019/102257
Other languages
English (en)
Inventor
Qiaoyu Li
Chao Wei
Min Huang
Yu Zhang
Original Assignee
Qualcomm Incorporated
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 Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2019/102257 priority Critical patent/WO2021035392A1/fr
Priority to PCT/CN2020/110654 priority patent/WO2021036961A1/fr
Publication of WO2021035392A1 publication Critical patent/WO2021035392A1/fr

Links

Images

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
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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/0037—Inter-user or inter-terminal allocation
    • 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/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H04B7/15542—Selecting at relay station its transmit and receive resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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/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

Definitions

  • aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to uplink control information (UCI) based uplink preemption indication transmissions.
  • UCI uplink control information
  • Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, and orthogonal frequency-division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.
  • CDMA code-division multiple access
  • TDMA time-division multiple access
  • FDMA frequency-division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • 5G communications technology can include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.
  • URLLC ultra-reliable-low latency communications
  • full duplex communication with respect to integrated access and backhaul (IAB) implementations may increase transmission speed and flexibility but also transmission complexity.
  • improvements in wireless communication operations may be desired.
  • a method of wireless communication at a first node may include transmitting data on an uplink communication channel to a second node.
  • the method may further include determining a collision with a reception of different data from a third node.
  • the method may further include transmitting, after transmission of the data, uplink control information (UCI) including a preemption indication representing a punctured uplink transmission of the data to the second node, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources, and wherein the preemption indication comprises a value identifying one or more of the number of time or frequency resources within the preemption indication cycle corresponding to the punctured uplink transmission.
  • UCI uplink control information
  • a method of wireless communication at a first node may include determining that data is to be received on an uplink communication channel from a second node. The method further include receiving, from the second node, UCI including a preemption indication representing a punctured uplink reception of the data after receiving the data. The method may further include receiving, the data from the second node, wherein at least one symbol is punctured as part of the transmission of the data, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources, and wherein the preemption indication comprises a value identifying one or more of the number of time or frequency resources within the indication cycle corresponding to the punctured uplink transmission.
  • an apparatus for wireless communication includes a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of the methods described herein.
  • an apparatus for wireless communication is provided that includes means for performing the operations of methods described herein.
  • a non-transitory computer-readable medium is provided including code executable by one or more processors to perform the operations of the methods described herein.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 illustrates an example of a wireless communication system, in accordance with various aspects of the present disclosure
  • FIG. 2 is a block diagram illustrating an example of a network entity (also referred to as a base station) , in accordance with various aspects of the present disclosure
  • FIG. 3 is a conceptual diagram of an example self-interference scenario in a wireless communication system, in accordance with various aspects of the present disclosure
  • FIG. 4 is a diagram of an example integrated access and backhaul (IAB) system, in accordance with various aspects of the present disclosure
  • FIG. 5 is a diagram of an example communication scenario in an IAB system, in accordance with various aspects of the present disclosure
  • FIG. 6 is a diagram of an example implementation of an uplink control information (UCI) encoding scheme, in accordance with various aspects of the present disclosure
  • FIG. 7 is a flow chart illustrating an example of a method for wireless communications at a first node such as an IAB node, in accordance with various aspects of the present disclosure
  • FIG. 8 is a flow chart illustrating an example of a method for wireless communications at a first node such as a parent node, in accordance with various aspects of the present disclosure.
  • FIG. 9 is a block diagram illustrating an example of a MIMO communication system including a base station and a UE, in accordance with various aspects of the present disclosure.
  • the described features generally relate to uplink control information (UCI) based uplink preemption indication transmissions in an integrated access and backhaul (IAB) system where one or more nodes employ full-duplex communication.
  • base stations may include a backhaul interface for communication with a backhaul portion of the network.
  • the backhaul may provide a link between a base station and a core network, and in some examples, the backhaul may provide interconnection between the respective base stations.
  • the core network is a part of a wireless communication system that is generally independent of the radio access technology used in the radio access network.
  • Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • Some base stations may be configured as IAB nodes, where the wireless spectrum may be used both for access links (i.e., wireless links with user equipments (UEs) ) , and for backhaul links, which may be referred to as wireless self-backhauling.
  • access links i.e., wireless links with user equipments (UEs)
  • backhaul links which may be referred to as wireless self-backhauling.
  • network entities such as base stations and UEs may employ full-duplex operations, where such entities may both receive and transmit signals simultaneously.
  • a common or same frequency and time resource may be used for downlink and uplink transmission.
  • the full-duplex IAB node can simultaneously transmit uplink data towards the parent-node, and receive the uplink data from the UE and/or child node.
  • the IAB node may also transmit downlink data towards the child node, and receive the downlink data from the parent node.
  • a base station communicating with at least two UEs according to full-duplex may experience self-interference (e.g., as shown in FIG. 3) .
  • self-interference may refer to the interference each transmitter generates for the receiver (s) in the same node.
  • self-interference may be experienced at the base station (e.g., gNB) from the transmission of UE1’s physical downlink shared channel (PDSCH) towards the reception of UE2’s physical uplink shared channel (PUSCH) .
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • UCI may be transmitted on the uplink by PUSCH (or PUCCH) and carry various information such as, but not limited to, scheduling requests (SRs) , hybrid automatic repeat request (HARQ) acknowledgments (ACK) /negative ACK (NACK) , and/or channel state information (CSI) .
  • SRs scheduling requests
  • HARQ hybrid automatic repeat request
  • ACK acknowledgments
  • NACK negative ACK
  • CSI channel state information
  • UCI HARQ-ACK and/or CSI
  • UCI may be multiplexed with uplink shared channel (UL-SCH) data in PUSCH. That is, UCI (e.g., including at least one of HARQ-ACK and CSI report (s) ) multiplexing with UL-SCH data in PUSCH may be supported.
  • UCI may be transmitted in PUSCH without any UL-SCH data.
  • the resource of the multiplexed UCI may be structured such that a base station (e.g., gNB) may dynamically or via semi-persistent scheduling (SPS) indicate beta-offsets as parameters regarding HARQ-ACK and/or CSI-reports (e.g., for CSI-part-1 and CSI-part-2 respectively) , where the resource quantities of the respective UCI components may be further determined according to these parameters. For example, a priority may be determined or designated based first on HARQ-ACK, then CSI-reports, and lastly UL-SCH data. Further, different CSI reports may have different priorities, while the same CSI report may include CSI-Part-1 and CSI-Part-2, where CSI-Part-2 has lower priority.
  • SPS semi-persistent scheduling
  • payloads of HARQ-ACK, CSI-part-1, and CSI-part-2 may be sequentially mapped to their resources determined as above, wherein HARQ-ACK payload do not need omission.
  • certain parts of the information bits of the CSI reports may be omitted, until the actual coding rate of the CSI report can be lower than an identified target coding rate.
  • the slot can also be used to receive uplink traffic from a UE or child node.
  • the UE or child node has an urgent ultra-reliable low-latency communication (URLLC) uplink traffic with mini-slot scheduling other than regular traffic, in order to avoid self-interference at the IAB node, the IAB node may puncture the PUSCH towards the parent node for the symbols used by the urgent UL URLLC traffic. In this case, preemption indication for uplink transmissions from the IAB node towards parent node may be desirable.
  • URLLC ultra-reliable low-latency communication
  • a first node such as an IAB node in an IAB system may transmit data on an uplink communication channel to a second node.
  • the data can be associated with a priority level.
  • the first node may further determine a collision with a reception of different data from a third node.
  • the first node may further transmit, after transmission of the data, UCI including a preemption indication representing a punctured uplink transmission of the data to the second node, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources.
  • the UCI may be associated with a preemption indication cycle representing a number of time or frequency resources, and the preemption indication may include a value identifying one or more of the number of time or frequency resources within the preemption indication cycle corresponding to the punctured uplink transmission.
  • a first node such as a parent node in an IAB system may determine that data is to be received on an uplink communication channel from a second node.
  • the data can be associated with a priority level.
  • the first node may further receive, from a second node, UCI including a preemption indication representing a punctured uplink reception of the data after receiving the data.
  • the first node may further receive, the data from the second node, wherein at least one symbol is punctured as part of the transmission of the data.
  • the UCI may be associated with a preemption indication cycle representing a number of time or frequency resources, and the preemption indication may include a value identifying one or more of the number of time or frequency resources within the indication cycle corresponding to the punctured uplink transmission.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device can be a component.
  • One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • the components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA) , etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases 0 and A are commonly referred to as CDMA2000 1X, 1X, etc.
  • IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD) , etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB) , Evolved UTRA (E-UTRA) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM TM , etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM TM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) .
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band.
  • LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to fifth generation (5G) NR networks or other next generation communication systems) .
  • 5G fifth generation
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100.
  • the wireless communications system (also referred to as a wireless wide area network (WWAN) ) can include base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and/or a 5G Core (5GC) 190.
  • the base stations 102 which may also be referred to as network entities, may include macro cells (high power cellular base station) and/or small cells (low power cellular base station) .
  • the macro cells can include base stations.
  • the small cells can include femtocells, picocells, and microcells.
  • the base stations 102 may also include gNBs 180, as described further herein.
  • some nodes acting as an IAB node may have a modem 240 and communicating component 242 for UCI based uplink preemption indication transmissions, as described herein.
  • a base station 102/gNB 180 is shown as having the modem 240 and communicating component 242, this is one illustrative example, and substantially any node or type of node acting as an IAB node may include a modem 240 and communicating component 242 for providing corresponding functionalities described herein.
  • the base stations 102 configured for 4G LTE (which can collectively be referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through backhaul links 132 (e.g., using an S1 interface) .
  • the base stations 102 configured for 5G NR (which can collectively be referred to as Next Generation RAN (NG-RAN) ) may interface with 5GC 190 through backhaul links 184.
  • NG-RAN Next Generation RAN
  • the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • NAS non-access stratum
  • RAN radio access network
  • MBMS multimedia broadcast multicast service
  • RIM RAN information management
  • the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over backhaul links 134 (e.g., using an X2 interface) .
  • the backhaul links 132, 134 and/or 184 may be wired or wireless.
  • the base stations 102 may wirelessly communicate with one or more UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102.
  • a network that includes both small cell and macro cells may be referred to as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group, which can be referred to as a closed subscriber group (CSG) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104.
  • the communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • the communication links may be through one or more carriers.
  • the base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • D2D communication link 158 may use the DL/UL WWAN spectrum.
  • the D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia,
  • the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • the small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • a base station 102 may include an eNB, gNodeB (gNB) , or other type of base station.
  • Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE 104.
  • mmW millimeter wave
  • mmW millimeter wave
  • mmW base station Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters.
  • Radio waves in the band may be referred to as a millimeter wave.
  • Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW /near mmW radio frequency band has extremely high path loss and a short range.
  • the mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
  • a base station 102 referred to herein can include a gNB 180.
  • the EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • IP Internet protocol
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • the 5GC 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195.
  • the AMF 192 may be in communication with a Unified Data Management (UDM) 196.
  • the AMF 192 can be a control node that processes the signaling between the UEs 104 and the 5GC 190.
  • the AMF 192 can provide QoS flow and session management.
  • User Internet protocol (IP) packets (e.g., from one or more UEs 104) can be transferred through the UPF 195.
  • the UPF 195 can provide UE IP address allocation for one or more UEs, as well as other functions.
  • the UPF 195 is connected to the IP Services 197.
  • the IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.
  • the base station may also be referred to as a gNB, Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology.
  • the base station 102 provides an access point to the EPC 160 or 5GC 190 for a UE 104.
  • Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a positioning system (e.g., satellite, terrestrial) , a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, robots, drones, an industrial/manufacturing device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet) ) , a vehicle/avehicular device, a meter (e.g., parking meter, electric meter, gas meter, water meter, flow meter) , a gas pump, a large or small kitchen appliance, a medical/healthcare device, an implant, a sensor
  • IoT devices e.g., meters, pumps, monitors, cameras, industrial/manufacturing devices, appliances, vehicles, robots, drones, etc.
  • IoT UEs may include MTC/enhanced MTC (eMTC, also referred to as CAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs.
  • eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies.
  • eMTC may include FeMTC (further eMTC) , eFeMTC (enhanced further eMTC) , mMTC (massive MTC) , etc.
  • NB-IoT may include eNB-IoT (enhanced NB-IoT) , FeNB-IoT (further enhanced NB-IoT) , etc.
  • the UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • one example of an implementation of a node acting as an IAB node such as base station 102 (e.g., a base station 102 and/or gNB 180, as described above) may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors 212 and memory 216 and transceiver 202 in communication via one or more buses 244, which may operate in conjunction with modem 240 and/or communicating component 242 for UCI based uplink preemption indication transmissions.
  • the communicating component 242 may include UCI 252 which in turn includes a preemption indication 254 representing a punctured uplink transmission of the data to the second node after transmission of the data, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources.
  • the preemption indication 254 may include a value identifying one or more of the number of time or frequency resources within the indication cycle corresponding to the punctured uplink transmission.
  • the one or more processors 212 can include a modem 240 and/or can be part of the modem 240 that uses one or more modem processors.
  • the various functions related to communicating component 242 may be included in modem 240 and/or processors 212 and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors.
  • the one or more processors 212 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver 202. In other aspects, some of the features of the one or more processors 212 and/or modem 240 associated with communicating component 242 may be performed by transceiver 202.
  • memory 216 may be configured to store data used herein and/or local versions of applications 275 or communicating component 242 and/or one or more of its subcomponents being executed by at least one processor 212.
  • Memory 216 can include any type of computer-readable medium usable by a computer or at least one processor 212, such as random access memory (RAM) , read only memory (ROM) , tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
  • RAM random access memory
  • ROM read only memory
  • tapes such as magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
  • memory 216 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining communicating component 242 and/or one or more of its subcomponents, and/or data associated therewith, when UE 104 is operating at least one processor 212 to execute communicating component 242 and/or one or more of its subcomponents.
  • Transceiver 202 may include at least one receiver 206 and at least one transmitter 208.
  • Receiver 206 may include hardware and/or software executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • Receiver 206 may be, for example, a radio frequency (RF) receiver.
  • RF radio frequency
  • receiver 206 may receive signals transmitted by at least one base station 102. Additionally, receiver 206 may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR) , reference signal received power (RSRP) , received signal strength indicator (RSSI) , etc.
  • SNR signal-to-noise ratio
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • Transmitter 208 may include hardware and/or software executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • a suitable example of transmitter 208 may including, but is not limited to, an RF transmitter.
  • UE 104 may include RF front end 288, which may operate in communication with one or more antennas 265 and transceiver 202 for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by UE 104.
  • RF front end 288 may be connected to one or more antennas 265 and can include one or more low- noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals.
  • the antennas 265 may include one or more antennas, antenna elements, and/or antenna arrays.
  • LNA 290 can amplify a received signal at a desired output level.
  • each LNA 290 may have a specified minimum and maximum gain values.
  • RF front end 288 may use one or more switches 292 to select a particular LNA 290 and its specified gain value based on a desired gain value for a particular application.
  • one or more PA (s) 298 may be used by RF front end 288 to amplify a signal for an RF output at a desired output power level.
  • each PA 298 may have specified minimum and maximum gain values.
  • RF front end 288 may use one or more switches 292 to select a particular PA 298 and its specified gain value based on a desired gain value for a particular application.
  • one or more filters 296 can be used by RF front end 288 to filter a received signal to obtain an input RF signal.
  • a respective filter 296 can be used to filter an output from a respective PA 298 to produce an output signal for transmission.
  • each filter 296 can be connected to a specific LNA 290 and/or PA 298.
  • RF front end 288 can use one or more switches 292 to select a transmit or receive path using a specified filter 296, LNA 290, and/or PA 298, based on a configuration as specified by transceiver 202 and/or processor 212.
  • transceiver 202 may be configured to transmit and receive wireless signals through one or more antennas 265 via RF front end 288.
  • transceiver may be tuned to operate at specified frequencies such that UE 104 can communicate with, for example, one or more base stations 102 or one or more cells associated with one or more base stations 102.
  • modem 240 can configure transceiver 202 to operate at a specified frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by modem 240.
  • modem 240 can be a multiband-multimode modem, which can process digital data and communicate with transceiver 202 such that the digital data is sent and received using transceiver 202.
  • modem 240 can be multiband and be configured to support multiple frequency bands for a specific communications protocol.
  • modem 240 can be multimode and be configured to support multiple operating networks and communications protocols.
  • modem 240 can control one or more components of UE 104 (e.g., RF front end 288, transceiver 202) to enable transmission and/or reception of signals from the network based on a specified modem configuration.
  • the modem configuration can be based on the mode of the modem and the frequency band in use.
  • the modem configuration can be based on UE configuration information associated with UE 104 as provided by the network during cell selection and/or cell reselection.
  • the processor (s) 212 may correspond to one or more of the processors described in connection with the UE in FIG. 9.
  • the memory 216 may correspond to the memory described in connection with the UE in FIG. 9.
  • FIG. 3 is a diagram of a self-interference scenario 300 that may occur at a node, as described herein.
  • a base station communicating with at least two UEs according to full-duplex may experience self-interference (e.g., as shown in FIG. 3) .
  • self-interference may refer to the interference each transmitter generates for the receiver (s) in the same node.
  • self-interference may be experienced at the base station (e.g., gNB) from the transmission of UE1’s physical downlink shared channel (PDSCH) towards the reception of UE2’s physical uplink shared channel (PUSCH) .
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • FIG. 4 is a diagram of an uplink and downlink communication scheme 400 in an IAB system, as described herein.
  • the full-duplex IAB node can simultaneously transmit uplink data towards the parent-node, and receive the uplink data from the UE and/or child node.
  • the IAB node may also transmit downlink data towards the child node, and receive the downlink data from the parent node.
  • FIG. 5 is a diagram of a communication scheme in an IAB system 500 in which an IAB node may puncture a PUSCH symbol to transmit high priority data, as described herein.
  • an IAB node may puncture a PUSCH symbol to transmit high priority data, as described herein.
  • the slot can also be used to receive uplink traffic from a UE or child node.
  • the UE or child node has an urgent ultra-reliable low-latency communication (URLLC) uplink traffic with mini-slot scheduling other than regular traffic, in order to avoid self-interference at the IAB node, the IAB node may puncture the PUSCH towards the parent node for the symbols used by the urgent UL URLLC traffic.
  • URLLC ultra-reliable low-latency communication
  • preemption indication for uplink transmissions from the IAB node towards parent node may be desirable.
  • the priority level for the high priority data is higher than a priority level of another data transmission (e.g., the regular traffic) so that the other data transmission is being punctured with this high priority data transmission.
  • the regular traffic may correspond to enhanced mobile broadband (eMBB) .
  • eMBB enhanced mobile broadband
  • the present aspects may support UCI based uplink preemption indication (UL-PI) transmissions according to at least one of a number of implementations.
  • UCI may be used for UL-PI associated with a UL-PI indication cycle.
  • UCI of the UL-PI may be multiplexed with PUSCH.
  • the UCI of UL-PI may be associated with UL-PI indication cycle #M, and can be multiplexed with at least the first scheduled PUSCH within UL-PI indication cycle # (M+1) .
  • transmission of the UL-PI associated with a UL-PI indication cycle may depend on whether preemption has occurred in the cycle.
  • UCI of the UL-PI may be separately encoded with other UCI of HARQ-ACK/CSI-reports/SR, or jointly encoded with CSI-reports.
  • the UL-PI granularity may depend on the resource quantity comprising UCI of UL-PI in PUSCH.
  • a node such as a gNB may separately configure/indicate the resource quantity in the PUSCH comprising the UCI of UL-PI.
  • the number of bits in the UL-PI and the preemption status that each bit can indicate may be associated with the resource quantity.
  • the UCI may be used for UL-PI associated with an UL-PI indication cycle.
  • the UL-PI payload may include similar forms as in DL-PI (i.e., each UL-PI bit is associated with a set of predefined time-frequency resources within the indication cycle) .
  • the UL-PI indication cycle can be configured by the gNB or predefined.
  • the UL-PI indication cycle may only be applied to a certain number of PUSCH slots (e.g., that are not contiguous in time-domain) .
  • a number of UL-PI bits and the connection between the bits and certain time-frequency resources can be fixed, or configured by a gNB.
  • a gNB may configure the UL-PI indication cycle to 14 OFDM symbols. The gNB may further configure that the number of UL-PI bits is 14, and that each bit indicates the preemption status of a corresponding OFDM symbol out of the 14 symbols. In another example, a gNB may configure the UL-PI indication cycle to 5 PUSCH slots, where each includes 8-PRBs. The gNB may further configure that the number of UL-PI bits is 10, the first 5 bits indicate the preemption status of a corresponding PUSCH slot out of the 5 PUSCH slots within the first 4 PRBs, while the last 5 bits indicate the preemption status of a corresponding PUSCH slot out of the 5 PUSCH slots within the last 4 PRBs.
  • the UL-PI associated with UL-PI indication cycle #M can be multiplexed with a first scheduled PUSCH within UL-PI indication cycle #(M+1) .
  • the UL-PI associated with UL-PI indication cycle #M can also be multiplexed with multiple PUSCHs within UL-PI indication cycle # (M+1) , or within multiple PUSCHs within multiple UL-PI indication cycles # (M+1) , # (M+2) , # (M+3) , etc.
  • the gNB may carry out blind detection to see if the UL-PI is actually transmitted.
  • the UCI of UL-PI may be separately encoded with other UCI of HARQ-ACK/CSI-reports/SR.
  • the resource used by UCI of UL-PI may start from the last symbol of the PUSCH.
  • the other UCI may comprise at least one resource starting from the first symbol of the PUSCH, this may reduce the blind-detection efforts at the gNB.
  • HARQ-ACK may also require blind-detection
  • placing the UCI of UL-PI also in the front may result in similar implementations.
  • UCI of UL-PI may be jointly encoded with CSI-reports.
  • a 1-bit may be added in CSI part-1 to indicate whether there is UL-PI in CSI part-2.
  • An omission priority may also be identified for the UL-PI, and CSI-omission may be carried out considering both CSI-reports and UL-PI, where the identification may be based on network configuration or standard predefinition.
  • certain parts of the information bits of the CSI reports may be omitted, until the actual coding rate of the CSI report can be lower than an identified target coding rate.
  • the omission priority level may be associated with omission priority levels of multiple components of CSI feedbacks for the UCI including the preemption indication, and a CSI and preemption indication omission for jointly encoding the CSI and the preemption indication to be multiplexed with the PUSCH based at least in part on priority levels of the preemption indication and the multiple components of the CSI feedback.
  • an UL-PI indication cycle may be one PUSCH slot.
  • UCI of the UL-PI may be separately encoded with other UCIs.
  • the resource in PUSCH for UL-PI may start from the last symbol of the PUSCH.
  • the gNB may separately configure or otherwise indicate a Beta_Offset_UL-PI for UCI of UL-PI such that the resource quantity in the PUSCH comprising the UL-PI is identified based on the Beta_Offset_UL-PI.
  • the number of bits and the preemption status that each bit can indicate may be associated with the network configured/indicated Beta_Offset_UL-PI.
  • the UL-PI indication cycle may be a single PUSCH slot comprising 14 OFDM symbols.
  • the Beta_Offset may correspond to an UL-PI including 1-bit, and indicating whether there was preemption during the corresponding slot.
  • Beta_Offset may correspond to an UL-PI that includes 2-bits, and each bit indicates whether there was preemption during the first or second half of the corresponding slot, respectively.
  • Beta_Offset may correspond to ab UL-PI that includes 14-bits, and each bit indicates whether there was preemption during the 1/2/.../14th symbol of the corresponding slot, respectively.
  • FIGS. 7 and 8 aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional.
  • FIGS. 7 and 8 are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation.
  • the following actions, functions, and/or described components may be performed by reference to one or more components of FIGS. 2 and/or 8, as described herein, a specially-programmed processor, a processor executing specially-programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions.
  • FIG. 7 illustrates a flow chart of an example of a method 700 for wireless communication at a first node, which may be an IAB node.
  • a base station 102 can perform the functions described in method 700 using one or more of the components described in FIGS. 1, 2, and 9.
  • the method 700 may transmit data on an uplink communication channel to a second node.
  • the data can be associated with a priority level.
  • the priority level associated with the data can be higher than a priority level of lower priority data as described with reference to FIG. 5.
  • the communicating component 242 e.g., in conjunction with processor (s) 212, memory 216, and/or transceiver 202, may be configured to transmit data on an uplink communication channel to a second node.
  • the base station 102, the processor (s) 212, the communicating component 242 or one of its subcomponents may define the means for transmitting data on an uplink communication channel to a second node.
  • the method 700 may determine a collision with a reception of different data from a third node.
  • the first node e.g., IAB-node
  • the first node may be communicating data of a first traffic type (e.g., eMBB) with a second node (e.g., parent node) .
  • the first node may determine that a collision occurs with a recepetion of different data from a third node (e.g., child node or UE) that is communicating the different data (e.g., URLCC, which may have a higher priority level than eMBB) .
  • a third node e.g., child node or UE
  • the communicating component 242 e.g., in conjunction with processor (s) 212, memory 216, and/or transceiver 202, may be configured to determine a collision with a reception of different data from a third node.
  • the base station 102, the processor (s) 212, the communicating component 242 or one of its subcomponents may define the means for determining a collision with a reception of different data from a third node.
  • the third node may be a child node or a UE.
  • the method 700 may transmit, after transmission of the data, UCI including a preemption indication representing a punctured uplink transmission of the data to the second node, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources, and wherein the preemption indication comprises a value identifying one or more of the number of time or frequency resources within the preemption indication cycle corresponding to the punctured uplink transmission.
  • the communicating component 242 e.g., in conjunction with processor (s) 212, memory 216, and/or transceiver 202, may be configured to transmit, after transmission of the data, UCI 252 including a preemption indication 254 representing a punctured uplink transmission of the data to the second node.
  • the network entity 102, the processor (s) 312, the determining component 342 or one of its subcomponents may define the means for transmitting, after transmission of the data, UCI including a preemption indication representing a punctured uplink transmission of the data to the second node.
  • the method 700 may include identifying a preemption indication cycle configuration, and configuring the number of time or frequency resources of the preemption indication cycle based on the preemption indication cycle configuration.
  • the preemption indication cycle may include two or more non-contiguous time slots of a PUSCH.
  • the value of the preemption indication may identify at least one PUSCH.
  • transmitting the preemption indication may include multiplexing the UCI including the preemption indication with a scheduled PUSCH transmission, and transmitting the multiplexed UCI including the preemption indication.
  • the scheduled PUSCH transmission is associated with a distinct preemption indication cycle that is after the preemption indication cycle to be indicated by the preemption indication.
  • multiplexing the UCI includes multiplexing with multiple PUSCHs associated with a distinct preemption indication cycle that is after the preemption indication cycle to be indicated by the preemption indication.
  • multiplexing the UCI includes multiplexing with multiple PUSCHs associated with multiple distinct preemption indication cycles that is after the preemption indication cycle to be indicated by the preemption indication.
  • the preemption indication is associated with a first preemption indication cycle
  • the method 700 may include determining whether the punctured uplink transmission occurs during the associated preemption indication cycle, and wherein transmitting the multiplexed preemption indication is in response to determining that the punctured uplink transmission does occur during the associated preemption indication cycle.
  • the UCI including the preemption indication multiplexed with the PUSCH may be separately encoded with one or more other UCIs multiplexed with the PUSCH, and at least one resource of the UCI including the preemption indication is mapped starting from a last symbol of the PUSCH.
  • the method 700 may include encoding the UCI multiplexed with a PUSCH including the preemption indication jointly with at least one other UCI multiplexed with the PUSCH and including CSI feedback.
  • the UCI including the preemption indication may be encoded within a Part-2 CSI feedback of the CSI feedback, the Part-2 CSI feedback includes a single bit indicating whether the UCI includes the preemption indication in the Part-2 CSI feedback.
  • determining that data is to be transmitted on an uplink communication channel to a second node may be based on a priority level of the data.
  • priority levels may be related to different level of priorities of a traffic type.
  • traffic types may include enhanced mobile broadband (eMBB) as one traffic type and URLLC as another, where URLCC may have a higher priority level than eMBB.
  • eMBB enhanced mobile broadband
  • the preemption indication may be beneficial because when higher priority traffic (e.g., URLLC) is to be received by the first node (e.g., IAB-node) , the currently transmitted PUSCH towards the parent node (e.g., eMBB) may be punctured for the symbols where the URLLC is to be received.
  • higher priority traffic e.g., URLLC
  • the parent node e.g., eMBB
  • the forgoing occurs after the whole eMBB transmission because the eMBB may be slot-level scheduled and there may be no existing process to monitor URLLC mini-slot level changes.
  • the method 700 may include identifying at least one of an omission priority level associated with omission priority levels of multiple components of CSI feedbacks for the UCI including the preemption indication, and a CSI and preemption indication omission for jointly encoding the CSI and the preemption indication to be multiplexed with the PUSCH based at least in part on priority levels of the preemption indication and the multiple components of the CSI feedback.
  • the method 700 may include receiving an offset configuration, and configuring an uplink resource quantity for the UCI including the preemption indication based on the offset configuration.
  • At least one of a number of bits forming the preemption indication or a preemption status of each bit of the number of bits is identified by the offset configuration.
  • the method 700 may include transmitting, on a physical uplink shared channel (PUSCH) , the data to the second node, wherein at least one symbol of the PUSCH is punctured as part of the transmission of the data on the PUSCH.
  • PUSCH physical uplink shared channel
  • the first node may be an IAB node in an IAB system
  • the second node may be a parent node in an IAB system
  • the third node may be a child node or a user equipment (UE) .
  • UE user equipment
  • FIG. 8 illustrates a flow chart of an example of a method 700 for wireless communication at a first node, which may be a parent node.
  • a base station 102 can perform the functions described in method 700 using one or more of the components described in FIGS. 1, 2, and 9.
  • the method 900 may determine that data is to be received on an uplink communication channel from a second node.
  • the data can be associated with a priority level.
  • the priority level associated with the data can be higher than a priority level of lower priority data as described with reference to FIG. 5.
  • the communicating component 242 e.g., in conjunction with processor (s) 212, memory 216, and/or transceiver 202, may be configured to determine that data is to be received on an uplink communication channel from a second node.
  • the base station 102, the processor (s) 212, the communicating component 242 or one of its subcomponents may define the means for determining that data is to be received on an uplink communication channel from a second node.
  • the method 900 may receive, from the second node, UCI including a preemption indication representing a punctured uplink reception of the data after receiving the data.
  • the communicating component 242 e.g., in conjunction with processor (s) 212, memory 216, and/or transceiver 202, may be configured to receive, from the second node, UCI 252 including a preemption indication 254 representing a punctured uplink reception of the data after receiving the data.
  • the base station 102, the processor (s) 212, the communicating component 242 or one of its subcomponents may define the means for receiving, from the second node, UCI including a preemption indication representing a punctured uplink reception of the data after receiving the data.
  • the method 800 may receive, the data from the second node, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources, and wherein the preemption indication comprises a value identifying one or more of the number of time or frequency resources within the indication cycle corresponding to the punctured uplink transmission.
  • the communicating component 242 e.g., in conjunction with processor (s) 212, memory 216, and/or transceiver 202, may be configured to receive, on a PUSCH, the data from the second node.
  • the network entity 102, the processor (s) 312, the determining component 342 or one of its subcomponents may define the means for receiving, on a PUSCH, the data from the second node.
  • the preemption indication cycle may include two or more non-contiguous time slots of a PUSCH.
  • the value of the preemption indication may identify at least one PUSCH.
  • receiving the preemption indication may include receiving a multiplexed UCI including the preemption indication.
  • the multiplexed UCI may be multiplexed with multiple PUSCHs associated with a distinct preemption indication cycle that is after the preemption indication cycle to be indicated by the preemption indication.
  • the multiplexed UCI may be multiplexed with multiple PUSCHs associated with multiple distinct preemption indication cycles that is after the preemption indication cycle to be indicated by the preemption indication.
  • the UCI including the preemption indication multiplexed with the PUSCH may be separately encoded with one or more other UCIs multiplexed with the PUSCH, and at least one resource of the UCI including the preemption indication is mapped starting from a last symbol of the PUSCH.
  • the UCI multiplexed with a PUSCH including the preemption indication may be separately or jointly encoded with at least one other UCI multiplexed with the PUSCH and including channel state information (CSI) feedback.
  • CSI channel state information
  • the UCI including the preemption indication may be encoded within a Part-2 CSI feedback of the CSI feedback, the Part-2 CSI feedback includes a single bit indicating whether the UCI includes the preemption indication in the Part-2 CSI feedback.
  • the multiplexed UCI is received on a last symbol of the PUSCH transmission.
  • the method 800 may further include transmitting an offset configuration to the second node, and configuring/identifying an uplink resource quantity for the UCI including the preemption indication based on the offset configuration.
  • At least one of a number of bits forming the preemption indication or a preemption status of each bit of the number of bits is identified by the a configured uplink resource quantity.
  • the second node may be an IAB node in an IAB system
  • the first node may be a parent node in an IAB system.
  • FIG. 9 is a block diagram of a MIMO communication system 900 including a base station 102, which may be acting as an IAB node or a parent node, and a UE 104.
  • the MIMO communication system 900 may illustrate aspects of the wireless communication access network 100 described with reference to FIG. 1.
  • the base station 102 may be an example of aspects of the base station 102 described with reference to FIG. 1.
  • the base station 102 may be equipped with antennas 934 and 935, and the UE 104 may be equipped with antennas 952 and 953.
  • the base station 102 may be able to send data over multiple communication links at the same time.
  • Each communication link may be called a “layer” and the “rank” of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station 102 transmits two “layers, ” the rank of the communication link between the base station 102 and the UE 104 is two.
  • a transmit (Tx) processor 920 may receive data from a data source. The transmit processor 920 may process the data. The transmit processor 920 may also generate control symbols or reference symbols.
  • a transmit MIMO processor 830 may perform spatial processing (e.g., precoding) on data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to the transmit modulator/demodulators 932 and 933. Each modulator/demodulator 932 through 933 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream.
  • Each modulator/demodulator 932 through 933 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a DL signal.
  • DL signals from modulator/demodulators 932 and 933 may be transmitted via the antennas 934 and 935, respectively.
  • the UE 104 may be an example of aspects of the UEs 104 described with reference to FIGS. 1 and 2.
  • the UE antennas 952 and 953 may receive the DL signals from the base station 102 and may provide the received signals to the modulator/demodulators 954 and 955, respectively.
  • Each modulator/demodulator 954 through 955 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each modulator/demodulator 954 through 955 may further process the input samples (e.g., for OFDM, etc. ) to obtain received symbols.
  • a MIMO detector 856 may obtain received symbols from the modulator/demodulators 954 and 955, perform MIMO detection on the received symbols, if applicable, and provide detected symbols.
  • a receive (Rx) processor 958 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE 104 to a data output, and provide decoded control information to a processor 980, or memory 982.
  • the processor 980 may in some cases execute stored instructions to instantiate a communicating component 242 (see e.g., FIGS. 1 and 2) .
  • a transmit processor 964 may receive and process data from a data source.
  • the transmit processor 964 may also generate reference symbols for a reference signal.
  • the symbols from the transmit processor 964 may be precoded by a transmit MIMO processor 966 if applicable, further processed by the modulator/demodulators 954 and 955 (e.g., for SC-FDMA, etc. ) , and be transmitted to the base station 102 in accordance with the communication parameters received from the base station 102.
  • the UL signals from the UE 104 may be received by the antennas 934 and 935, processed by the modulator/demodulators 932 and 933, detected by a MIMO detector 936 if applicable, and further processed by a receive processor 938.
  • the receive processor 938 may provide decoded data to a data output and to the processor 940 or memory 942.
  • the components of the UE 104 may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware.
  • Each of the noted modules may be a means for performing one or more functions related to operation of the MIMO communication system 900.
  • the components of the base station 102 may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware.
  • Each of the noted components may be a means for performing one or more functions related to operation of the MIMO communication system 900.
  • a method of communications by a first node comprises transmitting data on an uplink communication channel to a second node; determining a collision with a reception of data from a third node; and transmitting uplink control information (UCI) including a preemption indication representing a punctured uplink transmission of the data to the second node after transmission of the data, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources, and wherein the preemption indication comprises a value identifying one or more of the number of time or frequency resources within the indication cycle corresponding to the punctured uplink transmission.
  • UCI uplink control information
  • One or more of the above examples can further include further comprising identifying a preemption indication cycle configuration; and configuring the number of time or frequency resources of the preemption indication cycle based on the preemption indication cycle configuration.
  • One or more of the above examples can further include wherein the preemption indication cycle includes two or more non-contiguous time slots of a physical uplink shared channel (PUSCH) .
  • PUSCH physical uplink shared channel
  • One or more of the above examples can further include wherein transmitting the preemption indication includes multiplexing the UCI including the preemption indication with a scheduled physical uplink shared channel (PUSCH) transmission; and transmitting the multiplexed UCI including the preemption indication.
  • transmitting the preemption indication includes multiplexing the UCI including the preemption indication with a scheduled physical uplink shared channel (PUSCH) transmission; and transmitting the multiplexed UCI including the preemption indication.
  • PUSCH physical uplink shared channel
  • One or more of the above examples can further include wherein the scheduled PUSCH transmission is associated with a distinct preemption indication cycle that is after the preemption indication cycle to be indicated by the preemption indication.
  • One or more of the above examples can further include wherein multiplexing the UCI includes multiplexing with multiple PUSCHs associated with a distinct preemption indication cycle that is after the preemption indication cycle to be indicated by the preemption indication.
  • One or more of the above examples can further include wherein multiplexing the UCI includes multiplexing with multiple PUSCHs associated with multiple distinct preemption indication cycles that is after the preemption indication cycle to be indicated by the preemption indication.
  • One or more of the above examples can further include wherein the preemption indication is associated with a first preemption indication cycle, and further comprising determining whether the punctured uplink transmission occurs during the associated preemption indication cycle; and wherein transmitting the multiplexed preemption indication is in response to determining that the punctured uplink transmission does occur during the associated preemption indication cycle.
  • One or more of the above examples can further include wherein the UCI including the preemption indication multiplexed with the PUSCH is separately encoded with one or more other UCIs multiplexed with the PUSCH, and at least one resource of the UCI including the preemption indication is mapped starting from a last symbol of the PUSCH.
  • One or more of the above examples can further include further comprising encoding the UCI with at least one other UCI, wherein the UCI is multiplexed with a PUSCH including the preemption indication jointly, and wherein the at least one other UCI is multiplexed with the PUSCH and includes channel state information (CSI) feedback.
  • CSI channel state information
  • One or more of the above examples can further include wherein the UCI including the preemption indication is encoded within a Part-2 CSI feedback of the CSI feedback, the Part-2 CSI feedback includes a single bit indicating whether the UCI includes the preemption indication in the Part-2 CSI feedback.
  • One or more of the above examples can further include identifying at least one of an omission priority level associated with omission priority levels of multiple components of CSI feedbacks for the UCI including the preemption indication; and a CSI and preemption indication omission for jointly encoding the CSI and the preemption indication to be multiplexed with the PUSCH based at least in part on priority levels of the preemption indication and the multiple components of the CSI feedback.
  • One or more of the above examples can further include receiving an offset configuration and configuring/identifying an uplink resource quantity for the UCI including the preemption indication based on the offset configuration.
  • One or more of the above examples can further include wherein at least one of a number of bits forming the preemption indication or a preemption status of each bit of the number of bits is identified by the offset configuration.
  • One or more of the above examples can further include transmitting, on a physical uplink shared channel (PUSCH) , the data to the second node, wherein at least one symbol of the PUSCH is punctured as part of the transmission of the data on the PUSCH.
  • PUSCH physical uplink shared channel
  • One or more of the above examples can further include wherein the first node is an IAB node in an IAB system, the second node is a parent node in an IAB system.
  • a method of communications by a first node comprises determining that data is to be received on an uplink communication channel from a second node, receiving, from the second node, uplink control information (UCI) including a preemption indication representing a punctured uplink reception of the data; and receiving, the data from the second node, wherein at least one symbol is punctured as part of the transmission of the data, wherein the UCI is associated with a preemption indication cycle representing a number of time or frequency resources, and wherein the preemption indication comprises a value identifying one or more of the number of time or frequency resources within the indication cycle corresponding to the punctured uplink transmission.
  • UCI uplink control information
  • preemption indication comprises a value identifying one or more of the number of time or frequency resources within the indication cycle corresponding to the punctured uplink transmission.
  • One or more of the above examples can further include wherein the preemption indication cycle includes two or more non-contiguous time slots of a PUSCH.
  • One or more of the above examples can further include wherein the value of the preemption indication identifies at least one PUSCH.
  • One or more of the above examples can further include wherein receiving the preemption indication includes receiving a multiplexed UCI including the preemption indication.
  • One or more of the above examples can further include wherein the multiplexed UCI is multiplexed with multiple PUSCHs associated with a distinct preemption indication cycle that is after the preemption indication cycle to be indicated by the preemption indication.
  • One or more of the above examples can further include wherein the multiplexed UCI is multiplexed with multiple PUSCHs associated with multiple distinct preemption indication cycles that is after the preemption indication cycle to be indicated by the preemption indication.
  • One or more of the above examples can further include wherein the UCI including the preemption indication multiplexed with the PUSCH is separately encoded with one or more other UCIs multiplexed with the PUSCH, and at least one resource of the UCI including the preemption indication is mapped starting from a last symbol of the PUSCH.
  • One or more of the above examples can further include wherein the UCI multiplexed with a PUSCH including the preemption indication is separately or jointly encoded with at least one other UCI multiplexed with the PUSCH and including channel state information (CSI) feedback.
  • CSI channel state information
  • One or more of the above examples can further include wherein the UCI including the preemption indication is encoded within a Part-2 CSI feedback of the CSI feedback, the Part-2 CSI feedback includes a single bit indicating whether the UCI includes the preemption indication in the Part-2 CSI feedback.
  • One or more of the above examples can further include wherein the multiplexed UCI is received on a last symbol of the PUSCH transmission.
  • One or more of the above examples can further include transmitting an offset configuration to the second node, and configuring/identifying an uplink resource quantity for the UCI including the preemption indication based on the offset configuration.
  • One or more of the above examples can further include wherein at least one of a number of bits forming the preemption indication or a preemption status of each bit of the number of bits is identified by the a configured uplink resource quantity.
  • One or more of the above examples can further include receiving, on a physical uplink shared channel (PUSCH) , the data from the second node, wherein at least one symbol of the PUSCH is punctured as part of the transmission of the data on the PUSCH.
  • PUSCH physical uplink shared channel
  • One or more of the above examples can further include wherein the second node is an IAB node in an IAB system, the first node is a parent node in an IAB system.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.
  • a specially-programmed device such as but not limited to a processor, a digital signal processor (DSP) , an ASIC, a FPGA or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein.
  • DSP digital signal processor
  • a specially-programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a specially-programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a specially programmed processor, hardware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Moreover, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.
  • X employs A or B is intended to mean any of the natural inclusive permutations. That is, for example the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B.
  • “or” as used in a list of items prefaced by “at least one of” indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (A and B and C) .
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • Disk and disc include 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 are also included within the scope of computer-readable media.

Landscapes

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

Abstract

Des aspects de la présente invention concernent une indication de préemption de liaison montante basée sur des informations de commande de liaison montante (UCI). Dans un exemple, un premier nœud tel qu'un nœud d'accès et de raccordement intégré (IAB) peut déterminer que des données ayant un niveau de priorité doivent être transmises sur un canal de communication de liaison montante à un deuxième nœud. Le premier nœud transmet des UCI contenant une indication de préemption qui représente une transmission de liaison montante discontinue des données au deuxième nœud après la transmission des données. Dans un autre exemple, un premier nœud tel qu'un nœud parent dans un système IAB peut recevoir, en provenance d'un nœud IAB, des UCI comprenant une indication de préemption représentant une réception de liaison montante discontinue des données. Dans les deux exemples, les UCI peuvent être associées à un cycle d'indication de préemption représentant un certain nombre de ressources en temps ou en fréquence.
PCT/CN2019/102257 2019-08-23 2019-08-23 Techniques pour des transmissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci) WO2021035392A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/102257 WO2021035392A1 (fr) 2019-08-23 2019-08-23 Techniques pour des transmissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci)
PCT/CN2020/110654 WO2021036961A1 (fr) 2019-08-23 2020-08-22 Techniques pour des émissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/102257 WO2021035392A1 (fr) 2019-08-23 2019-08-23 Techniques pour des transmissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci)

Publications (1)

Publication Number Publication Date
WO2021035392A1 true WO2021035392A1 (fr) 2021-03-04

Family

ID=74683708

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2019/102257 WO2021035392A1 (fr) 2019-08-23 2019-08-23 Techniques pour des transmissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci)
PCT/CN2020/110654 WO2021036961A1 (fr) 2019-08-23 2020-08-22 Techniques pour des émissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci)

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/110654 WO2021036961A1 (fr) 2019-08-23 2020-08-22 Techniques pour des émissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci)

Country Status (1)

Country Link
WO (2) WO2021035392A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023177527A1 (fr) * 2022-03-15 2023-09-21 Qualcomm Incorporated Techniques de transmission d'une indication d'annulation

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180035459A1 (en) * 2016-07-29 2018-02-01 Huawei Technologies Co., Ltd. Coexistence of Grant-Based and Grant-Free Uplink Transmissions in a Channel
WO2018158926A1 (fr) * 2017-03-02 2018-09-07 株式会社Ｎｔｔドコモ Terminal utilisateur et procédé de communication sans fil
US20180270022A1 (en) * 2017-03-16 2018-09-20 Qualcomm Incorporated Multi-harq methods and apparatus for codeblock group based transmissions
WO2018175420A1 (fr) * 2017-03-20 2018-09-27 Convida Wireless, Llc Planification et commande dans une nouvelle radio en ayant recours à une indication de pré-emption
WO2018204730A1 (fr) * 2017-05-03 2018-11-08 Intel IP Corporation Traitement de collision destiné à une transmission basée sur un créneau et basée sur un mini-créneau
US20190098612A1 (en) * 2017-09-28 2019-03-28 Alireza Babaei Pre-Emption Indication In A Wireless Device
WO2019160969A1 (fr) * 2018-02-14 2019-08-22 Qualcomm Incorporated Indications de préemption de liaison montante et de liaison descendante

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3479616B1 (fr) * 2016-07-29 2021-05-05 Huawei Technologies Co., Ltd. Coexistence de transmissions de liaison montante avec octroi et sans octroi dans un canal
KR102404956B1 (ko) * 2017-01-04 2022-06-07 아이디에이씨 홀딩스, 인크. 무선 시스템들에서의 수신기 피드백

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180035459A1 (en) * 2016-07-29 2018-02-01 Huawei Technologies Co., Ltd. Coexistence of Grant-Based and Grant-Free Uplink Transmissions in a Channel
WO2018158926A1 (fr) * 2017-03-02 2018-09-07 株式会社Ｎｔｔドコモ Terminal utilisateur et procédé de communication sans fil
US20180270022A1 (en) * 2017-03-16 2018-09-20 Qualcomm Incorporated Multi-harq methods and apparatus for codeblock group based transmissions
WO2018175420A1 (fr) * 2017-03-20 2018-09-27 Convida Wireless, Llc Planification et commande dans une nouvelle radio en ayant recours à une indication de pré-emption
WO2018204730A1 (fr) * 2017-05-03 2018-11-08 Intel IP Corporation Traitement de collision destiné à une transmission basée sur un créneau et basée sur un mini-créneau
US20190098612A1 (en) * 2017-09-28 2019-03-28 Alireza Babaei Pre-Emption Indication In A Wireless Device
WO2019160969A1 (fr) * 2018-02-14 2019-08-22 Qualcomm Incorporated Indications de préemption de liaison montante et de liaison descendante

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Views on eURLLC WI", 3GPP DRAFT; RP-190221 VIEWS ON EURLLC WI, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Shenzhen, China; 20190318 - 20190321, 11 March 2019 (2019-03-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051690067 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023177527A1 (fr) * 2022-03-15 2023-09-21 Qualcomm Incorporated Techniques de transmission d'une indication d'annulation

Also Published As

Publication number Publication date
WO2021036961A1 (fr) 2021-03-04

Similar Documents

Publication Publication Date Title
US11871444B2 (en) Techniques for prioritizing transmission of types of wireless communications
US11791943B2 (en) Techniques for retransmissions in wireless communication systems
US11357028B2 (en) Techniques for beam sweep based semi-persistent scheduling/configured grant activation
WO2021016980A1 (fr) Techniques d'activation d'états d'indication de configuration de transmission dans des communications sans fil
US20220408417A1 (en) Techniques for determining resources for transmitting wireless communications
US11553482B2 (en) Techniques for determining resources for repetitions in wireless communications
US11737057B2 (en) Techniques for updating preempted or cancelled resources in wireless communications
US11606811B2 (en) Techniques for determining resources for communicating over an acquired channel
US20220369150A1 (en) Techniques for data rate sharing for uplink and sidelink wireless communications
WO2021036961A1 (fr) Techniques pour des émissions d'indication de préemption de liaison montante basée sur des informations de commande de liaison montante (uci)
US20230379915A1 (en) Uplink control information (uci) multiplexing for multi-slot physical uplink shared channel (pusch) with transport block size (tbs) scaling
WO2021223224A1 (fr) Techniques de résolution de transmissions d'informations en retour en désordre
US20220338242A1 (en) Techniques for determining feedback timing capability in sidelink wireless communications
US11626943B2 (en) Techniques for on-demand soft ACK/NACK in a wireless communication system
US20220322391A1 (en) Techniques for pucch repetition based on pdsch repetition
US11930498B2 (en) Techniques for scheduling sidelink communications in multiple time periods
WO2022213046A1 (fr) Techniques pour répétition de pucch basées sur une répétition de pdcch

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

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

Country of ref document: EP

Kind code of ref document: A1