Reporting of non-connected measurements based on validity timer values

Abstract

Embodiments include methods for a user equipment (UE). Such method include performing non- connected measurements while in one or more non-connected states with respect to a radio access network (RAN) and then sending, to a second RAN node via a second cell, a first request to resume a connection to the RAN. Such methods also include, after resuming the connection in the second cell, selectively performing a validity check of the non-connected measurements based on one of the following, which indicates a maximum age of non-connected measurements that may be reported by the UE: a validity timer value obtained from the second cell, or a validity timer value obtained from a source other than the second cell. Such methods include sending to the second RAN node a report including results of the non-connected measurements. Other embodiments include complementary methods for a second RAN node, as well as UEs and RAN nodes.

Description

[0001] REPORTING OF NON-CONNECTED MEASUREMENTS BASED ON VALIDITY TIMER VALUES

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to wireless networks and devices, and more specifically to techniques for managing reporting of measurements performed while a user equipment (UE) is not connected to a wireless network, specifically reporting after the UE resumes its connection with the wireless network.

[0004] BACKGROUND

[0005] Currently the fifth generation (5G) of cellular systems, also referred to as New Radio (NR), is being standardized within the Third-Generation Partnership Project (3GPP). NR is developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device-to-device (D2D), and several other use cases. NR was initially specified in 3GPP Release 15 (Rel-15) and continues to evolve through subsequent releases.

[0006] Figure 1 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE (110), a gNodeB (gNB, e.g., base station, 120), and an access and mobility management function (AMF, 130) in a 5G core network (5GC). Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP. PDCP provides ciphering / deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP, as well as header compression and retransmission for UP data.

[0007] On the UP side, Internet protocol (IP) packets arrive to PDCP as service data units (SDUs), and PDCP creates protocol data units (PDUs) to deliver to RLC. The Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS) including mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UL and DL packets. RLC transfers PDCP PDUs to MAC through logical channels (LCH). RLC provides error detection / correction, concatenation, segmentation / reassembly, sequence numbering, reordering of data transferred to / from the upper layers. MAC provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (in gNB). PHY provides transport channel services to MAC and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming. On the CP side, the non-access stratum (NAS) layer between UE and AMF handles UE / gNB authentication, mobility management, and security control. RRC sits below NAS in the UE but terminates in the gNB rather than the AMF. RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN. RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs. Additionally, RRC controls addition, modification, and release of carrier aggregation (CA) and dual-connectivity (DC) configurations for UEs, and performs various security functions such as key management.

[0008] After a UE is powered ON it will be in the RRC_IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC IDLE after the connection with the network is released. In RRCJDLE state, the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers. During DRX active periods (also referred to as “DRX On durations”), an RRCJDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on physical DL control channel (PDCCH) for pages from 5GC via gNB. A UE in RRC JDLE state is not known to the gNB serving the cell where the UE is camping. However, NR RRC includes an RRC INACTIVE state in which a UE is known (e.g., via context) by the serving gNB.

[0009] 3GPP Rel-16 introduced a feature referred to as “early measurements” in which a UE can be configured to perform measurements in RRC IDLE / RRC INACTIVE and report the measurement results to the network when entering RRC CONNECTED. The network can use the measurement results, for example, to decide which frequency carriers to use for CA or DC for the UE. The measurements are partly configured via dedicated RRC signaling, such as RRCRelease message sent to instruct the UE to enter RRC DLE.

[0010] The early measurement configuration includes ameasIdleDuration-r 16 field that sets the running time of atimer (T331). The UE starts T331 at reception of the configuration, is required to perform the early measurements while T331 is running, and may optionally continue performing the early measurements after T331 has expired. The configuration may also indicate one or more frequencies on which the UE should measure. This frequency information may also be broadcast in SI, specifically SI block (SIB) 11.

[0011] 3GPP Rel-18 enhances Rel-16 early measurements by adding a configurable validity timer X. If the validity timer X is configured, the UE will only transmit measurement results that are newer than the configured timer value. The validity timer value can be configured via the dedicated RRCRelease message or in SIB11. SUMMARY

[0012] According to Rel-18 specifications, the UE uses a validity timer value received in SIB11 only when it did not receive a validity timer value in the RRCRelease message. In other words, when the UE receives a validity timer value in RRCRelease, it uses that value regardless of SIB11. However, this specified behavior may create various problems, issues, and / or difficulties when a UE reenters RRC_CONNECTED in a second (target) cell after receiving a validity timer value in a. RRCRelease message from a first (source) cell.

[0013] An object of embodiments of the present disclosure is to provide consistent and predictable behavior of non-connected measurement reporting that promotes interoperability between UEs and networks.

[0014] Embodiments include exemplary methods (e.g., procedures) for a UE configured to report measurements performed while in a non-connected state with respect to RAN.

[0015] These exemplary methods include performing non-connected measurements while in one or more non-connected states with respect to the RAN. These exemplary methods also include sending, to a second RAN node via a second cell, a first request to resume a connection to the RAN (i.e., to enter a connected state from anon-connected state). These exemplary methods also include performing the following operations after resuming the connection in the second cell:

[0016] • selectively performing a validity check of the non-connected measurements based on a validity timer value that indicates a maximum age of non-connected measurements that may be reported by the UE; and

[0017] • sending to the second RAN node a report including results of the non-connected measurements.

[0018] In particular, the validity timer value is one of the following: a validity timer value obtained from the second cell, or a validity timer value obtained from a source other than the second cell.

[0019] In some embodiments, these exemplary methods also include, while connected to the RAN via a first cell, receiving from a first RAN node a message indicating for the UE release its connection to RAN. The message includes a configuration for non-connected measurements, and the configuration includes a first validity timer value that indicates a maximum age of nonconnected measurements that may be reported in the first cell. In such case, the non-connected measurements are performed in accordance with the configuration.

[0020] In some embodiments, the exemplary method also includes, before sending the request to the second RAN node, receiving system information (SI) broadcast in the second cell. In some of these embodiments, the received SI includes a second validity timer value that indicates a maximum age of non-connected measurements that may be reported in the second cell. For example, the second validity timer value may be received in one of the following: • in SI block 1 (SIB1), together with an indication of whether a validity timer for nonconnected measurements is supported in the second cell; or

[0021] • in SIB11, as part of a configuration for non-connected measurements in the second cell. In such embodiments, selectively performing the validity check includes performing the validity check based on the second validity timer value included in the received SI.

[0022] In other of these embodiments, selectively performing the validity check includes determining, based on the received SI, whether the second cell supports a validity timer for nonconnected measurements. Additionally, selectively performing the validity check may also include one of the following operations, based on the UE determining that the second cell does not support a validity timer for non-connected measurements:

[0023] • performing the validity check based on a validity timer value obtained from a source other than the second cell; or

[0024] • refraining from performing the validity check.

[0025] In other embodiments, the request to the resume the connection to the RAN is sent without attempting to receive any broadcast SI that indicates whether the second cell supports a validity timer for non-connected measurements. In such embodiments, selectively performing the validity check includes one of the following operations:

[0026] • refraining from performing the validity check;

[0027] • performing the validity check based on a second validity timer value received from the second cell during a previous visit to the second cell; or

[0028] • performing the validity check based on a validity timer value obtained from a source other than the second cell

[0029] In some embodiments, these exemplary methods also include, in response to the request, receiving from the second RAN node a command to resume the connection to the RAN in the second cell. The command includes a request for non-connected measurements and the report is sent in response to the request for non-connected measurements.

[0030] Other embodiments include exemplary methods (e.g., procedures) for a second RAN node configured to provide a second cell in which UEs may resume connections to the RAN. In general, these exemplary methods are complementary to the exemplary methods for a UE summarized above.

[0031] These exemplary methods include receiving, from a first RAN node, context information related to a UE that requests to resume a connection to the RAN that the UE released in a first cell provided by the first RAN node. The context information includes a first validity timer value provided to the UE by the first RAN node. The first validity timer value corresponds to a maximum age of non-connected measurements that may be reported by the UE in the first cell. These exemplary methods also include sending to the UE a command to resume the connection to the RAN in the second cell. The command includes a request for non-connected measurements. These exemplary methods also include, in response to the request, receiving from the UE a report including results of non-connected measurements performed by the UE while in one or more nonconnected states.

[0032] In some embodiments, these exemplary method also includes the following operations:

[0033] • receiving, from the UE via the second cell, a first request to resume the connection; and

[0034] • in response to the first request, sending to the first RAN node a second request for the context information related to the UE.

[0035] In some embodiments, these exemplary methods also include broadcasting SI in the second cell. In some of these embodiments, the broadcast SI includes a second validity timer value that indicates a maximum age of non-connected measurements that may be reported in the second cell. For example, the second validity timer value may be broadcast in one of the following:

[0036] • in SIB1, together with an indication of whether a validity timer for non-connected measurements is supported in the second cell; or

[0037] • in SIB11, as part of a configuration for non-connected measurements in the second cell.

[0038] In some of these embodiments, the second validity timer value overrides the first validity timer value. In other of these embodiments, the second validity timer value does not override the first validity timer value. In other of these embodiments, the broadcast SI indicates that the second cell does not support a validity timer for non-connected measurements. In other of these embodiments, the first request to the resume the connection to the RAN is received without the UE attempting to receive any broadcast SI that indicates whether the second cell supports a validity timer for non-connected measurements.

