Extension of a discontinuous reception active time

An aspect provides a method performed by a wireless device operating in a discontinuous reception, DRX, mode having an active state and a sleep state. The method includes, responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extending an active time of the DRX mode during which the wireless device is in the active state.

TECHNICAL FIELD

This disclosure relates to discontinuous reception (DRX) by a wireless device, and in particular to changing a DRX active time for a wireless device.

BACKGROUND

Next generation systems may be expected to support a wide range of use cases and devices, with varying requirements ranging from fully mobile devices, to stationary Internet of Things (IoT) or fixed wireless broadband devices. The traffic pattern associated with many use cases is expected to consist of short or long bursts of data traffic with varying lengths of waiting period in-between. The waiting periods are herein referred to as an inactive state. In New Radio (NR), both license assisted access and standalone unlicensed operation are to be supported in 3GPP. Hence the procedure of Physical Random Access Channel (PRACH) transmission and/or a Scheduling Request (SR) transmission in unlicensed spectrum may be investigated in 3GPP. In the following, New Radio Unlicensed (NR-U) and channel access procedure for an unlicensed channel based on Listen Before Talk (LBT) is introduced.

In order to tackle the ever increasing data demand, NR is considered for both the licensed and unlicensed spectrum. Compared to the Long Term Evolution License Assisted Access (LTE LAA), NR-U may also need to support Dual Connectivity (DC) and standalone scenarios, where the Medium Access Control (MAC) procedures including Random Access Procedure (RACH) and scheduling procedure taking place on the unlicensed spectrum are subject to the LBT failures, whereas there was no such restriction in LTE LAA, since there was licensed spectrum in LAA scenario so the RACH and scheduling related signaling could be transmitted on the licensed spectrum instead of unlicensed spectrum.

For discovery reference signal (DRS) transmissions such as Primary Synchronization Signal (PSS) or Secondary Synchronization Signal (SSS), Physical Broadcast Channel (PBCH), Channel State Information Reference Signal (CSI-RS), control channel transmissions such as on the Physical Uplink Control Channel (PUCCH) or the Physical Downlink Control Channel (PDCCH), transmission on the physical data channels such as the Physical Uplink Shared Channel (PUSCH) of the Physical Downlink Shared Channel (PDSCH), and uplink sounding reference signals such as a Sounding Reference Signal (SRS) transmission, channel sensing may be applied to determine the channel availability before the physical signal is transmitted using the channel.

The Radio Resource Management (RRM) procedures in NR-U would be generally similar to those used in LAA, since NR-U is aiming to reuse LAA, enhanced-Licensed Assisted Access (eLAA) or further enhanced-Licensed Assisted Access (feLAA) technologies as much as possible to handle the coexistence between NR-U and other legacy Radio Access Technologies (RATs). Radio Resource Management (RRM) measurements and report comprising special configuration procedure with respect the channel sensing and channel availability.

Hence, channel access/selection for LAA was one of a number of important aspects for ensuring coexistence with other Radio Access Technologies (RATs) such as Wi-Fi. For instance, LAA aimed to use carriers that are congested with Wi-Fi.

In the licensed spectrum, a UE measures Reference Signal Received Power (RSRP), and Reference Signal Received Quality (RSRQ) of the downlink radio channel, and provides the measurement reports to its serving base station (eNB/gNB). However, these measurements do not reflect the interference strength on the carrier. Another metric Received Signal Strength Indicator (RSSI) can reflect the interference strength on the carrier. At the eNB/gNB side, it is possible to derive RSSI based on the received RSRP and RSRQ reports, however, this requires the RSRP and RSRQ reports to be available. Due to the LBT failure, some reports in terms of RSRP or RSRP may be blocked (either because the reference signal transmission (DRS) is blocked in the downlink or the measurement report itself is blocked in the uplink). Hence, direct measurements in terms of RSSI are very useful. The RSSI measurements together with the time information concerning when and how long for the UEs have made the measurements can assist the gNB/eNB to detect the hidden node. Additionally, the gNB/eNB can measure the load of the carrier which is useful for the network to prioritize some channels for load balancing and channel access failure avoidance purposes.

LTE LAA has been defined to support measurements of averaged RSSI and channel occupancy for measurement reports. The channel occupancy is defined as a percentage of time that RSSI was measured above a configured threshold. For this purpose, a RSSI measurement timing configuration (RMTC) includes a measurement duration (e.g. 1-5 milliseconds, ms) and a period between measurements (e.g. {40, 80, 160, 320, 640} ms).

Channel Access Procedure in NR Unlicensed Spectrum

Listen-before-talk (LBT) is designed for the unlicensed spectrum to co-exist with other RATs. In this mechanism, a radio device applies a clear channel assessment (CCA) check (i.e. channel sensing) before any transmission. The transmitter involves energy detection (ED) over a time period compared to a certain threshold (ED threshold) in order to determine if a channel is idle. In case the channel is determined to be occupied, the transmitter performs a random back-off within a contention window before the next CCA attempt. In order to protect the acknowledgement (ACK) transmissions, the transmitter must defer a period after each busy CCA slot prior to resuming back-off. As soon as the transmitter has grasped access to a channel, the transmitter is only allowed to perform transmission up to a maximum time duration (namely, the maximum channel occupancy time (MCOT)). For Quality of Service (QoS) differentiation, a channel access priority based on the service type has been defined. For example, there are four LBT priority classes that are defined for differentiation of contention window sizes (CWS) and MCOT between services.

COT Sharing in NR-U

For a node (e.g., NR-U gNB/UE, LTE-LAA eNB/UE, or Wi-Fi AP/STA)) to be allowed to transmit in unlicensed spectrum (e.g., 5 GHz band) it typically needs to perform a clear channel assessment (CCA) as described above. This procedure typically includes sensing the medium to be idle for a number of time intervals. Sensing the medium to be idle can be done in different ways, e.g. using energy detection, preamble detection or using virtual carrier sensing. Where the latter implies that the node reads control information from other transmitting nodes informing when a transmission ends. After sensing the medium to be idle, the node is typically allowed to transmit for a certain amount of time, sometimes referred to as transmission opportunity (TXOP). The length of the TXOP depends on regulation and the type of CCA that has been performed, but typically ranges from 1 ms to 10 ms. This duration is often referred to as a COT (Channel Occupancy Time).

In Wi-Fi, feedback of data reception acknowledgements (ACKs) is transmitted without performing clear channel assessment. Preceding feedback transmission, a small time duration (called SIFS) is introduced between the data transmission and the corresponding feedback which does not include actual sensing of the channel. In 802.11, the SIFS period (16 microseconds, μs, for 5 GHz OFDM PHYs) is defined as:
aSIFSTime=aRxPHYDelay+aMACProcessingDelay+aRxTxTurnaroundTimewhere aRxPHYDelay defines the duration needed by the Physical (PHY) layer to deliver a packet to the MAC layer,aMACProcessingDelay defines the duration that the MAC layer needs to trigger the PHY layer transmitting a response, andaRxTxTurnaroundTime defines the duration needed to turn the radio from reception into transmit mode.

