EP4670397A1

EP4670397A1 - EU MEASUREMENTS

Info

Publication number: EP4670397A1
Application number: EP24703109.9A
Authority: EP
Inventors: Riikka Karoliina DIMNIK; Jani-Pekka KAINULAINEN; Lars Dalsgaard
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2023-02-24
Filing date: 2024-01-22
Publication date: 2025-12-31
Also published as: MX2025009793A; GB2627508A; JP2026508248A; CN120752954A; GB202302712D0; KR20250154462A; WO2024175283A1

Abstract

Examples of the disclosure relate to improving efficiencies of UE measurements. In examples of the disclosure a UE is configured to receiving a message from a network entity. The message comprises control instructions for performing validations of one or more measurements during a connection setup. The UE is also configured to perform validations of the one or more measurements in accordance with the instructions.

Description

TITLE

UE Measurements

TECHNOLOGICAL FIELD

Examples of the disclosure relate to User Equipment (UE) measurements. Some relate to improving efficiencies of UE measurements.

BACKGROUND

A UE is expected to perform measurements and validations of the measurements during procedures such as connection setup/connection resume of Carrier Aggregation (CA) or the set up Dual Connectivity or other procedure. Any improvement in the efficiencies of these measurements will provide for improved power consumption at the UE.

BRIEF SUMMARY

According to various, but not necessarily all, examples of the disclosure there is provided a UE comprising means for: receiving a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing validations of the one or more measurements in accordance with the instructions.

The message comprising the control instructions may comprise at least one of: a connection setup message; a connection reconfiguration message; an information request message.

The connection setup message may comprise at least one of: an RRCSetup message; an RRCResume message.

The connection reconfiguration message may comprise an RRCReconfiguration message.

The control instructions may comprise at least one of: an indication whether to start performing the validations of the one or more measurements; an indication to stop all ongoing validations of the one or more measurements; an indication to stop a subset of ongoing validations of the one or more measurements; an indication to continue a subset of ongoing validations of the one or more measurements; an indication whether to report measurement availability and an indication for validation status for cancelled validations of the one or more measurements; a maximum duration for validation process.

The subset of measurements may be indicted by at least one of: cell carrier

Synchronization Signal Block (SSB)

Reference Signal (RS).

The UE may use an indicated maximum duration for validation process to select measurements to perform validation for.

The means may also be for enabling transmission of a report comprising an indication of at least one of: measurement availability for one or more measurements performed by the UE; validation status for one or more measurements performed by the UE.

The report may be transmitted in an information response message. The one or more measurements may comprise measurements for assisting at least one of: set up of Carrier Aggregation (CA); set up of Dual Connectivity (DC).

The validation process may comprise at least one or more of: cell detection; measurements of a cell; index reading.

At least some of the measurements and the validation process may be performed by the UE during at least one of: an idle mode or an inactive mode; connection setup.

According to various, but not necessarily all, examples of the disclosure there is provided a method comprising: receiving a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing validations of the one or more measurements in accordance with the instructions.

According to various, but not necessarily all, examples of the disclosure there is provided a computer program comprising instructions which, when executed by a UE, cause the UE to perform at least: receiving a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing validations of the one or more measurements in accordance with the instructions.

According to various, but not necessarily all, examples of the disclosure there is provided a network entity comprising means for: transmitting a message to a UE wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.

The subset of measurements may be indicted by at least one of: cell carrier

Synchronization Signal Block (SSB)

Reference Signal (RS). The UE may use an indicated maximum duration for validation process to select measurements to perform validation for.

The means may also be for receiving a report comprising an indication of at least one of: measurement availability for one or more measurements performed by the UE; validation status for one or more measurements performed by the UE.

The report may be received in an information response message.

The one or more measurements may comprise measurements for assisting at least one of: set up of Carrier Aggregation (CA); set up of Dual Connectivity (DC).

According to various, but not necessarily all, examples of the disclosure there is provided a method comprising: transmitting a message to a UE wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.

According to various, but not necessarily all, examples of the disclosure there is provided a computer program comprising instructions which, when executed by a network entity, cause the network entity to perform at least: transmitting a message to a UE wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.

While the above examples of the disclosure and optional features are described separately, it is to be understood that their provision in all possible combinations and permutations is contained within the disclosure. It is to be understood that various examples of the disclosure can comprise any or all of the features described in respect of other examples of the disclosure, and vice versa. Also, it is to be appreciated that any one or more or all of the features, in any combination, may be implemented by/comprised in/performable by an apparatus, a method, and/or computer program instructions as desired, and as appropriate.

BRIEF DESCRIPTION

Some examples will now be described with reference to the accompanying drawings in which:

FIG. 1 shows an example network;

FIGS. 2A and 2B show example methods;

FIG. 3 shows another example method;

FIG. 4 shows another example method;

FIG. 5 shows another example method; and

FIG. 6 shows an example controller.

The figures are not necessarily to scale. Certain features and views of the figures can be shown schematically or exaggerated in scale in the interest of clarity and conciseness. For example, the dimensions of some elements in the figures can be exaggerated relative to other elements to aid explication. Corresponding reference numerals are used in the figures to designate corresponding features. For clarity, all reference numerals are not necessarily displayed in all figures.

DEFINITIONS

AMF Access and Mobility Management Function CA Carrier Aggregation

DC Dual Connectivity

E-UTRA Evolved Universal Mobile Telecommunications System (UMTS)

Terrestrial Radio Access eEMR Enhanced EMR

EMR Early Measurement Reporting

FR2 Frequency Range 2 gNB NR base station

IE Information Element