[0039] The following summary of certain features applies to both UE and second RAN node embodiments described above. In some embodiments, the report includes or indicates one of the following additional information:

[0040] • validity check status for the non-connected measurements;

[0041] • a validity timer value applicable when the UE sent the first request to resume the connection; or

[0042] • a validity timer value used by the UE for the validity check of the non-connected measurements.

[0043] In some of these embodiments, the report indicates the validity check status based on values or absence of one or more validity status flags, such that:

[0044] • first values indicates that a validity check of the non-connected measurements was performed; • second values indicate that a validity check of the non-connected measurements was performed based on the validity timer value obtained from a source other than the second cell; and

[0045] • third values or absence indicate that a validity check of the non-connected measurements was not performed.

[0046] In some embodiments, the validity timer value obtained from a source other than the second cell is one of the following:

[0047] • the first validity timer value received in the configuration for non-connected measurements;

[0048] • a third validity timer value received from a third cell most recently visited by the UE before the second cell; or

[0049] • a default validity timer value.

[0050] In some embodiments, the non-connected measurements include one or more of the following: early measurements for resuming a connection to the RAN, and measurements for cell reselection while not connected to the RAN. In some embodiments, the non-connected measurements are performed while the UE is in one or more of the following states: RRC IDLE, and RRC INACTIVE.

[0051] Other embodiments and variants of the exemplary methods summarized above are described herein. Other embodiments include UEs (e.g., wireless devices) and RAN nodes (e.g., base stations, eNBs, gNBs, etc.) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer- readable media storing program instructions that, when executed by processing circuitry, configure such UEs and RAN nodes to perform operations corresponding to any of the exemplary methods described herein.

[0052] These and other embodiments described herein may provide various benefits and / or advantages. For example, embodiments may prevent a UE from reporting that measurements have been validated to a cell that doesn’t support a validity timer. As another example, a RAN node that supports a validity timer will know whether the UE has applied a validity check to the measurements that it receives from the UE. Embodiments may also facilitate setting of the validity timer value for the UE’s target cell by the RAN node serving that cell, which is beneficial since this RAN node will use the received measurements when determining a configuration for the UE in the target cell. As another example, embodiments may provide unified and / or predictable UE behavior for non-connected (e.g., RRC IDLE / RRC IN ACTIVE) measurement reporting, which enables the network to use UE non-connected measurement results in a consistent manner These and other objects, features, and advantages of embodiments of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.

[0053] BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 shows exemplary NR user plane (UP) and control plane (CP) protocol stacks.

[0055] Figure 2 illustrates a high-level view of an exemplary 5G / NR network architecture.

[0056] Figure 3 shows a signaling diagram of an early measurement procedure between a UE and a gNB.

[0057] Figure 4 shows signaling diagram of a procedure for UE reporting of non-connected measurements, according to some embodiments of the present disclosure.

[0058] Figure 5 shows a flow diagram of an exemplary method for a UE (e.g, wireless device), according to various embodiments of the present disclosure.

[0059] Figure 6 shows a flow diagram of an exemplary method for a RAN node (e.g., wireless device), according to various embodiments of the present disclosure.

[0060] Figure 7 shows a communication system according to various embodiments of the present disclosure.

[0061] Figure 8 shows a UE according to various embodiments of the present disclosure.

[0062] Figure 9 shows a network node according to various embodiments of the present disclosure.

[0063] Figure 10 shows a virtualization environment in which some embodiments of the present disclosure may be implemented.

[0064] DETAILED DESCRIPTION

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

[0066] In general, all terms used herein are to be interpreted according to their ordinary meaning to a person of ordinary skill in the relevant technical field, unless a different meaning is expressly defined and / or implied from the context of use. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise or clearly implied from the context of use. The operations of any methods and / or procedures disclosed herein do not have to be performed in the exact order disclosed, unless an operation is explicitly described as following or preceding another operation and / or where it is implicit that an operation must follow or precede another operation. Any feature of any embodiment disclosed herein can apply to any other disclosed embodiment, as appropriate. Likewise, any advantage of any embodiment described herein can apply to any other disclosed embodiment, as appropriate.

[0067] Furthermore, the following terms are used throughout the description given below:

[0068] • Radio Access Node: As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g, gNB in a 3GPP 5G / NR network or an enhanced or eNB in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pi co, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.

[0069] • Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), aPDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.

[0070] • Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Communicating wirelessly can involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through air. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.

[0071] • Radio Node: As used herein, a “radio node” can be either a “radio access node” (or equivalent term) or a “wireless device.”

[0072] • Network Node: As used herein, a “network node” is any node that is either part of the radio access network (e.g, a radio access node or equivalent term) or of the core network (e.g., a core network node discussed above) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or equipment in the cellular communications network, to enable and / or provide wireless access to the wireless device, and / or to perform other functions (e.g., administration) in the cellular communications network.

[0073] • Node: As used herein, the term “node” (without prefix) can be any type of node that can in or with a wireless network (including RAN and / or core network), including a radio access node (or equivalent term), core network node, or wireless device. However, the term “node” may be limited to a particular type (e.g., radio access node, IAB node) based on its specific characteristics in any given context.

[0074] The above definitions are not meant to be exclusive. In other words, various ones of the above terms may be explained and / or described elsewhere in the present disclosure using the same or similar terminology. Nevertheless, to the extent that such other explanations and / or descriptions conflict with the above definitions, the above definitions should control.

[0075] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is generally used. However, the concepts disclosed herein are not limited to a 3 GPP system, and can be applied in any system that can benefit from the concepts, principles, and / or embodiments described herein.

[0076] Figure 2 shows a high-level view of an exemplary 5G network architecture, including a Next Generation Radio Access Network (NG-RAN, 299) and a 5GC (298). As shown in the figure, the NG-RAN can include gNBs (e.g., 210a,b) and ng-eNBs (e.g, 220a, b) that are connected via respective Xn interfaces. The gNBs and ng-eNBs are also connected to the 5GC via the NG interfaces, more specifically to access and mobility management function (AMFs, e.g, 230a, b) via respective NG-C interfaces and to user plane functions (UPFs, e.g. , 240a, b) via respective NG- U interfaces. Moreover, the AMFs can communicate with one or more policy control functions (PCFs, e.g., 250a,b) and network exposure functions (NEFs, e.g., 260a, b).

[0077] Each of the gNBs can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. In contrast, each of ng-eNBs can support the LTE radio interface but, unlike conventional LTE eNodeBs (eNBs), connect to the 5GC via the NG interface. Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells (e.g., 211a-b, 221a-b). The gNBs and ng-eNBs can also use various directional beams to provide coverage in the respective cells. Depending on the cell in which it is located, a UE (205) can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively. Although Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality. Each gNB can include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU), which can be viewed as logical nodes. CUs host higher-layer protocols and perform various gNB functions such controlling the operation of DUs, which host lower-layer protocols and can include various subsets of the gNB functions. A CU connects to its associated DUs over respective Fl logical interfaces. Each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, communication interface circuitry (e.g., for communication via Xn, NG, radio, etc. interfaces), and power supply circuitry.

[0078] As briefly mentioned above, 3GPP Rel-16 introduced a feature referred to as “early measurements” in which a UE can be configured to perform measurements in RRC IDLE / RRC INACTIVE and report the measurement results to the network when entering RRC CONNECTED. The network can use the measurement results, for example, to decide which frequency carriers to use for CA or DC for the UE. The measurements are partly configured via dedicated RRC signaling, such as RRCRelease message sent to instruct the UE to enter RRC IDLE.

[0079] Figure 3 shows a signaling diagram of an early measurement procedure between a UE and a gNB. Initially, the gNB sends the UE an RRCRelease message that includes the early measurement configuration mentioned above, specifically in an RRC MeasIdleConflg information element (IE). The RRCRelease message causes the UE to transmit an RRCReleaseComplete message, after which the UE enters RRC IDLE or RRC INACTIVE in the same cell in which it received the RRCRelease message.

[0080] Once in RRC IDLE or RRC INACTIVE, the UE performs the early measurements in accordance with the received configuration. The early measurement configuration includes a measIdleDuration-r 16 field that sets the running time of a timer (T331). The UE starts T331 at reception of the configuration, is required to perform the early measurements while T331 is running, and may optionally continue performing the early measurements after T331 has expired.

[0081] The configuration may optionally indicate one or more frequencies on which the UE should measure, which may also be broadcast in SIBI L If the configuration received in the RRCRelease message does not include the frequency information, the UE performs the measurements according to the SIB11 frequency information broadcast in the cell where the UE is currently located - including when the UE continues performing the early measurements after T331 has expired.

[0082] When the UE wants to enter RRC CONNECTED again by resuming (from RRC INACTIVE) or setting up (from RRC IDLE) its connection, the UE sends an RRCResumeRequest or an RRCSetupRequest message to the gNB serving a cell where the UE is currently located. Although Figure 3 shows this as the same gNB that sent the RRCRelease message, the UE may have moved to a different cell served by a different gNB while in RRC IDLE or RRC INACTIVE.

