RU2774066C2 - Structure of interval of long physical uplink control channel (pucch) for new radio network (nr) of 5th generation (5g) - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: user equipment (hereinafter – UE) contains: a processor and a storage device in electronic communication with the processor. In this case, instructions stored in the storage device are executable for: transmission of uplink control information (hereinafter – UCI), using a physical uplink control channel (hereinafter – PUCCH) format that supports more than 2 bits of UCI payload. At the same time, the location(s) of a demodulation reference signal (hereinafter – DMRS) for PUCCH format is determined based on PUCCH length for PUCCH format, an initial PUCCH symbol for PUCCH format and configuration of frequency hopping for PUCCH format. PUCCH with only 1 DMRS does not support frequency hopping, and PUCCH with 2 or more DMRS supports configurable frequency hopping.

EFFECT: increase in the flexibility and/or efficiency of data exchange.

4 cl, 34 dwg, 16 tbl

Description

RELATED APPLICATIONS

[0001] This application relates to U.S. Provisional Application No. 62/543,757 entitled SLOT STRUCTURE OF LONG PHYSICAL UPLINK CONTROL CHANNEL (PUCCH) DESIGN FOR 5th GENERATION (5G) NEW RADIO (NR), filed August 10, 2017, content which is incorporated herein by reference in its entirety and claims priority thereon.

FIELD OF TECHNOLOGY

[0002] The present description relates essentially to communication systems. More specifically, the present description relates to a long physical uplink control channel (PUCCH) slot design for a new 5th generation (5G) radio network (NR).

BACKGROUND OF THE INVENTION

[0003] Smaller and more powerful devices have been developed to meet consumer needs and improve portability and convenience. Consumers have become addicted to wireless devices and have come to expect reliable service, extended coverage areas and enhanced functionality. A wireless communication system may provide communications to a number of wireless communication devices, each of which can be served by a base station. A base station may be a device that communicates with wireless communication devices.

[0004] As wireless communication devices have evolved, it has been possible to improve throughput, speed, flexibility, and/or efficiency. However, improvements in throughput, speed, flexibility and/or efficiency may be associated with certain problems.

[0005] For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may provide only limited flexibility and/or efficiency. As illustrated herein, systems and methods that increase the flexibility and/or efficiency of communication can be advantageous.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] In FIG. 1 is a block diagram illustrating one embodiment of one or more base stations (gNBs) and one or more user equipments (UEs) in which systems and methods for constructing a long physical uplink control channel (PUCCH) slot can be implemented, designed for the new radio network (NR) fifth generation (5G).

[0007] In FIG. 2 is a diagram illustrating one example of a resource grid for a downlink.

[0008] In FIG. 3 is a diagram illustrating one example of an uplink resource grid.

[0009] In FIG. 4 shows examples of several numerical values.

[0010] In FIG. 5 shows examples of subframe structures for the numerical values shown in FIG. four.

[0011] In FIG. 6 shows examples of intervals and subintervals.

[0012] In FIG. 7 shows examples of the scheduling timeline.

[0013] In FIG. 8 shows examples of downlink (DL) control channel monitoring areas.

[0014] In FIG. 9 shows examples of a DL control channel composed of more than one control channel element.

[0015] In FIG. 10 shows examples of uplink (UL) control channel structures.

[0016] In FIG. 11 is a block diagram illustrating one embodiment of gNB.

[0017] In FIG. 12 is a block diagram illustrating one embodiment of a UE.

[0018] In FIG. 13 shows several examples of the long PUCCH duration structure.

[0019] In FIG. 14 shows examples of two demodulation reference signals (DMRS) for every 7 symbols for normal cyclic prefix (NCP) or 6 symbols for extended cyclic prefix (ECP).

[0020] In FIG. 15 shows examples of the minimum number of symbols for a long PUCCH.

[0021] In FIG. 16 shows examples of one DMRS in every 7 symbols for NCP or 6 symbols for ECP.

[0022] In FIG. 17 shows fixed hopping applicants for PUCCH based on fixed DMRS templates.

[0023] In FIG. 18 shows examples of PUCCH basic blocks of a DMRS signal at a frequency hop.

[0024] In FIG. 19A and 19B show examples of DMRS patterns for various durations.

[0025] In FIG. 20 shows examples of RS patterns with frequency division multiplexing (FDM) between UEs for two DMRS in every 7 symbols for NCP.

[0026] In FIG. 21 shows examples of RS patterns with inter-UE FDM for two DMRS in every 6 symbols for ECP.

[0027] In FIG. 22 shows examples of an inter-UE FDM offset RS pattern for two DMRSs in every 7 NCP symbols.

[0028] In FIG. 23 shows examples of a long PUCCH with one DMRS for every 7 symbols for NCP.

[0029] In FIG. 24 shows examples of DMRS extraction in the frequency domain.

[0030] In FIG. 25 illustrates examples of UE multiplexing using various DMRS patterns.

[0031] In FIG. 26 shows examples of frequency hopping for long PUCCH formats.

[0032] In FIG. 27 shows examples of patterns with separate DMRS in each symbol.

[0033] In FIG. 28 shows various components that can be used in a UE.

[0034] In FIG. 29 shows various components that can be used in gNB.

[0035] In FIG. 30 is a block diagram illustrating one embodiment of a UE in which systems and methods for constructing a long PUCCH slot designed for fifth generation (5G) NR can be implemented.

[0036] In FIG. 31 is a block diagram illustrating one gNB implementation in which systems and methods for a long PUCCH slot structure for 5G NR operation can be implemented.

[0037] In FIG. 32 is a flowchart illustrating a method for implementing a long PUCCH slot structure for 5G NR.

[0038] In FIG. 33 is a flowchart illustrating another way to implement a long PUCCH slot structure for 5G NR.

DETAILED DESCRIPTION

[0039] User Equipment (UE) has been described. The UE includes a processor and a storage device in electronic communication with the processor. The stored instructions are executable for determining the format and configuration of an uplink control channel (PUCCH) based on signaling from a base station (gNB). The instructions are also executable for locating the demodulation reference signal (DMRS) in the configured PUCCH. The instructions are further executable to define uplink control information (UCI) multiplexing methods for the configured PUCCH. The instructions are further executable to determine a control channel resource for UCI feedback. The instructions are also executable to transmit UCI feedback on the selected control channel.

[0040] Determining the format and configuration of the uplink control channel (PUCCH) may include selecting a long PUCCH format that supports more than 2 bits of the UCI payload. A long PUCCH may use a format containing a signal, a number of resource blocks (RBs), a reference symbol pattern (RS), and/or orthogonal sequences for RS symbols and data symbols, and/or one or more control resource regions. The RS symbols may be allocated in the time domain, and orthogonal sequences may be applied to UCI data in the time domain or frequency domain.

[0041] The DMRS of the long PUCCH may occupy fixed locations within the slot structure or relative to the start symbol of the long PUCCH. If there is only 1 DMRS in a long PUCCH, frequency hopping may not be supported, and if there are 2 or more DMRS in a long PUCCH, frequency hopping may be mandatory or configurable. When configuring or supporting frequency hopping, the location of the hopping may be fixed based on the DMRS structure.

[0042] The frequency hopping may be mandatory or configurable, and the DMRS of the long PUCCH may be determined for each frequency hopping based on basic building blocks. The long PUCCH may include one or two basic building blocks of the same length or different lengths, with each basic building block configured with 1 or 2 DMRS when using a 4-7 symbol long basic building block pattern. The hopping position may be determined in the middle of a given long PUCCH, and the DMRS positions at each hopping site may be determined based on the hopping distance from the base building blocks.

[0043] In addition, a base station (gNB) is described. gNB includes a processor and memory in electronic communication with the processor. The stored instructions are executable to determine the format and configuration of the uplink control channel (PUCCH). The instructions are also executable for locating the DMRS in the configured PUCCH. The instructions are further executable to determine how to multiplex the UCI information for the configured PUCCH. The instructions are further executable to determine a control channel resource for feedback of the UCI information. The instructions are also executable to receive feedback of UCI information on the selected control channel. The control channel used for UCI feedback and the control channel resource for UCI feedback are determined based on the signaling from the gNB.

[0044] The 3rd Generation Partnership Project, also referred to as 3GPP, is a collaborative agreement to define globally applicable specifications and technical reports for 3rd and 4th generation wireless communication systems. 3GPP may define characteristics for next generation mobile communication networks, systems and devices.

[0045] The 3GPP Long Term Evolution (LTE) Standard is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile device or telephone standard to meet future requirements. In one aspect, the UMTS system is modified to provide support and specification for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0046] At least some aspects of the systems and methods described herein may be described in connection with 3GPP LTE, LTE-Advanced (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, and /or 12). However, the scope of the present description should not be limited in this regard. At least some aspects of the systems and methods described herein can be used in other types of wireless communication systems.

[0047] A wireless communications device may be an electronic device used to transmit voice and/or data to a base station, which may in turn communicate with a network of devices (e.g., the public switched telephone network (PSTN), the Internet, etc.). d.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, user equipment, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptops, netbooks, electronic readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is commonly referred to as a UE. However, since the scope of the present description should not be limited by the 3GPP standards, the terms UE and "wireless device" can be used interchangeably herein to refer to the more general term "wireless device". A UE may also be referred to more generally as a terminal device.

[0048] In 3GPP specifications, a base station is commonly referred to as Node B, Evolved Node B (eNB), Home Enhanced or Evolved Node B (HeNB), or some other similar terminology. Since the scope of the description is not to be limited by the 3GPP standards, the terms "base station", "Node B", "eNB" and "HeNB" can be used interchangeably herein to refer to the more general term "base station". Moreover, the term "base station" can be used to refer to an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (eg, a local area network (LAN), the Internet, etc.). The term "communication device" can be used to refer to a wireless communication device and/or a base station. An eNB may also be referred to more generally as a base station device.

[0049] It should be noted that, as used herein, the term "cell" can be any set of communication channels that are specified through standardization or regulated by regulators for use as an International Mobile Telecommunications Advanced (IMT-Advanced) standard, with the entire set or a subset of it may be accepted by 3GPP as licensed frequency bands (eg, frequency bands) to be used for communication between the eNB and the UE. It should also be noted that in the general description of E-UTRA and E-UTRAN, the term "cell" used herein can be defined as "a combination of downlink and optionally uplink resources". The relationship between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

[0050] "Configured cells" are cells that are known to the UE and for which it has permission from the eNB to transmit or receive information. The "configured cell(s)" may(may) be the serving cell(s). The UE may receive system information and perform the required measurements on all configured cells. The "configured cell(s)" for a radio connection may (may) consist of a primary cell and/or none, one or more secondary cell(s). "Activated cells" are those configured cells on which the UE transmits and receives. Thus, activated cells are those cells for which the UE monitors the Physical Downlink Control Channel (PDCCH) and, in downlink transmission, those cells for which the UE decodes the Physical Shared Channel for Downlink Data (PDSCH). ). "Deactivated cells" are configured cells for which the UE does not control the transmission PDCCH. It should be noted that "cell" can be described by various indicators. For example, a "cell" may have temporal, spatial (eg, geographic), and frequency characteristics.

[0051] Fifth generation (5G) cellular communications (also referred to by 3GPP as "New Radio Network", "New Radio Access Technology", or NR) uses time/frequency/space resources to provide advanced mobile broadband (eMBB) and ultra-reliable services. low latency communications (URLLC); and machine type mass communication (mMTC) services. To make better use of the time/frequency/space environment in service provision, it would be useful to be able to schedul services in the environment in a flexible manner to ensure that the environment is used as efficiently as possible, considering the conflicting needs of URLLC, eMBB and mMTC. The base station of the new radio network can be called gNB. gNB can also be referred to more generally as a base station device.

[0052] In 5G NR, at least two different types of uplink control channel (PUCCH) formats can be specified: at least one short PUCCH format and one long PUCCH format. The PUCCH is configured to transmit uplink control information (UCI). In NR, the long PUCCH format may span multiple slots, and the UE PUCCH format may be configured by the base station. The systems and methods described herein detail formats for constructing a long PUCCH. In particular, RS templates, RS location, and long PUCCH configurations are described here. The demodulation reference signal (DMRS) pattern described herein refers to a long PUCCH within a slot structure.

[0053] The NR will specify multiple PUCCH formats. With respect to UCIs, different UCIs may be reported in different PUCCH channel formats. In 5G NR, both CP-OFDM and DFT-S-OFDM signals are supported for UL transmission. In addition, different numbers may be used in one or more carrier or serving cells.

[0054] The mapping and signaling techniques required for long PUCCH formats in NR are described in detail. To minimize performance impact, a common long PUCCH structure based on both CP-OFDM and DFT-S-OFDM can be used. In addition, design enhancements for some band-specific and application-specific scenarios are described.

[0055] For a long PUCCH within a slot length, a DMRS signal may be determined based on the length of the long PUCCH, frequency hopping requirements, etc. According to one method, the DMRS signals in the long PUCCH are at fixed locations in an interval configured by signaling higher level. According to another method, the DMRS signals in the long PUCCH are at fixed locations in the long PUCCH relative to the symbol start position.

[0056] If there is only one DMRS over a long PUCCH for these two methods, frequency hopping may not be supported. If there are more than 2 DMRS over a long PUCCH, frequency hopping can be supported. If frequency hopping is supported, it may be mandatory or configurable with higher layer signaling. However, these methods may not provide the best DMRS positions for the long PUCCH based on the start and end symbols of the long PUCCH.

[0057] According to another method, DMRS signals are determined based on the structure of each frequency hop. Frequency hopping may be mandatory for all long PUCCH durations, or may be configured with higher layer signaling based on the long PUCCH duration.

[0058] In addition, to provide more flexible UE multiplexing and UCI payload sizes, UE multiplexing capabilities in the frequency domain rather than in the time domain may be supported.

