Patent Description:
Referring to <FIG>, a wireless communication system typically includes a base station <NUM> that communicates with a mobile wireless device <NUM>, sometimes referred to as a user equipment, or UE <NUM>. The base station <NUM> receives uplink communications <NUM> from the UE <NUM> and transmits downlink communications <NUM> to the UE <NUM>.

The <NUM> wireless standard, which is the fifth generation of cellular technology, is designed to increase speed, reduce latency, and improve flexibility of wireless services. A <NUM> system (5GS) includes both a new radio access network (NG-RAN) which makes use of a new air interface called New Radio (NR), and a new core network (5GC).

The initial release of <NUM> in Release <NUM> is optimized for mobile broadband (MBB) and ultra-reliable and low latency communication (URLLC). These services require very high data rates and/or low latency and therefore puts high requirements on the UE. To enable <NUM> to be used for other services with more relaxed performance requirements a new low complexity UE type is introduced in Release <NUM>, called 'reduced capability NR devices' or RedCap. The low complexity UE type is particularly suited for machine type communication (MTC) services, such as wireless sensors or video surveillance, but it can also be used for MBB services with lower performance requirements such as wearables. The low complexity UE has reduced capabilities compared to a Release <NUM> NR UE such as possibility to support lower bandwidth compared to what is currently required for a NR UE and possibility to support only one reception (Rx) branch and one MIMO layer.

When an NR device is in RRC CONNECTED mode, it may be configured to perform radio resource measurements, such as radio resource management (RRM) measurements. RRM measurements include, for example, measurements of signal strength at the UE. The UE can be configured to report such measurements to the network.

Radio resource measurements may consume UE power due to the need to perform measurement and also the reporting of those measurements. Hence it is discussed in 3GPP to introduce relaxed radio measurements in CONNECTED mode. The measurement requirements may be relaxed, for example, by decreasing the frequency at which the UE needs to perform a measurement.

Relaxed radio measurements may save some UE energy. However, they may at the same time reduce the accuracy of the measurements. Moreover, some measurements may never be performed or sent to the network. Hence the radio measurement relaxation should only be performed when certain conditions are met.

It has been discussed that the UE shall monitor certain conditions and report to the network when they are fulfilled and not. One possible condition is that the UE-measured reference signal received power (RSRP) or reference signal received quality (RSRQ) is above a certain threshold. In response to such a report, the network may configure the UE to perform radio measurement relaxation. Two have been discussed. In a first approach, the network explicitly indicates that the UE shall apply a relaxed radio measurement behavior (the behavior would likely be specified in a specification, e.g. that the frequency of the measurements is reduced). In a second approach, the network reconfigures the radio measurement configuration for the UE. For example, the network may deconfigure measurements on some frequencies, or the periodicity of radio measurement reporting may be increased, etc..

Document <CIT> Method and Apparatus for reporting relaxed measurement in a wireless communication system discloses various embodiments for reporting relaxed measurements.

Document RRM measurements relaxation in time domain, 3GPP R2-<NUM> also discus measurement relaxation issues.

Document 3GPP TS <NUM> V16. <NUM> comprises a large swat of information related to telecommunication.

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In particular, some embodiments described herein provide methods to ensure that the UE sends timely indications of fulfillment or radio measurement relaxation criteria/conditions, while avoiding sending unnecessary indications to the network. Some embodiments use various approaches, such as applying a time to trigger for the radio measurement relaxation fulfillment-report, applying a hysteresis for determining when to send the radio measurement relaxation fulfillment-report, avoiding sending a report with the same value as already indicated, avoiding indicating unfulfillment of conditions without having indicated fulfillment earlier, and/or applying a prohibit timer for sending the report.

Certain embodiments may provide one or more of the following technical advantage(s). In particular, by employing one or more such approaches, a UE may send timely reports to the network about radio measurement relaxation criteria/condition fulfillment/unfulfillment, while avoiding sending unnecessary reports.

Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. , in which examples of embodiments of inventive concepts are shown. In the following description, the term "RRM measurement relaxation" refers to mechanisms which enable a UE to reduce RRM measurements in a specified way or as configured by the network.