MO Mobile Originated

NR New Radio

O-RAN Open-Radio Access Network

RAN Radio Access Network

RRC Radio Resource Control

RS Reference Signal

SCell Secondary Cell

SCG Secondary Cell Group

SIB System Information Block

SIM Subscriber Identity Module

SSB Synchronization Signal Block

UE User Equipment

DETAILED DESCRIPTION

Fig. 1 illustrates an example of a network 100 comprising a plurality of network entities including terminal apparatus 110, node apparatus 120 and one or more network apparatus 130. The terminal apparatus 110 and node apparatus 120 communicate with each other. The one or more network apparatus 130 communicate with the access nodes 120. In some examples the one or more network apparatus 130 communicate with the terminal apparatus 110.

The one or more network apparatus 130 can, in some examples, communicate with each other. The one or more node apparatus 120 can, in some examples, communicate with each other. The network 100 can be a cellular network comprising a plurality of cells 122 each served by a node apparatus 120. In this example, the interface between the terminal apparatus 110 and a node apparatus 120 defining a cell 122 is a wireless interface 124.

The node apparatus 120 comprises one or more cellular radio transceivers. The terminal apparatus 110 comprises one or more cellular radio transceivers.

In the example illustrated the cellular network 100 is a third generation Partnership Project (3GPP) network in which the terminal apparatus 110 are user equipment (UE) and the node apparatus 120 can be access nodes such as base stations.

The term ‘user equipment’ is used to designate mobile equipment comprising a smart card for authentication/encryption etc. such as a Subscriber Identity Module (SIM). In some examples the term ‘user equipment’ is used to designate mobile equipment comprising circuitry embedded as part of the user equipment for authentication/ encryption such as software SIM.

The node apparatus 120 can be any suitable base station. A base station is an access node. It can be a network element responsible for radio transmission and reception in one or more cells to or from the UE 110. The node apparatus 120 can be a network element in a Radio Access Network (RAN), an Open-Radio Access Network (O-RAN), a E-UTRA (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access) network, or any other suitable type of network.

The network apparatus 130 can be part of a core network. The network apparatus 130 can be configured to manage functions relating to connectivity for the UEs 110. For example, the network apparatus 130 can be configured to manage functions such as connectivity, mobility, authentication, authorization and/or other suitable functions. In some examples the network apparatus 130 can comprise an Access and Mobility management Function (AMF) or any other suitable entity.

In the example of Fig. 1 the network apparatus 130 is shown as a single entity. In some examples the network apparatus 130 could be distributed across a plurality of entities. For example, the network apparatus 130 could be cloud based or distributed in any other suitable manner.

The network 100 can be a 4G or 5G network, for example. It can for example be a New Radio (NR) network that uses gNB or eNB as access nodes 120. New Radio is the 3GPP name for 5G technology. In such cases the node apparatus 120 can comprise gNodeBs (gNBs) 120 configured to provide user plane and control plane protocol terminations towards the UE 110 and/or to perform any other suitable functions. The gNBs 120 are interconnected with each other by means of an X2/Xn interface 126. The gNBs are also connected by means of the N2 interface 128 to the network apparatus 130. The gNBs can be connected to an AMF or any other suitable network apparatus 130. Other types of networks and interfaces could be used in other examples. Other types of network could comprise next generation mobile and communication network, for example, a 6G network.

In networks 100 such as the network 100 of Fig. 1 when a connection is being set up or a connection is being resumed there is a benefit in having UE 110 measurements available early in connected mode. The benefit may be particularly relevant for a UE 110 transitioning from idle mode or inactive mode. For example, by decreasing the Frequency Range 2 (FR2) Secondary Cell/ Secondary Cell Group (SCell/SCG) setup/resume delay for a UE 110 connecting from idle mode or inactive mode there is a significant positive impact on the user throughput. The reduced delay will also have a positive impact on UE 110 power saving.

In NR networks 100 or other suitable networks early measurements can be configured in connection release messages that release a UE 110 to an idle or inactive mode. For example, the early measurements can be configured in an RRCRelease message or any other suitable type of message. In NR, and other suitable networks, both idle and inactive modes are supported for early measurements. For instance, a UE 110 can be configured to perform measurements until a given timer expires or is stopped. The timer could be T331 or any other suitable timer. This could be a mandatory part of the configuration which indicates for how long after release a UE 110 is required to perform early measurements. The measurements can then be used for assisting connected mode Carrier Aggregation (CA) and/or Dual Connectivity (DC) setup. The use of these measurements will limit the time taken to perform the measurements during CA and/or DC setup and can reduce power consumption of the UE 110.

The UE 110 can be configured to perform the measurements as indicated in the connection release message. The UE 110 does not need to perform measurements in an idle or inactive mode on a given carrier if the Synchronization Signal Block (SSB) configuration of that carrier provided via dedicated signaling is different from the SSB configuration broadcasted in the serving cell, if any.

If a UE 110 is not given carriers in the connection release message the UE 110 will measure carriers as listed in a suitable System Information Block (SIB) such as SIB11 (configuration for NR Cells in SIB5 in LTE). The UE 110 will perform the measurements in the idle or inactive mode only for the frequencies/carriers in the configured frequency list for which the UE 110 supports CA or DC between the frequency and the serving frequency/carrier.

Therefore, an Early Measurement Reporting (EMR) capable UE 110 can perform measurements in an idle mode or inactive mode until a timer such as T331 timer expires or is stopped. EMR UEs 110 can maintain the cells detectable from the connected mode until the timer expires or stopped. In the time interval between the expiry or stopping of the T331 timer the time that the UE 110 receives a connection setup or resume message it is unknown whether the cells are maintained. After the T331 timer expires, or is stopped it is dependent on UE 110 implementation whether the cells are maintained and detectable for early measurement reporting purposes. Based on UE 110 information indication and network information request the UE 110 can report the early measurement results after security is activated.

