WO2023219542A1 - Measurement configuration in wireless networks - Google Patents

Measurement configuration in wireless networks Download PDF

Info

Publication number
WO2023219542A1
WO2023219542A1 PCT/SE2023/050283 SE2023050283W WO2023219542A1 WO 2023219542 A1 WO2023219542 A1 WO 2023219542A1 SE 2023050283 W SE2023050283 W SE 2023050283W WO 2023219542 A1 WO2023219542 A1 WO 2023219542A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
user equipment
configuration
node
network
Prior art date
Application number
PCT/SE2023/050283
Other languages
French (fr)
Inventor
Angelo Centonza
Alberto GONZALEZ ESCUDERO
Oscar Ohlsson
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023219542A1 publication Critical patent/WO2023219542A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H04W36/0088—Scheduling hand-off measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers

Definitions

  • Embodiments of the disclosure relate to wireless communication, and particularly to methods, apparatus and computer-readable media for measurement configuration in wireless networks.
  • 3GPP TS 38.133 v17.5.0 defines intra-frequency and inter-frequency measurements as (emphasis added by underlining): “9.2 NR intra-frequency measurements 9.2.1 Introduction
  • a measurement is defined as a SSB based intra-frequency measurement provided the centre frequency of the SSB of the serving cell indicated for measurement and the centre frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs are also the same.
  • the UE shall be able to identify new intra-frequency cells and perform SS-RSRP, SS- RSRQ, and SS-SINR measurements of identified intra-frequency cells if carrier frequency information is provided by PCell or the PSCell, even if no explicit neighbour list with physical layer cell identities is provided.
  • the UE can perform intra-frequency SSB based measurements without measurement gaps (either legacy measurement gap or NCSG) if - the UE indicates ‘no-gap’ via intraFreq-needForGap for intra-frequency measurement, or - the SSB is completely contained in the active BWP of the UE, or - the active downlink BWP is initial BWP[3].” “9.3 NR inter-frequency measurements 9.3.1 Introduction A measurement is defined as an SSB based inter-frequency measurement provided it is not defined as an intra-frequency measurement according to clause 9.2.
  • the UE shall be able to identify new inter-frequency cells and perform SS-RSRP, SS- RSRQ, and SS-SINR measurements of identified inter-frequency cells if carrier frequency information is provided by PCell or PSCell, even if no explicit neighbour list with physical layer cell identities is provided.
  • a measurement is defined as an inter-frequency SSB based measurements without measurement gaps (either legacy measurement gap or NCSG) for UE capable of interFrequencyMeas-NoGap provided - the UE supports interFrequencyMeas-Nogap-r16 [15], and - the SSB is completely contained in the active BWP of the UE.” [0003]
  • the same standard also defines that measurement gaps are needed for certain measurements, based on UE capabilities: “9.1.2 Measurement gap If the UE requires measurement gaps to identify and measure intra-frequency cells and/or inter-frequency cells and/or inter-RAT E-UTRAN cells, and the UE does not support independent measurement gap patterns for different frequency ranges as specified in Table 5.1-1 in [18, 19, 20], in order for the requirements in the following clauses to apply the network must provide a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers.
  • the UE requires measurement gaps to identify and measure intra-frequency cells and/or inter-frequency cells and/or inter-RAT E-UTRAN cells, and the UE supports independent measurement gap patterns for different frequency ranges as specified in Table 5.1-1 in [18, 19, 20], in order for the requirements in the following clauses to apply the network must provide either per-FR measurement gap patterns for frequency range where UE requires per-FR measurement gap for concurrent monitoring of all frequency layers of each frequency range independently, or a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers of all frequency ranges.”
  • the overall architecture of NR RAN can be summarized as shown in Figure 1 (from 3GPP TS 38.401 v17.0.0).
  • a gNB is composed of one gNB-CU, and one or multiple gNB-DUs, connected via the F1 interface.
  • the configuration of the measurement gaps is requested by gNB-CU, and configured by the gNB-DU, as indicated in the F1AP interface (see 3GPP TS 38.473 v17.0.0, emphasis added by underlining): “If the gNB-CU includes the SMTC information of the measured frequency(ies) in the MeasurementTimingConfiguration IE of the CU to DU RRC Information IE that is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information.
  • the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message. If the MeasConfig IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall deduce that changes to the measurements configuration need to be applied. If the measObjectToAddModList IE is included in the MeasConfig IE, then the frequencies added in such IE are to be activated.
  • the gNB-DU shall decide if measurement gaps are needed or not and, if needed, the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message. If the measObjectToRemoveList IE is included in the MeasConfig IE, the gNB-DU shall ignore it.
  • the gNB-CU shall generate the measurement gaps based on the received SMTC information. Then the gNB- DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message.
  • the gNB-DU shall deduce that changes to the measurements’ configuration need to be applied.
  • the gNB-DU shall take the received info, e.g.
  • the Measurement Configuration is defined in 3GPP TS 38.331 v17.0.0 as (emphasis added by underlining): “– MeasConfig
  • MeasConfig specifies measurements to be performed by the UE, and covers intra- frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.
  • MeasConfig information element -- ASN1START -- TAG-MEASCONFIG-START MeasConfig :: SEQUENCE ⁇ measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, -- Need N measObjectToAddModList MeasObjectToAddModList OPTIONAL, -- Need N reportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, -- Need N reportConfigToAddModList ReportConfigToAddModList OPTIONAL, -- Need N measIdToRemoveList MeasIdToRemoveList OPTIONAL, -- Need N measIdToAddModList MeasIdToAddModList OPTIONAL, -- Need N s-MeasureConfig CHOICE ⁇ ssb-RSRP RSRP-Range, csi-RSRP RSRP-Range ⁇ OPTIONAL, -- Need M quantityConfig QuantityConfig OPTIONAL, -- Need M measGapConfig
  • MeasConfig field descriptions interFrequencyConfig-NoGap-r16 If the field is set to true, UE is configured to perform SSB based inter-frequency measurement without measurement gaps when the inter-frequency SSB is completely contained in the active DL BWP of the UE, as specified in TS 38.133 [14], clause 9.3. Otherwise, the SSB based inter-frequency measurement is performed within measurement gaps.
  • the field can only be configured in the measConfig associated with MCG, and when configured, it applies to all the Threshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells.
  • Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP to cell Specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing.
  • 3GPP TS 38.300 v17.0.0 describes how Bandwidth Adaptation works: “6.10 Bandwidth Adaptation With Bandwidth Adaptation (BA), the receive and transmit bandwidth of a UE need not be as large as the bandwidth of the cell and can be adjusted: the width can be ordered to change (e.g. to shrink during period of low activity to save power); the location can move in the frequency domain (e.g. to increase scheduling flexibility); and the subcarrier spacing can be ordered to change (e.g. to allow different services).
  • BA Bandwidth Adaptation With Bandwidth Adaptation
  • BWP Bandwidth Part
  • Figure 2 describes a scenario where three different BWPs are configured: - BWP 1 with a width of 40 MHz and subcarrier spacing of 15 kHz; - BWP 2 with a width of 10 MHz and subcarrier spacing of 15 kHz; - BWP3 with a width of 20 MHz and subcarrier spacing of 60 kHz.”
  • the same standard provides an example of a carrier where multiple SSBs are transmitted: “B.2 Multiple SSBs in a carrier
  • the BWPs configured by a serving cell may overlap in the frequency domain with the BWPs configured for other UEs by other cells within a carrier.
  • SSBs may also be transmitted within the frequency span of a carrier used by the serving cell.
  • each serving cell is associated to at most a single SSB.
  • measurements can be configured independently by MN and SN, as described in the excerpt below from 3GPP TS 37.340 v17.0.0 (emphasis added by underlining): “7.2 Measurements If the measurement is configured to the UE in preparation for the Secondary Node Addition procedure described in clause 10.2, the Master node should configure the measurement to the UE. In case of the intra-secondary node mobility described in clause 10.3, the SN should configure the measurement to the UE in coordination with the MN, if required.
  • the Secondary Node Change procedure described in clause 10.5 can be triggered by both the MN (only for inter-frequency secondary node change) and the SN.
  • the RRM measurement configuration is maintained by the SN which also processes the measurement reporting, without providing the measurement results to the MN.
  • Measurements can be configured independently by the MN and by the SN (intra-RAT measurements on serving and non-serving frequencies).
  • the MN indicates the maximum number of frequency layers and measurement identities of intra-frequency and inter- frequency measurement that can be used in the SN to ensure that UE capabilities are not exceeded.
  • MR-DC to assist MN to identify the measurement type
  • the SN indicates to the MN the list of SCG serving frequencies.
  • NR-DC to assist SN to identify the measurement type, the MN indicates also to SN the list of MCG serving frequencies.
  • the SN can also request the MN for new maximum values of the number of measurement identities that it can configure, and it is up to the MN whether to accommodate the SN request, based on the capability coordination principles as described in 7.3. If the SN receives from the MN a new value for the maximum number of measurement identities, is SN responsibility to ensure that its configured measurement identities to comply with the new limit. If MN and SN both configure measurements on the same carrier frequency then the configurations need to be consistent (if the network wants to ensure these are considered as a single measurement layer). Each node (MN and SN) can configure independently a threshold for the SpCell quality.
  • (NG)EN-DC scenario when the PCell quality is above the threshold configured by the MN, the UE is still required to perform inter-RAT measurements configured by the MN on the SN RAT (while it's not required to perform intra-RAT measurements); when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN.
  • NR-DC or NE-DC scenario when the PCell quality is above the threshold configured by the MN, the UE is not required to perform measurements configured by the MN; when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN.
  • both the MN and the SN can configure CGI reporting.
  • the MN can configure CGI reporting for intra-RAT and inter-RAT cells but the SN can only configure CGI reporting of intra-RAT cells.
  • the UE can be configured with at most one CGI reporting configuration.
  • the SN sends the CGI measurement request and the embedded CGI reporting configuration to the MN.
  • the SN sends the unknown cell information to the MN. If there is no ongoing CGI reporting measurement on UE side, the MN forwards the SN CGI measurement configuration to UE.
  • the MN rejects the request by sending X2/Xn reject message.
  • the MN can also reject the request, and sends the CGI information of the requested cell to the SN.
  • the SN cannot configure the CGI measurement using the SRB3.
  • Both MN-configured and SN-configured RRM measurements are supported while the SCG is deactivated.
  • the PSCell measurement cycle when in deactivated SCG state is configured by RRC.
  • SRB3 is not configured or the SCG is deactivated, reports for measurements configured by the SN are sent on SRB1.
  • Measurement results related to the target SN can be provided by MN to target SN at MN initiated SN change procedure. Measurement results of target SN can be forwarded from source SN to target SN via MN at SN initiated SN change procedure. Measurement results related to the target SN can be provided by source MN to target MN at Inter-MN handover with/without SN change procedure. Measurement results according to measurement configuration from the MN are encoded according to SN RRC when they are provided by MN to SN in SgNB Addition Request message / SN Addition Request message.
  • Per-UE or per-FR measurement gaps can be configured, depending on UE capability to support independent FR measurement and network preference.
  • Per-UE gap applies to both FR1 (E-UTRA, UTRA-FDD and NR) and FR2 (NR) frequencies.
  • FR1 gap and FR2 gap are configured for FR1 and FR2 respectively.
  • the UE may also be configured with a per-UE gap sharing configuration (applying to per-UE gap) or with two separate gap sharing configurations (applying to FR1 and FR2 measurement gaps respectively) [8].
  • a measurement gap configuration is always provided: - In EN-DC, NGEN-DC and NE-DC, for UEs configured with E-UTRA inter-frequency measurements as described in table 9.1.2-2 in TS 38.133 [8]; - In EN-DC and NGEN-DC, for UEs configured with UTRAN and GERAN measurements as described in table 9.1.2-2 in TS 38.133 [8]; - In NR-DC, for UEs configured with E-UTRAN measurements as described in table 9.1.2-3 in TS 38.133 [8]; - In NR-DC, NE-DC, for UEs configured with UTRAN measurements as described in table 9.4.6.3-1 and 9.4.6.3-2 in TS 38.133 [8]; - In MR-DC, for UEs that support either per-UE
  • the MN decides the FR1 gap pattern and the related gap sharing configuration for FR1, while the SN decides the FR2 gap pattern and the related gap sharing configuration for FR2; in NE-DC and NR-DC, the MN decides both the FR1 and FR2 gap patterns and the related gap sharing configurations.
  • the measurement gap configuration from the MN to the UE indicates if the configuration from the MN is a per-UE gap or an FR1 gap configuration.
  • the MN also indicates the configured per-UE or FR1 measurement gap pattern and the gap purpose (per-UE or per-FR1) to the SN.
  • Measurement gap configuration assistance information can be exchanged between the MN and the SN.
  • the SN indicates to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE.
  • the SN indicates to the MN the list of SN configured frequencies in FR1 measured by the UE and the MN indicates to the SN the list of MN configured frequencies in FR2 measured by the UE.
  • the MN indicates the configured per-UE or FR1 measurement gap pattern to the SN. The SN can provide a gap request to the MN, without indicating any list of frequencies.
  • the MN indicates the configured per-UE, FR1 or FR2 measurement gap pattern and the gap purpose to the SN.
  • the SN can indicate to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE.
  • SMTC can be used for PSCell addition/PSCell change to assist the UE in finding the SSB in the target PSCell.
  • the SMTC of the target PSCell is provided by both MN and SN it is up to UE implementation which one to use.
  • CLI measurements can be configured for NR cells in all MR-DC options.
  • EN-DC and NGEN-DC only the SN can configure CLI measurements.
  • the MN informs the SN node as part of the SN initiated SN Modification with MN involvement. See Figure 6 (taken from 3GPP TS 37.340 v17.0.0).
  • the SN can request the MN if the gaps are wanted or not by providing a list of frequencies in measuredFrequenciesSN. Additionally, there is a field called needForGaps. This field is related to a UE capability that is not in the scope of the present disclosure called NeedForGaps where the UE reports if target bands need measurement gaps or not. This capability does not apply to inter-frequency measurements in the active BWP.
  • CG-Config This message is used to transfer the SCG radio configuration as generated by the SgNB or SeNB. It can also be used by a CU to request a DU to perform certain actions, e.g. to request the DU to perform a new lower layer configuration.
  • ⁇ NR-FreqInfo :: SEQUENCE ⁇ measuredFrequency ARFCN-ValueNR OPTIONAL, ... ⁇ [0012]
  • a new field is proposed to F1AP, under the DU to CU RRC Information IE for the gNB-DU to indicate if the inter-frequency SSB measurement will be performed without gaps as the SSB is included in the active BWP.
  • the change request includes the message, where one additional IE, InterFrequencyConfig- NoGap, has been appended to 3GPP TS 38.331 v17.0.0: “9.3.1.26 DU to CU RRC Information”
  • This IE contains the RRC Information that are sent from the gNB-DU to the gNB-CU.
  • a first problem is that bandwidth part (BWP) handling is dynamic during scheduling, based on Downlink Control Info (DCI), while the gap configuration is performed via RRC requiring reconfigurations.
  • DCI Downlink Control Info
  • the conditionality of measurements based on active BWP means that the gNB-CU has no guarantee that the measurements will succeed, nor how long the measurement will take.
  • the gNB-CU configures UE1 with measurements on SSB3, even if the gNB-DU indicates that no gaps are needed and signals InterFrequencyConfig-NoGap set to “true”, it can decide to activate Dedicated BWP2, resulting in no measurement reports.
  • interFrequencyConfig- NoGap-r16 applies to both cell groups (Master Cell Group (MCG) and Secondary Cell Group (SCG)).
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the MN has configured the UE with interFrequencyConfig- NoGap-r16 set to “true” and if the UE is configured with NR-DC, it might occur that the SN gNB-DU will switch freely between BWPs as it is not aware of the MgNB-CU measurement configuration, nor the MgNB-DU decision to set InterFrequencyConfig-NoGap to true.
  • the problem in this case is that the UE will not report measurements from the SCG because the SSB to be measured is not contained in the SN active BWP.
  • a third problem is concerned with a similar situation in NR-DC, where the secondary node cannot request the master node to configure interFrequencyConfig-NoGap-r16 even if this configuration would benefit the SCG measurements.
  • the MgNB-DU is not aware of the configured BWPs and thus it cannot know if InterFrequencyConfig-NoGap would be beneficial or not.
  • Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
  • the disclosure comprises the following embodiments: - The possibility to indicate to the SN-gNB-CU and SN-gNB-DU if MN has configured interFrequencyConfig-NoGap-r16 or if the MN has de-configured it.
  • the SN-gNB-DU can adopt appropriate policies for BWP allocation, for example avoiding BWP changes and ensuring that the SSB to be measured and the UE active BWP at the scg are aligned.
  • the SN may indicate to the MN that interFrequencyConfig-NoGap-r16 should not be configured, which may correspond to a decision at the SN to use dynamic BWP allocation -
  • Embodiments of the disclosure may provide for one or more of: - The capability to indicate to the SN if interFrequencyConfig-NoGap-r16 has been configured by the MN. - The capability for the SN to request interFrequencyConfig-NoGap to the MN. - The capability for the gNB-CU and MN to indicate inter-frequency measurements without gaps so the gNB-DU or SN maintains an active BWP that allows for the measurements to be performed. [0020] A first aspect of the disclosure provides a method performed by a first network node.
  • a second aspect of the disclosure provides a method performed by a second network node. The method comprises: receiving, from a first network node, an indication of a configuration provided to a user equipment for performance of inter-frequency measurements without a measurement gap; and adaptively scheduling the user equipment for transmission or reception using one or more bandwidth parts based on the configuration.
  • Apparatus and computer programs for performing the methods of the aspects of the disclosure are also provided.
  • a first network node comprises processing circuitry configured to cause the first network node to: provide a user equipment with a configuration for performance of inter-frequency measurements without a measurement gap; and transmit, to a second network node, an indication of the configuration for performance of inter-frequency measurements without a measurement gap.
  • a second network node comprises processing circuitry configured to cause the second network node to: receive, from a first network node, an indication of a configuration provided to a user equipment for performance of inter-frequency measurements without a measurement gap; and adaptively schedule the user equipment for transmission or reception using one or more bandwidth parts based on the configuration.
  • FIG. 1 shows the NG-RAN overall architecture (taken from 3GPP TS 38.401 v17.0.0);
  • Figure 2 shows an example of bandwidth adaptation (taken from 3GPP TS 38.300 v17.0.0);
  • Figure 3 shows an example of multiple SSBs in a carrier (taken from 3GPP TS 38.300 v17.0.0);
  • Figure 4 shows the SN addition procedure taken from 3GPP TS 37.340 v17.0.0;
  • Figure 5 shows the
  • Embodiments of the disclosure relate to the configuration of measurement gaps in which a user equipment (UE) performs inter-frequency measurements, e.g., measurements on reference signals (e.g., SSB) transmitted by non-serving cells or network nodes.
  • Measurement gaps may comprise a suspension in communication between the user equipment and a serving network node, such that the UE has time to re-tune its receiver circuitry (if necessary).
  • intra-frequency measurements may be defined as measurements where the centre frequency of the SSB of a serving cell indicated for measurement and the centre frequency of the SSB of the neighbour cell (on which the measurements are to be performed) are the same, and the subcarrier spacing of the two SSBs are also the same.
  • Inter-frequency measurements are any type of measurement which does not fit the definition of intra-frequency measurements. Thus it may happen that an inter-frequency measurement is defined on an SSB of a neighbour cell whose centre frequency is the same as the serving cell, but where the subcarrier spacings of the SSBs are different.
  • FIG. 7 depicts a method in accordance with particular embodiments. The method may be performed by a first network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively).
  • the first network node may be a radio access network node, such as a master node (MN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration.
  • MN master node
  • UE user equipment
  • the method comprises interactions with a second network node which, in this example, may be a secondary node of the dual- or multi-connectivity configuration for the UE.
  • a second network node which, in this example, may be a secondary node of the dual- or multi-connectivity configuration for the UE.
  • Either or both of the master node and the second node may have a distributed architecture, comprising a centralized unit (CU) and one or more distributed units (DUs).
  • the first network node may itself be a radio access network node such as a centralized unit (CU) of a base station having a distributed architecture.
  • the second network node may be a distributed unit (DU) of the base station.
  • the base station may belong to a plurality of base stations providing service to a UE as part of a dual- or multi-connectivity configuration, and may be a master node or a secondary node.
  • the first network node provides a user equipment with a configuration for the performance of inter-frequency measurements without a measurement gap.
  • this step may correspond to the RRC Reconfiguration message transmitted from the MN-gNB to the UE in Figure 13 below.
  • the configuration may comprise a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. That is, the configuration may configure the UE to perform measurements on one or more frequencies or frequency ranges (e.g., corresponding to SSBs transmitted by other, neighbouring cells).
  • the configuration may further comprise an indication as to whether the UE is configured to perform measurements on those frequencies or frequency ranges with or without measurement gaps.
  • the first network node transmits, to a second network node, an indication of the configuration for the performance of inter-frequency measurements without a measurement gap.
  • this step may correspond to the XnAP S-NODE MODIFICATION REQUEST message transmitted from the MN-gNB-CU to the SN-gNB-CU in Figure 13.
  • the indication may correspond to the configuration provided to the UE in step 702, or may convey only part of the information contained in the configuration provided to the UE in step 702.
  • the indication of the configuration transmitted to the second network node in step 704 may indicate only that a configuration of inter-frequency measurements without measurement gaps has changed, has been added, or has been removed.
  • the indication of the configuration may be transmitted over a direct interface between the first and second network nodes, such as the Xn interface (e.g., where the network nodes are MN/SN in a dual- or multi-connectivity configuration) or the F1 interface (e.g., where the network nodes are CU/DU in a base station having a distributed architecture).
  • the first network node is a master node in a multi connectivity configuration towards the UE, e.g. the first network node is a MN in a NR-DC configuration
  • the first network node informs the second network node (e.g., the SN), of where the UE is configured to perform inter-frequency measurements without a measurement gap in the master cell group (MCG), e.g. interFrequencyConfig-NoGap.
  • MCG master cell group
  • the indication of the configuration may be transmitted, in step 704, inside the CG-ConfigInfo container included in the XnAP S-NODE ADDITION REQUEST or S-NODE MODIFICATION REQUEST.
  • MeasConfigMN MeasConfigMN OPTIONAL
  • MeasConfigMN :: SEQUENCE ⁇ measuredFrequenciesMN SEQUENCE (SIZE (1..maxMeasFreqsMN)) OF NR-FreqInfo OPTIONAL, measGapConfig SetupRelease ⁇ GapConfig ⁇ OPTIONAL
  • MN may signal such information to the second network node (e.g. SN) over a direct interface between the two nodes, e.g. such as the Xn interface.
  • a direct interface between the two nodes e.g. such as the Xn interface.
  • An example of how this information may be signaled from MN to SN is via the addition of the InterFrequencyConfig-NoGap IE defined as an Enumerated with value “True” or “False” in the Xn: S-NODE ADDITION REQUEST or in the Xn: S-NODE MODIFICATION REQUEST.
  • S-NODE ADDITION REQUEST (where underlined passages show changes to the existing technical specifications): 9.1.2.1 S-NODE ADDITION REQUEST This message is sent by the M-NG-RAN node to the S-NG-RAN node to request the preparation of resources for dual connectivity operation for a specific UE.
  • the second network node e.g. SgNB
  • the second network node understands that it is possible to configure inter-frequency measurements without gaps when the target SSB is included in in the active bandwidth part (BWP).
  • the second network node is enabled to adopt appropriate policies for the effective use of no-gap measurements at the second network node, e.g. the second network node may adopt policies that ensure alignment between the target SSB to be measured and the active BWP at the SCG.
  • step 704 may comprise transmitting the indication of the configuration to the CU of the second network node, for onward transmission to the DU of the second network node, e.g., where the CG-ConfigInfo is forwarded to the DU (e.g. SgNB-DU).
  • the DU understands that it needs to configure a BWP that allows the SgNB configured measurements to be performed without measurement gap, e.g. the Dedicated BWP with the broadest bandwidth.
  • the indication of the configuration may be signalled as part of the DU to CU RRC Information IE, or the CU to DU RRC Information IE (e.g., over the F1 interface).
  • the signaling from the first node CU to the second node CU and consequently from the second node CU to the second node DU may include information that the configuration to perform inter-frequency measurements without a measurement gap (e.g., InterFrequencyConfig-NoGap) has been removed.
  • Figure 8 depicts a method in accordance with particular embodiments. The method may be performed by a second network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively).
  • the second network node may be a radio access network node, such as a secondary node (SN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration.
  • SN secondary node
  • UE user equipment
  • the method comprises interactions with a first network node which, in this example, may be a master node (MN) of the dual- or multi-connectivity configuration for the UE.
  • MN master node
  • Either or both of the master node and the second node may have a distributed architecture, comprising a centralized unit (CU) and one or more distributed units (DUs).
  • the second network node may itself be a radio access network node such as a DU of a base station having a distributed architecture.
  • the first network node may be a CU of the base station.
  • the base station may belong to a plurality of base stations providing service to a UE as part of a dual- or multi-connectivity configuration, and may be a master node or a secondary node.
  • the steps in Figure 8 may provide a complement to the steps performed in Figure 7, performed by the first network node.
  • the method begins at step 802, in which the second network node receives, from a first network node, an indication of a configuration provided to a user equipment for the performance of inter-frequency measurements without a measurement gap. This step may correspond to step 704 described above, and/or the XnAP S-NODE MODIFICATION REQUEST message transmitted from the MN-gNB-CU to the SN-gNB-CU in Figure 13.
  • the configuration may comprise a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
  • the configuration may configure the UE to perform measurements on one or more frequencies or frequency ranges (e.g., corresponding to SSBs transmitted by other, neighbouring cells).
  • the configuration may further comprise an indication as to whether the UE is configured to perform measurements on those frequencies or frequency ranges with or without measurement gaps. Separate indications may be provided for each frequency or frequency range, such that the UE is configured to perform measurements (such as intra- or inter-frequency measurements) with a measurement gap for some frequencies or frequency ranges, and to perform measurements (such as intra- or inter-frequency measurements) without a measurement gap for other frequencies or frequency ranges.
  • the indication of the configuration may correspond to the configuration itself, or may convey only part of the information contained in the configuration.
  • the indication of the configuration received from the first network node may indicate only that a configuration of inter-frequency measurements without measurement gaps has changed, has been added, or has been removed.
  • the second network node adaptively schedules the user equipment for transmission or reception using one or more bandwidth parts based on the configuration. For example, the second network node may activate the Dedicated BWP with the broadest bandwidth. Additionally or alternatively, the second network node may schedule the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
  • the second network node may preferentially schedule the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap, e.g., by scheduling the user equipment with the active bandwidth part more often, or with higher priority than other bandwidth parts.
  • Figure 9 depicts a method in accordance with particular embodiments. The method may be performed by a second network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively).
  • the second network node may be a radio access network node, such as a secondary node (SN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration.
  • the method comprises interactions with a first network node which, in this example, may be a master node (MN) of the dual- or multi-connectivity configuration for the UE.
  • MN master node
  • the second network node may be a CU of a secondary node having a distributed or split architecture.
  • the method begins at step 902, in which the second network node communicates with the DU of the secondary node to determine whether a UE served by the secondary node is able to perform inter-frequency measurements without a measurement gap.
  • Step 902 may comprise determining whether the user equipment is able to perform inter-frequency measurements on a defined list of one or more frequencies or frequency ranges without a measurement gap.
  • the second network node may perform a query by sending its list of inter-frequency measurements in the cell bandwidth to the DU in e.g.
  • the second network node transmits, to a first network node (e.g., a MN for the UE), a request for a user equipment served by the second network node to be configured for the performance of inter-frequency measurements without a measurement gap.
  • Step 904 may correspond, in some embodiments, to step 1108 in Figure 11, and/or the transmission of XnAP S-NODE MODIFICATION REQUIRED message from the SN-gNB-CU to the MN- gNB-CU in Figure 12.
  • the request may comprise a frequency or a range of frequencies on which the user equipment is requested to be configured for the performance of inter-frequency measurements without a measurement gap. Further, the request may comprise an indication that the user equipment is requested to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. Additionally or alternatively, the request may comprise an indication that the user equipment is requested not to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. [0068] The request may comprise respective indications for the performance of inter- frequency measurements without a measurement gap for each of a plurality of frequencies or frequency ranges, or a single indication for the performance of inter-frequency measurements without a measurement gap in respect of all frequencies or frequency ranges.
  • the request may be transmitted in step 904 responsive to receipt of confirmation from the DU of the secondary node that the user equipment will be adaptively scheduled on one or more bandwidth parts so as to enable the performance of inter-frequency measurements without a measurement gap.
  • the request may be transmitted, for example, in an S-NODE ADDITION REQUEST ACKNOWLEDGE message, an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE ADDITION REQUIRED message.
  • the second network node e.g. SgNB
  • ⁇ NR-FreqInfo :: SEQUENCE ⁇ measuredFrequency ARFCN-ValueNR OPTIONAL, ... ⁇ -- TAG-CG-CONFIG-STOP -- ASN1STOP
  • the request is indicated as a global flag at SN level.
  • the request is provided on a per-frequency basis, e.g., as part of the NR-FreqInfo IE.
  • the SgNB may request the configuration as part of a XnAP S-NODE ADDITION REQUIRED as part of ConfigRestrictModReqSCG.
  • the second node CU may thus indicate to the MgNB if all its measurements can be performed without measurement gap. This would allow the first network node to skip the measurement gap and thereby improve the UE throughput in cases when the first network node does not have any measurements configured on its own or when all the first network node’s measurements can also be performed without measurement gap.
  • the CU can decide whether to send the reqInterFreqConfig-NoGap indication to the first node by first querying the secondary node DU over the F1 interface in step 902.
  • This is advantageous since it is the secondary node DU that controls the Bandwidth Adaptation and hence has the information of whether measurement gaps are needed or not for the required measurements.
  • the secondary node CU may perform the query by sending its list of inter-frequency measurements in the cell bandwidth to the secondary node DU in e.g. the F1 CU to DU RRC Information IE and the secondary node DU indicates in e.g.
  • the secondary node CU sends the reqInterFreqConfig-NoGap indication to the first network node (e.g. MgNB), e.g., over a direct interface between the first and second network nodes, e.g. the Xn interface.
  • the first network node e.g. MgNB
  • the second node CU e.g. Xn to the first node.
  • Another alternative is to re-use the existing/proposed interFrequencyConfig-NoGap indication in the e.g. F1 DU to CU RRC Information IE by updating the semantic description of the IE.
  • the second network node requests that a UE be configured to perform inter-frequency measurements without a measurement gap.
  • embodiments of the disclosure also contemplate and include the opposite arrangement, where the second network node requests that a UE that is already configured to perform inter-frequency measurements without a measurement gap, be no longer so configured. This may come as a consequence of the DU signalling to the second network node (e.g., in step 902 above).
  • Figure 10 depicts a method in accordance with particular embodiments.
  • the method may be performed by a second network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively).
  • the second network node may be a radio access network node, such as a DU of a secondary node (SN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration.
  • the method comprises interactions with a first network node which, in this example, may be a CU of the SN.
  • the steps of the method shown in Figure 10 may correspond to the signalling and steps of the DU described above with respect to step 902.
  • the method begins at step 1002, in which the second network node receives, from a first network node, an indication of one or more frequencies or frequency ranges on which a user equipment is configured to perform measurements. This step may correspond to step 1104 in Figure 11, and/or the reception of either or both of the F1AP UE CONTEXT MODIFICATION messages in Figure 12. [0079] In step 1004, the second network node transmits, to the first network node, an indication of one or more of the frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap.
  • step 1006 the second network node schedules the user equipment with an active bandwidth part which encompasses the one or more frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap.
  • the second network node is involved in configuration of UE measurements with and without measurement gaps.
  • the second network node e.g., RAN node DU
  • upon receiving from the CU an indication of the frequency on which the UE should perform measurements e.g.
  • the MeasConfig IE defined in TS38.331 v17.0.0 may reply to the RAN node CU in step 1004 with both information concerning the configuration of the measurements gaps for the UE (e.g. by signalling the MeasGapConfig IE defined over TS38.331), and with a InterFrequencyConfig- NoGap set to “true”, indicating that some measurements may be taken without the need for gaps.
  • the DU may signal to the CU the InterFrequencyConfig- NoGap set to “false”. This implies that all measurements will be taken by means of the gaps configured as per the measurement gap configuration, e.g. MeasGapConfig IE, signalled from DU to CU. If on the other hand, some or all of the gaps configured e.g.
  • Figure 11 shows a flowchart of a method in a system according to embodiments of the disclosure.
  • the method may enable the configuration of interFrequencyConfig-NoGap with SN involvement in NR-DC.
  • Figure 12 shows a signalling flow in a system according to embodiments of the disclosure, and particularly the method of Figure 11.
  • the signalling flow may provide for SN- initiated measurements requesting interFrequencyConfig-NoGap-r16 to be configured by the MN.
  • the SN-gNB-CU configures inter-frequency measurements associated with the SCG.
  • the SN-gNB-CU provides the SN-gNB-DU with an indicator to activate interFrequencyConfig-NoGaps, e.g., see F1AP UE CONTEXT MODIFICATION (CU-to-DU RRC Container (reqInterFreqConfig-NoGap)) in Figure 12.
  • the SN- gNB-DU sends a signal to the SN-gNB-CU indicating that interFrequencyConfig-NoGaps is ok to configure, e.g., see F1AP UE CONTEXT MODIFICATION RESPONSE (DU-to-CU RRC Container (InterFreqConfig-NoGap)) in Figure 12.
  • the SN-gNB-CU informs the MN-gNB-CU that it wants to activate interFrequencyConfig-NoGaps, e.g., see XnAP S-NODE MODIFICATION REQUIRED (cg-Config(reqInterFreqConfig-NoGap)) in Figure 12.
  • the MN-gNB-CU provides the MN-gNB-DU with an indicator to activate interFrequencyConfig-NoGaps, e.g., see XnAP S-NODE MODIFICATION REQUIRED (reqInterFreqConfig-NoGap) in Figure 12.
  • the MN-gNB-DU signals (e.g., to the MN-gNB-CU) that interFrequencyConfig-NoGaps is ok to configure, e.g., see XnAP S-NODE MODIFICATION REQUIRED (cg-Config(reqInterFreqConfig-NoGap)) in Figure 12.
  • the MN-gNB-CU reconfigures the UE with SCG measurements and interFrequencyConfig-NoGaps, e.g., see RRC Reconfiguration (configuring the UE with no-gap measurements) in Figure 12.
  • Figure 13 shows a signalling flow in a system according to embodiments of the disclosure.
  • the signalling flow may provide for MN-initiated measurements requesting interFrequencyConfig-NoGap-r16 to be configured by the MN.
  • the MN informs the SN of the configured no-gap measurements, so that the SN can ensure that such measurements can be performed at the SCG.
  • FIG. 14 shows an example of a communication system 1400 in accordance with some embodiments.
  • the communication system 1400 includes a telecommunication network 1402 that includes an access network 1404, such as a radio access network (RAN), and a core network 1406, which includes one or more core network nodes 1408.
  • the access network 1404 includes one or more access network nodes, such as network nodes 1410a and 1410b (one or more of which may be generally referred to as network nodes 1410), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 1410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1412a, 1412b, 1412c, and 1412d (one or more of which may be generally referred to as UEs 1412) to the core network 1406 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1410 and other communication devices.
  • the network nodes 1410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1412 and/or with other network nodes or equipment in the telecommunication network 1402 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1402.
  • the core network 1406 connects the network nodes 1410 to one or more hosts, such as host 1416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1406 includes one more core network nodes (e.g., core network node 1408) that are structured with hardware and software components.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1416 may be under the ownership or control of a service provider other than an operator or provider of the access network 1404 and/or the telecommunication network 1402, and may be operated by the service provider or on behalf of the service provider.
  • the host 1416 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1400 of Figure 14 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 1402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1402. For example, the telecommunications network 1402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs.
  • the UEs 1412 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1404.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN- DC).
  • MR-DC multi-radio dual connectivity
  • the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412c and/or 1412d) and network nodes (e.g., network node 1410b).
  • the hub 1414 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs.
  • the hub 1414 may be a broadband router enabling access to the core network 1406 for the UEs.
  • the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • Commands or instructions may be received from the UEs, network nodes 1410, or by executable code, script, process, or other instructions in the hub 1414.
  • the hub 1414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 1414 may have a constant/persistent or intermittent connection to the network node 1410b.
  • the hub 1414 may also allow for a different communication scheme and/or schedule between the hub 1414 and UEs (e.g., UE 1412c and/or 1412d), and between the hub 1414 and the core network 1406.
  • the hub 1414 is connected to the core network 1406 and/or one or more UEs via a wired connection.
  • the hub 1414 may be configured to connect to an M2M service provider over the access network 1404 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1410 while still connected via the hub 1414 via a wired or wireless connection.
  • the hub 1414 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1410b.
  • the hub 1414 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure 15 shows a UE 1500 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle- mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle- to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a power source 1508, a memory 1510, a communication interface 1512, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 15. The level of integration between the components may vary from one UE to another UE.
  • the processing circuitry 1502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1510.
  • the processing circuitry 1502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • FPGAs field-programmable gate arrays
  • ASICs application specific integrated circuits
  • DSP digital signal processor
  • the processing circuitry 1502 may include multiple central processing units (CPUs). The processing circuitry 1502 may be operable to provide, either alone or in conjunction with other UE 1500 components, such as the memory 1510, UE 1500 functionality.
  • the input/output interface 1506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1500.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device.
  • the power source 1508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1508 may further include power circuitry for delivering power from the power source 1508 itself, and/or an external power source, to the various parts of the UE 1500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1508.
  • the memory 1510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1510 includes one or more application programs 1514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1516.
  • the memory 1510 may store, for use by the UE 1500, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 1510 may allow the UE 1500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1510, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1502 may be configured to communicate with an access network or other network using the communication interface 1512.
  • the communication interface 1512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1522.
  • the communication interface 1512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1518 and/or a receiver 1520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1518 and receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • IoT Internet of Things
  • Non-limiting examples of such an IoT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • UAV Unmanned A
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence on the intended application of the IoT device in addition to other components as described in relation to the UE 1500 shown in Figure 15.
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Figure 16 shows a network node 1600 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1600 includes processing circuitry 1602, a memory 1604, a communication interface 1606, and a power source 1608, and/or any other component, or any combination thereof.
  • the network node 1600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1600 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1604 for different RATs) and some components may be reused (e.g., a same antenna 1610 may be shared by different RATs).
  • the network node 1600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1600.
  • RFID Radio Frequency Identification
  • the processing circuitry 1602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1600 components, such as the memory 1604, network node 1600 functionality.
  • the processing circuitry 1602 may be configured to cause the network node to perform the methods as described with reference to Figures 7, 8, 9 and/or 10.
  • the processing circuitry 1602 may also or alternatively be configured to cause the network node to perform any of the steps of the method as shown in Figure 11, and/or any of the signalling and processing of the MN-gNB- DU, MN-gNB-CU, SN-gNB-CU or CN-gNB-DU in Figures 12 and 13.
  • the processing circuitry 1602 includes a system on a chip (SOC).
  • the processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 1612 and the baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1612 and baseband processing circuitry 1614 may be on the same chip or set of chips, boards, or units.
  • the memory 1604 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1602.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non
  • the memory 1604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1602 and utilized by the network node 1600.
  • the memory 1604 may be used to store any calculations made by the processing circuitry 1602 and/or any data received via the communication interface 1606.
  • the processing circuitry 1602 and memory 1604 is integrated.
  • the communication interface 1606 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1606 comprises port(s)/terminal(s) 1616 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1606 also includes radio front-end circuitry 1618 that may be coupled to, or in certain embodiments a part of, the antenna 1610.
  • Radio front-end circuitry 1618 comprises filters 1620 and amplifiers 1622.
  • the radio front-end circuitry 1618 may be connected to an antenna 1610 and processing circuitry 1602.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1610 and processing circuitry 1602.
  • the radio front-end circuitry 1618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1620 and/or amplifiers 1622. The radio signal may then be transmitted via the antenna 1610. Similarly, when receiving data, the antenna 1610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1618. The digital data may be passed to the processing circuitry 1602. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0120] In certain alternative embodiments, the network node 1600 does not include separate radio front-end circuitry 1618, instead, the processing circuitry 1602 includes radio front-end circuitry and is connected to the antenna 1610.
  • the RF transceiver circuitry 1612 is part of the communication interface 1606.
  • the communication interface 1606 includes one or more ports or terminals 1616, the radio front-end circuitry 1618, and the RF transceiver circuitry 1612, as part of a radio unit (not shown), and the communication interface 1606 communicates with the baseband processing circuitry 1614, which is part of a digital unit (not shown).
  • the antenna 1610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1610 may be coupled to the radio front- end circuitry 1618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1610 is separate from the network node 1600 and connectable to the network node 1600 through an interface or port.
  • the antenna 1610, communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1610, the communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1608 provides power to the various components of network node 1600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1600 with power for performing the functionality described herein.
  • the network node 1600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1608.
  • the power source 1608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry.
  • Embodiments of the network node 1600 may include additional components beyond those shown in Figure 16 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 1600 may include user interface equipment to allow input of information into the network node 1600 and to allow output of information from the network node 1600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1600.
  • Figure 17 is a block diagram of a host 1700, which may be an embodiment of the host 1416 of Figure 14, in accordance with various aspects described herein.
  • the host 1700 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1700 may provide one or more services to one or more UEs.
  • the host 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a network interface 1708, a power source 1710, and a memory 1712.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 15 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host 1700.
  • the memory 1712 may include one or more computer programs including one or more host application programs 1714 and data 1716, which may include user data, e.g., data generated by a UE for the host 1700 or data generated by the host 1700 for a UE.
  • Embodiments of the host 1700 may utilize only a subset or all of the components shown.
  • the host application programs 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • FIG. 18 is a block diagram illustrating a virtualization environment 1800 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Hardware 1804 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1808a and 1808b (one or more of which may be generally referred to as VMs 1808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1806 may present a virtual operating platform that appears like networking hardware to the VMs 1808.
  • the VMs 1808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1806.
  • a virtual appliance 1802 may be implemented on one or more of VMs 1808, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 1808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1808, and that part of hardware 1804 that executes that VM forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1808 on top of the hardware 1804 and corresponds to the application 1802.
  • Hardware 1804 may be implemented in a standalone network node with generic or specific components. Hardware 1804 may implement some functions via virtualization. Alternatively, hardware 1804 may be part of a larger cluster of hardware (e.g.
  • hardware 1804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1812 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 19 shows a communication diagram of a host 1902 communicating via a network node 1904 with a UE 1906 over a partially wireless connection in accordance with some embodiments.
  • UE such as a UE 1412a of Figure 14 and/or UE 1500 of Figure 15
  • network node such as network node 1410a of Figure 14 and/or network node 1600 of Figure 16
  • host such as host 1416 of Figure 14 and/or host 1700 of Figure 17
  • embodiments of host 1902 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1902 also includes software, which is stored in or accessible by the host 1902 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1906 connecting via an over-the-top (OTT) connection 1950 extending between the UE 1906 and host 1902.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1950.
  • the network node 1904 includes hardware enabling it to communicate with the host 1902 and UE 1906.
  • the connection 1960 may be direct or pass through a core network (like core network 1406 of Figure 14) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1906 includes hardware and software, which is stored in or accessible by UE 1906 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1906 with the support of the host 1902.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1906 with the support of the host 1902.
  • an executing host application may communicate with the executing client application via the OTT connection 1950 terminating at the UE 1906 and host 1902.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1950 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1950.
  • the OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide the connection between the host 1902 and the UE 1906.
  • the connection 1960 and wireless connection 1970, over which the OTT connection 1950 may be provided, have been drawn abstractly to illustrate the communication between the host 1902 and the UE 1906 via the network node 1904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1902 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1906.
  • the user data is associated with a UE 1906 that shares data with the host 1902 without explicit human interaction.
  • the host 1902 initiates a transmission carrying the user data towards the UE 1906.
  • the host 1902 may initiate the transmission responsive to a request transmitted by the UE 1906.
  • the request may be caused by human interaction with the UE 1906 or by operation of the client application executing on the UE 1906.
  • the transmission may pass via the network node 1904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1912, the network node 1904 transmits to the UE 1906 the user data that was carried in the transmission that the host 1902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1914, the UE 1906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1906 associated with the host application executed by the host 1902. [0140] In some examples, the UE 1906 executes a client application which provides user data to the host 1902. The user data may be provided in reaction or response to the data received from the host 1902.
  • the UE 1906 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1906.
  • the UE 1906 initiates, in step 1918, transmission of the user data towards the host 1902 via the network node 1904.
  • the network node 1904 receives user data from the UE 1906 and initiates transmission of the received user data towards the host 1902.
  • the host 1902 receives the user data carried in the transmission initiated by the UE 1906.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1906 using the OTT connection 1950, in which the wireless connection 1970 forms the last segment. More precisely, the teachings of these embodiments may improve the measurement performance of the UE 1906, and therefore the radio connections of the UE 1906 are likely to be more reliable and stronger; thereby providing benefits such as reduced user waiting time, reduced drop-out rate of the OTT connection 1950, improved content resolution and better responsiveness.
  • factory status information may be collected and analyzed by the host 1902.
  • the host 1902 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1902 may store surveillance video uploaded by a UE.
  • the host 1902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1902 and/or UE 1906.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1904. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1902.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1950 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • Group B Embodiments 1 A method performed by a first network node, the method comprising: providing a user equipment with a configuration for the performance of inter- frequency measurements without a measurement gap; and transmitting, to a second network node, an indication of the configuration for the performance of inter-frequency measurements without a measurement gap.
  • the configuration comprises a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
  • the configuration comprises an indication that the user equipment is to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. 4.
  • the configuration comprises an indication that the user equipment is not to perform inter- frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies.
  • the first and second network nodes are radio access network nodes.
  • the indication of the configuration is transmitted to the second network node over a direct interface between the first network node and the second network node.
  • the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration.
  • the second network node comprises a centralized unit and a distributed unit, wherein the indication of the configuration is transmitted to the centralized unit to be forwarded to the distributed unit.
  • the method according to embodiment 13 or 14 wherein the indication of the configuration is provided in an information element, e.g., DU to CU RRC Information, or CU to DU RRC Information.
  • a method performed by a second network node comprising: receiving, from a first network node, an indication of a configuration provided to a user equipment for the performance of inter-frequency measurements without a measurement gap; and adaptively scheduling the user equipment for transmission or reception using one or more bandwidth parts based on the configuration.
  • the configuration comprises a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
  • the configuration comprises an indication that the user equipment is to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies.
  • the configuration comprises an indication that the user equipment is not to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies.
  • the second network node comprises a centralized unit and a distributed unit, wherein the indication of the configuration is received by the centralized unit to be forwarded to the distributed unit.
  • the method according to embodiment 28, wherein the indication of the configuration is provided in a CG-ConfigInfo container.
  • the method according to embodiment 28 or 29, wherein the indication of the configuration is provided in an information element, e.g., DU to CU RRC Information, or CU to DU RRC Information.
  • adaptively scheduling the user equipment comprises scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
  • adaptively scheduling the user equipment comprises preferentially scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
  • preferentially scheduling the user equipment with an active bandwidth part comprises scheduling the user equipment with the active bandwidth part more often, or with higher priority than other bandwidth parts.
  • a method performed by a second network node comprising: transmitting, to a first network node, a request for a user equipment served by the second network node to be configured for the performance of inter- frequency measurements without a measurement gap.
  • the request comprises a frequency or a range of frequencies on which the user equipment is requested to be configured for the performance of inter-frequency measurements without a measurement gap.
  • the request comprises an indication that the user equipment is requested to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies.
  • the request comprises an indication that the user equipment is requested not to perform inter- frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies.
  • the request comprises respective indications for the performance of inter-frequency measurements without a measurement gap for each of a plurality of frequencies or frequency ranges.
  • the request comprises a single indication for the performance of inter-frequency measurements without a measurement gap in respect of all frequencies or frequency ranges.
  • the first and second network nodes are radio access network nodes.
  • the method according to embodiment 44 further comprising communicating, with a distributed unit of the secondary node, to determine whether the user equipment is able to perform inter-frequency measurements on a defined list of one or more frequencies or frequency ranges without a measurement gap, and wherein the request is transmitted responsive to a determination that the user equipment is able to perform inter-frequency measurements on the defined list of one or more frequencies or frequency ranges without a measurement gap.
  • the request is further transmitted responsive to receipt of confirmation from the distributed unit of the secondary node that the user equipment will be adaptively scheduled on one or more bandwidth parts so as to enable the performance of inter-frequency measurements without a measurement gap.
  • a method performed by a second network node comprising: receiving, from a first network node, an indication of one or more frequencies or frequency ranges on which a user equipment is configured to perform measurements; and transmitting, to the first network node, an indication of one or more of the frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap.
  • the method according to embodiment 49 further comprising scheduling the user equipment with an active bandwidth part which encompasses the one or more frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap.
  • the first network node is a centralized unit of a base station
  • the second network node is a distributed unit of the base station.
  • the base station is a secondary node providing service to the user equipment in a dual- or multi-connectivity configuration.
  • the measurement gap comprises a suspension in communication between the user equipment and the first network node or the second network node, to enable the user equipment to perform inter-frequency measurements on transmissions by other network nodes.
  • the method according to any one of the preceding embodiments wherein the user equipment is able to perform inter-frequency measurements without a measurement gap where the measurements are performed on a frequency or a range of frequencies falling within an active bandwidth part configured for the user equipment. 55. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • the processing circuitry of the host is configured to execute a host application that provides the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • the method of the previous embodiment further comprising, at the network node, transmitting the user data provided by the host for the UE. 61.
  • a communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • the communication system of the previous embodiment further comprising: the network node; and/or the user equipment.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • the host of the previous embodiment wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • the initiating receipt of the user data comprises requesting the user data.
  • UE user equipment
  • 5GC 5G Core AMF Access and Mobility Management Function BA Bandwidth Adaptation BWP Bandwith Part CGI Cell Global Identity CLI Cross Link Interference CR Change Request CU Centralized Unit DC Dual Connectivity DCI Downlink Control Information DU Distributed Unit eNB E-UTRAN Node B E-UTRAN Evolved Universal Terrestrial Radio Access Network F1 Interface between gNB-CU and gNB-DU.
  • F1AP F1 Application Protocol
  • FR Frequency Range
  • FR1 Frequency Range 1
  • FR2 Frequency Range 2
  • Next Generation Node B gNB-CU gNB Centralized Unit gNB-DU gNB Distributed Unit IE Informatioomn Element LTE Long Term Evolution MCG Master Cell Group MgNB Master gNB MN Master Node MN-gNB Master Node gNB MR-DC Multi-RAT Dual Connectivity NCGI NR Cell Global Identity NCSG Network Configured Short Gaps NE-DC NR E-Utran Dual Connectivity NG-RAN Next Generation Radio Access Network (NG)EN-DC EN-DC where the Master eNB is connected to 5GC NR New Radio NR-DC NR-NR Dual Connectivity PCell Primary Cell PSCell Primary SCG Cell (in NR) or Primary Secondary Cell (in LTE) RAN Radio Access Network RAT Radio Access Technology RMSI Remaining Minimum System Information
  • RRC Radio Resource Control
  • RRM Radio Resource Management SCG Secondary Cell Group S

Abstract

One disclosed method, performed by a first network node, comprises: providing (702) a user equipment with a configuration for performance of inter-frequency measurements without a measurement gap; and transmitting (704), to a second network node, an indication of the configuration for performance of inter-frequency measurements without a measurement gap.

Description

METHODS, APPARTAUS AND COMPUTER-READABLE MEDIA RELATED TO MEASUREMENT CONFIGURATION IN WIRELESS NETWORKS TECHNICAL FIELD [0001] Embodiments of the disclosure relate to wireless communication, and particularly to methods, apparatus and computer-readable media for measurement configuration in wireless networks. BACKGROUND [0002] 3GPP TS 38.133 v17.5.0 defines intra-frequency and inter-frequency measurements as (emphasis added by underlining): “9.2 NR intra-frequency measurements 9.2.1 Introduction A measurement is defined as a SSB based intra-frequency measurement provided the centre frequency of the SSB of the serving cell indicated for measurement and the centre frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs are also the same. The UE shall be able to identify new intra-frequency cells and perform SS-RSRP, SS- RSRQ, and SS-SINR measurements of identified intra-frequency cells if carrier frequency information is provided by PCell or the PSCell, even if no explicit neighbour list with physical layer cell identities is provided. The UE can perform intra-frequency SSB based measurements without measurement gaps (either legacy measurement gap or NCSG) if - the UE indicates ‘no-gap’ via intraFreq-needForGap for intra-frequency measurement, or - the SSB is completely contained in the active BWP of the UE, or - the active downlink BWP is initial BWP[3].” “9.3 NR inter-frequency measurements 9.3.1 Introduction A measurement is defined as an SSB based inter-frequency measurement provided it is not defined as an intra-frequency measurement according to clause 9.2. The UE shall be able to identify new inter-frequency cells and perform SS-RSRP, SS- RSRQ, and SS-SINR measurements of identified inter-frequency cells if carrier frequency information is provided by PCell or PSCell, even if no explicit neighbour list with physical layer cell identities is provided. A measurement is defined as an inter-frequency SSB based measurements without measurement gaps (either legacy measurement gap or NCSG) for UE capable of interFrequencyMeas-NoGap provided - the UE supports interFrequencyMeas-Nogap-r16 [15], and - the SSB is completely contained in the active BWP of the UE.” [0003] The same standard also defines that measurement gaps are needed for certain measurements, based on UE capabilities: “9.1.2 Measurement gap If the UE requires measurement gaps to identify and measure intra-frequency cells and/or inter-frequency cells and/or inter-RAT E-UTRAN cells, and the UE does not support independent measurement gap patterns for different frequency ranges as specified in Table 5.1-1 in [18, 19, 20], in order for the requirements in the following clauses to apply the network must provide a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers. If the UE requires measurement gaps to identify and measure intra-frequency cells and/or inter-frequency cells and/or inter-RAT E-UTRAN cells, and the UE supports independent measurement gap patterns for different frequency ranges as specified in Table 5.1-1 in [18, 19, 20], in order for the requirements in the following clauses to apply the network must provide either per-FR measurement gap patterns for frequency range where UE requires per-FR measurement gap for concurrent monitoring of all frequency layers of each frequency range independently, or a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers of all frequency ranges.” [0004] The overall architecture of NR RAN can be summarized as shown in Figure 1 (from 3GPP TS 38.401 v17.0.0). [0005] A gNB is composed of one gNB-CU, and one or multiple gNB-DUs, connected via the F1 interface. In this split architecture, the configuration of the measurement gaps is requested by gNB-CU, and configured by the gNB-DU, as indicated in the F1AP interface (see 3GPP TS 38.473 v17.0.0, emphasis added by underlining): “If the gNB-CU includes the SMTC information of the measured frequency(ies) in the MeasurementTimingConfiguration IE of the CU to DU RRC Information IE that is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information. Then the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message. If the MeasConfig IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall deduce that changes to the measurements configuration need to be applied. If the measObjectToAddModList IE is included in the MeasConfig IE, then the frequencies added in such IE are to be activated. Then the gNB-DU shall decide if measurement gaps are needed or not and, if needed, the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message. If the measObjectToRemoveList IE is included in the MeasConfig IE, the gNB-DU shall ignore it. […] If the gNB-CU includes the SMTC information of the measured frequency(ies) in the MeasurementTimingConfiguration IE of the CU to DU RRC Information IE that is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information. Then the gNB- DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message. If the MeasConfig IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall deduce that changes to the measurements’ configuration need to be applied. The gNB-DU shall take the received info, e.g. the measObjectToAddModList IE, and/or the measObjectToRemoveList IE into account, when generating measurement gap and when deciding if a measurement gap is needed or not.” [0006] The Measurement Configuration is defined in 3GPP TS 38.331 v17.0.0 as (emphasis added by underlining): “– MeasConfig The IE MeasConfig specifies measurements to be performed by the UE, and covers intra- frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps. MeasConfig information element -- ASN1START -- TAG-MEASCONFIG-START MeasConfig ::= SEQUENCE { measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, -- Need N measObjectToAddModList MeasObjectToAddModList OPTIONAL, -- Need N reportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, -- Need N reportConfigToAddModList ReportConfigToAddModList OPTIONAL, -- Need N measIdToRemoveList MeasIdToRemoveList OPTIONAL, -- Need N measIdToAddModList MeasIdToAddModList OPTIONAL, -- Need N s-MeasureConfig CHOICE { ssb-RSRP RSRP-Range, csi-RSRP RSRP-Range } OPTIONAL, -- Need M quantityConfig QuantityConfig OPTIONAL, -- Need M measGapConfig MeasGapConfig OPTIONAL, -- Need M measGapSharingConfig MeasGapSharingConfig OPTIONAL, -- Need M ..., [[ interFrequencyConfig-NoGap-r16 ENUMERATED {true} OPTIONAL -- Need R ]], [[ posMeasGapPreConfigToAddModList-r17 PosMeasGapPreConfigToAddModList-r17 OPTIONAL, -- Need N posMeasGapPreConfigToRemoveList PosMeasGapPreConfigToRemoveList-r17 OPTIONAL -- Need N ]] } MeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId ReportConfigToRemoveList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigId PosMeasGapPreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxGapConfig-r17)) OF PosMeasGapPreConfig-r17 PosMeasGapPreConfigToRemoveList-r17 ::= SEQUENCE (SIZE (1..maxGapConfig-r17)) OF PosMeasGapPreConfig-r17 --Editor's Note: maxGapConfig is FFS-- -- TAG-MEASCONFIG-STOP -- ASN1STOP
MeasConfig field descriptions interFrequencyConfig-NoGap-r16 If the field is set to true, UE is configured to perform SSB based inter-frequency measurement without measurement gaps when the inter-frequency SSB is completely contained in the active DL BWP of the UE, as specified in TS 38.133 [14], clause 9.3. Otherwise, the SSB based inter-frequency measurement is performed within measurement gaps. In NR-DC, the field can only be configured in the measConfig associated with MCG, and when configured, it applies to all the
Figure imgf000007_0003
Threshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells. Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP to cell
Figure imgf000007_0001
Specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing.
Figure imgf000007_0002
[0007] 3GPP TS 38.300 v17.0.0 describes how Bandwidth Adaptation works: “6.10 Bandwidth Adaptation With Bandwidth Adaptation (BA), the receive and transmit bandwidth of a UE need not be as large as the bandwidth of the cell and can be adjusted: the width can be ordered to change (e.g. to shrink during period of low activity to save power); the location can move in the frequency domain (e.g. to increase scheduling flexibility); and the subcarrier spacing can be ordered to change (e.g. to allow different services). A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and BA is achieved by configuring the UE with BWP(s) and telling the UE which of the configured BWPs is currently the active one. Figure 2 describes a scenario where three different BWPs are configured: - BWP1 with a width of 40 MHz and subcarrier spacing of 15 kHz; - BWP2 with a width of 10 MHz and subcarrier spacing of 15 kHz; - BWP3 with a width of 20 MHz and subcarrier spacing of 60 kHz.” [0008] Furthermore, the same standard provides an example of a carrier where multiple SSBs are transmitted: “B.2 Multiple SSBs in a carrier For a UE in RRC_CONNECTED, the BWPs configured by a serving cell may overlap in the frequency domain with the BWPs configured for other UEs by other cells within a carrier. Multiple SSBs may also be transmitted within the frequency span of a carrier used by the serving cell. However, from the UE perspective, each serving cell is associated to at most a single SSB. Figure 3 describes a scenario with multiple SSBs in a carrier, identifying two different cells (NCGI = 5, associated to SSB1, and NCGI = 6, associated to SSB3) with overlapping BWPs, and where RRM measurements can be configured to be performed by the UE on each of the available SSBs, i.e. SSB1, SSB2, SSB3 and SSB4. [0009] In Dual Connectivity, measurements can be configured independently by MN and SN, as described in the excerpt below from 3GPP TS 37.340 v17.0.0 (emphasis added by underlining): “7.2 Measurements If the measurement is configured to the UE in preparation for the Secondary Node Addition procedure described in clause 10.2, the Master node should configure the measurement to the UE. In case of the intra-secondary node mobility described in clause 10.3, the SN should configure the measurement to the UE in coordination with the MN, if required. The Secondary Node Change procedure described in clause 10.5 can be triggered by both the MN (only for inter-frequency secondary node change) and the SN. For secondary node changes triggered by the SN, the RRM measurement configuration is maintained by the SN which also processes the measurement reporting, without providing the measurement results to the MN. Measurements can be configured independently by the MN and by the SN (intra-RAT measurements on serving and non-serving frequencies). The MN indicates the maximum number of frequency layers and measurement identities of intra-frequency and inter- frequency measurement that can be used in the SN to ensure that UE capabilities are not exceeded. In MR-DC, to assist MN to identify the measurement type, the SN indicates to the MN the list of SCG serving frequencies. In NR-DC, to assist SN to identify the measurement type, the MN indicates also to SN the list of MCG serving frequencies. The SN can also request the MN for new maximum values of the number of measurement identities that it can configure, and it is up to the MN whether to accommodate the SN request, based on the capability coordination principles as described in 7.3. If the SN receives from the MN a new value for the maximum number of measurement identities, is SN responsibility to ensure that its configured measurement identities to comply with the new limit. If MN and SN both configure measurements on the same carrier frequency then the configurations need to be consistent (if the network wants to ensure these are considered as a single measurement layer). Each node (MN and SN) can configure independently a threshold for the SpCell quality. In (NG)EN-DC scenario, when the PCell quality is above the threshold configured by the MN, the UE is still required to perform inter-RAT measurements configured by the MN on the SN RAT (while it's not required to perform intra-RAT measurements); when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN. In NR-DC or NE-DC scenario, when the PCell quality is above the threshold configured by the MN, the UE is not required to perform measurements configured by the MN; when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN. NOTE: The SN cannot renegotiate the number of frequency layers allocated by the MN in this version of the protocol. In MR-DC, both the MN and the SN can configure CGI reporting. The MN can configure CGI reporting for intra-RAT and inter-RAT cells but the SN can only configure CGI reporting of intra-RAT cells. At any point in time, the UE can be configured with at most one CGI reporting configuration. For CGI reporting coordination, the SN sends the CGI measurement request and the embedded CGI reporting configuration to the MN. Optionally, the SN sends the unknown cell information to the MN. If there is no ongoing CGI reporting measurement on UE side, the MN forwards the SN CGI measurement configuration to UE. Otherwise the MN rejects the request by sending X2/Xn reject message. In case the SN indicates the unknown cell information, and the CGI information of the requested cell is already available in the MN, the MN can also reject the request, and sends the CGI information of the requested cell to the SN. The SN cannot configure the CGI measurement using the SRB3. Both MN-configured and SN-configured RRM measurements are supported while the SCG is deactivated. The PSCell measurement cycle when in deactivated SCG state is configured by RRC. When SRB3 is not configured or the SCG is deactivated, reports for measurements configured by the SN are sent on SRB1. When SRB3 is configured and SCG transmission of radio bearers is not suspended and the SCG is not deactivated, reports for measurements configured by the SN are sent on SRB3. Measurement results related to the target SN can be provided by MN to target SN at MN initiated SN change procedure. Measurement results of target SN can be forwarded from source SN to target SN via MN at SN initiated SN change procedure. Measurement results related to the target SN can be provided by source MN to target MN at Inter-MN handover with/without SN change procedure. Measurement results according to measurement configuration from the MN are encoded according to SN RRC when they are provided by MN to SN in SgNB Addition Request message / SN Addition Request message. During SN initiated SN change procedure, measurement results according to measurement configuration from SN are encoded according to SN RRC when they are provided by MN to SN in SgNB Addition Request message / SN Addition Request message. Per-UE or per-FR measurement gaps can be configured, depending on UE capability to support independent FR measurement and network preference. Per-UE gap applies to both FR1 (E-UTRA, UTRA-FDD and NR) and FR2 (NR) frequencies. For per-FR gap, two independent gap patterns (i.e. FR1 gap and FR2 gap) are configured for FR1 and FR2 respectively. The UE may also be configured with a per-UE gap sharing configuration (applying to per-UE gap) or with two separate gap sharing configurations (applying to FR1 and FR2 measurement gaps respectively) [8]. A measurement gap configuration is always provided: - In EN-DC, NGEN-DC and NE-DC, for UEs configured with E-UTRA inter-frequency measurements as described in table 9.1.2-2 in TS 38.133 [8]; - In EN-DC and NGEN-DC, for UEs configured with UTRAN and GERAN measurements as described in table 9.1.2-2 in TS 38.133 [8]; - In NR-DC, for UEs configured with E-UTRAN measurements as described in table 9.1.2-3 in TS 38.133 [8]; - In NR-DC, NE-DC, for UEs configured with UTRAN measurements as described in table 9.4.6.3-1 and 9.4.6.3-2 in TS 38.133 [8]; - In MR-DC, for UEs that support either per-UE or per-FR gaps, when the conditions to measure SSB based inter-frequency measurement or SSB based intra-frequency measurement as described in clause 9.2.4 in TS 38.300 [3] are met; If per-UE gap is used, the MN decides the gap pattern and the related gap sharing configuration. If per-FR gap is used, in EN-DC and NGEN-DC, the MN decides the FR1 gap pattern and the related gap sharing configuration for FR1, while the SN decides the FR2 gap pattern and the related gap sharing configuration for FR2; in NE-DC and NR-DC, the MN decides both the FR1 and FR2 gap patterns and the related gap sharing configurations. In EN-DC and NGEN-DC, the measurement gap configuration from the MN to the UE indicates if the configuration from the MN is a per-UE gap or an FR1 gap configuration. The MN also indicates the configured per-UE or FR1 measurement gap pattern and the gap purpose (per-UE or per-FR1) to the SN. Measurement gap configuration assistance information can be exchanged between the MN and the SN. For the case of per-UE gap, the SN indicates to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE. For the per-FR gap case, the SN indicates to the MN the list of SN configured frequencies in FR1 measured by the UE and the MN indicates to the SN the list of MN configured frequencies in FR2 measured by the UE. In NE-DC, the MN indicates the configured per-UE or FR1 measurement gap pattern to the SN. The SN can provide a gap request to the MN, without indicating any list of frequencies. In NR-DC, the MN indicates the configured per-UE, FR1 or FR2 measurement gap pattern and the gap purpose to the SN. The SN can indicate to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE. In (NG)EN-DC and NR-DC, SMTC can be used for PSCell addition/PSCell change to assist the UE in finding the SSB in the target PSCell. In case the SMTC of the target PSCell is provided by both MN and SN it is up to UE implementation which one to use. CLI measurements can be configured for NR cells in all MR-DC options. In EN-DC and NGEN-DC, only the SN can configure CLI measurements. In NE-DC, only the MN can configure CLI measurements. In NR-DC, both the MN and the SN can configure CLI measurements, and the MN informs the SN about the maximum number of CLI measurement resources that can be configured by the SN to ensure that the total number of CLI measurement resources does not exceed the UE capabilities.” [0010] In DC, if the gaps are configured due to MN measurements the MN informs the SN as part of the SN Addition procedure or in a MN initiated SN Modification. Figures 4 and 5 show examples for MR-DC with 5GC (both taken from 3GPP TS 37.340 v17.0.0). Figure 4 shows the SN addition procedure, while Figure 5 shows the MN-initiated SN modification procedure. If the gaps are configured by MN but requested by the SN, the MN informs the SN node as part of the SN initiated SN Modification with MN involvement. See Figure 6 (taken from 3GPP TS 37.340 v17.0.0). [0011] In NR-DC, the SN can request the MN if the gaps are wanted or not by providing a list of frequencies in measuredFrequenciesSN. Additionally, there is a field called needForGaps. This field is related to a UE capability that is not in the scope of the present disclosure called NeedForGaps where the UE reports if target bands need measurement gaps or not. This capability does not apply to inter-frequency measurements in the active BWP. From 3GPP TS 38.331 v17.0.0 (emphasis added by underlining): “– CG-Config This message is used to transfer the SCG radio configuration as generated by the SgNB or SeNB. It can also be used by a CU to request a DU to perform certain actions, e.g. to request the DU to perform a new lower layer configuration. Direction: Secondary gNB or eNB to master gNB or eNB, alternatively CU to DU. CG-Config message CG-Config-IEs ::= SEQUENCE { scg-CellGroupConfig OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, configRestrictModReq ConfigRestrictModReqSCG OPTIONAL, drx-InfoSCG DRX-Info OPTIONAL, candidateCellInfoListSN OCTET STRING (CONTAINING MeasResultList2NR) OPTIONAL, measConfigSN MeasConfigSN OPTIONAL, selectedBandCombination BandCombinationInfoSN OPTIONAL, fr-InfoListSCG FR-InfoList OPTIONAL, candidateServingFreqListNR CandidateServingFreqListNR OPTIONAL, nonCriticalExtension CG-Config-v1540-IEs OPTIONAL } CG-Config-v1560-IEs ::= SEQUENCE { pSCellFrequencyEUTRA ARFCN-ValueEUTRA OPTIONAL, scg-CellGroupConfigEUTRA OCTET STRING OPTIONAL, candidateCellInfoListSN-EUTRA OCTET STRING OPTIONAL, candidateServingFreqListEUTRA CandidateServingFreqListEUTRA OPTIONAL, needForGaps ENUMERATED {true} OPTIONAL, drx-ConfigSCG DRX-Config OPTIONAL, reportCGI-RequestEUTRA SEQUENCE { requestedCellInfoEUTRA SEQUENCE { eutraFrequency ARFCN- ValueEUTRA, cellForWhichToReportCGI-EUTRA EUTRA- PhysCellId } OPTIONAL } OPTIONAL, nonCriticalExtension CG-Config-v1590-IEs OPTIONAL } MeasConfigSN ::= SEQUENCE { measuredFrequenciesSN SEQUENCE (SIZE (1..maxMeasFreqsSN)) OF NR-FreqInfo OPTIONAL, ... } NR-FreqInfo ::= SEQUENCE { measuredFrequency ARFCN-ValueNR OPTIONAL, ... }
Figure imgf000014_0001
[0012] In R3-223244, a new field is proposed to F1AP, under the DU to CU RRC Information IE for the gNB-DU to indicate if the inter-frequency SSB measurement will be performed without gaps as the SSB is included in the active BWP. The change request includes the message, where one additional IE, InterFrequencyConfig- NoGap, has been appended to 3GPP TS 38.331 v17.0.0: “9.3.1.26 DU to CU RRC Information This IE contains the RRC Information that are sent from the gNB-DU to the gNB-CU.
Figure imgf000015_0001
Figure imgf000016_0001
Figure imgf000017_0001
Figure imgf000018_0001
SUMMARY [0013] There currently exist certain challenge(s). [0014] A first problem is that bandwidth part (BWP) handling is dynamic during scheduling, based on Downlink Control Info (DCI), while the gap configuration is performed via RRC requiring reconfigurations. The conditionality of measurements based on active BWP means that the gNB-CU has no guarantee that the measurements will succeed, nor how long the measurement will take. [0015] Consider the example from Figure 3. If the gNB-CU configures UE1 with measurements on SSB3, even if the gNB-DU indicates that no gaps are needed and signals InterFrequencyConfig-NoGap set to “true”, it can decide to activate Dedicated BWP2, resulting in no measurement reports. This is due to the fact that the dynamic allocation to the UE of Dedicated BWP2 has implied that SSB3 is not contained in the active BWP and that SSB3 is not measurable without gaps. The problem in this situation is that the gNB-CU will not receive measurements from the UE [0016] A second problem is concerned with NR-DC, where interFrequencyConfig- NoGap-r16 applies to both cell groups (Master Cell Group (MCG) and Secondary Cell Group (SCG)). Currently the SN gNB-DU is not informed if the IE (e.g., the interFrequencyConfig- NoGap-r16 IE) is set or not. If the MN has configured the UE with interFrequencyConfig- NoGap-r16 set to “true” and if the UE is configured with NR-DC, it might occur that the SN gNB-DU will switch freely between BWPs as it is not aware of the MgNB-CU measurement configuration, nor the MgNB-DU decision to set InterFrequencyConfig-NoGap to true. The problem in this case is that the UE will not report measurements from the SCG because the SSB to be measured is not contained in the SN active BWP. [0017] A third problem is concerned with a similar situation in NR-DC, where the secondary node cannot request the master node to configure interFrequencyConfig-NoGap-r16 even if this configuration would benefit the SCG measurements. The MgNB-DU is not aware of the configured BWPs and thus it cannot know if InterFrequencyConfig-NoGap would be beneficial or not. [0018] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The disclosure comprises the following embodiments: - The possibility to indicate to the SN-gNB-CU and SN-gNB-DU if MN has configured interFrequencyConfig-NoGap-r16 or if the MN has de-configured it. This allows the SN-gNB-DU to adopt appropriate policies for BWP allocation, for example avoiding BWP changes and ensuring that the SSB to be measured and the UE active BWP at the scg are aligned. - The possibility for the SN to indicate to the MN if interFrequencyConfig-NoGap-r16 can be set to true. Namely, an indication from the SN to the MN that the active BWP at the SCG will be allocated in a way that no-gap measurements can be taken by the UE. Similarly, the SN may indicate to the MN that interFrequencyConfig-NoGap-r16 should not be configured, which may correspond to a decision at the SN to use dynamic BWP allocation - The possibility for the gNB-CU to communicate with the gNB-DU to establish if interFrequencyConfig-NoGap-r16 can be used and to guarantee a set of minimum measuring resources. - The possibility for the SN gNB-DU to indicate to the SN gNB-CU that the interFrequencyConfig-NoGap-r16 can be used, so that the SN gNB-CU can signal to the MN that the interFrequencyConfig-NoGap-r16 can be used at the SN. This may trigger the MN to also configure the interFrequencyConfig-NoGap-r16 to “true” and configure the UE accordingly. [0019] Embodiments of the disclosure may provide for one or more of: - The capability to indicate to the SN if interFrequencyConfig-NoGap-r16 has been configured by the MN. - The capability for the SN to request interFrequencyConfig-NoGap to the MN. - The capability for the gNB-CU and MN to indicate inter-frequency measurements without gaps so the gNB-DU or SN maintains an active BWP that allows for the measurements to be performed. [0020] A first aspect of the disclosure provides a method performed by a first network node. The method comprises: providing a user equipment with a configuration for performance of inter-frequency measurements without a measurement gap; and transmitting, to a second network node, an indication of the configuration for performance of inter-frequency measurements without a measurement gap. [0021] A second aspect of the disclosure provides a method performed by a second network node. The method comprises: receiving, from a first network node, an indication of a configuration provided to a user equipment for performance of inter-frequency measurements without a measurement gap; and adaptively scheduling the user equipment for transmission or reception using one or more bandwidth parts based on the configuration. [0022] Apparatus and computer programs for performing the methods of the aspects of the disclosure are also provided. For example, a first network node comprises processing circuitry configured to cause the first network node to: provide a user equipment with a configuration for performance of inter-frequency measurements without a measurement gap; and transmit, to a second network node, an indication of the configuration for performance of inter-frequency measurements without a measurement gap. In another example, a second network node comprises processing circuitry configured to cause the second network node to: receive, from a first network node, an indication of a configuration provided to a user equipment for performance of inter-frequency measurements without a measurement gap; and adaptively schedule the user equipment for transmission or reception using one or more bandwidth parts based on the configuration. [0023] Certain embodiments may provide one or more of the following technical advantage(s): better measurement coordination between nodes involved in multi connectivity towards the UE; increased throughput and decreased latency, particularly in the cases where measurement gaps are no longer needed. BRIEF DESCRIPTION OF THE DRAWINGS [0024] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which: [0025] Figure 1 shows the NG-RAN overall architecture (taken from 3GPP TS 38.401 v17.0.0); [0026] Figure 2 shows an example of bandwidth adaptation (taken from 3GPP TS 38.300 v17.0.0); [0027] Figure 3 shows an example of multiple SSBs in a carrier (taken from 3GPP TS 38.300 v17.0.0); [0028] Figure 4 shows the SN addition procedure taken from 3GPP TS 37.340 v17.0.0; [0029] Figure 5 shows the MN-initiated SN modification procedure taken from 3GPP TS 37.340 v17.0.0; [0030] Figure 6 shows the SN initiated SN modification procedure with MN involvement taken from 3GPP TS 37.340 v17.0.0; [0031] Figure 7 is a flowchart of a method performed by a first network node according to embodiments of the disclosure; [0032] Figure 8 is a flowchart of a method performed by a second network node according to embodiments of the disclosure; [0033] Figure 9 is a flowchart of a method performed by a second network node according to further embodiments of the disclosure; [0034] Figure 10 is a flowchart of a method performed by a second network node according to yet further embodiments of the disclosure; [0035] Figure 11 is a flowchart of a method performed by a system according to embodiments of the disclosure; [0036] Figure 12 is a signalling flow performed by a system according to embodiments to the disclosure; [0037] Figure 13 is a signalling flow performed by a system according to further embodiments to the disclosure; [0038] Figure 14 shows an example of a communication system according to embodiments of the disclosure; [0039] Figure 15 shows an example of a user equipment according to embodiments of the disclosure; [0040] Figure 16 shows an example of a network node according to embodiments of the disclosure; [0041] Figure 17 is a block diagram of host according to embodiments of the disclosure; [0042] Figure 18 is a block diagram illustrating a virtualization environment according to embodiments of the disclosure; and [0043] Figure 19 is a communication diagram according to embodiments of the disclosure. DETAILED DESCRIPTION [0044] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. [0045] Embodiments of the disclosure relate to the configuration of measurement gaps in which a user equipment (UE) performs inter-frequency measurements, e.g., measurements on reference signals (e.g., SSB) transmitted by non-serving cells or network nodes. Measurement gaps may comprise a suspension in communication between the user equipment and a serving network node, such that the UE has time to re-tune its receiver circuitry (if necessary). As noted above, “intra-frequency” measurements may be defined as measurements where the centre frequency of the SSB of a serving cell indicated for measurement and the centre frequency of the SSB of the neighbour cell (on which the measurements are to be performed) are the same, and the subcarrier spacing of the two SSBs are also the same. Inter-frequency measurements are any type of measurement which does not fit the definition of intra-frequency measurements. Thus it may happen that an inter-frequency measurement is defined on an SSB of a neighbour cell whose centre frequency is the same as the serving cell, but where the subcarrier spacings of the SSBs are different. Where the frequency or frequency ranges (e.g., corresponding to SSBs transmitted by non-serving cells) on which a UE is configured to perform inter-frequency measurements fall within an active bandwidth part of the UE, inter- frequency measurements may be performed without a measurement gap. [0046] Figure 7 depicts a method in accordance with particular embodiments. The method may be performed by a first network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively). The first network node may be a radio access network node, such as a master node (MN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration. The method comprises interactions with a second network node which, in this example, may be a secondary node of the dual- or multi-connectivity configuration for the UE. Either or both of the master node and the second node may have a distributed architecture, comprising a centralized unit (CU) and one or more distributed units (DUs). Alternatively, the first network node may itself be a radio access network node such as a centralized unit (CU) of a base station having a distributed architecture. In this example, the second network node may be a distributed unit (DU) of the base station. The base station may belong to a plurality of base stations providing service to a UE as part of a dual- or multi-connectivity configuration, and may be a master node or a secondary node. [0047] In step 702, the first network node provides a user equipment with a configuration for the performance of inter-frequency measurements without a measurement gap. In some embodiments, this step may correspond to the RRC Reconfiguration message transmitted from the MN-gNB to the UE in Figure 13 below. [0048] The configuration may comprise a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. That is, the configuration may configure the UE to perform measurements on one or more frequencies or frequency ranges (e.g., corresponding to SSBs transmitted by other, neighbouring cells). The configuration may further comprise an indication as to whether the UE is configured to perform measurements on those frequencies or frequency ranges with or without measurement gaps. Separate indications may be provided for each frequency or frequency range, such that the UE is configured to perform measurements (such as intra- or inter-frequency measurements) with a measurement gap for some frequencies or frequency ranges, and to perform measurements (such as intra- or inter-frequency measurements) without a measurement gap for other frequencies or frequency ranges. [0049] In step 704, the first network node transmits, to a second network node, an indication of the configuration for the performance of inter-frequency measurements without a measurement gap. In some embodiments, this step may correspond to the XnAP S-NODE MODIFICATION REQUEST message transmitted from the MN-gNB-CU to the SN-gNB-CU in Figure 13. [0050] The indication may correspond to the configuration provided to the UE in step 702, or may convey only part of the information contained in the configuration provided to the UE in step 702. For example, the indication of the configuration transmitted to the second network node in step 704 may indicate only that a configuration of inter-frequency measurements without measurement gaps has changed, has been added, or has been removed. [0051] The indication of the configuration may be transmitted over a direct interface between the first and second network nodes, such as the Xn interface (e.g., where the network nodes are MN/SN in a dual- or multi-connectivity configuration) or the F1 interface (e.g., where the network nodes are CU/DU in a base station having a distributed architecture). [0052] Thus, where the first network node is a master node in a multi connectivity configuration towards the UE, e.g. the first network node is a MN in a NR-DC configuration, the first network node informs the second network node (e.g., the SN), of where the UE is configured to perform inter-frequency measurements without a measurement gap in the master cell group (MCG), e.g. interFrequencyConfig-NoGap. In one embodiment, the indication of the configuration may be transmitted, in step 704, inside the CG-ConfigInfo container included in the XnAP S-NODE ADDITION REQUEST or S-NODE MODIFICATION REQUEST. One example of this container is set out below (where underlined passages indicate changes to the existing technical specifications): CG-ConfigInfo message -- ASN1START -- TAG-CG-CONFIG-INFO-START CG-ConfigInfo ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ cg-ConfigInfo CG-ConfigInfo-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } CG-ConfigInfo-IEs ::= SEQUENCE { […] measConfigMN MeasConfigMN OPTIONAL, […] } MeasConfigMN ::= SEQUENCE { measuredFrequenciesMN SEQUENCE (SIZE (1..maxMeasFreqsMN)) OF NR-FreqInfo OPTIONAL, measGapConfig SetupRelease { GapConfig } OPTIONAL, gapPurpose ENUMERATED {perUE, perFR1} OPTIONAL, ..., [[ measGapConfigFR2 SetupRelease { GapConfig } OPTIONAL ]] [[
Figure imgf000024_0001
} [0053] Alternatively, the first network node (e.g. MN) may signal such information to the second network node (e.g. SN) over a direct interface between the two nodes, e.g. such as the Xn interface. An example of how this information may be signaled from MN to SN is via the addition of the InterFrequencyConfig-NoGap IE defined as an Enumerated with value “True” or “False” in the Xn: S-NODE ADDITION REQUEST or in the Xn: S-NODE MODIFICATION REQUEST. An example is shown below for the Xn: S-NODE ADDITION REQUEST (where underlined passages show changes to the existing technical specifications): 9.1.2.1 S-NODE ADDITION REQUEST This message is sent by the M-NG-RAN node to the S-NG-RAN node to request the preparation of resources for dual connectivity operation for a specific UE. Direction: M-NG-RAN node
Figure imgf000025_0001
node.
Figure imgf000026_0001
Figure imgf000027_0001
Figure imgf000028_0001
Figure imgf000029_0001
Figure imgf000029_0002
Figure imgf000029_0003
[0054] Upon reception, the second network node (e.g. SgNB) understands that it is possible to configure inter-frequency measurements without gaps when the target SSB is included in in the active bandwidth part (BWP). Hence, the second network node is enabled to adopt appropriate policies for the effective use of no-gap measurements at the second network node, e.g. the second network node may adopt policies that ensure alignment between the target SSB to be measured and the active BWP at the SCG. [0055] Note that, where the second network node is a RAN node having a split or distributed architecture, step 704 may comprise transmitting the indication of the configuration to the CU of the second network node, for onward transmission to the DU of the second network node, e.g., where the CG-ConfigInfo is forwarded to the DU (e.g. SgNB-DU). In this case, the DU understands that it needs to configure a BWP that allows the SgNB configured measurements to be performed without measurement gap, e.g. the Dedicated BWP with the broadest bandwidth. [0056] Alternatively, particularly where the first network node comprises a CU and the second network node comprises a DU, the indication of the configuration (e.g., InterFrequencyConfig-NoGap) may be signalled as part of the DU to CU RRC Information IE, or the CU to DU RRC Information IE (e.g., over the F1 interface). [0057] As noted above, the signaling from the first node CU to the second node CU and consequently from the second node CU to the second node DU may include information that the configuration to perform inter-frequency measurements without a measurement gap (e.g., InterFrequencyConfig-NoGap) has been removed. This information may allow the second network node DU to change its BWP management policy and to enable a more dynamic BWP allocation without necessarily respecting that the active BWP includes the target SSB to be measured. [0058] Figure 8 depicts a method in accordance with particular embodiments. The method may be performed by a second network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively). The second network node may be a radio access network node, such as a secondary node (SN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration. The method comprises interactions with a first network node which, in this example, may be a master node (MN) of the dual- or multi-connectivity configuration for the UE. Either or both of the master node and the second node may have a distributed architecture, comprising a centralized unit (CU) and one or more distributed units (DUs). Alternatively, the second network node may itself be a radio access network node such as a DU of a base station having a distributed architecture. In this example, the first network node may be a CU of the base station. The base station may belong to a plurality of base stations providing service to a UE as part of a dual- or multi-connectivity configuration, and may be a master node or a secondary node. It will be apparent to the skilled reader that, in some embodiments, the steps in Figure 8 may provide a complement to the steps performed in Figure 7, performed by the first network node. [0059] The method begins at step 802, in which the second network node receives, from a first network node, an indication of a configuration provided to a user equipment for the performance of inter-frequency measurements without a measurement gap. This step may correspond to step 704 described above, and/or the XnAP S-NODE MODIFICATION REQUEST message transmitted from the MN-gNB-CU to the SN-gNB-CU in Figure 13. [0060] The configuration may comprise a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. That is, the configuration may configure the UE to perform measurements on one or more frequencies or frequency ranges (e.g., corresponding to SSBs transmitted by other, neighbouring cells). The configuration may further comprise an indication as to whether the UE is configured to perform measurements on those frequencies or frequency ranges with or without measurement gaps. Separate indications may be provided for each frequency or frequency range, such that the UE is configured to perform measurements (such as intra- or inter-frequency measurements) with a measurement gap for some frequencies or frequency ranges, and to perform measurements (such as intra- or inter-frequency measurements) without a measurement gap for other frequencies or frequency ranges. [0061] The indication of the configuration may correspond to the configuration itself, or may convey only part of the information contained in the configuration. For example, the indication of the configuration received from the first network node may indicate only that a configuration of inter-frequency measurements without measurement gaps has changed, has been added, or has been removed. [0062] In step 804, the second network node adaptively schedules the user equipment for transmission or reception using one or more bandwidth parts based on the configuration. For example, the second network node may activate the Dedicated BWP with the broadest bandwidth. Additionally or alternatively, the second network node may schedule the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. Additionally or alternatively, the second network node may preferentially schedule the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap, e.g., by scheduling the user equipment with the active bandwidth part more often, or with higher priority than other bandwidth parts. [0063] Figure 9 depicts a method in accordance with particular embodiments. The method may be performed by a second network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively). In this example, the second network node may be a radio access network node, such as a secondary node (SN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration. The method comprises interactions with a first network node which, in this example, may be a master node (MN) of the dual- or multi-connectivity configuration for the UE. In particular embodiments, the second network node may be a CU of a secondary node having a distributed or split architecture. [0064] The method begins at step 902, in which the second network node communicates with the DU of the secondary node to determine whether a UE served by the secondary node is able to perform inter-frequency measurements without a measurement gap. This communication may correspond to steps 1102, 1104 and 1106 described with respect to Figure 11, and/or the F1AP UE CONTEXT MODIFICATION message first transmitted from the SN- gNB-CU to the SN-gNB-DU in Figure 12 and the F1AP UE CONTEXT MODIFICATION RESPONSE message first transmitted from the SN-gNB-DU to the SN-gNB-CU in Figure 12. [0065] Step 902 may comprise determining whether the user equipment is able to perform inter-frequency measurements on a defined list of one or more frequencies or frequency ranges without a measurement gap. For example, the second network node may perform a query by sending its list of inter-frequency measurements in the cell bandwidth to the DU in e.g. the F1 CU to DU RRC Information IE. The DU may then response by indicating (e.g., in the F1 DU to CU RRC Information IE) whether those measurements require a measurement gap. [0066] In step 904, the second network node transmits, to a first network node (e.g., a MN for the UE), a request for a user equipment served by the second network node to be configured for the performance of inter-frequency measurements without a measurement gap. Step 904 may correspond, in some embodiments, to step 1108 in Figure 11, and/or the transmission of XnAP S-NODE MODIFICATION REQUIRED message from the SN-gNB-CU to the MN- gNB-CU in Figure 12. [0067] The request may comprise a frequency or a range of frequencies on which the user equipment is requested to be configured for the performance of inter-frequency measurements without a measurement gap. Further, the request may comprise an indication that the user equipment is requested to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. Additionally or alternatively, the request may comprise an indication that the user equipment is requested not to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. [0068] The request may comprise respective indications for the performance of inter- frequency measurements without a measurement gap for each of a plurality of frequencies or frequency ranges, or a single indication for the performance of inter-frequency measurements without a measurement gap in respect of all frequencies or frequency ranges. [0069] Where the second network node has first communicated with the DU to determine whether the UE is able to perform inter-frequency measurements without a measurement gap, the request may be transmitted in step 904 responsive to receipt of confirmation from the DU of the secondary node that the user equipment will be adaptively scheduled on one or more bandwidth parts so as to enable the performance of inter-frequency measurements without a measurement gap. [0070] The request may be transmitted, for example, in an S-NODE ADDITION REQUEST ACKNOWLEDGE message, an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE ADDITION REQUIRED message. The second network node (e.g. SgNB) can thus indicate to the first node (e.g. MgNB) a request to configure interFrequencyConfig-NoGap-r16, for example as part of the CG-Config IE included in the XnAP messages S-NODE ADDITION REQUEST ACKNOWLEDGE or S-NODE MODIFICATION REQUEST ACKNOWLEDGE according to the following example (underlined passages indicate changes to the current technical specifications): CG-Config message -- ASN1START -- TAG-CG-CONFIG-START CG-Config ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ cg-Config CG-Config-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } CG-Config-IEs ::= SEQUENCE { scg-CellGroupConfig OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, configRestrictModReq ConfigRestrictModReqSCG OPTIONAL, drx-InfoSCG DRX-Info OPTIONAL, candidateCellInfoListSN OCTET STRING (CONTAINING MeasResultList2NR) OPTIONAL, measConfigSN MeasConfigSN OPTIONAL, selectedBandCombination BandCombinationInfoSN OPTIONAL, fr-InfoListSCG FR-InfoList OPTIONAL, candidateServingFreqListNR CandidateServingFreqListNR OPTIONAL, nonCriticalExtension CG-Config-v1540-IEs OPTIONAL } […] MeasConfigSN ::= SEQUENCE { measuredFrequenciesSN SEQUENCE (SIZE (1..maxMeasFreqsSN)) OF NR-FreqInfo OPTIONAL, reqInterFreqConfig-NoGap BOOLEAN OPTIONAL, ... } NR-FreqInfo ::= SEQUENCE { measuredFrequency ARFCN-ValueNR OPTIONAL, ... } -- TAG-CG-CONFIG-STOP -- ASN1STOP [0071] In the exemplary embodiment above the request is indicated as a global flag at SN level. In another embodiment, the request is provided on a per-frequency basis, e.g., as part of the NR-FreqInfo IE. [0072] Alternatively, the SgNB may request the configuration as part of a XnAP S-NODE ADDITION REQUIRED as part of ConfigRestrictModReqSCG. An example of this embodiment is copied below (underlined passages show changes to the existing technical specifications): CG-Config message -- ASN1START -- TAG-CG-CONFIG-START CG-Config ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ cg-Config CG-Config-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } CG-Config-IEs ::= SEQUENCE { scg-CellGroupConfig OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, configRestrictModReq ConfigRestrictModReqSCG OPTIONAL, drx-InfoSCG DRX-Info OPTIONAL, candidateCellInfoListSN OCTET STRING (CONTAINING MeasResultList2NR) OPTIONAL, measConfigSN MeasConfigSN OPTIONAL, selectedBandCombination BandCombinationInfoSN OPTIONAL, fr-InfoListSCG FR-InfoList OPTIONAL, candidateServingFreqListNR CandidateServingFreqListNR OPTIONAL, nonCriticalExtension CG-Config-v1540-IEs OPTIONAL } […] ConfigRestrictModReqSCG ::= SEQUENCE { requestedBC-MRDC BandCombinationInfoSN OPTIONAL, requestedP-MaxFR1 P-Max OPTIONAL, reqinterFreqConfig-NoGap BOOLEAN OPTIONAL, ..., [[ requestedPDCCH-BlindDetectionSCG INTEGER (1..15) OPTIONAL, requestedP-MaxEUTRA P-Max OPTIONAL ]], [[ requestedP-MaxFR2-r16 P-Max OPTIONAL, requestedMaxInterFreqMeasIdSCG-r16 INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, requestedMaxIntraFreqMeasIdSCG-r16 INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, requestedToffset-r16 T-Offset-r16 OPTIONAL ]] } -- TAG-CG-CONFIG-STOP -- ASN1STOP [0073] Alternatively, the InterFrequencyConfig-NoGap indication (for example with values “true”, “false”) from the second network node to the first network node (e.g. from SN to MN) may be signalled as a new IE over the Xn interface, e.g. within the Xn: S-NODE ADDITION REQUEST ACKNOWLEDGE or Xn: S-NODE MODIFICATION REQUEST ACKNOWLEDGE. [0074] The second node CU may thus indicate to the MgNB if all its measurements can be performed without measurement gap. This would allow the first network node to skip the measurement gap and thereby improve the UE throughput in cases when the first network node does not have any measurements configured on its own or when all the first network node’s measurements can also be performed without measurement gap. [0075] Thus, in embodiments where the second network node is a CU of a secondary node, the CU can decide whether to send the reqInterFreqConfig-NoGap indication to the first node by first querying the secondary node DU over the F1 interface in step 902. This is advantageous since it is the secondary node DU that controls the Bandwidth Adaptation and hence has the information of whether measurement gaps are needed or not for the required measurements. The secondary node CU may perform the query by sending its list of inter-frequency measurements in the cell bandwidth to the secondary node DU in e.g. the F1 CU to DU RRC Information IE and the secondary node DU indicates in e.g. the F1 DU to CU RRC Information IE whether those measurements require a gap. If no gap is required, the secondary node CU sends the reqInterFreqConfig-NoGap indication to the first network node (e.g. MgNB), e.g., over a direct interface between the first and second network nodes, e.g. the Xn interface. One alternative is to add a corresponding indication reqInterFreqConfig-NoGap to the e.g. F1 DU to CU RRC Information IE which can be simply forwarded by the second node CU over e.g. Xn to the first node. Another alternative is to re-use the existing/proposed interFrequencyConfig-NoGap indication in the e.g. F1 DU to CU RRC Information IE by updating the semantic description of the IE. [0076] The embodiments set out above have described where the second network node requests that a UE be configured to perform inter-frequency measurements without a measurement gap. Of course, embodiments of the disclosure also contemplate and include the opposite arrangement, where the second network node requests that a UE that is already configured to perform inter-frequency measurements without a measurement gap, be no longer so configured. This may come as a consequence of the DU signalling to the second network node (e.g., in step 902 above). [0077] Figure 10 depicts a method in accordance with particular embodiments. The method may be performed by a second network node (e.g. the network node 1410 or network node 1600 as described later with reference to Figures 14 and 16 respectively). In this example, the second network node may be a radio access network node, such as a DU of a secondary node (SN) providing service to a user equipment (UE) as part of a dual- or multi-connectivity configuration. The method comprises interactions with a first network node which, in this example, may be a CU of the SN. In some embodiments, the steps of the method shown in Figure 10 may correspond to the signalling and steps of the DU described above with respect to step 902. [0078] The method begins at step 1002, in which the second network node receives, from a first network node, an indication of one or more frequencies or frequency ranges on which a user equipment is configured to perform measurements. This step may correspond to step 1104 in Figure 11, and/or the reception of either or both of the F1AP UE CONTEXT MODIFICATION messages in Figure 12. [0079] In step 1004, the second network node transmits, to the first network node, an indication of one or more of the frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap. This step may correspond to step 1106 below in Figure 11, and/or the transmission of either or both of the F1AP UE CONTEXT MODIFICATION RESPONSE messages in Figure 12. [0080] In step 1006, the second network node schedules the user equipment with an active bandwidth part which encompasses the one or more frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap. [0081] According to this embodiment, the second network node is involved in configuration of UE measurements with and without measurement gaps. The second network node (e.g., RAN node DU), upon receiving from the CU an indication of the frequency on which the UE should perform measurements (e.g. by receiving the MeasConfig IE defined in TS38.331 v17.0.0) and after receiving indications of the measurement gaps needed for such measurements (as in step 1002), may reply to the RAN node CU in step 1004 with both information concerning the configuration of the measurements gaps for the UE (e.g. by signalling the MeasGapConfig IE defined over TS38.331), and with a InterFrequencyConfig- NoGap set to “true”, indicating that some measurements may be taken without the need for gaps. If, after signalling such information, the InterFrequencyConfig-NoGap cannot be supported by the DU anymore (e.g., the active BWP allocation is such that it does not allow the UE to measure without gaps), the DU may signal to the CU the InterFrequencyConfig- NoGap set to “false”. This implies that all measurements will be taken by means of the gaps configured as per the measurement gap configuration, e.g. MeasGapConfig IE, signalled from DU to CU. If on the other hand, some or all of the gaps configured e.g. via the MeasGapConfig are de-allocated by the DU, and the DU signals such change in measurement gap configuration to the CU, while maintaining the InterFrequencyConfig-NoGap set to “true”, it means that the measurements will be taken by the UE solely via no-gaps measurements. [0082] Figure 11 shows a flowchart of a method in a system according to embodiments of the disclosure. In particular embodiments, the method may enable the configuration of interFrequencyConfig-NoGap with SN involvement in NR-DC. [0083] Figure 12 shows a signalling flow in a system according to embodiments of the disclosure, and particularly the method of Figure 11. The signalling flow may provide for SN- initiated measurements requesting interFrequencyConfig-NoGap-r16 to be configured by the MN. [0084] In step 1102, the SN-gNB-CU configures inter-frequency measurements associated with the SCG. In step 1104, the the SN-gNB-CU provides the SN-gNB-DU with an indicator to activate interFrequencyConfig-NoGaps, e.g., see F1AP UE CONTEXT MODIFICATION (CU-to-DU RRC Container (reqInterFreqConfig-NoGap)) in Figure 12. In step 1106, the SN- gNB-DU sends a signal to the SN-gNB-CU indicating that interFrequencyConfig-NoGaps is ok to configure, e.g., see F1AP UE CONTEXT MODIFICATION RESPONSE (DU-to-CU RRC Container (InterFreqConfig-NoGap)) in Figure 12. In step 1108, the SN-gNB-CU informs the MN-gNB-CU that it wants to activate interFrequencyConfig-NoGaps, e.g., see XnAP S-NODE MODIFICATION REQUIRED (cg-Config(reqInterFreqConfig-NoGap)) in Figure 12. In step 1110, the MN-gNB-CU provides the MN-gNB-DU with an indicator to activate interFrequencyConfig-NoGaps, e.g., see XnAP S-NODE MODIFICATION REQUIRED (reqInterFreqConfig-NoGap) in Figure 12. In step 1112, the MN-gNB-DU signals (e.g., to the MN-gNB-CU) that interFrequencyConfig-NoGaps is ok to configure, e.g., see XnAP S-NODE MODIFICATION REQUIRED (cg-Config(reqInterFreqConfig-NoGap)) in Figure 12. In step 1114, the MN-gNB-CU reconfigures the UE with SCG measurements and interFrequencyConfig-NoGaps, e.g., see RRC Reconfiguration (configuring the UE with no-gap measurements) in Figure 12. [0085] Figure 13 shows a signalling flow in a system according to embodiments of the disclosure. The signalling flow may provide for MN-initiated measurements requesting interFrequencyConfig-NoGap-r16 to be configured by the MN. In the embodiment shown in Figure 13, the MN informs the SN of the configured no-gap measurements, so that the SN can ensure that such measurements can be performed at the SCG. [0086] Figure 14 shows an example of a communication system 1400 in accordance with some embodiments. [0087] In the example, the communication system 1400 includes a telecommunication network 1402 that includes an access network 1404, such as a radio access network (RAN), and a core network 1406, which includes one or more core network nodes 1408. The access network 1404 includes one or more access network nodes, such as network nodes 1410a and 1410b (one or more of which may be generally referred to as network nodes 1410), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1412a, 1412b, 1412c, and 1412d (one or more of which may be generally referred to as UEs 1412) to the core network 1406 over one or more wireless connections. [0088] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0089] The UEs 1412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1410 and other communication devices. Similarly, the network nodes 1410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1412 and/or with other network nodes or equipment in the telecommunication network 1402 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1402. [0090] In the depicted example, the core network 1406 connects the network nodes 1410 to one or more hosts, such as host 1416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1406 includes one more core network nodes (e.g., core network node 1408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0091] The host 1416 may be under the ownership or control of a service provider other than an operator or provider of the access network 1404 and/or the telecommunication network 1402, and may be operated by the service provider or on behalf of the service provider. The host 1416 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0092] As a whole, the communication system 1400 of Figure 14 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. [0093] In some examples, the telecommunication network 1402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1402. For example, the telecommunications network 1402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. [0094] In some examples, the UEs 1412 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1404. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN- DC). [0095] In the example illustrated in Figure 14, the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412c and/or 1412d) and network nodes (e.g., network node 1410b). In some examples, the hub 1414 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub 1414 may be a broadband router enabling access to the core network 1406 for the UEs. As another example, the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1410, or by executable code, script, process, or other instructions in the hub 1414. As another example, the hub 1414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [0096] The hub 1414 may have a constant/persistent or intermittent connection to the network node 1410b. The hub 1414 may also allow for a different communication scheme and/or schedule between the hub 1414 and UEs (e.g., UE 1412c and/or 1412d), and between the hub 1414 and the core network 1406. In other examples, the hub 1414 is connected to the core network 1406 and/or one or more UEs via a wired connection. Moreover, the hub 1414 may be configured to connect to an M2M service provider over the access network 1404 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1410 while still connected via the hub 1414 via a wired or wireless connection. In some embodiments, the hub 1414 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1410b. In other embodiments, the hub 1414 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0097] Figure 15 shows a UE 1500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle- mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0098] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [0099] The UE 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a power source 1508, a memory 1510, a communication interface 1512, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 15. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [0100] The processing circuitry 1502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1510. The processing circuitry 1502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1502 may include multiple central processing units (CPUs). The processing circuitry 1502 may be operable to provide, either alone or in conjunction with other UE 1500 components, such as the memory 1510, UE 1500 functionality. [0101] In the example, the input/output interface 1506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1500. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0102] In some embodiments, the power source 1508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1508 may further include power circuitry for delivering power from the power source 1508 itself, and/or an external power source, to the various parts of the UE 1500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1508 to make the power suitable for the respective components of the UE 1500 to which power is supplied. [0103] The memory 1510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1510 includes one or more application programs 1514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1516. The memory 1510 may store, for use by the UE 1500, any of a variety of various operating systems or combinations of operating systems. [0104] The memory 1510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1510 may allow the UE 1500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1510, which may be or comprise a device-readable storage medium. [0105] The processing circuitry 1502 may be configured to communicate with an access network or other network using the communication interface 1512. The communication interface 1512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1522. The communication interface 1512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1518 and/or a receiver 1520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1518 and receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522) and may share circuit components, software or firmware, or alternatively be implemented separately. [0106] In some embodiments, communication functions of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0107] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0108] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input. [0109] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence on the intended application of the IoT device in addition to other components as described in relation to the UE 1500 shown in Figure 15. [0110] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0111] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [0112] Figure 16 shows a network node 1600 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). [0113] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). [0114] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). [0115] The network node 1600 includes processing circuitry 1602, a memory 1604, a communication interface 1606, and a power source 1608, and/or any other component, or any combination thereof. The network node 1600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1604 for different RATs) and some components may be reused (e.g., a same antenna 1610 may be shared by different RATs). The network node 1600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1600. [0116] The processing circuitry 1602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1600 components, such as the memory 1604, network node 1600 functionality. For example, the processing circuitry 1602 may be configured to cause the network node to perform the methods as described with reference to Figures 7, 8, 9 and/or 10. The processing circuitry 1602 may also or alternatively be configured to cause the network node to perform any of the steps of the method as shown in Figure 11, and/or any of the signalling and processing of the MN-gNB- DU, MN-gNB-CU, SN-gNB-CU or CN-gNB-DU in Figures 12 and 13. [0117] In some embodiments, the processing circuitry 1602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614. In some embodiments, the radio frequency (RF) transceiver circuitry 1612 and the baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1612 and baseband processing circuitry 1614 may be on the same chip or set of chips, boards, or units. [0118] The memory 1604 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1602. The memory 1604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1602 and utilized by the network node 1600. The memory 1604 may be used to store any calculations made by the processing circuitry 1602 and/or any data received via the communication interface 1606. In some embodiments, the processing circuitry 1602 and memory 1604 is integrated. [0119] The communication interface 1606 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1606 comprises port(s)/terminal(s) 1616 to send and receive data, for example to and from a network over a wired connection. The communication interface 1606 also includes radio front-end circuitry 1618 that may be coupled to, or in certain embodiments a part of, the antenna 1610. Radio front-end circuitry 1618 comprises filters 1620 and amplifiers 1622. The radio front-end circuitry 1618 may be connected to an antenna 1610 and processing circuitry 1602. The radio front-end circuitry may be configured to condition signals communicated between antenna 1610 and processing circuitry 1602. The radio front-end circuitry 1618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1620 and/or amplifiers 1622. The radio signal may then be transmitted via the antenna 1610. Similarly, when receiving data, the antenna 1610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1618. The digital data may be passed to the processing circuitry 1602. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0120] In certain alternative embodiments, the network node 1600 does not include separate radio front-end circuitry 1618, instead, the processing circuitry 1602 includes radio front-end circuitry and is connected to the antenna 1610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1612 is part of the communication interface 1606. In still other embodiments, the communication interface 1606 includes one or more ports or terminals 1616, the radio front-end circuitry 1618, and the RF transceiver circuitry 1612, as part of a radio unit (not shown), and the communication interface 1606 communicates with the baseband processing circuitry 1614, which is part of a digital unit (not shown). [0121] The antenna 1610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1610 may be coupled to the radio front- end circuitry 1618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1610 is separate from the network node 1600 and connectable to the network node 1600 through an interface or port. [0122] The antenna 1610, communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1610, the communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [0123] The power source 1608 provides power to the various components of network node 1600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1600 with power for performing the functionality described herein. For example, the network node 1600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1608. As a further example, the power source 1608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [0124] Embodiments of the network node 1600 may include additional components beyond those shown in Figure 16 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1600 may include user interface equipment to allow input of information into the network node 1600 and to allow output of information from the network node 1600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1600. [0125] Figure 17 is a block diagram of a host 1700, which may be an embodiment of the host 1416 of Figure 14, in accordance with various aspects described herein. As used herein, the host 1700 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1700 may provide one or more services to one or more UEs. [0126] The host 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a network interface 1708, a power source 1710, and a memory 1712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 15 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host 1700. [0127] The memory 1712 may include one or more computer programs including one or more host application programs 1714 and data 1716, which may include user data, e.g., data generated by a UE for the host 1700 or data generated by the host 1700 for a UE. Embodiments of the host 1700 may utilize only a subset or all of the components shown. The host application programs 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1700 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [0128] Figure 18 is a block diagram illustrating a virtualization environment 1800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. [0129] Applications 1802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [0130] Hardware 1804 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1808a and 1808b (one or more of which may be generally referred to as VMs 1808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1806 may present a virtual operating platform that appears like networking hardware to the VMs 1808. [0131] The VMs 1808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1806. Different embodiments of the instance of a virtual appliance 1802 may be implemented on one or more of VMs 1808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [0132] In the context of NFV, a VM 1808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1808, and that part of hardware 1804 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1808 on top of the hardware 1804 and corresponds to the application 1802. [0133] Hardware 1804 may be implemented in a standalone network node with generic or specific components. Hardware 1804 may implement some functions via virtualization. Alternatively, hardware 1804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1810, which, among others, oversees lifecycle management of applications 1802. In some embodiments, hardware 1804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1812 which may alternatively be used for communication between hardware nodes and radio units. [0134] Figure 19 shows a communication diagram of a host 1902 communicating via a network node 1904 with a UE 1906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1412a of Figure 14 and/or UE 1500 of Figure 15), network node (such as network node 1410a of Figure 14 and/or network node 1600 of Figure 16), and host (such as host 1416 of Figure 14 and/or host 1700 of Figure 17) discussed in the preceding paragraphs will now be described with reference to Figure 19. [0135] Like host 1700, embodiments of host 1902 include hardware, such as a communication interface, processing circuitry, and memory. The host 1902 also includes software, which is stored in or accessible by the host 1902 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1906 connecting via an over-the-top (OTT) connection 1950 extending between the UE 1906 and host 1902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1950. [0136] The network node 1904 includes hardware enabling it to communicate with the host 1902 and UE 1906. The connection 1960 may be direct or pass through a core network (like core network 1406 of Figure 14) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0137] The UE 1906 includes hardware and software, which is stored in or accessible by UE 1906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1906 with the support of the host 1902. In the host 1902, an executing host application may communicate with the executing client application via the OTT connection 1950 terminating at the UE 1906 and host 1902. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1950 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1950. [0138] The OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide the connection between the host 1902 and the UE 1906. The connection 1960 and wireless connection 1970, over which the OTT connection 1950 may be provided, have been drawn abstractly to illustrate the communication between the host 1902 and the UE 1906 via the network node 1904, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0139] As an example of transmitting data via the OTT connection 1950, in step 1908, the host 1902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1906. In other embodiments, the user data is associated with a UE 1906 that shares data with the host 1902 without explicit human interaction. In step 1910, the host 1902 initiates a transmission carrying the user data towards the UE 1906. The host 1902 may initiate the transmission responsive to a request transmitted by the UE 1906. The request may be caused by human interaction with the UE 1906 or by operation of the client application executing on the UE 1906. The transmission may pass via the network node 1904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1912, the network node 1904 transmits to the UE 1906 the user data that was carried in the transmission that the host 1902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1914, the UE 1906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1906 associated with the host application executed by the host 1902. [0140] In some examples, the UE 1906 executes a client application which provides user data to the host 1902. The user data may be provided in reaction or response to the data received from the host 1902. Accordingly, in step 1916, the UE 1906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1906. Regardless of the specific manner in which the user data was provided, the UE 1906 initiates, in step 1918, transmission of the user data towards the host 1902 via the network node 1904. In step 1920, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1904 receives user data from the UE 1906 and initiates transmission of the received user data towards the host 1902. In step 1922, the host 1902 receives the user data carried in the transmission initiated by the UE 1906. [0141] One or more of the various embodiments improve the performance of OTT services provided to the UE 1906 using the OTT connection 1950, in which the wireless connection 1970 forms the last segment. More precisely, the teachings of these embodiments may improve the measurement performance of the UE 1906, and therefore the radio connections of the UE 1906 are likely to be more reliable and stronger; thereby providing benefits such as reduced user waiting time, reduced drop-out rate of the OTT connection 1950, improved content resolution and better responsiveness. [0142] In an example scenario, factory status information may be collected and analyzed by the host 1902. As another example, the host 1902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1902 may store surveillance video uploaded by a UE. As another example, the host 1902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. [0143] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1950 between the host 1902 and UE 1906, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1902 and/or UE 1906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1902. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1950 while monitoring propagation times, errors, etc. [0144] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [0145] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
The following numbered statements set out some embodiments of the disclosure: Group B Embodiments 1. A method performed by a first network node, the method comprising: providing a user equipment with a configuration for the performance of inter- frequency measurements without a measurement gap; and transmitting, to a second network node, an indication of the configuration for the performance of inter-frequency measurements without a measurement gap. 2. The method according to embodiment 1, wherein the configuration comprises a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. 3. The method according to embodiment 1 or 2, wherein the configuration comprises an indication that the user equipment is to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. 4. The method according to any one of the preceding embodiments, wherein the configuration comprises an indication that the user equipment is not to perform inter- frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. 5. The method according to any one of the preceding embodiments, wherein the first and second network nodes are radio access network nodes. 6. The method according to any one of the preceding embodiments, wherein the indication of the configuration is transmitted to the second network node over a direct interface between the first network node and the second network node. 7. The method according to any one of the preceding embodiments, wherein the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration. The method according to embodiment 7, wherein the first network node is a master node and the second network node is a secondary node. The method according to any one of embodiments 7 to 8, wherein the indication of the configuration is transmitted in an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message. The method according to any one of embodiments 7 to 9, wherein the indication of the configuration is provided as an information element. The method according to any one of embodiments 7 to 9, wherein the indication of the configuration is provided in a CG-ConfigInfo container. The method according to any one of embodiments 7 to 11, wherein the second network node comprises a centralized unit and a distributed unit, wherein the indication of the configuration is transmitted to the centralized unit to be forwarded to the distributed unit. The method according to any one of embodiments 1 to 6, wherein the first network node is a centralized unit of a base station, and the second network node is a distributed unit of a base station. The method according to embodiment 13, wherein the indication of the configuration is provided in a CG-ConfigInfo container. The method according to embodiment 13 or 14, wherein the indication of the configuration is provided in an information element, e.g., DU to CU RRC Information, or CU to DU RRC Information. A method performed by a second network node, the method comprising: receiving, from a first network node, an indication of a configuration provided to a user equipment for the performance of inter-frequency measurements without a measurement gap; and adaptively scheduling the user equipment for transmission or reception using one or more bandwidth parts based on the configuration. The method according to embodiment 16, wherein the configuration comprises a frequency or a range of frequencies on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. The method according to embodiment 16 or 17, wherein the configuration comprises an indication that the user equipment is to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. The method according to any one of embodiments 16 to 18, wherein the configuration comprises an indication that the user equipment is not to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. The method according to any one of embodiments 16 to 19, wherein the first and second network nodes are radio access network nodes. The method according to any one of embodiments 16 to 20, wherein the indication of the configuration is received from the first network node over a direct interface between the first network node and the second network node. The method according to any one of embodiments 16 to 21, wherein the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration. The method according to embodiment 22, wherein the first network node is a master node and the second network node is a secondary node. The method according to any one of embodiments 22 to 23, wherein the indication of the configuration is received in an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message. The method according to any one of embodiments 22 to 24, wherein the indication of the configuration is provided as an information element. The method according to any one of embodiments 22 to 24, wherein the indication of the configuration is provided in a CG-ConfigInfo container. The method according to any one of embodiments 22 to 26, wherein the second network node comprises a centralized unit and a distributed unit, wherein the indication of the configuration is received by the centralized unit to be forwarded to the distributed unit. The method according to any one of embodiments 16 to 21, wherein the first network node is a centralized unit of a base station, and the second network node is a distributed unit of a base station. The method according to embodiment 28, wherein the indication of the configuration is provided in a CG-ConfigInfo container. The method according to embodiment 28 or 29, wherein the indication of the configuration is provided in an information element, e.g., DU to CU RRC Information, or CU to DU RRC Information. The method according to any one of embodiments 16 to 30, wherein adaptively scheduling the user equipment comprises scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. The method according to any one of embodiments 16 to 30, wherein adaptively scheduling the user equipment comprises preferentially scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap. The method according to embodiment 32, wherein preferentially scheduling the user equipment with an active bandwidth part comprises scheduling the user equipment with the active bandwidth part more often, or with higher priority than other bandwidth parts. A method performed by a second network node, the method comprising: transmitting, to a first network node, a request for a user equipment served by the second network node to be configured for the performance of inter- frequency measurements without a measurement gap. The method according to embodiment 34, wherein the request comprises a frequency or a range of frequencies on which the user equipment is requested to be configured for the performance of inter-frequency measurements without a measurement gap. The method according to embodiment 34 or 35, wherein the request comprises an indication that the user equipment is requested to perform inter-frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. The method according to any one of embodiments 34 to 36, wherein the request comprises an indication that the user equipment is requested not to perform inter- frequency measurements without a measurement gap in respect of one or more frequencies or ranges of frequencies. The method according to any one of embodiments 34 to 37, wherein the request comprises respective indications for the performance of inter-frequency measurements without a measurement gap for each of a plurality of frequencies or frequency ranges. The method according to any one of embodiments 34 to 37, wherein the request comprises a single indication for the performance of inter-frequency measurements without a measurement gap in respect of all frequencies or frequency ranges. The method according to any one of embodiments 34 to 39, wherein the first and second network nodes are radio access network nodes. The method according to any one of embodiments 34 to 40, wherein the indication of the configuration is transmitted to the second network node over a direct interface between the first network node and the second network node. The method according to any one of embodiments 34 to 41, wherein the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration. The method according to embodiment 42, wherein the first network node is a master node and the second network node is a secondary node. The method according to embodiment 42, wherein the first network node is a master node and the second network node is a centralized unit of a secondary node. The method according to embodiment 44, further comprising communicating, with a distributed unit of the secondary node, to determine whether the user equipment is able to perform inter-frequency measurements on a defined list of one or more frequencies or frequency ranges without a measurement gap, and wherein the request is transmitted responsive to a determination that the user equipment is able to perform inter-frequency measurements on the defined list of one or more frequencies or frequency ranges without a measurement gap. The method according to embodiment 45, wherein the request is further transmitted responsive to receipt of confirmation from the distributed unit of the secondary node that the user equipment will be adaptively scheduled on one or more bandwidth parts so as to enable the performance of inter-frequency measurements without a measurement gap. The method according to any one of embodiments 42 to 46, wherein the request is transmitted in an S-NODE ADDITION REQUEST ACKNOWLEDGE message, an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE ADDITION REQUIRED message. The method according to any one of embodiments 34 to 41, wherein the first network node is a centralized unit of a base station, and the second network node is a distributed unit of a base station. A method performed by a second network node, the method comprising: receiving, from a first network node, an indication of one or more frequencies or frequency ranges on which a user equipment is configured to perform measurements; and transmitting, to the first network node, an indication of one or more of the frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap. The method according to embodiment 49, further comprising scheduling the user equipment with an active bandwidth part which encompasses the one or more frequencies or frequency ranges on which the user equipment is configurable for the performance of inter-frequency measurements without a measurement gap. The method according to embodiment 49 or 50, wherein the first network node is a centralized unit of a base station, and the second network node is a distributed unit of the base station. The method according to embodiment 51, wherein the base station is a secondary node providing service to the user equipment in a dual- or multi-connectivity configuration. The method according to any one of the preceding embodiments, wherein the measurement gap comprises a suspension in communication between the user equipment and the first network node or the second network node, to enable the user equipment to perform inter-frequency measurements on transmissions by other network nodes. The method according to any one of the preceding embodiments, wherein the user equipment is able to perform inter-frequency measurements without a measurement gap where the measurements are performed on a frequency or a range of frequencies falling within an active bandwidth part configured for the user equipment. 55. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Group C Embodiments 56. A network node, the network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry. 57. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 58. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host. 59. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 60. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE. 61. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. 62. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 63. The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment. 64. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host. 65. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 66. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data. 67. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host. 68. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.
Some abbreviations: 5GC 5G Core AMF Access and Mobility Management Function BA Bandwidth Adaptation BWP Bandwith Part CGI Cell Global Identity CLI Cross Link Interference CR Change Request CU Centralized Unit DC Dual Connectivity DCI Downlink Control Information DU Distributed Unit eNB E-UTRAN Node B E-UTRAN Evolved Universal Terrestrial Radio Access Network F1 Interface between gNB-CU and gNB-DU. F1AP F1 Application Protocol FR Frequency Range FR1 Frequency Range 1 FR2 Frequency Range 2 gNB Next Generation Node B gNB-CU gNB Centralized Unit gNB-DU gNB Distributed Unit IE Informatioomn Element LTE Long Term Evolution MCG Master Cell Group MgNB Master gNB MN Master Node MN-gNB Master Node gNB MR-DC Multi-RAT Dual Connectivity NCGI NR Cell Global Identity NCSG Network Configured Short Gaps NE-DC NR E-Utran Dual Connectivity NG-RAN Next Generation Radio Access Network (NG)EN-DC EN-DC where the Master eNB is connected to 5GC NR New Radio NR-DC NR-NR Dual Connectivity PCell Primary Cell PSCell Primary SCG Cell (in NR) or Primary Secondary Cell (in LTE) RAN Radio Access Network RAT Radio Access Technology RMSI Remaining Minimum System Information RRC Radio Resource Control RRM Radio Resource Management SCG Secondary Cell Group SgNB Secondary gNB SgNB-CU Secondary gNB Centralized Unit SgNB-DU Secondary gNB Distributed Unit SMTC SSB Measurement Timing Configuration SN Secondary Node SN-gNB Secondary Node gNB SpCell Secondary Primary Cell SRB Signaling Radio Bearer SSB Synchronization Signal Block SS-RSRP Synchronization Signal Reference Signal Received Power SS-RSRQ Synchronization Signal Reference Signal Received Quality SS-SINR Synchronization Signal Signal to Interference Noise Rati UPF 5G User Plane Function X2 Interface between two eNBs, or between eNB and an EN-DC capable gNB. Xn Interface between two gNBs, or between gNB and (NG)EN-DC or NR E-UTRAN DC capable eNB. XnAP Xn Application Protocol UE User Equipment

