Measurement gap control

Abstract

Examples of the disclosure relate to flexibility of measurement gap control. A network node configures a user equipment (UE) with a measurement window. The measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions. The network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements. The network node determines if data has been scheduled on a threshold number of measurement gap occasions within the measurement window and determines whether to schedule data during a measurement gap occasion based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window.

Description

[0001] TITLE

[0002] Measurement Gap Control

[0003] TECHNOLOGICAL FIELD

[0004] Examples of the disclosure relate to measurement gap control. Some relate to providing flexibility as to whether a measurement gap is used for performing measurements or for scheduled data.

[0005] BACKGROUND

[0006] Measurements can be used for procedures such as cell selection, cell reselection, power control calculations, mobility procedures, beam management, or any other suitable procedures. Measurements can be performed by User Equipments (UEs). Measurement gaps are used to enable a UE to perform the measurements when the UE is in RRC connected and cannot perform measurements in parallel to receiving or transmitting data corresponding to the connection. In a period defined by a measurement gap the UE does not send or receive data.

[0007] BRIEF SUMMARY

[0008] According to various, but not necessarily all, examples of the disclosure there is provided a network node comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network node to perform at least: configuring a user equipment (UE) with a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data has been scheduled on a threshold number of measurement gap occasions within the measurement window; and determining whether to schedule data during a measurement gap occasion based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window.

[0009] The threshold number of measurement gap occasions may be set to ensure that the configured number of measurements are secured within the measurement window.

[0010] If it is determined that data has been scheduled on a threshold number of measurement gap occasions the network node may be arranged to determine not to schedule data on any more measurement gap occasions within the measurement window.

[0011] If it is determined that data has not been scheduled on a threshold number of measurement gap occasions one or more remaining measurement gap occasions within the measurement window may be available to be used for scheduled data.

[0012] The measurement window may be applicable to multiple frequency ranges.

[0013] The measurement window may be applicable to a single frequency range.

[0014] The processor and memory may be arranged to cause the network node to perform configuring different UEs with different measurement windows.

[0015] The at least one processer and at least one memory may be arranged to cause the network node to perform using a medium access control - control element (MAC-CE) to activate or deactivate the configured measurement window.

[0016] Activation or deactivation of the measurement window may be determined based, at least in part, on scheduling requirements of the network node.

[0017] According to various, but not necessarily all, examples of the disclosure there is provided a method comprising: configuring a user equipment (UE) with a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data has been scheduled on a threshold number of measurement gap occasions within the measurement window; and determining whether to schedule data during a measurement gap occasion based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window.

[0018] 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 node, cause the network node to perform: configuring a user equipment (UE) with a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data has been scheduled on a threshold number of measurement gap occasions within the measurement window; and determining whether to schedule data during a measurement gap occasion based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window.

[0019] According to various, but not necessarily all, examples of the disclosure there is provided a user equipment (UE) comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the UE to perform at least: receiving a configuration from a network node, the configuration comprising a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data is scheduled within a given time period of a measurement gap occasion; and performing measurements based on whether data is scheduled within the given time period of the measurement gap occasion.

[0020] Performing measurements based on whether data is scheduled may comprise performing measurements in a measurement gap occasion if no data is scheduled within the given time period of the measurement gap occasion and refraining from performing measurements if data is scheduled within the given time period of the measurement gap occasion.

[0021] The at least one processer and at least one memory may be arranged to cause the UE to perform determining that all remaining measurement gap occasions in the measurement window are to be kept free from scheduled data to meet the configured number of measurement gap occasions and refraining from determining if data is scheduled within a given time period of the measurement gap occasions.

[0022] The at least one processor and at least one memory may be arranged to cause the UE to perform at least one of: receiving scheduled data during a measurement gap occasion that is not used for performing measurements; refraining from performing measurements during a measurement gap occasion that is scheduled for data.

[0023] Data may be determined to be scheduled within a given time period of the measurement gap occasion if any data is scheduled within a defined number of slots of the measurement gap occasion. The measurement window may be applicable to multiple frequency ranges.

[0024] The measurement window may be applicable to a single frequency range.

[0025] The measurement window may be specific to the UE.

[0026] The at least one processer and at least one memory may be arranged to cause the UE to perform receiving a medium access control - control element (MAC-CE) to activate or deactivate the configured measurement window.

[0027] According to various, but not necessarily all, examples of the disclosure there is provided a method comprising: receiving a configuration from a network node, the configuration comprising a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data is scheduled within a given time period of a measurement gap occasion; and performing measurements based on whether data is scheduled within the given time period of the measurement gap occasion.

[0028] 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: receiving a configuration from a network node, the configuration comprising a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data is scheduled within a given time period of a measurement gap occasion; and performing measurements based on whether data is scheduled within the given time period of the measurement gap occasion.

[0029] According to various, but not necessarily all, embodiments there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least a part of one or more methods described herein.

[0030] According to various, but not necessarily all, embodiments there is provided an apparatus comprising means for performing at least part of one or more methods described herein. The description of a function and / or action should additionally be considered to also disclose any means suitable for performing that function and / or action. Functions and / or actions described herein can be performed in any suitable way using any suitable method.

[0031] According to various, but not necessarily all, embodiments there is provided examples as claimed in the appended claims.

