Identifying resources for transmitting a first uplink channel

By identifying and utilizing uplink resource sets in LTE PUCCH and transmitting short-duration uplink channels, the problem of transmission time mismatch in LTE PUCCH in 5G is solved, achieving low-latency communication and efficient resource utilization.

CN114826499BActive Publication Date: 2024-11-19MOTOROLA MOBILITY LLC
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
CN202210496752.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2016-11-04
Filing Date
2017-11-06
Publication Date
2024-11-19
Estimated Expiration
2037-11-06

AI Technical Summary

Technical Problem

The long transmission time of LTE PUCCH is not suitable for achieving the short HARQ round-trip time of a single time slot in fifth-generation radio access, resulting in high GP overhead and making it difficult to meet the requirements of low-latency communication.

Method used

By receiving downlink scheduling assignment messages, identifying the uplink resource set, determining the first uplink resource within the time slot, sending a short-duration uplink channel, such as HARQ-ACK feedback, and using information such as frequency resource units and control channel element indexes to determine resources, short PUCCH transmission is achieved.

Benefits of technology

It reduces protection period overhead, supports low-latency communication, improves resource utilization efficiency, and adapts to communication needs with different latency requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114826499B_ABST
    Figure CN114826499B_ABST
Patent Text Reader

Abstract

The present invention relates to identifying resources for sending a first uplink channel. To send an uplink channel, a device includes a processor and a transceiver that communicates with a user equipment ("UE") in a mobile communication network. The processor receives a first uplink channel from the UE on a first uplink resource and a second uplink channel from the UE on a second uplink resource, wherein the first uplink resource and the second uplink resource overlap at least partially in time, and wherein the first uplink channel is used for a first transmission and reception point ("TRP") and the second uplink channel is used for a second TRP, wherein the first TRP is different from the second TRP.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of an application which entered the Chinese national phase on April 30, 2019, with PCT application number PCT / US2017 / 060241, international application date November 6, 2017, Chinese application number 201780067831.2, and invention name “Identifying resources for sending a first uplink channel”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 418,010, entitled “Methods to multiplex physical channel and signals for flexible radio communication,” filed on November 4, 2016 by Hyejung Jung, Ravikiran Nory and Vijay Nangia, which is incorporated herein by reference, and claims priority to U.S. Patent Application No. 15 / 804,947, entitled “Identifying a Resource for Transmitting a First Uplink Channel,” filed on November 6, 2017 by Hyejung Jung, Ravikiran Nory and Vijay Nangia. Technical Field

[0004] The subject matter disclosed herein relates generally to wireless communications, and more particularly, to transmitting short duration uplink channels, such as PUCCH or PUSCH. Background Art

[0005] The following abbreviations and acronyms are defined herein, at least some of which are referred to in the following description.3rd Generation Partnership Project (“3GPP”), Access and Mobility Management Function (“AMF”), Carrier Aggregation (“CA”), Clear Channel Assessment (“CCA”), Control Channel Element (“CCE”), Channel State Information (“CSI”), Common Search Space (“CSS”), Downlink Control Information (“DCI”), Downlink (“DL”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), European Telecommunications Standards Institute (“ETSI”), Frame-based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”), Frequency Resource Unit (“H ARQ”), Guard Period (“GP”), Hybrid Automatic Repeat Request (“HARQ”), Internet of Things (“IoT”), Key Performance Indicator (“KPI”), License Assisted Access (“LAA”), Load Based Equipment (“LBE”), Listen Before Talk (“LBT”), Long Term Evolution (“LTE”), LTA-Advanced (“LTE-A”), Medium Access Control (“MAC”), Multiple Access (“MA”), Modulation and Coding Scheme (“MCS”), Machine Type Communication (“MTC”), Massive MTC (“mMTC”), Multiple Input Multiple Output (“MIMO”), Multipath TCP (“MPTCP”), Multi-User Shared Access (“MUSA”), Narrowband (“NB”), Network Function (“NF”), Next Generation Node B (“gNB”), Policy Control & Charging (“PCC”), Policy Control Function (“PCF”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Resource Block (“RB”), Radio Resource Control (“RRC”), Receive (“RX”), Switching / Split Function (“SSF”), Scheduling Request (“SR”), Session Management Function (“SMF”), System Information Block (“SIB”), Transport Block (“TB”), Transport Block Size (“TBS”), Transmission Control Protocol (“TCP”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Time Resource Unit ( “TRU”), transmission and reception point (“TRP”), transmission (“TX”), uplink control information (“UCI”), user datagram protocol (“UDP”), user entity / equipment (mobile terminal) (“UE”), uplink (“UL”), physical downlink control channel (“PDCCH”), physical downlink shared channel (“PDSCH”), physical uplink control channel (“PUCCH”), physical uplink shared channel (“PUSCH”), physical resource block (“PRB”), universal mobile telecommunications system (“UMTS”), ultra-reliable and low-latency communications (“URLLC”), and world-wide interoperability for microwave access (“WiMAX”).

[0006] In an LTE mobile communication network, a user equipment ("UE") sends uplink control messages on a physical uplink control channel ("PUCCH"). The PUCCH carries uplink control information ("UCI") - such as HARQ-ACK feedback, scheduling requests ("SR"), and channel state information ("CSI"), and typically spans the entire subframe duration (i.e., 1 millisecond or 14 OFDM symbol duration).

[0007] The long transmission time of LTE PUCCH is not suitable for achieving HARQ round trip time (RTT) as short as 1 time slot period (e.g., 1 ms or 0.5 ms) in fifth generation wireless access. In addition, for low latency communication, DL to UL switching can occur within each time slot (e.g., 7 or 14 OFDM symbols). Therefore, the guard period ("GP") based on the maximum expected propagation delay in the cell will result in very high GP overhead. Considering that the minimum GP in LTE TDD is one OFDM symbol period, the minimum GP overhead with a 1 millisecond switching period is 14% or 7%, that is, 1 symbol GP in every 7 or 14 symbols. Summary of the invention

[0008] A method for transmitting a short duration uplink channel is disclosed. The device and system also perform the functions of the method. In some embodiments, a method for transmitting a short duration uplink channel includes: receiving a downlink scheduling assignment message that allocates resources for data reception of a transport block ("TB"); and identifying a set of uplink resources allocated for a first uplink channel within a time slot. In addition, the method includes: determining a first uplink resource from the uplink resource set. Here, the first uplink resource is determined based on one of the following: a resource block ("RB") index of a first assigned frequency resource unit ("FRU") of the TB, a lowest control channel element ("CCE") index of the downlink scheduling assignment message, a hybrid automatic repeat request acknowledgment ("HARQ-ACK") feedback delay, and a HARQ-ACK resource index / offset indicated in the downlink scheduling assignment message. The method includes: sending a first uplink channel that transmits at least HARQ-ACK feedback for the TB on a first uplink resource, wherein the first uplink channel includes one or two symbols in the time slot. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more particular description of the embodiments briefly described above will be presented with reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0010] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for transmitting a short duration uplink channel;

[0011] Figure 2 is a block diagram illustrating one embodiment of a network architecture for transmitting short duration uplink channels;

[0012] Figure 3 is a block diagram illustrating one embodiment of a user equipment sending an uplink control message to multiple transmission reception points ("TRPs");

[0013] Figure 4 is a schematic block diagram illustrating one embodiment of a user equipment apparatus for transmitting a short duration uplink channel;

[0014] Figure 5 is a schematic block diagram illustrating one embodiment of a base station apparatus for transmitting a short duration uplink channel;

[0015] Figure 6 is a block diagram illustrating one embodiment of communication between a gNB and a UE, wherein the UE transmits a short duration uplink channel;

[0016] Fig. 7A is a block diagram illustrating an embodiment of a reference signal time division multiplexed with a corresponding data channel or control channel;

[0017] Figure 7B is a block diagram illustrating further embodiments of reference signals time-division multiplexed with corresponding data channels or control channels;

[0018] Figure 7C is a block diagram illustrating an embodiment of a mix of frequency division multiplexing and time division multiplexing of reference signals with corresponding data channels or control channels;

[0019] Fig.7D is a block diagram illustrating further embodiments of a mix of frequency division multiplexed and time division multiplexed reference signals with corresponding data channels or control channels;

[0020] Figure 8 is a schematic diagram illustrating multi-slot scheduling between a gNB and a UE;

[0021] Fig. 9A is a schematic diagram illustrating uplink control message timing for multi-slot scheduling between a gNB and a UE, wherein the UE transmits a short duration uplink channel;

[0022] Fig. 9Bis a schematic diagram illustrating uplink control message collision for multi-slot scheduling between a gNB and a UE, wherein the UE transmits a short duration uplink channel; and

[0023] Fig.10 is a flow chart illustrating one embodiment of a method for transmitting a short duration uplink channel. DETAILED DESCRIPTION

[0024] As those skilled in the art will appreciate, various aspects of the embodiments may be embodied as systems, devices, methods or program products. Therefore, the embodiments may take the form of complete hardware embodiments, complete software embodiments (including firmware, resident software, microcode, etc.) or embodiments combining software and hardware aspects.

[0025] For example, the disclosed embodiments may be implemented as hardware circuits including custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions.

[0026] In addition, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as code). The storage device may be a tangible storage device, a non-transitory storage device, and / or a non-transmitting storage device. The storage device may not contain signals. In some embodiments, the storage device only uses signals to access the code.

[0027] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, an infrared storage device, a holographic storage device, a micromechanical storage device, or a semiconductor system, device, or apparatus, or any suitable combination of the foregoing.

[0028] More specific examples of storage devices (a non-comprehensive list) would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0029] Throughout this specification, references to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, throughout this specification, the phrases "in one embodiment," "in an embodiment," and similar language may, but do not necessarily, refer to the same embodiment, but rather to "one or more but not all embodiments," unless otherwise expressly specified. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise expressly specified. An enumerated list of items does not imply that any or all of the items are mutually exclusive, unless otherwise expressly specified. The terms "a," "an," and "the" also refer to "one or more," unless otherwise expressly specified.

[0030] In addition, the features, structures or characteristics of the description of the embodiments can be combined in any suitable manner. In the following description, a large number of specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other examples, well-known structures, materials or operations are not shown or described in detail to avoid blurring the aspects of the embodiments.

[0031] The various aspects of the embodiment are described below with reference to the schematic flow chart and / or schematic block diagram of the method, device, system and program product according to the embodiment.It is to be understood that each frame in the schematic flow chart and / or schematic block diagram and the combination of frames in the schematic flow chart and / or schematic block diagram can be implemented by code.The code can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instruction is created when executed via the processor of a computer or other programmable data processing device for implementing the means of the function / action specified in the schematic flow chart and / or one or more schematic block diagram frames.

[0032] The code may also be stored in a storage device that can direct a computer, other programmable data processing device, or other apparatus to operate in a specific manner, so that the instructions stored in the storage device produce an article of manufacture including instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0033] The code may also be loaded onto a computer or other programmable data processing device or other apparatus so that a series of operating steps are performed on the computer, other programmable device or other apparatus to produce a computer-implemented process, so that the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0034] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functions and operations of possible implementation methods of the devices, systems, methods and program products according to various embodiments. In this regard, each box in the schematic flow charts and / or schematic block diagrams may represent a code module, a code segment, or a part of a code, which includes one or more code executable instructions for implementing (one or more) specified logical functions.

[0035] It should also be noted that in some alternative implementations, the functions mentioned in the blocks may not occur in the order mentioned in the drawings. For example, two blocks shown in succession may actually be performed substantially simultaneously, or the blocks may sometimes be performed in reverse order, depending on the functions involved. It is contemplated that other steps and methods are equivalent in function, logic, or effect to one or more blocks or portions thereof in the illustrated drawings.

