Interoperability Test Plan for VoLTE Wireless Devices

Interoperability Test Plan for VoLTE Wireless Devices

Version 1.1

April 2020

© 2019 - 2020 CTIA Certification. All Rights Reserved.

Any reproduction, modification, alteration, creation of a derivative work, or transmission of all or any part of this publication (“Test Plan”), in any form, by any means, whether electronic or mechanical, including photocopying, recording, or via any information storage and retrieval system, without the prior written permission of CTIA Certification, is unauthorized and strictly prohibited by federal copyright law. This Test Plan is solely for use within the CTIA Certification Program. Any other use of this Test Plan is strictly prohibited unless authorized by CTIA Certification or its assigns in writing.

Test Plan Version 1.1

2 © 2019 - 2020 CTIA Certification. All Rights Reserved.

CTIA Certification LLC 1400 16th Street, NW

Suite 600 Washington, DC 20036

1.202.785.0081

[email protected]

mailto:[email protected]



Table of Contents Section 1 Introduction ...................................................................................................................... 7

1.1 Purpose ........................................................................................................................... 7 1.2 Scope .............................................................................................................................. 7 1.3 Reference Documents...................................................................................................... 7 1.4 Acronyms and Definitions ................................................................................................. 8 1.5 Basic Lab Configuration ................................................................................................. 10

Section 2 Test Requirements ......................................................................................................... 12 2.1 UE Initial Registration Using the MSISDN-based SIP URI and Digest-akav2 Authentication

................................................................................................................................... 12 2.2 UE Initial Registration using UICC that has ISIM............................................................. 13 2.3 UE Initiated De-Registration - Airplane Mode.................................................................. 14

Section 3 Basic VoLTE Calls ......................................................................................................... 16 3.1 VoLTE (WB enabled) to PSTN call, VoLTE User Disconnects the Call............................ 16 3.2 VoLTE (WB disabled) to PSTN Call, PSTN User Disconnects the Call............................ 16 3.3 eNB VoLTE (AMR-NB) to VoLTE (AMR-WB) Call, VoLTE User is Forwarded ................. 17 3.4 PSTN to VoLTE (WB enabled) Call, PSTN User Disconnects the Call ............................ 19 3.5 VoLTE to 3GPP/3GPP2 Both Devices WB Enabled, 3GPP/3GPP2 User Disconnects the

Call ................................................................................................................................ 20 3.6 VoLTE (WB Enabled) to 3GPP/3GPP2 (WB Disabled), VoLTE User Disconnects the Call ..

................................................................................................................................... 21 3.7 VoLTE (WB Disabled) to 3GPP/3GPP2 (WB Enabled), VoLTE User Disconnects the Call ..

................................................................................................................................... 22 3.8 3GPP/3GPP2 (WB Enabled) to VoLTE call (WB Enabled), 3GPP/3GPP2 User

Disconnects the Call ...................................................................................................... 22 3.9 3GPP/3GPP2 (WB Disabled) to VoLTE call (WB Disabled), VoLTE User Disconnects the

Call ................................................................................................................................ 23 3.10 VoLTE to VoLTE call, Wideband Enabled on Both Devices. MO Device Disconnects the

Call ................................................................................................................................ 24 3.11 VoLTE to VoLTE call, Narrowband is used on both Devices. MT Device Disconnects the

Call ................................................................................................................................ 24 3.12 VoLTE to VoLTE Call, Call cancelled by MO device ....................................................... 25 3.13 VoLTE to VoLTE Call, Call Ignored by MT Device .......................................................... 26 3.14 VoLTE to VoLTE Call, Both Sides Use Pre-Conditions ................................................... 26 3.15 VoLTE to VoLTE Call, B Side Does Not Support Pre-Conditions .................................... 27 3.16 VoLTE to VoLTE Call, A Side Does Not Support Pre-Conditions .................................... 28 3.17 VoLTE to VoLTE Call, A Side Includes Early Media in Header ........................................ 29 3.18 VOID: VoLTE to VoLTE Call, B Side Includes Early Media in Header ............................. 30 3.19 VoLTE to VoLTE Call, MT Device Busy .......................................................................... 30 3.20 VoLTE to VoLTE Call, URI based INVITE....................................................................... 31



3.21 VoLTE to VoLTE Call, SIP URI based INVITE ................................................................ 31 3.22 DTMF While in VoLTE Call............................................................................................. 32 3.23 VoLTE to VoLTE Call - Long Duration ............................................................................ 33 3.24 VoLTE to VoLTE Call using SIP Compact Header .......................................................... 33 3.25 VoLTE to VoLTE Call when both Devices Supporting EVS ............................................. 35 3.26 VoLTE to VoLTE Call Between Device Supporting EVS and the Other Using AMR-WB .. 36 3.27 VoLTE Call from a Device Supporting EVS to PSTN ...................................................... 36

Section 4 Basic SMS Over IP ........................................................................................................ 38 4.1 VoLTE to VoLTE SMS.................................................................................................... 38

Section 5 IMS Emergency Call ...................................................................................................... 39 5.1 VoLTE Emergency Call Establishment and Release ....................................................... 39

Section 6 Concurrent Use of IMS and Data Services ..................................................................... 41 6.1 Simultaneous Use of VoLTE and UDP UL ...................................................................... 41 6.2 Simultaneous use of VoLTE and UDP DL....................................................................... 42 6.3 Simultaneous VoLTE Call and 2CC CA DL/UL UDP and VoLTE call Initiated before Data

Transfer on 2CC ............................................................................................................ 43 6.4 Simultaneous VoLTE Call and 3CA DL UDP and VoLTE call Initiated before Data Transfer

on 3CA. (Use 2 CA if UE is not capable of supporting 3CA) ............................................ 44 6.5 Simultaneous VoLTE Call and CA UDP and VoLTE Call Initiated after Data Transfer on

UL.................................................................................................................................. 45 Section 7 Basic Mobility ................................................................................................................. 47

7.1 Intra eNB Handover with Ongoing Voice and Data Call................................................... 47 7.2 Inter frequency intra band X2 Handover With Voice and Data Call Between Same

Bandwidth Cells ............................................................................................................. 48 7.3 Inter frequency Intra Band S1 Handover with Voice and Data Call Between Different

Bandwidth Cells ............................................................................................................. 50 7.4 Inter band X2 Handover with Voice and Data Call between Same Bandwidth Cells ........ 52 7.5 Inter band S1 Handover with Voice and Data Call between Different Bandwidth Cells .... 54

Section 8 Failure Scenarios ........................................................................................................... 57 8.1 During Ongoing VoLTE Call, Trigger RLF, UE Trigger Re-Establishment In Different Cell

Same eNB ..................................................................................................................... 57 8.2 During VoLTE call Ringing Phase MO Device Goes Out Of Service ............................... 58 8.3 UE IMS Registration Reject -- Reject Cause 403 Forbidden ........................................... 59 8.4 UE IMS Registration Reject -- Reject Cause 503 Service Unavailable ............................ 60 8.5 UE IMS Registration Reject -- Reject Cause 408 Request Timeout................................. 61

Section 9 TTI Bundling .................................................................................................................. 62 9.1 Activation and Deactivation of TTI Bundling .................................................................... 62 9.2 UE Switch to TTI Bundling Followed by Inter-Frequency Handover................................. 62 9.3 UE Switch to Frequency Hopping Mode ......................................................................... 63



Scope of Level 1 and Basic Test Cases ......................................................................... 65 A.1 Level 1 Test Cases ........................................................................................................ 65 A.2 Basic Test Cases ........................................................................................................... 67

Revision History ............................................................................................................. 69



List of Figures Figure 1.5-1 Basic Lab Configuration .................................................................................................... 11

Figure 7.1-1 Handover Call Flows ......................................................................................................... 48

Figure 7.2-1 X2 Handover Call Flows .................................................................................................... 50

Figure 7.3-1 S1 Handover Call Flows .................................................................................................... 52

Figure 7.4-1 X2 Handover Call Flows .................................................................................................... 54

Figure 7.5-1 S1 Handover Call Flows .................................................................................................... 56

Figure 8.1-1 Radio Link Failure Call Flows ............................................................................................ 58

List of Tables Table 1.4-1 Acronyms and Definitions ...................................................................................................... 8

Table 3.24-1 Compact Header Abbreviations ........................................................................................ 34

Table 5.1-1a Message Flows ................................................................................................................ 40

Table 5.1-1b Message Flows ................................................................................................................ 40

Table 6.1-1a Message Flows ................................................................................................................. 42

Table 6.1-1b Message Flows ................................................................................................................. 42

Table 6.2-1a Message Flows ................................................................................................................. 43

Table 6.2-1b Message Flows ................................................................................................................. 43

Table A.1-1 Level 1 Test Cases ............................................................................................................ 65

Table A-2.1 Basic Test Cases ................................................................................................................ 67



Section 1 Introduction

1.1 Purpose

The purpose of this document is to define the CTIA Certification Program test requirements for VoLTE interoperability. Test requirements are applicable to both FDD and TDD supported bands and bandwidths.

1.2 Scope

This document provides cabled interoperability testing for UE and networks supporting E-UTRA as defined by 3GPP. This document includes relevant protocol related testing as well as functional testing required for interoperability requirements. This testing is intended to be performed in an infrastructure vendor test lab and includes multimode (FDD and/or TDD).

Cabled Interoperability tests are referenced from 3GPP test specifications. All tests listed shall be included as line items in the Cabled Interoperability Test Report.

Cabled Interoperability testing is divided into three levels:

• Level 2 Cabled IOT

• Level 1 Cabled IOT

• Level 0 (Basic) Cabled IOT

Level 2 Cabled Interoperability Testing

Level 2 Cabled IOT Testing is a comprehensive verification effort which determines the interoperability of a device prior to being released.

Level 1 Cabled Interoperability Testing

Level 1 Cabled IOT Testing is defined as a reduced set of test cases from Level 2. This level of testing is used for regression verification and/or certifying a device based on target market requirements.

Level 0 (Basic) Cabled Interoperability Testing

