WO2020028868A1 - New radio (nr) physical uplink control channel (pucch) formats for nr-unlicensed - Google Patents

New radio (nr) physical uplink control channel (pucch) formats for nr-unlicensed Download PDF

Info

Publication number
WO2020028868A1
WO2020028868A1 PCT/US2019/044995 US2019044995W WO2020028868A1 WO 2020028868 A1 WO2020028868 A1 WO 2020028868A1 US 2019044995 W US2019044995 W US 2019044995W WO 2020028868 A1 WO2020028868 A1 WO 2020028868A1
Authority
WO
WIPO (PCT)
Prior art keywords
prbs
pucch
cch
sequences
sequence
Prior art date
Application number
PCT/US2019/044995
Other languages
French (fr)
Inventor
Gang Xiong
Jeongho Jeon
Lopamudra Kundu
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to EP24162441.0A priority Critical patent/EP4358452A2/en
Priority to EP19843075.3A priority patent/EP3831008A4/en
Priority to CN201980043271.6A priority patent/CN112470420B/en
Priority to CN202410141064.7A priority patent/CN117955588A/en
Publication of WO2020028868A1 publication Critical patent/WO2020028868A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/69—Spread spectrum techniques
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/0007—Code type
    • H04J13/0055—ZCZ [zero correlation zone]
    • H04J13/0059—CAZAC [constant-amplitude and zero auto-correlation]
    • H04J13/0062—Zadoff-Chu
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/0074—Code shifting or hopping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/69—Spread spectrum techniques
    • H04B2001/6904—Spread spectrum techniques using code hopping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1858—Transmission or retransmission of more than one copy of acknowledgement message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/26025—Numerology, i.e. varying one or more of symbol duration, subcarrier spacing, Fourier transform size, sampling rate or down-clocking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/261—Details of reference signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal

