Physical uplink control channel transmission scheme

Abstract

[0003] Embodiments herein provide techniques for transmitting a Physical Uplink Control Channel (PUCCH) in a wireless cellular network. For example, transmission schemes are provided for sequence-based transmission of the PUCCH and / or to improve PUCCH coverage. Other embodiments may be described and claimed.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to U.S. Provisional Patent Application No. 63 / 059,033, filed July 30, 2020, U.S. Provisional Patent Application No. 63 / 083,522, filed September 25, 2020, U.S. Provisional Patent Application No. 63 / 088,885, filed October 7, 2020, and U.S. Provisional Patent Application No. 63 / 091,659, filed October 14, 2020.

[0002] Various embodiments may generally relate to the field of wireless communications. [Background technology]

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. The next-generation wireless communications system, 5G, or New Radio (NR), provides access to information and sharing of data anywhere, anytime by a variety of users and applications. NR is envisioned as a unified network / system that aims to meet vastly different and sometimes conflicting performance dimensions and services. These diverse multi-dimensional requirements are driven by different services and applications. In general, NR evolves based on 3GPP LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people's lives with better, simpler, and seamless wireless connectivity solutions. NR enables everything to be connected wirelessly, delivering rich content and services at high speeds. [Brief explanation of the drawings]

[0004] [Figure 1] 1 illustrates a performance comparison of a physical uplink control channel (PUCCH) with and without a demodulation reference signal (DMRS), according to various embodiments.

[0005] [Figure 2] 1 illustrates PUCCH format 1 without DMRS, according to various embodiments.

[0006] [Figure 3] 1 illustrates an orthogonal cover code (OCC) for PUCCH format 1 without DMRS, in accordance with various embodiments.

[0007] [Figure 4] 1 illustrates an example sequence for PUCCH format 1 without DMRS, in accordance with various embodiments.

[0008] [Figure 5] 1 illustrates symbol division for PUCCH format 1 with more than seven symbols, according to various embodiments.

[0009] [Figure 6] 1 illustrates PUCCH format 3 without DMRS, according to various embodiments.

[0010] [Figure 7] 1 illustrates an example of sequence-based PUCCH transmission using a Discrete Fourier Transform (DFT)-Spread(s)-Orthogonal Frequency Division Multiplexing (OFDM) waveform, in accordance with various embodiments.

[0011] [Figure 8] 1 illustrates a network in accordance with various embodiments.

[0012] [Figure 9] 1 illustrates a schematic diagram of a wireless network in accordance with various embodiments.

[0013] [Figure 10] FIG. 1 is a block diagram illustrating components that, in some example embodiments, are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods described herein.

[0014] [Figure 11] 1 illustrates an example procedure for implementing various embodiments described herein. [Figure 12] 1 illustrates an example procedure for implementing various embodiments described herein. [Figure 13] 1 illustrates an example procedure for implementing various embodiments described herein. [Figure 14] 1 illustrates an example procedure for implementing various embodiments described herein. DETAILED DESCRIPTION OF THE INVENTION

[0015] The following detailed description refers to the accompanying drawings. The same reference numbers may be used to identify the same or similar elements in different drawings. In the following detailed description, for purposes of explanation, and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to one skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0016] For cellular systems, coverage is a key factor for successful operation. Compared to LTE, NR can be deployed at a relatively higher carrier frequency in Frequency Range 1 (FR1), e.g., 3.5 GHz. In this case, coverage loss due to larger path loss is expected, which makes it more difficult to maintain adequate service quality. Typically, uplink coverage is a bottleneck for system operation, given the low transmit power at the UE side.

[0017] In NR Rel-15, the short Physical Uplink Control Channel (PUCCH) (PUCCH formats 0 and 2) can span 1 or 2 symbols, and the long PUCCH (PUCCH formats 1, 3, and 4) can span 4 to 14 symbols within a slot. More specifically, PUCCH format 0 can be used to carry up to two uplink control information (UCI) bits. It is designed based on a sequence selection mechanism, where information bits are used to select the sequence to be transmitted. The sequence is a computer-generated sequence (CGS) of length 12 with low peak-to-average power ratio (PAPR) characteristics. PUCCH format 1 can be used to carry up to two UCI bits. Furthermore, one or two UCI bits are first modulated as a BPSK or QPSK symbol and then multiplied by a CGS with length 12 and low PAPR characteristics. PUCCH format 2 can be used to carry more than two UCI bits. It is based on an OFDM waveform, where the demodulation reference signal (DMRS) is interleaved with the UCI symbols within the allocated resources. The number of physical resource blocks (PRBs) can be configured from 1 to 16. PUCCH format 3 can be used to carry more than two UCI bits. It is based on a DFT-s-OFDM waveform, where DMRS and UCI symbols are multiplexed in a time division multiplexing (TDM) manner. PUCCH format 4 can be used to carry more than two UCI bits, spanning one PRB in frequency. Additionally, a pre-Discrete Fourier Transform (DFT) block-wise sequence is applied to the modulated UCI symbols, allowing multiple UEs to be multiplexed in the same PRB.

[0018] For long PUCCHs, such as PUCCH formats 1, 3, and 4, the number of slots can be configured to further extend coverage. Note that if repetition is employed, the same time-domain resource allocation (TDRA) for PUCCH transmission is used in each slot. Furthermore, inter-slot frequency hopping can be configured to improve performance by leveraging frequency diversity.

[0019] To further improve coverage, gNB receivers may rely on non-coherent detection of the PUCCH, especially when the UCI payload size is relatively small. In this case, a demodulation reference signal (DMRS) associated with the PUCCH transmission may not be required. Note that in NR, the sequences used for PUCCH Format 1 and Format 3 when the UCI payload is smaller than 12 bits lead to undesirable cross-correlation characteristics, which significantly degrade performance, especially when a non-coherent detection algorithm is employed at the receiver. To improve detection performance, certain enhancements may need to be considered for sequence-based PUCCH schemes and PUCCH coverage extensions.

[0020] Embodiments herein include systems and methods for an enhanced PUCCH transmission scheme. For example, some embodiments relate to a sequence-based transmission scheme. The embodiments may be used in wireless cellular networks, such as NR networks. The embodiments may improve PUCCH coverage.

[0021] [I.1 Extended PUCCH format 1 for sequence-based transmission scheme] An embodiment of an extended scheme for PUCCH format 1 for a sequence-based transmission scheme is provided as further described below.

[0022] In one embodiment, multiple orthogonal sequences may be defined for transmission of PUCCH format 1. Furthermore, the sequences may be directly mapped to the allocated resources of PUCCH format 1 according to the UCI payload information, without any associated DMRS.

[0023] In one option, Zadoff-Chu (ZC) sequences with different root indices may be used to generate sequences for PUCCH format 1. In particular, assuming UCI payload information is n, the sequence group identity parameter u may be generated according to the UCI payload information n, where n may be bits {0,1} for a 1-bit UCI payload and may be bits {0,1,2,3} for a 2-bit UCI payload.

[0024] More specifically, the sequence group identity parameter can be defined as follows: Option 1:

number

number

number

number

number

number

[0025] In another example, the updated text of section 6.3.2.2.1 in TS38.211[1] reads: gh In this case, you can update it as follows in bold:

number

[0026] In another embodiment, Zadoff-Chu (ZC) sequences with different cyclic shifts may be used to generate sequences for PUCCH format 1. In particular, assuming that the UCI payload information is n, the cyclic shift parameter α may be generated according to the UCI payload information n, where n may be bits {0,1} for a 1-bit UCI payload and may be bits {0,1,2,3} for a 2-bit UCI payload.

[0027] In one example, the updated text of section 6.3.2.2.12 in TS38.211[1] for the cyclic shift parameter α can be updated in bold as follows:

number

[0028] In another example, the cyclic shift parameter α can be defined as follows:

number

[0029] In one example, for PUCCH format 1 with 1-bit UCI payload, the cyclic shift parameter α can be defined as follows:

number

number

[0030] In one embodiment, the scrambling sequence generation for PUCCH format 3 is modified to ensure desirable cross-correlation properties for different sequences, which may help improve detection performance at the receiver. In particular, the scrambling sequence may be initialized according to partial or complete UCI payload information.

[0031] In one option, the following formula can be used to determine the default value for scrambling sequence generation for PUCCH format 3:

number

number

number

Number

Number

Number

Number

[0032] In another option, two scrambling IDs can be configured for PUCCH format 3, where the first scrambling ID can be applied when the UCI payload is n < N / 2, and the second scrambling ID can be applied when the UCI payload is

Number

Number

[0034] The updated text in section 6.3.2.6.2 of TS38.211[1] can be highlighted in bold as follows:

[0035] For PUCCH format 3, when interlaced mapping is not configured, block-wise spreading is not applied,

number

number

number

number

number

number

number

[0036] In one example, the text of section 5.3.3.3 in 3GPP TS 38.212, V16.1.0 (hereinafter “TS38.212” or “[2]”) can be updated in bold to read as follows:

[0037] For 3≦K≦10, the code block is

number

[0038] In another embodiment, a sequence representing UCI payload information is transmitted on symbols allocated for UCI transmission, where DMRS symbols are present in PUCCH format 3. Note that the same DMRS pattern as defined for PUCCH format 3 can be reused. In this case, the length of the sequence is determined with respect to the number of symbols allocated for UCI transmission, the number of REs allocated to PUCCH format 3, and the modulation order.

[0039] II. NR PUCCH Coverage Extension Transmission Scheme As mentioned above, for long PUCCHs (e.g., PUCCH formats 1, 3, and 4), the number of slots can be configured to further extend coverage. Note that if repetition is employed, the same time-domain resource allocation (TDRA) for PUCCH transmission is used in each slot. Furthermore, inter-slot frequency hopping can be configured to improve performance by leveraging frequency diversity. To further improve coverage, a gNB receiver (Rx) may rely on non-coherent detection of the PUCCH, especially when the UCI payload size is relatively small. In this case, a demodulation reference signal (DMRS) associated with the PUCCH transmission may not be required. Figure 1 shows a performance comparison between PUCCH transmission with and without DMRS. In the figure, PUCCH format 3 with an 11-bit UCI payload is assumed. Furthermore, the PUCCH spans 14 symbols and occupies one PRB. From the figure, it can be observed that when a non-coherent detection-based receiver algorithm is employed, PUCCH transmission without DMRS can achieve better performance than PUCCH transmission with DMRS. Embodiments of transmission schemes for PUCCH for NR coverage extension are further described below.

[0040] In one embodiment, for PUCCH format 1, BPSK is used as modulation for 1-bit HARQ-ACK feedback, and QPSK is used as modulation for 2-bit HARQ-ACK feedback. The modulated symbols are then multiplied by a length-12 sequence in the frequency domain and an orthogonal cover code (OCC). The modulated sequences are then directly mapped to the allocated resources configured for PUCCH format 1. Note that DMRS is not transmitted on the resources allocated to PUCCH format 1.

[0041] For PUCCH format 1 without DMRS, the length 12 sequence can be reused according to the NR specifications. In particular, the sequence can be generated according to section 5.2.2.2 in [1] sequence, and cyclic shift hopping can be reused according to section III.2 (infra) or section 6.3.2.2 in [1]. In various embodiments, the PUCCH format 1 sequence y(n) assigned to the original data symbol is

number

number

[0042] 2 shows an example of PUCCH format 1 without DMRS in accordance with various embodiments. In this example, PUCCH format 1 spans six symbols in time within a slot and occupies one physical resource block (PRB) in frequency. Furthermore, all six symbols are used to transmit either the UCI d(0) or the conjugate d(0) of the UCI for PUCCH format 1; that is, the DMRS symbols are replaced with their original sequence multiplied by the conjugate of d(0). Note that in the figure, UCI0 indicates a length-12 sequence multiplied by d(0), while UCI1 indicates a length-12 sequence multiplied by the conjugate of d(0).