[0036] The description of an element in each figure may refer to the element in the figure in which the description is made. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0037] In wireless communication systems, a time slot may be defined as a time unit consisting of one or more symbols, for example, orthogonal frequency division multiplexing ("OFDM") symbols or discrete Fourier transform spread OFDM ("DFT-S-OFDM") symbols. A transmission time interval ("TTI") refers to the duration during which a UE may receive / send a transport block ("TB") from a higher layer. In fifth generation ("5G") radio access technologies ("RATs"), there may be a need to support multiple TTIs or concatenated slots within a time slot, flexible timing relationships between scheduling grant signaling and actual transmission / reception, and flexible hybrid automatic repeat request acknowledgment ("HARQ") feedback timing, taking into account various service requirements (e.g., latency, reliability, data rate), UE types, deployment scenarios (e.g., unlicensed bands), and energy-efficient UE operations (e.g., operating bandwidth adaptation), among others.

[0038] For low-latency operation, a user equipment ("UE") may perform downlink ("DL") reception and corresponding HARQ-ACK feedback transmission, or reception of an uplink ("UL") scheduling grant and corresponding UL transmission (so-called self-contained operation) within the slot duration. To achieve this in a time division duplex ("TDD") system, a low-latency slot (also referred to as a "self-contained" slot) consisting of a DL transmission region, a guard region, and a UL transmission region may be defined. In addition, for both frequency division duplex ("FDD") and TDD, a DL physical control channel (e.g., PDCCH) may be placed in the first part of the slot, and an uplink physical control channel (e.g., PUCCH) may be placed in the second part of the slot.

[0039] Disclosed herein are methods for achieving low-latency communications with low guard period ("GP") overhead, methods for multiplexing physical channels for simultaneously supporting communications with various latency requirements (e.g., mixed low-latency traffic and normal traffic), and methods for using both short physical uplink control channels ("PUCCH") and long PUCCH. As used herein, a "short" PUCCH refers to a PUCCH that spans one or two OFDM symbols in a time slot. In contrast, a "long" PUCCH refers to a PUCCH that spans more than two symbols in a time slot. Typically, a long PUCCH spans an entire time slot (just like the LTE PUCCH); however, a long PUCCH can be shorter than an entire time slot, for example, to allow narrowband retuning and / or transmission of a sounding reference signal ("SRS") in a band-limited UE. The UE can multiplex short and long PUCCHs based on the UE beamforming architecture / hardware capabilities and deployment scenarios.

[0040] Figure 1A wireless communication system 100 for transmitting a short duration uplink channel according to an embodiment of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, an access network 120 including at least one base unit 110, a wireless communication link 115, and a mobile core network 130. Even in Figure 1 Although a specific number of remote units 105, access networks 120, base units 110, wireless communication links 115, and mobile core networks 130 are depicted in the wireless communication system 100, those skilled in the art will also recognize that any number of remote units 105, access networks 120, base units 110, wireless communication links 115, and mobile core networks 130 may be included in the wireless communication system 100. In another embodiment, the access network 120 includes one or more WLANs (e.g., Wi-Fi TM ) access point.

[0041] In one embodiment, the wireless communication system 100 complies with the 5G system specified in the 3GPP specification (e.g., "5GNR"). However, more generally, the wireless communication system 100 may implement some other open or proprietary communication network, such as LTE or WiMAX, among other networks. The present disclosure is not intended to be limited to implementations of any particular wireless communication system architecture or protocol.

