Radio resource control-state-independent radio resource management measurements

Abstract

A method of a user equipment (UE) in a wireless communications network, the method comprising: performing, whilst in a radio resource control connected (RRC_CONNECTED) state with the network, a plural

Description

BACKGROUND Field

[0001] Certain examples of the present disclosure provide approaches for radio resource control-state-independent radio resource management measurements. For example, certain examples of the present disclosure provide methods, apparatus and systems for radio resource control-state-independent radio resource management measurements in 3rd Generation Partnership Project (3GPP) networks such as LTE, 4th Generation (4G), 5th Generation (5G) and 6th Generation (6G) networks. Description of Related Art

[0002] The content of the following documents is referred to below and / or their content provides background information and context that the following disclosure should be considered in view of: [1] 3GPP TR 36.902 April 2011; Self-configuring and self-optimizing network (SON) use cases and solutions [2] 3GPP TS 38.331 v17.4.0 March 2023; NR; Radio Resource Control (RRC) protocol specification [3] - 3GPP TS 38.304 v17.4.0 April 2023; NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state [4] 3GPP TS 38.133 v18.1.0 April 2023; NR; Requirements for support of radio resource management [5] 3GPP TS 37.320 v17.3.0 March 2023 Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; [6] 3GPP RAN3#119 meeting Chair’s notes [7] 3GPP RAN3#119bis-e meeting Chair’s notes [8] 3GPP TS 38.423 v17.4.0 April 2023 [9] 3GPP TS 38.413 v17.4.0 April 2023 Other relevant documents include 3GPP: TS 36.331 17.4.0. March 2023 and TS 36.304 V17.4.0 March 2023 (LTE) and O-RAN Alliance: WG3 E2SM-RC and future E2SM evolvement. (Note: the example versions shown for each document are non-limiting, other versions of the documents may be considered also)

[0003] Wireless or mobile (cellular) communications networks in which a mobile terminal (e.g., user equipment (UE), such as a mobile handset) communicates via a radio link with a network of base stations, or other wireless access points or nodes, have undergone rapid development through a number of generations. The 3rd Generation Partnership Project (3GPP) design, specify and standardise technologies for mobile wireless communication networks. Fourth Generation (4G) and Fifth Generation (5G) systems are now widely deployed, and development of Sixth Generation (6G) Systems is in progress.

[0004] 3GPP standards for 4G systems include an Evolved Packet Core (EPC) and an Enhanced-UTRAN (E-UTRAN: an Enhanced Universal Terrestrial Radio Access Network). The E-UTRAN uses Long Term Evolution (LTE) radio technology. LTE is commonly used to refer to the whole system including both the EPC and the E-UTRAN, and LTE is used in this sense in the remainder of this document. LTE should also be taken to include LTE enhancements such as LTE Advanced and LTE Pro, which offer enhanced data rates compared to LTE.

[0005] In 5G systems a new air interface has been developed, which may be referred to as 5G New Radio (5G NR) or simply NR. NR is designed to support the wide variety of services and use case scenarios envisaged for 5G networks, though builds upon established LTE technologies. New frameworks and architectures are also being developed as part of 5G networks in order to increase the range of functionality and use cases available through 5G networks.

