Triggers for controlling stored connected mode measurements for early measurement reporting

Abstract

A method performed by a wireless device. The method comprises while in a connected mode with respect to a communication network, performing one or more measurements of one or more frequencies. The method comprises after transitioning to an idle mode or inactive mode with respect to the communication network, and after occurrence of an event, deleting, discarding or releasing one or more of the measurements.

Description

[0001] Triggers for controlling stored Connected mode measurements for Early Measurement Reporting

[0002] TECHNICAL FIELD

[0003] Embodiments described herein related to methods and apparatuses for controlling stored connected mode measurements for early measurement reporting (EMR).

[0004] BACKGROUND

[0005] Early Measurement Reporting (EMR) in 5thGeneration (5G) New Radio (NR)

[0006] In 3rdGeneration Partnership Project (3GPP) Release 15 (Rel-15), the User Equipment (UE) is configured to perform and report measurements (e.g. on a neighbour cell in a frequency which is not the same as the frequency of the Primary Cell (PCell)) for the network to identify a Secondary Cell (SCell), or a Primary SCG Cell (PSCell) in the case of a Secondary Cell Group (SCG) in Dual Connectivity (DC), to be added and / or activated (so the UE operates in Carrier Aggregation (CA)). These measurements are configured when the UE is transitioned to Radio Resource Control (RRC) Connected, e.g. in an RRCResume message when transitioning from RRC Inactive or an RRCReconfiguration when transitioning from RRC Idle.

[0007] The issue which was later addressed by the so-called Early Measurement Report (EMR) was that when these measurements are reported, some of the bursty traffic was already received / transmitted via the PCell, i.e. it is sometimes too late to add and / or activate an SCell to distribute the traffic among additional frequencies.

[0008] EMR is a feature that was introduced in Release 16 (Rel-16) to aid the network in setting up carrier aggregation (CA) or Dual Connectivity (DC) after performing the state transition from RRC Idle mode or RRC Inactive state to RRC Connected mode. In this feature, a UE is configured (either via broadcast signalling or dedicated signalling) with a set of frequencies and cells to perform measurements which are of interest for the network in setting up the CA and / or DC. A UE in RRC Idle mode or RRC Inactive state can perform the measurements according to the configuration from the network provided, e.g. in an RRC Release message which the UE receives when the UE transitions from RRC Connected (RRC_CONNECTED) state to RRC Idle or RRC Inactive, or is broadcasted via system information (SI). Then, later on, upon performing the state transition from RRC Idle or RRC Inactive to RRC Connected, the UE provides the performed measurements to the network node in an EMR, e.g. in a RRC Resume Complete (RRCResumeComplete), or in a UE Information Response message.

[0009] According to the EMR solution in 3GPP Rel-16, the IDLE or INACTIVE measurements for EMR are configured, at least partly, through dedicated signalling (RRC message RRCRelease). The dedicated configuration includes a timer value (for timer T331, set with measIdleDuration-r16), indicating to the UE 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 UE starts the timer T331 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. These operations are described in 3GPP Technical Standard (TS) 38.300 v16.18.0 and 3GPP TS 38.331 v16.19.0. A procedure for early measurement is shown in Figure 1, involving UE 100 and a gNB 102. In step 104, the gNB transmita RRCRelease message to the UE, comprising a configuration for performing measurements in RRCJDLE, in MeasIdleConfig. In step 106, the UE transmits an RRCReleaseComplete message. In step 108, while in RRCJDLE and / or RRC NACTIVE, the UE performs measurements according to the configuration received in step 104. In step 112, the gNB transmits an RRCResume message to the UE; optionally, where the UE triggers resume, this step is preceded by step 110 in which the UE transmits an RRCResumeRequest message to the gNB. In step 114, the UE transmits an RRCResumeComplete message to the gNB, comprising the measurement result (or an indication of the measurement results) from the measurements performed in step 108.

[0010] Information about early measurement configuration can also be broadcast in System Information Block (SIB) 11 (SIB11) which contains, e.g., information about the frequency the UE should measure on. If the dedicated signalling does not include information about frequencies to perform measurements on, the UE performs the measurements according to the broadcast configuration in the cell where the UE is currently located. If the UE continues performing the measurements in RRC DLE / RRC NACTIVE even after T331 has expired (or has been stopped), the UE performs the measurements on the frequency / ies that is included in the broadcast configuration (in SIB11) for the cell. 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.

[0011] Enhancements to EMR after Rel-16

[0012] After Rel-16 there have been further discussions and enhancements to EMR. The Rel-16 EMR measurement duration is fully controlled by the T331 timer. Due to the uncertainty of how long the UE stays in Idle or Inactive mode, the time when the UE finishes the early measurements can be long before UE transition into the connected mode, which means that there is a risk that measurements for EMR are outdated and do not reflect the radio conditions when the UE is trying to resume or setup an RRC connection. An enhancement for Release 18 (Rel-18) is to introduce a validity duration timer so the UE only reports fresh measurement results.

[0013] Another enhancement for Rel-18 is to report cell-reselection measurements. Since measurement gaps are not available during Idle / lnactive mode, the UE must performmeasurement on frequency basis. The EMR configuration allows up to 8 carriers for UE to perform measurement when there are overlapping carriers with the Idle / lnactive inter-frequency measurement, the UE can report these measurement results to the network.

[0014] SUMMARY

[0015] There currently exist certain challenge(s). Despite its benefits, EMR in NR was specified but not widely implemented in the industry due to some limitations. The need to perform additional inter-frequency measurements in RRC Idle mode or RRC Inactive state consumes UE battery, which should be preserved as much as possible when the UE is in Idle or Inactive state.

[0016] In addition, the quality (accuracy) of the Idle mode or RRC Inactive state measurements is inferior to the RRC Connected mode measurements, and thus the network node cannot trust the EMR reported by the UE completely. Considering that the problem of efficient resource utilisation remains in 6thGeneration (6G) and must be addressed, there is an interest to introduce a solution for the problem with the first release of Sixth Generation (6G), with as many UEs as possible supporting it, e.g. effectively making the feature mandatory.

[0017] One way to improve EMR for 6G is to enable the UE to store one or more measurements performed while the UE is in RRC Connected for later EMR. The UE, upon transitioning to RRC Idle mode or RRC Inactive state from RRC Connected mode, stores one or more measurements performed while the UE was in RRC Connected mode (denoted “stored Connected measurements” or “stored Connected mode measurements”). The UE can transmit a report including at least one of the one or more stored Connected measurements to the network node upon subsequently transitioning from RRC Idle mode or RRC Inactive state to RRC Connected mode.

[0018] While this approach provides benefits in that the UE does not have to perform additional measurements when it transitions to RRC Idle or RRC Inactive and the UE is still able to indicate to the network in EMR one or more measurements of one or more frequencies / carriers / cells for an efficient setup of CA and / or DC, in some scenarios it may be beneficial to have further control on these measurements. In particular, the “stored Connected measurements” may become outdated by the time that the UE needs to report them to the network. This may lead to wrong decisions at the network side. For example, suppose the UE stored a measurement for a frequency f1 which indicates that this frequency has a cell that is very good. However, when the UE needs to report that measurement for EMR later in time, that measurement for EMR is outdated, e.g., because the situation of that frequency has changed for the worse. Based on the EMR, the network may set up CA and / or DC for f 1 , but that is no longer a good frequency.

[0019] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. This disclosure proposes a UE method in which the UE, upon transitioning toRRC Idle mode or RRC Inactive state from RRC Connected mode, stores one or more measurements performed while the UE was in RRC Connected mode (with these stored measurements being denoted “stored Connected measurements” or “stored Connected mode measurements”). Then, while the UE is in RRC Idle or RRC Inactive and has one or more stored Connected mode measurements, the UE releases (i.e. discards, removes, deletes) the “stored Connected measurements” upon detection of one or more events. The one or more events can include any of the following events:

[0020] expiry of a timer;

[0021] UE mobility, e.g. cell reselection, movement, etc.;

[0022] the network requests only certain measurements available at the UE;

[0023] a change in the broadcasted parameter associated to the validity of the stored connected measurements.

[0024] The method can further comprise, upon deleting the one or more stored Connected measurements, performing at least one measurement based on an EMR measurement configuration (e.g. IdleMeasConfig), with that measurement configuration either being received upon transitioning to RRC Idle or RRC Inactive, or being obtained via a system information (SI) message.

[0025] Further, according to the method, when the UE is transitioning to RRC Idle or RRC Inactive (e.g. an RRC Release with or without suspend configuration, or a Suspend message), or via a message transmitted to the UE some time prior to the UE’s transition to RRC Idle or RRC Inactive state (e.g. an RRC Reconfiguration), the UE is configured to store and / or to NOT delete (i.e. retain) one or more stored Connected measurements. In some cases, the UE is configured to store and / or to NOT delete (i.e. retain) the one or more stored Connected measurements by receiving a parameter (and / or information element (IE)) indicating this in a message which indicates to the UE to transition to RRC Idle or RRC Inactive. In other cases, the network may configure the UE at an earlier occasion (e.g. in the Connected measurement configuration), in a message received earlier than the message which indicates to the UE to transition for RRC Idle or RRC Inactive state, e.g. using another RRC message. This early configuration could ensure that the UE does not discard measurements as soon as they are reported to the network, but requires the UE to retain them for some time. Without such an early proactive configuration, there is a risk that the UE will not have any Connected measurements to store when it enters RRC Idle or RRC Inactive state.

[0026] According to a first aspect of the invention, there is provided a method performed by a wireless device. The method comprises while in a connected mode with respect to a communication network, performing one or more measurements of one or more frequencies. The method comprises after transitioning to an idle mode or inactive mode with respect to thecommunication network, and after occurrence of an event, deleting, discarding or releasing one or more of the measurements.

[0027] According to some embodiments, the method comprises receiving, from a Radio Access Network, RAN, node, a measurement configuration. The step of performing one or more measurements is performed according to the received measurement configuration.

[0028] According to some embodiment, the measurement configuration indicates one or more frequencies on which the one or more measurements are to be performed.

[0029] According to some embodiments, the measurement configuration comprises one or more of: an indication of one or more frequencies on which the one or more measurements are to be performed; an indication of one or more cells on which the one or more measurements are to be performed; an indication of one or more beams on which the one or more measurements are to be performed; an indication of when a measurement report is to be transmitted to a Radio Access Node, RAN, node in the communication network; an indication of content of a measurement report to be transmitted to a RAN node in the communication network; an indication of whether the wireless device is to store or retain the one or more measurements when transitioning to the idle or inactive mode; an indication of a time period T 1 that the wireless device is to store or retain the one or more measurements; an indication that the one or more measurements are to be reported to the communication network as Early Measurement Reporting, EMR; indications on a per measurement object basis; indications on a per measurement identifier basis; and an indication of a maximum number of measurements to store.

[0030] According to some embodiments, the method comprises prior to transitioning to the idle mode or inactive mode, storing the one or more measurements of the one or more frequencies as a first set of measurements.

[0031] According to some embodiments, the method comprises prior to transitioning to the idle mode or inactive mode, deleting, discarding or releasing one or more of the one or more measurements to form a second set of measurements.

[0032] According to some embodiments, the method comprises after transitioning to the idle mode or inactive mode and prior to the event occurring, deleting, discarding or releasing one or more of the one or more measurements to form a second set of measurements.

[0033] According to some embodiments, deleting, discarding or releasing one or more of the one or more measurements after occurrence of a predetermined event comprises deleting, discarding or releasing one or more of the one or more measurements in the second set of measurements to form a third set of measurements.

[0034] According to some embodiments, the method comprises after deleting, discarding or releasing the one or more of the one or more measurements following occurrence of the event, sending any remaining measurements to a RAN node.

[0035] According to some embodiments, the remaining measurements are sent to the RAN nodethat provided the wireless device with a measurement configuration for performing the one or more measurements.

[0036] According to some embodiments, the remaining measurements are sent to a different RAN node to the RAN node that provided the wireless device with a measurement configuration for performing the one or more measurements.

[0037] According to some embodiments, the remaining measurements are sent to a RAN node after transitioning to the connected mode with the RAN node.

[0038] According to some embodiments, the event is one or more of: a mobility event for or by the wireless device; expiry of a timer; measurement(s) exceeding a permitted age; the communication network requesting only certain measurements stored at the wireless device; a time elapsed since the one or more measurements were performed exceeds a threshold; and / or a change in a broadcasted parameter from the communication network.

[0039] According to some embodiments, the event is any of: a cell reselection; a change of cell; a change in the quality of the cell the wireless device is camping on; a change in the quality of any measured frequency or cell; a change of best beam and / or Synchronisation Signal Block, SSB, for a cell the wireless device is camping on;

[0040] a change of best beam and / or SSB the wireless device is camping on;

[0041] a change of Radio Access Network, RAN, area;

[0042] a RAN Area Update;

[0043] a change of RAN Notification Area;

[0044] a RAN Notification Area Update;

[0045] a change of Tracking Area;

[0046] a Tracking Area Update;

[0047] a change of Registration Area;

[0048] a Registration Area Update;

[0049] a change of Public Land Mobile Network, PLMN;

[0050] the wireless device loses coverage or goes out of coverage; and

[0051] a change in a geographical location of the wireless device larger than a threshold.

[0052] According to some embodiment, the event is expiry of a timer or a time elapsed since the one or more measurements were performed exceeding a threshold. The timer is started, or the time elapsed monitored from, any of: when the wireless device transitions to idle mode; when the wireless device transitions to inactive mode; when the wireless device receives a message transitioning the wireless device to idle mode or inactive mode; when the wireless device receives a reporting configuration; a start of a timer for starting Early Measurement Reporting, EMR, measurements according to an EMR configuration; when the performed one or more measurements are stored; and when the one or more measurements are performed.

[0053] According to some embodiments, the event is expiry of a timer. The timer is stopped whenany of: the wireless device transmits measurements to the communication network; the wireless device transitions to connected mode;the wireless device prepares to resume or to setup connected mode; the wireless device sends a message for transitioning to connected mode; the wireless device triggers a cell reselection; the wireless device receives a setup message; the wireless device receives a resume message; the wireless device transmits a resume complete message; the wireless device receives a connected mode measurement configuration; the wireless device receives an indication in system information for stopping the timer; the wireless device transmits one or more of the one or more measurements; the wireless device receives a request to report measurements; the wireless device reporting the measurements for Early Measurement Reporting, EMR; the wireless device indicates to the communication network that measurements are available; the wireless device receives a message instructing it to delete, discard or release one or more of the one or more measurements; the wireless device receives a message instructing it to release, delete, deconfigure or deactivate a measurement configuration used to configure the performance of the one or more measurements; or the wireless device receives a message instructing it to reconfigure, modify or replace a measurement configuration used to configure the performance of the measurements.

[0054] According to some embodiment, the event is expiry of a timer or a time elapsed since the measurements were performed exceeding a threshold. The timer value or threshold is: received in a message transitioning the wireless device to idle mode or inactive mode; received in a configuration or reconfiguration message while the wireless device is in connected mode; received in a message that includes a measurement configuration used to configure the performance of the one or more measurements; received in the measurement configuration; received in a message providing a reporting configuration to the wireless device; received in a broadcasted message; received in a System Information, SI, message; or preconfigured in the wireless device.

[0055] According to some embodiment, the event is a change in a broadcasted parameter from the communication network. The broadcasted parameter is any of: a flag indicating whether any of the measurements are valid; a value of a validity timer relating to the storage of measurements; a parameter indicating what measurements are to be performed; and a parameter indicating what measurements are to be reported.