[0083] In any case, the gNB responds to the UE with an RRCResume (or RRCSetup) message. In the case of RRCResume, the gNB may also include a request for early measurements. In response, the UE sends an RRCResumeComplete (or RRCSetupRequest message to the gNB, including an indication that the UE has early measurement results. If the gNB has requested early measurements in RRCResume, the UE may also include the measurement results in RRCResumeComplete .

[0084] 3GPP Rel-18 enhances Rel-16 early measurements by adding a configurable validity timer X. If the validity timer X is configured, the UE will only transmit measurement results that are newer than the configured timer value. The validity timer value can be configured via the dedicated RRCRelease message or in SIBI L The UE can report an indication “checked” if the validity of the reported early measurements was checked prior to sending.

[0085] 3GPP Rel-18 also specifies that cell reselection measurements can be reported to the network. The UE performs cell reselection measurements for mobility when in RRC IDLE or RRC INACTIVE, so obtaining these measurements for reporting requires no extra overhead for the UE. The network can also configure for which frequencies the UE should report cell reselection measurement results in a similar manner as the Rel-16 early measurements. Moreover, the network may also configure a validity timer X also for the cell reselection measurements in a similar manner as the Rel-16 early measurements, i.e., in RRCRelease and / or SIB11. The UE can report an indication “checked” if the validity of the reported cell reselection measurements was checked prior to sending.

[0086] According to Rel-18 specifications, the UE uses a validity timer value received in SIB11 only when it did not receive a validity timer value in the RRCRelease message. If the UE received a validity timer value in RRCRelease, it uses that value regardless of SIBI L However, this specified behavior may create various problems, issues, and / or difficulties when a UE reenters RRC_CONNECTED in a second (target) cell after receiving a validity timer value in a RRCRelease message from a first (source) cell.

[0087] For example, when the UE has received a validity timer value of in RRCRelease from the source cell, it has no way of knowing whether the target cell supports the validity timer nor whether the UE can include validity status “checked” when it transmits the early measurement results. As another example, if the source and target cells are served by different RAN nodes, the RAN node serving the source cell may not know which validity timer value is preferred in the target cell, i.e., maximum age of measurement results the target cell considers useful. Since the measurement results will be used when the UE enters RRC_CONNECTED in the target, the RAN node serving the target cell should set the validity timer value used by the UE - which is not done if the UE obtains the value from a different cell.

[0088] Currently, there is no requirement for the UE to acquire SIB 11 in a target cell before accessing the target cell, so the UE may transmits an RRCResumeRequest message in a target cell acquiring SIB 11 from that cell. Moreover, the UE may receive an RRCResume or UEInformationRequest message via the target cell before acquiring SIBI L It is currently unclear how the UE should handle the validity timer associated with the measurement results when it hasn’t acquired SIB11 of the target cell. As such, it is also unclear which measurement results the UE will report in an RRCResumeComplete, UEInformationResponse, or other message sent in the target cell.

[0089] Embodiments of the present disclosure address these problems, issues, and / or difficulties by providing flexible and efficient procedures for UE reporting of valid measurement results in a target cell when no validity timer value is broadcast in the target cell or when a validity time value is broadcast in the target cell but the UE has not acquired it before resuming its connection and reporting non-connected measurements in the target cell. Common to both of these cases is that the UE does not acquire a validity timer value from the target cell before reporting nonconnected measurements via the target cell.

[0090] Some embodiments include methods (e.g., procedures) performed by a UE configured for reporting measurements performed while in a non-connected state (e.g., RRC IDLE, RRC_INACTIVE) with respect to a RAN after resuming its connection to the RAN (e.g., returning to a connected state such as RRC CONNECTED) in a second (target) cell. The configuration for reporting the measurements was received by the UE in a first (source) cell, such as in an RRCRelease message. The measurements may be Rel-16 early measurements and / or Rel-18 cell reselection measurements. The UE is also configured with a validity timer value that corresponds to a maximum age of the measurements to be reported (i.e., no older measurements may be reported).

[0091] In some embodiments, the UE resumes its connection to the RAN in a target cell that does not broadcast a validity timer value in SI (e.g., SIB11). According to different variants, the UE may:

[0092] • refrain from both performing any validity check of the reported measurements and setting one or more validity status flags in the report to “checked”; or • perform validity check of the reported measurements according to the configuration received in the first (source) cell or a second configuration received in a third cell, e.g., cell most recently visited before the second (target) cell. However, the UE refrains from setting one or more validity status flags in the report to “checked”, even though the validity check was performed.

[0093] In other embodiments, the UE resumes its connection to the RAN in a target cell that broadcasts a validity timer value in SI (e.g., SIB 11), which the UE acquires. In some of these embodiments, the validity timer value broadcast in the target cell overrides the validity timer value most recently acquired by the UE, e.g., in the first (source) cell or in the third (most recently visited) cell. The UE sets one or more validity status flags in the report to “checked”.

[0094] In other of these embodiments, the validity timer value received in the first (source) cell overrides the validity timer value broadcast in the target cell. According to different variants, the UE performs validity check of the reported measurements based on the validity timer value received in the first (source) cell and also:

[0095] • sets one or more validity status flags in the report to “checked”;

[0096] • refrains from setting one or more validity status flags in the report to “checked”, since the validity check was performed using a configuration that was not broadcast in the target cell;

[0097] • set the one or more validity status flags set to a value indicating that validity of the measurements was checked using another configuration that is not broadcast in the target cell; or

[0098] • include in the report the validity timer value used for validity checking..

[0099] In other embodiments, the UE did not acquire the SI with the validity timer value broadcast in the target cell before accessing the target cell to resume its connection to the RAN. In some of these embodiments, the UE refrains from performing a validity check of the measurements prior to reporting them in the target cell.

[0100] In other of these embodiments, the UE performs a validity check of the measurements based on the validity timer value received in the first (source) cell, received in a third cell (e.g., cell most recently visited before the target cell), or a pre-configured validity timer value. According to different variants, the UE may:

[0101] • refrain from setting one or more validity status flags in the report to “checked”, since the validity check was performed using a configuration that was not broadcast in the target cell; • set the one or more validity status flags set to a value indicating that validity of the measurements was checked using another configuration that is not broadcast in the target cell; or

[0102] • include in the report the validity timer value used for validity checking.

[0103] Other embodiments include methods (e.g., procedures) performed by a second RAN node configured to provide a second (target) cell in which UEs may resume their connections to the RAN (e.g., return to a connected state such as RRC_CONNECTED). The second RAN node receives from a first RAN node a validity timer value provided to a UE in a first (source) cell in which the UE entered a non-connected state (e.g., RRC IDLE, RRC IN ACTIVE) with respect to the RAN. The validity timer value corresponds to a maximum age of non-connected state measurements to be reported (i.e., none older may be reported) by UEs in the first (source) cell.

[0104] When the UE resumes its connection in the target cell, the second RAN node receives from the UE a report of measurements performed by the UE while in a non-connected state. In some embodiments, the report may also include one or more validity status flags set to “checked” or to a value indicating that validity of the measurements was checked using another configuration that is not broadcast in the target cell. Based on the validity timer value received from the first RAN node, the second RAN node may determine a maximum age of the reported measurements.

[0105] Embodiments may provide various benefits and / or advantages. For example, embodiments may prevent a UE from reporting that the measurements have been validated to a cell that doesn’t support a validity timer. As another example, a RAN node that supports the validity timer will know whether the UE has applied a validity check to the measurements that it receives from the UE. Embodiments also facilitate setting of the validity timer value for the UE’s target cell by the RAN node serving that cell, which is beneficial since this RAN node will use the received measurements when determining a configuration for the UE in the target cell. As another example, embodiments may provide unified and / or predictable UE behavior for measurement reporting, which enables the network to use UE RRC IDLE / RRC INACTIVE measurement results in a consistent manner.

[0106] Figure 4 shows signaling diagram of a procedure for UE reporting of non-connected measurements, according to some embodiments of the present disclosure. The procedure is between a UE (410), a first RAN node (420) that serves a source (or first) cell, and a second RAN node (430) that serves a target (or second) cell.

[0107] Initially, the first RAN nodes sends the UE an RRCRelease message that includes a configuration for non-connected measurements (e.g., in RRC INACTIVE and / or RRC IDLE). The measurement configuration includes a validity timer value, which corresponds to a maximum age of non-connected measurements to be reported (i.e., none older may be reported) by UEs in the source cell. The non-connected measurements may be Rel-16 early measurements and / or Rel-18 cell reselection measurements. The measurement configuration may include other information, such as discussed above in relation to Figure 3.

[0108] The RRCRelease message causes the UE to transmit an RRCReleaseComplete message, after which the UE enters RRC IDLE or RRC INACTIVE in the source cell. Once in RRC IDLE or RRC INACTIVE, the UE performs non-connected measurements in accordance with the received configuration. At some point, the UE moves from the source cell to the target cell, possibly via an intermediate third cell, while remaining in RRC IDLE or RRC INACTIVE. The UE continue to performs non-connected measurements in accordance with the received configuration.

[0109] Subsequently, the UE decides to re-enter RRC CONNECTED and sends an RRCResumeRequest to the second RAN node serving the target cell where the UE is currently located. The second RAN node may optionally broadcast SIB 11 with a validity timer value in the target cell. When broadcasted, the UE may or may not receive SIB11 with the validity timer value in the target cell before sending the RRCResumeRequest to the second RAN node via the target cell. Different embodiments described below address UE behaviors in these different cases.

[0110] In any case, the second RAN node responds to the UE with an RRCResume and may also include a request for non-connected measurements. In response, the UE sends an RRCResumeComplete message to the second RAN node, including the measurement results (if requested) or an indication of available measurement results (if not requested). The UE may also include other information, as discussed in more detail below.

[0111] In some embodiments, the second RAN node does not broadcast a validity timer value in the target cell. For example, the UE may determine this condition by receiving target cell SI that excludes SIBIL In some of these embodiments, the UE may refrain from both performing any validity check of the reported measurements and setting one or more validity status flags in the report to “checked”.

[0112] In other of these embodiments, the UE may perform a validity check of the reported measurements according to the configuration received in the source cell or a second configuration received in a third cell, e.g., a cell most recently visited before the target cell. With regard to the validity status flags, the UE may perform one of the following:

[0113] • refrain from setting the one or more validity status flags in the report to “checked” even though the validity check was performed.

[0114] • set the one or more validity status flags set to a value indicating that a validity check was performed using a validity timer value from a source other than the target cell; or • include in the report the validity timer value used for the validity check.

[0115] In other embodiments, the second RAN node broadcasts a validity timer value in the target cell, and the UE acquires this value before sending the RRCResumeRequest message. In some of these embodiments, the validity timer value broadcast in the target cell overrides the validity timer value most recently acquired by the UE, e.g., in the source cell or in the most recently visited third cell. The UE sets one or more validity status flags in the report to “checked”.

[0116] In other of these embodiments, the validity timer value most recently acquired by the UE before entering the target cell (i.e., in the source cell or in the most recently visited third cell) overrides the validity timer value broadcast in the target cell. According to different variants, the UE performs validity check of the reported measurements based on the validity timer value most recently acquired by the UE before entering the target cell, and also one of the following:

[0117] • setting the one or more validity status flags in the report to “checked”;

[0118] • refrain from setting the one or more validity status flags in the report to “checked”, since the validity check was not performed using the validity timer value broadcast in the target cell;

[0119] • setting the one or more validity status flags set to a value indicating that a validity check was performed using a validity timer value from a source other than the target cell; or

[0120] • including in the report the validity timer value used for the validity check..

[0121] In other embodiments, the UE does not acquire the broadcast SIB11 with the validity timer value in the target cell before accessing the target cell to resume its connection to the RAN. In some of these embodiments, the UE refrains from performing a validity check of the measurements prior to reporting them in the target cell and from setting the one or more validity status flags in the report to “checked” (e.g., by not including them or by setting instead to a value indicating no validity check was performed).

[0122] In other of these embodiments, the UE performs a validity check of the measurements based on another validity timer value, such as one of the following:

[0123] • the validity timer value received in RRCRelease via the source cell,

[0124] • the validity timer value most recently acquired by the UE before entering the target cell (e.g., in the source cell or via broadcast SIB11 in an intermediate third cell);

[0125] • a validity timer value acquired by the UE during a previous visit to the target cell (e.g., by reading broadcast SIB11); or

[0126] • a default validity timer value applicable when the UE resumes in a cell without acquiring SIB11, which may be pre-defined (e.g., in 3GPP specification) or pre-configured (e.g., in UE subscriber identity module, by NAS message, etc.). Based on using any of these other validity timer values, the UE performs one of the following according to different variants:

[0127] • refrains from setting one or more validity status flags in the report to “checked”, since the validity check was not performed using a validity timer value broadcast in the target cell;

[0128] • sets the one or more validity status flags set to a value indicating that a validity check was performed using a validity timer value from a source other than the target cell; or

[0129] • include in the report the validity timer value used for validity checking.

[0130] In some embodiments, when the UE does not attempt to acquire a broadcast SIB11 (e.g., due to lack of time) before accessing the target cell to resume its connection to the RAN, the UE includes in the report timing information that indicates when the reported measurements were performed. For example, the timing information may include a measurement timestamp, a validity timer value applicable when the measurements were performed, or a validity timer value previously acquired from the target cell. If the second RAN node does not support non-connected measurement reporting or the validity timer in the target cell, the second RAN node discards the received non-connected measurement results. On the other hand, if the second RAN node supports non-connected measurement reporting and the validity timer in the target cell, it can compare the timing information to the validity timer value used in the target cell to determine whether the reported measurement results are usable for configuring the UE in the target cell.

[0131] In some embodiments, the second RAN node may broadcast in SIB1 of the target cell an indication that the validity timer is supported in the target cell (e.g., in broadcast SIB11). In this case, based on acquiring SIB1 but not necessarily SIB11 in the target cell, the UE can determine that that the validity timer is supported in the target cell, perform a validity check of the reported non-connected measurements based on its applicable validity timer value, and set the one or more validity status flags in the report to “checked”. In some variants, the validity timer value can also be included in SIB1, and the UE can apply this value acquired from SIB1 for the validity check.

[0132] In some embodiments, as illustrated in Figure 4, upon receiving the RRCResumeRequest message from the UE in the target cell, the second RAN node sends a RETRIEVE UE CONTEXT REQUEST message to the first RAN node that placed the UE in RRC IDLE or RRC INACTIVE. The first RAN node responds with a RETRIEVE UE CONTEXT REQUEST message that includes the validity timer value provided to the UE in RRCRelease, which the first RAN node also stores in the UE context. Based on this value received from the first RAN node, the second RAN node can determine a maximum age of non-connected measurements reported by the UE in RRCResumeComplete (provided the UE is still using that validity timer value). Accordingly, the second RAN node can reliably use (or not use) these reported measurements for configuring the UE’s operation in the target cell. In other variants, the validity timer value may be sent by the first RAN node to the second RAN node inn other messages, such as during RRC re-establishment or handover preparation (e.g., in HandoverPreparationlnformation). This implies that a configuration parameter for RRC INACTIVE is also stored in UE context and not only the parameters applicable to RRC CONNECTED as in conventional procedures.

[0133] The above-described UE behavior may be tested or verified in various ways. The following is a test scenario for when a UE applies an old validity timer value, e.g. received in an RRCRelease message or in SIB11 via a previous cell. The test scenario involves three cells - A, B, and C.

[0134] Assume that the UE receives an RRCRelease message from cell A, with a validity timer value of 10 seconds. After release, the UE performs measurements on cell C, until cell C is turned off. Two seconds later, the UE is moved so that cell B rather than cell A is the “best” cell for the UE (e.g., highest signal strength). Cell B broadcasts a validity timer value of 1 second.

[0135] Immediately after cell B has become the best cell, the UE is made to enter RRC CONNECTED, such as by triggering the UE to send some data to the network, which initiates an RRC setup or RRC resume procedure. Note that “immediately” in this context is a time so short that UE will be unable to read cell B’s SIB11.

[0136] Test equipment can be used to determine whether the UE reports measurements of cell C after entering RRC CONNECTED in cell B. If the UE reports measurements of cell C, this implies that the UE applied the 10-second validity timer value of cell A rather than the 1 -second validity timer value broadcast by cell B.

[0137] The above-described UE behavior may be UE implementation-specific or may be realized as procedural text in 3GPP specifications. The following example text is for 3GPP TS 38.331 (vl8.1.0) RRC specification, where indicates added text relevant to embodiments of the present disclosure and ellipses indicate existing text omitted for brevity or conciseness.

[0138] *** Begin 3GPP TS 38.331 text ***

[0139] 5.3.13.4 Reception of the RRCResume by the UE

[0140] [••]

[0141] 2> if the UE has idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport.

[0142] 3>if the idleModeMeasurementReq is included in the RRCResume message:

[0143] 4>if measIdleValidityDuration is included in VarEnhMeasIdleConflg,'

[0144] 5> set the measResultldleEUTRA in the RRCResumeComplete message to the value of measReportldleEUTRA in the VarMeasIdleReport for any valid measurement results, if available, and set validity status to value checked for each reported measurement; 5>set the measResultldleNR in the RRCResumeComplete message to the value of measReportldleNR in the VarMeasIdleReport for any valid measurement results, if available, and set validity status to value checked for each reported measurement;

[0145] 5> discard the VarMeasIdleReport upon successful delivery of the RRCResumeComplete message is confirmed by lower layers;

[0146] 4>else:

[0147] 5> set the measResultldleEUTRA in the RRCResumeComplete message to the value of measReportldleEUTRA in the VarMeasIdleReport, if available;

[0148] 5>set the measResultldleNR in the RRCResumeComplete message to the value of measReportldleNR in the VarMeasIdleReport , if available;

[0149] 5> discard the VarMeasIdleReport upon successful delivery of the RRCResumeComplete message is confirmed by lower layers;

[0150] 3>else:

[0151] 4>if the SIB1 contains idleModeMeasurementsNR and the UE has NR idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport,' or

[0152] 4>if the SIB1 contains idleModeMeasurementsEUTRA and the UE has E-UTRA idle / inactive measurement information available in VarMeasIdleReport'.

[0153] 5>include the idleMeasAvailable,' > if the UE has valid reselection measurements available;

[0154] 3>if the reselectionModeMeasurementReq is included in the RRCResume message:

[0155] 4> if measReselectionValidityDuration is included in VarMeasReselectionConflg

[0156] 5>set the measResultReselectionNR in the RRCResumeComplete message to the valid NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConflg and set validity status to value checked for each reported measurement;

[0157] 4> else:

[0158] 5>set the measResultReselectionNR in the RRCResumeComplete message to the NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConflg,'

[0159] 3>else:

[0160] 4>if the SIB1 contains reselectionMeasurementsNR and the UE has valid NR reselection measurements available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConflg,' or 5>include the reselectionMeasAvailablc,

[0161] NOTE: The UE omits the validityStatus in the message if measIdleValidityDuration is not included in SIB 11 or if SIB 11 has not been acquired when the idle / inactive or reselection measurements are reported.

[0162] *** End 3GPP TS 38.331 text ***

[0163] Various features of the embodiments described above correspond to various operations illustrated in Figures 5-6, which show exemplary methods (e.g, procedures) for a UE and a RAN node, respectively. In other words, various features of the operations described below correspond to various embodiments described above. Furthermore, the exemplary methods shown in Figures 5-6 can be used cooperatively to provide various benefits, advantages, and / or solutions to problems described herein. Although Figures 5-6 show specific blocks in particular orders, the operations of the exemplary methods can be performed in different orders than shown and can be combined and / or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.

[0164] In addition, Figure 5 shows an exemplary method (e.g., procedure) for a UE configured to report measurements performed while in a non-connected state with respect to a RAN, according to various embodiments of the present disclosure. The exemplary method can be performed by a UE (c.g. wireless device) such as described elsewhere herein.

[0165] The exemplary method includes the operations of block 520, where the UE performs nonconnected measurements while in one or more non-connected states with respect to the RAN. The exemplary method also includes the operations of block 540, where the UE sends, to a second RAN node via a second cell, a first request to resume a connection to the RAN (i.e., to enter a connected state from a non-connected state). The exemplary method also includes the operations of blocks 570-580, where the UE performs the following operations after resuming the connection in the second cell in block 560:

[0166] • (570) selectively performing a validity check of the non-connected measurements based on a validity timer value that indicates a maximum age of non-connected measurements that may be reported by the UE; and

[0167] • (580) sending to the second RAN node a report including results of the non-connected measurements.

[0168] In particular, the validity timer value used in block 570 is one of the following: a validity timer value obtained from the second cell, or a validity timer value obtained from a source other than the second cell.

[0169] In some embodiments, the exemplary method also includes the operations of block 510, where while connected to the RAN via a first cell, the UE receives from a first RAN node a message indicating for the UE release its connection to RAN. The message includes a configuration for non-connected measurements, and the configuration includes a first validity timer value that indicates a maximum age of non-connected measurements that may be reported in the first cell. In such case, the non-connected measurements are performed in block 520 in accordance with the configuration.

[0170] In some embodiments, the exemplary method also includes the operations of block 530, where before sending the request to the second RAN node in block 550, the UE receives system information (SI) broadcast in the second cell. In some of these embodiments, the received SI includes a second validity timer value that indicates a maximum age of non-connected measurements that may be reported in the second cell. For example, the second validity timer value may be received in one of the following:

[0171] • in SI block 1 (SIB1), together with an indication of whether a validity timer for nonconnected measurements is supported in the second cell; or

[0172] • in SIB11, as part of a configuration for non-connected measurements in the second cell.

[0173] In such embodiments, selectively performing the validity check in block 570 includes the operations of sub-block 571, where the UE performs the validity check based on the second validity timer value included in the received SI.

[0174] In other of these embodiments, selectively performing the validity check in block 570 includes the operations of sub-block 572, where the UE determines, based on the received SI, whether the second cell supports a validity timer for non-connected measurements. Additionally, selectively performing the validity check in block 570 may also include one of the following operations (labelled with corresponding sub-block numbers), based on the UE determining in subblock 572 that the second cell does not support a validity timer for non-connected measurements:

[0175] • (573) performing the validity check based on a validity timer value obtained from a source other than the second cell; or

[0176] • (574) refraining from performing the validity check.

[0177] In other embodiments, the request to the resume the connection to the RAN is sent in block 540 without attempting to receive any broadcast SI that indicates whether the second cell supports a validity timer for non-connected measurements. In such embodiments, selectively performing the validity check in block 570 includes one of the following operations, labelled with corresponding sub-block numbers:

[0178] • (574) refraining from performing the validity check;

[0179] • (575) performing the validity check based on a second validity timer value received from the second cell during a previous visit to the second cell; or • (573) performing the validity check based on a validity timer value obtained from a source other than the second cell

[0180] In various embodiments described above, the report includes or indicates one of the following additional information:

[0181] • validity check status for the non-connected measurements;

[0182] • a validity timer value applicable when the UE sent the first request to resume the connection; or

[0183] • a validity timer value used by the UE for the validity check of the non-connected measurements.

[0184] In some of these embodiments, the report indicates the validity check status based on values or absence of one or more validity status flags, such that:

[0185] • first values indicates that a validity check of the non-connected measurements was performed;

[0186] • second values indicate that a validity check of the non-connected measurements was performed based on the validity timer value obtained from a source other than the second cell; and

[0187] • third values or absence indicate that a validity check of the non-connected measurements was not performed.

[0188] In some embodiments, the validity timer value obtained from a source other than the second cell is one of the following:

[0189] • the first validity timer value received in the configuration for non-connected measurements;

[0190] • a third validity timer value received from a third cell most recently visited by the UE before the second cell; or

[0191] • a default validity timer value.

[0192] In some embodiments, the non-connected measurements include one or more of the following: early measurements for resuming a connection to the RAN, and measurements for cell reselection while not connected to the RAN. In some embodiments, the non-connected measurements are performed while the UE is in one or more of the following states: RRC IDLE, and RRC INACTIVE.

[0193] In some embodiments, the exemplary method also includes the operations of block 550, where in response to the request in block 540, the UE receives from the second RAN node a command to resume the connection to the RAN in the second cell. The command includes a request for non-connected measurements and the report is sent in block 580 in response to the request for non-connected measurements. In addition, Figure 6 shows an exemplary method (e.g., procedure) for a second RAN node configured to provide a second cell in which UEs may resume connections to the RAN, according to various embodiments of the present disclosure. The exemplary method can be performed by a RAN node (e.g, base station, eNB, gNB, etc.) such as described elsewhere herein.

[0194] The exemplary method includes the operations of block 640, where the second RAN node receives, from a first RAN node, context information related to a UE that requests to resume a connection to the RAN that the UE released in a first cell provided by the first RAN node. The context information includes a first validity timer value provided to the UE by the first RAN node. The first validity timer value corresponds to a maximum age of non-connected measurements that may be reported by the UE in the first cell. The exemplary method also includes the operations of block 650, where the second RAN node sends to the UE a command to resume the connection to the RAN in the second cell. The command includes a request for non-connected measurements. The exemplary method also includes the operations of block 660, where in response to the request, the second RAN node receives from the UE a report including results of non-connected measurements performed by the UE while in one or more non-connected states.

[0195] In some embodiments, the exemplary method also includes the following operations, labelled with corresponding block numbers:

[0196] • (620) receiving, from the UE via the second cell, a first request to resume the connection; and

[0197] • (630) in response to the first request, sending to the first RAN node a second request for the context information related to the UE.

[0198] In some embodiments, the exemplary method also includes the operations of block 610, where the second RAN node broadcasts SI in the second cell. In some of these embodiments, the broadcast SI includes a second validity timer value that indicates a maximum age of nonconnected measurements that may be reported in the second cell. For example, the second validity timer value may be broadcast in one of the following:

[0199] • in SIB1, together with an indication of whether a validity timer for non-connected measurements is supported in the second cell; or

[0200] • in SIB11, as part of a configuration for non-connected measurements in the second cell.

[0201] In some of these embodiments, the second validity timer value overrides the first validity timer value. In other of these embodiments, the second validity timer value does not override the first validity timer value. In other of these embodiments, the broadcast SI indicates that the second cell does not support a validity timer for non-connected measurements. In other of these embodiments, the first request to the resume the connection to the RAN is received in block 620 without the UE attempting to receive any broadcast SI that indicates whether the second cell supports a validity timer for non-connected measurements.

[0202] In various embodiments described above, the report includes or indicates one of the following additional information:

[0203] • validity check status for the non-connected measurements;

[0204] • a validity timer value applicable when the UE sent the first request to resume the connection; or

[0205] • a validity timer value used by the UE for the validity check of the non-connected measurements.

[0206] In some of these embodiments, the report indicates the validity check status based on values or absence of one or more validity status flags, such that:

[0207] • first values indicates that a validity check of the non-connected measurements was performed;

[0208] • second values indicate that a validity check of the non-connected measurements was performed based on the validity timer value obtained from a source other than the second cell; and

[0209] • third values or absence indicate that a validity check of the non-connected measurements was not performed.

[0210] In some of these embodiments, the validity timer value used by the UE for the validity check is one of the following:

[0211] • the first validity timer value received in the configuration for non-connected measurements;

[0212] • a third validity timer value received from a third cell most recently visited by the UE before the second cell; or

[0213] • a default validity timer value.

[0214] In some of these embodiments, the exemplary method also includes the operations of block 670, where the second RAN node determines, based on the additional information, whether the results of the non-connected measurements are usable for configuring the UE for operation in the second cell.

[0215] In some embodiments, the non-connected measurements include one or more of the following: early measurements for resuming a connection to the RAN, and measurements for cell reselection while not connected to the RAN. In some embodiments, the non-connected measurements are performed while the UE is in one or more of the following states: RRC IDLE, and RRC INACTIVE. Although various embodiments are described above in terms of methods, techniques, and / or procedures, the person of ordinary skill will readily comprehend that such methods, techniques, and / or procedures can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc.

[0216] Figure 7 shows an example of a communication system 700 in accordance with some embodiments. In this example, communication system 700 includes a telecommunication network 702 that includes an access network 704 (e.g., RAN) and a core network 706, which includes one or more core network nodes 708. Access network 704 includes one or more access network nodes, such as network nodes 710a-b (one or more of which may be generally referred to as network nodes 710), or any other similar 3GPP access nodes or non-3GPP access points. 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.

[0217] Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, telecommunication network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in 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 of any node in telecommunication network 702, including one or more network nodes 710 and / or core network nodes 708.

[0218] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e. g. , r App), or any combination thereof (the adj ective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN 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 Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. Network nodes 710 facilitate direct or indirect connection of UEs, such as by connecting UEs 712a-d (one or more of which may be generally referred to as UEs 712) to core network 706 over one or more wireless connections.

[0219] 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, 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. 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.

[0220] UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network nodes 710 and other communication devices. Similarly, network nodes 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly with UEs 712 and / or with other network nodes or equipment in telecommunication network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in telecommunication network 702.

[0221] In the depicted example, core network 706 connects network nodes 710 to one or more hosts, 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. Core network 706 includes one or more core network nodes (e.g., 708) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of 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 De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0222] Host 716 may be under the ownership or control of a service provider other than an operator or provider of access network 704 and / or telecommunication network 702, and may be operated by the service provider or on behalf of the service provider. 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.