[0042] In one embodiment, the remote unit 105 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a smart home appliance (e.g., a home appliance connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 105 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or by other terminology used in the art. The remote unit 105 can communicate directly with one or more base station units 110 via uplink ("UL") and downlink ("DL") communication signals. In addition, the UL and DL communication signals can be carried by the wireless communication link 115.

[0043] The base units 110 may be distributed over a geographic area. In some embodiments, the base units 110 may also be referred to as access terminals, access points, base stations, base stations, node Bs, eNBs, gNBs, home node Bs, relay nodes, devices, or by any other terminology used in the art. The base units 110 are typically part of a radio access network ("RAN"), for example, an access network 120, which may include one or more controllers communicatively coupled to one or more corresponding base units 110. These and other elements of the radio access network are not shown, but are generally familiar to those of ordinary skill in the art. The base units 110 are connected to the mobile core network 130 via the access network 120.

[0044] The base unit 110 can serve several remote units 105 within a service area, such as a cell or a cell sector, via a wireless communication link 115. The base unit 110 can communicate directly with one or more remote units 105 via communication signals. Typically, the base unit 110 sends downlink ("DL") communication signals in the time domain, frequency domain, and / or spatial domain to serve the remote units 105. In addition, the DL communication signals can be carried by the wireless communication link 115. The wireless communication link 115 can be any suitable carrier in the licensed or unlicensed radio spectrum. The wireless communication link 115 facilitates communication between one or more remote units 105 and / or one or more base units 110.

[0045] In one embodiment, mobile core network 130 is a 5G core ("5GC") or an evolved packet core ("EPC"), which can be coupled to other data networks 125, such as the Internet and private data networks and other data networks. Each mobile core network 130 belongs to a single public land mobile network ("PLMN"). The present disclosure is not intended to be limited to implementation of any particular wireless communication system architecture or protocol.

[0046] The mobile core network 130 includes several network functions ("NFs"). As depicted, the mobile core network 130 includes an access and mobility management function ("AMF") 135, a session management function ("SMF") 140, and a user plane function ("UPF") 145. Figure 1 A specific number of AMF 135, SMF 140, and UPF 145 are depicted in the figure, but technicians in this field will recognize that any number and type of network functions may be included in the mobile core network 130.

[0047] AMF 135 provides services such as UE registration, UE connection management, and UE mobility management. SMF 140 manages data sessions, such as PDU sessions, for remote unit 105. UPF 145 provides user plane (e.g., data) services to remote unit 105. The data connection between remote unit 105 and data network 125 is managed by UPF 145.

[0048] The RAN 120 supports two types of UL physical control channels (e.g., PUCCH): a short control channel (e.g., short PUCCH) placed in the latter part of the time slot (e.g., the last or two symbol periods of the time slot), and a long control channel (e.g., long PUCCH) that spans the time slot. In some embodiments, the long control channel may occupy less than the entire time slot, but more than half of the time slot duration. Similarly, a short physical uplink data channel (e.g., short PUSCH) may be frequency-division multiplexed with the short PUCCH in (one or more) the same symbols. The short PUCCH frequency-division multiplexed with the short PUSCH is referred to herein as "short PUCCH / PUSCH". In addition, a long physical data channel (e.g., long PUSCH) that spans a large portion of the time slot or the time slot duration (e.g., more than two symbols) may be defined.

[0049] A short control channel (e.g., a short PUCCH) can be used to transmit a scheduling request ("SR"), a small number of HARQ-ACK bits (e.g., up to 8 bits of HARQ-ACK feedback), and limited CSI reports for non-power-constrained remote units 105 (e.g., an indication of a change in the best DL beam). In contrast, a long control channel (e.g., a long PUCCH) is used to transmit a complete CSI report (e.g., interference measurements and reports with multiple interference hypotheses). Long control channels are also used to send a large number of HARQ-ACK bits, for example, through slot aggregation and / or carrier aggregation. In addition, long control channels are used by power-constrained remote units 105.

[0050] In some embodiments, the remote unit 105 always uses an OFDM waveform to send a short control channel (e.g., a short PUCCH or a short PUCCH / PUSCH). In some embodiments, a long PUCCH (or long PUSCH) is sent using an OFDM waveform or a DFT-S-OFDM waveform. Here, the remote unit 105 can be configured by the RAN 120 to use an OFDM waveform or a DFT-S-OFDM waveform when sending a long PUCCH or a long PUSCH, for example, selecting the waveform based on a cell or TRP measurement, such as a reference signal received power ("RSRP"). In other embodiments, the RAN 120 dynamically indicates to the remote unit 105 whether to use an OFDM waveform or a DFT-S-OFDM waveform for a long PUCCH (or long PUSCH). Here, the dynamic indication can be an explicit parameter or element in the DCI, or the dynamic indication can be implicitly signaled to the remote unit 105. In addition, as described below with reference to Figure 3 As discussed, the waveform used for long PUCCH / PUSCH may depend on the target TRP.

[0051] For resource assignment of a short control channel (e.g., short PUCCH), the RAN 120 may allocate a set of subcarriers (or a set of resource blocks) as a short PUCCH region. In addition, the RAN 120 may dynamically indicate (e.g., with each DCI indication) the allocated set to the remote unit 105 in the DCI, wherein the remote unit 105 determines the specific resources for the short PUCCH via implicit signaling. This hybrid approach for determining short PUCCH resources may reduce DCI signaling overhead and may also provide flexibility in scheduling long PUCCH / PUSCH. In some embodiments, the DCI may indicate specific resources for the PUCCH from a pre-configured set of resources.

[0052] In certain embodiments, the remote unit 105 receives a downlink resource / scheduling assignment message that assigns a plurality of time resource units ("TRUs") and a plurality of frequency resource units ("FRUs") for data reception. The remote unit 105 then determines a set of transport blocks (TBs) corresponding to the received resource assignment and determines an end time resource unit corresponding to each TB in the set of TBs. In one embodiment, the received resource assignment corresponds to a single large TB. In another embodiment, the received resource assignment corresponds to a plurality of smaller TBs.

[0053] The remote unit 105 sends HARQ-ACK feedback corresponding to each TB in the TB set. In some embodiments, the remote unit 105 determines the uplink resources for the transmission of HARQ-ACK based at least on the end TRU of the corresponding TB and the FRU of the corresponding TB. In one embodiment, the uplink resources for the transmission of HARQ-ACK, for example, (one or more) uplink PRBs and / or (one or more) sequences, are based on the index of the first assigned FRU of the corresponding TB. In some embodiments, the FRU is a resource block including 12 subcarriers. In addition, the TRU can be a time slot including an integer number (one or more) of OFDM symbols.

[0054] In some embodiments, the remote unit 105 receives a higher layer message configuring the HARQ-ACK resources, and further receives an indication in a DL scheduling / assignment message, wherein the remote unit 105 determines the resources for transmission of the HARQ-ACK based on the indication and the higher layer message. For example, the indication may signal the remote unit 105 to use the resources identified by the TRU and FRU based on the corresponding TB. As another example, the indication may signal the remote unit 105 to use specific resources in the configured HARQ-ACK resources. In yet another example, the indication may be an offset, and the remote unit 105 may be signaled to use resources that are an indicated offset from the resources identified by the TRU and FRU based on the corresponding TB.

[0055] In some embodiments, the RAN 120 operates with "paired spectrum," where one carrier is dedicated to the downlink and the other carrier is dedicated to the uplink. In other embodiments, the RAN 120 operates with unpaired spectrum, such that there are no frequencies (e.g., subcarriers) dedicated to the downlink and frequencies / subcarriers dedicated to the uplink. In such embodiments, the RAN 120 may employ the entire frequency range of the carrier for downlink communications during a first time period, and then employ the entire frequency range of the carrier for uplink communications during a second time period. In addition, the downlink time periods and the uplink time periods are separated by guard periods, i.e., times when no communications occur.

[0056] In some embodiments, for cells with unpaired spectrum, the RAN 120 sets a guard period that is shorter than the symbol duration of the data channel. Doing so allows the RAN 120 to use the remainder of the symbol duration of the data channel to send / receive the demodulation reference signal ("DM RS") of the data channel. In order to send / receive the DM RS of the data channel with a shorter than normal duration, the DM RS uses a subcarrier spacing that is larger than the subcarrier spacing of the data channel. For example, if the normal subcarrier spacing of the data channel is 15kHz, a subcarrier spacing of 30kHz can be used to send the DM RS within half the normal symbol length. In addition, the DM RS can be time-division multiplexed with the data channel or with the control channel. Here, the data / control channel can support both OFDM waveforms and DFT-S-OFDM waveforms in the uplink. Refer to the following FIG. 7A to FIG. 7D Time division multiplexing of DM RS and data / control channels is described in more detail.

[0057] Figure 2 A network architecture 200 for transmitting a short duration uplink channel according to an embodiment of the present disclosure is depicted. The network architecture 200 may be a simplified embodiment of the wireless communication system 100. As depicted, the network architecture 200 includes a UE 205 in communication with a gNB 210. The UE 205 may be an embodiment of the remote unit 105 described above, and the gNB 210 may be an embodiment of the base unit 110 described above.

[0058] As depicted, gNB 210 sends various control and / or data signals to UE 205 on the downlink (see box 215). UE 205 determines to send a short PUCCH or a short PUCCH / PUSCH, and identifies uplink resources (see box 220). UE 205 then sends a short PUCCH (or a short PUCCH multiplexed with a short PUSCH, e.g., a short PUCCH / PUSCH) on the identified uplink resources. As described above, gNB 210 can assign uplink resources to UE 205 for sending the short PUCCH or PUCCH / PUSCH. In one embodiment, gNB 210 assigns uplink resources to UE 205 when sending a downlink resource assignment message.

[0059] The downlink control channel overhead can be reduced by UE 205 using implicit signaling to identify the time slot and (one or more) resource blocks for short PUCCH or short PUCCH / PUSCH. In this embodiment, when a downlink resource assignment is given, the remote unit 105 can determine the transport block (TB) corresponding to the resource assignment. The remote unit then determines the end time-resource unit (e.g., symbol) corresponding to each TB. The remote unit 105 sends its HARQ-ACK feedback at a time based at least on the end time-resource unit ("TRU") of the TB. In one embodiment, the UE 205 selects an uplink resource for sending HARQ-ACK feedback based on the frequency-resource unit ("FRU") corresponding to the TB, for example, an uplink PRB and / or (one or more) sequence. In another embodiment, the UE 205 selects an uplink resource for sending HARQ-ACK feedback based on an indicator in the downlink resource assignment message.

[0060] In one embodiment, the gNB 210 configures the UE 205 with a set of ARQ-ACK resources for use with low latency communications (e.g., for sending HARQ-ACK feedback on a short PUCCH). For example, the UE 205 may be configured via RRC signaling with the set of HARQ-ACK resources. Thereafter, the UE 205 selects a particular HARQ-ACK resource selected from one of the multiple HARQ-ACK resources based on the criteria described above, referred to as an "implicit determination." In some embodiments, the gNB 210 may override the implicit determination of the HARQ-ACK resource by, for example, sending an indication of the particular HARQ-ACK resource to be used in a DCI.

[0061] For example, the gNB 210 may include a two-bit information element or field in the DCI, wherein a value of '00' indicates that the UE 205 will use resources indicated by the implicit determination, a value of '01' indicates that the UE 205 will use resources that are a first offset from the implicitly determined resources, a value of '10' indicates that the UE 205 will use resources that are a second offset from the implicitly determined resources, and a value of '11' indicates that the UE 205 will use resources that are a third offset from the implicitly determined resources. In other embodiments, as described below with reference to Fig. 9B As discussed, the values ​​'01', '10', and '11' may point to specific HARQ-ACK resources.

[0062] In some embodiments, the mobile communication network may dynamically determine and signal the radio resources (e.g., subcarrier allocation) for the short PUCCH / PUSCH in time slot n, taking into account other pre-scheduled long PUSCH / PUCCH transmissions (e.g., UL data or full / periodic CSI reports) in time slot n. Dynamically adjusting the short PUCCH / PUSCH resources allows flexible scheduling of long PUSCH / PUCCH and efficient resource utilization. In the case where there is no DL region in time slot n - for example, a UL-only time slot for unpaired spectrum, the subcarrier allocation for the short PUCCH / PUSCH in time slot n may be indicated in time slot nk including the DL region before time slot n but closest to time slot n.

[0063] In one embodiment, both short PUCCH resources and short PUSCH resources for time slot n may be dynamically signaled via DCI in time slot n (or in time slot nk if there is no DL region in time slot n). If a DL scheduling DCI is sent in time slot n or time slot nk, the short PUCCH resources for HARQ-ACK feedback may be indicated in the DCI that schedules the corresponding DL data channel.

[0064] In some embodiments, the UE 205 transmits in a first OFDM symbol using a first transmission direction. Here, the first OFDM symbol corresponds to a first subcarrier spacing value. The UE 205 also transmits in a second transmission direction using a second OFDM symbol. Here, the second OFDM symbol corresponds to a second subcarrier spacing value. In addition, the second OFDM symbol occurs immediately after a transmission gap (e.g., a guard period) between the first and second OFDM symbols.

[0065] In addition, UE 205 transmits using the second transmission direction in a third OFDM symbol. Here, the third OFDM symbol corresponds to the first subcarrier spacing value. In addition, the third OFDM symbol is immediately after the second OFDM symbol. In some embodiments, the second subcarrier spacing value is an integer multiple (e.g., twice) of the first subcarrier spacing value.

[0066] In one embodiment, the first transmission direction is downlink and the second transmission direction is uplink. In addition, the second OFDM symbol may contain a reference signal and the third OFDM symbol may contain data. In such an embodiment, the UE 205 receives, for example, downlink data in the first OFDM symbol, switches to uplink communication (e.g., during a gap period), sends a reference signal in the second OFDM symbol, and sends, for example, UCI in the third OFDM symbol.

[0067] In another embodiment, the first transmission direction is uplink and the second transmission direction is downlink. In addition, the second OFDM symbol may contain a reference signal and the third OFDM symbol may contain data. In such an embodiment, the UE 205 sends, for example, uplink data in the first OFDM symbol, switches to downlink communication (e.g., during a gap period), receives a reference signal in the second OFDM symbol, and receives, for example, UCI in the third OFDM symbol.

[0068] Figure 3 A network 300 is depicted in which a UE 205 sends an uplink control message to multiple transmission reception points ("TRPs"). The network 300 may be an embodiment of the system 100 described above. Here, the UE 205 is simultaneously connected to a macro base station ("macro BS") 310 and one or more low power nodes 315. In this case, the uplink reception point may be dynamically changed between the macro BS 310 and the low power nodes 315. Here, the macro BS 310 and the low power nodes 315 may be embodiments of the base unit 110. In the depicted embodiment, the UE 205 transmits a long PUCCH / PUSCH 320 by using a DFT-S-OFDM waveform. In addition, the UE transmits a short PUCCH / PUSCH 325 by using an OFDM waveform. Although UE 205 is depicted as sending long PUCCH / PUSCH 320 to macro BS 310 and short PUCCH / PUSCH 325 to low power node 315 , in other embodiments, UE 205 sends long PUCCH / PUSCH to low power node 315 and short PUCCH / PUSCH to macro BS 310 .

[0069] From the network (system) perspective, long PUCCH and short PUCCH can be multiplexed in a given time slot. For a given UE 205, the UE can be configured to use both long PUCCH and short PUCCH unless it is in a transmit (Tx) power-limited condition for all service TRPs (e.g., for both macro BS 310 and low power node 315).

[0070] In some embodiments, the UE 205 always uses an OFDM waveform to send short PUCCH / PUSCH. In certain embodiments, the UE 205 uses an OFDM waveform or a DFT-S-OFDM waveform to send long PUCCH / PUSCH. In one embodiment, the UE 205 can be configured (e.g., through higher layer signaling from a network function) to use an OFDM waveform or a DFT-S-OFDM waveform based on cell (or TRP) measurements / reports, such as reference signal received power. In another embodiment, the UE 205 receives an indication in the DCI that it uses an OFDM waveform or a DFT-S-OFDM waveform for long PUCCH / PUSCH. Here, the DCI can use explicit parameters or implicit indications in the DCI to indicate which waveform is used for the long PUCCH / PUSCH. In addition, the DCI can dynamically indicate the waveform based on the target TRP of the long PUCCH / PUSCH. In some embodiments, the UE 205 is configured (or signaled) to use an OFDM waveform when sending a long uplink control channel to the low power node 315 and to use a DFT-S-OFDM waveform when sending a long uplink control channel to the macro BS. In other embodiments, the UE 205 is configured to always use a DFT-S-OFDM waveform when sending a long PUCCH / PUSCH.

[0071] In some embodiments, UE 205 may require both long PUCCH (or long PUSCH) and short PUCCH to be sent in the same time slot, so that long PUCCH (or long PUSCH) and short PUCCH partially overlap in time. For example, UE 205 may be scheduled using uplink resources that send long PUCCH, and UE 205 may also receive low-latency downlink data that requires it to send short PUCCH with HARQ-ACK feedback.

[0072] Depending on the hardware capabilities of UE 205 and various network deployment scenarios, UE 205 may send long PUCCH / PUSCH during the overlapped duration in addition to the overlapped duration and send short PUCCH during the overlapped duration. Where supported, UE 205 may instead send long PUCCH / PUSCH during the overlapped duration and send short PUCCH during the overlapped duration. In addition, as described below with reference to Figure 6 As further discussed, the UE 205 may transmit long PUCCH / PUSCH and short PUCCH according to different transmit beamforming weights.

[0073] Figure 4One embodiment of a user equipment device 400 that may be used to transmit a short duration uplink channel according to an embodiment of the present disclosure is depicted. The user equipment device 400 may be an embodiment of a remote unit 105 and / or a UE 205. In addition, the user equipment device 400 may include a processor 405, a memory 410, an input device 415, a display 420, and a transceiver 425. In some embodiments, the input device 415 and the display 425 are combined into a single device, such as a touch screen. In some embodiments, the user equipment device 400 may not include any input device 415 and / or display 420.

[0074] In one embodiment, processor 405 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 405 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, processor 405 executes instructions stored in memory 410 to perform the methods and routines described herein. Processor 405 is communicatively coupled to memory 410, input device 415, display 420, and transceiver 425.

[0075] In some embodiments, the transceiver 425 receives a downlink scheduling assignment message from a base unit 110 in a mobile communication network (e.g., system 100) that assigns resources for data reception of a transport block ("TB"). In response to the downlink scheduling assignment, the processor 405 may identify a set of uplink resources allocated for a short uplink control channel within a time slot. In addition, the processor 405 determines a first uplink resource from the set of uplink resources based on the downlink scheduling assignment message.

[0076] In one embodiment, the processor 405 determines the first uplink resource using a resource block ("RB") index of a first assigned frequency resource unit ("FRU") of the TB. In another embodiment, the processor 405 determines the first uplink resource using a lowest control channel element ("CCE") index of a downlink scheduling assignment message. In a third embodiment, the processor 405 determines the first uplink resource using a hybrid automatic repeat request acknowledgement ("HARQ-ACK") feedback delay of the device. In a fourth embodiment, the processor 405 determines the first uplink resource using a HARQ-ACK resource index or offset indicated in a downlink scheduling assignment message.

[0077] After having determined the first uplink resource, the processor 405 controls the transceiver 425 to send the first uplink channel on the first uplink resource, and the first uplink channel transmits the HARQ-ACK feedback for the TB. In some embodiments, the TB is received in the same time slot as the first uplink resource. Here, the transceiver 425 further receives a DCI indicating the resource set allocated for the first uplink channel. In this embodiment, receiving the DCI includes: receiving a common DCI in a common control region of a time slot.

[0078] In some embodiments, the transceiver 425 receives scheduling information to send a second uplink channel on a second uplink resource in a time slot, wherein the first uplink resource and the second uplink resource overlap at least partially in the time domain. Here, the second uplink resource is larger than the first uplink resource in the time domain. In this embodiment, the processor 405 controls the transceiver 425 to send the first and second uplink channels, including: sending at least the first uplink channel during the overlapping time period. In some embodiments, the processor 405 controls the transceiver 425 to multiplex the first uplink channel into the second uplink channel. In one embodiment, sending the first and second uplink channels includes: sending the first uplink channel using an OFDM waveform, and sending the second uplink channel using a DFT-S-OFDM waveform.

[0079] In some embodiments, transmitting the first and second uplink channels includes transmitting the second uplink channel on the second uplink resource except during overlapping time. For example, the transceiver 425 may support only a single transmit beamforming weight at a given time instance. In this scenario, transmitting the first and second uplink channels includes transmitting the first uplink channel and the second uplink channel with different transmit beamforming weights.

[0080] In some embodiments, transmitting the first and second uplink channels includes transmitting the second uplink channel during overlapping time periods. For example, the transceiver 425 may support more than one transmit beamforming weight at a given time instance. In this scenario, transmitting the first and second uplink channels includes transmitting the first uplink channel with a first transmit beamforming weight, and transmitting the second uplink channel with a second transmit beamforming weight. As another example, the transceiver 425 may support only a single transmit beamforming weight at a given time instance, but transmits the first uplink channel with the same transmit beamforming weight as the second uplink channel. In one embodiment, the first and second uplink channels are transmitted using an orthogonal frequency division multiplexing ("OFDM") waveform.

[0081] In some embodiments, processor 405 determines the time domain resource of the first uplink resource based at least on the end time resource unit ("TRU") of the TB. In some embodiments, identifying the set of uplink resources allocated for the first uplink channel in the time slot may include: receiving a higher layer message configuring the set of HARQ-ACK resources, and identifying a HARQ-ACK resource index indicated in the downlink scheduling assignment message. Here, the HARQ-ACK resource index indicates a specific one of the HARQ-ACK resources.

[0082] In some embodiments, the resources for data reception include multiple TRUs and multiple FRUs corresponding to multiple TBs. Here, the processor 405 determines the uplink resources for each TB in response to receiving the TB, and controls the transceiver 425 to send HARQ-ACK feedback in the first uplink channel. In addition, the processor 405 can determine and send HARQ-ACK feedback for at least one TB before receiving all TBs in the downlink resource assignment. In one embodiment, the TRU is a time slot including an integer number of OFDM symbols, and the FRU is a resource block including 12 subcarriers.

[0083] In various embodiments, the processor 405 controls the transceiver 425 to transmit the first channel using the first transmission direction in the first OFDM symbol, to transmit the second channel using the second transmission direction in the second OFDM symbol, and to transmit the third channel by using the second direction in the third OFDM symbol. In such an embodiment, the first channel and the third channel are transmitted at a first subcarrier spacing value, and the second channel is transmitted at a second subcarrier spacing value greater than the first subcarrier spacing value. In some embodiments, the second subcarrier spacing value is an integer multiple of the first subcarrier spacing value. In addition, the third OFDM symbol occurs immediately after the second OFDM symbol, and the second OFDM symbol occurs immediately after the transmission gap between the first and second OFDM symbols.

[0084] In some embodiments, the second channel includes a reference signal and the third channel includes data. In one embodiment, the first transmission direction is a downlink and the second transmission direction is an uplink. Here, transmitting the first channel includes: receiving a TB, and transmitting the third channel includes: sending HARQ-ACK feedback. In one embodiment, the first transmission direction is an uplink and the second transmission direction is a downlink. Here, transmitting the third channel includes: receiving a TB immediately after the reference signal.

[0085] In one embodiment, memory 410 is a computer-readable storage medium. In some embodiments, memory 410 includes volatile computer storage media. For example, memory 410 may include RAM, including: dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 410 includes non-volatile computer storage media. For example, memory 410 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 410 includes both volatile computer storage media and non-volatile computer storage media.

[0086] In some embodiments, the memory 410 stores data related to transmitting a short duration uplink channel. For example, the memory 410 may store a set of candidate resources for PUCCH, HARQ-ACK feedback, downlink scheduling assignments, downlink control information, etc. In some embodiments, the memory 410 also stores program code and related data, such as an operating system or other controller algorithms for operating the user equipment device 400.

[0087] In one embodiment, input device 415 may include any known computer input device, including: a touch panel, a button, a keyboard, a stylus, a microphone, etc. In some embodiments, input device 415 may be integrated with display 420, for example as a touch screen or similar touch-sensitive display. In some embodiments, input device 415 includes a touch screen so that text can be entered by using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 415 includes two or more different devices, such as a keyboard and a touch panel.

[0088] In one embodiment, the display 420 may include any known electronically controllable display or display device. The display 420 may be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, the display 420 includes an electronic display capable of outputting visual data to a user. For example, the display 420 may include, but is not limited to: an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the display 420 may include a wearable display, such as a smart watch, smart glasses, a head-up display, etc. Further, the display 420 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0089] In some embodiments, the display 420 includes one or more speakers for producing sound. For example, the display 420 can produce an audible alarm or notification (e.g., a beep or ring). In some embodiments, the display 420 includes one or more tactile devices for generating vibration, motion or other tactile feedback. In some embodiments, all or a portion of the display 420 can be integrated with the input device 415. For example, the input device 415 and the display 420 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 420 can be located near the input device 415.