Therefore, the SIFS duration is used to accommodate for the hardware delay to switch the direction from reception to transmission.

It is anticipated that for NR in unlicensed bands (NR-U), a similar gap to accommodate for the radio turnaround time will be allowed. For example, this will enable the transmission of PUCCH carrying Uplink Control Information (UCI) feedback as well as PUSCH carrying data and possible UCI within the same transmit opportunity (TXOP) acquired by the initiating gNB, without the UE performing clear channel assessment before PUSCH/PUCCH transmission as long as the gap between downlink (DL) and uplink (UL) transmission is less than or equal to 16 μs. Operation in this manner is typically called “COT sharing”. An example is shown inFIG.1, which shows transmission opportunities (TXOP) both with and without COT sharing where CCA is performed by the initiating node (gNB). For the case of COT sharing the gap between DL and UL transmission is less than 16 μs.

When a UE accesses a medium via, for example, category 4 LBT with a configured grant outside of a gNB COT, it is also possible for UE and gNB to share the UE acquired COT to schedule DL data to the same UE. The UE COT information can be indicated in UCI such as CG-UCI for configured grant PUSCH resources. An example on UE COT sharing is shown inFIG.2, which is an example of a UE COT sharing with the DL transmission. For the case of COT sharing the gap between UL and DL transmission is less than 16 μs.

There currently exist certain challenge(s).

In the unlicensed system, data transmission interruption and latency may be incurred due to LBT operations, which may lead to service QoS degradation for a UE. Therefore, the COT sharing mechanism described above has been identified to be beneficial to reduce unnecessary LBT operations for NR-U. However, it is important that the gap between two consecutive transmission bursts must be less than a given time period in order to share a COT. For example, as described in the TR 38.889 V 16.0.0:

Within a gNB-initiated COT, an UL burst for a UE consisting of one or more of PUSCH, PUCCH, PRACH, and SRS follows the channel access schemes in Table 7.2.1.3.1-3.

TABLE 7.2.1.3.1-3Channel access schemes for a UL burst within a gNB-initiated COT as LBE deviceCat 1 ImmediatetransmissionCat 2 LBTCat 4 LBTWhen the gap fromFor any of the following cases:N/Athe end of the DLWhen the gap between any two successivetransmission to the beginningscheduled/granted transmissions in the COT isof the UL burst is not morenot greater than 25 msecthan 16 msec. Note:For the case where a UL transmission in the gNBMaximum limits of theinitiated COT is not followed by a DLduration of the UL burst othertransmission in the same COTthan those already derivedNote: the duration from the start of the firstfrom MCOT duration limitstransmission within the channel occupancyshould be further discusseduntil the end of the last transmission in thewhen specifications aresame channel occupancy shall not exceed 20developed.ms.Note:An UL burst is defined as a set of transmissions from a given UE having no gaps or gaps of no more than 16 μs. Transmissions from a UE having a gap of more than 16 μs are considered as separate UL bursts.

Equivalently, a DL burst may be defined as a set of transmissions from a given base station having no gaps or gaps of no more than 16 μs.

Based on above description, in order for a UE to perform an uplink transmission immediately within a gNB initiated COT, the gap between the beginning of UL data burst and the end of DL burst must be shorter than 16 μs.

The following may be implemented by a wireless device or UE in order to detect a DL transmission burst.

The UE may assume that the presence of a signal, such as the DMRS, in any downlink PDCCH or Group Common (GC) PDCCH (GC-PDCCH) transmission, to be indicative of an upcoming downlink transmission burst by the serving gNB. The UE may then enable power saving by not necessitating performing blind decodes to detect the transmission burst (Note: The power saving possibility by not necessitating blind decodes assumes performance relaxation for PDCCH decoding is not needed. Also, this does not mandate a two-step PDCCH decoding process for the UE with respect to DMRS detection).

The payload of a PDCCH and/or GC-PDCCH transmission may contain information regarding the COT structure that may then be used by the UE for power saving.

There may therefore be two aspects that are able to apply to enhance the UE power saving. The two aspects are concluded as below:

Aspect 1: the design of a shared COT concept is to allow a transmitter (either a UE or a gNB) to initiate a transmission without the UE (or eNB) performing clear channel assessment before transmission as long as the gap between two adjacent transmissions is less than or equal to 16 μs. For UEs in a shared COT, the UE needs to monitor PDCCHs more often to prepare for any potential transmission or reception. In other words, UEs that are not in a shared COT may not in principle need to monitor PDCCHs.

Aspect 2: with a signal such as the DMRS carried by a PDCCH or GC-PDCCH, the UE can detect if there is an upcoming DL transmission burst from the gNB associated with a COT. If there is a DL transmission burst presented or indicated by the DMRS or other downlink signaling, a UE may then monitor the PDCCH for potential DL data reception of the upcoming DL transmission burst. In other words, if there is not a DL transmission burst presented or indicated by a DMRS or other downlink signaling, the UE may not need to monitor PDCCH.

Discontinuous Reception (DRX) is a technique for reducing battery power consumption by UEs, in which the UE's receiver is switched off except during configured periods at configured intervals. Operating in a DRX mode comprises switching between an active (or ‘on’) state in which the UE's receiver is switched on, and a sleep (or ‘off’) state in which the UE's receiver is switched off. For a DRX cycle, the duration of the active state and the duration of the sleep state are (independently) configurable, and the DRX cycle length is defined as the sum of the durations of the active state and the sleep state within the DRX cycle.

The following statements may be true for Discontinuous Reception (DRX) mode in NR-U. The DRX On-duration may start as in Rel-15 NR (except for potentially to have a new switch trigger to go to short DRX, i.e. where the ‘Off-duration’ is shortened). There may be one DRX configuration for one MAC entity (no change). The DRX active time may be extended, or go to short DRX, by a non-data DL transmission (however, which is not a Wake Up Signal (WUS), which has been defined for Machine Type Communications (MTC) and NB-IOT battery saving in LTE).

SUMMARY

It may therefore be beneficial to determine whether or not the DRX active time needs to be extended based on detection of a DL signalling indicating an upcoming data burst. Extending the DRX active time typically means that the proportion of time that the UE is in the active state is increased. Therefore extending the DRX active time can include any of: extending the duration of the DRX active time while maintaining the duration of the DRX sleep time (which will lead to a longer DRX cycle length), extending the duration of the DRX active time while shortening the duration of the DRX sleep time (which can be used to maintain the same DRX cycle length), or the duration DRX active time can be maintained while shortening the duration of the DRX sleep time (which will lead to a shorter DRX cycle length).

