CN114287168A

CN114287168A - Downlink monitoring in a telecommunications system

Info

Publication number: CN114287168A
Application number: CN201980099799.5A
Authority: CN
Inventors: M·劳里德森; F·弗雷德里克森; J·凯科南; 贺敬
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2019-08-30
Filing date: 2019-08-30
Publication date: 2022-04-05
Anticipated expiration: 2039-08-30
Also published as: WO2021035732A1; CN114287168B

Abstract

Example embodiments of the present disclosure relate to apparatuses, methods, apparatuses, and computer-readable storage media for Downlink (DL) monitoring in a telecommunication system. In an example embodiment, the first device determines that data is to be transmitted via the second device towards the third device. The first device determines whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device. If it is determined that the time is to be extended, the first device transmits data and an indication to the second device to extend the time. The first device then receives a response from the third device via the second device for an extended time.

Description

Downlink monitoring in a telecommunications system

Technical Field

Example embodiments of the present disclosure relate generally to the field of communications, and in particular, to an apparatus, method, apparatus, and computer-readable storage medium for Downlink (DL) monitoring in a telecommunication system.

Background

In third generation partnership project (3GPP) standardization for New Radios (NR), power saving of User Equipment (UE) is a big problem. For example, power saving for Radio Resource Control (RRC) connected UEs is being developed. According to 3GPP specifications such as 3GPP TS 38.321, a key technology to achieve power saving is Discontinuous Reception (DRX). In DRX mode, the UE periodically monitors a Physical Downlink Control Channel (PDCCH) to detect scheduling information from the NR node B (or gNB). The DRX pattern is defined by a DRX cycle length indicating a cycle of the PDCCH monitoring occasion and a length of the PDCCH monitoring occasion called "On Duration (On S Duration)".

The DRX mode may be complemented with inactivity timers to extend PDCCH monitoring for UL or DL transmissions, as well as timers for retransmissions, such as DL retransmission timers, UL retransmission timers and contention resolution timers for random access. Accordingly, the DRX active time of the UE may include a time in the on duration, and a time when the inactivity timer, DL retransmission timer, UL retransmission timer, and/or contention resolution timer is running.

The DRX active time may be followed by a series of short DRX cycles with a period shorter than the DRX cycle length and the same on-duration. The short DRX cycle is only activated when the inactivity timer has run and expired. In DRX mode, the network side may use a power save signal (pos) to trigger whether the UE activates the on duration to reduce the power consumption of the UE. If there is no incoming downlink data, a PoSS may be sent from the network side to the UE to allow the UE to skip the next DRX activity time and extend the low power sleep state.

Furthermore, for NR, it is specified in the 3GPP specifications that PDCCH search space monitoring may be configured such that not every available PDCCH is monitored by a given UE. This configuration is provided during initial configuration of the UE. Depending on the length of the sleep state, the UE may enter a deep, shallow or micro sleep state. The reference power level and state transition energy and time have been specified in 3GPP specifications (e.g., 3GPP TR 38.840).

When the UE transmits data to the application server, if the remaining activation time is short, the response from the application server may reach the serving gNB after the UE returns to the sleep state. In this case, the response needs to be buffered in the gNB and thus delayed until the next DRX active time.

Disclosure of Invention

In general, example embodiments of the present disclosure provide devices, methods, apparatuses, and computer-readable storage media for extension of DL monitoring in a telecommunication system.

In a first aspect, a first apparatus is provided that includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the first device to determine that data is to be transmitted via the second device towards the third device. The first device is then caused to determine whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device. In response to determining that the time is to be extended, the first device is caused to transmit data and an indication to extend the time to the second device. The first device is also caused to receive a response from the third device via the second device for an extended time.

In a second aspect, a second apparatus is provided that includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to receive, from the first device, data directed to the third device and an indication to extend a time for the first device to actively monitor transmissions from the second device. The second device is then caused to forward the data to the third device. The second device is also caused to receive a response to the data from the third device and forward the response to the first device for an extended time.

In a third aspect, a method is provided. In the method, the first device determines that data is to be transmitted via the second device towards the third device. The first device determines whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device. If it is determined that the time is to be extended, the first device transmits data and an indication to the second device to extend the time. The first device then receives a response from the third device via the second device for an extended time.

In a fourth aspect, a method is provided. In the method, the second device receives, from the first device, data directed to the third device and an indication to extend a time for the first device to actively monitor transmissions from the second device. The data is then forwarded to the third device. Further, the second device receives a response to the data from the third device and forwards the response to the first device for an extended time.

In a fifth aspect, there is provided an apparatus comprising means for performing a method according to the third or fourth aspect.

In a sixth aspect, a computer-readable storage medium is provided that includes program instructions stored thereon. The instructions, when executed by a processor of an apparatus, cause the apparatus to perform the method according to the third or fourth aspect.

It should be understood that the summary is not intended to identify key or essential features of the example embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become readily apparent from the following description.

Drawings

Some example embodiments will now be described with reference to the accompanying drawings, in which:

fig. 1 illustrates a conventional example signaling flow between a UE, a gNB, and an application server;

FIG. 2 illustrates an example environment in which example embodiments of the present disclosure may be implemented;

fig. 3 shows a flow diagram of an example method according to some example embodiments of the present disclosure;

fig. 4 shows a flowchart of an example method according to some other example embodiments of the present disclosure;

fig. 5 illustrates an example signaling flow between various devices in an environment, according to some example embodiments of the present disclosure;

fig. 6 illustrates an example signaling flow between various devices in an environment according to some other example embodiments of the present disclosure; and

fig. 7 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure.

Throughout the drawings, the same or similar reference numbers refer to the same or similar elements.

Detailed Description

The principles of the present disclosure will now be described with reference to a few exemplary embodiments. It is understood that these exemplary embodiments are described merely to illustrate and assist those of ordinary skill in the art in understanding and enabling the disclosure, and do not imply any limitation on the scope of the disclosure. The disclosure described herein may be implemented in various ways other than those described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or a base station. Communication may involve the transmission and/or reception of wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for the transmission of information over the air. In some example embodiments, the UE may be configured to transmit and/or receive information without direct human-machine interaction. For example, the UE may transmit information to the base station according to a predetermined schedule, triggered by an internal or external event, or in response to a request from the network side.

Examples of UEs include, but are not limited to, smart phones, wireless enabled tablets, laptop embedded devices (LEEs), laptop installed devices (LMEs), wireless client devices (CPEs), sensors, metering devices, personal wearable devices such as watches, and/or communication enabled vehicles. For purposes of discussion, some example embodiments will be described with reference to a UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of this disclosure. The UE may also correspond to a Mobile Terminal (MT) part of an Integrated Access and Backhaul (IAB) node (also referred to as a relay node).