Claims

CLAIMS 1. A method performed by a first network node, the method comprising: providing (702) a user equipment with a configuration for performance of inter-frequency measurements without a measurement gap; and transmitting (704), to a second network node, an indication of the configuration for performance of inter-frequency measurements without a measurement gap.
2. The method according to claim 1, wherein the first and second network nodes are radio access network nodes.
3. The method according to claim 1 or 2, wherein the indication of the configuration is transmitted to the second network node over a direct interface between the first network node and the second network node.
4. The method according to any one of the preceding claims, wherein the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration, and wherein the first network node is a master node and the second network node is a secondary node.
5. The method according to claim 4, wherein the indication of the configuration is transmitted in an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message.
6. The method according to claim 4 or 5, wherein the indication of the configuration is provided in a CG-ConfigInfo container.
7. The method according to any one of claims 4 to 6, wherein the second network node comprises a centralized unit and a distributed unit, and wherein the indication of the configuration is transmitted to the centralized unit to be forwarded to the distributed unit.
8. A method performed by a second network node, the method comprising: receiving (802), from a first network node, an indication of a configuration provided to a user equipment for performance of inter-frequency measurements without a measurement gap; and adaptively scheduling (804) the user equipment for transmission or reception using one or more bandwidth parts based on the configuration.
9. The method according to claim 8, wherein the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration, and wherein the first network node is a master node and the second network node is a secondary node.
10. The method according to claim 8 or 9, wherein adaptively scheduling the user equipment comprises scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
11. The method according to claim 8 or 9, wherein adaptively scheduling the user equipment comprises preferentially scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
12. The method according to claim 11, wherein preferentially scheduling the user equipment with an active bandwidth part comprises scheduling the user equipment with the active bandwidth part more often, or with higher priority than other bandwidth parts.
13. A first network node (1600) adapted to: provide a user equipment with a configuration for performance of inter- frequency measurements without a measurement gap; and transmit, to a second network node, an indication of the configuration for performance of inter-frequency measurements without a measurement gap.
14. The first network node according to claim 13, wherein the first network node is further adapted to perform the method according to any one of claims 2 to 7.
15. A second network node (1600) adapted to: receive, from a first network node, an indication of a configuration provided to a user equipment for performance of inter-frequency measurements without a measurement gap; and adaptively schedule the user equipment for transmission or reception using one or more bandwidth parts based on the configuration.
16. The second network node according to claim 15, wherein the second network node is further adapted to perform the method according to any one of claims 9 to 12.
17. A first network node (1600) comprising: processing circuitry (1602) configured to cause the first network node to: provide a user equipment with a configuration for performance of inter- frequency measurements without a measurement gap; and transmit, to a second network node, an indication of the configuration for performance of inter-frequency measurements without a measurement gap.
18. The first network node according to claim 17, wherein the first and second network nodes are radio access network nodes.
19. The first network node according to claim 17 or 18, wherein the indication of the configuration is transmitted to the second network node over a direct interface between the first network node and the second network node.
20. The first network node according to any one of claims 17 to 19, wherein the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration, and wherein the first network node is a master node and the second network node is a secondary node.
21. The first network node according to claim 20, wherein the indication of the configuration is transmitted in an S-NODE ADDITION REQUEST message or an S- NODE MODIFICATION REQUEST message.
22. The first network node according to claim 20 or 21, wherein the indication of the configuration is provided in a CG-ConfigInfo container.
23. The first network node according to any one of claims 20 to 22, wherein the second network node comprises a centralized unit and a distributed unit, and wherein the indication of the configuration is transmitted to the centralized unit to be forwarded to the distributed unit.
24. A second network node (1600) comprising: processing circuitry (1602) configured to cause the second network node to: receive, from a first network node, an indication of a configuration provided to a user equipment for performance of inter-frequency measurements without a measurement gap; and adaptively schedule the user equipment for transmission or reception using one or more bandwidth parts based on the configuration.
25. The second network node according to claim 24, wherein the first and second network nodes provide service to the user equipment as part of a dual- or multi-connectivity configuration, and wherein the first network node is a master node and the second network node is a secondary node.
26. The second network node according to claim 24 or 25, wherein adaptively scheduling the user equipment comprises scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
27. The second network node according to claim 24 or 25, wherein adaptively scheduling the user equipment comprises preferentially scheduling the user equipment with an active bandwidth part which encompasses one or more frequencies or frequency ranges on which the user equipment is configured to perform inter-frequency measurements without a measurement gap.
28. The second network node according to claim 27, wherein preferentially scheduling the user equipment with an active bandwidth part comprises scheduling the user equipment with the active bandwidth part more often, or with higher priority than other bandwidth parts.
29. A computer program comprising instructions which, when executed by processing circuitry of a first network node, cause the first network node to perform the method according to any one of claims 1 to 7.
30. A non-transitory computer-readable medium storing the computer program according to claim 29.
31. A computer program comprising instructions which, when executed by processing circuitry of a second network node, cause the second network node to perform the method according to any one of claims 8 to 12.
32. A non-transitory computer-readable medium storing the computer program according to claim 31.
PCT/SE2023/050283 2022-05-10 2023-03-29 Measurement configuration in wireless networks WO2023219542A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263340196P 2022-05-10 2022-05-10
US63/340,196 2022-05-10

