EARL Y MEASUREMENT REPORTING TO SECOND NODE

Related Applications

This application claims the benefit of provisional patent application serial number 62/868,655, filed June 28, 2019, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates to early measurement reporting in a cellular communications system.

Background

1 Secondary Node Addition

Multi-Radio Access Technology (RAT) Dual Connectivity (MR-DC) is a

generalization of the Intra-Evolved Universal Terrestrial Radio Access (Intra-E-UTRA) Dual Connectivity (DC), where a multiple Receive/Transmit (Rx/Tx) User Equipment (UE) may be configured to use resources provided by two different nodes connected via non-ideal backhaul, one providing New Radio (NR) access and the other one providing either Evolved Universal Terrestrial Radio Access (E-UTRA) or NR access. One node acts as the Master Node (MN) and the other as the Secondary Node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network.

For E-UTRA-NR DC (EN-DC), the SN Addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE. For bearers requiring Secondary Cell Group (SCG) radio resources, this procedure is used to add at least the first cell of the SCG. This procedure can also be used to configure an SN terminated Master Cell Group (MCG) bearer where no SCG

configuration is needed. The SN Addition procedure is illustrated in Figure 1. The SN Addition procedure for EN-DC is described in Third Generation Partnership Project (3GPP) Technical Specification (TS) 37.340 V15.5.0 as follows: 1. The MN decides to request the SN to allocate resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters, TNL address information corresponding to bearer type). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG

configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. The MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. In case of bearer options that require X2-U resources between the MN and the SN, the MN provides X2-U TNL address information for the respective E-RAB, X2-U DL TNL address information for SN terminated bearers, X2-U UL TNL address information for MN terminated bearers. In case of SN terminated split bearers the MN provides the maximum QoS level that it can support. The SN may reject the request.

NOTE 1 : For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MNs decision is reflected in step 1 by the E-RAB parameters signalled to the SN, which may differ from E-RAB parameters received over S1.

NOTE 2: For a specific E-RAB, the MN may request the direct establishment of an SCG or a split bearer, i.e., without first having to establish an MCG bearer. It is also allowed that all E- RABs can be configured as SN terminated bearers, i.e. there is no E-RAB established as an MN terminated bearer.

2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer option, respective transport network resources. For bearers requiring SCG radio resources, the SN triggers Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN in a NR RRC configuration message contained in the SgNB Addition Request Acknowledge message. In case of bearer options that require X2-U resources between the MN and the SN, the SN provides X2-U TNL address information for the respective E-RAB, X2-U UL TNL address information for SN terminated bearers, X2-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the S1 -U DL TNL address information for the respective E- RAB and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided.

NOTE 3: For the SN terminated split bearer option, the SN may either decide to request resources from the MN of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MN and the SN together, or even more. The SNs decision is reflected in step 2 by the E-RAB parameters signalled to the MN, which may differ from E-RAB parameters received in step 1. The QoS level requested from the MN shall not exceed the level that the MN offered when setting up the split bearer in step 1.

NOTE 4: In case of MN terminated bearers, transmission of user plane data may take place after step

2

NOTE 5: In case of SN terminated bearers, data forwarding and the SN Status Transfer may take place after step 2.

3. The MN sends to the UE the RRCConnectionReconfiguration message including the NR RRC configuration message, without modifying it.

In the case of Fifth Generation (5G) MR-DC, the SN Addition procedure is initiated by the MN and is used to establish a UE context at the SN in order to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the initial SCG serving cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG

configuration is needed). The SN Addition procedure is illustrated in Figure 2. The SN Addition procedure for 5G MR-DC is described in 3GPP TS 37.340 V15.5.0 as follows:

For SN terminated bearer options that require Xn-U resources between the MN and the SN, the MN provides in step 1 a list of QoS flows per PDU Sessions for which SCG resources are requested to be setup upon which the SN decides how to map QoS flows to DRB.

NOTE 1 : For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective QoS Flow is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the QoS Flow parameters signalled to the SN, which may differ from QoS Flow parameters received over NG.

NOTE 2: For a specific QoS flow, the MN may request the direct establishment of SCG and/or split bearers, i.e. without first having to establish MCG bearers. It is also allowed that all QoS flows can be mapped to SN terminated bearers, i.e. there is no QoS flow mapped to an MN terminated bearer.

2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer type options, respective transport network resources. For bearers requiring SCG radio resources the SN triggers UE Random Access so that

synchronisation of the SN radio resource configuration can be performed. The SN decides for the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN within an SN RRC configuration message contained in the SN Addition Request Acknowledge message. In case of bearer options that require Xn-U resources between the MN and the SN, the SN provides Xn-U TNL address information for the respective DRB, Xn-U UL TNL address information for SN terminated bearers, Xn-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the NG-U DL TNL address information for the respective PDU Session and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided.

NOTE 3: In case of MN terminated bearers, transmission of user plane data may take place after step

2

NOTE 4: In case of SN terminated bearers, data forwarding and the SN Status Transfer may take place after step 2.

NOTE 5: For MN terminated NR SCG bearers for which PDCP duplication with CA is configured the MN allocates 2 separate Xn-U bearers.

For SN terminated NR MCG bearers for which PDCP duplication with CA is configured the SN allocates 2 separate Xn-U bearers.

2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message.

3. The MN sends the MN RRC reconfiguration message to the UE including the SN RRC

configuration message, without modifying it.

4. The UE applies the new configuration and replies to MN with MN RRC reconfiguration complete message, including an SN RRC response message for SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure.

5. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the SN RRC response message, if received from the UE.

2 Inter-node Radio Resource Control (RRC) messages

For both EN-DC and MR-DC, it is clear that the MN may make decisions to add an SCG based on measurement reports. In the case of MR-DC, an SN Addition Request from the MN provides the latest measurement results for the SN to choose and configure the SCG cell(s). In the EN-DC case, this is the Secondary NR base station (SgNB) Addition Request. In fact, these measurements are included in inter-node messages in a RRC container. These messages from the MN to the SN are shown below.

In the E-UTRA specification, the MN can generate the following messages:

}

}