As used herein, the term "network device" refers to a device via which services may be provided to terminal devices in a communication network. As an example, the network device may include a base station. As used herein, the term "base station" (BS) refers to a network device via which services may be provided to terminal devices in a communication network. A base station may comprise any suitable device via which a terminal device or UE may access a communication network. Examples of base stations include relays, Access Points (APs), transmission points (TRPs), node bs (NodeB or NB), evolved NodeB (eNodeB or eNB), New Radio (NR) NodeB (gnb), remote radio modules (RRUs), Radio Heads (RH), Remote Radio Heads (RRHs), low power nodes such as femto, pico, etc. The relay node may correspond to a Distributed Unit (DU) portion of the IAB node.

As used herein, the term "application server" refers to a device that can provide any suitable application service to a terminal device or UE. By way of example, an application server may include a data sink and/or source. Examples of application servers may include, but are not limited to, computing devices, servers, blade computers, Personal Digital Assistants (PDAs), and the like. The application server may communicate with the terminal device via a network device or a transmission network.

As used herein, the term "circuitry" may refer to one or more or all of the following:

(a) a purely hardware circuit implementation (such as an implementation using only analog and/or digital circuitry), and

(b) a combination of hardware circuitry and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) and software/firmware, and (ii) a hardware processor(s) with software (including a digital signal processor), software, and any portion of memory(s) that cooperate to cause an apparatus (such as a mobile phone or server) to perform various functions, and (ii) a computer program product

(c) Hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of microprocessor(s), that require software (e.g., firmware) for operation, but software may not be present when operation is not required.

The definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also encompasses implementations of only a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. For example, the term circuitry, if applicable to a particular claim element, also encompasses a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular base station, or other computing or base station.

As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "include" and its variants should be understood as open-ended terms meaning "including, but not limited to". The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other definitions (explicit and implicit) may be included below.

As used herein, the terms "first," "second," and the like may be used herein to describe various elements, which should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.

As the name implies, DRX is downlink oriented. In case the UE in DRX mode is currently in a sleep state (i.e. outside the on-duration within the DRX cycle), if there is data in the uplink buffer of the UE, the UE may exit DRX mode and initiate a Buffer Status Reporting (BSR) procedure to acquire a scheduling grant. If a scheduling request is not available, the UE may initiate a Random Access Channel (RACH) procedure. Alternatively, the UE may delay UL data transmission until the next DRX active time. Therefore, UL data transmission is inevitably delayed.

In Long Term Evolution (LTE), some actions are specified for the UE to reduce UL transmission delay. For example, assuming that the UE performs a BSR procedure during DRX activity and then transmits UL data transmissions towards the application server, the inactivity timer will be activated to extend the active time for PDCCH monitoring.

However, long duration inactivity timers and potentially subsequent short DRX cycles are expensive in terms of power savings if rarely needed in the case of infrequent DL packets or data. Conversely, if a short duration inactivity timer is applied, a potential response from the application server may reach the serving gNB after the UE returns to sleep. In this case, the response needs to be buffered in the gNB and delayed until the next DRX active time.

Fig. 1 shows a conventional example signaling flow 100 between a UE 105, a gNB 110, and an application server 115.

In flow 100, UE 105 starts (120) DRX active time and sends (125) a new message towards application server 115. The UE then ends (130) the DRX active time. The UE is sleeping (135). The application server processes (140) the received message and sends (145) a response to the gNB 110. The gNB 110 buffers 150 the response received from the application server 115 and waits 155 for the UE 105 to wake up. After the UE starts (160) the next DRX active time, the gNB 110 forwards (165) the delayed response to the UE 105. The UE then ends (170) the current DRX active time. As shown, the response from the application server 115 is delayed until the next DRX active time.

In 3GPP narrowband internet of things (NB-IoT), the UE may send a "release assistance indication" to the network side. This indication informs the network side that the UE does not expect additional UL and DL data and therefore the UE can move from RRC connected to RRC idle. However, moving to RRC idle (or NR-enabled inactivity) when a connection is re-established for the next data transmission represents significant signaling and time overhead.

In addition, for UE power saving, the following UE assistance information is proposed:

UE prefers to process timeline parameters, such as K0, K1, K2 values,

UE preferred bandwidth part (BWP) information/configuration,

UE preferred antenna configuration including Multiple Input Multiple Output (MIMO) layers, antenna panel sensing information,

UE assistance/feedback DRX configuration/parameters,

UE-preferred BWP, provided to assist the network side for BWP handover,

UE requests secondary cell (SCell)/Secondary Cell Group (SCG) activation/deactivation/configuration,

UE preferred PDCCH monitoring parameters/search space configuration/maximum number of blind decodings,

mobility history information (e.g., similar to information via mobility state and MobilityHistoryReport in LTE),

power preference indication, preference information of UE related to connected DRX (C-DRX), BWP and SCell configuration.

As mentioned above, UE assistance/feedback on DRX configurations/parameters is considered as a recommendation from the UE side on preferred configurations/parameters for DRX operation, e.g. with a DRX cycle of 160ms, an on duration of 8ms, etc.

The inventors note that UE assistance/feedback on DRX configuration/parameters is a (semi-) static configuration estimated by the UE to be suitable for traffic profile and modem performance. Furthermore, the reconfiguration of DRX is based on RRC signaling, which is time consuming and therefore may not be performed in a dynamic manner.

The inventors have also noted that if the gNB controls when to start or restart the inactivity timer, e.g., the gNB does not know whether an uplink transmission resulting in an empty uplink buffer would result in a response from the application server filling an otherwise empty downlink buffer. Therefore, the control of the gNB cannot avoid that the response from the application server is buffered in the gNB and then delayed until the next DRX active time.

Example embodiments of the present disclosure provide a scheme for extending a monitoring time of a device. Using this scheme, if a device (e.g., a UE) is to transmit data via a further device (e.g., a gNB) towards another device (e.g., an application server), the device determines whether a transmission time for actively monitoring from the further device needs to be extended to receive a response to the data. If it is determined that the time is to be extended, the device transmits data to the further device along with an indication to extend the time. Thus, the device may receive a response over an extended time.

