Radio Resource Management Requirements for New Wireless Dual Connectivity

Abstract

This disclosure specifies requirements for supporting Multi-Radio (MR)-Dual Connectivity (DC) Radio Resource Management (RRM) requirements, including RRM requirements for Frequency Range 1 (FR1)+FR1 New Radio (NR)-NR Dual Connectivity (NR-DC) scenarios.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to U.S. Provisional Application No. 63 / 394,866, filed August 3, 2022, the entire contents of which are incorporated herein by reference.

[0002] [Technical field] The present disclosure relates generally to wireless communications, cellular networks, cloud computing, edge computing, data centers, network topologies and communication system implementations, and more particularly to radio resource management (RRM) requirements for new radio (NR) dual connectivity (DC). [Background technology]

[0003] In 3GPP (Third Generation Partnership Project) systems, RRM includes mechanisms that ensure efficient use of available radio resources and also provides mechanisms that enable fifth generation (5G) / NR networks to meet radio resource-related requirements. In particular, RRM provides the means to manage (e.g., allocate, reallocate, and release) radio resources, taking into account single-cell and multi-cell aspects.

[0004] 5G / NR systems also support multi-radio DC (MR-DC), in which a user equipment (UE) can transmit and receive data on multiple component carriers (CCs) from two cell groups to increase throughput. The two cell groups include a master cell group (MCG) and a secondary cell group (SCG). A typical NR-NR dual connectivity (NR-DC) scenario includes a CC of the MCG operating in a first frequency range (FR1) and a CC of the SCG operating in a second frequency range (FR2), and the UE is configured to perform measurements in both FR1 and FR2. These measurements include RRM-related measurements. However, RRM requirements for the FR1-FR1 NR-DC scenario have not yet been defined. [Brief explanation of the drawings]

[0005] BRIEF DESCRIPTION OF THE DRAWINGS Embodiments will be readily understood by the following detailed description taken in conjunction with the accompanying drawings, in which: To facilitate this description, like reference numerals refer to like structural elements; and Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings, in which: [Figure 1] 1 illustrates an exemplary network architecture. [Figure 2] 1 illustrates an exemplary wireless network. [Figure 3] Showing exemplary hardware resources [Figure 4] 1 illustrates an exemplary measurement model. [Figure 5] 1 illustrates an exemplary process for implementing various embodiments discussed herein. [Figure 6] 1 illustrates an exemplary process for implementing various embodiments discussed herein. [Figure 7] 1 illustrates an exemplary process for implementing various embodiments discussed herein. DETAILED DESCRIPTION OF THE INVENTION

[0006] 1. RRM requirements for FR1+FR1 NR-DC aspects The 3GPP work item description (WID) RP-220977, titled "Even Further RRM enhancement for NR and MR-DC," introduces several enhancements for NR and multi-radio (MR)-dual connectivity (DC) radio resource management (RRM) requirements to be specified and / or defined, including RRM requirements for FR1-FR1 NR-NR dual connectivity (NR-DC) scenarios.

[0007] The frequency ranges in which NR can operate include Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 includes the frequency range of 410 MHz to 7125 MHz. FR2 includes two sub-FRs: FR2-1, which has a frequency range of 24250 MHz to 52600 MHz, and FR2-2, which has a frequency range of 52600 MHz to 71000 MHz. Further aspects of FR1 and FR2 are discussed in 3GPP TS38.104 and [TS38133].

[0008] The FR1+FR1 NR-DC band combination was introduced in Release (Rel)-16, and related deployment scenarios are expected to be used globally. However, RRM requirements for FR1+FR1 NR-DC are missing, which may adversely affect overall performance in NR-DC scenarios. Specifically, one of the objectives of RP-220977 is to define RRM requirements for FR1-FR1 NR-DC scenarios. RRM requirements include the number of serving carriers, PSCell addition / release delay requirements, primary secondary cell group (SCG) cell (PSCell) change, conditional PSCell change delay, scheduling availability, and carrier-specific scaling factor (CSSF). Other Rel-15 requirements are not excluded. For R16 and R17 features, RRM requirements for FR1-FR1 NR-DC include HO using PSCell, SCG activation / deactivation, and CPAC. This disclosure defines new RRM requirements for FR1+FR1 NR-DC scenarios.

[0009] [1.1. Number of serving carriers for NR-DC] The number of serving carriers requirement for NR-DC is applicable to a UE 102 configured with the following number of serving NR component carriers (CCs): up to two NR downlink (DL) CCs in FR1 in total, and up to eight NR DL CCs in FR2 in total, along with one UL in the PCell, one uplink (UL) in the PSCell, and up to one UL in each SCell.

[0010] In a first example, the requirements for FR1+FR1 NR-DC are applicable to a UE 102 configured with the following number of serving NR CCs: one UL in the PCell, one UL in the PSCell, and up to one UL in each SCell, for a total of up to 10 NR DL CCs:

[0011] In a second example, the requirements for FR1+FR1 NR-DC are applicable to a UE 102 configured with the following number of serving NR CCs: up to five NR DL CCs in the PCell and up to five DL CCs in the PSCell, along with one UL in the PCell, one UL in the PSCell, and up to one UL in each SCell.

[0012] In a third example, the requirements for FR1+FR1 NR-DC are applicable to a UE 102 configured with the following number of serving NR CCs: one UL in the PCell, one UL in the PSCell, and up to eight UL SCells, for a total of up to ten NR DL CCs:

[0013] [1.2. NR-DC PSCELL Addition and Release Delay Requirements] The NR-DC addition and release delay requirements define the delay by which a UE 102 can configure a PSCell in NR-DC. The NR-DC addition and release delay requirements are applicable to NR-DC-capable UEs 102. These requirements are also applicable to PSCell change delay requirements (e.g., the delay by which a UE 102 can change a PSCell to another cell in NR-DC).

[0014] The PSCell release delay requirement applies to a UE 102 configured with a PCell and at least one PSCell. Upon receiving a PSCell release in subframe n, the UE 102 RRC_delay / NR slot length), perform the release action specified in [TS38331]. RRC_delayis the RRC procedure delay specified in [TS38331] (see Table 1.2-1). PCell suspension, as specified in Section 8.2 of [TS38133], is only allowed during the RRC reconfiguration procedure (see, for example, [TS38331]).

[0015] The PSCell addition delay requirement applies to a UE 102 configured with only a PCell in FR1. Currently, the PSCell addition delay requirement is defined for the FR1+FR2 scenario, and upon receiving a PSCell addition in subframe n, the UE 102 must config_PSCell Upon receiving a PSCell addition in subframe n, the UE 102 may transmit a physical random access channel (PRACH) preamble to the PSCell in FR2 by slot n+(T config_PSCell In either case, the PRACH preamble can be transmitted to the PSCell in FR2 within T config_PSCell is defined as shown in Equation 1.2-1, and the parameters / variables of Equation 1.2-1 are provided in Table 1.2-1. T config_PSCell =T RRC_delay +T processing +T search +T Δ +T PSCell_DU +2 milliseconds (ms) (1.2-1) [Table 1]

[0016] In FR1 and FR2, a PSCell is configured if the following conditions are met: the UE 102 has transmitted a valid measurement report for the configured PSCell during the last 5 seconds before receiving the PSCell configuration command, one of the measured SSBs from the configured PSCell remains detectable according to the cell identification conditions specified in clause 9.3 of [TS38133], and one of the measured SSBs from the configured PSCell remains detectable according to the cell identification conditions specified in clause 9.3 of [TS38133] within the PSCell configuration delay T config_PSCell ), it is known. Otherwise, the PSCell is unknown. PCell suspension as specified in Section 8.2 of [TS38133] is only allowed during RRC reconfiguration procedures (see, for example, [TS38331]). Additionally or alternatively, if the SSB-based measurement timing configuration (SMTC) period of the target cell is not provided in the PSCell addition, release, or modification message, and measObjectNRs with the same SSB frequency and subcarrier spacing configured by the MN and SN have different SMTCs, then T rs is one period of the SMTC, which depends on the UE implementation.

[0017] According to various embodiments, some modifications are made to the above requirements and / or parameters for FR1+FR1 NR-DC. In some embodiments, the PSCell additional delay is T processing = 20. This is because the PSCell is in the same frequency range (FR) as the PCell, which means that RF warming is not required. Additionally or alternatively, the PSCell additional delay is T for FR1-FR1 NR-DC. search =3*T rsms, since the target cell is in FR1 and Rx beam sweeping is not required. In these embodiments, the UE 102 can transmit a PRACH preamble towards the target PSCell no later than previously specified for NR-DC, where T processing and T search The modified value of overrides the existing value in Table 1.2-1.

[0018] [1.3.FR1-FR1 UE Availability Scheduling for RLM in NR-DC] In legacy 3GPP standards, there are no FR1+FR2 scenarios for NR-DC. In particular, the legacy 3GPP standards specify that there are no scheduling restrictions on FR1 serving cells due to radio link monitoring performed for FR2 serving PCells and / or PSCells, and that there are no scheduling restrictions on FR2 serving cells due to radio link monitoring performed for FR1 serving PCells and / or PSCells.

[0019] Similar to inter-band carrier aggregation within FR1, there are no scheduling restrictions on the FR1 serving cell due to the radio link monitoring performed on the FR1 PSCell. In some embodiments, the 3GPP standard (e.g., [TS38133] §8.1.7.4) is updated to include the following: There are no scheduling restrictions on the FR1 serving cell due to the radio link monitoring (RLM) performed on the FR1 PSCell.

[0020] [1.4. Carrier-specific scaling factors] The measurement window (e.g., SMTC or CSI-RS resource period) of an SSB-based or CSI-RS-based measurement may not fully overlap with a measurement gap (MG) or other measurement period. For example, the measurement window and measurement period / MG may be non-overlapping, partially overlapping, or fully overlapping. To meet specified / configured measurement accuracy requirements, the measurement period / MG may be scaled through a measurement delay scaling mechanism, where the UE 102 receives sufficient measurement samples of the reference signal for evaluation and then reports the measurement results to the network within an intra-frequency (intra-frequency) or inter-frequency (inter-frequency) measurement period. When the UE 102 is configured to monitor multiple measurement objects (MOs), the UE 102 derives or determines a carrier-specific scaling factor (CSSF) value to scale the measurement delay requirements for performing measurements on the multiple MOs.

[0021] When the UE 102 is configured to monitor multiple MOs, the CSSF value is used to scale the measurement delay requirements given in Sections 9.2, 9.2A, 9.3, 9.3A, and 9.4 of [TS38133], the NR PRS-based positioning measurements in Section 9.9 of [TS38133], and the CSI-RS-based L3 measurements in Section 9.10 of [TS38133]. The CSSF value is used to scale the CSSF for measurements made outside the MG and inside the MG, respectively. outside_gap,i and CSSF within_gap,i In particular, if the UE 102 is supposed to perform measurements of MOi outside the MG, the UE 102 should outside_gap,i and if the UE 102 is supposed to perform measurements of MOi inside the MG, the UE 102 may derive the cell identity and measurement period based on within_gap,i The cell identity and measurement period can be derived based on

[0022] For intra-frequency measurements, the parameter CSSF intra is used for measurements made outside the MG (e.g., when the intra-frequency SMTC does not fully overlap or partially overlaps with the MG or NCSG), as discussed herein and / or in [TS38133] §9.1.5.1. outside_gap,i or for measurements made within the MG (e.g., when the intra-frequency SMTC completely overlaps with the MG), the CSSF as discussed herein and / or in [TS38133] §9.1.5.2. within_gap,i In some examples, the parameter CSSF intra is the CSSF as discussed herein and / or in [TS38133] §9.1.5.3 for measurements made within an NCSG (e.g., when an intra-frequency SMTC completely overlaps with an NCSG). within_ncsg,i The calculated / derived CSSF is determined according to intra The value is used to scale or adjust the period for PSS / SSS detection, the period for time index detection, and / or the measurement period for intra-frequency measurements with or without MG (see, e.g., [TS38133] §§ 9.2.5, 9.2.6, 9.10).

[0023] For inter-frequency measurements, the parameter CSSF inter shall be used for measurements made outside of the MG or NCSG (e.g., when the inter-frequency SMTC does not fully overlap or only partially overlaps with the MG) as discussed herein and / or in [TS38133] §9.1.5.1. outside_gap,i CSSF as discussed herein and / or in [TS38133] §9.1.5.2 for measurements made within the MG (e.g., when the inter-frequency SMTC fully overlaps with the MG). within_gap,ior (e.g., when an inter-frequency SMTC completely overlaps with an NCSG) for measurements made within an NCSG, the CSSF as discussed herein and / or in [TS38133] §9.1.5.x. within_ncsg,i The CSSF is then calculated / derived inter The value is used to scale or adjust the period for PSS / SSS detection, the period for time index detection, and / or the measurement period for intra-frequency measurements with or without MG (see, e.g., [TS38133] §§ 9.3.4, 9.3.5, 9.3.9, and 9.10).

[0024] When simultaneous MGs are configured by the network (e.g., RAN 104 or RAN node 114), according to UE capabilities, the term union of simultaneous MGs in the following discussion refers to the undropped MG opportunities from all configured MG patterns after considering MG collisions as specified in Section 9.1.8.3 of [TS38133]. The term associated MGs within a simultaneous MG in the following sections refers to the undropped MG opportunities associated by MOi after considering MG collisions as specified in Section 9.1.8.3 of [TS38133].

[0025] [1.4.1. Monitoring multiple layers outside the gap] For a UE 102 that supports simultaneous gaps and for which simultaneous gaps are configured, the carrier-specific scaling factor CSSF of MOi outside_gap,iis derived and is used for the following measurement types: SSB-based intra-frequency measurements without MG in Clause 9.2.5 of [TS38133] and Clause 9.2A.5 of [TS38133] when none of the SMTC opportunities for this intra-frequency MO are overlapped by MG or a union of simultaneous MGs; SSB-based intra-frequency measurements without MG in Clause 9.2.5 of [TS38133] and Clause 9.2A.5 of [TS38133] when some of the SMTC opportunities for this intra-frequency MO are overlapped by MG or a union of simultaneous MGs; CSI-RS-based intra-frequency measurements in Clause 9.10.2 of [TS38133] when none of the CSI-RS resources for L3 measurements for this intra-frequency MO are overlapped by MG or a union of simultaneous MGs; and CSI-RS-based intra-frequency measurements in Clause 9.10.2 of [TS38133] when all of the CSI-RS resources for L3 measurements for this intra-frequency MO are overlapped by MG or a union of simultaneous MGs. This applies to CSI-RS based intra-frequency measurements in clause 9.10.2, SSB based inter-frequency measurements without MG in clause 9.3.9 of [TS38133] when none of the SMTC opportunities of this inter-frequency MO are overlapped by an MG or a union of simultaneous MGs if the UE 102 supports interFrequencyMeas-NoGap-r16 and the flag interFrequencyConfig-NoGap-r16 is configured by the network, and / or SSB based inter-frequency measurements without MG in clause 9.3.9 of [TS38133] when some of the SMTC opportunities of this inter-frequency MO are overlapped by an MG or a union of simultaneous MGs if the UE 102 supports interFrequencyMeas-NoGap-r16 and the flag interFrequencyConfig-NoGap-r16 is configured by the network.