[0032] 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 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 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. The description of a function should additionally be considered to also disclose any means suitable for performing that function BRIEF DESCRIPTION

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

[0034] FIG. 1 shows an example network;

[0035] FIG. 2 shows an example measurement gap configuration;

[0036] FIG. 3 shows an example measurement gap pattern;

[0037] FIGS. 4A and 4B show example methods;

[0038] FIG. 5 shows an example measurement gap window;

[0039] FIG. 6 shows an example measurement gap window;

[0040] FIGS. 7A and 7B show example methods; and

[0041] FIG. 8 shows an example controller.

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

[0043] DEFINITIONS

[0044] BWP Bandwidth Part gNB Base Station

[0045] MAC-CE Medium Access Control - Control Element

[0046] MGL Measurement Gap Length

[0047] MGRP Measurement Gap Repetition Period

[0048] PDCCH Physical Downlink Control Channel

[0049] RAT Radio Access Technology

[0050] RRC Radio Resource Control

[0051] SSB Synchronization Signal Blocks

[0052] UE User Equipment DETAILED DESCRIPTION

[0053] Fig. 1 illustrates an example of a communications network 100. The network 100 comprises a plurality of different types of nodes 110, 120, 130. The different types of nodes can comprise terminal nodes 110, network nodes 120 and core network nodes 130 and / or any other suitable type of nodes.

[0054] The network 100 is in this example a radio telecommunications network, in which at least some of the terminal nodes 110 and network nodes 120 communicate with each other using transmission / reception of radio waves.

[0055] The network nodes 120 can be configured to communicate with the terminal nodes 110. The one or more core network nodes 130 communicate with the network nodes 120. In some examples the one or more core network nodes 130 communicate with the terminal nodes 110.

[0056] The one or more core network nodes 130 can, in some examples, communicate with each other. The one or more network nodes 120 can, in some examples, communicate with each other.

[0057] The network 100 can be a cellular network comprising a plurality of cells 122. Each of the cells is served by a network node 120. The network node 120 can provide an access node. In this example, the interface between the terminal nodes 110 and a network node 120 defining a cell 122 is a wireless interface 124.

[0058] The network node 120 comprises one or more cellular radio transceivers. The terminal node 110 comprises one or more cellular radio transceivers.

[0059] In the example illustrated the cellular network 100 is a third generation Partnership Project (3GPP) standard compliant network in which the terminal nodes 110 are user equipment (UE) and the network nodes 120 can be access nodes such as base stations (gNB). The UE can comprise a mobile equipment. A network node 120 can be a network entity responsible for radio transmission and reception in one or more cells to or from the UE 110. A network node 120 can be a network element in a Radio Access Network (RAN), an Open-Radio Access Network (O-RAN), a E-LITRA (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access) network, or any other suitable type of network.

[0060] The core network nodes 130 can be part of a core network. The core network nodes 130 can be configured to manage functions relating to connectivity for the UEs 110. For example, the core network nodes 130 can be configured to manage functions such as connectivity, mobility, authentication, authorization and / or other suitable functions.

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

[0062] In some examples the network 100 can be a Fifth Generation (or New Radio, NR) Radio Access network (NG-RAN). The NG-RAN consists of gNodeBs (gNBs) 120, providing the user plane and control plane (RRC) protocol terminations towards the UE 110. The gNBs 120 are interconnected with each other by means of a network interface such as an X2 / Xn interface 126. The gNBs 120 are also connected by means of the NG interface 128 to core network nodes 130 such as the Access and Mobility management Function (AMF).

[0063] In some examples the network 100 can be an Evolved Universal Terrestrial Radio Access network (E-UTRAN). The E-UTRAN consists of E-UTRAN NodeBs (eNBs) 120, providing the E-UTRA user plane and control plane (RRC) protocol terminations towards the UE 110. The eNBs 120 can be interconnected with each other by means of an X2 interface 126. The eNBs can also be connected by means of the S1 interface to the Mobility Management Entity (MME).

[0064] Other types of networks can be used in other examples. In networks 100 such as the network of Fig. 1 measurements can be used for procedures such as cell selection, cell reselection, power control calculations, mobility procedures, beam management, or any other suitable procedures. The measurements can be performed by the UEs 110. Measurement gaps are used when the UE 110 is in RRC connected and cannot perform measurements in parallel to receiving or transmitting data corresponding to the connection. Measurement gaps are used to enable a UE 110 to carry out inter-frequency measurements, intra-frequency measurements on different BWP, as well as inter-radio access technology (RAT) measurements. In a period defined by a measurement gap neither the gNB 120 nor the UE 110 will send or receive data. In a period defined by a measurement gap the UE 110 is not scheduled by the network node 120 for any data reception or transmission from / to the network node 120. The measurement gap is used by the UE 110 to measure synchronization signal blocks (SSBs) that appear at regular intervals, such as 40 msec. A UE 110 might measure several SSBs to obtain a reliable measurement.

[0065] The measurement gaps require that both UE 110 and gNB 120 have a configuration of the gap definition. This can be achieved by configuring measurement gap parameters such as gap starting position, gap length, gap repletion period, number of gaps or any other suitable parameters. The measurement gap parameters can be provided using radio resource control (RRC) information elements such as the RRC MeasGapConfig information element.