Definitions

  • Wireless systems typically include multiple User Equipment (UE) devices communicatively coupled to one or more Base Stations (BS).
  • the one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNB) or new radio (NR) NodeBs (gNB), next generation node Bs (gNB), or new radio base stations (NR BS) that can be communicatively coupled to one or more UEs by a Third-Generation Partnership Project (3GPP) network.
  • LTE Long Term Evolved
  • NR new radio
  • 3GPP Third-Generation Partnership Project
  • Next generation wireless communication systems are expected to be a unified network/system that is targeted to meet vastly different and sometimes conflicting performance dimensions and services.
  • New Radio Access Technology is expected to support a broad range of use cases including Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Mission Critical Machine Type Communication (uMTC), and similar service types operating in frequency ranges up to 100 GHz.
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • uMTC Mission Critical Machine Type Communication
  • similar service types operating in frequency ranges up to 100 GHz.
  • FIG. 1 illustrates a block diagram of a Third-Generation Partnership Project (3GPP) New Radio (NR) Release 15 frame structure in accordance with an example;
  • 3GPP Third-Generation Partnership Project
  • NR New Radio
  • FIG. 2a illustrates functionality of mapping sequences in the frequency domain in accordance with an example
  • FIG. 2b illustrates functionality of mapping sequences in the frequency domain in accordance with an example
  • FIG. 2c illustrates functionality of mapping sequences in the frequency domain in accordance with an example
  • FIG. 2d illustrates functionality of mapping sequences in the frequency domain in accordance with an example
  • FIG. 2e illustrates functionality of mapping sequences in the frequency domain in accordance with an example
  • FIG. 2f illustrates functionality of mapping sequences in the frequency domain in accordance with an example
  • FIG. 2g illustrates functionality of frequency hopping in accordance with an example
  • FIG. 3a illustrates functionality of mapping demodulation reference signal (DMRS) and uplink control information (UCI) in the frequency domain in accordance with an example
  • FIG. 3b illustrates functionality of mapping demodulation reference signal (DMRS) and uplink control information (UCI) in the frequency domain in accordance with an example
  • FIG. 3c illustrates functionality of mapping demodulation reference signal (DMRS) and uplink control information (UCI) in the frequency domain in accordance with an example
  • FIG. 3d illustrates functionality of frequency hopping in accordance with an example
  • FIG. 4 depicts functionality of a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U) in accordance with an example;
  • UE user equipment
  • PUCCH physical uplink control channel
  • FIG. 5 depicts functionality of a new radio node B (gNB) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U) in accordance with an example;
  • gNB new radio node B
  • PUCCH physical uplink control channel
  • FIG. 6 depicts a flowchart of a machine-readable storage medium having instructions embodied thereon for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U) in accordance with an example;
  • NR new radio
  • PUCCH physical uplink control channel
  • FIG. 7 illustrates an example architecture of a system of a network in accordance with an example
  • FIG. 8 illustrates an example of a platform or device in accordance with an example
  • FIG. 9 illustrates example components of baseband circuitry and radio front end modules (RFEM) in accordance with an example
  • FIG. 10 is a block diagram illustrating components able to read instructions from a machine-readable or computer-readable medium in accordance with an example.
  • FIG. 11 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.
  • UE wireless device
  • next generation wireless communication system 5G, or new radio (NR) is going to provide ubiquitous connectivity and access to information, as well as ability to share data, around the globe.
  • NR is expected to be a unified framework that will target to meet versatile and sometimes, conflicting performance criteria and provide services to vastly heterogeneous application domains ranging from Enhanced Mobile Broadband (eMBB) to massive Machine-Type
  • NR Ultra-Reliable Low-Latency Communications
  • 3GPP third generation partnership project
  • LTE long term evolution
  • RATs enhanced radio access technologies
  • LAA Licensed- Assisted- Access
  • Coexistence methods defined for LTE-based LAA context may be assumed as a baseline for the operation of NR-unlicensed systems. NR-based operation in unlicensed spectrum should not impact deployed Wi-Fi services (data, video, and voice services) more than an additional Wi-Fi network on the same carrier.
  • Occupied Channel Bandwidth (OCB)
  • ETSI European Telecommunications Standards Institute
  • limits on OCB are stated as follows:“The Occupied Channel Bandwidth shall be between 80% and 100% of the Nominal Channel Bandwidth. In case of smart antenna systems (devices with multiple transmit chains) each of the transmit chains shall meet this regulation.
  • the Occupied Channel Bandwidth might change with time/payload.
  • COT Channel Occupancy Time
  • equipment may operate temporarily with an Occupied Channel Bandwidth of less than 80% of its Nominal Channel Bandwidth with a minimum of 2 [megahertz] MHz.”
  • the ETSI specification uses a maximum Power Spectral Density (PSD) of 10 decibel- milliwatts (dBm)/MHz for 5150-5350 MHz, while the Federal Communications
  • FCC Federal Communications Commission
  • regulations can use 10 kilohertz (kHz) resolution for testing the 1 MHz PSD constraint and the maximum PSD constraint can be followed in any occupied lMHz bandwidth.
  • regulations can impose a band specific total maximum transmission power in terms of EIRP (e.g., ESTI with an effective isotropic radiated power (EIRP) limit of 23 dBm for 5150 - 5350 MHz.
  • EIRP effective isotropic radiated power
  • the baseline physical uplink control channel (PUCCH) design can be based on different PUCCH formats used in NR licensed spectrum (e.g., NR -PUCCH formats 0, 1, 2, 3 or 4).
  • Legacy NR-licensed PUCCH design may not be suitable for NR-unlicensed spectrum because unlicensed spectrum utilization can be restricted by regulatory limitations (e.g., OCB and PSD) which may not be fulfilled by legacy NR-PUCCH formats designed for licensed spectrum.
  • an apparatus of a user equipment can be operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR- U).
  • the apparatus can comprise: one or more processors configured to: identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body; map, at the UE, in each of n symbols, a sequence in M RB ' physical resource blocks (PRBs) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M CH ' X PRBS includes N c subcarriers and the M RB CCH,X PRBs are distributed in the frequency domain, and wherein n is a positive integer, is a positive integer, and iVTM is a positive integer; and encode, at the UE, information on the M RB ' PRBs for transmission on the PUCCH.
  • the apparatus can further comprise a memory interface configured to retrieve the information from a memory
  • FIG. 1 provides an example of a 3GPP NR Release 15 frame structure.
  • FIG. 1 illustrates a downlink radio frame structure.
  • a radio frame 100 of a signal used to transmit the data can be configured to have a duration, T/, of 10 milliseconds (ms).
  • T/ duration
  • Each radio frame can be segmented or divided into ten subframes llOi that are each 1 ms long.
  • Each slot can include a physical downlink control channel (PDCCH) and/or a physical downlink shared channel (PDSCH).
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • Each slot for a component carrier (CC) used by the node and the wireless device can include multiple resource blocks (RBs) l30a, l30b, 130i, l30m, and 130h based on the CC frequency bandwidth.
  • the CC can have a carrier frequency having a bandwidth.
  • Each slot of the CC can include downlink control information (DCI) found in the PDCCH.
  • the PDCCH is transmitted in control channel resource set (CORESET) which can include one, two or three Orthogonal Frequency Division Multiplexing (OFDM) symbols and multiple RBs.
  • CORESET control channel resource set
  • OFDM Orthogonal Frequency Division Multiplexing
  • Each RB (physical RB or PRB) can include 12 subcarriers (on the frequency axis) and 14 orthogonal frequency-division multiplexing (OFDM) symbols (on the time axis) per slot.
  • the RB can use 14 OFDM symbols if a short or normal cyclic prefix is employed.
  • the RB can use 12 OFDM symbols if an extended cyclic prefix is used.
  • the resource block can be mapped to 168 resource elements (REs) using short or normal cyclic prefixing, or the resource block can be mapped to 144 REs (not shown) using extended cyclic prefixing.
  • the RE can be a unit of one OFDM symbol 142 by one subcarrier (i.e., 15 kHz, 30kHz, 60kHz, l20kHz, and 240kHz) 146.
  • Each RE l40i can transmit two bits l50a and l50b of information in the case of quadrature phase-shift keying (QPSK) modulation.
  • QPSK quadrature phase-shift keying
  • Other types of modulation may be used, such as 16 quadrature amplitude modulation (QAM) or 64 QAM to transmit a greater number of bits in each RE, or bi-phase shift keying (BPSK) modulation to transmit a lesser number of bits (a single bit) in each RE.
  • QAM quadrature amplitude modulation
  • BPSK bi-phase shift keying
  • the RB can be configured for a downlink transmission from the NR BS to the UE, or the RB can be configured for an uplink transmission from the UE to the NR BS.
  • This example of the 3GPP NR Release 15 frame structure provides examples of the way in which data is transmitted, or the transmission mode.
  • the example is not intended to be limiting.
  • Many of the Release 15 features will evolve and change in the 5G frame structures included in 3GPP LTE Release 15, MulteFire Release 1.1, and beyond.
  • the design constraint can be on co-existence with multiple 5G numerologies in the same carrier due to the coexistence of different network services, such as eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type
  • the carrier in a 5G system can be above or below 6GHz.
  • each network service can have a different numerology.
  • NR PUCCH formats may not be able to meet the OCB criteria for enabling its operation in the unlicensed spectrum.
  • Enhancements of NR- PUCCH formats 0/1/2/3/4 can be used to fulfill regulations relating to unlicensed operation.
  • a length-l2 sequence can PUCCH 0
  • mapping can be contiguous (i.e. localized) or non contiguous (i.e. distributed or interlaced), or a combination thereof, to fulfill the OCB criteria, wherein:
  • OCB can be the minimum bandwidth to be occupied by PUCCH format 0 to meet regulations (for example, 80%-l00% of nominal channel bandwidth or 2 MHz bandwidth), wherein N B( ? can be the number of sub-carriers per PRB (e.g., 12) and SCS can be the sub-carrier spacing (for example, in the sub-6 GHz frequency range, the SCS can be 15, 30, or 60 kHz). Scaling can be applied if the OCB and SCS are expressed in different units (e.g., OCB in units of MHz and SCS in units of kHz).
  • the length- 12 base sequence can be mapped on M RB
  • PRBs by applying M RB ' cyclic shifts. Different cyclic shifts can be applied on different PRBs.
  • the cyclic shift pattern in different PRBs can be predefined in the specification or configured by higher layers via NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling.
  • MSI NR minimum system information
  • RMSI NR remaining minimum system information
  • OSI NR other system information
  • RRC radio resource control
  • the cyclic shift pattern in different PRBs can be defined as a function of physical or virtual cell ID, symbol or slot index, or the like.
  • a constant cyclic shift offset can be applied on different PRBs.
  • the base sequence (n) can be mapped on the i-th PRB
  • the same length- 12 sequence (with the same cyclic shift) can be used.
  • phase offsets can be predefined in the specification, randomly selected by the UE, or configured by higher layers via MSI, RMSI, OSI or RRC signaling.
  • different base sequences (with cyclic shift hopping and/or base sequence hopping being applied) can be mapped on M R P B UCCH ' 0 PRBs. Additional phase offsets can be applied on the M R P B U CC H ' 0 different base sequences.
  • the base sequence ⁇ (n) can be mapped on the i-th PRB
  • FIGS. 2a - 2c illustrate the mapping of n sequences across frequency, in a contiguous manner (FIG. 2a), a non-contiguous/interlaced manner (FIG. 2b), and a combination thereof (FIG. 2c), wherein the n sequences can have different cyclic shifts and/or different phase offsets and/or different base sequences as described in the above embodiments.
  • the transmission bandwidth over n PRBs can be greater than or equal to the OCB, as previously discussed.
  • Sequence mapping across PRB as shown in FIG 2c is an example of interlace based PUCCH format 0 transmission wherein two consecutive interlaces can be assigned to PUCCH format 0.
  • a length-l e.g., Z > 12 or, l ⁇ 12
  • low peak-to-average power ratio (PAPR) sequence e.g., Zadoff-Chu (ZC) sequence or computer generated sequence (CGS)
  • ZC Zadoff-Chu
  • CCS computer generated sequence
  • Z can be a factor of L and other quantities (e.g., OCB and SCS) can be similar to the above example.
  • the same length-Z base sequence can be mapped on L frequency sub-carriers by applying L/l cyclic shifts.
  • the cyclic shift pattern can be predefined in the specification or configured by higher layers via NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling.
  • MSI NR minimum system information
  • RMSI NR remaining minimum system information
  • OSI NR other system information
  • RRC radio resource control
  • the cyclic shift pattern can be defined as a function of physical or virtual cell ID, symbol or slot index, or the like.
  • a constant cyclic shift offset can be applied to generate L/l different cyclic shifts.
  • the length-Z sequence (with the same cyclic shift) can be repeatedly mapped on L frequency sub-carriers by applying additional phase offsets on each of these repetitions.
  • different base sequences can be mapped on L frequency sub-carriers.
  • Additional phase offsets can be applied on these L/l different base sequences.
  • a length-Z sequence can be mapped (e.g., non-contiguously or interlaced) across frequency on Z sub-carriers so that the bandwidth occupied by Z tones meets the OCB criteria.
  • a long computer generated sequence (CGS) or ZC sequence can be applied for the transmission of PUCCH format 0.
  • the length of CGS or ZC sequence can be equal to the length of allocated subcarriers.
  • a length-L sequence can be mapped on L contiguous frequency sub-carriers.
  • a single length-l2 base sequence can be mapped on 11 PRBs of one interlace by applying 11 different cyclic shifts.
  • 11 different base sequences (with the same cyclic shift) can be mapped on the 11 PRBs on one interlace.
  • a single length- 132 low PAPR base sequence (with certain cyclic shift a, where 0 ⁇ a ⁇ 132) can be mapped non-contiguously on 11 PRBs of one interlace.
  • frequency hopping can be enabled so that the total bandwidth occupied by the frequency hops fulfills the OCB criteria.
  • 2-symbol NR- PUCCH format 0 can be used with frequency hopping being enabled between the lst and the 2nd symbols so that the total hopping bandwidth (BW) (including the 1 st and 2nd hops) can be greater than or equal to the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz), as illustrated in FIG. 2g.
  • Base sequence hopping and/or cyclic shift hopping and/or additional phase offset may be applied between the frequency hops.
  • the DMRS and UCI sequences on different symbols in time can be repeatedly mapped across frequency on the same set of M ⁇ g CCH 1 PRBs (each PRB can include 12 frequency sub-carriers), which may be contiguous (i.e. localized), non contiguous (i.e. distributed or interlaced), or a combination thereof, to fulfill the OCB criteria, where:
  • OCB can be the minimum bandwidth to be occupied by PUCCH format 1 to meet regulations (for example 80%-l00% of nominal channel bandwidth or 2 MHz bandwidth)
  • iVTM can be the number of sub-carriers per PRB (e.g. 12)
  • SCS can be sub-carrier spacing (for example, in sub-6 GHz frequency range, SCS can be 15, 30, or 60 kHz).
  • Scaling can be applied if the OCB and SCS are expressed in different units (e.g., OCB in units of MHz and SCS in units of kHz).
  • the DMRS and UCI sequences can be used in NR PUCCH format 1 (i.e. length-l2, low PAPR, computer generated sequences), and can be mapped M ⁇ , cch ' 1 times across frequency contiguously or non-contiguously by applying M ⁇ , CCH ' 1 cyclic shifts.
  • NR PUCCH format 1 i.e. length-l2, low PAPR, computer generated sequences
  • M zc can be the length of the sequence and
  • M s P c UCCH ' 1 can be the total number of frequency sub-carriers on one symbol used for PUCCH format 1 transmission to fulfill the OCB criteria.
  • the cyclic shifts applied on DMRS sequences can be the same or different from those applied on UCI sequences.
  • the examples for the design of 25 PUCCH format 0 can be applied for the generation of UCI and DMRS sequence of
  • the cyclic shift applied on UCI sequences can be n i ucI , wherein: wherein V j 0 ⁇ set can be predefined in the specification and can be either a fixed value or a function of system parameters like physical cell ID, slot or symbol index or the like, or provided by higher layer signaling.
  • n i DMRS can be defined similar to a i i for enhanced PUCCH format 1 as previously discussed.
  • m! can be set to 0 (e.g., distributed or interlaced) enhanced PUCCH format 1, with > 1 because frequency diversity can be achieved from distributed PRB allocation without additional frequency hopping.
  • the same DMRS and UCI sequences can be repeatedly
  • phase offsets applied on DMRS sequences can be the same or different from those applied on UCI sequences.
  • different base sequences can used for DMRS and spreading sequence for UCI to generate each of the copies of PUCCH format 1, to be mapped on M rb cch ’ 1 PRBS. Additional phase offsets can be applied on these M RB CCH ’ 1 different copies of PUCCH format 1 DMRS and UCI sequences, wherein the phase offsets applied on DMRS sequences can be the same or different from those applied on UCI sequences.
  • M zc can be the length of the sequence and the sequence group iq can be provided by: 30.
  • a length-l (where / > 12 or, l ⁇ 12), low PAPR sequence (for example, ZC sequence or CGS) can be used for DMRS and spreading sequence of UCI, and mapped across frequency on the same L subcarriers, which can be contiguous (i.e. localized), non-contiguous (i.e. distributed or interlaced), or a combination thereof to fulfill the OCB criteria, where:
  • l can be a factor of L and other quantities (e.g., OCB and SCS) can be similar to above example.
  • length- 1 DMRS and UCI sequences can be mapped on L frequency sub-carriers by applying L/l cyclic shifts.
  • the cyclic shifts applied on DMRS sequences can be different from those applied on UCI sequences.
  • the same length-Z DMRS and UCI sequences can be repeatedly mapped on L frequency sub-carriers by applying additional phase offsets on each of these repetitions.
  • the phase offsets applied on DMRS sequences can be different from those applied on UCI sequences.
  • n i DMRS denotes the cyclic shift applied on DMRS sequences
  • the cyclic shift applied on UCI sequences can be n UCI , wherein: n i,UCl — ( n i,DMRS + Vi,offset m °d (l ) ,
  • off set can be predefined in the specification and can be either a fixed value or a function of system parameters like physical cell ID, slot or symbol index, or provided by higher layer signaling.
  • different base sequences can used for DMRS and spreading sequence of UCI to generate each of L/l copies of PUCCH format 1, to be mapped on L frequency sub-carriers. Additional phase offsets can be applied on these L/l different copies of PUCCH format 1, wherein the phase offsets applied on the DMRS sequences can be f O different from those applied on UCI sequences.
  • length- 1 DMRS and UCI sequences can be mapped (e.g., non- contiguously or interlaced) across frequency on the same l sub-carriers so that the bandwidth occupied by l tones of DMRS and UCI fulfill the OCB criteria.
  • FIGS. 3a - 3c illustrate the mapping of n sets of sequences
  • n sequences can have different cyclic shifts or different phase offsets or different base sequences as described in the above example and the transmission bandwidth over n PRBs can be
  • frequency hopping can be enabled or disabled.
  • a long computer generated sequence (CGS) or ZC sequence can be applied for the generation of DMRS and UCI sequence.
  • the length of CGS or ZC sequence is equal to the length of allocated subcarriers.
  • length-L sequence can be mapped on L contiguous frequency sub-carriers.
  • frequency hopping can be enabled so that the total BW occupied by the two frequency hops fulfills the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz), as illustrated in FIG. 3d, where 8-symbol PUCCH can be frequency hopped with 4-symbols per hop.
  • Base sequence hopping and/or cyclic shift hopping and/or additional phase offset can be applied between the frequency hops.
  • n PRB min a lower limit on the number of PRBs (n PRB min ) can be predefined in the specification or configured by higher layer signaling (e.g., RRC signaling) or derived based on the subcarrier spacing and allocated BW so that PUCCH format 2 can be allocated at least n PRB min number of PRBs or more when localized mapping is used across frequency so as to fulfill the OCB criteria.
  • nPRB,min ⁇ OCB/(N s f SCS) ⁇ 1
  • SCS can denote sub-carrier spacing and iVTM can denote the number of sub carriers in one PRB (e.g., 12). Scaling can be applied if the OCB and SCS are expressed in different units. In another example, depending on the OCB criteria, n PRB min can be greater than the maximum number of PRBs configured in Release 15 specification for NR (i.e. 16 PRBs).
  • PUCCH format 2 can be configured by higher layer signaling
  • M R P B UCCH ' 2 can be determined by the total number of UCI bits and the configured maximum coding rate, and:
  • the preceding examples can be applied, wherein the same frequency domain resource allocation on one symbol can be repeated across N symbols of PUCCH format 2.
  • frequency hopping can be enabled so that the total bandwidth occupied by the frequency hops fulfills the OCB criteria.
  • 2-symbol NR- PUCCH format 2 can be used with frequency hopping enabled between the lst and the 2nd symbols, wherein the total hopping bandwidth including the lst and 2nd hops can be greater than or equal to the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz).
  • NR PUCCH format 2 can be enhanced to support transmission of 1 to 2 UCI bits (e.g., HARQ-ACK or SR bits without CSI reports).
  • simplex or repetition code can be used to encode 1 or 2-bits HARQ-ACK with or without SR.
  • bit 1 or bit 0 can be transmitted using coding schemes discussed in the preceding corresponding to positive or negative SR respectively.
  • existing coding schemes in NR for PUCCH format 2 can also be used to transmit 1 to 2 UCI bits using PUCCH format 2.
  • zero padding can be applied for SR or 1 to 2 UCI bits so that at least 3 bits can be carried by PUCCH format 2.
  • the preceding examples can be applied when PUCCH format 0 or 1 is not defined for the NR unlicensed system.
  • a lower limit on the number of PRBs can be configured by higher layer signaling (e.g., RRC signaling), such that PUCCH format 3 can be allocated at least n PRBmin number of PRBs or more when localized mapping is used across frequency to meet the OCB criteria.
  • higher layer signaling e.g., RRC signaling
  • n PRB,min can be greater than the maximum number of PRBs configured in the Release 15 specification for NR (i.e. 16 PRBs).
  • PUCCH format 3 can be configured by higher layer signaling
  • n can be determined by the total number of UCI bits and the configured maximum coding rate, and:
  • frequency hopping can be enabled so that the total bandwidth occupied by the two frequency hops fulfills the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz).
  • NR PUCCH format 3 can support transmission of 1 - 2 UCI bits (e.g., HARQ-ACK or SR bits without CSI reports).
  • simplex or repetition code can be used to encode 1 or 2-bit HARQ-ACK with or without SR.
  • bit 1 or bit 0 can be transmitted using coding schemes discussed in the preceding to positive or negative SR respectively.
  • existing coding schemes in NR for PUCCH format 3 can be used to transmit 1 to 2 UCI bits using PUCCH format 3.
  • zero padding can be applied for SR or 1 to 2 UCI bits so that at least 3 bits can be carried by PUCCH format 2.
  • the preceding examples can be applied for the case wherein PUCCH format 0 or 1 is not defined for an NR unlicensed system.
  • NR PUCCH format 4 can be configured by higher layer signaling (e.g., RRC signaling), with M RB CCH ’ 4 number of PRBs (M RB CCH ’ 4 > 1)), which can be mapped contiguously or non-contiguously (e.g., distributed or interlaced) in the frequency domain to fulfill the OCB criteria.
  • RRC signaling e.g., RRC signaling
  • M RB CCH ’ 4 number of PRBs M RB CCH ’ 4 > 1
  • M RB CCH ' 4 can be determined by the total number of UCI bits and a configured maximum coding rate such that the encoding, scrambling, and DFT-pre-coding of UCI bits can be based on the total number of available frequency resources and UCI symbols mapped across M RB CCH ’ A PRBs.
  • the preceding examples for the generation of the DMRS sequence for NR PUCCH format 3 with length greater than 12 for NR unlicensed system can be applied for the generation of the DMRS sequence for enhanced PUCCH format 4 for unlicensed spectrum.
  • UE multiplexing and pre-DFT OCC can be applied on a per- PRB basis.
  • the same OCC can be applied on UCI symbols mapped on each PRB with OCC cycling to keep PAPR low, or block-wise spread OCC applied on CCHA PRBs on which UCI symbols can be mapped.
  • a one-to-one correspondence between OCC index on UCI symbols and cyclic shift on DMRS sequences on the lst PRB can be configured.
  • a block of complex valued symbols — 1) can be generated according to section 6.3.2.6.3 of 3GPP
  • N S,F ,max £ Nsc w n can t> e based on DFT based OCC code block- wise spread by a factor Ms £ CCH ’ 4 / N P p CCHA , with n denoting the index of the orthogonal sequence (n
  • block-wise spreading can be applied on enhanced PUCCH format 3 (e.g., interlaced).
  • enhanced PUCCH format 3 e.g., interlaced.
  • y(0), ... , y(Ns F CCH ' 3 M symb — 1) can be generated according to section 6.3.2.6.3 of 3GPP TS 38.211 vl5.5.0:
  • Table 1 can be enhanced to w n (m ) for PUCCH format s with
  • N S. F 4 and Ml RB > 1.
  • frequency hopping can be enabled so that the total bandwidth occupied by the two frequency hops fulfills the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz.
  • Frequency mapping of UCI and DMRS symbols can be applied on n PRBs (n >
  • the 12 sub-carriers can be mapped non-contiguously across frequency to fulfill the OCB criteria.
  • NR PUCCH format 4 can be enhanced to support transmission of 1 to 2 UCI bits (e.g., HARQ-ACK or SR bits without CSI reports).
  • simplex or repetition code may be used to encode 1 or 2-bits HARQ-ACK with or without SR.
  • bit 1 or bit 0 can be transmitted using coding schemes corresponding to positive or negative SR respectively.
  • existing coding schemes in NR for PUCCH format 4 can be used to transmit 1 to 2 UCI bits using PUCCH format 4.
  • zero padding can be applied for SR or 1 to 2 UCI bits so that at least 3 bits can be carried by PUCCH format 4.
  • the preceding examples can be applied when PUCCH format 0 or 1 is not defined for NR unlicensed system.
  • FIG. 4 Another example provides functionality 400 of a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), as shown in FIG. 4.
  • the UE can comprise one or more processors.
  • the one or more processors can be configured to identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body, as in block 410.
  • the one or more processors can be configured to map, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M RB CCH,X PRBs includes N B c subcarriers and the PRBs are distributed in the frequency domain, and wherein n is a positive integer, M RB CCH,X is a positive integer, and iVTM is a positive integer, as in block 420.
  • the one or more processors can be configured to encode, at the UE, information on the M RB CCH,X PRBs for transmission on the PUCCH, as in block 430.
  • the UE can comprise a memory interface configured to retrieve the information from a memory.
  • Another example provides functionality 500 of a new radio node B (gNB) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR- unlicensed (NR-U), as shown in FIG. 5.
  • the gNB can comprise one or more processors.
  • the one or more processors can be configured to decode, at the gNB, information located in M RB CCH,X physical resource blocks (PRBs) received on a PUCCH, wherein M RB CCH,X is a positive integer, as in block 510.
  • PRBs physical resource blocks
  • the one or more processors can be configured to identify, at the gNB, a minimum occupied bandwidth of the PUCCH based on a regulation of a regulatory body, wherein on one or more of the n symbols in a time domain, the M RB ' PRBs each include one or more sequences, wherein the
  • PRBs are determined at the user equipment (UE) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M ⁇ B CCH,X PRBs includes N c subcarriers and the PRBs are distributed in the frequency domain, and wherein n is a positive integer N B( ? is a positive integer, as in block 520.
  • the gNB can comprise a memory interface configured to send the information to a memory.
  • Another example provides at least one machine readable storage medium having instructions 600 embodied thereon for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), as shown in FIG. 6.
  • the instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium.
  • the instructions when executed perform: identifying, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body, as in block 610.
  • the instructions when executed perform: mapping, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on M RB ' physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M RB CCH,X PRBs includes N B c subcarriers and the PRBs are distributed in the frequency domain, and wherein n is a positive integer, M R P B UCCH ' x is a positive integer, and /V i6 is a positive integer, as in block 620.
  • the instructions when executed perform: encoding, at the UE, information on the M R P B UCCH x PRBs for transmission on the PUCCH, as in block 630.
  • gNB next generation node B
  • gNB next generation node B
  • gNB new radio node B
  • NR BS new radio base station
  • Figure 7 illustrates an example architecture of a system 700 of a network, in accordance with various embodiments.
  • the following description is provided for an example system 700 that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.
  • 6G Sixth Generation
  • IEEE 802.16 protocols e.g., WMAN, WiMAX, etc.
  • the system 700 includes UE 70 la and UE 70 lb (collectively referred to as“UEs 701” or“UE 701”).
  • UEs 701 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non- mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an
  • smartphones e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks
  • PDAs personal digital assistants
  • IVI in-vehicle infotainment
  • ICE in-car entertainment
  • Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or“smart” appliances, MTC devices, M2M, IoT devices, and/or the like.
  • EEMS Electronic Engine Management System
  • ECUs electronic/engine control units
  • ECMs electronic/engine control modules
  • embedded systems microcontrollers, control modules, engine management systems (EMS), networked or“smart” appliances, MTC devices, M2M, IoT devices, and/or the like.
  • any of the UEs 701 may be IoT UEs, which may comprise a network access layer designed for low-power IoT applications utilizing short lived UE connections.
  • An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device via a PLMN, ProSe or D2D
  • the M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UEs 701 may be configured to connect, for example, communicatively couple, with an or RAN 710.
  • the RAN 710 may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN.
  • the term“NG RAN” or the like may refer to a RAN 710 that operates in an NR or 5G system 700
  • the term“E-UTRAN” or the like may refer to a RAN 710 that operates in an LTE or 4G system 700.
  • the UEs 701 utilize connections (or channels) 703 and 704, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below).
  • connections 703 and 704 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein.
  • the UEs 701 may directly exchange communication data via a ProSe interface 705.
  • the ProSe interface 705 may alternatively be referred to as a SL interface 705 and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.
  • the UE 70lb is shown to be configured to access an AP 706 (also referred to as“WLAN node 706,”“WLAN 706,”“WLAN Termination 706,”“WT 706” or the like) via connection 707.
  • the connection 707 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 706 would comprise a wireless fidelity (Wi-Fi®) router.
  • the AP 706 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the UE 70 lb, RAN 710, and AP 706 may be configured to utilize LWA operation and/or LWIP operation.
  • the LWA operation may involve the UE 70 lb in RRC_CONNECTED being configured by a RAN node 7lla-b to utilize radio resources of LTE and WLAN.
  • LWIP operation may involve the UE 70 lb using WLAN radio resources (e.g., connection 707) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 707.
  • IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
  • the RAN 710 can include one or more AN nodes or RAN nodes 711 a and 71 lb (collectively referred to as“RAN nodes 711” or“RAN node 711”) that enable the connections 703 and 704.
  • “RAN nodes 711” or“RAN node 711” may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users.
  • BS gNode B
  • RSU eNode B
  • TRxP TRxP
  • TRP TRP
  • NG RAN node a RAN node 711 that operates in an NR or 5G system 700
  • E-UTRAN node a RAN node 711 that operates in an LTE or 4G system 700 (e.g., an eNB).
  • the RAN nodes 711 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • LP low power
  • all or parts of the RAN nodes 711 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP).
  • a CRAN and/or a virtual baseband unit pool (vBBUP).
  • vBBUP virtual baseband unit pool
  • the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 711; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 711; or a“lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 711.
  • a RAN function split such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 711; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN
  • an individual RAN node 711 may represent individual gNB-DUs that are connected to a gNB-CU via individual Fl interfaces (not shown by Figure 7).
  • the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server that is located in the RAN 710 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP.
  • one or more of the RAN nodes 711 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 701, and are connected to a 5GC via an NG interface (discussed infra).
  • ng-eNBs next generation eNBs
  • RSU Radio Access Side Unit
  • An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a“UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an“eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a“gNB-type RSU,” and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs 701 (vUEs 701).
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications.
  • radiofrequency circuitry of the RSU 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 and/or a backhaul network.
  • a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.
  • any of the RAN nodes 711 can terminate the air interface protocol and can be the first point of contact for the UEs 701.
  • any of the RAN nodes 711 can fulfill various logical functions for the RAN 710 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 701 can be configured to communicate using OFDM communication signals with each other or with any of the RAN nodes 711 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 711 to the UEs 701, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time -frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time- frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the UEs 701 and the RAN nodes 711 communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the“licensed spectrum” and/or the“licensed band”) and an unlicensed shared medium (also referred to as the“unlicensed spectrum” and/or the“unlicensed band”).
  • the licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.
  • the UEs 701 and the RAN nodes 711 may operate using LAA, eLAA, and/or feLAA mechanisms.
  • the UEs 701 and the RAN nodes 711 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum.
  • the medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • LBT is a mechanism whereby equipment (for example, UEs 701 RAN nodes 711, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied).
  • the medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear.
  • CCA which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear.
  • This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks.
  • ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.
  • the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies.
  • WLAN employs a contention-based channel access mechanism, called CSMA/CA.
  • CSMA/CA contention-based channel access mechanism
  • a WLAN node e.g., a mobile station (MS) such as UE 701, AP 706, or the like
  • the WLAN node may first perform CCA before transmission.
  • a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time.
  • the backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds.
  • the LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN.
  • the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA.
  • the minimum CWS for an LAA transmission may be 9 microseconds (ps); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulations.
  • each aggregated carrier is referred to as a CC.
  • a CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz.
  • the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers.
  • individual CCs can have a different bandwidth than other CCs.
  • the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.
  • CA also comprises individual serving cells to provide individual CCs.
  • the coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss.
  • a primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities.
  • the other serving cells are referred to as S Cells, and each SCell may provide an individual SCC for both UL and DL.
  • the SCCs may be added and removed as required, while changing the PCC may require the UE 701 to undergo a handover.
  • LAA SCells may operate in the unlicensed spectrum (referred to as“LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum.
  • LAA SCells When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.
  • the PDSCH carries user data and higher-layer signaling to the UEs 701.
  • the PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 701 about the transport format, resource allocation, and HARQ information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 70 lb within a cell) may be performed at any of the RAN nodes 711 based on channel quality information fed back from any of the UEs 701.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 701.
  • the PDCCH uses CCEs to convey the control information. Before being mapped to resource elements, the PDCCH complex- valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG.
  • QPSK Quadrature Phase Shift Keying
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.
  • the RAN nodes 711 may be configured to communicate with one another via interface 712.
  • the interface 712 may be an X2 interface 712.
  • the X2 interface may be defined between two or more RAN nodes 711 (e.g., two or more eNBs and the like) that connect to EPC 720, and/or between two eNBs connecting to EPC 720.
  • the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C).
  • the X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs.
  • the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 701 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 701 ; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like.
  • the X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.
  • the interface 712 may be an Xn interface 712.
  • the Xn interface is defined between two or more RAN nodes 711 (e.g., two or more gNBs and the like) that connect to 5GC 720, between a RAN node 711 (e.g., a gNB) connecting to 5GC 720 and an eNB, and/or between two eNBs connecting to 5GC 720.
  • the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface.
  • the Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality.
  • the Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 701 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 711.
  • the mobility support may include context transfer from an old (source) serving RAN node 711 to new (target) serving RAN node 711; and control of user plane tunnels between old (source) serving RAN node 711 to new (target) serving RAN node 711.
  • a protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs.
  • the Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP
  • the SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages.
  • point-to-point transmission is used to deliver the signaling PDUs.
  • the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.
  • the RAN 710 is shown to be communicatively coupled to a core network— in this embodiment, core network (CN) 720.
  • the CN 720 may comprise a plurality of network elements 722, which are configured to offer various data and
  • NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below).
  • a logical instantiation of the CN 720 may be referred to as a network slice, and a logical instantiation of a portion of the CN 720 may be referred to as a network sub-slice.
  • NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches.
  • NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC
  • the application server 730 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.).
  • the application server 730 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 701 via the EPC 720.
  • communication services e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.
  • the CN 720 may be a 5GC (referred to as“5GC 720” or the like), and the RAN 710 may be connected with the CN 720 via an NG interface 713.
  • the NG interface 713 may be split into two parts, an NG user plane (NG-U) interface 714, which carries traffic data between the RAN nodes 711 and a UPF, and the Sl control plane (NG-C) interface 715, which is a signaling interface between the RAN nodes 711 and AMFs.
  • NG-U NG user plane
  • N-C Sl control plane
  • the CN 720 may be a 5G CN (referred to as“5GC 720” or the like), while in other embodiments, the CN 720 may be an EPC).
  • the RAN 710 may be connected with the CN 720 via an Sl interface 713.
  • the Sl interface 713 may be split into two parts, an Sl user plane (Sl-U) interface 714, which carries traffic data between the RAN nodes 711 and the S-GW, and the Sl-MME interface 715, which is a signaling interface between the RAN nodes 711 and MMEs.
  • Sl-U Sl user plane
  • FIG. 8 illustrates an example of a platform 800 (or“device 800”) in accordance with various embodiments.
  • the computer platform 800 may be suitable for use as UEs 701, application servers 730, and/or any other element/device discussed herein.
  • the platform 800 may include any combinations of the components shown in the example.
  • the components of platform 800 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 800, or as components otherwise incorporated within a chassis of a larger system.
  • the block diagram of Figure 8 is intended to show a high level view of components of the computer platform 800. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.
  • Application circuitry 805 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I 2 C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports.
  • the processors (or cores) of the application circuitry 805 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 800.
  • the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM,
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state memory
  • solid-state memory any other type of memory device technology, such as those discussed herein.
  • the processor(s) of application circuitry may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof.
  • the application circuitry may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.
  • the processor(s) of application circuitry 805 may include an Intel® Architecture CoreTM based processor, such as a QuarkTM, an AtomTM, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, CA.
  • the processors of the application circuitry 805 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processors) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., QualcommTM processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)TM processor(s); a MIPS-based design from MIPS Technologies, Inc.
  • AMD Advanced Micro Devices
  • APUs Accelerated Processing Units
  • A5-A9 processor(s) from Apple® Inc.
  • SnapdragonTM processor(s) from Qualcomm® Technologies, Inc. Texas Instruments, Inc.
  • OMAP Open Multimedia Applications Platform
  • the application circuitry 805 may be a part of a system on a chip (SoC) in which the application circuitry 805 and other components are formed into a single integrated circuit, or a single package, such as the EdisonTM or GalileoTM SoC boards from Intel® Corporation.
  • SoC system on a chip
  • application circuitry 805 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.
  • FPDs field-programmable devices
  • PLDs programmable logic devices
  • CPLDs complex PLDs
  • HPLDs high-capacity PLDs
  • PSoCs programmable SoCs
  • the circuitry of application circuitry 805 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein.
  • the circuitry of application circuitry 805 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.
  • memory cells e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)
  • SRAM static random access memory
  • LUTs look-up tables
  • the baseband circuitry 810 may be implemented, for example, as a solder- down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • the various hardware electronic elements of baseband circuitry 810 are discussed infra with regard to Figure 9.
  • the RFEMs 815 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs).
  • mmWave millimeter wave
  • RFICs radio frequency integrated circuits
  • the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM.
  • the RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 911 of Figure 9 infra), and the RFEM may be connected to multiple antennas.
  • both mmWave and sub- mmWave radio functions may be implemented in the same physical RFEM 815, which incorporates both mmWave antennas and sub-mmWave.
  • the memory circuitry 820 may include any number and type of memory devices used to provide for a given amount of system memory.
  • the memory circuitry 820 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc.
  • RAM random access memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • NVM nonvolatile memory
  • Flash memory high-speed electrically erasable memory
  • PRAM phase change random access memory
  • MRAM magnetoresistive random access memory
  • the memory circuitry 820 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like.
  • JEDEC Joint Electron Device
  • Memory circuitry 820 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA).
  • the memory circuitry 820 may be on-die memory or registers associated with the application circuitry 805.
  • memory circuitry 820 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others.
  • SSDD solid state disk drive
  • HDD hard disk drive
  • micro HDD micro HDD
  • resistance change memories phase change memories
  • phase change memories phase change memories
  • holographic memories holographic memories
  • chemical memories among others.
  • the computer platform 800 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • Removable memory circuitry 823 may include devices, circuitry,
  • portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.
  • flash memory cards e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like
  • USB flash drives e.g., USB drives, optical discs, external HDDs, and the like.
  • the platform 800 may also include interface circuitry (not shown) that is used to connect external devices with the platform 800.
  • the external devices connected to the platform 800 via the interface circuitry include sensor circuitry 821 and electro mechanical components (EMCs) 822, as well as removable memory devices coupled to removable memory circuitry 823.
  • EMCs electro mechanical components
  • the sensor circuitry 821 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc.
  • sensors include, inter alia, inertia measurement units (IMUs) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio
  • EMCs 822 include devices, modules, or subsystems whose purpose is to enable platform 800 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs 822 may be configured to generate and send messages/ signalling to other components of the platform 800 to indicate a current state of the EMCs 822.
  • EMCs 822 examples include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components.
  • platform 800 is configured to operate one or more EMCs 822 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.
  • the interface circuitry may connect the platform 800 with positioning circuitry 845.
  • the positioning circuitry 845 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS.
  • the positioning circuitry 845 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes.
  • the positioning circuitry 845 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance.
  • the positioning circuitry 845 may also be part of, or interact with, the baseband circuitry and/or RFEMs 815 to communicate with the nodes and components of the positioning network.
  • the positioning circuitry 845 may also provide position data and/or time data to the application circuitry 805, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like
  • the interface circuitry may connect the platform 800 with Near-Field Communication (NFC) circuitry 840.
  • NFC circuitry 840 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 840 and NFC-enabled devices external to the platform 800 (e.g., an“NFC touchpoint”).
  • RFID radio frequency identification
  • NFC circuitry 840 comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller.
  • the NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 840 by executing NFC controller firmware and an NFC stack.
  • the NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals.
  • the RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 840, or initiate data transfer between the NFC circuitry 840 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 800.
  • a passive NFC tag e.g., a microchip embedded in a sticker or wristband
  • another active NFC device e.g., a smartphone or an NFC-enabled POS terminal
  • the driver circuitry 846 may include software and hardware elements that operate to control particular devices that are embedded in the platform 800, attached to the platform 800, or otherwise communicatively coupled with the platform 800.
  • the driver circuitry 846 may include individual drivers allowing other components of the platform 800 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 800.
  • I/O input/output
  • driver circuitry 846 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 800, sensor drivers to obtain sensor readings of sensor circuitry 821 and control and allow access to sensor circuitry 821, EMC drivers to obtain actuator positions of the EMCs 822 and/or control and allow access to the EMCs 822, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
  • a display driver to control and allow access to a display device
  • a touchscreen driver to control and allow access to a touchscreen interface of the platform 800
  • sensor drivers to obtain sensor readings of sensor circuitry 821 and control and allow access to sensor circuitry 821
  • EMC drivers to obtain actuator positions of the EMCs 822 and/or control and allow access to the EMCs 822
  • a camera driver to control and allow access to an embedded image capture device
  • audio drivers to control and allow access to one or more audio devices.
  • the power management integrated circuitry (PMIC) 825 may manage power provided to various components of the platform 800.
  • the PMIC 825 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMIC 825 may often be included when the platform 800 is capable of being powered by a battery 830, for example, when the device is included in a UE 701.
  • the PMIC 825 may control, or otherwise be part of, various power saving mechanisms of the platform 800. For example, if the platform 800 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 800 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 800 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • DRX Discontinuous Reception Mode
  • the platform 800 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the platform 800 may not receive data in this state; in order to receive data, it must transition back to RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • a battery 830 may power the platform 800, although in some examples the platform 800 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid.
  • the battery 830 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 830 may be a typical lead-acid automotive battery.
  • the battery 830 may be a“smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry.
  • BMS Battery Management System
  • the BMS may be included in the platform 800 to track the state of charge (SoCh) of the battery 830.
  • the BMS may be used to monitor other parameters of the battery 830 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 830.
  • the BMS may communicate the information of the battery 830 to the application circuitry 805 or other components of the platform 800.
  • the BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 805 to directly monitor the voltage of the battery 830 or the current flow from the battery 830.
  • ADC analog-to-digital
  • the battery parameters may be used to determine actions that the platform 800 may perform, such as transmission frequency, network operation, sensing frequency, and the like.
  • a power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 830.
  • the power block may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 800.
  • a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 830, and thus, the current required.
  • the charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power
  • User interface circuitry 850 includes various input/output (I/O) devices present within, or connected to, the platform 800, and includes one or more user interfaces designed to enable user interaction with the platform 800 and/or peripheral
  • the user interface circuitry 850 includes input device circuitry and output device circuitry.
  • Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like.
  • the output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information.
  • Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 800.
  • the output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like.
  • the sensor circuitry 821 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like).
  • EMCs e.g., an actuator to provide haptic feedback or the like.
  • NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device.
  • Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.
  • the components of platform 800 may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies.
  • the bus/IX may be a proprietary bus/IX, for example, used in a SoC based system.
  • Other bus/IX systems may be included, such as an I 2 C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.
  • FIG. 9 illustrates example components of baseband circuitry 910 and radio front end modules (RFEM) 915 in accordance with various embodiments.
  • the baseband circuitry 910 corresponds to the baseband circuitry 810 of Figure 8, respectively.
  • the RFEM 915 corresponds to the RFEM 815 of Figure 8, respectively.
  • the RFEMs 915 may include Radio Frequency (RF) circuitry 906, front-end module (FEM) circuitry 908, antenna array 911 coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the baseband circuitry 910 includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that
  • the radio control functions may include, but are not limited to, signal
  • modulation/demodulation circuitry of the baseband circuitry 910 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 910 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 910 is configured to process baseband signals received from a receive signal path of the RF circuitry 906 and to generate baseband signals for a transmit signal path of the RF circuitry 906.
  • the baseband circuitry 910 is configured to interface with application circuitry 805 (see Figure 8) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 906.
  • the baseband circuitry 910 may handle various radio control functions.
  • the aforementioned circuitry and/or control logic of the baseband circuitry 910 may include one or more single or multi-core processors.
  • the one or more processors may include a 3G baseband processor 904A, a 4G/LTE baseband processor 904B, a 5G/NR baseband processor 904C, or some other baseband processor(s) 904D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.).
  • 6G sixth generation
  • some or all of the functionality of baseband processors 904A-D may be included in modules stored in the memory 904G and executed via a Central Processing Unit (CPU) 904E.
  • CPU Central Processing Unit
  • baseband processors 904A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells.
  • the memory 904G may store program code of a real-time OS (RTOS), which when executed by the CPU 904E (or other baseband processor), is to cause the CPU 904E (or other baseband processor) to manage resources of the baseband circuitry 910, schedule tasks, etc.
  • RTOS real-time OS
  • the RTOS may include Operating System Embedded (OSE)TM provided by Enea®, Nucleus RTOSTM provided by Mentor Graphics®, Versatile Real- Time Executive (VRTX) provided by Mentor Graphics®, ThreadXTM provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein.
  • the baseband circuitry 910 includes one or more audio digital signal processor(s) (DSP) 904F.
  • the audio DSP(s) 904F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • each of the processors 904A-904E include respective memory interfaces to send/receive data to/from the memory 904G.
  • the baseband circuitry 910 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry 910; an application circuitry interface to send/receive data to/if om the application circuitry 805 of FIG.
  • an RF circuitry interface to send/receive data to/from RF circuitry 906 of Figure 9; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/ Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC 825.
  • NFC Near Field Communication
  • Bluetooth®/ Bluetooth® Low Energy components e.g., Bluetooth®/ Bluetooth® Low Energy components, Wi-Fi® components, and/or the like
  • a power management interface to send/receive power or control signals to/from the PMIC 825.
  • baseband circuitry 910 comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem.
  • the digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem.
  • Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein.
  • the audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog- to-digital and digital-to- analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components.
  • baseband circuitry 910 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules 915).
  • the baseband circuitry 910 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a“multi-protocol baseband processor” or“protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions.
  • the PHY layer functions include the aforementioned radio control functions.
  • the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols.
  • the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry 910 and/or RF circuitry 906 are part of mmWave communication circuitry or some other suitable cellular communication circuitry.
  • the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions.
  • the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 910 and/or RF circuitry 906 are part of a Wi-Fi communication system.
  • the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions.
  • the protocol processing circuitry may include one or more memory structures (e.g., 904G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data.
  • the baseband circuitry 910 may also support radio communications for more than one wireless protocol.
  • the various hardware elements of the baseband circuitry 910 discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi chip module containing two or more ICs.
  • the components of the baseband circuitry 910 may be suitably combined in a single chip or chipset, or disposed on a same circuit board.
  • some or all of the constituent components of the baseband circuitry 910 and RF circuitry 906 may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP).
  • SoC system on a chip
  • SiP System-in-Package
  • the constituent components of the baseband circuitry 910 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 906 (or multiple instances of RF circuitry 906).
  • some or all of the constituent components of the baseband circuitry 910 and the application circuitry 805 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).
  • the baseband circuitry 910 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 910 may support communication with an E-UTRAN or other WMAN, a WLAN, a WPAN.
  • Embodiments in which the baseband circuitry 910 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 906 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 906 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 906 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 908 and provide baseband signals to the baseband circuitry 910.
  • RF circuitry 906 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 910 and provide RF output signals to the FEM circuitry 908 for transmission.
  • the receive signal path of the RF circuitry 906 may include mixer circuitry 906a, amplifier circuitry 906b and filter circuitry 906c.
  • the transmit signal path of the RF circuitry 906 may include filter circuitry 906c and mixer circuitry 906a.
  • RF circuitry 906 may also include synthesizer circuitry 906d for synthesizing a frequency for use by the mixer circuitry 906a of the receive signal path and the transmit signal path.
  • the mixer circuitry 906a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906d.
  • the amplifier circuitry 906b may be configured to amplify the down-converted signals and the filter circuitry 906c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 910 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 906a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 906a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 906d to generate RF output signals for the FEM circuitry 908.
  • the baseband signals may be provided by the baseband circuitry 910 and may be filtered by filter circuitry 906c.
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate
  • the RF circuitry 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 910 may include a digital baseband interface to communicate with the RF circuitry 906.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the
  • the synthesizer circuitry 906d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 906d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 906d may be configured to synthesize an output frequency for use by the mixer circuitry 906a of the RF circuitry 906 based on a frequency input and a divider control input.
  • the synthesizer circuitry 906d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 910 or the application circuitry 805 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 805.
  • Synthesizer circuitry 906d of the RF circuitry 906 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 906d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 906 may include an IQ/polar converter.
  • FEM circuitry 908 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 911, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 906 for further processing.
  • FEM circuitry 908 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 906 for transmission by one or more of antenna elements of antenna array 911.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 906, solely in the FEM circuitry 908, or in both the RF circuitry 906 and the FEM circuitry 908.
  • the FEM circuitry 908 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 908 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 908 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 906).
  • the transmit signal path of the FEM circuitry 908 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 906), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 911.
  • PA power amplifier
  • the antenna array 911 comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals.
  • digital baseband signals provided by the baseband circuitry 910 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array 911 including one or more antenna elements (not shown).
  • the antenna elements may be omnidirectional, direction, or a combination thereof.
  • the antenna elements may be formed in a multitude of arranges as are known and/or discussed herein.
  • the antenna array 911 may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards.
  • the antenna array 911 may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 906 and/or FEM circuitry 908 using metal transmission lines or the like.
  • Processors of the application circuitry 805 and processors of the baseband circuitry 910 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 910 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 805 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers).
  • Layer 3 may comprise a RRC layer, described in further detail below.
  • Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below.
  • Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.
  • Figure 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer- readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 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.
  • node virtualization e.g., NFV
  • a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.
  • the processors 1010 may include, for example, a processor 1012 and a processor 1014.
  • the processor(s) 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 discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1020 may include, but are not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read-only memory
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read only memory
  • the communication resources 1030 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008.
  • the communication resources 1030 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components,
  • Bluetooth® (or Bluetooth® Low Energy) components Wi-Fi® components, and other communication components.
  • Instructions 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein.
  • the instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor’s cache memory), the memory/storage devices 1020, or any suitable combination thereof.
  • any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.
  • FIG. 11 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile
  • the wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point.
  • the wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi.
  • the wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards.
  • the wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN.
  • the wireless device can also comprise a wireless modem.
  • the wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor).
  • the wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.
  • FIG. 11 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device.
  • the display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display.
  • the display screen can be configured as a touch screen.
  • the touch screen can use capacitive, resistive, or another type of touch screen technology.
  • An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities.
  • Anon- volatile memory port can also be used to provide data input/output options to a user.
  • the non-volatile memory port can also be used to expand the memory capabilities of the wireless device.
  • a keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input.
  • a virtual keyboard can also be provided using the touch screen.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 includes an apparatus of a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR- U), the apparatus comprising: one or more processors configured to: identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body; map, at the UE, at one or more of n symbols in a time domain, one or more sequences
  • UE user equipment
  • PUCCH physical uplink control channel
  • each PRB of the M RB CCH,X PRBs includes /V i6 subcarriers and the PRBs are distributed in the frequency
  • PUCCH X n p domain wherein n is a positive integer, M RB ' is a positive integer, and /V i6 is a positive integer; and encode, at the UE, information on the PRBs for transmission on the PUCCH; and a memory interface configured to retrieve the information from a memory.
  • Example 2 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the PRBs in the frequency
  • each PRB of the M RB CCH,X PRBS has a selected cyclic shift.
  • Example 3 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the M R P B UCCH' x PRBs by applying
  • Example 4 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, one or more additional sequences on the PRBs, wherein the one or more additional sequences are sequences with different sequence group numbers or different base sequences.
  • Example 5 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, a long sequence mapped on the PRBs, wherein the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
  • PAPR peak-to-average power ratio
  • CCS computer generated sequence
  • ZC Zadoff-Chu
  • Example 6 includes the apparatus of Example 5, wherein the length of the long sequence is equal to a length of allocated subcarriers.
  • Example 7 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at one or more of the n symbols in the time domain, a sequence mapped on the M RB ' PRBs based on a selected bandwidth and a selected subcarrier spacing (SCS).
  • SCS subcarrier spacing
  • Example 8 includes the apparatus of Example 7, wherein: the selected bandwidth is 10 megahertz (MHz), 20 MHz, or integer multiples of 20 MHz; or the SCS is 15 kilohertz (kHz), 30 kHz, or 60 kHz.
  • the selected bandwidth is 10 megahertz (MHz), 20 MHz, or integer multiples of 20 MHz; or the SCS is 15 kilohertz (kHz), 30 kHz, or 60 kHz.
  • Example 9 includes the apparatus of any of Examples 1 to 5, wherein the M CH ' X PRBS are distributed over one interlace.
  • Example 10 includes the apparatus of any of Examples 1 to 5, wherein the n symbols comprise: a 1 -symbol or 2-symbol NR PUCCH format 0.
  • Example 11 includes the apparatus of any of Examples 1 to 5, wherein the PUCCH is configured for an NR PUCCH format 0 or an NR PUCCH format 1, wherein the PUCCH is further configured to carry: a demodulation reference signal (DM-RS); or an uplink control channel information (UCI) including 1 bit or 2 bits.
  • DM-RS demodulation reference signal
  • UCI uplink control channel information
  • Example 12 includes the apparatus of any of Examples 1 to 5, wherein: the minimum occupied bandwidth is an occupied channel bandwidth (OCB); or the regulatory body is the federal communications commission (FCC).
  • OBC occupied channel bandwidth
  • FCC federal communications commission
  • Example 13 includes an apparatus of a new radio node B (gNB) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), the apparatus comprising: one or more processors configured to: decode, at the gNB, information located in physical resource blocks (PRBs) received on a PUCCH, wherein is a positive integer; and identify, at the gNB, a minimum occupied bandwidth of the PUCCH based on a regulation of a regulatory body, wherein on one or more of the n symbols in a time domain, the PRBs each include one or more sequences, wherein the PRBs are determined at the user equipment (UE) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M CH ’ X PRBS includes iVTM subcarriers and the M RB CCH,X PRBS are distributed in the frequency domain, and wherein n is a positive integer N B c is a positive integer; and
  • Example 14 includes the apparatus of Example 13, wherein the M RB CCH,X sequences on the M RB CCH,X PRBS are mapped at the UE by applying M RB CCH ' X cyclic shifts on each of the M RB CCH,X sequences, wherein each PRB of the M RB CCH ' X PRBs has a selected cyclic shift.
  • Example 15 includes the apparatus of Example 13, wherein the M RB CCH,X sequences on the M RB CCH,X PRBs are mapped at the UE by applying M RB CCH ' X phase
  • Example 16 includes the apparatus of Example 13, wherein at one or more of the n symbols in the time domain, one or more additional sequences mapped on the PRBs at the UE, wherein the one or more additional sequences are sequences with different sequence numbers.
  • Example 17 includes the apparatus of Example 13, wherein a long sequence
  • the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
  • PAPR peak-to-average power ratio
  • CCS computer generated sequence
  • ZC Zadoff-Chu
  • Example 18 includes the apparatus of any of Examples 13 to 17, wherein the PUCCH is configured for an NR PUCCH format 0 or an NR PUCCH format 1.
  • Example 19 includes the apparatus of any of Examples 13 to 17, wherein: the minimum occupied bandwidth is an occupied channel bandwidth (OCB); or the regulatory body is the federal communications commission (FCC).
  • OBC occupied channel bandwidth
  • FCC federal communications commission
  • Example 20 includes at least one machine readable storage medium having instructions embodied thereon for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), the instructions when executed by one or more processors at a user equipment (UE) perform the following: identifying, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body; mapping, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M CH ’ X PRBS includes N P c subcarriers and the M RB CCH ' X PRBS are distributed in the frequency domain, and wherein n is a positive integer, is a positive integer, and Nsc is a positive integer; and encoding, at the UE, information on the M RB CCH,X PRB
  • Example 21 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the M CH ' X PRBS in the frequency domain, by applying M RB CCH,X cyclic shifts on the one or more sequences, wherein each PRB of the M RB CCH,X PRBs has a selected cyclic shift.
  • Example 22 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the M CH ' X PRBS by applying M RB CCH,X phase offsets to each sequence mapped on the M CCH ' X PRBS of the M R P B UCCH ’ X PRBs.
  • Example 23 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, one or more additional
  • sequences on the M RB ' PRBs wherein the one or more additional sequences are sequences with different sequence group numbers or different base sequences.
  • Example 24 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, a long sequence mapped on the PRBs, wherein the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
  • PAPR peak-to-average power ratio
  • CCS computer generated sequence
  • ZC Zadoff-Chu
  • Example 25 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at one or more of the n symbols in the time domain, a sequence mapped on the PUCCH x
  • M RB ' PRBs based on a selected bandwidth and a selected subcarrier spacing (SCS).
  • SCS subcarrier spacing
  • Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
  • the computing device may include a processor, a storage medium readable by the processor (including volatile and non volatile memory and/or storage elements), at least one input device, and at least one output device.
  • the volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data.
  • the node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer).
  • transceiver module i.e., transceiver
  • a counter module i.e., counter
  • a processing module i.e., processor
  • a clock module i.e., clock
  • timer module i.e., timer
  • selected components of the transceiver module can be located in a cloud radio access network (C-RAN).
  • C-RAN cloud radio access network
  • One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like.
  • API application programming interface
  • Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system.
  • the program(s) may be implemented in assembly or machine language, if desired.
  • the language may be a compiled or interpreted language, and combined with hardware implementations.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in software for execution by various types of processors.
  • An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
  • a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the modules may be passive or active, including agents operable to perform desired functions.