[0006] Within 3GPP systems, Radio Resource Measurements (RRM) or the results thereof may be used for the Radio Resource Control. The current (legacy) RRM measurements configuration requirements defined by 3GPP RAN WGs are statically linked to the currently used RRC protocol state in the UE (5G NR UE states and transitions are described in TR 38.912). As a result, their configuration must be updated (restarted) every time the RRC protocol state is changed (please note the UE state machine is reflected on the RAN side as they need to be in sync). This may be suboptimal as the state transition requires time and introduces latency e.g. to establish or release dedicated RRC signalling connection between the UE and RAN (when moving to or leaving the RRC connected state), reconfigure the UE radio protocol stack, receive new measurements control information from RAN in the UE etc. Such RRC state change may take up to tens of ms in 5G NR (e.g. 10 ms target requirement for transition from idle to connected RRC state in 3GPP TR 38.913 v17.0.0) depending on the transition type, RAN signalling load, etc. In a typical UE implementation this transition causes discontinuity in the RRM measurements - old measurements control configuration and actual cell measurements are deleted and stopped until the new configuration is received in the UE from RAN (using RRC signalling messages) and the serving and neighbour cells measurements could be restarted. Discontinuity is typically the longest during the transition between the RRC_IDLE and RRC_CONNECTED states as it is the most complex from the radio protocol stack point of view. There are various reasons why such measurements discontinuity is undesired from the mobile network performance point of view e.g.: - For fast moving UEs (e.g. used in trains or vehicles) which also change the RRC state frequently (e.g. due to the intermittent data traffic) may lead to the delayed RRM cells measurements evaluation required to trigger mobility procedures (handover or cell reselection) potentially causing data transmission latency and reduced user experience - As the UE RRM measurements may be indirectly used to optimise the RAN performance (e.g. by leveraging reporting them using MDT function) using SON mechanisms [1] or AI / ML algorithms, the discontinuity may negatively impact the performance of such optimisation approaches e.g. AI / ML based optimisation model training may be disrupted by the lack of continuous training data such as UE cell measurements. Such a problem(s) was recently identified by 3GPP RAN3 WG in its study ‘Artificial Intelligence (Al) / Machine Learning (ML) for NG-RAN’ (3GPP Tdoc RP-220635) which during 3GPP TSG-RAN WG3 #119 and 119bis-e meetings concluded the following, respectively: RAN3#119 meeting [6]: o There are the benefits in enabling UEs to continuously collect MDT measurement across RRC states and to provide to the network such continuous time series of data for the purpose of AI / ML Training / Retraining. The evaluation of gains vs impacts related to the use cases in R18 coming from potential solutions needs to be further discussed RAN3#119bis-e meeting [7]: o Continuous collection of MDT traces is beneficial only for AI / ML training in 0AM. Continuous MDT collection is to enable the continuous collection of MDT data from the same UE across RRC state changes (RRC-Connected, RRC_Idle, RRC_Inactive). However, RAN3 have not agreed on a solution for continuous collection of MDT: o Solutions on how to achieve Continuous MDTare FES

[0007] It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein.

[0008] The present disclosure introduces a solution for the RRM measurements discontinuity and indirectly helps with the issue of MDT measurements discontinuity, during the RRC state transitions, by defining the corresponding control plane architecture to support such RAN optimisations.

[0009] The present disclosure also proposes a solution to address the discontinuity of RRM measurements obtained during different RRC states, and also enable continuous MDT framework, to support RAN optimizations.

[0010] More specifically, the present disclosure removes the static mapping between the current UE RRC state and its measurements control and configuration, eliminating the need for the L1 / PHY measurements reconfiguration between the RRC connected and idle / inactive states transition. This gives the system more flexibility in terms of configuring and providing suitable UE cell measurements to the network (e.g. using MDT reporting) e.g. for the optimization purposes especially based on automated AI / ML, SON mechanisms etc. Further benefits beyond MDT and AI / ML features may also arise, for example improved UE mobility procedures between cells e.g. quicker cell reselection when leaving the RRC_CONNECTED state etc.

[0011] In accordance with a first aspect of the present disclosure, there is provided a method of a user equipment (UE) in a wireless communications network, the method comprising: performing, whilst in a radio resource control connected (RRC_CONNECTED) state with the network, a plurality of RRC_CONNECTED measurements; storing a result of the RRC_CONNECTED measurements; and reporting the results of the RRC_CONNECTED measurements to the network as minimisation of drive tests (MDT) data.

[0012] In an example of the present disclosure, the method further comprises receiving measurement configuration information from the network and performing the RRC_CONNECTED measurements based on the configuration information and / or reporting the results of the RRC_CONNECTED measurements based on the configuration information.

[0013] In an example of the present disclosure, the reporting is performed whilst the UE is in an RRC_CONNECTED state.

[0014] In an example of the present disclosure, the plurality of RRC_CONNECTED measurements are performed across a time period, and the results of the plurality of RRC_CONNECTED measurements are reported after the period of time.

[0015] In an example of the present disclosure, the results of the RRC_CONNECTED measurements are not reported immediately following the measurement.

[0016] In an example of the present disclosure, the reporting is performed during a transition of the UE from an RRC_CONNECTED state to an RRC_IDLE state or an RRCJNACTIVE state.

[0017] In an example of the present disclosure, an adapted version of the results of the RRC_CONNECTED measurements are reported to the network during a transition of the UE from an RRC_CONNECTED state to an RRC_IDLE state or an RRCJNACTIVE state.

[0018] In an example of the present disclosure, the results of the RRC_CONNECTED measurements are adapted to emulate a result of measurements performed in the RRCJDLE or an RRCJNACTIVE state.

[0019] In an example of the present disclosure, the results of the RRC_CONNECTED measurements are adapted to emulate a predetermined measurement periodicity.

