EP3453207A1 - Verfahren für mehrträgerbetrieb mit mehreren verankerungsträgern im schmalbandigen internet der dinge - Google Patents

Verfahren für mehrträgerbetrieb mit mehreren verankerungsträgern im schmalbandigen internet der dinge

Info

Publication number
EP3453207A1
EP3453207A1 EP17723590.0A EP17723590A EP3453207A1 EP 3453207 A1 EP3453207 A1 EP 3453207A1 EP 17723590 A EP17723590 A EP 17723590A EP 3453207 A1 EP3453207 A1 EP 3453207A1
Authority
EP
European Patent Office
Prior art keywords
message
iot
iot carrier
carrier
repetitions
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP17723590.0A
Other languages
English (en)
French (fr)
Inventor
Debdeep CHATTERJEE
Ralf Bendlin
Seau S. Lim
Marta MARTINEZ TARRADELL
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Intel IP Corp
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 Corp filed Critical Intel IP Corp
Publication of EP3453207A1 publication Critical patent/EP3453207A1/de
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel

Definitions

  • a variety of wireless cellular communication systems have been implemented or are being proposed, including a 3rd Generation Partnership Project (3GPP) Universal Mobile Telecommunications System (UMTS), a 3GPP Long-Term Evolution (LTE) system, a 3GPP LTE-Advanced (LTE-A) system, and a 5th Generation wireless / 5th Generation mobile networks (5G) system.
  • Next-generation wireless cellular communication systems may provide support for massive numbers of user devices like Narrow-Band Internet-of- Things (NB-IoT) devices, Cellular Internet-of-Things (CIoT) devices, or Machine-Type Communication (MTC) devices.
  • NB-IoT Narrow-Band Internet-of- Things
  • CCIoT Cellular Internet-of-Things
  • MTC Machine-Type Communication
  • Such devices may have very low device complexity, may be latency -tolerant, and may be designed for low throughput and very low power consumption.
  • FIG. 1 illustrates a scenario of an anchor NB-IoT carrier and a non-anchor
  • NB-IoT carrier for Multi-Carrier Operation MCO
  • FIG. 2 illustrates a scenario of repetitions of Narrow-Band System Information
  • Block 1 (SIB1-NB) transmissions, in accordance with some embodiments of the disclosure.
  • Fig. 3 illustrates a scenario of Starting Radio Frame Numbers (SRFNs) of
  • FIG. 4 illustrates an Evolved Node B (eNB) and a User Equipment (UE), in accordance with some embodiments of the disclosure.
  • eNB Evolved Node B
  • UE User Equipment
  • FIG. 5 illustrates hardware processing circuitries for a UE for MCO with multiple anchor carriers in Narrow-Band Intemet-of-Things (NB-IoT) systems, in accordance with some embodiments of the disclosure.
  • NB-IoT Narrow-Band Intemet-of-Things
  • FIG. 6 illustrates hardware processing circuitries for an eNB for MCO with multiple anchor carriers in NB-IoT systems, in accordance with some embodiments of the disclosure.
  • Fig. 7 illustrates methods for a UE for MCO with multiple anchor carriers in
  • Fig. 8 illustrates methods for an eNB for MCO with multiple anchor carriers in NB-IoT systems, in accordance with some embodiments of the disclosure.
  • Fig. 9 illustrates example components of a UE device, in accordance with some embodiments of the disclosure.
  • Various wireless cellular communication systems have been implemented or are being proposed, including a 3rd Generation Partnership Project (3GPP) Universal Mobile Telecommunications System (UMTS), a 3GPP Long-Term Evolution (LTE) system, a 3GPP LTE-Advanced (LTE- A) system, and a 5th Generation wireless system / 5th Generation mobile networks (5G) system / 5th Generation new radio (NR) system.
  • 3GPP 3rd Generation Partnership Project
  • UMTS Universal Mobile Telecommunications System
  • LTE Long-Term Evolution
  • LTE- A 3GPP LTE-Advanced
  • 5G 5th Generation mobile networks
  • NR 5th Generation new radio
  • the 3GPP NB-IoT specifications describe a Radio Access Technology (RAT) for a cellular Intemet-of-Things (CIoT) system based on a non-backward-compatible variant of the Evolved UMTS Terrestrial Radio Access (E-UTRA) standard, which may support a massive number of low throughput devices, ultra-low device complexity and cost, low device power consumption, support for low delay sensitivity, improved indoor coverage, and optimized network architecture.
  • RAT Radio Access Technology
  • C-UTRA Evolved UMTS Terrestrial Radio Access
  • NB-IoT systems under development may support low complexity devices and
  • NB-IoT guard-band deployment e.g., deployment in a guard band of an LTE carrier
  • NB-IoT in-band deployment may comprise a legacy LTE Physical Resource Block (PRB) for in-band mode and its equivalent in stand-alone mode or guard-band modes (which may correspond to a system bandwidth of 180kHz).
  • PRB Physical Resource Block
  • a UE in an RRC connected mode with a first NB-IoT carrier may be directed to a second NB-IoT carrier via dedicated RRC signaling, and may retune from the current NB-IoT carrier to the second NB-IoT carrier for Downlink (DL) transmission, Uplink (UL) transmission, or both, in order to receive or transmit, respectively.
  • MCO Multi-Carrier Operation
  • FIG. 1 illustrates a scenario of an anchor NB-IoT carrier and a non-anchor
  • An NB-IoT scenario 100 may comprise a first NB-IoT carrier 1 10, a second NB-IoT carrier 120, and a UE 130.
  • First NB-IoT carrier 1 10 may be operable to provide NB-IoT services over a geographic area within a first cell 11 1
  • second NB-IoT carrier 120 may be operable to provide NB-IoT services over a geographic area within a second cell 121.
  • first NB-IoT carrier 110 may support DL transmissions and/or UL transmissions with UE 130.
  • second NB-IoT carrier 120 may also support DL transmissions and/or UL transmissions with UE 130.
  • NB-IoT MCO e.g., in-band deployment with in-band deployment, in-band deployment with guard- band deployment, or guard-band deployment with guard-band deployment.
  • Both a guard- band and an in-band may be associated with the same LTE donor cell (e.g., a total span might not exceed 110 PRBs from the same Fast Fourier Transform (FFT)).
  • FFT Fast Fourier Transform
  • NB-IoT multi-carrier operation might not be supported for stand-alone deployment in combination with either guard-band deployment or in-band deployment.
  • stand-alone deployment in combination with standalone deployment may be allowed for NB-IoT MCO.
  • Some such embodiments may be constrained such that a total frequency span does not exceed 20 megaherz (MHz) and both NB-IoT carriers are synchronized (e.g., a time alignment error may not exceed a minimum requirement for intra-band contiguous carrier aggregation).
  • NB-IoT UE has received Narrow-Band Primary Synchronization Signal (NB-PSS), Narrow- Band Secondary Synchronization Signal (NB-SSS), Narrow-Band Physical Broadcast Channel (NB-PBCH), and/or System Information Block (SIB) transmissions, the NB-IoT UE might not rate match around NB-PBCH, NB-PSS, and/or NB-SSS.
  • NB-PDCCH Narrow-Band Physical Downlink Control Channel
  • NB-PDSCH Narrow- Band Physical Downlink Shared Channel
  • REs Resource Elements
  • a carrier may be termed an “anchor carrier” and/or an
  • anchor NB-IoT carrier if it carries NB-PSS, NB-SSS, NB-PBCH, Narrow-Band System Information Block 1 (SIB1-NB), and/or other Narrow-Band System Information (NB-SI) messages.
  • a carrier may otherwise be termed a “non-anchor carrier” and/or a “non-anchor NB-IoT carrier.”
  • carriers described with different terminology may benefit from the mechanisms and methods discussed herein (e.g., such as primary carriers and secondary carriers).
  • a UE directed to an additional NB-IoT carrier might be disposed to using the additional NB-IoT carrier for unicast traffic (e.g., primarily, or exclusively).
  • Some or all common control message transmissions, including procedures like Random Access (RA) and paging, may be performed on an anchor NB-IoT carrier.
  • RA Random Access
  • support of MCO for NB-IoT may be based on the presence of a single anchor NB-IoT carrier in the case of multiple carriers being configured for NB-IoT deployment.
  • support for MCO involving multiple anchor NB-IoT carriers may include various aspects.
  • a Physical Cell Identity (PCID) of a non-anchor NB-IoT carrier may optionally be different than a PCID of an associated anchor NB-IoT carrier, and otherwise may be the same the PCID of the associated anchor NB-IoT carrier.
  • PCID Physical Cell Identity
  • a parameter indicating that an NB-IoT carrier serves as an anchor for others e.g., a parameter such as "servesAsAnAnchorForOthers”
  • a predetermined value e.g., a value of "true”
  • a UE may assume the same available subframes as in an associated anchor NB-IoT carrier.
  • the available subframes may in turn be determined by and/or established by PSS, SSS, Master Information Block (MIB), System Information Block 1 (SIB1) and other System Information (SI) messages (or by their Narrow- Band (NB) counterparts), and/or by a signaled available-subframes bitmap.
  • PSS Packet Control Service
  • SSS Session Initiation Block
  • MIB Master Information Block
  • SIB1 System Information Block 1
  • SIB1 System Information Block 1
  • SI System Information
  • SI System Information
  • NB Narrow- Band
  • a UE may assume that a bitmap of available subframes for an anchor NB-IoT carrier may also be applied for a non-anchor NB-IoT carrier.
  • Some embodiments comprise the signaling of information to UEs for MCO operation regarding, for example, time-domain resources used for SIBl-NB and other NB-SI messages, signaling options to indicate a UE's rate-matching behavior, potential use of NB-PSS and/or NB-SSS in an additional NB-IoT carrier, and related UE behavior.
  • signals are represented with lines. Some lines may be thicker, to indicate a greater number of constituent signal paths, and/or have arrows at one or more ends, to indicate a direction of information flow. Such indications are not intended to be limiting. Rather, the lines are used in connection with one or more exemplary embodiments to facilitate easier understanding of a circuit or a logical unit. Any represented signal, as dictated by design needs or preferences, may actually comprise one or more signals that may travel in either direction and may be implemented with any suitable type of signal scheme. [0031] Throughout the specification, and in the claims, the term "connected" means a direct electrical, mechanical, or magnetic connection between the things that are connected, without any intermediary devices.
  • Coupled means either a direct electrical, mechanical, or magnetic connection between the things that are connected or an indirect connection through one or more passive or active intermediary devices.
  • circuit or “module” may refer to one or more passive and/or active components that are arranged to cooperate with one another to provide a desired function.
  • signal may refer to at least one current signal, voltage signal, magnetic signal, or data/clock signal.
  • the transistors in various circuits, modules, and logic blocks are Tunneling FETs (TFETs).
  • Some transistors of various embodiments may comprise metal oxide semiconductor (MOS) transistors, which include drain, source, gate, and bulk terminals.
  • MOS metal oxide semiconductor
  • the transistors may also include Tri-Gate and FinFET transistors, Gate All Around Cylindrical Transistors, Square Wire, or Rectangular Ribbon Transistors or other devices implementing transistor functionality like carbon nanotubes or spintronic devices.
  • MOSFET symmetrical source and drain terminals i.e., are identical terminals and are interchangeably used here.
  • a TFET device on the other hand, has asymmetric Source and Drain terminals.
  • A, B, and/or C means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • combinatorial logic and sequential logic discussed in the present disclosure may pertain both to physical structures (such as AND gates, OR gates, or XOR gates), or to synthesized or otherwise optimized collections of devices implementing the logical structures that are Boolean equivalents of the logic under discussion.
  • NB-IoT eNB may refer to a legacy LTE capable Evolved Node-B (eNB), a NB-IoT capable eNB, a Cellular Internet-of-Things (CIoT) capable eNB, a Machine-Type Communication (MTC) capable eNB, and/or another base station for a wireless
  • eNB Evolved Node-B
  • CIoT Cellular Internet-of-Things
  • MTC Machine-Type Communication
  • NB-IoT UE and “UE” may refer to a legacy LTE capable UE, an NB-IoT capable UE, a CIoT capable UE, an MTC capable UE, and/or another mobile equipment for a wireless communication system.
  • Various embodiments of eNBs and/or UEs discussed below may process one or more transmissions of various types. Some processing of a transmission may comprise demodulating, decoding, detecting, parsing, and/or otherwise handling a transmission that has been received.
  • an eNB or UE processing a transmission may determine or recognize the transmission's type and/or a condition associated with the transmission. For some embodiments, an eNB or UE processing a transmission may act in accordance with the transmission's type, and/or may act conditionally based upon the transmission's type. An eNB or UE processing a transmission may also recognize one or more values or fields of data carried by the transmission.
  • Processing a transmission may comprise moving the transmission through one or more layers of a protocol stack (which may be implemented in, e.g., hardware and/or software-configured elements), such as by moving a transmission that has been received by an eNB or a UE through one or more layers of a protocol stack.
  • a protocol stack which may be implemented in, e.g., hardware and/or software-configured elements
  • Various embodiments of eNBs and/or UEs discussed below may also generate one or more transmissions of various types. Some generating of a transmission may comprise modulating, encoding, formatting, assembling, and/or otherwise handling a transmission that is to be transmitted. In some embodiments, an eNB or UE generating a transmission may establish the transmission's type and/or a condition associated with the transmission. For some embodiments, an eNB or UE generating a transmission may act in accordance with the transmission's type, and/or may act conditionally based upon the transmission's type. An eNB or UE generating a transmission may also determine one or more values or fields of data carried by the transmission.
  • Generating a transmission may comprise moving the transmission through one or more layers of a protocol stack (which may be implemented in, e.g., hardware and/or software-configured elements), such as by moving a transmission to be sent by an eNB or a UE through one or more layers of a protocol stack.
  • a protocol stack which may be implemented in, e.g., hardware and/or software-configured elements
  • resources may span various Resource Blocks (RBs),
  • PRBs Physical Resource Blocks
  • time periods e.g., frames, subframes, and/or slots
  • allocated resources e.g., channels, Orthogonal Frequency -Division Multiplexing (OFMD) symbols, subcarrier frequencies, resource elements (REs), and/or portions thereof
  • OFMD Orthogonal Frequency -Division Multiplexing
  • REs resource elements
  • allocated resources e.g., channels, OFDM symbols, subcarrier frequencies, REs, and/or portions thereof
  • allocated resources e.g., channels, OFDM symbols, subcarrier frequencies, REs, and/or portions thereof
  • an NB-IoT carrier to which an NB-IoT UE is directed by dedicated RRC configuration is an anchor NB-IoT carrier for other NB-IoT UEs, then the first NB-IoT UE may be disposed to knowing the subframes used for NB-PSS, NB-SSS, NB-PBCH,
  • SIB l-NB and/or NB-SI messages.
  • Subframes used for transmission of NB-PSS, NB-SSS, and/or NB-PBCH may be predetermined (e.g., fixed by specification), and may therefore be common between different carriers. However, subframes for carrying SI may not be common between different carriers.
  • a number of repetitions of a SIBl -NB transmission, a Transport Block Size (TBS), and/or a specific SRFN (and/or specific subframes) used for transmission of SIBl -NB may be given by a signaled field in a Narrow-Band MIB (NB- MIB), which may be carried by an NB-PBCH, and a PCID.
  • NB- MIB Narrow-Band MIB
  • Fig. 2 illustrates a scenario of repetitions of SIBl-NB transmissions, in accordance with some embodiments of the disclosure.
  • a first case 210 may comprise a first set of repetitions 215 of a SIBl -NB transmission.
  • a second case 220 may comprise a second set of repetitions 225 of a SIBl -NB transmission.
  • a third case 230 may comprise a third set of repetitions 235 of a SIB l-NB transmission.
  • first set of repetitions 215 may comprise four repetitions of the SIBl -NB transmission.
  • second set of repetitions 225 may comprise eight repetitions of the SIBl -NB transmission.
  • third set of repetitions 235 may comprise sixteen repetitions of the SIBl -NB transmission.
  • third set of repetitions 235 may comprise any number of repetitions of the SIB l-NB transmission.
  • second set of repetitions 225 may comprise a greater number of repetitions of the SIB l-NB transmission than first set of repetitions 215.
  • third set of repetitions 235 may comprise a greater number of repetitions of the SIBl -NB transmission than second set of repetitions 225.
  • Fig. 3 illustrates a scenario of Starting Radio Frame Numbers (SRFNs) of
  • a first set of SRFN cases 310 may comprise a first SRFN 312, a second SRFN 314, a third SRFN 316, and a fourth SRFN 318.
  • a second set of SRFN cases 320 may comprise a first SRFN 322 and a second SRFN 324.
  • a third set of SRFN cases 330 may comprise a first SRFN 332 and a second SRFN 334.
  • first SRFN 312 may be a frame number 0, second
  • SRFN 314 may be a frame number 16
  • third SRFN 316 may be a frame number 32
  • fourth SRFN 318 may be a frame number 48.
  • first SRFN 322 may be a frame number 0 and/or second SRFN 324 may be a frame number 16.
  • first SRFN 332 may be a frame number 0 and/or second SRFN 334 may be a frame number 1.
  • SIB l-NB transmission a TBS, and an SFRN for a SIB l-NB transmission may be given by a field in an NB-MIB in accordance with Table 1 and/or Table 2 below.
  • Table 1 4-bit field in the NB-MIB to indicate TBS and
  • Table 2 Mapping from number of repetitions of SIB1 -NB and PCID to
  • starting radio frame numbers for the SIBl-NB repetitions may also be different.
  • a UE may assume that an anchor NB-IoT carrier and a non-anchor NB-IoT carrier use the same number of repetitions.
  • the UE may determine the starting radio frame number of SIBl-NB repetitions using the PCID of the non-anchor NB-IoT carrier.
  • the PCID value of a non-anchor NB-IoT carrier may be signaled to a UE, if it is different from the value for the UE's anchor NB-IoT carrier.
  • the number of repetitions of the SIBl-NB and the NB-PDSCH transmissions carrying NB-SI messages may be different between two carriers.
  • a UE's anchor NB-IoT carrier and non-anchor NB-IoT carrier may be in different modes of operation.
  • an anchor NB-IoT carrier may be deployed in a guard-band mode of operation
  • a non-anchor NB-IoT carrier may be deployed in an in- band mode of operation.
  • a significant difference in a number of REs available in a DL PRB-pair or a DL subframe such as up to 50% of REs in a guard-band mode of operation, which may be 152 REs, in comparison with 100 REs in an in-band mode of operation (assuming 3 symbols reserved for LTE Physical Downlink Control Channel (PDCCH), the presence of 4-port LTE Cell-Specific Reference Signal (CRS), and a 2-port Narrow-Band Reference Signals (NB-RS)).
  • PDCCH Physical Downlink Control Channel
  • CRS 4-port LTE Cell-Specific Reference Signal
  • NB-RS 2-port Narrow-Band Reference Signals
  • the number of repetitions of SIB1-NB, or the number of repetitions of another NB-SI transmission targeting the same coverage level may be significantly different, in order to avoid either over-dimensioning or under-provisioning in case the same number of repetitions is assumed for both cases.
  • Tx Transmit
  • PPAs power amplifiers
  • a network may multiplex UEs in different coverage levels on different
  • NB-IoT carriers e.g., an anchor NB-IoT carrier and a non-anchor NB-IoT carrier
  • common control channels which may include SIB1-NB and other NB-SI messages.
  • an eNB may target extended coverage and extreme coverage UEs on one NB-IoT carrier, and may target basic coverage UEs on the other NB-IoT carrier.
  • a number of repetitions used for SIB1-NB and other NB-SI messages may be markedly higher for the NB-IoT carrier targeting extended and extreme coverage UEs compared to those for the NB-IoT carrier targeting UEs in better coverage conditions.
  • the subframes used for SIB1-NB and other NB-SI messages may be different between two anchor carriers in a deployment, which may advantageously support better resource allocation flexibility and optimized operation. Accordingly, in some embodiments, instead of assuming the same number and location of subframes for SIB1-NB and other NB-SI message transmissions, time-domain scheduling information for SIB1-NB and other NB-SI messages may be signaled to a UE during RRC configuration directing it to another NB-IoT carrier (which may serve as an anchor NB-IoT carrier for other UEs).
  • SI scheduling related information might be sent to the
  • SI scheduling related information might be sent to the UE via broadcast RRC configuration signaling.
  • Dedicated signaling may facilitate improved flexibility of a network to reconfigure UEs to different NB-IoT carriers dynamically (e.g., based on a network load).
  • Some examples of dedicated signaling that might be used to carry SI scheduling related information may include an RRC Connection Reconfiguration message, an RRC Connection Setup message, an RRC Connection Resume message, and/or another DL RRC message in which a network may convey RRC configuration information.
  • a network may send SI scheduling related information through a broadcast channel on the premise that such information is common for one or more UEs (e.g., up to and including all UEs) redirected to the corresponding NB-IoT carrier.
  • Such information may be conveyed through an existing SIB, or through a new SIB. Conveying such information via broadcast signaling may be advantageous when a network shares much of, or all of, the information for each NB-IoT carrier, and the UE uses an NB-IoT carrier that it is reconfigured to use. In such embodiments, even if a UE gets reconfigured at a future time while being connected, it may be possible to use stored SI scheduling information.
  • a UE may decode before getting connected, or potentially after dedicated signaling indicates its reconfiguration to a new NB-IoT carrier.
  • a network may indicate, semi-statically, one or more UEs operating at different coverage enhancements (CE) levels to different carriers.
  • CE coverage enhancements
  • SI scheduling information may be broadcast, and after establishing an RRC connection, a UE may automatically start operating directly in another NB-IoT carrier (e.g., a non-anchor NB-IoT carrier) for future dedicated messages and/or unicast messages (e.g., as a default
  • a UE may wait until a network indicates that the UE may start operating in another NB-IoT carrier (e.g., a non-anchor NB-IoT carrier) considering associated signaling that has been broadcast, and potentially a new configuration sent to the UE through a dedicated NB-IoT carrier (e.g., an anchor NB-IoT carrier).
  • another NB-IoT carrier e.g., a non-anchor NB-IoT carrier
  • a dedicated NB-IoT carrier e.g., an anchor NB-IoT carrier
  • a 2-bit field may be used to signal a number of repetitions used for SIB1-NB transmissions (RSIBI-NB) within a 256 radio frame period.
  • RSIBI-NB SIB1-NB transmissions
  • an entire 4-bit field from an NB-MIB for a second anchor NB-IoT carrier, which may correspond to SIB1-NB scheduling information indicating both a TBS and an RSIBI-NB value, may be signaled to a UE via dedicated signaling.
  • scheduling information may be carried by a SIB1-NB transmission itself.
  • time- domain scheduling information for other NB-SI message transmission for the second anchor NB-IoT carrier e.g., details of the scheduling window and/or a number of repetitions within a scheduling window
  • some of, or all of, the scheduling information for transmission of other NB-SI messages (which may include time-domain resource scheduling information and/or TBS values) may be signaled to the UE.
  • a bitmap of subframes occupied by SI and subframes not occupied by SI may be provided. Such a bitmap may be applicable at certain instants in time, or with certain periodicity. For some embodiments, multiple different bitmaps may be provided, which may be applicable at various different instants in time, or with various different periodicities.
  • a cell-specific DL valid subframe configuration for an additional NB-IoT carrier may also be signaled to a UE via dedicated signaling (e.g., RRC signaling).
  • a cell-specific DL valid subframe configuration may be optionally signaled by an eNB using a 10-bit bitmap in a stand-alone mode or a guard-band mode, and/or by a 10-bit bitmap or a 40-bit bitmap in an in-band mode.
  • a UE may perform rate-matching around subframes used for
  • NB-PSS, NB-SSS, NB-PBCH, SIB1-NB, and/or other NB-SI messages on the additional NB-IoT carrier e.g., for any NB-PDCCH and/or NB-PDSCH transmissions that may coincide with the above-mentioned subframes
  • the UE may postpone any NB-PDCCH and/or NB-PDSCH transmissions to a next available valid DL subframe.
  • a UE may use knowledge of physical resources used for carrying the NB-PSS, NB-SSS, NB-PBCH, SIB1-NB, and/or other NB-SI messages for rate matching purposes, and might not be expected to detect or decode any of these signals or messages.
  • Some embodiments discussed herein may also apply to signaling of a UL valid subframes configuration (e.g., an NB-IoT UL subframe configuration) for an RRC- configured additional UL carrier (e.g., an NB-IoT UL carrier), if indication of UL valid subframes is supported for NB-IoT.
  • a UL valid subframes configuration e.g., an NB-IoT UL subframe configuration
  • RRC- configured additional UL carrier e.g., an NB-IoT UL carrier
  • an additional NB-IoT carrier may carry NB-PSS and/or NB-SSS only, and not NB-PBCH or system information (e.g., NB-SI).
  • NB-SI system information
  • an NB-IoT carrier may serve as an anchor for others (e.g., a parameter such as
  • a new parameter indicating that an NB-IoT carrier bears synchronization signals may also be signaled as part of an RRC configuration, or via SIB signaling on anchor NB-IoT carriers, to indicate that an additional NB-IoT carrier bears NB-PSS and/or NB-SSS transmissions.
  • a parameter such as “carrierHasSyncSignals”
  • Each of the two parameters may be operable to have a first value (e.g., a value of "true”) and/or a second value (e.g., a value of "false").
  • the parameter indicating that the carrier may serve as an anchor for others has the first value (e.g., "true")
  • the parameter indicating that the carrier bears synchronization signals e.g., the "carrierHasSyncSignals” parameter
  • the carrierHasSyncSignals may be assumed to have the first value (e.g., "true"), and might not be signaled.
  • a first parameter indicating that an NB-IoT carrier has common channels e.g., a parameter such as "carrierHasCommonChannels”
  • a second parameter indicating that the carrier bears synchronization signals e.g., the
  • carrierHasSyncSignals may be signaled to a UE by dedicated RRC signaling, or by SIB signaling on an anchor carriers.
  • a parameter indicating that a carrier may serve as an anchor for others e.g., the "servesAsAnAnchorForOthers” parameter
  • Each of the two parameters may have a first value (e.g., a value of "true") and/or a second value (e.g., a value of "false”) independent of each other.
  • a parameter indicating that an NB-IoT carrier has common channels e.g., the "carrierHasCommonChannels” parameter
  • the first value e.g., "true”
  • a parameter indicating that the carrier bears synchronization signals e.g., the "carrierHasSyncSignals” parameter
  • the signaling of these parameters may be provided corresponding to each candidate additional NB-IoT carrier that a UE may be subsequently directed to via dedicated RRC signaling.
  • NB-IoT carriers may be the same, and a single set of parameters may be configured. For example, some of, or all of, the NB-IoT carriers in a deployment carry NB-PSS and/or NB-SSS. Accordingly, a parameter indicating that a carrier has synchronization signals (e.g., the "carrierHasSyncSignals" parameter) may have a predetermined value (e.g., a value of "true") for all carriers within the MCO.
  • a parameter indicating that a carrier has synchronization signals e.g., the "carrierHasSyncSignals" parameter
  • a predetermined value e.g., a value of "true
  • Fig. 4 illustrates an eNB and a UE, in accordance with some embodiments of the disclosure.
  • Fig. 4 includes block diagrams of an eNB 410 and a UE 430 which are operable to co-exist with each other and other elements of an LTE network. High-level, simplified architectures of eNB 410 and UE 430 are described so as not to obscure the embodiments. It should be noted that in some embodiments, eNB 410 may be a stationary non-mobile device.
  • eNB 410 is coupled to one or more antennas 405, and UE 430 is similarly coupled to one or more antennas 425.
  • eNB 410 may incorporate or comprise antennas 405, and UE 430 in various embodiments may incorporate or comprise antennas 425.
  • antennas 405 and/or antennas 425 may comprise one or more directional or omni-directional antennas, including monopole antennas, dipole antennas, loop antennas, patch antennas, microstrip antennas, coplanar wave antennas, or other types of antennas suitable for transmission of RF signals.
  • antennas 405 are separated to take advantage of spatial diversity.
  • eNB 410 and UE 430 are operable to communicate with each other on a network, such as a wireless network.
  • eNB 410 and UE 430 may be in communication with each other over a wireless communication channel 450, which has both a downlink path from eNB 410 to UE 430 and an uplink path from UE 430 to eNB 410.
  • eNB 410 may include a physical layer circuitry 412, a MAC (media access control) circuitry 414, a processor 416, a memory 418, and a hardware processing circuitry 420.
  • MAC media access control
  • physical layer circuitry 412 includes a transceiver 413 for providing signals to and from UE 430.
  • Transceiver 413 provides signals to and from UEs or other devices using one or more antennas 405.
  • MAC circuitry 414 controls access to the wireless medium.
  • Memory 418 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory-based storage media), or any tangible storage media or non-transitory storage media.
  • Hardware processing circuitry 420 may comprise logic devices or circuitry to perform various operations.
  • processor 416 and memory 418 are arranged to perform the operations of hardware processing circuitry 420, such as operations described herein with reference to logic devices and circuitry within eNB 410 and/or hardware processing circuitry 420.
  • eNB 410 may be a device comprising an application processor, a memory, one or more antenna ports, and an interface for allowing the application processor to communicate with another device.
  • UE 430 may include a physical layer circuitry 432, a MAC circuitry 434, a processor 436, a memory 438, a hardware processing circuitry 440, a wireless interface 442, and a display 444.
  • a physical layer circuitry 432 may include a physical layer circuitry 432, a MAC circuitry 434, a processor 436, a memory 438, a hardware processing circuitry 440, a wireless interface 442, and a display 444.
  • a person skilled in the art would appreciate that other components not shown may be used in addition to the components shown to form a complete UE.
  • physical layer circuitry 432 includes a transceiver 433 for providing signals to and from eNB 410 (as well as other eNBs). Transceiver 433 provides signals to and from eNBs or other devices using one or more antennas 425.
  • MAC circuitry 434 controls access to the wireless medium.
  • Memory 438 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory -based storage media), or any tangible storage media or non-transitory storage media.
  • Wireless interface 442 may be arranged to allow the processor to communicate with another device.
  • Display 444 may provide a visual and/or tactile display for a user to interact with UE 430, such as a touch-screen display.
  • Hardware processing circuitry 440 may comprise logic devices or circuitry to perform various operations.
  • processor 436 and memory 438 may be arranged to perform the operations of hardware processing circuitry 440, such as operations described herein with reference to logic devices and circuitry within UE 430 and/or hardware processing circuitry 440.
  • UE 430 may be a device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display.
  • FIG. 5 and 6 also depict embodiments of eNBs, hardware processing circuitry of eNBs, UEs, and/or hardware processing circuitry of UEs, and the embodiments described with respect to Fig. 4 as well as Figs. 5 and 6 can operate or function in the manner described herein with respect to any of the figures.
  • eNB 410 and UE 430 are each described 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 and/or other hardware elements.
  • the functional elements can refer to one or more processes operating on one or more processing elements. Examples of software and/or hardware configured elements include Digital Signal Processors (DSPs), one or more microprocessors, DSPs, Field-Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Radio-Frequency Integrated Circuits (RFICs), and so on.
  • DSPs Digital Signal Processors
  • FPGAs Field-Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • RFICs Radio-Frequency Integrated Circuits
  • Fig. 5 illustrates hardware processing circuitries for a UE for MCO with multiple anchor carriers in NB-IoT systems, in accordance with some embodiments of the disclosure.
  • a UE may include various hardware processing circuitries discussed herein (such as hardware processing circuitry 500 of Fig. 5), which may in turn comprise logic devices and/or circuitry operable to perform various operations.
  • UE 430 (or various elements or components therein, such as hardware processing circuitry 440, or combinations of elements or components therein) may include part of, or all of, these hardware processing circuitries.
  • one or more devices or circuitries within these hardware processing circuitries may be implemented by combinations of software-configured elements and/or other hardware elements.
  • processor 436 and/or one or more other processors which UE 430 may comprise
  • memory 438 and/or other elements or components of UE 430 (which may include hardware processing circuitry 440) may be arranged to perform the operations of these hardware processing circuitries, such as operations described herein with reference to devices and circuitry within these hardware processing circuitries.
  • processor 436 (and/or one or more other processors which UE 430 may comprise) may be a baseband processor.
  • an apparatus of UE 430 (or another UE or mobile handset), which may be operable to communicate with one or more eNBs on a wireless network, may comprise hardware processing circuitry 500.
  • hardware processing circuitry 500 may comprise one or more antenna ports 505 operable to provide various transmissions over a wireless communication channel (such as wireless
  • Antenna ports 505 may be coupled to one or more antennas 507 (which may be antennas 425).
  • hardware processing circuitry 500 may incorporate antennas 507, while in other embodiments, hardware processing circuitry 500 may merely be coupled to antennas 507.
  • Antenna ports 505 and antennas 507 may be operable to provide signals from a UE to a wireless communications channel and/or an eNB, and may be operable to provide signals from an eNB and/or a wireless communications channel to a UE.
  • antenna ports 505 and antennas 507 may be operable to provide transmissions from UE 430 to wireless communication channel 450 (and from there to eNB 410, or to another eNB).
  • antennas 507 and antenna ports 505 may be operable to provide transmissions from a wireless communication channel 450 (and beyond that, from eNB 410, or another eNB) to UE 430.
  • An apparatus of a UE which may be operable to communicate with a first
  • NB-IoT carrier and a second NB-IoT carrier on a wireless network may comprise hardware processing circuitry 500.
  • Hardware processing circuitry 500 may comprise various circuitries operable in accordance with the various embodiments discussed herein. With reference to Fig. 5, hardware processing circuitry 500 may comprise a first circuitry 510 and/or a second circuitry 520.
  • First circuitry 510 may be operable to process an RRC message from the first NB-IoT carrier directing the UE to process an SI message from the second NB-IoT carrier.
  • Second circuitry 520 may be operable to determine one or more parameters of the second NB-IoT carrier based on the RRC message.
  • First circuitry 510 may be operable to provide information pertaining to the RRC message to second circuitry 520 via an interface 515.
  • the one or more parameters may include: a number of repetitions for the SI message from the second NB-IoT carrier, and/or an SRFN for the SI message from the second NB-IoT carrier.
  • the apparatus of the UE may comprise an interface to receive the RRC message (e.g., an interface with an RF circuitry to input the RRC message from the RF circuitry).
  • the UE may be an NB-IoT capable UE, and/or one or more of the first NB-IoT carrier and the second NB-IoT carrier may be NB-IoT capable eNBs.
  • the first NB-IoT carrier may be an anchor eNB, and/or the second NB-IoT carrier is a non-anchor eNB.
  • the SI message may be a SIB-1 message.
  • the determination of the one or more parameters of the second NB-IoT carrier may be based upon a four-bit indicator in a MIB transmission of the first NB-IoT carrier.
  • the number of repetitions for the SI message from the second NB-IoT carrier may be predetermined to be the same as a number of repetitions for the SI message for the first NB-IoT carrier, and/or the SRFN for the SI message from the second NB-IoT carrier may be predetermined to be the same as an SRFN for the SI message for the first NB-IoT carrier.
  • the RRC message may carry time-domain scheduling information for the SI message.
  • the time-domain scheduling information may include the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • the RRC message may carry a four-bit indicator indicating both a TBS and the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry a NB-IoT DL subframe configuration for the second NB-IoT carrier.
  • the RRC message may carry a first additional parameter indicating that the second NB-IoT carrier is operable as an anchor eNB, and/or a second additional parameter indicating that the second NB-IoT carrier is operable to provide at least one of: PSS, and SSS.
  • an additional parameter may indicate that the second NB-IoT carrier is operable to provide one or more of a PSS and a SSS is carried by one of: RRC signaling, or SIB signaling of the first NB-IoT carrier.
  • first circuitry 510 and/or second circuitry 520 may be implemented as separate circuitries. In other embodiments, first circuitry 510 and second circuitry 520 may be combined and implemented together in a circuitry without altering the essence of the embodiments.
  • Fig. 6 illustrates hardware processing circuitries for an eNB for MCO with multiple anchor carriers in NB-IoT systems, in accordance with some embodiments of the disclosure.
  • an eNB may include various hardware processing circuitries discussed herein (such as hardware processing circuitry 600 of Fig. 6), which may in turn comprise logic devices and/or circuitry operable to perform various operations.
  • eNB 410 (or various elements or components therein, such as hardware processing circuitry 420, or combinations of elements or components therein) may include part of, or all of, these hardware processing circuitries.
  • one or more devices or circuitries within these hardware processing circuitries may be implemented by combinations of software-configured elements and/or other hardware elements.
  • processor 416 and/or one or more other processors which eNB 410 may comprise
  • memory 418 and/or other elements or components of eNB 410 (which may include hardware processing circuitry 420) may be arranged to perform the operations of these hardware processing circuitries, such as operations described herein with reference to devices and circuitry within these hardware processing circuitries.
  • processor 416 (and/or one or more other processors which eNB 410 may comprise) may be a baseband processor.
  • an apparatus of eNB 410 (or another eNB or base station), which may be operable to communicate with one or more UEs on a wireless network, may comprise hardware processing circuitry 600.
  • hardware processing circuitry 600 may comprise one or more antenna ports 605 operable to provide various transmissions over a wireless communication channel (such as wireless communication channel 450).
  • Antenna ports 605 may be coupled to one or more antennas 607 (which may be antennas 405).
  • hardware processing circuitry 600 may incorporate antennas 607, while in other embodiments, hardware processing circuitry 600 may merely be coupled to antennas 607.
  • Antenna ports 605 and antennas 607 may be operable to provide signals from an eNB to a wireless communications channel and/or a UE, and may be operable to provide signals from a UE and/or a wireless communications channel to an eNB.
  • antenna ports 605 and antennas 607 may be operable to provide transmissions from eNB 410 to wireless communication channel 450 (and from there to UE 430, or to another UE).
  • antennas 607 and antenna ports 605 may be operable to provide transmissions from a wireless communication channel 450 (and beyond that, from UE 430, or another UE) to eNB 410.
  • An apparatus of a first NB-IoT carrier which may be operable to
  • Hardware processing circuitry 600 may comprise various circuitries operable in accordance with the various embodiments discussed herein.
  • hardware processing circuitry 600 may comprise a first circuitry 610 and/or a second circuitry 620.
  • First circuitry 610 may be operable to establish one or more parameters of a second NB-IoT carrier.
  • Second circuitry 620 may be operable to generate an RRC message carrying the one or more parameters and directing the UE to process an SI message from the second NB-IoT carrier.
  • First circuitry 610 may be operable to provide information pertaining to the one or more parameters to second circuitry 620 via an interface 615.
  • the one or more parameters may include: a number of repetitions for the SI message from the second NB-IoT carrier, and/or an SRFN for the SI message from the second NB-IoT carrier.
  • the apparatus of the first NB-IoT carrier may comprise an interface to transmit the RRC message (e.g., an interface with an RF circuitry to output the RRC message to the RF circuitry).
  • the UE may be an NB-IoT capable UE, and/or one or more of the first NB-IoT carrier and the second NB-IoT carrier may be NB-IoT capable eNBs.
  • the first NB-IoT carrier may be an anchor eNB, and/or the second NB-IoT carrier may be a non-anchor eNB.
  • the SI message may be a SIB-1 message.
  • second circuitry 620 may be operable to generate a MIB transmission carrying a four-bit indicator establishing the one or more parameters of the second NB-IoT carrier.
  • the number of repetitions for the SI message from the second NB-IoT carrier may be predetermined to be the same as a number of repetitions for the SI message for the first NB-IoT carrier, and/or the SRFN for the SI message from the second NB-IoT carrier may be predetermined to be the same as an SRFN for the SI message for the first NB-IoT carrier.
  • the RRC message may carry time-domain scheduling information for the SI message.
  • the time-domain scheduling information may include the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • the RRC message may carry a four-bit indicator indicating both a TBS and the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry a NB-IoT DL subframe configuration for the second NB-IoT carrier.
  • the RRC message may carry a first additional parameter indicating that the second NB-IoT carrier is operable as an anchor eNB, and/or a second additional parameter indicating that the second NB-IoT carrier is operable to provide at least one of: PSS, and SSS.
  • an additional parameter may indicate that the second NB IoT carrier is operable to provide one or more of a PSS and a SSS is carried by one of: RRC signaling, or SIB signaling of the first NB IoT carrier.
  • Fig. 7 illustrates methods for a UE for MCO with multiple anchor carriers in
  • NB-IoT systems in accordance with some embodiments of the disclosure.
  • methods that may relate to UE 430 and hardware processing circuitry 440 are discussed herein.
  • the actions in the method 700 of Fig. 7 are shown in a particular order, the order of the actions can be modified. Thus, the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel. Some of the actions and/or operations listed in Fig. 7 are optional in accordance with certain
  • machine readable storage media may have executable instructions that, when executed, cause UE 430 and/or hardware processing circuitry 440 to perform an operation comprising the methods of Fig. 7.
  • Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash- memory-based storage media), or any other tangible storage media or non-transitory storage media.
  • an apparatus may comprise means for performing various actions and/or operations of the methods of Fig. 7.
  • a method 700 (which may be for a UE operable to communicate with a first NB-IoT carrier and a second NB-IoT carrier on a wireless network) may comprise a processing 710 and a determining 715.
  • processing 710 an RRC message from the first NB-IoT carrier may be processed by the UE, the RRC message directing the UE to process an SI message from the second NB-IoT carrier.
  • determining 715 one or more parameters of the second NB-IoT carrier may be determined based on the RRC message. The one or more parameters may include: a number of repetitions for the SI message from the second NB-IoT carrier, and/or an SRFN for the SI message from the second NB-IoT carrier.
  • the UE may be an NB-IoT capable UE, and/or one or more of the first NB-IoT carrier and the second NB-IoT carrier may be NB-IoT capable eNBs.
  • the first NB-IoT carrier may be an anchor eNB, and/or the second NB-IoT carrier is a non-anchor eNB.
  • the SI message may be a SIB-1 message.
  • the determination of the one or more parameters of the second NB-IoT carrier may be based upon a four-bit indicator in a MIB transmission of the first NB-IoT carrier.
  • the number of repetitions for the SI message from the second NB-IoT carrier may be predetermined to be the same as a number of repetitions for the SI message for the first NB-IoT carrier, and/or the SRFN for the SI message from the second NB-IoT carrier may be predetermined to be the same as an SRFN for the SI message for the first NB-IoT carrier.
  • the RRC message may carry time-domain scheduling information for the SI message.
  • the time-domain scheduling information may include the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • the RRC message may carry a four-bit indicator indicating both a TBS and the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry a NB-IoT DL subframe configuration for the second NB-IoT carrier.
  • the RRC message may carry a first additional parameter indicating that the second NB-IoT carrier is operable as an anchor eNB, and/or a second additional parameter indicating that the second NB-IoT carrier is operable to provide at least one of: PSS, and SSS.
  • an additional parameter may indicate that the second NB-IoT carrier is operable to provide one or more of a PSS and a SSS is carried by one of: RRC signaling, or SIB signaling of the first NB-IoT carrier.
  • Fig. 8 illustrates methods for an eNB for MCO with multiple anchor carriers in NB-IoT systems, in accordance with some embodiments of the disclosure.
  • various methods that may relate to eNB 410 and hardware processing circuitry 420 are discussed herein.
  • the actions in method 800 of Fig. 8 are shown in a particular order, the order of the actions can be modified. Thus, the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel. Some of the actions and/or operations listed in Fig. 8 are optional in accordance with certain
  • machine readable storage media may have executable instructions that, when executed, cause eNB 410 and/or hardware processing circuitry 420 to perform an operation comprising the methods of Fig. 8.
  • Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash- memory-based storage media), or any other tangible storage media or non-transitory storage media.
  • an apparatus may comprise means for performing various actions and/or operations of the methods of Fig. 8.
  • a method 800 (which may be for an NB-IoT carrier operable to communicate with a UE on a wireless network) may comprise an establishing 810 and a generating 815.
  • establishing 810 one or more parameters of a second NB-IoT carrier may be established.
  • generating 815 an RRC message carrying the one or more parameters may be generated, the RRC message directing the UE to process an SI message from the second NB-IoT carrier.
  • the one or more parameters may include: a number of repetitions for the SI message from the second NB-IoT carrier, and/or an SRFN for the SI message from the second NB-IoT carrier.
  • the UE may be an NB-IoT capable UE, and/or one or more of the first NB-IoT carrier and the second NB-IoT carrier may be NB-IoT capable eNBs.
  • the first NB-IoT carrier may be an anchor eNB, and/or the second NB-IoT carrier is a non-anchor eNB.
  • the SI message may be a SIB-1 message.
  • a MIB transmission may be generated, the MIB transmission carrying a four-bit indicator establishing the one or more parameters of the second NB-IoT carrier.
  • the number of repetitions for the SI message from the second NB-IoT carrier may be predetermined to be the same as a number of repetitions for the SI message for the first NB-IoT carrier, and/or the SRFN for the SI message from the second NB-IoT carrier may be predetermined to be the same as an SRFN for the SI message for the first NB-IoT carrier.
  • the RRC message may carry time-domain scheduling information for the SI message.
  • the time-domain scheduling information may include the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry an indicator of a number of repetitions used for the SI message within a 256 radio-frame period. For some
  • the RRC message may carry a four-bit indicator indicating both a TBS and the number of repetitions for the SI message from the second NB-IoT carrier.
  • the RRC message may carry a NB-IoT DL subframe configuration for the second NB-IoT carrier.
  • the RRC message may carry a first additional parameter indicating that the second NB-IoT carrier is operable as an anchor eNB, and/or a second additional parameter indicating that the second NB-IoT carrier is operable to provide at least one of: PSS, and SSS.
  • an additional parameter may indicate that the second NB-IoT carrier is operable to provide one or more of a PSS and a SSS is carried by one of: RRC signaling, or SIB signaling of the first NB-IoT carrier.
  • first circuitry 610 and/or second circuitry 620 may be implemented as separate circuitries. In other embodiments, first circuitry 610 and/or second circuitry 620 may be combined and implemented together in a circuitry without altering the essence of the embodiments.
  • Fig. 9 illustrates example components of a UE device 900, in accordance with some embodiments of the disclosure.
  • a UE device 900 may include application circuitry 902, baseband circuitry 904, Radio Frequency (RF) circuitry 906, front- end module (FEM) circuitry 908, a low-power wake-up receiver (LP-WUR), and one or more antennas 910, coupled together at least as shown.
  • the UE device 900 may include additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface.
  • I/O input/output
  • the application circuitry 902 may include one or more application processors.
  • the application circuitry 902 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 and/or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 904 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 904 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 906 and to generate baseband signals for a transmit signal path of the RF circuitry 906.
  • Baseband processing circuity 904 may interface with the application circuitry 902 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 906.
  • the baseband circuitry 904 may include a second generation (2G) baseband processor 904A, third generation (3G) baseband processor 904B, fourth generation (4G) baseband processor 904C, and/or other baseband processor(s) 904D for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 904 e.g., one or more of baseband processors 904A-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 904 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 904 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 904 may include elements of a protocol stack such as, for example, elements of an EUTRAN protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or RRC elements.
  • a central processing unit (CPU) 904E of the baseband circuitry 904 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 904F.
  • DSP audio digital signal processor
  • the audio DSP(s) 904F 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 904 and the application circuitry 902 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 904 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 904 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/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 904 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 906 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 906 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 906 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 908 and provide baseband signals to the baseband circuitry 904.
  • RF circuitry 906 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 904 and provide RF output signals to the FEM circuitry 908 for transmission.
  • the RF circuitry 906 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 906 may include mixer circuitry 906A, amplifier circuitry 906B and filter circuitry 906C.
  • the transmit signal path of the RF circuitry 906 may include filter circuitry 906C and mixer circuitry 906A.
  • RF circuitry 906 may also include synthesizer circuitry 906D for synthesizing a frequency for use by the mixer circuitry 906A of the receive signal path and the transmit signal path.
  • the mixer circuitry 906A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906D.
  • the amplifier circuitry 906B may be configured to amplify the down-converted signals and the filter circuitry 906C may be a low- pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 904 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 906A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 906A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 906D to generate RF output signals for the FEM circuitry 908.
  • the baseband signals may be provided by the baseband circuitry 904 and may be filtered by filter circuitry 906C.
  • the filter circuitry 906C may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively.
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively.
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 904 may include a digital baseband interface to communicate with the RF circuitry 906.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 906D may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 906D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 906D may be configured to synthesize an output frequency for use by the mixer circuitry 906A of the RF circuitry 906 based on a frequency input and a divider control input.
  • the synthesizer circuitry 906D may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 904 or the applications processor 902 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 902.
  • Synthesizer circuitry 906D of the RF circuitry 906 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (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 906D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 906 may include an IQ/polar converter.
  • FEM circuitry 908 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 910, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 906 for further processing.
  • FEM circuitry 908 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 906 for transmission by one or more of the one or more antennas 910.
  • the FEM circuitry 908 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 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 906).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 908 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 906), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 910.
  • PA power amplifier
  • the UE 900 comprises a plurality of power saving mechanisms. If the UE 900 is in an RRC Connected state, where it is still connected to the eNB as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the UE 900 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the UE 900 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. Since the device might not receive data in this state, in order to receive data, it should 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.
  • the baseband circuitry 904 of Fig. 9 may comprise processors 904A-904E and a memory utilized by said processors.
  • Each of the processors 904A-904E may include a memory interface to send/receive data to/from the memory 904G.
  • the baseband circuitry 904 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 904), an application circuitry interface (e.g., an interface to send/receive data to/from the application circuitry 902 of Fig. 9), an RF circuitry interface (e.g., an interface to send/receive data to/from RF circuitry 906 of Fig.
  • a memory interface e.g., an interface to send/receive data to/from memory external to the baseband circuitry 904
  • an application circuitry interface e.g., an interface to send/receive data to/from the application circuitry 902 of Fig. 9
  • an RF circuitry interface e.g., an interface to send/receive data to/from RF circuitry 906 of Fig.
  • a wireless hardware connectivity interface e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface e.g., an interface to send/receive power or control signals to/from the PMC 912).
  • an eNB device may include components substantially similar to one or more of the example components of UE device 900 described herein.
  • elements of any of the Figures herein having the same reference numbers and/or names as elements of any other Figure herein may, in various embodiments, operate or function in a manner similar those elements of the other Figure (without being limited to operating or functioning in such a manner).
  • DRAM Dynamic RAM
  • example 1 provides an apparatus of a User Equipment (UE) operable to communicate with a first Narrow-Band Internet-of-Things (NB IoT) carrier and a second NB IoT carrier on a wireless network, comprising: one or more processors to: process a Radio Resource Control (RRC) message from the first NB IoT carrier directing the UE to process a System Information (SI) message from the second NB IoT carrier; and determine one or more parameters of the second NB IoT carrier based on the RRC message, and an interface to receive the RRC message, wherein the one or more parameters include at least one of: a number of repetitions for the SI message from the second NB IoT carrier, and a starting radio frame number (SRFN) for the SI message from the second NB IoT carrier.
  • RRC Radio Resource Control
  • SI System Information
  • example 2 the apparatus of example 1 , wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • example 3 the apparatus of either of examples 1 or 2, wherein the first NB
  • IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • example 4 the apparatus of any of examples 1 through 3, wherein the SI message is a System Information Block 1 (SIB-1) message.
  • SIB-1 System Information Block 1
  • example 5 the apparatus of any of examples 1 through 4, wherein the determination of the one or more parameters of the second NB IoT carrier is based upon a four-bit indicator in a Master Information Block (MIB) transmission of the first NB IoT carrier.
  • MIB Master Information Block
  • example 6 the apparatus of any of examples 1 through 5, wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • example 7 the apparatus of any of examples 1 through 5, wherein the RRC message carries time-domain scheduling information for the SI message.
  • the time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • example 9 the apparatus of any of examples 1 through 8, wherein the RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • RRC message carries a four-bit indicator indicating both a Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • DL Downlink
  • RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 13 the apparatus of any of examples 1 through 12, wherein an additional parameter indicating that the second NB IoT carrier is operable to provide one or more of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) is carried by one of: RRC signaling, or System Information Block (SIB) signaling of the first NB IoT carrier.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • RRC signaling Radio Resource Control
  • SIB System Information Block
  • example 14 the apparatus of any of examples 56 through 13, comprising a transceiver circuitry for at least one of: generating transmissions, encoding transmissions, processing transmissions, or decoding transmissions.
  • example 15 provides a User Equipment (UE) device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display, the UE device including the apparatus of any of examples 1 through 14.
  • UE User Equipment
  • example 16 provides a method comprising: processing, for a User
  • UE Radio Resource Control
  • RRC Radio Resource Control
  • SI System Information
  • SI System Information
  • SRFN starting radio frame number
  • example 17 the method of example 16, wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • NB IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • SIB-1 System Information Block 1
  • example 20 the method of any of examples 16 through 19, wherein the determination of the one or more parameters of the second NB IoT carrier is based upon a four-bit indicator in a Master Information Block (MIB) transmission of the first NB IoT carrier.
  • MIB Master Information Block
  • example 21 the method of any of examples 16 through 20, wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • RRC message carries time-domain scheduling information for the SI message.
  • time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • RRC message carries a four-bit indicator indicating both a Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • DL Downlink
  • RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 28 the method of any of examples 16 through 27, wherein an additional parameter indicating that the second NB IoT carrier is operable to provide one or more of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) is carried by one of: RRC signaling, or System Information Block (SIB) signaling of the first NB IoT carrier.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • RRC signaling Radio Resource Control
  • SIB System Information Block
  • example 29 provides machine readable storage media having machine executable instructions stored thereon that, when executed, cause one or more processors to perform a method according to machine readable storage media of any of examples 16 through 28.
  • example 30 provides an apparatus of a User Equipment (UE) operable to communicate with a first Narrow-Band Internet-of-Things (NB IoT) carrier and a second NB IoT carrier on a wireless network, comprising: means for processing a Radio Resource Control (RRC) message from the first NB IoT carrier directing the UE to process a System Information (SI) message from the second NB IoT carrier; and means for determining one or more parameters of the second NB IoT carrier based on the RRC message, wherein the one or more parameters include at least one of: a number of repetitions for the SI message from the second NB IoT carrier, and a starting radio frame number (SRFN) for the SI message from the second NB IoT carrier.
  • RRC Radio Resource Control
  • SI System Information
  • example 31 the apparatus of example 30, wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • NB IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • SIB-1 System Information Block 1
  • example 34 the apparatus of any of examples 30 through 33, wherein the determination of the one or more parameters of the second NB IoT carrier is based upon a four-bit indicator in a Master Information Block (MIB) transmission of the first NB IoT carrier.
  • MIB Master Information Block
  • example 35 the apparatus of any of examples 30 through 34, wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • RRC message carries time-domain scheduling information for the SI message.
  • time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • RRC message carries a four-bit indicator indicating both a Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • example 40 the apparatus of any of examples 30 through 39, wherein the
  • RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • DL Downlink
  • RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 42 the apparatus of any of examples 30 through 41, wherein an additional parameter indicating that the second NB IoT carrier is operable to provide one or more of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) is carried by one of: RRC signaling, or System Information Block (SIB) signaling of the first NB IoT carrier.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • SIB System Information Block
  • example 43 provides machine readable storage media having machine executable instructions that, when executed, cause one or more processors of a User
  • UE operable to communicate with a first Narrow-Band Internet-of-Things (NB IoT) carrier and a second NB IoT carrier on a wireless network to perform an operation comprising: process a Radio Resource Control (RRC) message from the first NB IoT carrier directing the UE to process a System Information (SI) message from the second NB IoT carrier; and determine one or more parameters of the second NB IoT carrier based on the RRC message, wherein the one or more parameters include at least one of: a number of repetitions for the SI message from the second NB IoT carrier, and a starting radio frame number (SRFN) for the SI message from the second NB IoT carrier.
  • RRC Radio Resource Control
  • SI System Information
  • example 44 the machine readable storage media of example 43, wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • the first NB IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • example 46 the machine readable storage media of any of examples 43 through 45, wherein the SI message is a System Information Block 1 (SIB-1) message.
  • SIB-1 System Information Block 1
  • example 47 the machine readable storage media of any of examples 43 through 46, wherein the determination of the one or more parameters of the second NB IoT carrier is based upon a four-bit indicator in a Master Information Block (MIB) transmission of the first NB IoT carrier.
  • MIB Master Information Block
  • example 48 the machine readable storage media of any of examples 43 through 47, wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • example 49 the machine readable storage media of any of examples 43 through 47, wherein the RRC message carries time-domain scheduling information for the SI message.
  • example 50 the machine readable storage media of example 49, wherein the time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • the machine readable storage media of any of examples 43 through 50 wherein the RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • the machine readable storage media of any of examples 43 through 51 wherein the RRC message carries a four-bit indicator indicating both a Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • example 53 the machine readable storage media of any of examples 43 through 52, wherein the RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • the RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • example 54 the machine readable storage media of any of examples 43 through 53, wherein the RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 55 the machine readable storage media of any of examples 43 through 54, wherein an additional parameter indicating that the second NB IoT carrier is operable to provide one or more of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) is carried by one of: RRC signaling, or System Information Block (SIB) signaling of the first NB IoT carrier.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • SIB System Information Block
  • example 56 provides an apparatus of a first Narrow-Band Internet-of-
  • NB IoT Network-to-Network Interface
  • UE User Equipment
  • RRC Radio Resource Control
  • SI System Information
  • SRFN starting radio frame number
  • example 57 the apparatus of example 56, wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • example 58 the apparatus of either of examples 56 or 57, wherein the first
  • NB IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • SIB-1 System Information Block 1
  • example 60 the apparatus of any of examples 56 through 59, wherein the one or more processors are to: generate a Master Information Block (MIB) transmission carrying a four-bit indicator establishing the one or more parameters of the second NB IoT carrier.
  • MIB Master Information Block
  • example 61 the apparatus of any of examples 56 through 60, wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • example 62 the apparatus of any of examples 56 through 60, wherein the
  • RRC message carries time-domain scheduling information for the SI message.
  • example 63 the apparatus of example 62, wherein the time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • example 64 the apparatus of any of examples 56 through 63, wherein the
  • RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • example 65 the apparatus of any of examples 56 through 64, wherein the
  • RRC message carries a four-bit indicator indicating both a Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • example 66 the apparatus of any of examples 56 through 65, wherein the
  • RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • DL Downlink
  • RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 68 the apparatus of any of examples 56 through 67, comprising a transceiver circuitry for at least one of: generating transmissions, encoding transmissions, processing transmissions, or decoding transmissions.
  • eNB Evolved Node B
  • An Evolved Node B (eNB) device comprising an application processor, a memory, one or more antenna ports, and an interface for allowing the application processor to communicate with another device, the eNB device including the apparatus of any of examples 56 through 68.
  • example 70 provides a method comprising: establishing, for a Narrow-Band
  • NB-IoT Intemet-of-Things
  • NB-IoT Intemet-of-Things
  • RRC Radio Resource Control
  • SI System Information
  • SRFN starting radio frame number
  • example 71 the method of example 70, wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • example 72 the method of either of examples 70 or 71, wherein the first
  • NB IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • SIB-1 System Information Block 1
  • example 74 the method of any of examples 70 through 73, the operation comprising: generate a Master Information Block (MIB) transmission carrying a four-bit indicator establishing the one or more parameters of the second NB IoT carrier.
  • MIB Master Information Block
  • example 75 the method of any of examples 70 through 74, wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • example 76 the method of any of examples 70 through 74, wherein the
  • RRC message carries time-domain scheduling information for the SI message.
  • example 77 the method of example 76, wherein the time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • example 78 the method of any of examples 70 through 77, wherein the
  • RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • RRC message carries a four-bit indicator indicating both a Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • example 80 the method of any of examples 70 through 79, wherein the
  • RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • DL Downlink
  • RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 82 provides machine readable storage media having machine executable instructions stored thereon that, when executed, cause one or more processors to perform a method according to 70 through 81.
  • example 83 provides an apparatus of a first Narrow-Band Internet-of-
  • NB IoT Network-to-Network Interface
  • UE User Equipment
  • RRC Radio Resource Control
  • SI System Information
  • SRFN starting radio frame number
  • example 84 the apparatus of example 83, wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • example 85 the apparatus of either of examples 83 or 84, wherein the first
  • NB IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • SIB-1 System Information Block 1
  • SIB-1 System Information Block 1
  • MIB Master Information Block
  • example 88 the apparatus of any of examples 83 through 87, wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • RRC message carries time-domain scheduling information for the SI message.
  • time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • example 92 the apparatus of any of examples 83 through 91, wherein the
  • RRC message carries a four-bit indicator indicating both a Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • example 93 the apparatus of any of examples 83 through 92, wherein the
  • RRC message carries a NB IoT Downlink (DL) subframe configuration for the second NB IoT carrier.
  • DL Downlink
  • example 94 the apparatus of any of examples 83 through 93, wherein the
  • RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 95 provides machine readable storage media having machine executable instructions that, when executed, cause one or more processors of a Narrow-Band Intemet-of-Things (NB IoT) carrier operable to communicate with a User Equipment (UE) on a wireless network to perform an operation comprising: establish one or more parameters of a second NB IoT carrier; and generate a Radio Resource Control (RRC) message carrying the one or more parameters and directing the UE to process a System Information (SI) message from the second NB IoT carrier, wherein the one or more parameters include at least one of: a number of repetitions for the SI message from the second NB IoT carrier, and a starting radio frame number (SRFN) for the SI message from the second NB IoT carrier.
  • NB IoT Narrow-Band Intemet-of-Things
  • example 96 the machine readable storage media of example 95, wherein the UE is an NB IoT capable UE, and one or more of the first NB IoT carrier and the second NB IoT carrier are NB IoT capable eNBs.
  • example 97 the machine readable storage media of either of examples 95 or
  • the first NB IoT carrier is an anchor eNB; and wherein the second NB IoT carrier is a non-anchor eNB.
  • example 98 the machine readable storage media of any of examples 95 through 97, wherein the SI message is a System Information Block 1 (SIB-1) message.
  • SIB-1 System Information Block 1
  • the machine readable storage media of any of examples 95 through 98 comprising: generate a Master Information Block (MIB) transmission carrying a four-bit indicator establishing the one or more parameters of the second NB IoT carrier.
  • MIB Master Information Block
  • the machine readable storage media of any of examples 95 through 99 wherein the number of repetitions for the SI message from the second NB IoT carrier is predetermined to be the same as a number of repetitions for the SI message for the first NB IoT carrier; and wherein the SRFN for the SI message from the second NB IoT carrier is predetermined to be the same as an SRFN for the SI message for the first NB IoT carrier.
  • example 101 the machine readable storage media of any of examples 95 through 99, wherein the RRC message carries time-domain scheduling information for the SI message.
  • example 102 the machine readable storage media of example 101 , wherein the time-domain scheduling information includes the number of repetitions for the SI message from the second NB IoT carrier.
  • example 103 the machine readable storage media of any of examples 95 through 102, wherein the RRC message carries an indicator of a number of repetitions used for the SI message within a 256 radio-frame period.
  • example 104 the machine readable storage media of any of examples 95 through 103, wherein the RRC message carries a four-bit indicator indicating both a
  • Transport Block Size (TBS) and the number of repetitions for the SI message from the second NB IoT carrier.
  • TBS Transport Block Size
  • DL NB IoT Downlink
  • the machine readable storage media of any of examples 95 through 105 wherein the RRC message carries a first additional parameter indicating that the second NB IoT carrier is operable as an anchor eNB; and wherein the RRC message carries a second additional parameter indicating that the second NB IoT carrier is operable to provide at least one of: Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • example 107 the apparatus of any of 1 through 13, and examples 56 through 67, wherein the one or more processors comprise a baseband processor.
  • example 108 the apparatus of any of 1 through 13, and examples 56 through 67, comprising a memory for storing instructions, the memory being coupled to the one or more processors.
  • example 109 the apparatus of any of 1 through 13, and examples 56 through 67, comprising a transceiver circuitry for generating transmissions and processing transmissions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP17723590.0A 2016-05-02 2017-05-02 Verfahren für mehrträgerbetrieb mit mehreren verankerungsträgern im schmalbandigen internet der dinge Withdrawn EP3453207A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662330660P 2016-05-02 2016-05-02