[0066] The gNB 120 informs the UE 110 of the timing of neighbor cell SSBs via SSB measurement timing configurations (SMTC) and configures measurement gap length and SMTC window based on SSB burst periodicity. The gNB 120 configures the UE 110 with one or more measurement gap patterns with measurement gap offset so that the measurement gaps are aligned with the location of SSBs.

[0067] Fig. 2 shows an example measurement gap configuration. The gap configuration can comprise information on measurement gap length, periodicity of measurement gaps, location, or any other suitable information. Fig. 2 shows the relationship between the SSB, SMTC and the measurement gaps Multiple SSB bursts 200 are shown in Fig. 2. The SSB bursts 400 comprise any suitable number of SSBs. The SSB bursts 200 can comprise 4, 8 or 64 SSBs. In this example the SSB bursts 200 have a duration of 5ms. Other durations could be used in other examples.

[0068] The SSB bursts 200 have a defined SSB periodicity. The SSB periodicity is indicated by arrow 204 in Fig. 2. The SSB periodicity in this example is 20ms. Other periodicities could be used in other examples.

[0069] The SSB bursts 200 are provided within the SMTC window 206. The SMTC window 206 has a window length of between 1 and 5ms. The SMTC window 206 periodicity is indicated by arrow 208 and can be between 5 and 160ms. Other values could be used in other examples.

[0070] The measurement gaps 202 are aligned with the SSB bursts 200. The measurement gaps 202 have a measurement gap length (MGL) and a measurement gap repetition period (MGRP). In this example the MGL is 6ms and the MGRP is 40ms. Other values could be used in other examples. The MGL is longer than the duration of an SSB burst 200.

[0071] In some examples a UE 110 can have capability to support concurrent measurement gap patterns. In such examples a gNB 120 can provide multiple measurement gaps. The multiple measurement gaps can be configured by RRC message(s).

[0072] Fig. 3 shows an example measurement gap pattern. At block 300 a UE 110 is connected to a serving gNB 120_1. Data is scheduled to be transmitted between the UE 110 and the serving gNB 120_1 during the scheduling periods 302. The measurement gaps 202 are provided at regular intervals between the scheduling periods 302. During the measurement gaps 202 the UE 110 can perform measurements using SSBs from the serving gNB 120_1 and from other nodes 120_X. The other nodes 120_X could be non-serving gNBs or any other suitable network nodes. The serving gNB 120_1 is not allowed to schedule the UE 110 during the measurement gap 202. However, the UE 110 is not required to use the measurement gap 202. That is, there can be some measurement gaps 202 in which the UE 110 does not perform any measurements. In such a scenario the serving gNB 120_1 would not be aware that the measurement gap 202 is not being used. Therefore the serving gNB 120_1 would not schedule data during the measurement gap 202 even when the measurement gap 202 is unused.

[0073] The configuration of the measurement gaps 202 is determined by the measurement requirements and is not necessarily aligned with the traffic requirements or network load. Changes to a long term measurement gap pattern can be made, but this is inefficient because it requires additional RRC signaling. Therefore the measurement gaps 202 can be problematic for scheduling because they restrict when data can be scheduled.

[0074] Also, as shown in Fig. 3 and block 304, there can be instances where there are low traffic levels during a scheduling period 302. The UE 110 cannot perform any measurements during this period because there is no measurement gap 202.

[0075] Therefore, although the measurement gaps 202 are needed they are problematic because they are not flexible and cannot be adapted to take into account traffic loads. This could cause data to be delayed or even lost. For example, for high priority bearers the measurement gaps 202 may cause a packet delay budget to be exceeded due to retransmissions, which makes the packet unusable.

[0076] Examples of the disclosure address these problems by providing increased flexibility in the configuration of measurement gaps 202. Figs. 4A and 4B show example methods that can be used to provide a flexible configuration of measurement gaps 202. Fig. 4A shows an example method that can be performed by a network node. The network node can be a gNB 120. The network node can be a serving gNB 120 for a UE 110 that can perform the corresponding method of Fig. 4B.

[0077] The method comprises, at block 400, configuring a UE 110 with a measurement window. The measurement window defines multiple measurement gap occasions. The measurement window can define M measurement gap occasions, where M is an integer. The measurement gap occasions are aligned with SMTC positions.

[0078] The measurement gap occasions provide occasions which can potentially be used as a measurement gap 202. The measurement window can define the parameters of the measurement gap occasion, for example, it can define parameters such as length of a measurement gap occasions, periodicity of measurement gap occasions, number of measurement gap occasions within the window, and / or any other suitable parameter.

[0079] The configuration of the measurement window provides the gNB 120 with flexibility to use one or more of the measurement gap occasions for scheduling. The configuration of the measurement window can define how many of the measurement gap occasions within the window can be used for scheduling by the gNB 120.

[0080] The gNB 120 ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements. For example, if N measurement gaps are needed then the gNB 120 will ensure that at least N measurement gap occasions within the measurement window will be available for measurements. N can be any integer number which is less than or equal to M. The gNB 120 will ensure that no data is scheduled on at least N measurement gap occasions within the measurement window.

[0081] The number of measurement gap occasions that are available for measurements can be configured for a UE 110 or can be defined in a network specification.

[0082] The measurement window can be applicable to multiple frequency ranges or to a single frequency range. The gNB 120 can use a medium access control - control element (MAC-CE) to activate or deactivate the configured measurement window. The activation or deactivation of the measurement window can be determined based on scheduling requirements of the gNB 120 and / or any other suitable factors..