[0090] The transceiver 425 communicates with one or more base units 110 in the mobile communication network. Via the base unit 110, the transceiver 425 can communicate with one or more network functions in the mobile communication network. The transceiver 425 operates under the control of the processor 405 to send messages, data, and other signals, and also receives messages, data, and other signals. For example, the processor 405 can selectively activate the transceiver (or part thereof) to send and receive messages at a specific time. As depicted, the transceiver 425 may include one or more transmitters 430 and one or more receivers 435. In addition, the transceiver 425 may support one or more network interfaces 440 for communicating with the base unit 110 and the mobile core network 130.

[0091] Figure 5 An embodiment of a base station device 500 that can be used to transmit a short duration uplink channel according to an embodiment of the present disclosure is depicted. The base station device 500 can be an embodiment of a base unit 110 and / or a gNB 210. In addition, the base station device 500 may include a processor 505, a memory 510, an input device 515, a display 520, and a transceiver 525. In some embodiments, the input device 515 and the display 520 are combined into a single device, such as a touch screen. In some embodiments, the base station device 500 may not include any input device 515 and / or display 520.

[0092] In one embodiment, the processor 505 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 505 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field programmable gate array ("FPGA"), or a similar programmable controller. In some embodiments, the processor 505 executes instructions stored in the memory 510 to perform the methods and routines described herein. The processor 505 is communicatively coupled to the memory 510, the input device 515, the display 520, and the transceiver 525.

[0093] In some embodiments, the transceiver 525 sends a downlink scheduling assignment message to the base unit 105 in the mobile communication network, which assigns resources for data reception of a transport block ("TB"). In addition, the processor 505 can control the transceiver to indicate to the remote unit 105 a set of uplink resources allocated for a first uplink channel within a time slot. Here, the first uplink channel can be a short uplink channel consisting of one or two symbols in the time slot (e.g., the last one or two symbols in the time slot).

[0094] In one embodiment, the downlink scheduling assignment message includes an indicator of a specific uplink resource in the uplink resources that the remote unit 105 uses for the first uplink channel. In another embodiment, the attributes of the downlink resource assignment implicitly indicate a specific uplink resource in the uplink resources that the remote unit 105 uses for the short uplink control channel. In addition, the remote unit 105 determines the first uplink resource from the set of uplink resources based on the downlink scheduling assignment message.

[0095] In one embodiment, the first uplink resource is indicated by using a resource block ("RB") index of a first allocated frequency resource unit ("FRU") of the TB. In another embodiment, the first uplink resource is indicated by using a lowest control channel element ("CCE") index of a downlink scheduling assignment message. In a third embodiment, the first uplink resource is indicated by using a hybrid automatic repeat request acknowledgement ("HARQ-ACK") feedback delay of the device. In a fourth embodiment, the first uplink resource is indicated by using a HARQ-ACK resource index or offset indicated in a downlink scheduling assignment message.

[0096] In addition, the processor 505 controls the transceiver 525 to receive a first uplink channel on the first uplink resource, and the first uplink channel transmits at least HARQ-ACK feedback for the TB. In some embodiments, the TB is sent in the same time slot as the first uplink resource. Here, the transceiver 525 further sends a DCI indicating a resource set allocated for the first uplink channel. In this embodiment, sending the DCI includes: sending a common DCI in a common control region of a time slot.

[0097] In some embodiments, the transceiver 525 sends scheduling information to the remote unit 105 to send a second uplink channel on a second uplink resource within a time slot, but wherein the first uplink resource and the second uplink resource at least partially overlap in the time domain. Here, the second uplink resource is larger than the first uplink resource in the time domain. In such embodiments, the processor 505 controls the transceiver 525 to receive the first and second uplink channels, including: receiving at least the first uplink channel during the overlapping time.

[0098] In some embodiments, the remote unit 105 multiplexes the first uplink channel into the second uplink channel, wherein the multiplexed channels are received by the transceiver 525. In one embodiment, receiving the first and second uplink channels includes receiving the first uplink channel having an OFDM waveform, and receiving the second uplink channel having a DFT-S-OFDM waveform.

[0099] In some embodiments, sending the first and second uplink channels includes: receiving the second uplink channel on the second uplink resource except during overlapping time periods. For example, the remote unit 105 may support only a single transmit beamforming weight at a given time instance, wherein the first uplink channel and the second uplink channel require different transmit beamforming weights. In other embodiments, receiving the first and second uplink channels includes: receiving the second uplink channel during overlapping time periods. For example, the first uplink channel may require the same transmit beamforming weight as the second uplink channel (e.g., the first and second uplink channels may be used for the same TRP). In one embodiment, the first and second uplink channels are sent using an orthogonal frequency division multiplexing ("OFDM") waveform.

[0100] In some embodiments, the processor 505 controls the transceiver 525 to send a higher layer message configuring a set of HARQ-ACK resources to the remote unit 105. In addition, the processor 505 controls the transceiver 525 to indicate a HARQ-ACK resource index in the downlink scheduling assignment message. Here, the HARQ-ACK resource index indicates a specific HARQ-ACK resource in the configured HARQ-ACK resources for the remote unit 105 to use as the first uplink resource.

[0101] In some embodiments, the resources used for data reception (by the remote unit 105) include multiple TRUs and multiple FRUs corresponding to multiple TBs. Here, the transceiver 525 receives uplink resources for each TB, each uplink resource being used to transmit HARQ-ACK feedback in a first uplink channel. In addition, the transceiver 525 can receive HARQ-ACK feedback for at least one TB before sending all TBs in a downlink resource assignment. In one embodiment, a TRU is a time slot comprising an integer number of OFDM symbols, and a FRU is a resource block comprising 12 subcarriers.

[0102] In various embodiments, the processor 505 controls the transceiver 525 to transmit the first channel using the first transmission direction in the first OFDM symbol, to transmit the second channel using the second transmission direction in the second OFDM symbol, and to transmit the third channel using the second transmission direction in the third OFDM symbol. In such embodiments, the first channel and the third channel are transmitted at a first subcarrier spacing value, and the second channel is transmitted at a second subcarrier spacing value greater than the first subcarrier spacing value. In some embodiments, the second subcarrier spacing value is an integer multiple of the first subcarrier spacing value. In addition, the third OFDM symbol occurs immediately after the second OFDM symbol, and the second OFDM symbol occurs immediately after the transmission gap between the first and second OFDM symbols.

[0103] In some embodiments, the second channel includes a reference signal and the third channel includes data. In one embodiment, the first transmission direction is a downlink and the second transmission direction is an uplink. Here, transmitting the first channel includes sending a TB and transmitting the third channel includes receiving HARQ-ACK feedback for the TB. In one embodiment, the first transmission direction is an uplink and the second transmission direction is a downlink. Here, transmitting the third channel includes sending the TB immediately after the reference signal.