There currently exist certain challenge(s) with radio measurement relaxation, and in particular RRM measurement relaxation. For example, a UE may apply RRM measurement relaxation in IDLE mode. While in IDLE mode, the UE may monitor certain conditions, and when the conditions are fulfilled, the UE may apply relaxed radio measurements.

As described above, radio measurement relaxation in CONNECTED mode may be based on a report sent from the UE to the network which indicates that the UE fulfills certain conditions (e.g. that RSRP or RSRQ is above a certain threshold). The network may in response to such a report indicate to the UE that the UE shall apply RRM measurement relaxation in CONNECTED mode. The UE-to-network report for RRM measurement relaxation may be triggered when certain criteria are met for a predetermined period of time. That means that the UE may start to monitor those criteria only upon being configured with such reporting, even if the criteria had been fulfilled for a long time before being configured. Therefore, an opportunity to perform RRM measurement relaxation might be missed, which may cause unnecessary UE power consumption.

According to some embodiments, a UE may consider historical measurements when determining whether to send a report regarding radio measurement relaxation for connected mode. This may, for example, include measurements which the UE performed when the UE was in IDLE mode before entering connected mode. Moreover the measurements may include measurements the UE performed prior to receiving a radio measurement relaxation configuration from the network for sending reports regarding radio measurement relaxation in CONNECTED mode.

Some embodiments described herein may allow a UE to more quickly provide an indication to the network regarding fulfillment of radio measurement relaxation criteria. That in turn may enable the network to configure the UE to apply radio measurement relaxation earlier, and hence may result in more power saving in the UE. Although described primarily in the context of RRM measurement relaxation, it will be understood that the inventive concepts described herein may apply to other types of radio measurement relaxation.

According to some embodiments, a UE may monitor for the conditions for sending an RRM measurement relaxation report while in connected mode and also before entering CONNECTED mode, such as when the UE is in idle or inactive mode. The UE may, upon entering connected mode, determine if the UE should send the report based on the monitoring done in idle or inactive mode.

In some embodiments, the UE may store measurements or information related to measurements when in IDLE or INACTIVE and that data can be used upon entering connected mode to determine whether to send a report to the network about RRM measurement relaxation condition fulfillment.

In prior approaches, the UE would enter connected mode, and then, when the network subsequently configured the UE to perform RRM measurement relaxation reporting, start monitoring RRM measurement relaxation conditions. That would delay the sending of the report until at least the point in time when the network has been able to send the reporting configuration to the UE. The UE would possibly have to wait even longer, since there may be a time-to-trigger behavior associated with sending the report. This means that there may be a delay in sending the report when the UE enters connected mode, even if the UE had been been fulfilling the conditions prior to entering connected mode.

The mechanism for sending the RRM measurement relaxation report may use a time-to-trigger (TTT) timer such that the report is sent to the network only when the conditions have been fulfilled for a meaningful duration of time (rather than triggering the report due to a very short peak in e.g. RSRP/RSRQ). In some embodiments, the UE starts a TTT (or considers the TTT to have been started) already when the UE is in idle or inactive, and when entering connected if the condition has been fulfilled in IDLE or INACTIVE for a predetermined period time (that time may be the same as TTT). Another approach is that the TTT is started with a shorter duration to take in to account the IDLE or INACTIVE time.

<FIG> is an example graph of a measured parameter (e.g., RSRP or RSRQ) that is used to trigger RRM measurement relaxation reporting as a function of time with a time-to-trigger requirement. The sending of an RRM measurement relaxation report may be triggered if the measured parameter exceeds a threshold value (X) and stays above the threshold value for a TTT period. In the example illustrated in <FIG>, the measured parameter exceeds the threshold value X at a time T1 while the UE is in IDLE or INACTIVE mode and remains above the threshold for more than a TTT time period while the UE is in IDLE or INACTIVE mode. The UE transitions to CONNECTED mode at time T2, at which time the value of the measured parameter still exceeds the threshold value X. The UE may send an RRM measurement relaxation report immediately at time T2 when it enters CONNECTED mode. In these embodiments, the UE may start the TTT timer while it is in IDLE or INACTIVE mode.

<FIG> is an example graph of a measured parameter that is used to trigger RRM measurement relaxation reporting as a function of time with a time-to-trigger requirement according to further embodiments. In the embodiments of <FIG>, when the UE transitions to CONNECTED mode at time T2, the UE checks historical measurements taken when it was in IDLE or INACTIVE mode and determines that the value of the measured parameter was higher than the threshold X for at least a time period TTT prior to entering CONNECTED mode. The UE may then send an RRM measurement relaxation report immediately at time T2 when it enters CONNECTED mode.