For discussion purposes, in some example embodiments, the UE may use this scheme to extend the time for monitoring DL transmissions from the gNB to reduce latency of communications with the application server. For example, in UL transmissions, the UE may optionally provide assistance information regarding expected or expected delays in responses from the application server (and transport network) to indicate the extension of time. As an example, the UE may send an "i expect downlink response" flag as an indication during DRX active time for PDCCH monitoring.

Thus, the UE may change internal operations to accommodate the assistance information so that the UE will be available for scheduling at the expected arrival time of the response from the application server. For example, the UE may monitor the PDCCH for additional durations. Alternatively or additionally, the UE may extend the inactivity timer to an extended duration. As another example, the UE may perform PDCCH monitoring within an additional window, which means that the UE may temporarily stop PDCCH monitoring until an expected response from the application.

A shorter inactivity timer may be applied because the UE may extend the duration of the inactivity timer and/or PDCCH monitoring when needed. This may reduce power consumption for PDCCH monitoring during the on-duration, since the UE is scheduled only once or several times. The UE may be allowed to extend the duration of the inactivity timer and/or PDCCH monitoring until a response is received in the DL to reduce the communication delay and buffer memory required in the gNB to store the DL response until the next DRX activity time.

Furthermore, if a power save signal (pos) is applied, a UE extending the duration of the inactivity timer and/or PDCCH monitoring may be able to skip the subsequent on duration completely because a DL response of the application layer has been received. In contrast to the conventional (semi-) static UE assistance information regarding preferred DRX configurations as described above, the scheme according to the exemplary embodiments of the present disclosure may achieve an optimal DRX configuration from a system perspective. Further, the UE may dynamically adjust the duration of PDCCH monitoring to achieve lower delay.

FIG. 2 illustrates an example environment 200 in which example embodiments of the present disclosure may be implemented.

The environment 200, which may be part of a communication network, includes

devices

210 and 220 in communication with each other, the

devices

210 and 220 being referred to as a first device 210 and a second device 220, respectively. The first device 210 and the second device 220 may be implemented by any suitable device in a communication network. For example, the first device 210 may be implemented by a terminal device such as a UE, and the second device 220 may be implemented by a network device such as a base station. As another example, both the first device 210 and the second device 220 may be implemented by terminal devices. For discussion purposes only, in some example embodiments, a terminal device will be taken as an example of the first device 210 and a network device will be taken as an example of the second device 220.

As shown in FIG. 2, environment 200 also includes an additional device 230, referred to as a third device 230. The third device 230 may be any suitable device that may communicate with the second device 420 either directly in a cable or indirectly through other network entities or a transmission network. In some example embodiments, third device 230 may be implemented by a server, such as an application server. The first device 110 may communicate with the third device 230 via the second device 220. It should be understood that the three devices shown in environment 200 are for illustration purposes only and do not represent any limitation on the scope of the present disclosure. Any suitable number or type of devices may be included in environment 200.

The communications in environment 200 may conform to any suitable communication standard or protocol that already exists or will be developed in the future, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-advanced (LTE-a), fifth generation (5G) New Radio (NR), wireless fidelity (Wi-Fi), and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employs any suitable communication techniques including, for example, multiple-input multiple-output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), bluetooth, ZigBee, and Machine Type Communication (MTC), enhanced mobile broadband (eMBB), mass Machine Type Communication (MTC), ultra-reliable low latency communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC), and new radio unlicensed (NR-U) techniques.

In various example embodiments, the first device 210 may transmit data via the second device 220 towards the third device 230. If the first device 210 determines that its time for actively monitoring transmissions from the second device 220 (e.g., DRX active time) is to be extended to receive a response to the data from the third device 230, the first device 210 will transmit the data to the second device 220 along with an indication to extend the time. Further, the first device 210 receives a response from the third device 230 via the second device 220 for an extended time. In this way, the communication delay between the first device 210 and the third device 230 may be reduced.

Fig. 3 illustrates a flow diagram of an example method 300 in accordance with some example embodiments of the present disclosure. The method 300 may be implemented by the first device 210 shown in fig. 2. For purposes of discussion, the method 300 will be described with reference to fig. 2.

At block 305, the first device 210 determines that data is to be transmitted via the second device 220 towards the third device 230. The data may include user plane data and/or control plane data and may be transmitted at any suitable layer. For example, the data may comprise application layer data and may therefore be transported at the non-access stratum (NAS) layer or other higher layers.

At block 310, the first device 210 determines whether the time to actively monitor for transmissions from the second device 220 is to be extended to receive a response to the data from the third device 230. In some example embodiments, this time may be used for DRX. As an example, the time may include a DRX active time including an on duration, a duration of an inactivity timer, or any other duration that the first device 210 is actively monitoring transmissions from the second device 220.

The determination of whether to extend the time may be implemented by the first device 210 based on any suitable criteria. In some example embodiments, this determination may be implemented based on an estimated time of arrival (TOA) of the response from the third device 230. The TOA of the response may be estimated or predicted by the first device 210 based on historical statistics regarding responses previously received from the third device 230 or other devices. Other estimation or prediction methods are also possible, and the scope of the present disclosure is not to be limited in this respect.

As an example, the first device 210 may determine to extend the time if the TOA of the estimated response is later than the end of the time. Furthermore, if the required extension time is too long, e.g. almost as long as the DRX cycle, it is preferable not to extend the time but to postpone the reception until the next DRX active time. Accordingly, the first device 210 may enter a sleep state to further reduce power consumption. Thus, in some example embodiments, the extension of time may be further decided by the first device 210 based on a predetermined time. The predetermined time may be set on the network side or by the first device 210 by considering a trade-off between communication delay and power consumption. For example, when the estimated TOA is determined to be later than the end of the time, the first device 210 determines whether the estimated TOA is within a predetermined time. The time may be extended if the estimated TOA is within a predetermined time. Otherwise, the first device 210 may wait for the next monitoring opportunity without extending the time of the current monitoring opportunity.

In some cases, a determination of whether to extend the time may be triggered. For example, the first device 210 may trigger the determination if a quality of service (QoS) requirement of the data is above a threshold requirement, which indicates that the data has a higher delay requirement. The QoS requirements may be reflected by the QoS flow and/or the data radio bearer to be used for the transmission of the data.

Alternatively or additionally, the determination may be triggered based on historical statistics regarding delays of previous responses from the third device 230. For example, if a greater number (above a threshold number) of previous responses from the third device 230 are delayed, the first device 210 may initiate a determination of whether to extend the current time to receive a response to the current data. The threshold number may depend on the network or terminal implementation.