SCG-Configl nfo-r12-I Es ::= SEQUENCE {

radioResourceConfigDedMCG-r12 RadioResourceConfigDedicated OPTIONAL, sCellToAddModListMCG-r12 SCellToAddModList-r10 OPTIONAL, measGapConfig-r12 MeasGapConfig OPTIONAL, powerCoordi nation I nfo-r12 PowerCoordinationlnfo-r12 OPTIONAL, scg-RadioConfig-r12 SCG-ConfigPartSCG-r12 OPTIONAL, eutra-Capabilitylnfo-r12 OCTET STRING (CONTAINING UECapabilitylnformation)

OPTIONAL,

scg-ConfigRestrictlnfo-r12 SCG-ConfigRestrictl nfo-r12 OPTIONAL,

mbmslnterestlndication-r12 OCTET STRING (CONTAINING

MBMSInterestlndication-r11 ) OPTIONAL.

measResultServCellListSCG-r12 MeasResultServCellListSCG-r12 OPTIONAL,

drb-ToAddModListSCG-r12 DRB-lnfoListSCG-r12 OPTIONAL, drb-ToReleaseListSCG-r12 DRB-ToReleaseList OPTIONAL, sCellT oAddModListSCG-r12 SCellToAddModListSCG-r12 OPTIONAL, sCellToReleaseListSCG-r12 SCellToReleaseList-r10 OPTIONAL, p-Max-r12 P-Max OPTIONAL, nonCriticalExtension SCG-Configl nfo-v1310-l Es OPTIONAL

SCG-Configl nfo-v1310-l Es ::= SEQUENCE {

measResultSSTD-r13 MeasResultSSTD-r13 OPTIONAL, sCellToAddModListMCG-Ext-r13 SCellToAddModListExt-r13 OPTIONAL, measResultServCellListSCG-Ext-r13 MeasResultServCellListSCG-Ext-r13 OPTIONAL, sCellToAddModListSCG-Ext-r13 SCellToAddModListSCG-Ext-r13 OPTIONAL, sCellToReleaseListSCG-Ext-r13 SCellToReleaseListExt-r13 OPTIONAL, nonCriticalExtension SCG-Configlnfo-v1330-IEs OPTIONAL

}

SCG-Configl nfo-v1330-I Es ::= SEQUENCE {

measResultListRSSI-SCG-r13 MeasResultListRSSI-SCG-r13 OPTIONAL, nonCriticalExtension SCG-Configl nfo-v1430-I Es OPTIONAL

}

SCG-Configl nfo-v1430-I Es ::= SEQUENCE {

makeBeforeBreakSCG-Req-r14 ENUMERATED {true} OPTIONAL, measGapConfigPerCC-List MeasGapConfigPerCC-List-r14 OPTIONAL, nonCriticalExtension SCG-Configl nfo-v1530-I Es OPTIONAL

}

SCG-Configl nfo-v1530-IEs ::= SEQUENCE {

drb-ToAddModListSCG-r15 DRB-lnfoListSCG-r15 OPTIONAL, drb-ToReleaseListSCG-r15 DRB-ToReleaseList-r15 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL

}

DRB-lnfoListSCG-r12 ::= SEQUENCE (SIZE (l.maxDRB)) OF DRB-lnfoSCG-r12

DRB-lnfoListSCG-r15 ::= SEQUENCE (SIZE (1..maxDRB-r15)) OF DRB-lnfoSCG-r12 DRB-lnfoSCG-r12 ::= SEQUENCE {

eps-Bearerldentity-r12 INTEGER (0..15) OPTIONAL, - Cond DRB-Setup drb-ldentity-r12 DRB-ldentity,

drb-Type-r12 ENUMERATED {split, scg} OPTIONAL, - Cond DRB-Setup

}

SCellToAddModListSCG-r12 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF Cell-ToAddMod-r12

SCellToAddModListSCG-Ext-r13 ::= SEQUENCE (SIZE (1..maxSCell-r13)) OF Cell-ToAddMod-r12

Cell-T oAddMod-r12 ::= SEQUENCE {

sCelllndex-r12 SCelllndex-r10,

cellldentification-r12 SEQUENCE {

physCellld-r12 PhysCellld,

dl-CarrierFreq-r12 ARFCN-ValueEUTRA-r9

} OPTIONAL, - Cond

SCellAdd

measResultCellToAdd-r12 SEQUENCE {

rsrpResult-r12 RSRP-Range,

rsrqResult-r12 RSRQ-Range

} OPTIONAL, - Cond

SCellAdd2

[[ sCelllndex-r13 SCelllndex-r13 OPTIONAL,

measResultCellToAdd-v1310 SEQUENCE {

rs-sinr-Result-r13 RS-SINR-Range-r13

} OPTIONAL - Cond

SCellAdd2

]]

}

MeasResultServCellListSCG-r12 ::= SEQUENCE (SIZE (1..maxServCell-r10)) OF

MeasResultServCellSCG-r12

MeasResultServCellListSCG-Ext-r13 ::= SEQUENCE (SIZE (1..maxServCell-r13)) OF

MeasResultServCellSCG-r12

MeasResultServCellSCG-r12 ::= SEQUENCE {

servCellld-r12 ServCelllndex-r10,

measResultSCell-r12 SEQUENCE {

rsrpResultSCell-r12 RSRP-Range,

rsrqResultSCell-r12 RSRQ-Range

},

[[ servCellld-r13 ServCelllndex-r13 OPTIONAL,

measResultSCell-v1310 SEQUENCE {

rs-sinr-ResultSCell-r13 RS-SINR-Range-r13

} OPTIONAL ]]

}

MeasResultListRSSI-SCG-r13 ::= SEQUENCE (SIZE (1..maxServCell-r13)) OF MeasResultRSSI-SCG- r13

MeasResultRSSI-SCG-r13 ::= SEQUENCE {

servCellld-r13 ServCelllndex-r13,

measResultForRSSI-rl 3 MeasResultForRSSI-r13

SCG-Configlnfo field descriptions

I drb-ToAddModUstSCG

j Includes DRBs the SeNB is requested to establish or modify (DRB type change). When drb- j I ToAddModListSCG-r15 is configured, UE shall ignore the drb-ToAddModListSCG-r12.

j drb foReleaseListSCG

j Includes DRBs the SeNB is requested to release. When drb-ToReleaseListSCG-r15 is configured, j [ UE shall ignore the drb-ToReleaseListSCG-r12.

\ makeBeforeBreakSCG Req

j To request the target eNB to add the makeBeforeBreakSCG indication in the mobilityControllnfoSCG j in case of intra-frequency SCG change. j maxSCH-TB-BitsXL

Indicates the maximum DL-SCH/UL-SCH TB bits that may be scheduled in a TTI. Specified as a | percentage of the value defined for the applicable UE categor meas esu

Includes measurement results of UE SFN and Subframe Timing Difference between the PCell j i and the PSCell.

sCellToAddModListMCG, sCellToAddModListMCG-Ext

j Includes the current MCG SCell configuration. Field sCellToAddModListMCG is used to add the first j j 4 SCells with sCelllndex-r10 while sCellToAddModListMCG-Ext is used to add the rest.

sCellToAddModListSCG, sCellToAddModListSCG-Ext

j Includes SCG cells the SeNB is requested to establish. Measurement results may be provided for j ! these cells. Field sCellToAddModListSCG is used to add the first 4 SCells with sCelllndex-r12 while j ! sCellToAddModListSCG-Ext is used to add the rest.

In the current NR specification, the MN can generate the following message: configRestrictl nfo ConfigRestrictlnfoSCG OPTIONAL, drx-lnfoMCG DRX-lnfo OPTIONAL,

measConfigMN MeasConfigMN OPTIONAL, sourceConfigSCG OCTET STRING (CONTAINING RRCReconfiguration)

OPTIONAL,

scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig)

OPTIONAL,

mcg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig)

OPTIONAL,

mrdc-Assistancelnfo MRDC-Assistancelnfo OPTIONAL, nonCriticalExtension CG-Configlnfo-v1540-IEs OPTIONAL

}

MeasResultList2NR ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR

CG-Configlnfo-v1540-IEs ::= SEQUENCE {

ph-lnfoMCG PH-TypeListMCG OPTIONAL, measResultReportCGI SEQUENCE {

ssbFrequency ARFCN-ValueNR,

cellForWhichToReportCGI PhysCellld,

cgi-lnfo CGI-lnfoNR

} OPTIONAL,

nonCriticalExtension CG-Configlnfo-v1560-IEs OPTIONAL

}

CG-Configlnfo-v1560-IEs ::= SEQUENCE {

candidateCelllnfoListMN-EUTRA OCTET STRING OPTIONAL,

candidateCelllnfoListSN-EUTRA OCTET STRING OPTIONAL,

sourceConfigSCG-EUTRA OCTET STRING OPTIONAL, scgFailurelnfoEUTRA SEQUENCE {

failureTypeEUTRA ENUMERATED { t313-Expiry, randomAccessProblem,

rlc-MaxNumRetx, scg-ChangeFailure},

measResultSCG-EUTRA OCTET STRING

} OPTIONAL,

drx-ConfigMCG DRX-Config OPTIONAL, measResultReportCGI-EUTRA SEQUENCE {

eutraFrequency ARFCN-ValueEUTRA,

cellForWhichToReportCGI-EUTRA EUTRA-PhysCellld,

cgi-lnfoEUTRA CGI-lnfoEUTRA

} OPTIONAL,

measResultCellListSFTD-EUTRA MeasResultCellListSFTD-EUTRA

OPTIONAL,

fr-lnfoListMCG FR-lnfoList OPTIONAL,

nonCriticalExtension SEQUENCE {} OPTIONAL

}

ConfigRestrictlnfoSCG ::= SEQUENCE {

allowedBC-ListMRDC BandCombinationlnfoList OPTIONAL, powerCoordination-FR1 SEQUENCE {

p-maxNR-FR1 P-Max OPTIONAL,

p-maxEUTRA P-Max OPTIONAL, p-maxUE-FR1 P-Max OPTIONAL

} OPTIONAL,

servCelllndexRangeSCG SEQUENCE {

lowBound ServCelllndex,

upBound ServCelllndex

} OPTIONAL, - Cond SN-AddMod maxMeasFreqsSCG INTEGER(1..maxMeasFreqsMN) OPTIONAL,

-- TBD Late Drop: If maxMeasldentitiesSCG is used needs to be decided after RAN4 replies to the LS on measurement requirements for MR-DC.

maxMeasldentitiesSCG-NR INTEGER(1..maxMeasldentitiesMN) OPTIONAL,

[[

maxNumberROHC-ContextSessionsSN INTEGER(0.. 16384)

OPTIONAL,

pdcch-BlindDetectionSCG INTEGER (1..15) OPTIONAL, selectedBandEntriesMN SEQUENCE (SIZE (1..maxSimultaneousBands)) OF

BandEntrylndex OPTIONAL

]]

}

BandEntrylndex ::= INTEGER (0.. maxNrofServingCells)

PH-TypeListMCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF PH-lnfoMCG

PH-lnfoMCG ::= SEQUENCE {

ServCelllndex ServCelllndex,

ph-Uplink PH-UplinkCarrierMCG,

ph-SupplementaryUplink PH-UplinkCarrierMCG OPTIONAL,

}

PH-UplinkCarrierMCG ::= SEQUENCE{

ph-Type1 or3 ENUMERATED {type1 , type3},

}

BandCombinationlnfoList ::= SEQUENCE (SIZE (l.maxBandComb)) OF BandCombinationlnfo

BandCombinationlnfo ::= SEQUENCE {

bandCombinationlndex BandCombinationlndex,

allowedFeatureSetsList SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF

FeatureSetEntrylndex

}

FeatureSetEntrylndex ::= INTEGER (1.. maxFeatureSetsPerBand)

DRX-lnfo ::= SEQUENCE {

d rx- Lo ng Cycl eStartOffset CHOICE {

ms10 INTEGER(0..9), ms20 INTEGER(0..19),

ms32 INTEGER(0..31 ),

ms40 INTEGER(0..39),

ms60 INTEGER(0..59),

ms64 INTEGER(0..63),

ms70 INTEGER(0..69),

ms80 INTEGER(0..79),

ms 128 INTEGER(0..127),

ms 160 INTEGER(0..159),

ms256 INTEGER(0..255),

ms320 INTEGER(0..319),

ms512 INTEGER(0..51 1 ),

ms640 INTEGER(0..639),

ms 1024 INTEGER(0..1023),

ms1280 INTEGER(0..1279),

ms2048 INTEGER(0..2047),

ms2560 INTEGER(0..2559),

ms5120 INTEGER(0..51 19),

ms10240 INTEGER(0..10239)

},

shortDRX SEQUENCE {

drx-ShortCycle ENUMERATED {

ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32,

ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9,

spare8, spare7, spare6, spare5, spare4, spare3, spare2, sparel }, drx-ShortCycleTimer INTEGER (1..16)

} OPTIONAL

}

