WO2017136000A1 - Conception de pbch pour un internet des objets à bande étroite (nb-iot) - Google Patents

Conception de pbch pour un internet des objets à bande étroite (nb-iot) Download PDF

Info

Publication number
WO2017136000A1
WO2017136000A1 PCT/US2016/053127 US2016053127W WO2017136000A1 WO 2017136000 A1 WO2017136000 A1 WO 2017136000A1 US 2016053127 W US2016053127 W US 2016053127W WO 2017136000 A1 WO2017136000 A1 WO 2017136000A1
Authority
WO
WIPO (PCT)
Prior art keywords
mib
bits
circuitry
processing circuitry
narrowband
Prior art date
Application number
PCT/US2016/053127
Other languages
English (en)
Inventor
Ralf Matthias Bendlin
Debdeep CHATTERJEE
Utsaw KUMAR
Holger Neuhaus
Seunghee Han
Marta MARTINEZ TARRADELL
Seau S. Lim
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
Priority to EP16889632.2A priority Critical patent/EP3411987A4/fr
Publication of WO2017136000A1 publication Critical patent/WO2017136000A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0041Arrangements at the transmitter end
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045Arrangements at the receiver end
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00Modulated-carrier systems
    • H04L27/26Systems using multi-frequency codes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • H04L5/0064Rate requirement of the data, e.g. scalable bandwidth, data priority
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056Systems characterized by the type of code used
    • H04L1/0067Rate matching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056Systems characterized by the type of code used
    • H04L1/0071Use of interleaving
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/08Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system