For example it may be unnecessary for all UEs in the cell/bandwidth part (BWP) to extend their DRX active time, because it may be that only some of the UEs are able to be scheduled within the COT period due to limits on the system capacity. Otherwise, there would be a risk of an increase in power consumption for those UEs that are not able to be scheduled.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.

There is provided a method for a wireless device to determine whether to extend its discontinuous reception (DRX) mode active time. In particular, the method may be performed upon receipt of a DL signal indicating upcoming transmission of a downlink data burst. With the proposed method, only a subset of UEs that are potentially going to be scheduled with the COT in the system adjust or extend their DRX active time or DRX configuration. In this way, a good balance between UE power saving and better service Quality of Service (QoS) guarantee is achieved.

There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.

According to a first aspect, there is provided a method performed by a wireless device operating in a discontinuous reception, DRX, mode having an active state and a sleep state. The method comprises: responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extending an active time of the DRX mode during which the wireless device is in the active state.

According to a second aspect, there is provided a method performed by a base station. The method comprises: transmitting, or causing to transmit, signaling to a wireless device, wherein the signaling includes or comprises information indicating that the wireless device can extend an active time of a DRX mode responsive to the wireless device receiving downlink signaling from the base station or another base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition.

According to a third aspect, there is provided a wireless device configured to operate in a discontinuous reception, DRX, mode. The wireless device comprises: processing circuitry configured to: responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extend an active time of the DRX mode during which the wireless device is in the active state; and power supply circuitry configured to supply power to the wireless device.

According to a fourth aspect, there is provided a base station. The base station comprises: processing circuitry configured to: transmit, or cause to transmit, signaling to a wireless device, wherein the signaling includes or comprises information indicating that the wireless device can extend an active time of a DRX mode responsive to the wireless device receiving downlink signaling from the base station or another base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, and power supply circuitry configured to supply power to the base station.

According to a fifth aspect, there is provided a wireless device for operating in a discontinuous reception, DRX, mode. The wireless device is configured to, responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extend an active time of the DRX mode during which the wireless device is in the active state; and power supply circuitry configured to supply power to the wireless device.

According to a sixth aspect, there is provided a base station configured to transmit, or cause to transmit, signaling to a wireless device, wherein the signaling includes or comprises information indicating that the wireless device can extend an active time of a DRX mode responsive to the wireless device receiving downlink signaling from the base station or another base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, and power supply circuitry configured to supply power to the base station.

According to a seventh aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of the first aspect, the second aspect, or any embodiment thereof.

Certain of the above embodiments and the embodiments disclosed herein may provide one or more of the following technical advantage(s).

A wireless device with potential data transmission or reception need may adapt its DRX configuration for best power saving prior to start of a COT period initiated by the base station. Furthermore, a good balance between UE power saving and better service QoS guarantee is achieved.

DETAILED DESCRIPTION

The below embodiments are described in the context of NR unlicensed spectrum (NR-U). However, embodiments described herein are not limited to NR-U scenarios. They may also applicable to other unlicensed operation scenarios such as LTE LAA/eLAA/feLAA.

As noted above, in DRX, a UE's receiver is switched off (powered off/deactivated) except during configured periods at configured intervals. Operating in a DRX mode comprises switching between an active (or ‘on’) state in which the UE's receiver is switched on, and a sleep (or ‘off’) state in which the UE's receiver is switched off. The duration of the active state and the duration of the sleep state are (independently) configurable, and the DRX cycle length is defined as the sum of the durations of the active state and the sleep state.

According to some embodiments, there is provided a method performed by a wireless device operating in a discontinuous reception, DRX, mode having an active state and a sleep state, the method comprising: responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extending an active time of the DRX mode during which the wireless device is in the active state.

Thus, the downlink signaling from the base station (e.g. gNB) indicates that the base station will transmit data to the wireless device following that downlink signaling. The upcoming data burst is downlink data that will be transmitted to the wireless device.

As noted above, the channel occupancy time (COT) is the amount of time that a node is typically allowed to transmit after sensing the transmission medium to be idle. COT signaling (such as GC-PDCCH based signaling) can indicate when the COT starts, and/or when the COT ends. The COT signaling information and/or the DL signaling information indicating a coming data burst may be carried in the same signaling message, or in different signaling messages.

Also as noted above, extending the DRX active time means increasing the proportion of time that the UE is in the active state relative to the sleep state. Therefore extending the DRX active time can include any of: extending the duration of the DRX active time while maintaining the duration of the DRX sleep time (which will lead to a longer DRX cycle length), extending the duration of the DRX active time while shortening the duration of the DRX sleep time by a corresponding amount (which will maintain the same DRX cycle length), or the duration DRX active time can be maintained while shortening the duration of the DRX sleep time (which will lead to a shorter DRX cycle length). If, responsive to receiving the downlink signaling from the base station indicative of the upcoming data burst during a COT, none of the one or more conditions is met, then the active time of the DRX mode is not extended. In this case, there is no change to the DRX cycle length, or the durations of the DRX active time or DRX sleep time.

In embodiments where there is just one condition, the active time of the DRX mode is extended if the wireless device meets that condition and downlink signaling is received from the base station indicative of an upcoming data burst during a COT.

In embodiments where there are two or more conditions, it is sufficient for one or more of the conditions to be met for the active time of the DRX mode to be extended if downlink signaling is received from the base station indicative of an upcoming data burst during a COT.

The at least one condition may comprise a first condition that is met when the wireless device has not been scheduled for data transmission or reception for a first predetermined time period (e.g., after the last transmission or the reception of data by the wireless device, the wireless device has not been scheduled over X seconds), and either the wireless device has first uplink data ready for transmission (for example, in a buffer), or the wireless device estimates that there is first downlink data ready for reception from the base station (for example, based on known traffic pattern or based on a prediction). In this first condition, a timer may be introduced for defining the first predetermined time period accordingly. The length of the first predetermined time period (i.e. the value of X) may be configured based on a service type. For a service with a critical latency requirement, X can be set with a low value such as of the order of 100 ms, while for a service with a non-critical latency requirement, X can be set with a high value such as in the order of seconds. The value of X may be also set depending on the system load. A low value is set in case of low or medium system load, while a high value is set in case high system load.

The at least one condition may comprise a second condition that is met when the wireless device has transmitted second uplink data to the base station and there is a pending downlink acknowledgment from the base station of the transmitted second uplink data. In an alternative embodiment of the second condition, the second condition is met when the wireless device has transmitted second uplink data to the base station within a second predetermined time period and received no downlink acknowledgement from the base station of the transmitted second uplink data.