[0056] According to a second aspect of the invention, a method performed by a RAN node is provided. The method comprises sending, to a wireless device, information for use by the wireless device in determining if one or more measurements stored by the wireless device are to be deleted, discarded or released.

[0057] According to some embodiments, the information is for use by the wireless device in determining if one or more measurements obtained when the wireless device was in a connected mode with respect to a communication network are to be deleted, discarded or released after thewireless device transitions to an idle mode or inactive mode with respect to the communication network.

[0058] According to some embodiment, the information is a timer value or value for a time period. According to some embodiments, the timer value or value for the time period is sent to the wireless device in any of: a message transitioning the wireless device to idle mode or inactive mode; a configuration or reconfiguration message sent to the wireless device while the wireless device is in connected mode; a message that includes a measurement configuration used to configure the performance of the one or more measurements by the wireless device; a measurement configuration used to configure the performance of the measurements by the wireless device; a message providing a reporting configuration to the wireless device; a broadcasted message; ora System Information, SI, message.

[0059] According to some embodiments, the information is any of: a flag indicating whether any of the measurements are valid; a value of a validity timer relating to the storage of measurements; a parameter indicating what measurements are to be performed; a parameter indicating what measurements are to be reported.

[0060] According to a third aspect of the invention, a computer program product is provided. The computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of the embodiments of the first aspect of the invention and / or any of the embodiments of the second aspect of the invention.

[0061] According to a fourth aspect of the invention, a wireless device is provided. The wireless device is configured to perform the method of any of the embodiments of the first aspect of the invention.

[0062] According to a fifth aspect of the invention, a wireless device is provided. The wireless device comprises a processor and a memory, said memory containing instructions executable by said processor whereby said wireless device is operative to perform the method of any of the embodiments of the first aspect of the invention.

[0063] According to a sixth aspect of the invention, a RAN node is provided. The RAN node is configured to perform the method of any of the embodiments of the second aspect of the invention.

[0064] According to a seventh aspect of the invention, a RAN node is provided. The RAN node comprises a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to perform the method of any of the embodiments of the second aspect of the invention.

[0065] According to an eighth aspect of the invention, a wireless device is provided. The wireless device comprises processing circuitry configured to cause the user equipment to perform any ofthe steps of any of the embodiments of the first aspect of the invention; and power supply circuitry configured to supply power to the processing circuitry.

[0066] According to a ninth aspect of the invention, a RAN node is provided. The RAN node comprises processing circuitry configured to cause the RAN node to perform any of the steps of any of the embodiments of the second aspect of the invention; and power supply circuitry configured to supply power to the processing circuitry.

[0067] According to a tenth aspect of the invention, a wireless device is provided. The wireless device comprises one or more antennas; a 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 embodiments of the first aspect of the invention; an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the wireless device.

[0068] Certain embodiments may provide one or more of the following technical advantage(s). Most UEs transition from RRC Idle mode or RRC Inactive state to RRC Connected mode within a short duration of transitioning to the corresponding RRC Idle mode or RRC Inactive state. Thus, any measurements performed by the UE while being in RRC Connected mode before transitioning to RRC Idle mode or RRC Inactive state might still be of relevance by the time that the UE comes back to RRC Connected mode.

[0069] However, as noted above, it is possible that the “stored Connected measurements” may have become outdated before the UE needs to report them to the network, which can lead to wrong decisions at the network side. The techniques described herein can provide that the UE discards the stored Connected measurements when the UE detects that these measurements may lead to the wrong decisions at the network side if they were reported. For example, the UE can discard those measurements when the UE detects a movement that could mean there is a change in radio conditions for the cell / frequency of the performed measurements. Alternatively or in addition, the UE can discard the measurements if they have been stored for too long, since the likelihood that the measurements are outdated is higher.

[0070] BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:

[0072] Fig. 1 is a signalling diagram illustrating a procedure for early measurements;

[0073] Fig. 2 is a flow chart illustrating a method performed by a user equipment in accordancewith some embodiments;

[0074] Figs. 3, 4 and 5 are signalling diagrams that illustrate the reporting of Connected measurements a UE has stored when it transitioned to Idle or Inactive;

[0075] Fig. 6 is a flow chart illustrating a method performed by one or more RAN nodes in accordance with some embodiments;

[0076] Fig. 7 shows an example of a communication system in accordance with some embodiments;

[0077] Fig. 8 shows a wireless device in accordance with some embodiments;

[0078] Fig. 9 shows a network node in accordance with some embodiments; and

[0079] Fig. 10 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0080] DETAILED DESCRIPTION

[0081] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0082] Some of the terminology and generalisations used herein are discussed below.

[0083] References to the UE storing / reporting / transmitting / discarding / deleting “measurements” should be understood as referring to the UE storing / reporting / transmitting / discarding / deleting measurement results.

[0084] A measurement may be performed on a network entity, such as a cell, a frequency, a beam (e.g. of a cell), a reference signal (e.g. of a cell), a synchronization signal (e.g. of a cell), a sounding signal (e.g. of a cell), a Synchronization Signal Block (SSB), a Channel State Information-Reference Signal (CSI-RS), a Mobility Reference Signal, etc. A measurement may represent the radio properties, such as quality of that entity, such as a Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR). Examples of measurements may be found in TS 38.215 v16.7.0.

[0085] The terms “state” and “mode” are used interchangeably and should be interpreted as being equivalent in this disclosure.

[0086] Reference is made to Idle and Inactive as states defined in 3GPP TS 38.331 in which the UE is optimised for energy savings, and network reachability is via paging monitoring. However, the techniques described herein are applicable to any other state optimised for energy savings which may be defined for 6G, with one or more characteristics similar to Idle or Inactive states defined for 5G.

[0087] The term “Early Measurement Reporting” and its abbreviation “EMR” are used throughout this disclosure. EMR is a term that was introduced for a particular concept / functionality in 5G, and EMR is also used herein to refer to the same / similar concept / functionality being used in 6G(or a later generation of mobile wireless networks). However, it is noted that a different name or term may be used or adopted for the 6G implementation of the EMR concept / functionality. As such, references herein to “Early Measurement Reporting “EMR” should not be understood as referring just to 5G, but also to implementations of the EMR concept / functionality in 6G and / or other generations of mobile wireless network standards.

[0088] The terms “RRC Idle”, “RRC Inactive” and “RRC Connected”, or “Idle”, “Inactive” and “Connected” are used herein to refer to states (e.g. 6G states) with the same or similar properties as “RRCJDLE, “RRCJNACTIVE” and “RRC_CONNECTED” in 5G.

[0089] The terms “Connected measurements”, “Connected mode measurements” or “Connected state measurements” are used interchangeably herein to refer to measurements performed by a UE in a Connected state / RRC Connected state, or measurement results obtained from measurements performed by a UE in a Connected state / RRC Connected state.

[0090] In this disclosure, references to “releasing stored Connected measurements” means that the UE discards or deletes the stored Connected measurements or otherwise considers the stored Connected measurements as invalid and not to be reported to the network. In the context of stored measurements, the terms “release”, “discard”, “delete” are used interchangeably herein.

[0091] The terms “frequency”, “carrier”, “frequency band”, and “carrier frequency” are used interchangeably herein.

[0092] Embodiments of methods performed by a UE in accordance with the techniques presented herein are explained below with reference to Fig. 2.

[0093] The method performed by a UE may be as follows:

[0094] In step 201, the UE receives a measurement configuration (also referred to as “first configuration” or “connected measurement configuration”) from a first network node while the UE is in RRC Connected mode (or a 6G equivalent). The first network node may be a network node in a Radio Access Network (RAN) of a communication network, such as a base station, an eNB, a gNB, or a 6G RAN node. The measurement configuration indicates a first set of frequencies to be measured.

[0095] In step 202, the UE performs a first set of measurements associated to the first set of frequencies while the UE is in RRC Connected mode (or the 6G equivalent). At least some of the first set of measurements may be retained / stored by the UE, and the stored / retained measurements may be denoted “stored first set of measurements”. At least some of the first set of measurements can be retained / stored for potential later use for EMR (or the 6G equivalent).

[0096] In step 203, the UE transitions to RRC Idle mode or RRC Inactive state (or a 6G equivalent). Transitioning to RRC Idle mode or RRC Inactive state may be performed in response to the reception of a RRC message, e.g. a RRC message that comprises an EMR configuration (e.g. IdleMEasConfig). In some cases, after transitioning to RRC Idle mode or RRC Inactive state, thewireless device may transition to the other one of the Idle mode or Inactive state.

[0097] In step 204, which is optional, as denoted by step 204 being shown with a dashed outline, the UE retains / stores a second set of measurements (denoted “stored Connected measurements”, or “stored second set of measurements”). The second set of measurements are amongst the stored first set of measurements, i.e. the second set of measurements may be a subset of the first set of measurements. Alternatively, all of the first set of measurements may continue to be stored after the transition to RRC Idle mode or RRC Inactive state, which means that the second set of measurements is the same as / identical to the first set of measurements, and step 204 does not need to be performed.

[0098] In step 205, upon detecting an event while in RRC Idle mode or in RRC Inactive state, the UE releases (or deletes) at least one of the one or more stored Connected measurements.

[0099] In some embodiments, upon deleting one or more stored Connected measurements in step 205, the UE may perform one or more measurements according to the EMR configuration (e.g. IdleMeasConfig).

[0100] It will be appreciated that steps 203 and 204 could occur in the order shown in Fig. 2, or they could occur at the same time, or in the opposite order to that shown in Fig. 2 (i.e. step 204 could be performed followed by step 203). In the latter case, this means that the second set of measurements is stored prior to the transition from RRC Connected to RRC Idle or Inactive, and after the transition in step 203 the second set of measurements is retained until the event according to step 205 occurs. In some embodiments, an occurrence of step 204 may be performed before step 203 in order to store the second set of measurements prior to the transition, and after the transition from RRC Connected to RRC Idle or Inactive occurs in step 203, a second occurrence of step 204 may be performed in which one or more of the stored measurements is discarded or deleted. Further deletion / discarding / releasing of one or more stored measurements may occur in step 205 on the occurrence of an event.

[0101] A UE mobility event may be used to lead to the deletion of one or more of the second set of measurements. An expiry of a time may be used to lead to the deletion of one or more of the second set of measurements. The measurement(s) in the second set of measurement exceeding a permitted age (e.g., a time elapsed since the measurement(s) is obtained exceeds a threshold) may be used to lead to the deletion of one or more of the second set of measurements. The network requesting only certain measurements available at the UE may be used to lead to the deletion of one or more of the second set of measurements. A change in a broadcast parameter by the first network node, where the broadcasted associated to the validity of the stored Connected measurements may be used to lead to the deletion of one or more of the second set of measurements. Any one or more of the following events may be used to lead to the deletion of one or more of the second set of measurements (noting that 5G-specific terminology is beingused, the same or different terminology may be used in 6G):

[0102] a UE mobility event;

[0103] the expiry of a timer;

[0104] the measurement(s) in the second set of measurements exceed a permitted age (i.e. the time elapsed since the measurement(s) were obtained exceeds a threshold); the network requests only certain measurements available at the UE; or a change in a broadcasted parameter by the first network node, where the broadcasted is associated to the validity of the stored Connected measurements. Thus, in a specific embodiment of step 205, upon expiry of a timer while in RRC Idle state or in RRC Inactive state, the UE releases (or deletes) at least one of the one or more stored Connected measurements.

[0105] In another specific embodiment of step 205, upon a UE mobility event while in RRC Idle state or in RRC Inactive state, the UE releases (or deletes) at least one of the one or more stored Connected measurements.

[0106] In another specific embodiment of step 205, the network may request certain measurements from the UE. The UE may have other stored measurements in addition to those requested by the network, in which the UE may release or delete the stored measurements that the network did not request. For example, the UE may have stored measurements on frequencies fO, f 1 , f2..., and the network may request the UE to report measurements on fO. In this case, on receiving this request (event), the UE deletes the measurements on f1 and f2 as they were not requested by the network.

[0107] In another specific embodiment of step 205, upon a change in the broadcasted parameter associated to the validity of the stored Connected measurements, the UE releases (or deletes) at least one of the one or more stored Connected measurements.

[0108] A UE mobility event may relate to a cell reselection. A UE mobility event may relate to a change of cell. A UE mobility event may relate to a change in the quality of the cell the UE is camping on. A UE mobility event may relate to a change in the quality of any measured frequency or cell. A UE mobility event may relate to a change of the best beam and / or Synchronization Signal Block (SBB) for the cell the UE is camping on. A UE mobility event may relate to a change of the best beam and / or SSB the UE is camping on. A UE mobility event may relate to a change of RAN area. A UE mobility event may relate to a RAN Area Update. A UE mobility event may relate to a change of RAN Notification Area. A UE mobility event may relate to a change of Tracking Area. A UE mobility event may relate to a Tracking Area Update. A UE mobility event may relate to a change of Registration Area. A UE mobility event may relate to a change of Public Land Mobile Network (PLMN). A UE mobility event may relate to the UE loses coverage or goes out of coverage. A UE mobility event may relate to a change in the geographic location of the UE. A UE mobility event may relate to any one or more of the following (again noting that 5G-specific terminology is being used, the same or different terminology may be used in 6G): a cell reselection;

[0109] a change of cell;

[0110] a change in the quality of the cell the UE is camping on;

[0111] a change in the quality of any measured frequency or cell;

[0112] a change of the best beam and / or Synchronisation Signal Block (SSB) for the cell the UE is camping on;

[0113] a change of the best beam and / or SSB the UE is camping on;

[0114] a change of RAN area;

[0115] a RAN Area Update;

[0116] a change of RAN Notification Area;

[0117] a RAN Notification Area Update;

[0118] a change of T racking Area;

[0119] a Tracking Area Update;

[0120] a change of Registration Area;

[0121] a Registration Area Update;

[0122] a change of Public Land Mobile Network (PLMN);

[0123] the UE loses coverage or goes out of coverage; and

[0124] a large enough change in the geographical location of the UE.

[0125] In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurements when the UE transitions to Idle. In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurements when the UE transitions to Inactive. In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurements when the UE receives a message transitioning the UE to Idle or Inactive. In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurements when the UE receives an EMR configuration, e.g., IdleMeasConfig. In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurements when the start of timer for starting EMR measurements according to the EMR configuration. In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurements when the measurement(s) whose result(s) is(are) stored is(are) performed. In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurements when the measurement result(s) which is(are) stored is(are) obtained. In the case of the event being the expiry of a timer or the age of the measurements, the UE may start the timer or start to count the age of the measurementswhen one or more of the following occurs (noting that 5G-specific terminology is being used, the same or different terminology may be used in 6G):

[0126] the UE transitions to Idle;

[0127] the UE transitions to Inactive;

[0128] the UE receives a message transitioning the UE to Idle or Inactive;

[0129] the UE receives an EMR configuration, e.g. IdleMeasConfig;

[0130] the start of timer for starting EMR measurements according to the EMR configuration; the storing of the Connected measurements;

[0131] the measurement(s) whose result(s) is(are) stored is(are) performed; or the measurement result(s) which is(are) stored is(are) obtained.

