UE triggers for starting early measurements in idle / inactive for 6g

Abstract

The present disclosure includes methods performed by a wireless device for Early Measurement Reporting (EMR). One embodiment can include receiving a message that includes an EMR configuration, a condition associated with an EMR procedure, and an indication to transition to an idle or inactive state. The method further includes performing one or more measurements associated with the EMR procedure based on the condition and the EMR configuration. The wireless device can monitor the condition while in the idle state or the inactive state and performs the one or more measurements when the condition is fulfilled. The condition may include an expiration of a timer or leaving WLAN coverage.

Description

UE TRIGGERS FOR STARTING EARLY MEASUREMENTS IN IDLE / INACTIVE FOR 6G CROSS-REFERNCE TO RELATED INFORMATION

[0001] This application claims the benefit of United States of America priority application No. 63 / 779,943, filed March 28, 2025, and titled, "UE Triggers for Starting Early Measurements in Idle / Inactive for 6G. "FIELD OF INVENTION

[0002] The present disclosure relates to methods and devices for triggering early measurement reporting procedures in idle or inactive states.BACKGROUNDRelease- 16 Early Measurements

[0003] In rel- 16 early measurements reporting (EMR) were standardized. EMR consists in the UE being configured to perform measurements while in RRC IDLE or RRC INACTIVE states and report the measurement results when transitioning to RRC CONNECTED, so-called IDLE or INACTIVE measurements (or EMR measurements). The network can use the measurement results to e.g. decide as early as possible which carrier to setup for carrier aggregation or dual connectivity. The alternative to EMR would have been to first configure measurement reports when the UE enters RRC CONNECTED (according to MeasConfig in the RRCReconfiguration) and get the first reports after few hundreds of milliseconds required for performing these so-called CONNECTED measurements. The problem is that often when these CONNECTED measurements are reported, some of the bursty traffic has already been scheduled in the PCell, i.e., activating the SCells and / or configuring SCells or an SCG at the point in time might be too late.

[0004] According to the existing solution (initially specified in Rel- 16), the IDLE or INACTIVE measurements for EMR are configured, at least partly, through dedicated signaling(RRC message RRCRelease). The dedicated configuration includes a timer (timer T331, set with measIdleDuration-rl6), for how long the UE is required to perform the IDLE / INACTIVE measurements for EMR, and it may include information about which frequency / -ies the UE needs to measure on. The timer T331 is started by the UE at reception of the configuration, when it enters IDLE or INACTIVE. The UE may optionally continue to perform measurements also after the timer T331 has expired.

[0005] Information about early measurement configuration can also be broadcasted in SIB11 and it e.g. contains information about the frequency the UE should measure on. If the dedicated signaling does not include information about frequencies to perform measurements on, the UE performs the measurements according to the broadcasted configuration in the cell where the UE is currently located. If the UE continues performing the measurements in RRC IDLE / RRC IN ACTIVE even after T331 is expired (or has been stopped) the UE performs the measurements on the frequency / -ies that is included in the broadcasted configuration (in SIB11) for the cell.

[0006] When the UE resumes or is being setup to RRC CONNECTED again, the UE can transmit, in RRCResumeComplete or RRCSetupComplete, an indication that it has measurement results. In RRCResumeComplete, the UE may also transmit the measurement results directly, if the network has requested this in the RRCResume message.

[0007] Figure 1 illustrates a procedure for early measurements.Enhancements to EMR After Rel- 16

[0008] After Rel-16 there have been further discussions and enhancements to EMR. The Rel-16 EMR measurement time is fully controlled by the T331 timer, due to the uncertainty of how long UE can stay within Idle / Inactive mode, the time when UE finishes the early measurements can be long before UE transition into the connected mode. The time validity of the EMRmeasurements is being challenged. The enhancement for release 18 of the 3 GPP standard is to introduce validity duration timer to indicate UE only report the fresh measurement results.

[0009] New IE of MeasurementValidityDuration was being introduced for Rel-18 EMR enhancements. Two new UE variables measIdleValidityDuration-rl 8 and measReselectionValidityDuration-rl 8 was being introduced for Rel-18 EMR to allow UE only to report fresh measurement results upon network configuration.

[0010] Another enhancement for in release 18 of the 3 GPP standard is to report cell-reselection measurements. Since measurement gaps are not available during Idle / Inactive mode, the UE must perform measurement on frequency basis. The EMR configuration allows up to 8 carriers for UE to perform measurement, when there is overlapping carrier with the Idle / Inactive inter-frequency measurement, UE can report these measurement results to the network work.

[0011] NewUE variables VarMeasReselectionConfig was being introduced for store the measurement configuration of Reselection carriers and the measurements.SUMMARY

[0012] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description.

[0013] In a first aspect, a method performed by a wireless device for Early Measurement Reporting, EMR, is provided. The method comprises receiving an RRC message including an EMR configuration, transitioning, in response to the message, to an idle state or an inactive state, monitoring, after transitioning to the idle state or the inactive state, a trigger condition for starting performance of one or more measurements based on the EMR configuration, and while in the idle state or the inactive state, when the trigger condition is fulfilled, starting performance of the one or more measurements based on the EMR configuration.

[0014] In a second aspect, a method performed by a wireless device for Early Measurement Reporting, EMR, is provided. The method comprises receiving an RRC message including an EMR configuration, transitioning, in response to the message, to an idle state or an inactive state, monitoring a trigger condition for starting performance of one or more measurements based on the EMR configuration based on a first timer, and while the trigger condition is not fulfilled, postponing a starting time to perform the one or more measurements based on the EMR configuration.

[0015] In a third aspect, a method performed by a network node for Early Measurement Reporting, EMR, is provided. The method comprises transmitting, to a wireless device, an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device while in an idle state or an inactive state, and receiving, from the wireless device, the one or more measurements performed based on the EMR configuration.

[0016] In a fourth aspect, a method performed by a network node for Early Measurement Reporting, EMR, is provided. The method comprises transmitting, to a wireless device, an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device based on a first timer while in an idle state or an inactive state, and receiving, from the wireless device, the one or more measurements performed based on the EMR configuration, wherein the wireless device postpones a starting time to perform the one or more measurements while the trigger condition is not fulfilled.

[0017] In a fifth aspect, a wireless device for Early Measurement Reporting, EMR, is provided. The wireless device comprises processing circuitry configured to perform the method of the first or second aspect, and a power source configured to supply power to the processing circuitry.

[0018] In a sixth aspect, a wireless device for Early Measurement Reporting, EMR, is provided. The wireless device comprises processing circuitry and a memory storing instructions whereby the processing circuitry is operable to perform the steps of receiving an RRC message including an EMR configuration, transitioning, in response to the message, to an idle state or an inactive state, monitoring, after transitioning to the idle state or the inactive state, a trigger condition for starting performance of one or more measurements based on the EMR configuration, and while in the idle state or the inactive state, when the trigger condition is fulfilled, starting performance of the one or more measurements based on the EMR configuration.

[0019] In a seventh aspect, a wireless device for Early Measurement Reporting, EMR, is provided. The wireless device comprises processing circuitry and a memory storing instructions whereby the processing circuitry is operable to perform the steps of receiving an RRC message including an EMR configuration, transitioning, in response to the message, to an idle state or an inactive state, monitoring a trigger condition for starting performance of one or more measurements based on the EMR configuration based on a first timer, and while the trigger condition is not fulfilled, postponing a starting time to perform the one or more measurements based on the EMR configuration.

[0020] In an eighth aspect, a network node for providing a measurement configuration is provided. The network node comprises processing circuitry configured to perform the method of the third or fourth aspect, and a power source configured to supply power to the processing circuitry.

[0021] In a ninth aspect, a network node for providing a measurement configuration is provided. The network node comprises processing circuitry and a memory storing instructions whereby the processing circuitry is operable to perform the steps of transmitting, to a wireless device, an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wirelessdevice while in an idle state or an inactive state, and receiving, from the wireless device, the one or more measurements performed based on the EMR configuration.

[0022] In a tenth aspect, a network node for providing a measurement configuration is provided. The network node comprises processing circuitry and a memory storing instructions whereby the processing circuitry is operable to perform the steps of transmitting, to a wireless device, an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device based on a first timer while in an idle state or an inactive state, and receiving, from the wireless device, the one or more measurements performed based on the EMR configuration, wherein the wireless device postpones a starting time to perform the one or more measurements while the trigger condition is not fulfilled.

[0023] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter.BRIEF DESCRIPTION OF FIGURES

[0024] Embodiments will be described, by way of example, with reference to the following drawings, in which:

[0025] Figure 1 illustrates a sequence diagram for an early measurement reporting procedure between a UE and a gNB, according to an embodiment.

[0026] Figure 2 illustrates a flowchart for a method performed by a UE for measurement reporting, according to an embodiment.

