New Radio (NR) short-duration and long-duration physical uplink control channel (PUCCH) design

Abstract

A technique for a user equipment (UE) is disclosed that is operable to encode a new radio (NR) short duration physical uplink control channel (PUCCH) for transmission to a next generation Node B (gNB). The UE may identify uplink control information (UCI) for the UE. The UE may multiplex the UCI and a pseudo-random sequence associated with a demodulation reference signal (DMRS) onto multiple subcarriers in one or more physical resource blocks (PRBs) of one or more orthogonal frequency division multiplexed (OFDM) symbols using frequency division multiplexing (FDM) at the UE. The UE may encode the UCI and the pseudo-random sequence associated with the DMRS multiplexed onto multiple subcarriers of one or more OFDM symbols for transmission to the gNB on the NR short duration PUCCH.

Description

[0001] This application is a divisional application of the Chinese invention patent application with application number 201880020924.4, filed on March 22, 2018, which entered the Chinese national phase on September 24, 2019, and invention name “New Radio (NR) Short Duration and Long Duration Physical Uplink Control Channel (PUCCH) Design”. Technical Field

[0002] The present disclosure relates to wireless communications. Background Art

[0003] A wireless system typically includes multiple user equipment (UE) devices communicatively coupled to one or more base stations (BSs). The one or more BSs may be long term evolution (LTE) evolved NodeBs (eNBs) or new radio (NR) next generation NodeBs (gNBs), which may be communicatively coupled to one or more UEs via a third generation partnership project (3GPP) network.

[0004] The next generation of wireless communication systems is expected to be unified networks / systems with the goal of meeting extremely different and sometimes conflicting performance dimensions and services. New radio access technologies (RATs) are expected to support a wide range of use cases, including enhanced mobile broadband (eMBB), massive machine type communications (mMTC), mission critical machine type communications (uMTC), and similar service types operating in the frequency range up to 100 GHz. Summary of the invention

[0005] According to one aspect of the present disclosure, a user equipment (UE) is provided, the UE being operable to encode a new radio (NR) physical uplink control channel (PUCCH) for transmission to a base station, the UE comprising: one or more processors configured to: identify uplink control information (UCI) of the UE at the UE; when the NR PUCCH is a NR long duration PUCCH, multiplex the UCI and an uplink (UL) data channel at the UE using frequency division multiplexing (FDM); when the NR PUCCH is a NR short duration PUCCH, multiplex the UCI and the UL data channel at the UE using time division multiplexing (TDM); and encode the UCI and the UL data channel at the UE for transmission to the base station on the NR PUCCH; and a memory interface configured to retrieve the UCI from a memory.

[0006] According to one aspect of the present disclosure, a method for a user equipment (UE) is provided, the method comprising: identifying, at the UE, uplink control information (UCI) for the UE to send to a base station; when a new radio (NR) physical uplink control channel (PUCCH) is a NR long duration PUCCH, multiplexing the UCI and an uplink (UL) data channel at the UE using frequency division multiplexing (FDM); when the NR PUCCH is a NR short duration PUCCH, multiplexing the UCI and the UL data channel at the UE using time division multiplexing (TDM); and encoding the UCI and the UL data channel at the UE for transmission to the base station on the NR PUCCH.

[0007] According to one aspect of the present disclosure, at least one machine-readable storage medium is provided, on which instructions are implemented, the instructions being used to encode a New Radio (NR) physical uplink control channel (PUCCH) for transmission from a user equipment (UE) to a base station, the instructions performing the following operations when executed by one or more processors at the UE: identifying uplink control information (UCI) for the UE to send to a base station; when the NR PUCCH is a NR long duration PUCCH, multiplexing the UCI and an uplink (UL) data channel at the UE using frequency division multiplexing (FDM); when the NR PUCCH is a NR short duration PUCCH, multiplexing the UCI and the UL data channel at the UE using time division multiplexing (TDM); and encoding the UCI and the UL data channel at the UE for transmission to the base station on the NR PUCCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Features and advantages of the present disclosure will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which together illustrate features of the present disclosure by way of example; and wherein:

[0009] Figure 1 A New Radio (NR) uplink control channel according to an example is shown;

[0010] Figure 2 A short physical uplink control channel (PUCCH) carrying one or two hybrid automatic repeat request acknowledgement (HARQ-ACK) bits is shown according to an example;

[0011] Figure 3 A short Physical Uplink Control Channel (PUCCH) carrying a one-bit Scheduling Request (SR) according to an example is shown;

[0012] Figure 4 shows multiplexing of a short physical uplink control channel (PUCCH) for hybrid automatic repeat request acknowledgement (HARQ-ACK) and scheduling request (SR) from different user equipments (UEs) according to an example;

[0013] Figure 5 shows a physical resource block (PRB) and subcarrier configuration for a short physical uplink control channel (PUCCH) carrying more than two uplink control information (UCI) bits according to an example;

[0014] Fig. 6A and 6B shows the performance of a short physical uplink control channel (PUCCH) structure according to an example;

[0015] Figure 7 is a table of long physical uplink control channel (PUCCH) formats according to an example;

[0016] Figure 8 A long physical uplink control channel (PUCCH) carrying one or two hybrid automatic repeat request acknowledgement (HARQ-ACK) bits is shown according to an example;

[0017] Fig.9A , 9B 9C shows a demodulation reference signal (DMRS) structure of a long physical uplink control channel (PUCCH) carrying one or two hybrid automatic repeat request acknowledgement (HARQ-ACK) bits according to an example;

[0018] Fig. 10A , 10B and 10C show a long physical uplink control channel (PUCCH) carrying a one-bit scheduling request (SR) according to an example;

[0019] Fig.11 A long physical uplink control channel (PUCCH) carrying up to tens of bits of uplink control information (UCI) according to an example is shown;

[0020] Fig. 12A , 12B and 12C show a demodulation reference signal (DMRS) structure of a long physical uplink control channel (PUCCH) carrying up to tens of bits of uplink control information (UCI) according to an example;

[0021] Fig.13Depicted are functions of a user equipment (UE) operable to encode a New Radio (NR) short duration physical uplink control channel (PUCCH) for transmission to a next generation Node B (gNB) according to an example;

[0022] Fig.14 Depicted are functions of a user equipment (UE) operable to encode a New Radio (NR) long duration physical uplink control channel (PUCCH) for transmission to a next generation Node B (gNB) according to an example;

[0023] Fig.15 A flow diagram of a machine-readable storage medium having instructions thereon for encoding a New Radio (NR) Physical Uplink Control Channel (PUCCH) for transmission from a User Equipment (UE) to a Next Generation Node B (gNB) is depicted according to an example;

[0024] Fig.16 illustrates an architecture of a wireless network according to an example;

[0025] Fig.17 A schematic diagram of a wireless device (e.g., UE) according to an example is shown;

[0026] Fig.18 An interface of a baseband circuit according to an example is shown;

[0027] Fig.19 A schematic diagram of a wireless device (e.g., UE) according to an example is shown;

[0028] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. However, it will be understood that no limitation of the scope of the technology is thereby intended. DETAILED DESCRIPTION

[0029] It should be understood that before disclosing and describing the present technology, the present technology is not limited to the specific structures, process actions or materials disclosed herein, but extends to their equivalents as recognized by those of ordinary skill in the relevant art. It should also be understood that the terms used herein are only for the purpose of describing specific examples and are not restrictive. The same reference numerals in different figures represent the same elements. The numbers provided in the flow charts and processes are for the purpose of clearly illustrating the actions and operations and do not necessarily represent a specific order or sequence.

[0030] definition

[0031] As used herein, the term "user equipment (UE)" refers to a computing device capable of wireless digital communication, such as a smartphone, a tablet computing device, a laptop computer, a multimedia device such as an iPod, or other types of computing devices that provide text or voice communications.The term "user equipment (UE)" may also be referred to as "mobile device," "wireless device," or "wireless mobile device."

[0032] As used herein, the term "base station (BS)" includes "base transceiver station (BTS)", "NodeB", "evolved NodeB (eNodeB or eNB)" and / or "next generation NodeB (gNodeB or gNB)", and refers to a device or configuration node of a mobile telephone network that wirelessly communicates with a UE.

[0033] As used herein, the terms “cellular telephone network,” “4G cellular,” “Long Term Evolution (LTE),” “5G cellular,” and / or “New Radio (NR)” refer to wireless broadband technologies developed by the 3rd Generation Partnership Project (3GPP).

[0034] Example Embodiments

[0035] An initial overview of the technical embodiments is provided below, and then specific technical embodiments are described in further detail later. This preliminary overview is intended to help readers understand the technology more quickly, but is not intended to identify the key features or essential features of the technology, nor is it intended to limit the scope of the claimed subject matter.

[0036] Mobile communications have evolved from early voice systems to today's highly complex integrated communications platforms. The next generation of wireless communication systems, fifth generation (5G) or new radio (NR) access technology, can provide information access and data sharing to a variety of users and applications. NR is expected to be a unified network / system that is designed to meet distinct and sometimes conflicting performance dimensions and services. This diverse multi-dimensional specification is driven by different services and applications. In general, NR will develop based on 3GPP LTE-Advanced and other potential new radio access technologies (RATs), which provide improved, simple and seamless wireless connectivity solutions. NR can enhance wireless connectivity and provide fast, rich content and services.