Landscapes

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

Abstract

Technology for a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U) is disclosed. The apparatus can comprise: one or more processors configured to: identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body; map, at the UE, on each of n symbols, a sequence in M RB PUCCH,x physical resource blocks (PRBs) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M RB PUCCH,x PRBs includes N SC RB subcarriers and the M RB PUCCH,x PRBs are distributed in the frequency domain, and wherein n is a positive integer, M RB PUCCH,x is a positive integer, and N SC RB is a positive integer; and encode, at the UE, information on the M RB PUCCH,x PRBs for transmission on the PUCCH.

Description

NEW RADIO (NR) PHYSICAL UPLINK CONTROL CHANNEL (PUCCH)
LORMATS LOR NR-UNLICEN SED
BACKGROUND
[0001] Wireless systems typically include multiple User Equipment (UE) devices communicatively coupled to one or more Base Stations (BS). The one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNB) or new radio (NR) NodeBs (gNB), next generation node Bs (gNB), or new radio base stations (NR BS) that can be communicatively coupled to one or more UEs by a Third-Generation Partnership Project (3GPP) network.
[0002] Next generation wireless communication systems are expected to be a unified network/system that is targeted to meet vastly different and sometimes conflicting performance dimensions and services. New Radio Access Technology (RAT) is expected to support a broad range of use cases including Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Mission Critical Machine Type Communication (uMTC), and similar service types operating in frequency ranges up to 100 GHz.
BRIEF DESCRIPTION OF THE DRAWINGS
[0003] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:
[0004] FIG. 1 illustrates a block diagram of a Third-Generation Partnership Project (3GPP) New Radio (NR) Release 15 frame structure in accordance with an example;
[0005] FIG. 2a illustrates functionality of mapping sequences in the frequency domain in accordance with an example;
[0006] FIG. 2b illustrates functionality of mapping sequences in the frequency domain in accordance with an example;
[0007] FIG. 2c illustrates functionality of mapping sequences in the frequency domain in accordance with an example;
[0008] FIG. 2d illustrates functionality of mapping sequences in the frequency domain in accordance with an example;
[0009] FIG. 2e illustrates functionality of mapping sequences in the frequency domain in accordance with an example;
[0010] FIG. 2f illustrates functionality of mapping sequences in the frequency domain in accordance with an example;
[0011] FIG. 2g illustrates functionality of frequency hopping in accordance with an example;
[0012] FIG. 3a illustrates functionality of mapping demodulation reference signal (DMRS) and uplink control information (UCI) in the frequency domain in accordance with an example;
[0013] FIG. 3b illustrates functionality of mapping demodulation reference signal (DMRS) and uplink control information (UCI) in the frequency domain in accordance with an example;
[0014] FIG. 3c illustrates functionality of mapping demodulation reference signal (DMRS) and uplink control information (UCI) in the frequency domain in accordance with an example;
[0015] FIG. 3d illustrates functionality of frequency hopping in accordance with an example;
[0016] FIG. 4 depicts functionality of a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U) in accordance with an example;
[0017] FIG. 5 depicts functionality of a new radio node B (gNB) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U) in accordance with an example;
[0018] FIG. 6 depicts a flowchart of a machine-readable storage medium having instructions embodied thereon for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U) in accordance with an example;
[0019] FIG. 7 illustrates an example architecture of a system of a network in accordance with an example;
[0020] FIG. 8 illustrates an example of a platform or device in accordance with an example;
[0021] FIG. 9 illustrates example components of baseband circuitry and radio front end modules (RFEM) in accordance with an example;
[0022] FIG. 10 is a block diagram illustrating components able to read instructions from a machine-readable or computer-readable medium in accordance with an example; and
[0023] FIG. 11 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.
[0024] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.
DETAILED DESCRIPTION
[0025] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.
EXAMPLE EMBODIMENTS
[0026] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.
[0027] Mobile communication has advanced remarkably in the past two decades:
emerging from early voice systems and transforming into today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) is going to provide ubiquitous connectivity and access to information, as well as ability to share data, around the globe. NR is expected to be a unified framework that will target to meet versatile and sometimes, conflicting performance criteria and provide services to vastly heterogeneous application domains ranging from Enhanced Mobile Broadband (eMBB) to massive Machine-Type
Communications (mMTC) and Ultra-Reliable Low-Latency Communications (URLLC), to name a few. In general, NR will evolve based on third generation partnership project (3GPP) long term evolution (LTE)-Advanced technology with additional enhanced radio access technologies (RATs) to enable seamless and faster wireless connectivity solutions.
[0028] One major enhancement for LTE in Release 13 has been to enable the operation of cellular networks in the unlicensed spectrum, via Licensed- Assisted- Access (LAA). Ever since, exploiting the access of unlicensed spectrum is considered by 3GPP as one promising solution to cope with the increasing growth of wireless data traffic. One important consideration for unlicensed spectrum includes fair co-existence with incumbent systems like wireless local area networks (WLANs), which has been the primary focus of LAA standardization efforts since Release 13.
[0029] Following the trend of LTE enhancements, study on NR based access to unlicensed spectrum (NR-unlicensed) has started in 3GPP Release 15. In 3GPP Radio Access Network (RAN) meeting #77, a new study item (SI) on“NR-Based Access to Unlicensed Spectrum” was approved. Within the scope of this SI, one of the primary objectives was to identify additional functionalities for a physical (PHY) layer design of NR to operate in unlicensed spectrum. In particular, it is desirable to minimize the design efforts by identifying the enhancements for Release 15 NR design to enable unlicensed operation, while avoiding divergence from the Release 15 NR licensed framework.
Coexistence methods defined for LTE-based LAA context may be assumed as a baseline for the operation of NR-unlicensed systems. NR-based operation in unlicensed spectrum should not impact deployed Wi-Fi services (data, video, and voice services) more than an additional Wi-Fi network on the same carrier.
[0030] Regulations should be followed by networks and systems operating in the unlicensed spectrum. One such regulatory restriction imposed on physical channels or signals operating in the unlicensed spectrum is related to the bandwidth occupied by these channels or signals (i.e. an Occupied Channel Bandwidth (OCB)). According to European Telecommunications Standards Institute (ETSI) standards for 5 gigahertz (GHz), limits on OCB are stated as follows:“The Occupied Channel Bandwidth shall be between 80% and 100% of the Nominal Channel Bandwidth. In case of smart antenna systems (devices with multiple transmit chains) each of the transmit chains shall meet this regulation. The Occupied Channel Bandwidth might change with time/payload. During a Channel Occupancy Time (COT), equipment may operate temporarily with an Occupied Channel Bandwidth of less than 80% of its Nominal Channel Bandwidth with a minimum of 2 [megahertz] MHz.”
[0031] In addition to restrictions on OCB, there are important regulatory rules on power usage by networks and systems operating in unlicensed spectrum. Regulations on the maximum power spectral density can be stated with a resolution bandwidth of 1 MHz.
The ETSI specification uses a maximum Power Spectral Density (PSD) of 10 decibel- milliwatts (dBm)/MHz for 5150-5350 MHz, while the Federal Communications
Commission (FCC) uses a maximum PSD of 11 dBm/MHz for 5150-5350 MHz.
Additionally, regulations can use 10 kilohertz (kHz) resolution for testing the 1 MHz PSD constraint and the maximum PSD constraint can be followed in any occupied lMHz bandwidth. In addition, regulations can impose a band specific total maximum transmission power in terms of EIRP (e.g., ESTI with an effective isotropic radiated power (EIRP) limit of 23 dBm for 5150 - 5350 MHz.
[0032] The regulatory limitations imposed in terms of OCB and PSD guided the design choices for the uplink channels of legacy LTE-unlicensed system and can be used for NR- unlicensed systems as well. Legacy LTE-unlicensed systems or Release 14 eLAA (enhanced Licensed Assisted Access) was designed to meet the aforementioned regulations while utilizing the available spectrum efficiently. But the enhancement of LTE-unlicensed design to NR-unlicensed may be different because NR can be targeted to support diverse numerology configurations with a much wider channel bandwidth than LTE’s 20 MHz. Though it can be desirable to avoid divergence from Release 15 NR framework as much as possible while designing uplink physical signals or channels for NR-unlicensed spectrum, NR physical signals or channels can be redesigned to fulfill the regulations of unlicensed spectrum usage.
[0033] The baseline physical uplink control channel (PUCCH) design can be based on different PUCCH formats used in NR licensed spectrum (e.g., NR -PUCCH formats 0, 1, 2, 3 or 4). Legacy NR-licensed PUCCH design may not be suitable for NR-unlicensed spectrum because unlicensed spectrum utilization can be restricted by regulatory limitations (e.g., OCB and PSD) which may not be fulfilled by legacy NR-PUCCH formats designed for licensed spectrum.
[0034] In one example, an apparatus of a user equipment (UE) can be operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR- U). The apparatus can comprise: one or more processors configured to: identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body; map, at the UE, in each of n symbols, a sequence in MRB ' physical resource blocks (PRBs) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M CH'X PRBS includes N c subcarriers and the MRB CCH,X PRBs are distributed in the frequency domain, and wherein n is a positive integer,
Figure imgf000008_0001
is a positive integer, and iV™ is a positive integer; and encode, at the UE, information on the MRB ' PRBs for transmission on the PUCCH. The apparatus can further comprise a memory interface configured to retrieve the information from a memory.
[0035] FIG. 1 provides an example of a 3GPP NR Release 15 frame structure. In particular, FIG. 1 illustrates a downlink radio frame structure. In the example, a radio frame 100 of a signal used to transmit the data can be configured to have a duration, T/, of 10 milliseconds (ms). Each radio frame can be segmented or divided into ten subframes llOi that are each 1 ms long. Each subframe can be further subdivided into one or multiple slots l20a, l20i, and l20x, each with a duration, TSM, of 1 / m ms, where m = 1 for 15 kHz subcarrier spacing, m = 2 for 30kHz, m = 4 for 60kHz, m = 8 for 120kHz, and u = 16 for 240kHz. Each slot can include a physical downlink control channel (PDCCH) and/or a physical downlink shared channel (PDSCH).
[0036] Each slot for a component carrier (CC) used by the node and the wireless device can include multiple resource blocks (RBs) l30a, l30b, 130i, l30m, and 130h based on the CC frequency bandwidth. The CC can have a carrier frequency having a bandwidth. Each slot of the CC can include downlink control information (DCI) found in the PDCCH. The PDCCH is transmitted in control channel resource set (CORESET) which can include one, two or three Orthogonal Frequency Division Multiplexing (OFDM) symbols and multiple RBs. [0037] Each RB (physical RB or PRB) can include 12 subcarriers (on the frequency axis) and 14 orthogonal frequency-division multiplexing (OFDM) symbols (on the time axis) per slot. The RB can use 14 OFDM symbols if a short or normal cyclic prefix is employed. The RB can use 12 OFDM symbols if an extended cyclic prefix is used. The resource block can be mapped to 168 resource elements (REs) using short or normal cyclic prefixing, or the resource block can be mapped to 144 REs (not shown) using extended cyclic prefixing. The RE can be a unit of one OFDM symbol 142 by one subcarrier (i.e., 15 kHz, 30kHz, 60kHz, l20kHz, and 240kHz) 146.
[0038] Each RE l40i can transmit two bits l50a and l50b of information in the case of quadrature phase-shift keying (QPSK) modulation. Other types of modulation may be used, such as 16 quadrature amplitude modulation (QAM) or 64 QAM to transmit a greater number of bits in each RE, or bi-phase shift keying (BPSK) modulation to transmit a lesser number of bits (a single bit) in each RE. The RB can be configured for a downlink transmission from the NR BS to the UE, or the RB can be configured for an uplink transmission from the UE to the NR BS.
[0039] This example of the 3GPP NR Release 15 frame structure provides examples of the way in which data is transmitted, or the transmission mode. The example is not intended to be limiting. Many of the Release 15 features will evolve and change in the 5G frame structures included in 3GPP LTE Release 15, MulteFire Release 1.1, and beyond. In such a system, the design constraint can be on co-existence with multiple 5G numerologies in the same carrier due to the coexistence of different network services, such as eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type
Communications or massive IoT) and URLLC (Ultra Reliable Low Latency
Communications or Critical Communications). The carrier in a 5G system can be above or below 6GHz. In one embodiment, each network service can have a different numerology.
[0040] In another example, some of the NR PUCCH formats may not be able to meet the OCB criteria for enabling its operation in the unlicensed spectrum. Enhancements of NR- PUCCH formats 0/1/2/3/4 can be used to fulfill regulations relating to unlicensed operation.
Enhancements of NR PUCCH format 0
[0041] In one example, for a l-symbol NR PUCCH format 0, a length-l2 sequence can PUCCH 0
be repeatedly mapped across frequency on MRB ' PRBs, wherein each PRB can include 12 sub-carriers. The mapping can be contiguous (i.e. localized) or non contiguous (i.e. distributed or interlaced), or a combination thereof, to fulfill the OCB criteria, wherein:
Figure imgf000010_0001
[0042] In another example, OCB can be the minimum bandwidth to be occupied by PUCCH format 0 to meet regulations (for example, 80%-l00% of nominal channel bandwidth or 2 MHz bandwidth), wherein NB(? can be the number of sub-carriers per PRB (e.g., 12) and SCS can be the sub-carrier spacing (for example, in the sub-6 GHz frequency range, the SCS can be 15, 30, or 60 kHz). Scaling can be applied if the OCB and SCS are expressed in different units (e.g., OCB in units of MHz and SCS in units of kHz).
PUCCH 0
[0043] In another example, the length- 12 base sequence can be mapped on MRB
PRBs by applying MRB ' cyclic shifts. Different cyclic shifts can be applied on different PRBs. The cyclic shift pattern in different PRBs can be predefined in the specification or configured by higher layers via NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling. In another example, the cyclic shift pattern in different PRBs can be defined as a function of physical or virtual cell ID, symbol or slot index, or the like. In one example, a constant cyclic shift offset can be applied on different PRBs.
[0044] In another example, the base sequence
Figure imgf000010_0002
(n) can be mapped on the i-th PRB
PUCCH 0
(i = 0, 1, L ( MRB ' — 1)) and can be defined by a cyclic shift at i of a base sequence fu v(ri) according to ru i7 ! l’ (n) = eiai infu v(ji), 0 < n < Mzc„ where Mzc is the length of the sequence and
Figure imgf000010_0003
wherein can be a constant cyclic shift offset (e.g. mi & = i. moffset„ where moffset can be a constant cyclic shift offset) or can be a function of physical or virtual cell ID, symbol or slot index, or the like. The sequence x(n) can be mapped on PUCCH format 0 transmission bandwidth of MBB CCH'° = MRB CCH'° and can be generated according to:
Figure imgf000011_0001
wherein Ns PyUmCbCH’ 0 can be the number of symbols used for PUCCH format 0 transmission (e.g. Nsymb H’° = {1’2} for NR PUCCH format 0) and MBB CCH’° can be the total number of frequency sub-carriers on one symbol used for PUCCH format 0 transmission to fulfill the OCB criteria.
[0045] In another example, the same length- 12 sequence (with the same cyclic shift) can
Figure imgf000011_0002
be repeatedly mapped on MRB ’ PRBs by applying additional phase offsets on each of these repetitions. The phase offsets can be predefined in the specification, randomly selected by the UE, or configured by higher layers via MSI, RMSI, OSI or RRC signaling.
[0046] In another example, different base sequences (with cyclic shift hopping and/or base sequence hopping being applied) can be mapped on MR PBUCCH ' 0 PRBs. Additional phase offsets can be applied on the MR PB U CC H ' 0 different base sequences.
[0047] In another example, the base sequence
Figure imgf000011_0003
} (n) can be mapped on the i-th PRB
PUCCH 0
(i = 0, 1, L ( MRB ' — 1)) and can be defined by a cyclic shift a of a base sequence fUi V(ri) according to
Figure imgf000011_0004
= eianfu. v{n), 0 < n < Mzc, wherein Mzc can be the length of the sequence and the sequence group iq can be given by:
Ui = C fgh + fss + / )mod 30·
[0048] In another example fi A can be a fixed sequence group offset (e.g., fi A = i. f0 ffset, where f0 ffset can be a fixed value), or a function of physical or virtual cell ID, symbol or slot index, or the like. The sequence x(n) can be mapped on PUCCH format 0 transmission bandwidth of MBB CCH = NRB MRB CCH can be generated according to:
Figure imgf000012_0001
PU CC H 0
wherein, Nsymb ’ can be the number of symbols used for PUCCH format 0 transmission (e.g. Nsy b H’° = (1’2} for NR PUCCH format 0) and M^CCH’° can be the total number of frequency sub-carriers on one symbol used for PUCCH format 0 transmission to fulfill the OCB criteria.
[0049] In another example, FIGS. 2a - 2c illustrate the mapping of n sequences across frequency, in a contiguous manner (FIG. 2a), a non-contiguous/interlaced manner (FIG. 2b), and a combination thereof (FIG. 2c), wherein the n sequences can have different cyclic shifts and/or different phase offsets and/or different base sequences as described in the above embodiments. The transmission bandwidth over n PRBs can be greater than or equal to the OCB, as previously discussed. Sequence mapping across PRB as shown in FIG 2c is an example of interlace based PUCCH format 0 transmission wherein two consecutive interlaces can be assigned to PUCCH format 0.
[0050] In another example, for 1 -symbol NR PUCCH format 0, a length-l (e.g., Z > 12 or, l < 12), low peak-to-average power ratio (PAPR) sequence (e.g., Zadoff-Chu (ZC) sequence or computer generated sequence (CGS)) can be used and mapped across frequency on L subcarriers, which may be contiguous (i.e. localized), non-contiguous (i.e. distributed or interlaced), or a combination thereof, to fulfill the OCB criteria, wherein:
L ³ \{OCB/(SCS)} 1
and Z can be a factor of L and other quantities (e.g., OCB and SCS) can be similar to the above example.
[0051] In another example, the same length-Z base sequence can be mapped on L frequency sub-carriers by applying L/l cyclic shifts. The cyclic shift pattern can be predefined in the specification or configured by higher layers via NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling. In another example, the cyclic shift pattern can be defined as a function of physical or virtual cell ID, symbol or slot index, or the like. In another example, a constant cyclic shift offset can be applied to generate L/l different cyclic shifts.
[0052] In another example, the length-Z sequence (with the same cyclic shift) can be repeatedly mapped on L frequency sub-carriers by applying additional phase offsets on each of these repetitions.
[0053] In another example, different base sequences (with cyclic shift hopping and/or base sequence hopping being applied) can be mapped on L frequency sub-carriers.
Additional phase offsets can be applied on these L/l different base sequences.
[0054] In another example, a length-Z sequence can be mapped (e.g., non-contiguously or interlaced) across frequency on Z sub-carriers so that the bandwidth occupied by Z tones meets the OCB criteria.
[0055] In another example, a long computer generated sequence (CGS) or ZC sequence can be applied for the transmission of PUCCH format 0. The length of CGS or ZC sequence can be equal to the length of allocated subcarriers. As one example, a low PAPR sequence r^a/S> (n) of length- L can be generated by a cyclic shift a of a base sequence fu v(n according to
Figure imgf000013_0001
0 < n < Mzc, wherein Mzc = m/VBB/26 can be the length of the sequence and m
Figure imgf000013_0002
can depend on the interlace size (i.e., when length- L sequence is mapped on an interlace with 171
Figure imgf000013_0003
PRBs Per interlace).
In another example, for a bandwidth (BW) of 20 MHz, = 10/11· In another
Figure imgf000013_0004
example, a length-L sequence can be mapped on L contiguous frequency sub-carriers.
[0056] In another example, FIGS. 2d- 2f illustrate different examples of candidate sequence types and mapping schemes for enhancing the NR PUCCH format 0 to support multi-PRB transmissions for 20 MHz BW and 30 KHz SCS (e.g., total number of available PRBs = 51), where the PRBs can be mapped (e.g., non-contiguously or interlaced) across frequency. In FIG. 2d, a single length-l2 base sequence can be mapped on 11 PRBs of one interlace by applying 11 different cyclic shifts. In FIG. 2e, 11 different base sequences (with the same cyclic shift) can be mapped on the 11 PRBs on one interlace. In FIG. 2f, a single length- 132 low PAPR base sequence (with certain cyclic shift a, where 0 < a < 132) can be mapped non-contiguously on 11 PRBs of one interlace. [0057] In another example, for iV-symbol NR PUCCH format 0, where TV >1 (for example, N = 2), similar examples as discussed above with relation to N =1 can be applied, wherein the same frequency domain allocation on one symbol can be repeated across N symbols of PUCCH format 0.
[0058] In another example, for iV-symbol NR PUCCH format 0, where N > 1 (for example, N = 2), frequency hopping can be enabled so that the total bandwidth occupied by the frequency hops fulfills the OCB criteria. In another example, 2-symbol NR- PUCCH format 0 can be used with frequency hopping being enabled between the lst and the 2nd symbols so that the total hopping bandwidth (BW) (including the 1 st and 2nd hops) can be greater than or equal to the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz), as illustrated in FIG. 2g. Base sequence hopping and/or cyclic shift hopping and/or additional phase offset may be applied between the frequency hops.
Enhancements of NR PUCCH format 1
[0059] In one example, the DMRS and UCI sequences on different symbols in time can be repeatedly mapped across frequency on the same set of M^g CCH 1 PRBs (each PRB can include 12 frequency sub-carriers), which may be contiguous (i.e. localized), non contiguous (i.e. distributed or interlaced), or a combination thereof, to fulfill the OCB criteria, where:
M™'1 > \{OCB/(Ns R c B * SCS)}].
[0060] In another example, OCB can be the minimum bandwidth to be occupied by PUCCH format 1 to meet regulations (for example 80%-l00% of nominal channel bandwidth or 2 MHz bandwidth), iV™ can be the number of sub-carriers per PRB (e.g. 12) and SCS can be sub-carrier spacing (for example, in sub-6 GHz frequency range, SCS can be 15, 30, or 60 kHz). Scaling can be applied if the OCB and SCS are expressed in different units (e.g., OCB in units of MHz and SCS in units of kHz).
[0061] In another example, the DMRS and UCI sequences can be used in NR PUCCH format 1 (i.e. length-l2, low PAPR, computer generated sequences), and can be mapped M^, cch'1 times across frequency contiguously or non-contiguously by applying M^, CCH'1 cyclic shifts. [0062] In another example, the base sequence ^ ( n ) for DMRS (and spreading sequence of UCI) can be mapped on the i-th PRB ( i = 0, 1, L (M^g CCH 1— 1)), and can be defined by a cyclic shift at i of a base sequence fU V(ri) according to
Figure imgf000015_0001
= eiai infu v(n), 0 < n < Mzc. wherein Mzc can be the length of the sequence and
Figure imgf000015_0002
wherein m, can be a constant cyclic shift offset (e.g. mi & = i. moffset, where moffset is a constant cyclic shift offset) or can be a function of physical or virtual cell ID, symbol or slot index, or the like. A block of complex valued symbols y(n) =
fO c/(0).
Figure imgf000015_0003
mod Nsc can be blockwise spread with orthogonal sequence w; (m) and mapped on PUCCH format 1 transmission bandwidth of M^CCH 1 = N^c
Figure imgf000015_0004
according to:
(m'M PUCCH.ljyPUCCH.l PUCCH, 1
S, C SF,m' + mM, c + nj = Wj(ni).y(n )
Figure imgf000015_0005
0 no intra-slot frequency hopping m‘ = {o.1 intra-slot frequency hopping enabled wherein
Figure imgf000015_0006
can be given by Table 6.3.2.4.1-1 of 3GPP TS 38.211 V15.5.0 section 20 6.3.2.4.1, d(0) can be as defined in section 6.3.2.4.1 of 3GPP TS 38.211 V15.5.0 and
Ms PcUCCH ' 1 can be the total number of frequency sub-carriers on one symbol used for PUCCH format 1 transmission to fulfill the OCB criteria.
[0063] In another example, the cyclic shifts applied on DMRS sequences can be the same or different from those applied on UCI sequences. The examples for the design of 25 PUCCH format 0 can be applied for the generation of UCI and DMRS sequence of
PUCCH format 1. For example, if ni DMRS is the cyclic shift applied on the DMRS sequence mapped on the i-th PRB (i = 0, 1, . . , MRR CCH’1— 1 ), the cyclic shift applied on UCI sequences can be ni ucI, wherein:
Figure imgf000015_0007
wherein Vj 0^set can be predefined in the specification and can be either a fixed value or a function of system parameters like physical cell ID, slot or symbol index or the like, or provided by higher layer signaling. Mzc can be the length of the sequence (e.g. Mzc = 12). In this example, ni DMRScan be defined similar to ai i for enhanced PUCCH format 1 as previously discussed. In another example, m! can be set to 0 (e.g., distributed or interlaced) enhanced PUCCH format 1, with
Figure imgf000016_0001
> 1 because frequency diversity can be achieved from distributed PRB allocation without additional frequency hopping.
[0064] In another example, the same DMRS and UCI sequences can be repeatedly
Figure imgf000016_0002
mapped on MRB ’ PRBs by applying additional phase offsets on each of these repetitions. The phase offsets applied on DMRS sequences can be the same or different from those applied on UCI sequences.
[0065] In another example, different base sequences (with cyclic shift hopping and/or base sequence hopping being applied) can used for DMRS and spreading sequence for UCI to generate each of the
Figure imgf000016_0003
copies of PUCCH format 1, to be mapped on Mrb cch’1 PRBS. Additional phase offsets can be applied on these MRB CCH’1 different copies of PUCCH format 1 DMRS and UCI sequences, wherein the phase offsets applied on DMRS sequences can be the same or different from those applied on UCI sequences. In another example, the base sequence
Figure imgf000016_0004
(n) used for DMRS (and spreading sequence for UCI) can be mapped on the i-th PRB (i = 0, 1, L (MRB CCH 1— 1)) and can be defined by a cyclic shift a of a base sequence fu. v(n) according to
Figure imgf000016_0005
=
e'anfUi V(n), 0 < n < Mzc. where Mzc can be the length of the sequence and the sequence group iq can be provided by:
Figure imgf000016_0006
30.
[0066] In another example, / D can be a fixed sequence group offset (e.g. f A = i. /offset · where foSse t can be a fixed value), or a function of physical or virtual cell ID, symbol or slot index, or the like, wherein fgh and fss can be the same as defined in 3GPP TS 38.211 V15.5.0 section 6.3.2.2.1. A block of complex valued symbols y(n) =
Figure imgf000016_0007
mod Nsc ) can be blockwise spread with orthogonal sequence
Wj (m) given by Table 6.3.2.4.1-2 of3GPP TS 38.211 V15.5.0 section 6.3.2.4.1 and mapped on PUCCH format 1 transmission bandwidth of Msc
Figure imgf000016_0008
' = Nsc Mrr' CCH'1 according to::
Figure imgf000017_0001
opping
Figure imgf000017_0003
(0,1 intra-slot frequency hopping enabled wherein
Figure imgf000017_0002
can be provided by Table 6.3.2.4.1-1 of 3GPP TS 38.211 V15.5.0 section 6.3.2.4.1, d 0) can be as defined in section 6.3.2.4.1 of 3GPP TS 38.211 V15.5.0, and Ms PcU CC H ' 1 can be the total number of frequency sub-carriers on one symbol used for PUCCH format 1 transmission to meet OCB criteria.
[0067] In another example, for l-symbol NR PUCCH format 1, a length-l (where / > 12 or, l < 12), low PAPR sequence (for example, ZC sequence or CGS) can be used for DMRS and spreading sequence of UCI, and mapped across frequency on the same L subcarriers, which can be contiguous (i.e. localized), non-contiguous (i.e. distributed or interlaced), or a combination thereof to fulfill the OCB criteria, where:
L ³ \{OCB/(SCS)} 1
And l can be a factor of L and other quantities (e.g., OCB and SCS) can be similar to above example.
[0068] In another example, length- 1 DMRS and UCI sequences can be mapped on L frequency sub-carriers by applying L/l cyclic shifts. The cyclic shifts applied on DMRS sequences can be different from those applied on UCI sequences.
[0069] In another example, the same length-Z DMRS and UCI sequences can be repeatedly mapped on L frequency sub-carriers by applying additional phase offsets on each of these repetitions. The phase offsets applied on DMRS sequences can be different from those applied on UCI sequences. For example, if ni DMRS denotes the cyclic shift applied on DMRS sequences, the cyclic shift applied on UCI sequences can be nUCI, wherein: ni,UCl — ( n i,DMRS+Vi,offset m°d (l ) ,
Wherein offset can be predefined in the specification and can be either a fixed value or a function of system parameters like physical cell ID, slot or symbol index, or provided by higher layer signaling.
5 [0070] In another example, different base sequences (with cyclic shift hopping and/or base sequence hopping being applied) can used for DMRS and spreading sequence of UCI to generate each of L/l copies of PUCCH format 1, to be mapped on L frequency sub-carriers. Additional phase offsets can be applied on these L/l different copies of PUCCH format 1, wherein the phase offsets applied on the DMRS sequences can be f O different from those applied on UCI sequences.
[0071] In another example, length- 1 DMRS and UCI sequences can be mapped (e.g., non- contiguously or interlaced) across frequency on the same l sub-carriers so that the bandwidth occupied by l tones of DMRS and UCI fulfill the OCB criteria.
[0072] In another example, FIGS. 3a - 3c illustrate the mapping of n sets of sequences
15 across frequency (each set including 2 DMRS sequences and 2 UCI sequences in this example mapped over 4 symbols of PUCCH), (e.g., contiguous in FIG. 3a; non contiguous in FIG. 3b; or a combination thereof in FIG. 3c), wherein the n sequences can have different cyclic shifts or different phase offsets or different base sequences as described in the above example and the transmission bandwidth over n PRBs can be
20 greater than or equal to the OCB. In the preceding examples, frequency hopping can be enabled or disabled.
[0073] In another example, a long computer generated sequence (CGS) or ZC sequence can be applied for the generation of DMRS and UCI sequence. The length of CGS or ZC sequence is equal to the length of allocated subcarriers. As one example, a low PAPR
25 sequence r^a/S> (n) of length- L can be generated by a cyclic shift a of a base sequence fu,v( ) according to r^/S) (n) = eianfu v(n), 0 < n < Mzc, as defined in 3GPP TS 38.211 vl5.5.0 section 5.2.2, wherein Mzc = m/V B/20 can be the length of the sequence and m/2 can depend on the interlace size (i.e., when length-L sequence is mapped on an interlace with 171 /2s PRBs per interlace). In another example, for a BW of 20 MHz,
30 m/7s = 10/11· In another example, length-L sequence can be mapped on L contiguous frequency sub-carriers.
[0074] In another example, for iV-symbol NR PUCCH format 1 (4 < N < 14), frequency hopping can be enabled so that the total BW occupied by the two frequency hops fulfills the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz), as illustrated in FIG. 3d, where 8-symbol PUCCH can be frequency hopped with 4-symbols per hop. Base sequence hopping and/or cyclic shift hopping and/or additional phase offset can be applied between the frequency hops.
Enhancements of NR PUCCH format 2
[0075] In one example, a lower limit on the number of PRBs (nPRB min) can be predefined in the specification or configured by higher layer signaling (e.g., RRC signaling) or derived based on the subcarrier spacing and allocated BW so that PUCCH format 2 can be allocated at least nPRB min number of PRBs or more when localized mapping is used across frequency so as to fulfill the OCB criteria. nPRB,min \{OCB/(Nsf SCS)}1
wherein SCS can denote sub-carrier spacing and iV™ can denote the number of sub carriers in one PRB (e.g., 12). Scaling can be applied if the OCB and SCS are expressed in different units. In another example, depending on the OCB criteria, nPRB min can be greater than the maximum number of PRBs configured in Release 15 specification for NR (i.e. 16 PRBs).
[0076] In another example, PUCCH format 2 can be configured by higher layer signaling
(e.g., RRC signaling), with MR PBUCCH ' 2 number of PRBs which can be mapped non- contiguously (e.g., distributed or interlaced) in the frequency domain to fulfill the OCB criteria. In another example, MR PBUCCH ' 2 can be determined by the total number of UCI bits and the configured maximum coding rate, and:
M CCH'2 > \{OCB/(Ns R c B * SCS)} 1.
[0077] In another example, for iV-symbol NR PUCCH format 2, wherein N > 1 (for example, N = 2), the preceding examples can be applied, wherein the same frequency domain resource allocation on one symbol can be repeated across N symbols of PUCCH format 2.
[0078] In another example, for iV-symbol NR PUCCH format 2, where N > 1 (for example, N = 2), frequency hopping can be enabled so that the total bandwidth occupied by the frequency hops fulfills the OCB criteria. In another example, 2-symbol NR- PUCCH format 2 can be used with frequency hopping enabled between the lst and the 2nd symbols, wherein the total hopping bandwidth including the lst and 2nd hops can be greater than or equal to the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz).
[0079] In another example, NR PUCCH format 2 can be enhanced to support transmission of 1 to 2 UCI bits (e.g., HARQ-ACK or SR bits without CSI reports). In this example, simplex or repetition code can be used to encode 1 or 2-bits HARQ-ACK with or without SR. For SR-only transmission, bit 1 or bit 0 can be transmitted using coding schemes discussed in the preceding corresponding to positive or negative SR respectively. In another example, rather than using simplex or repetition codes, existing coding schemes in NR for PUCCH format 2 can also be used to transmit 1 to 2 UCI bits using PUCCH format 2.
[0080] In another example, zero padding can be applied for SR or 1 to 2 UCI bits so that at least 3 bits can be carried by PUCCH format 2. The preceding examples can be applied when PUCCH format 0 or 1 is not defined for the NR unlicensed system.
Enhancements of NR PUCCH format 3
[0081] In one example, a lower limit on the number of PRBs (nPRBmin) can be configured by higher layer signaling (e.g., RRC signaling), such that PUCCH format 3 can be allocated at least nPRBmin number of PRBs or more when localized mapping is used across frequency to meet the OCB criteria.
Figure imgf000020_0001
wherein SCS denotes sub-carrier spacing and a, b, and c are integers and iV Jf denotes the number of sub-carriers in one PRB (e.g. 12). Scaling can be applied in if OCB and SCS are expressed in different units. In another example, depending on the OCB criteria, nPRB,min can be greater than the maximum number of PRBs configured in the Release 15 specification for NR (i.e. 16 PRBs).
[0082] In another example, PUCCH format 3 can be configured by higher layer signaling
(e.g., RRC signaling), with PUCCH 3
MRB ' number of PRBs which can be mapped non- contiguously (e.g., distributed or interlaced) in the frequency domain to meet the OCB criteria. In another example, n can be determined by the total number of UCI bits and the configured maximum coding rate, and:
Figure imgf000021_0001
[0083] In another example, for N-symbol NR PUCCH format 3 (4 < N < 14), frequency hopping can be enabled so that the total bandwidth occupied by the two frequency hops fulfills the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz).
[0084] In another example, NR PUCCH format 3 can support transmission of 1 - 2 UCI bits (e.g., HARQ-ACK or SR bits without CSI reports). In this example, simplex or repetition code can be used to encode 1 or 2-bit HARQ-ACK with or without SR. For SR-only transmission, bit 1 or bit 0 can be transmitted using coding schemes discussed in the preceding to positive or negative SR respectively. In another example, instead of using simplex or repetition codes, existing coding schemes in NR for PUCCH format 3 can be used to transmit 1 to 2 UCI bits using PUCCH format 3.
[0085] In another example, zero padding can be applied for SR or 1 to 2 UCI bits so that at least 3 bits can be carried by PUCCH format 2. The preceding examples can be applied for the case wherein PUCCH format 0 or 1 is not defined for an NR unlicensed system.
Enhancements of NR PUCCH format 4
[0086] In one example, NR PUCCH format 4 can be configured by higher layer signaling (e.g., RRC signaling), with MRB CCH’4 number of PRBs (MRB CCH’4 > 1)), which can be mapped contiguously or non-contiguously (e.g., distributed or interlaced) in the frequency domain to fulfill the OCB criteria.
Figure imgf000021_0002
[0087] In another example, to enhance NR PUCCH format 4 frequency domain resource allocation from 1 PRB to more than 1 PRB, MRB CCH'4 can be determined by the total number of UCI bits and a configured maximum coding rate such that the encoding, scrambling, and DFT-pre-coding of UCI bits can be based on the total number of available frequency resources and UCI symbols mapped across MRB CCH’A PRBs. For a DMRS sequence, a cyclic shift offset configured by higher layer signaling can be applied 'ii the DMRS sequence of the lst PRB to generate the DMRS sequence of the next M7CCH'4 PRBS such that cyclic shift ncs i can be applied on the DMRS sequence corresponding to the i-th PRB (i = 0,1,2, . .
Figure imgf000022_0001
— 1) can be: ncs,i = (%,o + i * Vcs) mod MS Pp CCHA, wherein ncs o can be the cyclic shift applied on the DMRS sequence mapped on the lst PRB (i=0), MS P7CHA = M7P CCHA * N can be the length of the DMRS sequence mapped
Figure imgf000022_0002
sub-carriers and Vcs can be an offset provided by higher layer signaling. The preceding examples for the generation of the DMRS sequence for NR PUCCH format 3 with length greater than 12 for NR unlicensed system can be applied for the generation of the DMRS sequence for enhanced PUCCH format 4 for unlicensed spectrum.
[0088] In another example, UE multiplexing and pre-DFT OCC can be applied on a per- PRB basis. The same OCC can be applied on UCI symbols mapped on each PRB with OCC cycling to keep PAPR low, or block-wise spread OCC applied on
Figure imgf000022_0003
CCHA PRBs on which UCI symbols can be mapped. In another example, a one-to-one correspondence between OCC index on UCI symbols and cyclic shift on DMRS sequences on the lst PRB can be configured.
[0089] In another example, block-wise spreading can applied on PUCCH format 4 with M7CCHA > 1 and M7CCHA = 2“2 3“3 5“4·. A block of complex valued symbols
Figure imgf000022_0004
— 1) can be generated according to section 6.3.2.6.3 of 3GPP
TS 38.211 vl 5.5.0:
Figure imgf000022_0005
PUCCH, 4
k = 0, 1, ... , M Si C 1
/ = 0,1. (Ns7CCHAMsymb/M^CCH·4) wherein
Figure imgf000022_0006
N S,F ,max £ Nsc wn can t>e based on DFT based OCC code block- wise spread by a factor Ms£ CCH’4 / NP p CCHA , with n denoting the index of the orthogonal sequence (n
0, 1, . . , N7CCHA - 1) . [0090] In another example, block-wise spreading can be applied on enhanced PUCCH format 3 (e.g., interlaced). A block of complex valued symbols
y(0), ... , y(NsF CCH'3Msymb— 1) can be generated according to section 6.3.2.6.3 of 3GPP TS 38.211 vl5.5.0:
Figure imgf000023_0001
l = 0,1. (Ns7 CCH’3Msymb/M CCH·3) wherein
Figure imgf000023_0002
NsF max'3— ^sc w n can be based on DFT based OCC code block- wise spread by a factor M^CCH'3 /N^p CCH'3, with n denoting the index of the orthogonal sequence (n =
0, 1, . . , N™cch’3 - 1).
[0091] In another example, orthogonal sequences wn(m) for PUCCH format s with N CCH,S = 2 and
Figure imgf000023_0003
> 1 can be obtained from Table 6.3.2.6.3-1 of 3GPP TS 38.211 vl5.5.0 by blockwise spreading each row of Table 6.3.2.6.3-1, wherein wn(m) is of length
Figure imgf000023_0004
TABLE 1:
Figure imgf000023_0005
[0092] In another example, Table 1 can be enhanced to wn(m ) for PUCCH format s with
PUCCH, S -PUCCH, s
N S. F = 4 and Ml RB > 1.
[0093] In another example, for N-symbol NR PUCCH format 4 (4 £ N £ 14), frequency hopping can be enabled so that the total bandwidth occupied by the two frequency hops fulfills the OCB criteria (for example, 80%-l00% of nominal channel bandwidth or 2 MHz. Frequency mapping of UCI and DMRS symbols can be applied on n PRBs (n >
2).
[0094] In another example, for iV-symbol NR PUCCH format 4 (4 < N < 14) occupying 12 sub-carriers over 1 PRB, the 12 sub-carriers can be mapped non-contiguously across frequency to fulfill the OCB criteria.
[0095] In another example, NR PUCCH format 4 can be enhanced to support transmission of 1 to 2 UCI bits (e.g., HARQ-ACK or SR bits without CSI reports). In this example, simplex or repetition code may be used to encode 1 or 2-bits HARQ-ACK with or without SR. For SR only transmission, bit 1 or bit 0 can be transmitted using coding schemes corresponding to positive or negative SR respectively. In another example, instead of using simplex or repetition codes, existing coding schemes in NR for PUCCH format 4 can be used to transmit 1 to 2 UCI bits using PUCCH format 4.
[0096] In another example, zero padding can be applied for SR or 1 to 2 UCI bits so that at least 3 bits can be carried by PUCCH format 4. The preceding examples can be applied when PUCCH format 0 or 1 is not defined for NR unlicensed system.
[0097] Another example provides functionality 400 of a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), as shown in FIG. 4. The UE can comprise one or more processors. The one or more processors can be configured to identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body, as in block 410. The one or more processors can be configured to map, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on
Figure imgf000024_0001
physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the MRB CCH,X PRBs includes NBc subcarriers and the
Figure imgf000024_0002
PRBs are distributed in the frequency domain, and wherein n is a positive integer, MRB CCH,X is a positive integer, and iV™ is a positive integer, as in block 420. The one or more processors can be configured to encode, at the UE, information on the MRB CCH,X PRBs for transmission on the PUCCH, as in block 430. In addition, the UE can comprise a memory interface configured to retrieve the information from a memory.
[0098] Another example provides functionality 500 of a new radio node B (gNB) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR- unlicensed (NR-U), as shown in FIG. 5. The gNB can comprise one or more processors. The one or more processors can be configured to decode, at the gNB, information located in MRB CCH,X physical resource blocks (PRBs) received on a PUCCH, wherein MRB CCH,X is a positive integer, as in block 510. The one or more processors can be configured to identify, at the gNB, a minimum occupied bandwidth of the PUCCH based on a regulation of a regulatory body, wherein on one or more of the n symbols in a time domain, the MRB ' PRBs each include one or more sequences, wherein the
Figure imgf000025_0001
PRBs are determined at the user equipment (UE) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M^B CCH,X PRBs includes N c subcarriers and the
Figure imgf000025_0002
PRBs are distributed in the frequency domain, and wherein n is a positive integer NB(? is a positive integer, as in block 520. In addition, the gNB can comprise a memory interface configured to send the information to a memory.
[0099] Another example provides at least one machine readable storage medium having instructions 600 embodied thereon for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), as shown in FIG. 6. The instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The instructions when executed perform: identifying, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body, as in block 610. The instructions when executed perform: mapping, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on MRB ' physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the MRB CCH,X PRBs includes NBc subcarriers and the
Figure imgf000025_0003
PRBs are distributed in the frequency domain, and wherein n is a positive integer, MR PBUCCH ' x is a positive integer, and /Vi6 is a positive integer, as in block 620. The instructions when executed perform: encoding, at the UE, information on the MR PBUCCH x PRBs for transmission on the PUCCH, as in block 630.
[00100] While examples have been provided in which a gNB has been specified, they are not intended to be limiting. An evolved node B (eNB) can be used in place of a next generation node B (gNB), a new radio node B (gNB), or a new radio base station (NR BS). Accordingly, unless otherwise stated, any example herein in which a gNB has been disclosed, can similarly be disclosed with the use of eNB or new radio base station (NR BS).
[00101] Figure 7 illustrates an example architecture of a system 700 of a network, in accordance with various embodiments. The following description is provided for an example system 700 that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.
[00102] As shown by Figure 7, the system 700 includes UE 70 la and UE 70 lb (collectively referred to as“UEs 701” or“UE 701”). In this example, UEs 701 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non- mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an
Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or“smart” appliances, MTC devices, M2M, IoT devices, and/or the like.
[00103] In some embodiments, any of the UEs 701 may be IoT UEs, which may comprise a network access layer designed for low-power IoT applications utilizing short lived UE connections. An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device via a PLMN, ProSe or D2D
communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
[00104] The UEs 701 may be configured to connect, for example, communicatively couple, with an or RAN 710. In embodiments, the RAN 710 may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term“NG RAN” or the like may refer to a RAN 710 that operates in an NR or 5G system 700, and the term“E-UTRAN” or the like may refer to a RAN 710 that operates in an LTE or 4G system 700. The UEs 701 utilize connections (or channels) 703 and 704, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below).
[00105] In this example, the connections 703 and 704 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UEs 701 may directly exchange communication data via a ProSe interface 705. The ProSe interface 705 may alternatively be referred to as a SL interface 705 and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.
[00106] The UE 70lb is shown to be configured to access an AP 706 (also referred to as“WLAN node 706,”“WLAN 706,”“WLAN Termination 706,”“WT 706” or the like) via connection 707. The connection 707 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 706 would comprise a wireless fidelity (Wi-Fi®) router. In this example, the AP 706 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE 70 lb, RAN 710, and AP 706 may be configured to utilize LWA operation and/or LWIP operation. The LWA operation may involve the UE 70 lb in RRC_CONNECTED being configured by a RAN node 7lla-b to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 70 lb using WLAN radio resources (e.g., connection 707) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 707. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
[00107] The RAN 710 can include one or more AN nodes or RAN nodes 711 a and 71 lb (collectively referred to as“RAN nodes 711” or“RAN node 711”) that enable the connections 703 and 704. As used herein, the terms“access node,”“access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term“NG RAN node” or the like may refer to a RAN node 711 that operates in an NR or 5G system 700 (for example, a gNB), and the term“E-UTRAN node” or the like may refer to a RAN node 711 that operates in an LTE or 4G system 700 (e.g., an eNB). According to various embodiments, the RAN nodes 711 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
[00108] In some embodiments, all or parts of the RAN nodes 711 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 711; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 711; or a“lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 711. This virtualized framework allows the freed-up processor cores of the RAN nodes 711 to perform other virtualized applications. In some implementations, an individual RAN node 711 may represent individual gNB-DUs that are connected to a gNB-CU via individual Fl interfaces (not shown by Figure 7). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server that is located in the RAN 710 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes 711 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 701, and are connected to a 5GC via an NG interface (discussed infra).
[00109] In V2X scenarios one or more of the RAN nodes 711 may be or act as RSUs. The term“Road Side Unit” or“RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a“UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an“eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a“gNB-type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs 701 (vUEs 701). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the
aforementioned low latency communications, as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications. The computing device(s) and some or all of the
radiofrequency circuitry of the RSU 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 and/or a backhaul network.
[00110] Any of the RAN nodes 711 can terminate the air interface protocol and can be the first point of contact for the UEs 701. In some embodiments, any of the RAN nodes 711 can fulfill various logical functions for the RAN 710 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
[00111] In embodiments, the UEs 701 can be configured to communicate using OFDM communication signals with each other or with any of the RAN nodes 711 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[00112] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 711 to the UEs 701, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot. Such a time -frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time- frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
[00113] According to various embodiments, the UEs 701 and the RAN nodes 711 communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the“licensed spectrum” and/or the“licensed band”) and an unlicensed shared medium (also referred to as the“unlicensed spectrum” and/or the“unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band. [00114] To operate in the unlicensed spectrum, the UEs 701 and the RAN nodes 711 may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UEs 701 and the RAN nodes 711 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
[00115] LBT is a mechanism whereby equipment (for example, UEs 701 RAN nodes 711, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.
[00116] Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 701, AP 706, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (ps); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulations.
[00117] The LAA mechanisms are built upon CA technologies of LTE- Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.
[00118] CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities. The other serving cells are referred to as S Cells, and each SCell may provide an individual SCC for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE 701 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as“LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.
[00119] The PDSCH carries user data and higher-layer signaling to the UEs 701. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 701 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 70 lb within a cell) may be performed at any of the RAN nodes 711 based on channel quality information fed back from any of the UEs 701. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 701.
[00120] The PDCCH uses CCEs to convey the control information. Before being mapped to resource elements, the PDCCH complex- valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the DCI and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=l, 2, 4, or 8).
[00121] Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.
[00122] The RAN nodes 711 may be configured to communicate with one another via interface 712. In embodiments where the system 700 is an LTE system, the interface 712 may be an X2 interface 712. The X2 interface may be defined between two or more RAN nodes 711 (e.g., two or more eNBs and the like) that connect to EPC 720, and/or between two eNBs connecting to EPC 720. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 701 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 701 ; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.
[00123] In embodiments where the system 700 is a 5G or NR system, the interface 712 may be an Xn interface 712. The Xn interface is defined between two or more RAN nodes 711 (e.g., two or more gNBs and the like) that connect to 5GC 720, between a RAN node 711 (e.g., a gNB) connecting to 5GC 720 and an eNB, and/or between two eNBs connecting to 5GC 720. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 701 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 711. The mobility support may include context transfer from an old (source) serving RAN node 711 to new (target) serving RAN node 711; and control of user plane tunnels between old (source) serving RAN node 711 to new (target) serving RAN node 711. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.
[00124] The RAN 710 is shown to be communicatively coupled to a core network— in this embodiment, core network (CN) 720. The CN 720 may comprise a plurality of network elements 722, which are configured to offer various data and
telecommunications services to customers/subscribers (e.g., users of UEs 701) who are connected to the CN 720 via the RAN 710. The components of the CN 720 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 720 may be referred to as a network slice, and a logical instantiation of a portion of the CN 720 may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC
components/ functions .
[00125] Generally, the application server 730 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 730 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 701 via the EPC 720.
[00126] In embodiments, the CN 720 may be a 5GC (referred to as“5GC 720” or the like), and the RAN 710 may be connected with the CN 720 via an NG interface 713. In embodiments, the NG interface 713 may be split into two parts, an NG user plane (NG-U) interface 714, which carries traffic data between the RAN nodes 711 and a UPF, and the Sl control plane (NG-C) interface 715, which is a signaling interface between the RAN nodes 711 and AMFs.
[00127] In embodiments, the CN 720 may be a 5G CN (referred to as“5GC 720” or the like), while in other embodiments, the CN 720 may be an EPC). Where CN 720 is an EPC (referred to as“EPC 720” or the like), the RAN 710 may be connected with the CN 720 via an Sl interface 713. In embodiments, the Sl interface 713 may be split into two parts, an Sl user plane (Sl-U) interface 714, which carries traffic data between the RAN nodes 711 and the S-GW, and the Sl-MME interface 715, which is a signaling interface between the RAN nodes 711 and MMEs.
[00128] Figure 8 illustrates an example of a platform 800 (or“device 800”) in accordance with various embodiments. In embodiments, the computer platform 800 may be suitable for use as UEs 701, application servers 730, and/or any other element/device discussed herein. The platform 800 may include any combinations of the components shown in the example. The components of platform 800 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 800, or as components otherwise incorporated within a chassis of a larger system. The block diagram of Figure 8 is intended to show a high level view of components of the computer platform 800. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.
[00129] Application circuitry 805 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports. The processors (or cores) of the application circuitry 805 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 800. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM,
EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.
[00130] The processor(s) of application circuitry may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuitry may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.
[00131] As examples, the processor(s) of application circuitry 805 may include an Intel® Architecture Core™ based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, CA. The processors of the application circuitry 805 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processors) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P- class processors; an ARM-based design licensed from ARM Holdings, Ltd., such as the ARM Cortex- A, Cortex-R, and Cortex-M family of processors; or the like. In some implementations, the application circuitry 805 may be a part of a system on a chip (SoC) in which the application circuitry 805 and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.
[00132] Additionally or alternatively, application circuitry 805 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of application circuitry 805 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 805 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.
[00133] The baseband circuitry 810 may be implemented, for example, as a solder- down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 810 are discussed infra with regard to Figure 9.
[00134] The RFEMs 815 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some
implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 911 of Figure 9 infra), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub- mmWave radio functions may be implemented in the same physical RFEM 815, which incorporates both mmWave antennas and sub-mmWave.
[00135] The memory circuitry 820 may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry 820 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry 820 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 820 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry 820 may be on-die memory or registers associated with the application circuitry 805. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry 820 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform 800 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
[00136] Removable memory circuitry 823 may include devices, circuitry,
enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform 800. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.
[00137] The platform 800 may also include interface circuitry (not shown) that is used to connect external devices with the platform 800. The external devices connected to the platform 800 via the interface circuitry include sensor circuitry 821 and electro mechanical components (EMCs) 822, as well as removable memory devices coupled to removable memory circuitry 823.
[00138] The sensor circuitry 821 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units (IMUs) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc.
[00139] EMCs 822 include devices, modules, or subsystems whose purpose is to enable platform 800 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs 822 may be configured to generate and send messages/ signalling to other components of the platform 800 to indicate a current state of the EMCs 822. Examples of the EMCs 822 include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform 800 is configured to operate one or more EMCs 822 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.
[00140] In some implementations, the interface circuitry may connect the platform 800 with positioning circuitry 845. The positioning circuitry 845 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS.
Examples of navigation satellite constellations (or GNSS) include United States’ GPS, Russia’s GLONASS, the European Union’s Galileo system, China’s BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan’s QZSS, France’s DORIS, etc.), or the like. The positioning circuitry 845 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 845 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 845 may also be part of, or interact with, the baseband circuitry and/or RFEMs 815 to communicate with the nodes and components of the positioning network. The positioning circuitry 845 may also provide position data and/or time data to the application circuitry 805, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like
[00141] In some implementations, the interface circuitry may connect the platform 800 with Near-Field Communication (NFC) circuitry 840. NFC circuitry 840 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 840 and NFC-enabled devices external to the platform 800 (e.g., an“NFC touchpoint”). NFC circuitry 840 comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 840 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 840, or initiate data transfer between the NFC circuitry 840 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 800.
[00142] The driver circuitry 846 may include software and hardware elements that operate to control particular devices that are embedded in the platform 800, attached to the platform 800, or otherwise communicatively coupled with the platform 800. The driver circuitry 846 may include individual drivers allowing other components of the platform 800 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 800. For example, driver circuitry 846 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 800, sensor drivers to obtain sensor readings of sensor circuitry 821 and control and allow access to sensor circuitry 821, EMC drivers to obtain actuator positions of the EMCs 822 and/or control and allow access to the EMCs 822, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
[00143] The power management integrated circuitry (PMIC) 825 (also referred to as “power management circuitry 825”) may manage power provided to various components of the platform 800. In particular, with respect to the baseband circuitry 810, the PMIC 825 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC 825 may often be included when the platform 800 is capable of being powered by a battery 830, for example, when the device is included in a UE 701.
[00144] In some embodiments, the PMIC 825 may control, or otherwise be part of, various power saving mechanisms of the platform 800. For example, if the platform 800 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 800 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 800 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 800 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The platform 800 may not receive data in this state; in order to receive data, it must transition back to RRC Connected state. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable. [00145] A battery 830 may power the platform 800, although in some examples the platform 800 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 830 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 830 may be a typical lead-acid automotive battery.
[00146] In some implementations, the battery 830 may be a“smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform 800 to track the state of charge (SoCh) of the battery 830. The BMS may be used to monitor other parameters of the battery 830 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 830. The BMS may communicate the information of the battery 830 to the application circuitry 805 or other components of the platform 800. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 805 to directly monitor the voltage of the battery 830 or the current flow from the battery 830. The battery parameters may be used to determine actions that the platform 800 may perform, such as transmission frequency, network operation, sensing frequency, and the like.
[00147] A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 830. In some examples, the power block may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 800. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 830, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power
Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.
[00148] User interface circuitry 850 includes various input/output (I/O) devices present within, or connected to, the platform 800, and includes one or more user interfaces designed to enable user interaction with the platform 800 and/or peripheral
component interfaces designed to enable peripheral component interaction with the platform 800. The user interface circuitry 850 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 800. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like. In some embodiments, the sensor circuitry 821 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like). In another example, NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.
[00149] Although not shown, the components of platform 800 may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.
[00150] Figure 9 illustrates example components of baseband circuitry 910 and radio front end modules (RFEM) 915 in accordance with various embodiments. The baseband circuitry 910 corresponds to the baseband circuitry 810 of Figure 8, respectively. The RFEM 915 corresponds to the RFEM 815 of Figure 8, respectively. As shown, the RFEMs 915 may include Radio Frequency (RF) circuitry 906, front-end module (FEM) circuitry 908, antenna array 911 coupled together at least as shown.
[00151] The baseband circuitry 910 includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that
enable communication with one or more radio networks via the RF circuitry 906. The radio control functions may include, but are not limited to, signal
modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 910 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 910 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments. The baseband circuitry 910 is configured to process baseband signals received from a receive signal path of the RF circuitry 906 and to generate baseband signals for a transmit signal path of the RF circuitry 906. The baseband circuitry 910 is configured to interface with application circuitry 805 (see Figure 8) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 906. The baseband circuitry 910 may handle various radio control functions.
[00152] The aforementioned circuitry and/or control logic of the baseband circuitry 910 may include one or more single or multi-core processors. For example, the one or more processors may include a 3G baseband processor 904A, a 4G/LTE baseband processor 904B, a 5G/NR baseband processor 904C, or some other baseband processor(s) 904D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functionality of baseband processors 904A-D may be included in modules stored in the memory 904G and executed via a Central Processing Unit (CPU) 904E. In other embodiments, some or all of the functionality of baseband processors 904A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells. In various embodiments, the memory 904G may store program code of a real-time OS (RTOS), which when executed by the CPU 904E (or other baseband processor), is to cause the CPU 904E (or other baseband processor) to manage resources of the baseband circuitry 910, schedule tasks, etc. Examples of the RTOS may include Operating System Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, Versatile Real- Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuitry 910 includes one or more audio digital signal processor(s) (DSP) 904F. The audio DSP(s) 904F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
[00153] In some embodiments, each of the processors 904A-904E include respective memory interfaces to send/receive data to/from the memory 904G. The baseband circuitry 910 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry 910; an application circuitry interface to send/receive data to/if om the application circuitry 805 of FIG. 9); an RF circuitry interface to send/receive data to/from RF circuitry 906 of Figure 9; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/ Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC 825.
[00154] In alternate embodiments (which may be combined with the above described embodiments), baseband circuitry 910 comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog- to-digital and digital-to- analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry 910 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules 915).
[00155] Although not shown by Figure 9, in some embodiments, the baseband circuitry 910 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a“multi-protocol baseband processor” or“protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols. In a first example, the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry 910 and/or RF circuitry 906 are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In the first example, the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 910 and/or RF circuitry 906 are part of a Wi-Fi communication system. In the second example, the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 904G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data. The baseband circuitry 910 may also support radio communications for more than one wireless protocol.
[00156] The various hardware elements of the baseband circuitry 910 discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi chip module containing two or more ICs. In one example, the components of the baseband circuitry 910 may be suitably combined in a single chip or chipset, or disposed on a same circuit board. In another example, some or all of the constituent components of the baseband circuitry 910 and RF circuitry 906 may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP). In another example, some or all of the constituent components of the baseband circuitry 910 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 906 (or multiple instances of RF circuitry 906). In yet another example, some or all of the constituent components of the baseband circuitry 910 and the application circuitry 805 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).
[00157] In some embodiments, the baseband circuitry 910 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 910 may support communication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodiments in which the baseband circuitry 910 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
[00158] RF circuitry 906 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 906 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 906 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 908 and provide baseband signals to the baseband circuitry 910. RF circuitry 906 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 910 and provide RF output signals to the FEM circuitry 908 for transmission.
[00159] In some embodiments, the receive signal path of the RF circuitry 906 may include mixer circuitry 906a, amplifier circuitry 906b and filter circuitry 906c. In some embodiments, the transmit signal path of the RF circuitry 906 may include filter circuitry 906c and mixer circuitry 906a. RF circuitry 906 may also include synthesizer circuitry 906d for synthesizing a frequency for use by the mixer circuitry 906a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 906a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906d. The amplifier circuitry 906b may be configured to amplify the down-converted signals and the filter circuitry 906c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 910 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 906a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
[00160] In some embodiments, the mixer circuitry 906a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 906d to generate RF output signals for the FEM circuitry 908. The baseband signals may be provided by the baseband circuitry 910 and may be filtered by filter circuitry 906c.
[00161] In some embodiments, the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may be configured for super-heterodyne operation.
[00162] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate
embodiments, the RF circuitry 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 910 may include a digital baseband interface to communicate with the RF circuitry 906.
[00163] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the
embodiments is not limited in this respect.
[00164] In some embodiments, the synthesizer circuitry 906d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 906d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
[00165] The synthesizer circuitry 906d may be configured to synthesize an output frequency for use by the mixer circuitry 906a of the RF circuitry 906 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 906d may be a fractional N/N+l synthesizer.
[00166] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 910 or the application circuitry 805 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 805.
[00167] Synthesizer circuitry 906d of the RF circuitry 906 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[00168] In some embodiments, synthesizer circuitry 906d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 906 may include an IQ/polar converter.
[00169] FEM circuitry 908 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 911, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 906 for further processing. FEM circuitry 908 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 906 for transmission by one or more of antenna elements of antenna array 911. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 906, solely in the FEM circuitry 908, or in both the RF circuitry 906 and the FEM circuitry 908.
[00170] In some embodiments, the FEM circuitry 908 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 908 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 908 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 906). The transmit signal path of the FEM circuitry 908 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 906), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 911.
[00171] The antenna array 911 comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals provided by the baseband circuitry 910 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array 911 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, direction, or a combination thereof. The antenna elements may be formed in a multitude of arranges as are known and/or discussed herein. The antenna array 911 may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards. The antenna array 911 may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 906 and/or FEM circuitry 908 using metal transmission lines or the like.
[00172] Processors of the application circuitry 805 and processors of the baseband circuitry 910 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 910, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 805 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers). As referred to herein, Layer 3 may comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below. As referred to herein, Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.
[00173] Figure 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer- readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 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. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.
[00174] The processors 1010 may include, for example, a processor 1012 and a processor 1014. The processor(s) 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 discussed herein), or any suitable combination thereof.
[00175] The memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1020 may include, but are not limited to, any type of volatile or nonvolatile memory such as 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.
[00176] The communication resources 1030 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008. For example, the communication resources 1030 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components,
Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components..
[00177] Instructions 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein. The instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor’s cache memory), the memory/storage devices 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 devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.
[00178] FIG. 11 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile
communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. The wireless device can also comprise a wireless modem. The wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). The wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.
[00179] FIG. 11 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. Anon- volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.
[00180] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
[00181] The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments. [00182] Example 1 includes an apparatus of a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR- U), the apparatus comprising: one or more processors configured to: identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body; map, at the UE, at one or more of n symbols in a time domain, one or more sequences
Figure imgf000054_0001
mapped on MRB ' physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the MRB CCH,X PRBs includes /Vi6 subcarriers and the
Figure imgf000054_0002
PRBs are distributed in the frequency
PUCCH X n p domain, and wherein n is a positive integer, MRB ' is a positive integer, and /Vi6 is a positive integer; and encode, at the UE, information on the
Figure imgf000054_0003
PRBs for transmission on the PUCCH; and a memory interface configured to retrieve the information from a memory.
[00183] Example 2 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the
Figure imgf000054_0004
PRBs in the frequency
PUCCH x
domain, by applying MRB ' cyclic shifts on the one or more sequences, wherein each PRB of the MRB CCH,X PRBS has a selected cyclic shift.
[00184] Example 3 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the MR PBUCCH' x PRBs by applying
MRB CCH,X phase offsets to each sequence mapped on the MRB CCH,X PRBs of the MRB CCH,X PRBs.
[00185] Example 4 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, one or more additional sequences on the
Figure imgf000054_0005
PRBs, wherein the one or more additional sequences are sequences with different sequence group numbers or different base sequences.
[00186] Example 5 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at the one or more of the n symbols in the time domain, a long sequence mapped on the
Figure imgf000054_0006
PRBs, wherein the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
[00187] Example 6 includes the apparatus of Example 5, wherein the length of the long sequence is equal to a length of allocated subcarriers.
[00188] Example 7 includes the apparatus of Example 1, wherein the one or more processors are further configured to: map, at the UE, at one or more of the n symbols in the time domain, a sequence mapped on the MRB ' PRBs based on a selected bandwidth and a selected subcarrier spacing (SCS).
[00189] Example 8 includes the apparatus of Example 7, wherein: the selected bandwidth is 10 megahertz (MHz), 20 MHz, or integer multiples of 20 MHz; or the SCS is 15 kilohertz (kHz), 30 kHz, or 60 kHz.
[00190] Example 9 includes the apparatus of any of Examples 1 to 5, wherein the M CH'X PRBS are distributed over one interlace.
[00191] Example 10 includes the apparatus of any of Examples 1 to 5, wherein the n symbols comprise: a 1 -symbol or 2-symbol NR PUCCH format 0.
[00192] Example 11 includes the apparatus of any of Examples 1 to 5, wherein the PUCCH is configured for an NR PUCCH format 0 or an NR PUCCH format 1, wherein the PUCCH is further configured to carry: a demodulation reference signal (DM-RS); or an uplink control channel information (UCI) including 1 bit or 2 bits.
[00193] Example 12 includes the apparatus of any of Examples 1 to 5, wherein: the minimum occupied bandwidth is an occupied channel bandwidth (OCB); or the regulatory body is the federal communications commission (FCC).
[00194] Example 13 includes an apparatus of a new radio node B (gNB) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), the apparatus comprising: one or more processors configured to: decode, at the gNB, information located in
Figure imgf000055_0001
physical resource blocks (PRBs) received on a PUCCH, wherein
Figure imgf000055_0002
is a positive integer; and identify, at the gNB, a minimum occupied bandwidth of the PUCCH based on a regulation of a regulatory body, wherein on one or more of the n symbols in a time domain, the
Figure imgf000055_0003
PRBs each include one or more sequences, wherein the
Figure imgf000055_0004
PRBs are determined at the user equipment (UE) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M CH’X PRBS includes iV™ subcarriers and the MRB CCH,X PRBS are distributed in the frequency domain, and wherein n is a positive integer NBc is a positive integer; and a memory interface configured to send the information to a memory.
[00195] Example 14 includes the apparatus of Example 13, wherein the MRB CCH,X sequences on the MRB CCH,X PRBS are mapped at the UE by applying MRB CCH'X cyclic shifts on each of the MRB CCH,X sequences, wherein each PRB of the MRB CCH'X PRBs has a selected cyclic shift.
[00196] Example 15 includes the apparatus of Example 13, wherein the MRB CCH,X sequences on the MRB CCH,X PRBs are mapped at the UE by applying MRB CCH'X phase
PU CC H x
offsets on each of the sequences mapped to each PRB of the MRB ’ PRBs.
[00197] Example 16 includes the apparatus of Example 13, wherein at one or more of the n symbols in the time domain, one or more additional sequences mapped on the
Figure imgf000056_0001
PRBs at the UE, wherein the one or more additional sequences are sequences with different sequence numbers.
[00198] Example 17 includes the apparatus of Example 13, wherein a long sequence
PUCCH x
on the MRB ' PRBs is mapped at the UE, wherein the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
[00199] Example 18 includes the apparatus of any of Examples 13 to 17, wherein the PUCCH is configured for an NR PUCCH format 0 or an NR PUCCH format 1.
[00200] Example 19 includes the apparatus of any of Examples 13 to 17, wherein: the minimum occupied bandwidth is an occupied channel bandwidth (OCB); or the regulatory body is the federal communications commission (FCC).
[00201] Example 20 includes at least one machine readable storage medium having instructions embodied thereon for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), the instructions when executed by one or more processors at a user equipment (UE) perform the following: identifying, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body; mapping, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on
Figure imgf000056_0002
physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the M CH’X PRBS includes NPc subcarriers and the MRB CCH'X PRBS are distributed in the frequency domain, and wherein n is a positive integer,
Figure imgf000057_0001
is a positive integer, and Nsc is a positive integer; and encoding, at the UE, information on the MRB CCH,X PRBs for transmission on the PUCCH.
[00202] Example 21 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the M CH'X PRBS in the frequency domain, by applying MRB CCH,X cyclic shifts on the one or more sequences, wherein each PRB of the MRB CCH,X PRBs has a selected cyclic shift.
[00203] Example 22 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the M CH'X PRBS by applying MRB CCH,X phase offsets to each sequence mapped on the M CCH'X PRBS of the MR P B UCCH’X PRBs.
[00204] Example 23 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, one or more additional
Figure imgf000057_0002
sequences on the MRB ' PRBs, wherein the one or more additional sequences are sequences with different sequence group numbers or different base sequences.
[00205] Example 24 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at the one or more of the n symbols in the time domain, a long sequence mapped on the
Figure imgf000057_0003
PRBs, wherein the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
[00206] Example 25 includes the at least one machine readable storage medium of Example 20, further comprising instructions that when executed perform: mapping, at the UE, at one or more of the n symbols in the time domain, a sequence mapped on the PUCCH x
MRB ' PRBs based on a selected bandwidth and a selected subcarrier spacing (SCS).
[00207] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). In one example, selected components of the transceiver module can be located in a cloud radio access network (C-RAN). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
[00208] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. [00209] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
[00210] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
[00211] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.
[00212] Reference throughout this specification to "an example" or“exemplary” means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word“exemplary” in various places throughout this specification are not necessarily all referring to the same embodiment.
[00213] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.
[00214] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.
[00215] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

