Bluesky E2E-Functional Test-Object-List PA1

Download as xlsx, pdf, or txt
Download as xlsx, pdf, or txt
You are on page 1of 402

End-to-End Functional Acceptace Test

Test Category Pass Conditional Pass

Registration
VoLTE-VoWiFi E2E Site1 Call Set-up (including ICS) 0 0
Supplementary Services
Subscriber Self-Service (Ut)
Handover (SRVCC)
Special Numbers dialing
VoLTE-VoWiFi E2E Site2 Emergency Calls 0 0
Voice Mail

SSC Dialing SITE1 0 0


SSC Dialing SITE2 0 0

3G UMTS Site1 Authentication 0 0


Location Update
Call Handling
3G UMTS Site2 Supplementary Services 0 0

E2E PS Core Site 1 0 0


E2E PS Core Site 2 0 0
PBX Site1 0 0
PBX Site2 0 0
SMSoIP SITE1 0 0
SMSoIP SITE2 0 0
Entitlement SITE1 0 0
Entitlement SITE2 0 0
CS Roaming
LTE Data Roaming
Roaming S8HR VoLTE Roaming 0 0
3G/4G SMS MO/MT
In-bound Roaming
Provisioning 0 0

Inter-Site/ Geographic Redundancy 0 0

GRAND TOTAL 0 0
onal Acceptace Test Cases Summary
Failed Not Applicable To be Completed bBocked Total Test cases

0 0 119 0 119

0 0 119 0 119

0 0 9 0 9
0 0 9 0 9
0 0 31 0 31

0 0 31 0 31
0 0 41 0 41
0 0 41 0 41
0 0 5 0 5
0 0 5 0 5
0 0 11 0 11
0 0 11 0 11
0 0 26 0 26
0 0 26 0 26

0 0 55 0 55

0 0 6 0 6
0 2 99 0 101

0 2 644 0 646
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 3 (402)

Test Case Inform


TOL Ref. Test Object Name / Priority
Level Description / Objective
TC Ref. Test Case Title (P1/P2)
TO-E2E-01 IMS Registration/ Re-Registration/ Deregistration

TC-SITE1-E2E-01.01 VoLTE IMS Registration P1 VoLTE IMS Registration

TC-SITE1-E2E-01.02 VoLTE User Re-registration P1 VoLTE User Re-registration

TC-SITE1-E2E-01.03 VoLTE User De-registration P1 VoLTE User De-registration

TC-SITE1-E2E-01.04 VoWiFi IMS Registration - Trusted P1 VoWiFi IMS Registration

TC-SITE1-E2E-01.05 VoWiFi User Re-registration - Trusted P1 VoWiFi User Re-registration

TC-SITE1-E2E-01.06 VoWiFi User De-registration - Trusted P1 VoWiFi User De-registration

Network initiated De-registration - Administrative Network initiated De-registration -


TC-SITE1-E2E-01.07 (HSS) P1 Administrative (HSS)
Network initiated De-registration - Administrative Network initiated De-registration -
TC-SITE1-E2E-01.08 P1
(S-CSCF) Administrative (S-CSCF)

TC-SITE1-E2E-01.09 Network initiated De-registration - Registration P1 Network initiated De-registration -


Timeout (S-CSCF) Registration Timeout (S-CSCF)

TC-SITE1-E2E-01.10 VoWiFi IMS Registration - Untrusted P1 VoWiFi IMS Registration

TC-SITE1-E2E-01.11 VoWiFi User Re-registration - Untrusted P1 VoWiFi User Re-registration

TC-SITE1-E2E-01.12 VoWiFi User De-registration - Untrusted P1 VoWiFi User De-registration

TO-E2E-02 Call Setup

TC-SITE1-E2E-02.01 Voice call from VoWiFi to VoWiFi - Trusted P1 Call Setup - IMS-WiFi to IMS-WiFi

TC-SITE1-E2E-02.02 Voice call from VoWiFi to VoWiFi - Untrusted P1 Call Setup - IMS-WiFi to IMS-WiFi
Successful calls for following cases:
TC-SITE1-E2E-02.03 Voice call from VoLTE to VoLTE P1 1) without any data session
2) with data session
TC-SITE1-E2E-02.04 Voice call from VoWiFi Trusted to VoLTE P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE1-E2E-02.05 Voice call from VoLTE to VoWiFi Trusted P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE1-E2E-02.06 Voice call from VoWiFi Untrusted to VoLTE P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE1-E2E-02.07 Voice call from VoLTE to VoWiFi Untrusted P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE1-E2E-02.08 Voice call from VoWiFi to PLMN(other operator) via P2 IMS-LTE to PSTN customers
nSBG
Voice call from VoLTE to PLMN(other operator) via
TC-SITE1-E2E-02.09 P2 IMS-LTE to PLMN(other operator)
nSBG

TC-SITE1-E2E-02.10 Voice call from IMS-in-3G to PLMN P1 IMS-IN-3G to PLMN

TC-SITE1-E2E-02.11 Voice call from IMS-in-3G to IMS-in-3G - T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 4 (402)

TC-SITE1-E2E-02.12 Voice call from PSTN/PLMN to IMS-in-3G T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

TC-SITE1-E2E-02.13 Voice call from VoWiFi to IMS-in-3G - T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

TC-SITE1-E2E-02.14 Voice call from VoLTE to IMS-in-3G - T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

TC-SITE1-E2E-02.15 Voice call from IMS-in-3G to VoWiFi - T-SDS P1 IMS-IN-3G to IMS-LTE -T-SDS

TC-SITE1-E2E-02.16 Voice call from IMS-in-3G to VoLTE - T-SDS P1 IMS-IN-3G to IMS-LTE -T-SDS

TC-SITE1-E2E-02.17 Voice call from PSTN/PLMN to VoWiFi - T-SDS P1 PSTN to IMS-LTE - T-SDS

TC-SITE1-E2E-02.18 Voice call from PSTN/PLMN to VoLTE - T-SDS P1 PSTN to IMS-LTE - T-SDS

Voice call from PLMN (other operator) to VoWiFi -


TC-SITE1-E2E-02.19 P2 PLMN (other operator) to IMS-LTE - T-SDS
T-SDS
Voice call from PLMN (other operator) to VoLTE - T-
TC-SITE1-E2E-02.20 P2 PLMN (other operator) to IMS-LTE - T-SDS
SDS
user A cancels the call after ringing (VoLTE to
TC-SITE1-E2E-02.21 Voice call from VoLTE to VoLTE P2
VoLTE) Call clears
user A cancels the call before ringing (VoLTE
TC-SITE1-E2E-02.22 Voice call from VoLTE to VoLTE P2 to VoLTE) Call clears

TO-E2E-03 VoLTE Supplementary Services

TC-SITE1-E2E-03.01 Originating Identification Presentation - OIP P1 Originating Identification Presentation - OIP

TC-SITE1-E2E-03.02 Originating Identification Restriction - OIR P1 Originating Identification Restriction - OIR

Communication Diversion Unconditional - CDIV- Communication Diversion Unconditional -


TC-SITE1-E2E-03.03 P1
CFU CDIV-CFU

TC-SITE1-E2E-03.04 Communication Diversion on Busy - CDIV-CFB P1 Communication Diversion on Busy - CDIV-CFB

Communication Diversion on not Reachable - CDIV- Communication Diversion on not Reachable -


TC-SITE1-E2E-03.05 P1
CFNRc CDIV-CFNRc
Communication Diversion on No Reply - CDIV-
TC-SITE1-E2E-03.06 Communication Diversion on No Reply - CDIV-CFNR P1 CFNR
Barring of All Incoming Calls - ICB
TC-SITE1-E2E-03.07 Barring of All Incoming Calls - ICB P1
(Announcement)

TC-SITE1-E2E-03.08 Barring of All Outgoing Calls - OCB P1 Barring of All Outgoing Calls - OCB
(Announcement)

TC-SITE1-E2E-03.08 Barring of All Outgoing Calls - - hotline P1 Barring of All Outgoing Calls -(hotline)

Barring of Outgoing International Calls - OCB


TC-SITE1-E2E-03.09 Barring of Outgoing International Calls - OCB P1 (Announcement)

TC-SITE1-E2E-03.10 Communication HOLD - Resume P1 Communication HOLD - Resume

TC-SITE1-E2E-03.11 Communication Waiting - Comm. Waiting P1 Communication Waiting - Comm. Waiting

TC-SITE1-E2E-03.12 Ad-Hoc Multi Party Conference - CONF P1 Ad-Hoc Multi Party Conference - CONF

TO-E2E-04 VoWiFi Supplementary Services

TC-SITE1-E2E-04.01 Originating Identification Presentation - OIP P1 Originating Identification Presentation - OIP

TC-SITE1-E2E-04.02 Originating Identification Restriction - OIR P1 Originating Identification Restriction - OIR

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 5 (402)

Communication Diversion Unconditional - CDIV- Communication Diversion Unconditional -


TC-SITE1-E2E-04.03 P1
CFU CDIV-CFU

TC-SITE1-E2E-04.04 Communication Diversion on Busy - CDIV-CFB P1 Communication Diversion on Busy - CDIV-CFB

Communication Diversion on No Reply - CDIV-


TC-SITE1-E2E-04.05 Communication Diversion on No Reply - CDIV-CFNR P1
CFNR

TC-SITE1-E2E-04.06 Barring of All Incoming Calls - ICB P1 Barring of All Incoming Calls - ICB
(Announcement)
Barring of All Outgoing Calls - OCB
TC-SITE1-E2E-04.07 Barring of All Outgoing Calls - OCB P1
(Announcement)
Barring of Outgoing International Calls - OCB
TC-SITE1-E2E-04.08 Barring of Outgoing International Calls - OCB P1 (Announcement)

TC-SITE1-E2E-04.09 Communication HOLD - Resume P1 Communication HOLD - Resume

TC-SITE1-E2E-04.10 Communication Waiting - Comm. Waiting P1 Communication Waiting - Comm. Waiting

TC-SITE1-E2E-04.11 Ad-Hoc Multi Party Conference - CONF P1 Ad-Hoc Multi Party Conference - CONF

TO-E2E-05 VoLTE-VoWiFi Call Forwarding Cases

CFU - VoLTE-A, VoWiFi-B. B has forwarded to


TC-SITE1-E2E-05.01 CFU - VoLTE-A, VoWiFi-B. PSTN (SIP-NNI) - C P1 PSTN (SIP-NNI) - C
CFU - VoWiFi-A, VoLTE-B. B has forwarded to
TC-SITE1-E2E-05.02 CFU - VoWiFi-A, VoLTE-B. PSTN (SIP-NNI) - C P1
PSTN (SIP-NNI) - C

TC-SITE1-E2E-05.03 CFU - PSTN-A, VoLTE-B, VoWiFi-C P1 CFU - Term Call from PSTN (A) to VoLTE-B, B
has forwarded to VoWiFi-C
CFU - Term Call from PSTN (A) to VoWiFi-B, B
TC-SITE1-E2E-05.04 CFU - PSTN-A, VoWiFi-B, VoLTE-C P1
has forwarded to VoLTE-C
CFU - VoLTE-A, VoWiFi-B. B has forwarded to
TC-SITE1-E2E-05.05 CFU - VoLTE-A, VoWiFi-B. VoLTE - C P1
VoLTE - C

TC-SITE1-E2E-05.06 CFU - VoWiFi-A, VoLTE-B. VoWiFi-C P1 CFU - VoWiFi-A, VoLTE-B. B has forwarded to
VoWiFi-C
CFU - VoLTE-A, VoLTE-B. B has forwarded to
TC-SITE1-E2E-05.07 CFU - VoLTE-A, VoLTE-B. 3G CS - C P1
3G CS - C
CFU - VoWiFi-A, VoLTE-B. B has forwarded to
TC-SITE1-E2E-05.08 CFU - VoWiFi-A, VoLTE-B. 3G CS - C P1 3G CS - C
CFU - VoLTE-A, VoWiFi-B. B has forwarded to
TC-SITE1-E2E-05.09 CFU - VoLTE-A, VoWiFi-B. 3G CS - C P1
3G CS - C

TC-SITE1-E2E-05.10 CFU - VoWiFi-A, VoWiFi-B. 3G CS - C P1 CFU - VoWiFi-A, VoWiFi-B. B has forwarded to


3G CS - C

TO-E2E-06 Ut-interface

Communication Diversion Unconditional -


TC-SITE1-E2E-06.01 IMS-WIFI UE, Using Ut, Enable CFU P1 Enable CDIV-CFU via IMS-WiFi
Communication Diversion Unconditional -
TC-SITE1-E2E-06.02 IMS-WIFI UE, Using Ut, Disable CFU P1 Disable CDIV-CFU via IMS-WiFi

TC-SITE1-E2E-06.03 IMS-WIFI UE, Using Ut, Interrogation CFU P1 Check status of CFU via WiFi

TC-SITE1-E2E-06.04 IMS-LTE UE, Using Ut, Enable CFU P1 Communication Diversion Unconditional -
Enable CDIV-CFU via IMS-LTE
Communication Diversion Unconditional -
TC-SITE1-E2E-06.05 IMS-LTE UE, Using Ut, Disable CFU P1
Disable CDIV-CFU via IMS-LTE

TC-SITE1-E2E-06.06 IMS-LTE UE, Using Ut,Interrogation CFU P1 Check status of CFU via IMS-LTE

TO-E2E-07 Handover

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 6 (402)

During VoLTE to VoLTE, Originator moves from LTE During VoLTE to VoLTE, Originator moves
TC-SITE1-E2E-07.01 P1
Access to WIFI Trusted from LTE Access to WIFI
During VoLTE to VoLTE, Terminator moves from During VoLTE to VoLTE, Terminator moves
TC-SITE1-E2E-07.02 LTE Access to WIFI Trusted P1 from LTE Access to WIFI
During VoWiFi to VoLTE, Originator moves from During VoWiFi to VoLTE, Originator moves
TC-SITE1-E2E-07.03 P1
WiFi Trsuted Access to LTE from WiFi Access to LTE

TC-SITE1-E2E-07.04 During VoWiFi to VoWiFi, Terminator moves from P1 During VoWiFi to VoWiFi, Terminator moves
WiFi Trusted Access to LTE from WiFi Access to LTE
During VoLTE to VoLTE, Originator moves from LTE During VoLTE to VoLTE, Originator moves
TC-SITE1-E2E-07.05 P1
Access to WIFI Untrusted from LTE Access to WIFI
During VoLTE to VoLTE, Terminator moves from During VoLTE to VoLTE, Terminator moves
TC-SITE1-E2E-07.06 LTE Access to WIFI Untrusted P1 from LTE Access to WIFI
During VoWiFi to VoLTE, Originator moves from During VoWiFi to VoLTE, Originator moves
TC-SITE1-E2E-07.07 WiFi Untrusted Access to LTE P1 from WiFi Access to LTE
During VoWiFi to VoWiFi, Terminator moves from During VoWiFi to VoWiFi, Terminator moves
TC-SITE1-E2E-07.08 P1
WiFi Untrusted Access to LTE from WiFi Access to LTE
During VoLTE to VoLTE, Originator performs During VoLTE to VoLTE, Originator
TC-SITE1-E2E-07.09
SRVCC P1 performs SRVCC

TC-SITE1-E2E-07.10
During VoLTE to VoLTE, Originator performs P1 During VoLTE to VoLTE, Originator
LTE To LTE handover performs LTE to LTE handover

During VoLTE to VoLTE, Terminator performs During VoLTE to VoLTE, Termintor


TC-SITE1-E2E-07.11
SRVCC P1 performs SRVCC
During VoLTE to PSTN, Originator performs During VoLTE to PSTN, Originator
TC-SITE1-E2E-07.12 P1
SRVCC performs SRVCC
During PSTN call VoLTE, Terminator performs During PSTN to Volte subscriber,
TC-SITE1-E2E-07.13
SRVCC P1 Terminator performs SRVCC
TO-E2E-08 MTAS Number analysis and Call routing (Short codes and long numbers to be updated as per Bluesky requirement)

TC-SITE1-E2E-08.01 IMS call 7-digit dialed number P1 Verify 7-digit dialed number from IMS
subscribers

TC-SITE1-E2E-08.02 IMS call to international number P1 Verify international calls from IMS subscribers

Verify 411 calls from IMS subscribers


TC-SITE1-E2E-08.03 VoLTE call to 411 P1 (18772465052)
Verify 411 calls from IMS subscribers
TC-SITE1-E2E-08.04 VoWifi call to 411 P1
(18772465052)

TC-SITE1-E2E-08.05 VoLTE call to 611 P1 Verify 611 calls from IMS subscribers
(19704673299)
Verify 611 calls from IMS subscribers
TC-SITE1-E2E-08.06 VoWifi call to 611 P1
(19704673299)
Verify 222 calls from IMS subscribers
TC-SITE1-E2E-08.07 VoLTE call to 222 P1
(19704673295)

TC-SITE1-E2E-08.08 VoWifi call to 222 P1 Verify 222 calls from IMS subscribers
(19704673295)
Verify #250 calls from IMS subscribers
TC-SITE1-E2E-08.09 VoLTE call to #250 P1
(8778724114)
Verify #611 calls from IMS subscribers
TC-SITE1-E2E-08.10 VoLTE call to #611 P1 (9704673299)

TC-SITE1-E2E-08.11 VoLTE call to #7623 P1 Verify #7623 calls from IMS subscribers
(8665196373)
Verify *1067 calls from IMS subscribers
TC-SITE1-E2E-08.12 VoLTE call to *1067 P1
(4023712129)
Verify *225 calls from IMS subscribers
TC-SITE1-E2E-08.13 VoLTE call to *225 P1
(9704670414)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 7 (402)

Verify *384 calls from IMS subscribers


TC-SITE1-E2E-08.14 VoLTE call to *384 P1
(3032394501)
Verify *611 calls from IMS subscribers
TC-SITE1-E2E-08.15 VoLTE call to *611 P1 (9704673299)
Verify *646 calls from IMS subscribers
TC-SITE1-E2E-08.16 VoLTE call to *646 P1
(9704673293)

TC-SITE1-E2E-08.17 VoLTE call to *7627 P1 Verify *7627 calls from IMS subscribers
(9704671116)
Verify 9704672222 calls from IMS subscribers
TC-SITE1-E2E-08.18 VoLTE call to 9704672222 P1
(9704673295)
Verify 0 calls from IMS subscribers
TC-SITE1-E2E-08.19 VoLTE call to 0 P1 (9704673299)
Verify 00 calls from IMS subscribers
TC-SITE1-E2E-08.20 VoLTE call to 00 P1 (9704673299)

TO-E2E-09 Emergency call

TC-SITE1-E2E-09.01 VoLTE Emergency 911 P1 Verify 911 call

TC-SITE1-E2E-09.02 VoLTE Emergency 911 (no SIM) P1 Verify 911 call

TC-SITE1-E2E-09.03 VoLTE Emergency 911(SIM/Roaming IN) P1 Verify 911 call

TC-SITE1-E2E-09.04 VoLTE Emergency 911(Suspended) P1 Verify 911 call

TC-SITE1-E2E-09.05 VoWiFi Emergency 911 Trusted P1 VoWiFi Emergency 911

TC-SITE1-E2E-09.06 VoWiFi Emergency 911 Untrusted P1 VoWiFi Emergency 911

TO-E2E-10 Toll-Free (0800 series)

TC-SITE1-E2E-10.01 VoLTE to 08xx series (800, 877 etc.) P1 Verify Toll-free calls

TC-SITE1-E2E-10.02 VoWiFi to 08xx series (800, 877 etc.) P1 Verify Toll-free calls

TO-E2E-11 Voice Mail

TC-SITE1-E2E-11.01 Voice mail deposit Voice mail deposit

TC-SITE1-E2E-11.01 Voice Mail Retrieval from IMS P1 Verify Voice Mail Retrieval from an IMS
subscriber in LTE

TC-SITE1-E2E-11.01 Voice Mail Retrieval from IMS-in-3G P1 Verify Voice Mail Retrieval from an IMS
subscriber in 3G

TC-SITE1-E2E-11.01 Visual Voicemail (if applicable) Verify Voice Mail Retrieval

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 8 (402)

E2E USE CASES vIMS TOL


Test Case Information
Steps

Assumptions:
Assumptions:
1. UE is provisioned for VoLTE
1.
2. UE
LTEisattach
provisioned for VoLTE
is working
2. LTE attach is working
Steps:
Steps:
1. Power up the UE in LTE Coverage where Voice over PS is
1. Power up the UE in LTE Coverage where VoPS Supported
Supported
Assumptions:
2. From the pcap, check the Expires value in the REGISTER and
1. UE ismessage
200OK VoLTE Registered
from the CSCF.
3. Wait until half the timer value has elasped.
Assumptions:
Assumption:
Steps:
4. From theenable
pcap, verify the UE sends another REGISTER to the
1. Power
1. UE is wifi
IMS core.Off the UE
Steps:
1. Power up the UE in Wifi Coverage.
Coverage
2. From the pcap, check the Expires value in the REGISTER and
Assumptions:
200OK
1. UE ismessage from the CSCF.
VoWifi Registered
3. Wait until half the timer value has elasped.
4. From the pcap, verify the UE sends another REGISTER to the
Steps:
Assumptions:
IMS
1. UEcore.
Power Off(LTE/WiFi)
is IMS the UE Registered
Steps:
Assumptions:
1. De-register the subscriber from HSS using command.
1. UE is IMS (LTE/WiFi) Registered
Steps:
2. UE subscription to RegEvents or the SBG subscribing to
1. De-register
RegEvents the subscriber
on behalf of UE. from S-CSCF using command.
Steps:
Assumptions:
Assumption:
1. Check the status of registration in S-CSCF.
1.
2. UE
Makeis wifi
the enable
registered UE not-reachable.
3. Wait until the Registration Timer expires.
Steps:
4. Check the status of registration in S-CSCF.
1. Power up the UE in Wifi Coverage.
Coverage
2. From the pcap, check the Expires value in the REGISTER and
Assumptions:
200OK
1. UE ismessage from the CSCF.
VoWifi Registered
3. Wait until half the timer value has elasped.
4. From the pcap, verify the UE sends another REGISTER to the
Steps:
UE-A
IMS
1. is a registered
core.
Power Off the UE VoWifi user, with no data session running.
UE-B isisaaregistered
UE-A registered VoWifi
VoLTEuser
user, with no data session
running.
UE-A is adials
registered VoWifi user, with no data session running.
1. UE-A
UE-B 10-digits to call UE-B
UE-A
UE-B isis
2. UE-A isaaahears
registered
registered
registered VoLTE
VoWiFi
VoWifi
ringback
user
toneuseruser, with no data session
running.
3. UE-B answers and 2-way voice is verified
1.
1. UE-A
UE-A
UE-B is dials
dials 10-digits
10-digits to to
callcall
UE-BUE-B
4.
2.
UE-A
UE-AUE-A
UE-A is aaends
registered
hears
hears
the
registeredcall VoLTE
ringback
ringback VoLTE tone
tone
user
user, with no data session
5. The call ends at UE-B
running.
3.
1. UE-B
UE-B
UE-A answers
answers
dials and
and
10-digits 2-way
2-way
to voicevoice is verified
is verified
calluser
UE-B
UE-B
4.
4. UE-A
UE-AUE-Ais
is aaends
registered
ends the
the
registeredcall
callVoWiFi
VoWiFi user, with no data session
2.
5. UE-A
The callhears
ends ringback tone
5.
3. The
running.
UE-B call endsatat
answers
UE-B
andUE-B 2-way voice is verified
1.
UE-BUE-Ais dials 10-digits to call UE-B
4.
UE-A
2. UE-A
UE-A
Repeat is aathe
registered
ends
hears the
registered callVoLTE
ringback
test, but VoLTE
this tone
user
user,
time UE-Awith no data
starts session
a data streaming
5. The
running.
3. UE-B call ends at
answers andUE-B 2-way voice is verified
session
1. UE-A (ie youtube).
dials 10-digits to call UE-B
UE-B
4. UE-Ais aends
registered
the callVoWiFi user
2. UE-Athe
Repeat hears ringback
test, but thistone
time UE-A starts a data streaming
5.
3. The
Verify
UE-B call
after ends at
the call
answers andUE-B
is 2-way
up, thevoice
data streaming is still
session
1. UE-A(ie
running.
youtube).
dials 10-digits to call UE-Bis verified
4.
2. UE-A
UE-Athe ends
hears the call
ringback
Repeat
5. The test, but thistone
time UE-A starts a data streaming
Verify
UE-A
3. UE-B acall
is after ends
VoLTEtheuser
answers at
call
andUE-B
is 2-way
up, thevoice
data isstreaming
verified is still
session
UE-B (ie
is a PSTN youtube).
running.
4. UE-A ends user
the call
Repeat
//
5. Block thetrunk
SIP
The call test,towards
ends but
at UE-Bthismetaswitch
time UE-A2&3 starts a data streaming
Verify
1. UE-Aafter
session calls
(ie the
UE-Bcall is up, the data streaming is still
youtube).
UE-A is ahears
running.
2. UE-A VoLTEringback
user.
Repeat
UE-B
3. the
is aanswers
UE-B test,the
external but this time UE-A starts a data streaming
subscriber.
Verify
session after
(ie the callcall
youtube). is up, the data streaming is still
4. Verify
UE-A 2-way audio
is a VoLTE user in 3G coverage.
running.
Action:
5. UE-A ends the call
UE-B
1. is adials
UE-A external
the subscriber.
User B.3G(ICS)
Verify
User
6. TheA –after
VoLTE
call theuser
ends atcallinis
UE-B up, thecoverage
data streaming is still
2. UE-B
User B
running. – answers
VoLTE the
user call.
in 3G(ICS) coverage.
Action:
1. UE-A dials the User B.
To verifyanswers
2. UE-B that a VoLTE UE outside VoLTE coverage can receive
the call.
voice calls from a 3G(ICS) user.
1. Make a call from User A to User B.
2. User B answers the call.
3. Verify the call establishment Date: 2018-02-09
4. Terminate the
Prepared: call fromEdmund
LMIESN either party.Sheridan _x000D_Rev: PA1
Sheet: VoLTE-VoWiFi E2E Site1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 9 (402)
UE-A is a external subscriber.
UE-B is a VoLTE user in 3G coverage.
UE-A is a VoLTE subscriber.
Action:
UE-B
1. is adials
UE-A VoLTE user
theuser inB.3G coverage.
Userin
User A – VoLTE 3G(ICS) coverage
2. UE-B
User B –answers
VoLTE userthe in
call.
3G(ICS) coverage.
Action:
1. UE-A dials the User B.
To verifyanswers
2. UE-B that a VoLTE UE outside VoLTE coverage can receive
the call.
UE-A
voice is a VoLTE
calls from user in 3Guser.
a 3G(ICS) coverage.
UE-B
1. Make a call from User A in
is a VoLTE subscriber to WiFi
User coverage.
B.
2. User
UE-A is B VoLTE
a answers theincall.
user 3G coverage.
Action:
3. Verify the callsubscriber
establishment
UE-B
1. is adials
VoLTE in WiFi coverage.
4. UE-A
Terminate the
the User B. either
call from party.
2. UE-B
UE-A answers the call.
is a PSTN/external user in 3G coverage.
Action:
UE-B is adials
1. UE-A VoLTE
thesubscriber
User B. in WiFi coverage.
2. UE-B
UE-A answers the
is a PSTN/external call.user in 3G coverage.
Action:
UE-B
1. UE-A dials the User B. in WiFi coverage.
is a VoLTE subscriber
2. UE-B
UE-A is aanswers the call.user in 3G coverage.
PSTN/external
Action:
UE-B is adials
1. UE-A VoLTE
thesubscriber
User B. in WiFi coverage.
2. UE-B
UE-A answers the
is a PSTN/external call.user in 3G coverage.
Action:
UE-B
1. UE-A dials the User B. in WiFi coverage.
is a VoLTE subscriber
2. UE-B answers the call.
Action:
UE-A is a VoLTE user
1. UE-A
UE-B is adials theuser
VoLTE User B.
2. UE-B answers the call.
UE-A is ainitiate
1. UE-A VoLTE user
a call with UE-B.
UE-B is acancelled
2. UE-A VoLTE user the call before UE-B ring.
1. UE-A initiate a call with UE-B.
2. UE-A cancelled the call after UE-B ring.
User A is a VoLTE user
User B is a VoLTE user with OIP service activated.
User A is a VoLTE user with OIR service activated.
Action:
User B isA ainitiates
1. User VoLTE usera call to user B.
2. User
User A isB'sa VoLTE
UE ringuserand shows the number of Uesr A.
Action:
User
1. B isA ainitiates
User VoLTE usera callwith CFUB.
to user to PSTN (UE-C)
User A is a VoLTE user
2. User
User B isB'sa UE ringuser
VoLTE andwuth
doesn’t'
CFBshow the number of Uesr A.
to C enabled
Action:
User
1. C isA ainitiates
A
User VoLTE usera call to user B.
User B isanswers
2. UE-C a VoLTEthe user wuth CFNRc to C enabled
call
Action:
User C
A is PLMN
a VoLTE user
user
1. User
User B isA ainitiates
VoLTE usera callwuth
to user B. to C enabled
CFNR
2. User
C isB PLMN
Action:
User rejectsuser
the call
3. User A
1. C answers
initiates athecallcall.
to user B.
2. User B first register in IMS, then take out battery or loose
Action:
User
VoLTE,
1. A is
User A ainitiates
but VoLTE user
keep register
a call toinuser
IMS.B.(no paging to User B)
User B isB
2. User C aanswers
VoLTE answer
doesn't user with
the call. theBaring
call. all incoming calls
3. TheA call
User is a got VoLTEtransfer
user to User C after no answer from User B
Action:
timerBreached.
User
1. User isA adials
VoLTEthe user with
B Baring all outgoing calls
Usercall.
4. User C answers the
2.User
User AAis hears
a VoLTE barring
user announcement
Action:
User
1. B isB adials
User VoLTEthe user
UserwithA Holtline provisioned.
User A is a VoLTE user with service to enable or disable Call
2.UserisBa hears
Barring
UE-A barring announcement
Action: VoLTE user.
UE-B
1. is aB VoLTE
User dials theuser.
User A
Action:
2.User B is connected to the hotline number.
1. User
A isA aenables
Action:
User the International call barring service by dialing
VoLTE user
SSC
User digits
1. UE-A
B isdials
a PSTN the user
User B with SDP offer request.
User A
User
2. UE-B
User isAanswers
C is aadials
VoLTE
VoLTEanthe
international
usercall. number
User
3.User
3. BA
UE-A isholds
a VoLTE
hears barring
the call. announcement
User
4.
ToUE-AC isresume
verify asupplementary
VoLTEthe call. service of call waiting for a VoLTE UE
Make
5. UE-B
with sure
HD holds UsertheA’s
capability UE has been provisioned with the conference
call
factory
1. UE-B URI.
6. User Aresumes
makes an theaudio
call call to User C
To
7. verifyrelease
2. UE-A
Verify multi
the callparty
the audio conference speech call.
call.
establishment
1.
3. User
User A calls User
B calls User A B.
2.
4. User
User C A calls
doesUser A.
not answer the call from User B
3. User
User A isA aputs the call
VoWiFi useron hold and takes the call with User C.
4. Verify
User B is call establishment.
a VoWiFi user with OIP service activated.
5. After the call establishment hit the conference button.
User
6. A is a VoWiFi
Terminate
Action: user with OIR service activated.
the call.
User B isA ainitiates
1. User VoWiFi ausercall to user B.
2. User B's UE ring and shows the number of Uesr A.
Action:
1. User A initiates a call to user B.
2. User B's UE ring and doesn’t' show the number of Uesr A.
Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 10 (402)
User A is a VoWiFi user
User B is a VoWiFi user with CFU to UE-C
User A is VoWiFi user
User B is VoWiFi user wuth CFNA to C enabled
Action:
User C isA VoWiFi
A
1. User initiatesuser
a call to user B.
User B isanswers
2. UE-C VoWiFi the usercall
wuth CFNRc to C enabled
Action:
User C is PSTN
1. User A initiates a call to user B.
2. User
A isB adoPSTN
Action:
User not answer
user 3Gthe usercall until timeout.
2.
1. User
User B isAC aanswers
VoWiFi athe
initiates callcall.
user to user
with B. all incoming calls
Baring
2. User B first register in IMS, then take out battery or loose
VoLTE,
Action:
User A isbut keep register
a VoWiFi user within IMS.
with(no paging
Baring to User B)calls
all outgoing
2. User A
1. C answers
dials the the
Usercall.
B
2. User
Action:
UE-A A hears user.barring announcement
User
1. Ais isVoWiFi
User A VoWiFi
dials the user with Baring all outgoing international calls
UE-B is VoWiFi userUser B
2. User A hears barring announcement
Action:
Action:
User A isA adials
1. User VoLTEan user
international number
1. UE-A
User
2.UserBA isdials the
a VoLTE
hears User
userBannouncement
barring with SDP offer request.
User A
2. UE-B
User is a
C isanswersVoWiFi
a VoLTEthe call.
user
User
3. B isholds
UE-A a VoWiFi
the call.
User
4.
ToUE-AC isresume
verify asupplementary
VoWiFi the call. service of call waiting for a VoLTE UE
Make
5. UE-B
with HDsureholdsUsertheA’s
capability UE has been provisioned with the conference
call
factory
1. UE-B URI.
6. User Aresumes
makes an theaudio
call call to User C
To
7. verifyrelease
2. UE-A
Verify multi
the callparty
the audio conference speech call.
call.
establishment
1.
3. User
User A calls User
B calls User A B.
2.
4. User
User C A calls Userthe
received A. call from User B.
3. User
User A isA aputsVoLTEtheuser
call on hold and takes the call with User C.
4. Verify
User B is call establishment.
a VoWiFi user with CFU to UE-C (PSTN SIP NNI)
5. After the call establishment hit the conference button.
User
6. A is
Terminate
Action: a VoWiFi
the user
call.
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (PSTN SIP NNI)
2. UE-C
User A isanswers
a PSTN the
UE call
Action:
User
1. B isA ainitiates
User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a PSTN the
UE call
Action:
User B isA ainitiates
1. User VoWiFi ausercall with CFUB.to UE-C (VoLTE)
to user
2. UE-C
User A isanswers
a VoLTEthe usercall
Action:
User
1. B isA ainitiates
User VoWiFi ausercall with CFUB.to UE-C (VoLTE)
to user
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User
1. B isA ainitiates
User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C answers the call
Action:
User
1. A isA any
User user a call to user B.
initiates
User B isanswers
2. UE-C a VoWiFi user
the callwith CFU to UE-C
User C is any user
User A is any user
User B is a VoWiFi user with CFU to UE-C
Action:
User C is any
1. Enable CFUuser
on User B's UE through Ut interface(menu)
2. User A initiates a call to user B.
Action:
User A isanswers
3. UE-C any userthe call
1.
4. Disable
User B
A is aany
Disable CFU on
on User
VoWiFi
CFU user user B's
User with
B's UE through
UECFU to UE-C
through Ut
Ut interface(menu)
interface(menu)
2. User
User C isA any
B ainitiates a callwith
useruser
VoLTE to user
CFUB.to UE-C
3. UE-B
User C isanswers
any userthe call
User A is any user
Action:
User B is CFU
1. Check
Action: a VoLTE userB's
on User withUECFU to UE-C
through Ut interface(menu)
User C is any
1. Enable CFUuser
on User B's UE through Ut interface(menu)
2. User A initiates a call to user B.
Action:
User A isanswers
3. UE-C any userthe call
1.
4. Disable
User B is aCFU
Disable VoLTE
CFU on User
on user B's
B's UE
Userwith through
CFU
UE to UE-CUt
through Ut interface(menu)
interface(menu)
2. User
User C isA anyinitiates
user a call to user B.
3. UE-B answers the call
Action:
1. Check CFU on User B's UE through Ut interface(menu)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 11 (402)
UE-A and B are VoWifi user coverage in LTE

1. UE-A and B established a call


UE-A and call
2. During B are VoWifi
UE-A turnuser coverage
off wifi access.in LTE
3. Call should be continue.
1. UE-A and B established a call
UE-A is a VoWifi
2. During user
call UE-B coverage
turn off wifi in Wifi
access.
3. Call should be continue.
1. UE-A
UE-A is aestablished
VoLTE useracoverage
call with anyuser using VoWifi
in LTE Only.
2. During
UE-A callbe
Should turn offenabled.
Wifi Wifi
3. Call should be continue.
1. UE-A
UE-A and established
B are VoWifia call
userwith anyuserinusing
coverage LTE VoLTE
2. During call move from LTE Coverage to Wifi Coverage.
3. UE-A
1. Call should
and B be continue.a call
established
UE-A and call
2. During B are VoWifi
UE-A turnuser coverage
off wifi access.in LTE
3. Call should be continue.
1. UE-A and B established a call
UE-A is a VoWifi
2. During user
call UE-B coverage
turn off wifi in Wifi
access.
3. Call should be continue.
1. UE-A
UE-A is aestablished
VoLTE useracoverage
call with anyuser using VoWifi
in LTE Only.
2. During
UE-A callbe
Should turn offenabled.
Wifi Wifi
3. Call should be continue.
UE-A and
1. UE-A B are VoLTE
established users
a call with anyuser using VoLTE
UE-A and call
2. During B are in a VoLTE
move callCoverage
from LTE with 2-way audioCoverage.
to Wifi verified
3. Call should be continue.
1. UE-A moves from LTE to 3G radio coverage (attenuate the LTE
signal)
UE-A is aattaches
2. UE-A VoLTE userto 3G and the call survives the handover
1. UE-A established a call with anyuser.
2. Move the UE-A using drive testing from one eNodeB Coverage
UE-A and BeNodeB
to another are VoLTE users under different EPC.
Coverage
UE-A and B are in a VoLTE call with 2-way audio verified
UE-A is VoLTE users
1. UE-B
UE-A moves afrom
establish LTEcall
VoLTE to 3G radiosubscriber
to PSTN coverage (attenuate
with 2-waythe LTE
audio
signal)
verified
UE-B is VoLTE
2. UE-B users
attaches to 3G and the call survives the handover
UE-B established
1. UE-A moves from a VoLTE
LTE tocall
3Gfrom
radioPSTN with 2-way
coverage audiothe LTE
(attenuate
verified
signal)
2. UE-A attaches to 3G and the call survives the handover
1. UE-Bismoves
UE-A from LTE
a registered to 3Guser
VoLTE radio coverage (attenuate the LTE
signal)
UE-B
uesky requirement) is a registered VoLTE user
2. UE-B attaches to 3G and the call survives the handover
UE-A is a VoLTE user
UE-B is adials
1. UE-A International
7-digits touser
call UE-B
2. UE-A hears ringback tone
1.
3. UE-A calls UE-Band 2-way voice is verified
UE-B answers
UE-A
2. is ahears
4. UE-A registered
ends callVoLTE user
ringback
the
3.
5. UE-B answers
The call the
ends at UE-Bcall
1.
4. UE-A
is adials
Verify
UE-A 2-way411audio
registered VoWiFi user
2.
5. UE-A hears ringback
ends the call tone
3.
6.
1. UE-B
The
UE-A answers
call ends
dials 411 and
at UE-B2-way voice is verified
UE-A
4. is aends
UE-A registered
the VoLTE user
call
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
611andVoWiFi
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
611andVoLTE
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
222andVoWiFi
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
222andVoLTE
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
#250
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
#611
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
#7623
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
*1067
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
dials *225and 2-way voice is verified
4. UE-A ends the call tone
2. UE-A hears ringback
3. UE-B answers and 2-way voice is verified
4. UE-A ends the call Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 12 (402)
UE-A is a registered VoLTE user

1. UE-A
UE-A is adials *384 VoLTE user
registered
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials *611
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials *646
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials *7627
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials 9704672222
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers
0 andVoLTE
2-way voice is verified
UE-A
4. is adials
registered user
2. UE-A
UE-A ends
hearsthe call tone
ringback
3.
1. UE-B
UE-A answers
dials 00 and 2-way voice is verified
4.
2. UE-A
UE-A ends
hearsthe call tone
ringback
3. UE-B answers and 2-way voice is verified
4. UE-A ends the call
1. VoLTE UE Dial 911 in LTE Coverage.
2. Call connect to PSAP IVR to choose options
1. VoLTE UE without sim card Dial 911 in LTE Coverage.
2. Call connect to PSAP IVR to choose options
1. VoLTE UE roaming in from other operator Dial 911 in LTE
Coverage.
2. Call connect to PSAP IVR to choose options
1. VoLTE UE with sunscription suspended Dial 911 in LTE
Coverage.
2. Call connect to PSAP IVR to choose options
1. VoWiFi UE Dial 911 in Wifi Coverage.
2. Call connect to PSAP IVR to choose options
1. VoWiFi UE Dial 911 in Wifi Coverage.
2. Call connect to PSAP IVR to choose options

1. UE Dial Tollfree number 08xx in LTE Coverage.


2. Call connect to the service.
3. Billing confirmation needed.
1. UE Dial Tollfree number 08xx in WiFi Coverage.
2. Call connect to the service.
3. Billing confirmation needed.

UE-A is a VoLTE user


1. UE-A
UE-A is adials
VoLTEOwn Number.
user
2. UE-A is able to navigate the IVR menus by using the
UE's
1. dial-pad
UE-A
UE-A is adials
VoLTEVoice
usermail retrieval number
in 3G
2. UE-A is able to navigate the IVR menus by using the
UE's
1. dial-pad
UE-A
UE-A is adials
VoLTEVoice
usermail retrieval number
2. UE-A is able to navigate the IVR menus by using the
UE's dial-pad
1. UE-A dials Voice mail retrieval number
2. UE-A is able to navigate the IVR menus by using the
UE's dial-pad

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 13 (402)

E2E USE CASES vIMS TOL


1. Verify that attach request message sequence contains:
a) Prior to communicating with IMS, the UE must establish IPSEC tunnel with EPG.
b) PDN connection to the ims APN via GTP tunnel. Acceptance Test
Pass/fail Criteria Procedure document Test Result
2. Verify that challenge response is sent from I-CSCF to the UE Status-Line: SIP/2.0 401 available
Unauthorized including:
Nonce Value: “…"
1.Cipher
Verify Key:
that attach
"…" request message sequence contains:
Integrity Key: "…"
a) PriorUEto attaches
communicating withregisters
IMS, thetoUE must establish IPSEC tunnel withIMSWMG. To be Completed
1. The to LTE and IMS network connectivity via the APN,
3.
due Verify that Status-Line:
to VoLTE coverage and SIP/2.0
public200 OK isresolution
domain received from the I-CSCF when registration
1.
b) The
PDNUE terminates
connection
is complete.
2. Verify that registration to an
theIMSimsregistrations
200OK via GTPby
APNmessage performing
tunnel.
receives expirationde-registration.
timer Ex: REGISTER To be Completed
message sent by P-CSCF expires”
“sip.contact.parameter: to S-CSCFvalue with Contact header including expire parameter
equal
2.
3. Verify
4. The to
VerifyUE0that
should
that challenge
UE issubscribe
sendingresponse
to theisREGISTRATION
sent from
re-registration andI-CSCF
IMSevent to the
network UE
( P-CSCF Status-Line:
respondgenerates SIP/2.0
a OK 401
with 200
Unauthorized
SUBSCRIBE request including: forward it to the S-CSCF in the home network). To be Completed
Protocol:
Nonce Value:SIP/Register/Contact:
“…" sip:scscfxx.xx.xx.5060/Expires: 0
2. The
5.Cipher UEKey:
3rd party will perform a to
"…"
registration PDN thedisconnection
SCCAS and SIPprocedure port and disconnect from the IMS
APN To be Completed
Integrity
6. The UEKey:
1.MESSAGE "…"from
sent
attaches SCCAS
to LTE andto ATCF with
registers to IMSMSISDN
networkfor SRVCC
connectivity via the IMS APN,
due to VoLTE coverage and public domaine resolution
1.Verify
3.
2. The UEthat terminates
Status-Line:
registration an IMS
SIP/2.0
200OK registrations by
200 OK isreceives
message performing
received fromde-registration.
expiration the timer
I-CSCFEx:whenREGISTER
registration To be Completed
message
is complete. sent by P-CSCF expires”
“sip.contact.parameter: to S-CSCFvalue with Contact header including expire parameter
equal
3. to 0 UE is sending re-registration and IMS network respond with 200 OK
1.Verify
The UEthat terminates an IMS registrations by performing de-registration. REGISTER To be Completed
4. The UEsent
message should subscribe
by P-CSCF to the REGISTRATION
to S-CSCF withsequence
Contact headerevent including
( P-CSCF generates a
Protocol:
1. Verify
SUBSCRIBE SIP/Register/Contact:
that attach
request request
forward it to sip:scscfxx.xx.xx.5060/Expires:
message
the S-CSCF in contains:
the home 0 expire parameter
network).
equal
2. to 0will perform a PDN disconnection procedure and disconnect from the IMS
1.The
TheUE UE terminates an IMS registrations by performing de-registration. REGISTER To be Completed
APN
a)
5. Priorparty
3rd
message to communicating
by P-CSCF towith
registration the IMS,
SCCAS the
and UESIPmust
port establish IPSEC tunnel with WMG.
Protocol: sentSIP/Register/Contact: S-CSCF with Contact header
sip:scscfxx.xx.xx.5060/Expires: including 0 expire parameter
6. The
2. MESSAGE
equal to
UE 0willsentperform from aSCCAS PDN to ATCF with MSISDN
disconnection procedure for and
SRVCC disconnect from the IMS
b) PDN connection to the ims APN via GTP tunnel. To be Completed
APN
Protocol: SIP/Register/Contact: sip:scscfxx.xx.xx.5060/Expires: 0
2.
2. Verify
The UEthat willchallenge
perform aresponse is sent fromprocedure
PDN disconnection I-CSCF to and the UE Status-Line:
disconnect fromSIP/2.0
the IMS 401
1. The status ofincluding:
Unauthorized
APN the UE shows "not registered". To be Completed
Nonce Value: “…"
Cipher
check WMGKey: ue "…"trace.
To be Completed
Integrity
1.
1.Verify Key:
The UEthat "…" touser
VoWiFi
attaches LTE can
and initiate
registers voice
to IMScallnetwork
using 10-digit dialing via
connectivity andthe
AMR-WB
IMS APN,
codec.
due to VoLTE coverage and public domaine resolution
check
3. The WMG
1.Verify
Protocol:
2. UEthat ue
terminates
SIP/SDP. trace.an IMS
Status-Line:
registration SIP/2.0
200OK registrations by
200 OK isreceives
message performing
received fromde-registration.
expiration the timer
I-CSCFEx:whenREGISTER
registration To be Completed
1. Verify
message
is complete.
a) Message that
sent VoWiFi
by
initial
“sip.contact.parameter: P-CSCF
INVITE userexpires”
to can
S-CSCF
coming initiate
withvoice
from
value call
Contact
SBG to using
header
originating 10-digit
including
S-CSCF.dialing andthat
expire
Verify AMR-WB
parameter
SDP AMR-
1. Verify
codec.
equal
that
to 0that
VoLTE user can initiate voice call using 10-digit dialing and
contains
3.
WB Verify
codec.the following
UE is sending attributes:
re-registration and IMS network respond with 200 OK
Protocol:
4. The UE SIP/SDP.
should subscribe to the REGISTRATION event ( P-CSCF generates a To be Completed
Protocol:
a) Message
Protocol: SIP/SDP.
initial(a): INVITE
SIP/Register/Contact: coming fromS-CSCF
SBG toinoriginating S-CSCF. 0 Verify that SDP
SUBSCRIBE
Media request
Attribute forward
rtpmap:104 it tosip:scscfxx.xx.xx.5060/Expires:
the
AMR /16000/1 the home network).
contains
2. The Type:
check
MIME UE
WMGthe following
willAMR-WB
ue trace. attributes:
perform a PDN disconnection procedure and disconnect from the IMS
a)
APN
1. Message
5. Verify
3rd
Sample party
Rate: initial
thatregistration
VoWiFi
16000 INVITE
usertocan coming
the SCCASfrom
initiate voiceSIP
and SBG
call to originating
using
port S-CSCF.
10-digit dialing andVerify
AMR-WB that
1.
SDP Verify
Media
codec. that
contains
Attribute VoLTE
the(a): user
following
rtpmap:104 can initiate
attributes:
6. MESSAGE sent from SCCAS to ATCF with MSISDN for SRVCCAMR voice
/16000/1 call using 10-digit dialing and AMR-
WB
MIME codec.
Protocol:
Verify Type: AMR-WB
SIP/SDP.
P-Access-Network-Info Header: access-type:
1.Message
Verify
Protocol:
Sample
Media
a) that
Rate:
Attribute afterINVITE
SIP/SDP.
16000
initial P-CSCF
(a): receives
rtpmap:104
coming frominitial
AMRSBGINVITE,
/16000/1 theIEEE.802.11
to originating S-CSCF
S-CSCF.
(wlan) based on the
is selected
Verify that SDP
To be Completed
registration information stored in cache.
MIME
contains
2.
2. Verify
check
Ensure Type:
WMGMTAS
that ueAMR-WB
the following
normalizes
thetrace.access
attributes:
the for
type B number
the to +1 and
originating 10-digit
party is a VoWiFi.
Verify
a) P-Access-Network-Info
Message thatinitial INVITE Header:
coming access-type:
from SBG tothe IEEE.802.11
originating (wlan) based
S-CSCF. To be Completed
Sample
3.
1.Verify
1. Verify Rate:
that for16000
after
VoWiFi theP-CSCF
Buser
numberreceives
can the codec
initiate initial
voice negotiated
INVITE,
call using in AMR-WB
S-CSCF
10-digit isdialing andVerify
selected AMR-WB onthat
the
1.
SDP Verify
Media that
contains
Attribute
registration
codec. VoLTE
the
information user
(a):following
rtpmap:104
storedcan initiate
attributes:
inAMR
cache. voice call using 10-digit dialing and AMR-
/16000/1
In
2.
WB
MIMEinitial
Verify
codec.SIP
MTAS
Type: INVITEnormalizes
AMR-WB coming from
the B SBG
number to originating
to +1 and S-CSCF,
10-digit verify that the P-Access-
2. Ensure
Protocol:
Verify that
SIP/SDP. the access type forHeader:the originating party is a3GPP-E-UTRAN-FDD
VoLTE.
3. VerifyP-Access-Network-Info
Network-Info
Protocol:
Sample that
Rate: Header
for
SIP/SDP.
16000 the Bcontains
number the the known access-type:
access
codec negotiated typein“3GPP-E-UTRAN-FDD”.
AMR-WB To be Completed
Media
a)
3. Message
Verify
Media Attribute
initial
that VoLTE
Attribute (a):
INVITEuser
(a):coming rtpmap:104
coming
can originate
rtpmap:104 from AMRSBG /16000/1
to originating
HD voice call using AMR-WB
AMRto/16000/1 S-CSCF. Verify that SDP
codec.
In
MIME
2. initial
contains
Verify
Protocol: SIP
Type:
the INVITE
MTAS AMR-WB
following
SIP/SDP. normalizes from
attributes: the SBGB originating
number to +1 S-CSCF,
and verify that the P-Access-
10-digit
MIME
Verify
4. VerifyType: AMR-WB
P-Access-Network-Info
that initial
RTP is INVITE
established Header:
both access-type:
ways and voice IEEE.802.11
quality (wlan) Verify that
is good. To be Completed
a) Message
Network-Info
Sample
3. Verify
Sample Rate:
that
Rate:
Header
16000
for
16000 the contains
B can coming
number the
thefrom
known
codec SBGnegotiated
access to originating
type S-CSCF.
“3GPP-E-UTRAN-FDD”.
in AMR-WB
5.
3.
SDP Verfy
Verify
Media
a) the
that
contains call
Attribute
Message VoLTE
initial is(a):
the released
user
following
INVITErtpmap:104 properly
coming originate by/16000/1
attributes:
AMR
from either
HD
SBG voice
to party
call usingS-CSCF.
originating AMR-WB codec.
Verify that SDP
Media
2.
6. Verify
Protocol:
MIME Attribute
MTAS
SAPC
SIP/SDP.
Type: Policy
AMR-WB (a):forrtpmap:104
normalizes the B Charging
correct numberAMRto /16000/1
+1 Install
Rule and 10-digit
of Audio Rules & QoS Values in
contains
Verify
4.
MIMEVerify the
that
Type:
3. VerifyRate:
that following
P-Access-Network-Info
RTP
AMR-WB
for is attributes:
established
the B&number Header:
both ways access-type:
and voice
the codec negotiated in AMR-WB quality3GPP-E-UTRAN-FDD
is good. To be Completed
Gx-RAR
Sample
Media
Media for both
Attribute
Attribute 16000 MO (a): MT numbers
rtpmap:104 AMR /16000/1
5. Verfy
Sample
Media
a) the
Rate:call
Attribute
Message initial is(a):
16000
(a):
INVITE
rtpmap:104
released
rtpmap:104 properly
coming
AMR-WB/16000/1
AMR
from by either
/16000/1
SBG party
to originating S-CSCF. Verify that SDP
MIME
Media
6.
2.
MIMEVerify
Verify
contains
Type:
Attribute
SAPC
Type:MTAS
the
AMR-WB
AMR-WB Fieldname:
Policy
following for
normalizes rtpmap
correct
attributes: theCharging
B number Rule Install
to of Audio
+1 IEEE.802.11
and Rules & QoS Values in
10-digit
Verify
Media
Sample
Gx-RAR P-Access-Network-Info
Format:
Rate:
for both 104
16000
MO &established
MT Header:
numbers access-type: (wlan) To be Completed
3.
4. Verify
Sample
Media that
Rate:
Attribute for
16000
RTP(a): the
is B number
rtpmap:104 the
both codec
AMR-WB/16000/1ways negotiated
and voice in AMR-WB
quality is good.
MIME Type: AMR-WB
Media
Media
5.
2. Verfy
Verify
Sample Attribute
Attribute
the call
MTAS
Rate: is(a):
Fieldname:
normalizes
16000 rtpmap:104
released rtpmap
the properly
B number AMRby to/16000/1
either
+1 party
and 10-digit
Verify
4.
6. Verify
MIME
Media
3. Verify
SAPC P-Access-Network-Info
that
Type:
Format:
that
Policy RTP
AMR-WB
for104
has is established
the B number
correct theHeader:
both
Charging ways
codec access-type:
and voice of
negotiated
Rule Install quality3GPP-E-UTRAN-FDD
in AMR-WB
Audio is good.
Rules in Gx-RAR To be Completed
5.
MIMEVerfyType:
Sample
Media
towards the
Rate:call
Attribute
EPG, AMR-WB is(a):
16000
after released
rtpmap:104
receivingproperly AMR
Rx-AARby/16000/1
either
from party
P-CSCF
However,
6. Verify terminating
SAPC Policy user can
for correct only support
Charging AMR-NB.
Ruleto Install of Audio Rules & QoS Values in
2. Verify
Sample
MIME
Protocol: MTAS
Rate:
Type: 16000
AMR-WB
SIP/SDP. normalizes the B number +1 and 10-digit To be Completed
Gx-RAR
3. Verify
Sample
4. Verify for
Rate: both
that
that for
16000
RTP MO is&established
the MT numbersthe
B number both codec
waysnegotiated
and voice qualityin AMR-WB is good.
However,
Media
5.
b) Message terminating
VerfyAttribute
the183 is(a):
callSession user
released canproperly
rtpmap:104
Progress only support
AMRby
coming AMR-NB.
/16000/1
from either
MSCpartyto CSCF. Verify that SDP contains
Protocol:
4.
theVerify
MIME
6. SIP/SDP.
that
Type:
following
SAPC Policy RTP
AMR-WB is established
attributes:
has correct Charging both ways Rule and voice of
Install quality
Audio is good.
Rules in Gx-RAR To be Completed
5. Verfy the
Sample
towards Rate:
EPG,call16000
is released
after receivingproperly Rx-AARby either
from party
P-CSCF
1.
1.
b) UE-A
UE in
Message
6. Verify calls
3G UE-B
(ICS)
183
SAPC Policy originates
Session a
Progress voice call in the CS domain to
Charging Rule Install of Audio Rulesthat
coming
for correctAMR-NB/8000 from MSC to CSCF. party-B.
Verify SDPValues
& QoS containsin
Media
2. UE-B
VerifyAttribute
answers
that the (a):
and
agreedrtpmap:97
two-way
codec voice
is AMR pathWB.is established sussessfully. To be Completed
the
Gx-RAR
Media following
for both
Attribute attributes:
MO
Fieldname:& MT numbers
rtpmap
4. Message
a) Verify that initialRTP is established
INVITE coming from bothMGCF ways to and voice quality
originating is good.
I-CSCF. Verify that SDP
Media
5. Verfy
contains Format:
theAMR
the 97 is
call released
according toproperly
the by eitherrequirement.
preconditions party
Media
MIME Attribute
Type: (a): rtpmap:97 AMR-NB/8000 To be Completed
6.
3. SAPC
MediaVerify thatAMR-NB
Policy
Attribute has
SCCAS correct
Fieldname: Charging
inserts rtpmap
the CSRN number Rule Install of Audio
and routes Rulesininorder
to S-CSCF Gx-RARto break
Sample
towards
out Rate:
to MGCF EPG, 8000
basedafteronreceiving
external NetworkRx-AAR Selection
from P-CSCF
Media Format: 97
4.
MIMEVerify thatAMR-NB
Type: call is completed successfully and audio path is established between UE A
4.
and Verify
UE B. that ENUM request is executed by S-CSCF. Date: 2018-02-09
Sample
Protocol: Rate:
DNS 8000
Prepared: LMIESN Edmund Sheridan Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
xxx1.e164.arpa: type NAPTR, class IN
4.
and Verify that ENUM
response received request
is: Noissuch executed
name by S-CSCF. Ericsson Internal
Protocol:
5. Verify thatDNSthe call break out and the INVITE is sent to the MGCF based on External
xxx1.e164.arpa:
Network Selection settings type NAPTR, class IN
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 14 (402)

1. UE-A calls UE-B


2. UE-B answers and two-way voice path is established sussessfully. To be Completed
UE-A
1. UE in calls UE-Boriginates a voice call in the CS domain to party-B.
3G (ICS)
UE-B answers
2. Verify that theand two-way
agreed codecvoice path
is AMR is established sussessfully.
WB. To be Completed
a) Message initial INVITE coming from MGCF to originating I-CSCF. Verify that SDP
contains the AMR according to the preconditions requirement.
To be Completed
3. Verify that SCCAS inserts the CSRN number and routes to S-CSCF in order to break
out to MGCF
1. UE-A based on external Network Selection
calls UE-B
4. UE-B
2. Verifyanswers
that calland
is completed successfully
two-way voice path is and audio path
established is established between UE A
sussessfully. To be Completed
and UE B.
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed

Call cancelled To be Completed

Call cancelled To be Completed

User B shows the User A's number on screen when calls received from User A. To be Completed

User B doesn't show the User A's number on screen when calls received from User A. To be Completed

1. Call is forwarded to user C by IMS network.


To be Completed
2. User B doesn't ring and User C receives the call.
1. Call is forwarded to user C by IMS network. To be Completed
2. User C can talk with user A.
Test case passes if:
1. Call is forwarded to user C by IMS network. To be Completed
2. User C can talk with user A.
Test case passes if:
1. Call is forwarded to user C by IMS network. To be Completed
2. User C can talk with user A.
1.After
1. The callthefrom
conference
user A to button
user Bisdoes
hit the
notINVITE is sent to the MTAS with the conference
complete
URI andAthe response is a 200 OK To be Completed
2. User hears the barring announcement.
2. UE A has an active session with UE B on hold and a session with the conference
1.
1.The
focus.
UE-A call
UE Afrom
callssends
UE-B user B to user
a REFER to theA does
focusnotandcomplete
sets the conference URI (focus) in the To be Completed
2.
2. User
UE-B Banswers
request hears
URI, andthe barring
Refer-To
and two-way announcement.
headervoicetopath
the URI (PUI) of B. sussessfully.
is established The Refer-To method is set to
INVITE.
3. UE-A preses Hold, and sends re-INVITE/UPDATE
1. The call from user B to user A does not complete with held SDP "a=sendonly"
3. To be Completed
2. The
Userfocus
parameter tosends
B hears theaand
UE-B re-INVITE
barringreceives on200theOK
announcement. existing UE B SDP
with HELD leg .The content ofUE-B
"a=recvonly". the Refer-To
is held (no
header
voice pathis moved
in either to the Request-URI. The re-INVITE includes the SessionId URI and the
direction).
1.Verify
Verifyfeature
‘isfocus’
4. that call waiting
parameter feature has
in the call, been
Contact activated
header. successfully (check using SOAP UI
1. User
get,
4. TheEMA Awhen
got
getsends
focus or
UE-A
connected
puretest
resumesto
a re-INVITE thethe
get) hotthe
on
itnumber..
sends
lineexisting re-INVITE/UPDATE
UE
with held SDP To be Completed
"a=sendrecv" parameter to UE-B and receives 200B OKlegwith
(d2).HELD
The content of the Refer-
SDP "a=sendrecv" and
2.
To Verify
headerthat
two-way VoLTE
is moved
voice path is user
to thecan receive HD
Request-URI.
re-established voicere-INVITE
The
sussessfullycall usingincludes
AMR-WB thecodec.
SessionId URI and
3.
5. User
the A the
canfeature
‘isfocus’
Verify see tears
call theparameter
notification in of
down successfullythethe incoming
Contact
whenheader.
UE-Acallreleases
from User
theB.call header is
An Allow-Events To be Completed
4. Verify that
included and setthe to180 Ringing is sent
‘conference’ back
in case to the caller (User B) with the
mtasConfNotificationService CWA indication
is enabled
present.
5.
6. The
UE-Bfocus
preses responds
Hold, and to A withre-INVITE/UPDATE
sends a 202 Accepted. The ‘isfocus’
with feature
held SDP parameter is
"a=sendonly"
Check
included
parametertheinAlert-Info
theUE-A
to ContactandHeader
header.
receivesin the200SIPOKmessage:
with HELD SDP "a=recvonly". UE-A is held (no To be Completed
Parameter
6. Thepath
voice Focus Line
in Alert-Info:
sends
either Notify<urn:alert:service:call-waiting>
adirection). (100 Trying)
5.
7. Verify
7. Focus that
Verify receives User
when UE-B B
a 200 can hear an
OK (Notify)
resumes announcement being played (ringing)
the call, it sends re-INVITE/UPDATE with while waiting
held SDP
for User A to answer the incoming call. To be Completed
8. 200 OK with SDP offer from B, media direction indicate
"a=sendrecv" parameter to UE-A and receives 200 OK with HELD SDP "a=sendrecv" ‘sendReceive’.200 OK withand
6.
SDPWhen User
voiceApath
forwarded
two-way toignores
focus. the call from sussessfully
is re-established User B, verify User B is forwarded to User A's VM
or
9. the
8. The call
focus
Verify ends
the callif tears
sends user Adown
an INVITE doesn't havewith
request
successfullyVMwhenservicde
the UE-B
UE-Aoffer to thethe
releases MRFcallrequesting MRF to
7. The
add UEcall
B tobetween
the same User A and User
conference C remain
as UE A. up
10. Focus receives a 200 OK with SDP answer from the MRF. Focus sends ACK to the
User B shows the User A's number on screen when calls received from User A.
MRF. To be Completed
11. The focus sends NOTIFY to UE A to indicate the success of the REFER.200 OK in
response to NOTIFY
User B doesn't show(200 the User OK). A's number on screen when calls received from User A. To be Completed
12.Focus sends ACK with SDP answer to UE B; UE B and focus is now in conference
session with media.Ro: CCR update/CCA including Conference-Id and two Related-ICID
AVPs
13.ACK is forwarded to UE B by the terminating AS Date: 2018-02-09
Prepared: LMIESN
14 The Focus initiates EdmundofSheridan
disconnection the replacedSheet: VoLTE-VoWiFi
dialog by sending BYE. E2E Site1 _x000D_Rev: PA1
15. UE A responds with 200 OK Ericsson Internal
16. Media resource for handling UE B on hold is released
17. 200 OK (hold resource release) from MRF
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 15 (402)

1. Call is forwarded to user C by IMS network.


2. User B doesn't ring and User C receives the call.
To be Completed
3. 181
Test Callpasses
case Forwarded
if: and INVITE from MTAS contains the correct cause in the History-
info header
1. Call is forwarded to user C by IMS network.
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call is
info headerforwarded to user C by IMS network.
2. User C can talk with user A. To be Completed
3. 181 Call Forwarded and INVITE from MTAS contains the correct cause in the History-
1. The
info call from user A to user B does not complete
header
2. MTAS blocks the call with 603 Denied To be Completed
1.User
3. UE-AAcalls
hears UE-B
the barring announcement.
1.UE-B
2. The call to theand
answers international
two-way voice numberpathdoes not complete
is established sussessfully.
2.
3. MTAS blocksHold,
UE-A preses the call
andwith
sends603re-INVITE/UPDATE
Denied with held SDP "a=sendonly" To be Completed
3. User A hears
parameter the and
barring announcement.
1. The call toto UE-B receives
the international 200 OKdoes
number with not
HELD SDP "a=recvonly". UE-B is held (no
complete
voice path in either direction).
2. MTAS blocks the call with 603 Denied To be Completed
4.
3. Verify
User when
Athat
hears UE-A
the resumes
barring the call, it sends re-INVITE/UPDATE with held SDP
announcement.
MRF
1. requesting
Verify
"a=sendrecv" call MRF
waiting
parameter tofeature
add UEhas
to UE-B Band
tobeen
the same conference
activated
receives 200 OK withas
successfullyUE
HELD A.
(check using SOAP UIand
SDP "a=sendrecv"
10.
get, Focus receives
EMA voice
two-way get orpath a is
200
puretest OK with SDPsussessfully
get)
re-established answer from the MRF. Focus sends ACK to the To be Completed
MRF.
2.
5. User
UE-B Apreses
can see theand
Hold, notification of the incoming callwith
sends re-INVITE/UPDATE fromheld
UserSDP
B. "a=sendonly"
11.
3. The focus
Verify
parameter sends
thattothe NOTIFY
180and
UE-A Ringing to
is UE
receives sent Aback
200 to
OKindicate the SDP
to theHELD
with success
caller (User of with
B) the REFER.200
the CWA
"a=recvonly". OK
heldin(no
indication
UE-B is
response
voice pathtoinNOTIFY
present. (200 OK).
either direction). To be Completed
12.Focus sendsUE-B
6. Verify when ACK with SDP the
resumes answer
call, to UE B; UE
it sends B and focus is now
re-INVITE/UPDATE in conference
with held SDP
Check
session the
with
"a=sendrecv" Alert-Info
media.Ro:Header
parameter to in
CCR the and
SIP message:
update/CCA
UE-A including
receives 200 Conference-Id
OK with HELD SDPand two Related-ICID
"a=sendrecv" and
Parameter Line path
Alert-Info: <urn:alert:service:call-waiting> To be Completed
AVPs
two-way voice is re-established sussessfully
13.ACK
7. Verifyis the
forwarded
call tearstodown
UE B by the terminating
successfully AS releases the call
when UE-A
14 The Focus initiates disconnection of the replaced dialog by sending BYE.
Test
15. UEcase passes if:with 200 OK
A responds
1.
16.Call is forwarded
Media resource to foruser C by IMS
handling UE Bnetwork.
on hold is released
2.
17.User
200 COKcan talkresource
(hold with userrelease)
A. from MRF To be Completed
Test
3. 181case passes
Call Forwardedif: and
18
1. Termination
Call is forwarded of UE on INVITE
toBuser hold from MTAS contains the correct cause in the History-
C by announcement.
IMS network.
info header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
3. 181 Call Forwarded and INVITE from MTAS contains the correct cause in the History-
info header
1. Call is forwarded to user C by IMS network.
2. User B doesn't ring and User C receives the call.
3. 181 Call Forwarded and INVITE from MTAS contains the correct cause in the History- To be Completed
info header
1. Call is not forwarded to user C by IMS network.
2. User B ring and receives the call. To be Completed
3. INVITE from MTAS contains the destination number.
UE showed CFU status correctly. To be Completed

1. Call is forwarded to user C by IMS network. To be Completed


2. User B doesn't ring and User C receives the call.
1. Call is not forwarded to user C by IMS network.
2. User B ring and receives the call. To be Completed
3. INVITE from MTAS contains the destination number.
UE showed CFU status correctly. To be Completed

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
1. Verify that while a VoWiFi call is established, UE-A undergoes a LTE to WiFi
handover TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 16 (402)
2. Verify messages at the MME
1. a)Verify that while a VoWiFiw/Request
S1 UplinkNASTransport call is established, UE-A undergoes
type: Handover a LTE to WiFi
under Non-Access-Stratum
handover
b) GTPv2 Create Session Request to ims APN w/Handover Indicator set to True
2. c)
Verify messages
Successful at the (Request
Response MME
1. a)Verify that while
S1 UplinkNASTransport call isAccepted)
a VoWiFiw/Request established, UE-A undergoes
type: Handover under a WiFi to LTE
Non-Access-Stratum
To be Completed
3. STR/STA
handover success (EPG to AAA) with Termination-Cause: DIAMETER_USER_MOVED
b) GTPv2
4. Verify
UE registersCreate Session
on VoLTE Request to ims APN w/Handover Indicator set to True
2. messages at thew/PANI
MME setAccepted) to: 3GPP-E-UTRAN-FDD
5. c)
a)
Successful
STR/STA
S1
Response
success (WMG(Request
UplinkNASTransport tow/Request
AAA) with Termination-Cause:
type: Handover underDIAMETER_USER_MOVED
Non-Access-Stratum
To be Completed
3. STR/STA
8. b)
Verify thesuccess (EPG to
call survives theAAA) with Termination-Cause:
handover andAPN
2-way DIAMETER_USER_MOVED
audio continues to work.
UEGTPv2
4. Verify
9.
Create
registers
the SAPC
Session
on VoLTE
policy
Request
w/PANI settoto:ims w/Handover
3GPP-E-UTRAN-FDD Indicator set to True
5. c) Successful
1. STR/STA
Verify that
that Response
while(WMG
success a VoLTE (Request
VoWiFi tocall
AAA) Accepted)
callisisestablished,
established,
with UE-Aundergoes
undergoes
Termination-Cause: aLTE
LTEtotoWiFi
WiFihandover
DIAMETER_USER_MOVED To be Completed
1.
3. Verify
STR/STA while a UE-A a
handover
8. thesuccess
VerifyWiFi)
(enable
(EPG to
call survives theAAA) with Termination-Cause:
handover DIAMETER_USER_MOVED
and 2-way audio continues to work.
4. Verify
2. UE registers
messages on VoLTE
at the w/PANI set to: 3GPP-E-UTRAN-FDD
9.
2.
5. Verify
1. a)
Verify
STR/STA
the
UE-A
that
SAPC
while
success
policy
attaches toMME
a VoWiFi
(WMG the WMG
call andTermination-Cause:
iswith
tow/Request
AAA) IMS UE-A undergoes
established, a LTE to WiFi
DIAMETER_USER_MOVED To be Completed
3. S1 UplinkNASTransport
Verify the call survives the handover type:
and Handover
2-way audio under Non-Access-Stratum
handover
8. b)
Verify
GTPv2the call
Create survives the handover
Session Request to ims APN and 2-way audio continues
w/Handover continues to
to work.
Indicator work.
set to True
4.
2. Verify
Verify
9. c) the SAPC
messages
the SAPC policy
at the
policy MME
Successful
1. a)Verify Response (Request
that while a VoWiFiw/Request Accepted)
call is established, UE-A undergoes a WiFi to LTE To be Completed
3. S1 UplinkNASTransport type: Handover
STR/STA success (EPG to AAA) with Termination-Cause: DIAMETER_USER_MOVED under Non-Access-Stratum
handover
b) GTPv2 Create Session Request toto:ims APN w/Handover Indicator set to True
4. UE
2. c) registers
Verify messages on VoLTE
at thew/PANI
MME setAccepted) 3GPP-E-UTRAN-FDD
5. a) Successful
STR/STA Response
success (WMG(Request
tow/Request
AAA) with Termination-Cause: DIAMETER_USER_MOVED To be Completed
3. S1
STR/STAUplinkNASTransport type: Handover under Non-Access-Stratum
8. b)
Verify
GTPv2thesuccess
Create
(EPG to
call survives
Session theAAA)
Request
with Termination-Cause:
handover to andAPN
ims 2-way DIAMETER_USER_MOVED
audio continues
w/Handover to work.
Indicator set to True
4.
9. UE
1. c) registers
Verify
Verify the
thatSAPCon VoLTE
while policy
a VoLTEw/PANI
call isset to: 3GPP-E-UTRAN-FDD
established, UE-A undergoes an LTE to 3G handover
5. Successful
STR/STA Response
success (WMG (Request
to AAA) Accepted)
with Termination-Cause: DIAMETER_USER_MOVED To be Completed
1. Verify
2. STR/STA
3. that
Verify messages while a
at VoLTE
thetoMME call is established, UE-A undergoes a LTE to WiFi handover
8. Verify
(enable
a) thesuccess
WiFi)
HandoverRequired
(EPG
call survives theAAA) with Termination-Cause:
handover DIAMETER_USER_MOVED
and 2-way audio continues to work.
4.
9. UE registers
Verify on VoLTE w/PANI set to: 3GPP-E-UTRAN-FDD
2.
5. b) PS tothe
Verify
STR/STA UE-A
CS SAPC policyto the WMG and IMS
attaches
request/response
success (WMG to AAA) with Termination-Cause: DIAMETER_USER_MOVED To be Completed
3. Verify
8. c) the
the call survives the
call
HandoverComplete
Verify survives the handover
handover and and 2-way
2-way audio
audio continues
continues to
to work.
work.
4. Verify
9. d) SRVCC
Verify the
thePSSAPC
to CS
SAPC policy
Complete notification/acknowledge
policy
1. To be Completed
3. Verify
PCRF sendsthat Rxafter P-CSCF receives initial
Abort-Session-Request INVITE,
to PCSCF withthe
AVPS-CSCF is selected
Abort-cause = PS tobased
CS
on the registration information stored in cache.
Handover
2.
1. Ensure
4.
1. MSC
Verify thatINVITE
sends
that
Verify forwards
that the access
while
while aato
VoLTE
VoLTE type
the STN-SR
call
call isfor
is ofthe
the originating
established,
established, party is aan
ATCF UE-B undergoes
UE-A undergoes VoLTE.
an LTE to 3G handover
S1 handover or UE-
5.
2.
3. PCSCF
Verify
MTAS messages
normalizes the INVITE
at the
the MME to the
number CSCF containing the SCCAS ATU-STI
B
6. undergoes
CSCF an
forwards X2 handover
the INVITE to the SCCAS, who updates the TO header to UE-A's To be Completed
In
2. a) HandoverRequired
initial
Verify
1. b)
Verify SIP
the
thatINVITE
call acoming
survives
while VoLTEand from
2-way SBG
audio tocontinues
originating S-CSCF,anverify
to work tothat thesip
P-uri
7. Verify
PS tothe
CScall
Access-Network-Info survives
request/response thecall
Header
is established,
handover
contains andthe UE-A
2-way undergoes
audio
known continues
access type
LTE 3G handover
to“3GPP-E-
work.
2.
1. Verify
Verify
c) messages
that VoLTE
HandoverComplete at the
userMME can initiate voice call using 7-digit dialing and AMR-
UTRAN-FDD”.
a) HandoverRequired
WB
4. d) codec.
SRVCC
1. Verify
Verify PS
that
that to
whileCS
VoLTE Complete
a VoLTE
user callnotification/acknowledge
can is established,
originate UE-B undergoes an LTE to 3G handover
toHD voice call using AMR-WB codec.
b) PS to CS request/response To be Completed
3. PCRF
Protocol:
2. Verify sends Rx Abort-Session-Request
SIP/SDP.
messages at the MME PCSCF with AVP Abort-cause = PS to CS
Protocol:
c) SIP/SDP.
HandoverComplete
Handover
a)
d) HandoverRequired
SRVCC PSINVITE
to CS Complete notification/acknowledge
4.
a) MSC
b) PS sends
Messageto CSinitial to the coming
request/response
INVITE STN-SR offrom
the ATCF
SBG to originating S-CSCF. Verify To be Completed
3.
a)
5. PCRF
Message
PCSCF sends
forwardsRx Abort-Session-Request
initial INVITE
the INVITE coming
to fromtocontaining
the CSCF PCSCF
SBG to with
theAVP
originatingAbort-cause
SCCAS S-CSCF. = PS tothat
ATU-STI Verify CS
that
SDP c) HandoverComplete
contains
Handover the following attributes:
1.
SDP Verify
6. d) that
contains
CSCF forwards
SRVCC VoLTE
the
to the
PSINVITE user
following can initiate
attributes: voice
INVITE to notification/acknowledge
CS Complete call to 411 and AMR-WB
the SCCAS, who updates the TO header to UE-B's sip uricodec.
4.
7. MSC
Protocol:
Media sends
SIP/SDP.
VerifyAttribute
the call (a):tortpmap:104
the
theSTN-SR of the ATCF
AMR-WB/16000/1 To be Completed
3. PCRF
Media
5. PCSCF sends
Attribute
forwardsRxsurvives
(a):
the
handover
Abort-Session-Request
rtpmap:104
INVITE to the AMR
and 2-way with
CSCFtocontaining
PCSCF
/16000/1
audioAVPcontinues
the SCCAS
to work.
Abort-cause
ATU-STI = PS to CS
Media
Handover
1.
6. Verify Attribute
CSCFType: that
forwards
Fieldname:
VoWiFi
theINVITEuser can
INVITEcoming
rtpmap
initiate
to the SCCAS, voice call
who updates to 411 and AMR-WB
the TO S-CSCF.
header toVerifycodec.
UE-A's sip uri
MIME
a) Message
Media AMR-WB
initial offrom SBG to originating that
4. VerifyFormat:
7. MSC
Protocol:
Sample
sends
SIP/SDP.
the
Rate: call 104
INVITE to the
survives
16000 theSTN-SR
handover the ATCF
and 2-way audio continues to work.
SDP
MIME contains
5. PCSCF Type: the the
AMR-WB
forwards following
INVITE toattributes:
the CSCF containing the SCCAS ATU-STI
1.
6. Verify
Sample that VoLTE
CSCF forwards
Rate: user can
theINVITE
16000 INVITE initiate
to the SCCAS, voice
who call to 611
updates theand AMR-WB
TO S-CSCF.
header codec.
toVerify
UE-B's sip uri
a) Message
Verify
Protocol:
7. Verify
initial
P-Access-Network-Info
SIP/SDP.
the call survives
coming
the handover
from
Header: SBG to originating
access-type:
and/16000/1 3GPP-E-UTRAN-FDD
2-way audio continues to work.
that To be Completed
Media Attribute (a): rtpmap:104
SDP contains the following attributes: AMR
MIME
1. Type:
However,
Verify that AMR-WB
terminating
VoWiFi user usercancaninitiate
only support AMR-NB.
voice call to 611 and AMR-WB codec.
2.
a) Verify
Message
Sample
Protocol: MTAS
Rate: normalizes
initial
16000
SIP/SDP. INVITE comingthe B number
from SBG toto
+1originating
and 10-digitS-CSCF. Verify that To be Completed
Media
SDP Attribute
3. Verify that the
contains (a):
for the rtpmap:104
B number
following AMR /16000/1
the codec negotiated in AMR-WB
attributes:
MIME
1.
Media Type:
Verify thatAMR-WB
AttributeVoLTE(a): user can initiate
rtpmap:104 AMR voice call to 2223GPP-E-UTRAN-FDD
/16000/1 and AMR-WB codec.
Verify
b)
a)
Sample P-Access-Network-Info
Message
Rate:183
initialSession
16000 INVITE Progress
coming Header:
coming
from access-type:
SBG from MSC to CSCF.
to originating Verify
S-CSCF. that that
Verify SDP To be Completed
Protocol:
MIME
Media Type:SIP/SDP.
AMR-WB
Attribute (a): rtpmap:104 AMR /16000/1
contains
SDP the following
contains the following attributes:
attributes:
Sample
MIME
1.
2. VerifyRate:
Type:
that
MTAS 16000
AMR-WB
VoWiFi
normalizes user can initiate
theHeader:
B number voice call to 222 and AMR-WB codec.
Verify
a)
Sample P-Access-Network-Info
Message
Rate:initial
16000 INVITE coming from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that To be Completed
Protocol:
3. Verify
Media SIP/SDP.
that
Attributefor the
(a): B number
rtpmap:97
rtpmap:104 the codec
AMR-NB/8000
AMR negotiated
/16000/1 in AMR-WB
SDP
4. contains
Verify that the
RTP following
is
(a): attributes:
established
rtpmap:104 both
AMR ways and
/16000/1 voice quality is good.
Media
MIME
1.
2. Attribute
Type:
Verify that
MTAS AMR-WB
VoLTEFieldname:
normalizesuser can rtpmap
the initiate
B numbervoice callparty
to #250 and AMR-WB codec.
5. Verfy
Verify
a)
MIME
Media
Sample the
Type: call
initial
Format:
Rate: is
AMR-WB
97
16000 released
P-Access-Network-Info
Message INVITE properly
Header:
comingthe from by either
access-type:
SBGnegotiated 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that
Protocol:
3. SAPC
6. Verify
Media SIP/SDP.
that
Attribute
Policy for
has the
(a): B number
rtpmap:104
correct Charging AMRcodec
Rule/16000/1
Install of Audioin AMR-WB
Rules in Gx-RAR To be Completed
SDP
MIME
Mediacontains
Sample Rate:
Type: the
16000
AMR-NB
Attribute following
(a): attributes:
rtpmap:104 AMR /16000/1
MIME
towards
1.
2. Type:
Verify EPG,
that
MTAS AMR-WB
after
VoLTE receiving
normalizesuser cantheRx-AAR
initiate
B numberfrom
voice P-CSCF
call to #611 and AMR-WB codec.
Sample
Verify
a)
MIME
Sample Rate:
Message
Type:
Rate: 8000
P-Access-Network-Info
initial
AMR-WB
16000 INVITE coming Header:
from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that
Protocol:
3.
4. Verify
Media
Verify SIP/SDP.
that
Attribute
that for
RTP the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec negotiated
/16000/1
ways and voice in AMR-WB
quality is good. To be Completed
SDP
Mediacontains
Sample Rate: the
Attribute16000 following
(a): attributes:
rtpmap:104 AMR /16000/1
MIME
1.
2. VerfyType:
5. Verify the
that
MTAS AMR-WB
call
ENUMis released
VoLTE
normalizesrequest
user canproperly
theis executed
initiate
B numberby either
voiceby callparty
S-CSCF.
to #7623 and AMR-WB codec.
Verify
a)
MIME
Sample
6. SAPCP-Access-Network-Info
Message
Type:
Rate:initial
Policy AMR-WB
16000
has INVITE
correct coming Header:
Charging from
Rule access-type:
SBGInstall of 3GPP-E-UTRAN-FDD
to originating
Audio S-CSCF.
Rules in Verify that
Gx-RAR
Protocol:
3.
4. Verify
Media
Verify DNS
SIP/SDP.
that
Attribute
that for
RTP the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec negotiated
/16000/1
ways and voice in AMR-WB
quality is good. To be Completed
SDP contains
Sample
towards Rate:
EPG,
xxx1.e164.arpa:
Media Attributethe
16000
afterfollowing
type
(a): receiving
NAPTR, attributes:
rtpmap:104 Rx-AAR
class IN
AMR from P-CSCF
/16000/1
MIME
1.
2. VerfyType:
5. Verify the
that
MTAS AMR-WB
call is released
VoLTE
normalizesuser can properly
the initiate
B numberby either
voice callparty
to *1067 and AMR-WB codec.
Verify
and
a)
MIME
Sample
6. SAPCP-Access-Network-Info
response
Message
Type:
Rate:
Policy received
initial
AMR-WB
16000
has INVITE
correct No Header:
is:coming such
Charging name
from
Rule access-type:
SBGInstall of 3GPP-E-UTRAN-FDD
to originating
Audio S-CSCF.
Rules in Verify that
Gx-RAR To be Completed
Protocol:
3.
4. Verify
Media SIP/SDP.
that
Attribute
Verify that for
RTP the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec negotiated
/16000/1
ways and in AMR-WB
6.
SDPVerify
Sample
towards
Media that the
contains
Rate:
EPG,
Attribute16000
after call break attributes:
following
(a): receiving out
rtpmap:104 and
Rx-AARAMR the
fromINVITE
P-CSCF
/16000/1 is sent to the is
voice quality good.
MGCF based on
MIME
5.
1.
2. VerfyType:
Verify
External the
that
MTAS AMR-WB
call is Selection
VoLTE
Network released
normalizesuser can properly
the initiate
B number
settings by either
voice callparty
to *225 and AMR-WB codec.
Verify
a)
MIME
Sample
6. SAPCP-Access-Network-Info
Message
Type:
Rate:initial
Policy AMR-WB
16000
has INVITE coming Header:
from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that
Protocol:
3.
7. Verify
Media
4.
SDP
SIP/SDP.
that
Attribute
contains
Sample Rate:
for
call
RTP
the
16000 isiscorrect
the
(a): Charging
B number
completed
rtpmap:104
established
following
the Rule
codec
successfully
AMR
both
attributes:
Install
and of
negotiated
/16000/1
ways and Audio
audio
voice in Rules
AMR-WB
path
quality in Gx-RAR
isisestablished
good. To be Completed
towards
Media
between
MIME
5. Verify EPG,
Attribute
UE
VerfyType:
the A after
and
AMR-WB
call (a): receiving
rtpmap:104
PSTN
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS normalizes
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
a) Message
MIME
Sample
6. SAPC thatinitial
Type:
Rate:
Policy AMR-WB
16000
has INVITE
correct coming
Charging from
RuleSBG to originating
Install S-CSCF. Verify that
3.
4.
SDP
Verify
Media Attribute
contains
Sample Rate:
for
RTP
the
16000
the
(a):
is B number
rtpmap:104
established
following
the
AMR
both
attributes:
codec and of
negotiated
/16000/1
ways Audio
voice Rules
quality is in
in AMR-WB Gx-RAR
good. To be Completed
towards
Media
MIME EPG,
Attribute
VerfyType:
5. Verify the after
AMR-WB
call (a): receiving
rtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS normalizes
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
MIME
Sample
6. SAPCType:
Rate:
Policy AMR-WB
16000
has correct Charging Rule Install
3.
4. Verify
Media
Verify
Sample
that
Attribute
that
Rate:
for
RTP
16000
the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec and of
negotiated
/16000/1
ways Audio
voice Rules
quality is in
in AMR-WB Gx-RAR
good. To be Completed
towards
Media
MIME EPG,
Attribute
VerfyType:
5. Verify the after
AMR-WB
call (a): receiving
rtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS normalizes
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
MIME
Sample
6. SAPCType:
Rate:
Policy AMR-WB
16000
hasthe correct Charging Rule Install
3.
4. Verify
Verify
Sample
that
that
Rate:
for
RTP
16000 is B number
established the
bothcodec
ways and of
negotiated Audio
voice Rulesis in
in AMR-WB
quality Gx-RAR
good. To be Completed
towards
Media
5. Verify EPG,
Attribute
Verfy the after
(a): receiving
callnormalizesrtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
MIME
6. SAPCType:
Policy AMR-WB
hasthe correct Charging Rule Install
3.
4. Verify
Verify
Sample
that
that
Rate:
for
RTP
16000 is B number
established the
bothcodec
ways and of
negotiated Audio
voice Rulesis in
in AMR-WB
quality Gx-RAR
good. To be Completed
towards
Media
5. Verify EPG,
Attribute
Verfy the after
(a): receiving
callnormalizesrtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2. MTAS B number
MIME
6. SAPCType:
thatAMR-WB
Policy hasthe correct Charging Rule Install
3.
4. Verify
Sample Rate:
for
RTP
16000 is B number
established the
bothcodec
ways and of
negotiated Audio
voice Rules
quality
Date: is in
in AMR-WB Gx-RAR
good.
2018-02-09
towards
Media EPG,
Attribute
5. Verfy the call after
(a): receiving
rtpmap:104
is released Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party VoLTE-VoWiFi E2E Site1
Prepared: LMIESN Edmund Sheridan Sheet: _x000D_Rev: PA1
MIME
6. SAPCType:
Policy AMR-WB
hasiscorrect Charging Rule Install of Audio Rules
4. Verify
Sample that
Rate: RTP
16000 established both ways and voice quality
Ericsson is in Gx-RAR
good.
Internal
towards EPG, after receiving Rx-AAR from
5. Verfy the call is released properly by either party P-CSCF
6. SAPC Policy has correct Charging Rule Install of Audio Rules in Gx-RAR
SDP contains the following attributes:
1. Verify that VoLTE user can initiate voice call to *646 and AMR-WB codec.
a) Message
Protocol: initial INVITE coming from SBG to originating S-CSCF. Verify that
SIP/SDP.
Media Attribute
SDP contains the(a): rtpmap:104
following AMR /16000/1
attributes:
MIME Type:
1. Verify thatAMR-WB
VoLTE TEST user canOBJECT
initiate voice _x000D_VoLTE/VoWiFi
LISTcall to *7627 and AMR-WB codec. Test Object List 17 (402)
a) Message
Sample
Protocol: Rate: initial
16000
SIP/SDP. INVITE coming from SBG to originating S-CSCF. Verify that
Media
SDP Attribute
contains the (a): rtpmap:104
following AMR
attributes: /16000/1
1. Verify
MIME thatAMR-WB
Type: VoLTE user can initiate voice call to 9704672222 and AMR-WB
Verify
codec.
a)
Sample P-Access-Network-Info
MessageRate: initial
16000 INVITE comingHeader:
from SBGaccess-type: 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that To be Completed
Media
Protocol:Attribute
SDP contains the(a):
SIP/SDP. rtpmap:104
following AMR /16000/1
attributes:
MIME
1.
2. Type:
Verify that
MTAS AMR-WB
VoLTE
normalizesuser can theinitiate
B numbervoice call to 0 and AMR-WB codec.
Verify
Sample P-Access-Network-Info
Rate: 16000 Header: access-type: 3GPP-E-UTRAN-FDD To be Completed
Protocol:
3.
a) Verify
Message
Media SIP/SDP.
that for
initial
Attribute the
INVITE
(a): B number
comingthe
rtpmap:104 codec
from
AMR SBGnegotiated in AMR-WB
to originating
/16000/1 S-CSCF. Verify that
Media
SDP
MIME
1.
2. Attribute
contains
Type:
Verify that
MTAS the
AMR-WB
VoLTE(a):
normalizesrtpmap:104
following
user can
the AMRvoice
attributes:
initiate
B number /16000/1
call to 00 and AMR-WB codec.
Verify
a)
MIME
Sample P-Access-Network-Info
Message
Type:
Rate: initial
AMR-WB
16000 INVITE comingHeader:
from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that To be Completed
Protocol:
3. Verify SIP/SDP.
that for the B number the codec negotiated in AMR-WB
SDP
Sample
Media
Media contains
Rate: the
Attribute
Attribute 16000 following
(a):
(a): rtpmap:104
rtpmap:104attributes:
AMR
AMR /16000/1
/16000/1
2. Verify
MIME
Verify MTAS
Type: normalizes
AMR-WB
P-Access-Network-Info theHeader:
B number access-type: 3GPP-E-UTRAN-FDD
a)
3. Message
MIME Type:
Verify thatinitial
AMR-WB
for INVITE
the B coming
number from
the SBG
codec to originating
negotiated S-CSCF. Verify that
in AMR-WB To be Completed
Media
4. Verify
Sample
SDP
Sample Attribute
that the
Rate:
contains
Rate: RTP
16000
16000(a): rtpmap:104
is established
following AMRways
both
attributes: /16000/1
and voice quality is good.
Media
MIME
5.
2. Verfy
VerifyAttribute
Type:
the
MTAS AMR-WB
call is(a): rtpmap:104
released
normalizes AMRby/16000/1
properly
the B number either party
MIME
Sample
6. SAPC Type:
Rate:
PolicyAMR-WB
16000
has
Verify
3.
Media
4. Verify
Sample Attribute
Rate: RTP
16000 iscorrect
P-Access-Network-Info
Verify that
that for the
(a): Charging
B number
rtpmap:104
established Header:
the
AMR
bothRule
codec
waysInstall
and of
access-type:
negotiated
/16000/1 Audio
voice Rules
in AMR-WB
quality is in
3GPP-E-UTRAN-FDDGx-RAR
good. To be Completed
towards
Media
MIME EPG,
Attribute
5. VerfyType: after
AMR-WB
the call is(a): receiving
rtpmap:104
released Rx-AAR
AMRby
properly from P-CSCF
/16000/1
either party
Verify
2.
MIME
Sample
6. SAPC P-Access-Network-Info
Verify MTAS
Type:
Rate:
Policy normalizes
AMR-WB
16000
has theHeader:
B number access-type: 3GPP-E-UTRAN-FDD
4.
3. Verify that
that RTP
VerifyRate:
Sample for
16000 iscorrect
the
Charging
established
B number both
the
Rule
ways
codec
Install
and of Audio
voice
negotiated
Rules
quality
in AMR-WBis in Gx-RAR
good. To be Completed
towards
5. Verfy EPG,
the after
call is receiving
released Rx-AAR
properly from
by P-CSCF
either party
2. Verify
Media
Verify MTAS normalizes
Attribute (a): rtpmap:104
P-Access-Network-Info theHeader:
B number
AMR /16000/1
access-type: 3GPP-E-UTRAN-FDD
6.
3. SAPC
4. Verify
MIME Policy
that
Type:
Verify hasthe
for
thatAMR-WB
RTP iscorrect Charging
B number
established the
bothRule
codec
waysInstall
and of
negotiatedAudio
voice Rules
in AMR-WB
quality is in Gx-RAR
good. To be Completed
towards
Media
Sample
5. Verfy EPG,
Attribute
Rate:
the after
16000
call (a):
is receiving
rtpmap:104
released Rx-AAR
AMR
properly from
by P-CSCF
/16000/1
either party
2. Verify MTAS normalizes the B number
MIME
1.
3. the Type:
6. Verify
SAPC thatAMR-WB
VoLTE
Policy UE-A
hasthe
for sends
correct sos when
Charging
B number dialing 911 of Audio
Rule Install
the codec negotiated Rules in Gx-RAR
in AMR-WB
Sample
4.
2. Verify
the
towards Rate:
MME/EPG
EPG,
Media Attribute 16000
that RTPafter isreceiving
established
should
(a): both
haveRx-AAR
rtpmap:104 the ways
sosfrom
AMR APN and voice quality
configured
P-CSCF
/16000/1 and soisthe
good.
SOS SIP call
5. VerfyType:
continues
MIME thetocall
theisPCSCF,
AMR-WB released properly
ECSCF, GMLCby(LRF),
eitherECSCF,
party MGCF, Metaswitch, and
4.
6. Verify
SAPC thatUE-A
Policy RTP iscorrect
hassends established
ChargingbothRule
ways and ofvoice quality is in
good. To be Completed
PSAP.
1. the VoLTE
Sample Rate: 16000 sos when dialing 911Install Audio Rules Gx-RAR
5.
3.
2. Verfy
towards the
EPG,call
theMME/EPG
the location is the
after
of released
should receiving
UE
have properly
Rx-AAR
is the
determined
sos APNby
fromeither party
viaP-CSCF
the:
configured Dia-LRR/LRA,
and so the SOSDia-PLR/PLA,
SIP call continues
6.
to
andSAPC
4. the Policy
PCSCF,
lcsap/lpp/lppa
Verify hasiscorrect
thatECSCF,
RTP GMLC Charging
(LRF),
messages.
established bothRule
ECSCF, MGCF,
waysInstall of Audio
Metaswitch,
and voice Rules
and
quality is in
PSAP. Gx-RAR
good. To be Completed
1.
3. the
the VoLTE
towards EPG,UE-A
location after
of thesendsUE issos
receiving when dialing
Rx-AAR
determined 911
from
via the:P-CSCF
Dia-LRR/LRA, Dia-PLR/PLA, and
5.
2. Verfy the
the MME/EPG
lcsap/lpp/lppa
call is released properly by either party
should have the sos APN configured and so the SOS SIP call continues
messages.
6. the
to SAPC Policy
PCSCF, has correct
ECSCF, GMLC (LRF),Charging
ECSCF,Rule
MGCF,Install of Audioand
Metaswitch, Rules
PSAP.in Gx-RAR To be Completed
1.
3. the
towardsVoLTE
EPG,
the location UE-A
after
of thesends sos
receiving
UE is when dialing
Rx-AAR
determined 911
from
via the:P-CSCF
Dia-LRR/LRA, Dia-PLR/PLA, and
1. VoWiFi dials
2. the MME/EPG 911
should have the sos APN configured and so the SOS SIP call continues
lcsap/lpp/lppa messages.
2. the
to UE attaches
PCSCF, ECSCF, to the GMLCsos (LRF),
APN via the MGCF,
ECSCF, WMG Metaswitch,
and EPG and PSAP. To be Completed
3.
1. UE
the sends
location
VoWiFi INVITE
dials the w/
of911 UE urn:service:sos
is determined viato the
the: PCSCF
Dia-LRR/LRA, Dia-PLR/PLA, and
lcsap/lpp/lppa
4. the call is messages.
routed to the ECSCF then MGCF
2. UE attaches to the sos APN via the WMG and EPG To be Completed
5.
3. Verify
UE sends callINVITE
is successful and Phase 1 to
w/ urn:service:sos andthe2 information
PCSCF from the 911
dispatch person
4. the call is routed to the ECSCF then MGCF
6. To be Completed
5. Verify
Verify SAPC
call is Policy
successful for correct
and PhaseRules1 &andQoS Values for SOS
2 information apn
from thein911
Gx-RAR
7. Verify charging
dispatch person from ECSCF after call ends
6. Verify SAPC Policy for correct Rules & QoS Values for SOS apn in Gx-RAR
7. Verify charging from ECSCF after call ends
1. Call gets successfully connected.
2. Subscriber doesn't get charged (Billing confirmation). To be Completed
1. Call gets successfully connected.
2. Subscriber doesn't get charged (Billing confirmation). To be Completed

1. VoLTE UE-A dials it's own number


2. MTAS changes the R-URI to the VM number
3. The call breaks out to CS via the MGCF To be Completed
1.
4. VoLTE
The callUE-A dials the
between UE-AVM digits
and VM is established
2.
5. The callDTMF
VoLTE breaks out to
tones CS via thenavigates
successfully MGCF the VM online menu To be Completed
3.
1. The callUE-A
VoLTE between
in 3G UE-A
dials and VM digits
the VM is established
4.
2. VoLTE
The callDTMF
breakstones successfully
out to CS via thenavigates
MGCF the VM online menu To be Completed
3.
1. VoLTE UE-A dials the VM digits established
The call between UE-A and VM is
4.
2. DTMF
The calltones successfully
breaks out to CS navigates the VM online menu
via the MGCF To be Completed
3. The call between UE-A and VM is established
4. VoLTE DTMF tones successfully navigates the VM online menu

Pass 0

Conditional Pass 0

Failed 0

Not Applicable 0

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 18 (402)

To be Completed 119

blocked 0

Total Test cases 119

wifi 31

3G 12

AAT 65

VNC 0

manual 0

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 19 (402)

Bluesky Witness Ericsson Test Date


Witness

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 20 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 21 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 22 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 23 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 24 (402)

total 0

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 25 (402)

Comments wifi 3G AAT

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 26 (402)

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 27 (402)

x x

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 28 (402)

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 29 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 30 (402)

VNC manual

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 31 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 32 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 33 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 34 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site1 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 35 (402)

Test Case Inform


TOL Ref. Test Object Name / Priority
Level Description / Objective
TC Ref. Test Case Title (P1/P2)
TO-E2E-01 IMS Registration/ Re-Registration/ Deregistration

TC-SITE2-E2E-01.01 VoLTE IMS Registration P1 VoLTE IMS Registration

TC-SITE2-E2E-01.02 VoLTE User Re-registration P1 VoLTE User Re-registration

TC-SITE2-E2E-01.03 VoLTE User De-registration P1 VoLTE User De-registration

TC-SITE2-E2E-01.04 VoWiFi IMS Registration - Trusted P1 VoWiFi IMS Registration

TC-SITE2-E2E-01.05 VoWiFi User Re-registration - Trusted P1 VoWiFi User Re-registration

TC-SITE2-E2E-01.06 VoWiFi User De-registration - Trusted P1 VoWiFi User De-registration

Network initiated De-registration - Administrative Network initiated De-registration -


TC-SITE2-E2E-01.07 (HSS) P1 Administrative (HSS)
Network initiated De-registration - Administrative Network initiated De-registration -
TC-SITE2-E2E-01.08 P1
(S-CSCF) Administrative (S-CSCF)

TC-SITE2-E2E-01.09 Network initiated De-registration - Registration P1 Network initiated De-registration -


Timeout (S-CSCF) Registration Timeout (S-CSCF)

TC-SITE2-E2E-01.10 VoWiFi IMS Registration - Untrusted P1 VoWiFi IMS Registration

TC-SITE2-E2E-01.11 VoWiFi User Re-registration - Untrusted P1 VoWiFi User Re-registration

TC-SITE2-E2E-01.12 VoWiFi User De-registration - Untrusted P1 VoWiFi User De-registration

TO-E2E-02 Call Setup

TC-SITE2-E2E-02.01 Voice call from VoWiFi to VoWiFi - Trusted P1 Call Setup - IMS-WiFi to IMS-WiFi

TC-SITE2-E2E-02.02 Voice call from VoWiFi to VoWiFi - Untrusted P1 Call Setup - IMS-WiFi to IMS-WiFi
Successful calls for following cases:
TC-SITE2-E2E-02.03 Voice call from VoLTE to VoLTE P1 1) without any data session
2) with data session
TC-SITE2-E2E-02.04 Voice call from VoWiFi Trusted to VoLTE P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE2-E2E-02.05 Voice call from VoLTE to VoWiFi Trusted P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE2-E2E-02.06 Voice call from VoWiFi Untrusted to VoLTE P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE2-E2E-02.07 Voice call from VoLTE to VoWiFi Untrusted P1 Call Setup - IMS-LTE to IMS-LTE

TC-SITE2-E2E-02.08 Voice call from VoWiFi to PLMN(other operator) via P2 IMS-LTE to PSTN customers
nSBG
Voice call from VoLTE to PLMN(other operator) via
TC-SITE2-E2E-02.09 P2 IMS-LTE to PLMN(other operator)
nSBG

TC-SITE2-E2E-02.10 Voice call from IMS-in-3G to PLMN P1 IMS-IN-3G to PLMN

TC-SITE2-E2E-02.11 Voice call from IMS-in-3G to IMS-in-3G - T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 36 (402)

TC-SITE2-E2E-02.12 Voice call from PSTN/PLMN to IMS-in-3G T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

TC-SITE2-E2E-02.13 Voice call from VoWiFi to IMS-in-3G - T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

TC-SITE2-E2E-02.14 Voice call from VoLTE to IMS-in-3G - T-ADS P1 IMS-IN-3G to IMS-IN-3G - T-ADS

TC-SITE2-E2E-02.15 Voice call from IMS-in-3G to VoWiFi - T-SDS P1 IMS-IN-3G to IMS-LTE -T-SDS

TC-SITE2-E2E-02.16 Voice call from IMS-in-3G to VoLTE - T-SDS P1 IMS-IN-3G to IMS-LTE -T-SDS

TC-SITE2-E2E-02.17 Voice call from PSTN/PLMN to VoWiFi - T-SDS P1 PSTN to IMS-LTE - T-SDS

TC-SITE2-E2E-02.18 Voice call from PSTN/PLMN to VoLTE - T-SDS P1 PSTN to IMS-LTE - T-SDS

Voice call from PLMN (other operator) to VoWiFi -


TC-SITE2-E2E-02.19 P2 PLMN (other operator) to IMS-LTE - T-SDS
T-SDS
Voice call from PLMN (other operator) to VoLTE - T-
TC-SITE2-E2E-02.20 P2 PLMN (other operator) to IMS-LTE - T-SDS
SDS
user A cancels the call after ringing (VoLTE to
TC-SITE2-E2E-02.21 Voice call from VoLTE to VoLTE P2
VoLTE) Call clears
user A cancels the call before ringing (VoLTE
TC-SITE2-E2E-02.22 Voice call from VoLTE to VoLTE P2 to VoLTE) Call clears

TO-E2E-03 VoLTE Supplementary Services

TC-SITE2-E2E-03.01 Originating Identification Presentation - OIP P1 Originating Identification Presentation - OIP

TC-SITE2-E2E-03.02 Originating Identification Restriction - OIR P1 Originating Identification Restriction - OIR

Communication Diversion Unconditional - CDIV- Communication Diversion Unconditional -


TC-SITE2-E2E-03.03 P1
CFU CDIV-CFU

TC-SITE2-E2E-03.04 Communication Diversion on Busy - CDIV-CFB P1 Communication Diversion on Busy - CDIV-CFB

Communication Diversion on not Reachable - CDIV- Communication Diversion on not Reachable -


TC-SITE2-E2E-03.05 P1
CFNRc CDIV-CFNRc
Communication Diversion on No Reply - CDIV-
TC-SITE2-E2E-03.06 Communication Diversion on No Reply - CDIV-CFNR P1 CFNR
Barring of All Incoming Calls - ICB
TC-SITE2-E2E-03.07 Barring of All Incoming Calls - ICB P1
(Announcement)

TC-SITE2-E2E-03.08 Barring of All Outgoing Calls - OCB P1 Barring of All Outgoing Calls - OCB
(Announcement)

TC-SITE2-E2E-03.08 Barring of All Outgoing Calls - - hotline P1 Barring of All Outgoing Calls -(hotline)

Barring of Outgoing International Calls - OCB


TC-SITE2-E2E-03.09 Barring of Outgoing International Calls - OCB P1 (Announcement)

TC-SITE2-E2E-03.10 Communication HOLD - Resume P1 Communication HOLD - Resume

TC-SITE2-E2E-03.11 Communication Waiting - Comm. Waiting P1 Communication Waiting - Comm. Waiting

TC-SITE2-E2E-03.12 Ad-Hoc Multi Party Conference - CONF P1 Ad-Hoc Multi Party Conference - CONF

TO-E2E-04 VoWiFi Supplementary Services

TC-SITE2-E2E-04.01 Originating Identification Presentation - OIP P1 Originating Identification Presentation - OIP

TC-SITE2-E2E-04.02 Originating Identification Restriction - OIR P1 Originating Identification Restriction - OIR

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 37 (402)

Communication Diversion Unconditional - CDIV- Communication Diversion Unconditional -


TC-SITE2-E2E-04.03 P1
CFU CDIV-CFU

TC-SITE2-E2E-04.04 Communication Diversion on Busy - CDIV-CFB P1 Communication Diversion on Busy - CDIV-CFB

Communication Diversion on No Reply - CDIV-


TC-SITE2-E2E-04.05 Communication Diversion on No Reply - CDIV-CFNR P1
CFNR

TC-SITE2-E2E-04.06 Barring of All Incoming Calls - ICB P1 Barring of All Incoming Calls - ICB
(Announcement)
Barring of All Outgoing Calls - OCB
TC-SITE2-E2E-04.07 Barring of All Outgoing Calls - OCB P1
(Announcement)
Barring of Outgoing International Calls - OCB
TC-SITE2-E2E-04.08 Barring of Outgoing International Calls - OCB P1 (Announcement)

TC-SITE2-E2E-04.09 Communication HOLD - Resume P1 Communication HOLD - Resume

TC-SITE2-E2E-04.10 Communication Waiting - Comm. Waiting P1 Communication Waiting - Comm. Waiting

TC-SITE2-E2E-04.11 Ad-Hoc Multi Party Conference - CONF P1 Ad-Hoc Multi Party Conference - CONF

TO-E2E-05 VoLTE-VoWiFi Call Forwarding Cases

CFU - VoLTE-A, VoWiFi-B. B has forwarded to


TC-SITE2-E2E-05.01 CFU - VoLTE-A, VoWiFi-B. PSTN (SIP-NNI) - C P1 PSTN (SIP-NNI) - C
CFU - VoWiFi-A, VoLTE-B. B has forwarded to
TC-SITE2-E2E-05.02 CFU - VoWiFi-A, VoLTE-B. PSTN (SIP-NNI) - C P1
PSTN (SIP-NNI) - C

TC-SITE2-E2E-05.03 CFU - PSTN-A, VoLTE-B, VoWiFi-C P1 CFU - Term Call from PSTN (A) to VoLTE-B, B
has forwarded to VoWiFi-C
CFU - Term Call from PSTN (A) to VoWiFi-B, B
TC-SITE2-E2E-05.04 CFU - PSTN-A, VoWiFi-B, VoLTE-C P1
has forwarded to VoLTE-C
CFU - VoLTE-A, VoWiFi-B. B has forwarded to
TC-SITE2-E2E-05.05 CFU - VoLTE-A, VoWiFi-B. VoLTE - C P1
VoLTE - C

TC-SITE2-E2E-05.06 CFU - VoWiFi-A, VoLTE-B. VoWiFi-C P1 CFU - VoWiFi-A, VoLTE-B. B has forwarded to
VoWiFi-C
CFU - VoLTE-A, VoLTE-B. B has forwarded to
TC-SITE2-E2E-05.07 CFU - VoLTE-A, VoLTE-B. 3G CS - C P1
3G CS - C
CFU - VoWiFi-A, VoLTE-B. B has forwarded to
TC-SITE2-E2E-05.08 CFU - VoWiFi-A, VoLTE-B. 3G CS - C P1 3G CS - C
CFU - VoLTE-A, VoWiFi-B. B has forwarded to
TC-SITE2-E2E-05.09 CFU - VoLTE-A, VoWiFi-B. 3G CS - C P1
3G CS - C

TC-SITE2-E2E-05.10 CFU - VoWiFi-A, VoWiFi-B. 3G CS - C P1 CFU - VoWiFi-A, VoWiFi-B. B has forwarded to


3G CS - C

TO-E2E-06 Ut-interface

Communication Diversion Unconditional -


TC-SITE2-E2E-06.01 IMS-WIFI UE, Using Ut, Enable CFU P1 Enable CDIV-CFU via IMS-WiFi
Communication Diversion Unconditional -
TC-SITE2-E2E-06.02 IMS-WIFI UE, Using Ut, Disable CFU P1 Disable CDIV-CFU via IMS-WiFi

TC-SITE2-E2E-06.03 IMS-WIFI UE, Using Ut, Interrogation CFU P1 Check status of CFU via WiFi

TC-SITE2-E2E-06.04 IMS-LTE UE, Using Ut, Enable CFU P1 Communication Diversion Unconditional -
Enable CDIV-CFU via IMS-LTE
Communication Diversion Unconditional -
TC-SITE2-E2E-06.05 IMS-LTE UE, Using Ut, Disable CFU P1
Disable CDIV-CFU via IMS-LTE

TC-SITE2-E2E-06.06 IMS-LTE UE, Using Ut,Interrogation CFU P1 Check status of CFU via IMS-LTE

TO-E2E-07 Handover

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 38 (402)

During VoLTE to VoLTE, Originator moves from LTE During VoLTE to VoLTE, Originator moves
TC-SITE2-E2E-07.01 P1
Access to WIFI Trusted from LTE Access to WIFI
During VoLTE to VoLTE, Terminator moves from During VoLTE to VoLTE, Terminator moves
TC-SITE2-E2E-07.02 LTE Access to WIFI Trusted P1 from LTE Access to WIFI
During VoWiFi to VoLTE, Originator moves from During VoWiFi to VoLTE, Originator moves
TC-SITE2-E2E-07.03 P1
WiFi Trsuted Access to LTE from WiFi Access to LTE

TC-SITE2-E2E-07.04 During VoWiFi to VoWiFi, Terminator moves from P1 During VoWiFi to VoWiFi, Terminator moves
WiFi Trusted Access to LTE from WiFi Access to LTE
During VoLTE to VoLTE, Originator moves from LTE During VoLTE to VoLTE, Originator moves
TC-SITE2-E2E-07.05 P1
Access to WIFI Untrusted from LTE Access to WIFI
During VoLTE to VoLTE, Terminator moves from During VoLTE to VoLTE, Terminator moves
TC-SITE2-E2E-07.06 LTE Access to WIFI Untrusted P1 from LTE Access to WIFI
During VoWiFi to VoLTE, Originator moves from During VoWiFi to VoLTE, Originator moves
TC-SITE2-E2E-07.07 WiFi Untrusted Access to LTE P1 from WiFi Access to LTE
During VoWiFi to VoWiFi, Terminator moves from During VoWiFi to VoWiFi, Terminator moves
TC-SITE2-E2E-07.08 P1
WiFi Untrusted Access to LTE from WiFi Access to LTE
During VoLTE to VoLTE, Originator performs During VoLTE to VoLTE, Originator
TC-SITE2-E2E-07.09
SRVCC P1 performs SRVCC

TC-SITE2-E2E-07.10
During VoLTE to VoLTE, Originator performs P1 During VoLTE to VoLTE, Originator
LTE To LTE handover performs LTE to LTE handover

During VoLTE to VoLTE, Terminator performs During VoLTE to VoLTE, Termintor


TC-SITE2-E2E-07.11
SRVCC P1 performs SRVCC
During VoLTE to PSTN, Originator performs During VoLTE to PSTN, Originator
TC-SITE2-E2E-07.12 P1
SRVCC performs SRVCC
During PSTN call VoLTE, Terminator performs During PSTN to Volte subscriber,
TC-SITE2-E2E-07.13
SRVCC P1 Terminator performs SRVCC
TO-E2E-08 MTAS Number analysis and Call routing (Short codes and long numbers to be updated as per Bluesky requirement)

TC-SITE2-E2E-08.01 IMS call 7-digit dialed number P1 Verify 7-digit dialed number from IMS
subscribers

TC-SITE2-E2E-08.02 IMS call to international number P1 Verify international calls from IMS subscribers

Verify 411 calls from IMS subscribers


TC-SITE2-E2E-08.03 VoLTE call to 411 P1 (18772465052)
Verify 411 calls from IMS subscribers
TC-SITE2-E2E-08.04 VoWifi call to 411 P1
(18772465052)

TC-SITE2-E2E-08.05 VoLTE call to 611 P1 Verify 611 calls from IMS subscribers
(19704673299)
Verify 611 calls from IMS subscribers
TC-SITE2-E2E-08.06 VoWifi call to 611 P1
(19704673299)
Verify 222 calls from IMS subscribers
TC-SITE2-E2E-08.07 VoLTE call to 222 P1
(19704673295)

TC-SITE2-E2E-08.08 VoWifi call to 222 P1 Verify 222 calls from IMS subscribers
(19704673295)
Verify #250 calls from IMS subscribers
TC-SITE2-E2E-08.09 VoLTE call to #250 P1
(8778724114)
Verify #611 calls from IMS subscribers
TC-SITE2-E2E-08.10 VoLTE call to #611 P1 (9704673299)

TC-SITE2-E2E-08.11 VoLTE call to #7623 P1 Verify #7623 calls from IMS subscribers
(8665196373)
Verify *1067 calls from IMS subscribers
TC-SITE2-E2E-08.12 VoLTE call to *1067 P1
(4023712129)
Verify *225 calls from IMS subscribers
TC-SITE2-E2E-08.13 VoLTE call to *225 P1
(9704670414)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 39 (402)

Verify *384 calls from IMS subscribers


TC-SITE2-E2E-08.14 VoLTE call to *384 P1
(3032394501)
Verify *611 calls from IMS subscribers
TC-SITE2-E2E-08.15 VoLTE call to *611 P1 (9704673299)
Verify *646 calls from IMS subscribers
TC-SITE2-E2E-08.16 VoLTE call to *646 P1
(9704673293)

TC-SITE2-E2E-08.17 VoLTE call to *7627 P1 Verify *7627 calls from IMS subscribers
(9704671116)
Verify 9704672222 calls from IMS subscribers
TC-SITE2-E2E-08.18 VoLTE call to 9704672222 P1
(9704673295)
Verify 0 calls from IMS subscribers
TC-SITE2-E2E-08.19 VoLTE call to 0 P1 (9704673299)
Verify 00 calls from IMS subscribers
TC-SITE2-E2E-08.20 VoLTE call to 00 P1 (9704673299)

TO-E2E-09 Emergency call

TC-SITE2-E2E-09.01 VoLTE Emergency 911 P1 Verify 911 call

TC-SITE2-E2E-09.02 VoLTE Emergency 911 (no SIM) P1 Verify 911 call

TC-SITE2-E2E-09.03 VoLTE Emergency 911(SIM/Roaming IN) P1 Verify 911 call

TC-SITE2-E2E-09.04 VoLTE Emergency 911(Suspended) P1 Verify 911 call

TC-SITE2-E2E-09.05 VoWiFi Emergency 911 Trusted P1 VoWiFi Emergency 911

TC-SITE2-E2E-09.06 VoWiFi Emergency 911 Untrusted P1 VoWiFi Emergency 911

TO-E2E-10 Toll-Free (0800 series)

TC-SITE2-E2E-10.01 VoLTE to 08xx series (800, 877 etc.) P1 Verify Toll-free calls

TC-SITE2-E2E-10.02 VoWiFi to 08xx series (800, 877 etc.) P1 Verify Toll-free calls

TO-E2E-11 Voice Mail

TC-SITE2-E2E-11.01 Voice mail deposit Voice mail deposit

TC-SITE2-E2E-11.01 Voice Mail Retrieval from IMS P1 Verify Voice Mail Retrieval from an IMS
subscriber in LTE

TC-SITE2-E2E-11.01 Voice Mail Retrieval from IMS-in-3G P1 Verify Voice Mail Retrieval from an IMS
subscriber in 3G

TC-SITE2-E2E-11.01 Visual Voicemail (if applicable) Verify Voice Mail Retrieval

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 40 (402)

E2E USE CASES vIMS TOL


Test Case Information
Steps

Assumptions:
Assumptions:
1. UE is provisioned for VoLTE
1.
2. UE
LTEisattach
provisioned for VoLTE
is working
2. LTE attach is working
Steps:
Steps:
1. Power up the UE in LTE Coverage where Voice over PS is
1. Power up the UE in LTE Coverage where VoPS Supported
Supported
Assumptions:
2. From the pcap, check the Expires value in the REGISTER and
1. UE ismessage
200OK VoLTE Registered
from the CSCF.
3. Wait until half the timer value has elasped.
Assumptions:
Assumption:
Steps:
4. From theenable
pcap, verify the UE sends another REGISTER to the
1. Power
1. UE is wifi
IMS core.Off the UE
Steps:
1. Power up the UE in Wifi Coverage.
Coverage
2. From the pcap, check the Expires value in the REGISTER and
Assumptions:
200OK
1. UE ismessage from the CSCF.
VoWifi Registered
3. Wait until half the timer value has elasped.
4. From the pcap, verify the UE sends another REGISTER to the
Steps:
Assumptions:
IMS
1. UEcore.
Power Off(LTE/WiFi)
is IMS the UE Registered
Steps:
Assumptions:
1. De-register the subscriber from HSS using command.
1. UE is IMS (LTE/WiFi) Registered
Steps:
2. UE subscription to RegEvents or the SBG subscribing to
1. De-register
RegEvents the subscriber
on behalf of UE. from S-CSCF using command.
Steps:
Assumptions:
Assumption:
1. Check the status of registration in S-CSCF.
1.
2. UE
Makeis wifi
the enable
registered UE not-reachable.
3. Wait until the Registration Timer expires.
Steps:
4. Check the status of registration in S-CSCF.
1. Power up the UE in Wifi Coverage.
Coverage
2. From the pcap, check the Expires value in the REGISTER and
Assumptions:
200OK
1. UE ismessage from the CSCF.
VoWifi Registered
3. Wait until half the timer value has elasped.
4. From the pcap, verify the UE sends another REGISTER to the
Steps:
UE-A
IMS
1. is a registered
core.
Power Off the UE VoWifi user, with no data session running.
UE-B isisaaregistered
UE-A registered VoWifi
VoLTEuser
user, with no data session
running.
UE-A is adials
registered VoWifi user, with no data session running.
1. UE-A
UE-B 10-digits to call UE-B
UE-A
UE-B isis
2. UE-A isaaahears
registered
registered
registered VoLTE
VoWiFi
VoWifi
ringback
user
toneuseruser, with no data session
running.
3. UE-B answers and 2-way voice is verified
1.
1. UE-A
UE-A
UE-B is dials
dials 10-digits
10-digits to to
callcall
UE-BUE-B
4.
2.
UE-A
UE-AUE-A
UE-A is aaends
registered
hears
hears
the
registeredcall VoLTE
ringback
ringback VoLTE tone
tone
user
user, with no data session
5. The call ends at UE-B
running.
3.
1. UE-B
UE-B
UE-A answers
answers
dials and
and
10-digits 2-way
2-way
to voicevoice is verified
is verified
calluser
UE-B
UE-B
4.
4. UE-A
UE-AUE-Ais
is aaends
registered
ends the
the
registeredcall
callVoWiFi
VoWiFi user, with no data session
2.
5. UE-A
The callhears
ends ringback tone
5.
3. The
running.
UE-B call endsatat
answers
UE-B
andUE-B 2-way voice is verified
1.
UE-BUE-Ais dials 10-digits to call UE-B
4.
UE-A
2. UE-A
UE-A
Repeat is aathe
registered
ends
hears the
registered callVoLTE
ringback
test, but VoLTE
this tone
user
user,
time UE-Awith no data
starts session
a data streaming
5. The
running.
3. UE-B call ends at
answers andUE-B 2-way voice is verified
session
1. UE-A (ie youtube).
dials 10-digits to call UE-B
UE-B
4. UE-Ais aends
registered
the callVoWiFi user
2. UE-Athe
Repeat hears ringback
test, but thistone
time UE-A starts a data streaming
5.
3. The
Verify
UE-B call
after ends at
the call
answers andUE-B
is 2-way
up, thevoice
data streaming is still
session
1. UE-A(ie
running.
youtube).
dials 10-digits to call UE-Bis verified
4.
2. UE-A
UE-Athe ends
hears the call
ringback
Repeat
5. The test, but thistone
time UE-A starts a data streaming
Verify
UE-A
3. UE-B acall
is after ends
VoLTEtheuser
answers at
call
andUE-B
is 2-way
up, thevoice
data isstreaming
verified is still
session
UE-B (ie
is a PSTN youtube).
running.
4. UE-A ends user
the call
Repeat
//
5. Block thetrunk
SIP
The call test,towards
ends but
at UE-Bthismetaswitch
time UE-A2&3 starts a data streaming
Verify
1. UE-Aafter
session calls
(ie the
UE-Bcall is up, the data streaming is still
youtube).
UE-A is ahears
running.
2. UE-A VoLTEringback
user.
Repeat
UE-B
3. the
is aanswers
UE-B test,the
external but this time UE-A starts a data streaming
subscriber.
Verify
session after
(ie the callcall
youtube). is up, the data streaming is still
4. Verify
UE-A 2-way audio
is a VoLTE user in 3G coverage.
running.
Action:
5. UE-A ends the call
UE-B
1. is adials
UE-A external
the subscriber.
User B.3G(ICS)
Verify
User
6. TheA –after
VoLTE
call theuser
ends atcallinis
UE-B up, thecoverage
data streaming is still
2. UE-B
User B
running. – answers
VoLTE the
user call.
in 3G(ICS) coverage.
Action:
1. UE-A dials the User B.
To verifyanswers
2. UE-B that a VoLTE UE outside VoLTE coverage can receive
the call.
voice calls from a 3G(ICS) user.
1. Make a call from User A to User B.
2. User B answers the call.
3. Verify the call establishment Date: 2018-02-09
4. Terminate the
Prepared: call fromEdmund
LMIESN either party.Sheridan _x000D_Rev: PA1
Sheet: VoLTE-VoWiFi E2E Site2
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 41 (402)
UE-A is a external subscriber.
UE-B is a VoLTE user in 3G coverage.
UE-A is a VoLTE subscriber.
Action:
UE-B
1. is adials
UE-A VoLTE user
theuser inB.3G coverage.
Userin
User A – VoLTE 3G(ICS) coverage
2. UE-B
User B –answers
VoLTE userthe in
call.
3G(ICS) coverage.
Action:
1. UE-A dials the User B.
To verifyanswers
2. UE-B that a VoLTE UE outside VoLTE coverage can receive
the call.
UE-A
voice is a VoLTE
calls from user in 3Guser.
a 3G(ICS) coverage.
UE-B
1. Make a call from User A in
is a VoLTE subscriber to WiFi
User coverage.
B.
2. User
UE-A is B VoLTE
a answers theincall.
user 3G coverage.
Action:
3. Verify the callsubscriber
establishment
UE-B
1. is adials
VoLTE in WiFi coverage.
4. UE-A
Terminate the
the User B. either
call from party.
2. UE-B
UE-A answers the call.
is a PSTN/external user in 3G coverage.
Action:
UE-B is adials
1. UE-A VoLTE
thesubscriber
User B. in WiFi coverage.
2. UE-B
UE-A answers the
is a PSTN/external call.user in 3G coverage.
Action:
UE-B
1. UE-A dials the User B. in WiFi coverage.
is a VoLTE subscriber
2. UE-B
UE-A is aanswers the call.user in 3G coverage.
PSTN/external
Action:
UE-B is adials
1. UE-A VoLTE
thesubscriber
User B. in WiFi coverage.
2. UE-B
UE-A answers the
is a PSTN/external call.user in 3G coverage.
Action:
UE-B
1. UE-A dials the User B. in WiFi coverage.
is a VoLTE subscriber
2. UE-B answers the call.
Action:
UE-A is a VoLTE user
1. UE-A
UE-B is adials theuser
VoLTE User B.
2. UE-B answers the call.
UE-A is ainitiate
1. UE-A VoLTE user
a call with UE-B.
UE-B is acancelled
2. UE-A VoLTE user the call before UE-B ring.
1. UE-A initiate a call with UE-B.
2. UE-A cancelled the call after UE-B ring.
User A is a VoLTE user
User B is a VoLTE user with OIP service activated.
User A is a VoLTE user with OIR service activated.
Action:
User B isA ainitiates
1. User VoLTE usera call to user B.
2. User
User A isB'sa VoLTE
UE ringuserand shows the number of Uesr A.
Action:
User
1. B isA ainitiates
User VoLTE usera callwith CFUB.
to user to PSTN (UE-C)
User A is a VoLTE user
2. User
User B isB'sa UE ringuser
VoLTE andwuth
doesn’t'
CFBshow the number of Uesr A.
to C enabled
Action:
User
1. C isA ainitiates
A
User VoLTE usera call to user B.
User B isanswers
2. UE-C a VoLTEthe user wuth CFNRc to C enabled
call
Action:
User C
A is PLMN
a VoLTE user
user
1. User
User B isA ainitiates
VoLTE usera callwuth
to user B. to C enabled
CFNR
2. User
C isB PLMN
Action:
User rejectsuser
the call
3. User A
1. C answers
initiates athecallcall.
to user B.
2. User B first register in IMS, then take out battery or loose
Action:
User
VoLTE,
1. A is
User A ainitiates
but VoLTE user
keep register
a call toinuser
IMS.B.(no paging to User B)
User B isB
2. User C aanswers
VoLTE answer
doesn't user with
the call. theBaring
call. all incoming calls
3. TheA call
User is a got VoLTEtransfer
user to User C after no answer from User B
Action:
timerBreached.
User
1. User isA adials
VoLTEthe user with
B Baring all outgoing calls
Usercall.
4. User C answers the
2.User
User AAis hears
a VoLTE barring
user announcement
Action:
User
1. B isB adials
User VoLTEthe user
UserwithA Holtline provisioned.
User A is a VoLTE user with service to enable or disable Call
2.UserisBa hears
Barring
UE-A barring announcement
Action: VoLTE user.
UE-B
1. is aB VoLTE
User dials theuser.
User A
Action:
2.User B is connected to the hotline number.
1. User
A isA aenables
Action:
User the International call barring service by dialing
VoLTE user
SSC
User digits
1. UE-A
B isdials
a PSTN the user
User B with SDP offer request.
User A
User
2. UE-B
User isAanswers
C is aadials
VoLTE
VoLTEanthe
international
usercall. number
User
3.User
3. BA
UE-A isholds
a VoLTE
hears barring
the call. announcement
User
4.
ToUE-AC isresume
verify asupplementary
VoLTEthe call. service of call waiting for a VoLTE UE
Make
5. UE-B
with sure
HD holds UsertheA’s
capability UE has been provisioned with the conference
call
factory
1. UE-B URI.
6. User Aresumes
makes an theaudio
call call to User C
To
7. verifyrelease
2. UE-A
Verify multi
the callparty
the audio conference speech call.
call.
establishment
1.
3. User
User A calls User
B calls User A B.
2.
4. User
User C A calls
doesUser A.
not answer the call from User B
3. User
User A isA aputs the call
VoWiFi useron hold and takes the call with User C.
4. Verify
User B is call establishment.
a VoWiFi user with OIP service activated.
5. After the call establishment hit the conference button.
User
6. A is a VoWiFi
Terminate
Action: user with OIR service activated.
the call.
User B isA ainitiates
1. User VoWiFi ausercall to user B.
2. User B's UE ring and shows the number of Uesr A.
Action:
1. User A initiates a call to user B.
2. User B's UE ring and doesn’t' show the number of Uesr A.
Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 42 (402)
User A is a VoWiFi user
User B is a VoWiFi user with CFU to UE-C
User A is VoWiFi user
User B is VoWiFi user wuth CFNA to C enabled
Action:
User C isA VoWiFi
A
1. User initiatesuser
a call to user B.
User B isanswers
2. UE-C VoWiFi the usercall
wuth CFNRc to C enabled
Action:
User C is PSTN
1. User A initiates a call to user B.
2. User
A isB adoPSTN
Action:
User not answer
user 3Gthe usercall until timeout.
2.
1. User
User B isAC aanswers
VoWiFi athe
initiates callcall.
user to user
with B. all incoming calls
Baring
2. User B first register in IMS, then take out battery or loose
VoLTE,
Action:
User A isbut keep register
a VoWiFi user within IMS.
with(no paging
Baring to User B)calls
all outgoing
2. User A
1. C answers
dials the the
Usercall.
B
2. User
Action:
UE-A A hears user.barring announcement
User
1. Ais isVoWiFi
User A VoWiFi
dials the user with Baring all outgoing international calls
UE-B is VoWiFi userUser B
2. User A hears barring announcement
Action:
Action:
User A isA adials
1. User VoLTEan user
international number
1. UE-A
User
2.UserBA isdials the
a VoLTE
hears User
userBannouncement
barring with SDP offer request.
User A
2. UE-B
User is a
C isanswersVoWiFi
a VoLTEthe call.
user
User
3. B isholds
UE-A a VoWiFi
the call.
User
4.
ToUE-AC isresume
verify asupplementary
VoWiFi the call. service of call waiting for a VoLTE UE
Make
5. UE-B
with HDsureholdsUsertheA’s
capability UE has been provisioned with the conference
call
factory
1. UE-B URI.
6. User Aresumes
makes an theaudio
call call to User C
To
7. verifyrelease
2. UE-A
Verify multi
the callparty
the audio conference speech call.
call.
establishment
1.
3. User
User A calls User
B calls User A B.
2.
4. User
User C A calls Userthe
received A. call from User B.
3. User
User A isA aputsVoLTEtheuser
call on hold and takes the call with User C.
4. Verify
User B is call establishment.
a VoWiFi user with CFU to UE-C (PSTN SIP NNI)
5. After the call establishment hit the conference button.
User
6. A is
Terminate
Action: a VoWiFi
the user
call.
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (PSTN SIP NNI)
2. UE-C
User A isanswers
a PSTN the
UE call
Action:
User
1. B isA ainitiates
User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a PSTN the
UE call
Action:
User B isA ainitiates
1. User VoWiFi ausercall with CFUB.to UE-C (VoLTE)
to user
2. UE-C
User A isanswers
a VoLTEthe usercall
Action:
User
1. B isA ainitiates
User VoWiFi ausercall with CFUB.to UE-C (VoLTE)
to user
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User
1. B isA ainitiates
User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C
User A isanswers
a VoWiFi the call
user
Action:
User B isA ainitiates
1. User VoLTE usera callwith CFUB.
to user to UE-C (VoWiFi)
2. UE-C answers the call
Action:
User
1. A isA any
User user a call to user B.
initiates
User B isanswers
2. UE-C a VoWiFi user
the callwith CFU to UE-C
User C is any user
User A is any user
User B is a VoWiFi user with CFU to UE-C
Action:
User C is any
1. Enable CFUuser
on User B's UE through Ut interface(menu)
2. User A initiates a call to user B.
Action:
User A isanswers
3. UE-C any userthe call
1.
4. Disable
User B
A is aany
Disable CFU on
on User
VoWiFi
CFU user user B's
User with
B's UE through
UECFU to UE-C
through Ut
Ut interface(menu)
interface(menu)
2. User
User C isA any
B ainitiates a callwith
useruser
VoLTE to user
CFUB.to UE-C
3. UE-B
User C isanswers
any userthe call
User A is any user
Action:
User B is CFU
1. Check
Action: a VoLTE userB's
on User withUECFU to UE-C
through Ut interface(menu)
User C is any
1. Enable CFUuser
on User B's UE through Ut interface(menu)
2. User A initiates a call to user B.
Action:
User A isanswers
3. UE-C any userthe call
1.
4. Disable
User B is aCFU
Disable VoLTE
CFU on User
on user B's
B's UE
Userwith through
CFU
UE to UE-CUt
through Ut interface(menu)
interface(menu)
2. User
User C isA anyinitiates
user a call to user B.
3. UE-B answers the call
Action:
1. Check CFU on User B's UE through Ut interface(menu)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 43 (402)
UE-A and B are VoWifi user coverage in LTE

1. UE-A and B established a call


UE-A and call
2. During B are VoWifi
UE-A turnuser coverage
off wifi access.in LTE
3. Call should be continue.
1. UE-A and B established a call
UE-A is a VoWifi
2. During user
call UE-B coverage
turn off wifi in Wifi
access.
3. Call should be continue.
1. UE-A
UE-A is aestablished
VoLTE useracoverage
call with anyuser using VoWifi
in LTE Only.
2. During
UE-A callbe
Should turn offenabled.
Wifi Wifi
3. Call should be continue.
1. UE-A
UE-A and established
B are VoWifia call
userwith anyuserinusing
coverage LTE VoLTE
2. During call move from LTE Coverage to Wifi Coverage.
3. UE-A
1. Call should
and B be continue.a call
established
UE-A and call
2. During B are VoWifi
UE-A turnuser coverage
off wifi access.in LTE
3. Call should be continue.
1. UE-A and B established a call
UE-A is a VoWifi
2. During user
call UE-B coverage
turn off wifi in Wifi
access.
3. Call should be continue.
1. UE-A
UE-A is aestablished
VoLTE useracoverage
call with anyuser using VoWifi
in LTE Only.
2. During
UE-A callbe
Should turn offenabled.
Wifi Wifi
3. Call should be continue.
UE-A and
1. UE-A B are VoLTE
established users
a call with anyuser using VoLTE
UE-A and call
2. During B are in a VoLTE
move callCoverage
from LTE with 2-way audioCoverage.
to Wifi verified
3. Call should be continue.
1. UE-A moves from LTE to 3G radio coverage (attenuate the LTE
signal)
UE-A is aattaches
2. UE-A VoLTE userto 3G and the call survives the handover
1. UE-A established a call with anyuser.
2. Move the UE-A using drive testing from one eNodeB Coverage
UE-A and BeNodeB
to another are VoLTE users under different EPC.
Coverage
UE-A and B are in a VoLTE call with 2-way audio verified
UE-A is VoLTE users
1. UE-B
UE-A moves afrom
establish LTEcall
VoLTE to 3G radiosubscriber
to PSTN coverage (attenuate
with 2-waythe LTE
audio
signal)
verified
UE-B is VoLTE
2. UE-B users
attaches to 3G and the call survives the handover
UE-B established
1. UE-A moves from a VoLTE
LTE tocall
3Gfrom
radioPSTN with 2-way
coverage audiothe LTE
(attenuate
verified
signal)
2. UE-A attaches to 3G and the call survives the handover
1. UE-Bismoves
UE-A from LTE
a registered to 3Guser
VoLTE radio coverage (attenuate the LTE
signal)
UE-B
uesky requirement) is a registered VoLTE user
2. UE-B attaches to 3G and the call survives the handover
UE-A is a VoLTE user
UE-B is adials
1. UE-A International
7-digits touser
call UE-B
2. UE-A hears ringback tone
1.
3. UE-A calls UE-Band 2-way voice is verified
UE-B answers
UE-A
2. is ahears
4. UE-A registered
ends callVoLTE user
ringback
the
3.
5. UE-B answers
The call the
ends at UE-Bcall
1.
4. UE-A
is adials
Verify
UE-A 2-way411audio
registered VoWiFi user
2.
5. UE-A hears ringback
ends the call tone
3.
6.
1. UE-B
The
UE-A answers
call ends
dials 411 and
at UE-B2-way voice is verified
UE-A
4. is aends
UE-A registered
the VoLTE user
call
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
611andVoWiFi
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
611andVoLTE
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
222andVoWiFi
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
222andVoLTE
2-way voice is verified
UE-A
4. is adials
UE-A registered
ends the call user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
#250
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
#611
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
#7623
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials
UE-A ends
*1067
registered
the callVoLTE user
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers
dials *225and 2-way voice is verified
4. UE-A ends the call tone
2. UE-A hears ringback
3. UE-B answers and 2-way voice is verified
4. UE-A ends the call Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 44 (402)
UE-A is a registered VoLTE user

1. UE-A
UE-A is adials *384 VoLTE user
registered
2. UE-A hears ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials *611
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials *646
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials *7627
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers and 2-way voice is verified
UE-A
4. is adials 9704672222
registered
callVoLTE user
2. UE-A
UE-A ends
hearsthe
ringback tone
3.
1. UE-B
UE-A answers
0 andVoLTE
2-way voice is verified
UE-A
4. is adials
registered user
2. UE-A
UE-A ends
hearsthe call tone
ringback
3.
1. UE-B
UE-A answers
dials 00 and 2-way voice is verified
4.
2. UE-A
UE-A ends
hearsthe call tone
ringback
3. UE-B answers and 2-way voice is verified
4. UE-A ends the call
1. VoLTE UE Dial 911 in LTE Coverage.
2. Call connect to PSAP IVR to choose options
1. VoLTE UE without sim card Dial 911 in LTE Coverage.
2. Call connect to PSAP IVR to choose options
1. VoLTE UE roaming in from other operator Dial 911 in LTE
Coverage.
2. Call connect to PSAP IVR to choose options
1. VoLTE UE with sunscription suspended Dial 911 in LTE
Coverage.
2. Call connect to PSAP IVR to choose options
1. VoWiFi UE Dial 911 in Wifi Coverage.
2. Call connect to PSAP IVR to choose options
1. VoWiFi UE Dial 911 in Wifi Coverage.
2. Call connect to PSAP IVR to choose options

1. UE Dial Tollfree number 08xx in LTE Coverage.


2. Call connect to the service.
3. Billing confirmation needed.
1. UE Dial Tollfree number 08xx in WiFi Coverage.
2. Call connect to the service.
3. Billing confirmation needed.

UE-A is a VoLTE user


1. UE-A
UE-A is adials
VoLTEOwn Number.
user
2. UE-A is able to navigate the IVR menus by using the
UE's
1. dial-pad
UE-A
UE-A is adials
VoLTEVoice
usermail retrieval number
in 3G
2. UE-A is able to navigate the IVR menus by using the
UE's
1. dial-pad
UE-A
UE-A is adials
VoLTEVoice
usermail retrieval number
2. UE-A is able to navigate the IVR menus by using the
UE's dial-pad
1. UE-A dials Voice mail retrieval number
2. UE-A is able to navigate the IVR menus by using the
UE's dial-pad

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 45 (402)

E2E USE CASES vIMS TOL


1. Verify that attach request message sequence contains:
a) Prior to communicating with IMS, the UE must establish IPSEC tunnel with EPG.
b) PDN connection to the ims APN via GTP tunnel. Acceptance Test
Pass/fail Criteria Procedure document Test Result
2. Verify that challenge response is sent from I-CSCF to the UE Status-Line: SIP/2.0 401 available
Unauthorized including:
Nonce Value: “…"
1.Cipher
Verify Key:
that attach
"…" request message sequence contains:
Integrity Key: "…"
a) PriorUEto attaches
communicating withregisters
IMS, thetoUE must establish IPSEC tunnel withIMSWMG. To be Completed
1. The to LTE and IMS network connectivity via the APN,
3.
due Verify that Status-Line:
to VoLTE coverage and SIP/2.0
public200 OK isresolution
domain received from the I-CSCF when registration
1.
b) The
PDNUE terminates
connection
is complete.
2. Verify that registration to an
theIMSimsregistrations
200OK via GTPby
APNmessage performing
tunnel.
receives expirationde-registration.
timer Ex: REGISTER To be Completed
message sent by P-CSCF expires”
“sip.contact.parameter: to S-CSCFvalue with Contact header including expire parameter
equal
2.
3. Verify
4. The to
VerifyUE0that
should
that challenge
UE issubscribe
sendingresponse
to theisREGISTRATION
sent from
re-registration andI-CSCF
IMSevent to the
network UE
( P-CSCF Status-Line:
respondgenerates SIP/2.0
a OK 401
with 200
Unauthorized
SUBSCRIBE request including: forward it to the S-CSCF in the home network). To be Completed
Protocol:
Nonce Value:SIP/Register/Contact:
“…" sip:scscfxx.xx.xx.5060/Expires: 0
2. The
5.Cipher UEKey:
3rd party will perform a to
"…"
registration PDN thedisconnection
SCCAS and SIPprocedure port and disconnect from the IMS
APN To be Completed
Integrity
6. The UEKey:
1.MESSAGE "…"from
sent
attaches SCCAS
to LTE andto ATCF with
registers to IMSMSISDN
networkfor SRVCC
connectivity via the IMS APN,
due to VoLTE coverage and public domaine resolution
1.Verify
3.
2. The UEthat terminates
Status-Line:
registration an IMS
SIP/2.0
200OK registrations by
200 OK isreceives
message performing
received fromde-registration.
expiration the timer
I-CSCFEx:whenREGISTER
registration To be Completed
message
is complete. sent by P-CSCF expires”
“sip.contact.parameter: to S-CSCFvalue with Contact header including expire parameter
equal
3. to 0 UE is sending re-registration and IMS network respond with 200 OK
1.Verify
The UEthat terminates an IMS registrations by performing de-registration. REGISTER To be Completed
4. The UEsent
message should subscribe
by P-CSCF to the REGISTRATION
to S-CSCF withsequence
Contact headerevent including
( P-CSCF generates a
Protocol:
1. Verify
SUBSCRIBE SIP/Register/Contact:
that attach
request request
forward it to sip:scscfxx.xx.xx.5060/Expires:
message
the S-CSCF in contains:
the home 0 expire parameter
network).
equal
2. to 0will perform a PDN disconnection procedure and disconnect from the IMS
1.The
TheUE UE terminates an IMS registrations by performing de-registration. REGISTER To be Completed
APN
a)
5. Priorparty
3rd
message to communicating
by P-CSCF towith
registration the IMS,
SCCAS the
and UESIPmust
port establish IPSEC tunnel with WMG.
Protocol: sentSIP/Register/Contact: S-CSCF with Contact header
sip:scscfxx.xx.xx.5060/Expires: including 0 expire parameter
6. The
2. MESSAGE
equal to
UE 0willsentperform from aSCCAS PDN to ATCF with MSISDN
disconnection procedure for and
SRVCC disconnect from the IMS
b) PDN connection to the ims APN via GTP tunnel. To be Completed
APN
Protocol: SIP/Register/Contact: sip:scscfxx.xx.xx.5060/Expires: 0
2.
2. Verify
The UEthat willchallenge
perform aresponse is sent fromprocedure
PDN disconnection I-CSCF to and the UE Status-Line:
disconnect fromSIP/2.0
the IMS 401
1. The status ofincluding:
Unauthorized
APN the UE shows "not registered". To be Completed
Nonce Value: “…"
Cipher
check WMGKey: ue "…"trace.
To be Completed
Integrity
1.
1.Verify Key:
The UEthat "…" touser
VoWiFi
attaches LTE can
and initiate
registers voice
to IMScallnetwork
using 10-digit dialing via
connectivity andthe
AMR-WB
IMS APN,
codec.
due to VoLTE coverage and public domaine resolution
check
3. The WMG
1.Verify
Protocol:
2. UEthat ue
terminates
SIP/SDP. trace.an IMS
Status-Line:
registration SIP/2.0
200OK registrations by
200 OK isreceives
message performing
received fromde-registration.
expiration the timer
I-CSCFEx:whenREGISTER
registration To be Completed
1. Verify
message
is complete.
a) Message that
sent VoWiFi
by
initial
“sip.contact.parameter: P-CSCF
INVITE userexpires”
to can
S-CSCF
coming initiate
withvoice
from
value call
Contact
SBG to using
header
originating 10-digit
including
S-CSCF.dialing andthat
expire
Verify AMR-WB
parameter
SDP AMR-
1. Verify
codec.
equal
that
to 0that
VoLTE user can initiate voice call using 10-digit dialing and
contains
3.
WB Verify
codec.the following
UE is sending attributes:
re-registration and IMS network respond with 200 OK
Protocol:
4. The UE SIP/SDP.
should subscribe to the REGISTRATION event ( P-CSCF generates a To be Completed
Protocol:
a) Message
Protocol: SIP/SDP.
initial(a): INVITE
SIP/Register/Contact: coming fromS-CSCF
SBG toinoriginating S-CSCF. 0 Verify that SDP
SUBSCRIBE
Media request
Attribute forward
rtpmap:104 it tosip:scscfxx.xx.xx.5060/Expires:
the
AMR /16000/1 the home network).
contains
2. The Type:
check
MIME UE
WMGthe following
willAMR-WB
ue trace. attributes:
perform a PDN disconnection procedure and disconnect from the IMS
a)
APN
1. Message
5. Verify
3rd
Sample party
Rate: initial
thatregistration
VoWiFi
16000 INVITE
usertocan coming
the SCCASfrom
initiate voiceSIP
and SBG
call to originating
using
port S-CSCF.
10-digit dialing andVerify
AMR-WB that
1.
SDP Verify
Media
codec. that
contains
Attribute VoLTE
the(a): user
following
rtpmap:104 can initiate
attributes:
6. MESSAGE sent from SCCAS to ATCF with MSISDN for SRVCCAMR voice
/16000/1 call using 10-digit dialing and AMR-
WB
MIME codec.
Protocol:
Verify Type: AMR-WB
SIP/SDP.
P-Access-Network-Info Header: access-type:
1.Message
Verify
Protocol:
Sample
Media
a) that
Rate:
Attribute afterINVITE
SIP/SDP.
16000
initial P-CSCF
(a): receives
rtpmap:104
coming frominitial
AMRSBGINVITE,
/16000/1 theIEEE.802.11
to originating S-CSCF
S-CSCF.
(wlan) based on the
is selected
Verify that SDP
To be Completed
registration information stored in cache.
MIME
contains
2.
2. Verify
check
Ensure Type:
WMGMTAS
that ueAMR-WB
the following
normalizes
thetrace.access
attributes:
the for
type B number
the to +1 and
originating 10-digit
party is a VoWiFi.
Verify
a) P-Access-Network-Info
Message thatinitial INVITE Header:
coming access-type:
from SBG tothe IEEE.802.11
originating (wlan) based
S-CSCF. To be Completed
Sample
3.
1.Verify
1. Verify Rate:
that for16000
after
VoWiFi theP-CSCF
Buser
numberreceives
can the codec
initiate initial
voice negotiated
INVITE,
call using in AMR-WB
S-CSCF
10-digit isdialing andVerify
selected AMR-WB onthat
the
1.
SDP Verify
Media that
contains
Attribute
registration
codec. VoLTE
the
information user
(a):following
rtpmap:104
storedcan initiate
attributes:
inAMR
cache. voice call using 10-digit dialing and AMR-
/16000/1
In
2.
WB
MIMEinitial
Verify
codec.SIP
MTAS
Type: INVITEnormalizes
AMR-WB coming from
the B SBG
number to originating
to +1 and S-CSCF,
10-digit verify that the P-Access-
2. Ensure
Protocol:
Verify that
SIP/SDP. the access type forHeader:the originating party is a3GPP-E-UTRAN-FDD
VoLTE.
3. VerifyP-Access-Network-Info
Network-Info
Protocol:
Sample that
Rate: Header
for
SIP/SDP.
16000 the Bcontains
number the the known access-type:
access
codec negotiated typein“3GPP-E-UTRAN-FDD”.
AMR-WB To be Completed
Media
a)
3. Message
Verify
Media Attribute
initial
that VoLTE
Attribute (a):
INVITEuser
(a):coming rtpmap:104
coming
can originate
rtpmap:104 from AMRSBG /16000/1
to originating
HD voice call using AMR-WB
AMRto/16000/1 S-CSCF. Verify that SDP
codec.
In
MIME
2. initial
contains
Verify
Protocol: SIP
Type:
the INVITE
MTAS AMR-WB
following
SIP/SDP. normalizes from
attributes: the SBGB originating
number to +1 S-CSCF,
and verify that the P-Access-
10-digit
MIME
Verify
4. VerifyType: AMR-WB
P-Access-Network-Info
that initial
RTP is INVITE
established Header:
both access-type:
ways and voice IEEE.802.11
quality (wlan) Verify that
is good. To be Completed
a) Message
Network-Info
Sample
3. Verify
Sample Rate:
that
Rate:
Header
16000
for
16000 the contains
B can coming
number the
thefrom
known
codec SBGnegotiated
access to originating
type S-CSCF.
“3GPP-E-UTRAN-FDD”.
in AMR-WB
5.
3.
SDP Verfy
Verify
Media
a) the
that
contains call
Attribute
Message VoLTE
initial is(a):
the released
user
following
INVITErtpmap:104 properly
coming originate by/16000/1
attributes:
AMR
from either
HD
SBG voice
to party
call usingS-CSCF.
originating AMR-WB codec.
Verify that SDP
Media
2.
6. Verify
Protocol:
MIME Attribute
MTAS
SAPC
SIP/SDP.
Type: Policy
AMR-WB (a):forrtpmap:104
normalizes the B Charging
correct numberAMRto /16000/1
+1 Install
Rule and 10-digit
of Audio Rules & QoS Values in
contains
Verify
4.
MIMEVerify the
that
Type:
3. VerifyRate:
that following
P-Access-Network-Info
RTP
AMR-WB
for is attributes:
established
the B&number Header:
both ways access-type:
and voice
the codec negotiated in AMR-WB quality3GPP-E-UTRAN-FDD
is good. To be Completed
Gx-RAR
Sample
Media
Media for both
Attribute
Attribute 16000 MO (a): MT numbers
rtpmap:104 AMR /16000/1
5. Verfy
Sample
Media
a) the
Rate:call
Attribute
Message initial is(a):
16000
(a):
INVITE
rtpmap:104
released
rtpmap:104 properly
coming
AMR-WB/16000/1
AMR
from by either
/16000/1
SBG party
to originating S-CSCF. Verify that SDP
MIME
Media
6.
2.
MIMEVerify
Verify
contains
Type:
Attribute
SAPC
Type:MTAS
the
AMR-WB
AMR-WB Fieldname:
Policy
following for
normalizes rtpmap
correct
attributes: theCharging
B number Rule Install
to of Audio
+1 IEEE.802.11
and Rules & QoS Values in
10-digit
Verify
Media
Sample
Gx-RAR P-Access-Network-Info
Format:
Rate:
for both 104
16000
MO &established
MT Header:
numbers access-type: (wlan) To be Completed
3.
4. Verify
Sample
Media that
Rate:
Attribute for
16000
RTP(a): the
is B number
rtpmap:104 the
both codec
AMR-WB/16000/1ways negotiated
and voice in AMR-WB
quality is good.
MIME Type: AMR-WB
Media
Media
5.
2. Verfy
Verify
Sample Attribute
Attribute
the call
MTAS
Rate: is(a):
Fieldname:
normalizes
16000 rtpmap:104
released rtpmap
the properly
B number AMRby to/16000/1
either
+1 party
and 10-digit
Verify
4.
6. Verify
MIME
Media
3. Verify
SAPC P-Access-Network-Info
that
Type:
Format:
that
Policy RTP
AMR-WB
for104
has is established
the B number
correct theHeader:
both
Charging ways
codec access-type:
and voice of
negotiated
Rule Install quality3GPP-E-UTRAN-FDD
in AMR-WB
Audio is good.
Rules in Gx-RAR To be Completed
5.
MIMEVerfyType:
Sample
Media
towards the
Rate:call
Attribute
EPG, AMR-WB is(a):
16000
after released
rtpmap:104
receivingproperly AMR
Rx-AARby/16000/1
either
from party
P-CSCF
However,
6. Verify terminating
SAPC Policy user can
for correct only support
Charging AMR-NB.
Ruleto Install of Audio Rules & QoS Values in
2. Verify
Sample
MIME
Protocol: MTAS
Rate:
Type: 16000
AMR-WB
SIP/SDP. normalizes the B number +1 and 10-digit To be Completed
Gx-RAR
3. Verify
Sample
4. Verify for
Rate: both
that
that for
16000
RTP MO is&established
the MT numbersthe
B number both codec
waysnegotiated
and voice qualityin AMR-WB is good.
However,
Media
5.
b) Message terminating
VerfyAttribute
the183 is(a):
callSession user
released canproperly
rtpmap:104
Progress only support
AMRby
coming AMR-NB.
/16000/1
from either
MSCpartyto CSCF. Verify that SDP contains
Protocol:
4.
theVerify
MIME
6. SIP/SDP.
that
Type:
following
SAPC Policy RTP
AMR-WB is established
attributes:
has correct Charging both ways Rule and voice of
Install quality
Audio is good.
Rules in Gx-RAR To be Completed
5. Verfy the
Sample
towards Rate:
EPG,call16000
is released
after receivingproperly Rx-AARby either
from party
P-CSCF
1.
1.
b) UE-A
UE in
Message
6. Verify calls
3G UE-B
(ICS)
183
SAPC Policy originates
Session a
Progress voice call in the CS domain to
Charging Rule Install of Audio Rulesthat
coming
for correctAMR-NB/8000 from MSC to CSCF. party-B.
Verify SDPValues
& QoS containsin
Media
2. UE-B
VerifyAttribute
answers
that the (a):
and
agreedrtpmap:97
two-way
codec voice
is AMR pathWB.is established sussessfully. To be Completed
the
Gx-RAR
Media following
for both
Attribute attributes:
MO
Fieldname:& MT numbers
rtpmap
4. Message
a) Verify that initialRTP is established
INVITE coming from bothMGCF ways to and voice quality
originating is good.
I-CSCF. Verify that SDP
Media
5. Verfy
contains Format:
theAMR
the 97 is
call released
according toproperly
the by eitherrequirement.
preconditions party
Media
MIME Attribute
Type: (a): rtpmap:97 AMR-NB/8000 To be Completed
6.
3. SAPC
MediaVerify thatAMR-NB
Policy
Attribute has
SCCAS correct
Fieldname: Charging
inserts rtpmap
the CSRN number Rule Install of Audio
and routes Rulesininorder
to S-CSCF Gx-RARto break
Sample
towards
out Rate:
to MGCF EPG, 8000
basedafteronreceiving
external NetworkRx-AAR Selection
from P-CSCF
Media Format: 97
4.
MIMEVerify thatAMR-NB
Type: call is completed successfully and audio path is established between UE A
4.
and Verify
UE B. that ENUM request is executed by S-CSCF. Date: 2018-02-09
Sample
Protocol: Rate:
DNS 8000
Prepared: LMIESN Edmund Sheridan Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
xxx1.e164.arpa: type NAPTR, class IN
4.
and Verify that ENUM
response received request
is: Noissuch executed
name by S-CSCF. Ericsson Internal
Protocol:
5. Verify thatDNSthe call break out and the INVITE is sent to the MGCF based on External
xxx1.e164.arpa:
Network Selection settings type NAPTR, class IN
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 46 (402)

1. UE-A calls UE-B


2. UE-B answers and two-way voice path is established sussessfully. To be Completed
UE-A
1. UE in calls UE-Boriginates a voice call in the CS domain to party-B.
3G (ICS)
UE-B answers
2. Verify that theand two-way
agreed codecvoice path
is AMR is established sussessfully.
WB. To be Completed
a) Message initial INVITE coming from MGCF to originating I-CSCF. Verify that SDP
contains the AMR according to the preconditions requirement.
To be Completed
3. Verify that SCCAS inserts the CSRN number and routes to S-CSCF in order to break
out to MGCF
1. UE-A based on external Network Selection
calls UE-B
4. UE-B
2. Verifyanswers
that calland
is completed successfully
two-way voice path is and audio path
established is established between UE A
sussessfully. To be Completed
and UE B.
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed
1. UE-A calls UE-B
2. UE-B answers and two-way voice path is established sussessfully. To be Completed

Call cancelled To be Completed

Call cancelled To be Completed

User B shows the User A's number on screen when calls received from User A. To be Completed

User B doesn't show the User A's number on screen when calls received from User A. To be Completed

1. Call is forwarded to user C by IMS network.


To be Completed
2. User B doesn't ring and User C receives the call.
1. Call is forwarded to user C by IMS network. To be Completed
2. User C can talk with user A.
Test case passes if:
1. Call is forwarded to user C by IMS network. To be Completed
2. User C can talk with user A.
Test case passes if:
1. Call is forwarded to user C by IMS network. To be Completed
2. User C can talk with user A.
1.After
1. The callthefrom
conference
user A to button
user Bisdoes
hit the
notINVITE is sent to the MTAS with the conference
complete
URI andAthe response is a 200 OK To be Completed
2. User hears the barring announcement.
2. UE A has an active session with UE B on hold and a session with the conference
1.
1.The
focus.
UE-A call
UE Afrom
callssends
UE-B user B to user
a REFER to theA does
focusnotandcomplete
sets the conference URI (focus) in the To be Completed
2.
2. User
UE-B Banswers
request hears
URI, andthe barring
Refer-To
and two-way announcement.
headervoicetopath
the URI (PUI) of B. sussessfully.
is established The Refer-To method is set to
INVITE.
3. UE-A preses Hold, and sends re-INVITE/UPDATE
1. The call from user B to user A does not complete with held SDP "a=sendonly"
3. To be Completed
2. The
Userfocus
parameter tosends
B hears theaand
UE-B re-INVITE
barringreceives on200theOK
announcement. existing UE B SDP
with HELD leg .The content ofUE-B
"a=recvonly". the Refer-To
is held (no
header
voice pathis moved
in either to the Request-URI. The re-INVITE includes the SessionId URI and the
direction).
1.Verify
Verifyfeature
‘isfocus’
4. that call waiting
parameter feature has
in the call, been
Contact activated
header. successfully (check using SOAP UI
1. User
get,
4. TheEMA Awhen
got
getsends
focus or
UE-A
connected
puretest
resumesto
a re-INVITE thethe
get) hotthe
on
itnumber..
sends
lineexisting re-INVITE/UPDATE
UE
with held SDP To be Completed
"a=sendrecv" parameter to UE-B and receives 200B OKlegwith
(d2).HELD
The content of the Refer-
SDP "a=sendrecv" and
2.
To Verify
headerthat
two-way VoLTE
is moved
voice path is user
to thecan receive HD
Request-URI.
re-established voicere-INVITE
The
sussessfullycall usingincludes
AMR-WB thecodec.
SessionId URI and
3.
5. User
the A the
canfeature
‘isfocus’
Verify see tears
call theparameter
notification in of
down successfullythethe incoming
Contact
whenheader.
UE-Acallreleases
from User
theB.call header is
An Allow-Events To be Completed
4. Verify that
included and setthe to180 Ringing is sent
‘conference’ back
in case to the caller (User B) with the
mtasConfNotificationService CWA indication
is enabled
present.
5.
6. The
UE-Bfocus
preses responds
Hold, and to A withre-INVITE/UPDATE
sends a 202 Accepted. The ‘isfocus’
with feature
held SDP parameter is
"a=sendonly"
Check
included
parametertheinAlert-Info
theUE-A
to ContactandHeader
header.
receivesin the200SIPOKmessage:
with HELD SDP "a=recvonly". UE-A is held (no To be Completed
Parameter
6. Thepath
voice Focus Line
in Alert-Info:
sends
either Notify<urn:alert:service:call-waiting>
adirection). (100 Trying)
5.
7. Verify
7. Focus that
Verify receives User
when UE-B B
a 200 can hear an
OK (Notify)
resumes announcement being played (ringing)
the call, it sends re-INVITE/UPDATE with while waiting
held SDP
for User A to answer the incoming call. To be Completed
8. 200 OK with SDP offer from B, media direction indicate
"a=sendrecv" parameter to UE-A and receives 200 OK with HELD SDP "a=sendrecv" ‘sendReceive’.200 OK withand
6.
SDPWhen User
voiceApath
forwarded
two-way toignores
focus. the call from sussessfully
is re-established User B, verify User B is forwarded to User A's VM
or
9. the
8. The call
focus
Verify ends
the callif tears
sends user Adown
an INVITE doesn't havewith
request
successfullyVMwhenservicde
the UE-B
UE-Aoffer to thethe
releases MRFcallrequesting MRF to
7. The
add UEcall
B tobetween
the same User A and User
conference C remain
as UE A. up
10. Focus receives a 200 OK with SDP answer from the MRF. Focus sends ACK to the
User B shows the User A's number on screen when calls received from User A.
MRF. To be Completed
11. The focus sends NOTIFY to UE A to indicate the success of the REFER.200 OK in
response to NOTIFY
User B doesn't show(200 the User OK). A's number on screen when calls received from User A. To be Completed
12.Focus sends ACK with SDP answer to UE B; UE B and focus is now in conference
session with media.Ro: CCR update/CCA including Conference-Id and two Related-ICID
AVPs
13.ACK is forwarded to UE B by the terminating AS Date: 2018-02-09
Prepared: LMIESN
14 The Focus initiates EdmundofSheridan
disconnection the replacedSheet: VoLTE-VoWiFi
dialog by sending BYE. E2E Site2 _x000D_Rev: PA1
15. UE A responds with 200 OK Ericsson Internal
16. Media resource for handling UE B on hold is released
17. 200 OK (hold resource release) from MRF
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 47 (402)

1. Call is forwarded to user C by IMS network.


2. User B doesn't ring and User C receives the call.
To be Completed
3. 181
Test Callpasses
case Forwarded
if: and INVITE from MTAS contains the correct cause in the History-
info header
1. Call is forwarded to user C by IMS network.
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call is
info headerforwarded to user C by IMS network.
2. User C can talk with user A. To be Completed
3. 181 Call Forwarded and INVITE from MTAS contains the correct cause in the History-
1. The
info call from user A to user B does not complete
header
2. MTAS blocks the call with 603 Denied To be Completed
1.User
3. UE-AAcalls
hears UE-B
the barring announcement.
1.UE-B
2. The call to theand
answers international
two-way voice numberpathdoes not complete
is established sussessfully.
2.
3. MTAS blocksHold,
UE-A preses the call
andwith
sends603re-INVITE/UPDATE
Denied with held SDP "a=sendonly" To be Completed
3. User A hears
parameter the and
barring announcement.
1. The call toto UE-B receives
the international 200 OKdoes
number with not
HELD SDP "a=recvonly". UE-B is held (no
complete
voice path in either direction).
2. MTAS blocks the call with 603 Denied To be Completed
4.
3. Verify
User when
Athat
hears UE-A
the resumes
barring the call, it sends re-INVITE/UPDATE with held SDP
announcement.
MRF
1. requesting
Verify
"a=sendrecv" call MRF
waiting
parameter tofeature
add UEhas
to UE-B Band
tobeen
the same conference
activated
receives 200 OK withas
successfullyUE
HELD A.
(check using SOAP UIand
SDP "a=sendrecv"
10.
get, Focus receives
EMA voice
two-way get orpath a is
200
puretest OK with SDPsussessfully
get)
re-established answer from the MRF. Focus sends ACK to the To be Completed
MRF.
2.
5. User
UE-B Apreses
can see theand
Hold, notification of the incoming callwith
sends re-INVITE/UPDATE fromheld
UserSDP
B. "a=sendonly"
11.
3. The focus
Verify
parameter sends
thattothe NOTIFY
180and
UE-A Ringing to
is UE
receives sent Aback
200 to
OKindicate the SDP
to theHELD
with success
caller (User of with
B) the REFER.200
the CWA
"a=recvonly". OK
heldin(no
indication
UE-B is
response
voice pathtoinNOTIFY
present. (200 OK).
either direction). To be Completed
12.Focus sendsUE-B
6. Verify when ACK with SDP the
resumes answer
call, to UE B; UE
it sends B and focus is now
re-INVITE/UPDATE in conference
with held SDP
Check
session the
with
"a=sendrecv" Alert-Info
media.Ro:Header
parameter to in
CCR the and
SIP message:
update/CCA
UE-A including
receives 200 Conference-Id
OK with HELD SDPand two Related-ICID
"a=sendrecv" and
Parameter Line path
Alert-Info: <urn:alert:service:call-waiting> To be Completed
AVPs
two-way voice is re-established sussessfully
13.ACK
7. Verifyis the
forwarded
call tearstodown
UE B by the terminating
successfully AS releases the call
when UE-A
14 The Focus initiates disconnection of the replaced dialog by sending BYE.
Test
15. UEcase passes if:with 200 OK
A responds
1.
16.Call is forwarded
Media resource to foruser C by IMS
handling UE Bnetwork.
on hold is released
2.
17.User
200 COKcan talkresource
(hold with userrelease)
A. from MRF To be Completed
Test
3. 181case passes
Call Forwardedif: and
18
1. Termination
Call is forwarded of UE on INVITE
toBuser hold from MTAS contains the correct cause in the History-
C by announcement.
IMS network.
info header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
Test
3. 181case
Callpasses if: and INVITE from MTAS contains the correct cause in the History-
Forwarded
1. Call
info is forwarded to user C by IMS network.
header
2. User C can talk with user A. To be Completed
3. 181 Call Forwarded and INVITE from MTAS contains the correct cause in the History-
info header
1. Call is forwarded to user C by IMS network.
2. User B doesn't ring and User C receives the call.
3. 181 Call Forwarded and INVITE from MTAS contains the correct cause in the History- To be Completed
info header
1. Call is not forwarded to user C by IMS network.
2. User B ring and receives the call. To be Completed
3. INVITE from MTAS contains the destination number.
UE showed CFU status correctly. To be Completed

1. Call is forwarded to user C by IMS network. To be Completed


2. User B doesn't ring and User C receives the call.
1. Call is not forwarded to user C by IMS network.
2. User B ring and receives the call. To be Completed
3. INVITE from MTAS contains the destination number.
UE showed CFU status correctly. To be Completed

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
1. Verify that while a VoWiFi call is established, UE-A undergoes a LTE to WiFi
handover TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 48 (402)
2. Verify messages at the MME
1. a)Verify that while a VoWiFiw/Request
S1 UplinkNASTransport call is established, UE-A undergoes
type: Handover a LTE to WiFi
under Non-Access-Stratum
handover
b) GTPv2 Create Session Request to ims APN w/Handover Indicator set to True
2. c)
Verify messages
Successful at the (Request
Response MME
1. a)Verify that while
S1 UplinkNASTransport call isAccepted)
a VoWiFiw/Request established, UE-A undergoes
type: Handover under a WiFi to LTE
Non-Access-Stratum
To be Completed
3. STR/STA
handover success (EPG to AAA) with Termination-Cause: DIAMETER_USER_MOVED
b) GTPv2
4. Verify
UE registersCreate Session
on VoLTE Request to ims APN w/Handover Indicator set to True
2. messages at thew/PANI
MME setAccepted) to: 3GPP-E-UTRAN-FDD
5. c)
a)
Successful
STR/STA
S1
Response
success (WMG(Request
UplinkNASTransport tow/Request
AAA) with Termination-Cause:
type: Handover underDIAMETER_USER_MOVED
Non-Access-Stratum
To be Completed
3. STR/STA
8. b)
Verify thesuccess (EPG to
call survives theAAA) with Termination-Cause:
handover andAPN
2-way DIAMETER_USER_MOVED
audio continues to work.
UEGTPv2
4. Verify
9.
Create
registers
the SAPC
Session
on VoLTE
policy
Request
w/PANI settoto:ims w/Handover
3GPP-E-UTRAN-FDD Indicator set to True
5. c) Successful
1. STR/STA
Verify that
that Response
while(WMG
success a VoLTE (Request
VoWiFi tocall
AAA) Accepted)
callisisestablished,
established,
with UE-Aundergoes
undergoes
Termination-Cause: aLTE
LTEtotoWiFi
WiFihandover
DIAMETER_USER_MOVED To be Completed
1.
3. Verify
STR/STA while a UE-A a
handover
8. thesuccess
VerifyWiFi)
(enable
(EPG to
call survives theAAA) with Termination-Cause:
handover DIAMETER_USER_MOVED
and 2-way audio continues to work.
4. Verify
2. UE registers
messages on VoLTE
at the w/PANI set to: 3GPP-E-UTRAN-FDD
9.
2.
5. Verify
1. a)
Verify
STR/STA
the
UE-A
that
SAPC
while
success
policy
attaches toMME
a VoWiFi
(WMG the WMG
call andTermination-Cause:
iswith
tow/Request
AAA) IMS UE-A undergoes
established, a LTE to WiFi
DIAMETER_USER_MOVED To be Completed
3. S1 UplinkNASTransport
Verify the call survives the handover type:
and Handover
2-way audio under Non-Access-Stratum
handover
8. b)
Verify
GTPv2the call
Create survives the handover
Session Request to ims APN and 2-way audio continues
w/Handover continues to
to work.
Indicator work.
set to True
4.
2. Verify
Verify
9. c) the SAPC
messages
the SAPC policy
at the
policy MME
Successful
1. a)Verify Response (Request
that while a VoWiFiw/Request Accepted)
call is established, UE-A undergoes a WiFi to LTE To be Completed
3. S1 UplinkNASTransport type: Handover
STR/STA success (EPG to AAA) with Termination-Cause: DIAMETER_USER_MOVED under Non-Access-Stratum
handover
b) GTPv2 Create Session Request toto:ims APN w/Handover Indicator set to True
4. UE
2. c) registers
Verify messages on VoLTE
at thew/PANI
MME setAccepted) 3GPP-E-UTRAN-FDD
5. a) Successful
STR/STA Response
success (WMG(Request
tow/Request
AAA) with Termination-Cause: DIAMETER_USER_MOVED To be Completed
3. S1
STR/STAUplinkNASTransport type: Handover under Non-Access-Stratum
8. b)
Verify
GTPv2thesuccess
Create
(EPG to
call survives
Session theAAA)
Request
with Termination-Cause:
handover to andAPN
ims 2-way DIAMETER_USER_MOVED
audio continues
w/Handover to work.
Indicator set to True
4.
9. UE
1. c) registers
Verify
Verify the
thatSAPCon VoLTE
while policy
a VoLTEw/PANI
call isset to: 3GPP-E-UTRAN-FDD
established, UE-A undergoes an LTE to 3G handover
5. Successful
STR/STA Response
success (WMG (Request
to AAA) Accepted)
with Termination-Cause: DIAMETER_USER_MOVED To be Completed
1. Verify
2. STR/STA
3. that
Verify messages while a
at VoLTE
thetoMME call is established, UE-A undergoes a LTE to WiFi handover
8. Verify
(enable
a) thesuccess
WiFi)
HandoverRequired
(EPG
call survives theAAA) with Termination-Cause:
handover DIAMETER_USER_MOVED
and 2-way audio continues to work.
4.
9. UE registers
Verify on VoLTE w/PANI set to: 3GPP-E-UTRAN-FDD
2.
5. b) PS tothe
Verify
STR/STA UE-A
CS SAPC policyto the WMG and IMS
attaches
request/response
success (WMG to AAA) with Termination-Cause: DIAMETER_USER_MOVED To be Completed
3. Verify
8. c) the
the call survives the
call
HandoverComplete
Verify survives the handover
handover and and 2-way
2-way audio
audio continues
continues to
to work.
work.
4. Verify
9. d) SRVCC
Verify the
thePSSAPC
to CS
SAPC policy
Complete notification/acknowledge
policy
1. To be Completed
3. Verify
PCRF sendsthat Rxafter P-CSCF receives initial
Abort-Session-Request INVITE,
to PCSCF withthe
AVPS-CSCF is selected
Abort-cause = PS tobased
CS
on the registration information stored in cache.
Handover
2.
1. Ensure
4.
1. MSC
Verify thatINVITE
sends
that
Verify forwards
that the access
while
while aato
VoLTE
VoLTE type
the STN-SR
call
call isfor
is ofthe
the originating
established,
established, party is aan
ATCF UE-B undergoes
UE-A undergoes VoLTE.
an LTE to 3G handover
S1 handover or UE-
5.
2.
3. PCSCF
Verify
MTAS messages
normalizes the INVITE
at the
the MME to the
number CSCF containing the SCCAS ATU-STI
B
6. undergoes
CSCF an
forwards X2 handover
the INVITE to the SCCAS, who updates the TO header to UE-A's To be Completed
In
2. a) HandoverRequired
initial
Verify
1. b)
Verify SIP
the
thatINVITE
call acoming
survives
while VoLTEand from
2-way SBG
audio tocontinues
originating S-CSCF,anverify
to work tothat thesip
P-uri
7. Verify
PS tothe
CScall
Access-Network-Info survives
request/response thecall
Header
is established,
handover
contains andthe UE-A
2-way undergoes
audio
known continues
access type
LTE 3G handover
to“3GPP-E-
work.
2.
1. Verify
Verify
c) messages
that VoLTE
HandoverComplete at the
userMME can initiate voice call using 7-digit dialing and AMR-
UTRAN-FDD”.
a) HandoverRequired
WB
4. d) codec.
SRVCC
1. Verify
Verify PS
that
that to
whileCS
VoLTE Complete
a VoLTE
user callnotification/acknowledge
can is established,
originate UE-B undergoes an LTE to 3G handover
toHD voice call using AMR-WB codec.
b) PS to CS request/response To be Completed
3. PCRF
Protocol:
2. Verify sends Rx Abort-Session-Request
SIP/SDP.
messages at the MME PCSCF with AVP Abort-cause = PS to CS
Protocol:
c) SIP/SDP.
HandoverComplete
Handover
a)
d) HandoverRequired
SRVCC PSINVITE
to CS Complete notification/acknowledge
4.
a) MSC
b) PS sends
Messageto CSinitial to the coming
request/response
INVITE STN-SR offrom
the ATCF
SBG to originating S-CSCF. Verify To be Completed
3.
a)
5. PCRF
Message
PCSCF sends
forwardsRx Abort-Session-Request
initial INVITE
the INVITE coming
to fromtocontaining
the CSCF PCSCF
SBG to with
theAVP
originatingAbort-cause
SCCAS S-CSCF. = PS tothat
ATU-STI Verify CS
that
SDP c) HandoverComplete
contains
Handover the following attributes:
1.
SDP Verify
6. d) that
contains
CSCF forwards
SRVCC VoLTE
the
to the
PSINVITE user
following can initiate
attributes: voice
INVITE to notification/acknowledge
CS Complete call to 411 and AMR-WB
the SCCAS, who updates the TO header to UE-B's sip uricodec.
4.
7. MSC
Protocol:
Media sends
SIP/SDP.
VerifyAttribute
the call (a):tortpmap:104
the
theSTN-SR of the ATCF
AMR-WB/16000/1 To be Completed
3. PCRF
Media
5. PCSCF sends
Attribute
forwardsRxsurvives
(a):
the
handover
Abort-Session-Request
rtpmap:104
INVITE to the AMR
and 2-way with
CSCFtocontaining
PCSCF
/16000/1
audioAVPcontinues
the SCCAS
to work.
Abort-cause
ATU-STI = PS to CS
Media
Handover
1.
6. Verify Attribute
CSCFType: that
forwards
Fieldname:
VoWiFi
theINVITEuser can
INVITEcoming
rtpmap
initiate
to the SCCAS, voice call
who updates to 411 and AMR-WB
the TO S-CSCF.
header toVerifycodec.
UE-A's sip uri
MIME
a) Message
Media AMR-WB
initial offrom SBG to originating that
4. VerifyFormat:
7. MSC
Protocol:
Sample
sends
SIP/SDP.
the
Rate: call 104
INVITE to the
survives
16000 theSTN-SR
handover the ATCF
and 2-way audio continues to work.
SDP
MIME contains
5. PCSCF Type: the the
AMR-WB
forwards following
INVITE toattributes:
the CSCF containing the SCCAS ATU-STI
1.
6. Verify
Sample that VoLTE
CSCF forwards
Rate: user can
theINVITE
16000 INVITE initiate
to the SCCAS, voice
who call to 611
updates theand AMR-WB
TO S-CSCF.
header codec.
toVerify
UE-B's sip uri
a) Message
Verify
Protocol:
7. Verify
initial
P-Access-Network-Info
SIP/SDP.
the call survives
coming
the handover
from
Header: SBG to originating
access-type:
and/16000/1 3GPP-E-UTRAN-FDD
2-way audio continues to work.
that To be Completed
Media Attribute (a): rtpmap:104
SDP contains the following attributes: AMR
MIME
1. Type:
However,
Verify that AMR-WB
terminating
VoWiFi user usercancaninitiate
only support AMR-NB.
voice call to 611 and AMR-WB codec.
2.
a) Verify
Message
Sample
Protocol: MTAS
Rate: normalizes
initial
16000
SIP/SDP. INVITE comingthe B number
from SBG toto
+1originating
and 10-digitS-CSCF. Verify that To be Completed
Media
SDP Attribute
3. Verify that the
contains (a):
for the rtpmap:104
B number
following AMR /16000/1
the codec negotiated in AMR-WB
attributes:
MIME
1.
Media Type:
Verify thatAMR-WB
AttributeVoLTE(a): user can initiate
rtpmap:104 AMR voice call to 2223GPP-E-UTRAN-FDD
/16000/1 and AMR-WB codec.
Verify
b)
a)
Sample P-Access-Network-Info
Message
Rate:183
initialSession
16000 INVITE Progress
coming Header:
coming
from access-type:
SBG from MSC to CSCF.
to originating Verify
S-CSCF. that that
Verify SDP To be Completed
Protocol:
MIME
Media Type:SIP/SDP.
AMR-WB
Attribute (a): rtpmap:104 AMR /16000/1
contains
SDP the following
contains the following attributes:
attributes:
Sample
MIME
1.
2. VerifyRate:
Type:
that
MTAS 16000
AMR-WB
VoWiFi
normalizes user can initiate
theHeader:
B number voice call to 222 and AMR-WB codec.
Verify
a)
Sample P-Access-Network-Info
Message
Rate:initial
16000 INVITE coming from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that To be Completed
Protocol:
3. Verify
Media SIP/SDP.
that
Attributefor the
(a): B number
rtpmap:97
rtpmap:104 the codec
AMR-NB/8000
AMR negotiated
/16000/1 in AMR-WB
SDP
4. contains
Verify that the
RTP following
is
(a): attributes:
established
rtpmap:104 both
AMR ways and
/16000/1 voice quality is good.
Media
MIME
1.
2. Attribute
Type:
Verify that
MTAS AMR-WB
VoLTEFieldname:
normalizesuser can rtpmap
the initiate
B numbervoice callparty
to #250 and AMR-WB codec.
5. Verfy
Verify
a)
MIME
Media
Sample the
Type: call
initial
Format:
Rate: is
AMR-WB
97
16000 released
P-Access-Network-Info
Message INVITE properly
Header:
comingthe from by either
access-type:
SBGnegotiated 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that
Protocol:
3. SAPC
6. Verify
Media SIP/SDP.
that
Attribute
Policy for
has the
(a): B number
rtpmap:104
correct Charging AMRcodec
Rule/16000/1
Install of Audioin AMR-WB
Rules in Gx-RAR To be Completed
SDP
MIME
Mediacontains
Sample Rate:
Type: the
16000
AMR-NB
Attribute following
(a): attributes:
rtpmap:104 AMR /16000/1
MIME
towards
1.
2. Type:
Verify EPG,
that
MTAS AMR-WB
after
VoLTE receiving
normalizesuser cantheRx-AAR
initiate
B numberfrom
voice P-CSCF
call to #611 and AMR-WB codec.
Sample
Verify
a)
MIME
Sample Rate:
Message
Type:
Rate: 8000
P-Access-Network-Info
initial
AMR-WB
16000 INVITE coming Header:
from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that
Protocol:
3.
4. Verify
Media
Verify SIP/SDP.
that
Attribute
that for
RTP the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec negotiated
/16000/1
ways and voice in AMR-WB
quality is good. To be Completed
SDP
Mediacontains
Sample Rate: the
Attribute16000 following
(a): attributes:
rtpmap:104 AMR /16000/1
MIME
1.
2. VerfyType:
5. Verify the
that
MTAS AMR-WB
call
ENUMis released
VoLTE
normalizesrequest
user canproperly
theis executed
initiate
B numberby either
voiceby callparty
S-CSCF.
to #7623 and AMR-WB codec.
Verify
a)
MIME
Sample
6. SAPCP-Access-Network-Info
Message
Type:
Rate:initial
Policy AMR-WB
16000
has INVITE
correct coming Header:
Charging from
Rule access-type:
SBGInstall of 3GPP-E-UTRAN-FDD
to originating
Audio S-CSCF.
Rules in Verify that
Gx-RAR
Protocol:
3.
4. Verify
Media
Verify DNS
SIP/SDP.
that
Attribute
that for
RTP the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec negotiated
/16000/1
ways and voice in AMR-WB
quality is good. To be Completed
SDP contains
Sample
towards Rate:
EPG,
xxx1.e164.arpa:
Media Attributethe
16000
afterfollowing
type
(a): receiving
NAPTR, attributes:
rtpmap:104 Rx-AAR
class IN
AMR from P-CSCF
/16000/1
MIME
1.
2. VerfyType:
5. Verify the
that
MTAS AMR-WB
call is released
VoLTE
normalizesuser can properly
the initiate
B numberby either
voice callparty
to *1067 and AMR-WB codec.
Verify
and
a)
MIME
Sample
6. SAPCP-Access-Network-Info
response
Message
Type:
Rate:
Policy received
initial
AMR-WB
16000
has INVITE
correct No Header:
is:coming such
Charging name
from
Rule access-type:
SBGInstall of 3GPP-E-UTRAN-FDD
to originating
Audio S-CSCF.
Rules in Verify that
Gx-RAR To be Completed
Protocol:
3.
4. Verify
Media SIP/SDP.
that
Attribute
Verify that for
RTP the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec negotiated
/16000/1
ways and in AMR-WB
6.
SDPVerify
Sample
towards
Media that the
contains
Rate:
EPG,
Attribute16000
after call break attributes:
following
(a): receiving out
rtpmap:104 and
Rx-AARAMR the
fromINVITE
P-CSCF
/16000/1 is sent to the is
voice quality good.
MGCF based on
MIME
5.
1.
2. VerfyType:
Verify
External the
that
MTAS AMR-WB
call is Selection
VoLTE
Network released
normalizesuser can properly
the initiate
B number
settings by either
voice callparty
to *225 and AMR-WB codec.
Verify
a)
MIME
Sample
6. SAPCP-Access-Network-Info
Message
Type:
Rate:initial
Policy AMR-WB
16000
has INVITE coming Header:
from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that
Protocol:
3.
7. Verify
Media
4.
SDP
SIP/SDP.
that
Attribute
contains
Sample Rate:
for
call
RTP
the
16000 isiscorrect
the
(a): Charging
B number
completed
rtpmap:104
established
following
the Rule
codec
successfully
AMR
both
attributes:
Install
and of
negotiated
/16000/1
ways and Audio
audio
voice in Rules
AMR-WB
path
quality in Gx-RAR
isisestablished
good. To be Completed
towards
Media
between
MIME
5. Verify EPG,
Attribute
UE
VerfyType:
the A after
and
AMR-WB
call (a): receiving
rtpmap:104
PSTN
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS normalizes
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
a) Message
MIME
Sample
6. SAPC thatinitial
Type:
Rate:
Policy AMR-WB
16000
has INVITE
correct coming
Charging from
RuleSBG to originating
Install S-CSCF. Verify that
3.
4.
SDP
Verify
Media Attribute
contains
Sample Rate:
for
RTP
the
16000
the
(a):
is B number
rtpmap:104
established
following
the
AMR
both
attributes:
codec and of
negotiated
/16000/1
ways Audio
voice Rules
quality is in
in AMR-WB Gx-RAR
good. To be Completed
towards
Media
MIME EPG,
Attribute
VerfyType:
5. Verify the after
AMR-WB
call (a): receiving
rtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS normalizes
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
MIME
Sample
6. SAPCType:
Rate:
Policy AMR-WB
16000
has correct Charging Rule Install
3.
4. Verify
Media
Verify
Sample
that
Attribute
that
Rate:
for
RTP
16000
the
(a):
is B number
rtpmap:104
established the
AMR
bothcodec and of
negotiated
/16000/1
ways Audio
voice Rules
quality is in
in AMR-WB Gx-RAR
good. To be Completed
towards
Media
MIME EPG,
Attribute
VerfyType:
5. Verify the after
AMR-WB
call (a): receiving
rtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS normalizes
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
MIME
Sample
6. SAPCType:
Rate:
Policy AMR-WB
16000
hasthe correct Charging Rule Install
3.
4. Verify
Verify
Sample
that
that
Rate:
for
RTP
16000 is B number
established the
bothcodec
ways and of
negotiated Audio
voice Rulesis in
in AMR-WB
quality Gx-RAR
good. To be Completed
towards
Media
5. Verify EPG,
Attribute
Verfy the after
(a): receiving
callnormalizesrtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2.
Verify MTAS
P-Access-Network-Info B number
Header: access-type: 3GPP-E-UTRAN-FDD
MIME
6. SAPCType:
Policy AMR-WB
hasthe correct Charging Rule Install
3.
4. Verify
Verify
Sample
that
that
Rate:
for
RTP
16000 is B number
established the
bothcodec
ways and of
negotiated Audio
voice Rulesis in
in AMR-WB
quality Gx-RAR
good. To be Completed
towards
Media
5. Verify EPG,
Attribute
Verfy the after
(a): receiving
callnormalizesrtpmap:104
is releasedthe Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party
2. MTAS B number
MIME
6. SAPCType:
thatAMR-WB
Policy hasthe correct Charging Rule Install
3.
4. Verify
Sample Rate:
for
RTP
16000 is B number
established the
bothcodec
ways and of
negotiated Audio
voice Rules
quality
Date: is in
in AMR-WB Gx-RAR
good.
2018-02-09
towards
Media EPG,
Attribute
5. Verfy the call after
(a): receiving
rtpmap:104
is released Rx-AAR
properlyAMR from P-CSCF
/16000/1
by either party VoLTE-VoWiFi E2E Site2
Prepared: LMIESN Edmund Sheridan Sheet: _x000D_Rev: PA1
MIME
6. SAPCType:
Policy AMR-WB
hasiscorrect Charging Rule Install of Audio Rules
4. Verify
Sample that
Rate: RTP
16000 established both ways and voice quality
Ericsson is in Gx-RAR
good.
Internal
towards EPG, after receiving Rx-AAR from
5. Verfy the call is released properly by either party P-CSCF
6. SAPC Policy has correct Charging Rule Install of Audio Rules in Gx-RAR
SDP contains the following attributes:
1. Verify that VoLTE user can initiate voice call to *646 and AMR-WB codec.
a) Message
Protocol: initial INVITE coming from SBG to originating S-CSCF. Verify that
SIP/SDP.
Media Attribute
SDP contains the(a): rtpmap:104
following AMR /16000/1
attributes:
MIME Type:
1. Verify thatAMR-WB
VoLTE TEST user canOBJECT
initiate voice _x000D_VoLTE/VoWiFi
LISTcall to *7627 and AMR-WB codec. Test Object List 49 (402)
a) Message
Sample
Protocol: Rate: initial
16000
SIP/SDP. INVITE coming from SBG to originating S-CSCF. Verify that
Media
SDP Attribute
contains the (a): rtpmap:104
following AMR
attributes: /16000/1
1. Verify
MIME thatAMR-WB
Type: VoLTE user can initiate voice call to 9704672222 and AMR-WB
Verify
codec.
a)
Sample P-Access-Network-Info
MessageRate: initial
16000 INVITE comingHeader:
from SBGaccess-type: 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that To be Completed
Media
Protocol:Attribute
SDP contains the(a):
SIP/SDP. rtpmap:104
following AMR /16000/1
attributes:
MIME
1.
2. Type:
Verify that
MTAS AMR-WB
VoLTE
normalizesuser can theinitiate
B numbervoice call to 0 and AMR-WB codec.
Verify
Sample P-Access-Network-Info
Rate: 16000 Header: access-type: 3GPP-E-UTRAN-FDD To be Completed
Protocol:
3.
a) Verify
Message
Media SIP/SDP.
that for
initial
Attribute the
INVITE
(a): B number
comingthe
rtpmap:104 codec
from
AMR SBGnegotiated in AMR-WB
to originating
/16000/1 S-CSCF. Verify that
Media
SDP
MIME
1.
2. Attribute
contains
Type:
Verify that
MTAS the
AMR-WB
VoLTE(a):
normalizesrtpmap:104
following
user can
the AMRvoice
attributes:
initiate
B number /16000/1
call to 00 and AMR-WB codec.
Verify
a)
MIME
Sample P-Access-Network-Info
Message
Type:
Rate: initial
AMR-WB
16000 INVITE comingHeader:
from access-type:
SBG 3GPP-E-UTRAN-FDD
to originating S-CSCF. Verify that To be Completed
Protocol:
3. Verify SIP/SDP.
that for the B number the codec negotiated in AMR-WB
SDP
Sample
Media
Media contains
Rate: the
Attribute
Attribute 16000 following
(a):
(a): rtpmap:104
rtpmap:104attributes:
AMR
AMR /16000/1
/16000/1
2. Verify
MIME
Verify MTAS
Type: normalizes
AMR-WB
P-Access-Network-Info theHeader:
B number access-type: 3GPP-E-UTRAN-FDD
a)
3. Message
MIME Type:
Verify thatinitial
AMR-WB
for INVITE
the B coming
number from
the SBG
codec to originating
negotiated S-CSCF. Verify that
in AMR-WB To be Completed
Media
4. Verify
Sample
SDP
Sample Attribute
that the
Rate:
contains
Rate: RTP
16000
16000(a): rtpmap:104
is established
following AMRways
both
attributes: /16000/1
and voice quality is good.
Media
MIME
5.
2. Verfy
VerifyAttribute
Type:
the
MTAS AMR-WB
call is(a): rtpmap:104
released
normalizes AMRby/16000/1
properly
the B number either party
MIME
Sample
6. SAPC Type:
Rate:
PolicyAMR-WB
16000
has
Verify
3.
Media
4. Verify
Sample Attribute
Rate: RTP
16000 iscorrect
P-Access-Network-Info
Verify that
that for the
(a): Charging
B number
rtpmap:104
established Header:
the
AMR
bothRule
codec
waysInstall
and of
access-type:
negotiated
/16000/1 Audio
voice Rules
in AMR-WB
quality is in
3GPP-E-UTRAN-FDDGx-RAR
good. To be Completed
towards
Media
MIME EPG,
Attribute
5. VerfyType: after
AMR-WB
the call is(a): receiving
rtpmap:104
released Rx-AAR
AMRby
properly from P-CSCF
/16000/1
either party
Verify
2.
MIME
Sample
6. SAPC P-Access-Network-Info
Verify MTAS
Type:
Rate:
Policy normalizes
AMR-WB
16000
has theHeader:
B number access-type: 3GPP-E-UTRAN-FDD
4.
3. Verify that
that RTP
VerifyRate:
Sample for
16000 iscorrect
the
Charging
established
B number both
the
Rule
ways
codec
Install
and of Audio
voice
negotiated
Rules
quality
in AMR-WBis in Gx-RAR
good. To be Completed
towards
5. Verfy EPG,
the after
call is receiving
released Rx-AAR
properly from
by P-CSCF
either party
2. Verify
Media
Verify MTAS normalizes
Attribute (a): rtpmap:104
P-Access-Network-Info theHeader:
B number
AMR /16000/1
access-type: 3GPP-E-UTRAN-FDD
6.
3. SAPC
4. Verify
MIME Policy
that
Type:
Verify hasthe
for
thatAMR-WB
RTP iscorrect Charging
B number
established the
bothRule
codec
waysInstall
and of
negotiatedAudio
voice Rules
in AMR-WB
quality is in Gx-RAR
good. To be Completed
towards
Media
Sample
5. Verfy EPG,
Attribute
Rate:
the after
16000
call (a):
is receiving
rtpmap:104
released Rx-AAR
AMR
properly from
by P-CSCF
/16000/1
either party
2. Verify MTAS normalizes the B number
MIME
1.
3. the Type:
6. Verify
SAPC thatAMR-WB
VoLTE
Policy UE-A
hasthe
for sends
correct sos when
Charging
B number dialing 911 of Audio
Rule Install
the codec negotiated Rules in Gx-RAR
in AMR-WB
Sample
4.
2. Verify
the
towards Rate:
MME/EPG
EPG,
Media Attribute 16000
that RTPafter isreceiving
established
should
(a): both
haveRx-AAR
rtpmap:104 the ways
sosfrom
AMR APN and voice quality
configured
P-CSCF
/16000/1 and soisthe
good.
SOS SIP call
5. VerfyType:
continues
MIME thetocall
theisPCSCF,
AMR-WB released properly
ECSCF, GMLCby(LRF),
eitherECSCF,
party MGCF, Metaswitch, and
4.
6. Verify
SAPC thatUE-A
Policy RTP iscorrect
hassends established
ChargingbothRule
ways and ofvoice quality is in
good. To be Completed
PSAP.
1. the VoLTE
Sample Rate: 16000 sos when dialing 911Install Audio Rules Gx-RAR
5.
3.
2. Verfy
towards the
EPG,call
theMME/EPG
the location is the
after
of released
should receiving
UE
have properly
Rx-AAR
is the
determined
sos APNby
fromeither party
viaP-CSCF
the:
configured Dia-LRR/LRA,
and so the SOSDia-PLR/PLA,
SIP call continues
6.
to
andSAPC
4. the Policy
PCSCF,
lcsap/lpp/lppa
Verify hasiscorrect
thatECSCF,
RTP GMLC Charging
(LRF),
messages.
established bothRule
ECSCF, MGCF,
waysInstall of Audio
Metaswitch,
and voice Rules
and
quality is in
PSAP. Gx-RAR
good. To be Completed
1.
3. the
the VoLTE
towards EPG,UE-A
location after
of thesendsUE issos
receiving when dialing
Rx-AAR
determined 911
from
via the:P-CSCF
Dia-LRR/LRA, Dia-PLR/PLA, and
5.
2. Verfy the
the MME/EPG
lcsap/lpp/lppa
call is released properly by either party
should have the sos APN configured and so the SOS SIP call continues
messages.
6. the
to SAPC Policy
PCSCF, has correct
ECSCF, GMLC (LRF),Charging
ECSCF,Rule
MGCF,Install of Audioand
Metaswitch, Rules
PSAP.in Gx-RAR To be Completed
1.
3. the
towardsVoLTE
EPG,
the location UE-A
after
of thesends sos
receiving
UE is when dialing
Rx-AAR
determined 911
from
via the:P-CSCF
Dia-LRR/LRA, Dia-PLR/PLA, and
1. VoWiFi dials
2. the MME/EPG 911
should have the sos APN configured and so the SOS SIP call continues
lcsap/lpp/lppa messages.
2. the
to UE attaches
PCSCF, ECSCF, to the GMLCsos (LRF),
APN via the MGCF,
ECSCF, WMG Metaswitch,
and EPG and PSAP. To be Completed
3.
1. UE
the sends
location
VoWiFi INVITE
dials the w/
of911 UE urn:service:sos
is determined viato the
the: PCSCF
Dia-LRR/LRA, Dia-PLR/PLA, and
lcsap/lpp/lppa
4. the call is messages.
routed to the ECSCF then MGCF
2. UE attaches to the sos APN via the WMG and EPG To be Completed
5.
3. Verify
UE sends callINVITE
is successful and Phase 1 to
w/ urn:service:sos andthe2 information
PCSCF from the 911
dispatch person
4. the call is routed to the ECSCF then MGCF
6. To be Completed
5. Verify
Verify SAPC
call is Policy
successful for correct
and PhaseRules1 &andQoS Values for SOS
2 information apn
from thein911
Gx-RAR
7. Verify charging
dispatch person from ECSCF after call ends
6. Verify SAPC Policy for correct Rules & QoS Values for SOS apn in Gx-RAR
7. Verify charging from ECSCF after call ends
1. Call gets successfully connected.
2. Subscriber doesn't get charged (Billing confirmation). To be Completed
1. Call gets successfully connected.
2. Subscriber doesn't get charged (Billing confirmation). To be Completed

1. VoLTE UE-A dials it's own number


2. MTAS changes the R-URI to the VM number
3. The call breaks out to CS via the MGCF To be Completed
1.
4. VoLTE
The callUE-A dials the
between UE-AVM digits
and VM is established
2.
5. The callDTMF
VoLTE breaks out to
tones CS via thenavigates
successfully MGCF the VM online menu To be Completed
3.
1. The callUE-A
VoLTE between
in 3G UE-A
dials and VM digits
the VM is established
4.
2. VoLTE
The callDTMF
breakstones successfully
out to CS via thenavigates
MGCF the VM online menu To be Completed
3.
1. VoLTE UE-A dials the VM digits established
The call between UE-A and VM is
4.
2. DTMF
The calltones successfully
breaks out to CS navigates the VM online menu
via the MGCF To be Completed
3. The call between UE-A and VM is established
4. VoLTE DTMF tones successfully navigates the VM online menu

Pass 0

Conditional Pass 0

Failed 0

Not Applicable 0

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 50 (402)

To be Completed 119

blocked 0

Total Test cases 119

wifi 31

3G 12

AAT 65

VNC 0

manual 0

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 51 (402)

Bluesky Witness Ericsson Test Date


Witness

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 52 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 53 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 54 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 55 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 56 (402)

total 0

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 57 (402)

Comments wifi 3G AAT

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 58 (402)

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 59 (402)

x x

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 60 (402)

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 61 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 62 (402)

VNC manual

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 63 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 64 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 65 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_VoLTE/VoWiFi Test Object List 66 (402)

Date: 2018-02-09
Prepared: LMIESN Edmund Sheridan
Sheet: VoLTE-VoWiFi E2E Site2 _x000D_Rev: PA1
Ericsson Internal
Supplementary Service
Test Case Information
Priority
TOL Ref. Test Object Name /
Level Description / Objective
TC Ref. Test Case Title
(P1/P2)

TC-SITE1-E2E-SCC-01 CFU P1 *21*PhoneNumber# enable CFU, #21#


disable CFU

*67*PhoneNumber# enables CFB, #67#


TC-SITE1-E2E-SCC-02 CFB P1
disable CFB

*61*PhoneNumber# enables CFNA, #61#


TC-SITE1-E2E-SCC-03 CFNA - Call Forwarding No Answer P1
disable CFNA

TC-SITE1-E2E-SCC-04 CW - Call Waiting P1 *43# Activates, #43# Deactivates

*35*code# Activates, #35*code#


TC-SITE1-E2E-SCC-05 Bar all incomming calls P1
Deactivates
TC-SITE1-E2E-SCC-06 Bar all outgoing international calls P1 *331*code# Activate, #331*code#
Deactivate

TC-SITE1-E2E-SCC-07 Bar all outgoing calls P1 *33*code# Activate, #33*code#


Deactivates

TC-SITE1-E2E-SCC-08 Temporary Caller ID suppression P1 *67PhoneNumber

TC-SITE1-E2E-SCC-09 Temporary Caller ID Allow P1 *82PhoneNumber (Must be provisioned


to block Call ID)
Supplementary Service Code (SSC) Dialing TOL using Toy Cell
est Case Information
< Pass Criteria

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CFU and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CFU and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *21*msisdn# to activate CFU service.
3. On UE-A, dial #21# to Disable CFU.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CFB and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CFB and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *67*msisdn# to activate CFB service.
3. On UE-A, dial #67# to Disable CFB.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CFNA and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CFNA and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *61*msisdn# to activate CFNA service.
3. On UE-A, dial #61# to Disable CFNA.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CAW and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CAW and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *43# to activate CAW service.
3. On UE-A, dial #43# to Disable CAW.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate BAIC and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate BAIC and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *35*psw# to activate BAIC service.
3. On UE-A, dial #35*psw# to Disable BAIC.
1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate BOIC and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate BOIC and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *331*psw# to activate BOIC service.
3. On UE-A, dial #331*psw# to Disable BOIC.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate BAOC and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate BAOC and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *33*psw# to activate BAOC service.
3. On UE-A, dial #33*psw# to Disable BAOC.

On UE-B, received call from UE-A, without the msisdn of UE-A.


Pre-requisties:
1. UE-A is registered on IMS core
2. UE-A is capable of attaching to the service APN
3. UE-A has a Ut interface (ie Voice call Services)
4. UE-B has CLIP
Steps:
1. On UE-A, dial *67msisdn-UE-B.
3. On UE-B, received call from UE-A, without the msisdn of UE-
A.

On UE-B, received call from UE-A, with the msisdn of UE-A.

Pre-requisties:
1. UE-A is registered on IMS core
2. UE-A is capable of attaching to the service APN
3. UE-A has a Ut interface (ie Voice call Services)
4. UE-B has CLIR
Steps:
1. On UE-A, dial *82msisdn-UE-B.
3. On UE-B, received call from UE-A, with the msisdn of UE-A.

Pass
Pass with Comment
Failed
Not Applicable
To be Completed
Blocked
Total Test Cases
wifi
3G
AAT
VNC
manual
Toy Cell
Tracking
Result (Futon Device)
Bluesky Witness
Ericsson Witness Date Comment wifi 3G

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.
To be Completed No UE supporting this feature, all
going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

0 0
0 0
0 0
0 0
9 total 0
0
9
0
0
0
0
0
AAT VNC manual
Supplementary Service
Test Case Information
Priority
TOL Ref. Test Object Name /
Level Description / Objective
TC Ref. Test Case Title
(P1/P2)

TC-SITE2-E2E-SCC-01 CFU P1 *21*PhoneNumber# enable CFU, #21#


disable CFU

*67*PhoneNumber# enables CFB, #67#


TC-SITE2-E2E-SCC-02 CFB P1
disable CFB

*61*PhoneNumber# enables CFNA, #61#


TC-SITE2-E2E-SCC-03 CFNA - Call Forwarding No Answer P1
disable CFNA

TC-SITE2-E2E-SCC-04 CW - Call Waiting P1 *43# Activates, #43# Deactivates

*35*code# Activates, #35*code#


TC-SITE2-E2E-SCC-05 Bar all incomming calls P1
Deactivates
TC-SITE2-E2E-SCC-06 Bar all outgoing international calls P1 *331*code# Activate, #331*code#
Deactivate

TC-SITE2-E2E-SCC-07 Bar all outgoing calls P1 *33*code# Activate, #33*code#


Deactivates

TC-SITE2-E2E-SCC-08 Temporary Caller ID suppression P1 *67PhoneNumber

TC-SITE2-E2E-SCC-09 Temporary Caller ID Allow P1 *82PhoneNumber (Must be provisioned


to block Call ID)
Supplementary Service Code (SSC) Dialing TOL using Toy Cell
est Case Information
< Pass Criteria

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CFU and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CFU and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *21*msisdn# to activate CFU service.
3. On UE-A, dial #21# to Disable CFU.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CFB and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CFB and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *67*msisdn# to activate CFB service.
3. On UE-A, dial #67# to Disable CFB.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CFNA and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CFNA and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *61*msisdn# to activate CFNA service.
3. On UE-A, dial #61# to Disable CFNA.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate CAW and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate CAW and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *43# to activate CAW service.
3. On UE-A, dial #43# to Disable CAW.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate BAIC and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate BAIC and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *35*psw# to activate BAIC service.
3. On UE-A, dial #35*psw# to Disable BAIC.
1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate BOIC and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate BOIC and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *331*psw# to activate BOIC service.
3. On UE-A, dial #331*psw# to Disable BOIC.

1. On UE-A, open it's Call forwarding menu under the Voice Call
Pre-requisties: services and interrogate BAOC and verify it's activated.
1. UE-A is registered on IMS core 2. On UE-A, open it's Call forwarding menu under the Voice Call
2. UE-A is capable of attaching to the service APN services and interrogate BAOC and verify it's de-activated.
3. UE-A has a Ut interface (ie Voice call Services)

Steps:
1. On UE-A, dial *33*psw# to activate BAOC service.
3. On UE-A, dial #33*psw# to Disable BAOC.

On UE-B, received call from UE-A, without the msisdn of UE-A.


Pre-requisties:
1. UE-A is registered on IMS core
2. UE-A is capable of attaching to the service APN
3. UE-A has a Ut interface (ie Voice call Services)
4. UE-B has CLIP
Steps:
1. On UE-A, dial *67msisdn-UE-B.
3. On UE-B, received call from UE-A, without the msisdn of UE-
A.

On UE-B, received call from UE-A, with the msisdn of UE-A.

Pre-requisties:
1. UE-A is registered on IMS core
2. UE-A is capable of attaching to the service APN
3. UE-A has a Ut interface (ie Voice call Services)
4. UE-B has CLIR
Steps:
1. On UE-A, dial *82msisdn-UE-B.
3. On UE-B, received call from UE-A, with the msisdn of UE-A.

Pass
Pass with Comment
Failed
Not Applicable
To be Completed
Blocked
Total Test Cases
wifi
3G
AAT
VNC
manual
Toy Cell
Tracking
Result (Futon Device)
Bluesky Witness
Ericsson Witness Date Comment wifi 3G

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.
To be Completed No UE supporting this feature, all
going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

To be Completed No UE supporting this feature, all


going through Ut interface.

0 0
0 0
0 0
0 0
9 total 0
0
9
0
0
0
0
0
AAT VNC manual
Test Case Inform
Priority
TOL Ref. Test Object Name /
Level
TC Ref. Test Case Title
(P1/P2)
TC-SITE1-E2E-3G-01 Authentication

TC-SITE1-E2E-3G-01.01 UE Register with IMSI in AUC P1

TC-SITE1-E2E-3G-01.02 UE with Unregister IMSI in AUC P1

TC-SITE1-E2E-3G-01.03 Roaming Restriction tests (RSA Roaming P1


Service Area tests)

TC-SITE1-E2E-3G-02 Location Update

TC-SITE1-E2E-3G-02.01 Location Updating P1

TC-SITE1-E2E-3G-02.02 Subscriber Location Reset P1

TC-SITE1-E2E-3G-02.03 UE Purge from MSC P1


TC-SITE1-E2E-3G-02.04 GPRS Attach P1

TC-SITE1-E2E-3G-03 Call Handling

TC-SITE1-E2E-3G-03.01 Mobile Originated Call - UE-A in CS, UE-B P1


in CS

TC-SITE1-E2E-3G-03.02 Mobile Originated Call - UE-A in CS, UE-B P1


in LTE

TC-SITE1-E2E-3G-03.03 Mobile Originated Call - UE-A in CS, UE-B P1


in WiFi

TC-SITE1-E2E-3G-03.04 Mobile Originated Call - UE-A in CS, UE-B P1


in PSTN (SIP NNI)

Mobile Originated Call - UE-A in CS, UE-B


TC-SITE1-E2E-3G-03.05 in PSTN (SIP NNI) - Toll-Free 0800 P1

Mobile Originated Call - UE-A in CS, UE-B


TC-SITE1-E2E-3G-03.06 is 911 PSAP (Emergency Call) P1

Mobile Terminating Call - UE-A in LTE, UE-


TC-SITE1-E2E-3G-03.07 B in CS P1

Mobile Terminating Call - UE-A in WiFi,


TC-SITE1-E2E-3G-03.08 UE-B in CS P1
Mobile Terminating Call - UE-A is PSTN-
TC-SITE1-E2E-3G-03.09 NNI, UE-B in CS P1

SMS Mobile Originated - UE-A in CS, UE-B


TC-SITE1-E2E-3G-03.10 in CS P1

SMS Mobile Originated - UE-A in CS, UE-B


TC-SITE1-E2E-3G-03.11 in LTE P1

TC-SITE1-E2E-3G-03.12 SMS Mobile Originated - UE-A in CS, UE-B P1


in WiFi

TC-SITE1-E2E-3G-03.13 SMS Mobile Terminating - UE-A in LTE, P1


UE-B in CS

TC-SITE1-E2E-3G-03.14 SMS Mobile Terminating - UE-A in WiFi, P1


UE-B in CS

TC-SITE1-E2E-3G-04 Supplementary Services

TC-SITE1-E2E-3G-04.01 Barring of Incoming Call (BAIC) P1

TC-SITE1-E2E-3G-04.02 Barring of Outgoing Call (BAOC) P1


TC-SITE1-E2E-3G-04.03 Call Line Identification Presentation P1

TC-SITE1-E2E-3G-04.04 Call Line Identification Restriction P1

TC-SITE1-E2E-3G-04.05 Call Forwarding Unconditional (CFU) P1

TC-SITE1-E2E-3G-04.06 Call Forwarding On Busy (CFB) P1

Call Forwarding On Not Reachable


TC-SITE1-E2E-3G-04.07 (CFNRC) P1

TC-SITE1-E2E-3G-04.08 Call Forwarding On No Reply (CFNRY) P1


TC-SITE1-E2E-3G-04.09 Call Waiting (CW) and Call Hold(CH) P1

TC-SITE1-E2E-3G-04.10 Multi Party Call (MPTY) P1


UMTS End to End TOL using T
Test Case Information
Description / Objective

To Verify the subscriber can be connected in the HLR and


location update attempt is successful with the IMSI is defined in
the AUC.

To Verify the subscriber cannot be connected in the HLR and


location update attempt is rejected if IMSI is not defined in the
AUC.

To verify user can't be location updated in forigen network.

Make a Location Update from the UE

The location data is updated in the Centralized User Database


(CUDB) and the cancellation procedure towards the Visitor
Location Register (VLR)

To verify that an individual UDC subscriber can be ‘Purged’


from the MSC by HLR-FE individual GT and the HLR-FE is
notified and the CUDB is updated accordingly.
Power on the MS, check MS status in SGSN

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully receive MT call in network

To verify user can successfully receive MT call in network


To verify user can successfully receive MT call in network

To verify user can successfully send SMS in network

To verify user can successfully send SMS in network

To verify user can successfully send SMS in network

To verify user can successfully receive SMS in network

To verify user can successfully receive SMS in network

To verify user can successfully register/invoke/de-register BAIC


service in network.

To verify user can successfully register/invoke/de-register BAIC


service in network.
To verify user can successfully register/invoke/de-register CLIP
service in network

To verify user can successfully register/invoke/de-register CLIR


service in network

To verify user can successfully register/invoke/de-register CFU


service in network

To verify user can successfully register/invoke/de-register CFB


service in network

To verify user can successfully register/invoke/de-register


CFNRc service in network

To verify user can successfully register/invoke/de-register CFNR


service in network
To verify user can successfully register/invoke/de-register CAW
service in network

To verify user can successfully register/invoke/de-register


MPTY service in network
UMTS End to End TOL using Toy Cell
mation
Action: Make sure UE has IMSI defined in AUC and HLR via PG
MML. Steps Pass Criteria
PG MML- AGSUP:IMSI=<imsi>;
PG MML- HGSDP:IMSI=<imsi>;
Result: Subscriber AUC and HLR Data has been print.
Action: Make sure UE has IMSI defined in AUC and HLR via PG
MML.
Action: Turn the UE off.
PG MML-
Action: FromAGSUP:IMSI=<imsi>;
MSC, purge the UE from the VLR
PG
MSCMML-
MML-HGSDP:IMSI=<imsi>;
mgsre:imsi=<imsi>;
Result: UE be able to register on network
Result: Subscriber
Validate theAUCVLRand HLR
entry Data
has beenhasremoved
been print.
MSC MML- mgslp:imsi=<imsi>,all;
Action:
Example: Turn the UE off.
Action: From MSC, purge the UE from the VLR
<mgslp:imsi=310450000790126,all;
MSC MTMML- mgsre:imsi=<imsi>;
MOBILE SUBSCRIBER LIST
Result: Validate the VLR entry has been removed
MSC SUBSCRIBER
MML- mgslp:imsi=<imsi>,all;
IDENTITY
Example:
IMSI MSTAT MSISDN CAT
<mgslp:imsi=310450000790126,all;
310450000790126 NOTREG UE got rejected when registering on
MT MOBILE SUBSCRIBER LIST network
END
SUBSCRIBER IDENTITY
IMSI MSTAT MSISDN CAT
310450000790126
Action: Delete subscriberNOTREGdata from CUDB using PG MML.
PG MML- AGSUE:IMSI=<imsi>;
END
Action: Make
Result: Make sure
Action: Subscriber UE
testhas
sure Data IMSI defined
is removed
UE has RSA frominAUC.
service AUC and HLR via PG
in CUDB
MML.
Action: Turn the UE on.
PG MML- HGSDP:IMSI=<imsi>; UE should not be able to make call in
PG MML-
Result:
Action: HGSDP:IMSI=<imsi>;
Location
Attemp update update
location attemptinisforigen
rejectedVLRby network. forigen VLR
Action:
Result:
Action: Turn
Turn the
Subscriber
the UE
UE on.
AUC
off.and HLR Data has been print.
Result:
Result: Location updateisinperformed
forigen VLR failed.
Action: Authentication
Define subscriber data in theand AUCthe UE Location
update
Action:
PG MML- to thethe
Turn network.
UE off.
Action: From MSC, purge the UE from the VLR
AGSUI:IMSI=imsi,EKI=eki,KIND=kind,FSETIND=fsetind,A4IND=a4
MSC
ind; MML- mgsre:imsi=<imsi>;
Result: Validate the
Result: Subscriber VLRisentry
data hasinbeen
defined AUC.removed
MSC MML-
Action: Turnmgslp:imsi=<imsi>,all;
the UE on.
Example:
Result:
Action1:Authentication
Ensure the UEisuser performed
subscriberanddata
the in
UECUDB
Location
via PG CLI.
update
PG <mgslp:imsi=310450000790126,all;
MML-to the network.
HGSDP:IMSI=<imsi>; UE be able to register on network
MT Subscriber
Result1: MOBILE SUBSCRIBER LIST The VLR Address and MSC
data be printout,
Number is set for the corresponding VLR and MSC.
SUBSCRIBER
Action2: Check theIDENTITY
UE user register on 3G MSC status.
IMSI
MGSLP:IMSI=<imsi>; MSTAT MSISDN CAT
310450000790126 NOTREG
Result2: The UE has register 3G MSC by check the MSTAT
should be REG.
ENDTo perform the reset message to VLR and SGSN by set
Action3:
the subscriber location data to unknown via PG CLI.
PG MML- HGSLR:IMSI=<imsi>; VLR and SGSN number is unknown for
Action:
Result3:Turn
The the UE on.
location data is updated in the CUDB and the
Result: Authentication theistowards
performed and the UE UE data printout
Action1: Make sure
cancellation procedure HLR-FE OWN
the VLRGT and theLocation
address has defined
SGSN where
update
on
theHLR-FEto the
mobile network.is currently located is initiated.
node.
subscriber
>Action4:
MML -aCheck the VLR and SGSN status of UE user in CUDB via
HECAP;
PG CLI.
Result1:
PG MML-The HLR-FE address will be show on .
HGSDP:IMSI=<imsi>;
Action2: To survey
Result4: VLR and SGSNall registration subscribers
number is unknown forinUE
3Gdata
MSC/VLR.
MGSVP;
printout.
Result2:
Action5: The amount
Check the UEofuser
registration
register onsubscribers belong to HLR-
3G MSC status.
address will be<imsi>;
MGSLP:IMSI= show .
Action3: Execute
Result5: The UE no toregister
PURGE user3G MSCfromby2G/3G
check MSC/VLR
the MSTAT byshould
HLR-
FE
be GT.
NOTREG Individual Subscribers purged
MGSRE:HLRADDR=<hlraddr>;
Action4: Check the amount under HLR-FE GT.
MGSVP;
Result4: The amount of registration subscriber will decrease
per 5 minis.
Action5: Check the UE user subscriber data in CUDB via PG
MML.
PG MML- HGSDP:IMSI=<imsi>;
Result5: The subscriber data should be print, the result is MS
PURGED IN VLR.
Action: Make sure test UE is not register in SGSN yet.
Action: Make sure the subscription of test UE contains APN and
NAM in CUDB via PG MML.
MS successfully attached to the
PG MML- HGSDP:IMSI=<imsi>; network. From SGSN can see the MS is
Action: EDA performs a GET on the HLR portion of the UE's
provisioning. in PMM-Connected or PMM-idle
Action: Turn on test UE state.
Action: Check UE record in 2G/3G SGSN.
Result: User successful registered in PS network

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MT call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MT call as per test scenario.
Action1: Make sure test user has MO service in HLR.
PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MT call as per test scenario.

Action: Make sure test UE has SMS MO service in CUDB


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR SMS should be successfully sent
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS from test UE

Action: Make sure test UE has SMS MO service in CUDB


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR SMS should be successfully sent
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS from test UE

Action: Make sure test UE has SMS MO service in CUDB


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR SMS should be successfully sent
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS from test UE

Action: Make sure test UE has SMS MT service in CUDB.


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR. SMS should be successfully received
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS to test UE.

Action: Make sure test UE has SMS MT service in CUDB.


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR. SMS should be successfully received
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS to test UE.

Action: Make sure test UE has BAIC (SOCB/BAIC/PWD) service


in CUDB
PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate BAIC service MT call should be rejected
Action: Make MT call to test UE
Result: MT call should be rejected
Action: Use test UE to de-activate BAIC service
Action: Make MT call to test UE
Action: Make sure test UE has BAOC (SOCB/BAOC/PWD) service
in CUDB
PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>; MO call should be rejected
Action: Use test UE to activate BAOC service
Action: Make MO call from test UE
Result: MO call should be rejected
Action: Use test UE to de-activate BAOC service
Action: Make MO call from test UE
Action: Make sure test UE has CLIP service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CLIP-1;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=SOCLIP-1; Calling line Identification presentation
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Make MT call to test UE (has CLIP service)

Action: Make sure test UE has CLIR(CLIR-1/SOCLIR-2) service in


CUDB, if not, provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CLIR-1;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=SOCLIR-2; Calling line Identification restriction
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Make MO call from test UE with prefix #31#

Action: Make sure test UE has CFU service in CUDB, if not,


provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC:MSISDN=<msisdn>,SUD= CFU-1;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>; Call forward to CFU number
Action: Use test UE to activate CFU service
Action: Make MT call to test UE(has CFU service)
Result: Call forward to CFU number
Action: Use test UE to De-activate CFU service
Action: Make MT call to test UE
Action: Make sure test UE has CFB service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD= CFB-1;
Action: Make sure test user registered in 3G MSC/VLR Call forward to CFB number
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate CFB service
Action: Make MT call to test UE (has CFB service)
Action: Test UE rejects the call
Action: Make sure test UE has CFNRC service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CFNRC-1;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate CFNRC service Call forward to CFNRC number
Action: Turn off test UE (has CFNRC service)
Action: Make MT call to test UE (has CFNRC service) Action:
Turn on test UE (has CFNRC service)
Action: Use test UE to de-activate CFNRC service
Action: Restore original setting to test UE in CUDB.
Action: Make sure test UE has CFNRY service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CFNRY-1;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate CFNRY service Call forward to CFNRY number
Action: Make MT call to test UE (has CFNRY service)
Action: Test UE not answer the call
Result: Call forward to CFNRY number
Action: Use test UE to de-activate CFNRY service
Action: Restore original setting to test UE in CUDB.
Action: Make sure 3 test users registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Make sure test UE-A has CAW and Hold service in
CUDB, if not, provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CAW-1; UE receive the notification of the
PG MML- HGSDC: MSISDN=<msisdn>,SUD=HOLD-1;
Action: Use test UE to activate CAW and HOLD service waiting call & Same UE can able to
Action: Make a call from UE-B to UE- A while UE-A is making a HOLD the call also.
call to UE-C.
 Make MT call from UE-A (CAW/HOLD) to UE-C and
establish this call.
 Use UE-B make MT Call to UE-A during communication
(UE-A  UE-C)
Action: Make sure test UE has MPTY service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=MPTY-1;
Action: Make sure 3 test users registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>; Subscriber can able to attend multiple
Action: Make MT call to test UE (has MPTY service) calls(Conference)
Action: Test UE answer the call
Action: Test UE HOLD the call via handset
Action: Test UE makes call to the 3rd. UE
Action: The 3rd. UE answer the call
Action: Test UE joins 3 parties call via handset

Pass
Pass with Comment
Failed
Not Applicable
To be Completed
blocked
Total Test Cases
wifi
3G
AAT
VNC
manual
Tracking
Result (Futon Device) Bluesky Witness Ericsson Witness Date

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

0 0
0 0
0 0
0 0
31 total 0
0
31
0
31
0
0
0
Comment wifi 3G AAT VNC manual

forigen VLR access needed. x


 

x
x
 

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from PSTN to 3G x

called from PSTN to 3G x


called from PSTN to 3G x

from 7009 to 7012 x

from 7009 to 7012 x

from 7009 to 7012 x

from 7009 to 7012 x

from 7009 to 7012 x

BAIC activate only in suscriber. x

BAOC activate only in suscriber. x


3G x

3G x

3G x

3G x

3G x

3G/ with MRD 105 65-0209/66064.


due to Huawei sent A-law from MSC. x
3G x

3G x
Test Case Inform
Priority
TOL Ref. Test Object Name /
Level
TC Ref. Test Case Title
(P1/P2)
TC-SITE2-E2E-3G-01 Authentication

TC-SITE2-E2E-3G-01.01 UE Register with IMSI in AUC P1

TC-SITE2-E2E-3G-01.02 UE with Unregister IMSI in AUC P1

TC-SITE2-E2E-3G-01.03 Roaming Restriction tests (RSA Roaming P1


Service Area tests)

TC-SITE2-E2E-3G-02 Location Update

TC-SITE2-E2E-3G-02.01 Location Updating P1

TC-SITE2-E2E-3G-02.02 Subscriber Location Reset P1

TC-SITE2-E2E-3G-02.03 UE Purge from MSC P1


TC-SITE2-E2E-3G-02.04 GPRS Attach P1

TC-SITE2-E2E-3G-03 Call Handling

TC-SITE2-E2E-3G-03.01 Mobile Originated Call - UE-A in CS, UE-B P1


in CS

TC-SITE2-E2E-3G-03.02 Mobile Originated Call - UE-A in CS, UE-B P1


in LTE

TC-SITE2-E2E-3G-03.03 Mobile Originated Call - UE-A in CS, UE-B P1


in WiFi

TC-SITE2-E2E-3G-03.04 Mobile Originated Call - UE-A in CS, UE-B P1


in PSTN (SIP NNI)

Mobile Originated Call - UE-A in CS, UE-B


TC-SITE2-E2E-3G-03.05 in PSTN (SIP NNI) - Toll-Free 0800 P1

Mobile Originated Call - UE-A in CS, UE-B


TC-SITE2-E2E-3G-03.06 is 911 PSAP (Emergency Call) P1

Mobile Terminating Call - UE-A in LTE, UE-


TC-SITE2-E2E-3G-03.07 B in CS P1

Mobile Terminating Call - UE-A in WiFi,


TC-SITE2-E2E-3G-03.08 UE-B in CS P1
Mobile Terminating Call - UE-A is PSTN-
TC-SITE2-E2E-3G-03.09 NNI, UE-B in CS P1

SMS Mobile Originated - UE-A in CS, UE-B


TC-SITE2-E2E-3G-03.10 in CS P1

SMS Mobile Originated - UE-A in CS, UE-B


TC-SITE2-E2E-3G-03.11 in LTE P1

TC-SITE2-E2E-3G-03.12 SMS Mobile Originated - UE-A in CS, UE-B P1


in WiFi

TC-SITE2-E2E-3G-03.13 SMS Mobile Terminating - UE-A in LTE, P1


UE-B in CS

TC-SITE2-E2E-3G-03.14 SMS Mobile Terminating - UE-A in WiFi, P1


UE-B in CS

TC-SITE2-E2E-3G-04 Supplementary Services

TC-SITE2-E2E-3G-04.01 Barring of Incoming Call (BAIC) P1

TC-SITE2-E2E-3G-04.02 Barring of Outgoing Call (BAOC) P1


TC-SITE2-E2E-3G-04.03 Call Line Identification Presentation P1

TC-SITE2-E2E-3G-04.04 Call Line Identification Restriction P1

TC-SITE2-E2E-3G-04.05 Call Forwarding Unconditional (CFU) P1

TC-SITE2-E2E-3G-04.06 Call Forwarding On Busy (CFB) P1

Call Forwarding On Not Reachable


TC-SITE2-E2E-3G-04.07 (CFNRC) P1

TC-SITE2-E2E-3G-04.08 Call Forwarding On No Reply (CFNRY) P1


TC-SITE2-E2E-3G-04.09 Call Waiting (CW) and Call Hold(CH) P1

TC-SITE2-E2E-3G-04.10 Multi Party Call (MPTY) P1


UMTS End to End TOL using T
Test Case Information
Description / Objective

To Verify the subscriber can be connected in the HLR and


location update attempt is successful with the IMSI is defined in
the AUC.

To Verify the subscriber cannot be connected in the HLR and


location update attempt is rejected if IMSI is not defined in the
AUC.

To verify user can't be location updated in forigen network.

Make a Location Update from the UE

The location data is updated in the Centralized User Database


(CUDB) and the cancellation procedure towards the Visitor
Location Register (VLR)

To verify that an individual UDC subscriber can be ‘Purged’


from the MSC by HLR-FE individual GT and the HLR-FE is
notified and the CUDB is updated accordingly.
Power on the MS, check MS status in SGSN

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully make MO call in network

To verify user can successfully receive MT call in network

To verify user can successfully receive MT call in network


To verify user can successfully receive MT call in network

To verify user can successfully send SMS in network

To verify user can successfully send SMS in network

To verify user can successfully send SMS in network

To verify user can successfully receive SMS in network

To verify user can successfully receive SMS in network

To verify user can successfully register/invoke/de-register BAIC


service in network.

To verify user can successfully register/invoke/de-register BAIC


service in network.
To verify user can successfully register/invoke/de-register CLIP
service in network

To verify user can successfully register/invoke/de-register CLIR


service in network

To verify user can successfully register/invoke/de-register CFU


service in network

To verify user can successfully register/invoke/de-register CFB


service in network

To verify user can successfully register/invoke/de-register


CFNRc service in network

To verify user can successfully register/invoke/de-register CFNR


service in network
To verify user can successfully register/invoke/de-register CAW
service in network

To verify user can successfully register/invoke/de-register


MPTY service in network
UMTS End to End TOL using Toy Cell
mation
Action: Make sure UE has IMSI defined in AUC and HLR via PG
MML. Steps Pass Criteria
PG MML- AGSUP:IMSI=<imsi>;
PG MML- HGSDP:IMSI=<imsi>;
Result: Subscriber AUC and HLR Data has been print.
Action: Make sure UE has IMSI defined in AUC and HLR via PG
MML.
Action: Turn the UE off.
PG MML-
Action: FromAGSUP:IMSI=<imsi>;
MSC, purge the UE from the VLR
PG
MSCMML-
MML-HGSDP:IMSI=<imsi>;
mgsre:imsi=<imsi>;
Result: UE be able to register on network
Result: Subscriber
Validate theAUCVLRand HLR
entry Data
has beenhasremoved
been print.
MSC MML- mgslp:imsi=<imsi>,all;
Action:
Example: Turn the UE off.
Action: From MSC, purge the UE from the VLR
<mgslp:imsi=310450000790126,all;
MSC MTMML- mgsre:imsi=<imsi>;
MOBILE SUBSCRIBER LIST
Result: Validate the VLR entry has been removed
MSC SUBSCRIBER
MML- mgslp:imsi=<imsi>,all;
IDENTITY
Example:
IMSI MSTAT MSISDN CAT
<mgslp:imsi=310450000790126,all;
310450000790126 NOTREG UE got rejected when registering on
MT MOBILE SUBSCRIBER LIST network
END
SUBSCRIBER IDENTITY
IMSI MSTAT MSISDN CAT
310450000790126
Action: Delete subscriberNOTREGdata from CUDB using PG MML.
PG MML- AGSUE:IMSI=<imsi>;
END
Action: Make
Result: Make sure
Action: Subscriber UE
testhas
sure Data IMSI defined
is removed
UE has RSA frominAUC.
service AUC and HLR via PG
in CUDB
MML.
Action: Turn the UE on.
PG MML- HGSDP:IMSI=<imsi>; UE should not be able to make call in
PG MML-
Result:
Action: HGSDP:IMSI=<imsi>;
Location
Attemp update update
location attemptinisforigen
rejectedVLRby network. forigen VLR
Action:
Result:
Action: Turn
Turn the
Subscriber
the UE
UE on.
AUC
off.and HLR Data has been print.
Result:
Result: Location updateisinperformed
forigen VLR failed.
Action: Authentication
Define subscriber data in theand AUCthe UE Location
update
Action:
PG MML- to thethe
Turn network.
UE off.
Action: From MSC, purge the UE from the VLR
AGSUI:IMSI=imsi,EKI=eki,KIND=kind,FSETIND=fsetind,A4IND=a4
MSC
ind; MML- mgsre:imsi=<imsi>;
Result: Validate the
Result: Subscriber VLRisentry
data hasinbeen
defined AUC.removed
MSC MML-
Action: Turnmgslp:imsi=<imsi>,all;
the UE on.
Example:
Result:
Action1:Authentication
Ensure the UEisuser performed
subscriberanddata
the in
UECUDB
Location
via PG CLI.
update
PG <mgslp:imsi=310450000790126,all;
MML-to the network.
HGSDP:IMSI=<imsi>; UE be able to register on network
MT Subscriber
Result1: MOBILE SUBSCRIBER LIST The VLR Address and MSC
data be printout,
Number is set for the corresponding VLR and MSC.
SUBSCRIBER
Action2: Check theIDENTITY
UE user register on 3G MSC status.
IMSI
MGSLP:IMSI=<imsi>; MSTAT MSISDN CAT
310450000790126 NOTREG
Result2: The UE has register 3G MSC by check the MSTAT
should be REG.
ENDTo perform the reset message to VLR and SGSN by set
Action3:
the subscriber location data to unknown via PG CLI.
PG MML- HGSLR:IMSI=<imsi>; VLR and SGSN number is unknown for
Action:
Result3:Turn
The the UE on.
location data is updated in the CUDB and the
Result: Authentication theistowards
performed and the UE UE data printout
Action1: Make sure
cancellation procedure HLR-FE OWN
the VLRGT and theLocation
address has defined
SGSN where
update
on
theHLR-FEto the
mobile network.is currently located is initiated.
node.
subscriber
>Action4:
MML -aCheck the VLR and SGSN status of UE user in CUDB via
HECAP;
PG CLI.
Result1:
PG MML-The HLR-FE address will be show on .
HGSDP:IMSI=<imsi>;
Action2: To survey
Result4: VLR and SGSNall registration subscribers
number is unknown forinUE
3Gdata
MSC/VLR.
MGSVP;
printout.
Result2:
Action5: The amount
Check the UEofuser
registration
register onsubscribers belong to HLR-
3G MSC status.
address will be<imsi>;
MGSLP:IMSI= show .
Action3: Execute
Result5: The UE no toregister
PURGE user3G MSCfromby2G/3G
check MSC/VLR
the MSTAT byshould
HLR-
FE
be GT.
NOTREG Individual Subscribers purged
MGSRE:HLRADDR=<hlraddr>;
Action4: Check the amount under HLR-FE GT.
MGSVP;
Result4: The amount of registration subscriber will decrease
per 5 minis.
Action5: Check the UE user subscriber data in CUDB via PG
MML.
PG MML- HGSDP:IMSI=<imsi>;
Result5: The subscriber data should be print, the result is MS
PURGED IN VLR.
Action: Make sure test UE is not register in SGSN yet.
Action: Make sure the subscription of test UE contains APN and
NAM in CUDB via PG MML.
MS successfully attached to the
PG MML- HGSDP:IMSI=<imsi>; network. From SGSN can see the MS is
Action: EDA performs a GET on the HLR portion of the UE's
provisioning. in PMM-Connected or PMM-idle
Action: Turn on test UE state.
Action: Check UE record in 2G/3G SGSN.
Result: User successful registered in PS network

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MO call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MT call as per test scenario.

Action1: Make sure test user has MO service in HLR.


PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MT call as per test scenario.
Action1: Make sure test user has MO service in HLR.
PG MML- HGSDP:IMSI=<imsi>; Call is successfully completed.
Action2: Make sure test user registered in 3G MSC/VLR. IMS is the anchoring point as
MSC - MGSLP:IMSI=<imsi>; observed in pcap traces.
Action3: Use test UE to make MT call as per test scenario.

Action: Make sure test UE has SMS MO service in CUDB


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR SMS should be successfully sent
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS from test UE

Action: Make sure test UE has SMS MO service in CUDB


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR SMS should be successfully sent
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS from test UE

Action: Make sure test UE has SMS MO service in CUDB


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR SMS should be successfully sent
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS from test UE

Action: Make sure test UE has SMS MT service in CUDB.


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR. SMS should be successfully received
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS to test UE.

Action: Make sure test UE has SMS MT service in CUDB.


PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR. SMS should be successfully received
MSC - MGSLP:IMSI=<imsi>;
Action: Send a test SMS to test UE.

Action: Make sure test UE has BAIC (SOCB/BAIC/PWD) service


in CUDB
PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate BAIC service MT call should be rejected
Action: Make MT call to test UE
Result: MT call should be rejected
Action: Use test UE to de-activate BAIC service
Action: Make MT call to test UE
Action: Make sure test UE has BAOC (SOCB/BAOC/PWD) service
in CUDB
PG MML- HGSDP:IMSI=<imsi>;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>; MO call should be rejected
Action: Use test UE to activate BAOC service
Action: Make MO call from test UE
Result: MO call should be rejected
Action: Use test UE to de-activate BAOC service
Action: Make MO call from test UE
Action: Make sure test UE has CLIP service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CLIP-1;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=SOCLIP-1; Calling line Identification presentation
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Make MT call to test UE (has CLIP service)

Action: Make sure test UE has CLIR(CLIR-1/SOCLIR-2) service in


CUDB, if not, provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CLIR-1;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=SOCLIR-2; Calling line Identification restriction
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Make MO call from test UE with prefix #31#

Action: Make sure test UE has CFU service in CUDB, if not,


provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC:MSISDN=<msisdn>,SUD= CFU-1;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>; Call forward to CFU number
Action: Use test UE to activate CFU service
Action: Make MT call to test UE(has CFU service)
Result: Call forward to CFU number
Action: Use test UE to De-activate CFU service
Action: Make MT call to test UE
Action: Make sure test UE has CFB service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD= CFB-1;
Action: Make sure test user registered in 3G MSC/VLR Call forward to CFB number
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate CFB service
Action: Make MT call to test UE (has CFB service)
Action: Test UE rejects the call
Action: Make sure test UE has CFNRC service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CFNRC-1;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate CFNRC service Call forward to CFNRC number
Action: Turn off test UE (has CFNRC service)
Action: Make MT call to test UE (has CFNRC service) Action:
Turn on test UE (has CFNRC service)
Action: Use test UE to de-activate CFNRC service
Action: Restore original setting to test UE in CUDB.
Action: Make sure test UE has CFNRY service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CFNRY-1;
Action: Make sure test user registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Use test UE to activate CFNRY service Call forward to CFNRY number
Action: Make MT call to test UE (has CFNRY service)
Action: Test UE not answer the call
Result: Call forward to CFNRY number
Action: Use test UE to de-activate CFNRY service
Action: Restore original setting to test UE in CUDB.
Action: Make sure 3 test users registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>;
Action: Make sure test UE-A has CAW and Hold service in
CUDB, if not, provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=CAW-1; UE receive the notification of the
PG MML- HGSDC: MSISDN=<msisdn>,SUD=HOLD-1;
Action: Use test UE to activate CAW and HOLD service waiting call & Same UE can able to
Action: Make a call from UE-B to UE- A while UE-A is making a HOLD the call also.
call to UE-C.
 Make MT call from UE-A (CAW/HOLD) to UE-C and
establish this call.
 Use UE-B make MT Call to UE-A during communication
(UE-A  UE-C)
Action: Make sure test UE has MPTY service in CUDB, if not,
provide to test UE via PG MML.
PG MML- HGSDP:IMSI=<imsi>;
PG MML- HGSDC: MSISDN=<msisdn>,SUD=MPTY-1;
Action: Make sure 3 test users registered in 3G MSC/VLR
MSC - MGSLP:IMSI=<imsi>; Subscriber can able to attend multiple
Action: Make MT call to test UE (has MPTY service) calls(Conference)
Action: Test UE answer the call
Action: Test UE HOLD the call via handset
Action: Test UE makes call to the 3rd. UE
Action: The 3rd. UE answer the call
Action: Test UE joins 3 parties call via handset

Pass
Pass with Comment
Failed
Not Applicable
To be Completed
blocked
Total Test Cases
wifi
3G
AAT
VNC
manual
Tracking
Result (Futon Device) Bluesky Witness Ericsson Witness Date

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

0 0
0 0
0 0
0 0
31 total 0
0
31
0
31
0
0
0
Comment wifi 3G AAT VNC manual

forigen VLR access needed. x


 

x
x
 

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from 3G to PSTN x

called from PSTN to 3G x

called from PSTN to 3G x


called from PSTN to 3G x

from 7009 to 7012 x

from 7009 to 7012 x

from 7009 to 7012 x

from 7009 to 7012 x

from 7009 to 7012 x

BAIC activate only in suscriber. x

BAOC activate only in suscriber. x


3G x

3G x

3G x

3G x

3G x

3G/ with MRD 105 65-0209/66064.


due to Huawei sent A-law from MSC. x
3G x

3G x
Test C
TOL Ref./TC Ref. Test Object Name / Test Case Title

TO-SITE1-E2E-01 E2E System Test Cases

TC-SITE1-E2E-01.01 Attach with IMSI and Default Bearer Activation

TC-SITE1-E2E-01.02 Attach with GUTI and Default Bearer Activation


TC-SITE1-E2E-01.03 UE initiated Detach

TC-SITE1-E2E-01.04 MME initiated Detach


TC-SITE1-E2E-01.05 HSS Initiated Detach

TC-SITE1-E2E-01.06 PGW Initiated Bearer Deactivation


TC-SITE1-E2E-01.07 Periodic TAU

TC-SITE1-E2E-01.08 Unsuccessful Paging - UE Not Responding

TC-SITE1-E2E-01.09 IPv4 Address Allocation by PGW

TC-SITE1-E2E-01.10 IPv6 Address Allocation by PGW


TC-SITE1-E2E-01.11 Static IP Address Allocation

TC-SITE1-E2E-01.12 eNodeB Triggered S1 Release

TC-SITE1-E2E-01.13 Network Triggered Service Request (Paging)


TC-SITE1-E2E-01.14 UE Triggered Service Request

TC-SITE1-E2E-01.15 S/P/GW Selection using DNS

TC-SITE1-E2E-01.16 DSCP Mapping According to QCI

TC-SITE1-E2E-01.17 MME Pool Move


TC-SITE1-E2E-01.18 Inter-eNB Inter-TA S1 Based Handover (TAU)

TC-SITE1-E2E-01.19 inter-eNB inter-tracking area X2 based handover (TAU)

TC-SITE1-E2E-01.20 4G-MME-MM-Combined_Deatch

TC-SITE1-E2E-01.21 Generic-4G-MME-MM-Handover_4G_3G

TC-SITE1-E2E-01.22 Generic-4G-MME-MM-3G_LTE_3G_LTE_Handover_Intra
TC-SITE1-E2E-01.23 Generic-4G-MME-MM-3G_LTE_3G_LTE_Handover_Inter

TC-SITE1-E2E-01.24 Generic-4G-MME-4G_Testing-Internet_Browsing

TC-SITE1-E2E-01.25 Generic-4G-MME-CSF-Return_Data_Session_CSFB
TC-SITE1-E2E-01.26 Generic-4G-MME-VoLTE-Test_SRVCC

TC-SITE1-E2E-01.27 Generic-4G-MME-AT-CSFB_Idle_Mode

TC-SITE1-E2E-01.28 Generic-4G-MME-AT-CSFB_Active_Mode
TC-SITE1-E2E-01.29 Generic-4G-MME-VoLTE-IMS_Voice_Web_Browse

TC-SITE1-E2E-01.30 Generic-4G-EPG-APN-Additional_PDN

TC-SITE1-E2E-01.31 Generic-4G-EPG-APN-Shared_IP_Pool

TC-SITE1-E2E-01.32 Generic-4G-EPG-APN-3G_APN_Handling
TC-SITE1-E2E-01.33 Generic-4G-EPG-APN-4G_APN_Handling

TC-SITE1-E2E-01.34 Generic-4G-EPG-BCF-Verify_Service_Request_DL_UL

TC-SITE1-E2E-01.35 Generic-4G-EPG-Mobility_Volte-Idle_Mode_TAU

TC-SITE1-E2E-01.36 Generic-4G-EPG-BCF-UE_Initiate_All_PDN_Disconn

TC-SITE1-E2E-01.37 Generic-4G-EPG-BCF-Internet_PDN_Default_Bearer

TC-SITE1-E2E-01.38 Generic-4G-EPG-QOS-Default_Bearer_QCI_5
TC-SITE1-E2E-01.39 Generic-4G-EPG-QOS-Dedicated_Bearer_QCI_1

TC-SITE1-E2E-01.40 Generic-4G-EPG-PM-Verify_Internet_APN

TC-SITE1-E2E-01.41 Generic-4G-EPG-Diameter-Gx_Comm_PCRF_Attach
Packet Core End-to-End
Test Case Information
Description / Objective

Perform initial attach using IMSI

Perform attach using GUTI. This implies that the subscriber


was attached in the network previously and a GUTI was
alloced by the MME.
This test case will verify a UE initiated detach from state
ECM-CONNECTED by powering off the device.

This test case is to verify PUR/PUA (Purge UE


Request/Purge UE Ack) between the SGSN-MME and
HSS. The SGSN-MME uses PUR to inform the HSS that
the subscriber profile has been deleted. The HSS shall
respond with PUA with “diameter_success” and remove
MME info from the subscriber profile.
When the UE is in the ECM-CONNECTED state: This test
case is to verify CLR/CLA (Cancel Location
Request/Cancel Location Answer) messaging between the
MME and HSS. The HSS sends the CLR to inform the
MME that the subscriber profile in the MME is to be
deleted. The MME shall delete the subscriber profile and
respond with a CLA indicating success.

This test is to verify that the manual deletion of a subscriber


from the PGW results in the PDN connection being torn
down
After expiration of the periodic TAU timer, UE send TAU
request to network with cause set to periodic updating

Verify the unsuccessful paging due to no answer from UE.


In order to trigger the unsuccessful paging the UE is
powered off (removing battery).

Verify that the UE has been allocated an IP address from


the local APN pool

Verify that the UE has been allocated an IP address from


the local APN pool
Verify that the UE has been allocated a static IP address

The MME sends an Update Bearer Request message to


the SGW. This message can be triggered by an S1
Release Request message from the eNodeB due to user-
inactivity, for eample.

Verify the successful paging triggered by downlink data


notification.
Demonstrate the service request procedure initiated by an
UE in idle state.

Verify the MME queries iDNS for TAC/APN to SGW/PGW


IP address mapping

Thee purpose of this testcase is to verify that the DSCP


values on the traffic interfaces respects the QCI/DSCP
mapping as defined

This test case verifies that a subscriber or group of


subscribers can be seamlessly moved from one MME in
the pool to the other without traffic impact
To validate the S1 inter-eNB handovers

To validate the X2 inter-eNB handovers

To verify the combined detach procedure initiated by UE

PS Handover from an LTE Network to a UMTS Network

To verify intra access handover with active pdp for 3g to 4g


and vice-versa
To verify inter sgsn access handover with active pdp for 3g
to 4g and vice-versa

To verify 4G testing : Internet Browsing

Return to data session after CSFB


Test SRVCC

To verify CSFB in idle mode

To verify CSFB in active mode


Simultaneous use of IMS voice and web browsing

Initial+Additional PDN Conn on different APN (subscribed


APN=*)

address reuse in shared pool

3G APN Handling
4G APN Handling

Verify Service Request from UE (DL/UL).

Verify Idle Mode Tracking Area Update from UE

Verify UE initiated all PDN disconnect on LTE

Verify Internet PDN data communication on default bearer

Verify establishment of default bearer with QCI 5 with IMS


PDN
Verify establishment of dedicated bearer with QCI 1 during
voice call

Verify Internet APN

Verify Gx communication to PCRF during attach and


detach
Packet Core End-to-End Functional TOL using Toy Cel
ase Information
Steps

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

Result: The UE state in MME is EMM-REGISTERED ECM-


CONNECTED

4. Convert the collected UE trace files to pcap for verification of


the procedure in Wireshark
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is generated

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE state on MME and EPG
MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The UE state in MME is EMM-REGISTERED ECM-


CONNECTED

4. Convert the collected UE trace files to pcap for verification of


the procedure in Wireshark
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is generated


Action: Make sure test UE is registered in SGSN.
Action: Turn off test UE
Result: User successful deregistered from SGSN network
"0. If not already implemented, start a UE trace on the
MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

1. Verify the UE is registered in the MME

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

2. Trigger a detach from the MME


gsh delete_subscriber -imsi <imsi>

Result: UE is successfully detached from the network

3. Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The UE state in MME is EMM-DEREGISTERED


ECM-IDLE

4. Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is


generated"
"1. If not already implemented, start a UE trace on the
MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

2. Verify the UE is registered in the MME

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

3. Verify the HSS-EsmLocationState of the subscriber in


the HSS by opening the CM Browser from the HSS-ESM
Node Management toolbox, and checking the HSS-
EsmLocationState

Result: The subscriber’s HSS-EsmLocationState is


“LOCATED”

4. Trigger a detach from the HSS by opening the CM


Browser from the HSS-ESM Node Management toolbox,
and changing the subscriber’s HSS-EsmLocationState to
“UNKNOWN”
Result: UE is successfully detached from the network. HSS
sends a Cancel Location Request to the MME to delete the
subscriber’s record; MME confirms the record removal by
sending Cancel Location Answer to the HSS.

5. Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi
"1: Verify the UE state on MME and EPG.
MME --> gsh get_subscriber -imsi <imsi>
SGW/PGW --> ManagedElement=1,Epg=1,Sgw=1,userInfo
imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

2: Using the CLI, trigger a manual detach from the PGw.


ManagedElement=1,Epg=1,Pgw=1,ControlPlane=1,Sessio
n=1, terminateImsi <imsi>

3: Verify the UE state on MME and EPG again by above


commands."
"1:change the S1 Mobile Reachable Timer to 34 mins,
thereby setting the Periodic TAU timer (T3412) sent to the
UE to 30 mins.
gsh modify_s1_mme -s1 s1_mme -mrt 34
gsh check_config
gsh activate_config_pending
2:Verify the UE state on MME and EPG.
3:If the subscriber is registered in the MME, purge the
subscriber from the network and force the UE to reattach
gsh delete_subscriber -imsi <imsi> -dettype
reattach_required
4: Wait ~34 mins for the UE to execute the periodic TAU
procedure.
5:Convert the collected UE trace files to pcap for
verification of the procedure in Wireshark and View the
pcap file in Wireshark to verify the detach procedure.
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
6:Change the S1 Mobile Reachable Timer back to the
default of 58 mins, thereby setting the Periodic TAU timer
(T3412) sent to the UE to 54 mins."

1. Move the UE out of radio coverage or remove


battery(not detacched).
2.a initiate a down link data traffic from network to UE and
trigger a paging from MME to UE.
2.b make a call to this VoLTE subscriber and trigger a
paging from MME to UE.
1. UE-A = <imsi>
2. configure the UE selecting the APN with IPv4
configuration.
3. Power on UE-A
4. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

1. UE-A = <imsi>
2. configure the UE selecting the APN with IPv6
configuration.
3. Power on UE-A
4. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>
1. UE-A = <imsi>
2. configure the UE selecting the APN with static IP
configuration.
3. Power on UE-A
4. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE state on MME and EPG
4. delete the scuriber from MME and trigger release on S1.

MME:
gsh get_subscriber -imsi <imsi>

gsh delete_subscriber -imsi <imsi>

"1: If not already implemented, start a UE trace on the


MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

2: Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

3: After ~30s verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

Result: The UE should be in the EMM REGISTERED and


ECM IDLE state

4: Try to ping the UE IP address from the IAC context on


the EPG

context IAC
ping <UE IP address>

5: Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
"1: If not already implemented, start a UE trace on the
MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

2: Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

3: After ~30s verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

Result: The UE should be in the EMM REGISTERED and


ECM IDLE state

4: From the UE, execute a function that triggers the


sending of uplink data e.g. open a web page, send/receive
email, etc.

5: Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is


"1. On EPG, start UE trace for test IMSI on both control
and user plane
2. From a device with SIM card inserted, create a PDN
connection to assigned APN and make a note of the
pdp_id
3. Verify SACC statistic for the subscriber with pdp_id
4. On the UE, browse to xxx,xxx,xx URL and initiate an
account top-up.
5. On EPG, verify SACC statistic again
6. Collect user-plane trace for the test imsi and verify the
list of URL are included in the free-rated URL in LLD"

1. After power up, verify UE-A is attached to the IMS APN


via the MME UE trace (or BSP Capture unit trace)
2. Dump the subscribers data from the EPG to verify it's
QCI for signaling (default bearer)
3. Verify UE-A registers on IMS successfully
4. Verify SAPC policy for correct QoS values in Gx CCA-I
for IMS Default Bearer

Check if subscriber is able to move back to it's orignal


latched MME of pool group
*break the X2 link between the eNBs in the testing area if it
exists*
1:Verify the UE state on MME and EPG , It should be in
EMM REGISTERED ECM CONNECTED state.
2:From the UE, start a continuous ping to
www.google.com, for example.
3: Trigger a TAU between two TACs either by moving
across the TAC boundaries or reducing the Tx power of the
source eNB.
4: Convert the collected UE trace files to pcap for
verification of the procedure in Wireshark.
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
5:View the pcap file in Wireshark to verify the detach
procedure

*Ensure there exists an X2 link between the eNBs in the


testing area*
1:Verify the UE state on MME and EPG , It should be in
EMM REGISTERED ECM CONNECTED state.
2:From the UE, start a continuous ping to
www.google.com, for example.
3: Trigger a TAU between two TACs either by moving
across the TAC boundaries or reducing the Tx power of the
source eNB.
4: Convert the collected UE trace files to pcap for
verification of the procedure in Wireshark.
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
5:View the pcap file in Wireshark to verify the detach
procedure

1. UE-A = <imsi>
2. UE-A already attached on LTE
3. From MME, check UE status with
gsh get_subscriber <imsi>
4. Power-off UE-A
5. From MME, check UE status with
gsh get_subscribe <imsi>

Action: Make sure test UE is register in LTE network.


Action: Now attach the test UE automatically UMTS
network.
Result:UE can successfully handed over from LTE network
to UMTS network with no PS call drop
Action: Make sure test UE is register in 3G.
Action: Now attach the test UE automatically in LTE
network.
Result:Test UE can successfully handed over from UMTS
network to LTE network with no PS call drop
Action: Make sure test UE is register in 3G.
Action: Now attach the test UE automatically in LTE
network.
Result:Test UE can successfully handed over from UMTS
network to LTE network with no PS call drop

Action: Make sure test UE is register in 4G.


Action: Start browsing from UE
Result: User successful can browse the internet

1. the VoLTE UE-A sends messages when dialing


2. the MME/EPG should not have the APN configured and
so the UE falls back to CS to complete the call
1. Verify that attach request message sequence contains:

a) Prior to communicating with IMS, the UE must establish


IPSEC tunnel with EPG.

b) PDN connection to the ims APN via GTP tunnel.

2. Verify that challenge response is sent from I-CSCF to


the UE Status-Line: SIP/2.0 401 Unauthorized including:
Nonce Value: “…"
Cipher Key: "…"
Integrity Key: "…"

3. Verify that Status-Line: SIP/2.0 200 OK is received from


the I-CSCF when registration is complete.

4. The UE should subscribe to the REGISTRATION event (


P-CSCF generates a SUBSCRIBE request forward it to the
S-CSCF in the home network).

5. 3rd party registration to the SCCAS and SIP port


6. MESSAGE sent from SCCAS to ATCF with MSISDN for
SRVCC

1. the VoLTE UE-A sends messages when dialing


2. the MME/EPG should not have the APN configured and
so the UE falls back to CS to complete the call

1. the VoLTE UE-A sends messages when dialing


2. the MME/EPG should not have the APN configured and
so the UE falls back to CS to complete the call
Action: Make sure test UE is register in VoLTE.
Action: Start browsing from UE
Result: User successful can browse the internet

1. Attach UE with existing subscriber profile, check MME


with get_subscriber to review the APN list
2. Add a new APN to existing sub profile in HSS (more
details will be added)
3. Reattach UE, check MME with get_subscriber to review
the updated APN list

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

"- Initiate IMSI Attach procedure


- UE initiated service request
- Activate PDP context
- Check subscriber details using command :
gsh get_subscriber -imsi <imsi>
- Check specific subscriber statistics information on the
GGSN/PGW using command and verify apn details :
epg pgw user-info identifier-type imsi value <imsi>"
"- Initiate IMSI Attach procedure
- Initiate UE requested PDN Connectivity
- Get subscriber details and verify UE state using command
:
gsh get_subscriber -imsi <imsi> -dl 2
- Check specific subscriber statistics information on the
GGSN/PGW and verify apn details using command :
epg pgw user-info identifier-type imsi value <imsi>"

"- Initiate IMSI Attach procedure


- UE requested PDN connection
- EnodeB Initiated S1 Release
- Check specific subscriber statistics information using
command :
epg pgw user-info identifier-type imsi value <imsi>
and verify active PDN connection.
- UE Initiated Service Request
- Get subscriber details
- Payload- Uplink
- Payload-downlink
- Get Subscriber details"

"- Initiate IMSI Attach procedure


- UE Requested PDN connectivity
- Get subscriber details
- eNodeB initiated S1 Release
- Get subscriber details
- Initiate TAU procedure
- Initiate UE detach procedure"

"- Initiate IMSI Attach procedure


- UE Requested PDN connection
- Get subscriber details
- UE Requested PDN Disconnection
- Check specific subscriber statistics information on the
PGW using command :
epg pgw user-info identifier-type imsi value <imsi>
- Delete subscriber
- Get subscriber details"

"- Initiate IMSI Attach procedure


- UE requested PDN connection
- Check specific subscriber statistics information on the
PGW using command :
epg PGW user-info identifier-type IMSI value <IMSI>
- UE initiated detach procedure"

"- IMSI Attach - UE1


- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2
- Appointed IE Checking - QCI 5"
"- IMSI Attach - UE1
- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2"

"1: Power off the UE and verify it is no longer registered in


the SGW & PGW

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi>

2: Start a UE trace on the EPG for the subscriber IMSI

ManagedElement=1,Epg=1,Node=1,uetraceStart
<trace_reference> imsi <imsi>

3: Power on the UE and verify it is successfully attached to


the network and has an active PDN connection on the
SGW & PGW for the internet.Bluesky.com APN

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi>

4: Verify, that the subscriber can browse the internet and


stream video using YouTube, for example.

5: Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

start shell
cd ~/epg-ssr-toolbox-linux_iX86/
./epg_uetrace2pcap.pl -d
/var/log/services/epg/uetrace/ongoing/

Result: A UE trace pcap file for the subscriber IMSI is


generated

6: View the pcap file in Wireshark to verify the attach and


PDN connection procedure
"
"- Initiate IMSI Attach procedure
- UE initiated detach procedure
- Gx message validation"
End-to-End Functional TOL using Toy Cell

Pass Criteria Result managedService Customer Witness

Attach is successful with a default bearer created for


the internet APN.

To be Completed

Attach is successful with a default bearer created for


the internet APN.

To be Completed
The UE is shown as detached in the MME.
To be Completed

The UE is shown as detached in the MME after the


MME sends the PUR to the HSS, and the HSS
responds with the PUA to the MME.

To be Completed
The UE is shown as detached (unknown) in the MME,
after the MME sends the CLA to the HSS in response
to the CLR from the HSS.

To be Completed

The subscriber is disconnected from the network.

To be Completed
At expiration of periodic TAU timer (T3412), UE send
TAU request to network with cause set to periodic
updating.

To be Completed

The Downlink Data Notification Failure Indication is


sent from MME to the SGW indicating that the UE did
not respond to paging.
To be Completed

UE obtains an IP address from the local APN address


pool

To be Completed

UE obtains an IP address from the local APN address


pool

To be Completed
UE is assigned a static IP per the HSS configuration.

To be Completed

S1 release procedure is successfully executed


between eNB and MME

To be Completed

The UE receives the paging from the network and


successfully responds to it.
The UE transitions from ECM-IDLE to ECM-
CONNECTED.

To be Completed
The UE sends uplink data in ECM-Idle state with a
default bearer. Service request is sent by UE, bringing
the default bearer into Active again and resuming the
traffic.

To be Completed

DNS server is reachable and successfully resolves


SGW and PGW addresses based on TAC and APN
values.
The iDNS will successfully respond, resulting in the
MME selecting the correct combination of SGW/PGW.
To be Completed

QCI-> DSCP mapping is correct

To be Completed

Subscribers moved to the other MME in the pool


without traffic impact To be Completed
S1 based inter-eNB handover is successful

To be Completed

X2 based inter-eNB handover is successful

To be Completed

Initiate imsi combined attach


- UE initiate detach procedure

To be Completed

Initiate IMSI attach procedure


Initiate the handover process for 4g to 3g
To be Completed

Verify general node information


- Delete Subscriber for verification
-Initiate IMSI attach in 3g
- UE initiated service request
-Initiate PDP context activation To be Completed
- Perform IRAT handover from 3g to 4g
- Perform IRAT handover from 4g to 3g
Perform IRAT handover from 3g to 4g
- Perform IRAT handover from 4g to 3g
Initiate IMSI attach in 3g
- UE initiated service request
- Initiate PDP context activation
- Perform IRAT handover from 3g to 4g and change
MME
- Perform IRAT handover from 4g to 3g and change
To be Completed
MME
- Perform IRAT handover from 3g to 4g and change
MME
- Perform IRAT handover from 4g to 3g and change
MME

IMSI attach procedure


- Send Uplink UDP
- Receive downlink UDP. To be Completed
- UE initiated Detack
Initiate IMSI combined attach for UE1
- Initiate IMSI combined attach for UE2
- Initiate enodeB S1 release for UE2
- Initiate CSFB procedure without PS handover using
messages
- Initiate MO call MT call in CS core network
- Disconnect call
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE1
- Send uplink UDP (UE1) To be Completed
- Send downlink UDP (UE1)
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE2
- Send uplink UDP (UE1)
- Send downlink UDP (UE1)
- (L) UE Initiated Detach for UE1
- (L) UE Initiated Detach for UE2
IMSI Combine Attach for UE1
- IMSI Combine Attach for UE2
- UE IMS register for UE1
- UE IMS register for UE2
- VOLTE call establishment (with E-RAB modify)
- SRVCC (CS and PS HO) procedure
- TMSI reallocation procedure
- RAB assignment
- RAU procedure
- UE Disconnection
- SGSN Initiated Iu Release procedure
- Volte call termination
- UE IMS deregister for UE2 To be Completed
- UE initiated detach for UE1
- UE initiated detach for UE2

Initiate IMSI combined attach for UE1


- Initiate IMSI combined attach for UE2
- Initiate enodeB S1 release for UE1
- Initiate CSFB procedure without PS handover using
messages
- Initiate MO call MT call in CS core network
- Disconnect call
- TAU (Active Flag Set, TAU Complete Not Sent) for To be Completed
UE1
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE2
- (L) UE Initiated Detach for UE1
- (L) UE Initiated Detach for UE2

Initiate IMSI combined attach for UE1


- Initiate IMSI combined attach for UE2
- Initiate CSFB procedure without PS handover using
messages
- Initiate MO call MT call in CS core network
- Disconnect call
- TAU (Active Flag Set, TAU Complete Not Sent) for To be Completed
UE1
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE2
- (L) UE Initiated Detach for UE1
- (L) UE Initiated Detach for UE2
Initiate IMSI attach for UE1
- Initiate PDN connectivity (UE1)
- Initiate IMSI attach for UE2
- Initiate PDN connectivity (UE2)
- Perform UE IMS resgister (UE1)
- Perform UE IMS resgister (UE2)
- Enable VoLTE call (UE1->UE2)
- Send uplink UDP
- Send downlink UDP
- Start Volte call termination To be Completed
- Initiate UE IMS deregister (UE1)
- Initiate UE IMS deregister (UE2)
- eNodeB initiated S1 release (UE1)
- Send downlink UDP
- Paging
- UE initiated detach (UE1)
- UE initiated detach (UE2)

- Initiate IMSI Attach procedure


- Initiate UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>
- Initiate UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command : To be Completed
epg pgw user-info identifier-type imsi value <imsi>
- Initiate UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>

- Initiate IMSI Attach procedure


- Initiate UE requested PDN Connectivity
- Check shared IP pool statistics information using
command :
epg pgw statistics of shared-ip-pool;
epg pgw shared-ip-pool pool-iac1 statistics;
- Check specific subscriber statistics information on To be Completed
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>

Note:- Need to check the IP Pool Range and IP


assigned to the UE. It should be from the same

- Initiate IMSI Attach procedure


- UE initiated service request
- Activate PDP context
- Check subscriber details using command :
gsh get_subscriber -imsi <imsi> To be Completed
- Check specific subscriber statistics information on
the GGSN/PGW using command and verify apn
details :
epg pgw user-info identifier-type imsi value <imsi>
- Initiate IMSI Attach procedure
- Initiate UE requested PDN Connectivity
- Get subscriber details and verify UE state using
command :
gsh get_subscriber -imsi <imsi> -dl 2 To be Completed
- Check specific subscriber statistics information on
the GGSN/PGW and verify apn details using
command :
epg pgw user-info identifier-type imsi value <imsi>

- Initiate IMSI Attach procedure


- UE requested PDN connection
- EnodeB Initiated S1 Release
- Check specific subscriber statistics information using
command :
epg pgw user-info identifier-type imsi value <imsi>
and verify active PDN connection. To be Completed
- UE Initiated Service Request
- Get subscriber details
- Payload- Uplink
- Payload-downlink
- Get Subscriber details

- Initiate IMSI Attach procedure


- UE Requested PDN connectivity
- Get subscriber details
- eNodeB initiated S1 Release To be Completed
- Get subscriber details
- Initiate TAU procedure
- Initiate UE detach procedure

- Initiate IMSI Attach procedure


- UE Requested PDN connection
- Get subscriber details
- UE Requested PDN Disconnection
- Check specific subscriber statistics information on To be Completed
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>
- Delete subscriber
- Get subscriber details

- Initiate IMSI Attach procedure


- UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command : To be Completed Haiping Ou
epg PGW user-info identifier-type IMSI value
<IMSI>
- UE initiated detach procedure

- IMSI Attach - UE1


- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment To be Completed
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2
- Appointed IE Checking - QCI 5
- IMSI Attach - UE1
- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment To be Completed
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2

- Check EPG reachability


- Check the statistics of internet APN using command :
epg pgw apn internet statistics

To be Completed

- Initiate IMSI Attach procedure


- UE initiated detach procedure To be Completed
- Gx message validation

Pass 0
Conditional Pass 0
Failed 0
Not Applicable 0
To be Completed 41
Blocked 0
Total Test cases 41

wifi 0
3G 8
AAT 25
VNC 8
manual 0
Tracking
Ericsson
Date
Witness
Comment wifi 3G AAT VNC manual

x x

x x
x x

x x
x

x x
x x

x x

x x

x x
x x

x x

x x
x x

x
need MME pool
need second radio

need second radio

x x
need HO configuration

x
need HO configuration

x
need HO configuration

x x
need configuration

x
need configuration

x
need configuration

x
need configuration

x
x

x x

x x
ims-in-3G UE can browse

x
x x

x x

x x

x x

x x

x x
x

x x

x
Test C
TOL Ref./TC Ref. Test Object Name / Test Case Title

TO-SITE2-E2E-01 E2E System Test Cases

TC-SITE2-E2E-01.01 Attach with IMSI and Default Bearer Activation

TC-SITE2-E2E-01.02 Attach with GUTI and Default Bearer Activation


TC-SITE2-E2E-01.03 UE initiated Detach

TC-SITE2-E2E-01.04 MME initiated Detach


TC-SITE2-E2E-01.05 HSS Initiated Detach

TC-SITE2-E2E-01.06 PGW Initiated Bearer Deactivation


TC-SITE2-E2E-01.07 Periodic TAU

TC-SITE2-E2E-01.08 Unsuccessful Paging - UE Not Responding

TC-SITE2-E2E-01.09 IPv4 Address Allocation by PGW

TC-SITE2-E2E-01.10 IPv6 Address Allocation by PGW


TC-SITE2-E2E-01.11 Static IP Address Allocation

TC-SITE2-E2E-01.12 eNodeB Triggered S1 Release

TC-SITE2-E2E-01.13 Network Triggered Service Request (Paging)


TC-SITE2-E2E-01.14 UE Triggered Service Request

TC-SITE2-E2E-01.15 S/P/GW Selection using DNS

TC-SITE2-E2E-01.16 DSCP Mapping According to QCI

TC-SITE2-E2E-01.17 MME Pool Move


TC-SITE2-E2E-01.18 Inter-eNB Inter-TA S1 Based Handover (TAU)

TC-SITE2-E2E-01.19 inter-eNB inter-tracking area X2 based handover (TAU)

TC-SITE2-E2E-01.20 4G-MME-MM-Combined_Deatch

TC-SITE2-E2E-01.21 Generic-4G-MME-MM-Handover_4G_3G

TC-SITE2-E2E-01.22 Generic-4G-MME-MM-3G_LTE_3G_LTE_Handover_Intra
TC-SITE2-E2E-01.23 Generic-4G-MME-MM-3G_LTE_3G_LTE_Handover_Inter

TC-SITE2-E2E-01.24 Generic-4G-MME-4G_Testing-Internet_Browsing

TC-SITE2-E2E-01.25 Generic-4G-MME-CSF-Return_Data_Session_CSFB
TC-SITE2-E2E-01.26 Generic-4G-MME-VoLTE-Test_SRVCC

TC-SITE2-E2E-01.27 Generic-4G-MME-AT-CSFB_Idle_Mode

TC-SITE2-E2E-01.28 Generic-4G-MME-AT-CSFB_Active_Mode
TC-SITE2-E2E-01.29 Generic-4G-MME-VoLTE-IMS_Voice_Web_Browse

TC-SITE2-E2E-01.30 Generic-4G-EPG-APN-Additional_PDN

TC-SITE2-E2E-01.31 Generic-4G-EPG-APN-Shared_IP_Pool

TC-SITE2-E2E-01.32 Generic-4G-EPG-APN-3G_APN_Handling
TC-SITE2-E2E-01.33 Generic-4G-EPG-APN-4G_APN_Handling

TC-SITE2-E2E-01.34 Generic-4G-EPG-BCF-Verify_Service_Request_DL_UL

TC-SITE2-E2E-01.35 Generic-4G-EPG-Mobility_Volte-Idle_Mode_TAU

TC-SITE2-E2E-01.36 Generic-4G-EPG-BCF-UE_Initiate_All_PDN_Disconn

TC-SITE2-E2E-01.37 Generic-4G-EPG-BCF-Internet_PDN_Default_Bearer

TC-SITE2-E2E-01.38 Generic-4G-EPG-QOS-Default_Bearer_QCI_5
TC-SITE2-E2E-01.39 Generic-4G-EPG-QOS-Dedicated_Bearer_QCI_1

TC-SITE2-E2E-01.40 Generic-4G-EPG-PM-Verify_Internet_APN

TC-SITE2-E2E-01.41 Generic-4G-EPG-Diameter-Gx_Comm_PCRF_Attach
Packet Core End-to-End
Test Case Information
Description / Objective

Perform initial attach using IMSI

Perform attach using GUTI. This implies that the subscriber


was attached in the network previously and a GUTI was
alloced by the MME.
This test case will verify a UE initiated detach from state
ECM-CONNECTED by powering off the device.

This test case is to verify PUR/PUA (Purge UE


Request/Purge UE Ack) between the SGSN-MME and
HSS. The SGSN-MME uses PUR to inform the HSS that
the subscriber profile has been deleted. The HSS shall
respond with PUA with “diameter_success” and remove
MME info from the subscriber profile.
When the UE is in the ECM-CONNECTED state: This test
case is to verify CLR/CLA (Cancel Location
Request/Cancel Location Answer) messaging between the
MME and HSS. The HSS sends the CLR to inform the
MME that the subscriber profile in the MME is to be
deleted. The MME shall delete the subscriber profile and
respond with a CLA indicating success.

This test is to verify that the manual deletion of a subscriber


from the PGW results in the PDN connection being torn
down
After expiration of the periodic TAU timer, UE send TAU
request to network with cause set to periodic updating

Verify the unsuccessful paging due to no answer from UE.


In order to trigger the unsuccessful paging the UE is
powered off (removing battery).

Verify that the UE has been allocated an IP address from


the local APN pool

Verify that the UE has been allocated an IP address from


the local APN pool
Verify that the UE has been allocated a static IP address

The MME sends an Update Bearer Request message to


the SGW. This message can be triggered by an S1
Release Request message from the eNodeB due to user-
inactivity, for eample.

Verify the successful paging triggered by downlink data


notification.
Demonstrate the service request procedure initiated by an
UE in idle state.

Verify the MME queries iDNS for TAC/APN to SGW/PGW


IP address mapping

Thee purpose of this testcase is to verify that the DSCP


values on the traffic interfaces respects the QCI/DSCP
mapping as defined

This test case verifies that a subscriber or group of


subscribers can be seamlessly moved from one MME in
the pool to the other without traffic impact
To validate the S1 inter-eNB handovers

To validate the X2 inter-eNB handovers

To verify the combined detach procedure initiated by UE

PS Handover from an LTE Network to a UMTS Network

To verify intra access handover with active pdp for 3g to 4g


and vice-versa
To verify inter sgsn access handover with active pdp for 3g
to 4g and vice-versa

To verify 4G testing : Internet Browsing

Return to data session after CSFB


Test SRVCC

To verify CSFB in idle mode

To verify CSFB in active mode


Simultaneous use of IMS voice and web browsing

Initial+Additional PDN Conn on different APN (subscribed


APN=*)

address reuse in shared pool

3G APN Handling
4G APN Handling

Verify Service Request from UE (DL/UL).

Verify Idle Mode Tracking Area Update from UE

Verify UE initiated all PDN disconnect on LTE

Verify Internet PDN data communication on default bearer

Verify establishment of default bearer with QCI 5 with IMS


PDN
Verify establishment of dedicated bearer with QCI 1 during
voice call

Verify Internet APN

Verify Gx communication to PCRF during attach and


detach
Packet Core End-to-End Functional TOL using Toy Cel
ase Information
Steps

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

Result: The UE state in MME is EMM-REGISTERED ECM-


CONNECTED

4. Convert the collected UE trace files to pcap for verification of


the procedure in Wireshark
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is generated

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE state on MME and EPG
MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The UE state in MME is EMM-REGISTERED ECM-


CONNECTED

4. Convert the collected UE trace files to pcap for verification of


the procedure in Wireshark
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is generated


Action: Make sure test UE is registered in SGSN.
Action: Turn off test UE
Result: User successful deregistered from SGSN network
"0. If not already implemented, start a UE trace on the
MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

1. Verify the UE is registered in the MME

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

2. Trigger a detach from the MME


gsh delete_subscriber -imsi <imsi>

Result: UE is successfully detached from the network

3. Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The UE state in MME is EMM-DEREGISTERED


ECM-IDLE

4. Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is


generated"
"1. If not already implemented, start a UE trace on the
MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

2. Verify the UE is registered in the MME

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

3. Verify the HSS-EsmLocationState of the subscriber in


the HSS by opening the CM Browser from the HSS-ESM
Node Management toolbox, and checking the HSS-
EsmLocationState

Result: The subscriber’s HSS-EsmLocationState is


“LOCATED”

4. Trigger a detach from the HSS by opening the CM


Browser from the HSS-ESM Node Management toolbox,
and changing the subscriber’s HSS-EsmLocationState to
“UNKNOWN”
Result: UE is successfully detached from the network. HSS
sends a Cancel Location Request to the MME to delete the
subscriber’s record; MME confirms the record removal by
sending Cancel Location Answer to the HSS.

5. Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi
"1: Verify the UE state on MME and EPG.
MME --> gsh get_subscriber -imsi <imsi>
SGW/PGW --> ManagedElement=1,Epg=1,Sgw=1,userInfo
imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

2: Using the CLI, trigger a manual detach from the PGw.


ManagedElement=1,Epg=1,Pgw=1,ControlPlane=1,Sessio
n=1, terminateImsi <imsi>

3: Verify the UE state on MME and EPG again by above


commands."
"1:change the S1 Mobile Reachable Timer to 34 mins,
thereby setting the Periodic TAU timer (T3412) sent to the
UE to 30 mins.
gsh modify_s1_mme -s1 s1_mme -mrt 34
gsh check_config
gsh activate_config_pending
2:Verify the UE state on MME and EPG.
3:If the subscriber is registered in the MME, purge the
subscriber from the network and force the UE to reattach
gsh delete_subscriber -imsi <imsi> -dettype
reattach_required
4: Wait ~34 mins for the UE to execute the periodic TAU
procedure.
5:Convert the collected UE trace files to pcap for
verification of the procedure in Wireshark and View the
pcap file in Wireshark to verify the detach procedure.
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
6:Change the S1 Mobile Reachable Timer back to the
default of 58 mins, thereby setting the Periodic TAU timer
(T3412) sent to the UE to 54 mins."

1. Move the UE out of radio coverage or remove


battery(not detacched).
2.a initiate a down link data traffic from network to UE and
trigger a paging from MME to UE.
2.b make a call to this VoLTE subscriber and trigger a
paging from MME to UE.
1. UE-A = <imsi>
2. configure the UE selecting the APN with IPv4
configuration.
3. Power on UE-A
4. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

1. UE-A = <imsi>
2. configure the UE selecting the APN with IPv6
configuration.
3. Power on UE-A
4. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>
1. UE-A = <imsi>
2. configure the UE selecting the APN with static IP
configuration.
3. Power on UE-A
4. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE state on MME and EPG
4. delete the scuriber from MME and trigger release on S1.

MME:
gsh get_subscriber -imsi <imsi>

gsh delete_subscriber -imsi <imsi>

"1: If not already implemented, start a UE trace on the


MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

2: Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

3: After ~30s verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

Result: The UE should be in the EMM REGISTERED and


ECM IDLE state

4: Try to ping the UE IP address from the IAC context on


the EPG

context IAC
ping <UE IP address>

5: Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
"1: If not already implemented, start a UE trace on the
MME for the subscriber IMSI

gsh create_ue_trace -id <imsi> -type imsi -ref


<12_digit_ref#> -depth maximum -ifl all -iflm all -ip NULL -
ent enodeb

2: Verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi

Result: The subscriber is registered in the MME and in the


EMM REGISTERED ECM CONNECTED state

3: After ~30s verify the UE state on MME and EPG

MME:
gsh get_subscriber -imsi <imsi>

Result: The UE should be in the EMM REGISTERED and


ECM IDLE state

4: From the UE, execute a function that triggers the


sending of uplink data e.g. open a web page, send/receive
email, etc.

5: Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>

Result: A UE trace pcap file for the subscriber IMSI is


"1. On EPG, start UE trace for test IMSI on both control
and user plane
2. From a device with SIM card inserted, create a PDN
connection to assigned APN and make a note of the
pdp_id
3. Verify SACC statistic for the subscriber with pdp_id
4. On the UE, browse to xxx,xxx,xx URL and initiate an
account top-up.
5. On EPG, verify SACC statistic again
6. Collect user-plane trace for the test imsi and verify the
list of URL are included in the free-rated URL in LLD"

1. After power up, verify UE-A is attached to the IMS APN


via the MME UE trace (or BSP Capture unit trace)
2. Dump the subscribers data from the EPG to verify it's
QCI for signaling (default bearer)
3. Verify UE-A registers on IMS successfully
4. Verify SAPC policy for correct QoS values in Gx CCA-I
for IMS Default Bearer

Check if subscriber is able to move back to it's orignal


latched MME of pool group
*break the X2 link between the eNBs in the testing area if it
exists*
1:Verify the UE state on MME and EPG , It should be in
EMM REGISTERED ECM CONNECTED state.
2:From the UE, start a continuous ping to
www.google.com, for example.
3: Trigger a TAU between two TACs either by moving
across the TAC boundaries or reducing the Tx power of the
source eNB.
4: Convert the collected UE trace files to pcap for
verification of the procedure in Wireshark.
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
5:View the pcap file in Wireshark to verify the detach
procedure

*Ensure there exists an X2 link between the eNBs in the


testing area*
1:Verify the UE state on MME and EPG , It should be in
EMM REGISTERED ECM CONNECTED state.
2:From the UE, start a continuous ping to
www.google.com, for example.
3: Trigger a TAU between two TACs either by moving
across the TAC boundaries or reducing the Tx power of the
source eNB.
4: Convert the collected UE trace files to pcap for
verification of the procedure in Wireshark.
uetrace2pcap.pl -f /logs/ue_trace/tmp/ue_trace.<file#>
5:View the pcap file in Wireshark to verify the detach
procedure

1. UE-A = <imsi>
2. UE-A already attached on LTE
3. From MME, check UE status with
gsh get_subscriber <imsi>
4. Power-off UE-A
5. From MME, check UE status with
gsh get_subscribe <imsi>

Action: Make sure test UE is register in LTE network.


Action: Now attach the test UE automatically UMTS
network.
Result:UE can successfully handed over from LTE network
to UMTS network with no PS call drop
Action: Make sure test UE is register in 3G.
Action: Now attach the test UE automatically in LTE
network.
Result:Test UE can successfully handed over from UMTS
network to LTE network with no PS call drop
Action: Make sure test UE is register in 3G.
Action: Now attach the test UE automatically in LTE
network.
Result:Test UE can successfully handed over from UMTS
network to LTE network with no PS call drop

Action: Make sure test UE is register in 4G.


Action: Start browsing from UE
Result: User successful can browse the internet

1. the VoLTE UE-A sends messages when dialing


2. the MME/EPG should not have the APN configured and
so the UE falls back to CS to complete the call
1. Verify that attach request message sequence contains:

a) Prior to communicating with IMS, the UE must establish


IPSEC tunnel with EPG.

b) PDN connection to the ims APN via GTP tunnel.

2. Verify that challenge response is sent from I-CSCF to


the UE Status-Line: SIP/2.0 401 Unauthorized including:
Nonce Value: “…"
Cipher Key: "…"
Integrity Key: "…"

3. Verify that Status-Line: SIP/2.0 200 OK is received from


the I-CSCF when registration is complete.

4. The UE should subscribe to the REGISTRATION event (


P-CSCF generates a SUBSCRIBE request forward it to the
S-CSCF in the home network).

5. 3rd party registration to the SCCAS and SIP port


6. MESSAGE sent from SCCAS to ATCF with MSISDN for
SRVCC

1. the VoLTE UE-A sends messages when dialing


2. the MME/EPG should not have the APN configured and
so the UE falls back to CS to complete the call

1. the VoLTE UE-A sends messages when dialing


2. the MME/EPG should not have the APN configured and
so the UE falls back to CS to complete the call
Action: Make sure test UE is register in VoLTE.
Action: Start browsing from UE
Result: User successful can browse the internet

1. Attach UE with existing subscriber profile, check MME


with get_subscriber to review the APN list
2. Add a new APN to existing sub profile in HSS (more
details will be added)
3. Reattach UE, check MME with get_subscriber to review
the updated APN list

1. UE-A = <imsi>
2. Power on UE-A
3. Verify the UE data in EPG

SGW/PGW:
epg pgw user-info identifier-type imsi value <imsi>
epg sgw user-info identifier-type imsi value <imsi>

"- Initiate IMSI Attach procedure


- UE initiated service request
- Activate PDP context
- Check subscriber details using command :
gsh get_subscriber -imsi <imsi>
- Check specific subscriber statistics information on the
GGSN/PGW using command and verify apn details :
epg pgw user-info identifier-type imsi value <imsi>"
"- Initiate IMSI Attach procedure
- Initiate UE requested PDN Connectivity
- Get subscriber details and verify UE state using command
:
gsh get_subscriber -imsi <imsi> -dl 2
- Check specific subscriber statistics information on the
GGSN/PGW and verify apn details using command :
epg pgw user-info identifier-type imsi value <imsi>"

"- Initiate IMSI Attach procedure


- UE requested PDN connection
- EnodeB Initiated S1 Release
- Check specific subscriber statistics information using
command :
epg pgw user-info identifier-type imsi value <imsi>
and verify active PDN connection.
- UE Initiated Service Request
- Get subscriber details
- Payload- Uplink
- Payload-downlink
- Get Subscriber details"

"- Initiate IMSI Attach procedure


- UE Requested PDN connectivity
- Get subscriber details
- eNodeB initiated S1 Release
- Get subscriber details
- Initiate TAU procedure
- Initiate UE detach procedure"

"- Initiate IMSI Attach procedure


- UE Requested PDN connection
- Get subscriber details
- UE Requested PDN Disconnection
- Check specific subscriber statistics information on the
PGW using command :
epg pgw user-info identifier-type imsi value <imsi>
- Delete subscriber
- Get subscriber details"

"- Initiate IMSI Attach procedure


- UE requested PDN connection
- Check specific subscriber statistics information on the
PGW using command :
epg PGW user-info identifier-type IMSI value <IMSI>
- UE initiated detach procedure"

"- IMSI Attach - UE1


- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2
- Appointed IE Checking - QCI 5"
"- IMSI Attach - UE1
- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2"

"1: Power off the UE and verify it is no longer registered in


the SGW & PGW

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi>

2: Start a UE trace on the EPG for the subscriber IMSI

ManagedElement=1,Epg=1,Node=1,uetraceStart
<trace_reference> imsi <imsi>

3: Power on the UE and verify it is successfully attached to


the network and has an active PDN connection on the
SGW & PGW for the internet.Bluesky.com APN

SGW/PGW:
ManagedElement=1,Epg=1,Sgw=1,userInfo imsi <imsi>
ManagedElement=1,Epg=1,Pgw=1,userInfo imsi <imsi>

4: Verify, that the subscriber can browse the internet and


stream video using YouTube, for example.

5: Convert the collected UE trace files to pcap for


verification of the procedure in Wireshark

start shell
cd ~/epg-ssr-toolbox-linux_iX86/
./epg_uetrace2pcap.pl -d
/var/log/services/epg/uetrace/ongoing/

Result: A UE trace pcap file for the subscriber IMSI is


generated

6: View the pcap file in Wireshark to verify the attach and


PDN connection procedure
"
"- Initiate IMSI Attach procedure
- UE initiated detach procedure
- Gx message validation"
End-to-End Functional TOL using Toy Cell

Pass Criteria Result managedService Customer Witness

Attach is successful with a default bearer created for


the internet APN.

To be Completed

Attach is successful with a default bearer created for


the internet APN.

To be Completed
The UE is shown as detached in the MME.
To be Completed

The UE is shown as detached in the MME after the


MME sends the PUR to the HSS, and the HSS
responds with the PUA to the MME.

To be Completed
The UE is shown as detached (unknown) in the MME,
after the MME sends the CLA to the HSS in response
to the CLR from the HSS.

To be Completed

The subscriber is disconnected from the network.

To be Completed
At expiration of periodic TAU timer (T3412), UE send
TAU request to network with cause set to periodic
updating.

To be Completed

The Downlink Data Notification Failure Indication is


sent from MME to the SGW indicating that the UE did
not respond to paging.
To be Completed

UE obtains an IP address from the local APN address


pool

To be Completed

UE obtains an IP address from the local APN address


pool

To be Completed
UE is assigned a static IP per the HSS configuration.

To be Completed

S1 release procedure is successfully executed


between eNB and MME

To be Completed

The UE receives the paging from the network and


successfully responds to it.
The UE transitions from ECM-IDLE to ECM-
CONNECTED.

To be Completed
The UE sends uplink data in ECM-Idle state with a
default bearer. Service request is sent by UE, bringing
the default bearer into Active again and resuming the
traffic.

To be Completed

DNS server is reachable and successfully resolves


SGW and PGW addresses based on TAC and APN
values.
The iDNS will successfully respond, resulting in the
MME selecting the correct combination of SGW/PGW.
To be Completed

QCI-> DSCP mapping is correct

To be Completed

Subscribers moved to the other MME in the pool


without traffic impact To be Completed
S1 based inter-eNB handover is successful

To be Completed

X2 based inter-eNB handover is successful

To be Completed

Initiate imsi combined attach


- UE initiate detach procedure

To be Completed

Initiate IMSI attach procedure


Initiate the handover process for 4g to 3g
To be Completed

Verify general node information


- Delete Subscriber for verification
-Initiate IMSI attach in 3g
- UE initiated service request
-Initiate PDP context activation To be Completed
- Perform IRAT handover from 3g to 4g
- Perform IRAT handover from 4g to 3g
Perform IRAT handover from 3g to 4g
- Perform IRAT handover from 4g to 3g
Initiate IMSI attach in 3g
- UE initiated service request
- Initiate PDP context activation
- Perform IRAT handover from 3g to 4g and change
MME
- Perform IRAT handover from 4g to 3g and change
To be Completed
MME
- Perform IRAT handover from 3g to 4g and change
MME
- Perform IRAT handover from 4g to 3g and change
MME

IMSI attach procedure


- Send Uplink UDP
- Receive downlink UDP. To be Completed
- UE initiated Detack
Initiate IMSI combined attach for UE1
- Initiate IMSI combined attach for UE2
- Initiate enodeB S1 release for UE2
- Initiate CSFB procedure without PS handover using
messages
- Initiate MO call MT call in CS core network
- Disconnect call
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE1
- Send uplink UDP (UE1) To be Completed
- Send downlink UDP (UE1)
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE2
- Send uplink UDP (UE1)
- Send downlink UDP (UE1)
- (L) UE Initiated Detach for UE1
- (L) UE Initiated Detach for UE2
IMSI Combine Attach for UE1
- IMSI Combine Attach for UE2
- UE IMS register for UE1
- UE IMS register for UE2
- VOLTE call establishment (with E-RAB modify)
- SRVCC (CS and PS HO) procedure
- TMSI reallocation procedure
- RAB assignment
- RAU procedure
- UE Disconnection
- SGSN Initiated Iu Release procedure
- Volte call termination
- UE IMS deregister for UE2 To be Completed
- UE initiated detach for UE1
- UE initiated detach for UE2

Initiate IMSI combined attach for UE1


- Initiate IMSI combined attach for UE2
- Initiate enodeB S1 release for UE1
- Initiate CSFB procedure without PS handover using
messages
- Initiate MO call MT call in CS core network
- Disconnect call
- TAU (Active Flag Set, TAU Complete Not Sent) for To be Completed
UE1
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE2
- (L) UE Initiated Detach for UE1
- (L) UE Initiated Detach for UE2

Initiate IMSI combined attach for UE1


- Initiate IMSI combined attach for UE2
- Initiate CSFB procedure without PS handover using
messages
- Initiate MO call MT call in CS core network
- Disconnect call
- TAU (Active Flag Set, TAU Complete Not Sent) for To be Completed
UE1
- TAU (Active Flag Set, TAU Complete Not Sent) for
UE2
- (L) UE Initiated Detach for UE1
- (L) UE Initiated Detach for UE2
Initiate IMSI attach for UE1
- Initiate PDN connectivity (UE1)
- Initiate IMSI attach for UE2
- Initiate PDN connectivity (UE2)
- Perform UE IMS resgister (UE1)
- Perform UE IMS resgister (UE2)
- Enable VoLTE call (UE1->UE2)
- Send uplink UDP
- Send downlink UDP
- Start Volte call termination To be Completed
- Initiate UE IMS deregister (UE1)
- Initiate UE IMS deregister (UE2)
- eNodeB initiated S1 release (UE1)
- Send downlink UDP
- Paging
- UE initiated detach (UE1)
- UE initiated detach (UE2)

- Initiate IMSI Attach procedure


- Initiate UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>
- Initiate UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command : To be Completed
epg pgw user-info identifier-type imsi value <imsi>
- Initiate UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>

- Initiate IMSI Attach procedure


- Initiate UE requested PDN Connectivity
- Check shared IP pool statistics information using
command :
epg pgw statistics of shared-ip-pool;
epg pgw shared-ip-pool pool-iac1 statistics;
- Check specific subscriber statistics information on To be Completed
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>

Note:- Need to check the IP Pool Range and IP


assigned to the UE. It should be from the same

- Initiate IMSI Attach procedure


- UE initiated service request
- Activate PDP context
- Check subscriber details using command :
gsh get_subscriber -imsi <imsi> To be Completed
- Check specific subscriber statistics information on
the GGSN/PGW using command and verify apn
details :
epg pgw user-info identifier-type imsi value <imsi>
- Initiate IMSI Attach procedure
- Initiate UE requested PDN Connectivity
- Get subscriber details and verify UE state using
command :
gsh get_subscriber -imsi <imsi> -dl 2 To be Completed
- Check specific subscriber statistics information on
the GGSN/PGW and verify apn details using
command :
epg pgw user-info identifier-type imsi value <imsi>

- Initiate IMSI Attach procedure


- UE requested PDN connection
- EnodeB Initiated S1 Release
- Check specific subscriber statistics information using
command :
epg pgw user-info identifier-type imsi value <imsi>
and verify active PDN connection. To be Completed
- UE Initiated Service Request
- Get subscriber details
- Payload- Uplink
- Payload-downlink
- Get Subscriber details

- Initiate IMSI Attach procedure


- UE Requested PDN connectivity
- Get subscriber details
- eNodeB initiated S1 Release To be Completed
- Get subscriber details
- Initiate TAU procedure
- Initiate UE detach procedure

- Initiate IMSI Attach procedure


- UE Requested PDN connection
- Get subscriber details
- UE Requested PDN Disconnection
- Check specific subscriber statistics information on To be Completed
the PGW using command :
epg pgw user-info identifier-type imsi value <imsi>
- Delete subscriber
- Get subscriber details

- Initiate IMSI Attach procedure


- UE requested PDN connection
- Check specific subscriber statistics information on
the PGW using command : To be Completed Haiping Ou
epg PGW user-info identifier-type IMSI value
<IMSI>
- UE initiated detach procedure

- IMSI Attach - UE1


- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment To be Completed
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2
- Appointed IE Checking - QCI 5
- IMSI Attach - UE1
- IMSI Attach - UE2
- UE IMS Register - UE1
- UE IMS Register - UE2
- VoLTE Call Establishment To be Completed
- VoLTE Call Termination
- UE IMS deregister -UE1
- UE IMS Deregister - UE2

- Check EPG reachability


- Check the statistics of internet APN using command :
epg pgw apn internet statistics

To be Completed

- Initiate IMSI Attach procedure


- UE initiated detach procedure To be Completed
- Gx message validation

Pass 0
Conditional Pass 0
Failed 0
Not Applicable 0
To be Completed 41
Blocked 0
Total Test cases 41

wifi 0
3G 8
AAT 25
VNC 8
manual 0
Tracking
Ericsson
Date
Witness
Comment wifi 3G AAT VNC manual

x x

x x
x x

x x
x

x x
x x

x x

x x

x x
x x

x x

x x
x x

x
need MME pool
need second radio

need second radio

x x
need HO configuration

x
need HO configuration

x
need HO configuration

x x
need configuration

x
need configuration

x
need configuration

x
need configuration

x
x

x x

x x
ims-in-3G UE can browse

x
x x

x x

x x

x x

x x

x x
x

x x

x
Test Case Information
Priority
TOL Ref. Test Object Name /
Level
TC Ref. Test Case Title
(P1/P2)
TC-SITE1-PBX-01

PBX Originating Call to Bluesky Mobile


TC-SITE1-PBX-01.01 subscriber in LTE/WiFi P1

TC-SITE1-PBX-01.02 PBX Originating Call to Bluesky Mobile


subscriber in UMTS P1

TC-SITE1-PBX-01.03 PBX Originating Call to External subscriber P1

Bluesky Mobile to PBX Number


TC-SITE1-PBX-01.04 Terminating Call - LTE/WiFi originating P1

Bluesky Mobile to PBX Number


TC-SITE1-PBX-01.05 Terminating Call - UMTS originating P1
PBX TOL using Toy Cell
Test Case Information
Description / Objective Steps

To verify that a PBX originating call terminating in a Bluesky


mobile subscriber is completed successfully. PBX user to UE-B call.

To verify that a PBX originating call terminating in a Bluesky PBX user to UE-B call.
mobile subscriber is completed successfully.

To verify that a PBX originating call terminating in a remote PBX user to UE-B (other
network (other PLMN/ PSTN) is completed successfully. operator) call.

To verify that a PBX terminating call from Bluesky mobile


subscriber is completed successfully. UE-A to PBX call.

To verify that a PBX terminating call from Bluesky mobile


subscriber is completed successfully. UE-A to PBX call.
PBX TOL using Toy Cell
Tracking
Pass Criteria Result (Futon Device) Bluesky Witness

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Pass 0
Pass with Comment 0
Failed 0
Not Applicable 0
To be Completed 5 total
blocked 0
Total Test Cases 5
wifi 0
3G 0
AAT 0
VNC 0
manual 0
Tracking
Ericsson Witness Date Comment wifi 3G

0
0
0
0
0
AAT VNC manual
Test Case Information
Priority
TOL Ref. Test Object Name /
Level
TC Ref. Test Case Title
(P1/P2)
TC-SITE2-PBX-01

PBX Originating Call to Bluesky Mobile


TC-SITE2-PBX-01.01 subscriber in LTE/WiFi P1

TC-SITE2-PBX-01.02 PBX Originating Call to Bluesky Mobile


subscriber in UMTS P1

TC-SITE2-PBX-01.03 PBX Originating Call to External subscriber P1

Bluesky Mobile to PBX Number


TC-SITE2-PBX-01.04 Terminating Call - LTE/WiFi originating P1

Bluesky Mobile to PBX Number


TC-SITE2-PBX-01.05 Terminating Call - UMTS originating P1
PBX TOL using Toy Cell
Test Case Information
Description / Objective Steps

To verify that a PBX originating call terminating in a Bluesky


mobile subscriber is completed successfully. PBX user to UE-B call.

To verify that a PBX originating call terminating in a Bluesky PBX user to UE-B call.
mobile subscriber is completed successfully.

To verify that a PBX originating call terminating in a remote PBX user to UE-B (other
network (other PLMN/ PSTN) is completed successfully. operator) call.

To verify that a PBX terminating call from Bluesky mobile


subscriber is completed successfully. UE-A to PBX call.

To verify that a PBX terminating call from Bluesky mobile


subscriber is completed successfully. UE-A to PBX call.
PBX TOL using Toy Cell
Tracking
Pass Criteria Result (Futon Device) Bluesky Witness

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Successful call completion. No abnormal observations


in call set-up, ringing, call progress and call termination. To be Completed

Pass 0
Pass with Comment 0
Failed 0
Not Applicable 0
To be Completed 5 total
blocked 0
Total Test Cases 5
wifi 0
3G 0
AAT 0
VNC 0
manual 0
Tracking
Ericsson Witness Date Comment wifi 3G

0
0
0
0
0
AAT VNC manual
SMS over IP
Test Case Information
Priority
TOL Ref. Test Object Name /
Level Description / Objective
TC Ref. Test Case Title
(P1/P2)
IPSMGW

TC-SITE1-E2E-IPSM-01 VoLTE user register to EME P1 VoLTE register

TC-SITE1-E2E-IPSM-02 Volte to VoLTE P1 MO-SMS-IMS domain

TC-SITE1-E2E-IPSM-03 VoLTE to UMTS SMS P1 MO-SMS-breakout

TC-SITE1-E2E-IPSM-04 UMTS to VoLTE P1 MT-SMS-break in

TC-SITE1-E2E-IPSM-05 Volte MMS to external MMS P1 MO-MMS- ims domain

TC-SITE1-E2E-IPSM-06 VoLTE MMS to UMTS MMS P1 MO-MMS-break out


TC-SITE1-E2E-IPSM-07 UMTS to VoLTE MMS P1 MT-MMS-break in

TC-SITE1-E2E-IPSM-08 MWI after VM deposit P1 MWI

TC-SITE1-E2E-IPSM-09 PLMN to VoLTE SMS P1 MT-SMS-break in

TC-SITE1-E2E-IPSM-10 PLMN to VoWiFi Trusted SMS P1 MT-SMS-break in

PLMN to VoWiFi Untrusted


TC-SITE1-E2E-IPSM-11 SMS P1 MT-SMS-break in
SMS over IP (IP-SM-GW/ vEMe) TOL using Toy Cell
Test Case Information
Steps

Action: Make sure UE-A has SMS MO/MT service in EDA


Action: Make sure UE-A is registered in LTE.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in EDA
Action: Make sure UE-A/B are registered in LTE.
Action: Send a test SMS from UE-A
Result: SMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in HLR
Action: Make sure UE-A is registered in LTE.
Action: Make sure UE-B is registered in UMTS.
Action: Send a test SMS from UE-A
Result: SMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-A has SMS MT service in HLR
Action: Make sure UE-B is registered in LTE.
Action: Make sure UE-A is registered in UMTS.
Action: Send a test SMS from UE-A
Result: SMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in external network.
Action: Make sure UE-A is registered in LTE.
Action: Make sure UE-B is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in HLR
Action: Make sure UE-A is registered in LTE.
Action: Make sure UE-B is registered in UMTS.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.
Action: Make sure UE-B has SMS MO service in EDA
Action: Make sure UE-A has SMS MT service in HLR
Action: Make sure UE-B is registered in LTE.
Action: Make sure UE-A is registered in UMTS.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has VM service in EDA


Action: Make sure UE-A is registered in LTE.
Action: call to VM from UE-A and leave a message.
Result: UE-A should get notice of a new VM received.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-B is registered in LTE.
Action: Make sure UE-A has SMS MT service in external network.
Action: Make sure UE-A is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-B is registered in WiFi.
Action: Make sure UE-A has SMS MT service in external network.
Action: Make sure UE-A is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-B is registered in WiFi.
Action: Make sure UE-A has SMS MT service in external network.
Action: Make sure UE-A is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.
) TOL using Toy Cell
Tracking
Pass Criteria Result Bluesky Witness
Ericsson Witness Date

UE-A registered with SMS service. To be Completed

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

MMS should be successfully sent and received To be Completed


on Ues

MMS should be successfully sent and received To be Completed


on Ues
MMS should be successfully sent and received To be Completed
on Ues

UE should be notified once VM received . To be Completed

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

Pass 0 0
Pass with Comment 0 0
Failed 0 0
Not Applicable 0 0
To be Completed 11 total 0
Blocked 0
Total Test Cases 11
wifi 0
3G 4
AAT 0
VNC 0
manual 0
Tracking
Comment wifi 3G AAT VNC manual

x
x
SMS over IP
Test Case Information
Priority
TOL Ref. Test Object Name /
Level Description / Objective
TC Ref. Test Case Title
(P1/P2)
IPSMGW

TC-SITE2-E2E-IPSM-01 VoLTE user register to EME P1 VoLTE register

TC-SITE2-E2E-IPSM-02 Volte to VoLTE P1 MO-SMS-IMS domain

TC-SITE2-E2E-IPSM-03 VoLTE to UMTS SMS P1 MO-SMS-breakout

TC-SITE2-E2E-IPSM-04 UMTS to VoLTE P1 MT-SMS-break in

TC-SITE2-E2E-IPSM-05 Volte MMS to external MMS P1 MO-MMS- ims domain

TC-SITE2-E2E-IPSM-06 VoLTE MMS to UMTS MMS P1 MO-MMS-break out


TC-SITE2-E2E-IPSM-07 UMTS to VoLTE MMS P1 MT-MMS-break in

TC-SITE2-E2E-IPSM-08 MWI after VM deposit P1 MWI

TC-SITE2-E2E-IPSM-09 PLMN to VoLTE SMS P1 MT-SMS-break in

TC-SITE2-E2E-IPSM-10 PLMN to VoWiFi Trusted SMS P1 MT-SMS-break in

PLMN to VoWiFi Untrusted


TC-SITE2-E2E-IPSM-11 SMS P1 MT-SMS-break in
SMS over IP (IP-SM-GW/ vEMe) TOL using Toy Cell
Test Case Information
Steps

Action: Make sure UE-A has SMS MO/MT service in EDA


Action: Make sure UE-A is registered in LTE.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in EDA
Action: Make sure UE-A/B are registered in LTE.
Action: Send a test SMS from UE-A
Result: SMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in HLR
Action: Make sure UE-A is registered in LTE.
Action: Make sure UE-B is registered in UMTS.
Action: Send a test SMS from UE-A
Result: SMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-A has SMS MT service in HLR
Action: Make sure UE-B is registered in LTE.
Action: Make sure UE-A is registered in UMTS.
Action: Send a test SMS from UE-A
Result: SMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in external network.
Action: Make sure UE-A is registered in LTE.
Action: Make sure UE-B is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has SMS MO service in EDA


Action: Make sure UE-B has SMS MT service in HLR
Action: Make sure UE-A is registered in LTE.
Action: Make sure UE-B is registered in UMTS.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.
Action: Make sure UE-B has SMS MO service in EDA
Action: Make sure UE-A has SMS MT service in HLR
Action: Make sure UE-B is registered in LTE.
Action: Make sure UE-A is registered in UMTS.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-A has VM service in EDA


Action: Make sure UE-A is registered in LTE.
Action: call to VM from UE-A and leave a message.
Result: UE-A should get notice of a new VM received.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-B is registered in LTE.
Action: Make sure UE-A has SMS MT service in external network.
Action: Make sure UE-A is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-B is registered in WiFi.
Action: Make sure UE-A has SMS MT service in external network.
Action: Make sure UE-A is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.

Action: Make sure UE-B has SMS MO service in EDA


Action: Make sure UE-B is registered in WiFi.
Action: Make sure UE-A has SMS MT service in external network.
Action: Make sure UE-A is registered in external network.
Action: Send a test MMS from UE-A
Result: MMS-C center replied message sent and show on the screen, and UE-B should get messages
delivered.
) TOL using Toy Cell
Tracking
Pass Criteria Result Bluesky Witness
Ericsson Witness Date

UE-A registered with SMS service. To be Completed

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

MMS should be successfully sent and received To be Completed


on Ues

MMS should be successfully sent and received To be Completed


on Ues
MMS should be successfully sent and received To be Completed
on Ues

UE should be notified once VM received . To be Completed

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

SMS should be successfully sent and received To be Completed


on Ues

Pass 0 0
Pass with Comment 0 0
Failed 0 0
Not Applicable 0 0
To be Completed 11 total 0
Blocked 0
Total Test Cases 11
wifi 0
3G 4
AAT 0
VNC 0
manual 0
Tracking
Comment wifi 3G AAT VNC manual

x
x
ID Test Object

Verify UE
SES-E & FR-001
-Full Authentication

Verify UE
SES-E & FR-002 -Full Authentication
-With Valid Token

Verify UE
-Full Authentication
SES-E & FR-003
-Update emergency address from Iphone
vowifi option

Verify UE
-Full Authentication
SES-E & FR-004
-Update emergency address from Iphone
vowifi option with in-correct address

Verify UE
SES-E & FR-005
-AKA Token Expired & Renew AKA Token

Verify UE
SES-E & FR-006
-Full Authentication

Verify UE
SES-E & FR-007 -Full Authentication
-With Valid Token

Verify UE
-Full Authentication
SES-E & FR-008
-Update emergency address from samsung
vowifi option

Verify UE
-Full Authentication
SES-E & FR-009
-Update emergency address from samsung
vowifi option with in-correct address
Verify UE
SES-E & FR-010
-AKA Token Expired & Renew AKA Token

Verify UE
SES-E & FR-011
-Full Authentication with incorrect address

Verify UE
SES-E & FR-012
-Full Authentication with incorrect address

Verify VoWiFi UE profile is not present in


SES-VoWiFi-001
HSS

SES-VoWiFi-002 Verify VoWiFi UE is not present from CCDM

SES-VoWiFi-003 Verify VoWiFi UE is not entitled from CCDM

VoWiFi activation case :subscriber has not


accepted T&C & not provide the emergency
address
SES-VoWiFi-004
1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber has


accepted T&C but not provide the emergency
address
SES-VoWiFi-005
1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus
VoWiFi activation case : subscriber accepts
T&C & and provide the emergency address
SES-VoWiFi-006 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-007 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-008 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-009 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus
VoWiFi activation case : subscriber accepts
T&C & and provide the emergency address
SES-VoWiFi-010 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-011 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-012 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-013 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-014 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus
Pre-conditions Test Date Result
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to Update the emergency address with new
correct address.
5. Address Should be updated and VoWiFi should be enabled as it
is.
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber is already entiteled and tries to Update the
emergency address with new in-correct address.
5. Address Should be failed and and VoWiFi should be disabled.

1. Carrier bundle is installed in Apple device (iPhone). To be Completed


2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
To be Completed
1. Carrier bundle is installed in in Samsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Samsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Samsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to Update the emergency address with new
correct address.
5. Address Should be updated and VoWiFi should be enabled as it
is.
To be Completed
1. Carrier bundle is installed inSamsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber is already entiteled and tries to Update the
emergency address with new in-correct address.
5. Address Should be failed and and VoWiFi should be disabled.
1. Carrier bundle is installed in Samsung device To be Completed
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
1. Carrier bundle is installed in Apple device (iPhone). To be Completed
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
1. Carrier bundle is installed in Samsung device. To be Completed
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are not correctly configured in
HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are not defined in the CCDM.
4. Location Server is ready

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing does not have the VoWiFi
services active in the CCDM.
4. Location Server is ready

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 701
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 709
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 701 and RC2 Code as
709.
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 709 and RC1 Code as
701.
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB
To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 701 and RC2 Code as
802.
6. SubscriberVoWiFi should not be enabled on handset.
7. Emergency address data should not be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 709 and RC2 Code as
802.
6. SubscriberVoWiFi should not be enabled on handset.
7. Emergency address data should not be updated at Intrado DB

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Subscriber put the invalid characters in House Number.
6. Subscriberto get error from Websheet page.
7. Subscriber VoWiFi will not be enabled.

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Subscriber missed the ZIP code.
6. Subscriberto get error from Websheet page.
7. Subscriber VoWiFi will not be enabled.

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Subscriber missed the HNO/STN or MCN.
6. Subscriberto get error from Websheet page.
7. Subscriber VoWiFi will not be enabled.

Pass 0
Pass with Commen 0
Failed 0
Not Applicable 0
To be Completed 26
Blocked 0
Total Test Cases 26
Start Time End Time A-Msisdn A-IMSI B-Msisdn B-IMSI
Ericsson
Notes/Comments
ID Test Object

Verify UE
SES-E & FR-001
-Full Authentication

Verify UE
SES-E & FR-002 -Full Authentication
-With Valid Token

Verify UE
-Full Authentication
SES-E & FR-003
-Update emergency address from Iphone
vowifi option

Verify UE
-Full Authentication
SES-E & FR-004
-Update emergency address from Iphone
vowifi option with in-correct address

Verify UE
SES-E & FR-005
-AKA Token Expired & Renew AKA Token

Verify UE
SES-E & FR-006
-Full Authentication

Verify UE
SES-E & FR-007 -Full Authentication
-With Valid Token

Verify UE
-Full Authentication
SES-E & FR-008
-Update emergency address from samsung
vowifi option

Verify UE
-Full Authentication
SES-E & FR-009
-Update emergency address from samsung
vowifi option with in-correct address
Verify UE
SES-E & FR-010
-AKA Token Expired & Renew AKA Token

Verify UE
SES-E & FR-011
-Full Authentication with incorrect address

Verify UE
SES-E & FR-012
-Full Authentication with incorrect address

Verify VoWiFi UE profile is not present in


SES-VoWiFi-001
HSS

SES-VoWiFi-002 Verify VoWiFi UE is not present from CCDM

SES-VoWiFi-003 Verify VoWiFi UE is not entitled from CCDM

VoWiFi activation case :subscriber has not


accepted T&C & not provide the emergency
address
SES-VoWiFi-004
1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber has


accepted T&C but not provide the emergency
address
SES-VoWiFi-005
1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus
VoWiFi activation case : subscriber accepts
T&C & and provide the emergency address
SES-VoWiFi-006 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-007 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-008 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-009 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus
VoWiFi activation case : subscriber accepts
T&C & and provide the emergency address
SES-VoWiFi-010 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-011 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-012 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-013 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus

VoWiFi activation case : subscriber accepts


T&C & and provide the emergency address
SES-VoWiFi-014 1/getAuthentication
2/getEntitlement (vowifi)
3/getPhoneServiceAccountStatus
Pre-conditions Test Date Result
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to Update the emergency address with new
correct address.
5. Address Should be updated and VoWiFi should be enabled as it
is.
To be Completed
1. Carrier bundle is installed in Apple device (iPhone).
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber is already entiteled and tries to Update the
emergency address with new in-correct address.
5. Address Should be failed and and VoWiFi should be disabled.

1. Carrier bundle is installed in Apple device (iPhone). To be Completed


2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
To be Completed
1. Carrier bundle is installed in in Samsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Samsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. Carrier bundle is installed in Samsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to Update the emergency address with new
correct address.
5. Address Should be updated and VoWiFi should be enabled as it
is.
To be Completed
1. Carrier bundle is installed inSamsung device
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber is already entiteled and tries to Update the
emergency address with new in-correct address.
5. Address Should be failed and and VoWiFi should be disabled.
1. Carrier bundle is installed in Samsung device To be Completed
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
1. Carrier bundle is installed in Apple device (iPhone). To be Completed
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
1. Carrier bundle is installed in Samsung device. To be Completed
2. SES <-> AAA integration is done.
3. Test IMSI is present in HSS.
4. Subscriber tries to enable the VoWiFi on Device
To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are not correctly configured in
HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are not defined in the CCDM.
4. Location Server is ready

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing does not have the VoWiFi
services active in the CCDM.
4. Location Server is ready

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 701
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 709
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 701 and RC2 Code as
709.
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 709 and RC1 Code as
701.
6. Websheet Interaction to be successful.
7. SubscriberVoWiFi should be enabled on handset.
8. Emergency address data should be updated at Intrado DB
To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 701 and RC2 Code as
802.
6. SubscriberVoWiFi should not be enabled on handset.
7. Emergency address data should not be updated at Intrado DB

To be Completed

1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Intrado server provided the RC1 Code as 709 and RC2 Code as
802.
6. SubscriberVoWiFi should not be enabled on handset.
7. Emergency address data should not be updated at Intrado DB

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Subscriber put the invalid characters in House Number.
6. Subscriberto get error from Websheet page.
7. Subscriber VoWiFi will not be enabled.

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Subscriber missed the ZIP code.
6. Subscriberto get error from Websheet page.
7. Subscriber VoWiFi will not be enabled.

To be Completed
1. The UE used for the testing support VoWiFi, VoLTE call and
carrier bundle file is correctly installed.
2. The IMSIs (Subscribers) data are correctly configured in HSS.
3. The IMSIs used in the testing are defined in the CCDM.
4. Location Server is ready
5. Subscriber missed the HNO/STN or MCN.
6. Subscriberto get error from Websheet page.
7. Subscriber VoWiFi will not be enabled.

Pass 0
Pass with Commen 0
Failed 0
Not Applicable 0
To be Completed 26
Blocked 0
Total Test Cases 26
Start Time End Time A-Msisdn A-IMSI B-Msisdn B-IMSI
Ericsson
Notes/Comments
Test Case Info
TOL Ref./TC Ref. Test Object Name / Test Case Title
TC-Roam-01 LTE Roaming (Data)
TC-Roam-01.01 4G LTE Data Roaming International Allowed
(Bluesky outbound Subsciber)
TC-Roam-01.02 4G LTE Data Roaming International Not Allowed
(Bluesky outbound Subsciber)
TC-Roam-01.03 4G LTE Data Roaming National Allowed
(Bluesky outbound Subsciber)
TC-Roam-01.04 4G LTE Data Roaming National Not Allowed
(Bluesky outbound Subsciber)
TC-Roam-01.05 Inbound Roamer International Subscriber (4G)

TC-Roam-01.06 Inbound Roamer National Subscriber (4G)

TC-Roam-01.07 SGw CDR for inbound roamers

TC-Roam-01.08 PGw CDR for outbound Customer subscriber

TC-Roam-02 CS Roaming
TC-Roam-02.01 CS Voice/ 3G Data Roaming International Allowed
(Bluesky outbound Subsciber)

TC-Roam-02.02 CS Voice/ 3G Data Roaming International Not Allowed


(Bluesky outbound Subsciber)

TC-Roam-02.03 CS Voice/ 3G Data Roaming National Allowed


(Bluesky outbound Subsciber)
TC-Roam-02.04 CS Voice/ 3G Data Roaming National Not Allowed
(Bluesky outbound Subsciber)

TC-Roam-02.05 Outbound Roamer 3G SMS MT

TC-Roam-02.06 Outbound Roamer 3G SMS MO

TC-Roam-03 VoLTE (S8HR) Roaming - Outbound


TC-RoamOG-03.01 HSS Provisioning - Enable/Disable IMS subscription
TC-RoamOG-03.02 HSS Provisioning - Enable/Disable VoLTE Roaming
subscription
TC-RoamOG-03.03 HSS Provisioning - Enable/Disable Regional Roaming
blocks
TC-RoamOG-03.04 VoLTE IMS Registration
TC-RoamOG-03.05 VoLTE User Re-registration
TC-RoamOG-03.06 VoLTE User De-registration
TC-RoamOG-03.07 Network initiated De-registration - Administrative (HSS)
TC-RoamOG-03.08 Network initiated De-registration - Administrative (S-CSCF)

TC-RoamOG-03.09 Network initiated De-registration - Registration Timeout (S-


CSCF)
TC-RoamOG-03.10 MO Call - National Allowed - to HPLMN subscriber
TC-RoamOG-03.11 MO Call - National Allowed - to VPLMN subscriber

TC-RoamOG-03.12 MO Call - National Allowed - to PSTN subscriber

TC-RoamOG-03.13 MO Call - National Allowed - to Emergency (Local breakout)

TC-RoamOG-03.14 MO Call - National Allowed - to Toll-free Calls (Local


breakout) - as applicable and agreed in Roaming
Agreement
TC-RoamOG-03.15 MO Call - International Allowed - to HPLMN subscriber

TC-RoamOG-03.16 MO Call - International Allowed - to VPLMN subscriber

TC-RoamOG-03.17 MO Call - International Allowed - to PSTN subscriber

TC-RoamOG-03.18 MO Call - International Allowed - to Emergency (Local


breakout)
TC-RoamOG-03.19 MO Call - International Allowed - to Toll-free Calls (Local
breakout) - as applicable and agreed in Roaming
Agreement
TC-RoamOG-03.20 MT Call - National Allowed - from HPLMN subscriber

TC-RoamOG-03.21 MT Call - National Allowed - from VPLMN subscriber

TC-RoamOG-03.22 MT Call - National Allowed - from PSTN subscriber

TC-RoamOG-03.23 MT Call - National Allowed - from Emergency (Local


breakout)
TC-RoamOG-03.24 MT Call - National Allowed - from Toll-free Calls (Local
breakout) - as applicable and agreed in Roaming
Agreement
TC-RoamOG-03.25 MT Call - International Allowed - from HPLMN subscriber

TC-RoamOG-03.26 MT Call - International Allowed - from VPLMN subscriber

TC-RoamOG-03.27 MT Call - International Allowed - from PSTN subscriber

TC-RoamOG-03.28 MO SMS

TC-RoamOG-03.29 MT SMS

TC-RoamOG-03.30 XCAP (Ut-interface) - Enable supplementary services


TC-RoamOG-03.31 XCAP (Ut-interface) - Disable supplementary services
TC-RoamOG-03.32 XCAP (Ut-interface) - Interrogate supplementary services
TC-RoamOG-03.33 MO & MT Call Charging (Prepaid/ Online)
TC-RoamOG-03.34 MO & MT Call Charging (Postpaid/ Offline)
TC-RoamOG-03.35 S8HR Video Call
TC-RoamOG-03.36 Voice Mail deposit
TC-RoamOG-03.37 Voice Mail Retrieval from IMS
TC-RoamOG-03.38 Verification of Indications, Tones and Announcements
Wait,
Busy,
Hold,
Disconnect,
Low Balance,
Ringback
Service barred
Incorrect Dialing

TC-Roam-04 VoLTE (S8HR) Roaming - Inbound


TC-RoamOG-04.01 VoLTE S8HR Inbound Roamer (4G)

TC-RoamOG-04.02 Inbound Roamer Emergency Call

TC-RoamOG-04.03 Inbound Roamer Tollfree Calls


Roaming TOL using Toy C
Test Case Information
Description / Objective

Verify Bluesky subscriber can roam international and is


able to use 4G data as per defined policy
Verify Bluesky subscriber cannot roam international and is
not able to use 4G data as per defined policy
Verify Bluesky subscriber can roam national and is able to
use 4G data as per defined policy
Verify Bluesky subscriber cannot roam national and is not
able to use 4G data as per defined policy
Verify inbound roamer can browse 4G Data and 3G Voice
call on Bluesky network
Verify inbound roamer can browse 4G Data and 3G Voice
call on Bluesky network
The test case is to verify that the SGw CDRs are created
for the inbound LTE roamer
The test case is to verify that the PGw CDRs are created
for their outbound LTE roamer

Verify Bluesky subscriber can roam international and is


able to make a voice call and use data as per defined
policy
Verify Bluesky subscriber cannot roam international and is
not able to make a voice call and use data as per defined
policy
Verify Bluesky subscriber can roam national and is able to
make a voice call and use data as per defined policy
Verify Bluesky subscriber cannot roam national and is not
able to make a voice call and use data as per defined
policy
Verify Bluesky outbound subscriber is able to receive SMS
while roaming on 3G
Verify Bluesky outbound subscriber is able to send SMS
while roaming on 3G

HSS Provisioning - Enable/Disable IMS subscription


HSS Provisioning - Enable/Disable VoLTE Roaming
subscription
HSS Provisioning - Enable/Disable Regional Roaming
blocks
VoLTE IMS Registration
VoLTE User Re-registration
VoLTE User De-registration
Network initiated De-registration - Administrative (HSS)
Network initiated De-registration - Administrative (S-CSCF)

Network initiated De-registration - Registration Timeout (S-


CSCF)
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming

Verify Bluesky subscriber is able to roam international and


is able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam international and
is able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam international and
is able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam international and
is able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam international and
is able to make VoLTE call using S8HR roaming

Verify Bluesky subscriber is able to roam national and is


able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam national and is
able to make VoLTE call using S8HR roaming

Verify Bluesky subscriber is able to roam international and


is able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam international and
is able to make VoLTE call using S8HR roaming
Verify Bluesky subscriber is able to roam international and
is able to make VoLTE call using S8HR roaming
Verify Bluesky outbound subscriber is able to send SMS
while roaming on 4G
Verify Bluesky outbound subscriber is able to receive SMS
while roaming on 4G
XCAP (Ut-interface) - Enable supplementary services
XCAP (Ut-interface) - Disable supplementary services
XCAP (Ut-interface) - Interrogate supplementary services
MO & MT Call Charging (Prepaid/ Online)
MO & MT Call Charging (Postpaid/ Offline)
Video call
Voice mail deposit by an outbound S8HR roamer
Verify Voice Mail Retrieval from an outbound IMS
subscriber.
Verification of Indications, Tones and Announcements
Wait,
Busy,
Hold,
Disconnect,
Low Balance,
Ringback
Service barred
Incorrect Dialing

Verify inbound roamer can do a VoLTE S8HR call while


attached to Bluesky network
Verify inbound roamer can perform a VoLTE 911 call while
attached to the Bluesky network
Verify inbound roamer can perform a VoLTE Tollfree call
while attached to the Bluesky network - as applicable
according to the Roaming Agreement with the Partner
network.
Roaming TOL using Toy Cell
mation
Steps Pass Criteria Result

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed

To be Completed
To be Completed
To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed
To be Completed
To be Completed
To be Completed
To be Completed
To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

Pass 0
Conditional Pass 0
Failed 0
Not Applicable 0
To be Completed 55
Blocked 0
Total Test cases 55
Tracking
Customer Witness Ericsson Witness Date
Tracking
Comment wifi 3G AAT VNC

x
manual
TOL Ref./TC Ref. Test Object Name / Test Case Title
TC-Provisioning-01 Prepaid Subscriber
TC-Provisioning-01.01
Create Subscriber

TC-Provisioning-01.02

Modify Subscriber services

TC-Provisioning-01.03
Delete Subscriber

TC-Provisioning-02 Prepaid Subscriber


TC-Provisioning-02.01
Create Subscriber

TC-Provisioning-02.02

Modify Subscriber services

TC-Provisioning-02.03
Delete Subscriber
Description / Objective Steps

Create a new subscriber. All subscribers are assumed to


be ICS enabled. BSS-EDA should be able to define the
subscriber in all nodes (IMS/HSS, EPC/HSS, HLR/AUC,
MTAS, ENUM, SAPC, EIR)
Modify an existing subscriber.
Change IMSI and/or MSISDN,
provision and/or change supplementary services,
bar outgoing/ incoming services,
implement roaming restrictions,
suspend/resume etc.
Delete a subscriber/ end subscription. BSS-EDA should be
able to remove the subscriber data from all nodes
(IMS/HSS, EPC/HSS, HLR/AUC, MTAS, ENUM, SAPC,
EIR)

Create a new subscriber. All subscribers are assumed to


be ICS enabled. BSS-EDA should be able to define the
subscriber in all nodes (IMS/HSS, EPC/HSS, HLR/AUC,
MTAS, ENUM, SAPC, EIR)
Modify an existing subscriber.
Change IMSI and/or MSISDN,
provision and/or change supplementary services,
bar outgoing/ incoming services,
implement roaming restrictions,
suspend/resume etc.
Delete a subscriber/ end subscription. BSS-EDA should be
able to remove the subscriber data from all nodes
(IMS/HSS, EPC/HSS, HLR/AUC, MTAS, ENUM, SAPC,
EIR)
Pass Criteria Result Customer Witness Ericsson Witness

Subscriber created successfully as per To be Completed


objective. No error generated.

Change is implemented sucessfully as per To be Completed


objective. No error generated.

Deletion carried out successfully as per To be Completed


objective.

Subscriber created successfully as per To be Completed


objective. No error generated.

Change is implemented sucessfully as per To be Completed


objective. No error generated.

Deletion carried out successfully as per To be Completed


objective.

Pass 0
Conditional Pass 0
Failed 0
Not Applicable 0
To be Completed 6
Blocked 0
Total Test cases 6
wifi 0
3G 1
SAPC team 0
SI 0
Customer 0
Date Comment wifi 3G

x
AAT VNC manual
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
378 (402)

Test Case Information


Priority
TOL Ref. Test Object Name /
TC Ref. Test Case Title Level
(P1/P2)

TO-RED-01 Geo-Redundancy P-CSCF/A-SBG

TC-RED-01.01 IMS initial registration when SBG1 is down P1

TC-RED-01.02 IMS initial registration when SBG2 is down P1


TC-RED-01.03 IMS re-registration when SBG1 is down P1
TC-RED-01.04 IMS re-registration when SBG2 is down P1
TC-RED-01.05 VoLTE originating call when SBG1 is down P1

TC-RED-01.06 VoWifi originating call when SBG2 is down P1

TC-RED-01.07 VoWifi terminating call when SBG1 is down P1

TC-RED-01.08 VoLTE terminating call when SBG2 is down P1

TO-RED-02 Geo-Redundancy S-CSCF/I-CSCF/BGCF


TC-RED-02.01 VoLTE IMS initial registration when CSCF1 is down P1
TC-RED-02.02 VoWiFi IMS initial registration when CSCF2 is down P1
TC-RED-02.03 VoLTE IMS re-registration when CSCF1 is down P1
TC-RED-02.04 VoWiFi IMS re-registration when CSCF2 is down P1

TC-RED-02.05 VoLTE originating call when CSCF1 is down P1

TC-RED-02.06 VoWiFi originating call when CSCF2 is down P1

TC-RED-02.07 VoLTE terminating call when CSCF1 is down P1

TC-RED-02.08 VoWiFi terminating call when CSCF2 is down P1

TO-RED-03 Geo-Redundancy MTAS


TC-RED-03.01 VoLTE IMS registration from SITE1 when MTAS1 is down P1

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
379 (402)

TC-RED-03.02 VoWifi IMS registration from SITE2 when MTAS2 is P1


down
TC-RED-03.03 VoLTE originating call when MTAS1 is down P1
TC-RED-03.04 VoWifi originating call when MTAS2 is down P1
TC-RED-03.05 VoLTE terminating call when MTAS1 is down P1
TC-RED-03.06 Vowifi terminating call when MTAS2 is down P1
Routing XCAP messages to SITE2 MTAS when SITE1
TC-RED-03.07 MTAS unavailable P1
CF - Activation
Routing XCAP messages to SITE1 MTAS when SITE2
TC-RED-03.08 MTAS unavailable CF - Activation P1

TC-RED-03.09 Subscriber provisioning possible when MTAS1 is down P1

TC-RED-03.10 Subscriber provisioning possible when MTAS2 is down P1

TO-RED-04 Geo-Redundancy WMG (Trusted & Untrusted)


TC-RED-04.01 Site-1 UE to Site-2 WMG VoWiFi (Trusted) P1

Site-1 UE to Site-1 WMG VoWiFi, when Site-1 WMG


TC-RED-04.02 comes back up (Trusted) P1

TC-RED-04.03 Site-2 UE to Site-1 WMG VoWiFi (Trusted) P1

TC-RED-04.04 Site-2 UE to Site-2 WMG VoWiFi, when Site-2 WMG P1


comes back up (Trusted)

TC-RED-04.05 Site-1 UE to Site-2 WMG VoWiFi (Untrusted) P1

Site-1 UE to Site-1 WMG VoWiFi, when Site-1 WMG


TC-RED-04.06 comes back up (Untrusted) P1

TC-RED-04.07 Site-2 UE to Site-1 WMG VoWiFi (Untrusted) P1

TC-RED-04.08 Site-2 UE to Site-2 WMG VoWiFi, when Site-2 WMG


comes back up (Untrusted) P1
TO-RED-06 Geo-Redundancy AAA
TC-RED-06.01 VoWiFi (Trusted) attach when AAA-1 is down P1
TC-RED-06.02 VoWiFi (Trusted) attach when AAA-2 is down P1
TC-RED-06.03 VoWiFi (Untrusted) attach when AAA-1 is down P1
TC-RED-06.04 VoWiFi (Untrusted) attach when AAA-2 is down P1
TO-RED-07 Geo-Redundancy DNS/ENUM
TC-RED-07.01 VoLTE to VoLTE call when DNS/ENUM-1 is down P1
TC-RED-07.02 VoLTE to VoLTE call when DNS/ENUM-2 is down P1
TO-RED-08 Geo-Redundancy AFG - Cold Standby
TC-RED-08.01 Update Call Forwarding P1
TO-RED-09 Geo-Redundancy MRF (Not applicable for Bluesky since there is a single MRFP)
TC-RED-09.01 VoLTE originating conference call when MRF fails in P1
SITE1
VoLTE originating conference call when MRF fails in
TC-RED-09.02 SITE2 P1
TO-RED-10 Geo-Redundancy BGF
TC-RED-10.01 VoLTE to PSTN call when BGF in SITE1 unavailable P1

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
380 (402)

TC-RED-10.02 VoLTE to PSTN call when BGF in SITE2 unavailable P1


TC-RED-10.03 VoLTE to 911 call when BGF in SITE1 unavailable P1
TC-RED-10.04 VoLTE to 911 call when BGF in SITE2 unavailable P1
TO-RED-11 SAPC Failover
TC-RED-11.01 VoLTE originating call when SAPC fails in SITE1 P1
TC-RED-11.02 VoLTE originating call when SAPC fails in SITE2 P1
TC-RED-11.03 VoLTE 911 call when SAPC fails in SITE1 P1
TC-RED-11.04 VoLTE 911 call when SAPC fails in SITE2 P1
TO-RED-12 NELS Failover
TC-RED-12.01 Shutdown NELS 01 verify all traffic still carried on NELS P1
02
Shutdown NELS 02 verify all traffic still carried on NELS
TC-RED-12.02 01 P1

TO-RED-13 HSS Failover


TC-RED-13.01 VoLTE IMS Registration SITE1 HSS down P1
TC-RED-13.02 VoLTE to VoLTE call when HSS Site1 is down P1
TC-RED-13.03 VoLTE IMS Registration SITE2 HSS down P1
TC-RED-13.04 VoLTE to VoLTE call when HSS Site2 is down P1
TO-RED-14 HLR Failover
TC-RED-14.01 UMTS Registration SITE1 HLR down P1
TC-RED-14.02 UMTS to UMTS call when HLR Site1 is down P1
TC-RED-14.03 UMTS Registration SITE2 HLR down P1
TC-RED-14.04 UMTS to UMTS call when HLR Site2 is down P1
TO-RED-15 CCDM Failover

TC-RED-15.01 Fail HSS over to Site 2 CCDM P1

TO-RED-16 EIR
TC-RED-16.01 IMEI Check – Active EIR-FE unavailable - MAP P1

TC-RED-16.02 IMEI Check – Active EIR-FE unavailable – Diameter P1


TO-RED-17 Charging-related
TC-RED-17.01 SFTP Pull (Bluesky BSS pulls the files from SGw, PGw) P1
TC-RED-17.02 SFTP Push (MSC pushes the files to Bluesky BSS) P1
TC-RED-17.03 Diameter (IMS sends Diameter ACR to Bluesky BSS) P1
TC-RED-17.04 Diameter (IMS sends Diameter CCR to Bluesky BSS) P1
TO-RED-18 DSC Failover

TO-RED-18-01 P1
Verify the MME to DSC local Redundancy

TO-RED-18-02 P1
Verify the MME to DSC in a Geo Redundancy

TO-RED-18-03 P1
Verify the MTAS to DSC local redundancy

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
381 (402)

TO-RED-18-04 P1
Verify the MTAS to DSC in a Geo Redundancy

TO-RED-18-05 P1
Verify the PCRF to DSC local redundancy

TO-RED-18-06 P1
Verify the PCRF to DSC in a Geo Redundancy

TO-RED-18-07 P1
Verify the EPG to DSC local redundancy

TO-RED-18-08 P1
Verify the EPG DSC in a Geo Redundancy
TO-RED-18-09 Resilience verification (covers all peers of DSC) P1

TO-RED-19 MSC-S/ STP Failover


Fresh Location Update check when MSC1 (STP1) is
TO-RED-19-01 down P1

TO-RED-19-02 Fresh Location Update check when MSC2 (STP2) is P1


down

TO-RED-19-03 Mobile Originating Call check when MSC1 (STP1) is P1


down
Mobile Originating Call check when MSC2 (STP2) is
TO-RED-19-04 down P1

TO-RED-19-05 Mobile
down
Terminating Call check when MSC1 (STP1) is P1

TO-RED-19-06 Mobile Terminating Call check when MSC2 (STP2) is P1


down
TO-RED-19-07 SMS MO check when MSC1 (STP1) is down P1
TO-RED-19-08 SMS MO check when MSC2 (STP2) is down P1
TO-RED-19-09 SMS MT check when MSC1 (STP1) is down P1
TO-RED-19-10 SMS MT check when MSC2 (STP2) is down P1
TO-RED-19-11 Call Forwarding Activation/Deactivation when MSC1 P1
(STP1) is down
Call Forwarding Activation/Deactivation when MSC2
TO-RED-19-12 (STP2) is down P1

TO-RED-20 IP-SM-GW (EMe)


TO-RED-20-01 MAP Network Redundancy(at the STP) for MT SMS P1
TO-RED-20-02 MAP Network Redundancy(at the STP) for MT SMS P1
TO-RED-21 SGSN-MME
TO-RED-21-01 S1-MME redudancy P1

TO-RED-21-02 S11/S11-U redudancy P1

TO-RED-21-03 S6a redudancy P1

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
382 (402)

MME pool, successful GUTI Attach when MME is


TO-RED-21-04 OutOfService P1

TO-RED-21-05 MME Pool move - UE in ECM-Connected state P1

TO-RED-21-06 MME Pool move - UE in ECM-IDLE state P1

TO-RED-22 EPG
TO-RED-22-01 Site-1 UE/MME to Site-2 EPG P1

TO-RED-22-02 Site-2 UE/MME to Site-1 EPG when it comes back up P1

TO-RED-22-03 Site-2 UE/MME to Site-1 EPG P1

TO-RED-22-04 Site2 UE/MME to Site-2 EPG when it comes back up P1

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
383 (402)

Geo-Red VoLTE and VoWiFi TOL


Test Case Information
Acceptanc
e Test
Description / Objective Pass/fail Criteria Procedure
document
available

IMS subscriber able to register using SBG2


(Node Failure simulated by Locking the ASBG mobile_access interface to the
VNF)
IMS subscriber able to register using SBG1
IMS subscriber able to register using SBG2
IMS subscriber able to register using SBG1
UE registered in SITE1, failed just before originating a call triggers new
registeration with SITE2 IMS core, user need to originate the call again
UE registered in SITE2, failed just before originating a call triggers new
registeration with SITE1 IMS core, user need to originate the call again
UE registered in SITE1, failed just before receving the call, call given
diversion treatment. Termiating UE will triggers new registeration with SITE2
IMS core
UE registered in SITE2, failed just before receving the call, call given
diversion treatment. Termiating UE will triggers new registeration with SITE1
IMS core

VoLTE IMS subscriber able to register on CSCF2


VoLTE IMS subscriber able to register on CSCF1
VoLTE IMS subscriber able to re-register on CSCF2
VoLTE IMS subscriber able to re-register on CSCF1
UE registered in CSCF1. CSCF1 goes down just before originating a call. The
failed call triggers new registration with CSCF2 IMS core. The user needs to
originate the call again
UE registered in CSCF2. CSCF2 goes down just before originating a call. The
failed call triggers new registration with CSCF1 IMS core. The user needs to
originate the call again

UE registered in CSCF1. CSCF1 goes down just before receving the call, call
given diversion treatment. Termiating UE will trigger new registration with
CSCF2 IMS core

UE registered in CSCF2. CSCF2 goes down just before receving the call, call
given diversion treatment. Termiating UE will trigger new registration with
CSCF1 IMS core

Ensure MTAS2 is updated when MTAS1 is down.

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
384 (402)

Ensure MTAS1 is updated when MTAS2 is down.


VoLTE originating call able to be establish using the MTAS2
VoLTE originating call able to be establish using the MTAS in SITE1
VoLTE terminating call able to be establish using the MTAS in SITE2
VoLTE terminating call able to be establish using the MTAS in SITE1

Ensure users call forward feature is update on SITE2 MTAS when SITE1 MTAS
is unavailable.

Ensure users call forward feature is update on SITE1 MTAS when SITE2 MTAS
is unavailable.
Ensure subscriber provisioning is successful in SITE2 MTAS when SITE1 MTAS
is unavailable. Also ensure primary HSS in SITE1 is updated with the
appropriate information when the SITE2 MTAS becomes unavailable

Ensure subscriber provisioning is successful in SITE1 MTAS when SITE2 MTAS


is unavailable. Also ensure primary HSS in SITE1 is updated with the
appropriate information when the SITE2 MTAS becomes unavailable

To verify Site-1 UE able to establish succesful VoWiFi call with Site-2 WMG,
when Site-1 WMG is down
To verify Site-1 UE able to establish succesful VoWiFi call with Site-1 WMG,
when Site-1 WMG was down and comes back up.
To verify Site-2 UE able to establish succesful VoWiFi call with Site-1 WMG,
when Site-2 WMG is down
To verify Site-2 UE able to establish succesful VoWiFi call with Site-2 WMG,
when Site-2 WMG was down and comes back up.
To verify Site-1 UE able to establish succesful VoWiFi call with Site-2 WMG,
when Site-1 WMG is down
To verify Site-1 UE able to establish succesful VoWiFi call with Site-1 WMG,
when Site-1 WMG was down and comes back up.
To verify Site-2 UE able to establish succesful VoWiFi call with Site-1 WMG,
when Site-2 WMG is down
To verify Site-2 UE able to establish succesful VoWiFi call with Site-2 WMG,
when Site-2 WMG was down and comes back up.

VoWiFi attach is successful via AAA-2


VoWiFi attach is successful via AAA-1
VoWiFi attach is successful via AAA-2
VoWiFi attach is successful via AAA-1

SITE1 UE able to make VoLTE to VoLTE call when DNS/ENUM-1 is down


SITE2 UE able to make VoLTE to VoLTE call when DNS/ENUM-2 is down
The AFG is Active-Standy and requires manual switchover via DNS
Update CFU via menu on phone (XCAP)
there is a single MRFP)
VoLTE originating conference call able to be establish using the MRF in SITE2

VoLTE originating conference call able to be establish using the MRF in SITE1

VoLTE to PSTN call using the BGF-2

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
385 (402)

VoLTE to PSTN call using the BGF-1


VoLTE to 911 call using the BGF-2
VoLTE to 911 call using the BGF-1

VoLTE originating call able to be establish using the SAPC in SITE2


VoLTE originating call able to be establish using the SAPC in SITE1
VoLTE 911 call able to be establish using the SAPC in SITE2
VoLTE 911 call able to be establish using the SAPC in SITE1

Shutdown NELS01 verify all licesne still carried on NELS02

Shutdown NELS02 verify all licesne still carried on NELS01

Mobile able to register on site 1 via Site2 HSS


Call completes via Site2 HSS
Mobile able to register on site 2 via Site1 HSS
Call completes via Site1 HSS

Mobile able to register on site 1 via Site2 HLR


Call completes via Site2 HLR
When
Mobileactive
able toEIR-FE is unavailable,
register on site 2 viastandby EIR-FE can take over the requests
Site1 HLR
from Core Network.
Call
1: completes
Provision via Site1viaHLREMA with EquipmentListNumber equals to 2 and
When activethe IMEI-A
EIR-FE is unavailable, standby EIR-FE can take over the requests
do a re-check.
from Core Network.
2:
1: Check thethe
Provision dataIMEI-A
in CUDB.via EMA with EquipmentListNumber equals to 2 and
IMEI-A
do a created in CUDB with EquipmentListNumber equals to 2.
re-check.
Check vHSSFE put to failover mode once detecting all CCDM down.
3:
2: Start
Checkwireshark
the data in onCUDB.
PL-1 and PL-2
#IMEI-A
wireshark & in CUDB with EquipmentListNumber equals to 2.
created
Wireshark started on
3: Start wireshark on PL-1
PL-1 and
and PL-2
PL-2.
#4:wireshark
Turn on handset
& with IMEI-A.
Handset
Wireshark with IMEI-A
started onisPL-1
succesfully
and PL-2. “location updated” in the network.
5: Turn
4: Checkon the data inwith
handset CUDB via EMA.
IMEI-A.
The user with
Handset “location
IMEI-A updated” in the“location
is succesfully network.updated” in the network.
6:
5: Make
Check athe
calldata
to another
in CUDBtest via phone
EMA. (UE-B).
Call
The is successful.
user “locationRelease
updated” theincall.
the network.
7: Make
6: Stop wireshark on PL-1 test
a call to another and phone
PL-2 (UE-B).
Wireshark stopped
Call is successful. on PL-1
Release and
the PL-2.
call.
8:
7: Check on the wireshark
Stop wireshark on PL-1 and signaling
PL-2 trace and look for the equipmentStatus.
equipmentStatus
Wireshark stopped shows greyListed.
on PL-1 and PL-2.
41:Check
8: DeleteonIMEI-A via EMA.signaling trace and look for the equipmentStatus.
the wireshark
IMEI-A deleted from
equipmentStatus showsCUDB.
greyListed.
42: Delete IMEI-A via EMA.
IMEI-A deleted from CUDB.
Verify that if the Diameter connection is down from both MMEs to
DSC1 when peers are locked here, the end-to-end traffic MME-HSS is
still possible through Mated DSC2 connection.
Verify that if the Diameter connection is down from both MMEs to
DSC1 while it is rebooted, the end-to-end traffic MME-HSS is still
possible through Mated DSC2 connection.
Verify that if the Diameter connection is down from the OCSs to DSC1
when peers are locked here, the end-to-end traffic MTAS-OCS is still
possible through Mated DSC2 connection.

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
386 (402)

Verify that if the Diameter connection is down from the OCSs to DSC1
while it is rebooted, the end-to-end traffic MTAS-OCS is still possible
through Mated DSC2 connection.
Verify that if the Diameter connection is down from the OCSs to DSC1
when peers are locked here, the end-to-end traffic PCRF-OCS is still
possible through Mated DSC2 connection.
Verify that if the Diameter connection is down from the OCSs to DSC1
while it is rebooted, the end-to-end traffic OCS-PCRF is still possible
through Mated DSC2 connection.
Verify that if the Diameter connection is down from the EPGs to DSC1
when peers are locked here, the end-to-end traffic EPG-DSC is still
possible through Mated DSC2 connection.
Verify that if the Diameter connection is down from the OCSs to DSC1
while it is rebooted, the end-to-end traffic OCS-EPG is still possible
through Mated DSC2 connection.
Block the DSC active and verify the mate DSC takes the traffic of the remote
peers

UMTS - Able to Fresh Location Update using MSC2 (STP2)

UMTS - Able to Fresh Location Update using MSC1 (STP1)

UMTS - Able to Mobile Originating Call using MSC2 (STP2)

UMTS - Able to Mobile Originating Call using MSC1 (STP1)

UMTS - Able to Mobile Terminating Call using MSC2 (STP2)

UMTS - Able to Mobile Terminating Call using MSC1 (STP1)


IMS - Able to SMS MO using MSC2 (STP2)
IMS - Able to SMS MO using MSC1 (STP1)
IMS - Able to SMS MT using MSC2 (STP2)
IMS - Able to SMS MT using MSC1 (STP1)
UMTS - Able to Call Forwarding Activation/Deactivation using MSC2 (STP2)

UMTS - Able to Call Forwarding Activation/Deactivation using MSC1 (STP1)

Take Down link toward IP-SM Site 1, make IMS-SMS call


Take Down link toward IP-SM Site 2, make IMS-SMS call

The test case is to verify S1-MME logical interface redundancy and


functionality.
The test case is to verify S11 and S11-U logical interface redundancy and
functionality.

The test case is to verify S6a logical interface redundancy and functionality.

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
387 (402)

The purpose of this test is to demonstrate that eNodeB will select a new
available MME within the pool during a GUTI Attach if the original MME
where the UE was attached is not reachable anymore.
The purpose of this test is to demonstrate successful move of the UE
registration between MMEs in pool using CLI command when UE is in ECM-
CONNECTED state.
The purpose of this test is to demonstrate successful move of the UE
registration between MMEs in pool using CLI command when UE is in ECM-
IDLE state

To verify PDN session and browsing can be established with UE attached to


Site-1 MME & Site-2 EPG when Site-1 EPG is unavailable.
To verify PDN session and browsing can be established with UE attached to
Site-1 MME & Site-1 EPG when Site-1 EPG was unavailable, then comes
back up.
To verify PDN session and browsing can be established with UE attached to
Site-2 MME & Site-1 EPG when Site-2 EPG is unavailable.
To verify PDN session and browsing can be established with UE attached to
Site-2 MME & Site-2 EPG when Site-2 EPG was unavailable, then comes
back up.

Pass
Conditional Pass
Failed
Not Applicable
To be Completed
Blocked
Total Test cases
wifi
3G
AAT
VNC
manual

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
388 (402)

d VoWiFi TOL
Tracking

Bluesky Ericsson Scheduled Test


Test Result Witness Witness Date

To be Completed

To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
389 (402)

To be Completed
To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed
To be Completed
To be Completed

To be Completed
To be Completed

To be Completed

Not Applicable

Not Applicable

To be Completed

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
390 (402)

To be Completed
To be Completed
To be Completed

To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed

To be Completed
To be Completed
To be Completed
To be Completed

To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
391 (402)

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed
To be Completed
To be Completed
To be Completed
To be Completed
To be Completed

To be Completed

To be Completed
To be Completed

To be Completed

To be Completed

To be Completed

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
392 (402)

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

To be Completed

0 0
0 0
0 0
2 0
99 0
0 total 0
101
23
0
0
0
0

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
393 (402)

Tracking

Comments wifi 3G

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
394 (402)

x
x
x
x

x
x

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
395 (402)

HSS_CUDB_Failover.txt

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
396 (402)

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
397 (402)

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
398 (402)

AAT VNC manual

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
399 (402)

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
400 (402)

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
401 (402)

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal
TEST OBJECT LIST_x000D_SouthernLINC VoLTE/VoWiFi Test Object List
402 (402)

Date: 2016-10-13
Prepared: EBRISPE BRIAN SPENCER
Sheet: Inter-Site Redundancy _x000D_Rev: PA1
Ericsson Internal

You might also like