[0027] Figure 3 illustrates a flowchart for a method performed by a wireless device for measurement reporting, according to an embodiment.

[0028] Figure 4 illustrates a flowchart for a method performed by a wireless device for measurement reporting, according to an embodiment.

[0029] Figure 5 illustrates a flowchart for a method performed by a network node for providing a measurement configuration, according to an embodiment.

[0030] Figure 6 illustrates a flowchart for a method performed by a wireless device for Early Measurement Reporting, according to an embodiment.

[0031] Figure 7 illustrates a flowchart for a method performed by a wireless device for Early Measurement Reporting, according to an embodiment.

[0032] Figure 8 illustrates a flowchart for a method performed by a network node for Early Measurement Reporting, according to an embodiment.

[0033] Figure 9 illustrates a communication system, according to an embodiment.

[0034] Figure 10 illustrates a communication system including access points and stations, according to an embodiment.

[0035] Figure 11 illustrates a wireless device, according to an embodiment.

[0036] Figure 12 illustrates a network node, according to an embodiment.

[0037] Figure 13 illustrates a virtualization environment, according to an embodiment.

[0038] Common reference numerals are used throughout the figures to indicate similar features.DETAILED DESCRIPTION

[0039] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element,apparatus, component means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa.

[0040] A few notes on terminology. Herein, that the UE stores / reports / transmits / discards / deletes measurements should be understood as the UE stores / reports / transmits / discards / deletes measurement results. The terms "state" and "mode" should be interpreted as equivalent herein. The term "Early Measurement Reporting" or its abbreviation "EMR" is used herein. This is a term that was introduced for a concept / functionality in 5G. Certain embodiments may target 6G (or a later generation of mobile wireless networks), and it is possible that another term will be introduced for the same or a similar concept / functionality in 6G, but due to the lack of such a 6G term at the time of writing, the term "Early Measurement Reporting" / "EMR" is used herein also referring to the same or a similar concept / functionality in 6G. In this solution description, the terms "RRC Idle", "RRC Inactive" and "RRC Connected", or "Idle", "Inactive" and "Connected", are used to refer to states (e.g. 6G states) with the same or similar properties as "RRC\_IDLE, "RRC\_INACTIVE" and "RRC\_CONNECTED" in 5G. The term "RRC" refers to Radio Resource Control, which is a protocol used for signaling between a UE and a network node. Note 5: The term "Connected measurements" or "Connected mode measurements" or "Connected state measurements" is used herein to refer to measurements performed in RRC Connected state, or measurement results obtained from measurements performed in RRC Connected state. In this description, "releasing stored Connected measurements" means that that the UE discards or deletes the stored Connected measurements, or considers them as invalid and not to be reported to the network. The terms "frequency" and "carrier frequency" are considered to be equivalent herein. In the description, itis often referred to a signaling message, sometimes called "RRC Release", sometimes called "RRC\_Release", sometimes called "RRCRelease" or just "Release". All these terms refer to a potential future 6G message with a similar function as the RRCRelease message in 5G, i.e, to transition a UE from RRC\_CONNECTED state to RRC\_IDLE state or RRC\_INACTIVE state. The term "timer T331" or just "T331" is used in the solution description to refer to a timer used in a 6G UE for supervising the time the UE performs measurements for EMR, i.e. a timer similar to timer T331 in 5G. In the description, the term "gNB" or "gNodeB" is used when referring to a radio base station in 5G / NR, but due to the lack of a specific term for a radio base station in 6G, the terms "gNB" and "gNodeB" are used to refer to a radio base station in 6G too. When a UE in Idle or Inactive state has selected a cell to stay in, obtained downlink synchronization and acquired the necessary system information, this is referred to as the UE is camping on the cell. That cell is referred to as the UE's camping cell (or the camped cell). The carrier frequency used in the camping cell is referred to as the camping carrier frequency or the camping frequency or the camping carrier (or the camped carrier frequency or the camped frequency or the camped carrier). Although certain embodiments target future 6G telecom systems, it is also applicable to 5G / NR, or an advanced, evolved or enhanced version thereof. Under the present disclosure, the term early measurements refer to measurements that the UE has performed while in RRC\_IDLE or RRC\_INACTIVE state. The UE reports the measurement results upon transitioning to RRC\_CONNECTION state.

[0041] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0042] There currently exist certain challenges.• EMR measurements (i.e. measurements for the purpose of EMR) are performed by the UE while the UE is in RRC\_IDLE or RRC\_INACTIVE mode which typically is the timewhen UE saves energy. EMR measurement results are very useful to the network for setting up extra frequency resources or even direct activate aggregated carriers.• Currently upon receiving the EMR measurement configuration in an RRC\_Release message (e.g- IdleMeasConfig), UE shall start performing these measurements for EMR, so they are available if needed to be reported. However, due to the uncertainty of how long UE will stay within Idle / Inactive state, some of the measurements performed long before UE transition to RRC\_CONNECTED mode are not useful for the network, especially when UE is in high mobility states. These measurements are pure waste of energy from UE energy consumption aspect.• The Idle / Inactive measurement is different from typical connected mode measurement (i. e. measurements the UE performs while the UE is in RRC\_CONNECTED mode) due to its longer measurement period. Also, the Idle / Inactive measurement is conducted per frequency in a time sequential manner due to there is no measurement gap to scale up the measurements.

[0043] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The present disclosure includes a UE method wherein upon receiving the EMR measurement configuration (e.g. when the UE transitions to Inactive or Idle), the UE postpone measurement starting time without compromise the measurement quality.

[0044] Some embodiments can involve the UE monitoring new triggers for the starting of EMR measurements when it enters Idle or Inactive state. The EMR measurements can be performed while theUE is in Idle or Inactive, and according to the EMR measurement configuration (e.g. IdleMeasConfig). The UE does not start the EMR measurements upon entering Idle or Inactive, but afterwards, based on another trigger while the UE is in Idle or Inactive i.e. only after the UE has transitions to Idle or Inactive. The disclosure also includes further methods for re-starting measurements for EMR, if they have been stopped (and after they have stopped).

[0045] The disclosure also comprises certain ways the UE can receive one or more NW configurations (e.g. as part of the EMR configuration) to aid UE achieve energy savings by delaying the measurement starting time without compromise measurement results quality. Or, in other words, the UE receives EMR configuration associated to one or more triggers for starting to perform EMR measurements while in Inactive and Idle.

[0046] Furthermore, certain embodiments can include an indication in the measurement report contents to aid network decision for example indication on the availability of multiple rounds of measurement being triggered, the postponed starting time duration, how many rounds of measurement have been performed on which frequency, which condition have triggered the starting of measurement.

[0047] Figure 2 shows an example embodiment of a method performed by a UE for measurement reporting, in accordance with some embodiments of the present disclosure. Step 101, receive early measurement (EMR)configuration when transitioning to and / or in Idle / Inactive. Next, evaluate whether to start the measurement (e.g., determining if a trigger has happened). If yes, then perform measurement, step 102, based on the configuration. If no, then postpone the measurement starting time, step 103, and return to evaluating whether to start the measurement. After 102, it is determined whether to transition from RRC Idle / Inactive to RRC Connected. If yes, then evaluate measurement results and transmit measurement report, step 104. If no, then return to evaluating whether to start the measurement.

[0048] Below are provided several possible embodiments under the present disclosure.

[0049] Embodiment Al. A method at a UE, comprising: Receiving anRRC message (e.g. RRC release with or without suspend configuration) including an EMR configuration and, in response to the message, transitioning to Idle state or Inactive state; after the UE has transitions to Idle state or Inactive state, the UE monitors a trigger / condition for start performing one or more measurements based on the EMR configuration; and while in Idle or Inactive, when the trigger / condition is fulfilled, start performing the one or more measurements based on the EMR configuration.

[0050] Embodiment A2. A method of Al, wherein the trigger / condition is based on a timer expiry (Tl).

[0051] Embodiment A3. A method of A2, comprising starting the timer Tl when entering Idle or Inactive, and stopping the timer when transitioning to Connected (when the timer is running) again.

[0052] Embodiment A4. A method of Al, A2, A3, wherein upon expiry of timer Tithe UE starts a timer controlling EMR (e.g. timer T331).

[0053] Embodiment A5. A method of Al, wherein the trigger / condition is leaving the WLAN coverage

[0054] Embodiment A6. A method of Al, A5, wherein the WLAN coverage is computed based on the RS SI associated to the WLAN AP

[0055] Embodiment A7. A method of Al, A5, A6, wherein the trigger / condition further consisting of an ongoing data transmission using the WLAN AP.

[0056] Embodiment B 1. A method at a UE, comprising: receiving an RRC message (e.g. RRC release with or without suspend configuration) including an EMR configuration and, in response to the message, transitioning to Idle state or Inactive state; monitoring a trigger / condition for start performing one or more measurements based on the EMR configuration based on a timer (Tl); and while the trigger / condition is NOT fulfilled, postpone (or refrains from) the starting time to perform one of more measurements based on the EMR configuration.