[0037] Figure 1An example of a New Radio (NR) uplink control channel is shown. The NR uplink control channel may include a long duration physical uplink control channel (PUCCH) and a short duration PUCCH within a time slot. The user equipment (UE) may use the long and short duration PUCCH to transmit uplink control information (UCI) to the NR gNB. Multiple OFDM symbols may be allocated for the long PUCCH to improve the link budget and uplink coverage of the control channel. For the long PUCCH, the OFDM symbols may employ discrete Fourier transform spread OFDM (DFT-s-OFDM), where DFT precoding is applied before the inverse DFT (IDFT) at the transmitter. The length of the long PUCCH may range from 4 DFT-s-OFDM symbols to 14 DFT-s-OFDM symbols. The long PUCCH may be multiplexed with UL data channels, such as the physical uplink shared channel (PUSCH), in a frequency division multiplexing (FDM) manner. The short PUCCH can be multiplexed with the PUSCH in a time division multiplexing (TDM) manner, and the short PUCCH can use one or two OFDM symbols. In order to accommodate the switching time and round-trip propagation delay of DL to UL and UL to DL, a guard period (GP) can be inserted between the NR physical downlink control channel (NR PDCCH) and the PUSCH.

[0038] In one example, short PUCCH and long PUCCH can have various use cases. For example, short PUCCH can be applicable to UEs close to the gNB so that short duration transmissions do not cause severe coverage issues. Short PUCCH can provide higher resource efficiency because it requires fewer resources. Due to the short duration (e.g., within one slot), short PUCCH can be used for low latency (delay) transmissions, which can support DL data reception and corresponding UL responses to short PUCCH. As another example, long PUCCH can provide coverage extension for UEs at the cell edge. The long transmission duration can increase the total received signal energy and offset the significant path loss due to the long distance to the gNB. Compared to short duration PUCCH, long PUCCH can provide enhanced immunity to inter-cell interference due to the additional DFT-s-OFDM symbols in the transmission duration.

[0039] In one configuration, various designs for NR short PUCCH are described. Each short PUCCH may carry UCI of different types or payload sizes. The NR PUCCH is designed so that the same time / frequency resources can be shared between different types of PUCCHs and between different UEs to improve the efficiency of resource usage.

[0040] In one example, with respect to a short PUCCH carrying 1-2 hybrid automatic repeat request acknowledgement (HARQ-ACK) bits, two consecutive physical resource blocks (PRBs) may be the minimum resource unit. A demodulation reference signal (DMRS) and UCI may each use a constant amplitude zero autocorrelation (CAZAC) sequence of length 12, and may be alternately multiplexed in frequency division multiplexing (FDM) on different subcarriers. In addition, multiplexing with a short SR PUCCH may be supported on a DMRS or UCI subcarrier.

[0041] In one example, a pseudo-random sequence is used for DMRS and mapped to subcarriers. Therefore, when referring to UCI multiplexed with DMRS and mapped to subcarriers, UCI is actually multiplexed to the pseudo-random sequence associated with DMRS, which is then mapped to subcarriers.

[0042] In another example, regarding different designs of short PUCCH for carrying 1-2 HARQ-ACK bits, two consecutive PRBs may be the minimum resource unit for short PUCCH. A CAZAC sequence of length 12 may be applied on even or odd subcarriers within two PRBs, and on-off keying (OOK) may be employed. In addition, multiplexing with short HARQ-ACK PUCCH may be supported on DMRS or UCI subcarriers.

[0043] In one example, regarding simultaneous transmission of HARQ-ACK and SR from the same UE, in the case where the UE sends HARQ-ACK and SR in the same time slot, a comb with SR can be used to convey HARQ-ACK modulation symbols to indicate that a valid SR as well as HARQ-ACK has been sent from the UE, and another comb is used to send DMRS for HARQ-ACK.

[0044] In one example, a set of subcarriers with even or odd indices may be referred to as an even comb or an odd comb, respectively. When the same signal waveform is repeated over a given duration, a discrete Fourier transform of the signal waveform (which is equal to a representation of the signal in the frequency domain) results in the signal being mapped on an even comb or an odd comb. Whether the signal is mapped on an even comb or an odd comb depends on whether the same signal waveform is repeated or whether a waveform replica of a symbol transition is repeated over the second half duration.

[0045] In one example, for a short PUCCH carrying tens of UCI bits, DMRS can be sent on four subcarriers per PRB (i.e., 4 subcarriers per 12 subcarriers), which can result in 1 / 3 overhead. Each UCI subcarrier can carry a quadrature phase shift keying (QPSK) symbol corresponding to a different UCI coded bit. In addition, the network configuration can support non-contiguous and continuous allocations.

[0046] In one example, in a cellular network, a UE may support UCI of various types and payload sizes. Multiple short PUCCH structures may be used to carry 1-2 bits of Hybrid ARQ Acknowledgement (HARQ-ACK), 1 bit Scheduling Request (SR), and dozens of UCI bits. When designing a short PUCCH structure, it may be considered to share time / frequency resources between different types of PUCCHs and between different UEs in order to improve resource utilization and spectrum efficiency. In addition, the short PUCCH structure may consider flexibly configuring the amount and location of PUCCH resources, depending on the UCI payload size, deployment scenario, etc.

[0047] Figure 2 An example of a short PUCCH carrying one or two HARQ-ACK bits is shown. The short PUCCH may span two PRBs, which may correspond to 24 subcarriers. The short PUCCH may carry UCI multiplexed with DMRS using FDM, where the UCI and DMRS may be in alternating subcarriers. The short PUCCH may employ binary phase shift keying (BPSK) and / or quadrature phase shift keying and a CAZAC sequence. For example, the UCI may be a BPSK / QPSK modulated CAZAC sequence of length 12, and the DMRS may be a CAZAC sequence of length 12.

[0048] In one example, if Figure 2 As shown, a short duration PUCCH structure can be used to carry 1-2 HARQ-ACK bits, which can indicate the decoding success / failure of the received DL data. The transmitted waveform can be based on cyclic prefix OFDM (CP-OFDM), which can multiplex HARQ-ACK and DMRS signals on different subcarriers. DMRS and HARQ-ACK can be multiplexed in FDM using different subcarriers alternately within two consecutive PRBs. This design can generate 1 / 2 DMRS overhead, which can provide improved performance for short PUCCH carrying 1-2 UCI bits.

[0049] In one example, two CAZAC sequences of length 12 can be applied to the HARQ-ACK and DMRS subcarriers without discrete Fourier transform (DFT) precoding. In this example, BPSK and QPSK modulation can be applied to the cases of 1 and 2 HARQ-ACK bits, respectively. The CAZAC sequence for HARQ-ACK can be modulated by BPSK or QPSK modulation symbols corresponding to the encoded HARQ-ACK bits and then mapped to 12 subcarriers. The DMRS CAZAC sequence can be mapped directly to the subcarriers without modulation. Since both sequences are low peak-to-average power ratio (PAPR) / cubic metric (CM) CAZAC sequences, by avoiding the structural combination of the waveforms generated by the HARQ-ACK and DMRS sequences, assigning different cyclic shifts to the HARQ-ACK and DMRS sequences can result in lower PAPR / CM than using the same cyclic shift for both sequences.

[0050] In one example, considering multi-user multiplexing, short HARQ-ACK PUCCH for different UEs can be multiplexed within the same PRB by assigning different cyclic shifts for CAZAC sequences to UEs. The cyclic shifts of HARQ-ACK and DMRS sequences can have a non-zero constant offset for low PAPR / CM, and the UE-specific cyclic shift value for each UE can be applied to both HARQ-ACK and DMRS sequences in addition to the constant offset. In addition, multiple groups of two PRBs for short HARQ-ACK PUCCH can be configured in distant frequency blocks, enabling the benefit of frequency and interference diversity. By utilizing the DMRS transmitted in each frequency block, the HARQ-ACK PUCCH transmitted in the distant frequency block can be coherently combined at the gNB receiver. By assigning different cyclic shifts to the PUCCH transmitted from each transmit antenna of the UE, spatial diversity can be additionally pursued.

[0051] Figure 3 An example of a short PUCCH carrying a one-bit SR is shown. In this example, a CAZAC sequence of length 12 may be applied to even or odd subcarriers within two PRBs using on-off keying (OOK). When the UE is to schedule resources for PUSCH transmission in the UL, the UE may send the sequence on the configured comb, otherwise the SR resources may remain unused.

[0052] In one example, by assigning different cyclic shifts for CAZAC sequences to different UEs, short SR PUCCHs for different UEs can be multiplexed within the same PRB. Moreover, since the short SR PUCCH can use only odd or even subcarriers, the short SR PUCCH can be multiplexed with DRMS ​​or HARQ-ACK of the short HARQ-ACK PUCCH within the same PRB on the corresponding comb. The cyclic shift offset, comb index, and PRB index can be configured in a UE-specific manner via high-layer signaling. Multiple groups of two PRBs for short SR PUCCH can also be configured in long-distance frequency blocks to enhance frequency diversity gain.

[0053] Figure 4 An example of multiplexing of short PUCCH for HARQ-ACK and SR from different UEs is shown. In this example, different cyclic shifts of the CAZAC sequence with a minimum cyclic shift offset of 3 can be assigned to each UE. Each SRPUCCH can be sent on an odd comb or an even comb only by multiplexing with the DMRS or HARQ-ACK sequence of the HARQ-ACK PUCCH. In the case where the UE happens to send HARQ-ACK and SR in the same time slot, the SR resources can be used to deliver HARQ-ACK information to indicate that a valid SR has been sent from the UE together with the HARQ-ACK. Specifically, a comb with an SR for the UE can be used to deliver HARQ-ACK modulation symbols, and another comb can be used to send DMRS for HARQ-ACK.