The at least one condition may comprise a third condition that is met when the wireless device has received third downlink data from the base station (for example recently) and there is a pending uplink acknowledgment of the received third downlink data for the wireless device to transmit. In an alternative embodiment of the third condition, the third condition is met when the wireless device has received third downlink data from the base station within a third predetermined time period (for example recently) and there is a pending uplink acknowledgment of the received third downlink data for the wireless device to transmit.

The at least one condition may comprise a fourth condition that is met when the wireless device has been triggered for Radio Resource Control (RRC) signaling. For example, the wireless device may have been triggered for RRC signaling due to mobility or reconfiguration needs and pending for transmission or reception. In an example, the fourth condition is met when a specific measurement event is fulfilled, and the UE needs to provide a measurement report accordingly via RRC signaling.

The at least one condition may comprise a fifth condition that is met when the wireless device has opportunities or occasions for uplink control signaling transmissions or downlink control signaling receptions during the channel occupancy time. In an example, the fifth condition is met when a wireless device is configured with PUCCH resources (frequency domain and time domain), and the wireless device can transmit PUCCH signaling using those configured PUCCH resources.

The at least one condition may comprise a sixth condition that is met when the wireless device belongs to a preconfigured group of wireless devices associated with the channel occupancy time. A group can be configured containing specific wireless devices. The sixth condition can be met where a base station (e.g. gNB) signals that the channel occupancy time is associated with that group.

The at least one condition may comprise a seventh condition that is met when the wireless device has a pending data transmission of a service or traffic type associated with the channel occupancy time. For example, the COT may be planned to serve the data transmission or reception for that service/traffic type. The service associated with a COT could be a delay sensitive service such as a video call. The base station (e.g. gNB) may signal the service type/priority indicator associated with the service in the COT information. Different services may require different channel occupancy time lengths to fulfil the QoS requirement.

The at least one condition may comprise an eighth condition that is met when the wireless device was unable to be scheduled for data transmission or reception during a last channel occupancy time. The base station (e.g. gNB) may signal this in the COT information-related signaling message for example, GC-PDCCH.

The at least one condition may comprise a ninth condition that is met when a channel access category and/or channel access priority class associated with wireless device data to be transmitted is the same as a channel access category and/or channel access priority class associated with the channel occupancy time. In other words, the channel access category and/or channel access priority class and/or Quality of Service (QoS) class identifier (e.g., QCI in LTE, and 5QI in NR) associated with the UE data is mapping to the channel access category and/or channel access priority class and/or QoS class identifier (e.g., QCI in LTE, and 5QI in NR) associated with the COT. As specified in 3GPP TS 37.213 v16.0.0, a UE can access a channel on which uplink (UL) transmission(s) are performed according to one of Type 1 or Type 2 UL channel access procedures. Type 1 channel access procedures are described in sub-clause 4.2.1.1. Type 2 channel access procedures are described in sub-clause 4.2.1.2. Different categories of channel access schemes can be used.

The at least one condition may comprise a tenth condition that is met when an identity of the wireless device is associated with the channel occupancy time. In other words, the wireless device ID (such as C-RNTI) may be determined to be relevant to the COT. The determination may be made via explicit signaling (such as Downlink Control Information (DCI), or Medium Access Control Control Element (MAC CE), or Radio Resource Control (RRC) signaling) or in an implicit fashion, such as the wireless device may be assigned to a COT which starts at a predefined time position, i.e., at a slot with an even index, while another wireless device may be assigned to a COT which starts at a slot with an odd index. In another example, the wireless device ID is assigned to a COT if the COT period is above a configured time period, meaning that the coming COT has sufficient resources in the time domain. The configured time period could be a certain number of time slots, which is sufficiently long enough to serve the data transmission for one or more wireless devices.

The at least one condition may comprise an eleventh condition that is met when a measured channel occupancy or a number of listen before talk (LBT) failures is below a configured threshold. A LBT failure occurs when the channel is determined to be busy by the wireless device. In other words, upon detection of DL signaling indicating a coming DL data burst associated with a COT period, a wireless device may determine to extend its DRX active time when the measured channel occupancy or the number of occurrences of LBT failures is below a configured threshold, meaning that the system (cell, bandwidth part (BWP), subband or channel) has a low load, so that all or most wireless devices in the system can be quickly serviced within a short time period. The configured threshold can be an absolute number, such as 10, 20, or a percentage such as 10%, 20% etc. This also means the function of the extension of DRX active time can be enabled or disabled dynamically. The enabling or disabling may require additional signaling, such as a RRC signaling message, a MAC CE or a DCI signaling.

The step of extending the active time of the DRX mode may comprise starting or restarting a first timer indicating a number of consecutive subframes for which the wireless device should be in the active state after receiving the downlink signaling. For example, the step of extending the active time of the DRX mode may comprise starting or restarting of the drx-InactivityTimer.

The step of extending the active time of the DRX mode may comprise; responsive to the wireless device operating in a longer DRX cycle when receiving the downlink signaling indicative of an upcoming data burst, switching from the longer DRX cycle to a shorter DRX cycle.

The step of extending the active time of the DRX mode may comprise applying a DRX configuration having a longer or more frequent second timer specifying a number of subframes for which the wireless device is in the active state for each DRX cycle. A ‘more frequent second timer’ means that the wireless device has more frequent (shorter) DRX cycles. For example, the step of extending the active time of the DRX mode may comprise applying a different DRX configuration with a more frequent or longer drx-onDurationTimer. The NR RRC specifications define a number of different possible values for the active time (e.g. 1 ms, 2 ms, 3 ms, 4 ms, 5 ms, 6 ms, 8 ms, 10 ms, 20 ms, 30 ms, 40 ms, 50 ms, 60 ms, 80 ms, 100 ms, 200 ms, 300 ms, 400 ms, 500 ms, 600 ms, 800 ms, 1000 ms, 1200 ms, 1600 ms), and extending the active time can comprise selecting a larger value for the active time from the available values.

The step of extending the active time of the DRX mode may comprise remaining in the active state for the duration of the channel occupancy time. For example, the wireless device may keep its DL PDCCH monitoring to be always active during the COT period.

The step of extending the active time of the DRX mode may comprise remaining in the active state for the duration of a third timer that starts in response to receiving the downlink signaling indicative of the upcoming data burst. For example, a new timer may be introduced into the DRX configuration, which defines the time period that the UE shall continue to keep its DL monitoring to be active after the detection of the DL signal indicating a coming data burst and the wireless device meeting the at least one condition. The third (new) timer may have a duration related to the COT, e.g. the third timer duration can be half the COT.