[0043] In one embodiment, to allow PUCCH Format 1 defined in Rel-15 and PUCCH Format 1 without DMRS to coexist simultaneously and within the same frequency resources, if intra-slot frequency hopping is disabled, time-domain OCC can be applied to odd / UCI symbols and even / UCI symbols, respectively. If intra-slot frequency hopping is enabled, at each hop, OCC is applied to odd and even UCI symbols, respectively. Note that odd and even UCI symbols are defined relative to the first symbol of the PUCCH transmission, not relative to the slot boundary. For this option, the maximum OCC length can be maintained at 7, and OCC sequences can be reused according to Table III.4.1-2 (infra) or Table 6.3.2.4.1-2 in [1].

[0044] Furthermore, the same or different OCC sequence indexes can be configured for odd and even UCI symbols, respectively, of PUCCH format 1. In the case where different OCC sequence indexes are configured for odd and even UCI symbols of PUCCH format 1, separate timeDomainOCC may be defined.

[0045] 3 shows an example of applying OCC to PUCCH format 1 without DMRS in accordance with various embodiments. In this example, an OCC of length 3 is applied to even and odd UCI symbols, respectively. The indices of these two OCCs do not necessarily have to be the same.

[0046] In another embodiment, the complex number d(0) may be replaced with a sequence from a sequence set, where the sequence is a one-to-one mapping to the values ​​of the UCI bits. More specifically, assume that the number of symbols in PUCCH format 1 is K. The sequences in the sequence set may be defined as

number

number

number

[0047] As an example of PUCCH format 1 with K symbols, multiple UEs share resources using orthogonal sequences of length 12. Furthermore, different UEs use different cyclic shifts in the PUCCH symbols. For a 1-bit UCI, two binary sequences of length K can be used to represent the bits. One sequence can be all ones, and the other sequence can be the first [K / 2] bits that are all ones and the remaining K-[K / 2] bits can be all -1. In general, a sequence set for PUCCH format 1 of length K can be generated by an exhaustive search of K-bit binary sequences for the maximum Hamming distance between any pair of sequences, e.g., 4≦K≦14.

[0048] As another example of multiple UEs sharing the K symbol resource allocated to PUCCH format 1, length K orthogonal sequences can be applied. More specifically, a set of length K 2 / 4 sequences can be allocated to a UE with 1 / 2 bit UCI. All sets should theoretically be orthogonal to each other.

[0049] In another embodiment, multiple orthogonal sequences may be defined for PUCCH format 1 transmission. In particular, In the case of a positive SR, a sequence of 1s may be configured for the UE. For 1-bit HARQ-ACK feedback, two orthogonal sequences can be configured for the UE. Furthermore, bit "0" can map to the first sequence, and bit "1" can map to the second sequence. For 2-bit HARQ-ACK feedback, four orthogonal sequences can be configured for the UE. Table 1 shows an example of mapping UCI payload to sequences for PUCCH format 1. Table 1: Mapping UCI payload to PUCCH format 1 sequences [Table 2] Note that the sequence can be directly mapped to the resources allocated to PUCCH format 1. In this case, DMRS is not transmitted in PUCCH format 1. Alternatively, the sequence can be mapped to the resources for UCI transmission. This sequence is selected from two sequences representing one configured bit of UCI and four sequences representing two configured bits of UCI. In this case, the DMRS position can be reused to transmit the selected sequence according to Section 6.4.1.3.1 in [1]. Since the NR specifications specify 12 orthogonal sequences for PUCCH over frequency, the total number of UEs simultaneously sharing the same resource can, in principle, be between three and six, depending on the number of bits used by the UE for UCI transmission.

[0050] As an example of a sequence that can be mapped to the UCI payload, the length 12 sequence specified in the NR specifications for PUCCH format 1 can be reused for the proposed PUCCH format 1. More specifically, the complex value symbol d(0) and the sequence in Section III.4 (infra) or 6.3.2.4 of [1]

number

number

[0051] Additionally, the text of Section 9.2.3 of [2] after Table 9.2.3-4 can be updated as shown below.

[0052] When a UE transmits a PUCCH with HARQ-ACK information using PUCCH format 1, the UE is provided with the value of m0 by the initialCyclicShift of PUCCH-format 1, or, if initialCyclicShift is not provided, by the index of the initial cyclic shift described in Section 9.2.1 [[.]]. cs is determined from the value of one HARQ-ACK information bit or from the values ​​of two HARQ-ACK information bits as in Table 9.2.3-3 and Table 9.2.3-4, respectively.

[0053] As a further extension, an orthogonal sequence can be defined as a combination of a length-12 sequence in the frequency domain and an OCC in the time domain. Furthermore, different initial cyclic shift values ​​and / or OCC indices can be configured to generate two or four orthogonal sequences for one-bit or two-bit HARQ-ACK feedback.

[0054] In one example, assuming that sequences of length 12 in frequency are reused according to the NR specification, this indicates that up to 12 orthogonal sequences can be generated by using 12 different cyclic shift values. Furthermore, depending on the length of PUCCH format 1, i.e., length K, the number of orthogonal sequences in time, w, of Section 6.3.2.4.1 in [1], can be generated. i (m) can be up to K by using different OCC indices, in which case the number of UEs that can be multiplexed simultaneously and on the same frequency resource for PUCCH format 1 can be between 3 and K, and between 6 and K for 1-bit and 2-bit UCI, respectively.

[0055] Since the length of OCC is only up to 7 in the NR specifications and the number of symbols in PUCCH format 1 can be 14 when intra-slot frequency hopping is disabled, two options can be considered to apply OCC for multiple UEs when the number of symbols is greater than 7 when intra-slot frequency hopping is disabled.

[0056] In one option, the OCC code can be extended to support lengths greater than 7. Additionally, the OCC code can be generated based on a Discrete Fourier Transform (DFT)-based orthogonal code.

[0057] In another option, sequence-based PUCCH Format 1 transmissions can be divided into multiple groups, each of which is no larger than seven symbols, and OCC is applied to these groups separately. Furthermore, the same or different OCC sequence indices can be configured for the PUCCH Format 1 groups. If different OCC sequence indices are configured, a separate timeDomainOCC can be defined for each of those groups.

[0058] In one example, the K symbols are divided into two groups when intra-slot frequency hopping is disabled, where [K / 2] symbols are assigned to the first group and K-[K / 2] symbols are assigned to the second group.

[0059] In another example, the K symbols are divided into two groups, regardless of whether intra-slot frequency hopping is disabled or enabled, where [K / 2] symbols are assigned to the first group and K-[K / 2] symbols are assigned to the second group.

[0060] In another example, if K>7 and intra-slot frequency hopping is disabled, then these K symbols are divided into two groups, where [K / 2] symbols are assigned to the first group and K-[K / 2] symbols are assigned to the second group.

[0061] 5 shows an example of symbol division for PUCCH format 1 with more than seven symbols in accordance with various embodiments. In this example, eight symbols are allocated to PUCCH format 1 without DMRS. These eight symbols are further divided into two groups, each having four symbols. Note that length-four OCC is applied to the first and second groups, each having four symbols.

[0062] In another embodiment, the UE can be configured with two different cyclic shift values ​​over frequency and two different OCC indices over time for the four orthogonal sequences. Alternatively, the UE can be configured with four different cyclic shift values ​​over frequency and one OCC index over time for the four orthogonal sequences. In another example, the UE can be configured with one cyclic shift value over frequency and four different OCC indices over time for the four orthogonal sequences.

[0063] Table 2 shows an example of mapping UCI payloads to sequences in PUCCH format 1. In this example, separate initial cyclic shift values ​​and OCC indices are configured for different UCI payloads. Table 2: Mapping UCI payload to PUCCH format 1 sequences: Example 1 [Table 3] In one example, for PUCCH Format 1 with K symbols, a UE may be assigned two initial cyclic shifts and two OCC indices of length K. Table 3 shows one example of mapping UCI payload to the proposed PUCCH Format 1 sequence. In this example, two initial cyclic shifts of 0 and 6 and two time-domain OCC indices of 0 and 1 are assigned to the UE. Note that other examples can be directly extended from this example. Table 3: Mapping UCI payload to PUCCH format 1 sequence: Example 2 [Table 4] In another embodiment, for PUCCH format 3, if the UCI payload size is smaller than K bits, after encoding and modulation, the modulated symbols are directly mapped to the allocated resources of the PUCCH transmission. In addition, a phase rotation procedure can be applied to the modulated symbols. For this option, the DMRS does not exist within the allocated resources of PUCCH format 3. Note that K can be predetermined herein or configured by higher layers via NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling. In one example, K = 12. Furthermore, for the encoding process, the UE performs rate matching of the encoded bits to the allocated resources for PUCCH format 3 transmission.

[0064] 6 shows an example of PUCCH format 3 without DMRS, in accordance with various embodiments. In this example, PUCCH format 3 spans 8 symbols in time and occupies N PRBs in frequency within a slot, where N is configured by higher layers. Furthermore, all 8 symbols are used to transmit UCI for PUCCH format 3, i.e., no DMRS symbols are present in PUCCH format 3.

[0065] In another embodiment, if the UCI payload size is smaller than K bits, multiple sequences can be defined for PUCCH format 3 transmission. In particular, if the UCI payload size is smaller than K bits, multiple sequences can be defined for PUCCH format 3 transmission. UCI Assuming that the sequence is K bits, UCI Then, the number of sequences for PUCCH format 3 transmission is

number

[0066] In one option, multiple long sequences can be generated based on the pseudorandom binary sequence (PRBS) of section 5.2.1 of [1] for PUCCH format 3. PRB Assuming that the PRBs are allocated to L symbol The number of symbols and UCI payload is K UCI Depending on the modulation of PUCCH format 3, M = 2 when QPSK is configured, or M = 1 when BPSK is configured. Then, the length of the PRBS is 12 N PRB L symbol ·M. UCI K UCIThe PRBS mapping to bit values ​​can be generated with a unique initial seed. The UE then selects one PRBS based on the UCI payload for transmission. Modulation is then applied to the selected sequence. In the final step, the modulated sequence is directly mapped to the allocated resources for PUCCH format 3 transmission. For this option, the DMRS does not exist within the allocated resources of PUCCH format 3.

[0067] For example, the initial seed for generating a long sequence is

number

number

number

number

number

[0068] It should be noted that different sequence generation methods may affect the detection performance of PUCCH format 3 of the embodiments herein. The larger the minimum distance between any pair of sequences, the better the detection performance.

[0069] In another embodiment, the initial seed for the generation of the long sequence may be defined depending on one or more of the following parameters: Radio Network Temporary Identifier (RNTI), Virtual Cell ID or Scrambling ID, and / or UCI payload information.

[0070] In particular, the initial seed for the generation of the long sequence can be defined as follows:

number

number

number

[0071] In one example, the initial seed for the generation of the long sequence can be defined as follows:

number

number

number

number

[0072] In one example, the initial seed for the generation of the long sequence can be defined as follows:

number

number

number

number

number

[0073] In another embodiment, for the new PUCCH format 3, sequences based on either long or short sequences in each OFDM symbol can be transmitted using pi / 2 BPSK modulation based on a DFT-s-OFDM waveform.

[0074] Note that in the case of π / 2-BPSK modulation, bits b(i) are mapped to complex-valued modulation symbols d(i) according to the following equation:

number

[0075] In Figure 7, a pi / 2 BPSK modulated sequence with length M0 is input to a DFT or FFT block. The output of the DFT or FFT block with length M1 is then mapped to subcarriers in the frequency domain as input to an IFFT block, and then converted to a time domain signal. The size of the IFFT block is N. Typically, N > M1 ≥ M0. For sequence-based PUCCH transmission, M1 = M0.

[0076] III. Physical Uplink Control Channel (PUCCH) Format Aspects Some supporting information from TS38.211[1] and 38.212[2] is provided below for context associated with various embodiments of this specification.

[0077] [III.1 General] PUCCH supports multiple formats as shown in Table III.1-1 or Table 6.3.2.1-1 in [1]. If intra-slot frequency hopping is configured for PUCCH format 1, 3 or 4 according to clause 9.2.1 in [2], the number of symbols in the first hop is

number

number

number

number

[0078] III.2.1 Group and Sequence Hopping Sequence Groups Within Groups