[0054] For example, in the case where UE 1 and UE 2 are the same UE, the HARQ-ACK modulation symbol may be carried on a CAZAC sequence with a cyclic shift of 3 on an even subcarrier that has been allocated to the SR, and the DMRS may be carried on a CAZAC sequence with a cyclic shift of 9 on an odd subcarrier that has been allocated to the DMRS. On the other hand, in the case where UE 1 and UE 4 are the same UE, the HARQ-ACK modulation symbol may be carried on a CAZAC sequence with a cyclic shift of 0 on an odd subcarrier that has been allocated to the SR, and the DMRS may be carried on a CAZAC sequence with a cyclic shift of 6 on an even subcarrier that has been allocated to the HARQ-ACK DMRS. The gNB may provide a configuration such that resources for the HARQ-ACK PUCCH and the SR PUCCH of the same UE in one slot are allocated in the same PRB.

[0055] Figure 5An example of a PRB and subcarrier configuration for a short PUCCH carrying more than two UCI bits is shown. In this example, a given PRB used to form a short PUCCH includes 12 subcarriers, where 4 of the 12 subcarriers correspond to DMRS and 8 of the 12 subcarriers correspond to UCI. In this example, 4 of the 12 subcarriers corresponding to DMRS include subcarriers 1, 4, 7, and 10 of the short PUCCH.

[0056] In one example, the UCI bits may include CSI, beam information, multiple HARQ-ACK bits, and any combination of these UCI types. DMRS and UCI may be multiplexed in FDM using different subcarriers, and DMRS may be sent on four subcarriers per PRB, resulting in a DMRS overhead of 1 / 3, which provides optimal performance.

[0057] In one example, each UCI subcarrier may carry a QPSK symbol corresponding to a different UCI coded bit. Unlike the short PUCCH used to carry 1-2 HARQ-ACK bits, no additional sequence may be applied on the UCI subcarrier, where the UCI subcarrier may carry a sequence modulated by a HARQ-ACK BPSK / QPSK symbol.

[0058] In one example of reliable performance for a short PUCCH format, technical aspects such as frequency diversity gain, channel estimation performance, and robustness under delay spread may be considered in the structure design. The structure may be designed to support up to about 20 UCI bits with a code rate of about 1 / 2. In this regard, it may be assumed that three PRBs are used for the short PUCCH format and may carry 24 QPSK symbols with 1 / 3 DMRS overhead.

[0059] about Figure 5 , various structures can be used for short PUCCH to carry up to dozens of UCI bits. For example, the first structure can adopt three consecutive PRBs with a CAZAC sequence of length 12 for DMRS across the PRBs. The second structure can adopt three consecutive PRBs with a DFT sequence of length 4 for DMRS on each PRB. The third structure can adopt three non-contiguous PRBs with a DFT sequence of length 4 for DMRS on each PRB. Among the three candidate structures, non-contiguous PRB allocation can allow for greater frequency diversity gain, on the other hand, continuous PRBs allocated with a CAZAC sequence of length 12 can provide higher channel estimation SNR and stronger robustness against inter-cellular interference.

[0060] Fig. 6A and 6BAn exemplary performance of a short PUCCH structure is shown. These evaluations have been performed for a UCI payload size of 8 bits and a channel root mean square (RMS) delay spread of 100 ns. For non-contiguous allocation, the spacing between PRBs is 48 PRBs.

[0061] like Fig. 6A As shown, under ideal channel estimation, non-continuous allocation of DMRS sequences with a length of 4 can outperform continuous allocation of sequences with lengths of 4 and 12 by about 1.5 decibels (dB). Figure 6B As shown, in the case of actual channel estimation, for a signal-to-noise ratio (SNR) greater than 2 dB, non-continuous allocation with a DMRS sequence of length 4 can outperform continuous allocation with a CAZAC of length 12, and for an SNR less than 2 dB, exhibits similar or worse performance, because the use of CAZAC of length 12 can provide more reliable channel estimation due to the combination of channel estimates of longer sequences than the case of using a DMRS sequence of length 4. In addition, in the case where the channel bandwidth is not sufficient to provide sufficient frequency diversity gain for non-continuous allocation, Figure 6B , a continuous allocation with a CAZAC sequence of length 12 can outperform a non-contiguous allocation at an increased level. Therefore, it is beneficial to enable the gNB to configure frequency resources for short PUCCH in non-contiguous blocks or continuous blocks, taking into account deployment scenarios, network bandwidth, channel load, etc. This configuration can be indicated to each UE via high-layer signaling. In the case of aperiodic CSI or HARQ-ACK transmission, dynamic indication of resource allocation via downlink control information (DCI) can also be additionally applied.

[0062] In one example, the described techniques can be directly extended to cases where the number of subcarriers, sequence lengths, and number of PRBs are different from those in the above examples.

[0063] In one configuration, various designs for NR long PUCCH are described. Each long PUCCH may carry UCI of different types or payload sizes, and the number of DMRS symbols within each PUCCH transmission may vary depending on the length of the NR PUCCH transmission.

[0064] In one example, with respect to an NR long PUCCH for carrying 1-2 bit HARQ-ACK, there may be floor(x / 2) DMRS symbols of length x for the PUCCH. In general, a floor function is a function that takes a real number x as input and provides a maximum integer less than or equal to x as output. In this example, when the PUCCH length is four symbols, two DMRS symbols may be configured in the middle. Additionally, when the PUCCH transmission changes frequency during transmission, in the case where the PUCCH length is 12 OFDM symbols, two DMRS symbols may be configured in one transmission of a PUCCH with five symbols, and three DMRS symbols may be configured in another transmission of a PUCCH with seven symbols.

[0065] In one example, for NR long PUCCH for carrying 1-bit SR, a sequence of length 12 can be mapped in each DFT-s-OFDM symbol without any DMRS symbol. PUCCH for 1-bit SR and 1-2-bit HARQ-ACK with the same PUCCH length can be multiplexed in the same PRB using different cyclic shifts of the same CAZAC sequence.

[0066] In one example, with respect to an NR long PUCCH for carrying up to tens of UCI bits, the floor(x / 3) DMRS symbols of length x for the NR PUCCH can be used to carry up to tens of UCI bits. PUCCH transmission can apply an orthogonal cover code (OCC) on the PUCCH symbols and the subcarriers within each symbol to carry different UCI modulation symbols. The length of the orthogonal cover code can vary according to the PUCCH length. In the case where the number of UCI bits exceeds a certain threshold, two or more PRBs can be configured. In the case where the PUCCH length is four symbols, one DMRS symbol can be configured in the middle. In addition, when the PUCCH transmission changes frequency during transmission, in the case where the PUCCH length is 12 OFDM symbols, one DMRS symbol can be configured in one transmission of a PUCCH with five symbols, and two DMRS symbols can be configured in another transmission of a PUCCH with seven symbols.

[0067] In one configuration, the duration of the long PUCCH may vary depending on the presence and duration of other physical channels. Figure 1As shown, the PDCCH and short PUCCH can have one OFDM symbol in duration. In another case, the short PUCCH may not exist in the time slot, and the duration of the long PUCCH may be one or more symbols. In other cases, the PDCCH or short PUCCH may have two OFDM symbols, and the duration of the long PUCCH may become shorter. Moreover, as an alternative, the duration of the time slot can be reduced by half, which can result in only half of the OFDM symbols in the time slot, and therefore, the duration of the long PUCCH can be reduced accordingly and have fewer symbols. The structure of the long PUCCH can be designed with respect to UCI and DMRS, which help the receiver recover the received signal and detect UCI, and the performance and resource efficiency of the long PUCCH are designed to be robust to changes in the duration of the long PUCCH.

[0068] In one example, multiple types of UCI may be defined in the uplink, such as HARQ-ACK, channel state information (CSI), SR, beam information (BI), etc. The UE may use PUCCH to send one or more different UCI types. The UCI combination and number of information bits carried by PUCCH may vary depending on the situation and may be configured and controlled by the network.

[0069] In one example, in order to adapt to and support various deployment scenarios, channel configurations and situations, multiple PUCCH formats may be defined. Each format may be designed taking into account, but not limited to, the target payload size and target UCI type carried by the PUCCH format, and the UCI and DMRS structure may be designed to accommodate changes in the duration of the long PUCCH.

[0070] Figure 71 is an example of a table of long physical uplink control channel (PUCCH) formats. PUCCH format 0 may correspond to a payload size of 1 bit, SR of UCI type, modulation type of OOK, one PRB, and a sequence of length 12 for each DFT-s-OFDM symbol. PUCCH format 1 may correspond to a payload size of 1 or 2 bits, HARQ-ACK of UCI type, modulation type of BPSK / QPSK, one PRB, and floor(x / 2) DMRS symbols of length x, and a sequence of length 12 for each DFT-s-OFDM symbol. PUCCH format 2 may correspond to a payload size of tens of bits, any UCI type and combination, modulation type of QPSK, about two PRBs, and floor(x / 3) DMRS symbols of length x. PUCCH format 3 may correspond to a payload size of hundreds of bits, any UCI type and combination, modulation type of QPSK, an adaptable number of PRBs, and dynamic switching between formats 2 and 3, and no intra-PRB UE multiplexing.