[0026] Otherwise, the carrier-specific scaling factor CSSF of MOi outside_gap,iis derived and is used for the following measurement types: SSB-based intra-frequency measurements without MG in Clause 9.2.5 of [TS38133] and Clause 9.2A.5 of [TS38133] when none of the SMTC opportunities for this intra-frequency MO are overlapped by MG or simultaneous MG; SSB-based intra-frequency measurements without MG in Clause 9.2.5 of [TS38133] and Clause 9.2A.5 of [TS38133] when some of the SMTC opportunities for this intra-frequency MO are overlapped by MG or simultaneous MG; and NR measurements configured by an E-UTRAN PCell on an NR serving carrier for UEs in E-UTRA-NR dual connectivity operation. SSB-based inter-RAT MO (SSB is fully included in the active BWP of the UE 102 and none of the SMTC opportunities of this inter-RAT MO are overlapped or partially overlapped by MG or simultaneous MG), CSI-RS-based intra-frequency measurement in clause 9.10.2 of [TS38133] when none of the CSI-RS resources for L3 measurements of this intra-frequency MO are overlapped by MG or simultaneous MG, CSI-RS-based intra-frequency measurement in clause 9.10.2 of [TS38133] when all of the CSI-RS resources for L3 measurements of this intra-frequency MO are overlapped by MG or simultaneous MG, and when the UE 102 performs interFrequencyMeas- If the UE 102 supports NoGap-r16 and the flag interFrequencyConfig-NoGap-r16 is configured by the network, SSB-based inter-frequency measurements without MG in clause 9.3.9 of [TS38133] when none of the SMTC opportunities of this inter-frequency MO are overlapped by a MG or simultaneous MG; if the UE 102 supports interFrequencyMeas-NoGap-r16 and the flag interFrequencyConfig-NoGap-r16 is configured by the network, SSB-based inter-frequency measurements without MG in clause 9.3.9 of [TS38133] when some of the SMTC opportunities of this inter-frequency MO are overlapped by a MG or simultaneous MG.The SSB-based inter-frequency measurements without MG in Clause 9, for UEs in E-UTRA-NR dual connectivity operation, apply to NR SSB-based inter-RAT MO configured by the E-UTRAN PCell on the NR serving carrier (where the SSB is fully included in the UE's 102 active BWP and none of the SMTC opportunities for this inter-RAT MO are overlapped or partially overlapped by the MG), and / or intra-frequency RSSI and channel occupancy measurements without MG on carriers covered by CCA when the SMTC and RMTC overlap and the RMTC does not fully overlap with the MG. The UE 102 is expected to perform this MOi measurement only outside of the MG.

[0027] The number of frequency layers for SSB measurements includes the total number of MOs with ssb-ConfigMobility configured, or the total number of MOs with no ssb-ConfigMobility configured but with csi-rs-ResourceConfigMobility configured in associatedSSB.

[0028] If multiple MOs have the same ssbfrequency, smtc1, smtc2, and ssbSubcarrierSpacing, the multiple MOs are counted as one SSB frequency layer. If there is higher layer signaling in [TS38331] for smtc2, and smtc1 completely overlaps with the MG and smtc2 partially overlaps with the MG, the CSSF outside_gap,i and CSSF outside_gap,i The requirements derived from are not specified.

[0029] CSSF in Sections 9.2.5.1, 9.2.5.2, and 9.10.2 of [TS38133] outside_gap,i When MG is not provided, the UE cell identity and measurement period are derived based on the T specified in clause 9.3.8 of [TS38133]. measure_SFTD1 may be extended to overlapping MOs.

[0030] The requirements in this section are: (i) all CCs without MG in FR2 and SMTC on the inter-frequency layer have the same offset and one of the following conditions is met: if smtc2 is configured on any FR2 CC, all CCs have the same configuration for smtc1, all CCs configured with smtc2 have the same configuration for smtc2; if smtc2 is not configured on any FR2 CC, the total number of different SMTC periods on all serving CCs without MG and on the inter-frequency layer does not exceed four; and / or (ii) the starting point of the first 5 ms window for CSI-RS measurements as defined in Section 9.10.1 on all CCs in FR2 is the same and one of the following conditions is met: if smtc2 is configured on any FR2 CC, all CCs have the same configuration for smtc1, all CCs configured with smtc2 have the same configuration for smtc2; if smtc2 is not configured on any FR2 CC, the total number of different SMTC periods on all serving CCs without MG and on the inter-frequency layer does not exceed four. This rule applies if the following conditions are met: if any CSI-RS resources are configured in the second 5 ms window for CSI-RS measurements as defined in Section 9.10.1 on a CC, all CCs that have CSI-RS resources in only the first 5 ms window have the same CSI-RS resource periodicity, all CCs that have CSI-RS resources in both the first and second 5 ms windows have the same CSI-RS resource periodicity, and if no CSI-RS resources are configured in the second 5 ms window for CSI-RS measurements as defined in Section 9.10.1 on any FR2 CC, the total number of different CSI-RS resource periodicities on all serving CCs does not exceed 3. In some examples, if a UE 102 is configured with more than four different SMTC periodicities on an FR2 serving carrier, the CSSF in Sections 9.2.5.1 and 9.2.5.2 of [TS38133] outside_gap,i A longer delay can be assumed for cell identification and measurement periods derived based on the following: The longer delay applies to the FR2 intra-frequency MO with the longest SMTC period / periods.

[0031] In legacy 3GPP standards, CSSFs for SSB-based and CSI-RS-based L3 measurements performed outside and inside the gap are defined for FR1+FR2 NR-DC (e.g., CSSFs 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 112, 113, 114, 115, 120, 121, 122, 123, 124, 125, 130, 13 outside_gap,iand CSSF within_gap,i ).

[0032] 1.4.1.1. NR-DC Mode: Carrier-Specific Scaling Factors for SSB- and CSI-RS-Based L3 Measurements Performed Outside the Gap In FR1+FR1 NR-DC, two searchers are assumed: the first searcher is dedicated to the Primary CC (PCC), half of the second searcher is dedicated to the Primary Secondary CC (PSCC), and the other half of the second searcher is shared between the FR1 Secondary CC (SCC) and the FR1 SCC. There are two scenarios for SCC measurements on the FR1 PSCell: (1) intra-frequency CA on the PSCell, and (2) inter-frequency CA without gap on the PSCell. Measurements are shared between the PCell SCC and the PSCell SCC. Therefore, the CSSF for FR1+FR1 outside_gap,i shall be as shown in Table 1.4.1.1-1 and / or Table 1.4.1.1-2.

[0033] For a UE 102 configured for NR-DC operation, the carrier-specific scaling factor CSSF for intra-frequency SSB-based measurements, inter-frequency SSB-based measurements performed outside the measurement gap, and intra-frequency CSI-RS-based L3 measurements outside_gap,i is specified in Table 1.4.1.1-1 and / or Table 1.4.1.1-2. [Table 2] [Table 3]

[0034] [1.4.2. Monitoring multiple layers within the gap] For a UE 102 that supports simultaneous gaps and for which simultaneous gaps are configured, the carrier-specific scaling factor CSSF of MOi within_gap,iis derived and the following measurement types for the relevant MGs: SSB-based intra-frequency MOs without MGs in Clause 9.2.5 of [TS38133] and Clause 9.2A.5 of [TS38133], when all of the SMTC opportunities for this intra-frequency MO overlap with the relevant MGs in the MG or simultaneous MGs, or some of the SMTC opportunities for this intra-frequency MO overlap with the relevant MGs and all of the SMTC opportunities for this intra-frequency MO overlap with the union of all MGs; SSB-based intra-frequency MO using MG in Section 9.2A.6, CSI-RS-based inter-frequency measurement in Section 9.10.3 of [TS38133] when the CSI-RS resources for L3 measurements of this inter-frequency MO are overlapped by MG or by an associated MG in a simultaneous MG, CSI-RS-based inter-frequency measurement in Section 9.10.3 of [TS38133] when the CSI-RS resources for L3 measurements of this inter-frequency MO are partially overlapped by MG or by an associated MG in a simultaneous MG, L3 measurements of this intra-frequency MO CSI-RS-based intra-frequency measurements in clause 9.10.2 of [TS38133], when all CSI-RS resources for L3 measurements of this intra-frequency MO partially overlap with the associated MG and all CSI-RS resources for L3 measurements of this intra-frequency MO overlap with the union of configured simultaneous MGs, or SSB-based inter-frequency MO using MG in clause 9.3.4 of [TS38133], when all SMTC opportunities of this inter-frequency MO overlap with the MG or associated MGs in the simultaneous MG, or when some of the SMTC opportunities of this inter-frequency MO overlap with the associated MG. SSB-based inter-frequency MO without MG for interFrequencyMeas-NoGap capable UE 102 in clause 9.3.9 of [TS38133] when the UE 102 overlaps with the MG and all SMTC opportunities of this inter-frequency MO overlap with the union of all MGs, or some of the SMTC opportunities of this inter-frequency MO are overlapped by the MG or related MGs in a simultaneous MG, and the flag interFrequencyConfig-NoGap-r16 is not configured by the network.This applies to NR PRS-based measurements for positioning in Section 9 and / or E-UTRA inter-RAT MO in Sections 9.4.2 and 9.4.3 of [TS38133].

[0035] Otherwise, the carrier-specific scaling factor CSSF of MOi derived in this chapter within_gap,iis the following measurement type: SSB-based intra-frequency MO without MG in clauses 9.2.5 of [TS38133] and 9.2A.5 of [TS38133] when all of the SMTC opportunities for this intra-frequency MO are overlapped by MG or simultaneous MG; SSB-based intra-frequency MO with MG in clauses 9.2.6 of [TS38133] and 9.2A.6 of [TS38133]; CSI-RS-based inter-frequency measurement in clause 9.10.3 of [TS38133] when the CSI-RS resources for L3 measurements for this inter-frequency MO are overlapped by MG or simultaneous MG; CSI-RS-based inter-frequency measurement in clause 9.10.3 of [TS38133] when the CSI-RS resources for L3 measurements for this inter-frequency MO are partially overlapped by MG or simultaneous MG; SSB-based inter-frequency MO with MG in clause 9.3.4 of [TS38133]; SMTC opportunities for this inter-frequency MO SSB-based inter-frequency MO without MG for interFrequencyMeas-NoGap capable UEs 102 in Section 9.3.9 of [TS38133] when all of the RMTC opportunities for this inter-frequency MO are overlapped by MG or simultaneous MG, or when some of the SMTC opportunities for this inter-frequency MO are overlapped by MG or simultaneous MG but the flag interFrequencyConfig-NoGap-r16 is not configured by the network; intra-frequency RSSI / CO measurement with MG in Section 9.2A7 of [TS38133]; intra-frequency RSSI / CO measurement without MG in Section 9.2A.7 when all of the RMTC opportunities for this intra-frequency RSSI / CO measurement are overlapped by MG; inter-frequency RSSI / CO measurement in Sections 9.3A.8 of [TS38133] and 9.3A.9 of [TS38133]; and E-UTRA in Sections 9.4.2 of [TS38133] and 9.4.3 of [TS38133]. Inter-RAT MO, NR PRS-based measurements for positioning in Section 9.9 of [TS38133], Sections 9.4.4 and 9.4 of [TS38133].E-UTRA inter-RAT reference signal time difference (RSTD) and Enhanced Cell ID (E-CID) measurements in Section 5, for a UE 102 in E-UTRA-NR dual connectivity operation, include NR SSB-based inter-RAT MO configured by an E-UTRAN PCell on an NR serving carrier (see, e.g., 3GPP TS36.133 §8.17.4) (the SSB is not fully included in the UE 102's active BWP or all SMTC opportunities for this inter-RAT MO are overlapped by MG), NR SSB-based inter-RAT MO configured by an E-UTRAN PCell on an NR non-serving carrier (see, e.g., 3GPP TS36.133 §8.17.4), E-UTRAN PCell (see, e.g., 3GPP TS36.133 §8.17.3) and E-UTRAN PSCell (see, e.g., 3GPP This applies to E-UTRAN inter-frequency MOs configured by the E-UTRAN PCell (see, e.g., 3GPP TS36.133 §8.19.3), E-UTRAN inter-frequency RSTD measurements configured by the E-UTRAN PCell (see, e.g., 3GPP TS36.133 §8.17.15), UTRA inter-RAT MOs configured by the E-UTRAN PCell (see, e.g., 3GPP TS36.133 §8.17.5 to 8.17.12), and / or GSM inter-RAT measurements configured by the E-UTRAN PCell (see, e.g., 3GPP TS36.133 §§8.17.13 and 8.17.14).

[0036] The UE 102 is assumed to measure this MOi only within the MG, or, if simultaneous MGs are configured, only within the associated MG. If the UE 102 is configured with simultaneous MGs and an association between an MOi and a particular MG is provided, the requirements are defined assuming that the UE 102 measures this MOi within the associated MG.

[0037] If there is higher layer signaling in [TS38331] for smtc2, smtc1 completely overlaps with MG, and smtc2 partially overlaps with MG, then CSSFwithin_gap,i and CSSF outside_gap,i The requirements derived from are not specified.

[0038] The number of SSB layers should include SSBs for mobility and SSBs as associated SSBs for CSI-RS mobility. ssbfrequency is counted only once if the ssbfrequency and associated SSB for mobility are the same, or if the ssbfrequency and smtc in multiple MOs are the same. In some instances, how to add a layer corresponding to the associated SSB for MOs where only CSI-RS measurements are configured is a topic for future study (FFS).

[0039] 1.4.2.1. NR-DC: Carrier-specific scaling factors for SSB-based and CSI-RS-based L3 measurements performed within the gap When more than one MO is monitored in a MG, the carrier-specific scaling factor of the target MO with index i is given by CSSF within_gap,i When NR PRS-based measurements for positioning are configured on one or more positioning frequency layers in a MG, the CSSF for a target measurement on a positioning frequency layer with index i is given by CSSF within_gap,i and is derived as described below and / or in Section 9.1.5.2.4 of [TS38133]. The NR positioning measurement requirements for long period measurements apply when all PRS resources within a PFL are configured with a period longer than 160 ms.

[0040] For a UE 102 that supports gapping per FR, the CSSF used to derive the measurement requirements for each MOi measured based on the effective MG repetition period (MGRP) defined in clause 9.1.2 of [TS38133]. within_gap,i is 2*N with_CSI-RS +N SSB_onlywhere N with_CSI-RS is the number of MOs in which both SSB and CSI-RS based L3 measurements are configured in the same FR as MOi, or the number of MOs in which only CSI-RS based L3 measurements are configured, and N SSB_only is the number of MOs for which only SSB-based L3 measurements are configured at the same FR as MOi.

[0041] MOi has a period Tprs>160ms, or has a period Tprs=160ms but prs-ShiftInfo-r9 is configured, or E-UTRA RSTD measurement T available_PRS,i If the long period measurement is any of the NR measurements of positioning frequency layer i with >160 ms (T available_PRS,i are defined in clauses 9.9.2.5, 9.9.3.5 and 9.9.4.5 of [TS38133] for RSTD, PRS-RSRP and UE Rx-Tx time difference measurements, respectively), CSSF within_gap,i = 1. Otherwise, the CSSF for other MOs (including E-UTRA RSTD measurements with period Tprs = 160 ms) within_gap,i Participated in the GAP competition and CSSF within_gap,i is derived as follows:

[0042] When multiple positioning frequency layers are configured, for each positioning frequency layer i, CSSF within_gap,i is derived in the following steps assuming that no other positioning frequency layers are configured: For each RRM frequency layer i, CSSF within_gap,i is derived as follows: Intermediate CSSF within_gap,i,k is derived in the following steps assuming that only the positioning frequency layer k is configured, and CSSF within_gap,i =max(CSSF within_gap,i,k ) where k=0...K-1, and K is the number of configured positioning frequency layers.

[0043] For each MGj that is not used for RSTD measurements with periodicity Tprs > 160 ms or periodicity Tprs = 160 ms but for which prs-MutingInfo-r9 is configured within any 160 ms period, count the total number of NR PRS measurements on all positioning frequency layers and intra-frequency and inter-frequency / inter-RAT MOs that are candidates for measurement within gap j (e.g., MGj). An NR MO configured with SSB measurements is a candidate for measurement within a gap if its SMTC period is fully covered by the MGL except for RF switching times. For intra-frequency NR MOs, if higher layers in [TS38331] signaling for smtc2 are configured, the assumed period of the SMTC opportunity corresponds to the value of the higher layer parameter smtc2; otherwise, the assumed period of the SMTC opportunity corresponds to the value of the higher layer parameter smtc1. An NR MO configured with CSI-RS measurements is a candidate for measurement within a gap if the window limiting all CSI-RS resources is fully covered by the MGL except for RF switching times. A positioning frequency layer is counted as a candidate for an MG opportunity if at least one PRS resource on that positioning frequency layer is fully covered by the MGL except during RF switching times.

[0044] For UEs 102 that support and are configured with per-FR gaps, counting is done per-FR, and for UEs 102 that are configured with per-UE gaps, counting is done per-UE. For UEs that support and are configured with per-FR gaps, the CSSF requirement does not apply when NR PRS measurements in one FR gap collide with SSB / CSI-RS / PRS measurements in another FR gap in the time domain.

[0045] Currently, if the number of NR PRS measurements and configured inter-frequency and inter-RAT measurement objects on all positioning frequency layers is non-zero and the UE 102 is configured with per-UE gaps, or if the UE 102 is configured with per-FR gaps, the FR1 and FR2 intra-frequency MOs belong to Group A, and up to one NR PRS measurement and inter-frequency and inter-RAT MOs on any one positioning frequency layer belong to Group B, and M groupA,i,j is the candidate MOi measured in gap j, including both SSB-based and CSI-RS-based MOi in FR1 frequency band. intra-FR1,i,j Number of MO M in FR2 frequency intra-FR2,i,j otherwise, M groupA,i,j is equal to 0, and / or M groupBi,j is the number of NR inter-frequency layers, including both SSB-based and CSI-RS-based EUTRA inter-RAT and UTRA inter-RAT MOs and up to one frequency layer, that are candidates measured in gap j, for which MOi is also a candidate; otherwise, M groupB,i,j is equal to 0.

[0046] Currently, if the number of NR PRS measurements on all positioning frequency layers and the number of configured inter-frequency and inter-RAT MOs are zero, and the UE 102 is configured with per-UE gaps, the FR1 intra-frequency MOs belong to group A, the FR2 intra-frequency MOs belong to group B, and the M groupA,i,j is the candidate MOi measured in gap j, including both SSB-based and CSI-RS-based MOi in FR1 frequency band. intra-FR1,i,j otherwise, M groupA,i,j is equal to 0, and / or M groupBi,j is the candidate MOi measured in gap j, including both SSB-based and CSI-RS-based MOi in the FR2 frequency band. intra-FR2,i,j otherwise, M groupB,i,j is equal to 0.

[0047] Furthermore, the parameter M tot,i,jis the total number of MOs in group A and group B that are candidates measured in gap j, where MOi is also a candidate; otherwise, M tot,i,j is equal to 0. In other words, M tot,i,j =M groupA,i,j +M groupB,i,j is.

[0048] For each MGj used in the long-period measurements defined above, Mi ntra,i,j =M inter,i,j =M tot,i,j = 0. Carrier-specific scaling factor CSSF within_gap,i is given by (A) and (B).

[0049] (A) If measGapSharingScheme is equal distribution, CSSF within_gap,i =max(ceil(R i ×M tot,i,j )), where j=0...(160 / MGRP)-1.

[0050] (B) If measGapSharingScheme is not an equal distribution, a) MOi is the MO of Group A, and CSSF within_gap,i is the maximum of the following: i)M groupB,i,j ceil(R i ×K intra ×M groupA,i,j ), where j=0...(160 / MGRP)-1 ii) M groupB,i,j = 0 in the gap where ceil(R i ×M groupA,i,j ), where j=0...(160 / MGRP)-1 b) MOi is the MO of Group B, and CSSF within_gap,i is the maximum of the following: i)M groupA,i,j ceil(R i ×K inter ×M groupBi,j ), where j=0...(160 / MGRP)-1 ii) M groupA,i,j = 0 in the gap where ceil(R i ×M groupB,i,j ), where j=0...(160 / MGRP)-1.

[0051] In (A) and (B), R i is the maximum ratio of the number of MGs for which MOi is a candidate to be measured to the number of MGs for which MOi is a candidate and which are not used for long-period measurements as defined above. Furthermore, "ceil" may represent a ceiling function that rounds up a number to the next integer if the number is not already an integer, and "max" may represent a maximum function that takes a set of values as input and returns the maximum value from the set.

[0052] From the measGapSharingScheme formula (e.g., (A) and (B) above), the CSSF within_gap is a function of two factors: the first factor is the number of candidates measured in group A or group B, and the ratio K between the two pools. intra / K inter (See, for example, Equations 2.1-1 and 2.1-2 below.) The method for classifying / grouping PCell SCCs and PSCell SCCs into Group A and Group B is as follows.

[0053] In some embodiments, the grouping scheme for FR1+FR1 NR-DC includes grouping or including intra-frequency MOs for FR1 PCell and FR1 PSCell in Group A and grouping or including up to one NR PRS measurement and inter-frequency and inter-RAT MOs on any one positioning frequency layer in Group B if the number of NR PRS measurements and configured inter-frequency and inter-RAT MOs on all positioning frequency layers is non-zero and the UE 102 is configured with per-UE gaps or if the UE 102 is configured with per-FR gaps.

[0054] Additionally or alternatively, the grouping scheme for FR1+FR1 NR-DC includes grouping or including intra-frequency MOs of FR1 PCells in group A and grouping or including intra-frequency MOs of FR1 PSCells in group B when the number of NR PRS measurements on all positioning frequency layers and the number of configured inter-frequency and inter-RAT measurement objects is zero and the UE 102 is configured with per-UE gapping or per-FR gapping.

[0055] Additionally or alternatively, the grouping scheme for FR1+FR1 NR-DC includes grouping or including intra-frequency MOs of the FR1 PCell into one group (e.g., group A or group B) and grouping or including intra-frequency MOs of the FR1 PSCell into the same group (e.g., group A or group B) when the number of NR PRS measurements on all positioning frequency layers and the configured inter-frequency and inter-RAT measurement objects is zero and the UE 102 is configured with per-UE gaps. Additionally or alternatively, no further classification of MOs into group A and / or group B is required (e.g., both group A and group B are combined into one group).

[0056] Additionally or alternatively, the grouping scheme for FR1+FR1 NR-DC includes grouping or including FR1 intra-frequency MOs associated with MCGs in group A and grouping or including FR1 intra-frequency MOs associated with SCGs in group B when the number of NR PRS measurements on all positioning frequency layers and the number of configured inter-frequency and inter-RAT measurement objects is zero and the UE 102 is configured with per-UE gaps.

[0057] Based on the above grouping scheme for FR1+FR1 NR-DC, if the number of configured NR PRS measurements on all positioning frequency layers and inter-frequency and inter-RAT MOs is zero, and the UE 102 is configured with per-UE gaps, the FR1 intra-frequency MOs of the MCG belong to group A, the FR1 intra-frequency MOs of the SCG belong to group B, and the MCG belongs to group B.groupA,i,j is the intra-FR1 frequency MO associated with the MCG, including both SSB-based and CSI-RS-based, that is a candidate to be measured in gap j, for which measurement object i is also a candidate. intra-FR1,i,j otherwise, M groupA,i,j is equal to 0. M groupBi,j is the intra-FR1 frequency MO M associated with the SCG, including both SSB-based and CSI-RS-based, that is a candidate to be measured in gap j, for which measurement object i is also a candidate. intra-FR1,i,j otherwise, M groupB,i,j is equal to 0.

[0058] Additionally or alternatively, the above grouping scheme may be modified for FR1+FR2 NR-DC as follows: The FR2 intra-frequency MOs of the SCG belong to group B for FR1+FR2 NR-DC, and M groupBi,j is the FR2 intra-frequency MO M including both SSB and CSI-RS based that are candidates to be measured in gap j, for which measurement object i is also a candidate. intra-FR2,i,j otherwise, M groupB,i,j is equal to 0.

[0059] 2. Cellular Network Aspects 1 illustrates a network 100 in accordance with various embodiments. Network 100 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, example embodiments are not limited in this respect, and the described examples may apply to other networks that would benefit from the principles described herein, such as future 3GPP systems, etc.

[0060] The network 100 includes a UE 102. The UE 102 is any mobile or non-mobile computing device designed to communicate over a wireless connection with a RAN 104. The UE 102 is communicatively coupled to the RAN 104 by a Uu interface, which may be applicable to both LTE and NR systems. Examples of UE 102 include smartphones, tablet computers, wearable devices (e.g., smart watches, fitness trackers, smart glasses, smart clothing / fabrics, head-mounted displays, smart shows, etc.), desktop computers, workstations, laptop computers, in-vehicle infotainment systems, in-vehicle entertainment systems, instrument clusters, head-up display (HUD) devices, on-board diagnostic devices, dash-top mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) devices, Internet of Things (IoT) devices, smart appliances, flying drones or unmanned aerial vehicles (UAVs), ground drones or autonomous vehicles, robots, electronic signage, single-board computers (SBCs), and the like. The term "computer" includes, but is not limited to, any type of computing device such as a USB 3.0 port (e.g., a Raspberry Pi, an Arduino, an Intel Edison, etc.), a plug computer, and / or any of those discussed herein.

[0061] The network 100 may include a set of UEs 102 directly coupled to each other via D2D, ProSe, PC5, and / or sidelink (SL) interfaces, and / or any other suitable interfaces, such as any of those discussed herein. In a 3GPP system, SL communication involves communication between two or more UEs 102 using 3GPP techniques without traversing a network node. These UEs 102 may be M2M / D2D / MTC / IoT devices and / or vehicular systems communicating using an SL interface, which may include, for example, one or more SL logical channels (e.g., a Sidelink Broadcast Control Channel (SBCCH), a Sidelink Control Channel (SCCH), and a Sidelink Traffic Channel (STCH)), one or more SL transport channels (e.g., a Sidelink Shared Channel (SL-SCH) and a Sidelink Broadcast Channel (SL-BCH)), and one or more SL physical channels (e.g., a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Feedback Channel (PSFCH), a Physical Sidelink Broadcast Channel (PSBCH), etc.). The UEs 102 may perform blind decoding attempts on the SL channels / links in accordance with various examples herein.

[0062] The UE 102 may communicate with the AP 106 via an over-the-air (OTA) connection. The AP 106 manages a WLAN connection that may function to offload some or all network traffic from the RAN 104. The connection between the UE 102 and the AP 106 may conform to any IEEE 802.11 protocol. Furthermore, the UE 102, the RAN 104, and the AP 106 may utilize cellular-WLAN aggregation / integration (e.g., LWA / LWIP). Cellular-WLAN aggregation may include the UE 102 being configured by the RAN 104 to utilize both cellular radio resources and WLAN resources.

[0063] The RAN 104 includes one or more network access network nodes (NANs) 114, each of which terminates the air interface for the UE 102 by providing access stratum (AS) protocols, including RRC, PDCP, RLC, MAC, and PHY protocols. Thus, the NANs 114 enable data / voice connectivity between the CN 140 and the UE 102. The NANs 114 may be macrocell base stations, or low-power base stations providing femtocells, picocells, or other similar cells with smaller coverage areas, lower user capacities, or higher bandwidths compared to macrocells, or some combination thereof. Each NAN 114 manages one or more cells, cell groups, component carriers (CCs) in carrier aggregation (CA), etc., to provide the UE 102 with an air interface for network access. The UE 102 may simultaneously connect to a set of cells provided by the same or different NANs 114. For example, the UE 102 and the RAN 104 may use CA to enable the UE 102 to connect with a set of CCs, each corresponding to a PCell, SCell, PSCell, SpCell, etc. In a dual connectivity (DC) scenario, the first NAN 114 may be a master node providing an MCG, and the second NAN 114 may be a secondary node providing an SCG. The first / second NANs 114 may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0064] The NG-RAN 104 (or individual RAN nodes 114) provides a 5G-NR air interface (Uu interface) with the following characteristics: variable subcarrier spacing (SCS), Cyclic-Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) for DL, CP-OFDM and Discrete Fourier Transform-Spread (DFT-s)-OFDM for UL, Polar, Repetitive, Simplex, and Reed-Muller codes for control, and LDPC for data. The 5G / NR air interface includes physical channels and physical signals. A UL physical channel corresponds to a set of resource elements (REs) that carry information originating from higher layers. Examples of UL physical channels include the physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), and physical random access channel (PRACH). A DL physical channel corresponds to a set of REs that carry information originating from higher layers. Examples of DL physical channels include the physical downlink shared channel (PDSCH), the physical broadcast channel (PBCH), and the physical downlink control channel (PDCCH). UL physical signals are used by the physical layer but do not carry information originating from higher layers.Examples of UL physical signals (or reference signals (RS)) include a demodulation reference signal (DMRS), a phase-tracking reference signal (PTRS), and a sounding reference signal (SRS). DL physical signals correspond to a set of resource elements used by the physical layer but do not carry information originating from higher layers. Examples of DL physical signals (or RS) include DMRS, PTRS, a positioning reference signal (PRS), a channel-state information reference signal (CSI-RS), a synchronization signal block (SSB), a primary synchronization signal (PSS), and a secondary synchronization signal (SSS). Additional or alternative physical channels and / or physical signals may be defined and / or used. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and tracking reference signals for time tracking. The 5G-NR air interface may operate in the FR1 band, which includes the sub-6 GHz band, or the FR2 band, which includes the band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may also include SSB, which is a region of the downlink resource grid that includes PSS / SSS / PBCH. The 5G-NR air interface may utilize bandwidth parts (BWPs) for various purposes, such as dynamic adaptation of the SCS.