Figs. 2A and 2B show methods according to examples of the disclosure. The methods enable the network to control the validation processes for measurements that are performed by the UE 110.

The method of Fig. 2A could be implemented by a UE 110 or an apparatus within a UE 110 or by any other suitable terminal entity. At block 200 the method comprises receiving a message comprising control instructions for performing validations of one or more measurements during a connection setup. The message can be received from a network entity such as a gNB 120.

The measurements can comprise measurements that are performed by the UE 110 while the UE 110 is an idle mode or an inactive mode and/or measurements that are performed during connection setup and possibly during a period of time in connected mode. The measurements can comprise measurements that are used for assisting setup of CA or setup of DC. In some examples the measurements can comprise stored measurements. The stored measurements can be performed by the UE 110 prior to leaving connected mode.

The UE 110 can perform a validation process for the measurements it has performed or is performing. The validation process that is used will depend upon the type of measurements that have been made or are being made. The validation process can determine that the measurement results are still accurate or relevant or that the measurements satisfy one or more other appropriate criteria. For example, the validation process can determine if the measurements have been made during an appropriate time period or that they have obtained using an appropriate procedure. The validation process can comprise cell detection, measurements of a cell, index reading or any other suitable process.

The control instructions can comprise information that indicates how the UE 110 should perform the validations of the measurements. This can indicate whether the measurements and validations are needed or if only a subset of the measurements and validations are needed. The control instructions can enable the UE 110 to avoid making unnecessary measurements and performing unnecessary validations.

The control instructions can comprise an indication whether to start performing the validations of the one or more measurements, an indication to stop all ongoing validations of the one or more measurements, an indication to stop a subset of ongoing validations of the one or more measurements, an indication to continue a subset of ongoing validations of the one or more measurements, an indication whether to report measurement availability and an indication for validation status for cancelled validations of the one or more measurements, a maximum duration for validation process, or any other suitable indication or combination of indications.

In examples where the control instructions comprise an indication of a maximum duration for a validation process this could be a predefined duration, for example it could be defined in a standard or in any other suitable protocol.

Where a maximum validation has been indicated the UE 110 can use this information to select one or more measurements to perform validation for. For example, the UE 110 can select the measurements for which the validations can be completed within the maximum duration. The UE 110 could select not to perform the validations that cannot be completed within the maximum duration.

In examples where the control instructions indicate that a subset of validations are to be started or stopped the subset can be indicated in any suitable manner. For example, the subset can be indicated by, cell, carrier, Synchronization Signal Block (SSB), Reference Signal (RS) or in any other suitable manner.

The message comprising the control instructions could comprise a connection setup message, a connection reconfiguration message, an information request message or any other suitable type of message.

Where the message comprising the control instructions comprises a connection setup message the connection setup message can comprise an RRCSetup message, an RRCResume message or any other suitable type of message.

Where the message comprising the control instructions comprises a connection reconfiguration message the connection reconfiguration message can comprise an RRCReconfiguration message or any other suitable type of message.

At block 202 the method comprises performing validations of the one or more measurements in accordance with the instructions. For example, the UE 110 can start to perform the validation, can stop some ongoing validations or can select which validations are to be performed.

In some examples the UE 110 can also be configured to transmit a report indicating a measurement availability and/or a validation status for one or more measurements performed by the UE 110. The control instructions can comprise instructions relating to how the report is to be provided. For example, the control instructions could comprise an indication of the information that is to be included within the report or when the report is to be sent or any other suitable instruction.

The report can be transmitted in an information response message. For example, the report could be transmitted in a UElnformationResponse message or any other suitable type of message.

The report can comprise any suitable information relating to the measurements performed by the UE 110. In some examples the response can comprise an indication of any one or more of: measurements available, measurements not available, measurements ongoing (partially available), validation not started, validation ongoing, validation completed, cell detected, index availability (available/not available), or any other suitable information.

Fig. 2B shows another example method. The method of Fig. 2B could be implemented by a gNB 120 or an apparatus within a gNB 120 or other network entity.

The method comprises, at block 204, transmitting a message to a UE 110 wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup. The control instructions can comprise indicates how the UE 110 should perform the validations of the measurements. The control instructions can be as described herein.

Once the message has been transmitted to the UE 110 the UE 110 can perform the validations in accordance with the instructions. In some examples the gNB 120 can receive a report from the UE 110 where the report comprises an indication of measurement availability and/or validation status for one or more measurements performed by the UE 110. The report can be as described herein.

Fig. 3 shows another example method that can be implemented using a UE 110 and gNB 120. The UE 110 and the gNB 120 can be part of a network as shown in Fig. 1 or could be part of any other suitable type of network 100. In this example the network indicates to the UE 110 that the UE 110 is not to perform validation of the measurements. The UE 110 also does not report the status of the validations.

At block 300 the UE 110 is configured with FR2 SCell and enhanced EMR (eEMR) capabilities. The eEMR capabilities enable the UE 110 to implement examples of the disclosure. However, the UE 110 can also implement examples of the disclosure without support of these capabilities.

At block 302 the gNB 120 transmits a release message to the UE 110. The release message can be an RRCRelease message or any other suitable type of message. The release message can release or suspend an RRCConnection so that the UE 110 can enter an idle mode or an inactive mode.