[0071] Figure 8 An example of a long PUCCH carrying one or two HARQ-ACK bits is shown. In this example, a long duration PUCCH format 1 for carrying 1-2 HARQ-ACK bits can indicate to the gNB the decoding success / failure of the received DL data. Figure 8 As shown, an exemplary structure of a long PUCCH can be provided for the case where the PUCCH duration w is seven DFT-s-OFDM symbols. Each DFT-s-OFDM symbol can carry a CAZAC sequence of length 12, and the sequence of UCI can be modulated by a HARQ-ACK modulation symbol. For a PUCCH carrying 1-2 UCI bits, about 1 / 2 DMRS overhead can provide favorable performance. Therefore, as Figure 8 As shown, among the seven DFT-s-OFDM symbols in the PUCCH duration, the middle three DFT-s-OFDM symbols can be used for DMRS.

[0072] In one example, in order to achieve reliable performance of PUCCH detection at the gNB receiver, it is beneficial to adjust the number of DMRS symbols according to the length of the long PUCCH. Specifically, the HARQ-ACK PUCCH can be configured so that floor(x / 2) DMRS symbols are allocated for a PUCCH of length x.

[0073] Fig.9A , 9B 9C show examples of DMRS structures for long PUCCH carrying one or two HARQ-ACK bits. Fig.9A As shown, when the PUCCH length is four DFT-s-OFDM symbols, two DMRS symbols can be configured in the middle. Fig. 9B As shown, when the PUCCH length is seven DFT-s-OFDM symbols, three DMRS symbols can be configured in the middle. Fig. 9B The configuration shown in corresponds to Figure 8 9C ). The PUCCH transmission may change frequency during transmission. In this example, two transmissions may be sent on different PRBs, which may result in greater frequency diversity gain. Two DMRS symbols may be configured in the first transmission of the PUCCH having five DFT-s-OFDM symbols, and three DMRS symbols may be configured in the next transmission of the PUCCH having seven DFT-s-OFDM symbols.

[0074] Fig. 10A , 10B 10C shows an example of a long PUCCH carrying a one-bit SR. In this example, a long duration PUCCH format 0 can be used to carry a 1-bit SR. Here, the SR PUCCH does not contain DMRS, and a sequence of length 12 can be mapped in each DFT-s-OFDM symbol. In addition, the number of DFT-s-OFDM symbols can vary according to the PUCCH length.

[0075] like Fig. 10A As shown, PUCCHs for 1-bit SR and 1-2-bit HARQ-ACK with the same PUCCH length of 4 DFT-s-OFDM symbols can be multiplexed in the same PRB using different cyclic shifts of the same CAZAC sequence (e.g., CS offset k). Fig. 10B As shown in FIG. 10A , different cyclic shifts of the same CAZAC sequence (e.g., CS offset n) can be used to multiplex 1-bit SR and 1-2-bit HARQ-ACK PUCCHs with the same PUCCH length of 7 DFT-s-OFDM symbols within the same PRB. As shown in FIG. 10C , in one example, when the PUCCH length is longer than seven DFT-s-OFDM symbols, the PUCCH transmission can change frequency during transmission. Fig. 10CAs shown, in this example, each of the two SR PUCCH transmissions can be multiplexed with a HARQ-ACK PUCCH transmission within the same PRB, with their transmission length and hopping timing aligned. In this case, the two SR PUCCH transmissions can span 12 DFT-s-OFDM symbols with intra-frequency hopping. In addition, for both HARQ-ACK and SRPUCCH, different UEs can be multiplexed within the same PRB using different cyclic shifts between PUCCH transmissions from different UEs.

[0076] In one example, for a long PUCCH carrying up to tens of UCI bits, it is important that the UE can send up to tens of UCI bits even when the PUCCH length is shorter, eg, four DFT-s-OFDM symbols.

[0077] Fig.11 An example of a long PUCCH carrying up to dozens of UCI bits is shown. In this example, long duration PUCCH format 2 can be used to carry dozens of UCI bits. PUCCH transmission can apply an orthogonal cover code (OCC) on the PUCCH symbol, and each DFT-s-OFDM symbol for UCI can carry the same group of twelve UCI modulation symbols, where the twelve UCI modulation symbols can be mapped on the corresponding twelve subcarriers within one PRB of each symbol, and the first half and the second half of the PUCCH transmission can carry different groups of twelve modulation symbols. Removing or adding a DFT-s-OFDM symbol in each half does not change the number of UCI modulation symbols carried by the PUCCH. In order to further increase the capacity of the PUCCH, two or more PRBs can be configured in a frequency-continuous or non-continuous manner when the number of UCI bits exceeds a certain threshold. Then, each PRB can carry different UCI modulation symbols, and orthogonal cover codes can be applied separately on each PRB.

[0078] In one example, for a PUCCH carrying up to tens of UCI bits, a DMRS overhead of about 1 / 3 may provide the best performance. In this regard, the PUCCH may be configured such that floor(x / 3) DMRS symbols are allocated to a PUCCH of length x.

[0079] Fig. 12A , 12B 12C and 12C show examples of DMRS structures for long PUCCHs carrying up to tens of UCI bits. In these examples, long duration PUCCH format 2 can be used to carry tens of UCI bits. Fig. 12AAs shown in FIG. 1 , when the PUCCH length is four DFT-s-OFDM symbols, a DMRS symbol can be configured in the middle. Fig. 12B As shown, when the PUCCH length is seven DFT-s-OFDM symbols, two DMRS symbols can be configured. Fig. 12C As shown, the PUCCH transmission can change frequency during transmission. In this example, the two transmissions can be sent in different PRBs, providing greater frequency diversity gain. One DMRS symbol can be configured in the first transmission of the PUCCH with four DFT-s-OFDM symbols, and two DMRS symbols can be configured in the second transmission of the PUCCH with six DFT-s-OFDM symbols. Therefore, the two transmissions can span ten DFT-s-OFDM symbols with intra-frequency hopping.

[0080] like Fig. 12A , 12B As shown in FIG. 12C , transmissions from different UEs can be multiplexed by using different orthogonal cover codes on the UCI symbols and using different cyclic shifts on the DMRS sequence. In doing so, the length of the orthogonal cover code can be changed according to the PUCCH length. For example, Fig. 12A As shown, the length of the orthogonal cover code can be 3, and for UE A and B, orthogonal cover codes 1 and 2 are allocated, and cyclic shifts n and k are used respectively. Fig. 12C As shown, in the case where frequency hopping is applied between two transmissions, the orthogonal cover code length can be adjusted according to the length of each transmission, and UE multiplexing can be performed in each transmission by assigning different orthogonal cover codes and cyclic shifts between UEs.

[0081] In one example, long duration PUCCH format 3 can be used to carry hundreds of UCI bits. For long PUCCH carrying up to hundreds of UCI bits, the structure applied to PUSCH can be used. That is, depending on the expected payload size, different numbers of PRBs can be used for PUCCH transmission. In addition, depending on the payload size, the UE can switch the PUCCH structure between format 2 and format 3.

[0082] In one configuration, techniques are described for wireless communications in a 5G NR system. A UE may transmit DMRS symbols associated with an NR PUCCH, where the NR PUCCH may be configured with different numbers of DMRS symbols depending on the length of the NR PUCCH.

[0083] In one example, the number of DMRS symbols may be the floor(x / 2) DMRS symbols of an NRPUCCH of length x carrying 1-2 bit HARQ-ACK. In another example, in the case where the PUCCH length is four symbols, two DMRS symbols may be configured in the middle. In yet another example, the PUCCH transmission may change frequency during transmission, and in the case where the PUCCH length is 12 OFDM symbols, two DMRS symbols may be configured in one transmission of a PUCCH with five symbols, and three DMRS symbols may be configured in another transmission of a PUCCH with seven symbols.

[0084] In one example, the number of DMRS symbols can be the floor(x / 3) DMRS symbols of an NRPUCCH of length x carrying up to tens of UCI bits. In another example, the PUCCH transmission can apply an orthogonal cover code on the PUCCH symbols and the subcarriers within each symbol can carry different UCI modulation symbols. In yet another example, two PRBs can be configured in the case where the number of UCI bits exceeds a certain threshold. In another example, for the case where the PUCCH length is four symbols, one DMRS symbol can be configured in the middle. In yet another example, the PUCCH transmission can change frequency during transmission, and in the case where the PUCCH length is 12 OFDM symbols, one DMRS symbol can be configured in one transmission of a PUCCH with five symbols, and two DMRS symbols can be configured in another transmission of a PUCCH with seven symbols.

[0085] like Fig.13 As shown, another example provides functionality 1300 of a user equipment (UE) operable to encode a new radio (NR) short duration physical uplink control channel (PUCCH) for transmission to a next generation Node B (gNB). The UE may include one or more processors configured to identify uplink control information (UCI) of the UE at the UE, as shown in block 1310. The UE may include one or more processors configured to multiplex the UCI and a pseudo-random sequence associated with a demodulation reference signal (DMRS) onto a plurality of subcarriers in one or more physical resource blocks (PRBs) of one or more orthogonal frequency division multiplexing (OFDM) symbols using frequency division multiplexing (FDM) at the UE, as shown in block 1320. The UE may include one or more processors configured to encode the UCI and the pseudo-random sequence associated with the DMRS at the UE for transmission to the gNB on the NR short duration PUCCH, as shown in block 1330. Additionally, the UE may include a memory interface configured to retrieve the UCI from a memory.