[0083] The gNB 120 can configure different UEs 110 with different measurement windows. A measurement window can be specific to particular UE 110.

[0084] At block 402 the gNB 120 determines if data has been scheduled on a threshold number of measurement gap occasions within the measurement window. The threshold number of measurement gap occasions is set to ensure that the configured number of measurements are secured within the measurement window. The threshold is set so as to ensure that N measurement gap occasions within the measurement window will be available for measurements. For example, if the measurement window comprises M measurement gap occasions and at least N measurement gap occasions are to be provided then the gNB 120 can schedule data on M-N measurement gap occasions. The gNB 120 can therefore determine if data has already been scheduled on M-N measurement gap occasions.

[0085] At block 404 the gNB 120 determines whether to schedule data during a measurement gap occasion. The decision whether to schedule data during a measurement gap occasion is based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window. That is, the determination made at block 402 is used to decide whether to schedule data during a measurement gap occasion. Other factors can also be taken into account when determining whether to schedule data.

[0086] If it is determined that data has been scheduled on a threshold number of measurement gap occasions, the gNB 120 is arranged to determine not to schedule data on any more measurement gap occasions within the measurement window. This leaves the measurement gap occasions available for measurements. Conversely, if it is determined that data has not been scheduled on a threshold number of measurement gap occasions, then one or more remaining measurement gap occasions within the measurement window are available to be used for scheduled data. This means that the gNB 120 could decide to use a remaining measurement gap occasion for scheduling. The decision of whether to use the measurement gap occasion for scheduling could be based on traffic load and any other relevant factors.

[0087] Fig. 4B shows an example method that can be performed by a UE 110. The UE 110 can be connected to a gNB 120 that performs the corresponding method of Fig. 4A.

[0088] At block 410 the method comprises receiving a configuration from a gNB 120. The configuration comprises a measurement window. The measurement window defines multiple measurement gap occasions. The measurement gap occasions are aligned with SMTC positions. The measurement window can define the parameters of the measurement gap occasions and can define how many of the measurement gap occasions within the window can be used for scheduling by the gNB 120.

[0089] The gNB 120 ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements. The configured number of measurement gap occasions which will be available for measurements is a minimum number of measurement gap occasions that will not be scheduled for data and available for measurements. The gNB 120 may provide more than the configured number of measurement gap occasions available for measurements. For example, if the gNB 120 has low traffic and no need for scheduling then more measurement gap occasions can be used for measurements.

[0090] The measurement window can be applicable to multiple frequency ranges or to a single frequency range.

[0091] The UE 110 can receive a MAC-CE from the gNB 120 to activate or deactivate the configured measurement window. The activation or deactivation of the measurement window can be determined based on scheduling requirements of the gNB 120 and / or any other suitable factors.. The measurement window can be specific to the UE 110.

[0092] At block 412 the UE 110 determines if data is scheduled within a given time period of a measurement gap occasion. Data can be determined to be scheduled within a given time period of the measurement gap occasion if any data is scheduled within a defined number of slots of the measurement gap occasion. The defined number of slots could be zero or more than zero. The number of slots could be defined in a network specification such as a 3GPP specification. The data can be uplink (UL) or downlink (DL) data. The downlink control information (DCI) in the physical downlink control channel (PDCCH)) can be used to indicate the scheduling for the UE 110.

[0093] At block 414 the UE 110 performs measurements based on whether data is scheduled within the given time period of the measurement gap occasion. If it is determined that no data is scheduled within the given time period of the measurement gap occasion then the UE 110 can perform measurements during the given measurement gap occasion.

[0094] If it is determined that data is scheduled within the given time period of the measurement gap occasion then the UE 110 will refrain from performing measurements during the given measurement gap occasion. The UE 110 can receive or transmit scheduled data during a measurement gap occasion that is not used for performing measurements.

[0095] In some examples the UE 110 can determine that all remaining measurement gap occasions in the measurement window are to be kept free from scheduled data to meet the configured number of measurement gap occasions. For example, the UE 110 can determine the number of measurement gap occasions that have already been used for scheduled data and the number remaining measurement gap occasions in the measurement window. If all of the remaining measurement gap occasions in the window are needed to provide the configured number of measurement gap occasions that are available for measurements then the UE 110 knows that no data can be scheduled during these measurement gap occasions. Therefore, in such scenarios, the UE 110 can refrain from determining if data is scheduled within a given time period of the measurement gap occasions.

[0096] The use of the measurement windows and the measurement gap occasions provides flexibility in the positioning of the measurement gaps. This can enable measurement gap occasions that occur during periods of low traffic to be used for measurements and measurement gap occasions that occur during periods of heavier traffic to be used for scheduling.

[0097] Fig. 5 shows an example measurement gap window 500 that could be used in some examples of the disclosure.

[0098] Fig. 5 also shows example measurement gaps 202 that would be used in implementations that do not use the configured measurement windows 500 with measurement gap occasions 502. These legacy measurement gaps 202 could not be used for scheduling. The legacy measurement gaps 202 are shown for comparison with examples of the disclosure. The UE 110 might not use all of the available measurement gaps 202 based on the measurement requirements.