At block 304 the UE 110 enters the idle mode or the inactive mode.

At block 306 the frequencies are re-evaluated after reselection.

At block 308 the gNB 120 sends a message to the UE 110 indicating which frequencies the UE 110 is to perform measurement for. The message could comprise a suitable System Information Block (SIB) such as SIB11.

At block 310 the gNB 120 sends a message to the UE 110 indicating the type of measurements that are to be performed. For example, it could indicate if the network needs NR or E-UTRA measurements. The message could comprise a suitable System Information Block (SIB) such as SIB2.

At block 312 the UE 110 performs measurements. The UE 110 performs measurements while in the idle mode or the inactive mode. The measurements can comprise any measurements that can assist with the setup of carrier aggregation or dual connectivity.

At block 314 the UE 110 transmits a connection request message to the gNB 120. The connection request message can comprise an RRCRequest message, an RRCResume message or any other suitable type of message. The connection request message can comprise information such as UE 110 identity and establishment cause.

In this example the control instructions for performing validations of one or more measurements during a connection setup can be sent in the connection request message. In this example the control instructions comprise an instruction to the UE 110 not to start to perform validation of the measurements. The control instructions can also comprise an instruction that the validation status of the measurements is not to be reported. These control instructions could be used in scenarios where the gNB 120 does not need the measurements. Other types of instructions, or combinations of instructions, could be provided in other examples of the disclosure.

In this example the control instructions are sent before the validation process has started. The control instructions could be sent at other times in other examples.

At block 316 the UE 110 does not perform validation of the measurements. In this case none of the validation processes are started.

At block 318 the UE 110 sends the setup complete message to the gNB 120. The setup complete message could be an RRCSetupComplete message or any other type of message. The setup complete message does not need to comprise a report regarding the validation status because the gNB 120 does not need this information.

At block 320 security is activated between the UE 110 and the gNB 120. Any suitable protocol can be used to activate the security.

Therefore, in the example of Fig. 3, the control instructions that are provided in the connection request message are used to prevent the UE 110 from performing unnecessary validation process. The control instructions prevent the UE 110 from starting the validation processes and so help to reduce power consumption at the UE 110.

If the control instructions not to start the validation process were not sent then the UE 110 could start the validation process according to an agreed procedure. This could be done without any specific control instructions from the gNB 120. For instance, if the setup message sent at block 314 comprises control instructions then the UE 110 will perform the validations in accordance with the control instructions but if the setup message sent at block 314 does not comprise any control instructions then the UE 110 will perform the validation process according to a default agreed procedure.

Variations to the methods shown in Fig. 3 could be used in examples of the disclosure.

For instance, in some examples the control instructions could be used to indicate to the UE 110 to start the validation process. In such cases the control instructions that are sent from the gNB 120 to the UE 110 could include an instruction to start to perform validation of the measurements. In such cases the control instructions can also comprise an instruction that the validation status of the measurements is to be reported.

The report of the can validation status of the measurements comprise any suitable information relating to the measurements performed by the UE 110. In some examples the response can comprise an indication of any one or more of: measurements available, measurements not available, measurements ongoing (partially available), validation not started, validation ongoing, validation completed, cell detected, index availability (available/not available), or any other suitable information.

Control instructions to start to perform validation of the measurements can be sent in any suitable message. The message can be sent before the UE 110 begins the validation processes. The message can be a connection request message similar to that shown in block 314 or could be any other suitable type of message.

In some cases the UE 110 might only perform the validations if the UE 110 receives control instructions from the GNB 120 indicating that the validation is to be started. Otherwise the default procedure for the UE 110 would be followed which, in this case, could be not to start the validations.

Other messages could be used by the gNB to transmit control instructions to the UE 110 indicating whether to start or not start to perform the validation process. For instance, in some examples an RRCReconfiguration could be used to provide the control instructions.

The control instructions to start or not start the validation process can be applied to all of the measurements or to a subset of the measurements. If the control instructions are only to be applied to a subset of the measurements, then the relevant subset of measurements can be indicated in the control instructions. For instance, the control instructions could indicate not to start the validations and a list of reference Signals (RS) or carrier or cell to which this instruction applies. In this case the UE 110 would not start the validation process for the indicated RS but would start the validation for the RS or carrier or cell that have not been indicated. Conversely in some examples the control instructions could indicate to start the validations and a list of reference Signals (RS) or carrier or cell to which this instruction applies. In this case the UE 110 would start the validation process for the indicated RS or carrier or cell but would not start the validation for the RS or carrier or cell that have not been indicated.

In the examples of Fig. 3 the control instructions are sent before the validation process has started. In other examples the control instructions could be sent while the validation processes are ongoing. Figs. 4 and 5 show example methods in which the gNB 120 sends the control instructions after the validation processes have started. In these examples the control instructions are sent in an information request message. The control instructions could be sent in any suitable message at any suitable time.

Fig. 4 shows another example method that can be implemented using a UE 110 and gNB 120. The UE 110 and the gNB 120 can be part of a network as shown in Fig. 1 or could be part of any other suitable type of network 100. In this example the network indicates to the UE 110 that the UE 110 is to stop performing validation processes that are ongoing. Blocks 300 to 312 can be as shown in Fig. 3. Corresponding reference numerals are used for corresponding blocks of the process.

At block 400 the UE 110 transmits a connection request message to the gNB 120. The connection request message can comprise an RRCRequest message, an RRCResume message or any other suitable type of message. The connection request message can comprise information such as UE 110 identity and establishment cause.