[0086] like Fig.14 As shown, another example provides functionality 1400 of a user equipment (UE) operable to encode a new radio (NR) long duration physical uplink control channel (PUCCH) for transmission to a next generation Node B (gNB). The UE may include one or more processors configured to identify uplink control information (UCI) of the UE at the UE, as shown in block 1410. The UE may include one or more processors configured to multiplex a UCI symbol associated with the UCI and a pseudo-random sequence symbol associated with a demodulation reference signal (DMRS) using time division multiplexing (TDM) at the UE, wherein the number of pseudo-random sequence symbols multiplexed with the UCI symbol depends on the length of the NR long duration PUCCH, as shown in block 1420. The UE may include one or more processors configured to encode the UCI symbol and the pseudo-random sequence symbol associated with the DMRS at the UE for transmission on the NR long duration PUCCH to the gNB, as shown in block 1430. Additionally, the UE may include a memory interface configured to retrieve the UCI from a memory.

[0087] like Fig.15As shown, another example provides at least one machine-readable storage medium having instructions 1500 thereon for encoding a new radio (NR) physical uplink control channel (PUCCH) for transmission from a user equipment (UE) to a next generation node B (gNB). The instructions can be executed on a machine, wherein the instructions are included in at least one computer-readable medium or a non-transitory machine-readable storage medium. When executed by one or more processors of a user equipment (UE), the instructions perform: identifying uplink control information (UCI) of the UE at the UE, as shown in block 1510. When executed by one or more processors of the UE, the instructions perform: identifying a pseudo-random sequence associated with a demodulation reference signal (DMRS) of the UE at the UE, as shown in block 1520. When executed by one or more processors of the UE, the instructions perform: when the NR PUCCH is a NR short duration PUCCH, multiplexing UCI and a pseudo-random sequence associated with a DMRS at the UE using frequency division multiplexing (FDM), wherein when the NR PUCCH is a NR short duration PUCCH, the UCI and the pseudo-random sequence associated with the DMRS are multiplexed using different subcarriers in one or more physical resource blocks (PRBs), as shown in block 1530. When executed by one or more processors of the UE, the instructions perform: when the NR PUCCH is a NR long duration PUCCH, multiplexing UCI and a pseudo-random sequence associated with the DMRS at the UE using time division multiplexing (TDM), wherein the number of pseudo-random sequence symbols associated with the DMRS depends on the length of the NR long duration PUCCH, as shown in block 1540. When executed by one or more processors of the UE, the instructions perform: encoding the multiplexed UCI and the pseudo-random sequence associated with the DMRS at the UE for transmission to the gNB via the NR PUCCH, as shown in block 1550.

[0088] Fig.17 The architecture of a network system 700 according to some embodiments is shown. System 700 is shown to include user equipment (UE) 1701 and UE 1702. UE 1701 and 1702 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device that includes a wireless communication interface.

[0089] In some embodiments, any of UEs 1701 and 1702 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communications, a sensor network, or an IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0090] UEs 1701 and 1702 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 1710, which may be, for example, an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or other types of RANs. UEs 1701 and 1702 utilize connections 1703 and 1704, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 1703 and 1704 are shown as air interfaces for achieving communicatively coupling, and may be compatible with cellular communication protocols, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a PTT over cellular (POC) protocol, a universal mobile telecommunications system (UMTS) protocol, a 3GPP long term evolution (LTE) protocol, a fifth generation (5G) protocol, a new radio (NR) protocol, etc.

[0091] In this embodiment, UE 1701 and 1702 may also directly exchange communication data via ProSe interface 1705. Alternatively, ProSe interface 1705 may be referred to as a sidelink interface including one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0092] UE 1702 is shown as being configured to access access point (AP) 1706 via connection 1707. Connection 1707 may include a local wireless connection, such as a connection compliant with any IEEE 1802.15 protocol, wherein AP 1706 may include wireless fidelity In this example, AP 1706 is shown connected to the Internet and not to the core network of the wireless system (described in further detail below).

[0093] The RAN 1710 may include one or more access nodes that enable connections 1703 and 1704. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage in a geographic area (e.g., (cellular) cells). The RAN 1710 may include one or more RAN nodes for providing macro cells, such as macro RAN nodes 1711, and one or more RAN nodes for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells), such as low power (LP) RAN nodes 1712.

[0094] Any one of the RAN nodes 1711 and 1712 may terminate the air interface protocol and may be the first point of contact for the UEs 1701 and 1702. In some embodiments, any one of the RAN nodes 1711 and 1712 may fulfill various logical functions of the RAN 1710, including but not limited to Radio Network Controller (RNC) functions such as radio carrier management, uplink and downlink dynamic radio resource management and packet scheduling, and mobility management.

[0095] According to some embodiments, UEs 1701 and 1702 may be configured to communicate with each other or with any of RAN nodes 1711 and 1712 using orthogonal frequency division multiplexing (OFDM) communication signals on a multi-carrier communication channel according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited thereto. OFDM signals may include multiple orthogonal subcarriers.

[0096] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 1711 and 1712 to the UEs 1701 and 1702, while similar techniques may be used for uplink transmissions. The grid may be a time-frequency grid (referred to as a resource grid or a time-frequency resource grid), which is a physical resource in the downlink in each time slot. This representation of the time-frequency plane is a common practice in OFDM systems, which makes it intuitive for radio resource allocation. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Several different physical downlink channels are transmitted using such resource blocks.

[0097] The physical downlink shared channel (PDSCH) may transmit user data and higher layer signaling to the UEs 1701 and 1702. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation associated with the PDSCH channel, etc. It may also inform the UEs 1701 and 1702 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to the UEs 1702 within the cell) may be performed at any of the RAN nodes 1711 and 1712 based on channel quality information fed back from any of the UEs 1701 and 1702. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UEs 1701 and 1702.

[0098] PDCCH can use control channel elements (CCE) to transmit control information. Before mapping to resource elements, PDCCH complex symbols can first be organized into four tuples, which can then be permuted using a sub-block interleaver for rate matching. Each PDCCH can be sent using one or more of these CCEs, where each CCE can correspond to nine groups of four physical resource elements called resource element groups (REGs). Four orthogonal phase shift keying (QPSK) symbols can be mapped to each REG. PDCCH can be sent using one or more CCEs, depending on the size of the downlink control information (DCI) and channel conditions. There can be four or more different PDCCH formats (e.g., aggregation levels, L=1, 2, 4, or 18) defined in LTE with different numbers of CCEs.

[0099] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. EPDCCH can be sent using one or more enhanced control channel elements (ECCE). Similar to the above, each ECCE can correspond to four physical resource elements of nine groups called enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.

[0100] The RAN 1710 is shown as being communicatively coupled to a core network (CN) 1720 via an S1 interface 1713. In an embodiment, the CN 1720 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, the S1 interface 1713 is divided into two parts: an S1-U interface 1714, which carries traffic data between the RAN nodes 1711 and 1712 and a serving gateway (S-GW) 1722, and an S1-mobility management entity (MME) interface 1715, which is a signaling interface between the RAN nodes 1711 and 1712 and the MME 1721.

[0101] In this embodiment, CN 1720 includes MME 1721, S-GW 1722, Packet Data Network (PDN) Gateway (P-GW) 1723 and Home Subscriber Server (HSS) 1724. MME 1721 can be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 1721 can manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 1724 can include a database for network users, which includes subscription-related information to support the handling of communication sessions by network entities. CN 1720 can include one or more HSS 1724, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, HSS 1724 can provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc.

[0102] The S-GW 1722 may terminate the S1 interface 1713 towards the RAN 1710 and route packets between the RAN 1710 and the CN 1720. In addition, the S-GW 1722 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0103] The P-GW 1723 may terminate the SGi interface toward the PDN. The P-GW 1723 may route packets between the EPC network 1723 and an external network such as a network including an application server 1730 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 1725. Typically, the application server 1730 may be an element that provides an application that uses IP bearer resources with a core network (e.g., a UMTS packet service (PS) domain, a LTE PS data service, etc.). In this embodiment, the P-GW 1723 is shown as being communicatively coupled to the application server 1730 via an IP communication interface 1725. The application server 1730 may also be configured to support one or more communication services (e.g., voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UEs 1701 and 1702 via CN 1720.

[0104] The P-GW 1723 may also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 1726 is a policy and charging control element of the CN 1720. In a non-roaming scenario, there may be a single PCRF associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session in the Home Public Land Mobile Network (HPLMN). In a roaming scenario with local breakout, there may be two PCRFs associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) within the HPLMN and the Visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). The PCRF 1726 may be communicatively coupled to the Application Server 1730 via the P-GW 1723. The Application Server 1730 may signal the PCRF 1726 to indicate a new service flow and select appropriate Quality of Service (QoS) and charging parameters. PCRF 1726 may provide the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by the Application Server 1730.

[0105] Fig.18Example components of a device 1800 according to some embodiments are shown. In some embodiments, the device 1800 may include at least an application circuit 1802, a baseband circuit 1804, a radio frequency (RF) circuit 1806, a front-end module (FEM) circuit 1808, one or more antennas 1810, and a power management circuit (PMC) 1812 coupled together as shown. The components of the device 1800 shown may be included in a UE or a RAN node. In some embodiments, the device 1800 may include fewer elements (e.g., the RAN node may not utilize the application circuit 1802, but may include a processor / controller to process IP data received from the EPC). In some embodiments, the device 1800 may include additional elements, such as, for example, a memory / storage, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuit may be included separately in more than one device for a cloud RAN (C-RAN) implementation).

