A method for generating pre-configured gaps for different BWP configurations in RedCap UE.

Abstract

Various embodiments disclosed herein provide a method for a central unit (gNB-CU) to provide and configure measurement gaps (MGs) for multiple bandwidth portions (BWPs) selected by a distributed unit (gNB-DU) for configuring a user equipment device (UE), thereby avoiding the gNB sending multiple radio resource configuration (RRC) reconfiguration messages to the UE via downlink control information (DCI) based BWP switching. The gNB-DU can select multiple BWPs for the UE, the gNB-DU can notify the gNB-CU about the multiple BWPs, the gNB-CU can decide whether to configure a pre-configured MG for the currently inactive BWP and notify the gNB-DU of the selection of the inactive BWP. The gNB-DU can then generate different pre-configured MGs and notify the gNB-CU of the pre-configured MGs, the gNB-CU can then configure the UE with the pre-configured MGs via RRCReconfiguration.

Description

Technical Field

[0001] This application claims the benefit of International Patent Application No. PCT / CN2023 / 078039, filed on February 24, 2023, the disclosure of which is hereby incorporated by reference in its entirety.

[0002] This disclosure relates to a method for generating preconfigured measurement gaps for different configured bandwidth parts for a low power consumption (RedCap) user equipment device (UE) in a wireless communication system.

Background Art

[0003] NG-RAN Architecture The overall architecture of the 5th generation (5G) radio access network (RAN) is shown in FIG. 1, and the core network 102 of the wireless communication system can communicate with a next-generation radio access network (NG-RAN) 104 including various base stations or gNBs 106 that may each include a core unit or central unit (gNB-CU) 108 and a distributed unit (gNB-DU) 110. A gNB 106 with a split architecture is shown in FIG. 2. · gNB-CU 108 (e.g., gNB-CU 108-1 and gNB-CU 108-2) hosts the control plane parts of RRC and PDCP, and gNB-DU 110 (or gNB-DU 110-1 and gNB-DU 110-2) hosts radio link control (RLC), media access control (MAC), and the physical layer. · In the split gNB architecture, the F1 UE context management function supports the establishment and change of the entire necessary UE context. · The establishment of the F1 UE context is initiated by the gNB-CU 108 and is accepted or rejected by the gNB-DU 110 based on admission control criteria (e.g., resources are not available). • Changes to the F1 UE context can be initiated by either the gNB-CU108 or the gNB-DU110. The receiving node can accept or reject the change. The F1 UE context management function also supports the release of previously established contexts in the gNB-DU110.

[0004] RedCap RedCap (low-power) user equipment (UE) is a low-power UE as defined in Section 4.2.21.1 of TS38.306. It was introduced by the Third Generation Partnership Project (3GPP) in Release 17 with the intention of being less complex than non-RedCap UEs. RedCap UEs are required to support a maximum UE channel bandwidth of 20 MHz in FR1 and a maximum UE channel bandwidth of 100 MHz in FR2.

[0005] In Rel-17, RAN2 introduced a non-cell-defined synchronization signal block (NCD-SSB) specifically for Redcap UEs. A single bandwidth portion (BWP) can have at most one SSB (CD-SSB or NCD-SSB). A BWP with an NCD-SSB is at a different frequency than a cell-defined SSB (CD-SSB). A RedCap UE can consist of multiple NCD-SSBs, provided each BWP consists of at most one SSB. An NCD-SSB may be configured for a RedCap UE in RRC_CONNECTED to perform Radio Resource Management (RRM) measurements when the active BWP does not contain a CD-SSB.

[0006] For BWP configuration and activation, the gNB notifies the RedCap UE of its active BWP via Radio Resource Control (RRC) messages or Downlink Control Information (DCI). If a BWP configuration (sent via RRC msg) includes NCD-SSB and the servingCellMO-r17 IE within BWP-DownlinkDedicated IE (see excerpt from TS38.331 below) appears within this BWP configuration, then when this BWP becomes the active BWP for a RedCap UE, the UE will use servingCellMO-r17 within this BWP configuration as the current serving cell measurement target. • If the BWP configuration (sent via RRC msg) does not include servingCellMO-r17 IE, when this BWP becomes the active BWP for a RedCap UE, the UE will use the servingCellMO IE from the ServingCellConfig IE as its current serving cell metric.

[0007] ****Excerpt from TS38.331 begins**** BWP-DownlinkDedicated IE -> servingCellMO-r17: The servingCellMO measObjectId of the MeasObjectNR in the MeasConfig associated with the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and the nonCellDefiningSSB in the BWP-DownlinkDedicated of the associated downlink BWP: if ssbFrequency is set, its value is the same as absoluteFrequencySSB in nonCellDefiningSSB. If the field exists in the downlink BWP and the BWP is activated, the RedCap UE uses this measure for serving cell measurement; otherwise, the RedCap UE uses servingCellMO in the ServingCellConfig IE. ****End of TS38.331 excerpt****

[0008] In an NG-RAN separation architecture, the CU is the entity that determines whether the measured frequency of the UE corresponds to an in-frequency or inter-frequency adjacent cell, and therefore whether a measurement gap needs to be performed to reduce the UE's throughput.

[0009] It was previously proposed that the gNB-CU send an F1 message to the gNB-DU to set up / modify the UE context, containing a list of measObjectIds for NCD-SSBs that have SSB frequency information in this cell. The gNB-DU then uses this information to encode the measObject IDs used for BWP configuration in the appropriate place within the Cell Group Configuration (CGC) in the RRC message. If the active BWP of a RedCap UE is later changed via DCI, the gNB-DU notifies the gNB-CU with an F1AP message, and as a result, the gNB-CU updates the UE's neighbor cell measurements based on this new servingCellMO (e.g., selecting different SSBs to measure in neighboring cells).

[0010] Currently, several challenges exist. In DCI-based BWP switching scenarios, the possible introduction and use of preConfGapStatus-r17 in the BWP-DownlinkDedicated IE during RRC (see excerpt from TS38.331 below) allows the UE to autonomously know which measurement gap (MG) to apply after the active BWP associated with the NCD-SSB has been changed via DCI. However, it is unclear how both the gNB-CU and gNB-DU can know the different pre-configured MGs for all BWPs used by the UE, so that the gNB-CU can prepare RRC messages to the UE. The following configuration options are available in RRC per BWP Config:

[0011] ****Excerpt from TS38.331 begins**** BWP-DownlinkDedicated IE -> preConfGapStatus-r17: preConfGapStatus indicates whether a pre-configured measurement gap (i.e., the gap configured in preConfigInd) will be activated or deactivated when switching to this BWP. If this field is set, the UE shall apply a network control mechanism for activating and deactivating pre-configured measurement gaps; otherwise, the UE shall apply an autonomous activation / deactivation mechanism as specified in TS38.133

[14] . The first / leftmost bit corresponds to the measurement gap of gap ID 1, the second bit corresponds to the measurement gap of gap ID 2, and so on. A value of 0 indicates that the corresponding pre-configured measurement gap will be deactivated, while a value of 1 indicates that the corresponding pre-configured measurement gap will be activated. The UE shall ignore the bit if the corresponding measurement gap is not a pre-configured measurement gap. ****End of TS38.331 excerpt****

[0012] Furthermore, TS38.133 h60 contains the following statement:

[0013] ****Excerpt from TS38.331 begins**** If the UE indicates support only for preconfiguredNW-ControlledMeasGap, the UE can anticipate that the network will be configured as such. 9.1.7 Pre-configured measurement gap 9.1.7.1 Introduction UEs capable of pre-configured measurement gap (Pre-MG) patterns can be configured with the Pre-MG pattern via RRC signaling [2]. The gap interruption requirements in Section 9.1.2 apply to Pre-MG when it is activated, and no gap interruption is expected when Pre-MG is deactivated. The requirements apply to single-carrier and NR standalone operation using NR CA.