The example of Fig. 4 differs from the example of Fig. 3 because no control instructions for performing validation of one or more measurements are sent in the connection request message in the example of Fig. 4. Instead, the UE 110 starts to perform the validations at block 402. The validations could be started according to an agreed procedure.

At block 404 the UE 110 sends the setup complete message to the gNB 120. The setup complete message could be an RRCSetupComplete message or any other type of message and at block 406 security is activated between the UE 110 and the gNB 120. Any suitable protocol can be used to activate the security.

At block 408 an information request message is sent from the gNB 120 to the UE 110. The information request message can be a UElnformationRequest message or any other suitable type of message.

In the example of Fig. 4 the control instructions for performing validations of one or more measurements during a connection setup can be sent in the information request message. In this example the control instructions comprise an instruction to the UE 110 to stop the validation processes that are ongoing. This instruction can cause the UE 110 to stop the validation processes that were started at block 402.

The control instructions can also comprise an instruction that the validation status of the measurements is not to be reported. These control instructions could be used in scenarios where the gNB 120 does not need the measurements. Other types of instructions, or combinations of instructions, could be provided in other examples of the disclosure. At block 410 the UE 110 stops the validation of the measurements. This can stop any ongoing validation processes in accordance with the control instructions. Any timers overseeing the validation processes can be stopped or reset when the validation processes are stopped.

At block 412 the UE 110 responds to the information request message by sending an information response message to the gNB 120. The information response message can comprise a UElnformationResponse message or any other suitable type of message. The information response message can comprise the information that was requested in the information request message.

In some examples, the information response message can comprise a report indicating the measurement availability and the validation status for one or more measurements. The UE 110 can determine whether the report should be included in the information request message based on the control instructions. For instance, if the control instructions request a report for validations that have been completed then this information can be included in the information response message. If the control instructions request that no report is sent then no report needs to be sent in the information response message.

The report that is sent by the UE 110 can comprise any suitable information relating to the measurements performed by the UE 110. In some examples the response can comprise an indication of any one or more of: measurements available, measurements not available, measurements ongoing (partially available), validation not started, validation ongoing, validation completed, cell detected, index availability (available/not available), or any other suitable information.

Variations to this method could be used in examples of the disclosure.

For instance, in the example of Fig. 4 the control instructions can indicate to the UE 110 to stop the all of the ongoing validations. In some examples the gNB 120 might need the validations of some of the measurements. In such cases the control instructions that are sent from the gNB 120 to the UE 110 could include an instruction to continue the validation process for a subset of the measurements or targets. This can cause the UE 110 to stop the validation processes for the measurements that are not in the subset.

If the control instructions are only to be applied to a subset of the targeted measurements then the relevant subset of measurements can be indicated in the control instructions. For instance, the control instructions could indicate to continue the validations and a list of targets Reference Signals (RS) to which this instruction applies. The targets can comprise Reference Signals (RS), carriers or cells. In this case the UE 110 would continue the validation process for the indicated targets but would stop the validation for the targets that have not been indicated. Conversely in some examples the control instructions could indicate to stop the validations and a list of targets to which this instruction applies. In this case the UE 110 would stop the validation process for the indicated targets but would continue the validations for the targets that have not been indicated.

A field in the information request message, or any other suitable message, can be used to indicate the measurements to which the control instructions applies. If the control instruction is to be applied to all of the measurements the field could be left empty. That is, the control instructions need not be applied to any specific measurements. Fig. 5 shows an example method in which the gNB 120 can control the UE 110 to stop a subset of ongoing measurements.

Fig. 5 shows another example method that can be implemented using a UE 110 and gNB 120. The UE 110 and the gNB 120 can be part of a network as shown in Fig. 1 or could be part of any other suitable type of network 100. In this example the network indicates to the UE 110 that the UE 110 is to stop performing a subset of the validation processes that are ongoing.

Blocks 300 to 312 can be as shown in Figs. 3 and 4. Blocks 400 to 406 can be as shown in Fig. 4. Corresponding reference numerals are used for corresponding blocks of the process. At block 500 an information request message is sent from the gNB 120 to the UE 110. The information request message can be a UElnformationRequest message or any other suitable type of message.

In the example of Fig. 5 the control instructions for performing validations of one or more measurements during a connection setup can be sent in the information request message. In this example the control instructions comprise an instruction to the UE 110 to stop a subset of the validation processes that are ongoing. This instruction can cause the UE 110 to stop a subset of the validation processes that were started at block 402.

The control instructions can also comprise instructions relating to reporting the measurement availability and/or the validation status. For instance, the control instructions could comprise an instruction that the validation status of the measurements that have been stopped are not to be reported.

These control instructions could be used in scenarios where the gNB 120 only needs a subset of the measurements. Other types of instructions, or combinations of instructions, could be provided in other examples of the disclosure

At block 502 the UE 110 stops the validation of the measurements that have been indicated in the control instructions. This can stop a subset of the ongoing validation processes. Any timers overseeing the validation processes that have been stopped can be stopped or reset.

At block 504 the UE 110 responds to the information request message by sending an information response message to the gNB 120. The information response message can comprise a UElnformationResponse message or any other suitable type of message. The information response message can comprise the information that was requested in the information request message.

At block 506 the UE continues the validations for the other measurements that were not indicated in the control instructions. These validation procedures can proceed according to an agreed procedure. In some examples the UE 110 can send a report indicating the measurement availability and the validation status for one or more measurements to the UE 110. The report can be sent in any suitable message. For example, the information response message can comprise a report indicating the measurement availability and the validation status for one or more measurements. The UE 110 can determine whether the report should be included in the information request message based on the control instructions. For instance, if the control instructions request a report for validations that have been completed then this information can be included. If the control instructions request that no report is sent then no report needs to be sent in the information response message.