The step of extending the active time of the DRX mode may comprise extending the active time up to a configured maximum time. For example, upon detection of DL signaling indicating a coming data burst associated with (i.e. during) a COT period, a UE may be configured to extend its DRX active time for up to a configured time, or up to a configured maximum time period. The maximum time/period can be defined in terms of a number of slots. If there is no scheduling assignment or UL grant received by the UE, the UE may stop the extension of its DRX active time, or switch back to the ordinary DRX configuration or switch back to long DRX cycle if the UE is in short DRX cycle.

The channel occupancy time may be initiated by a base station or a wireless device. That is, the base station or wireless device (as appropriate) can perform channel sensing, and if the channel is idle, the base station or wireless device (as appropriate) starts transmission during the COT. For example, the detected (i.e. upcoming) data burst may be associated to a COT, initiated by a base station or initiated by a wireless device and shared with the base station and other wireless devices. For both cases, the base station may transmit a DL signaling indicating transmission of the data burst.

The downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time may comprise a demodulation reference signal.

The function of the extension of DRX active time upon detection of a coming data burst may be configured per UE, or service, or per cell/carrier/BWP/sub-band/channel basis. The configuration can be signaled to the UE by the base station (e.g. gNB) via signaling such as RRC signaling, a MAC control element (CE) or DCI. A new UE capability bit may be also introduced, that is preconfigured or stored at the UE (e.g. in the SIM card). The capability bit indicates the capability of the UE to extend the DRX active time as described herein. The base station may send a message (e.g. a RRC message) to the wireless device to query the capabilities of the wireless device. The wireless device can respond with its capability information.

Thus, in various embodiments, the wireless device can be configured to receive signaling from a base station indicating that the wireless device can extend an active time of a DRX mode responsive to the wireless device receiving downlink signaling from the base station or another base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition. In some embodiments the wireless device can be configured to receive signaling indicating the condition(s) to be met by the wireless device from the base station, for example in the downlink signaling that indicates an upcoming data burst.

In this respect, there is also provided a method performed by a base station, the method comprising transmitting, or causing to transmit, signaling to a wireless device, wherein the signaling includes or comprises information indicating that the wireless device can extend an active time of a DRX mode responsive to the wireless device receiving downlink signaling from the base station or another base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition. As noted above, the base station may signal the condition(s) to be met by the wireless device to the wireless device, for example in the downlink signaling that indicates an upcoming data burst. Where appropriate for the signaled condition, such signaling may also indicate a threshold or period applicable to the condition.

Also as noted above with respect to the tenth condition, the base station may signal an identity or identities of wireless devices that the COT is associated with.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated inFIG.3. For simplicity, the wireless network ofFIG.3only depicts network306, network nodes360and360b, and WDs310,310b, and310c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node360and wireless device (WD)310are depicted with additional detail. The wireless device310may be a wireless device as described in the embodiments above. The network node may be a base station (e.g. a gNB) as described in the embodiments above. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

InFIG.3, network node360includes processing circuitry370, device readable medium380, interface390, auxiliary equipment384, power source386, power circuitry387, and antenna362. Although network node360illustrated in the example wireless network ofFIG.3may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node360are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium380may comprise multiple separate hard drives as well as multiple RAM modules).

Processing circuitry370is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry370may include processing information obtained by processing circuitry370by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry370may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node360components, such as device readable medium380, network node360functionality. For example, processing circuitry370may execute instructions stored in device readable medium380or in memory within processing circuitry370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry370may include a system on a chip (SOC).

In some embodiments, processing circuitry370may include one or more of radio frequency (RF) transceiver circuitry372and baseband processing circuitry374. In some embodiments, radio frequency (RF) transceiver circuitry372and baseband processing circuitry374may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry372and baseband processing circuitry374may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry370executing instructions stored on device readable medium380or memory within processing circuitry370. In alternative embodiments, some or all of the functionality may be provided by processing circuitry370without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry370can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry370alone or to other components of network node360, but are enjoyed by network node360as a whole, and/or by end users and the wireless network generally.

Device readable medium380may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry370. Device readable medium380may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry370and, utilized by network node360. Device readable medium380may be used to store any calculations made by processing circuitry370and/or any data received via interface390. In some embodiments, processing circuitry370and device readable medium380may be considered to be integrated.

Interface390is used in the wired or wireless communication of signalling and/or data between network node360, network306, and/or WDs310. As illustrated, interface390comprises port(s)/terminal(s)394to send and receive data, for example to and from network306over a wired connection. Interface390also includes radio front end circuitry392that may be coupled to, or in certain embodiments a part of, antenna362. Radio front end circuitry392comprises filters398and amplifiers396. Radio front end circuitry392may be connected to antenna362and processing circuitry370. Radio front end circuitry may be configured to condition signals communicated between antenna362and processing circuitry370. Radio front end circuitry392may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry392may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters398and/or amplifiers396. The radio signal may then be transmitted via antenna362. Similarly, when receiving data, antenna362may collect radio signals which are then converted into digital data by radio front end circuitry392. The digital data may be passed to processing circuitry370. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node360may not include separate radio front end circuitry392, instead, processing circuitry370may comprise radio front end circuitry and may be connected to antenna362without separate radio front end circuitry392. Similarly, in some embodiments, all or some of RF transceiver circuitry372may be considered a part of interface390. In still other embodiments, interface390may include one or more ports or terminals394, radio front end circuitry392, and RF transceiver circuitry372, as part of a radio unit (not shown), and interface390may communicate with baseband processing circuitry374, which is part of a digital unit (not shown).

Antenna362may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna362may be coupled to radio front end circuitry390and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna362may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna362may be separate from network node360and may be connectable to network node360through an interface or port.

Antenna362, interface390, and/or processing circuitry370may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna362, interface390, and/or processing circuitry370may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry387may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node360with power for performing the functionality described herein. Power circuitry387may receive power from power source386. Power source386and/or power circuitry387may be configured to provide power to the various components of network node360in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source386may either be included in, or external to, power circuitry387and/or network node360. For example, network node360may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry387. As a further example, power source386may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry387. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node360may include additional components beyond those shown inFIG.3that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node360may include user interface equipment to allow input of information into network node360and to allow output of information from network node360. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node360.

As illustrated, wireless device310includes antenna311, interface314, processing circuitry320, device readable medium330, user interface equipment332, auxiliary equipment334, power source336and power circuitry337. WD310may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD310, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD310.

Antenna311may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface314. In certain alternative embodiments, antenna311may be separate from WD310and be connectable to WD310through an interface or port. Antenna311, interface314, and/or processing circuitry320may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna311may be considered an interface.