PCT/US2017/030692 WO2017192624A1 (en) 2016-05-02 2017-05-02 Methods for multi-carrier operation with multiple anchor carriers in narrow-band internet-of-things

Publications (1)

Publication Number Publication Date
EP3453207A1 true EP3453207A1 (de) 2019-03-13

Family

ID=58708042

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17723590.0A Withdrawn EP3453207A1 (de) 2016-05-02 2017-05-02 Verfahren für mehrträgerbetrieb mit mehreren verankerungsträgern im schmalbandigen internet der dinge

Country Status (2)

Country Link
EP (1) EP3453207A1 (de)
WO (1) WO2017192624A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11425724B2 (en) * 2019-07-12 2022-08-23 Qualcomm Incorporated Carrier aggregation for narrowband internet of things user equipment

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108111570A (zh) * 2017-11-10 2018-06-01 四川高科技有限责任公司 基于电信NB-IoT技术数据无线传输系统
JP6818139B2 (ja) 2017-11-15 2021-01-20 エルジー エレクトロニクス インコーポレイティド Ｔｄｄ狭帯域を支援する無線通信システムにおけるシステム情報を送受信するための方法及びこのための装置
EP3522433B1 (de) * 2017-11-15 2021-09-15 LG Electronics Inc. Verfahren zum senden und empfangen von systeminformationen in einem drahtloskommunikationssystem, das tdd-schmalband unterstützt, und vorrichtung dafür
WO2019095203A1 (zh) * 2017-11-16 2019-05-23 华为技术有限公司 一种系统消息传输的方法及网络设备
JP7016413B2 (ja) 2017-11-17 2022-02-04 華為技術有限公司 システムメッセージ伝送方法、装置及びシステム
CN117769025A (zh) 2018-02-12 2024-03-26 华为技术有限公司 一种通信方法、通信设备及计算机程序存储介质
CN112042253B (zh) * 2018-04-04 2022-10-11 华为技术有限公司 通信方法、装置及计算机可读存储介质
CN110574419B (zh) * 2018-07-23 2023-12-08 深圳市汇顶科技股份有限公司 跨无线频段的灵活的NB-IoT多载波操作
CN109709268B (zh) * 2018-12-20 2021-06-25 深汕特别合作区智慧城市研究院有限公司 一种以智慧杆为5g微基站载体的智慧管网数据传输系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11425724B2 (en) * 2019-07-12 2022-08-23 Qualcomm Incorporated Carrier aggregation for narrowband internet of things user equipment