Level 0 (Basic) Cabled IOT Testing is defined as a basic set of test cases from Level 2. This level of testing is used for basic verification and/or certifying a device based on target market requirements.

1.3 Reference Documents

The following documents are referenced in this test plan:

[1] Official Document TS.11: Device Field and Lab Test Guidelines, version 21, October 23, 2017, GSM Association.

[2] TS 24.301: Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3, 3GPP

[3] TS 36.211: Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation, 3GPP

[4] TS 36.213: Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer Procedures, 3GPP

[5] TS 36.300: Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2, 3GPP



[6] TS 36.306: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities, 3GPP

[7] TS 36.331: Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification, 3GPP

[8] 3GPP TS 23.401: General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

[9] 3GPP TS 36.300: Overall description; Stage 2 [10] 3GPP TS 36.101: Technical Specification Group Radio Access Network; Evolved

Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception

[11] 3GPP TS 36.201: LTE physical layer; General description [12] 3GPP TS 36.212: Technical Specification Group Radio Access Network; Evolved

Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding [13] 3GPP TS 36.413: Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1

Application Protocol (S1AP) [14] 3GPP TS 36.423: Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2

Application Protocol (X2AP) [15] 3GPP TS 37.320: Radio measurement collection for Minimization of Drive Tests (MDT);

Overall description; Stage 2 [16] CTIA Certification Interoperability Test Plan for LTE Wireless Devices, the latest version

1.4 Acronyms and Definitions

Table 1.4-1 Acronyms and Definitions

Acronym Definition Cell contents Cell contents

Cell contents 1.1

3GPP 3rd Generation Partnership Project, manages GSM, EDGE, UMTS, HSPA, and LTE standards

APN Access Point Name

ARFCN Absolute Radio Frequency Channel Number

BW Bandwidth

Cell A portion of an eNB

CBRA Contention-Based Random Access

CQI Channel Quality Information

CSR Channel Status Report

DL Downlink

E-UTRA Evolved Universal Terrestrial Radio Access

EARFCN E-UTRA Absolute Radio Frequency Channel Number



Acronym Definition eNB Evolved Node B. An eNB can consist of multiple Cells.

EMM EPS Mobility Management

EPDCCH Enhanced Physical Downlink Control channel

EPC Evolved Packet Core

EPS Evolved Packet System

FDD Frequency Division Duplex

FTP File Transfer Protocol

HO Handover

HTTP Hypertext Transfer Protocol

IMS Internet Protocol Multimedia Subsystem

IOT Interoperability Testing

Ipv4 Internet Protocol version 4

Ipv6 Internet Protocol version 6

LTE Long Term Evolution

MFBI Multiple Frequency Band Indicator

MBMS Multimedia Broadcast and Multicast Service

MBSFN Multicast/Broadcast over Single Frequency Network

MFBI Multiple Frequency Band Indicator

MCS Modulation Code Scheme

MDT Minimization of Drive Test

MIB Master Information Block

Mbps Mega Bits Per Second

NAS Non-Access Stratum

OLSM Open Loop Spatial Multiplexing

CLSM Close Loop Spatial Multiplexing

PDN Packet Data Network

PBCH Physical Broadcast Channel



Acronym Definition PDCCH Physical Downlink Control channel

PDSCH Physical Downlink Shared Channel

PLMN Public Land Mobile Network

PRB Physical Resource Blocks

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

QAM Quadrature Amplitude Modulation

QPSK Quadrature Phase Shift Keying

RAN Radio Access Network

RI Rank Indication

RNTI Radio Network Temporary Identifier

SIB System Information Block

SSS Secondary Synchronization Signal

SIMO Single Input Multiple Output

TDD Time Division Duplex

UDP User Datagram Protocol

UE User Equipment

UL Uplink

1.5 Basic Lab Configuration

Figure 1.5-1 below shows the basic lab configuration, which reflects the network implementation of the VoLTE Wireless 3GPP network deployment.



Figure 1.5-1 Basic Lab Configuration



Section 2 Test Requirements

This section explicitly tests some of the procedures required for initial system acquisition and device access

2.1 UE Initial Registration Using the MSISDN-based SIP URI and Digest-akav2 Authentication

Reference:

• 3GPP TS 24.229 Section 5.1.1

• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To verify the UE shall successfully register on IMS using MSISDN based sip uri and digest-akav2 authentication.

Initial Configuration:

1. UE is powered off. 2. LTE eNB is available. 3. UE and EPS both support voice calls. 4. UE is configured for VoLTE with digest-akav2.

Procedure:

1. Power on the UE.

Expected Results:

1. UE attaches to the LTE/EPC network. 2. UE shall send PDN connectivity request with IMS APN. 3. Network (MME) configure the default bearer for the IMS PDN to be the EPS bearer used

for SIP signaling with correct QCI Value. 4. Verify that UE sends a SIP REGISTER message to P-CSCF with the following.

a. UE uses MSISDN-based SIP URI’s in the FROM or TO headers. b. UE set the value of Expires header to 600 000 seconds. c. UE/IMS client include PANI header: P-access-Network-Info:3GPP-EUTRAN;

utran-cell-id-. d. UE include Authorization header, contact header, via header, Request URI,

security client header. 5. Configure P-CSCF to respond with 401 unauthorized message to challenge the

REGISTER message using DigestAKAV2. 6. Verify UE sends second REGISTER message with challenge response. 7. P-CSCF respond to SIP REGISTER with 200 OK with expire header set to Network

configured expiry timer. 8. Verify UE sends a SIP SUBSCRIBE message to P-CSCF to subscribe to event reg and

set expire header field to 600 000 seconds.



9. P-CSCF responds with 200 OK for the SIP SUBSCRIBE with Expire header set to Network configured expiry timer.

10. Configure P-CSCF to send SIP NOTIFY to UE for the subscription indicating its state. 11. Verify UE responds with 200 OK messages. 12. UE shall successfully be registered with IMS Core and IMS Application server. 13. Verify above steps by checking sip signaling between UE and Network.

2.2 UE Initial Registration using UICC that has ISIM

This test checks that the system can attach a UE, register the user in IMS for the UE with ISIM.

Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 33.203 Section 8.1

• 3GPP TS 24.301

Purpose:

To verify the UE shall successfully register on IMS with ISIM.


1. UE is powered off. 2. LTE eNB is available. 3. UE and EPS both support Voice calls.

Procedure:

1. Power on the UE.

Expected Results:

1. UE attaches to the LTE/EPC network. 2. UE shall send PDN connectivity request with IMS APN. 3. Network (MME) configure the default bearer for the IMS PDN to be the EPS bearer used

for SIP signaling with correct QCI Value. 4. Verify that UE sends a SIP REGISTER message to P-CSCF with the following:

a. UE uses MSISDN-based SIP URI’s in the FROM or TO headers. b. UE set the value of Expires header to 600 000 seconds. c. UE/IMS client include PANI header: P-access-Network-Info:3GPP-EUTRAN;


security client header. 5. Configure P-CSCF to respond with 401 unauthorized message to challenge the

REGISTER message. 6. Verify UE sends second REGISTER message with challenge response.



7. P-CSCF respond to SIP REGISTER with 200 OK with expire header set to Network configured expiry timer.

8. Verify UE sends a SIP SUBSCRIBE message to P-CSCF to subscribe to event reg and set expire header field to 600 000 seconds.

9. P-CSCF responds with 200 OK for the SIP SUBSCRIBE with Expire header set to Network configured expiry timer.

10. Configure P-CSCF to send SIP NOTIFY to UE for the subscription indicating its state. 11. Verify UE responds with 200 OK messages. 12. UE shall successfully be registered with IMS Core and IMS Application server. 13. Verify above steps by checking sip signaling between UE and Network.

2.3 UE Initiated De-Registration - Airplane Mode

This test checks that the UE can de-register in IMS on Airplane Mode.

Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To Verify UE successfully de-registers on IMS due to Airplane Mode on.


1. UE is powered off. 2. LTE eNB is available. 3. UE and EPS both support Voice calls. 4. UE is configured for VoLTE with digest-akav2. 5. UE is configured for IMS APN with IPV4 and IPV6.

Procedure:

1. Power on the UE. 2. UE shall successfully be registered with IMS Core and IMS Application server. 3. Enable airplane mode on UE.

Expected Results:

1. UE attaches to the LTE/EPC network. 2. UE shall send PDN connectivity request with IMS APN. 3. UE shall use PCO to get the IP address to the P-CSCF. 4. Network (MME) configure the default bearer for the IMS PDN to be the EPS bearer used

for SIP signaling with correct QCI Value. 5. Verify that UE sends a SIP REGISTER message to P-CSCF with the following:

a. UE uses MSISDN-based SIP URI’s in the FROM or TO headers.



b. UE set the value of Expires header to 600 000 seconds. c. UE/IMS client include PANI header: P-access-Network-Info: 3GPP-EUTRAN;


security client header.

6. P-CSCF to respond with 401 unauthorized message to challenge the REGISTER message.

7. Verify UE sends second REGISTER message with challenge response. 8. P-CSCF respond to SIP REGISTER with 200 OK with expire header set to Network

configured expiry timer. 9. Verify UE sends a SIP SUBSCRIBE message to P-CSCF to subscribe to event reg and

set expire header field to 600 000 seconds. 10. P-CSCF responds with 200 OK for the SIP SUBSCRIBE with Expire header set to Network

configured expiry timer. 11. Configure P-CSCF to send SIP NOTIFY to UE for the subscription indicating its state. 12. Verify UE responds with 200 OK messages. 13. After step 3 from procedure, verify UE sends below messages to de-register from IMS.

a. SIP SUBSCRIBE message with EXPIRES= 0 for the event reg termination. b. SIP REGISTER message with EXPIRES=0 to indicate de-registration. c. NAS detach request.



Section 3 Basic VoLTE Calls

3.1 VoLTE (WB enabled) to PSTN call, VoLTE User Disconnects the Call

This test checks that the system can originate and release a Voice call between VoLTE UE using the AMR-WB codec for voice and PSTN. In this case the UE under test is originating the call.

Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To verify UE can successfully make VoLTE (AMR-WB) call to PSTN.