[0132] In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE transmits a set of measurements to the network, i.e. when the UE performs EMR. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE transitions to Connected. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE prepares to resume or to setup, e.g. transmission of RRC Resume Request message or RRC Setup Request. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE sends a message for transitioning to RRC Connected. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE triggers a cell reselection. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives a RRC Setup message. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives a RRC Setup message. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE transmits a RRC Resume Complete. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives a connected mode measurement configuration, e.g. in a RRC Resume message. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives an indication in system information for stopping the timer. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE transmits one or more stored Connected measurements, e.g., in EMR. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives a request to report EPR, e.g., in an RRC Resume, RRC Setup or UE Information Request message. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE reporting for EMR (e.g., in a RRC Resume Complete and / or UE Information message) the second set of Connected measurements. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE indicates to the network that measurement(s) for EMR is(are) available in the UE, e.g., in an RRC Resume Complete, an RRC Setup Complete or a RRCReestablishment Complete message, or a 6G message corresponding to the RRCResumeComplete, RRCSetupComplete, or RRCReestablishmentComplete message in 5G. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE sends one or more stored Connected measurement(s) to the network, e.g., in an RRC Resume Complete, an RRCSetupComplete or UE Information Response message, e.g. a 6G message corresponding to the RRCResumeComplete, RRCSetupComplete or UElnformationResponse message in 5G. In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives a message instructing it to release / delete one or more stored Connected measurement(s), e.g. a dedicated signalling message, e.g. a dedicated RRC message (applicable in embodiments where the timer is started while the UE is in RRC Connected state). In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives a message instructing it to release / delete / deconfigure / deactivate the EMR configuration, e.g. a dedicated signalling message, e.g. a dedicated RRC message (applicable in embodiments where the timer is started while the UE is in RRC Connected state). In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of the UE receives a message instructing it to reconfigure / modify / replace the EMR configuration, e.g. a dedicated signalling message, or a dedicated RRC message, e.g. where the reconfiguration, modification or replacement of the EMR configuration impacts how deletion of stored Connected measurements is triggered / controlled (this is applicable to embodiments where the timer is started while the UE is in RRC Connected state). In embodiments where the event is related to a timer, the UE may stop the timer on the occurrence of any of the following (noting that 5G-specific terminology is being used, the same or different terminology may be used in 6G):

[0133] the UE transmits a set of measurements to the network, i.e. when the UE performs EMR;

[0134] the UE transitions to Connected;

[0135] the UE prepares to resume or to setup e.g. transmission of RRC Resume Request message or RRC Setup Request;

[0136] the UE sends a message for transitioning to RRC Connected;

[0137] the UE triggers a cell reselection;

[0138] the UE receives a RRC Setup message;

[0139] the UE receives a RRC Resume message;

[0140] the UE transmits a RRC Resume Complete;

[0141] the UE receives a connected mode measurement configuration, e.g. in a RRC Resume message;

[0142] the UE receives an indication in system information for stopping the timer; the UE transmits one or more stored Connected measurements, e.g. in EMR;the UE receives a request to report EMR, e.g. in an RRC Resume, RRC Setup or UE Information Request message;

[0143] the UE reporting for EMR (e.g. in a RRC Resume Complete and / or UE Information message) the second set of Connected measurements;

[0144] the UE indicates to the network that measurement(s) for EMR is(are) available in the UE, e.g. in an RRC Resume Complete, an RRC Setup Complete or a RRC Reestablishment Complete message, or a 6G message corresponding to the RRCResumeComplete, RRCSetupComplete or RRCReestablishmentComplete message in 5G;

[0145] the UE sends one or more stored Connected measurement(s) to the network, e.g. in an RRC Resume Complete, RRC Setup Complete or UE Information Response message, e.g. a 6G message corresponding to the RRCResumeComplete, RRCSetupComplete or UElnformationResponse message in 5G;

[0146] the UE receives a message instructing it to release / delete one or more stored Connected measurement(s), e.g. a dedicated signalling message, e.g. a dedicated RRC message (applicable in embodiments where the timer is started while the UE is in RRC Connected state);

[0147] the UE receives a message instructing it to release / delete / deconfigure / deactivate the EMR configuration, e.g. a dedicated signalling message, e.g. a dedicated RRC message (applicable in embodiments where the timer is started while the UE is in RRC Connected state); or

[0148] the UE receives a message instructing it to reconfigure / modify / replace the EMR configuration, e.g. a dedicated signalling message, or a dedicated RRC message, e.g. where the reconfiguration, modification or replacement of the EMR configuration impacts how deletion of stored Connected measurements is triggered / controlled (this is applicable to embodiments where the timer is started while the UE is in RRC Connected state).

[0149] In embodiments where the event is related to a timer, the values for the timer may be obtained by the UE in a RRC message transitioning the UE to Idle or Inactive state, e.g. RRC Suspend, RRC Release (with suspend Configuration), RRC Release (without suspend Configuration). In embodiments where the event is related to a timer, the values for the timer may be obtained by the UE in an RRC Reconfiguration, e.g. while the UE was in Connected state. In embodiments where the event is related to a timer, the values for the timer may be obtained by the UE in a message that includes the Connected mode measurement configuration, e.g. IE MeasConfig. In embodiments where the event is related to a timer, the values for the timer may be obtained by the UE in the Connected mode measurement configuration, e.g. IE MeasConfig. In embodiments where the event is related to a timer, the values for the timer may be obtainedby the UE in a message providing EMR configuration information to the UE. In embodiments where the event is related to a timer, the values for the timer may be obtained by the UE via a broadcasted message, e.g. a System Information (SI) message. In embodiments where the event is related to a timer, the values for the timer may be obtained by the implementation of the UE, for example in accordance with a timer value defined in a standard, e.g. a 3GPP standard. In embodiments where the event is related to a timer, the value for the timer may be obtained by the UE in one or more of the following ways:

[0150] in a RRC message transitioning the UE to Idle or Inactive state, e.g. RRC Suspend, RRC Release (with suspend Configuration), RRC Release (without suspend Configuration);

[0151] in an RRC Reconfiguration, e.g. while the UE was in Connected state;

[0152] in a message that includes the Connected mode measurement configuration, e.g. IE MeasConfig;

[0153] in the Connected mode measurement configuration, e.g. IE MeasConfig; in a message providing EMR configuration information to the UE;

[0154] via a broadcasted message, e.g. a System Information (SI) message; or by the implementation of the UE, for example in accordance with a timer value defined in a standard, e.g. a 3GPP standard.

[0155] Embodiments of the various steps shown in Fig. 2 will now be described in more detail. For the steps in which the UE is configured to perform one or more actions described below, the UE is described as being configured by a RAN node (a network node in the radio access network (RAN) of a communication network). A RAN node can be any of a network node, a base station, an eNB, a gNB, a network entity in the RAN, a RAN function, etc.

[0156] Step 201 - Receiving a measurement configuration

[0157] In step 201 , the UE receives a measurement configuration from a first network node while the UE is in RRC Connected mode (or a 6G eguivalent). The RRC Connected mode may also be denoted RRC_CONNECTED state, or an RRC state for which procedures are optimised for data transmissions / reception by the UE. The measurement configuration is also referred to as “Connected measurement configuration” or “MeasConfig”.

[0158] The measurement configuration configures the UE to perform measurements while the UE is in RRC Connected mode. That is, a UE in RRC Connected state is configured to perform one or more measurements while in the RRC Connected state, such as Radio Resource Management (RRM) measurements, which may also be referred to as Layer 3 (L3) measurements, or Channel State Information (CSI) measurements.

[0159] A measurement configuration that the UE may receive while in RRC Connected may includeparameter(s) indicating on what frequencies (or more generally, frequency-related information) and / or cell(s) the UE should perform measurements. The measurement configuration that the UE may receive while in RRC Connected may include parameter(s) indicating when to transmit a measurement report while in RRC Connected. The measurement configuration that the UE may receive while in RRC Connected may include parameter(s) indicating what to include in the measurement report to be transmitted while the UE is in RRC Connected. The measurement configuration that the UE may receive while in RRC Connected may include an indication or information indicating that the UE shall store one or more of the configured and performed measurements, and keep the stored measurements when transitioning to a RRC Idle or a RRC Inactive state. That is, for each of the concerned measurements, the UE shall store the obtained measurement result of the measurement as soon as the measurement result has been obtained, i.e. as soon as the measurement has been performed and keep it stored if / when transitioning to RRC Idle or RRC Inactive state (irrespective of whether it has been reported to the network while the UE is in the RRC Connected state). The indication may further instruct the UE that such stored measurements may be reported to the network as EMR. The measurement configuration that the UE may receive while in RRC Connected may include an indication indicating that the UE shall store one or more of the configured and performed measurements for a certain time period, denoted T1 (irrespective of whether the UE has reported the performed measurements or not to the network) and keep them stored if transitioning to RRC Idle or RRC Inactive state before the concerned measurements have been discarded. The measurement configuration that the UE may receive while in RRC Connected may include an indication of a maximum number, N, of Connected measurements to store and keep when / if the UE transits from RRC Connected state to RRC Idle or RRC Inactive state. This may, e.g., instruct the UE to only store the N latest measurements even if the certain time periods governing the storage time for earlier measurements have not expired. That is, when the UE has performed N measurements after a preceding measurement was performed and stored, the UE can discard the stored preceding measurement irrespective of how long it has been stored. The indication may further instruct the UE that such stored measurements may be reported to the network as EMR.

[0160] A measurement configuration that the UE may receive while in RRC Connected may include, but is not limited to, one or more of the following:

[0161] 1) Parameter(s) indicating on what frequencies (or more generally, frequency-related information) and / or cell(s) the UE should perform measurements.

[0162] 2) Parameter(s) indicating when to transmit a measurement report while in RRC Connected.

[0163] 3) Parameter(s) indicating what to include in the measurement report to be transmitted while the UE is in RRC Connected.

[0164] 4) An indication or information indicating that the UE shall store one or more of the configured and performed measurements, and keep the stored measurements when transitioning toa RRC Idle or a RRC Inactive state. That is, for each of the concerned measurements, the UE shall store the obtained measurement result of the measurement as soon as the measurement result has been obtained, i.e. as soon as the measurement has been performed and keep it stored if / when transitioning to RRC Idle or RRC Inactive state (irrespective of whether it has been reported to the network while the UE is in the RRC Connected state). The indication may further instruct the UE that such stored measurements may be reported to the network as EMR.

[0165] 5) An indication indicating that the UE shall store one or more of the configured and performed measurements for a certain time period, denoted T 1 (irrespective of whether the UE has reported the performed measurements or not to the network) and keep them stored if transitioning to RRC Idle or RRC Inactive state before the concerned measurements have been discarded. The indication can further instruct the UE that such stored measurements may be reported to the network as EMR.

[0166] One option of the indication 5) is for the indication / information to further comprise an indication of a time period or a timer value, T 1 , indicating for how long the UE should store / retain an obtained measurement result which is subject to the measurement configuration (i.e. obtained according to the received measurement configuration).

[0167] Another option of the indication 5) is for the indication / information to further comprise a value for T1. The value for T1 can be the length of the time period T1, or the start value of a timer T1 (which counts down to zero from T1), or the value at which a timer T1 expires (where the timer counts from zero up the value T1).

[0168] Another option of the indication 5) is for the indication to indicate storage of measurements in both RRC Idle and RRC Inactive state.

[0169] An alternative option of the indication 5) is for the indication to indicate storage of measurements only in RRC Idle state.

[0170] Another alternative option of the indication 5) is for the indication to indicate storage of measurements only in RRC Inactive state.

[0171] Another alternative option of the indication 5) is for the connected measurement configuration to explicitly indicate whether measurements should be stored in RRC Idle state, in RRC Inactive state, or in both RRC Idle and RRC Inactive state.

[0172] In yet another option of the indication 5), although the instruction to the UE to store one or more measurements for later continued storage when transitioning to RRC Idle or RRC Inactive state can be conveyed in a configuration message (e.g. an RRCReconfiguration message or a corresponding message in 6G), a later message from the network, e.g. a message transitioning the UE to RRC Idle or RRC Inactive state (e.g. an RRCRelease message or a corresponding 6G message) or another (re)configuration message (e.g. an RRCReconfiguration message or a corresponding 6G message) may refine this instruction. For example, the later message from thenetwork may indicate which ones of the stored Connected measurements, or indicate criteria for selecting which ones of the stored Connected measurements, to retain (i.e. keep stored) when transitioning to RRC Idle or RRC Inactive state.

[0173] The indication according this paragraph 5 may be configured in different granularities. As one option the indication may be configured per measurement object (e.g. SSB frequency). That means the UE stores as Connected measurements the measurements the UE has performed for that indicated measurement object, e.g. associated measld(s) with that indicated measurement object. The indication may be, e.g., a parameter within the MeasObject IE. As another option the indication can be configured per measurement identifier (i.e. per MeasIdToAddMod). A measld is associated to quantities the UE shall report and these are the quantities, also associated to a measurement object, that shall be stored.

[0174] 6) An indication of a maximum number, N, of Connected measurements to store and keep when / if the UE transits from RRC Connected state to RRC Idle or RRC Inactive state. This may, e.g., instruct the UE to only store the N latest measurements even if the certain time periods governing the storage time for earlier measurements have not expired. That is, when the UE has performed N measurements after a preceding measurement was performed and stored, the UE can discard the stored preceding measurement irrespective of how long it has been stored.

[0175] a. In one option of the indication 6), while the UE is in Connected state, and before the UE is configured to perform Connected measurements, the UE reports a UE capability to the network indicating the value N. That value may be set per measld and / or per measurement object (or frequency).

[0176] Various properties of the timer or time period T 1 can be one or more of the following:

[0177] The time period T1 may start when the UE performs the measurement and keeps running if the UE transits from RRC Connected state to RRC Idle or RRC Inactive state before T 1 expires.

[0178] The time period T 1 may start when the UE transits from RRC Connected state to RRC Idle or RRC Inactive state.

[0179] The time period T 1 may start when the UE transits from RRC Connected state to RRC Idle or RRC Inactive state and the configuration may further include an indication of a second time period, T2, which governs how long the UE may store a performed measurement before it transits from RRC Connected state to RRC Idle or RRC Inactive state. That is, if T2 expires before the UE transitions from RRC Connected state to RRC Idle or RRC Inactive state, the UE deletes the stored measurement(s), while when the UE is in RRC Idle or RRC Inactive state (after transitioning from RRC Connected state), it deletes the stored measurement(s) if / when T1 expires. T 1 may be started for a measurement when the UE has performed the measurement,or when the UE performs the measurement.

[0180] T 1 can be started when the UE transitions from RRC Connected to RRC Idle or RRC Inactive state, and the configuration can explicitly or implicitly indicate to the UE that it should keep the stored Connected measurements until it transitions to RRC Idle or RRC Inactive state, and thereafter for an additional time period T 1.

[0181] T 1 may be started for a measurement when the UE has performed the measurement, or when the UE performs the measurement, and the configuration can further indicate an additional time period T2 which starts when the UE transitions from RRC Connected state to RRC Idle or RRC Inactive state.

[0182] o In one variant, the UE may store the Connected measurements until both T1 and T2 has expired (or the UE has reported the stored Connected measurements as EMR).

[0183] o In another variant, the UE may store the Connected measurements until either T1 or T2 has expired (whichever expires first), or the UE has reported the stored Connected measurements as EMR.

[0184] T1 may be started for a measurement when the UE has transitioned from RRC Connected to RRC Idle or RRC Inactive state, and the configuration can further indicate an additional time period, T3, that indicates how long the UE may store the Connected measurement while remaining in RRC Connected state.