[0223] As a whole, communication system 700 of Figure 7 enables connectivity between the 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 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (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.

[0224] In some examples, telecommunication network 702 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunication network 702 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 702. For example, telecommunication 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.

[0225] In some examples, 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 access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 704. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

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

[0227] Hub 714 may have a constant / persistent or intermittent connection to network node 710b. Hub 714 may also allow for a different communication scheme and / or schedule between hub 714 and UEs (e.g., 712c and / or 712d), and between hub 714 and core network 706. In other examples, hub 714 is connected to core network 706 and / or one or more UEs via a wired connection. Moreover, hub 714 may be configured to connect to an M2M service provider over access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 710 while still connected via hub 714 via a wired or wireless connection. In some embodiments, hub 714 may be a dedicated hub -that is, ahub whose primary function is to route communications to / from the UEs from / to network node 710b. In other embodiments, hub 714 may be a non-dedicated hub capable of routing communications between the UEs and network node 710b as well as operating as a communication start and / or end point for certain data channels.

[0228] In some embodiments, any of UEs 712 may be configured to perform operations attributed to a UE in various embodiments described above, including the exemplary method shown in Figure 5. In some embodiments, any of network nodes 710 may be configured to perform operations attributed to a RAN node in various embodiments described above, including the exemplary method shown in Figure 6.

[0229] Figure 8 shows a UE 800 in accordance with some embodiments. Examples of a UE include, but are not limited to, 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), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by 3GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0231] UE 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 UEs may utilize all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0232] 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 as machine-readable computer programs in memory 810. 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, processing circuitry 802 may include multiple central processing units (CPUs).