When it is determined that the time is to be extended, the first device 210 transmits data and an indication to extend the time to the second device 220 at block 315. The indication may indicate the extension of time in any suitable manner. In some example embodiments, the indication may indicate an extended duration of monitoring. For example, the indication may be used by the first device 210 to indicate to the second device 220 that DL transmissions are to be monitored for an additional duration X. X represents any suitable duration.

In addition to the existing value of the extended duration of time, the indication may also indicate an additional window in which the first device 210 is to specifically monitor for transmissions from the second device 220. For example, x1 may indicate the beginning of a window and y1 may indicate the end of a window, where x1 and y1 represent any suitable positive numbers. The use of the window may allow the first device 210 to potentially temporarily stop monitoring until the expected response from the third device 230, so that power consumption may be further reduced. The values of x1 and y1 may be statically predefined or semi-statically or dynamically configured in the network. These values may also be set by the first device 210.

Alternatively or additionally, the indication may be used to indicate an extended duration of the inactivity timer of the first device 210. For example, the indication may indicate that the duration of the inactivity timer is to be extended to Y. Y represents any suitable duration.

The values of X and Y may be statically predefined in the network. For example, the values of X and/or Y may be specified in the relevant 3GPP specifications. Based on the specification, the first device 210 may know the value. As another example, the values of X and/or Y may be semi-statically or dynamically configured or indicated from the network side. Thus, the first device 210 may receive a configuration or indication of the value from the network side, e.g. via the second device 220 acting as a network device. Alternatively or additionally, the values of X and/or Y may be determined by the first device 210. For example, the first device 210 may determine the value based on historical statistics regarding delay times of responses from the third device 230.

In some example embodiments, the extension of the time may be pre-negotiated and agreed upon between the first device 210 and the network side via the second device 220. For example, the first device 210 may send a request to the second device 220 for an extension of the time. In some example embodiments, the request may indicate a set of one or more extension times desired by the first device 210. In response, the first device 210 may receive an indication of an extended time from the second device 220. In the case where the request sent by the first device 210 indicates a desired set of extended times, the extended time indicated by the indication may be determined from the desired set of extended times. For example, the extension time may be selected by the second device 220 from a set of desired extension times. The second device 220 may also determine the time extension of the time from a set of desired time extensions based on some other criteria.

In some example embodiments, the indication may indicate a number of inactivity timers to be used for the first device 210. Alternatively or additionally, the indication may indicate a single additional duration of the inactivity timer. In this case, after the inactivity timer expires, the first device 210 may resend the indication to the second device 220 to extend the active device so that the active time may be extended continuously.

In some example embodiments, the indication may indicate continuous use of an inactivity timer previously used for the first device 210. For example, after expiration of the inactivity timer, the first device 210 may send an indication to indicate that the previously-instance inactivity timer was continuously applied to extend the time for actively monitoring transmissions from the second device 220.

In some example embodiments, the first device 210 may monitor using a short period. As an example, the short cycle may follow a pre-configured short DRX pattern for DRX. In these embodiments, the indication may indicate a number of short cycles and/or a number of short cycle timers to be used for the first device 210. Thus, the first device 210 may monitor for transmissions from the second device 220, such as PDCCH or PDCCH, based on a short period with an extended duration. The short cycle can be selectively extended by the number of cycles or the number of timers, which is more flexible and efficient.

The indication may be implemented in any suitable form. For example, in an example embodiment where the indication indicates a value of X or Y, the indication may be interpreted as a different value depending on the number of available bits for the indication. For example, the indication may be scaled to 1, 2, 3ms using a cardinality of 1, 10, or 100; 10. 20, 30 ms; or 100, 200, 300 ms. Alternatively or additionally, the indication indicates an accurate value of X or Y, such as 12, 37, 92 ms. It should be appreciated that the values of X and Y may take other forms to indicate the time desired to be delayed. The time units may also include slots, symbols, or other well-defined time units that may help to obtain a contracted time between various devices. In some example embodiments, if the extension of time has been predefined, the first device 210 only needs a single bit to indicate whether the extension is applied.

The indication and data may be sent by the first device 210 separately or integrally. In some example embodiments, the indication may be transmitted after or before the data is transmitted. For example, data may be first transmitted by the first device 210 to the second device 220, for example in a NAS message. Then, an indication for the extended time is sent by the first device 210 to the second device 220 in a MAC Control Element (CE) on the MAC layer or in uplink control information on the Physical (PHY) layer or in a message on the RRC layer.

In some example embodiments, the data and the indication may be encapsulated in the same message. For example, the data and the indication may be encapsulated in and transmitted in an RRC message. The use of RRC layer messages may avoid additional inter-layer communication between higher layers, such as the NAS layer, and lower layers, such as the MAC and PHY layers. Thus, the transmission efficiency can be further improved, and the communication delay can be further reduced.

As an example, in an example embodiment where the first device 210 is implemented by a UE, the second device 220 is implemented by a gNB, and the third device 230 is implemented by an application server, the RRC ULInformationTransfer message for UL transmission of NAS or non-3 GPP-specific information towards the application server may be reused for integrally transmitting data and indications. The ULInformationTransfer message may be changed to enable integration as follows:

ULInformationTransfer message

Where the Information Element (IE) "expectdownlinlinresponsein" indicates that a DL response is expected and the parameters Xms and Yms indicate the extended duration of the DL monitoring and inactivity timers, respectively. Reuse of the ULInformationTransfer message is a straightforward way to ensure that the RRC layer of the UE gets the "i expect downlink response" flag from the NAS layer of the UE as an indication to extend the monitoring time and carries this indication to the gNB via a message, which is more efficient and effective.

After the data and indication are transmitted, the first device 210 receives a response from the third device 230 via the second device 220 for an extended time at block 320. For example, in an example embodiment in which DL monitoring is extended by Xms, the first device 210 may actively monitor DL transmissions for an additional duration of Xms. In an example embodiment where the duration of the inactivity timer is extended to Yms, the first device 210 may monitor for DL transmissions based on the extended duration of the inactivity timer Yms. In example embodiments in which additional windows are used, the first device 210 may specifically monitor DL transmissions within the additional windows, e.g., starting x1 ms and ending after y1 ms after the last layer 1 (L1) or layer 2 (L2) UL transmission.

Fig. 4 illustrates a flow diagram of an example method 400 in accordance with some example embodiments of the present disclosure. The method 400 may be implemented by the second device 220 shown in fig. 2. For discussion purposes, the method 400 will be described with reference to fig. 2.