<FIG> is an example graph of a measured parameter that is used to trigger RRM measurement relaxation reporting as a function of time with a time-to-trigger requirement according to the claimed embodiment. In <FIG>, when the UE transitions to CONNECTED mode at time T2, the UE checks historical measurements taken when it was in IDLE or INACTIVE mode and determines that the value of the measured parameter was higher than the threshold X for at least a first time period TTT1 prior to entering CONNECTED mode. Upon entering CONNECTED mode at time T2, the UE starts a timer of duration TTT2. After the expiration of the second time period TTT2 at time T3, the UE may send an RRM measurement relaxation report provided the value of the measured parameter has remained above the threshold X for the duration of the second time period TTT2. The second time period TTT2 may be shorter, longer, or the same length as the first time period TTT1.

Operations of a wireless communication device/UE according to some embodiments are illustrated in the flowchart of <FIG>. Referring to <FIG>, a method of operating a UE in a communication network is illustrated. The UE monitors (<NUM>) a network parameter while in the IDLE or INACTIVE state to determine whether the fulfillment condition or unfulfillment condition has been met. The UE may optionally determine (<NUM>) while the UE is in the IDLE or INACTIVE state that the fulfillment or unfulfillment condition has been met. The UE then switches (<NUM>) from INACTIVE or IDLE state to an ACTIVE state. After switching to the ACTIVE state, the UE determines (<NUM>) whether a fulfillment or unfulfillment condition for radio measurement relaxation has been persistently met for at least a time-to-trigger, TTT, period. The TTT period at least partially includes a time period during which the UE was in the INACTIVE or IDLE state. In response to determining that the fulfillment or unfulfillment condition has been met for the TTT period, the UE transmits (<NUM>) an RRM measurement relaxation report to a radio access network, RAN, node indicating that the fulfillment or unfulfillment condition has been met.

The method may include in starting a TTT timer that has a duration equal to the TTT period response to determining that the fulfillment or unfulfillment condition has been met during the IDLE or INACTIVE state.

The fulfillment condition may indicate that the UE is in a state that is suitable for RRM measurement relaxation, and may include a power level and/or quality of a reference signal received by the UE being greater than a threshold value.

The unfulfillment condition may indicate that the UE is in a state that is unsuitable for radio measurement relaxation, and may include a power level and/or quality of a reference signal received by the UE being less than a threshold value.

The method may further include, after switching to ACTIVE state, starting a timer having a timer duration. The radio measurement relaxation report is sent after expiration of the timer. The timer may have a duration different than the TTT period. In some embodiments, the duration of the timer is less than the TTT period.

In some embodiments, the method may include receiving a configuration for radio measurement relaxation after entering ACTIVE state. Determining that the fulfillment or unfulfillment condition has been met for the TTT period is performed in response to receiving the configuration for radio measurement relaxation.

In the embodiments described above, when a UE transitions from IDLE to CONNECTED mode, the UE may consider historical measurements for determining whether the conditions for radio measurement relaxation have been met. For example, the UE may consider measurements performed when it was in IDLE or INACTIVE when it later moves to CONNECTED, and those historical measurements may be used when the UE decides whether to send a report indicating that it has fulfilled radio measurement relaxation conditions.

In other embodiments, a UE which is in CONNECTED mode and subsequently receives a configuration for radio measurement relaxation reporting may consider historical measurements (i.e., measurements made before receiving the configuration) for determining whether the conditions for radio measurement relaxation have been met. That is, the UE may consider measurements performed before the configuration was received when determining whether to send the report or not. The measurements may include measurements taken while the UE was in IDLE or INACTIVE mode, or while the UE was in CONNECTED mode but had not yet become configured for RRM measurement relaxation reporting.

In some embodiments a UE will trigger to send the radio measurement relaxation report in response to being configured with such reporting, if, based on historical measurements, the UE has been fulfilling the conditions even before getting the configuration. For example, assume a UE has been fulfilling the conditions for radio measurement relaxation. If the UE becomes configured for the radio measurement relaxation reporting at time T, the UE may then send a report immediately at time T (or shortly thereafter since some processing time may be required).