The report that is sent by the UE 110 can comprise any suitable information relating to the measurements performed by the UE 110. In some examples the response can comprise an indication of any one or more of: measurements available, measurements not available, measurements ongoing (partially available), validation not started, validation ongoing, validation completed, cell detected, index availability (available/not available), or any other suitable information. This information can be provided only for the subset of measurements that have been indicated in the control instructions.

Variations to this method could be used in examples of the disclosure. For instance, in the example of Fig. 5 the gNB 120 sends control instructions that indicate the subset of measurements for which the UE 110 is to stop the validation process. In other examples, the gNB 120 can send control instructions that indicate the subset of measurements or targets for which the UE 110 is to continue the validation process. This could be indicated in the information request as shown in Fig. 5 or in any other suitable message. In such examples the UE 110 would continue the validation process for the indicated measurements and stop the validation process for the measurements that have not been indicated.

Any suitable fields can be used to provide the control instructions in the respective messages. For instance, if the control instructions are to be used to indicate to the UE 110 to stop all validation processes a field STOP_VALIDATION = true/false could be included in the appropriate message. The indication does not need to be true/false. Other types of indication could be used such as a bit “0” or “1” indicating start or stop. In some examples the indications could be part of a configuration bitmap. The bitmap can comprise multiple bits. For instance, 0001 would indicate to stop measurements for three cells but start for one.

If the control instructions are to be used to indicate to the UE 110 to stop a subset of validation processes a field STOP_VALIDATION = true + list of affected targets. The affected targets can be indicated by a list of RS indices, cells, carriers or any combination of these. These control instructions could cause the UE 110 to stop the indicated measurements and continue all other measurements.

In some examples the control instructions can also comprise instructions indicating to the UE 110 whether to provide a report relating to the measurement availability and/or the validity status. In some cases, the reporting of this information could use a default agreed procedure. This default agreed procedure can be replaced if the appropriate instructions are provided from the gNB 120. Any suitable field in the appropriate messages could be used by the gNB 120 to provide an instruction relating to the reporting of information. For instance, in some cases a field STOP_VALIDATION = true could indicate to the UE 110 to stop the validation process and also not to respond to the information request. That is, it can indicate not to send the information response message and/or not to send the report in any other suitable message. The indication does not need to be true/false. Other types of indication could be used such as a bit “0” or “1” indicating start or stop. In some examples the indications could be part of a configuration bitmap. The indication can indicate whether to stop or start the validation of the measurements for one or more targets.

In some examples the UE 110 could be configured to always send the report on the measurement availability and/or the validity status for any measurements that have been requested. In some cases the gNB 120 can indicate to the UE 110 to provide the report for measurements that have been validated when the validation of all of, or a subset of, the measurements is stopped. This could be indicated using any suitable field such as a REPORT = true/false indicating whether to report the measurement results and the validation status. The indication does not need to be true/false. Other types of indication could be used such as a bit “0” or “1” indicating start or stop. In some examples the indications could be part of a configuration bitmap.

In some examples the control instructions could indicate a maximum allowed duration for the validation processes. This could indicate the maximum duration for the process from the moment UE 110 receives the connection request message until the moment the UE 110 has to stop the validation process and continue in RRC connected mode. In some examples the maximum allowed duration could be predefined in a standard. In other examples the maximum allowed duration might not be defined in a standard but could be defined by any other suitable means.

The gNB 120 can send control instructions indicating a maximum allowed duration to the UE 110 in any suitable message. In some examples the control instructions indicating a maximum allowed duration could be sent to the UE 110 before the validation process has begun. For instance, the control instructions could be sent in a connection request message, in and SIB or measurement configuration message or any other suitable type of message.

In some examples the control instructions indicating a maximum allowed duration could be sent to the UE 110 after the validation process has begun. This could be used if the network 100 want to change the defined or previously signaled maximum allowed duration. In such cases the control instructions indicating a maximum allowed duration could be sent in an information request message or in any other suitable message.

In some examples the UE 110 might be requires to response to the information request message immediately. In such examples the gNB 120 can be configured to send multiple information request messages and the gNB 120 can adjust the time it will request for any results based on the indicated maximum allowed duration. In some cases the UE 110 can be configured to postpone the response to the information request message. In such cases the UE 110 will postpone the information response message until the maximum validation duration is over. The UE 110 can decide which measurements are to be validated based, at least in part, on the maximum allowed duration. The maximum allowed duration could be shorter than the time it might take for the UE 110 to validate some of the measurements. The UE 110 can evaluate how long validating respective measurements will take, and only start validation of measurements that can be validated in a time shorter or equal to the maximum validation duration. The UE 110 can evaluate how long validating respective measurements will take by calculating how long index reading takes, calculating how long measurements associated with the validation) take, assuming that the cell is detected, and/or any other process or combination of processes.

All the methods described herein can be used either alone or as any kind of combination to allow better control of the validation processes performed by the UE 110.

A benefit of allowing the gNB 120 to control the validation processes performed by the UE 110 as described herein is that the UE 110 does not need to spend unnecessary time or power validating measurements that the network 100 might not be interested to use in the SCell/SCG activation. The methods described herein also allow the network 100 and the UE 110 to react to sudden changes during the activation process.

Fig. 6 illustrates an example of a controller 600. The controller 600 could be provided within an apparatus such as a UE 110 or a network apparatus. Implementation of a controller 600 may be as controller circuitry. The controller 600 may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware).

