11.1.4 MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with redirection / Single registration mode with N26 interface / E-UTRAN cell selection using cell status barred / Success
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
11.1.4.1 Test Purpose (TP)
(1)
with { UE supporting both S1 mode and N1 mode and operating in single-registration mode, and, the Network has indicated "interworking without N26 interface not supported", and, the UE in NR RRC_CONNECTED state }
ensure that {
when { User initiates a MMTEL call, the MO IMS voice session establishment has been initiated and the UE receives a RRCRelease message which includes redirectedCarrierInfo indicating redirection to eutra, and, an E-UTRA cell on the frequency indicated by redirectedCarrierInfo is found with cell status "barred" and another E-UTRA cell is found on another frequency with cell status "notBarred" }
then { UE selects the E-UTRA cell with cell status "notBarred", performs a TAU procedure, and, the UE successfully completes the MO MMTEL call in EPS }
}
11.1.4.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 23.502, clauses 4.13.6.1 and 4.11.1.3.2, TS 24.501, clauses 4.8.2.2, 5.1.4.2 and 6.1.4.1, TS 38.331, clauses 5.3.3.2, 5.3.3.3, 5.3.8.3 and 5.3.11; TS 38.304, clause 5.2.6, TS 36.304 clause 5.3.1. Unless otherwise stated these are Rel-15 requirements.
[TS 23.502, clause 4.13.6.1]
Figure 4.13.6.1-1 describes the EPS fallback procedure for IMS voice.
When the UE is served by the 5G System, the UE has one or more ongoing PDU Sessions each including one or more QoS Flows. The serving PLMN AMF has sent an indication towards the UE during the Registration procedure that IMS voice over PS session is supported, see clause 5.16.3.10 in TS 23.501 [2] and the UE has registered in the IMS. If N26 is not supported, the serving PLMN AMF sends an indication towards the UE during the Registration procedure that interworking without N26 is supported, see clause 5.17.2.3.1 in TS 23.501 [2].
Figure 4.13.6.1-1: EPS Fallback for IMS voice
1. UE camps on NG-RAN in the 5GS and an MO or MT IMS voice session establishment has been initiated.
2. Network initiated PDU Session modification to setup QoS flow for voice reaches the NG-RAN (see N2 PDU Session Request in clause 4.3.3).
3. NG-RAN is configured to support EPS fallback for IMS voice and decides to trigger fallback to EPS, taking into account UE capabilities, indication from AMF that "Redirection for EPS fallback for voice is possible" (received as part of initial context setup as defined in TS 38.413 [10]), network configuration (e.g. N26 availability configuration) and radio conditions. If NG-RAN decides not to trigger fallback to EPS, then the procedure stops here and following steps are not executed.
NG-RAN may initiate measurement report solicitation from the UE including E-UTRAN as target.
NOTE 1: If AMF has indicated that "Redirection for EPS fallback for voice is not possible", then AN Release via inter-system redirection to EPS is not performed in step 5.
4. NG-RAN responds indicating rejection of the PDU Session modification to setup QoS flow for IMS voice received in step 2 by PDU Session Response message towards the PGW-C+SMF (or H-SMF+P-GW-C via V-SMF, in case of roaming scenario) via AMF with an indication that mobility due to fallback for IMS voice is ongoing. The PGW-C+SMF maintains the PCC rule(s) associated with the QoS Flow(s).
5. NG-RAN initiates either handover (see clause 4.11.1.2.1), or AN Release via inter-system redirection to EPS (see clause 4.2.6 and clause 4.11.1.3.2), taking into account UE capabilities. The PGW-C+SMF reports change of the RAT type if subscribed by PCF as specified in clause 4.11.1.2.1, or clause 4.11.1.3.2.6. When the UE is connected to EPS, either 6a or 6b is executed
6a. In the case of 5GS to EPS handover, see clause 4.11.1.2.1, and in the case of inter-system redirection to EPS with N26 interface, see clause 4.11.1.3.2. In either case the UE initiates TAU procedure; or
6b. In the case of inter-system redirection to EPS without N26 interface, see clause 4.11.2.2. If the UE supports Request Type flag "handover" for PDN connectivity request during the attach procedure as described in clause 5.3.2.1 of TS 23.401 [13] and has received the indication that interworking without N26 is supported, then the UE initiates Attach with PDN connectivity request with request type "handover".
In inter-system redirection, the UE uses the emergency indication in the RRC message as specified in clause 6.2.2 of TS 36.331 [16] and E-UTRAN provides the emergency indication to MME during Tracking Area Update or Attach procedure. For the handover procedure see clause 4.11.1.2.1, step 1.
7. After completion of the mobility procedure to EPS or as part of the 5GS to EPS handover procedure (see clause 4.11.1.2.1), the SMF/PGW re-initiates the setup of the dedicated bearer for IMS voice, mapping the 5G QoS to EPC QoS parameters. The PGW-C+SMF behaves as specified in clause 4.9.1.3.1. The PGW-C+SMF reports about Successful Resource Allocation and Access Network Information if subscribed by PCF.
8. The IMS voice session establishment is continued.
At least for the duration of the voice call in EPS the E-UTRAN is configured to not trigger any handover to 5GS.
[TS 23.502, clause 4.11.1.3.2]
Clause 4.11.1.3.2 covers the case of idle mode mobility from 5GC to EPC. UE performs Tracking Area Update procedure in E-UTRA/EPS when it moves from NG-RAN/5GS to E-UTRA/EPS coverage area.
The procedure involves a Tracking Area Update to EPC and setup of default EPS bearer and dedicated bearers in EPC in steps 1-11 and re-activation, if required.
Figure 4.11.1.3.2-1: 5GS to EPS Idle mode mobility using N26 interface
The TAU procedure in TS 23.401 [13] is used with the following 5GS interaction:
1. Step 1 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401 [13].
2. Step 2 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401 [13] with the modification captured in clause 4.11.1.5.3.
3-4. Steps 3-4 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401 [13].
5a. The AMF verifies the integrity of the TAU request message and requests the PGW-C+SMF to provide SM Context by using Nsmf_PDUSession_ContextRequest that also includes the mapped EPS Bearer Contexts. The AMF provides the target MME capability to SMF in the request to allow the SMF to determine whether to include EPS Bearer context for non-IP PDN Type or not. This step is performed with all the PGW-C+SMFs corresponding to PDU Sessions of the UE which are associated with 3GPP access and have EBI(s) allocated to them. In this step, if the AMF correctly validates the UE, then the AMF starts a timer.
NOTE 1: The AMF knows the MME capability to support non-IP PDN type or not through local configuration.
5b. For Non-roaming or roaming with local breakout scenario, if CN Tunnel Info is allocated by the PGW-U+UPF, the SMF sends N4 Session Modification Request to PGW-U+UPF to establish the tunnel for each EPS bearers, and PGW-U+UPF provides the PGW-U Tunnel Info for each EPS bearers to PGW-C+SMF.
NOTE2: In home routed roaming case, the CN Tunnel Info for each EPS bearer has been prepared by the PGW-C+SMF and provided to the V-SMF as specified in clause 4.11.1.4.1.
5c. SMF returns mapped EPS bearer contexts, which includes PGW-C control plane tunnel information of the PDN connection corresponding to the PDU session, EBI for each EPS bearer, PGW-U tunnel information for each EPS bearer, and EPS QoS parameters for each EPS bearer. For PDU Sessions with PDU Session Type Ethernet or Unstructured, the SMF provides SM Context for non-IP PDN Type.
6. The AMF responds with a Context Response message carrying mapped MM context (including mapped security context), Return preferred and SM EPS UE Context (default and dedicated GBR bearers) to the MME. If the verification of the integrity protection fails, the AMF returns an appropriate error cause. Return preferred is an optional indication by the AMF of a preferred return of the UE to the 5GS PLMN at a later access change to a 5GS shared network. The AMF may start an implementation specific (guard) timer for the UE context.
7 – 14. Steps 6-12 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401 [13] are performed with following addition and modification:
In the step 10, If the QoS Flow associated with the default QoS rule has an EPS Bearer ID assigned, the PGW-C+SMF keeps the PDU Session (PDN connection) and for the remaining QoS Flows that do not have EPS bearer ID(s) assigned, the PGW-C+SMF deletes the PCC rule(s) associated with those QoS Flows and informs the PCF about the removed PCC rule(s).
In the step 11, the PGW-C+SMF requests the PGW-U+UPF to establish the tunnel for each EPS bearer by providing SGW-U Tunnel Info, and PGW-U Tunnel Info if the PGW-U Tunnel Info is allocated by the PGW-C+SMF.
In step 10, the PGW-C+SMF may need to report some subscribed event to the PCF by performing an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.
Step 9a from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401 [13] with the modification captured in clause 4.11.1.5.3
15a. The HSS+UDM invokes Nudm_UECM_DeregistrationNotification to notify the AMF associated with 3GPP access with reason as 5GS to EPS Mobility. If the timer started in step 6 is not running, the old AMF removes the UE context. Otherwise, the AMF may remove UE context when the timer expires. The AMF request the release of the PDU Session which is associated with 3GPP access, not expected to be transferred to EPC, i.e. no EBI(s) allocated to them, and corresponding to the PGW-C+SMF which is not contacted by AMF for SM context at step 5a. The AMF requests the release of the SM context in the V-SMF only, for Home Routed PDU Session with EBIs allocated. The 5GC may also keep UE context to allow the use of native security parameters when UE moves back from EPS to 5GS later.
Registration associated with the non-3GPP access in the AMF is not removed (i.e. an AMF that was serving the UE over both 3GPP and non-3GPP accesses does not consider the UE as deregistered over non 3GPP access and will remain registered and subscribed to subscription data updates in UDM).
When the UE decides to deregister over non-3GPP access or the old AMF decides not to maintain a UE registration for non-3GPP access anymore, the old AMF then deregisters from UDM by sending a Nudm_UECM_Deregistration service operation, unsubscribes from Subscription Data updates by sending an Nudm_SDM_Unsubscribe service operation to UDM and releases all the AMF and AN resources related to the UE.
16 – 18. Steps 17-21 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401 [13] with the following modification:
The MME may provide the eNodeB with a PLMN list in the Handover Restriction List taking into account the last used 5GS PLMN ID and the Return preferred indication. The Handover Restriction List contains a list of PLMN IDs as specified by TS 23.251 [35] clause 5.2a for eNodeB functions.
The MME may not release the signalling connection with the UE based on the indication received in the step 1 that the UE is moving from 5GC.
19. [conditional] Step 19 from clause 4.11.1.2.1 applies.
[TS 24.501, clause 4.8.2.2]
See subclause 5.1.4.2 for coordination between 5GMM and EMM and subclause 6.1.4.1 for coordination between 5GSM and ESM.
[TS 24.501, clause 5.1.4.2]
At inter-system change from N1 mode to S1 mode when there is at least one active PDU session for which interworking with EPS is supported as specified in subclause 6.1.4.1, the UE shall enter substates EMM-REGISTERED.NORMAL-SERVICE and 5GMM-REGISTERED.NO-CELL-AVAILABLE and initiate a tracking area updating procedure (see 3GPP TS 24.301 [15]).
[TS 24.501, clause 6.1.4.1]
Upon inter-system change from N1 mode to S1 mode, the UE shall create the default EPS bearer context and the dedicated EPS bearer context(s) based on the parameters of the mapped EPS bearer contexts or the associations between QoS flow and mapped EPS bearer in the PDU session, if available. The EPS bearer identity assigned for the QoS flow of the default QoS rule becomes the EPS bearer identity of the default bearer in the corresponding PDN connection. If there is no EPS bearer identity assigned to the QoS flow of the default QoS rule, the UE shall release locally the PDU session. If there is no EPS bearer identity assigned to the QoS flow(s) which is not associated with the default QoS rule, the UE shall locally delete the QoS rules and the QoS flow level QoS parameters associated with the QoS flow(s). The UE uses the parameters from each PDU session for which interworking with EPS is supported to create corresponding default EPS bearer context and optionally dedicated EPS bearer context(s) as follows:
a) the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows:
1) the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet" or "Unstructured";
2) the PDN type shall be set to "IPv4" if the PDU session type is "IPv4";
3) the PDN type shall be set to "IPv6" if the PDU session type is "IPv6"; and
4) the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6";
b) the PDU address of the PDU session shall be mapped to the PDN address of the default EPS bearer context as follows:
1) the PDN address of the default EPS bearer context is set to the PDU address of the PDU session, if the PDU session type is "IPv4", "IPv6" or "IPv4v6"; and
2) the PDN address of the default EPS bearer context is set to zero, if the PDU session type is "Ethernet" or "Unstructured";
c) the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context;
d) the APN-AMBR and extended APN-AMBR received in the parameters of the default EPS bearer context of the mapped EPS bearer contexts shall be mapped to the APN-AMBR and extended APN-AMBR of the default EPS bearer context;
e) for each PDU session in state PDU SESSION ACTIVE, PDU SESSION MODIFICATION PENDING or PDU SESSION INACTIVE PENDING the UE shall set the state of the mapped EPS bearer context(s) to BEARER CONTEXT ACTIVE; and
f) for any other PDU session the UE shall set the state of the mapped EPS bearer context(s) to BEARER CONTEXT INACTIVE.
Additionally, for each mapped EPS bearer context or the association between QoS flow and mapped EPS bearer in the PDU session:
a) the EPS bearer identity shall be set to the EPS bearer identity received in the mapped EPS bearer context, or the EPS bearer identity associated with the QoS flow;
b) the EPS QoS parameters shall be set to the mapped EPS QoS parameters of the EPS bearer received in the mapped EPS bearer context, or the EPS QoS parameters associated with the QoS flow;
c) the extended EPS QoS parameters shall be set to the mapped extended EPS QoS parameters of the EPS bearer received in the mapped EPS bearer context, or the extended EPS QoS parameters associated with the QoS flow; and
d) the traffic flow template shall be set to the mapped traffic flow template of the EPS bearer received in the mapped EPS bearer context, or the stored traffic flow template associated with the QoS flow, if available.
After inter-system change from N1 mode to S1 mode, the UE shall associate the PDU session identity, the S-NSSAI, and the session-AMBR with the default EPS bearer context, and for each EPS bearer context mapped from one or more QoS flows, associate the QoS rule(s) for the QoS flow(s) and the QoS flow description(s) for the QoS flow(s) with the EPS bearer context.
After inter-system change from N1 mode to S1 mode, the UE and the SMF shall maintain the PDU session type of the PDU session until the PDN connection corresponding to the PDU session is released if the UE supports non-IP PDN type and the PDU session type is "Ethernet" or "Unstructured".
After inter-system change from N1 mode to S1 mode, the UE and the SMF shall maintain the always-on PDU session indication.
After inter-system change from N1 mode to S1 mode, the UE and the SMF shall maintain the maximum number of supported packet filters until the PDN connection corresponding to the PDU session is released.
[TS 38.331, clause 5.3.3.2]
Upon initiation of the procedure, the UE shall:
1> if the upper layers provide an Access Category and one or more Access Identities upon requesting establishment of an RRC connection:
2> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers;
3> if the access attempt is barred, the procedure ends;
1> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1;
1> apply the default MAC Cell Group configuration as specified in 9.2.2;
1> apply the CCCH configuration as specified in 9.1.1.2;
1> apply the timeAlignmentTimerCommon included in SIB1;
1> start timer T300;
1> initiate transmission of the RRCSetupRequest message in accordance with 5.3.3.3;
[TS 38.331, clause 5.3.3.3]
The UE shall set the contents of RRCSetupRequest message as follows:
1> set the ue-Identity as follows:
2> if upper layers provide a 5G-S-TMSI:
3> set the ue-Identity to ng-5G-S-TMSI-Part1;
2> else:
3> draw a 39-bit random value in the range 0..239-1 and set the ue-Identity to this value;
NOTE 1: Upper layers provide the 5G-S-TMSI if the UE is registered in the TA of the current cell.
1> set the establishmentCause in accordance with the information received from upper layers;
The UE shall submit the RRCSetupRequest message to lower layers for transmission.
The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.6.
[TS 38.331, clause 5.3.8.3]
The UE shall:
…
1> if the RRCRelease message includes redirectedCarrierInfo indicating redirection to eutra:
2> if cnType is included:
3> after the cell selection, indicate the available CN Type(s) and the received cnType to upper layers;
NOTE 1: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cnType, is up to UE implementation.
2> if voiceFallbackIndication is included:
3> consider the RRC connection release was for EPS fallback for IMS voice (see TS 23.502 [43]);
[TS 38.331, clause 5.3.11]
The UE shall:
…
1> else:
2> if T302 is running:
3> stop timer T302;
3> perform the actions as specified in 5.3.14.4;
[TS 38.304, clause 5.2.6]
At reception of RRCRelease message to transition the UE to RRC_IDLE or RRC_INACTIVE, UE shall attempt to camp on a suitable cell according to redirectedCarrierInfo if included in the RRCRelease message. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the RRCRelease message does not contain the redirectedCarrierInfo, UE shall attempt to select a suitable cell on an NR carrier. If no suitable cell is found according to the above, the UE shall perform cell selection using stored information in order to find a suitable cell to camp on.
When returning to RRC_IDLE state after UE moved to RRC_CONNECTED state from camped on any cell state, UE shall attempt to camp on an acceptable cell according to redirectedCarrierInfo, if included in the RRCRelease message. If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the RRCRelease message does not contain redirectedCarrierInfo UE shall attempt to select an acceptable cell on an NR frequency. If no acceptable cell is found according to the above, the UE not in SNPN Access Mode shall continue to search for an acceptable cell of any PLMN in state any cell selection.
[TS 36.304, clause 5.3.1]
Cell status and cell reservations are indicated in the SystemInformationBlockType1 message (or SystemInformationBlockType1-BR message or SystemInformationBlockType1-NB message) TS 36.331 [3] by means of the following fields:
– cellBarred (IE type: "barred" or "not barred")
This field indicates if the cell is barred for connectivity to EPC.
This field is ignored by the UEs supporting crs-IntfMitig while crs-IntfMitigEnabled is included in SIB1.
This field is ignored by the BL UEs or UEs in CE supporting ce-CRS-IntfMitig while crs-IntfMigitNumPRBs is included in SIB1-BR.
In case of multiple EPC PLMNs indicated in SIB1/SIB1-BR, this field is common for all EPC PLMNs
NOTE: For IAB node, it ignores the cellBarred, cellReservedForOperatorUse and cellReservedForOtherUse as defined in TS 36.331 [3].
…
The following description for handling of barred and reserved cells is per CN type. If the UE supports more than one CN type, the UE shall only exclude a cell as candidate for selection/reselection if it is excluded for both CN types.
NOTE: Fields cellBarred-CRS and cellReservedForOperatorUse-CRS are not indicated in SystemInformationBlockType1-NB
When cell status is indicated as "not barred" and "not reserved" for operator use,
– All UEs shall treat this cell as candidate during the cell selection and cell reselection procedures.
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
– UEs assigned to Access Class 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate during the cell selection and reselection procedures if the field cellReservedForOperatorUse for that PLMN set to "reserved".
– UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 shall behave as if the cell status is "barred" in case the cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
NOTE: ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN; ACs 12, 13, 14 are only valid for use in the home country TS 22.011 [4].
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
– The UE is not permitted to select/reselect this cell, not even for emergency calls.
– The UE shall consider other cells for cell selection/reselection according to the following rule:
11.1.4.3 Test Description
11.1.4.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is configured according to TS 38.508-1 [4] Table 4.4.2-3 and is connected to 5GC.
– E-UTRA Cell 1 and E-UTRA Cell 3 are configured to TS 36.508 [7] Table 4.4.2-2 and are connected to EPC.
– System information on the NR Cell 1 in accordance with combination NR-6 in TS 38.508-1 [4] sub-clause 4.4.3.1.2, and, for the E-UTRA Cell 1 and Cell 3 in accordance with combination 31 as defined in TS 36.508 [7], subclause 4.4.3.1.1.
– N26 interface is configured.
– Power levels are constant and as defined in Tables 11.1.4.3.1-1/2.
Table 11.1.4.3.1-1: Time instances of cell power level and parameter changes for conducted test environment
|
Parameter name |
Unit |
NR Cell 1 |
E-UTRA Cell 1 |
E-UTRA Cell 3 |
Remark |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
– |
– |
|
|
RS EPRE |
dBm/15kHz |
– |
-97 |
-85 |
Table 11.1.4.3.1-2: Time instances of cell power level and parameter changes for OTA test environment
|
Parameter name |
Unit |
NR Cell 1 |
E-UTRA Cell 1 |
E-UTRA Cell 3 |
Remark |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-82 |
– |
– |
|
|
RS EPRE |
dBm/15kHz |
– |
-96 |
-96 |
UE:
– The UE is configured to use IMS preconditions
Preamble:
– With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using generic procedure parameters Connectivity (E-UTRA) and Unrestricted nr PDN (On) in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2. 4G GUTI and eKSI are assigned and security context established.
– The UE is switched-off.
– With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state 1N-A, RRC_IDLE Connectivity (NR) with at least one IMS PDU session on NR Cell 1, in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.2.2-2. 5G-GUTI and ngKSI are assigned.
11.1.4.3.2 Test procedure sequence
Table 11.1.4.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Void |
– |
– |
– |
– |
|
– |
The following messages are to be observed on NR Cell 1 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
2 |
The SS transmits a Paging message. |
<– |
NR RRC: Paging |
– |
– |
|
3 |
The UE transmits an RRCSetupRequest message. |
–> |
NR RRC: RRCSetupRequest |
– |
– |
|
4-9 |
Steps 3 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 [4] Table 4.5.4.2-3 are executed to successfully complete the service request procedure. |
– |
– |
– |
– |
|
9A |
Set the power levels according to “T0” as per Table 11.1.4.3.1-1/2. |
– |
– |
– |
– |
|
10a1 |
Void |
– |
– |
– |
– |
|
11 |
Make the UE attempt an IMS speech call. |
– |
– |
– |
– |
|
12-16 |
Steps 1-5 of generic procedure “EPS Fallback for Voice Call / steps before fallback / 5GS” as defined in Appendix A.9.1 of TS 34.229-5 [41] take place. |
– |
– |
– |
– |
|
17 |
The SS transmits an RRCRelease message |
<– |
NR RRC:RRCRelease |
– |
– |
|
– |
The following messages are to be observed on E-UTRA Cell 1 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
18 |
Generic test procedure in TS 38.508-1 [4] Table 4.9.7.2.2-1 Steps 1-6 is performed without ‘connected without release‘ on E-UTRAN cell upon mobility from NR. |
– |
– |
– |
– |
|
18A-18D |
Generic Test Procedure as defined in Steps 5-8 of TS 36.508-1 [4] Table 4.5A.6.3-1 is performed to establish radio bearer corresponding to IMS PDN. |
– |
– |
– |
– |
|
19 |
The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to TS 36.508 [7] Table 6.6.2-1: Reference dedicated EPS bearer contexts. Reference dedicated EPS bearer contexts is to establish the dedicated EPS bearer context on IMS PDN. |
<– |
RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in steps 20-22 below, the steps specified in table 11.1.4.3.2-2 will take place. |
– |
– |
– |
– |
|
20 |
The UE transmits an RRCConnectionReconfigurationComplete message. |
–> |
RRC: RRCConnectionReconfigurationComplete |
– |
– |
|
21 |
The UE transmits an ULInformationTransfer message including the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. |
–> |
RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT |
– |
– |
|
22 |
The SS waits 1 second for call duration. |
– |
– |
– |
– |
|
23a1 |
Void |
– |
– |
– |
– |
|
24 |
Release IMS Call as specified in the generic procedure in TS 34.229-1 [35] subclause C.32. |
– |
– |
– |
– |
Table 11.1.4.3.2-2: Parallel behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
– |
EXCEPTION: Steps 1a1 to 1b7 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported |
– |
– |
– |
– |
|
1a1-1a2 |
The UE performs IMS re-registration on EUTRAN as per steps 1-2 as defined in TS 34.229-1 [35] C.46. |
– |
– |
– |
– |
|
1a3-1a6A |
Steps 1-5 of the generic procedure “EPS Fallback for Voice Call / steps after fallback / 5GS” as defined in Appendix A.9.2 of TS 34.229-5 [41] take place. |
– |
– |
– |
– |
|
1a7 |
Check: Does the UE perform step 6 of the generic procedure “EPS Fallback for Voice Call / steps after fallback / 5GS” as defined in Appendix A.9.2 of TS 34.229-5 [41] |
–> |
SIP: ACK |
1 |
P |
11.1.4.3.3 Specific message contents
Table 11.1.4.3.3-1: REGISTRATION REQUEST (preamble, Table 11.1.4.3.2-1)
|
Derivation path: TS 38.508-1 [4] Table 4.7.1-6 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
5GMM capability |
|||
|
S1 mode |
‘1’B |
S1 mode supported |
|
|
S1 UE network capability |
Present but contents not checked |
||
Table 11.1.4.3.3-2: REGISTRATION ACCEPT (preamble, Table 11.1.4.3.2-1)
|
Derivation path: TS 38.508-1 [4] Table 4.7.1-7 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
5GS network feature support |
|||
|
IMS- VoPS-3GPP |
‘1’B |
IMS voice over PS session supported over 3GPP access |
|
|
IWK N26 |
‘0’B |
Interworking without N26 interface not supported |
|
Table 11.1.4.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (preamble for PDU Session for PS data, Table 11.1.4.3.2-1)
|
Derivation path: TS 38.508-1 [4] Table 4.7.2-2, condition Interworking_with_EPS |
Table 11.1.4.3.3-4: PDU SESSION ESTABLISHMENT ACCEPT (preamble for IMS PDU Session, Table 11.1.4.3.2-1)
|
Derivation path: TS 38.508-1 [4] Table 4.7.2-2, condition Interworking_with_EPS, IMS_DNN_ Requested |
Table 11.1.4.3.3-5: Void
Table 11.1.4.3.3-6: RRCRelease message (step 17, table 11.1.4.3.2-1)
|
Derivation path: TS 38.508-1 [4] Table 4.6.1-16 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcRelease SEQUENCE { |
|||
|
redirectedCarrierInfo CHOICE { |
|||
|
eutra SEQUENCE { |
|||
|
eutraFrequency |
Cell 3’s EARFCN |
||
|
cnType |
epc |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 11.1.4.3.3-7: SystemInformationBlockType1 of E-UTRA Cell 3 (Preamble and all steps, Table 11.1.4.3.2-1)
|
Derivation Path: 36.508 [7] Table 4.4.3.2-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType1 ::= SEQUENCE { |
|||
|
cellAccessRelatedInfo SEQUENCE { |
|||
|
cellBarred |
barred |
||
|
} |
|||
|
} |
|||