[0185] The UE may be configured to (or mandated / instructed to) retain the stored Connected measurements even after a time period or timer for the retaining of the Connected measurements (e.g. T1 and / or T2) has expired if the UE has not yet obtained any other measurement results to report to the network as EMR (e.g. results of measurements performed in RRC Idle or RRC Inactive state).

[0186] In some embodiments the timer or time period T1 may be used to control the storage / retaining of Connected measurements in RRC Connected state and the indication of the timer or time period T1 corresponds to a timer value. In that case, when the UE reports a measurement while in Connected state (e.g. for a given measld and / or measObjectld) the UE starts a timer set to the value T1. In these embodiments:

[0187] when the timer expires while the UE is still in RRC Connected state the UE deletes the stored Connected measurements;

[0188] when the UE enters RRC Idle or RRC Inactive while the timer is running, the UE stops the timer;

[0189] when the UE triggers another measurement report based on a measld for which the UE has stored measurements, the UE restarts the timer. Alternatively, the UE first stops the timer and starts it.

[0190] In some embodiments, the timer or time period T1 may be used to control thestorage / retaining of Connected measurements in RRC Connected state and the indication of the timer or time period T 1 corresponds to a timer value. In these embodiments, when the UE reports a measurement while in RRC Connected state (e.g. for a given measld and / or measObjectld), for the last time, the UE starts a timer set to the value T1. The term “for the last time” here means that the UE has reported a measurement and as long as it needs to keep reporting (e.g. in case of event triggered periodic reporting) the UE does not start the timer. In other words, the UE starts the timer (with the value T1) when the last measurement is reported for that given measld. For example, when there are a maximum number of measurements to be transmitted for a given measld, the UE starts the timer when that number is reached for a given measld. In these embodiments:

[0191] when the timer expires while the UE is still in RRC Connected state the UE deletes the stored Connected measurements;

[0192] when the UE enters RRC Idle or RRC Inactive while the timer is running, the UE stops the timer.

[0193] In this disclosure, the frequency-related information the UE is configured with in the Connected measurement configuration may correspond to, or include Synchronization Signal Block (SSB) frequency (e.g. center frequency and / or frequency interval / range, frequency bandwidth) on which the UE needs to perform measurements. In this disclosure, the frequency-related information the UE is configured with in the Connected measurement configuration may correspond to, or include subcarrier spacing. In this disclosure, the frequency-related information the UE is configured with in the Connected measurement configuration may correspond to, or include frequency band. In this disclosure, the frequency-related information the UE is configured with in the Connected measurement configuration may correspond to, or include frequency information of a reference signal (e.g. center frequency and / or frequency interval / range, frequency bandwidth) on which the UE needs to perform measurements e.g. a CSI-Reference Signal (CSI-RS) frequency. In this disclosure, the frequency-related information the UE is configured with in the Connected measurement configuration may correspond to, or include one or more of the following:

[0194] Synchronization Signal Block (SSB) frequency (e.g. center frequency and / or frequency interval / range, frequency bandwidth) on which the UE needs to perform measurements;

[0195] subcarrier spacing;

[0196] frequency band;

[0197] frequency information of a reference signal (e.g. center frequency and / or frequency interval / range, frequency bandwidth) on which the UE needs to perform measurements e.g. a CSI-Reference Signal (CSI-RS) frequency.

[0198] The frequency-related information (and parameters associated to it, e.g. SSB frequencyand subcarrier spacing) may be included in a measurement object (MO) configuration (e.g. denoted MO configuration, or simply MO), or any other structure or Information Element (IE) in which parameters for frequency related information are configured.

[0199] The measurement configuration the UE receives while in RRC Connected, which is denoted “Connected measurement configuration”, or “MeasConfig”, may be received in a MeasConfig IE.

[0200] The MeasConfig IE may be used to configure layer 3 (L3) measurements; The MeasConfig IE may be used to configure both layer 1 (L1) and L3 measurements in a unified measurement configuration used for a 6G UE.

[0201] The connected measurement configuration may include a configuration associated to a particular frequency (e.g. SSB frequency fO, configured in a measurement object) or a particular cell could include an explicit indicator indicating whether the corresponding frequency’s or cell’s measurements are to be stored as part of the measurements subject to EMR. Such an indicator could be configured per frequency (i.e. , per measurement object), or per cell on a frequency. It should be noted that the corresponding measurements are also part of the connected mode measurement report triggering and / or connected mode measurements reporting configurations.

[0202] An example implementation in the 3GPP standards is given below, with the example being based on 3GPP TS 38.331 v18.4.0. New text is indicated by underlined bold font). In this example, the network has the option of including an indicator, applicableForEMR, in the measurement object. When this field is configured, the UE realises that the measurements on the corresponding frequency are applicable for EMR, i.e., the UE has to store the corresponding measurements on this MO upon transitioning to RRC Idle mode or RRC Inactive state.

[0203]

[0204]

[0205] The connected measurement configuration may include a configuration of one or more measurement objects (e.g. in a MeasObjectToAddModList IE), where each configured MO is associated to a reporting configuration (reportConfigld) and measurement identifier (measld).

[0206] the UE may determine whether or not to store one or more measurement(s) associated to a measurement object based on an indication in the measurement object;

[0207] the UE may determine whether or not to store one or more measurement(s) associated to a measurement identifier based on an indication associated to the measurement identifier.

[0208] The connected measurement configuration may be received in an RRC message. The RRC message may be according to any of the following:

[0209] an RRC message the UE receives while the UE is in RRC Connected;

[0210] an RRC Reconfiguration message (e.g. RRCReconfiguration);

[0211] a message for resuming a suspended RRC connection, e.g. an RRCResume message; or

[0212] a message for transitioning the UE from RRC Idle state to RRC Connected state, e.g. an RRCSetup message.

[0213] The connected measurement configuration may include a timer value for the timer controlling the release / deletion of the stored Connected measurements. The UE sets the timer to the received value and starts the timerwhen it enters Idle or Inactive, with the stored Connected measurements being kept in storage while the timer is running, and deleted when the timerexpires. In other words, the timer value determines for how long the UE stores the stored Connected measurements while the UE is in Inactive or Idle.

[0214] Step 202 - Performing a first set of measurements

[0215] In step 202, the UE performs a first set of measurements associated to the first set of frequencies while the UE is in RRC Connected mode (or the 6G equivalent). At least some of the first set of measurements may be retained / stored by the UE, and the stored / retained measurements are denoted “stored first set of measurements”. At least some of the first set of measurements may be retained / stored for potential later use for EMR (or the 6G equivalent).

[0216] The UE may perform the RRM measurements on a first set of frequencies (e.g. fO, f 1 , f2 frequencies) as configured in the Connected measurement configuration, and generate a first set of measurements. Frequencies that are configured in the Connected measurement configuration are referred to herein as “configured frequencies” or “configured first set of frequencies”). The UE may store all or a subset of the first set of measurements which are to be reported in RRC Connected state and / or which may be kept stored when / if the UE transitions from RRC Connected state to RRC Idle or RRC Inactive state.

[0217] The first set of measurements may include measurement(s) associated to a measurement quantity, such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), etc., on one or more cells for the first set of frequencies.

[0218] The first set of measurements may include a first derivative and / or a second derivative of the RSRP, RSRQ, SINR, etc. measurements on one or more cells on the configured first set of frequencies.

[0219] The first set of measurements may include predicted measurements of the measurement quantities, such as predictions of RSRP, predictions of RSRQ, predictions of SINR, on one or more cells for the first set of frequencies.

[0220] The predictions may be time-domain prediction(s), i.e. estimates of a measurement quantity for a given cell and / or frequency in a future time instance.

[0221] The predictions may be spatial-domain prediction(s), i.e. estimates of a measurement quantity for a given cell and / or frequency based on measurements on another cell in that frequency.

[0222] The predictions may be frequency-domain prediction(s), i.e. estimates of a measurement quantity for a given cell on a frequency of the first set based on measurements on a cell on another frequency of the first set of frequencies.

[0223] The predictions may be a combination of two or more of the above types of predictions.

[0224] The first set of measurements may include beam measurements on one or more cells forthe first set of frequencies.

[0225] The first set of measurements may include one or more beam measurements on a reference signal (RS) and / or a synchronisation signal(s) to be received on a frequency of the first set of frequencies. For example, the one or more beam measurements may correspond to measurements on SSBs of a cell e.g. Synchronisation Signal (SS)-RSRP, SS-SINR, SS-RSRQ as defined in 3GPP TS 38.215 since Release 15, or a corresponding standard specification for 6G. For example, the one or more beam measurements may correspond to measurements on CSI-RSs of a cell e.g. CSI-RSRP, CSI-SINR, CSI-RSRQ as defined in 3GPP TS 38.215 since Release 15, or a corresponding standard specification for 6G. For example, the one or more beam measurements may be measurements on Mobility Reference Signals (MRSs). For example, the one or more beam measurements may be measurements on Connected mode SSBs that are configured for Connected mode measurements on SSBs.

[0226] The first set of frequencies may comprise one or more serving frequencies. The first set of frequencies may be associated to a single measurement object for the Primary Cell (PCell) the UE is connected to. The first set of frequencies may be associated to a single measurement object for the Primary Secondary Cell Group (SCG) Cell (PSCell) the UE is connected to while in Dual Connectivity (DC). The first set of frequencies may be associated to a single measurement object, for a Special Cell (SpCell) of a Master Cell Group (MCG) or SCG.

[0227] The first set of frequencies may comprise one or more neighbour frequencies, e.g. frequencies for which the SSB frequency and / or subcarrier spacing differs from the SSB frequencies and / or subcarrier spacings of serving cells.

[0228] Step 203 - Transition from RRC Connected mode to RRC Idle mode or RRC Inactive state In step 203, the UE transitions from the RRC Connected mode to the RRC Idle mode or RRC Inactive state. This transition may be upon, or shortly after, reception of an RRC message from the network, such as a RRCRelease message in 5G, or a 6G equivalent, that explicitly indicates the UE is to perform such a transition. Alternatively, the transition may be triggered via an autonomous UE action. The transition may be performed using a RRCRelease message or any other equivalent message.

[0229] As noted, the UE may transition from RRC Connected to RRC Idle upon reception of an RRC message, such as an RRC Release message (e.g. not including a suspend configuration).

[0230] Alternatively, the UE may transition from RRC Connected to RRC Idle upon reception of an RRC Reconfiguration message that includes an indication that the UE is to transition to RRC Idle.

[0231] In another alternative, the UE may transition from RRC Connected to RRC Inactive upon reception of a RRC Reconfiguration message that includes an indication that the UE is to transition to RRC Inactive. Alternatively, the UE may transition from RRC Connected to RRC Idle upon reception of a RRC message, such as a RRC Release message that includes a suspendconfiguration (or a RRC Suspend).

[0232] A RRC message that transitions the UE, or that causes the UE to transition, from RRC Connected to RRC Idle or RRC Inactive upon reception of the RRC message may also include an EMR configuration. Upon deleting the stored Connected measurements in step 205, the UE performs one or more measurements, while in RRC Idle or RRC Inactive, based on the EMR configuration.

[0233] Step 204 - Store a second set of measurements

[0234] In step 204, the UE may store a second set of measurements upon entering the RRC Idle mode or the RRC inactive state. The second set of measurements may be the same as, or a subset of, the first set of measurements the UE has performed in RRC Connected. For example, the second set of measurements may be measurements on a second set of frequencies, where the second set of frequencies (e.g. f1 , f2) is a subset of the first set of frequencies (e.g. fO, f1 , f2) that the first set of measurements relate to. For example, the second set of measurements may be measurements on a set of measurement quantities, such as RSRP, RSRQ, SINR, radio quality, radio power, an interference measurement, etc. (e.g. for a given cell and / or frequency), where the set of measurement quantities is a subset of quantities the UE has available (e.g. for a given cell and / or frequency). For example, the second set of measurements may be measurements on a set of cells in the first set of frequencies, where the first set of cells is a subset of the cells in the first set of frequencies for which the UE has measurements available. For example, the second set of measurements may be measurements associated to a subset of measurement identifiers (measld(s)) the UE is configured with. For example, a UE may be configured with measurements for measld=1, measld=2, measld=3, measld=4, and the UE may store measurements for measld=1 and measld=2, which are associated to the same or a different reporting configuration and / or the same or different measurement objects. Here, the UE may receive in the message that indicates the transition to Idle or Inactive an indication of the measurement identifiers for which the associated measurements are to be stored.

[0235] In step 204, the UE may store / retain the available first set of measurements as part of the second set of measurements. Such measurements may include one or more of the measurements on serving cells, measurements of neighbour cells on the serving frequencies, measurements of neighbour cells on non-serving frequencies, etc. Here, the term “serving cell” refers to the set of serving cells as configured while the UE is in RRC Connected mode.

[0236] In some embodiments, the UE stores one or more measurements performed on the PCell, as part of the second set of measurements.

[0237] In some embodiments, the UE stores one or more measurements on one or more previously configured SCell(s) as part of the second set of measurements. The UE may in any case have to measure the PCell, since that is likely the cell the UE would select for camping on whentransitioning to RRC Idle or RRC Inactive, but the SCell measurements would otherwise be lost and measurements would have to be performed again for EMR, which may be a waste and consume battery. The UE may store the strongest neighbour cell per configured SCell frequency as part of the second set of measurements. In some cases, the UE may use any of the RSRP, RSRQ or SINR as the ‘sorting quantity’ to decide the strongest cell on a frequency.

[0238] The UE may store in the second set of measurements one or more measurements on the second set of frequencies. The second set of frequencies is a subset of the first set of frequencies explicitly indicated in the RRC message that caused the UE to transition to RRC Idle or RRC Inactive. The second set of frequencies may be indicated to the UE by reception of one or more measurement object identifiers associated to the UE’s measurement configuration in Connected mode, e.g. the MeasConfig or the UE’s variable in which the MeasConfig is stored. The second set of frequencies may be indicated to the UE by reception of one or more serving cell indexes (or identifiers) associated to the UE’s configuration while the UE was in Connected mode, e.g. in case the UE is configured to store measurements of the UE’s serving cells while the UE was in Connected mode.

[0239] The UE may be informed which of the RRC Connected mode measurements on certain frequencies and / or cells are also applicable to EMR (i.e. which are stored as part of the second set of measurements upon entering RRC idle or RRC inactive). The UE may be informed via information received in the RRC message that transitions the UE to RRC Idle or RRC Inactive (e.g. a RRCRelease message). For example, the UE might be configured with Frequency 1, Frequency 2, Frequency 3 and Frequency 4, each associated to a measurement object while being in RRC Connected mode, and the UE can then receive a RRC Release message in which the network node indicates that Frequency 2- and Frequency 3-related measurements are applicable. The UE then stores any available Frequency 2- and Frequency 3-related measurements as the second set of measurements.