[0014] 9.1.7.2 Applicability of Requirements The requirements regarding pre-set measurement gaps apply, subject to the following conditions: - The UE indicates support for preconfiguredUE-AutonomousMeasGap[2] and / or preconfiguredNW-ControlledMeasGap[2]. - A measurement gap for each single UE is pre-configured by the network, or one or two measurement gaps for each FR are pre-configured by the network. - For the pre-configured measurement gap, one of the measurement gap patterns #0 to #25 will be set. - The UE is in an NR SA with a single carrier or an NR CA. The measurement gap is set as a pre-configured measurement gap if preConfigInd is indicated by the network in the measurement gap configuration message. If the UE indicates support only for NW-Controlled MeasGap[2], the UE can anticipate that the network will have a RAN2 signaling design for per-BWP status indication.

[0015] Editor's note: The current RAN2 specification does not include explicit signaling from the network to indicate which activation / deactivation mechanism is selected by the network. RAN2 may address this issue later. ****End of TS38.331 excerpt****

[0016] 38.331 h20 6.3.3 In the UE power consumption information element: MeasAndMobParametersCommon ::= SEQUENCE { ... -- R4 19-3-2 Pre-set measurement gap preconfiguredUE - AutonomousMeasGap - r17 Enumeration {supported} OPTIONAL, -- R4 19 - 3 - 1 Pre - configured Measurement Gap preconfiguredNW - ControlledMeasGap - r17 Enumeration {supported} OPTIONAL, ··· } and in 38.306 h20 4.2.9 TIFF2026509736000002.tif78170

[0017] Some aspects of the present disclosure and their embodiments may provide solutions to these or other problems.

Summary of the Invention

[0018] Various embodiments disclosed herein provide a method for a central unit (gNB - CU, or CU) to provide and configure measurement gaps (MGs) for a plurality of bandwidth parts (BWPs) selected by a distributed unit (e.g., gNB - DU or DU) for the configuration of a user equipment device (UE), and for the gNB to avoid transmitting a plurality of radio resource configuration (RRC) re - configuration messages by downlink control information (DCI) - based BWP switching to the UE. The gNB - DU can select a plurality of BWPs for the UE, the gNB - DU can notify the gNB - CU about the plurality of BWPs, the gNB - CU can determine whether to set pre - configured MGs for the currently non - active BWPs, and can notify the gNB - DU of the selection of the non - active BWPs. The gNB - DU can then generate different pre - configured MGs and notify the gNB - CU of the pre - configured MGs, and the gNB - CU can then configure the UE with the pre - configured MGs via RRCReconfiguration.

[0019] In one embodiment, a method is provided, performed by a first network node, for generating pre-configured measurement gaps for a plurality of BWPs for a UE. The method includes providing a second network node with a list of configured BWPs associated with the UE. The method also includes receiving a request from the second network node to generate pre-configured measurement gaps associated with selected BWPs from the list of configured BWPs, and providing the second network node with information identifying the pre-configured measurement gaps associated with the selected BWPs.

[0020] In one embodiment, providing a list of configured BWPs associated with the UE is done in a UE context change response message in response to receiving a UE context change request message.

[0021] In one embodiment, providing a list of configured BWPs associated with the UE is done in a UE context setup response message in response to receiving a UE context setup request message.

[0022] In one embodiment, the list of configured BWPs associated with the UE further includes at least one of the serving cells or BWP locations associated with each BWP in the list of configured BWPs.

[0023] In one embodiment, providing information identifying a pre-configured measurement gap associated with a selected BWP is done in response to a first network node that supports switching of the active BWP via downlink control information.

[0024] In one embodiment, a request to generate a pre-configured measurement gap associated with a selected BWP includes a list of frequencies to which a second network node requests the first network node to generate a pre-configured measurement gap.

[0025] In one embodiment, information identifying a pre-configured measurement gap is included in a separate UE context change response message, which also includes an updated CellGroupConfig information element.

[0026] In one embodiment, the first network node is a DU network node, and the second network node is a CU network node.

[0027] In one embodiment, a first network node can be provided that generates pre-configured measurement gaps for a plurality of BWPs for a UE, the first network node comprising processing circuitry for performing the operation. This operation may include providing a second network node with a list of configured BWPs associated with the UE. This operation may also include receiving a request from the second network node to generate pre-configured measurement gaps associated with selected BWPs from the list of configured BWPs, and providing the second network node with information identifying the pre-configured measurement gaps associated with the selected BWPs.

[0028] In one embodiment, one method may be performed by a second network node requesting pre-configured measurement gaps for a plurality of BWPs for a UE. This method may include receiving a list of configured inactive BWPs associated with the UE from a first network node. This method may also include deciding to request pre-configured measurement gaps for one or more inactive BWPs from the list of configured inactive BWPs. This method may also include providing a request to the first network node to generate pre-configured measurement gaps associated with one or more inactive BWPs from the list of configured inactive BWPs. This method may also include receiving information from the first network node that identifies the pre-configured measurement gaps associated with the selected BWPs.

[0029] In one embodiment, receiving a list of configured BWPs associated with the UE is done in a UE context change response message in response to providing a UE context change request message to a first network node.

[0030] In one embodiment, receiving a list of configured BWPs associated with the UE is done in a UE context setup response message in response to providing a UE context setup request message to a first network node.

[0031] In one embodiment, the list of configured BWPs associated with the UE further includes at least one of the serving cells or BWP locations associated with each BWP in the list of configured BWPs.

[0032] In one embodiment, receiving information identifying a pre-configured measurement gap associated with a selected BWP is done in response to a first network node that supports the switching of the active BWP via downlink control information.

[0033] In one embodiment, a request to generate a pre-configured measurement gap associated with a selected BWP includes a list of frequencies to which a second network node requests the first network node to generate a pre-configured measurement gap.

[0034] In one embodiment, information identifying a pre-configured measurement gap is included in a separate UE context change response message, which also includes an updated CellGroupConfig information element.

[0035] In one embodiment, the first network node is a DU network node, and the second network node is a CU network node.

[0036] In one embodiment, a second network node is provided that requests pre-configured measurement gaps for a plurality of BWPs for the UE. The second network node may include processing circuitry for performing an operation which may include receiving a list of configured inactive BWPs associated with the UE from the first network node. This operation may include deciding to request pre-configured measurement gaps for one or more inactive BWPs from the list of configured inactive BWPs. This operation may include providing the first network node with a request to generate pre-configured measurement gaps associated with one or more inactive BWPs from the list of configured inactive BWPs. This operation may also include receiving information from the first network node that identifies the pre-configured measurement gaps associated with the selected BWPs.

[0037] Some embodiments may offer one or more of the following technical advantages:

[0038] This disclosure enables the CU to provide all the necessary MGs for multiple BWPs selected by the DU for UE configuration, and avoids the gNB sending multiple RRC reconfiguration messages due to DCI-based BWP switching for UEs that consume many Uu resources.

[0039] In fact, by pre-configuring multiple measurement gaps (covering all possible gaps considering a list of BWPs that may be actively configured via DCI at some point), the CU can provide pre-configurations via RRC signaling so that the UE knows which gap to apply when the active BWP is switched via DCI, without requiring RRC reconfiguration from the CU.

[0040] The accompanying drawings incorporated herein and forming part of herein illustrate several aspects of this disclosure and, together with the description, are useful in illustrating the principles of this disclosure. [Brief explanation of the drawing]

[0041] [Figure 1] This diagram shows the overall architecture of the fifth-generation (5G) radio access network (RAN). [Figure 2] This diagram shows a 5G RAN-separated architecture. [Figure 3] This is a message sequence chart between a distributed unit and a core unit for setting pre-configured measurement gaps for multiple bandwidth portions (BWPs) for a user equipment device (UE). [Figure 4] This figure shows examples of communication systems according to some embodiments of the present disclosure. [Figure 5] This figure shows a UE according to some embodiments of the present disclosure. [Figure 6] This figure shows network nodes according to some embodiments of the present disclosure. [Figure 7]This is a block diagram of a host that may be one embodiment of the host shown in Figure 4, according to various aspects of the present disclosure described herein. [Figure 8] This block diagram shows a virtualization environment in which the functions implemented by some embodiments of this disclosure can be virtualized. [Modes for carrying out the invention]

[0042] The embodiments described below are intended to provide information that will enable those skilled in the art to implement the embodiments and to represent the best mode of implementation. By reading the following description in reference to the accompanying figures, those skilled in the art will understand the concepts of this disclosure and recognize examples of applications of these concepts that are not specifically addressed herein. It should be understood that these concepts and examples of applications fall within the scope of this disclosure.