number

number

number

number

number

number

number

number

number

[0079] When intra-slot frequency hopping is disabled by the higher layer parameter intraSlotFrequencyHopping, the frequency hopping index n hop = 0. When frequency hopping is enabled by the higher layer parameter intraSlotFrequencyHopping, n for the first hop hop =0 and for the second hop n hop =1.

[0080] [III.2.2 Cyclic Shift Hopping] The cyclic shift α is

number

number

number

number

number

number

[0081] [III.3 PUCCH format 0] [III.3.1 Sequence Generation] The sequence x(n) is

number

number

[0082] [III.3.2 Mapping to physical resources] The sequence x(n) is scaled by an amplitude scaling factor β to comply with the transmit power specified in [2]. PUCCH,0 multiplied by x(k,l) and allocated to be transmitted according to clause 9.2.1 of [2] in a sequence starting with x(0). p,u Let index k be mapped in increasing order through the allocated physical resources spanning one resource block, and then the index l on the antenna port is p=2000.

[0083] In case of interlaced transmission, the mapping operation shall be repeated for each resource block in the interlace and in the active bandwidth portion across the physical resource blocks allocated according to clause 9.2.1 of [2], using the resource block dependent sequence generated according to clause III.2 or clause 6.3.2.2 of [1].

[0084] [III.4 PUCCH format 1] [III.4.1 Sequence modulation] Bits b(0),...,b(M bit -1) block is M bit When =1, BPSK is used and M bit = 2, it shall be modulated using QPSK as described in section 5.1 of [1], resulting in the complex-valued symbol d(0).

[0085] The complex-valued symbol d(0) is

number

number

number

number

number

number

[0086] Orthogonal sequence w i (m) is given by Table III.4-1-2 or Table 6.3.2.4.1-2 of [1], where i is the index of the orthogonal sequence to be used according to Section 9.2.1 of [2]. If the PUCCH transmission spans multiple slots according to Section 9.2.6 of [2], the complex-valued symbol d(0) is repeated for subsequent slots. Table III.4.1-1: PUCCH symbols and corresponding

number

number

[0087] In case of interlaced transmission, the mapping operation shall be repeated for each resource block in the interlace and in the active bandwidth portion across the physical resource blocks allocated according to clause 9.2.1 of [2], using the resource block dependent sequence generated according to clause III.2 or clause 6.3.2.2 of [1].

[0088] [III.5 PUCCH format 2] [III.5.1 Scramble] M bit where b(0),...,b(M) is the number of bits transmitted on the physical channel. bit -1) shall be scrambled before modulation, resulting in

number

number

number

number

number

[0089] [III.5.2 Modulation] Scrambled bits

number

[0090] [III.5.2A Diffusion] The diffusion is

number

number

number

number

[0091] When the upper layer parameter interlace1 is not configured and the upper layer parameter OCC-Length-r16 is configured, -

number

number

number

[0092] Table III.5A-1:

number

number

number

[0093] - resource elements (k,l) not reserved for other purposes p,u The mapping to p = 2000 is as per clause 9.2.1 of [2], where first the index k is in increasing order through the assigned physical resource blocks, and then the index l on the antenna port p = 2000.

[0094] [III.6 PUCCH formats 3 and 4] [III.6.1 Scramble] M bit where b(0),...,b(M) is the number of bits transmitted on the physical channel. bit -1) shall be scrambled before modulation, resulting in

number

number

number

number

number

[0095] [III.6.2 Modulation] Scrambled bits

number

[0096] [III.6.3 Block-by-Block Diffusion] For both PUCCH formats 3 and 4,

number

number

number

number

number

number

[0097] For PUCCH format 3, when interlaced mapping is not configured, block-wise spreading is not applied,

number

number

number

[0098] For PUCCH format 3 and PUCCH format 4 with interlaced mapping, the block-wise spreading is

number

number

number

number

number

number

number

number

[0099] Table III.6.3-1: Orthogonal sequences w for PUCCH format 3 with interlaced mapping n (m), and

number

number

number

number

number

[0100] [III.6.5 Mapping to physical resources] Modulation Symbols

number

[0101] For intra-slot frequency hopping according to section 9.2.1 of [2],

number

number

number

[0102] [System and Implementation] 8-10 illustrate various systems, devices and components that may implement aspects of the disclosed embodiments.

[0103] 8 illustrates a network 800 in accordance with various embodiments. Network 800 may operate in a manner consistent with LTE or 5G / NR system 3GPP® technical specifications. However, example embodiments are not so limited, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP® systems.

[0104] The network 800 may include a UE 802, which may include any mobile or non-mobile computing device designed to communicate with the RAN 804 via an over-the-air connection. The UE 802 may be communicatively coupled to the RAN 804 by a Uu interface. The UE 802 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine, a management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network-connected appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0105] In some embodiments, the network 800 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0106] In some embodiments, the UE 802 may further communicate with an AP 806 via a wireless connection. The AP 806 may manage a WLAN connection, which may provide services to offload some / all network traffic from the RAN 804. The connection between the UE 802 and the AP 806 may conform to any IEEE 802.11 protocol, where the AP 806 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 802, the RAN 804, and the AP 806 may use cellular WLAN aggregation (e.g., LWA / LWIP). The cellular WLAN aggregation may use both cellular radio resources and WLAN resources by including the UE 802 configured by the RAN 804.

[0107] The RAN 804 may include one or more access nodes, such as the AN 808. The AN 808 may terminate air-interface protocols for the UE 802 by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 808 may enable data / voice connectivity between the CN 820 and the UE 802. In some embodiments, the AN 808 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 808 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 808 may be a macrocell base station, or a low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0108] In embodiments in which the RAN 804 includes multiple ANs, they may be coupled to one another via an X2 interface (when the RAN 804 is an LTE RAN) or an Xn interface (when the RAN 804 is a 5G RAN). The X2 / Xn interface may be separated into a control / user plane interface in some embodiments and may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0109] The ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 802 with network access over the air interface. The UE 802 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 804. For example, the UE 802 and the RAN 804 may use carrier aggregation, allowing the UE 802 to be connected with multiple component carriers, each corresponding to a PCell or SCell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first AN / second AN may be any combination of an eNB, gNB, ng-eNB, etc.

[0110] The RAN 804 may provide an air interface over a licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques with a PCell / SCell. Before accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example, based on a Listen Before Talk (LBT) protocol.

[0111] In a V2X scenario, the UE 802 or AN 808 may be or operate as an RSU, which may refer to any carrier infrastructure entity used for V2X communications. The RSU may be implemented within or by a suitable AN or a stationary (or relatively stationary) UE. Depending on what it implements within or by, the RSU may be referred to as a "UE-type RSU" if it is a UE, an "eNB-type RSU" if it is an eNB, a "gNB-type RSU" if it is a gNB, etc. In one example, the RSU is a computing device coupled with radio frequency circuitry located on the roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store node map geometry, traffic statistics, media, and application / software, and may sense and control ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications necessary for high-speed events such as collision avoidance and traffic warnings. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0112] In some embodiments, the RAN 804 may be an LTE RAN 810 having an eNB, such as eNB 812. The LTE RAN 810 may provide an LTE air interface with the following characteristics: a 15 kHz SCS, a CP-OFDM waveform for DL ​​and an SC-FDMA waveform for UL, turbo codes for data, and TBCC for control. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell search, and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on a sub-6 GHz band.

[0113] In some embodiments, the RAN 804 may be a gNB, such as a gNB 816, or an NG-RAN 814 having an ng-eNB, such as an ng-eNB 818. The gNB 816 may be connected to a 5G-capable UE using a 5G NR interface. The gNB 816 may be connected to a 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 818 may also be connected to the 5G core via an NG interface, but may be connected to a UE via an LTE air interface. The gNB 816 and the ng-eNB 818 may be connected to each other via an Xn interface.

[0114] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface, which carries traffic data between nodes in the NG-RAN 814 and the UPF 848 (e.g., the N3 interface), and an NG Control Plane (NG-C) interface, which is the signaling interface between nodes in the NG-RAN 814 and the AMF 844 (e.g., the N2 interface).

[0115] The NG-RAN 814 may provide a 5G-NR air interface with the following characteristics: variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, polar, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS and PDSCH / PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for PDSCH phase tracking, and tracking reference signals for time tracking. The 5G-NR air interface may operate on the FR1 band, which includes the sub-6 GHz band, or the FR2 band, which includes the band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0116] In some embodiments, the 5G-NR air interface may use BWPs for various purposes. For example, BWPs can be used for dynamic SCS adaptation. For example, a UE 802 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is instructed to the UE 802, the SCS of the transmission is changed as well. Another use case of BWPs relates to power saving. Specifically, multiple BWPs can be configured for the UE 802 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic loading scenarios. A BWP including a smaller number of PRBs can be used for data transmission with a smaller traffic load, while enabling power saving in the UE 802 and, in some cases, power saving in the gNB 816. A BWP including a larger number of PRBs can be used for scenarios with a higher traffic load. The RAN 804 is communicatively coupled to the CN 820, which includes network elements, to provide various functions and support data and telecommunication services to customers / subscribers (e.g., users of the UE 802). The components of CN 820 may be implemented in one physical node or in separate physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functions provided by the network elements of CN 820 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of CN 820 may be referred to as a network slice, and a logical instantiation of a portion of CN 820 may be referred to as a network sub-slice.

[0117] In some embodiments, the CN 820 may be an LTE CN 822, which may also be referred to as an EPC. The LTE CN 822 may include an MME 824, an SGW 826, an SGSN 828, an HSS 830, a PGW 832, and a PCRF 834 coupled to each other via interfaces (or "reference points") as shown. The functionality of the elements of the LTE CN 822 may be briefly introduced as follows.

[0118] The MME 824 may implement mobility management functions, track the current location of the UE 802, and facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0119] The SGW 826 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 822. The SGW 826 may be a local mobility anchor point for inter-RAN node handovers and may provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging, and some policy enforcement.

[0120] The SGSN 828 may track the location of the UE 802 and perform security functions and access control. In addition, the SGSN 828 may perform inter-EPC node signaling for mobility between different RAT networks, selection of PDN and S-GW designated by the MME 824, selection for handover, etc. The S3 reference point between the MME 824 and the SGSN 828 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0121] The HSS 830 may include a database for network users containing subscription-related information to support communication session processing of the network entities. The HSS 830 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between the HSS 830 and the MME 824 may enable transfer of subscription and authentication data for authentication / authorization of user access to the LTE CN 820.

[0122] The PGW 832 may terminate an SGi interface toward a data network (DN) 836, which may include an application / content server 838. The PGW 832 may route data packets between the LTE CN 822 and the data network 836. The PGW 832 may be coupled to the SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 832 may further include nodes for policy enforcement and charging data collection (e.g., a PCEF). In addition, the SGi reference point between the PGW 832 and the data network 836 may be an operator external public, private PDN, or intra-operator packet data network, for example, for provisioning of IMS services. The PGW 832 may be coupled to a PCRF 834 via a Gx reference point. The PCRF 834 is the policy and control element charging of the LTE CN 822. The PCRF 834 is communicatively coupled to the app / content server 838 and may determine appropriate QoS and charging parameters for service flows. The PCRF 832 may provision the associated rules to the PCEF (via the Gx reference point) with the appropriate TFT and QCI.

[0123] In some embodiments, the CN 820 may be a 5GC 840. The 5GC 840 may include an AUSF 842, an AMF 844, an SMF 846, a UPF 848, an NSSF 850, an NEF 852, an NRF 854, a PCF 856, a UDM 858, and an AF 860 coupled together via interfaces (or "reference points") as shown. The functionality of the elements of the 5GC 840 may be briefly introduced as follows: The AUSF 842 may store data for authentication of the UE 802 and handle authentication-related functions. The AUSF 842 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 840 via reference points as shown, the AUSF 842 may exhibit a Nausf service-based interface.