CLAIMS What is claimed is:
1. An apparatus of a user equipment (UE) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), the apparatus comprising:
one or more processors configured to:
identify, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body;
map, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on
Figure imgf000061_0001
physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the MRB CCH,X PRBs includes N c subcarriers and the
Figure imgf000061_0002
PRBs are distributed in the frequency domain, and wherein n is a positive integer,
Figure imgf000061_0003
is a positive integer, and Nsc is a positive integer; and
encode, at the UE, information on the MRB CCH,X PRBs for transmission on the PUCCH; and
a memory interface configured to retrieve the information from a memory.
2. The apparatus of claim 1, wherein the one or more processors are further
configured to:
map, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the MR PBUCCH ' x PRBs in the frequency domain, by applying MR PB U CC H ' x cyclic shifts on the one or more sequences, wherein each PRB of the MRB CCH,X PRBS has a selected cyclic shift.
3. The apparatus of claim 1, wherein the one or more processors are further
configured to:
map, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the MRB CCH,X PRBs by applying MRB CCH,X phase offsets to each sequence mapped on the MRB CCH,X PRBs of the MRB CCH,X PRBs.
4. The apparatus of claim 1, wherein the one or more processors are further configured to:
map, at the UE, at the one or more of the n symbols in the time domain, one or more additional sequences on the
Figure imgf000062_0001
PRBs, wherein the one or more additional sequences are sequences with different sequence group numbers or different base sequences.
5. The apparatus of claim 1, wherein the one or more processors are further
configured to:
map, at the UE, at the one or more of the n symbols in the time domain, a long sequence mapped on the
Figure imgf000062_0002
PRBs, wherein the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
6. The apparatus of claim 5, wherein the length of the long sequence is equal to a length of allocated subcarriers.
7. The apparatus of claim 1, wherein the one or more processors are further
configured to:
map, at the UE, at one or more of the n symbols in the time domain, a sequence mapped on the MR PB CC H ' x PRBs based on a selected bandwidth and a selected subcarrier spacing (SCS).
8. The apparatus of claim 7, wherein:
the selected bandwidth is 10 megahertz (MHz), 20 MHz, or integer multiples of 20 MHz; or
the SCS is 15 kilohertz (kHz), 30 kHz, or 60 kHz.
PUCCH x
9. The apparatus of any of claims 1 to 5, wherein the MRB ' PRBs are distributed over one interlace.
10. The apparatus of any of claims 1 to 5, wherein the n symbols comprise: a 1-symbol or 2-symbol NR PUCCH format 0.
11. The apparatus of any of claims 1 to 5, wherein the PUCCH is configured for an NR PUCCH format 0 or an NR PUCCH format 1 , wherein the PUCCH is further configured to carry:
a demodulation reference signal (DM-RS); or
an uplink control channel information (UCI) including 1 bit or 2 bits.
12. The apparatus of any of claims 1 to 5, wherein:
the minimum occupied bandwidth is an occupied channel bandwidth (OCB); or
the regulatory body is the federal communications commission (FCC).
13. An apparatus of a new radio node B (gNB) operable for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), the apparatus comprising:
one or more processors configured to:
decode, at the gNB, information located in MR PBUCCH ' x physical resource blocks (PRBs) received on a PUCCH, wherein MRB CCH,X is a positive integer; and
identify, at the gNB, a minimum occupied bandwidth of the PUCCH based on a regulation of a regulatory body,
wherein on one or more of the n symbols in a time domain, the
Figure imgf000063_0001
PRBs each include one or more sequences, wherein the
Figure imgf000063_0002
PRBs are determined at the user equipment (UE) based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the MRB CCH,X PRBS includes NBc subcarriers and the MRB CCH,X PRBs are distributed in the frequency domain, and wherein n is a positive integer Nsc is a positive integer; and
a memory interface configured to send the information to a memory.
14. The apparatus of claim 13, wherein the MRB CCH,X sequences on the MRB CCH,X PRBs are mapped at the UE by applying MRB ' cyclic shifts on each of the M CH'X sequences, wherein each PRB of the MRB CCH,X PRBs has a selected cyclic shift.
15. The apparatus of claim 13, wherein the MRB CCH,X sequences on the MRB CCH,X
PUCCH x
PRBs are mapped at the UE by applying MRB ' phase offsets on each of the sequences mapped to each PRB of the MRB CCH,X PRBs.
16. The apparatus of claim 13, wherein at one or more of the n symbols in the time domain, one or more additional sequences mapped on the MR PB CCH ' x PRBs at the UE, wherein the one or more additional sequences are sequences with different sequence numbers.
Figure imgf000064_0001
17. The apparatus of claim 13, wherein a long sequence on the MRB ' PRBs is mapped at the UE, wherein the long sequence is one or more of a low peak-to- average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence.
18. The apparatus of any of claims 13 to 17, wherein the PUCCH is configured for an NR PUCCH format 0 or an NR PUCCH format 1.
19. The apparatus of any of claims 13 to 17, wherein:
the minimum occupied bandwidth is an occupied channel bandwidth (OCB); or
the regulatory body is the federal communications commission (FCC).
20. At least one machine readable storage medium having instructions embodied thereon for new radio (NR) physical uplink control channel (PUCCH) operation in NR-unlicensed (NR-U), the instructions when executed by one or more processors at a user equipment (UE) perform the following: identifying, at the UE, a minimum occupied bandwidth of a PUCCH based on a regulation of a regulatory body;
mapping, at the UE, at one or more of n symbols in a time domain, one or more sequences mapped on
Figure imgf000065_0001
physical resource blocks (PRBs) in a frequency domain, based on the minimum occupied bandwidth of the PUCCH, wherein each PRB of the MRB CCH,X PRBs includes NBc subcarriers and the
Figure imgf000065_0002
PRBs are distributed in the frequency domain, and wherein n is a positive integer, MR PBUCCH ' x is a positive integer, and /Vi6 is a positive integer; and encoding, at the UE, information on the MR PBUCCH ' x PRBs for transmission on the PUCCH.
21. The at least one machine readable storage medium of claim 20, further comprising instructions that when executed perform:
mapping, at the UE, at the one or more of the n symbols in the time
PUCCH x
domain, the one or more sequences on the MRB ' PRBs in the frequency domain, by applying
Figure imgf000065_0003
cyclic shifts on the one or more sequences, wherein each PRB of the MRB CCH,X PRBs has a selected cyclic shift..
22. The at least one machine readable storage medium of claim 20, further comprising instructions that when executed perform:
mapping, at the UE, at the one or more of the n symbols in the time domain, the one or more sequences on the MRB CCH,X PRBs by applying MRB CCH,X phase offsets to each sequence mapped on the MRB CCH,X PRBs of the MRB CCH,X PRBs.
23. The at least one machine readable storage medium of claim 20, further comprising instructions that when executed perform:
mapping, at the UE, at the one or more of the n symbols in the time
PUCCH x
domain, one or more additional sequences on the MRB ' PRBs, wherein the one or more additional sequences are sequences with different sequence group numbers or different base sequences..
24. The at least one machine readable storage medium of claim 20, further comprising instructions that when executed perform:
mapping, at the UE, at the one or more of the n symbols in the time
Figure imgf000066_0001
domain, a long sequence mapped on the MRB ' PRBs, wherein the long sequence is one or more of a low peak-to-average power ratio (PAPR) sequence, a computer generated sequence (CGS), or a Zadoff-Chu (ZC) sequence..
25. The at least one machine readable storage medium of claim 20, further comprising instructions that when executed perform:
mapping, at the UE, at one or more of the n symbols in the time domain, a sequence mapped on the
Figure imgf000066_0002
PRBs based on a selected bandwidth and a selected subcarrier spacing (SCS).
PCT/US2019/044995 2018-08-02 2019-08-02 New radio (nr) physical uplink control channel (pucch) formats for nr-unlicensed WO2020028868A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP24162441.0A EP4358452A2 (en) 2018-08-02 2019-08-02 New radio (nr) physical uplink control channel (pucch) formats for nr-unlicensed
EP19843075.3A EP3831008A4 (en) 2018-08-02 2019-08-02 New radio (nr) physical uplink control channel (pucch) formats for nr-unlicensed
CN201980043271.6A CN112470420B (en) 2018-08-02 2019-08-02 Apparatus and medium for unlicensed New Radio (NR) Physical Uplink Control Channel (PUCCH)
CN202410141064.7A CN117955588A (en) 2018-08-02 2019-08-02 Apparatus, method and medium for NR PUCCH for unlicensed NR

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862713985P 2018-08-02 2018-08-02
US62/713,985 2018-08-02