As illustrated in Fig. 6 the controller 600 can be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program 606 in a general-purpose or special-purpose processor 602 that may be stored on a computer readable storage medium (disk, memory etc.) to be executed by such a processor 602. The processor 602 is configured to read from and write to the memory 604. The processor 602 may also comprise an output interface via which data and/or commands are output by the processor 602 and an input interface via which data and/or commands are input to the processor 602.

The memory 604 stores a computer program 606 comprising computer program instructions (computer program code) that controls the operation of the apparatus when loaded into the processor 602. The computer program instructions, of the computer program 606, provide the logic and routines that enables the apparatus to perform the methods illustrated in the Figs. The processor 602 by reading the memory 604 is able to load and execute the computer program 606.

In examples where the controller 600 is provided within a UE 110 the controller 600 therefore comprises: at least one processor 602; and at least one memory 604 storing instructions that, when executed by the at least one processor 602, cause a UE 110 at least to perform: receiving 200 a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing 202 validations of the one or more measurements in accordance with the instructions.

In examples where the controller 600 is provided within a gNB 120 the controller 600 therefore comprises: at least one processor 602; and at least one memory 604 storing instructions that, when executed by the at least one processor 602, cause a UE 110 at least to perform: transmitting 204 a message to a UE 110 wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.

The computer program 606 may arrive at the UE 110 via any suitable delivery mechanism 608. The delivery mechanism 608 may be, for example, a machine readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a Compact Disc Read-Only Memory (CD-ROM) or a Digital Versatile Disc (DVD) or a solid-state memory, an article of manufacture that comprises or tangibly embodies the computer program 606. The delivery mechanism may be a signal configured to reliably transfer the computer program 606. The apparatus may propagate or transmit the computer program 606 as a computer data signal.

The computer program 606 can comprise computer program instructions for causing a UE 110 to perform at least the following or for performing at least the following: receiving 200 a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing 202 validations of the one or more measurements in accordance with the instructions.

The computer program 606 can comprise computer program instructions for causing a gNB 120 to perform at least the following or for performing at least the following: transmitting 204 a message to a UE 110 wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.

The computer program instructions may be comprised in a computer program, a non- transitory computer readable medium, a computer program product, a machine readable medium. In some but not necessarily all examples, the computer program instructions may be distributed over more than one computer program.

Although the memory 604 is illustrated as a single component/circuitry it may be implemented as one or more separate components/circuitry some or all of which may be integrated/removable and/or may provide permanent/semi-permanent/ dynamic/cached storage.

Although the processor 602 is illustrated as a single component/circuitry it may be implemented as one or more separate components/circuitry some or all of which may be integrated/removable. The processor 602 may be a single core or multi-core processor. References to ‘computer-readable storage medium’, ‘computer program product’, ‘tangibly embodied computer program’ etc. or a ‘controller’, ‘computer’, ‘processor’ etc. should be understood to encompass not only computers having different architectures such as single /multi- processor architectures and sequential (Von Neumann)/parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices and other processing circuitry. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.

As used in this application, the term ‘circuitry’ may refer to one or more or all of the following:

(a) hardware-only circuitry implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable):

(i) a combination of analog and/or digital hardware circuit(s) with software/firmware and