[0104] In one embodiment, memory 510 is a computer-readable storage medium. In some embodiments, memory 510 includes volatile computer storage media. For example, memory 510 may include RAM, including: dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 510 includes non-volatile computer storage media. For example, memory 510 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 510 includes both volatile computer storage media and non-volatile computer storage media.

[0105] In some embodiments, the memory 510 stores data related to transmitting a short duration uplink channel. For example, the memory 510 may store a set of candidate resources for PUCCH, HARQ-ACK feedback, downlink scheduling assignments, downlink control information, etc. In some embodiments, the memory 510 also stores program code and related data, such as an operating system or other controller algorithms for base station device 500 operation and one or more software applications.

[0106] In one embodiment, input device 515 may include any known computer input device, including: a touch panel, a button, a keyboard, a stylus, a microphone, etc. In some embodiments, input device 515 may be integrated with display 520, for example as a touch screen or similar touch-sensitive display. In some embodiments, input device 515 includes a touch screen so that text can be entered by using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 515 includes two or more different devices, such as a keyboard and a touch panel.

[0107] In one embodiment, the display 520 may include any known electronically controllable display or display device. The display 520 may be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, the display 520 includes an electronic display capable of outputting visual data to a user. For example, the display 520 may include, but is not limited to: an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the display 520 may include a wearable display, such as a smart watch, smart glasses, a head-up display, etc. Further, the display 520 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, etc.

[0108] In some embodiments, the display 520 includes one or more speakers for producing sound. For example, the display 520 can produce an audible alarm or notification (e.g., a beep or ring). In some embodiments, the display 520 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or a portion of the display 520 can be integrated with the input device 515. For example, the input device 515 and the display 520 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 520 can be located near the input device 515.

[0109] The transceiver 525 communicates with one or more remote units in the mobile communication network. The transceiver 525 can also communicate with one or more functions in the mobile communication network. The transceiver 525 operates under the control of the processor 505 to send messages, data, and other signals, and also receives messages, data, and other signals. For example, the processor 505 can selectively activate the transceiver (or part thereof) to send and receive messages at a specific time. As depicted, the transceiver 525 may include one or more transmitters 530 and one or more receivers 535. In addition, the transceiver 525 can support one or more network interfaces 540 for communicating with the remote unit 105 and / or the mobile core network 130.

[0110] Figure 6 Communications 600 between a gNB 210 and a UE 205 are depicted, wherein the UE 205 transmits a short duration uplink channel. Here, the system uses a paired spectrum (e.g., FDD) including a downlink carrier 605 (labeled "Carrier 1A") and an uplink carrier 610 (labeled "Carrier 1B"). Here, the gNB 210 transmits (and the UE 205 receives) downlink signals (including a downlink control channel and a downlink data channel) over the downlink carrier 605, and the UE 205 transmits (and the gNB 210 receives) uplink signals (including an uplink control channel and an uplink data channel) over the uplink carrier 610.

[0111] As depicted, gNB 210 transmits downlink control information (“DCI”) 615 including scheduling information in slot n-1. Here, DCI 615 schedules UE 205 to utilize long PUSCH (e.g., for transmitting uplink data 620) in slot n. In some embodiments, the scheduling information includes a waveform indicator for the long PUSCH. However, due to the arrival of urgent / time-critical / low-latency DL data 630 for UE 205 (as indicated in DCI 625 for slot n), the network schedules low-latency DL data reception in slot n along with HARQ-ACK feedback transmission expected to occur in the last part of slot n (e.g., the last one or two symbols of slot n). Note that in other embodiments, UE 205 may be expected to transmit its full / periodic CSI report in slot n using long PUCCH (e.g., as semi-statically configured via higher layer signaling). In any case, the long PUSCH (or long PUCCH) and the short PUCCH in slot n partially overlap in time.

[0112] UE 205 sends a short PUCCH (e.g., including UCI 635) at the expected position within time slot n. Depending on the hardware capabilities of UE 205 and the network deployment scenario, UE 205 may optionally send a long PUSCH (or long PUCCH) during the overlapping time. Note that UCI 635 includes HARQ-ACK feedback for downlink data 630.

[0113] In a first embodiment, UCI 635 for short PUCCH is intended for a first TRP (e.g., low power node 315), and long PUSCH (or long PUCCH) is intended for a different TRP (e.g., macro BS 310), and different TRPs require different Tx beam directions (e.g., different beamforming weights). In this scenario, it is assumed that UE 205 is only able to transmit signals in one beam direction at a time, for example, due to one radio frequency (RF) chain having one antenna panel, or two RF chains corresponding to dual polarization having one antenna panel, wherein each RF chain (a chain consisting of RF devices such as transmitters, receivers, cables, amplifiers, attenuators, analog-to-digital converters, loads, etc.) is connected to antenna elements having a common polarization direction.

[0114] In this embodiment, UE 205 does not send (one or more) symbols of long PUSCH / PUCCH that overlap with short PUCCH, but instead sends short PUCCH during the overlapping time. In some embodiments, in addition to (one or more) symbols of long PUSCH / PUCCH that overlap with short PUCCH, UE 205 may also not send one or more symbols of long PUSCH / PUCCH that occur before overlapping with short PUCCH. In some embodiments, the target TRP (e.g., macro BS 310) for long PUSCH / PUCCH may or may not be aware of the presence of (one or more) punctured symbols, depending on the coordination level between TRPs. Even if the target TRP for long PUSCH / PUCCH is unaware of the presence of the co-scheduled short PUCCH for UE 205, the TRP receiver may blindly detect the (one or more) punctured symbols.

[0115] In the second embodiment, UCI 635 for short PUCCH and long PUSCH (or long PUCCH) is also intended for different TRPs with different Tx beam directions (e.g., different beamforming weights), respectively. However, in this scenario, it is assumed that UE 205 is capable of transmitting signals with more than one beam direction at a time based on more than one antenna panel and / or associated more than one RF chain. Two or more RF chains may be able to form beams in different directions.

[0116] In this second embodiment, UE 205 transmits both long PUSCH / PUCCH and short PUCCH as scheduled, regardless of the configured waveform of the long PUSCH / PUCCH. In one embodiment, because each antenna panel has its own power amplifier (e.g., combined with an antenna element), simultaneously transmitting a DFT-S-OFDM waveform and an OFDM waveform through different antenna panels does not degrade the peak-to-average power ratio ("PAPR") performance of the DFT-S-OFDM waveform.

[0117] In the third embodiment, the UCI 635 for short PUCCH and long PUSCH / PUCCH is intended for a common TRP (e.g., macro BS 310) with the same Tx beam direction (e.g., using the same beamforming weights). In addition, it is assumed that in this scenario, the DCI 615 indicates that the long PUSCH / PUCCH is transmitted using DFT-S-OFDM.

[0118] Because it is undesirable for the UE 205 to simultaneously transmit the OFDM-based short PUCCH and the DFT-S-OFDM-based long PUSCH / PUCCH on (one or more) overlapping symbols (due to PAPR degradation), the UE 205 multiplexes the UCI 635 for the short PUCCH into the long PUSCH / PUCCH. In addition, the UE 205 performs rate matching or puncturing on the long PUSCH / PUCCH around the last (one or more) symbols corresponding to the short PUCCH to multiplex the UCI 635. In an alternative scenario, the UE 205 does not transmit the (one or more) symbols of the long PUSCH / PUCCH that overlap with the short PUCCH, but instead transmits only the short PUCCH during the overlapping time.

[0119] In the fourth embodiment, the UCI 635 for short PUCCH and long PUSCH / PUCCH is also intended for a common TRP with the same Tx beam direction (e.g., using the same beamforming weights). In addition, it is assumed that in this scenario, the DCI 615 indicates that the long PUSCH / PUCCH is transmitted using an OFDM waveform. Here, the UE 205 transmits both the long PUSCH / PUCCH and the short PUCCH as scheduled.

[0120] The UE 205 operation described above also applies when long PUSCH (or long PUCCH) and short PUSCH transmissions are scheduled / expected in a time slot. In one embodiment, the short PUCCH resources and short PUSCH resources for time slot n may be dynamically signaled via DCI 625 in time slot n. In one embodiment, if a DL scheduling DCI is sent in time slot n, the resources of the short PUCCH for HARQ-ACK feedback may be indicated in the DCI 625 that schedules the corresponding DL data channel (e.g., downlink data 630).

[0121] In another embodiment, a set of subcarriers (or a set of resource blocks) allocated as the short PUCCH region of slot n is dynamically indicated via DCI, and the subcarriers used for each short PUCCH within the set of allocated subcarriers are implicitly determined, for example, based on a combination of the lowest control channel element ("CCE") index of the DCI 625 that schedules the corresponding DL data channel and the HARQ-ACK feedback delay. This hybrid approach for determining short PUCCH resources reduces DCI signaling overhead and also provides flexibility in scheduling long PUCCH / PUSCH.

[0122] In some embodiments, the network identifies a shortage of available subcarriers for short PUSCH / PUCCH in time slot n. Here, the network can reassign some of the subcarriers scheduled for long PUSCH / PUCCH as part of the short PUCCH region or short PUSCH, and indicate the shortened (i.e., shortened by 1 to 2 symbols) long PUSCH / PUCCH transmission to the affected UEs via DCI in time slot n or time slot n-1. Therefore, a UE that receives an indication of a truncated long PUSCH / PUCCH does not transmit on symbols reassigned to short PUCCH / PUSCH (e.g., overlapping with short PUCCH / PUSCH) in time slot n.

[0123] FIG. 7A to FIG. 7DVarious examples of slot resource usage for unpaired spectrum (e.g., TDD) are depicted. Here, each physical channel carrying DCI, UCI, DL data, or UL data can have a separate demodulation reference signal ("DMRS") 702. In one embodiment, frequency division multiplexed (FDM) DM RSs are used to demodulate DCI and short PUCCH / PUSCH / DL data channels. Here, short PUCCH / PUSCH / DL data channels are always sent using OFDM waveforms. In this embodiment, time division multiplexed (TDM) DM RSs are used for long PUSCH, which can be sent using OFDM or DFT-S-OFDM waveforms as discussed above. In another embodiment, TDM DM RSs are used for all physical channels, regardless of the waveform used.

[0124] Fig. 7A and Figure 7B An example of time slot usage of TDM DM RS for unpaired spectrum (eg, TDD mode operation) is shown. Figure 7C and Fig.7D An example of a time slot usage of a mix of TDM and FDM DM RS for unpaired spectrum (e.g., TDD mode operation) is shown. Figures 7A to 7D In the example, the time slot duration is equal to 7 symbol durations (T S ).

[0125] FIG. 7A to FIG. 7D An exemplary use of time slots from a system perspective in an unpaired spectrum is shown. Here, a time slot comprises a time slot having a symbol duration T s 7 OFDM (or DFT-S-OFDM) symbols. FIG. 7A to FIG. 7D In the , "UCI" occupying 1 symbol depicts a short PUCCH, and "UCI" occupying more than 2 symbols corresponds to a long PUCCH. The short PUCCH may be frequency-division multiplexed with a short UL data channel (e.g., a PUSCH that also occupies one or two symbol periods), a long UL data channel (e.g., a PUSCH that occupies more than 2 symbol periods), and / or a long PUCCH in the last symbol period.

[0126] In some embodiments, the mobile communication network may dynamically determine and signal the radio resources (e.g., subcarrier allocation) of the short PUCCH / PUSCH of time slot n in time slot n, taking into account other pre-scheduled long PUSCH / PUCCH transmissions (e.g., UL data or full / periodic CSI reports) in time slot n. Dynamically adjusting the short PUCCH / PUSCH resources allows flexible scheduling of long PUSCH / PUCCH and efficient resource utilization. In the case where there is no DL region in time slot n, such as a full UL time slot for unpaired spectrum, the subcarrier allocation of the short PUCCH / PUSCH in time slot n may be indicated in time slot nk including the DL region before time slot n but closest to time slot n.