[0240] The UE may only store those measurements from the first set of measurements that are explicitly configured as candidates for EMR. Such a configuration might be received as described above with respect to the embodiments of step 201. The UE may use such a configuration to filter the first set of measurements and generate the second set of measurements, with the so-generated second set of measurements being stored. For example, if the first network node had configured an indicator in the MO that indicates the measurements on the corresponding MO to be relevant for EMR, then the UE can store any available measurements in the first set of measurements on the cells in the corresponding MO as part of the second set of measurements. In another example, if the first network node had configured a list in the MO, with the list indicating the measurements on the particular list of cells on the corresponding MO that are relevant for EMR, the UE can store any measurements in the first set of measurements on the corresponding cells in the corresponding MO as part of the second set of measurements.The stored second set of measurements may consist of the measurements in the first set of measurements that were associated to the cells that were the serving cells before transitioning to the RRC Idle mode or RRC Inactive state. In such an embodiment, there may not be an explicit configuration indicating which measurements of the first set of measurements are to be stored as the second set of measurements by the UE. The UE may filter the first set of measurements for the measurements of the serving cell(s), and store them as the second set of measurements.

[0241] The stored second set of measurements may consist of the measurements in the first set of measurements that were associated to the strongest cells on each of the configured frequencies before transitioning to the RRC Idle mode or RRC Inactive state. Different measurement quantities could be used to determine the strongest cell on a configured frequency. For example, any of RSRP measurements, RSRQ measurements, and SINR measurements can be used to determine the strongest cell (or the cell which has the best quality, e.g. the highest RSRP, RSRQ or SINR) on a frequency. In some embodiments the stored second set of measurements may consist of the first set of measurements associated to the serving cells before transitioning to the RRC Idle mode or RRC Inactive state. In such an embodiment, there is no explicit configuration associated to which of the first set of measurements are to be stored as the second set of measurements by the UE and the UE filters for the serving cells’ measurements from the first set of measurements and stores them as the second set of measurements.

[0242] In some embodiments, the stored second set of measurements consists of the first set of measurements associated to the strongest cells on each of the configured frequencies before transitioning to the RRC Idle mode or RRC Inactive state. Different measurement quantities could be used to determine the strongest cell on a configured frequency. For example, in some embodiments RSRP measurements are used for determining the strongest cell, in some embodiments RSRQ measurements are used for determining the strongest cell on a frequency and in some embodiments SINR measurements are used for determining the strongest cell on a frequency.

[0243] The second set of measurements stored by the UE in step 204 could further comprise other measurements that are readily available to the UE. For example, the second set of measurements can include any of: a Timing Advance (TA) value, or a last-reported Channel Quality Indicator (CQI) re port- related information such as Rank Indicator (Rl), a Precoding Matrix Indicator (PMI), and / or CSI RSRP / SINR values.

[0244] It is to be noted that some of the measurements for the second set of measurements may be derived based on measurements in the first set of measurements. For example, as described above with respect to the embodiments of step 202, the first set of measurements may consist of RSRP, RSRQ and / or SINR measurements, and the UE may derive the first and / or second order derivatives of these measurements. These derivatives may be stored as part of the second set of measurements. That is, step 204 may include the UE deriving new measurements from thefirst set of measurements that are to be included in the second set of measurements.

[0245] In some embodiments, when the UE transitions to RRC Inactive, the UE may store the second set of measurements in a UE Inactive Access Stratum (AS) Context, which is stored when the UE’s connection is suspended, and restored when the connection is resumed.

[0246] In addition to storing a measurement (e.g. RSRP of a cell in a given frequency), the UE may also store one or more parameters (e.g. from the Connected measurement configuration) associated with the stored measurement. For example, the parameters include a measurement identifier associated with the measurement. For example, the parameters include a measurement object identifier associated with the measurement. For example, the parameters include one or more parameters of the measurement object associated with the measurement. These may be, e.g., parameters within the MO such as SSB frequency (e.g. absolute radio-frequency channel number (ARFCN) value), subcarrier spacing, etc. The reason is that the network node that receives these measurements (e.g. a second network node, different from the first network node that sends the measurement configuration) may not recognise the measConfig (e.g. in case the UE transitions from Idle to Connected) so that the UE needs to indicate which frequency and / or cell and / or beam (SSB, CSI-RS) the measurement is associated with.

[0247] In some embodiments, in addition to storing a measurement (e.g. RSRP of a cell in a given frequency), the UE may also store one or more parameters (e.g. from the Connected measurement configuration) associated with the stored measurement when the UE transitions to RRC Idle from RRC Connected.

[0248] 205 - Delete one or more of the second set of measurements on occurrence of an event

[0249] In step 205, upon detecting an event while in Idle or Inactive state, the UE deletes (releases, discards, etc.) at least one of the one or more stored Connected measurements (i.e. one or more of the stored second set of measurements).

[0250] In some embodiments, the event is configured at the UE. The event may be configured per measurement, e.g. per measID, in the connected measurement configuration. Then, the UE controls the deletion in step 205 per measld. For example, the event would be associated to a particular measld. In an alternative approach, the event can be configured or defined / specified per measurement object / frequency, e.g. per measObjectID, in the connected measurement configuration. In this case, the UE can control the deletion in step 205 per measObjectld. For example, the event would be associated to a particular measObjectld.

[0251] As described in further detail below, the event may comprise a UE mobility event. The event may comprise an expiry of a timer or a time period. The event may comprise the network requests only certain measurements available at the UE. The event may comprise a change in a broadcast parameter associated to the validity of the stored Connected measurements where at least part of the configuration is provided to the UE via broadcast transmission, e.g., broadcasted systeminformation. As described in further detail below, the event may comprise any of:

[0252] a UE mobility event;

[0253] an expiry of a timer or a time period;

[0254] the network requests only certain measurements available at the UE; and a change in a broadcasted parameter associated to the validity of the stored Connected measurements where at least part of the configuration is provided to the UE via broadcast transmission, e.g. broadcasted system information.

[0255] The UE may monitor for at least two of these types of events, e.g. two or three of the above listed types of events. In some embodiments, when at least one of these events occurs (e.g. the event is triggered or fulfilled) the UE deletes the stored Connected measurements according to step 205. In other embodiments, the UE only deletes the stored Connected measurements according to step 205 when all of the monitored events have occurred (e.g. when all events have been triggered or fulfilled).

[0256] Event: the network requests only certain measurements available at the UE - In some embodiments, the UE’s deletion of stored Connected measurements in step 205 may be based on a request from the network to report certain available stored measurements. Specifically, if the UE has additional stored Connected measurements that do not match what the network requests, the UE deletes these Connected measurements. In further embodiments, this principle is also applied to stored measurements that were performed when the UE was in RRC Idle or RRC Inactive state, e.g. measurements performed in accordance with an EMR configuration.

[0257] Event: timer expiry or time period expiry - In these embodiments the UE starts a timer or otherwise starts monitoring a time period or age of the stored measurements (noting that the term “timer” is used herein to refer to both the timer and the time period / age), and when the timer expires, while the UE is in Idle or Inactive, the UE deletes the ‘stored Connected measurements’, i.e. the second set of measurements.

[0258] The timer (or time period) may be, or correspond to, timer / time period T1, T2 or T3 with properties (and associated UE behaviour) as described above with reference to step 201.

[0259] The UE may start the time or start to count the time / age of the measurements when the UE transitions to Idle. The UE may start the time or start to count the time / age of the measurements when the UE transitions to Inactive. The UE may start the time or start to count the time / age of the measurements when the UE receives a message transitioning the UE to Idle or Inactive. The UE may start the time or start to count the time / age of the measurements when the UE receives an EMR configuration, e.g. IdleMeasConfig. The UE may start the time or start to count the time / age of the measurements when the start of timer for starting EMR measurements according to the EMR configuration. The UE may start the time or start to count the time / age of themeasurements when the storing of the Connected measurements. The UE may start the time or start to count the time / age of the measurements when the measurement(s) whose result(s) is(are) performed. The UE may start the time or start to count the time / age of the measurements when the measurement result(s) which is(are) stored is(are) obtained. The UE may start the timer or start to count the time / age of the measurements when one or more of the following occurs (noting that 5G-specific terminology is being used, the same or different terminology may be used in 6G):

[0260] the UE transitions to Idle;

[0261] the UE transitions to Inactive;

[0262] the UE receives a message transitioning the UE to Idle or Inactive;

[0263] the UE receives an EMR configuration, e.g. IdleMeasConfig;

[0264] the start of timer for starting EMR measurements according to the EMR configuration; the storing of the Connected measurements;

[0265] the measurement(s) whose result(s) is(are) stored is(are) performed; or the measurement result(s) which is(are) stored is(are) obtained.

[0266] The value for the timer / time period may be obtained by the UE in a message (e.g. a RRC message) transitioning the UE to Idle or Inactive state, e.g. RRC Suspend, RRC Release (with suspend Configuration), RRC Release (without suspend Configuration), or in a 6G message corresponding to RRC Suspend, RRC Release (with suspend Configuration), RRC Release (without suspend Configuration) in 5G. Alternatively or additionally, the value for the timer / time period may be obtained by the UE in a RRC Reconfiguration message (or 6G equivalent) received while the UE was in Connected state, or in another message reconfiguring the UE received while the UE was in Connected state. Alternatively or additionally, the value for the timer / time period may be obtained by the UE in a message that includes the measurement configuration (Connected mode measurement configuration), e.g. IE MeasConfig. Alternatively or additionally, the value for the timer / time period may be obtained by the UE in the measurement configuration (Connected mode measurement configuration), e.g. IE MeasConfig. Alternatively or additionally, the value for the timer / time period may be obtained by the UE in a message providing EMR configuration information to the UE. Alternatively or additionally, the value for the timer / time period may be obtained by the UE via a broadcasted message, e.g. a System Information (SI) message. Alternatively or additionally, the value for the timer / time period may be obtained by the implementation of the UE, for example in accordance with a timer value defined in a standard, e.g. a 3GPP standard.

[0267] When the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE transmits a set of measurements to the network (referred to as a “third” set of measurements), i.e. when the UE performs EMR. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE transitions to Connected, e.g. to RRCConnected state. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE prepares to resume or to setup e.g. transmission of RRC Resume Request message or RRC Setup Request, or a 6G message corresponding to the RRCResumeRequest, RRCResumeRequestl or RRCSetupRequest message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE sends a message for transitioning to RRC Connected, e.g. a RRC Resume Request or RRC Setup Request, or a 6G message corresponding to the RRCSetupRequest, RRCResumeRequest or RRCResumeRequestl message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE triggers a cell reselection. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives a RRC Setup message or a 6G equivalent to the RRC Setup message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives a RRC Resume message or a 6G equivalent to the RRC Resume message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE transmits a RRC Resume Complete or a 6G equivalent to the RRC Resume Complete message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives a connected mode measurement configuration, e.g. in an RRC Resume message or a 6G equivalent to the RRCResumeRequest or RRCResumeRequestl message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives an indication in system information for stopping the timer. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE transmits one or more stored Connected measurements, e.g. in EMR. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives a request to report EMR, e.g. in an RRC Resume, RRC Setup or UE Information Request message, or a 6G equivalent to the RRCResume, RRCSetup or UElnformationRequest message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE reporting for EMR (e.g. in an RRC Resume Complete and / or UE Information message) the second set of Connected measurements. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE indicates to the networkthat measurement(s) for EMR is(are) available in the UE, e.g. in an RRC Resume Complete, an RRC Setup Complete or an RRC Reestablishment Complete message, or a 6G message corresponding to the RRCResumeComplete, RRCSetupComplete or RRCReestablishmentComplete message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE sends one or more stored Connected measurement(s) to the network, e.g. in an RRC Resume Complete, RRC Setup Complete or UE Information Response message, e.g. a 6G message corresponding to the RRCResumeComplete, RRCSetupComplete or UElnformationResponse message in 5G. Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives a message instructing it to release / delete one or more stored Connected measurement(s), e.g. a dedicated signalling message, e.g. a dedicated RRC message (applicable in embodiments where the timer is started while the UE is in RRC Connected state). Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives a message instructing it to release / delete / deconfigure / deactivate the EMR configuration, e.g. a dedicated signalling message, e.g. a dedicated RRC message (applicable in embodiments where the timer is started while the UE is in RRC Connected state). Alternatively or additionally, when the timer is running, or the time period is being monitored, the UE may stop the timer or stop monitoring the time period when the UE receives a message instructing it to reconfigure / modify / replace the EMR configuration, e.g. a dedicated signalling message, or a dedicated RRC message, e.g. where the reconfiguration, modification or replacement of the EMR configuration impacts how deletion of stored Connected measurements is triggered / controlled (this is applicable to embodiments where the timer is started while the UE is in RRC Connected state).

[0268] Event: UE mobility event - In these embodiments the UE monitors for the occurrence of a UE mobility event, and if such an event occurs while the UE is in Idle or Inactive, the UE deletes the ‘stored Connected measurements’, i.e. the second set of measurements.

[0269] As mentioned herein, 5G specific terminology is being used, the same or different terminology may be used in 6G.

[0270] A UE mobility event may relate to a cell reselection.

[0271] Alternatively or additionally, the UE mobility event may relate to a change of cell.

[0272] Alternatively or additionally, the UE mobility event may relate to a change in the quality of the cell the UE is camping on (e.g. in terms of any of: RSRP, RSRQ, SINR, Signal to Noise Ratio (SNR), pathloss, etc.), where the change in quality is of a sufficient magnitude, e.g. greater than a threshold. The change in the quality of the cell the UE is camped on may be computed as the difference in any of: RSRP, RSRQ, SNR, SINR or pathloss taken at the time of transitioning tothe RRC Idle mode or RRC Inactive state from the RRC Connected mode (or from the last measurement result obtained before the transition to RRC Idle or RRC Inactive state from RRC Connected state) and corresponding measurements performed while in RRC Idle or RRC Inactive state (e.g. the UE performs the RRC Idle mode or RRC Inactive state measurements periodically for cell reselection purposes). In this embodiment, the UE mobility event may be considered to have occurred if the change in the quality is above a certain threshold.

[0273] Alternatively or additionally, the UE mobility event may relate to a change in the quality of any measured frequency or cell (e.g. in terms of any of: RSRP, RSRQ, SINR, Signal to Noise Ratio (SNR), pathloss, etc.), where the change in quality is of a sufficient magnitude, e.g. greater than a threshold. In some embodiments, it is enough for the change in the quality of one of the measured frequencies or cells to exceed a threshold for the UE mobility event to be detected and for one or more (or all) of the stored second set of measurements to be deleted. In some embodiments, the UE may delete all stored Connected measurements if a quantity difference for at least a minimum number of cells N exceeds a threshold. In some embodiments, the UE may delete all stored Connected measurements if a quantity difference for at least one frequency exceeds a threshold. In some embodiments, the UE may delete all stored Connected measurements if a quantity difference for at least a minimum number of frequencies N exceeds a threshold. In some embodiments, the UE may delete all stored Connected measurements if a quantity difference for the cell that the UE is camping on exceeds a threshold. In some embodiments, the UE may delete all stored Connected measurements if a quantity difference for the frequency the UE is currently camping on exceeds a threshold. In some embodiments, the UE may delete all stored Connected measurements pertaining to a certain frequency if a quantity difference for that frequency exceeds a threshold. In some embodiments, the UE may delete only those stored Connected measurements for which a quantity difference exceeds a threshold. In some embodiments, the above principle for the deletion of stored Connected measurements may also be applied to stored Connected measurements while the UE is in RRC Connected state. That is, if the condition for deletion is fulfilled (i.e. the occurrence of the UE mobility event is detected) before the UE transitions to RRC Idle or RRC Inactive state, the UE may delete one or more stored Connected measurements. For example, for a UE that has stored one or more Connected measurements and is still in RRC Connected state, the UE may perform one or more subsequent measurements while in RRC Connected state, and the difference in one or more quantity(ies) may be computed between the most recently obtained measurement result(s) and the previously stored Connected measurement results. If this difference exceeds a threshold, the UE may delete the stored Connected measurements for which the difference exceeds the threshold, or, alternatively, the UE may delete all stored Connected measurement results except for the most recently obtained measurement result(s).