As illustrated, interface314comprises radio front end circuitry312and antenna311. Radio front end circuitry312comprise one or more filters318and amplifiers316. Radio front end circuitry314is connected to antenna311and processing circuitry320, and is configured to condition signals communicated between antenna311and processing circuitry320. Radio front end circuitry312may be coupled to or a part of antenna311. In some embodiments, WD310may not include separate radio front end circuitry312; rather, processing circuitry320may comprise radio front end circuitry and may be connected to antenna311. Similarly, in some embodiments, some or all of RF transceiver circuitry322may be considered a part of interface314. Radio front end circuitry312may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry312may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters318and/or amplifiers316. The radio signal may then be transmitted via antenna311. Similarly, when receiving data, antenna311may collect radio signals which are then converted into digital data by radio front end circuitry312. The digital data may be passed to processing circuitry320. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry320may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD310components, such as device readable medium330, WD310functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry320may execute instructions stored in device readable medium330or in memory within processing circuitry320to provide the functionality disclosed herein.

As illustrated, processing circuitry320includes one or more of RF transceiver circuitry322, baseband processing circuitry324, and application processing circuitry326. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry320of WD310may comprise a SOC. In some embodiments, RF transceiver circuitry322, baseband processing circuitry324, and application processing circuitry326may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry324and application processing circuitry326may be combined into one chip or set of chips, and RF transceiver circuitry322may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry322and baseband processing circuitry324may be on the same chip or set of chips, and application processing circuitry326may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry322, baseband processing circuitry324, and application processing circuitry326may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry322may be a part of interface314. RF transceiver circuitry322may condition RF signals for processing circuitry320.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry320executing instructions stored on device readable medium330, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry320without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry320can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry320alone or to other components of WD310, but are enjoyed by WD310as a whole, and/or by end users and the wireless network generally.

Processing circuitry320may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry320, may include processing information obtained by processing circuitry320by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD310, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium330may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry320. Device readable medium330may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry320. In some embodiments, processing circuitry320and device readable medium330may be considered to be integrated.

User interface equipment332may provide components that allow for a human user to interact with WD310. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment332may be operable to produce output to the user and to allow the user to provide input to WD310. The type of interaction may vary depending on the type of user interface equipment332installed in WD310. For example, if WD310is a smart phone, the interaction may be via a touch screen; if WD310is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment332may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment332is configured to allow input of information into WD310, and is connected to processing circuitry320to allow processing circuitry320to process the input information. User interface equipment332may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment332is also configured to allow output of information from WD310, and to allow processing circuitry320to output information from WD310. User interface equipment332may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment332, WD310may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Power source336may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD310may further comprise power circuitry337for delivering power from power source336to the various parts of WD310which need power from power source336to carry out any functionality described or indicated herein. Power circuitry337may in certain embodiments comprise power management circuitry. Power circuitry337may additionally or alternatively be operable to receive power from an external power source; in which case WD310may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry337may also in certain embodiments be operable to deliver power from an external power source to power source336. This may be, for example, for the charging of power source336. Power circuitry337may perform any formatting, converting, or other modification to the power from power source336to make the power suitable for the respective components of WD310to which power is supplied.

InFIG.4, UE400includes processing circuitry401that is operatively coupled to input/output interface405, radio frequency (RF) interface409, network connection interface411, memory415including random access memory (RAM)417, read-only memory (ROM)419, and storage medium421or the like, communication subsystem431, power source433, and/or any other component, or any combination thereof. Storage medium421includes operating system423, application program425, and data427. In other embodiments, storage medium421may include other similar types of information. Certain UEs may utilize all of the components shown inFIG.4, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

InFIG.4, RF interface409may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface411may be configured to provide a communication interface to network443a. Network443amay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network443amay comprise a Wi-Fi network. Network connection interface411may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface411may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM417may be configured to interface via bus402to processing circuitry401to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM419may be configured to provide computer instructions or data to processing circuitry401. For example, ROM419may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium421may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium421may be configured to include operating system423, application program425such as a web browser application, a widget or gadget engine or another application, and data file427. Storage medium421may store, for use by UE400, any of a variety of various operating systems or combinations of operating systems.

InFIG.4, processing circuitry401may be configured to communicate with network443busing communication subsystem431. Network443aand network443bmay be the same network or networks or different network or networks. Communication subsystem431may be configured to include one or more transceivers used to communicate with network443b. For example, communication subsystem431may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter433and/or receiver435to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter433and receiver435of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem431may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem431may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network443bmay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network443bmay be a cellular network, a Wi-Fi network, and/or a near-field network. Power source413may be configured to provide alternating current (AC) or direct current (DC) power to components of UE400.

The features, benefits and/or functions described herein may be implemented in one of the components of UE400or partitioned across multiple components of UE400. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem431may be configured to include any of the components described herein. Further, processing circuitry401may be configured to communicate with any of such components over bus402. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry401perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry401and communication subsystem431. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments500hosted by one or more of hardware nodes530. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications520(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications520are run in virtualization environment500which provides hardware530comprising processing circuitry560and memory590. Memory590contains instructions595executable by processing circuitry560whereby application520is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment500, comprises general-purpose or special-purpose network hardware devices530comprising a set of one or more processors or processing circuitry560, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory590-1which may be non-persistent memory for temporarily storing instructions595or software executed by processing circuitry560. Each hardware device may comprise one or more network interface controllers (NICs)570, also known as network interface cards, which include physical network interface580. Each hardware device may also include non-transitory, persistent, machine-readable storage media590-2having stored therein software595and/or instructions executable by processing circuitry560. Software595may include any type of software including software for instantiating one or more virtualization layers550(also referred to as hypervisors), software to execute virtual machines540as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines540, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer550or hypervisor. Different embodiments of the instance of virtual appliance520may be implemented on one or more of virtual machines540, and the implementations may be made in different ways.

During operation, processing circuitry560executes software595to instantiate the hypervisor or virtualization layer550, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer550may present a virtual operating platform that appears like networking hardware to virtual machine540.

As shown inFIG.5, hardware530may be a standalone network node with generic or specific components. Hardware530may comprise antenna5225and may implement some functions via virtualization. Alternatively, hardware530may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO)5100, which, among others, oversees lifecycle management of applications520.

In the context of NFV, virtual machine540may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines540, and that part of hardware530that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines540, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines540on top of hardware networking infrastructure530and corresponds to application520inFIG.5.

In some embodiments, one or more radio units5200that each include one or more transmitters5220and one or more receivers5210may be coupled to one or more antennas5225. Radio units5200may communicate directly with hardware nodes530via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system5230which may alternatively be used for communication between the hardware nodes530and radio units5200.