[0106] The application circuit 1802 may include one or more application processors. For example, the application circuit 1802 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of a general-purpose processor and a special-purpose processor (e.g., a graphics processor, an application processor, etc.). The processor may be coupled to or may include a memory / storage, and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 1800. In some embodiments, the processor of the application circuit 1802 may process an IP packet received from the EPC.

[0107] The baseband circuit 1804 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1804 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuit 1806 and generate baseband signals for the transmit signal path of the RF circuit 1806. The baseband processing circuit 1804 may interact with the application circuit 1802 for generating and processing baseband signals and for controlling the operation of the RF circuit 1806. For example, in some embodiments, the baseband circuit 1804 may include a third generation (3G) baseband processor 1804a, a fourth generation (4G) baseband processor 1804b, a fifth generation (5G) baseband processor 1804c, or other baseband processors 1804d for other existing generations, being developed, or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 1804 (e.g., one or more of the baseband processors 1804a-d) may handle various radio control functions that are capable of communicating with one or more radio networks via the RF circuit 1806. In other embodiments, some or all of the functions of the baseband processors 1804a-d may be included in a module stored in the memory 1804g and may be executed via the central processing unit (CPU) 1804e. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 1804 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 1804 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

[0108] In some embodiments, the baseband circuit 1804 may include one or more audio digital signal processors (DSPs) 1804f. The audio DSP 1804f may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip or a single chipset, or provided on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuit 1804 and the application circuit 1802 may be implemented together, such as, for example, on a system on a chip (SOC).

[0109] In some embodiments, the baseband circuit 1804 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 1804 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 1804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0110] RF circuit 1806 may use modulated electromagnetic radiation through a non-solid medium to enable communication with a wireless network. In various embodiments, RF circuit 1806 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1806 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 1808 and providing baseband signals to baseband circuit 1804. RF circuit 1806 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 1804 and providing RF output signals to FEM circuit 1808 for transmission.

[0111] In some embodiments, the receive signal path of the RF circuit 1806 may include a mixer circuit 1806a, an amplifier circuit 1806b, and a filter circuit 1806c. In some embodiments, the transmit signal path of the RF circuit 1806 may include a filter circuit 1806c and a mixer circuit 1806a. The RF circuit 1806 may also include a synthesizer circuit 1806d, which is used to synthesize the frequencies used by the mixer circuit 1806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1806a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1808 based on the synthesized frequency provided by the synthesizer circuit 1806d. The amplifier circuit 1806b may be configured to amplify the down-converted signal, and the filter circuit 1806c may be a low pass filter (LPF) or a band pass filter (BPF), which is configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 1804 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some embodiments, the mixer circuit 1806a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this regard.

[0112] In some embodiments, mixer circuit 1806a of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1806d to generate an RF output signal for FEM circuit 1808. The baseband signal may be provided by baseband circuit 1804 and may be filtered by filter circuit 1806c.

[0113] In some embodiments, the mixer circuit 1806a of the receive signal path and the mixer circuit 1806a of the transmit signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1806a of the receive signal path and the mixer circuit 1806a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1806a of the receive signal path and the mixer circuit 1806a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1806a of the receive signal path and the mixer circuit 1806a of the transmit signal path may be configured for superheterodyne operation.

[0114] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited thereto. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1806 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 1804 may include a digital baseband interface to communicate with the RF circuit 1806.

[0115] In some dual-mode embodiments, separate radio IC circuits may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this regard.

[0116] In some embodiments, the synthesizer circuit 1806d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may also be applicable. For example, the synthesizer circuit 1806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0117] Synthesizer circuit 1806d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1806a of RF circuit 1806. In some embodiments, synthesizer circuit 1806d may be a fractional-N / N+1 synthesizer.

[0118] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuit 1804 or the application circuit 1802 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 1802.

[0119] The synthesizer circuit 1806d of the RF circuit 1806 may include a frequency divider, a delay locked loop ("DLL"), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay element may be configured to decompose the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0120] In some embodiments, the synthesizer circuit 1806d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some embodiments, the output frequency can be an LO frequency (fLO). In some embodiments, the RF circuit 1806 can include an IQ / polar converter.

[0121] The FEM circuitry 1808 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1810, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1806 for further processing. The FEM circuitry 1808 may also include a transmit signal path that may include circuitry configured to amplify signals provided for transmission by the RF circuitry 1806 for transmission by one or more of the one or more antennas 1810. In various embodiments, amplification by the transmit or receive signal paths may be performed only in the RF circuitry 1806, only in the FEM 1808, or in both the RF circuitry 1806 and the FEM 1808.

[0122] In some embodiments, the FEM circuit 1808 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified receive RF signal as an output (e.g., to the RF circuit 1806). The transmit signal path of the FEM circuit 1808 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by the RF circuit 1806), and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 1810).

[0123] In some embodiments, PMC 1812 can manage the power provided to baseband circuit 1804. In particular, PMC 1812 can control power selection, voltage regulation, battery charging, or DC-DC conversion. When device 1800 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 1812 can generally be included. PMC 1812 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0124] Although Fig.18 PMC 1812 is shown coupled only to baseband circuit 1804. However, in other embodiments, PMC 1812 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuit 1802, RF circuit 1806, or FEM 1808) and perform similar power management operations for the other components.

[0125] In some embodiments, the PMC 1812 may control, or be part of, various power saving mechanisms for the device 1800. For example, if the device 1800 is in the RRC_Connected state, in which it is still connected to the RAN node because it expects to receive traffic soon, it may enter a state called discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 1800 may be powered down for brief intervals, thereby saving power.

[0126] If there is no data traffic activity for an extended period of time, the device 1800 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1800 enters a very low power state, and it performs paging, in which it wakes up periodically again to listen to the network and then powers down again. The device 1800 may not receive data in this state, and in order to receive data, it may transition back to the RRC_Connected state.

[0127] An additional power saving mode may allow the device to be unavailable to the network for periods longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to access the network and may be completely powered off. Any data sent during this time will incur significant latency, assuming the latency is acceptable.

[0128] The processor of the application circuit 1802 and the processor of the baseband circuit 1804 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1804 (alone or in combination) can be used to perform layer 3, layer 2, or layer 1 functions, and the processor of the application circuit 1804 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0129] Figure 1900 shows an example interface of a baseband circuit according to some embodiments. As described above, Fig.18 The baseband circuit 1804 may include processors 1804a-1804e and a memory 1804g used by the processors. Each of the processors 1804a-1804e may include a memory interface 1904a-1904e, respectively, to send / receive data to / from the memory 1804g.

[0130] The baseband circuit 1804 may further include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 1912 (e.g., an interface for transmitting data to a memory external to the baseband circuit 1804 / an interface for receiving data from a memory external to the baseband circuit 504), an application circuit interface 1914 (e.g., an interface for transmitting data to a memory external to the baseband circuit 1804 / an interface for receiving data from a memory external to the baseband circuit 504), and a memory interface 1915 (e.g., an interface for transmitting data to a memory external to the baseband circuit 1804). Fig.18 The application circuit 1802 transmits data to / from the interface Fig.18 The application circuit 1802 receives data from the interface), the RF circuit interface 1916 (for example, Fig.18 The RF circuit 1806 transmits data to / from the interface Fig.18 an interface for receiving data from the RF circuit 1806), a wireless hardware connection interface 1918 (e.g., to a near field communication (NFC) component, Components (e.g., low power ), components and other communication components to transmit data / interface from which data is received), and a power management interface 1920 (for example, an interface for transmitting power or control signals to / from the PMC 1812).

[0131] Fig.19 Example illustrations of wireless devices such as user equipment (UE), mobile stations (MS), mobile wireless devices, mobile communication devices, tablet computers, handsets, or other types of wireless devices are provided. The wireless device may include one or more antennas configured to communicate with a node, macro node, low power node (LPN) or transmission station (such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE) or other types of wireless wide area network (WWAN) access points. The wireless device may be configured to communicate using at least one wireless communication standard (such as but not limited to 3GPP LTE, WiMAX, High Speed ​​Packet Access (HSPA), Bluetooth, and WiFi). The wireless device may communicate using a separate antenna for each wireless communication standard or a shared antenna for multiple wireless communication standards. The wireless device may communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and / or a WWAN. The wireless device may also include a wireless modem. The wireless modem may include, for example, a wireless radio transceiver and a baseband circuit (e.g., a baseband processor). In one example, the wireless modem may modulate signals transmitted by the wireless device via one or more antennas and demodulate signals received by the wireless device via one or more antennas.

[0132] Fig.19 Also provided are illustrations of microphones and one or more speakers that can be used for audio input and output of the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other types of display screens, such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive or other types of touch screen technology. An application processor and a graphics processor can be coupled to an internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input / output options to a user. The non-volatile memory port can also be used to expand the memory capacity of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using a touch screen.

[0133] Example

[0134] The following examples relate to specific technical embodiments and indicate specific features, elements, or acts that may be used or combined in implementing these embodiments.

