8.2.4 Carrier Aggregation
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
8.2.4.1 NR CA / NR SCell addition / modification / release / Success
8.2.4.1.1 NR CA / NR SCell addition / modification / release / Success / EN-DC
8.2.4.1.1.1 NR CA / NR SCell addition / modification / release / Success / EN-DC / Intra-band Contiguous CA
8.2.4.1.1.1.1 Test Purpose (TP)
(1)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with initial AS security activated }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message containing sCellToAddModList with an sCellIndex set to the configured Scell }
then { UE adds the new SCell, configures lower layers to consider the SCell to be in deactivated state and sends an RRCConnectionReconfigurationComplete message }
}
(2)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message containing sCellToAddModList with an sCellIndex matching one of the current UE SCell configuration }
then { UE modifies the affected SCell dedicated configurations and sends an RRCConnectionReconfigurationComplete message }
}
(3)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message containing sCellToReleaseList with an sCellIndex matching one of the current UE SCell configuration }
then { UE releases the SCell and sends an RRCConnectionReconfigurationComplete message }
}
8.2.4.1.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331: 5.3.5.3; TS 38.331: 5.3.5.3, 5.3.5.5.8, 5.3.5.5.9. Unless otherwise stated these are Rel-15 requirements.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:
2> re-establish PDCP for SRB2 configured with E-UTRA PDCP entity and for all DRBs that are established and configured with E-UTRA PDCP, if any;
2> re-establish RLC for SRB2 and for all DRBs that are established and configured with E-UTRA RLC, if any;
2> if the RRCConnectionReconfiguration message includes the fullConfig:
3> perform the radio configuration procedure as specified in 5.3.5.8;
2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
NOTE 1: Void
NOTE 2: Void
1> else:
2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
NOTE 3: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an outstanding acknowledgment of the SecurityModeComplete message.
1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:
2> perform SCell release as specified in 5.3.10.3a;
1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:
2> perform SCell addition or modification as specified in 5.3.10.3b;
1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or
1> if the current UE configuration includes one or more split DRBs configured with pdcp-Config and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:
2> perform SCG reconfiguration as specified in 5.3.10.10;
1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or
1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:
2> perform EN-DC release as specified in TS 38.331 [82], clause 5.3.5.10;
1> if the received RRCConnectionReconfiguration includes the sk-Counter:
2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;
1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:
2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:
2> resume SRB2 and all DRBs that are suspended, if any, including RBs configured with NR PDCP;
NOTE 4: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].
NOTE 5: The UE may discard SRB2 messages and data that it receives prior to completing the reconfiguration used to resume these bearers.
1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:
2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;
1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:
2> forward each element of the dedicatedInfoNASList to upper layers in the same order as listed;
1> if the RRCConnectionReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;
1> if the RRCConnectionReconfiguration message includes the otherConfig:
2> perform the other configuration procedure as specified in 5.3.10.9;
1> upon RRC connection establishment, if UE does not need UL gaps during continuous uplink transmission:
2> configure lower layers to stop using UL gaps during continuous uplink transmission in FDD for RRCConnectionReconfigurationComplete message and subsequent uplink transmission in RRC_CONNECTED except for UL transmissions as specified in TS36.211 [21];
1> set the content of RRCConnectionReconfigurationComplete message as follows:
2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:
3> include perCC-GapIndicationList and numFreqEffective;
2> if the frequencies are configured for reduced measurement performance:
3> include numFreqEffectiveReduced;
2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:
3> include scg-ConfigResponseNR in accordance with TS 38.331 [82, 5.3.5.3];
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
1> if the RRCReconfiguration includes the fullConfig:
2> perform the radio configuration procedure as specified in 5.3.5.11;
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> if the RRCReconfiguration includes the masterKeyUpdate:
2> perform security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the secondaryCellGroup:
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration message contains the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList:
2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed;
1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery:
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery:
2> perform the action upon reception of System Information as specified in 5.2.2.4;
1> set the content of RRCReconfigurationComplete message as follows:
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent, or;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent:
3> include the uplinkTxDirectCurrentList;
1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCReconfiguration was received via SRB1:
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG:
4> initiate the random access procedure on the SpCell, as specified in TS 38.321 [3];
3> else:
4> the procedure ends;
NOTE: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2> else (RRCReconfiguration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE: For EN-DC, in the case RRCReconfiguration is received via SRB1, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.
1 > else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure:
3> resume SRB2 and DRBs that are suspended;
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a random access procedure triggered above;
2> stop timer T304 for that cell group;
2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if T390 is running:
4> stop timer T390 for all access categories;
4> perform the actions as specified in 5.3.14.4.
3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1:
4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2;
2> the procedure ends.
NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
Editor’s Note: FFS Check automatic measurement handling for SCells.
2> for each measId included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
1> modify the SCell configuration in accordance with the sCellConfigDedicated.
8.2.4.1.1.1.3 Test description
8.2.4.1.1.1.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 is the PCell. NR Cell 1 is the PSCell and NR Cell 3 is the SCell.
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC), Bearers (MCG(s) and SCG) established according to TS 38.508-1 [4], clause 4.5.4.
– Else, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC), Bearers (MCG(s) and SCG) established and Test Loop Function (On) with UE test loop mode B according to TS 38.508-1 [4], clause 4.5.4.
8.2.4.1.1.1.3.2 Test procedure sequence
Table 8.2.4.1.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
||
|
U – S |
Message |
|||||
|
1 |
The SS transmits a RRCConnectionReconfiguration message including NR RRCReconfiguration message to configure the NR SCell. |
<– |
RRCConnectionReconfiguration (RRCReconfiguration) |
– |
– |
|
|
2 |
Check: Does the UE transmit a RRCConnectionReconfigurationComplete message containing RRCReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
1 |
P |
|
|
2A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 3? |
– |
– |
– |
– |
|
|
3 |
The SS transmits a RRCConnectionReconfiguration message including NR RRCReconfiguration message to modify the startingBitOfFormat2-3 of the NR SCell. |
<– |
RRCConnectionReconfiguration (RRCReconfiguration) |
– |
– |
|
|
4 |
Check: Does the UE transmit a RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
2 |
P |
|
|
4A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 3? |
– |
– |
– |
– |
|
|
5 |
The SS transmits a RRCConnectionReconfiguration message including NR RRCReconfiguration message to release the NR SCell. |
<– |
RRCConnectionReconfiguration (RRCReconfiguration) |
– |
– |
|
|
6 |
Check: Does the UE release SCell and sends a RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
3 |
P |
|
8.2.4.1.1.1.3.3 Specific message contents
Table 8.2.4.1.1.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.1.1.1.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_NR_CA |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup. |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-2: RRCReconfiguration (Table 8.2.4.1.1.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-3: CellGroupConfig (Table 8.2.4.1.1.1.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 With condition SCell_Add |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CellGroupConfig ::= SEQUENCE { |
||||
|
sCellToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SCellConfig { |
1 entry |
|||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
|||
|
sCellIndex |
1 |
|||
|
sCellConfigCommon |
ServingCellConfigCommon |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.4.1.1.1.3.3-4: ServingCellConfigCommon (Table 8.2.4.1.1.1.3.3-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-168. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfigCommon ::= SEQUENCE { |
|||
|
PhysCellId |
Physical Cell Identity of NR Cell 3 |
||
|
} |
|||
Table 8.2.4.1.1.1.3.3-5: RRCConnectionReconfiguration (step 3, Table 8.2.4.1.1.1.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_NR_CA |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup. |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-6: RRCReconfiguration (Table 8.2.4.1.1.1.3.3-5)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-7: CellGroupConfig (Table 8.2.4.1.1.1.3.3-6)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition SCell_Add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToAddModList SEQUENCE (SIZE(1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellConfigDedicated |
ServingCellConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-8: ServingCellConfig (Table 8.2.4.1.1.1.3.3-7)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-167 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfig ::= SEQUENCE { |
|||
|
initialDownlinkBWP |
BWP-DownlinkDedicated |
||
|
firstActiveDownlinkBWP-Id |
Not present |
||
|
uplinkConfig SEQUENCE { |
|||
|
firstActiveUplinkBWP-Id |
Not present |
||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-9: BWP-DownlinkDedicated (Table 8.2.4.1.1.1.3.3-8)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-11 with condition Scell_Add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
BWP-DownlinkDedicated ::= SEQUENCE { |
|||
|
pdcch-Config CHOICE { |
|||
|
setup |
PDCCH-Config |
||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-10: PDCCH-Config (Table 8.2.4.1.1.1.3.3-9)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-100 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDCCH-Config ::= SEQUENCE { |
|||
|
tpc-SRS SetupRelease { |
|||
|
setup |
SRS-TPC-CommandConfig |
||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-11: SRS-TPC-CommandConfig (Table 8.2.4.1.1.1.3.3-10)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-183 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SRS-TPC-CommandConfig ::= SEQUENCE { |
|||
|
startingBitOfFormat2-3 |
1 |
||
|
fieldTypeFormat2-3 |
1 |
||
|
} |
|||
Table 8.2.4.1.1.1.3.3-12: RRCConnectionReconfiguration (step 5, Table 8.2.4.1.1.1.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_NR_CA |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup. |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-13: RRCReconfiguration (Table 8.2.4.1.1.1.3.3-12)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.1.3.3-14: CellGroupConfig (Table 8.2.4.1.1.1.3.3-13)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToReleaseList SEQUENCE (SIZE(1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
|
SCellIndex[1] |
2 |
entry 1 |
|
|
} |
|||
|
} |
|||
8.2.4.1.1.2 NR CA / NR SCell addition / modification / release / Success / EN-DC / Intra-band non-Contiguous CA
8.2.4.1.1.2.1 Test Purpose (TP)
Same as TC 8.2.4.1.1.1 but applied to Intra-band non-Contiguous CA.
8.2.4.1.1.2.2 Conformance requirements
Same as TC 8.2.4.1.1.1 but applied to Intra-band non-Contiguous CA.
8.2.4.1.1.2.3 Test description
8.2.4.1.1.2.3.1 Pre-test conditions
Same as TC 8.2.4.1.1.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.2.4.1.1.2.3.2 Test procedure sequence
Same as TC 8.2.4.1.1.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.2.4.1.1.3 NR CA / NR SCell addition / modification / release / Success / EN-DC / Inter-band CA
8.2.4.1.1.3.1 Test Purpose (TP)
Same as TC 8.2.4.1.1.1 but applied to Inter-band CA
8.2.4.1.1.3.2 Conformance requirements
Same as TC 8.2.4.1.1.1 but applied to Inter-band CA
8.2.4.1.1.3.3 Test description
8.2.4.1.1.3.3.1 Pre-test conditions
Same as TC 8.2.4.1.1.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 replaces NR Cell 3
8.2.4.1.1.3.3.2 Test procedure sequence
Same as TC 8.2.4.1.1.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 replaces NR Cell 3
8.2.4.1.1.4 NR CA / NR SCell addition / modification / release / Success / EN-DC / Active SCG SCell addition / Intra-band Contiguous CA
8.2.4.1.1.4.1 Test Purpose (TP)
(1)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with initial AS security activated }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message containing sCellToAddModList for SCG SCell addition including IE sCellState }
then { UE adds the new NR SCell, configures lower layers to consider the SCell to be in activated state and sends an RRCConnectionReconfigurationComplete message }
}
(2)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message containing sCellToAddModList for SCG SCell modification including IE sCellState }
then { UE modifies the affected SCell dedicated configurations and sends an RRCConnectionReconfigurationComplete message and consider the SCell to be in activated state }
}
(3)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message containing sCellToReleaseList }
then { UE releases the SCell and sends an RRCConnectionReconfigurationComplete message }
}
8.2.4.1.1.4.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331: 5.3.5.3; TS 38.331: 5.3.5.3, 5.3.5.5.8, 5.3.5.5.9. Unless otherwise stated these are Rel-15 requirements.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:
2> re-establish PDCP for SRB2 configured with E-UTRA PDCP entity and for all DRBs that are established and configured with E-UTRA PDCP, if any;
2> re-establish RLC for SRB2 and for all DRBs that are established and configured with E-UTRA RLC, if any;
2> if the RRCConnectionReconfiguration message includes the fullConfig:
3> perform the radio configuration procedure as specified in 5.3.5.8;
2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
NOTE 1: Void
NOTE 2: Void
1> else:
2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
NOTE 3: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an outstanding acknowledgment of the SecurityModeComplete message.
1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:
2> perform SCell release as specified in 5.3.10.3a;
1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:
2> perform SCell addition or modification as specified in 5.3.10.3b;
1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or
1> if the current UE configuration includes one or more split DRBs configured with pdcp-Config and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:
2> perform SCG reconfiguration as specified in 5.3.10.10;
1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or
1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:
2> perform EN-DC release as specified in TS 38.331 [82], clause 5.3.5.10;
1> if the received RRCConnectionReconfiguration includes the sk-Counter:
2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;
1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:
2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:
2> resume SRB2 and all DRBs that are suspended, if any, including RBs configured with NR PDCP;
NOTE 4: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].
NOTE 5: The UE may discard SRB2 messages and data that it receives prior to completing the reconfiguration used to resume these bearers.
1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:
2> perform the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;
1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:
2> forward each element of the dedicatedInfoNASList to upper layers in the same order as listed;
1> if the RRCConnectionReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;
1> if the RRCConnectionReconfiguration message includes the otherConfig:
2> perform the other configuration procedure as specified in 5.3.10.9;
1> upon RRC connection establishment, if UE does not need UL gaps during continuous uplink transmission:
2> configure lower layers to stop using UL gaps during continuous uplink transmission in FDD for RRCConnectionReconfigurationComplete message and subsequent uplink transmission in RRC_CONNECTED except for UL transmissions as specified in TS36.211 [21];
1> set the content of RRCConnectionReconfigurationComplete message as follows:
2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:
3> include perCC-GapIndicationList and numFreqEffective;
2> if the frequencies are configured for reduced measurement performance:
3> include numFreqEffectiveReduced;
2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:
3> include scg-ConfigResponseNR in accordance with TS 38.331 [82, 5.3.5.3];
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
1> if the RRCReconfiguration includes the fullConfig:
2> perform the radio configuration procedure as specified in 5.3.5.11;
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> if the RRCReconfiguration includes the masterKeyUpdate:
2> perform security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the secondaryCellGroup:
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration message contains the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList:
2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed;
1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery:
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery:
2> perform the action upon reception of System Information as specified in 5.2.2.4;
1> set the content of RRCReconfigurationComplete message as follows:
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent, or;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent:
3> include the uplinkTxDirectCurrentList;
1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCReconfiguration was received via SRB1:
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG:
4> initiate the random access procedure on the SpCell, as specified in TS 38.321 [3];
3> else:
4> the procedure ends;
NOTE: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2> else (RRCReconfiguration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE: For EN-DC, in the case RRCReconfiguration is received via SRB1, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.
1 > else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure:
3> resume SRB2 and DRBs that are suspended;
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a random access procedure triggered above;
2> stop timer T304 for that cell group;
2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if T390 is running:
4> stop timer T390 for all access categories;
4> perform the actions as specified in 5.3.14.4.
3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1:
4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2;
2> the procedure ends.
NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
…
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated.
2> if the sCellToAddModList was received in an RRCReconfiguration message including reconfigurationWithSync, or received in an RRCResume message, or received in an RRCReconfiguration message including reconfigurationWithSync embedded in an RRCResume message or embedded in an RRCReconfiguration message or embedded in an E-UTRA RRCConnectionReconfiguration message or embedded in an E-UTRA RRCConnectionResume message:
3> if the sCellState is included:
4> configure lower layers to consider the SCell to be in activated state;
3> else:
4> configure lower layers to consider the SCell to be in deactivated state.
8.2.4.1.1.4.3 Test description
8.2.4.1.1.4.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 is the PCell. NR Cell 1 is the PSCell and NR Cell 3 is the SCell.
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC), Bearers (MCG(s) and SCG) established according to TS 38.508-1 [4], clause 4.5.4.
– Else, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC), Bearers (MCG(s) and SCG) established and Test Loop Function (On) with UE test loop mode B according to TS 38.508-1 [4], clause 4.5.4.
8.2.4.1.1.4.3.2 Test procedure sequence
Table 8.2.4.1.1.4.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
||
|
U – S |
Message |
|||||
|
1 |
The SS transmits a RRCConnectionReconfiguration message including NR RRCReconfiguration message to configure the NR SCell. |
<– |
RRCConnectionReconfiguration (RRCReconfiguration) |
– |
– |
|
|
2 |
Check: Does the UE transmit a RRCConnectionReconfigurationComplete message containing RRCReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
1 |
P |
|
|
2A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 3? |
– |
– |
– |
– |
|
|
3 |
The SS transmits a RRCConnectionReconfiguration message including NR RRCReconfiguration message to modify the startingBitOfFormat2-3 of the NR SCell. |
<– |
RRCConnectionReconfiguration (RRCReconfiguration) |
– |
– |
|
|
4 |
Check: Does the UE transmit a RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
2 |
P |
|
|
4A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 3? |
– |
– |
– |
– |
|
|
5 |
The SS transmits a RRCConnectionReconfiguration message including NR RRCReconfiguration message to release the NR SCell. |
<– |
RRCConnectionReconfiguration (RRCReconfiguration) |
– |
– |
|
|
6 |
Check: Does the UE release SCell and sends a RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
3 |
P |
|
8.2.4.1.1.4.3.3 Specific message contents
Table 8.2.4.1.1.4.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.1.1.4.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_NR_CA |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup. |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-2: RRCReconfiguration (Table 8.2.4.1.1.4.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-3: CellGroupConfig (Table 8.2.4.1.1.4.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 With condition SCell_Add |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CellGroupConfig ::= SEQUENCE { |
||||
|
sCellToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SCellConfig { |
1 entry |
|||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
|||
|
sCellIndex |
1 |
|||
|
sCellConfigCommon |
ServingCellConfigCommon |
|||
|
sCellState-r16 |
activated |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.4.1.1.4.3.3-4: ServingCellConfigCommon (Table 8.2.4.1.1.4.3.3-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-168. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfigCommon ::= SEQUENCE { |
|||
|
PhysCellId |
Physical Cell Identity of NR Cell 3 |
||
|
} |
|||
Table 8.2.4.1.1.4.3.3-5: RRCConnectionReconfiguration (step 3, Table 8.2.4.1.1.4.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_NR_CA |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup. |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-6: RRCReconfiguration (Table 8.2.4.1.1.4.3.3-5)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-7: CellGroupConfig (Table 8.2.4.1.1.4.3.3-6)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition SCell_Add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToAddModList SEQUENCE (SIZE(1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellConfigDedicated |
ServingCellConfig |
||
|
sCellState-r16 |
activated |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-8: ServingCellConfig (Table 8.2.4.1.1.4.3.3-7)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-167 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfig ::= SEQUENCE { |
|||
|
initialDownlinkBWP |
BWP-DownlinkDedicated |
||
|
firstActiveDownlinkBWP-Id |
Not present |
||
|
uplinkConfig SEQUENCE { |
|||
|
firstActiveUplinkBWP-Id |
Not present |
||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-9: BWP-DownlinkDedicated (Table 8.2.4.1.1.4.3.3-8)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-11 with condition Scell_Add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
BWP-DownlinkDedicated ::= SEQUENCE { |
|||
|
pdcch-Config CHOICE { |
|||
|
setup |
PDCCH-Config |
||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-10: PDCCH-Config (Table 8.2.4.1.1.4.3.3-9)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-100 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDCCH-Config ::= SEQUENCE { |
|||
|
tpc-SRS SetupRelease { |
|||
|
setup |
SRS-TPC-CommandConfig |
||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-11: SRS-TPC-CommandConfig (Table 8.2.4.1.1.4.3.3-10)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-183 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SRS-TPC-CommandConfig ::= SEQUENCE { |
|||
|
startingBitOfFormat2-3 |
1 |
||
|
fieldTypeFormat2-3 |
1 |
||
|
} |
|||
Table 8.2.4.1.1.4.3.3-12: RRCConnectionReconfiguration (step 5, Table 8.2.4.1.1.4.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_NR_CA |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup. |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-13: RRCReconfiguration (Table 8.2.4.1.1.4.3.3-12)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.1.1.4.3.3-14: CellGroupConfig (Table 8.2.4.1.1.4.3.3-13)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToReleaseList SEQUENCE (SIZE(1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
|
SCellIndex[1] |
2 |
entry 1 |
|
|
} |
|||
|
} |
|||
8.2.4.1.1.5 NR CA / NR SCell addition / modification / release / Success / EN-DC / Active SCG SCell addition / Intra-band non-Contiguous CA
8.2.4.1.1.5.1 Test Purpose (TP)
Same as TC 8.2.4.1.1.4 but applied to Intra-band non-Contiguous CA.
8.2.4.1.1.5.2 Conformance requirements
Same as TC 8.2.4.1.1.4 but applied to Intra-band non-Contiguous CA.
8.2.4.1.1.5.3 Test description
8.2.4.1.1.5.3.1 Pre-test conditions
Same as TC 8.2.4.1.1.4 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.2.4.1.1.5.3.2 Test procedure sequence
Same as TC 8.2.4.1.1.4 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.2.4.1.1.6 NR CA / NR SCell addition / modification / release / Success / EN-DC / Active SCG SCell addition / Inter-band CA
8.2.4.1.1.6.1 Test Purpose (TP)
Same as TC 8.2.4.1.1.4 but applied to Inter-band CA
8.2.4.1.1.6.2 Conformance requirements
Same as TC 8.2.4.1.1.4 but applied to Inter-band CA
8.2.4.1.1.6.3 Test description
8.2.4.1.1.6.3.1 Pre-test conditions
Same as TC 8.2.4.1.1.4 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 replaces NR Cell 3
8.2.4.1.1.6.3.2 Test procedure sequence
Same as TC 8.2.4.1.1.4 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 replaces NR Cell 3
8.2.4.1.2 NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition
8.2.4.1.2.1 NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition / Intra-band Contiguous CA
8.2.4.1.2.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message containing sCellToAddModList for SCG SCell addition including IE sCellState }
then { UE adds the new SCG SCell and sends an RRCReconfigurationComplete message and consider the SCell to be in activated state }
}
(2)
with { UE in NR RRC_CONNECTED state with SCell configured}
ensure that {
when { UE receives an RRCReconfiguration message containing sCellToAddModList for SCG SCell modification including IE sCellState }
then { UE modifies the SCG SCell configuration and sends an RRCReconfigurationComplete message and consider the SCell to be in activated state }
}
(3)
with { UE in NR RRC_CONNECTED state with SCG SCell configured}
ensure that {
when { UE receives an RRCReconfiguration message containing SCG sCellToReleaseList }
then { UE sends an RRCReconfigurationComplete message }
}
8.2.4.1.2.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.3, 5.3.5.5.1 and 5.3.5.5.9.
[TS 38.331 clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
…
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
…
1> else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
[TS 38.331 clause 5.3.5.5.1]
The UE performs the following actions based on a received CellGroupConfig IE:
…
1> if the CellGroupConfig contains the sCellToReleaseList:
2> perform SCell release as specified in 5.3.5.5.8;
…
1> if the CellGroupConfig contains the sCellToAddModList:
2> perform SCell addition/modification as specified in 5.3.5.5.9.
[TS 38.331 clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
…
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated.
2> if the sCellToAddModList was received in an RRCReconfiguration message including reconfigurationWithSync, or received in an RRCResume message, or received in an RRCReconfiguration message including reconfigurationWithSync embedded in an RRCResume message or embedded in an RRCReconfiguration message or embedded in an E-UTRA RRCConnectionReconfiguration message or embedded in an E-UTRA RRCConnectionResume message:
3> if the sCellState is included:
4> configure lower layers to consider the SCell to be in activated state;
3> else:
4> configure lower layers to consider the SCell to be in deactivated state.
8.2.4.1.2.1.3 Test description
8.2.4.1.2.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell, NR Cell 10 is the PSCell, NR Cell 28 is the SCG SCell.
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.
None.
Preamble:
– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC) and NR-DC bearers (MCG(s) and SCG) and with UE test loop mode B active if pc_IP_Ping is set to FALSE according to TS 38.508-1 [4], Table 4.5.1-1.
8.2.4.1.2.1.3.2 Test procedure sequence
Table 8.2.4.1.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCReconfigurationmessage containing an sCellToAddModList with SCell NR Cell 3 addition, |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
2 |
Check: Does the UE transmits an RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationtComplete |
1 |
P |
|
3 |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB1 and Cell 3? |
– |
– |
1 |
P |
|
4 |
The SS transmits an RRCReconfigurationmessage containing an sCellToAddModList with SCell NR Cell 3 modification. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
5 |
Check: Does the UE transmit an RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationtComplete |
2 |
P |
|
6 |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB1 and Cell 3? |
– |
– |
2 |
P |
|
7 |
The SS transmits an RRCReconfigurationmessage containing an sCellToReleaseList with SCell NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
8 |
Check: Does the UE transmit an RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationtComplete |
3 |
P |
8.1.2.5.1.1.3.3 Specific message contents
Table 8.1.2.5.1.1.3.3-1: RRCReconfiguration (step 1, Table 8.2.4.1.2.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.2.5.1.1.3.3-2: CellGroupConfig (Table 8.1.2.5.1.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 with condition SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellState-r16 |
activated |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.2.5.1.1.3.3-3: RRCReconfiguration (step 4, Table 8.2.4.1.2.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.2.5.1.1.3.3-4: CellGroupConfig (Table 8.1.2.5.1.1.3.3-3)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 with condition SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellConfigCommon |
Not present |
||
|
sCellConfigDedicated |
ServingCellConfig |
||
|
sCellState-r16 |
activated |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.2.5.1.1.3.3-5: ServingCellConfig (Table 8.1.2.5.1.1.3.3-4)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.3-167 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfig ::= SEQUENCE { |
|||
|
firstActiveDownlinkBWP-Id |
Not present |
||
|
uplinkConfig SEQUENCE { |
|||
|
firstActiveUplinkBWP-Id |
Not present |
||
|
} |
|||
|
pdsch-ServingCellConfig CHOICE { |
|||
|
setup |
PDSCH-ServingCellConfig |
||
|
} |
|||
|
} |
|||
Table 8.1.2.5.1.1.3.3-6: PDSCH-ServingCellConfig (Table 8.1.2.5.1.1.3.3-5)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.3-102 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDSCH-ServingCellConfig ::= SEQUENCE { |
|||
|
nrofHARQ-ProcessesForPDSCH |
n16 |
||
|
} |
|||
Table 8.1.2.5.1.1.3.3-7: RRCReconfiguration (step 7, Table 8.2.4.1.2.1.3.2-6)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.2.5.1.1.3.3-8: CellGroupConfig (Table 8.1.2.5.1.1.3.3-7)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 with condition SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToAddModList |
Not present |
||
|
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
|
SCellIndex[1] |
1 |
entry 1 |
|
|
} |
|||
|
} |
|||
8.2.4.1.2.2 NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition / Inter-band CA
8.2.4.1.2.2.1 Test Purpose (TP)
Same as TC 8.2.4.1.2.1 but applied to Inter-band CA.
8.2.4.1.2.2.2 Conformance requirements
Same as TC 8.2.4.1.2.1 but applied to Inter-band CA.
8.2.4.1.2.2.3 Test description
8.2.4.1.2.2.3.1 Pre-test conditions
Same as TC 8.2.4.1.2.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 and NR Cell 28 are in the different band.
8.2.4.1.2.2.3.2 Test procedure sequence
Same as TC 8.2.4.1.2.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 replaces NR Cell 3
8.2.4.1.2.3 NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition / Intra-band non-contiguous CA
8.2.4.1.2.3.1 Test Purpose (TP)
Same as TC 8.2.4.1.2.1 but applied to Intra-band non-contiguous CA.
8.2.4.1.2.3.2 Conformance requirements
Same as TC 8.2.4.1.2.1 but applied to Intra-band non-contiguous CA.
8.2.4.1.2.3.3 Test description
8.2.4.1.2.3.3.1 Pre-test conditions
Same as TC 8.2.4.1.2.1 with the following differences:
– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA
8.2.4.1.2.3.3.2 Test procedure sequence
Same as TC 8.2.4.1.2.1 with the following differences:
– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 and NR Cell 28 are in the different band
8.2.4.2 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release
8.2.4.2.1 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release/ EN-DC
8.2.4.2.1.1 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release / EN-DC / Intra-band Contiguous CA
8.2.4.2.1.1.1 Test Purpose (TP)
(1)
with { UE in RRC_CONNECTED state with E-UTRA }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message to configure NR PSCell and sCellToAddModList with an sCellIndex set to the configured SCell }
then { UE sends an RRCConnectionReconfigurationComplete message indicating the addition of PSCell and configures lower layers to consider the SCell to be in deactivated state }
}
(2)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message to perform both PSCell and SCell change to the configured target PSCell and SCell }
then { UE sends an RRCConnectionReconfigurationComplete message and configures new PSCell and configures lower layers to consider the SCell to be in deactivated state }
}
(3)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured }
ensure that {
when { UE receives an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message to perform PSCell change to one of the SCell equalling to one of the current UE SCell configuration }
then { UE sends an RRCConnectionReconfigurationComplete message and reconfigures the current NR Scell to PSCell }
}
8.2.4.2.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331: 5.3.5.3; TS 38.331: 5.3.5.3, 5.3.5.5.7, 5.3.5.5.8, 5.3.5.5.9, 5.3.5.6.4 and 5.3.5.6.5. Unless otherwise stated these are Rel-15 requirements.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:
2> re-establish PDCP for SRB2 configured with E-UTRA PDCP entity and for all DRBs that are established and configured with E-UTRA PDCP, if any;
2> re-establish RLC for SRB2 and for all DRBs that are established and configured with E-UTRA RLC, if any;
2> if the RRCConnectionReconfiguration message includes the fullConfig:
3> perform the radio configuration procedure as specified in 5.3.5.8;
2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
NOTE 1: Void
NOTE 2: Void
1> else:
2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
NOTE 3: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an outstanding acknowledgment of the SecurityModeComplete message.
1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:
2> perform SCell release as specified in 5.3.10.3a;
1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:
2> perform SCell addition or modification as specified in 5.3.10.3b;
1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or
1> if the current UE configuration includes one or more split DRBs configured with pdcp-Config and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:
2> perform SCG reconfiguration as specified in 5.3.10.10;
1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or
1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:
2> perform EN-DC release as specified in TS 38.331 [82], clause 5.3.5.10;
1> if the received RRCConnectionReconfiguration includes the sk-Counter:
2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;
1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:
2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:
2> resume SRB2 and all DRBs that are suspended, if any, including RBs configured with NR PDCP;
NOTE 4: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].
NOTE 5: The UE may discard SRB2 messages and data that it receives prior to completing the reconfiguration used to resume these bearers.
1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:
2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;
1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:
2> forward each element of the dedicatedInfoNASList to upper layers in the same order as listed;
1> if the RRCConnectionReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;
1> if the RRCConnectionReconfiguration message includes the otherConfig:
2> perform the other configuration procedure as specified in 5.3.10.9;
1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig or sl-CommConfig:
2> perform the sidelink dedicated configuration procedure as specified in 5.3.10.15;
1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated:
2> perform the V2X sidelink communication dedicated configuration procedure as specified in 5.3.10.15a;
1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:
2> perform the dedicated WLAN offload configuration procedure as specified in 5.6.12.2;
1> if the RRCConnectionReconfiguration message includes rclwi-Configuration:
2> perform the WLAN traffic steering command procedure as specified in 5.6.16.2;
1> if the RRCConnectionReconfiguration message includes lwa-Configuration:
2> perform the LWA configuration procedure as specified in 5.6.14.2;
1> if the RRCConnectionReconfiguration message includes lwip-Configuration:
2> perform the LWIP reconfiguration procedure as specified in 5.6.17.2;
1> upon RRC connection establishment, if UE does not need UL gaps during continuous uplink transmission:
2> configure lower layers to stop using UL gaps during continuous uplink transmission in FDD for RRCConnectionReconfigurationComplete message and subsequent uplink transmission in RRC_CONNECTED except for UL transmissions as specified in TS36.211 [21];
1> set the content of RRCConnectionReconfigurationComplete message as follows:
2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:
3> include perCC-GapIndicationList and numFreqEffective;
2> if the frequencies are configured for reduced measurement performance:
3> include numFreqEffectiveReduced;
2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:
3> include scg-ConfigResponseNR in accordance with TS 38.331 [82, 5.3.5.3];
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
1> if the RRCReconfiguration includes the fullConfig:
2> perform the radio configuration procedure as specified in 5.3.5.11;
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> if the RRCReconfiguration includes the masterKeyUpdate:
2> perform security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the secondaryCellGroup:
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration message contains the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery:
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery:
2> perform the action upon reception of System Information as specified in 5.2.2.4;
1> set the content of RRCReconfigurationComplete message as follows:
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent, or;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent:
3> include the uplinkTxDirectCurrentList;
1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCReconfiguration was received via SRB1:
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG:
4> initiate the random access procedure on the SpCell, as specified in TS 38.321 [3];
3> else:
4> the procedure ends;
NOTE: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2> else (RRCReconfiguration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE: For EN-DC, in the case of SRB1, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case of SRB3, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.
1> else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a random access procedure triggered above;
2> stop timer T304 for that cell group;
2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured:
4> acquire the SIB1 of the target SpCell of the MCG, as specified in 5.2.2.3.1;
2> the procedure ends.
NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 5.3.5.5.7]
The UE shall:
1> if the SpCellConfig contains the rlf-TimersAndConstants:
2> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6.
1> else if rlf-TimersAndConstants is not configured for this cell group:
2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
1> if the SpCellConfig contains spCellConfigDedicated:
2> configure the SpCell in accordance with the spCellConfigDedicated;
2> consider the bandwidth part indicated in firstActiveUplinkBWP-Id if configured to be the active uplink bandwidth part;
2> consider the bandwidth part indicated in firstActiveDownlinkBWP-Id if configured to be the active downlink bandwidth part;
2> if the any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated:
3> stop timer T310 for the corresponding SpCell, if running;
3> reset the counters N310 and N311.
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
Editor’s Note: FFS Check automatic measurement handling for SCells.
2> for each measId included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated.
[TS 38.331, clause 5.3.5.6.4]
Editor’s Note: FFS / TODO: Add handling for the new QoS concept (mapping of flows; configuration of QFI-to-DRB mapping; reflective QoS…) but keep also EPS-Bearer handling for the EN-DC case
The UE shall:
1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration (DRB release):
2> release the PDCP entity;
2> if SDAP entity associated with this DRB is configured:
3> indicate the release of the DRB to SDAP entity associated with this DRB (TS 37.324 [xx] section 5.3.3);
2> if the UE is operating in EN-DC:
3> if a new bearer is not added either with NR or E-UTRA with same eps-BearerIdentity:
4> indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers.
NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration.
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig.
[TS 38.331, clause 5.3.5.6.5]
The UE shall:
1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used):
2> if an sdap-Config is included:
3> if an SDAP entity with the received pdu-Session does not exist:
4> establish an SDAP entity as specified in TS 37.324 [xx] section 5.1.1;
3> configure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324 [xx] and associate the DRB with the SDAP entity;
2> establish a PDCP entity and configure it in accordance with the received pdcp-Config;
2> if the PDCP entity of this DRB is not configured with cipheringDisabled:
3> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the KUPenc key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse;
2> if the PDCP entity of this DRB is configured with integrityProtection:
3> configure the PDCP entity with the integrity algorithms according to securityConfig and apply the KUPint key associated with the master (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse;
2> if the UE is operating in EN-DC:
3>if the DRB was configured with the same eps-BearerIdentity either by NR or E-UTRA prior to receiving this reconfiguration:
4> associate the established DRB with the corresponding eps-BearerIdentity;
3> else:
4> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;
1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration:
2> if an sdap-Config is included, reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324 [xx];
2> if the reestablishPDCP is set:
3> if target RAT is E-UTRA/5GC:
4> if the PDCP entity of this DRB is not configured with cipheringDisabled:
5> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331 [10, 5.4.2.3], i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
3> else:
4> if the PDCP entity of this DRB is not configured with cipheringDisabled:
5> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master or secondary key (KeNB/S-KgNB/KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
4> if the PDCP entity of this DRB is configured with integrityProtection:
5> configure the PDCP entity with the integrity algorithms according to securityConfig and apply the KUPint key associated with the master (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse;
3> re-establish the PDCP entity of this DRB as specified in 38.323 [5], section 5.1.2;
2> else, if the recoverPDCP is set:
3> trigger the PDCP entity of this DRB to perform data recovery as specified in 38.323;
2> if the pdcp-Config is included:
3> reconfigure the PDCP entity in accordance with the received pdcp-Config.
NOTE 1: Removal and addition of the same drb-Identity in a single radioResourceConfig is not supported. In case drb-Identity is removed and added due to reconfiguration with sync or re-establishment with the full configuration option, the network can use the same value of drb-Identity.
NOTE 2: When determining whether a drb-Identity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB-ToAddModList that DRB was originally configured in. To re-associate a DRB with a different key (KeNB to S-KeNB or vice versa), the network provides the drb-Identity value in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-Identity in the (source) drb-ToReleaseList.
NOTE 3: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity.
NOTE 4: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated.
NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB.
8.2.4.2.1.1.3 Test description
8.2.4.2.1.1.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 is the PCell, NR Cell 1 is the PSCell to be added, and NR Cell 3 is Scell to be added. NR Cell 2 and NR Cell 12 are the target PSCell and SCell.
– NR Cell 1 and NR Cell 3 are Intra-band Contiguous. NR Cell 2 and NR Cell 12 are Intra-band Contiguous.
UE:
None
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (E-UTRA/EPC) established according to TS 38.508-1 [4], clause 4.5.4.
– Else, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (E-UTRA/EPC) established and Test Mode (On) associated with UE test loop mode B configured on E-UTRA Cell 1 according to TS 38.508-1 [4], clause 4.5.4.
8.2.4.2.1.1.3.2 Test procedure sequence
Table 8.2.4.2.1.1.3.2-1 illustrates the downlink power levels to be applied for EUTRA Cell 1, NR Cell 1, NR Cell 3, NR Cell 2 and NR Cell 12 at various time instants of the test execution. Row marked “T0” denotes the conditions after the preamble, while rows marked “T1” are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.2.4.2.1.1.3.2-1: Power levels for conducted test environment
|
Parameter |
Unit |
E-UTRA Cell 1 |
NR Cell 1 |
NR Cell 3 |
NR Cell 2 |
NR Cell 12 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
– |
– |
– |
– |
EUTRA Cell 1, NR Cell 1 and NR Cell 3 are available. NR Cell 2 and NR Cell 12 are not available. |
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-88 |
-88 |
off |
off |
||
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
– |
– |
– |
– |
EUTRA Cell 1, NR Cell 1, NR Cell 3, NR Cell 2 and NR Cell 12 are available. |
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-88 |
-88 |
-88 |
-88 |
Table 8.2.4.2.1.1.3.2-1A: Power levels for OTA test environment
|
Parameter |
Unit |
E-UTRA Cell 1 |
NR Cell 1 |
NR Cell 3 |
NR Cell 2 |
NR Cell 12 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-96 |
– |
– |
– |
– |
EUTRA Cell 1, NR Cell 1 and NR Cell 3 are available. NR Cell 2 and NR Cell 12 are not available. |
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-91 |
-91 |
off |
off |
||
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-96 |
– |
– |
– |
– |
EUTRA Cell 1, NR Cell 1, NR Cell 3, NR Cell 2 and NR Cell 12 are available. |
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-91 |
-91 |
-91 |
-91 |
Table 8.2.4.2.1.1.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS changes Cell parameters according to the row “T0” in table 8.2.4.2.1.1.3.2-1. |
– |
– |
– |
– |
|
2 |
The SS transmits an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message to configure NR Cell 1 as the NR PSCell and sCellToAddModList with a sCellIndex set to NR Cell 3 as the configured Scell. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
3 |
Check: Does the UE transmit an RRCConnectionReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete |
1 |
P |
|
– |
EXCEPTION: Steps 3AAa1 to 3AAa2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation. |
– |
– |
– |
– |
|
3AAa1 |
IF pc_IP_Ping = FALSE, then, the SS transmits a CLOSE UE TEST LOOP message. |
<– |
CLOSE UE TEST LOOP |
– |
– |
|
3AAa2 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
3A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 3? |
– |
– |
– |
– |
|
4 |
The SS changes NR Cell 2 and NR Cell 12 parameters according to the row “T1” in table 8.2.4.2.1.1.3.2-1. |
– |
– |
– |
– |
|
5 |
The SS transmits an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message to perform both NR Cell 1 and NR Cell 3 changed to the configured target NR Cell 2 and NR Cell 12. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
6 |
Check: Does the UE transmit an RRCConnectionReconfigurationComplete message configuring the new PSCell and SCell and configure lower layers to consider the SCell to be in deactivated state? |
–> |
RRCConnectionReconfigurationComplete |
2 |
P |
|
– |
EXCEPTION: Steps 7Aa1 to 7Aa2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation. |
– |
– |
– |
– |
|
7Aa1 |
IF pc_IP_Ping = FALSE, then, the SS transmits a OPEN UE TEST LOOP message. |
<– |
OPEN UE TEST LOOP |
– |
– |
|
7Aa2 |
The UE transmits a OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
6A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 12? |
– |
– |
– |
– |
|
7 |
The SS transmits an RRCConnectionReconfiguration message with nr-Config IE including NR RRCReconfiguration message to change the current PSCell (NR Cell 2) to NR Cell 12 equaling to one of the current UE SCell configuration. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
8 |
Check: Does the UE send an RRCConnectionReconfigurationComplete message and reconfigure the current NR Scell to PSCell? |
–> |
RRCConnectionReconfigurationComplete |
3 |
P |
8.2.4.2.1.1.3.3 Specific message contents
Table 8.2.4.2.1.1.3.3-1: RRCConnectionReconfiguration (step 2, Table 8.2.4.2.1.1.3.2-2)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition MCG_and_SCG |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
RRCReconfiguration |
OCTET STRING including the RRCReconfiguration |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.2.1.1.3.3-2: RRCReconfiguration (Table 8.2.4.2.1.1.3.3-1: RRCConnectionReconfiguration)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with Condition EN-DC |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.2.1.1.3.3-3: CellGroupConfig (Table 8.2.4.2.1.1.3.3-2: RRCReconfiguration)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition EN-DC and SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
spCellConfig SEQUENCE { |
|||
|
servCellIndex |
1 |
||
|
reconfigurationWithSync SEQUENCE { |
|||
|
spCellConfigCommon SEQUENCE { |
|||
|
physCellId |
Physical Cell Identity of NR Cell 1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellIndex |
2 |
||
|
sCellConfigCommon SEQUENCE { |
|||
|
physCellId |
Physical Cell Identity of NR Cell 3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.2.1.1.3.3-4: RRCConnectionReconfigurationComplete (step 3, step 6 and step 8, Table 8.2.4.2.1.1.3.2-2)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-9 with condition MCG_and_SCG |
Table 8.2.4.2.1.1.3.3-5: RRCConnectionReconfiguration (step 5, Table 8.2.4.2.1.1.3.2-2)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_PSCell_HO AND RBConfig_NoKeyChange |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
RRCReconfiguration |
OCTET STRING including the RRCReconfiguration |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.2.1.1.3.3-6: RRCReconfiguration (Table 8.2.4.2.1.1.3.3-5: RRCConnectionReconfiguration)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with Condition EN-DC |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.2.1.1.3.3-7: CellGroupConfig (Table 8.2.4.2.1.1.3.3-6: RRCReconfiguration)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PSCell_change and SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
spCellConfig SEQUENCE { |
|||
|
servCellIndex |
1 |
||
|
reconfigurationWithSync SEQUENCE { |
|||
|
spCellConfigCommon SEQUENCE { |
|||
|
physCellId |
Physical Cell Identity of NR Cell 2 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellIndex |
2 |
||
|
sCellConfigCommon SEQUENCE { |
|||
|
physCellId |
Physical Cell Identity of NR Cell 12 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
|
SCellIndex[1] |
2 |
entry 1 |
|
|
} |
|||
Table 8.2.4.2.1.1.3.3-8: RRCConnectionReconfiguration (step 7, Table 8.2.4.2.1.1.3.2-2)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with Condition EN-DC_PSCell_HO AND RBConfig_NoKeyChange |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nr-Config-r15 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
nr-SecondaryCellGroupConfig-r15 |
RRCReconfiguration |
OCTET STRING including the RRCReconfiguration |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.2.1.1.3.3-9: RRCReconfiguration (Table 8.2.4.2.1.1.3.3-8: RRCConnectionReconfiguration)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with Condition EN-DC |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
secondaryCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.2.1.1.3.3-10: CellGroupConfig (Table 8.2.4.2.1.1.3.3-10: RRCReconfiguration)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PSCell_change and SCell_Add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
spCellConfig SEQUENCE { |
|||
|
servCellIndex |
1 |
||
|
reconfigurationWithSync SEQUENCE { |
|||
|
spCellConfigCommon SEQUENCE { |
|||
|
physCellId |
Physical Cell Identity of NR Cell 12 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
sCellToAddModList |
Not present |
||
|
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
|
SCellIndex[1] |
2 |
entry 1 |
|
|
} |
|||
8.2.4.2.1.2 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release / EN-DC / Intra-band non-Contiguous CA
8.2.4.2.1.2.1 Test Purpose (TP)
Same as TC 8.2.4.2.1.1 but applied to Intra-band non-Contiguous CA.
8.2.4.2.1.2.2 Conformance requirements
Same as TC 8.2.4.2.1.1 but applied to Intra-band non-Contiguous CA.
8.2.4.2.1.2.3 Test description
8.2.4.2.1.2.3.1 Pre-test conditions
Same as TC 8.2.4.2.1.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.2.4.2.1.2.3.2 Test procedure sequence
Same as TC 8.2.4.2.1.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.2.4.2.1.3 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release / EN-DC / Inter-band CA
8.2.4.2.1.3.1 Test Purpose (TP)
Same as TC 8.2.4.2.1.1 but applied to Inter-band CA.
8.2.4.2.1.3.2 Conformance requirements
Same as TC 8.2.4.2.1.1 but applied to Inter-band CA.
8.2.4.2.1.3.3 Test description
8.2.4.2.1.3.3.1 Pre-test conditions
Same as TC 8.2.4.2.1.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
8.2.4.2.1.3.3.2 Test procedure sequence
Same as TC 8.2.4.2.1.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12
8.2.4.3 NR CA / SCell change / Intra-NR measurement event A6 / SRB3
8.2.4.3.1 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC
8.2.4.3.1.1 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Intra-band Contiguous CA
8.2.4.3.1.1.1 Test Purpose (TP)
(1)
with { UE in RRC_CONNECTED state with EN-DC, and MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured and SRB3 configured and Intra-NR measurement configured for event A6 }
ensure that {
when { Neighbour becomes offset better than NR SCell }
then { UE sends a Measurement Report message on SRB3 while entering condition for event A6 is satisfied }
}
(2)
with { UE in RRC_CONNECTED state with EN-DC, and MCG(s) (E-UTRA PDCP) and SCG with SCell(s) configured and Intra-NR measurement is configured for event A6 }
ensure that {
when { UE receives an RRCReconfiguration message containing sCellToReleaseList with an sCellIndex equalling to one of the current UE SCell configuration and sCellToAddModList with an sCellIndex set to the configured target SCell and servingCellMO equalling to one of the released SCell }
then { UE sends an RRCReconfigurationComplete message and changes the SCell and continues performing measurements on that SCell}
}
8.2.4.3.1.1.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 36.331, clause 5.3.5.3, TS 38.331, clauses 5.3.5.3, 5.3.5.5.8, 5.3.5.5.9, 5.5.4.7 and 5.5.5. Unless otherwise stated these are Rel-15 requirements.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
…
1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or
1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:
2> perform ENDC release as specified in TS38.331 [82], clause 5.3.5.10;
…
1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:
2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.5;
…
1> set the content of RRCConnectionReconfigurationComplete message as follows:
…
2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:
3> include scg-ConfigResponseNR in accordance with TS 38.331 [82, 5.3.5.3];
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
1> if the RRCReconfiguration includes the secondaryCellGroup:
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration message contains the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCReconfiguration was received via SRB1:
2> else (RRCReconfiguration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE: For EN-DC, in the case of SRB1, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case of SRB3, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.
1> else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
…
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell;
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
2> for each measId included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated;
[TS 38.331, clause 5.5.4.7]
The UE shall:
1> consider the entering condition for this event to be satisfied when condition A6-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A6-2, as specified below, is fulfilled;
1> for this measurement, consider the (secondary) cell corresponding to the measObjectNR associated to this event to be the serving cell.
NOTE: The reference signal(s) of the neighbour(s) and the reference signal(s) of the SCell are both indicated in the associated measObjectNR.
Inequality A6-1 (Entering condition)
Inequality A6-2 (Leaving condition)
The variables in the formula are defined as follows:
Mnis the measurement result of the neighbouring cell, not taking into account any offsets.
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within the associated measObjectNR), and set to zero if not configured for the neighbour cell.
Msis the measurement result of the serving cell, not taking into account any offsets.
Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within the associated measObjectNR), and is set to zero if not configured for the serving cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).
Off is the offset parameter for this event (i.e. a6-Offset as defined withinreportConfigNR for this event).
Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.
Ocn, Ocs, Hys, Off are expressed in dB.
[TS 38.331, clause 5.5.5]
Figure 5.5.5.1-1: Measurement reporting
The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this procedure only after successful security activation.
For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:
1> set the measId to the measurement identity that triggered the measurement reporting;
1> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR for each configured serving cell derived based on the rsType indicated in the associated reportConfig;
1> set the measResultServingCell within measResultServingMOList to include for each NR serving cell that is configured with servingCellMO, if any, the servCellId;
1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRsIndexes and maxNrofRSIndexesToReport:
2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2;
…
1> if there is at least one applicable neighbouring cell to report:
2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:
3> if the reportType is set to eventTriggered:
4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;
3> else:
4> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;
4> if reportQuantityRsIndexesand maxNrofRSIndexesToReport are configured, include beam measurement information as described in 5.5.5.2;
3> for each cell that is included in the measResultNeighCells, include the physCellId;
3> if the reportType is set to eventTriggered:
4> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:
5> if the measObject associated with this measId concerns NR:
6> if rsType in the associated reportConfig is set to ssb:
7> set resultsSSB-Cell within the measResult to include the SS/PBCH block based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in order of decreasing trigger quantity, i.e. the best cell is included first:
8> if reportQuantityRsIndexesand maxNrofRSIndexesToReport are configured, include beam measurement information as described in 5.5.5.2;
6> else if rsType in the associated reportConfig is set to csi-rs:
7> set resultsCSI-RS-Cell within the measResult to include the CSI-RS based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in order of decreasing trigger quantity, i.e. the best cell is included first:
8> if reportQuantityRsIndexesand maxNrofRSIndexesToReport are, include beam measurement information as described in 5.5.5.2;
5> if the measObject associated with this measId concerns E-UTRA:
6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfigInterRAT in order of decreasing E-UTRA trigger quantity, i.e. the best cell is included first;
1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;
1> stop the periodical reporting timer, if running;
1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:
2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;
…
1> if the UE is configured with EN-DC:
2> if SRB3 is configured:
3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;
2> else:
3> submit the MeasurementReport message via the EUTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10].
8.2.4.3.1.1.3 Test description
8.2.4.3.1.1.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 is the PCell. NR Cell 1 is the PSCell and NR Cell 3 is the SCell to be added, NR Cell 12 is the intra-frequency neighbour cell of NR Cell 3;
– NR Cell 3 and NR Cell 12 are Inactive SCells according to TS 38.508-1 [4] clause 6.3.3.2.
UE:
None.
Preamble:
– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC) and DC bearers (MCG(s) and SCG) according to TS 38.508-1 [4], table 4.5.4.
8.2.4.3.1.1.3.2 Test procedure sequence
Table 8.2.4.3.1.1.3.2-1 and table 8.2.4.3.1.1.3.2-1A illustrates the downlink power levels to be applied for E-UTRA Cell 1, NR Cell 1, NR Cell 3 and NR Cell 12 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.2.4.3.1.1.3.2-2.
Table 8.2.4.3.1.1.3.2-1: Power levels for conducted test environment
|
Parameter |
Unit |
E-UTRA Cell 1 |
NR Cell 1 |
NR Cell 3 |
NR Cell 12 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
– |
– |
– |
Power levels are such that entry condition for event A6 is not satisfied for NR Cell 3 when being an SCell:
but satisfied for NR Cell 12 when being an SCell:
|
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-79 |
-85 |
-97 |
||
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
– |
– |
– |
Power levels are such that entry condition for event A6 is satisfied for NR Cell 3 when being an SCell:
but not satisfied for NR Cell 12 when being an SCell:
|
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-79 |
-97 |
-85 |
Table 8.2.4.3.1.1.3.2-1A: Power levels for OTA test environment
|
Parameter |
Unit |
E-UTRA Cell 1 |
NR Cell 1 |
NR Cell 3 |
NR Cell 12 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-96 |
– |
– |
– |
Power levels are such that entry condition for event A6 is not satisfied for NR Cell 3 when being an SCell:
but satisfied for NR Cell 12 when being an SCell:
|
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-91 |
-91 |
-100 |
||
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-96 |
– |
– |
– |
Power levels are such that entry condition for event A6 is satisfied for NR Cell 3 when being an SCell:
but not satisfied for NR Cell 12 when being an SCell:
|
|
SS/PBCH SSS EPRE |
dBm/SCS |
– |
-91 |
-100 |
-91 |
Table 8.2.4.3.1.1.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionReconfiguration message containing RRCReconfiguration message to configure SCell (NR Cell 3) and SRB3. |
<– |
RRCConnectionReconfiguration(RRCReconfiguration) |
– |
– |
|
2 |
The UE transmits an RRCConnectionReconfigurationComplete message containing RRCReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete(RRCReconfigurationComplete) |
– |
– |
|
3 |
SS transmits an RRCConnectionReconfiguration message containing RRCReconfiguration message including measConfig to setup intra NR measurement and reporting for event A6 |
<– |
RRCConnectionReconfiguration(RRCReconfiguration) |
– |
– |
|
4 |
The UE transmits an RRCConnectionReconfigurationComplete message containing RRCReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete(RRCReconfigurationComplete) |
– |
– |
|
5 |
SS re-adjusts the cell-specific reference signal level according to row "T1" in table 8.2.4.3.1.1.3.2-1/1A. |
– |
– |
– |
– |
|
6 |
Check: Does the UE transmit a MeasurementReport message via SRB3 to report event A6 with the measured RSRP and RSRQ value for NR Cell 12? |
–> |
MeasurementReport |
1 |
P |
|
7 |
The SS transmits an RRCReconfiguration message including sCellToReleaseList with NR Cell 3 as SCell release and sCellToAddModList with NR Cell 12 as SCell addition via SRB3. |
<– |
RRCReconfiguration |
– |
– |
|
8 |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1. |
–> |
RRCReconfigurationComplete |
– |
– |
|
9 |
Check: Does the UE transmit a MeasurementReport message via SRB3 within the next 10s to report event A6? |
–> |
MeasurementReport |
2 |
F |
|
10 |
SS re-adjusts the cell-specific reference signal level according to row "T0" in table 8.2.4.3.1.1.3.2-1/1A. |
– |
– |
– |
– |
|
11 |
Check: Does the UE transmit a MeasurementReport message via SRB3 to report event A6 with the measured RSRP and RSRQ value for NR Cell 3? |
–> |
MeasurementReport |
2 |
P |
8.2.4.3.1.1.3.3 Specific message contents
Table 8.2.4.3.1.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.3.1.1.3.2-2)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 condition MCG_and_SCG. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nr-Config-r15 CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message according to the Table 8.2.4.3.1.1.3.3-2 |
|||
|
} |
||||
|
} |
||||
|
sk-Counter-r15 |
Not present |
|||
|
nr-RadioBearerConfig1-r15 |
OCTET STRING including RadioBearerConfig according TS 38.508-1 [67], table 4.6.3-132 with condition SRB3 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.4.3.1.1.3.3-2: RRCReconfiguration (step 1, Table 8.2.4.3.1.1.3.2-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
secondaryCellGroup |
CellGroupConfig-SRB3 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.4.3.1.1.3.3-3: CellGroupConfig-SRB3 (Table 8.2.4.3.1.1.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.8.1-2A. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CellGroupConfig ::= SEQUENCE { |
||||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig { |
1 entry |
|||
|
RLC-BearerConfig[1] |
RLC-BearerConfig with condition SRB3 |
entry 1 |
||
|
} |
||||
|
sCellToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SCellConfig { |
1 entry |
|||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
|||
|
sCellIndex |
2 |
|||
|
sCellConfigCommon |
ServingCellConfigCommon |
|||
|
sCellConfigDedicated |
ServingCellConfig |
TS 38.508-1 [4] table 4.6.3-167 |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.4.3.1.1.3.3-4: ServingCellConfigCommon (Table 8.2.4.3.1.1.3.3-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-168. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfigCommon ::= SEQUENCE { |
|||
|
PhysCellId |
Physical Cell Identity of NR Cell 3 |
||
|
} |
|||
Table 8.2.4.3.1.1.3.3-5: RRCReconfiguration (step 3, Table 8.2.4.3.1.1.3.2-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition EN-DC_MEAS. |
Table 8.2.4.3.1.1.3.3-6: MeasConfig (Table 8.2.4.3.1.1.3.3-5)
|
Derivation path: TS 38.508-1 [4], Table 4.6.3-69. |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
measConfig ::= SEQUENCE { |
|||
|
measObjectToAddModList SEQUENCE (SIZE (1.. maxNrofObjectId)) OF MeasObjectToAddMod { |
2 entries |
||
|
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
|
measObjectId |
1 |
NR Cell 1 |
|
|
measObject CHOICE { |
|||
|
measObjectNR |
MeasObjectNR(60) |
ssbFrequency IE equals the ARFCN for NR Cell 1 Thresh value set to -96dBm |
|
|
} |
|||
|
} |
|||
|
MeasObjectToAddMod[2] SEQUENCE { |
entry 2 |
||
|
measObjectId |
2 |
NR Cell 3 |
|
|
measObject CHOICE { |
|||
|
measObjectNR |
MeasObjectNR(67) |
ssbFrequency IE equals the ARFCN for NR Cell 3 Thresh value set to -89dBm |
FR1 |
|
MeasObjectNR(62) |
ssbFrequency IE equals the ARFCN for NR Cell 3 Thresh value set to -94dBm |
FR2 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
|
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
|
reportConfigId |
1 |
||
|
reportConfig CHOICE { |
|||
|
reportConfigNR |
ReportConfigNR(Delta(NRf2) – Delta(NRf1)) |
See Table 8.2.4.3.1.1.3.3-6A |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF MeasIdToAddMod { |
1 entry |
||
|
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
|
measId |
1 |
||
|
measObjectId |
2 |
||
|
reportConfigId |
1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
NOTE 1: Delta(NRf1) and Delta(NRf2) is derived based on calibration procedure defined in the TS 38.508-1 [4], clause 6.1.3.3 |
|||
Table 8.2.4.3.1.1.3.3-6A: ReportConfigNR (Table 8.2.4.3.1.1.3.3-6)
|
Derivation path: TS 38.508-1 [4], Table 4.6.3-142 condition EVENT_A6 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ReportConfigNR ::= SEQUENCE { |
|||
|
reportType CHOICE { |
|||
|
eventTriggered SEQUENCE { |
|||
|
reportAmount |
r1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.3.1.1.3.3-7: MeasurementReport (step 6, Table 8.2.4.3.1.1.3.2-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-5A. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasurementReport ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
measurementReport SEQUENCE { |
|||
|
measResults SEQUENCE { |
|||
|
measId |
1 |
||
|
measResultServingMOListSEQUENCE(SIZE (1..maxNrofServingCells)) OF MeasResultServMO { |
2 entries |
||
|
MeasResultServMO[1] SEQUENCE { |
entry 1 |
||
|
servCellId |
ServCellIndex of NR Cell 1 |
||
|
measResultServingCell SEQUENCE { |
Report NR Cell 1 |
||
|
physCellId |
physCellId of NR Cell 1 |
||
|
measResult SEQUENCE { |
|||
|
cellResults SEQUENCE { |
|||
|
resultsSSB-Cell SEQUENCE { |
|||
|
rsrp |
(0..127) |
||
|
rsrq |
(0..127) |
||
|
sinr |
(0..127) |
pc_ss_SINR_Meas |
|
|
Not present |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
MeasResultServMO[2] SEQUENCE { |
entry 2 |
||
|
servCellId |
ServCellIndex of NR Cell 3 |
||
|
measResultServingCell SEQUENCE { |
Report NR Cell 3 |
||
|
physCellId |
physCellId of NR Cell 3 |
||
|
measResult SEQUENCE { |
|||
|
cellResults SEQUENCE { |
|||
|
resultsSSB-Cell SEQUENCE { |
|||
|
rsrp |
(0..127) |
||
|
rsrq |
(0..127) |
||
|
sinr |
(0..127) |
pc_ss_SINR_Meas |
|
|
Not present |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
measResultNeighCells CHOICE { |
|||
|
measResultListNR[1] SEQUENCE { |
Report NR Cell 12 |
||
|
physCellId |
physCellId of NR Cell 12 |
||
|
measResult SEQUENCE { |
|||
|
cellResults SEQUENCE { |
|||
|
resultsSSB-Cell SEQUENCE { |
|||
|
rsrp |
(0..127) |
||
|
rsrq |
(0..127) |
||
|
sinr |
(0..127) |
pc_ss_SINR_Meas |
|
|
Not present |
|||
|
} |
|||
|
resultsCSI-RS-Cell |
Not present |
||
|
} |
|||
|
rsIndexResults |
Not present |
||
|
} |
|||
|
cgi-Info |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.4.3.1.1.3.3-8: RRCReconfiguration (step 7, Table 8.2.4.3.1.1.3.2-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
SecondaryCellGroup |
CellGroupConfig-SRB3 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.4.3.1.1.3.3-9: CellGroupConfig-SRB3 (Table 8.2.4.3.1.1.3.3-8)
|
Derivation Path: TS 38.508-1 [4], Table 4.8.1-2A. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CellGroupConfig ::= SEQUENCE { |
||||
|
sCellToAddModList SEQUENCE (SIZE (1.. maxNrofSCells)) OF SCellConfig { |
1 entry |
|||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
|||
|
sCellIndex |
3 |
|||
|
sCellConfigCommon |
ServingCellConfigCommon |
|||
|
sCellConfigDedicated |
ServingCellConfig |
TS 38.508-1 [4] table 4.6.3-167 |
||
|
} |
||||
|
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
|||
|
SCellIndex[1] |
2 |
entry 1 |
||
|
} |
||||
|
} |
||||
|
Note: ServingCellMO equal to the released SCell NR Cell 3. |
||||
Table 8.2.4.3.1.1.3.3-10: ServingCellConfigCommon (Table 8.2.4.3.1.1.3.3-9)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-168. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfigCommon ::= SEQUENCE { |
|||
|
PhysCellId |
Physical Cell Identity of NR Cell 12 |
||
|
} |
|||
Table 8.2.4.3.1.1.3.3-11: MeasurementReport (step 11, Table 8.2.4.3.1.1.3.2-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-5A. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasurementReport ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
measurementReport SEQUENCE { |
|||
|
measResults SEQUENCE { |
|||
|
measId |
1 |
||
|
measResultServingMOList SEQUENCE(SIZE (1..maxNrofServingCells)) OF MeasResultServMO { |
2 entries |
||
|
MeasResultServMO[1] SEQUENCE { |
entry 1 |
||
|
servCellId |
ServCellIndex of NR Cell 1 |
||
|
measResultServingCell SEQUENCE { |
Report NR Cell 1 |
||
|
physCellId |
physCellId of NR Cell 1 |
||
|
measResult SEQUENCE { |
|||
|
cellResults SEQUENCE { |
|||
|
resultsSSB-Cell SEQUENCE { |
|||
|
rsrp |
(0..127) |
||
|
rsrq |
(0..127) |
||
|
sinr |
(0..127) |
pc_ss_SINR_Meas |
|
|
Not present |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
MeasResultServMO[2] SEQUENCE { |
entry 2 |
||
|
servCellId |
ServCellIndex of NR Cell 12 |
||
|
measResultServingCell SEQUENCE { |
Report NR Cell 12 |
||
|
physCellId |
physCellId of NR Cell 12 |
||
|
measResult SEQUENCE { |
|||
|
cellResults SEQUENCE { |
|||
|
resultsSSB-Cell SEQUENCE { |
|||
|
rsrp |
(0..127) |
||
|
rsrq |
(0..127) |
||
|
sinr |
(0..127) |
pc_ss_SINR_Meas |
|
|
Not present |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
measResultNeighCells CHOICE { |
|||
|
measResultListNR SEQUENCE (SIZE (1.. maxCellReport)) OF MeasResultNR { |
1 entry |
Report NR Cell 3 |
|
|
MeasResultNR[1] SEQUENCE { |
entry 1 |
||
|
physCellId |
physCellId of NR Cell 3 |
||
|
measResult SEQUENCE { |
|||
|
cellResults SEQUENCE { |
|||
|
resultsSSB-Cell SEQUENCE { |
|||
|
rsrp |
(0..127) |
||
|
rsrq |
(0..127) |
||
|
sinr |
(0..127) |
pc_ss_SINR_Meas |
|
|
Not present |
|||
|
} |
|||
|
resultsCSI-RS-Cell |
Not present |
||
|
} |
|||
|
rsIndexResults |
Not present |
||
|
} |
|||
|
cgi-Info |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.2.4.3.1.2 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Intra-band non-Contiguous CA
The scope and description of the present TC is the same as test case 8.2.4.3.1.1 with the following differences:
– CA configuration: Intra-band non-contiguous CA replaces Intra-band Contiguous CA
8.2.4.3.1.3 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Inter-band CA
8.2.4.3.1.3.1 Test Purpose (TP)
Same as TC 8.2.4.3.1.1 but applied to Inter-band CA case.
8.2.4.3.1.3.2 Conformance requirements
Same as TC 8.2.4.3.1.1.
8.2.4.3.1.3.3 Test description
8.2.4.3.1.3.3.1 Pre-test conditions
Same as test case 8.2.4.3.1.1 with the following differences:
– Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12
8.2.4.3.1.3.3.2 Test procedure sequence
Same as test case 8.2.4.3.1.1 with the following differences:
– Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12
8.2.4.3.1.3.3.3 Specific message contents
Table 8.2.4.3.1.3.3.3-1: MeasConfig (Table 8.2.4.3.1.1.3.3-6)
|
Derivation path: TS 38.508-1 [4], Table 4.6.3-69. |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
measConfig ::= SEQUENCE { |
|||
|
measObjectToAddModList SEQUENCE (SIZE (1.. maxNrofObjectId)) OF MeasObjectToAddMod { |
2 entries |
||
|
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
|
measObjectId |
1 |
NR Cell 1 |
|
|
measObject CHOICE { |
|||
|
measObjectNR |
MeasObjectNR(60) |
ssbFrequency IE equals the ARFCN for NR Cell 1 Thresh value set to -96dBm |
|
|
} |
|||
|
} |
|||
|
MeasObjectToAddMod[2] SEQUENCE { |
entry 2 |
||
|
measObjectId |
2 |
NR Cell 10 |
|
|
measObject CHOICE { |
|||
|
measObjectNR |
MeasObjectNR(67) |
ssbFrequency IE equals the ARFCN for NR Cell 10 Thresh value set to -89dBm |
FR1 |
|
MeasObjectNR(62) |
ssbFrequency IE equals the ARFCN for NR Cell 10 Thresh value set to -94dBm |
FR2 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
|
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
|
reportConfigId |
1 |
||
|
reportConfig CHOICE { |
|||
|
reportConfigNR |
ReportConfigNR(2) |
TS 38.508-1 [4] table 4.6.3-142 condition EVENT_A6 |
FR1 |
|
reportConfigNR |
ReportConfigNR(Delta(NRf2) – Delta(NRf1)) |
TS 38.508-1 [4] table 4.6.3-142 condition EVENT_A6 |
FR2 |
|
} |
|||
|
} |
|||
|
} |
|||
|
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF MeasIdToAddMod { |
1 entry |
||
|
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
|
measId |
1 |
||
|
measObjectId |
2 |
||
|
reportConfigId |
1 |
||
|
} |
|||
|
} |
|||
|
} |
|||