8.1.5 RRC others
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
8.1.5.1 UE capability transfer
8.1.5.1.1 UE capability transfer / Success
8.1.5.1.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an UECapabilityEnquiry message }
then { UE transmits an UECapabilityInformation message including UE radio access capability information corresponding to the ue-CapabilityRequest variable }
}
8.1.5.1.1.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.6.1.3, 5.6.1.4, 5.7.7.2 and 5.7.7.3.
[TS 38.331, clause 5.6.1.3]
The UE shall set the contents of UECapabilityInformation message as follows:
1> if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to nr:
2> include in the ue-CapabilityRAT-ContainerList a UE-CapabilityRAT-Container of the type UE-NR-Capability and with the rat-Type set to nr;
2> include the supportedBandCombinationList, featureSets and featureSetCombinations as specified in clause 5.6.1.4;
…
1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends.
[TS 38.331, clause 5.6.1.4]
The UE invokes the procedures in this clause if the NR or E-UTRA network requests UE capabilities for nr, eutra-nr or eutra. This procedure is invoked once per requested rat-Type (see clause 5.6.1.3 for capability enquiry by the NR network; see TS 36.331 [10], clause 5.6.3.3 for capability enquiry by the E-UTRA network). The UE shall ensure that the feature set IDs are consistent across feature sets, feature set combinations and band combinations in all three UE capability containers that the network queries with the same fields with the same values, i.e. UE-CapabilityRequestFilterNR and fields in UECapabilityEnquiry message (i.e. requestedFreqBandsNR-MRDC, requestedCapabilityNR and eutra-nr-only flag) as defined in TS 36.331, where applicable.
NOTE 1: Capability enquiry without frequencyBandListFilter is not supported.
[TS 38.331, clause 5.7.7.2]
A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:
1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and
1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323 [5];
Upon initiating the procedure, the UE shall:
1> initiate transmission of the ULDedicatedMessageSegment message as specified in 5.7.7.3;
[TS 38.331, clause 5.7.7.3]
The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 38.323 [5]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:
1> F or each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;
1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;
1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:
2> set the rrc-MessageSegmentType to lastSegment;
1> else:
2> set the rrc-MessageSegmentType to notLastSegment;
1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.
8.1.5.1.1.3 Test Description
8.1.5.1.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cell.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A on NR Cell 1.
8.1.5.1.1.3.2 Test procedure sequence
Table 8.1.5.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits a UECapabilityEnquiry message including nr and rrc-segAllowed-r16 set to enabled. |
<– |
UECapabilityEnquiry |
– |
– |
|
– |
EXCEPTION: The "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message. IF pc_NR_UL_Segmentation and UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then steps 2a1 and 2a2 will be performed else step 2b1 will be performed |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 2a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the UlDedicatedMessageSegment message indicates rrc-MessageSegmentType-r16 = lastSegment. |
– |
– |
– |
– |
|
2a1 |
The UE sends segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message? |
–> |
ULDedicatedMessageSegment |
– |
– |
|
2a2 |
Check: Is the received UE radio access capability information as per the ue-CapabilityRequest variable? |
– |
– |
1 |
P |
|
2b1 |
Check: Does the UE transmit a UECapabilityInformation message including UE radio access capability information as per the ue-CapabilityRequest variable? |
–> |
UECapabilityInformation |
1 |
P |
8.1.5.1.1.3.3 Specific message contents
Table 8.1.5.1.1.3.3-1: UECapabilityEnquiry (step 1, Table 8.1.5.1.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-31 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UECapabilityEnquiry ::= SEQUENCE { |
|||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
||
|
criticalExtensions CHOICE { |
|||
|
ueCapabilityEnquiry SEQUENCE { |
|||
|
ue-CapabilityRAT-RequestList SEQUENCE (SIZE (1.. maxRAT-CapabilityContainers)) OF CapabilityRAT-Request { |
– |
||
|
UE-CapabilityRAT-Request[1] SEQUENCE { |
entry 1 |
||
|
rat-Type |
nr |
||
|
} |
|||
|
} |
|||
|
lateNonCriticalExtension |
Not present |
||
|
ue-CapabilityEnquiryExt |
OCTET STRING Containing UECapabilityEnquiry-v1560-IEs |
||
|
} |
|||
|
criticalExtensionsFuture |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.1.1.3.3-2: UECapabilityInformation (steps2a2 and 2b1, Table 8.1.5.1.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-32 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UECapabilityInformation ::= SEQUENCE { |
|||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
||
|
criticalExtensions CHOICE { |
|||
|
ueCapabilityInformation SEQUENCE { |
|||
|
ue-CapabilityRAT-ContainerList SEQUENCE (SIZE (0..maxRAT-CapabilityContainers)) OF CapabilityRAT-Request { |
|||
|
UE-CapabilityRAT-Request[1] SEQUENCE { |
entry 1 |
||
|
rat-Type |
nr |
||
|
ueCapabilityRAT-Container |
UE-NR-Capability |
Encoded as per TS 38.331 [12] clause 5.6.1 |
|
|
} |
|||
|
} |
|||
|
lateNonCriticalExtension |
Not checked |
||
|
nonCriticalExtension |
Not checked |
||
|
} |
|||
|
criticalExtensionsFuture |
Not checked |
||
|
} |
|||
|
} |
|||
Table 8.1.5.1.1.3.3-3: UE-NR-Capability (Table 8.1.5.1.1.3.3-2)
|
Derivation Path: TS 38.331 [12], clause 6.3.3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UE-NR-Capability ::= SEQUENCE { |
|||
|
accessStratumRelease |
Checked |
"rel-15" or higher |
|
|
pdcp-Parameters SEQUENCE { |
|||
|
supportedROHC-Profiles SEQUENCE { |
|||
|
profile0x0000 |
Not checked |
||
|
profile0x0001 |
Not checked |
||
|
profile0x0002 |
Not checked |
||
|
profile0x0003 |
Not checked |
||
|
profile0x0004 |
Not checked |
||
|
profile0x0006 |
Not checked |
||
|
profile0x0101 |
Not checked |
||
|
profile0x0102 |
Not checked |
||
|
profile0x0103 |
Not checked |
||
|
profile0x0104 |
Not checked |
||
|
} |
|||
|
maxNumberROHC-ContextSessions |
Not checked |
||
|
uplinkOnlyROHC-Profiles |
Not checked |
||
|
continueROHC-Context |
Not checked |
||
|
outOfOrderDelivery |
Checked |
pc_outOfOrderDelivery |
|
|
shortSN |
Checked |
pc_shortSN |
|
|
pdcp-DuplicationSRB |
Checked |
pc_pdcp_DuplicationSplitSRB |
|
|
pdcp-DuplicationMCG-OrSCG-DRB |
Checked |
pc_pdcp_DuplicationMCG_OrSCG_DRB |
|
|
drb-IAB-r16 |
Not checked |
||
|
non-DRB-IAB-r16 |
Not checked |
||
|
extendedDiscardTimer-r16 |
Not checked |
||
|
continueEHC-Context-r16 |
Not checked |
||
|
ehc-r16 |
Checked |
pc_NR_ehc_r16 |
|
|
maxNumberEHC-Contexts-r16 |
Not checked |
||
|
jointEHC-ROHC-Config-r16 |
Not checked |
||
|
pdcp-DuplicationMoreThanTwoRLC-r16 |
Checked |
pc_pdcp_DuplicationMoreThanTwoRLC_r16 |
|
|
} |
|||
|
rlc-Parameters SEQUENCE { |
|||
|
am-WithShortSN |
Checked |
pc_am_WithShortSN |
|
|
um-WithShortSN |
Checked |
pc_um_WithShortSN |
|
|
um-WithLongSN |
Checked |
pc_um_WIthLongSN |
|
|
} |
|||
|
mac-Parameters SEQUENCE { |
|||
|
mac-ParametersCommon SEQUENCE { |
|||
|
lcp-Restriction |
Checked |
pc_lcp_Restriction |
|
|
dummy |
Not checked |
||
|
lch-ToSCellRestriction |
Not checked |
||
|
recommendedBitRate |
Checked |
pc_recommendedBitRate |
|
|
recommendedBitRateQuery |
Checked |
pc_recommendedBitRateQuery |
|
|
recommendedBitRateMultiplier-r16 |
Not checked |
||
|
preEmptiveBSR-r16 |
Not checked |
||
|
autonomousTransmission-r16 |
Not checked |
||
|
lch-PriorityBasedPrioritization-r16 |
Checked |
pc_lch_PriorityBasedPrioritization_r16 |
|
|
lch-ToConfiguredGrantMapping-r16 |
Not checked |
||
|
lch-ToGrantPriorityRestriction-r16 |
Checked |
pc_lch_ToGrantPriorityRestriction_r16 |
|
|
singlePHR-P-r16 |
Not checked |
||
|
ul-LBT-FailureDetectionRecovery-r16 |
Not checked |
||
|
tdd-MPE-P-MPR-Reporting-r16 |
Not checked |
||
|
lcid-ExtensionIAB-r16 |
Not checked |
||
|
spCell-BFR-CBRA-r16 |
Not checked |
||
|
srs-ResourceId-Ext-r16 |
Not checked |
||
|
} |
|||
|
mac-ParametersXDD-Diff SEQUENCE { |
|||
|
skipUplinkTxDynamic |
Checked (NOTE 4) |
pc_skipUplinkTxDynamic |
|
|
logicalChannelSR-DelayTimer |
Checked (NOTE 5) |
pc_logicalChannelSR_DelayTimer |
|
|
longDRX-Cycle |
Checked (NOTE 6) |
pc_longDRX_Cycle |
|
|
shortDRX-Cycle |
Checked (NOTE 7) |
pc_shortDRX_Cycle |
|
|
multipleSR-Configurations |
Not checked |
||
|
multipleConfiguredGrants |
Checked (NOTE 12) |
pc_multipleConfiguredGrants_r16 |
|
|
} |
|||
|
} |
|||
|
phy-Parameters SEQUENCE { |
|||
|
phy-ParametersCommon SEQUENCE { |
|||
|
csi-RS-CFRA-ForHO |
Checked |
pc_csi_RS_CFRA_ForHO |
|
|
dynamicPRB-BundlingDL |
Not checked |
||
|
sp-CSI-ReportPUCCH |
Not checked |
||
|
sp-CSI-ReportPUSCH |
Not checked |
||
|
nzp-CSI-RS-IntefMgmt |
Not checked |
||
|
type2-SP-CSI-Feedback-LongPUCCH |
Not checked |
||
|
precoderGranularityCORESET |
Not checked |
||
|
dynamicHARQ-ACK-Codebook |
supported |
||
|
semiStaticHARQ-ACK-Codebook |
Not checked |
||
|
spatialBundlingHARQ-ACK |
Checked |
pc_spatialBundlingHARQ_ACK |
|
|
dynamicBetaOffsetInd-HARQ-ACK-CSI |
Not checked |
||
|
pucch-Repetition-F1-3-4 |
Not checked |
||
|
ra-Type0-PUSCH |
Checked |
pc_ra_Type0_PUSCH |
|
|
dynamicSwitchRA-Type0-1-PDSCH |
Checked |
pc_dynamicSwitchRA_Type0_1_PDSCH |
|
|
dynamicSwitchRA-Type0-1-PUSCH |
Checked |
pc_dynamicSwitchRA_Type0_1_PUSCH |
|
|
pdsch-MappingTypeA |
supported |
pc_pdsch_MappingTypeA |
|
|
pdsch-MappingTypeB |
Checked |
pc_pdsch_MappingTypeB |
|
|
interleavingVRB-ToPRB-PDSCH |
Checked |
pc_interleavingVRB_ToPRB_PDSCH |
|
|
interSlotFreqHopping-PUSCH |
Not checked |
||
|
type1-PUSCH-RepetitionMultiSlots |
Not checked |
||
|
type2-PUSCH-RepetitionMultiSlots |
Not checked |
||
|
pusch-RepetitionMultiSlots |
Checked |
pc_pusch_RepetitionMultiSlots |
|
|
pdsch-RepetitionMultiSlots |
Checked |
pc_pdsch_RepetitionMultiSlots |
|
|
downlinkSPS |
Checked |
pc_downlinkSPS |
|
|
configuredUL-GrantType1 |
Checked |
pc_configuredUL_GrantType1 |
|
|
configuredUL-GrantType2 |
Checked |
pc_configuredUL_GrantType2 |
|
|
pre-EmptIndication-DL |
Not checked |
||
|
cbg-TransIndication-DL |
Not checked |
||
|
cbg-TransIndication-UL |
Not checked |
||
|
cbg-FlushIndication-DL |
Not checked |
||
|
dynamicHARQ-ACK-CodeB-CBG-Retx-DL |
Not checked |
||
|
rateMatchingResrcSetSemi-Static |
Not checked |
||
|
rateMatchingResrcSetDynamic |
Not checked |
||
|
bwp-SwitchingDelay |
Checked |
38.306, 4.2.7.10: It is mandatory to report type 1 or type 2. This capability is not applicable to IAB-MT |
pc_bwp_SwitchingDelay_Type1 or pc_bwp_SwitchingDelay_Type2 |
|
dummy |
Not checked |
||
|
maxNumberSearchSpaces |
n10 |
||
|
rateMatchingCtrlResrsSetDynamic |
Not checked |
||
|
maxLayersMIMO-Indication |
Not checked |
||
|
spCellPlacement |
Not checked |
||
|
twoStepRACH-r16 |
Not checked |
||
|
dci-Format1-2And0-2-r16 |
Checked |
pc_dci_Format1_2And0_2_r16 |
|
|
monitoringDCI-SameSearchSpace-r16 |
Not checked |
||
|
type2-CG-ReleaseDCI-0-1-r16 |
Not checked |
||
|
type2-CG-ReleaseDCI-0-2-r16 |
Not checked |
||
|
sps-ReleaseDCI-1-1-r16 |
Not checked |
||
|
sps-ReleaseDCI-1-2-r16 |
Not checked |
||
|
csi-TriggerStateNon-ActiveBWP-r16 |
Not checked |
||
|
seperateSMTC-InterIAB-Support-r16 |
Not checked |
||
|
seperateRACH-IAB-Support-r16 |
Not checked |
||
|
ul-flexibleDL-SlotFormatSemiStatic-IAB-r16 |
Not checked |
||
|
ul-flexibleDL-SlotFormatDynamics-IAB-r16 |
Not checked |
||
|
dft-S-OFDM-WaveformUL-IAB-r16 |
Not checked |
||
|
dci-25-AI-RNTI-Support-IAB-r16 |
Not checked |
||
|
t-DeltaReceptionSupport-IAB-r16 |
Not checked |
||
|
guardSymbolReportReception-IAB-r16 |
Not checked |
||
|
harqACK-CB-SpatialBundlingPUCCH-Group-r16 |
Not checked |
||
|
crossSlotScheduling-r16 |
Not checked |
||
|
maxNumberSRS-PosPathLossEstimateAllServingCells-r16 |
Not checked |
||
|
extendedCG-Periodicities-r16 |
Not checked |
||
|
extendedSPS-Periodicities-r16 |
Not checked |
||
|
codebookVariantsList-r16 |
Not checked |
||
|
pusch-RepetitionTypeA-r16 |
Not checked |
||
|
dci-DL-PriorityIndicator-r16 |
Checked |
pc_dci_DL_PriorityIndicator_r16 |
|
|
dci-UL-PriorityIndicator-r16 |
Checked |
pc_dci_UL_PriorityIndicator_r16 |
|
|
maxNumberPathlossRS-Update-r16 |
Not checked |
||
|
type2-HARQ-ACK-Codebook-r16 |
Not checked |
||
|
maxTotalResourcesForAcrossFreqRanges-r16 |
Not checked |
||
|
harqACK-separateMultiDCI-MultiTRP-r16 |
Not checked |
||
|
harqACK-jointMultiDCI-MultiTRP-r16 |
Not checked |
||
|
bwp-SwitchingMultiCCs-r16 |
Not checked |
||
|
targetSMTC-SCG-r16 |
Not checked |
||
|
supportRepetitionZeroOffsetRV-r16 |
Not checked |
||
|
cbg-TransInOrderPUSCH-UL-r16 |
Not checked |
||
|
bwp-SwitchingMultiDormancyCCs-r16 |
Not checked |
||
|
supportRetx-Diff-CoresetPool-Multi-DCI-TRP-r16 |
Not checked |
||
|
pdcch-MonitoringAnyOccasionsWithSpanGapCrossCarrierSch-r16 |
Not checked |
||
|
newBeamIdentifications2PortCSI-RS-r16 |
Not checked |
||
|
pathlossEstimation2PortCSI-RS-r16 |
Not checked |
||
|
} |
|||
|
phy-ParametersXDD-Diff SEQUENCE { |
|||
|
dynamicSFI |
Not checked |
||
|
twoPUCCH-F0-2-ConsecSymbols |
Not checked |
||
|
twoDifferentTPC-Loop-PUSCH |
Not checked |
||
|
twoDifferentTPC-Loop-PUCCH |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeA |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeB |
Not checked |
||
|
ul-SchedulingOffset |
Not checked |
||
|
} |
|||
|
phy-ParametersFRX-Diff SEQUENCE { |
|||
|
dynamicSFI |
Not checked |
||
|
dummy1 |
Not checked |
||
|
twoFL-DMRS |
Not checked |
||
|
dummy2 |
Not checked |
||
|
dummy3 |
Not checked |
||
|
supportedDMRS-TypeDL |
Not checked |
||
|
supportedDMRS-TypeUL |
Not checked |
||
|
semiOpenLoopCSI |
Not checked |
||
|
csi-ReportWithoutPMI |
Not checked |
||
|
csi-ReportWithoutCQI |
Not checked |
||
|
onePortsPTRS |
Not checked |
||
|
twoPUCCH-F0-2-ConsecSymbols |
Not checked |
||
|
pucch-F2-WithFH |
supported |
||
|
pucch-F3-WithFH |
supported |
||
|
pucch-F4-WithFH |
Not checked |
||
|
freqHoppingPUCCH-F0-2 |
Not checked |
||
|
freqHoppingPUCCH-F1-3-4 |
Not checked |
||
|
mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot |
Not checked |
||
|
uci-CodeBlockSegmentation |
Not checked |
||
|
onePUCCH-LongAndShortFormat |
Not checked |
||
|
twoPUCCH-AnyOthersInSlot |
Not checked |
||
|
intraSlotFreqHopping-PUSCH |
Not checked |
||
|
pusch-LBRM |
Not checked |
||
|
pdcch-BlindDetectionCA |
Not checked |
||
|
tpc-PUSCH-RNTI |
Not checked |
||
|
tpc-PUCCH-RNTI |
Not checked |
||
|
tpc-SRS-RNTI |
Not checked |
||
|
absoluteTPC-Command |
Not checked |
||
|
twoDifferentTPC-Loop-PUSCH |
Not checked |
||
|
twoDifferentTPC-Loop-PUCCH |
Not checked |
||
|
pusch-HalfPi-BPSK |
Not checked |
||
|
pucch-F3-4-HalfPi-BPSK |
Not checked |
||
|
almostContiguousCP-OFDM-UL |
Not checked |
||
|
sp-CSI-RS |
Not checked |
||
|
sp-CSI-IM |
Not checked |
||
|
tdd-MultiDL-UL-SwitchPerSlot |
Not checked |
||
|
multipleCORESET |
Not checked |
||
|
csi-RS-IM-ReceptionForFeedback |
Not checked |
CSI-RS-IM-ReceptionForFeedback |
|
|
csi-RS-ProcFrameworkForSRS |
Not checked |
CSI-RS-ProcFrameworkForSRS |
|
|
csi-ReportFramework |
Not checked |
CSI-ReportFramework |
|
|
mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot SEQUENCE { |
|||
|
sameSymbol |
Not checked |
||
|
diffSymbol |
Not checked |
||
|
} |
|||
|
mux-SR-HARQ-ACK-PUCCH |
Not checked |
||
|
mux-MultipleGroupCtrlCH-Overlap |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeA |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeB |
Not checked |
||
|
ul-SchedulingOffset |
Not checked |
||
|
dl-64QAM-MCS-TableAlt |
Not checked |
||
|
ul-64QAM-MCS-TableAlt |
Not checked |
||
|
cqi-TableAlt |
Not checked |
||
|
oneFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
twoFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
oneFL-DMRS-ThreeAdditionalDMRS-UL |
Not checked |
||
|
} |
|||
|
phy-ParametersFR1 SEQUENCE { |
|||
|
pdcchMonitoringSingleOccasion |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
pdsch-256QAM-FR1 |
Checked |
pc_pdsch_256QAM_FR1 |
|
|
pdsch-RE-MappingFR1-PerSymbol |
Not checked |
||
|
pdsch-RE-MappingFR1-PerSlot |
Not checked |
||
|
} |
|||
|
phy-ParametersFR2 SEQUENCE { |
|||
|
dummy |
Not checked |
||
|
pdsch-RE-MappingFR2-PerSymbol |
Not checked |
||
|
pCell-FR2 |
Not checked |
||
|
pdsch-RE-MappingFR2-PerSlot |
Not checked |
||
|
} |
|||
|
} |
|||
|
rf-Parameters SEQUENCE { |
|||
|
supportedBandListNR SEQUENCE (SIZE (1..maxBands)) OF BandNR { |
|||
|
BandNR[i] SEQUENCE { |
|||
|
bandNR |
Checked |
Checked for ‘maxBands’ entries of FreqBandIndicatorNR[i] |
pc_nrBandx (‘x’ being the band number/type related PICS listed in TS 38.508-2) |
|
modifiedMPR-Behaviour |
Not checked |
||
|
mimo-ParametersPerBand |
Not checked |
MIMO-ParametersPerBand[i] |
|
|
extendedCP |
Not checked |
||
|
multipleTCI |
supported |
||
|
bwp-WithoutRestriction |
Checked |
pc_bwp_WithoutRestriction |
|
|
bwp-SameNumerology |
Not checked |
||
|
bwp-DiffNumerology |
Not checked |
||
|
crossCarrierScheduling-SameSCS |
Not checked |
||
|
pdsch-256QAM-FR2 |
Checked |
Note 8 |
pc_pdsch_256QAM_FR2 |
|
pusch-256QAM |
Checked |
Note 9 |
pc_pusch_256QAM_FR1 OR pc_pusch_256QAM_FR2 |
|
ue-PowerClass |
Not checked |
||
|
rateMatchingLTE-CRS |
Not checked |
||
|
channelBWs-DL-v1530 CHOICE { |
|||
|
fr1 SEQUENCE { |
|||
|
scs-15kHz |
Not checked |
||
|
scs-30kHz |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
} |
|||
|
fr2 SEQUENCE { |
|||
|
scs-60kHz |
Not checked |
||
|
scs-120kHz |
Not checked |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
channelBWs-UL-v1530[i] CHOICE { |
|||
|
fr1 SEQUENCE { |
|||
|
scs-15kHz |
Not checked |
||
|
scs-30kHz |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
} |
|||
|
fr2 SEQUENCE { |
|||
|
scs-60kHz |
Not checked |
||
|
scs-120kHz |
Not checked |
||
|
} |
|||
|
maxUplinkDutyCycle-PC2-FR1 |
Not checked |
||
|
pucch-SpatialRelInfoMAC-CE |
Not checked |
||
|
powerBoosting-pi2BPSK |
Not checked |
||
|
maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 |
Checked |
pc_nrBandx_maxUplinkDutyCycle_PC1dot5_MPE_FR1_r16 (‘x’ being the band number related PICS listed in Table A.4.3.1-4h of TS 38.508-2) |
|
|
maxUplinkDutyCycle-FR2 |
Not checked |
||
|
channelBWs-DL-v1590 |
Not checked |
||
|
channelBWs-UL-v1590 |
Not checked |
||
|
asymmetricBandwidthCombinationSet |
Not checked |
||
|
sharedSpectrumChAccessParamsPerBand-r16 |
Not checked |
||
|
cancelOverlappingPUSCH-r16 |
Not checked |
||
|
multipleRateMatchingEUTRA-CRS-r16 |
Not checked |
||
|
overlapRateMatchingEUTRA-CRS-r16 |
Not checked |
||
|
pdsch-MappingTypeB-Alt-r16 |
Not checked |
||
|
oneSlotPeriodicTRS-r16 |
Not checked |
||
|
olpc-SRS-Pos-r16 |
Not checked |
||
|
spatialRelationsSRS-Pos-r16 |
Not checked |
||
|
simulSRS-MIMO-TransWithinBand-r16 |
Not checked |
||
|
channelBW-DL-IAB-r16 |
Not checked |
||
|
channelBW-UL-IAB-r16 |
Not checked |
||
|
rasterShift7dot5-IAB-r16 |
Not checked |
||
|
ue-PowerClass-v1610 |
Not checked |
||
|
condHandover-r16 |
Checked |
pc_condHandover_r16 |
|
|
condHandoverFailure-r16 |
Checked |
pc_condHandoverFailure_r16 |
|
|
condHandoverTwoTriggerEvents-r16 |
Checked |
pc_condHandoverTwoTriggerEvents_r16 |
|
|
condPSCellChange-r16 |
Checked |
pc_condPSCellChange_r16 |
|
|
condPSCellChangeTwoTriggerEvents-r16 |
Not checked |
||
|
mpr-PowerBoost-FR2-r16 |
Not checked |
||
|
activeConfiguredGrant-r16 |
Not checked |
||
|
jointReleaseConfiguredGrantType2-r16 |
Not checked |
||
|
sps-r16 |
Not checked |
||
|
jointReleaseSPS-r16 |
Not checked |
||
|
simulSRS-TransWithinBand-r16 |
Not checked |
||
|
trs-AdditionalBandwidth-r16 |
Not checked |
||
|
handoverIntraF-IAB-r16 |
Not checked |
||
|
simulTX-SRS-AntSwitchingIntraBandUL-CA-r16 |
Not checked |
||
|
sharedSpectrumChAccessParamsPerBand-v1630 |
Not checked |
||
|
handoverUTRA-FDD-r16 |
Not checked |
||
|
enhancedUL-TransientPeriod-r16 |
Not checked |
||
|
sharedSpectrumChAccessParamsPerBand-v1640 |
Not checked |
||
|
type1-PUSCH-RepetitionMultiSlots-v1650 |
Not checked |
||
|
type2-PUSCH-RepetitionMultiSlots-v1650 |
Not checked |
||
|
pusch-RepetitionMultiSlots-v1650 |
Not checked |
||
|
configuredUL-GrantType1-v1650 |
Not checked |
||
|
configuredUL-GrantType2-v1650 |
Not checked |
||
|
sharedSpectrumChAccessParamsPerBand-v1650 |
Not checked |
||
|
enhancedSkipUplinkTxConfigured-v1660 |
Not checked |
||
|
enhancedSkipUplinkTxDynamic-v1660 |
Not checked |
||
|
} |
|||
|
} |
|||
|
supportedBandCombinationList SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination { |
|||
|
BandCombinationSEQUENCE { |
|||
|
bandList SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters { |
|||
|
BandParameters CHOICE |
|||
|
eutra SEQUENCE { |
|||
|
bandEUTRA |
Not checked |
FreqBandIndicatorEUTRA |
|
|
ca-BandwidthClassDL-EUTRA |
Not checked |
CA-BandwidthClassEUTRA |
|
|
ca-BandwidthClassUL-EUTRA |
Not checked |
CA-BandwidthClassEUTRA |
|
|
} |
|||
|
nr SEQUENCE { |
|||
|
bandNR |
Not checked |
FreqBandIndicatorNR |
|
|
ca-BandwidthClassDL-NR |
Not checked |
CA-BandwidthClassNR |
|
|
ca-BandwidthClassUL-NR |
Not checked |
CA-BandwidthClassNR |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
featureSetCombination |
Not checked |
FeatureSetCombinationId |
|
|
ca-ParametersEUTRA |
Not checked |
CA-ParametersEUTRA |
|
|
ca-ParametersNR |
Not checked |
CA-ParametersNR |
|
|
mrdc-Parameters |
Not checked |
MRDC-Parameters |
|
|
supportedBandwidthCombinationSet |
Not checked |
||
|
powerClass-v1530 |
Not checked |
||
|
} |
|||
|
appliedFreqBandListFilter |
Not checked |
FreqBandList |
|
|
supportedBandCombinationList-v1540 SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1540 { |
BandCombinationList-v1540 |
||
|
BandCombination-v1540 SEQUENCE { |
|||
|
bandList-v1540 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1540 { |
Not checked |
BandParameters-v1540 |
|
|
BandParameters-v1540 SEQUENCE { |
|||
|
srs-CarrierSwitch CHOICE { |
|||
|
nr SEQUENCE [ |
NR bands |
||
|
srs-SwitchingTimesListNR SEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingTimeNR |
Not checked |
||
|
} |
|||
|
eutra SEQUENCE { |
EUTRA bands |
||
|
srs-SwitchingTimesListEUTRA SEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingTimeEUTRA |
Not checked |
||
|
} |
|||
|
} |
|||
|
srs-TxSwitch-v1540 SEQUENCE { |
|||
|
supportedSRS-TxPortSwitch |
Not checked |
||
|
txSwitchImpactToRx |
Not checked |
||
|
txSwitchWithAnotherBand |
Not checked |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
ca-ParametersNR-v1540[i] |
Not checked |
CA-ParametersNR-v1540 |
|
|
} |
|||
|
} |
|||
|
srs-SwitchingTimeRequested |
Not checked |
||
|
supportedBandCombinationList-v1550 |
Not checked |
BandCombinationList-v1550 |
|
|
supportedBandCombinationList-v1560 |
Not checked |
BandCombinationList-v1560 |
|
|
supportedBandCombinationList-v1610 SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1610 { |
BandCombinationList-v1610 |
||
|
BandCombination-v1610 SEQUENCE { |
|||
|
bandList-v1610 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1610 { |
|||
|
ca-ParametersNR-v1610 |
Checked |
CA-ParametersNR-v1610 (Table 8.1.5.1.1.3.3-8 |
|
|
ca-ParametersNRDC-v1610 |
Not checked |
CA-ParametersNRDC-v1610 |
|
|
powerClass-v1610 |
Not checked |
||
|
powerClassNRPart-r16 |
Not checked |
||
|
featureSetCombinationDAPS-r16 |
Not checked |
FeatureSetCombinationId |
|
|
mrdc-Parameters-v1620 |
Not checked |
MRDC-Parameters-v1620 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
supportedBandCombinationListSidelinkEUTRA-NR-r16 |
Not checked |
BandCombinationListSidelinkEUTRA-NR-r16 |
|
|
supportedBandCombinationList-UplinkTxSwitch-r16 |
Not checked |
BandCombinationList-UplinkTxSwitch-r16 |
|
|
supportedBandCombinationList-v1630 |
Not checked |
BandCombinationList-v1630 |
|
|
supportedBandCombinationListSidelinkEUTRA-NR-v1630 |
Not checked |
BandCombinationListSidelinkEUTRA-NR-v1630 |
|
|
supportedBandCombinationList-UplinkTxSwitch-v1630 |
Not checked |
BandCombinationList-UplinkTxSwitch-v1630 |
|
|
supportedBandCombinationList-v1640 |
Not checked |
BandCombinationList-v1640 |
|
|
supportedBandCombinationList-UplinkTxSwitch-v1640 |
Not checked |
BandCombinationList-UplinkTxSwitch-v1640 |
|
|
supportedBandCombinationList-v1650 |
Not checked |
BandCombinationList-v1650 |
|
|
supportedBandCombinationList-UplinkTxSwitch-v1650 |
Not checked |
BandCombinationList-UplinkTxSwitch-v1650 |
|
|
extendedBand-n77-r16 |
Not checked |
||
|
} |
|||
|
measAndMobParameters SEQUENCE { |
|||
|
measAndMobParametersCommon SEQUENCE { |
|||
|
supportedGapPattern |
Not checked |
||
|
ssb-RLM |
supported |
||
|
ssb-AndCSI-RS-RLM |
Not checked |
||
|
eventB-MeasAndReport |
Checked |
pc_eventB_MeasAndReport |
|
|
handoverFDD-TDD |
Not checked |
||
|
eutra-CGI-Reporting |
Checked |
pc_eutra_CGI_Reporting |
|
|
nr-CGI-Reporting |
Checked |
pc_nr_CGI_Reporting |
|
|
independentGapConfig |
Checked |
pc_independentGapConfig |
|
|
periodicEUTRA-MeasAndReport |
Checked |
pc_periodicEUTRA_MeasAndReport |
|
|
handoverFR1-FR2 |
Not checked |
||
|
maxNumberCSI-RS-RRM-RS-SINR |
Not checked |
||
|
nr-CGI-Reporting-ENDC |
Not checked |
||
|
eutra-CGI-Reporting-NEDC |
Not checked |
||
|
eutra-CGI-Reporting-NRDC |
Not checked |
||
|
nr-CGI-Reporting-NEDC |
Not checked |
||
|
nr-CGI-Reporting-NRDC |
Not checked |
||
|
reportAddNeighMeasForPeriodic-r16 |
Not checked |
||
|
condHandoverParametersCommon-r16 |
Not checked |
||
|
nr-NeedForGap-Reporting-r16 |
Not checked |
||
|
supportedGapPattern-NRonly-r16 |
Not checked |
||
|
supportedGapPattern-NRonly-NEDC-r16 |
Not checked |
||
|
maxNumberCLI-RSSI-r16 |
Not checked |
||
|
maxNumberCLI-SRS-RSRP-r16 |
Not checked |
||
|
maxNumberPerSlotCLI-SRS-RSRP-r16 |
Not checked |
||
|
mfbi-IAB-r16 |
Not checked |
||
|
dummy |
Not checked |
||
|
nr-CGI-Reporting-NPN-r16 |
Checked |
pc_nr_CGI_Reporting_NPN_r16 |
|
|
idleInactiveEUTRA-MeasReport-r16 |
Not checked |
||
|
idleInactive-ValidityArea-r16 |
Not checked |
||
|
eutra-AutonomousGaps-r16 |
Not checked |
||
|
eutra-AutonomousGaps-NEDC-r16 |
Not checked |
||
|
eutra-AutonomousGaps-NRDC-r16 |
Not checked |
||
|
pcellT312-r16 |
Not checked |
||
|
supportedGapPattern-r16 |
Not checked |
||
|
} |
|||
|
measAndMobParametersXDD-Diff SEQUENCE { |
|||
|
intraAndInterF-MeasAndReport |
Checked (NOTE 1) |
pc_intraAndInterF-MeasAndReport |
|
|
eventA-MeasAndReport |
Checked (NOTE 2) |
pc_eventA_MeasAndReport |
|
|
handoverInterF |
Checked (NOTE 15) |
pc_ handoverInterF |
|
|
handoverLTE-EPC |
Not checked |
||
|
handoverLTE-5GC |
Not checked |
||
|
sftd-MeasNR-Neigh |
Checked (NOTE 13) |
pc_SFTD_MeasNR_Neigh_FDD and/or pc_SFTD_MeasNR_Neigh_TDD |
|
|
sftd-MeasNR-Neigh-DRX |
Not checked |
||
|
dummy |
Not checked |
||
|
} |
|||
|
measAndMobParametersFRX-Diff SEQUENCE { |
|||
|
ss-SINR-Meas |
Checked (NOTE 10) |
pc_ss_SINR_Meas |
|
|
csi-RSRP-AndRSRQ-MeasWithSSB |
Checked (NOTE 3) |
pc_csi-RSRP-AndRSRQ-MeasWithSSB |
|
|
csi-RSRP-AndRSRQ-MeasWithoutSSB |
Checked (NOTE 11) |
pc_csi_RSRP_AndRSRQ_MeasWithoutSSB |
|
|
csi-SINR-Meas |
Not checked |
||
|
csi-RS-RLM |
Not checked |
||
|
handoverInterF |
Checked (NOTE 14) |
pc_ handoverInterF |
|
|
handoverLTE-EPC |
Not checked |
||
|
handoverLTE-5GC |
Not checked |
||
|
maxNumberResource-CSI-RS-RLM |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology |
Not checked |
||
|
nr-AutonomousGaps-r16 |
Not checked |
||
|
nr-AutonomousGaps-ENDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NEDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NRDC-r16 |
Not checked |
||
|
dummy |
Not checked |
||
|
cli-RSSI-Meas-r16 |
Not checked |
||
|
cli-SRS-RSRP-Meas-r16 |
Not checked |
||
|
interFrequencyMeas-NoGap-r16 |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology-Inter-r16 |
Not checked |
||
|
idleInactiveNR-MeasReport-r16 |
Not checked |
||
|
idleInactiveNR-MeasBeamReport-r16 |
Not checked |
||
|
increasedNumberofCSIRSPerMO-r16 |
Not checked |
||
|
} |
|||
|
} |
|||
|
fdd-Add-UE-NR-Capabilities SEQUENCE { |
|||
|
phy-ParametersXDD-Diff SEQUENCE { |
|||
|
dynamicSFI |
Not checked |
||
|
twoPUCCH-F0-2-ConsecSymbols |
Not checked |
||
|
twoDifferentTPC-Loop-PUSCH |
Not checked |
||
|
twoDifferentTPC-Loop-PUCCH |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeA |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeB |
Not checked |
||
|
ul-SchedulingOffset |
Not checked |
||
|
} |
|||
|
mac-ParametersXDD-Diff SEQUENCE { |
|||
|
skipUplinkTxDynamic |
Checked (NOTE 4) |
pc_skipUplinkTxDynamic |
|
|
logicalChannelSR-DelayTimer |
Checked (NOTE 5) |
pc_logicalChannelSR_DelayTimer |
|
|
longDRX-Cycle |
Checked (NOTE 6) |
pc_longDRX_Cycle |
|
|
shortDRX-Cycle |
Checked (NOTE 7) |
pc_shortDRX_Cycle |
|
|
multipleSR-Configurations |
Not checked |
||
|
multipleConfiguredGrants |
Checked (NOTE 12) |
pc_multipleConfiguredGrants_r16 |
|
|
} |
|||
|
measAndMobParametersXDD-Diff SEQUENCE { |
|||
|
intraAndInterF-MeasAndReport |
Checked (NOTE 1) |
pc_intraAndInterF-MeasAndReport |
|
|
eventA-MeasAndReport |
Checked (NOTE 2) |
pc_eventA_MeasAndReport |
|
|
handoverInterF |
Checked (NOTE 15) |
pc_ handoverInterF |
|
|
handoverLTE-EPC |
Not checked |
||
|
handoverLTE-5GC |
Not checked |
||
|
sftd-MeasNR-Neigh |
Checked (NOTE 13) |
pc_SFTD_MeasNR_Neigh_FDD and/or pc_SFTD_MeasNR_Neigh_TDD |
|
|
sftd-MeasNR-Neigh-DRX |
Not checked |
||
|
dummy |
Not checked |
||
|
} |
|||
|
} |
|||
|
tdd-Add-UE-NR-Capabilities SEQUENCE { |
|||
|
phy-ParametersXDD-Diff SEQUENCE { |
|||
|
dynamicSFI |
Not checked |
||
|
twoPUCCH-F0-2-ConsecSymbols |
Not checked |
||
|
twoDifferentTPC-Loop-PUSCH |
Not checked |
||
|
twoDifferentTPC-Loop-PUCCH |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeA |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeB |
Not checked |
||
|
ul-SchedulingOffset |
Not checked |
||
|
} |
|||
|
mac-ParametersXDD-Diff SEQUENCE { |
|||
|
skipUplinkTxDynamic |
Checked (NOTE 4) |
pc_skipUplinkTxDynamic |
|
|
logicalChannelSR-DelayTimer |
Checked (NOTE 5) |
pc_logicalChannelSR_DelayTimer |
|
|
longDRX-Cycle |
Checked (NOTE 6) |
pc_longDRX_Cycle |
|
|
shortDRX-Cycle |
Checked (NOTE 7) |
pc_shortDRX_Cycle |
|
|
multipleSR-Configurations |
Not checked |
||
|
multipleConfiguredGrants |
Checked (NOTE 12) |
pc_multipleConfiguredGrants_r16 |
|
|
} |
|||
|
measAndMobParametersXDD-Diff SEQUENCE { |
|||
|
intraAndInterF-MeasAndReport |
Checked (NOTE 1) |
pc_intraAndInterF-MeasAndReport |
|
|
eventA-MeasAndReport |
Checked (NOTE 2) |
pc_eventA_MeasAndReport |
|
|
handoverInterF |
Checked (NOTE 15) |
pc_ handoverInterF |
|
|
handoverLTE-EPC |
Not checked |
||
|
handoverLTE-5GC |
Not checked |
||
|
sftd-MeasNR-Neigh |
Checked (NOTE 13) |
pc_SFTD_MeasNR_Neigh_FDD and/or pc_SFTD_MeasNR_Neigh_TDD |
|
|
sftd-MeasNR-Neigh-DRX |
Not checked |
||
|
dummy |
Not checked |
||
|
} |
|||
|
fr1-Add-UE-NR-Capabilities SEQUENCE { |
|||
|
phy-ParametersFRX-Diff SEQUENCE { |
|||
|
dynamicSFI |
Not checked |
||
|
dummy1 |
Not checked |
||
|
twoFL-DMRS |
Not checked |
||
|
dummy2 |
Not checked |
||
|
dummy3 |
Not checked |
||
|
supportedDMRS-TypeDL |
Not checked |
||
|
supportedDMRS-TypeUL |
Not checked |
||
|
semiOpenLoopCSI |
Not checked |
||
|
csi-ReportWithoutPMI |
Not checked |
||
|
csi-ReportWithoutCQI |
Not checked |
||
|
onePortsPTRS |
Not checked |
||
|
twoPUCCH-F0-2-ConsecSymbols |
Not checked |
||
|
pucch-F2-WithFH |
Not checked |
||
|
pucch-F3-WithFH |
Not checked |
||
|
pucch-F4-WithFH |
Not checked |
||
|
freqHoppingPUCCH-F0-2 |
Not checked |
||
|
freqHoppingPUCCH-F1-3-4 |
Not checked |
||
|
mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot |
Not checked |
||
|
uci-CodeBlockSegmentation |
Not checked |
||
|
onePUCCH-LongAndShortFormat |
Not checked |
||
|
twoPUCCH-AnyOthersInSlot |
Not checked |
||
|
intraSlotFreqHopping-PUSCH |
Not checked |
||
|
pusch-LBRM |
Not checked |
||
|
pdcch-BlindDetectionCA |
Not checked |
||
|
tpc-PUSCH-RNTI |
Not checked |
||
|
tpc-PUCCH-RNTI |
Not checked |
||
|
tpc-SRS-RNTI |
Not checked |
||
|
absoluteTPC-Command |
Not checked |
||
|
twoDifferentTPC-Loop-PUSCH |
Not checked |
||
|
twoDifferentTPC-Loop-PUCCH |
Not checked |
||
|
pusch-HalfPi-BPSK |
Not checked |
||
|
pucch-F3-4-HalfPi-BPSK |
Not checked |
||
|
almostContiguousCP-OFDM-UL |
Not checked |
||
|
sp-CSI-RS |
Not checked |
||
|
sp-CSI-IM |
Not checked |
||
|
tdd-MultiDL-UL-SwitchPerSlot |
Not checked |
||
|
multipleCORESET |
Not checked |
||
|
csi-RS-IM-ReceptionForFeedback |
Not checked |
||
|
csi-RS-ProcFrameworkForSRS |
Not checked |
||
|
csi-ReportFramework |
Not checked |
||
|
mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot SEQUENCE { |
|||
|
sameSymbol |
Not checked |
||
|
diffSymbol |
Not checked |
||
|
} |
|||
|
mux-SR-HARQ-ACK-PUCCH |
Not checked |
||
|
mux-MultipleGroupCtrlCH-Overlap |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeA |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeB |
Not checked |
||
|
ul-SchedulingOffset |
Not checked |
||
|
dl-64QAM-MCS-TableAlt |
Not checked |
||
|
ul-64QAM-MCS-TableAlt |
Not checked |
||
|
cqi-TableAlt |
Not checked |
||
|
oneFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
twoFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
oneFL-DMRS-ThreeAdditionalDMRS-UL |
Not checked |
||
|
} |
|||
|
measAndMobParametersFRX-Diff SEQUENCE { |
|||
|
ss-SINR-Meas |
Checked (NOTE 10) |
pc_ss_SINR_Meas |
|
|
csi-RSRP-AndRSRQ-MeasWithSSB |
Checked (NOTE 3) |
pc_csi-RSRP-AndRSRQ-MeasWithSSB |
|
|
csi-RSRP-AndRSRQ-MeasWithoutSSB |
Checked (NOTE 11) |
pc_csi_RSRP_AndRSRQ_MeasWithoutSSB |
|
|
csi-SINR-Meas |
Not checked |
||
|
csi-RS-RLM |
Not checked |
||
|
handoverInterF |
Checked (NOTE 14) |
pc_ handoverInterF |
|
|
handoverLTE-EPC |
Not checked |
||
|
handoverLTE-5GC |
Not checked |
||
|
maxNumberResource-CSI-RS-RLM |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology |
Not checked |
||
|
nr-AutonomousGaps-r16 |
Not checked |
||
|
nr-AutonomousGaps-ENDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NEDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NRDC-r16 |
Not checked |
||
|
dummy |
Not checked |
||
|
cli-RSSI-Meas-r16 |
Not checked |
||
|
cli-SRS-RSRP-Meas-r16 |
Not checked |
||
|
interFrequencyMeas-NoGap-r16 |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology-Inter-r16 |
Not checked |
||
|
idleInactiveNR-MeasReport-r16 |
Not checked |
||
|
idleInactiveNR-MeasBeamReport-r16 |
Not checked |
||
|
increasedNumberofCSIRSPerMO-r16 |
Not checked |
||
|
} |
|||
|
} |
|||
|
fr2-Add-UE-NR-Capabilities SEQUENCE { |
|||
|
phy-ParametersFRX-Diff SEQUENCE { |
Not checked |
||
|
dynamicSFI |
Not checked |
||
|
dummy1 |
Not checked |
||
|
twoFL-DMRS |
Not checked |
||
|
dummy2 |
Not checked |
||
|
dummy3 |
Not checked |
||
|
supportedDMRS-TypeDL |
Not checked |
||
|
supportedDMRS-TypeUL |
Not checked |
||
|
semiOpenLoopCSI |
Not checked |
||
|
csi-ReportWithoutPMI |
Not checked |
||
|
csi-ReportWithoutCQI |
Not checked |
||
|
onePortsPTRS |
Not checked |
||
|
twoPUCCH-F0-2-ConsecSymbols |
Not checked |
||
|
pucch-F2-WithFH |
Not checked |
||
|
pucch-F3-WithFH |
Not checked |
||
|
pucch-F4-WithFH |
Not checked |
||
|
freqHoppingPUCCH-F0-2 |
Not checked |
||
|
freqHoppingPUCCH-F1-3-4 |
Not checked |
||
|
mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot |
Not checked |
||
|
uci-CodeBlockSegmentation |
Not checked |
||
|
onePUCCH-LongAndShortFormat |
Not checked |
||
|
twoPUCCH-AnyOthersInSlot |
Not checked |
||
|
intraSlotFreqHopping-PUSCH |
Not checked |
||
|
pusch-LBRM |
Not checked |
||
|
pdcch-BlindDetectionCA |
Not checked |
||
|
tpc-PUSCH-RNTI |
Not checked |
||
|
tpc-PUCCH-RNTI |
Not checked |
||
|
tpc-SRS-RNTI |
Not checked |
||
|
absoluteTPC-Command |
Not checked |
||
|
twoDifferentTPC-Loop-PUSCH |
Not checked |
||
|
twoDifferentTPC-Loop-PUCCH |
Not checked |
||
|
pusch-HalfPi-BPSK |
Not checked |
||
|
pucch-F3-4-HalfPi-BPSK |
Not checked |
||
|
almostContiguousCP-OFDM-UL |
Not checked |
||
|
sp-CSI-RS |
Not checked |
||
|
sp-CSI-IM |
Not checked |
||
|
tdd-MultiDL-UL-SwitchPerSlot |
Not checked |
||
|
multipleCORESET |
Not checked |
||
|
csi-RS-IM-ReceptionForFeedback |
Not checked |
||
|
csi-RS-ProcFrameworkForSRS |
Not checked |
||
|
csi-ReportFramework |
Not checked |
||
|
mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot SEQUENCE { |
|||
|
sameSymbol |
Not checked |
||
|
diffSymbol |
Not checked |
||
|
} |
|||
|
mux-SR-HARQ-ACK-PUCCH |
Not checked |
||
|
mux-MultipleGroupCtrlCH-Overlap |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeA |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeB |
Not checked |
||
|
ul-SchedulingOffset |
Not checked |
||
|
dl-64QAM-MCS-TableAlt |
Not checked |
||
|
ul-64QAM-MCS-TableAlt |
Not checked |
||
|
cqi-TableAlt |
Not checked |
||
|
oneFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
twoFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
oneFL-DMRS-ThreeAdditionalDMRS-UL |
Not checked |
||
|
} |
|||
|
measAndMobParametersFRX-Diff SEQUENCE { |
|||
|
ss-SINR-Meas |
Checked (NOTE 10) |
pc_ss_SINR_Meas |
|
|
csi-RSRP-AndRSRQ-MeasWithSSB |
Checked (NOTE 3) |
pc_csi-RSRP-AndRSRQ-MeasWithSSB |
|
|
csi-RSRP-AndRSRQ-MeasWithoutSSB |
Checked (NOTE 11) |
pc_csi_RSRP_AndRSRQ_MeasWithoutSSB |
|
|
csi-SINR-Meas |
Not checked |
||
|
csi-RS-RLM |
Not checked |
||
|
handoverInterF |
Checked (NOTE 14) |
pc_ handoverInterF |
|
|
handoverLTE-EPC |
Not checked |
||
|
handoverLTE-5GC |
Not checked |
||
|
maxNumberResource-CSI-RS-RLM |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology |
Not checked |
||
|
nr-AutonomousGaps-r16 |
Not checked |
||
|
nr-AutonomousGaps-ENDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NEDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NRDC-r16 |
Not checked |
||
|
dummy |
Not checked |
||
|
cli-RSSI-Meas-r16 |
Not checked |
||
|
cli-SRS-RSRP-Meas-r16 |
Not checked |
||
|
interFrequencyMeas-NoGap-r16 |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology-Inter-r16 |
Not checked |
||
|
idleInactiveNR-MeasReport-r16 |
Not checked |
||
|
idleInactiveNR-MeasBeamReport-r16 |
Not checked |
||
|
increasedNumberofCSIRSPerMO-r16 |
Not checked |
||
|
} |
|||
|
} |
|||
|
featureSets SEQUENCE { |
|||
|
featureSetsDownlink SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink { |
|||
|
FeatureSetDownlink SEQUENCE { |
Not checked |
||
|
featureSetListPerDownlinkCC |
Not checked |
||
|
intraBandFreqSeparationDL |
Not checked |
||
|
scalingFactor |
Not checked |
||
|
crossCarrierScheduling-OtherSCS |
Not checked |
||
|
scellWithoutSSB |
Not checked |
||
|
csi-RS-MeasSCellWithoutSSB |
Not checked |
||
|
dummy1 |
Not checked |
||
|
type1-3-CSS |
Not checked |
||
|
pdcch-MonitoringAnyOccasions |
Not checked |
||
|
dummy2 |
Not checked |
||
|
ue-SpecificUL-DL-Assignment |
Not checked |
||
|
searchSpaceSharingCA-DL |
Not checked |
||
|
timeDurationForQCL SEQUENCE { |
|||
|
scs-60kHz |
Not checked |
||
|
scs-120kHz |
Not checked |
||
|
} |
|||
|
pdsch-ProcessingType1-DifferentTB-PerSlot SEQUENCE { |
|||
|
scs-15kHz |
Not checked |
||
|
scs-30kHz |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
scs-120kHz |
Not checked |
||
|
} |
|||
|
dummy3 |
Not checked |
||
|
dummy4 |
Not checked |
||
|
dummy5 |
Not checked |
||
|
dummy6 |
Not checked |
||
|
dummy7 |
Not checked |
||
|
} |
|||
|
} |
|||
|
featureSetsDownlinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC { |
|||
|
FeatureSetDownlinkPerCCSEQUENCE { |
|||
|
supportedSubcarreirSpacingDL |
Not checked |
SubcarrierSpacing |
|
|
supportedBandwidthDL |
Not checked |
SupportedBandwidth |
|
|
channelBW-90mhz |
Not checked |
||
|
maxNumberMIMO-LayersPDSCH |
Not checked |
MIMO-LayersDL |
|
|
supportedModulationOrderDL |
Not checked |
ModulationOrder |
|
|
} |
|||
|
} |
|||
|
featureSetsUplink SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink { |
|||
|
FeatureSetUplink SEQUENCE { |
|||
|
featureSetListPerUplinkCC |
Not checked |
||
|
scalingFactor |
Not checked |
||
|
crossCarrierScheduling-OtherSCS |
Not checked |
||
|
intraBandFreqSeparationUL |
Not checked |
||
|
searchSpaceSharingCA-UL |
Not checked |
||
|
dummy1 |
Not checked |
||
|
supportedSRS-Resources |
Not checked |
SRS-Resources |
|
|
twoPUCCH-Group |
Not checked |
||
|
dynamicSwitchSUL |
Checked |
pc_dynamicSwitch_SUL |
|
|
simultaneousTxSUL-NonSUL |
Not checked |
||
|
pusch-ProcessingType1-DifferentTB-PerSlot SEQUENCE { |
|||
|
scs-15kHz |
Not checked |
||
|
scs-30kHz |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
scs-120kHz |
Not checked |
||
|
} |
|||
|
dummy2 |
Not checked |
||
|
} |
|||
|
} |
|||
|
featureSetsUplinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC { |
|||
|
FeatureSetUplinkPerCCSEQUENCE { |
|||
|
supportedSubcarrierSpacingUL |
Not checked |
SubcarrierSpacing |
|
|
supportedBandwidthUL |
Not checked |
SupportedBandwidth |
|
|
channelBW-90mHz |
Not checked |
||
|
mimo-CB-PUSCH SEQUENCE { |
|||
|
maxNumberMIMO-LayersCB-PUSCH |
Not checked |
||
|
maxNumberSRS-ResourcePerSet |
Not checked |
||
|
} |
|||
|
maxNumberMIMO-LayersNonCB-PUSCH |
Not checked |
||
|
supportedModulationOrderUL |
Not checked |
ModulationOrder |
|
|
} |
|||
|
} |
|||
|
featureSetsDownlink-v1540 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1540 { |
|||
|
FeatureSetDownlink-v1540 SEQUENCE { |
|||
|
oneFL-DMRS-TwoAdditionalDMRS-DL |
Not checked |
||
|
additionalDMRS-DL-Alt |
Not checked |
||
|
twoFL-DMRS-TwoAdditionalDMRS-DL |
Not checked |
||
|
oneFL-DMRS-ThreeAdditionalDMRS-DL |
Not checked |
||
|
pdcch-MonitoringAnyOccasionsWithSpanGap SEQUENCE { |
|||
|
scs-15kHz |
Not checked |
||
|
scs-30kHz |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
scs-120kHz |
Not checked |
||
|
} |
|||
|
pdsch-SeparationWithGap |
Not checked |
||
|
pdsch-ProcessingType2 SEQUENCE { |
|||
|
scs-15kHz |
Not checked |
||
|
scs-30kHz |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
} |
|||
|
pdsch-ProcessingType2-Limited SEQUENCE { |
|||
|
differentTB-PerSlot-SCS-30kHz |
Not checked |
||
|
} |
|||
|
dl-MCS-TableAlt-DynamicIndication |
Not checked |
||
|
} |
|||
|
} |
|||
|
featureSetsUplink-v1540 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1540 { |
|||
|
FeatureSetUplink-v1540 SEQUENCE { |
|||
|
zeroSlotOffsetAperiodicSRS |
Not checked |
||
|
pa-PhaseDiscontinuityImpacts |
Not checked |
||
|
pusch-SeparationWithGap |
Not checked |
||
|
pusch-ProcessingType2 SEQUENCE { |
|||
|
scs-15kHz |
Not checked |
||
|
scs-30kHz |
Not checked |
||
|
scs-60kHz |
Not checked |
||
|
} |
|||
|
ul-MCS-TableAlt-DynamicIndication |
Not checked |
||
|
} |
|||
|
} |
|||
|
featureSetsUplinkPerCC-v1540 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1540 { |
|||
|
FeatureSetUplinkPerCC-v1540 SEQUENCE { |
|||
|
mimo-NonCB-PUSCH SEQUENCE { |
|||
|
maxNumberSRS-ResourcePerSet |
Not checked |
||
|
maxNumberSimultaneousSRS-ResourceTx |
Not checked |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
featureSetsDownlink-v15a0 SEQUENCE (SIZE (1.. maxDownlinkFeatureSets)) OF FeatureSetDownlink-v15a0 |
Not checked |
FeatureSetDownlink-v15a0 |
|
|
featureSetsDownlink-v1610 SEQUENCE (SIZE (1.. maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1610 |
Checked |
FeatureSetDownlink-v1610 (Table 8.1.5.1.1.3.3-6) |
|
|
featureSetsUplink-v1610 SEQUENCE (SIZE (1.. maxUplinkFeatureSets)) OF FeatureSetUplink-v1610 |
Checked |
FeatureSetUplink-v1610 (Table 8.1.5.1.1.3.3-7) |
|
|
featureSetDownlinkPerCC-v1620 SEQUENCE (SIZE (1.. maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1620 |
Not checked |
FeatureSetDownlinkPerCC-v1620 |
|
|
featureSetsUplink-v1630 SEQUENCE (SIZE (1.. maxUplinkFeatureSets)) OF FeatureSetUplink-v1630 |
Not checked |
FeatureSetUplink-v1630 |
|
|
featureSetsUplink-v1640 SEQUENCE (SIZE (1.. maxUplinkFeatureSets)) OF FeatureSetUplink-v1640 |
Not checked |
FeatureSetUplink-v1640 |
|
|
featureSetCombinations SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OF FeatureSetCombination { |
|||
|
FeatureSetCombination SEQUENCE (SIZE (1..maxSimultaneousBands)) OF FeatureSetsPerBand { |
|||
|
FeatureSetsPerBand SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSet { |
|||
|
FeatureSetCHOICE { |
|||
|
eutra SEQUENCE { |
|||
|
downlinkSetEUTRA |
Not checked |
FeatureSetEUTRA-DownlinkId |
|
|
uplinkSetEUTRA |
Not checked |
FeatureSetEUTRA-UplinkId |
|
|
} |
|||
|
nr SEQUENCE { |
|||
|
downlinkSetNR |
Not checked |
FeatureSetDownlinkId |
|
|
uplinkSetNR |
Not checked |
FeatureSetUpinkId |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
lateNonCriticalExtension |
Not checked |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
fdd-Add-UE-NR-Capabilities-v1530 SEQUENCE { |
|||
|
eutra-ParametersXDD-Diff SEQUENCE { |
|||
|
rsrqMeasWidebandEUTRA |
Not checked |
||
|
} |
|||
|
} |
|||
|
tdd-Add-UE-NR-Capabilities-v1530 SEQUENCE { |
|||
|
eutra-ParametersXDD-Diff SEQUENCE { |
|||
|
rsrqMeasWidebandEUTRA |
Not checked |
||
|
} |
|||
|
} |
|||
|
dummy |
Not checked |
||
|
interRAT-Parameters SEQUENCE { |
|||
|
eutra SEQUENCE { |
|||
|
supportedBandListEUTRA SEQUENCE (SIZE (1..maxBandsEUTRA)) OF FreqBandIndicatorEUTRA |
Not checked |
||
|
eutra-ParametersCommon SEQUENCE { |
|||
|
mfbi-EUTRA |
Not checked |
||
|
modifiedMRP-BehaviorEUTRA |
Not checked |
||
|
multiNS-Pmax-EUTRA |
Not checked |
||
|
rs-SINR-MeasEUTRA |
Checked |
pc_RS_SINR_MeasEUTRA |
|
|
ne-DC |
Not checked |
||
|
nr-HO-ToEN-DC-r16 |
Checked |
pc_interRAT_NR_ToENDC |
|
|
} |
|||
|
eutra-ParametersXDD-Diff SEQUENCE { |
|||
|
rsrqMeasWidebandEUTRA |
Not checked |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
inactiveState |
Checked |
pc_inactiveState |
|
|
delayBudgetReporting |
Not checked |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
sdap-Parameters SEQUENCE { |
|||
|
as-ReflectiveQoS |
Checked |
pc_as_ReflectiveQoS |
|
|
} |
|||
|
overheatingInd |
Not checked |
||
|
ims-Parameters SEQUENCE { |
|||
|
ims-ParametersCommon SEQUENCE { |
|||
|
voiceOverEUTRA-5GC |
Not checked |
||
|
voiceOverSCG-BearerEUTRA-5GC |
Not checked |
||
|
voiceFallbackIndicationEPS-r16 |
Checked |
pc_voiceFallbackIndication |
|
|
} |
|||
|
ims-ParametersFRX-Diff SEQUENCE { |
|||
|
voiceOverNR |
Checked (NOTE 16) |
pc_voiceOverNR |
|
|
} |
|||
|
} |
|||
|
fr1-Add-UE-NR-Capabilities-v1540 SEQUENCE { |
|||
|
ims-ParametersFRX-Diff SEQUENCE { |
|||
|
voiceOverNR |
Checked (NOTE 16) |
pc_voiceOverNR |
|
|
} |
|||
|
} |
|||
|
fr2-Add-UE-NR-Capabilities-v1540 SEQUENCE { |
|||
|
ims-ParametersFRX-Diff SEQUENCE { |
|||
|
voiceOverNR |
Checked (NOTE 16) |
pc_voiceOverNR |
|
|
} |
|||
|
} |
|||
|
fr1-fr2-Add-UE-NR-Capabilities SEQUENCE { |
|||
|
phy-ParametersFRX-Diff SEQUENCE { |
|||
|
dynamicSFI |
Not checked |
||
|
dummy1 |
Not checked |
||
|
twoFL-DMRS |
Not checked |
||
|
dummy2 |
Not checked |
||
|
dummy3 |
Not checked |
||
|
supportedDMRS-TypeDL |
Not checked |
||
|
supportedDMRS-TypeUL |
Not checked |
||
|
semiOpenLoopCSI |
Not checked |
||
|
csi-ReportWithoutPMI |
Not checked |
||
|
csi-ReportWithoutCQI |
Not checked |
||
|
onePortsPTRS |
Not checked |
||
|
twoPUCCH-F0-2-ConsecSymbols |
Not checked |
||
|
pucch-F2-WithFH |
Not checked |
||
|
pucch-F3-WithFH |
Not checked |
||
|
pucch-F4-WithFH |
Not checked |
||
|
freqHoppingPUCCH-F0-2 |
Not checked |
||
|
freqHoppingPUCCH-F1-3-4 |
Not checked |
||
|
mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot |
Not checked |
||
|
uci-CodeBlockSegmentation |
Not checked |
||
|
onePUCCH-LongAndShortFormat |
Not checked |
||
|
twoPUCCH-AnyOthersInSlot |
Not checked |
||
|
intraSlotFreqHopping-PUSCH |
Not checked |
||
|
pusch-LBRM |
Not checked |
||
|
pdcch-BlindDetectionCA |
Not checked |
||
|
tpc-PUSCH-RNTI |
Not checked |
||
|
tpc-PUCCH-RNTI |
Not checked |
||
|
tpc-SRS-RNTI |
Not checked |
||
|
absoluteTPC-Command |
Not checked |
||
|
twoDifferentTPC-Loop-PUSCH |
Not checked |
||
|
twoDifferentTPC-Loop-PUCCH |
Not checked |
||
|
pusch-HalfPi-BPSK |
Not checked |
||
|
pucch-F3-4-HalfPi-BPSK |
Not checked |
||
|
almostContiguousCP-OFDM-UL |
Not checked |
||
|
sp-CSI-RS |
Not checked |
||
|
sp-CSI-IM |
Not checked |
||
|
tdd-MultiDL-UL-SwitchPerSlot |
Not checked |
||
|
multipleCORESET |
Not checked |
||
|
csi-RS-IM-ReceptionForFeedback |
Not checked |
CSI-RS-IM-ReceptionForFeedback |
|
|
csi-RS-ProcFrameworkForSRS |
Not checked |
CSI-RS-ProcFrameworkForSRS |
|
|
csi-ReportFramework |
Not checked |
CSI-ReportFramework |
|
|
mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot SEQUENCE { |
|||
|
sameSymbol |
Not checked |
||
|
diffSymbol |
Not checked |
||
|
} |
|||
|
mux-SR-HARQ-ACK-PUCCH |
Not checked |
||
|
mux-MultipleGroupCtrlCH-Overlap |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeA |
Not checked |
||
|
dl-SchedulingOffset-PDSCH-TypeB |
Not checked |
||
|
ul-SchedulingOffset |
Not checked |
||
|
dl-64QAM-MCS-TableAlt |
Not checked |
||
|
ul-64QAM-MCS-TableAlt |
Not checked |
||
|
cqi-TableAlt |
Not checked |
||
|
oneFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
twoFL-DMRS-TwoAdditionalDMRS-UL |
Not checked |
||
|
oneFL-DMRS-ThreeAdditionalDMRS-UL |
Not checked |
||
|
} |
|||
|
measAndMobParametersFRX-Diff SEQUENCE { |
|||
|
ss-SINR-Meas |
Checked (NOTE 10) |
pc_ss_SINR_Meas |
|
|
csi-RSRP-AndRSRQ-MeasWithSSB |
Checked (NOTE 3) |
pc_csi-RSRP-AndRSRQ-MeasWithSSB |
|
|
csi-RSRP-AndRSRQ-MeasWithoutSSB |
Checked (NOTE 11) |
pc_csi_RSRP_AndRSRQ_MeasWithoutSSB |
|
|
csi-SINR-Meas |
Not checked |
||
|
csi-RS-RLM |
Not checked |
||
|
handoverInterF |
Checked (NOTE 14) |
pc_ handoverInterF |
|
|
handoverLTE-EPC |
Not checked |
||
|
handoverLTE-5GC |
Not checked |
||
|
maxNumberResource-CSI-RS-RLM |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology |
Not checked |
||
|
nr-AutonomousGaps-r16 |
Not checked |
||
|
nr-AutonomousGaps-ENDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NEDC-r16 |
Not checked |
||
|
nr-AutonomousGaps-NRDC-r16 |
Not checked |
||
|
dummy |
Not checked |
||
|
cli-RSSI-Meas-r16 |
Not checked |
||
|
cli-SRS-RSRP-Meas-r16 |
Not checked |
||
|
interFrequencyMeas-NoGap-r16 |
Not checked |
||
|
simultaneousRxDataSSB-DiffNumerology-Inter-r16 |
Not checked |
||
|
idleInactiveNR-MeasReport-r16 |
Not checked |
||
|
idleInactiveNR-MeasBeamReport-r16 |
Not checked |
||
|
increasedNumberofCSIRSPerMO-r16 |
Not checked |
||
|
} |
|||
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
UE-NR-Capability-v1550 |
||
|
reducedCP-Latency |
Checked |
pc_reducedCP_Latency |
|
|
nonCriticalExtension SEQUENCE { |
UE-NR-Capability-v1560 |
||
|
nrdc-Parameters |
Not checked |
NRDC-Parameters |
|
|
receivedFilters |
Not checked |
||
|
nonCriticalExtension SEQUENCE { |
UE-NR-Capability-v1570 |
||
|
nrdc-Parameters-v1570 |
Not checked |
NRDC-Parameters-v1570 |
|
|
nonCriticalExtension SEQUENCE { |
UE-NR-Capability-v1610 |
||
|
inDeviceCoexInd-r16 |
Not checked |
||
|
dl-DedicatedMessageSegmentation-r16 |
Not checked |
||
|
nrdc-Parameters-v1610 |
Not checked |
||
|
powSav-Parameters-r16 |
Checked |
PowSav-Parameters-r16 (Table 8.1.5.1.1.3.3-9) |
|
|
fr1-Add-UE-NR-Capabilities-v1610 |
Not checked |
||
|
fr2-Add-UE-NR-Capabilities-v1610 |
Not checked |
||
|
bh-RLF-Indication-r16 |
Not checked |
||
|
directSN-AdditionFirstRRC-IAB-r16 |
Not checked |
||
|
bap-Parameters-r16 |
Not checked |
||
|
referenceTimeProvision-r16 |
Not checked |
||
|
sidelinkParameters-r16 SEQUENCE { |
|||
|
sidelinkParametersNR-r16 { |
|||
|
rlc-ParametersSidelink-r16 |
Not checked |
||
|
mac-ParametersSidelink-r16 |
Not checked |
||
|
fdd-Add-UE-Sidelink-Capabilities-r16 |
Not checked |
||
|
tdd-Add-UE-Sidelink-Capabilities-r16 |
Not checked |
||
|
supportedBandListSidelink-r16 SEQUENCE (SIZE (1..maxBands)) OF BandSidelink-r16 { |
|||
|
freqBandSidelink-r16 |
Not checked |
||
|
sl-Reception-r16 |
Not checked |
||
|
sl-TransmissionMode1-r16 |
Not checked |
||
|
sync-Sidelink-r16 |
Not checked |
||
|
sl-Tx-256QAM-r16 |
Not checked |
||
|
psfch-FormatZeroSidelink-r16 |
Not checked |
||
|
lowSE-64QAM-MCS-TableSidelink-r16 |
Not checked |
||
|
enb-sync-Sidelink-r16 |
Not checked |
||
|
sl-TransmissionMode2-r16 |
Checked |
38.306, 4.2.16.1.6: Support of this feature is mandatory if UE supports NR sidelink |
pc_NR_sl_TransmissionMode2_r16 |
|
congestionControlSidelink-r16 |
Not checked |
||
|
fewerSymbolSlotSidelink-r16 |
Not checked |
||
|
sl-openLoopPC-RSRP-ReportSidelink-r16 |
Not checked |
||
|
sl-Rx-256QAM-r16 |
Not checked |
||
|
} |
|||
|
} |
|||
|
sidelinkParametersEUTRA-r16 |
Not checked |
||
|
} |
|||
|
highSpeedParameters-r16 |
Not checked |
||
|
mac-Parameters-v1610 |
Not checked |
||
|
mcgRLF-RecoveryViaSCG-r16 |
Not checked |
||
|
resumeWithStoredMCG-SCells-r16 |
Not checked |
||
|
resumeWithStoredSCG-r16 |
Not checked |
||
|
resumeWithSCG-Config-r16 |
Not checked |
||
|
ue-BasedPerfMeas-Parameters-r16 |
Checked |
UE-BasedPerfMeas-Parameters-r16 (Table 8.1.5.1.1.3.3-10) |
|
|
son-Parameters-r16 { |
|||
|
rach-Report-r16 |
Checked |
pc_rachReport_r16 |
|
|
} |
|||
|
onDemandSIB-Connected-r16 |
Not checked |
||
|
nonCriticalExtension SEQUENCE {} |
Not checked |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
nonCriticalExtension SEQUENCE {} |
Not checked |
||
|
} |
|||
|
} |
|||
|
Note 1: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and intraAndInterF-MeasAndReport is supported in both modes, then support of intraAndInterF-MeasAndReport will be signaled in measAndMobParameters/measAndMobParametersXDD-Diff. Note 2: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and eventA-MeasAndReport is supported in both modes, then support of eventA-MeasAndReport will be signaled in measAndMobParameters/measAndMobParametersXDD-Diff. Note 3: If the UE supports single frequency range (FR1 or FR2), or the UE supports both frequency ranges (FR1 and FR2) and csi-RSRP-AndRSRQ-MeasWithSSB is supported in both frequency ranges, then support of csi-RSRP-AndRSRQ-MeasWithSSB will be signaled in measAndMobParameters/MeasAndMobParametersFRX-Diff. Note 4: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and skipUplinkTxDynamic is supported in both modes, then support of skipUplinkTxDynamic will be signaled in mac-Parameters/mac-ParametersXDD-Diff. Note 5: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and logicalChannelSR-DelayTimer is supported in both modes, then support of logicalChannelSR-DelayTimer will be signaled in mac-Parameters/mac-ParametersXDD-Diff. Note 6: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and longDRX_Cycle is supported in both modes, then support of longDRX_Cycle will be signaled in mac-Parameters/mac-ParametersXDD-Diff. Note 7: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and shortDRX_Cycle is supported in both modes, then support of shortDRX_Cycle will be signaled in mac-Parameters/mac-ParametersXDD-Diff. Note 8: If the UE supports FR2 and pc_pdsch_256QAM_FR2 is supported, then support of pdsch_256QAM_FR2 will be signaled in at least one entry of supportedBandListNR as appropriate. Note 9: If pc_pusch_256QAM_FR1 or pc_pusch_256QAM_FR2 is supported, then support of pusch-256QAM will be signaled in at least one entry of supportedBandListNR as appropriate. Note 10: If the UE supports single frequency range (FR1 or FR2), or the UE supports both frequency ranges (FR1 and FR2) and ss-SINR-Meas is supported in both frequency ranges, then support of ss-SINR-Meas will be signaled in measAndMobParameters/MeasAndMobParametersFRX-Diff. Note 11: If the UE supports single frequency range (FR1 or FR2), or the UE supports both frequency ranges (FR1 and FR2) and csi-RSRP-AndRSRQ-MeasWithoutSSB is supported in both frequency ranges, then support of csi-RSRP-AndRSRQ-MeasWithoutSSB will be signaled in measAndMobParameters/MeasAndMobParametersFRX-Diff. Note 12: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and multipleConfiguredGrants is supported in both modes, then support of multipleConfiguredGrants will be signaled in mac-Parameters/mac-ParametersXDD-Diff. Note 13: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and sftd-MeasNR-Neigh is supported in both modes, then support of sftd-MeasNR-Neigh will be signaled in measAndMobParameters/measAndMobParametersXDD-Diff. Note 14: If the UE supports single frequency range (FR1 or FR2), or the UE supports both frequency ranges (FR1 and FR2) and handoverInterF is supported in both frequency ranges, then support of handoverInterF will be signaled in measAndMobParameters/MeasAndMobParametersFRX-Diff. Note 15: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and handoverInterF is supported in both modes, then support of handoverInterF will be signaled in measAndMobParameters/measAndMobParametersXDD-Diff. Note 16: If the UE supports single frequency range (FR1 or FR2), or the UE supports both frequency ranges (FR1 and FR2) and voiceOverNR is supported in both frequency ranges, then support of voiceOverNR will be signaled in ims-Parameters/ims-ParametersFRX-Diff. |
|||
Table 8.1.5.1.1.3.3-4: UECapabilityEnquiry-v1560-IEs (Table 8.1.5.1.1.3.3-1)
|
Information Element |
Value/remark |
Comment |
Condition |
|
UECapabilityEnquiry-v1560-IEs ::= SEQUENCE { |
|||
|
capabilityRequestFilterCommon |
Not present |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
rrc-SegAllowed-r16 |
enabled |
||
|
nonCriticalExtension |
Not present |
||
|
} |
|||
|
} |
Table 8.1.5.1.1.3.3-5: ULDedicatedMessageSegment (step 2a1, Table 8.1.5.1.1.3.2-1)
|
Derivation Path: 38.508-1 [4], Table 4.6.1-32C |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ULDedicatedMessageSegment-r16 ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
segmentNumber-r16 |
0 for first segment, and incremented by 1 for each subsequent segment |
||
|
rrc-MessageSegmentContainer-r16 |
Not Checked |
OCTET STRING including segmented UECapabilityInformation message |
|
|
rrc-MessageSegmentType-r16 |
notLastSegment for all segments except the last segment. lastSegment for the last segment |
||
|
lateNonCriticalExtension |
Not present |
||
|
nonCriticalExtension |
Not present |
||
|
} |
|||
|
} |
|||
Table 8.1.5.1.1.3.3-6: FeatureSetDownlink-v1610 (Table 8.1.5.1.1.3.3-3)
|
Information Element |
Value/remark |
Comment |
Condition |
|
FeatureSetDownlink-v1610 ::= SEQUENCE { |
|||
|
cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16 |
Not checked |
||
|
cbgPDSCH-ProcessingType2-DifferentTB-PerSlot-r16 |
Not checked |
||
|
intraFreqDAPS-r16 |
Checked |
pc_intraFreqDAPS_r16 |
|
|
intraBandFreqSeparationDL-v1620 |
Not checked |
||
|
intraBandFreqSeparationDL-Only-r16 |
Not checked |
||
|
pdcch-Monitoring-r16 |
Not checked |
||
|
pdcch-MonitoringMixed-r16 |
Not checked |
||
|
crossCarrierSchedulingProcessing-DiffSCS-r16 |
Not checked |
||
|
singleDCI-SDM-scheme-r16 |
Not checked |
||
|
} |
Table 8.1.5.1.1.3.3-7: FeatureSetUplink-v1610 (Table 8.1.5.1.1.3.3-3)
|
Information Element |
Value/remark |
Comment |
Condition |
|
FeatureSetUplink-v1610 ::= SEQUENCE { |
|||
|
pusch-RepetitionTypeB-r16 |
Checked |
pc_pusch_RepetitionTypeB_r16 |
|
|
ul-CancellationSelfCarrier-r16 |
Not checked |
||
|
ul-CancellationCrossCarrier-r16 |
Not checked |
||
|
ul-FullPwrMode2-MaxSRS-ResInSet-r16 |
Not checked |
||
|
cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16 |
Not checked |
||
|
cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16 |
Not checked |
||
|
supportedSRS-PosResources-r16 |
Not checked |
||
|
intraFreqDAPS-UL-r16 |
Not checked |
||
|
intraBandFreqSeparationUL-v1620 |
Not checked |
||
|
multiPUCCH-r16 |
Not checked |
||
|
twoPUCCH-Type1-r16 |
Not checked |
||
|
twoPUCCH-Type2-r16 |
Not checked |
||
|
twoPUCCH-Type3-r16 |
Not checked |
||
|
twoPUCCH-Type4-r16 |
Not checked |
||
|
mux-SR-HARQ-ACK-r16 |
Not checked |
||
|
dummy1 |
Not checked |
||
|
dummy2 |
Not checked |
||
|
twoPUCCH-Type5-r16 |
Not checked |
||
|
twoPUCCH-Type6-r16 |
Not checked |
||
|
twoPUCCH-Type7-r16 |
Not checked |
||
|
twoPUCCH-Type8-r16 |
Not checked |
||
|
twoPUCCH-Type9-r16 |
Not checked |
||
|
twoPUCCH-Type10-r16 |
Not checked |
||
|
twoPUCCH-Type11-r16 |
Not checked |
||
|
ul-IntraUE-Mux-r16 |
Not checked |
||
|
ul-FullPwrMode-r16 |
Not checked |
||
|
crossCarrierSchedulingProcessing-DiffSCS-r16 |
Not checked |
||
|
ul-FullPwrMode1-r16 |
Not checked |
||
|
ul-FullPwrMode2-SRSConfig-diffNumSRSPorts-r16 |
Not checked |
||
|
ul-FullPwrMode2-TPMIGroup-r16 |
Not checked |
||
|
} |
Table 8.1.5.1.1.3.3-8: CA-ParametersNR-v1610 (Table 8.1.5.1.1.3.3-3)
|
Information Element |
Value/remark |
Comment |
Condition |
|
CA-ParametersNR-v1610 ::= SEQUENCE { |
|||
|
parallelTxMsgA-SRS-PUCCH-PUSCH-r16 |
Not checked |
||
|
msgA-SUL-r16 |
Not checked |
||
|
jointSearchSpaceSwitchAcrossCells-r16 |
Not checked |
||
|
half-DuplexTDD-CA-SameSCS-r16 |
Not checked |
||
|
scellDormancyWithinActiveTime-r16 |
Not checked |
||
|
scellDormancyOutsideActiveTime-r16 |
Checked |
pc_scellDormancyOutsideActiveTime_r16 |
|
|
crossCarrierA-CSI-trigDiffSCS-r16 |
Not checked |
||
|
defaultQCL-CrossCarrierA-CSI-Trig-r16 |
Not checked |
||
|
interCA-NonAlignedFrame-r16 |
Not checked |
||
|
simul-SRS-Trans-BC-r16 |
Not checked |
||
|
interFreqDAPS-r16 |
Checked |
pc_interFreqDAPS_r16 |
|
|
codebookParametersPerBC-r16 |
Not checked |
||
|
blindDetectFactor-r16 |
Not checked |
||
|
pdcch-MonitoringCA-r16 |
Not checked |
||
|
pdcch-BlindDetectionCA-Mixed-r16 |
Not checked |
||
|
pdcch-BlindDetectionMCG-UE-r16 |
Not checked |
||
|
pdcch-BlindDetectionSCG-UE-r16 |
Not checked |
||
|
pdcch-BlindDetectionMCG-UE-Mixed-r16 |
Not checked |
||
|
pdcch-BlindDetectionSCG-UE-Mixed-r16 |
Not checked |
||
|
crossCarrierSchedulingDL-DiffSCS-r16 |
Not checked |
||
|
crossCarrierSchedulingDefaultQCL-r16 |
Not checked |
||
|
crossCarrierSchedulingUL-DiffSCS-r16 |
Not checked |
||
|
simul-SRS-MIMO-Trans-BC-r16 |
Not checked |
||
|
codebookParametersAdditionPerBC-r16 |
Not checked |
||
|
codebookComboParametersAdditionPerBC-r16 |
Not checked |
||
|
} |
Table 8.1.5.1.1.3.3-9: PowSav-Parameters-r16 (Table 8.1.5.1.1.3.3-3)
|
Information Element |
Value/remark |
Comment |
Condition |
|
PowSav-Parameters-r16 ::= SEQUENCE { |
|||
|
powSav-ParametersCommon-r16 SEQUENCE { |
|||
|
drx-Preference-r16 |
Not checked |
||
|
maxCC-Preference-r16 |
Not checked |
||
|
releasePreference-r16 |
Checked |
pc_releasePreference_r16 |
|
|
minSchedulingOffsetPreference-r16 |
Not checked |
||
|
} |
|||
|
powSav-ParametersFRX-Diff-r16 |
Not checked |
||
|
} |
Table 8.1.5.1.1.3.3-10: UE-BasedPerfMeas-Parameters-r16 (Table 8.1.5.1.1.3.3-3)
|
Information Element |
Value/remark |
Comment |
Condition |
|
UE-BasedPerfMeas-Parameters-r16 ::= SEQUENCE { |
|||
|
barometerMeasReport-r16 |
Checked |
pc_barometer_r16 |
|
|
immMeasBT-r16 |
Not checked |
||
|
immMeasWLAN-r16 |
Checked |
pc_immMeasWLAN_r16 |
|
|
loggedMeasBT-r16 |
Not checked |
||
|
loggedMeasurements-r16 |
Checked |
pc_loggedMeasurements_r16 |
|
|
loggedMeasWLAN-r16 |
Checked |
pc_loggedMeasWLAN_r16 |
|
|
orientationMeasReport-r16 |
Checked |
pc_orientation_r16 |
|
|
speedMeasReport-r16 |
Checked |
pc_speed_r16 |
|
|
gnss-Location-r16 |
Checked |
pc_GNSS_location_r16 |
|
|
ulPDCP-Delay-r16 |
Checked |
pc_PDCP_Delay_r16 |
|
|
} |
8.1.5.2 SI change / On-demand SIB
8.1.5.2.1 Void
8.1.5.2.2 SI change / Notification of BCCH modification / Short message for SI update in NR RRC_CONNECTED state
8.1.5.2.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a short message transmitted on PDCCH using P-RNTI indicating a systemInfoModification }
then { UE re-acquires the SIB1 }
}
8.1.5.2.2.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clause 5.2.2.2.2, 5.2.2.3.1, 5.2.2.4.2 and 6.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.2.2.2.2]
A modification period is used, i.e. updated SI (other than for ETWS and CMAS) is broadcasted in the modification period following the one where SI change indication is transmitted. The modification period boundaries are defined by SFN values for which SFN mod m= 0, where m is the number of radio frames comprising the modification period. The modification period is configured by system information. The UE receives indications about SI modifications and/or PWS notifications using Short Message transmitted with P-RNTI over DCI (see clause 6.5). Repetitions of SI change indication may occur within preceding modification period.
UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for SI change indication in its own paging occasion every DRX cycle. UEs in RRC_CONNECTED shall monitor for SI change indication in any paging occasion at least once per modification period if the UE is provided with common search space on the active BWP to monitor paging, as specified in TS 38.213 [13], clause 13.
…
If the UE receives a Short Message, the UE shall:
…
1> if the systemInfoModification bit of Short Message is set:
2> apply the SI acquisition procedure as defined in sub-clause 5.2.2.3 from the start of the next modification.
[TS 38.331, clause 5.2.2.3.1]
The UE shall:
1> apply the specified BCCH configuration defined in 9.1.1.1;
…
1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1 and pagingSearchSpace and has received an indication about change of system information; or
…
NOTE: The UE in RRC_CONNECTED 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.2.2.4.2]
Upon receiving the SIB1 the UE shall:
…
3> if the UE has a stored valid version of a SIB, in accordance with sub-clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with sub-clause 5.2.2.1:
4> use the stored version of the required SIB;
3> if the UE has not stored a valid version of a SIB, in accordance with sub-clause 5.2.2.2.1, of one or several required SIB(s), in accordance with sub-clause 5.2.2.1:
4> for the SI message(s) that, according to the si-SchedulingInfo, contain at least one required SIB and for which si-BroadcastStatus is set to broadcasting:
5> acquire the SI message(s) as defined in sub-clause 5.2.2.3.2;
[TS 38.331, clause 6.5]
Short messages can be transmitted on PDCCH using P-RNTI with or without associated Paging message using Short Message field in DCI format 1_0 (see TS 38.212 [17, 7.3.1.2.1]).
Table 6.5-1 defines Short Messages. Bit 1 is the most significant bit.
Table 6.5-1: Short messages
|
Bit |
Short message |
|
1 |
systemInfoModification If set to 1: indication of a BCCH modification other than SIB6, SIB7 and SIB8. |
|
2 |
etwsAndCmasIndication If set to 1: indication of an ETWS primary notification and/or an ETWS secondary notification and/or a CMAS notification. |
|
3 – [8] |
Not used in this release of the specification, and shall be ignored by UE if received. |
8.1.5.2.2.3 Test Description
8.1.5.2.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cell.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A and Test Loop Function (ON) with UE test loop mode B established according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3 with the exception that Short_DCI condition is applied in NR Serving cell configuration.
8.1.5.2.2.3.2 Test procedure sequence
Table 8.1.5.2.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends one IP Packet to the UE. |
– |
– |
– |
– |
|
1A |
The SS waits 0.5 second and then ignores scheduling requests and does not allocate any uplink grant. |
– |
– |
– |
– |
|
2 |
The SS changes the prach-ConfigurationIndex and ra-ResponseWindow in the system information. |
– |
– |
– |
– |
|
3 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
4 |
Void |
– |
– |
– |
– |
|
5 |
Check: Does the UE initiate a random access using prach-ConfigurationIndex given in step 3 to send pending Uplink data? |
– |
– |
1 |
P |
|
6 |
The SS transmits Random Access Response with RAPID corresponding to preamble in step 5. (Note 1) |
– |
– |
– |
– |
|
7 |
The UE loop backs the IP packets received in step 1 |
– |
– |
– |
– |
|
8 |
The SS starts the UL default grant transmissions. |
||||
|
Note 1: The resource allocation for Msg3 shall be enough to accommodate all of the DRB data that UE will loop back at step 7. To be more specific, resource allocation shall be no less than: TB size = IP packet (64 bytes) + SDAP header (1 bytes) + PDCP header (3 bytes) + RLC header (3 bytes) + MAC header (2 bytes) + padding or BSR (2 bytes) + C-RNTI MAC CE (3 Bytes) + PHR (3 bytes) = 81 bytes. |
|||||
8.1.5.2.2.3.3 Specific message contents
Table 8.1.5.2.2.3.3-1: CLOSE UE TEST LOOP (Preamble, Table 8.1.5.2.2.3.2-1)
|
Derivation Path: TS 36.508-1 [7] table 4.7A-3 condition UE test loop mode B |
||||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
|
UE test loop mode B LB setup |
||||
|
IP PDU delay |
‘0000 1111’B |
15 seconds |
||
Table 8.1.5.2.2.3.3-2: SIB1 (step 2, Table 8.1.5.2.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4] table 4.6.1-28 |
||||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
|
SIB1 ::= SEQUENCE { |
||||
|
servingCellConfigCommon SEQUENCE { |
||||
|
uplinkConfigCommon SEQUENCE { |
||||
|
initialUplinkBWP SEQUENCE { |
||||
|
rach-ConfigCommon SEQUENCE { |
||||
|
rach-ConfigGeneric SEQUENCE { |
||||
|
prach-ConfigurationIndex |
119 |
. |
FR1 FDD |
|
|
91 |
FR1 TDD |
|||
|
6 |
FR2 |
|||
|
ra-ResponseWindow |
sl20 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
8.1.5.3 PWS notification
8.1.5.3.1 PWS notification / PWS reception in NR RRC_IDLE state
8.1.5.3.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_IDLE state }
ensure that {
when { an ETWS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB6 }
then { the UE is able to retrieve the PWS message from SIB6 and alert the user }
}
(2)
with { UE in NR RRC_IDLE state }
ensure that {
when { an ETWS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB7 }
then { the UE is able to retrieve all the PWS message segments from SIB7, reassemble the message and alert the user }
}
(3)
with { UE in NR RRC_IDLE state }
ensure that {
when { a CMAS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB8 }
then { the UE is able to retrieve all the PWS message segments from SIB8, reassemble the message and alert the user }
}
8.1.5.3.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clause 5.2.2.2.2.
[TS 38.331 clause 5.2.2.2.2]
…
ETWS or CMAS capable UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for indications about PWS notification in its own paging occasion every DRX cycle. ETWS or CMAS capable UEs in RRC_CONNECTED shall monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle if the UE is provided with common search space on the active BWP to monitor paging.
For Short Message reception in a paging occasion, the UE monitors the PDCCH monitoring occasion(s) for paging as specified in TS 38.304 [20] and TS 38.213 [13].
If the UE receives a Short Message, the UE shall:
1> if the UE is ETWS capable or CMAS capable, the etwsAndCmasIndication bit of Short Message is set, and the UE is provided with searchSpaceOtherSystemInformation on the active BWP:
2> immediately re-acquire the SIB1;
2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB6:
3> acquire SIB6, as specified in sub-clause 5.2.2.3.2, immediately;
2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB7:
3> acquire SIB7, as specified in sub-clause 5.2.2.3.2, immediately;
2> if the UE is CMAS capable and si-SchedulingInfo includes scheduling information for SIB8:
3> acquire SIB8, as specified in sub-clause 5.2.2.3.2, immediately;
1> if the systemInfoModification bit of Short Message is set:
2> apply the SI acquisition procedure as defined in sub-clause 5.2.2.3 from the start of the next modification period.
8.1.5.3.1.3 Test description
8.1.5.3.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
UE:
– None.
Preamble:
– The UE is in test state 1N-A according to TS 38.508-1 [4].
8.1.5.3.1.3.2 Test procedure sequence
Table 8.1.5.3.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
– |
If pc_ETWS_NR is true, step1-8 will be excuted. |
– |
– |
– |
– |
|
1 |
The SS indicates an etwsAndCmasIndication by Short Message field in DCI format 1_0 and transmitted on PDCCH using P-RNTI. The SS starts transmitting SIB1 with the si-SchedulingInfo including scheduling information for SIB6 on NR Cell 1. |
<– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
2 |
The SS includes an ETWS message with new messageIdentifier and serialNumber in SIB6. (Note 1) |
– |
– |
– |
– |
|
3 |
Check: Does the UE alert or activate alerting the user (NOTE 2)? |
– |
– |
1 |
P |
|
4 |
The SS waits for 10s. |
– |
– |
– |
– |
|
5 |
The SS indicates an etwsAndCmasIndication by Short Message field in DCI format 1_0 and transmitted on PDCCH using P-RNTI. The SS starts transmitting SIB1 with the si-SchedulingInfo including scheduling information for SIB7 on NR Cell 1. |
<– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
6 |
The SS includes an ETWS message with new messageIdentifier and serialNumber in SIB7. (NOTE 3). |
– |
– |
– |
– |
|
7 |
Check: Does the UE indicate the contents of the "warning message" to the user, and alert or activate alerting the user (NOTE 2)? |
– |
– |
2 |
P |
|
8 |
The SS waits for 10s. |
– |
– |
– |
– |
|
– |
If pc_CMAS_NR is true, step9-11 will be excuted. |
– |
– |
– |
– |
|
9 |
The SS indicates an etwsAndCmasIndication by Short Message field in DCI format 1_0 and transmitted on PDCCH using P-RNTI. The SS starts transmitting SIB1 with the si-SchedulingInfo including scheduling information for SIB8 on NR Cell 1. |
<– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
10 |
The SS includes a CMAS message with new messageIdentifier and serialNumber in SIB8. (NOTE 4). |
– |
– |
– |
– |
|
11 |
Check: Does the UE indicate the contents of the "warning message" to the user, and alert or activate alerting the user (NOTE 2)? |
– |
– |
3 |
P |
|
NOTE 1: The NR-10 in Table 4.4.3.1.2-1 Combinations of system information blocks of TS 38.508-1 [4] is used. NOTE 2: The data indication and user alerting are the UE implementation issues. NOTE 3: The NR-11 in Table 4.4.3.1.2-1 Combinations of system information blocks of TS 38.508-1 [4] is used. NOTE 4: The NR-9 in Table 4.4.3.1.2-1 Combinations of system information blocks of TS 38.508-1 [4] is used. |
|||||
8.1.5.3.1.3.3 Specific message contents
None
8.1.5.3.2 PWS notification / PWS reception in NR RRC_INACTIVE state
8.1.5.3.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { an ETWS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB6 }
then { the UE is able to retrieve the PWS message from SIB6 and alert the user }
}
(2)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { an ETWS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB7 }
then { the UE is able to retrieve all the PWS message segments from SIB7, reassemble the message and alert the user }
}
(3)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { a CMAS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB8 }
then { the UE is able to retrieve all the PWS message segments from SIB8, reassemble the message and alert the user }
}
8.1.5.3.2.2 Conformance requirements
Same as test case 8.1.5.3.1.
8.1.5.3.2.3 Test description
8.1.5.3.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
UE:
None.
Preamble:
– The UE is in state Registered, Inactive mode (state 2N-A) according to TS 38.508-1 [4].
8.1.5.3.2.3.2 Test procedure sequence
Same as test case 8.1.5.3.1
8.1.5.3.2.3.3 Specific message contents
Same as test case 8.1.5.3.1.
8.1.5.3.3 PWS notification / PWS reception in NR RRC_CONNECTED state
8.1.5.3.3.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { an ETWS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB6 }
then { the UE is able to retrieve all the PWS message segments from SIB6, reassemble the message and alert the user }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { an ETWS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB7 }
then { the UE is able to retrieve all the PWS message segments from SIB7, reassemble the message and alert the user }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { a CMAS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB8 }
then { the UE is able to retrieve all the PWS message segments from SIB8, reassemble the message and alert the user }
}
8.1.5.3.3.2 Conformance requirements
Same as test case 8.1.5.3.1.
8.1.5.3.3.3 Test description
8.1.5.3.3.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
UE:
None.
Preamble:
– The UE is in test state 3N-A according to TS 38.508-1 [4].
8.1.5.3.3.3.2 Test procedure sequence
Same as test case 8.1.5.3.1 except PDCCH (DCI 1_0): Short Message is sent on active BWP.
8.1.5.3.3.3.3 Specific message contents
Same as test case 8.1.5.3.1.
8.1.5.3.4 PWS notification / PWS reception using dedicatedSystemInformationDelivery
8.1.5.3.4.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message including dedicatedSystemInformationDelivery containing SIB6 }
then { UE reads the SIB6 to alert the user and sends an RRCReconfigurationComplete message }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message including dedicatedSystemInformationDelivery containing SIB7 }
then { UE reads the SIB7 to alert the user and sends an RRCReconfigurationComplete message }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message including dedicatedSystemInformationDelivery containing SIB8 }
then { UE reads the SIB8 to alert the user and sends an RRCReconfigurationComplete message }
}
8.1.5.3.4.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.2.2.4.7, 5.2.2.4.8, 5.2.2.4.9, 5.3.5.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
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;
[TS 38.331, clause 5.2.2.4.7]
Upon receiving the SIB6 the UE shall:
1> forward the received warningType, messageIdentifier and serialNumber to upper layers;
[TS 38.331, clause 5.2.2.4.8]
Upon receiving the SIB7 the UE shall:
1> if there is no current value for messageIdentifier and serialNumber for SIB7; or
1> if either the received value of messageIdentifier or of serialNumber or of both are different from the current values of messageIdentifier and serialNumber for SIB7:
2> use the received values of messageIdentifier and serialNumber for SIB7 as the current values of messageIdentifier and serialNumber for SIB7;
2> discard any previously buffered warningMessageSegment;
2> if all segments of a warning message have been received:
3> assemble the warning message from the received warningMessageSegment;
3> forward the received warning message, messageIdentifier, serialNumber and dataCodingScheme to upper layers;
3> stop reception of SIB7;
3> discard the current values of messageIdentifier and serialNumber for SIB7;
2> else:
3> store the received warningMessageSegment;
3> continue reception of SIB7;
1> else if all segments of a warning message have been received:
2> assemble the warning message from the received warningMessageSegment;
2> forward the received complete warning message, messageIdentifier, serialNumber and dataCodingScheme to upper layers;
2> stop reception of SIB7;
2> discard the current values of messageIdentifier and serialNumber for SIB7;
1> else:
2> store the received warningMessageSegment;
2> continue reception of SIB7;
The UE should discard any stored warningMessageSegment and the current value of messageIdentifier and serialNumber for SIB7 if the complete warning message has not been assembled within a period of 3 hours.
[TS 38.331, clause 5.2.2.4.9]
Upon receiving the SIB8 the UE shall:
1> if the SIB8 contains a complete warning message and the complete geographical area coordinates (if any):
2> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and the geographical area coordinates (if any) to upper layers;
2> continue reception of SIB8;
1> else:
2> if the received values of messageIdentifier and serialNumber are the same (each value is the same) as a pair for which a warning message and the geographical area coordinates (if any) are currently being assembled:
3> store the received warningMessageSegment;
3> store the received warningAreaCoordinatesSegment (if any);
3> if all segments of a warning message and geographical area coordinates (if any) have been received:
4> assemble the warning message from the received warningMessageSegment;
4> assemble the geographical area coordinates from the received warningAreaCoordinatesSegment (if any);
4> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and geographical area coordinates (if any) to upper layers;
4> stop assembling a warning message and geographical area coordinates (if any) for this messageIdentifier and serialNumber and delete all stored information held for it;
3> continue reception of SIB8;
2> else if the received values of messageIdentifier and/or serialNumber are not the same as any of the pairs for which a warning message is currently being assembled:
3> start assembling a warning message for this messageIdentifier and serialNumber pair;
3> start assembling the geographical area coordinates (if any) for this messageIdentifier and serialNumber pair;
3> store the received warningMessageSegment;
3> store the received warningAreaCoordinatesSegment (if any);
3> continue reception of SIB8;
The UE should discard warningMessageSegment and warningAreaCoordinatesSegment (if any) and the associated values of messageIdentifier and serialNumber for SIB8 if the complete warning message and the geographical area coordinates (if any) have not been assembled within a period of 3 hours.
NOTE: The number of warning messages that a UE can re-assemble simultaneously is a function of UE implementation.
8.1.5.3.4.3 Test description
8.1.5.3.4.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
UE:
– None
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1
8.1.5.3.4.3.2 Test procedure sequence
Table 8.1.5.3.4.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
– |
If pc_ETWS_NR is true, steps 1-6 will be excuted. |
– |
– |
– |
– |
|
1 |
The SS transmits an RRCReconfiguration message containing dedicatedSystemInformationDelivery containing SIB6. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
2 |
Check: Does the UE transmit an RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
3 |
Check: Does the UE alert or activate alerting the user (NOTE 1)? |
– |
– |
1 |
P |
|
4 |
The SS transmits an RRCReconfiguration message containing dedicatedSystemInformationDelivery containing SIB7. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
5 |
Check: Does the UE transmit an RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
6 |
Check: Does the UE indicate the "warning message" to the user, and alert or activate alerting the user (NOTE 1)? |
– |
– |
2 |
P |
|
– |
If pc_CMAS_NR is true, steps 7-9 will be excuted. |
– |
– |
– |
– |
|
7 |
The SS transmits an RRCReconfiguration message containing dedicatedSystemInformationDelivery containing SIB8. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
8 |
Check: Does the UE transmit an RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
9 |
Check: Does the UE alert or activate alerting the user (NOTE 1)? |
– |
– |
3 |
P |
|
NOTE 1: The data indication and user alerting are the UE implementation issues. |
|||||
8.1.5.3.4.3.3 Specific message contents
Table 8.1.5.3.4.3.3-1: RRCReconfiguration (Steps 1, 4 and 7 Table 8.1.5.3.4.3.2-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 { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
Not present |
||
|
dedicatedNAS-MessageList |
Not present |
||
|
dedicatedSystemInformationDelivery |
SystemInformation |
OCTET STRING (CONTAINING SystemInformation) |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.3.4.3.3-2: SystemInformation (Steps 1, 4 and 7 Table 8.1.5.3.4.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-29 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformation ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
systemInformation-r15 SEQUENCE { |
|||
|
sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
1 entry |
||
|
sib6 |
SIB6 |
Acc to 38.508-1 [4] Table 4.6.2-5: SIB6 |
Step 1 |
|
sib7 |
SIB7 |
Step 4 |
|
|
sib8 |
SIB8 |
Step 7 |
|
|
} |
|||
|
lateNonCriticalExtension |
Not present |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.3.4.3.3-3: SIB7 (Step 4 in Table 8.1.5.3.4.3.2-1)
|
Derivation Path: TS 38.331 [6], clause 6.3.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB7 ::= SEQUENCE { |
|||
|
messageIdentifier |
‘0001 0001 0000 0010’B |
ETWS message identifier for earthquake and tsunami message (see TS 23.041 [25]) |
|
|
serialNumber |
‘0011 0000 0000 0000’B |
Note 1. |
|
|
warningMessageSegmentType |
lastSegment |
||
|
warningMessageSegmentNumber |
0 |
||
|
warningMessageSegment |
Octetstring of N |
Containing the complete ETWS message |
|
|
dataCodingScheme |
Bitstring (8) ID of the alphabet/coding and the applied language |
see TS 23.041 [25]. |
|
|
lateNonCriticalExtension |
Not present |
||
|
} |
|||
|
Note 1: Geographical Scope (Octet 1 bit 7 ~ 6) set to ‘Cell wide’, Emergency User Alert (Octet 1 bit 5) set to ‘Activate emergency user alert’, Popup (Octet 1 bit 4) set to ‘Activate popup’, Update Number (Octet 2 bits 3~0) for each update, incremented by one, See TS 23.041 [25]. |
|||
Table 8.1.5.3.4.3.3-4: SIB8 (Step 7 in Table 8.1.5.3.4.3.2-1)
|
Derivation Path: TS 38.331 [6], clause 6.3.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB8 ::= SEQUENCE { |
|||
|
messageIdentifier |
‘0001 0001 0001 0010’B |
CMAS CBS Message Identifier for CMAS Presidential Level Alerts (see TS 23.041 [25]) |
|
|
serialNumber |
‘0011 0000 0000 0000’B |
Note 1 |
|
|
warningMessageSegmentType |
lastSegment |
||
|
warningMessageSegmentNumber |
0 |
||
|
warningMessageSegment |
Octetstring of N |
||
|
dataCodingScheme |
Bitstring (8) ID of the alphabet/coding and the applied language |
Containing the complete CMAS message |
|
|
warningAreaCoordinatesSegment |
Not present |
||
|
lateNonCriticalExtension |
Not present |
||
|
} |
|||
|
Note 1: Geographical Scope (Octet 1 bit 7 ~ 6) set to ‘Cell wide’, Emergency User Alert (Octet 1 bit 5) set to ‘Activate emergency user alert’, Popup (Octet 1 bit 4) set to ‘Activate popup’, Update Number (Octet 2 bits 3~0) for each update, incremented by one, See TS 23.041 [25]. |
|||
8.1.5.4 Counter check
8.1.5.4.1 Counter check / Reception of CounterCheck message by the UE
8.1.5.4.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state with two DRBs established and having received 10 data packets on each DRB }
ensure that {
when { UE receives CounterCheck message with drb-CountMSB-InfoList included for DRB3(not established) and DRB1 (with the most significant bits of the count different from the actual COUNT)}
then { UE sends CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT – 1 and RX_NEXT – 1 in drb-CountInfoList IE for each DRB established, and by including the drb-Identity, the count-Uplink and the count-Downlink with the most significant bits set identical to the corresponding values in the drb-CountMSB-InfoList and the least significant bits set to zero for the DRB that is not established }
}
8.1.5.4.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.6.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.6.3]
Upon receiving the CounterCheck message, the UE shall:
1> for each DRB that is established:
2> if no COUNT exists for a given direction (uplink or downlink) because it is a uni-directional bearer configured only for the other direction:
3> assume the COUNT value to be 0 for the unused direction;
2> if the drb-Identity is not included in the drb-CountMSB-InfoList:
3> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT – 1 and RX_NEXT – 1 (specified in TS 38.323 [5]), respectively;
2> else if, for at least one direction, the most significant bits of the COUNT are different from the value indicated in the drb-CountMSB-InfoList:
3> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT – 1 and RX_NEXT – 1 (specified in TS 38.323 [5]), respectively;
1> for each DRB that is included in the drb-CountMSB-InfoList in the CounterCheck message that is not established:
2> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink with the most significant bits set identical to the corresponding values in the drb-CountMSB-InfoList and the least significant bits set to zero;
1> submit the CounterCheckResponse message to lower layers for transmission upon which the procedure ends.
8.1.5.4.1.3 Test description
8.1.5.4.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in the NR cell.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A on NR Cell 1 with atleast one PDU session active according to TS 38.508-1 [4], clause 4.4A.3 Table 4.4A.3-1 and Test Loop Function (On) with UE test loop mode B is established. 2 DRBs are configured where DRB1 is defined as default DRB.
8.1.5.4.1.3.2 Test procedure sequence
Table 8.1.5.4.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits 10 IP packets on each DRB (using QFI2 for DRB1 and QFI5 for DRB2) |
– |
– |
– |
– |
|
2 |
The UE loops back the IP packets received in step 1 (Note 1) |
– |
– |
– |
– |
|
3 |
The SS transmits CounterCheck message with drb-Identity not included in the drb-CountMSB-InfoList |
<– |
NR RRC: CounterCheck |
– |
– |
|
4 |
Check: Does the UE send CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT – 1 and RX_NEXT – 1 in drb-CountInfoList IE for each DRB established? |
–> |
NR RRC: CounterCheckResponse |
1 |
P |
|
Note 1: IP packets at step 2 may be received by the SS in the same slot or in multiple slots |
|||||
8.1.5.4.1.3.3 Specific message contents
Table 8.1.5.4.1.3.3-1: RRCReconfiguration (Preamble, Table 8.1.5.4.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 with condition NR |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
radioBearerConfig |
RadioBearerConfig-2DRBs |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup |
CellGroupConfig-2DRBs |
OCTET STRING (CONTAINING CellGroupConfig) |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.4.1.3.3-2: RadioBearerConfig-2DRBs (Preamble, Table 8.1.5.4.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition SRB2 and DRB1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
2 entries |
||
|
DRB-ToAddMod[1] SEQUENCE { |
entry 1 |
||
|
cnAssociation CHOICE { |
|||
|
sdap-Config::= SEQUENCE { |
|||
|
pdu-Session |
PDU session ID |
Same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST |
|
|
defaultDRB |
true |
||
|
mappedQoS-FlowsToAdd SEQUENCE { |
|||
|
QFI |
2 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
drb-Identity |
DRB-Identity with Condition DRB1 |
||
|
} |
|||
|
} |
|||
|
DRB-ToAddMod[2] SEQUENCE |
entry 2 |
||
|
cnAssociation CHOICE { |
|||
|
sdap-Config SEQUENCE { |
|||
|
pdu-Session |
PDU session ID |
Same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST |
|
|
defaultDRB |
false |
||
|
mappedQoS-FlowsToAdd SEQUENCE { |
|||
|
QFI |
5 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
drb-Identity |
DRB-Identity with Condition DRB2 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.4.1.3.3-3: CellGroupConfig-2DRBs (Preamble, Table 8.1.5.4.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4], table 4.6.3-19 and condition SRB2_DRB1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig { |
3 entries |
||
|
RLC-BearerConfig[1] |
RLC-BearerConfig with condition SRB2 |
entry 1 |
|
|
RLC-BearerConfig[2] |
RLC-BearerConfig with conditions AM and DRB1 |
entry 2 |
|
|
RLC-BearerConfig[3] |
RLC-BearerConfig with conditions AM and DRB2 |
entry 3 |
|
|
} |
|||
|
} |
|||
Table 8.1.5.4.1.3.3-4: PDU SESSION ESTABLISHMENT ACCEPT (Preamble) (Table 8.1.5.4.1.3.2-1)
|
Derivation Path: TS 38.508-1, table 4.7.2-2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDU session ID |
The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST |
||
|
Authorized QoS rules |
3 entries |
||
|
QoS rule [1] |
Reference QoS rule #1 as defined in Table 4.8.2.1-1. |
QFI=1 |
|
|
QoS rule [2] |
Reference QoS rule #4 as defined in Table 4.8.2.1-4 except DQR bit set to ‘0’B. |
QFI=2 |
|
|
QoS rule [3] |
Reference QoS rule #5 as defined in Table 4.8.2.1-5. |
QFI=5 |
|
|
Mapped EPS Bearer contexts |
Not Present |
||
|
Authorized QoS flow descriptions |
3 entries |
||
|
QoS flow [1] |
Reference QoS flow #1 as defined in Table8.1.5.4.1.3.3-7. |
QFI=1 |
|
|
QoS flow [2] |
Reference QoS flow #2 as defined in Table8.1.5.4.1.3.3-8. |
QFI=2 |
|
|
QoS flow [3] |
Reference QoS flow #3 as defined in Table 4.8.2.3-3. |
QFI=5 |
|
Table 8.1.5.4.1.3.3-5: CounterCheck (step 3, Table 8.1.5.4.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] table 4.6.1-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
CounterCheck ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
counterCheck SEQUENCE { |
|||
|
drb-CountMSB-InfoList SEQUENCE (SIZE (1..maxDRB)) OF DRB-CountMSB-Info { |
2 entries |
||
|
DRB-CountMSB-Info[1] SEQUENCE { |
entry 1 |
||
|
drb-Identity |
DRB-Identity with Condition DRB1 |
DRB established |
|
|
countMSB-Uplink |
1 |
||
|
countMSB-Downlink |
1 |
||
|
} |
|||
|
DRB-CountMSB-Info[2] SEQUENCE { |
entry 2 |
||
|
drb-Identity |
DRB-Identity with Condition DRB3 |
DRB not established |
|
|
countMSB-Uplink |
3 |
||
|
countMSB-Downlink |
3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.4.1.3.3-6: CounterCheckResponse (step 4, Table 8.1.5.4.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] table 4.6.1-2 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
CounterCheckResponse ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
counterCheckResponse SEQUENCE { |
|||
|
drb-CountInfoList SEQUENCE (SIZE (0..maxDRB)) OF DRB-CountInfo { |
3 entries |
||
|
DRB-CountInfo[1] SEQUENCE { |
entry 1 |
||
|
drb-Identity |
DRB-Identity with Condition DRB1 |
DRB established |
|
|
count-Uplink |
9 |
||
|
count-Downlink |
9 |
||
|
} |
|||
|
DRB-CountInfo[2] SEQUENCE { |
entry 2 |
||
|
drb-Identity |
DRB-Identity with Condition DRB2 |
DRB established but not requested |
|
|
count-Uplink |
9 |
||
|
count-Downlink |
9 |
||
|
} |
|||
|
DRB-CountInfo[3] SEQUENCE { |
entry 3 |
||
|
drb-Identity |
DRB-Identity with Condition DRB3 |
DRB not established |
|
|
count-Uplink] |
384 |
MSB 3 and LSB 0 |
|
|
count-Downlink |
384 |
MSB 3 and LSB 0 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.4.1.3.3-7: Reference QoS flow #1 (Preamble)
|
Derivation Path: TS 38.508-1, table 4.8.2.3-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QFI |
‘00 0001’B |
QFI 1 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
5QI |
‘0000 1001’B |
5QI 9 |
|
Table 8.1.5.4.1.3.3-8: Reference QoS flow #2 (Preamble)
|
Derivation Path: TS 38.508-1, table 4.8.2.3-2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
QoS flow descriptions |
|||
|
QoS flow description |
|||
|
QFI |
‘00 0010’B |
QFI 2 |
|
|
Operation code |
‘001’B |
Create new QoS flow description |
|
|
E bit |
‘1’B |
Parameters list is included |
|
|
Number of parameters |
’00 0001’B |
1 parameter |
|
|
5QI |
‘0000 0101’B |
5QI 5 |
|
8.1.5.5 Redirection to NR
8.1.5.5.1 Redirection to NR / From E-UTRA / Success
8.1.5.5.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including a redirectedCarrierInfo for redirection to an NR cell }
then { UE enters E-UTRA RRC_IDLE state and performs redirection to NR cell }
}
8.1.5.5.1.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 36.331 clause 5.3.8.3. Unless otherwise stated these are Rel-15 requirements.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> except for NB-IoT, BL UEs or UEs in CE, delay the following actions defined in this sub-clause 60 ms from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;
1> for BL UEs or UEs in CE, delay the following actions defined in this sub-clause 1.25 seconds from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;
1> for NB-IoT, delay the following actions defined in this sub-clause 10 seconds from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier.
NOTE: For BL UEs, UEs in CE and NB-IoT, when STATUS reporting, as defined in TS 36.322 [7], has not been triggered and the UE has sent positive HARQ feedback (ACK), as defined in TS 36.321 [6], the lower layers can be considered to have indicated that the receipt of the RRCConnectionRelease message has been successfully acknowledged.
1> stop T380, if running;
1> if T309 is running:
2> stop timer T309 for all access categories;
2> perform the actions as specified in 5.3.16.4.
1> if the RRCConnectionRelease message is received in response to an RRCConnectionResumeRequest for EDT:
2> indicate to upper layers that the suspended RRC connection has been resumed;
2> discard the stored UE AS context and resumeIdentity;
2> stop timer T300;
2> stop timer T302, if running;
2> stop timer T303, if running;
2> stop timer T305, if running;
2> stop timer T306, if running;
2> stop timer T308, if running;
2> perform the actions as specified in 5.3.3.7;
2> stop timer T320, if running;
2> stop timer T322, if running;
1> if the security is not activated and if UE is connected to 5GC:
2> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12 with the release cause ‘other’ upon which the procedure ends;
1> if the RRCConnectionRelease message includes redirectedCarrierInfo indicating redirection to geran; or
1> if the RRCConnectionRelease message includes idleModeMobilityControlInfo including freqPriorityListGERAN:
2> if AS security has not been activated; and
2> if upper layers indicate that redirect to GERAN without AS security is not allowed:
3> ignore the content of the RRCConnectionRelease;
3> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12, with release cause ‘other’, upon which the procedure ends;
1> if AS security has not been activated:
2> ignore the content of redirectedCarrierInfo, if included and indicating redirection to nr;
2> ignore the content of idleModeMobilityControlInfo, if included and including freqPriorityListNR;
2> if the UE ignores the content of redirectedCarrierInfo or of idleModeMobilityControlInfo:
3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’, upon which the procedure ends;
1> if the RRCConnectionRelease message includes redirectedCarrierInfo indicating redirection to eutra and if UE is connected to 5GC:
2> if cn-Type is included:
3> after the cell selection, indicate the available CN Type(s) and the received cn-Type to upper layers;
NOTE 1: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cn-Type, is up to UE implementation.
1> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
2> store the cell reselection priority information provided by the idleModeMobilityControlInfo;
2> if the t320 is included:
3> start timer T320, with the timer value set according to the value of t320;
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the RRCConnectionRelease message includes the measIdleConfig:
2> clear VarMeasIdleConfig and VarMeasIdleReport;
2> store the received measIdleDuration in VarMeasIdleConfig;
2> start T331 with the value of measIdleDuration;
2> if the measIdleConfig contains measIdleCarrierListEUTRA:
3> store the received measIdleCarrierListEUTRA in VarMeasIdleConfig;
3> start performing idle mode measurements as specified in 5.6.20;
NOTE 2: If the measIdleConfig does not contain measIdleCarrierListEUTRA, UE may receive measIdleCarrierListEUTRA as specified in 5.2.2.12.
1> for NB-IoT, if the RRCConnectionRelease message includes the redirectedCarrierInfo:
2> if the redirectedCarrierOffsetDedicated is included in the redirectedCarrierInfo:
3> store the dedicated offset for the frequency in redirectedCarrierInfo;
3> start timer T322, with the timer value set according to the value of T322 in redirectedCarrierInfo;
1> if the releaseCause received in the RRCConnectionRelease message indicates loadBalancingTAURequired:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘load balancing TAU required’;
1> else if the releaseCause received in the RRCConnectionRelease message indicates cs-FallbackHighPriority:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘CS Fallback High Priority’;
1> else:
2> if the waitTime is present:
3> start timer T302, with the timer value set according to the waitTime;
3> inform the upper layer that access barring is applicable for all access categories except categories ‘0’ and ‘2’;
2> if the extendedWaitTime is present; and
2> if the UE supports delay tolerant access or the UE is a NB-IoT UE:
3> forward the extendedWaitTime to upper layers;
2> if the extendedWaitTime-CPdata is present and the NB-IoT UE only supports the Control Plane CIoT EPS optimisation:
3> forward the extendedWaitTime-CPdata to upper layers;
2> if the releaseCause received in the RRCConnectionRelease message indicates rrc-Suspend:
3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC suspension’;
2> else if rrc-InactiveConfig is included:
3> perform the actions upon entering RRC_INACTIVE as specified in 5.3.8.7;
2> else:
3> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12, with release cause ‘other’;
8.1.5.5.1.3 Test Description
8.1.5.5.1.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 is the serving cell and NR Cell 1 is the suitable neighbour cell.
– System information combination 31 as defined in TS 36.508 [7] clause 4.4.3.1 is used in the E-UTRA cell.
– System information combination NR-6 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in the NR cell.
UE:
– In E-UTRA RRC_CONNECTED state using generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On)in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.4.
Preamble:
– With NR Cell 1 "Serving cell" and E-UTRA Cell 1 "Non-suitable "Off" cell", the UE is brought to state 1N-A, RRC_IDLE Connectivity (NR), in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.2.2-2. 5G-GUTI and ngKSI are assigned and security context established.
– the UE is switched-off
– With E-UTRA Cell 1 and NR Cell 1 power levels set according to T0, the UE is brought to state Generic RB Established (state 3) according to TS 36.508 [7] clause 4.5.3. 4G GUTI and eKSI are assigned and security context established
8.1.5.5.1.3.2 Test procedure sequence
Tables 8.1.5.5.1.3.2-0/ 8.1.5.5.1.3.2-0A illustrates the downlink power levels to be applied for NR Cell 1, E-UTRA Cell 1 for the test execution.
Table 8.1.5.5.1.3.2-0: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
E-UTRA Cell 1 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
The power levels are such that reselection to NR Cell 1 does not happen. |
|
|
SS/PBCH SSS EPRE |
dBm/SCS |
-91 |
– |
Table 8.1.5.5.1.3.2-0A: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
E-UTRA Cell 1 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
The power levels are such that reselection to NR Cell 1 does not happen. |
|
|
SS/PBCH SSS EPRE |
dBm/SCS |
-94 |
– |
Table 8.1.5.5.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message indicating redirection to NR Cell 1. |
– |
E-UTRA RRC: RRCConnectionRelease |
– |
– |
|
2-14a1 |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.9 indicate that the UE has performed mobility registration updating when it camps on NR Cell 1? |
– |
– |
1 |
P |
8.1.5.5.1.3.3 Specific message contents
Table 8.1.5.5.1.3.3-1: RRCConnectionRelease (step 1, Table 8.1.5.5.1.3.2-1)
|
Derivation Path: TS 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo CHOICE { |
|||
|
nr-r15 SEQUENCE { |
|||
|
carrierFreq-r15 |
ARFCN of NR Cell 1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.5.6 Radio link failure
8.1.5.6.1 Radio link failure / RRC connection re-establishment success
8.1.5.6.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE detecting physical layer recovery while T310 was running }
then { UE resumes the RRC connection without explicit signalling }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE detecting physical layer problems }
then { UE shall start timer T310 and UE does not initiate any RRC connection re-establishment procedure before expiring of timer T310 }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE detecting radio link failure on expiring of timer T310 }
then { UE starts timer T311 and UE initiates the RRC connection re-establishment procedure }
}
(4)
with { UE having initiated RRC connection re-establishment procedure and timer T311 running }
ensure that {
when { UE successfully completes the RRC connection re-establishment procedure }
then { UE is in NR RRC_CONNECTED state }
}
(5)
with { UE in NR RRC_CONNECTED state and upon detecting radio link failure UE sends RRCReestablishmentRequest message }
ensure that {
when { UE receives a RRCSetup message }
then { UE completes RRC setup procedure by sending RRCSetupComplete message }
}
8.1.5.6.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.3.4, 5.3.7.2, 5.3.7.8, 5.3.10.1, 5.3.10.2 and 5.3.10.3.
[TS 38.331 clause 5.3.3.4]
The UE shall perform the following actions upon reception of the RRCSetup:
1> if the RRCSetup is received in response to an RRCReestablishmentRequest; or
1> if the RRCSetup is received in response to an RRCResumeRequest or RRCResumeRequest1:
2> discard any stored UE Inactive AS context and suspendConfig;
2> discard any current AS security context including the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key;
2> release radio resources for all established RBs except SRB0, including release of the RLC entities, of the associated PDCP entities and of SDAP;
2> release the RRC configuration except for the default L1 parameter values, default MAC Cell Group configuration and CCCH configuration;
2> indicate to upper layers fallback of the RRC connection;
2> stop timer T380, if running;
1> perform the cell group configuration procedure in accordance with the received masterCellGroup and as specified in 5.3.5.5;
1> perform the radio bearer configuration procedure in accordance with the received radioBearerConfig and as specified in 5.3.5.6;
1> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited from another RAT;
1> stop timer T300, T301 or T319 if running;
1> if T390 is running:
2> stop timer T390 for all access categories;
2> perform the actions as specified in 5.3.14.4;
1> if T302 is running:
2> stop timer T302;
2> perform the actions as specified in 5.3.14.4;
1> stop timer T320, if running;
1> if the RRCSetup is received in response to an RRCResumeRequest, RRCResumeRequest1 or RRCSetupRequest:
2> enter RRC_CONNECTED;
2> stop the cell re-selection procedure;
1> consider the current cell to be the PCell;
1> set the content of RRCSetupComplete message as follows:
2> if upper layers provide a 5G-S-TMSI:
3> if the RRCSetup is received in response to an RRCSetupRequest:
4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI-Part2;
3> else:
4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI;
2> set the selectedPLMN-Identity to the PLMN selected by upper layers (TS 24.501 [23]) from the PLMN(s) included in the plmn-IdentityList in SIB1;
2> if upper layers provide the ‘Registered AMF’:
3> include and set the registeredAMF as follows:
4> if the PLMN identity of the ‘Registered AMF’ is different from the PLMN selected by the upper layers:
5> include the plmnIdentity in the registeredAMF and set it to the value of the PLMN identity in the ‘Registered AMF’ received from upper layers;
4> set the amf-Identifier to the value received from upper layers;
3> include and set the guami-Type to the value provided by the upper layers;
2> if upper layers provide one or more S-NSSAI (see TS 23.003 [21]):
3> include the s-NSSAI-List and set the content to the values provided by the upper layers;
2> set the dedicatedNAS-Message to include the information received from upper layers;
1> submit the RRCSetupComplete message to lower layers for transmission, upon which the procedure ends
[TS 38.331 clause 5.3.7.2]
The UE initiates the procedure when one of the following conditions is met:
1> upon detecting radio link failure of the MCG, in accordance with 5.3.10; or
1> upon re-configuration with sync failure of the MCG, in accordance with sub-clause 5.3.5.8.3; or
1> upon mobility from NR failure, in accordance with sub-clause 5.4.3.5; or
1> upon integrity check failure indication from lower layers concerning SRB1 or SRB2, except if the integrity check failure is detected on the RRCReestablishment message; or
1> upon an RRC connection reconfiguration failure, in accordance with sub-clause 5.3.5.8.2.
Upon initiation of the procedure, the UE shall:
1> stop timer T310, if running;
1> stop timer T304, if running;
1> start timer T311;
1> suspend all RBs, except SRB0;
1> reset MAC;
1> release the MCG SCell(s), if configured;
1> release spCellConfig;
1> release delayBudgetReportingConfig, if configured, and stop timer T342, if running;
1> release overheatingAssistanceConfig, if configured, and stop timer T345, if running;
1> perform cell selection in accordance with the cell selection process as specified in TS 38.304 [20], clause 5.2.6.
[TS 38.331 clause 5.3.7.8]
The UE shall:
1> perform the RRC connection establishment procedure as specified in 5.3.3.4.
[TS 38.331 clause 5.3.10.1]
The UE shall:
1> upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while neither T300, T301, T304, T311 nor T319 are running:
2> start timer T310 for the corresponding SpCell.
[TS 38.331 clause 5.3.10.2]
Upon receiving N311 consecutive "in-sync" indications for the SpCell from lower layers while T310 is running, the UE shall:
1> stop timer T310 for the corresponding SpCell.
NOTE 1: In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration.
NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by L1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.
[TS 38.331 clause 5.3.10.3]
The UE shall:
1> upon T310 expiry in PCell; or
1> upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running; or
1> upon indication from MCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from MCG RLC and CA duplication is configured and activated, and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.
2> else:
3> consider radio link failure to be detected for the MCG i.e. RLF;
3> if AS security has not been activated:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘other’;-
3> else if AS security has been activated but SRB2 and at least one DRB have not been setup:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’;
3> else:
4> initiate the connection re-establishment procedure as specified in 5.3.7.
8.1.5.6.1.3 Test description
8.1.5.6.1.3.1 Pre-test conditions
System Simulator:
– 3 NR Cells. NR Cell 1 is the serving cell, NR Cell 2 and NR Cell 4 are the intra-frequency neighbour cell.
None.
Preamble:
– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.
8.1.5.6.1.3.2 Test procedure sequence
Table 8.1.5.6.1.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
“Off” |
“Off” |
|
T0A |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
“Off” |
“Off” |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
-88 |
-94 |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
“Off” |
-88 |
|
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
|||||
Table 8.1.5.6.1.3.2-2: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
“Off” |
“Off” |
|
T0A |
SS/PBCH SSS EPRE |
dBm/SCS |
-82 |
“Off” |
“Off” |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
-82 |
-91 |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
“Off” |
-82 |
|
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2. |
|||||
Table 8.1.5.6.1.3.2-3: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0A |
The SS changes NR Cell 1 parameters according to the row "T0" in table Table 8.1.5.6.1.3.2-1/2 to set NR Cell 1 to Non-suitable “Off”. |
– |
– |
– |
– |
|
0B |
The SS wait for 1,5 s (T310 (2s) is transmitted in SIB1). |
– |
– |
– |
– |
|
0C |
The SS changes NR Cell 1 parameters according to the row "T0A" in table 8.1.5.6.1.3.2-1/2 making NR Cell 1 serving cell. |
– |
– |
– |
– |
|
0D |
Check: For the next 5 s does the UE transmit any signalling message? |
– |
– |
1 |
F |
|
0E |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.10 indicate that the UE is in NR RRC_CONNECTED state on NR Cell 1? |
– |
– |
1 |
P |
|
1 |
The SS changes NR Cell 1, NR Cell 2 and NR Cell 4 parameters according to the row "T1" in table 8.1.5.6.1.3.2-1/2 in order that the radio link quality of NR Cell 1 is degraded, and NR Cell 2 is suitable for camping. |
– |
– |
– |
– |
|
2 |
Check: Does the UE initiate an RRC connection re-establishment procedure on Cell 1 or Cell 2. This is checked during the time T=T310? |
– |
– |
2 |
F |
|
3 |
Check: Does the UE send RRCReestablishmentRequest message on NR Cell 2? |
–> |
NR RRC: RRCReestablishmentRequest |
3 |
P |
|
4 |
The SS transmits RRCReestablishment message. |
<– |
NR RRC: RRCReestablishment |
– |
– |
|
5 |
The UE transmits RRCReestablishmentComplete message. |
–> |
NR RRC: RRCReestablishmentComplete |
– |
– |
|
6 |
The SS transmits an RRCReconfiguration message to resume existing radio bearer. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
7 |
Check: Does the UE transmit an RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationtComplete |
4 |
P |
|
8 |
The SS changes NR Cell 2 and NR Cell 4 parameters according to the row "T2" in table 8.1.5.6.1.3.2-1/2 in order that the radio link quality of NR Cell 2 is degraded and cell 4 is suitable for camping. |
– |
– |
– |
– |
|
9 |
Check: Does the UE send RRCReestablishmentRequest message on NR Cell 4? |
–> |
NR RRC: RRCReestablishmentRequest |
– |
– |
|
10 |
The SS transmits RRCSetup message. |
<– |
NR RRC: RRCSetup |
– |
– |
|
11 |
Check: Does the UE transmit a RRCSetupComplete message and a REGISTRATION REQUEST message indicating "mobility registration updating"? |
–> |
NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST |
5 |
P |
|
11A |
The SS transmits a DLInformationTransfer message and an AUTHENTICATION REQUEST message. |
<– |
RRC: DLInformationTransfer NAS: AUTHENTICATION REQUEST |
– |
– |
|
11B |
The UE transmits an ULInformationTransfer message and an AUTHENTICATION RESPONSE message. |
–> |
RRC: ULInformationTransfer NAS: AUTHENTICATION RESPONSE |
– |
– |
|
11C |
The SS transmits a NAS SECURITY MODE COMMAND message to activate NAS security. |
<– |
RRC: DLInformationTransfer NAS: SECURITY MODE COMMAND |
– |
– |
|
11D |
The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration. |
–> |
RRC: ULInformationTransfer NAS: SECURITY MODE COMPLETE |
– |
– |
|
12 |
The SS transmits a SecurityModeCommand message. |
<– |
NR RRC: SecurityModeCommand |
– |
– |
|
13 |
The UE transmits a SecurityModeComplete message. |
–> |
NR RRC: SecurityModeComplete |
– |
– |
|
14 |
The SS transmits an RRCReconfiguration message to establish SRB2 and DRB and a REGISTRATION ACCEPT message. |
<– |
NR RRC: RRCReconfiguration 5GMM: REGISTRATION ACCEPT |
– |
– |
|
15 |
The UE transmits an RRCReconfigurationtComplete message. |
–> |
NR RRC: RRCReconfigurationtComplete |
– |
– |
|
16 |
The UE sends a REGISTRATION COMPLETE. |
–> |
NR RRC: ULInformationTransfer 5GMM: REGISTRATION COMPLETE |
– |
– |
8.1.5.6.1.3.3 Specific message contents
Table 8.1.5.6.1.3.3-0: SIB1 for Cell 1 (all steps)
|
Derivation Path: TS 38.508-1 [4] table 4.6.1-28 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SIB1 ::= SEQUENCE { |
|||
|
ue-TimersAndConstants SEQUENCE { |
|||
|
t310 |
ms2000 |
||
|
} |
|||
|
} |
|||
Table 8.1.5.6.1.3.3-0A: RLF-TimersAndConstants(preamble)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.1-150 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLF-TimersAndConstants ::= SEQUENCE { |
|||
|
t310 |
ms2000 |
||
|
} |
|||
Table 8.1.5.6.1.3.3-0B: RRCSetup (preamble)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-21 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCSetup ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcSetup SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
spCellConfig SEQUENCE { |
||||
|
rlf-TimersAndConstants CHOICE { |
||||
|
setup |
RLF-TimersAndConstants |
Table 8.1.5.6.1.3.3-0A |
||
|
} |
||||
|
spCellConfigDedicated SEQUENCE { |
||||
|
initialDownlinkBWP SEQUENCE { |
||||
|
radioLinkMonitoringConfig CHOICE { |
||||
|
setup |
RadioLinkMonitoringConfig specified in TS 38.508-1[4] Table 4.6.3-133 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.6.1.3.3-1: RRCReestablishmentRequest (step 3, Table 8.1.5.6.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4] table 4.6.1-12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReestablishmentRequest ::= SEQUENCE { |
|||
|
ue-Identity SEQUENCE { |
|||
|
c-RNTI |
the value of the C-RNTI of the UE |
||
|
physCellId |
PhysicalCellIdentity of NR Cell 1 |
||
|
shortMAC-I |
The same value as the 16 least significant bits of the XMAC-I value calculated by SS |
||
|
} |
|||
|
reestablishmentCause |
otherFailure |
||
|
} |
|||
Table 8.1.5.6.1.3.3-1A: RRCReconfiguration (step 6, Table 8.1.5.6.1.3.2-3)
|
Derivation Path: TS 38.508-1[4], table 4.6.1-13 with condition REEST |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
spCellConfig SEQUENCE { |
||||
|
spCellConfigDedicated SEQUENCE { |
||||
|
initialDownlinkBWP SEQUENCE { |
||||
|
radioLinkMonitoringConfig CHOICE { |
||||
|
setup |
RadioLinkMonitoringConfig specified in TS 38.508-1[4] Table 4.6.3-133 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.6.1.3.3-2: RRCReestablishmentRequest (step 9, Table 8.1.5.6.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4] table 4.6.1-12 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReestablishmentRequest ::= SEQUENCE { |
|||
|
ue-Identity SEQUENCE { |
|||
|
c-RNTI |
the value of the C-RNTI of the UE |
||
|
physCellId |
PhysicalCellIdentity of NR Cell 2 |
||
|
shortMAC-I |
The same value as the 16 least significant bits of the XMAC-I value calculated by SS |
||
|
} |
|||
|
reestablishmentCause |
otherFailure |
||
|
} |
|||
Table 8.1.5.6.1.3.3-3: RRCReconfiguration (step 14, Table 8.1.5.6.1.3.2-3)
|
Derivation Path: TS 38.508-1[4], table 4.6.1-13 with condition NR |
8.1.5.6.2 Void
8.1.5.6.3 Radio link failure / T311 expiry
8.1.5.6.3.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and radio link failure was detected and UE attempts to select a suitable NR cell to re-establish the RRC connection }
ensure that {
when { UE cannot find a suitable NR cell within T311 }
then { UE does not try to re-establish the RRC connection and goes to NR RRC_IDLE state after T311 expired }
}
8.1.5.6.3.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.7.2, 5.3.7.6, 5.3.7.8, 5.3.10.1, 5.3.10.3 and 5.3.5.5.7.
[TS 38.331 clause 5.3.7.2]
The UE initiates the procedure when one of the following conditions is met:
1> upon detecting radio link failure of the MCG, in accordance with 5.3.10; or
1> upon re-configuration with sync failure of the MCG, in accordance with sub-clause 5.3.5.8.3; or
1> upon mobility from NR failure, in accordance with sub-clause 5.4.3.5; or
1> upon integrity check failure indication from lower layers concerning SRB1 or SRB2, except if the integrity check failure is detected on the RRCReestablishment message; or
1> upon an RRC connection reconfiguration failure, in accordance with sub-clause 5.3.5.8.2.
Upon initiation of the procedure, the UE shall:
1> stop timer T310, if running;
1> stop timer T304, if running;
1> start timer T311;
1> suspend all RBs, except SRB0;
1> reset MAC;
1> release the MCG SCell(s), if configured;
1> release spCellConfig;
1> release delayBudgetReportingConfig, if configured, and stop timer T342, if running;
1> release overheatingAssistanceConfig, if configured, and stop timer T345, if running;
1> perform cell selection in accordance with the cell selection process as specified in TS 38.304 [20], clause 5.2.6.
[TS 38.331 clause 5.3.7.7]
Upon T311 expiry, the UE shall:
1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’.
[TS 38.331 clause 5.3.7.8]
The UE shall:
1> perform the RRC connection establishment procedure as specified in 5.3.3.4.
[TS 38.331 clause 5.3.10.1]
The UE shall:
1> upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while neither T300, T301, T304, T311 nor T319 are running:
2> start timer T310 for the corresponding SpCell.
[TS 38.331 clause 5.3.10.3]
The UE shall:
1> upon T310 expiry in PCell; or
1> upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running; or
1> upon indication from MCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from MCG RLC and CA duplication is configured and activated, and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.
2> else:
3> consider radio link failure to be detected for the MCG i.e. RLF;
3> if AS security has not been activated:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘other’;-
3> else if AS security has been activated but SRB2 and at least one DRB have not been setup:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’;
3> else:
4> initiate the connection re-establishment procedure as specified in 5.3.7.
[TS 38.331, 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;
8.1.5.6.3.3 Test description
8.1.5.6.3.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
None.
Preamble:
– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.
8.1.5.6.3.3.2 Test procedure sequence
Table 8.1.5.6.3.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
|
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
|
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
|||
Table 8.1.5.6.3.3.2-2: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
|
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-82 |
|
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2. |
|||
Table 8.1.5.6.3.3.2-3: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS changes NR Cell 1 parameters according to the row "T1" in table 8.1.5.6.3.3.2-1 in order that the radio link quality of NR Cell 1 is degraded. |
– |
– |
– |
– |
|
2 |
Wait for 12s (T311 (10s) is transmitted in RRCSetup). |
– |
– |
– |
– |
|
3 |
The SS changes NR Cell 1 parameters according to the row "T2" in table 8.1.5.6.3.3.2-1 making NR Cell 1 is suitable for camping. |
– |
– |
– |
– |
|
4 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.5 indicate that the UE is camped on NR Cell 1? |
– |
– |
1 |
P |
8.1.5.6.3.3.3 Specific message contents
Table 8.1.5.6.3.3.3-1: RRCSetup(Preamble)
|
Derivation Path: TS 38.508-1 [4] table 4.6.1-21 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCSetup ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcSetup SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig with condition SRB1 |
OCTET STRING (CONTAINING CellGroupConfig) |
|
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.6.3.3.3-2: CellGroupConfig (Table 8.1.5.6.3.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
rlf-TimersAndConstants SEQUENCE { |
|||
|
t311-v1530 |
ms10000 |
||
|
} |
|||
|
spCellConfigDedicated |
ServingCellConfig |
||
|
} |
|||
Table 8.1.5.6.3.3.3-3: ServingCellConfig (Table 8.1.5.6.3.3.3-2: CellGroupConfig)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-167 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfig ::= SEQUENCE { |
|||
|
initialDownlinkBWP |
BWP-DownlinkDedicated |
||
|
} |
|||
Table 8.1.5.6.3.3.3-4: BWP-DownlinkDedicated (Table 8.1.5.6.3.3.3-3: ServingCellConfig)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-11 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
BWP-DownlinkDedicated ::= SEQUENCE { |
|||
|
radioLinkMonitoringConfig |
RadioLinkMonitoringConfig |
||
|
} |
|||
8.1.5.6.4 Void
8.1.5.6.5 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell
8.1.5.6.5.1 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band Contiguous CA
8.1.5.6.5.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED, security activated and SCell configured }
ensure that {
when { the SCell becomes out of coverage for the UE }
then { UE does not consider radio link failure to be detected and stay in NR RRC_CONNECTED state }
}
8.1.5.6.5.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.3.5.5.6, 5.3.10.1 and 5.3.10.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.6]
The UE shall:
1> if the received rlf-TimersAndConstants is set to release:
2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
1> else:
2> (re-)configure the value of timers and constants in accordance with received rlf-TimersAndConstants;
2> stop timer T310 for this cell group, if running;
2> reset the counters N310 and N311.
[TS 38.331, clause 5.3.10.1]
The UE shall:
1> upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while neither T300, T301, T304, T311 nor T319 are running:
2> start timer T310 for the corresponding SpCell.
[TS 38.331, clause 5.3.10.3]
The UE shall:
1> upon T310 expiry in PCell; or
1> upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running; or
1> upon indication from MCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from MCG RLC and CA duplication is configured and activated, and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.
2> else:
3> consider radio link failure to be detected for the MCG, i.e. MCG RLF;
3> if AS security has not been activated:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘other’;-
3> else if AS security has been activated but SRB2 and at least one DRB have not been setup:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’;
3> else:
4> initiate the connection re-establishment procedure as specified in 5.3.7.
The UE shall:
1> upon T310 expiry in PSCell; or
1> upon random access problem indication from SCG MAC; or
1> upon indication from SCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from SCG RLC and CA duplication is configured and activated, and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.
2> else:
3> consider radio link failure to be detected for the SCG, i.e. SCG RLF;
3> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.
8.1.5.6.5.1.3 Test description
8.1.5.6.5.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, and NR Cell 3
– NR Cell 1 is PCell
– NR Cell 3 is 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.
UE:
None.
Preamble:
– The UE is in 5GS state 3N-A with UE test loop mode B active if pc_IP_Ping is set to FALSE according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3 on NR Cell 1.
8.1.5.6.5.1.3.2 Test procedure sequence
Table 8.5.1.7.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.1.5.6.5.1.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
Remark |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
NR Cell1 and NR Cell 3 are available |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
“Off” |
Only NR Cell 1 is available. |
Table 8.1.5.6.5.1.3.2-1A: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
Remark |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-95 |
-95 |
NR Cell1 and NR Cell 3 are available |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-95 |
“Off” |
Only NR Cell 1 is available. |
Table 8.1.5.6.5.1.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to configure NR Cell 3 as SCell. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1. |
–> |
RRCReconfigurationComplete |
– |
– |
|
2A |
The SS transmits an Activation MAC control element to activate SCell. |
<– |
MAC PDU (SCell Activation/Deactivation MAC CE of one octet (C1=1)) |
– |
– |
|
3 |
Wait for 1s. |
– |
– |
– |
– |
|
4 |
The SS changes power levels according to row "T1" in Table 8.1.5.6.5.1.3.2-1/1A. |
– |
– |
– |
– |
|
5 |
Wait for 1s. |
– |
– |
– |
– |
|
6 |
Check: Does the UE transmit an RRCReestablishmentRequest message on NR Cell 1 within next 2 seconds? |
–> |
RRCReestablishmentRequest |
1 |
F |
|
7 |
The SS changes power levels according to row "T0" in Table 8.1.5.6.5.1.3.2-1/1A. |
– |
– |
– |
– |
|
8 |
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 NR Cell 3? |
– |
– |
1 |
P |
|
9 |
The SS transmits an RRCReconfiguration message containing an sCellToReleaseList with SCell NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
10 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationtComplete |
– |
– |
8.1.5.6.5.1.3.3 Specific message contents
Table 8.1.5.6.5.1.3.3-1: RRCReconfiguration (step 1, Table 8.1.5.6.5.1.3.2-2)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add |
Table 8.1.5.6.5.1.3.3-2: Void
Table 8.1.5.6.5.1.3.3-3: Void
Table 8.1.5.6.5.1.3.3-4: RRCReconfiguration (Step 9, Table 8.1.5.6.5.1.3.2-2)
|
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 { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
sCellToAddModList |
Not present |
|||
|
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
|||
|
SCellIndex[1] |
SCellIndex of Cell 3 |
entry 1 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
8.1.5.6.5.2 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Inter-band CA
8.1.5.6.5.2.1 Test Purpose (TP)
Same as TC 8.1.5.6.5.1 but applied to Inter-band CA Test Case.
8.1.5.6.5.2.2 Conformance Requirements
Same as TC 8.1.5.6.5.1 but applied to Inter-band CA Test Case.
8.1.5.6.5.2.3 Test Description
8.1.5.6.5.2.3.1 Pre-test conditions
Same as TC 8.1.5.6.5.1 but with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: Cell 10 replaces Cell 3.
– Cell 10 is an Inactive SCell according to TS 38.508-1 [4] clause 6.3.1.
8.1.5.6.5.2.3.2 Test procedure sequence
Same as TC 8.1.5.6.5.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: Cell 10 replaces Cell 3.
8.1.5.6.5.2.3.3 Specific message contents
Same as TC 8.1.5.6.5.1 but applied to Inter-band CA Test Case.
8.1.5.6.5.3 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band non-Contiguous CA
8.1.5.6.5.3.1 Test Purpose (TP)
Same as TC 8.1.5.6.5.1 but applied to Intra-band non-Contiguous CA Test Case.
8.1.5.6.5.3.2 Conformance Requirements
Same as TC 8.1.5.6.5.1 but applied to Intra-band non-Contiguous CA Test Case.
8.1.5.6.5.3.3 Test Description
8.1.5.6.5.3.3.1 Pre-test conditions
Same as TC 8.1.5.6.5.1 but with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
8.1.5.6.5.3.3.2 Test procedure sequence
Same as TC 8.1.5.6.5.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
8.1.5.6.5.3.3.3 Specific message contents
Same as TC 8.1.5.6.5.1 but applied to Intra-band non-Contiguous CA Test Case.
8.1.5.7 Failure information
8.1.5.7.1 Failure information / RLC failure / MCG
8.1.5.7.1.1 Failure information / RLC failure / MCG / Intra-band Contiguous CA
8.1.5.7.1.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { an indication from MCG RLC that the maximum number of retransmissions has been reached and when CA duplication is configured and activated and for the corresponding logical channel allowedServingCells only includes SCell(s) }
then { UE initiates the failure information procedure to report RLC failure via SRB1 }
}
8.1.5.7.1.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clauses 5.7.5.2 and 5.7.5.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.10.3]
The UE shall:
…
1> upon indication from MCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from MCG RLC and CA duplication is configured and activated, and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.
…
[TS 38.331, clause 5.7.5.2]
A UE initiates the procedure when there is a need inform the network about a failure detected by the UE. In particular, the UE initiates the procedure when the following condition is met:
1> upon detecting failure for an RLC bearer, in accordance with 5.3.10.3;
Upon initiating the procedure, the UE shall:
1> initiate transmission of the FailureInformation message as specified in 5.7.5.3;
[TS 38.331, clause 5.7.5.3]
The UE shall:
1> if initiated to provide RLC failure information, set FailureInfoRLC-Bearer as follows:
2> set logicalChannelIdentity to the logical channel identity of the failing RLC bearer;
2> set cellGroupId to the cell group identity of the failing RLC bearer;
2> set the failureType as rlc-failure;
1> if used to inform the network about a failure for an MCG RLC bearer:
2> submit the FailureInformation message to lower layers for transmission via SRB1;
…
8.1.5.7.1.1.3 Test description
8.1.5.7.1.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell, NR Cell 3 is the SCell.
UE:
– None.
Preamble:
Same Pre-Test conditions as in clause 7.1.3.0 except the following:
– 2 NR cells (NR Cell 1 as Pcell and NR Cell 3 as Scell)
– NR Cell 1 is configured with DRBs in RLC AM mode
8.1.5.7.1.1.3.2 Test procedure sequence
Table 8.1.5.7.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
||
|
U – S |
Message |
|||||
|
1 |
The SS transmits an RRCReconfiguration message to add SCell (NR Cell 3) for the UE. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
|
2 |
The UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
|
2A |
The SS transmits a SCell Activation/Deactivation MAC-CE to activate SCell (NR Cell 3). |
<– |
MAC PDU (SCell Activation/Deactivation MAC CE of one octet (C1=1)) |
– |
– |
|
|
3 |
The SS transmits an RRCReconfiguration message to reconfigure DRB #j for the UE |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
|
4 |
The UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
|
5 |
Void |
– |
– |
– |
– |
|
|
6 |
Void |
– |
– |
– |
– |
|
|
7 |
The SS stops sending MCG RLC acknowledgmentson PCell (NR Cell 1) and SCell (NR Cell 3) |
– |
– |
– |
– |
|
|
8 |
SS transmits a periodic UL Grant on SCell (as PUCCH is not configured in the SCell), allowing the UE to loop back the PDCP PDU on SCell. |
– |
– |
– |
||
|
8A |
The SS transmits one PDCP PDU to the UE on DRB #j. |
<- |
PDCP PDU |
– |
– |
|
|
– |
EXCEPTION: Steps 9-9A occur in any sequence. |
– |
– |
– |
– |
|
|
9 |
The UE loops back the PDCP PDU on PCell (NR Cell 1) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
|
9A |
The UE loops back the PDCP PDU on SCell (NR Cell 3) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
|
10 |
Check: Does the UE transmit a FailureInformation message with failureType set to ‘rlc-failure’? |
–> |
NR RRC: FailureInformation |
1 |
P |
|
|
10A |
SS resumes sending MCG RLC acknowledgments |
– |
– |
– |
– |
|
|
11 |
The SS transmits an RRCReconfiguration message containing an sCellToReleaseList with SCell NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
|
12 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
8.1.5.7.1.1.3.3 Specific message contents
Table 8.1.5.7.1.1.3.3-1: RRCReconfiguration (Step 1, Table 8.1.5.7.1.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 { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
|||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
|||
|
sCellIndex |
SCellIndex for NR Cell 3 |
|||
|
sCellConfigCommon |
ServingCellConfigCommon |
|||
|
sCellConfigDedicated |
ServingCellConfig |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.7.1.1.3.3-1A: ServingCellConfig (Table 8.1.5.7.1.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-167. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ServingCellConfig ::= SEQUENCE { |
|||
|
uplinkConfig SEQUENCE { |
|||
|
initialUplinkBWP |
BWP-UplinkDedicated |
||
|
} |
|||
|
} |
|||
Table 8.1.5.7.1.1.3.3-1B: BWP-UplinkDedicated (Table 8.1.5.7.1.1.3.3-1A)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
BWP-UplinkDedicated ::= SEQUENCE { |
|||
|
pucch-Config |
Not present |
||
|
} |
|||
Table 8.1.5.7.1.1.3.3-1C: ServingCellConfigCommon (Table 8.1.5.7.1.1.3.3-1)
|
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 |
||
|
uplinkConfigCommon |
UplinkConfigCommon |
||
|
} |
|||
Table 8.1.5.7.1.1.3.3-1D: UplinkConfigCommon (Table 8.1.5.7.1.1.3.3-1C)
|
Derivation Path: TS 38.331 [6], clause 6.3.2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UplinkConfigCommon ::= SEQUENCE { |
|||
|
initialUplinkBWP |
BWP-UplinkCommon |
||
|
} |
|||
Table 8.1.5.7.1.1.3.3-1E: BWP-UplinkCommon (Table 8.1.5.7.1.1.3.3-1D)
|
Derivation Path: TS 38.331 [6], clause 6.3.2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
BWP-UplinkCommon ::= SEQUENCE { |
|||
|
pucch-ConfigCommon |
Not present |
||
|
} |
|||
Table 8.1.5.7.1.1.3.3-2: RRCReconfiguration (Step 3, Table 8.1.5.7.1.1.3.2-1)
|
Derivation Path: TS 38.508-1[4], Table 4.6.1-13 with condition NR |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
RadioBearerConfig-DRB |
Table 8.1.5.7.1.1.3.3-3 |
|
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig-DRB |
Table 8.1.5.7.1.1.3.3-4 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.7.1.1.3.3-3: RadioBearerConfig-DRB (Table 8.1.5.7.1.1.3.3-2)
|
Derivation Path: TS 508-1 [4], Table 4.6.3-132 with condition DRB2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
1 entry |
||
|
DRB-ToAddMod[1] SEQUENCE { |
entry 1 |
||
|
drb-Identity |
DRB-Identity with condition DRB j |
j is the ID of the DRB established during the preamble which is allocated according to internal TTCN mapping |
|
|
pdcp-Config |
PDCP-Config |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.7.1.1.3.3-4: PDCP-Config (Table 8.1.5.7.1.1.3.3-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-99 with condition Split |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDCP-Config ::= SEQUENCE { |
|||
|
moreThanOneRLC SEQUENCE { |
|||
|
primaryPath SEQUENCE { |
|||
|
logicalChannel |
LogicalChannelIdentity with Condition DRB j |
||
|
} |
|||
|
pdcp-Duplication |
True |
||
|
} |
|||
|
} |
|||
Table 8.1.5.7.1.1.3.3-5: CellGroupConfig-DRB
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition DRB j |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig { |
2 entries |
||
|
RLC-BearerConfig[1] |
RLC-BearerConfig-1 |
entry 1 Table 8.1.5.7.1.1.3.3-6 Primary RLC |
|
|
RLC-BearerConfig[2] |
RLC-BearerConfig-2 |
entry 1 Table 8.1.5.7.1.1.3.3-7 Secondary RLC |
|
|
} |
|||
|
spCellConfig |
Not present |
||
|
} |
|||
Table 8.1.5.7.1.1.3.3-6: RLC-BearerConfig-1 (Table 8.1.5.7.1.1.3.3-5)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-148 with Condition AM |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLC-BearerConfig ::= SEQUENCE { |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j |
ID of primary logical channel |
|
|
servedRadioBearer CHOICE { |
|||
|
drb-Identity |
DRB-Identity with condition DRB j |
||
|
} |
|||
|
rlc-Config CHOICE { |
|||
|
am SEQUENCE { |
|||
|
ul-AM-RLC SEQUENCE { |
|||
|
maxRetxThreshold |
t32 |
To ensure RLC failure happens before RLF |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
mac-LogicalChannelConfig SEQUENCE { |
|||
|
ul-SpecificParameters SEQUENCE { |
|||
|
allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex { |
1 entry |
||
|
ServCellIndex[1] |
ServCellIndex of NR Cell 1 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.7.1.1.3.3-7: RLC-BearerConfig-2 (Table 8.1.5.7.1.1.3.3-5)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-148 with Condition AM |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLC-BearerConfig ::= SEQUENCE { |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j+1 |
To ensure ID of secondary logical channel ID is different with existing logical channel and the primary logical channel defined in Table 8.1.5.7.1.1.3.3-6 |
|
|
servedRadioBearer CHOICE { |
|||
|
drb-Identity |
DRB-Identity with condition DRB j |
||
|
} |
|||
|
rlc-Config CHOICE { |
|||
|
am SEQUENCE { |
|||
|
ul-AM-RLC SEQUENCE { |
|||
|
maxRetxThreshold |
t1 |
To ensure RLC failure happens before RLF |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
mac-LogicalChannelConfig SEQUENCE { |
|||
|
ul-SpecificParameters SEQUENCE { |
|||
|
allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex { |
1 entry |
||
|
ServCellIndex[1] |
ServCellIndex of NR Cell 3 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.7.1.1.3.3-8: FailureInformation (Step 10, Table 8.1.5.7.1.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-4 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
FailureInformation ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
failureInformation SEQUENCE { |
||||
|
failureInfoRLC-Bearer SEQUENCE { |
||||
|
cellGroupId |
CellGroupId as per TS 38.508-1 [4] Table 4.6.3-20 |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j+1 |
|||
|
failureType |
rlc-failure |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.7.1.1.3.3-9: RRCReconfiguration (step 11, Table 8.1.5.7.1.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 { |
|||
|
nonCriticalExtension SEQUENCE{ |
|||
|
masterCellGroup |
CellGroupConfig |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.7.1.1.3.3-10: CellGroupConfig (Table 8.1.5.7.1.1.3.3-9)
|
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.1.5.7.1.2 Failure information / RLC failure / MCG / Inter-band CA
8.1.5.7.1.2.1 Test Purpose (TP)
Same as TC 8.1.5.7.1.1 but applied to Inter-band CA case.
8.1.5.7.1.2.2 Conformance requirements
Same as TC 8.1.5.7.1.1 but applied to Inter-band CA case.
8.1.5.7.1.2.3 Test description
8.1.5.7.1.2.3.1 Pre-test conditions
Same as test case 8.1.5.7.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.1.5.7.1.2.3.2 Test procedure sequence
Same as test case 8.1.5.7.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.1.5.7.1.2.3.3 Specific message contents
Same as test case 8.1.5.7.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.1.5.7.1.3 Failure information / RLC failure / MCG / Intra-band non Contiguous CA
8.1.5.7.1.3.1 Test Purpose (TP)
Same as TC 8.1.5.7.1.1 but applied to Intra-band non Contiguous CA case.
8.1.5.7.1.3.2 Conformance requirements
Same as TC 8.1.5.7.1.1 but applied to Intra-band non Contiguous CA case.
8.1.5.7.1.3.3 Test description
8.1.5.7.1.3.3.1 Pre-test conditions
Same as test case 8.1.5.7.1.1 with the following differences:
– CA configuration: Intra-band non Contiguous CA replaces Intra-band Contiguous CA.
8.1.5.7.1.3.3.2 Test procedure sequence
Same as test case 8.1.5.7.1.1 with the following differences:
– CA configuration: Intra-band non Contiguous CA replaces Intra-band Contiguous CA.
8.1.5.7.1.3.3.3 Specific message contents
Same as test case 8.1.5.7.1.1 but applied to Intra-band non Contiguous CA case.
8.1.5.8 Processing delay
8.1.5.8.1 Processing delay / RRC_Idle to RRC_Connected / RRC_Inactive to RRC_Connected / Success / Latency check
8.1.5.8.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_IDLE state and has sent an RRCSetupRequest message }
ensure that {
when { UE receives RRCSetup message and after 10ms receives an UL grant }
then { UE successfully transmits RRCSetupComplete message }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receive a SecurityModeCommand message and after 5ms receives an UL grant }
then { UE successfully transmits SecurityModeComplete }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receive a RRCReconfiguration message to establish DRB that is not part of the current UE configuration and after 10ms receives an UL grant }
then { UE successfully transmits RRCReconfigurationComplete message }
}
(4)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an UECapabilityEnquiry message and after 80ms receives an UL grant }
then { UE successfully transmits an UECapabilityInformation message }
}
(5)
with { UE in NR RRC_INACTIVE state and has sent an RRCResumeRequest message }
ensure that {
when { UE receives RRCResume message and after 6 or 10ms receives an UL grant depending on UE capability }
then { UE successfully transmits RRCResumeComplete message }
}
(6)
Void
(7)
with { UE in NR RRC_CONNECTED state and and has sent an RRCReestablishmentRequest message after detecting radio link failure on expiring of timer T310 }
ensure that {
when { UE receives RRCReestablishment message and after 10ms receives an UL grant }
then { UE successfully transmits RRCReestablishmentComplete message }
}
(8)
Void
(9)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives CounterCheck message and after 5ms receives an UL grant }
then { UE successfully transmists an CounterCheckResponse message }
}
8.1.5.8.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.3.3.4, 5.3.4.3, 5.3.5.3, 5.3.6.3, 5.3.7.4, 5.3.13.4, 5.6.1.3 and 12. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.3.4]
The UE shall perform the following actions upon reception of the RRCSetup:
…
1> submit the RRCSetupComplete message to lower layers for transmission, upon which the procedure ends.
[TS 38.331, clause 5.3.4.3]
The UE shall:
…
1> if the SecurityModeCommand message passes the integrity protection check:
…
2> submit the SecurityModeComplete message to lower layers for transmission, 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 masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
…
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
…
1> else (RRCReconfiguration was received via SRB1):
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
…
[38.331, clause 5.3.6.3]
Upon receiving the CounterCheck message, the UE shall:
…
1> submit the CounterCheckResponse message to lower layers for transmission upon which the procedure ends.
[38.331, clause 5.3.7.4]
The UE shall set the contents of RRCReestablishmentRequest message as follows:
…
1> submit the RRCReestablishmentRequest message to lower layers for transmission.
[38.331, clause 5.3.13.4]
The UE shall:
…
1> if the RRCResume includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
…
1> submit the RRCResumeComplete message to lower layers for transmission;
…
[38.331, clause 5.6.1.3]
The UE shall set the contents of UECapabilityInformation message as follows:
1> if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to nr:
2> include in the ue-CapabilityRAT-ContainerList a UE-CapabilityRAT-Container of the type UE-NR-Capability and with the rat-Type set to nr;
2> include the supportedBandCombinationList, featureSets and featureSetCombinations as specified in clause 5.6.1.4;
…
1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends.
[TS 38.331, clause 12]
The UE performance requirements for RRC procedures are specified in the following tables. The performance requirement is expressed as the time in [ms] from the end of reception of the network -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> network response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation). In case the RRC procedure triggers BWP switching, the RRC procedure delay is the value defined in the following table plus the BWP switching delay defined in TS 38.133 [14], clause 8.6.3.
Figure 12.1-1: Illustration of RRC procedure delay
Table 12.1-1: UE performance requirements for RRC procedures for UEs
|
Procedure title: |
Network -> UE |
UE -> Network |
Value [ms] |
Notes |
|---|---|---|---|---|
|
RRC Connection Control Procedures |
||||
|
RRC reconfiguration |
RRCReconfiguration |
RRCReconfigurationComplete |
10 |
|
|
RRC reconfiguration (scell addition/release) |
RRCReconfiguration |
RRCReconfigurationComplete |
16 |
|
|
RRC setup |
RRCSetup |
RRCSetupComplete |
10 |
|
|
RRC re-establishment |
RRCReestablishment |
RRCReestablishmentComplete |
10 |
|
|
RRC resume |
RRCResume |
RRCResumeComplete |
6 or 10 |
Value=6 applies for a UE supporting reduced CP latency for the case of RRCResume message only including MAC and PHY configuration, reestablishPDCP and reestablishRLC for SRB2 and DRB(s), and no DRX, SPS, configured grant, CA or MIMO re-configuration will be triggered by this message. Further, the UL grant for transmission of RRCResumeComplete and the data is transmitted over common search space with DCI format 0_0. In this scenario, the RRC procedure delay [ms] can extend beyond the reception of the UL grant, up to 7 ms. For other cases, Value = 10 applies. |
|
RRC resume (scell addition) |
RRCResume |
RRCResumeComplete |
16 |
|
|
Initial AS security activation |
SecurityModeCommand |
SecurityModeComplete/SecurityModeFailure |
5 |
|
|
Other procedures |
||||
|
UE capability transfer |
UECapabilityEnquiry |
UECapabilityInformation |
80 |
|
|
Counter check |
CounterCheck |
CounterCheckResponse |
5 |
|
8.1.5.8.1.3 Test description
8.1.5.8.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 and NR Cell 2.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells.
– Test frequency NRf1 is as specified in TS 38.508-1 [4] clause 4.3.1 using the common highest UL and DL channel bandwidth and using the default subcarrier spacing specified in TS 38.508-1 [4] clause 6.2.3.1.
UE:
– None.
Preamble:
– The UE is in state RRC_IDLE using generic procedure parameter Connectivity (NR) according to TS 38.508-1 [4], clause 4.5.4.
8.1.5.8.1.3.2 Test procedure sequence
Table 8.1.5.8.1.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while column marked "T1", is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.1.5.8.1.3.2-1: Time instances of cell power level and parameter changes in FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-96 |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
-88 |
Table 8.1.5.8.1.3.2-2: Time instances of cell power level and parameter changes in FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
FFS |
Table 8.1.5.8.1.3.2-3: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits a Paging message including a matched ng-5G-S-TMSI. |
<– |
NR RRC: Paging |
– |
– |
|
2 |
The UE transmits an RRCSetupRequest message. |
–> |
NR RRC: RRCSetupRequest |
– |
– |
|
3 |
The SS transmits an RRCSetup message. |
<– |
NR RRC: RRCSetup |
– |
– |
|
3A |
The SS starts transmitting a periodic DCI from (10∙2μ+1+TDL) slots after step 3 to schedule PUSCH. (Note 1, Note 2) |
||||
|
4 |
Check: Does the UE transmit an RRCSetupComplete message piggybacked with SERVICE REQUEST message within (10∙2μ+1+TDL+K2) slots after successful completion of step 3? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCSetupComplete NR 5GMM: SERVICE REQUEST |
1 |
P |
|
5 |
The SS transmits a SecurityModeCommand message. |
<– |
NR RRC: SecurityModeCommand |
– |
– |
|
5A |
The SS starts transmitting a periodic DCI from (5∙2μ+1+TDL) slots after step 5 to schedule PUSCH. (Note 1, Note 2) |
||||
|
6 |
Check: Does the UE transmit a SecurityModeComplete message within (5∙2μ+1+TDL+K2) slots after successful completion of step 5? (Note 1, Note 2, Note 3) |
–> |
NR RRC: SecurityModeComplete |
2 |
P |
|
7 |
The SS transmits a UECapabilityEnquiry message. |
<– |
NR RRC: UECapabilityEnquiry |
– |
– |
|
7A |
The SS starts transmitting a periodic DCI with the maximum grant allowed by the carrier bandwidth from (80∙2μ+1+TDL) slots after step 7 to schedule PUSCH. (Note 1, Note 2) |
||||
|
8 |
Check: Does the UE transmit a UECapabilityInformation message within (80∙2μ+1+TDL+K2) slots after successful completion of step 7? (Note 1, Note 2, Note 3) |
–> |
NR RRC: UECapabilityInformation |
4 |
P |
|
9 |
The SS transmits an RRCReconfiguration message to establish SRB2 and DRB #n for the UE piggybacked with SERVICE ACCEPT message. |
<– |
NR RRC: RRCReconfiguration NR 5GMM: SERVICE ACCEPT |
– |
– |
|
9A |
The SS starts transmitting a periodic DCI from (10∙2μ+1+TDL) slots after step 9 to schedule PUSCH. (Note 1, Note 2) |
||||
|
10 |
Check: Does the UE transmit an RRCReconfigurationComplete message within (10∙2μ+1+TDL+K2) slots after successful completion of step 9? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCReconfigurationComplete |
3 |
P |
|
11 |
The SS transmits a CounterCheck message. |
<– |
NR RRC: CounterCheck |
– |
– |
|
11A |
The SS starts transmitting a periodic DCI from (5∙2μ+1+TDL) slots after step 11 to schedule PUSCH. (Note 1, Note 2) |
||||
|
12 |
Check: Does the UE transmit a CounterCheckResponse message within (5∙2μ+1+TDL+K2) slots after successful completion of step 11? (Note 1, Note 2, Note 3) |
–> |
NR RRC: CounterCheckResponse |
9 |
P |
|
13 |
Void |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 14a1 to 14a7 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported |
– |
– |
– |
– |
|
14a1 |
IF pc_inactiveState THEN the SS transmits an RRCRelease message with suspendConfig. |
<– |
NR RRC: RRCRelease |
– |
– |
|
14a2 |
Wait 1s to let UE enter RRC_INACTIVE state. |
– |
– |
– |
– |
|
14a3 |
The SS transmits a Paging message including a matched ng-5G-S-TMSI. |
<– |
NR RRC: Paging |
– |
– |
|
14a4 |
The UE transmits an RRCResumeRequest message. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
14a5 |
The SS transmits an RRCResume message for the UE |
<– |
NR RRC: RRCResume |
– |
– |
|
– |
EXCEPTION: Steps 14a5Aa1 to 14a5Ab2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported |
– |
– |
– |
– |
|
14a5Aa1 |
IF pc_reducedCP_Latency THEN the SS starts transmitting a periodic DCI from (6∙2μ+1+TDL) slots after step 14a5 to schedule PUSCH. (Note 1, Note 2) |
||||
|
14a5Aa2 |
Check: Does the UE transmit an RRCResumeComplete message within (6∙2μ+1+TDL+K2) slots after successful completion of step 14a5? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCResumeComplete |
5 |
P |
|
14a5Ab1 |
ELSE the SS starts transmitting a periodic DCI from (10∙2μ+1+TDL) slots after step 14a5 to schedule PUSCH. (Note 1, Note 2) |
||||
|
14a5Ab2 |
Check: Does the UE transmit an RRCResumeComplete message within (10∙2μ+1+TDL+K2) slots after successful completion of step 14a5? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCResumeComplete |
5 |
P |
|
14a6-14a7 |
Void |
– |
– |
– |
– |
|
14-21 |
Void |
– |
– |
– |
– |
|
22 |
The SS re-adjusts the SS levels according to row "T1" in table 8.1.5.8.1.3.2-1/2 in order that the radio link quality of NR Cell 1 is degraded, and NR Cell 2 is suitable for camping |
– |
– |
– |
– |
|
23 |
Wait 1s to let T310 expire |
– |
– |
– |
– |
|
24 |
The UE transmits an RRCReestablishmentRequest message on Cell 2 |
–> |
NR RRC: RRCReestablishmentRequest |
– |
– |
|
25 |
The SS transmits an RRCReestablishment message on slot #i in the radio frame,where: i = 1 for μ=0,1 i = 21 for μ=3 (Note 2) |
<– |
NR RRC: RRCReestablishment |
– |
– |
|
25A |
The SS starts transmitting a periodic DCI from (10∙2μ+1+TDL) slots after step 25 to schedule PUSCH. IF UE transmits a Random Access Preamble, then SS sends RAR. (Note 1, Note 2) |
– |
– |
– |
– |
|
26 |
Check: Does the UE transmit an RRCReestablishmentComplete message within (10∙2μ+1+TDL+K2) slots after successful completion of step 25? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCReestablishmentComplete |
7 |
P |
|
26A |
The SS transmits an RRCReconfiguration message to resume existing radio bearer. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
26B |
The UE transmit an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationtComplete |
– |
– |
|
27-35 |
Void |
– |
– |
– |
– |
|
Note 1: TDL is the delay in slots to the next available DL slot suitable for the transmission of a DCI if the UL grant is provided by DCI, and it is the delay in slots to the DL slot used for the transmission of RAR if the UL grant is provided by RAR. Note 2: μ is the SCS index. μ = 0/1/2/3 for SCS = 15kHz/30kHz/60kHz/120kHz respectively. Note 3: K2 is the offset (in slots) between UL grant and the PUSCH it scheduled |
|||||
8.1.5.8.1.3.3 Specific message contents
Table 8.1.5.8.1.3.3-1: RRCReconfiguration (Step 9, Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1[4], table 4.6.1-13 with condition NR |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcReconfiguration SEQUENCE { |
|||
|
radioBearerConfig |
RadioBearerConfig-SRB2-DRB(1,0) |
TS 38.508-1 [4] Table 4.8.1-4 |
|
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
masterCellGroup |
CellGroupConfig-SRB2-DRB(1,0) |
TS 38.508-1 [4] Table 4.8.1-2B |
|
|
dedicatedNAS-MessageList |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.8.1.3.3-2: CounterCheck (Step 11, Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1[4], Table 4.6.1-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CounterCheck ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
counterCheck SEQUENCE { |
||||
|
drb-CountMSB-InfoList SEQUENCE (SIZE (1..maxDRB)) OF DRB-CountMSB-Info { |
1 entry |
|||
|
drb-Identity[1] |
DRB-Identity with Condition DRBn |
entry 1 n is the index of the DRB established in step 9 of Table 8.1.5.8.1.3.2-3, which is allocated according to internal TTCN mapping |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.8.1.3.3-3: CounterCheckResponse (Step 12, Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1[4], Table 4.6.1-2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CounterCheckResponse ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
counterCheckResponse SEQUENCE { |
||||
|
drb-CountInfoList SEQUENCE (SIZE (0..maxDRB)) OF DRB-CountInfo { |
1 entry |
|||
|
drb-Identity[1] |
DRB-Identity with Condition DRBn |
entry 1 n is the index of the DRB established in step 9 of Table 8.1.5.8.1.3.2-3, which is allocated according to internal TTCN mapping |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.8.1.3.3-4: RRCRelease (Step 14a1, Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-16 with Condition NR_RRC_INACTIVE |
Table 8.1.5.8.1.3.3-5: RRCResume (Step 14a5, Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1[4],Table 4.6.1-17 |
Table 8.1.5.8.1.3.3-6 to Table 8.1.5.8.1.3.3-10: Void
Table 8.1.5.8.1.3.3-11: Physical layer parameters for DCI format 1_0 (Steps 25, Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.3.6.1.2.1-1 |
|||
|
Parameter |
Value |
Value in binary |
Condition |
|
PDSCH-to-HARQ_feedback timing indicator |
K1 slots as specified in 9.2.3 in TS 38.213 |
||
|
µ=0 (SCS=15kHz): K1=3 |
‘010’B |
||
|
µ=1 (SCS=30kHz): K1=7 |
‘110’B |
||
|
µ=3 (SCS=120kHz): K1=3 |
‘010’B |
||
Table 8.1.5.8.1.3.3-12: SIB1 (Preamble, and all steps of Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
SIB1 ::= SEQUENCE { |
||||
|
cellSelectionInfo SEQUENCE { |
||||
|
servingCellConfigCommon SEQUENCE { |
||||
|
uplinkConfigCommon SEQUENCE { |
||||
|
initialUplinkBWP SEQUENCE { |
||||
|
rach-ConfigCommon CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
rach-ConfigGeneric SEQUENCE { |
||||
|
prach-ConfigurationIndex |
159 |
FR2 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.8.1.3.3-13: RRCReconfiguration (Step 26A, Table 8.1.5.8.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition REEST |
8.1.5.8.2 Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition
8.1.5.8.2.1 Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition / Intra-band Contiguous CA
8.1.5.8.2.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message containing sCellToAddModList with a SCell addition and after 16ms receives an UL grant }
then { UE successfully transmits RRCReconfigurationComplete message }
}
(2)
with { UE in NR RRC_INACTIVE state and has sent an RRCResumeRequest message }
ensure that {
when { UE receives RRCResume message containing sCellToAddModList with a SCell addition and after 16ms receives an UL grant }
then { UE successfully transmits RRCResumeComplete message }
}
8.1.5.8.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.3.3.4, 5.3.4.3, 5.3.5.3, 5.3.6.3, 5.3.7.4, 5.3.13.4, 5.6.1.3 and 12. Unless otherwise stated these are Rel-15 requirements.
[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> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
…
1> else (RRCReconfiguration was received via SRB1):
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
…
[38.331, clause 5.3.13.4]
The UE shall:
…
1> if the RRCResume includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
…
1> submit the RRCResumeComplete message to lower layers for transmission;
…
[TS 38.331, clause 12]
The UE performance requirements for RRC procedures are specified in the following tables. The performance requirement is expressed as the time in [ms] from the end of reception of the network -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> network response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation). In case the RRC procedure triggers BWP switching, the RRC procedure delay is the value defined in the following table plus the BWP switching delay defined in TS 38.133 [14], clause 8.6.3.
Figure 12.1-1: Illustration of RRC procedure delay
Table 12.1-1: UE performance requirements for RRC procedures for UEs
|
Procedure title: |
Network -> UE |
UE -> Network |
Value [ms] |
Notes |
|---|---|---|---|---|
|
RRC Connection Control Procedures |
||||
|
RRC reconfiguration (scell addition/release) |
RRCReconfiguration |
RRCReconfigurationComplete |
16 |
|
|
RRC resume (scell addition) |
RRCResume |
RRCResumeComplete |
16 |
|
8.1.5.8.2.1.3 Test description
8.1.5.8.2.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell and NR Cell 3 is the SCell.
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.5.4.
8.1.5.8.2.1.3.2 Test procedure sequence
Table 8.1.5.8.2.1.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble.
Table 8.1.5.8.2.1.3.2-1: Time instances of cell power level and parameter changes in FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
Table 8.1.5.8.2.1.3.2-2: Time instances of cell power level and parameter changes in FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
Table 8.1.5.8.2.1.3.2-3: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCReconfiguration message with sCellToAddModList to add SCell(Cell 3) |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
2 |
The SS starts transmitting a periodic DCI from (16∙2μ+1+TDL) slots after step 1 to schedule PUSCH. (Note 1, Note 2) |
||||
|
3 |
Check: Does the UE transmit an RRCReconfigurationComplete message within (16∙2μ+1+TDL+K2) slots after successful completion of step 1? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
|
4 |
The SS transmits an RRCReconfiguration message to release SCell(Cell 3) |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
5 |
UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Steps 6a1 to 6a9 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if a capability is configured |
– |
– |
– |
– |
|
6a1 |
IF pc_inactiveState THEN the SS transmits an RRCRelease message with suspendConfig. |
<– |
NR RRC: RRCRelease |
– |
– |
|
6a2 |
Wait 1s to let UE enter RRC_INACTIVE state. |
– |
– |
– |
– |
|
6a3 |
The SS transmits a Paging message including a matched ng-5G-S-TMSI. |
<– |
NR RRC: Paging |
– |
– |
|
6a4 |
The UE transmits an RRCResumeRequest message. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
6a5 |
The SS transmits an RRCResume message with sCellToAddModList to add SCell(Cell 3) |
<– |
NR RRC: RRCResume |
– |
– |
|
6a6 |
The SS starts transmitting a periodic DCI from (16∙2μ+1+TDL) slots after step 10 to schedule PUSCH. (Note 1, Note 2) |
||||
|
6a7 |
Check: Does the UE transmit an RRCResumeComplete message within (16∙2μ+1+TDL+K2) slots after successful completion of step 9? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCResumeComplete |
2 |
P |
|
6a8 |
The SS transmits an RRCReconfiguration message containing an sCellToReleaseList with SCell NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
6a9 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationtComplete |
– |
– |
|
Note 1: TDL is the delay in slots to the next available DL slot suitable for the transmission of a DCI Note 2: μ is the SCS index. μ = 0/1/2/3 for SCS = 15kHz/30kHz/60kHz/120kHz respectively. Note 3: K2 is the offset (in slots) between DCI and the PUSCH it scheduled |
|||||
8.1.5.8.2.1.3.3 Specific message contents
Table 8.1.5.8.2.1.3.3-1: RRCReconfiguration (Step 1, Table 8.1.5.8.2.1.3.2-3)
|
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 { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup |
CellGroupConfig |
Table 8.1.5.8.2.1.3.3-2 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.8.2.1.3.3-2: CellGroupConfig (Table 8.1.5.8.2.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 |
||
|
sCellConfigCommon SEQUENCE { |
|||
|
physCellId |
physCellId of Cell 3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.8.2.1.3.3-3: RRCReconfiguration (Steps 4 and 6a8, Table 8.1.5.8.2.1.3.2-3)
|
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 { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
sCellToAddModList |
Not present |
|||
|
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
|||
|
SCellIndex[1] |
SCellIndex of Cell 3 |
entry 1 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.8.2.1.3.3-4: RRCRelease (Step 6a1, Table 8.1.5.8.2.1.3.2-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-16 with Condition NR_RRC_INACTIVE |
Table 8.1.5.8.2.1.3.3-5: RRCResume (Step 6a5, Table 8.1.5.8.2.1.3.2-3)
|
Derivation Path: TS 38.508-1[4],Table 4.6.1-17 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCResume ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcResume SEQUENCE { |
||||
|
masterCellGroup |
CellGroupConfig |
Table 8.1.5.8.2.1.3.3-6 |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.8.2.1.3.3-6: CellGroupConfig (Table 8.1.5.8.2.1.3.3-5)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition SCell_Add and RESUME |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellConfigCommon SEQUENCE { |
|||
|
physCellId |
physCellId of Cell 3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.5.8.2.2 Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition / Inter-band CA
8.1.5.8.2.2.1 Test Purpose (TP)
Same as TC 8.1.5.8.2.1 but applied to Inter-band CA Test Case
8.1.5.8.2.2.2 Conformance requirements
Same as TC 8.1.5.8.2.1 but applied to Inter-band CA Test Case
8.1.5.8.2.2.3 Test description
8.1.5.8.2.2.3.1 Pre-test conditions
Same as TC 8.1.5.8.2.1 but with the following differences：
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: Cell 10 replaces Cell 3.
8.1.5.8.2.2.3.2 Test procedure sequence
Same as TC 8.1.5.8.2.1 but with the following differences：
– Cells configuration: Cell 10 replaces Cell 3.
8.1.5.8.2.2.3.3 Specific message contents
Same as TC 8.1.5.8.2.1 but with the following differences：
– Cells configuration: Cell 10 replaces Cell 3.
8.1.5.8.2.3 Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition / Intra-band non-Contiguous CA
8.1.5.8.2.3.1 Test Purpose (TP)
Same as TC 8.1.5.8.2.1 but applied to Intra-band non-Contiguous CA Test Case
8.1.5.8.2.3.2 Conformance requirements
Same as TC 8.1.5.8.2.1 but applied to Intra-band non-Contiguous CA Test Case
8.1.5.8.2.3.3 Test description
8.1.5.8.2.3.3.1 Pre-test conditions
Same as TC 8.1.5.8.2.1 but with the following differences：
- CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
8.1.5.8.2.3.3.2 Test procedure sequence
Same as TC 8.1.5.8.2.1.
8.1.5.8.2.3.3.3 Specific message contents
Same as TC 8.1.5.8.2.1.
8.1.5.9 Message Segment transfer
8.1.5.9.1 RACS / UL Message Segment transfer / UECapabilityInformation
8.1.5.9.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives UECapabilityEnquiry message with rrc-segAllowed-r16 enabled }
then { UE successfully segments UECapabilityInformation message at RRC layer and sends UlDedicatedMessageSegment messages with rrc-MessageSegmentType set accordingly for the first and last segment and rrc-MessageSegmentContainer containing the segments of UECapabilityInformation message }
}
(2)
with { UE in NR RRC_CONNECTED state and UE having received UECapabilityEnquiry message with rrc-segAllowed-r16 enabled and having transmitted the firstSegment of UECapabilityInformation message within the ULDedicatedMessageSegment message }
ensure that {
when { UE detects radio link failure on expiry of timer T310 }
then { UE successfully completes RRC re-establishment procedure and discards the remaining segments of UECapabilityInformation message }
}
8.1.5.9.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331 clause 5.6.1.3, 5.7.7.2, 5.7.7.3 and 5.3.7.2. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.6.1.3]
The UE shall set the contents of UECapabilityInformation message as follows:
1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323 [5]:
2> initiate the UL message segment transfer procedure as specified in clause 5.7.7;
1> else:
2> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends.
[TS 38.331, clause 5.7.7.2]
A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:
1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and
1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323 [5];
Upon initiating the procedure, the UE shall:
1> initiate transmission of the ULDedicatedMessageSegment message as specified in 5.7.7.3;
[TS 38.331, clause 5.7.7.3]
The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 38.323 [5]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:
1> F or each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;
1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;
1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:
2> set the rrc-MessageSegmentType to lastSegment;
1> else:
2> set the rrc-MessageSegmentType to notLastSegment;
- submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.
[TS 38.331, clause 5.3.7.2]
Upon initiation of the procedure, the UE shall:
…
1> if UE is not configured with conditionalReconfiguration:
2> reset MAC;
2> release spCellConfig, if configured;
2> suspend all RBs, except SRB0;
8.1.5.9.1.3 Test description
8.1.5.9.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
UE:
– None.
Preamble:
– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.
8.1.5.9.1.3.2 Test procedure sequence
Table 8.1.5.9.1.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
|
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
|
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
|||
Table 8.1.5.9.1.3.2-2: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
|
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-82 |
|
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2. |
|||
Table 8.1.5.9.1.3.2-3: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits a UECapabilityEnquiry message to enquire max capability and with rrc-segAllowed-r16 set to enabled. |
<– |
UECapabilityEnquiry |
– |
– |
|
– |
EXCEPTION: Steps 2a1 to 2b7 describe behaviour that depends on the size of UEs capability container; the "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message. IF UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then step 2a1 will be performed else step 2b1 to 2b7 will be performed. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 2a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the ULDedicatedMessageSegment message indicates rrc-MessageSegmentType-r16 = lastSegment. |
– |
– |
– |
– |
|
2a1 |
Check: Does the UE send segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message? NOTE: The SS shall ensure that the concatenated segments decode into a valid UECapabilityInformation message (specific capability content is not checked). |
–> |
ULDedicatedMessageSegment |
1 |
P |
|
2b1 |
Check: Does the UE send UECapabilityInformation Message? |
–> |
UECapabilityInformation |
– |
– |
|
3a1-4a13 |
Void |
– |
– |
– |
– |
|
2b2 |
The SS transmits a SET UL MESSAGE REQUEST message. |
<– |
SET UL MESSAGE REQUEST |
– |
– |
|
2b3 |
The UE transmits a SET UL MESSAGE RESPONSE message. |
–> |
SET UL MESSAGE RESPONSE |
– |
– |
|
2b4 |
The SS transmits a UECapabilityEnquiry message with rrc-segAllowed-r16 set to enabled. |
<– |
UECapabilityEnquiry |
– |
– |
|
– |
EXCEPTION: Step 2b5 is repeated a maximum of 2 times. |
– |
– |
– |
– |
|
2b5 |
Check: Does the UE send segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message? NOTE: The SS shall ensure that the concatenated segments decode into a valid UECapabilityInformation message (specific capability content is not checked). |
–> |
ULDedicatedMessageSegment |
1 |
P |
|
2b6 |
The SS transmits a SET UL MESSAGE REQUEST message. |
<– |
SET UL MESSAGE REQUEST |
– |
– |
|
2b7 |
The UE transmits a SET UL MESSAGE RESPONSE message. |
–> |
SET UL MESSAGE RESPONSE |
– |
– |
|
3 |
SS stops regular grant transmission upon scheduling request. |
– |
– |
– |
– |
|
4 |
The SS transmits a UECapabilityEnquiry message to enquire max capability and with rrc-segAllowed-r16 set to enabled. |
<– |
UECapabilityEnquiry |
– |
– |
|
5 |
The SS transmits periodic grant from (80∙2μ+1+TDL) slots after step 4 to schedule PUSCH till the ULDedicatedMessageSegment at step 6 is received. (Note 1, Note 2) |
– |
– |
– |
– |
|
6 |
The UE sends 1st segment of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message. |
–> |
ULDedicatedMessageSegment |
– |
– |
|
7 |
The SS changes NR Cell 1 parameters according to the row "T1" in table 8.1.5.9.1.3.2-1/2 in order that the radio link quality of NR Cell 1 is degraded. |
– |
– |
– |
– |
|
8 |
Wait for T310 to expire |
– |
– |
– |
– |
|
9 |
The SS changes NR Cell 1 parameters according to the row "T2" in table 8.1.5.9.1.3.2-1/2. |
– |
– |
– |
– |
|
10 |
The UE sends an RRCReestablishmentRequest message on NR Cell 1. |
–> |
RRCReestablishmentRequest |
– |
– |
|
11 |
The SS transmits an RRCReestablishment message to resume SRB1 operation on NR Cell 1. |
<– |
RRCReestablishment |
– |
– |
|
12 |
The UE transmits an RRCReestablishmentComplete message on NR Cell 1? |
–> |
RRCReestablishmentComplete |
– |
– |
|
13 |
SS resumes regular UL grant transmission. |
– |
– |
– |
– |
|
14 |
Check: Upon successful completion of RRC re-establishment procedure, does the UE discards remaining segments of UECapabilityInformation message and does not send any ULDedicatedMessageSegment message in the next 5 seconds? |
– |
– |
2 |
P |
|
Note 1: TDL is the delay in slots to the next available DL slot suitable for the transmission of a DCI. Note 2: μ is the SCS index. μ = 0/1/2/3 for SCS = 15kHz/30kHz/60kHz/120kHz respectively. |
|||||
8.1.5.9.1.3.3 Specific message contents
Table 8.1.5.9.1.3.3-0: CellGroupConfig (preamble)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
rlf-TimersAndConstants SEQUENCE { |
|||
|
t311-v1530 |
ms10000 |
||
|
} |
|||
|
} |
|||
Table 8.1.5.9.1.3.3-1: UECapabilityEnquiry (step 1, 2b4 and step 4, Table 8.1.5.9.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-31 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UECapabilityEnquiry ::= SEQUENCE { |
|||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
||
|
criticalExtensions CHOICE { |
|||
|
ueCapabilityEnquiry SEQUENCE { |
|||
|
ue-CapabilityRAT-RequestList SEQUENCE (SIZE (1.. maxRAT-CapabilityContainers)) OF UE-CapabilityRAT-Request { |
2 entries |
||
|
UE-CapabilityRAT-Request[1] SEQUENCE { |
entry 1 |
||
|
rat-Type |
nr |
||
|
capabilityRequestFilter |
UE-CapabilityRequestFilterNR |
OCTET STRING (CONTAINING UE-CapabilityRequestFilterNR) |
|
|
} |
|||
|
UE-CapabilityRAT-Request[2] SEQUENCE { |
entry 2 |
||
|
rat-Type |
eutra-nr |
||
|
capabilityRequestFilter |
UE-CapabilityRequestFilterNR |
OCTET STRING (CONTAINING UE-CapabilityRequestFilterNR) |
|
|
} |
|||
|
} |
|||
|
lateNonCriticalExtension |
Not present |
||
|
ue-CapabilityEnquiryExt |
OCTET STRING Containing UECapabilityEnquiry-v1560-IEs |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.9.1.3.3-2: UE-CapabilityRequestFilterNR (Table 8.1.5.9.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-47 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UE-CapabilityRequestFilterNR ::= SEQUENCE { |
|||
|
frequencyBandListFilter |
FreqBandList |
||
|
nonCriticalExtension SEQUENCE { |
Not present |
||
|
srs-SwitchingTimeRequest |
Not present |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
srs-SwitchingTimeRequest |
Not present |
||
|
nonCriticalExtension |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.9.1.3.3-3: FreqBandList (Table 8.1.5.9.1.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.4-21 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
FreqBandList::= SEQUENCE (SIZE (1..maxBandsMRDC)) OF FreqBandInformation { |
43 entries |
FreqBandIndicatorNR = n1, n2, n3, n5, n7, n8, n12, n14, n20, n25, n26, n28, n29, n30, n34, n38, n39, n40, n41, n48, n50, n51, n53, n65, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261. |
|
|
FreqBandInformation[n] CHOICE { |
entry n |
||
|
bandInformationNR SEQUENCE { |
|||
|
bandNR |
FreqBandIndicatorNR |
||
|
maxBandwidthRequestedDL |
Not present |
||
|
maxBandwidthRequestedUL |
Not present |
||
|
maxCarriersRequestedDL |
Not present |
||
|
maxCarriersRequestedUL |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.9.1.3.3-4: UECapabilityEnquiry-v1560-IEs (Table 8.1.5.9.1.3.3-1)
|
Information Element |
Value/remark |
Comment |
Condition |
|
UECapabilityEnquiry-v1560-IEs ::= SEQUENCE { |
|||
|
capabilityRequestFilterCommon |
Not present |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
rrc-SegAllowed-r16 |
enabled |
||
|
nonCriticalExtension |
Not present |
||
|
} |
|||
|
} |
Table 8.1.5.9.1.3.3-5: ULDedicatedMessageSegment (step 2a1, 2b5 and step 6, Table 8.1.5.9.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-32C |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ULDedicatedMessageSegment-r16 ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
segmentNumber-r16 |
0 for first segment, and incremented by 1 for each subsequent segment |
||
|
rrc-MessageSegmentContainer-r16 |
Not Checked |
OCTET STRING Includes a segment of the encoded UL DCCH message. The size of the included segment in this container should be small enough so the resulting encoded RRC message PDU is less than or equal to the PDCP SDU size limit |
|
|
rrc-MessageSegmentType-r16 |
notLastSegment for all segments except the last segment. lastSegment for the last segment |
||
|
lateNonCriticalExtension |
Not present |
||
|
nonCriticalExtension |
Not present |
||
|
} |
|||
|
} |
|||
8.1.5.9.2 RRC reconfiguration / DL segment transfer
8.1.5.9.2.1 Test Purpose (TP)
(1)
with { UE having completed the RRC connection establishment procedure}
ensure that {
when { SS initiates the DL Dedicated Message Segment transfer procedure to send an RRCReconfiguration message to establish a DRB and SRB2}
then { UE successfully completes the reconfiguration }
}
(2)
with { UE in NR RRC_CONNECTED state with SRB2 and has previously received the first and second segment of an RRCReconfiguration message including SRB2 configuration }
ensure that {
when { SS releases the RRC connection }
then { UE discards all segments }
}
8.1.5.9.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.3.11 and 5.7.6.3. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.3.11]
The UE shall:
…
1> discard any segments of segmented RRC messages stored according to 5.7.6.3;
[TS 38.331, clause 5.7.6.3]
Upon receiving DLDedicatedMessageSegment message, the UE shall:
1> store the segment included in rrc-MessageSegmentContainer;
1> if all segments of the message have been received:
2> assemble the message from the received segments and process the message according to 5.3.5.3 for the RRCReconfiguration message or 5.3.13.4 for the RRCResume message;
2> discard all segments.
8.1.5.9.2.3 Test description
8.1.5.9.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
UE:
– None
Preamble:
– If pc_IP_Ping is set to TRUE then the UE is in 5GS state 1N-A, PDU SESSION ACTIVE according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1
– Else, the UE is in 5GS state 1N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.5.9.2.3.2 Test procedure sequence
Table 8.1.5.9.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordList. |
<– |
NR RRC: Paging |
– |
– |
|
2 |
UE transmits an RRCSetupRequest message. |
–> |
NR RRC: RRCSetupRequest |
– |
– |
|
3 |
SS transmits an RRCSetup message |
<– |
NR RRC: RRCSetup |
– |
– |
|
4 |
The UE transmits an RRCSetupComplete to confirm the successful completion of the connection establishment. |
–> |
NR RRC: RRCSetupComplete |
– |
– |
|
5 |
SS transmits a SecurityModeCommand message to activate AS security. |
<– |
NR RRC: SecurityModeCommand |
– |
– |
|
6 |
Using the same slot as the SecurityModeCommand message in step 5, the SS transmits an DLDedicatedMessageSegment containing the first segment of the RRCReconfiguration message to establish a data radio bearer, DRB1 and signalling radio bearer, SRB2. |
<– |
NR RRC: DLDedicatedMessageSegment |
– |
– |
|
7 |
The UE transmits a SecurityModeComplete message. |
–> |
NR RRC: SecurityModeComplete |
– |
– |
|
8 |
The SS transmits a DLDedicatedMessageSegment containing the second(last) segment of the RRCReconfiguration message. |
<– |
NR RRC: DLDedicatedMessageSegment |
– |
– |
|
9 |
Check: Does the UE transmit an RRCReconfigurationComplete message to confirm the establishment of data radio bearer, DRB1 and signalling radio bearer, SRB2? |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
|
10 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB#1 established in Step 8? |
– |
– |
1 |
– |
|
11 |
The SS transmits a DLDedicatedMessageSegment containing the first segment of the RRCReconfiguration message to modify SRB and DRB configuration. |
<– |
NR RRC: DLDedicatedMessageSegment |
||
|
12 |
The SS transmits the second segment of the RRCReconfiguration message to modify SRB and DRB configuration. |
<– |
NR RRC: DLDedicatedMessageSegment |
– |
– |
|
13 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
14 |
Step 1-8 of generic test procedure in TS 38.508-1 [4] subclause 4.5.4 to bring the UE in RRC_CONNECTED mode. |
– |
– |
– |
– |
|
15 |
The SS transmits the third(last) segment of the RRCReconfiguration message to modify SRB2 and DRB configuration. |
<– |
NR RRC: DLDedicatedMessageSegment |
– |
– |
|
16 |
Check: Does the UE transmit an RRCReconfigurationComplete message in the next 3s? |
–> |
NR RRC: RRCReconfigurationComplete |
2 |
F |
|
17 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
18 |
Step 1-8 of generic test procedure in TS 38.508-1 [4] subclause 4.5.4 to bring the UE in RRC_CONNECTED mode. |
– |
– |
– |
– |
|
19 |
The SS transmits a DLDedicatedMessageSegment containing the first segment of the RRCReconfiguration message to modify SRB and DRB configuration. |
NR RRC: DLDedicatedMessageSegment |
|||
|
20 |
The SS transmits the second segment of the RRCReconfiguration message to modify SRB and DRB configuration. |
<– |
NR RRC: DLDedicatedMessageSegment |
– |
– |
|
21 |
The SS transmits the third(last) segment of the RRCReconfiguration message to modify SRB2 and DRB configuration. |
<– |
NR RRC: DLDedicatedMessageSegment |
– |
– |
|
22 |
Check: Does the UE transmit an RRCReconfigurationComplete message in the next 3s? |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
|
23 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB#1 established in Steps 12-21? |
– |
– |
1 |
|
|
24 |
The SS transmits an OPEN UE TEST LOOP Message. |
<– |
OPEN UE TEST LOOP |
– |
– |
|
25 |
The UE transmits an OPEN UE TEST LOOP COMPLETE Message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
26 |
The SS transmits DEACTIVATE TEST MODE message. |
<– |
DEACTIVATE TEST MODE |
– |
– |
|
27 |
The UE transmits DEACTIVATE TEST MODE COMPLETE message. |
–> |
DEACTIVATE TEST MODE COMPLETE |
– |
– |
|
NOTE 1: The request to establish a PDU session may be performed by MMI or AT Command. |
|||||
8.1.5.9.2.3.3 Specific message contents
Table 8.1.5.9.2.3.3-1: DLDedicatedMessageSegment (Step 6, 8, 11, 12, 15, 19, 20 and 21, Table 8.1.5.9.2.3.2-1)
|
Derivation Path: TS 38.508-1[4], table 4.6.1-2B |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
DLDedicatedMessageSegment-r16 ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
dlDedicatedMessageSegment-r16 SEQUENCE { |
||||
|
segmentNumber-r16 |
0 |
Step 6, Step 11, Step 19 |
||
|
segmentNumber-r16 |
1 |
Step 8, Step 12, Step 20 |
||
|
segmentNumber-r16 |
2 |
Step 15, Step 21 |
||
|
rrc-MessageSegmentContainer-r16 |
OCTET STRING (CONTAINING First segment of the RRCReconfiguration message) |
Table 8.1.5.9.2.3.3-2 |
Step 6 |
|
|
rrc-MessageSegmentContainer-r16 |
OCTET STRING (CONTAINING Last segment of the RRCReconfiguration message) |
Table 8.1.5.9.2.3.3-2 |
Step 8 |
|
|
rrc-MessageSegmentContainer-r16 |
OCTET STRING (CONTAINING First segment of the RRCReconfiguration message) |
Table 8.1.5.9.2.3.3-4 |
Step 11, Step 19 |
|
|
rrc-MessageSegmentContainer-r16 |
OCTET STRING (CONTAINING Second segment of the RRCReconfiguration message) |
Table 8.1.5.9.2.3.3-4 |
Step 12, Step 20 |
|
|
rrc-MessageSegmentContainer-r16 |
OCTET STRING (CONTAINING Last (third) segment of the RRCReconfiguration message) |
Table 8.1.5.9.2.3.3-4 |
Step 15, Step 21 |
|
|
rrc-MessageSegmentType-r16 |
notLastSegment |
Step 6, Step 11, Step 19, Step 12, Step 20 |
||
|
rrc-MessageSegmentType-r16 |
LastSegment |
Step 8, Step 15, Step 21 |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.9.2.3.3-2: RRCReconfiguration (Step 6 and 8, Table 8.1.5.9.2.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 { |
||||
|
radioBearerConfig |
RadioBearerConfig with conditions SRB2 and DRB1 |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig Table 8.1.5.9.2.3.3-3) |
||
|
lateNonCriticalExtension |
’00,,,00’O |
Add enough padding so that: maximum PDCP SDU size < encoded DLDedicatedMessageSegment size < 2 x maximum PDCP SDU size |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.9.2.3.3-3: CellGroupConfig (Table 8.1.5.9.2.3.3-2)
|
Derivation Path: TS 38.508-1[4], table 4.6.3-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CellGroupConfig ::= SEQUENCE { |
||||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig { |
2 entries |
|||
|
RLC-Bearer-Config[1] SEQUENCE { |
entry 1 |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity |
|||
|
servedRadioBearer CHOICE { |
||||
|
drb-Identity |
DRB-Identity with condition DRB1 |
|||
|
} |
||||
|
reestablishRLC |
Not present |
|||
|
RLC-Config |
RLC-Config with condition AM according to 38.508-1 [4], table 4.6.3-149 |
|||
|
mac-LogicalChannelConfig |
LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66 |
|||
|
} |
||||
|
RLC-Bearer-Config[2] SEQUENCE { |
entry 2 |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity |
|||
|
servedRadioBearer CHOICE { |
||||
|
srb-Identity |
SRB-Identity with condition SRB2 |
|||
|
} |
||||
|
reestablishRLC |
Not present |
|||
|
RLC-Config |
Not present |
|||
|
mac-LogicalChannelConfig |
LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66 |
|||
|
} |
||||
|
} |
||||
|
mac-CellGroupConfig |
Not present |
|||
|
physicalCellGroupConfig |
Not present |
|||
|
spCellConfig SEQUENCE |
Not present |
|||
|
} |
||||
Table 8.1.5.9.2.3.3-4: RRCReconfiguration (Step 11, 12, 15, 19, 20 and 21, Table 8.1.5.9.2.3.2-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 { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig Table 8.1.5.9.2.3.3-5) |
||
|
} |
||||
|
lateNonCriticalExtension |
’00,,,00’O |
Add enough padding so that the size of the encoded DLDedicatedMessageSegment = 3 x maximum PDCP SDU size |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.9.2.3.3-5: CellGroupConfig (Table 8.1.5.9.2.3.3-3)
|
Derivation Path: TS 38.508-1, table 4.6.3-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CellGroupConfig ::= SEQUENCE { |
||||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig { |
2 entries |
|||
|
RLC-Bearer-Config[1] SEQUENCE { |
entry 1 |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity |
|||
|
servedRadioBearer CHOICE { |
||||
|
srb-Identity |
SRB-Identity with condition SRB2 |
|||
|
} |
||||
|
reestablishRLC |
true |
|||
|
RLC-Config |
RLC-Config with condition AM according to 38.508-1 [4], table 4.6.3-149 |
|||
|
mac-LogicalChannelConfig |
LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66 |
|||
|
} |
||||
|
RLC-Bearer-Config[2] SEQUENCE { |
entry 2 |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity |
|||
|
servedRadioBearer CHOICE { |
||||
|
drb-Identity |
DRB-Identity with condition DRB1 |
|||
|
} |
||||
|
reestablishRLC |
true |
|||
|
RLC-Config |
Not present |
|||
|
mac-LogicalChannelConfig |
LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66 |
|||
|
} |
||||
|
} |
||||
|
mac-CellGroupConfig |
Not present |
|||
|
physicalCellGroupConfig |
Not present |
|||
|
spCellConfig SEQUENCE |
Not present |
|||
|
} |
||||
8.1.5.10 UE Assistance Information
8.1.5.10.1 UE Assistance Information/ Release Preference
8.1.5.10.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE configured to provide its release preference and a Preferred RRC State is provided (UE determines that it would prefer to transition out of RRC_CONNECTED) and timer T346f is not running }
then { the UE transmits a UEAssistanceInformation message }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE configured to provide its release preference and a Preferred RRC State is provided (UE determines that it would prefer to transition out of RRC_CONNECTED) and timer T346f is running }
then { the UE does not transmit a UEAssistanceInformation message }
}
(3)
with { UE in NR RRC_CONNECTED state and is configured with connectedReporting and having transmitted a UEAssistanceInformation message to indicate preference to transition out of RRC_CONNECTED state }
ensure that {
when { UE determines that it would prefer to remain in RRC_CONNECTED state and timer T346f is not running }
then { the UE transmits a UEAssistanceInformation message }
}
8.1.5.10.1.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.5.9, 5.7.4.2 and 5.7.4.3. Unless state explicitly these are Rel-16 requirements.
[TS 38.331, clause 5.3.5.9]
The UE shall:
…
1> if the received otherConfig includes the releasePreferenceConfig:
2> if releasePreferenceConfig is set to setup:
3> consider itself to be configured to provide assistance information to transition out of RRC_CONNECTED in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide assistance information to transition out of RRC_CONNECTED and stop timer T346f, if running.
[TS 38.331, clause 5.7.4.2]
A UE capable of providing assistance information to transition out of RRC_CONNECTED state may initiate the procedure if it was configured to do so, upon determining that it prefers to transition out of RRC_CONNECTED state, or upon change of its preferred RRC state.
…
Upon initiating the procedure, the UE shall:
1> if configured to provide its release preference and timer T346f is not running:
2> if the UE determines that it would prefer to transition out of RRC_CONNECTED state; or
2> if the UE is configured with connectedReporting and the UE determines that it would prefer to revert an earlier indication to transition out of RRC_CONNECTED state:
3> start timer T346f with the timer value set to the releasePreferenceProhibitTimer;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the release preference;
[TS 38.331, clause 5.7.4.3]
The UE shall set the contents of the UEAssistanceInformation message as follows:
…
1> if transmission of the UEAssistanceInformation message is initiated to provide a release preference according to 5.7.4.2 or 5.3.5.3:
2> include releasePreference in the UEAssistanceInformation message;
2> set preferredRRC-State to the desired RRC state on transmission of the UEAssistanceInformation message;
8.1.5.10.1.3 Test Description
8.1.5.10.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used for NR cell 1.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
8.1.5.10.1.3.2 Test procedure sequence
Table 8.1.5.10.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCReconfiguration message to configure releasePreferenceConfig with releasePreferenceProhibitTimer IE. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
2 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
3 |
The SS transmits an SET UAI REQUEST message indicating Preferred RRC State = ‘idle’. |
<– |
SET UAI REQUEST |
– |
– |
|
– |
EXCEPTION: Step 4 and 5 can be performed in any order. |
– |
– |
– |
– |
|
4 |
The UE transmits an SET UAI RESPONSE message. |
–> |
SET UAI RESPONSE |
– |
– |
|
5 |
Check: Does the UE transmits an UEAssistanceInformation message to indicate IE preferredRRC-State-r16 = ‘idle’ within the ReleasePreference-r16 IE? |
–> |
NR RRC: UEAssistanceInformation |
1 |
P |
|
6 |
SS starts timer T346f = 30s. |
– |
– |
– |
– |
|
7 |
The SS transmits an SET UAI REQUEST message indicating Preferred RRC State = ‘inactive’. |
<– |
SET UAI REQUEST |
– |
– |
|
8 |
The UE transmits an SET UAI RESPONSE message. |
–> |
SET UAI RESPONSE |
– |
– |
|
9 |
Check: Does the UE transmit an UEAssistanceInformation message to indicate IE preferredRRC-State-r16 = ‘inactive’ within the ReleasePreference-r16 IE? |
–> |
NR RRC: UEAssistanceInformation |
2 |
F |
|
10 |
SS waits for timer T346f expiry. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 10a may be performed if the UE cached the preferredRRC-State indication from upper layers. |
||||
|
10a |
The UE transmit an UEAssistanceInformation message to indicate IE preferredRRC-State-r16 = ‘inactive’ within the ReleasePreference-r16 IE. |
–> |
NR RRC: UEAssistanceInformation |
– |
– |
|
11 |
The SS transmits an SET UAI REQUEST message indicating Preferred RRC State = connected. |
<– |
SET UAI REQUEST |
– |
– |
|
12 |
The UE transmits an SET UAI RESPONSE message. |
–> |
SET UAI RESPONSE |
– |
– |
|
13 |
Check: Does the UE transmits an UEAssistanceInformation message to indicate IE preferredRRC-State-r16 = ‘connected’ within the ReleasePreference-r16 IE? |
–> |
NR RRC: UEAssistanceInformation |
3 |
F |
|
14 |
The SS transmits an RRCReconfiguration message to configure releasePreferenceConfig with connectedReporting. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
15 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
16 |
The SS transmits an SET UAI REQUEST message indicating Preferred RRC State = ‘connected’. |
<– |
SET UAI REQUEST |
– |
– |
|
– |
EXCEPTION: Step 18 and 19 can be performed in any order. |
– |
– |
– |
– |
|
17 |
The UE transmits an SET UAI RESPONSE message. |
–> |
SET UAI RESPONSE |
– |
– |
|
18 |
Check: Does the UE transmits an UEAssistanceInformation message to indicate IE preferredRRC-State-r16 = ‘connected’ within the ReleasePreference-r16? |
–> |
NR RRC: UEAssistanceInformation |
3 |
P |
8.1.5.10.1.3.3 Specific message contents
Table 8.1.5.10.1.3.3-1: RRCReconfiguration (step 1, Table 8.1.5.10.1.3.2-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 { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
otherConfig-v1610 SEQUENCE { |
|||
|
releasePreferenceConfig-r16 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
releasePreferenceProhibitTimer-r16 |
s30 |
||
|
connectedReporting |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.10.1.3.3-2: UEAssistanceInformation (Step 5, step 10a and step 18, Table 8.1.5.10.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.1-30 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
UEAssistanceInformation ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
ueAssistanceInformation SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
releasePreference-r16 SEQUENCE { |
||||
|
preferredRRC-State-r16 |
idle |
Step 5 |
||
|
inactive |
Step 10a |
|||
|
connected |
Step 18 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.5.10.1.3.3-3: RRCReconfiguration (step 14, Table 8.1.5.10.1.3.2-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 { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
otherConfig-v1610 SEQUENCE { |
|||
|
releasePreferenceConfig-r16 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
releasePreferenceProhibitTimer-r16 |
s30 |
||
|
connectedReporting |
true |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.5.11 Idle/Inactive measurements
8.1.5.11.1 Idle/Inactive measurements / Idle mode / SIB11 configuration / Measurement of NR cells
8.1.5.11.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and SIB11 including measIdleCarrierListNR with ssb-MeasConfig }
then { UE enters RRC_IDLE state, performs cell measurements and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig, SIB11 including measIdleCarrierListNR without ssb-MeasConfig and ssb-MeasConfig parameters derived from SIB4 }
then { UE enters RRC_IDLE state, performs cell measurements and reports measurement results in RRC_CONNECTED state }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig, SIB11 including measIdleCarrierListNR without ssb-MeasConfig and ssb-MeasConfig parameters derived from SIB4 and T331 expires }
then { UE enters RRC_IDLE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(4)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and SIB11 does not include measIdleCarrierListNR }
then { UE enters RRC_IDLE state, UE does not report measurement results in RRC_CONNECTED state }
}
8.1.5.11.1.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.2.3.
[TS 38.331, clause 5.7.8.1]
This procedure specifies the measurements to be performed and stored by a UE in RRC_IDLE and RRC_INACTIVE when it has an idle/inactive measurement configuration.
[TS 38.331, clause 5.7.8.1a]
The purpose of this procedure is to update the idle/inactive measurement configuration.
The UE initiates this procedure while T331 is running and one of the following conditions is met:
1> upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or
1> upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection;
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> if VarMeasIdleConfig includes neither a measIdleCarrierListEUTRA nor a measIdleCarrierListNR received from the RRCRelease message:
2> if the UE supports idleInactiveNR-MeasReport:
3> if SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListNR:
4> store or replace the measIdleCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasIdleConfig;
3> else:
4> remove the measIdleCarrierListNR in VarMeasIdleConfig, if stored;
1> for each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message:
2> if there is an entry in measIdleCarrierListNR in measIdleConfigSIB of SIB11 that has the same carrier frequency and subcarrier spacing as the entry in the measIdleCarrierListNR within VarMeasIdleConfig and that contains ssb-MeasConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB11 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else if there is an entry in interFreqCarrierFreqList of SIB4 with the same carrier frequency and subcarrier spacing as the entry in measIdleCarrierListNR within VarMeasIdleConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB4 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else:
3> remove the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig, if stored;
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [9].
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if the VarMeasIdleConfig includes the measIdleCarrierListNR and the SIB1 contains idleModeMeasurementsNR:
3> for each entry in measIdleCarrierListNR within VarMeasIdleConfig that contains ssb-MeasConfig:
4> if UE supports carrier aggregation or NR-DC between serving carrier and the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry:
5> perform measurements in the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry;
5> if the reportQuantities is set to rsrq:
6> consider RSRQ as the cell sorting quantity;
5> else:
6> consider RSRP as the cell sorting quantity;
5> if the measCellListNR is included:
6> consider cells identified by each entry within the measCellListNR to be applicable for idle/inactive measurement reporting;
5> else:
6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;
5> for all cells applicable for idle/inactive measurement reporting, derive cell measurement results for the measurement quantities indicated by reportQuantities;
5> store the derived cell measurement results as indicated by reportQuantities for cells applicable for idle/inactive measurement reporting within measResultsPerCarrierListIdleNR in the measReportIdleNR in VarMeasIdleReport in decreasing order of the cell sorting quantity, i.e. the best cell is included first, as follows:
6> if qualityThreshold is configured:
7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold;
6> else:
7> include the measurement results from all cells applicable for idle/inactive measurement reporting;
5> if beamMeasConfigIdle is included in the associated entry in measIdleCarrierListNR and if UE supports idleInactiveNR-MeasBeamReport for the FR of the carrier frequency indicated by carrierFreq within the associated entry, for each cell in the measurement results:
6> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215 [9];
6> if the reportQuantityRS-Indexes is set to rsrq:
7> consider RSRQ as the beam sorting quantity;
6> else:
7> consider RSRP as the beam sorting quantity;
6> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:
7> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;
6> if the includeBeamMeasurements is set to true:
7> include the beam measurement results as indicated by reportQuantityRS–Indexes;
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
3> if the VarMeasIdleConfig includes the measIdleCarrierListNR and it contains an entry with carrierFreq set to the value of the serving frequency:
4> if beamMeasConfigIdle is included in that entry, and if the UE supports idleInactiveNR- MeasBeamReport for the FR of the serving cell:
5> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215 [9];
5> if the reportQuantityRS-Indexes is set to rsrq:
6> consider RSRQ as the beam sorting quantity;
5> else:
6> consider RSRP as the beam sorting quantity;
5> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:
6> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included in SIB2 of serving cell, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;
5> if the includeBeamMeasurements is set to true:
6> include the beam measurement results as indicated by reportQuantityRS-Indexes;
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
[TS 38.331, clause 5.7.8.3]
The UE shall:
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.10.3]
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:
2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;
8.1.5.11.1.3 Test Description
8.1.5.11.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
– NR Cell 3, suitable for inter-frequency measurements
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.1.5.11.1.3.2 Test procedure sequence
Table 8.1.5.11.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
3-10 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
11 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
12 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
1 |
P |
|
13 |
The SS removes ssb-MeasConfig in SIB11. |
– |
– |
– |
– |
|
14 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
15 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
16 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
17 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
18-25 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
26 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
27 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
2 |
P |
|
28 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
29 |
Wait for 11 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
30-37 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
38 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
39 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
3 |
F |
|
40 |
The SS removes measIdleCarrierListNR in SIB11. |
– |
– |
– |
– |
|
41 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
42 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
43 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
44 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
45-52 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
53 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
54 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
4 |
F |
8.1.5.11.1.3.3 Specific message contents
TBD
8.1.5.11.2 Void
8.1.5.11.2 Idle/Inactive measurements / Idle mode / RRCRelease configuration / Measurement of NR cells
8.1.5.11.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig with ssb-MeasConfig }
then { UE enters RRC_IDLE state, performs cell measurements and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig, ssb-MeasConfig from SIB11 }
then { UE enters RRC_IDLE state, performs cell measurements and reports measurement results }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig, ssb-MeasConfig parameters derived from SIB4 }
then { UE enters RRC_IDLE state, performs cell measurements and reports measurement results }
}
(4)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig with ssb-MeasConfig, T331 expires }
then { UE enters RRC_IDLE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(5)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig without measIdleCarrierListNR }
then { UE does not report measurement results }
}
8.1.5.11.2.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3, 5.7.8 and 5.7.10.3.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
[TS 38.331, clause 5.7.8.1]
This procedure specifies the measurements to be performed and stored by a UE in RRC_IDLE and RRC_INACTIVE when it has an idle/inactive measurement configuration.
[TS 38.331, clause 5.7.8.1a]
The purpose of this procedure is to update the idle/inactive measurement configuration.
The UE initiates this procedure while T331 is running and one of the following conditions is met:
1> upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or
1> upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection;
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> for each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message:
2> if there is an entry in measIdleCarrierListNR in measIdleConfigSIB of SIB11 that has the same carrier frequency and subcarrier spacing as the entry in the measIdleCarrierListNR within VarMeasIdleConfig and that contains ssb-MeasConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB11 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else if there is an entry in interFreqCarrierFreqList of SIB4 with the same carrier frequency and subcarrier spacing as the entry in measIdleCarrierListNR within VarMeasIdleConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB4 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else:
3> remove the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig, if stored;
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [9].
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if the VarMeasIdleConfig includes the measIdleCarrierListNR and the SIB1 contains idleModeMeasurementsNR:
3> for each entry in measIdleCarrierListNR within VarMeasIdleConfig that contains ssb-MeasConfig:
4> if UE supports carrier aggregation or NR-DC between serving carrier and the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry:
5> perform measurements in the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry;
5> if the reportQuantities is set to rsrq:
6> consider RSRQ as the cell sorting quantity;
5> else:
6> consider RSRP as the cell sorting quantity;
5> if the measCellListNR is included:
6> consider cells identified by each entry within the measCellListNR to be applicable for idle/inactive measurement reporting;
5> else:
6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;
5> for all cells applicable for idle/inactive measurement reporting, derive cell measurement results for the measurement quantities indicated by reportQuantities;
5> store the derived cell measurement results as indicated by reportQuantities for cells applicable for idle/inactive measurement reporting within measResultsPerCarrierListIdleNR in the measReportIdleNR in VarMeasIdleReport in decreasing order of the cell sorting quantity, i.e. the best cell is included first, as follows:
6> if qualityThreshold is configured:
7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold;
6> else:
7> include the measurement results from all cells applicable for idle/inactive measurement reporting;
5> if beamMeasConfigIdle is included in the associated entry in measIdleCarrierListNR and if UE supports idleInactiveNR-MeasBeamReport for the FR of the carrier frequency indicated by carrierFreq within the associated entry, for each cell in the measurement results:
6> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215 [9];
6> if the reportQuantityRS-Indexes is set to rsrq:
7> consider RSRQ as the beam sorting quantity;
6> else:
7> consider RSRP as the beam sorting quantity;
6> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:
7> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;
6> if the includeBeamMeasurements is set to true:
7> include the beam measurement results as indicated by reportQuantityRS–Indexes;
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
3> if the VarMeasIdleConfig includes the measIdleCarrierListNR and it contains an entry with carrierFreq set to the value of the serving frequency:
4> if beamMeasConfigIdle is included in that entry, and if the UE supports idleInactiveNR- MeasBeamReport for the FR of the serving cell:
5> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215 [9];
5> if the reportQuantityRS-Indexes is set to rsrq:
6> consider RSRQ as the beam sorting quantity;
5> else:
6> consider RSRP as the beam sorting quantity;
5> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:
6> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included in SIB2 of serving cell, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;
5> if the includeBeamMeasurements is set to true:
6> include the beam measurement results as indicated by reportQuantityRS-Indexes;
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
[TS 38.331, clause 5.7.8.3]
The UE shall:
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.10.3]
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:
2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;
8.1.5.11.2.3 Test Description
8.1.5.11.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
– NR Cell 3, suitable for inter-frequency measurements
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.1.5.11.2.3.2 Test procedure sequence
Table 8.1.5.11.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message with measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
3-10 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
11 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
12 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
1 |
P |
|
13 |
The SS transmits RRCRelease message with measIdleConfig not including ssb-MeasConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
14 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
15-22 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
23 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
24 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
2 |
P |
|
25 |
The SS removes measIdleCarrierListNR in SIB11. |
– |
– |
– |
– |
|
26 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
27 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
28 |
The SS transmits RRCRelease message with measIdleConfig not including ssb-MeasConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
29 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
30-37 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
38 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
39 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
3 |
P |
|
40 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
41 |
Wait for 11 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
42-49 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
50 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
51 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
4 |
F |
|
52 |
The SS transmits RRCRelease message with measIdleConfig not including measIdleCarrierListNR to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
53 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
54-61 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
62 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
63 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
5 |
F |
8.1.5.11.2.3.3 Specific message contents
TBD
8.1.5.11.3 Idle/Inactive measurements / Inactive mode / SIB11 configuration / Measurement of NR cells
8.1.5.11.3.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, SIB11 including measIdleCarrierListNR with ssb-MeasConfig }
then { UE enters RRC_INACTIVE state, performs cell measurements and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, SIB11 including measIdleCarrierListNR without ssb-MeasConfig and ssb-MeasConfig parameters derived from SIB4 }
then { UE enters RRC_INACTIVE state, performs cell measurements and reports measurement results in RRC_CONNECTED state }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, SIB11 including measIdleCarrierListNR without ssb-MeasConfig, ssb-MeasConfig parameters derived from SIB4 and T331 expires }
then { UE enters RRC_INACTIVE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(4)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, SIB11 does not include measIdleCarrierListNR }
then { UE enters RRC_INACTIVE state, UE does not report measurement results in RRC_CONNECTED state }
}
8.1.5.11.3.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3, 5.7.8 and 5.7.10.3. Unless otherwise stated, these are Rel-16 requirements.
[TS 38.331, clause 5.3.8.3]
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
3> if the measIdleConfig contains measIdleCarrierListNR:
4> store the received measIdleCarrierListNR in VarMeasIdleConfig;
[TS 38.331, clause 5.7.8.1a]
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> if VarMeasIdleConfig includes neither a measIdleCarrierListEUTRA nor a measIdleCarrierListNR received from the RRCRelease message:
2> if the UE supports idleInactiveNR-MeasReport:
3> if SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListNR:
4> store or replace the measIdleCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasIdleConfig;
3> else:
4> remove the measIdleCarrierListNR in VarMeasIdleConfig, if stored;
1> for each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message:
2> if there is an entry in measIdleCarrierListNR in measIdleConfigSIB of SIB11 that has the same carrier frequency and subcarrier spacing as the entry in the measIdleCarrierListNR within VarMeasIdleConfig and that contains ssb-MeasConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB11 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else if there is an entry in interFreqCarrierFreqList of SIB4 with the same carrier frequency and subcarrier spacing as the entry in measIdleCarrierListNR within VarMeasIdleConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB4 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else:
3> remove the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig, if stored;
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if the VarMeasIdleConfig includes the measIdleCarrierListNR and the SIB1 contains idleModeMeasurementsNR:
3> for each entry in measIdleCarrierListNR within VarMeasIdleConfig that contains ssb-MeasConfig:
4> if UE supports carrier aggregation or NR-DC between serving carrier and the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry:
5> perform measurements in the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry;
5> if the reportQuantities is set to rsrq:
6> consider RSRQ as the cell sorting quantity;
5> else:
6> consider RSRP as the cell sorting quantity;
5> if the measCellListNR is included:
6> consider cells identified by each entry within the measCellListNR to be applicable for idle/inactive measurement reporting;
5> else:
6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;
5> for all cells applicable for idle/inactive measurement reporting, derive cell measurement results for the measurement quantities indicated by reportQuantities;
5> store the derived cell measurement results as indicated by reportQuantities for cells applicable for idle/inactive measurement reporting within measResultsPerCarrierListIdleNR in the measReportIdleNR in VarMeasIdleReport in decreasing order of the cell sorting quantity, i.e. the best cell is included first, as follows:
6> if qualityThreshold is configured:
7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold;
6> else:
7> include the measurement results from all cells applicable for idle/inactive measurement reporting;
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
[TS 38.331, clause 5.7.8.3]
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.10.3]
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:
2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;
2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;
8.1.5.11.3.3 Test Description
8.1.5.11.3.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, serving cell. System information combination NR-7 defined in TS 38.508-1 [4] clause 4.4.3.1.2 together with SIB11 defined in specific message contents
– NR Cell 3, suitable for inter-frequency measurements. System information combination NR-4 defined in TS 38.508-1 [4] clause 4.4.3.1.2.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.1.5.11.3.3.2 Test procedure sequence
Table 8.1.5.11.3.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<– |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 15 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
3 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
4 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
5 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
6 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
7 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<– |
NR RRC: UEInformationRequest |
– |
– |
|
8 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
–> |
NR RRC: UEInformationResponse |
1 |
P |
|
9 |
The SS removes ssb-MeasConfig in SIB11. |
– |
– |
– |
– |
|
10 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
<– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
11 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
12 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<– |
NR RRC: RRCRelease |
– |
– |
|
13 |
Wait for 15 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
14 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
15 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
16 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
17 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
18 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<– |
NR RRC: UEInformationRequest |
– |
– |
|
19 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
–> |
NR RRC: UEInformationResponse |
2 |
P |
|
20 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
21 |
Wait for 15 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
22 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
23 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
24 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
25 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
26 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
27 |
Check: Does the UE transmit UEInformationResponse without measResultIdleNR? |
–> |
NR RRC: UEInformationResponse |
3 |
P |
|
28 |
The SS removes measIdleCarrierListNR in SIB11. |
– |
– |
– |
– |
|
29 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
<– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
30 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
31 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<– |
NR RRC: RRCRelease |
– |
– |
|
32 |
Wait for 15 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
33 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
34 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
35 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
36 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
37 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<– |
NR RRC: UEInformationRequest |
– |
– |
|
38 |
Check: Does the UE transmit UEInformationResponse without measResultIdleNR? |
–> |
NR RRC: UEInformationResponse |
4 |
P |
8.1.5.11.3.3.3 Specific message contents
Table 8.1.5.11.3.3.3-1: RRCRelease (steps 1, 13 and 28, Table 8.1.5.11.3.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.6.1-16 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCRelease ::= SEQUENCE { |
|||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
||
|
criticalExtensions CHOICE { |
|||
|
rrcRelease SEQUENCE { |
|||
|
suspendConfig |
SuspendConfig |
||
|
nonCriticalExtensions SEQUENCE { |
|||
|
nonCriticalExtensions SEQUENCE { |
|||
|
measIdleConfig-r16 SetupRelease { |
|||
|
setup |
MeasIdleConfigDedicated-r16 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.11.3.3.3-2: SuspendConfig (Table 8.1.5.11.3.3.3-1)
|
Derivation Path: TS 38.331 [12] Chapter 6.2.2 Message definitions – RRCRelease |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SuspendConfig ::= SEQUENCE { |
|||
|
fullI-RNTI |
I-RNTI-Value |
38.508-1[4] Table 4.6.3-64 |
|
|
shortI-RNTI |
ShortI-RNTI-Value |
38.508-1[4] Table 4.6.3-170 |
|
|
ran-PagingCycle |
rf32 |
||
|
ran-NotificationAreaInfo CHOICE { |
|||
|
cellList SEQUENCE (SIZE (1.. maxPLMNIdentities)) OF PLMN-RAN-AreaCell { |
2 entries |
||
|
PLMN-RAN-AreaCellList[1] SEQUENCE { |
entry 1 |
||
|
plmn-Identity |
PLMN1 |
||
|
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity { |
1 entry |
||
|
CellIdentity[1] |
CellIdentity of NR Cell 1 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
PLMN-RAN-AreaCellList[2] SEQUENCE { |
entry 2 |
||
|
plmn-Identity |
PLMN2 |
||
|
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity { |
1 entry |
||
|
CellIdentity[1] |
CellIdentity of NR Cell 3 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
t380 |
Not present |
||
|
nextHopChainingCount |
NextHopChainingCount |
38.508-1[4] Table 4.6.3-83 |
|
|
} |
|||
Table 8.1.5.11.3.3.3-3: MeasIdleConfigDedicated (Table 8.1.5.11.3.3.3-1)
|
Derivation Path: TS 38.331 [12] Chapter 6.3.2 Radio resource control information elements – MeasIdleConfig |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasIdleConfigDedicated-r16 ::= SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 |
Not present |
||
|
measIdleCarrierListEUTRA-r16 |
Not present |
||
|
measIdleDuration-r16 |
sec120 |
||
|
validityAreaList-r16 |
Not present |
||
|
} |
|||
Table 8.1.5.11.3.3.3-4: RRCResumeRequest (Table 8.1.5.11.3.3.2-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-19 |
Table 8.1.5.11.3.3.3-5: RRCResume (Table 8.1.5.11.3.3.2-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-17 |
Table 8.1.5.11.3.3.3-6: RRCResumeComplete (Table 8.1.5.11.3.3.2-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-18 |
Table 8.1.5.11.3.3.3-7: SIB11 (Table 8.1.5.11.3.3.2-1, steps 1 to 12)
|
Derivation Path: TS 38.331 12Z] Chapter 6.3.1 System information blocks – SIB11 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB11-r16 ::= SEQUENCE { |
|||
|
measIdleConfigSIB-r16 SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 { |
1 entry |
||
|
MeasIdleCarrierNR-r16 SEQUENCE { |
|||
|
carrierFreq-r16 |
ARFCN value corresponding NR cell 3 |
||
|
ssbSubcarrierSpacing-r16 |
kHz15 |
||
|
frequencyBandList |
Not present |
||
|
measCellListNR-r16 |
|||
|
reportQuantities-r16 |
both |
||
|
qualityThreshold-r16 |
Not present |
||
|
ssb-MeasConfig-r16 SEQUENCE { |
|||
|
nrofSS-BlocksToAverage-r16 |
2 |
||
|
absThreshSS-BlocksConsolidation-r16 SEQUENCE { |
|||
|
thresholdRSRP |
RSRP-Range |
38.508-1[4] Table 4.6.3-152 |
|
|
thresholdRSRQ |
Not present |
||
|
thresholdSINR |
Not present |
||
|
} |
|||
|
smtc-r16 |
SSB-MTC |
38.508-1[4] Table 4.6.3-185 |
|
|
ssb-ToMeasure-r16 |
SSB-ToMeasure |
38.508-1[4] Table 4.6.3-187 |
|
|
deriveSSB-IndexFromCell-r16 |
false |
||
|
true |
FR1_TDD, FR2_TDD |
||
|
ss-RSSI-Measurement-r16 |
Not present |
||
|
} |
|||
|
measIdleCarrierListEUTRA-r16 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.11.3.3.3-8: SIB11 (Table 8.1.5.11.3.3.2-1, steps 13 to 39)
|
Derivation Path: TS 38.331 [XYZ] Chapter 6.3.1 System information blocks – SIB11 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB11-r16 ::= SEQUENCE { |
|||
|
measIdleConfigSIB-r16 SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 { |
1 entry |
||
|
MeasIdleCarrierNR-r16 SEQUENCE { |
|||
|
carrierFreq-r16 |
ARFCN value corresponding NR cell 3 |
||
|
ssbSubcarrierSpacing-r16 |
kHz15 |
||
|
frequencyBandList |
Not present |
||
|
measCellListNR-r16 |
|||
|
reportQuantities-r16 |
both |
||
|
qualityThreshold-r16 |
Not present |
||
|
ssb-MeasConfig-r16 |
Not present |
||
|
measIdleCarrierListEUTRA-r16 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.5.11.3.3.3-9: SIB11 (Table 8.1.5.11.3.3.2-1, steps 25 to 39)
|
Derivation Path: TS 38.331 [XYZ] Chapter 6.3.1 System information blocks – SIB11 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB11-r16 ::= SEQUENCE { |
|||
|
measIdleConfigSIB-r16 SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 |
Not present |
||
|
measIdleCarrierListEUTRA-r16 |
Not present |
||
|
} |
|||
|
} |
|||
Table 8.1.5.11.3.3.3-10: UEInformationRequest (Table 8.1.5.11.3.3.2-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-32A with condition IDLE |
Table 8.1.5.11.3.3.3-11: UEInformationResponse (Table 8.1.5.11.3.3.2-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-32B |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UEInformationResponse-r16 ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
ueInformationResponse-r16 SEQUENCE { |
|||
|
measResultIdleNR-r16 SEQUENCE { |
|||
|
measResultServingCell-r16 SEQUENCE { |
|||
|
rsrp-Result-r16 |
INTEGER (0..127) |
||
|
rsrq-Result-r16 |
INTEGER (0..127) |
||
|
resultsSSB-Indexes-r16 SEQUENCE { |
|||
|
ssb-Index-r16 |
INTEGER (0..maxNrofSSBs-1) |
||
|
ssb-Results-r16 SEQUENCE { |
|||
|
ssb-RSRP-Result-r16 |
INTEGER (0..127) |
||
|
ssb-RSRQ-Result-r16 |
INTEGER (0..127) |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
measResultsPerCarrierListIdleNR-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleNR-r16 |
1 entry |
||
|
MeasResultsPerCarrierIdleNR-r16[1] SEQUENCE { |
entry 1 |
||
|
carrierFreq-r16 |
ARFCN value corresponding to NR cell 3 |
||
|
measResultsPerCellListIdleNR-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleNR-r16 { |
1 entry |
||
|
MeasResultsPerCellIdleNR-r16[1] SEQUENCE { |
entry 1 |
||
|
physCellId-r16 |
PhysCellId corresponding to NR cell 3 |
||
|
measIdleResultNR-r16 SEQUENCE { |
|||
|
rsrp-Result-r16 |
INTEGER (0..127) |
||
|
rsrq-Result-r16 |
INTEGER (0..127) |
||
|
resultsSSB-Indexes-r16 SEQUENCE { |
|||
|
ssb-Index-r16 |
INTEGER (0..maxNrofSSBs-1) |
||
|
ssb-Results-r16 SEQUENCE { |
|||
|
ssb-RSRP-Result-r16 |
INTEGER (0..127) |
||
|
ssb-RSRQ-Result-r16 |
INTEGER (0..127) |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.5.11.4 Idle/Inactive measurements / Inactive mode / RRCRelease configuration / Measurement of NR cells
8.1.5.11.4.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig with ssb-MeasConfig }
then { UE enters RRC_INACTIVE state, performs cell measurements and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, ssb-MeasConfig from SIB11 }
then { UE enters RRC_INACTIVE state, performs cell measurements and reports measurement results }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, ssb-MeasConfig parameters derived from SIB4 }
then { UE enters RRC_INACTIVE state, performs cell measurements and reports measurement results }
}
(4)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig with ssb-MeasConfig and suspendConfig, T331 expires }
then { UE enters RRC_INACTIVE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(5)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig without measIdleCarrierListNR }
then { UE does not report measurement results }
}
8.1.5.11.4.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3, 5.7.8 and 5.7.10.3. Unless otherwise stated, these are Rel-16 requirements.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
[TS 38.331, clause 5.7.8.1]
This procedure specifies the measurements to be performed and stored by a UE in RRC_IDLE and RRC_INACTIVE when it has an idle/inactive measurement configuration.
[TS 38.331, clause 5.7.8.1a]
The purpose of this procedure is to update the idle/inactive measurement configuration.
The UE initiates this procedure while T331 is running and one of the following conditions is met:
1> upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or
1> upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection;
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> for each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message:
2> if there is an entry in measIdleCarrierListNR in measIdleConfigSIB of SIB11 that has the same carrier frequency and subcarrier spacing as the entry in the measIdleCarrierListNR within VarMeasIdleConfig and that contains ssb-MeasConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB11 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else if there is an entry in interFreqCarrierFreqList of SIB4 with the same carrier frequency and subcarrier spacing as the entry in measIdleCarrierListNR within VarMeasIdleConfig:
3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
3> store the SSB measurement configuration from SIB4 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;
2> else:
3> remove the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig, if stored;
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [9].
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if the VarMeasIdleConfig includes the measIdleCarrierListNR and the SIB1 contains idleModeMeasurementsNR:
3> for each entry in measIdleCarrierListNR within VarMeasIdleConfig that contains ssb-MeasConfig:
4> if UE supports carrier aggregation or NR-DC between serving carrier and the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry:
5> perform measurements in the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry;
5> if the reportQuantities is set to rsrq:
6> consider RSRQ as the cell sorting quantity;
5> else:
6> consider RSRP as the cell sorting quantity;
5> if the measCellListNR is included:
6> consider cells identified by each entry within the measCellListNR to be applicable for idle/inactive measurement reporting;
5> else:
6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;
5> for all cells applicable for idle/inactive measurement reporting, derive cell measurement results for the measurement quantities indicated by reportQuantities;
5> store the derived cell measurement results as indicated by reportQuantities for cells applicable for idle/inactive measurement reporting within measResultsPerCarrierListIdleNR in the measReportIdleNR in VarMeasIdleReport in decreasing order of the cell sorting quantity, i.e. the best cell is included first, as follows:
6> if qualityThreshold is configured:
7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold;
6> else:
7> include the measurement results from all cells applicable for idle/inactive measurement reporting;
5> if beamMeasConfigIdle is included in the associated entry in measIdleCarrierListNR and if UE supports idleInactiveNR-MeasBeamReport for the FR of the carrier frequency indicated by carrierFreq within the associated entry, for each cell in the measurement results:
6> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215 [9];
6> if the reportQuantityRS-Indexes is set to rsrq:
7> consider RSRQ as the beam sorting quantity;
6> else:
7> consider RSRP as the beam sorting quantity;
6> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:
7> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;
6> if the includeBeamMeasurements is set to true:
7> include the beam measurement results as indicated by reportQuantityRS–Indexes;
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
3> if the VarMeasIdleConfig includes the measIdleCarrierListNR and it contains an entry with carrierFreq set to the value of the serving frequency:
4> if beamMeasConfigIdle is included in that entry, and if the UE supports idleInactiveNR- MeasBeamReport for the FR of the serving cell:
5> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215 [9];
5> if the reportQuantityRS-Indexes is set to rsrq:
6> consider RSRQ as the beam sorting quantity;
5> else:
6> consider RSRP as the beam sorting quantity;
5> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:
6> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included in SIB2 of serving cell, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;
5> if the includeBeamMeasurements is set to true:
6> include the beam measurement results as indicated by reportQuantityRS-Indexes;
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
[TS 38.331, clause 5.7.8.3]
The UE shall:
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.10.3]
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:
2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;
2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;
8.1.5.11.4.3 Test Description
8.1.5.11.4.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, serving cell. System information combination NR-7 defined in TS 38.508-1 [4] clause 4.4.3.1.2.
– NR Cell 3, suitable for inter-frequency measurements. System information combination NR-4 defined in TS 38.508-1 [4] clause 4.4.3.1.2.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.1.5.11.4.3.2 Test procedure sequence
Table 8.1.5.11.4.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message with measIdleConfig and suspendConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 5 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
3 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
4 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
5 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
6 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
7 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
8 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
1 |
P |
|
9 |
The SS transmits RRCRelease message with measIdleConfig and suspendConfig not including ssb-MeasConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
10 |
Wait for 15 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
11 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
12 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
13 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
14 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
15 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
16 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
2 |
P |
|
17 |
The SS removes measIdleCarrierListNR in SIB11. |
– |
– |
– |
– |
|
18 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
19 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
20 |
The SS transmits RRCRelease message with measIdleConfig and suspendConfig not including ssb-MeasConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
21 |
Wait for 15 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
22 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
23 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
24 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
25 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
26 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
27 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
3 |
P |
|
28 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
29 |
Wait for 11 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
30 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
31 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
32 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
33 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
34 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
35 |
Check: Does the UE transmit UEInformationResponse without measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
4 |
P |
|
36 |
The SS transmits RRCRelease message with measIdleConfig and suspendConfig not including measIdleCarrierListNR to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
37 |
Wait for 5 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
38 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
39 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
40 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
41 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
42 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
43 |
Check: Does the UE transmit UEInformationResponse without measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
5 |
P |
8.1.5.11.4.3.3 Specific message contents
TBD