[0057] Embodiment B2. A method of Bl, wherein the postpone is based on a timer expiry (T2).

[0058] Embodiment B3. A method of B2, comprising starting the timer T2 after entering Idle / Inactive upon monitoring timer T1 expires , and stopping the timer T2 when transition to connected mode(if the timer is running).

[0059] Embodiment B4. A method of Bl, B2, B3, wherein upon expiry of the timer T2, the UE starts a timer T1 to monitoring a trigger / condition for start performing one or more measurements.

[0060] Embodiment B5. A method of Al, wherein the trigger / condition is being within the WLAN coverage of a WLAN AP

[0061] Embodiment B6. A method of Al, A5, wherein the WLAN coverage is computed based on the RS SI associated to the WLAN AP

[0062] Embodiment B7. A method of Al, A5, wherein the trigger / condition further consisting of a lack of ongoing data transmission using the WLAN AP.

[0063] Certain embodiments may provide one or more of the following technical advantages. One advantage of certain embodiments is that it allows UE to save energy when it is not necessary to perform the measurements for EMR, without compromising the measurement results' quality. In the scenario where UE stays in Idle / Inactive for very long time, only the time before transition to Connected mode is within network's interest for setting up carrier aggregation. Instead of performing measurement directly from receiving the EMR measurement configuration, which is long before UE transition to connected, the UE can wait until there is triggered to start and not perform the measurement on the time when UE receives the measurement configuration.

[0064] Another advantage of certain embodiments is that by delaying measurement starting time for EMR measurements, the UE has higher chances to have latest fresh measurement results to report to the network. This will enable better network decision for activating extra carriers.

[0065] Also, by postpone measurement starting time without compromising measurement quality, the carrier will be maintained detected by the UE before network trigger activation command, this will speed up the activation procedure for the UE and shorten the activation delay.

[0066] As described above regarding Figure 2, certain embodiments propose a UE method and the method consisting of: receive (101) early measurement (EMR)configuration when transitioning to and / or in Idle / Inactive; evaluate whether to start the measurement; perform measurement (102) based on the configuration; postpone the measurement starting time (103); transition from RRC\_Idle / Inactive to RRC\_Connected; evaluate measurement results and transmit (104) measurement report.Receive (101) early measurement configuration when transitioning to and / or while inRRC Idle / Inactive

[0067] The following embodiments describes one or more of the aspects related to the configuration of the EMR measurements in relation to monitoring / starting to perform EMR measurement / postpone the starting time to perform the EMR measurements.

[0068] In some embodiments, a UE in RRC Idle or Inactive state could be configured to perform measurements when it transitions from Connected state to Inactive or Idle, e.g. , upon receiving an RRC\_Release message (i.e. the configuration may be included in the RRC\_Release message). Also, extra measurement configuration can be indicated to UE by SIB while UE is in RRC\_Idle / Inactive mode. The measurement configuration includes, but is not limited to, one or more of the following:• How long time the UE shall monitor the trigger condition;• Priority between frequencies.

[0069] In one example, the network has preconfigured high priority carrier(s) within the full configuration, in another example, there is a pre-configured criteria for UE to select which is thehighest priority carrier, in yet another example, the UE can select the highest priority carrier within the network pre-configured carrier list.• Trigger / condition / Criteria to start the measurements for EMR while in Inactive or Idle • When trigger / condition / criteria are not fulfilled within the configuration, configurations for UE postpone the start of measurement.Evaluate whether to start the measurement

[0070] According to the method the UE does not start EMR measurements, according to EMR configuration, upon reception of the EMR configuration in an RRC Release message, but after one or more trigger condition(s) or trigger criterion / criteria is(are) fulfilled. In the following, examples of trigger conditions / criteria are provided.

[0071] In some embodiments, the criteria to start the measurements for EMR is based on the UE mobility. In other words, as long as the UE remains static and / or semi-static (i.e. has not moved or moved insignificantly since it transitioned to Idle or Inactive state) the UE does not perform EMR measurements while in Idle or Inactive. The reasoning is that in Inactive state the last serving gNodeB has the latest measurements reported in Connected mode for that UE, and for the case of Idle state, the UE can retain the last measurement(s) performed in Connected state for later reporting if the UE remains static (optionally also applicable in Inactive state), and as long as UE remains in the same location, the measurements will likely not change, so performing these Idle / Inactive state measurements for EMR would have been unnecessary in this situation. Another way to handle the case when the UE transitions to Idle state could be that the gNB transfers Connected state measurement s), e.g. the latest Connected state measurement result(s) to the core network when the UE enters Idle state, so that this / these measurement result(s) can be downloaded from the core network to the next serving gNB.

[0072] In one embodiment, the UE mobility is determined by the occurrence of cell selection upon transitioning to Inactive or Idle if a cell other than the one the UE was connected in isselected. According to the embodiment, when the UE transitions to Idle or Inactive and receives the EMR configuration (e.g. in an RRC Release message), the UE selects a cell to camp on in Idle and Inactive. When the selected cell is the same cell as the UE was last connected (i.e. the same cell in which the UE has received the RRC Release with the EMR configuration), the UE does not start the measurements for EMR e.g. the UE does not start timer T331. And, when the selected cell is different than the cell as the UE was last connected (i.e. the same cell in which the UE has received the RRC Release with the EMR configuration), the UE starts the measurements for EMR e.g. the UE starts timer T331.

[0073] In one embodiment, the UE mobility is determined by the occurrence of cell reselection while in Inactive or Idle. According to the embodiment, when the UE transitions to Idle or Inactive and receives the EMR configuration (e.g. in an RRC Release message), the UE selects a cell to camp in Idle and Inactive. After having selected a cell, when the UE performs cell reselection, the UE starts to perform the measurements for EMR. For example, upon cell reselection the UE starts timer T331 and, while timer T331 is running, the UE performs the measurements for EMR.

[0074] In one embodiment, the UE mobility is determined by the occurrence of cell selection upon transitioning to Inactive or Idle, and cell re-selection while the UE is in Inactive or Idle. According to the embodiment, when the UE transitions to Idle or Inactive and receives the EMR configuration (e.g. in an RRC Release message), the UE selects a cell to camp on in Idle and Inactive. When the selected cell is the same cell as the UE was last connected (i.e. the same cell in which the UE has received the RRC Release with the EMR configuration), the UE does not start the measurements for EMR until a cell reselection occurs. For example, upon transitioning to Idle or Inactive the UE selects the same cell as the last serving cell (e.g. and does not start timer T331), and, when a cell reselection occurs while the UE is in Idle or Inactive, the UE starts to perform the measurements for EMR (and optionally also start timer T331).

[0075] In one embodiment, the UE mobility is determined by a change in a measurement quantity associated to the camping cell. The change in the measurement quantity is measured between the time of transitioning from Connected state to the Idle mode or Inactive state and the time of evaluation (i.e. evaluation of whether and how much a measurement quantity has changed). Alternatively, the change in the measurement quantity is measured between the time of the last performed measurement(s) before the UE transitioned to Idle or Inactive state and the time of evaluation (i.e. evaluation of whether and how much a measurement quantity has changed). As another alternative, the change in the measurement quantity is determined / measured by comparing measurement(s) performed in Idle or Inactive state with the latest measurements performed before the UE transitioned from Connected state to Idle or Inactive state, wherein the measurements performed in Idle or Inactive state may be measurements performed primarily with the purpose to evaluate whether the UE should reselect to another cell (i.e. change the camping cell). When such a change in the measurement quantity is above a threshold (either explicitly configured by the network node or hardcoded value in the specification or up to UE implementation), then the UE starts performing the EMR measurements according to the EMR configuration. The measurement quantity referred here could be e.g. Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), Signal-to-Noise Ratio (SNR) or Received Signal Strength Indicator (RS SI) of the camping cell.

[0076] In some embodiments, the criteria to start the measurements for EMR is based on a timer (denoted Tl) started when the UE enters Idle or Inactive (such a timer is different from timer T331). The UE starts the timer Tl when it enters Idle and Inactive and the UE is configured with an EMR configuration (in the RRC Release message and / or the broadcast system information). While the timer Tl is running the UE refrains from performing measurements for EMR. When timer Tl expires the UE starts to perform measurements for EMR. In some embodiments, the UE monitors potential triggers for starting EMR measurements (e.g. selection of a different cell than where the UE received the RRC Release message, cell reselection and / or a significant change in ameasurement quantity) immediately upon transitioning from Connected state to Idle or Inactive state and acts upon such a trigger (i.e. starts to perform measurements in accordance with the EMR configuration) if a trigger occurs (and then the UE stops timer Tl), but if no such trigger is detected before timer Tl expires, the UE starts performing measurements for EMR when timer Tl expires. In some other embodiments, the UE does not monitor potential triggers for starting EMR measurements while timer Tl is running, but when timer Tl expires, the UE starts to monitor potential triggers for starting EMR measurements.