At block 405, the second device 220 receives from the first device 210 data directed to the third device 230 and an indication to extend the time for the first device 210 to actively monitor transmissions from the second device 220. At block 410, the second device 220 forwards the data to the third device 230. At block 415, the second device 220 receives a response to the data from the third device 230. At block 420, the second device 220 forwards the response to the first device 210 for an extended time.

The data and the indication may be received separately or integrally. In some example embodiments, the indication may be received after or before the receipt of the data. The data may be received in a NAS message and the indication may be received in a MAC CE, uplink control information on PHY layer, or RRC message. In some example embodiments, the data and the indication may be integrated in one message, such as an RRC ULInformationTransfer message.

The indication may indicate the extension of time in any suitable manner. For example, the indication may simply indicate whether or not to apply the extension. Alternatively or additionally, the indication may indicate an additional window of extended duration and/or monitoring. As another example, the indication may indicate an extended duration of the inactivity timer and/or a number of inactivity timers to be used for the first device 210.

The extended time of monitoring may be predefined in the network or dynamically or semi-statically configured by the second device 220. In some example embodiments, the extension time may be determined by a negotiation between the first device 210 and the second device 220. For example, prior to receiving the data and indication from the first device 210, the second device 220 may receive a request from the first device 210 for an extended time for the first device 210 to actively monitor transmissions from the second device. In some example embodiments, the request may indicate a set of extended times desired by the first device 210. The second device 220 may then determine an extension time based on the request. For example, if the request indicates a desired set of extension times, the second device 220 may select an extension time from the desired set of extension times. The second device 220 may use other rules or consider other factors to determine the extension time. The second device 220 further sends an indication of the extended time to the first device 210.

All operations and features in the method 300 at the first device 210 as described above with reference to fig. 2 and 3 are equally applicable to the method 400 at the second device 220 and have similar effects. Details will be omitted for simplicity.

Fig. 5 illustrates an example signaling flow 500 between various devices in the environment 200, according to some example embodiments of the present disclosure. In this example, the first device 210 is implemented by a UE, the second device 220 is implemented by a gNB, and the third device 230 is implemented by an application server. This time is used for DRX, e.g., corresponding to DRX active time.

In flow 500, the first device 210 starts 505 the DRX active time and sends 510 a new message containing data towards the third device 230 via the second device 220. In this example, the first device 210 may be instructed or configured to inform the network side whether the first device 210 desires additional information to arrive in the DL as part of the C-DRX configuration. The first device 210 may also be configured to transmit the indication to extend DRX active time only when a response to the transmitted message is expected to arrive within a certain time to achieve a tradeoff between communication delay and power consumption. Alternatively or additionally, the first device 210 may be configured to send the indication if the delay requirement or other quality of service parameter of the data meets certain criteria. Accordingly, the configuration may only be applicable for certain quality of service flows and/or certain data radio bearers.

As shown in fig. 5, the first device 210 sends (515) an "i expect downlink response" flag to the second device 220 as an indication to extend DRX active time. The first device 210 and the second device 220 extend (520) the duration of the inactivity timer and/or PDCCH monitoring for DRX activity time. The third device 230 processes (525) the message. The first device 210 then receives (530) a response to the message from the third device 230 via the second device 220. The first device 210 ends 535 the DRX active time.

Fig. 6 illustrates an example signaling flow 600 between various devices in the environment 200, according to some other example embodiments of the present disclosure. Similar to the flow 500 shown in fig. 5, in this example, the first device 210 is implemented by a UE, the second device 220 is implemented by a gNB, and the third device 230 is implemented by an application server. Further, this time is used for DRX, e.g. corresponding to DRX active time.

In flow 600, DRX is configured (605) for the first device 210 by the second device 220. The first device 210 sends (610) a new message to the third device 230 via the second device 220 and receives (615) a delayed response from the third device 230 via the second device 220. Then, time elapses (620). The first device 210 further sends 625 a new message towards the third device 230 via the second device 220 and receives 630 a delayed response from the third device 230 via the second device 220. Since the two responses from the third device 230 are delayed, the first device 210 identifies (635) a need for PDCCH monitoring adjustments.

The first device 210 suggests (640) an extended duration Xms or Yms for the time to the second device 220. Such feedback by the first device 210 may be for each traffic flow to accommodate communications with different application servers having different response times. Then, if configured, the second device 210 sets 645 an extension duration Yms. The extended duration of inactivity timer or PDCCH monitoring may take the form of a simple extension of an existing value. Alternatively or additionally, the extended duration may take the form of a window. By using this window, the first device 210 may potentially temporarily stop PDCCH monitoring until the earliest expected response from the third device 230, which may further reduce power consumption.

The first device 210 sends 650 a new message and further sends 655 an "i expect downlink response" flag as an indication to extend DRX active time. If the required extension time is long, e.g. almost as long as the DRX cycle, it is beneficial that the first device 210 does not send a flag but defers reception until the next on duration. The exact tradeoff between application layer delay and UE power consumption is UE specific and therefore the choice of whether or not to send a flag is left to the UE implementation.

The first device 210 and the second device 220 extend (660) a duration of inactivity timer and/or PDCCH monitoring for DRX activity time. The first device 210 receives (665), via the second device 220, a response to the message from the third device 230.

The extension of the time of the first device 210 may result in significant savings in the power consumption of the first device 210. Table 1 shows an estimated energy consumption using conventional DRX and a scheme for extending DRX active time according to an example embodiment of the present disclosure.

TABLE 1

In the estimation procedure, the first device 210 is implemented by the UE and uses an 80ms DRX cycle in combination with an 8ms on duration and a 5ms inactivity timer in regular DRX. Further, assume that the UE occasionally initiates UL communication with the third device 230 that responds after 20 ms. The energy consumption and delay of the conventional DRX and the proposed scheme can be calculated. For the proposed scheme, it is assumed that the UE applies an extended duration of 15ms for the inactivity timer, i.e. the inactivity timer is started 8+15 ═ 23 ms.

As shown in table 1, if regular DRX has a transmission in one cycle and a DL response in the next cycle, the proposed scheme has a transmission and a DL response in the first cycle, followed by a "null" DRX cycle where the UE monitors only the PDCCH. Therefore, 2 DRX cycles are considered in both the conventional DRX and the proposed scheme for fair comparison. When no pos is used, the proposed scheme increases the energy consumption by 15%, while still reducing the round trip time from 80ms (i.e. DRX cycle) to 20ms (actual server response time). If PoSS is applied, the "empty" DRX cycle can be omitted and energy is saved by about 10%. If the data transmission is sporadic, e.g., the data transmission occurs only once in 10 DRX cycles, the power savings is-4% and 5% without and with the pos, respectively.