[0065] The NG-RAN 104 supports multi-radio DC (MR-DC) operation, and the UE 102 is configured to utilize radio resources provided by two different schedulers located in at least two different NG-RAN nodes 114 connected via a non-ideal backhaul, one NG-RAN node 114 providing NR access and the other NG-RAN node 114 providing either E-UTRA or NR access. One node functions as a master node (MN) and the other functions as a secondary node (SN), and the MN and SN are connected via a network interface, with at least the MN connected to a core network (e.g., CN 140). In some implementations, the MN and / or SN can operate using shared spectrum channel access. Further details of MR-DC operations, including conditional PSCell addition (CPA) and conditional PSCell change (CPC), can be found in 3GPP TS36.300 v17.5.0(2023-07-06) (“TS36300”), TS38300, and 3GPP TS37.340 v17.5.0(2023-06-30), the contents of each of which are incorporated herein by reference in their entirety. The NG-RAN 104 also supports Layer 1 (L1) and / or Layer 2 (L2) based inter-cell mobility, as discussed in U.S. patent application Ser. No. 18 / 352,810, filed July 14, 2023, the contents of which are incorporated herein by reference in their entirety.

[0066] As described in more detail below, the UE 102 can be configured to perform / collect signal / cell measurements and provide measurement reports to one or more NANs 114. The measurement report includes, for example, the measId of the associated measurement configuration that triggered the report, cell and / or beam measurement quantities to be included in the measurement report as configured by the network, and / or other information as discussed herein. Additionally or alternatively, each measurement report can be tagged with a timestamp and / or the location where the measurement was performed / collected. In any of the examples discussed herein, any suitable measurement collection and / or reporting mechanism may be used to collect and report measurements, such as, for example, data marking, sequence numbering, packet tracing, signal measurement, data sampling, and / or time stamping techniques. Measurement collection may be based on the occurrence of an event that triggers the collection of data. Additionally or alternatively, measurement collection may occur at the start or end of an event. Data collection may be continuous, discontinuous, and / or have start and stop times. Measurement collection and / or reporting techniques / mechanisms may be specific to a hardware (HW) configuration / implementation or may be non-HW specific and / or based on various SW parameters (e.g., OS type and version, wireless platform, etc.). By way of example, the measurement and reporting procedures performed by the UE 102 may be in accordance with 3GPP TS38.211 v17.5.0(2023-06-26), 3GPP TS38.212 v17.5.0(2023-03-30), 3GPP TS38.213 v17.6.0(2023-06-26), 3GPP TS38.214 v17.6.0(2023-06-26), [TS38215], 3GPP TS38.101-1 v18.2.0(2023-06-30), 3GPP TS38.104 v18.2.0(2023-06-30), and / or 3GPP TS38.133 v18.2.0(2023-06-30), [TS38331], the entire contents of each of which are incorporated herein by reference.

[0067] Examples of measurements that are collected and included in the measurement report are: bandwidth (BW) (or channel BW), network or cell load, latency, jitter, round trip time (RTT), number of interrupts, out-of-order delivery of data packets, transmit power, bit error rate (BER), block error rate (BLER), packet error rate (PER), packet loss rate, packet reception rate (PRR), data rate, peak data rate, end-to-end (e2e) delay, signal-to-noise ratio (SNR), signal-to-noise and interference ratio (SINR), signal-plus-noise-plus-distortion to noise-plus-distortion (SINAD) ratio, carrier-to-interference plus noise ratio (CINR). ratio), Additive White Gaussian Noise (AWGN), total received power density (Io) (e.g., including signal and interference as measured at the UE antenna connector or radiating interface boundary), power spectral density (Ioc) of a band-limited noise source (a simulation of interference from a cell, not defined in the test procedure) as measured at the UE antenna connector or radiating interface boundary (e.g., integrated over a noise bandwidth equal to the chip rate and normalized to the chip rate), received power spectral density (Iot) of the total noise and interference for a specific RE as measured at the UE antenna connector or radiating interface boundary (e.g., power integrated over the RE and normalized to the subcarrier spacing), power spectral density of a white noise source (N oc) (e.g., average power per RE normalized to subcarrier spacing), simulation of interference from cells not defined in the test procedure, as measured at the UE antenna connector or radiating interface boundary, energy per bit to noise power density ratio (E b / N0), energy-to-interference power density ratio per chip (E c / I0), energy-to-noise power density ratio per chip (E c / N0), peak-to-average power ratio (PAPR), reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), received channel power indicator (RCPI), received signal to noise indicator (RSNI), received signal code power (RSCP), average noise plus interference (ANPI), GNSS timing of the cell frame, GNSS code measurements, GNSS carrier phase measurements and / or accumulated delta range (ADR). range), received energy per RE during the useful portion of the symbol (e.g., power normalized to the subcarrier spacing) (in some examples excluding cyclic prefixes at the UE antenna connector or radiating interface boundary), timing advance, timing offset, channel interference measurement, thermal noise power measurement, received interface power measurement, power histogram measurement, channel load measurement, station characteristics, and / or variations of any of these.3GPP TS36.214 v17.0.0(2022-03-31), 3GPP TS38.215 v17.3.0(2023-03-30)("[TS38215]"), 3GPP TS38.314 v17.3.0(2023-06-30), 3GPP TS28.552 v18.3.0(2023-06-27)(``[TS28552]''), 3GPP TS32.425 v17.1.0(2021-06-24)(``[TS32425]''), 3GPP TS32.401 v17.0.0(2022-04-01) and IEEE Standard for Information Technology--Telecommunications and Information Exchange between Systems-Local and Metropolitan Area Additional or alternative measurements may also be collected and reported, such as any of the measurement types discussed in Networks--Specific Requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, IEEE Std 802.11-2020, pp. 1-4379 (26 Feb 2021) ("IEEE80211"), the contents of each of which are incorporated herein by reference in their entirety. Additionally or alternatively, any of the above measurements (or combinations of measurements) may be collected by one or more NANs 114 and provided to edge compute nodes, NFs, and / or any other entities / elements discussed herein.

[0068] In some examples, the measurement is an NR intra-frequency measurement. The measurement is defined as an SSB-based intra-frequency measurement, provided that the center frequency of the SSB of the serving cell designated for the measurement is the same as the center frequency of the SSB of the neighboring cell, and the subcarrier spacing of the two SSBs is also the same. Even if an explicit neighbor list with physical layer cell identities is not provided, the UE 102 can identify new intra-frequency cells and perform SS-RSRP, SS-RSRQ, and SS-SINR measurements of the identified intra-frequency cells if carrier frequency information is provided by the PCell or PSCell. The UE 102 can perform intra-frequency SSB-based measurements with or without a MG (either legacy MG or Network Controlled Small Gap (NCSG)). Further aspects of NR intra-frequency measurements are described in §9.2 of [TS38133]. In some examples, the measurement is an NR inter-frequency measurement. Measurements are defined as SSB-based inter-frequency measurements when they are not defined as intra-frequency measurements as described above and / or in accordance with [TS38133] §9.2. The UE 102 can identify new inter-frequency cells and perform SS-RSRP, SS-RSRQ, and SS-SINR measurements of identified inter-frequency cells when carrier frequency information is provided by the PCell or PSCell, even if an explicit neighbor list with physical layer cell identities is not provided. The UE 102 can perform inter-frequency SSB-based measurements with or without a MG (either legacy MG or NCSG) in an active BWP. Further aspects of NR inter-frequency measurements are described in [TS38133] §9.3.

[0069] The signal / cell measurements and reports may be used to perform handover (HO) and / or conditional HO (CHO). HO and / or CHO can be performed within the same RAT (or RAN 104) and / or CN 140, or can involve a change of RAT (or RAN 104) and / or CN 140. To perform HO, the UE 102 receives a measurement configuration from a source cell (e.g., a cell provided by the RAN node 114), performs neighbor cell measurements according to the measurement configuration, and sends a measurement report to the network (e.g., the source cell) when an entry condition for at least one measurement event is met. The source cell then sends an HO command to the UE 102, and the UE 102 performs a random access channel (RACH) procedure to gain access to a target cell (e.g., another cell provided by the same or a different RAN node 114), which includes sending a random access (RA) preamble to the target cell and receiving an RA response from the target cell. The UE 102 then sends an HO Complete message to the target cell. In NR, the HO command is (or is included in) an RRCReconfiguration message, in which the masterCellGroup field includes a reconfigurationWithSync field, and the HO Complete message is (or is included in) an RRCReconfigurationComplete message. In CHO, to avoid delayed transmission (Tx) of the HO command, candidate target cells (e.g., one or more cells provided by one or more RAN nodes 114) and corresponding execution conditions can be configured for the UE 102 in advance. When the entry condition of at least one measurement event is met (e.g., the CHO execution condition is met), the UE 102 initiates execution of a conditional reconfiguration for the target cell by performing a RACH procedure and sending an RRCReconfigurationComplete message to the target cell.On the other hand, a set of multiple candidate target cells can be configured for the UE 102, and the UE 102 can select one of the target cells from the set of candidate target cells (e.g., more than one candidate target cell is configured) when a corresponding measurement event for the candidate cell is triggered.

[0070] The RAN node 114 may include a set of gNBs 114a. Each gNB 114a connects to a 5G-capable UE 102 using a 5G-NR air interface (Uu interface) having parameters and characteristics as discussed in [TS38300], among many other 3GPP standards. The RAN node 114 may also include a set of ng-eNBs 114b that connect to the UE 102 via a 5G Uu and / or LTE Uu interface. The gNBs 114a and ng-eNBs 114b connect to the 5G LTE 102 over respective NG interfaces, including an N2 interface, an N3 interface, and / or other interfaces. The gNBs 114a and ng-eNBs 114b are connected to each other over an Xn interface. Furthermore, the individual gNBs 114a are connected to each other via their respective Xn interfaces, and the individual ng-eNBs 114b are connected to each other via their respective Xn interfaces. The NG interface may be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface), which carries traffic data between nodes in the NG-RAN 114 and the UPF 148, and an NG control plane (NG-C) interface (e.g., N2 interface), which is a signaling interface between nodes in the NG-RAN 114 and the AMF 144. The Xn interface may be separated into a control / user plane interface, which allows the NAN 114 to communicate information related to handover (HO), data / context transfer, mobility, load management, interference coordination, etc.

[0071] One exemplary implementation is a "CU / DU split" architecture in which NAN114 is embodied as a gNB-Central Unit (CU) that is communicatively coupled to one or more gNB Distributed Units (DUs), each of which may be communicatively coupled to one or more Radio Units (RUs) (see, e.g., 3GPP TS38.300 v17.5.0 (2023-06-30) ("[TS38300]"), 3GPP TS38.401 v17.5.0 (2023-06-29) ("[TS38401]"), 3GPP TS38.410 v17.1.0 (2022-06-23) and 3GPP TS38.473 v17.5.0 (2023-06-29), the contents of each of which are incorporated by reference in their entirety). Any other type of architecture, arrangement, and / or configuration may be used. For example, in some implementations, the RAN 104, the CN 140, and / or the edge computing nodes (e.g., the server 138) may be separated into various functions, as discussed in U.S. Application No. 17 / 704,658, filed March 25, 2022 ("['658]").

[0072] The NG-RAN 104 supports multi-radio DC (MR-DC) operation, and an RRC_CONNECTED UE 102 is configured to utilize radio resources provided by two different schedulers located at at least two different NG-RAN nodes 114 connected via a non-ideal backhaul, one NG-RAN node 114 providing NR access and the other NG-RAN node 114 providing either E-UTRA or NR access. One node functions as a master node (MN) and the other as a secondary node (SN), and the MN and SN are connected via a network interface, with at least the MN connected to a core network (e.g., CN 140). In some implementations, the MN and / or SN can operate using shared spectrum channel access. In particular, the NG-RAN 104 supports NR-NR Dual Connectivity (NR-DC), in which the UE 102 is connected to one gNB 114a functioning as an MN and another gNB 114a functioning as an SN. Furthermore, NR-DC can also be used when the UE is connected to a single gNB that functions as both an MN and an SN and constitutes both an MCG and an SCG. Further details of NR-DC operation, including conditional PSCell addition (CPA) and conditional PSCell change (CPC), can be found in [TS36300], [TS38300], and 3GPP TS37.340 v17.5.0(2023-06-30) (“[TS37340]”), the contents of each of which are incorporated herein by reference in their entirety for all purposes. For DC at L2, if the UE 102 is configured with an SCG, the UE 102 is configured with at least two MAC entities: one MAC entity for the MCG and one MAC entity for each SCG. Further details of DC operation can be found in [TS37340].Additionally or alternatively, the UE 102 may be equipped with a respective measurement configuration for each cell (e.g., one measurement configuration for the MCG cell (or PCell) and one measurement configuration for each SCG (or each PSCell or SCell)).

[0073] Additionally or alternatively, the NG-RAN 104 supports carrier aggregation (CA). In CA, two or more component carriers (CCs) are aggregated. A UE 102 may simultaneously receive or transmit on one or more CCs, depending on its capabilities. For example, a UE 102 with a single timing advance (TA) capability for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells sharing the same TA (multiple serving cells grouped into one timing advance group (TAG)), while a UE 102 with multiple timing advance capabilities for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells with different timing advances (multiple serving cells grouped into multiple TAGs). The NG-RAN 104 ensures that each TAG includes at least one serving cell, and a non-CA-capable UE 102 can receive on a single CC and transmit on a single CC corresponding to only one serving cell (one serving cell in one TAG).

[0074] CA is supported for both contiguous and non-contiguous CCs. When CA is deployed, frame timing and SFN are aligned across aggregated cells, or a slot multiple offset between the PCell / PSCell and the SCell is configured in the UE. The maximum number of configured CCs for a UE 102 is 16 for DL and 16 for UL. CA can also include a primary cell (PCell, primary cell), a primary secondary cell group (SCG) cell (PSCell, primary SCG cell), a serving cell, a secondary cell, and a special cell. The PCell is a master cell group (MCG) cell operating on the primary frequency, and the UE 102 performs an initial connection establishment procedure or initiates a connection re-establishment procedure. For dual connectivity operation, the PSCell is an SCG cell that performs random access when the UE 102 performs reconfiguration via a synchronization procedure. Regarding the serving cell, for an RRC_CONNECTED UE 102 not configured with CA / DC, there is only one serving cell configured as the primary cell. For an RRC_CONNECTED UE 102 configured with CA / DC, the term "serving cell" is used to refer to the set of cells including the SpCell and all SCells. An SCell for a CA-configured UE 102 is a cell that provides additional radio resources in addition to the SpCell. For DC operation, the term SpCell refers to a PCell of the MCG or a PSCell of the SCG; otherwise, the term SpCell refers to a PCell.

[0075] At Layer 3 (L3) (e.g., RRC), when CA is configured, the UE 102 has only one RRC connection with the network (e.g., the RAN 104 and / or RAN node 114). During RRC connection establishment / re-establishment / HO, one serving cell provides non-access stratum (NAS) mobility information, and during RRC connection re-establishment / handover, one serving cell provides security input. This cell is called the PCell. Depending on the UE capabilities, one or more SCells can be configured to form a set of serving cells with the PCell. In these implementations, the configured set of serving cells for the UE 102 includes one PCell and one or more SCells. Reconfiguration, addition, and removal of SCells can be performed by RRC. During intra-NR HO and during connection resumption from RRC_INACTIVE, the network can also add, remove, retain, or reconfigure SCells for use with the target PCell. When adding a new SCell, for example, while in connected mode, dedicated RRC signaling is used to transmit all required system information for the SCell, and the UE 102 does not need to obtain broadcast system information directly from the SCell.

[0076] At Layer 2 (L2), in the case of CA, the multi-carrier nature of the PHY layer is only exposed to the MAC layer, where one HARQ entity per serving cell is required. In both UL and DL, there may be one independent HARQ entity per serving cell, and in the absence of spatial multiplexing, one transport block is generated per assignment / grant per serving cell. Each transport block and its potential HARQ retransmissions are mapped to a single serving cell. Further aspects are discussed in [TS38300], [TS37324], [TS38323], [TS38322], and [TS38321].

[0077] Continuing with reference to FIG. 1 , the RAN 104 is communicatively coupled to the CN 140, which includes network elements and / or network functions (NFs) for providing various functions to support data and telecommunication services to customers / subscribers (e.g., UEs 102). The components of the CN 140 may be implemented within a single physical node or separate physical nodes. NFV may be utilized to virtualize some or all of the functionality provided by the network elements of the CN 140 onto physical compute / storage resources within servers, switches, etc. A logical instantiation of the CN 140 may be referred to as a network slice, and a logical instantiation of a portion of the CN 140 may be referred to as a network sub-slice.

[0078] In the example of FIG. 1, the CN 140 is a 5G Core Network (5GC) 140 that includes an Authentication Server Function (AUSF) 142, an Access and Mobility Management Function (AMF) 144, a Session Management Function (SMF) 146, a User Plane Function (UPF) 148, a Network Slice Selection Function (NSSF) 150, a Network Exposure Function (NEF) 152, a Network Repository Function (NRF) 154, a Policy Control Function (PCF) 156, a Unified Data Management (UDM) 158, an Application Function (AF) 160, an Edge Application Server Discovery Function (EASDF) 161, and a Network Data Analytics Function (NWDAF) 162, coupled to each other over various interfaces as shown. The NFs within 5GC140 are described below and in [TS23501], [TS23502], [TS23503], among many other 3GPP standards.

[0079] The NWDAF 162 includes one or more of the following functions: support for collecting data from the NFs and AFs 160; support for collecting data from the OAM 240; support for NWDAF service registration and metadata publishing to the NFs and AFs 160; support for providing analytics information to the NFs and AFs 160; and support for training and providing machine learning (ML) models to the NWDAF 162. Some or all of the NWDAF functions may be supported in a single instance of the NWDAF 162. The NWDAF 162 includes analytics reporting capabilities (e.g., analytics logical function (AnLF)) that include means to enable discovery of types of analytics that can be consumed by external parties and / or request consumption of analytics information generated by the NWDAF 162. The NWDAF 162 may include an AnLF and / or a model training logical function (MTLF). Further aspects of the NWDAF162 functionality are defined in 3GPP TS23.288 v18.2.0(2023-06-21) (“[TS23288]”).

[0080] The AUSF 142 stores data and handles authentication-related functions for authentication of the UE 102. The AUSF 142 may facilitate a common authentication framework for various access types.

[0081] The AMF 144 enables other functions of the 5GC 140 to communicate with the UE 102 and the RAN 104 and subscribe to notifications about mobility events relating to the UE 102. The AMF 144 provides the following functions: termination of the RAN CP interface (N2), termination of the NAS (N1), NAS ciphering and integrity protection, registration management, connection management, reachability management, mobility management, lawful intercept (for AMF events and interface to the L1 system), providing transport for session management (SM) messages between the UE 102 and the SMF 146, transparent proxy for routing SM messages, access authentication, access authorization, providing transport for short message service (SMS) messages between the UE 102 and the SMS function (SMSF), security anchor functionality (SEAF) as specified in 3GPP TS 33.501 ("TS33501"). The AMF 144 may provide transport for location service messages between the RAN 104 and the LMF (as described in Section 6.2.8), EPS bearer ID allocation for interconnection with EPS, UE mobility event notification, S-NSSAI per TA mapping notification, support for control plane CIoT 5GS optimization, support for user plane CIoT 5GS optimization, support for restricting extended coverage usage, providing external parameters (expected UE behavior parameters or network configuration parameters), support for network slice specific authentication and authorization, support for charging, control of 5G access stratum-based time allocation based on UE subscription data, and / or control of gNB time synchronization status reporting and subscription, some or all of which may be supported in a single instance of the AMF 144. In addition to the above functions of the AMF 144, the AMF 144 may also include policy-related functions as described in Section 6.2.8.