Publications (1)

Publication Number Publication Date
WO2023219542A1 true WO2023219542A1 (en) 2023-11-16

Family

ID=85937060

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050283 WO2023219542A1 (en) 2022-05-10 2023-03-29 Measurement configuration in wireless networks

Country Status (1)

Country Link
WO (1) WO2023219542A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190222478A1 (en) * 2014-04-30 2019-07-18 Lg Electronics Inc. Method and apparatus for configuring measurement gap in wireless communication system
US20210144658A1 (en) * 2018-04-13 2021-05-13 Zte Corporation Measurement gap configuration method and device, storage medium, and electronic device
WO2021206929A1 (en) * 2020-04-06 2021-10-14 Google Llc Managing measurement gap configurations

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190222478A1 (en) * 2014-04-30 2019-07-18 Lg Electronics Inc. Method and apparatus for configuring measurement gap in wireless communication system
US20210144658A1 (en) * 2018-04-13 2021-05-13 Zte Corporation Measurement gap configuration method and device, storage medium, and electronic device
WO2021206929A1 (en) * 2020-04-06 2021-10-14 Google Llc Managing measurement gap configurations

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
3GPP TS 37.340
3GPP TS 38.133
3GPP TS 38.300
3GPP TS 38.331
3GPP TS 38.401
3GPP TS 38.473
BT PLC ET AL: "On inter-frequency measurement configuration and reporting enhancements", vol. RAN WG2, no. e meeting; 20220509 - 20220520, 25 April 2022 (2022-04-25), XP052139242, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_118-e/Docs/R2-2205832.zip R2-2205832 - Configuration of chronological order for performing inter-frequency measurements.docx> [retrieved on 20220425] *

