WO2018045247A1 - Conception de canal d'accès aléatoire physique (prach) pour porteuses sans licence en lte - Google Patents

Conception de canal d'accès aléatoire physique (prach) pour porteuses sans licence en lte Download PDF

Info

Publication number
WO2018045247A1
WO2018045247A1 PCT/US2017/049770 US2017049770W WO2018045247A1 WO 2018045247 A1 WO2018045247 A1 WO 2018045247A1 US 2017049770 W US2017049770 W US 2017049770W WO 2018045247 A1 WO2018045247 A1 WO 2018045247A1
Authority
WO
WIPO (PCT)
Prior art keywords
prach
transmission
rach
enodeb
uplink
Prior art date
Application number
PCT/US2017/049770
Other languages
English (en)
Inventor
Abhijeet Bhorkar
Huaning Niu
Qiaoyang Ye
Jeongho Jeon
Wenting CHANG
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
Publication of WO2018045247A1 publication Critical patent/WO2018045247A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • 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/0037—Inter-user or inter-terminal allocation
    • H04L5/0039—Frequency-contiguous, i.e. with no allocation of frequencies for one user or terminal between the frequencies allocated to another
    • 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
    • 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/0053—Allocation of signaling, i.e. of overhead other than pilot 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/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space

Definitions

  • Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device).
  • Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in uplink (UL).
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • OFDM orthogonal frequency-division multiplexing
  • 3 GPP third generation partnership project
  • LTE long term evolution
  • IEEE Institute of Electrical and Electronics Engineers 802.16 standard
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiFi Wireless Fidelity
  • the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • RNCs Radio Network Controllers
  • the downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.
  • UE user equipment
  • FIG. 1 illustrates a physical random access channel (PRACH) transmission in a special subframe in accordance with an example
  • FIG. 2 illustrates a random access channel (RACH) transmission that is blocked by an ongoing data transmission due to a timing advance (TA) in accordance with an example
  • FIG. 3 illustrates an uplink (UL) timing advance (TA) setting for a random access channel (RACH) transmission in a small cell in accordance with an example
  • FIG. 4 illustrates an uplink (UL) timing advance (TA) setting issue for a random access channel (RACH) transmission in accordance with an example
  • FIG. 5 illustrates a channel access technique and timing advance (TA) setting for a random access channel (RACH) transmission in accordance with an example
  • FIG. 6 illustrates a physical random access channel (PRACH) symbol structure in accordance with an example
  • FIG. 7 illustrates another physical random access channel (PRACH) symbol structure in accordance with an example
  • FIG. 8 illustrates yet another physical random access channel (PRACH) symbol structure in accordance with an example
  • FIG. 9 illustrates a further physical random access channel (PRACH) symbol structure in accordance with an example
  • FIG. 10 depicts functionality of an eNodeB operable to set an uplink timing advance (TA) value for random access channel (RACH) transmissions in a MuLTEfire system in accordance with an example;
  • TA uplink timing advance
  • FIG. 11 depicts functionality of an eNodeB operable to perform physical random access channel (PRACH) transmissions in accordance with an example
  • FIG. 12 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for performing physical random access channel (PRACH) transmissions in accordance with an example;
  • PRACH physical random access channel
  • FIG. 13 illustrates an architecture of a wireless network in accordance with an example
  • FIG. 14 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example
  • FIG. 15 illustrates interfaces of baseband circuitry in accordance with an example
  • FIG. 16 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.
  • UE wireless device
  • LAA licensed- assisted access
  • CA flexible carrier aggregation
  • LTE operation in the unlicensed spectrum can be achieved using dual connectivity (DC) based LAA.
  • DC based LAA an anchor deployed in the licensed spectrum can be utilized.
  • 3GPP Release 14 describes that LTE operation in the unlicensed system can be achieved using a MuLTEfire system, which does not utilize an anchor in the licensed spectrum.
  • the MuLTEfire system is a standalone LTE system that operates in the unlicensed spectrum, and does not necessitate assistance from the licensed spectrum and combines the performance benefits of LTE technology with the simplicity of WiFi-like deployments. Therefore, Release 14 eLAA and MuLTEfire systems can potentially be significant evolutions in future wireless networks.
  • the unlicensed frequency band of current interest for 3GPP systems is the 5 gigahertz (GHz) band, which has wide spectrum with global common availability.
  • the 5 GHz band in the United States is governed using Unlicensed National Information Infrastructure (U-NII) rules by the Federal Communications Commission
  • WLAN wireless local area networks
  • LBT listen-before-talk
  • the regulations for usage of the unlicensed spectrum can vary based on region.
  • ETSI European Telecommunications Standards Institute
  • OCB occupied channel bandwidth
  • a transmitter is to transmit a signal by occupying between 80% and 100% of the system bandwidth.
  • OCB occupied channel bandwidth
  • each transmission is to occupy at least 8 MHz.
  • the regulations on the maximum power spectral density are typically stated with a resolution bandwidth of 1 megahertz (MHz).
  • the ETSI specification defines a maximum power spectral density (PSD) of 10 decibel-milliwatts (dBm)/MHz for 5150-5350 MHz.
  • the FCC has a maximum PSD of 11 dBm/MHz for 5150-5350 MHz.
  • a 10 kilohertz (KHz) resolution can be utilized for testing the 1 MHz PSD constraint and, therefore, the maximum PSD constraint can be satisfied in an occupied lMHz bandwidth.
  • the regulations impose a band specific total maximum transmission power in terms of equivalent isotropically radiated power (EIRP), e.g., ESTI has an EIRP limit of 23 dBm for 5150 - 5350 MHz.
  • EIRP equivalent isotropically radiated power
  • FIG. 1 illustrates an exemplary physical random access channel (PRACH) transmission in a special subframe.
  • the PRACH can utilize a block interleaved frequency division multiple access (B-IFDMA) waveform, in part, to satisfy an occupied channel bandwidth (OCB) regulation (e.g., the OCB is to be between 80% and 100% system bandwidth).
  • B-IFDMA block interleaved frequency division multiple access
  • OCB occupied channel bandwidth
  • an UL portion of the special subframe can be used for the PRACH transmission.
  • an uplink pilot time slot (UpPTS) region or an extended UpPTS region occupying a last four OFDM symbols of the special subframe can be used for the PRACH transmission.
  • the PRACH can be transmitted over a regular UL subframe, which can be beneficial for large cells.
  • the special subframe can include a DL portion and an UL portion.
  • the first N symbols in the special subframe can be used for DL transmissions, wherein N is an integer.
  • the PRACH can be transmitted during the UL portion of the special subframe.
  • the PRACH can utilize 4 symbols, but a different number of symbols can be used for the PRACH as well.
  • the PRACH can be transmitted using an interlaced subframe structure, such as a B-IFDMA subframe structure, to satisfy the OCB regulation.
  • a total system bandwidth can be separated into multiple interlaces. For example, a 20 MHz system can be separated into 10 interlaces.
  • One interlace can include 10 resource blocks (RBs).
  • Interlace #0 can occupy RB 0, 10, 20 and so on.
  • Interlace #1 can occupy RB 1, 11, 21 and so on.
  • the total occupied bandwidth can be from 0 to 90 RBs, which is more than 80% of the total system bandwidth (which satisfies the OCB regulation). By interlacing, the bandwidth usage can be increased to at least 80%.
  • the 5 GHz band there are regional unlicensed bands or shared licensed bands, such as the 3.5GHz band in the United States, or the 1.9GHz band in Japan, which are of great interest to extend coverage and data rates. These bands can allow for an increased cell size without WiFi.
  • UL LAA design is being considered.
  • the UL LAA design can be inherently different from a legacy LTE design, as the UE has to perform LBT before transmission.
  • a random access channel is defined in MulteFire systems, such that a RACH transmission is periodically allocated in a location, which can be signaled through a system information block MulteFire (SIB-MF).
  • SIB-MF system information block MulteFire
  • the RACH can use a shortened physical uplink control channel (sPUCCH) format for a short cell size, and an enhanced physical uplink control channel (ePUCCH) format for a large cell size.
  • sPUCCH shortened physical uplink control channel
  • ePUCCH enhanced physical uplink control channel
  • the UE can perform one shot clear channel assessment (CCA) sensing. If successful, the UE can send a RACH preamble. Otherwise, the UE can wait until a next RACH transmission opportunity.
  • CCA clear channel assessment
  • a technique for setting a timing advance (TA), as well as a random access procedure for RACH transmissions in a MulteFire system.
  • TA timing advance
  • a TA can be set to a TA offset (TA_offset), and the random access procedure can follow the one shot CCA process defined in the 5 GHz band.
  • the TA can be set to the TA offset (TA_offset), while the random access procedure can perform an earlier sensing and a self-defer, where a defer value can be signaled through the SIB-MF.
  • the UE can perform listen before talk (LBT) before a transmission, and if the UE does not perform the self-defer in conjunction with LBT, the UE can potentially block other UEs from performing transmissions.
  • LBT listen before talk
  • RACH transmissions do not apply the TA.
  • a RACH sequence can typically have a longer cyclic prefix (CP), which can be longer than a round trip delay plus a channel delay spread.
  • CP cyclic prefix
  • the TA can be applied to following data and control information after a radio resource control (RRC) connection is established.
  • RRC radio resource control
  • MulteFire systems due to the listen before talk procedure, the TA that is applied to data transmission through a different frequency interlace can block a RACH transmission.
  • FIG. 2 illustrates an example of a random access channel (RACH) transmission that is blocked by an ongoing data transmission due to a timing advance (TA).
  • RACH random access channel
  • TA timing advance
  • a subframe can include a downlink radio frame, an uplink radio frame for a PUSCH or e/sPUCCH for a first UE (UE1) and an uplink radio frame for RACH for a second UE (UE2).
  • UE1 uplink radio frame for RACH for a second UE
  • UE2 RACH transmission can be blocked by the ongoing data transmission due to the TA.
  • NTA offset can be 0 in frame structure type 1
  • NTA offset can be 624 in frame structure type 2
  • NTA offset can be 0 in frame structure type 3.
  • an NTA offset can be applied to RACH transmissions.
  • the RACH can be configured using the sPUCCH transmission format, and the RTT can be smaller than 5 micro seconds (us) (cell size is less than 750 meters).
  • a CCA mechanism or procedure in the 5GHz band can necessitate a CCA sensing time of 4us out of a slot of 9us, while the last 5us can be used for medium access control (MAC) processing, receive (Rx) to transmit (Tx) switching, etc.
  • MAC medium access control
  • Rx receive
  • Tx transmit
  • a subframe can include a downlink (DL) radio frame, an UL radio frame for a PUSCH or e/sPUCCH and an UL radio frame for a RACH transmission.
  • DL downlink
  • UL uplink
  • RACH random access channel
  • a RACH transmission can block a PUSCH/PUCCH transmission, or a PUSCH/PUCCH transmission can block the RACH transmission.
  • the NTA offset T s is applied to the RACH transmission, the RACH transmission can be blocked by the other UE's UL transmission.
  • the RACH transmission can be blocked by the other UE's UL transmission, wherein max(NTA) indicates a maximum individual TA value per UE.
  • FIG. 4 illustrates an example of an uplink (UL) timing advance (TA) setting issue for a random access channel (RACH) transmission.
  • a subframe can include a downlink (DL) radio frame, an uplink (UL) radio frame for a first user equipment (UE) (UEl) with a max(NTA), an UL radio frame for the UEl with NTAO, and an UL radio frame for RACH.
  • UE user equipment
  • NAO user equipment
  • RACH transmission can block a PUSCH/PUCCH transmission, or a
  • PUSCH/PUCCH transmission can block a RACH transmission. More specifically, as shown, when the NTA offset T s is applied to the RACH transmission, the RACH
  • the transmission can be blocked by the other UE's UL transmission.
  • the RACH transmission can be blocked by the other UE's UL transmission.
  • a UE CCA sensing period in order to resolve the above issue regarding the UL TA setting for the RACH transmission, a UE CCA sensing period can be moved by
  • the UE can self-defer to a common TA setting of NTA offset T s or max(NTA), and start the RACH transmission.
  • a RACH CCA time can end by (NTA offset + max(NTA)) T s .
  • the UE self- defer for the RACH transmission may not be applicable to the 5GHz band due to regulation.
  • the RACH transmission can apply the TA offset NTA offset Ts, and a self-defer value for the UE can be signaled in the SIB-MF.
  • FIG. 5 illustrates an example of a channel access technique and timing advance (TA) setting for a random access channel (RACH) transmission.
  • a subframe can include a downlink (DL) radio frame, an uplink (UL) radio frame for a first user equipment (UE) (UE1) with a max(NTA), an UL radio frame for the UE1 with NTAO, and an UL radio frame for RACH.
  • the UL radio frame for RACH can be preceded by CCA and a self- defer period.
  • a UE CCA sensing period can be moved by max(NTA).
  • the UE senses that a channel is clear, the UE can self-defer to a common TA setting of NTA offset Ts and start the RACH transmission.
  • a RACH CCA time can end by (NTA offset + max(NTA)) T s .
  • a technique for channel access and setting a TA value for a RACH transmission in MulteFire systems is described.
  • the TA when the RACH transmission is performed using the sPUCCH format, the TA can be set using NTA offset Ts for the RACH transmission.
  • a 4 micro second (us) CCA sensing can be performed at a beginning of a CCA slot.
  • the TA when the RACH transmission is performed using ePUCCH resources, the TA can be set using NTA offset T s for the RACH transmission.
  • the CCA for the RACH transmission can be performed max(NTA) T s earlier.
  • the UE can self-defer the RACH transmission by max(NTA) T s , and the max(NTA) can be signaled in the SIB-MF.
  • MulteFire systems can consider the 3.5 GHz unlicensed spectrum as a potential unlicensed deployment.
  • 3GPP may also consider the operation of new radio (NR) or (e)LAA systems on a 3.5 GHz Citizens Broadband Radio Service (CBRS) spectrum.
  • NR new radio
  • e LAA
  • CBRS Citizens Broadband Radio Service
  • the 3.5 GHz band was previously locked up by the United States Department of Defense (DoD), but was recently allowed to be used for commercial purposes.
  • the Federal Communications Commission (FCC) has adopted a three-tiered access model for the 3.5 GHz CBRS band as follows: (1) incumbent (federal user, fixed satellite service), (2) priority access licensees (PALs), which can involve 100 MHz and an auction for short-term licensing, and (3) general authorized access (GAA), which can involve 150 MHz open for anyone with an FCC-certified device.
  • incumbent federal user, fixed satellite service
  • PALs priority access licensees
  • GAA general authorized access
  • a channel access by higher priority is protected from lower priorities.
  • a channel access by PAL can be protected from GAA, whereas PAL should not hinder a channel access by an Incumbent.
  • no particular coexistence rule, such as LBT is mandated by the FCC among GAAs.
  • the FCC has defined a spectrum access system (SAS) that authorizes and manages the use of the CBRS (PAL, GAA) spectrum.
  • SAS is responsible for maintaining the prioritized channel access.
  • the SAS can optimize frequency use to facilitate coexistence.
  • the SAS can have limited coexistence provisioning between GAAs by means of spectrum coordination.
  • a novel PRACH design can be defined for the 3.5 GHz band.
  • the PRACH can be used for scheduling requests (SR), uplink (UL) synchronization and power control for an initial UL transmission.
  • SR scheduling requests
  • UL uplink
  • an sPUCCH waveform can be used for the PRACH, which has an interlaced structure with 4 symbols (as shown in FIG. 1).
  • the sPUCCH waveform can have 4 symbols in 20MHz systems, and there can be 10 interlaces with 10 PRBs per interlace in MulteFire systems with 20MHz bandwidth.
  • the PRACH is to be used for timing advance.
  • the PRACH with the interlaced structure cannot provide a favorable timing estimation performance.
  • the novel PRACH design can involve a PRACH preamble transmitted over continuous PRBs, which can have various benefits.
  • the PRACH over the continuous PRB can have better timing estimation accuracy as compared to the interlaced structure.
  • there is no regulation on a minimal channel bandwidth and PSD limitation and thus there is no penalty to transmit the PRACH over continuous PRBs.
  • the resource granularity for the PRACH transmission can be smaller, and thus the overhead for the PRACH transmission can be reduced.
  • a number of PRBs less than 10 can be used for the PRACH transmission (as the interlaced structure has 10 PRBs per interlace).
  • an impact on other channels with the interlaced structure can be limited.
  • the novel PRACH design with continuous PRBs for operation on the 3.5 GHz spectrum can reduce the PRACH overhead and improve the timing estimation accuracy, as compared to the interlaced structure.
  • the PRACH transmission can occupy continuous N PRBs, where N can be 5 or 6 PRBs.
  • N can be 5 or 6 PRBs.
  • a PRACH preamble from the legacy LTE system can be extended. Similar to the PRACH design in the legacy LTE system, a subcarrier spacing can be reduced. For example, a PRACH format similar to PRACH preamble format 0 in the legacy LTE system can be transmitted over a regular UL subframe.
  • the subcarrier spacing of PRACH preamble format 0 is 1.25 kHz, and a CP duration is 103.13 ⁇ , which can be applied to cells with a radius of about 14km (e.g.,, with a maximal delay spread of 6.25 ⁇ ).
  • a cell size to be supported on the 3.5 GHz band can be smaller than a cell size to be supported with a CP of 103.13 us (i.e., the cell radius may be smaller than 14km).
  • a shorter CP can be adopted, and a remaining time (103.13us minus the reduced CP duration) can be used for LBT
  • the PRACH format 4 in legacy LTE systems can be used as a baseline.
  • a subcarrier spacing of the PRACH can be 7.5 kHz, and the CP duration is 14.6 ⁇ , which can be applied to cells with a radius of at least 1km.
  • the PRACH preamble symbol in this option can be repeated over the time domain when transmitted over a regular UL subframe.
  • a guard band can be utilized for the PRACH transmission when frequency multiplexed with other transmissions (e.g., a PUSCH transmission from another UE using the 15 kHz subcarrier spacing). Similar to the LTE PRACH design, a guard band at two ends of a "large resource chunk" consisting of N continuous PRBs can be applied. The number of subcarriers to leave blank as a guard band can depend on the cell size, as well as operation preferences on a tradeoff of performance loss due to overhead caused by the guard band. In another example, 15 kHz at one end and 22.5 kHz at another end can be left blank.
  • the PRACH waveform can have the same subcarrier spacing as the PUSCH (i.e., 15 kHz). Within every 2 symbols, a preceding symbol within these 2 symbols can be performed as a 'long CP' for the following symbol.
  • FIG. 6 illustrates an example of a physical random access channel (PRACH) symbol structure.
  • the PRACH symbol structure can include symbol k and symbol (k+1).
  • the symbol k can be used as a CP. For instance, by truncating with a length of an OFDM symbol without prefix, the obtained part is a cyclic shifted version of the OFDM symbol without prefix.
  • the OFDM symbol without prefix in symbol k+1 is a cyclic shifted version of OFDM symbol without prefix in symbol k.
  • every other symbol is also overhead.
  • the symbol (k+1) can be a cyclic shifted version of symbol k in the time domain.
  • an eNodeB can obtain one Fast Fourier Transform (FFT) duration within every 2 FFT durations for detection.
  • FFT Fast Fourier Transform
  • FIG. 7 illustrates an example of a physical random access channel (PRACH) symbol structure.
  • PRACH physical random access channel
  • the first symbol duration can be used as a CP, and thus can help overcome the inter-interlace interference.
  • the CP duration in the first symbol can be the same as the CP duration in the PUSCH, or can be twice of the CP duration in the PUSCH to align a symbol boundary of every two symbols.
  • the symbol boundary may not be aligned with other channels (e.g., PUSCH).
  • the additional time can be left blank (i.e., no transmission) and used as a guard period.
  • the CP duration in symbol k can be set to be twice of the CP duration in legacy LTE systems.
  • the symbol boundary of every 2 symbols can be aligned with other channels (e.g., PUSCH).
  • the total duration of 2n with ne ⁇ 1, 2, ... ,7 ⁇ symbols in this option is the same as the total duration of 2n symbols in legacy LTE systems.
  • FIG. 8 illustrates an example of a physical random access channel (PRACH) symbol structure. Similar to PRACH formats 2 and 3 in legacy LTE systems where the PRACH symbols are repeated, the PRACH in eLAA and MuLTEfire systems can also be repeated multiple times to enhance coverage. As shown, the PRACH transmission can include a CP and several repeated PRACH preamble symbols.
  • the repeated PRACH preamble symbols (e.g., 3 symbols) can follow a CP duration, which can depend on a maximal delay spread, a maximal round trip delay and a cell size, or the repeated PRACH preamble symbols can have no CP. A number of preamble repetitions can depend on a specified coverage area.
  • the CP duration can be predefined in the 3GPP LTE
  • the PRACH preamble can include no CP, but only several repeated PRACH preamble symbols, and a preceding symbol can perform as a CP for a following symbol.
  • a first format can be supported having a subcarrier spacing of 7.5 kHz, which can be transmitted over a special subframe (e.g. an uplink pilot time slot (UpPTS) region).
  • the first format can be transmitted without frequency multiplexing of other channels with different subcarrier spacing, which can reduce ICI and limit a number of needed guard subcarriers.
  • a second format can be supported having a subcarrier spacing of 1.25 kHz, which can be transmitted over a regular UL subframe.
  • FIG. 9 illustrates an example of a physical random access channel (PRACH) symbol structure. Similar to PRACH formats 2 and 3 in legacy LTE systems where the PRACH symbols are repeated, the PRACH in eLAA and MuLTEfire systems can also be repeated multiple times to enhance coverage. As shown, the PRACH transmission can include several repeated PRACH preamble symbols, but no CP. The repeated PRACH preamble symbols (e.g., 3 symbols) can depend on a maximal delay spread, a maximal round trip delay and a cell size.
  • PRACH physical random access channel
  • a sequence designed in legacy LTE systems can be reused, which can involve repeating or truncating the sequence to fit into a number of REs that are allocated for the PRACH transmission.
  • the PRACH can be transmitted over continuous 5 PRBs, and a legacy LTE PRACH sequence which is designed to map to 6 PRBs can be truncated to fit into 5 PRBs.
  • the PRACH can be transmitted over 6 continuous PRBs, and the legacy LTE PRACH sequence can be reused directly.
  • a new sequence can be designed with a desirable length.
  • a new set of Zadoff-Chu (ZC) sequences with a desirable length can be designed.
  • ZC Zadoff-Chu
  • the PRACH sequence can be one belonging to the set of ZC sequences with length of 683 for 1.25kHz SC spacing and with a length of 113 for 7.5kHz SC spacing.
  • UE multiplexing among the PRACH on same resources can be based on cyclic shifts (CS), orthogonal cover codes (OCC) and/or different base sequences.
  • CS cyclic shifts
  • OCC orthogonal cover codes
  • a CS value should be at least larger than a maximal delay spread plus a maximal round-trip delay.
  • OCC an OCC length can be the same as the number of PRACH preamble symbols with CP, e.g., an OCC with length of N can be applied for PRACH format 4 when the format 4 preamble is repeated N times.
  • an OCC with length of N/2 can be applied instead of N.
  • the OCC for the symbol k and k+1 with ke ⁇ 0, 2, 4, 6, 8, 10, 12 ⁇ can be the same.
  • FDM frequency division multiplexing
  • TDM time division multiplexing
  • the PRACH and other UL channels, e.g., PUSCH and PUCCH, which use interlaced structure can be multiplexed via FDM and/or TDM.
  • the UL transmissions with the interlaced structure can be rate matched around the RBs allocated for the PRACH transmission. Specifically, when there are 5 PRBs allocated for the PRACH transmission in a subframe, the UL transmissions with the interlaced structure can be mapped to 9 RBs per interlace in the subframe, with 1 RB in each interlaced left empty for the PRACH transmission. In another example, when there are 6 PRBs allocated for the PRACH transmission in a subframe, there can be 4 interlaces with 9 PRBs per interlace and 1 interlace with 8 PRBs per interlace available for the UL transmission with the interlaced structure. Alternatively, the RBs allocated for the PRACH transmission can be punctured.
  • the UL transmissions with the interlaced structure can be mapped to 10 PRBs per interlace. Then the RBs allocated for PRACH transmissions can be used to carry a PRACH preamble, with symbols for other UL transmissions being punctured on these PRBs.
  • the PRACH can be transmitted over a remaining part following a downlink pilot time slot (DwPTS) of a special subframe or a regular UL subframe, which is similar to MulteFire 1.0 systems.
  • DwPTS downlink pilot time slot
  • various techniques can be considered.
  • a PDCCH order can be used to indicate the PRACH preamble sequence, and a time resource to transmit PRACH, which can be explicit or implicit.
  • a fixed timing relationship between a reception of the PDCCH order and the transmission of the PRACH can be predefined (e.g., 4 or 6 subframes between the PDCCH order and the PRACH transmission).
  • the timing resource can be semi-statically configured via RRC signaling for contention-free and/or contention-based PRACH.
  • the periodicity and offset can be indicated by the RRC signaling.
  • frequency resources for the PRACH transmission can be semi-statically configured via RRC signaling, or can be dynamically indicated via the PDCCH order for contention-free PRACH.
  • indication information can include a starting RB index.
  • UEs can know a whole "resource chunk" available for the PRACH, given that N is predefined.
  • N can also be configured via RRC signaling.
  • a user equipment (UE) operating on an unlicensed spectrum can be capable of listen before talk (LBT).
  • the UE can communicate with an enhanced node B (eNodeB) using a licensed medium and/or an unlicensed medium.
  • the UE can be capable of sensing the unlicensed medium before an UL transmission, and when the unlicensed medium is determined to be idle, the UE can perform the UL transmission.
  • the UE can prevent the UL transmission.
  • the eNodeB can receive the UL transmission from the UE.
  • the UE and the eNodeB can operate using a 3.5 GHz unlicensed spectrum.
  • PRACH physical random access channel
  • PRBs physical resource blocks
  • a subcarrier spacing can be reduced and a longer sequence can be designed.
  • a cyclic prefix (CP) duration can follow a LTE PRACH design (e.g., 103.13us for PRACH format 0).
  • the CP duration can be shorter than the LTE PRACH design, with remaining time available for transmitters to perform LBT.
  • the PRACH can have a same subcarrier spacing as a PUSCH (i.e., 15 kHz).
  • every other symbol can be used to carry the PRACH preamble, and remaining symbols can be cyclic shifted versions of other symbols that can use a "long CP".
  • the CP duration of symbol ke ⁇ 0, 2, 4, 6, 8, 10, 12 ⁇ can be the same as in legacy LTE systems (e.g.,
  • 4.7 ⁇ 8 or can be twice of the CP duration as in legacy LTE systems, where a symbol boundary of every 2 symbols can be aligned with other channels (e.g., PUSCH) in the latter case.
  • the PRACH in eLAA and MulteFire systems can also be repeated multiple times.
  • the PRACH transmission can include a CP and several repeated PRACH preamble symbols, where the CP duration can depend on a maximal delay spread and a maximal round trip delay, and a number of preamble repetition can depend on a specified coverage area.
  • the CP duration can be predefined in a 3GPP LTE specification, or can be configured via RRC signaling.
  • the PRACH transmission can include no CP, but only several repeated PRACH preamble symbols.
  • a guard band can be introduced at two ends of whole allocated resource blocks (RBs).
  • a number of subcarriers left to the guard band can depend on a cell size and operation preference (e.g., a tolerable performance loss due to overhead caused by the guard band). For example, 15 kHz and 22.5 kHz can be left blank at the two ends, respectively, to reduce inter-cell interference (ICI).
  • ICI inter-cell interference
  • a PRACH preamble sequence after puncturing/repeating can be a length of (720-N_guard) for a 1.25kHz subcarrier spacing and (120-N_guard) for 7.5kHz, where N ua rd
  • a novel sequence with a desirable length can be designed.
  • ZC Zadoff-Chu
  • a PRACH from different UEs can be multiplexed in a frequency domain, via cyclic shifts (CS) and/or orthogonal cover codes (OCC) and/or base sequences.
  • OCC length can be the same as a number of PRACH preamble symbols with a CP, e.g., an OCC with a length of N can be applied for PRACH format 4 when a PRACH format 4 preamble is repeated N times.
  • an OCC length can be half of a number of PRACH symbols, where the OCC can be applied to symbol k and k+1 with ke ⁇ 0, 2, 4, 6, 8, 10, 12 ⁇ being the same.
  • the PRACH and other UL channels, e.g., PUSCH and PUCCH, which use an interlaced structure can be multiplexed via time division multiplexing (TDM) but not frequency division multiplexing (FDM).
  • the PRACH and other UL channels, e.g., PUSCH and PUCCH, which use an interlaced structure can be multiplexed via TDM and/or FDM.
  • the PRACH and other UL channels with interlaced structure are multiplexed via FDM, the UL
  • transmissions with the interlaced structure can be rate matched around the RBs allocated for the PRACH transmission.
  • the UL transmissions with interlaced structure can be mapped to 9 RBs per interlace in the subframe, with 1 RB in each interlaced left empty for the PRACH transmission.
  • 6 PRBs are allocated for the PRACH
  • the RBs allocated for the PRACH transmission can be punctured, i.e., the UL transmissions with interlaced structure can be mapped to 10 PRBs per interlace, and RBs allocated for the PRACH transmissions can be used to carry the PRACH preamble, with the symbols for other UL transmissions being punctured on these PRBs.
  • the PRACH can be transmitted over a remaining part following a downlink pilot time slot (DwPTS) of a special subframe or a regular UL subframe.
  • DwPTS downlink pilot time slot
  • a PDCCH order can be used to indicate a PRACH preamble sequence, and a time resource to transmit the PRACH, which can be either explicit or implicit.
  • a fixed timing relationship between the reception of the PDCCH order and the transmission of the PRACH can be predefined (e.g., 4 or 6 subframes between the PDCCH order and PRACH transmission).
  • the timing resource for the PRACH can be semi-statically configured via RRC signaling for contention-free and/or contention-based PRACH.
  • frequency resources for the PRACH transmission can be semi- statically configured via RRC, or dynamically indicated via the PDCCH order for contention-free PRACH.
  • indication information can include a starting RB index.
  • a number of PRBs available for the PRACH transmission (denoted by N) can be predefined, or can be configured via RRC signaling.
  • the UL design for MulteFire systems is to abide by regulatory specifications. For example, to satisfy the occupied channel bandwidth (OCB) regulation, traditional subband-based UL scheduling is to be updated, unless one UE is always assigned for the entire bandwidth.
  • multi-cluster transmissions are to be supported in eLAA and MulteFire systems, where user data is placed over interlaced RBs and are frequency multiplexed.
  • one interlace can include 10 RBs for systems with 20MHz.
  • a cluster can include 1 RB, and thus one interlace can have 10 clusters for 20MHz, e.g., a B-IFDMA waveform.
  • a novel PRACH design is described for the unlicensed spectrum.
  • the PRACH can be used for scheduling requests (SR), uplink synchronization and power control for initial UL transmissions in legacy LTE systems. Due to the OCB regulation, the PRACH can use the B-IFDMA waveform (as shown in FIG. 1).
  • an UL portion in a special subframe can be used for the PRACH transmission, where the PRACH can occupy a last 4 symbols, which can be referred to as a shortened PRACH (sPRACH).
  • the sPRACH can utilize a 15 kHz subcarrier spacing, and a cyclic prefix
  • CP duration of 4.7 us, which is the same as other UL channels.
  • the targeted use case of the sPRACH is for small cell deployments with a cell radius within 200-300m.
  • the transmissions from different UEs in a small cell can arrive at an eNodeB within a CP duration.
  • transmissions on different interlaces can be orthogonal, and there is no inter-interlace interference.
  • a transmission arrival time at the eNodeB from different UEs can have larger disparities, e.g., larger than the CP duration in LTE systems. This may break the orthogonality among transmissions on different interlaces, which can result in inter-interlace interference.
  • a novel PRACH design can overcome the inter-interlace interference in large cell deployments.
  • the PRACH can be transmitted over a regular UL subframe, which can be referred to as an enhanced PRACH (ePRACH).
  • the PRACH can include an interlaced structure and is useful for MulteFire systems.
  • novel PRACH design can incorporate various novel design aspects, such as a combination of specific UE multiplexing techniques, LBT techniques, a novel PRACH waveform and resource allocation (or interlace allocation) techniques to improve a timing estimation accuracy (or timing estimation ambiguity issues).
  • a PRACH waveform can have a same subcarrier spacing as a PUSCH (i.e., 15 kHz).
  • a PRACH transmission can include a CP and several repeated PRACH preamble symbols, where a CP duration can depend on a maximal delay spread and a maximal round trip delay.
  • the CP duration can be predefined in a 3GPP LTE
  • the PRACH preamble can have no CP.
  • a preceding symbol can be used as a CP for a following symbol, and a number of preamble repetitions can depend on a specified coverage area.
  • a PRACH symbol structure can include repeated PRACH preamble symbols (e.g., 3 repeated preambles) that follow a CP duration, which can depend on the maximal delay spread and a cell size, or have no CP.
  • UE multiplexing techniques can be based on a cyclic shift (CS), an orthogonal cover code (OCC) or different root sequences.
  • CS cyclic shift
  • OCC orthogonal cover code
  • a CS value is to be at least larger than a maximal delay spread plus a maximal round-trip delay.
  • OCC when a number of transmitted PRACH preambles is N, an OCC with a length of N/2 can be applied instead of N.
  • an OCC for a symbol k and k+1 with ke ⁇ 0, 2, 4, 6, 8, 10, 12 ⁇ can be the same.
  • a timing estimation ambiguity issue caused by an equidistant B-IFDMA waveform can be resolved.
  • the equidistant B-IFDMA can result in multiple peaks in a correlation profile of the PRACH, which can lead to ambiguity in timing estimation and impact TA functionality.
  • a generated RB partem for each UE can be irregular, which can help reduce the ambiguity in timing estimation.
  • two interlaces e.g., interlaces ⁇ 0, 5 ⁇ , ⁇ 1, 6 ⁇ , ⁇ 2, 7 ⁇ , ⁇ 3, 8 ⁇ , or ⁇ 4, 9 ⁇
  • each set of resources among the M sets can be allocated with different sets of PRACH preamble sequences, or a common set of PRACH preamble sequences.
  • the PRACH can have a subcarrier spacing of 15 kHz, which can include N repeated PRACH preamble symbols, which may or may not be preceded by a CP.
  • the PRACH can be multiplexed via the CS, OCC and/or root sequences.
  • the OCC can be applied with a length of N/2 instead of N, where N is the number of PRACH symbols.
  • the OCC for the symbol k and k+1 with ke ⁇ 0, 2, 4, 6, 8, 10, 12 ⁇ can be the same.
  • L interlaces can be shared with M sets of UEs (e.g.
  • Each UE can use 10L/M RBs for the PRACH transmission.
  • the generated RB pattern for each UE can be irregular, which can help reduce the ambiguity in timing estimation.
  • two interlaces can be shared with two sets of UEs, and each set of preambles can be transmitted on 10 out of 20 PRBs within the two interlaces.
  • the resource can be separated into RBs ⁇ 0, 5, 20, 25, 30, 50, 55, 70, 75, 95 ⁇ and ⁇ 10, 15, 35, 40, 45, 60, 65, 80, 85, 90 ⁇ , where each set of PRBs can be associated with two different sets of PRACH preamble sequences, or a common set of PRACH preamble sequences.
  • a PRACH design is defined with an interlaced structure for MulteFire systems.
  • the PRACH design can define a PRACH waveform, a format, and a resource allocation, and can be utilized to resolve a timing estimation ambiguity issue.
  • the PRACH can have the same subcarrier spacing as a PUSCH (i.e., 15 kHz).
  • the PRACH in MulteFire systems can also be repeated multiple times. A previous symbol can be used as a "long CP" for a following symbol.
  • a PRACH transmission can include a CP and several repeated PRACH preamble symbols, where a CP duration can depend on a maximal delay spread and a maximal round trip delay, and a number of preamble repetition can depend on a specified coverage area.
  • the CP duration can be predefined in a 3 GPP LTE specification, or can be configured via RRC signaling.
  • the PRACH transmission can include no CP, but only several repeated PRACH preamble symbols.
  • UEs can be multiplexed in same resources, via a cyclic shift (CS), root sequence and/or OCC.
  • an OCC length can be half of the number of PRACH symbols, where the OCC applied to symbol k and k+1 with ke ⁇ 0, 2, 4, 6, 8, 10, 12 ⁇ are the same.
  • an irregular RB pattern can be allocated.
  • RBs in each interlace can be randomly separated into M parts, allocated to these M sets of UEs, to generate irregular RB pattern for each UE.
  • Each separate PRB can be associated with a different set of PRACH preambles, or a common set of PRACH preambles can be transmitted in any separation of PRBs.
  • N can be 2 and M can be 2, i.e., two interlaces can be separated into two parts, with each part having 10 PRBs out of the 20 PRBs, and the two interlaces can belong to set ⁇ 0, 5 ⁇ , ⁇ 1, 6 ⁇ , ⁇ 2, 7 ⁇ , ⁇ 3, 8 ⁇ , or ⁇ 4, 9 ⁇ .
  • FIG. 10 Another example provides functionality 1000 of an eNodeB operable to set an uplink timing advance (TA) value for random access channel (RACH) transmissions in a MuLTEfire system, as shown in FIG. 10.
  • the eNodeB can comprise one or more processors.
  • the one or more processors can be configured to determine, at the eNodeB, that a RACH transmission to be received from a user equipment (UE) in an uplink in the MuLTEfire system is associated with a shortened physical uplink control channel (sPUCCH) format or an enhanced physical uplink control channel (ePUCCH) format, as in block 1010.
  • sPUCCH shortened physical uplink control channel
  • ePUCCH enhanced physical uplink control channel
  • the one or more processors can be configured to configure, at the eNodeB, the UE to utilize the uplink TA value for the RACH transmission when the RACH transmission is associated with the sPUCCH format or the ePUCCH format, wherein the uplink TA value is a common TA offset value for a plurality of UEs, as in block 1020.
  • the one or more processors can be configured to encode, at the eNodeB, an instruction for transmission to the UE that instructs the UE to perform clear channel access (CCA) sensing prior to performing the RACH transmission in the uplink when the RACH transmission is associated with the sPUCCH format, as in block 1030.
  • CCA clear channel access
  • the one or more processors can be configured to encode, at the eNodeB, an instruction for transmission to the UE that instructs the UE to perform CCA sensing and a self-defer mechanism prior to performing the RACH transmission in the uplink when the RACH transmission is associated with the ePUCCH format, as in block 1040.
  • the eNodeB can comprise a memory interface configured to send to a memory the uplink TA value.
  • the eNodeB can comprise one or more processors.
  • the one or more processors can be configured to identify, at the eNodeB, a PRACH configuration being utilized by a MuLTEfire system that operates in an unlicensed spectrum, wherein the PRACH configuration defines a number of continuous physical resource blocks (PRBs) in the unlicensed spectrum to be used for PRACH transmissions, as in block 1110.
  • PRBs physical resource blocks
  • the one or more processors can be configured to decode, at the eNodeB, a PRACH transmission received from a user equipment (UE) in accordance with the PRACH configuration, wherein the PRACH transmission includes a PRACH preamble that is transmitted using the number of continuous PRBs defined in the PRACH configuration, as in block 1120.
  • the eNodeB can comprise a memory interface configured to send to a memory the PRACH configuration being utilized by the MuLTEfire system.
  • Another example provides at least one machine readable storage medium having instructions 1200 embodied thereon for performing physical random access channel (PRACH) transmissions, as shown in FIG. 12.
  • 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 eNodeB, a PRACH configuration being utilized by a MuLTEfire system that operates in an unlicensed spectrum, wherein the PRACH configuration defines an interlaced structure of physical resource blocks (PRBs) in a regular uplink subframe to be used for PRACH transmissions, as in block 1210.
  • PRBs physical resource blocks
  • the instructions when executed perform: decoding, at the eNodeB, a PRACH transmission received from a user equipment (UE) in accordance with the PRACH configuration, wherein the PRACH transmission is transmitted using the interlaced structure of PRBs in the regular subframe in accordance with the PRACH configuration, as in block 1220.
  • UE user equipment
  • FIG. 13 illustrates an architecture of a system 1300 of a network in accordance with some embodiments.
  • the system 1300 is shown to include a user equipment (UE) 1301 and a UE 1302.
  • the UEs 1301 and 1302 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 Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • any of the UEs 1301 and 1302 can comprise an Intemet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • 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 1301 and 1302 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1310—
  • the RAN 1310 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 1301 and 1302 utilize connections 1303 and 1304, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 1303 and 1304 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code- division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code- division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 1301 and 1302 may further directly exchange communication data via a ProSe interface 1305.
  • the ProSe interface 1305 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 1302 is shown to be configured to access an access point (AP) 1306 via connection 1307.
  • the connection 1307 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.15 protocol, wherein the AP 1306 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 1306 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 1310 can include one or more access nodes that enable the connections 1303 and 1304. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, 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).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes 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).
  • the RAN 1310 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1311, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1312.
  • macro RAN node 1311 e.g., macro RAN node 1311
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 1311 and 1312 can terminate the air interface protocol and can be the first point of contact for the UEs 1301 and 1302.
  • any of the RAN nodes 1311 and 1312 can fulfill various logical functions for the RAN 1310 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 1301 and 1302 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1311 and 1312 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (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.
  • 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 1311 and 1312 to the UEs 1301 and 1302, 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
  • 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.
  • the physical downlink shared channel may carry user data and higher- layer signaling to the UEs 1301 and 1302.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 1301 and 1302 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 1302 within a cell) may be performed at any of the RAN nodes 1311 and 1312 based on channel quality information fed back from any of the UEs 1301 and 1302.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 1301 and 1302.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel 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 resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • 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).
  • 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 enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 1310 is shown to be communicatively coupled to a core network (CN) 1320— via an SI interface 1313.
  • the CN 1320 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 1313 is split into two parts: the S l-U interface 1314, which carries traffic data between the RAN nodes 1311 and 1312 and the serving gateway (S-GW) 1322, and the S l-mobility management entity (MME) interface 1315, which is a signaling interface between the RAN nodes 1311 and 1312 and MMEs 1321.
  • S-GW serving gateway
  • MME S l-mobility management entity
  • the CN 1320 comprises the MMEs 1321, the S-GW 1322, the Packet Data Network (PDN) Gateway (P-GW) 1323, and a home subscriber server (HSS) 1324.
  • the MMEs 1321 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 1321 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 1324 may comprise a database for network users, including subscription-related information to support the network entities' handling of
  • the CN 1320 may comprise one or several HSSs 1324, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 1324 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 1322 may terminate the S I interface 1313 towards the RAN 1310, and routes data packets between the RAN 1310 and the CN 1320.
  • the S-GW 1322 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 1323 may terminate an SGi interface toward a PDN.
  • the P-GW 1323 may route data packets between the EPC network 1323 and external networks such as a network including the application server 1330 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 1325.
  • the application server 1330 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 1323 is shown to be communicatively coupled to an application server 1330 via an IP communications interface 1325.
  • the application server 1330 can also be configured to support one or more communication services (e.g., Voice- over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1301 and 1302 via the CN 1320.
  • VoIP Voice- over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 1323 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 1326 is the policy and charging control element of the CN 1320.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 1326 may be communicatively coupled to the application server 1330 via the P-GW 1323.
  • the application server 1330 may signal the PCRF 1326 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 1326 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 1330.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 14 illustrates example components of a device 1400 in accordance with some embodiments.
  • the device 1400 may include application circuitry 1402, baseband circuitry 1404, Radio Frequency (RF) circuitry 1406, front-end module (FEM) circuitry 1408, one or more antennas 1410, and power management circuitry (PMC) 1412 coupled together at least as shown.
  • the components of the illustrated device 1400 may be included in a UE or a RAN node.
  • the device 1400 may include less elements (e.g., a RAN node may not utilize application circuitry 1402, and instead include a processor/controller to process IP data received from an EPC).
  • the device 1400 may include additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • C-RAN Cloud-RAN
  • the application circuitry 1402 may include one or more application processors.
  • the application circuitry 1402 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 1400.
  • processors of application circuitry 1402 may process IP data packets received from an EPC.
  • the baseband circuitry 1404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 1404 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1406 and to generate baseband signals for a transmit signal path of the RF circuitry 1406.
  • Baseband processing circuity 1404 may interface with the application circuitry 1402 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1406.
  • the baseband circuitry 1404 may include a third generation (3G) baseband processor 1404a, a fourth generation (4G) baseband processor 1404b, a fifth generation (5G) baseband processor 1404c, or other baseband processor(s) 1404d for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 1404 e.g., one or more of baseband processors 1404a-d
  • baseband processors 1404a-d may be included in modules stored in the memory 1404g and executed via a Central Processing Unit (CPU) 1404e.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • signal modulation/demodulation e.g., a codec
  • encoding/decoding e.g., a codec
  • radio frequency shifting e.
  • modulation/demodulation circuitry of the baseband circuitry 1404 may include Fast- Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast- Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 1404 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 1404 may include one or more audio digital signal processor(s) (DSP) 1404f.
  • the audio DSP(s) 1404f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 1404 and the application circuitry 1402 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 1404 may provide for
  • the baseband circuitry 1404 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 1404 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 1406 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 1406 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 1406 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1408 and provide baseband signals to the baseband circuitry 1404.
  • RF circuitry 1406 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1404 and provide RF output signals to the FEM circuitry 1408 for transmission.
  • the receive signal path of the RF circuitry 1406 may include mixer circuitry 1406a, amplifier circuitry 1406b and filter circuitry 1406c.
  • the transmit signal path of the RF circuitry 1406 may include filter circuitry 1406c and mixer circuitry 1406a.
  • RF circuitry 1406 may also include synthesizer circuitry 1406d for synthesizing a frequency for use by the mixer circuitry 1406a of the receive signal path and the transmit signal path.
  • the mixer circuitry 1406a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1408 based on the synthesized frequency provided by synthesizer circuitry 1406d.
  • the amplifier circuitry 1406b may be configured to amplify the down-converted signals and the filter circuitry 1406c 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 1404 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a necessity.
  • mixer circuitry 1406a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1406a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1406d to generate RF output signals for the FEM circuitry 1408.
  • the baseband signals may be provided by the baseband circuitry 1404 and may be filtered by filter circuitry 1406c.
  • the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a 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 1406a of the receive signal path and the mixer circuitry 1406a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a 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.
  • the RF circuitry 1406 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1404 may include a digital baseband interface to communicate with the RF circuitry 1406.
  • 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 embodiments is not limited in this respect.
  • the synthesizer circuitry 1406d 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 1406d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1406d may be configured to synthesize an output frequency for use by the mixer circuitry 1406a of the RF circuitry 1406 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1406d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 1404 or the applications processor 1402 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 applications processor 1402.
  • Synthesizer circuitry 1406d of the RF circuitry 1406 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 1406d 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 1406 may include an IQ/polar converter.
  • FEM circuitry 1408 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1410, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1406 for further processing.
  • FEM circuitry 1408 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1406 for transmission by one or more of the one or more antennas 1410.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1406, solely in the FEM 1408, or in both the RF circuitry 1406 and the FEM 1408.
  • the FEM circuitry 1408 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 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 1406).
  • the transmit signal path of the FEM circuitry 1408 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1406), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1410).
  • PA power amplifier
  • the PMC 1412 may manage power provided to the baseband circuitry 1404.
  • the PMC 1412 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 1412 may often be included when the device 1400 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 1412 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation
  • FIG. 14 shows the PMC 1412 coupled only with the baseband circuitry 1404.
  • the PMC 14 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1402, RF circuitry 1406, or FEM 1408.
  • the PMC 1412 may control, or otherwise be part of, various power saving mechanisms of the device 1400. For example, if the device 1400 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 device 1400 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 1400 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 device 1400 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 device 1400 may not receive data in this state, in order to receive data, it must transition back to
  • 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.
  • Processors of the application circuitry 1402 and processors of the baseband circuitry 1404 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 1404 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1404 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 15 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 1404 of FIG. 14 may comprise processors 1404a-1404e and a memory 1404g utilized by said processors.
  • Each of the processors 1404a-1404e may include a memory interface, 1504a-1504e, respectively, to send/receive data to/from the memory 1404g.
  • the baseband circuitry 1404 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1512 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1404), an application circuitry interface 1514 (e.g., an interface to send/receive data to/from the application circuitry 1402 of FIG. 14), an RF circuitry interface 1516 (e.g., an interface to send/receive data to/from RF circuitry 1406 of FIG.
  • a memory interface 1512 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1404
  • an application circuitry interface 1514 e.g., an interface to send/receive data to/from the application circuitry 1402 of FIG. 14
  • an RF circuitry interface 1516 e.g., an interface to send/receive data to/from RF circuitry 1406 of FIG.
  • a wireless hardware connectivity interface 1518 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 1520 e.g., an interface to send/receive power or control signals to/from the PMC 1412.
  • FIG. 16 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, 3 GPP 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
  • 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. 16 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.
  • a non-volatile memory port can also be used to provide data input/output options to a user.
  • the non-volatile memory port can also be used to expand the memory 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.
  • Example 1 includes an apparatus of an eNodeB operable to set an uplink timing advance (TA) value for random access channel (RACH) transmissions in a MuLTEfire system, the apparatus comprising: one or more processors configured to: determine, at the eNodeB, that a RACH transmission to be received from a user equipment (UE) in an uplink in the MuLTEfire system is associated with a shortened physical uplink control channel (sPUCCH) format or an enhanced physical uplink control channel (ePUCCH) format; configure, at the eNodeB, the UE to utilize the uplink TA value for the RACH transmission when the RACH transmission is associated with the sPUCCH format or the ePUCCH format, wherein the uplink TA value is a common TA offset value for a plurality of UEs; encode, at the eNodeB, an instruction for transmission to the UE that instructs the UE to perform clear channel access (CCA) sensing prior to performing the RACH transmission in the up
  • Example 2 includes the apparatus of Example 1, further comprising a transceiver configured to: transmit the uplink TA value to the UE; transmit an instruction to the UE to perform the CCA sensing when the RACH transmission is associated with the sPUCCH format; and transmit an instruction to the UE to perform the CCA sensing and the self- defer mechanism when the RACH transmission is associated with the ePUCCH format.
  • a transceiver configured to: transmit the uplink TA value to the UE; transmit an instruction to the UE to perform the CCA sensing when the RACH transmission is associated with the sPUCCH format; and transmit an instruction to the UE to perform the CCA sensing and the self- defer mechanism when the RACH transmission is associated with the ePUCCH format.
  • Example 3 includes the apparatus of any of Examples 1 to 2, wherein the one or more processors are further configured to encode an instruction for transmission to the UE that instructs the UE to perform the CCA sensing at a beginning of a CCA slot when the RACH transmission is associated with the sPUCCH format.
  • Example 4 includes the apparatus of any of Examples 1 to 3, wherein the one or more processors are further configured to: encode an instruction for transmission to the UE that instructs the UE to perform the CCA sensing at a maximum individual TA value for the UE earlier than the RACH transmission when the RACH transmission is associated with the ePUCCH format; and encode an instruction for transmission to the UE that instructs the UE to perform the self-defer mechanism for the RACH transmission by the maximum individual TA value for the UE when the RACH transmission is associated with the ePUCCH format.
  • Example 5 includes the apparatus of any of Examples 1 to 4, wherein the one or more processors are further configured to encode a system information block for
  • SIB-MF MuLTEfire
  • Example 6 includes the apparatus of any of Examples 1 to 5, wherein the one or more processors are further configured to encode a system information block for
  • Example 7 includes the apparatus of any of Examples 1 to 6, wherein the sPUCCH format for the RACH transmission corresponds to a reduced cell size, and the ePUCCH format for the RACH transmission corresponds to an increased cell size.
  • Example 8 includes the apparatus of any of Examples 1 to 7, wherein the one or more processors are further configured to decode a RACH preamble received from the UE, wherein the PRACH preamble is received when the UE is successful in performing the CCA sensing.
  • Example 9 includes the apparatus of any of Examples 1 to 8, wherein the one or more processors are further configured to: encode an instruction for transmission to the UE that instructs the UE to perform the CCA sensing as defined for a 5 gigahertz (GHz) band when the RACH transmission is associated with the sPUCCH format; and encode an instruction for transmission to the UE that instructs the UE to perform the CCA sensing as defined for a 3.5 GHz band when the RACH transmission is associated with the ePUCCH format.
  • GHz gigahertz
  • Example 10 includes the apparatus of any of Examples 1 to 9, wherein the one or more processors are configured to encode an instruction for transmission to the UE that instructs the UE to perform the CCA sensing and the self-defer mechanism to mitigate the RACH transmission being blocked by a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) transmission, or a PUSCH or PUCCH transmission blocking the RACH transmission, wherein the self-defer mechanism is performed at the UE in conjunction with listen before talk (LBT) to prevent the UE from blocking transmissions from other UEs.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • LBT listen before talk
  • Example 11 includes an apparatus of an eNodeB operable to perform physical random access channel (PRACH) transmissions, the eNodeB comprising: one or more processors configured to: identify, at the eNodeB, a PRACH configuration being utilized by a MuLTEfire system that operates in an unlicensed spectrum, wherein the PRACH configuration defines a number of continuous physical resource blocks (PRBs) in the unlicensed spectrum to be used for PRACH transmissions; and decode, at the eNodeB, a PRACH transmission received from a user equipment (UE) in accordance with the PRACH configuration, wherein the PRACH transmission includes a PRACH preamble that is transmitted using the number of continuous PRBs defined in the PRACH configuration; and a memory interface configured to send to a memory the PRACH configuration being utilized by the MuLTEfire system.
  • PRACH physical random access channel
  • Example 12 includes the apparatus of Example 11, wherein the unlicensed spectrum is in a 3.5 gigahertz (GHz) band.
  • GHz gigahertz
  • Example 13 includes the apparatus of any of Examples 11 to 12, wherein the number of continuous PRBs is 5 continuous PRBs or 6 continuous PRBs.
  • Example 14 includes the apparatus of any of Examples 11 to 13, wherein the number of continuous PRBs to be used for PRACH transmissions are separate from other PRBs being utilized for other uplink channels in accordance with an interlaced structure.
  • Example 15 includes the apparatus of any of Examples 11 to 14, wherein the
  • PRACH configuration defines the number of continuous PRBs in the unlicensed spectrum to be used for PRACH transmissions in order to improve a timing estimation
  • Example 16 includes the apparatus of any of Examples 11 to 15, wherein the PRACH transmission includes a number of repeated PRACH preamble symbols that are preceded by a cyclic prefix or not preceded by a cyclic prefix.
  • Example 17 includes the apparatus of any of Examples 11 to 16, wherein the PRACH configuration enables a PRACH and other uplink channels that utilize an interlaced structure to be multiplexed via one or more of time division multiplexing (TDM) or frequency division multiplexing (FDM), wherein the other uplink channels include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).
  • TDM time division multiplexing
  • FDM frequency division multiplexing
  • the other uplink channels include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • Example 18 includes at least one machine readable storage medium having instructions embodied thereon for performing physical random access channel (PRACH) transmissions, the instructions when executed by one or more processors at an eNodeB perform the following: identifying, at the eNodeB, a PRACH configuration being utilized by a MuLTEfire system that operates in an unlicensed spectrum, wherein the PRACH configuration defines an interlaced structure of physical resource blocks (PRBs) in a regular uplink subframe to be used for PRACH transmissions; and decoding, at the eNodeB, an PRACH transmission received from a user equipment (UE) in accordance with the PRACH configuration, wherein the PRACH transmission is transmitted using the interlaced structure of PRBs in the regular subframe in accordance with the PRACH configuration.
  • PRACH physical random access channel
  • Example 19 includes the at least one machine readable storage medium of Example 18, wherein the unlicensed spectrum is in a 5 gigahertz (GHz) band.
  • GHz gigahertz
  • Example 20 includes the at least one machine readable storage medium of any of Examples 18 to 19, wherein the PRACH configuration defines the interlaced structure of PRBs in the regular uplink subframe to be used for PRACH transmissions in order to satisfy a specification defined by a regulatory body.
  • Example 21 includes the at least one machine readable storage medium of any of Examples 18 to 20, wherein the PRACH transmission includes a number of repeated PRACH preamble symbols that are preceded by a cyclic prefix or not preceded by a cyclic prefix, wherein a cyclic prefix duration depends on a maximal delay spread and a maximal round trip delay, wherein the cyclic prefix duration is configured via radio resource control (RRC) signaling.
  • RRC radio resource control
  • Example 22 includes the at least one machine readable storage medium of any of Examples 18 to 21, wherein the PRACH configuration enables a PRACH to be multiplexed via one or more of a cyclic shift, an orthogonal cover code (OCC) or a root sequence.
  • the PRACH configuration enables a PRACH to be multiplexed via one or more of a cyclic shift, an orthogonal cover code (OCC) or a root sequence.
  • OCC orthogonal cover code
  • Example 23 includes the at least one machine readable storage medium of any of Examples 18 to 22, wherein the PRACH configuration defines a number of interlaces to be shared with a number of sets of UEs for the PRACH transmission, wherein PRBs in each interlace are randomly separated into a number of parts allocated to the number of sets, wherein a generated PRB pattern for each UE is irregular to reduce ambiguity in a timing estimation.
  • Example 24 includes an eNodeB operable to perform physical random access channel (PRACH) transmissions, the eNodeB comprising: means for identifying, at the eNodeB, a PRACH configuration being utilized by a MuLTEfire system that operates in an unlicensed spectrum, wherein the PRACH configuration defines an interlaced structure of physical resource blocks (PRBs) in a regular uplink subframe to be used for PRACH transmissions; and means for decoding, at the eNodeB, an PRACH transmission received from a user equipment (UE) in accordance with the PRACH configuration, wherein the PRACH transmission is transmitted using the interlaced structure of PRBs in the regular subframe in accordance with the PRACH configuration.
  • PRACH physical random access channel
  • Example 25 includes the eNodeB of Example 24, wherein the unlicensed spectrum is in a 5 gigahertz (GHz) band.
  • GHz gigahertz
  • Example 26 includes the eNodeB of any of Examples 24 to 25, wherein the PRACH configuration defines the interlaced structure of PRBs in the regular uplink subframe to be used for PRACH transmissions in order to satisfy a specification defined by a regulatory body.
  • Example 27 includes the eNodeB of any of Examples 24 to 26, wherein the PRACH transmission includes a number of repeated PRACH preamble symbols that are preceded by a cyclic prefix or not preceded by a cyclic prefix, wherein a cyclic prefix duration depends on a maximal delay spread and a maximal round trip delay, wherein the cyclic prefix duration is configured via radio resource control (RRC) signaling.
  • RRC radio resource control
  • Example 28 includes the eNodeB of any of Examples 24 to 27, wherein the PRACH configuration enables a PRACH to be multiplexed via one or more of a cyclic shift, an orthogonal cover code (OCC) or a root sequence.
  • OCC orthogonal cover code
  • Example 29 includes the eNodeB of any of Examples 24 to 28, wherein the PRACH configuration defines a number of interlaces to be shared with a number of sets of UEs for the PRACH transmission, wherein PRBs in each interlace are randomly separated into a number of parts allocated to the number of sets, wherein a generated PRB pattern for each UE is irregular to reduce ambiguity in a timing estimation.
  • 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 nonvolatile 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.
  • modules 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une technologie pour un nœud B évolué (eNodeB) utilisable pour réaliser des transmissions de canal d'accès aléatoire physique (PRACH, "physical random access channel") dans une bande de fréquences sans licence, dans le contexte de eLAA LTE 3GPP, c'est-à-dire MuLTEfire. L'eNodeB peut identifier une configuration de PRACH utilisée par un système d'incendie qui fonctionne dans un spectre sans licence. La configuration PRACH peut définir un certain nombre de blocs de ressources physiques (PRB, "physical resource block") continus dans le spectre sans licence à utiliser pour des transmissions PRACH. L'eNodeB peut décoder une transmission PRACH reçue en provenance d'un équipement utilisateur (UE, "user equipment") conformément à la configuration PRACH. La transmission PRACH peut comprendre un préambule PRACH qui est transmis à l'aide du nombre de PRB continus définis dans la configuration PRACH. L'eNB configure les performances d'évaluation de canal libre (CCA, "clear channel assesment") avant la transmission de préambule par l'UE. Dans le cas où la trame de transmission de liaison montante est configurée avec un PUCCH court (sPUCCH, "short PUCCH"), seule une CCA courte est configurée. Sinon, par exemple lorsque la trame permet de configurer un ePUCCH, la CCA est suivie d'une période d'auto-report.