[0059] Various examples of the systems and methods described herein are described below with reference to the drawings, where like reference numerals may indicate similar functional elements. The systems and methods that are essentially described and illustrated in the drawings herein may be configured and developed in a wide variety of different implementations. Thus, the following more detailed description of several embodiments that are presented in the drawings is not intended to limit the scope of the claimed invention, but merely represents systems and methods.

[0060] In FIG. 1 is a block diagram illustrating one implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods can be implemented for a Long Physical Uplink Control Channel (PUCCH) slot structure for New Radio Network (NR) 5 -th generation (5G). One or more UEs 102 communicate with one or more gNBs 160 via one or more antennas 122a-n. For example, UE 102 transmits electromagnetic signals to gNB 160 and receives electromagnetic signals from gNB 160 using one or more antennas 122a-n. gNB 160 communicates with UE 102 using one or more antennas 180a-n.

[0061] To communicate with each other, UE 102 and gNB 160 may use one or more channels 119, 121. For example, UE 102 may transmit information or data to gNB 160 using one or more uplink channels 121. In examples, uplink channels 121 include PUCCH and PUSCH, etc. One or more gNBs 160 may also transmit information or data to one or more UEs 102 using, for example, one or more downlink channels 119. In the examples, downlink channels 119 include PDCCH, PDSCH, etc. Other types of channels may be used.

[0062] Each of one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a module 124 UE operations. For example, UE 102 may implement one or more receive and/or transmit paths. For convenience, only one transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown at UE 102, although many parallel elements (eg, transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0063] Transceiver 118 may include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 may receive signals from gNB 160 using one or more antennas 122a-n. For example, receiver 120 may receive and downconvert signals to generate one or more received signals 116. One or more received signals 116 may be provided to demodulator 114. One or more transmitters 158 may signal to gNB 160 using one or more antennas 122a-n. For example, one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.

[0064] Demodulator 114 may demodulate one or more received signals 116 to create one or more demodulated signals 112. One or more demodulated signals 112 may be provided to decoder 108. UE 102 may use decoder 108 to decode the signals. Decoder 108 may generate decoded signals 110, which may include UE decoded signal 106 (also referred to as first UE decoded signal 106). For example, the first UE-decoded signal 106 may contain received payload data, which may be stored in the data buffer 104 . The other signal included in the decoded signals 110 (also referred to as the second UE-decoded signal 110) may contain overhead and/or control data. For example, the second UE-decoded signal 110 may provide data that the UE operations module 124 may use to perform one or more operations.

[0065] Typically, UE operations module 124 may enable UE 102 to communicate with one or more gNBs 160. UE operations module 124 may include one or more of UE long PUCCH modules 126.

[0066] The UE long PUCCH module 126 may implement a long PUCCH design for a new 5th generation (5G) radio network (NR). The uplink control information and the uplink waveform in NR are described. In LTE, the UCI information conveys hybrid ARQ acknowledgments (HARQ-ACK), channel state information (CSI), and scheduling request (SR). The CSI may include one or more of a channel quality indicator (CQI), a rank indicator (RI), a precoding matrix indicator (PMI), a precoding type indicator (PTI), etc. One or more cells may report about multiple CSI sizes to support Full Size Multiple Input-Multiple Output (FD-MIMO) and Coordinated Multipoint (CoMP) operations.

[0067] Similarly, in NR, when determining a scheduling request (SR), it is necessary to transmit it outside the PUSCH, as well as the HARQ-ACK due to delay. The CSI report in NR needs to be enhanced to support mobile terminal mass media (MEMO) and beamforming techniques. Thus, multiple sets of CSIs may be reported in NR reports. In addition, the CSI feedback data may include one or more of CQI, RI, PMI, PTI, beam index, etc. At least two types of CSI reports may be supported: periodic and non-periodic CSI. The periodic CSI report can be configured semi-statically. Aperiodic CSI may be triggered by a CSI request from gNB 160. Therefore, physical uplink control channel signaling must carry at least hybrid ARQ acknowledgments, CSI reports (possibly including beamforming information), and scheduling requests.

[0068] The UCI information may be transmitted as L1/L2 control signaling (eg, via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) or an uplink data channel). In addition, it should be possible to dynamically indicate (at least in conjunction with Radio Resource Control (RRC)) the time between data reception and hybrid ARQ acknowledgment transmission as part of the downlink control information (DCI).

[0069] In NR, different numerical values are supported on the same or different carriers. For uplink transmission, two waveforms/modulation schemes based on Orthogonal Frequency Division Multiplexing (OFDM) are supported. One waveform/modulation scheme is cyclic prefix OFDM (CP-OFDM). Another waveform/modulation scheme is Fast Fourier Transform (DFT) Extended OFDM (DFT-S-OFDM), also called Single Carrier FDMA (SC-FDMA) or Low Peak-to-Average Ratio (PAPR). Thus, the uplink control channel and the uplink data channel may be configured separately using the same or different waveforms and numerical values.

[0070] Hereinafter, the numerical value and length of the NR interval are described. A variety of numerical OFDM values are supported, as shown in Table 1.

µ Δƒ =2 ^µ 15[kHz] Cyclic prefix 0 fifteen Normal one thirty Normal 2 60 normal, extended 3 120 Normal four 240 Normal 5 480 Normal

Table 1

в увеличивающемся порядке в пределах подкадра и как

в увеличивающемся порядке в пределах кадра. В интервале имеется

последовательных символов OFDM, где

зависит от используемого разноса поднесущих и конфигурации интервала, как показано в таблице 2 и таблице 3. Начало интервала

в подкадре согласовано по времени с началом символа

OFDM в том же подкадре. [0071] For the subcarrier spacing configuration μ , the intervals are numbered as

in increasing order within a subframe and how

in increasing order within a frame. The interval has

consecutive OFDM symbols, where

depends on the subcarrier spacing used and the slot configuration as shown in Table 2 and Table 3. Slot start

in the subframe is timed to the beginning of the symbol

OFDM in the same subframe.

[0072] Not all UEs 102 may be configured to simultaneously transmit and receive, ie, not all OFDM symbols in a downlink interval or uplink interval may be used.

для конфигурации μ разноса поднесущих и нормального циклического префикса. [0073] Table 2 shows the number of OFDM symbols per interval

for the subcarrier spacing configuration μ and the normal cyclic prefix.

µ Interval Configuration 0 one

0 fourteen ten one 7 twenty 2 one fourteen twenty 2 7 40 four 2 fourteen 40 four 7 80 eight 3 fourteen 80 eight - - - four fourteen 160 16 - - - 5 fourteen 320 32 - - -

table 2

для конфигурации μ разноса поднесущих и расширенного циклического префикса. [0074] Table 3 shows the number of OFDM symbols per interval

for subcarrier spacing configuration μ and extended cyclic prefix.

µ Interval Configuration 0 one

2 12 40 four 6 80 eight

Table 3

[0075] This document also describes the Physical Uplink Control Channel (PUCCH) of LTE and 5G NR. In LTE, a normal TTI duration PUCCH occupies a full subframe and 1 resource block (RB) for format 1/2/3/5, and in case of format 4, more than one RB is supported. Use different formats to convey different UCI payload sizes. Frequency hopping is supported for all 1 ms TTI PUCCH formats by transmitting two slots at both ends of the carrier frequency. The multiplexing capability of the UE is implemented in the frequency domain and/or time domain depending on the PUCCH format.

для нормального CP,

для расширенного CP. [0076] According to the 1/1a/1b format, each interval contains 3 RS symbols. The Zadoff-Chu (ZC) sequence is used in the frequency domain, and the orthogonal sequences are used to spread the PUCCH in the time domain,

for normal CP,

for extended CP.

[0077] The 2/2a/2b format provides for two RS symbols in each interval. It uses frequency domain ZC sequences for UE multiplexing without time domain multiplexing.

для нормального CP и

для расширенного CP) при отсутствии мультиплексирования в частотной области. [0078] Format 3 provides for two RS symbols in each interval and uses time domain-only multiplexing with orthogonal sequences (

for normal CP and

for extended CP) in the absence of frequency domain multiplexing.

[0079] Format 4 may occupy one or more RBs. It contains encoded information bits in all data transmission symbols. Thus, it provides the largest payload size, but does not support multiplexing for multiple UEs 102 in the same RB.

; таким образом, два UE 102 могут быть мультиплексированы с применением одних и тех же ресурсов RB. [0080] Format 5 uses only one RB. It has the same structure as format 4, except for the support of spread factor 2

; thus, two UEs 102 can be multiplexed using the same RB resources.

[0081] Like the various PUCCH formats inherent in LTE, at least two transmission durations are supported in NR for uplink control. One short transmission duration around the last OFDM symbol in the interval may be supported for uplink control in NR. This short transmission duration can be time division multiplexed (TDM) or frequency division multiplexed (FDM) with data. One large transmission duration spanning many symbols (eg, filling most of a slot or slots) can be frequency division multiplexed (FDM) with data.

[0082] The short PUCCH format may be one or two symbols long. The long PUCCH format may span multiple symbols and spaces. A variety of long PUCCH formats may be defined (eg, 4 symbols, slot, multiple slots, etc.). The long PUCCH format can be used for larger payload HARQ-ACK feedback, CSI feedback, etc.

[0083] For the long PUCCH format, at least the low PAPR/CM variant must be supported. A UCI transmitted on a UL Control Channel with a long duration and at least a low PAPR variant may be transmitted in one slot or multiple slots, and transmission in multiple slots should provide a total duration of 1 ms, at least in some cases.

[0084] At least one or more of the following PUCCH formats may be supported. PUCCH format 1 may be a short PUCCH. In PUCCH format 1, the transmission duration is 1 symbol or 2 symbols, and the number of bits of UCI information (eg, HARQ-ACK) may be 1 or 2.

[0085] PUCCH format 2 may be a short PUCCH. In PUCCH format 2, the transmission duration is 1 symbol or 2 symbols, and the number of bits of UCI information (for example, HARQ-ACK) may be greater than 2.

[0086] PUCCH format 3 may be a long PUCCH. In PUCCH format 3, the transmission duration is 4 or more symbols, and the number of bits of UCI information (eg, HARQ-ACK) may be 1 or 2.

[0087] PUCCH format 4 may be a long PUCCH. In the PUCCH 4 format, the transmission duration is 4 or more symbols, and the number of bits of UCI information (eg, HARQ-ACK) may be greater than 2.

[0088] UE 102 may transmit one or more PUCCHs during a period of L _PUCCH symbols, referred to as a PUCCH interval. The value of L _PUCCH =7 or L _PUCCH =14 may be supported, with one value being configured at higher levels. If UE 102 defines a DCI format on the PDCCH that configures PDSCH reception for the number of symbols whose last symbol is within PUCCH slot n , UE 102 may provide the corresponding HARQ-ACK information when transmitting PUCCH within n + k PUCCH slot. , where k is in DCI format.

[0089] For PUCCH format configuration, a combination of semi-static configuration and (for at least some types of UCI information) dynamic signaling is used to determine PUCCH formats and resources for both long and short PUCCH formats.

[0090] This document will describe the design of the long PUCCH for 5G NR in more detail. The following describes the structure of a long PUCCH with more than 2 UCI payload bits (eg, PUCCH format 4) in 5G NR. Hereinafter, a long PUCCH is referred to as a format 4 PUCCH (ie, a PUCCH with a length of 4 or more symbols), and the number of UCI bits (eg, HARQ-ACK) is more than 2. FIG. 13 shows several examples of the long PUCCH duration structure.

[0091] In one case, a long PUCCH must span one or more integer slots. On FIG. 13 in example (a) shows that a long PUCCH spans the entire slot length in a full UL slot. On FIG. 13 in example (b) shows that a long PUCCH spans a plurality of full UL slots. In this case, the long PUCCH should not be configured in partial UL slots (eg, in a split slot or in a directed UL slot). Otherwise, a different PUCCH structure may be defined for a oriented UL slot with a different number of symbols. For example, RS location, RS and UCI multiplexing methods, orthogonal sequences used for UE multiplexing, etc.

[0092] Alternatively, a long PUCCH may be generated for one or more slots, but some symbols may be punctured in a oriented UL slot. In this case, the configuration should take into account the potential puncturing of some characters up to a given limit (for example, 4 characters).

[0093] In yet another case, the long PUCCH may be configured in a portion of the UL interval with the number of uplink symbols exceeding the threshold number X. However, for another number of symbols in the long PUCCH, different DMRS structures and orthogonal sequences may be used for UE multiplexing.

[0094] The value of X may be 4 according to 3GPP meetings. An interval of 7 or 10 characters can be configured in NR. Thus, for a normal CP, if the interval includes 7 symbols, the long PUCCH in the interval may have a duration of 4 to 7 symbols. If the interval includes 14 symbols, the long PUCCH in the interval may have a duration of 4 to 14 symbols. Similarly, for extended CP, if the interval includes 6 symbols, the long PUCCH in the interval may have a duration of 4 to 6 symbols. If the interval includes 12 symbols, the long PUCCH in the interval may have a duration of 4 to 12 symbols.

[0095] The Long PUCCH may occupy all UL symbols in the UL oriented slot, as shown in example (c) in FIG. 13. In an alternative embodiment, the long PUCCH may occupy a portion of the UL symbols up to the end of the oriented UL slot or the entire UL slot, as shown in example (e) in FIG. 13.

[0096] A long PUCCH may span multiple symbols in a oriented UL slot or a full UL slot, as shown in example (g) in FIG. 13. In this case, the long PUCCH may start at the start or the middle of the full UL slot, or else the start UL symbol of the oriented UL slot, and may end at the middle or end of the full UL slot, or the start UL symbol of the oriented UL slot, provided that the number characters is greater than or equal to the threshold value X.

[0097] If the long PUCCH spans multiple slots, the long PUCCH may span both oriented UL slots and full UL slots. The multiplexing capabilities of the UE may be different for a oriented UL slot and for a full UL slot due to the different number of symbols available to perform symbol multiplexing.