[0082] The SMF 146 performs the following functions: SM (SM refers to management of PDU sessions, and PDU sessions or "sessions" refers to PDU connection services that provide or enable the exchange of PDUs between the UE 102 and the DN 136), including session establishment, modification, and release, including, for example, tunnel maintenance between the UPF 148 and the (R)AN node 114; UE internet protocol (IP) address allocation and management, including optional authorization (UE IP addresses may be received from the UPF or from an external data network); server and client functions in Dynamic Host Configuration Protocol (DHCP) version 4 (DHCPv4) and / or DHCPv6; address resolution protocol (ARP) requests and / or IP version 6 (IPv6) based on locally cached information for Ethernet PDU sessions; 6) Functions for responding to peripheral solicitation requests (the SMF 146 responds to ARP and / or IPv6 peripheral solicitation requests by providing the MAC address corresponding to the IP address sent in the request), selection and control of UP functions (including controlling the UPF to proxy ARP or IPv6 peripheral discovery for Ethernet PDU sessions or to forward all ARP / IPv6 peripheral solicitation traffic to the SMF), configuration of traffic forwarding in the UPF to route traffic to the appropriate destination, 5G Virtual Networks (VNs),(virtual network) group management, e.g. maintaining the topology of the involved PSA UPFs, establishing and releasing N19 tunnels between PSA UPFs, local switching, configuring traffic forwarding in the UPF to apply N6-based or N19-based forwarding, managing traffic forwarding when an SMF set or multiple SMF sets are providing a 5G VN, terminating the interface towards policy control functions, lawful interception (for SM events and interface towards the L1 system), supporting charging, controlling and coordinating charging data collection in the UPF 148, terminating the SM part of NAS messages, DL data notification, initiator of (R)AN specific SM information sent over N2 to the (R)AN 104 via the AMF 144, determining the session and service continuity (SSC) mode for sessions, supporting control plane CIoT 5G optimization, supporting header compression, acting as an I-SMF in deployments where an I-SMF can be inserted, providing external parameters (expected UE behavior parameters or network configuration parameters), supporting P-CSCF discovery for IMS services, the following roaming functions: QoS Functions as a V-SMF with locally implemented processing for applying SLA (VPLMN), charging (VPLMN) and lawful intercept (at the VPLMN for SM events and interface to L1 systems), supports interaction with external DNs 136 for transport of signaling for PDU session authentication / authorization by the external DNs 136, time-sensitive communication based on TSC assistance containers received from the PCF 156 (TSC,This includes generation of time-sensitive communication assistance information, support for RAN feedback for BAT offsets and adjusted periodicity as defined in Section 5.27.2.5 of [TS23548], and / or support for edge computing extensions as discussed in [TS23548], [TS23558], and [TS23501] §6.3.23, some or all of which may be supported in a single instance of SMF 146. In addition to the above functions, SMF 146 may also include policy-related functionality as described in Section 6.2.2 of [TS23501].

[0083] The UPF 148 serves as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the DN 136, and a branch point for supporting multi-homed PDU sessions. Aspects of the PDU connection service and PDU sessions are discussed in 3GPP TS38.415 v17.0.0 (2022-04-06) and 3GPP TS38.413 v17.3.0 (2023-01-06). The UPF 148 also performs packet routing and forwarding, packet inspection, enforces the user plane portion of policy rules, lawfully intercepts packets (UP collection), performs traffic usage reporting, performs QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), performs UL traffic validation (e.g., SDF-to-QoS flow mapping), transport-level packet marking on the UL and DL, DL packet buffering, and DL data notification triggering. The UPF 148 may include a UL classifier that supports routing traffic flows to the data network.

[0084] The NSSF 150 selects a set of network slice instances to serve the UE 102. The NSSF 150 also determines the authorized NSSAI and its mapping to the subscribed S-NSSAI, if necessary. The NSSF 150 also determines the AMF set to be used to serve the UE 102, or alternatively, determines a list of candidate AMFs 144 based on an appropriate configuration, possibly by querying the NRF 154. The selection of a set of network slice instances for the UE 102 may be triggered by the AMF 144 to which the UE 102 is registered by interacting with the NSSF 150, which may result in a change of the AMF 144. The NSSF 150 may interact with the AMF 144 over the N22 reference point and communicate with another NSSF in a visited network over the N31 reference point (not shown).

[0085] The NEF 152 securely exposes services and capabilities offered by 3GPP NFs to third parties, internal exposure / re-exposure, AFs 160, edge computing networks / frameworks, etc. In such instances, the NEF 152 may authenticate, authorize, or throttle AFs. The NEF 152 stores / retrieves information as structured data using the Nudr interface to the Unified Data Repository (UDR). The NEF 152 may also translate information exchanged with the AF 160 and with internal NFs. For example, the NEF 152 may translate between AF service identifiers and internal 5GC information such as DNNs and S-NSSAs, as described in Section 5.6.7 of [TS23501]. In particular, the NEF 152 handles the masking of network and user sensitive information from external AFs 160 in accordance with network policy. The NEF 152 also receives information from other NFs based on their published capabilities. This information may be stored in the NEF 152 as structured data or in a data storage NF using a standardized interface. The stored information can then be republished by the NEF 152 to other NFs and AFs, or used for other purposes such as analysis. For example, NWDAF analytics may be securely published by the NEF 152 for external parties as specified in [TS23288]. Furthermore, data provided by external parties may be collected by the NWDAF 162 via the NEF 152 for the purpose of analytics generation. The NEF 152 processes and forwards requests and notifications between the NWDAF 162 and the AF 160 as specified in [TS23288].

[0086] The NRF 154 supports service discovery functions, receives NF discovery requests from NF instances, and provides information about discovered NF instances to the NF instances. The NRF 154 also maintains NF profiles of available NF instances and their supported services. The NF profiles of NF instances maintained in the NRF 154 include various information discussed in [TS23501], [TS23502], [TS23288], 3GPP TS29.510 v18.3.0 (2023-06-26), 3GPP TS23.287 v18.0.0 (2023-03-31), 3GPP TS23.247 v18.2.0 (2023-06-21), etc.

[0087] The PCF 156 provides policy rules to control plane functions for enforcement and supports a unified policy framework for managing network behavior. The PCF 156 may also implement a front end to access subscription information related to policy decisions in the UDRs of the UDM 158. In addition to communicating with functions over reference points as shown, the PCF 156 presents an Npcf service-based interface.

[0088] The UDM 158 processes subscription-related information to support processing of communication sessions by network entities and stores subscription data for the UE 102. For example, the subscription data may be communicated via the N8 reference point between the UDM 158 and the AMF 144. The UDM 158 may include two parts: an application front end and a UDR. The UDR may store structured data for subscription and policy data for the UDM 158 and the PCF 156, and / or public and application data for the NEF 152 (including PFDs for application discovery, application requirement information for multiple UEs 102). A Nudr service-based interface may be exposed by the UDR to enable the UDM 158, the PCF 156, and the NEF 152 to access specific sets of stored data and to read, update (e.g., add, modify), delete, and subscribe to notifications of associated data changes in the UDR. The UDM 158 may include a UDM-FE, which is responsible for credential processing, location management, subscription management, etc. Several different front ends may serve the same user for different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 158 may present a Nudm service-based interface.

[0089] The EASDF 161 exposes a Neasdf service-based interface and is connected to the SMF 146 via an N88 interface. One or more EASDF instances may be located within the PLMN, and the interaction between the 5GC NFs and the EASDF 161 takes place within the PLMN. The EASDF 161 includes one or more of the following functions: registration with the NRF 154 for EASDF 161 discovery and selection, processing DNS messages according to instructions from the SMF 146, and / or termination of DNS security if used. Processing DNS messages according to instructions from the SMF 146 includes one or more of the following functions: receiving DNS message processing rules and / or BaselineDNSPattern from the SMF 146; exchanging DNS messages with / from the UE 102; forwarding DNS messages to C-DNS or L-DNS for DNS queries; adding the EDNS client subnet (ECS) option for FQDNs to DNS queries; reporting information about received DNS messages to the SMF 146; and / or buffering / discarding DNS messages from the UE 102 or DNS server. The EASDF has a direct user plane connection (e.g., without a NAT) with the PSA UPF over N6 for the transmission of DNS signaling exchanged with the UE. The placement of a NAT between the EASDF 161 and the PSA UPF 148 may or may not be supported. Further aspects of the EASDF 161 are discussed in [TS23548].

[0090] The AF 160 provides application influence on traffic routing, provides access to the NEF 152, and interacts with the policy framework for policy control. The AF 160 may influence the (re)selection of the UPF 148 and traffic routing. Based on operator deployment, when the AF 160 is considered a trusted entity, the network operator may allow the AF 160 to interact directly with associated NFs. In some implementations, the AF 160 is used for edge computing implementations. NFs that need to collect data from the AF 160 may subscribe / unsubscribe to notifications about the data collected from the AF 160 directly from the AF 160 or via the NEF 152.

[0091] The 5GC 140 may enable edge computing by selecting an operator / third-party service to be geographically close to the point where the UE 102 attaches to the network. This may reduce latency and load on the network. In an edge computing implementation, the 5GC 140 may select a UPF 148 close to the UE 102 and perform traffic steering from the UPF 148 to the DN 136 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 160, which allows the AF 160 to influence UPF (re)selection and traffic routing.

[0092] The data network (DN) 136 is a network that hosts data-centric services, such as operator services, the Internet, third-party services, and / or enterprise networks. The DN 136 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers 138. By way of example, the servers 138 may be or include application (app) servers, content servers, web servers, database servers, edge computing nodes or servers, DNS servers, cloud computing nodes or resources, etc. The DN 736 may represent one or more local area DNs (LA DNs), which are DNs 136 (or DN names) that provide connectivity to the specific DNs and are accessible by the UE 102 within one or more specific areas where availability is provided to the UE 102. Outside these specific areas, the UE 102 cannot access the LADN / DN 1336.

[0093] Additionally or alternatively, the DN 136 may be an edge DN 136, which is a (local) DN that supports an architecture for enabling edge applications. In these examples, the server 138 may represent a physical hardware system / device providing app server functionality and / or app software residing in a cloud or on an edge computing node that performs server functionality. The server 138 provides an edge hosting environment (or edge computing platform) that provides support for implementing or operating edge app execution and / or providing one or more edge services. The 5GS 100 can use one or more edge computing nodes to provide interface and offload processing for wireless communication traffic. In these examples, the edge computing nodes may be included in or co-located with one or more RANs 104 or RAN nodes 114. For example, the edge computing nodes can provide connectivity between the RAN 104 and the UPF 148 within the 5GC 140. The edge computing nodes can handle wireless connectivity with the RAN 114 and the UPF 148 using one or more NFV instances instantiated on a virtualization infrastructure within the edge computing node.

[0094] An edge computing network (or collection of edge computing nodes) provides a distributed computing environment for application and service hosting, as well as storage and processing resources so that data and / or content can be processed closer to subscribers (e.g., users of UEs 102) for faster response times. The edge network also supports a multi-tenancy runtime and hosting environment for applications, including, among other services, virtual appliance applications that can be delivered as packaged virtual machine (VM) images, virtualized containers, middleware applications and infrastructure services, content delivery services including content caching, mobile big data analytics, and compute offloading. The edge network includes a collection of edge computing nodes (or edge servers) and edge management systems using one or more edge computing technologies (ECTs) (also referred to as "edge computing frameworks" or similar) to run edge applications (apps) within an operator network or a subset of the operator network. Each edge computing node includes an edge platform and / or virtualization infrastructure and provides compute, storage, and network resources to edge apps. Each edge computing node is located at the edge of a corresponding access network (e.g., RAN 104) and is configured to provide computing resources and / or various services (e.g., computational task and / or work offloading, cloud computing capabilities, IT services, and other similar resources and / or services as discussed herein) relatively close to the UE 102. The VIs of the edge computing nodes provide virtualization environments and virtualization resources for edge hosts, and edge computing applications may run as VMs and / or application containers on the VIs. An example of ECT is the MEC framework (e.g., ETSI GS MEC 003 v3.1).1 (2022-03)), Open RAN (O-RAN) (see, for example, O-RAN Working Group 1 (Use Cases and Overall Architecture): O-RAN Architecture Description, O-RAN ALLIANCE WG1, O-RAN Architecture Description v09.00, Release R003 (Jun. 2023)), Multi-Access Management Service (MAMS) (see, for example, Kanugovi et al., Multi-Access Management Services (MAMS), INTERNET ENGINEERING TASK FORCE (IETF), Request for Comments (RFC) 8743 (Mar. 2020)), and / or 3GPP system architecture for enabling edge applications (see, for example, 3GPP TS23.558 v18.3.0 (2023-06-21) (“[TS23558]”), 3GPP TS23.501 v18.2.1(2023-06-29)("[TS23501]"), 3GPP TS23.502 v18.2.0(2023-06-29)("TS23502"), 3GPP TS23.548 3GPP TS23.222 v18.2.0(2023-06-21), 3GPP TS33.122 v18.0.0(2023-06-22), 3GPP TS29.222 v18.2.0(2023-06-26), 3GPP TS29.522 v18.2.0(2023-06-27), 3GPP TS29.122 v18.2.0(2023-06-26), 3GPP TS23.682 v18.0.0(2023-03-31), 3GPP TS23.434 v18.5.0(2023-06-21), 3GPP TS23.401 v18.2.0 (2023-06-21), 3GPP TS28.532 v17.5.2 (2023-07-05), 3GPP TS28.533 v17.3.0 (2023-03-30) ("[TS28533]"), 3GPP TS28.535 v17.7.0(2023-06-22)("[TS28535]"), 3GPP TS28.536 v17.5.0(2023-03-30)("[TS28536]"), 3GPP TS28.541 v18.4.1(2023-06-30), 3GPP TS28.545 v17.0.0(2021-06-24), 3GPP See 3GPP TS28.550 v18.1.0 (2023-03-30) (“[TS28550]”), 3GPP TS28.554 v18.2.0 (2023-06-22) (“[TS28554]”), and 3GPP TS28.622 v18.3.0 (2023-06-22) (“[TS28622]”) (collectively referred to herein as “[3GPPEdge]”), the entire contents of each of which are incorporated herein by reference. It should be understood that the above edge computing framework / ECT and service deployment examples are merely illustrative examples of ECT, and that the present disclosure may be applicable to many other or additional edge computing / networking technologies with various combinations and layouts of devices located at the edge of a network, including the various edge computing networks / systems described herein. Furthermore, the techniques disclosed herein may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be applicable to the present disclosure. Examples of such edge computing / networking techniques, as well as the techniques disclosed herein, may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be used for purposes of the present disclosure.

[0095] The interfaces of the 5GC 140 include reference points and service-based interfaces. The reference points are N1 (between the UE 102 and the AMF 144), N2 (between the RAN 114 and the AMF 144), N3 (between the RAN 114 and the UPF 148), N4 (between the SMF 146 and the UPF), N5 (between the PCF 156 and the AF 160), N6 (between the UPF 148 and the DN 136), N7 (between the SMF 146 and the PCF 156), N8 (between the UDM 158 and the AMF 144), N9 (between two UPFs 148), N10 (between the UDM 158 and the SMF 146), and N11 (between the AM 1 ). Other reference point representations not shown in Figure 1 may also be used. The service-based representation in Figure 1 represents an NF in the control plane that allows other authorized NFs to access these services. Service-based interfaces (SBIs) include Namf (an SBI exposed by the AMF 144), Nsmf (an SBI exposed by the SMF 146), Nnef (an SBI exposed by the NEF 152), Npcf (an SBI exposed by the PCF 156), Nudm (an SBI exposed by the UDM 158), Naf (an SBI exposed by the AF 160), Nnrf (an SBI exposed by the NRF 154), Nnssf (an SBI exposed by the NSSF 150), and Nausf (an SBI exposed by the AUSF 142). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1 may also be used. The NEF 152 may provide an interface to edge compute nodes, which may be used to handle wireless connectivity with the RAN 714.

[0096] Although not shown in FIG. 1 , the system 100 may also include, for example, an Unstructured Data Storage Function (UDSF), a Network Slice Admission Control Function (NSACF), a Network Slice-specific and Stand-alone Non-Public Network (SNPN) Authentication and Authorization Function (NSSAAF), a UE radio Capability Management Function (UCMF), a 5G-Equipment Identity Register (5G-EIR), a Charging Function (CHF), a Time Sensitive Networking (TSN) AF160, a Time Sensitive Communication and Time Synchronization Function (TSCTSF), a Data Collection Coordination Function (DCCF), and other functions discussed in [TS23501]. Function), Analytics Data Repository Function (ADRF), Messaging Framework Adaptor Function (MFAF), Binding Support Function (BSF), Non-Seamless WLAN Offload Function (NSWOF), Service Communication Proxy (SCP), Security Edge Protection Proxy (SEPP)The NF may include NFs not shown, such as a Security Edge Protection Proxy, a Non-3GPP Interworking Function (N3IWF), a Trusted Non-3GPP Gateway Function (TNGF), a Wireline Access Gateway Function (W-AGF), and / or a Trusted WLAN Interworking Function (TWIF).

[0097] 2 illustrates a wireless network 200 including a UE 202 communicatively coupled to a NAN 204 via a connection 206. The UE 202 and NAN 204 may be the same as or similar to the UE 102 and NAN 104, respectively. The connection 206 is an air interface for enabling the communicative coupling consistent with a cellular communication protocol such as LTE, mmWave, or 5G / NR operating in sub-6 GHz frequencies and / or in accordance with any other RAT discussed herein.

[0098] The UE 202 includes a host platform 208 coupled to a modem platform 210. The host platform 208 includes an application processing circuit 212, which is coupled to a protocol processing circuit 214 of the modem platform 210. The application processing circuit 212 sources / sinks application data and executes various applications for the UE 202. The application processing circuit 212 implements one or more layer operations to transmit / receive application data to / from a data network. These layer operations include transport (e.g., UDP, TCP, QUICK, etc.), network (e.g., IP, etc.), and / or other layer operations. The protocol processing circuit 214 implements one or more of the layer operations to facilitate transmission or reception of data over the connection 206. Layer operations implemented by the protocol processing circuit 214 include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0099] The modem platform 210 may further include digital baseband circuitry 216 that implements one or more layer operations "below" the layer operations performed by the protocol processing circuitry 214 in the network protocol stack. These operations include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (including one or more of space-time coding, space-frequency coding, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0100] The modem platform 210 includes transmit (Tx) circuitry 218, receive (Rx) circuitry 220, radio frequency (RF) circuitry 222, and an RF front end (RFFE) 224, which include or connect to one or more antenna panels 126. The Tx circuitry 218 includes digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the Rx circuitry 220 includes analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 222 includes low-noise amplifiers, power amplifiers, power tracking components, etc.; the RFFE 224 includes filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc.; and the antenna panel 226 (also referred to as "Tx / Rx components") includes one or more antenna elements such as a planar inverted-F antenna (PIFA), monopole antenna, dipole antenna, loop antenna, patch antenna, Yagi antenna, parabolic antenna, omnidirectional antenna, etc. The selection and arrangement of components in Tx circuitry 218, Rx circuitry 220, RF circuitry 222, RFFE 224, and antenna panel 226 may be specific to the details of a particular implementation, such as whether communications are TDM or FDM, mmWave or sub-6 GHz frequencies, etc. The Tx / Rx components may be arranged in multiple parallel Tx / Rx chains, may be located on the same or different chips / modules, etc. The protocol processing circuitry 214 includes one or more instances of control circuitry (not shown) to provide control functions to the Tx / Rx components.

[0101] UE reception is established by and through antenna panel 226, RFFE 224, RF circuitry 222, Rx circuitry 220, digital baseband circuitry 216, and protocol processing circuitry 214. Antenna panel 226 may receive transmissions from NAN 204 by receive beamforming signals received by the set of antennas / antenna elements of antenna panel 226. UE transmission is established by and through protocol processing circuitry 214, digital baseband circuitry 216, Tx circuitry 218, RF circuitry 222, RFFE 224, and antenna panel 226. The Tx component of UE 204 may apply a spatial filter to the data to be transmitted to form a Tx transmit beam to be radiated by the antenna elements of antenna panel 226.

[0102] Similar to the UE 202, the AN 204 includes a host platform 228 coupled to a modem platform 230. The host platform 228 includes an application processing circuit 232 coupled to a protocol processing circuit 234 of the modem platform 230. The modem platform may further include a digital baseband circuit 236, a Tx circuit 238, an Rx circuit 240, an RF circuit 242, an RFFE circuit 244, and an antenna panel 246. The components of the NAN 204 may be similar to, and substantially interchangeable with, the similarly named components of the UE 202. In addition to performing data transmission / reception as described above, the components of the NAN 208 may perform various logical functions, including, for example, radio bearer management, uplink and downlink dynamic radio resource management, RNC functions such as data packet scheduling, and / or various other functions such as any of those discussed herein.

[0103] FIG. 3 illustrates a hardware resource 300 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein. The hardware resource 300 may correspond to any of the entities / elements discussed herein, such as the UE 102, 202, the NAN 114, 204, and / or any of the NFs discussed with respect to FIGS. 1-2. The hardware resource 300 includes one or more processors (or processor cores) 310, one or more memory / storage devices 320, and one or more communication resources 330, each of which may be communicatively coupled via an interconnect (IX) 306 or any suitable bus and / or other interface circuitry implementing IX technology. If node virtualization (e.g., NFV) is utilized, a hypervisor 302 may execute to provide an execution environment for one or more network slices / sub-slices for utilizing the hardware resource 300. The hardware resource 300 may be implemented within or by individual compute nodes, which may be housed in enclosures of various form factors. Additionally or alternatively, hardware resource 300 may be implemented by multiple computing nodes that may be deployed in one or more data centers and / or distributed across one or more geographic regions.

[0104] Processor 310 may include, for example, processors 310-1 through 310-p (where p is a number). Processor 310 may be or include, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), a microprocessor or controller, a multi-core processor, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, an xPU, a data processing unit (DPU), an infrastructure processing unit (IPU), a network processing unit (NPU), another processor (including any of those discussed herein), and / or any suitable combination thereof.

[0105] The memory / storage device 320 may include, for example, main memory, disk storage, or any suitable combination thereof. The memory / storage device 320 may include, but is not limited to, any type of volatile, non-volatile, semi-volatile memory, and / or any combination thereof. By way of example, the memory / storage device 320 may be a random access memory (RAM), a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a magnetoresistive RAM (MRAM), a conductive bridge random access memory (CB-RAM), a spin transfer torque (STT)-MRAM, a phase change RAM (PRAM), a core memory, a dual inline memory module (DIMM), a micro DIMM, a mini DIMM, a block addressable memory device (e.g., based on NAND or NOR technology (e.g., single-level cell (SLC), multi-level cell (MLC), quad-level cell (QLC), tri-level cell (TLC), or other NAND), a read-only memory (ROM), a programmable ROM (PROM), or a programmable ROM (PROM). ROM), erasable PROM (EPROM), electrically EPROM (EEPROM), flash memory, non-volatile RAM (NVRAM,non-volatile RAM), solid state storage, magnetic disk storage media, optical storage media, memory devices using chalcogenide glass, multi-threshold level NAND flash memory, NOR flash memory, single or multi-level phase change memory (PCM) and / or phase change memory with a switch (PCMS), NVM devices using chalcogenide phase change materials (e.g., chalcogenide glass), resistive memory, nanowire memory, ferroelectric transistor random access memory (FeTRAM), antiferroelectric memory, magnetoresistive random access memory (MRAM) incorporating memristor technology, phase change RAM (PRAM), resistive memory including metal oxide-based, oxygen vacancy-based, and conductive bridge, and conductive bridge random access memory (CB-RAM), or spin transfer torque (STT), spintronic magnetic junction memory-based devices, magnetic tunneling junctions (MTJ), The memory device may be or include a memory junction-based device, a domain wall (DW) and spin orbit transfer (SOT)-based device, a thyristor-based memory device, and / or any combination of the above memory devices and / or other memories.