[0233] In the example, 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 UE 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.

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

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

[0236] 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ Memory 810 may allow UE 800 to access instructions, application 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 memory 810, which may be or comprise a device-readable storage medium. Processing circuitry 802 may be configured to communicate with an access network or other network using communication interface 812. Communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822. 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 UE 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, 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.

[0237] In the illustrated embodiment, communication functions of communication interface 812 may include cellular communication, Wi-Fi communication, 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 in 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0238] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 812, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The 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).

[0239] As another example, a UE 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, the UE 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. A UE, 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, city 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device 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 UE 800 shown in Figure 8.

[0240] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE 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.

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

[0242] In some embodiments, UE 800 may be configured to perform operations attributed to a UE in various embodiments described above, including the exemplary method shown in Figure 5. Figure 9 shows a network node 900 in accordance with some embodiments. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (e.g., radio base stations, Node Bs, eNBs, gNBs), and O-RAN nodes or components of an O-RAN node (e g., O-RU, O-DU, O-CU).

[0243] Base stations 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. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

[0245] Network node 900 includes processing circuitry 902, memory 904, communication interface 906, and power source 908. Network node 900 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 900 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components 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, network node 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 904 for different RATs) and some components may be reused (e.g., a same antenna 910 may be shared by different RATs). 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, WiFi, 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.