Fig. 7 is a simplified block diagram of a device 700 suitable for implementing an example embodiment of the present disclosure. The device 700 may be implemented at or as part of the first device 210 or the second device 220 shown in fig. 2.

As shown, device 700 includes a processor 710, a memory 720 coupled to processor 710, a communication module 730 coupled to processor 710, and a communication interface (not shown) coupled to communication module 730. The memory 720 stores at least a program 740. The communication module 730 is used for bi-directional communication, e.g., via multiple antennas. The communication interface may represent any interface required for communication.

The programs 740 are assumed to include program instructions that, when executed by the associated processor 710, enable the device 700 to operate in accordance with example embodiments of the present disclosure, as discussed herein with reference to fig. 2-6. The example embodiments herein may be implemented by computer software executable by the processor 710 of the device 700, or by hardware, or by a combination of software and hardware. The processor 710 may be configured to implement various example embodiments of the present disclosure.

The memory 720 may be of any type suitable to the local technology network and may be implemented using any suitable data storage technology, such as non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. Although only one memory 720 is shown in device 700, there may be several physically distinct memory modules in device 700. The processor 710 may be of any type suitable for a local technology network, and may include, by way of non-limiting example, one or more of the following: general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs) and processors based on a multi-core processor architecture. Device 700 may have multiple processors, such as an application specific integrated circuit chip that is time dependent from a clock synchronized to the main processor.

When the device 700 is acting as the first device 210 or part of the first device 210, the processor 710 and the communication module 730 may cooperate to implement the method 300 as described above with reference to fig. 2, 3, 5, and 6. When device 700 is acting as second device 220 or part of second device 220, processor 710 and communication module 730 may cooperate to implement method 400 as described above with reference to fig. 2, 4, 5, and 6. All of the operations and features described above with reference to fig. 2-6 are equally applicable to the device 700 and have similar effects. Details will be omitted for simplicity.

In general, the various example embodiments of this disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the example embodiments of this disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product comprises computer executable instructions, such as instructions included in program modules, that are executed in a device on a target real or virtual processor to perform the

methods

300 and 400 and the

flows

500 and 600 as described above with reference to fig. 2-6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various example embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions of program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote memory storage media.

Program code for performing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are described in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Also, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular example embodiments. Certain features that are described in the context of separate example embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple example embodiments separately or in any suitable subcombination.

Although the disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Various example embodiments of these techniques have been described. In addition to or in lieu of the foregoing, the following embodiments are described. Features described in any of the examples below may be used with any of the other examples described herein.

In some aspects, a first device comprises: at least one processor; at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the first apparatus to: determining that data is to be transmitted via the second device towards the third device; determining whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device; in response to determining that the time is to be extended, transmitting data and an indication to extend the time to the second device; and receiving a response from the third device via the second device for the extended time.

In some example embodiments, the first device is caused to determine whether the time is to be extended by: determining whether the estimated arrival time of the response is later than the end of time; and determining that the time is to be extended in response to determining that the estimated time of arrival of the response is later than the end of the time.

In some example embodiments, the first device is caused to determine that the time is to be extended by: in response to determining that the estimated time of arrival of the response is later than the end of the time, determining whether the estimated time of arrival of the response is within a predetermined time; and in response to determining that the estimated time of arrival of the response is within the predetermined time, determining that the time is to be extended.

In some example embodiments, the first device is caused to determine whether the time is to be extended by: determining whether the time is to be extended when at least one of: the quality of service requirement for the data is above a threshold requirement and the number of previous delayed responses from the third device is above a threshold number.

In some example embodiments, the first device is caused to transmit the data and the indication by: after or before transmitting the data to the second device, sending an indication to the second device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, or a message on a radio resource control layer.

In some example embodiments, the first device is caused to transmit the data and the indication by: the data and the indication are transmitted to the second device in a message on a radio resource control layer.

In some example embodiments, the indication indicates at least one of an extended duration of monitoring or an additional window.

In some example embodiments, the indication indicates at least one of: an extended duration of an inactivity timer for the first device, a number of inactivity timers to be used for the first device, or a continuous use of an inactivity timer previously used for the first device.

In some example embodiments, the indication indicates at least one of: a number of short cycles to be used for the first device, or a number of short cycle timers to be used for the first device.

In some example embodiments, the indication indicates an extended duration of the inactivity timer for the first device, and the first device is further caused to: in response to expiration of the inactivity timer, resending the indication for the extended time to the second device.

In some example embodiments, the first device is further caused to: sending a request to a second device for an extended time to actively monitor transmissions from the second device; and receiving an indication of an extended time from the second device.

In some example embodiments, the request for the extended time indicates a set of extended times expected by the first device to actively monitor transmissions from the second device, and the received indication of the extended time indicates an extended time determined by the second device from the desired set of extended times.

In some example embodiments, the first device comprises a terminal device and the second device comprises a network device.

In some example embodiments, time is used for discontinuous reception.

In some aspects, a second device comprises: at least one processor; at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the second apparatus to: receiving, from the first device, data directed to the third device and an indication to extend a time for the first device to actively monitor transmissions from the second device; forwarding the data to a third device; receiving a response to the data from the third device; and forwarding the response to the first device for the extended time.

In some example embodiments, the second device is caused to receive the data and the indication by: after or before receiving the data from the first device, an indication is received from the first device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, and a message on a radio resource control layer.

In some example embodiments, the second device is caused to receive the data and the indication to comprise: the data and the indication are received from the first device in a message on a radio resource control layer.

In some example embodiments, the second device is further caused to: receiving, from a first device, a request for an extended time for the first device to actively monitor transmissions from a second device; determining an extension time based on the request; and sending an indication of the extended time to the first device.

In some example embodiments, the request for the extended time indicates a set of extended times expected by the first device to actively monitor transmissions from the second device, and the second device determines the extended time based on the request by: an extension time is determined from a set of desired extension times.

In some example embodiments, time is used for discontinuous reception.

In some aspects, a method implemented at a first device includes: determining that data is to be transmitted via the second device towards the third device; determining whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device; in response to determining that the time is to be extended, transmitting data and an indication to extend the time to the second device; and receiving a response from the third device via the second device for the extended time.

In some example embodiments, determining whether the time is to be extended comprises: determining whether the estimated arrival time of the response is later than the end of time; and determining that the time is to be extended in response to determining that the estimated time of arrival of the response is later than the end of the time.