[0106] Communications resources 330 may include, for example, interconnection controllers and / or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 304 or one or more databases 306 and / or other network elements over network 308. Network 308 may represent any suitable network (e.g., DN136, the Internet, an enterprise network, a WAN, a LAN, a WLAN, a VN, a VPN, etc.), an edge computing network, a cloud computing service, etc. For example, communications resources 330 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth (or Bluetooth low energy) components, WiFi (or other communications components), and other communications components.

[0107] The instructions 350 may include software, program code, an application, an applet, an app, firmware, microcode, machine code, and / or other executable code for causing at least one of the processor 310 to perform any one or more of the methods and techniques discussed herein. The instructions 350 may reside, completely or partially, within at least one of the processor 310 (e.g., a cache memory of the processor), the memory / storage device 320, or any suitable combination thereof. Any portion of the instructions 350 may be transferred to the hardware resources 300 from any combination of the peripheral device 304 and / or the database 306. Accordingly, the memory of the processor 310, the memory / storage device 320, the peripheral device 304, and the database 306 are examples of computer-readable and machine-readable media.

[0108] In some implementations, peripheral device 304 may represent one or more sensors (also referred to as “sensor circuitry”). A sensor circuitry includes a device, module, or subsystem that is designed to detect events or changes in its environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Individual sensors may be exteroceptive sensors (e.g., sensors that capture and / or measure environmental phenomena and / or external conditions), proprioceptive sensors (e.g., sensors that capture and / or measure internal conditions of a computational node or platform and / or individual components of a computational node or platform), and / or exproprioceptive sensors (e.g., sensors that capture, measure, or correlate internal and external conditions). Examples of such sensors include, among others, inertia measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers, microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, and / or magnetometers, level sensors, flow sensors, temperature sensors (e.g., thermistors including sensors for measuring the temperature of internal components and sensors for measuring the temperature external to the computational node or platform), pressure sensors, barometric pressure sensors, gravity meters, altimeters, image capture devices (e.g., cameras), light detection and ranging (LiDAR) sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, optical light sensors, ultrasonic transceivers, microphones, etc.

[0109] Additionally or alternatively, peripheral device 304 may represent one or more actuators that enable a computational node, platform, machine, device, mechanism, system, or other object to change its state, position, and / or orientation, or to move or control a computational node (e.g., node 300), platform, machine, device, mechanism, system, or other object. Actuators include electrical and / or mechanical devices for moving or controlling mechanisms or systems, and convert energy (e.g., electrical current or moving air and / or liquid) into some type of motion. By way of example, actuators may include the following: soft actuators (e.g., actuators that change their shape in response to a stimulus such as a mechanical, thermal, magnetic, and / or electrical stimulus), hydraulic actuators, pneumatic actuators, mechanical actuators, electromechanical actuators (EMA), microelectromechanical actuators, electrohydraulic actuators, linear actuators, linear motors, rotary motors, DC motors, stepper motors, servomechanisms, electromechanical switches, electromechanical relays (EMR), power switches, valve actuators, piezoelectric actuators and / or bimorphs, thermal bimorphs, solid state actuators, solid state relays (SSR), shape memory alloy based actuators, electroactive polymer based actuators, relay driver integrated circuits (IC), The actuator may be or include any number and combination of actuators, such as actuators, claws, tweezers, clamps, hooks, mechanical fingers, humanoid dexterous robotic hands, and / or other gripper mechanisms that physically grasp an object by direct impact with the object), propulsion actuators / mechanisms, projectile actuators / mechanisms, and / or audible sound generators, visual warning devices, and / or other similar electromechanical components.The computing node 300 may be configured to operate one or more actuators based on one or more captured events, commands, control signals, and / or configurations received from a service provider, a client device, and / or other components of the computing node or platform. Additionally or alternatively, the actuators may be used to change the operating state, position, and / or orientation of sensors.

[0110] [2.1. Measurement mode] As described above, the UE 102 can be configured to perform signal / cell measurement and reporting procedures to provide the network with information regarding the quality of one or more wireless channels and / or the communication medium in general, which can be used to optimize various aspects of the communication system. For example, the network (e.g., the RAN 104 and / or RAN nodes 114) may configure the UE 102 in RRC_CONNECTED mode (e.g., using a measurement configuration (measConfig)) to perform measurements that may be performed in accordance with the measurement model 400 of FIG. 4. The network may configure the UE 102 to report these in accordance with the measurement configuration or to perform conditional reconfiguration evaluation in accordance with a conditional reconfiguration. The measurement configuration may be provided by dedicated signaling, e.g., using an RRCReconfiguration or RRCResume message. The network may configure the UE 102 to perform the following types of measurements: intra-frequency NR measurements, inter-frequency NR measurements, inter-RAT measurements for E-UTRA, and inter-RAT measurements for UTRA (e.g., UTRA-FDD frequencies), and NR sidelink measurements for L2 UE-to-network (U2N, UE to network) relaying UE 102. Additionally or alternatively, the network may configure the UE 102 to report the following measurement information based on the SS / PBCH block (SSB): measurement results per SSB, measurement results per cell based on the SSB, and / or an SSB index. Additionally or alternatively, the network may configure the UE 102 to report the following measurement information based on the CSI-RS resource: measurement results per CSI-RS resource, measurement results per cell based on the CSI-RS resource, and / or a CSI-RS resource measurement identifier. Additionally or alternatively, the network may configure the UE 102 to perform the following types of measurements for the NR sidelink and V2X sidelink channel busy ratio (CBR) measurements:Additionally or alternatively, the network may configure the UE 102 to report the following cross link interference (CLI) measurement information based on the SRS resource: measurement results per SRS resource and SRS resource index. Additionally or alternatively, the network may configure the UE 102 to report the following CLI measurement information based on the CLI-RSSI resource: measurement results per CLI-RSSI resource and CLI-RSSI resource index. Additionally or alternatively, the network may configure the UE 102 to report the following Rx-Tx time difference measurement information based on the CSI-RS for tracking or PRS: UE Rx-Tx time difference measurement result. Additional or alternative measurement types can be configured as discussed in [TS38331].

[0111] Each measurement configuration (e.g., the measConfig IE discussed in [TS38331]) includes the following parameters: a list of measurement objects (MOs), a reporting configuration, a measurement identity, a quantity configuration, and a measurement gap (MG) configuration (e.g., the measGapConfig IE discussed in [TS38331]). In some implementations, the measConfig also includes a measurement gap sharing scheme (e.g., a MeasGapSharingConfig IE (see, e.g., [TS38331]) that controls the setup and / or release of measurement gap sharing). When the UE 102 receives the measConfig (e.g., in an appropriate RRC message), the UE 102 performs various operations / actions discussed in [TS38331] §5.5.

[0112] For each measurement type, one or several MOs can be defined. The MO contains a list of objects on which the UE 102 performs measurements (see, for example, measObjectToAddModList and / or measObjectToRemoveList discussed in [TS38331]). For intra-frequency and inter-frequency measurements, the MO indicates the frequency / time location and subcarrier spacing (SCS) of the RS to be measured. Associated with this MO, the network may configure a list of cell-specific offsets, a list of "exclusion list" cells (e.g., cells not applicable for event evaluation or measurement reporting), and / or a list of "allowed list" cells (e.g., cells only applicable for event evaluation or measurement reporting). The measObjectId of the MO corresponding to each serving cell is indicated by the servingCellMO in the serving cell configuration. For inter-RAT E-UTRA measurements, the MO is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell-specific offsets and a list of "exclusion list" cells. For inter-RAT UTRA-FDD measurements, the MO is the set of cells on a single UTRA-FDD carrier frequency. In some examples, if the received measConfig includes measObjectToRemoveList, the UE 102 performs the measurement object removal procedure specified in [TS38331] §5.5.2.4, and if the received measConfig includes measObjectToAddModList, the UE 102 performs the measurement object addition / modification procedure specified in [TS38331] §5.5.2.5.

[0113] For each MO, one or several reporting configurations can be defined. For example, a list of reporting configurations can be provided, where there can be one or more reporting configurations per MO (e.g., the reportConfigToAddModList IE and / or the reportConfigToRemoveList IE discussed in [TS38331]). Each measurement reporting configuration includes a reporting criterion, an RS type, and a reporting format. The reporting criterion is the criterion that triggers the UE 102 to send a measurement report. The trigger / condition can be event-triggered reporting, periodic reporting, and event-triggered periodic reporting. The RS type is the RS (e.g., SSB or CSI-RS) that the UE 102 uses for beam and / or cell measurement results. The reporting format includes the amount per cell and per beam (e.g., RSRP and / or some other measurement type) that the UE 102 includes in the measurement report, as well as other related information such as the maximum number of cells and the maximum number of beams per cell to report. In case of conditional reconfiguration, each configuration includes an execution criterion and an RS type. The execution criteria is the criteria that the UE 102 uses for the conditional reconfiguration execution, and the RS type is the RS that the UE 102 uses to obtain the beam and cell measurement results (e.g., SSB-based or CSI-RS-based) that are used to evaluate the conditional reconfiguration execution condition. In some examples, if the received measConfig includes reportConfigToRemoveList, the UE 102 performs the reporting configuration removal procedure specified in [TS38331] §5.5.2.6, and if the received measConfig includes reportConfigToAddModList, the UE 102 performs the reporting configuration addition / modification procedure specified in [TS38331] §5.5.2.7.

[0114] The association between an MO and a reporting configuration is created by a measurement identity (measId) (e.g., the measIdToAddModList IE and / or the measIdToRemoveList IE discussed in [TS38331]). For measurement reporting, a list of measIds is provided, with each measId linking one MO to one reporting configuration. Configuring multiple measIds allows more than one MO to be linked to the same reporting setting and more than one reporting configuration to the same MO. The measurement identity is also included in the measurement report that triggered the report and serves as a reference to the network. For conditional reconfiguration triggers, one measurement identity can be linked to exactly one conditional reconfiguration trigger configuration, and up to two measIds can be linked to one conditional reconfiguration execution condition. In some examples, if the received measConfig includes measIdToRemoveList, the UE 102 performs the measurement identity removal procedure specified in [TS38331] §5.5.2.2, and if the received measConfig includes measIdToAddModList, the UE 102 performs the measurement identity addition / modification procedure specified in [TS38331] §5.5.2.3.

[0115] A quantity configuration (e.g., the quantityConfig IE discussed in [TS38331]) defines the measurement filtering configuration to be used for all event evaluation and associated reporting, and for periodic reporting of the measurements. For NR measurements, the network may configure up to two quantity configurations with a reference in the NR MO to the configuration to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for per-cell and per-beam measurements. In some examples, measurement quantities are considered separately for each RAT (or RAN 104), and measurement commands may be used by the NG-RAN 104 to instruct the UE 102 to start, modify, or stop measurements. In some examples, if the received measConfig includes quantityConfig, the UE 102 performs the quantity configuration procedure specified in [TS38331] §5.5.2.8.

[0116] An MG is a period of time that the UE 102 can use to perform measurements. In some examples, if the received measConfig includes measGapConfig, the UE 102 performs the measurement gap configuration procedure specified in [TS38331] §5.5.2.9. If the UE 102 requires an MG to identify and measure intra-frequency, inter-frequency, and / or inter-RAT cells and the UE 102 does not support independent MG patterns for different FRs, the network provides a single per-UE MG pattern for simultaneous monitoring of all frequency layers. If the UE 102 requires an MG to identify and measure intra-frequency, inter-frequency, and / or inter-RAT E-UTRAN cells and the UE 102 supports independent MG patterns for different FRs, the network provides either a per-FR MG pattern for FRs in which the UE 102 requires a per-FR MG for independent and simultaneous monitoring of all frequency layers in each frequency range, or a single per-UE MG pattern for simultaneous monitoring of all frequency layers in all frequency ranges. For example, the parameter gapType indicates the MG type of this MG, the value perUE indicates this is a per-UE MG, the value perFR1 indicates this is an FR1 MG, and the value perFR2 indicates this is an FR2 MG. Furthermore, the parameter gapUE indicates the MG configuration that applies to all frequencies (FR1 and FR2). In some implementations for NR-DC, the parameter gapUE is set only in the measConfig associated with the MCG, and if gapUE is configured, neither the gapFR1 nor the gapFR2 parameters are configured. The applicability of per-UE MG follows Tables 9.1.2-2 and 9.1.2-3 of [TS38133].

[0117] During per-UE MG, the UE 102 is not required to receive / transmit from / to the corresponding NR serving cell for SA (single carrier or CA configured), except for receiving RRM measurements, signals used for PRS measurements, and signals used for random access procedures per [TS38321], and is not required to receive / transmit from / to the corresponding NR serving cell for NR-DC, except for receiving RRM measurements, signals used for PRS measurements, and signals used for random access procedures per [TS38321]. During per-FR MG, the UE 102 is not required to receive / transmit from / to the corresponding NR serving cell within the corresponding frequency range for SA (single carrier or CA configured), except for receiving RRM measurements, signals used for PRS measurements, and signals used for random access procedures per [TS38321], and is not required to receive / transmit from / to the corresponding NR serving cell within the corresponding frequency range for NR-DC, except for receiving RRM measurements, signals used for PRS measurements, and signals used for random access procedures per [TS38321]. The UE 102 supports the MG patterns listed in Table 9.1.2-1 of [TS38133], based on the applicability specified in Tables 9.1.2-2 and 9.1.2-3 of [TS38133]. The UE 102 determines the MG timing based on the gap offset configuration and MG timing advance (MGTA) configuration provided by higher layer signaling as specified in [TS38331] and [TS36331]. In NR-DC mode, the MG for each UE is T MG When configured with an MGTA of ms, the MG shall be configured with a T with respect to the end of the latest MCG subframe that occurs immediately before the configured MG in the subframe of the MCG serving cell. MG ms before the start of the FR1. MG When configured with an MGTA of ms, the MG for FR1 is configured with a T with respect to the end of the latest MCG subframe that occurs immediately before the configured MG in the subframe of the MCG serving cell. MGStarts about ms ahead. MG is the MGTA value provided in milliseconds (ms) according to [TS38331]. In determining the MG start point, the UE 102 uses the DL timing of the latest subframe occurring immediately before the configured MG in the serving cell.

[0118] The MG configuration may also include the mgrp field, which indicates the measurement gap repetition period (MGRP) of the MG in ms according to Table 9.1.2-1 of [TS38133]. If ncsgInd-r17 is present, the mgrp field indicates the Visible Interruption Repetition Period (VIRP) of the NCSG pattern and is configured according to Table 9.1.9.3-1 of [TS38133]. The MG configuration may also include the MG length (MGL) field (mgl). The value mgl (in the mgl field) is the MGL of the MG in ms. If ncsgInd-r17 is not present, the MGL follows Table 9.1.2-1 of [TS38133]. If ncsgInd-r17 is present, the mgl field indicates the measurement length (ML) of the NCSG pattern and is configured according to Table 9.1.9.3-1 of [TS38133]. The value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms, etc. If mgl-r16 is present, the UE 102 ignores mgl (without suffix). The values ms1, ms2, and ms5 are configurable only if ncsgInd is present.

[0119] For a UE 102 with NR-DC operation and configured with a per-UE MG, MG sharing applies when the UE 102 requires an MG to identify and measure cells on intra-frequency carriers, or when the SMTC configured for intra-frequency measurements fully overlaps with the per-UE measurement gaps, and the UE 102 requires measurement gaps to identify and measure cells on inter-frequency carriers and / or inter-RAT E-UTRAN carriers for both SSB and CSI-RS based L3 measurements, or when all of the SMTCs configured for inter-frequency SSB-based measurements without measurement gaps fully overlap with the per-UE measurement gaps and / or inter-RAT UTRAN carriers for SRVCC, and the UE 102 is configured to measure positioning frequency layers. For a UE 102 having NR-DC operation and configured with per-FR1 measurement gaps, measurement gap sharing applies when the UE 102 requires measurement gaps to identify and measure cells on FR1 intra-frequency carriers, or when the SMTC configured for FR1 intra-frequency measurements fully overlaps with the per-FR1 measurement gaps, and the UE 102 requires measurement gaps to identify and measure cells on FR1 inter-frequency carriers and / or inter-RAT E-UTRAN carriers for both SSB and CSI-RS based L3 measurements, or when all of the SMTCs configured for inter-frequency SSB-based measurements without measurement gaps fully overlap with the per-FR1 measurement gaps and / or inter-RAT UTRAN carriers for Single Radio Voice Call Continuity (SRVCC), and the UE 102 is configured to measure positioning frequency layers within FR1. The network (e.g., the RAN 104 and / or RAN node 114) signals the RRC parameter measGapSharingConfig (see, e.g., [TS38331]) with a value of "01" indicating 25% split, "10" indicating 50% split, "11" indicating 75% split, or "00" indicating equal split gap sharing and / or no gap sharing is applied. The split values are applied as shown in equations 2.1-1 and 2.1-2. K intra =1 / X*100 (2.1-1) K inter =1 / (100-X)*100 (2.1-2)

[0120] In equations 2.1-1 and 2.1-2, X is the division value provided in the measGapSharingConfig parameter, and K is a scaling factor, offset, or other parameter. When MeasGapSharingScheme is not present and there is no value stored in the field, it is up to the UE implementation to determine which measurement gap sharing scheme should be applied. The RRC parameter MeasGapSharingScheme is applied to the calculation of the carrier-specific scaling factors as specified in Section 9.1.5.2.4 of [TS38133] and / or as discussed herein (e.g., see Section 1.4.2.1 above). In some examples, if the received measConfig includes measGapSharingConfig, the UE 102 performs the measurement gap sharing configuration procedure specified in [TS38131] §5.5.2.11.

[0121] An RRC_CONNECTED UE 102 maintains an MO list, a reporting configuration list, and a measId list according to the signaling and procedures discussed in [TS38331]. The MO list includes NR MO, CLI MO, inter-RAT object, and / or L2 U2N relay object. Additionally or alternatively, the reporting configuration list includes NR, inter-RAT, and / or L2 U2N relay reporting configurations. Any MO can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to an MO. Similarly, some MOs may not be linked to a reporting configuration. The measurement procedure distinguishes between the following types of cells: (1) NR serving cells (e.g., an SpCell and one or more SCells), (2) listed cells (e.g., cells listed in the MO or MO list), and (3) detected cells (e.g., cells not listed in the MO but detected by the UE 102 on the SSB frequency and SCS indicated by the MO).

[0122] For NR MO, the UE 102 measures and reports the serving cell / serving relay UE 102 (for L2 U2N remote UE 102), listed cells, and / or detected cells. For E-UTRA inter-RAT measurement objects, the UE 102 measures and reports for listed and detected cells, and for RSSI and channel occupancy measurements, the UE 102 measures and reports on configured resources on the indicated frequencies. For UTRA-FDD inter-RAT measurement objects, the UE 102 measures and reports on listed cells. For CLI MO, the UE measures and reports on configured measurement resources (e.g., SRS resources and / or CLI-RSSI resources). For L2 U2N relay objects, the UE measures and reports on serving NR cells and discovered L2 U2N relay UEs. Whenever the specification of a procedure other than those contained in clause 5.5.2 of [TS38331] indicates a field, this relates to a field contained in VarMeasConfig, unless explicitly stated otherwise (e.g., the measurement configuration procedure only covers direct UE actions on the received measConfig).

[0123] In MR-DC (or NR-DC), the UE 102 may receive at least two independent measConfigs, including a measConfig associated with an MCG included in an RRC Reconfiguration message received via SRB1 and a measConfig associated with an SCG included in an RRC Reconfiguration message received via system resource block 3 (SRB3) or embedded in an RRC Reconfiguration message received via system resource block 1 (SRB1). In some implementations, multiple measConfigs can be obtained, each associated with an SCG. In this case, the UE 102 maintains two independent VarMeasConfigs and VarMeasReportLists, one associated with each measConfig, and independently performs all procedures in Section 5.5 of [TS38331] for each measConfig and its associated VarMeasConfig and VarMeasReportList, unless explicitly specified otherwise. Configuration for CBR measurement is only included in measConfig associated with MCG. Configuration for Rx-Tx time difference measurement is only included in measConfig associated with MCG.

[0124] To perform measurements, an RRC_CONNECTED UE 102 derives cell measurements by measuring one or more beams associated with each cell configured by the network (e.g., the RAN 104 and / or individual RAN nodes 114), as described in Section 5.5.3.3 of [TS38331] and / or as described below with reference to Figure 4. For all cell measurements except RSSI and CLI measurements in RRC_CONNECTED, the UE 102 applies L3 filtering as specified in Section 5.5.3.2 of [TS38331] and / or as described below with reference to Figure 4 before using the measurement for evaluation of reporting criteria, measurement reporting, and / or criteria for triggering a conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP, and / or Ec / N0 as trigger quantities, and for CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantities. Additional or alternative measurement types can be configured for these purposes. For cell and beam measurements, the reporting quantity can be any combination of quantities (e.g., RSRP only, RSRQ only, SINR only, RSRP and RSRQ, RSRP and SINR, RSRQ and SINR, RSRP, RSRQ and SINR, RSCP only, EcN0 only, RSCP and EcN0, etc., additional or alternative measurement types and / or combinations can be configured for these purposes), regardless of the trigger quantity. For CLI measurements, the reporting quantity can be either SRS-RSRP or CLI-RSSI. For conditional reconfiguration, the network can configure up to two quantities, both using the same RS type. The UE 102 does not apply L3 filtering, as specified in Section 5.5.3.2 of [TS38331], to derive CBR measurements or to derive Rx-Tx time difference measurements.The network may also configure the UE 102 to report per-beam measurement information (which can be either per-beam measurement results with the respective beam identifiers, or just the beam identifiers), derived as described in Section 5.5.3.3a of [TS38331]. If configured to include beam measurement information in the measurement report, the UE 102 applies L3 beam filtering as specified in Section 5.5.3.2 of [TS38331]. However, the exact L1 filtering of the beam measurements used to derive the cell measurement results may be implementation specific.