[0246] 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 network node 900 components, such as memory 904, to provide network node 900 functionality.

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

[0248] 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 processing circuitry 902. 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 (collected denoted computer program 904a, which may be in the form of a computer program product) capable of being executed by processing circuitry 902 and utilized by network node 900. Memory 904 may be used to store any calculations made by processing circuitry 902 and / or any data received via communication interface 906. In some embodiments, processing circuitry 902 and memory 904 is integrated.

[0249] Communication interface 906 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, 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. Communication interface 906 also includes radio front-end circuitry 918 that may be coupled to, or in certain embodiments a part of, antenna 910. Radio front-end circuitry 918 comprises filters 920 and amplifiers 922. 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. 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. Radio front-end circuitry 918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 920 and / or amplifiers 922. The radio signal may then be transmitted via antenna 910. Similarly, when receiving data, antenna 910 may collect radio signals which are then converted into digital data by radio front-end circuitry 918. The digital data may be passed to processing circuitry 902. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

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

[0251] Antenna 910 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 910 may be coupled to 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, antenna 910 is separate from network node 900 and connectable to network node 900 through an interface or port.

[0252] Antenna 910, communication interface 906, and / or processing circuitry 902 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, antenna 910, communication interface 906, and / or processing circuitry 902 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0253] 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). Power source 908 may further comprise, or be coupled to, power management circuitry to supply the components of network node 900 with power for performing the functionality described herein. For example, 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 power source 908. As a further example, 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.

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

[0255] In some embodiments, network node 900 may be configured to perform operations attributed to a RAN node in various embodiments described above, including the exemplary method shown in Figure 6.

[0256] Figure 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 a network node, UE, core network node, or host. Further, in embodiments in which the 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.

[0257] 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 1000 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. For example, one or more virtual nodes 1002 may be configured to perform operations attributed to a RAN node in various embodiments described above, including the exemplary method shown in Figure 6. Hardware 1004 includes processing circuitry, memory that stores software and / or instructions (collected denoted computer program 1004a, which may be in the form of a computer program product) 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 VMs 1008a-b (one or more of which may be generally referred to as VMs 1008), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. Virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.

[0258] VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding 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, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

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

[0260] 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 function 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 signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.

[0261] 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 spirit and scope of the disclosure. Various 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.

[0262] The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and / or electronic devices and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.

[0263] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0264] As described herein, device and / or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and / or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

[0265] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0266] In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). It should be understood that although such terms may be used synonymously herein, there may also be instances when such terms are not intended to be used synonymously.

[0267] Embodiments of the present disclosure also include, but are not limited to, the following enumerated examples.

[0268] Al. A method for a user equipment (UE) configured to report measurements performed while in a non-connected state with respect to a radio access network (RAN), the method comprising: while connected to the RAN via a first cell, receiving from a first RAN node a message indicating for the UE release its connection to RAN, wherein the message includes a configuration for non-connected measurements, wherein the configuration includes a first validity timer value corresponding to a maximum age of non-connected measurements to be reported in the first cell; after releasing the connection to the RAN, performing the non-connected measurements in accordance with the configuration; sending, to a second RAN node via a second cell, a request to resume the connection to the RAN; and performing the following after resuming the connection to the RAN in the second cell: selectively performing a validity check on the non-connected measurements based on one of the following: a validity timer value obtained from the second cell, or a validity timer value obtained from a source other than the second cell; and sending to the second RAN node a report including results of the non-connected measurements.

[0269] A2. The method of embodiment Al, further comprising, before sending the request to the second RAN node, receiving system information (SI) broadcast in the second cell.

[0270] A2a. The method of embodiment A2, wherein the received SI includes a second validity timer value applicable in the second cell.

[0271] A2b. The method of embodiment A2a, wherein the second validity timer value is received in one of the following: in SI block 1 (SIB1), together with an indication of whether a validity timer for nonconnected measurements is supported in the second cell; or in SIB11, as part of a configuration for non-connected measurements in the second cell.

[0272] A2c. The method of any of embodiments A2a-A2b, wherein: selectively performing the validity check comprises performing the validity check based on the second validity timer value; and the report also includes one or more validity status flags indicating that a validity check of the non-connected measurements was performed.

[0273] A2d. The method of any of embodiments A2a-A2b, wherein: selectively performing the validity check comprises performing the validity check based on the validity timer value obtained from a source other than the second cell; and the report also indicates one of the following: validity check status; or timing information that indicates when the non-connected measurements were performed.

[0274] A3. The method of embodiment A2, wherein: the method further comprises determining, based on the received SI, that the second cell does not support a validity timer for non-connected measurements; and selectively performing the validity check comprises one of the following: refraining from performing a validity check of the non-connected measurements, based on determining that the second cell does not support a validity timer for non-connected measurements; or performing the validity check based on a validity timer value obtained from a source other than the second cell.

[0275] A4. The method of embodiment A2, wherein: the request to the resume the connection to the RAN is sent without attempting to receive any broadcast system information (SI) that indicates whether the second cell supports a validity timer for non-connected measurements; and selectively performing the validity check comprises one of the following: refraining from performing a validity check of the non-connected measurements; performing the validity check based on a second validity timer value received from the second cell during a previous visit to the second cell; or performing the validity check based on a validity timer value obtained from a source other than the second cell; and