For example, <FIG> is an example graph of a measured parameter that is used to trigger RRM measurement relaxation reporting as a function of time according to some embodiments. In the embodiments of <FIG>, a UE in CONNECTED mode becomes configured for RRM measurement relaxation reporting at time T1. The UE checks historical measurements taken prior to becoming configured for RRM measurement relaxation reporting and determines that the value of the measured parameter was higher than the threshold X for at least a time period TTT prior to becoming configured for RRM measurement relaxation reporting. The UE may then send an RRM measurement relaxation report immediately at time T1 after becoming configured for RRM measurement relaxation reporting.

<FIG> is an example graph of a measured parameter that is used to trigger RRM measurement relaxation reporting as a function of time according to further embodiments. In the embodiments of <FIG>, a UE in CONNECTED mode becomes configured for RRM measurement relaxation reporting at time T1. The UE checks historical measurements taken prior to becoming configured for RRM measurement relaxation reporting and determines that the value of the measured parameter was higher than the threshold X for at least a first time period TTT1 prior to becoming configured for RRM measurement relaxation reporting. Upon being configured for RRM measurement relaxation reporting at time T1, the UE starts a timer of duration TTT2.

After the expiration of a second time period TTT2 at time T2, the UE may send an RRM measurement relaxation report provided the value of the measured parameter has remained above the threshold X for the duration of the second time period TTT2. The second time period TTT2 may be shorter, longer, or the same length as the first time period TTT1.

The network may indicate to the UE whether the UE is allowed to consider historical measurements when determining whether or not to send the report. That configuration may be provided to the UE in a message which configures the feature for the UE.

From the perspective of the UE, the UE can take into account the possible use of historical data when it receives an indication or understands the network supports and can configure RRM measurement relaxation as described, or if for example in the past the network has indicated the UE is allowed to consider historical measurements. The UE may, in such cases, store historical data in case the network later configures the use of historical data for the purpose.

In some embodiments, in addition to measurements while in CONNECTED mode taken prior to becoming configured for RRM measurement relaxation reporting for determining whether RRM measurement relaxation conditions have been fulfilled, a UE may consider measurements taken while in IDLE and/or INACTIVE mode taken prior to entering CONNECTED mode and becoming configured for RRM measurement relaxation reporting for determining whether RRM measurement relaxation conditions have been fulfilled.

For example, as shown in <FIG>, a UE in IDLE or INACTIVE mode performs measurements on a measured parameter that is used to determine whether RRM measurement relaxation conditions have been fulfilled. The UE enters CONNECTED mode at time T1 and receives a configuration for RRM measurement relaxation reporting from the network at time T2. When the UE enters connected mode, the UE checks historical measurements taken prior to entering CONNECTED mode and determines that the value of the measured parameter was higher than the threshold X for at least a time period TTT prior to entering CONNECTED mode. The UE may send an RRM measurement relaxation report immediately at time T2 after becoming configured for RRM measurement relaxation reporting, provided the value of the measured parameter remained above the threshold X before becoming configured for RRM measurement relaxation.

Referring to <FIG>, a UE in IDLE or INACTIVE mode performs measurements on a measured parameter that is used to determine whether RRM measurement relaxation conditions have been fulfilled. The UE enters CONNECTED mode at time T1 and becomes configured for RRM measurement relaxation reporting at time T2. When the UE becomes configured for RRM measurement relaxation at time T2, the UE checks historical measurements taken prior to becoming configured for RRM measurement relaxation and determines that the value of the measured parameter was higher than the threshold X for at least a time period TTT prior becoming configured for RRM measurement relaxation, which includes measurements taken while the UE was in IDLE or INACTIVE mode. The UE may then send an RRM measurement relaxation report immediately at time T2 after becoming configured for RRM measurement relaxation reporting.

Operations of a wireless communication device/UE according to some embodiments are illustrated in the flowchart of <FIG>.