[0135] Example 1 includes an apparatus of a user equipment (UE) operable to encode a new radio (NR) short duration physical uplink control channel (PUCCH) for transmission to a next generation Node B (gNB), the apparatus comprising: one or more processors configured to: identify uplink control information (UCI) of the UE at the UE; multiplex the UCI and a pseudo-random sequence associated with a demodulation reference signal (DMRS) onto multiple subcarriers in one or more physical resource blocks (PRBs) of one or more orthogonal frequency division multiplexing (OFDM) symbols at the UE using frequency division multiplexing (FDM); and encode the UCI and the pseudo-random sequence associated with the DMRS at the UE for transmission to the gNB in ​​the NR short duration PUCCH; and a memory interface configured to retrieve the UCI from a memory.

[0136] Example 2 includes the apparatus of Example 1, further comprising: a transceiver configured to send the UCI and the pseudo-random sequence associated with the DMRS to the gNB via the NR short duration PUCCH.

[0137] Example 3 includes the apparatus of any one of Examples 1 to 2, wherein the one or more PRBs used to form the NR short duration PUCCH include: two or more consecutive PRBs; or two or more non-consecutive PRBs.

[0138] Example 4 includes an apparatus of any one of Examples 1 to 3, wherein the prescribed PRB used to form the NR short duration PUCCH includes 12 subcarriers, wherein 4 of the 12 subcarriers correspond to the pseudo-random sequence associated with the DMRS carried in the NR short duration PUCCH, and 8 of the 12 subcarriers correspond to the UCI carried in the NR short duration PUCCH.

[0139] Example 5 includes an apparatus of any one of Examples 1 to 4, wherein the 4 subcarriers of the 12 subcarriers corresponding to the pseudo-random sequence associated with the DMRS carried in the NR short duration PUCCH include subcarriers 1, 4, 7 and 10 of the NR short duration PUCCH.

[0140] Example 6 includes the apparatus of any one of Examples 1 to 5, wherein the NR short duration PUCCH carrying the UCI and the pseudo-random sequence associated with the DMRS includes one or two OFDM symbols.

[0141] Example 7 includes an apparatus of any one of Examples 1 to 6, wherein the UCI carried in the NR short duration PUCCH includes one or more of the following: channel state information (CSI), hybrid automatic repeat request acknowledgment (HARQ-ACK), scheduling request (SR), or beam information.

[0142] Example 8 includes an apparatus of any one of Examples 1 to 7, wherein, when alternating subcarriers in two PRBs are used to multiplex the UCI and the pseudo-random sequence associated with the DMRS, the UCI carried in the NR short duration PUCCH and the pseudo-random sequence associated with the DMRS respectively adopt a constant amplitude zero autocorrelation (CAZAC) sequence of length 12.

[0143] Example 9 includes the apparatus of any one of Examples 1 to 8, wherein the pseudo-random sequence associated with the DMRS carried in the NR short duration PUCCH adopts a discrete Fourier transform (DFT) sequence of length 4 for each PRB.

[0144] Example 10 includes an apparatus of a user equipment (UE) operable to encode a new radio (NR) long duration physical uplink control channel (PUCCH) for transmission to a next generation Node B (gNB), the apparatus comprising: one or more processors configured to: identify uplink control information (UCI) of the UE at the UE; multiplex UCI symbols associated with the UCI and pseudo-random sequence symbols associated with a demodulation reference signal (DMRS) using time division multiplexing (TDM) at the UE, wherein the number of pseudo-random sequence symbols multiplexed with the UCI symbols depends on the length of the NR long duration PUCCH; encode the UCI symbols and the pseudo-random sequence symbols associated with the DMRS at the UE to be sent to the gNB on the NR long duration PUCCH; and a memory interface configured to retrieve the UCI from a memory.

[0145] Example 11 includes the apparatus of Example 10, further comprising: a transceiver configured to send the UCI symbol and the pseudo-random sequence symbol associated with the DMRS to the gNB via the NR long duration PUCCH.

[0146] Example 12 includes an apparatus of any one of Examples 10 or 11, wherein: when the length of the NR long duration PUCCH is 4 discrete Fourier transform spread OFDM (DFT-s-OFDM) symbols, the NR long duration PUCCH carries 2 pseudo-random sequence symbols associated with the DMRS; or, when the length of the NR long duration PUCCH is 7 DFT-s-OFDM symbols, the NR long duration PUCCH carries 3 pseudo-random sequence symbols associated with the DMRS.

[0147] Example 13 includes an apparatus of any one of Examples 10 to 12, wherein the NR long duration PUCCH carrying the UCI symbol and the pseudo-random sequence symbol associated with the DMRS is multiplexed into a PUCCH carrying a scheduling request (SR) sequence of the same length within the same physical resource block (PRB) using different cyclic shifts of the same constant amplitude zero autocorrelation (CAZAC) sequence.

[0148] Example 14 includes an apparatus of any one of Examples 10 to 13, wherein, when UE multiplexing is used to multiplex NR long duration PUCCH transmissions of multiple UEs, the NR long duration PUCCH applies a unique orthogonal cover code (OCC) and a unique cyclic shift to the UCI symbol and the pseudo-random sequence symbol associated with the DMRS, respectively, compared to other UEs.

[0149] Example 15 includes an apparatus of any one of Examples 10 to 14, wherein the length of the NR long duration PUCCH carrying the UCI symbol and the pseudo-random sequence symbol associated with the DMRS ranges from 4 discrete Fourier transform spread OFDM (DFT-s-OFDM) symbols to 14 DFT-s-OFDM symbols.

[0150] Example 16 includes an apparatus of any one of Examples 10 to 15, wherein the UCI symbol carried in the NR long duration PUCCH includes one or more of: channel state information (CSI), hybrid automatic repeat request acknowledgment (HARQ-ACK), scheduling request (SR), or beam information.

[0151] Example 17 includes at least one machine-readable storage medium having instructions for encoding a new radio (NR) physical uplink control channel (PUCCH) for transmission from a user equipment (UE) to a next generation node B (gNB), which, when executed by one or more processors at the UE, performs the following operations: identifying uplink control information (UCI) of the UE at the UE; identifying a pseudo-random sequence associated with a demodulation reference signal (DMRS) of the UE at the UE; when the NR PUCCH is an NR short duration PUCCH, multiplexing the UCI and the pseudo-random sequence associated with the DMRS at the UE using frequency division multiplexing (FDM), wherein when the NR PUCCH is an NR short duration PUCCH, multiplexing the UCI and the pseudo-random sequence associated with the DMRS using different subcarriers in one or more physical resource blocks (PRBs); when the NR When the PUCCH is a NR long duration PUCCH, multiplexing the UCI and the pseudo-random sequence associated with the DMRS at the UE using time division multiplexing (TDM), wherein the number of pseudo-random sequence symbols associated with the DMRS depends on the length of the NR long duration PUCCH; and encoding the UCI and the pseudo-random sequence associated with the DMRS at the UE for sending to the gNB through the NR PUCCH.

[0152] Example 18 includes at least one machine-readable storage medium of Example 17, wherein the NR short duration PUCCH comprises one or two orthogonal frequency division multiplexing (OFDM) symbols.

[0153] Example 19 includes at least one machine-readable storage medium of any one of Examples 17 to 18, wherein the length of the NR long duration PUCCH ranges from 4 discrete Fourier transform spread OFDM (DFT-s-OFDM) symbols to 14 DFT-s-OFDM symbols.

[0154] Example 20 includes at least one machine-readable storage medium of any one of Examples 17 to 19, wherein the UCI carried in the NRPUCCH includes one or more of the following: channel state information (CSI), hybrid automatic repeat request acknowledgment (HARQ-ACK), scheduling request (SR), or beam information.

[0155] Example 21 includes a user equipment (UE) operable to encode a new radio (NR) physical uplink control channel (PUCCH) for transmission from the user equipment (UE) to a next generation node B (gNB), the UE comprising: a module for identifying uplink control information (UCI) of the UE at the UE; a module for identifying a pseudo-random sequence associated with a demodulation reference signal (DMRS) of the UE at the UE; when the NR PUCCH is an NR short duration PUCCH, a module for multiplexing the UCI and the pseudo-random sequence associated with the DMRS at the UE using frequency division multiplexing (FDM), wherein when the NR PUCCH is an NR short duration PUCCH, the UCI and the pseudo-random sequence associated with the DMRS are multiplexed using different subcarriers in one or more physical resource blocks (PRBs); when the NR PUCCH is an NR short duration PUCCH, the UCI and the pseudo-random sequence associated with the DMRS are multiplexed using different subcarriers in one or more physical resource blocks (PRBs); When the PUCCH is an NR long duration PUCCH, means for multiplexing UCI and a pseudo-random sequence associated with a DMRS using time division multiplexing (TDM) at the UE, wherein the number of pseudo-random sequence symbols associated with the DMRS depends on the length of the NR long duration PUCCH; and means for encoding the UCI and the pseudo-random sequence associated with the DMRS at the UE for transmission to the gNB via the NR PUCCH.

[0156] Example 22 includes the UE of Example 21, wherein the NR short duration PUCCH includes one or two orthogonal frequency division multiplexing (OFDM) symbols.

[0157] Example 23 includes the UE of any of Examples 21 or 22, wherein the length of the NR long duration PUCCH ranges from 4 discrete Fourier transform spread OFDM (DFT-s-OFDM) symbols to 14 DFT-s-OFDM symbols.

[0158] Example 24 includes the UE of any one of Examples 21 to 23, wherein the UCI carried in the NR PUCCH includes one or more of the following: channel state information (CSI), hybrid automatic repeat request acknowledgment (HARQ-ACK), scheduling request (SR), or beam information.