[0124] The AMF 844 may allow other functions of the 5GC 840 to communicate with the UE 802 and the RAN 804 and subscribe to notifications about mobility events related to the UE 802. The AMF 844 may be responsible for registration management (e.g., registration of the UE 802), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 844 may provide transport of SM messages between the UE 802 and the SMF 846 and act as a transparent proxy for routing of SM messages. The AMF 844 may also provide transport of SMS messages between the UE 802 and the SMSF. The AMF 844 may interact with the AUSF 842 and the UE 802 and perform various security anchor and context management functions. Additionally, the AMF 844 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 804 and the AMF 844, and the AMF 844 may be the termination point of NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 844 may also support NAS signaling with the UE 802 via the N3 IWF interface.

[0125] The SMF 846 may be responsible for SM (e.g., session establishment between the UPF 848 and the AN 808, tunnel management), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuring traffic steering in the UPF 848 to route traffic to the appropriate destination, terminating the interface to the policy control function, controlling policy enforcement, charging, and parts of QoS, lawful interception (SM events and interface to the LI system), terminating the SM portion of NAS messages, downlink data notification, initiating AN-specific SM information sent over the N2 to the AN 808 via the AMF 844, and determining the SSC mode of the session. The SM refers to the management of PDU sessions, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 802 and the data network 836.

[0126] The UPF 848 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection with the data network 836, and a branch point supporting multi-homed PDU sessions. The UPF 848 may also perform packet routing and forwarding, packet inspection, enforce the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), transport-level packet marking in the uplink and downlink, and buffer downlink packets and trigger downlink data notification. The UPF 848 may include an uplink classifier to support routing of traffic flows to the data network.

[0127] The NSSF 850 ​​may select a set of network slice instances to serve the UE 802. The NSSF 850 ​​may also determine the allowed NSSAIs and the mapping to subscribed S-NSSAIs, if necessary. The NSSF 850 ​​may also determine the AMF set to be used to serve the UE 802, or may determine a list of candidate AMFs based on a preferred configuration and possibly by querying the NRF 854. The selection of a set of network slice instances for the UE 802 may be triggered by the AMF 844 to which the UE 802 is registered by interacting with the NSSF 850, which may lead to an AMF change. The NSSF 850 ​​may interact with the AMF 844 via the N22 reference point and may communicate with another NSSF in the visited network via the N31 reference point (not shown). Additionally, the NSSF 850 ​​may exhibit an Nnssf service-based interface.

[0128] The NEF 852 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AFs 860), edge computing or fog computing systems, etc. In such embodiments, the NEF 852 may authenticate, authorize, or throttle AFs. The NEF 852 may also translate information exchanged with the AF 860 and information exchanged with internal network functions. For example, the NEF 852 may translate between AF service identifiers and internal 5GC information. The NEF 852 may also receive information from other NFs based on the other NFs' exposed capabilities. This information may be stored in the NEF 852 as structured data or in a data storage NF using a standard interface. The stored information can then be re-exposed by the NEF 852 to other NFs and AFs or used for other purposes, such as analysis. Additionally, the NEF 852 may present an NEF service-based interface. The NRF 854 supports service discovery functions, receives NF discovery requests from NF instances, and may provide information about discovered NF instances to the NF instances. The NRF 854 also maintains information about available NF instances and their supported services. As used herein, terms such as "instantiate," "instantiation," and the like may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 854 may exhibit an Nnrf service-based interface. The PCF 856 may provide and enforce policy rules to control plane functions and may support a unified policy framework to govern network behavior. The PCF 856 may also implement a front end to access subscription information related to policy decisions in the UDRs of the UDM 858. In addition to communicating with functions via reference points as shown, the PCF 856 exhibits an Npcf service-based interface.The UDM 858 may process subscription-related information to support communication session processing for network entities and may store subscription data for the UE 802. For example, the subscription data may be communicated via the N8 reference point between the UDM 858 and the AMF 844. The UDM 858 may include two parts: an application front end and a UDR. The UDR may store structured data for subscription and policy data for the UDM 858 and PCF 856, and / or exposure and application data for the NEF 852 (including PFD for application discovery and application requirement information for multiple UEs 802). The Nudr service-based interface, represented by the UDR 221, may enable the UDM 858, PCF 856, and NEF 852 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of associated data changes in the UDR. The UDM may include a UDM-FE, which is responsible for processing credentials, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access rights, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, the UDM 858 may exhibit a Nudm service-based interface. The AF 860 may provide application influence over traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0129] In some embodiments, the 5GC 840 may enable edge computing by selecting an operator / third-party service that is geographically close to the point where the UE 802 attaches to the network. This may reduce latency and load on the network. To provide edge computing implementation, the 5GC 840 may select a UPF 848 close to the UE 802 and perform traffic steering from the UPF 848 to the data network 836 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 860. In this way, the AF 860 may influence UPF (re)selection and traffic routing. Based on operator deployment, if the AF 860 is considered a trusted entity, the network operator may allow the AF 860 to interact directly with associated NFs. Additionally, the AF 860 may represent a NAF service-based interface. The data network 836 may represent various network operator services, Internet access, or third-party services, which may be provided by one or more servers, including, for example, the application / content server 838.

[0130] FIG. 9 schematically illustrates a wireless network 900 in accordance with various embodiments. The wireless network 900 may include a UE 902 in wireless communication with an AN 904. The UE 902 and the AN 904 may be similar to and substantially interchangeable with similarly named components described elsewhere herein. The UE 902 may be communicatively coupled to the AN 904 via a connection 906. The connection 906 is illustrated as an air interface for enabling the communication coupling and may conform to a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating in mmWave or sub-6 GHz frequencies. The UE 902 may include a host platform 908 coupled to a modem platform 910. The host platform 908 may include an application processing circuit 912, which may be coupled to a protocol processing circuit 914 of the modem platform 910. The application processing circuit 912 may execute various applications for the UE 902 to source / sink application data. The application processing circuit 912 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations. The protocol processing circuit 914 may implement one or more of the layer operations to facilitate the transmission or reception of data over the connection 906. The layer operations implemented by the protocol processing circuit 914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. The modem platform 910 may further include a digital baseband circuit 916 that may implement one or more layer operations being performed "below" the layer operations by the protocol processing circuit 914 in the network protocol stack.These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions. The modem platform 910 may further include transmit circuitry 918, receive circuitry 920, RF circuitry 922, and an RF front end (RFFE) 924, which may include or be connected to one or more antenna panels 926. Briefly, the transmit circuitry 918 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 920 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 922 may include low-noise amplifiers, power amplifiers, power tracking components, etc.; and the RFFE 924 may include filters (e.g., surface / bulk acoustic wave filters), switches, antennas, tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components in the transmit circuitry 918, receive circuitry 920, RF circuitry 922, RFFE 924, and antenna panel 926 (collectively referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communications are TDM or FDM, at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be configured in multiple parallel transmit / receive chains, located on the same or different chips / modules, etc. In some embodiments, the protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.UE reception may be established by and through the antenna panel 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914. In some embodiments, the antenna panel 926 may receive transmissions from the AN 904 by way of receive-beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 926.

[0131] UE transmissions may be established by and through protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panel 926. In some embodiments, the transmit components of the UE 904 may apply spatial filters to data to be transmitted to form transmit beams radiated by antenna elements of the antenna panel 926. Similar to the UE 902, the AN 904 may include a host platform 928 coupled to a modem platform 930. The host platform 928 may include an application processing circuit 932 coupled with the protocol processing circuitry 934 of the modem platform 930. The modem platform may further include digital baseband circuitry 936, transmit circuitry 938, receive circuitry 940, RF circuitry 942, RFFE circuitry 944, and antenna panel 946. The components of the AN 904 may be similar to and substantially interchangeable with similarly named components of the UE 902. In addition to performing data transmission / reception as described above, the components of AN908 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. 10 is a block diagram illustrating components that, in some example embodiments, are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies described herein. Specifically, FIG. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is employed, a hypervisor 1002 may run and provide an execution environment for one or more network slices / sub-slices to use the hardware resources 1000.

[0132] Processor 1010 may include, for example, processor 1012 and processor 1014. Processor 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

[0133] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0134] The communications resources 1030 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1004 or one or more databases 1006 or other network elements over the network 1008. For example, the communications resources 1030 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth (or Bluetooth Low Energy) components, Wi-Fi (or Bluetooth Low Energy) components, and other communications components.

[0135] The instructions 1050 may include software, a program, an application, an applet, an app, or other executable code for causing at least one of the processors 1010 to perform any one or more of the methods described herein. The instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., in the processor's cache memory), the memory / storage device 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral device 1004 or the database 1006. Thus, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.

[0136] [Example Procedure] In some embodiments, an electronic device, network, system, chip, or component of Figures 8-10 or some other figures herein, or a portion or implementation thereof, may be configured to perform one or more processes, techniques, or methods, or portions thereof, described herein. One such process 1100 is shown in Figure 11. For example, process 1100 may include, at 1102, determining uplink control information (UCI) for a physical uplink control channel (PUCCH). In some embodiments, the PUCCH may have PUCCH format 1, 3, or 4.

[0137] At 1104, the process 1100 may further include determining a sequence for transmitting the PUCCH based on the UCI. For example, the sequence may be determined based on a payload of the UCI. In some embodiments, the sequence may be determined from multiple orthogonal sequences. The multiple sequences may be associated with a group identity. In some embodiments, the sequences may include different root indices and / or cyclic prefixes. In some embodiments, the sequence may be a Zadoff-Chu (ZC) sequence.

[0138] In various embodiments, process 1100 may be performed by a UE or a portion thereof (eg, baseband circuitry of the UE).

[0139] 12 illustrates another process 1200 in accordance with various embodiments. Process 1200 may be performed by a UE or a portion thereof. Process 1200 may include, at 1202, determining uplink control information (UCI) payload information for a physical uplink control channel (PUCCH) having PUCCH format 1.

[0140] At 1204, process 1200 may further include determining a sequence for transmission of the PUCCH based on the UCI payload information. At 1206, process 1200 may further include mapping the determined sequence to allocated resources of PUCCH format 1 for transmission.

[0141] 13 illustrates another process 1300 in accordance with various embodiments. Process 1300 may be performed by a UE or a portion thereof. Process 1300 may include, at 1302, determining uplink control information (UCI) payload information for a physical uplink control channel (PUCCH) having PUCCH format 3.

[0142] At 1304, process 1300 may further include initializing a sequence based on some or all of the UCI payload information. At 1306, process 1300 may further include encoding a PUCCH for transmission based on the initialized sequence.

[0143] 14 shows another process 1400 in accordance with various embodiments. Process 1400 may be performed by a UE or a portion thereof. At 1402, process 1400 may include determining one or more uplink control information (UCI) bits of a physical uplink control channel (PUCCH). At 1404, process 1400 may further include encoding the PUCCH for transmission in a resource allocation for PUCCH format 1, 3, or 4 without a demodulation reference signal (DMRS).

[0144] For one or more embodiments, at least one of the components depicted in one or more of the above-mentioned drawings may be configured to perform one or more of the operations, techniques, processes, and / or methods described in the example section below. For example, baseband circuitry as described above in connection with one or more of the above-mentioned drawings may be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, a base station as described above in connection with one or more of the above-mentioned drawings, a network element, etc. may be configured to operate according to one or more of the examples described below in the example section. [example]

[0145] Additional examples of the presently described embodiments include the following non-limiting implementations: Each of the following non-limiting examples may stand alone or may be combined in any permutation or with any one or more of the other examples provided below or throughout this disclosure.

[0146] Example A01 includes a wireless communication method for a fifth generation (5G) or new radio (NR) system, the method including a step in which a user equipment (UE) transmits a physical uplink control channel (PUCCH) format 1 and / or a PUCCH format 3 without an associated demodulation reference signal (DMRS).

[0147] Example A02 includes the method of Example A01 and / or any other example herein, where for PUCCH format 1 without DMRS, the sequence y(n) assigned to the original data symbols is

number

number

[0148] Example A03 includes the method of Example A01 and / or any other example herein, where a time-domain orthogonal cover code (OCC) can be applied to odd / uplink control information (UCI1) and even / UCI0 symbols, respectively, when intra-slot frequency hopping is disabled.