[0099] Two measurement windows 500 are shown in Fig. 5. The measurement windows 500 comprises multiple measurement gap occasions 502. In this example two measurement gap occasions 502 are shown within each measurement window 500. Other numbers of measurement gap occasions 502 could be provided in other examples.

[0100] The measurement gap occasions 502 are aligned with SSB bursts 200. In the example of Fig. 5 the measurement gap occasions 502 have the same periodicity as the SSB bursts 200. A measurement gap occasion 502 is provided for each SSB burst 200. Other arrangements could be used in other examples.

[0101] The cross hatched areas 506 indicate when no data is scheduled. When a measurement gap occasion 502 coincides with a time at which no data is scheduled, the UE 110 can use the measurement gap occasions 502 for measurements. In the example of Fig. 5, measurement gap occasions used for measurements are indicated by reference number 508.

[0102] When a measurement gap occasion 502 coincides with a time at which data is scheduled, the UE 110 does not use the measurement gap occasions 502 for measurements. Instead, the UE 110 can receive or transmit the scheduled data during this time. In the example of Fig. 5, measurement gap occasions that coincide with scheduled data are indicated by reference number 510.

[0103] In the example of Fig. 5, there is also a measurement gap occasion 502 that coincides with a time at which no data is scheduled but which is not used for measurements. The UE 110 can determine that no data is scheduled during the measurement gap occasion and knows that the measurement gap occasion is available for measurements. The UE 110 can determine whether to use the available measurement gap occasion 502 based on measurement requirements and any other relevant factor. In the example of Fig. 5, measurement gap occasions that are not used for measurements and do not coincide with scheduled data are indicated by reference number 504.

[0104] Fig. 5 therefore demonstrates the flexibility that the measurement windows 500 provide. If the legacy measurement gaps 202 were used, it would not be possible to send any scheduled data during the measurement gap occasion 510. This could cause data to be delayed or even lost. This issue is resolved with the measurement window 500 and flexible measurement gap occasions because the measurement gap occasion 510 can be used for scheduled data rather than measurements. This mitigates data being lost or delayed. The measurements can still be performed at the next measurement gap occasion.

[0105] Fig. 6 shows another example measurement gap window 500 that could be used in some examples of the disclosure. Fig. 6 also shows example measurement gaps 202 that would be used in implementations that do not use examples that do not make use of the measurement windows 500. These legacy measurement gaps 202 could not be used for scheduling. The legacy measurement gaps 202 are shown for comparison with examples of the disclosure. The UE 110 might not use all of the available measurement gaps 202 based on the measurement requirements.

[0106] The measurement window 500 comprises multiple measurement gap occasions 502 and SSB bursts 200. In the example of Fig. 6 a single measurement window 500 comprising four measurement gap occasions 502 is shown. Other arrangements could be used in other examples.

[0107] As in the previous example, the grey areas 506 indicate when no data is scheduled. When a measurement gap occasion 502 coincides with a time at which no data is scheduled, the UE 110 can use the measurement gap occasions 502 for measurements. In the example of Fig. 6, three of the available measurement gap occasions 502 are used for measurements. In the example of Fig. 6, measurement gap occasions used for measurements are indicated by reference number 508.

[0108] Fig. 6 also shows a measurement gap occasion 502 that coincides with a time at which data is scheduled. The UE 110 does not use this measurement gap occasion 502 for measurements. Instead the UE 110 can receive or transmit the scheduled data during this time. In the example of Fig. 6 the measurement gap occasion that coincides with scheduled data are indicated by reference number 510.

[0109] Fig. 6 therefore demonstrates the measurement window 500 can also provide for enhanced measurements. The use of measurement gap occasions 502 can enable more measurements to be performed compared to the legacy measurement gaps 202 and / or can enable a shorter spacing between consecutive measurements.

[0110] The configuration of the measurement window 500 can configure the gNB 120 and the UE 110 with rules that are to be followed when scheduling data or determining whether to perform measurements. In some examples the rules can be:

[0111] Rule 1 The gNB 120 configures measurement gap occasions 502 that are aligned with SMTC positions. The measurement gap occasions 502 can effectively replace the legacy measurement gaps 202. Rule 2 The gNB 120 ensures that a configured number of measurement gap occasions 502 will be available within a given measurement window 500. The measurement window 500 can have any suitable length. The measurement gap window 500 can be larger than, or an integer multiple of the length of, the MGRP of the legacy measurement gaps 202.

[0112] The number of measurement gap occasions 502 that are to be available for measurements within a given measurement window 500 can be denoted by N. N can be any integer number. In the simplest case N=1. The UE 110 is not required to use more than N measurement gap occasions 502 within the measurement window 500.

[0113] Rule 3 The UE 110 can perform measurements at a measurement gap occasion 502 if no data is scheduled before the beginning of the measurement gap occasion 502 and the UE has not yet already acquired the N required measurements. This can cause the first N scheduling gaps within the measurement window 500 that coincide with a measurement gap occasion 502 to be used for measurements. Some measurement gap occasions 502 can be skipped because data is scheduled on them. This can be as shown in Figs. 5 and 6.

[0114] Rule 4 Because the first N scheduling gaps are used for measurements, the gNB 120 ensures that the first N scheduling gaps will be long enough to carry out measurements. The gNB 120 needs to sure that at least N measurement gap occasions 502 are provided within the measurement window 500 that can be used by the UE 110 for measurements, where the measurement window 500 Some may have room for M measurement gap occasions 502 where M>N.

