WO2019032676A1 - Communication de canal de commande de l'internet des objets à bande étroite sans licence - Google Patents

Communication de canal de commande de l'internet des objets à bande étroite sans licence Download PDF

Info

Publication number
WO2019032676A1
WO2019032676A1 PCT/US2018/045761 US2018045761W WO2019032676A1 WO 2019032676 A1 WO2019032676 A1 WO 2019032676A1 US 2018045761 W US2018045761 W US 2018045761W WO 2019032676 A1 WO2019032676 A1 WO 2019032676A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
circuitry
unlicensed spectrum
baseband apparatus
channel
Prior art date
Application number
PCT/US2018/045761
Other languages
English (en)
Inventor
Wenting CHANG
Huaning Niu
Salvatore TALARICO
Qiaoyang Ye
Yu HUAI
Original Assignee
Intel IP 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 IP Corporation filed Critical Intel IP Corporation
Publication of WO2019032676A1 publication Critical patent/WO2019032676A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0072—Error control for data other than payload data, e.g. control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the third-generation partnership project (3 GPP) has standardized two designs to support internet of things (IoT) services - enhanced Machine Type Communication (eMTC) and NarrowBand IoT (NB-IoT).
  • IoT internet of things
  • eMTC enhanced Machine Type Communication
  • NB-IoT NarrowBand IoT
  • eMTC and NB-IoT user equipments (UEs) are expected to be deployed in huge numbers, lowering the cost of these UEs may help enable further implementation of IoT.
  • low power consumption is desirable to extend the life time of the battery.
  • LTE long-term evolution
  • eMTC, and NB-IoT techniques are designed to ensure that the UEs have low cost, low power consumption, and enhanced coverage.
  • the devices may be considered to be divergent.
  • some devices may have a cost limitation and have a correspondingly lower data rate or latency parameters.
  • Other devices may have a relatively high data rate requirement with tolerable cost consideration.
  • IoT Internet of Thing
  • Figure 1 depicts a demodulation reference signal (DMRS) pattern that may be used for a narrowband physical downlink shared channel (NPDSCH) transmission, in accordance with various embodiments.
  • Figure 2 depicts an example of channel timing relationships, in accordance with various embodiments.
  • DMRS demodulation reference signal
  • NPDSCH narrowband physical downlink shared channel
  • Figure 3 depicts an alternative example of channel timing relationships, in accordance with various embodiments.
  • Figure 4 depicts an alternative example of channel timing relationships, in accordance with various embodiments.
  • Figure 5 depicts an alternative example of channel timing relationships, in accordance with various embodiments.
  • Figure 6 illustrates an architecture of a system of a network in accordance with some embodiments.
  • Figure 7 illustrates an architecture of a system of a network in accordance with some embodiments.
  • FIG. 8 illustrates an example of infrastructure equipment in accordance with various embodiments.
  • Figure 9 illustrates an example of a platform in accordance with various
  • FIG. 10 illustrates example components of baseband circuitry and radio front end modules (RFEM) in accordance with some embodiments.
  • RFEM radio front end modules
  • FIG. 11 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • Figure 12 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • Coupled may mean one or more of the following. “Coupled” may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements indirectly contact each other, but yet still cooperate or interact with each other, and may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or elements are in direct contact.
  • the phrase "a first feature formed, deposited, or otherwise disposed on a second feature,” may mean that the first feature is formed, deposited, or disposed over the feature layer, and at least a part of the first feature may be in direct contact (e.g., direct physical or electrical contact) or indirect contact (e.g., having one or more other features between the first feature and the second feature) with at least a part of the second feature.
  • direct contact e.g., direct physical or electrical contact
  • indirect contact e.g., having one or more other features between the first feature and the second feature
  • module may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, or other suitable components that provide the described functionality.
  • ASIC application specific integrated circuit
  • processor shared, dedicated, or group
  • memory shared, dedicated, or group
  • industrial IoT applications may include devices with divergent requirements.
  • a unified downlink shared channel in the unlicensed hybrid system may be desired.
  • Such a unified downlink shared channel may be able to efficiently satisfy the parameters of both eMTC and NB-IOT in the unlicensed spectrum.
  • the unlicensed spectrum may refer to a spectrum with subcarriers that have a sub-gigahertz (GHz) frequency.
  • embodiments herein may describe the unified downlink shared channel, which may be the NPDSCH, and aspects thereof.
  • the aspects of the NPDSCH may include, for example, configurations of elements such as resource unit (RUs), resource mapping, the DMRS pattern, channel hopping, hybrid automatic repeat request (HARQ) number, channel quality indicator (CQI) table, etc.
  • RUs resource unit
  • HARQ hybrid automatic repeat request
  • CQI channel quality indicator
  • the resource unit may be defined for the NPDSCH.
  • the RU may contain one RB in the frequency domain, and one subframe in the time domain.
  • the transport block (TB) size for the NPDSCH may be derived based on factors such as RU number or modulation coding scheme (MCS) index, as discussed below.
  • MCS modulation coding scheme
  • the UE may have a "narrow bandwidth capability.” That is, in embodiments the UE may be configured to communicate using a channel that only includes a single RB in the frequency domain.
  • “narrow bandwidth capability” may refer to a communication scheme wherein the UE communicates using frequency of less than 1 GHz.
  • multiple RUs may span into the time domain. That is, for a UE with narrow bandwidth capability, the same information may be repeated in time over multiple subframes, instead of spanning on multiple physical resource blocks (PRBs).
  • PRBs physical resource blocks
  • the RU number may reuse numbering of the legacy B-IOT system, i.e. ⁇ 1,2,3,4,5,6,8, 10 ⁇ .
  • the UE may have a "wide bandwidth capability.” That is, in embodiments the UE may be configured to communicate using a channel that includes more than one RB in the frequency domain. For example, the channel may include up to 6 RBs in the frequency domain. More generally, for a UE with wide bandwidth capability, multiple RUs can span into both time domain and frequency domain.
  • the RU mapping may be performed first in the frequency domain and secondly in the time domain. In other embodiments, the RU mapping may be performed first in the time domain and secondly in the frequency domain. More specifically, the UE may identify an RU mapping as described above. In other embodiments, the mapping sequence may be configured by the base station through high layer signaling. That is, in embodiments, the base station may transmit one or more signals that includes information in a layer such as the radio resource control (RRC) layer that indicates the RU mapping that the UE should use.
  • RRC radio resource control
  • the RU mapping in the frequency domain may include one or more parameters such as a starting RB or carrier index, or an ending RB or carrier index. These parameters may be pre-defined by the base station, configured by the base station through higher layer signaling, or dynamically configured through a downlink control information (DCI) transmission received from the base station.
  • DCI downlink control information
  • the number of allocated RUs may vary in the frequency domain, while the time domain resource is predefined to be 1 millisecond (ms).
  • one domain (i.e., frequency or time domain) resource may be predefined, for example by a 3GPP specification or previously identified by a network administrator or operator, or it may be configured by higher layer signaling.
  • the number of Rus may be variable and may be indicated by DCI.
  • two resource allocation factors may be used to indicate the number of RUs in the frequency domain and the number of subframes in the frequency domain.
  • Other embodiments may have other variations of how resources may be allocated in the time or frequency domain. Repetition times
  • the repetition factor used for the PDSCH transmission may be ⁇ 1, 2, 4, 8, 16, 32, 64, 128, 192, 256, 384, 512, 768, 1024, 1536, 2048 ⁇ .
  • the higher repetition factors i.e., 128 and above
  • the repetition factor used for the NPDSCH transmission may have a maximum value of 64.
  • the repetition factor may be explicitly indicated by DCI.
  • a maximum value is may be configured through RRC signaling, and a fraction factor ⁇ 1, 1/2, 1/4, 1/8, 1/16, 1/32, 1/64, 1/127 ⁇ may be indicated through a DCI transmission which may be applied to the maximum value to provide the repetition factor to be used.
  • Transport block size (TBS)
  • the maximum TBS may be pre-defined, or may be reported by the UE.
  • the maximum TBS for a UE with narrow bandwidth capability and the maximum TBS for a UE with wide bandwidth capability may be equal to 2546 bits.
  • different UEs may still indicate their TBS capacity to a base station, and the TBS index for different UEs with different capacity may be altered to have different restrictions.
  • a UE with narrow bandwidth capability may use two types of TBS capacity, namely 680 bits and 2536 bits.
  • the UE with wide bandwidth capability may have three types of TBS capacity, namely 1000 bits, 2536 bits, and 4008 bits. In these
  • the UE may be configured to indicate to the base station which TBS capacity they are configured to use.
  • separate TBSs may be defined for UEs with different capability.
  • a UE with a 680-bit maximum TBS may be configured to use a Rel-13 TBS table to select a TBS, while a UE with a maximum 2536 bits TBS may be configured to reuse the Rel-14 TBS table to select a TBS.
  • which TBS table is to be used by the UE may be configured by higher layer signaling. That is, the TBS used may be selected by min ⁇ indicated TBS by reading from the TBS table, max TBS supported by the UE ⁇ .
  • a unified TBS table may be utilized for UEs with different bandwidth capability.
  • Table 1 provides an example table where 4 bits (ITBS) may be used to indicate the TBS and three bits (NRU) may be used to indicate the RU to be used in the NPDSCH transmission. Based on those two values, the TBS to be used for the NPDSCH may be identified. According to different UE capability, the MCS index may be restricted. Alternatively, the TBS can be determined by min ⁇ indicated TBS by reading from Table 1, max TBS supported by the UE ⁇ . In Table 1, the darker shading may indicate values that may be unu
  • DMRS Demodulation Reference Signal
  • the DMRS for the NPDSCH may use the DMRS pattern illustrated in Figure 1.
  • Figure 1 depicts a subframe 100.
  • the subframe 100 may include a number of RUs 105. More specifically, the RUs 105 may be organized along the frequency domain F, one RU per subcarrier, for a total of 12 subcarriers in the frequency domain. Similarly, the RUs 105 may be organized along the time domain T, one RU per orthogonal frequency division multiplexed (OFDM) symbol, for a total of 14 OFDM symbols in the time domain.
  • the subframe 100 may have a number of reference signals 110 and 115.
  • the reference signals 110 and 115 may be at the sixth, seventh, thirteenth, and fourteenth OFDM symbols in the time domain, and the third, sixth, ninth, and twelfth subcarriers in the frequency domain.
  • one or both of the reference signals 110 and 115 may be the DMRS.
  • the NPDSCH may reuse the legacy cell-specific reference signal (CRS) pattern, wherein the reference signals are on the same subcarriers, but are in the first, fifth, eighth, and twelfth OFDM symbols in the time domain.
  • CRS cell-specific reference signal
  • HARQ Hybrid Automatic Repeat Request
  • the number of HARQ processes that a UE may support may be reported by UE.
  • the maximum HARQ processes numbers can be chose from ⁇ 1, 2 ⁇ .
  • the maximum HARQ process number may be 2.
  • the maximum HARQ processes number may be chosen from ⁇ 1,2,8, 6, 9, 10, 11, 12, 14, 16 ⁇ .
  • the HARQ processes number for a UE may be associated with the UE's bandwidth capability. Specifically, for a UE with narrow bandwidth capability, the HARQ processes capability may be either 1 or 2 by default. For a UE with wide bandwidth capability, the HARQ process capability may be 8.
  • x subframes may have RU-level repetition, where x can be a pre- defined value such as 4 or some other value. In other embodiments, x may be associated with the repetition times, e.g. min ⁇ 4, Nrep ⁇ .
  • the RU, and particularly the RU after subjected to a scrambling process may be repeated in the adjacent subframes.
  • the channel coding may use tail biting convolutional coding (TBCC) or turbo coding.
  • TBCC and turbo coding may be supported, and the specific channel coding type may be based on a factor such as the UE's TBS capacity, bandwidth capability, or UE selection.
  • one or multiple transmission modes e.g. TM1, TM2, TM6, or TM9, may be supported.
  • multiple repetitions of a NPDSCH RU may be transmitted within one specific channel, and the remaining part beyond that one specific channel may be dropped.
  • multiple NPDSCH RU repetition may be spanned to multiple channels.
  • the UE may be configured to detect whether the next new channel is acquired or not through CRS or presence signaling, and then continue to receive the NPDSCH based on that detection.
  • a specific UE category may be introduced.
  • the category may include one or more of the following features: TBS capability, e.g. ⁇ 680, 1000, 2536, 4008 ⁇
  • Bandwidth capability e.g. ⁇ 1RB, 6RB ⁇
  • Channel coding capability e.g. ⁇ TBCC, Turbo Coding
  • Quadrature Phase Shift Keying (QPSK)-only e.g. ⁇ Quadrature Phase Shift Keying (QPSK)-only
  • NPUSCH Narrowband Physical Uplink Shared Channel
  • the physical shared channel design for the unlicensed spectrum may need to be changed.
  • Embodiments herein may describe various aspects of a NPUSCH design for the unlicensed spectrum, including elements such as: numerology and mapping of RUs, modulation order, channel coding and repetitions cycles, number of repetitions, transport block size, HARQ processes, DMRS design, frequency hopping, power control, UL gap compensation and related timing relationship, etc.
  • a UE with narrow band capabilities may support RUs with tones or subcarriers spacings as follows. It will be understood that the following examples are intended as examples of various embodiments, and other embodiments may use RUs in accordance with other parameters:
  • multiple RUs may span into the time domain.
  • a data transmission may be performed by occupying one PRB, and that transmission may span into multiple time resources.
  • only multi-tone transmission may be supported.
  • single-tone and multi-tone transmission may be supported, but only 15 KHz subcarrier spacing is supported. In other words, in this embodiment both single-tone and multi-tone transmission may be supported, but the 3.75 KHz subcarrier spacing may not be supported.
  • both 15 KHz and 3.75 KHz subcarrier spacing may be supported.
  • only multi-tone transmission may be supported, and the numerology used may be similar to that of legacy licensed B-IoT.
  • the numerology used may be similar to that of legacy licensed B-IoT.
  • only one RB configuration for PUSCH may be configured, similarly to the configuration used for PDSCH.
  • NPUSCH transmission with 6 tones and 12 tones may be supported.
  • NPUSCH with 3, 6 and 12 tones may be supported.
  • Other embodiments may support different numbers of tones.
  • a UE with wide band capabilities may support RUs with tones or subcarriers spacings as follows. It will be understood that the following examples are intended as examples of various embodiments, and other embodiments may use RUs in accordance with other parameters:
  • the number of allocated RUs may always span in one
  • the resources in time domain may be limited by 1ms.
  • “span” may refer to "occupying.”
  • "spanning" in one domain may mean that a data transmission may occupy multiple PRBs and be transmitted in one subframe (i.e., spanning in the frequency domain), or the data transmission may occupy one PRB and be transmitted in multiple subframes (i.e., spanning in the time domain).
  • multiple RUs can span in both the time domain and the frequency domain.
  • the specific configuration of the RUs may be fixed or pre- configured, dynamically defined through higher layer signaling, or indicated through DCI.
  • multiple RUs can be mapped in time domain first, and then in frequency domain. o In some embodiments, multiple RUs can be mapped in frequency domain first, and then in time domain.
  • the RB index, carrier index, or subcarrier index for the mapping in frequency domain may be pre-defined, configured by higher layer signaling, or configured through DCI.
  • the PUSCH is transmitted over only 12 subcarriers or only 6 subcarriers.
  • a UE with wideband capability may only supports PUSCH transmissions in units of PRBs.
  • sub-PRB allocation may be supported, e.g. 1, 3, or 6-tone allocation may be supported.
  • tone and “subcarrier” may be used interchangeably unless explicitly indicated otherwise.
  • sub-PRB allocation may be configured by higher layer signaling.
  • DCI resource allocation field and MCS fields received by the UE in the higher layer signaling may need to be interpreted correspondingly.
  • DCI may be used to dynamically schedule the resource allocation in unit of subcarrier or PRB. This scheduling may require an increased DCI size as compared to legacy NB-IoT operation, or some limit in terms of resource allocation flexibility to keep the DCI size small.
  • different modulation techniques or orders may be adopted for UEs with different capabilities.
  • single-tone may not be supported, and only QPSK may be supported.
  • QPSK may be supported in order to increase spectral efficiency.
  • a higher order modulation may be supported (i.e., 16 QAM and/or 64QAM).
  • QPSK and 16-QAM may be supported.
  • single-tone transmission may be supported, and pi/2 BPSK and pi/2 QPSK are supported.
  • RV cycling may be supported to boost performance through additional coding gain.
  • RV cycling may refer to a situation wherein RV cycling is performed across a given repetition cycle when the NPUSCH is transmitted with repetitions.
  • each subframe or narrowband slot in the allocated resources may be repeated consecutively for Z times.
  • single- tone transmission may be supported and the RV may be repeated only once.
  • Z may equal 1, 4, or min ⁇ 4, repetition/2 ⁇ . Scrambling may be applied in each cycle, where the first RV can be pre- defined, configured by the base station through high layer signaling, or indicated through DCI.
  • the RV sequence may be ⁇ 0,2 ⁇ .
  • Z may be 1, 4, or 5, scrambling may be applied at each cycle, and RV cycling may be supported across NPUSCH repetitions.
  • the RV sequence may be ⁇ 0,2,3,1.
  • the initial RV for narrowband UE or wideband UE may be predefined, indicated by higher layer signaling, or dynamically indicated via DCI.
  • scrambling may be applied for Z subframes before changing the scrambling sequence. Number of Repetitions
  • the number of repetitions may be chosen among the set ⁇ 1, 2, 4, 8, 16, 32, 64, 128 ⁇ . In one embodiment, for UE with wideband capabilities the set of repetitions may be chosen from the set ⁇ 1, 2, 4, 8, 16, 32, 64, 128, 192, 256, 384, 512, 768, 1024, 1536, 2048 ⁇ . In some embodiments, regardless of the UE capability, the set of number of repetitions may be ⁇ 1, 2, 4, 8, 16, 32, 64, 128, 192, 256, 384, 512, 768, 1024, 1536, 2048 ⁇ .
  • the number of repetitions may be explicitly indicated through DCI, or through higher layer signaling. In other embodiments, some subset of the allowed number of repetitions may be formed and chosen through system information block (SIB) signaling together with DCI.
  • SIB system information block
  • the set of candidate repetitions is configured by higher layer signaling
  • the set of repetitions for msg3 may be cell specific, while the set of repetitions for other NPUSCH may be cell specific or UE specific.
  • Transport Block Size (TBS)
  • a predefined maximum TBS may be used for the NPUSCH, whether the UE has narrowband or wideband capabilities. In one embodiment, the maximum TBS may be 2546 bits or 2984 bits.
  • a unified TBS table may be formed as that of Table 3.
  • TBS TBS values higher than the
  • TBS may be bounded to the maximum TBS supported.
  • UEs with different capabilities may support a different maximum TBS.
  • a UE with narrowband capability may support a maximum TBS equal to 1000 and 2536.
  • a UE with wideband capabilities may support a maximum TBS equal to 1000, 2536, 2984, and 6968.
  • separate TBS tables may be defined for UEs with different capabilities.
  • the Rel-13 TBS table may be used for a UE with a maximum TBS equal to 1000
  • the Rel- 14 TBS table may be used for UE with maximum supported TBS equal to 2536.
  • the entries larger than the maximum TBS supported may be bounded by it.
  • a unified TBS table may be used (e.g., Table 3), and according to the maximum TBS supported the entries that have higher TBS values than its maximum supported value may be bounded by it. Additionally, the MCS indexes may be restricted.
  • the maximum number of HARQ processes may be either 1 or 2. In one embodiment, for a UE with wideband capabilities, the maximum number of HARQ processes may be chosen among the set ⁇ 1, 2, 3, 4, 6, 7, 8 ⁇ . In one embodiment, the number of HARQ processes may be related to the UE bandwidth capabilities: for instance, for a UE with narrowband capabilities, the HARQ processes may be either 1, 2 or 8 by default, and for a UE with wideband capabilities, the HARQ processes may be 8 by default. In one embodiment, asynchronous and adaptive HARQ may be supported for PUSCH, for both narrowband UE and wideband UE.
  • DMRS 15 KHz and 3.75 KHz subcarrier spacing
  • the length of DMRS for multi-tone transmission may be the same as the number of tones used: i) x-tone DMRS for x-tone NPUSCH.
  • a new DMRS base sequence with length-6 and length-3 may be respectively used for 6-tone and 3-tone transmission.
  • the DMRS base sequences may be based on computer generated QPSK symbols mapped directly in the frequency domain.
  • the number of base sequences may be 12; while for 6-tones and 12-tones it may be 14 and 30, respectively.
  • CSs cyclic shifts
  • the DMRS density and location may be as follows:
  • DMRS symbol per NB-slot may be located in the 5th symbol of every 7 symbols in a 2ms long NB- slot.
  • a DMRS base sequence with length- 16 may be used.
  • the DMRS may be constructed by a pseudo-number (PN)/Gold-sequence (not physical cell identifier (PCID)-dependent) and a Hadamard sequence that is PCID-dependent.
  • PN pseudo-number
  • PCID physical cell identifier
  • only 15 MHz subcarrier spacing may be supported for a UE with narrowband capabilities.
  • only multi-tone transmission may be supported, and the DMRS may be as described above for the single-tone transmission.
  • the DMRS may be obtained by a shorter length Zadoff-Chu (ZC) sequence, or PN sequence, with cyclic shift or orthogonal cover code (OCC) applied to it.
  • ZC Zadoff-Chu
  • OCC orthogonal cover code
  • the DMRS may be formed and then truncated to accommodate different numbers of tones.
  • multi-tone transmissions may be supported, and the DMRS may be as described above.
  • the DMRS may occupy the center of the slot, in symbol 3 and 10.
  • frequency hopping may not be supported. In one embodiment, for a UE with narrowband capabilities, frequency hopping (FH) may not be supported. In one embodiment, for a UE with wideband capabilities, FH is used. In one embodiment, regardless of the UE capabilities, FH may be supported. When frequency hopping is applied, one of the following two options can be used:
  • multiple PUSCH RU repetitions may be transmitted within one specific channel, and the remaining part beyond that specific channel is dropped.
  • repetitions may be spanned to multiple channels, and an FH interval Ych may equal ⁇ 1, 2, 4, 8 ⁇ for FDD CE mode A and ⁇ 1, 5, 10, 20 ⁇ for TDD CE mode A. In other embodiments Ych may equal ⁇ 2, 4, 8, 16 ⁇ for FDD CE mode B and ⁇ 5, 10, 20, 40 ⁇ for TDD CE mode B.
  • the FH interval Y ch may be configured in a cell-specific manner.
  • FH may occur between a group of narrowbands, or some specific group of subcarriers or PRBs, where the number can be pre-defined or configured at the cell- specific level.
  • the FH may occur between 2 narrowbands.
  • the granularity can be scaled from narrowband to PRB or subcarrier, e.g. occur between 2 subcarriers or PRB for single tone transmission.
  • the first narrowband or subcarrier may be signaled through higher layer signaling or DCI.
  • the first narrowband or subcarrier may be signaled through higher layer signaling or DCI.
  • the first narrowband or subcarrier may be signaled through higher layer signaling or DCI.
  • narrowband/subcarrier/PRB may be pre-defined.
  • narrowbands/PRB/subcarriers may be determined according to a
  • the configurable offset which can be cell-specific or UE specific.
  • the offset can have granularity of 6 PRBs for wideband UE and 1 PRB for narrowband UE.
  • the narrowbands/PRB/subcarriers used by FH may be symmetric to the central frequency of the system bandwidth. In one embodiment the allocation of the narrowbands/PRB/subcarriers may not be symmetric to the central frequency of the system bandwidth. For 1-tone, 3-tone, and 6-tones transmission, the FH may occur within a specific PRB or multiple
  • FH may be turned ON or OFF via dedicated RRC signaling. In one embodiment, the FH may be turned ON and OFF dynamically through DCI signaling, if FH is enabled through higher-layer signaling. In one embodiment, for UE with wideband capabilities FH may always be used when NPUSCH is transmitted with repetitions. In alternative, FH may always be used when NPUSCH is transmitted with repetitions.
  • guard time for retuning when FH is used, retuning is enabled, and the following guard time for retuning can be used:
  • UE retunes from narrowband physical uplink control channel (NPUCCH) narrowband to NPUSCH narrowband: in this case, the first two symbols of the NPUSCH SF may be used as guard time
  • the affected NPUSCH symbols may be punctured.
  • the UE may transmit the NPUSCH with maximum power. If the UE with narrowband capabilities is using two or less repetitions, power control with no closed loop may be applied.
  • open power control may be used for NPUSCH transmissions to limit inter-cell interference.
  • the open power control may be configured for all or some NB-IoT UEs in the cell.
  • the maximum transmit power may be used to transmit the NPUSCH for deep coverage, otherwise power control with or without open loop may be applied.
  • power control with fractional path-loss compensation may be configured to limit inter-cell interference to neighboring cells.
  • full path loss compensation may always be applied when transmitting NPUSCH with repetitions.
  • the value of X and Y can be chosen differently, and for instance the gap may be chosen in order to accommodate for listen- before-talk (LBT) attempts, downlink requirements (i.e., discovery reference signal (DRS) or NPDCCH design, etc.), or some other parameter.
  • LBT listen- before-talk
  • DRS discovery reference signal
  • NPDCCH design etc.
  • the start of a downlink Acknowledgement (ACK)/Negative ACK (NACK) transmission may be greater than or equal to 3 ms later than the end of the corresponding
  • NPUSCH transmission as described in further detail below.
  • the start of a downlink transmission may be greater than or equal to 3 ms later than the end of any NPUSCH transmission for the same UE.
  • the uplink grant for NPUSCH scheduling may be indicated in the DCI format NO, together with the scheduling delay.
  • the fields indicated in the following Table 4 are included:
  • the above timing relationships may only be used for a UE with narrowband capabilities.
  • the scheduling delay may take into account all subframes, or only subframes designated for uplink transmissions.
  • some additional UE categories can be introduced, where one or more of the following features may be taken into account:
  • ⁇ TBS capability e.g. ⁇ 1000, 2536, 2984,4008 ⁇ .
  • BW capability e.g. ⁇ 1RB, 6RB ⁇ .
  • Modulation capability e.g. ⁇ QPSK-only, pi/2 BPSK, pi/2 QPSK, QPSK+16QAM, QPSK+64QAM ⁇ .
  • NB-IoT may be used in the unlicensed band to support these divergent devices with divergent service requirements.
  • the available time relationships may be different for UE with different capability. For instance, a UE with high power/capability may be able to receive narrowband PDCCH (NPDCCH) and NPDSCH transmissions at the same time, while a UE with low capability may first receive a NPDCCH transmission and then find the related timing/frequency position for the coming NPDSCH transmission.
  • NPDCCH narrowband PDCCH
  • a UE with low capability may first receive a NPDCCH transmission and then find the related timing/frequency position for the coming NPDSCH transmission.
  • transmission frame structure may be limited to the regulation. Due to the maximum usage (MU) limitation, the downlink subframe and uplink subframe may not be configured in a very flexible manner, e.g. 10 downlink subframes followed by 90 uplink subframes may be desired to achieve the 10% MU requirement.
  • Embodiments herein may relate to the timing relationship between NPDCCH and the corresponding data channel in unlicensed NB-IoT. More specifically, embodiments may relate to the timing relationship between the NPDCCH and the associated NPDSCH or NPUSCH. Other embodiments may relate to the timing reservation for downlink to uplink switching, and vice versa. Various embodiments may flexibly support different types of scheduling according to a given UE' s capability Timing/channel association between NPDCCH and the associated NPDSCH
  • the DCI may be carried on one or more subframes of the NPDCCH.
  • the starting subframe of NPDSCH that corresponds to the DCI may be x subframes later than the ending subframe of NPDCCH.
  • x may be larger than 0, pre-defined as 4, or configured by the base station through high layer signaling or DCI.
  • the scheduling delay is indicated by DCI
  • the starting of the NPDSCH transmission may be greater than or equal to 4 ms later than the end of its associated DL assignment.
  • x may be selected or reported by the UE based on its processing capability
  • the gap x (in terms of subframes or slots) between the ending subframe of NPDCCH and the starting subframe of NPDSCH may be equal to 0. More specifically, the NPDCCH and NPDSCH are transmitted at the same subframe in a frequency division multiplexed (FDMed) manner.
  • the resource block, subcarrier, or carrier index of the NPDSCH may be configured by the associated DCI. This configuration may be applicable to UEs near the base station, without or with small repetition times.
  • the gap x (in terms of subframes or slots) between the ending subframe of NPDCCH and the starting subframe of NPDSCH may be larger than 0.
  • x may be either a pre-defined number, e.g. 1, 2 or 4, or configured by the base station through high layer signaling or DCI.
  • the x subframe may be either x absolute subframe, or x valid downlink subframes, where the uplink subframes are precluded.
  • the NPDCCH and NPDSCH may be allocated at one specific channel before hopping to another channel. In one embodiment, the NPDCCH and NPDSCH may be allocated at different channels, where the channel for NPDSCH transmission may be configured by the base station through DCI. Alternatively, a mapping defining the channel for NPDSCH transmission from where the NPDCCH is sent may be predefined or configured by higher layer signaling.
  • the NPDSCH may be restricted to one channel, or spanned to multiple channels.
  • the gap x in terms of subframe or slots, between the ending subframe of NPDSCH and the ACK/NCK report may be larger than 0.
  • the gap x may be pre-defined as 4 or 12, or configured by the base station through high layer signaling or DCI. In other embodiments the gap x may be identified and reported to the base station by UE according to the processing capability of the UE.
  • the HARQ itself may be a bitmap which may be transmitted by the base station in a DL transmission corresponding to a time in which the NPDSCH is scheduled.
  • the ACK/NCK bit after the subframe identified by the gap x above may be viewed as a valid ACK/NCK report.
  • HARQ- ACK bundling when multiple ACK/NCK is scheduled to be sent on the same time, HARQ- ACK bundling may be used.
  • the NPDSCH and NPUCCH/NPUSCH carrying the ACK/NCK may be allocated at one specific channel before hopping to another channel.
  • the NPDSCH and NPUCCH/NPUSCH carrying the ACK/NCK may be allocated at different channels.
  • NPDSCH transmission may be configured by eNB through DCI, e.g., in terms of the offset from where the DCI or NPDSCH is sent.
  • a mapping defining the channel for ACK/NCK transmission from where the NPDSCH or DCI is sent may be predefined or configured by higher layer signaling.
  • Figure 2 depicts a transmission window 200 that may be arranged along both a frequency domain F and a time domain T.
  • the transmission window 200 may include downlink portions 205 and 215 that are reserved for downlink transmissions, that is transmissions from a base station such as an evolved NodeB (e B), a fifth generation (5G) e B, or some other base station to a UE.
  • the transmission window 200 may also include uplink portions 210 and 220 that are reserved for uplink transmissions from the UE to the base station.
  • Downlink portion 205 may include a PDCCH transmission 225.
  • the PDCCH transmission 225 may include information related to further transmissions, either uplink or downlink.
  • the NPDCCH transmission 225 may include DCI which may have parameters usable by the UE to identify further downlink transmissions, or some other parameter as described above.
  • Downlink portion 215 may include a NPDSCH transmission 230.
  • the NPDSCH transmission 230 may include data or information, and may be based on one or more parameters that are signaled by the NPDCCH transmission 225.
  • the uplink portion 220 may then include an ACK/NCK transmission 235, which may be transmitted by the UE to the base station and include a signal that indicates whether the NPDSCH transmission 230 was successfully received by the UE.
  • the various transmissions 225, 230, and 235 may all span the same subcarriers in the unlicensed frequency band. That is, each of the transmissions 225, 230, and 235 may be transmitted on the same subcarriers as one another using a frequency band that is less than 1 GHz.
  • the specific configuration of the transmission window 200 is only an example, and the relative proportions along the frequency domain F or time domain T of the portions 205, 210, 215, or 220, or the transmissions 225, 230, and 235, is intended as an illustrative example and is not intended to specifically identify relative lengths.
  • NPDCCH and NPDSCH may be transmitted at different channels as shown in Figure 3.
  • Figure 3 depicts two transmission windows 305 and 310, which may be organized along the frequency domain F and the time domain T.
  • the transmission window 305 may include a downlink portion 315 and an uplink portion 320, which may be respectively similar to downlink portion 205 and uplink portion 210 of Figure 2.
  • the transmission window 310 may additionally include a downlink portion 325 and an uplink portion 330, which may be respectively similar to downlink portion 215 and uplink portion 220.
  • the downlink portion 315 may include a PDCCH transmission 335, which may be similar to NPDCCH transmission 225.
  • the downlink portion 325 may include a NPDSCH transmission 340, which may be similar to NPDSCH transmission 230.
  • the uplink portion 330 may include an ACK/NCK transmission 345, which may be similar to ACK/NCK transmission 235.
  • transmission 335 may use a first set of subcarriers in the frequency domain F
  • the transmission window 310 that includes the NPDSCH transmission 340 and the ACK/NCK transmission 345 may use a second set of subcarriers in the frequency domain F.
  • the subcarriers of both the transmission window 305 and the transmission window 310 may be in the unlicensed spectrum, that is at frequency less than 1 GHz.
  • Figure 2 it will be understood that the specific configuration of Figure 3 is only an example, and the relative proportions along the frequency domain F or time domain T are not intended to specifically identify relative lengths. Additionally, Figure 3 is not intended to specify the specific locations of subcarriers. In other words, transmission window 310 may, in some
  • embodiments use subcarriers that are "higher” than the subcarriers used by transmission window 305, where "higher” is used in reference to the orientation depicted in Figure 3.
  • the downlink control information may be carried in NPDCCH on one or multiple subframes.
  • the starting subframe of the NPUSCH transmission that corresponds to the DCI may be x subframes later than the ending subframe of the NPDCCH transmission.
  • x may be larger than 0, e.g. pre-defined as 4 or 8, or configured by eNB through high layer signaling or DCI.
  • x may be identified or reported by UE according to the processing capability of the UE.
  • the number x may refer to all subframes (e.g., if x is equal to four, then four subframes regardless of whether they are uplink or downlink). In another embodiment, x may only refer to uplink subframes.
  • the NPDCCH and NPUSCH may both be transmitted on one channel before hopping to another channel.
  • the NPDCCH and NPUSCH may be transmitted on different channels, where the channel used for NPUSCH transmission may be configured by the base station through DCI.
  • a mapping defining the channel for NPUSCH transmission as the channel from which the DCI is transmitted i.e., the channel used for NPDCCH transmission
  • the NPUSCH itself may be restricted to one channel, or spanned to multiple channels.
  • Figure 4 depicts a scenario wherein the NPDCCH and the corresponding NPUSCH are transmitted within one channel.
  • Figure 4 depicts two transmission windows 405 and 410, which may be organized along the frequency domain F and the time domain T.
  • Transmission windows 405 and 410 may include downlink portions 415 and 425, respectively.
  • Transmission windows 405 and 410 may further include uplink portions 420 and 430.
  • the downlink portions 415 and 425 may be similar to downlink portions 205 or 215.
  • the uplink portions 420 and 430 may be similar to uplink portions 210 and 220.
  • Downlink portions 415 may include two NPDCCH transmissions 435 and 440.
  • the NPDCCH transmissions 435 or 440 may be similar, for example, to NPDCCH transmission 225.
  • the uplink portion 420 may include two NPUSCH transmissions 445 and 450.
  • NPUSCH transmission 445 may correspond to NPDCCH transmission 435
  • NPUSCH transmission 450 may correspond to NPDCCH transmission 440.
  • downlink portion 425 may include a single NPDCCH transmission 455
  • NPUSCH transmission 460 (which may also be similar, for example, to NPDCCH transmission 225) and a corresponding NPUSCH transmission 460.
  • a NPDCCH transmission and its corresponding NPUSCH transmission may be located on the same subcarriers in the frequency domain F.
  • the transmission windows 405 and 415 maybe in the unlicensed (that is, sub- 1 GHz) frequency bands.
  • transmission windows 405 and 410 are depicted as examples of transmission windows that may include a single NPDCCH/NPUSCH pair (e.g., transmission window 410) or a plurality of NPDCCH/NPUSCH pairs (e.g.,
  • transmission window 405) in the same transmission window.
  • both transmission windows 405 and 410 may not be transmitted or desired.
  • a transmission window may include additional NPDCCH/NPUSCH pairs. Other variations on the configuration of Figure 4 may be present in other embodiments.
  • the NPDCCH and NPUSCH may be located on different channels as depicted in Figure 5. Specifically, in some embodiments different channels may be desirable for edge users because there may not be enough subframes for both a NPDCCH and corresponding NPUSCH transmission in the same channel.
  • Figure 5 may depict two transmission windows 505 and 510, which respectively have uplink portions 515 and 525, and downlink portions 520 and 530.
  • Uplink portions 515 and 525 may be similar to uplink portions 415 and 425.
  • Downlink portions 520 and 530 may be similar to downlink portions 420 and 430.
  • the downlink portion 415 may include a NPDCCH transmission 435 on a first set of subcarriers in the frequency domain F.
  • the uplink portion 440 may include a corresponding NPUSCH transmission 440 on a different set of subcarriers in the frequency domain F.
  • Figures 2-4 it will be understood that the specific configuration of Figure 5 is only an example, and the relative proportions along the frequency domain F or time domain T are not intended to specifically identify relative lengths or locations of subcarriers.
  • x subframes may be reserved for switching from an uplink transmission to a downlink transmission such as a NPDCCH transmission or a NPDSCH transmission.
  • x may be equal to 0, 1, 3, or some other value.
  • x may be pre-defined, configured by the base station through high layer signaling or DCI, or identified/reported by the UE.
  • a UE may receive multiple DCIs in NPDCCH, and then perform the NPDSCH reception and NPUSCH transmission one by one.
  • the UE might receive a first DCI and perform the NPDSCH reception based on that first DCI.
  • the UE might then receive a second DCI and perform NPUSCH transmission based on that second DCI.
  • UE can receive one DCI, and perform the NPDSCH reception or NPUSCH transmission accordingly before it receives the next DCI.
  • the UE may identify, prepare, or send a report to the base station related to the soft buffer or processing capability of the UE. The base station may then identify how many DCIs should be transmitted and when based on the report.
  • Figure 6 illustrates an architecture of a system XQ00 of a network in accordance with some embodiments.
  • the system XQ00 is shown to include a user equipment (UE) XQ01 and a UE XQ02.
  • UE user equipment
  • UE may refer to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • user equipment or “UE” may be considered synonymous to, and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • user equipment or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • UEs XQ01 and XQ02 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, machine-type communications (MTC) devices, machine-to-machine (M2M), Internet of Things (IoT) devices, and
  • any of the UEs XQ01 and XQ02 can comprise an Internet 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
  • 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 XQ01 and XQ02 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) XQ10.
  • the RAN XQ10 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 XQ01 and XQ02 utilize connections (or channels) XQ03 and XQ04, respectively, each of which comprises a physical communications interface or layer (discussed in further detail infra).
  • connections or channels
  • XQ03 and XQ04 each of which comprises a physical communications interface or layer (discussed in further detail infra).
  • channel may refer to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to "communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is
  • the term "link” may refer to a connection between two devices through a Radio Access Technology (RAT) for the purpose of transmitting and receiving information.
  • RAT Radio Access Technology
  • the connections XQ03 and XQ04 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular
  • 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 XQ01 and XQ02 may further directly exchange communication data via a ProSe interface XQ05.
  • the ProSe interface XQ05 may
  • SL sidelink
  • SL sidelink
  • logical channels including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSCH Physical Sidelink Discovery Channel
  • V2X is a mode of communication where UEs (for example, UEs XQ01, XQ02) communicate with each other directly over the PC5/SL interface XQ05 and can take place when the UEs XQ01, XQ02 are served by RAN nodes XQl 1, XQ12 or when one or more UEs are outside a coverage area of the RAN XQ10.
  • UEs for example, UEs XQ01, XQ02
  • RAN nodes XQl 1, XQ12 when one or more UEs are outside a coverage area of the RAN XQ10.
  • V2X may be classified into four different types: vehicle-to-vehicle (V2V), vehicle-to- infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). These V2X applications can use "co-operative awareness" to provide more intelligent services for end- users.
  • vehicle UEs (vUEs) XQOl, XQ02, RAN nodes XQl 1, XQl 2, application servers XQ30, and pedestrian UEs XQOl, XQ02 may collect knowledge of their local environment (for example, information received from other vehicles or sensor equipment in proximity) to process and share that knowledge in order to provide more intelligent services, such as cooperative collision warning, autonomous driving, and the like.
  • V2V vehicle-to-vehicle
  • V2I vehicle-to- infrastructure
  • V2N vehicle-to-network
  • V2P vehicle-to-pedestrian
  • the UEs XQOl, XQ02 may be implemented/employed as Vehicle
  • VECS Embedded Communications Systems
  • vUEs vUEs
  • the UE XQ02 is shown to be configured to access an access point (AP) XQ06 (also referred to as "WLAN node XQ06", “WLAN XQ06", “WLAN Termination XQ06” or “WT XQ06” or the like) via connection XQ07.
  • the connection XQ07 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP XQ06 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP XQ06 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the UE XQ02, RAN XQ10, and AP XQ06 may be configured to utilize LTE-WLAN aggregation (LWA) operation and/or WLAN LTE/WLAN Radio Level Integration with IPsec Tunnel (LWIP) operation.
  • LWA operation may involve the UE XQ02 in RRC CONNECTED being configured by a RAN node XQl 1, XQl 2 to utilize radio resources of LTE and WLAN.
  • LWIP operation may involve the UE XQ02 using WLAN radio resources (e.g., connection XQ07) via Internet Protocol Security (IPsec) protocol tunneling to authenticate and encrypt packets (e.g., internet protocol (IP) packets) sent over the connection XQ07.
  • IPsec tunneling may include encapsulating entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
  • the RAN XQ10 can include one or more access nodes that enable the connections
  • access node may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users.
  • These access nodes can be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, Road Side Units (RSUs), 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).
  • BS base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RSUs Road Side Units
  • ground stations e.g., terrestrial access points
  • satellite stations providing coverage within a geographic area (e.g., a cell).
  • RSU may refer to any transportation infrastructure entity implemented in or by a gNB/eNB/RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU.”
  • the RAN XQ10 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node XQl 1, 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 XQ12.
  • LP low power
  • any of the RAN nodes XQl 1 and XQl 2 can terminate the air interface protocol and can be the first point of contact for the UEs XQ01 and XQ02.
  • any of the RAN nodes XQl 1 and XQl 2 can fulfill various logical functions for the RAN XQ10 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 XQ01 and XQ02 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM)
  • OFDM Orthogonal Frequency-Division Multiplexing
  • OFDMMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the UEs XQ01, XQ02 and the RAN nodes XQ11, XQ12 communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the "licensed spectrum” and/or the "licensed band") and an unlicensed shared medium (also referred to as the "unlicensed spectrum” and/or the "unlicensed band”).
  • the licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.
  • the UEs XQ01, XQ02 and the RAN nodes XQ11, XQ12 may operate using Licensed Assisted Access (LAA), enhanced LAA (eLAA), and/or further eLAA (feLAA) mechanisms.
  • LAA Licensed Assisted Access
  • eLAA enhanced LAA
  • feLAA further eLAA
  • the UEs XQ01, XQ02 and the RAN nodes XQ11, XQ12 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum.
  • the medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • LBT is a mechanism whereby equipment (for example, UEs XQ01, XQ02, RAN nodes XQ11, XQ12, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied).
  • the medium sensing operation may include clear channel assessment (CCA), which utilizes at least energy detection (ED) to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear.
  • CCA clear channel assessment
  • ED energy detection
  • This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks.
  • ED may include sensing radiofrequency (RF) energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.
  • RF radiofrequency
  • WLAN employs a contention-based channel access mechanism, called carrier sense multiple access with collision avoidance (CSMA/CA).
  • CSMA/CA carrier sense multiple access with collision avoidance
  • a WLAN node e.g., a mobile station (MS) such as UE XQ01 or XQ02, AP 106, or the like
  • MS mobile station
  • AP 106 e.g., AP 106, or the like
  • a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time.
  • the backoff mechanism may be a counter that is drawn randomly within the contention window size (CWS), which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds.
  • CWS contention window size
  • the LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL
  • transmission bursts including PDSCH or PUSCH transmissions, respectively may have an LAA contention window that is variable in length between X and Y extended CCA (ECCA) slots, where X and Y are minimum and maximum values for the CWSs for LAA.
  • ECCA extended CCA
  • the minimum CWS for an LAA transmission may be 9 microseconds ( ⁇ ); however, the size of the CWS and a maximum channel occupancy time (MCOT) (for example, a transmission burst) may be based on governmental regulatory requirements.
  • MCOT maximum channel occupancy time
  • each aggregated carrier is referred to as a component carrier (CC).
  • a CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz.
  • FDD Frequency Division Duplexing
  • the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers.
  • individual CCs can have a different bandwidth than other CCs.
  • TDD Time Division Duplexing
  • CA also comprises individual serving cells to provide individual CCs.
  • the coverage of the serving cells may differ, for example, due to that CCs on different frequency bands will experience different pathloss.
  • a primary service cell or primary cell may provide a Primary CC (PCC) for both UL and DL, and may handle Radio Resource Control (RRC) and Non-Access Stratum (NAS) related activities.
  • the other serving cells are referred to as secondary cells (SCells), and each SCell may provide an individual Secondary CC (SCC) for both UL and DL.
  • the SCCs may be added and removed as required, while changing the PCC may require the UE XQOl, XQ02 to undergo a handover.
  • LAA SCells may operate in the unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by a PCell operating in the licensed spectrum.
  • LAA SCells When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different Physical Uplink Shared Channel (PUSCH) starting positions within a same subframe.
  • PUSCH Physical Uplink Shared Channel
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs XQOl and XQ02.
  • the physical downlink control channel may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs XQOl and XQ02 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 XQ02 within a cell) may be performed at any of the RAN nodes XQ11 and XQ12 based on channel quality information fed back from any of the UEs XQ01 and XQ02.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs XQ01 and XQ02.
  • 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. For example, 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 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 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 XQ10 is shown to be communicatively coupled to a core network (CN)
  • the CN XQ20 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 XQ13 is split into two parts: the Sl-U interface XQ14, which carries traffic data between the RAN nodes XQ11 and XQ12 and the serving gateway (S-GW) XQ22, and the S 1 -mobility management entity (MME) interface XQ 15, which is a signaling interface between the RAN nodes XQ11 and XQ12 and MMEs XQ21.
  • MME S 1 -mobility management entity
  • the CN XQ20 comprises the MMEs XQ21, the S-GW XQ22, the Packet Data Network (PDN) Gateway (P-GW) XQ23, and a home subscriber server (HSS) XQ24.
  • the MMEs XQ21 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 XQ21 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS XQ24 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN XQ20 may comprise one or several HSSs XQ24, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS XQ24 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW XQ22 may terminate the SI interface XQ13 towards the RAN XQ10, and routes data packets between the RAN XQ10 and the CN XQ20.
  • the S-GW XQ22 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 XQ23 may terminate an SGi interface toward a PDN.
  • the P-GW XQ23 may route data packets between the EPC network XQ20 and external networks such as a network including the application server XQ30 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface XQ25.
  • the application server XQ30 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 XQ23 is shown to be communicatively coupled to an application server XQ30 via an IP communications interface XQ25.
  • the application server XQ30 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 XQ01 and XQ02 via the CN XQ20.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW XQ23 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) XQ26 is the policy and charging control element of the CN XQ20.
  • PCRF Policy and Charging Rules 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 XQ26 may be communicatively coupled to the application server XQ30 via the P-GW XQ23.
  • the application server XQ30 may signal the PCRF XQ26 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF XQ26 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 XQ30.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 7 illustrates an architecture of a system XR00 of a network in accordance with some embodiments.
  • the system XR00 is shown to include a UE XROl, which may be the same or similar to UEs XQ01 and XQ02 discussed previously; a RAN node XRl 1, which may be the same or similar to RAN nodes XQ11 and XQ12 discussed previously; a Data Network (DN) XR03, which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC or CN) XR20.
  • DN Data Network
  • the CN XR20 may include an Authentication Server Function (AUSF) XR22; an Access and Mobility Management Function (AMF) XR21; a Session Management Function (SMF) XR24; a Network Exposure Function (NEF) XR23; a Policy Control Function (PCF) XR26; a Network Function (NF) Repository Function (NRF) XR25; a Unified Data
  • AUSF Authentication Server Function
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • NEF Network Exposure Function
  • PCF Policy Control Function
  • NF Network Function
  • UDM User Plane Management
  • AF Application Function
  • UPF User Plane Function
  • NSSF Network Slice Selection Function
  • the UPF XR02 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN XR03, and a branching point to support multi-homed PDU session.
  • the UPF XR02 may also perform packet routing and forwarding, perform packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection), traffic usage reporting, perform QoS handling for user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering.
  • UP collection packet inspection
  • QoS handling for user plane e.g., packet filtering, gating, UL/DL rate enforcement
  • Uplink Traffic verification e.g., SDF to QoS flow mapping
  • transport level packet marking in the uplink and downlink e.g., SDF to Qo
  • UPF XR02 may include an uplink classifier to support routing traffic flows to a data network.
  • the DN XR03 may represent various network operator services, Internet access, or third party services.
  • DN XR03 may include, or be similar to, application server XQ30 discussed previously.
  • the UPF XR02 may interact with the SMF XR24 via an N4 reference point between the SMF XR24 and the UPF XR02.
  • the AUSF XR22 may store data for authentication of UE XROl and handle authentication related functionality.
  • the AUSF XR22 may facilitate a common authentication framework for various access types.
  • the AUSF XR22 may communicate with the AMF XR21 via an N12 reference point between the AMF XR21 and the AUSF XR22; and may communicate with the UDM XR27 via an N13 reference point between the UDM XR27 and the AUSF XR22. Additionally, the AUSF XR22 may exhibit an Nausf service-based interface.
  • the AMF XR21 may be responsible for registration management (e.g., for registering UE XROl, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF XR21 may be a termination point for an Nl 1 reference point between the AMF XR21 and the SMF XR24.
  • the AMF XR21 may provide transport for Session Management (SM) messages between the UE XROl and the SMF XR24, and act as a transparent proxy for routing SM messages.
  • AMF XR21 may also provide transport for short message service (SMS) messages between UE XROl and an SMS function (SMSF) (not shown by Figure 7).
  • SMS short message service
  • AMF XR21 may act as Security Anchor Function (SEAF), which may include interaction with the AUSF XR22 and the UE XROl, as well as receipt of an intermediate key that was established as a result of the UE XROl authentication process. Where UMTS Subscriber Identity Module (USFM) based authentication is used, the AMF XR21 may retrieve the security material from the AUSF XR22. AMF XR21 may also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys.
  • SEAF Security Anchor Function
  • SCM Security Context Management
  • AMF XR21 may be a termination point of RAN CP interface, which may include or be an N2 reference point between the (R)AN XRl 1 and the AMF XR21; and the AMF XR21 may be a termination point of NAS (Nl) signalling, and perform NAS ciphering and integrity protection.
  • AMF XR21 may also support NAS signalling with a UE XROl over an N3 interworking-function (IWF) interface.
  • the N3IWF may be used to provide access to untrusted entities.
  • N3IWF may be a termination point for the N2 interface between the (R)AN XRl 1 and the AMF XR21 for the control plane, and may be a termination point for the N3 reference point between the (R)AN XRl 1 and the UPF XR02 for the user plane.
  • the AMF XR21 may handle N2 signalling from the SMF XR24 and the AMF XR21 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking, which may take into account QoS requirements associated to such marking received over N2.
  • N3TvVF may also relay uplink and downlink control-plane NAS signalling between the UE XROl and AMF XR21 via an Nl reference point between the UE XROl and the AMF XR21, and relay uplink and downlink user-plane packets between the UE XROl and UPF XR02.
  • the N3IWF also provides mechanisms for IPsec tunnel establishment with the UE XROl .
  • the AMF XR21 may exhibit an Namf service-based interface, and may be a termination point for an N14 reference point between two AMFs XR21 and an N17 reference point between the AMF XR21 and a 5G-Equipment Identity Register (5G-EIR) (not shown by Figure 7).
  • 5G-EIR 5G-Equipment Identity Register
  • the SMF XR24 may be responsible for session management (e.g., session
  • the SMF XR24 may also allocate and manage UE IP addresses (including optional authorization), select and control UP functions, and configures traffic steering at the UPF XR02 to route traffic to a proper destination.
  • the SMF XR24 may also terminate interfaces towards Policy Control Functions, control part of policy enforcement and QoS, and perform lawful interception (e.g., for SM events and interface to LI system).
  • the SMF XR24 may also terminate SM parts of NAS messages, provide downlink data notification, and initiate AN specific SM information, sent via AMF over N2 to AN, and determine Session and Service Continuity (SSC) mode of a session.
  • SSC Session and Service Continuity
  • the SMF XR24 may include the following roaming functionality: handle local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); and support for interaction with external DN for transport of signalling for PDU session authorization/authentication by external DN.
  • An N16 reference point between two SMFs XR24 may be included in the system XR00, which may be between another SMF XR24 in a visited network and the SMF XR24 in the home network in roaming scenarios. Additionally, the SMF XR24 may exhibit the Nsmf service-based interface.
  • the NEF XR23 may provide means for securely exposing the services and
  • the NEF XR23 may authenticate, authorize, and/or throttle the AFs. NEF XR23 may also translate information exchanged with the AF XR28 and
  • the NEF XR23 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF XR23 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF XR23 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re- exposed by the NEF XR23 to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF XR23 may exhibit an Nnef service-based interface.
  • NFs network functions
  • the RF XR25 may support service discovery functions, receive F Discovery Requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF XR25 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate”, “instantiation”, and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF XR25 may exhibit the Nnrf service-based interface.
  • the PCF XR26 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF XR26 may also implement a front end (FE) to access subscription information relevant for policy decisions in a Unified Data Repository (UDR) of the UDM XR27.
  • the PCF XR26 may communicate with the AMF XR21 via an N15 reference point between the PCF XR26 and the AMF XR21, which may include a PCF XR26 in a visited network and the AMF XR21 in case of roaming scenarios.
  • the PCF XR26 may communicate with the AF XR28 via an N5 reference point between the PCF XR26 and the AF XR28; and with the SMF XR24 via an N7 reference point between the PCF XR26 and the SMF XR24.
  • the system XR00 and/or CN XR20 may also include an N24 reference point between the PCF XR26 (in the home network) and a PCF XR26 in a visited network. Additionally, the PCF XR26 may exhibit an Npcf service-based interface.
  • the UDM XR27 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE XR01. For example, subscription data may be communicated between the UDM XR27 and the AMF XR21 via an N8 reference point between the UDM XR27 and the AMF XR21 (not shown by Figure 7).
  • the UDM XR27 may include two parts, an application FE and a User Data Repository (UDR) (the FE and UDR are not shown by Figure 7).
  • the UDR may store subscription data and policy data for the UDM XR27 and the PCF XR26, and/or structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, application request information for multiple UEs XROl) for the NEF XR23.
  • the Nudr service-based interface may be exhibited by the UDR to allow the UDM XR27, PCF XR26, and NEF XR23 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM XR27 may include a UDM FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identification handling; access authorization; registration/mobility management; and subscription management.
  • the UDR may interact with the SMF XR24 via an N10 reference point between the UDM XR27 and the SMF XR24.
  • UDM XR27 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM XR27 may exhibit the Nudm service-based interface.
  • the AF XR28 may provide application influence on traffic routing, provide access to the Network Capability Exposure (NCE), and interact with the policy framework for policy control.
  • the NCE may be a mechanism that allows the 5GC and AF XR28 to provide information to each other via NEF XR23, which may be used for edge computing implementations.
  • the network operator and third party services may be hosted close to the UE XR01 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
  • the 5GC may select a UPF XR02 close to the UE XR01 and execute traffic steering from the UPF XR02 to DN XR03 via the N6 interface.
  • the AF XR28 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF XR28 to interact directly with relevant NFs. Additionally, the AF XR28 may exhibit an Naf service-based interface.
  • the NSSF XR29 may select a set of network slice instances serving the UE XR01.
  • the NSSF XR29 may also determine allowed Network Slice Selection Assistance
  • the NSSF XR29 may also determine the AMF set to be used to serve the UE XR01, or a list of candidate AMF(s) XR21 based on a suitable configuration and possibly by querying the NRF XR25.
  • the selection of a set of network slice instances for the UE XR01 may be triggered by the AMF XR21 with which the UE XR01 is registered by interacting with the NSSF XR29, which may lead to a change of AMF XR21.
  • the NSSF XR29 may interact with the AMF XR21 via an N22 reference point between AMF XR21 and NS SF XR29; and may communicate with another NSSF XR29 in a visited network via an N31 reference point (not shown by Figure 7). Additionally, the NSSF XR29 may exhibit an Nnssf service-based interface. As discussed previously, the CN XR20 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE XR01 to/from other entities, such as an Short Message Service (SMS)-Global Systems for Mobile Communication (GMSC)/Inter-Working Mobile Switching Center (IWMSCySMS-router.
  • SMS Short Message Service
  • GMSC Global Systems for Mobile Communication
  • IWMSCySMS-router Inter-Working Mobile Switching Center
  • the SMS may also interact with AMF XR21 and UDM XR27 for notification procedure that the UE XR01 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM XR27 when UE XR01 is available for SMS).
  • AMF XR21 and UDM XR27 for notification procedure that the UE XR01 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM XR27 when UE XR01 is available for SMS).
  • the CN XR20 may also include other elements that are not shown by Figure 7, such as a Data Storage system/architecture, a 5G-Equipment Identity Register (5G-EIR), a Security Edge Protection Proxy (SEPP), and the like.
  • the Data Storage system may include a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and/or the like.
  • SDSF Structured Data Storage network function
  • UDSF Unstructured Data Storage network function
  • Any NF may store and retrieve unstructured data into/from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by Figure 7).
  • Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs.
  • the UDSF may exhibit an Nudsf service-based interface (not shown by Figure 7).
  • the 5G-EIR may be an NF
  • the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.
  • the CN XR20 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME XQ21) and the AMF XR21 in order to enable interworking between CN XR20 and CN XQ20.
  • MME Mobility Management Entity
  • AMF XR21 AMF XR21
  • Other example interfaces/reference points may include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between an NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.
  • system XR00 may include multiple RAN nodes XR11 wherein an Xn interface is defined between two or more RAN nodes XRl 1 (e.g., gNBs and the like) connecting to 5GC XR20, between a RAN node XRl 1 (e.g., gNB) connecting to 5GC XR20 and an eNB (e.g., a RAN node XQ11 of Figure 6), and/or between two eNBs connecting to 5GC XR20.
  • the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface.
  • the Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality.
  • the Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; and mobility support for UE XR01 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes XR11.
  • the mobility support may include context transfer from an old (source) serving RAN node XRl 1 to new (target) serving RAN node XRl 1 ; and control of user plane tunnels between old (source) serving RAN node XRl 1 to new (target) serving RAN node XRl 1.
  • a protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs.
  • IP Internet Protocol
  • the Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn
  • Xn-AP Application Protocol
  • SCTP layer may be on top of an IP layer.
  • the SCTP layer provides the guaranteed delivery of application layer messages.
  • point-to-point transmission is used to deliver the signaling PDUs.
  • the Xn-U protocol stack and/or the Xn-C protocol stack may be the same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.
  • FIG 8 illustrates an example of infrastructure equipment XS00 in accordance with various embodiments.
  • the infrastructure equipment XS00 (or "system XS00") may be implemented as a base station, radio head, RAN node, etc., such as the RAN nodes XQl 1 and XQ12, and/or AP XQ06 shown and described previously.
  • the system XS00 could be implemented in or by a UE, application server(s) XQ30, and/or any other element/device discussed herein.
  • the system XS00 may include one or more of application circuitry XS05, baseband circuitry XS10, one or more radio front end modules XS15, memory XS20, power management integrated circuitry (PMIC) XS25, power tee circuitry XS30, network controller XS35, network interface connector XS40, satellite positioning circuitry XS45, and user interface XS50.
  • the device XT00 may include 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).
  • circuitry may refer to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (for example, a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable System on Chip (SoC)), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • SoC programmable System on Chip
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term "circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry may refer to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations; and recording, storing, and/or transferring digital data.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad- core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.
  • CPU central processing unit
  • network elements may describe a physical or virtualized equipment used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, radio access network device, gateway, server, virtualized network function (VNF), network functions virtualization infrastructure ( FVI), and/or the like.
  • VNF virtualized network function
  • FVI network functions virtualization infrastructure
  • Application circuitry XS05 may include one or more central processing unit (CPU) cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD/)MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • CPU central processing unit
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as SPI, I2C or universal programmable serial interface module
  • RTC real time clock
  • timer-counters including interval and watchdog timers
  • I/O or IO general purpose input/output
  • memory card controllers such as Secure Digital (SD/)MultiMediaCard
  • the application circuitry XS05 may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; and/or the like.
  • the system XS00 may not utilize application circuitry XS05, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.
  • application circuitry XS05 may include circuitry such as, but not limited to, one or more field-programmable devices (FPDs) such as field- programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.
  • FPDs field-programmable devices
  • FPGAs field- programmable gate arrays
  • PLDs programmable logic devices
  • ASICs such as structured ASICs and the like
  • PSoCs programmable SoCs
  • the circuitry of application circuitry XS05 may comprise logic blocks or logic fabric including other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein.
  • the circuitry of application circuitry XS05 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in lookup-tables (LUTs) and the like.
  • memory cells e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)
  • SRAM static random access memory
  • LUTs lookup-tables
  • the baseband circuitry XS10 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • baseband circuitry XS10 may comprise one or more digital baseband systems, which may be coupled via an interconnect subsystem to a CPU subsystem, an audio subsystem, and an interface subsystem.
  • the digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband sub-system via another interconnect subsystem.
  • Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein.
  • the audio sub-system may include digital signal processing circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital- to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components.
  • baseband circuitry XS10 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (for example, the radio front end modules XS15).
  • User interface circuitry XS50 may include one or more user interfaces designed to enable user interaction with the system XS00 or peripheral component interfaces designed to enable peripheral component interaction with the system XS00.
  • User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, etc.
  • Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.
  • USB universal serial bus
  • the radio front end modules (RFEMs) XS15 may comprise a millimeter wave RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs).
  • the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM.
  • the RFICs may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas.
  • both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module XS15.
  • the RFEMs XS15 may incorporate both millimeter wave antennas and sub-millimeter wave antennas.
  • the memory circuitry XS20 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresi stive random access memory (MRAM), etc., and may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • Memory circuitry XS20 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.
  • the PMIC XS25 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor.
  • the power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions.
  • the power tee circuitry XS30 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment XS00 using a single cable.
  • the network controller circuitry XS35 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol.
  • Network connectivity may be provided to/from the infrastructure equipment XS00 via network interface connector XS40 using a physical connection, which may be electrical (commonly referred to as a "copper interconnect"), optical, or wireless.
  • the network controller circuitry XS35 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocol.
  • the network controller circuitry XS35 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
  • the positioning circuitry XS45 may include circuitry to receive and decode signals transmitted by one or more navigation satellite constellations of a global navigation satellite system (GNSS).
  • GNSS global navigation satellite system
  • Examples of navigation satellite constellations (or GNSS) may include United States' Global Positioning System (GPS), Russia's Global Navigation System
  • the positioning circuitry XS45 may comprise various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate the communications over-the-air (OTA) communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes.
  • OTA over-the-air
  • GNSS nodes may provide positioning services by continuously transmitting or broadcasting GNSS signals along a line of sight, which may be used by GNSS receivers (e.g., positioning circuitry XS45 and/or positioning circuitry implemented by UEs XQOl, XQ02, or the like) to determine their GNSS position.
  • the GNSS signals may include a pseudorandom code (e.g., a sequence of ones and zeros) that is known to the GNSS receiver and a message that includes a time of transmission (ToT) of a code epoch (e.g., a defined point in the pseudorandom code sequence) and the GNSS node position at the ToT.
  • the GNSS receivers may include a pseudorandom code (e.g., a sequence of ones and zeros) that is known to the GNSS receiver and a message that includes a time of transmission (ToT) of a code epoch (e.g., a defined point in the pseudoran
  • the positioning circuitry XS45 may include a Micro- Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance.
  • Micro-PNT Micro- Technology for Positioning, Navigation, and Timing
  • the GNSS receivers may measure the time of arrivals (To As) of the GNSS signals from the plurality of GNSS nodes according to its own clock.
  • the GNSS receivers may determine time of flight (ToF) values for each received GNSS signal from the To As and the ToTs, and then may determine, from the ToFs, a three-dimensional (3D) position and clock deviation.
  • the 3D position may then be converted into a latitude, longitude and altitude.
  • the positioning circuitry XS45 may provide data to application circuitry XS05, which may include one or more of position data or time data.
  • Application circuitry XS05 may use the time data to synchronize operations with other radio base stations (e.g., RAN nodes XQ11, XQ12, XR11 or the like).
  • interface circuitry may refer to, is part of, or includes circuitry providing for the exchange of information between two or more
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, input/output (I/O) interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • Any suitable bus technology may be used in various implementations, which may include any number of technologies, including industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies.
  • ISA industry standard architecture
  • EISA extended ISA
  • PCI peripheral component interconnect
  • PCIx peripheral component interconnect extended
  • PCIe PCI express
  • the bus may be a proprietary bus, for example, used in a SoC based system.
  • Other bus systems may be included, such as an I2C interface, an SPI interface, point to point interfaces, and a power bus, among others.
  • Figure 9 illustrates an example of a platform XTOO (or "device XTOO") in accordance with various embodiments.
  • the computer platform XTOO may be suitable for use as UEs XQ01, XQ02, XR01, application servers XQ30, and/or any other element/device discussed herein.
  • the platform XTOO may include any combinations of the components shown in the example.
  • the components of platform XTOO may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform XT00, or as components otherwise incorporated within a chassis of a larger system.
  • the block diagram of FigurelO is intended to show a high level view of components of the computer platform XT00. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.
  • the application circuitry XT05 may include circuitry such as, but not limited to single-core or multi-core processors and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as serial peripheral interface (SPI), inter-integrated circuit (I2C) or universal programmable serial interface circuit, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input-output (10), memory card controllers such as secure digital / multi-media card
  • the processor(s) may include any combination of general-purpose processors and/or dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors (or cores) 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 platform XTOO.
  • processors of application circuitry XS05/XT05 may process IP data packets received from an EPC or 5GC.
  • Application circuitry XT05 may be or may include a microprocessor, a multi-core processor, a multithreaded processor, an ultra-low voltage processor, an embedded processor, or other known processing element.
  • the application circuitry XT05 may include an Intel® Architecture CoreTM based processor, such as a QuarkTM, an AtomTM, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel®
  • the processors of the application circuitry XT05 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., QualcommTM processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia
  • OMAP Applications Platform
  • the application circuitry XT05 may be a part of a system on a chip (SoC) in which the application circuitry XT05 and other components are formed into a single integrated circuit, or a single package, such as the EdisonTM or GalileoTM SoC boards from Intel® Corporation.
  • SoC system on a chip
  • application circuitry XT05 may include circuitry such as, but not limited to, one or more field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.
  • FPDs field-programmable devices
  • PLDs programmable logic devices
  • CPLDs complex PLDs
  • HPLDs high-capacity PLDs
  • PSoCs programmable SoCs
  • the circuitry of application circuitry XT05 may comprise logic blocks or logic fabric including other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein.
  • the circuitry of application circuitry XT05 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in lookup-tables (LUTs) and the like.
  • memory cells e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)
  • SRAM static random access memory
  • LUTs lookup-tables
  • the baseband circuitry XT 10 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • baseband circuitry XT10 may comprise one or more digital baseband systems, which may be coupled via an interconnect subsystem to a CPU subsystem, an audio subsystem, and an interface subsystem.
  • the digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband sub-system via another interconnect subsystem.
  • Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein.
  • the audio sub-system may include digital signal processing circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital- to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components.
  • baseband circuitry XT 10 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (for example, the radio front end modules XT 15).
  • the radio front end modules (RFEMs) XT15 may comprise a millimeter wave RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs).
  • the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM.
  • the RFICs may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas.
  • both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module XT15.
  • the RFEMs XT 15 may incorporate both millimeter wave antennas and sub-millimeter wave antennas.
  • the memory circuitry XT20 may include any number and type of memory devices used to provide for a given amount of system memory.
  • the memory circuitry XT20 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM),
  • RAM random access memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • NVM nonvolatile memory
  • Flash memory commonly referred to as Flash memory
  • PRAM phase change random access memory
  • the memory circuitry XT20 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like.
  • Memory circuitry XT20 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DFMMs) including microDFMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA).
  • JEDEC Joint Electron Devices Engineering Council
  • LPDDR low power double data rate
  • SDP single die package
  • DDP dual die package
  • Q17P quad die package
  • DFMMs dual inline memory modules
  • BGA ball grid array
  • the memory circuitry XT20 may be on-die memory or registers associated with the application circuitry XT05.
  • memory circuitry XT20 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others.
  • SSDD solid state disk drive
  • HDD hard disk drive
  • micro HDD micro HDD
  • resistance change memories phase change memories
  • phase change memories phase change memories
  • holographic memories holographic memories
  • chemical memories among others.
  • the computer platform XT00 may incorporate the three-dimensional (3D) cross- point (XPOF T) memories from Intel® and Micron®.
  • Removable memory circuitry XT23 may include devices, circuitry,
  • portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.
  • flash memory cards e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like
  • USB flash drives e.g., USB drives, optical discs, external HDDs, and the like.
  • the platform XT00 may also include interface circuitry (not shown) that is used to connect external devices with the platform XT00.
  • the external devices connected to the platform XTOO via the interface circuitry may include sensors XT21, such as accelerometers, level sensors, flow sensors, temperature sensors, pressure sensors, barometric pressure sensors, and the like.
  • the interface circuitry may be used to connect the platform XTOO to electro-mechanical components (EMCs) XT22, which may allow platform XTOO to change its state, position, and/or orientation, or move or control a mechanism or system.
  • EMCs electro-mechanical components
  • the EMCs XT22 may include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components.
  • EMRs electromechanical relays
  • SSRs solid state relays
  • actuators e.g., valve actuators, etc.
  • an audible sound generator e.g., a visual warning device
  • motors e.g., DC motors, stepper motors, etc.
  • wheels thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components.
  • platform XTOO may be configured to operate one or more EMCs XT22 based on one or more captured events and/or instructions or
  • the interface circuitry may connect the platform XTOO with positioning circuitry XT45, which may be the same or similar as the positioning circuitry XS45 discussed with regard to Figure 8.
  • the interface circuitry may connect the platform XTOO with near-field communication (NFC) circuitry XT40, which may include an NFC controller coupled with an antenna element and a processing device.
  • NFC circuitry XT40 may be configured to read electronic tags and/or connect with another NFC-enabled device.
  • the driver circuitry XT46 may include software and hardware elements that operate to control particular devices that are embedded in the platform XTOO, attached to the platform XTOO, or otherwise communicatively coupled with the platform XTOO.
  • the driver circuitry XT46 may include individual drivers allowing other components of the platform XTOO to interact or control various input/output (I/O) devices that may be present within, or connected to, the platform XTOO.
  • I/O input/output
  • driver circuitry XT46 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform XTOO, sensor drivers to obtain sensor readings of sensors XT21 and control and allow access to sensors XT21, EMC drivers to obtain actuator positions of the EMCs XT22 and/or control and allow access to the EMCs XT22, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
  • a display driver to control and allow access to a display device
  • a touchscreen driver to control and allow access to a touchscreen interface of the platform XTOO
  • sensor drivers to obtain sensor readings of sensors XT21 and control and allow access to sensors XT21
  • EMC drivers to obtain actuator positions of the EMCs XT22 and/or control and allow access to the EMCs XT22
  • a camera driver to control and allow access to an embedded image capture device
  • audio drivers
  • the power management integrated circuitry (PMIC) XT25 may manage power provided to various components of the platform XTOO.
  • the PMIC XT25 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMIC XT25 may often be included when the platform XT00 is capable of being powered by a battery XT30, for example, when the device is included in a UE XQ01, XQ02, XR01.
  • the PMIC XT25 may control, or otherwise be part of, various power saving mechanisms of the platform XT00. For example, if the platform XT00 is in an RRC Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform XT00 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform XT00 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • DRX Discontinuous Reception Mode
  • the platform XT00 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the platform XT00 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • a battery XT30 may power the platform XT00, although in some examples the platform XT00 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid.
  • the battery XT30 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery XT30 may be a typical lead-acid automotive battery.
  • the battery XT30 may be a "smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry.
  • BMS Battery Management System
  • the BMS may be included in the platform XT00 to track the state of charge (SoCh) of the battery XT30.
  • SoCh state of charge
  • the BMS may be used to monitor other parameters of the battery XT30 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery XT30.
  • the BMS may communicate the information of the battery XT30 to the application circuitry XT05 or other components of the platform XT00.
  • the BMS may also include an analog-to-digital (ADC) converter that allows the application circuitry XT05 to directly monitor the voltage of the battery XT30 or the current flow from the battery XT30.
  • ADC analog-to-digital
  • the battery parameters may be used to determine actions that the platform XT00 may perform, such as transmission frequency, network operation, sensing frequency, and the like.
  • a power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery XT30.
  • the power block XQ28 may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform XT00.
  • a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery XT30, and thus, the current required.
  • the charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard, promulgated by the Alliance for Wireless Power, among others.
  • a suitable bus technology may include any number of technologies, including industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), a Time-Trigger Protocol (TTP) system, or a FlexRay system, or any number of other technologies.
  • the bus may be a proprietary bus, for example, used in a SoC based system.
  • Other bus systems may be included, such as an I2C interface, an SPI interface, point to point interfaces, and a power bus, among others.
  • FIG. 10 illustrates example components of baseband circuitry XS10/XT10 and radio front end modules (RFEM) XS15/XT15 in accordance with some embodiments.
  • the RFEM XS15/XT15 may include Radio Frequency (RF) circuitry XT06, front-end module (FEM) circuitry XT08, one or more antennas XT 10 coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the baseband circuitry XS10/XT10 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry XS10/XT10 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry XT06 and to generate baseband signals for a transmit signal path of the RF circuitry XT06.
  • Baseband processing circuitry XS10/XT10 may interface with the application circuitry XS05/XT05 for generation and processing of the baseband signals and for controlling operations of the RF circuitry XT06.
  • the baseband circuitry XS10/XT10 may include a third generation (3G) baseband processor XT04A, a fourth generation (4G) baseband processor XT04B, a fifth generation (5G) baseband processor XT04C, or other baseband processor(s) XT04D 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 XS10/XT10 (e.g., one or more of baseband processors XT04A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry XT06.
  • baseband processors XT04A-D may be included in modules stored in the memory XT04G and executed via a Central Processing Unit (CPU) XT04E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry XS10/XT10 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry XS10/XT10 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 XS10/XT10 may include one or more audio digital signal processor(s) (DSP) XT04F.
  • the audio DSP(s) XT04F 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 XS10/XT10 and the application circuitry XS05/XT05 may be implemented together such as, for example, on a system on a chip (SoC).
  • SoC system on a chip
  • the baseband circuitry XS10/XT10 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry XS10/XT10 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 XS10/XT10 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry XT06 may enable communication with wireless networks
  • the RF circuitry XT06 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry XT06 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry XT08 and provide baseband signals to the baseband circuitry XS10/XT10.
  • RF circuitry XT06 may also include a transmit signal path which may include circuitry to up- convert baseband signals provided by the baseband circuitry XS10/XT10 and provide RF output signals to the FEM circuitry XT08 for transmission.
  • the receive signal path of the RF circuitry XT06 may include mixer circuitry XT06a, amplifier circuitry XT06b and filter circuitry XT06c.
  • the transmit signal path of the RF circuitry XT06 may include filter circuitry XT06c and mixer circuitry XT06a.
  • RF circuitry XT06 may also include synthesizer circuitry XT06d for synthesizing a frequency for use by the mixer circuitry XT06a of the receive signal path and the transmit signal path.
  • the mixer circuitry XT06a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry XT08 based on the synthesized frequency provided by synthesizer circuitry XT06d.
  • the amplifier circuitry XT06b may be configured to amplify the down-converted signals and the filter circuitry XT06c 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.
  • LPF low-pass filter
  • BPF band-pass filter
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry XT06a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry XT06a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry XT06d to generate RF output signals for the FEM circuitry XT08.
  • the baseband signals may be provided by the baseband circuitry XS10/XT10 and may be filtered by filter circuitry XT06c.
  • the mixer circuitry XT06a of the receive signal path and the mixer circuitry XT06a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry XT06a of the receive signal path and the mixer circuitry XT06a 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 XT06a of the receive signal path and the mixer circuitry XT06a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry XT06a of the receive signal path and the mixer circuitry XT06a 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 XT06 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry XS10/XT10 may include a digital baseband interface to communicate with the RF circuitry XT06.
  • 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 XT06d 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 XT06d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry XT06d may be configured to synthesize an output frequency for use by the mixer circuitry XT06a of the RF circuitry XT06 based on a frequency input and a divider control input.
  • the synthesizer circuitry XT06d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry XS10/XT10 or the applications processor XS05/XT05 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 XS05/XT05.
  • Synthesizer circuitry XT06d of the RF circuitry XT06 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 (DP A).
  • 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 XT06d 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 XT06 may include an IQ/polar converter.
  • FEM circuitry XT08 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas XT 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry XT06 for further processing.
  • FEM circuitry XT08 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry XT06 for transmission by one or more of the one or more antennas XT10.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry XT06, solely in the FEM XT08, or in both the RF circuitry XT06 and the FEM XT08.
  • the FEM circuitry XT08 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 XT06).
  • the transmit signal path of the FEM circuitry XT08 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry XT06), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas XT10).
  • PA power amplifier
  • Processors of the application circuitry XS05/XT05 and processors of the baseband circuitry XS10/XT10 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry XS10/XT10 alone or in
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • 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. 11 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry XS10/XT10 of FIGS. XS- XT1 may comprise processors XT04A-XT04E and a memory XT04G utilized by said processors.
  • Each of the processors XT04A-XT04E may include a memory interface, XU04A- XU04E, respectively, to send/receive data to/from the memory XT04G.
  • the baseband circuitry XS10/XT10 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface XU12 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry
  • an application circuitry interface XU14 e.g., an interface to send/receive data to/from the application circuitry XS05/XT05 of FIGS. XS-XT1
  • an RF circuitry interface XU16 e.g., an interface to send/receive data to/from RF circuitry XT06 of Figure 10
  • a wireless hardware connectivity interface XU18 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 Wi-Fi® components
  • Figure 12 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 12 shows a diagrammatic representation of hardware resources XZ00 including one or more processors (or processor cores) XZ10, one or more memory/storage devices XZ20, and one or more communication resources XZ30, each of which may be communicatively coupled via a bus XZ40.
  • computing resource may refer to a physical or virtual device, a physical or virtual component within a computing environment, and/or physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time and/or processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, and/or the like.
  • node virtualization e.g., FV
  • a hypervisor XZ02 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources XZ00.
  • a "virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • the processors XZ10 may include, for example, a processor XZ12 and a processor XZ14.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices XZ20 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices XZ20 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources XZ30 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices XZ04 or one or more databases XZ06 via a network XZ08.
  • the communication resources XZ30 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • the term “network resource” or “communication resource” may refer to computing resources that are accessible by computer devices via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • Instructions XZ50 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors XZ10 to perform any one or more of the methodologies discussed herein.
  • the instructions XZ50 may reside, completely or partially, within at least one of the processors XZ10 (e.g., within the processor's cache memory), the memory/storage devices XZ20, or any suitable combination thereof.
  • any portion of the instructions XZ50 may be transferred to the hardware resources XZ00 from any combination of the peripheral devices XZ04 or the databases XZ06. Accordingly, the memory of processors XZ10, the memory/storage devices XZ20, the peripheral devices XZ04, and the databases XZ06 are examples of computer- readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 includes a method of transmitting a downlink (DL) transmission related to narrowband internet of things (NB-IoT) operation in an unlicensed spectrum, the method comprising: identifying, by a base station, a DL resource unit (RU) that includes only one resource block (RB) in the frequency domain and only one subframe in the time domain, wherein the RB includes a plurality of subcarriers in the unlicensed spectrum; and transmitting, by the base station on the DL RU, the DL transmission related to NB-IoT operation in the unlicensed spectrum.
  • DL downlink
  • NB-IoT narrowband internet of things
  • Example 2 includes the method of example 1, wherein the DL transmission is a narrowband physical DL shared channel (NPDSCH) transmission.
  • NPDSCH narrowband physical DL shared channel
  • Example 3 includes the method of examples 1, 2, or some other example herein, wherein the plurality of subcarriers includes 12 subcarriers.
  • Example 4 includes the method of examples 1, 2, or some other example herein, wherein the RB includes 14 orthogonal frequency division multiplexed (OFDM) symbols.
  • Example 5 includes the method of examples 1, 2, or some other example herein, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • GHz gigahertz
  • Example 6 includes the method of examples 1, 2, or some other example herein, wherein the DL transmission has a repetition value of less than 128.
  • Example 7 includes the method of example 6, further comprising transmitting, by the base station through radio resource control (RRC) signaling, an indication of a maximum value of the repetition value.
  • RRC radio resource control
  • Example 8 includes the method of examples 1, 2, or some other example herein, further comprising: identifying, by the base station, a maximum number of bits in a transport block size (TBS) usable by a user equipment (UE); identifying, by the base station based on the maximum number of bits, a TBS table; and generating, by the base station based on the TBS table, the DL transmission.
  • TBS transport block size
  • Example 9 includes the method of example 8, wherein the maximum number of bits is 680 and the TBS table is a third generation partnership project (3GPP) release-13 (Rel-13) TBS table.
  • 3GPP third generation partnership project
  • Example 10 includes the method of example 8, wherein the maximum number of bits is 2536 and the TBS table is a third generation partnership project (3GPP) release-14 (Rel-14) TBS table.
  • 3GPP third generation partnership project
  • Example 11 includes the method of examples 1, 2, or some other example herein, wherein the DL RU includes a plurality of demodulation reference signals (DMRSs) that have a pattern based on a third generation partnership project (3 GPP) release-14 (Rel-14) DMRS pattern.
  • DMRSs demodulation reference signals
  • 3 GPP third generation partnership project
  • Rel-14 release-14
  • Example 12 includes the method of examples 1, 2, or some other example herein, further comprising supporting, by the base station, a first hybrid automatic repeat request (HARQ) process related to the DL transmission and a second HARQ process related to the DL transmission, wherein the first HARQ process and the second HARQ process are concurrent.
  • HARQ hybrid automatic repeat request
  • Example 13 includes the method of example 12, further comprising identifying, by the base station, an indication from a user equipment (UE) related to the UE's capability to support the first HARQ process and the second HARQ process.
  • Example 14 includes the method of examples 1, 2, or some other example herein, further comprising generating the DL transmission based on use of a tail-biting convolutional code (TBCC).
  • TBCC tail-biting convolutional code
  • Example 15 includes the method of examples 1, 2, or some other example herein, further comprising transmitting the DL transmission in accordance with a third generation partnership project (3GPP) transmission mode 1 (TM1), transmission mode 2 (TM2), transmission mode 6 (TM6), or transmission mode 9 (TM9).
  • 3GPP third generation partnership project
  • Example 16 includes the method of examples 1, 2, or some other example herein, wherein transmission of the DL transmission occurs on a first channel and further comprising re-transmitting the DL transmission on a second channel different than the first channel.
  • Example 17 includes the method of examples 1, 2, or some other example herein, wherein transmitting the DL transmission includes transmitting, by the base station, the DL transmission on a single channel without the use of frequency hopping.
  • Example 18 includes a method of transmitting an uplink (UL) transmission related to narrowband internet of things (NB-IoT) operation in an unlicensed spectrum, the method comprising: identifying, by a user equipment (UE), a plurality of subcarriers in the unlicensed spectrum, wherein the plurality of subcarriers have a 15 kilohertz (KHz) subcarrier spacing; identifying, by the UE, a multi-tone transmission configuration; and transmitting, by the UE based on the 15 KHz subcarrier spacing and the multi-tone transmission configuration, the UL transmission related to NB-IoT operation in the unlicensed spectrum.
  • KHz kilohertz
  • Example 19 includes the method of example 18, wherein the UL transmission is a narrowband physical UL shared channel (NPUSCH) transmission.
  • NPUSCH narrowband physical UL shared channel
  • Example 20 includes the method of example 19, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 2536 bits.
  • TBS transport block size
  • Example 21 includes the method of example 19, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 1000 bits.
  • TBS transport block size
  • Example 22 includes the method of any of examples 18-21, or some other example herein, wherein the UL transmission includes a plurality of resource units with a numerology used for licensed NB-IoT transmissions.
  • Example 23 includes the method of any of examples 18-21, or some other example herein, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • Example 24 includes the method of any of examples 18-21, or some other example herein, further comprising modulating, by the UE, information related to the UL transmission based on a quadrature phase shift keying (QPSK) scheme to form the UL transmission.
  • QPSK quadrature phase shift keying
  • Example 25 includes the method of any of examples 18-21, or some other example herein, further comprising encoding, by the UE, information related to the UL transmission based on convolutional turbo coding (CTC).
  • CTC convolutional turbo coding
  • Example 26 includes the method of any of examples 18-21, or some other example herein, wherein transmitting the UL transmission includes: cycling, by the UE, the UL transmission across a plurality of repetition cycles; and cycling a redundancy version (RV) related to the UL transmission across respective ones of the plurality of repetition cycles.
  • transmitting the UL transmission includes: cycling, by the UE, the UL transmission across a plurality of repetition cycles; and cycling a redundancy version (RV) related to the UL transmission across respective ones of the plurality of repetition cycles.
  • RV redundancy version
  • Example 27 includes the method of example 26, further comprising: scrambling, by the UE, a UL transmission at a first repetition cycle of the plurality of repetition cycles with a first scrambling factor; and scrambling, by the UE, a UL transmission at a second repetition cycles of the plurality of repetition cycles with a second scrambling factor.
  • Example 28 includes the method of example 27, wherein the first repetition cycle and the second repetition cycle are based on a radio frame number of a radio frame in which the DL transmission occurs.
  • Example 29 includes the method of example 26, wherein the plurality of repetition cycles is two repetition cycles.
  • Example 30 includes the method of example 26, wherein the RV is selected from a set of ⁇ 0, 2 ⁇ .
  • Example 31 includes the method of example 26, wherein a number of the plurality of repetition cycles is indicated in a signal received by the UE from a base station.
  • Example 32 includes the method of any of examples 18-21, or some other example herein, wherein transmitting the UL transmission includes transmitting, by the UE, the UL transmission without use of a compensation gap.
  • Example 33 includes the method of any of examples 18-21, or some other example herein, wherein transmitting the UL transmission includes transmitting, by the UE, the UL transmission on a single channel without the use of frequency hopping.
  • Example 34 includes the method of any of examples 18-21, or some other example herein, further comprising supporting, by the UE, a first hybrid automatic repeat request (HARQ) process related to the UL transmission and a second HARQ process related to the DL transmission, wherein the first HARQ process and the second HARQ process are concurrent.
  • Example 35 includes the method of example 34, wherein the first HARQ process is asynchronous and adaptive.
  • Example 36 includes the method of any of examples 18-21, or some other example herein, wherein transmitting the UL transmission includes transmitting the UL transmission in a plurality of slots in time, wherein each slot includes seven orthogonal frequency division (OFDM) symbols, and wherein a fourth symbol in a slot of the plurality of slots includes a demodulation reference signal (DMRS).
  • OFDM orthogonal frequency division
  • DMRS demodulation reference signal
  • Example 37 includes the method of any of examples 18-21, or some other example herein, further comprising transmitting, by the UE, the UL transmission based on open loop power control.
  • Example 38 includes the method of any of examples 18-21, or some other example herein, further comprising: identifying, by the UE, a first subframe in which the uplink transmission is transmitted; identifying, by the UE, a time of a last symbol of the first subframe; identifying, by the UE, a second subframe that has a first symbol at a time that is greater than or equal to 3 milliseconds later than the time of the last symbol of the first subframe; and identifying, by the UE based on the identification of the second subframe, a downlink transmission in the second subframe.
  • Example 39 includes a method of communicating in an unlicensed spectrum related to narrowband internet of things (NB-IoT), wherein the method comprises: identifying, by the UE, a narrowband physical downlink control channel (NPDCCH) transmission related to NB- IoT operation on the unlicensed spectrum, wherein the NPDCCH transmission includes downlink control information (DCI); identifying, by the UE based on the DCI, a resource related to a second transmission related to NB-IoT operation on the unlicensed spectrum; and transmitting, by the UE based on the identification of the resource related to the second transmission, an uplink transmission on a subcarrier of the unlicensed spectrum.
  • NB-IoT narrowband internet of things
  • Example 40 includes the method of example 39, wherein the unlicensed spectrum includes subcarriers with a frequency less than 1 Gigahertz (GHz).
  • Example 41 includes the method of examples 39 or 40, or some other example herein, wherein the second transmission is a narrowband physical downlink shared channel
  • NPDSCH NPDSCH
  • HARQ hybrid automatic repeat request
  • ACK/NCK acknowledgement/negative acknowledgement
  • Example 42 includes the method of example 41, wherein a first symbol of the
  • NPDSCH transmission is greater than or equal to four seconds later than a last symbol of the NPDCCH transmission.
  • Example 43 includes the method of example 41, wherein the NPDSCH transmission includes a first part on a first channel that includes a first plurality of subcarriers in the unlicensed spectrum and a second part on a second channel that includes a second plurality of subcarriers in the unlicensed spectrum.
  • Example 44 includes the method of example 41, wherein the NPDSCH transmission is in a first subframe and the HARQ ACK/NCK transmission is in a second subframe, and wherein the second subframe is greater than or equal to 12 subframes from the first subframe.
  • Example 45 includes the method of example 41, wherein the ACK/NCK transmission is one of a plurality of ACK-NCK transmissions in a HARQ-ACK bundle.
  • Example 46 includes the method of example 41, wherein the NPDSCH transmission and the ACK/NCK transmission use a same set of subcarriers as one another in the unlicensed spectrum.
  • Example 47 includes the method of example 41, wherein the NPDSCH transmission uses a first set of subcarriers in the unlicensed spectrum, and the ACK/NCK transmission uses a second set of subcarriers in the unlicensed spectrum that is different than the first set of subcarriers.
  • Example 48 includes the method of examples 39 or 40, or some other example herein, wherein the second transmission is the uplink transmission, and the second transmission is a narrowband physical uplink shared channel (NPUSCH) transmission.
  • NPUSCH narrowband physical uplink shared channel
  • Example 49 includes the method of example 48, wherein a first symbol of the
  • NPUSCH transmission is greater than or equal to 8 milliseconds (ms) later than a last symbol of the NPDCCH transmission.
  • Example 50 includes the method of example 48, wherein the NPDCCH transmission and the NPUSCH transmission are transmitted using identical subcarriers in the unlicensed spectrum.
  • Example 51 includes the method of example 48, wherein the NPDCCH transmission is transmitted using a first set of subcarriers in the unlicensed spectrum and the NPUSCH transmission is transmitted using a second set of subcarriers in the unlicensed spectrum.
  • Example 52 includes the method of example 48, wherein the NPUSCH transmission includes a first portion that is transmitted using a first set of subcarriers in the unlicensed spectrum and a second portion that is transmitted using a second set of subcarriers in the unlicensed spectrum.
  • Example 53 includes the method of examples 39 or 40, or some other example herein, further comprising: identifying, by the UE, a number of subframes after the transmission of the uplink transmission; and identifying, by the UE based on the number of subframes, a downlink transmission that follows the uplink transmission.
  • Example 54 includes the method of example 53, wherein the number of subframes is 0, 1, or 3.
  • Example 55 includes a method of identifying a downlink (DL) transmission related to narrowband internet of things (NB-IoT) operation in an unlicensed spectrum, the method comprising: identifying, by a user equipment (UE) in the DL transmission, a DL RU that includes only one resource block (RB) in the frequency domain and only one subframe in the time domain, wherein the RB includes a plurality of subcarriers in the unlicensed spectrum; and identifying, by the UE based on the DL RU, information related to NB-IoT operation in the unlicensed spectrum.
  • UE user equipment
  • RB resource block
  • Example 56 includes the method of example IV, wherein the DL transmission is a narrowband physical DL shared channel (NPDSCH) transmission.
  • NPDSCH narrowband physical DL shared channel
  • Example 57 includes the method of examples 55 or 56, or some other example herein, wherein the plurality of subcarriers includes 12 subcarriers.
  • Example 58 includes the method of examples 55 or 56, or some other example herein, wherein the RB includes 14 orthogonal frequency division multiplexed (OFDM) symbols.
  • OFDM orthogonal frequency division multiplexed
  • Example 59 includes the method of examples 55 or 56, or some other example herein, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • GHz gigahertz
  • Example 60 includes the method of examples 55 or 56, or some other example herein, wherein the DL transmission has a repetition value of less than 128.
  • Example 61 includes the method of example 60, further comprising identifying, by the UE based on radio resource control (RRC) signaling, an indication of a maximum value of the repetition value.
  • RRC radio resource control
  • Example 62 includes the method of examples 55 or 56, or some other example herein, wherein the DL transmission is based on a transport block size (TBS) table related to a maximum number of bits in a TBS usable by the UE.
  • TBS transport block size
  • Example 63 includes the method of example 62, wherein the maximum number of bits is 680 and the TBS table is a third generation partnership project (3GPP) release-13 (Rel- 13) TBS table.
  • 3GPP third generation partnership project
  • Example 64 includes the method of example 62, wherein the maximum number of bits is 2536 and the TBS table is a third generation partnership project (3GPP) release-14 (Rel- 14) TBS table.
  • 3GPP third generation partnership project
  • Example 65 includes the method of examples 55 or 56, or some other example herein, wherein the DL RU includes a plurality of demodulation reference signals (DMRSs) that have a pattern based on a third generation partnership project (3 GPP) release-14 (Rel- 14) DMRS pattern.
  • DMRSs demodulation reference signals
  • Example 66 includes the method of examples 55 or 56, or some other example herein, further comprising transmitting, by the UE to a base station, an indication of a capability to support a first hybrid automatic repeat request (HARQ) process related to the DL
  • HARQ hybrid automatic repeat request
  • Example 67 includes the method of examples 55 or 56, or some other example herein, further comprising generating the DL transmission based on use of a tail-biting convolutional code (TBCC).
  • TBCC tail-biting convolutional code
  • Example 68 includes the method of examples 55 or 56, or some other example herein, wherein the DL transmission is in accordance with a third generation partnership project (3GPP) transmission mode 1 (TM1), transmission mode 2 (TM2), transmission mode 6 (TM6), or transmission mode 9 (TM9).
  • 3GPP third generation partnership project
  • Example 69 includes the method of examples 55 or 56, or some other example herein, wherein transmission of the DL transmission occurs on a first channel, and further comprising identifying, by the UE, a re-transmission of DL transmission on a second channel different than the first channel.
  • Example 70 includes the method of examples 55 or 56, or some other example herein, wherein the DL transmission is transmitted on a single channel without the use of frequency hopping.
  • Example 71 includes a method of identifying an uplink (UL) transmission related to narrowband internet of things (NB-IoT) operation in an unlicensed spectrum, the method comprising: identifying, by a base station, a UL transmission that includes a plurality of subcarriers with a 15 kilohertz (KHz) subcarrier spacing in the unlicensed spectrum, wherein the UL transmission further has a multi-tone transmission configuration; and identifying, by the base station based on the UL transmission, information related to NB-IoT operation in the unlicensed spectrum.
  • KHz kilohertz
  • Example 72 includes the method of example 71, wherein the UL transmission is a narrowband physical UL shared channel (NPUSCH) transmission.
  • NPUSCH narrowband physical UL shared channel
  • Example 73 includes the method of example 72, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 2536 bits.
  • TBS transport block size
  • Example 74 includes the method of example 72, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 1000 bits.
  • TBS transport block size
  • Example 75 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission includes a plurality of resource units with a numerology used for licensed NB-IoT transmissions.
  • Example 76 includes the method of any of examples 71-74, or some other example herein, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • GHz gigahertz
  • Example 77 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission is modulated based on a quadrature phase shift keying (QPSK) scheme.
  • QPSK quadrature phase shift keying
  • Example 78 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission is encoded based on convolutional turbo coding (CTC).
  • CTC convolutional turbo coding
  • Example 79 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission is transmitted based on: cycling, by the UE, the UL transmission across a plurality of repetition cycles; and cycling a redundancy version (RV) related to the UL transmission across respective ones of the plurality of repetition cycles.
  • RV redundancy version
  • Example 80 includes the method of example 79, wherein the UL transmission is further transmitted based on: scrambling, by the UE, a UL transmission at a first repetition cycle of the plurality of repetition cycles with a first scrambling factor; and scrambling, by the UE, a UL transmission at a second repetition cycles of the plurality of repetition cycles with a second scrambling factor.
  • Example 81 includes the method of example 80, wherein the first repetition cycle and the second repetition cycle are based on a radio frame number of a radio frame in which the DL transmission occurs.
  • Example 82 includes the method of example 79, wherein the plurality of repetition cycles is two repetition cycles.
  • Example 83 includes the method of example 79, wherein the RV is selected from a set of ⁇ 0, 2 ⁇ .
  • Example 84 includes the method of example 79, wherein a number of the plurality of repetition cycles is indicated in a signal transmitted by the base station.
  • Example 85 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission is transmitted without use of a compensation gap.
  • Example 86 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission is transmitted on a single channel without the use of frequency hopping.
  • Example 87 includes the method of any of examples 71-74, or some other example herein, further comprising supporting, by the base station, a first hybrid automatic repeat request (HARQ) process related to the UL transmission and a second HARQ process related to the DL transmission, wherein the first HARQ process and the second HARQ process are concurrent.
  • HARQ hybrid automatic repeat request
  • Example 88 includes the method of example 87, wherein the first HARQ process is asynchronous and adaptive.
  • Example 89 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission is transmitted in a plurality of slots in time, wherein each slot includes seven orthogonal frequency division (OFDM) symbols, and wherein a fourth symbol in a slot of the plurality of slots includes a demodulation reference signal
  • OFDM orthogonal frequency division
  • Example 90 includes the method of any of examples 71-74, or some other example herein, wherein the UL transmission is transmitted based on open loop power control.
  • Example 91 includes the method of any of examples 71-74, or some other example herein, further comprising: identifying, by the base station, a first subframe in which the uplink transmission is transmitted; identifying, by the base station, a time of a last symbol of the first subframe; identifying, by the base station, a second subframe that has a first symbol at a time that is greater than or equal to 3 milliseconds later than the time of the last symbol of the first subframe; and transmitting, by the base station based on the identification of the second subframe, a downlink transmission in the second subframe.
  • Example 92 includes a method of communicating in an unlicensed spectrum related to narrowband internet of things (NB-IoT), wherein the method comprises: transmitting, by a base station, a narrowband physical downlink control channel (NPDCCH) transmission related to NB-IoT operation on the unlicensed spectrum, wherein the NPDCCH transmission includes downlink control information (DCI) that has an indication of a resource related to a second transmission related to B-IoT operation on the unlicensed spectrum; and identifying, by the base station from a user equipment (UE) based on the resource related to the second transmission, an uplink transmission on a subcarrier of the unlicensed spectrum.
  • DCI downlink control information
  • Example 93 includes the method of example 92, wherein the unlicensed spectrum includes subcarriers with a frequency less than 1 Gigahertz (GHz).
  • GHz Gigahertz
  • Example 94 includes the method of examples 92 or 93, or some other example herein, wherein the second transmission is a narrowband physical downlink shared channel
  • PDSCH downlink transmission
  • uplink transmission is a hybrid automatic repeat request (HARQ) acknowledgement/negative acknowledgement (ACK/NCK) transmission related to the NPDSCH transmission.
  • HARQ hybrid automatic repeat request
  • ACK/NCK acknowledgement/negative acknowledgement
  • Example 95 includes the method of example 94, wherein a first symbol of the
  • NPDSCH transmission is greater than or equal to four seconds later than a last symbol of the NPDCCH transmission.
  • Example 96 includes the method of example 94, wherein the NPDSCH transmission includes a first part on a first channel that includes a first plurality of subcarriers in the unlicensed spectrum and a second part on a second channel that includes a second plurality of subcarriers in the unlicensed spectrum.
  • Example 97 includes the method of example 94, wherein the NPDSCH transmission is in a first subframe and the HARQ ACK/NCK transmission is in a second subframe, and wherein the second subframe is greater than or equal to 12 subframes from the first subframe.
  • Example 98 includes the method of example 94, wherein the ACK/NCK transmission is one of a plurality of ACK-NCK transmissions in a HARQ-ACK bundle.
  • Example 99 includes the method of example 94, wherein the NPDSCH transmission and the ACK/NCK transmission use a same set of subcarriers as one another in the unlicensed spectrum.
  • Example 100 includes the method of example 94, wherein the NPDSCH transmission uses a first set of subcarriers in the unlicensed spectrum, and the ACK/NCK transmission uses a second set of subcarriers in the unlicensed spectrum that is different than the first set of subcarriers.
  • Example 101 includes the method of examples 92 or 93, or some other example herein, wherein the second transmission is the uplink transmission, and the second
  • Example 102 includes the method of example 101, wherein a first symbol of the PUSCH transmission is greater than or equal to 8 milliseconds (ms) later than a last symbol of the PDCCH transmission.
  • ms milliseconds
  • Example 103 includes the method of example 101, wherein the NPDCCH
  • transmission and the NPUSCH transmission are transmitted using identical subcarriers in the unlicensed spectrum.
  • Example 104 includes the method of example 101, wherein the NPDCCH
  • the NPUSCH transmission is transmitted using a second set of subcarriers in the unlicensed spectrum.
  • Example 105 includes the method of example 101, wherein the NPUSCH
  • transmission includes a first portion that is transmitted using a first set of subcarriers in the unlicensed spectrum and a second portion that is transmitted using a second set of subcarriers in the unlicensed spectrum.
  • Example 106 includes the method of examples 92 or 93, or some other example herein, further comprising: identifying, by the base station, a number of subframes after the transmission of the uplink transmission; and transmitting, by the base station based on the number of subframes, a downlink transmission that follows the uplink transmission.
  • Example 107 includes the method of example 106, wherein the number of subframes is 0, 1, or 3.
  • Example 108 includes a baseband apparatus to be used in a base station, wherein the baseband apparatus comprises: a processor to identify a downlink (DL) resource unit (RU) that includes only one resource block (RB) in a frequency domain and only one subframe in a time domain, wherein the RB includes a plurality of subcarriers in an unlicensed spectrum; and a radio frequency (RF) interface coupled with the processor, wherein the RF interface is to facilitate, based on the DL RU, a DL transmission related to narrowband internet of things (NB-IoT) operation in the unlicensed spectrum.
  • DL downlink
  • RB resource block
  • RF radio frequency
  • Example 109 includes the baseband apparatus of example 108, wherein the DL transmission is a narrowband physical DL shared channel (NPDSCH) transmission.
  • NPDSCH narrowband physical DL shared channel
  • Example 110 includes the baseband apparatus of example 108, wherein the plurality of subcarriers includes 12 subcarriers.
  • Example 111 includes the baseband apparatus of example 108, wherein the RB includes 14 orthogonal frequency division multiplexed (OFDM) symbols.
  • Example 112 includes the baseband apparatus of example 108, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • GHz gigahertz
  • Example 113 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein the DL transmission has a repetition value of less than 128.
  • Example 114 includes the baseband apparatus of example 113, wherein the RF interface or some other element of the baseband apparatus is to facilitate transmission, through radio resource control (RRC) signaling, of an indication of a maximum value of the repetition value.
  • RRC radio resource control
  • Example 115 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein the processor or some other element of the baseband apparatus is to perform one or more of: identify a maximum number of bits in a transport block size (TBS) usable by a user equipment (UE); identify, based on the maximum number of bits, a TBS table; and generate, based on the TBS table, the DL transmission.
  • TBS transport block size
  • Example 116 includes the baseband apparatus of example 115, wherein the maximum number of bits is 680 and the TBS table is a third generation partnership project (3GPP) release- 13 (Rel-13) TBS table.
  • 3GPP third generation partnership project
  • Example 117 includes the baseband apparatus of example 115, wherein the maximum number of bits is 2536 and the TBS table is a third generation partnership project (3GPP) release- 14 (Rel-14) TBS table.
  • 3GPP third generation partnership project
  • Example 118 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein the DL RU includes a plurality of demodulation reference signals (DMRSs) that have a pattern based on a third generation partnership project (3GPP) release- 14 (Rel-14) DMRS pattern.
  • DMRSs demodulation reference signals
  • 3GPP third generation partnership project
  • Example 119 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein the processor or some other element of the baseband apparatus is to support a first hybrid automatic repeat request (HARQ) process related to the DL transmission and a second HARQ process related to the DL transmission, wherein the first HARQ process and the second HARQ process are concurrent.
  • HARQ hybrid automatic repeat request
  • Example 120 includes the baseband apparatus of example 119, wherein the processor or some other element of the baseband apparatus is to identify an indication from a user equipment (UE) related to the UE's capability to support the first HARQ process and the second HARQ process.
  • Example 121 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein the processor or some other element of the baseband apparatus is to generate the DL transmission based on use of a tail-biting convolutional code (TBCC).
  • TBCC tail-biting convolutional code
  • Example 122 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein the RF interface circuitry or some other element of the baseband apparatus is to facilitate transmission of the DL transmission in accordance with a third generation partnership project (3GPP) transmission mode 1 (TMl), transmission mode 2 (TM2), transmission mode 6 (TM6), or transmission mode 9 (TM9).
  • 3GPP third generation partnership project
  • TMl transmission mode 1
  • TM2 transmission mode 2
  • TM6 transmission mode 6
  • TM9 transmission mode 9
  • Example 123 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein transmission of the DL transmission occurs on a first channel and wherein the RE interface circuitry or some other element of the baseband apparatus is to facilitate re-transmission of the DL transmission on a second channel different than the first channel.
  • Example 124 includes the baseband apparatus of any of examples 108-112, or some other example herein, wherein the RF interface circuitry or some other element of the baseband apparatus is to facilitate transmission of the DL transmission on a single channel without the use of frequency hopping.
  • Example 125 includes a baseband apparatus to be used in a user equipment (UE), wherein the baseband apparatus comprises: a processor to: identify a plurality of subcarriers in the unlicensed spectrum, wherein the plurality of subcarriers have a 15 kilohertz (KHz) subcarrier spacing; and identify a multi-tone transmission configuration; and radio frequency (RF) interface circuitry coupled with the processor, wherein the RF interface circuitry is to transmit, based on the 15 KHz subcarrier spacing and the multi-tone transmission
  • KHz kilohertz
  • an uplink (UL) transmission related to narrowband internet of things ( B-IoT) operation in the unlicensed spectrum an uplink (UL) transmission related to narrowband internet of things ( B-IoT) operation in the unlicensed spectrum.
  • B-IoT narrowband internet of things
  • Example 126 includes the baseband apparatus of example 125, wherein the UL transmission is a narrowband physical UL shared channel (NPUSCH) transmission.
  • NPUSCH narrowband physical UL shared channel
  • Example 127 includes the baseband apparatus of example 126, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 2536 bits.
  • TBS transport block size
  • Example 128 includes the baseband apparatus of example 126, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 1000 bits.
  • TBS transport block size
  • Example 129 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the UL transmission includes a plurality of resource units with a numerology used for licensed NB-IoT transmissions.
  • Example 130 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • GHz gigahertz
  • Example 131 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the processor or some other element of the baseband apparatus is to modulate information related to the UL transmission based on a quadrature phase shift keying (QPSK) scheme to form the UL transmission.
  • QPSK quadrature phase shift keying
  • Example 132 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the processor or some other element of the baseband apparatus is to encode information related to the UL transmission based on convolutional turbo coding (CTC).
  • CTC convolutional turbo coding
  • Example 133 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the processor or some other element of the baseband apparatus is to: cycle the UL transmission across a plurality of repetition cycles; and cycle a
  • RV redundancy version
  • Example 134 includes the baseband apparatus of example 133, wherein the processor or some other element of the baseband apparatus is to: scramble a UL transmission at a first repetition cycle of the plurality of repetition cycles with a first scrambling factor; and scramble a UL transmission at a second repetition cycles of the plurality of repetition cycles with a second scrambling factor.
  • Example 135 includes the baseband apparatus of example 134, wherein the first repetition cycle and the second repetition cycle are based on a radio frame number of a radio frame in which the DL transmission occurs.
  • Example 136 includes the baseband apparatus of example 133, wherein the plurality of repetition cycles is two repetition cycles.
  • Example 137 includes the baseband apparatus of example 133, wherein the RV is selected from a set of ⁇ 0, 2 ⁇ .
  • Example 138 includes the baseband apparatus of example 133, wherein a number of the plurality of repetition cycles is indicated in a signal received by the UE from a base station.
  • Example 139 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the RF circuitry or some other element of the baseband apparatus is to facilitate transmission of the UL transmission without use of a compensation gap-
  • Example 140 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the RF circuitry or some other element of the baseband apparatus is to facilitate transmission of the UL transmission on a single channel without the use of frequency hopping.
  • Example 141 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the processor or some other element of the baseband apparatus is to support a first hybrid automatic repeat request (HARQ) process related to the UL transmission and a second HARQ process related to the DL transmission, wherein the first
  • HARQ hybrid automatic repeat request
  • Example 142 includes the baseband apparatus of example 141, wherein the first
  • HARQ process is asynchronous and adaptive.
  • Example 143 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the RF interface or some other element of the baseband apparatus is to facilitate transmission of the UL transmission in a plurality of slots in time, wherein each slot includes seven orthogonal frequency division (OFDM) symbols, and wherein a fourth symbol in a slot of the plurality of slots includes a demodulation reference signal (DMRS).
  • OFDM orthogonal frequency division
  • DMRS demodulation reference signal
  • Example 144 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the RF interface or some other element of the baseband apparatus is to facilitate transmission of the UL transmission based on open loop power control.
  • Example 145 includes the baseband apparatus of any of examples 125-128, or some other example herein, wherein the processor or some other element of the baseband apparatus is further to perform one or more of: identify a first subframe in which the uplink
  • transmission is transmitted; identify a time of a last symbol of the first subframe; identify a second subframe that has a first symbol at a time that is greater than or equal to 3
  • Example 146 includes a baseband apparatus to be used in a user equipment (UE), wherein the baseband apparatus comprises: a processor to: identify a narrowband physical downlink control channel ( PDCCH) transmission related to narrowband internet of things (NB-IoT) operation on the unlicensed spectrum, wherein the NPDCCH transmission includes downlink control information (DCI); and identify, based on the DCI, a resource related to a second transmission related to NB-IoT operation on the unlicensed spectrum; and a radio frequency (RF) interface coupled with the processor, the RF interface to transmit, based on the identification of the resource related to the second transmission, an uplink transmission on a subcarrier of the unlicensed spectrum.
  • PDCCH physical downlink control channel
  • NB-IoT narrowband internet of things
  • Example 147 includes the baseband apparatus of example 146, wherein the unlicensed spectrum includes subcarriers with a frequency less than 1 Gigahertz (GHz).
  • GHz Gigahertz
  • Example 148 includes the baseband apparatus of examples 146 or 147, or some other example herein, wherein the second transmission is a narrowband physical downlink shared channel (NPDSCH) transmission and the uplink transmission is a hybrid automatic repeat request (HARQ) acknowledgement/negative acknowledgement (ACK/NCK) transmission related to the NPDSCH transmission.
  • NPDSCH narrowband physical downlink shared channel
  • HARQ hybrid automatic repeat request
  • ACK/NCK hybrid automatic repeat request acknowledgement/negative acknowledgement
  • Example 149 includes the baseband apparatus of example 148, wherein a first symbol of the NPDSCH transmission is greater than or equal to four seconds later than a last symbol of the NPDCCH transmission.
  • Example 150 includes the baseband apparatus of example 148, wherein the NPDSCH transmission includes a first part on a first channel that includes a first plurality of subcarriers in the unlicensed spectrum and a second part on a second channel that includes a second plurality of subcarriers in the unlicensed spectrum.
  • Example 151 includes the baseband apparatus of example 148, wherein the NPDSCH transmission is in a first subframe and the HARQ ACK/NCK transmission is in a second subframe, and wherein the second subframe is greater than or equal to 12 subframes from the first subframe.
  • Example 152 includes the baseband apparatus of example 148, wherein the
  • ACK/NCK transmission is one of a plurality of ACK-NCK transmissions in a HARQ-ACK bundle.
  • Example 153 includes the baseband apparatus of example 148, wherein the NPDSCH transmission and the ACK/NCK transmission use a same set of subcarriers as one another in the unlicensed spectrum.
  • Example 154 includes the baseband apparatus of example 148, wherein the NPDSCH transmission uses a first set of subcarriers in the unlicensed spectrum, and the ACK/NCK transmission uses a second set of subcarriers in the unlicensed spectrum that is different than the first set of subcarriers.
  • Example 155 includes the baseband apparatus of examples 146 or 147, or some other example herein, wherein the second transmission is the uplink transmission, and the second transmission is a narrowband physical uplink shared channel (PUSCH) transmission.
  • PUSCH physical uplink shared channel
  • Example 156 includes the baseband apparatus of example 155, wherein a first symbol of the NPUSCH transmission is greater than or equal to 8 milliseconds (ms) later than a last symbol of the NPDCCH transmission.
  • Example 157 includes the baseband apparatus of example 155, wherein the NPDCCH transmission and the NPUSCH transmission are transmitted using identical subcarriers in the unlicensed spectrum.
  • Example 158 includes the baseband apparatus of example 155, wherein the NPDCCH transmission is transmitted using a first set of subcarriers in the unlicensed spectrum and the NPUSCH transmission is transmitted using a second set of subcarriers in the unlicensed spectrum.
  • Example 159 includes the baseband apparatus of example 155, wherein the NPUSCH transmission includes a first portion that is transmitted using a first set of subcarriers in the unlicensed spectrum and a second portion that is transmitted using a second set of subcarriers in the unlicensed spectrum.
  • Example 160 includes the baseband apparatus of examples 146 or 147, or some other example herein, wherein the processor or some other element of the baseband apparatus is to: identify a number of subframes after the transmission of the uplink transmission; and identify, based on the number of subframes, a downlink transmission that follows the uplink transmission.
  • Example 161 includes the baseband apparatus of example 160, wherein the number of subframes is 0, 1, or 3.
  • Example 162 includes a baseband apparatus to be used in a user equipment (UE), wherein the baseband apparatus comprises: a radio frequency (RF) interface to identify a downlink (DL) transmission related to narrowband internet of things (NB-IoT) operation in an unlicensed spectrum; and a processor coupled with the RF interface, the processor to: identify, in the DL transmission, a DL RU that includes only one resource block (RB) in the frequency domain and only one subframe in the time domain, wherein the RB includes a plurality of subcarriers in the unlicensed spectrum; and identify, based on the DL RU, information related to NB-IoT operation in the unlicensed spectrum.
  • RF radio frequency
  • DL downlink
  • NB-IoT narrowband internet of things
  • Example 163 includes the baseband apparatus of example 162, wherein the DL transmission is a narrowband physical DL shared channel (NPDSCH) transmission.
  • Example 164 includes the baseband apparatus of example 162, wherein the plurality of subcarriers includes 12 subcarriers.
  • NPDSCH narrowband physical DL shared channel
  • Example 165 includes the baseband apparatus of example 162, wherein the RB includes 14 orthogonal frequency division multiplexed (OFDM) symbols.
  • OFDM orthogonal frequency division multiplexed
  • Example 166 includes the baseband apparatus of example 162, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • GHz gigahertz
  • Example 167 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein the DL transmission has a repetition value of less than 128.
  • Example 168 includes the baseband apparatus of example 167, wherein the RF interface or some other element of the baseband apparatus is to identify a radio resource control (RRC) signal that includes an indication of a maximum value of the repetition value.
  • RRC radio resource control
  • Example 169 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein the DL transmission is based on a transport block size (TBS) table related to a maximum number of bits in a TBS usable by the UE.
  • TBS transport block size
  • Example 170 includes the baseband apparatus of example 169, wherein the maximum number of bits is 680 and the TBS table is a third generation partnership project (3GPP) release-13 (Rel-13) TBS table.
  • 3GPP third generation partnership project
  • Example 171 includes the baseband apparatus of example 169, wherein the maximum number of bits is 2536 and the TBS table is a third generation partnership project (3GPP) release- 14 (Rel-14) TBS table.
  • 3GPP third generation partnership project
  • Example 172 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein the DL RU includes a plurality of demodulation reference signals (DMRSs) that have a pattern based on a third generation partnership project (3GPP) release- 14 (Rel-14) DMRS pattern.
  • DMRSs demodulation reference signals
  • 3GPP third generation partnership project
  • Example 173 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein the RF interface or some other element of the baseband apparatus is to facilitate transmission, to a base station, of an indication of a capability to support a first hybrid automatic repeat request (HARQ) process related to the DL
  • HARQ hybrid automatic repeat request
  • Example 174 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein the processor or some other element of the baseband apparatus are to generate the DL transmission based on use of a tail-biting convolutional code (TBCC).
  • Example 175 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein the DL transmission is in accordance with a third generation partnership project (3GPP) transmission mode 1 (TM1), transmission mode 2 (TM2), transmission mode 6 (TM6), or transmission mode 9 (TM9).
  • 3GPP third generation partnership project
  • Example 176 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein transmission of the DL transmission occurs on a first channel, and wherein the RF interface or some other element of the UE is to identify a re-transmission of DL transmission on a second channel different than the first channel.
  • Example 177 includes the baseband apparatus of any of examples 162-166, or some other example herein, wherein the DL transmission is transmitted on a single channel without the use of frequency hopping.
  • Example 178 includes a baseband apparatus to be used in a base station, wherein the baseband apparatus comprises: a radio frequency (RF) interface to identify an uplink (UL) transmission related to narrowband internet of things ( B-IoT) operation in an unlicensed spectrum, wherein the UL transmission includes a plurality of subcarriers with a 15 kilohertz (KHz) subcarrier spacing in the unlicensed spectrum, and wherein the UL transmission further has a multi-tone transmission configuration; and a processor coupled with the RF interface, wherein the processor is to identify, based on the UL transmission, information related to NB-IoT operation in the unlicensed spectrum.
  • RF radio frequency
  • Example 179 includes the baseband apparatus of example 178, wherein the UL transmission is a narrowband physical UL shared channel (NPUSCH) transmission.
  • NPUSCH narrowband physical UL shared channel
  • Example 180 includes the baseband apparatus of example 179, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 2536 bits.
  • TBS transport block size
  • Example 181 includes the baseband apparatus of example 179, wherein the NPUSCH transmission is based on a transport block size (TBS) with a maximum of 1000 bits.
  • TBS transport block size
  • Example 182 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission includes a plurality of resource units with a numerology used for licensed NB-IoT transmissions.
  • Example 183 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the unlicensed spectrum includes subcarriers with a frequency of less than 1 gigahertz (GHz).
  • GHz gigahertz
  • Example 184 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission is modulated based on a quadrature phase shift keying (QPSK) scheme.
  • Example 185 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission is encoded based on convolutional turbo coding (CTC).
  • CTC convolutional turbo coding
  • Example 186 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission is transmitted based on: cycling, by the UE, the UL transmission across a plurality of repetition cycles; and cycling a redundancy version (RV) related to the UL transmission across respective ones of the plurality of repetition cycles.
  • RV redundancy version
  • Example 187 includes the baseband apparatus of example 186, wherein the UL transmission is further transmitted based on: scrambling, by the UE, a UL transmission at a first repetition cycle of the plurality of repetition cycles with a first scrambling factor; and scrambling, by the UE, a UL transmission at a second repetition cycles of the plurality of repetition cycles with a second scrambling factor.
  • Example 188 includes the baseband apparatus of example 187, wherein the first repetition cycle and the second repetition cycle are based on a radio frame number of a radio frame in which the DL transmission occurs.
  • Example 189 includes the baseband apparatus of example 186, wherein the plurality of repetition cycles is two repetition cycles.
  • Example 190 includes the baseband apparatus of example 186, wherein the RV is selected from a set of ⁇ 0, 2 ⁇ .
  • Example 191 includes the baseband apparatus of example 186, wherein a number of the plurality of repetition cycles is indicated in a signal transmitted by the base station.
  • Example 192 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission is transmitted without use of a compensation gap.
  • Example 193 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission is transmitted on a single channel without the use of frequency hopping.
  • Example 194 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the processor or some other element of the baseband apparatus is further to support a first hybrid automatic repeat request (HARQ) process related to the UL transmission and a second HARQ process related to the DL transmission, wherein the first HARQ process and the second HARQ process are concurrent.
  • Example 195 includes the baseband apparatus of example 194, wherein the first HARQ process is asynchronous and adaptive.
  • Example 196 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission is transmitted in a plurality of slots in time, wherein each slot includes seven orthogonal frequency division (OFDM) symbols, and wherein a fourth symbol in a slot of the plurality of slots includes a demodulation reference signal (DMRS).
  • OFDM orthogonal frequency division
  • DMRS demodulation reference signal
  • Example 197 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the UL transmission is transmitted based on open loop power control.
  • Example 198 includes the baseband apparatus of any of examples 178-181, or some other example herein, wherein the processor or some other element of the baseband apparatus is to: identify a first subframe in which the uplink transmission is transmitted; identify a time of a last symbol of the first subframe; and identify a second subframe that has a first symbol at a time that is greater than or equal to 3 milliseconds later than the time of the last symbol of the first subframe; and the RF interface or some other element of the baseband apparatus is to transmit, based on the identification of the second subframe, a downlink transmission in the second subframe.
  • Example 199 includes a baseband apparatus to be used in a base station, wherein the baseband apparatus comprises: a processor to generate downlink control information (DCI) that includes an indication of a resource related to a second transmission related to narrowband internet of things (NB-IoT) operation on an unlicensed spectrum; and a radio frequency (RF) interface coupled with the processor, wherein the RF interface is to: facilitate transmission of a narrowband physical downlink control channel ( PDCCH) transmission that includes the DCI; and identify, based on the resource related to the second transmission, an uplink transmission on a subcarrier of the unlicensed spectrum.
  • DCI downlink control information
  • NB-IoT narrowband internet of things
  • RF radio frequency
  • Example 200 includes the baseband apparatus of example 199, wherein the unlicensed spectrum includes subcarriers with a frequency less than 1 Gigahertz (GHz).
  • GHz Gigahertz
  • Example 201 includes the baseband apparatus of examples 199 or 200, or some other example herein, wherein the second transmission is a narrowband physical downlink shared channel (PDSCH) transmission and the uplink transmission is a hybrid automatic repeat request (HARQ) acknowledgement/negative acknowledgement (ACK/NCK) transmission related to the NPDSCH transmission.
  • Example 202 includes the baseband apparatus of example 201, wherein a first symbol of the PDSCH transmission is greater than or equal to four seconds later than a last symbol of the PDCCH transmission.
  • Example 203 includes the baseband apparatus of example 201, wherein the NPDSCH transmission includes a first part on a first channel that includes a first plurality of subcarriers in the unlicensed spectrum and a second part on a second channel that includes a second plurality of subcarriers in the unlicensed spectrum.
  • Example 204 includes the baseband apparatus of example 201, wherein the NPDSCH transmission is in a first subframe and the HARQ ACK/NCK transmission is in a second subframe, and wherein the second subframe is greater than or equal to 12 subframes from the first subframe.
  • Example 205 includes the baseband apparatus of example 201, wherein the
  • ACK/NCK transmission is one of a plurality of ACK-NCK transmissions in a HARQ-ACK bundle.
  • Example 206 includes the baseband apparatus of example 201, wherein the NPDSCH transmission and the ACK/NCK transmission use a same set of subcarriers as one another in the unlicensed spectrum.
  • Example 207 includes the baseband apparatus of example 201, wherein the NPDSCH transmission uses a first set of subcarriers in the unlicensed spectrum, and the ACK/NCK transmission uses a second set of subcarriers in the unlicensed spectrum that is different than the first set of subcarriers.
  • Example 208 includes the baseband apparatus of examples 199 or 200, or some other example herein, wherein the second transmission is the uplink transmission, and the second transmission is a narrowband physical uplink shared channel (NPUSCH) transmission.
  • NPUSCH narrowband physical uplink shared channel
  • Example 209 includes the baseband apparatus of example 208, wherein a first symbol of the NPUSCH transmission is greater than or equal to 8 milliseconds (ms) later than a last symbol of the NPDCCH transmission.
  • Example 210 includes the baseband apparatus of example 208, wherein the NPDCCH transmission and the NPUSCH transmission are transmitted using identical subcarriers in the unlicensed spectrum.
  • Example 211 includes the baseband apparatus of example 208, wherein the NPDCCH transmission is transmitted using a first set of subcarriers in the unlicensed spectrum and the
  • Example 212 includes the baseband apparatus of example 208, wherein the PUSCH transmission includes a first portion that is transmitted using a first set of subcarriers in the unlicensed spectrum and a second portion that is transmitted using a second set of subcarriers in the unlicensed spectrum.
  • Example 213 includes the baseband apparatus of examples 199 or 200, or some other example herein, wherein the processor or some other element of the baseband apparatus is to identify a number of subframes after the transmission of the uplink transmission; and the RF interface is to facilitate transmission, based on the number of subframes, of a downlink transmission that follows the uplink transmission.
  • Example 214 includes the baseband apparatus of example 213, wherein the number of subframes is 0, 1, or 3.
  • Example 215 includes the downlink shared channel design to support divergence UEs, including RU design, DMRS, HARQ, repetition, channel coding and so on.
  • Example 216 includes the subject matter of example 215 or some other examples herein, wherein the RU can be defined for physical downlink shared channel, where it contains one RB in the frequency domain, and 1 subframe in the time domain.
  • the TB size is derived based on RU number and MCS index, which is introduced in the TBS subsection, wherein: for the UE with narrow bandwidth capability, multiple RUs span into the time domain, where the RU number can reuse B-IOT system, i.e. ⁇ 1,2,3,4,5,6,8, 10 ⁇ , and for the UE with wide bandwidth capability, multiple RUs can span into both time domain and frequency domain.
  • Example 217 includes the subject matter of example 215 or some other examples herein, wherein for UE with wide bandwidth capability: the RU mapping can be frequency domain firstly and time domain secondly, and vice versa.
  • the mapping sequence can be configured by eNB through high layer singling; for RU mapping in the frequency domain, the starting RB/carrier index, and the ending RB/carrier index can be predefined by eNB, or high layer configured by eNB, or dynamically configured through DCI.
  • the number of allocated RUs is always in frequency domain, while the time domain resource is 1ms.
  • one domain (i.e., frequency or time domain) resource can be predefined or configured by higher layer signaling, while the number of RUs can be indicated by DCI.
  • DCI can be two resource allocation factors to indicate the number of RUs in frequency domain and number of subframes to be allocated.
  • Example 218 includes the subject matter of example 215 or some other examples herein, wherein the repetition can be ⁇ 1, 2, 4, 8, 16, 32, 64, 128, 192, 256, 384, 512, 768, 1024, 1536, 2048 ⁇ . It can be explicitly indicated by DCI, or a maximum value is configured through RRC signaling, and a fraction factor ⁇ 1, 1/2, 1/4, 1/8, 1/16, 1/32, 1/64, 1/127 ⁇ is explicitly configured by DCI.
  • Example 219 includes the subject matter of example 215 or some other examples herein, wherein the maximum TBS is pre-defined, or be reported by UE, that is: Option 1 : pre-defined maximum TB size, wherein the maximum TBS for UE with narrow bandwidth capability and maximum TBS for UE with wide bandwidth capability, are equal to 2546 bits; while different UE may still report their TBS capacity, then the TBS index for different UEs with different capacity has different restriction; and Option 2: the UE with narrow bandwidth capability have two type of TBS capacity, one is 680, and the other is 2536 bits, wherein the UE with wide bandwidth capability have three types of TBS capacity, one is lOOObits, one is 2536bits, and the other is 4008.
  • Option 1 pre-defined maximum TB size, wherein the maximum TBS for UE with narrow bandwidth capability and maximum TBS for UE with wide bandwidth capability, are equal to 2546 bits; while different UE may still report their TBS capacity, then the TBS index for different UEs with different capacity has different
  • Example 220 includes the subject matter of example 215 or some other examples herein, wherein separate TBS can be de-fined for UEs with different capability. For instance, the UE with 680 bits maximum TBS, it can use the Rel-13 TBS table, while UE with maximum 2536 bits, it can reuse the Rel-14 TBS table. As another example, which TBS table to be used can be configured by higher layer signaling. The TBS can be min ⁇ indicated TBS by reading from the TBS table, max TBS supported by the UE.
  • Example 221 includes the subject matter of example 215 or some other examples herein, wherein a unified TBS table can be utilized for UEs with different bandwidth capability.
  • Table 1, herein, may illustrate a table of 4 bits field of TBS and three bits of RU. According to different UE capability, the MCS index is restricted.
  • the TBS can be determined by min ⁇ indicated TBS by reading from the TBS table, max TBS supported by the UE ⁇ .
  • Example 222 includes the subject matter of example 215 or some other examples herein, wherein the demodulation reference signal (DMRS) can reuse either legacy LTE DMRS pattern, as illustrated in the example (a), or the legacy LTE CRS pattern.
  • DMRS demodulation reference signal
  • Example 223 includes the subject matter of example 215 or some other examples herein, wherein the HARQ processes capability signaling for different UE can be reported by UE: Option 1 : reported by UE.
  • the maximum HARQ processes numbers can be chose from ⁇ 1, 2 ⁇ ; for UE with wide bandwidth capability, the maximum HARQ processes number can be chose from ⁇ 1,2,8, 6, 9, 10, 11, 12, 14, 16 ⁇ .
  • the HARQ processes number for UE is associated with the UE bandwidth capability.
  • the HARQ processes capability can be either 1 or 2 by default.
  • the UE with wide bandwidth capability, the HARQ processes capability can be 8 by default.
  • Example 224 includes the subject matter of example 215 or some other examples herein, wherein x subframes are RU-level repetition, where x can be a pre-defined value, e.g., 4, or be associated with the repetition times, e.g., min ⁇ 4,Nrep ⁇ .
  • the RU is repeated in the adjacent subframes, including the scrambling.
  • Example 225 includes the subject matter of example 215 or some other examples herein, wherein the channel coding can reuse the either NB-IOT which is TBCC, or eMTC turbo coding, wherein: alternatively, the both NB-IOT and eMTC channel coding schemes are supported, where the specific channel coding type is associated with UE's TBS capacity, or bandwidth capability, or reported by UE separately.
  • NB-IOT which is TBCC
  • eMTC turbo coding wherein: alternatively, the both NB-IOT and eMTC channel coding schemes are supported, where the specific channel coding type is associated with UE's TBS capacity, or bandwidth capability, or reported by UE separately.
  • Example 226 includes the subject matter of example 215 or some other examples herein, wherein one or multiple transmission mode, e.g., TM1, TM2, TM6, TM9 can be supported.
  • TM1, TM2, TM6, TM9 can be supported.
  • Example 227 includes the subject matter of example 215 or some other examples herein, wherein multiple PDSCH RU repetition can be transmitted within one specific channel, and the remaining part beyond one specific channel is dropped.
  • Example 228 includes the subject matter of example 215 or some other examples herein, wherein multiple PDSCH RU repetition can be spanned to multiple channels: UE can detect whether the next new channel is acquired or not through CRS or presence signaling firstly, and then continue to receive the PDSCH.
  • Example 229 includes the subject matter of example 215 or some other examples herein, wherein a UE category can be introduced, where one or multiple following features are contained: TBS capability, e.g., ⁇ 680, 1000, 2536, 4008 ⁇ ; BW capability, e.g., ⁇ 1RB, 6RB ⁇ ; Channel coding capability, e.g., ⁇ TBCC, Turbo ⁇ ; Modulation capability, e.g., ⁇ QPSK- only, QPSK+16QAM ⁇ ; HARQ process, which is related to the soft buffer size; and
  • TBS capability e.g., ⁇ 680, 1000, 2536, 4008 ⁇
  • BW capability e.g., ⁇ 1RB, 6RB ⁇
  • Channel coding capability e.g., ⁇ TBCC, Turbo ⁇
  • Modulation capability e.g., ⁇ QPSK- only, QPSK+16QAM ⁇
  • HARQ process which is related to the soft buffer size
  • Example 230 includes the design for the PUSCH for divergent UEs operating in unlicensed band, with the aim to provide coexistence between UE with narrowband (Nb-IoT like) and wideband (MTC like) capabilities. This includes embodiments for numerology and mapping of resource units, modulation order, channel coding and repetitions cycles, number of repetitions, transport block size, HARQ processes, DMRS design, frequency hopping, power control, UL gap compensation and related timing relationship.
  • Nb-IoT like narrowband
  • MTC like wideband
  • Example 231 includes the method of example 230 or some other example herein, wherein for the UE with narrow band capabilities: multiple RUs span into the time domain, and the numerology remain the same as that of B-IoT; single-tone transmission is not supported; single-tone and multi-tone transmission is permitted, following the NB-IoT design, but only 15 KHz subcarrier spacing is supported; 3.75 KHz subcarrier spacing is supported; only multi-tone transmission is supported with the same numerology as NB-IoT (for instance, only one RB configuration for PUSCH is configured as downlink); or PUSCH transmission with 6 tones and 12 tones can be supported.
  • NB-IoT for instance, only one RB configuration for PUSCH is configured as downlink
  • PUSCH transmission with 6 tones and 12 tones can be supported.
  • Example 232 includes the method of example 230 or some other example herein, wherein for the UE with wideband capabilities: the number of allocated RUs may span in one domain (e.g., only one domain); or multiple RUs can span in a fixed manner into both time and frequency domain, or this can be dynamically defined through higher layer signaling, or through DCI.
  • the number of allocated RUs may span in one domain (e.g., only one domain); or multiple RUs can span in a fixed manner into both time and frequency domain, or this can be dynamically defined through higher layer signaling, or through DCI.
  • Example 233 includes the method of example 230 or some other example herein, wherein in order to reuse the eMTC design this can be scaled down from 6 PRBs into 12/6 sub carriers.
  • Example 234 includes the method of example 230 or some other example herein, wherein UE with wideband capability only supports PUSCH allocation in unit of PRB.
  • Example 235 includes the method of example 230 or some other example herein, wherein sub-PRB allocation can be supported.
  • Example 236 includes the method of example 230 or some other example herein, wherein the use of sub-PRB allocation can be configured by higher layer signaling and the DCI resource allocation and MCS fields need to be interpreted correspondingly.
  • DCI can dynamically schedule the resource allocation in unit of subcarrier or PRB.
  • Example 237 includes the method of example 230 or some other example herein, wherein different modulations can be adopted for UEs with different capabilities.
  • Example 238 includes the method of example 230 or some other example herein, wherein RV cycling is supported to boost the performance through additional coding gain.
  • Example 240 includes the method of examples 230 or 238 or some other example herein, wherein the RV sequence is ⁇ 0,2 ⁇ as for NB-IoT.
  • Example 241 includes the method of examples 230 or 238 or some other example herein, scrambling follows the NB-IoT procedure, or in alternative it is similar to that in LTE.
  • Example 242 includes the method of examples 230 or 238 or some other example herein, wherein for UE with narrowband capabilities Z is one and/or min ⁇ 4, repetition/2 ⁇ as for NB-IoT.
  • Example 243 includes the method of examples 230 or 238 or some other example herein, wherein UE with wideband capabilities Z is 1 or 4 or 5, and scrambling is applied at each cycle, and RV cycling is supported across PUSCH repetitions.
  • Example 244 includes the method of examples 230 or 238 or some other example herein, wherein the RV sequence is ⁇ 0,2,3,1 ⁇ as for eMTC.
  • the initial RV for narrowband UE or wideband UE can be predefined, or indicated by higher layer signaling or dynamically via DCI.
  • Example 245 includes the method of examples 230 or 238 or some other example herein, wherein for UE with narrowband capabilities scrambling is applied similarly as the NB-IoT design.
  • Example 246 includes the method of examples 230 or 238 or some other example herein, wherein for UE with wideband capabilities scrambling is applied for Z SFs before changing.
  • Example 247 includes the method of example 230 or some other example herein, wherein for UE with narrowband capabilities the set of the NB-IoT repetitions are re-used.
  • Example 248 includes the method of example 230 or some other example herein, wherein for UE with wideband capabilities the set of repetitions can be chosen from the set ⁇ 1, 2, 4, 8, 16, 32, 64, 128, 192, 256, 384, 512, 768, 1024, 1536, 2048 ⁇ .
  • Example 249 includes the method of example 230 or some other example herein, wherein regardless of the UE capability the set of number of repetitions are equivalent to that of eMTC.
  • Example 250 includes the method of example 230 or some other example herein, wherein the number of repetitions can be explicitly indicated through DCI, or through higher layer signaling, or similarly to eMTC some subset of the allowed number of repetitions can be formed, and chosen through SIB signaling together with DCI.
  • Example 251 includes the method of example 230 or some other example herein, wherein a predefined maximum TBS is used, whether the UE has narrowband or wideband capabilities. In one embodiment, the maximum TBS is 2546 bits or 2984 bits.
  • Example 252 includes the method of example 230 or some other example herein, wherein a unified TBS table can be formed.
  • Example 253 includes the method of example 230 or some other example herein, wherein UEs with different capabilities support a different maximum TBS.
  • Example 254 includes the method of example 230 or some other example herein, wherein UEs with narrowband capability support maximum TBS equal to 1000 and 2536. In one embodiment, UEs this wideband capabilities support maximum TBS equal to 1000, 2536, 2984, and 6968.
  • Example 255 includes the method of example 230 or some other example herein, wherein for UE with narrowband capabilities the maximum number of HARQ processes is either 1 or 2.
  • Example 256 includes the method of example 230 or some other example herein, wherein for UE with wideband capabilities the maximum number of HARQ processes can be chosen among the set ⁇ 1, 2, 3, 4, 6, 7, 8 ⁇ .
  • Example 257 includes the method of example 230 or some other example herein, wherein the number of HARQ processes is related to the UE bandwidth capabilities.
  • Example 258 includes the method of example 230 or some other example herein, wherein asynchronous and adaptive HARQ can be supported for PUSCH, for both narrowband UE and wideband UE.
  • Example 259 includes the method of example 230 or some other example herein, wherein the DMRS is constructed as for B-IoT.
  • Example 260 includes the method of example 230 or some other example herein, wherein the DMRS is obtained by a shorter length ZC sequence, or PN sequence, with cyclic shift and/or OCC applied to it.
  • Example 261 includes the method of example 230 or some other example herein, wherein regardless of the number of tones in a multi-tone transmission, the DMRS is formed as in LTE for 1 PRB, and it is truncated accordingly to accommodate different number of tones.
  • Example 262 includes the method of example 230 or some other example herein, wherein for UE with wideband capabilities multi-tone transmissions are supported, and the DMRS follows the NB-IoT design.
  • Example 263 includes the method of example 230 or some other example herein, wherein for UE with wideband capabilities, the DMRS follows the LTE-like design (DMRS in the center of the slot, in symbol 3 and 10, and DMRS sequence formed as in section 5.5 of spec 36.211).
  • Example 264 includes the method of example 230 or some other example herein, wherein FH is not supported.
  • Example 265 includes the method of example 230 or some other example herein, wherein for UE with wideband capabilities FH is used.
  • Example 266 includes the method of example 230 or some other example herein, wherein regardless of the UE capabilities, frequency hopping is supported.
  • frequency hopping is applied, one of the following two options can be used: FH within one channel: in one embodiment, multiple PUSCH RU repetitions can be transmitted within one specific channel, and the remaining part beyond that specific channel is dropped; or Channel level hopping: in another embodiment, multiple PUSCH RU repetitions can be spanned to multiple
  • Example 267 includes the method of example 230 or some other example herein, wherein details regarding the frequency interval, granularity, offset, and retuning are provided in some embodiments.
  • Example 268 includes the method of example 230 or some other example herein, wherein details regarding the power control are provided.
  • Example 269 includes the method of example 230 or some other example herein, wherein regardless of the UE capabilities the NB-IoT timing relationships can be carried on and reused, as well as the DCI signaling for the timing scheduling.
  • Example 270 includes the method of example 230 or some other example herein, wherein the NB-IoT timing relationship of NB-IoT are used for UE with narrowband capabilities.
  • the scheduling delay can take into account absolute SFs, or only valid UL SFs.
  • Example 271 includes the method of example 230 or some other example herein, wherein the UL gap compensation is not supported.
  • Example 272 includes the method of example 230 or some other example herein, wherein the UL compensation gap is introduced for long continuous PUSCH transmission.
  • Example 273 includes the method of example 230 or some other example herein, wherein some additional UE categories can be introduced.
  • Example 274 includes a method comprising a timing relationship between the PDCCH and the associated PDSCH or PUSCH, as well we timing reserved for
  • Example 275 includes the method of example 274, for UEs with narrow bandwidth, the downlink control information (DCI), which are carried in PDCCH on one or multiple subframes, the starting subframe of PDSCH can be x subframes later than the ending subframe of PDCCH, wherein: x is larger than 0, can be pre-defined as 4, or configured by eNB through high layer signaling or DCI.
  • the scheduling delay is indicated by DCI
  • the method in NB-IoT can be reused; or x can be reported by UE according to its processing capability.
  • Example 276 includes the method of example 274, for UEs with wide bandwidth, the gap x in terms of subframe/slots, between ending subframe of PDCCH and the starting subframe of PDSCH, can be: x is equal to 0, where the PDCCH and PDSCH are transmitted at the same subframe in the FDMed manner, where the RB/SC/carrier index of PDSCH can be configured by the associated DCI.
  • This configuration can be applicable to UEs near the eNB, without or with small repetition times; or x can be larger than 0. It can be either a predefined number, e.g., 1, 2 or 4, or configured by eNB through high layer signaling or DCI.
  • Example 277 includes the method of examples 275 or 276, the x subframe can be either x absolute subframe, or x valid downlink subframes, where the uplink subframes are precluded.
  • Example 278 includes the method of example 274, the PDCCH and PDSCH can be allocated at one specific channel before hopping to another channel.
  • Example 279 includes the method of example 274, the PDCCH and PDSCH can be allocated at different channels, where the channel for PDSCH transmission can be configured by eNB through DCI. Alternatively, a mapping defining the channel for PDSCH transmission from where the PDCCH is sent can be predefined or configured by higher layer signaling.
  • Example 280 includes the method of example 274, the PDSCH can be restricted to one channel, or spanned to multiple channels.
  • Example 281 includes the method of example 274, for UEs with narrow bandwidth, the gap x in terms of subframe/slots, between ending subframe of PDSCH and the ACK/NCK report, can be: x is larger than 0, can be pre-defined as 4 or 12, or configured by eNB through high layer signaling or DCI; or x can be reported by UE according to its processing capability.
  • Example 282 includes the method of example 274, the HARQ may be a bitmap, it can be transmitted at any time corresponding to the PDSCH. But only the ACK/NCK bit after x subframe can be viewed as the valid report. In embodiments, when multiple ACK/NACK is scheduled to be sent on the same time, HARQ-ACK bundling can be used.
  • Example 283 includes the method of example 274, the PDSCH and PUCCH/PUSCH carrying the ACK/NCK can be allocated at one specific channel before hopping to another channel;
  • Example 284 includes the method of example 274, the PDSCH and PUCCH/PUSCH carrying the ACK/NCK can be allocated at different channels, where the channel for PDSCH transmission can be configured by eNB through DCI, e.g., in terms of the offset from where the DCI or PDSCH is sent.
  • a mapping defining the channel for ACK/NACK transmission from where the PDSCH or DCI is sent can be predefined or configured by higher layer signaling.
  • Example 285 includes the method of example 281, for UEs with narrow bandwidth, the downlink control information (DCI), which are carried in PDCCH on one or multiple subframes, the starting subframe of PUSCH can be x subframes later than the ending subframe of PDCCH, wherein: x is larger than 0, can be pre-defined as 4 or 8, or configured by eNB through high layer signaling or DCI, or x can be reported by UE according to its processing capability.
  • DCI downlink control information
  • Example 286 includes the method of example 274, the x subframe can be either x absolute subframe, or x valid uplink subframes, where the downlink subframes are precluded.
  • Example 287 includes the method of example 274, the PDCCH and PUSCH can be allocated at one specific channel before hopping to another channel.
  • Example 288 includes the method of example 274, the PDCCH and PUSCH can be allocated at different channels, where the channel for PUSCH transmission can be configured by eNB through DCI. Alternatively, a mapping defining the channel for PUSCH
  • transmission from where the DCI is sent can be predefined or configured by higher layer signaling.
  • Example 289 includes the method of example 274, the PUSCH can be restricted to one channel, or spanned to multiple channels.
  • Example 290 includes the method of example 274, for one UE, x subframes can be reserved for switching from uplink transmission to downlink reception, while the downlink can be PDCCH or PDSCH, wherein x can be 0, 1, 3, or other values. It can be pre-defined, or configured by eNB through high layer signaling or DCI, or reported by UE.
  • Example 291 includes the method of example 274, for one UE, it can receive multiple DCIs in PDCCH, and then perform the PDSCH reception and PUSCH transmission one by one. Alternatively, UE can receive one DCI, and perform the PDSCH reception or PUSCH transmission accordingly before it receives the next DCI. In embodiments, UE can report the capability to e B to report its soft buffer, and processing capability.
  • Example 292 includes an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-107, 215-291 or any other method or process described herein.
  • Example 293 includes one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-107, 215-291, or any other method or process described herein.
  • Example 294 includes an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-107, 215-291, or any other method or process described herein.
  • Example 295 includes a method, technique, or process as described in or related to any of examples 1-107, 215-291, or portions or parts thereof.
  • Example 296 includes an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-107, 215-291, or portions thereof.
  • Example 297 includes a signal as described in or related to any of examples 1-107, 215-291, or portions or parts thereof.
  • Example 298 includes a signal in a wireless network as shown and described herein.
  • Example 299 includes a method of communicating in a wireless network as shown and described herein.
  • Example 300 includes a system for providing wireless communication as shown and described herein.
  • Example 301 includes a device for providing wireless communication as shown and described herein.
  • Various embodiments may include any suitable combination of the above-described embodiments including alternative (or) embodiments of embodiments that are described in conjunctive form (and) above (e.g., the "and” may be “and/or”).
  • some embodiments may include one or more articles of manufacture (e.g., non-transitory computer-readable media) having instructions, stored thereon, that when executed result in actions of any of the above-described embodiments.
  • some embodiments may include apparatuses or systems having any suitable means for carrying out the various operations of the above-described embodiments.

Landscapes

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

Abstract

Selon certains modes de réalisation, l'invention concerne un processeur qui peut identifier une unité de ressources (RU) de liaison descendante (DL) qui comprend uniquement un bloc de ressources (RB) dans un domaine de fréquence et une seule sous-trame dans un domaine temporel. De plus, le RB peut comprendre une pluralité de sous-porteuses dans un spectre sans licence. Une interface radiofréquence (RF) couplée au processeur peut faciliter, sur la base de la RU DL, une transmission DL relative à une opération de l'Internet des objets à bande étroite (NB-IdO) dans le spectre sans licence. D'autres modes de réalisation peuvent être décrits et/ou revendiqués.
PCT/US2018/045761 2017-08-10 2018-08-08 Communication de canal de commande de l'internet des objets à bande étroite sans licence WO2019032676A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US201762543862P 2017-08-10 2017-08-10
US62/543,862 2017-08-10
US201762544274P 2017-08-11 2017-08-11
US62/544,274 2017-08-11
CNPCT/CN2017/098029 2017-08-18
CN2017098029 2017-08-18

Publications (1)

Publication Number Publication Date
WO2019032676A1 true WO2019032676A1 (fr) 2019-02-14

Family

ID=65271778

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/045761 WO2019032676A1 (fr) 2017-08-10 2018-08-08 Communication de canal de commande de l'internet des objets à bande étroite sans licence

Country Status (1)

Country Link
WO (1) WO2019032676A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021163539A1 (fr) * 2020-02-14 2021-08-19 Qualcomm Incorporated Configuration de liaison descendante à modulation d'amplitude en quadrature 16 (16-qam)
CN113692719A (zh) * 2019-03-29 2021-11-23 苹果公司 新无线电(nr)的混合自动重传请求(harq)传输
US11502892B2 (en) 2020-04-22 2022-11-15 Nokia Technologies Oy Modulation adjustment for 16-QAM in narrowband IoT

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016208897A1 (fr) * 2015-06-22 2016-12-29 엘지전자 주식회사 Procédé de transmission de canal de liaison montante et dispositif nb-ido
WO2017116114A1 (fr) * 2015-12-27 2017-07-06 Lg Electronics Inc. Procédé et appareil permettant de définir une unité de ressources de base pour un équipement utilisateur nb-iot dans un système de communication sans fil
WO2017121620A1 (fr) * 2016-01-11 2017-07-20 Sony Corporation Espacement de sous-porteuses de signalisation dans un système de communication d'internet des objets à bande étroite
US20170223725A1 (en) * 2014-08-01 2017-08-03 Intel IP Corporation Pdcch design for narrowband deployment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170223725A1 (en) * 2014-08-01 2017-08-03 Intel IP Corporation Pdcch design for narrowband deployment
WO2016208897A1 (fr) * 2015-06-22 2016-12-29 엘지전자 주식회사 Procédé de transmission de canal de liaison montante et dispositif nb-ido
WO2017116114A1 (fr) * 2015-12-27 2017-07-06 Lg Electronics Inc. Procédé et appareil permettant de définir une unité de ressources de base pour un équipement utilisateur nb-iot dans un système de communication sans fil
WO2017121620A1 (fr) * 2016-01-11 2017-07-20 Sony Corporation Espacement de sous-porteuses de signalisation dans un système de communication d'internet des objets à bande étroite

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE ET AL.: "Discussion on NR operation in unlicensed spectrum", RI-1701619, 3GPP TSG RAN WG1 MEETING #88, 6 February 2017 (2017-02-06), XP051208786 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113692719A (zh) * 2019-03-29 2021-11-23 苹果公司 新无线电(nr)的混合自动重传请求(harq)传输
CN113692719B (zh) * 2019-03-29 2024-03-15 苹果公司 新无线电(nr)的混合自动重传请求(harq)传输
WO2021163539A1 (fr) * 2020-02-14 2021-08-19 Qualcomm Incorporated Configuration de liaison descendante à modulation d'amplitude en quadrature 16 (16-qam)
US11888674B2 (en) 2020-02-14 2024-01-30 Qualcomm Incorporated 16-quadrature amplitude modulation (16-QAM) downlink configuration
US11502892B2 (en) 2020-04-22 2022-11-15 Nokia Technologies Oy Modulation adjustment for 16-QAM in narrowband IoT

Similar Documents

Publication Publication Date Title
US11659564B2 (en) Radio control channel resource set design
US11096043B2 (en) Downlink control information format for ultra-reliable physical downlink control channel
US11569954B2 (en) Demodulation reference signal and phase-tracking reference signal port indication
US10912071B2 (en) Reliability mechanisms for physical downlink control channel (PDCCH) transmissions in new radio (NR) systems
US20220086824A1 (en) Resource allocation for physical uplink control channel during initial access in nr-unlicensed
US11076318B2 (en) Vehicle-to-Everything (V2X) communication authorization in Fifth Generation (5G) systems
EP3949540B1 (fr) Signal de reveil basé sur le canal physique de contrôle en liaison descendante
EP3462795B1 (fr) Système de communication mobile, équipement utilisateur, noeud d'accès, émetteur-récepteur, circuiterie de bande de base, appareil, procédé et supports lisibles par machine et programmes informatiques pour traiter des signaux de bande de base
US10873962B2 (en) Mechanisms for handling uplink grants indicating different physical uplink shared channel starting positions in a same subframe
US11070320B2 (en) Resource element (RE) mapping in new radio (NR)
US11219046B2 (en) Two-tone physical uplink shared channel for machine type communications
US20220201515A1 (en) Enhanced physical downlink control channel monitoring
CN113475144A (zh) 用于新无线电(nr)中的ue内复用的系统和方法
US11363608B2 (en) Unlicensed narrowband internet of things control channel communication
US10952186B2 (en) Reserved resource elements for hybrid automatic repeat request bits
CN113940022A (zh) 跨时隙调度功率节省技术
WO2019032676A1 (fr) Communication de canal de commande de l'internet des objets à bande étroite sans licence
CN113875308A (zh) 在未许可频谱上运行的nr系统中的宽带载波中的上行链路(ul)传输和载波聚合

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

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

Country of ref document: EP

Kind code of ref document: A1