In some example embodiments, determining that the time is to be extended comprises: in response to determining that the estimated time of arrival of the response is later than the end of the time, determining whether the estimated time of arrival of the response is within a predetermined time; and in response to determining that the estimated time of arrival of the response is within the predetermined time, determining that the time is to be extended.

In some example embodiments, determining whether the time is to be extended comprises: determining whether the time is to be extended when at least one of: the quality of service requirement for the data is above a threshold requirement and the number of previous delayed responses from the third device is above a threshold number.

In some example embodiments, transmitting the data and the indication comprises: after or before transmitting the data to the second device, sending an indication to the second device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, or a message on a radio resource control layer.

In some example embodiments, transmitting the data and the indication comprises: the data and the indication are transmitted to the second device in a message on a radio resource control layer.

In some example embodiments, the indication indicates an extended duration of an inactivity timer for the first device, and the method further comprises: in response to expiration of the inactivity timer, resending the indication for the extended time to the second device.

In some example embodiments, the method further comprises: sending a request to a second device for an extended time to actively monitor transmissions from the second device; and receiving an indication of an extended time from the second device.

In some example embodiments, time is used for discontinuous reception.

In some aspects, a method implemented at a second device includes: receiving, from the first device, data directed to the third device and an indication to extend a time for the first device to actively monitor transmissions from the second device; forwarding the data to a third device; receiving a response to the data from the third device; and forwarding the response to the first device for the extended time.

In some example embodiments, receiving the data and the indication comprises: after or before receiving the data from the first device, an indication is received from the first device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, and a message on a radio resource control layer.

In some example embodiments, receiving the data and the indication comprises: the data and the indication are received from the first device in a message on a radio resource control layer.

In some example embodiments, the method further comprises: receiving, from a first device, a request for an extended time for the first device to actively monitor transmissions from a second device; determining an extension time based on the request; and sending an indication of the extended time to the first device.

In some example embodiments, the request for the extension time indicates a set of extension times expected by the first device to actively monitor transmissions from the second device, and determining the extension time based on the request comprises: an extension time is determined from a set of desired extension times.

In some example embodiments, time is used for discontinuous reception.

In some aspects, an apparatus comprises: means for determining that data is to be transmitted via the second device towards the third device; means for determining whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device; means for transmitting data and an indication to extend the time to the second device in response to determining that the time is to be extended; and means for receiving a response from the third device via the second device for an extended time.

In some example embodiments, the means for determining whether the time is to be extended comprises: means for determining whether the estimated arrival time of the response is later than the end of time; and means for determining that the time is to be extended in response to determining that the estimated time of arrival of the response is later than the end of the time.

In some example embodiments, the means for determining that the time is to be extended comprises: means for determining whether the estimated time of arrival of the response is within a predetermined time in response to determining that the estimated time of arrival of the response is later than the end of time; and means for determining that the time is to be extended in response to determining that the estimated time of arrival of the response is within the predetermined time.

In some example embodiments, the means for determining whether the time is to be extended comprises: means for determining whether time is to be extended when at least one of: the quality of service requirement for the data is above a threshold requirement and the number of previous delayed responses from the third device is above a threshold number.

In some example embodiments, the means for transmitting data and instructions comprises: means for sending an indication to the second device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, or a message on a radio resource control layer after or before transmitting data to the second device.

In some example embodiments, the means for transmitting data and instructions comprises: means for transmitting the data and the indication to the second device in a message on a radio resource control layer.

In some example embodiments, the indication indicates an extended duration of an inactivity timer for the first device, and the apparatus further comprises: means for retransmitting the indication for the extended time to the second device in response to the inactivity timer expiring.

In some example embodiments, the apparatus further comprises: means for sending a request to a second device for an extended time to actively monitor transmissions from the second device; and means for receiving an indication of the extended time from the second device.

In some aspects, an apparatus comprises: means for receiving, from the first device, data directed to the third device and an indication to extend a time for the first device to actively monitor transmissions from the second device; means for forwarding the data to a third device; means for receiving a response to the data from the third device; and means for forwarding the response to the first device for an extended time.

In some example embodiments, the means for receiving data and indications comprises: means for receiving an indication from the first device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, and a message on a radio resource control layer after or before receiving data from the first device.

In some example embodiments, the means for receiving data and indications comprises: means for receiving data and an indication from a first device in a message on a radio resource control layer.

In some example embodiments, the apparatus further comprises: means for receiving, from a first device, a request for an extended time for the first device to actively monitor transmissions from a second device; means for determining an extended time based on the request; and means for sending an indication of the extended time to the first device.

In some example embodiments, the request for the extended time indicates a set of extended times expected by the first device to actively monitor transmissions from the second device, and the means for determining the extended time based on the request comprises: means for determining an extension time from a set of desired extension times.

In some example embodiments, time is used for discontinuous reception.

In some aspects, a computer-readable storage medium includes program instructions stored thereon that, when executed by a processor of a device, cause the device to perform a method according to some example embodiments of the present disclosure.

Claims

1. A first device, comprising:

at least one processor; and

at least one memory including computer program code;

the at least one memory and the computer program code configured to, with the at least one processor, cause the first apparatus to:

determining that data is to be transmitted via the second device towards the third device;

determining whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device;

in response to determining that the time is to be extended, transmitting the data and an indication to extend the time to the second device; and

receiving the response from the third apparatus via the second apparatus for the extended time.

2. The first device of claim 1, wherein the first device is caused to determine whether the time is to be extended by:

determining whether the estimated time of arrival of the response is later than the end of the time; and

determining that the time is to be extended in response to determining that the estimated time of arrival of the response is later than the end of the time.

3. The first device of claim 2, wherein the first device is caused to determine that the time is to be extended by:

in response to determining that the estimated time of arrival of the response is later than the end of the time, determining whether the estimated time of arrival of the response is within a predetermined time; and

determining that the time is to be extended in response to determining that the estimated time of arrival of the response is within the predetermined time.

4. The first device of claim 1, wherein the first device is caused to determine whether the time is to be extended by:

determining whether the time is to be extended when at least one of:

a quality of service requirement for the data is above a threshold requirement, an

The number of previous delayed responses from the third device is above a threshold number.

5. The first device of claim 1, wherein the first device is caused to transmit the data and the indication by:

transmitting the indication to the second device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, or a message on a radio resource control layer after or before transmitting the data to the second device.

6. The first device of claim 1, wherein the first device is caused to transmit the data and the indication by:

transmitting the data and the indication to the second device in a message on a radio resource control layer.

7. The first device of claim 1, wherein the indication indicates at least one of an extended duration of the monitoring or an additional window.