Publications (1)

Publication Number Publication Date
WO2020028868A1 true WO2020028868A1 (en) 2020-02-06

Family

ID=69230746

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/044995 WO2020028868A1 (en) 2018-08-02 2019-08-02 New radio (nr) physical uplink control channel (pucch) formats for nr-unlicensed

Country Status (3)

Country Link
EP (2) EP3831008A4 (en)
CN (2) CN112470420B (en)
WO (1) WO2020028868A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210029731A1 (en) * 2019-10-15 2021-01-28 Intel Corporation Resource allocation for physical uplink control channel during initial access in new radio unlicensed
CN114726478A (en) * 2021-01-05 2022-07-08 大唐移动通信设备有限公司 Method, apparatus and storage medium for transmitting uplink control information
WO2022159978A1 (en) * 2021-01-25 2022-07-28 Qualcomm Incorporated Physical uplink control channel configuration for millimeter wave bands
WO2022177672A1 (en) * 2021-02-19 2022-08-25 Qualcomm Incorporated Resource selection for communicating uplink control information

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170164352A1 (en) * 2015-12-07 2017-06-08 Telefonaktiebolaget Lm Ericsson (Publ) Uplink control channel configuration for unlicensed carriers

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017044066A1 (en) * 2015-09-11 2017-03-16 Intel IP Corporation Transmission of uplink control information in wireless systems

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170164352A1 (en) * 2015-12-07 2017-06-08 Telefonaktiebolaget Lm Ericsson (Publ) Uplink control channel configuration for unlicensed carriers

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"On UL Signals and Channels in NR-Unlicensed", RI-1807035, 3GPP TSG RAN WG1 MEETING #93, 12 May 2018 (2018-05-12), Busan, Korea, XP051462861 *
"Potential enhancements to NR UL signals and channels for unlicensed operation", RI-1806543, 3GPP TSG RAN WG1 MEETING #93, 12 May 2018 (2018-05-12), Busan, Korea, XP051462602 *
HUAWEI ET AL.: "UL PHY channels for NR unlicensed", 3GPP DRAFT; R1-1805921, 3RD GENERATION, 21 May 2018 (2018-05-21)
HUAWEI ET AL.: "UL PHY channels for NR unlicensed", RI-1805921, 3GPP TSG RAN WG1 MEETING #93, 11 May 2018 (2018-05-11), Busan, Korea, XP051461631 *
INTERDIGITAL INC: "On UL Signals and Channels in NR-Unlicensed", 3GPP DRAFT; R1-1807035, 21 May 2018 (2018-05-21)
SAMSUNG: "Uplink signal and channel design for NR-U", RI-1806760, 3GPP TSG RAN WG1 MEETING #93, 11 May 2018 (2018-05-11), Busan, Korea, XP051461960 *
See also references of EP3831008A4

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210029731A1 (en) * 2019-10-15 2021-01-28 Intel Corporation Resource allocation for physical uplink control channel during initial access in new radio unlicensed
US11743887B2 (en) * 2019-10-15 2023-08-29 Intel Corporation Resource allocation for physical uplink control channel during initial access in new radio unlicensed
CN114726478A (en) * 2021-01-05 2022-07-08 大唐移动通信设备有限公司 Method, apparatus and storage medium for transmitting uplink control information
CN114726478B (en) * 2021-01-05 2023-09-01 大唐移动通信设备有限公司 Method, device and storage medium for transmitting uplink control information
WO2022159978A1 (en) * 2021-01-25 2022-07-28 Qualcomm Incorporated Physical uplink control channel configuration for millimeter wave bands
WO2022177672A1 (en) * 2021-02-19 2022-08-25 Qualcomm Incorporated Resource selection for communicating uplink control information
US20220272690A1 (en) * 2021-02-19 2022-08-25 Qualcomm Incorporated Resource selection for communicating uplink control information
US11683805B2 (en) * 2021-02-19 2023-06-20 Qualcomm Incorporated Resource selection for communicating uplink control information