FIG.6shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. With reference toFIG.6, in accordance with an embodiment, a communication system includes telecommunication network610, such as a 3GPP-type cellular network, which comprises access network611, such as a radio access network, and core network614. Access network611comprises a plurality of base stations612a,612b,612c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area613a,613b,613c. Each base station612a,612b,612cis connectable to core network614over a wired or wireless connection615. A first UE691located in coverage area613cis configured to wirelessly connect to, or be paged by, the corresponding base station612c. A second UE692in coverage area613ais wirelessly connectable to the corresponding base station612a. While a plurality of UEs691,692are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station612.

Telecommunication network610is itself connected to host computer630, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer630may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections621and622between telecommunication network610and host computer630may extend directly from core network614to host computer630or may go via an optional intermediate network620. Intermediate network620may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network620, if any, may be a backbone network or the Internet; in particular, intermediate network620may comprise two or more sub-networks (not shown).

The communication system ofFIG.6as a whole enables connectivity between the connected UEs691,692and host computer630. The connectivity may be described as an over-the-top (OTT) connection650. Host computer630and the connected UEs691,692are configured to communicate data and/or signaling via OTT connection650, using access network611, core network614, any intermediate network620and possible further infrastructure (not shown) as intermediaries. OTT connection650may be transparent in the sense that the participating communication devices through which OTT connection650passes are unaware of routing of uplink and downlink communications. For example, base station612may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer630to be forwarded (e.g., handed over) to a connected UE691. Similarly, base station612need not be aware of the future routing of an outgoing uplink communication originating from the UE691towards the host computer630.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG.7. In communication system700, host computer710comprises hardware715including communication interface716configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system700. Host computer710further comprises processing circuitry718, which may have storage and/or processing capabilities. In particular, processing circuitry718may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer710further comprises software711, which is stored in or accessible by host computer710and executable by processing circuitry718. Software711includes host application712. Host application712may be operable to provide a service to a remote user, such as UE730connecting via OTT connection750terminating at UE730and host computer710. In providing the service to the remote user, host application712may provide user data which is transmitted using OTT connection750.

Communication system700further includes base station720provided in a telecommunication system and comprising hardware725enabling it to communicate with host computer710and with UE730. Hardware725may include communication interface726for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system700, as well as radio interface727for setting up and maintaining at least wireless connection770with UE730located in a coverage area (not shown inFIG.7) served by base station720. Communication interface726may be configured to facilitate connection760to host computer710. Connection760may be direct or it may pass through a core network (not shown inFIG.7) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware725of base station720further includes processing circuitry728, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station720further has software721stored internally or accessible via an external connection.

Communication system700further includes UE730already referred to. Its hardware735may include radio interface737configured to set up and maintain wireless connection770with a base station serving a coverage area in which UE730is currently located. Hardware735of UE730further includes processing circuitry738, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE730further comprises software731, which is stored in or accessible by UE730and executable by processing circuitry738. Software731includes client application732. Client application732may be operable to provide a service to a human or non-human user via UE730, with the support of host computer710. In host computer710, an executing host application712may communicate with the executing client application732via OTT connection750terminating at UE730and host computer710. In providing the service to the user, client application732may receive request data from host application712and provide user data in response to the request data. OTT connection750may transfer both the request data and the user data. Client application732may interact with the user to generate the user data that it provides.

It is noted that host computer710, base station720and UE730illustrated inFIG.7may be similar or identical to host computer630, one of base stations612a,612b,612cand one of UEs691,692ofFIG.6, respectively. This is to say, the inner workings of these entities may be as shown inFIG.7and independently, the surrounding network topology may be that ofFIG.6.

InFIG.7, OTT connection750has been drawn abstractly to illustrate the communication between host computer710and UE730via base station720, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE730or from the service provider operating host computer710, or both. While OTT connection750is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection770between UE730and base station720is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE730using OTT connection750, in which wireless connection770forms the last segment. More precisely, the teachings of these embodiments may improve the power consumption of the wireless device and thereby provide benefits such as extended battery lifetime of the wireless device.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection750between host computer710and UE730, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection750may be implemented in software711and hardware715of host computer710or in software731and hardware735of UE730, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection750passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software711,731may compute or estimate the monitored quantities. The reconfiguring of OTT connection750may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station720, and it may be unknown or imperceptible to base station720. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer710's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software711and731causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection750while it monitors propagation times, errors etc.