PCT/US2017/049770 2016-09-02 2017-08-31 Conception de canal d'accès aléatoire physique (prach) pour porteuses sans licence en lte WO2018045247A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US201662383103P 2016-09-02 2016-09-02
US62/383,103 2016-09-02
US201662414470P 2016-10-28 2016-10-28
US62/414,470 2016-10-28
US201662415215P 2016-10-31 2016-10-31
US62/415,215 2016-10-31

Publications (1)

Publication Number Publication Date
WO2018045247A1 true WO2018045247A1 (fr) 2018-03-08

Family

ID=59846730

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/049770 WO2018045247A1 (fr) 2016-09-02 2017-08-31 Conception de canal d'accès aléatoire physique (prach) pour porteuses sans licence en lte

Country Status (1)

Country Link
WO (1) WO2018045247A1 (fr)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019192622A1 (fr) * 2018-04-06 2019-10-10 Mediatek Inc. Conception d'entrelacement pour un fonctionnement dans un spectre sans licence en nouvelle radio
WO2019216702A1 (fr) * 2018-05-10 2019-11-14 엘지전자 주식회사 Procédé de transmission de préambule prach dans un système de communication sans fil à l'aide d'une bande sans licence et appareil correspondant
WO2020030263A1 (fr) * 2018-08-08 2020-02-13 Huawei Technologies Co., Ltd. Dispositifs, procédés et programmes informatiques pour économiser des ressources de fréquence dans les communications sans fil
US20200068625A1 (en) * 2018-08-21 2020-02-27 Qualcomm Incorporated Interlace prach design in nr-u
WO2020067696A1 (fr) 2018-09-26 2020-04-02 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception d'un signal dans un système de communication sans fil
CN111181885A (zh) * 2018-11-13 2020-05-19 中国科学院上海高等研究院 超高速移动宽带通信中前导信号的发送方法与接收方法
WO2020143907A1 (fr) * 2019-01-09 2020-07-16 Huawei Technologies Co., Ltd. Dispositif client et nœud d'accès au réseau permettant de transmettre et de recevoir un préambule d'accès aléatoire
CN112399546A (zh) * 2019-08-12 2021-02-23 华为技术有限公司 公共定时提前的指示方法、装置、设备及存储介质
WO2021066590A1 (fr) * 2019-10-04 2021-04-08 엘지전자 주식회사 Procédé pour la transmission et la réception d'un signal dans un système de communication sans fil, et dispositif prenant en charge le procédé
CN112868266A (zh) * 2018-09-26 2021-05-28 华为技术有限公司 用于发送和接收随机接入前导的客户端设备和网络接入节点
WO2021147898A1 (fr) * 2020-01-23 2021-07-29 中国移动通信有限公司研究院 Procédé de détermination de rythme d'émission en liaison montante, terminal et station de base
US20210307075A1 (en) * 2018-11-01 2021-09-30 Panasonic Intellectual Property Corporation Of America Transmission device, reception device, transmission method, and reception method
EP3841819A4 (fr) * 2018-09-26 2021-12-08 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception d'un signal dans un système de communication sans fil

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016137948A1 (fr) * 2015-02-24 2016-09-01 Qualcomm Incorporated Canal prach amélioré pour communications autonomes basées sur la contention, comprenant un spectre sans licence

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016137948A1 (fr) * 2015-02-24 2016-09-01 Qualcomm Incorporated Canal prach amélioré pour communications autonomes basées sur la contention, comprenant un spectre sans licence

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 13)", 3GPP STANDARD; 3GPP TS 36.321, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V13.2.0, 7 July 2016 (2016-07-07), pages 1 - 91, XP051123446 *
ERICSSON: "On Channel Access Procedures for PRACH and SRS", vol. RAN WG1, no. Nanjing, China; 20160523 - 20160527, 14 May 2016 (2016-05-14), XP051089830, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_85/Docs/> [retrieved on 20160514] *
NOKIA ET AL: "Discussion on PRACH design for eLAA", vol. RAN WG1, no. Busan, South Korea; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051080411, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/> [retrieved on 20160402] *
NTT DOCOMO ET AL: "Discussion on PRACH for eLAA UL", vol. RAN WG1, no. Nanjing; 20160523 - 20160527, 14 May 2016 (2016-05-14), XP051089816, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_85/Docs/> [retrieved on 20160514] *
SAMSUNG: "Discussion on random access procedure for eLAA", vol. RAN WG1, no. Nanjing, China; 20160523 - 20160527, 14 May 2016 (2016-05-14), XP051096334, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_85/Docs/> [retrieved on 20160514] *

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019192622A1 (fr) * 2018-04-06 2019-10-10 Mediatek Inc. Conception d'entrelacement pour un fonctionnement dans un spectre sans licence en nouvelle radio
TWI746958B (zh) * 2018-04-06 2021-11-21 聯發科技股份有限公司 用於新無線電未授權頻譜操作的交錯設計
WO2019216702A1 (fr) * 2018-05-10 2019-11-14 엘지전자 주식회사 Procédé de transmission de préambule prach dans un système de communication sans fil à l'aide d'une bande sans licence et appareil correspondant
WO2020030263A1 (fr) * 2018-08-08 2020-02-13 Huawei Technologies Co., Ltd. Dispositifs, procédés et programmes informatiques pour économiser des ressources de fréquence dans les communications sans fil
US11950214B2 (en) 2018-08-08 2024-04-02 Huawei Technologies Co., Ltd. Devices, methods and computer programs for saving frequency resources in wireless communications
US20200068625A1 (en) * 2018-08-21 2020-02-27 Qualcomm Incorporated Interlace prach design in nr-u
WO2020040933A1 (fr) * 2018-08-21 2020-02-27 Qualcomm Incorporated Conception de prach d'entrelacement dans un nr-u
US11917697B2 (en) * 2018-08-21 2024-02-27 Qualcomm Incorporated Interlace PRACH design in NR-U
WO2020067696A1 (fr) 2018-09-26 2020-04-02 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception d'un signal dans un système de communication sans fil
US11968713B2 (en) 2018-09-26 2024-04-23 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving signal in wireless communication system
CN112868266A (zh) * 2018-09-26 2021-05-28 华为技术有限公司 用于发送和接收随机接入前导的客户端设备和网络接入节点
US11805554B2 (en) 2018-09-26 2023-10-31 Huawei Technologies Co., Ltd. Client device and network access node for transmitting and receiving a random access preamble
CN112868266B (zh) * 2018-09-26 2023-03-28 华为技术有限公司 用于发送和接收随机接入前导的客户端设备和网络接入节点
EP3841819A4 (fr) * 2018-09-26 2021-12-08 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception d'un signal dans un système de communication sans fil
US20210307075A1 (en) * 2018-11-01 2021-09-30 Panasonic Intellectual Property Corporation Of America Transmission device, reception device, transmission method, and reception method
CN111181885A (zh) * 2018-11-13 2020-05-19 中国科学院上海高等研究院 超高速移动宽带通信中前导信号的发送方法与接收方法
CN111181885B (zh) * 2018-11-13 2022-09-09 中国科学院上海高等研究院 超高速移动宽带通信中前导信号的发送方法与接收方法
CN113303024B (zh) * 2019-01-09 2022-09-16 华为技术有限公司 用于发送和接收随机接入前导码的客户端设备和网络接入节点
CN113303024A (zh) * 2019-01-09 2021-08-24 华为技术有限公司 用于发送和接收随机接入前导码的客户端设备和网络接入节点
US11956107B2 (en) 2019-01-09 2024-04-09 Huawei Technologies Co., Ltd. Client device and network access node for transmitting and receiving a random access preamble
WO2020143907A1 (fr) * 2019-01-09 2020-07-16 Huawei Technologies Co., Ltd. Dispositif client et nœud d'accès au réseau permettant de transmettre et de recevoir un préambule d'accès aléatoire
CN112399546A (zh) * 2019-08-12 2021-02-23 华为技术有限公司 公共定时提前的指示方法、装置、设备及存储介质
US11627604B2 (en) 2019-10-04 2023-04-11 Lg Electronics Inc. Method for transmitting and receiving signal in wireless communication system, and device supporting same
US11729822B2 (en) 2019-10-04 2023-08-15 Lg Electronics Inc. Method for transmitting and receiving signal in wireless communication system, and device supporting same
WO2021066590A1 (fr) * 2019-10-04 2021-04-08 엘지전자 주식회사 Procédé pour la transmission et la réception d'un signal dans un système de communication sans fil, et dispositif prenant en charge le procédé
WO2021147898A1 (fr) * 2020-01-23 2021-07-29 中国移动通信有限公司研究院 Procédé de détermination de rythme d'émission en liaison montante, terminal et station de base