8. The first device of claim 1, wherein the indication indicates at least one of:

an extended duration of an inactivity timer for the first device,

a number of inactivity timers to be used for the first device, or

Continuous use of an inactivity timer previously used for the first device.

9. The first device of claim 1, wherein the indication indicates at least one of:

a number of short periods to be used for the first device, or

A number of short period timers to be used for the first device.

10. The first device of claim 1, wherein the indication indicates an extended duration of an inactivity timer for the first device, and the first device is further caused to:

re-sending the indication to the second device to extend the time in response to the inactivity timer expiring.

11. The first device of claim 1, wherein the first device is further caused to:

sending a request to the second device for an extended time to actively monitor the transmission from the second device; and

receiving an indication of the extended time from the second device.

12. The first device of claim 11, wherein the request for the extended time indicates a set of extended times desired by the first device for actively monitoring the transmission from the second device, and the received indication of the extended time indicates an extended time determined by the second device from the set of extended times desired.

13. The first device of claim 1, wherein the first device comprises a terminal device and the second device comprises a network device.

14. The first device of claim 1, wherein the time is used for discontinuous reception.

15. A second device, comprising:

at least one processor; and

at least one memory including computer program code;

the at least one memory and the computer program code configured to, with the at least one processor, cause the second apparatus to:

receiving, from a first device, data directed to a third device and an indication to extend a time for the first device to actively monitor transmissions from the second device;

forwarding the data to the third device;

receiving a response to the data from the third device; and

forwarding the response to the first device for the extended time.

16. The second device of claim 15, wherein the second device is caused to receive the data and the indication by:

receiving the indication from the first device in at least one of a medium access medium control element on a medium access medium layer, uplink control information on a physical layer, and a message on a radio resource control layer after or before receiving the data from the first device.

17. The second device of claim 15, wherein the second device caused to receive the data and the indication comprises:

receiving the data and the indication from the first device in a message on a radio resource control layer.

18. The second device of claim 15, wherein the indication indicates at least one of an extended duration of the monitoring or an additional window.

19. The second device of claim 15, wherein the indication indicates at least one of:

an extended duration of an inactivity timer for the first device,

a number of inactivity timers to be used for the first device, or

Continuous use of an inactivity timer previously used for the first device.

20. The second device of claim 15, wherein the indication indicates at least one of:

a number of short periods to be used for the first device, or

A number of short period timers to be used for the first device.

21. The second device of claim 15, wherein the second device is further caused to:

receiving, from the first device, a request for an extended time for the first device to actively monitor the transmission from the second device;

determining the extended time based on the request; and

transmitting an indication of the extended time to the first device.

22. The second device of claim 21, wherein the request for the extended time indicates a set of extended times that the first device desires for actively monitoring the transmission from the second device, and the second device determines the extended time based on the request by:

determining the extension time from the set of extension times desired.

23. The second device of claim 15, wherein the first device comprises a terminal device and the second device comprises a network device.

24. The second device of claim 15, wherein the time is used for discontinuous reception.

25. A method implemented at a first device, comprising:

26. The method of claim 25, wherein determining whether the time is to be extended comprises:

27. The method of claim 26, wherein determining that the time is to be extended comprises:

28. The method of claim 25, wherein determining whether the time is to be extended comprises:

determining whether the time is to be extended when at least one of:

29. The method of claim 25, wherein transmitting the data and the indication comprises:

30. The method of claim 25, wherein transmitting the data and the indication comprises:

31. The method of claim 25, wherein the indication indicates at least one of an extended duration of the monitoring or an additional window.

32. The method of claim 25, wherein the indication indicates at least one of:

an extended duration of an inactivity timer for the first device,

a number of inactivity timers to be used for the first device, or

Continuous use of an inactivity timer previously used for the first device.

33. The method of claim 25, wherein the indication indicates at least one of:

a number of short periods to be used for the first device, or

A number of short period timers to be used for the first device.

34. The method of claim 25, wherein the indication indicates an extended duration of an inactivity timer for the first device, and further comprising:

35. The method of claim 25, further comprising:

receiving an indication of the extended time from the second device.

36. The method of claim 35, wherein the request for the extended time indicates a set of extended times desired by the first device for actively monitoring the transmission from the second device, and the received indication of the extended time indicates an extended time determined by the second device from the set of extended times desired.

37. The method of claim 25, wherein the first device comprises a terminal device and the second device comprises a network device.

38. The method of claim 25, wherein the time is used for discontinuous reception.

39. A method implemented at a second device, comprising:

forwarding the data to the third device;

receiving a response to the data from the third device; and

forwarding the response to the first device for the extended time.

40. The method of claim 39, wherein receiving the data and the indication comprises:

41. The method of claim 39, wherein receiving the data and the indication comprises:

42. The method of claim 39, wherein the indication indicates at least one of an extended duration of the monitoring or an additional window.

43. The method of claim 39, wherein the indication indicates at least one of:

an extended duration of an inactivity timer for the first device,

a number of inactivity timers to be used for the first device, or

Continuous use of an inactivity timer previously used for the first device.

44. The method of claim 39, wherein the indication indicates at least one of:

a number of short periods to be used for the first device, or

A number of short period timers to be used for the first device.

45. The method of claim 39, further comprising:

determining the extended time based on the request; and

transmitting an indication of the extended time to the first device.

46. The method of claim 45, wherein the request for the extended time indicates a set of extended times desired by the first device for actively monitoring the transmission from the second device, and determining the extended time based on the request comprises:

determining the extension time from the set of extension times desired.

47. The method of claim 39, wherein the first device comprises a terminal device and the second device comprises a network device.

48. The method of claim 39, wherein the time is used for discontinuous reception.

49. An apparatus, comprising:

means for determining that data is to be transmitted via the second device towards the third device;

means for determining whether a time for actively monitoring transmissions from the second device is to be extended to receive a response to the data from the third device via the second device;

means for transmitting, to the second device, the data and an indication to extend the time in response to determining that the time is to be extended; and

means for receiving the response from the third device via the second device for an extended time.

50. An apparatus, comprising:

means for receiving, from a first device, data directed to a third device and an indication to extend a time for the first device to actively monitor transmissions from the second device;

means for forwarding the data to the third device;

means for receiving a response to the data from the third device; and

means for forwarding the response to the first device for an extended time.

51. A computer readable storage medium comprising program instructions stored thereon which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any of claims 25 to 38.

52. A computer readable storage medium comprising program instructions stored thereon that, when executed by a processor of an apparatus, cause the apparatus to perform the method of any of claims 39 to 48.