FIG.8is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.6and7. For simplicity of the present disclosure, only drawing references toFIG.8will be included in this section. In step810, the host computer provides user data. In substep811(which may be optional) of step810, the host computer provides the user data by executing a host application. In step820, the host computer initiates a transmission carrying the user data to the UE. In step830(which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step840(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG.10is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.6and7. For simplicity of the present disclosure, only drawing references toFIG.1010will be included in this section. In step1010(which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step1020, the UE provides user data. In substep1021(which may be optional) of step1020, the UE provides the user data by executing a client application. In substep1011(which may be optional) of step1010, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep1030(which may be optional), transmission of the user data to the host computer. In step1040of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG.11is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.6and7. For simplicity of the present disclosure, only drawing references toFIG.11will be included in this section. In step1110(which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step1120(which may be optional), the base station initiates transmission of the received user data to the host computer. In step1130(which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

FIG.12depicts a method in accordance with particular embodiments, wherein the method is performed by a wireless device operating in a discontinuous reception, DRX, mode having an active state and a sleep state. The method begins at step1202with responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extending an active time of the DRX mode during which the wireless device is in the active state.

FIG.13illustrates a schematic block diagram of an apparatus1300in a wireless network (for example, the wireless network shown inFIG.3). The apparatus may be implemented in a wireless device or network node (e.g., wireless device310or network node360shown inFIG.3). Apparatus1300is operable to carry out the example method described with reference toFIG.12and possibly any other processes or methods disclosed herein. It is also to be understood that the method ofFIG.12is not necessarily carried out solely by apparatus1300. At least some operations of the method can be performed by one or more other entities.

As illustrated inFIG.13, apparatus1300includes Extending unit1302. The Extending Unit1302is configured to responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extend an active time of the DRX mode during which the wireless device is in the active state.

FIG.14depicts a method in accordance with particular embodiments, wherein the method is performed by a base station. The method begins at step1402with the base station transmitting, or causing to transmit, signaling to a wireless device. The signaling includes or comprises information indicating that the wireless device can extend an active time of a DRX mode responsive to the wireless device receiving downlink signaling from the base station or another base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition.

FIG.15illustrates a schematic block diagram of an apparatus1500in a wireless network (for example, the wireless network shown inFIG.3). The apparatus may be implemented in a network node (e.g., network node360shown inFIG.3). Apparatus1500is operable to carry out the example method described with reference toFIG.14and possibly any other processes or methods disclosed herein. It is also to be understood that the method ofFIG.14is not necessarily carried out solely by apparatus1500. At least some operations of the method can be performed by one or more other entities.

As illustrated inFIG.15, apparatus1500includes Transmitting unit1502. The Transmitting unit1502is configured to transmit, or cause to transmit, signaling to a wireless device. The signaling includes or comprises information indicating that the wireless device can extend an active time of a DRX mode responsive to the wireless device receiving downlink signaling from the base station or another base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition.

Various groups of exemplary embodiments are set out in the following paragraphs:

Group A Embodiments

1. A method performed by a wireless device operating in a discontinuous reception, DRX, mode having an active state and a sleep state, the method comprising:a. responsive to receiving downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time, and responsive to the wireless device meeting at least one condition, extending an active time of the DRX mode during which the wireless device is in the active state.2. The method of embodiment 1 wherein the at least one condition comprises a first condition that the wireless device has not been scheduled for data transmission or reception for a first predetermined time period, and either the wireless device has first uplink data ready for transmission, or the wireless device estimates that there is first downlink data ready for reception from the base station.3. The method of any previous embodiment wherein the at least one condition comprises a second condition that the wireless device has transmitted second uplink data to the base station within a second predetermined time period and received no downlink acknowledgment from the base station of the transmitted second uplink data.4. The method of any previous embodiment wherein the at least one condition comprises a third condition that the wireless device has received third downlink data from the base station within a third predetermined time period and there is a pending uplink acknowledgment of the received third downlink data for the wireless device to transmit.5. The method of any previous embodiment wherein the at least one condition comprises a fourth condition that the wireless device has been triggered for Radio Resource Control signaling.6. The method of any previous embodiment wherein the at least one condition comprises a fifth condition that the wireless device has opportunities or occasions for uplink control signaling transmissions or downlink control signaling transmissions during the channel occupancy time.7. The method of any previous embodiment wherein the at least one condition comprises a sixth condition that the wireless device belongs to a preconfigured group of wireless devices associated with the channel occupancy time.8. The method of any previous embodiment wherein the at least one condition comprises a seventh condition that the wireless device has a pending data transmission of a service or traffic type associated with the channel occupancy time.9. The method of any previous embodiment wherein the at least one condition comprises an eighth condition that the wireless device was unable to be scheduled for data transmission or reception during a last channel occupancy time.10. The method of embodiment 1 wherein the at least one condition comprises a ninth condition that a channel access category and/or channel access priority class associated with wireless device data to be transmitted is the same as a channel access category and/or channel access priority class associated with the channel occupancy time.11. The method of any previous embodiment wherein the at least one condition comprises a tenth condition that an identity of the wireless device is associated with the channel occupancy time.12. The method of any previous embodiment wherein the at least one condition comprises an eleventh condition that a measured channel occupancy or a number of listen before talk failures is below a configured threshold.13. The method as in any previous embodiment wherein the step of extending the active time of the DRX mode comprises starting or restarting a first timer indicating a number of consecutive subframes for which the wireless device should be in the active state after receiving the downlink signaling.14. The method as in any previous embodiment wherein the step of extending the active time of the DRX mode comprises; responsive to the wireless device operating in a longer DRX cycle when receiving the downlink signaling indicative of an upcoming data burst, switching from the longer DRX cycle to a shorter DRX cycle.15. The method as in any previous embodiment wherein the step of extending the active time of the DRX mode comprises applying a DRX configuration having a longer or more frequent second timer specifying a number of subframes for which the wireless device is in the active state for each DRX cycle.16. The method as in any previous embodiment wherein the step of extending the active time of the DRX mode comprises remaining in the active time for the duration of the channel occupancy time.17. The method as in any previous embodiment wherein the step of extending the active time of the DRX mode comprises remaining in the active time for the duration of a third timer that starts in response to receiving the downlink signaling indicative of the upcoming data burst.18. The method as in any previous embodiment wherein the step of extending the active time of the DRX mode comprises extending the active time up to a configured maximum time.19. The method as in any previous embodiments wherein the channel occupancy time is initiated by a base station.20. The method as in any previous embodiments wherein the channel occupancy time is initiated by a wireless device.21. The method as in any previous embodiments wherein the downlink signaling from a base station indicative of an upcoming data burst during a channel occupancy time comprises a demodulation reference signal.22. The method of any of the previous embodiments, further comprising:providing user data; andforwarding the user data to a host computer via the transmission to the base station.

Group C Embodiments

23. A wireless configured to operate in a discontinuous reception, DRX, mode, the wireless device comprising:processing circuitry configured to perform any of the steps of any of the Group A embodiments; andpower supply circuitry configured to supply power to the wireless device.24. A user equipment (UE), the UE comprising:an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda battery connected to the processing circuitry and configured to supply power to the UE.25. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.26. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.27. The communication system of the previous 2 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE's processing circuitry is configured to execute a client application associated with the host application.28. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.29. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.30. A communication system including a host computer comprising:communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.31. The communication system of the previous embodiment, further including the UE.32. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.33. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.34. The communication system of the previous 4 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.35. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.36. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.37. The method of the previous 2 embodiments, further comprising:at the UE, executing a client application, thereby providing the user data to be transmitted; andat the host computer, executing a host application associated with the client application.38. The method of the previous 3 embodiments, further comprising:at the UE, executing a client application; andat the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,wherein the user data to be transmitted is provided by the client application in response to the input data.39. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.40. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.41. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Abbreviations

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).1×RTT CDMA2000 1× Radio Transmission Technology3GPP 3rd Generation Partnership Project5G 5th GenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplexing AccessCGI Cell Global IdentifierCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCPICH Ec/No CPICH Received energy per chip divided by the power density in the bandCQI Channel Quality informationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)E-SMLC Evolved-Serving Mobile Location CentreECGI Evolved CGIeNB E-UTRAN NodeBePDCCH enhanced Physical Downlink Control ChannelE-SMLC evolved Serving Mobile Location CenterE-UTRA Evolved UTRAE-UTRAN Evolved UTRANFDD Frequency Division DuplexFFS For Further StudyGERAN GSM EDGE Radio Access NetworkgNB Base station in NRGNSS Global Navigation Satellite SystemGSM Global System for Mobile communicationHARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionMAC Medium Access ControlMBMS Multimedia Broadcast Multicast ServicesMBSFN Multimedia Broadcast multicast service Single Frequency NetworkMBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDP Profile Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoder Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyRLM Radio Link ManagementRNC Radio Network ControllerRNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power ORReference Signal Received PowerRSRQ Reference Signal Received Quality ORReference Symbol Received QualityRSSI Received Signal Strength IndicatorRSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self Optimized NetworkSS Synchronization SignalSSS Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunication SystemUSIM Universal Subscriber Identity ModuleUTDOA Uplink Time Difference of ArrivalUTRA Universal Terrestrial Radio AccessUTRAN Universal Terrestrial Radio Access NetworkWCDMA Wide CDMAWLAN Wide Local Area Network