[0043] Next, some embodiments intended herein will be described in more detail with reference to the accompanying drawings. Embodiments are provided as examples to convey the scope of the subject to those skilled in the art.

[0044] Various embodiments disclosed herein provide a method for a central unit (gNB-CU) to provide and configure measurement gaps (MGs) for multiple bandwidth portions (BWPs) selected by a distributed unit (gNB-DU) for configuring a user equipment device (UE), thereby avoiding the gNB sending multiple radio resource configuration (RRC) reconfiguration messages to the UE via downlink control information (DCI) based BWP switching. The gNB-DU can select multiple BWPs for the UE, the gNB-DU can notify the gNB-CU about the multiple BWPs, the gNB-CU can decide whether to configure a pre-configured MG for the currently inactive BWP and notify the gNB-DU of the selection of the inactive BWP. The gNB-DU can then generate different pre-configured MGs and notify the gNB-CU of the pre-configured MGs, the gNB-CU can then configure the UE with the pre-configured MGs via RRCReconfiguration.

[0045] If the gNB-DU selects multiple BWPs for the UE (i.e., the BWPs are encoded in CellGroupConfig) and the DU can later ask the UE to change the active BWP via DCI, then several new information elements (IEs) proposed in the following chapters should be provided from the gNB-DU to the gNB-CU in the UE context setup response / UE context change response.

[0046] After receiving the above response, if the gNB-CU decides to set a pre-configured measurement gap for the currently inactive BWP, the gNB-CU should send a UE context change request to the DU, along with several new information elements (IEs) proposed in the following chapters.

[0047] After receiving the above response, if gNB-CU also determines that a measurement gap is needed for the UE's currently active BWP in the same UE context change request, gNB-CU can still ask gNB-DU to generate it in the legacy F1 IE.

[0048] This proposed method allows the gNB-CU to set only a pre-configured measurement gap for the UE's current active BWP, without using legacy IE (in the UE context change request) to ask the gNB-DU to generate a measurement gap for the UE's current active BWP.

[0049] Upon receiving the above UE context change request message with a pre-configured measurement gap generation request, gNB-DU generates different pre-configured measurement gaps for BWPs in CellGroupConfig in the BWP-change-via-DCI scenario.

[0050] If successful, the gNB-DU sends a UE context change response message to the gNB-CU, along with the updated CellGroupConfig and measurement gap settings. This allows the CU to send all MGs to the UE in a single RRC reconfiguration message.

[0051] This disclosure adds a new F1AP function that allows the DU to notify the CU of a list of configured BWP information.

[0052] This disclosure adds a new FAP (Functional Action Program) feature that, based on information previously received from the DU, allows the CU to notify the DU of a BWP change scenario via DCI, generating different pre-configured measurement gaps for all configured BWPs within the CGC.

[0053] This disclosure adds a new RRC (Rapid Relay Control) feature to supported network controls' meas preconfigured GAPs, which allows the CU (Control Unit) to notify the UE (User Environment Engine) of a list of preconfigured Meas GAPs based on DU (Digital Unit) scheduling.

[0054] Some embodiments may offer one or more of the following technical advantages:

[0055] This disclosure enables the CU to provide all the necessary MGs for multiple BWPs selected by the DU for UE configuration, and avoids the gNB sending multiple RRC reconfiguration messages due to DCI-based BWP switching for UEs that consume many Uu resources.

[0056] In fact, by pre-configuring multiple measurement gaps (covering all possible gaps considering a list of BWPs that may be actively configured via DCI at some point), the CU can provide pre-configurations via RRC signaling so that the UE knows which gap to apply when the active BWP is switched via DCI, without requiring RRC reconfiguration from the CU.

[0057] BWP information elements -- ASN1START -- TAG-BWP-START BWP ::= SEQUENCE { locationAndBandwidth integer type (0..37949), subcarrierSpacing SubcarrierSpacing, cyclicPrefix enumeration {extended } OPTIONAL -- Need R } -- TAG-BWP-STOP -- ASN1STOP

[0058] Description of the BWP field CyclicPrefix (CP): Indicates whether to use an extended cyclic prefix for this bandwidth portion. If not set, the UE uses a normal cyclic prefix. Normal CP is supported for all subcarrier intervals and slot formats. Extended CP is supported only for 60 kHz subcarrier intervals. (See TS38.211

[16] , Section 4.2). Except for SUL, the network ensures that the same cyclic prefix length is used for active downlink (DL) BWPs and active uplink (UL) BWPs within a serving cell.

[0059] LocationAndBandwidth: The frequency domain location and bandwidth of this bandwidth portion. The value of the field is based on the assumptions described in TS38.213

[13] , Section 12, i.e., the settings. TIFF2026509736000003.tif9170=275 shall be interpreted as a resource indicator value (RIV) as defined in TS38.214

[19] . The first physical resource block (PRB) is determined by the subcarrierSpacing of this BWP and the offsetToCarrier corresponding to this subcarrier spacing (set in the SCS-SpecificCarrier contained within FrequencyInfoDL / FrequencyInfoUL / FrequencyInfoUL-SIB / FrequencyInfoDL-SIB within ServingCellConfigCommon / ServingCellConfigCommonSIB). In the case of time-division duplexing (TDD), BWP pairs (UL BWP and DL BWP having the same bwp-Id) must have the same center frequency (see TS38.213

[13] , Section 12).

[0060] Unless explicitly set elsewhere, the subcarrier spacing to be used in this BWP for all channels and reference signals corresponds to the subcarrier spacing given in TS38.211

[16] , Table 4.2-1. A value of 15 kHz corresponds to μ=0, a value of 30 kHz corresponds to μ=1, and so on.

[0061] Depending on the frequency used, only the following values ​​are applicable. • FR1: 15, 30, or 60 kHz • FR2-1: 60 or 120 kHz • FR2-2: 120, 480, or 960 kHz

[0062] In operation with the initial DL BWP and authorization spectrum, this field has the same value as the subCarrierSpacingCommon field in the MIB of the same serving cell. Except for SUL, the network ensures that the same subcarrier spacing is used for active DL BWPs and active UL BWPs within a serving cell. In operation with the initial DL BWP and shared spectral channel access, the value of this field corresponds to the subcarrier spacing of the SSB associated with the initial DL BWP.

[0063] Figure 3 shows a message sequence chart between the distributed unit 110 and the core unit 108 for setting pre-configured measurement gaps for multiple bandwidth portion BWPs for UE302. Optional steps in the message sequence chart are represented by dashed lines.

[0064] In step 304, CU108 may send a UE context setup / change request to DU110. This message may include, for example, a list of non-cell-defined synchronization signal block (NCD-SSB) measurement information. If the UE context is successfully established, gNB-DU responds to gNB-CU with a UE context setup response. If no logical F1 connection associated with the UE exists, a logical F1 connection associated with the UE shall be established as part of the procedure. gNB-CU shall perform radio resource configuration (RRC) reconfiguration or RRC connection reactivation as described in TS38.331[8]. CellGroupConfig IE shall be signaled transparently to the UE as specified in TS38.331[8].

[0065] If the UE-CapabilityRAT-ContainerList IE is included in the UE context setup request, the gNB-DU shall take this information into consideration for UE-specific configuration.

[0066] If the servingCellMO IE is included in the UE context setup request message, the gNB-DU shall set the servingCellMO of the indicated SpCell accordingly.

[0067] If a servingCellMO list IE is included in the UE context setup request message, the gNB-DU shall select a servingCellMO after determining the list of BWPs for the UE and include the used servingCellMO as the used servingCellMO list IE in the UE context setup response message.

[0068] If the active BWP location and bandwidth IE are included in the UE context setup response message, the gNB-CU assumes, if supported, that the UE's currently used servingCellMO points to an SSB outside the UE's active BWP.

[0069] If the DU configures multiple BWPs for the UE (in 306) (in CellGroupConfig) and the DU supports active BWP switching via DCI, then in step 308, the configured current inactive BWP list IE is included in the UE context setup response message. When the current inactive BWP list IE is included in the UE context setup response message, the gNB-CU shall take this into account when requesting the DU to generate a pre-configured MG for the indicated BWP / BWPSID, if supported.