Definitions

  • Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3 GPP LTE- A (LTE Advanced) networks, and 5G networks, although the scope of the embodiments is not limited in this respect. Some embodiments relate to a physical broadcast channel (PBCH) design for narrowband Internet- of-Thmgs (NB-IoT).
  • PBCH physical broadcast channel
  • 3GPP LTE systems With the increase in different types of devices communicating with various network devices, usage of 3GPP LTE systems has increased. The penetration of mobile devices (user equipment or UEs) in modern society has continued to drive demand for a wide variety of networked devices in a number of disparate environments. The use of networked UEs using 3GPP LTE systems has increased in all areas of home and work life. Fifth generation (5G) wireless systems are forthcoming, and are expected to enable even greater speed, connectivity, and usability.
  • 5G Fifth generation
  • the 3GPP introduced a narrowband Internet-of-Things (NB-
  • the 3GPP LTE NB-IoT specifications define a Radio Access Technology (RAT) for a cellular Internet-of-Things (CIoT) based on a non-backward-compatible variant of the evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) standard specifically tailored towards improved indoor coverage, support for a massive number of low throughput devices, low- delay sensitivity, ultra-low device cost, low device power consumption and (optimized) network architecture.
  • RAT Radio Access Technology
  • UMTS Universal Mobile Telecommunications System
  • E-UTRA evolved Universal Mobile Telecommunications System
  • FIG. 1 is a functional diagram of a 3GPP network in accordance with some embodiments.
  • FIG . 2 is a block diagram of a User Equipment (UE) in accordance with some embodiments.
  • UE User Equipment
  • FIG. 3 is a block diagram of an Evol ved Node-B (eNB) in accordance with some embodiments.
  • eNB Evol ved Node-B
  • FIG. 4 illustrates example narrowband physical broadcast channel (NB-PBCH) processing, in accordance with some embodiments.
  • NB-PBCH narrowband physical broadcast channel
  • FIG 5 illustrates example NB-PBCH resource element mapping with repetitions inside a code block, in accordance with some embodiments.
  • FIG. 6 illustrates example NB-PBCH resource element mapping with continuous mapping inside a code block, in accordance with some embodiments.
  • FIG. 7 illustrates a block diagram of narrowband master information block (NB-MIB) decoding using a code block with bit sequence repetitions, in accordance with some embodiments.
  • FIG. 8 is a flow diagram illustrating example functionalities for communicating information using an NB-PBCH, in accordance with some embodiments.
  • FIG. 9 illustrates a block diagram of a communication device such as an eNB or a UE, in accordance with some embodiments.
  • FIG. 1 shows an example of a portion of an end-to-end network architecture of a Long Term Evolution (LTE) network with various components of the network in accordance with some embodiments.
  • LTE and LTE-A networks and devices are referred to merely as LTE networks and devices.
  • the network 100 may comprise a radio access network (RAN) (e.g., as depicted, the E-UTRAN or evolved universal terrestrial radio access network) 101 and the core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together through an S I interface 1 15.
  • RAN radio access network
  • EPC evolved packet core
  • the RAN 101 includes Evolved Node-B's (eNB) 104 (which may operate as base stations) for communicating with User Equipment (UE) 102.
  • the eNBs 104 may include macro eNBs and low power (LP) eNBs, such as micro, pico or femto eNBs.
  • the eNB 104 may transmit a dow nlink control message to the UE 102 to indicate an allocation of physical uplink control channel (PUCCH) channel resources.
  • the UE 102 may receive the downlink control message from the eNB 104, and may transmit an uplink control message to the eNB 104 in at least a portion of the PUCCH channel resources.
  • PUCCH physical uplink control channel
  • the MME 122 is similar in function to the control plane of legacy Serving GPRS Support Nodes (SGSN).
  • the MME 122 manages mobility aspects in access such as gateway selection and tracking area list management.
  • the serving GW 124 terminates the interface toward the RAN 101 , and routes data packets between the RAN 101 and the core network 120.
  • it may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter-3GPP mobility.
  • the serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.
  • the PDN GW 126 terminates a SGi interface toward the packet data network (PDN).
  • the PDN GW 126 routes data packets between the EPC 120 and the external PDN, and may be a key node for policy enforcement and charging data collection. It may also provide an anchor point for mobility w ith non-LTE accesses.
  • the external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domain.
  • IMS IP Multimedia Subsystem
  • the PDN GW 126 and the serving GW 124 may be implemented in one physical node or separated physical nodes.
  • the eNBs 104 may terminate the air interface protocol and may be the first point of contact for a UE 102. At least some of the eNBs 104 may be in a cell 106, in which the eNBs 104 of the cell 106 may be controlled by the same processor or set of processors. In some embodiments, an eNB 104 may be in a single ceil 106, while in other embodiments the eNB 104 may be a member of multiple cells 106. In some embodiments, an eNB 104 may fulfill various logical functions for the RAN
  • UEs 102 may be configured to perform RNC (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller functions
  • UEs 102 may be configured to
  • Orthogonal frequency-division multiplexing (OFDM) communication signals with an eNB 104 over a multicarrier communication channel in accordance with an OFDMA communication technique.
  • the OFDM signals may comprise a plurality of orthogonal subcarriers.
  • Each of the eNBs 104 may be able to transmit a reconfiguration message to each UE
  • the reconfiguration message may contain reconfiguration information including one or more parameters that indicate specifics about reconfiguration of the UE 102 upon a mobility scenario (e.g., handover) to reduce the latency involved in the handover.
  • the parameters may include physical layer and layer 2 reconfiguration indicators, and a security key update indicator.
  • the parameters may be used to instruct the UE 102 to avoid or skip one or more of the processes indicated to decrease messaging between the UE 102 and the network.
  • the network may be able to automatically route packet data between the UE 102 and the new eNB 104 and may be able to provide the desired information between the eNBs 104 involved in the mobility.
  • the application is not limited to this, however, and additional embodiments are described in more detail below.
  • the S I interface 115 is the interface that separates the RAN 101 and the EPC 120. It is split into two parts: the Sl-U, which carries traffic data between the eNB 104 and the serving GW 124, and the Sl-MME, which is a signaling interface between the eNB 104 and the MME 122.
  • the X2 interface is the interface between eNB 104.
  • the X2 interface comprises two parts, the X2-C and X2-U.
  • the X2-C is the control plane interface between the eNB 104
  • the X2-U is the user plane interface between the eNB 104.
  • LP cells are typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with very dense phone usage, such as train stations.
  • the term low power (LP) eNB refers to any suitable relatively low power eNB for implementing a narrower cell (narrower than a macro cell) such as a femtocell, a picocell, or a micro cell.
  • Femtocell eNBs are typically provided by a mobile network operator to its residential or enterprise customers.
  • a femtocell is typical ly the size of a residential gateway or smaller and generally connects to the user's broadband line.
  • a picocell is a wireless communication system typically covering a small area, such as in-building (offices, shopping malls, train stations, etc.), or more recently in-aircraft.
  • a picocell eNB can generally connect through the X2 link to another eNB such as a macro eNB through its base station controller (BSC) functionality.
  • BSC base station controller
  • LP eNB may be implemented with a picocell eNB since it is coupled to a macro eNB via an X2 interface.
  • Picocell eNBs or other LP eNBs may incorporate some or all functionality of a macro eNB. In some cases, this may be referred to as an access point base station or enterprise femtocell.
  • a resource block (also called physical resource block (PRB)) may be the smallest unit of resources that can be allocated to a UE.
  • a resource block may be 180 kHz wide in frequency and 1 slot long in time. In frequency, resource blocks may be either 12 x 15 kHz subcarriers or 24 x 7.5 kHz subcarriers wide. For most channels and signals, 12 subcarriers may be used per resource block.
  • both the uplink and downlink frames may be 10ms and may be frequency (full-duplex) or time (half-duplex) separated.
  • Time Division Duplexed the uplink and downlink subframes may be transmitted on the same frequency and may be multiplexed in the time domain.
  • a downlink resource grid may be used for downlink transmissions from an eNB to a UE.
  • the grid may be a time-frequency grid, which is the physical resource in the downlink in each slot.
  • Each column and each row of the resource grid may correspond to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain may correspond to one slot.
  • Each resource grid may comprise a number of the above resource blocks, which describe the mapping of certain physical channels to resource elements.
  • a downlink resource grid may be used for downlink transmissions from an eNB 104 to a UE 102, while uplink transmission from the UE 102 to the eNB 104 may utilize similar techniques.
  • the grid may 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 correspond 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.
  • Each resource grid comprises a number of resource blocks (RBs), which describe the mapping of certain physical channels to resource elements.
  • RBs resource blocks
  • Each resource block comprises a collection of resource elements in the frequency domain and may represent the smallest quanta of resources that currently can be allocated.
  • Each subframe may be partitioned into the PDCCH and the PDSCH.
  • the physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to a UE 102 (FIG. 1).
  • the physical downlink control channel (PDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It also informs the UE 102 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel.
  • HARQ hybrid automatic repeat request
  • downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 102 within a cell) may be performed at the eNB 104 based on channel quality information fed back from the UE 102 to the eNB 104, and then the downlink resource assignment information may be sent to the UE 102 on the control channel (PDCCH) used for (assigned to) the UE 102.
  • PDCCH control channel
  • the PDCCH uses CCEs (control channel elements) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols are first organized into quadruplets, which are then permuted using a sub-block inter-leaver for rate matching. Each PDCCH is transmitted using one or more of these control channel elements (CCEs), where each CCE corresponds to nine sets of four physical resource elements known as resource element groups (REGs). Four QPSK symbols are mapped to each REG.
  • CCEs control channel elements
  • REGs resource element groups
  • the network 100 may be compliant with the
  • a NB-loT carrier may comprises one legacy LTE Physical Resource Block (PRB) corresponding to a system bandwidth of 180kHz for a subcarrier spacing of 15kHz.
  • LTE NB-loT (or NB-LTE) may be based on Orthogonal Frequency-Division Multiple Access (OFDM A) in the downlink (DL) and Single-Carrier Frequency- Division Multiple Access (SC-FDMA) in the uplink (UL).
  • OFDM A Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single-Carrier Frequency- Division Multiple Access
  • Different numerologies may be supported and the embodiments herein shall apply to any such numerology.
  • the NB-loT physical layer design may use a subset of the channels defined for legacy LTE systems.
  • An NB-loT UE (such as the UE 102) may perform a ceil search to identify a suitable cell to connect to the Internet.
  • the NB-loT UE 102 may attempt to detect a narrowband Primary Synchronization Signal (NB-PSS) 130.
  • the NB-loT UE 102 may also use the NB-PSS 130 to synchronize its clock with the NB-loT network 100 and to detect the symbol boundaries of the OFDM waveforms.
  • NB-PSS Primary Synchronization Signal
  • the NB-loT UE 102 may obtain the downlink subframe and frame timing as well as the Physical Cell ID (PCI) of the NB-loT carrier using a narrowband Secondary Synchronization Signal (NB-SSS) 131. From the cell ID and the radio frame synchronization, the UE may proceed to decode the narrowband Physical Broadcast Channel (NB-PBCH) 132, which may contain scheduling information for additional system information
  • NB-PBCH narrowband Physical Broadcast Channel
  • a narrowband master information block (NB- MIB) 133 may also be transmitted to the UE 102 via the NB-PBCH 132. Additional details about the ⁇ - ⁇ 133 composition are provided herein below.
  • NB-loT system information may enable the NB- loT UE 102 to initiate a Random Access (RA) procedure to attach to the NB- IoT network 100.
  • the network 100 may respond to the random access procedure with a Random Access Response (RAR).
  • RAR Random Access Response
  • the random access procedure may allow the network to configure the NB-loT UE 102 for communication with the network, and may comprise a contention resolution procedure.
  • the network can configure the NB-loT UE 102 with cell-specific and UE-specific Radio Resource Control (RRC) parameters to control the NB-loT UE's transmission and reception behavior.
  • RRC Radio Resource Control
  • NB-loT UE 102 may be scheduled by a NB-PDCCH (with the exception of the Random Access Channel (RACH)).
  • the NB-PDCCH may convey Downlink Control Information (DCI) from the eNodeB to the NB-loT UE 102 that schedules narrowband physical downlink shared channel (NB-PDSCH) and narrowband physical uplink shared channel (NB-PUSCH) transmissions in the downlink and uplink, respectively.
  • DCI Downlink Control Information
  • NB-PDSCH narrowband physical downlink shared channel
  • NB-PUSCH narrowband physical uplink shared channel
  • Other channels may not be needed in an NB-LTE system but are not precluded,
  • demodulation of the NB-PBCH, NB-PDCCH, and NB-PDSCH may be based on Cell-specific Reference Signals (CRS), Demodulation Reference Signals (DMRS) or Narrowband Reference Signals (NB-RS) although these are not meant to be construed in a limiting sense and other naming conventions are not precluded.
  • CRS Cell-specific Reference Signals
  • DMRS Demodulation Reference Signals
  • NB-RS Narrowband Reference Signals
  • different channels may be modulated using different reference signals.
  • a single channel may be demodulated using several reference signals.
  • the NB-PBCH may be demodulated using NB-RS
  • the NB-PDCCH may be demodulated using CRS.
  • the NB-PDCCH may ⁇ be demodulated using CRS when the NB-IoT UE 102 is in good coverage conditions, whereas other NB-IoT UEs may use both CRS and NB-RS to demodulate the NB-PDCCH.
  • circuitry 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 executes one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware or software.
  • FIG. 2 is a functional diagram of a User Equipment (UE) in accordance with some embodiments.
  • the UE 200 may be suitable for use as a UE 102 as depicted in FIG. 1.
  • the UE 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, and multiple antennas 210A-210D, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • other circuitry or arrangements may include one or more elements or components of the application circuitry 202, the baseband circuitry 204, the RF circuitry 206 or the FEM circuitry 208, and may also include other elements or components in some cases.
  • processing circuitry may include one or more elements or components, some or ail of which may be included in the application circuitry 202 or the baseband circuitry 204.
  • transceiver circuitry may include one or more elements or components, some or all of which may be included in the RF circuitry 206 or the FEM circuitry 208. These examples are not limiting, however, as the processing circuitry or the transceiver circuitry may also include other elements or components in some cases.
  • the application circuitry 202 may include one or more application processors.
  • the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi- core processors.
  • the processor(s) may include any combination of general- purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/ storage to enable various applications or operating systems to run on the system to perform one or more of the functionalities described herein.
  • the baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206.
  • Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206.
  • the baseband circuitry 204 may include a second generation (2G) baseband processor 204a, third generation (3G) baseband processor 204b, fourth generation (4G) baseband processor 204c, or other baseband processor(s) 204d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 204 e.g., one or more of baseband processors 204a-d
  • 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 204 may include Fast-Fourier Transform (FFT), preceding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 204 may include Low Density Parity Check (LDPC) encoder/decoder functionality, optionally alongside other techniques such as, for example, block codes, convolutional codes, turbo codes, or the like, which may be used to support legacy protocols.
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 204 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EL!TRAN) protocol including, for example, physical (PHY), media ECC6SS control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), or radio resource control (RRC) elements.
  • a central processing unit (CPU) 204e of the baseband circuitry 204 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 204f.
  • the audio DSP(s) 204f 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
  • the constituent components of the baseband circuitry 204 and the application circuitry 202 may be implemented together such as, for example, on a system on chip (SOC).
  • SOC system on chip
  • the baseband circuitry 204 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 204 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 (WP AN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WP AN wireless personal area network
  • RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium, in various embodiments, the RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204.
  • RF circuitry 206 may also include a transmit signal path which may include circuitry to up- convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.
  • the RF circuitry 206 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 206 may include mixer circuitry 206a, amplifier circuitry 206b and filter circuitry 206c.
  • the transmit signal path of the RF circuitry 206 may include filter circuitry 206c and mixer circuitry 206a.
  • RF circuitry 206 may also include synthesizer circuitry 2()6d for synthesizing a frequency for use by the mixer circuitry 206a of the receive signal path and the transmit signal path.
  • the mixer circuitry 206a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d.
  • the amplifier circuitry 206b may be configured to amplify the down- converted signals and the filter circuitry 206c 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
  • Output baseband signals may be pro vided to the baseband circuitry 204 for further processing.
  • the output baseband signals may be zero -frequency baseband signals, although this is not a requirement.
  • mixer circuitry 206a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 206a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206d to generate RF output signals for the FEM circuitry 208.
  • the baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206c.
  • the filter circuitry 206c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • LPF low-pass filter
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for quadrature
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a may be arranged for direct downconversion or direct upconversion, respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a 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. In some alternate
  • the output baseband signals and the input baseband signals may ⁇ be digital baseband signals.
  • the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.
  • 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 206d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 206d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 206d may be configured to synthesize an output frequency for use by the mixer circuitry 206a of the RF ' circuitry 206 based on a frequency input and a divider control input.
  • the synthesizer circuitry 2()6d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCQ), although that is not a requirement.
  • VCI voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 204 or the applications processor 202 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 202.
  • Synthesizer circuitry 206d of the RF circuitry 206 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 VCQ period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
  • synthesizer circuitry 206d 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 io each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 206 may include an IQ/poiar converter.
  • FEM circuitry 208 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more of the antennas 210A-D, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing.
  • FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 210A-D.
  • the FEM circuitry 208 may include a
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 206).
  • the transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 210.
  • the UE 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • FIG. 3 is a functional diagram of an Evolved Node-B (eNB) in accordance with some embodiments.
  • the eNB 300 may be a stationary non-mobile device.
  • the eNB 300 may be suitable for use as an eNB 104 as depicted in FIG. 1.
  • the components of eNB 300 may be included in a single device or a plurality of devices.
  • the eNB 300 may include physical layer (PHY) circuitry 302 and a transceiver 305, one or both of which may enable transmission and reception of signals to and from the UE 200, other eNBs, other UEs or other devices using one or more antennas 301A-B.
  • PHY physical layer
  • the physical layer circuitry 302 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals.
  • physical layer circuitry 302 may include LDPC encoder/decoder functionality, optionally along-side other techniques such as, for example, block codes, convolutional codes, turbo codes, or the like, which may be used to support legacy protocols.
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the transceiver 305 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range.
  • RF Radio Frequency
  • the physical layer circuitry 302 and the transceiver 305 may be separate components or may be part of a combined component.
  • some of the described functionality related to transmission and reception of signals may be performed by a combination that may include one, any or all of the physical layer circuitry 302, the transceiver 305, and other components or layers.
  • the eNB 300 may also include medium access control layer (MAC) circuitry 304 for controlling access to the wireless medium.
  • the eNB 300 may also include processing circuitry 306 and memory 308 arranged to perform the operations described herein.
  • the eNB 300 may also include one or more interfaces 3 0, which may enable communication with other components, including other eNB 104 (FIG. 1), components in the EPC 120 (FIG. 1) or other network components.
  • the interfaces 310 may enable communication with other components that may not be shown in FIG. 1, including components external to the network.
  • the interfaces 310 may be wired or wireless or a combination thereof.
  • the antennas 210A-D (in the UE) and 301A-B (in the eNB) may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, nionopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • the antennas 210A-D, 301 A-B may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • the UE 200 or the eNB 300 may be a mobile device and may be a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device such as a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive or transmit information wirelessly.
  • PDA personal digital assistant
  • a laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device such as a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may
  • Mobile devices or other devices in some embodiments may be configured to operate according to other protocols or standards, including IEEE 802.11 or other IEEE standards.
  • the UE 200, eNB 300 or other device may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the UE 200 and the eNB 300 are each illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), or other hardware elements.
  • DSPs digital signal processors
  • some elements may comprise one or more microprocessors, DSPs, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements may refer to one or more processes operating on one or more processing elements.
  • Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
  • a computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • an apparatus used by the UE 200 or eNB 300 may include various components of the UE 200 or the eNB 300 as shown in FIG. 2 and FIG. 3. Accordingly, techniques and operations described herein that refer to the UE 200 (or 102) may be applicable to an apparatus for a UE. In addition, techniques and operations described herein that refer to the eNB 300 (or 104) may be applicable to an apparatus for an eNB.
  • FIG. 4 illustrates example narrowband physical broadcast channel (NB-PBCH) processing, in accordance with some embodiments.
  • the example NB-PBCH processing flow 400 may start at 402, when an NB-MIB may be generated by the eNB 104.
  • the NB-MIB may be 16 bits long.
  • CRC cyclic redundancy check
  • the entire transport block may be used to calculate 16 CRC parity bits.
  • the CRC bits may be scrambled to indicate the number of NB-RS antenna ports, on which the NB-PBCH 132 is transmitted, whereby NB-RS is the narrowband reference signal used for demodulation of the NB-PBCH.
  • NB-RS is the narrowband reference signal used for demodulation of the NB-PBCH.
  • two scrambling sequences suffice for the NB-RS antenna port indication as a maximum of two NB-RS antenna ports is defined.
  • channel coding may be performed by the eNB 104.
  • tail biting convoiutional encoding may be used for the NB-PBCH channel coding.
  • the encoded bits may be rate matched (e.g., as explained further in reference to FIGS. 5 and 6).
  • the rate matched bits may be scrambled.
  • PCI Physical Cell Identifier
  • the eNB 104 may perform modulation mapping. More specifically, the NB-PBCH may be transmitted using QPSK modulation. At 414, the modulated symbols may be mapped to layers for a single NB-RS antenna port and more than one NB-RS antenna port, respectively. At 416, the modulated symbols may be pre-coded for a single NB-RS antenna port and more than one NB-RS antenna port, respectively. At 418 resource element (RE) mapping may be performed, and the OFDM signal may be generated at 420.
  • RE resource element
  • FIG. 5 illustrates example NB-PBCH resource element mapping with repetitions inside a code block, in accordance with some embodiments.
  • the NB-PBCH may be transmitted in subframe #0 of every radio frame and the BCH transport channel passes a narrowband Master Information Block (NB-MTB) to the physical layer (PHY) every transmission time interval (TTI) of 640ms.
  • NB-MTB narrowband Master Information Block
  • the NB-MIB may be split into a plurality of independently decodabie code blocks (e.g., eight blocks) of 80ms duration each.
  • FIG. 5 and FIG. 6 illustrate two possible resource element mappings for the NB-PBCH.
  • the NB-PBCH does not use the first three symbols in a subframe and is rate matched around four LTE CRS ports, and assuming it is always rate matched around two NB-RS antenna ports with the same NB-RS density per antenna port as LTE CRS antenna ports 0 and 1 , a single radio frame provides 100 resource elements for NB-PBCH transmission, or, alternatively, 200 hits (which can be within subframe #0 of each frame),
  • the broadcast channel may pass one NB-
  • each of the code blocks 502a - 502h can include a plurality of subframes - Al - A8, Bl - B8, ... , HI - H8, respectively.
  • Each of the code blocks 502a - 502h can be self-decodable, and the 80ms boundaiy of each block can be detected by the UE based on the NB-SSS.
  • Subframes Al - H8 are each 10ms, providing 64 transmit opportunities for the NB-MIB.
  • each of the eight s ubframes within one code block is identical and self-decodable.
  • each of the code blocks 502a - 502h uses a 200-bit scrambling sequence, so that 200 bits representing a portion of the rate-matched 1600 bits for the NB-MIB are repeated eight times (i.e., within each subframe) within a given code biock. More specifically, a short scrambling sequence of length 1,600 bits may be segmented into eight scrambling sequences of 200 bits each, and one of the 200-bit sequences may be used as illustrated in FIG. 5.
  • FIG. 6 illustrates example NB-PBCH resource element mapping with continuous mapping inside a code block, in accordance with some embodiments.
  • the broadcast channel may pass one NB-MIB to the PHY every TTI, or 640ms.
  • the encoded bits may be rate matched to 12,800 bits, which may be segmented into eight code blocks (602a - 602h) of 80ms duration each, with 1,600 bits within each code biock.
  • the rate matched and encoded NB-MIB (i.e., 12,800 bits of the rate matched NB- MIB) can be mapped continuously to the NB-PBCH resources (i.e., eight code blocks 602a - 602h), as depicted in FIG. 6.
  • NB-PBCH resources i.e., eight code blocks 602a - 602h
  • a long scrambling sequence of 1,600 bits may be used so that rate matching is with respect to all resources within one ⁇ and unique 1600 bits are mapped to each of the 8 code blocks 602a - 602h.
  • a long scrambling sequence of length 12,800 bits may be segmented into eight scrambling sequences of 1 ,600 bits each, and one of the 1 , 600-bit sequences may be used as illustrated in FIG. 6.
  • FIG. 7 illustrates a block diagram of narrowband master information block (NB-MIB) decoding using a code block with bit sequence repetitions, in accordance with some embodiments.
  • decoding circuitry 700 within a UE, which can include a deinterlacer 710 and a decoder 720 for decoding an NB-MIB which has been rate matched to 1600 bits as illustrated in FIG. 5 (i. e., 1600 bits spread over eight blocks of 200 bits, with 200 bits being repeated eight times within each code biock).
  • a NB-MIB payload may be 34 bits and including 16 CRC bits
  • each output of a convolutional encoder at the eNB denoted vi
  • can include 50 bits i.e., four 50-bit blocks may fit into one radio frame, or sub-frame #0 of a radio frame.
  • the first block v0 gets repeated twice as often as the other two blocks vl and v2, as illustrated in FIG. 7. More specifically, the bit sequence v0-vl-v2-v0 is being repeated 8 times within code block A, once in each of the subfraraes SF1-SF8 in code block A.
  • the repetition of block vO within code block A may be beneficial for phase estimation at the UE, but may result in reduced coding efficiency at the eNB.
  • 150 bits from each subframe may be deinterlaced and decoded, resulting in the 50-bit combination 730 of the NB- MIB (34 bits) and CRC (16 bits).
  • the NB-MIB can be rate matched to 12,800 bits (as in FIG. 6), which may result in a more regular repetition of blocks vi within each frame.
  • the above exemplary descriptions and accompanying drawings are construed in an illustrative and not in a limiting manner. Specific designations in bit size are provided only as an example, whereas novel aspects of the disclosure may include the repetitive (e.g., as in FIG. 5) or continuous (e.g., as in FIG. 6) mapping of the rate matched bits to the physical resources within one code block segment of 80ms.
  • FIG. 8 is a flow diagram illustrating example functionalities for communicating information using an NB-PBCH, in accordance with some embodiments.
  • the example method 800 may start at 802 when a plurality of code blocks received on a Narrowband Physical Broadcast Channel (NB-PBCH) during a Master Information Block transmission time interval (MIB TTI) are detected.
  • NB-PBCH Narrowband Physical Broadcast Channel
  • MIB TTI Master Information Block transmission time interval
  • the UE 102 may receive one or more of the code blocks 502a - 502h during the MIB TTI.
  • a code block of the plurality of code blocks may be partitioned into a plurality of subframes. For example, and as seen in FIG.
  • a code block (e.g., A) may be partitioned into a plurality of subframes Al - A8.
  • Each of the plurality of subframes may include a bit sequence representing an encoded Narrowband Master Information Block (NB-MIB) and the bit sequence is repeated a number of times within the code block.
  • NB-MIB Narrowband Master Information Block
  • the bit sequence may be decoded to obtain the NB-MIB.
  • the bit sequence in the first subframe Al may be deinterlaced and decoded to obtain the 50 bits 730 representing the NB-MIB and the CRC.
  • the NB-MIB payload may also be redesigned as explained herein below.
  • the NB-IoT may obtain the timing with respect to the 640ms TTI during which the NB- MIB payload does not change.
  • SFN system frame number
  • four more bits may be needed and may be included in the NB-MIB payload. Therefore, from a physical layer perspective, at least four bits may ⁇ be used in the NB-MIB to signal the system frame number.
  • the UE may be informed about the CRS configuration of the LTE donor cell for NB-IoT in-band operation.
  • the CRS frequency shift is already known from the NB-SSS detection since NB-SSS and PSS/SSS may indicate different PCIs but not different v-shifts.
  • NB-IoT SIB1 transmissions may be restricted to non-MBSFN subframes only, i.e., subframe # 5 in ever ⁇ 7 odd frame and subframe #9 in every even frame assuming NB-PBCH is transmitted in subframe #0, NB-PSS in subframe #4, and NB-SSS in subframe #9 of every odd radio frame. If NB-SIB1 transmissions are restricted to these options, no valid subframe information in the NB-MIB is required for NB- SIB .1 reception and any information pertaining to MBSFN subframes may be signaled to the NB-IoT UE at a later stage, e.g., in the NB-SIB1 payload.
  • Additional subframes may be reserved for paging.
  • SIB1 subframes every 20ms in subframe #9 and subframe #5 is available for paging.
  • every 10ms subframe #5 is used for NB-SIB1 transmission and in that case, paging occasions may only map to subframe #9 of ever ⁇ 7 even radio frame.
  • At least partial information on the valid subframes for SIB1 scheduling is indicated in the NB-MIB.
  • a bitmap (up to 6 bits for 6 non-MBSFN subframes) may be used.
  • subframe #5 may be used in addition to signaling the aforementioned bitmap.
  • the complete 40-bit bitmap for mbsfri-SubframeConfigList may be carried in the NB-MIB.
  • the same subframes for SIB1 transmissions as for in-band mode may be used for simplicity, although any other subframe can also be used as well.
  • such information may be included in the SIB1 scheduling information itself.
  • the maximum control format indicator (CFI) of the LTE donor cell may be indicated to the NB-IoT UE in the NB-MIB. Alternatively, this may happen at a later stage, i.e., in the system information messages or via dedicated RRC signaling.
  • the maximum CFI may also be fixed by specification.
  • the LTE PRB index in which the NB-PBCH is transmitted may also be included in the NB-MIB.
  • seven bits may be included in the NB-MIB to signal the LTE PRB index in which the NB-IoT system is operated within the LTE donor cell.
  • the range of the LTE PRB index may exceed 100 indices to also include PRBs in the guard-band.
  • less bits may be used to signal the LTE PRB index because only those PRB indices whose center frequencies fall within a certain frequency offset to the NB-IoT channel raster may be included in the enumeration of NB-IoT PRBs.
  • the relative power offset between resource elements carrying LTE CRS and those carrying NB- RS may be signaled to the NB-IoT UE.
  • the power offset may be included in the NB-MIB.
  • the PRB index may be signaled in the NB-MIB whereas the power offset is included at a later stage, e.g., the system information broadcast.
  • the power offset may be signaled to the NB-IoT UE via dedicated RRC signaling.
  • the number of LTE CRS antenna ports may be indicated in the NB-MIB.
  • two bits may be used to signal the number of LTE CRS antenna ports, namely, ⁇ 0, 1,2,4 ⁇ or ⁇ reserved, 1,2,4 ⁇ although other orderings are not precluded.
  • the number of LTE CRS antenna ports may be indicated by a single bit in the NB-MIB whereby a ZERO indicates that the number of LTE CRS antenna ports is the same as the number of NB-RS antenna ports, e.g., 1 or 2, and a ONE indicates that the number of LTE CRS antenna ports is fo ur.
  • the number of NB-RS antenna ports may not be encoded in the scrambling of the CRC bits of the NB-MIB but
  • a dedicated bit in the NB-MIB signals the number of NB-RS antenna ports.
  • a ZERO may indicate one NB-RS antenna port and a logical ONE indicates two NB-RS antenna ports.
  • the System Information Value Tag may be the same size as in legacy LTE systems (i.e., 5 bits) and may be included in the NB-MIB.
  • the SystemlnformationValueTag may be defined as an INTEGER (0..3.1 ) for NB- loT (same as systemlnfoValueTag in LTE and eMTC).
  • the schedufinglnfoSIB 1 -BR-rl 3 information element (5 bits) defined as INTEGER (0..31) may be included in the NB-MIB and may contain an index to a table that defines
  • One bit may be included in the NB-MIB to indicate when system information message for access congestion (AC) is (de)activated.
  • the mode of operation (one of in-band, guard- band, or standalone) may be indicated (e.g., by two bits) in the NB-MIB.
  • the mode of operation may be implicitly indicated by the aforementioned parameters.
  • the PRB index may signal in-band (0-99), guard-band (100-1 10), or standalone (111) mode of operation although other values are not precluded.
  • a non-zero number of LTE CRS antenna ports may signal in-band mode of operation, if the number of LTE CRS antenna ports is set to zero.
  • the PRB index may be used to distinguish between guard-band and standalone mode of operation.
  • the PRB index signals standalone mode of operation, otherwise the PRB index distinguishes between in-band and guard-band mode of operation. In instances when the PRB index indicates guard-band mode of operation, the UE may ignore the indicated number of LTE CRS antenna ports accordingly.
  • the LTE system bandwidth needs to be indicated to the NB-IoT UE in the NB-MIB pay load to facilitate frequency hopping for NB-SIB1 transmission depends on the detailed design of the frequency hopping scheme.
  • multiple PRB indices may be provided in the NB-MIB, and frequency hopping may be applied over these indicated PRBs.
  • the system bandwidth of the LTE donor cell may be indicated in the NB-MIB and a specified frequency hopping pattern like in LTE Rel. 13 eMTC may be used for SIB1 transmissions.
  • multiple NB-IoT PRB indices may be indicated in the NB-MIB to allow NB-IoT multi-carrier operation, e.g., for the sake of load balancing/offloading of SIB 1 transmissions and/or NB-IoT unicast or common control transmissions.
  • different PRB indices/carriers may be indicated for SIB1 transmissions via the NB-MIB, e.g., as part of the SIB1 scheduling information.
  • NB-IoT UEs may chose an NB- loT carner/PRB index based on such NB-MIB signaling of multiple NB-IoT PRB indices in conjunction with their coverage level, e.g., to group NB-IoT UEs of the same coverage level onto the same NB-IoT carrier and NB-IoT UEs of different coverage levels onto different NB-IoT carriers.
  • a flag (1 bit) in the NB-MIB may indicate whether frequency hopping is enabled for unicast and/or common control transmissions.
  • this information may be used to implicitly turn off frequency hopping for unicast and/or common control transmissions.
  • three bits may be included in the NB-MIB to signal the system bandwidth of the LTE donor ceil. Since there are only six LTE system bandwidths, one representation of the three bits may indicate frequency- hopping is disabled whereas six representations may signal a specified frequency hopping pattern for the corresponding LTE system bandwidth.
  • frequency hopping may be specified for a subset of the LTE system bandwidths. In this case, one or two bits may be used to signal the system bandwidth of the LTE donor cell in the NB-MIB.
  • one bit may be included in the NB-MIB to signal the duplex mode, i.e., frequency-division duplex (FDD) or time- division duplex (TDD).
  • FDD frequency-division duplex
  • TDD time- division duplex
  • the minimum offset is +/-2.5kHz for even bandwidth configurations and +/-7.5kHz for odd bandwidth configurations.
  • the raster offset information may be indicated in the NB-MIB using one bit.
  • the system bandwidth information may implicitly indicate whether the offset values are +/-2.5kHz (even bandwidth) or +/-7.5kHz (odd bandwidth). Thus, only one bit may suffice to indicate raster frequency offset information.
  • the raster offset information may be indicated in the NB-MIB using two bits for +1-2.5kHz and +/-7.5kHz.
  • FIG. 9 illustrates a block diagram of a communication device such as an eNB or a UE, in accordance with some embodiments.
  • the communication device 900 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 900 may operate in the capacity of a server communication device, a client communication device, or both in server-client network environments. In an example, the communication device 900 may act as a peer
  • the communication device 900 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device.
  • the term "communication device” shall also be taken to include any collection of communication de vices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner, in an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general- purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Communication device (e.g., UE) 900 may include a hardware processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a mam memory 904 and a static memory 906, some or all of which may communicate with each other via an interlink (e.g., bus) 908.
  • the communication device 900 may further include a display unit 910, an alphanumeric input device 912 (e.g., a keyboard), and a user interface (UI) navigation device 914 (e.g., a mouse).
  • the display unit 910, input device 912 and UI navigation device 914 may be a touch screen display.
  • the communication device 900 may additionally include a storage device (e.g., drive unit) 916, a signal generation device 918 (e.g., a speaker), a network interface device 920, and one or more sensors 921, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • the communication device 900 may include an output controller 928, such as a serial (e.g. , universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc. ) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g. , universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc. ) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal
  • the storage device 916 may include a communication device readable medium 922 on which is stored one or more sets of data structures or instructions 924 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 924 may also reside, completely or at least partially, within the main memory 904, within static memory 906, or within the hardware processor 902 during execution thereof by the communication device 900.
  • one or any combination of the hardware processor 902, the main memory 904, the static memory 906, or the storage device 916 may constitute communication device readable media.
  • the term “communication device readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 924.
  • the term "communication device readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 900 and that cause the communication device 900 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or earning data structures used by or associated with such instructions.
  • Non-limiting communication device readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of
  • communication device readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read- Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read- Only Memory (EEPROM)) and flash memory devices
  • magnetic disks such as internal hard disks and removable disks
  • magneto-optical disks Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • communication device readable media may include non-transitory communication device readable media.
  • communication device readable media may include communication device readable media that is not a transitory propagating signal.
  • the instructions 924 may further be transmitted or received over a communications network 926 using a transmission medium via the network interface device 920 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802, 1 1 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMaxCg)), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others.
  • LAN local area network
  • WAN wide area network
  • packet data network e.g., the Internet
  • mobile telephone networks e.g., cellular networks
  • wireless data networks e.g., Institute of Electrical and Electronics Engineers (IEEE) 802, 1 1 family of standards known as Wi-Fi®, IEEE 802.16 family
  • the network interface device 920 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 926.
  • the network interface de vice 920 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MI SO) techniques.
  • SIMO single-input multiple-output
  • MIMO MIMO
  • MI SO multiple-input single-output
  • the network interface device 920 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or earning instructions for execution by the communication device 900, and includes digital or analog communications signals or other intangible medium to facilitate
  • Example 1 is an apparatus of an evol ved Node B (eNB) configured to communicate with a user equipment (UE), the apparatus comprising: memory; and processing circuitry, the processing circuitry configured to: generate a Narrowband Master Information Block (NB-MIB) for transmission on a Narrowband Physical Broadcast Channel (NB-PBCH); encode the NB-MIB and cyclic redundancy check bits appended to the NB- MIB; segment the encoded NB-MIB into a plurality of independently decodable code blocks, each code block configured for transmission to the UE during a Master Information Block transmission time interval (MIB TTI); and partition resources reserved for the NB-PBCH within the MIB TTI into a plurality of partitions, wherein a bit sequence representing a portion of the encoded NB-MIB is repeated a number of times within the code block during NB-PBCH transmissions within the partitions.
  • NB-MIB Narrowband Master Information Block
  • MIB TTI Master Information Block transmission time interval
  • Example 2 the subject matter of Example 1 optionally includes wherein the processing circuitry is further configured to: segment the NB-MIB into 8 independently decodable code blocks of 80ms duration each for transmission during a 640ms MIB TTI.
  • Example 3 the subject matter of any one or more of
  • Examples 1-2 optionally include wherein the processing circuitry is further configured to: rate match the encoded NB-MIB to 1600 rate matched bits.
  • the subject matter of Example 3 optionally includes wherein the processing circuitry is further configured to: partition a short scrambling sequence of length 1 ,600 bits into a plurality of scrambling sequence segments of 200 bits each; and scramble the rate matched bits using one of the scrambling sequences of length 200 bits so that the bit sequence is of length 200 bits and is repeated eight times within the code block.
  • Example 5 the subject matter of any one or more of Examples 1-4 optionally include a transceiver coupled to an antenna, the transceiver configured to transmit the plurality of independently decodable code blocks using at least one narrowband (NB) Internet-of-Things (loT) carrier signal, the at least one NB-IoT carrier signal comprising a legacy LTE Physical Resource Block (PRB) corresponding to a system bandwidth of 180kHz for a subcarrier spacing of 15kHz.
  • NB narrowband
  • LoT Internet-of-Things
  • PRB Physical Resource Block
  • Example 6 the subject matter of Example 5 optionally includes wherein the NB-MIB comprises information indicative of a power offset between a legacy reference signal and a NB-loT reference signal.
  • Example 7 the subject matter of any one or more of Examples 5-6 optionally include wherein the transceiver is configured to transmit information indicative of a power offset between a legacy reference signal and a NB-IoT reference signal in a system information block type 1 (SIB 1 ).
  • SIB 1 system information block type 1
  • Example 8 the subject matter of any one or more of Examples 1- 7 optionally include wherein the NB-MIB comprises at least four bits indicating a system frame number (SFN).
  • SFN system frame number
  • Example 9 the subject matter of any one or more of
  • Examples 1- 8 optionally include wherein the NB-MIB indicates a number of cell specific reference signal (CRS) antenna ports associated with a donor cell of the eNB.
  • CRS cell specific reference signal
  • Example 10 the subject matter of Example 9 optionally includes wherein the number of antenna ports is indicated via a single bit, the single bit indicating one of: the number of antenna ports is the same as a number of NB-RS antenna ports or the number of antenna ports is four.
  • the subject matter of any one or more of Examples 1-10 optionally include wherein the NB-MIB comprises at least one bit indicating a physical resource block (PRB), in which the NB-PBCH is transmitted.
  • PRB physical resource block
  • Example 12 the subject matter of any one or more of
  • Examples 1- 11 optionally include wherein the NB-MIB comprises at least one bit indicating an NB-IoT mode of operation, wherein the mode of operation is one of an in-hand, a guard-band, or a standalone mode of operation.
  • Example 13 the subject matter of Example 12 optionally includes wherein the mode of operation is indicated by a physical resource block (PRB) index or the number of ceil specific reference signal (CRS) antenna ports or a combination thereof within the NB-MIB.
  • PRB physical resource block
  • CRS ceil specific reference signal
  • Example 14 the subject matter of any one or more of Examples 1-13 optionally include wherein the NB-MIB comprises information indicative of system bandwidth associated with a donor cell of the eNB.
  • Example 15 the subject matter of any one or more of
  • Examples 1-14 optionally include wherein the NB-MIB comprises a control format indicator (CFI).
  • CFI control format indicator
  • Example 16 the subject matter of any one or more of
  • Examples 1- 15 optionally include wherein the processing circuitry is further configured to: subsequent to transmission of the NB-MIB, generate a narrowband system information block type 1 (NB-SIB1) for transmission to the UE, the NB-SIB1 comprising a control format indicator (CFI) for a donor LTE cell.
  • NB-SIB1 narrowband system information block type 1
  • CFI control format indicator
  • Example 17 the subject matter of any one or more of Examples 1-16 optionally include wherein the NB-MIB comprises information indicative of whether frequency hopping is enabled for unicast or common control transmissions.
  • Example 18 the subject matter of any one or more of
  • Examples 1-17 optionally include wherein the NB-MIB comprises at least one bit indicating a frequency-division duplex (FDD) or time-division duplex (TDD) mode of operation.
  • the subject matter of any one or more of Examples 1-18 optionally include wherein the NB-MIB comprises at least two bits indicating channel raster offset.
  • Example 20 the subject matter of Example 19 optionally includes wherein the NB-MIB comprises information indicative of system bandwidth and a bit indicative of channel raster information associated with the system bandwidth.
  • Example 21 is an apparatus of an evolved Node B (eNB) configured to communicate with a user equipment (UE), the apparatus comprising: memory; and processing circuitry, the processing circuitry configured to: encode a Narrowband Master Information Block (NB-MIB) and cyclic redundancy check bits to generate encoded NB-MIB; scramble a plurality of rate matched bits corresponding to the encoded NB-MI B, using a long scrambling sequence of a fixed length; and segment the scrambled rate matched bits into a plurality of independently decodable code blocks, each code block configured for transmission to the UE on a Narrowband Physical Broadcast Channel (NB-PBCH) during a Master Information Block transmission time interval (MIB TTI), wherein the scrambled rate matched bits are continuously mapped within resource elements reserved for the NB- PBCH within the MIB TTI, without a repetition of bit sequences between the code blocks.
  • NB-MIB Narrowband Master Information Block
  • MIB TTI Master Information Block transmission time
  • Example 22 the subject matter of Example 21 optionally includes wherein the processing circuitry is further configured to: rate match the encoded NB-MIB to generate the plurality of rate matched bits representing the encoded NB-MIB.
  • Example 23 the subject matter of Example 22 optionally includes wherein the processing circuitry is further configured to: rate match the encoded NB-MIB to generate 12,800 rate matched bits.
  • Example 24 the subject matter of any one or more of Examples 22-23 optionally include wherein the processing circuitry is further configured to: partition a long scrambling sequence of length 12,800 bits into a plurality of scrambling sequence segments of 1,600 bits each; and scramble the plurality of rate matched bits using one of the scrambling sequence segments of length 1,600 bits so that the scrambled rate matched bits are segmented into eight code blocks for transmission to the UE during the MIB TTI.
  • Example 25 the subject matter of Example 24 optionally includes wherein the processing circuitry is further configured to: modulation map, layer map and pre-code the 12,800 scrambled rate matched bits to generate a plurality of pre-coded bits; and continuously map the plurality of pre-coded bits into the eight code blocks, without the repetition of bit sequences between the code blocks,
  • Example 26 is a computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (LIE), the one or more processors to configure the UE to: detect a plurality of code blocks recei ved on a Narrowband Physical Broadcast Channel (NB- PBCH) during a Master Information Block transmission time interval (MIB TTI): partition a code block of the plurality of code blocks into a plurality of subframes, wherein each of the plurality of subframes comprises a bit sequence representing an encoded Narrowband Master Information Block (NB-MIB) and the bit sequence is repeated a number of times within the code block; and decode the bit sequence to obtain the NB-MIB.
  • LIE user equipment
  • Example 27 the subject matter of Example 26 optionally includes wherein the one or more processors further configure the UE to: decode a narrowband secondary synchronization signal (NB-SSS) to obtain downlink subframe and frame timing, wherein the plurality of code blocks are detected based on the downlink subframe and frame timing.
  • NB-SSS narrowband secondary synchronization signal
  • Example 28 the subject matter of any one or more of
  • Examples 26-27 optionally include wherein the bit sequence is 200 bits long and is mapped to a single 80 ms timing window associated with a single code block of the plurality of code blocks.
  • Example 29 the subject matter of any one or more of Examples 26-28 optionally include wherein the one or more processors further configure the UE to: deinterlace a portion of the bit sequence to obtain deinterlaced bit sequence; and decode the deinterlaced bit sequence to obtain the NB-MIB with appended cyclic redundancy check bits.
  • Example 30 the subject matter of any one or more of Examples 26-29 optionally include wherein the one or more processors further configure the UE to: subsequent to obtaining the NB-MIB, receive a narrowband system information block type 1 (NB-SIB1), the NB-SIB1 comprising a control format indicator (CFI) for a donor LTE cell.
  • NB-SIB1 narrowband system information block type 1
  • CFI control format indicator
  • Example 31 is an apparatus of a user equipment configured to communicate with an evolved Node B (eNB), the apparatus comprising: means for detecting a plurality of code blocks received on a Narrowband Physical Broadcast Channel (NB-PBCH) during a Master Information Block transmission time interval (MTB TTI); means for partitioning a code block of the plurality of code blocks into a plurality of subframes, wherein each of the plurality of subframes comprises a bit sequence representing an encoded Narrowband Master Information Block (NB-MIB) and the bit sequence is repeated a number of times within the code block; and means for decoding the bit sequence to obtain the NB-MIB.
  • NB-PBCH Narrowband Physical Broadcast Channel
  • MTB TTI Master Information Block transmission time interval
  • Example 32 the subject matter of Example 31 optionally includes wherein the apparatus further comprises: means for, subsequent to obtaining the NB-MIB, receiving a narrowband system information block type 1 (NB-SIBl), the NB-SIB1 comprising a control format indicator (CFI) for a donor LTE cell.
  • NB-SIBl narrowband system information block type 1
  • CFI control format indicator
  • embodiments may include fewer features than those disclosed in a particular example.
  • the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment.
  • the scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