[0127] In one embodiment, both short PUCCH resources and short PUSCH resources for time slot n may be dynamically signaled via DCI 625 in time slot n (or in time slot nk if there is no DL region in time slot n). If a DL scheduling DCI is sent in time slot n or time slot nk, the resources for the short PUCCH for HARQ-ACK feedback may be indicated in the DCI that schedules the corresponding DL data channel.

[0128] In a cell with unpaired spectrum, the network may set a guard period ("GP") 711 that is shorter than the symbol duration of the data channel, and may utilize the remaining time of the symbol duration of the data channel, which is not reserved for GP 711, to transmit / receive the DM RS 702 of the data channel. Here, the DM RS 702 of the data channel is transmitted / received with a subcarrier spacing greater than the subcarrier spacing of the data channel (the subcarrier spacing corresponding to the shorter symbol duration). As shown, the DM RS 702 is further time-division multiplexed with the data channel. Note that GP 711 is applicable to DL to UL switching including hardware switching time and UL transmit timing advance (TA).

[0129] Fig. 7AThe first time slot use example 700 and the second time slot use example 705 using TDM DM RS 702 are illustrated. In the first time slot use example 700, the time slot starts with a half symbol for sending DM RS 702. In the following symbols (e.g., from 0.5 to 1.5 symbols), short downlink data channels 704 and 708 (e.g., PDSCH) are sent, and DCI 706 and 710 are sent (e.g., in a downlink control channel such as PDCCH), that is, an example of time division multiplexing of DMRS using downlink channels. Note that the DM RS 702 sent in the first half symbol is associated with the downlink channel sent in the symbol time. GP 711 is set for the following half symbol (e.g., from 1.5 to 2.0 symbols), where the system transitions from downlink to uplink.

[0130] After GP 711, the uplink portion of the time slot begins with another half symbol (e.g., from 2.0 to 2.5 symbols) for DM RS 702. Here, DM RS 702 is associated with an uplink channel transmitted at least over the next three symbols (e.g., from 2.5 to 5.5 symbols), i.e., an example of time division multiplexing of DM RS with an uplink channel. The uplink channels include long uplink control channels carrying UCI 712 and UCI 720. Note that these control channels are considered "long" control channels because their duration is longer than two symbols. The uplink channels also include long data channels (e.g., long PUSCH) carrying UL data 714, 716, and 718.

[0131] In the following half symbol (e.g., from 5.5 to 6.0 symbols), the UE sends another DM RS 702. Here, the DMRS 702 is associated with the uplink channel sent at least on the last symbol (e.g., from 6.0 to 7.0 symbols), that is, the DM RS is time-division multiplexed with the uplink channel. Note that UCI 712 and UCI 720 continue in the last symbol. Moreover, the long data channel 716 continues into the last symbol of the time slot. Therefore, on these frequency bands (e.g., subcarriers), the first DM RS (labeled as "DM RS1") is sent immediately after GP 711, and the second DM RS (labeled as "DM RS2") is sent immediately before the last symbol of the time slot.

[0132] In addition, the first time slot use example 700 includes a short control channel (e.g., short PUCCH) for UCI 722, UL data 724, and UCI 726 transmitted in the last symbol of the time slot. Recall that these channels are considered "short" uplink channels because their duration does not exceed two symbols. Also note that the DM RS 702 corresponding to the short uplink channel is transmitted immediately before the short PUCCH / PUSCH.

[0133] In one embodiment, UL data 724 and at least one of UCI 722 and UCI 726 are transmitted by the same UE, that is, an example of multiplexing short PUCCH with short PUSCH in the frequency domain. In another embodiment, one of UCI 712 and UCI 720 and at least one of UCI 722 and UCI 726 are transmitted by the same UE, that is, an example of multiplexing short PUCCH with long PUCCH in the time-frequency domain. Such UE is described above with reference to Figure 6 In yet another embodiment, the UL data 716 and at least one of the UCI 722, UL data 724 and UCI 726 are transmitted by the same UE, i.e., an example of multiplexing the long PUSCH with the short PUCCH and / or the short PUSCH in the time-frequency domain.

[0134] In the second time slot use example 705, the time slot also starts with a half symbol for sending DM RS 702. In the following symbols (e.g., from 0.5 to 1.5 symbols), a long downlink data channel 728 and a short downlink data channel 708 (e.g., PDSCH) are sent, and DCI 706 and 710 are sent, for example, in a short downlink control channel (such as PDCCH). Note that the DM RS 702 sent in the first half symbol is associated with the downlink channel sent in the symbol time, that is, the DM RS is time-division multiplexed with the downlink channel. Another DM RS 702 is sent in the following half symbol (e.g., from 1.5 to 2.0 symbols). Here, the DM RS 702 is associated with the downlink data channels 728, 730 and 732 sent in the following three symbol periods (e.g., from 2.0 to 5.0 symbols), and the DMRS is also time-division multiplexed with the downlink channel. Note that here, the downlink data channel 728 continues such that the second DM RS for the channel is transmitted from 1.5 to 2.0 symbols.

[0135] After the long downlink data channel, the system sets a GP 711 for switching from downlink to uplink. In addition, the GP has a half symbol duration (e.g., from 5.0 to 5.5 symbols). After GP 711, the uplink portion of the time slot starts with another half symbol (e.g., from 5.5 to 6.0 symbols) for uplink DM RS 702. Here, DM RS 702 is associated with the uplink channel sent on the last symbol of the time slot (e.g., from 6.0 to 7.0 symbols), that is, the uplink channel is used to time-division multiplex DM RS. Here, the second time slot usage example 705 includes a short control channel (e.g., short PUCCH) for UCI 734 and UCI 738 and a short data channel (e.g., short PUSCH) for uplink data 736. Recall that these channels are considered "short" uplink channels because their duration does not exceed two symbols. Also note that the DM RS 702 associated with the short uplink channel is transmitted immediately before the short PUCCH / PUSCH (and immediately after the GP 711). In one embodiment, the UL data 736 and at least one of the UCI 734 and the UCI 738 are transmitted by the same UE, i.e., an example of multiplexing the short PUCCH with the short PUSCH in the frequency domain.

[0136] Figure 7B A third example 715 and a fourth example 725 of time slot usage utilizing TDM DM RS 702 are illustrated. Figure 7B In the third slot usage example 715, the first two symbols are used to send long PUCCH / PUSCH, and then DM RS 702 is sent on half a symbol (e.g., from 2.0 to 2.5 symbols). After the first DM RS 702, the transmission of long PUCCH / PUSCH continues for the next three symbol durations (e.g., from 2.5 to 5.5 symbols), so the DM RS is time-division multiplexed with the uplink channel. Then, another DM RS is sent on the next half symbol (e.g., from 5.5 to 6.0 symbols). Note that these DM RS 702 are associated with at least the transmission in the last symbol of the slot, that is, the DM RS is time-division multiplexed with the uplink channel. In the last symbol, the third slot usage example 715 includes a short control channel for UCI 722 and UCI 726 and a short data channel for uplink data 724. Further, the long control channels for UCI 712 and UCI 720 and the long data channel for uplink data 716 both continue into the last symbol of the slot.

[0137] Note that there is no switch from DL to UL in the third time slot use example 715, and therefore, GP 711 is not required. Further, as discussed above, the same UE 205 may be assigned both one of UCI 712, UL data 716, and UCI 720 and one of UCI 722, UL data 724, and UCI 726, all of which overlap in time during the last symbol of the time slot. Here, the UE may send a short channel (e.g., UCI 722, UL data 724, or UCI 726) without sending a long channel (e.g., UCI 712, UL data 716, or UCI 720) based on UE capabilities and the expected waveform of the uplink channel.

[0138] In one embodiment, UL data 724 and at least one of UCI 722 and UCI 726 are transmitted by the same UE, that is, an example of multiplexing a short PUCCH with a short PUSCH in the frequency domain. In another embodiment, one of UCI 712 and UCI 720 and at least one of UCI 722 and UCI 726 are transmitted by the same UE, that is, an example of multiplexing a short PUCCH with a long PUCCH in the time-frequency domain. Such a UE is described above with reference to Figure 6 In yet another embodiment, the UL data 716 and at least one of the UCI 722, UL data 724, and UCI 726 are transmitted by the same UE, i.e., an example of multiplexing the long PUSCH with the short PUCCH and / or the short PUSCH in the time-frequency domain.

[0139] In the fourth time slot use example 725, the time slot starts with a half symbol for sending a downlink DM RS 702. In the following symbols (e.g., from 0.5 to 1.5 symbols), a long downlink data channel 728 and a short downlink data channel 708 (e.g., PDSCH) are sent, and DCI 706 and 710 are sent, for example, in a short downlink control channel (such as PDCCH), i.e., the DM RS is time-division multiplexed with the downlink channel. Note that the DMRS 702 sent in the first half symbol is associated with at least the downlink channel sent in the symbol time.

[0140] Another DM RS 702 is transmitted in the following half symbol (e.g., from 1.5 to 2.0 symbols). Here, DM RS 702 is associated with downlink data channels 728, 730, and 732 transmitted in the following five symbol periods (e.g., from 2.0 to 7.0 symbols), and thus, the DM RS is time-division multiplexed with the downlink channel. Note that here, the downlink data channel 728 continues, so that the second DM RS for the channel is transmitted from 1.5 to 2.0 symbols.

[0141] Figure 7C A fifth example 735 and a sixth example 745 of slot usage are illustrated. Here, however, the slot usage includes both TDM DM RS and FDM DM RS. In the fifth slot usage example 735, the slot starts with an entire symbol for sending short downlink channels 740 to 744 multiplexed with FDM DM RS. Included are DCI+DM RS combination 740, DL data+DM RS combination 742, and DCI+DM RS combination 744. Note that DL data 728 (without multiplexed FDM DMRS) is also sent in the first symbol.

[0142] At the beginning of the second symbol, a TDM DM RS 702 is transmitted within a half symbol duration (e.g., from 1.0 to 1.5 symbols). Note that the DM RS 702 transmitted here is associated with a long downlink channel transmitted in the following four symbols (e.g., from 1.5 to 5.5 symbols), i.e., the DM RS is time-division multiplexed with the downlink channel. Here, the DMRS 702 is associated with a downlink data channel that carries DL data 728, 746, 748, and 750 and is transmitted in the following three symbol periods (e.g., from 2.0 to 5.0 symbols). Also note that the downlink data channel 728 continues.

[0143] After the long downlink data channel, the system sets a GP 711 for switching from downlink to uplink. As previously described, the GP has a half symbol duration (e.g., from 5.5 to 6.0 symbols). After GP 711, the uplink portion of the time slot starts with the last symbol (e.g., from 6.0 to 7.0 symbols) of the short uplink channel multiplexed with FDM DM RS. UCI+DM RS combination 752, UL data+DM RS combination 754, and UCI+DM RS combination 756 are depicted here. In one embodiment, UL data+DM RS combination 754, and at least one of UCI+DM RS combination 752 and UCI+DM RS combination 756 are sent by the same UE, that is, an example of multiplexing short PUCCH with short PUSCH in the frequency domain (and further multiplexing with DM RS in the frequency domain).

[0144] In the sixth time slot use example 745, the time slot starts with the entire symbol used to transmit the short downlink channels 740 to 744 multiplexed with FDM DM RS. This includes DCI+DM RS combination 740, DL data+DM RS combination 742, DCI+DM RS combination 744, and DL data+DM RS combination 758. Note that DL data 728 (without multiplexed FDM DMRS) is also transmitted in the first symbol.