MeasConfigMN ::= SEQUENCE {

measuredFrequenciesMN SEQUENCE (SIZE (1..maxMeasFreqsMN)) OF NR-Freqlnfo

OPTIONAL,

measGapConfig SetupRelease { GapConfig } OPTIONAL, gapPurpose ENUMERATED {perUE, perFRI } OPTIONAL,

[[

measGapConfigFR2 SetupRelease { GapConfig } OPTIONAL

]]

}

MRDC-Assistancelnfo ::= SEQUENCE {

affectedCarrierFreqComblnfoListMRDC SEQUENCE (SIZE (1..maxNrofComblDC)) OF

AffectedCarrierFreqComblnfoMRDC,

}

AffectedCarrierFreqComblnfoMRDC ::= SEQUENCE {

victimSystemType VictimSystemType, interferenceDirectionMRDC ENUMERATED {eutra-nr, nr, other, utra-nr-other, nr-other, spare3, spare2, sparel },

affectedCarrierFreqCombMRDC SEQUENCE {

affectedCarrierFreqCombEUTRA AffectedCarrierFreqCombEUTRA OPTIONAL, affectedCarrierFreqCombNR AffectedCarrierFreqCombNR

} OPTIONAL

VictimSystemType ::= SEQUENCE {

gps ENUMERATED {true} OPTIONAL,

glonass ENUMERATED {true} OPTIONAL,

bds ENUMERATED {true} OPTIONAL,

galileo ENUMERATED {true} OPTIONAL,

wlan ENUMERATED {true} OPTIONAL,

bluetooth ENUMERATED {true} OPTIONAL

}

AffectedCarrierFreqCombEUTRA ::= SEQUENCE (SIZE (1..maxNrofServingCellsEUTRA)) OF ARFCN-

ValueEUTRA

AffectedCarrierFreqCombNR ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF ARFCN-ValueNR

FR-lnfoList ::= SEQUENCE (SIZE (1..maxNrofServingCells-1 )) OF FR-lnfo

FR-lnfo ::= SEQUENCE {

servCelllndex ServCelllndex,

fr-Type ENUMERATED {fr1 , fr2}

}

- TAG-CG-CONFIGINFO-STOP

- ASN1 STOP

MeasResult2NR

The IE MeasResult2NR contains measurements on NR frequencies.

MeasResult2NR information element

- ASN1 START

- TAG-MEASRESULT2NR-START

MeasResult2NR ::= SEQUENCE {

ssbFrequency ARFCN-ValueNR OPTIONAL,

refFreqCSI-RS ARFCN-ValueNR OPTIONAL,

measResultServingCell MeasResultNR OPTIONAL,

measResultNeighCellListNR MeasResultListNR OPTIONAL,

}

- TAG-MEASRESULT2NR-STOP

- ASN1 STOP

3 Idle measurements for early reporting upon transition to Connected In Long Term Evolution (LTE) Release 15, it is possible to configure the UE to report so called early measurements upon the transition from idle to connected state. These measurements are measurements that the UE can perform in the idle state, and are performed by the UE according to a configuration provided by the source cell with the intention to receive these measurements immediately after the UE gets connected, so a Carrier Aggregation (CA) can be quickly setup without the need to first provide a measurement configuration (measConfig) in RRC_CONNECTED.

3.1 Measurement configuration for early measurements upon resume in

LTE

A first aspect of the existing solution, as standardized in E-UTRA TS 36.331 V15.5.1, is described in 5.6.20 Idle Mode Measurements. The UE can receive these idle mode measurement configurations in the System Information Block 5 (SIB5) in the field MeasIdleConfigSIB-rl5, indicating up to eight cells or ranges of cell identities (IDs) on which to perform measurements. In addition, the UE can be either configured upon the transition from RRC_CONNECTED to RRC_IDLE with a dedicated measurement configuration in the RRCConnectionRelease message with the measIdleDedicated-rl5 which overrides the broadcasted configurations in SIB5. The broadcasted and dedicated signaling is shown below:

Carrier information and cell list: The UE is provided with a list of carriers and optionally with a list of cells on which the UE shall perform measurements. The fields s- NonlntraSearch in SystemInformationBlockType3 do not affect the UE measurement procedures in IDLE mode.

Timer T331: Upon the reception of that measurement configuration, the UE starts a timer T331 with the value provided in measIdleDuration, which can go from 0 to 300 seconds. The timer stops upon receiving RRCConnectionSetup,

RRCConnection Resume which indicates a transition to RRC_CONNECTED. That concept exists to limit the amount of time the UE performs measurements for the purpose of early measurements.

Validity Area: Another concept introduced in the LTE Release 15 solution is a validity area, which comprises a list of Physical Cell Identities (PCIs). The intention is to limit the area where CA or DC may be setup later when the UE resumes/sets up the connection, so the early measurements are somewhat useful for that purpose. If validityArea is configured and the UE reselects to a serving cell whose PCI does not match any entry in validityArea for the corresponding carrier frequency, the timer T331 is stopped. Then, the UE stops to perform IDLE measurements and releases the configuration (i.e., VarMeasIdleConfig). Notice that this does not necessarily imply that the UE releases the idle measurements that were configured and that were performed, i.e. these may still be stored and possibly requested by the network. In addition, the UE may continue with IDLE mode measurements according to the broadcasted SIB5 configuration after the timer T331 has expired or stopped.

Minimum quality threshold: Notice also that only measurements above a certain threshold shall be stored as the cell candidates for CA setup need to be within a minimum acceptable threshold. How the UE performs measurements in IDLE mode is up to UE implementation as long as Radio Access Network (RAN) Working Group 4 (RAN4) requirements for measurement reporting defined in 36.133 are met.

The UE behavior is shown below in more detail as captured in TS 36.331 as follows:

3.2 Indication of available early measurements upon resume/setup in

LTE

Another aspect of the existing solution occurs when the UE tries to resume or setup a call from RRC_IDLE without context. If the previous step is performed, i.e., if the UE is configured to store idle measurements, the network may request the UE after resume / setup (after security is activated) to indicate whether the UE has idle measurements available.

In the case this UE is setting up a connection coming from RRC_IDLE without the Access Stratum (AS) Context, the network is not aware that the UE has available measurements stored. Then, to allow the network to know that, and possibly request the UE to report early measurements, the UE may indicate the availability of stored idle measurements in RRCConnectionSetupComplete. As not all cells would support the feature anyway, the UE only includes that availability information if the cell broadcasts the idieModeMeasurements indication in SIB2. The flag in

RRCReconnectionSetupComplete and procedure text are shown below:

In the case this UE is setting up a connection coming from RRC_IDLE but with a stored AS Context (i.e., resume from suspended), the network may be aware that the UE may have available idle measurements stored after checking the fetched context from the source node where the UE got suspended. However, it is still not certain that the UE has measurements available since the UE is only required to perform the measurements if the cells are above the configured Reference Signal Received Power (RSRP) / Reference Signal Received Quality (RSRQ) thresholds and while it performs cell selection/cell reselection within the configured validity area. Then, to allow the network to know that, and possibly request the UE to report early measurements, the UE may also indicate the availability of stored idle measurements in

RRCConnectionResumeComp/ete. As not all cells would support the feature anyway, the UE only includes that availability information if the cell broadcasts the

idleModeMeasurements indication in SIB2. The flag in

RRCReconnectionResumeComp/ete and procedure text are shown below:

3.3 Reporting of early measurements upon resume/setup in L TE

Once the UE indicates to the target cell upon resume or setup that idle measurements are available, the network may finally request the UE to report these available measurements by including the field idleModeMeasurementReq in the

UEInformationRequest message transmitted to the UE. Then, the UE responds with a UEInformation Response containing these measurements. Reception of the

UEInformationRequest message is illustrated in Figure 3 and described below, as in the current specification:

_ _

4 Introducing of early measurements upon idle/inactive to connected

transition in NR (Release 16)

A work item has been approved in Release 16 to enhance the setup of CA/DC in NR. The Work Item Description (WID) "Enhancing CA Utilization" was approved in RAN#80 in RP-181469 and updated in RAN#81 in RP-182076. One of the objectives of this WID is the following:

Early Measurement reporting: Early and fast reporting of measurements information availability from neighbor and serving cells to reduce delay setting up MR-DC and/or CA. [RAN2, RAN4]

o This objective applies to MR-DC, NR-NR DC and CA

o The objective should consider measurements in IDLE,

INACTIVE mode and CONNECTED mode

o The impacts on UE power consumption should be minimized o The LTE Rel-15 euCA work should be utilized, when

applicable

Hence, 3GPP is going to investigate solutions to enable early measurements performed when the UE is in RRC_INACTIVE or RRC_IDLE state and reporting mechanisms for when the UE enters RRC_CONNECTED. Three different kinds of solutions are being considered:

1. UE reports early measurements in UEInformation Response after a request from the network in UEInformationRequest is transmitted after the UE sends an RRCResumeComplete or after security is activated when the UE comes from idle without stored context (as in LTE Release 15);

2. UE reports early measurements with (e.g., multiplexed with or as part of the message) RRCResumeComplete; 3. UE reports early measurements with (e.g., multiplexed with or as part of the message) RRCResumeRequest.

There are some differences in details of each of these solutions, and not all of them may be applicable for RRC_IDLE in the same way they are for RRC_INACTIVE. However, in any of these solutions for the reporting, the UE relies on a measurement configuration, which may be provided with dedicated signaling when the UE is suspended to RRC_INACTIVE or when the UE is released to RRC_IDLE. That measurement configuration indicates how the UE shall perform these measurements to be reported when the UE resumes (in the case of coming from RRC_INACTIVE or sets up a connection in the case of coming from RRC_IDLE).

In RAN2#105bis in Xi'an, the following has been agreed concerning early measurement reporting for fast EN-DC and CA in NR (and LTE for EN-DC):

Agreements

1. For NR IDLE mode, the LTE rel-15 euCA early measurement

reporting solution (i.e. via UEInformationRequest and

UEInformationResponse like messages) after connection is setup will be supported.

2. For both LTE and NR, sending full idle mode measurements before security activation shall not be allowed.

FFS if some measurement information (detail TBD) related to idle mode measurements can be sent before security activation.

3. SMC and SMC complete messages will not be modified to enable the signaling of early measurements.

4. For both LTE and NR, RAN2 confirm that current specification allow that UEInformationRequest (or equivalent message to be specified in NR) can be sent by the network immediate after Security Mode Command without network having to wait for Security Mode Complete (i.e. similar to sending of Reconfiguration after SMC)

5. For NR INACTIVE mode, the LTE rel-15 euCA early measurement

reporting solution (i.e. via UEInformationRequest and

UEInformationResponse like messages) after connection is resumed will be supported.

6. Sending early measurement report is network controlled

7. For NR INACTIVE, the network can request early measurement

report in RRCResume

8. For NR INACTIVE, early measurement reporting can be sent in RRCResumeComplete

FFS Whether agreements 7 and 8 should be applied to LTE

RRCConnectionResume and RRCConnectionResumeComplete message. The following agreements are documented in Qualcomm Incorporated, "R2- 1903237, Summary of email discussion [105#54] [NR/eCA-DC]: measurement configuration," April 8-12, 2019.

Agreements

1. NR early measurements can be configured in both NR RRCRelease message and NR system information.

FFS: Whether there are differences in the configuration that can be provided by RRCRelease and SI.

2. Introduce some indication about the cell's early measurement support in NR system information.

3. To control the duration of UE performing both IDLE and INACTIVE measurements, a single validity timer (similar to measIdleDuration in LTE euCA) is mandatory indicated only in NR RRCRelease message, i.e. not included in NR SIB.

4. For both IDLE and INACTIVE early measurements, the following IEs can be optionally configured per NR frequency in both NR RRCRelease message and NR SIB:

- A list of frequencies and optionally cells (similar to measCellList in LTE euCA) the UE is required to perform early measurements.

- A cell quality threshold (similar to qualityThreshold in LTE euCA) the UE is required to report the measurement results only for the cells which met the configured thresholds.

FFS: A validity Area (similar to validityArea in LTE euCA) to indicate the list of cells within which UE is required to perform early measurements. If the UE reselects to a cell outside this list, the early measurements are no longer required (same as timer expiry). o If it is absent, the UE will not have area limitation of early measurements.

For SSB based measurements:

5. For both IDLE and INACTIVE early measurements, SSB frequencies to be measured can be located out of sync raster

6. For both IDLE and INACTIVE early measurements, RSRP and RSRQ can be configured as cell and beam measurement quantity.

7. For both IDLE and INACTIVE early measurements, the configuration parameters provided per SSB frequency follow the same principles as those provided in SIB2/4 for the purposes of Idle/Inactive mobility. (Details differences can be discussed at stage 3 level)

8. As LTE euCA, cell / beam SINR is not introduced as measurement quantity in NR early measurement configuration in Rel-16.

For SSB based beam level measurement configurations:

9. The UE is required to report the beam with the highest measurement quantity

FFS: Whether additional beams can be reported.

10. For both IDLE and INACTIVE early measurements, the UE can be configured with one of the 3 beam reporting types 1) No beam reporting;