[0098] According to one approach, a long PUCCH should always be configured at the end of a oriented UL slot or a full UL slot, as shown in example (d) and example (f) in FIG. 13. According to another approach, a long PUCCH may start with a UL symbol in a oriented UL slot or full UL slot, and end with a symbol in the same slot or the next UL slot, as shown in example (h) in FIG. 13.

[0099] As a general description of the length of a long PUCCH, note that a long PUCCH may occupy part of the symbols of a oriented UL slot or a full UL slot. The long PUCCH may occupy all symbols of a oriented UL slot or a full UL slot. The long PUCCH may occupy part of the symbols of a oriented UL slot or a full UL slot followed by one or more subsequent full UL slots.

[00100] In terms of structure, the options presented in examples (a), (b), (c) and (d) in FIG. 13 may be optimal because the long PUCCH always occupies all symbols of oriented UL slots or full UL slots. On the other hand, other options may provide more flexibility in assigning PUCCH resources.

[00101] The Long PUCCH may support DFT-S-OFDM and CP-OFDM based formats. The following sections discuss the long PUCCH structure for various signals in the oriented UL slot and full UL slot. The PUCCH structure in the full UL slot will be discussed first, and then the PUCCH structure in the oriented UL slot.

[00102] With regard to long PUCCH based on DFT-S-OFDM, long PUCCH formats must support at least a low PAPR signal (eg, DFT-S-OFDM). For DFT-S-OFDM based long PUCCH formats, the LTE PUCCH structure can also be used in NR at least at the DMRS location and in the spread sequence structure. Thus, the following two DMRS patterns must be supported for a long NR PUCCH with a low PAPR signal or with a DFT-S-OFDM based signal.

[00103] The first DMRS pattern (pattern 1) includes 2 RSs in every 7 or 6 symbols as shown in FIG. 14. In such a pattern, the long PUCCH format contains 2 DMRS in every 7 symbols for normal CP (NCP) and 2 DMRS in every 6 symbols for extended CP (ECP) within the interval as shown in FIG. 14 showing the positions of the DMRS.

[00104] The DMRS signal generation and spreading sequences for UCI data may be the same as in PUCCH format 2 and PUCCH format 3. Thus, for the long PUCCH NR format, at least two formats may be supported depending on the UCI data extension methods. In one format, within each RB, different UCI symbols are transmitted in different OFDM symbols, and a spreading factor is applied in the frequency domain using a ZC sequence. This format is similar to PUCCH LTE format 2.

указано для нормального CP, а

указано для расширенного CP. Такой формат подобен формату 3 PUCCH LTE. В таблице 4 представлена ортогональная последовательность

. [00105] In another format, within each RB, different UCI symbols are transmitted on different subcarriers, and a spreading factor is applied in the time domain with the orthogonal sequences shown in Table 4 below, where

indicated for normal CP, and

indicated for extended CP. This format is similar to PUCCH LTE format 3. Table 4 shows the orthogonal sequence

.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1 1 1] [+1 +1 +1 +1] one

[+1 -1 +1 -1] 2

[+1 +1 -1 -1] 3

[+1 -1 -1 +1] four

-

Table 4

[00106] For the above pattern, it is assumed that all symbols are used in the entire UL interval. If some or all of the symbols of a oriented UL interval or a portion of the symbols in the entire UL interval can be used for the long PUCCH, the DMRS pattern for all symbols of the entire UL interval can also be reused in the long PUCCH structure. In other words, the location of the DMRS in an interval may be fixed regardless of the duration of the long PUCCH. This allows better RS multiplexing capabilities and prevents UCI interference from other PUCCH transmissions.

[00107] Thus, if a long PUCCH always occupies UL symbols until the end of a oriented UL slot or a full UL slot, to ensure that a DMRS symbol is included in a long PUCCH, the minimum number of X symbols for a long PUCCH in a oriented UL slot or a full UL slot should be 3 as shown in FIG. 15(a). If the long PUCCH can be allocated with any symbol set in the interval, to ensure that the DMRS symbol is included in the long PUCCH, the minimum number of X symbols for a normal CP may be 4, as shown in FIG. 15(b).

[00108] In the following discussion, as a general example, it can be assumed that a long PUCCH always occupies UL symbols until the end of a oriented UL slot or a full UL slot. In one format, within each RB, different UCI symbols are transmitted in different OFDM symbols, and a spreading factor is applied in the frequency domain using a ZC sequence. This format is similar to PUCCH LTE format 2. The same structure may be used for long PUCCHs occupying all symbols or some symbols of a oriented UL slot or some symbols of a full UL slot. This causes a reduction in the number of UCI transmission symbols compared to a long PUCCH occupying all the symbols of the full UL interval.

[00109] In addition, in this format, for frequency domain multiplexing in each RB, an orthogonal covering code (OCC) with a length of 12 can be used instead of the ZC sequence. This allows multiple UCI symbols to be transmitted on different subcarriers. Below are some examples of OCC codes with a length of 12.

[00110] For 2-UE multiplexing, the OCC in the frequency domain may be as specified in Table 5. Each UE 102 may transmit 6 QPSK UCI symbols in each RB of a UCI transmission symbol.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1 1 1 1 1 1 1 1 1 1] one [1 -1 1 -1 1 -1 1 -1 1 -1 1 -1]

Table 5

[00111] For 3 UE multiplexing, the OCC in the frequency domain may be as specified in Table 6. Each UE 102 may transmit 4 QPSK UCI symbols in each RB of a UCI transmission symbol.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1 1 1 1 1 1 1 1 1 1] one

2

Table 6

[00112] For 4 UE multiplexing, OCC in the frequency domain may be defined as indicated in Table 7. Each UE 102 may transmit 3 QPSK UCI symbols in each RB of a UCI transmission symbol.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1 1 1 1 1 1 1 1 1 1] one [+1 -1 +1 -1 +1 -1 +1 -1 +1 -1 +1 -1] 2 [+1 +1 -1 -1 +1 +1 -1 -1 +1 +1 -1 -1] 3 [+1 -1 -1 +1 +1 -1 -1 +1 +1 -1 -1 +1]

Table 7

[00113] In the case of frequency OCC, the same OCC may be applied to all UCI transmission symbols. Thus, the total number of UCI symbols can be determined based on the number of transmitted UCIs.

[00114] In another format, within each RB, different UCI symbols are transmitted on different subcarriers, and a time domain spreading factor is applied using orthogonal sequences, since a long PUCCH occupying a part of a slot in a oriented UL slot or in a full UL slot may contain different number of UL characters.

для 3-символьного длинного PUCCH. [00115] If the number of symbols is 3 for long PUCCH, one symbol is used for DMRS, only 2 symbols are used for UE UCI multiplexing, and the number of orthogonal sequences can be only 2. Table 8 shows the orthogonal sequence

for 3-character long PUCCH.

Sequence index n _oc

Orthogonal sequence

0 [+l +1] one [+1 -1]

Table 8

для 4-символьного длинного PUCCH. [00116] If the number of symbols is 4 for long PUCCH, 1 symbol is used for DMRS, only 3 symbols are used for UCI UCI multiplexing, and the number of orthogonal sequences can be only 3. Table 9 shows the orthogonal sequence

for 4-character long PUCCH.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1] one

2

Table 9

или 5-символьный длинный PUCCH с нормальным CP. [00117] If the number of symbols for a long PUCCH is 5, 1 symbol is used for a normal CP for DMRS, and 4 symbols are used for UE UCI multiplexing, and the number of orthogonal sequences can only be 4. Table 10 shows the orthogonal sequence

or 5 character long PUCCH with normal CP.

Sequence index n _oc

Orthogonal sequence

0 [+1 +1 +1 +1] one [+1 -1 +1 -1] 2 [+1 +1 -1 -1] 3 [+1 -1 -1 +1]

Table 10

для 5-символьного длинного PUCCH с расширенным CP. [00118] If the number of symbols for the long PUCCH is 5, 2 symbols are used for the extended CP for DMRS, and 3 symbols are used for UE UCI multiplexing, and the number of orthogonal sequences can be only 3. The same orthogonal sequences as for 4-character long PUCCH. Table 11 shows the orthogonal sequence

for 5-character long PUCCH with extended CP.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1] one

2

Table 11

для 5-символьного длинного PUCCH с нормальным CP. [00119] If the number of symbols for a long PUCCH is 6, 2 symbols are used for a normal CP for DMRS, and 4 symbols are used for UE UCI multiplexing, and the number of orthogonal sequences can be only 4. The same orthogonal sequences as for a 5-character long PUCCH. Table 12 shows the orthogonal sequence

for 5-character long PUCCH with normal CP.

Sequence index n _oc

Orthogonal sequence

0 [+1 +1 +1 +1] one [+1 -1 +1 -1] 2 [+1 +1 -1 -1] 3 [+1 -1 -1 +1]

Table 12

[00120] If the interval contains 14 symbols, and the long PUCCH is configured with more than 7 symbols, the above restrictions may be applied for every 7 symbols, and the multiplexing capabilities of the UE may be limited to a UL fragment with less than 7 symbols. And UE 102 may be configured to use an orthogonal sequence for a 7-character part and another orthogonal sequence for a fragment that is less than 7 symbols long. In this case, only a subset of orthogonal sequences of 7-character parts may be configured for UE 102.

[00121] Similarly, if the long PUCCH contains both oriented UL slots and full UL slots, the multiplexing capabilities of the UE may be limited to the oriented UL slot, as described above. Thus, in this case, only a subset of orthogonal sequences for the entire UL interval may be configured for UE 102. Meanwhile, UE 102 may be configured using an orthogonal sequence for a part of the oriented UL interval and another orthogonal sequence for parts of the entire UL interval. With this method, the UCI payload does not decrease in the oriented UL interval and the full UL interval.

[00122] According to another method, if an interval contains 14 symbols and a long PUCCH is configured with more than 7 symbols, orthogonal sequences for UE multiplexing may be jointly arranged for all configured symbols for a long PUCCH in the interval. Similarly, if the long PUCCH contains both oriented UL slots and full UL slots, orthogonal sequences for UE multiplexing may be jointly arranged for all oriented or full UL slots. For example, if a oriented UL slot contains 3 UCI transmission symbols and a full UL interval contains 5 UCI transmission symbols, eight orthogonal sequences with a length of eight can be generated for UE multiplexing. In this case, the UE's multiplexing capability is increased, but the UCI payload is reduced in all symbols or in all oriented UL slots and full UL slots.

[00123] The second DMRS pattern (pattern 2) includes one RS every 7 or 6 symbols as shown in FIG. 16. In such a pattern, the long PUCCH format contains 1 DMRS in every 7 symbols for a normal CP (NCP) and 1 DMRS in every 6 symbols for an extended CP (ECP) within an interval, as shown in FIG. 16 showing the positions of the DMRS.

[00124] The format of the DMRS signal generation and spreading sequences for UCI data may be similar to LTE PUCCH format 4 if UE multiplexing in the same RB is not supported. When supporting maximum 2 UE multiplexing in the same RB, the orthogonal sequence from Table 13 with a spreading factor of 2, which is similar to the orthogonal sequence according to the PUCCH format 5, can be used.

n _oc

Orthogonal sequence

0 [+1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1] one [+1 +1 +1 +1 +1 +1 -1 -1 -1 -1 -1 -1]

Table 13

[00125] For the above pattern, it is assumed that all symbols are used in the full UL interval. If some or all of the oriented UL slot symbols or a portion of the UL symbols in the full UL slot can be used for the long PUCCH, the DMRS pattern for the full UL slot should be used for the long PUCCH structure.

[00126] Other 12-length OCCs can be used similarly to allow multiple UCI symbols to be transmitted on different subcarriers. For example, with 3 UE multiplexing, the OCC in the frequency domain may be as specified in Table 14. Each UE 102 may transmit 4 QPSK UCI symbols in each RB of a UCI transmit symbol.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1 1 1 1 1 1 1 1 1 1] one

2

Table 14

[00127] For 4 UE multiplexing, OCC in the frequency domain may be defined as indicated in Table 15. Each UE 102 may transmit 3 QPSK UCI symbols in each RB of a UCI transmission symbol.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1 1 1 1 1 1 1 1 1 1] one [+1 -1 +1 -1 +1 -1 +1 -1 +1 -1 +1 -1] 2 [+1 +1 -1 -1 +1 +1 -1 -1 +1 +1 -1 -1] 3 [+1 -1 -1 +1 +1 -1 -1 +1 +1 -1 -1 +1]

Table 15

[00128] In the case of a frequency OCC, the same OCC may be applied to all UCI transmission symbols. Thus, the total number of UCI symbols can be determined based on the number of transmitted UCIs.

[00129] Thus, in order to ensure the inclusion of a DMRS symbol in a long PUCCH, the minimum number of X symbols for a long PUCCH in a oriented UL slot or in a full UL slot should be 4. In the case of multiplexing two UE 102s in one RB resource, the same orthogonal sequences can be applied for each UCI transmission character.

[00130] DMRS patterns and frequency hopping are also described herein. Frequency hopping is a key function of the PUCCH to provide frequency diversity. When configured, PUCCH symbols may be transmitted in different PUCCH areas. For long PUCCH duration, only 1 frequency hop is supported in an interval. The presence of frequency hopping support can be determined by DMRS templates and vice versa. The following discussion of DMRS frequency and location hopping may be applicable for DFT-S-OFDM based PUCCH and CP-OFDM based PUCCH.

[00131] According to one method, a fixed interval DMRS pattern, as described above, can be applied to a long PUCCH with any duration in the interval, regardless of the start and end symbol in the interval. This allows for better DMRS matching for long PUCCHs with different durations.

[00132] According to another method, a fixed DMRS pattern as described above can be applied from the start symbol for a long PUCCH of any duration. Thus, the fixed pattern matches the start symbol of the long PUCCH, not the start of the interval.

[00133] In both cases, the use of fixed DMRS templates may result in suboptimal placement of the DMRS in the PUCCH. In addition, if only one DMRS is present for a given PUCCH duration, frequency hopping may not be possible in some cases. Thus, with fixed DMRS locations in an interval, frequency hopping may not be supported for all PUCCH durations. For example, if there are 2 DMRS in every 7 normal CP symbols, a long PUCCH with a length of 4 may contain only one DMRS, thus frequency hopping cannot be applied. Depending on the location of the start symbol, there may be cases where only one DMRS is used for long PUCCHs of 5 or 6 symbols.