[0125] FIG. 4 shows an example measurement model 400 that may be used by the UE 102 to measure signals, cells, channels, beams, etc. In RRC_CONNECTED, the UE 102 measures at least one or more beams of a cell (e.g., gNB beams 1-K in FIG. 4), and the measurement results (e.g., power values, signal strength, signal quality, interference, etc.) are averaged to derive cell quality. In doing so, the UE 102 is configured to consider a subset of detected beams. Filtering is performed at two different levels: at the physical layer to derive beam quality, and then at the RRC level to derive cell quality from multiple beams. Cell quality from beam measurements is derived in the same way for serving and non-serving cells. The measurement report may include measurement results of the X best beams if the UE 102 is configured to do so by the gNB 114a.

[0126] Point A includes PHY layer internal measurements (e.g., beam-specific samples) that are provided to Layer 1 (L1, layer 1) filtering. The beam-specific samples include 1 to K gNB beams, where K is a number. In some examples, the K beams correspond to measurements on synchronization signal blocks (SSBs) and / or CSI-RS resources configured for L3 mobility by the gNB 114a and detected by the UE 102 at L1. The L1 filtering includes internal L1 filtering of the input measured at point A. The specific filtering mechanisms and / or techniques actually performed at the PHY layer are implementation specific.

[0127] Point A 1 contains measurements (e.g., beam-specific measurements) reported by L1-L3 after L1 filtering. In the beam integration / selection element, the beam-specific measurements are integrated to derive the cell quality. The behavior of the beam integration / selection element is configurable, and the configuration of this module is provided by RRC signaling. In some examples, the reporting period at point B is longer than the reporting period at point A. 1 is equal to one measurement period in

[0128] Point B is a point (e.g., cell quality) derived from beam-specific measurements reported to L3 after beam integration / selection. L3 filtering for cell quality elements performs filtering on the measurements provided at point B. The behavior of the L3 filter is configurable, and the configuration of this module is provided by RRC signaling. In some examples, the filtering reporting period at point C is equal to one measurement period at point B.

[0129] Point C includes the measurement after processing with the L3 filter. In some instances, the reporting rate is the same as the reporting rate at point B. This measurement is used as input for evaluation of one or more of the reporting criteria.

[0130] The evaluation of the reporting criteria element checks whether an actual measurement report is required at point D. The evaluation can be based on more than one flow of measurements at reference point C (e.g., to compare between different measurements). This is the case for input C and input C. 1 The UE 102 determines whether the new measurement results are at least at points C, C 1 At point D, the measurement report information (message) is transmitted over the air interface.

[0131] The L3 beam filtering element is located at point A. 1 The beam filter behavior is configurable, and the beam filter configuration is provided by RRC signaling. In some examples, the filtering reporting period at point E is 1 is equal to one measurement period in

[0132] Point E includes measurements after processing with the L3 beam filter (e.g., beam-specific measurements). In some examples, the reporting rate is 1 This measurement is used as input to select the X measurements to be reported.

[0133] The beam selection for the beam report element selects X measurements from the measurements provided in point E. The beam selection behavior is configurable and the configuration of this module is provided by RRC signaling. Point F contains the beam measurement information to be included in the measurement report (transmission) on the air interface.

[0134] L1 filtering introduces a certain level of measurement averaging. Exactly how and when the UE 102 performs the necessary measurements is implementation specific, in that the output at point B meets the performance requirements set in [TS38133]. L3 filtering for cell quality and the associated parameters used are specified in [TS38331] and do not introduce any delay in sample availability between points B and C. 1 The measurements at are the inputs used in the event evaluation. The L3 beam filtering and related parameters used are specified in [TS38331] and do not introduce any delay in sample availability between points E and F.

[0135] The measurement report has the following characteristics: it contains the measId of the associated measurement configuration that triggered the report, the cell and beam measurements included in the measurement report are configured by the network, the number of non-serving cells reported can be limited through configuration by the network, cells belonging to an exclusion list configured by the network are not used in event evaluation and reporting, conversely, when an allowed list is configured by the network, only cells belonging to the allowed list are used in event evaluation and reporting, and the beam measurements included in the measurement report are configured by the network (e.g. beam identifier only, measurement result and beam identifier, or no beam report).

[0136] Intra-frequency surrounding (cell) measurements and inter-frequency surrounding (cell) measurements are defined as follows: SSB-based intra-frequency measurements, SSB-based inter-frequency measurements, CSI-RS-based intra-frequency measurements, and CSI-RS-based inter-frequency measurements.

[0137] An SSB-based intra-frequency measurement is defined as an SSB-based intra-frequency measurement, provided that the center frequency of the SSB of the serving cell is the same as the center frequency of the SSB of the neighboring cell and the subcarrier spacing of the two SSBs is also the same. An SSB-based inter-frequency measurement is defined as an SSB-based inter-frequency measurement, provided that the center frequency of the SSB of the serving cell is different from the center frequency of the SSB of the neighboring cell or the subcarrier spacing of the two SSBs is different. In some examples, for SSB-based measurements, one MO corresponds to one SSB, and the UE 102 considers different SSBs to be different cells. Additionally or alternatively, if a reduced capability (RedCap) UE 102 is configured to perform serving cell measurements based on a non-cell defining (NCD)-SSB configured in its active BWP, this NCD-SSB is considered to be the SSB of the serving cell in the definitions of intra-frequency and inter-frequency measurements described above. A RedCap UE 102 is a UE 102 with reduced capabilities as specified in section 4.2.21.1 of 3GPP TS38.306.

[0138] A CSI-RS-based intra-frequency measurement is defined as a CSI-RS-based intra-frequency measurement provided that the subcarrier spacing of the CSI-RS resources on the neighboring cell configured for measurement is the same as the SCS of the CSI-RS resources on the serving cell indicated for measurement, for 60 kHz subcarrier spacing, the CP type of the CSI-RS resources on the neighboring cell configured for measurement is the same as the CP type of the CSI-RS resources on the serving cell indicated for measurement, and the center frequency of the CSI-RS resources on the neighboring cell configured for measurement is the same as the center frequency of the CSI-RS resources on the serving cell indicated for measurement. A CSI-RS-based inter-frequency measurement is defined as a CSI-RS-based inter-frequency measurement if it is not a CSI-RS-based intra-frequency measurement. In some implementations, extended CP for CSI-RS-based measurements is not supported.

[0139] The UE 102 can identify new intra-frequency cells and perform various measurements (e.g., SS-RSRP, SS-RSRQ, SS-SINR, and / or other measurement types) of the identified intra-frequency cells when carrier frequency information is provided by the PCell or PSCell, even if an explicit neighbor list with physical layer cell identities is not provided. The UE 102 can perform intra-frequency measurements as described in [TS38133] §9.2 (e.g., including without MG as described in [TS38133] §9.2.5 and / or with MG as described in [TS38133] §9.2.6). The UE 102 can identify new inter-frequency cells and perform various measurements (e.g., SS-RSRP, SS-RSRQ, SS-SINR, and / or other measurement types) of the identified inter-frequency cells when carrier frequency information is provided by the PCell or PSCell, even if an explicit neighbor list with physical layer cell identities is not provided. The UE 102 may perform intra-frequency measurements as described in [TS38133] §9.3 (e.g., including without MG as described in [TS38133] §9.3.9 and / or with MG as described in [TS38133] §9.3.4).

[0140] Whether a measurement is non-gap-assisted or gap-assisted depends on the capabilities of the UE 102, the active BWP of the UE 102, and the current operating frequency. For SSB-based inter-frequency measurements, if MG requirement information is reported by the UE 102, MG configuration may be provided according to the information. Otherwise, MG configuration is always provided in the following cases: if the UE 102 supports only per-UE MG and / or if the UE 102 supports per-FR MG and any of the serving cells is within the same frequency range of the MO. For SSB-based intra-frequency measurements, if MG requirement information is reported by the UE 102, MG configuration may be provided according to the information. Otherwise, MG configuration is always provided in the following cases: if either the configured BWP of the UE 102 or the RedCap UE 102, other than the initial BWP, does not include frequency domain resources of the SSB associated with the initial DL BWP, and for the RedCap UE 102, NCD-SSB for serving cell measurements is not configured. In a non-gap-assisted scenario, the UE 102 can perform such measurements without using an MG. In a gap-assisted scenario, the UE 102 cannot assume that it can perform such measurements without the MG.

[0141] The network (e.g., the RAN 104 and / or RAN node 114) may request the UE 102 to measure NR and / or E-UTRA carriers in RRC_IDLE or RRC_INACTIVE via system information or via a dedicated measurement configuration in the RRCRelease message. If the UE 102 is configured to perform measurements on NR and / or E-UTRA carriers while in RRC_IDLE or RRC_INACTIVE, it may provide an indication of the availability of the corresponding measurements to the gNB 114a in the RRCSetupComplete message. The network may request the UE 102 to report these measurements after security activation. The request for measurements can be sent by the network immediately after sending the security mode command (e.g., before receiving security mode complete from the UE 102).

[0142] If the UE 102 is configured to perform measurements on the NR and / or E-UTRA carriers while in RRC_INACTIVE, the gNB 114a can request the UE 102 to provide the corresponding measurement results in an RRCResume message, and the UE 102 can then include the available measurement results in an RRCResumeComplete message. Additionally or alternatively, the UE 102 can provide an indication of the availability of the measurement results to the gNB 114a in the RRCResumeComplete message, and the gNB 114a can then request the UE 102 to provide these measurements.

[0143] 3. Example Implementation 5 illustrates an example process 500 that may be performed by a UE 102 capable of operating in NR-DC, including FR1+FR1 NR-DC. Process 500 begins with operation 501, in which the UE 102 determines a measurement occasion on which to perform one or more signal measurements. The UE 102 determines the measurement occasion based on at least one measurement configuration of at least two measurement configurations obtained from the network (e.g., the RAN 104 and / or the RAN node 114) and stored by the UE 102, the at least two measurement configurations including a first measurement configuration for an MCG cell operating in FR1 and a second measurement configuration for an SCG cell operating in FR1. The measurement occasion may include, for example, a configured MG, SMTC period, or CSI-RS resource period, any of which may include a period for PSS / SSS detection, a period for time index detection, and / or a measurement period for performing intra-frequency and / or inter-frequency measurements. In operation 502, the UE 102 determines or derives a carrier-specific scaling factor (CSSF). In operation 503, the UE 102 scales or adjusts the determined measurement occasion based on the CSSF. In operation 504, the UE 102 performs one or more signal measurements during the scaled measurement occasion.

[0144] 6 shows an example process 600 that may be performed by a UE 102 that is not configured with an MG. In some examples, process 600 may be performed at operation 502 of process 500. Process 600 begins at operation 601, in which the UE 102 determines a CSSF for an FR1 PCC. In one example, the CSSF for the FR1 PCC is 1+N PCC_CSIRS and N PCC_CSIRS is the number of configured PCells, and N is the number of configured PCells if the FR1 PCC is configured with either both SSB and CSI-RS based L3 measurements or only CSI-RS based L3 measurements. PCC_CSIRS is 1, otherwise N PCC_CSIRS is 0. In operation 602, the UE 102 determines the CSSF for the FR1 SCC. In one example, the CSSF for the FR1 SCC is 2×(N SCC_SSB +Y+2×N SCC_CSIRS ) and N SCC_SSB is the number of configured SCells when only SSB-based L3 measurements are configured, measured without MG, and N SCC_CSIRS where ∑ is the number of configured SCells when both SSB and CSI-RS based L3 measurements are configured or when only CSI-RS based L3 measurements are configured, and Y is the number of configured inter-frequency SSB based frequency layers without MG that are measured outside of MG, otherwise Y is 0. In operation 603, the UE 102 determines the CSSF for the FR1 PSCC, if necessary. In one example, the CSSF for the FR1 PSCC is 2×(1+N PSCC_CSIRS ) and if the PSCC consists of both SSB and CSI-RS based L3 measurements or only CSI-RS based L3 measurements, then N PSCC_CSIRS is 1, otherwise N PSCC_CSIRSis 0. In this example, if no SCell is configured, there is no gapless inter-frequency MO, and only SSB-based L3 measurements are configured on the PSCC, the CSSF is 1, and if no SCell is configured, there is no gapless inter-frequency MO, and both SSB- and CSI-RS-based L3 measurements are configured, or only CSI-RS-based L3 measurements are configured on the PSCC, the CSSF is 2. In operation 604, the UE 102 determines the CSSF for inter-frequency MO without MG, if necessary. In one example, the CSSF for inter-frequency MO without MG is 2×(N SCC_SSB +Y+2×N SCC_CSIRS ) and N SCC_SSB is the number of configured SCells when only SSB-based L3 measurements are configured, measured without MG, and N SCC_CSIRS is the number of configured SCells when both SSB and CSI-RS based L3 measurements are configured or when only CSI-RS based L3 measurements are configured, and Y is the number of configured inter-frequency SSB based frequency layers without MG that are being measured outside the MG; otherwise, Y is 0.

[0145] 7 illustrates an example process 700 that may be performed by a UE 102 configured with an MG. In some examples, process 700 may be performed at operation 502 of process 500. Process 700 may begin at operation 701, in which the UE 102 determines whether the number of NR PRS measurements and configured inter-frequency and inter-RAT MOs on all positioning frequency layers is non-zero and whether the UE 102 is configured with per-UE gapping or per-FR gapping. If so, the UE 102 proceeds to operation 702 and determines to classify the intra-frequency MOs of the FR1 PCell and the intra-frequency MOs of the FR1 PSCell as belonging to a first group (Group A), and in operation 703, the UE 102 determines or classifies up to one NR PRS measurement and inter-frequency and inter-RAT MOs on any one positioning frequency layer as belonging to a second group (Group B). In operation 701, if the UE 102 determines that the number of NR PRS measurements on all positioning frequency layers and the number of configured inter-frequency and inter-RAT MOs are zero, the UE 102 proceeds to operation 703, where it determines or classifies the intra-frequency MOs of the FR1 PCell as belonging to a first group (Group A), and then proceeds to operation 704, where it determines or classifies the intra-frequency MOs of the FR1 PSCell as belonging to a second group (Group B). In operation 705, the UE 102 determines an appropriate CSSF based on the MG sharing scheme and the number of MOs in the first and second groups. In operation 703, the UE 102 determines the configuration of the intra-frequency MOs of the primary cell to the first group in response to the PRS measurements on all positioning frequency layers and the number of inter-frequency and inter-RAT MOs being zero and that the UE is configured with per-UE gaps. In operation 704, the UE 102 determines the configuration of intra-frequency MO of the primary secondary cell into the second group in response to the PRS measurements on all positioning frequency layers and the number of inter-frequency and inter-RAT MOs being 0, and the UE being configured with a gap per UE.

[0146] The example operations of processes 500-700 may be arranged in a different order, one or more of the operations shown may be combined and / or divided / separated into multiple operations, operations shown may be omitted, and / or additional or alternative operations may be included in any of the processes shown.

[0147] Further examples of the methods, devices, systems, and networks described herein that are discussed herein include the following non-limiting implementations: Each of the following non-limiting examples may stand on its own or may be combined in any permutation or combination with any one or more of the other examples provided below or throughout this disclosure.

[0148] Example 1 includes a method including that requirements for NR new radio (NR new radio) dual connectivity (DC) for frequency range 1 (FR1)+FR1 are applicable to user equipment (UE) configured with multiple serving NR component carriers (CCs).

[0149] Example 2 includes the method of Example 1 and / or any other example herein, wherein the multiple serving NR CCs include one UL in a primary cell (PCell), one UL in a primary secondary cell group cell (PSCell), and up to one UL in each secondary cell (SCell), for a total of up to 10 NR DL CCs.

[0150] Example 3 includes the method of Example 1 and / or any other example herein, wherein the multiple serving NR CCs include up to five NR DL CCs in the PCell and up to five DL CCs in the PSCell, along with one UL in the PCell, one UL in the PSCell, and up to one UL in each SCell.

[0151] Example 4 includes the method of Example 1 and / or any other example herein, wherein the multiple serving NR CCs include one UL in the PCell, one UL in the PSCell, and up to eight UL SCells, for a total of up to 10 NR DL CCs.

[0152] Example 5 includes the method of Examples 1 to 4 and / or any other example herein, wherein for PSCell addition in FR1+FR1 NR-DC, the delay is T config_PSCell =T RRC_delay +T processing +T search +T Δ +T PSCell_DU +2ms, T RRC_delay is the radio resource control (RRC) procedure delay, and T processing is the software (SW) processing time required by the UE, including the RF warm-up period, and T search is the time for automatic gain control (AGC) settling and primary / secondary synchronization signal (PSS / SSS) detection, and T Δ is the time for fine time tracking and collection of complete timing information of the target cell, and T PSCell_DU is the delay uncertainty in acquiring the first available physical random access channel (PRACH) opportunity in the primary secondary cell (PSCell), and T PSCell_DU is up to the sum of the synchronization signal block (SSB) to PRACH opportunity association period plus 10 milliseconds (ms).

[0153] Example 6 includes the method of example 5 and / or any other example herein, wherein if the target cell is known, T search =0ms.

[0154] Example 7 includes the method of example 5 and / or any other example herein, further comprising: search =(24*T rs )ms.

[0155] Example 8 includes the methods of Example 5 and / or any other example herein, and is not intended to limit the scope of the present invention. search =(3*T rs )ms.

[0156] Example 9 includes the method of Examples 6-8 and / or any other example herein, further comprising: if the UE includes an SSB-based Measurement Timing configuration (SMTC) for the target cell in the PSCell Add message, rs is the SMTC period of the target cell, otherwise, T rs is the SMTC configured in measObjectNR with the same SSB frequency and subcarrier spacing.

[0157] Example 10 includes the method of example 9 and / or any other example herein, wherein if the UE is not provided with an SMTC configuration or measurement object on this frequency and the SSB transmission period is 5 ms, T rs =5ms.

[0158] Example 11 includes the methods of Examples 5-10 and / or any other examples herein, and processing = 40 ms or T processing =20ms.

[0159] Example 12 includes the methods of Examples 5-11 and / or any other examples herein, and is further directed to determining the T Δ=(1*T rs )ms.

[0160] Example 13 includes the method of Examples 1-12 and / or any other example herein, wherein there is no scheduling restriction on the FR1 serving cell due to radio link monitoring (RLM) performed on the FR1 PSCell.

[0161] Example 14 includes the method of Examples 1-13 and / or any other example herein, wherein the method comprises determining a measurement gap (CSSF) for FR1+FR1 NR-CSSF. outside_gap,i This includes determining a carrier-specific scaling factor (CSSF) for measurements made outside the

[0162] Example 15 includes the method of Example 14 and / or any other example herein, and outside_gap,i is 1+N for the FR1 primary component carrier (PCC). PCC_CSIRS is.

[0163] Example 16 includes the method of Example 15 and / or any other example herein, wherein when the PCC is configured with only CSI-RS based L3 measurements or with both SSB and CSI-RS based L3 measurements, N PCC_CSIRS = 1, otherwise N PCC_CSIRS =0.

[0164] Example 17 includes the method of Example 14 and / or any other example herein, and outside_gap,i is 2×(1+N PSCC_CSIRS )

[0165] Example 18 includes the method of Example 17 and / or any other example herein, wherein when the PSCC is configured with both SSB and CSI-RS based L3 measurements or configured with only CSI-RS based L3 measurements, N PSCC_CSIRS = 1, otherwise N PSCC_CSIRS =0.

[0166] Example 19 includes the method of Examples 17-18 and / or any other example herein, further including: when an SCell is not configured, a gapless inter-frequency measurement object is not configured, and / or only SSB-based L3 measurements are configured on the PSCC, the CSSF outside_gap,i =1.

[0167] Example 20 includes the method of Examples 17-18 and / or any other example herein, further comprising: when an SCell is not configured, a gapless inter-frequency measurement object is not configured, and / or both SSB and CSI-RS based L3 measurements are configured on the PSCC, or only CSI-RS based L3 measurements are configured on the PSCC, outside_gap,i =2.

[0168] Example 21 includes the method of Example 14 and / or any other example herein, and outside_gap,i is 2×(N SCC_SSB +Y+2×N SCC_CSIRS )

[0169] Example 22 includes the method of Example 14 and / or any other example herein, and outside_gap,i is 2×(N SCC_SSB +Y+2×N SCC_CSIRS )

[0170] Example 23 includes the method of Example 14 and / or any other example herein, and is outside_gap,i is 2×(N SCC_SSB+Y+2×N SCC_CSIRS )

[0171] Example 24 includes the method of Examples 21-23 and / or any other example herein, wherein Y is the number of configured inter-frequency SSB-based frequency layers without measurement gaps that are being measured outside of the measurement gap, and otherwise Y=0.

[0172] Example 25 includes the methods of Examples 21-24 and / or any other examples herein, and SCC_CSIRS is the number of configured SCells when configured with both SSB and CSI-RS based L3 measurements or when configured with only CSI-RS based L3 measurements.

[0173] Example 25 includes the methods of Examples 21-24 and / or any other examples herein, and SCC_SSB is the number of configured SCells when configured with only SSB-based L3 measurements, measured without measurement gaps.

[0174] Example 26 includes the method of Examples 1-25 and / or any other example herein, wherein the method comprises determining a measurement gap (CSSF) for FR1+FR1 NR DC. within_gap,i ) includes determining a CSSF for the target measurement object to be monitored.

[0175] Example 27 includes the method of Example 26 and / or any other example herein, wherein when the measurement gap sharing scheme is an equal sharing scheme, the CSSF within_gap,i =max(ceil(R i ×M tot,i,j )), where j=0...(160 / MGRP)-1, max is the maximum function, ceil is the ceiling function, and R i is the maximum ratio of the number of measurement gaps in which measurement object i is a candidate to be measured to the number of measurement gaps j, and M tot,i,j is the total number of measurement objects in group A and group B, where group A and group B contain different sets of measurement objects.