[0077] In some embodiments, the UE considers both the timer Tl and UE mobility for triggering the measurements for EMR.• In one embodiment, the UE receives the EMR configuration (e.g. in an RRC Release message), transitions to Inactive or Idle, and performs cell selection to camp in Idle and Inactive. When the selected cell is the same cell as the UE was last connected (i.e. the same cell in which the UE has received the RRC Release with the EMR configuration), the UE starts timer Tl i.e. UE does not start the measurements for EMR (e.g. the UE does not start timer T331). And, when the selected cell is different than the cell as the UE was last connected (i.e. the same cell in which the UE has received the RRC Release with the EMR configuration), the UE starts the measurements for EMR e.g. the UE starts timer T331 , and does NOT start timer Tl .• In one embodiment, the UE receives the EMR configuration (e.g. in an RRC Release message), transitions to Inactive or Idle, performs cell selection to camp on in Idle or Inactive and starts timer Tl. When the selected cell is the same cell as the UE was last connected (i.e. the same cell in which the UE has received the RRC Release with the EMR configuration), the timer Tl continues to run and the UE does not start the measurements for EMR (e.g. the UE does not start timer T331). And, when the selected cell is different than the cell as the UE was last connected (i.e. the cell in which the UE has received theRRC Release with the EMR configuration), the UE stops timer T1 and starts the measurements for EMR e.g. the UE starts timer T331 , and does NOT start timer T1. • In one embodiment, when the UE transitions to Idle or Inactive and receives the EMR configuration (e.g. in an RRC Release message), the UE selects a cell to camp on in Idle or Inactive and starts timer Tl. While the timer T1 is running the UE does NOT perform measurements for EMR. After having selected a cell, when the UE performs cell reselection, the UE stops timer Tland starts to perform the measurements for EMR. For example, upon cell reselection while in Idle or Inactive, the UE stops timer Tl and starts timer T331 and, while timer T331 is running, the UE performs the measurements for EMR.• In one embodiment, the UE starts timer T331 upon cell reselection or upon expiry of timer Tl.• In one embodiment, the UE starts to perform measurements for EMR, while in Inactive or Idle, upon cell reselection or upon expiry of timer Tl.• In some embodiments, the criterion to start the measurements for EMR is based on monitoring signal quality e.g. determined by a measurement quantity such as RSRP, RSRQ , SINR, SNR or RS SI of the camping cell and detecting that a measurement quantity has changed or fluctuated more than a certain threshold based on the timer being configured Tl. Optionally, the criterion may be that change / fluctuation greater than a threshold for one of a set or channel quality measurement quantities is detected. As another option, the criterion may be that multiple channel quality related measurement quantities change / fluctuate more than respective thresholds. The UE starts the timer Tl when the UE receives the EMR measurement configuration and continuously evaluates the fluctuation / change of one or more channel quality related measurement quantity / quantities e.g. RSRP, RSRQ, SINR, SNR, RSSI, of the camping cell.• In one example, the large fluctuation / change of the camping cell signal quality, e.g. determined by a measurement quantity such as RSRP, RSRQ , SINR, SNR or RSSI, can be due to the reason that the UE is currently at the cell edge of the camping cell while thecell re-selection criteria are not fulfilled. The large fluctuation / change of the camping cell signal quality indicates that the UE is not in a static situation where measurement performed before starting of the T1 timer can be used, and hence the UE starts to perform the measurement(s) for EMR (and optionally starts timer T331).• In another example, the large fluctuation / change of the camping cell signal quality, e.g. determined by a measurement quantity such as RSRP, RSRQ , SINR, SNR or RS SI can be due to the reason that the UE currently experiences high interference from other UEs. Hence, the previous measurements performed before the starting of the T1 timer cannot be trusted, and consequently the UE starts to perform the measurement for EMR (and optionally starts timer T331).• In some embodiments, the criterion to start the measurements for EMR is based on a measurement on the WLAN receiver indicating lack of coverage from any of the first set of WLAN APs. The coverage of a WLAN AP could be defined based on one or more of the measurement quantities like RSRP, RS SI etc. In some embodiments, the UE could be explicitly configured with the set of WLAN APs that could be part of such a monitoring. In some other embodiments, it is up to the UE implementation. The coverage of a WLAN AP could be defined based on the signal strength associated to the WLAN AP being better than a threshold. When the UE has none of the WLAN APs amongst a set of WLAN APs being better than a threshold, the UE starts performing the EMR measurements. In some embodiments, this could be further constrained that the UE shall start performing the EMR measurements only if there is an ongoing data transmission using a WLAN AP when the WLAN APs' coverage becomes worse than a threshold.

[0078] UE performs the measurement according to the EMR configuration. And the UE performs measurement on frequency based on the priority that has been configured from the network.

[0079] In one example the transition to Connected mode (for example UE have UL traffic or UE being paged from the network) happened before the UE finishes the measurements, the UE will report the frequencies it has measured.

[0080] In another example, when UE has finished all the measurements being configured from the EMR configuration, there is still no transition to the connected mode, the UE can start to evaluate based on the triggers / criteria to start to perform measurements.

[0081] In one embodiment, the UE evaluates whether to start measurements again based on one or multiple embodiments described above.

[0082] In another embodiment, the UE directly postpones the measurements based on the embodiments described below.

[0083] In another embodiment, if the UE is in Idle or Inactive state and has received an EMR configuration and determines that it is camping on the carrier frequency with the highest priority (according to configuration received from the network), it may postpone the start of the measurements, e.g. for a duration determined by timer Tl.

[0084] In another embodiment, the UE starts measuring for EMR on different carrier frequencies at different times, based on the configured priorities of the carrier frequencies. For instance, the UE may first start to measure for EMR on carrier frequencies with equal priority as the camping carrier frequency or higher priority than the camping carrier frequency, e.g. when timer Tl expires or when a trigger for start of measurements for EMR has been detected, but starts measuring on the lower priority carrier frequencies later, where the difference in starting time may be configured by the network, e.g. based on a configured timer, or determined by UE implementation. In a variant of this, the carrier frequencies may be divided into more than two groups of carrier frequencies based on the configured priorities and more than two different EMR measurement starting times, one for each carrier frequency group.

[0085] When the evaluation timer T1 expires and no trigger / criterion for UE to start the EMR measurement has been fulfilled, the UE can postpone the measurement starting time.

[0086] In one embodiment, the UE postpones the measurement starting time for a duration determined by a timer denoted as T2 which is different from T1 and T331.

[0087] The timer T2 starts when T1 expires and none of the predefined triggers / criteria defined above is fulfilled.

[0088] In one example, the UE directly starts EMR measurement when T2 expires (and in some embodiments starts the timer T331).

[0089] In another example, when T2 expires, the UE continues to evaluate for trigger to start the EMR measurement based on the T1 timer and decide whether to start or postpone the measurement based on the second time of evaluation during T1 timer .

[0090] In yet another example, the UE start the EMR measurement after n times of T2 expiry.