Also Published As

Publication number Publication date
WO2017192624A1 (en) 2017-11-09

Similar Documents

Publication Publication Date Title
US20190372719A1 (en) Design of downlink control information for wideband coverage enhancement
US10849170B2 (en) Signaling methods for flexible radio resource management
US11576142B2 (en) System and method for multiplexing of tracking reference signal and synchronization signal block
US11533675B2 (en) System and methods for system operation for narrowband-LTE for cellular IoT
EP3453207A1 (de) Verfahren für mehrträgerbetrieb mit mehreren verankerungsträgern im schmalbandigen internet der dinge
CN108293191B (zh) 未授权频谱中的主信息块和系统信息块传输
US11368981B2 (en) Low latency physical random access channel design
US11722352B2 (en) Configurability and signaling for half-tone shift
WO2018085709A1 (en) Beam reciprocity indication and joint uplink downlink beam management
US10932185B2 (en) Transmitter and receiver for master information block over physical broadcast channel
WO2017080229A1 (en) Intra-frequency and inter-frequency measurement for narrow band machine-type communication
WO2017062061A1 (en) Signaling methods for flexible radio resource management
EP3596871B1 (de) Phasenverfolgungsreferenzsignalanzeige bei mehrbenutzerüberpositionsübertragung
WO2017197296A1 (en) Selection of priority class for uplink listen-before-talk channel access procedure
WO2017131810A1 (en) System and method for system information transmission in stand-alone mmwave systems
CN109076603B (zh) 用于上行链路传输的对话前监听
US11224023B2 (en) Timing advance for grantless uplink transmission
WO2018022782A1 (en) Control signaling for user equipment transmission beamforming
US20190387580A1 (en) Common search space design in enhanced physical downlink control channel
WO2018094175A1 (en) Orthogonal resource slicing for autonomous transmission
WO2018053364A1 (en) Downlink physical broadcast channel design for beamforming systems
WO2017099857A1 (en) Methods for latency reduction between uplink grant and physical uplink shared channel transmission

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20181002

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIN1 Information on inventor provided before grant (corrected)

Inventor name: BENDLIN, RALF

Inventor name: LIM, SEAU S.

Inventor name: MARTINEZ TARRADELL, MARTA

Inventor name: CHATTERJEE, DEBDEEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: APPLE INC.

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210615

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20211026