[0070] When the message in step 304 is a UE context change request message, upon receiving the UE context change request message, the gNB-DU shall perform the change in step 306, and if successful, report the update in a UE context change response message in step 308.

[0071] If the SpCell ID IE is included in the UE context change request message, the gNB-DU shall replace any previously received value and consider it a synchronized reconfiguration as defined in TS38.331[8]. If the ServCellIndex IE is included in the UE context change request message, the gNB-DU shall take this into consideration for the indicated SpCell. If the UE context change request message includes the IE of a UL-configured SpCell, the gNB-DU shall configure the UL for the indicated SpCell accordingly. If the servingCellMO IE is included in the UE context change request message, the gNB-DU shall configure the servingCellMO for the indicated SpCell accordingly. If the servingCellMO list IE is included in the UE context setup change request message, the gNB-DU shall configure the servingCellMO after determining the list of BWPs for the UE and include the used servingCellMO as the used servingCellMO list IE in the UE context change response message. If the active BWP location and bandwidth IE are included in the UE context change response message, the gNB-CU shall, if supported, decide in step 312 to ask the gNB-DU110 to generate a pre-configured MG for the selected configured BWP.

[0072] When the currently inactive BWP list IE is included in the UE context change response message, the gNB-CU shall take this into consideration when requesting the DU to generate a pre-configured MG for the BWP / BWP ID shown in step 314, if supported.

[0073] In step 314, if a pre-configured measurement gap information list IE exists in the UE context change request message (in the RRC information IE from CU to DU), the DU shall generate different pre-configured measurement gaps for the BWP. If the gNB-DU successfully generates different pre-configured measurement gaps for the BWP, the gNB-DU shall update the CellGroupConfig and pre-configured measurement gap settings in the UE context change response message in step 316.

[0074] In step 318, the gNB-CU108 can then configure the UE302 with a pre-configured MG.

[0075] If a list of SCells to be set up IE is included in the UE context change request message, gNB-DU shall consider it as a list of candidate SCells to be set up. If a list of SCells to be set up IE is included in the UE context change request message and the indicated SCell is already set up, gNB-DU shall replace any previously received values. If a UL-configured SCell IE is included in the UE context change request message, gNB-DU shall configure the UL for the indicated SpCell accordingly. If a servingCellMO IE is included in the UE context change request message, gNB-DU shall configure the servingCellMO for the indicated SCell accordingly.

[0076] The following is an example of an implementation of the above embodiment for TS38.473, with new changes underlined.

[0077] <Changes begin> 8.3.1 UE Context Setup 8.3.1.1 General The purpose of the UE context setup procedure is to establish a UE context that includes, among other things, SRB, DRB, BH RLC channel, Uu relay RLC channel, PC5 relay RLC channel, and SL DRB configuration. This procedure uses the signaling associated with the UE.

[0078] 8.3.1.2 Successful Operation The gNB-CU initiates the procedure by sending a UE context setup request message to the gNB-DU. If the UE context is successfully established, the gNB-DU responds to the gNB-CU with a UE context setup response. If no logical F1 connection associated with the UE exists, a logical F1 connection associated with the UE shall be established as part of the procedure. The gNB-CU shall perform RRC reconfiguration or RRC connection reactivation as described in TS38.331[8]. The CellGroupConfig IE shall be signaled transparently to the UE as specified in TS38.331[8]. If the UE-CapabilityRAT-ContainerList IE is included in the UE context setup request, the gNB-DU shall take this information into consideration for UE-specific configuration. If the servingCellMO IE is included in the UE context setup request message, the gNB-DU shall set the servingCellMO of the indicated SpCell accordingly. If a servingCellMO list IE is included in the UE context setup request message, the gNB-DU shall select a servingCellMO after determining the list of BWPs for the UE and include the used servingCellMO as the used servingCellMO list IE in the UE context setup response message. If the active BWP location and bandwidth IE are included in the UE context setup response message, the gNB-CU assumes, if supported, that the UE's currently used serving cell MO points to an SSB outside the UE's active BWP.

[0079] If the DU configures multiple BWPs for the UE (in CellGroupConfig) and the DU supports active BWP switching via DCI, the configured current inactive BWP list IE is included in the UE context setup response message. When the current inactive BWP list IE is included in the UE context setup response message, the gNB-CU shall take this into account when requesting the DU to generate a pre-configured MG for the indicated BWP / BWPSID, if supported.

[0080] <Next changes> 8.3.4 UE Context Change (gNB-CU Start) 8.3.4.1 General The purpose of the UE context modification procedure is to modify an established UE context, for example, to establish, modify, and release radio or sidelink resources. This procedure is also used to instruct the gNB-DU to stop transmitting data to the UE for movement (see TS38.401[4]). This procedure uses the signaling associated with the UE.

[0081] 8.3.4.2 Successful Operation The UE context change request message is initiated by the gNB-CU. Upon receiving a UE context change request message, gNB-DU shall execute the change and, if successful, report the update in a UE context change response message. If the SpCell ID IE is included in the UE context change request message, the gNB-DU shall replace any previously received value and consider it a reconfiguration with synchronization as defined in TS38.331[8]. If the ServCellIndex IE is included in the UE context change request message, the gNB-DU shall take this into consideration for the indicated SpCell. If the UE context change request message includes the IE of a UL-configured SpCell, the gNB-DU shall configure the UL for the indicated SpCell accordingly. If the servingCellMO IE is included in the UE context change request message, the gNB-DU shall configure the servingCellMO for the indicated SpCell accordingly. If the servingCellMO list IE is included in the UE context setup change request message, the gNB-DU shall configure the servingCellMO after determining the list of BWPs for the UE and include the used servingCellMO as the used servingCellMO list IE in the UE context change response message. If the active BWP location and bandwidth IE are included in the UE context change response message, the gNB-CU assumes, if supported, that the UE's currently used serving cell MO points to an SSB outside the UE's active BWP. When the currently inactive BWP list IE is included in the UE context change response message, the gNB-CU shall take this into consideration when requesting the DU to generate a pre-configured MG for the indicated BWP / BWPSID, if supported. If a pre-configured measurement gap information list IE exists in the UE context change request message (in the RRC information IE from CU to DU), the DU shall generate different pre-configured measurement gaps for the BWP. If the gNB-DU successfully generates different pre-configured measurement gaps for the BWP, the gNB-DU shall update the CellGroupConfig and pre-configured measurement gap settings in the UE context change response message. If a list of SCells to be set up IE is included in the UE context change request message, gNB-DU shall consider it as a list of candidate SCells to be set up. If a list of SCells to be set up IE is included in the UE context change request message and the indicated SCell is already set up, gNB-DU shall replace any previously received values. If a UL-configured SCell IE is included in the UE context change request message, gNB-DU shall configure the UL for the indicated SpCell accordingly. If a servingCellMO IE is included in the UE context change request message, gNB-DU shall configure the servingCellMO for the indicated SCell accordingly.

[0082] <Next changes> 9.2.2.2 UE Context Setup Response This message is sent by gNB-DU to confirm the setup of the UE context. Direction: gNB-DU to gNB-CU. TIFF2026509736000004.tif251170TIFF2026509736000005.tif251170TIFF2026509736000006.tif250170 TIFF2026509736000007.tif251170TIFF2026509736000008.tif243170TIFF2026509736000009.tif176170

[0083] In one embodiment, the above information is also present in the UE context change response message.

[0084] <Next changes> 9.2.2.7 UE Context Change Request This message is sent by gNB-CU to provide gNB-DU with UE context information changes. Direction: gNB-CU to gNB-DU TIFF2026509736000010.tif251170TIFF2026509736000011.tif251170TIFF2026509736000012.tif251170TIFF202650973 6000013.tif252170TIFF2026509736000014.tif85170TIFF2026509736000015.tif39170TIFF2026509736000016.tif24170

[0085] <Next changes> 9.2.2.8 UE Context Change Response This message is sent by gNB-DU to acknowledge changes in the UE context. Direction: gNB-DU to gNB-CU. TIFF2026509736000017.tif227170TIFF2026509736000018.tif220170TIFF2026509736000019.tif176170