[0149] Example A04 includes the method of Example A01 and / or any other example herein, where, if intra-slot frequency hopping is enabled, OCC is applied to each odd and even UCI symbol in each hop.

[0150] Example A05 includes the method of Example A01 and / or some other examples herein, where the complex number d(0) may be replaced by a sequence from a sequence set where the sequences are a one-to-one mapping to the values ​​of the UCI bits.

[0151] Example A06 includes the method of Example A01 and / or any other example herein, where multiple orthogonal sequences can be defined for PUCCH format 1 transmission, and where different UCI payloads are mapped to sequences from the orthogonal sequences.

[0152] Example A07 includes the method of Example A01 and / or some other examples herein, where the sequence may be directly mapped to resources allocated to PUCCH format 1.

[0153] Example A08 includes the method of Example A01 and / or some other examples herein, where the orthogonal sequence may be defined as a combination of a length-12 sequence in the frequency domain and an OCC in the time domain.

[0154] Example A09 includes the method of Example A01 and / or some other examples herein, where the OCC code can be extended to support lengths greater than 7, and where the OCC code can be generated based on a discrete Fourier transform (DFT)-based orthogonal code.

[0155] Example A10 includes the method of Example A01 and / or any other example herein, where the sequence-based PUCCH format 1 transmission may be divided into multiple groups, where the number of symbols in each group is not greater than 7.

[0156] Example A11 includes the method of Example A01 and / or some other examples herein, where the UE can be configured with two different cyclic shift values ​​over frequency and two different OCC indices over time for the four orthogonal sequences.

[0157] Example A12 includes the method of Example A01 and / or any other example herein, wherein for PUCCH format 3, if the UCI payload size is smaller than K bits, after encoding and modulation, the modulated symbols are directly mapped to resources allocated for PUCCH transmission, where K may be predetermined herein or configured by higher layers via NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling.

[0158] Example A13 includes the method of Example A01 and / or any other example herein, where multiple sequences may be defined for PUCCH format 3 transmission when the UCI payload size is less than K bits.

[0159] Example A14 includes the method of Example A01 and / or any other example herein, where the multiple long sequences can be generated based on a pseudo-random binary sequence (PRBS) of section 5.2.1 of 3GPP TS 38.211 for PUCCH format 3.

[0160] Example A15 includes the method of Example A01 and / or any other example herein, wherein the initial seed for generating the long sequence is:

number

number

number

[0161] Example A16 includes the method of Example A01 and / or some other examples herein, where an initial seed for the generation of the long sequence can be defined as a function of one or more of the following parameters: a radio network temporary identifier (RNTI), a virtual cell ID or scrambling ID, and / or UCI payload information, where the initial seed for the generation of the long sequence is

number

number

number

[0162] Example A17 includes the method of Example A01 and / or any other example herein, where an initial seed for generating the long sequence can be defined according to one or more of the following parameters: a radio network temporary identifier (RNTI), a virtual cell ID, or a scrambling ID, and where a different cyclic shift based on UCI payload information can be applied to generate the new PUCCH format 3 sequence.

[0163] Example A18 includes the method of Example A17 and / or any other example herein, wherein the initial seed for generating the long sequence is:

number

[0164] Example A19 includes the method of Example A17 and / or any other example herein, wherein the long sequence of the one or more long sequences comprises:

number

[0165] Example A20 includes the method of Example A19 and / or any other example herein, wherein M bit may be equal to the number of bits mapped to the PUCCH resource when pi / 2 BPSK is used.

[0166] Example A21 includes the method of Example A01 and / or any other example herein, where for new PUCCH format 3, a sequence based on either the long sequence or the short sequence in each OFDM symbol can be transmitted using pi / 2 BPSK modulation based on a DFT-s-OFDM waveform.

[0167] Example B01 includes a method that includes transmitting a physical uplink control channel (PUCCH) transmission using a PUCCH format.

[0168] Example B02 includes the method of Example B01 and / or any other example herein, where the PUCCH format is PUCCH format 1, BPSK is used as modulation for 1-bit HARQ-ACK feedback, QPSK is used as modulation for 2-bit HARQ-ACK feedback, the modulated symbols are multiplied with a length-12 sequence and an orthogonal cover code (OCC) in the frequency domain, and the modulated sequence is directly mapped to the allocated resources configured for PUCCH format 1.

[0169] Example B03 includes the method of Example B02 and / or any other example herein, where transmitting includes not transmitting the DMRS on resources allocated to PUCCH format 1.

[0170] Example B04 includes the method of Example B03 and / or any other example herein, where for PUCCH format 1 without DMRS, the sequence y(n) assigned to the original data symbols is

number

number

[0171] Example B05 includes the method of Examples B02-B04 and / or any other example herein, further including applying a time-domain orthogonal cover code (OCC) to odd UCI (UCI1) and even UCI (UCI0) symbols when intra-slot frequency hopping is disabled.

[0172] Example B06 includes the method of Examples B02-B05 and / or any other example herein, and further includes applying OCC to odd and even UCI symbols in each hop when intra-slot frequency hopping is enabled.

[0173] Example B07 includes the methods of Examples B05-B06 and / or some other examples herein, where the same or different OCC sequence indexes can be configured for odd UCI and even UCI symbols of PUCCH format 1, and a separate timeDomainOCC is defined when different OCC sequence indexes are configured for odd and even UCI symbols of PUCCH format 1.

[0174] Example B08 includes the method of Examples B02-B07 and / or any other example herein, and further includes replacing the complex number d(0) with a sequence from a sequence set, where the sequence is a one-to-one mapping to the value of the UCI bit.

[0175] Example B09 includes the method of Examples B02-B08 and / or any other example herein, wherein multiple orthogonal sequences can be defined for transmission of PUCCH format 1, and wherein different UCI payloads can be mapped to sequences from the orthogonal sequences and / or the sequences can be directly mapped to resources allocated to PUCCH format 1.

[0176] Example B10 includes the method of Example B09 and / or any other example herein, where at least one of the orthogonal sequences is defined as a combination of a length-12 sequence in the frequency domain and an OCC in the time domain.

[0177] Example B11 includes the method of Examples B02 to B09 and / or some other examples herein, where the OCC code can be extended to support lengths greater than 7, and where the OCC code can be generated based on a Discrete Fourier Transform (DFT)-based orthogonal code.

[0178] Example B12 includes the methods of Examples B02-B11 and / or some other examples herein, where the sequence-based PUCCH format 1 transmission can be divided into multiple groups, where each group has no more than 7 symbols.

[0179] Example B13 includes the method of Examples B02-B12 and / or any other example herein, and further includes receiving a configuration having two different cyclic shift values ​​in frequency and two different OCC indices in time for the four orthogonal sequences.

[0180] Example B14 includes the method of Examples B02-B13 and / or any other example herein, where PUCCH format 1 is replaced with PUCCH format 3 in any of the above examples.

[0181] Example B15 includes the method of Example B01 and / or any other example herein, where the PUCCH format is PUCCH Format 3, and the method further includes, after encoding and modulation, directly mapping the modulated symbols to resources allocated for the PUCCH transmission if the UCI payload size is less than K bits.

[0182] Example B16 includes the method of Example B01, B15, and / or any other example herein, where the PUCCH format is PUCCH format 3, and the multiple sequences are defined for transmission of PUCCH format 3 when the UCI payload size is less than K bits.

[0183] Example B17 includes the method of Examples B15-B16 and / or any other example herein, where K is a predetermined value or is configured by higher layers via NR Minimum Remaining System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling.

[0184] Example B18 includes the method of Examples B01, B15-B17 and / or any other example herein, where the PUCCH format is PUCCH Format 3, and the method further includes generating a plurality of long sequences using low peak-to-average power ratio (PAPR) sequence generation type 1 for a base sequence having a length of 36 or greater.

[0185] Example B19 includes the methods of Examples B15-B18 and / or any other examples herein, where the pseudo-random sequence c(i) of the generated sequence is specified by clause 5.2.1 of 3GPP TS 38.211 for PUCCH format 3.

[0186] Example B20 includes the method of Example B19 and / or any other example herein, wherein the pseudo-random sequence c(i) is

number

number

number

[0187] Example B21 includes the method of Examples B01 to B20 and / or any other example herein, wherein the initial seed for generating the one or more long sequences is a function of one or more of a Radio Network Temporary Identifier (RNTI), a virtual cell ID, a scrambling ID, and / or UCI payload information.

[0188] Example B22 includes the method of Example B21 and / or any other example herein, wherein the initial seed for generating the one or more long sequences is:

number

number

number

[0189] Example B23 includes the method of Example B21 and / or any other example herein, where a different cyclic shift based on UCI payload information is applied to generate the new PUCCH format 3 sequence.

[0190] Example B24 includes the method of Example B23 and / or any other example herein, wherein the initial seed for generating the one or more long sequences is:

number

[0191] Example B24 includes the method of Example B23 and / or any other example herein, wherein the long sequence of the one or more long sequences comprises:

number

[0192] Example B25 includes the method of Example B24 and / or any other example herein, wherein M bit may be equal to the number of bits mapped to the PUCCH resource when pi / 2 BPSK is used.

[0193] Example B26 includes the method of Examples B01-B25 and / or any other example herein, where the sequence of New PUCCH Format 3 is a long sequence or a short sequence for each OFDM symbol, and New PUCCH Format 3 is transmitted using pi / 2 BPSK modulation based on a DFT-s-OFDM waveform.

[0194] Example B27 includes the method of Examples B01-B26 and / or any other example herein, where the method is performed by a user equipment (UE) or a next generation NodeB (gNB).

[0195] Example C1 may include a wireless communication method for a fifth generation (5G) or new radio (NR) system, including:

[0196] Transmitting, by the UE, a sequence representing uplink control information (UCI) payload information on a physical uplink control channel (PUCCH).

[0197] Example C2 may include the method of Example C1 or some other example herein, where the PUCCH includes PUCCH formats 1, 3, and 4.

[0198] Example C3 may include the method of Example C1 or some other example herein, where multiple orthogonal sequences may be defined for transmission of PUCCH format 1, where the sequences may be directly mapped to resources allocated to PUCCH format 1 without associated DMRS according to UCI payload information.

[0199] Example C4 may include the method of Example C1 or some other example herein, where Zadoff-Chu (ZC) sequences with different root indices may be used for sequence generation for PUCCH format 1.

[0200] Example C5 may include the method of Example C1 or some other example herein, where, assuming UCI payload information is n, the sequence group identity parameter u may be generated according to the UCI payload information n, where n may be bits {0,1} for a 1-bit UCI payload and may be bits {0,1,2,3} for a 2-bit UCI payload.

[0201] Example C6 may include the method of Example C1, where Zadoff-Chu (ZC) sequences with different cyclic shifts may be used for sequence generation of PUCCH format 1.

[0202] Example C7 may include the method of Example C1 or some other example herein, where, for PUCCH format 3, the scrambling sequence may be initialized according to some or all of the UCI payload information.

[0203] Example C8 may include the method of Example C1 or some other example herein, where, for determining the initial setting value of scrambling sequence generation of PUCCH format 3, the following formula can be used.

Number

Number

[0204] Example C9 may include the method of Example C1 or some other example herein, where two scrambling IDs may be configured for PUCCH format 3, where the first scrambling ID may be applied when the UCI payload is n < N / 2, and the second scrambling ID may be applied when the UCI payload is

Number

[0205] Example C10 includes the method of Example C1 or some other example herein, where, after encoding, the modulated symbols for PUCCH format 3 may be multiplied by a sequence that depends on the UCI payload information.

[0206] Example C11 may include the method of Example C1 or some other example herein, where the sequence representing UCI payload information is transmitted on symbols allocated to UCI transmission, and where the DMRS symbols are present in PUCCH format 3.

[0207] Example C12 may include the method of example C1 or some other example herein, where the first column for Reed-Muller (RM) code generation may be removed. In this case, the number of input bits may be 3 to 10 bits.