[0091] In some embodiments, when the UE has performed measurements for EMR and timer T331 (if used) expires, the UE may start another timer, e.g. called timer T3, and when timer T3 expires, restart measurements for EMR and restart timer T331 (if timer T331 is used), and optionally delete the previously stored measurements for EMR. As another option, the UE deletes the previously stored measurements for EMR when a new set of EMR measurements, e.g. a full T331 period of new EMR measurements, have been performed and stored. As yet another option, the UE stores and retains all performed measurements for EMR. As yet another option, the UE retains N rounds of EMR measurements (i.e. when the (N+l)th round of EMR measurements have been performed, or when it is about to start, the first (oldest) round of EMR measurements is deleted (where N is an integer > 0). As one option, when the UE has more than one round of EMR measurements (e.g. N rounds of EMR measurements) stored when it transitions to Connected state, it indicates to the network that multiple (e.g. N) rounds of EMR measurements available. Based on this indication, the network may request the UE to report 0, all or a subset of the available1rounds of EMR measurements (e.g. M rounds of EMR measurements, where M fulfills 0 < M < N). Timer T3 may be configured by the network, specified in a standard or determined by UE implementation. The number N may be configured by the network, specified in a standard or determined by UE implementation.Evaluate Measurement Results and Transmit (104) Measurement Report

[0092] When the UE finishes the EMR measurements that have been configured, the UE can indicate to the network within the EMR measurement report about the information for postpone / start of the EMR measurement.

[0093] In one example, when / if the UE has postponed starting of the EMR measurement, the UE can indicate how many times of expiry for both for T1 and T2.

[0094] In one example, when UE has postponed EMR measurement while still having finished more than one round of the EMR measurement according to the EMR configuration, the UE can indicate multiple rounds of measurement results available. As another option, the UE only retains the last round of EMR measurements and reports these measurements or indicates their availability to the network.

[0095] In another example, when UE has postponed EMR measurement starting time, the UE can indicate which criteria triggered starting of the EMR measurements.

[0096] In yet another example, when UE has postponed EMR measurement starting time, while the UE has not been able to finish all the measurements that have been configured, the UE can indicate which criteria triggered starting of the EMR measurements.Additional Embodiments

[0097] Figure 3 illustrates a method 300 performed by a wireless device 4300 for Early Measurement Reporting (EMR) in accordance with some embodiments. At step 302, the wireless device 4300 receives a message from a network node 4400, where the message includes an EMR configuration, a condition associated with an EMR procedure, and an indication to transition to anidle state or an inactive state. At step 304, the wireless device 4300 performs one or more measurements associated with the EMR procedure based on the condition and the EMR configuration.

[0098] Method 300 can comprise a variety of additional, alternative, and / or optional steps, and / or other modifications. In some embodiments, based on the indication in the message, the wireless device 4300 transitions to the idle state or the inactive state. The wireless device 4300 may perform the one or more measurements after transitioning to the idle state or the inactive state. In certain embodiments, the wireless device 4300 monitors the condition while in the idle state or the inactive state. In some embodiments, the wireless device 4300 determines the condition to be fulfilled and, based on the determination, performs the one or more measurements. The condition may comprise an expiration of a first timer. In such embodiments, the wireless device 4300 starts the first timer upon transitioning to the idle state or the inactive state and stops the first timer upon transitioning to a connected state. In alternative embodiments, the condition is associated with leaving WLAN coverage. The WLAN coverage may be computed based on a Received Signal Strength Indicator (RS SI) associated with a WLAN access point. When the RS SI falls at or below a threshold, the wireless device 4300 may determine that it has left WLAN coverage and accordingly start performing the EMR measurements. In some embodiments, the message is received via Radio Resource Control (RRC) signaling. The message may comprise an RRC release message that instructs the wireless device 4300 to transition from a connected state to the idle state or the inactive state while also providing the EMR configuration and the condition for starting measurements. In some embodiments, after performing the one or more measurements, the wireless device 4300 transmits the measurement results to the network node 4400. The transmission may occur when the wireless device 4300 transitions back to the connected state, for example in an RRCResumeComplete or RRCSetupComplete message.

[0099] Eigure 4 illustrates a method 400 performed by a wireless device 4300 for Early Measurement Reporting (EMR) in accordance with some embodiments. At step 402, the wirelessdevice 4300 receives a message from a network node 4400, where the message includes an EMR configuration and a condition associated with an EMR procedure. At step 404, the wireless device 4300 determines the condition is not satisfied. At step 406, based on the determination, the wireless device 4300 prevents performance of the EMR procedure.

[0100] Method 400 can comprise a variety of additional, alternative, and / or optional steps, and / or other modifications. In some embodiments, the condition comprises a timer expiry. In such embodiments, determining the condition is not satisfied may comprise determining that a timer is running. In some embodiments, the wireless device 4300 subsequently determines the condition is satisfied and, based on the determination that the condition is satisfied, performs the EMR procedure. In certain embodiments, the wireless device 4300 starts a first timer associated with the condition and, upon expiration of the first timer, starts a second timer associated with the EMR procedure.

[0101] Figure 5 illustrates a method 500 performed by a network node 4400 for providing a measurement configuration in accordance with some embodiments. At step 502, the network node 4400 transmits, to a wireless device 4300, a message including an EMR configuration, a condition associated with an EMR procedure, and an indication to transition to an idle state or an inactive state. At step 504, the network node 4400 receives, from the wireless device 4300, one or more measurements associated with the EMR configuration.

[0102] Method 500 can comprise a variety of additional, alternative, and / or optional steps, and / or other modifications. In some embodiments, the indication is configured to trigger the wireless device 4300 to transition to the idle state or the inactive state. In certain embodiments, the message is transmitted via Radio Resource Control (RRC) signaling. The condition may comprise an expiration of a timer. In alternative embodiments, the condition is associated with leaving WLAN coverage.

[0103] Figure 6 illustrates a method 600 performed by a wireless device 4300 for Early Measurement Reporting (EMR) in accordance with some embodiments. At step 602, the wirelessdevice 4300 receives an RRC message including an EMR configuration. At step 604, the wireless device 4300 transitions, in response to the message, to an idle state or an inactive state. At step 606, the wireless device 4300 monitors, after transitioning to the idle state or the inactive state, a trigger condition for starting performance of one or more measurements based on the EMR configuration. At step 608, while in the idle state or the inactive state, when the trigger condition is fulfilled, the wireless device 4300 starts performance of the one or more measurements based on the EMR configuration.

[0104] Method 600 can comprise a variety of additional, alternative, and / or optional steps, and / or other modifications. In some embodiments, the trigger condition is based on a timer expiry. In certain embodiments, the wireless device 4300 starts a first timer when entering the idle state or the inactive state and stops the first timer when transitioning to a connected state. In some embodiments, upon expiry of the first timer, the wireless device 4300 starts a timer controlling EMR. In alternative embodiments, the trigger condition comprises leaving WLAN coverage. The WLAN coverage may be computed based on a Received Signal Strength Indicator (RS SI) associated with a WLAN access point. In some embodiments, the trigger condition further comprises an ongoing data transmission using the WLAN access point.

[0105] Figure 7 illustrates a method 700 performed by a wireless device 4300 for Early Measurement Reporting (EMR) in accordance with some embodiments. At step 702, the wireless device 4300 receives an RRC message including an EMR configuration. At step 704, the wireless device 4300 transitions, in response to the message, to an idle state or an inactive state. At step 706, the wireless device 4300 monitors a trigger condition for starting performance of one or more measurements based on the EMR configuration based on a first timer. At step 708, while the trigger condition is not fulfilled, the wireless device 4300 postpones a starting time to perform the one or more measurements based on the EMR configuration.

[0106] Method 700 can comprise a variety of additional, alternative, and / or optional steps, and / or other modifications. In some embodiments, the postponing is based on a second timerexpiry. In certain embodiments, the wireless device 4300 starts the second timer after entering the idle state or the inactive state upon expiry of the first timer and stops the second timer when transitioning to a connected state. In some embodiments, upon expiry of the second timer, the wireless device 4300 starts the first timer to monitor the trigger condition for starting performance of the one or more measurements. In alternative embodiments, the trigger condition comprises being within WLAN coverage of a WLAN access point. The WLAN coverage may be computed based on a Received Signal Strength Indicator (RS SI) associated with the WLAN access point. In some embodiments, the trigger condition further comprises a lack of ongoing data transmission using the WLAN access point.

[0107] Figure 8 illustrates a method 800 performed by a network node 4400 for Early Measurement Reporting (EMR) in accordance with some embodiments. At step 802, the network node 4400 transmits, to a wireless device 4300, an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device 4300 while in an idle state or an inactive state. At step 804, the network node 4400 receives, from the wireless device 4300, the one or more measurements performed based on the EMR configuration.

[0108] Method 800 can comprise a variety of additional, alternative, and / or optional steps, and / or other modifications. In some embodiments, the trigger condition is based on a timer expiry. In certain embodiments, the trigger condition comprises leaving WLAN coverage. The WLAN coverage may be computed based on a Received Signal Strength Indicator (RS SI) associated with a WLAN access point. In some embodiments, the RRC message comprises an RRC release message. In certain embodiments, the RRC message further includes an indication to transition to the idle state or the inactive state. In some embodiments, the trigger condition further comprises an ongoing data transmission using a WLAN access point. In certain embodiments, based on the received one or more measurements, the network node 4400 configures carrier aggregation or dual connectivity for the wireless device 4300.

[0109] Figure 9 shows an example of a communication system 4100 in accordance with some embodiments. In the example, the communication system 4100 includes a telecommunications network 4102 that includes an access network 4104, such as a radio access network (RAN), and a core network 4106, which includes one or more core network nodes 4108. The access network 4104 includes one or more access network nodes or base stations of various types, access network nodes 4110A and 4110B are depicted (which may be collectively referred to as network nodes 4110), or any other similar 3 Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 4104 may include more than one access network technology. The network nodes 4110 of access network 4104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 4112A, 4112B, 4112C, and 4112D (one or more of which may be generally referred to as UEs 4112) to the core network 4106 over one or more wireless connections.

[0110] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 4102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 4102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 4102, including one or more access network nodes 4110 and / or core network nodes 4108.

[0111] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near- real time control application (e.g.,xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0112] The network nodes 4110 facilitate direct or indirect connection of one or more UEs 4112 to the core network 4106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 4100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 4100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0113] The UEs 4112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 4110 and other communication devices. Similarly, the network nodes 4108, 4110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 4102) with the UEs 4112 and / or with other networknodes or equipment in the telecommunications network 4102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 4102. More specifically, UEs 4112 may send messages, data, and / or other signals to network nodes 4108, 4110 or other elements of the telecommunications network 4102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 4108, 4110 may send messages, data, and other signals to UEs 41122, other network nodes 4108, 4110, and other devices in telecommunications network 4102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 4112 by transmitting the message to an access network node 4110 that will then transmit the message to the intended UE 4112. Similarly, a core network node 108 may receive a particular message from a UE 4112 by receiving the message from an access network node 4110 that itself received the message from the UE 4112.