1. LTE eNB is available. 2. UE and EPS both support Voice calls. 3. UE is registered with LTE and IMS. 4. UE configured for AMR-WB codec.

Procedure:

1. Make a Voice call from UE to PSTN. 2. Release the call from UE.

Expected Results:

1. In step 1, verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer. Verify minimum of below messages.

a. Verify UE sends SIP INVITE to P-CSCF with SDP containing Media codec supported by UE.

b. Verify S-CSCF forwards SIP INVITE to MGCF. c. VoLTE Voice call to PSTN is established. d. Verify Voice Quality in both ways.

2. In Step 2, verify that the VoLTE call to the PSTN is released and that the EPS bearer used for VoLTE is released, verify minimum of below messages.

a. UE sends BYE to P-CSCF. b. S-CSCF forwards BYE to MGCF. c. MGCF sends 200 OK to S-CSCF.

3.2 VoLTE (WB disabled) to PSTN Call, PSTN User Disconnects the Call

This test checks that the system can originate and release a Voice call between VoLTE UE using the AMR-NB codec for voice and PSTN. In this case the UE under test is originating the call.



Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To Verify UE can successfully make VoLTE (AMR-NB) call to PSTN.


1. LTE eNB is available. 2. UE and EPS both support Voice calls. 3. UE is registered with LTE and IMS. 4. UE configured for AMR-NB codec.

Procedure:

1. Make a Voice call from UE to PSTN. 2. Release the call from PSTN.

Expected Results:


a. Verify UE sends SIP INVITE to P-CSCF with SDP containing Media codec supported by UE.

b. Verify S-CSCF forwards SIP INVITE to MGCF. c. Verify After negotiation for the media attributes AMR-NB is selected as Voice

Codec. d. VoLTE Voice call to PSTN is established. e. Verify Voice Quality in both ways.

2. In Step 2, verify that the VoLTE call to the PSTN is released and that the EPS bearer used for VoLTE is released, verify minimum of below messages.

a. MGCF sends BYE to S-CSCF. b. S-CSCF sends 200 OK to MGCF. c. PCSCF Forwards BYE to UE. d. UE sends 200 OK to P-CSCF.

3.3 eNB VoLTE (AMR-NB) to VoLTE (AMR-WB) Call, VoLTE User is Forwarded

This test checks that the system can originate and release a Voice call between VoLTE (AMR-NB) UE and VoLTE (AMR-WB) UE, VoLTE (AMR-WB) user is forwarded. In this case the VoLTE (AMR-NB) is originating call to UE under test.



Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To verify VoLTE call from PSTN to UE- when VoLTE user (UE) is forwarded.


1. LTE eNB is available. 2. UE-1, UE-2 and EPS both support Voice calls. 3. UE-1, UE-2 are registered with LTE and IMS.

Procedure:

1. Make a Voice call from PSTN to UE-1. 2. UE-1 is forwarded to UE-2. 3. Voice call is established between UE-1 and UE-2. 4. Release the call from PSTN.

Expected Results:

1. In step 2, verify VoLTE UE-1 call is forwarded to UE-2, verify minimum of below messages:

a. Verify MGCF sends SIP INVITE to S-CSCF for the UE-1 with SDP containing Media codec supported by UE.

b. Verify S-CSCF forwards SIP INVITE to TAS. c. Verify TAS forwards SIP INVITE To S-CSCF for UE-2. d. Verify P-CSCF forwards SIP INVITE to UE-2.

2. In step 3, verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer.

a. VoLTE Voice call to UE-2 is established. b. Verify Voice Quality in both ways.

3. In Step 4, verify that the VoLTE call to UE-2 is released and that the EPS bearer used for VoLTE is released. Verify minimum of below messages.

a. MGCF sends BYE to S-CSCF. b. S-CSCF forwards BYE to TAS. c. S-CSCF sends 200 OK to MGCF. d. P-CSCFF sends BYE to UE-2. e. UE-2 responds with 200 OK to P-CSCF.



3.4 PSTN to VoLTE (WB enabled) Call, PSTN User Disconnects the Call

This test checks that the system can originate and release a Voice call between PSTN and VoLTE UE (AMR-WB). In this case the PSTN is originating call to UE under test.

Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To verify UE can successfully receive VoLTE Voice call from PSTN.


1. LTE eNB is available. 2. UE and EPS both support Voice calls. 3. UE is registered with LTE and IMS. 4. UE is configured for AMR-WB codec.

Procedure:

1. Make a Voice call from PSTN to UE. 2. Release the call from PSTN.

Expected Results:


a. MGCF sends SIP INVITE to S-CSCF for UE. b. P-CSCF forwards SIP INVITE to UE. c. P-CSCF sends ACK to UE. d. Verify Voice Quality in both ways.

2. In Step 2, verify that the VoLTE call to UE is released and that the EPS bearer used for VoLTE is released. Verify minimum of below messages.

a. MGCF sends BYE to S-CSCF. b. S-CSCF forwards BYE to TAS. c. S-CSCF sends 200 OK to MGCF. d. P-CSCF sends BYE to UE. e. UE responds with 200 OK to P-CSCF.



3.5 VoLTE to 3GPP/3GPP2 Both Devices WB Enabled, 3GPP/3GPP2 User Disconnects the Call

This test checks that the system can originate and release a Voice call between VoLTE UE (AMR-WB) and 3GPP/3GPP2 (AMR-WB). In this case the VoLTE UE is originating call to 3GPP/3GPP2 UE.

Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To verify UE can successfully make VoLTE Voice call to 3GPP/3GPP2.


1. LTE eNB is available. 2. 3GPP/3GPP2 NodeB is available. 3. UE-1 and EPS both support Voice calls. 4. UE-1 (AMR-WB) is registered on LTE and IMS. 5. UE-2(AMR-WB) is registered on 3GPP/3GPP2.

Procedure:

1. Make a Voice call from UE-1 to UE-2. 2. Release the call from UE-1.

Expected Results:


a. UE-1 sends SIP INVITE to P-CSCF. b. S-CSCF forward SIP INVITE to MGCF. c. UE-1 sends ACK to P-CSCF. d. S-CSCF sends ACK to MGCF. e. Verify Voice Quality in both ways.


a. MGCF sends BYE to S-CSCF. b. S-CSCF forwards BYE to TAS. c. S-CSCF sends 200 OK to MGCF. d. P-CSCF sends BYE to UE.



e. UE responds with 200 OK to P-CSCF.

3.6 VoLTE (WB Enabled) to 3GPP/3GPP2 (WB Disabled), VoLTE User Disconnects the Call

This test checks that the system can originate and release a Voice call between VoLTE UE (AMR-WB) and 3GPP/3GPP2 (WB disabled). In this case the VoLTE UE is originating call to 3GPP/3GPP2 UE.

Reference:


• 3GPP TS 23.203 Table 6.1.7

• 3GPP TS 23.401

• 3GPP TS 23.228

• 3GPP TS 24.301

Purpose:

To verify UE can successfully make VoLTE Voice call to 3GPP/3GPP2 (WB disabled).


1. LTE eNB is available. 2. 3GPP/3GPP2 NodeB is available. 3. UE-1 and EPS both support Voice calls. 4. UE-1 (AMR-WB) is registered on LTE and IMS. 5. UE-2(AMR-NB) is registered on 3GPP/3GPP2.

Procedure:

1. Make a Voice call from UE-1 to UE-2. 2. Release the call from UE-1.

Expected Results:

1. In step 1, verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer. Verify minimum of below messages

a. UE-1 sends SIP INVITE to P-CSCF. b. S-CSCF forward SIP INVITE to MGCF. c. UE-1 sends ACK to P-CSCF. d. S-CSCF sends ACK to MGCF. e. Verify after negotiation for the media attributes, AMR-NB is selected as Voice

Codec. f. Verify Voice Quality in both ways.


a. UE-1 sends BYE to P-CSCF. b. S-CSCF sends BYE to MGCF.



c. M-GCF responds with 200 OK to S-CSCF.

3.7 VoLTE (WB Disabled) to 3GPP/3GPP2 (WB Enabled), VoLTE User Disconnects the Call

This test verifies that the system can originate and release a Voice call between VoLTE UE and 3GPP/3GPP2 (WB enabled). In this case the VoLTE UE is originating call to 3GPP/3GPP2 UE.

Reference:

• 3GPP TS 24.229

• 3GPP TS 24.615

• GSMA IR.92 Section 3.2.1

Purpose:

To verify that the VoLTE device uses the appropriate audio codec during VoLTE call.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls. 3. UEs are attached to LTE and ready for a VoLTE call. 4. The DUT (UE-1) support EVS, NB-AMBR and the UE-2 supports AMR-WB, NB-AMBR.

Procedure:

1. Make a VoLTE call from the UE-1 to UE-2. 2. Call is successfully established and verify audio in both sides. 3. End the call from the UE-1.

Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer.

2. Verify 2-way audio and verify AMR-NB is negotiated for the VoLTE call. 3. Verify VoLTE call to UE-2 subscriber is released and all the bearers are released.

3.8 3GPP/3GPP2 (WB Enabled) to VoLTE call (WB Enabled), 3GPP/3GPP2 User Disconnects the Call

This test verifies that the system can originate and release a Voice call between 3GPP/3GPP2 UE (AMR-WB enabled) and a VoLTE UE (AMR-WB enabled) UE. This call originates from 3GPP/3GPP3 UE to DUT.

Reference:

• 3GPP TS24.229


Purpose:

To verify that the UE (DUT) shall use the appropriate audio codec on a VoLTE call.




1. 3GPP/3GPP2 Base Stations are available. 2. The UE and EPS both support Voice calls. 3. UEs are attached to LTE and ready for a VoLTE call. 4. Both devices support AMR-WB, AMR-NB voice codecs.

Procedure:

1. Make a VoLTE call from the UE-1 to UE-2. 2. Call is successfully established and verify audio in both sides. 3. End the call from UE-2.

Expected Results:

1. In step 1, verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE-1(DUT) has a successful VoLTE call over the dedicated EPS bearer.

