13.1.4 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with handover / MT call
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
13.1.4.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_IDLE state }
ensure that {
when { UE receives a Paging message with CN domain indicator set to “CS” }
then { UE transmits an ULInformationTransfer message containing an EXTENDED SERVICE REQUEST message with Service Type IE set to "mobile terminating CS fallback or 1xCS fallback” }
}
(2)
with { UE having transmitted an ULInformationTranfer message containing an EXTENDED SERVICE REQUEST message with Service Type IE set to "mobile terminating CS fallback or 1xCS fallback” }
ensure that {
when { SS transmits a MobilityFromEUTRACommand message with handover to a UTRA cell in a different location area and operating in NMO I }
then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra cell and initiates a CS domain PAGING RESPONSE procedure or LA update procedure and a parallel PS domain RA Update procedure }
}
13.1.4.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 23.272, clause 7.2, 7.3, and TS 24.301, clause 5.6.2.3.
[TS 23.272, clause 7.2]
The procedure for Mobile Terminating Call in idle mode is illustrated in figure 7.2-1, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
Figure 7.2-1: Mobile Terminating Call in idle mode
1. G‑MSC receives IAM.
2. G‑MSC retrieves routing information of the terminating UE by Send Routing Info procedures as specified in TS 23.018 [5].
3. G‑MSC sends IAM to the MSC on the terminating side as specified in TS 23.018 [5].
4. The MME receives a Paging Request (IMSI, VLR TMSI, Location Information) message from the MSC over a SGs interface. If the TMSI is received from the MSC, it is used by the MME to find the S‑TMSI which is used as the paging address on the radio interface. If the IMSI is received from the MSC, the IMSI shall be used as the paging address on the radio interface. If location information is reliably known by MME (i.e. MME stores the list of TAs), the MME shall page the UE in all the TAs. If the MME does not have a stored TA list for the UE, the MME should use the location information received from the MSC to page the UE.
NOTE 1: This procedure takes place before step 3, immediately after MSC receives MAP_PRN from HSS, if pre-paging is deployed.
If the MME receives a Paging Request message for an UE which is considered as detach for EPS services, the MME sends the Paging reject message to the MSC with an appropriate cause value. This rejection triggers the MSC to page the UE over A or Iu-cs interface.
NOTE 2: In case of a CS fallback capable UE in NMO II or III, there is a case where, for example, the MME releases the SGs association due to the UE idle mode mobility while the VLR still maintains the SGs association.
5. If the MME did not return an "SMS-only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME sends a Paging (as specified in TS 23.401 [2]) message to each eNodeB. The Paging message includes a suitable UE Identity (i.e. S‑TMSI or IMSI) and a CN Domain Indicator that indicates which domain (CS or PS) initiated the paging message. In this case it shall be set to "CS" by the MME.
If the MME returned the "SMS-only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME shall not send the paging to the eNodeBs and sends Paging Reject towards MSC to stop CS Paging procedure and this CSFB procedure stops.
6. The radio resource part of the paging procedure takes place. The message contains a suitable UE Identity (i.e. S‑TMSI or IMSI) and a CN Domain indicator.
7a. The UE establishes an RRC connection and sends an Extended Service Request (CS Fallback Indicator) to MME. The UE indicates its S-TMSI in the RRC signalling. The Extended Service Request message is encapsulated in RRC and S1‑AP messages. The CS Fallback Indicator indicates to the MME that CS Fallback for this UE is required. The MME sends the SGs Service Request message to the MSC containing an indication that the UE was in idle mode (and hence, for example, that the UE has not received any Calling Line Identification information). Receipt of the SGs Service Request message stops the MSC retransmitting the SGs interface Paging message.
NOTE 3: In order to avoid the calling party experiencing a potentially long period of silence, the MSC may use the SGs Service Request message containing the idle mode indication as a trigger to inform the calling party that the call is progressing.
7b. MME sends S1‑AP: Initial UE Context Setup (UE capabilities, CS Fallback Indicator, LAI and other parameters specified in TS 23.401 [2]) to indicate the eNodeB to move the UE to UTRAN/GERAN. The registered PLMN for CS domain is identified by the PLMN ID included in the LAI, which is allocated by the MME.
7c. The eNodeB shall reply with S1-AP: Initial UE Context Setup Response message.
8a. If the eNodeB knows that both the UE and the network support PS handover: The information flow may continue as described in clause 7.3 "Mobile Terminating call in Active Mode – PS HO supported" from step 2, in clause 7.3, and onwards.
. If the eNodeB knows that either the UE or the network does not support PS handover: The information flow shall continue as described in clause 7.4 "Mobile Terminating call in Active Mode – No PS HO support" from step 2, in clause 7.4, and onwards.
NOTE 4: Even in case both the UE and the network support PS HO, the eNodeB may choose to use a different inter-RAT mobility procedure.
[TS 23.272, clause 7.3]
This flow may be executed when the eNodeB knows that both the UE and the network support PS HO in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
Figure 7.3-1: CS Page in E-UTRAN, Call in GERAN/UTRAN
1a. The MSC receives an incoming voice call and responds by sending a Paging Request (IMSI or TMSI, optional Caller Line Identification and Connection Management information, CS call indicator) to the MME over a SGs interface. The MSC only sends a CS Page for an UE that provides location update information using the SGs interface. In active mode the MME has an established S1 connection and if the MME did not return the "SMS-only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME reuses the existing connection to relay the CS Page to the UE.
If the MME returned the "SMS-only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME shall not send the CS Service Notification to the UE and shall send Paging Reject towards MSC to stop CS Paging procedure, and this CSFB procedure stops.
The eNodeB forwards the paging message to the UE. The message contains CN Domain indicator and, if received from the MSC, the Caller Line Identification.
The MME immediately sends the SGs Service Request message to the MSC containing an indication that the UE was in connected mode. The MSC uses this connected mode indication to start the Call Forwarding on No Reply timer for that UE and the MSC should send an indication of user alerting to the calling party. Receipt of the SGs Service Request message stops the MSC retransmitting the SGs interface Paging message.
NOTE 1: The pre‑configured policy may be used by UE to avoid being disturbed without Caller Line Identification display and the detailed handling is to be decided by CT1 and CT6.
NOTE 2: This procedure can also take place immediately after MSC receives MAP_PRN from HSS, if pre-paging is deployed. Caller Line Identification and CS call indicator are also provided in the case of pre-paging.
NOTE 3: In order to avoid the calling party experiencing a potentially long period of silence, the MSC may use the SGs Service Request message as a trigger to inform the calling party that the call is progressing.
1b. UE sends an Extended Service Request (CS Fallback Indicator, Reject or Accept) message to the MME. The Extended Service Request message is encapsulated in RRC and S1‑AP messages. CS Fallback Indicator indicates to the MME to perform CS Fallback. The UE may decide to reject CSFB based on Caller Line Identification.
1c. Upon receiving the Extended Service Request (CSFB, Reject), the MME sends Paging Reject towards MSC to stop CS Paging procedure and this CSFB procedure stops.
1d. MME sends an S1‑AP UE Context Modification Request (CS Fallback Indicator, LAI) message to eNodeB. This message: indicates to the eNodeB that the UE should be moved to UTRAN/GERAN. The registered PLMN for CS domain is identified by the PLMN ID included in the LAI, which is allocated by the MME.
1e. The eNodeB shall reply with S1-AP UE Context Modification Response message.
2. The eNodeB may optionally solicit a measurement report from the UE to determine the target GERAN/UTRAN cell to which PS handover will be performed.
3a. The eNodeB triggers PS handover to a GERAN/UTRAN neighbour cell by sending a Handover Required message to MME. The eNodeB selects the target PS handover cell considering the PLMN ID and possibly the LAC for CS domain provided by the MME in step 1d. In the following an inter-RAT handover from E‑UTRAN to UTRAN or GERAN as specified in TS 23.401 [2] begins. The eNodeB indicates in the Source RNC to Target RNC Transparent container that PS handover was triggered due to CSFB. The eNodeB also indicates whether CSFB was triggered for emergency purpose. As part of this handover, the UE receives a HO from E‑UTRAN Command and tries to connect to a cell in the target RAT. The HO from E-UTRAN Command may contain a CS Fallback Indicator which indicates to UE that the handover was triggered due to a CS fallback request. If the HO from E-UTRAN Command contains a CS Fallback Indicator and the UE fails to establish connection to the target RAT, then the UE considers that CS fallback has failed.
The UE establishes the signalling connection as described in step 4b.
NOTE 4: During the PS HO the SGSN does not create a Gs association with the MSC/VLR.
3b. If the target RAT is GERAN and the UE has entered Dedicated Mode, the UE starts the Suspend procedure (see TS 44.018 [4]) unless both the UE and the Target cell support DTM in which case TBF re-establishment may be performed.
3c. A Gn/Gp-SGSN that receives the Suspend message from the UE follows the Suspend procedure specified in TS 23.060 [3], clause 16.2.1.1.1.
An S4-SGSN that receives the Suspend message from the UE follows the Suspend procedure specified in TS 23.060 [3]. The S4-SGSN deactivates GBR bearers towards S-GW and P-GW(s) by initiating MS-and SGSN Initiated Bearer Deactivation procedure as specified in TS 23.060 [3], and starts the preservation and suspension of non-GBR bearers by sending Suspend Notification message to the S-GW. The S-GW releases all RNC related information (address and TEIDs) for the UE if Direct Tunnel is established, and sends Suspend Notification message to the P-GW(s). The SGSN stores in the UE context that UE is in suspended status. All the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW(s). The P-GW should discard packets if received for the suspended UE.
4a. If the LA of the new cell is different from the one stored in the UE, the UE shall initiate a Location Area Update or a Combined RA/LA Update procedure as follows:
– If the network is operating in NMO-I (Network Modes of Operation), the UE should initiate a separate Location Area Update before initiating the RAU procedure instead of a Combined RA/LA Update procedure (to speed up the CSFB procedure); or
– if the network is operating in NMO-II or NMO-III the UE shall initiate a Location Area Update procedure before initiating the RAU procedure required for PS handover.
The UE shall set the "CSMT" flag in the LAU Request. The "CSMT" flag is used to avoid missing MT call in roaming retry case. Further the UE performs any Routing Area Update procedure as specified in TS 23.060 [3].
The UE may initiate a Location Area Update procedure immediately when the UE is handed over to the target cell i.e. before the UE receives e.g. LAI or NMO information as part of the RAN Mobility Information.
When the MSC receives a LA Update Request, it shall check for pending terminating CS calls and, if the "CSMT" flag is set, maintain the CS signalling connection after the Location Area Update procedure for pending terminating CS calls.
4b. If the UE does not initiate a LAU procedure, it shall respond with a Paging Response message to the MSC as follows:
– If the Target RAT is UTRAN or GERAN Iu mode: The UE establishes a radio signalling connection and responds to the paging by sending an RRC Paging Response as specified in TS 25.331 [7]. The CN Domain Indicator is set to "CS" in the Initial Direct Transfer message.
– If the Target RAT is GERAN A/Gb mode: The UE establishes a radio signalling connection and responds to paging by using the procedures specified in TS 44.018 [4] (i.e. UE requests and is assigned a dedicated channel where it sends a SABM containing a Paging Response to the BSS and the BSS responds by sending a UA). Upon receiving the SABM (containing a Paging Response message) the BSS sends a COMPLETE LAYER 3 INFORMATION message (containing a Paging Response message) to the MSC which indicates CS resources have been allocated in the GERAN cell. If both the UE and the target cell support enhanced CS establishment in DTM (indicated by GERAN system information included within the HO from E‑UTRAN Command) an RR connection may be established while in packet transfer mode without release of the packet resources, see TS 43.055 [24]. After the establishment of the main signalling link as described in TS 44.018 [4] the UE enters either Dual Transfer Mode or Dedicated Mode and the CS call establishment procedure completes.
NOTE 5: The BSS should be prepared to receive a Paging Response even when the corresponding Paging Request has not been sent by this BSS.
5a. After performing the LAU procedure or after receiving the Paging Response the MSC shall establish the CS call if the UE is allowed in the LA.
5b. If the UE is not registered in the MSC that receives the Paging Response or the UE is not allowed in the LA, the MSC shall reject the Paging Response message by releasing the A/Iu-CS. The BSC/RNC in turn releases the signalling connection for UTRAN or GERAN CS domain. The signalling connection release shall trigger the UE to obtain the LAI, which causes the initiation of a Location Area Update or a Combined RA/LA procedure as specified in TS 23.060 [3] for the different Network Modes of Operation (NMO).
The Location Area Update triggers the Roaming Retry for CS Fallback procedure as defined in clause 7.5.
5c. After performing the LAU procedure the MSC shall establish the CS call if the UE is allowed in the LA.
6. The UE performs any remaining steps of the inter-RAT handover from E-UTRAN to UTRAN or GERAN as specified in TS 23.401 [2]
With the exception of steps 1a and 1c, above, Call Forwarding (see TS 23.082 [31]) is performed on the basis of the TS 24.008 [21] signalling received on the GERAN/UTRAN cell.
If the UE remains on UTRAN/GERAN after the CS voice call is terminated the UE performs normal mobility management procedures as defined in TS 23.060 [3] and TS 24.008 [21].
[TS 24.301, clause 5.6.2.3]
The network may initiate the paging procedure for CS fallback when the UE is IMSI attached for non-EPS services (see example in figure 5.6.2.3.1).
Figure 5.6.2.3.1: Paging procedure for CS fallback to A/Gb or Iu mode
To initiate the procedure when no NAS signalling connection exists, the EMM entity in the network requests the lower layer to start paging (see 3GPP TS 36.300 [20], 3GPP TS 36.413 [23]). The EMM entity may provide the lower layer with a list of CSG IDs, including the CSG IDs of both the expired and the not expired subscriptions. If there is a PDN connection for emergency bearer services established, the EMM entity in the network shall not provide the list of CSG IDs to the lower layer. The paging message includes a CN domain indicator set to "CS" in order to indicate that this is paging for CS fallback.
NOTE: The timer T3413 is not started in the network when the paging procedure is initiated for CS fallback.
To notify the UE about an incoming mobile terminating CS service excluding SMS over SGs when a NAS signalling connection exists, the EMM entity in the network shall send a CS SERVICE NOTIFICATION message. This message may also include CS service related parameters (e.g. Calling Line Identification, SS or LCS related parameters).
Upon reception of a paging indication, a UE that is IMSI attached for non-EPS services shall respond with an EXTENDED SERVICE REQUEST. If the paging is received in EMM-IDLE mode, the UE shall respond immediately. If the paging is received as NAS CS NOTIFICATION message in EMM-CONNECTED mode, the UE may request upper layers input i.e. to accept or reject CS fallback before responding with an EXTENDED SERVICE REQUEST. The response is indicated in the CSFB response information element in the EXTENDED SERVICE REQUEST message in both EMM-IDLE and EMM-CONNECTED modes.
[TS 24.008, clause 4.5.1.3.4]
If the MS determines, before sending the response to paging, that it is in a different location area than the stored location area, the MS shall initiate a normal location updating procedure or a combined routing area update procedure first, depending on Network Mode of Operation. The MM connection establishment is delayed until successful completion of the normal location updating or combined routing area update procedure. In A/Gb mode, if the MS is a non DTM MS, or a DTM MS in a cell not supporting DTM, the MS may perform location area updating procedure instead of combined routing area update procedure in NMO I. After the completion of the normal location updating procedure, the MS shall not send the PAGING RESPONSE message.
13.1.4.3 Test description
13.1.4.3.1 Pre-test conditions
System Simulator:
– Cell 1 serving cell
– Cell 5 suitable neighbour cell
– 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 Registered, Idle Mode (state 2) on Cell 1 according to [18].
13.1.4.3.2 Test procedure sequence
Table 13.1.4.3.2-1 shows the cell power levels after the preamble.
Table 13.1.4.3.2-1: Time instances of cell power level and parameter changes
|
Parameter name |
Unit |
Cell 1 |
Cell 5 |
|
|
T0 |
RS EPRE |
dBm/15kHz |
-75 |
|
|
CPICH_Ec |
dBm/3.84 MHz |
-70 |
||
|
P-CCPCH |
dBm/1.28 MHz |
-72 |
||
|
T1 |
RS EPRE |
dBm/15kHz |
Non-suitable “Off” |
|
|
CPICH_Ec |
dBm/3.84 MHz |
-70 |
||
|
P-CCPCH |
dBm/1.28 MHz |
-72 |
Table 13.1.4.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits a Paging message to the UE on Cell 1 using S-TMSI with CN domain indicator set to “CS”. |
<– |
Paging |
– |
– |
|
– |
EXCEPTION: Step 2a1 describes behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. |
– |
– |
– |
– |
|
2a1 |
IF the UE needs to request upper layer input before accepting the CS fallback, the incoming CS call is accepted at the UE through MMI or AT command. |
– |
– |
– |
– |
|
3 |
The UE transmits an RRCConnectionRequest message on Cell1. |
–> |
RRCConnectionRequest |
– |
– |
|
4 |
The SS transmits an RRCConnectionSetup message on Cell1. |
<– |
RRCConnectionSetup |
– |
– |
|
5 |
Check: Does the UE transmit an RRCConnectionSetupComplete message containing an EXTENDED SERVICE REQUEST with Service Type IE set to "mobile terminating CS fallback or 1xCS fallback” on Cell 1? |
–> |
RRCConnectionSetupComplete NAS: EXTENDED SERVICE REQUEST |
1 |
P |
|
5A |
The SS transmits a SecurityModeCommand message on Cell 1. |
<– |
SecurityModeCommand |
– |
– |
|
5B |
The UE transmits a SecurityModeComplete message on Cell 1. |
–> |
SecurityModeComplete |
– |
– |
|
5C |
The SS transmits an RRCConnectionReconfiguration message on Cell 1. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
5D |
The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
5E |
The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E-UTRA and UTRA. |
<– |
UECapabilityEnquiry |
– |
– |
|
5F |
The UE transmits a UECapabilityInformation message on Cell 1. NOTE: The start-PS values received, should be used to configure ciphering on cell 5. |
–> |
UECapabilityInformation |
– |
– |
|
6 |
The SS transmits a MobilityFromEUTRACommand message on Cell 1 with IE handover. |
<– |
MobilityFromEUTRACommand |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in step 7 to 19 the steps specified in table 13.1.4.3.2-3 takes place.based on UE capability and if pc_IMS = TRUE |
– |
– |
– |
– |
|
7-19 |
Check: Are steps 1 to 11 of the generic test procedure in TS 36.508 subclause 6.4.3.7.5 performed? |
–> |
HANDOVER TO UTRAN COMPLETE |
2 |
– |
|
20 |
SS adjusts cell levels according to row T1 of table 13.1.4.3.2-1. |
||||
|
– |
The UE is in end state UTRA CS call (U5). |
– |
– |
– |
– |
Table 13.1.4.3.2-3: Parallel behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
– |
Exception: Steps below describe optional behaviour that depend on the UE capability. |
– |
– |
– |
– |
|
1a1 |
IMS de-registration is performed using the generic procedure defined in 34.229-1 [35] Annex C.30. |
– |
– |
– |
– |
Table 13.1.4.3.2-3: Void
13.1.4.3.3 Specific message contents
Table 13.1.4.3.3-1: Void
Table 13.1.4.3.3-2: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 13.1.4.3.2-2)
|
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 13.1.4.3.3-3: Message Paging (step 1, Table 13.1.4.3.2-2)
|
Derivation Path: 36.508 clause 4.6.1-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Paging ::= SEQUENCE { |
||||
|
pagingRecordList SEQUENCE (SIZE (1..maxPageRec)) OF SEQUENCE { |
1 entry |
|||
|
ue-Identity[1] CHOICE { |
||||
|
s-TMSI |
Set to the value of the S-TMSI of the UE |
|||
|
} |
||||
|
cn-Domain[1] |
cs |
|||
|
} |
||||
|
} |
||||
Table 13.1.4.3.3-4: RRCConnectionSetupComplete (step 5, Table 13.1.4.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-18 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionSetupComplete ::= SEQUENCE { |
||||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier-UL |
|||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
rrcConnectionSetupComplete-r8 SEQUENCE { |
||||
|
selectedPLMN-Identity |
Set to the PLMN selected by upper layers |
|||
|
registeredMME |
Not present |
|||
|
dedicatedInfoNAS |
Set according to 36.508 Table 4.7.2-14A |
EXTENDED SERVICE REQUEST (Note: Sent as integrity protected NAS message) |
||
|
nonCriticalExtension SEQUENCE {} |
Not checked |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 13.1.4.3.3-5: RRCConnectionReconfiguration (step 5C, Table 13.1.4.3.2-2)
|
Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(1, 0) |
Table 13.1.4.3.3-6: Message MobilityFromEUTRACommand (step 6, Table 13.1.4.3.2-2)
|
Derivation Path: 36.508 clause 4.6.1-6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
MobilityFromEUTRACommand ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
mobilityFromEUTRACommand-r8 SEQUENCE { |
||||
|
csFallbackIndicator |
True |
|||
|
purpose CHOICE { |
||||
|
handover SEQUENCE { |
||||
|
targetRAT-Type |
Utra |
|||
|
targetRAT-MessageContainer |
HANDOVER TO UTRAN COMMAND |
|||
|
nas-SecurityParamFromEUTRA |
The 4 least significant bits of the NAS downlink COUNT value |
|||
|
systemInformation |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 13.1.4.3.3-7: HANDOVER TO UTRAN COMMAND (step 6, Table 13.1.4.3.3-6)
|
Derivation Path: 36.508 table 4.7B.1-1, condition UTRA PS RB |
Table 13.1.4.3.3-8: Void
Table 13.1.4.3.3-9: UECapabilityEnquiry (step 5E, Table 13.1.4.3.2-2)
|
Derivation path: 36.508 clause 4.6.1 table 4.6.1-22 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
UECapabilityEnquiry ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
ueCapabilityEnquiry-r8 SEQUENCE { |
|||
|
ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE { |
2 entry |
||
|
RAT-Type[1] |
Eutra |
||
|
RAT-Type[2] |
Utra |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 13.1.4.3.3-10: ATTACH ACCEPT (Preamble)
|
Derivation Path: 36.508 Table 4.7.2-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EPS network feature support |
Not present |
|||