[0114] In the depicted example, the core network 4106 connects elements of the access network 4104 (e.g., one or more of the network nodes 4110) to one or more host computing systems, such as host 4116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 4106 includes one or more core network nodes (e.g., core network node 4108) of various types, one or more of which may be generally referred to as network nodes 4108. Network nodes 4108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 4108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF),Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0115] The host 4116 may be under the ownership or control of a service provider other than an operator or provider of the access network 4104 and / or the telecommunications network 4102. The host 4116 may be operated by the service provider or on behalf of the service provider. The host 4116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0116] As a whole, the communication system 4100 of Figure 6 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 4100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 4100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 4100 supporting different standards, protocols, or rule sets.

[0117] As one example, in certain embodiments, access network 4104 may contain some access network nodes 4110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 4110 support (or the same access network nodes 4110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 4102 may support multiple generations of related communication standards (e.g., 4G and 5G 3 GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0118] Telecommunications network 4102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 4102. For example, the telecommunications network 4102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0119] In some examples, one or more of the UEs 4112 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 4104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 4104. 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).

[0120] In the example, the hub 4114 communicates with the access network 4104 to facilitate indirect communication between one or more UEs (e.g., UE 4112C and / or 4112D) and network nodes (e.g., network node 4110B). In some examples, the hub 4114 may be a controller, router,content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 4114 may be a broadband router enabling access to the core network 4106 for the UEs. As another example, the hub 4114 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 4110, or by executable code, script, process, or other instructions in the hub 4114.

[0121] As another example, the hub 4114 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 4114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 4114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 4114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 4114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0122] The hub 4114 may have a constant / persistent or intermittent connection to the network node 4110B. The hub 4114 may also allow for a different communication scheme and / or schedule between the hub 4114 and UEs (e.g., UE 4112C and / or 4112D), and between the hub 4114 and the core network 4106. In other examples, the hub 4114 is connected to the core network 4106 and / or one or more UEs via a wired connection. Moreover, the hub 4114 may be configured to connect to an M2M service provider over the access network 4104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 4110 while still connected via the hub 4114 via a wired or wireless connection. In some embodiments, the hub 4114 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 4110B. In other embodiments, the hub 4114 may be a non-dedicated hub - that is, a device which is capable of operating to routecommunications between the UEs and network node 4110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0123] Figure 10 is another example of a communication system 4200 according to some embodiments. As used herein, the communication system 4200 includes multiple access points (APs) 4210 (with four exemplary APs 4210A, 4210B, 4210C, and 4210D being depicted) and multiple wireless devices, referred to in the context of communication system 4200 as stations (STAs) 4212 (referred to individually as STA 4212A, STA 4212B, STA 4212C, STA 4212D, and STA 4212E). STA 4212A is served by AP 4210A in a first basic service set (BSS) 4220A. STA 4210B and STA 4210C are served by AP 4210B in a second BSS, BSS 4220B. STA 4212D is served by AP 4210C in a third BSS, BSS 4220C. STA 4212E is served by AP 4210D in a fourth BSS, BSS 4220D. Stations 4212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, headmounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 4212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0124] Each of STAs 4212 may connect through a radio link to one of APs 4210. For example, depending on location or channel conditions experienced by a given STA 4212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention- based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0125] Each AP 4210 may provide data connectivity to STAs 4212 connected to a particular AP 4210. As illustrated, APs 4210 may be connected to a data network 4230. In this way, APs 4210 may also provide data connectivity between STAs 4212 and other entities, e.g., to one ormore servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 4212 and its serving AP 4210 may be used for providing various kinds of services to STA 4212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 4212 and / or on a device linked to STA 4212. By way of example, Figure 11 illustrates an application service platform 4232 provided in data network 4230. The application(s) executed on STA 4212 and / or on one or more other devices linked to STA 4212 may use the radio link for data communication with one or more other STA 4212 and / or the application service platform 4232, thereby enabling utilization of the corresponding service(s) at STA 4212.

[0126] Figure 11 shows a wireless device 4300, which may be configured to operate in communication system 4100 of Figure 9 or in communication system 4200 of Figure 10. The wireless device 4300 may be alternatively referred to as aUE 4300, like a UE 4112 within the context of communication system 4100, or as a station (STA) 4300 or as a non-access-point station (non-AP STA) 4300, like a STA 4212 within the context of the communication system 4200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of 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.

[0127] A wireless device 4300 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 4300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 4300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 4300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0128] In particular embodiments, wireless device 4300 includes processing circuitry 4302 that is operatively coupled via a bus 4304 to an input / output interface 4306, a power source 4308, a memory 4310, a communication interface 4312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 4300 may include all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one embodiment of wireless device 4300 to another. In general, in a particular embodiment of wireless device 4300, processing circuitry 4302, input / output interface 4306, power source 4308, memory 4310, and communication interface 4312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 4300. Further, certain embodiments of wireless devices 4300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0129] The processing circuitry 4302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 4310. The processing circuitry 4302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.);programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 4302 may include multiple central processing units (CPUs).

[0130] In the example, the input / output interface 4306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 4300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0131] In some embodiments, the power source 4308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 4308 may further include power circuitry for delivering power from the power source 4308 itself, and / or an external power source, to the various parts of wireless device 4300 via input circuitry or an interface such as an electrical power cable. Power source 4308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 4300 to which power is supplied.31

[0132] The memory 4310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 4310 includes one or more programs 4314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 4316. The memory 4310 may store, for use by wireless device 4300, any of a variety of various operating systems or combinations of operating systems.

[0133] The memory 4310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘ SIM card. ’ The memory 4310 may allow wireless device 4300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 4310, which may be or comprise a device-readable storage medium.

[0134] The processing circuitry 4302 may be configured to communicate with an access network or other network via or using the communication interface 4312. The communication interface 4312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 4322. The communication interface 4312 may include oneor more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 4318 and / or a receiver 4320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 4318 and receiver 4320 may be coupled to one or more antennas (e.g., antenna 4322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0135] In the illustrated embodiment, communication functions of the communication interface 4312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, 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. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0136] In particular embodiments, wireless device 4300 may provide an output of data captured via a sensor, through its communication interface 4312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 4300 can be communicated through a wireless connection to a network node via another wireless device 4300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), inresponse to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0137] As another example, wireless device 4300 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 4300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0138] Wireless device 4300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT 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 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. In particular embodiments, wireless device 4300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 4300 shown in Figure 11.

[0139] As yet another specific example, in anloT scenario, wireless device 4300 may represent a machine or other device that performs monitoring and / or measurements, and transmitsthe results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 4300 may in this case be a machine-to-machine (M2M) device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, wireless device 4300 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 4300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0140] In practice, any number of wireless devices 4300 may be used together with respect to a single use case. For example, a first wireless device 4300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 4300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 4300 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 wireless device 4300 can also include more than one of the functionalities described above. For example, wireless device 4300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0141] Figure 12 shows a network node 4400 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 telecommunications network. In accordance with respective embodiments, network node 4400 may be configured to operate in communication system 4100 of Figure 9, like network nodes 4108 or 4110, or in communication system 4200 of Figure 10, like an AP 4210 or a station 4212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an O-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0142] Network nodes 4400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 4400 may be a relay node or a relay donor node controlling a relay. Network nodes 4400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0143] Other examples of network nodes 4400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0144] In particular embodiments, network node 4400 includes a processing circuitry 4402, a memory 4404, a communication interface 4406, and a power source 4408. In general, in a particular embodiment of network node 4400, processing circuitry 4402, memory 4404, communication interface 4406, and power source 4408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 4400.

[0145] The network node 4400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the networknode 4400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 4400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 4404 or portions of memory 4404 for different RATs) and some components may be reused (e.g., a same antenna 4410 may be shared by different RATs). The network node 4400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 4400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 4400.

[0146] The processing circuitry 4402 may 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 components, such as the memory 4404, to provide network node 4400 functionality.

[0147] In some embodiments, the processing circuitry 4402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 4402 includes one or more of radio frequency (RF) transceiver circuitry 4412 and baseband processing circuitry 4414. In some embodiments, the RF transceiver circuitry 4412 and the baseband processing circuitry 4414 may 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 circuitry 4412 and baseband processing circuitry 4414 may be on the same chip or set of chips, boards, or units.