2) Only beam identifier

3) Both beam identifier and quantity

FFS: Whether to support CSI-RS based NR early measurements

ll. LTE UE in IDLE mode, IDLE with suspended, and INACTIVE can be configured with NR early measurements to support fast setup of (NG)EN-DC (i.e. euCA is extended to support NR measurements). Details are FFS

Figures 4-7 are signaling diagrams illustrating the agreements above.

Summary

Systems and methods related to providing early measurements or an indication of early measurements from a first network node to a second network node in a cellular communications system are disclosed herein. In one embodiment, a method performed by a first network node comprises receiving, from a wireless device, a request to resume, setup, establish, or re-establish a connection between the wireless device and the first network node and determining that the wireless device has measurements available for reporting, wherein the measurements are measurements performed by the wireless device while the wireless device was in a dormant state. The method further comprises transmitting a message to a second network node, the message comprising at least some of the measurements performed by the wireless device while the wireless device was in the dormant state or an indication that the measurements performed by the wireless device while the wireless device was in the dormant state are available. In this manner, the second network node is enabled to consider the early measurements, e.g., for Secondary Cell Group (SCG) addition.

In one embodiment, the method further comprises transmitting, to the wireless device, a request for available measurements performed by the wireless device while the wireless device was in the dormant state and receiving, from the wireless device, a first message that comprises available measurements performed by the wireless device while the wireless device was in the dormant state. Further, transmitting the message to the second network node comprises sending a second message to the second network node, the second message comprising at least some of the available

measurements comprised in the first message. In one embodiment, the second message comprises all of the available measurements that are comprised in the first message received from the wireless device. In another embodiment, the second message comprises only those of the available measurements comprised in the first message received from the wireless device that are associated to frequencies that are candidates for SCG second cell addition.

In one embodiment, the second message further comprises time information related to the at least some of the available measurements performed while the wireless device was in the dormant state. In one embodiment, the time information comprises an indication of an amount of time that elapsed since expiry of a timer that marks an end a period of time during which the wireless device performed the measurements while the wireless device was in the dormant state. In one embodiment, the time information comprises an indication of whether a timer associated with performing the measurements while the wireless device was in the dormant state had expired when the first message was transmitted to the first network node.

In one embodiment, the second message comprises an idle measurement configuration with which the wireless device was configured when performing the measurements.

In one embodiment, the message transmitted to the second node comprises the indication that the measurements performed by the wireless device while the wireless device was in the dormant state are available.

In one embodiment, the first network node is a Master Node (MN) for Dual Connectivity (DC), the second network node is a Secondary Node (SN) for DC, and the method further comprises receiving an acknowledgement from the SN that confirms setup of a SCG and/or SN terminated bearers and configuring the wireless device with the SCG and/or SN terminated bearers.

In one embodiment, the message transmitted to the second network node comprises a request for addition of a SCG or addition of a SN terminated bearer.

In one embodiment, the first network node is a MN for DC, and the second network node is a SN for DC.

In one embodiment, the message transmitted to the second network node is an inter-node message for handover preparation.

In one embodiment, the dormant state is either a Radio Resource Control (RRC) idle state or an RRC inactive state.

Corresponding embodiments of a first network node are also disclosed. In one embodiment, a first network node comprises processing circuitry configured to cause the first network node to receive, from a wireless device, a request to resume, setup, establish, or re-establish a connection between the wireless device and the first network node and determine that the wireless device has measurements available for reporting, the measurements being measurements performed by the wireless device while the wireless device was in a dormant state. The processing circuitry is further configured to cause the first network node to transmit a message to a second network node, the message comprising at least some of the measurements performed by the wireless device while the wireless device was in the dormant state or an indication that the measurements performed by the wireless device while the wireless device was in the dormant state are available.

Embodiments of a method performed by a second network node are also disclosed. In one embodiment, a method performed by a second network node comprises receiving, from a first network node, a first message comprising

measurements performed by a wireless device while the wireless device was in a dormant state or an indication that measurements performed by the wireless device while the wireless device was in the dormant state are available.

In one embodiment, the first message comprises the measurements performed by the wireless device while the wireless device was in the dormant state, and the method further comprises determining whether to add, remove, or modify a SCG related Secondary Cell(s) (SCell(s)) or a SN terminated bearer(s) based on the measurements and transmitting a second message to the first network node that confirms setup of the SCG or SN terminated bearer(s). In one embodiment, the first message comprises a request for setup of a SCG or a SN terminated bearer. In one embodiment, the first message further comprises time information related to the measurements performed while the wireless device was in the dormant state, and determining whether to add, remove, or modify a SCG related SCell(s) or a SN terminated bearer(s) comprises determining whether to add, remove, or modify a SCG related SCell(s) or a SN terminated bearer(s) based on the measurements and the time information.

In one embodiment, the first message further comprises an indication that the measurements are measurements performed by the wireless device while the wireless device was in the dormant state.

In one embodiment, the dormant state is either an RRC idle state or an RRC inactive state. Corresponding embodiments of a second node are also disclosed. In one embodiment, a second network node comprising processing circuitry configured to cause the second network node to receive, from a first network node, a first message comprising measurements performed by a wireless device while the wireless device was in the dormant state or an indication that measurements performed by the wireless device while the wireless device was in the dormant state are available.

Embodiments of a method performed by a wireless device are also disclosed. In one embodiment, a method performed by a wireless device comprises receiving, from a first network node, a request to report measurements performed by the wireless device while in a dormant state and transmitting, to the first node, a first message including at least some of the measurements performed by the wireless device while in the dormant state. The method further comprises keeping at least some of the measurements performed by the wireless device, receiving, from a second network node, a request to report at least some of the measurements performed by the wireless device while in the dormant state, and transmitting, to the second network node, a second message that comprises at least some of the measurements performed by the wireless device while in the dormant state.