Abstract

L'invention concerne un appareil d'un équipement d'utilisateur (UE) configuré pour communiquer avec un nœud B évolué (eNB). L'UE peut comprendre une mémoire et un montage de circuits de traitement couplé à la mémoire. Le montage de circuits de traitement peut être configuré pour détecter une pluralité de blocs codés reçue sur un canal de diffusion physique à bande étroite (NB-PBCH) pendant un intervalle de temps de transmission d'un bloc d'informations maître (MIB-TTI). Le montage de circuits de traitement peut en outre être configuré pour diviser un bloc codé de la pluralité de blocs codés en une pluralité de sous-trames. Chacune de la pluralité de sous-trames contient une séquence binaire représentant un bloc d'informations maître à bande étroite (NB-MIB) codé, et la séquence binaire est répétée un certain nombre de fois dans le bloc codé. La séquence binaire peut être décodée afin d'obtenir le NB-MIB.
PCT/US2016/053127 2016-02-05 2016-09-22 Conception de pbch pour un internet des objets à bande étroite (nb-iot) WO2017136000A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP16889632.2A EP3411987A4 (fr) 2016-02-05 2016-09-22 Conception de pbch pour un internet des objets à bande étroite (nb-iot)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662292062P 2016-02-05 2016-02-05
US62/292,062 2016-02-05