[0148] The memory 4404 may 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 the processing circuitry 4402. The memory 4404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 4402 and utilized by the network node 4400. The memory 4404 may be used to store any calculations made by the processing circuitry 4402 and / or any data received via the communication interface 4406. In some embodiments, the processing circuitry 4402 and memory 4404 is integrated.

[0149] The communication interface 4406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 4406 comprises port(s) / terminal(s) 4416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 4300 may be capable of wireless communication and communication interface 4406 may also include radio front-end circuitry 4418 that may be coupled to, or in certain embodiments a part of, an antenna 4410. Particular embodiments of radio front-end circuitry 4418 include filter(s) 4420 and amplifier(s) 4422. The radio front-end circuitry 4418 may be connected to an antenna 4410 and processing circuitry 4402. The radio front-end circuitry may be configured to condition signals communicated between antenna 4410 and processing circuitry 4402. The radio front-end circuitry 4418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 4418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination offilters 4420 and / or amplifiers 4422. The radio signal(s) may then be transmitted via the antenna 4410. Similarly, when receiving data, the antenna 4410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 4418. The digital data may be passed to the processing circuitry 4402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0150] In certain alternative embodiments, network node 4400 may be capable of wireless communication but does not include separate radio front-end circuitry 4418, instead, the processing circuitry 4402 includes radio front-end circuitry and is connected to the antenna 4410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 4412 is part of the communication interface 4406. In still other embodiments, the communication interface 4406 includes one or more ports or terminals 4416, the radio front-end circuitry 4418, and the RF transceiver circuitry 4412, as part of a radio unit (not shown), and the communication interface 4406 communicates with the baseband processing circuitry 4414, which is part of a digital unit (not shown).

[0151] The antenna 4410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 4410 may be coupled to the radio front-end circuitry 4418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 4410 is separate from the network node 4400 and connectable to the network node 4400 through one or more interfaces or ports.

[0152] The antenna 4410, communication interface 4406, and / or the processing circuitry 4402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 4400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 4410, the communication interface 4406, and / or the processing circuitry 4402 may be configured to perform some or all of the transmitting or sending operations describedherein as being performed by the network node 4400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0153] The power source 4408 provides power to the various components of network node 4400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 4408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 4400 with power for performing the functionality described herein. For example, the network node 4400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 4408. As a further example, the power source 4408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0154] Embodiments of the network node 4400 may include additional components beyond those shown in Figure 12 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, the network node 4400 may include user interface equipment to allow input of information into the network node 4400 and to allow output of information from the network node 4400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 4400.

[0155] Figure 13 is a block diagram illustrating a virtualization environment 4500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or morevirtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 4500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 4500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0156] Applications 4502 (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 4504 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 4506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 4508A and VM 4508B (which may be collectively referred to as VMs 4508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 4506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 4508.

[0157] The VMs 4508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 4506. Different embodiments of the instance of a virtual appliance 4502 may be implemented on one or more of VMs 4508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0158] In the context of NFV, each of the VMs 4508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 4508, and that part of hardware 4504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 4508 on top of the hardware 4504 and corresponds to an application 4502.

[0159] Hardware 4504 may be implemented in a standalone network node with generic or specific components. Hardware 4504 may implement some functions via virtualization. Alternatively, hardware 4504 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 4510, which, among others, oversees lifecycle management of applications 4502. In some embodiments, hardware 4504 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 4512 which may alternatively be used for communication between hardware nodes and radio units.

[0160] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or softwareneeded to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0161] 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.

[0162] Features of any of the examples or embodiments outlined above may be combined to create additional examples or embodiments without losing the intended effect. It should be understood that the description of an embodiment or example provided above is by way of example only, and various modifications could be made by one skilled in the art. Furthermore, one skilled in the art will recognise that numerous further modifications and combinations of various aspects are possible. Accordingly, the described aspects are intended to encompass all such alterations, modifications, and variations that fall within the scope of the appended claims.Example Embodiments

[0163] Below are provided a number of possible example embodiments under the present disclosure.Group A Embodiments

[0164] Embodiment 1: A method performed by a wireless device for Early Measurement Reporting (EMR), the method comprising: receiving a message including: an EMR configuration; a condition associated with an EMR procedure; and an indication to transition to an idle state or an inactive state; based on the condition and the EMR configuration, performing one or more measurements associated with the EMR procedure.

[0165] Embodiment 2:The method of any of the previous embodiments, further comprising: based on the indication, transitioning to the idle state or the inactive state.

[0166] Embodiment 3: The method of any of the previous embodiments, further comprising: transitioning to the idle state or the inactive state in response to receiving the message.

[0167] Embodiment 4:The method of any of the previous embodiments, further comprising: after transitioning to the idle state or the inactive state, performing the one or more measurements.

[0168] Embodiment 5:The method of any of the previous embodiments, further comprising, while the wireless device is in the idle state or the inactive state, performing the one or more measurements.

[0169] Embodiment 6:The method of any of the previous embodiments, wherein the message is received via RRC signaling.

[0170] Embodiment 7: The method of any of the previous embodiments, wherein the message comprises an RRC release message.

[0171] Embodiment 8:The method of any of the previous embodiments, further comprising: monitoring the condition.

[0172] Embodiment 9:The method of any of the previous embodiments, further comprising: determining the condition to be fulfilled; and based on the determination, performing the one or more measurements.

[0173] Embodiment 10:The method of any of the previous embodiments, wherein the condition comprises a timer.

[0174] Embodiment ll:The method of any of the previous embodiments, wherein the condition comprises an expiration of a timer.

[0175] Embodiment 12:The method of any of the previous embodiments, wherein the condition is fulfilled by an expiration of a timer.

[0176] Embodiment 13:The method of any of the previous embodiments, further comprising: starting a timer associated with the condition.

[0177] Embodiment 14:The method of embodiment 13, further comprising: upon transitioning to the idle state or the inactive state, starting the timer.

[0178] Embodiment 15:The method of embodiments 13 and 14, further comprising: stopping the timer upon transitioning to a connected state.

[0179] Embodiment 16:The method of embodiment 15, wherein the connected state comprises an RRC connected state.

[0180] Embodiment 17: The method of any of the previous embodiments, further comprising: determining the condition to be satisfied; and based on the determination, starting a timer associated with the EMR procedure.

[0181] Embodiment 18:The method of any of the previous embodiments, further comprising: based on performing the one or more measurements, starting a timer associated with the EMR procedure.

[0182] Embodiment 19: The method of any of the previous embodiments, wherein the condition is associated with leaving WLAN coverage.

[0183] Embodiment 20: The method of any of the previous embodiments, wherein the condition comprises leaving WLAN coverage.

[0184] Embodiment 21 : The method of any of the previous embodiments, wherein the WLAN coverage is computed based on the RS SI associated with the WLAN AP.

[0185] Embodiment 22: The method of any of the previous embodiments, wherein leaving the WLAN coverage comprises an RS SI associated with the WLAN AP being at or below a threshold RSSI.

[0186] Embodiment 23: The method of any of the previous embodiments, wherein the condition comprises an ongoing data transmission using the WLAN AP.

[0187] Embodiment 24:A method performed by a wireless device for Early Measurement Reporting (EMR), the method comprising: receiving a message including: an EMR configuration; a condition associated with an EMR procedure; and an indication to transition to an idle state or an inactive state; determining the condition is not satisfied; and based on the determination, preventing the performance of the EMR procedure.

[0188] Embodiment 25: The method of embodiment 24, wherein the condition comprises a timer expiry.

[0189] Embodiment 26: The method of embodiments 24 and 25, wherein determining the condition is not satisfied comprises determining the timer is running.

[0190] Embodiment 27: The method of embodiments 24 and 25, further comprising: determining the condition is satisfied; and based on the determination, performing the EMR procedure.

[0191] Embodiment 28: The method of embodiment 27, wherein determining the condition is satisfied comprises determining the timer is expired.

[0192] Embodiment 29: The method of any of the previous embodiments, further comprising: starting the timer upon transition to the idle state or the inactive state; and stopping the timer upon transition to a connected state.

[0193] Embodiment 30: The method of any of the previous embodiments, further comprising: starting a first timer associated with the condition; and upon expiration of the first timer, starting a second timer associated with the EMR procedure.

[0194] Embodiment 31:The method of any of the previous embodiments, further comprising: stopping the second timer upon transition to a connected state.

[0195] Embodiment 32:The method of any of the previous embodiments, further comprising: determining the condition is satisfied; and based on the determination, starting a timer associated with the EMR procedure.

[0196] Embodiment 33:The method of any of the previous embodiments, further comprising: transmitting, to a network node, the one or more measurements.

[0197] Embodiment 34:The method of any of the previous embodiments, further comprising: any of the operations of the Group A embodiments.

[0198] Embodiment 35:The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.Group B Embodiments