Similar Documents

Publication Publication Date Title
WO2023113674A1 (en) User equipment (ue) operation with base station energy-saving configuration
WO2023022642A1 (en) Reporting of predicted ue overheating
WO2023219542A1 (en) Measurement configuration in wireless networks
WO2023207433A1 (en) Methods and apparatuses for communication in wireless communication system with network power saving feature
WO2023068983A1 (en) Measurement reporting based on measurement configurations using frequency specific priority indications
WO2024035309A1 (en) Methods, apparatus and computer-readable medium related to conditional cell change
WO2024033808A1 (en) Csi measurements for inter-cell mobility
WO2023152043A1 (en) Efficient inter-cell l1-rsrp measurement and reporting
WO2022240334A1 (en) Conditional reconfigurations of cells in secondary cell groups
WO2024035293A1 (en) User equipment (ue) selection of candidate cells to be measured for l1/l2 inter-cell mobility
WO2023152683A1 (en) Secondary node initiated conditional pscell change
WO2023075672A1 (en) Methods and systems for indicating measured frequencies in a measurement report
EP4356683A1 (en) Methods and network nodes for suspend-resume for l1/l2 centric inter-cell mobility configuration(s)
WO2024052852A1 (en) Handling of multiple frequency granularities for idc
WO2022238896A1 (en) Handling of rejection of candidate target cells for conditional pscell change
WO2022243850A1 (en) L1/l2 centric mobility via lightweight reconfiguration with sync
WO2023073677A2 (en) Measurements in a communication network
WO2023059238A1 (en) Calculating communication device mobility state using reference frequency
WO2023146453A1 (en) Ue logging and reporting of hsdn properties
WO2023284935A1 (en) Secondary node requested measurement gaps at secondary node addition
WO2023062509A1 (en) Temporary reference signal-based secondary cell activation via radio resource control
WO2024035305A1 (en) Successful pscell change or addition report
WO2023121520A1 (en) Method and apparatuses for three cell group multi-connectivity using two uplink data split thresholds
WO2022234537A1 (en) L1/l2 centric mobility for scell(s)
WO2023136764A1 (en) Methods for handling logging of different types of measurements in son reports

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23715617

Country of ref document: EP

Kind code of ref document: A1