[00134] Thus, for fixed DMRS patterns with respect to a slot boundary or start symbol of a long PUCCH, frequency hopping can be disabled when there is only 1 DMRS throughout the long PUCCH. According to one approach, if there are 2 or more DMRSs over a long PUCCH within an interval, frequency hopping may be mandatory; according to another approach, the use or non-use of frequency hopping can be configured with higher layer signaling.

[00135] In the case of applying fixed DMRS patterns with respect to a slot boundary or start symbol of a long PUCCH, the hop location may also be fixed based on the DMRS patterns. On FIG. 17 below shows an exemplary potential hop location.

[00136] According to another method, the location of the DMRS is determined at each frequency hop location based on the basic structures of different length building blocks. Since the duration of a long PUCCH in an interval may vary between 4-14 symbols, in the case of frequency hopping, each frequency hopping position may occupy 2 to 7 symbols. The basic structures of the building blocks for each frequency hop are shown in FIG. 18. In FIG. 19A and 19B show some examples of DMRS patterns and hop locations for various long PUCCH durations.

[00137] This document also describes a long PUCCH based on CP-OFDM. To minimize performance impact, a common long PUCCH structure based on both DFT-S-OFDM and CP-OFDM can be used. Thus, at least the same UCI multiplexing techniques can be applied to long CP-OFDM based PUCCHs as to long DFT-S-OFDM based PUCCHs. In addition, the RS symbol location can also be provided in the same manner as for DFT-S-OFDM-based PUCCH.

[00138] In DFT-S-OFDM-based transmissions, the RS signal is separated by different ZC sequences. For a long PUCCH based on CP-OFDM, the RS should be FDM separated for different UEs 102. Thus, different UEs 102 are assigned different RS patterns that do not overlap with those of other UEs 102. FIG. 20 and 21 show several examples of RS multiplexing for various UEs 102 with pattern 1, in which two RS symbols are used in every 7 symbols for NCP and every 6 symbols for ECP. Different UEs 102 are assigned different subcarriers for RS transmission in two DMRS symbols. In these figures, each cross-hatched portion represents a DMRS of a different UE 102.

[00139] A trade-off between the UE's multiplexing capabilities and the number of RS symbols in each RB may be chosen. In one implementation, UE 102 may be configured with 2 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 6 UEs 102.

[00140] In another implementation, UE 102 may be configured with 3 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 4 UEs 102.

[00141] In another implementation, UE 102 may be configured with 4 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 3 UEs 102.

[00142] In yet another implementation, the UE may be configured with 6 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 2 UEs 102.

[00143] For CP-OFDM-based transmission with 2 RS symbols in every 7 symbols for NCP and every 6 symbols for ECP, the RS signal may also be placed at the beginning. Thus, an RS offset pattern can be applied. On FIG. 22 shows an example for NCP.

[00144] For the above pattern, it is assumed that all symbols are used in the entire UL interval. If some or all of the oriented UL slot symbols or a portion of the UL symbols in the full UL slot can be used for the long PUCCH, the DMRS pattern for the full UL slot can be used for the long PUCCH structure. In other words, the location of the DMRS in an interval may be fixed regardless of the duration of the long PUCCH. This allows better RS multiplexing capabilities and prevents UCI interference from other PUCCH transmissions.

[00145] Thus, if a long PUCCH always occupies UL symbols until the end of a oriented UL slot or a full UL slot, to ensure that a DMRS symbol is included in a long PUCCH, the minimum number of X symbols for a long PUCCH in a oriented UL slot or a full UL slot should be 3 If a long PUCCH can be allocated with any character set in the interval, the minimum number of X symbols for a normal CP must be 4 to ensure that a DMRS symbol is included in a long PUCCH.

[00146] The same orthogonal UE multiplexing sequences can be applied to long PUCCH formats with different number of symbols as described above for long PUCCH formats based on DFT-S-OFDM. In addition, for a long PUCCH, the RS multiplexing capabilities must be designed together with the UCI multiplexing capabilities. The actual UE multiplexing capability is defined as the minimum multiplexing capability of the RS multiplexing capabilities and the UCI multiplexing capabilities.

[00147] Similarly, the same combinations of frequency division multiplexing (FDM) can be used in a pattern with one RS symbol in every 7 symbols for NCP and every 6 symbols for ECP. In this case, the position of the RS should be the same as in DFT-S-OFDM-based transmission, and no RS position shift is required. On FIG. 23 shows several examples of a long PUCCH with one DMRS in every 7 symbols for NCPs with different UE multiplexing capabilities.

[00148] In one embodiment, UE 102 may be configured with 2 subcarriers for RS transmission. Thus, the RB can be multiplexed using 6 UEs 102.

[00149] In another implementation, UE 102 may be configured with 3 subcarriers for RS transmission. Thus, the RB can be multiplexed using 4 UEs 102.

[00150] In another implementation, UE 102 may be configured with 4 subcarriers for RS transmission. Thus, the RB can be multiplexed using 3 UEs 102.

[00151] In yet another implementation, UE 102 may be configured with 6 subcarriers for RS transmission. Thus, the RB can be multiplexed using 2 UEs 102.

[00152] To provide UE multiplexing in the time domain or frequency domain, the same orthogonal sequence or similar orthogonal sequences can be applied as in the case of 2 DMRS in every 7 symbols for NCP and every 6 symbols for ECP.

[00153] For the above pattern, it is assumed that all symbols are used in the entire UL interval. If some or all of the oriented UL slot symbols or a portion of the UL symbols in the full UL slot can be used for the long PUCCH, the DMRS template for the full UL slot should be reused for the long PUCCH structure. Thus, in order to ensure that a DMRS symbol is included in a long PUCCH, the minimum number of X symbols for a long PUCCH in a oriented UL slot or full UL slot should be 4. In the case of multiplexing two UE 102s in one RB resource, the same orthogonal sequences can be applied for each symbol UCI transfers.

[00154] In addition, for a long PUCCH, the RS multiplexing capabilities must be designed along with the UCI multiplexing capabilities. The actual UE multiplexing capability is defined as the minimum multiplexing capability of the RS multiplexing capabilities and the UCI multiplexing capabilities. Thus, in the case of more than two UE 102 multiplexing on an RB using the RS pattern, the UCI multiplexing capabilities can be changed similarly to the two DMRS symbol case.

[00155] In one format, within each RB, different UCI symbols are transmitted in different OFDM symbols, and a spreading factor is applied in the frequency domain using a ZC sequence. This format is similar to PUCCH LTE format 2. The same structure may be used for long PUCCHs occupying all symbols or some symbols of a oriented UL slot or some symbols of a full UL slot. This causes a reduction in the number of UCI transmission symbols compared to a long PUCCH occupying all the symbols of the full UL interval.

[00156] In addition, in this format, for frequency domain multiplexing in each RB, an orthogonal covering code with a length of 12 can be used instead of the ZC sequence. This allows multiple UCI symbols to be transmitted on different subcarriers. OCCs with a length of 12 in the frequency domain defined above for DFT-S-OFDM based PUCCH can also be used for CP-OFDM based PUCCH.

[00157] In another format, within each RB, different UCI symbols are transmitted on different subcarriers, and a time domain spreading factor is applied using orthogonal sequences, since a long PUCCH occupying a part of a slot in a oriented UL slot or in a full UL slot may contain different number of UL characters.

для расширения 6 символов. [00158] When using all symbols, up to 6 orthogonal sequences with a length equal to 6 can be generated (for example, the sequences indicated in table 14). By using only some symbols, the number of reduced-length orthogonal sequences can be reduced, and the corresponding orthogonal sequences with lengths of 2, 3, 4, and 5 can be used. Table 16 shows the orthogonal sequence

for a 6 character extension.

Sequence index n _oc

Orthogonal sequence

0 [1 1 1 1 1 1] one

2

3 [1 1 1 -1 -1 -1] four

5

Table 16

[00159] For frequency hopping for long PUCCH with CP-OFDM, the same methods can be used as for long PUCCH based on DFT-S-OFDM. According to one method, a fixed slot DMRS pattern as described above can be applied to a long PUCCH of any duration in the slot, regardless of the start and end symbols in the slot. In this way, better DMRS matching can be achieved for long PUCCHs with different durations.

[00160] According to another method, a fixed DMRS pattern as described above can be applied from the start symbol for a long PUCCH of any length. Thus, the fixed pattern matches the start symbol of the long PUCCH, not the start of the interval.

[00161] Thus, for fixed DMRS patterns with respect to the slot boundary or start symbol of the long PUCCH, frequency hopping can be disabled when there is only 1 DMRS throughout the long PUCCH. If there are 2 or more DMRSs over a long PUCCH within an interval, according to one approach, frequency hopping may be mandatory. According to another approach, the use or non-use of frequency hopping can be configured with higher layer signaling.

[00162] Compared to fixed DMRS patterns for long PUCCH based on DFT-S-OFDM, the DMRS pattern for long PUCCH based on CP-OFDM can be shifted (eg, in the DMRS start section at each frequency hop).

[00163] In the case of applying fixed DMRS patterns with respect to a slot boundary or start symbol of a long PUCCH, the hop location may also be fixed based on the DMRS patterns. Depending on the start and end symbols of the long PUCCH, only 1 hop should be supported in an interval. The hop location is determined based on the closest location to the middle of the length of the N symbol long PUCCH (i.e., the nearest fixed hop location with respect to the end of the xth symbol, where X=floor(N/2) [or ceil(N/ 2)]).

[00164] According to yet another method, the location of the DMRS is determined at each hop location based on basic structures of different length building blocks, such as a long PUCCH based on DFT-S-OFDM. The DMRS for the CP-OFDM based PUCCH at each hop location may be shifted compared to the DFT-S-OFDM based PUCCH.

[00165] This method provides optimal DMRS locations for all long PUCCH durations between 4-14 symbols. Using this method, the long PUCCH may be included in one slot or in consecutive symbols from multiple slots. It should be noted that frequency hopping may be required for all long PUCCH lengths in an interval.

[00166] In addition, it should be noted that this method can be used to determine the location/template of the DMRS regardless of whether frequency hopping is configured for the long PUCCH. If frequency hopping is not configured, one of two approaches can be applied. According to one approach, for any long PUCCH lengths between 4-14 symbols, the same DMRS position is determined as if frequency hopping was configured. According to another approach, if the duration of the long PUCCH is in the range of 4-7 symbols inclusive, the position of the DMRS can be determined with a single hop pattern as described with respect to FIG. eighteen.

[00167] As described above, the same DMRS symbol locations can be used for the CP-OFDM based long PUCCH as for the DFT-S-OFDM based long PUCCH. On the other hand, a CP-OFDM based long PUCCH may be more flexible with respect to the DMRS template. For example, DMRS locations may be spread in the frequency domain rather than in the time domain. On FIG. 24 shows several examples of spreading DMRS in the frequency domain by 2 subcarriers, 3 subcarriers, and 4 subcarriers within each RB for NCP. For each number of RSs in the RB, two potential DMRS locations are provided.

[00168] For DMRS multiplexing, different orthogonal sequences can be applied for different UE 102. The number of orthogonal sequences available depends on the number of symbols in the interval used for the long PUCCH format. For example, in a full UL interval that is 7 or 14 for normal CP or 6 or 12 for extended CP, the number of orthogonal sequences may be the same as the number of symbols in the interval.

[00169] On the other hand, if the long PUCCH is configured in a UL oriented slot, the minimum number of long PUCCH symbols may be represented as X=3. The number of orthogonal sequences for a long PUCCH in a oriented UL slot is the same as the number of long PUCCH symbols in a oriented UL slot.

[00170] In an alternative embodiment, different UEs 102 with different symbols in the time domain can be allocated for UE DMRS multiplexing using a DMRS template. On FIG. 25 shows several examples in which four UEs 102 are multiplexed using different DMRS patterns. On FIG. 25, each cross-hatched area represents a DMRS pattern of a given UE 102.

[00171] With respect to UCI data, for UE multiplexing, orthogonal sequences can be applied in either the time domain or the frequency domain. If the orthogonal sequence is spread in the time domain, the sequence length may be 7 for NCP and 6 for ECP. If the orthogonal sequence is spread in the frequency domain, the sequence length may be equal to the number of subcarriers per RB minus the number of subcarriers for DMRS.

[00172] If some or all of the UL oriented slot symbols or a portion of the UL symbols in the entire UL slot can be used for a long PUCCH, the minimum number of long PUCCH symbols can be represented as X=3 or X=4 to ensure there are at least two symbols DMRS for each UE 102.

[00173] With regard to UCI data, in a long PUCCH in a oriented UL slot for UE multiplexing, orthogonal sequences may be applied in either the time domain or the frequency domain. If the orthogonal sequence is spread in the time domain, the number of orthogonal sequences, and thus the length of the sequence, may be the same as the number of symbols for a long PUCCH in a oriented UL slot. If the orthogonal sequence is spread in the frequency domain, the sequence length may be the same as the number of subcarriers per RB minus the number of subcarriers for DMRS.

[00174] This document also describes the long PUCCH configuration. For a long PUCCH, both continuous and distributed resource allocation can be supported. PUCCH resource allocation may be performed at the RB layer. In one method, the long PUCCH resource may have a localized configuration in adjacent RBs in a PUCCH region/subband. In another method, the long PUCCH resource may have a distributed configuration in non-contiguous RBs in a PUCCH region/subband. In this case, the PUCCH resource template must be configured in the PUCCH region/subband for the specific UE 102. With one PUCCH region/subband configured, the size and position of the PUCCH region/subband can be configured.

[00175] Long PUCCH frequency hopping can be tuned to provide frequency diversity. In this case, individual PUCCH regions or subbands must be configured for UE 102, and PUCCH may be transmitted in frequency hopping in different regions/subbands, as shown in FIG. 26.