[0276] A5. The method of any of embodiments A2d-A4, wherein the report also includes one of the following: validity check status, or timing information that indicates when the non-connected measurements were performed.

[0277] A5a. The method of embodiment A5, wherein the report indicates validity check status based on values or absence of one or more validity status flags, such that: first values indicates that a validity check of the non-connected measurements was performed; second values indicate that a validity check of the non-connected measurements was performed based on a validity timer value obtained from a source other than the second cell; and third values, or absence of, indicate that a validity check of the non-connected measurements was not performed.

[0278] A5b. The method of embodiment A5, wherein the timing information includes one of the following: a validity timer value applicable when the UE sent the request to resume the connection; a validity timer value used for the validity check; or a measurement timestamp.

[0279] A6. The method of any of embodiments Al-A5b, wherein the validity timer value obtained from a source other than the second cell is one of the following: the first validity timer value received from the first RAN node; a third validity timer value received from a third cell most recently visited by the UE before the second cell; or a default validity timer value.

[0280] A7. The method of any of embodiments A1-A6, wherein the non-connected measurements include one or more of the following: early measurements for resuming a connection to the RAN, and measurements for cell reselection while not connected to the RAN.

[0281] A8. The method of any of embodiments A1-A6, wherein the non-connected measurements are performed while the UE is in one or more of the following states: RRC IDLE, and

[0282] RRC INACTIVE.

[0283] A9. The method of any of embodiments A1-A8, further comprising, in response to the request, receiving from the second RAN node a command to resume the connection to the RAN in the second cell, wherein the command includes a request for non-connected measurements and the report is sent in response to the request for non-connected measurements.

[0284] Bl . A method for a second radio access network (RAN) node configured to provide a second cell in which user equipment (UEs) may resume connections to the RAN, the method comprising: receiving, from a UE via the second cell, a request by the UE to resume a connection to the RAN, which the UE released in a first cell served by a first RAN node; sending to the first RAN node a request for context information related to the UE; receiving from the first RAN node the requested context information, which includes a first validity timer value provided to the UE by the first RAN node, wherein the first validity timer value corresponds to a maximum age of non-connected measurements to be reported in the first cell; sending to the UE a command to resume the connection to the RAN in the second cell, wherein the command includes a request for non-connected measurements; and in response to the request, receiving from the UE a report including results of nonconnected measurements performed by the UE prior to sending the request to resume the connection.

[0285] B2. The method of embodiment Bl, further comprising broadcasting system information (SI) in the second cell.

[0286] B2a. The method of embodiment B2, wherein the broadcast SI includes a second validity timer value applicable in the second cell.

[0287] B2b. The method of embodiments B2a, wherein the second validity timer value is broadcast in one of the following: in SI block 1 (SIB1), together with an indication of whether a validity timer for nonconnected measurements is supported in the second cell; or in SIB11, as part of a configuration for non-connected measurements in the second cell.

[0288] B2c. The method of any of embodiments B2a-B2b, wherein: the second validity timer value overrides the first validity timer value; and the report also includes one or more validity status flags indicating that a validity check of the non-connected measurements was performed.

[0289] B2d. The method of any of embodiments B2a-B2b, wherein the second validity timer value does not override the first validity timer value.

[0290] B3. The method of embodiment B2, wherein the broadcast SI indicates that the second cell does not support a validity timer for non-connected measurements.

[0291] B4. The method of any of embodiments B1-B2, wherein the request to the resume the connection to the RAN is received without the UE attempting to receive any broadcast system information (SI) that indicates whether the second cell supports a validity timer for nonconnected measurements.

[0292] B5. The method of any of embodiments B2d-B4, wherein the report also includes one of the following: validity check status, or timing information that indicates when the non-connected measurements were performed. B5a. The method of embodiment B5, wherein the report indicates validity check status based on values or absence of one or more validity status flags, such that: first values indicates that a validity check of the non-connected measurements was performed; second values indicate that a validity check of the non-connected measurements was performed based on a validity timer value obtained from a source other than the second cell; and third values, or absence of, indicate that a validity check of the non-connected measurements was not performed.

[0293] B5b. The method of embodiment B5, wherein the timing information includes one of the following: a validity timer value applicable when the UE sent the request to resume the connection; a validity timer value used by the UE for a validity check of the non-connected measurements; or a measurement timestamp.

[0294] B5c. The method of embodiment B5b, wherein the validity timer used by the UE for the validity check is one of the following: the first validity timer value provided by the first RAN node; a third validity timer value provided by a third cell most recently visited by the UE before the second cell; or a default validity timer value.

[0295] B6. The method of any of embodiments B5-B5c, further comprising, based on the validity check status or the timing information, determining whether the results of the non-connected measurements are usable for configuring the UE for operation in the second cell.

[0296] B7. The method of any of embodiments B1-B6, wherein the non-connected measurements include one or more of the following: early measurements for resuming a connection to the RAN, and measurements for cell reselection while not connected to the RAN. B8. The method of any of embodiments B1-B6, wherein the non-connected measurements are performed while the UE is in one or more of the following states: RRC IDLE, and RRC INACTIVE.

[0297] Cl . User equipment (UE) configured to report measurements performed while in a nonconnected state with respect to a radio access network (RAN), the UE comprising: communication interface circuitry configured to communicate with RAN nodes; and processing circuitry operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments A1-A9.

[0298] C2. User equipment (UE) configured to report measurements performed while in a nonconnected state with respect to a radio access network (RAN), the UE being further configured to perform operations corresponding to the methods of any of embodiments A1-A9.

[0299] C3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of user equipment (UE) configured to report measurements performed while in a non-connected state with respect to a radio access network (RAN), configure the UE to perform operations corresponding to the methods of any of embodiments A1-A9.

[0300] C4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of user equipment (UE) configured to report measurements performed while in a non-connected state with respect to a radio access network (RAN), configure the UE to perform operations corresponding to the methods of any of embodiments A1-A9.

[0301] DI. A second radio access network (RAN) node configured to provide a second cell in which user equipment (UEs) may resume connections to the RAN, the second RAN node comprising: communication interface circuitry configured to communicate with UEs and with other RAN nodes; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments B1-B8.

[0302] D2. A second radio access network (RAN) node configured to provide a second cell in which user equipment (UEs) may resume connections to the RAN, the second RAN node being further configured to perform operations corresponding to the methods of any of embodiments B1-B8.

[0303] D3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a second radio access network (RAN) node configured to provide a second cell in which user equipment (UEs) may resume connections to the RAN, configure the second RAN node to perform operations corresponding to the methods of any of embodiments B1-B8.

[0304] D4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a second radio access network (RAN) node configured to provide a second cell in which user equipment (UEs) may resume connections to the RAN, configure the second RAN node to perform operations corresponding to the methods of any of embodiments B1-B8.

Claims

CLAIMS1. A method for a user equipment, UE, configured to report measurements performed while in one or more non-connected states with respect to a radio access network, RAN, the method comprising: performing (520) non-connected measurements while in one or more non-connected states with respect to the RAN; sending (540), to a second RAN node via a second cell, a first request to resume a connection to the RAN; and performing the following after resuming (560) the connection in the second cell: selectively performing (570) a validity check of the non-connected measurements based on one of the following validity timer values, which indicates a maximum age of non-connected measurements that may be reported by the UE: a validity timer value obtained from the second cell, or a validity timer value obtained from a source other than the second cell; and sending (580) to the second RAN node a report including results of the nonconnected measurements.

2. The method of claim 1, further comprising, while connected to the RAN via a first cell, receiving (510) from a first RAN node a message indicating for the UE release the connection, wherein: the message includes a configuration for non-connected measurements, the configuration includes a first validity timer value that indicates a maximum age of non-connected measurements that may be reported in the first cell, and the non-connected measurements are performed in accordance with the configuration after releasing (515) the connection.

3. The method of any of claims 1-2, further comprising, before sending (540) the first request to the second RAN node, receiving (530) system information, SI, broadcast in the second cell.

4. The method of claim 3, wherein:the received SI includes a second validity timer value that indicates a maximum age of non-connected measurements that may be reported in the second cell; the second validity timer value is received in one of the following SI blocks, SIBs:SIB1, together with an indication of whether a validity timer for non-connected measurements is supported in the second cell; orSIB11, as part of a configuration for non-connected measurements in the second cell; and selectively performing (570) the validity check comprises performing (571) the validity check based on the second validity timer value included in the received SI.

5. The method of claim 3, wherein selectively performing (570) the validity check comprises: determining (572), based on the received SI, whether the second cell supports a validity timer for non-connected measurements; and performing one of the following, in response to determining that the second cell does not support a validity timer for non-connected measurements: performing (573) the validity check based on a validity timer value obtained from a source other than the second cell; or refraining (574) from performing the validity check.

6. The method of any of claims 1 -2, wherein: the first request to the resume the connection is sent without attempting to receive any broadcast system information, SI, that indicates whether the second cell supports a validity timer for non-connected measurements; and selectively performing (570) the validity check comprises one of the following: refraining (574) from performing the validity check; performing (575) the validity check based on a second validity timer value received from the second cell during a previous visit to the second cell; or performing (573) the validity check based on a validity timer value obtained from a source other than the second cell; and7. The method of any of claims 4-6, wherein the report includes or indicates one of the following additional information: validity check status for the non-connected measurements;a validity timer value applicable when the UE sent the first request to resume the connection; or a validity timer value used by the UE for the validity check of the non-connected measurements.