[0176] Example 28 includes the method of Example 26 and / or any other example herein, wherein when the measurement gap sharing scheme is not an equal sharing scheme and the measurement object i is a measurement object of group A, the CSSF within_gap,i is (i) M groupB,i,j ceil(R i ×K intra ×M groupA,i,j ) and (ii) M groupB,i,j = 0 and ceil(R i ×M groupA,i,j ) and if measurement object i is a measurement object in group B, then CSSF within_gap,i (iii) M groupA,i,j ceil(R i ×K inter ×M groupB,i,j ) and (iv) M groupA,i,j = 0 and j = 0...(160 / MGRP)-1 in the gap i ×M groupB,i,j ) and is the largest among them, max is the maximum function, ceil is the ceiling function, and R i is the maximum ratio of the number of measurement gaps in which measurement object i is a candidate to be measured to the number of measurement gaps j, and M groupA,i,j is the number of measurement objects in FR1 frequency in group A, and M groupB,i,j is the number of intra-FR1 frequency measurement objects in group B.

[0177] Example 29 includes the method of Example 28 and / or any other example herein, wherein the FR1 intra-frequency measurement object in group A is a master cell group (MCG) measurement object and the FR1 intra-frequency measurement object in group B is a secondary cell group (SCG) measurement object.

[0178] Example 30 includes the method of Examples 27-29 and / or any other example herein, wherein when the number of Positioning Reference Signal (PRS) measurements and configured inter-frequency and inter-RAT measurement objects on all positioning frequency layers is non-zero and the UE is configured with per-UE measurement gaps, the intra-frequency measurement objects of the FR1 PCell and FR1 PSCell belong to Group A, and up to one NR PRS measurement and inter-frequency and inter-RAT measurement objects on any one positioning frequency layer belong to Group B.

[0179] Example 31 includes the method of Examples 27-29 and / or any other example herein, wherein when the number of NR PRS measurements on all positioning frequency layers and the number of configured inter-frequency and inter-RAT measurement objects are zero and the UE is configured with per-UE measurement gaps, the intra-frequency measurement objects of the FR1 PCell belong to group A and the intra-frequency measurement objects of the FR1 PSCell belong to group B.

[0180] Example 32 includes the method of Examples 27-29 and / or any other example herein, wherein when the number of NR PRS measurements on all positioning frequency layers and configured inter-frequency and inter-RAT measurement objects is zero and the UE is configured with per-UE measurement gaps, the intra-frequency measurement object of the FR1 PCell and the intra-frequency measurement object of the FR1 PSCell belong to only Group A or only Group B.

[0181] Example 33 includes the method of Examples 1-32 and / or any other example herein, where the method is performed by a user equipment (UE).

[0182] Example 34 includes a method of configuring user equipment (UE) with a new radio (NR) network, including: assigning intra-frequency measurement objects of a primary cell operating in a first frequency range and a primary secondary cell operating in the first frequency range to a first group in response to a number of NR positioning reference signal (PRS) measurement and inter-frequency and inter-radio access technology (RAT) measurement objects on all positioning frequency layers being greater than zero and the UE being configured with per-UE gaps; assigning up to one NR PRS measurement and inter-frequency and inter-RAT measurement object for one of the positioning frequency layers to a second group in response to a number of NR PRS measurement and inter-frequency and inter-RAT measurement objects on all positioning frequency layers being greater than zero and the UE being configured with per-UE gaps; assigning intra-frequency measurement objects of the primary cell to the first group in response to a number of NR PRS measurement and inter-frequency and inter-RAT measurement objects on all positioning frequency layers being zero and the UE being configured with per-UE gaps; and allocating intra-frequency measurement objects of the primary secondary cell to a second group in response to the number of PRS measurements and inter-frequency and inter-RAT measurement objects being zero and the UE being configured with a per-UE gap.

[0183] Example 35 includes a method for configuring user equipment (UE) connected to a new radio (NR) network, including: receiving an assignment of intra-frequency measurement objects for a primary cell operating in a first frequency range and a primary secondary cell operating in the first frequency range to a first group in response to a number of NR Positioning Reference Signal (PRS) measurements and inter-frequency and inter-radio access technology (RAT) measurement objects on all positioning frequency layers being greater than zero and the UE being configured with a per-UE gap; receiving an assignment of NR PRS measurements and inter-frequency and inter-RAT measurement objects for up to one of the positioning frequency layers to a second group in response to a number of NR PRS measurements and inter-frequency and inter-RAT measurement objects on all positioning frequency layers being zero and the UE being configured with a per-UE gap; receiving an assignment of intra-frequency measurement objects for the primary cell to the first group in response to a number of NR PRS measurements and inter-frequency and inter-RAT measurement objects on all positioning frequency layers being zero and the UE being configured with a per-UE gap; and receiving an allocation of intra-frequency measurement objects of the primary secondary cell to a second group in response to the number of PRS measurements and inter-frequency and inter-RAT measurement objects being zero and the UE being configured with a per-UE gap.

[0184] Example Z01 includes an apparatus including means for performing one or more elements of a method described in or related to any of Examples 1-35, or any other method or process described herein. Example Z02 includes one or more non-transitory computer-readable media including instructions that, upon execution by one or more processors of the electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 1-35, or any other method or process described herein. Example Z03 includes an apparatus including logic, modules, or circuitry that performs one or more elements of a method described in or related to any of Examples 1-35, or any other method or process described herein. Example Z04 includes a method, technique, or process described in or related to any of Examples 1-35, or a portion or part thereof. Example Z05 includes an apparatus including one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described or related to any of Examples 1-35. Example Z06 includes a signal described or related to any of Examples 1-35, or a portion or portion thereof. Example Z07 includes a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples 1-35, or a portion or portion thereof, or otherwise described in this disclosure. Example Z08 includes a signal encoded with data described or related to any of Examples 1-35, or a portion or portion thereof, or otherwise described in this disclosure. Example Z09 includes a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples 1-35, or a portion or portion thereof, or otherwise described in this disclosure. Example Z10 includes an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process, or portion thereof, described or related to any of Examples 1-35. Example Z11 includes a computer program including instructions, where execution of the program by a processing element causes the processing element to perform a method, technique, or process, or portion thereof, described or related to any of Examples 1-35. Example Z12 includes a signal in a wireless network as shown and described herein. Example Z13 includes a method of communicating in a wireless network as shown and described herein. Example Z14 includes a system for providing wireless communications as shown and described herein. Example Z15 includes a device for providing wireless communications as shown and described herein.

[0185] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise specified. The above description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0186] [4. Terminology] For the purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed herein. As used herein, the singular forms "a," "an," "the," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. It is further understood that the terms "comprises" and / or "comprising," as used herein, specify the presence of the referenced features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The phrase "A and / or B" means (A), (B), or (A and B). For the purposes of this disclosure, the phrase "A, B, and / or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C). The term "X" means one or more Xs or a set of Xs. The description may use phrases such as "in one embodiment," "in some embodiments," "in one implementation," "in some implementations," "in some examples," etc., each of which may refer to one or more of the same or different embodiments, implementations, and / or examples. Furthermore, terms such as "comprising," "including," and "having" as used in connection with this disclosure are synonymous.

[0187] The term "circuit" in at least some examples refers to a circuit or a system of circuits configured to perform a particular function in an electronic device. A circuit or system of circuits may be part of or include one or more hardware components, such as logic circuits, processors (shared, dedicated, or group), and / or memories (shared, dedicated, or group), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic controllers (PLCs), single-board computers (SBCs), systems on chips (SoCs), systems in packages (SiPs), multi-chip packages (MCPs), digital signal processors (DSPs), etc., configured to provide the described functionality. Furthermore, the term "circuit" may also refer to a combination of one or more hardware elements and program code used to perform the function of the program code. Some types of circuits may execute one or more software or firmware programs to provide at least some of the described functionality. Such a combination of hardware elements and program code may be referred to as a particular type of circuit. The term "processor circuitry" in at least some examples refers to, is part of, or includes circuitry that is capable of sequentially and automatically performing a series of arithmetic or logical operations, or that is capable of recording, storing, and / or transferring digital data.The term "processor circuitry" in at least some examples refers to one or more application processors, one or more baseband processors, a physical CPU, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or running computer-executable instructions such as program code, software modules, and / or functional processes. The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry." The terms “memory” and / or “memory circuitry” in at least some examples refer to one or more hardware devices for storing data, including random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), magnetoresistive RAM (MRAM), conductive bridge random access memory (CB-RAM), spin transfer torque (STT)-MRAM, phase change RAM (PRAM), core memory, read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), flash memory, non-volatile RAM (NVRAM), magnetic disk storage media, optical storage media, flash memory devices, or other machine-readable media for storing data.The term "computer-readable medium" includes, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions or data. The term "interface circuitry" in at least some examples refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" in at least some examples refers to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0188] The term "device" in at least some examples refers to a physical entity embedded within or attached to another physical entity in its vicinity, and has the ability to communicate digital information to or from that physical entity. The term "controller" in at least some examples refers to an element or entity that has the ability to affect a physical entity, such as by changing its state or moving the physical entity. The term "scheduler" in at least some examples refers to an entity or element that allocates resources (e.g., processor time, network links, memory space, etc.) to perform tasks. The terms "network scheduler," "packet scheduler," "queuing discipline," or "qdisc" in at least some examples refer to a node, element, or entity that manages network packets in transmit and / or receive queues of one or more protocol stacks of network access circuitry (e.g., network interface controller, baseband processor, etc.).

[0189] The terms “computing node” or “computing device” in at least some examples refer to an identifiable entity that implements some aspect of a computing operation, whether part of a larger system, a distributed collection of systems, or a standalone device. In some examples, a computing node may be referred to as a “computing device,” a “computing system,” or the like, whether operating as a client, server, or intermediate entity. Particular implementations of a computing node may be incorporated into a server, base station, gateway, roadside unit, on-premise unit, user equipment, end consumption device, appliance, or the like. For purposes of this disclosure, the term “node” in at least some examples refers to and / or is interchangeable with terms such as “device,” “component,” “subsystem,” etc.

[0190] The term "user equipment" or "UE" in at least some examples refers to a device having wireless communication capabilities and may describe a remote user of network resources in a communications network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, station, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" includes any type of wireless / wired device or any computing device that includes a wireless communication interface. Examples of UEs, client devices, etc. include desktop computers, workstations, laptop computers, mobile data terminals, smartphones, tablet computers, wearable devices, machine-to-machine (M2M) devices, machine-type communication (MTC) devices, Internet of Things (IoT) devices, embedded systems, sensors, autonomous vehicles, drones, robots, in-vehicle infotainment systems, instrument clusters, on-board diagnostic devices, dash-top mobile devices, electronic engine management systems, electronic / engine control units / modules, microcontrollers, control modules, server devices, network appliances, head-up display (HUD) devices, helmet-mounted display devices, augmented reality (AR) devices, virtual reality (VR) devices, mixed reality (MR) devices, and / or other similar systems or devices.

[0191] The term "network access node" or "NAN" in at least some examples refers to a network element in a radio access network (RAN) responsible for transmitting and receiving radio signals to and from UEs or stations within one or more cells or coverage areas. A "network access node" or "NAN" may have an integrated antenna or may be connected to an antenna array by a feeder cable. Additionally or alternatively, a "network access node" or "NAN" includes dedicated digital signal processing, network function hardware, and / or computational hardware for operating as a computational node. In some examples, a "network access node" or "NAN" may be divided into multiple functions (e.g., RAN functions) or functional blocks that are operated in software for flexibility, cost, and performance. In some examples, a "network access node" or "NAN" may be a base station (e.g., an evolved node B (eNB) or next generation Node B (gNB)), an access point and / or wireless network access point, a router, a switch, a hub, a radio unit or remote radio head, a Transmission Reception Point (TRP), a gateway device (e.g., a residential gateway, a wireline 5G access network, a wireline 5G cable access network, a wireline BBF access network, etc.), a network appliance, and / or some other network access hardware. The term "network controller" in at least some examples refers to a functional block that may centralize some or all of the control and management functions of a network domain and provide an abstract view of the network domain to other functional blocks via interfaces.The term "access point" or "AP" in at least some examples refers to an entity that contains one station (STA) and provides access to distribution services over a wireless medium (WM) for an associated STA. The AP includes the STA and a distribution system access function (DSAF).

[0192] The term "cell" in at least some examples refers to a wireless network object that can be uniquely identified by a UE from an identifier (e.g., a cell ID) broadcast throughout a geographic area from a network access node (NAN). Additionally or alternatively, the term "cell" in at least some examples refers to a geographic area covered by the NAN. In at least some examples, the term "serving a cell" refers to a UE in idle mode that has completed a cell selection / reselection process and selected a cell, and in some examples, the UE monitors system information and (in most cases) paging information. The term "serving cell" in at least some examples refers to a primary cell (PCell) for a UE that is in a connected mode or state (e.g., RRC_CONNECTED) and is not configured with carrier aggregation (CA) and / or dual connectivity (DC). Additionally or alternatively, the term "serving cell" in at least some examples refers to a set of cells that includes zero or more special cells and one or more secondary cells for a UE that is in a connected mode or state (e.g., RRC_CONNECTED) and configured with CA. The term "primary cell" or "PCell" in at least some examples refers to a master cell group (MCG) cell operating on a primary frequency on which a UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure. The term "primary SCG cell" in at least some examples refers to a secondary cell group (SCG) cell to which a UE performs random access when performing a reconfiguration in a synchronization procedure for DC operation. The terms "primary secondary cell," "primary SCG cell," or "PSCell" in at least some examples refer to a primary cell of a secondary cell group (SCG).The term "conditional PSCell addition" or "CPA" in at least some examples refers to a PSCell addition procedure that is performed only when a PSCell addition execution condition is met. The term "conditional PSCell modification" or "CPC" in at least some examples refers to a PSCell modification procedure that is performed only when a PSCell modification execution condition is met. The term "conditional PSCell addition or modification" or "CPAC" in at least some examples refers to CPA and / or CPC. The term "secondary cell" or "SCell" in at least some examples refers to a cell that provides additional radio resources over a special cell (SpCell) for a UE configured with carrier aggregation (CA). The term "special cell" or "SpCell" in at least some examples refers to a PCell for non-DC operation, or a PCell of an MCG or a PSCell of an SCG for DC operation. In some examples, the terms "PCell" and "PSCell" are collectively referred to as "special cell," "SpCell," or "SpCell."

[0193] The term "master cell group" or "MCG" in at least some examples refers to a group of serving cells associated with a "master node" that includes an SpCell (PCell) and zero or more SCells. The term "secondary cell group" or "SCG" in at least some examples refers to a subset of serving cells that includes at least one primary SCell (PSCell, primary SCell) for a UE configured with dual connectivity (DC) and optionally zero or more SCells.

[0194] The term "handover" or "HO" in at least some examples refers to the transfer of a user's connection from one radio channel to another (which may be the same cell or a different cell). Additionally or alternatively, the term "handover" or "HO" in at least some examples refers to a process by which a radio access network changes the radio transmitter, radio access mode, and / or radio system used to provide a bearer service while maintaining a defined bearer service QoS.

[0195] The term "master node" or "MN" in at least some examples refers to a NAN that provides a control plane connection to a core network. The term "secondary node" or "SN" in at least some examples refers to a NAN that provides resources to a UE in addition to resources provided by a MN and / or a NAN that does not have a control plane connection to a core network.