2. In Step 2, verify there is audio in both directions and AMR-WB is negotiated between the UE-1 and UE-2.

3. In Step 3, verify VoLTE call to UE-1 is released and that the EPS bearer used for VoLTE is released.

3.9 3GPP/3GPP2 (WB Disabled) to VoLTE call (WB Disabled), VoLTE User Disconnects the Call

This test verifies that the system can originate and release a Voice call between 3GPP/3GPP2 UE with AMR-WB (disabled) and a VoLTE UE (AMRWB disabled.) 3GPP/3GPP2 UE originates the call.

Reference:

• 3GPP TS 24.229


Purpose:



1. 3GPP/3GPP2 Base stations available. 2. The UE and EPS both support Voice calls. 3. UEs are attached to LTE and ready for a VoLTE call. 4. Both devices support AMR-WB, AMR-NB voice codecs.

Procedure:

1. Make a VoLTE call from the UE -1 to UE-2. 2. Call is successfully established and verify audio in both sides. 3. End the call from the UE-2 (DUT) to UE-1.



Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE (DUT) has a successful VoLTE call over the dedicated EPS bearer.

2. Verify there is audio in both directions and AMR-WB is negotiated between the UE-1 and UE-2.

3. Verify VoLTE call to UE-1 is released from UE-2 and that the EPS bearer used for VoLTE is released.

3.10 VoLTE to VoLTE call, Wideband Enabled on Both Devices. MO Device Disconnects the Call

This test verifies that the system can originate and release a Voice call between two VoLTE UE supporting AM-WB.

Reference

• 3GPP TS24.229


Purpose:



1. LTE eNB is available. 2. The UE and EPS both support Voice calls. 3. UEs are attached to LTE and ready to make VoLTE calls. 4. Both devices support AMR-WB, AMR-NB voice codecs.

Procedure:

1. Make a VoLTE call from the UE -1 to UE-2. 2. Call is successfully established and verify audio in both directions. 3. Terminate the call to UE-2.

Expected Results:


2. Verify there is audio in both directions and AMR-WB is negotiated between UE-1 and UE-2.

3. Verify VoLTE call to UE-2 is released and that the EPS bearer used for VoLTE is released.

3.11 VoLTE to VoLTE call, Narrowband is used on both Devices. MT Device Disconnects the Call

This test verifies that the system can originate and release a Voice call between two VoLTE UEs supporting AMR-NB.



Reference:

• 3GPP TS24.229


Purpose:



1. LTE eNB is available. 2. The UE and EPS both support Voice calls. Both UE support AMR-NB. 3. UEs are attached to LTE and ready for a VoLTE call.

Procedure:

1. Make a VoLTE call from the UE-1 to UE-2. 2. Call is successfully established and verify audio in both sides. 3. UE-2 terminates the VoLTE call.

Expected Results:


2. Verify there is audio in both directions and AMR-NB is negotiated between UE -1 and UE-2.

3. Verify VoLTE call to UE (DUT) party is released by UE-2 and that the EPS bearer used for VoLTE is released.

3.12 VoLTE to VoLTE Call, Call cancelled by MO device

This test verifies the UE (DUT) can cancel MO call during setup

Reference:

• 3GPP TS 24.229

• RFC 3665

Purpose:

To verify the UE is capable of sending cancel during call setup.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls. 3. UEs are successfully attached to LTE and IMS and ready for a VoLTE call.

Procedure:

1. Make a VoLTE call from the UE -1 to UE-2.



2. Ensure that the UE-2 do not answer the call. 3. End the call while UE-2 party is alerting.

Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Check the SIP INVITE message.

2. Check UE-2 is alerting (180 ringing). 3. Verify the SIP message in the UE-1 (DUT) and verify CANCEL message is sent.

3.13 VoLTE to VoLTE Call, Call Ignored by MT Device

This test verifies UE can handle unsuccessful MO VoLTE to VoLTE call.

Reference:

• 3GPP TS 24.229

• 3GPP TS 22.030

• IR92.1

Purpose:

To verify the UE can handle unsuccessful MO Voice call when terminating party ignore/reject the call.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls. 3. UEs are attached to LTE and ready for a VoLTE call.

Procedure:

1. Make a VoLTE call from the UE -1 to UE-2. 2. Ensure that UE-2 do not answer the call by either making it Busy or Ignoring the call.

Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE.

2. Verify SIP message from the terminating UE be 486(Busy) or 600 if the end device has a IGNORE/Reject UI and verify the UE-1 (DUT) display “Busy” and has busy tones if code 486 or appropriate display according to Service Provider treatment.

3.14 VoLTE to VoLTE Call, Both Sides Use Pre-Conditions

This test verifies when resource is available, UE should operate the QoS status when pre-conditions are met.

Reference:

• 3GPP TS 24.229

• RFC 3312



• RFC4032

• IR92.1 Section 2.4.1

Purpose:

This test verifies when resource is available, UE should operate the QoS status when pre-conditions are met.


1. LTE eNB is available. 2. The UE an EPS both support Voice calls and registered with IMS. Both UE support SIP

Pre-Condition. Network support Pre-Condition. QoS Resources are available in the Network.

3. UEs are attached to LTE and ready for a VoLTE call.

Procedure:

1. Make a VoLTE call from the UE-1 to UE-2. 2. Answer call at UE-2. 3. End the VoLTE to VoLTE call from the UE-1.

Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer. Check SIP messages for the UE “INVITE” indicating “Precondition” within the “Supported “tag. Verify INVITE message contains Local QoS setting: desired-status attribute (a=des) and MO UPDATE message contains Local QoS setting desired-status attribute (a=des).

2. Verify there is audio in both directions. 3. Verify VoLTE call to UE (DUT) is released by UE-2 and that the EPS bearer used for VoLTE

is released.

3.15 VoLTE to VoLTE Call, B Side Does Not Support Pre-Conditions

This test verifies VoLTE to VoLTE call can be made when one side does not support pre-conditions. The terminating side does not support pre-conditions.

Reference:

• 3GPP TS 24.229

• RFC 3312

• RFC 4032


Purpose:

1. This test verifies when resource are available, and the end VoLTE UE is not supporting pre-conditions, the Originating UE should not apply QoS.




1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. Originating UE support

Pre-Condition and terminating UE does not support. Network support Pre-Condition. QoS Resources are available in the Network.


Procedure:

1. Make a VoLTE call from the UE -1 to UE-2. 2. Answer call at UE-2. 3. End the call between UE-1 and UE-2.

Expected Results:

1. Check SIP messages. Verify “INVITE message indicates “Preconditions within the “Supported “tag. Verify it contains a=des:qos mandatory local “sendrecev”;a=des:qos optional remote “sendrecev”.

2. Verify at the originating UE the MT message received from terminating UE. 3. It can have Session Progress without indicating “Precondition” within the “Require Tag” or

does not indicate “a=des: qos local“or a=des: qos remote “or the Ringing Message does not indicate “Precondition” within the “Supported tag”.

4. Confirm Voice call is established and confirm audio in both directions. 5. Verify call is ended.

3.16 VoLTE to VoLTE Call, A Side Does Not Support Pre-Conditions

This test verifies VoLTE to VoLTE call can be made when one side does not support pre-conditions.

Reference:

• 3GPP TS 24.229

• RFC 3312

• RFC 4032


Purpose:

This test verifies when resource is available and VoLTE UE-1 is not supporting pre-conditions the call is connected.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. VOLTE UE (1) does

not support Pre-Condition and UE (2) support preconditions. Network support Pre-Condition. QoS Resources are available in the Network.




Procedure:

1. Make a MO VoLTE call. 2. Answer call at UE-2. 3. End the call between UE -1 and UE-2.

Expected Results:

1. Verify MO “INVITE” message indicates not supporting Preconditions. 2. Verify at the originating UE the MT message received from terminating UE can any of the

options below. 3. It can have Session Progress does not indicate “a=des: qos local“or a=des: qos remote

“or the Ringing Message does not indicate “Precondition” within the “Supported tag”. 4. Confirm Voice call is established and confirm audio in both directions. 5. Verify call is ended and bearers are released.

3.17 VoLTE to VoLTE Call, A Side Includes Early Media in Header

This test verifies early media can be received and played by UE.

Reference:

• 3GPP TS 24.229

• 3GPP TS 24.628 Section 4.7.2.1


• RFC 3960

Purpose:

This test verifies early media can be received and played by UE before answered by the end user.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. 3. The UE, network and terminating side are all configured and supporting SIP Early Media. 4. UEs are attached to LTE and ready for a VoLTE call. 5. The terminating user a device which sends announcements. The feature is enabled in

terminating device.

Procedure:

1. Make a VoLTE call from UE to the terminating device and let the device ring for a few seconds.

2. Answer call at the terminating device after the announcement. 3. End the call between UE and the terminating device.

Expected Results:

1. Verify UE establishes a connection to the terminating device and announcement is played while it’s ringing. Verify 183 SESSION PROGRESS contains “P-Early-Media” tag.



2. Confirm voice call is established and confirm audio in both directions. 3. Verify call is ended.

3.18 VOID: VoLTE to VoLTE Call, B Side Includes Early Media in Header

Test case is VOID since it is covered by previous test case: This test verifies VoLTE to VoLTE call can be made with Early Media header.

Reference:

• 3GPP TS 24.229

• 3GPP TS 24.628 Section 4.7.2.1


• RFC 3960

Purpose:

This test verifies early media can be received and played by UE before answered by the end user.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. 3. UEs are attached to LTE and ready for a VoLTE call. 4. The UE-1 configured with alternative ringtone.

Procedure:

1. Make a VoLTE call from UE-2 to UE-1. 2. Answer call at the UE-1 after the personal tone is heard on UE-2. 3. End the call between UE and the terminating device.

Expected Results:

1. Verify originating UE has P-Early-Media header field with the “supported” parameter in INVITE message. Verify 183 SESSION PROGRESS contains “P-Early-Media” tag. UE establishes a connection to the terminating device and can hear the alternative ringtone if available. Confirm voice call is established and confirm audio in both directions.

