8.1.3 RRC connection release
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
8.1.3.1 Void
NOTE: The present test (RRC connection release / Success) is superseded by test case 8.2.1.1 (i.e. all requirements which the present test verified are verified in test case 8.2.1.1).
8.1.3.2 Void
8.1.3.3 Void
8.1.3.4 RRC connection release / Redirection to another E-UTRAN frequency
8.1.3.4.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with eutra different from the frequency UE was on in RRC_CONNECTED state}
then { UE enters RRC_IDLE state on new frequency included in IE redirectedCarrierInfo }
}
8.1.3.4.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.8.3, 5.3.12 and TS 36.304, clauses 5.2.4.1, 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.4.1]
…
UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
…
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on an EUTRA carrier. If no suitable cell is found, the UE shall perform a cell selection starting with Stored Information Cell Selection procedure in order to find a suitable cell to camp on.
…
8.1.3.4.3 Test description
8.1.3.4.3.1 Pre-test conditions
System Simulator:
– 2 cells on different E-UTRA frequencies and different tracking areas:
– Cell 1 serving cell
– Cell 23 suitable neighbour inter-frequency cell
– Cell power levels are selected according to [18] so that camping on Cell 1 is guaranteed
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) according to [18] on cell 1.
8.1.3.4.3.2 Test procedure sequence
Table 8.1.3.4.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message (IE redirectedCarrierInfo including eutra of Cell 23). |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Check: does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 23? |
– |
– |
1 |
– |
8.1.3.4.3.3 Specific message contents
Table 8.1.3.4.3.3-1: Conditions for specific message contents in tables 8.1.3.4.3.3-3 and 8.1.3.4.3.3-3A
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.4.3.3-2: Void
Table 8.1.3.4.3.3-3: SystemInformationBlockType5 for cell 1 (preamble and all steps, Table 8.1.3.4.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[n] |
Same downlink EARFCN as used for Cell 23 |
||
|
dl-CarrierFreq[n] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[n] |
Not present |
||
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[n] |
Same downlink EARFCN as used for Cell 23 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.4.3.3-3A: SystemInformationBlockType5 for cell 23 (preamble and all steps, Table 8.1.3.4.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[n] |
Same downlink EARFCN as used for Cell 1 |
||
|
dl-CarrierFreq[n] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[n] |
Not present |
||
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[n] |
Same downlink EARFCN as used for Cell 1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.4.3.3-4: RRCConnectionRelease message (step 1, Table 8.1.3.4.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo ::= CHOICE { |
|||
|
eutra |
Downlink EARFCN of cell 23 |
||
|
} |
|||
|
redirectedCarrierInfo {} |
Not present |
Band > 64 |
|
|
nonCriticalExtension SEQUENCE { |
Band > 64 |
||
|
lateNonCriticalExtension SEQUENCE { |
|||
|
redirectedCarrierInfo-v9e0 SEQUENCE { |
|||
|
eutra-v9e0 |
Downlink EARFCN of cell 23 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.5 RRC connection release / Success / With priority information
8.1.3.5.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_IDLE state having received an RRCConnectionRelease message with the freqPriorityListEUTRA with higher priority frequency}
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher priority frequency }
then { UE reselects the cell which belongs to the higher priority frequency }
}
8.1.3.5.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.8.3 and TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> 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> 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:
…
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:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;
[TS 36.304, clause 5.2.4.1]
Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an E-UTRAN frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight network configured values), irrespective of any other priority value allocated to this frequency. The UE shall delete priorities provided by dedicated signalling when:
– the UE enters RRC_CONNECTED state; or
– the optional validity time of dedicated priorities (T320) expires; or
– a PLMN selection is performed on request by NAS [5].
NOTE: Equal priorities between RATs are not supported.
The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
The UE shall not consider any black listed cells as candidate for cell reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e., T320 in E-UTRA, T322 in UTRA and T3230 in GERAN), if configured, at inter-RAT cell (re)selection.
NOTE: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.
[TS 36.304, clause 5.2.4.2]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
– If the serving cell fulfils Srxlev > SIntraSearchP and Squal > SIntraSearchQ, the UE may choose not to perform intra-frequency measurements.
– Otherwise, the UE shall perform intra-frequency measurements.
– The UE shall apply the following rules for E-UTRAN inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:
– For an E-UTRAN inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current E-UTRA frequency the UE shall perform measurements of higher priority E-UTRAN inter-frequency or inter-RAT frequencies according to [10].
– For an E-UTRAN inter-frequency with an equal or lower reselection priority than the reselection priority of the current E-UTRA frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current E-UTRAN frequency:
– If the serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE may choose not to perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority.
– Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority EUTRAN or UTRAN RAT/ frequency fulfils Squal > ThreshX, HighQ during a time interval TreselectionRAT; or
– A cell of a higher priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
- More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based on ranking for Intra-frequency cell reselection as defined in sub-clause 5.2.4.6.
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority EUTRAN or UTRAN RAT/ frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT; or
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a higher priority RAT/ frequency shall take precedence over a lower priority RAT/ frequency, if multiple cells of different priorities fulfil the cell reselection criteria.
For cdma2000 RATs, Srxlev is equal to -FLOOR(-2 x 10 x log10 Ec/Io) in units of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, ThreshX, HighP and ThreshX, LowP are equal to -1 times the values signalled for the corresponding parameters in the system information.
In all the above criteria the value of TreselectionRAT is scaled when the UE is in the medium or high mobility state as defined in subclause 5.2.4.3.1. If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
– If the highest-priority frequency is an E-UTRAN frequency, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria according to section 5.2.4.6;
– If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.
8.1.3.5.3 Test description
8.1.3.5.3.1 Pre-test conditions
System Simulator:
– Cell 1, Cell 3 and Cell6.
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
NOTE: For Cell 3 and 6 TAI is set to TAI-2
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
8.1.3.5.3.2 Test procedure sequence
Table 8.1.3.5.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.3.5.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 3 |
Cell 6 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
"off” |
"off” |
The power level values are assigned to satisfy SrxlevCell 1 > Sintrasearch. (NOTE 1) |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-73 |
-73 |
The power level values are assigned to satisfy both Threshx, low < SrxlevCell 3 and Threshx, high <SrxlevCell 6. |
|
NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1. |
||||||
Table 8.1.3.5.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message including the freqPriorityListEUTRA on Cell 1. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state on Cell 1. |
– |
– |
– |
– |
|
3 |
The SS changes Cell 1, Cell 3 and Cell 6 level according to the row "T1" in table 8.1.3.5.3.2-1. |
– |
– |
– |
– |
|
4 |
Void |
– |
– |
– |
– |
|
5 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 6? |
– |
– |
1 |
– |
8.1.3.5.3.3 Specific message contents
Table 8.1.3.5.3.3-0: Conditions for specific message contents
in Tables 8.1.3.5.3.3-1, 8.1.3.5.3.3-2 and 8.1.3.5.3.3-3.
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.5.3.3-1: RRCConnectionRelease (step 1, Table 8.1.3.5.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
idleModeMobilityControlInfo SEQUENCE { |
|||
|
freqPriorityListEUTRA SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
3 entries |
||
|
carrierFreq[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
carrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[1] |
4 |
||
|
carrierFreq[2] |
Same downlink EARFCN as used for Cell 3 |
||
|
carrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[2] |
1 |
||
|
carrierFreq[3] |
Same downlink EARFCN as used for Cell 6 |
||
|
carrierFreq[3] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[3] |
5 |
||
|
} |
|||
|
freqPriorityListGERAN |
Not present |
||
|
freqPriorityListUTRA-FDD |
Not present |
||
|
freqPriorityListUTRA-TDD |
Not present |
||
|
bandClassPriorityListHRPD |
Not present |
||
|
bandClassPriorityList1XRTT |
Not present |
||
|
t320 |
Not present |
||
|
} |
|||
|
nonCriticalExtension |
Band > 64 |
||
|
nonCriticalExtension |
|||
|
idleModeMobilityControlInfo-v9e0 SEQUENCE { |
|||
|
freqPriorityListEUTRA-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
carrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
carrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 3 |
||
|
carrierFreq-v9e0[3] |
Same downlink EARFCN as used for Cell 6 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.5.3.3-2: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table 8.1.3.5.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[n] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq[n] |
maxEARFCN |
Band > 64 |
|
|
dl-CarrierFreq[m] |
Same downlink EARFCN as used for Cell 6 |
||
|
dl-CarrierFreq[m] |
maxEARFCN |
Band > 64 |
|
|
threshX-Low[n] |
11 |
||
|
threshX-High[m] |
11 |
||
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[n] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq-v9e0[m] |
Same downlink EARFCN as used for Cell 6 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.5.3.3-3: SystemInformationBlockType5 for Cell 6 (all steps, Table 8.1.3.5.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
2 entries |
||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
dl-CarrierFreq[2] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
dl-CarrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.5a RRC connection release / Success / With extended priority information
8.1.3.5a.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_IDLE state having received an RRCConnectionRelease message with the freqPriorityListExtEUTRA with higher priority frequency}
ensure that {
when { UE detects the cell re-selection criteria are met for the cell, which belongs to the higher priority frequency in freqPriorityListExtEUTRA and this cell is the highest ranked cell }
then { UE reselects the cell which belongs to the higher priority frequency }
}
8.1.3.5a.2 Conformance requirements
Same as 8.1.3.5.2 and
[TS 36.331, clause 6.2.2.]
|
RRCConnectionRelease field descriptions |
|---|
|
carrierFreq or bandClass The carrier frequency (UTRA and E-UTRA) and band class (HRPD and 1xRTT) for which the associated cellReselectionPriority is applied. |
|
carrierFreqs The list of GERAN carrier frequencies organised into one group of GERAN carrier frequencies. |
|
cellInfoList Used to provide system information of one or more cells on the redirected inter-RAT carrier frequency. The system information can be used if, upon redirection, the UE selects an inter-RAT cell indicated by the physCellId and carrierFreq (GERAN and UTRA TDD) or by the physCellId (other RATs). The choice shall match the redirectedCarrierInfo. In particular, E-UTRAN only applies value utra-TDD-r10 in case redirectedCarrierInfo is set to utra-TDD-r10. |
|
extendedWaitTime Value in seconds for the wait time for Delay Tolerant access requests. |
|
freqPriorityListX Provides a cell reselection priority for each frequency, by means of separate lists for each RAT (including E-UTRA). The UE shall be able to store at least 3 occurrences of FreqsPriorityGERAN. If E-UTRAN includes freqPriorityListEUTRA-v9e0 and/or freqPriorityListEUTRA-v1310 it includes the same number of entries, and listed in the same order, as in freqPriorityListEUTRA (i.e. without suffix). Field freqPriorityListExt includes additional neighbouring inter-frequencies, i.e. extending the size of the inter-frequency carrier list using the general principles specified in 5.1.2. EUTRAN only includes freqPriorityListExtEUTRA if freqPriorityListEUTRA (i.e. without suffix) includes maxFreq entries. If E-UTRAN includes freqPriorityListExtEUTRA-v1310 it includes the same number of entries, and listed in the same order, as in freqPriorityListExtEUTRA-r12. |
8.1.3.5a.3 Test description
8.1.3.5a.3.1 Pre-test conditions
Same as 8.1.3.5.3.1 and
System Simulator:
– Cell 14 is a non used cell.
8.1.3.5a.3.2 Test procedure sequence
Same as 8.1.3.5.3.2 except
Table 8.1.3.5a.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message including the freqPriorityListExtEUTRA-r12 on Cell 1. |
<– |
RRCConnectionRelease |
– |
– |
|
2-5 |
Same as in table 8.1.3.5.3.2-2. |
– |
– |
– |
– |
8.1.3.5a.3.3 Specific message contents
Same as 8.1.3.5.3.3 except
Table 8.1.3.5a.3.3-1: RRCConnectionRelease (step 1, Table 8.1.3.5a.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
idleModeMobilityControlInfo SEQUENCE { |
|||
|
freqPriorityListEUTRA SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
carrierFreq[1] |
EARFCN of Cell 14 |
Non used cell |
|
|
carrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
carrierFreq[2] |
EARFCN of Cell 14 +1 |
Non used cell |
|
|
carrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
carrierFreq[3] |
EARFCN of Cell 14 +2 |
Non used cell |
|
|
carrierFreq[3] |
maxEARFCN |
Band > 64 |
|
|
carrierFreq[4] |
EARFCN of Cell 14 +3 |
Non used cell |
|
|
carrierFreq[4] |
maxEARFCN |
Band > 64 |
|
|
carrierFreq[5] |
EARFCN of Cell 14 +4 |
Non used cell |
|
|
carrierFreq[5] |
maxEARFCN |
Band > 64 |
|
|
carrierFreq[6] |
EARFCN of Cell 14 +5 |
Non used cell |
|
|
carrierFreq[6] |
maxEARFCN |
Band > 64 |
|
|
carrierFreq[7] |
EARFCN of Cell 14 +6 |
Non used cell |
|
|
carrierFreq[7] |
maxEARFCN |
Band > 64 |
|
|
carrierFreq[8] |
EARFCN of Cell 14 +7 |
Non used cell |
|
|
carrierFreq[8] |
maxEARFCN |
Band > 64 |
|
|
} |
|||
|
freqPriorityListGERAN |
Not present |
||
|
freqPriorityListUTRA-FDD |
Not present |
||
|
freqPriorityListUTRA-TDD |
Not present |
||
|
bandClassPriorityListHRPD |
Not present |
||
|
bandClassPriorityList1XRTT |
Not present |
||
|
t320 |
Not present |
||
|
} |
|||
|
freqPriorityListExtEUTRA-r12 SEQUENCE (SIZE (1.. maxFreq)) OF SEQUENCE { |
|||
|
carrierFreq-r12[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
cellReselectionPriority-r12[1] |
4 |
||
|
carrierFreq-r12[2] |
Same downlink EARFCN as used for Cell 3 |
||
|
cellReselectionPriority-r12[2] |
1 |
||
|
carrierFreq-r12[3] |
Same downlink EARFCN as used for Cell 6 |
||
|
cellReselectionPriority-r12[3] |
5 |
||
|
} |
|||
|
nonCriticalExtension |
Band > 64 |
||
|
nonCriticalExtension |
|||
|
idleModeMobilityControlInfo-v9e0 SEQUENCE { |
|||
|
freqPriorityListEUTRA-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
carrierFreq-v9e0[1] |
EARFCN of Cell 14 |
Non used cell |
|
|
carrierFreq-v9e0[2] |
EARFCN of Cell 14 + 1 |
Non used cell |
|
|
carrierFreq-v9e0[3] |
EARFCN of Cell 14 + 2 |
Non used cell |
|
|
carrierFreq-v9e0[4] |
EARFCN of Cell 14 + 3 |
Non used cell |
|
|
carrierFreq-v9e0[5] |
EARFCN of Cell 14 + 4 |
Non used cell |
|
|
carrierFreq-v9e0[6] |
EARFCN of Cell 14 + 5 |
Non used cell |
|
|
carrierFreq-v9e0[7] |
EARFCN of Cell 14 + 6 |
Non used cell |
|
|
carrierFreq-v9e0[8] |
EARFCN of Cell 14 + 7 |
Non used cell |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.6 RRC connection release / Redirection from E-UTRAN to UTRAN
8.1.3.6.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency }
then { UE enters RRC_IDLE state on UTRA frequency included in IE redirectionInformation }
}
8.1.3.6.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on an EUTRA carrier.
…
8.1.3.6.3 Test description
8.1.3.6.3.1 Pre-test conditions
System Simulator:
– 2 cells, one E-UTRA and one UTRA cell and different location areas:
– Cell 1 E-UTRA serving cell
– Cell 5 suitable neighbour UTRA cell
– The parameters settings and power levels for Cell 1 and Cell 5 are selected according to [18], [5] and Table 8.1.3.6.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 5 can take place (utra priority is lower than serving and S Cell 1 > Thresh Cell 1,low).
– System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on cell 1 according to [18].
8.1.3.6.3.2 Test procedure sequence
Table 8.1.3.6.3.2-0 shows the cell power levels after the preamble.
Table 8.1.3.6.3.2-0: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 5 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-75 |
– |
The power levels are such that camping on Cell 1 is guaranteed. |
|
CPICH_Ec |
dBm/3.84 MHz |
– |
-70 |
||
|
P-CCPCH |
dBm/1.28 MHz |
– |
-72 |
Table 8.1.3.6.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message (IE redirectionInformation including UTRA-CarrierFreq of Cell 5). |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.8 indicate that the UE is camped on UTRAN Cell 5? |
– |
– |
1 |
– |
|
3a1-3a3Aa7a2 |
Void |
– |
– |
– |
– |
8.1.3.6.3.3 Specific message or IE contents
Table 8.1.3.6.3.3-1: Void
Table 8.1.3.6.3.3-2: Void
Table 8.1.3.6.3.3-3: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 8.1.3.6.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType6 ::= SEQUENCE { |
|||
|
carrierFreqListUTRA-FDD SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OF SEQUENCE { |
UTRA-FDD |
||
|
carrierFreq[n] |
Same downlink UARFCN as used for cell 5 |
||
|
cellReselectionPriority[n] |
3 |
Lower priority than E-UTRA |
|
|
} |
|||
|
carrierFreqListUTRA-TDD SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OF SEQUENCE { |
UTRA-TDD |
||
|
carrierFreq[n] |
Same downlink UARFCN as used for cell 5 |
||
|
cellReselectionPriority[n] |
3 |
Lower priority than E-UTRA |
|
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
UTRA-FDD |
UTRA FDD cell environment |
|
UTRA-TDD |
UTRA TDD cell environment |
Table 8.1.3.6.3.3-4 RRCConnectionRelease message (step 1, Table 8.1.3.6.3.2-1)
|
Derivation Path: 36.508 table 4.6.1.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo ::= CHOICE { |
|||
|
utra-FDD |
Downlink UARFCN of cell 5 |
UTRA-FDD |
|
|
utra-TDD |
Downlink UARFCN of cell 5 |
UTRA-TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
UTRA-FDD |
UTRA FDD cell environment |
|
UTRA-TDD |
UTRA TDD cell environment |
Table 8.1.3.6.3.3-5: System Information Block type 19 for Cell 5 (preamble and all steps, Table 8.1.3.6.3.2-1)
|
Derivation Path: 36.508 table 4.4.4.1-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SysInfoType19 ::= SEQUENCE { |
|||
|
Utra-PriorityInfoList ::= SEQUENCE { |
|||
|
utra-ServingCell ::= SEQUENCE { |
|||
|
priority |
5 |
||
|
} |
|||
|
} |
|||
8.1.3.6a RRC connection release / Redirection from E-UTRAN to UTRAN / Pre-redirection info
8.1.3.6a.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with utra-CarrierFreq UTRA frequency }
then { UE sends an RRC CONNECTION REQUEST message including IE Pre-redirection info set to FALSE on UTRA frequency included in IE redirectionInformation and enters RRC_IDLE state on that UTRA frequency }
}
8.1.3.6a.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7 and TS 25.331, clause 8.1.3.3, 10.2.39 with additional clarification in R2-105061.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on an EUTRA carrier.
[TS 25.331, clause 8.1.3.3]
…
1> if the UE supports E-UTRA:
2> if the UE is attempting to establish the signalling connection as a result of being redirected by E-UTRA; and
2> if this is the first attempt to establish the signalling connection;
3> do not include the IE "Pre-Redirection info";
[TS 25.331, clause 10.2.39]
|
Pre-redirection info |
OP |
Pre-redirection info 10.3.3.25a |
The presence of this IE indicates the UE support of radio access technologies that the UE could be directed to, and that the UE was not redirected from EUTRA. |
REL-8 |
8.1.3.6a.3 Test description
8.1.3.6a.3.1 Pre-test conditions
System Simulator:
– 2 cells, one E-UTRA and one UTRA cell and different location areas:
– Cell 1 E-UTRA serving cell
– Cell 5 suitable neighbour UTRA cell
– The parameters settings and power levels for Cell 1 and Cell 5 are selected according to [18], [5] and Table 8.1.3.6a.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 5 can take place (utra priority is lower than serving and S Cell 1 > Thresh Cell 1,low).
– System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on cell 1 according to [18].
8.1.3.6a.3.2 Test procedure sequence
Table 8.1.3.6a.3.2-0 shows the cell power levels after the preamble.
Table 8.1.3.6a.3.2-0: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 5 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-75 |
– |
The power levels are such that camping on Cell 1 is guaranteed. |
|
CPICH_Ec |
dBm/3.84 MHz |
– |
-70 |
||
|
P-CCPCH |
dBm/1.28 MHz |
– |
-72 |
Table 8.1.3.6a.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message (IE redirectedCarrierInfo including UTRA-CarrierFreq of Cell 5). |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.8 indicate that the UE is camped on UTRAN Cell 5? |
– |
– |
1 |
– |
8.1.3.6a.3.3 Specific message or IE contents
Table 8.1.3.6a.3.3-1: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 8.1.3.6a.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType6 ::= SEQUENCE { |
|||
|
carrierFreqListUTRA-FDD SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OF SEQUENCE { |
UTRA-FDD |
||
|
carrierFreq[n] |
Same downlink UARFCN as used for cell 5 |
||
|
cellReselectionPriority[n] |
3 |
Lower priority than E-UTRA |
|
|
} |
|||
|
carrierFreqListUTRA-TDD SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OF SEQUENCE { |
UTRA-TDD |
||
|
carrierFreq[n] |
Same downlink UARFCN as used for cell 5 |
||
|
cellReselectionPriority[n] |
3 |
Lower priority than E-UTRA |
|
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
UTRA-FDD |
UTRA FDD cell environment |
|
UTRA-TDD |
UTRA TDD cell environment |
Table 8.1.3.6a.3.3-2 RRCConnectionRelease message (step 1, Table 8.1.3.6a.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo ::= CHOICE { |
|||
|
utra-FDD |
Downlink UARFCN of cell 5 |
UTRA-FDD |
|
|
utra-TDD |
Downlink UARFCN of cell 5 |
UTRA-TDD |
|
|
} |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
cellInfoList-r9 ::= CHOICE {} |
Not present |
redirection with SIB is optional |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
UTRA-FDD |
UTRA FDD cell environment |
|
UTRA-TDD |
UTRA TDD cell environment |
Table 8.1.3.6a.3.3-3: System Information Block type 19 for Cell 5 (preamble and all steps, Table 8.1.3.6a.3.2-1)
|
Derivation Path: 36.508 table 4.4.4.1-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SysInfoType19 ::= SEQUENCE { |
|||
|
Utra-PriorityInfoList ::= SEQUENCE { |
|||
|
utra-ServingCell ::= SEQUENCE { |
|||
|
priority |
5 |
||
|
} |
|||
|
} |
|||
Table 8.1.3.6a.3.3-4 RRC CONNECTION REQUEST (step 2, Table 8.1.3.6a.3.2-1)
|
Derivation Path: 36.508 table 4.7B.1-7 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Pre-redirection info |
Not present |
The presence of this IE indicates the UE support of radio access technologies that the UE could be directed to, and that the UE was not redirected from EUTRA |
|
8.1.3.7 RRC connection release / Redirection from UTRAN to E-UTRAN
8.1.3.7.1 Test Purpose (TP)
(1)
with { UE in UTRA Idle state }
ensure that {
when { UE is requested to make an outgoing PS call }
then { UE includes in the RRC CONNECTION REQUEST the IE Pre-Redirection info" }
}
(2)
with { UE in UTRA CELL_DCH state }
ensure that {
when { UE receives an RRC CONNECTION RELEASE message including an IE Redirection info with E-UTRA target info E-UTRA frequency }
then { UE enters RRC_IDLE state on E-UTRAN Carrier included in IE Redirection info }
}
8.1.3.7.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 25.331, clause 8.1.3.3, 8.1.4.3 and clause 8.5.2.
[TS 25.331, clause 8.1.3.3]
The UE shall, in the transmitted RRC CONNECTION REQUEST message:
…
1> if the UE supports E-UTRA:
2> if the variable EUTRA_FREQUENCY_INFO_LIST contains no E-UTRA frequencies;
3> include the IE "Pre-Redirection info";
3> if the UE supports E-UTRA FDD:
4> set the IE "Support of E-UTRA FDD" to TRUE.
3> if the UE supports E-UTRA TDD:
4> set the IE "Support of E-UTRA TDD" to TRUE.
2> if the UE supports any of the bands that the E-UTRA frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to;
3> include the IE "Pre-Redirection info";
3> if the UE supports any of the bands that the E-UTRA FDD frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:
4> set the IE "Support of E-UTRA FDD" to TRUE.
3> if the UE supports any of the bands that the E-UTRA TDD frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:
4> set the IE "Support of E-UTRA TDD" to TRUE.
[TS 25.331, clause 8.1.4.3]
The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH and CELL_PCH (FDD only). Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed states.
When the UE receives the first RRC CONNECTION RELEASE message; and
1> if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable U_RNTI; or
1> if the message is received on DCCH:
the UE shall perform the RRC connection release procedure as specified below.
When the UE receives the first RRC CONNECTION RELEASE message; and
1> if the message is received on the CCCH, the IE "UTRAN group identity" is present and there is a group identity match according to subclause 8.6.3.13:
the UE shall perform the RRC connection release procedure as specified below.
The UE shall:
1> in state CELL_DCH:
2> initialise the counter V308 to zero;
2> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS;
2> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using UM RLC on the DCCH to the UTRAN;
2> if the IE "Rplmn information" is present:
3> the UE may:
4> store the IE on the ME together with the PLMN id for which it applies;
3> the UE may then:
4> utilise this information, typically indicating where a number of BCCH frequency ranges of a RAT may be expected to be found, during subsequent Rplmn selections of the indicated PLMN.
2> if the IE "UE Mobility State Indicator" is present:
3> consider the High-mobility state to have being detected when entering idle mode.
2> start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio interface.
1> in state CELL_FACH:
2> if the RRC CONNECTION RELEASE message was received on the DCCH:
3> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS;
3> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using AM RLC on the DCCH to the UTRAN.
3> when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been confirmed by the lower layers:
4> release all its radio resources; and
4> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; and
4> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS;
4> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
4> clear the variable ESTABLISHED_RABS;
4> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to upper layers;
4> enter idle mode;
4> perform the actions specified in subclause 8.5.2 when entering idle mode.
3> and the procedure ends.
2> if the RRC CONNECTION RELEASE message was received on the CCCH:
3> release all its radio resources;
3> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to the upper layers;
3> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS;
3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
3> clear the variable ESTABLISHED_RABS;
3> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to upper layers;
3> enter idle mode;
3> perform the actions specified in subclause 8.5.2 when entering idle mode;
3> and the procedure ends.
[TS 25.331, clause 8.5.2]
When entering idle mode from connected mode, the UE shall:
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4;
1> if the RRC CONNECTION RELEASE message was received and the IE "Redirection info" was present therein:
2> if the IE "Frequency info" is present, attempt to camp on a suitable cell on the indicated UTRA carrier included in the RRC CONNECTION RELEASE message;
2> if the IE "GSM target cell info" is present, attempt to camp on a suitable cell of the list of cells for the indicated RAT included in the RRC CONNECTION RELEASE message. If no cells were indicated for that RAT or no suitable cell of the indicated cells for that RAT is found within 10s, attempt to camp on any suitable cell of that RAT; or
2> if the IE "E-UTRA target info" is present, attempt to camp on any of the frequencies for the indicated RAT included in the RRC CONNECTION RELEASE message, excluding any cell indicated in the list of not allowed cells for that RAT, if present. If no suitable cell on the indicated frequencies for that RAT is found within 10s, attempt to camp on any suitable cell of that RAT, excluding any cell indicated in the list of not allowed cells for that RAT; or
2> if no suitable cell is found on the indicated UTRA carrier or RAT camp on any suitable cell.
8.1.3.7.3 Test description
8.1.3.7.3.1 Pre-test conditions
System Simulator:
– 2 cells, one UTRA and one E-UTRA cell:
– Cell 5 UTRA serving cell (priority 4 default)
– Cell 1 suitable neighbour E-UTRA cell (priority 3)
– System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
UTRAN Idle state
Preamble:
The UE is in state Registered, Idle mode according to section 4.5A.3A [18] on Cell 5 (serving cell)..
8.1.3.7.3.2 Test procedure sequence
Table 8.1.3.7.3.2-0 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Subsequent configurations marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.1.3.7.3.2-1.
Table 8.1.3.7.3.2-0: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 5 |
Remark |
|
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-70 |
– |
The power level values are such that entering condition for event 3c is satisfied. |
|
CPICH Ec (UTRA FDD) |
dBm/3.84 MHz |
– |
-85 |
||
|
PCCPCH Ec (UTRA LCR TDD) |
dBm/1.28 MHz |
– |
-85 |
Table 8.1.3.7.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Make the UE initiate an outgoing PS call. |
– |
– |
– |
– |
|
2 |
Check: Does the UE include the IE Pre-redirection info with Support of E-UTRA set to TRUE? |
–> |
RRC CONNECTION REQUEST |
1 |
P |
|
3 |
The SS transmits a RRC CONNECTION SETUP on SRB1 on Cell 5. |
<– |
RRC CONNECTION SETUP |
– |
– |
|
4 |
The UE transmits an RRC CONNECTION SETUP COMPLETE message |
–> |
RRC CONNECTION SETUP COMPLETE |
– |
– |
|
5 |
The UE transmits the SERVICE REQUEST message for PS data call |
–> |
INITIAL DIRECT TRANSFER |
– |
– |
|
– |
EXCEPTION: Steps 6a1 and 6a2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. UTRAN FDD: IF pc_UTRA_CompressedModeRequired and pc_UTRA_FeatrGrp_2 THEN Steps 6a1, 6a2 UTRAN TDD: go to step 6Aa1 |
||||
|
6a1 |
The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message on Cell 5 including the DPCH compressed mode info. |
<– |
PHYSICAL CHANNEL RECONFIGURATION |
– |
– |
|
6a2 |
The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on Cell 5. |
–> |
PHYSICAL CHANNEL RECONFIGURATION COMPLETE |
– |
– |
|
– |
EXCEPTION: Steps 6Aa1 and 6Aa2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. IF pc_UTRA_FeatrGrp_2 THEN 6Aa1 to 6Aa2. |
||||
|
6Aa1 |
The SS configures the Inter-RAT measurement with E-UTRA frequency list including the DL Carrier frequency of Cell 1 |
<– |
MEASUREMENT CONTROL |
– |
– |
|
6Aa2 |
The SS changes Cell 1 and Cell 5 power level according to the row "T1" in table 8.1.3.7.3.2-0. Note: The UE starts sending MEASUREMENT REPORT messages during the Authentication Phase |
– |
– |
– |
– |
|
7-9 |
Void |
||||
|
10 |
The SS starts the Authentication and Ciphering Request procedure |
<– |
DOWNLINK DIRECT TRANSFER |
– |
– |
|
11 |
The UE transmits the Authentication and Ciphering Response |
–> |
UPLINK DIRECT TRANSFER |
– |
– |
|
12 |
The SS transmits a SECURITY MODE COMMAND message. EXCEPTION: Step 13A and Step 14a can occur in any order. |
<– |
SECURITY MODE COMMAND |
– |
– |
|
13 |
The UE transmits a SECURITY MODE COMPLETE message |
–> |
SECURITY MODE COMPLETE |
– |
– |
|
13A |
The UE transmits an ACTIVATE PDP CONTEXT REQUEST message NOTE: Retransmission of this message is ignored |
–> |
UPLINK DIRECT TRANSFER |
||
|
– |
EXCEPTION: Step 14a describes behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. |
||||
|
14a |
IF pc_UTRA_FeatrGrp_2 THEN if MEASUREMENT REPORT is received during the authentication and security phase (from step 10 to 13) goto next step otherwise the SS waits for MEASUREMENT REPORT message. |
–> |
MEASUREMENT REPORT |
– |
– |
|
15 |
The SS transmits an RRC CONNECTION RELEASE message (IE E-UTRA target info including DL Carrier frequency of Cell 1). |
<– |
RRC CONNECTION RELEASE |
– |
– |
|
16 |
The UE transmits a RRC CONNECTION RELEASE COMPLETE message |
–> |
RRC CONNECTION RELEASE COMPLETE |
– |
– |
|
17 |
The UE transmits a RRC CONNECTION RELEASE COMPLETE message |
–> |
RRC CONNECTION RELEASE COMPLETE |
– |
– |
|
– |
EXCEPTION : Step 18a1 to 18b6 describe behaviour that depends on whether a UE that has a PDP context activated on UTRAN |
– |
– |
– |
– |
|
18a1 |
If PDP context is not active: Check: Does the test result of generic test procedure in TS 36.508 Table 6.4.2.7A-2 indicate that the UE is camped on E-UTRAN Cell 1? |
– |
– |
2 |
– |
|
18b1 |
If PDP context is active: Check: Does the test result of generic test procedure in TS 36.508 Table 6.4.2.7A-1 is performed and the UE is camped on E-UTRAN Cell 1? |
– |
– |
2 |
– |
|
18b2 |
The UE transmits a RRCConnectionRequest message on E-UTRAN Cell1 |
–> |
RRC: RRCConnectionRequest |
– |
– |
|
18b3 |
SS transmit an RRCConnectionSetup message |
<– |
RRC: RRCConnectionSetup |
– |
– |
|
18b4 |
The UE transmits a RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a EMM SERVICE REQUEST message. |
–> |
RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST |
– |
– |
|
18b5 |
SS transmits a SERVICE REJECT with cause Protocol error, unspecified |
<– |
SERVICE REJECT |
– |
– |
|
18b6 |
The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE. |
<– |
RRC: RRCConnectionRelease |
– |
– |
|
NOTE: pc_UTRA_FeatrGrp_2 is always set to TRUE when pc_UTRA_CompressedModeRequired is TRUE |
|||||
8.1.3.7.3.3 Specific message or IE contents
Table 8.1.3.7.3.3-0: Conditions for specific message contents
in Table 8.1.3.7.3.3-1
|
Condition |
Explanation |
|
Band > 64 |
If E-UTRA band > 64 is selected |
Table 8.1.3.7.3.3-1: System Information Block type 19 for Cell 5 (preamble and all steps, Table 8.1.3.7.3.2-1)
|
Derivation Path: 36.508 table Table 4.4.4.1-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SysInfoType19 ::= SEQUENCE { |
|||
|
utra-PriorityInfoList SEQUENCE { |
|||
|
utra-ServingCell SEQUENCE { |
|||
|
priority |
4 |
||
|
} |
|||
|
} |
|||
|
eutra-FrequencyAndPriorityInfoList SEQUENCE (SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE |
1 entry |
||
|
earfcn[1] |
Downlink EARFCN of Cell 1 |
||
|
priority[1] |
3 |
||
|
} |
|||
|
v920NonCriticalExtensions SEQUENCE { |
Band > 64 |
||
|
earfcn [1] |
Same downlink EARFCN as used for Cell 1 |
||
|
priority [1] |
3 |
||
|
} |
|||
|
} |
|||
Table 8.1.3.7.3.3-2: RRC CONNECTION REQUEST (step 2, Table 8.1.3.7.3.2-1)
|
Derivation path: 34.108 default RRC CONNECTION REQUEST in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA TDD |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Pre-redirection info |
The presence of this IE indicates the UE support of radio access technologies that the UE could be directed to |
||
|
Support of E-UTRA FDD |
TRUE |
E-UTRA-FDD |
|
|
Support of E-UTRA TDD |
TRUE |
E-UTRA-TDD |
|
Table 8.1.3.7.3.3-3: MEASUREMENT CONTROL (step 6Aa1, Table 8.1.3.7.3.2-1)
|
Derivation Path: 36.508, clause 4.7B.1 Table 4.7B.1-3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CHOICE Measurement type |
Inter-RAT measurement |
|||
|
CHOICE report criteria |
Inter-RAT measurement reporting criteria |
|||
|
Parameters required for each event |
1 entry |
|||
|
Inter-RAT event identity |
3c |
|||
|
Threshold own system |
Not present |
|||
|
W |
Not present |
|||
|
DPCH Compressed mode status info |
UTRA CM-Support |
|||
|
TGPS reconfiguration CFN |
(Current CFN + (256 – TTI/10msec))mod 256 |
|||
|
Transmission gap pattern sequence |
1 entry |
|||
|
TGPSI |
1 |
|||
|
TGPS Status Flag |
activate |
|||
|
TGCFN |
(Current CFN + (256 – TTI/10msec))mod 256 |
|||
|
DPCH Compressed mode status info |
Not Present |
UTRA CM-Not Supported |
||
|
Condition |
Explanation |
|
UTRA CM-Supported |
UTRAN Compressed Mode configuration supported |
|
UTRA CM-Not Supported |
UTRAN Compressed Mode configuration not supported |
Table 8.1.3.7.3.3-4: RRC CONNECTION RELEASE (step 15, Table 8.1.3.7.3.2-1)
|
Derivation path: 34.108 default RRC CONNECTION RELEASE in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA TDD |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
N308 |
1 |
||
|
Redirection info |
|||
|
Frequency info |
Omitted |
||
|
Inter-RAT info |
E-UTRA |
||
|
E-UTRA target info |
|||
|
E-UTRA Target Frequency Info List |
1 Entry |
||
|
FDD |
E-UTRA-FDD |
||
|
DL Carrier frequency |
The DL Carrier frequency of Cell 1 |
||
|
Blacklisted cells per freq list |
Omitted |
||
|
DL Carrier frequency |
65535 |
Band > 64 |
|
|
TDD |
E-UTRA-TDD |
||
|
DL Carrier frequency |
The DL Carrier frequency of Cell 1 |
||
|
Blacklisted cells per freq list |
Omitted |
||
|
DL Carrier frequency |
65535 |
Band > 64 |
|
|
E-UTRA Target Frequency Info extension List |
Band > 64 |
||
|
EARFCN extension |
EARFCN of the downlink Cell 1 carrier frequency |
||
Table 8.1.3.7.3.3-5: PHYSICAL CHANNEL RECONFIGURATION (step 6a1, Table 8.1.3.7.3.2-1)
|
Derivation path: 36.508, clause 4.7B.1 Table 4.7B.1-5 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
CHOICE UL/DL Mode |
UL and DL, UL only or DL only (depending on the UE capability) |
||
|
Downlink compressed mode method |
SF/2(or not sent, depending on the UE capability) |
||
|
Uplink compressed mode method |
SF/2(or not sent, depending on the UE capability) |
||
Table 8.1.3.7.3.3-6: SERVICE REJECT (step 18b5, Table 8.1.3.7.3.2-1)
|
Derivation Path: 36.508 table 4.7.2-22 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EMM cause |
‘01101111’B |
Protocol error, unspecified |
||
8.1.3.8 RRC connection release / Redirection from E-UTRAN to GERAN
8.1.3.8.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo set to geran }
then { UE enters Idle mode on GERAN Cell included in IE redirectedCarrierInfo }
}
8.1.3.8.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, a UE shall attempt to camp on the last cell for which it was in RRC_CONNECTED or any cell on a frequency or frequency of RAT assigned by RRC in the state transition message.
…
8.1.3.8.3 Test description
8.1.3.8.3.1 Pre-test conditions
System Simulator:
– 2 cells, one E-UTRA and one GERAN cell and different location areas:
– Cell 1 E-UTRA serving cell (priority 4 default)
– Cell 24 GERAN neighbouring cell (priority 3)
– The parameters settings and power levels for Cell 1 and Cell 24 are selected according to [18], [5], [25] and Table 8.1.3.8.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 24 can take place (GERAN priority is lower than serving and S Cell 1 > Thresh Cell 1,low)
– System information combination 5 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on cell 1 according to [18].
8.1.3.8.3.2 Test procedure sequence
Table 8.1.3.6.3.2-0 shows the cell power levels after the preamble.
Table 8.1.3.8.3.2-0: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 24 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-75 |
– |
The power levels are such that camping on Cell 1 is guaranteed. |
|
GERAN Cell Power |
dBm |
– |
-70 |
||
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-115 |
– |
The power levels are such that reselection back to cell 1 should not occur |
|
GERAN Cell Power |
dBm |
-70 |
Table 8.1.3.8.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message (IE redirectedCarrierInfo including startingARFCN of Cell 24). |
<– |
RRCConnectionRelease |
– |
– |
|
1A |
The UE sends a CHANNEL REQUEST message on the cell 24 |
–> |
CHANNEL REQUEST |
– |
– |
|
1B |
An uplink TBF is established in order to allow the UE to transmit a ROUTING AREA UPDATE REQUEST message signalling. |
– |
– |
– |
– |
|
1C |
The UE transmits a ROUTING AREA UPDATE REQUEST message. |
–> |
ROUTING AREA UPDATING REQUEST |
– |
– |
|
1D |
The SS changes cell 1 level according to the row “T1” in table 8.1.3.8.3.2-0 |
||||
|
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.9 steps 4-11 indicate that the UE is camped on GERAN Cell 24? NOTE: The UE completes the RAU procedure. |
– |
– |
1 |
– |
8.1.3.8.3.3 Specific message or IE contents
Table 8.1.3.8.3.3-1: Void
Table 8.1.3.8.3.3-2: SystemInformationBlockType7 for cell 1 (preamble and all steps, Table 8.1.3.8.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-6 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType7 ::= SEQUENCE { |
|||
|
carrierFreqsInfoList SEQUENCE (SIZE (1..maxGNFG)) OF SEQUENCE { |
|||
|
carrierFreqs SEQUENCE [n] { |
|||
|
startingARFCN |
Same as cell 24 |
||
|
bandIndicator |
Same as cell 24 |
||
|
followingARFCNs CHOICE { |
|||
|
equallySpacedARFCNs SEQUENCE { |
|||
|
arfcn-Spacing |
Same as cell 24 |
||
|
numberOfFollowingARFCNs |
Same as cell 24 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
commonInfo SEQUENCE { |
|||
|
cellReselectionPriority |
3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.8.3.3-3: RRCConnectionRelease message (step 1, Table 8.1.3.8.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo CHOICE { |
|||
|
geran SEQUENCE { |
|||
|
startingARFCN |
Downlink ARFCN of Cell 24 |
||
|
bandIndicator |
The same band indicator of the Cell 24 |
||
|
followingARFCNs CHOICE { |
|||
|
explicitListOfARFCNs |
0 Entries |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.9 RRC connection release / Redirection from E-UTRAN to CDMA2000-HRPD
8.1.3.9.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo set to cdma2000-HRPD }
then { UE enters cdma2000-HRPD mode }
}
8.1.3.9.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> use the idle mobility parameters broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, a UE shall attempt to camp on the last cell for which it was in RRC_CONNECTED or any cell on a frequency or frequency of RAT assigned by RRC in the state transition message.
…
8.1.3.9.3 Test description
8.1.3.9.3.1 Pre-test conditions
System Simulator:
– 2 cells, one E-UTRA and one HRPD cell:
– Cell 1 E-UTRA serving cell
– Cell 15 suitable neighbour HRPD cell
– The parameters settings and power levels for Cell 1 and Cell 15 are selected according to [18], [xx] and Table 8.1.3.9.3.2-1 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 15 can take place (hrpd priority is lower than serving and S Cell 1 > Thresh Cell 1,low).
– System information combination 6 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
Note: UE is not pre-registered in Cell 15.
8.1.3.9.3.2 Test procedure sequence
Table 8.1.3.9.3.2-1 shows the cell power levels after the preamble.
Table 8.1.3.9.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 15 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-75 |
– |
The power levels are such that camping on Cell 1 is guaranteed. |
|
Îor/Ioc |
dB |
– |
-5 |
||
|
Ioc |
dBm/1.23 MHz |
– |
-55 |
||
|
Pilot Ec /Io (Note 1) |
dB |
– |
-6 |
||
|
Note 1: This parameter is not directly settable, but is derived by calculation from the other parameters set by the SS. |
|||||
Table 8.1.3.9.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message (IE redirectedCarrierInfo including cdma2000-HRPD of Cell 15). |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Check: Does the UE transmit an Access Probe on Cell 15 to initiate registration? |
–> |
Access Probe |
1 |
P |
8.1.3.9.3.3 Specific message or IE contents
Table 8.1.3.9.3.3-1: Void
Table 8.1.3.9.3.3-2: RRCConnectionRelease (step 1, Table 8.1.3.9.3.2-2)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo CHOICE { |
|||
|
cdma2000-HRPD |
cdma2000-CarrierInfo for Cell 15 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.10 RRC connection release / Redirection from E-UTRAN to CDMA2000-1xRTT
8.1.3.10.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo set to cdma2000-1xRTT }
then { UE enters cdma2000-1xRTT mode }
}
8.1.3.10.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, a UE shall attempt to camp on the last cell for which it was in RRC_CONNECTED or any cell on a frequency or frequency of RAT assigned by RRC in the state transition message.
…
8.1.3.10.3 Test description
8.1.3.10.3.1 Pre-test conditions
System Simulator:
– 2 cells, one E-UTRA and one 1xRTT cell:
– Cell 1 E-UTRA serving cell
– Cell 19 suitable neighbour 1xRTT cell
– The parameters settings and power levels for Cell 1 and Cell 19 are selected according to [18] and Table 8.1.3.10.3.2-1 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 19 can take place (1xRTT priority is lower than serving and S Cell 1 > Thresh Cell 1,low).
– System information combination 6 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
– UE is not pre-registered in Cell 19.
Preamble:
– The UE is in state Generic RB Established (state 3) on cell 1 according to [18].
8.1.3.10.3.2 Test procedure sequence
Table 8.1.3.10.3.2-1 shows the cell power levels after the preamble.
Table 8.1.3.10.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 19 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-75 |
– |
The power levels are such that camping on Cell 1 is guaranteed. |
|
Îor/Ioc |
dB |
– |
0 |
||
|
Pilot Ec/ Ior |
dB |
– |
-7 |
||
|
Ioc |
dBm/1.23 MHz |
– |
-75 |
||
|
CPICH_Ec/Io (Note 1) |
dB |
– |
-10 |
||
|
Note 1: This parameter is not directly settable, but is derived by calculation from the other parameters set by the SS. |
|||||
Table 8.1.3.10.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Check: Does the UE transmit an Access Probe on Cell 19 to initiate registration? |
–> |
Access Probe |
1 |
P |
8.1.3.10.3.3 Specific message or IE contents
Table 8.1.3.10.3.3-1: Void
Table 8.1.3.10.3.3-2: RRCConnectionRelease (step 1, Table 8.1.3.10.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo CHOICE { |
|||
|
cdma2000-1xRTT |
cdma2000-CarrierInfo for Cell 19 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.11 RRC connection release / Redirection to another E-UTRAN band
8.1.3.11.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with E-UTRA CarrierFreq on different E-UTRAN band }
then { UE enters RRC_IDLE state on new E-UTRA frequency included in IE redirectedCarrierInfo }
}
8.1.3.11.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.8.3, 5.3.12 and TS 36.304, clauses 5.2.4.1, 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.4.1]
…
UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
…
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on an EUTRA carrier. If no suitable cell is found, the UE shall perform a cell selection starting with Stored Information Cell Selection procedure in order to find a suitable cell to camp on.
…
8.1.3.11.3 Test description
8.1.3.11.3.1 Pre-test conditions
System Simulator:
– 2 cells on different E-UTRA frequencies and different tracking areas:
– Cell 1 serving cell
– Cell 10 suitable neighbour inter-band cell
– Cell power levels are selected according to [18] so that camping on Cell 1 is guaranteed
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) according to [18] on cell 1.
8.1.3.11.3.2 Test procedure sequence
Table 8.1.3.11.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message (IE redirectedCarrierInfo including eutra of Cell 10). |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Check: does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 10? |
– |
– |
1 |
– |
8.1.3.11.3.3 Specific message contents
Table 8.1.3.11.3.3-1: Conditions for specific message contents in table 8.1.3.11.3.3-2, 8.1.3.11.3.3-2A and 8.1.3.11.3.3-3
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.11.3.3-2: SystemInformationBlockType5 for cell 1 (preamble and all steps, Table 8.1.3.11.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[n] |
Same downlink EARFCN as used for Cell 10 |
||
|
dl-CarrierFreq[n] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[n] |
3 |
Cell 1 |
|
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[n] |
Same downlink EARFCN as used for Cell 10 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.11.3.3-2A: SystemInformationBlockType5 for cell 10 (preamble and all steps, Table 8.1.3.11.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[n] |
Same downlink EARFCN as used for Cell 1 |
||
|
dl-CarrierFreq[n] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[n] |
3 |
||
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[n] |
Same downlink EARFCN as used for Cell 1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.11.3.3-3: RRCConnectionRelease message (step 1, Table 8.1.3.11.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo ::= CHOICE { |
|||
|
eutra |
Downlink EARFCN of cell 10 |
||
|
} |
|||
|
redirectedCarrierInfo {} |
Not present |
Band > 64 |
|
|
nonCriticalExtension SEQUENCE { |
Band > 64 |
||
|
lateNonCriticalExtension SEQUENCE { |
|||
|
redirectedCarrierInfo-v9e0 SEQUENCE { |
|||
|
eutra-v9e0 |
Downlink EARFCN of cell 10 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.11a RRC connection release / Redirection to another E-UTRAN band / Between FDD and TDD
8.1.3.11a.1 Test Purpose (TP)
(1)
with { UE in E-UTRA FDD RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with E-UTRA CarrierFreq on different E-UTRAN TDD band }
then { UE enters RRC_IDLE state on new E-UTRA TDD frequency included in IE redirectedCarrierInfo }
}
(2)
with { UE in E-UTRA TDD RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with E-UTRA CarrierFreq on different E-UTRAN FDD band }
then { UE enters RRC_IDLE state on new E-UTRA FDD frequency included in IE redirectedCarrierInfo }
}
8.1.3.11a.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.8.3, 5.3.12 and TS 36.304, clauses 5.2.4.1, 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60ms 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> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
…
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
…
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
…
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.4.1]
…
UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
…
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on an EUTRA carrier. If no suitable cell is found, the UE shall perform a cell selection starting with Stored Information Cell Selection procedure in order to find a suitable cell to camp on.
…
8.1.3.11a.3 Test description
8.1.3.11a.3.1 Pre-test conditions
System Simulator:
– 2 cells on different E-UTRA bands which are in different E-UTRA mode (E-UTRA FDD and E-UTRA TDD) and PLMNs, both PLMNs are UE’s EPLMN.
– Cell 1 is FDD cell and Cell 28 is TDD cell
–
– Each cell has only a single PLMN identity. The PLMNs are identified in the test by the identifiers in Table 8.1.3.11a.3.1-1.
Table 8.1.3.11a.3.1-1: PLMN identifiers
|
Cell |
PLMN name |
|
1 |
PLMN1 |
|
28 |
PLMN2 |
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 and Table 6.3.1.2-2 is used in E-UTRA cells.
UE:
None.
Preamble:
- The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508[18] clause 4.5.2.3 except that the ATTACH ACCEPT message indicates PLMN2 in the Equivalent PLMN list as described in Table 8.1.3.11a.3.3-3.
– The UE is in state Generic RB Established (state 3) according to [18] on Cell 1.
8.1.3.11a.3.2 Test procedure sequence
Table 8.1.3.11a.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS transmits an RRCConnectionRelease message (IE redirectedCarrierInfo including eutra CarrierFreq of Cell 28. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 28? NOTE: The TAU is accepted with PLMN1 listed as an Equivalent PLMN |
– |
– |
1 |
– |
|
3 |
Generic test procedure in TS 36.508 subclause 4.5.3.3 is performed to make the UE enter state Generic RB Established (state 3) on Cell 28. |
– |
– |
– |
– |
|
4 |
SS transmits an RRCConnectionRelease message (IE redirectedCarrierInfo including eutra CarrierFreq of Cell 1). |
<– |
RRCConnectionRelease |
– |
– |
|
5 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 1? NOTE: The TAU is accepted with PLMN2 listed as an Equivalent PLMN |
– |
– |
2 |
– |
.
8.1.3.11a.3.3 Specific message contents
Table 8.1.3.11a.3.3-0: Conditions for specific message contents
in Tables 8.1.3.11a.3.3-1 and 8.1.3.11a.3.3-2.
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.11a.3.3-1: RRCConnectionRelease message (step 1, Table 8.1.3.11a.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo ::= CHOICE { |
|||
|
eutra |
Downlink EARFCN of Cell 28 |
||
|
} |
|||
|
redirectedCarrierInfo {} |
Not present |
Band > 64 |
|
|
nonCriticalExtension SEQUENCE { |
Band > 64 |
||
|
lateNonCriticalExtension SEQUENCE { |
|||
|
redirectedCarrierInfo-v9e0 SEQUENCE { |
|||
|
eutra-v9e0 |
Downlink EARFCN of cell 28 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.11a.3.3-2: RRCConnectionRelease message (step 4, Table 8.1.3.11a.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
redirectedCarrierInfo ::= CHOICE { |
|||
|
eutra |
Downlink EARFCN of cell 1 |
||
|
} |
|||
|
redirectedCarrierInfo {} |
Not present |
Band > 64 |
|
|
nonCriticalExtension SEQUENCE { |
Band > 64 |
||
|
lateNonCriticalExtension SEQUENCE { |
|||
|
redirectedCarrierInfo-v9e0 SEQUENCE { |
|||
|
eutra-v9e0 |
Downlink EARFCN of cell 1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.11a.3.3-3: ATTACH ACCEPT for Cell 1 (preamble)
|
Derivation path: 36.508 Table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Equivalent PLMNs |
PLMN2 |
||
Table 8.1.3.11a.3.3-4: TRACKING AREA UPDATE ACCEPT for Cell 28 (step 2, Table 8.1.3.11a.3.2-2)
|
Derivation path: 36.508 Table 4.7.2-24 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Equivalent PLMNs |
PLMN1 |
||
Table 8.1.3.11a.3.3-5: TRACKING AREA UPDATE ACCEPT for Cell 1 (step 5, Table 8.1.3.11a.3.2-2)
|
Derivation path: 36.508 Table 4.7.2-24 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Equivalent PLMNs |
PLMN2 |
||
8.1.3.12 RRC connection release / Success / With priority information / Inter-band
8.1.3.12.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_IDLE state having received an RRCConnectionRelease message with the freqPriorityListEUTRA with higher priority frequency in different band}
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher priority band }
then { UE reselects the cell which belongs to the higher priority band}
}
8.1.3.12.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.8.3 and TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> 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> 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:
…
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:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;
[TS 36.304, clause 5.2.4.1]
Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an E-UTRAN frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight network configured values), irrespective of any other priority value allocated to this frequency. The UE shall delete priorities provided by dedicated signalling when:
– the UE enters RRC_CONNECTED state; or
– the optional validity time of dedicated priorities (T320) expires; or
– a PLMN selection is performed on request by NAS [5].
NOTE 1: Equal priorities between RATs are not supported.
The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
The UE shall not consider any black listed cells as candidate for cell reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e., T320 in E-UTRA, T322 in UTRA and T3230 in GERAN), if configured, at inter-RAT cell (re)selection.
NOTE 2: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.
[TS 36.304, clause 5.2.4.2]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
– If the serving cell fulfils Srxlev > SIntraSearchP and Squal > SIntraSearchQ, the UE may choose not to perform intra-frequency measurements.
– Otherwise, the UE shall perform intra-frequency measurements.
– The UE shall apply the following rules for E-UTRAN inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:
– For an E-UTRAN inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current E-UTRA frequency the UE shall perform measurements of higher priority E-UTRAN inter-frequency or inter-RAT frequencies according to [10].
– For an E-UTRAN inter-frequency with an equal or lower reselection priority than the reselection priority of the current E-UTRA frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current E-UTRAN frequency:
– If the serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE may choose not to perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority.
– Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority EUTRAN or UTRAN RAT/ frequency fulfils Squal > ThreshX, HighQ during a time interval TreselectionRAT; or
– A cell of a higher priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
- More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based on ranking for Intra-frequency cell reselection as defined in sub-clause 5.2.4.6.
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority EUTRAN or UTRAN RAT/ frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT; or
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a higher priority RAT/ frequency shall take precedence over a lower priority RAT/ frequency, if multiple cells of different priorities fulfil the cell reselection criteria.
For cdma2000 RATs, Srxlev is equal to -FLOOR(-2 x 10 x log10 Ec/Io) in units of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, ThreshX, HighP and ThreshX, LowP are equal to -1 times the values signalled for the corresponding parameters in the system information.
In all the above criteria the value of TreselectionRAT is scaled when the UE is in the medium or high mobility state as defined in subclause 5.2.4.3.1. If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
– If the highest-priority frequency is an E-UTRAN frequency, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria according to section 5.2.4.6;
– If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.
8.1.3.12.3 Test description
8.1.3.12.3.1 Pre-test conditions
System Simulator:
– Cell 1, Cell 3 and Cell 10.
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
NOTE 3: For Cell 10 TAI is set to TAI-2
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
8.1.3.12.3.2 Test procedure sequence
Table 8.1.3.12.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.3.12.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 3 |
Cell 10 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
"off” |
"off” |
The power level values are assigned to satisfy SrxlevCell 1 > Snonintrasearch. (NOTE 1) |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-73 |
-73 |
The power level values are assigned to satisfy both Threshx, low < SrxlevCell 3 and Threshx, high <SrxlevCell 10. |
|
NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1. |
||||||
Table 8.1.3.12.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message including the freqPriorityListEUTRA on Cell 1. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state on Cell 1. |
– |
– |
– |
– |
|
3 |
The SS changes Cell 1, Cell 3 and Cell 10 level according to the row "T1" in table 8.1.3.12.3.2-1. |
– |
– |
– |
– |
|
4 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 10? |
– |
– |
1 |
– |
8.1.3.12.3.3 Specific message contents
Table 8.1.3.12.3.3-0: Conditions for specific message contents
in Tables 8.1.3.12.3.3-1, 8.1.3.12.3.3-2 and 8.1.3.12.3.3-3
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.12.3.3-1: RRCConnectionRelease (step 1, Table 8.1.3.12.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
idleModeMobilityControlInfo SEQUENCE { |
|||
|
freqPriorityListEUTRA SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
3 entries |
||
|
carrierFreq[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
carrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[1] |
4 |
||
|
carrierFreq[2] |
Same downlink EARFCN as used for Cell 10 |
||
|
carrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[2] |
5 |
||
|
carrierFreq[3] |
Same downlink EARFCN as used for Cell 3 |
||
|
carrierFreq[3] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[3] |
1 |
||
|
} |
|||
|
freqPriorityListGERAN |
Not present |
||
|
freqPriorityListUTRA-FDD |
Not present |
||
|
freqPriorityListUTRA-TDD |
Not present |
||
|
bandClassPriorityListHRPD |
Not present |
||
|
bandClassPriorityList1XRTT |
Not present |
||
|
t320 |
Not present |
||
|
} |
|||
|
nonCriticalExtension |
Band > 64 |
||
|
nonCriticalExtension |
|||
|
idleModeMobilityControlInfo-v9e0 SEQUENCE { |
|||
|
freqPriorityListEUTRA-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
carrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
carrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 10 |
||
|
carrierFreq-v9e0[3] |
Same downlink EARFCN as used for Cell 3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.12.3.3-2: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table 8.1.3.12.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
dl-CarrierFreq[2] |
Same downlink EARFCN as used for Cell 10 |
||
|
dl-CarrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
threshX-Low[1] |
11 |
||
|
threshX-High[2] |
11 |
||
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 10 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.12.3.3-3: SystemInformationBlockType5 for Cell 10 (all steps, Table 8.1.3.12.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
dl-CarrierFreq[2] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority [2] |
1 |
||
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
dl-CarrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.12a RRC connection release / Success / With priority information / Inter- band / Between FDD and TDD
8.1.3.12a.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_IDLE state in LTE FDD mode having received an RRCConnectionRelease message with the freqPriorityListEUTRA with higher priority frequency on different LTE TDD band }
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher priority frequency on different LTE TDD band }
then { UE reselects the cell which belongs to the higher priority frequency on different LTE TDD band }
}
(2)
with { UE in E-UTRA RRC_IDLE state in LTE TDD mode having received an RRCConnectionRelease message with the freqPriorityListEUTRA with lower priority frequency on different LTE FDD band }
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the lower priority frequency on different LTE FDD band }
then { UE reselects the cell which belongs to the lower priority frequency on different LTE FDD band }
}
8.1.3.12a.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.8.3 and TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> 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> 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:
…
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:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;
[TS 36.304, clause 5.2.4.1]
Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an E-UTRAN frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight network configured values), irrespective of any other priority value allocated to this frequency. The UE shall delete priorities provided by dedicated signalling when:
– the UE enters RRC_CONNECTED state; or
– the optional validity time of dedicated priorities (T320) expires; or
– a PLMN selection is performed on request by NAS [5].
NOTE 1: Equal priorities between RATs are not supported.
The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
The UE shall not consider any black listed cells as candidate for cell reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e., T320 in E-UTRA, T322 in UTRA and T3230 in GERAN), if configured, at inter-RAT cell (re)selection.
NOTE 2: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.
[TS 36.304, clause 5.2.4.2]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
– If the serving cell fulfils Srxlev > SIntraSearchP and Squal > SIntraSearchQ, the UE may choose not to perform intra-frequency measurements.
– Otherwise, the UE shall perform intra-frequency measurements.
– The UE shall apply the following rules for E-UTRAN inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:
– For an E-UTRAN inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current E-UTRA frequency the UE shall perform measurements of higher priority E-UTRAN inter-frequency or inter-RAT frequencies according to [10].
– For an E-UTRAN inter-frequency with an equal or lower reselection priority than the reselection priority of the current E-UTRA frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current E-UTRAN frequency:
– If the serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE may choose not to perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority.
– Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority EUTRAN or UTRAN RAT/ frequency fulfils Squal > ThreshX, HighQ during a time interval TreselectionRAT; or
– A cell of a higher priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
- More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based on ranking for Intra-frequency cell reselection as defined in sub-clause 5.2.4.6.
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority EUTRAN or UTRAN RAT/ frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT; or
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a higher priority RAT/ frequency shall take precedence over a lower priority RAT/ frequency, if multiple cells of different priorities fulfil the cell reselection criteria.
For cdma2000 RATs, Srxlev is equal to -FLOOR(-2 x 10 x log10 Ec/Io) in units of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, ThreshX, HighP and ThreshX, LowP are equal to -1 times the values signalled for the corresponding parameters in the system information.
In all the above criteria the value of TreselectionRAT is scaled when the UE is in the medium or high mobility state as defined in subclause 5.2.4.3.1. If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
– If the highest-priority frequency is an E-UTRAN frequency, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria according to section 5.2.4.6;
– If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.
8.1.3.12a.3 Test description
8.1.3.12a.3.1 Pre-test conditions
System Simulator:
– Cell 1 and Cell 2 are FDD cell and Cell 10 is TDD cell
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 and Table 6.3.1.2-2 is used in E-UTRA cells.
NOTE 1: For Cell 10 TAI is set to TAI-2
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
8.1.3.12a.3.2 Test procedure sequence
Table 8.1.3.12a.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.3.12a.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
Cell 10 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
"off” |
"off” |
The power level values are assigned to satisfy SrxlevCell 1 > Sintrasearch. (NOTE 1) |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
-73 |
-73 |
The power level values are assigned to satisfy SrxlevCell 10 > Threshx, high when reselect to higher priority Cell 10 from lower priority Cell 1 |
|
T2 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
-73 |
-85 |
The power level values are assigned to satisfy both SrxlevCell 2 > Threshx, low (good enough ) and SrxlevCell 10 < Threshserving,low(bad enough) |
|
NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1. |
||||||
Table 8.1.3.12a.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message including the freqPriorityListEUTRA on Cell 1. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state on Cell 1. |
– |
– |
– |
– |
|
3 |
The SS changes Cell 2 and Cell 10 levels according to the row "T1" in table 8.1.3.12a.3.2-1. |
– |
– |
– |
– |
|
4-8 |
Check: Does the test result of generic test procedure in TS 36.508 steps 1 to 5 of subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 10?” |
– |
– |
1 |
– |
|
9 |
The SS transmits an RRCConnectionRelease message including the freqPriorityListEUTRA on Cell 10. |
<– |
RRCConnectionRelease |
– |
– |
|
10 |
Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state on Cell 10. |
– |
– |
– |
– |
|
11 |
The SS changes Cell 1 and Cell 10 level according to the row "T2" in table 8.1.3.12a.3.2-1. |
– |
– |
– |
– |
|
12-17 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 2? |
– |
– |
2 |
– |
8.1.3.12a.3.3 Specific message contents
Table 8.1.3.12a.3.3-0: Conditions for specific message contents
in Tables 8.1.3.12a.3.3-1, 8.1.3.12a.3.3-2 and 8.1.3.12a.3.3-4.
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.12a.3.3-1: RRCConnectionRelease (step 1 and step 9, Table 8.1.3.12a.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
idleModeMobilityControlInfo SEQUENCE { |
|||
|
freqPriorityListEUTRA SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
2 entries |
||
|
carrierFreq[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
carrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[1] |
4 |
||
|
carrierFreq[2] |
Same downlink EARFCN as used for Cell 10 |
||
|
carrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
cellReselectionPriority[2] |
5 |
||
|
} |
|||
|
freqPriorityListGERAN |
Not present |
||
|
freqPriorityListUTRA-FDD |
Not present |
||
|
freqPriorityListUTRA-TDD |
Not present |
||
|
bandClassPriorityListHRPD |
Not present |
||
|
bandClassPriorityList1XRTT |
Not present |
||
|
t320 |
Not present |
||
|
} |
|||
|
nonCriticalExtension |
Band > 64 |
||
|
nonCriticalExtension |
|||
|
idleModeMobilityControlInfo-v9e0 SEQUENCE { |
|||
|
freqPriorityListEUTRA-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
carrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 1 |
||
|
carrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 10 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.12a.3.3-2: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table 8.1.3.12a.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
||||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
|
SystemInformationBlockType5 ::= SEQUENCE { |
||||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
||||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 10 |
|||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
||
|
threshX-High[1] |
11 |
Actual value of threshold = IE value * 2 [dB] |
||
|
threshX-Low[1] |
11 |
Actual value of threshold = IE value * 2 [dB] |
||
|
} |
||||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
||||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 10 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.3.12a.3.3-3: SystemInformationBlockType3 for Cell 10 (preamble and all steps, Table 8.1.3.12a.3.2-2)
|
Derivation Path: TS 36.508 [7] clause 4.4.3.3, Table 4.4.3.3-2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
cellReselectionServingFreqInfo SEQUENCE { |
|||
|
threshServingLow |
14 (28 dB) |
28 is actual value in dB (14 * 2 dB) |
|
|
} |
|||
|
intraFreqCellReselectionInfo SEQUENCE { |
|||
|
s-IntraSearch |
0 (0 dB) |
||
|
} |
|||
Table 8.1.3.12a.3.3-4: SystemInformationBlockType5 for Cell 10 (preamble and all steps, Table 8.1.3.12a.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
||||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
|
SystemInformationBlockType5 ::= SEQUENCE { |
||||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
||||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 1 |
|||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
||
|
threshX-High[1] |
11 |
Actual value of threshold = IE value * 2 [dB] |
||
|
threshX-Low[1] |
11 |
Actual value of threshold = IE value * 2 [dB] |
||
|
} |
||||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
||||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 1 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.3.12a.3.3-5: SystemInformationBlockType3 for Cells 1 and 2 (preamble and all steps, Table 8.1.3.12a.3.2-2)
|
Derivation Path: TS 36.508 [7] clause 4.4.3.3, Table 4.4.3.3-2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
intraFreqCellReselectionInfo SEQUENCE { |
|||
|
s-IntraSearch |
0 (0 dB) |
||
|
} |
|||
8.1.3.12b RRC connection release / Success / With priority information / Inter-band (Single frequency operation in source band)
The scope and description of the present TC is the same as test case 8.1.3.12 with the following differences:
– Cell configuration: Cell 28 with frequency f6 replaces Cell 3 with frequency f2.
8.1.3.13 LTE RRC connection release / Success / With idle mode measurement information from SIB5
8.1.3.13.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message with the measIdleConfig and SIB5 includes measIdleCarrierListEUTRA-r15 }
then { UE enters RRC_IDLE state }
}
(2)
with { UE in E-UTRA RRC_IDLE state after receiving RRCConnectionRelease message with measIdleConfig }
ensure that {
when { UE receives RRCConnectionSetup after sending RRCConnectionRequest and SIB2 includes idleModeMeasurements }
then { UE sends RRCConnectionComplete message including idleMeasAvailable }
}
(3)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives UEInformationRequest message with idleModeMeasurementReq included }
then { UE sends UEInformationResponse message including measResultListIdle }
}
8.1.3.13.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.4, 5.3.8.3, 5.6.5.3 and 5.6.20.2.
[TS 36.331, clause 5.3.3.4]
The UE shall:
- set the content of RRCConnectionSetupComplete message as follows:
2> if the UE is connected to EPC:
3> except for NB-IoT:
4> if the SIB2 contains idleModeMeasurements, and the UE has IDLE mode measurement information available in VarMeasIdleReport:
5> include the idleMeasAvailable;
[TS 36.331, clause 5.3.8.3]
The UE shall:
- 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> else:
3> store the measIdleCarrierListEUTRA received in SIB5 in VarMeasIdleConfig;
2> start performing idle mode measurements as specified in 5.6.20;
[TS 36.331, clause 5.6.5.3]
The UE shall:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and UE has stored VarMeasIdleReport:
2> set the measResultListIdle in the UEInformationResponse message to the value of idleMeasReport in the VarMeasIdleReport;
2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;
[TS 36.331, clause 5.6.20.2]
While T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig:
3> if UE supports carrier aggregation between serving carrier and the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry;
4> perform measurements in the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry;
NOTE: The fields s-NonIntraSearch in SystemInformationBlockType3 do not affect the UE measurement procedures in IDLE mode. How the UE performs measurements in IDLE mode is up to UE implementation as long as the requirements in TS 36.133 [16] are met for measurement reporting. UE is not required to perform idle measurements if SIB2 idle measurement indication is not configured.
4> if the measCellList is included:
5> consider PCell and cells identified by each entry within the measCellList to be applicable for idle mode measurement reporting;
4> else:
5> consider PCell and up to maxCellMeasIdle strongest identified cells whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold (if any) to be applicable for idle mode measurement reporting;
4> store measurement results for cells applicable for idle mode measurement reporting within the VarMeasIdleReport;
3> else:
4> do not consider the carrier frequency to be applicable for idle mode measurement reporting;
1> if validityArea is configured in VarMeasIdleConfig and UE reselects to a serving cell whose physical cell identity does not match any entry in validityArea for the corresponding carrier frequency:
2> stop T331;
8.1.3.13.3 Test description
8.1.3.13.3.1 Pre-test conditions
System Simulator:
– Cell 1, Cell 3 and Cell 6.
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
8.1.3.13.3.2 Test procedure sequence
Table 8.1.3.13.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.3.13.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 3 |
Cell 10 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-97 |
-97 |
Table 8.1.3.13.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message including the measIdleConfig on Cell 1. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Wait for 30 s for the UE to enter E-UTRA RRC_IDLE state on Cell 1 and do measurements over cells 1, 3 and 6. |
– |
– |
– |
– |
|
3 |
The SS sends RRC Paging message with UE S-TMSI on the cell 1. |
<– |
Paging |
||
|
4 |
Check: Does UE transmits an RRCConnectionRequest message on the cell 1? |
–> |
RRCConnectionRequest |
1 |
P |
|
5 |
The SS transmits a RRCConnectionSetup message. |
<– |
RRCConnectionSetup |
– |
– |
|
6 |
Check: Does the UE send RRCConnectionSetupComplete message with idleMeasAvailable? |
–> |
RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST |
2 |
P |
|
7 |
The SS transmits a SecurityModeCommand message to activate AS security. |
<– |
SecurityModeCommand |
– |
– |
|
8 |
The UE transmits a SecurityModeComplete message. |
–> |
SecurityModeComplete |
– |
– |
|
9 |
The SS transmits a RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0) according to 4.8.2.2.1.1, |
<– |
RRCConnectionReconfiguration |
– |
– |
|
10 |
The UE transmits an RRCConnectionReconfiguration complete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
11 |
The SS transmits UEInformationRequest message with idleModeMeasurementReq included. |
<– |
UEInformationRequest |
– |
– |
|
12 |
Check: Does UE send UEInformationResponse message including measResultListIdle? |
–> |
UEInformationResponse |
3 |
P |
8.1.3.13.3.3 Specific message contents
Table 8.1.3.13.3.3-0: Conditions for specific message contents
in Tables 8.1.3.13.3.3-1, 8.1.3.13.3.3-2 and 8.1.3.12.3.3-3
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.13.3.3-1: RRCConnectionRelease (step 1, Table 8.1.3.13.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier-DL |
||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
releaseCause |
other |
||
|
redirectedCarrierInfo |
Not present |
||
|
idleModeMobilityControlInfo |
Not present |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
drb-ContinueROHC-r15 |
Not present |
||
|
nextHopChainingCount-r15 |
Not present |
||
|
measIdleConfig-r15 |
MeasIdleConfigDedicated-r15 |
||
|
rrc-InactiveConfig-r15 |
Not present |
||
|
cn-Type-r15 |
Not present |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.13.3.3-2: MeasIdleConfigDedicated-r15 (step 1, Table 8.1.3.13.3.2-2)
|
Derivation Path: 36.331, clause 6.3.5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasIdleConfigDedicated-r15 ::= SEQUENCE { |
|||
|
measIdleCarrierListEUTRA-r15 |
Not present |
Provided by SIB5 |
|
|
measIdleDuration-r15 |
sec60 |
||
|
} |
|||
Table 8.1.3.13.3.3-3: SystemInformationBlockType2 for Cell 1 (preamble and all the steps in Table 8.1.3.13.3.2-2)
|
Derivation Path: 36.508, Table 4.4.3.3-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType2 ::= SEQUENCE { |
|||
|
idleModeMeasurements-r15 |
true |
||
|
} |
|||
Table 8.1.3.13.3.3-4: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table 8.1.3.12.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
dl-CarrierFreq[2] |
Same downlink EARFCN as used for Cell 6 |
||
|
dl-CarrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 6 |
||
|
} |
|||
|
} |
|||
|
measIdleConfigSIB-r15 SEQUENCE { |
|||
|
measIdleCarrierListEUTRA-r15 |
EUTRA-CarrierList-r15 |
||
|
} |
|||
|
} |
|||
Table 8.1.3.13.3.3-5: EUTRA-CarrierList-r15 (step 1, Table 8.1.3.12.3.2-2)
|
Derivation Path: 36.331, clause 6.3.5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EUTRA-CarrierList-r15 SEQUENCE ( |
2 entries |
||
|
MeasIdleCarrierEUTRA-r15[1] SEQUENCE { |
|||
|
carrierFreq-r15 |
Same downlink EARFCN as used for Cell 3 |
||
|
allowedMeasBandwidth-r15 |
mbw6 |
||
|
validityArea-r15 |
Not present |
||
|
measCellList-r15 |
Not present |
||
|
reportQuantities |
both |
||
|
qualityThreshold-r15 SEQUENCE { |
|||
|
idleRSRP-Threshold-r15 |
43 |
-97 dBm |
|
|
idleRSRQ-Threshold-r15 |
Not present |
||
|
} |
|||
|
} |
|||
|
MeasIdleCarrierEUTRA-r15[2] SEQUENCE { |
|||
|
carrierFreq-r15 |
Same downlink EARFCN as used for Cell 6 |
||
|
allowedMeasBandwidth-r15 |
mbw6 |
||
|
validityArea-r15 |
Not present |
||
|
measCellList-r15 |
Not present |
||
|
reportQuantities |
both |
||
|
qualityThreshold-r15 SEQUENCE { |
|||
|
idleRSRP-Threshold-r15 |
43 |
-97 dBm |
|
|
idleRSRQ-Threshold-r15 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.14 LTE RRC connection release / Success / With idle mode measurement information from RRCConnectionRelease
8.1.3.14.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message with the measIdleConfig with measIdleCarrierListEUTRA-r15 }
then { UE enters RRC_IDLE state }
}
(2)
with { UE in E-UTRA RRC_IDLE state after receiving RRCConnectionRelease message with measIdleConfig }
ensure that {
when { UE receives RRCConnectionSetup after sending RRCConnectionRequest and SIB2 includes idleModeMeasurements }
then { UE sends RRCConnectionComplete message including idleMeasAvailable }
}
(3)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives UEInformationRequest message with idleModeMeasurementReq included }
then { UE sends UEInformationResponse message including measResultListIdle }
}
8.1.3.14.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.4, 5.3.8.3, 5.6.5.3 and 5.6.20.2.
[TS 36.331, clause 5.3.3.4]
The UE shall:
- set the content of RRCConnectionSetupComplete message as follows:
2> if the UE is connected to EPC:
3> except for NB-IoT:
4> if the SIB2 contains idleModeMeasurements, and the UE has IDLE mode measurement information available in VarMeasIdleReport:
5> include the idleMeasAvailable;
[TS 36.331, clause 5.3.8.3]
The UE shall:
- 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;
2> start performing idle mode measurements as specified in 5.6.20;
[TS 36.331, clause 5.6.5.3]
The UE shall:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and UE has stored VarMeasIdleReport:
2> set the measResultListIdle in the UEInformationResponse message to the value of idleMeasReport in the VarMeasIdleReport;
2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;
[TS 36.331, clause 5.6.20.2]
While T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig:
3> if UE supports carrier aggregation between serving carrier and the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry;
4> perform measurements in the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry;
NOTE: The fields s-NonIntraSearch in SystemInformationBlockType3 do not affect the UE measurement procedures in IDLE mode. How the UE performs measurements in IDLE mode is up to UE implementation as long as the requirements in TS 36.133 [16] are met for measurement reporting. UE is not required to perform idle measurements if SIB2 idle measurement indication is not configured.
4> if the measCellList is included:
5> consider PCell and cells identified by each entry within the measCellList to be applicable for idle mode measurement reporting;
4> else:
5> consider PCell and up to maxCellMeasIdle strongest identified cells whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold (if any) to be applicable for idle mode measurement reporting;
4> store measurement results for cells applicable for idle mode measurement reporting within the VarMeasIdleReport;
3> else:
4> do not consider the carrier frequency to be applicable for idle mode measurement reporting;
1> if validityArea is configured in VarMeasIdleConfig and UE reselects to a serving cell whose physical cell identity does not match any entry in validityArea for the corresponding carrier frequency:
2> stop T331;
8.1.3.14.3 Test description
8.1.3.14.3.1 Pre-test conditions
System Simulator:
– Cell 1, Cell 3 and Cell 6.
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
8.1.3.14.3.2 Test procedure sequence
Table 8.1.3.14.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.3.14.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 3 |
Cell 10 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-97 |
-97 |
Table 8.1.3.14.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message including the measIdleConfig on Cell 1. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Wait for 30 s for the UE to enter E-UTRA RRC_IDLE state on Cell 1 and do measurements over cells 1, 3 and 6. |
– |
– |
– |
– |
|
3 |
The SS sends RRC Paging message with UE S-TMSI on the cell 1. |
<– |
Paging |
||
|
4 |
Check: Does UE transmit an RRCConnectionRequest message on the cell 1? |
–> |
RRCConnectionRequest |
1 |
P |
|
5 |
The SS transmits a RRCConnectionSetup message. |
<– |
RRCConnectionSetup |
– |
– |
|
6 |
Check: Does the UE send RRCConnectionSetupComplete message with idleMeasAvailable? |
–> |
RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST |
2 |
P |
|
7 |
The SS transmits a SecurityModeCommand message to activate AS security. |
<– |
SecurityModeCommand |
– |
– |
|
8 |
The UE transmits a SecurityModeComplete message. |
–> |
SecurityModeComplete |
– |
– |
|
9 |
The SS transmits a RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0) according to 4.8.2.2.1.1, |
<– |
RRCConnectionReconfiguration |
– |
– |
|
10 |
The UE transmits an RRCConnectionReconfiguration complete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
11 |
The SS transmits UEInformationRequest message with idleModeMeasurementReq included. |
<– |
UEInformationRequest |
– |
– |
|
12 |
Check: Does UE send UEInformationResponse message including measResultListIdle? |
–> |
UEInformationResponse |
3 |
P |
8.1.3.14.3.3 Specific message contents
Table 8.1.3.14.3.3-0: Conditions for specific message contents
in Table 8.1.3.14.3.3-4
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.14.3.3-1: RRCConnectionRelease (step 1, Table 8.1.3.14.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-15 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionRelease ::= SEQUENCE { |
||||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier-DL |
|||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
rrcConnectionRelease-r8 SEQUENCE { |
||||
|
releaseCause |
other |
|||
|
redirectedCarrierInfo |
Not present |
|||
|
idleModeMobilityControlInfo |
Not present |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
measIdleConfig-r15 |
MeasIdleConfigDedicated-r15 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.3.14.3.3-2: MeasIdleConfigDedicated-r15 (step 1, Table 8.1.3.14.3.2-2)
|
Derivation Path: 36.331, clause 6.3.5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasIdleConfigDedicated-r15 ::= SEQUENCE { |
|||
|
measIdleCarrierListEUTRA-r15 |
EUTRA-CarrierList-r15 |
||
|
measIdleDuration-r15 |
sec60 |
||
|
} |
|||
Table 8.1.3.14.3.3-3: EUTRA-CarrierList-r15 (step 1, Table 8.1.3.14.3.2-2)
|
Derivation Path: 36.331, clause 6.3.5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EUTRA-CarrierList-r15 SEQUENCE ( |
2 entries |
||
|
MeasIdleCarrierEUTRA-r15[1] SEQUENCE { |
|||
|
carrierFreq-r15 |
Same downlink EARFCN as used for Cell 3 |
||
|
allowedMeasBandwidth-r15 |
mbw6 |
||
|
validityArea-r15 |
Not present |
||
|
measCellList-r15 |
Not present |
||
|
reportQuantities |
both |
||
|
qualityThreshold-r15 SEQUENCE { |
|||
|
idleRSRP-Threshold-r15 |
43 |
-97 dBm |
|
|
idleRSRQ-Threshold-r15 |
Not present |
||
|
} |
|||
|
} |
|||
|
MeasIdleCarrierEUTRA-r15[2] SEQUENCE { |
|||
|
carrierFreq-r15 |
Same downlink EARFCN as used for Cell 6 |
||
|
allowedMeasBandwidth-r15 |
mbw6 |
||
|
validityArea-r15 |
Not present |
||
|
measCellList-r15 |
Not present |
||
|
reportQuantities |
both |
||
|
qualityThreshold-r15 SEQUENCE { |
|||
|
idleRSRP-Threshold-r15 |
43 |
-97 dBm |
|
|
idleRSRQ-Threshold-r15 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.14.3.3-4: SystemInformationBlockType2 for Cell 1 (preamble and all the steps in Table 8.1.3.14.3.2-2)
|
Derivation Path: 36.508, Table 4.4.3.3-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType2 ::= SEQUENCE { |
|||
|
idleModeMeasurements-r15 |
true |
||
|
} |
|||
Table 8.1.3.14.3.3-4: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table 8.1.3.14.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
dl-CarrierFreq[2] |
Same downlink EARFCN as used for Cell 6 |
||
|
dl-CarrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 6 |
||
|
} |
|||
|
} |
|||
|
} |
|||
8.1.3.15 LTE RRC connection release / Success / With idle mode measurement information / No idle mode measurement capability provided
8.1.3.15.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionRelease message with the measIdleConfig with measIdleCarrierListEUTRA-r15 }
then { UE enters RRC_IDLE state }
}
(2)
with { UE in E-UTRA RRC_IDLE state after receiving RRCConnectionRelease message with measIdleConfig }
ensure that {
when { UE receives RRCConnectionSetup after sending RRCConnectionRequest and SIB2 does not include idleModeMeasurements }
then { UE sends RRCConnectionComplete message }
}
8.1.3.15.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.4, 5.3.8.3, 5.6.5.3 and 5.6.20.2.
[TS 36.331, clause 5.3.3.4]
The UE shall:
- set the content of RRCConnectionSetupComplete message as follows:
2> if the UE is connected to EPC:
3> except for NB-IoT:
4> if the SIB2 contains idleModeMeasurements, and the UE has IDLE mode measurement information available in VarMeasIdleReport:
5> include the idleMeasAvailable;
[TS 36.331, clause 5.3.8.3]
The UE shall:
- 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;
2> start performing idle mode measurements as specified in 5.6.20;
[TS 36.331, clause 5.6.5.3]
The UE shall:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and UE has stored VarMeasIdleReport:
2> set the measResultListIdle in the UEInformationResponse message to the value of idleMeasReport in the VarMeasIdleReport;
2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;
[TS 36.331, clause 5.6.20.2]
While T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig:
3> if UE supports carrier aggregation between serving carrier and the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry;
4> perform measurements in the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry;
NOTE: The fields s-NonIntraSearch in SystemInformationBlockType3 do not affect the UE measurement procedures in IDLE mode. How the UE performs measurements in IDLE mode is up to UE implementation as long as the requirements in TS 36.133 [16] are met for measurement reporting. UE is not required to perform idle measurements if SIB2 idle measurement indication is not configured.
4> if the measCellList is included:
5> consider PCell and cells identified by each entry within the measCellList to be applicable for idle mode measurement reporting;
4> else:
5> consider PCell and up to maxCellMeasIdle strongest identified cells whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold (if any) to be applicable for idle mode measurement reporting;
4> store measurement results for cells applicable for idle mode measurement reporting within the VarMeasIdleReport;
3> else:
4> do not consider the carrier frequency to be applicable for idle mode measurement reporting;
1> if validityArea is configured in VarMeasIdleConfig and UE reselects to a serving cell whose physical cell identity does not match any entry in validityArea for the corresponding carrier frequency:
2> stop T331;
8.1.3.15.3 Test description
8.1.3.15.3.1 Pre-test conditions
System Simulator:
– Cell 1, Cell 3 and Cell 6.
– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
8.1.3.15.3.2 Test procedure sequence
Table 8.1.3.15.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.3.15.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 3 |
Cell 10 |
Remark |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-97 |
-97 |
Table 8.1.3.15.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionRelease message including the measIdleConfig on Cell 1. |
<– |
RRCConnectionRelease |
– |
– |
|
2 |
Wait for 30 s for the UE to enter E-UTRA RRC_IDLE state on Cell 1 and do measurements over cells 1, 3 and 6. |
– |
– |
– |
– |
|
3 |
Check: Does UE transmit an RRCConnectionRequest message on the cell 1? |
–> |
RRCConnectionRequest |
1 |
P |
|
4 |
The SS transmits a RRCConnectionSetup message. |
<– |
RRCConnectionSetup |
– |
– |
|
5 |
Check: Does the UE send RRCConnectionSetupComplete message without idleMeasAvailable? |
–> |
RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST |
2 |
P |
8.1.3.15.3.3 Specific message contents
Table 8.1.3.15.3.3-0: Conditions for specific message contents
in Tables 8.1.3.15.3.3-1, 8.1.3.15.3.3-2 and 8.1.3.15.3.3-3
|
Condition |
Explanation |
|
Band > 64 |
If band > 64 is selected |
Table 8.1.3.15.3.3-1: RRCConnectionRelease (step 1, Table 8.1.3.15.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-15 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionRelease ::= SEQUENCE { |
||||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier-DL |
|||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
rrcConnectionRelease-r8 SEQUENCE { |
||||
|
releaseCause |
other |
|||
|
redirectedCarrierInfo |
Not present |
|||
|
idleModeMobilityControlInfo |
Not present |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
measIdleConfig-r15 |
MeasIdleConfigDedicated-r15 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.1.3.15.3.3-2: MeasIdleConfigDedicated-r15 (step 1, Table 8.1.3.15.3.2-2)
|
Derivation Path: 36.331, clause 6.3.5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasIdleConfigDedicated-r15 ::= SEQUENCE { |
|||
|
measIdleCarrierListEUTRA-r15 |
EUTRA-CarrierList-r15 |
||
|
measIdleDuration-r15 |
sec60 |
||
|
} |
|||
Table 8.1.3.15.3.3-3: EUTRA-CarrierList-r15 (step 1, Table 8.1.3.15.3.2-2)
|
Derivation Path: 36.331, clause 6.3.5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EUTRA-CarrierList-r15 SEQUENCE ( |
2 entries |
||
|
MeasIdleCarrierEUTRA-r15[1] SEQUENCE { |
|||
|
carrierFreq-r15 |
Same downlink EARFCN as used for Cell 3 |
||
|
allowedMeasBandwidth-r15 |
mbw6 |
||
|
validityArea-r15 |
Not present |
||
|
measCellList-r15 |
Not present |
||
|
reportQuantities |
both |
||
|
qualityThreshold-r15 SEQUENCE { |
|||
|
idleRSRP-Threshold-r15 |
43 |
-97 dBm |
|
|
idleRSRQ-Threshold-r15 |
Not present |
||
|
} |
|||
|
} |
|||
|
MeasIdleCarrierEUTRA-r15[2] SEQUENCE { |
|||
|
carrierFreq-r15 |
Same downlink EARFCN as used for Cell 6 |
||
|
allowedMeasBandwidth-r15 |
mbw6 |
||
|
validityArea-r15 |
Not present |
||
|
measCellList-r15 |
Not present |
||
|
reportQuantities |
both |
||
|
qualityThreshold-r15 SEQUENCE { |
|||
|
idleRSRP-Threshold-r15 |
43 |
-97 dBm |
|
|
idleRSRQ-Threshold-r15 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.1.3.15.3.3-4: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table 8.1.3.15.3.2-2)
|
Derivation path: 36.508 table 4.4.3.3-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType5 ::= SEQUENCE { |
|||
|
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq[1] |
maxEARFCN |
Band > 64 |
|
|
dl-CarrierFreq[2] |
Same downlink EARFCN as used for Cell 6 |
||
|
dl-CarrierFreq[2] |
maxEARFCN |
Band > 64 |
|
|
} |
|||
|
SystemInformationBlockType5-v8h0-IEs SEQUENCE { |
Band > 64 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
interFreqCarrierFreqList-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
|
dl-CarrierFreq-v9e0[1] |
Same downlink EARFCN as used for Cell 3 |
||
|
dl-CarrierFreq-v9e0[2] |
Same downlink EARFCN as used for Cell 6 |
||
|
} |
|||
|
} |
|||
|
} |
|||