[0115] The rules that are applied by the UE 110 can be:

[0116] Rule 1 If no data is scheduled for the UE 110 at the beginning of a measurement gap occasion 502, the UE 110 shall assume that this is a measurement gap occasion 502 to be used for measurements. Rule 2 If the UE 110 has already acquired N measurements within the measurement window 500, the UE 110 shall not assume that further scheduling gaps coinciding with measurement gap occasions 502 will have minimum measurement length and shall not assume that those further scheduling gap occasions can be used for measurements. That is, once the required number of measurements have been performed, the UE 110 can assume that it is possible for the data to be scheduled in any of the remaining measurement gap occasions 502.

[0117] Figs. 7A and 7B show example methods that can be used in examples of the disclosure. Fig. 7A shows an example method that can be performed by a UE 110. The UE 110 can be connected to a gNB 120 that performs the corresponding method of Fig. 7B.

[0118] At block 700 the method comprises configuring a measurement window 500. The measurement window 500 configuration can be received from the gNB 120.

[0119] At block 702 the measurement window 500 is activated. The measurement window 500 can be activated using MAC-CE received from the gNB 120 or any other suitable signaling.

[0120] At block 704 the UE 110 determines if data is scheduled at a measurement gap occasion 502. The data can be UL or DL data and the scheduling information is received by the UE 110 in PDCCH. When there is a gap in scheduling it is determined, at block 706, whether this gap coincides with a measurement gap occasion 502. If the gap in scheduling does not coincide with a measurement gap occasion 502 then the method returns to block 704 and the UE 110 makes the same determination for the next measurement gap occasion 502.

[0121] If the gap in scheduling does coincide with a measurement gap occasion 502 then the method proceeds to block 708 and the UE 110 performs the measurement.

[0122] At block 710 it is determined if N measurement gap occasions 502 within the measurement window 500 have been used for measurements. That is, the UE 110 can determine if the required number of measurements have been performed within the measurement window 500. If the required number of measurements have not yet been performed within the measurement window 500, the method returns to block 704 and the UE 110 waits for another measurement gap occasion that coincides with a gap in scheduling.

[0123] If the required number of measurements have been performed within the measurement window 500, the method proceeds to block 712 and the UE 110 waits for the next measurement window 500.

[0124] Fig. 7B shows an example method that can be performed by a gNB 120. The UE 110 that performs the corresponding method of Fig. 7A can be connected to the gNB 120.

[0125] At block 720 the method comprises configuring a measurement window 500. The measurement window 500 configuration can be sent from the gNB 120 to the UE 11-.

[0126] At block 722 the measurement window 500 is activated. The measurement window 500 can be activated using MAC-CE or any other suitable signaling. The MAC-CE can be sent from the gNB 120 to the UE 110.

[0127] At block 724 the gNB 120 schedules data. At block 726 it is determined if N measurement gap occasions 502 within the measurement window 500 have been available for measurements. The gNB 120 can determine if N measurement gap occasions 502 within the measurement window 500 have been available for measurements based on the scheduling history. If no data has been scheduled during a measurement gap occasion 502, then the measurement gap occasion 502 was available for measurement. If data was scheduled during a measurement gap occasion 502 then the measurement gap occasion 502 was not available for measurement.

[0128] If the required number of measurement gaps 502 have already been made available within the measurement window 500, then the method proceeds to block 728 and the scheduling of data is possible within the measurement gap occasions 502 for the remainder of the measurement window 500. That is, none of the measurement gap occasions 502 need to be kept available for measurements and so are available for scheduling.

[0129] If the required number of measurement gaps 502 have not yet been made available within the measurement window 500 then the method proceeds to block 730. At block 730 the gNB 120 determines if a gap in the scheduling coincides with a measurement gap occasion 502.

[0130] If a gap in the scheduling coincides with a measurement gap occasion 502 then the method proceeds to block 734 and the measurement gap occasion 502 is available for measurements.

[0131] If a gap in the scheduling does not coincide with a measurement gap occasion 502 then the method proceeds to block 732. At block 732 it is determined if the measurement gap occasion 502 provides the last opportunity for measurement within the measurement window 500. That is, the gNB 120 can determine if all of the remaining measurement gap occasions 502 within the measurement window 500 need to be available and free from scheduled data in order to ensure that the configured number of measurement gap occasions 502 are available for measurement within the measurement window 500.

[0132] If it is determined that the measurement gap occasion 502 provides the last opportunity for measurement within the measurement window 500 then the method proceeds to block 734 and the measurement gap occasion 502 is available for measurements. In this case the gNB 120 would not schedule data for the measurement gap occasion 502.

[0133] If it is determined that the measurement gap occasion 502 does not provide the last opportunity for measurement within the measurement window 500 then the method returns to block 724. In this scenario the UE 110 will have other opportunities within the measurement window 500 to perform the necessary measurements. In this case the measurement gap occasion can be used for scheduling. In some examples a UE 110 can have capability to support concurrent measurement gap patterns. In such cases the UE 110 can be configured with measurement windows 500 to be used simultaneously as shown in the following table.

[0134] In order to support concurrent measurement gap patterns using the measurement windows 500, the following options can be considered. Case 1 : UE 110 can be configured with 2 per-FR1 measurement gaps (i.e., gap combination configuration ID 0)