[0020] In an example of the present disclosure, the RRC_CONNECTED measurements are performed at a first periodicity corresponding to the RRC_CONNECTED state, and the results of the RRC_CONNECTED measurements are adapted to emulate a second measurement periodicity corresponding to an RRCJDLE state or an RRCJNACTIVE state.

[0021] In an example of the present disclosure, the adaptation includes filtering of the results of the RRC_CONNECTED measurements.

[0022] In an example of the present disclosure, the adaptation is based on configuration information received from the network.

[0023] In an example of the present disclosure, the results of the RRC_CONNECTED measurements are utilised for AI / ML model training.

[0024] In an example of the present disclosure, the RRC_CONNECTED measurements are radio resource measurements (RRM) (e.g. UE cell measurements).

[0025] In an example of the present disclosure, the reporting is performed based on an MDT framework / procedure.

[0026] In an example of the present disclosure, the RRC_CONNECTED measurements are MDT measurements.

[0027] In an example of the present disclosure, the reporting is performed based on an RRC reporting procedure.

[0028] In an example of the present disclosure, the network is a 3GPP wireless communications network.

[0029] In accordance with a second aspect of the present disclosure, there is provided a user equipment (UE) for operation in a wireless communications network, the UE comprising a controller, a receiver, and a transmitter, wherein the controller in combination with the transmitter and the receiver are configured to perform any above-specified method.

[0030] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Embodiments / examples of the present disclosure are further described hereinafter with reference to the accompanying drawings, in which: Figure 1 provides an example 3GPP NR RRC UE measurements configuration for cell handover in RRC_CONNECTED; Figure 2 provides an example 3GPP NR RRC UE measurements configuration for cell reselection in RRC_IDLE and RRC_INACTIVE; Figure 3 provides an example 3GPP NR RRC UE state machine extended with emulated RRM measurements in accordance with the present disclosure; Figure 4 provides an example 3GPP NR RRC UE emulated measurements configuration for cell reselection in RRC_CONNECTED in accordance with the present disclosure; and Figure 5 provides a block diagram of an exemplary UE or network entity / function that may be used in certain examples of the present disclosure. DETAILED DESCRIPTION

[0032] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of certain examples of the present disclosure. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the disclosure.

[0033] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0034] Detailed descriptions of techniques, structures, constructions, functions or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0035] The terms and words used herein are not limited to the bibliographical or standard meanings, but are merely used to enable a clear and consistent understanding of the disclosure.

[0036] Throughout the description of this specification, the words “comprise”, “include” and “contain” and variations of the words, for example “comprising” and “comprises”, means “including but not limited to”, and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof.

[0037] Throughout the description of this specification, the singular form, for example “a”, “an” and “the”, encompasses the plural unless the context otherwise requires. For example, reference to “an object” includes reference to one or more of such objects.

[0038] Throughout the description, the expression “at least one of A, B and / or C” (or the like) and the expression “one or more of A, B and / or C” (or the like) should be seen to separately include all possible combinations, for example: A, B, C, A and B, A and C, A and B and C.

[0039] Throughout the description of this specification, language in the general form of “X for Y” (where Y is some action, process, operation, function, activity or step and X is some means for carrying out that action, process, operation, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.

[0040] Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment or example are to be understood to be applicable to any other aspect, embodiment or example described herein unless incompatible therewith.

[0041] The following examples are applicable to, and use terminology associated with, 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR). However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR), and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards (e.g., B5G, 5G-Advanced, 6G etc.). The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR) and / or 5G Advanced and / or 6G, and / or (3GPP Release 17, 18, 19, 20, etc.) or any other relevant standard. For example, the functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in other communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function, operation or purpose within the network.

[0042] Furthermore, the following also applies to the present disclosure: • The terms functionality / use-case / configuration / scenario / site may be used interchangeably. • The terms model and model functionality may be used interchangeably. • This disclosure also apply to non-3GPP entities. • The concepts, proposals, solutions, methods, embodiments, figures, and / or examples, presented in this disclosure, would apply to various type of communication systems, such as 4G, 4G-Advanced, 5G, 5G-Advanced, and 6G. Moreover, the above may also apply (in full or part or modified) to systems of Non-Terrestrial Networks (NR-NTN and / or loT-NTN and / or UAV, etc.), in addition to Terrestrial Networks (TN).