[0145] After the short downlink data channel, the system sets the GP 711 for switching from the downlink to the uplink. As previously mentioned, the GP has a half symbol duration (e.g., from 1.0 to 1.5 symbols). After GP 711, the uplink portion of the time slot begins with a TDM DM RS 702 sent over a half symbol duration (e.g., from 1.5 to 2.0 symbols). Note that the DM RS 702 sent here is associated with the long uplink channel sent in the following four symbols (e.g., from 2.0 to 6.0 symbols), that is, the uplink channel is used to time-division multiplex the DM RS. Here, DMRS 702 is associated with the uplink control channel for UCI 712 and 720 and the uplink data channel for UL data 714, UL data 716, and UL data 718. It should also be noted that the uplink control channel for UCI 712 and UCI 720 continues to enter the end of the time slot (e.g., continues to enter the last symbol). In addition, the sixth time slot usage example 745 is depicted in the last symbol (eg, from 6.0 to 7.0 symbols) of a short uplink channel multiplexed with FDM DM RS. A UCI+DM RS combination 760, a UL data+DM RS combination 762, and a UCI+DM RS combination 764 are depicted here.

[0146] In one embodiment, the UL data + DM RS combination 762, and at least one of the UCI + DM RS combination 760 and the UCI + DM RS combination 764 are transmitted by the same UE, that is, an example of multiplexing the short PUCCH with the short PUSCH in the frequency domain (and further multiplexing with the DM RS in the frequency domain). In another embodiment, one of the UCI 712 and the UCI 720, and at least one of the UCI + DM RS combination 760 and the UCI + DM RS combination 764 are transmitted by the same UE, that is, an example of multiplexing the short PUCCH with the long PUCCH in the time domain. Such a UE is described above with reference to Figure 6 In yet another embodiment, the UL data 716, and at least one of the UCI+DM RS combination 760, the UL data+DM RS combination 762, and the UCI+DM RS combination 764 are transmitted by the same UE, i.e., an example of multiplexing the long PUSCH with the short PUCCH and / or the short PUSCH in the time-frequency domain.

[0147] Fig.7D A seventh example 755 and an eighth example 765 of time slot usage are illustrated. Fig.7D The time slots in include both FDM DM RS and TDM DM RS 702. Fig.7D In the example 755, the time slot is dedicated to the uplink or downlink. In the seventh time slot use example 755, the time slot starts with a whole symbol for sending short downlink channels 740 to 744 multiplexed with FDM DM RS. It includes DCI+DM RS combination 740, DL data+DM RS combination 742, and DCI+DM RS combination 744. Note that DL data 728 is also sent in the first symbol (without multiplexed FDM DM RS).

[0148] At the beginning of the second symbol, a TDM DM RS 702 is transmitted within a half symbol duration (e.g., from 1.0 to 1.5 symbols). Note that the DM RS 702 transmitted here is associated with a long downlink channel transmitted in the following four symbols (e.g., from 1.5 to 5.5 symbols), i.e., the DM RS is time-division multiplexed with the downlink channel. Here, the DMRS 702 is associated with a downlink data channel for DL ​​data 728, DL data 746, DL data 748, and DL data 750 transmitted in the following three symbol periods (e.g., from 1.5 to 4.5 symbols). Also note that the downlink data channel 728 continues.

[0149] TDM DM RS 702 is sent again, for example, from 4.5 to 5.0 symbols. Here, DM RS 702 is a second DM RS 702 for a downlink data channel carrying DL data 728, DL data 746, DL data 748, and DL data 750, and the DM RS is also time-division multiplexed using the data channel. Then, the DL data channel transmits DL data 728, 746, 748, and 750 on the last two symbols of the time slot.

[0150] In the eighth time slot use example 765, the time slot starts with a half symbol for sending a downlink DM RS 702. In the following three symbols (e.g., from 0.5 to 3.5 symbols), UCI 712 and 720 are sent on the long uplink control channel, and UL data 714, UL data 716, and UL data 718 are sent on the long uplink data channel, that is, the uplink channel is used to time-division multiplex the DM RS. The second TDM DM RS 702 is sent again, for example, from 3.5 to 4.0 symbols. Here, the DM RS 702 is the second DM RS 702 for the long uplink control channel and the long uplink data channel, and the uplink channel is also used to time-division multiplex the DM RS. In addition, the eighth time slot use example 765 is depicted in the last symbol (e.g., from 6.0 to 7.0 symbols) of the short uplink channel multiplexed with FDM DM RS. A UCI+DM RS combination 760, a UL data+DM RS combination 762, and a UCI+DM RS combination 764 are depicted here.

[0151] In one embodiment, the UL data + DM RS combination 762, and at least one of the UCI + DM RS combination 760 and the UCI + DM RS combination 764 are transmitted by the same UE, that is, an example of multiplexing the short PUCCH with the short PUSCH in the frequency domain (and further multiplexing with the DM RS in the frequency domain). In another embodiment, one of the UCI 712 and the UCI 720, and at least one of the UCI + DM RS combination 760 and the UCI + DM RS combination 764 are transmitted by the same UE, that is, an example of multiplexing the short PUCCH with the long PUCCH in the time-frequency domain. Such a UE is described above with reference to Figure 6 In yet another embodiment, the UL data 716, and at least one of the UCI+DM RS combination 760, the UL data+DM RS combination 762, and the UCI+DM RS combination 764 are transmitted by the same UE, i.e., an example of multiplexing the long PUSCH with the short PUCCH and / or the short PUSCH in the time-frequency domain.

[0152] However, since the system-wide protection period of half a symbol duration may not be large enough for some UEs in a large cell, in other embodiments, the following UE / network operations may be required:

[0153] If the round-trip propagation delay or timing advance value signaled by the base station for UE 205 is greater than T1 but less than T2 (e.g., T1 < T2), then UE 205 skips receiving the last DL symbol and switches to the scheduled UL transmission. For DL demodulation, UE 205 may set the log-likelihood ratio ("LLR") information of the channel bits of the skipped DL symbol to zero (e.g., puncturing). In one example, T1 is equal to the system-wide protection period of half a symbol duration, and T2 is equal to the sum of the system-wide protection period and one symbol duration.

[0154] If the round-trip propagation delay or timing advance value signaled by the base station for the UE is greater than T1 but less than T2 (T1 < T2) and if the UE is scheduled with a long PUSCH / PUCCH immediately after the system-wide GP within a time slot, then UE205 skips transmitting the first UL symbol.

[0155] If the round-trip propagation delay or timing advance value signaled by the base station for UE 205 is greater than T2, then the network does not schedule UE 205 with a short PUSCH / PUCCH together with DL reception within the same time slot.

[0156] If the round-trip propagation delay or timing advance value signaled by the base station for UE 205 is greater than T2 and if the UE is scheduled with a long PUSCH / PUCCH immediately after the system-wide GP within a time slot, then the network assumes that UE 205 will not monitor DCI and will not receive any downlink data within that time slot.

[0157] Figure 8 Depicts multi-slot scheduling between a gNB and a UE - such as, UE 205 and gNB 210. When UE 205 receives a DL data resource assignment (e.g., PDSCH resource assignment), the resource assignment may apply to a single time slot or multiple time slots. As depicted, UE 205 may receive downlink control signals (e.g., DCI) using resource assignments applicable to time slot 0, time slot 1, time slot 2, and time slot 3. When the resource assignment applies to multiple time slots, the data transmitted over multiple time slots may be sent as one transport block ("TB") or media access control layer protocol data unit ("MAC PDU"), or may be sent as multiple TBs or MAC PDUs.

[0158] As depicted, the first resource assignment 800 includes a single TB spanning time slot 0, time slot 1, time slot 2, and time slot 3. In contrast, the second resource assignment 805 includes multiple TBs in the assignment spanning time slot 0, time slot 1, time slot 2, and time slot 3. Figure 8 Four TBs are shown, with one TB per time slot, but in other embodiments, the resource assignment may have more or fewer TBs over the same number of time resource units ("TRUs"), and TB boundaries may or may not align with slot boundaries.

[0159] Whether downlink data is to be sent as one or multiple TBs may be indicated to the UE 205 as part of the PDSCH resource assignment (i.e., dynamically). In another embodiment, it may be indicated via higher layer signaling (e.g., via RRC). In addition, HARQ-ACK transmissions (on a dedicated UL control channel, such as PUCCH; or piggybacked with UL data transmission, such as within PUSCH) by the UE 205 in response to data reception corresponding to the DL data resource assignment may depend on whether the resource assignment is for multiple TBs or whether it allocates a single TB.

[0160] Fig. 9A and Fig. 9B Depicted is uplink control message timing for multi-slot scheduling between a gNB and a UE, where the UE transmits a short duration uplink channel. Fig. 9A Downlink resources 905 and uplink resources 910 are shown for a first timing scenario 900. As depicted, a first UE ("UE1") receives a first DL resource assignment 915 spanning time slot 0 and time slot 1. Here, the DL resource assignment includes a plurality of FRUs (frequency resource units, e.g., RBs) and a plurality of TRUs (time resource units, e.g., time slots or OFDM symbols). Note that the first DL resource assignment 915 is for a single TB, even though the assignment spans multiple time slots.

[0161] Upon receiving DL data in the assigned first DL resource 915, UE1 is expected to provide HARQ-ACK feedback. It is assumed here that UE1 will use the short PUCCH to send HARQ-ACK feedback (or multiplex the HARQ-ACK feedback with UL data in the short PUSCH). In some embodiments, UE1 uses the information implicit in the first DL resource assignment 915 to select the uplink resource for sending the short uplink control channel carrying the HARQ-ACK feedback.

[0162] In some embodiments, the UL resources for HARQ-ACK transmission are selected based on the last assigned TRU of the TB. As discussed above, the short PUCCH / PUSCH is located in the last symbol (one or more) of the time slot. In addition, the subcarriers for the short uplink control channel carrying HARQ-ACK feedback can be selected based on the FRU in which UE1 receives DL data (e.g., based on the starting RB index of the allocated RB). Using the information implicit in the first DL resource assignment 915, UE1 selects a HARQ resource 925 (e.g., from a set of possible HARQ resources) for sending a short uplink control channel carrying HARQ-ACK feedback. As depicted, UE1 sends HARQ-ACK feedback in time slot 3.

[0163] Furthermore, a second UE ("UE2") receives a second DL resource assignment 920 spanning slot 0, slot 1, slot 2, and slot 3. Again, the DL resource assignment includes multiple FRUs (frequency resource units, e.g., RBs) and multiple TRUs (time resource units, e.g., slots or OFDM symbols). Here, the second DL resource assignment 920 is for multiple TBs; specifically, one TB for each slot.

[0164] Upon receiving DL data in the assigned second DL resource 920, UE2 is expected to provide HARQ-ACK feedback for each TB. It is assumed here that UE2 will use short PUCCH to send HARQ-ACK feedback (or multiplex HARQ-ACK feedback with UL data in short PUSCH). Because the resource assignment corresponds to multiple TBs, it is beneficial for UE2 to send multiple HARQ-ACK transmissions, for example, each HARQ-ACK transmission corresponds to a TB. Beneficially, this reduces delays when scheduling retransmissions for those TBs, thereby improving system performance.

[0165] In some embodiments, UE2 uses the information implicit in the second DL resource assignment 920 to select the uplink resources for each short uplink control channel for carrying HARQ-ACK feedback. In some embodiments, the UL resources for HARQ-ACK transmission are selected based on the last allocated TRU for each TB. As discussed above, the short PUCCH / PUSCH is located in the last symbol (one or more) of the time slot. In addition, the subcarriers of the short uplink control channel for carrying HARQ-ACK feedback can be selected based on the FRU in which the UE2 receives DL data (e.g., based on the starting RB index of the allocated RB).