[0274] Alternatively or additionally, the UE mobility event may relate to a change of the best beamand / or Synchronisation Signal Block (SSB) for the cell the UE is camping on.

[0275] Alternatively or additionally, the UE mobility event may relate to a change of the best beam and / or SSB the UE is camping on.

[0276] Alternatively or additionally, the UE mobility event may relate to a change of RAN area. Alternatively or additionally, the UE mobility event may relate to a RAN Area Update. Alternatively or additionally, the UE mobility event may relate to a change of RAN Notification Area,

[0277] Alternatively or additionally, the UE mobility event may relate to a RAN Notification Area Update.

[0278] Alternatively or additionally, the UE mobility event may relate to a change of Tracking Area.

[0279] Alternatively or additionally, the UE mobility event may relate to a Tracking Area Update. Alternatively or additionally, the UE mobility event may relate to a change of Registration Area.

[0280] Alternatively or additionally, the UE mobility event may relate to a Registration Area Update.

[0281] Alternatively or additionally, the UE mobility event may relate to a change of Public Land Mobile Network (PLMN).

[0282] Alternatively or additionally, the UE mobility event may relate to the UE loses coverage or goes out of coverage.

[0283] Alternatively or additionally, the UE mobility event may relate to a large enough change in the geographical location of the UE. The UE may monitor its location using one or more receivers (e.g. a Global Navigation Satellite System (GNSS) receiver such as a Global Positioning System (GPS) receiver) and / or sensors (e.g. accelerometer, barometer, etc.). The UE may monitor / determine its location at the time of transitioning to the Idle / lnactive state as a reference location and compare its current location to determine if the UE has moved by more than a certain distance. Such a distance threshold may be configured by the network (either in a dedicated message like RRCRelease or in a broadcasted message like system information) or left to UE implementation.

[0284] Event: Change in broadcasted parameter associated to the validity of the stored connected measurements - In these embodiments, the UE may delete stored Connected measurement(s) in response to a change in one or more broadcasted parameter(s) associated to the validity of the stored Connected measurements.

[0285] For example, a network node may broadcast a flag indicating whether any of the stored Connected mode measurements are valid or not. As another example, a network node may broadcast a parameter indicating the value of a validity timer governing storage of Connectedmode measurements. Such a parameter may be broadcast in one of the system information blocks (SIBs), e.g. a SIB associated to the early measurements reporting feature.

[0286] When the network changes such a parameter (e.g., changing the flag from true to false or reducing the value of the validity timer), the UEs that have any stored Connected mode measurements discard the stored Connected mode measurements from their memory.

[0287] Thus, as one example, if the network changes the above-mentioned flag from true to false, the UEs that have any stored Connected mode measurements discard the stored Connected mode measurements from their memory. As another example, if the network reduces the value of the above-mentioned parameter indicating the value of a validity timer governing storage of Connected mode measurements, the UEs that have Connected mode measurements which that have been stored for a longer time than indicated by the new value of the validity timer discards the stored Connected mode measurements from their memory.

[0288] As another example, the broadcasted parameter that has changed may be a parameter indicating what to measure and report as EMR. In this case, a UE deletes any stored Connected measurements (as well as any measurements performed in RRC Idle or RRC Inactive state) that are not relevant to the changed broadcasted parameter (e.g. which do not match what should be measured and reported as EMR according to the changed broadcasted parameter).

[0289] In some embodiments, the broadcasted parameter that is changed could be specific to a particular frequency or particular cell-related stored Connected mode measurements. For example, the network node may broadcasta parameter that instructs the UE to discard any stored Connected mode measurements associated to Physical Cell Identity (PCI)-X on Frequency-Y. These embodiments may be useful when the network deployment status changes. For example, when a cell is put to sleep for network energy saving reasons, the cell is not available for any data transmissions until it is woken up from sleep state. In such a scenario, all the UEs that have stored Connected mode measurements associated to the sleeping cell could discard those measurements when the cell the UE is camping on starts to indicate to discard them in the broadcasted parameter, e.g. in a broadcasted message.

[0290] In some embodiments, after deleting one or more of the second set of measurements in step 205, the UE may perform a further step in which the UE performs measurements according to an EMR configuration upon deleting stored connected measurements. Thus, the UE may release / delete / discard at least one of the stored Connected measurements upon detecting an event while in Idle or Inactive state in accordance with step 205, and, in response to the deletion, or subsequently, the UE may perform one or more measurements according to an EMR configuration, e.g., IdleMeasConfig. The EMR configuration may be received in a message transitioning the UE to Idle or Inactive, or received in system information.

[0291] In an alternative to the above approach, the UE may start performing measurements according to the EMR configuration in RRC Idle or RRC Inactive state some time before the oneor more stored Connected measurements is(are) deleted according to step 205.

[0292] In some embodiments, after step 205 the UE may perform a state transition from RRC Idle mode or RRC Inactive state to RRC Connected mode. The UE may do this in the same cell that the UE transitioned from RRC Connected state to RRC Idle or RRC Inactive state in step 203, or the UE can transition to RRC Connected state in a different cell to the cell that the UE was previously in RRC Connected state. The different cell may be controlled by the same network node as the cell where the UE transitioned from RRC Connected state to RRC Idle or RRC Inactive state in step 203, or it may be controlled by a different network node.

[0293] In some embodiments, after step 205 the UE may transmit a third set of measurements to a network node. That is, the UE may transmit a report to the second network node (which may be the same or a different network node to the first network node that the UE received the configuration from in step 201). The report consists of a third set of measurements that are based on the stored second set of measurements that were not deleted in step 205, and / or one or more measurements performed based on an EMR configuration (e.g. IdleMeasConfig) that were triggered upon deletion of the stored Connected measurements, e.g. due to a detected event such as timer expiry or UE mobility.

[0294] Thus, in some embodiments the third set of measurements may comprise a subset of the second set of measurements, i.e. the ones which were not deleted in step 205. In some embodiments, the third set of measurements may comprise a subset of measurements performed based on the EMR configuration, and that were performed upon deletion of the stored Connected measurements in step 205.

[0295] In some embodiments, the third set of measurements may comprise a subset of the second set of measurements, where the measurements in the second set of measurements selected to be included in the third set of measurements is based on a configuration provided by the second network node. For example, the second network node may indicate the frequencies and / or cells that are allowed to be part of the third set of measurements. Such a configuration may be a broadcasted configuration or a configuration transmitted by dedicated signalling. Based on such a configuration the UE may filter the second set of measurements to generate the third set of measurements.

[0296] In some embodiments, the third set of measurements may comprise a subset of the second set of measurements, where the measurements in the second set of measurements selected to be included in the third set of measurements is based on a request from the network to report the third set of measurements provided by the second network node (e.g. a request for EMR). For example, the network may indicate in this request which measurements the network is interested in and wants the UE to report, e.g. measurements pertaining to a certain frequency, or measurements of all frequencies (for which the UE has available stored measurements) except for a certain frequency, or all stored measurements except measurements on the UE’s currentcell.

[0297] In some embodiments the third set of measurements may consist of both Connected measurements (i.e. measurements performed in RRC Connected state) and measurements performed in RRC Idle or RRC Inactive state.

[0298] In some embodiments, the UE indicates whether a measurement to be reported (e.g. for a given frequency) is a Connected stored measurement or a measurement performed based on EMR configuration (e.g. performed aftera stored Connected measurement was deleted according to step 205).

[0299] The transmitted third set of measurements may include an indication indicating whether the third set of measurements was collected while the UE was in RRC Connected mode or not. In some embodiments, this indication may be provided per reported measurement.

[0300] The transmitted third set of measurements may include duration information indicating the time since the previous transition to the RRC Idle mode or RRC Inactive state from the RRC Connected mode.

[0301] The transmitted third set of measurements may include a measurement associated with the difference in the measurement quantities (e.g., RSRP, RSRQ, SINR, etc.) of the cell that the UE is camped on. The difference in the camping cell measurement quantity may be computed as the difference between the measurement quantity of the camped-on cell as measured at the time of transitioning from RRC Idle mode or RRC Inactive state to RRC connected mode, and the corresponding measurement for the cell stored in the second set of measurements. This difference information assists the network in knowing if the radio conditions have changed significantly between the state transitions in step 203 and step 205. This difference may be indicated as an explicit indication (i.e. an explicit indication of the difference). In some embodiments the indication may only be reported to the network if it exceeds a certain threshold value. The threshold value may be configured by the network, e.g. as part of the configuration of the measurements, the configuration of the reporting, or the configuration of EMR, or the threshold can be specified in a standard. As an alternative to the above, the difference in measurement quantities does not need to be explicitly indicated by the UE, and instead both measurement quantities are reported to the network and it is up to the receiver of the measurement quantities to calculate the difference.

[0302] In some embodiments, the transmitted third set of measurements may include the measurement quantities (e.g. RSRP, RSRQ, SINR, etc.) of the cell that the UE was camped on that were measured while transitioning from RRC Idle mode or RRC Inactive state to RRC connected mode, or the most recent such measurement available at that point in time. This information may be used by the network node to compute the difference between the measurement quantities of the camped cell and the corresponding cell’s measurements that were stored as part of the second set of measurements by the UE. This computed difference mayassist the network in determining whether the radio conditions have changed significantly between the state transitions in step 203 and step 205.

[0303] The transmission of the third set of measurements to the second network node may be based on an explicit request from the network node. In some embodiments, the network may request the EMR from the UE and the UE reports the third set of measurements in response. In other embodiments, the network may request the UE to trigger the EMR only if the UE has measurements performed while being in RRC Connected mode. In these embodiments, if the UE has any relevant third set of measurements derived from the second set of measurements, the UE responds with the transmission of the third set of measurements.

[0304] In some embodiments, the UE may indicate the presence / availability of the third set of measurements in its memory via an indication in an uplink (UL) message (e.g. a RRC message). Such an indication may be different from the EMR related measurements performed / collected in the RRC Idle mode or RRC Inactive state. Based on such an indication, the network node may request the UE to transmit the third set of measurements.

[0305] Figs. 3, 4 and 5 are signalling diagrams that illustrate the reporting of Connected measurements a UE has stored when it transitioned to Idle or Inactive. The figures show the signalling between a UE 302 and a RAN node 304 (e.g., a 6G RAN node).

[0306] In Fig. 3, in step 304 the UE is initially in RRC Connected.

[0307] In step 306, the UE receives a RRC Reconfiguration message that includes measurement configuration. The measurement configuration indicates a first set of frequencies, e.g. fO, f1 , f2. Step 306 may correspond to step 201 as defined herein.

[0308] In step 307, the UE responds to the RRC Reconfiguration message with a RRC Reconfiguration Complete message.

[0309] In step 308, the UE performs measurements on the first set of frequencies (e.g., fO, f 1 , f2). Step 308 may correspond to step 202 as defined herein.

[0310] In step 309, the UE receives a RRC message that indicates the UE is to transition from RRC Connected to RRC Idle. The RRC message can be a RRC Release message. In step 310, the UE then transitions to RRC Idle or Inactive. The step 309 may correspond to the step 203 as defined herein.

[0311] In step 311 , from the measurements performed in step 308, the UE stores a second set of measurements, with these measurements being measurements on a second set of frequencies, e.g. f 1 , f2. The second set of frequencies are a subset of the frequencies in the first set of frequencies. Step 311 nay correspond to the step 204 as defined herein.

[0312] In step 312, the UE starts a timer, and if / when the timer expires, the UE releases (discards / deletes) the second set of measurements. Step 312 may correspond to the step 205 as defined herein.Fig. 4 shows similar signalling to Fig. 3, except for the final step by the UE.

[0313] In step 404 the UE is initially in RRC Connected.

[0314] In step 406, the UE receives a RRC Reconfiguration message that includes measurement configuration. The measurement configuration indicates a first set of frequencies, e.g. fO, f1 , f2. Step 306 may correspond to step 201 as defined herein.

[0315] In step 407, the UE responds to the RRC Reconfiguration message with a RRC Reconfiguration Complete message.

[0316] In step 408, the UE performs measurements on the first set of frequencies (e.g., fO, f 1 , f2). Step 308 may correspond to step 202 as defined herein.

[0317] In step 409, the UE receives a RRC message that indicates the UE is to transition from RRC Connected to RRC Idle. The RRC message can be a RRC Release message. In step 410, the UE then transitions to RRC Idle or Inactive. The step 409 may correspond to the step 203 as defined herein.

[0318] In step 411 , from the measurements performed in step 308, the UE stores a second set of measurements, with these measurements being measurements on a second set of frequencies, e.g. f 1 , f2. The second set of frequencies are a subset of the frequencies in the first set of frequencies. Step 411 nay correspond to the step 204 as defined herein.

[0319] After, the UE has stored the second set of measurements (step 411, step 204), in step 412, the UE monitors for occurrence of a UE mobility event. On the occurrence of a UE mobility event (e.g. cell reselection), the UE releases (discards / deletes) the second set of measurements. Step 412 may correspond to step 205 as defined herein.

[0320] In Fig. 5, in step 505, the UE is initially in RRC Connected.

[0321] In step 506, the UE receives a RRC Reconfiguration message that includes measurement configuration. The measurement configuration indicates a first set of frequencies, e.g. fO, f1 , f2. Step 506 may correspond to step 201 as defined herein.

[0322] In step 507, the UE responds to the RRC Reconfiguration message with a RRC Reconfiguration Complete message.

[0323] In step 508, the UE performs measurements on the first set of frequencies. Step 508 may correspond to step 202 as defined herein.

[0324] In step 509, the UE receives a RRC message that indicates the UE is to transition from RRC Connected to RRC Idle. The RRC message includes an EMR configuration. The RRC message can be a RRC Release message.

[0325] In step 510, the UE then transitions to RRC Idle or Inactive. Step 510 may correspond to step 203 as defined herein.

[0326] From the measurements performed in step 508, in step 511, the UE stores a second set of measurements, with these measurements being measurements on a second set of frequencies,e.g. f 1 , f2. The second set of frequencies are a subset of the frequencies in the first set of frequencies. Step 511 may correspond to step 204 as defined herein.

[0327] In step 512, the UE starts a timer, and if / when the timer expires, the UE releases (discards / deletes) the second set of measurements (as defined herein in step 205), and starts performing measurements according to the received EMR configuration (which indicated a third set of frequencies).

[0328] In step 513, the UE sends a RRC Resume request message to the RAN node in order for the UE to transition back to RRC Connected.

[0329] In step 514, the RAN node responds with a RRC Resume message.

[0330] In step 515, the UE transitions to RRC Connected and in step 516 the UE responds to the RAN node with a RRC Resume Complete message.

[0331] In step 517, the UE sends a message to the RAN node that includes the measurements on the third set of frequencies according to the EMR configuration.

[0332] It will be appreciated that the actions performed by a UE according to the embodiments above relating to step 204, 311, 411, 511 (storing the second set of measurements) and / or step 205, 312, 412, 512 (deleting / releasing one or more of the second set of measurements) may be specified in a standard, e.g. a 3GPP standard such as 3GPP TS 38.331, or a 6G equivalent of that standard. Alternatively, embodiments of these step(s) may be left to UE implementation.