[00176] According to one method, if a long PUCCH spans multiple slots, frequency hopping may be applied at the slot level. Thus, adjacent slots are transmitted on different control areas/subbands.

[00177] According to another method, if a long PUCCH spans a set of 7 symbols for NCP or a set of 6 symbols for ECP, frequency hopping may be applied every 7 symbols for NCP and every 6 symbols for ECP. Thus, the different control areas/subbands are switched every 7 symbols for NCP and every 6 symbols for ECP. This method is slightly different from the one described above. For example, the interval may contain from 7 to 14 symbols depending on the frequency band. Thus, if the interval contains 14 symbols, this method assumes frequency hopping of the sub-slot. This may involve hopping between intervals if the interval contains 7 symbols for NCP and every 6 symbols for ECP. This may involve hopping within an interval if the interval contains 14 symbols for NCP and 12 symbols for ECP.

[00178] According to yet another method, if a long PUCCH occupies one interval of 7 symbols for NCP or 6 symbols for ECP, frequency hopping may be applied at the symbol level of the sub-slot, i.e., the first 4 symbols for NCP and the first 3 symbols for The ECP is transmitted on one control subband and the remaining 3 symbols are transmitted on the other control subband. According to one approach, this sub-slot hopping technique can be used for all long PUCCH lengths. It can be thought of as hopping within an interval. Within-slot hopping can be applied even if a long PUCCH spans multiple slots.

[00179] It is possible not to apply UL oriented slot hopping when there is only 1 DMRS in the long PUCCH or when the number of symbols is only 3 or 4 symbols.

[00180] A plurality of PUCCH regions or subbands can also be considered as distributed resource allocation for a long PUCCH. In particular, when transmitting on unlicensed spectrum, the matching of allocated resources is important for regulatory compliance. In case a plurality of PUCCH regions/subbands are configured, the size of each PUCCH region/subband may be configured, and positions of the PUCCH regions/subbands may be configured using a pattern in the carrier.

[00181] Similarly, UE 102 may be configured using two PUCCH resources to provide transmission diversity. The two PUCCH resources may be configured in the same PUCCH region/subband or in different PUCCH regions/subbands. The PUCCH resources may be localized with contiguous RB allocation or distributed with non-contiguous RB allocation.

[00182] LTE defines multiple PUCCH formats for different maximum payload sizes. Similarly, in NR, multiple long PUCCH formats need to be configured for different maximum payload sizes and multiplexing capabilities. Thus, RS negotiation, information bits and multiplexing capabilities should be considered.

[00183] In addition, for a given PUCCH format, resource allocation may be more flexible than in LTE, depending on channel conditions. For UE 102 with very good signal state for PUCCH, fewer RB resources may be allocated. In case of UE 102 with poor signal conditions (eg, UE 102 at cell edge), more RB resources may be allocated for PUCCH.

[00184] Thus, for a long PUCCH for a given UE 102, at least the following parameters may be configured: signal (eg, DFT-S-OFDM or CP-OFDM); the long PUCCH may occupy a plurality of RBs, and the number of RBs of the long PUCCH may be configured (eg, based on payload size); the long PUCCH may occupy one or more slots, and the length of the long PUCCH may be configurable based on payload size, delay tolerance, etc.; the ratio of the number of RBs and the number of intervals can be taken into account; RS template and RS position; extended sequence for UCI multiplexing; frequency diversity with multiple PUCCH regions/subbands; transmit diversity using two configured PUCCH resources; the location of one or more configured PUCCH regions/subbands, including the size and position of each PUCCH subband/region in the carrier; and localized or distributed resource allocation for the PUCCH resource in the PUCCH region/subband.

[00185] To reduce signaling overhead, a list of supported long uplink control channel formats can be specified with a given set of parameters for each of them, and a name or index of the supported long PUCCH format for UE 102 can be specified or configured.

[00186] This document also describes specific aspects regarding the long PUCCH band. 5G NR supports different frequency bands with different channel characteristics. Thus, PUCCH behavior may be different for different frequency bands. The channel condition with frequency bands below 6 GHz is more stable. Thus, it is better to use a PUCCH resource with a semi-static configuration or a PUCCH resource with a dynamic indication.

[00187] In addition to using the same DMRS positions as in a long PUCCH that spans all symbols in a slot, for a long PUCCH in a partial slot (e.g., oriented UL slot or full UL slot), DMRS positions can also be configured with signaling RRC or indicated by physical layer signaling. In this case, the DMRS locations may be different from the positions in the long PUCCH that spans all symbols in the interval. However, the same orthogonal sequences and/or RS patterns described above may be used for RS REs, and the same orthogonal sequences described previously for UCI transmission REs may also be used.

[00188] For frequencies above 6 GHz, beamforming technology is critical to performance. With regard to beamsweeping, UE 102 may use different beams in different symbols, and DMRS from different symbols may not be suitable for decoding another symbol. Thus, several methods can be considered for the long PUCCH format in the higher frequency bands above 6 GHz.

[00189] According to the first method (method 1), the long PUCCH can be configured with fewer symbols with the same beam in the time domain and more RBs in the frequency domain. For example, a long PUCCH may be limited to 7 symbols for NCP and 6 symbols for ECP, or limited to one slot length.

[00190] According to the second method (method 2), the long PUCCH may be configured using a beam pattern (ie, a pattern for symbols with the same beam). Long PUCCH symbols may be spread over a beam pattern.

[00191] According to the third method (method 3), the long PUCCH can use a separate DMRS in each symbol. UE multiplexing within a RB can be reduced or eliminated. In addition, DMRS with a length of 1 short PUCCH symbol can be used in each symbol. On FIG. 27 illustrates the patterns of reference signal patterns. For each RS setting, at least two patterns can be defined, designated Pattern 1 and Pattern 2, without loss of generality. For different symbols, you can apply a staggered DMRS pattern or other DMRS patterns. At UE 102, adjacent symbols or non-adjacent symbols may be used, as determined by the symbol template. The symbol template can be configured by the gNB 160. The same beam can be applied to the symbols in the symbol template. Or, different beams can be applied to the symbols in the symbol template by using a separate DMRS in each symbol.

[00192] In one method, for a long PUCCH above 6 GHz, gNB 160 may indicate which symbols and/or beams to use to transmit the long PUCCH using upper layer semi-static signaling or dynamic DCI signaling. The 5G NR standard needs more configurations to define the long PUCCH resource. At least one of the following aspects may be supported in NR. The long PUCCH format and/or resource for UE 102 may be semi-statically configured via higher layer signaling. The long PUCCH format and/or resource for UE 102 may be dynamically specified by physical layer signaling (eg, DCI). Various long PUCCH formats may be configured or used for feedback and different types of UCI payload sizes.

[00193] The PUCCH resource configuration considers the ratio of semi-static RRC signaling and dynamic DCI indication. In general, the PUCCH format/structure must be configured with RRC signaling, and the actual PUCCH resource to be used for UCI reporting must be determined with an explicit DCI indication.

[00194] Thus, UE 102 may be configured with a long PUCCH resource set with detailed parameters. The parameters include PUCCH formats, resource allocation, etc. In addition, the DCI indicates a long PUCCH index in the configured RRC resource set. In another method, the PUCCH resources may be indexed based on a configured RRC long PUCCH structure. UE 102 may be configured with a set of PUCCH resources based on PUCCH indices. The DCI indicates a PUCCH resource index in the PUCCH resource set configured for UE 102.

[00195] This document also discusses PUCCH for URLLC. In order to provide Ultra Reliable Low Latency Link (URLLC) traffic, some aspects of PUCCH transmission need to be taken into account. URLLC traffic requires ultra-reliability and low latency and may conflict with the PUCCH or PUSCH transmission of the same UE 102. As a general rule, URLLC traffic should have a higher priority than any other UL transmissions.

[00196] In the case where a PUCCH transmission encounters URLLC traffic in the same symbol, the URLLC should take precedence. Several ways can be considered.

[00197] In the first method (method 1), URLLC traffic is transmitted and the PUCCH in the overlapped symbol is discarded. This is a simple solution applicable in all cases regardless of the waveform and/or numerical values of the PUCCH. The entire short PUCCH shall be discarded in the presence of a 1-character PUCCH. In the case of a 2-character PUCCH, if the URLLC collides with the first character of the short PUCCH, all characters of the short PUCCH shall be discarded. If transmission of the 2-character short PUCCH is already underway and the URLLC collides with the 2nd character in the 2-character short PUCCH, the second character of the short PUCCH is discarded.

[00198] To transmit a long PUCCH, overlapping symbols must be discarded to allow higher priority to be performed for URLLC transmission. The transmission of the long PUCCH may be resumed after the transmission of the URLLC has been completed. UE 102 may discard the remaining transmission of the long PUCCH if the number of PUCCH symbols punctured by the URLLC exceeds a threshold, since the PUCCH is likely to be incorrectly decoded. Said threshold may be semi-statically configured for a given long PUCCH format.

[00199] According to the second method (method 2), simultaneous transmission of URLLC and PUCCH can be performed with power scaling in PUCCH (if necessary). When supporting simultaneous transmission of URLLC and PUCCH for the same symbol, UL transmit power must first be allocated to the URLLC traffic. The remaining power can be scaled over the RE PUCCH in the same UL symbol. This may be applied if the PUCCH REs do not overlap the URLLC transmission REs.

[00200] In the case of overlapping REs in the URLLC and PUCCH, URLLC signals are transmitted and the PUCCH symbols in the corresponding REs may be discarded. According to another approach, in the case of an overlap of RE for URLLC and PUSCH, URLLC signals are transmitted and the entire PUCCH symbol should be discarded, as in method 1.

[00201] It should be noted that if different signals are used for URLLC and PUCCH traffic, simultaneous transmission of URLLC and PUCCH may not be possible. In addition, if different numerical values are used for URLLC and PUCCH traffic, some guard interval may be required between different numerical values, and in some cases there may be no support for simultaneous transmission of URLLC and PUCCH.

[00202] UE operations module 124 may provide information 148 to one or more receivers 120. For example, UE operations module 124 may inform receiver(s) 120 of when a transmission was received.

[00203] UE operations unit 124 may provide information 138 to demodulator 114. For example, UE operations unit 124 may inform demodulator 114 of the modulation scheme intended for transmissions from gNB 160.

[00204] UE operations module 124 may provide information 136 to decoder 108. For example, UE operations module 124 may inform decoder 108 of the intended encoding of transmissions from gNB 160.

[00205] UE operations module 124 may provide information 142 to encoder 150. Information 142 may include data to be encoded and/or encoding instructions. For example, UE operations module 124 may instruct encoder 150 to encode transmission data 146 and/or other information 142. Other information 142 may include PDSCH HARQ-ACK information.

[00206] Encoder 150 may encode transmission data 146 and/or other information 142 provided by UE operations module 124. For example, encoding data 146 and/or other information 142 may include error detection and/or correction coding, mapping data to spatial, temporal, and/or frequency resources for transmission, multiplexing, etc. Encoder 150 may provide encoded data 152 modulator 154.

[00207] UE operations unit 124 may provide information 144 to modulator 154. For example, UE operations unit 124 may inform modulator 154 of the modulation type (eg, constellation matching) to be used for gNB 160 transmissions. Modulator 154 may modulate encoded data 152 to feed one or more modulated signals 156 to one or more transmitters 158.

[00208] UE operations module 124 may provide information 140 to one or more transmitters 158. This information 140 may include instructions for one or more transmitters 158. For example, UE operations module 124 may instruct one or more transmitters 158 when to transmit the signal. on gNB 160. For example, one or more transmitters 158 may transmit during a UL subframe. One or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more gNBs 160.

[00209] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a module 182 gNB operations. For example, one or more receive and/or transmit paths may be implemented on gNB 160. For convenience, only one transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in gNB 160, although many parallel elements can be implemented (e.g., transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113).

[00210] Transceiver 176 may include one or more receivers 178 and one or more transmitters 117. One or more receivers 178 may receive signals from UE 102 using one or more antennas 180a-n. For example, receiver 178 may receive and downconvert signals to generate one or more received signals 174. One or more received signals 174 may be provided to demodulator 172. One or more transmitters 117 may signal to UE 102 using one or more antennas 180a-n. For example, one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[00211] Demodulator 172 may demodulate one or more received signals 174 to create one or more demodulated signals 170. One or more demodulated signals 170 may be provided to decoder 166. Decoder 166 may be used to decode gNB signals 160. Decoder 166 may provide one or more decoded signals 164, 168. For example, the first eNB decoded signal 164 may contain received payload data that may be stored in data buffer 162. The second eNB decoded signal 168 may contain overhead and/or control data. For example, the second eNB decoded signal 168 may provide data (eg, PDSCH HARQ-ACK information) that gNB operations module 182 may use to perform one or more operations.

[00212] Typically, gNB operations module 182 may enable gNB 160 to communicate with one or more UEs 102. gNB operations module 182 may include one or more gNB long PUCCH modules 194. The gNB long PUCCH module 194 may implement the 5G NR long PUCCH design as described herein.

[00213] gNB operations module 182 may provide information 188 to demodulator 172. For example, gNB operations module 182 may inform demodulator 172 of a modulation scheme intended for transmissions from one or more UEs 102.

[00214] gNB station operations module 182 may provide information 186 to decoder 166. For example, gNB station operations module 182 may inform decoder 166 of the expected encoding of transmissions from one or more UEs 102.

[00215] gNB station operations module 182 may provide information 101 to encoder 109. Information 101 may include data to be encoded and/or instructions for encoding. For example, gNB station operations module 182 may instruct encoder 109 to encode information 101 including transmission data 105 .

[00216] Encoder 109 may encode transmission data 105 and/or other information included in information 101 provided by gNB operations module 182. For example, encoding data 105 and/or other information in information 101 may include error detection and/or correction coding, mapping data to space, time, and/or frequency resources for transmission, multiplexing, and so on. Encoder 109 may provide encoded data 111 to modulator 113. Transmission data 105 may include network data to be relayed to UE 102.