[0135] Case 2: UE 110 can be configured with 1 per-FR1 and 2 per-FR2 measurement gaps (i.e., gap combination configuration ID 1) Case 3: UE 110 can be configured with 2 per-UE measurement gaps (i.e., gap combination configuration ID 2)

[0136] Case 4: UE 110 can be configured with 1 per-FR1 / 2 per-FR2 and 1 per-UE measurement gaps (i.e., gap combination configuration ID3 & 4).

[0137] To cater for the cases, the basic measurement window 500 can be specific to the frequency range, for example, FR1 , or FR2, or FR3, and separate measurement window configurations are provided for each frequency range. The application of the measurement window 500 rules is then specific to the scheduling on the respective frequency range (scheduling on one frequency does not affect usage of measurement gap occasions on another frequency).

[0138] In other examples, the measurement window 500 configuration is applicable to all frequency ranges. In these examples, scheduling on one frequency does not affect the usage of measurement gap occasions on another frequency.

[0139] Fig. 8 shows an example controller 800. The controller 800 could be provided within an entity such as a network node 120 or a UE 110 any other suitable entity. Implementation of the controller 800 may be as controller circuitry. The controller 800 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).

[0140] As illustrated in Fig. 8, the controller 800 can be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program 806 in a general-purpose or special-purpose processor 802 that may be stored on a computer readable storage medium (disk, memory etc.) to be executed by such a processor 802.

[0141] The processor 802 is configured to read from and write to the memory 804. The processor 802 may also comprise an output interface via which data and / or commands are output by the processor 802 and an input interface via which data and / or commands are input to the processor 802. The memory 804 stores a computer program 806 comprising computer program instructions (computer program code) that controls the operation of the apparatus when loaded into the processor 802. The computer program instructions, of the computer program 806, provide the logic and routines that enables the apparatus to perform the methods illustrated in the Figs. The processor 802 by reading the memory 804 is able to load and execute the computer program 806.

[0142] In some examples where the controller 800 is provided within a device such as a network node 120 the controller 800 therefore comprises means for: configuring 400 a UE 110 with a measurement window 500, the measurement window 500 defining multiple measurement gap occasions 502 where the measurement gap occasions 502 are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node 120 ensures that a configured number of the measurement gap occasions 502 within the measurement window 500 will be available for measurements; determining 402 if data has been scheduled on a threshold number of measurement gap occasions 502 within the measurement window 500; and determining 404 whether to schedule data during a measurement gap occasion 502 based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions 502 within the measurement window 500.

[0143] In some examples where the controller 800 is provided within a device such as a UE 110 the controller 800 therefore comprises means for: receiving 410 a configuration from a network node 120, the configuration comprising a measurement window 500, the measurement window 500 defining multiple measurement gap occasions 502 where the measurement gap occasions 502 are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node 120 ensures that a configured number of the measurement gap occasions 502 within the measurement window 500 will be available for measurements; determining 412 if data is scheduled within a given time period of a measurement gap occasion 502; and performing 414 measurements based on whether data is scheduled within the given time period of the measurement gap occasion 502.

[0144] The computer program 806 may arrive at the apparatus via any suitable delivery mechanism 808. The delivery mechanism 808 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 806. The delivery mechanism may be a signal configured to reliably transfer the computer program 806. The apparatus may propagate or transmit the computer program 806 as a computer data signal.

[0145] The computer program 806 can comprise computer program instructions, which when executed by a network node 120, cause the network node 120 to perform at least the following or for performing at least the following: configuring 400 a UE 110 with a measurement window 500, the measurement window 500 defining multiple measurement gap occasions 502 where the measurement gap occasions 502 are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node 120 ensures that a configured number of the measurement gap occasions 502 within the measurement window 500 will be available for measurements; determining 402 if data has been scheduled on a threshold number of measurement gap occasions 502 within the measurement window 500; and determining 404 whether to schedule data during a measurement gap occasion 502 based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions 502 within the measurement window 500.

[0146] The computer program 806 can comprise computer program instructions, which when executed by a UE 110, cause the UE 110 to perform at least the following or for performing at least the following: receiving 410 a configuration from a network node 120, the configuration comprising a measurement window 500, the measurement window 500 defining multiple measurement gap occasions 502 where the measurement gap occasions 502 are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node 120 ensures that a configured number of the measurement gap occasions 502 within the measurement window 500 will be available for measurements; determining 412 if data is scheduled within a given time period of a measurement gap occasion 502; and performing 414 measurements based on whether data is scheduled within the given time period of the measurement gap occasion 502.

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

[0148] Although the memory 804 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.

[0149] Although the processor 802 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 802 may be a single core or multi-core processor.

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

[0151] As used in this application, the term “circuitry” can refer to one or more or all of the following:

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

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

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