Similar Documents

Publication Publication Date Title
US11659592B2 (en) Contention window adjustment mechanisms for FELAA systems
US10873969B2 (en) Beam management for carrier aggregation (CA)
US11956169B2 (en) Anchor channel design for unlicensed internet of things (IoT)
US10912150B2 (en) Anchor channel design for unlicensed Internet of Things (IoT)
WO2018045247A1 (fr) Conception de canal d&#39;accès aléatoire physique (prach) pour porteuses sans licence en lte
US11063652B2 (en) Techniques for improved beam management
EP3619940B1 (fr) Conception de motifs d&#39;intervalle pour des systèmes de nouvelle radio (nr)
EP3635906A1 (fr) Système et procédé de multiplexage de signal de référence de suivi de phase (pt-rs)
US11070407B2 (en) Partial uplink subframe transmissions on unlicensed carriers
US20210135803A1 (en) Radio (nr) unlicensed physical uplink control channel with interlaced structure
US20210219166A1 (en) Channel quality measurement reporting
WO2018165202A1 (fr) Surveillance de canaux de commande dans des ensembles de ressources de commande pour une nouvelle technologie radio
US10979099B2 (en) Detection of hopping channel for unlicensed internet of things
US20190239286A1 (en) Common and user equipment (ue)-specific physical uplink control channel (pucch) configuration
WO2018106658A1 (fr) Systèmes et procédés d&#39;accès à un canal dans un environnement multefire
US11044660B2 (en) System information block (SIB) transmission for wide coverage enhancement (WCE)
WO2017197086A1 (fr) Activation de commutation sur la base de porteuse composante de signal de référence de sondage dans une communication sans fil
WO2018106841A1 (fr) Conception de signaux de référence de découverte
US20220060905A1 (en) Unlicensed narrowband internet of things (nb-iot) operation on band 47b
WO2018144642A1 (fr) Structure de trame pour un internet des objets sans licence
WO2017173154A1 (fr) Évitement d&#39;interférence pour signaux de référence de faisceau
US20200137788A1 (en) Method and apparatus for communication in lte system on unlicensed spectrum
WO2018085043A1 (fr) Procédé et appareil de transmission uci autonome

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: 17765034

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17765034

Country of ref document: EP

Kind code of ref document: A1