Publications (1)

Publication Number Publication Date
WO2017136000A1 true WO2017136000A1 (fr) 2017-08-10

Family

ID=59499803

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/053127 WO2017136000A1 (fr) 2016-02-05 2016-09-22 Conception de pbch pour un internet des objets à bande étroite (nb-iot)

Country Status (2)

Country Link
EP (1) EP3411987A4 (fr)
WO (1) WO2017136000A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107621648A (zh) * 2017-09-13 2018-01-23 西安航光卫星测控技术有限公司 一种带窄带蜂窝物联网通信功能的北斗定位装置及实现方法
US20210067282A1 (en) * 2018-01-03 2021-03-04 Lenovo (Beijing) Limited Non-anchor carrier frequency offset indication
US11210074B2 (en) 2016-06-27 2021-12-28 Intel Corporation On-demand binary translation state map generation
US20230134170A1 (en) * 2021-11-03 2023-05-04 At&T Intellectual Property I, L.P. Mobile broadband and machine type communication network coexistence

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150078329A1 (en) * 2012-05-23 2015-03-19 Huawei Technologies Co., Ltd. Method, Network Device, and Base Station for Paging Narrowband Terminal

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150078329A1 (en) * 2012-05-23 2015-03-19 Huawei Technologies Co., Ltd. Method, Network Device, and Base Station for Paging Narrowband Terminal

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"NB-IoT broadcast channel design", 3GPP TDOC. RI-160126, January 2016 (2016-01-01)
"NB-IoT Broadcast Channel Design", R1-160126, 3GPP TSG RAN WG1 NB-IOT AD-HOC MEETING, 12 January 2016 (2016-01-12), XP051053445 *
"NB-PBCH design", 3GPP TDOC. RI-160023, January 2016 (2016-01-01)
HUAWEI ET AL.: "NB-PBCH design", R1-160023, 3GPP TSG RAN WG1 NB-IOT AD-HOC MEETING, 12 January 2016 (2016-01-12), XP051053346 *
SAMSUNG: "NB-PBCH Design", R1-160138, 3GPP TSG RAN WG1 NB-IOT AD-HOC MEETING, 12 January 2016 (2016-01-12), XP051053457 *
See also references of EP3411987A4 *
ZTE: "NB-PBCH design for NB-IoT", R1-160042, 3GPP TSG RAN WG1 NB-IOT AD-HOC MEETING, 11 January 2016 (2016-01-11), XP051053365 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11210074B2 (en) 2016-06-27 2021-12-28 Intel Corporation On-demand binary translation state map generation
CN107621648A (zh) * 2017-09-13 2018-01-23 西安航光卫星测控技术有限公司 一种带窄带蜂窝物联网通信功能的北斗定位装置及实现方法
US20210067282A1 (en) * 2018-01-03 2021-03-04 Lenovo (Beijing) Limited Non-anchor carrier frequency offset indication
US20230134170A1 (en) * 2021-11-03 2023-05-04 At&T Intellectual Property I, L.P. Mobile broadband and machine type communication network coexistence