(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions and

(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g. firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device. The stages illustrated in Figs. 2 to 5 can represent steps in a method and/or sections of code in the computer program 606. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it can be possible for some blocks to be omitted.

Where a structural feature has been described, it may be replaced by means for performing one or more of the functions of the structural feature whether that function or those functions are explicitly or implicitly described.

The term ‘comprise’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising Y indicates that X may comprise only one Y or may comprise more than one Y. If it is intended to use ‘comprise’ with an exclusive meaning then it will be made clear in the context by referring to “comprising only one...” or by using “consisting”.

In this description, the wording ‘connect’, ‘couple’ and ‘communication’ and their derivatives mean operationally connected/coupled/in communication. It should be appreciated that any number or combination of intervening components can exist (including no intervening components), i.e., so as to provide direct or indirect connection/coupling/communication. Any such intervening components can include hardware and/or software components.

As used herein, the term "determine/determining" (and grammatical variants thereof) can include, not least: calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (for example, looking up in a table, a database or another data structure), ascertaining and the like. Also, "determining" can include receiving (for example, receiving information), accessing (for example, accessing data in a memory), obtaining and the like. Also, " determine/determining" can include resolving, selecting, choosing, establishing, and the like.

In this description, reference has been made to various examples. The description of features or functions in relation to an example indicates that those features or functions are present in that example. The use of the term ‘example’ or ‘for example’ or ‘can’ or ‘may’ in the text denotes, whether explicitly stated or not, that such features or functions are present in at least the described example, whether described as an example or not, and that they can be, but are not necessarily, present in some of or all other examples. Thus ‘example’, ‘for example’, ‘can’ or ‘may’ refers to a particular instance in a class of examples. A property of the instance can be a property of only that instance or a property of the class or a property of a sub-class of the class that includes some but not all of the instances in the class. It is therefore implicitly disclosed that a feature described with reference to one example but not with reference to another example, can where possible be used in that other example as part of a working combination but does not necessarily have to be used in that other example.

Although examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims.

Features described in the preceding description may be used in combinations other than the combinations explicitly described above.

Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not.

Although features have been described with reference to certain examples, those features may also be present in other examples whether described or not.

The term ‘a’, ‘an’ or ‘the’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising a/an/the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use ‘a’, ‘an’ or ‘the’ with an exclusive meaning then it will be made clear in the context. In some circumstances the use of ‘at least one’ or ‘one or more’ may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning.

The presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and also to features that achieve substantially the same technical effect (equivalent features). The equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. The equivalent features include, for example, features that perform substantially the same function, in substantially the same way to achieve substantially the same result.

In this description, reference has been made to various examples using adjectives or adjectival phrases to describe characteristics of the examples. Such a description of a characteristic in relation to an example indicates that the characteristic is present in some examples exactly as described and is present in other examples substantially as described.

The above description describes some examples of the present disclosure however those of ordinary skill in the art will be aware of possible alternative structures and method features which offer equivalent functionality to the specific examples of such structures and features described herein above and which for the sake of brevity and clarity have been omitted from the above description. Nonetheless, the above description should be read as implicitly including reference to such alternative structures and method features which provide equivalent functionality unless such alternative structures or method features are explicitly excluded in the above description of the examples of the present disclosure.

Whilst endeavoring in the foregoing specification to draw attention to those features believed to be of importance it should be understood that the Applicant may seek protection via the claims in respect of any patentable feature or combination of features hereinbefore referred to and/or shown in the drawings whether or not emphasis has been placed thereon. l/we claim:

Claims

1 . A UE comprising means for: receiving a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing validations of the one or more measurements in accordance with the instructions.

2. A UE as claimed in claim 1 wherein the message comprising the control instructions comprises at least one of: a connection setup message; a connection reconfiguration message; an information request message.

3. A UE as claimed in claim 2 wherein the connection setup message comprises at least one of: an RRCSetup message; an RRCResume message.

4. A UE as claimed in claim 2 wherein the connection reconfiguration message comprises an RRCReconfiguration message.

5. A UE as claimed in any preceding claim wherein the control instructions comprise at least one of: an indication whether to start performing the validations of the one or more measurements; an indication to stop all ongoing validations of the one or more measurements; an indication to stop a subset of ongoing validations of the one or more measurements; an indication to continue a subset of ongoing validations of the one or more measurements; an indication whether to report measurement availability and an indication for validation status for cancelled validations of the one or more measurements; a maximum duration for validation process.

6. A UE as claimed in claim 5 wherein the subset of measurements are indicted by at least one of: cell carrier

Synchronization Signal Block (SSB)

Reference Signal (RS).

7. A UE as claimed in claim 5 wherein the UE uses an indicated maximum duration for validation process to select measurements to perform validation for.

8. A UE as claimed in any preceding claim wherein the means are also for enabling transmission of a report comprising an indication of at least one of: measurement availability for one or more measurements performed by the UE; validation status for one or more measurements performed by the UE.

9. A UE as claimed in claim 8 wherein the report is transmitted in an information response message.

10. A UE as claimed in any preceding claim wherein the one or more measurements comprises measurements for assisting at least one of: set up of Carrier Aggregation (CA); set up of Dual Connectivity (DC).

11. A UE as claimed in any preceding claim wherein the validation process comprises at least one or more of: cell detection; measurements of a cell; index reading.

12. A UE as claimed in any preceding claim wherein at least some of the measurements and the validation process are performed by the UE during at least one of: an idle mode or an inactive mode; connection setup.

13. A method comprising: receiving a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing validations of the one or more measurements in accordance with the instructions.

14. A computer program comprising instructions which, when executed by a UE, cause the UE to perform at least: receiving a message from a network entity wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup; and performing validations of the one or more measurements in accordance with the instructions.

15. A network entity comprising means for: transmitting a message to a UE wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.

16. A network entity as claimed in claim 15 wherein the message comprising the control instructions comprises at least one of: a connection setup message; a connection reconfiguration message; an information request message.

17. A network entity as claimed in claim 16 wherein the connection setup message comprises at least one of: an RRCSetup message; an RRCResume message.

18. A network entity as claimed in claim 16 wherein the connection reconfiguration message comprises an RRCReconfiguration message.

19. A network entity as claimed in any of claims 15 to 18 wherein the control instructions comprise at least one of: an indication whether to start performing the validations of the one or more measurements; an indication to stop all ongoing validations of the one or more measurements; an indication to stop a subset of ongoing validations of the one or more measurements; an indication to continue a subset of ongoing validations of the one or more measurements; an indication whether to report measurement availability and an indication for validation status for cancelled validations of the one or more measurements; a maximum duration for validation process.

20. A network entity as claimed in claim 19 wherein the subset of measurements are indicted by at least one of: cell carrier

Synchronization Signal Block (SSB)

Reference Signal (RS).

21. A network entity as claimed in claim 19 wherein the UE uses an indicated maximum duration for validation process to select measurements to perform validation for.

22. A network entity as claimed in any of claims 15 to 21 wherein the means are also for receiving a report comprising an indication of at least one of: measurement availability for one or more measurements performed by the UE; validation status for one or more measurements performed by the UE.

23. A network entity as claimed in claim 22 wherein the report is received in an information response message.

24 A network entity as claimed in any of claims 15 to 23 wherein the one or more measurements comprises measurements for assisting at least one of: set up of Carrier Aggregation (CA); set up of Dual Connectivity (DC).

25. A network entity as claimed in any of claims 15 to 24 wherein the validation process comprises at least one or more of: cell detection; measurements of a cell; index reading.

26. A network entity as claimed in any of claims 15 to 25 wherein at least some of the measurements and the validation process are performed by the UE during at least one of: an idle mode or an inactive mode; connection setup.

27. A method comprising: transmitting a message to a UE wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.

28. A computer program comprising instructions which, when executed by a network entity, cause the network entity to perform at least: transmitting a message to a UE wherein the message comprises control instructions for performing validations of one or more measurements during a connection setup.