[00217] gNB operations module 182 may provide information 103 to modulator 113. This information 103 may include instructions for modulator 113. For example, gNB station operations module 182 may inform modulator 113 of the modulation type (eg, constellation mapping) to be used for transmissions from one or more UEs 102. Modulator 113 may modulate encoded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[00218] gNB station operations module 182 may provide information 192 to one or more transmitters 117. This information 192 may include instructions for one or more transmitters 117. For example, gNB station operations module 182 may instruct one or more transmitters 117 about the time transmission (or non-transmission time) of the signal to one or more UEs 102. One or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.

[00219] It should be noted that a DL subframe may be transmitted from gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to gNBs 160. Moreover, both gNBs 160 and one or more UE 102 may transmit data in a standard dedicated subframe.

[00220] It should also be noted that one or more elements or parts thereof included in one or more eNBs 160 and one or more UEs 102 may be implemented as hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuit, or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and/or accomplished through its use. For example, one or more of the methods described herein may be implemented and/or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[00221] In FIG. 2 is a diagram illustrating one example of a resource grid for a downlink. The resource grid shown in Fig. 2 may be used in some implementations of the systems and methods described herein. More details regarding the resource grid are given in connection with FIG. one.

[00222] In Fig. 2, one downlink subframe 269 may include two downlink slots 283. N ^DL _RB is the downlink bandwidth configuration of the serving cell, expressed in multiples of N ^RB _sc , where N ^RB _sc is the size of the resource block 289 in the frequency domain, expressed in the number of subcarriers, and N ^DL _symb is some number of symbols 287 OFDM in slot 283 downlink. Resource block 289 may include a number of resource elements (REs) 291.

[00223] For PCell N ^DL _RB is a broadcast as part of the system information. For SCell (including licensed band access (LAA) SCell) N ^DL _RBs are configured with an RRC message specific to UE 102. To map the PDSCH to the available RE 291, there may be a RE 291 whose index 1 satisfies the conditions: l ≥ l _{data, start} and/or l _{data, end} ≥ l in a subframe.

[00224] In the downlink, a cyclic prefix (CP) OFDM access scheme, which may also be referred to as CP-OFDM, may be used. On the downlink, PDCCH, Enhanced PDCCH (EPDCCH), PDSCH, and the like may be transmitted. A downlink radio frame may be composed of multiple downlink resource block (RB) pairs, which are also referred to as physical resource blocks (PRBs). The downlink RB pair is a block for assigning downlink radio resources determined by a predetermined bandwidth (RB bandwidth) and a time interval. A downlink RB pair consists of two downlink RBs that are continuous in the time domain.

[00225] The downlink RB consists of twelve subcarriers in the frequency domain and seven (in case of normal CP) or six (in case of extended CP) OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) and is uniquely identified by a pair of indices ( k, l ) in the interval, where k and l are the indices in the frequency and time domains, respectively. . Although the present document discusses downlink subframes in a single component carrier (CC), downlink subframes are defined for each CC, and these downlink subframes are essentially synchronized with each other among CCs.

[00226] In FIG. 3 is a diagram illustrating one example of an uplink resource grid. The resource grid shown in Fig. 3 may be used in some implementations of the systems and methods described herein. More details regarding the resource grid are given in connection with FIG. one.

[00227] In Fig. 3, one uplink subframe 369 may include two uplink slots 383. N ^UL _RB is the uplink bandwidth configuration of the serving cell, expressed in multiples of N ^RB _SC , where N ^RB _SC is the size of the resource block 389 in the frequency domain, expressed in the number of subcarriers, and N ^UL _symb is the number of 393 SC symbols -FDMA in uplink slot 383. Resource block 389 may include a number of resource elements (REs) 391.

[00228] For PCell N ^UL _RB is a broadcast as part of the system information. For SCells (including LAA SCells), N ^UL _RBs are configured with an RRC message specific to UE 102.

[00229] In the uplink, in addition to CP-OFDM, a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme, which is also referred to as Discrete Fourier Transform Extended OFDM (DFT-S-OFDM), can be used. In the uplink, PUCCH, PDSCH, PRACH, and the like may be transmitted. An uplink radio frame may be composed of multiple pairs of uplink resource blocks. The uplink RB pair is a block for assigning uplink radio resources determined by a predetermined bandwidth (RB bandwidth) and a time interval. An uplink RB pair consists of two uplink RBs that are continuous in the time domain.

[00230] An uplink RB may consist of twelve subcarriers in the frequency domain and seven (in case of normal CP) or six (in case of extended CP) OFDM/DFT-S-OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM/DFT-S-OFDM symbol in the time domain is called RE and is uniquely identified by a pair of indices (k, l) in the interval, where k and l are indices in the frequency and time domains respectively. Although the present document discusses uplink subframes in a single component carrier (CC), uplink subframes are defined for each CC.

[00231] In FIG. 4 shows examples of several numbers 401. Number #1 401a may be a base number (eg, a reference number). For example, RE 495a of base number 401a may be defined with a subcarrier spacing 405a of 15 kHz in the frequency domain and a length of 2048Ts+CP (eg, 160Ts or 144Ts) in the time domain (i.e., symbol length #1 403a), where Ts denotes unit of baseband sampling time, defined as 1/(15000 * 2048) seconds. For the i-th numerical value, the subcarrier spacing 405 may be 15 * 2 ⁱ , and the effective OFDM symbol length is 2048 * 2 ^-i * Ts. This can provide a character length of 2048 * 2 ^-i * Ts + CP length (for example, 160 * 2 ^-i *Ts or 144 * 2 ^-i * Ts). In other words, the subcarrier spacing of the i+1 th numerical value is twice that of the i th numerical value, and the symbol length of the i+1 th numerical value is half of the symbol length of the i th numerical value. On FIG. 4 shows four numerical values, but the system may support a different number of numerical values. In addition, the system should not support all numerical values from 0th to Ith, i=0, 1, …, I.

[00232] In Fig. 5 shows examples of subframe structures for the numerical values 501 shown in FIG. 4. Considering that the interval 283 includes N ^DL _symb (or N ^UL _symb ) = 7 symbols, the length of the interval i + 1st numerical value 501 is half of the i th numerical value 501, and ultimately the number of intervals 283 in a subframe (i.e., 1 ms) becomes double. It may be noted that the radio frame may include 10 subframes, and the length of the radio frame may be 10 ms.

[00233] In Fig. 6 shows examples of slots 683 and sub-slots 607. If sub-slot 607 is not configured by a higher layer, UE 102 and eNB/gNB 160 can only use slot 683 as a scheduler. More specifically, a given transport block may be allocated to slot 683. If sub-slot 607 is configured with a higher layer, UE 102 and eNB/gNB 160 may use sub-slot 607 as well as slot 683. Sub-slot 607 may include one or more OFDM symbols. The maximum number of OFDM symbols that make up sub-slot 607 may be N ^DL _symb -l (or N ^UL _symb -l).

[00234] The length of the sub-interval can be configured through higher layer signaling. In an alternative embodiment, the sub-slot length may be indicated by a physical layer control channel (eg, DCI format).

[00235] Sub-slot 607 may start with any character in slot 683, as long as it does not conflict with a control channel. There may be restrictions on the length of the mini-span depending on the restrictions on the start position. For example, a subslot 607 of length N ^DL _symb -l (or N ^UL _symb -l) may start at the second symbol in interval 683. The starting position of subslot 607 may be indicated by a physical layer control channel (eg, DCI format). In an alternative embodiment, the starting position of the sub-slot 607 may be determined from information (e.g., search space index, blind decode applicant index, frequency and/or time resource indices, physical RB (PRB) index, control channel element index, channel element aggregation level control, antenna port index, etc.) of the physical layer control channel that schedules data on the corresponding sub-slot 607.

[00236] In cases where sub-slot 607 is configured, a given transport block may be allocated to slot 683, sub-slot 607, aggregated sub-slots 607, or aggregated sub-slot(s) 607 and slot 683. This block may also be a block for generating bits HARQ-ACK.

[00237] In FIG. 7 shows examples of scheduling timeline 709. For normal DL scheduling timeline 709a, DL control channels are mapped to the start portion of slot 783a. DL control channels 711 schedule shared DL channels 713a in the same slot 783a. HARQ-ACKs for shared DL channels 713a (i.e., HARQ-ACKs each indicating whether a transport block was successfully detected on each shared DL channel 713a) are reported on UL control channels 715a at a later interval 783b. In this case, this interval 783 may contain a DL transmission or a UL transmission.

[00238] For normal UL scheduling timeline 709b, DL control channels 711b are mapped to the start portion of slot 783c. DL control channels 711b schedule shared UL channels 717a in later slot 783d. In these cases, the timing (time offset) between DL slot 783c and UL slot 783d may be fixed or configured via higher layer signaling. In an alternative embodiment, this may be indicated by a physical layer control channel (eg, a DL assignment DCI format, a UL grant DCI format, or another DCI format, such as a common UE signaling DCI format that can be monitored in a common search space).

[00239] For the offline base DL scheduling timeline 709c, the DL control channels 711c are mapped to the start portion of slot 783e. DL control channels 711c schedule shared DL channels 713b in the same slot 783e. HARQ-ACKs for shared DL channels 713b are reported on UL control channels 715b that are mapped at the end of slot 783e.

[00240] For the offline base DL scheduling timeline 709d, the DL control channels 711d are mapped to the start portion of slot 783f. DL control channels 711d schedule shared DL channels 717b in the same slot 783f. In these cases, interval 783f may comprise DL and UL portions, and a guard interval may be provided between DL and UL transmissions.

[00241] The use of the offline slot can be done by configuring the offline slot. In an alternative embodiment, the use of an autonomous slot can be done with a sub-slot configuration. In yet another alternative embodiment, the use of the autonomous slot can be done with a shortened physical channel configuration (eg, PDSCH, PUSCH, PUCCH, etc.).

[00242] In FIG. 8 shows examples of DL control channel monitoring areas. One or more sets of PRBs may be configured to monitor the DL control channel. In other words, the frequency domain control resource set is a set of PRBs in which the UE 102 attempts to blindly decode the downlink control information, where the PRBs may or may not be frequency contiguous, the UE 102 may have one or more control resource sets, and one DCI message may reside in one control resource set. In the frequency domain, the PRB is the size of the resource unit (which may or may not include DM-RS) for the control channel. The shared DL channel may start with a later OFDM symbol than the one(s) that transmit(s) the detected DL control channel. In an alternative embodiment, the shared DL channel may start with (or earlier) an OFDM symbol that is the last OFDM symbol carrying the detected DL control channel. In other words, dynamic reuse of at least a portion of resources in control resource sets for data of the same or different UE 102 can be supported, at least in the frequency domain.

[00243] In FIG. 9 shows examples of a DL control channel composed of more than one control channel element. If the control resource set spans a plurality of OFDM symbols, the control channel applicant may be associated with a plurality of OFDM symbols, or may be associated with a single OFDM symbol. One DL control channel element may be mapped to REs defined by one PRB and one OFDM symbol. If more than one DL control channel element is used to transmit one DL control channel, aggregation of DL control channel elements can be performed.

[00244] The number of aggregated DL control channel elements is called the DL control channel element aggregation level. The DL control channel element aggregation level may be 1 or 2 to the power of an integer. gNB 160 may inform UE 102 which control channel applicants are associated with each subset of OFDM symbols in the control resource set. If one DL control channel is associated with one OFDM symbol and does not cover a plurality of OFDM symbols, the DL control channel elements are aggregated within the OFDM symbol, namely, the plurality of DL control channel elements in the OFDM symbol are aggregated. Otherwise, DL control channel elements in different OFDM symbols may be aggregated.

[00245] In FIG. 10 shows examples of UL control channel structures. The UL control channel may be mapped to REs defined as PRB and interval in the frequency and time domains, respectively. This UL control channel may be referred to as long format (or simply 1st format). The UL control channels may be mapped to REs in limited OFDM symbols in the time domain. This may be referred to as the short format (or simply the 2nd format). Short format UL control channels can be mapped to REs in one PRB. In an alternative embodiment, short format UL control channels may be mapped to REs in multiple PRBs. For example, interleaved mapping can be applied, namely the UL control channel can be mapped to every N PRBs (eg, 5 or 10) within the system bandwidth.

[00246] In FIG. 11 is a block diagram illustrating one implementation of gNB 1160. gNB 1160 may include an upper layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and transmitter 1129 PDSCH. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

[00247] The higher layer processor 1123 may control the behavior of the physical layer (DL transmitter and UL receiver) and provide higher layer parameters to the physical layer. The higher layer processor 1123 may receive transport blocks from the physical layer. The higher layer processor 1123 may send/receive higher layer messages such as an RRC message and a MAC message to or from a higher layer UE. Upper layer processor 1123 may provide PDSCH transmitter transport blocks and provide PDCCH transmitter transmission parameters related to transport blocks.

[00248] The DL transmitter 1125 may multiplex the downlink physical channels, the downlink physical signals (including the reservation signal) and transmit them via the transmit antennas 1131. The UL receiver 1133 may receive the multiplexed uplink physical channels and the uplink physical signals via receive antennas 1131 and demultiplex them. The PUCCH receiver 1135 may provide a higher UCI processor 1123 . The PUSCH receiver 1137 may provide the transport blocks received by the higher layer processor 1123.

[00249] In FIG. 12 is a block diagram illustrating one implementation of UE 1202. UE 1202 may include an upper layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. UL transmitter 1251 may include a PUCCH transmitter 1253 and transmitter 1255 PUSCH. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[00250] The higher layer processor 1223 may control the behavior of the physical layer (UL transmitter and DL receiver) and provide higher layer parameters to the physical layer. Higher layer processor 1223 may receive transport blocks from the physical layer. The higher layer processor 1223 may send/receive higher layer messages such as an RRC message and a MAC message to or from the higher layer UE. Higher layer processor 1223 may provide PUSCH transmitter transport blocks and provide UCI PUCCH transmitter 1253.

