Patent Application
20180192469
The present disclosure relates, in general, to wireless communications and, more particularly, to methods for controlling connected mode discontinuous reception operations.
Narrow Band Internet-of-Things (NB-IoT) is a narrowband (180 KHz bandwidth) system being developed for cellular Internet-of-Things (IoT) by the Third Generation Partnership Project (3GPP). The system is based on Long Term Evolution (LTE) systems, and addresses optimized network architecture and improved indoor coverage for a massive number of devices with any of the following characteristics: low throughput (e.g., 2 Kbps); low delay sensitivity (e.g., ˜10 seconds); ultra-low device cost (e.g., below 5 dollars); and low device power consumption (e.g., battery life of 10 years).
It is envisioned that each cell (e.g., ˜1 Km2) in this system will serve thousands (e.g., ˜50,000) devices such as sensors, meters, actuators, and other devices. It is imperative that this system be able to provide good coverage for its devices, which are often located deep indoors (e.g., underground in basements, or even built into walls of a building) and have limited or no possibility for battery charging. Although many different types of devices are envisioned, for the sake of simplicity they will be interchangeably referred to herein as user equipment (UEs) or wireless devices.
In order to make it possible to deploy NB-IoT using only one re-farmed GSM carrier and support lower manufacturing costs for NB-IoT UEs, the bandwidth has been reduced to one physical resource block (PRB) of size 180 KHz divided into several subcarriers.
For frequency division duplex (FDD) (i.e., the transmitter and the receiver operate at different carrier frequencies), only half-duplex mode needs to be supported in the UE. The lower complexity of the devices (e.g., only one transmission/receiver chain) means that some repetition might also be needed in normal coverage. Further, to alleviate UE complexity, the working assumption is to have cross-subframe scheduling. That is, a transmission is first scheduled on an Enhanced Physical Downlink Control Channel (E-PDCCH, also known as narrowband Physical Downlink Control Channel (NB-PDCCH or NPDCCH). Then, the first transmission of the actual data on the narrowband Physical Downlink Shared Channel (NB-PDSCH or NPDSCH) is carried out after the final transmission of the NB-PDCCH. Similarly, for uplink (UL) data transmission, information about resources scheduled by the network and needed by the UE for UL transmission is first conveyed on the NB-PDCCH and then the first transmission of the actual data by the UE on the narrowband Physical Uplink Shared Channel (NB-PUSCH or NPUSCH) is carried out after the final transmission of the NB-PDCCH. In other words, for both cases above, there is no simultaneous reception of control channel and reception/transmission of data channel from the UE's perspective.
In legacy cellular communication systems like High Speed Packet Access (HSPA) and LTE, a re-transmission procedure called Hybrid Automatic Repeat reQuest (HARQ) with soft combining is supported. After a data block is transmitted in one direction (e.g., between a UE and a radio base station) feedback on the decoding result is usually transmitted in the reverse direction, denoted as a HARQ feedback message. This feedback message is typically either a “binary” decoding result or a scheduling grant/assignment message. In cases where the feedback is a “binary” decoding result, the feedback may be in the form of an acknowledgement (ACK) indicating that data block decoding was successful, or a negative acknowledgement (NACK) indicating that data block decoding was unsuccessful. In cases where the feedback is in the form of a scheduling grant/assignment message, the scheduling grant/assignment message may request either a re-transmission (in the event that data block decoding is unsuccessful, similar to the NACK described above) or a transmission of a new data block that implicitly acknowledges that the previous data block was successfully decoded (similar to the ACK described above).
In some cases, HARQ feedback information could also be indicated by no transmission (DTX). In such a scenario, no transmission means either ACK or NACK (typically the latter) and transmitting something (e.g., a preamble or some other signal/code) could indicate an ACK. Lack of transmitting a HARQ feedback message could also be possible to indicate either a successful or unsuccessful decoded data block (i.e., ACK or NACK). The HARQ feedback (or lack of it) then triggers the re-transmission, or, if the data was received successfully and more data is available, a new data transmission could be started.
Typically, multiple so-called HARQ processes are used in parallel (e.g., in HSPA and LTE). A HARQ process is a stop-and-wait (SAW) HARQ entity that independently transfers data packets and waits for HARQ feedback before either a re-transmission or a new transmission is transmitted. In legacy LTE FDD, typically eight HARQ processes are supported per direction. The same applies to HSPA with 2 ms UL transmission time interval (TTI).
Synchronous HARQ operation means the retransmissions occur at a fixed time after the previous transmission. In asynchronous HARQ operation, on the other hand, the retransmissions can occur at any time after a previous transmission. In both legacy LTE and in HSPA, the UL uses synchronous HARQ and the downlink (DL) uses asynchronous HARQ.
To reduce UE battery consumption, a concept called connected mode discontinuous reception (DRX) is used, which allows the UE to go into sleep mode (i.e., no reception and/or transmission is required) during connected mode in LTE. The main idea is that when there has not been any transmission and/or reception activity (e.g., no transmissions/re-transmissions and no pending re-transmissions) for a period of time, the UE can go into sleep mode and only needs to be awake periodically for a short amount of time every DRX cycle to monitor the DL control channel. If new UL data becomes available, the UE can wake up at any time but needs to inform the network through configured UL resources (for example, a scheduling request could be triggered to be sent on Physical Uplink Control Channel (PUCCH)).
The DRX operation is defined in 3GPP TS 36.321, v. 13.0.0 for legacy LTE and controlled by a set of timers/parameters that are either pre-defined or sent to the UE. Specifically: onDurationTimer; drxStartOffset (from longDRX-CycleStartOffset in 3GPP TS 36.331, v. 13.0.0); longDRX-Cycle (from longDRX-CycleStartOffset in 3GPP TS 36.331, v. 13.3.0); shortDRX-Cycle; drxShortCycleTimer; drx-InactivityTimer; HARQ-RTT-Timer; and drx-RetransmissionTimer. Herein, citations to a particular version of the standard (e.g., TS 36.331, v. 13.0.0) are intended as representative versions available when the application was originally filed. However, other versions may also apply, as appropriate.
In legacy LTE, no retransmission timers are needed if there is an UL re-transmission 425, as synchronous HARQ is used. Synchronous HARQ provides the exact timing on when the HARQ feedback (e.g., ACK 435 and/or NACK 430) and the re-transmission is scheduled. A new grant on DL control channel 410 (e.g., PDCCH) could also be given at the same sub-frame as NACK 430 is sent on the Physical Hybrid Indicator Channel (PHICH) and then the re-transmission is called “adaptive.” The N+4 offsets between UL grant 405 and UL transmission 420, between uplink transmission 420 and NACK 430, between NACK 430 and UL retransmission 425, and between UL retransmission 425 and ACK 435 are shown as elements 220a, 220b, 220c, and 220d, respectively.
Note that in the example of
In 3GPP Release 13, a work item for enhanced Machine-Type Communication (eMTC) has been ongoing, in which changes have been made to HARQ operations as compared to legacy LTE. It has been decided that three parallel HARQ processes are supported. In addition, the UL HARQ has been changed from synchronous to asynchronous, and HARQ feedback is only implicit and received on M-PDCCH (i.e., no PHICH channel exists) earliest N+4 after the PUSCH transmission. As a result, changes are needed to how the UE should enter DRX when there is a re-transmission, as the timing of the HARQ feedback is no longer fixed.
In another work item in 3GPP Release 13 related to licensed-assisted access (LAA), it has also been identified that the UL HARQ needs to be changed from synchronous to asynchronous compared to legacy LTE. The impact of this is described in detail in 3GPP TR 36.889, v. 13.0.0 (and in particular section 7.2.2.2), which is hereby incorporated by reference in its entirety.
In LTE/eMTC all DRX parameters are semi-statically configured in the UE based on Radio Resource Control (RRC) signaling. Some dynamic change is supported through Medium Access Control (MAC) signaling to control the UE entering short/long DRX during the “Active time.”
A problem with existing approaches is that the HARQ/DRX design has been optimized for multiple HARQ processes and use cases where low latency is important and minimizing UE battery consumption has not been the main goal. If the same design is applied to a UE that only supports half-duplex operations, cross subframe scheduling and only one HARQ process, it would result in the UE being awake for a longer time than necessary for many traffic use cases that are typically used in MTC/IoT applications. For example, in many of the traffic use cases there are no simultaneous UL and DL data transfers. Instead, most use cases rely on a request-response type of traffic pattern where an IP packet is sent in one direction followed by a response in the other.
Further, according to existing approaches (both LTE and HSPA) the HARQ operation in the UL is synchronous. If the HARQ operation is changed to asynchronous, it is not known how long the UE shall wait for HARQ feedback after a transmission/re-transmission has been done. One approach would be to copy the DL design also for the UL (i.e., introduce similar timers (e.g., HARQ-RTT-Timer/drx-RetransmissionTimer) also for the UL). Although such an approach might be acceptable for legacy LTE use cases, it is not well suited for use cases in the area of MTC/IoT. These applications involve the use of new, simplified UEs with support for only half-duplex, one HARQ process and cross-subframe scheduling. Thus, a more optimized solution is desirable. The reason for this is that other solutions could reduce the UE battery/power consumption and therefore perform better if the properties of half-duplex, one HARQ process, only cross sub-frame scheduling and typical traffic patterns are utilized in the design.
One goal of NB-IoT is to re-use the legacy LTE (including eMTC changes) as much as possible. An important consideration is how the HARQ and connected mode DRX operations should work. If the legacy design is applied on NB-IoT this would lead to larger battery/power consumption for the UE. Further, since all the DRX-related timers are semi-static, there is very limited flexibility for the eNB to schedule HARQ transmissions/re-transmissions and HARQ feedbacks. If many UEs and/or UEs with different coverage levels (and thus different transmission duration times) need to be served, the previous approaches of having semi-static parameters are not flexible enough to enable short “active time” for UEs. Applying the same design as in legacy LTE would require the use of larger timer values, and thus the UE awake time would be longer resulting in larger battery/power consumption.
To address the foregoing problems with existing solutions, disclosed is a method in a user equipment (UE). The method comprises monitoring a downlink control channel during a duration of at least a first timer. The method comprises receiving, on the monitored downlink control channel, an indication of a downlink or uplink transmission for the UE. The method comprises after receiving the indication of the downlink or uplink transmission for the UE, stopping monitoring the first timer, wherein after the first timer is stopped the UE does not need to monitor the downlink control channel. The method comprises performing an uplink transmission associated with the indicated downlink or uplink transmission for the UE. The method comprises starting a second timer, after receiving the indication of the downlink or uplink transmission for the UE, the duration of the second timer comprising an offset period. The method comprises when the second timer expires, starting a third timer, wherein the UE monitors the downlink control channel for the duration of the third timer.
In certain embodiments, the second timer may be started either: after performing the associated uplink transmission; or at the end of the received indication of the downlink or uplink transmission for the UE.
In certain embodiments, the method may comprise entering a discontinuous reception mode when the third timer expires. The method may comprise receiving a message including information about a duration of at least one of the second and third timers. In certain embodiments, the first timer may be an onDurationTimer of a discontinuous reception cycle. In certain embodiments, at least one of the first timer and the third timer may be a drx-InactivityTimer. In certain embodiments, at least one of the first timer and the third timer may comprise a discontinuous reception retransmission timer. In certain embodiments, the second timer may be a Hybrid Automatic Repeat reQuest (HARQ)-Round Trip Time (RTT) timer that comprises the offset period.
In certain embodiments, the indication of the downlink or uplink transmission for the UE may comprise a downlink scheduling assignment, and the uplink transmission associated with the indicated downlink transmission may comprise an acknowledgement message. In certain embodiments, the indication of the downlink or uplink transmission for the UE may comprise an uplink grant, and the uplink transmission associated with the indicated uplink transmission may comprise a data transmission in the uplink. In certain embodiments, the indication of the downlink or uplink transmission for the UE may comprise information about a duration of at least one of the second and third timers.
Also disclosed is a user equipment (UE). The UE comprises processing circuitry. The processing circuitry is configured to monitor a downlink control channel during a duration of at least a first timer. The processing circuitry is configured to receive, on the monitored downlink control channel, an indication of a downlink or uplink transmission for the UE. The processing circuitry is configured to, after receiving the indication of the downlink or uplink transmission for the UE, stop monitoring the first timer, wherein after the first timer is stopped, the UE does not need to monitor the downlink control channel. The processing circuitry is configured to perform an uplink transmission associated with the indicated downlink or uplink transmission for the UE. The processing circuitry is configured to start a second timer after receiving the indication of the downlink or uplink transmission for the UE, the duration of the second timer comprising an offset period. The processing circuitry is configured to, when the second timer expires, start a third timer, wherein the UE monitors the downlink control channel for the duration of the third timer.
Also disclosed is a method in a network node. The method comprises determining a duration of a first timer and a duration of a second timer, the first and second timers for use by a user equipment (UE) to control discontinuous reception operation, wherein the duration of the first timer comprises an offset period. The method comprises sending, to the UE, information about the duration of the first timer and the duration of the second timer.
In certain embodiments, sending, to the UE, information about the duration of the first timer and the duration of the second timer may comprise sending a message to the UE including the information about the duration of the first timer and the duration of the second timer.
In certain embodiments, the information about the duration of the first timer and the duration of the second timer may be included in an indication of a downlink or uplink transmission for the UE. The method may comprise sending, to the UE, an indication of a downlink or uplink transmission for the UE, and receiving, from the UE, an uplink transmission associated with the indicated downlink or uplink transmission for the UE. In certain embodiments, the indication of the downlink or uplink transmission for the UE may comprise a downlink scheduling assignment, and the uplink transmission associated with the indicated downlink transmission may comprise an acknowledgement message. In certain embodiments, the indication of the downlink or uplink transmission for the UE may comprise an uplink grant, and the uplink transmission associated with the indicated uplink transmission may comprise a data transmission in the uplink.
In certain embodiments, the duration of the first timer comprises one of: an amount of time that the UE waits after sending the uplink transmission associated with the indicated downlink or uplink transmission for the UE before the UE starts the second timer; and an amount of time that the UE waits after the end of the indication of the downlink or uplink transmission for the UE before the UE starts the second timer. In certain embodiments, the first timer may be a Hybrid Automatic Repeat reQuest (HARQ)-Round Trip Time (RTT) timer. In certain embodiments, the duration of the second timer may comprise an amount of time that the UE monitors a downlink control channel before entering a discontinuous reception mode. In certain embodiments, the second timer may be a drx-InactivityTimer.
Also disclosed is a network node. The network node comprises processing circuitry. The processing circuitry is configured to determine a duration of a first timer and a duration of a second timer, the first and second timers for use by a user equipment (UE) to control discontinuous reception operation, wherein the duration of the first timer comprises an offset period. The processing circuitry is configured to send, to the UE, information about the duration of the first timer and the duration of the second timer.
Certain embodiments of the present disclosure may provide one or more technical advantages. For example, certain embodiments may advantageously reduce UE battery and/or power consumption compared to existing approaches. As another example, certain embodiments may advantageously reduce the time the UE needs to be awake to monitor the downlink control channel. As still another example, the amount of time the UE needs to be awake to monitor the downlink control channel can be adapted to the present scheduling situation in the network node (for example, an eNB). As yet another example, because the downlink control channel in NB-IoT needs to be time multiplexed both between UEs and with transmissions on the downlink shared channel, certain embodiments may advantageously enable time multiplexing of the “active time” for UEs, which may increase scheduling flexibility in the network node and allow the UEs to be awake during smaller (i.e., shorter time durations). Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.
For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:
As described above, one important consideration is how the HARQ and connected mode DRX operations should work in NB-IoT. Existing approaches, such as those used in legacy LTE, are not acceptable for the use cases associated with NB-IoT operations. For example, if the legacy design is applied on NB-IoT, this would lead to larger battery and/or power consumption for the UE. Furthermore, since all the DRX-related timers are semi-static, there is very limited flexibility for the eNB to schedule HARQ transmissions/re-transmissions and HARQ feedbacks. If many UEs and/or UEs with different coverage levels (and thus different transmission duration times) need to be served, the existing approaches having semi-static parameters are not flexible enough to enable short “Active time” for UEs. Applying the existing approaches used in legacy LTE to NB-IoT use cases would therefore necessitate the use of larger timer values, which would have the undesirable consequence of increasing the amount of time the UE is required to be awake and, in turn, result in larger battery and/or power consumption by the UE.
The present disclosure contemplates various embodiments that may address these and other deficiencies associated with existing approaches. In certain embodiments, the deficiencies associated with existing approaches may be overcome using a new, flexible way of handling/controlling the “active time” (i.e., the time a UE needs to be awake to monitor a DL control channel) in connected mode for NB-IoT. Generally, two parameters may be used for this: an “active time” that determines how long the UE should be awake to monitor the DL control channel before going into DRX; and an “offset time” that determines when to start the “active time.” In some cases, the “offset time” is set relative to an UL transmission that was triggered by receiving a control message on the DL control channel (e.g., NB-PDCCH). In one non-limiting example, the UL transmission may be either a HARQ feedback message associated with a DL assignment for receiving DL data or an UL grant resulting in an UL transmission of UL data. If a new control message is received on the DL control channel during the “active time,” the “active time” is stopped (i.e., the UE does not need to be awake to monitor the DL control channel). Then, the activity indicated by the control message (DL-assignment or UL-grant) is performed, and new “active time” and “offset time” parameters are used. Information about the values of the two parameters (“active time” and “offset time”) may be provided in any suitable manner. In certain embodiments, the information about the values of the two parameters may be provided per transmission as part of the DL-assignment/UL-grant message sent on the DL control channel, and may vary in-between different DL-assignments/UL-grants.
Aspects of the embodiments described herein are directed to methods performed by a UE in a communication system (e.g., NB-IoT) that controls the connected mode DRX operation and behavior for the UE and a network node (e.g., a radio base station/eNB). In certain embodiments, the method utilizes the properties of the communication capabilities of the NB-IoT devices described above (e.g., half-duplex, one HARQ process, cross-sub-frame scheduling) and typical traffic patterns used to optimize the “active time” for the device (UE) in order to minimize the battery and/or power consumption. Certain embodiments may also advantageously introduce a flexible way of controlling the connected mode DRX operations by dynamically signaling the involved parameters.
According to one example embodiment, a method in a UE is disclosed. The UE monitors a DL control channel during a duration of at least a first timer. The UE receives, on the monitored DL control channel, an indication of a DL or UL transmission for the UE. After receiving the indication of the DL or UL transmission for the UE, the UE stops monitoring the first timer, wherein after the first timer is stopped, the UE does not need to monitor the downlink control channel. The UE performs an UL transmission associated with the indicated DL or UL transmission for the UE. The UE starts a second timer after receiving the indication for the downlink or uplink transmission for the UE, the duration of the second timer comprising an offset period. In certain embodiments, the second timer may be started either: after performing the associated UL transmission; or at the end of the received indication of the DL or UL transmission for the UE. When the second timer expires, the UE starts a third timer, wherein the UE monitors the downlink control channel for the duration of the third channel. In certain embodiments, the UE may enter a discontinuous reception mode when the third timer expires. In certain embodiments, the UE may receive a message including information about a duration of at least one of the second and third timers.
According to another example embodiment, a method in a network node is disclosed. The network node determines a duration of a first timer and a duration of a second timer, the first and second timers for use by a UE to control discontinuous reception operation, wherein the duration of the first timer comprises an offset period. In certain embodiments, the duration of the first timer may comprise one of: an amount of time that the UE waits after sending the uplink transmission associated with the indicated downlink or uplink transmission for the UE before the UE starts the second timer; and an amount of time that the UE waits after the end of the indication of the downlink or uplink transmission for the UE before the UE starts the second timer. In certain embodiments, the duration of the second timer may comprise an amount of time that the UE monitors a DL control channel before entering a discontinuous reception mode. The network node sends, to the UE, information about the duration of the first timer and the duration of the second timer. As one non-limiting example, the network node may send a message to the UE including the information about the duration of the first timer and the duration of the second timer. In some cases, the information about the duration of the first timer and the duration of the second timer may be included in an indication of a DL or UL transmission for the UE.
In certain embodiments, network nodes 515 may interface with a radio network controller. The radio network controller may control network nodes 515 and may provide certain radio resource management functions, mobility management functions, and/or other suitable functions. In certain embodiments, the functions of the radio network controller may be included in network node 515. The radio network controller may interface with a core network node. In certain embodiments, the radio network controller may interface with the core network node via an interconnecting network 520. Interconnecting network 520 may refer to any interconnecting system capable of transmitting audio, video, signals, data, messages, or any combination of the preceding. Interconnecting network 520 may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof.
In some embodiments, the core network node may manage the establishment of communication sessions and various other functionalities for UEs 510. UEs 510 may exchange certain signals with the core network node using the non-access stratum layer. In non-access stratum signaling, signals between UEs 510 and the core network node may be transparently passed through the radio access network. In certain embodiments, network nodes 515 may interface with one or more network nodes over an internode interface, such as, for example, an X2 interface.
As described above, example embodiments of network 500 may include one or more UEs 510, and one or more different types of network nodes capable of communicating (directly or indirectly) with UEs 510.
In some embodiments, the non-limiting term UE is used. UEs 510 described herein can be any type of wireless device capable of communicating with network nodes 515 or another UE over radio signals. UE 510 may also be a radio communication device, target device, D2D UE, machine-type-communication UE or UE capable of machine to machine communication (M2M), low-cost and/or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc. UE 510 may operate under either normal coverage or enhanced coverage with respect to its serving cell. The enhanced coverage may be interchangeably referred to as extended coverage. UE 510 may also operate in a plurality of coverage levels (e.g., normal coverage, enhanced coverage level 1, enhanced coverage level 2, enhanced coverage level 3 and so on). In some cases, UE 510 may also operate in out-of-coverage scenarios.
Also, in some embodiments generic terminology, “radio network node” (or simply “network node”) is used. It can be any kind of network node, which may comprise a base station (BS), radio base station, Node B, multi-standard radio (MSR) radio node such as MSR BS, evolved Node B (eNB), network controller, radio network controller (RNC), base station controller (BSC), relay node, relay donor node controlling relay, base transceiver station (BTS), access point (AP), radio access point, transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), Multi-cell/multicast Coordination Entity (MCE), core network node (e.g., MSC, MME, etc.), O&M, OSS, SON, positioning node (e.g., E-SMLC), MDT, or any other suitable network node.
The terminology such as network node and UE should be considered non-limiting and does in particular not imply a certain hierarchical relation between the two; in general “eNodeB” could be considered as device 1 and “UE” device 2, and these two devices communicate with each other over some radio channel.
Example embodiments of UE 510, network nodes 515, and other network nodes (such as radio network controller or core network node) are described in more detail below with respect to
Although
As described above, certain embodiments provide novel methods for controlling DRX operations in connected mode. In the following description of various non-limiting example embodiments, certain assumptions can be made with respect to scheduling and HARQ operations for NB-IoT. First, it is assumed that DL/UL data is scheduled by a message on the DL control channel (e.g., NB-PDCCH). Second, it is assumed that DL/UL data is transmitted on the shared channels (e.g., NB-PDSCH and NB-PUSCH, respectively). Third, it is assumed that HARQ feedback is transmitted on the channels NB-PDCCH/NB-PUSCH (the UL resource for HARQ feedback is assumed to be sent as part of the DL assignment on NB-PDCCH). Finally, it is assumed that asynchronous HARQ is used in both DL and UL. Note that the scope of the present disclosure is not limited to the various example embodiments described herein. In some cases, none, some, or all of the above assumptions may apply.
As described above, a UE 510 may monitor a DL control channel (e.g., NB-PDCCH). Herein, the time when UE 510 monitors the DL control channel is referred to as the “active time.” The behavior of UE 510 in relation to the start of the “active time,” stop of the “active time,” expiration of the “active time” and how to retrieve information of the length and start of “active time” is described generally below in the context of
In certain embodiments, the behavior of UE 510 is described in the context of NB-IoT, and when the “active time” expires UE 510 is said to enter DRX operation in a similar way as in legacy LTE (i.e., the NB-PDCCH is only monitored during an “On Duration time” every DRX cycle). Note, however, that the various embodiments described herein are not limited to the NB-IoT context. Rather, the present disclosure contemplates that the various embodiments described herein are applicable to any suitable RATs.
In general, two main parameters are used: an “active time” that determines for how long a time the UE should be awake to monitor the DL control channel before going into DRX; and an “offset time” that determines when to start the “active time.” As described above, the “offset time” (which may be referred to herein interchangeably as “offset period”) is started relative to an UL transmission performed by UE 510 that was triggered by receiving an indication of a DL or UL transmission for UE 510 (e.g., a control message on the DL control channel (e.g., NB-PDCCH), such as: a DL assignment for receiving DL data resulting in that the UL transmission is a HARQ feedback message; or an UL grant resulting in that said UL transmission is UL data).
If a new control message is received on the DL control channel during the “active time,” the “active time” is stopped (i.e., the UE does not need to be awake to monitor the DL control channel (e.g., NB-PDCCH). Instead, the activity as said control message (e.g., DL-assignment or UL-grant) indicated is first performed and a new “active time” and “offset time” are used.
In certain embodiments, information about the values of the two parameters (“active time” and “offset time”) is provided per transmission as part of the DL-assignment/UL-grant message sent on the DL control channel, and may vary in-between every DL-assignment/UL-grant. For example, in certain embodiments a network node (e.g., network node 515) may determine a duration of the “active time” and the “offset time” for use by UE 510 to control DRX operation. Network node 515 may send information about the durations of the “active time” and the “offset time” to UE 510. Network node 515 may send the information to UE 510 in any suitable manner. As one example, network node 515 may send a message to UE 510 including information about the duration of the “active time” and the “offset time.” As another example, the information about the duration of the “active time” and the “offset time” may be included in the indication of a DL or UL transmission for UE 510 (e.g., a control message on the DL control channel (e.g, NB-PDCCH), such as: a DL assignment for receiving DL data resulting in that the UL transmission is a HARQ feedback message; or an UL grant resulting in that said UL transmission is UL data).
Although certain example embodiments may be described in terms of parameters described as time durations, this is for purposes of example only. The various embodiments described herein are not limited to such examples. Rather, the present disclosure contemplates that timers may be used instead when implementing, specifying, describing, and/or modeling these features of the various embodiments. Persons skilled in the art understand that descriptions using a time duration or a timer may be equivalent. In some cases, when implementing the various embodiments described herein in a device, a timer could preferably be used. In such a scenario, UE 510 may start a timer (with duration “offset time”) after the UL transmission ends, and upon expiry of said timer a new timer (with duration “offset time”) may be started, and while running UE 510 monitors the DL control channel (e.g., NB-PDCCH). Although the use of multiple timers is discussed herein, according to alternative embodiments, fewer timers (or even no timers) may be used, as long as time duration is still monitored and determined.
For example, in certain embodiments UE 510 monitors a DL control channel (e.g., NB-PDCCH) during a duration of at least a first timer. In certain embodiments, one or more timers may be running at this time. In certain embodiments, the first timer of the one or more timers may be one of an onDurationTimer of a DRX cycle, a drx-InactivityTimer, and a DRX retransmission timer. UE 510 may receive, on the monitored DL control, an indication of a DL or UL transmission for UE 510 (e.g., a DL scheduling assignment or an UL grant, respectively). After receiving the indication of the DL or UL transmission for UE 510, UE 510 may stop monitoring the first timer, and perform an UL transmission associated with the indicated DL or UL transmission for UE 510 (e.g., send an ACK message or a data transmission in the UL). According to certain embodiments, after receiving the indication of the DL or UL transmission for UE 510, UE 510 may also stop monitoring of the DL control channel. According to alternative embodiments, the UE is no longer required to monitor the DL control channel at this point, but may continue to do so. After receiving the indication of the DL or UL transmission, UE 510 starts a second timer, the duration of the second timer comprising an offset period (e.g., a HARQ-RTT timer that comprises an offset period). According to certain embodiments, UE may start the second timer after performing the associated UL transmission. When the second timer expires, UE 510 may start a third timer (e.g., a drx-InactivityTimer or a discontinuous reception retransmission timer). In certain embodiments, UE 510 may monitor the DL control channel during the duration of the third timer, and enter DRX mode when the third timer expires.
The various embodiments will now be described in more detail below with respect to
In the example of
After performing associated UL transmission 635, “active time” 640 is started an “offset time” 645 after UL transmission 635 ends. In embodiments in which timers are used, for example, after performing associated UL transmission 635 (the ACK message in the example of
In the example of
The present disclosure contemplates that information about the various parameters (e.g., length of “offset time” 645 and “active time” 640 or duration of second timer 645 and third timer 640 described above) may be signaled in any suitable manner. For example, they could be part of an L3 message or broadcasted on the system information. In such a scenario, the parameters would be semi-static as in previous approaches and not as flexible as sending them as part of the NB-PDCCH message 605 (e.g., DCI-1 in the example of
In the example of
In the example of
After performing associated UL transmission 710, “active time” 730 is started an “offset time” 735 after UL transmission 710 ends. In embodiments in which timers are used, for example, after performing associated UL transmission 710, the UE starts second timer 735 corresponding to the “offset time” described above. The duration of second timer 735 may be or comprise an offset period. For example, second timer 735 may be a HARQ-RTT timer that comprises an offset period. When second timer 735 expires, the UE starts third timer 730 corresponding to the “active time” described above. In certain embodiments, third timer 730 may be one of a drx-InactivityTimer and a DRX retransmission timer. During “active time” 730 (e.g., during the duration of third timer 730), the UE monitors DL control channel 715 (NB-PDCCH in the example of
In the example of
The present disclosure contemplates that information about the various parameters (e.g., length of “offset time” 735 and “active time” 730 or duration of second timer 735 and third timer 730 described above) may be signaled in any suitable manner. For example, they could be part of an L3 message or broadcasted on the system information. In such a scenario, the parameters would be semi-static and not as flexible as sending them as part of the NB-PDCCH message (e.g., DCI-0705 in the example of
The present disclosure contemplates that the values of the various parameters may be any suitable values. In certain embodiments, the values may vary based on any suitable criteria. For example, the values of the various parameters may depend on the used UL/DL frequency resources, coding rate and number of repetitions (i.e., the redundancy), message/data size, modulation type, network node (e.g., eNB) scheduling strategy, and any other suitable criteria.
In the example of
In the DL assignment case shown in the example of
After performing associated UL transmission 830, “active time” 835 is started an “offset time” 840 after UL transmission 830 ends. In embodiments in which timers are used, for example, after performing associated UL transmission 830 (the NACK message in the example of
In the example of
After performing the associated UL transmission 850, “active time” 860 is started “offset time” 865 after UL transmission 850 ends. In embodiments in which timers are used, for example, after performing the associated UL transmission 850 (the NACK message in the example of
In the example of
Similar to
In the example of
After performing the associated UL transmission, “active time” 930 is started an “offset time” 935 after UL transmission 910 ends. In embodiments in which timers are used, for example, after performing the associated UL transmission 910 (the UL transmission on either of SRB/DRB in the example of
In the UL grant case shown in the example of
After performing second associated UL transmission 945, “active time” 950 is started “offset time” 955 after UL transmission 945 ends. In embodiments in which timers are used, for example, after performing second associated UL transmission 945 (transmission of second SRB/DRB data on NB-PUSCH 920 in the example of
In the example of
The present disclosure contemplates that the values of the various parameters may be any suitable values. In certain embodiments, the values may vary based on any suitable criteria. For example, the values of the various parameters may depend on the used UL/DL frequency resources, coding rate and number of repetitions (i.e., the redundancy), message/data size, modulation type, network node (e.g., eNB) scheduling strategy, and any other suitable criteria.
Similar to
Although the example embodiments of
Alternatively, during monitoring of NB-PDCCH at step 1005 the flow may proceed to step 1030 if the UE receives a message on the downlink control channel (e.g., a DL scheduling assignment or an UL grant).
In some cases, at step 1035 the NB-PDCCH message received at step 1030 may be a DRX order. In such a scenario, the flow proceeds to step 1015, where the UE enters DRX and waits for the next OnDuration occurrence. From there, the DRX operations proceed as described above.
In some cases, at step 1040 the UE determines the content of the message received on the downlink control channel. If at step 1040 the UE determines that the received message is an UL grant, the flow proceeds to step 1045 where the UE transmits UL SRB and/or DRB data on an UL shared channel (NB-PUSCH in the example of
The flow then proceeds to step 1060, where the UE waits for an “offset time.” In certain embodiments, the UE may start a timer. In certain embodiments, the timer may be started either after performing the associated UL transmission (for example, when the UE determines that the received message is an UL grant) or at the end of the received indication of the DL or UL transmission for the UE (for example, when the UE determines that the received message is a DL scheduling assignment). Thus, the duration of the timer may comprise an amount of time that the UE waits after sending the UL transmission at step 1045 before the UE starts an “active time” or an amount of time that the UE waits after the end of the indication of the DL or UL transmission at step 1030 before the UE starts an “active time.” After waiting for the “offset time” at step 1060 (or, in certain embodiments, the timer having the duration of the offset time expires), the flow proceeds to step 1065. At step 1065, the UE starts the active time. In certain embodiments, the UE may start another timer having a duration that is an amount of time that the UE monitors the DL control channel (e.g., NB-PDCCH) before the UE enters DRX mode. After starting the active time at step 1065, the flow returns to step 1005, where the UE monitors NB-PDCCH during the duration of the “active time.”
At step 1108, the UE receives, on the monitored DL control channel, an indication of a DL or UL transmission for the UE. In certain embodiments, the indication of the DL or UL transmission for the UE may comprise information about a duration of at least one of the second and third timers. At step 1112, after receiving the indication of the DL or UL transmission for the UE, the UE stops monitoring the first timer. After the first timer is stopped, the UE does not need to monitor the downlink control channel.
At step 1116, the UE performs an UL transmission associated with the indicated DL or UL transmission for the UE. In certain embodiments, the indication of the DL or UL transmission for the UE may comprise a DL scheduling assignment, and the UL transmission associated with the indicated DL transmission may comprise an acknowledgement message. In certain embodiments, the indication of the DL or UL transmission for the UE may comprise an UL grant, and the UL transmission associated with the indicated UL transmission may comprise a data transmission in the UL.
At step 1120, the UE starts a second timer after receiving the indication for the downlink or uplink transmission for the UE, the duration of the second timer comprising an offset period. In certain embodiments, the second timer may be started either: after performing the associated UL transmission; or at the end of the received indication of the DL or UL transmission for the UE. In certain embodiments, the second timer may be a Hybrid Automatic Repeat reQuest (HARQ)-Round Trip Time (RTT) timer that comprises the offset period. Alternatively, at step 1120, the UE starts a second timer after receiving the indication for the downlink or uplink transmission for the UE.
At step 1124, when the second timer expires, the UE starts a third timer. In certain embodiments, the method may comprise monitoring the DL control channel during the duration of the third timer. In certain embodiments, at least one of the first timer and the third timer may be a drx-InactivityTimer. In certain embodiments, at least one of the first timer and the third timer may be a discontinuous reception retransmission timer.
In certain embodiments, the method may comprise entering a discontinuous reception mode when the third timer expires. In certain embodiments, the method may comprise receiving a message including information about a duration of at least one of the second and third timers.
At step 1208, the network node sends, to the UE, information about the duration of the first timer and the duration of the second timer. In certain embodiments, the information about the duration of the first timer and the duration of the second timer may be included in an indication of a DL or UL transmission for the UE. In certain embodiments, sending, to the UE, information about the duration of the first timer and the duration of the second timer may comprises sending a message to the UE including the information about the duration of the first timer and the duration of the second timer.
In certain embodiments, the method may comprise sending, to the UE, an indication of a DL or UL transmission for the UE, and receiving, from the UE, an UL transmission associated with the indicated DL or UL transmission for the UE. In certain embodiments, the indication of the DL or UL transmission for the UE may comprise a DL scheduling assignment, and the UL transmission associated with the indicated DL transmission may comprise an acknowledgement message. In certain embodiments, the indication of the DL or UL transmission for the UE may comprise an UL grant, and the UL transmission associated with the indicated UL transmission may comprise a data transmission in the UL. According to certain embodiments, the network node may transmit downlink control messages during the duration of the third timer. This may be beneficial when the UE stops monitoring the downlink control channel after a first timer is stopped.
Processing circuitry 1320 may include any suitable combination of hardware and software implemented in one or more modules to execute instructions and manipulate data to perform some or all of the described functions of UE 510, such as the functions of UE 510 described above in relation to
Memory 1330 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, etc. and/or other instructions capable of being executed by a processing circuitry 1320. Examples of memory 1330 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or or any other volatile or non-volatile, non-transitory computer-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1320.
Other embodiments of UE 510 may include additional components beyond those shown in
Network node 515 may include one or more of transceiver 1410, processing circuitry 1420, memory 1430, and network interface 1440. In some embodiments, transceiver 1410 facilitates transmitting wireless signals to and receiving wireless signals from UE 510 (e.g., via antenna 1450), processing circuitry 1420 executes instructions to provide some or all of the functionality described above as being provided by a network node 515, memory 1430 stores the instructions executed by processing circuitry 1420, and network interface 1440 communicates signals to backend network components, such as a gateway, switch, router, Internet, Public Switched Telephone Network (PSTN), core network nodes or radio network controllers 130, etc.
Processing circuitry 1420 may include any suitable combination of hardware and software implemented in one or more modules to execute instructions and manipulate data to perform some or all of the described functions of network node 515, such as those described above in relation to
Memory 1430 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1420. Examples of memory 1430 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or or any other volatile or non-volatile, non-transitory computer-readable and/or computer-executable memory devices that store information.
In some embodiments, network interface 1440 is communicatively coupled to processing circuitry 1420 and may refer to any suitable device operable to receive input for network node 515, send output from network node 515, perform suitable processing of the input or output or both, communicate to other devices, or any combination of the preceding. Network interface 1440 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate through a network.
Other embodiments of network node 515 may include additional components beyond those shown in
Processing circuitry 1520 may include any suitable combination of hardware and software implemented in one or more modules to execute instructions and manipulate data to perform some or all of the described functions of the radio network controller or core network node 130. In some embodiments, processing circuitry 1520 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more applications, and/or other logic.
Memory 1530 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1520. Examples of memory 1530 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or or any other volatile or non-volatile, non-transitory computer-readable and/or computer-executable memory devices that store information.
In some embodiments, network interface 1540 is communicatively coupled to processing circuitry 1520 and may refer to any suitable device operable to receive input for the network node, send output from the network node, perform suitable processing of the input or output or both, communicate to other devices, or any combination of the preceding. Network interface 1540 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate through a network.
Other embodiments of the network node may include additional components beyond those shown in
Determining module 1610 may perform the processing functions of UE 510. For example, determining module 1610 may monitor a DL control channel during a duration of at least a first timer. As another example, determining module 1610 may, after receiving the indication of the DL or UL transmission for the UE, stop monitoring the first timer. After the first timer is stopped, the UE does not need to monitor the downlink control channel. As still another example, determining module 1610 may start a second timer after receiving the indication for the downlink or uplink transmission for the UE, the duration of the second timer comprising an offset period. As yet another example, determining module 1610 may, when the second timer expires, start a third timer. As another example, determining module 1610 may monitor the DL control channel during the duration of the third timer. As another example, determining module 1610 may enter a discontinuous reception mode when the third timer expires.
Determining module 1610 may include or be included in one or more processors, such as processing circuitry 1320 described above in relation to
Communication module 1620 may perform the transmission functions of UE 510. For example, communication module 1620 may perform an UL transmission associated with the indicated DL or UL transmission for the UE. Communication module 1620 may transmit messages to one or more of network nodes 515 of network 500. Communication module 1620 may include a transmitter and/or a transceiver, such as transceiver 1310 described above in relation to
Receiving module 1630 may perform the receiving functions of UE 510. As one example, receiving module 1630 may receive, on the monitored DL control channel, an indication of a DL or UL transmission for the UE. As another example, receiving module 1630 may receive a message including information about a duration of at least one of the second and third timers. Receiving module 1630 may include a receiver and/or a transceiver, such as transceiver 1310 described above in relation to
Input module 1640 may receive user input intended for UE 510. For example, the input module may receive key presses, button presses, touches, swipes, audio signals, video signals, and/or any other appropriate signals. The input module may include one or more keys, buttons, levers, switches, touchscreens, microphones, and/or cameras. The input module may communicate received signals to determining module 1610. The functions of input module 1640 described above may, in certain embodiments, be performed in one or more distinct modules.
Display module 1650 may present signals on a display of UE 510. Display module 1650 may include the display and/or any appropriate circuitry and hardware configured to present signals on the display. Display module 1650 may receive signals to present on the display from determining module 1610. The functions of display module 1650 described above may, in certain embodiments, be performed in one or more distinct modules.
Determining module 1610, communication module 1620, receiving module 1630, input module 1640, and display module 1650 may include any suitable configuration of hardware and/or software. UE 510 may include additional modules beyond those shown in
Determining module 1710 may perform the processing functions of network node 515. For example, determining module 1710 may determine a duration of a first timer and a duration of a second timer, the first and second timers for use by a UE to control discontinuous reception operation, wherein the duration of the first timer comprises an offset period. Determining module 1710 may include or be included in one or more processors, such as processing circuitry 1420 described above in relation to
Communication module 1720 may perform the transmission functions of network node 515. As one example, communication module 1720 may send, to the UE, information about the duration of the first timer and the duration of the second timer. As another example, communication module 1720 may send a message to the UE including the information about the duration of the first timer and the duration of the second timer. As still another example, communication module 1720 may send, to the UE, an indication of a DL or UL transmission for the UE. Communication module 1720 may transmit messages to one or more of UEs 510. Communication module 1720 may include a transmitter and/or a transceiver, such as transceiver 1410 described above in relation to
Receiving module 1730 may perform the receiving functions of network node 515. For example, receiving module 1730 may receive, from the UE, an UL transmission associated with the indicated DL or UL transmission for the UE. Receiving module 1730 may receive any suitable information from a UE. Receiving module 1730 may include a receiver and/or a transceiver, such as transceiver 1410 described above in relation to
Determining module 1710, communication module 1720, and receiving module 1730 may include any suitable configuration of hardware and/or software. Network node 515 may include additional modules beyond those shown in
The following text provides additional explanation regarding certain embodiments and proposals described herein, and should not be seen as limiting the scope of the invention. The functionality for connected mode DRX in legacy LTE and eMTC are based on the following parameters (excluding the short DRX parameters):
The first three parameters can be re-used as is for NB-IoT except for the value ranges that need to be looked into further. The two last parameters are related to how the HARQ operation works. The drx-InactivityTimer parameter is used to control when the UE enters DRX after inactivity (unless a MAC CE is signaled) so the handling of this parameter will mainly be discussed. As it is already decided to support only one HARQ process per direction and if half-duplex operation for the UE is assumed changes/simplifications to these three last parameters could be discussed and made even if the details of the HARQ operations are not fully decided yet.
Due to the NB-IoT UE transmission/reception capabilities being half-duplex and having only one HARQ process per direction the handling of the DRX in-activity timer and the HARQ re-transmission timers for the connected mode DRX could be changed/simplified. Therefore, according to certain embodiments, the legacy parameters drxStartOffset, longDRX-Cycle and OnDurationTimer may be re-used as is for connected mode DRX with value ranges suitable for NB-IoT.
In the following examples it is assumed that the high level concept for HARQ operations for NB-IoT is similar to eMTC. To summarize the following is assumed:
In the upcoming embodiments the DRX operations are explained by applying these HARQ assumptions. Note that the time durations of the transmissions and the offsets in-between transmissions can vary in length. According to one embodiment, we have used the legacy behavior for the DRX operation with the drx-InactivityTimer and applied it to NB-IoT. The timer is started every time there is a new transmission scheduled either in the UL or the DL on the NB-PDCCH. In this case the downlink transmission is successful and no further data is scheduled so the UE goes into DRX sleep at timer expiry.
According to another embodiment there is one HARQ retransmission in the downlink when using the legacy DRX timers in NB-IoT. The timers HARQ-RTT-Timer/drx-RetransmissionTimer are used for this and the latter is cancelled when the re-transmission is received.
Compared to legacy LTE the uplink HARQ for eMTC (and LAA) has been changed from synchronous to asynchronous. It is assumed here that there is probably a need to introduce something similar as the HARQ-RTT-Timer/drx-RetransmissionTimer also for the uplink due to the asynchronous HARQ. For NB-IoT it is assumed that such timers will be needed when discussing the legacy base for DRX. Thus, according to another embodiment, there is a HARQ retransmission in the uplink with assumed new timer. Similar to the downlink case the timer is cancelled when the UE detects that a re-transmission is scheduled. Note that we call it the drx-RetransmissionTimer even if it is not really a “Retransmission Timer” as the UE does not know the result of the transmission. This may also be referred to as a HARQ-FeedbackWindowTimer.
As discussed, the legacy DRX timers could be used also for NB-IoT. This legacy scheme was developed with Mobile Broadband use cases in mind that include multiple HARQ processes in both directions and full duplex operations (except for TDD of course). For these use cases (except for VoLTE) the UE power consumption with regards to being awake a few extra sub-frames here and there is not a problem. However, for NB-IoT it is very important that the UE active time (i.e. when monitoring NB-PDCCH) is as small as possible also during connected mode for many of its use cases in order to get a good UE battery lifetime.
One problem with the legacy approach is how to set the value of the drx-InactivityTimer:
According to particular embodiments, a solution to the above problem would be to change drx-InactivityTimer so that it is re-started at every NB-PDCCH reception, i.e. regardless of if it is a new transmission or a re-transmission (both uplink and downlink). Then a short value of the drx-InactivityTimer could be used at the same time as no extra latency is introduced. If this is done then there is no need for any HARQ-RTT-Timer/drx-RetransmissionTimer as only one timer could be used to supervise both UL/DL re-transmissions and inactivity. This also decreases the UE complexity as only one timer is needed. According to this embodiment, the drx-InactivityTimer is re-started at the reception of any DCI on the NB-PDCCH.
According to additional embodiments, there is no need for the timers HARQ-RTT-Timer and drx-RetransmissionTimer for neither downlink nor uplink if the criterion for starting the timer drx-InactivityTimer is changed. A successful NB-PDCCH reception in the UE will be followed by an uplink transmission that contains of either SRB/DRB data (in case of an UL grant) or HARQ feedback (in case of a DL assignment). If it is assumed that a UE is not required to monitor the NB-PDCCH after being scheduled until after the transmission then additional changes to the start/re-start of the drx-InactivityTimer could be made. The timer should then be stopped at every successful reception of NB-PDCCH and be started after the end of the uplink transmission that was triggered by the NB-PDCCH message. This will enable the UE to be able to turn off its receiver (and potentially enter sleep mode) during more time occasions in connected mode especially if the time gaps in-between NB-PDCCH/NB-PDSCH/NB-PUSCH are long.
According to additional embodiments, stopping the drx-InactivityTimer at successful reception of anything on NB-PDCCH and starting it after the resulting uplink transmission (of DRB/SRB or HARQ feedback) enables the UE to reduce NB-PDCCH monitoring time and thus power consumption. Thus, according to certain embodiments, the start and stop criterion for the drx-InactivityTimer is changed for NB-IoT UEs to control connected mode DRX. According to certain embodiments, the start criterion of drx-InactivityTimer should be changed to after the NB-PUSCH transmission of the HARQ ACK or the DRB/SRB data for a downlink assignment and an uplink grant respectively. According to certain embodiments, the stop criterion of drx-InactivityTimer should be changed to when a downlink assignment or an uplink grant is received. According to certain embodiments, the HARQ-RTT-Timer and the drx-RetransmissionTimer may not be used in NB-IoT. According to certain embodiments, if the drx-InactivityTimer expires the UE does not need to monitor the NB-PDCCH until the next OnDuration occasion.
The majority of the NB-IoT use cases does not include simultaneous uplink/downlink traffic and instead most use cases rely on a request-response type of traffic pattern where an IP packet is sent in one direction followed by a response in the other (potentially repeated according to the same pattern a few times for some use cases). This traffic pattern is also true for the L3 (NAS/RRC) signaling procedures. As a consequence, after HARQ feedback or SRB/DRB data has been transmitted in the uplink by a UE there will not be any NB-PDCCH activity during at least one HARQ round trip time. During this time a NB-IoT UE could be allowed to not monitor the NB-PDCCH. Thus, according to certain embodiments, a change to the drx-InactivityTimer handling would be to not start it until an offset value after the uplink transmission.
In most use cases there is no need for a UE to monitor the NB-PDCCH until at least one roundtrip time after the end of the uplink transmission. Thus, according to certain embodiments, the start of the drx-InactivityTimer should be made at an offset value after the uplink transmission (of DRB/SRB or HARQ feedback) to enable the UE to reduce NB-PDCCH monitoring time. The value of this offset depends as described above on the roundtrip time but also on the physical layer design of the NB-PDCCH, e.g. time alignments and how the NB-PDCCH and NB-PDSCH is multiplexed. The value may even be variable depending on the physical layer design and the coverage class of the UE. According to certain embodiments, the start criterion of the drx-InactivityTimer could be set to at least a roundtrip time after the uplink transmission but the details is left FFS until more details are available from RAN1 on the downlink NB-PDCCH/PDSCH design. According to certain embodiments, semi-static connected mode DRX parameters for NB-IoT is included as part of RrcConnectionReestablish, RrcConnectionSetup, RrcConnectionResume, i.e. as part of Msg3. According to certain embodiments, the semi-static connected mode DRX parameters shall be applied directly when received in the UE.
Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.
Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.
Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure, as defined by the following claims.
Abbreviations used in the preceding description include:
3GPP Third Generation Partnership Project
ACK Acknowledgement
AP Access Point
BS Base Station
BSC Base Station Controller
BTS Base Transceiver Station
CPE Customer Premises Equipment
D2D Device-to-device
DAS Distributed Antenna System
DCI Downlink Control Information
DL Downlink
DRB Data Radio Bearer
DRX Discontinuous Reception
DTX Discontinuous Transmission
eNB evolved Node B
EPDCCH Enhanced Physical Downlink Control Channel
FDD Frequency Division Duplex
HARQ Hybrid Automatic Repeat reQuest
HSPA High Speed Packet Access
IoT Internet-of-Things
LAN Local Area Network
LEE Laptop Embedded Equipment
LME Laptop Mounted Equipment
LTE Long Term Evolution
M2M Machine-to-Machine
MAN Metropolitan Area Network
MCE Multi-cell/multicast Coordination Entity
MCS Modulation level and coding scheme
MIMO Multiple Input Multiple Output
MR Measurement Restriction
MSR Multi-standard Radio
NACK Negative Acknowledgement
NAS Non-Access Stratum
NB Narrowband
NB-IoT Narrowband Internet-of-Things
NB-PDCCH Narrowband Physical Downlink Control Channel
NB-PDSCH Narrowband Physical Downlink Shared Channel
NB-PUSCH Narrowband Physical Uplink Shared Channel
NPDCCH Narrowband Physical Downlink Control Channel
NPDSCH Narrowband Physical Downlink Shared Channel
NPUSCH Narrowband Physical Uplink Shared Channel
OFDM Orthogonal Frequency Division Multiplexing
PDCCH Physical Downlink Control Channel
PDSCH Physical Downlink Shared Channel
PMI Precoded Matrix Indicator
PRB Physical Resource Block
PSTN Public Switched Telephone Network
PHICH Physical Hybrid-ARQ Indicator Channel
PUSCH Physical Uplink Shared Channel
PUCCH Physical Uplink Control Channel
RB Resource Block
RI Rank Indicator
RNC Radio Network Controller
RRC Radio Resource Control
RRH Remote Radio Head
RRU Remote Radio Unit
RTT Round Trip Time
SAW Stop-and-Wait
SRB Signaling Radio Bearer
TDD Time Division Duplex
TFRE Time Frequency Resource Element
UCI Uplink Control Information
UE User Equipment
UL Uplink
WAN Wide Area Network
This application is a continuation of co-pending U.S. patent application Ser. No. 15/403,614 filed Jan. 11, 2017 which claims benefit of U.S. Patent Provisional Application No. 62/277,202 filed on Jan. 11, 2016, the disclosure of which is hereby incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 62277202 | Jan 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15403614 | Jan 2017 | US |
| Child | 15908007 | US |