2. Verify call is ended.

3.19 VoLTE to VoLTE Call, MT Device Busy

To verify device can make MO call to an end device which is busy.

Reference:

• 3GPP TS 24.229

Purpose:

To verify device can make MO call to an end device which is busy.




1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. 3. UEs are attached to LTE and ready for a VoLTE call. 4. Make the terminating UE (UE-2) busy with another call.

Procedure:

1. Make a VoLTE call from UE to the terminating device.

Expected Results:

1. Verify MO INVITE message has been sent by the UE. Verify MT SIP INVITE message has SIP code 486. Verify the Originating UE sends busy tones and displays User Busy or similar displays.

3.20 VoLTE to VoLTE Call, URI based INVITE

To verify UE can handle different PUID for outgoing calls.

Reference:

• 3GPP TS 24.229

• 3GPP TS 23.003


Purpose:



1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. 3. UEs are attached to LTE and ready for a VoLTE call. 4. Ensure UE is set for TEL-URI.

Procedure:

1. Make a VoLTE call from UE to the terminating device. 2. End the call.

Expected Results:

1. Verify MO INVITE message has From =tel:xxxx. 2. Verify in Step2 call is ended and all bearers are released.

3.21 VoLTE to VoLTE Call, SIP URI based INVITE




Reference:

• 3GPP TS 24.229

• 3GPP TS 23.003

• IR92.1 Section 2.2.33

Purpose:



1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. 3. UEs are attached to LTE and ready for a VoLTE call. 4. Ensure UE is set for SIP-URI.

Procedure:


Expected Results:

1. Verify MO INVITE message has From =sip:xxxx. 2. Verify in Step2 call is ended and all bearers are released.

3.22 DTMF While in VoLTE Call

This is to verify UE can transmit DTMF tones during a call.

Reference:

• 3GPP TS 24.229

• 3GPP TS 26.114

• IR92 3.3GPP

Purpose:

1. This is to verify UE can transmit DTMF tones during a call.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. 3. UEs are attached to LTE and ready for a VoLTE call. 4. Ensure terminating device supports DTMF.

Procedure:

1. Make a VOLTE call from UE to the terminating device. 2. Send DTMF(0-9,#,*) from the UE to the terminating UE.



3. End the call.

Expected Results:

1. Verify Voice call is established and verify audio in both directions. 2. Verify in Step2 DTMF tones are send correctly at the end device. Verify the RTP packets

to see if the DTMF tones are send correctly.

3.23 VoLTE to VoLTE Call - Long Duration

To verify the UE is able to send SIP Re-Reg after timer expiry during a VoLTE call and that the UE could send periodic refresh of SIP sessions through a re-INVITE or UPDATE request.

Reference:

• 3GPP TS 24.229

• IR.51

• IR.92 3GPP

Purpose:

To verify the UE is able to send SIP Re-Reg after timer expiry during a VoLTE call and that the UE could send periodic refresh of SIP sessions through a re-INVITE or UPDATE request.


1. LTE eNB is available. 2. The UE and EPS both support Voice calls and registered with IMS. 3. UEs are attached to LTE and ready for a VoLTE call. 4. Set the SIP Re-Reg timer to be a smaller value. 5. Maintain the volte call duration to span at least one periodic refresh of SIP sessions

Procedure:


Expected Results:

1. Verify Voice call is established and verify audio in both directions. 2. Verify UE sends SIP Re-Registration (REGISTER) during the ongoing call. Verify UE sends

MO REGISTER Message within the reregistration timer set. 3. Verify UE sends periodic refresh of SIP sessions through a re-INVITE or UPDATE request 4. Verify all bearers are released.

3.24 VoLTE to VoLTE Call using SIP Compact Header

To verify that devices with SIP Compact Header enabled can make VoLTE call successfully.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6





• IR.92 Section 3.2.1

• TS 26.114 Section 6.2.2

Purpose:

This test verifies that devices with SIP Compact Header enabled can make VoLTE call successfully.


1. LTE eNB is available. 2. The UE an EPS both support Voice calls and registered with IMS. Originating UE have SIP

Compact Header enabled. QoS Resources are available in the network. 3. UEs are attached to LTE and ready for a VoLTE call.

Procedure:


Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer. Check SIP messages for the UE “INVITE” including some of the SIP Compact Headers format in Table 3.24-1 below.


is released.

Table 3.24-1 Compact Header Abbreviations

Header Name (Long Format)

Compact Format

Call-ID i

Contact m

Content-Encoding e

Content-Length l

Content-Type c

From f

Subject s



Header Name (Long Format)

Compact Format

Supported k

To t

Via v

3.25 VoLTE to VoLTE Call when both Devices Supporting EVS

To verify that when both devices with EVS enabled can make VoLTE call successfully.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6



• IR.92: 3.2.1

• TS 26.114 Section 6.2.2

Purpose:

This test verifies when both devices with EVS enabled can make VoLTE call successfully.


1. LTE eNB is available. 2. The UE an EPS both support Voice calls and registered with IMS. Both UE support EVS.

QoS Resources are available in the Network. 3. UEs are attached to LTE and ready for a VoLTE call.

Procedure:


Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer. Verify UE sends SIP INVITE to P-CSCF with SDP containing Media codec 13.2 kbps that support by UE.


is released.



3.26 VoLTE to VoLTE Call Between Device Supporting EVS and the Other Using AMR-WB

The test verifies that device with EVS enabled can make VoLTE call successfully to device that supports AMR-WB but not EVS.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6




• TS 26.114 Section 6.2.2

Purpose:

This test verifies that device with EVS enabled can make VoLTE call successfully to device with AMR-WB but not EVS.


1. LTE eNB is available. 2. The UE an EPS both support Voice calls and registered with IMS. Both UE support EVS.

QoS Resources are available in the network. 3. UEs are attached to LTE and ready for a VoLTE call.

Procedure:


Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer. Verify UE sends SIP INVITE to P-CSCF with SDP containing Media codecs 13.2 kbps and 12.65 kbps that support by UE.


is released.

3.27 VoLTE Call from a Device Supporting EVS to PSTN

To verify that a device with EVS enabled can make VoLTE call successfully to PSTN.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6






• TS 26.114 Section 6.2.2

Purpose:

This test verifies that device with EVS enabled can make VoLTE call successfully to PSTN.


1. LTE eNB is available. 2. The UE an EPS both support Voice calls and registered with IMS. UE supports EVS. QoS

Resources are available in the network. 3. PSTN device is available. 4. UE is attached to LTE and ready for a VoLTE call.

Procedure:

1. Make a VoLTE call from the UE to PSTN. 2. Answer call at PSTN. 3. End the VoLTE call from the UE.

Expected Results:

1. Verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful VoLTE call over the dedicated EPS bearer. Verify UE sends SIP INVITE to P-CSCF with SDP containing Media codecs 13.2 kbps that support by UE and G7.11.

2. Verify there is audio in both directions. 3. Verify VoLTE call to UE (DUT) is released by PSTN and that the EPS bearer used for

VoLTE is released.



Section 4 Basic SMS Over IP

4.1 VoLTE to VoLTE SMS

Reference:

• 3GPP TS 24.341

• 3GPP TS 29.002

• 3GPP TS 24.228

Purpose:

To verify the UE under test shall successfully send and receive SMS over IMS and LTE network.


1. The LTE cell is up and transmitting. 2. The UE under test is powered ON. 3. The UE under test has a “message” application. 4. UE under test attaches to the LTE network with default and IMS/SIP bearer.

Procedure:

1. Open the “message” application on UE under test and send an SMS to an MT device which is under VoLTE network.

2. From the MT device, send an SMS to the MO UE under test.

Expected Results:

1. After step 1, UE UNDER TEST should be able to successfully send the SMS. Verify by checking the MT device to check the SMS is received from UE UNDER TEST.

2. After step 2, verify the UE UNDER TEST receives the SMS sent by the MT device. 3. Verify the SIP signaling for both the scenarios.



Section 5 IMS Emergency Call

5.1 VoLTE Emergency Call Establishment and Release

• 3GPP TS 24.229

• 3GPP TS 24.302

• 3GPP TS 24.234

• GSMA IR.51 Section 5.3

Purpose:

To verify the UE shall be able to successfully establish an emergency VoLTE call.


1. The LTE cell is up and transmitting. 2. The UE UNDER TEST is powered ON. 3. UE UNDER TEST is able attach to LTE network with IMS and data bearer established. 4. Network support for PS Emergency including advertisement in SIB1 to indicate that ims-

EmergencySupport-r9 is included and set to true. Network supports EPS Network Feature "Emergency Bearer in S1 Mode Supported".

Procedure:

1. Make an emergency call from the UE UNDER TEST. 2. Terminate the call.

Expected Results:

1. After step 1, check that the UE UNDER TEST requests RRC call establishment cause as “emergency.”

2. UE UNDER TEST requests and gets a dedicated bearer with QCI 1 from the network for the emergency call.

3. Verify the SIP signaling for VoLTE call establishment.



Table 5.1-1a Message Flows

Direction SIP Signaling Comment

UE IMS Request: REGISTER sip:abc.com Status: 401 Unauthorized | Request: REGISTER sip:abc.com Status: 200 OK Request: INVITE urn:service:sos | Status: 100 Trying Status: 180 Ringing Request: PRACK sip:xxx.abc.com:6087;app-session-id=xxxx | Status: 200 OK

4. After step 2, verify the call has ended. Verify SIP signaling for this step.

Table 5.1-1b Message Flows


UE IMS Request: CANCEL urn:service:sos | Status: 200 OK | Status: 487 Request Terminated | Request: ACK urn:service:sos |



Section 6 Concurrent Use of IMS and Data Services

6.1 Simultaneous Use of VoLTE and UDP UL

Reference:

• 3GPP TS 23.228

• 3GPP TS 33.203


• GSMA IR.92 Sections 5.1, 4.3.1


Purpose:

To verify the UE shall be able to successfully establish a VoLTE call and then be also able to do UDP UL traffic.


1. The LTE cell is up and transmitting. 2. The UE under test is powered ON. 3. UE can attach to LTE network with IMS and data bearer established.

Procedure:

1. Make a VoLTE call from MO UE UNDER TEST UE and establish a successful VoLTE call with an MT UE.

2. On the MO UE, open an iperf session and initiate UDP UL traffic to the network. 3. End the VoLTE call from MO UE and stop the iperf data session.

Expected Results:

1. After step 1, make sure the VoLTE call is established successfully by checking audio on UE under test.

2. UE UNDER TEST requests and gets a dedicated bearer with QCI 1 from the network for the voice call.

3. Also verify the SIP signaling for VoLTE call establishment.





UE IMS Request: REGISTER sip:abc.com Status: 401 Unauthorized | Request: REGISTER sip:abc.com Status: 200 OK Request: INVITE 10 tel:MO number; phone-context Status: 100 Trying Status: 180 Ringing Request: PRACK sip:xxx.abc.com:6087;app-session-id=xxxx | Status: 200 OK

4. After step 2, make sure the UDP UL iperf traffic sent by the UE is received on the network successfully.

5. Make sure the VoLTE call doesn’t drop at this point and voice is still clear and audible. 6. After step 3, make sure the call is successfully ended. Verify the SIP signaling for this step.



UE IMS Request: Bye | Status: 200 OK |

6.2 Simultaneous use of VoLTE and UDP DL

Reference:

• 3GPP TS 23.228

• 3GPP TS 33.203




Purpose:

To verify the UE shall be able to successfully establish a VoLTE call and then be also able to do UDP DL traffic.


1. The LTE cell is up and transmitting. 2. The UE under test is powered ON. 3. UE is able to attach to LTE network with IMS and data bearer established.



Procedure:

1. Make a VoLTE call from MO UE UNDER TEST and establish a successful VoLTE call. 2. On the MO UE, open an iperf session and initiate UDP DL traffic from the network. 3. End the VoLTE call from MO UE and stop the iperf data session.

Expected Results:

1. After step 1, make sure the VoLTE call is established successfully by checking audio on both MO and MT sides.

2. UE UNDER TEST requests and gets a dedicated bearer with QCI 1 from the network for the voice call.

3. Also verify the SIP signaling for VoLTE call establishment.



UE IMS Request: REGISTER sip:abc.com Status: 401 Unauthorized | Request: REGISTER sip:abc.com Status: 200 OK Request: INVITE 10 tel:MO number; phone-context Status: 100 Trying Status: 180 Ringing Request: PRACK sip:xxx.abc.com:6087;app-session-id=xxxx | Status: 200 OK

4. After step 2, make sure the UDP DL iperf traffic sent by the network is received from the UE successfully.

5. Make sure the VoLTE call doesn’t drop at this point and voice is still clear and audible on both sides.

6. After step 3, make sure the call is successfully ended. Verify the SIP signaling for this step.



UE IMS Request: Bye | Status: 200 OK |

6.3 Simultaneous VoLTE Call and 2CC CA DL/UL UDP and VoLTE call Initiated before Data Transfer on 2CC

To verify that the UE can successfully perform a VoLTE call before UL/DL Data Transfer on 2CC.



Reference:

• 3GPP TS 23.228

• 3GPP TS 33.203




Purpose:

This test verifies that the UE can successfully perform a VoLTE call before UL/DL Data Transfer on 2CC. Initial Configuration:

1. Configure the primary cell (PCC) and secondary cell (SCC) in the eNB. 2. Configure UE to support VoLTE and carrier aggregation.

Procedure:

1. Ensure that the UE is VoLTE capable and can register on the IMS network (for voice services) and LTE network (for data services) prior to executing any steps beyond powering up the device.

2. Attach the UE to primary cell PCC and perform SIP Registration. 3. Initiate VoLTE call. 4. Initiate maximum UDP Downlink and Uplink traffic (Dependent upon BW combination used)

for 120 seconds. 5. Terminate the VoLTE call after data session ends.

Expected Results:

1. Verify that the device maintains SIP registration throughout the test case. 2. After step 2, verify that the UE attaches successfully and registers on IMS network. After

step 3, verify that the VoLTE call is successful and voice path is ok on both sides. 3. After step 4, verify that SCC is activated and DL and UL throughput is acceptable. Voice

call is not impacted by the CA activation. 4. After step 5, verify that the call ends successfully.

6.4 Simultaneous VoLTE Call and 3CA DL UDP and VoLTE call Initiated before Data Transfer on 3CA. (Use 2 CA if UE is not capable of supporting 3CA)

To verify that the UE can successfully perform a VoLTE call before Data Transfer on 3CA and during simultaneous VoLTE call and data transfer on 3CA DL UDP.

Reference:

• 3GPP TS 23.228

• 3GPP TS 33.203






Purpose:

This test verifies that the UE can successfully perform a VoLTE call before Data Transfer on 3CA. And during simultaneous VoLTE call and data transfer on 3CA DL UDP.


1. Configure the primary cell (PCC) and secondary cell (SCC1) and secondary cell (SCC2) in the eNB.

2. Configure UE to support VoLTE and Three Carrier Aggregation.

Procedure:


2. Attach the UE to PCC and perform SIP Registration. 3. Initiate VoLTE call. 4. Initiate maximum UDP Downlink traffic (Dependent upon BW combination used) for 120

seconds. 5. Terminate the VoLTE call after data session ends.

Expected Results:

1. Verify that the device maintains SIP registration throughout the test case. 2. After step 2, verify that the UE attaches successfully and registers on IMS network. 3. The UE attaches successfully registers on the IMS network. 4. After step 3, verify that the VoLTE call is successful and voice path is ok on both sides. 5. After step 4, verify that both SCCs are activated and DL throughput is acceptable. Voice

call is not impacted by the CA activation. 6. After step 5, verify that the call ends successfully.

6.5 Simultaneous VoLTE Call and CA UDP and VoLTE Call Initiated after Data Transfer on UL

To verify that the UE can successfully perform a VoLTE call after Data Transfer on 2CC ULCA.

Reference:

• 3GPP TS 23.228

• 3GPP TS 33.203




Purpose:

This test verifies that the UE can successfully perform a VoLTE call after Data Transfer on 2CC ULCA and during simultaneous VoLTE call and data transfer on 3CA DL UDP.




1. Configure the primary cell (PCC) and secondary cell (SCC) in the eNB. 2. Configure UE to support VoLTE and Uplink Carrier Aggregation.

Procedure:


2. Attach the UE to PCC and perform SIP Registration. 3. Initiate maximum UDP Uplink traffic for 120 seconds (Dependent upon BW combination

used). 4. Initiate VoLTE call. 5. Terminate the VoLTE call after data session ends.

Expected Results:

1. Verify that the device maintains SIP registration throughout the test case. 2. After Step 2, verify that: UE is configured for ULCA by the network. 3. After Step 3, verify that: ULCA is activated and Uplink YDP throughput is acceptable. 4. After Step 4, verify that: VoLTE call is successful and voice quality is ok on both sides. 5. The voice call is not impacted by the configuration of CA. 6. After Step 5, verify that: Voice call ends successfully.



Section 7 Basic Mobility

7.1 Intra eNB Handover with Ongoing Voice and Data Call

This test checks that UE is able to perform handover between cells within the same eNB during ongoing VoLTE call and FTP data transfer.

Reference:

• 3GPP TS 36.300 Sections 10.1.2, 19.2.2.5, 20.2.2

• 3GPP TS 36.423

• 3GPP TS 25.331

Purpose:

To verify the UE capability to perform handover between cells within the same eNB during ongoing VoLTE call and FTP data transfer.


1. Configure the network to have 1 eNB with at least 2 cells available: both cells have the same frequency (i.e. EARFCN 8303).

2. Configure the LTE RF signaling cell 1 is turned on. 3. Configure the LTE RF signaling cell 2 is turned off. 4. UE under test is powered off.

Procedure:

1. Turn on the UE and make sure it attaches to the cell 1. 2. Make a Voice call from the UE to a B-party SIP subscriber. 3. Set up an FTP session with the UE to an FTP server over IPv4. 4. Transfer the test file from the remote host to the UE. 5. Perform handover from Cell #1 to Cell #2 and back to Cell #1 (bring RF signal cell 2 in and

gradually reduce RF signal cell 1 vice versa). 6. End the FTP session. 7. Release the Voice from the UE.

Expected Results:

• In step 1, verify that UE is attached to primary cell LTE network.

• In step 2, verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful Voice call over the dedicated EPS bearer. Verify the voice quality of the conversation.

• In step 3, verify that UE is able to establish FTP session with FTP server using IPV4 address.

• In step 4, verify that UE is able download a file from FTP server and the data session is ongoing.

• In step 5, verify UE is able to perform handover from cell 1 to cell 2 and handback to cell 1 successfully.

• In step 6, verify that FTP session is successfully ended.



• In Step 7, verify that the Voice call is released and that the EPS bearer used for voice is released

Figure 7.1-1 Handover Call Flows

7.2 Inter frequency intra band X2 Handover With Voice and Data Call Between Same Bandwidth Cells

This test checks that UE is able to perform X2 handover between different frequency, same bandwidth cells during ongoing VoLTE call and FTP data transfer.

Reference: • 3GPP TS 36.300 Sections 10.1.2, 19.2.2.5, 20.2.2

• 3GPP TS 36.423

• 3GPP TS 25.331

Purpose:

To verify the UE capability to perform X2 handover between different frequency, same bandwidth cells during ongoing VoLTE call and FTP data transfer.


1. Configure the network to have 2 eNB Cells are available: cells have a different frequency but same bandwidth.

2. Configure the network to be X2 (i.e. unblock the eNB term point). 3. Configure the network to ensure that the LTE RF signaling cell 1 is turned on. 4. Configure the network to ensure that the LTE RF signaling cell 2 is turned off. 5. UE under test is powered off.



Procedure:

1. Turn on the UE and make sure it attaches to the Primary LTE Cell. 2. Make a Voice call from the UE to a B-party SIP subscriber. 3. Set up an FTP session with the UE to an FTP server over IPv4. 4. Transfer the test file from the remote host to the UE. 5. Perform a X2 handover from eNB Cell #1 to eNB #2 Cell #2 and back to eNB #1Cell #1

(bring RF signal cell 2 in and gradually reduce RF signal cell 1 vice versa). 6. End the FTP session. 7. Release the Voice from the UE.

Expected Results:





• In step 5, verify UE is able to perform X2 handover from cell 1 to cell 2 and handback to cell 1 successfully.


• In step 7, verify that the Voice call is released and that the EPS bearer used for voice is released.



Figure 7.2-1 X2 Handover Call Flows

7.3 Inter frequency Intra Band S1 Handover with Voice and Data Call Between Different Bandwidth Cells

This test checks that UE is able to perform S1 handover between different frequency, different bandwidth cells in the same band during ongoing VoLTE call and FTP data transfer.

Reference:

• 3GPP TS 36.300 Sections 10.1.2, 19.2.2.5, 20.2.2

• 3GPP TS 36.423

• 3GPP TS 25.331



Purpose:

To verify the UE capability to perform S1 handover between different frequency, different bandwidth cells in the same band during ongoing VoLTE call and FTP data transfer.


1. Configure the network to have 2 eNB cells are available: both cells are in the same band but have a different frequency and a different bandwidth.

2. Configure the network to be S1(i.e. block the eNB term points). 3. Configure the network to ensure that the LTE RF signaling cell 1 is turned on. 4. Configure the network to ensure that the LTE RF signaling cell 2 is turned off. 5. UE under test is powered off.

Procedure:

1. Turn on the UE and make sure it attaches to the Primary LTE cell. 2. Make a Voice call from the UE to a B-party SIP subscriber. 3. Set up an FTP session with the UE to an FTP server over IPv4. 4. Transfer the test file from the remote host to the UE. 5. Perform a S1 handover from eNB Cell #1 to eNB #2 Cell #2 and back to eNB #1 Cell #1


Expected Results:





• In step 5, verify UE is able to perform S1 handover from cell 1 to cell 2 and handback to cell 1 successfully.





Figure 7.3-1 S1 Handover Call Flows

7.4 Inter band X2 Handover with Voice and Data Call between Same Bandwidth Cells

This test checks that UE is able to perform X2 handover between different band, same bandwidth cells during ongoing VoLTE call and FTP data transfer.

Reference:

• 3GPP TS 36.300 Sections 10.1.2, 19.2.2.5, 20.2.2

• 3GPP TS 36.423

• 3GPP TS 25.331

Purpose:

To verify the UE capability to perform X2 handover between different band, same bandwidth cells during ongoing VoLTE call and FTP data transfer.




1. Configure the network to have 2 eNB cells are available: cells are on different bands but have the same bandwidth.

2. Configure the network to be X2 (i.e unblock the eNB termpoint). 3. Configure the network to ensure that the LTE RF signaling cell 1 is turned on. 4. Configure the network to ensure that the LTE RF signaling cell 2 is turned off. 5. UE under test is powered off.

Procedure:

1. Turn on the UE and make sure it attaches to the Primary LTE cell. 2. Make a Voice call from the UE to a B-party SIP subscriber. 3. Set up an FTP session with the UE to an FTP server over IPv4. 4. Transfer the test file from the remote host to the UE. 5. Perform a X2 handover from eNB Cell #1 to eNB #2 Cell #2 and back to eNB #1 Cell #1


Expected Results:





• In step 5, verify UE is able to perform X2 handover from cell 1 to cell 2 and handback to cell 1 successfully.





Figure 7.4-1 X2 Handover Call Flows

7.5 Inter band S1 Handover with Voice and Data Call between Different Bandwidth Cells

This test checks that UE is able to perform S1 handover between different band, different bandwidth cells during ongoing VoLTE call and FTP data transfer.

Reference:

• 3GPP TS 36.300 Sections 10.1.2, 19.2.2.5, 20.2.2

• 3GPP TS 36.423

• 3GPP TS 25.331



Purpose:

To verify the UE capability to perform S1 handover between different band, different bandwidth cells during ongoing VoLTE call and FTP data transfer.


1. Configure the network to have 2 eNB cells are available: both cells are in different bands and have a different bandwidth.

2. Configure the network to be S1 (i.e. block the eNB term points). 3. Configure the network to ensure that the LTE RF signaling cell 1 is turned on. 4. Configure the network to ensure that the LTE RF signaling cell 2 is turned off. 5. UE under test is powered off.

Procedure:

1. Turn on the UE and make sure it attaches to the Primary LTE cell. 2. Make a Voice call from the UE to a B-party SIP subscriber. 3. Set up an FTP session with the UE to an FTP server over IPv4. 4. Transfer the test file from the remote host to the UE. 5. Perform a S1 handover from eNB Cell #1 to eNB #2 Cell #2 and back to eNB #1 Cell #1


Expected Results:





• In step 5, verify UE is able to perform S1 handover from cell 1 to cell 2 and handback to cell 1 successfully.





Figure 7.5-1 S1 Handover Call Flows



Section 8 Failure Scenarios

8.1 During Ongoing VoLTE Call, Trigger RLF, UE Trigger Re-Establishment In Different Cell Same eNB

This test checks that UE is able to trigger Radio Link Failure and able to re-establish the ongoing VoLTE call to the new cell within the eNB.

Reference:


• ETSI TS 136 331 Section 5.3.10.7

• 3GPP TS 36.523-1 Sections 8.2.2.3.1, 8.2.4.7

• TS 36.331

Purpose:

To verify the UE capability to trigger Radio Link Failure and able to re-establish the ongoing VoLTE call to the new cell within the eNB.


1. Configure the network with an eNB include at least 2 cells which is capable for VoLTE. 2. Configure eNB to support RLF and Re-Establishment procedures. 3. Configure timers T310 and T311 in the eNB are set to a minimum of 2 seconds and 5

seconds respectively. 4. Configure eNB supports the RRC connection re-establishment procedure. 5. Configure the LTE RF signaling cell 1 is turned on. 6. Configure the LTE RF signaling cell 2 is turned off. 7. UE under test is powered off.

Procedure:

1. Turn on the UE and make sure it attaches to the LTE cell. 2. Make a Voice call from the UE to a B-party SIP subscriber. 3. Rapidly attenuate RF Signal from the cell 1 until it is completely not accessible by the UE

for the 3 seconds. 4. After 3 seconds, rapidly increase the cell 2 signal until UE sees more than -85 RSRP. 5. Release the Voice from the UE.

Expected Results:

• In Step 1, verify that UE is attached to primary cell LTE network.

• In Step 2, verify that a SIP session is established and that the network has established a dedicated EPS bearer with the correct QCI value to the UE. Verify that the UE has a successful Voice call over the dedicated EPS bearer. Verify the voice quality of the conversation.

• In Step 3, verify after signal loss, the UE acquires the primary cell and sends an RCConnectionReestablishmentRequest message to the cell. Verify the primary cell will respond with an RRCConnectionReestablishment and the UE responds with RRCConnectionReestablishmentComplete message. Verify that the RRC message



exchange is successful and that the Reestablishment cause is set the value "Other Failure".

• In step 4, verify that the secondary cell is reconfigured after the Re-establishment on the primary cell. Verify SRB1 has been reconfigured and data traffic is resumed on both cells after reestablishment completed. The eNB activates the configured secondary cell by sending the Activation MAC control element and the UE continues its voice session.

• In Step 5, verify that the Voice call is released and that the EPS bearer used for voice is released.

Figure 8.1-1 Radio Link Failure Call Flows

8.2 During VoLTE call Ringing Phase MO Device Goes Out Of Service

This test checks that UE fails to establish VoLTE call due to out of service while the call is ongoing ringing phase.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6



• IR.92: 3.2.1

• TS 26.114 Section 6.2.2



Purpose:

To verify the UE fails to establish VoLTE call due to out of service while the call is ongoing ringing phase.


1. Configure the network with an eNB capable for VoLTE. 2. Configure eNB to disable the RLF and Re-Establishment procedures. 3. Configure eNB to disable the RRC connection re-establishment procedure. 4. Configure the LTE RF signaling LTE cell is turned on. 5. UE under test is powered off.

Procedure:

1. Turn on the UE and make sure it attaches to the LTE cell. 2. Make a Voice call from the UE to a B-party SIP subscriber. 3. During the ringing state, rapidly attenuate RF Signal from the cell until it is completely not

accessible by the UE (Recommend testing with shield box or shield room). 4. After RF is out of service, UE finally drops the call.

Expected Results:

• In Step 1, verify that UE is attached to primary cell LTE network.

• In Step 2, verify that the caller destination does not pick up the call and the ringing is remained.

• In Step 3, verify after signal loss, the UE is unable to continue the call procedure, and verify that the UE releases the call attempt.

• In Step 4, verify the UE is not lock on any LTE network.

8.3 UE IMS Registration Reject -- Reject Cause 403 Forbidden

This test checks that UE fails IMS Registration due to Reject cause 403 Forbidden.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6




• TS 26.114 Section 6.2.2

Purpose:

To verify the UE fails IMS registration with reject cause 403 Forbidden.




1. Configure the network with an eNB capable for VoLTE. 2. Configure the LTE RF signaling LTE cell is turned on. 3. UE under test is powered off.

Procedure:

1. Power on the UE. 2. IMS registration Reject with 403 Forbidden. 3. UE can not make VoLTE call.

Expected Results:

1. Verify that UE unsuccessful register to the IMS Network due to 403 Forbidden.

8.4 UE IMS Registration Reject -- Reject Cause 503 Service Unavailable

This test checks that UE fails IMS Registration due to Reject cause 503 Service Unavailable.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6




• TS 26.114 Section 6.2.2

Purpose:

To verify the UE fails IMS registration with reject cause 503 Service Unavailable.



Procedure:

1. Power on the UE. 2. IMS registration Reject with 503 Service Unavailable. 3. UE cannot make VoLTE call.

Expected Results:

1. Verify that UE unsuccessful register to the IMS Network due to 503 Service Unavailable.