[00251] The DL receiver 1243 may receive the multiplexed downlink physical channels and downlink physical signals via the receive antennas 1231 and demultiplex them. The PDCCH receiver 1245 may provide a higher DCI processor 1223 . The PDSCH receiver 1247 may provide transport blocks received by higher layer processor 1223.

[00252] It should be noted that the names of the physical channels described herein are given as examples. Other names may be used such as "NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH", "New Generation PDCCH (G), GPDSCH, GPUCCH and GPUSCH" or the like.

[00253] In FIG. 13 shows several examples of the long PUCCH duration structure. In the example shown in FIG. 13(a), the long PUCCH covers the entire full UL interval.

[00254] In the example shown in FIG. 13(b), the long PUCCH spans a plurality of full UL slots.

[00255] In the example shown in FIG. 13(c), the long PUCCH spans the entire oriented UL slot.

[00256] In the example shown in FIG. 13(d), the long PUCCH spans the entire oriented UL slot and one or more consecutive full UL slots.

[00257] In the example shown in FIG. 13(e), the long PUCCH spans some symbols until the end of the oriented UL slot or the entire UL slot.

[00258] In the example shown in FIG. 13(f), a long PUCCH spans some symbols until the end of a oriented UL slot or a full UL slot and one or more consecutive full UL slots.

[00259] In the example shown in FIG. 13(g), the long PUCCH spans some symbols of a oriented UL slot or a full UL slot.

[00260] In the example shown in FIG. 13(h), the long PUCCH starts at the middle of an oriented UL slot or a full UL slot. The long PUCCH spans one or more consecutive full UL slots and ends in the middle of the full UL slot.

[00261] In Fig. 14 shows examples of two demodulation reference signals (DMRS) 1401 for every 7 symbols for normal cyclic prefix (NCP) or 6 symbols for extended cyclic prefix (ECP). The first DMRS pattern 1403 (pattern 1) contains 2 RSs in every 7 or 6 symbols. In such a pattern, the long PUCCH format has 2 DMRS 1401 in every 7 symbols for normal CP (NCP) and 2 DMRS 1401 in every 6 symbols for extended CP (ECP) within the interval.

[00262] The first example (a) shows the DMRS pattern 1 1403a for a normal cyclic prefix (CP). The second example (b) shows the DMRS template 1 1403b for the extended CP.

[00263] In Fig. 15 shows examples of the minimum number of symbols for a long PUCCH. In the example shown in FIG. 15(a), X=3 if the long PUCCH covers the end of the interval. In the example shown in FIG. 15(b), X=4 if the long PUCCH can start/end on any symbol in the interval.

[00264] In Fig. 15 shows symbols that are not used or allocated for the long PUCCH. The remaining symbols (including the DMRS symbol) are allocated to the long PUCCH. Thus, in FIG. 15(a) shows a long PUCCH in the last 3 symbols. On FIG. 15(b) shows a long PUCCH allocated in the middle of the 2nd to 5th symbol interval.

[00265] In Fig. 16 shows examples of one DMRS 1601 in every 7 symbols for NCP or 6 symbols for ECP. The second DMRS pattern (pattern 2) 1603 includes one RS every 7 or 6 symbols. In such a pattern, the long PUCCH format has 1 DMRS 1601 in every 7 symbols for normal CP (NCP) and 1 DMRS 1601 in every 6 symbols for extended CP (ECP) within the interval.

[00266] The first example (a) shows a DMRS pattern 2 1603a for a normal cyclic prefix (CP). The second example (b) shows the DMRS template 2 1603b for the extended CP.

[00267] In FIG. 17 shows fixed hopping applicants for PUCCH based on fixed DMRS templates. In the first example, 2 DMRS symbols may be in every 7 symbols for a normal CP. In the second example, 2 DMRS symbols may be in every 7 symbols for extended CP. In the third example, 1 DMRS symbol may be in every 7 symbols for a normal CP. In the fourth example, 1 DMRS symbol may be in every 7 symbols for extended CP.

[00268] Fixed candidate hop locations are also shown in FIG. 17. Depending on the start and end symbols of the long PUCCH, only 1 frequency hopping may be supported in an interval. The hop location may be determined based on the closest location to the middle of the length of the long PUCCH of N symbols. In other words, the hop location may be determined based on the nearest fixed hop location with respect to the end of the Xth symbol, where X=floor(N /2) [or ceil(N/2)].

[00269] In Fig. 18 shows examples of PUCCH DMRS base blocks at a frequency hopping site. Showing PUCCH from 2 to 7 characters. In one configuration, the PUCCH may contain 1 DMRS. In another configuration, the PUCCH may contain 2 DMRS. The location of the DMRS may be determined for each hopping site based on the basic structures of different length building blocks. Since the duration of a long PUCCH in an interval may vary between 4-14 symbols, in the case of frequency hopping, each frequency hopping position may occupy 2 to 7 symbols.

[00270] Each hop may contain 1 or 2 DMRS. For a single hop length greater than or equal to 4 symbols, 1 or 2 DMRS at the hop site can be configured with higher layer signaling.

[00271] For an interval with 6 symbols for an extended CP or 7 symbols for a normal CP, if frequency hopping is not configured or supported, the long PUCCH may be configured with 1 or 2 DMRS according to the pattern in the base blocks. For a normal CP in a long PUCCH, structures with 4-7 symbols can be applied. For an extended CP in a long PUCCH, 4-6 symbol structures can be applied. The Long PUCCH may be configured with 1 DMRS symbol or 2 DMRS symbols.

[00272] When configuring or supporting frequency hopping, the location of the hopping may be determined in the middle of a given long PUCCH with a length of N symbols, where N is greater than or equal to 4 and less than or equal to the number of symbols in the interval. Frequency hopping may occur at the end of the Xth symbol, where X=floor(N/2) or ceil(N/2). The DMRS positions are then determined based on the length of each frequency hop from the basic building blocks of each length and the number of DMRSs configured for each frequency hop, if applicable. Basic blocks of 2-4 symbol structures can be applied in each frequency hop. On FIG. 18 shows hop locations for a 4-7 symbol long PUCCH duration, if configured. If frequency hopping is configured for a long PUCCH, two DMRSs are required.

[00273] For an interval with 12 symbols for extended CP or 14 symbols for normal CP, if the length of the long PUCCH is less than 6 symbols or equal to 6 symbols for extended CP, or less than 7 symbols or equal to 7 symbols for normal CP, use the same method, as described above. In other words, if frequency hopping is not configured or supported, the long PUCCH may be configured with 1 or 2 DMRS according to the pattern in the base blocks. For a normal CP in a long PUCCH, structures with 4-7 symbols can be applied. For an extended CP in a long PUCCH, 4-6 symbol structures can be applied. The Long PUCCH may be configured with 1 DMRS symbol or 2 DMRS symbols.

[00274] When configuring or supporting frequency hopping, the location of the hopping is determined in the middle of a given long PUCCH with a length of N symbols, where N is greater than or equal to 4 and less than or equal to the number of symbols in the interval. Frequency hopping may occur at the end of the Xth symbol, where X=floor(N/2) or ceil(N/2). The DMRS positions are then determined based on the length of each frequency hop from the basic building blocks of each length and the number of DMRSs configured for each frequency hop, if applicable. Basic blocks of 2-4 symbol structures can be applied in each frequency hop. On FIG. 18 shows hop locations for a 4-7 symbol long PUCCH duration, if configured. If frequency hopping is configured for a long PUCCH, two DMRSs are required.

[00275] If the length of the long PUCCH is greater than 6 symbols for an extended CP or greater than 7 symbols for a normal CP, the hop location may first be determined in the middle of a given long PUCCH of length N symbols, where N is greater than or equal to 6 for an extended CP and greater than 7 for normal CP, and less than or equal to the number of characters in the interval. Frequency hopping may occur at the end of the Xth symbol, where X=floor(N/2) or ceil(N/2). The DMRS positions are then determined based on the length of each frequency hop from the basic building blocks of each length and the number of DMRSs configured for each frequency hop, if applicable. Basic blocks of 4-7 symbol structures can be applied in each frequency hop. It should be noted that the same structure can be applied whether or not frequency hopping is configured.

[00276] This method provides optimal DMRS locations for all long PUCCH durations between 4-14 symbols. Using this method, the long PUCCH may be included in one slot or in consecutive symbols from multiple slots. It should be noted that frequency hopping may be mandatory for all long PUCCH lengths in an interval.

[00277] This method can be used for DMRS location/pattern regardless of whether long PUCCH frequency hopping is configured. If frequency hopping is not configured, one of two approaches can be applied. According to one approach, for any long PUCCH lengths between 4-14 symbols, the same DMRS position is determined as if frequency hopping was configured. According to another approach, if the duration of the long PUCCH is within 4-7 symbols inclusive, the position of the DMRS can be determined using the single hop pattern indicated in FIG. eighteen.

[00278] In Fig. 19A and 19B show examples of DMRS patterns for various durations. In one case, the long PUCCH may be configured with 1 DMRS symbol at the hop site. Otherwise, a long PUCCH may be configured with 2 DMRS symbols at the hop site. DMRS patterns and hop location for DMRS 1 or 2 are shown for long PUCCH duration values.

[00279] In FIG. 19A for a PUCCH with a length of 4 to 7 symbols, with only one DMRS, frequency hopping is not supported as shown on the left side with 1 DMRS at the frequency hop. With a PUCCH length of 4 to 7 symbols and having two DMRS symbols, frequency hopping can be supported at a given location, as shown on the right side with 2 DMRS at a frequency hop. It should be noted that in this case, when frequency hopping is applied, only 1 DMRS can be present at each hop location.

[00280] In Fig. 20 shows examples of RS patterns with frequency division multiplexing (FDM) between UEs for two DMRS in every 7 symbols for NCP. Different UEs 102 are assigned different RS patterns that do not overlap with those of other UEs 102. FIG. 20 shows several examples of RS multiplexing for different UEs 102 using pattern 1, in which two RS symbols are used in every 7 symbols for NCP. Different UEs 102 are assigned different subcarriers for RS transmission in two DMRS symbols. In these figures, each cross-hatched portion represents a DMRS of a different UE.

[00281] In embodiment (a), UE 102 may be configured with 2 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 6 UEs 102.

[00282] In embodiment (b), UE 102 may be configured with 3 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 4 UEs 102.

[00283] In embodiment (c), UE 102 may be configured with 4 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 3 UEs 102.

[00284] In embodiment (d), the UE may be configured with 6 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 2 UEs 102.

[00285] In Fig. 21 shows examples of RS patterns with inter-UE FDM for two DMRS in every 6 symbols for ECP. Different UEs 102 are assigned different RS patterns that do not overlap with those of other UEs 102. FIG. 21 shows several examples of RS multiplexing for different UEs 102 using pattern 1, in which two RS symbols are used in every 6 symbols for NCP. Different UEs 102 are assigned different subcarriers for RS transmission in two DMRS symbols.

[00286] In embodiment (a), UE 102 may be configured with 2 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 6 UEs 102.

[00287] In embodiment (b), UE 102 may be configured with 3 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 4 UEs 102.

[00288] In embodiment (c), UE 102 may be configured with 4 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 3 UEs 102.

[00289] In embodiment (d), the UE may be configured with 6 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 2 UEs 102.

[00290] In FIG. 22 shows examples of an inter-UE FDM offset RS pattern for two DMRS in every 7 symbols for NCP. For CP-OFDM-based transmission with 2 RS symbols in every 7 symbols for NCP and every 6 symbols for ECP, the RS signal may also be placed at the beginning. Thus, an RS offset pattern can be applied.

[00291] In embodiment (a), UE 102 may be configured with 2 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 6 UEs 102.

[00292] In embodiment (b), UE 102 may be configured with 3 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 4 UEs 102.

[00293] In embodiment (c), UE 102 may be configured with 4 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 3 UEs 102.

[00294] In embodiment (d), the UE may be configured with 6 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 2 UEs 102.

[00295] In Fig. 23 shows examples of a long PUCCH with one DMRS for every 7 symbols for NCP. The same FDM combinations can be used in the pattern with one RS symbol in every 7 symbols for NCP and every 6 symbols for ECP. In this case, the position of the RS should be the same as in DFT-S-OFDM-based transmission, and no RS position shift is required. On FIG. 23 shows several examples of a long PUCCH with one DMRS in every 7 symbols for NCPs with different UE multiplexing capabilities.

[00296] In embodiment (a), UE 102 may be configured with 2 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 6 UEs 102.

[00297] In embodiment (b), UE 102 may be configured with 3 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 4 UEs 102.

[00298] In embodiment (c), UE 102 may be configured with 4 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 3 UEs 102.

[00299] In embodiment (d), the UE may be configured with 6 subcarriers for RS transmission within each DMRS symbol. Thus, the RB can be multiplexed using 2 UEs 102.

[00300] In Fig. 24 shows examples of DMRS extraction in the frequency domain. On FIG. 24 shows several examples of DMRS spreading in the frequency domain. In the first example, there are 2 RS per RB. In the second example, there are 3 RS per RB. In the third example, there are 4 RS per RB.

[00301] In Fig. 25 illustrates examples of UE multiplexing using various DMRS patterns. On FIG. 25 shows several examples in which four UEs 102 are multiplexed using different DMRS patterns. On FIG. 25, each cross-hatched area represents a DMRS pattern of a given UE 102. In FIG. 25, each cross-hatched area represents a DMRS pattern of a given UE 102.

[00302] In the first example, there are two RSs per RB in the frequency domain. In the second example, there are three RSs per RB in the frequency domain. In the third example, there are four RSs per RB in the frequency domain.

[00303] In Fig. 26 shows examples of frequency hopping for long PUCCH formats. Long PUCCH frequency hopping can be configured to provide frequency diversity. In this case, separate PUCCH regions or subbands must be configured for UE 102, and PUCCH may be transmitted in frequency hopping in different regions/subbands, as shown in FIG. 26.