In one embodiment, the method further comprises receiving an indication that at least a subset of the measurements performed by the wireless device should not be reported to the first network node. In one embodiment, the at least some of the measurements transmitted in the first message comprise measurements other than the at least a subset of the measurements that the indication indicates should not be reported to the first network node. In one embodiment, the at least a subset of the measurements comprise measurements performed by the wireless device while in the dormant state that pertain to the second network node.

In one embodiment, the at least some of the measurements comprised in the second message comprise measurements performed by the wireless device while in the dormant state that pertain to the second network node.

In one embodiment, the method further comprises receiving an indication that at least a subset of the measurements should not be deleted, and keeping at least some of the measurements performed by the wireless device comprises keeping the at least a subset of the measurements that the indication indicates should not be deleted. In one embodiment, the method further comprises starting a timer upon transmission of the first message to the first network node. Further, transmitting the second message comprises transmitting the second message comprising the at least some of the measurements performed by the wireless device while in the dormant state responsive to the timer not expiring before receiving the request from the second network node.

In one embodiment, the first network node is a MN for DC, and the second network node is a SN for DC.

In one embodiment, the dormant state is either an RRC idle state or an RRC inactive state.

Corresponding embodiments of a wireless device are also disclosed. In one embodiment, a wireless device comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and the one or more receivers. The processing circuitry is configured to cause the wireless device to receive, from a first network node, a request to report measurements performed by the wireless device while in a dormant state and transmit, to the first node, a first message including at least some of the measurements performed by the wireless device while in the dormant state. The processing circuitry is further configured to cause the wireless device to keep at least some of the measurements performed by the wireless device, receive, from a second network node, a request to report at least some of the measurements performed by the wireless device while in the dormant state, and transmit, to the second network node, a second message that comprises at least some of the measurements performed by the wireless device while in the dormant state.

Brief Description of the Drawings

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

Figure 1 illustrates the Secondary Node (SN) Addition procedure for Evolved Universal Terrestrial Radio Access (E-UTRA) - New Radio (NR) Dual Connectivity (DC) (EN-DC); Figure 2 illustrates the SN Addition procedure for Fifth Generation (5G) Multi- Radio Access Technology (RAT) DC (MR-DC);

Figure 3 illustrates the User Equipment (UE) Information Request / Information Response procedure;

Figures 4 through 7 are signaling diagrams that illustrate several Third

Generation Partnership Project (3GPP) agreements related to early measurement reporting and DC;

Figure 8 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented;

Figure 9 is a flow chart that illustrates a procedure performed by a first network node (e.g., a Master Node (MN)) in accordance with embodiments of the present disclosure;

Figure 10 is a flow chart that illustrates a procedure performed by a second network node (e.g., a SN) in accordance with embodiments of the present disclosure;

Figure 11 is a flow chart that illustrates a procedure performed by a second network node (e.g., a SN) in accordance with some other embodiments of the present disclosure;

Figure 12 is a flow chart that illustrates a procedure performed by a wireless device in accordance with embodiments of the present disclosure;

Figures 13 to 15 are schematic block diagrams of a radio access node (e.g., a MN or a SN) in accordance with embodiments of the present disclosure; and

Figures 16 and 17 are schematic block diagrams of a UE in accordance with embodiments of the present disclosure.

Detailed Description

The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Radio Node: As used herein, a "radio node" is either a radio access node or a wireless device.

Radio Access Node: As used herein, a "radio access node" or "radio network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth

Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing a Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

Wireless Device: As used herein, a "wireless device" is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device.

Network Node: As used herein, a "network node" is any node that is either part of the RAN or the core network of a cellular communications network/ system.

Dormant State Measurements: The terms "early measurements", "dormant state measurements", and the like are used herein to refer to measurements performed by a wireless device (e.g., a UE) while the wireless device is in a dormant state (also referred to herein as a "dormant mode") (e.g., idle or inactive).

Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. Flowever, the concepts disclosed herein are not limited to a 3GPP system.

Note that, in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

There currently exist certain challenge(s) with respect to early measurement reporting. In particular, certain challenges exist when a UE in connected state is configured by a first network node (e.g., a Master Node (MN)) to perform

measurements and after the UE transmits a measurement report to the MN, the network decides to configure a Secondary Node (SN) connection (e.g., perform a Secondary Cell Group (SCG) addition procedure) for the UE. As described in the

Background, the message from the MN to the SN requesting the addition of an SN contains measurement information (i.e., serving cell and neighbor cell measurements in different frequencies) that enables the SN to properly configure SCG Secondary Cell(s) (SCell(s)), the UE's measurement configuration, etc. However, with the introduction of idle measurements for early reporting, there will be no measurement information from a connected state measurements report for these UEs, as the decision to add an SCG will be taken based on early measurements.

The problem addressed by the solutions described herein was not foreseen in the existing enhancing utilization of Carrier Aggregation (euCA) Release 15 solution for early measurements since that solution aimed to address the case where early measurements would be used to setup/add Carrier Aggregation (CA) (i.e., SCell(s)), which are cells associated to the same node to which the UE is resuming (i.e., with no inter-node coordination). On the other hand, the existing work item should also address Dual Connectivity (DC) related cases, such as Evolved Universal Terrestrial Radio Access (E- UTRA) - NR DC (EN-DC), where inter-node coordination is required.

Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Embodiments of the present disclosure provide a method executed at a first network node (e.g., a MN) for addition of a SN/cell such as an SCG addition. The method comprises the following actions:

- The first network node receives a request to resume, setup, establish, or re ^¬ establish a connection from the UE;

- The first network node determines that the UE has available idle measurements for early measurement reporting;

- The first network node requests the UE to report available idle measurements;

- The first network node transmits a message to a second network node (e.g., SN) requesting the addition of an SCG and/or SN terminated bearers, the message including idle measurements obtained via early reporting and related information (e.g., an indication that these are idle measurements instead of measurements obtained via connected mode measurement reports, time related information indicating how up to date (i.e., timely) the measurements are, etc.);

- The first network node receives an acknowledgement message from a second network node (e.g., SN) confirming the setup of an SCG and/or SN terminated bearers, the message including a Radio Resource Control (RRC) Reconfiguration like message that may include SCell(s) configurations associated to that SCG and/or an Information Element (IE) including radio bearer configurations. These configurations may indicate, to the UE, at least one SCell(s) associated to the SCG to add, to remove, or to modify, and/or higher layer configurations of SN terminated radio bearers, where the decisions at the SN were based on the reported early measurements; and

- The first network node configures the UE with the received SCG configuration and/or SN terminated bearers.

Note that, as described below with respect to Figure 9, not all of the aforementioned actions are required.

Embodiments of the present disclosure also provide a method executed by a second network node (e.g., SN) for SCG addition. The method comprises the following actions:

- The second network node receives a message from a first network node (e.g., MN) a message requesting the setup of an SCG and/or SN terminated bearers, the message including idle measurements obtained via early reporting and associated information;

- The second network node processes the received message and based on early measurements and associated information, determines whether the SN should add, remove, and/or modify SCG related SCell(s) and/or add, remove, or modify SN terminated bearers. For example, SCell(s) in a given frequency fx would be added only if the SCell on that frequency has measurements above a certain threshold and if the measurements are still valid, e.g. if time related information shows they are not very outdated. If a frequency has measurements below a certain threshold, the SN may omit configuring the SCG, but could configure SN terminated bearers as the measurements indicate the UE is in close vicinity of NR coverage. Early configuration of SN terminated bearers will improve the user plane performance if the UE later moves into good NR coverage, as there is then no need to move the bearer termination point.

- The second network node transmits an acknowledge message to a first network node (e.g., MN) confirming the setup of an SCG and/or SN terminated bearers, the message including an RRCReconfiguration like message that may include SCell(s) configurations associated to that SCG and/or IE including radio bearer configurations. These configurations may indicate to the UE SCell(s) associated to the SCG to add, to remove, or to modify and/or higher layer configurations of SN terminated radio bearers, where the decisions at the SN are based on the reported early measurements. Embodiments of the present disclosure also include a method for SCG addition executed by a wireless terminal (also called a UE). The method comprises the following actions:

- The wireless terminal receives a request to report early measurements from a first node (performed while the UE was in a dormant/power saving state (e.g., Idle, Inactive));

- The wireless terminal transmits a message including early measurements to a first node and keeps the idle measurements stored;

- The wireless terminal receives a request to report early measurements from a second node (performed while the UE was in a power saving state (e.g., Idle, Inactive));

- The wireless terminal transmits a message including early measurements to a second node; and

- The wireless terminal deletes early measurements upon the expiration of a

timer or upon the reporting to the second node.

The UE-based solution above could be seen as an alternative, where an SN has the possibility to request early measurements stored at the UE so that it avoids any changes in the coordination procedure for SN addition.

Certain embodiments may provide one or more of the following technical advantage(s). For example, in the case of the network-based solution (early

measurement information from the MN to the SN upon SCG addition in transition to connected state), the network node responsible to accept an SCG addition may be able to distinguish an SCG addition based on up to date measurements from an SCG addition based on early measurements. That is particularly important in the case of SCG associated SCell(s), wherein the SN has the responsibility for adding, removing, and modification.