[0086] <Next changes> This IE contains RRC information sent from gNB-CU to gNB-DU. TIFF2026509736000020.tif250170TIFF2026509736000021.tif250170TIFF2026509736 000022.tif251170TIFF2026509736000023.tif62170TIFF2026509736000024.tif24170

[0087] This IE contains RRC information sent from gNB-DU to gNB-CU. TIFF2026509736000025.tif230170TIFF2026509736000026.tif230170TIFF2026509736000027.tif230170 TIFF2026509736000028.tif230170TIFF2026509736000029.tif231170TIFF2026509736000030.tif168170

[0088] Figure 4 shows an example of a communication system 400 according to several embodiments.

[0089] In this example, the communication system 400 includes a telecommunications network 402 which includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410A and 410B (one or more of them may generally be referred to as network node 410), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). The network node 410 facilitates direct or indirect connectivity of UEs, such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of them may generally be referred to as UE412) to the core network 406 via one or more wireless connections.

[0090] Exemplary wireless communication via wireless connection includes transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wires, cables, or other material conductors. Furthermore, in different embodiments, the communication system 400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals via wired or wireless connections. The communication system 400 may include and / or interface with any type of communication, telecommunications, data, cellular, wireless network, and / or other similar types of systems.

[0091] UE412 may be any of a wide variety of communication devices, including wireless devices configured, set up, and / or operable to communicate wirelessly with network node 410 and other communication devices. Similarly, network node 410 may be configured, enabled, set up, and / or operable to communicate directly or indirectly with UE412 and / or other network nodes or devices in telecommunications network 402 in order to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management in telecommunications network 402.

[0092] In the illustrated example, the core network 406 connects the network node 410 to one or more hosts, such as host 416. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 406 includes one or more core network nodes (e.g., core network node 408) constructed using hardware and software components. The characteristics of these components may be substantially the same as those described for the UE, network nodes, and / or hosts, and therefore their descriptions are generally applicable to the corresponding components of core network node 408. An exemplary core network node includes one or more functions from among the following: 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), Subscriber Identifier Decryption Function (SIDF), Unified Data Management (UDM), Security Edge Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0093] Host 416 may be owned or under the control of a service provider other than the operator or provider of the access network 404 and / or the telecommunications network 402, and may be operated by or on behalf of the service provider. Host 416 may host a variety of applications to provide one or more services. Examples of such applications include data collection services such as extracting and compiling live and recorded audio / video content, data on various ambient conditions detected by multiple UEs, analytical functions, social media, functions for controlling or possibly interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0094] Overall, the communication system 400 in Figure 4 enables connectivity between the UE, network nodes, and hosts. In this sense, the communication system 400 may be configured to operate according to predefined rules or procedures, including, but not limited to, certain standards such as: Global Mobile Communication System (GSM), Universal Mobile Communication System (UMTS), Long-Term Evolution (LTE), and / or other suitable second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., sixth generation (6G)), wireless local area network (WLAN) standards such as the IEEE 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as Global 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.

[0095] In some examples, the telecommunications network 402 is a cellular network implementing 3GPP standardization features. Therefore, the telecommunications network 402 may support network slicing to provide different logical networks to different devices connected to the telecommunications network 402. For example, the telecommunications network 402 may provide ultra-high reliability low latency communications (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and / or provide massive machine-type communications (mMTC) / Massive Internet of Things (IoT) services to further UEs.

[0096] In some examples, UE412 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 404 on a predetermined schedule, triggered by an internal or external event, or in response to a request from access network 404. In addition, the UE may be configured to operate in single or multi-radio access technology (RAT) or multi-standards mode. For example, the UE may operate with one or a combination of WiFi, New Radio (NR), and LTE, i.e., it may be configured for multi-radio dual connectivity (MR-DC), such as dual connectivity with Advanced UMTS Ground RAN (E-UTRAN) and NR (EN-DC).

[0097] In this example, the hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE412C and / or 412D) and a network node (e.g., network node 410B). In some examples, the hub 414 may be a controller, router, content source and analysis, or any other communication device described herein with respect to the UE. For example, the hub 414 may be a broadband router that enables the UE to access the core network 406. In another example, the hub 414 may be a controller that sends commands or instructions to one or more actuators within the UE. Commands or instructions may be received from the UE, the network node 410, or by executable code, scripts, processes, or other instructions within the hub 414. In yet another example, the hub 414 may be a data collector that functions as a temporary storage device for UE data, and in some embodiments may perform data analysis or other processing. In yet another example, the hub 414 may be a content source. For example, in the case of a UE that is a virtual reality (VR) headset, display, loudspeaker, or other media distribution device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes, and then, after performing local processing and / or adding additional local content, provide that media or data directly to the UE. In yet another example, the hub 414 acts as a proxy server or orchestrator for the UE, especially if one or more of the UEs are low-energy IoT devices.

[0098] Hub 414 may have a permanent / persistent or intermittent connection to network node 410B. Hub 414 may also enable different communication methods and / or schedules between Hub 414 and UEs (e.g., UE412C and / or 412D), and between Hub 414 and the core network 406. In other examples, Hub 414 connects to the core network 406 and / or one or more UEs via a wired connection. Furthermore, Hub 414 may be configured to connect to a machine-to-machine (M2M) service provider via the access network 404, and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 410 while still being connected via Hub 414 via a wired or wireless connection. In some embodiments, Hub 414 may be a dedicated hub, i.e., a hub whose primary function is to route communication with UEs to and from network node 410B. In other embodiments, the hub 414 may be a non-dedicated hub, i.e., a device capable of routing communication between the UE and the network node 410B, but also capable of acting as a communication start and / or end point for a certain data channel.

[0099] Figure 5 shows the UE500 in several embodiments. As used herein, UE refers to a device that is capable of, configured in, positioned in, and / or operating in a manner that enables wireless communication with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, Voice over Internet Protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), and automotive or automotive / integrated wireless devices. Other examples include any UE identified by 3GPP, including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0100] A UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for side-link 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 device in question. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended to be sold to or operated by a human user, but may not be associated with, or may not be associated with in the first place with, a specific human user. Alternatively, a UE may represent a device (e.g., a smart electricity meter) that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user.

[0101] The UE500 includes a processing circuit 502 operably coupled to an input / output interface 506, a power supply 508, memory 510, a communication interface 512, and / or any other components, or any combination thereof, via a bus 504. Some UEs may utilize all or a subset of the components shown in Figure 5. The level of integration between components may vary from UE to UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, and receivers.

[0102] The processing circuit 502 is configured to process instructions and data and may be configured to implement any sequential state machine capable of executing instructions stored in memory 510 as machine-readable computer programs. The processing circuit 502 may be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), programmable logic with appropriate firmware, one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit 502 may include multiple central processing units (CPUs).

[0103] In this example, the input / output interface 506 may be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices may allow a user to bring information into the UE500. Examples of input devices include touch-sensitive displays or presence-aware displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smart cards, etc. A presence-aware display may include capacitive or resistive touch sensors for sensing user input. Sensors may include, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biometric sensors, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0104] In some embodiments, the power supply 508 is configured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power supply 508 may further include a power circuit for supplying power to various parts of the UE500 from the power supply 508 itself and / or an external power source via an interface such as an input circuit or a power cable. Supplying power may, for example, be for charging the power supply 508. The power circuit may perform any formatting, conversion, or other modification on the power from the power supply 508 to make power suitable for each component of the UE500 being powered.

[0105] Memory 510 is or can be configured to include random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, or other types of memory. In one example, memory 510 includes one or more application programs 514, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 516. Memory 510 may store any of a variety of operating systems or combinations of operating systems for use by the UE500.