[0159] Various technologies or some aspects or parts thereof may take the form of program codes (i.e., instructions) contained in tangible media (such as floppy disks, compact disk read-only memories (CD-ROMs), hard disk drives, non-transitory computer-readable storage media, or any other machine-readable storage media), wherein when the program code is loaded into and executed by a machine such as a computer, the machine becomes a device for implementing various technologies. In the case of executing program codes on a programmable computer, a computing device may include a processor, a storage medium (including volatile and non-volatile memory and / or storage elements) readable by the processor, at least one input device, and at least one output device. Volatile and non-volatile memory and / or storage elements may be random access memory (RAM), erasable programmable read-only memory (EPROM), flash drives, optical drives, magnetic hard disk drives, solid-state drives, or other media for storing electronic data. Nodes and wireless devices may also include transceiver modules (e.g., transceivers), counter modules (e.g., counters), processing modules (e.g., processors), and / or clock modules (e.g., clocks) or timer modules (e.g., timers). In one example, the selected components of the transceiver module may be located in a cloud radio access network (C-RAN). One or more programs that can implement or utilize the various techniques described herein can use application program interfaces (APIs), reusable controls, etc. These programs can be implemented in high-level procedural or object-oriented programming languages ​​to communicate with computer systems. However, if desired, the programs can be implemented in assembly language or machine language. In any case, the language can be a compiled or interpreted language and combined with a hardware implementation.

[0160] As used herein, the term "circuit" may refer to, be a part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

[0161] It should be understood that many of the functional units described in this specification have been labeled as modules in order to more specifically emphasize their implementation independence. For example, a module can be implemented as a hardware circuit including a customized very large scale integration (VLSI) circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module can also be implemented in a programmable hardware device (such as a field programmable gate array, programmable array logic, a programmable logic device, etc.).

[0162] Modules may also be implemented in software to be executed by various types of processors. The modules of the identified executable code may, for example, include one or more physical or logical blocks of computer instructions, which may, for example, be organized as objects, programs, or functions. However, the executable files of the identified modules may not be physically located together, but may include different instructions stored in different locations, which, when logically connected together, comprise the module and achieve the stated purpose of the module.

[0163] In fact, the module of executable code can be a single instruction or multiple instructions, and can even be distributed on several different code segments, different programs and several memory devices. Similarly, operating data can be identified and shown in the module herein, and can be implemented in any suitable form and organized in any suitable type of data structure. Operating data can be collected as a single data set, or can be distributed in different locations including different storage devices, and can exist at least partially as electronic signals on a system or network. Modules can be passive or active, including agents that can be operated to perform desired functions.

[0164] References throughout this specification to "one example" or "illustrative example" mean that a particular feature, structure, or characteristic described in conjunction with the example is included in at least one embodiment of the present technology. Therefore, the phrases "in one example" or "in an exemplary example" that appear in various places throughout this specification are not necessarily all referring to the same embodiment.

[0165] As used herein, for convenience, multiple items, structural elements, constituent elements, and / or materials may be presented in a common list. However, these lists should be interpreted as if each member of the list were individually identified as an independent and unique member. Therefore, any individual member in such a list should not be interpreted as being in fact equivalent to any other member in the same list, based solely on their presentation in a common group without any indication to the contrary. In addition, various embodiments and examples of the present technology and alternatives to its various components may be referenced herein. It should be understood that these embodiments, examples, and alternatives should not be interpreted as de facto equivalents of each other, but should be regarded as separate and autonomous representations of the present technology.

[0166] In addition, the described features, structures or characteristics can be combined in any suitable manner in one or more embodiments. In the specification, many specific details are provided, such as examples of layouts, distances, and network examples, etc., to provide a thorough understanding of the embodiments of the present technology. However, those skilled in the relevant art will recognize that the present technology can be implemented without one or more specific details or using other methods, components, layouts, etc. In other cases, well-known structures, materials, or operations are not shown or described in detail to avoid blurring various aspects of the present technology.

[0167] Although the foregoing examples illustrate the principles of the present technology in one or more specific applications, it is apparent to those skilled in the art that various modifications may be made to the form, use, and implementation details without departing from the principles and concepts of the present technology without implementing the capabilities of the present invention.

Claims

1. A user equipment UE, the UE being operable to encode a New Radio NR Physical Uplink Control Channel PUCCH for transmission to a base station, the UE comprising: One or more processors configured to: identifying, at the UE, uplink control information (UCI) of the UE; When the NR PUCCH is a NR long duration PUCCH, multiplexing the UCI with an uplink UL data channel using frequency division multiplexing FDM at the UE; when the NR PUCCH is a NR short duration PUCCH, multiplexing the UCI and the UL data channel using time division multiplexing TDM at the UE, wherein the NR short duration PUCCH includes a short HARQ-ACK PUCCH and a short SR PUCCH, and wherein the groups of two physical resource blocks PRBs of the NR short continuous time PUCCH are configured on a long-distance frequency block; as well as encoding, at the UE, the UCI and the UL data channel for transmission to the base station on the NR PUCCH; as well as A memory interface is configured to retrieve the UCI from a memory.

2. The UE according to claim 1, wherein: The UL data channel includes a physical uplink shared channel PUSCH.

3. The UE according to claim 2, wherein: The one or more processors are also configured to insert a guard period between a NR physical downlink control channel (PDCCH) and the PUSCH.

4. The UE according to claim 1, wherein: The NR short duration PUCCH includes one or two orthogonal frequency division multiplexing OFDM symbols.

5. The UE according to claim 1, wherein: The one or more processors are also configured to use discrete Fourier transform DFT-spread orthogonal frequency division multiplexing OFDM, ie, DFT-s-OFDM, for the NR long duration PUCCH.

6. The UE according to claim 5, wherein: The one or more processors are further configured to apply the DFT prior to inverse DFT IDFT at the UE.

7. The UE according to claim 5, wherein: The NR long duration PUCCH ranges from four DFT-s-OFDM symbols in length to fourteen DFT-s-OFDM symbols in length.

8. The UE according to claim 1, wherein: The UCI includes at least one of channel state information CSI, hybrid automatic repeat request acknowledgement HARQ-ACK, scheduling request SR and beam information.

9. A method for a user equipment UE, the method comprising: identifying, at the UE, uplink control information UCI for the UE to send to a base station; When the New Radio NR physical uplink control channel PUCCH is a NR long duration PUCCH, multiplexing the UCI with an uplink UL data channel using frequency division multiplexing FDM at the UE; when the NR PUCCH is a NR short duration PUCCH, multiplexing the UCI and the UL data channel using time division multiplexing (TDM) at the UE, wherein the NR short duration PUCCH includes a short HARQ-ACK PUCCH and a short SR PUCCH, and wherein the groups of two physical resource blocks (PRBs) of the NR short continuous time PUCCH are configured on a long-distance frequency block; as well as The UCI and the UL data channel are encoded at the UE for transmission to the base station on the NR PUCCH.

10. The method according to claim 9, wherein: The UL data channel includes a physical uplink shared channel PUSCH.

11. The method according to claim 10, further comprising: A guard period is inserted between the NR physical downlink control channel PDCCH and the PUSCH.

12. The method according to claim 9, wherein: The NR short duration PUCCH includes one or two orthogonal frequency division multiplexing OFDM symbols.

13. The method according to claim 9, further comprising: For the NR long duration PUCCH, discrete Fourier transform DFT-spread orthogonal frequency division multiplexing OFDM, namely DFT-s-OFDM, is used.

14. The method according to claim 13, further comprising: The DFT is applied at the UE before an inverse DFT IDFT.

15. The method according to claim 13, wherein: The NR long duration PUCCH ranges from four DFT-s-OFDM symbols in length to fourteen DFT-s-OFDM symbols in length.

16. At least one machine-readable storage medium having instructions embodied thereon, the instructions for encoding a New Radio (NR) Physical Uplink Control Channel (PUCCH) for transmission from a user equipment (UE) to a base station, the instructions when executed by one or more processors at the UE performing the following operations: identifying, at the UE, uplink control information UCI for the UE to send to a base station; When the NR PUCCH is a NR long duration PUCCH, multiplexing the UCI with an uplink UL data channel using frequency division multiplexing FDM at the UE; when the NR PUCCH is a NR short duration PUCCH, multiplexing the UCI and the UL data channel using time division multiplexing (TDM) at the UE, wherein the NR short duration PUCCH includes a short HARQ-ACK PUCCH and a short SR PUCCH, and wherein the groups of two physical resource blocks (PRBs) of the NR short continuous time PUCCH are configured on a long distance frequency block; and The UCI and the UL data channel are encoded at the UE for transmission to the base station on the NR PUCCH.

17. The at least one machine-readable storage medium of claim 16, wherein: The UL data channel includes a physical uplink shared channel PUSCH, and wherein the instruction is further used to insert a guard period between the NR physical downlink control channel PDCCH and the PUSCH.

18. The at least one machine-readable storage medium of claim 16, wherein the NR short duration PUCCH comprises one or two orthogonal frequency division multiplexing (OFDM) symbols.

19. The at least one machine-readable storage medium of claim 16, wherein: For the NR long duration PUCCH, the instruction is further used to: Spreading OFDM using Discrete Fourier Transform (DFT), i.e. DFT-s-OFDM; and The DFT is applied at the UE before an inverse DFT IDFT.

20. The at least one machine-readable storage medium of claim 19, wherein: The NR long duration PUCCH ranges from four DFT-s-OFDM symbols in length to fourteen DFT-s-OFDM symbols in length.

Images