Based on the early measurements, the network node may also determine that the UE is close to NR coverage, even though the reported quality is not sufficient for configuring the SCG. In this case the network may decide not to configure the SCG, but to instead to configure SN terminated bearers, such that if the UE later moves into good NR coverage, relocation of the Packet Data Convergence Protocol (PDCP) entities can be avoided. For the UE-based solution, one advantage is to make early measurement results available at the SN without the need to change existing inter-node messages. The change instead is at the UE, which could store early measurements a bit longer and possibly be requested to report these stored early measurements to the SN.

Figure 8 illustrates one example of a cellular communications system 800 in which embodiments of the present disclosure may be implemented. In the

embodiments described herein, the cellular communications system 800 is a 5G NR network, an E-UTRA network or, a network providing interworking between 5G and E- UTRA, as described above. In this example, the RAN includes base stations 802-1 and 802-2, which may be E-UTRA base stations, called eNBs, and/or NR base stations, called gNBs, for controlling corresponding (macro) cells 804-1 and 804-2. The base stations 802-1 and 802-2 are generally referred to herein collectively as base stations 802 and individually as base station 802. Likewise, the (macro) cells 804-1 and 804-2 are generally referred to herein collectively as (macro) cells 804 and individually as (macro) cell 804. The RAN may also include a number of low power nodes 806-1 through 806-4 controlling corresponding small cells 808-1 through 808-4. The low power nodes 806-1 through 806-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 808-1 through 808-4 may alternatively be provided by the base stations 802. The low power nodes 806-1 through 806-4 are generally referred to herein collectively as low power nodes 806 and individually as low power node 806. Likewise, the small cells 808-1 through 808-4 are generally referred to herein collectively as small cells 808 and individually as small cell 808. The cellular communications system 800 also includes a core network 810, which in the 5G System (5GS) is referred to as the 5G Core (5GC). The base stations 802 (and optionally the low power nodes 806) are connected to the core network 810.

The base stations 802 and the low power nodes 806 provide service to wireless devices 812-1 through 812-5 in the corresponding cells 804 and 808. The wireless devices 812-1 through 812-5 are generally referred to herein collectively as wireless devices 812 and individually as wireless device 812. The wireless devices 812 are also sometimes referred to herein as UEs.

A discussion of some example embodiments of the present disclosure is now provided. The embodiments described herein comprise a method executed by a first network node, and a method executed by a second network node. The first network node may be from a first Radio Access Technology (RAT), while the second node may be from a second RAT. The first RAT may be the same as the second RAT or a different RAT. For example, in case the UE is camping in LTE and triggers a resume/setup procedure, the network may decide to add EN-DC. In that case, the LTE MN may send the message to an NR SN, where the first RAT would be LTE and the second RAT would be NR. In another example, in case the UE is camping in LTE and triggers a

resume/setup procedure, the network may decide to add an LTE SCG. In that case, the LTE MN may send the message to an LTE SN, where the first RAT would be LTE and the second RAT would be LTE. In another example, in case the UE is camping in NR and triggers a resume/setup procedure, the network may decide to add an NR SCG. In that case, the NR MN may send the message to an NR SN, where the first RAT would be NR and the second RAT would be NR. For example, in case the UE is camping in NR and triggers a resume/setup procedure, the network may decide to add Multi-RAT DC (MR- DC). In that case, the NR MN may send the message to an LTE SN, where the first RAT would be NR and the second RAT would be LTE.

Even though the main use case described herein is SCG addition, the methods may also be useful for handovers after state transition and reporting of early

measurements. The main difference compared to the SCG addition case is that, instead of enhancing the SCG addition message, the handover preparation information message would be enhanced.

The methods may also be useful for resume attempts without context relocation. In other words, the UE tries to resume in a first network node and reports early idle measurements to the first network node. Then, these measurements are forwarded to the source node where the UE Access Stratum (AS) context is stored. That source node may decide to take further actions based on these early measurements such as handover the UE, redirect the UE to another frequency, re-configure early

measurements, etc. Hence, for that purpose, the target node forwards the early measurements to the source node so that further decisions are taken.

In the present disclosure, embodiments of a method executed by a first network node (e.g., MN) for addition of a SN/cell (such as an SCG or SN terminated bearer addition) are provided. As illustrated in Figure 9, in some embodiments, the method comprises the following steps. Note that while these actions are referred to as "steps", these actions may be performed in any suitable order and are not limited to the order in which they are presented here, unless otherwise stated or required. Optional steps are represented with dashed lines. In the example embodiment Figure 9, the first network node is a MN.

Step 900: The MN receives from a UE a request to resume, setup, establish, or re-establish a connection.

Step 902: The MN determines that the UE has idle measurements available for early measurement reporting.

Step 904 (Optional): The MN requests the UE to report available idle measurements.

Step 906 (Optional): The MN receives at least some of the available idle measurements from the UE, in response to the request.

Step 908A: In a first alternative embodiment, the MN transmits a message to a second network node (e.g., a SN) requesting the addition of an SCG or SN terminated bearer, the message including idle measurements obtained via early reporting and related information (e.g., an indication that these are idle measurements, time related information indicating how up to date the measurements are, etc.).

Step 908B: In a second alternative embodiment, the MN transmits a message to a second network node (e.g., a SN) indicating the availability of idle measurements at the UE pertaining to the SCG and related information (e.g., an indication that these are idle measurements, time related information indicating how up to date the

measurements are, etc.). This message may be an inter-node message from the MN to a SN for SCG addition, such as an enhanced version of the SCG-Configlnfo defined in E- UTRA specifications. This message may be an inter-node message from the MN to a SN for SCG addition, such as an enhanced version of the CG-Configlnfo defined in NR specifications. This message may be an inter-node message for handover preparation from a first network node to a second network node. For example, the UE may try to resume in the first network node and report early measurements there. Upon receiving these early measurements, the first network node decides to trigger a handover for that UE towards a second network node and, during handover preparation, the first network node forwards to the second network node these early measurements, so the second network node is able to decide whether it should add/remove/modify SCell(s) associated to its Master Cell Group (MCG) after the handover. In that handover use cases, this message may be an enhanced version of the HandoverPreparationlnformation defined in NR specifications.

Step 910 (Optional): The MN receives an acknowledgement message from the second network node (e.g., SN) confirming the setup of an SCG and/or SN terminated bearers, the message including an RRC Reconfiguration like message that may include SCell(s) configurations associated to that SCG and/or an IE including radio bearer configurations. These configurations may indicate, to the UE, at least one SCell(s) associated to the SCG to add, to remove, or to modify, and/or higher layer configurations of SN terminated radio bearers, where the decisions at the SN were based on the reported early measurements;

Step 912 (Optional): The MN configures the UE with the received SCG configuration, and/or SN terminated bearers.

In the present disclosure, embodiments of a method executed by a second network node (e.g., SN) for SCG addition are also provided. As illustrated in Figure 10, in some embodiments, the method comprises the following steps. Note that while these actions are referred to as "steps", these actions may be performed in any suitable order and are not limited to the order in which they are presented here, unless otherwise stated or required. In this example, the second network node is a SN.

Step 1000: The SN receives a message from a first network node (e.g., MN) a message requesting the setup of an SCG and/or SN terminated bearers, the message including idle measurements obtained via early reporting and associated information.

Step 1002: The SN processes the received message and, based on early measurements and associated information, determines whether the SN should add, remove, and/or modify SCG related SCell(s) and/or add, remove, or modify SN terminated bearers. For example, SCell(s) in a given frequency fx would be added only if the SCell on that frequency has measurements above a certain threshold and if the measurements are still valid, e.g. if time related information show they are not very outdated. If a frequency has measurements below a certain threshold, the SN may omit configuring the SCG, but could configure SN terminated bearers as the

measurements indicate the UE is in close vicinity of NR coverage. Early configuration of SN terminated bearers will improve the user plane performance if the UE later moves into good NR coverage, as there is then no need to move the bearer termination point. Step 1004: The SN transmits an acknowledge message to the first network node (e.g., MN) confirming the setup of an SCG and/or SN terminated bearers, the message including an RRCReconfiguration like message that may include SCell(s) configurations associated to that SCG and/or an IE including radio bearer

configurations. These configurations may indicate to the UE SCell(s) associated to the SCG to add, to remove, or to modify and/or higher layer configurations of SN

terminated radio bearers, where the decisions at the SN were based on the reported early measurements.

In the present disclosure, embodiments of an alternative method executed by a second network node/cell for an SCG or SN terminated bearer addition/modification, for example, are provided. As illustrated in Figure 11, in some embodiments, the method comprises the following steps. Note that while these actions are referred to as "steps", these actions may be performed in any suitable order and are not limited to the order in which they are presented here, unless otherwise stated or required. In this example, the second network node is a SN.

Step 1100: The SN receives a message from a first network node indicating that the UE has idle measurements available for early measurement reporting.

Step 1102: The SN requests the UE to report the available idle measurements (e.g., via Signaling Radio Bearer 3 (SRB3) or encapsulated in SRB1).

Step 1104: The SN receives from the UE a message including the available idle measurements.

Step 1106: The SN transmits a message to a primary network node (e.g., MN) requesting the modification or the change of an SCG, the message including idle measurements obtained via early reporting and related information (e.g., an indication that these are idle measurements, time related information indicating how up to date the measurements are, etc.).

Regarding the content of the early measurement information, various solutions are possible depending on what measurement information related to idle measurements is included in an early report.

In one embodiment, the first network node includes all reported early

measurements available. In the case of the content agreed in LTE Release 15, currently in Technical Specification (TS) 36.331, the content to be included includes serving cell measurement information, e.g. Reference Signal Received Power (RSRP) / Reference Signal Received Quality (RSRQ) for the serving cell and neighbor cell information that could be provided per carrier the UE has reported measurements, e.g. E-UTRA carriers (in the case of Release 15 content). This is shown below:

Further information may be included in early measurements for NR and LTE in Release 16, and this further information can possibly be included in the inter-node message content proposed in the methods described herein, such as:

- Beam measurement information such as:

o RSRP per Synchronization Signal Block (SSB), RSRQ per SSB, Signal to

Interference plus Noise Ratio (SINR) per SSB;

o RSRP per Channel State Information Reference Signal (CSI-RS), RSRQ per CSI-RS, SINR per CSI-RS; and

o Indexes derived based on beam measurements; and

- SINR per cell and/or beams (SSB, CSI-RS). In another embodiment, the first network node includes only the reported early measurements available associated to frequencies that are candidates for SCG SCell(s) addition.

In another embodiment, the first network node includes an indication that a SCG addition is being requested based on early measurements.

In another embodiment, the first network node includes time information related to early measurements as an indication of how up to date early measurements reported are. For example, the first network node may indicate:

- time elapsed since the expiry of timer T331 (timer the UE is required to

perform measurements). As known to those of skill in the art, the timer T331 defines the amount of time that the UE is required to perform early measurements. After the timer T331 has expired, whether the UE continues to perform early measurements or not is left for UE implementation. Thus, the timer T331 defines a period of time during which the UE is known to perform the early measurements; and/or

- indication if the timer T331 had expired when measurements were reported.

In another embodiment, the first network node includes the idle measurement configuration in the message. That would enable the second network node to understand how the measurements being reported were derived, e.g. threshold, which carriers were configured, etc.

In regard to the message from the first network node to the second network node where early measurement information is included, this message may be an inter ^¬ node message from a MN to a SN for SCG addition, such as an enhanced version of the SCG-Configlnfo defined in E-UTRA specifications. This message may be an inter-node message from a MN to a SN for SCG addition, such as an enhanced version of the CG- Configlnfo defined in NR specifications.

In the handover use case, the second network node may be considered as a new target MN. In that case, the purpose of the early measurements is to enable the new target MN to decide whether to add/remove/modify SCell(s) associated to its cell group. In that case, this message may be an inter-node message from a MN to a new MN (SN) for handover preparation, such as an enhanced version of the

HandoverPreparationlnformation defined in NR specifications. In one possible implementation, no changes are introduced to the structure of the inter-node message but instead the MN is allowed to include early measurements reported by the UE upon transition to connected in the existing inter-node message to the SN, as if these would be measurements reported by the UE and performed when the UE was in connected state, as in the state of the art. The SN then uses these early measurements as if these would be the same connected measurements. In one variant, the message includes a simple flag indicating that reported measurements (in the field of connected measurements) are actually early measurements.

In regard to the message from the second network node to the first network node where early measurement information is included, this message may be a

Secondary gNB (SgNB) modification required. The early measurement information may be included in an RRC inter-node message, e.g. CG-Config.

This message may be an SN change required. The early measurements information may be included in an RRC inter-node message, e.g. CG-Config.

In the present disclosure, embodiments of a method executed by a UE as an alternative or complement to the methods of a network node disclosed above for SCG addition are also provided. As illustrated in Figure 12, in some embodiments, the method comprises the following steps. Note that while these actions are referred to as "steps", these actions may be performed in any suitable order and are not limited to the order in which they are presented here, unless otherwise stated or required. Optional steps are represented with dashed lines.

Step 1200: The UE receives, from a first node, a request to report early measurements (e.g., performed while the UE was in a dormant or power saving state (e.g. Idle, Inactive)). In one embodiment, the UE receives an indication that (a subset of) the idle mode measurements should not be reported to the first node (e.g., the measurements pertaining to the SN). In another embodiment, the UE receives an indication that (a subset of) the idle mode measurements should not be deleted after reported to the first node, under the assumption that later the SN could request the report of these measurements.

Step 1202: The UE transmits a message including early measurements to a first node and keeps the idle measurements stored. In one embodiment, a timer is introduced (e.g., a timer called T332). The timer is started upon the transmission of the early measurements to a first node. Upon the expiry of that timer, the UE deletes the early measurements. While the timer is running, the UE keeps the early measurements stored as they may be requested again (e.g., by a second node).

Step 1204 (Optional): The UE receives from a second node a request to report early measurements (e.g., performed while the UE was in a power saving state (e.g., Idle, Inactive)). The request to the UE may be a UEInformationRequest (e.g., sent on SRB3), including an indication that the UE shall report early measurements.

Step 1206 (Optional): The UE transmits a message including early

measurements to a second node. The message/report may be a

UEInformation Response (e.g., sent on SRB3) including early measurements to the second node.

Step 1208 (Optional): The UE deletes early measurements upon the expiry of a timer or upon the reporting to the second node.

If the request from the second node is received by the UE (see step 1204) while the timer described above (e.g., timer T332) is running, the UE includes early

measurements in the message/report transmitted in step 1206. Otherwise, if the request (step 1204) occurs after the timer described above (e.g., new timer T332) has expired, the UE message/report in step 1206 is empty because the early measurements were deleted when the timer expired in step 1208.

One example implementation of some aspects of the solutions described herein is as follows. To signal the early measurements via an Inter-Node Message (INM), e.g., the MeasResult2NR could be extended as follows:

where it is assumed that the MeasResultListldle contains both the LTE and NR measurements.

In another embodiment, separate fields are introduced for the NR and LTE measurements:

In another embodiment, the CG-Configlnfo is extended to directly include the idle mode measurements (example here is show with a single IE for both LTE and NR):

In another embodiment, the field description of the candidateCelllnfoMN is updated to enable transmission of early measurements:

Figure 13 is a schematic block diagram of a radio access node 1300 according to some embodiments of the present disclosure. The radio access node 1300 may be, for example, a base station 802 or 806. As illustrated, the radio access node 1300 includes a control system 1302 that includes one or more processors 1304 (e.g., Central

Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field

Programmable Gate Arrays (FPGAs), and/or the like), memory 1306, and a network interface 1308. The one or more processors 1304 are also referred to herein as processing circuitry. In addition, the radio access node 1300 includes one or more radio units 1310 that each includes one or more transmitters 1312 and one or more receivers 1314 coupled to one or more antennas 1316. The radio units 1310 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 1310 is external to the control system 1302 and connected to the control system 1302 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 1310 and potentially the antenna(s) 1316 are integrated together with the control system 1302. The one or more processors 1304 operate to provide one or more functions of a radio access node 1300 as described herein (e.g., one or more functions of a first network node (e.g., a MN) as described herein or one or more functions of a second network node (e.g., a SN) as described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 1306 and executed by the one or more processors 1304.

Figure 14 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 1300 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes.

Further, other types of network nodes may have similar virtualized architectures.

As used herein, a "virtualized" radio access node is an implementation of the radio access node 1300 in which at least a portion of the functionality of the radio access node 1300 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 1300 includes the control system 1302 that includes the one or more processors 1304 (e.g., CPUs, ASICs, FPGAs, and/or the like), the memory 1306, and the network interface 1308 and the one or more radio units 1310 that each includes the one or more transmitters 1312 and the one or more receivers 1314 coupled to the one or more antennas 1316, as described above. The control system 1302 is connected to the radio unit(s) 1310 via, for example, an optical cable or the like. The control system 1302 is connected to one or more processing nodes 1400 coupled to or included as part of a network(s) 1402 via the network interface 1308. Each processing node 1400 includes one or more processors 1404 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1406, and a network interface 1408.

In this example, functions 1410 of the radio access node 1300 described herein (e.g., one or more functions of a first network node (e.g., a MN) as described herein or one or more functions of a second network node (e.g., a SN) as described herein) are implemented at the one or more processing nodes 1400 or distributed across the control system 1302 and the one or more processing nodes 1400 in any desired manner. In some particular embodiments, some or all of the functions 1410 of the radio access node 1300 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1400. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1400 and the control system 1302 is used in order to carry out at least some of the desired functions 1410. Notably, in some embodiments, the control system 1302 may not be included, in which case the radio unit(s) 1310 communicate directly with the processing node(s) 1400 via an appropriate network interface(s).

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 1300 or a node (e.g., a processing node 1400) implementing one or more of the functions 1410 of the radio access node 1300 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

Figure 15 is a schematic block diagram of the radio access node 1300 according to some other embodiments of the present disclosure. The radio access node 1300 includes one or more modules 1500, each of which is implemented in software. The module(s) 1500 provide the functionality of the radio access node 1300 described herein (e.g., one or more functions of a first network node (e.g., a MN) as described herein or one or more functions of a second network node (e.g., a SN) as described herein). This discussion is equally applicable to the processing node 1400 of Figure 14 where the modules 1500 may be implemented at one of the processing nodes 1400 or distributed across multiple processing nodes 1400 and/or distributed across the processing node(s) 1400 and the control system 1302.

Figure 16 is a schematic block diagram of a UE 1600 according to some embodiments of the present disclosure. As illustrated, the UE 1600 includes one or more processors 1602 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1604, and one or more transceivers 1606 each including one or more transmitters 1608 and one or more receivers 1610 coupled to one or more antennas 1612. The transceiver(s) 1606 includes radio-front end circuitry connected to the antenna(s) 1612 that is configured to condition signals communicated between the antenna(s) 1612 and the processor(s) 1602, as will be appreciated by on of ordinary skill in the art. The processors 1602 are also referred to herein as processing circuitry. The transceivers 1606 are also referred to herein as radio circuitry. In some embodiments, the functionality of a UE described above may be fully or partially implemented in software that is, e.g., stored in the memory 1604 and executed by the processor(s) 1602. Note that the UE 1600 may include additional components not illustrated in Figure 16 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other

components for allowing input of information into the UE 1600 and/or allowing output of information from the UE 1600), a power supply (e.g., a battery and associated power circuitry), etc.

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the UE 1600 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