[0196] The term "E-UTEAN Node B," "eNodeB," or "eNB" in at least some examples refers to a RAN node that provides E-UTRA user plane (PDCP / RLC / MAC / PHY) and control plane (e.g., RRC) protocol terminations for UEs and is connected to an Evolved Packet Core (EPC) via an S1 interface. Two or more eNBs are interconnected with each other (and / or with one or more en-gNBs) by an X2 interface. The term "next-generation eNB" or "ng-eNB" in at least some examples refers to a RAN node that provides E-UTRA user plane and control plane protocol terminations for UEs and is connected to a 5GC via an NG interface. Two or more ng-eNBs are interconnected with each other (and / or with one or more gNBs) by an Xn interface. The term "next-generation Node B," "gNodeB," or "gNB" in at least some examples refers to a RAN node that provides NR user plane and control plane protocol terminations for UEs and is connected to a 5GC via an NG interface. Two or more gNBs are interconnected to each other (and / or with one or more ng-eNBs) by an Xn interface. The term "E-UTRA-NR gNB" or "en-gNB" in at least some examples refers to a RAN node that provides NR user plane and control plane protocol terminations toward the UE and serves as a secondary node in an E-UTRA-NR Dual Connectivity (EN-DC) scenario (see, e.g., 3GPP TS37.340 v17.0.0(2022-04-15) ("TS37340"). Two or more en-gNBs are interconnected to each other (and / or with one or more eNBs) by an X2 interface. The term "next generation RAN node" or "NG-RAN node" in at least some examples refers to either a gNB or an ng-eNB.The term "IAB node" in at least some examples refers to a RAN node that supports new radio (NR) access links to user equipment (UE) and NR backhaul links to parent and child nodes. The term "IAB donor" in at least some examples refers to a RAN node (e.g., gNB) that provides network access to UEs via a network of backhaul and access links. The term "transmit / receive point" or "TRP" in at least some examples refers to an antenna array having one or more antenna elements available to the network located at a particular geographic location for a particular area.

[0197] The term "central unit" or "CU" in at least some examples refers to a logical node that hosts the radio resource control (RRC), Service Data Adaptation Protocol (SDAP) and / or Packet Data Convergence Protocol (PDCP) protocol / layers of an NG-RAN node, or the RRC and PDCP protocols of an en-gNB that controls the operation of one or more DUs, and the CU terminates an F1 interface connected to the DU and may be connected to multiple DUs. The term "distributed unit" or "DU" in at least some examples refers to a logical node that hosts the backhaul adaptation protocol (BAP), F1 application protocol (F1AP), radio link control (RLC), medium access control (MAC), and physical (PHY) layers of an NG-RAN node or en-gNB, the operation of which is partially controlled by a CU, where one DU supports one or more cells, where one cell is supported by only one DU, and where the DU terminates an F1 interface connected to the CU. The term "radio unit" or "RU" in at least some examples refers to a logical node that hosts the PHY layer or lower PHY layer and radio frequency (RF) processing based on a division of lower layer functions. The term "split architecture" in at least some examples refers to an architecture in which the CU, DU, and / or RU are physically separated from each other. Additionally or alternatively, the term "split architecture" in at least some examples refers to a RAN architecture such as those discussed in [TS38401], [TS38410], and / or [TS38473], the entire contents of each of which are incorporated herein by reference.The term "integrated architecture" in at least some examples refers to an architecture in which the RU and DU are implemented on one platform, and / or an architecture in which the DU and CU are implemented on one platform.

[0198] The term "Network Function" or "NF" in at least some examples refers to a functional block within a network infrastructure having one or more external interfaces and defined functional behavior. The term "Application Function" or "AF" in at least some examples refers to an element or entity that interacts with a 3GPP core network to provide a service. Additionally or alternatively, the term "Application Function" or "AF" in at least some examples refers to an edge compute node or ECT framework from the perspective of a 5G core network. The term "Virtualized Network Function" or "VNF" in at least some examples refers to an implementation of an NF that can be deployed on a Network Function Virtualization Infrastructure (NFVI). The term "Network Function Virtualization Infrastructure Manager" or "NFVI" in at least some examples refers to the entire set of all hardware and software components that make up the environment in which a VNF is deployed.

[0199] The terms “virtualization container,” “execution container,” or “container” in at least some examples refer to a partition of a compute node that provides an isolated virtualized computing environment. The term “OS container” in at least some examples refers to a virtualized container that utilizes its host’s shared operating system (OS) kernel, where the host providing the shared OS kernel can be a physical compute node or another virtualized container. Additionally or alternatively, the term “container” in at least some examples refers to a standard unit of software (or package) that includes code and its associated dependencies, and / or an abstraction at the application layer that packages code and dependencies together. Additionally or alternatively, the term “container” or “container image” in at least some examples refers to a lightweight, standalone, executable software package that includes everything needed to run an application, e.g., code, runtime environment, system tools, system libraries, and configuration. The term “virtual machine” or “VM” in at least some examples refers to a virtualized computing environment that operates in the same or similar manner as a physical computer and / or server. The term "hypervisor" in at least some examples refers to a software element that partitions the underlying physical resources of a compute node, creates VMs, manages resources for the VMs, and isolates individual VMs from each other.

[0200] The term "protocol" in at least some examples refers to a predetermined procedure or method for performing one or more operations. Additionally or alternatively, the term "protocol" in at least some examples refers to a common means (sometimes called an interface) by which unrelated objects communicate with each other. The term "communications protocol" in at least some examples refers to a standardized set of rules or instructions implemented by a communication device and / or system to communicate with other devices and / or systems, including instructions for packetizing / depacketizing data, instructions for modulating / demodulating signals, a protocol stack implementation, etc. The term "protocol stack" or "network stack" in at least some examples refers to an implementation of a protocol suite or protocol family. In various implementations, a protocol stack includes a set of protocol layers, with the lowest protocols handling low-level interaction with hardware and / or communication interfaces, and each higher layer adding further capabilities. Additionally or alternatively, the term "protocol" in at least some examples refers to a formal set of procedures employed to ensure communication between two or more functions within the same layer of a hierarchy of functions.

[0201] The term "session layer" in at least some examples refers to an abstraction layer that controls interactions and / or connections between entities or elements, and may include establishing, managing, and terminating connections between entities or elements. The term "transport layer" in at least some examples refers to a protocol layer that provides end-to-end (e2e) communication services, such as connection-oriented communication, reliability, flow control, and multiplexing. Examples of transport layer protocols include Datagram Congestion Control Protocol (DCCP), Fibre Channel Protocol (FBC), Generic Routing Encapsulation (GRE), GPRS Tunneling (GTP), Micro Transport Protocol (μTP), Multipath TCP (MPTCP), Multipath QUIC (MPQUIC), Multipath UDP (MPUDP), Quick UDP Internet Connections (QUIC), Remote Direct Memory Access (RDMA), Resource Reservation Protocol (RSVP), Stream Control Transmission Protocol (SCTP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), etc.

[0202] The term "network layer" in at least some examples refers to a protocol layer that includes means for forwarding network packets from a source to a destination over one or more networks. Additionally or alternatively, the term "network layer" in at least some examples refers to a protocol layer that is responsible for packet forwarding and / or routing through intermediate nodes. Additionally or alternatively, the term "network layer" or "internet layer" in at least some examples refers to a protocol layer that includes interworking methods, protocols, and specifications used to forward network packets between networks. By way of example, network layer protocols include Internet Protocol (IP), IP security (IPsec), Internet Control Message Protocol (ICMP), Internet Group Management Protocol (IGMP), Open Shortest Path First protocol (OSPF), Routing Information Protocol (RIP), RDMA over Converged Ethernet version 2 (RoCEv2), Subnetwork Access Protocol (SNAP), and / or some other internet or network protocol layer. The terms "link layer" or "data link layer" in at least some instances refer to a protocol layer that transfers data between nodes on a network segment between physical layers.Examples of link layer protocols include logical link control (LLC), medium access control (MAC), Ethernet, RDMA over Converged Ethernet version 1 (RoCEv1), etc.

[0203] The terms "Radio Resource Control," "RRC layer," or "RRC" in at least some examples refer to a protocol layer or sublayer that performs system information handling, paging, establishment, maintenance, and release of RRC connections, security functions, establishment, configuration, maintenance, and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs), mobility functions / services, QoS management, and some sidelink-specific services and functions over the Uu interface (see, e.g., 3GPP TS 36.331 v17.5.0(2023-07-04) and / or 3GPP TS 38.331 v17.5.0(2023-07-01) ("[TS38331]").

[0204] The terms "Service Data Adaptation Protocol," "SDAP layer," or "SDAP" in at least some examples refer to a protocol layer or sublayer that performs mapping between QoS flows and data radio bearers (DRBs) and marking QoS flow IDs (QFIs) in both DL and UL packets (e.g., 3GPP TS 37.324 v17.0.0 (2022-04-13)). The terms "Packet Data Convergence Protocol," "PDCP layer," or "PDCP" in at least some examples refer to a protocol layer or sublayer that performs forwarding of user plane data or control plane data, maintains PDCP sequence numbers (SNs), and implements the Robust Header Compression (ROHC) protocol and / or Ethernet Header Compression (EHC) protocol. Header compression and decompression using the Header Compression protocol, encryption and decryption, integrity protection and integrity verification, timer-based SDU discarding, routing for split bearers, duplication and duplicate discarding, reordering and in-order delivery, and / or out-of-order delivery (see, e.g., 3GPP TS 36.323 v17.2.0 (2023-01-13) and / or 3GPP TS 38.323 v17.5.0 (2023-06-30)).

[0205] The terms "Radio Link Control layer," "RLC layer," or "RLC" in at least some examples refer to a protocol layer or sublayer that performs the transfer of upper layer PDUs, sequence numbering independent of that in PDCP, error correction through ARQ, segmentation and / or re-segmentation of RLC SDUs, SDU reassembly, duplicate detection, RLC SDU discarding, RLC re-establishment, and / or protocol error detection (see, e.g., 3GPP TS 36.322 v17.0.0 (2022-04-15) and 3GPP TS 38.322 v17.3.0 (2023-06-30)).

[0206] The terms "medium access control protocol," "MAC protocol," or "MAC" in at least some examples refer to a protocol that manages access to a transmission medium in a network to enable the exchange of data between stations in the network. Additionally or alternatively, the terms "medium access control layer," "MAC layer," or "MAC" in at least some examples refer to a protocol layer or sublayer that performs functions to provide a frame-based, connectionless mode (e.g., datagram-style) transfer of data between stations or devices. Additionally or alternatively, the terms "medium access control layer," "MAC layer," or "MAC" in at least some examples may refer to a protocol layer or sublayer that performs mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels to / from transport blocks (TBs) delivered to / from the physical layer on the transport channels, scheduling information reporting, error correction through HARQ (one HARQ entity per cell in case of CA), priority handling between UEs through dynamic scheduling, priority handling between logical channels of one UE through logical channel prioritization, priority handling and / or padding between overlapping resources of one UE (see, e.g., 3GPP TS 36.321 v17.5.0 (2023-06-30) and 3GPP TS 38.321 v17.5.0 (2023-06-30)).

[0207] The terms "physical layer," "PHY layer," or "PHY" in at least some examples refer to a protocol layer or sublayer that includes capabilities for transmitting and receiving modulated signals for communication in a communications network (see, e.g., 3GPP TS 36.201 v17.0.0 (2022-03-31) and 3GPP TS 38.201 v17.0.0 (2022-01-05)).

[0208] The term "access technology" in at least some examples refers to a technology used for the underlying physical connection to a communications network. The term "radio access technology" or "RAT" in at least some examples refers to a technology used for the underlying physical connection to a radio-based communications network. The term "wireless technology" in at least some examples refers to a technology for wireless transmission and / or reception of electromagnetic radiation for information transfer. The term "RAT type" in at least some examples may identify a transmission technology and / or communication protocol used in an access network. Examples of access technologies include wired access technologies, RATs, optical fiber networks, digital subscriber line (DSL), coaxial cable access technologies, hybrid fiber-coaxial (HFC) technologies, etc.

[0209] The term "channel" in at least some examples refers to a transmission medium, either tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term referring to a path or medium over which data is communicated. Furthermore, the term "link" in at least some examples refers to a connection between two devices through a RAT for the purpose of sending and receiving information.

[0210] The term "carrier" in at least some examples refers to a modulated waveform that carries one or more physical channels (e.g., 5G / NR, E-UTRA / LTE, UTRA, GSM / EDGE physical channels). The term "carrier frequency" in at least some examples refers to a center frequency of a cell.

[0211] The term "bearer" in at least some examples refers to an information transmission path with a defined capacity, delay, bit error rate, etc. The term "radio bearer" in at least some examples refers to a service provided by Layer 2 (L2) for the transfer of user data between a user equipment (UE) and a radio access network (RAN). The term "radio access bearer" in at least some examples refers to a service provided by the access stratum to the non-access stratum for the transfer of user data between a UE and a CN.

[0212] The terms "instantiate," "instantiation," and the like in at least some examples refer to the creation of an instance. In some examples, the term "instance" in at least some examples also refers to a specific occurrence of an object that may occur, for example, during the execution of program code. The term "reference point" or "reference point" in at least some examples refers to a conceptual point in the joining of two non-overlapping functional groups, elements, or entities. The term "reference" in at least some examples refers to data that can be used to locate other data and may be implemented in various ways (e.g., a pointer, an index, a handle, a key, an identifier, a hyperlink, etc.).

[0213] The term "use case" in at least some examples refers to a description of a system from a user's perspective. Use cases, in some cases, treat the system as a black box, and interactions with the system, including system responses, are perceived as being from outside the system. In some examples, use cases avoid technical jargon, instead favoring the language of end users or domain experts. The term "user" in at least some examples refers to an abstract representation of any entity that issues commands, requests, and / or data to a computational node or system and / or consumes or uses services. Additionally or alternatively, the term "user" in at least some examples refers to an entity that uses 3GPP system services but is not part of the 3GPP system (e.g., a person who uses a 3GPP system mobile station as a mobile phone). The term "user profile" in at least some examples refers to a set of information used to provide a consistent, personalized service environment to a user, regardless of the user's location or the terminal used (within the confines of the terminal and serving network).

[0214] The term "datagram" in at least some examples refers to a basic transmission unit associated with a packet-switched network, and a datagram may be structured to have a header section and a payload section. The term "datagram" in at least some examples may be synonymous with any of the following terms: "data unit," "protocol data unit" or "PDU," "service data unit" or "SDU," "frame," "packet," "network packet," "segment," "block," "cell," "chunk," "type-length-value" or "TLV," etc., even though these terms may refer to different aspects. Examples of datagrams, network packets, etc. include Internet Protocol (IP) packets, Internet Control Message Protocol (ICMP) packets, UDP packets, TCP packets, SCTP packets, ICMP packets, Ethernet frames, RRC messages / packets, SDAP PDUs, SDAP SDUs, PDCP PDUs, PDCP SDUs, MAC PDUs, MAC SDUs, and BAP PDUs. BAP SDUs, RLC PDUs, RLC SDUs, and WiFi frames, as discussed in IEEE protocols / standards (e.g., IEEE 802.11, etc.), include Type Length Values (TLVs) and / or other similar data structures. The term "packet" in at least some examples refers to an information unit identified by a label at Layer 3 of the OSI reference model. In some examples, a "packet" may also be referred to as a "Network Protocol Data Unit" or "NPDU." The term "protocol data unit" in at least some examples refers to a unit of data specified in the (N) protocol layer and consisting of (N) protocol control information and possibly (N) user data.

[0215] The term "information element" or "IE" in at least some examples refers to a structural element that includes one or more fields. Additionally or alternatively, the term "information element" or "IE" in at least some examples refers to a field or set of fields defined in a standard or specification used to convey data and / or protocol information. The term "field" in at least some examples refers to the individual contents of an information element or a data element that includes the contents. The term "data frame," "data field," or "DF" in at least some examples refers to a data type that includes more than one data element in a predetermined order. The term "data element" or "DE" in at least some examples refers to a data type that includes one single piece of data. Additionally or alternatively, the term "data element" in at least some examples refers to the atomic state of a particular object having at least one particular property at a particular point in time and may include one or more of a data element name or identifier, a data element definition, one or more expression terms, enumerated values or codes (e.g., metadata), and / or a list of synonyms for the data element in another metadata registry. Additionally or alternatively, the term "data element" in at least some examples refers to a data type that includes one single piece of data.

[0216] The terms “configuration,” “policy,” “rule set,” and / or “operational parameters” in at least some examples refer to machine-readable information objects that include instructions, conditions, parameters, and / or criteria associated with a device, system, or other element / entity. The term “data set” or “dataset” in at least some examples refers to a collection of data, and a “dataset” or “dataset” may be formed or arranged in any type of data structure. In some examples, one or more characteristics can define or influence the structure and / or characteristics of a dataset, such as the number and type of attributes and / or variables and various statistical measures (e.g., standard deviation, kurtosis, etc.). The term “data structure” in at least some examples refers to data organization, management, and / or storage format. Additionally or alternatively, the term “data structure” in at least some examples refers to a collection of data values, relationships among these data values, and / or functions, operations, tasks, etc. that can be applied to the data. Examples of data structures include primitives (e.g., Booleans, characters, floating-point numbers, fixed-point numbers, integers, references or pointers, enumerations, etc.), composites (e.g., arrays, records, strings, unions, tagged unions, etc.), abstract data types (e.g., data containers, lists, tuples, associative arrays, maps, dictionaries, sets (or datasets), multisets or bags, stacks, queues, graphs (e.g., trees, heaps, etc.), etc.), routing tables, symbol tables, quad-edges, blockchains, purely functional data structures (e.g., stacks, queues, (multi)sets, random access lists, hash consing, zipper data structures, etc.).

[0217] The term "synchronization signal block" or "SSB" in at least some examples refers to a synchronization signal (SS) / physical broadcast channel (PBCH) block as defined in [TS38211]. The term "SSB-based measurement timing configuration" or "SMTC" in at least some examples refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration as specified in [TS38331].

[0218] Aspects of the inventive subject matter may be referred to individually and / or collectively herein for convenience only, without intending to intentionally limit the scope of the application to any single aspect or inventive concept when in fact more than one is disclosed. Thus, while specific aspects have been illustrated and described herein, it should be recognized that any configuration calculated to achieve the same purpose may be substituted for the specific aspect shown. The present disclosure is intended to cover any and all adaptations or variations of the various aspects. Combinations of the above aspects with other aspects not specifically described herein will be apparent to those skilled in the art upon reviewing the above description.

Claims

1. A device for use as user equipment (UE) capable of operating in New Radio (NR)-NR Dual Connectivity (NR-DC), a memory circuit configured to store at least two measurement configurations for corresponding cells among at least two cells that provide radio resources to the UE while operating in NR-DC, the at least two cells operating within Frequency Range 1 (FR1); and a processor circuit connected to the memory circuit; the processor circuitry includes: determining a measurement occasion for performing one or more signal measurements based on at least one measurement configuration of the at least two measurement configurations; determining a carrier-specific scaling factor (CSSF); scaling the determined measurement occasion based on the CSSF; An apparatus that performs the one or more signal measurements during the scaled measurement occasion.

2. 2. The apparatus of claim 1, wherein the at least two measurement configurations include a first measurement configuration for a master cell group (MCG) cell operating in FR1 and a second measurement configuration for a secondary cell group (SCG) cell operating in FR1.

3. When the at least one measurement configuration does not include a measurement gap (MG) configuration, the CSSF is configured to outside_gap,i ) The device of claim 1 .

4. The processor circuitry includes: For FR1 Primary Component Carrier (PCC), the CSSF outside_gap,i is 1+N PCC_CSIRS and If the FR1 PCC is configured with only Channel State Information Reference Signal (CSI-RS)-based Layer 3 (L3) measurements, or with both CSI-RS L3 measurements and Synchronization Signal Block (SSB)-based L3 measurements, N PCC_CSIRS The apparatus of claim 3, wherein is 1.

5. The processor circuitry includes: For FR1 Secondary Component Carriers (SCCs) or for inter-frequency measurement objects (MOs) without MGs, the CSSF outside_gap,i is 2×(N SCC_SSB +Y+2×N SCC_CSIRS ) and N SCC_SSB is the number of configured secondary cells (SCells) when configured with only SSB-based L3 measurements measured without MG, N SCC_CSIRS is the number of configured SCells when both SSB and CSI-RS based L3 measurements are configured or when only CSI-RS based L3 measurements are configured; 4. The apparatus of claim 3, wherein Y is the number of configured inter-frequency SSB-based frequency layers without MG, measured outside the MG.

6. The processor circuitry includes: For FR1 Primary Secondary Component Carrier (PSCC), the CSSF outside_gap,i is 2×(1+N PSCC_CSIRS ) and If the PSCC is configured with both SSB and CSI-RS based L3 measurements, or is configured with only CSI-RS based L3 measurements, N PSCC_CSIRS The apparatus of claim 3, wherein is 1.

7. If an SCell is not configured, inter-frequency MO without MG is not configured, and only SSB-based L3 measurements are configured on the PSCC, the CSSF outside_gap,i is 1, If an SCell is not configured, inter-frequency MO without MG is not configured, and both SSB and CSI-RS based L3 measurements are configured on the PSCC, or only CSI-RS based L3 measurements are configured, the CSSF outside_gap,i 7. The apparatus of claim 6, wherein is 2.

8. When the at least one measurement configuration includes an MG configuration, the CSSF may be configured to monitor the CSSF for measurements to be monitored in the MG (CSSF within_gap,i ) The device of claim 1 .

9. When the MG sharing method is an equal sharing method, the CSSF within_gap,i =max(ceil(R i ×M tot,i,j )) where j=0...(160 / MGRP)-1, max is the maximum function, ceil is the ceiling function R i is the maximum ratio of the number of MGs that are candidates for measuring MOi to the number of MGj, M tot,i,j is the total number of MOs in both group A and group B, where group A and group B contain different MOs; The apparatus of claim 8 , wherein MGRP is the MG repetition period indicated by the MG configuration.

10. When the MG sharing method is not equal sharing and MOi is an MO of group A, the CSSF within_gap,i teeth, M groupB,i,j ceil(R i ×K intra ×M groupA,i,j )and, M groupB,i,j = 0 and j = 0...(160 / MGRP)-1 i ×M groupA,i,j )and It is the largest of max is the maximum function, ceil is the ceiling function, R i is the maximum ratio of the number of MGs that are candidates for measuring MOi to the number of MGj, M groupA,i,j is the number of FR1 MOs in group A, M groupB,i,j is the number of FR1 MOs in group B, The apparatus of claim 8 , wherein MGRP is the MG repetition period indicated by the MG configuration.

11. When the MG sharing method is not equal sharing and MOi is an MO of group B, the CSSF within_gap,i teeth, M groupA,i,j ≠0 and ceil(R i ×K inter ×M groupB,i,j )and, M groupA,i,j = 0, and ceil(R i ×M groupB,i,j )and It is the largest of max is the maximum function, ceil is the ceiling function, R i is the maximum ratio of the number of MGs that are candidates for measuring MOi to the number of MGj, M groupA,i,j is the number of FR1 MOs in group A, M groupB,i,j is the number of FR1 MOs in group B, The apparatus of claim 8 , wherein MGRP is the MG repetition period indicated by the MG configuration.

12. The device of claim 10, wherein the FR1 MOs in group A are intra-frequency MOs of an MCG, and the FR1 MOs in group B are intra-frequency MOs of an SCG.

13. 11. The apparatus of claim 10, wherein when the number of positioning reference signal (PRS) measurements on all positioning frequency layers and configured inter-frequency and inter-Radio Access Technology (RAT) measurement gaps is zero, and when the UE is configured with per-UE measurement gaps based on the MG configuration, an FR1 measurement gap in the group A is an FR1 primary cell (PCell) intra-frequency measurement gap, and an FR1 measurement gap in the group B is an FR1 primary secondary cell (PSCell) intra-frequency measurement gap.

14. 11. The apparatus of claim 10, wherein when a number of PRS measurements on all positioning frequency layers and configured inter-frequency and inter-RAT MOs is non-zero and the UE is configured with per-UE measurement gaps or per-FR measurement gaps based on the MG configuration, FR1 MOs in the group A are FR1 PCell intra-frequency MOs and FR1 PSCell intra-frequency MOs, and FR1 MOs in the group B are up to one PRS measurement and inter-frequency and inter-RAT MOs on any one of the positioning frequency layers.

15. 1. A method of operating a user equipment (UE) in New Radio (NR)-NR Dual Connectivity (NR-DC), comprising: receiving a radio resource control (RRC) message including a first measurement configuration for a master cell group (MCG) cell operating in frequency range 1 (FR1), a second measurement configuration for a secondary cell group (SCG) cell operating in FR1, or both the first measurement configuration and the second measurement configuration; determining a measurement occasion for performing one or more signal measurements based on at least one of the first measurement configuration or the second measurement configuration; determining a carrier specific scaling factor (CSSF); scaling the determined measurement occasion based on the CSSF; performing the one or more signal measurements during the scaled measurement occasion; A method comprising:

16. When the at least one measurement configuration does not include a measurement gap (MG) configuration, the CSSF is configured to outside_gap,i 16. The method of claim 15, wherein

17. The method comprises: For FR1 Primary Component Carrier (PCC), the CSSF outside_gap,i is 1+N PCC_CSIRS determining that If the FR1 PCC is configured with only Channel State Information Reference Signal (CSI-RS)-based Layer 3 (L3) measurements, or with both CSI-RS L3 measurements and Synchronization Signal Block (SSB)-based L3 measurements, N PCC_CSIRS The method of claim 16, wherein is 1.

18. The method comprises: For FR1 Secondary Component Carriers (SCCs) or for inter-frequency measurement objects (MOs) without MGs, the CSSF outside_gap,i is 2×(N SCC_SSB +Y+2×N SCC_CSIRS ) determining that N SCC_SSB is the number of configured secondary cells (SCells) when configured with only SSB-based L3 measurements measured without MG, N SCC_CSIRS is the number of configured SCells when both SSB and CSI-RS based L3 measurements are configured or when only CSI-RS based L3 measurements are configured; 17. The method of claim 16, wherein Y is the number of configured inter-frequency SSB-based frequency layers without MG, measured outside the MG.

19. The method comprises: For FR1 Primary Secondary Component Carrier (PSCC), the CSSF outside_gap,i is 2×(1+N PSCC_CSIRS ) determining that If the PSCC is configured with both SSB and CSI-RS based L3 measurements, or is configured with only CSI-RS based L3 measurements, N PSCC_CSIRS is 1, If an SCell is not configured, inter-frequency MO without MG is not configured, and only SSB-based L3 measurements are configured on the PSCC, the CSSF outside_gap,i is 1, If an SCell is not configured, inter-frequency MO without MG is not configured, and both SSB and CSI-RS based L3 measurements are configured on the PSCC, or only CSI-RS based L3 measurements are configured, the CSSF outside_gap,i 17. The method of claim 16, wherein is 2.

20. When the at least one measurement configuration includes an MG configuration, the CSSF may be configured to monitor the CSSF for measurements to be monitored in the MG (CSSF within_gap,i 16. The device of claim 15, wherein

21. When the MG sharing method is an equal sharing method, the CSSF within_gap,i =max(ceil(R i ×M tot,i,j )) where j=0...(160 / MGRP)-1, max is the maximum function, ceil is the ceiling function R i is the maximum ratio of the number of MGs that are candidates for measuring MOi to the number of MGj, M tot,i,j is the total number of MOs in both group A and group B, where group A and group B contain different MOs; 21. The method of claim 20, wherein MGRP is the MG repetition period indicated by the MG configuration.

22. When the MG sharing method is not an equal sharing method, When MOi is an MO of Group A, the CSSF within_gap,i teeth, M groupB,i,j ceil(R i ×K intra ×M groupA,i,j )and, M groupB,i,j = 0 and j = 0...(160 / MGRP)-1 i ×M groupA,i,j )and It is the largest of When MOi is a MO of Group B, the CSSF within_gap,i teeth, M groupA,i,j ≠0 and ceil(R i ×K inter ×M groupB,i,j )and, M groupA,i,j = 0, and ceil(R i ×M groupB,i,j )and It is the largest of max is the maximum function, ceil is the ceiling function, R i is the maximum ratio of the number of MGs that are candidates for measuring MOi to the number of MGj, M groupA,i,j is the number of FR1 MOs in group A, M groupB,i,j is the number of FR1 MOs in group B, 21. The method of claim 20, wherein MGRP is the MG repetition period indicated by the MG configuration.

23. 22. The method of claim 21, wherein the FR1 MOs in group A are intra-frequency MOs of an MCG, and the FR1 MOs in group B are intra-frequency MOs of an SCG.

24. 22. The method of claim 21, wherein when the number of positioning reference signal (PRS) measurements on all positioning frequency layers and configured inter-frequency and inter-Radio Access Technology (RAT) measurements is zero, and when the UE is configured with per-UE measurement gaps based on the MG configuration, the FR1 measurements in the group A are FR1 primary cell (PCell) intra-frequency measurements, and the FR1 measurements in the group B are FR1 primary secondary cell (PSCell) intra-frequency measurements.

25. A computer program causing a user equipment to carry out the method of any one of claims 15 to 24.

26. 26. A computer-readable storage medium storing the computer program of claim 25.

Images