[00304] The first example (a) illustrates frequency hopping at the interval level or every 7 symbols for NCP. The second example (b) illustrates frequency hopping within 7 symbols for NCP.

[00305] In FIG. 27 shows examples of patterns with separate DMRS in each symbol. UE multiplexing within a RB may be reduced or eliminated. In addition, DMRS with a length of 1 short PUCCH symbol can be used in each symbol. On FIG. 27 shows reference signal pattern structures for 2 RS, 3 RS, 4 RS and 6 RS per RB. For each RS setting, at least two patterns can be defined, designated pattern 1 and pattern 2.

[00306] In Fig. 28 illustrates various components that can be used in UE 2802. UE 2802 described in connection with FIG. 28 may be implemented in accordance with UE 102 described in connection with FIG. 1. UE 2802 includes a processor 2803 that controls the operation of UE 2802. Processor 2803 may also be referred to as a central processing unit (CPU). Memory 2805, which may include Read Only Memory (ROM), Random Access Memory (RAM), a combination thereof, or any type of device that can store information, provides processor 2803 with instructions 2807a and data 2809a. The memory portion 2805 may also include a non-volatile random access memory (NRAM). Instructions 2807b or data 2809b may also reside in processor 2803. Instructions 2807b and/or data 2809b loaded into processor 2803 may also include instructions 2807a and/or data 2809a from memory 2805 that have been loaded for execution or processing by the processor. 2803. Instructions 2807b may be executed by processor 2803 to implement the methods described above.

[00307] UE 2802 may also include a housing that contains one or more transmitters 2858 and one or more receivers 2820 to enable data transmission and reception. Transmitter(s) 2858 and receiver(s) 2820 may be combined into one or more transceivers 2818. Attached to the housing are one or more antennas 2822a-n that are electrically coupled to transceiver 2818.

[00308] The various components of UE 2802 are connected together via a bus system 2811, which, in addition to a data bus, may include a power bus, a control signal bus, and a status signal bus. However, for clarity, various tires are illustrated in FIG. 28 as a bus system 2811. UE 2802 may also include a digital signal processor (DSP) 2813 for use in signal processing. UE 2802 may also include a communication interface 2815 that provides user access to functions of UE 2802. UE 2802 illustrated in FIG. 28 is a functional block diagram, not a list of specific components.

[00309] In Fig. 29 illustrates various components that can be used in gNB 2960. gNB 2960 described in connection with FIG. 29 may be implemented in accordance with gNB 160 described in connection with FIG. 1. gNB 2960 includes a processor 2903 that controls the operation of gNB 2960. Processor 2903 may also be referred to as a central processing unit (CPU). Memory 2905, which may include Read Only Memory (ROM), Random Access Memory (RAM), a combination thereof, or any type of device that can store information, provides processor 2903 with instructions 2907a and data 2909a. The memory portion 2905 may also include a non-volatile random access memory (NRAM). Instructions 2907b or data 2909b may also reside in processor 2903. Instructions 2907b and/or data 2909b loaded into processor 2903 may also include instructions 2907a and/or data 2909a from memory 2905 that have been loaded for execution or processing by the processor. 2903. Instructions 2907b may be executed by processor 2903 to implement the methods described above.

[00310] gNB 2960 may also include a housing that contains one or more transmitters 2917 and one or more receivers 2978 to enable data transmission and reception. Transmitter(s) 2917 and receiver(s) 2978 may be combined into one or more transceivers 2976. Attached to the housing are one or more antennas 2980a-n that are electrically coupled to transceiver 2976.

[00311] The various components of the gNB 2960 are connected together via a bus system 2911, which, in addition to a data bus, may include a power bus, a control signal bus, and a status signal bus. However, for clarity, various tires are illustrated in FIG. 29 as a 2911 bus system. gNB 2960 may also include a digital signal processor (DSP) 2913 for use in signal processing. gNB 2960 may also include a communications interface 2915 that provides user access to the functions of gNB 2960. gNB 2960 illustrated in FIG. 29 is a functional block diagram, not a list of specific components.

[00312] In Fig. 30 is a block diagram illustrating one embodiment of a UE 3002 in which systems and methods for a long PUCCH slot structure for 5G NR operation may be implemented. UE 3002 includes a transmit means 3058, a receive means 3020, and a control means 3024. The transmit means 3058, the receive means 3020, and the control means 3024 may be configured to perform one or more of the functions described in connection with FIG. 1. In FIG. 28 above illustrates one example of a specific structure of the device shown in FIG. 30. To perform one or more of the functions shown in FIG. 1, various other structures may be implemented. For example, a DSP may be implemented in software.

[00313] In Fig. 31 is a block diagram illustrating one implementation of gNB 3160 in which systems and methods for a long PUCCH slot structure for 5G NR operation can be implemented. gNB 3160 includes a transmit means 3117, a receive means 3178, and a control means 3182. The transmit means 3117, the receive means 3178, and the control means 3182 may be configured to perform one or more of the functions described in connection with FIG. 1. In FIG. 29 above illustrates one example of a specific structure of the device shown in FIG. 31. To perform one or more of the functions shown in FIG. 1, various other structures may be implemented. For example, a DSP may be implemented in software.

[00314] In FIG. 32 is a flowchart illustrating a method 3200 for implementing a long PUCCH slot structure for 5G NR. Method 3200 may be implemented by UE 102. UE 102 may determine 3202 the format and configuration of an uplink control channel (PUCCH) based on signaling from gNB 160. For example, determining the format and configuration of an uplink control channel (PUCCH) may include selecting a long PUCCH format that supports more than 2 UCI payload bits.

[00315] For a long PUCCH, a format may be used that includes a signal, a plurality of resource blocks (RBs), a reference symbol pattern (RS), and/or orthogonal sequences for RS symbols and data symbols, and/or one or more resource regions management. RS symbols may be allocated in the time domain and orthogonal sequences applied to UCI data in the time domain or frequency domain.

[00316] UE 102 may determine (3204) DMRS locations in the configured PUCCH. The DMRS of the long PUCCH may occupy fixed locations in the slot structure or relative to the start symbol of the long PUCCH. When configuring or supporting frequency hopping, the hopping location is also fixed based on the DMRS structure.

[00317] The frequency hopping may be mandatory or configurable, and the DMRS of the long PUCCH may be determined for each frequency hopping based on basic building blocks. The long PUCCH may include one or two basic building blocks of the same length or different lengths, with each basic building block configured with 1 or 2 DMRS when using a 4-7 symbol long basic building block pattern. The hopping position may be determined in the middle of a given long PUCCH, and the DMRS positions at each hopping site are determined based on the hopping distance from the base building blocks.

[00318] UE 102 may determine 3206 methods for multiplexing uplink control information (UCI) for the configured PUCCH. A common structure can be used for RS location and UCI multiplexing methods. The RS symbols may be allocated in the time domain, and orthogonal sequences may be applied to UCI data in the time domain or frequency domain.

[00319] When using CP-OFDM, RS symbols can be extracted in the frequency domain, and orthogonal sequences can be applied to UCI data in the time domain or frequency domain. When using CP-OFDM, orthogonal RS patterns can be applied for UE multiplexing.

[00320] UE 102 may determine 3208 a control channel resource for UCI feedback. UE 102 may transmit 3210 UCI on the selected channel.

[00321] In Fig. 33 is a flowchart illustrating a method 3300 for implementing a long PUCCH slot structure for 5G NR. Method 3300 may be implemented by base station (gNB) 160. gNB 160 may determine 3302 the format and configuration of an uplink control channel (PUCCH). For example, the uplink control channel (PUCCH) format and configurations may include a long PUCCH format that supports more than 2 UCI payload bits.

[00322] For a long PUCCH, a format may be used containing a signal, a number of resource blocks (RBs), a reference symbol pattern (RS), and/or orthogonal sequences for RS symbols and data symbols, and/or one or more control resource regions. In the long PUCCH, a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM) signal can be used.

[00323] gNB 160 may determine (3304) DMRS locations in the configured PUCCH. gNB 160 may determine (3306) uplink control information (UCI) multiplexing methods for the configured PUCCH. gNB 160 may determine 3308 a control channel resource for UCI feedback. This may be done as described in connection with FIG. 32.

[00324] gNB 160 may receive (3310) UCI feedback on the selected control channel. UE 102 determines the control channel used to feedback uplink control information (UCI) and the control channel resource for UCI feedback based on the signaling from gNB 160.

[00325] The term "computer-readable media" refers to any available media that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a computer and/or processor-readable medium that is non-volatile and tangible. By way of example, and not limitation, a computer-readable or processor-readable medium can be a RAM, ROM, EEPROM, CD-ROM, or other optical disk drive, a magnetic disk drive, or other magnetic storage devices, or any other medium that can be be used to carry or store the required program code in the form of instructions or data structures that can be accessed by a computer or processor. In this document, the term "disc" refers to a disc (disc) that reproduces data optically using lasers (e.g. compact disc (CD), laser disc, optical disc, digital versatile disc (DVD) and Blu-ray® disc. ), and to a disk (disk), which usually reproduces data in a magnetic way (for example, a floppy disk).

[00326] It should be noted that one or more of the methods described herein may be implemented and/or performed using equipment. For example, one or more of the methods described herein may be implemented and/or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[00327] Each of the methods described herein includes one or more steps or steps to implement the described method. The steps and/or steps of the method can be interchanged with each other and/or combined into one step within the scope defined by the claims. In other words, if a particular order of steps or actions is not required for proper operation of the described method, the order and/or use of certain steps and/or actions can be changed without deviating from the scope defined by the claims.

[00328] It should be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes, and variations may be made to the arrangement, operation, or details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

[00329] A program executing on gNB 160 or UE 102 in accordance with the described systems and methods is a program (a program that assumes the operation of a computer) that controls the CPU, etc. in such a way as to perform a function in accordance with the described systems and ways. At the same time, the information that these devices process is temporarily stored in RAM during processing. The information is then stored on various ROMs or HDDs and read by the CPU for modification or writing as needed. The recording medium on which the program is stored can be any of semiconductor devices (for example, ROM, non-volatile memory card, etc.), optical storage devices (for example, DVD, MO, MD, CD, BD, etc. .), magnetic storage devices (e.g., magnetic tape, floppy disk, etc.), and the like. the function in accordance with the described systems and methods is implemented in interaction with the operating system or other application programs based on instructions from the program.

[00330] Moreover, if programs are available on the market, a program stored on a portable storage medium can be distributed or the program can be transferred to a server computer that is connected via a network such as the Internet. In this case, the storage device on the server computer is also included in the system. Moreover, some or all of gNB 160 and UE 102 in accordance with the systems and methods described above may be implemented as an LSI, which is a typical integrated circuit. Each functional block of gNB 160 and UE 102 may be individually embedded on a chip, and some or all of the functional blocks may be combined on a chip. Moreover, the technique for implementing integrated circuits is not limited to LSI, and an integrated circuit for a functional block may be implemented with a dedicated circuit or a general purpose processor. In addition, when a technology embodied in an integrated circuit replacing existing LSIs appears in the field of semiconductors, an integrated circuit to which such technology has been applied can also be used.

[00331] Moreover, each functional block or various elements of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit, which is usually an integrated circuit or a plurality of integrated circuits. Circuit capable of performing the functions described in this specification may include a general purpose processor, digital signal processor (DSP), custom or application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, circuits based on discrete components or transistor logic circuits, a discrete hardware component, or a combination of both. A general purpose processor may be a microprocessor, or in an alternative embodiment, the processor may be a conventional processor, controller, microcontroller, or state machine. The general purpose processor, or each circuit described above, may be implemented as a digital circuit, or may be implemented as an analog circuit. Additionally, when a technology embodied in an integrated circuit appears in the field of semiconductors, replacing existing integrated circuits, an integrated circuit according to this technology can also be used.

Claims (20)

1. User Equipment (UE), comprising: CPU; and a memory device in electronic communication with the processor, wherein the instructions stored in the memory device are executable for: transmitting uplink control information (UCI) using a physical uplink control channel (PUCCH) format that supports more than 2 UCI payload bits, while the demodulation reference signal (DMRS) location(s) for the PUCCH format is determined based on the PUCCH length for the PUCCH format, the PUCCH start symbol for the PUCCH format, and the frequency hopping configuration for the PUCCH format, A PUCCH with only 1 DMRS does not support frequency hopping, and a PUCCH with 2 or more DMRS supports configurable frequency hopping. 2. Base station (gNB) containing: CPU; and a memory device in electronic communication with the processor, wherein the instructions stored in the memory device are executable for: receiving uplink control information (UCI) using a Physical Uplink Control Channel (PUCCH) format that supports more than 2 UCI payload bits, while the demodulation reference signal (DMRS) location(s) for the PUCCH format is determined based on the PUCCH length for the PUCCH format, the PUCCH start symbol for the PUCCH format, and the frequency hopping configuration for the PUCCH format, PUCCH with only 1 DMRS does not support frequency hopping and PUCCH with 2 or more DMRS. 3. A method for locating a demodulation reference signal (DMRS) in a configured physical uplink control channel (PUCCH) for a user equipment (UE), comprising transmission of uplink control information (UCI) using a PUCCH format that supports more than 2 bits of UCI payload, while the DMRS location(s) for the PUCCH format is determined based on the PUCCH length for the PUCCH format, the PUCCH start symbol for the PUCCH format, and the frequency hopping configuration for the PUCCH format, PUCCH with only 1 DMRS does not support frequency hopping and PUCCH with 2 or more DMRS. 4. A method for locating a demodulation reference signal (DMRS) in a configured physical uplink control channel (PUCCH) for a base station, comprising: receiving uplink control information (UCI) using a PUCCH format that supports more than 2 UCI payload bits, while the DMRS location(s) for the PUCCH format is determined based on the PUCCH length for the PUCCH format, the PUCCH start symbol for the PUCCH format, and the frequency hopping configuration for the PUCCH format, PUCCH with only 1 DMRS does not support frequency hopping and PUCCH with 2 or more DMRS.

Images