Figure 17 is a schematic block diagram of the UE 1600 according to some other embodiments of the present disclosure. The UE 1600 includes one or more modules 1700, each of which is implemented in software. The module(s) 1700 provide the functionality of the UE 1600 described herein.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

Some example embodiments of the present disclosure are as follows.

Group A Embodiments

Embodiment 1: A method performed by a wireless device, the method comprising: receiving (1200), from a first node, a request to report measurements performed by the wireless device while in a dormant state; and transmitting (1202), to the first node, a first message including at least some of the measurements performed by the wireless device while in the dormant state.

Embodiment 2: The method of embodiment 1, wherein: receiving an indication that at least a subset of the measurements should not be reported to the first node (e.g., the indication may be comprised in the request of step 1200); the at least some of the measurements transmitted in the first message comprises measurements other than the at least a subset of the measurements that the indication indicates should not be reported.

Embodiment 3: The method of embodiment 2 wherein the at least a subset of the measurements comprise measurements performed by the wireless device while in the dormant state that pertain to a second node (e.g., a secondary node).

Embodiment 4: The method of embodiments 2 or 3 further comprising keeping the at least a subset of the measurements not reported to the first node (e.g., the measurements performed by the wireless device while in the dormant state that pertain to the second node) at the wireless device. Embodiment 5: The method of embodiment 1, wherein the at least a subset of the measurements comprise measurements performed by the wireless device while in the dormant state that pertain to a second node (e.g., a secondary node).

Embodiment 5A: The method of any one of embodiments 1 to 5 further comprising receiving an indication that at least a subset of the measurements should not be deleted (e.g., not deleted after reporting the measurements to the first node) (e.g., the indication may be comprised in the request of step 1200).

Embodiment 6: The method of any one of embodiments 1 to 5A, further comprising: starting a timer upon transmission of the measurements to the first node; and deleting the measurements upon indication by the timer of expiration of a predetermined time.

Embodiment 7: The method of any one of embodiments 1 to 6, further comprising: receiving (1204), from a second node, a request to report the

measurements; transmitting (1206) a second message to the second node.

Embodiment 8: The method of embodiment 7, wherein the second message comprising at least some of the measurements performed by the wireless device while in the dormant state.

Embodiment 9: The method of embodiment 7 or 8 further comprising deleting (1208) the measurements.

Embodiment 10: The method of embodiment 7 or 8, wherein: transmitting (1206) the second message further comprises including the at least some of the measurements in the second message in response to receiving the request from the second node before expiration of a predetermined amount time.

Embodiment 11 : The method of embodiment 7, wherein: transmitting (1206) the second message comprises transmitting (1206) an empty message in response to receiving the request from the second node after expiration of a predetermined amount of time.

Embodiment 12: The method of any one of embodiments 7 to 9, wherein:the request (1204) (e.g., UEInformationRequest) from the second node comprises an indication that the wireless device shall report at least some of the measurements. Group B Embodiments

Embodiment 13: A method performed by a base station, the method comprising: receiving (900), from a user equipment, UE, a request to resume, setup, establish, or re-establish a connection between the UE and the base station; determining (902) that the UE has measurements, performed while the UE was in a dormant state, available for reporting; transmitting a message to a secondary node, SN, the message comprising at least some of the measurements (908A) obtained from the UE or an indication that the measurements are available (908B).

Embodiment 14: The method of embodiment 13 further comprising receiving (910) an acknowledgement from the SN confirming setup of a SCG and/or SN

terminated bearers; and configuring (912) the UE with the SCG and/or SN terminated bearers.

Embodiment 15: The method of embodiment 13 or 14, wherein: transmitting (908) the message to the SN further comprises transmitting (908) a message requesting addition of a secondary cell group, (SCG,) or SN terminated bearer.

Embodiment 16: The method of embodiment 13, 14, or 15, wherein the message further comprises related information, the related information comprising either or both of: an indication that the measurements were performed by the UE while the UE was in a dormant state; or information indicating a timeliness of the

measurements.

Embodiment 17: The method of embodiment 16 wherein the message further comprises related information pertaining to the SCG or SN terminated bearer.

Embodiment 18: The method of any one of embodiments 13 to 17, wherein:the message comprises an inter-node message from the base station, operating as a master node (MN), to the SN for SCG addition (e.g., an enhanced version of a SCG-Configlnfo defined in EUTRA).

Embodiment 19: The method of any one of embodiments 13 to 17, wherein the message comprises an inter-node message from the base station, operating as a master node (MN), to the SN for SCG addition (e.g., an enhanced version of CG-Configlnfo defined in 5G-NR).

Embodiment 20: The method of any one of embodiments 13 to 17, wherein the message comprises an inter-node message for handover preparation (e.g., an enhanced version of the HandoverPreparationlnformation defined in 5G-NR). Embodiment 21 : A method performed by a base station, the method comprising: receiving (1000), from a first network node, a first message including measurements performed by a UE while the UE was in a dormant state or an indication that the measurements are available; determining (1002) whether to add, remove, or modify a SCG related secondary cell (SCell) or a SN terminated bearer; and transmitting (1004) a second message to the first network node confirming setup of an SCG or SN terminated bearer.

Embodiment 22: The method of embodiment 21, wherein the first message comprises a request for setup of a secondary cell group (SCG) or a secondary node (SN) terminated bearer.

Embodiment 23: The method of embodiment 21, wherein the first message further comprises related information related to the measurements and obtained from the UE via early reporting.

Embodiment 24: The method of embodiment 21, wherein the determining (1002) is based on the measurements obtained from the UE.

Embodiment 25: The method of embodiment 21, further comprising adding an SCell in a frequency if the measurements indicate the SCell on that frequency has measurements above a threshold and the related information indicates the

measurements are still valid.

Embodiment 26: The method of embodiment 21, wherein the first message comprises an RRCReconfiguration-like message that may include an SCell configuration associated with the SCG including radio bearer configurations.

Embodiment 27: A method performed by a base station for adding a secondary node (SN), the method comprising: receiving (1100) a first message from a first network node, the first message indicating that a user equipment (UE) has

measurements, performed while in a dormant state, available for reporting; requesting (1102) the UE to report the available measurements; receiving (1104), from the UE, A second message comprising the measurements; and transmitting (1106) a third message to a primary network requesting modification or change of a secondary cell group (SCG).

Embodiment 28: The method of embodiment 24, wherein the second message comprises: an indication that the measurements were performed while the UE was in a dormant state; and time related information indicating the timeliness of the measurements.

Group C Embodiments

Embodiment 29: A wireless device, the wireless device comprising processing circuitry configured to perform any of the steps of any of the Group A embodiments and power supply circuitry configured to supply power to the wireless device.

Embodiment 30: A base station, the base station comprising processing circuitry configured to perform any of the steps of any of the Group B embodiments and power supply circuitry configured to supply power to the base station.

Embodiment 31 : A User Equipment, UE, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals

communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A

embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

• 3GPP Third Generation Partnership Project

• 5G Fifth Generation

• 5GC Fifth Generation Core

• 5GS Fifth Generation System

• AMF Access and Mobility Function

• AS Access Stratum

• ASIC Application Specific Integrated Circuit

• AUSF Authentication Server Function • CA Carrier Aggregation

• CPU Central Processing Unit

• CSI-RS Channel State Information Reference Signal

• DC Dual Connectivity

• DSP Digital Signal Processor

• eNB Enhanced or Evolved Node B

• EN-DC Evolved Universal Terrestrial Radio Access New Radio Dual

Connectivity

• euCA Enhancing Utilization of Carrier Aggregation

• E-UTRA Evolved Universal Terrestrial Radio Access

• FPGA Field Programmable Gate Array

. gNB New Radio Base Station

• HSS Home Subscriber Server

• ID Identity

• IE Information Element

• INM Inter-Node Message

• Intra-E-UTRA Intra-Evolved Universal Terrestrial Radio Access

• LTE Long Term Evolution

• MCG Master Cell Group

• MN Master Node

• MME Mobility Management Entity

• MR-DC Multi-Radio Access Technology Dual Connectivity

• MTC Machine Type Communication

• NEF Network Exposure Function

• NF Network Function

• NR New Radio

• NRF Network Function Repository Function

• NSSF Network Slice Selection Function

• PCF Policy Control Function

• PCI Physical Cell Identity

• PDCP Packet Data Convergence Protocol

• P-GW Packet Data Network Gateway

• RAM Random Access Memory RAN Radio Access Network

RAN4 Radio Access Network Working Group 4

RAT Radio Access Technology

ROM Read Only Memory

RRC Radio Resource Control

RRH Remote Radio Head

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

Rx Receive

SCEF Service Capability Exposure Function

SCell Secondary Cell

SCG Secondary Cell Group

SgNB Secondary New Radio Base Station

SIB System Information Block

SINR Signal to Interference Plus Noise Ratio

SMF Session Management Function

SN Secondary Node

SRB Signaling Radio Bearer

SSB Synchronization Signal Block

TS Technical Specification

Tx Transmit

UDM Unified Data Management

UE User Equipment

UPF User Plane Function

WID Work Item Description

Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.