[0166] Using the information implicit in the second DL resource assignment 920, UE2 selects (e.g., from a set of possible HARQ resources) a HARQ resource 925 for each TB to use when sending a short uplink control channel carrying HARQ-ACK feedback corresponding to the TB. Here, UE2 sends HARQ-ACK feedback for TB1 in time slot 1, HARQ-ACK feedback for TB2 in time slot 2, HARQ-ACK feedback for TB3 in time slot 3, and HARQ-ACK feedback for TB4 in time slot 4. Note that both UE1 and UE2 send HARQ-ACK in time slot 3. However, PUCCHs do not collide because UE1 and UE2 select different uplink frequency resources due to being assigned different FRUs (e.g., different RBs) for the TBs.

[0167] Note that the time delay between the end slot for DL ​​and the corresponding UL HARQ-ACK transmission can vary based on the TB size and / or the transmission duration of the TB and / or the timing advance limit (e.g., such as a maximum timing advance value). As depicted, TB1 for UE1 is a large TB (e.g., spanning more than one slot), and therefore, the corresponding HARQ-ACK has a longer delay than the TB for UE2. Here, UE1 sends the HARQ-ACK feedback corresponding to its TB1 after 2 slots, while for UE2, the corresponding HARQ-ACK is sent in the slot immediately following the slot at which each individual TB ends (e.g., because each individual TB does not span more than one slot).

[0168] Fig. 9B A second timing scenario 950 is depicted in which the UE selects a HARQ resource 925 based on an implicit determination using a DL resource assignment resulting in a collision 960. In the second timing scenario 950, the system schedules a first DL resource 915 for UE1 in slot 0 and a second DL resource 905 for UE2 in slots 0 to 3. Note that the first DL resource assignment 915 and the second DL resource assignment 920 occupy different RBs of the DL resource 905. In addition, the system schedules a third DL resource assignment 955 for a third UE ("UE3") in slot 2 and on the same RB as the first DL resource assignment 915. This results in a situation where HARQ-ACK resource selection based only on <end TRU receiving TB, FRU receiving TB> with a HARQ-ACK feedback delay configured or predefined for the corresponding TB duration causes UE1 and UE2 to select the same HARQ resource 925. This results in a collision and performance degradation.

[0169] Here, UE1 determines to send its HARQ-ACK feedback in slot 3 due to being given a large TB (or long duration for a TB) that ends in slot 1. Also, UE3, which has a small TB that ends in slot 2, determines to send its HARQ-ACK feedback in slot 3 (note that small TBs require less processing time and, therefore, can have a shorter HARQ-ACK delay). As discussed above, the system has multiple HARQ resources 925 for each slot; however, because UE1 and UE3 are assigned the same FRU (because their DL transmissions are not time-overlapping), they end up selecting the same HARQ resource 925 when the HARQ-ACK resource selection is based only on <end TRU of received TB, FRU of received TB>. This is illustrated by the collision 960.

[0170] However, because the network knows the TRU, FRU, and TB corresponding to the various DL resource assignments, the system can preempt the conflict 960 by indicating (e.g., to UE1 and / or UE3) the HARQ resource 925 for the short PUCCH. In some embodiments, UE3 (and / or UE1) is configured with multiple HARQ resources 925 via a higher layer (e.g., via an RRC layer). In such an embodiment, the third DL resource assignment 955 (and / or the first DL resource assignment 915) includes an indication of the HARQ resource 925 to be used. For example, the indication can be a 2-bit element, where a value of '00' indicates that the UE will use the implicitly determined HARQ resource 925, a value of '01' indicates that the UE will use the first resource configured by the higher layer, a value of '10' indicates that the UE will use the second resource configured by the higher layer, and a value of '11' indicates that the UE will use the third resource configured by the higher layer. Therefore, UE3 sends its HARQ-ACK in time slot 3 based on the indication. If UE3 does not receive the indication, or if it is not configured with higher layer configured resources, the UE may send its HARQ-ACK based on implicitly determined resources. In an alternative embodiment, the indication may indicate an offset (e.g., RB index offset or HARQ resource index offset) used when selecting HARQ resources 925.

[0171] Fig.10 A method 1000 for transmitting a short duration uplink channel according to an embodiment of the present disclosure is depicted. In some embodiments, the method 1000 is performed by a device such as a remote unit 105, a UE 205, and / or a user equipment device 400. In certain embodiments, the method 1000 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0172] The method 1000 starts and receives a downlink scheduling assignment message assigning resources for data reception of a transport block ("TB") (1005). In some embodiments, the TB is received in the same time slot as the first uplink resource.

[0173] The method 1000 includes identifying 1010 a set of uplink resources allocated for a first uplink channel within a time slot. In some embodiments, identifying 1010 includes receiving downlink control information ("DCI") indicating the set of resources allocated for the first uplink channel. In one embodiment, receiving the DCI includes receiving a common DCI in a common control region of the time slot. In some embodiments, identifying 1010 the set of uplink resources includes receiving a higher layer message configuring a set of HARQ-ACK resources.

[0174] The method 1000 includes determining 1015 a first uplink resource from within the set of uplink resources. Here, the determination is based on one of: a resource block ("RB") index of a first assigned frequency resource unit ("FRU") of the TB, a lowest control channel element ("CCE") index of a downlink scheduling assignment message, a hybrid automatic repeat request acknowledgement ("HARQ-ACK") feedback delay, and a HARQ-ACK resource index / offset indicated in the downlink scheduling assignment message.

[0175] In some embodiments, determining 1015 the first uplink resource includes: determining a time domain resource of the first uplink resource based at least on an end time resource unit ("TRU") of the TB. In certain embodiments, determining 1015 the first uplink resource includes: identifying a HARQ-ACK resource index indicated in a downlink scheduling assignment message, wherein the HARQ-ACK resource index indicates a specific resource in a configured HARQ-ACK resource set.

[0176] In some embodiments, the resources for data reception include a plurality of time resource units ("TRUs") and a plurality of FRUs corresponding to a plurality of TBs. Here, determining a first uplink resource (1015) includes: determining an uplink resource for each TB in response to receiving the TB. In one embodiment, a TRU is a time slot including an integer number of OFDM symbols, and a FRU is a resource block including 12 subcarriers.

[0177] The method 1000 includes sending 1020 a first uplink channel on a first uplink resource that transmits at least HARQ-ACK feedback for a TB, wherein the first uplink channel includes one or two symbols, and the method 1000 ends. In the case where the resources for data reception correspond to multiple TBs, then sending 1020 the first uplink channel includes sending HARQ-ACK feedback for at least one TB before all TBs are received in the downlink resource assignment.

[0178] In some embodiments, the remote unit receives scheduling information to send a second uplink channel on a second uplink resource within a time slot, wherein the first uplink resource and the second uplink resource at least partially overlap in the time domain. Here, the second uplink resource is larger than the first uplink resource in the time domain. In such embodiments, sending the first uplink channel (1020) on the first uplink resource includes sending the first uplink channel during the overlapping time.

[0179] In one embodiment, the second uplink channel is also sent during the overlapping time period. For example, the first uplink channel and the second uplink channel may be intended for the same TRP. In another embodiment, the first uplink channel and the second uplink channel may be intended for different TRPs, and the remote unit supports more than one transmit beamforming weight at a given time instance. In the case where the remote unit cannot transmit to two TRPs simultaneously (e.g., more than one transmit beamforming weight cannot be sent at a given point in time) or in the case where the first uplink channel and the second uplink channel are to be sent with different waveforms (e.g., OFDM and DFT-S-OFDM), then, sending 1020 the first uplink channel on the first uplink resource includes: sending only the first uplink channel during the overlapping time period. In another embodiment, sending 1020 the first uplink channel on the first uplink resource includes: multiplexing the first uplink channel into the second uplink channel.

[0180] In some embodiments, sending 1020 the first uplink channel includes sending immediately after sending the reference signal. For example, the UE may receive a TB in a first OFDM symbol and transition from DL to UL during the gap period. In addition, the reference signal may be sent immediately after the gap period in the second OFDM symbol using a different subcarrier spacing value than used to send the first uplink channel. Thus, the first uplink channel is sent in a third OFDM symbol immediately after the reference signal, but using the same subcarrier spacing value as used to transmit the TB. Here, the reference signal subcarrier spacing value may be an integer multiple of the subcarrier spacing value used to transmit the TB and the first uplink channel.

[0181] Various embodiments may be practiced in other specific forms. The described embodiments are considered to be illustrative and non-restrictive in all aspects. Therefore, the scope of the present invention is indicated by the appended claims rather than by the preceding description. All changes within the equivalent meaning and scope of the claims will be included within the scope of the claims.

Claims

1. A method performed by a user equipment UE, the method comprising: sending a first uplink channel on a first uplink resource; sending a second uplink channel on a second uplink resource in the same time slot, wherein the first uplink resource and the second uplink resource at least partially overlap in time, and wherein the first uplink channel comprises a short physical uplink control channel PUCCH and is used for a first transmission and reception point TRP, and the second uplink channel comprises a long PUCCH or a long physical uplink shared channel PUSCH and is used for a second TRP, wherein the first TRP is different from the second TRP.

2. The method according to claim 1, wherein: The UE supports transmission using more than one transmit antenna panel at a given time instance, wherein the first uplink channel is transmitted using a first transmit antenna panel and the second uplink channel is transmitted using a second transmit antenna panel.

3. The method of claim 1, further comprising receiving first scheduling information for the first uplink channel, and receiving second scheduling information for the second uplink channel.

4. The method according to claim 3, wherein: Receiving the first scheduling information further includes: receiving a higher layer message configuring a set of PUCCH resources, and Downlink control information (DCI) including a downlink scheduling assignment message is received, wherein the first uplink resource is selected from the PUCCH resource set based on the DCI.

5. The method according to claim 3, in, The first scheduling information and the second scheduling information indicate waveforms used for the first uplink channel and the second uplink channel; and Therein, the first uplink channel and the second uplink channel are transmitted on the indicated waveform.

6. A user equipment UE, comprising: Transceiver; as well as A processor, the processor: sending a first uplink channel on a first uplink resource; sending a second uplink channel on a second uplink resource in the same time slot, wherein the first uplink resource and the second uplink resource at least partially overlap in time, and wherein the first uplink channel comprises a short physical uplink control channel PUCCH and is used for a first transmission and reception point TRP, and the second uplink channel comprises a long PUCCH or a long physical uplink shared channel PUSCH and is used for a second TRP, wherein the first TRP is different from the second TRP.

7. The UE according to claim 6, wherein: The UE supports transmission using more than one transmit antenna panel at a given time instance, wherein the first uplink channel is transmitted using a first transmit antenna panel and the second uplink channel is transmitted using a second transmit antenna panel.

8. The UE according to claim 6, wherein: The processor further receives first scheduling information for the first uplink channel and receives second scheduling information for the second uplink channel.

9. The UE according to claim 8, wherein: Receiving the first scheduling information further includes: receiving a higher layer message configuring a set of PUCCH resources, and Downlink control information (DCI) including a downlink scheduling assignment message is received, wherein the first uplink resource is selected from the PUCCH resource set based on the DCI.

10. The UE according to claim 8, in, The first scheduling information and the second scheduling information indicate waveforms used for the first uplink channel and the second uplink channel; and Therein, the first uplink channel and the second uplink channel are transmitted on the indicated waveform.

Citation Information

Patent Citations

  • Input device, display device, method of controlling input device, and program

    US20170060241A1

  • Method and apparatus for transmitting control information

    CN103109487A

  • Uplink transmission method and uplink transmission device

    CN104685955A

  • Method for transmitting uplink signal of fallback mode in wireless communication system that supports change in use of wireless resource and device therefor

    CN105981324A

  • Methods of handling wireless communications for communication system

    EP3043502A1