Referring to <FIG>, method of operating a UE in a communication network is illustrated. The UE monitors (<NUM>) a network parameter prior to receiving a configuration for radio measurement relaxation to determine whether a fulfillment condition or unfulfillment condition for radio measurement relaxation has been met. While in an ACTIVE state, the UE receives (<NUM>) a configuration for radio measurement relaxation. The UE determines (<NUM>) whether a fulfillment or unfulfillment condition for radio measurement relaxation has been persistently met for at least a time-to-trigger, TTT, period, where the TTT period at least partially includes a time period prior to receiving the configuration for radio measurement relaxation. In response to determining that the fulfillment or unfulfillment condition has been met for the TTT period, the UE transmits (<NUM>) a radio measurement relaxation report to a radio access network, RAN, node (<NUM>) indicating that the fulfillment or unfulfillment condition has been met.

The method may further include starting a TTT timer that has a duration equal to the TTT period in response to determining that the fulfillment or unfulfillment condition has been met prior to receiving the configuration for radio measurement relaxation.

The method may further include starting a timer having a timer duration after receiving the configuration for radio measurement relaxation. The radio measurement relaxation report is sent after expiration of the timer. The timer may have a duration different than the TTT period. In some embodiments, the duration of the timer is less than the TTT period.

In some embodiments, the time period prior to receiving the configuration for radio measurement relaxation includes a time period in which the UE was in IDLE or INACTVE state.

A UE may send the report which indicates to the network that the UE has fulfilled radio measurement relaxation conditions in a "UE assistance information" message. However, other approaches may also be used.

For example, one approach is to send the report in an RRC message during the RRC setup procedure or the RRC resume procedure. Such a report is referred to herein as an early indication. The early indication may for example be sent in an RRCSetupRequest, RRCSetupComplete, RRCResumeRequest or RRCResumeComplete message. The early indication may be implemented by a flag set to a certain value to indicate the early indication, or a flag which is present to indicate the early indication.

In some embodiments a UE may send an early indication only if the network explicitly indicates that the UE is allowed to do so. The network may indicate whether it is allowed for example by sending an indication in system information, for example a flag in broadcast or dedicated system information and/or sending an indication to the UE before the UE went to IDLE or INACTIVE, for example in a configuration message which configured CONNECTED mode radio measurement relaxation reporting last time the UE were in CONNECTED.

Another approach is that the UE may consider itself to be allowed to send the indication the presence of some other fields an implicit indication. For example, the UE may consider that it can send the indication if the network configures thresholds related to an IDLE or INACTIVE mode radio measurement relaxation feature in broadcast system information or in dedicated UE configuration e.g. in other RRC signaling.

<FIG> is a block diagram illustrating elements of a communication device UE <NUM> (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Communication device <NUM> may be provided, for example, as discussed below with respect to wireless device <NUM> of <FIG> and/or UE <NUM> of <FIG>. As shown, communication device UE may include an antenna <NUM> (e.g., corresponding to antenna <NUM> of <FIG>), and transceiver circuitry <NUM> (also referred to as a transceiver, e.g., corresponding to interface <NUM> of <FIG>) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node 1210A of <FIG>, also referred to as a RAN node) of a radio access network. Communication device UE may also include processing circuitry <NUM> (also referred to as a processor, e.g., corresponding to processing circuitry <NUM> of <FIG>) coupled to the transceiver circuitry, and memory circuitry <NUM> (also referred to as memory, e.g., corresponding to device readable medium <NUM> of <FIG>) coupled to the processing circuitry. The memory circuitry <NUM> may include computer readable program code that when executed by the processing circuitry <NUM> causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry <NUM> may be defined to include memory so that separate memory circuitry is not required. Communication device UE may also include an interface (such as a user interface) coupled with processing circuitry <NUM>, and/or communication device UE may be incorporated in a vehicle.

As discussed herein, operations of communication device UE may be performed by processing circuitry <NUM> and/or transceiver circuitry <NUM>. For example, processing circuitry <NUM> may control transceiver circuitry <NUM> to transmit communications through transceiver circuitry <NUM> over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry <NUM> from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry <NUM>, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry <NUM>, processing circuitry <NUM> performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless communication devices). According to some embodiments, a communication device UE <NUM> and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.

<FIG> shows an example of a communication system <NUM> in accordance with some embodiments.