[0208] Example C13 is determining uplink control information (UCI) for a physical uplink control channel (PUCCH); and determining a sequence for transmitting the PUCCH based on the UCI.

[0209] Example C14 may include the method of Example C13 or some other example herein, further including mapping the sequence to the allocated resources of the PUCCH format without an associated DMRS.

[0210] Example C15 may include the method of Examples C13-C14 or some other examples herein, where the PUCCH has PUCCH format 1, 3, or 4.

[0211] Example C16 may include the method of Examples C13-C15 or some other examples herein, further including determining a sequence from one of a plurality of orthogonal sequences configured for transmitting a PUCCH of the same format.

[0212] Example C17 may include the method of example C16, where a plurality of orthogonal sequences are associated with respective group identities.

[0213] Example C18 may include the method of Examples C16-C17 or some other examples herein, where the plurality of sequences includes Zadoff-Chu (ZC) sequences with different root indices.

[0214] Example C19 may include the method of Examples C13-C18 or some other examples herein, where for UCI payload information n, the sequence group identity parameter u is generated according to the UCI payload information n, where n may be bits {0,1} for a 1-bit UCI payload and bits {0,1,2,3} for a 2-bit UCI payload.

[0215] Example C20 can include the method of Examples C16-C17 or some other examples herein, where the plurality of sequences includes Zadoff-Chu (ZC) sequences with different cyclic shifts.

[0216] Example C21 may include the method of Examples C13-C20 or some other examples herein, where the sequence is initialized according to partial or complete UCI payload information of the UCI.

[0217] Example C22 may include the method of Examples C13-C21 or some other example herein, where the default value for the sequence is:

number

number

[0218] Example C23 may include the method of Examples C13 - C22 or some other examples herein, and further, based on the first scrambling ID when the UCI payload n < N / 2 and based on the second scrambling ID when the UCI payload

Number

[0219] Example C24 may include the method of Examples C13 - C23 or some other examples herein, and further includes the step of multiplying the encoded symbols of the PUCCH by a sequence.

[0220] Example C25 may include the method of Examples C21 - C24 or some other examples herein, where the PUCCH is PUCCH format 3.

[0221] Example C26 may include the method of Examples C21 - C25 or some other examples herein, and further includes the step of transmitting the PUCCH based on the sequence.

[0222] Example C27 may include the method of Examples C13 - C26 or some other examples herein, where the sequence is transmitted on the symbols assigned for UCI transmission, and where the DMRS symbols are present within the PUCCH format 3.

[0223] Example C28 may include the method of Examples C13 - C27 or some other examples herein, where the sequence is determined based on the Reed - Muller (RM) code generation table presented herein.

[0224] Example C29 may include the method of Example C28 or some other examples herein, where the number of input bits of the sequence is from 3 to 10 bits.

[0225] Example D1 may include one or more non-transitory computer-readable media (NTCRM) having stored thereon instructions that, when executed by one or more processors, cause a user equipment (UE) to determine uplink control information (UCI) payload information for a physical uplink control channel (PUCCH), determine a sequence for transmission of the PUCCH based on the UCI payload information, and encode the PUCCH for transmission based on the determined sequence.

[0226] Example D2 may include one or more NTCRMs of Example D1, where the instructions, when executed, further cause the UE to map the sequence to assigned resources of a PUCCH format without an associated demodulation reference signal (DMRS).

[0227] Example D3 may include one or more NTCRMs of Example D1, where determining the sequence includes determining a root index of the sequence based on the UCI payload information.

[0228] Example D4 may include one or more NTCRMs of example D1, where determining the sequence includes determining a cyclic prefix of the sequence based on the UCI payload information.

[0229] Example D5 may include one or more NTCRMs of any of Examples D1-D4, where the PUCCH has PUCCH format 1 and the sequence is a Zadoff-Chu sequence.

[0230] Example D6 may include one or more NTCRMs of example D1, where the sequence is initialized according to some or all of the UCI payload information.

[0231] Example D7 may include one or more NTCRMs of example D6, where the instructions, when executed, further:

number

[0232] Example D8 may include one or more NTCRMs of Example D7, where the UCI payload information corresponds to the value n, where N is the number of UCI bits, and where the sequence is determined based on the first scrambling ID when n < N / 2 and is determined based on the second scrambling ID when n ≧ N / 2.

[0233] Example D9 may include one or more NTCRMs of Example D1 or D6-D8, where the instruction, when executed, further causes the UE to multiply the determined sequence by the encoded symbols of the PUCCH.

[0234] ?? Example D10 may include one or more NTCRMs of any of Examples D6-D9, where the PUCCH has PUCCH format 3.

[0235] Example E1 may include one or more non-transitory computer-readable media (NTCRMs) storing instructions which, when executed by one or more processors, cause a user equipment (UE) to determine uplink control information (UCI) payload information of a physical uplink control channel (PUCCH) having PUCCH format 1, determine a sequence for transmission of the PUCCH based on the UCI payload information, and map the determined sequence to the allocated resources of the PUCCH format 1 for transmission.

[0236] Example E2 may include one or more NTCRMs of Example E1, where the PUCCH is transmitted without a demodulation reference signal (DMRS).

[0237] Example E3 may include one or more NTCRMs of any of Examples E1-E2, where the sequence is a Zadoff-Chu sequence.

[0238] Example E4 may include one or more NTCRMs of any of Examples E1-E3, where the sequence is determined from a set of sequences having at least one of different root indices, different cyclic prefixes, or different orthogonal cover codes (OCCs).

[0239] Example E5 may include one or more NTCRMs of any of Examples E1-E4, wherein determining the sequence includes determining a sequence group identity parameter of the sequence based on the UCI payload information.

[0240] Example E6 may include one or more NTCRMs of example E5, wherein the sequence group identity parameter u is:

number

number

number

number

[0241] Example E7 may include one or more NTCRMs of any of Examples E1-E6, where determining the sequence includes determining a cyclic prefix of the sequence based on the UCI payload information.

[0242] Example E8 may include one or more of Examples E1 - E7, where the instructions, when executed, further cause the UE to apply respective time domain orthogonal cover codes (OCCs) to the odd and even UCI symbols of the PUCCH.

[0243] Example E9 may include an apparatus implemented in a user equipment (UE), the apparatus including a radio frequency (RF) interface and a processor circuit coupled to the RF interface, the processor circuit determining uplink control information (UCI) payload information of a physical uplink control channel (PUCCH) having PUCCH format 3, initializing a sequence based on a part or all of the UCI payload information, and encoding the PUCCH for transmission based on the initialized sequence.

[0244] Example E10 may include the apparatus of Example E9, where the processor circuit

Number

[0245] Example E11 may include the apparatus of Example E9, where the UCI payload information corresponds to a value n, and the sequence is determined based on a first scrambling ID when n < N / 2 and is determined based on a second scrambling ID when n ≧ N / 2, and N is the number of UCI bits.

[0246] Example E12 may include any one of the apparatuses of Examples E9 - E11, where the processor circuit multiplies a determined sequence by encoded symbols of the PUCCH.

[0247] Example E13 may include one or more non-transitory computer-readable media (NTCRM) having stored thereon instructions that, when executed by one or more processors, cause a user equipment (UE) to determine one or more uplink control information (UCI) bits of a physical uplink control channel (PUCCH) and encode the PUCCH for transmission in a resource allocation for PUCCH format 1, 3, or 4 without a demodulation reference signal (DMRS).

[0248] Example E14 may include one or more NTCRMs of example E13, wherein when the one or more UCI bits include 1 bit, then the PUCCH is encoded using binary phase shift keying (BPSK), and when the one or more UCI bits include 2 bits, then the PUCCH is encoded using quadrature phase shift keying (QPSK).

[0249] Example E15 may include one or more NTCRMs of example E14, where the modulated symbols are multiplied with a length-12 sequence in the frequency domain and an orthogonal cover code (OCC), and then directly mapped to the allocated resources configured for PUCCH format 1.

[0250] Example E16 may include one or more NTCRMs of any of Examples E13-E15, wherein the PUCCH has PUCCH Format 1, and the PUCCH comprises original data symbols multiplied by complex-valued symbols d(0) obtained from the one or more UCI bits.

number

number

[0251] Example E17 may include one or more NTCRMs of any of Examples E13-E16, wherein encoding the PUCCH includes applying respective time-domain orthogonal cover codes (OCCs) to odd and even UCI symbols.

[0252] Example E18 may include one or more NTCRMs of any of Examples E13-E17, wherein encoding the PUCCH includes generating an OCC based on a Discrete Fourier Transform (DFT) orthogonal code to support sequence lengths greater than 7 symbols.

[0253] Example E19 may include one or more NTCRMs of any of Examples E13-E18, where the instructions, when executed, further cause the UE to receive configuration information of multiple orthogonal sequences for PUCCH format 1 and select a first sequence from the multiple orthogonal sequences based on the one or more UCI bits, and the PUCCH is encoded based on the selected first sequence.

[0254] Example E20 may include one or more NTCRMs of example E19, where the configuration information includes a cyclic shift and an OCC index of each of the orthogonal sequences.

[0255] Example Z01 includes an apparatus including means for performing one or more elements of a method described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or any other method or process described herein.

[0256] Example Z02 includes one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or any other method or process described herein.

[0257] Example Z03 includes an apparatus having logic, modules, or circuitry for performing one or more elements of a method described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or any other method or process described herein.

[0258] Example Z04 includes any method, technique, or process described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or any part or portion thereof.

[0259] Example Z05 includes an apparatus that includes one or more processors and one or more computer-readable media that include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20.

[0260] Example Z06 includes a signal described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or a portion or part thereof.

[0261] Example Z07 includes a datagram, packet, frame, segment, protocol data unit (PDU), or message described in or relating to, or a portion or part of, any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or as otherwise described in this disclosure.

[0262] Example Z08 includes a signal encoded with data described in or relating to, or a portion or part of, any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or as otherwise described in this disclosure.

[0263] Example Z09 includes a signal encoded using a datagram, packet, frame, segment, protocol data unit (PDU), or message described in or relating to, or a portion or part of, any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20, or otherwise described in this disclosure.

[0264] Example Z10 includes an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process, or portion thereof, described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20.

[0265] Example Z11 includes a computer program including instructions, where execution of the program by a processing element causes the processing element to perform a method, technique, or process, or portion thereof, described in or related to any of Examples A01-A21, B01-B27, C1-C29, D1-D10, E1-E20.

[0266] Example Z12 includes signals in a wireless network as shown and described herein.

[0267] Example Z13 includes a method of communicating in a wireless network as shown and described herein.

[0268] Example Z14 includes a system for providing wireless communication as shown and described herein.

[0269] Example Z15 includes a device that provides wireless communication as shown and described herein.