[0106] Memory 510 may include Redundant Array of Independent Disk (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Multipurpose Disk (HD-DVD) optical disk drive, internal hard disk drive, Blu-ray optical disk drive, Holographic Digital Data Storage (HDDS) optical disk drive, external mini dual in-line memory module (DIMM), synchronous dynamic RAM (SDRAM), external microDIMM SDRAM, smart card memory (e.g., a tamper-proof module in the form of a general-purpose integrated circuit card (UICC), including one or more subscriber identification modules (SIMs), e.g., a general-purpose SIM (USIM) and / or an Internet Protocol Multimedia Services Identification Module (ISIM)), other memory, or any combination thereof. UICC is, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory 510 may enable UE500 to access instructions, application programs, etc., stored on temporary or non-temporary memory media, to offload data, or to upload data. Products that utilize communication systems, etc., may be or may be tangibly embodied as memory 510, which may contain or be equipped with a device-readable storage medium.

[0107] The processing circuit 502 may be configured to communicate with an access network or other networks using a communication interface 512. The communication interface 512 may comprise one or more communication subsystems, including or communicatively coupled to an antenna 522. The communication interface 512 may include one or more transceivers used for communication, such as by communicating with one or more remote transceivers of another wirelessly communicable device (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 518 and / or receiver 520 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522), and may share circuit components, software, or firmware, or alternatively, be implemented separately.

[0108] In the illustrated embodiment, the communication functions of the communication interface 512 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth and NFC, location-based communication such as the use of the Global Positioning System (GPS) for determining location, other similar communication functions, or any combination thereof. The communication may be implemented in accordance with one or more communication protocols and / or standards such as IEEE 802.11 (Wi-Fi), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMAX, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Internet Connection with Fast User Datagram Protocol (QUIC), and Hypertext Transfer Protocol (HTTP).

[0109] Regardless of the sensor type, the UE may provide an output of data captured by its sensors through its communication interface 512 or via a wireless connection to a network node. Data captured by the UE's sensors may be communicated to a network node via a wireless connection through another UE. The output may be periodic (e.g., once every 15 minutes if reporting sensed temperature), random (e.g., to equalize the load from reports from several sensors), in response to a trigger event (e.g., an alert is sent when moisture is detected), in response to a request (e.g., a user start request), or a continuous stream (e.g., a live video feed of a patient).

[0110] As another example, a UE may include actuators, motors, or switches 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 state of the actuators, motors, or switches may change. For example, a UE may include a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0111] When a UE is in the form of an IoT device, it may also be a device for use in one or more application domains, which include, but are not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-exclusive examples of such IoT devices include connected refrigerators or freezers, televisions, connected lighting devices, electric meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality, wearables for haptic augmentation or sensory enhancement, water sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device, or a device incorporated into them, such as a heart rate monitor or remotely controlled surgical robot. The UE in the form of an IoT device comprises circuitry and / or software, depending on the intended use of the IoT device, in addition to other components described in relation to the UE500 shown in Figure 5.

[0112] In yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE may also be an M2M device, which in a 3GPP context might be called an MTC device. In one specific example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle such as a car, bus, truck, ship, airplane, or other equipment that is capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0113] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be a drone or integrated into a drone and provide the drone's speed information (obtained through a speed sensor) to the second UE, which 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 actuators) to increase or decrease the drone's speed. The first UE and / or the second UE may also include two or more of the functions described above. For example, the UE may include a sensor and an actuator and handle the communication of data for both the speed sensor and the actuator.

[0114] Figure 6 shows network node 600 according to several embodiments. As used herein, a network node refers to a device that is configured, set to communicate, and / or operational, capable of communicating directly or indirectly with the UE and / or other network nodes or devices in the telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), base stations (BSs) (e.g., radio BSs, node Bs, advanced node Bs (eNBs), and NR node Bs (gNBs)).

[0115] BSs can be classified based on the amount of coverage they provide (or, in other words, their transmit power level), and are therefore sometimes called femtoBS, picoBS, microBS, or macroBS depending on the amount of coverage they provide. A BS can be a relay node or relay donor node that controls relays. Network nodes can also include one or all of the parts of a distributed radio BS, such as a centralized digital unit and / or remote radio unit (RRU), which may also be called a remote radio head (RRH). Such an RRU may or may not be integrated with an antenna as an antenna-integrated radio. Some parts of a distributed radio BS are sometimes called nodes in a distributed antenna system (DAS).

[0116] Other examples of network nodes include multiple transmit point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BS, network controllers such as radio network controllers (RNCs) or BS controllers (BSCs), base station transceivers (BTSs), transmit points, transmit nodes, multi-cell / multicast coordinated entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., advanced serving mobile location centers (E-SMLCs)), and / or drive test minimization (MDT).

[0117] Network node 600 includes a processing circuit 602, memory 604, communication interface 606, and power supply 608. Network node 600 may consist of multiple physically distinct components (e.g., node B components and RNC components, or BTS components and BSC components), each of which may have its own distinct components. In some scenarios where network node 600 has multiple distinct components (e.g., BTS and BSC components), one or more of the distinct components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique node B-RNC pair may, in some cases, be considered a single distinct network node. In some embodiments, network node 600 may be configured to support multiple RATs. In such embodiments, some components (e.g., distinct memory 604 for different RATs) may be duplicated, and some components may be reused (e.g., antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of various indicated components for different wireless technologies integrated into the network node 600, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be incorporated into the same or different chips or sets of chips and other components within the network node 600.

[0118] The processing circuit 602 may include one or more combinations of microprocessors, controllers, microcontrollers, CPUs, DSPs, ASICs, FPGAs, or any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic that can operate to provide network node 600 functionality, either alone or together with other network node 600 components such as memory 604.

[0119] In some embodiments, the processing circuit 602 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit 602 includes one or more of the radio frequency (RF) transceiver circuit 612 and the baseband processing circuit 614. In some embodiments, the RF transceiver circuit 612 and the baseband processing circuit 614 may be on separate chips (or sets of chips), boards, or units such as radio and digital units. In alternative embodiments, some or all of the RF transceiver circuit 612 and the baseband processing circuit 614 may be on the same chip or set of chips, board, or unit.

[0120] Memory 604 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-temporary device-readable memory device, and / or computer-executable memory device, for storing information, data, and / or instructions that can be used by the processing circuit 602. Memory 604 may store any appropriate instructions, data, or information, including computer programs, software, and applications, which include one or more logic, rules, codes, tables, and / or other instructions that can be executed by the processing circuit 602 and made available to the network node 600. Memory 604 may be used to store any calculations performed by the processing circuit 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuit 602 and the memory 604 are integrated.

[0121] The communication interface 606 is used for wired or wireless signaling and / or data between network nodes, access networks, and / or UEs. As illustrated, the communication interface 606 includes a port / terminal 616 for sending and receiving data to and from the network, for example, via a wired connection. The communication interface 606 also includes a wireless front-end circuit 618, which may be coupled to or, in some embodiments, part of the antenna 610. The wireless front-end circuit 618 comprises a filter 620 and an amplifier 622. The wireless front-end circuit 618 can be connected to the antenna 610 and the processing circuit 602. The wireless front-end circuit 618 may be configured to adjust signals communicated between the antenna 610 and the processing circuit 602. The wireless front-end circuit 618 may receive digital data to be sent to other network nodes or UEs via the wireless connection. The wireless front-end circuit 618 may use the combination of the filter 620 and / or the amplifier 622 to convert the digital data into a wireless signal with appropriate channel and bandwidth parameters. The wireless signal may then be transmitted via the antenna 610. Similarly, when receiving data, antenna 610 may collect radio signals that are converted into digital data by the radio front-end circuit 618. The digital data may be passed to processing circuit 602. In other embodiments, the communication interface 606 may comprise different components and / or different combinations of components.

[0122] In some alternative embodiments, the network node 600 does not include a separate radio front-end circuit 618; instead, the processing circuit 602 includes the radio front-end circuit and is connected to the antenna 610. Similarly, in some embodiments, all or part of the RF transceiver circuit 612 is part of the communication interface 606. In yet another embodiment, the communication interface 606, as part of a radio unit (not shown), includes one or more ports or terminals 616, a radio front-end circuit 618, and an RF transceiver circuit 612, and the communication interface 606 communicates with a baseband processing circuit 614, which is part of a digital unit (not shown).

[0123] Antenna 610 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 610 may be coupled to the wireless front-end circuit 618 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 610 is separate from the network node 600 and can be connected to the network node 600 through an interface or port.

[0124] The antenna 610, communication interface 606, and / or processing circuit 602 may be configured to perform any receiving operations and / or specific acquisition operations as described herein as being performed by the network node 600. Any information, data, and / or signals may be received from the UE, another network node, and / or any other network equipment. Similarly, the antenna 610, communication interface 606, and / or processing circuit 602 may be configured to perform any transmitting operations as described herein as being performed by the network node 600. Any information, data, and / or signals may be transmitted to the UE, another network node, and / or any other network equipment.

[0125] Power supply 608 supplies power to the various components of network node 600 in a form suitable for each component (for example, at the voltage and current levels required for each respective component). Power supply 608 may further include, or be coupled to, a power management circuit for supplying power to the components of network node 600 to perform the functions described herein. For example, network node 600 may be connectable to an external power source (e.g., a power grid or electrical outlet) via an interface such as an input circuit or electrical cable, thereby the external power source supplying power to the power circuit of power supply 608. As a further example, power supply 608 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. The battery may provide backup power in the event of a failure of the external power source.

[0126] Embodiments of the network node 600 may include additional components other than those shown in Figure 6 to provide several aspects of the network node's functionality, including any of the functions described herein and / or any functions necessary to support the subject matter described herein. For example, the network node 600 may include user interface equipment to enable input of information to and output of information from the network node 600. This would allow a user to perform diagnostic, maintenance, repair, and other management functions of the network node 600.

[0127] Figure 7 is a block diagram of a host 700 that may be an embodiment of host 416 in Figure 4, according to various aspects described herein. As used herein, host 700 may be or include various combinations of hardware and / or software, including standalone servers, blade servers, cloud implementation servers, distributed servers, virtual machines, containers, or processing resources within a server farm. Host 700 may provide one or more services to one or more UEs.

[0128] The host 700 includes a processing circuit 702 operably coupled to an input / output interface 706, a network interface 708, a power supply 710, and memory 712 via a bus 704. Other embodiments may include other components. The characteristics of these components may be substantially the same as those described with respect to the devices in the previous figures, such as Figures 5 and 6, and therefore their descriptions are generally applicable to the corresponding components of the host 700.

[0129] Memory 712 may include one or more computer programs, including one or more host application programs 714, and data 716, which may include user data, such as data generated by the UE for the host 700 or data generated by the host 700 for the UE. Embodiments of the host 700 may utilize only a subset or all of the illustrated components. The host application program 714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Multipurpose Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Expert Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (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, and heads-up display systems). The host application program 714 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node such as a device within the core network or at the edge of the core network. Thus, host 700 may select and / or indicate different hosts for over-the-top (OTT) services for the UE. The host application program 714 may support various protocols such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), and Dynamic Adaptive Streaming over HTTP: DASH or MPEG-DASH.