[0043] A particular network entity may be implemented as a network element on dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0044] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example: • The techniques disclosed herein are not limited to 3GPP 4G or 5G or 5G-Advanced and also apply to B5G and 6G systems. • One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations. • One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information. • One or more further elements, entities and / or messages may be added to the examples disclosed herein. • One or more non-essential elements, entities and / or messages may be omitted in certain examples. • The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example. • The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example. • Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example. • Information carried by two or more separate messages in one example may be carried by a single message in an alternative example. • The order in which operations are performed may be modified, if possible, in alternative examples. • The transmission of information between network entities is not limited to the specific form, type and / or order of messages described in relation to the examples disclosed herein.

[0045] Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Such an apparatus / device / network entity may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). Certain examples of the present disclosure may be provided in the form of a system (e.g., a network) comprising one or more such apparatuses / devices / network entities, and / or a method therefor. RRM Measurements Control

[0046] The present disclosure discloses a novel approach to control RRM measurements used by the RRC protocol defined for 5G New Radio (NR) in 3GPP TS 38.331 (for RRC connected state) and TS 38.304 (for RRC idle and inactive state) in 3GPP compliant Radio Access Networks (e.g. in NG-RAN defined in 3GPP TS 38.300 but also in 3G UMTS 3GPP TS 25.300 and 4G LTE 3GPP TS 36.300). These measurements configured by RRC protocol include e.g. serving cell and neighbouring cells received power (e.g. RSRP) and quality (e.g. RSRQ) which are used to support two User Equipment (UE) mobility procedures defined in 3GPP mobile systems: Cell handover (network controlled mobility) used in the RRC_CONNECTED state see Fig. 1 for measurement configuration details - Cell reselection (UE controlled mobility based on the network configuration) used in RRC_IDLE and RRCJNACTIVE states - - see Fig. 2 for measurement configuration details

[0047] Apart from the RRC mobility procedures, RRM measurements are also used by other RAN mechanisms e.g. such as ‘Radio measurement collection for Minimization of Drive Tests (MDT)’ defined in 3GPP TS 37.320 [5], The main difference in RRM cells measurements in the connected and idle / inactive RRC states is their periodicity i.e. significantly decreased in idle and inactive to reduce the UE energy consumption by allowing the UE protocol stack to enter ‘deep sleep’ state between the cells measurements. Detailed RRM measurements performance requirements (e.g. their configuration and periodicity) for 5G NR are defined in 3GPPTS 38.133.

[0048] The disclosure approach(es) leverages similarities between a RRM measurements defined and used in Radio Resource Control (RRC) protocol connected state (aka mode) and in the idle and inactive states.

[0049] More specifically, the present disclosure introduces emulated RRM cell measurements in the NR RRCJDLE, RRCJNACTIVE and RRC_CONNECTED states to enable RRC-state-independent RRM measurements (not possible in the state of the art approaches) - see Fig 3. It leverages common characteristics of both RRC connected and idle / inactive states in terms of the main cell measurements control and configuration mechanisms required for the UE mobility as defined in [2] and summarized in Table 1.

[0050] It is noted from Table 1 that system information can be acquired in RRC_IDLE I RRC_INACTIVE and RRC_CONNECTED states based on receiving broadcasted system information for the serving cell. Because of the availability of such system information (including cell measurements control information) and the UE ability to perform similar neighbouring cell measurements to support mobility when the UEs are at the RRC_CONNECTED state, the emulated UE RRM measurements for cell reselection (idle or active state behaviour) in the RRC_CONNECTED state can be performed - see Fig 4. As a result, these emulated UE RRM measurements are available immediately for use (e.g. for a cell reselection evaluation) during the state transition when the UE leaves the connected state and moves to the inactive or the idle state. They could be also leveraged for other RAN features such as MDT and reported to RAN e.g. using dedicated RRC signalling (e.g. NR RRC MeasurementReport or similar message). This measurement data could be then immediately reported to the related SON / AI algorithms performed in the relevant network entities. One of the advantages of this approach, comparing to the legacy approach, is that it allows the measurements continuity during the state transition, eliminating or reducing potential delays in other RAN procedures such as mobility and also improving network optimisation data quality. The proposed approach is currently not exploited in the existing cellular technologies.