[0270] Any of the above examples may be combined with any other example (or combination of examples) unless expressly stated otherwise. The above description of one or more implementations has been provided for illustration and description, and is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0271] Abbreviation Unless used differently herein, the terms, definitions, and abbreviations may conform to those defined in 3GPP® TR 21.905 v16.0.0(2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments described herein: 3GPP (registered trademark) Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network ACK Acknowledgement AF Application Function AM Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function AN: Access Network ANR Automatic Adjacency AP Application Protocol, Antenna Port, Access Point API Application Programming Interface APN Access Point Name ARP Allocation and Retention Priority ARQ Automatic Repeat Request AS Access Stratum ASN.1 Abstract Syntax Notation One AUSF Authentication Server Function AWGN Additive White Gaussian Noise BAP Backhaul Adaptation Protocol BCH Broadcast Channel BER Bit Error Ratio BFD Beam Failure Detection BLER Block Error Rate BPSK Binary Phase Shift Keying BRAS Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identity CA Carrier Aggregation, Certification Authority CAPEX capital expenditure (CAPital EXpenditure) CBRA Contention Based Random Access CC Component Carrier, Country Code, Cryptographic Checksum CCA Clear Channel Assessment CCE Control Channel Element CCCH Common Control Channel CE Coverage Enhancement CDM Content Delivery Network CDMA Code-Division Multiple Access CFRA Contention Free Random Access CG Cell Group CI Cell Identity CID Cell-ID (e.g., positioning method) CIM Common Information Model CIR Carrier to Interference Ratio CK Cipher Key CM Connection Management, Conditional Mandatory CMAS Commercial Mobile Alert Service CMD Command CMS Cloud Management System CO Conditional Optional CoMP (Coordinated Multi-Point) CORESET Control Resource Set COTS Commercial Off-The-Shelf CP Control Plane, Cyclic Prefix, Connection Point CPD Connection Point Descriptor CPE Customer Premise Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU CSI processing unit, Central Processing Unit C / R Command / Response field bit CRAN Cloud Radio Access Network, Cloud RAN CRB Common Resource Block CRC Cyclic Redundancy Check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS Circuit Switched CSAR Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI-RS CSI Reference Signal CSI-RSRP CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS Common Search Space, Cell-specific Search Space CTS Clear-to-Send CW Codeword CWS Contention Window Size D2D Device-to-Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Deployment Flavor DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation Reference Signal DN Data Network DRB Data Radio Bearer DRS Discovery Reference Signal DRX Discontinuous Reception DSL Domain Specific Language, Digital Subscriber Line DSLAM DSL Access Multiplexer DwPTS Downlink Pilot Time Slot E-LAN ​​Ethernet Local Area Network E2E End-to-End ECCA Extended Clear Channel Assessment, Extended CCA ECCE Enhanced Control Channel Element, Enhanced CCE ED Energy Detection EDGE Enhanced Datarates for GSM Evolution EGMF Exposure Governance Management Function EGPRS Enhanced GPRS EIR Equipment Identity Register eLAA Enhanced Licensed Assisted Access, enhanced LAA EM Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB Evolved NodeB, E-UTRAN Node B EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel EPRE Energy per resource element EPS Evolved Packet System EREG Enhanced REG, enhanced resource element groups ETSI European Telecommunications Standards Institute ETWS Earthquake and Tsunami Warning System eUICC embedded UICC, embedded Universal Integrated Circuit Card E-UTRA Evolved UTRA E‐UTRAN Evolved UTRAN EV2X Enhanced V2X F1AP F1 Application Protocol F1-C F1 Control plane interface F1-U F1 User plane interface FACCH Fast Associated Control Channel FACCH / F Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate FACH Forward Access Channel FAUSCH Fast Uplink Signalling Channel FB Functional Block FBI Feedback Information FCC Federal Communications Commission FCCH Frequency Correction Channel FDD Frequency Division Duplex FDM Frequency Division Multiplex FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS For Further Study FFT Fast Fourier Transformation feLAA further enhanced Licensed Assisted Access, further enhanced LAA FN Frame Number FPGA Field-Programmable Gate Array FR Frequency Range G-RNTI GERAN Radio Network Temporary Identity GERAN GSM EDGE RAN, GSM EDGE Radio Access Network GGSN Gateway GPRS Support Node GLONASS Global Navigation Satellite System (GLObal'naya NAvigatsionnaya Sputnikovaya Sistema) gNB Next Generation NodeB gNB-CU gNB-centralized unit, Next Generation NodeB centralized unit gNB‐DU gNB-distributed unit, Next Generation NodeB distributed unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GSM (Registered Trademark) Global System for Mobile Communications, Groupe Special Mobile GTP GPRS Tunneling Protocol GTP-U GPRS Tunneling Protocol for User Plane GTS Sleep Signal (Go To Sleep Signal) (WUS related) GUMMEI Globally Unique MME Identifier GUTI Globally Unique Temporary UE Identity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO Handover HFN HyperFrame Number HHO Hard Handover HLR Home Location Register HN Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA High Speed ​​Downlink Packet Access HSN Hopping Sequence Number HSPA High Speed ​​Packet Access HSS Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP Hyper Text Transfer Protocol HTTPS HyperText Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443) I-Block Information Block ICCID Integrated Circuit Card Identification IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID (identity, identifier) IDFT Inverse Discrete Fourier Transform IE Information element IBE In-Band Emission IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IM Interference Measurement, Intermodulation, IP Multimedia IMC IMS Credentials IMEI International Mobile Equipment Identity IMGI International mobile group identity IMPI IP Multimedia Private Identity IMPU IP Multimedia Public Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT Internet of Things IP Internet Protocol IPsec IP Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network IP-M IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS In Sync IRP Integration Reference Point ISDN Integrated Services Digital Network ISIM IM Services Identity Module ISO International Organisation for Standardisation ISP Internet Service Provider IWF Interworking Function I-WLAN Interworking WLAN Constraint length of the convolutional code, USIM Individual key kB Kilobyte (1000 bytes) kbps kilo-bits per second Kc Ciphering key Ki Individual subscriber authentication key KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps kilo-symbols per second KVM Kernel Virtual Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (Data Link Layer) L3 Layer 3 (Network Layer) LAA Licensed Assisted Access LAN Local Area Network LBT Listen Before Talk LCM Lifecycle Management LCR Low Chip Rate LCS Location Services LCID Logical Channel ID LI Layer Indicator LLC Logical Link Control, Low Layer Compatibility LPLMN Local PLMN LPP LTE Positioning Protocol LSB Least Significant Bit LTE Long Term Evolution LWA LTE-WLAN aggregation LTE / WLAN Radio Level Integration with IPsec Tunnel LTE Long Term Evolution M2M Machine-to-Machine MAC Medium Access Control (protocol layer context) MAC Message authentication code (security / cryptographic context) MAC-A MAC used for authentication and key agreement (TSG T WG3 context) MAC-I MAC used for data integrity of signaling messages (TSG T WG3 context) MANO Management and Orchestration MBMS Multimedia Broadcast and Multicast Service MBSFN Multimedia Broadcast multicast service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and coding scheme MDAF Management Data Analytics Function MDAS Management Data Analytics Service MDT Minimization of Drive Tests ME Mobile Equipment MeNB Master eNB MER Message Error Ratio MGL Measurement Gap Length MGRP Measurement Gap Repetition Period MIB Master Information Block, Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Centre MM Mobility Management MME Mobility Management Entity MN Master Node MnS Management Service MO Measurement Object, Mobile Originated MPBCH MTC Physical Broadcast Channel MPDCCH MTC Physical Downlink Control CHannel MPDSCH MTC Physical Downlink Shared CHannel MPRACH MTC Physical Random Access CHannel MPUSCH MTC Physical Uplink Shared Channel MPLS MultiProtocol Label Switching MS Mobile Station MSB Most Significant Bit MSC Mobile Switching Centre MSI Minimum System Information, MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Terminated, Mobile Termination MTC Machine-Type Communications mMTC (massive MTC, massive Machine-Type Communications) MU-MIMO Multi-User MIMO MWUS MTC wake-up signal, MTC WUS NACK Negative Acknowledgement NAI Network Access Identifier NAS Non-Access Stratum, Non-Access Stratum layer NCT Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV Network Functions Virtualization NFVI NFV Infrastructure NFVO NFV Orchestrator NG Next Generation, Next Gen NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB Narrowband MIB NPBCH Narrowband Physical Broadcast CHannel NPDCCH Narrowband Physical Downlink Control CHannel NPDSCH Narrowband Physical Downlink Shared Channel NPRACH Narrowband Physical Random Access CHannel NPUSCH Narrowband Physical Uplink Shared CHannel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR New Radio, Neighbor Relation NRF NF Repository Function NR Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD Network Service Descriptor NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single NSSAI (Single-NSSAI) NSSF Network Slice Selection Function NW Network NWUS Narrowband wake-up signal, Narrowband WUS NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical channel Data Unit-type 2 OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OOB Out-of-band OOS Out of Sync OPEX Operating Expense OSI Other System Information OSS Operations Support System OTA (over-the-air) PAPR Peak-to-Average Power Ratio PAR Peak to Average Ratio PBCH Physical Broadcast Channel PC Power Control, Personal Computer PCC Primary Component Carrier, Primary CC PCell Primary Cell PCI Physical Cell ID, Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF Policy Control and Charging Rules Function PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layer PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDN Packet Data Network, Public Data Network PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network PIN Personal Identification Number PM Performance Measurement PMI Precoding Matrix Indicator PNF Physical Network Function PNFD Physical Network Function Descriptor PNFR Physical Network Function Record POC PTT over Cellular PP, PTP Point-to-Point PPP Point-to-Point Protocol PRACH Physical RACH PRB Physical resource block PRG Physical resource block group ProSe Proximity Services, Proximity-Based Services PRS Positioning Reference Signal PRR Packet Reception Radio PS Packet Services PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSFCH Physical Sidelink Feedback Channel PSSCH Physical Sidelink Shared Channel PSCell Primary SCell PSS Primary Synchronization Signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM Quadrature Amplitude Modulation QCI QoS class of identifier QCL Quasi co-location QFI QoS Flow ID, QoS Flow Identifier QoS Quality of Service QPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-Zenith Satellite System RA-RNTI Random Access RNTI RAB Radio Access Bearer, Random Access Burst RACH Random Access Channel Remote Authentication Dial In RADIUS User Service RAN Radio Access Network RAND Random number (used for authentication) RAR Random Access Response RAT Radio Access Technology RAU Routing Area Update RB Resource block, Radio Bearer RBG Resource block group REG Resource Element Group Rel Release REQ Request (REQuest) RF Radio Frequency RI Rank Indicator RIV Resource indicator value RL Radio Link RLC Radio Link Control, Radio Link Control layer RLC AM RLC Acknowledged Mode RLC UM RLC Unacknowledged Mode RLF Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI, Remaining Minimum System Information (Remaining MSI) RN Relay Node RNC Radio Network Controller RNL Radio Network Layer RNTI Radio Network Temporary Identifier ROHC Robust Header Compression RRC Radio Resource Control, Radio Resource Control Layer RRM Radio Resource Management RS Reference Signal RSRP Reference Signal Received Power (Reference Signal) RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP Real Time Protocol RTS Ready-To-Send RTT Round Trip Time Rx Reception, Receiving, Receiver S1AP S1 Application Protocol S1-MME S1 (S1 Application Protocol) for control plane S1-U S1 for the user plane S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC SCell Secondary Cell SC-FDMA Single Carrier Frequency Division Multiple Access SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol layer SDL Supplementary Downlink SDNF Structured Data Storage Network Function SDP Session Description Protocol SDSF Structured Data Storage Function SDU Service Data Unit SEAF Security Anchor Function SeNB Secondary eNB SEPP Security Edge Protection Proxy SFI Slot format indication SFTD Space-Frequency Time Diversity, SFN and frame timing difference SFN System Frame Number or Single Frequency Network SgNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiated Protocol SiP System in Package SL Sidelink SLA Service Level Agreement SM Session Management SMF Session Management Function SMS Short Message Service SMSF SMS Function SMTC SSB-based Measurement Timing Configuration SN Secondary Node, Sequence Number SoC System on Chip SON Self-Organizing Network SpCell Special Cell SP-CSI-RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signalling Radio Bearer SR Sounding Reference Signal SS Synchronization Signal SSB SS Block SSBRI SSB Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received Power SS-RSRQ Synchronization Signal based Reference Signal Received Quality SS-SINR Synchronization Signal based Signal to Noise and Interference Ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Types SU-MIMO Single User MIMO SUL Supplementary Uplink TA Timing Advance, Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD To Be Defined TCI Transmission Configuration Indicator TCP Transmission Communication Protocol TDD Time Division Duplex TDM Time Division Multiplexing TDMA Time Division Multiple Access TE Terminal Equipment TEID Tunnel End Point Identifier TFT Traffic Flow Template TMSI Temporary Mobile Subscriber Identity TNL Transport Network Layer TPC Transmit Power Control TPMI Transmitted Precoding Matrix Indicator TR Technical Report TRP, TRxP Transmission Reception Point TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications, Technical Standards TTI Transmission Time Interval Tx Transmission, Transmitting, Transmitter U-RNTI UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Equipment UDM Unified Data Management UDP User Datagram Protocol UDR Unified Data Repository UDSF Unstructured Data Storage Network Function UICC Universal Integrated Circuit Card UL Uplink UM Unacknowledged Mode UML Unified Modeling Language UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-Reliable and Low Latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE-specific search space UTRA UMTS Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network UwPTS Uplink Pilot Time Slot V2I Vehicle-to-Infrastructure V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-everything VIM Virtualized Infrastructure Manager VL Virtual Link VLAN Virtual LAN, Virtual Local Area Network VM Virtual Machine VNF Virtualized Network Function VNFFG VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VoIP Voice-over-IP, Voice-over-Internet Protocol VPLMN Visited Public Land Mobile Network VPN Virtual Private Network VRB Virtual Resource Block WiMAX (registered trademark) Worldwide Interoperability for Microwave Access WLAN Wireless Local Area Network WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2 control plane X2-U X2 User Plane XML eXtensible Markup Language XRES Expected user response XOR Exclusive OR (eXclusive OR) ZC Zadoff-Chu ZP Zero Power [term] For purposes of this document, the following terms and definitions are applicable to the examples and embodiments described herein.

[0272] As used herein, the term “circuitry” refers to, is a part of, or includes hardware components configured to provide described functionality, such as electronic circuits, logic circuits, processors (shared, dedicated, or groups) and / or memories (shared, dedicated, or groups), application-specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to the combination of one or more hardware elements (or combinations of circuitry used in an electrical or electronic system) and program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0273] As used herein, the term "processor circuitry" refers to, is a part of, or includes circuitry capable of continuously and automatically performing sequences of arithmetic or logical operations, or recording, storing, and / or transferring digital data. A processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes. A processing circuitry may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry." As used herein, the terms "memory" and / or "memory circuitry" refer to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM and / or SDRAM, core memory, ROM, magnetic disk storage media, optical storage media, flash memory devices, or other machine-readable media for storing data. The term "computer-readable medium" may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or retaining instructions or data.

[0274] As used herein, the term "interface circuitry" refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, and / or a network interface card.

[0275] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0276] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as a network computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, and / or NFVI, etc.