[0130] Figure 8 is a block diagram showing a virtualized environment 800 in which functions implemented by several embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device or component described herein 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 800 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes may be fully virtualized.

[0131] Application 802 (which may be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc., instead) is launched within the virtualization environment 800 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0132] Hardware 804 includes processing circuits, memory for storing software and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers 806 (also called hypervisors or VM monitors (VMMs)), provide VM808A and 808B (one or more of them may generally be called VM808), and / or perform any of the functions, features, and / or benefits described in relation to some embodiments described herein. The virtualization layer 806 can present a virtual operating platform that appears to the VM808 as networking hardware.

[0133] VM808 includes virtual processing, virtual memory, virtual networking, or interfaces and virtual storage, and may be run by the corresponding virtualization layer 806. Different embodiments of instances of virtual appliance 802 may be implemented on one or more of VM808, and the implementation may be carried out in different ways. Hardware virtualization is, depending on the context, called Network Function Virtualization (NFV). NFV can be used to consolidate many types of network equipment onto industry-standard high-capacity server hardware, physical switches, and physical storage devices, which may be located in data centers and customer premises equipment.

[0134] In the context of NFV, a VM808 may be a software implementation of a physical machine that runs a program as if it were running on a physical, non-virtualized machine. Each VM808, and that portion of the hardware 804 running its VM, forms a separate virtual network element, whether it is dedicated hardware for that VM and / or hardware shared with other VM808s by that VM. Furthermore, in the context of NFV, a virtual network function runs in one or more VM808s on the hardware 804 and is responsible for handling specific network functions corresponding to the application 802.

[0135] Hardware 804 may be implemented in a standalone network node having general-purpose or specific components. Hardware 804 may implement some functions through virtualization. Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g., in a data center or CPE) where many hardware nodes work together and are managed, among other things, via management and orchestration 810 that oversees the lifecycle management of application 802. In some embodiments, hardware 804 is coupled to one or more radio units, each containing one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces, or they may be used in combination with virtual components to provide virtual nodes with radio capabilities such as RAN or BS. In some embodiments, some signaling can be provided using a control system 812, which may be used alternatively for communication between hardware nodes and radio units.

[0136] The computing devices described herein (e.g., UEs, network nodes, hosts) may include the indicated combinations of hardware components, but other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by processing circuits, which may process information by, for example, converting obtained information into other information, comparing the obtained or converted information with information stored in a network node, and / or performing one or more operations based on the obtained or converted information, and as a result of the processing making decisions. Furthermore, although components are shown as located within a larger box or as a single box nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that comprise a single indicated component, and functions may be divided among separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0137] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored in a separate or discrete device-readable storage medium, such as via a hard wired connection. In any of these particular embodiments, whether or not it executes instructions stored in a non-temporary computer-readable storage medium, the processing circuit can be configured to perform the functions described. The benefits provided by such functions are not limited to the processing circuit alone or other components of the computing device, but are generally enjoyed by the computing device as a whole, and / or by the end user and the wireless network.

[0138] Some embodiments of this disclosure include the following:

[0139] Embodiment 1: A method performed by a first network node (110) for generating pre-configured measurement gaps for a plurality of bandwidth portions (BWPs) for a user equipment device (UE) (302), the method comprising: providing a second network node (108) with a list of configured inactive BWPs associated with the UE (302) (308); receiving a request from the second network node (108) to generate pre-configured measurement gaps associated with selected BWPs from the list of configured inactive BWPs (314); and providing the second network node (108) with information identifying the pre-configured measurement gaps associated with the selected BWPs (316).

[0140] Embodiment 2: The method according to Embodiment 1, wherein providing a list of configured inactive BWPs associated with UE(302) is done in a UE context change response message in response to receiving a UE context change request message (304).

[0141] Embodiment 3: The method according to Embodiment 1, wherein providing a list of configured inactive BWPs associated with UE(302) is done in a UE context setup response message in response to receiving a UE context setup request message (304).

[0142] Embodiment 4: The method according to any one of Embodiments 1 to 3, wherein the list of configured inactive BWPs associated with UE(302) further comprises at least one of the serving cells or BWP locations associated with each inactive BWP in the list of configured inactive BWPs.

[0143] Embodiment 5: The method according to any one of Embodiments 1 to 4, wherein providing information identifying a pre-configured measurement gap associated with a selected BWP is done in response to a first network node (110) that supports switching of the active BWP via downlink control information.

[0144] Embodiment 6: The method according to any one of Embodiments 1 to 5, wherein the request to generate a pre-configured measurement gap associated with a selected BWP includes a list of frequencies in which a second network node (108) requests a first network node (110) to generate a pre-configured measurement gap.

[0145] Embodiment 7: The method according to any one of Embodiments 1 to 6, wherein information identifying a pre-configured measurement gap is included in another UE context change response message, which also includes an updated CellGroupConfig information element.

[0146] Embodiment 8: The method according to any one of Embodiments 1 to 7, wherein the first network node (110) is a distributed unit (DU) network node and the second network node (108) is a central unit (CU) network node.

[0147] Embodiment 9: A first network node (110) for generating pre-configured measurement gaps for a plurality of bandwidth portions (BWPs) for a user equipment device (UE) (302), wherein the first network node (110) comprises processing circuitry for performing an operation, the operation of which includes providing a second network node (108) with a list of configured inactive BWPs associated with the UE (302) (308), receiving a request from the second network node (108) to generate pre-configured measurement gaps associated with selected BWPs from the list of configured inactive BWPs (314), and providing the second network node (108) with information identifying the pre-configured measurement gaps associated with the selected BWPs (316).

[0148] Embodiment 10: A first network node (110) is further configured to perform the method described in any of Embodiments 2 to 8.