[0333] While this disclosure primarily relates to the actions by a UE, a corresponding method by one or more network nodes in the RAN is outlined below with reference to Fig. 6. As noted above with regard to Fig. 2 and the associated description, the UE may receive the first configuration (measurement configuration) from a first RAN node (i.e. a first network node in the RAN), and the UE may subsequently send a third set of measurements after transitioning to the Connected state. The third set of measurements are sent to the RAN node that the UE has the Connected state with. So, if the UE transitioned to Connected state with the first RAN node, the third set of measurements are sent to the first RAN node. However, if the UE transitioned to the Connected state with a different RAN node (e.g. a second RAN node), the third set of measurements are sent to the third RAN node.

[0334] The flow chart in Fig. 6 outlines the steps performed in the RAN according to the techniques described herein.

[0335] In step 601, which is performed by a first RAN node, a measurement configuration is transmitted to a UE. The measurement configuration may consist of a first set of frequencies on which the UE is to perform measurements. The measurement configuration may be according to any of the embodiments described above.

[0336] In step 602, the UE is transitioned the UE to RRC Idle mode or RRC Inactive state. This transition may be due to an explicit action by the first RAN node, e.g. by sending a RRC messageto the UE.

[0337] Steps 601 and 602 are performed by the first RAN node, and are shown in Fig. 6 by boxes with dashed outlines.

[0338] In step 603, a RAN node transitions the UE to the RRC Connected mode. This transition may be due to an explicit action by the RAN node, e.g. by sending a RRC message to the UE, or it can be initiated by the UE itself. As noted above, the UE may transition to Connected mode with the first RAN node or with a second RAN node. In the former case, step 603 and the subsequent steps 604 and 605 below are performed by the first RAN node. In the latter case, step 603 and the subsequent steps 604 and 605 below are performed by the second RAN node. As such, steps 603, 604 and 605 are shown with a dotted outline to indicate that they may be performed by the same or a different RAN node to the RAN node that performs steps 601 and 602.

[0339] In step 604, the RAN node receives a third set of measurements from the UE. The third set of measurements are based on the measurement configuration sent to the UE in step 601.

[0340] In step 605, the RAN node configures carrier aggregation (CA) and / or dual connectivity (DC) to the UE based on the received third set of measurements.

[0341] Fig. 7 shows an example of a communication system 700 in accordance with some embodiments.

[0342] In the example, the communication system 700 includes a telecommunication network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes or base stations of various types, such as access network nodes 710a and 710b (one or more of which are also referred to as RAN network nodes or RAN nodes 710 herein), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (AP). Some embodiments of the access network 704 may include more than one access network technology. The network nodes 710 of access network 704 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 712A, 712B, 712C, and 712D (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.

[0343] Moreover, as will be appreciated by those of skill in the art, 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 telecommunication network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 702 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 nodes to implement one or more functionalities ofany node in the telecommunication network 702, including one or more access network nodes 710 and / or core network nodes 708.

[0344] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-Cll user plane (O-CU-UP), a RAN intelligent controller (RIC) (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 A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access 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 (SMO) Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

[0345] The network nodes 710 facilitate direct or indirect connection of wireless devices / UEs 712, such as by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections. The access network nodes 710 may be, for example, access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and New Radio (NR) NodeBs (gNBs)).

[0346] 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 700 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 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0347] The wireless devices / UEs 712 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 710 and other communication devices. Similarly, the access network nodes 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 712 and / or with other network nodes or equipment in the telecommunication network 702 to enable and / or provide network access, such as wireless network access, and / or to performother functions, such as administration in the telecommunication network 702. More specifically, UEs 712 may send messages, data, and / or other signals to network nodes 708, 710 or other elements of the telecommunications network 702 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 708, 710 may send messages, data, and other signals to UEs 7122, other network nodes 708, 710, and other devices in telecommunications network 702 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 712 by transmitting the message to an access network node 710 that will then transmit the message to the intended UE 712. Similarly, a core network node 108 may receive a particular message from a UE 712 by receiving the message from an access network node 710 that itself received the message from the UE 712.

[0348] In the depicted example, the core network 706 connects elements of the access network 704 (e.g. one or more of the access network nodes 710) to one or more host computing systems, such as host 716. 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 706 includes one more core network nodes (e.g. core network node 708) of various types that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the wireless devices / UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708. Example core network nodes include 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 Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0349] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and / or the telecommunication network 702. The host 716 may be operated by the service provider or on behalf of the service provider. The host 716 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.As a whole, the communication system 700 of Fig. 7 enables connectivity between the wireless devices / UEs, network nodes, and hosts. In that sense, the communication system 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 2ndGeneration (2G), 3rdGeneration (3G), 4thGeneration (4G), 5thGeneration (5G) standards, or any applicable future generation standard (e.g. 6thGeneration (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 700 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 700 supporting different standards, protocols, or rule sets.

[0350] As one example, in certain embodiments, access network 704 may contain some access network nodes 710 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 710 support (or the same access network nodes 710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP 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.

[0351] In some examples, the telecommunication network 702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 702. For example, the telecommunications network 702 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) / Massive loT services to yet further UEs.

[0352] In some examples, the UEs 712 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 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (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-UTRA (UMTS Terrestrial Radio Access) Network) New Radio - Dual Connectivity (EN-DC).

[0353] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712c and / or 712d) and network nodes (e.g., network node 710b). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 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 710, or by executable code, script, process, or other instructions in the hub 714. As another example, the hub 714 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 714 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy Internet of Things (loT) devices.

[0354] The hub 714 may have a constant / persistent or intermittent connection to the network node 710b. The hub 714 may also allow for a different communication scheme and / or schedule between the hub 714 and UEs (e.g., UE 712c and / or 712d), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 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 710b. In other embodiments, the hub 714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0355] Fig. 8 shows a wireless device 800, which may be configured to operate in communication system 700 of Fig. 7. The wireless device 800 may be alternatively referred to as a UE 800, likea UE 712 within the context of communication system 700. The wireless device 800 may be configured to perform the method 200 and perform steps of Figures 2, 3, 4, and 5 as described herein.

[0356] 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-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0357] A wireless device 800 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 800 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 800 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 800 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).

[0358] In particular embodiments, wireless device 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input / output interface 806, a power source 808, a memory 810, a communication interface 812, and / or any other component, or any combination thereof. Certain embodiments of wireless device 800 may include all or a subset of the components shown in Fig. 8. The level of integration between the components may vary from one embodiment of wireless device 800 to another. In general, in a particular embodiment of wireless device 800, processing circuitry 802, input / output interface 806, power source 808, memory 810, and communication interface 812 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 800. Further, certain embodiments of wireless devices 800 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0359] The processing circuitry 802 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored asmachine-readable computer programs in the memory 810. The processing circuitry 802 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 802 may include multiple central processing units (CPUs). The processing circuitry 802 may be configured to cause the UE 800 to perform the methods as described with reference to any of Figs. 2-5.

[0360] In the example, the input / output interface 806 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 800. 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.

[0361] In some embodiments, the power source 808 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 808 may further include power circuitry for delivering power from the power source 808 itself, and / or an external power source, to the various parts of wireless device 800 via input circuitry or an interface such as an electrical power cable. Power source 808 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 800 to which power is supplied.

[0362] The memory 810 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 810 includes one or more programs 814, such as an operating system, web browser application, a widget, gadget engine, or other application, andcorresponding data 816. The memory 810 may store, for use by wireless device 800, any of a variety of various operating systems or combinations of operating systems.

[0363] The memory 810 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card’. The memory 810 may allow wireless device 800 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 810, which may be or comprise a device-readable storage medium.

[0364] The processing circuitry 802 may be configured to communicate with an access network or other network via or using the communication interface 812. The communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822. The communication interface 812 may include one or 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 818 and / or a receiver 820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 818 and receiver 820 may be coupled to one or more antennas (e.g., antenna 822) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0365] In the illustrated embodiment, communication functions of the communication interface 812 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), QIIIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0366] In particular embodiments, wireless device 800 may provide an output of data captured via a sensor, through its communication interface 812, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 800 can be communicated through a wireless connection to a network node via another wireless device 800. 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), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0367] As another example, wireless device 800 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 800 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.

[0368] Wireless device 800, 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 800 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 800 shown in Fig. 8.

[0369] As yet another specific example, in an loT scenario, wireless device 800 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 800 may in this case be an M2M device, which may in a 3GPP context be referredto as an MTC device. As one particular example, wireless device 800 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 800 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.

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

[0371] Fig. 9 shows a network node 900 in accordance with some embodiments. The network node 900 is configured to perform the method 600 and the method steps of any of Figure 3, 4, 5, and 6 as described herein.

[0372] 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 900 may be configured to operate in communication system 700 of Fig. 7, like network nodes 708 or 710. 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0373] Network nodes 900 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 900 may be a relay node or a relay donor node controlling a relay. Network nodes 900 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units (CUs), distributed units (Dlls)) (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).

[0374] Other examples of network nodes 900 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers suchas 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).

[0375] In particular embodiments, network node 900 includes a processing circuitry 902, a memory 904, a communication interface 906, and a power source 908. In general, in a particular embodiment of network node 900, processing circuitry 902, memory 904, communication interface 906, and power source 908 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 900.

[0376] The network node 900 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 network node 900 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 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 904 or portions of memory 904 for different RATs) and some components may be reused (e.g., a same antenna 910 may be shared by different RATs). The network node 900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 900, 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 900.

[0377] The processing circuitry 902 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 904, to provide network node 900 functionality. The processing circuitry 902 may be configured to cause the network node 900 to perform the methods as described with reference to any of Figs. 3-6.

[0378] In some embodiments, the processing circuitry 902 includes a system on a chip (SOC). In some embodiments, the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914. In some embodiments, the RF transceiver circuitry 912 and the baseband processing circuitry 914 may be on separate chips (orsets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 912 and baseband processing circuitry 914 may be on the same chip or set of chips, boards, or units.

[0379] The memory 904 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 902. The memory 904 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 902 and utilized by the network node 900. The memory 904 may be used to store any calculations made by the processing circuitry 902 and / or any data received via the communication interface 906. In some embodiments, the processing circuitry 902 and memory 904 is integrated.

[0380] The communication interface 906 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 906 comprises port(s) / terminal(s) 916 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 800 may be capable of wireless communication and communication interface 906 may also include radio front-end circuitry 918 that may be coupled to, or in certain embodiments a part of, an antenna 910. Particular embodiments of radio front-end circuitry 918 include filter(s) 920 and amplifier(s) 922. The radio front-end circuitry 918 may be connected to an antenna 910 and processing circuitry 902. The radio front-end circuitry may be configured to condition signals communicated between antenna 910 and processing circuitry 902. The radio front-end circuitry 918 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 918 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 920 and / or amplifiers 922. The radio signal(s) may then be transmitted via the antenna 910. Similarly, when receiving data, the antenna 910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 918. The digital data may be passed to the processing circuitry 902. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0381] In certain alternative embodiments, network node 900 may be capable of wireless communication but does not include separate radio front-end circuitry 918, instead, the processing circuitry 902 includes radio front-end circuitry and is connected to the antenna 910.Similarly, in some embodiments, all or some of the RF transceiver circuitry 912 is part of the communication interface 906. In still other embodiments, the communication interface 906 includes one or more ports or terminals 916, the radio front-end circuitry 918, and the RF transceiver circuitry 912, as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuitry 914, which is part of a digital unit (not shown).

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

[0383] The antenna 910, communication interface 906, and / or the processing circuitry 902 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 900. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 910, the communication interface 906, and / or the processing circuitry 902 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 900. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0384] The power source 908 provides power to the various components of network node 900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 900 with power for performing the functionality described herein. For example, the network node 900 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 908. As a further example, the power source 908 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.