[0051] It is also understood by a person skilled in the art that the SON / AI entity can be mapped to a network component that is based on a 3GPP based network architecture, where the SON / AI entity can be the SON component defined in RAN WG3 or OAM. It can also be based on a network architecture such as O-RAN, in which case the SON / AI entity may be considered as the near-RT RIC or Real-time RIC in an O-RAN architecture, and NW here are the E2 nodes in an O-RAN system. RRCJDLE / RRC_INACTIVE state RRC_CONNECTED state UE controlled mobility based on common broadcasted network configuration (from acquired System Information Blocks (SIB)) - cell reselection Network controlled mobility based on dedicated UE signalling (from RRC messages) - cell handover UE acquires common system information which may include as defined in [3]: - Measurement control information: periodicity (based on DRX cycle), cells, frequencies, RATs to be measured and their absolute priorities UE receives dedicated RRC signalling information which may include as defined in [2], For example: Measurement control information: periodicity, cells, frequencies, RATs to be - LI / PHY Averaging filter configuration measured, measurement gaps configuration etc UE performs serving and neighbouring cells measurements for UE triggered cell reselection UE performs serving and neighbouring cells measurements and measurements reporting (for network triggered HO) Table 1 - Comparison between NR RRC states and measurements control mechanisms required for the UE controlled and network controlled UE mobility procedures.

[0052] Figures 1 and 2 illustrate RRM cell measurements configuration for the RRC connected and idle / inactive states respectively. In particular, Figure 1 illustrates 3GPP NR RRC UE measurements configuration for cell handover in RRC_CONNECTED based on [2] and Figure 2 illustrates 3GPP NR RRC UE measurements configuration for cell reselection in RRC_IDLE and RRC_INACTIVE based on [3], Emulated idle / inactive State Measurements in RRC_CONNECTED

[0053] Even though cell reselection is (normally) not performed in the connected state, the RRM measurements for the proposed emulated cell reselection, could be performed in the UE ‘virtually’, in parallel to the RRM measurements for legacy HO, using the cell reselection configuration acquired from the system information and based on neighbouring cell measurements (see Fig.4).

[0054] However, considering that neighbouring cell measurements are (normally) performed more frequently in the connected state than in the idle state, the frequency of connected state measurements may need to be adopted (e.g. filtered) to become suitable for the idle / inactive state requirements (e.g. corresponding to the current Discontinuous Reception (DRX) Cycle). That is, using this approach, the UE in RRC connected state is able to emulate its measurements collection behaviour in the idle / inactive state measurements in parallel to the ongoing normal connected state measurement activity.

[0055] In summary, the idea is to re-use the same (or similar) RRM measurements of serving and neighbour cells, performed by the UE in the RRC connected state, for example, for the purpose of handover based mobility, with some sort of modification (adaptation or adjustment) in order to emulate the UE’s measurements collection configuration and behaviour in the RRC idle and / or inactive state. For example, this may require using measurements before L1 / PHY averaging filter is applied (if configured by the network a defined in [3]) and reducing their frequency. In another example, adapting (or adjusting) the measurement minimum period from 200ms, for intra-frequency measurements in the connected state [4] or less, to 1280ms in the typical system configuration.

[0056] The network may adjust the RRM measurements configuration in the connected state to help with making the emulated idle / inactive measurements more suitable for the current network optimisation requirements e.g. configure measurement gaps, additional measurements such as location reporting [2], etc.

[0057] In one example, the network configures the UE to re-use RRM measurements obtained for serving and neighbouring cells, during RRC connected state, as RRM measurements during RRC idle state.

[0058] In one example, the network may adapt the measurements configurations taking into consideration the AI / ML model life-cycle-management (LCM) procedures. For example, RRM measurements for model monitoring, training, and / or inference.

[0059] In one example, the network may adapt the measurement configurations taking into consideration the AI / ML model use case, functionality, scenario, and / or other assistance information obtained from the UE (or group of UEs). For example, information related to UE type, location, mobility (e.g. speed, trajectory), energy, altitude, information from other sensors etc.

[0060] In another example, the network may decide the measurements configurations (or data collection configurations) in different RRC states, for AI / ML models deployed at the network and / or UE. That is, network-side models, UE-side models, and / or two-sided (i.e. UE-partand network-part) models.

[0061] In an alternative example, the network may decide the measurement configurations (or data collection configurations) in different RRC states, for network-side and / or network-part of two-sided models, while the UE may decide the data collection configurations for the UE-side and the UE-part of two-sided models. In a related example, the UE may inform the network of the measurement configurations for different RRC states. In a related example, the UE may inform the network, either separately or as part of the measurements configurations indication, of the related AI / ML LCM purpose, and / or use case. Emulated Connected State Measurements in RRCJDLE or RRC_INACTIVE

[0062] For complementarity of the solution, there is also an opportunity for the UE to emulate the connected state measurements in non-connected RRC states (idle and inactive) (see Fig. 3). This may happen after the state transition to reduce the measurements discontinuity or independently e.g. the UE may continue or resume the RRM measurements based on the last known configuration received from dedicated RRC measurements control information. A possible disadvantage of this approach is that performing cell measurements in idle / inactive states may increase the energy consumption (as connected state measurements periodicity is typically higher than idle / inactive measurements as highlighted earlier) due to extra RF receiver activity reducing their opportunity to go to ‘deep sleep’ mode between measurements but may be tolerable for the UEs which have suitable power supply (large battery, vehicle UEs etc.) Emulated Measurements Configuration Signaling and Reporting Over Air interface Uu (TS 38.331)