[0277] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and / or "system" may refer to multiple computing devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0278] As used herein, the terms "appliance" or "computer appliance" or the like refer to a computing device or system having program code (e.g., software or firmware) specifically designed to provide particular computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates the computing appliance or is otherwise dedicated to providing particular computing resources.

[0279] As used herein, the term “resource” refers to a physical or virtual device, a physical or virtual component in a computing environment, and / or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and application, and / or workload units. “Hardware resources” may refer to computational, storage, and / or network resources provided by physical hardware elements. “Virtualized resources” may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The terms “network resources” or “communication resources” may refer to resources accessible by a computer device / system via a communication network. The term “system resources” may refer to any type of shared entity for providing services and may include computing and / or network resources. A system resource may be viewed as a set of coherent functions, network data objects, or services, where such system resources reside on a single host or multiple hosts and are accessible through a clearly identifiable server.

[0280] As used herein, the term "channel" refers to any transmission medium, either tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous with and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term indicating a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

[0281] As used herein, terms such as "instantiation" and "instantiation" refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0282] The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term "directly coupled" can mean that two or more elements are in direct contact with each other. The term "communicatively coupled" can mean that two or more elements may be in contact with each other by communication means, including communication via a wired or other interconnection connection, and / or communication via a wireless communication channel or link, etc.

[0283] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or the data element that contains the contents.

[0284] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0285] The term "SSB" refers to an SS / PBCH block.

[0286] The term "primary cell" refers to an MCG cell operating on a primary frequency on which a UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0287] The term "primary SCG cell" refers to the SCG cell to which the UE performs random access when performing a Reconfiguration with Sync procedure for DC operation.

[0288] The term "secondary cell" refers to a cell that provides additional radio resources above the special cell of a UE configured with CA.

[0289] The term "secondary cell group" refers to a subset of serving cells that includes the PSCell of a UE configured with a DC and zero or more secondary cells.

[0290] The term "serving cell" refers to the primary cell of a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell, including the primary cell.

[0291] The term "serving cell" or "serving cells" refers to a set of cells including the UE's dedicated cell and all secondary cells in RRC_CONNECTED configured with CA / .

[0292] The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG for DC operation; otherwise, the term "special cell" refers to a PCell.

[0293] [Other possible items] [Item 1] One or more non-transitory computer-readable media (NTCRM) storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: determining uplink control information (UCI) payload information of a physical uplink control channel (PUCCH) having PUCCH format 1; determining a sequence for transmitting the PUCCH based on the UCI payload information; mapping the determined sequence to allocated resources of the PUCCH format 1 for transmission; One or more NTCRMs to execute. [Item 2] Item 1, wherein the PUCCH is transmitted without a demodulation reference signal (DMRS). [Item 3] 3. The one or more NTCRMs according to any of items 1 to 2, wherein the sequence is a Zadoff-Chu sequence. [Item 4] 4. The one or more NTCRMs according to any one of items 1 to 3, wherein the sequence is determined from a set of sequences having at least one of different root indices, different cyclic prefixes, or different orthogonal cover codes (OCCs). [Item 5] 5. The one or more NTCRMs according to any one of items 1 to 4, wherein determining the sequence includes determining a sequence group identity parameter of the sequence based on the UCI payload information. [Item 6] The sequence group identity parameter u is

number

number

number

number

number

number

Claims

1. 1. A computer program comprising instructions that, when executed by one or more processors, cause a user equipment (UE) to: determining uplink control information (UCI) payload information for a physical uplink control channel (PUCCH) having PUCCH format 1; determining a sequence for transmitting the PUCCH based on the UCI payload information; mapping the determined sequence to allocated resources of the PUCCH format 1 for transmission; Execute determining the sequence includes determining a sequence group identity parameter u of the sequence based on the UCI payload information; The sequence group identity parameter u is [Number 175] [Number 176] [Number 177] or [Number 178] where n corresponds to the UCI payload information, and f gh and f ss are group and sequence hopping functions.

2. The computer program of claim 1, wherein the sequence is a Zadoff-Chu sequence.

3. A computer program comprising instructions that, when executed by one or more processors, cause a user equipment (UE) to: determining uplink control information (UCI) payload information for a physical uplink control channel (PUCCH) having PUCCH format 1; determining a sequence for transmitting the PUCCH based on the UCI payload information; mapping the determined sequence to allocated resources of the PUCCH format 1 for transmission; Execute the sequence is a Zadoff-Chu sequence with cyclic shifts, The computer program product, wherein a cyclic shift parameter α of the Zadoff-Chu sequence is generated according to the UCI payload information.

4. The computer program product of claim 1 , wherein the PUCCH is transmitted without a demodulation reference signal (DMRS).

5. The computer program product of claim 1 , wherein the sequence is determined from a set of sequences having at least one of different root indices, different cyclic prefixes, or different orthogonal cover codes (OCCs).

6. The computer program product of claim 1 , wherein determining the sequence comprises determining a cyclic prefix of the sequence based on the UCI payload information.

7. 7. The computer program product of claim 1, wherein the instructions, when executed, further cause the UE to apply respective time-domain orthogonal cover codes (OCCs) to odd and even UCI symbols of the PUCCH.

8. An apparatus implemented in a user equipment (UE), comprising: a radio frequency (RF) interface; a processor circuit coupled to the RF interface; Including, The processor circuitry includes: determining uplink control information (UCI) payload information for a physical uplink control channel (PUCCH) having PUCCH format 1; determining a sequence for transmitting the PUCCH based on the UCI payload information; mapping the determined sequence to allocated resources of the PUCCH format 1 for transmission; determining the sequence includes determining a sequence group identity parameter u of the sequence based on the UCI payload information; The sequence group identity parameter u is [Number 175] [Number 176] [Number 177] or [Number 178] where n corresponds to said UCI payload information, and f gh and f ss are group and sequence hopping functions.

9. An apparatus implemented in a user equipment (UE), comprising: a radio frequency (RF) interface; a processor circuit coupled to the RF interface; Including, The processor circuitry includes: determining uplink control information (UCI) payload information for a physical uplink control channel (PUCCH) having PUCCH format 1; determining a sequence for transmitting the PUCCH based on the UCI payload information; mapping the determined sequence to allocated resources of the PUCCH format 1 for transmission; the sequence is a Zadoff-Chu sequence with cyclic shifts, The apparatus, wherein a cyclic shift parameter α of the Zadoff-Chu sequence is generated in response to the UCI payload information.

10. A computer program comprising instructions that, when executed by one or more processors, cause a user equipment (UE) to: determining one or more uplink control information (UCI) bits of a physical uplink control channel (PUCCH) having PUCCH format 1, 3, or 4; determining UCI payload information of the PUCCH; determining a sequence based on a first scrambling ID if n<N / 2 and determining a sequence based on a second scrambling ID if n≧N / 2, where the UCI payload information corresponds to a value n, where N is the number of UCI bits; encoding the PUCCH for transmission without a demodulation reference signal (DMRS) based on the determined sequence; and A computer program that executes

11. 1. A computer program comprising instructions that, when executed by one or more processors, cause a user equipment (UE) to: determining one or more uplink control information (UCI) bits of a physical uplink control channel (PUCCH) having PUCCH format 1; multiplied by a complex-valued symbol d(0) obtained from said one or more UCI bits. [Number 180] the sequence y(n) assigned to the original data symbols, multiplied by the conjugate of d(0) [Number 181] the sequence y(n) assigned to the original DMRS symbol, encoding the PUCCH for transmission without a demodulation reference signal (DMRS) using A computer program that executes

12. 12. The computer program product of claim 10 or 11, wherein when the one or more UCI bits comprise one bit, then the PUCCH is encoded using binary phase shift keying (BPSK), and when the one or more UCI bits comprise two bits, then the PUCCH is encoded using quadrature phase shift keying (QPSK).

13. 13. The computer program product of claim 12, wherein the modulated symbols are multiplied with a length-12 sequence in the frequency domain and an orthogonal cover code (OCC), and then directly mapped to allocated resources configured for PUCCH format 1.

14. 14. The computer program product of claim 10, wherein encoding the PUCCH comprises applying respective time-domain orthogonal cover codes (OCCs) to odd and even UCI symbols.

15. 15. The computer program product of claim 10, wherein encoding the PUCCH includes generating an OCC based on a Discrete Fourier Transform (DFT) orthogonal code to support sequence lengths greater than seven symbols.

16. The instructions, when executed, further cause the UE to: receiving configuration information of a plurality of orthogonal sequences for PUCCH format 1; and selecting a first sequence from the plurality of orthogonal sequences based on the one or more UCI bits, wherein the PUCCH is encoded based on the selected first sequence.

17. The computer program product of claim 16 , wherein the configuration information includes a cyclic shift and an OCC index for each of the plurality of orthogonal sequences.

18. One or more non-transitory computer readable media (NTCRM) storing a computer program according to any one of claims 1 to 7 or any one of claims 10 to 17.

19. An apparatus implemented in a user equipment (UE), comprising: a radio frequency (RF) interface; a processor circuit coupled to the RF interface; Including, The processor circuitry includes: determining one or more uplink control information (UCI) bits of a physical uplink control channel (PUCCH) having PUCCH format 1, 3, or 4; determining UCI payload information of the PUCCH; determining a sequence based on a first scrambling ID if n<N / 2, and determining a sequence based on a second scrambling ID if n≧N / 2, where the UCI payload information corresponds to a value n, where N is the number of UCI bits; An apparatus that encodes the PUCCH for transmission without a demodulation reference signal (DMRS) based on the determined sequence.

20. An apparatus implemented in a user equipment (UE), comprising: a radio frequency (RF) interface; a processor circuit coupled to the RF interface; Including, The processor circuitry includes: determining one or more uplink control information (UCI) bits of a physical uplink control channel (PUCCH) having PUCCH format 1; multiplied by a complex-valued symbol d(0) obtained from said one or more UCI bits. [Number 180] the sequence y(n) assigned to the original data symbols, multiplied by the conjugate of d(0) [Number 181] the sequence y(n) assigned to the original DMRS symbol, 46. ​​An apparatus for encoding the PUCCH for transmission without a demodulation reference signal (DMRS) using a DMA carrier.

Images