[0385] Embodiments of the network node 900 may include additional components beyond those shown in Fig. 9 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 900 may include user interface equipment to allow input of information into the network node 900 and to allow output of information from the network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 900.Fig. 10 is a block diagram illustrating a virtualization environment 1000 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 more virtual 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 1000 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 1000 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0386] Applications 1002 (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.

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

[0388] The VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, 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 consolidate many network equipment types onto industry standard high volume server hardware, physicalswitches, and physical storage, which can be located in data centers, and customer premise equipment.

[0389] In the context of NFV, each of the VMs 1008 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 1008, and that part of hardware 1004 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 1008 on top of the hardware 1004 and corresponds to an application 1002.

[0390] Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 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 1010, which, among others, oversees lifecycle management of applications 1002. In some embodiments, hardware 1004 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 signalling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.

[0391] 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 software needed 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 anotherexample, 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.

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

[0393] Although the computing devices described herein (e.g., wireless devices, UEs, network nodes) 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 software needed 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.

[0394] 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 theprocessing 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.

[0395] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.EMBODIMENTS

[0396] A Embodiments

[0397] 1. A method performed by a wireless device, the method comprising:

[0398] while in a connected mode with respect to a communication network, performing measurements of one or more frequencies;

[0399] after transitioning to an idle or inactive mode with respect to the communication network, and after occurrence of an event, deleting, discarding or releasing one or more of the measurements.

[0400] 2. The method of embodiment 1 , wherein the method further comprises:

[0401] receiving, from a Radio Access Network, RAN, node, a measurement configuration; wherein the step of performing measurements is performed according to the received measurement configuration.

[0402] 3. The method of embodiment 2, wherein the measurement configuration indicates one or more frequencies on which measurements are to be performed.

[0403] 4. The method of embodiment 2 or 3, wherein the measurement configuration comprises one or more of:

[0404] an indication of one or more frequencies on which measurements are to be performed; an indication of one or more cells on which measurements are to be performed;

[0405] an indication of one or more beams on which measurements are to be performed;

[0406] an indication of when a measurement report is to be transmitted to a Radio Access Node, RAN, node in the communication network;

[0407] an indication of content of a measurement report to be transmitted to a RAN node in the communication network;

[0408] an indication of whether the wireless device is to store or retain measurements when transitioning to the idle or inactive mode;

[0409] an indication of a time period T 1 that the wireless device is to store or retain measurements; an indication that the measurements are to be reported to the communication network as Early Measurement Reporting, EMR;

[0410] indications on a per measurement object basis;

[0411] indications on a per measurement identifier basis; and

[0412] an indication of a maximum number of measurements to store.

[0413] 5. The method of any of embodiments 1-4, wherein the method further comprises:prior to transitioning to the idle or inactive mode, storing the measurements of the one or more frequencies as a first set of measurements.

[0414] 6. The method of any of embodiments 1-5, wherein the method further comprises:

[0415] prior to transitioning to the idle or inactive mode, deleting, discarding or releasing one or more of the measurements to form a second set of measurements.

[0416] 7. The method of any of embodiments 1-5, wherein the method further comprises:

[0417] after transitioning to the idle or inactive mode and prior to the event occurring, deleting, discarding or releasing one or more of the measurements to form a second set of measurements.

[0418] 8. The method of embodiment 6 or 7, wherein deleting, discarding or releasing one or more of the measurements after occurrence of a predetermined event comprises deleting, discarding or releasing one or more of the measurements in the second set of measurements to form a third set of measurements.

[0419] 9. The method of any of embodiments 1-8, wherein the method further comprises:

[0420] after deleting, discarding or releasing the one or more of the measurements following occurrence of the event, sending any remaining measurements to a RAN node.

[0421] 10. The method of embodiment 9, wherein the remaining measurements are sent to a RAN node that provided the wireless device with a measurement configuration for performing the measurements.

[0422] 11. The method of embodiment 9, wherein the remaining measurements are sent to a different RAN node to a RAN node that provided the wireless device with a measurement configuration for performing the measurements.

[0423] 12. The method of any of embodiments 9-11 , wherein the remaining measurements are sent to a RAN node after transitioning to the connected mode with the RAN node.

[0424] 13. The method of any of embodiments 1-12, wherein the event is:

[0425] a mobility event for or by the wireless device;

[0426] expiry of a timer;

[0427] measurement(s) exceeding a permitted age;

[0428] the communication network requests only certain measurements stored at the wireless device;a time elapsed since the measurements were performed exceeds a threshold; and / or a change in a broadcasted parameter from the communication network.

[0429] 14. The method of any of embodiments 1-13, wherein the event is any of:

[0430] a cell reselection;

[0431] a change of cell;

[0432] a change in the quality of the cell the wireless device is camping on;

[0433] a change in the quality of any measured frequency or cell;

[0434] a change of best beam and / or Synchronisation Signal Block, SSB, for a cell the wireless device is camping on;

[0435] a change of best beam and / or SSB the wireless device is camping on;

[0436] a change of Radio Access Network, RAN, area;

[0437] a RAN Area Update;

[0438] a change of RAN Notification Area;

[0439] a RAN Notification Area Update;

[0440] a change of Tracking Area;

[0441] a Tracking Area Update;

[0442] a change of Registration Area;

[0443] a Registration Area Update;

[0444] a change of Public Land Mobile Network, PLMN;

[0445] the wireless device loses coverage or goes out of coverage; and

[0446] a change in a geographical location of the wireless device larger than a threshold.

[0447] 15. The method of any of embodiments 1-14, wherein the event is expiry of a timer or a time elapsed since the measurements were performed exceeding a threshold, and wherein the timer is started, or the time elapsed monitored from, any of:

[0448] when the wireless device transitions to idle mode;

[0449] when the wireless device transitions to inactive mode;

[0450] when the wireless device receives a message transitioning the wireless device to idle mode or inactive mode;

[0451] when the wireless device receives a reporting configuration;

[0452] a start of a timer for starting Early Measurement Reporting, EMR, measurements according to an EMR configuration;

[0453] when the performed measurements are stored; and

[0454] when the measurements are performed.16. The method of any of embodiments 1-15, wherein the event is expiry of a timer, and wherein the timer is stopped when any of:

[0455] the wireless device transmits measurements to the communication network;

[0456] the wireless device transitions to connected mode;

[0457] the wireless device prepares to resume or to setup connected mode;

[0458] the wireless device sends a message for transitioning to connected mode;

[0459] the wireless device triggers a cell reselection;

[0460] the wireless device receives a setup message;

[0461] the wireless device receives a resume message;

[0462] the wireless device transmits a resume complete message;

[0463] the wireless device receives a connected mode measurement configuration;

[0464] the wireless device receives an indication in system information for stopping the timer; the wireless device transmits one or more of the measurements;

[0465] the wireless device receives a request to report measurements;

[0466] the wireless device reporting the measurements for Early Measurement Reporting, EMR; the wireless device indicates to the communication network that measurements are available;

[0467] the wireless device receives a message instructing it to delete, discard or release one or more of the measurements;

[0468] the wireless device receives a message instructing it to release, delete, deconfigure or deactivate a measurement configuration used to configure the performance of the measurements; or

[0469] the wireless device receives a message instructing it to reconfigure, modify or replace a measurement configuration used to configure the performance of the measurements.

[0470] 17. The method of any of embodiments 1-16, wherein the event is expiry of a timer or a time elapsed since the measurements were performed exceeding a threshold, and wherein the timer value or threshold is:

[0471] received in a message transitioning the wireless device to idle mode or inactive mode; received in a configuration or reconfiguration message while the wireless device is in connected mode;

[0472] received in a message that includes a measurement configuration used to configure the performance of the measurements;

[0473] received in the measurement configuration;

[0474] received in a message providing a reporting configuration to the wireless device; received in a broadcasted message;

[0475] received in a System Information, SI, message; orpreconfigured in the wireless device.

[0476] 18. The method of any of embodiments 1-17, wherein the event is a change in a broadcasted parameter from the communication network, and wherein the broadcasted parameter is any of:

[0477] a flag indicating whether any of the measurements are valid;

[0478] a value of a validity timer relating to the storage of measurements;

[0479] a parameter indicating what measurements are to be performed; and

[0480] a parameter indicating what measurements are to be reported.

[0481] Group B Embodiments

[0482] 19. A method performed by a radio access network, RAN, node, the method comprising: sending, to a wireless device, information for use by the wireless device in determining if one or more measurements stored by the wireless device are to be deleted, discarded or released.

[0483] 20. The method of embodiment 19, wherein the information is for use by the wireless device in determining if one or more measurements obtained when the wireless device was in a connected mode with respect to a communication network are to be deleted, discarded or released after the wireless device transitions to an idle or inactive mode with respect to the communication network.

[0484] 21. The method of embodiment 19 or 20, wherein the information is a timer value or value for a time period.

[0485] 22. The method of embodiment 21 , wherein the timer value or value for the time period is sent to the wireless device in any of:

[0486] a message transitioning the wireless device to idle mode or inactive mode;

[0487] a configuration or reconfiguration message sent to the wireless device while the wireless device is in connected mode;

[0488] a message that includes a measurement configuration used to configure the performance of the measurements by the wireless device;

[0489] a measurement configuration used to configure the performance of the measurements by the wireless device;

[0490] a message providing a reporting configuration to the wireless device;

[0491] a broadcasted message; or

[0492] a System Information, SI, message.

[0493] 23. The method of embodiment 19 or 20, wherein the information is any of:a flag indicating whether any of the measurements are valid;

[0494] a value of a validity timer relating to the storage of measurements;

[0495] a parameter indicating what measurements are to be performed;

[0496] a parameter indicating what measurements are to be reported.

[0497] Group C Embodiments

[0498] 24. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of the Group A embodiments and the Group B embodiments.

[0499] 25. A wireless device configured to perform the method of any of the Group A embodiments.

[0500] 26. A wireless device comprising a processor and a memory, said memory containing instructions executable by said processor whereby said wireless device is operative to perform the method of any of the Group A embodiments.

[0501] 27. A radio access network, RAN, node, configured to perform the method of any of the Group B embodiments.

[0502] 28. A radio access network, RAN, node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to perform the method of any of the Group B embodiments.

[0503] 29. A wireless device comprising:

[0504] processing circuitry configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; and

[0505] power supply circuitry configured to supply power to the processing circuitry.

[0506] 30. A radio access network, RAN, node, comprising:

[0507] processing circuitry configured to cause the RAN node to perform any of the steps of any of the Group B embodiments;

[0508] power supply circuitry configured to supply power to the processing circuitry.

[0509] 31. A wireless device comprising:

[0510] one or more antennas;a communication interface connected to the one or more antennas and to processing circuitry;

[0511] the processing circuitry being configured to perform any of the operations of any of the Group A embodiments;

[0512] an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry;

[0513] an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the wireless device.

Claims

CLAIMS1. A method performed by a wireless device, the method comprising:while in a connected mode with respect to a communication network, performing one or more measurements of one or more frequencies;after transitioning to an idle mode or inactive mode with respect to the communication network, and after occurrence of an event, deleting, discarding or releasing one or more of the measurements.

2. The method of claim 1 , wherein the method further comprises:receiving, from a Radio Access Network, RAN, node, a measurement configuration; wherein the step of performing one or more measurements is performed according to the received measurement configuration.

3. The method of claim 2, wherein the measurement configuration indicates one or more frequencies on which the one or more measurements are to be performed.

4. The method of claims 2 or 3, wherein the measurement configuration comprises one or more of:an indication of one or more frequencies on which the one or more measurements are to be performed;an indication of one or more cells on which the one or more measurements are to be performed;an indication of one or more beams on which the one or more measurements are to be performed;an indication of when a measurement report is to be transmitted to a Radio Access Node, RAN, node in the communication network;an indication of content of a measurement report to be transmitted to a RAN node in the communication network;an indication of whether the wireless device is to store or retain the one or more measurements when transitioning to the idle or inactive mode;an indication of a time period T 1 that the wireless device is to store or retain the one or more measurements;an indication that the one or more measurements are to be reported to the communication network as Early Measurement Reporting, EMR;indications on a per measurement object basis;indications on a per measurement identifier basis; andan indication of a maximum number of measurements to store.

5. The method of any of claims 1-4, wherein the method comprises:prior to transitioning to the idle mode or inactive mode, storing the one or more measurements of the one or more frequencies as a first set of measurements.

6. The method of any of claims 1-5, wherein the method comprises:prior to transitioning to the idle mode or inactive mode, deleting, discarding or releasing one or more of the one or more measurements to form a second set of measurements.

7. The method of any of claims 1-5, wherein the method comprises:after transitioning to the idle mode or inactive mode and prior to the event occurring, deleting, discarding or releasing one or more of the one or more measurements to form a second set of measurements.

8. The method of claims 6 or 7, wherein deleting, discarding or releasing one or more of the one or more measurements after occurrence of a predetermined event comprises deleting, discarding or releasing one or more of the one or more measurements in the second set of measurements to form a third set of measurements.

9. The method of any of claims 1-8, wherein the method comprises:after deleting, discarding or releasing the one or more of the one or more measurements following occurrence of the event, sending any remaining measurements to a RAN node.

10. The method of claim 9, wherein the remaining measurements are sent to the RAN node that provided the wireless device with a measurement configuration for performing the one or more measurements.

11. The method of claim 9, wherein the remaining measurements are sent to a different RAN node to the RAN node that provided the wireless device with a measurement configuration for performing the one or more measurements.

12. The method of any of claims 9-11, wherein the remaining measurements are sent to a RAN node after transitioning to the connected mode with the RAN node.

13. The method of any of claims 1-12, wherein the event is one or more of:a mobility event for or by the wireless device;expiry of a timer;measurement(s) exceeding a permitted age;the communication network requesting only certain measurements stored at the wireless device;a time elapsed since the one or more measurements were performed exceeds a threshold; and / ora change in a broadcasted parameter from the communication network.

14. The method of any of claims 1-13, wherein the event is any of:a cell reselection;a change of cell;a change in the quality of the cell the wireless device is camping on;a change in the quality of any measured frequency or cell;a change of best beam and / or Synchronisation Signal Block, SSB, for a cell the wireless device is camping on;a change of best beam and / or SSB the wireless device is camping on;a change of Radio Access Network, RAN, area;a RAN Area Update;a change of RAN Notification Area;a RAN Notification Area Update;a change of Tracking Area;a Tracking Area Update;a change of Registration Area;a Registration Area Update;a change of Public Land Mobile Network, PLMN;the wireless device loses coverage or goes out of coverage; anda change in a geographical location of the wireless device larger than a threshold.

15. The method of any of claims 1-14, wherein the event is expiry of a timer or a time elapsed since the one or more measurements were performed exceeding a threshold, and wherein the timer is started, or the time elapsed monitored from, any of:when the wireless device transitions to idle mode;when the wireless device transitions to inactive mode;when the wireless device receives a message transitioning the wireless device to idle mode or inactive mode;when the wireless device receives a reporting configuration;a start of a timer for starting Early Measurement Reporting, EMR, measurements accordingto an EMR configuration;when the performed one or more measurements are stored; andwhen the one or more measurements are performed.

16. The method of any of claims 1-15, wherein the event is expiry of a timer, and wherein the timer is stopped when any of:the wireless device transmits measurements to the communication network;the wireless device transitions to connected mode;the wireless device prepares to resume or to setup connected mode;the wireless device sends a message for transitioning to connected mode;the wireless device triggers a cell reselection;the wireless device receives a setup message;the wireless device receives a resume message;the wireless device transmits a resume complete message;the wireless device receives a connected mode measurement configuration;the wireless device receives an indication in system information for stopping the timer; the wireless device transmits one or more of the one or more measurements;the wireless device receives a request to report measurements;the wireless device reporting the measurements for Early Measurement Reporting, EMR; the wireless device indicates to the communication network that measurements are available;the wireless device receives a message instructing it to delete, discard or release one or more of the one or more measurements;the wireless device receives a message instructing it to release, delete, deconfigure or deactivate a measurement configuration used to configure the performance of the one or more measurements; orthe wireless device receives a message instructing it to reconfigure, modify or replace a measurement configuration used to configure the performance of the measurements.

17. The method of any of claims 1-16, wherein the event is expiry of a timer or a time elapsed since the measurements were performed exceeding a threshold, and wherein the timer value or threshold is:received in a message transitioning the wireless device to idle mode or inactive mode; received in a configuration or reconfiguration message while the wireless device is in connected mode;received in a message that includes a measurement configuration used to configure the performance of the one or more measurements;received in the measurement configuration;received in a message providing a reporting configuration to the wireless device; received in a broadcasted message;received in a System Information, SI, message; orpreconfigured in the wireless device.

18. The method of any of claims 1-17, wherein the event is a change in a broadcasted parameter from the communication network, and wherein the broadcasted parameter is any of:a flag indicating whether any of the measurements are valid;a value of a validity timer relating to the storage of measurements;a parameter indicating what measurements are to be performed; anda parameter indicating what measurements are to be reported.

19. A method performed by a radio access network, RAN, node, the method comprising: sending, to a wireless device, information for use by the wireless device in determining if one or more measurements stored by the wireless device are to be deleted, discarded or released.

20. The method of claims 19, wherein the information is for use by the wireless device in determining if one or more measurements obtained when the wireless device was in a connected mode with respect to a communication network are to be deleted, discarded or released after the wireless device transitions to an idle mode or inactive mode with respect to the communication network.

21. The method of claims 19 or 20, wherein the information is a timer value or value for a time period.

22. The method of claims 21 , wherein the timer value or value for the time period is sent to the wireless device in any of:a message transitioning the wireless device to idle mode or inactive mode;a configuration or reconfiguration message sent to the wireless device while the wireless device is in connected mode;a message that includes a measurement configuration used to configure the performance of the one or more measurements by the wireless device;a measurement configuration used to configure the performance of the measurements by the wireless device;a message providing a reporting configuration to the wireless device;a broadcasted message; ora System Information, SI, message.

23. The method of claims 19 or 20, wherein the information is any of:a flag indicating whether any of the measurements are valid;a value of a validity timer relating to the storage of measurements;a parameter indicating what measurements are to be performed;a parameter indicating what measurements are to be reported.

24. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1 to 18 and / or any of claims 19 to 23.

25. A wireless device configured to perform the method of any of claims 1 to 18.

26. A wireless device comprising a processor and a memory, said memory containing instructions executable by said processor whereby said wireless device is operative to perform the method of any of claims 1 to 18.

27. A radio access network, RAN, node, configured to perform the method of any of claims 19 to 23.

28. A radio access network, RAN, node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to perform the method of any of claims 19 to 23.

29. A wireless device comprising:processing circuitry configured to cause the user equipment to perform any of the steps of any of claims 1 to 18; andpower supply circuitry configured to supply power to the processing circuitry.

30. A radio access network, RAN, node, comprising:processing circuitry configured to cause the RAN node to perform any of the steps of any of claims 19 to 23;power supply circuitry configured to supply power to the processing circuitry.

31. A wireless device comprising:one or more antennas;a 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 claims 1 to 18;an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the wireless device.

Images