8.5 UE IMS Registration Reject -- Reject Cause 408 Request Timeout

This test checks that UE fails IMS Registration due to Reject cause 408 Request Timeout.

Reference:

• 3GPP TS 24.605 Section 4.5.2.1

• 3GPP TS 24.147 Sections 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.3.1.6




• TS 26.114 Section 6.2.2

Purpose:

To verify the UE fails to perform IMS Registration due to Reject cause 408 request timeout.



Procedure:

1. Power on the UE. 2. IMS registration Reject with 408 Request Timeout. 3. UE cannot make VoLTE call.

Expected Results:

1. Verify that UE unsuccessful register to the IMS Network due to 408 Request Timeout.



Section 9 TTI Bundling

9.1 Activation and Deactivation of TTI Bundling

Reference:

• 3GPP TS 36.213 Section 5.4.2.1

• 3GPP TS 36.331 Sections 5.4, 5.5

Purpose:

This test checks that a UE can turn on TTI Bundling feature when requested by the network.


1. Cell supports TTI bundling feature and has configured the proper thresholds to trigger bundling such as SNIR or RSPR thresholds.

2. UE is supporting and capable of activating TTI bundling.

Procedure:

1. Attach to the cell that support and configured for TTI bundling. 2. Trigger UL/DL traffic. The type of traffic profile or QCI to trigger bundling depends on eNB

implementation. 3. Triggering TTI bundling, if SINR or RSRP is used for triggering then allow the UE to fall

below certain RSRP or SNIR threshold for the eNB to enable TTI bundling. 4. Continue the UL/DL traffic and allow the UE to rise above the SNIR threshold for the eNB

to disable the UE use of TTI Bundling. 5. Allow the RSPR or SINR threshold to go above the TTI bundling to allow for eNB to disable

bundling.

Expected Results:

1. Verify UE's support for TTI bundling in featureGroupIndicators, bit 3, in the IE UE-EUTRA-Capability.

2. Verify that UL traffic is ongoing which the eNB will use to monitor for triggering TTI bundling. 3. When reaching the configured threshold, verify that the eNB sends an RRC

Reconfiguration message to enable TTI bundling and the UE acknowledges with a RRC Reconfiguration complete message.

4. verify that the UL traffic is continuing without interruption while using TTI bundling. 5. When reaching the configured threshold to disable TTI bundling, verify that the eNB sends

an RRC Reconfiguration message to disable TTI bundling and the UE acknowledges with a RRC Reconfiguration complete message.

9.2 UE Switch to TTI Bundling Followed by Inter-Frequency Handover

Reference:

• 3GPP TS 36.213 Section 5.4.2.1

• 3GPP TS 36.331 Sections 5.4, 5.5



Purpose:

This test checks that a UE can turn on TTI bundling and bundling is could also be enabled after performing inter-frequency handover.


1. Two neighboring cell configured to be on the same band but with different EARFCN. 2. The two cells support TTI bundling feature and have configured the proper thresholds to

trigger bundling such as SNIR or RSPR thresholds. 3. UE is supporting and capable of activating TTI bundling.

Procedure:

1. Attach to the serving and keep the target cell off. 2. Trigger UL/DL traffic. The type of traffic profile or QCI to trigger bundling depends on eNB

implementation. 3. Triggering TTI bundling, if SINR or RSRP is used for triggering then allow the UE to fall

below certain RSRP or SNIR threshold for the eNB to enable TTI bundling. 4. Turn on the target cell and attenuate the serving or target cells to trigger handover. 5. In the target cell, if bundling has not been already enabled, allow the RSPR or SINR

threshold to go below the TTI bundling to allow for eNB to enable TTI bundling.

Expected Results:

1. Verify UE's support for TTI bundling in featureGroupIndicators, bit 3, in the IE UE-EUTRA-Capability.

2. Verify that UL traffic is ongoing which the eNB will use to monitor for triggering TTI bundling. 3. When reaching the configured threshold, verify that the eNB sends an RRC

Reconfiguration message to enable TTI bundling and the UE acknowledges with a RRC Reconfiguration complete message.

4. While UL traffic is continuing, the UE is successfully performed handover to the target cell. 5. When reaching the configured threshold to enable TTI bundling, verify that the eNB sends

an RRC Reconfiguration message to enable TTI bundling and the UE acknowledges with an RRC Reconfiguration complete message.

9.3 UE Switch to Frequency Hopping Mode

Reference:


• 3GPP TS 36.212 Section 5.3.3.1.1

• 3GPP TS 36.213 Section 8.4

Purpose:

This test verifies that a UE can operate in PUSCH Frequency Hopping.




1. Configure the network to have an active eNB that supports PUSCH Frequency Hopping. 2. Configure UE to support PUSCH Frequency Hopping.

Procedure:

1. Connect UE to network. 2. Verify the UE attaches to the network. 3. Verify the network specifies PUSCH details of hopping pattern via SIB2 and DCI 0. 4. Verify the UE performs PUSCH frequency hopping by verifying the single bit Frequency

Hopping (FH) field in a corresponding PDCCH/EPDCCH with DCI format 0 is set to 1 and the uplink resource block assignment is type 0.

Expected Results:

• Verify the UE operates in PUSCH Frequency Hopping.



Scope of Level 1 and Basic Test Cases

A.1 Level 1 Test Cases

Note 1: Band(s) to be tested per Operator Market Endorsement.

Note 2: Only Primary Band is required for execution of all test cases below.

Table A.1-1 Level 1 Test Cases

Test Id Test Title Primary Band

SECTION 2 Test Requirements (Attach and Registration)

2.2 UE initial registration using UICC that has ISIM. X

2.3 UE initiated de-registration - airplane mode. X


3.10 VoLTE to VoLTE call, wideband enabled on both devices. MO device disconnects the call. X

3.11 VoLTE to VoLTE call, wideband disabled on both devices. MT device disconnects the call. X

3.12 VoLTE to VoLTE call, call cancelled by MO device. X

3.13 VoLTE to VoLTE call, call ignored by MT device. X

3.14 VoLTE to VoLTE call, both sides use pre-conditions. X

3.16 VoLTE to VoLTE call, A side does not support pre-conditions. X

3.17 VoLTE to VoLTE call, A side includes Early Media in header. X

3.19 VoLTE to VoLTE call, MT device busy. X

3.20 VoLTE to VoLTE call, tel URI based INVITE. X

3.22 DTMF while in VoLTE call. X

3.23 VoLTE to VoLTE call - long duration. X

3.25 VoLTE to VoLTE Call when both Devices Supporting EVS. X

3.27 VoLTE Call from a Device Supporting EVS to PSTN X

Section 4 Basic SMS Over IP

4.1 VoLTE to VoLTE SMS. X




Test Id Test Title Primary Band

5.1 VoLTE Emergency call establishment and release. X


6.3 Simultaneous VoLTE Call and 2CC CA DL/UL UDP and VoLTE call Initiated before Data Transfer on 2CC X

6.4 Simultaneous VoLTE Call and 3CA DL UDP and VoLTE call Initiated before Data Transfer on 3CA

X

6.5 Simultaneous VoLTE Call and CA UDP and VoLTE Call Initiated after Data Transfer on UL X


7.1 Intra eNB Handover with Ongoing Voice and Data Call X

7.2 Inter frequency intra band X2 Handover With Voice and Data Call Between Same Bandwidth Cells

X

7.4 Inter band X2 Handover with Voice and Data Call between Same Bandwidth Cells X

Section 8 Failure Scenarios


X

8.2 During VoLTE call Ringing Phase MO Device Goes Out Of Service X

8.3 UE IMS Registration Reject -- Reject Cause 403 Forbidden X

8.4 UE IMS Registration Reject -- Reject Cause 503 Service Unavailable X

8.5 UE IMS Registration Reject -- Reject Cause 408 Request Timeout X

SECTION 9 TTI Bundling

9.1 Activation and Deactivation of TTI bundling X

9.2 UE Switch to TTI Bundling Followed by Inter-Frequency Handover X



A.2 Basic Test Cases

Note 1: Band(s) to be tested per Operator Market Endorsement

Note 2: Only Primary Band is required for execution of all test cases below.

Table A-2.1 Basic Test Cases

Test ID Test Title Primary Band

Section 2 Test Requirements (Attach and Registration)

2.2 UE initial registration using UICC that has ISIM. X

2.3 UE initiated de-registration - airplane mode. X


3.13 VoLTE to VoLTE call, call ignored by MT device. X

3.14 VoLTE to VoLTE call, both sides use pre-conditions. X

3.19 VoLTE to VoLTE call, MT device busy. X

3.22 DTMF while in VoLTE call. X

3.25 VoLTE to VoLTE Call when both Devices Supporting EVS. X

SECTION 4 Basic SMS Over IP

4.1 VoLTE to VoLTE SMS. X


5.1 VoLTE Emergency call establishment and release. X


6.4 Simultaneous VoLTE Call and 3CA DL UDP and VoLTE call Initiated before Data Transfer on 3CA X


7.4 Inter band X2 Handover with Voice and Data Call between Same Bandwidth Cells

X

SECTION 8 Failure Scenarios


X



Test ID Test Title Primary Band

8.2 During VoLTE call Ringing Phase MO Device Goes Out Of Service X

8.3 UE IMS Registration Reject -- Reject Cause 403 Forbidden X

8.4 UE IMS Registration Reject -- Reject Cause 503 Service Unavailable X

8.5 UE IMS Registration Reject -- Reject Cause 408 Request Timeout X

Section 9 TTI Bundling

9.1 Activation and Deactivation of TTI bundling X



Revision History

Date Version Description

October 2019 1.0 • Initial Draft

April 2020 1.1 • Added Appendix A to identify Scope of Level 1 and Basic test cases.

• Editorial changes to:

o Update to test cases 6.4, 3.11, 3.17 and 3.23.

o Remove test case 3.18

o Section 1.2 and 1.4

Interoperability Test Plan for VoLTE Wireless Devices

Documents

Transcript of Interoperability Test Plan for VoLTE Wireless Devices