8. The method of claim 7, wherein the report indicates the validity check status based on values or absence of one or more validity status flags, such that: first values indicates that a validity check of the non-connected measurements was performed; second values indicate that a validity check of the non-connected measurements was performed based on the validity timer value obtained from a source other than the second cell; and third values or absence indicate that a validity check of the non-connected measurements was not performed.

9. The method of any of claims 2-8, wherein the validity timer value obtained from a source other than the second cell is one of the following: the first validity timer value received in the configuration for non-connected measurements; a third validity timer value received from a third cell most recently visited by the UE before the second cell; or a default validity timer value.

10. The method of any of claims 1-9, wherein one or more of the following applies: the non-connected measurements include one or more of the following: early measurements for resuming the connection, and measurements for cell reselection while not connected to the RAN; and the one or more non-connected states include one or more of the following: RRC IDLE, and RRC INACTIVE.

11. The method of any of claims 1-10, further comprising, in response to the request, receiving (550) from the second RAN node a command to resume the connection to the RAN in the second cell, wherein: resuming (560) the connection in the second cell is responsive to the command, the command includes a request for non-connected measurements, andsending (580) the report is responsive to the request for non-connected measurements.

12. A method for a second radio access network, RAN, node configured to provide a second cell in which user equipment, UEs, may resume connections to the RAN, the method comprising: receiving (640), from a first RAN node, context information related to a UE that requests to resume a connection to the RAN that the UE released in a first cell provided by the first RAN node, wherein: the context information includes a first validity timer value provided to the UE by the first RAN node, and the first validity timer value corresponds to a maximum age of non-connected measurements that may be reported by the UE in the first cell; sending (650) to the UE a command to resume the connection in the second cell, wherein the command includes a request for non-connected measurements; and in response to the command, receiving (660) from the UE a report including results of non-connected measurements performed by the UE while in one or more nonconnected states.

13. The method of claim 12, further comprising: receiving (620), from the UE via the second cell, a first request to resume the connection; and in response to the first request, sending (630) to the first RAN node a second request for the context information related to the UE, wherein the context information is received in response to the second request.

14. The method of any of claims 12-13, further comprising broadcasting (610) system information, SI, in the second cell.

15. The method of claim 14, wherein: the broadcast SI includes a second validity timer value that indicates a maximum age of non-connected measurements that may be reported in the second cell; the second validity timer value is broadcast in one of the following SI blocks, SIBs: SIB1, together with an indication of whether a validity timer for non-connected measurements is supported in the second cell; orSIB11, as part of a configuration for non-connected measurements in the second cell.

16. The method of claim 15, wherein one of the following applies: the second validity timer value overrides the first validity timer value; or the second validity timer value does not override the first validity timer value.

17. The method of claim 14, wherein the broadcast SI indicates that the second cell does not support a validity timer for non-connected measurements.

18. The method of any of claims 13-14, wherein the first request to the resume the connection is received without the UE attempting to receive any broadcast system information, SI, that indicates whether the second cell supports a validity timer for non-connected measurements.

19. The method of any of claims 16-18, wherein the report includes or indicates one of the following additional information: validity check status for the non-connected measurements; a validity timer value applicable when the UE sent the first request to resume the connection; or a validity timer value used by the UE for the validity check of the non-connected measurements.

20. The method of claim 19, wherein the report indicates the validity check status based on values or absence of one or more validity status flags, such that: first values indicates that a validity check of the non-connected measurements was performed by the UE; second values indicate that a validity check of the non-connected measurements was performed by the UE based on the validity timer value obtained from a source other than the second cell; and third values or absence indicate that a validity check of the non-connected measurements was not performed by the UE.

21. The method of claim 19, wherein the validity timer value used by the UE for the validity check is one of the following:the first validity timer value included in the context information; a third validity timer value provided by a third cell most recently visited by the UE before the second cell; or a default validity timer value.

22. The method of any of claims 19-21, further comprising determining (670), based on the additional information, whether the results of the non-connected measurements are usable for configuring the UE for operation in the second cell.

23. The method of any of claims 12-22, wherein one or more of the following applies: the non-connected measurements include one or more of the following: early measurements for resuming the connection, and measurements for cell reselection while not connected to the RAN; and the one or more non-connected states include one or more of the following: RRC IDLE, and RRC INACTIVE.

24. User equipment, UE (110, 205, 410, 721, 800) configured to report measurements performed while in a non-connected state with respect to a radio access network, RAN (299, 704), the UE comprising: communication interface circuitry (812) configured to communicate with RAN nodes; and processing circuitry (802) operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to: perform non-connected measurements while in one or more non-connected states with respect to the RAN; send, to a second RAN node (120, 210, 220, 430, 710, 900, 1002) via a second cell, a first request to resume a connection to the RAN; and perform the following after resuming the connection in the second cell: selectively perform a validity check of the non-connected measurements based on one of the following validity timer values, which indicates a maximum age of non-connected measurements that may be reported by the UE: a validity timer value obtained from the second cell, ora validity timer value obtained from a source other than the second cell; and send to the second RAN node a report including results of the nonconnected measurements.

25. The UE of claim 24, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 2-11.

26. User equipment, UE (110, 205, 410, 721, 800) configured to report measurements performed while in a non-connected state with respect to a radio access network, RAN (299, 704), the UE being further configured to: perform non-connected measurements while in one or more non-connected states with respect to the RAN; send, to a second RAN node (120, 210, 220, 430, 710, 900, 1002) via a second cell, a first request to resume a connection to the RAN; and perform the following after resuming the connection in the second cell: selectively perform a validity check of the non-connected measurements based on one of the following validity timer values, which indicates a maximum age of non-connected measurements that may be reported by the UE: a validity timer value obtained from the second cell, or a validity timer value obtained from a source other than the second cell; and send to the second RAN node a report including results of the non-connected measurements.

27. The UE of claim 26, being further configured to perform operations corresponding to any of the methods of claims 2-11.

28. Non-transitory, computer-readable medium (810) storing computer-executable instructions that, when executed by processing circuitry (802) of user equipment, UE (110, 205, 410, 721, 800) configured to report measurements performed while in anon-connected state with respect to a radio access network, RAN (299, 704), configure the UE to perform operations corresponding to any of the methods of claims 1-11.

29. Computer program product (814) comprising computer-executable instructions that, when executed by processing circuitry (802) of user equipment, UE (110, 205, 410, 721, 800) configured to report measurements performed while in a non-connected state with respect to a radio access network, RAN (299, 704), configure the UE to perform operations corresponding to any of the methods of claims 1-11.

30. Second radio access network, RAN, node (120, 210, 220, 430, 710, 900, 1002) configured to provide a second cell in which user equipment, UEs (110, 205, 410, 721, 800) may resume connections to the RAN (299, 704), the second RAN node comprising: communication interface circuitry (906, 1004) configured to communicate with UEs and with a first RAN node (120, 210, 220, 420, 710, 900, 1002); and processing circuitry (902, 1004) operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to: receive, from the first RAN node, context information related to a UE that requests to resume a connection to the RAN that the UE released in a first cell provided by the first RAN node, wherein: the context information includes a first validity timer value provided to the UE by the first RAN node, and the first validity timer value corresponds to a maximum age of nonconnected measurements that may be reported by the UE in the first cell; send to the UE a command to resume the connection in the second cell, wherein the command includes a request for non-connected measurements; and in response to the command, receive from the UE a report including results of non-connected measurements performed by the UE while in one or more non-connected states.

31. The second RAN node of claim 29, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 13-23.

32. Second radio access network, RAN, node (120, 210, 220, 430, 710, 900, 1002) configured to provide a second cell in which user equipment, UEs (110, 205, 410, 721, 800) may resume connections to the RAN (299, 704), the second RAN node being further configured to:receive, from a first RAN node (120, 210, 220, 420, 710, 900, 1002), context information related to a UE that requests to resume a connection to the RAN that the UE released in a first cell provided by the first RAN node, wherein: the context information includes a first validity timer value provided to the UE by the first RAN node, and the first validity timer value corresponds to a maximum age of non-connected measurements that may be reported by the UE in the first cell; send to the UE a command to resume the connection in the second cell, wherein the command includes a request for non-connected measurements; and in response to the command, receive from the UE a report including results of nonconnected measurements performed by the UE while in one or more nonconnected states.

33. The second RAN node of claim 31, being further configured to perform operations corresponding to any of the methods of claims 13-23.

34. Non-transitory, computer-readable medium (904, 1004) storing computer-executable instructions that, when executed by processing circuitry (902, 1004) of a second radio access network, RAN, node (120, 210, 220, 430, 710, 900, 1002) configured to provide a second cell in which user equipment, UEs (110, 205, 410, 721, 800) may resume connections to the RAN (299, 704), configure the second RAN node to perform operations corresponding to any of the methods of claims 12-23.

35. Computer program product (904a, 1004a) comprising computer-executable instructions that, when executed by processing circuitry (902, 1004) of a second radio access network, RAN, node (120, 210, 220, 430, 710, 900, 1002) configured to provide a second cell in which user equipment, UEs (110, 205, 410, 721, 800) may resume connections to the RAN (299, 704), configure the second RAN node to perform operations corresponding to any of the methods of claims 12-23.

Images