Also Published As

Publication number Publication date
EP3411987A4 (fr) 2020-01-08
EP3411987A1 (fr) 2018-12-12

Similar Documents

Publication Publication Date Title
US10512073B2 (en) Apparatus and method for IoT control channel
US11831479B2 (en) Device and method of configurable synchronization signal and channel design
US11245480B2 (en) Devices and methods for robust measurement and data receiving
US11122580B2 (en) Evolved node-b (ENB), user equipment (UE) and methods for flexible duplex communication
US11438872B2 (en) Narrowband internet of things devices and method of operation thereof
US20190335493A1 (en) User equipment (ue), evolved node-b (enb) and methods for multiplexing new radio (nr) physical uplink shared channel (nr pusch) and nr physical uplink control channel (nr pucch)
CN107548539B (zh) 用于第五代网络的物理下行链路控制信道
KR102527905B1 (ko) 5g 네트워크의 동적 파티션 자원 할당
EP3178281B1 (fr) Équipement d'utilisateur et procédés d'allocation et de signalisation de ressources de temps pour les communications de dispositif à dispositif (d2d)
US10862605B2 (en) Discovery reference signaling for dynamically-timed transmissions
US11082950B2 (en) User equipment (UE) and method of sidelink data communication in fifth generation (5G) new radio (NR) things networks
WO2017136000A1 (fr) Conception de pbch pour un internet des objets à bande étroite (nb-iot)
WO2017146781A1 (fr) Équipement utilisateur (ue) et procédé de communication de liaison latérale dans des réseaux des choses de nouvelle radio (nr) de cinquième génération (5g)
EP3437381A1 (fr) Échelonnement d'un trafic sans surveillance dans un système d'évolution à long terme (lte) après une interdiction

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016889632

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016889632

Country of ref document: EP

Effective date: 20180905