[0063] The UE may need to inform the NW about its capability to perform the emulated measurements using existing RRC capability reporting procedures as defined in [2] (e.g. due to HW or SW resources constrains some UEs may have such preference) by introducing relevant capability flag. Then the network needs to inform the capable UE about the need to start or stop the emulated RRM measurements. Typically this could happen during the RRC state transition (although it could also happen independently from the state transition e.g. when the UE is continuously in the RRC_CONNECTED state) using the extended RRC protocol signalling messages triggering the UE state change or RRM / radio protocol stack reconfiguration such as RRCReconfiguration, RRCRelease, RRCResume etc a described in [2], This information could be controlled by a new information element in the RRC message such as the measurements start / stop flag or similar e.g. ENUMERATED type (start, pause, stop, ...others). An alternative solution is to include this new information element into the existing MDT signalling, defining a new RRC message etc.

[0064] Reporting of emulated UE measurements could be based on extending existing RRC measurement reporting procedures, MDT reporting procedures etc as defined in [2] and [5], Examples of Emulated Measurements Configuration Signaling and Reporting Over Xn Interface (TS 38.423)

[0065] In one example, the source NG-RAN node indicates to the target NG-RAN node that the UE (or a group of UEs) involved in a handover procedure from the source NG-RAN node to the target NG-RAN, can support the capability of emulating RRM measurements in the RRC_CONNECTED state (or RRC_IDLE / INACTIVE states as defined in section “Emulated connected state measurements in RRCJDLE or RRC_INACTIVE’ above). In another example, the source NG-RAN node indicates to the target NG-RAN node that the UE (or a group of UEs) are configured to emulate the RRM measurements in the RRC_CONNECTED state (or RRC_IDLE / INACTIVE states as defined in section "‘Emulated connected state measurements in RRC_IDLE or RRC_INACTIVE’ above).

[0066] In one example, the source NG-RAN node may include this indication in a new information element (IE), for instance EmulatedRRMMeasurements IE (or any other suitable naming, included in the HANDOVER REQUEST message (or any other newly defined suitable message).

[0067] In another example, the EmulatedRRMMeasurements IE may be set to “support” and included in the HANDOVER REQUEST message (or any other newly defined suitable message).

[0068] In another example, the EmulatedRRMMeasurements IE may be defined as ENUMERATED (start, pause, stop, ...others).

[0069] Upon reception of the EmulatedRRMMeasurements IE, contained in the HANDOVER REQUEST message, the target NG-RAN node shall, for example, - store the information received in the EmulatedRRMMeasurements IE in the UE context; - perform other actions related to RRM measurements.

[0070] In another example, if the EmulatedRRMMeasurements IE is included in the HANDOVER REQUEST message, - the target NG-RAN node shall if supported, activate the emulated RRM measurements collection, or start or stop the emulated RRM measurements session. - the target NG-RAN node shall if supported, store the emulated RRM measurements, and take it into account when performing an AI / ML LCM procedure. In another example, the measurements maybe provided as collected data for use in at least one (other) network entity (or function) in the network.

[0071] In another example, the source and / or the target NG-RAN node may perform some modification (or filtering or other processing or manipulation) of the emulated RRM measurements data before using this data and / or forwarding this data to another network entity for use in an AI / ML LCM procedure. Examples of Emulated Measurements Configuration Signaling and Reporting Over NG interface (TS 38.413)

[0072] In one example, the AMF indicates to the NG-RAN node that the UE (or a group of UEs) can support the capability of emulating RRM measurements in the RRC_CONNECTED state (or RRC_IDLE / INACTIVE states as defined in section “Emulated connected state measurements in RRC_IDLE or RRC_INACTIVE’ above).

[0073] In one example, the AMF includes information on the UE’s capability to support emulating RRM measurements, in any suitable exiting (or newly defined) NG signalling, messages, and / or lEs.

[0074] In an example, the INITIAL CONTEXT SETUP REQUEST message may contain the EmulatedRRMMeasurements IE, if available in the AMF.

[0075] Upon receipt of the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall store the received EmulatedRRMMeasurements IE in the UE context; perform other actions related to RRM measurements.

[0076] Figure 3 illustrates the UE state machine based on [2] extended with the proposed emulated RRM cell measurements, where the additions / extensions are indicated with a + (i.e. the text following the +).

[0077] Figure 4 illustrates the proposed emulated RRM cell measurements in RRC connected state, where the new aspects are within the dashed outline 400.

[0078] It will be appreciated that examples of the present disclosure may be realized in the form of hardware, software or a combination of hardware and software. Certain examples of the present disclosure may provide a computer program comprising instructions or code which, when executed, implement a method, system and / or apparatus in accordance with any aspect, example and / or embodiment disclosed herein. Certain embodiments of the present disclosure provide a machine-readable storage storing such a program.

[0079] Figure 5 is a block diagram of an exemplary network entity / function that may be used in examples of the present disclosure, such as the techniques disclosed in relation to any of the preceding figures. For example, any of the network entities, network function etc. may be provided in the form of the network entity illustrated in Figure 5. The skilled person will appreciate that a network entity / function may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0080] The entity 500 comprises a processor (or controller) 501, a transmitter 503 and a receiver 505. The receiver 505 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 503 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 501 is configured for performing one or more operations, for example according to the operations as described above.

[0081] Further examples in accordance with the present disclosure are set out below, where the examples may be combined in any appropriate form and also combined with any of the approaches set out above.

[0082] For all of the examples / aspects / embodiments etc. described above / herein, it should be considered that the corresponding features / operations apply in any order or combination, and that furthermore there exists the possibility to omit one or more features / operations.

[0083] Moreover, for all of the examples, embodiments, aspects etc. above, these apply to at least LTE, NR, NR NTN or loT NTN (note this list is merely to give some examples and should not be seen as limiting), including any related signalling / messages on any of the inferences X2, Xn, NG, S1, F1, etc (again, this list is merely to give some examples and should not be seen as limiting).It will be appreciated that, in each example / embodiment / aspect etc. described above, one or more features or operations may be omitted, modified or moved (e.g., to change the order of the features or the operations), if desired and appropriate.

[0084] Additionally, where the figures illustrating example method flows include text in relation to a specific step / operation, it will be appreciated that this text is simply an example of the corresponding step / operation, where a more general definition (such as may be found in the description of the corresponding step) may apply for the step / operation.

[0085] Additionally, regarding all of the above, one or more features or operations etc. from any example / embodiment may be combined with features or operations from any other example / embodiment. That is, the present disclosure should be considered to include all combinations of examples / embodiments disclosed herein, as appropriate, as well as combinations of individual features within and between each example / embodiment, as appropriate.

[0086] The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment or example disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.

[0087] It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like.

[0088] It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment and / or aspect disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

[0089] While the disclosure has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the disclosure.

[0090] The reader's attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference. Acronyms and Definitions 3GPP 3rd Generation Partnership Project 5G 5th Generation 5GC 5G Core 5QI 5G QoS Identifier 5GS 5G System 5GSM 5G System Session Management 5GMM 5G System Mobility Management AF Application Function Al Artificial Intelligence AM Acknowledged Mode AMF Access and Mobility Management Function AS Application Server ASP Application Service Provider ATG Air-To-Ground AUSF Authentication Server Function CDN Content Delivery Network DCAF Data Collection Application Function DNAI Data Network Access Identifier DNN Data Network Name DNS Domain Name Server DRB Data Radio Bearer eNB Evolved Node B EPC Evolved Packet Core FEC Forward Error Correction FQDN Fully Qualified Domain Name GBR Guaranteed Bit Rate gNB Next generation Node B GPSI Generic Public Subscription Identifier GW Gateway HSS Home Subscriber Service IAB Integrated Access and Backhaul ID Identity / ldentifier HoT Industrial Internet of Things IoT Internet of Things IMEI International Mobile Equipment Identities IP Internet Protocol l-SMF Intermediate SMF LADN Local Area Data Network LL SSM Lower Layer SSM MBMS Multimedia Broadcast / Multicast Service MBS Multicast / Broadcast Service MBSF Multicast / Broadcast Service Function MBSTF Multicast / Broadcast Service Transport Function MB-SMF Multicast / Broadcast Session Management Function MB-UPF Multicast / Broadcast User Plane Function MDT Minimization of Drive Test ML Machine Learning MME Mobility Management Entity MN Master Node MNF Monitoring Network Function MNO Mobile Network Operator MT Mobile Termination NAS Non-Access Stratum NEF Network Exposure Function NR New Radio NRF Network Repository Function NG-RAN Next Generation Radio Access Network NG-eNB Next Generation eNB NSA Non-Standalone NSSF Network Slice Selection Function NTN Non-Terrestrial Networks NW Network NWDAF Network Data Analytics Function OS Operating System OSAPP OS Application PCF Policy Control Function PCO Protocol Configuration Options PDR Packet Detection Rule PDU Protocol Data Unit PTM Point To Multipoint PTP Point to Point QFI QoS Flow Identifier (ID) QoS Quality of Service RACH Random Access Channel RAN Radio Access Network RRC Radio Resource Control RSD Route Selection Descriptor RSRP Reference Signal Received Power SA Standalone SDAP Service Data Adaptation Protocol SDU Service Data Unit SGW Serving Gateway SIM Subscriber Identity Module SLA Service Level Agreement SM Session Management SMF Session Management Function SN Secondary Node S-NSSAI Single Network Slice Selection Assistance Information SSB Synchronization Signal Block SSM Source Specific IP Multicast address SSC Session and Service Continuity SRB Signaling Radio Bearer SUPI Subscription Permanent Identifier TA Tracking Area TAI Tracking Area Identity TE Terminal Equipment TM Transparent Mode TMGI Temporary Mobile Group Identity TS Technical Specification UAV Unmanned Aerial Vehicle UDM Unified Data Manager UDR Unified Data Repository UE User Equipment UL Uplink UM Unacknowledged Mode UP User Plane UPF User Plane Function URLLC Ultra-Reliable and Low-Latency Communication URSP UE Route Selection Policy

Claims

1. A method of a user equipment (UE) in a wireless communications network, the method comprising:performing, whilst in a radio resource control connected (RRC_CONNECTED) state with the network, a plurality of RRC_CONNECTED measurements;storing a result of the RRC_CONNECTED measurements; andreporting the results of the RRC_CONNECTED measurements to the network as minimisation of drive tests (MDT) data.

2. The method of claim 1, further comprising receiving measurement configuration information from the network and performing the RRC_CONNECTED measurements based on the configuration information and / or reporting the results of the RRC_CONNECTED measurements based on the configuration information.

3. The method of any preceding claim, wherein the reporting is performed whilst the UE is in an RRC_CONNECTED state.

4. The method of any preceding claim, wherein the plurality of RRC_CONNECTED measurements are performed across a time period, and the results of the plurality of RRC_CONNECTED measurements are reported after the period of time.

5. The method of any preceding claim, wherein the results of the RRC_CONNECTED measurements are not reported immediately following the measurement.

6. The method of any preceding claim, wherein the reporting is performed during a transition of the UE from an RRC_CONNECTED state to an RRC_IDLE state or an RRC_INACTIVE state.

7. The method of any preceding claim, wherein an adapted version of the results of theRRC_CONNECTED measurements are reported to the network during a transition of the UE from an RRC_CONNECTED state to an RRC_IDLE state or an RRC_INACTIVE state.

8. The method of any preceding claim, wherein the results of the RRC_CONNECTED measurements are adapted to emulate a result of measurements performed in the RRCJDLE or an RRC_INACTIVE state.

9. The method of any preceding claim, wherein the results of the RRC_CONNECTED measurements are adapted to emulate a predetermined measurement periodicity.

10. The method of any preceding claim, wherein the RRC_CONNECTED measurements are performed at a first periodicity corresponding to the RRC_CONNECTED state, and the results of theRRC_CONNECTED measurements are adapted to emulate a second measurement periodicity corresponding to an RRC_IDLE state or an RRC_INACTIVE state.

11. The method of any of claims 7 to 10, wherein the adaptation includes filtering of the results of the RRC_CONNECTED measurements.

12. The method of any of claims 7 to 11, wherein the adaptation is based on configuration information received from the network.

13. The method of any preceding claim, wherein the results of the RRC_CONNECTED measurements are utilised for AI / ML model training.

14. The method of any preceding claim, wherein the RRC_CONNECTED measurements are radio resource measurements (RRM) (e.g. UE cell measurements).

15. The method of any preceding claim, wherein the reporting is performed based on an MDT fra me wo rk / proced u re.

16. The method of any preceding claim, wherein the RRC_CONNECTED measurements are MDT measurements.

17. The method of any preceding claim, wherein the reporting is performed based on an RRC reporting procedure.

18. The method of any preceding claim, wherein the network is a 3GPP wireless communications network.

19. A user equipment (UE) for operation in a wireless communications network, the UE comprising a controller, a receiver, and a transmitter, wherein the controller in combination with the transmitter and the receiver are configured to perform the method of any of claims 1 to 18.

Images