Also Published As

Publication number Publication date
EP3831008A4 (en) 2022-04-27
CN112470420B (en) 2024-03-01
CN117955588A (en) 2024-04-30
EP4358452A2 (en) 2024-04-24
EP3831008A1 (en) 2021-06-09
CN112470420A (en) 2021-03-09

Similar Documents

Publication Publication Date Title
US11985674B2 (en) Data and control transmission enhancements for new radio (NR)
US11564249B2 (en) Configured grant uplink (UL) transmission in new radio unlicensed (NR-U)
US20220201515A1 (en) Enhanced physical downlink control channel monitoring
US20200374735A1 (en) Signaling enhancements of smtc configuration for an iab mt
US11917663B2 (en) Physical downlink shared channel (PDSCH) repetition transmission for reliable communications
US11985629B2 (en) Sensing-based distributed scheduling of event-based mission critical (MC) vehicle-to-everything (V2X) traffic
US11832183B2 (en) Wake-up signal design
US11936583B2 (en) SSB pattern and DMRS design for PBCH in 5G NR
US20210392673A1 (en) Enhanced physical uplink control channel (pucch) transmission for high reliability
EP4358452A2 (en) New radio (nr) physical uplink control channel (pucch) formats for nr-unlicensed
WO2020068596A1 (en) Non-orthogonal multiple access (noma) transmission for low latency random access channel (rach)
WO2020056364A1 (en) Signaling configurations for cell selection in fifth generation (5g) new radio (nr) (5g-nr) integrated access and backhaul (iab)
US20240023125A1 (en) Control resource set configuration and physical downlink control channel design for above 52.6ghz
WO2020198430A1 (en) Dynamic indication of soft resource availability
WO2020092261A1 (en) Radio resource control (rrc) signaling for off-raster synchronization signal block (ssb) in an integrated access and backhaul (iab) network
WO2020102076A1 (en) Beam switching in intra-band non-contiguous carrier aggregation
US11064566B2 (en) Symbol puncture for unlicensed narrowband internet of things (NB IoT)
US11844132B2 (en) User plane early data transmission (EDT) message 4 (MSG4) loss
CN112713977A (en) Method for sounding reference signal transmission
US11985645B2 (en) Dynamic uplink Tx DC sub-carrier location reporting
US20230163939A1 (en) Cross-division duplex signaling

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19843075

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019843075

Country of ref document: EP

Effective date: 20210302