WO2018212765A1 - Noeud b évolué de l'internet des objets à bande étroite de recouvrement - Google Patents

Noeud b évolué de l'internet des objets à bande étroite de recouvrement Download PDF

Info

Publication number
WO2018212765A1
WO2018212765A1 PCT/US2017/032925 US2017032925W WO2018212765A1 WO 2018212765 A1 WO2018212765 A1 WO 2018212765A1 US 2017032925 W US2017032925 W US 2017032925W WO 2018212765 A1 WO2018212765 A1 WO 2018212765A1
Authority
WO
WIPO (PCT)
Prior art keywords
narrow
things
data
band internet
iot
Prior art date
Application number
PCT/US2017/032925
Other languages
English (en)
Inventor
Anand Bedekar
Rajeev Agrawal
Original Assignee
Nokia Solutions And Networks Oy
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 Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/US2017/032925 priority Critical patent/WO2018212765A1/fr
Publication of WO2018212765A1 publication Critical patent/WO2018212765A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037—Inter-user or inter-terminal allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0092—Indication of how the channel is divided
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/002—Transmission of channel access control information
    • H04W74/008—Transmission of channel access control information with additional processing of random access related information at receiving side

Definitions

  • NB narrow-band
  • IOT internet-of-things
  • NB-IOT has been introduced in release 13 (Rel 13) of long term evolution (LTE) as a new set of capabilities for LTE to support large numbers of IOT devices with high coverage and low battery consumption.
  • LTE-M Long Term Evolution
  • eMTC enhanced Machine Type Communication
  • mMTC massive Machine Type Communication
  • the terms "narrow-band internet of things or NB-IOT” can refer to any of NB-IOT, LTE-M, LTE-Cat-Ml, or eMTC or mMTC.
  • An NB-IOT carrier conventionally occupies the equivalent of one LTE physical resource block (PRB).
  • an NB-IOT can be operated either in-band with LTE, or in an LTE guard-band, or in a standalone band, for example a re-farmed global system for mobile communication (GSM) carrier.
  • GSM global system for mobile communication
  • an LTE-M or LTE-Cat Ml carrier conventionally occupies the equivalent of 6 LTE PRBs, with the possibility of using additional groups of 6 LTE PRBs as needed.
  • a method can include receiving downlink data corresponding to a narrow-band internet-of-things carrier.
  • the method can also include conditionally multiplexing the downlink data to at least one physical resource block together with other data.
  • the other data can include data unrelated to narrow-band internet-of-things.
  • the method can further include transmitting the multiplexed data.
  • a method can include preparing downlink data to be transmitted on a narrow-band internet-of-things carrier. The method can also include providing with the downlink data an indicator indicating at least one of a time or frequency resource where the downlink data is to be transmitted multiplexed with other data.
  • An apparatus can include means for receiving downlink data corresponding to a narrow-band internet-of-things carrier.
  • the apparatus can also include means for conditionally multiplexing the downlink data to at least one physical resource block together with other data.
  • the other data can include data unrelated to narrow-band internet-of- things.
  • the apparatus can further include means for transmitting the multiplexed data.
  • An apparatus in certain embodiments, can include means for preparing downlink data to be transmitted on a narrow-band internet-of-things carrier.
  • the apparatus can also include means for providing with the downlink data an indicator indicating at least one of a time or frequency resource where the downlink data is to be transmitted multiplexed with other data.
  • an apparatus can include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to receive downlink data corresponding to a narrow-band internet-of-things carrier.
  • the at least one memory and the computer program code can also be configured to, with the at least one processor, cause the apparatus at least to conditionally multiplex the downlink data to at least one physical resource block together with other data.
  • the other data can include data unrelated to narrow-band internet-of-things.
  • the at least one memory and the computer program code can also be configured to, with the at least one processor, cause the apparatus at least to transmit the multiplexed data.
  • an apparatus can include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to prepare downlink data to be transmitted on a narrow-band internet-of-things carrier.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to provide with the downlink data an indicator indicating at least one of a time or frequency resource where the downlink data is to be transmitted multiplexed with other data.
  • a computer program product can, according to certain embodiments, encode instructions for performing a process.
  • the process can include receiving downlink data corresponding to a narrow-band internet-of-things carrier.
  • the process can also include conditionally multiplexing the downlink data to at least one physical resource block together with other data.
  • the other data can include data unrelated to narrow-band internet-of-things.
  • the process can further include transmitting the multiplexed data.
  • a computer program product can, according to certain embodiments, encode instructions for performing a process.
  • the process can include preparing downlink data to be transmitted on a narrow-band internet-of-things carrier.
  • the process can also include providing with the downlink data an indicator indicating at least one of a time or frequency resource where the downlink data is to be transmitted multiplexed with other data.
  • a non-transitory computer readable medium can, according to certain embodiments, be encoded with instructions that, when executed in hardware, perform a process.
  • the process can include receiving downlink data corresponding to a narrow-band internet-of-things carrier.
  • the process can also include conditionally multiplexing the downlink data to at least one physical resource block together with other data.
  • the other data can include data unrelated to narrow-band internet-of-things.
  • the process can further include transmitting the multiplexed data.
  • a non-transitory computer readable medium can, in certain embodiments, be encoded with instructions that, when executed in hardware, perform a process.
  • the process can include preparing downlink data to be transmitted on a narrow-band internet-of-things carrier.
  • the process can also include providing with the downlink data an indicator indicating at least one of a time or frequency resource where the downlink data is to be transmitted multiplexed with other data.
  • Figure 1 illustrates data path for overlay, according to certain embodiments.
  • Figure 2 illustrates resource element allocation for overlay, according to certain embodiments.
  • Figure 3 illustrates overlay with a distributed radio access network LTE eNB, according to certain embodiments.
  • Figure 4 illustrates a protocol stack according to certain embodiments.
  • Figure 5 illustrates overlay with a cloud RAN LTE eNB, according to certain embodiments.
  • Figure 6 illustrates latency in connection with certain embodiments.
  • Figure 7 illustrates latency estimation according to certain embodiments.
  • Figure 8 illustrates a multiplexing method, according to certain embodiments.
  • Figure 9 illustrates a mechanism for supporting longer latency, according to certain embodiments.
  • Figure 10 illustrates support of standalone-band or guard-band deployment, according to certain embodiments.
  • Figure 1 1 illustrates a method according to certain embodiments.
  • Figure 12 illustrates another method according to certain embodiments.
  • FIG. 13 illustrates a system according to certain embodiments.
  • Certain embodiments provide for the introduction of NB-IOT capabilities in the RAN as an overlay solution.
  • certain embodiments can leverage the radio frequency (RF) functions of existing or conventional LTE eNBs.
  • certain embodiments may make improvements to the existing or conventional LTE eNB baseband to, for example, support functional changes and a lightweight interface.
  • RF radio frequency
  • an entity may be introduced into the network as an overlay that interfaces to an existing or conventional LTE eNB, and that provides the eNB or baseband functionality needed for narrow-band internet of things operation.
  • Such an entity can be referred to variously as a narrow-band internet of things access point, or an NB-IOT eNB, or an NB- IOT BBU, or an NB-IOT overlay, all substantially having the same meaning.
  • Such an NB-IOT access point overlay can be introduced as either (i) fully virtualized implementation which provides the entire NB-IOT functionality (including L3/L2/L1), or (ii) fully bare-metal, or (iii) partly virtualized, for example only L3/L2-NRT virtualized and L2-RT/L1 on bare metal.
  • This overlay NB-IOT implementation whether virtualized or bare-metal, can be placed at an edge cloud location. In certain embodiments, there may not be any need for the introduction of a new physical boxes at the existing cell site.
  • the transport between the edge cloud hosting the narrow-band internet of things access point and the cell site can have relaxed latency characteristics, up to ⁇ 4.5ms one-way in certain embodiments.
  • the transport may need low incremental bandwidth added to existing IP backhaul.
  • Certain embodiments provide functionality that can be used over an interface between the overlay NB-IOT eNB and conventional LTE eNB. While this is described for LTE NB-IOT, the same concept can also be applied for the support of massive machine type communication (MTC) in fifth generation (5G) communication systems as well as LTE-M/LTE Cat-Mi .
  • MTC massive machine type communication
  • FIG. 1 illustrates data path for overlay, according to certain embodiments.
  • two different kinds of user equipment such as a sensor and a smart phone
  • eNB evolved Node B
  • a conventional LTE eNB base band unit (BBU) can perform baseband processing for conventional LTE user equipment (UEs), such as a smart phone.
  • IP Internet protocol
  • IP Internet protocol
  • the NB-IOT eNB BBU can perform baseband processing for NB-IOT signals.
  • the NB-IOT eNB BBU may interface to an element management system (EMS).
  • EMS element management system
  • the evolved packet core may process conventional LTE as well as narrow-band internet of things.
  • the same EPC entities may be used to serve both conventional LTE as well as narrow-band internet of things, or different EPC entities may be used for conventional LTE and for narrow-band internet of things.
  • the data corresponding to a narrow-band internet of things transmission is multiplexed with data unrelated to the narrow-band internet of things transmission, such as data for conventional LTE. In an embodiment, this may be accomplished by multiplexing a representation of the signal for narrow-band internet of things with a representation of the signal for conventional LTE.
  • the representation of the signal may be a representation of a physical-layer signal, for instance, I/Q sample data, or a compressed version of LQ sample data, or pre-FFT or post-FFT data, or any other suitable form.
  • Figure 2 illustrates resource element allocation for overlay, according to certain embodiments.
  • the air interface structure allows a set of physical resource blocks (PRBs) to be used for transmissions related to narrow-band internet of things, and may be referred to generally as narrow-band internet of things carriers (NB-IOT carriers).
  • PRBs physical resource blocks
  • NB-IOT carriers narrow-band internet of things carriers
  • specific resource elements (REs) are typically used for transmissions related to narrow-band internet of things, while other resource elements are used for conventional LTE transmissions, and in some cases, some resource elements may be common between NB-IOT transmissions as well as conventional LTE transmissions.
  • the exact set of PRBs or resource elements that can be used in this way for narrow-band internet of things and/or conventional LTE may differ depending on the details of the air interface.
  • the set of PRBs or REs used by the NB-IOT standard in 3 GPP Release 13 may differ from the resource elements used for LTE-M or LTE-Category-Ml .
  • Figure 2 illustrates an embodiment, wherein an NB-IOT carrier consisting of 1 PRB is shown.
  • PRBs physical resource blocks
  • REs resource elements
  • a PRB corresponding to an NB-IOT carrier there can be a conventional LTE physical downlink control channel (PHDCCH) region and an overlay region.
  • PHDCCH physical downlink control channel
  • the conventional LTE PDCCH region the first three symbols in the transmission time interval (TTI), resource elements can be allocated by a conventional LTE eNB.
  • the rest of the resource elements (REs), apart from LTE cell specific reference signal (CRS) REs, may be allocated by the overlay NB-IOT eNB which provides the data corresponding to the narrow-band internet of things transmission in those resource elements to the LTE eNB, which in turn multiplexes that data together with data corresponding to conventional LTE transmissions into the appropriate REs to form the full signal to be transmitted over the air.
  • REs resource elements
  • CRS LTE cell specific reference signal
  • the interface between the NB-IOT and the conventional LTE eNB can support negotiation of various elements. For example, there can be a parameter indicating the starting symbol for NB-IOT.
  • the starting symbol can be notified to the NB-IOT eNB by the LTE cell. This may dynamically change, but as this may also need to be broadcast in system information block (SIB) messages by the NB-IOT eNB, this may only be changed slowly by the LTE eNB.
  • SIB system information block
  • the cell ID of the NB-IOT cell and the embedding LTE cell can be provided. Similarly, the number of antenna ports of the LTE and NB-IOT cells can be provided.
  • LTE PRBs There can be a set of LTE PRBs that are used as NB-IOT carriers. This can be potentially static or this may be dynamically adjusted. For example, the PRBs can be dynamically adjusted in the following way.
  • a first set of LTE PRBs can be chosen and assigned to the NB-IOT cell. This may include anchor carrier and some non-anchor carriers for NB-IOT. As the load of NB-IOT varies, the NB-IOT may request additional PRBs to use for anchor carriers as well as non-anchor carriers.
  • FIG. 3 illustrates overlay with a distributed radio access network LTE eNB, according to certain embodiments. More specifically, Figure 3 show an instantiation with distributed-RAN LTE eNB.
  • a distributed RAN LTE eNB baseband unit (BBU).
  • BBU distributed RAN LTE eNB baseband unit
  • This eNB may be a bare-metal, all-in-one eNB for distributed RAN.
  • This eNB may be connected by an IP transport to an EMS for conventional LTE eNB and to a conventional EPC.
  • the eNB may be connected by the IP transport to an overlay NB-IOT eNB BBU, which can communicate with an EPC for NB-IOT.
  • Figure 4 illustrates a protocol stack according to certain embodiments. More specifically, Figure 4 illustrates a protocol stack for the case where the conventional LTE eNB is a distributed-RAN eNB. Two paths are shown: a first path shown with a solid line for the processing of signals corresponding to conventional LTE, and a second path shown with a broken line for the processing of signals corresponding to narrow-band internet of things.
  • data corresponding to narrow-band internet of things can be multiplexed (in downlink) or demultiplexed (in uplink) with data for conventional LTE.
  • This multiplexing or demultiplexing may occur based on physical layer (LI) data, or based on a modified form of physical layer data (sometimes referred to as LI ') which may include, for example, pre-FFT data on downlink or post-FFT data on uplink.
  • LI physical layer
  • LI ' modified form of physical layer data
  • a backhaul interface for the conventional LTE eNB which may use an internet protocol (IP)-based transport, can transport both SI protocol packets to or from the EPC as well as packetized data for narrow-band internet of things to or from the overlay NB- IOT eNB.
  • IP internet protocol
  • An overlay NB-IOT eNB can perform multiple layers of protocol and signal processing for narrow-band internet of things, including either full physical layer (LI) processing or partial physical layer processing (sometimes known as LI ').
  • the overlay NB-IOT eNB may be virtualized or not virtualized.
  • a conventional LTE eNB may be modified to take on additional functionality, for example to accomplish the features shown in Figure 4, or for other reasons.
  • the eNB can be configured to multiplex (Mux) downlink (DL) LI or LI ' data received from NB-IOT eNB for PRBs corresponding to NB-IOT carriers.
  • the eNB can also be configured to demultiplex (Demux) uplink (UL) LI or LI ' data to send to an NB-IOT eNB for PRBs corresponding to NB-IOT carriers.
  • Figure 5 illustrates overlay with a cloud RAN LTE eNB, according to certain embodiments. More particularly, Figure 5 illustrates an embodiment wherein the conventional LTE eNB is a cloud RAN eNB or a cloud BTS.
  • a portion of the conventional LTE baseband functions for example non-real-time baseband functions (referred to as BB-NRT) are performed in a virtualized manner in an edge cloud.
  • Other baseband functions for the conventional LTE for example real-time baseband functions(referred to BB-RT), are typically performed in a non-virtualized manner at a baseband unit which may be closer to the cell-site from where over-the-air transmissions will take place.
  • the BB-RT module can multiplex narrow-band internet of things data along with conventional LTE data for transmission in downlink, or demultiplex after reception in uplink.
  • the multiplexing or demultiplexing of data may happen at LI or LI ' in a manner similar to the embodiment of Figure 4.
  • the data for narrow-band internet of things can be sent between the BB-RT module and an overlay NB-IOT eNB via an IP transport network.
  • the overlay NB-IOT eNB may perform all or part of the baseband protocol and signal processing for narrow-band internet of things.
  • the overlay NB-IOT eNB itself may be virtualized and/or hosted in the edge cloud along with the BB-NRT for conventional LTE.
  • the NB-IOT overlay eNB may be managed by the same EMS as the conventional LTE eNB, or a separate one.
  • the virtualized NB-IOT eNB may be created in the same cloud data center as the cloud-LTE BTS, or a separate data center. If the same cloud data center is used, a common management and orchestration framework may be used for both the NB-IOT virtualized overlay as well as the conventional LTE cloud BTS.
  • Figure 6 illustrates latency in connection with certain embodiments.
  • Figure 6 illustrates latency tolerance of the interface between overlay NB-IOT eNB and Conventional LTE eNB.
  • NB-IOT hybrid automatic repeat request
  • DCI downlink control information
  • NB-PDCCH narrow-band physical downlink control channel
  • the UE would automatically retransmit 4 transmission time intervals (TTI) after initial physical uplink shared channel (PUSCH) Tx if ACK/NACK not received on physical HARQ indicator channel (PHICH), which can constrain the fronthaul latency in LTE.
  • TTI transmission time intervals
  • PUSCH physical uplink shared channel
  • PHICH physical HARQ indicator channel
  • NB-IOT is designed for very low throughput - just one HARQ process anyway - thus peak throughput is not important.
  • normal LTE operation for broadband traffic may have a need to maintain peak throughput by avoiding HARQ stall. This need to maintain peak throughput can significantly constrain the fronthaul latency.
  • NB-IOT UEs may not be expected to support high mobility and seamless handover. Thus, additional latency will also not degrade the control-plane ley performance indicators (KPIs), such as handover failure rates. Due to this, even the real-time baseband functions of NB-IOT (L2/Sch/Ll) can be at significant latency away from the RF, for example 5ms one-way. Due to RACH response timing, the maximum latency may be limited to ⁇ 4.5s.
  • FIG. 6 shows NB-IOT UE Tx RACH on UL.
  • the eNB sends RACH response.
  • TTI N transmission time interval
  • the UE sends PRACH in this example.
  • TTI N+6 the network can send the PRACH response.
  • a maximum (Max) RACH response window may be 10 ms
  • a response could be sent as late as TTI N+13.
  • the RACH response window size can have a maximum value of 10 subframes, starting from TTI N+3 in this example.
  • the latency budget available for the interface between NB-IOT eNB and the cell site may thus be 12 ms minus the processing time of NB-IOT baseband.
  • the NB-IOT baseband processing time may include both the actual processing of LI uplink, scheduling, DL medium access control (MAC), and LI downlink, and also fronthaul latency before and after such processing.
  • MAC medium access control
  • the latency budget can thus be constrained by the RACH window, which is a defined value in third generation partnership project (3 GPP) to 12 ms - (processing time of NB-IOT baseband).
  • 3 GPP third generation partnership project
  • NB-IOT round trip travel
  • the max value of the RACH response window advertised in SIB2 can be changed.
  • a user equipment When a user equipment performs a RACH transmission, it may expect a response within a certain window called a RACH response window.
  • the value of this window can be advertised in system information broadcast 2 (SIB 2) messages.
  • SIB 2 system information broadcast 2
  • the latency of the transport network between the conventional LTE eNB and the overlay NB-IOT eNB can affect the time it takes for the NB-IOT eNB to respond to RACH requests received from NB-IOT UEs.
  • the overlay NB-IOT eNB may generate SIB2 messages that indicate an enlarged RACH response window to narrow-band internet of things UEs, for example to allow for a greater latency tolerance on the transport network between the conventional LTE eNB and the overlay NB-IOT eNB.
  • FIG. 7 illustrates latency estimation according to certain embodiments.
  • latency can be measured using a protocol such as two-way active measurement protocol (TWAMP) to determine latency over IP transport between the conventional LTE BB RT and the overlay NB-IOT eNB BBU.
  • TWAMP two-way active measurement protocol
  • a conventional eNB may have its own global positioning system (GPS), and may controls its own common public radio interface (CPRI) link to its own remote radio head (RRH).
  • GPS global positioning system
  • CPRI common public radio interface
  • RRH remote radio head
  • the conventional eNB does not need to be dependent on the NB-IOT eNB for synchronization purposes, and the NB-IOT eNB need not have a very stringent synchronization interface towards the conventional eNB's radio head.
  • the interface between the NB-IOT eNB and the conventional eNB does not need to provide a CPRI-type precise timing/frequency reference or phase synchronization (sync) to the conventional eNB. Accordingly, a relaxed jitter, packetized transport may be adequate.
  • the NB-IOT eNB can estimate the latency between itself and the conventional LTE eNB.
  • the interface between the NB-IOT and LTE eNB can support the TWAMP protocol, which may be suitable for latency estimation. Other protocols are also permitted.
  • Accuracy of synchronization may be, for example, to the level of 1ms. Jitter in the measurements can be estimated and added to the latency estimate, to give an added safeguard.
  • the NB-IOT can round up the estimated latency to the next-higher 1ms value, for safety.
  • the NB-IOT can periodically monitor the latency of the link, in case the latency is variable and changes over time.
  • the conventional LTE eNB may contain various modifications and configurations that are not actually conventional.
  • the conventional LTE eNB can be configured to multiplex DL, LI or LI ', data received from NB-IOT eNB for PRBs corresponding to NB-IOT carriers.
  • the conventional LTE eNB can be configured to demultiplex UL, LI or LI ', data to send to NB-IOT eNB for PRBs corresponding to NB-IOT carriers.
  • Figure 8 illustrates a multiplexing method, according to certain embodiments. More particularly, Figure 8 illustrates multiplexing data into correct subframe at the LTE eNB.
  • the LD LI (or LI ') data received from the NB-IOT can arrive with some potentially variable jitter/latency, and may need to be multiplexed into the appropriate sub-frame for over-the-air transmission.
  • the LTE eNB can send time-stamped messages at the start of a subframe to the overlay NB-IOT eNB indicating frame, subframe number or any suitable timing reference indication. These time-stamped messages can be sent at some periodicity: either every subframe, or every frame, or some suitable periodicity, or may even be sent aperiodically.
  • the NB-IOT eNB can then use its estimate of the latency of the path to the LTE eNB together with the time-stamped messages to know which is the current TTI.
  • the NB-IOT eNB can use this estimated latency to determine how early the narrow-band internet of things data corresponding to a given frame/subframe needs to be sent so as to ensure that it will be received at the conventional LTE eNB early enough to allow multiplexing with conventional LTE data and transmission in the desired frame/subframe.
  • the latency can be estimated using, for example, TWAMP.
  • the Ll/Ll ' data sent by the NB-IOT eNB to the LTE eNB can be packetized and each packet can indicate an appropriate indication of a time and/or frequency resource, such as a frame/subframe number and/or symbol number and/or PRB or subcarrier index or narrow-band carrier index, into which the LTE eNB should multiplex that narrow-band internet of things data.
  • a time and/or frequency resource such as a frame/subframe number and/or symbol number and/or PRB or subcarrier index or narrow-band carrier index
  • This indication can ensure that the LTE eNB can multiplex the DL data sent by the NB-IOT eNB into the correct resources over the air. This may be particularly valuable for certain subframes, which carry information like primary synchronization signal (PSS), or the like, which may need to occur with deterministic timing.
  • PSS primary synchronization signal
  • the LTE enB can send an indication to the NB-IOT eNB.
  • the indication can, for example, indicate that the data was too late.
  • the indication can further indicate the amount of time by which the data was too late, which may allow the NB-IOT to adjust its latency/jitter estimate.
  • the execution of L2/L1 processing of a given TTI can be left-shifted by the estimated one-way latency, that is, executed earlier in time by an amount based on the latency, to ensure that the processing finishes sufficiently early for the NB-IOT data to be received at the conventional eNB in time.
  • the amount of the left-shift can be adjusted based on the data too late indication.
  • the NB-IOT eNB can perform path latency estimation. Then, at some subsequent time, the conventional LTE eNB can send a TTI start indication, which can include information such as frame and/or subframe.
  • the NB-IOT eNB can perform L2/L1 processing for subframe N, and can send DL data for subframe N, including frame/subframe number. If the data arrives in time, the LTE eNB can multiplex the downlink data into an appropriate subframe.
  • the NB-IOT eNB can perform L2/L1 processing for subframe N+l, and can send DL data for subframe N+l, including frame/subframe number. If the data is received too late, then the LTE eNB can stop from multiplexing the DL data into a subframe, as it may be too late to do so into the appropriate subframe. The LTE eNB can, however, send an indication of data received too late to the NB-IOT eNB.
  • the UE For UL retransmissions, the UE has to be awake to monitor for the NB- PDCCH grants for ACK/NACK and retransmissions, and the UE starts monitoring >3ms after the original PUSCH Tx. If the NB-IOT eNB is only going to respond after a longer latency, this is wasted battery at the NB-IOT UE to monitor for the NB-PDCCH.
  • the NB- IOT eNB can provide a parameter to the NB-IOT UE (e.g. by RRC) to provide an enlarged offset between the timing of the PUSCH transmission and the minimum timing of the DCI that will provide the ack/nack and retransmission grant, that accounts for the additional fronthaul latency.
  • RRC Radio Resource Control
  • Figure 9 illustrates a mechanism for supporting longer latency, according to certain embodiments. This may be a potential enhancement for NB-IOT UE battery life to support longer latency.
  • the NB-IOT eNB can indicate to the NB-IOT user equipment a minimum offset between PUSCH transmission timing and timing of DCI with ack/nack and transmission information. This indication can be provided, for example, in a radio resource control (RRC) message.
  • RRC radio resource control
  • the NB-IOT eNB can estimate the latency between itself and the conventional LTE eNB.
  • the interface between the NB-IOT and LTE eNB can support TWAMP.
  • the NB-IOT eNB can use this estimated latency in providing the offset/timing parameter to the NB-IOT UE.
  • Figure 10 illustrates support of standalone-band or guard-band deployment, according to certain embodiments.
  • Figure 10 illustrates an example of support of guard-band or standalone-band deployment of NB-IOT.
  • the above discussion has addressed support of in-band NB-IOT using an overlay NB-IOT eNB along with a conventional LTE eNB, NB-IOT may also be deployed in the frequencies corresponding to the guard band of conventional LTE carrier, or as a standalone carrier, for example refarmed GSM carrier.
  • the NB-IOT eNB can directly interface to the RRH supporting the guard-band/standalone NB-IOT carrier. There may be no need for multiplexing LTE eNB's resource allocation with NB-IOT enB's resource allocation, or the like. The same latency/jitter-tolerant interface considerations can still apply to the interface between the NB-IOT eNB and the RRH.
  • FIG. 10 there can be two data paths through the system: from the overlay NB-IOT-eNT BBU to the RRH for guard-band standalone-band NB-IOT and from the overlay NB-IOT-eNT BBU to the conventional LTE BB-RT.
  • the former path can be used for standalone / guard-band NB-IOT, whereas the latter can be used for in-band NB-IOT.
  • Both paths can go through the IP transport and additionally through a cell-site router. Even for a standalone or guard-band deployment of narrow band internet of things, the latter path can be used.
  • FIG. 11 illustrates a method according to certain embodiments.
  • the method can include, at 1110, receiving downlink data corresponding to a narrow-band internet-of-things carrier.
  • the data corresponding to the narrow-band internet-of-things carrier can be a representation of a signal or protocol data for a narrow-band internet-of-things transmission, for example layer one (LI) or layer one prime (LT) data.
  • LI layer one
  • LT layer one prime
  • the data corresponding to the narrow-band internet-of-things carrier can be packetized data.
  • Each packet of the packetized data can include an indicator that indicates that provides a time or frequency index indicating where the data corresponding to the narrow-band internet-of-things carrier is to be multiplexed.
  • the indicator can indicate at least one of a frame or subframe number into which the data corresponding to the narrowband internet-of-things carrier is to be multiplexed. More generally than a frame or subframe number, the indication may be a time indication for a particular symbol within a subframe, and may include a frequency indication like a PRB number (or subcarrier number), or a resource element indication (time+frequency). A broad range of time/ frequency/ resource indications may be used.
  • the method can also include, at 1120, conditionally multiplexing the downlink data to at least one physical resource block together with other data.
  • the other data can be data unrelated to narrow-band internet-of-things.
  • the method can further include, at 1130, transmitting the multiplexed data on the narrowband internet-of-things carrier. Transmitting the multiplexed data can refer to transmitting the multiplexed data over the air, but can also refer to sending the multiplexed data from a baseband unit to a remote radio head for transmission over the air, for example in the form of I/Q samples over a common public radio interface (CPRJ).
  • CPRJ common public radio interface
  • the method can additionally include, at 1 105, sending at least one time-stamped message indicating a time reference to a narrow band internet of things access point, for example sending a time-stamped message at a start of a subframe, indicating the subframe, to a narrow-band internet-of- things access point periodically.
  • a value of the indicator that indicates at least one of the frame or subframe number can be based on the time-stamped message.
  • the method can further include, at 1 115, determining whether to multiplex the downlink data based on the indicator.
  • the method can additionally include, at 1 125, when the determination is not to multiplex the downlink data, sending an indication of a reason for the determination to a narrow-band internet-of-things access point
  • Figure 12 illustrates another method according to certain embodiments.
  • a method can include, at 1210, preparing downlink data to be transmitted on a narrow-band internet-of-things carrier.
  • the method can also include, at 1220, providing with the downlink data an indicator indicating at least one of a time or frequency resource where the downlink data is to be transmitted multiplexed with other data.
  • a value of the indicator can be based on receipt of a time-stamped message.
  • the message can be one of a plurality of messages sent at a predetermined periodicity.
  • the method can further include at 1230, determining a latency between a narrow-band internet-of-things access point and another access point.
  • the method can additionally include, at 1240, calculating a value for the indicator based on the latency.
  • the method can also include, at 1245, adjusting an indication of a RACH response window in system information broadcast messages based on the determined latency.
  • the method can also include, at 1250, transmitting the downlink data with the indicator.
  • the method can further include, at 1260, receiving an indication that the downlink data was received too late to be multiplexed.
  • the method can further include, at 1270, adjusting an offset for a value of an indicator for a subsequent downlink data.
  • the method can additionally include, at 1280, recalculating the latency based on the indication.
  • Figure 13 illustrates a system according to certain embodiments of the invention.
  • a system may include multiple devices, such as, for example, at least one UE 1310, at least one NB-IOT access point 1320, which may be an eNB, or other base station or access point, and at least one other access point 1330, which may be an LTE access point, such as the conventional LTE eNB mentioned above.
  • Each of these devices may include at least one processor, respectively indicated as 1314, 1324, and 1334.
  • At least one memory can be provided in each device, and indicated as 1315, 1325, and 1335, respectively.
  • the memory may include computer program instructions or computer code contained therein.
  • the processors 1314, 1324, and 1334 and memories 1315, 1325, and 1335, or a subset thereof, can be configured to provide means corresponding to the various blocks of Figures 11 and 12.
  • transceivers 1316, 1326, and 1336 can be provided, and each device may also include an antenna, respectively illustrated as 1317, 1327, and 1337.
  • antenna 1337 can illustrate any form of communication hardware, without requiring a conventional antenna.
  • Transceivers 1316, 1326, and 1336 can each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that is configured both for transmission and reception.
  • Processors 1314, 1324, and 1334 can be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device.
  • the processors can be implemented as a single controller, or a plurality of controllers or processors.
  • Memories 1315, 1325, and 1335 can independently be any suitable storage device, such as a non-transitory computer-readable medium.
  • a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory can be used.
  • the memories can be combined on a single integrated circuit as the processor, or may be separate from the one or more processors.
  • the computer program instructions stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • the memory and the computer program instructions can be configured, with the processor for the particular device, to cause a hardware apparatus such as UE 1310, NB-IOT access point 1320, and other access point 1330, to perform any of the processes described herein (see, for example, Figures 11 and 12). Therefore, in certain embodiments, a non-transitory computer- readable medium can be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments of the invention can be performed entirely in hardware.
  • Figure 13 illustrates a system including a UE, NB-IOT access point, and other access point
  • embodiments of the invention may be applicable to other configurations, and configurations involving additional elements.
  • additional UEs may be present, and additional core network elements may be present.
  • Certain embodiments may have various benefits and/or advantages. For example, certain embodiments may enable rapid introduction of NB-IOT, as possibly fully virtualized overlay, without disrupting existing LTE deployments. Furthermore, certain embodiments may enable co-hosting at edge cloud of NB-IOT (virtualized) RAN with (virtualized) EPC optimized for NB-IOT, as well as possibly with application-layer frameworks.
  • Certain embodiments may provide an opportunity for an operator to provide a vertically integrated platform for IOT including EPC and RAN. Moreover, certain embodiments may enable early introduction of network- slicing for IOT, such as an end-to-end (E2E) IOT slice that is fully virtualized and customizable to needs of individual tenants
  • LTE Long Term Evolution
  • eNB evolved Node B
  • EPC Evolved Packet Core
  • LTE-M LTE Cat-Mi
  • LTE-Cat-Ml LTE category Ml
  • RRH Remote Radio Head
  • IP Internet Protocol

Abstract

La présente invention concerne divers systèmes de communication qui peuvent bénéficier d'un recouvrement de capacités. Par exemple, certains systèmes de communication sans fil peuvent bénéficier de l'introduction de capacités de l'Internet des objets (IdO) à bande étroite (NB) dans le réseau radio (RAN) en tant que solution de recouvrement. Un procédé peut consister à recevoir des données de liaison descendante correspondant à un support de l'internet des objets à bande étroite. Le procédé peut également comprendre le multiplexage conditionnel des données de liaison descendante vers au moins un bloc de ressources physiques conjointement avec d'autres données.
PCT/US2017/032925 2017-05-16 2017-05-16 Noeud b évolué de l'internet des objets à bande étroite de recouvrement WO2018212765A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2017/032925 WO2018212765A1 (fr) 2017-05-16 2017-05-16 Noeud b évolué de l'internet des objets à bande étroite de recouvrement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2017/032925 WO2018212765A1 (fr) 2017-05-16 2017-05-16 Noeud b évolué de l'internet des objets à bande étroite de recouvrement

Publications (1)

Publication Number Publication Date
WO2018212765A1 true WO2018212765A1 (fr) 2018-11-22

Family

ID=64274515

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/032925 WO2018212765A1 (fr) 2017-05-16 2017-05-16 Noeud b évolué de l'internet des objets à bande étroite de recouvrement

Country Status (1)

Country Link
WO (1) WO2018212765A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10887187B2 (en) 2019-05-14 2021-01-05 At&T Mobility Ii Llc Integration of a device platform with a core network or a multi-access edge computing environment
CN113056028A (zh) * 2021-02-07 2021-06-29 青岛海尔空调器有限总公司 用于设备入网的方法、装置和窄带物联网设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150173048A1 (en) * 2012-06-20 2015-06-18 Lg Electronics Inc. Signal transmission/reception method and apparatus therefor
WO2015131959A1 (fr) * 2014-03-07 2015-09-11 Telefonaktiebolaget L M Ericsson (Publ) Manipulation de messages
US20160119184A1 (en) * 2014-10-27 2016-04-28 Qualcomm Incorporated Dynamically reconfigurable radio air interface for communicating over a mesh network and a wide area network
WO2016176642A1 (fr) * 2015-04-30 2016-11-03 Cohere Technologies, Inc. Système de modulation d'espace temps-fréquence orthogonal pour l'internet des objets
WO2017039373A1 (fr) * 2015-09-02 2017-03-09 Lg Electronics Inc. Procédé et appareil d'indication de décalage de fréquence centrale pour ue à bande étroite dans un système de communications sans fil
WO2016200238A9 (fr) * 2015-06-11 2017-03-09 Lg Electronics Inc. Procédé et appareil pour configurer un internet des objets cellulaire dans un système de communication sans fil
WO2017111517A1 (fr) * 2015-12-22 2017-06-29 Samsung Electronics Co., Ltd. Procédé et appareil pour commander des communications à bande passante étroite dans un système de communication sans fil

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150173048A1 (en) * 2012-06-20 2015-06-18 Lg Electronics Inc. Signal transmission/reception method and apparatus therefor
WO2015131959A1 (fr) * 2014-03-07 2015-09-11 Telefonaktiebolaget L M Ericsson (Publ) Manipulation de messages
US20160119184A1 (en) * 2014-10-27 2016-04-28 Qualcomm Incorporated Dynamically reconfigurable radio air interface for communicating over a mesh network and a wide area network
WO2016176642A1 (fr) * 2015-04-30 2016-11-03 Cohere Technologies, Inc. Système de modulation d'espace temps-fréquence orthogonal pour l'internet des objets
WO2016200238A9 (fr) * 2015-06-11 2017-03-09 Lg Electronics Inc. Procédé et appareil pour configurer un internet des objets cellulaire dans un système de communication sans fil
WO2017039373A1 (fr) * 2015-09-02 2017-03-09 Lg Electronics Inc. Procédé et appareil d'indication de décalage de fréquence centrale pour ue à bande étroite dans un système de communications sans fil
WO2017111517A1 (fr) * 2015-12-22 2017-06-29 Samsung Electronics Co., Ltd. Procédé et appareil pour commander des communications à bande passante étroite dans un système de communication sans fil

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10887187B2 (en) 2019-05-14 2021-01-05 At&T Mobility Ii Llc Integration of a device platform with a core network or a multi-access edge computing environment
US11601340B2 (en) 2019-05-14 2023-03-07 At&T Mobility Ii Llc Integration of a device platform with a core network or a multiaccess edge computing environment
CN113056028A (zh) * 2021-02-07 2021-06-29 青岛海尔空调器有限总公司 用于设备入网的方法、装置和窄带物联网设备
CN113056028B (zh) * 2021-02-07 2023-03-21 青岛海尔空调器有限总公司 用于设备入网的方法、装置和窄带物联网设备

Similar Documents

Publication Publication Date Title
JP7120374B2 (ja) 端末装置及び通信方法
US11576059B2 (en) Communication device, communication method, and communication system
CN110140396B (zh) 无线通信设备、无线通信方法和存储介质
KR101988506B1 (ko) 무선 이동통신 시스템에서 디스커버리 신호를 송/수신하는 방법 및 장치
JP7209456B2 (ja) 基地局装置、端末装置、通信方法、及びプログラム
EP3439380B1 (fr) Dispositif de terminal, dispositif de station de base, procédé de communication et procédé de commande
TWI733733B (zh) 終端裝置、基地台裝置及通訊方法
JP7359269B2 (ja) 端末装置、基地局装置、通信方法およびプログラム
EP3166350B1 (fr) Dispositif de station mobile et dispositif de station de base
EP3500013B1 (fr) Dispositif de communication, procédé de communication, et programme pour double connectivité
EP3324682A1 (fr) Systèmes, procédés et dispositifs de mise en réseau opportuniste
WO2017183252A1 (fr) Appareil terminal, appareil station de base et procédé de communication
JP6911296B2 (ja) 通信装置、通信方法、及びプログラム
KR20190018736A (ko) 강화된 허가 보조 액세스를 위한 주기적 및 비주기적 csi 리포팅 절차들
CN109150486B (zh) 测量方法和用户设备
KR101982994B1 (ko) 단말 장치, 기지국 장치 및 통신 방법
KR20190040504A (ko) 무선 통신 네트워크에 대한 노드 및 동작 방법
US20220393794A1 (en) Timer handling in multiple active grant configurations
EP3429265A1 (fr) Procédé de gestion de ressources et dispositif associé
TW201739288A (zh) 終端裝置、基地台裝置及通訊方法
CN116368884A (zh) 利用朝向多个trp的时隙内重复的pucch增强的系统和方法
US9717103B2 (en) Wireless communication system, terminal apparatus, base station apparatus, wireless communication method, and integrated circuit
WO2018212765A1 (fr) Noeud b évolué de l'internet des objets à bande étroite de recouvrement
JP2024515464A (ja) サイドリンクベースの測距と測位のためのプロトコル交換パラメータ
WO2016121608A1 (fr) Station de base et terminal d'utilisateur

Legal Events

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

Ref document number: 17910304

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17910304

Country of ref document: EP

Kind code of ref document: A1