8.5.2 Redirection to E-UTRAN
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.5.2.1 Redirection to E-UTRAN / From UTRAN upon reception of RRC CONNECTION REJECT
8.5.2.1.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 REJECT 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.5.2.1.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.3.9]
When the UE receives an RRC CONNECTION REJECT message on the downlink CCCH, it shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION REJECT message with the value of the variable INITIAL_UE_IDENTITY:
…
1> if the IE "inter-RAT info" is present:
2> if the IE "wait time" = ‘0’:
3> the UE behaviour is not specified.
2> if V300 is equal to or smaller than N300:
3> if the IE "GSM target cell info" is present:
4> attempt to camp on a suitable cell of the list of cells indicated for that RAT;
4> if the UE selects and camps on one of the cells indicated for that RAT:
5> disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed.
4> if the UE cannot find any suitable cell from the indicated ones within 10s, the UE is allowed to camp on any suitable cell on that RAT.
5> after having selected and camped on a suitable cell on the designated RAT:
6> the UE may disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed.
3> if the IE "E-UTRA target info" is present:
4> attempt to camp on a suitable cell on one of the frequencies indicated for that RAT, excluding any cell indicated in the list of not allowed cells for that RAT (e.g. the "E-UTRA Target Cell Blacklist" for E-UTRA), if present;
4> if the UE selects and camps on one such cell:
5> disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed.
4> if the UE cannot find any suitable cell on the indicated frequencies within 10s, the UE is allowed to camp on any suitable cell on that RAT:
5> after having selected and camped on a suitable cell on the designated RAT:
6> disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed.
8.5.2.1.3 Test description
8.5.2.1.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)
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.5.2.1.3.2 Test procedure sequence
Table 8.5.2.1.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 transmit a RRC CONNECTION REJECT |
<– |
RRC CONNECTION REJECT |
– |
– |
– |
EXCEPTION : Step 4a1 to 4b6 describe behaviour that depends on whether a UE that has a PDP context activated on UTRAN |
– |
– |
– |
– |
4 a1 |
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 |
– |
4b1 |
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? |
– |
– |
– |
– |
4b2 |
The UE transmits a RRCConnectionRequest message on E-UTRAN Cell1 |
–> |
RRC: RRCConnectionRequest |
– |
– |
4b3 |
SS transmit an RRCConnectionSetup message |
<– |
RRC: RRCConnectionSetup |
– |
– |
4b4 |
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 |
– |
– |
4b5 |
SS transmits a SERVICE REJECT with cause Protocol error, unspecified |
<– |
SERVICE REJECT |
– |
– |
4b6 |
The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE. |
<– |
RRC: RRCConnectionRelease |
– |
– |
8.5.2.1.3.3 Specific message or IE contents
Table 8.5.2.1.3.3-0: Conditions for specific message contents
in Table 8.5.2.1.3.3-1
Condition |
Explanation |
Band > 64 |
If E-UTRA band > 64 is selected |
Table 8.5.2.1.3.3-1 System Information Block type 19 for cell 5 (preamble and all steps, Table 8.5.2.1.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 |
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.5.2.1.3.3-2: RRC CONNECTION REQUEST (UTRA Rel-8)
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 |
|
Domain indicator |
PS domain |
Table 8.5.2.1.3.3-3: RRC CONNECTION REJECT (UTRA Rel-8)
Derivation path: 34.108 default RRC CONNECTION REJECT in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA TDD |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Wait Time |
15 |
||
Redirection info |
|||
Inter-RAT info |
E-UTRA |
||
E-UTRA target info |
|||
E-UTRA Target Frequency Info List |
1 Entry |
||
DL Carrier frequency |
EARFCN of the downlink Cell 1 carrier frequency |
||
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.5.2.1.3.3-4: SERVICE REJECT (step 4b5, Table 8.5.2.1.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 |