[0149] Embodiment 11: A method performed by a second network node (108) for requesting pre-configured measurement gaps for a plurality of bandwidth portions (BWPs) for a user equipment device (UE) (302), the method comprising: receiving a list of configured inactive BWPs associated with the UE (302) from a first network node (110) (306); deciding to request pre-configured measurement gaps for one or more inactive BWPs from the list of configured inactive BWPs (312); providing the first network node (110) with a request to generate pre-configured measurement gaps associated with one or more inactive BWPs from the list of configured inactive BWPs (314); receiving information from the first network node (110) identifying pre-configured measurement gaps associated with the selected BWPs (316); and configuring the UE (302) with the pre-configured measurement gaps (318).

[0150] Embodiment 12: The method according to Embodiment 11, wherein receiving a list of configured inactive BWPs associated with UE(302) is done in a UE context change response message in response to providing a UE context change request message to a first network node (110) (304).

[0151] Embodiment 13: The method according to Embodiment 11, wherein receiving a list of configured inactive BWPs associated with UE(302) is done in a UE context setup response message in response to providing a UE context setup request message to a first network node (110) (304).

[0152] Embodiment 14: The method according to any one of embodiments 11 to 13, wherein the list of configured inactive BWPs associated with UE(302) further comprises at least one of the serving cells or BWP locations associated with each inactive BWP in the list of configured inactive BWPs.

[0153] Embodiment 15: The method according to any one of embodiments 11 to 14, wherein receiving information identifying a pre-configured measurement gap associated with a selected BWP is done in response to a first network node (110) that supports switching of the active BWP via downlink control information.

[0154] Embodiment 16: The method according to any one of Embodiments 11 to 15, wherein the request to generate a pre-configured measurement gap associated with a selected BWP includes a list of frequencies in which a second network node (108) requests a first network node (110) to generate a pre-configured measurement gap.

[0155] Embodiment 17: The method according to any one of Embodiments 11 to 16, wherein information identifying a pre-configured measurement gap is included in another UE context change response message, which also includes an updated CellGroupConfig information element.

[0156] Embodiment 18: The method according to any one of Embodiments 11 to 17, wherein the first network node (110) is a distributed unit (DU) network node and the second network node (108) is a central unit (CU) network node.

[0157] Embodiment 19: A second network node (108) that requests pre-configured measurement gaps for a plurality of bandwidth portions (BWPs) for a user equipment device (UE) (302), wherein the second network node (108) comprises processing circuitry for performing an operation, the operation comprising: receiving from a first network node (110) a list of configured inactive BWPs associated with the UE (302) (306); deciding to request pre-configured measurement gaps for one or more inactive BWPs from the list of configured inactive BWPs (312); providing the first network node (110) a request to generate pre-configured measurement gaps associated with one or more inactive BWPs from the list of configured inactive BWPs (314); receiving from the first network node (110) information identifying the pre-configured measurement gaps associated with the selected BWPs (316); and configuring the UE (302) with the pre-configured measurement gaps (318).

[0158] Embodiment 20: A second network node (108) as described in Embodiment 19, further configured to perform the method described in any of Embodiments 12 to 18.

[0159] Those skilled in the art will recognize improvements and modifications to embodiments of the present disclosure. All such improvements and modifications shall be deemed to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a first network node (110) for generating pre-configured measurement gaps for multiple bandwidth portions (BWPs) for a user equipment device (UE) (302), the method being: The second network node (108) is provided with a list of configured BWPs associated with the UE (302), The second network node (108) receives a request (314) to generate a pre-configured measurement gap associated with a selected BWP from the list of configured BWPs, A method comprising providing the second network node (108) with information identifying the pre-configured measurement gap associated with the selected BWP (316).

2. The method according to claim 1, wherein providing the list of configured BWPs associated with the UE (302) is done in a UE context change response message in response to receiving a UE context change request message (304).

3. The method according to claim 1, wherein providing the list of configured BWPs associated with the UE (302) is done in a UE context setup response message in response to receiving a UE context setup request message (304).

4. The method according to any one of claims 1 to 3, wherein the list of configured BWPs associated with the UE(302) further comprises at least one of a serving cell or BWP location associated with each BWP in the list of configured BWPs.

5. The method according to any one of claims 1 to 4, wherein providing the information identifying the pre-configured measurement gap associated with the selected BWP is done in response to the first network node (110) supporting the switching of the active BWP via downlink control information.

6. The method according to any one of claims 1 to 5, wherein the request to generate a pre-configured measurement gap associated with a selected BWP includes a list of frequencies on which the second network node (108) requests the first network node (110) to generate the pre-configured measurement gap.

7. The method according to any one of claims 1 to 6, wherein the information identifying the pre-configured measurement gap is included in another UE context change response message, which also includes an updated CellGroupConfig information element.

8. The method according to any one of claims 1 to 7, wherein the first network node (110) is a distributed unit (DU) network node, and the second network node (108) is a central unit (CU) network node.

9. A first network node (110) generates pre-configured measurement gaps for a plurality of bandwidth portions (BWPs) for a user equipment device (UE) (302), wherein the first network node (110) comprises processing circuitry for performing an operation, the operation being: The second network node (108) is provided with a list of configured BWPs associated with the UE (302), The second network node (108) receives a request (314) to generate a pre-configured measurement gap associated with a selected BWP from the list of configured BWPs, The first network node (110) includes providing the second network node (108) with information (316) that identifies the pre-configured measurement gap associated with the selected BWP.

10. The processing circuit is further configured to perform the method according to any one of claims 2 to 8, the first network node (110) according to claim 9.

11. A method performed by a second network node (108) for requesting pre-configured measurement gaps for multiple bandwidth portions (BWPs) for a user equipment device (UE) (302), the method being: The first network node (110) receives a list of configured BWPs associated with the UE (302) (306), (312) Deciding to request a pre-set measurement gap for one or more BWPs from the list of pre-configured BWPs, A request is provided to the first network node (110) to generate a pre-configured measurement gap associated with one or more BWPs from the list of configured BWPs (314), A method comprising receiving information from the first network node (110) that identifies the pre-configured measurement gap associated with the selected BWP (316).

12. The method according to claim 11, wherein receiving the list of configured BWPs associated with the UE (302) is done in a UE context change response message in response to providing a UE context change request message to a first network node (110) (304).

13. The method according to claim 11, wherein receiving the list of configured BWPs associated with the UE (302) is done in a UE context setup response message in response to providing a UE context setup request message to the first network node (110) (304).

14. The method according to any one of claims 11 to 13, wherein the list of configured BWPs associated with the UE(302) further comprises at least one of the serving cells or BWP locations associated with each BWP in the list of configured BWPs.

15. The method according to any one of claims 11 to 14, wherein receiving the information identifying the pre-configured measurement gap associated with the selected BWP is done in response to the first network node (110) supporting the switching of the active BWP via downlink control information.

16. The method according to any one of claims 11 to 15, wherein the request to generate a pre-configured measurement gap associated with a selected BWP includes a list of frequencies on which the second network node (108) requests the first network node (110) to generate the pre-configured measurement gap.

17. The method according to any one of claims 11 to 16, wherein the information identifying the pre-configured measurement gap is included in another UE context change response message, which also includes an updated CellGroupConfig information element.

18. The method according to any one of claims 11 to 17, wherein the first network node (110) is a distributed unit (DU) network node, and the second network node (108) is a central unit (CU) network node.

19. A second network node (108) requests pre-configured measurement gaps for a plurality of bandwidth portions (BWPs) for a user equipment device (UE) (302), wherein the second network node (108) comprises processing circuitry for performing an operation, the operation being: The first network node (110) receives a list of configured BWPs associated with the UE (302) (306), (312) Deciding to request a pre-set measurement gap for one or more BWPs from the list of pre-configured BWPs, A request is provided to the first network node (110) to generate a pre-configured measurement gap associated with one or more BWPs from the list of configured BWPs (314), A second network node (108) includes receiving information (316) from the first network node (110) that identifies the pre-configured measurement gap associated with the selected BWP.

20. The processing circuit is further configured to perform the method described in any one of claims 12 to 18, the second network node (108) according to claim 19.

Images