In the example, the communication system <NUM> includes a telecommunication network <NUM> that includes an access network <NUM>, such as a radio access network (RAN), and a core network <NUM>, which includes one or more core network nodes <NUM>. The access network <NUM> includes one or more access network nodes, such as network nodes 1210a and 1210b (one or more of which may be generally referred to as network nodes <NUM>), or any other similar <NUM>rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes <NUM> facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212a, 1212b, 1212c, and 1212d (one or more of which may be generally referred to as UEs <NUM>) to the core network <NUM> over one or more wireless connections.

In some examples, the UEs <NUM> are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network <NUM> on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network <NUM>. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub <NUM> communicates with the access network <NUM> to facilitate indirect communication between one or more UEs (e.g., UE 1212c and/or 1212d) and network nodes (e.g., network node 1210b). In some examples, the hub <NUM> may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub <NUM> may be a broadband router enabling access to the core network <NUM> for the UEs. As another example, the hub <NUM> may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes <NUM>, or by executable code, script, process, or other instructions in the hub <NUM>. As another example, the hub <NUM> may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub <NUM> may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub <NUM> may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub <NUM> then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub <NUM> acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

The hub <NUM> may have a constant/persistent or intermittent connection to the network node 1210b. The hub <NUM> may also allow for a different communication scheme and/or schedule between the hub <NUM> and UEs (e.g., UE 1212c and/or 1212d), and between the hub <NUM> and the core network <NUM>. In other examples, the hub <NUM> is connected to the core network <NUM> and/or one or more UEs via a wired connection. Moreover, the hub <NUM> may be configured to connect to an M2M service provider over the access network <NUM> and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes <NUM> while still connected via the hub <NUM> via a wired or wireless connection. In some embodiments, the hub <NUM> may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1210b. In other embodiments, the hub <NUM> may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

<FIG> shows a UE <NUM> in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE <NUM> shown in <FIG>.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone's speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

<FIG> shows a network node <NUM> in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.

Applications <NUM> (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware <NUM> includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers <NUM> (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608a and 1608b (one or more of which may be generally referred to as VMs <NUM>), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer <NUM> may present a virtual operating platform that appears like networking hardware to the VMs <NUM>.

Hardware <NUM> may be implemented in a standalone network node with generic or specific components. Hardware <NUM> may implement some functions via virtualization. Alternatively, hardware <NUM> may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration <NUM>, which, among others, oversees lifecycle management of applications <NUM>. In some embodiments, hardware <NUM> is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via 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 signaling can be provided with the use of a control system <NUM> which may alternatively be used for communication between hardware nodes and radio units.

<FIG> shows a communication diagram of a host <NUM> communicating via a network node <NUM> with a UE <NUM> over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1212a of <FIG> and/or UE <NUM> of <FIG>), network node (such as network node 1210a of <FIG> and/or network node <NUM> of <FIG>), and host (such as host <NUM> of <FIG> and/or host <NUM> of <FIG>) discussed in the preceding paragraphs will now be described with reference to <FIG>.

One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve the power and/or resource consumption of a UE and thereby provide benefits such as increased battery life, reduced network utilization, and/or increased network capacity among others.

In some examples, 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 the OTT connection <NUM> between the host <NUM> and UE <NUM>, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host <NUM> and/or UE <NUM>. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection <NUM> passes; 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 software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection <NUM> may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node <NUM>. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host <NUM>. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection <NUM> while monitoring propagation times, errors, etc..

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without 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 non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

The term "and/or" (abbreviated "/") includes any and all combinations of one or more of the associated listed items.

Claim 1:
A method executed by a user equipment, UE, (<NUM>) in a communication network, comprising:
switching (<NUM>) the UE from INACTIVE or IDLE state to an ACTIVE state; after switching to the ACTIVE state, determining (<NUM>) by the UE whether a fulfillment or unfulfillment condition for radio measurement relaxation has been persistently met for at least a time-to-trigger, TTT, period, wherein the TTT period at least partially includes a time period during which the wireless device was in the INACTIVE or IDLE state;
in response to determining that the fulfillment or unfulfillment condition has been met for the TTT period, transmitting (<NUM>) a radio measurement relaxation report from the UE to a radio access network, RAN, node (<NUM>) indicating that the fulfillment or unfulfillment condition has been met,
after switching to ACTIVE state, starting a timer having a timer duration;
wherein the radio measurement relaxation report is sent after expiration of the timer.