[0199] Embodiment 36:A method performed by a network node for providing a measurement configuration, the method comprising: transmitting, to a wireless device, a message including: an EMR configuration; a condition associated with an EMR procedure; and an indication to transition to an idle state or an inactive state; receiving, from the wireless device, one or more measurements associated with the EMR configuration.

[0200] Embodiment 37: The method of any of the Group B embodiments, wherein the indication is configured to trigger the wireless device to transition to the idle state or the inactive state.

[0201] Embodiment 38:The method of any of the Group B embodiments, wherein the message is transmitted via RRC signaling.

[0202] Embodiment 39: The method of any of the Group B embodiments, wherein the message comprises an RRC release message.

[0203] Embodiment 40: The method of any of the Group B embodiments, wherein the condition comprises a timer.

[0204] Embodiment 41: The method of any of the Group B embodiments, wherein the condition comprises an expiration of a timer.

[0205] Embodiment 42: The method of any of the Group B embodiments, wherein the condition is associated with leaving WLAN coverage.

[0206] Embodiment 43: The method of any of the Group B embodiments, wherein the condition comprises leaving WLAN coverage.

[0207] Embodiment 44: The method of any of the Group B embodiments, wherein the WLAN coverage is computed based on the RS SI associated with the WLAN AP.

[0208] Embodiment 45: The method of any of the Group B embodiments, wherein leaving the WLAN coverage comprises an RS SI associated with the WLAN AP being at or below a threshold RSSI.

[0209] Embodiment 46: The method of any of the Group B embodiments, wherein leaving the WLAN coverage comprises a reference signal strength and / or quality associated with the WLAN AP being at or below a threshold reference signal strength and / or quality.

[0210] Embodiment 47: The method of any of the Group B embodiments, wherein the condition comprises an ongoing data transmission using the WLAN AP.

[0211] Embodiment 48: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Group C Embodiments

[0212] Embodiment 49:A wireless device for measurement reporting, comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.

[0213] Embodiment 50:A network node for providing a measurement report configuration, the network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; a power source circuitry configured to supply power to the processing circuitry.

[0214] Embodiment 51: A wireless device for measurement reporting, the wireless device comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations 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 theprocessing 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; and a power source connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMSWhat is claimed is:

1. A method (600) performed by a wireless device (4300) for Early Measurement Reporting, EMR, the method comprising:receiving (602) an RRC message including an EMR configuration;transitioning (604), in response to the message, to an idle state or an inactive state; monitoring (606), after transitioning to the idle state or the inactive state, a trigger condition for starting performance of one or more measurements based on the EMR configuration; andwhile in the idle state or the inactive state, when the trigger condition is fulfilled, starting (608) performance of the one or more measurements based on the EMR configuration.

2. The method of claim 1 , wherein the trigger condition is based on a timer expiry.

3. The method of claim 1 or 2, further comprising:starting a first timer when entering the idle state or the inactive state; andstopping the first timer when transitioning to a connected state.

4. The method of any of claims 1 to 3, further comprising:upon expiry of the first timer, starting a timer controlling EMR.

5. The method of claim 1, wherein the trigger condition comprises leaving WLAN coverage.

6. The method of claim 5, wherein the WLAN coverage is computed based on a Received Signal Strength Indicator, RSSI, associated with a WLAN access point.

7. The method of claim 5 or 6, wherein the trigger condition further comprises an ongoing data transmission using the WLAN access point.

8. A method (700) performed by a wireless device (4300) for Early Measurement Reporting, EMR, the method comprising:receiving (702) an RRC message including an EMR configuration;transitioning (704), in response to the message, to an idle state or an inactive state; monitoring (706) a trigger condition for starting performance of one or more measurements based on the EMR configuration based on a first timer; andwhile the trigger condition is not fulfilled, postponing (708) a starting time to perform the one or more measurements based on the EMR configuration.

9. The method of claim 8, wherein the postponing is based on a second timer expiry.

10. The method of claim 9, further comprising:starting the second timer after entering the idle state or the inactive state upon expiry of the first timer; andstopping the second timer when transitioning to a connected state.

11. The method of any of claims 8 to 10, further comprising:upon expiry of the second timer, starting the first timer to monitor the trigger condition for starting performance of the one or more measurements.

12. The method of any of claims 8 to 11, wherein the trigger condition comprises being within WLAN coverage of a WLAN access point.

13. The method of claim 12, wherein the WLAN coverage is computed based on a Received Signal Strength Indicator, RSSI, associated with the WLAN access point.

14. The method of claim 12 or 13, wherein the trigger condition further comprises a lack of ongoing data transmission using the WLAN access point.

15. A method (500) performed by a network node (4400) for Early Measurement Reporting, EMR, the method comprising:transmitting (502), to a wireless device (4300), an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device (4300) while in an idle state or an inactive state; andreceiving (504), from the wireless device (4300), the one or more measurements performed based on the EMR configuration.

16. The method of claim 15, wherein the trigger condition is based on a timer expiry.

17. The method of claim 15 or 16, wherein the trigger condition comprises leaving WLAN coverage.

18. The method of claim 17, wherein the WLAN coverage is computed based on a Received Signal Strength Indicator, RSSI, associated with a WLAN access point.

19. The method of any of claims 15 to 18, wherein the RRC message comprises an RRC release message.

20. The method of any of claims 15 to 19, wherein the RRC message further includes an indication to transition to the idle state or the inactive state.

21. The method of any of claims 15 to 20, wherein the trigger condition further comprises an ongoing data transmission using a WLAN access point.

22. The method of any of claims 15 to 21, further comprising:based on the received one or more measurements, configuring carrier aggregation or dual connectivity for the wireless device (4300).

23. A method (800) performed by a network node (4400) for Early Measurement Reporting, EMR, the method comprising:transmitting (802), to a wireless device (4300), an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device (4300) based on a first timer while in an idle state or an inactive state; andreceiving (804), from the wireless device (4300), the one or more measurements performed based on the EMR configuration, wherein the wireless device (4300) postpones a starting time to perform the one or more measurements while the trigger condition is not fulfilled.

24. The method of claim 23, wherein the postponing is based on a second timer expiry.

25. The method of any of claims 23 to 26, wherein the trigger condition comprises being within WLAN coverage of a WLAN access point.

26. The method of claim 27, wherein the WLAN coverage is computed based on a Received Signal Strength Indicator, RSSI, associated with the WLAN access point.

27. The method of claim 27 or 28, wherein the trigger condition further comprises a lack of ongoing data transmission using the WLAN access point.

28. A wireless device (4300) for Early Measurement Reporting, EMR, the wireless device (4300) comprising:processing circuitry (4302) configured to perform the method (300) of any of claims 1 to 14; anda power source (4308) configured to supply power to the processing circuitry (4302).

29. A wireless device (4300) for Early Measurement Reporting, EMR, the wireless device (4300) comprising:processing circuitry (4302); anda memory (4310) storing instructions whereby the processing circuitry is operable to perform the steps of:receiving an RRC message including an EMR configuration;transitioning, in response to the message, to an idle state or an inactive state; monitoring, after transitioning to the idle state or the inactive state, a trigger condition for starting performance of one or more measurements based on the EMR configuration; andwhile in the idle state or the inactive state, when the trigger condition is fulfilled, starting performance of the one or more measurements based on the EMR configuration.

30. A wireless device (4300) for Early Measurement Reporting, EMR, the wireless device (4300) comprising:processing circuitry (4302); anda memory (4310) storing instructions whereby the processing circuitry is operable to perform the steps of:receiving an RRC message including an EMR configuration;transitioning, in response to the message, to an idle state or an inactive state; monitoring a trigger condition for starting performance of one or more measurements based on the EMR configuration based on a first timer; andwhile the trigger condition is not fulfilled, postponing a starting time to perform the one or more measurements based on the EMR configuration.

31. A network node (4400) for providing a measurement configuration, the network node (4400) comprising:processing circuitry (4402) configured to perform the method (500) of any of claims 15 to 27; anda power source (4408) configured to supply power to the processing circuitry (4402).

32. A network node (4400) for providing a measurement configuration, the network node (4400) comprising:processing circuitry (4402); anda memory (4404) storing instructions whereby the processing circuitry is operable to perform the steps of:transmitting, to a wireless device (4300), an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device (4300) while in an idle state or an inactive state; andreceiving, from the wireless device (4300), the one or more measurements performed based on the EMR configuration.

33. A network node (4400) for providing a measurement configuration, the network node (4400) comprising:processing circuitry (4402); anda memory (4404) storing instructions whereby the processing circuitry is operable to perform the steps of:transmitting, to a wireless device (4300), an RRC message including an EMR configuration, wherein the EMR configuration includes a trigger condition for starting performance of one or more measurements by the wireless device (4300) based on a first timer while in an idle state or an inactive state; andreceiving, from the wireless device (4300), the one or more measurements performed based on the EMR configuration, wherein the wireless device (4300) postpones a starting time to perform the one or more measurements while the trigger condition is not fulfilled.

Images