[0155] (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

[0156] (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 might not be present when it is not needed for operation.

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

[0158] The blocks illustrated in the Figs, can represent steps in a method and / or sections of code in the computer program 806. 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 can be varied. Furthermore, it can be possible for some blocks to be omitted. The apparatus can be provided in an electronic device, for example, a mobile terminal, according to an example of the present disclosure. It should be understood, however, that a mobile terminal is merely illustrative of an electronic device that would benefit from examples of implementations of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure to the same. While in certain implementation examples, the apparatus can be provided in a mobile terminal, other types of electronic devices, such as, but not limited to: mobile communication devices, hand portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices and other types of electronic systems, can readily employ examples of the present disclosure. Furthermore, devices can readily employ examples of the present disclosure regardless of their intent to provide mobility.

[0159] 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.’

[0160] 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., to provide direct or indirect connection / coupling / communication. Any such intervening components can include hardware and / or software components.

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

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

[0163] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

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

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

[0166] Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not. The description of a feature, such as an apparatus or a component of an apparatus, configured to perform a function, or for performing a function, should additionally be considered to also disclose a method of performing that function. For example, description of an apparatus configured to perform one or more actions, or for performing one or more actions, should additionally be considered to disclose a method of performing those one or more actions with or without the apparatus.

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

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

[0169] The presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and 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.

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

[0171] Whilst endeavoring in the foregoing specification to draw attention to those features believed to be of importance 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

CLAIMS1 . A network node comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network node to perform at least: configuring a user equipment (UE) with a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data has been scheduled on a threshold number of measurement gap occasions within the measurement window; and determining whether to schedule data during a measurement gap occasion based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window.

2. The network node of claim 1 wherein the threshold number of measurement gap occasions is set to ensure that the configured number of measurements are secured within the measurement window.

3. The network node of any preceding claim wherein if it is determined that data has been scheduled on a threshold number of measurement gap occasions the network node is arranged to determine not to schedule data on any more measurement gap occasions within the measurement window.

4. The network node of any of preceding claim wherein if it is determined that data has not been scheduled on a threshold number of measurement gap occasions one or more remaining measurement gap occasions within the measurement window are available to be used for scheduled data.

5. The network node of any preceding claim wherein the measurement window is applicable to multiple frequency ranges.

6. The network node of any of claims 1 to 4 wherein the measurement window is applicable to a single frequency range.

7. The network node of any preceding claim wherein the processor and memory are arranged to cause the network node to perform configuring different UEs with different measurement windows.

8. The network node of any preceding claim wherein the at least one processer and at least one memory are arranged to cause the network node to perform using a medium access control - control element (MAC-CE) to activate or deactivate the configured measurement window.

9. The network node of any preceding claim wherein activation or deactivation of the measurement window is determined based, at least in part, on scheduling requirements of the network node.

10. A method comprising: configuring a user equipment (UE) with a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data has been scheduled on a threshold number of measurement gap occasions within the measurement window; and determining whether to schedule data during a measurement gap occasion based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window.

11. A computer program comprising instructions which, when executed by a network node, cause the network node to perform: configuring a user equipment (UE) with a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data has been scheduled on a threshold number of measurement gap occasions within the measurement window; and determining whether to schedule data during a measurement gap occasion based, at least in part, on the determination of whether data has been scheduled on a threshold number of measurement gap occasions within the measurement window.

12. A user equipment (UE) comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the UE to perform at least: receiving a configuration from a network node, the configuration comprising a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data is scheduled within a given time period of a measurement gap occasion; and performing measurements based on whether data is scheduled within the given time period of the measurement gap occasion.

13. The UE of claim 12 wherein performing measurements based on whether data is scheduled comprises performing measurements in a measurement gap occasion if no data is scheduled within the given time period of the measurement gap occasionand refraining from performing measurements if data is scheduled within the given time period of the measurement gap occasion.

14. The UE of any of claims 12 to 13 wherein the at least one processer and at least one memory are arranged to cause the UE to perform determining that all remaining measurement gap occasions in the measurement window are to be kept free from scheduled data to meet the configured number of measurement gap occasions and refraining from determining if data is scheduled within a given time period of the measurement gap occasions.

15. The UE of any of claims 12 to 14 wherein the at least one processor and at least one memory are arranged to cause the UE to perform at least one of: receiving scheduled data during a measurement gap occasion that is not used for performing measurements; refraining from performing measurements during a measurement gap occasion that is scheduled for data.

16. The UE of any of claims 12 to 15 wherein data is determined to be scheduled within a given time period of the measurement gap occasion if any data is scheduled within a defined number of slots of the measurement gap occasion.

17. The UE of any of claims 12 to 16 wherein the measurement window is applicable to multiple frequency ranges.

18. The UE of any of claims 12 to 16 wherein the measurement window is applicable to a single frequency range.

19. The UE of any of claims 12 to 18 wherein the measurement window is specific to the UE.

20. The UE of any of claims 12 to 19 wherein the at least one processer and at least one memory are arranged to cause the UE to perform receiving a medium accesscontrol - control element (MAC-CE) to activate or deactivate the configured measurement window.

21. A method comprising: receiving a configuration from a network node, the configuration comprising a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data is scheduled within a given time period of a measurement gap occasion; and performing measurements based on whether data is scheduled within the given time period of the measurement gap occasion.

22. A computer program comprising instructions which, when executed by a UE, cause the UE to perform: receiving a configuration from a network node, the configuration comprising a measurement window, the measurement window defining multiple measurement gap occasions where the measurement gap occasions are aligned with synchronization signal block measurement timing configuration (SMTC) positions and wherein the network node ensures that a configured number of the measurement gap occasions within the measurement window will be available for measurements; determining if data is scheduled within a given time period of a measurement gap occasion; and performing measurements based on whether data is scheduled within the given time period of the measurement gap occasion.

Images