NETONE - Flexi Network Server - MME - Acceptance - Test - Plan v5.0.2.3

Flexi Network Server
Acceptance Test Doment

Release: NS 3.0 1.0
1
Nokia Solutions and Networks is continually striving to reduce the adverse environmental
effects of its products and services. We would like to encourage you as our customers and
users to join us in working towards a cleaner, safer environment. Please recycle product
packaging and follow the recommendations for power use and proper disposal of our
products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental
services we offer, please contact us at Nokia Solutions and Networks for additional
information.
2
Table of Contents
1 Acceptance test cases................................................................................................................................. 6

1.1 System maintenance................................................................................................................................................. 6
1.1.1 OMU switchover.................................................................................................................................. 6
1.1.2 MCHU switchover............................................................................................................................... 7
1.1.3 IPDU switchover.................................................................................................................................. 8
1.1.4 MMDU restart /spontaneous restart....................................................................................................9
1.1.5 MCHU restart /spontaneous restart..................................................................................................10
1.1.6 CPPU restart / spontaneous restart..................................................................................................11
1.1.7 IPDU restart / spontaneous restart....................................................................................................12
1.1.8 System restart................................................................................................................................... 13
1.1.9 Ethernet port redundancy - IPDU......................................................................................................14
1.1.10 Ethernet port redundancy – CPPU....................................................................................................15
1.1.11 Ethernet port redundancy – MMDU..................................................................................................16
1.1.12 Ethernet port redundancy – PAPU....................................................................................................17
1.1.13 Ethernet port redundancy – GBU......................................................................................................18
1.1.14 Ethernet port redundancy – IPPU.....................................................................................................19
1.1.15 Attach, CPPU restart, HSS detach....................................................................................................20
1.1.16 Attach, CPPU restart, UE initiated detach.........................................................................................21
1.1.17 Alarm handling.................................................................................................................................. 22
1.1.18 MML Command Log.......................................................................................................................... 23
1.1.19 Measurement handling...................................................................................................................... 24
1.1.20 SSH and SFTP - Configuring............................................................................................................25
1.1.21 2 shelfs; link between SWU0-SWU2 broken.....................................................................................27
1.1.22 2 shelfs; link between SWU1-SWU3 broken.....................................................................................28
1.1.23 MME restart – IP connectivity...........................................................................................................29
1.1.24 AHUB restart – IP connectivity.........................................................................................................30
1.1.25 LAG member down (AHUB- AHUB)..................................................................................................31
1.1.26 LAG member down (AHUB- RTR)....................................................................................................32
1.1.27 Primary SCTP path broken...............................................................................................................33
1.1.28 CPPU Blade Removal....................................................................................................................... 34
1.1.29 IPDU Blade Removal........................................................................................................................ 35
1.1.30 MMDU Blade Removal...................................................................................................................... 36
1.1.31 OMU Blade Removal........................................................................................................................ 37
1.1.32 MCHU blade removal........................................................................................................................ 38
1.1.33 Power Supply Redundancy...............................................................................................................40
1.2 Interface testing....................................................................................................................................................... 41
1.2.1 S1 setup, no subscribers in MME.....................................................................................................41
1.2.2 S1 setup............................................................................................................................................ 42
1.2.3 S1 Flex - MME configuration update.................................................................................................43
1.2.4 Echo Request on S11 interface initiated by SGW.............................................................................44
1.2.5 S11 Load Balancing.......................................................................................................................... 45
1.2.6 SCTP multihoming for S1.................................................................................................................. 46
1.2.7 OSS – Alarm forwarding to OSS.......................................................................................................47
1.3 Mobility and session management.......................................................................................................................... 48
1.3.1 Attach with IMSI – no IMEISV in SMC..............................................................................................48
1.3.2 Attach with IMSI – IMEISV in SMC...................................................................................................50
1.3.3 Attach with GUTI............................................................................................................................... 52
1.3.4 IMEI sending to HSS......................................................................................................................... 54
1.3.5 IMSI attach with SMP (correct ciphering)..........................................................................................55
1.3.6 Dynamically selected NAS security algorithm...................................................................................57
1.3.7 Double attach.................................................................................................................................... 58
1.3.8 Attach Reject - IMSI Unknown (HSS)...............................................................................................60
1.3.9 Attach Reject - IMSI Unknown (AuC)................................................................................................61
1.3.10 Attach Reject - IMSI analysis is missing...........................................................................................62
1.3.11 Attach with IMSI – two home PLMNs configured in MME.................................................................63
1.3.12 Attach with unknown GUTI (GUTI reallocation)................................................................................65
1.3.13 Attach Reject - SGW responses with error cause to create session request....................................67
1.3.14 UE initiated service request..............................................................................................................68
1.3.15 NW initiated service request (Paging)...............................................................................................68
1.3.16 UE initiated detach - UE in ECM idle state........................................................................................70
1.3.17 Network initiated (O&M) detach - UE in ECM connected state.........................................................71
1.3.18 Network initiated (O&M) detach to UE - UE in ECM idle state..........................................................72
1.3.19 HSS initiated detach – UE in ECM connected state.........................................................................72
1.3.20 HSS initiated detach – UE in ECM idle state....................................................................................74
3
1.3.21 S6A, Delete Subscriber Data............................................................................................................75
1.3.22 Cancel Location – UE in EMM deregistered state............................................................................76
1.3.23 UE initiated detach (UE power OFF).................................................................................................77
1.3.24 Delete Bearer Request from SGW – UE in ECM connected state....................................................78
1.3.25 Delete Bearer Request from SGW – UE in ECM idle state...............................................................79
1.3.26 Periodic Tracking Area Update.........................................................................................................80
1.3.27 TAU with S-GW relocation................................................................................................................ 81
1.4 Triple Access........................................................................................................................................................... 82
1.4.1 Attach and detach in 4G, Attach in 3G..............................................................................................82
1.5 QoS.......................................................................................................................................................................... 83
1.5.1 MME uses QoS parameters from HSS in default bearer creation....................................................83
1.5.2 HSS initiated QoS change (UE-AMBR) – UE in ECM connected state............................................85
1.5.3 HSS initiated QoS change (UE-AMBR) – UE in ECM idle state.......................................................86
1.5.4 HSS initiated QoS change (APN-AMBR) – UE in ECM connected state..........................................88
1.5.5 HSS initiated QoS change (APN-AMBR) – UE in ECM idle state.....................................................89
1.5.6 P-GW initiated QCI and ARP change in connected state.................................................................91
1.5.7 P-GW initiated TFT or APN-AMBR in connected state.....................................................................92
1.5.8 P-GW initiated QCI and APN-AMBR change in idle mode...............................................................93
1.6 DNS......................................................................................................................................................................... 94
1.6.1 SGW and PGW selection using DNS query......................................................................................94
1.6.2 PGW selection - HSS provides PGW IP address.............................................................................95
1.7 APN from UE during attach..................................................................................................................................... 97
1.7.1 Attach when UE provides APN.........................................................................................................97
1.7.2 Normal attach without ESM information Transfer flag.......................................................................99
1.7.3 ESM information transfer flag received but PRFILE is OFF............................................................100
1.7.4 UE provided invalid APN with APN overriding ON..........................................................................101
1.7.5 UE provides empty APN and APN overriding OFF.........................................................................103
1.7.6 UE provides invalid APN and APN overriding OFF.........................................................................104
1.8 HSS redundancy.................................................................................................................................................... 105
1.8.1 2 HSS connections for same realm.................................................................................................105
1.8.2 2 HSS connections for same realm, connection failure..................................................................107
1.8.3 2 HSS connections for same realm, connection failure second link...............................................108
1.9 DNS based load balancing.................................................................................................................................... 109
1.9.1 MME chooses the correct SGW/PGW pair for Attach.....................................................................109
1.10 Circuit switched fallback; CSFB............................................................................................................................. 110
1.10.1 MO CSFB to GERAN, UE in active mode.......................................................................................110
1.10.2 MO CSFB to GERAN, UE in idle mode...........................................................................................113
1.10.3 MT CSFB to GERAN, UE in active mode.......................................................................................115
1.10.4 MT CSFB to GERAN, UE in idle mode...........................................................................................117
1.10.5 MO CSFB to UTRAN, UE in active mode.......................................................................................119
1.10.6 MO CSFB to UTRAN, UE in idle mode...........................................................................................121
1.10.7 MT CSFB to UTRAN, UE in active mode........................................................................................123
1.10.8 MT CSFB to UTRAN, UE in idle mode...........................................................................................125
1.11 Additional Tests:.................................................................................................................................................... 126
1.11.1 MO SMS to UTRAN/GERAN- UE Active and Idle...........................................................................126
1.11.2 MT SMS to UTRAN/GERAN, UE Active and Idle Mode.................................................................126
1.11.3 MO USSD to GERAN/UTRAN, UE in active/idle mode..................................................................127
1.11.4 Check of features compared with BOQ content..............................................................................127
4
Purpose:
This document serves to certify that the Nokia Flexi NS was tested according to the Acceptance Test Document
and reports the outcome of the tests therein. It serves to demonstrate that the Flexi NS was tested and is working
as expected.
5
1 ACCEPTANCE TEST CASES
1.1 System maintenance

1.1.1 OMU switchover
1. Description
The purpose of this test case is to make switchover between OMUs and verify that switchover is working.
2. Required test environment
- MME
3. Preconditions
- OMU-<X> is WO-EX state and OMU-<Y> is SP-EX state
4. Guides for execution
- Make OMU switchover (MML-command: ZUSC:OMU,<WO-EX>:SP:;)

- Verify that switchover is successfully (MML-command: ZUSI:OMU;)
5. Expected results
- OMU switchover is successful. Verify that using MML-command: ZUSI:OMU;

- No unexpected alarms related to switchover.
6
1.1.2 MCHU switchover
1. Description
The purpose of this test case is to make switchover between MCHUs and verify that switchover is working.
- MME
- HSS
- SAE-GW
- EnodeB
- UE
3. Preconditions
- MCHU-<X> is WO-EX state and MCHU-<Y> is SP-EX state
- Make attach
- Make MCHU switchover (MML-command: ZUSC:MCHU,<WO-EX>:SP:;)
- Make detach
5. Expected results
- Attach is successful
- MCHU switchover is successful ZUSI:MCHU;. No unexpected alarms or computer logs.
- Detach is successful
7
1.1.3 IPDU switchover
1. Description
The purpose of this test case is to make switchover between IPDUs and verify that switchover is working.
- MME
- HSS
- SAE-GW
- EnodeB
- UE
3. Preconditions
- IPDU-<X> is WO-EX state and IPDU-<Y> is SP-EX state
- Make attach
- Make IPDU switchover (MML-command: ZUSC:IPDU,<WO-EX>:SP:;)
- Make detach
5. Expected results
- IPDU switchover is successful ZUSI:IPDU;. No unexpected alarms.
8
1.1.4 MMDU restart /spontaneous restart
1. Description
Purpose of this test case is to ensure that if MMDU which is serving subscriber goes down other MMDU in same
MMDU pair will handle subscriber while other MMDU is down.
In this case after attach MMDU restart is made to that MMDU which is serving attached subscriber. While MMDU
restart is ongoing subscriber makes TAU and after successful TAU subscriber makes detach. Procedures after
restart are now handled by another MMDU in same MMDU pair.
- MME
- eNodeB
- HSS
- SaeGW
- UE
3. Preconditions
- UE makes attach.
- Check from MME the serving MMDU and that the status of subscriber is ‘connected’ before, during and after
MMDU restart: (MML-command ZMMO:IMSI=xxxxxxxx;)
- MMDU restart for same MMDU which is serving attached subscriber (ZUSU:MMDU,x,)
- Ue makes TAU with no bearer establishment requested
- UE makes detach
-repeat test by executing a spontaneous restart for serving MMDU (e.g. pressing reset button)
5. Expected results
After MMDU restart another MMDU is successfully handling subscriber which serving MMDU is down.
eNodeB MME HSS SGW
*-------------------------------------------------------------------------------------------*
| Normal attach for subscriber |
*-------------------------------------------------------------------------------------------*
/////MMDU restart
TAU
-----------------------------> Tracking Area Update Request (active flag

OFF)
<---------------------------- Tracking Area Update Accept
-----------------------------> Tracking Area Update complete
*-------------------------------------------------------------------------------------------*
| Normal detach for subscriber |
*-------------------------------------------------------------------------------------------*
9
1.1.5 MCHU restart /spontaneous restart
1. Description
The purpose of this test case is to make a restart to active MCHU and verify that the units are recovered from it.
- MME
3. Preconditions
- Copy databases to disk:

ZDBC:EQUIPM,0:;
ZDBC:OEDATA,0:;
ZDBC:GPDATA,0:;
ZDBC:ILDATA,0:;
- Make MCHU restart (MML-command: ZUSU:MCHU,<WO-EX>;).
--repeat test by executing a spontaneous restart for WO-EX MCHU (e.g. pressing reset button)
5. Expected results
- All restarted units are recovered from active MCHU restart. Verify that using MML-command: ZUSI:COMP;
10
1.1.6 CPPU restart / spontaneous restart
1. Description
Purpose of this test case is to ensure that MME works correctly after CPPU restart.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Check from MME that the status of subscriber is ‘connected’: (MML-command ZMMO:IMSI=xxxxxxxx;)
- Give CPPU restart (MML-command: ZUSU:CPPU,<WO-EX>;)
- Make detach after CPPU comes up
-repeat test by executing a spontaneous restart for WO-EX CPPU (e.g. pressing reset button)
5. Expected results
- CPPU comes up successfully
eNodeB MME SGW
*---------------------------------------------------------*
*---------------------------------------------------------*
CPPU restart
CPPU up
*---------------------------------------------------------*
*---------------------------------------------------------*
11
1.1.7 IPDU restart / spontaneous restart.
1. Description
Purpose of this test case is to ensure that MME works correctly after IPDU restart. UE is in ECM Connected
state.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
-
- Make attach
- Give IPDU restart (MML-command: ZUSU:IPDU,<WO-EX>;)
- After IPDU/SCTP connection up, S1-SETUP from eNB.
- Transfer uplink data. This will trigger UE Initiated Service Request
- Make detach
-repeat test by executing a spontaneous restart for WO-EX IPDU (e.g. pressing reset button)
5. Expected results
- S1 Setup procedure is successful after IPDU comes up
- Uplink data will trigger UE initiated service request successfully
eNodeB MME SGW
*---------------------------------------------------------*
*---------------------------------------------------------*
IPDU restart
IPDU/SCTP connection up
-----------------------------> Release Access Bearer Request
<----------------------------- Release Access Bearer Response
-------------------------> S1 Setup Request

<------------------------ S1 Setup Response
------------------------> Service Request.
<------------------------ Initial Context Setup Request

------------------------> Initial Context Setup Response
------------------------------> Modify Bearer Request

<------------------------------ Modify Bearer Response
*---------------------------------------------------------*
12
1.1.8 System restart
1. Description
The purpose of this test case is to make a system restart to the MME and verify that the units are recovered from
it.
- MME
3. Preconditions
- Copy databases to disk:

ZDBC:EQUIPM,0:;
ZDBC:OEDATA,0:;
ZDBC:GPDATA,0:;
ZDBC:ILDATA,0:;
- Make System Restart (MML-command: ZUSS:SYM:C=DSK;)
5. Expected results
- Units are recovered from system restart. Verify that using MML-command: ZUSI:COMP;. No related alarms
after system recovery.
13
1.1.9 Ethernet port redundancy - IPDU
1. Description
Verify redundancy of S1,S6a and S11 interfaces connected to IPDU blade.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
Basic configuration
- Disable active interface in IPDU unit (ZQRI)

- If there is direct external connection from IPDU, this can be done for example pulling out physical cable
of active interface
- If external connectivity is via AHUB, thia can be done for example blocking port of IPDU active
interface from AHUB
- Check that system performed interface switchover (ZQRI)
- Check that traffic is now handled by redundant interface
5. Expected results
-Disabling is succesfull
-Interface switchover was succesfull
-S1,S6a,S11 traffic are handled by redundant physical interface
14
1.1.10 Ethernet port redundancy – CPPU
1. Description
Verify redundancy of Ethernet interface in CPPU unit
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
Basic configuration
- Disable active interface in CPPU unit (ZQRI)

- This can be done for example blocking port of CPPU active interface from AHUB
5. Expected results
- Disabling is succesfull
- Interface switchover was succesfull
- traffic is handled by redundant physical interface
15
1.1.11 Ethernet port redundancy – MMDU
1. Description
Verify redundancy of Ethernet interface in MMDU unit
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
Basic configuration
- Disable active interface in MMDU unit (ZQRI)

- This can be done for example blocking port of MMDU active interface from AHUB
5. Expected results
-Disabling is succesfull
-Interface switchover was succesfull
-traffic is handled by redundant physical interface
16
1.1.12 Ethernet port redundancy – PAPU
1. Description
Verify redundancy of Ethernet interface in PAPU unit
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
Basic configuration
- Disable active interface in PAPU unit (ZQRI)

- This can be done for example blocking port of PAPU active interface from AHUB
5. Expected results
17
1.1.13 Ethernet port redundancy – GBU
1. Description
Verify redundancy of Ethernet interface in GBU unit
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
Basic configuration
- Disable active interface in GBU unit (ZQRI)

- This can be done for example blocking port of GBU active interface from AHUB
5. Expected results
18
1.1.14 Ethernet port redundancy – IPPU
1. Description
Verify redundancy of Ethernet interface in IPPU unit
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
Basic configuration
- Disable active interface in IPPU unit (ZQRI)

- This can be done for example blocking port of IPPU active interface from AHUB
5. Expected results
- traffic are handled by redundant physical interface
19
1.1.15 Attach, CPPU restart, HSS detach
1. Description
Purpose of this test case is to ensure that MME works correctly in case of that two CPPUs are in WO-EX. In this
case HSS detach after CPPU restart is handled by different CPPU than used in attach.
- MME (with two WO-EX CPPU)

- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- CPPU restart
- HSS detach during CPPU restart
5. Expected results
- Check that different CPPU was used in different procedures. For example attach in CPPU-0 and HSS detach in
CPPU-1.
eNodeB MME HSS SGW
*---------------------------------------------------------------------------------------------*
*---------------------------------------------------------------------------------------------*
///// CPPU restart /////
<-------------------------- Cancel Location Request
<----------------------------- Detach Request

-----------------------------> Detach Accept
-------------------------> Cancel Location Answer
<----------------------------- UE Context Release Command

-----------------------------> UE Context Release Complete
20
1.1.16 Attach, CPPU restart, UE initiated detach
1. Description
Purpose of this test case is to ensure that MME works correctly in case of that two CPPUs are in WO-EX. In this
case UE initiated detach after CPPU restart is handled by different CPPU than used in attach.
- MME (with two WO-EX CPPU)

- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Used CPPU can be checked from CPPU’s TRhandler logs. Take both logs using ‘tail –f mmeTRHandler0.log’
command.
- CPPU restart
- UE makes detach during CPPU restart
5. Expected results
- Check that different CPPU was used in different procedures. For example attach in CPPU-0 and detach in
CPPU-1.
eNodeB MME HSS SGW
*---------------------------------------------------------------------------------------------*
*---------------------------------------------------------------------------------------------*
///// CPPU restart /////
-----------------------------> Detach Request
-----------------------------------------------> Delete Session Request

<---------------------------------------------- Delete Session Response
<---------------------------- Detach Accept
<---------------------------- UE Context Release Command

21
1.1.17 Alarm handling
1. Description
Purpose of this test case is to ensure that basic alarm handing is working correctly.
- MME
3. Preconditions
- Check active alarms (MML-command ZAHO;)

- Check alarm history (MML-command ZAHP;)
- Cancel active alarms (MML-command ZACA;)
5. Expected results
- Active alarms are displayed correctly

- Alarm history is displayed correctly
- Alarm cancellation works
22
1.1.18 MML Command Log
1. Description
Purpose of this test case is to ensure that MML command log works correctly.
- MME
3. Preconditions
- Check MML Command Log (MML-command ZIGO;)

- Give a few MML-commands, e.g.
- ZAHO;
- ZUSI;
- ZISI;
- Check again that given commands are stored in to the MML Command Log (MML-command ZIGO;)
5. Expected results
- MML command log can be displayed

- New commands can be added to command log
23
1.1.19 Measurement handling
1. Description
Purpose of this test case is to ensure that attach and detach related counters works correctly.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Create measurements for Mobility Management Transaction Measurement (MMMT) and Session Management
Transaction Measurement (SMMT) (MML-command ZTPM)
- Start both measurements (MML-command ZTPS)
- Make attach and detach at least.
- (make additional tests for example TAU, PTAU, service request, paging, path switch X2)
- Stop both measurements (MML-command ZTPE)
- Interrogate test related counters (MML-command ZTPP)
5. Expected results
- Verify that counter values are changed correctly with ZTPP –command.
24
1.1.20 SSH and SFTP - Configuring
1. Description
Purpose of this test case is to ensure that SSH and SFTP features can be activated and that SSH server can be
configured.
- MME
- SSH client (e.g. PuTTy)
3. Preconditions
In the beginning of the test, SSH and SFTP feature activation status must be DEACTIVATED.
Commands should be executed in following order:
- Check if SSH feature is activated:

ZWOS:58,;
- If not, the activate SSH feature with MML command:

ZWOA:58,2,A;
- Check that SSH feature was activated:

ZWOS:58,;
- Check existing keys:

ZQ4L;
- If required RSA and DSA keys do not exist, generate them with following MML commands. Names of keys can
be chosen by user:
ZI2K:RSAPUBKEY,RSAPRIKEY:RSA:1024:;
ZI2K:DSAPUBKEY,DSAPRIKEY:DSA:1024:;
- Check that keys were created:

ZQ4L:;
- Configure SSH server with following MML command, use same keys which were generated with I2K command:
ZI2S:IPV4STATE=ON,IPV4PORT=22:IPV6STATE=OFF:RSAKEY=RSAPRIKEY,DSAKEY=DSAPRIKEY:;
-Check configuration:
ZI2H:PROTOCOL=SSH:;
- Give SFTP rights to used profile with following MML command:

ZIAA:PROFILE:ALL=250:::FTP=W:;
- Activate SFTP feature with the following MML command:

ZWOA:58:3:A:;
- Check that activation was succeed:

WOS:58,;
- Set SFTP state ON with following MML command

ZI2Q:STATE=ON;
- Check SFTP configuration:

ZI2H:PROTOCOL=SFTP:;
- Interrogate network status:

QRS:OMU,0::::;
25
- Open SSH connection to OMU (MML session) using SSH client (e.g. PuTTY). When SSH connection is opened
very first time, client informs user about new server information and asks if the server is trusted or not
- Check status:
QRS:OMU,0:::SYM=:;
-Take SFTP connection to OMU. When SFTP connection is opened very first time, client informs user about new
server information and asks if the server is trusted or not
- Check status:
QRS:OMU,0:::SYM=:;
5. Expected results
- Activation of SSH feature succeeds.

- Activation of SFTP feature succeeds
- Configuration of SSH server succeed when SSH feature is activated
- SFTP connection succeeds
- MML session over SSH succeeds
- Command execution is successful
26
1.1.21 2 shelfs; link between SWU0-SWU2 broken
1. Description
This test case verifies that internal connectivity is working while link between SWU-0 and SWU-2 is broken.
- Nokia Solutions and Networks Flexi NS - MME configured according IP connectivity guidelines for ATCA HW
- 2 shelf configuration
3. Preconditions
- Verify active alarms and clear unit logs in MME

- Verify that MMDU-0 and MMDU-2 are using el0 for internal IP
1. Verify that connections between units and AHUB is working (Check port statuses SWU-0 àenable fi
SWU-0(enable-fi)# àshow port)
2. Verify that ping is working from MMDU-0 to MMDU-2 (example:
ZQRX:MMDU,0::PING:IP="169.254.255.50",SRC="169.254.255.1";)
3. Shutdown link between SWU-0 and SWU-2
SWU-0(enable-fi)#
SWU-0(enable-fi)-->conf terminal
SWU-0(config-fi)àbridge
SWU-0 (bridge-fi)àport disable 1/4
4. Verify status from AHUBs (SWU-2 (bridge-fi)àshow port )à1/1 port should be down)
(SWU-0 (bridge-fi)àshow port )à1/4 port should be down)
6. Change MMDU-0 internal interface to el1 (ZQRW:MMDU,0::EL0;)
7. Verify that ping is still working
10. Restore default settings. Set one link UP between AHUBs
SWU-0 (bridge-fi)àport enable 1/4
and check status from AHUB Check port statuses
(SWU 0 àenable fi
SWU-0(enable-fi)# àshow port) )à1/4 port should be up)
Verify status from AHUBs (SWU-2 (bridge-fi)àshow port )à1/1 port should be up)
5. Expected results
1. All ports up
2. Ping is working
3. Interface 1/4 - shutdown in SWU-0 and interface 1/1 shutdown in SWU-2
5. Ping is working
6. MMDU-0 using el1 (ZQRI:MMDU,0::;)
7. Ping is working
8. MMDU-2 using el1 (ZQRI:MMDU,2::;)
9. Ping is working
10. Interfaces up and el0 used
27
1.1.22 2 shelfs; link between SWU1-SWU3 broken
1. Description
This test case verifies that internal connectivity is working while link between SWU-1 and SWU-3 is broken.
- 2 shelf configuration
3. Preconditions

- Verify that MMDU-0 and MMDU-2 are using el0 for internal IP
1. Verify that connections between units and AHUB is working. Check port statuses (SWU-0 àenable fi
3. Shutdown link between SWU-1 and SWU-3.
SWU-1(enable-fi)#
SWU-1 (bridge-fi)àport disable 1/4)
4. Verify status from AHUBs (SWU-3 (bridge-fi)àshow port )à1/1 port should be down)
(SWU-1 (bridge-fi)àshow port )à1/4 port should be down)
10. Restore default settings. Set one link UP between AHUBs
SWU 1 àenable fi
SWU-1(enable-fi)# àshow port
5. Expected results
1. All ports up
2. Ping is working
3. Interface 1/4 - shutdown in SWU-1 and interface 1/1 shutdown in SWU-3
5. Ping is working
6. MMDU-0 using el1 (ZQRi:MMDU,0::;)
7. Ping is working
8. MMDU-2 using el1 (ZQRi:MMDU,2::;)
9. Ping is working
10. Interfaces up and el0 used
28
1.1.23 MME restart – IP connectivity
1. Description
This test case verifies that site connectivity to backbone is working after MME is restarted. The subscriber data
transfer should work after restart.
- S6a Multihoming used
3. Preconditions

- Attach subscriber to MME
1. Verify that connections between AHUB and MME is working (enable fi - show port)
2. Copy all databases to disk (ZDBC –command). Restart MME and wait that all units are up
4. Reattach MS and transfer some data
5. Verify that data transfer is working.
6. Check alarms
7. Check unit logs
5. Expected results
1. All units have EL0 and EL1 interfaces up

2. MME restarted and units up
4. User registered to MME
5. Data transfer is working.
6. No unexpected alarms in MME
7. No unexpected logs in MME
29
1.1.24 AHUB restart – IP connectivity
1. Description
This test case verifies that site connectivity to backbone is working while AHUB is restarted. The subscriber data
transfer should work during restart.
3. Preconditions

- Attach subscriber to MME and start data transfer
2. Restart AHUB that has primary S6a connection ( check primary link ZQRI:IPDU,X and ZOHI EL0 is SWU-0
and EL1 is SWU-1) then "reload" command from AHUBs linux CLI and wait that AHUB is up
5. Check alarms
6. Check unit logs
5. Expected results

2. AHUB restarted and secondary SCTP connection is up (ZOHI; and ZQRS:IPDU,X)
30
1.1.25 LAG member down (AHUB- AHUB)
1. Description
This test case verifies that site connectivity to backbone is working while one member of LAG is down from link
aggregation group between AHUBs. The subscriber data transfer should work during test.
3. Preconditions

1. Verify that connections between units and MME is working and LAG is up (enable fi - show port)
2. Shutdown interface 1/4 from SWU-2
(SWU-2(enable-fi)-->conf terminal
SWU-2 (bridge-fi)àport disable 1/4)
(SWU 2 àenable fi
Verify status from AHUBs (SWU-2 (bridge-fi)àshow port )à1/4 port should be down)
3. Verify that LAG is still up
(SWU 2 àenable fi
SWU-2(enable-fi)# àshow lacp aggregator)
5. Check alarms
6. Check unit logs
7. Change interface status back to up
SWU 2 àenable fi
Verify status from AHUBs
SWU-2 (bridge-fi)àshow port )à1/4 port should be up and
SWU 2 àenable fi
SWU-2(enable-fi)# show lacp aggregator show that port 1/4 is back to aggregator group member
5. Expected results

2. interface 1/4 down
3. LAG is still up and both IUU and GN paths working
7. interface 1/4 up
31
1.1.26 LAG member down (AHUB- RTR)
1. Description
This test case verifies that site connectivity to backbone is working while one member of LAG is down from link
aggregation group between AHUB and RTR. The subscriber data transfer should work during test.
3. Preconditions

1.Verify that connections between AHUB and MME is working and LAG is up
SWU-2(enable-fi) àconf terminal
SWU-2(enable-fi)# à show lacp)
SWU-2(enable-fi)# à show lacp aggregator)
2. Shutdown interface 3/1 from SWU-2 (port disable 3/1)
SWU-2(enable-fi)# à show lacp
SWU-2(enable-fi)# à show lacp aggregator
show that port 3/1 is not member of aggregator group )
3. Verify that LAG is still up and both SCTP paths are working (enable fi àshow port and ZQRS:IPDU,X)
5. Check alarms
6. Check unit logs
7. Change interface status back to up
Verify status from AHUBs
SWU-2 (bridge-fi)àshow port
à 3/1 port should be up.
SWU-2(config-fi)àenable fi
SWU-2(enable-fi)# show lacp aggregator
show that port 3/1 is back to aggregator group member .
5. Expected results

2. interface 3/1 down (show port and show lacp aggregator)
3. LAG is still up and both SCTP paths working
7. interface 3/1 up (show port and show lacp aggregator)
32
1.1.27 Primary SCTP path broken
1. Description
This test case verifies that site connectivity to backbone is working while primary S6a SCTP path is broken. The
subscriber data transfer should work during test.
3. Preconditions

1. Verify that connections between units and AHUB is working (enable fi -> show port)
2. Shutdown IPDUs interface from AHUB that has primary S6a connection ( check ZQRS:IPDU,X and
ZWTI:P:IPDU,X to see what is interface number) example IPDU-0
Verify port status from AHUB
SWU 0 àenable fi
3. Verify that secondary SCTP path is working ZQRS:IPDU,X;, ZOHI; and ZQRI;
5. Check alarms
6. Check unit logs
7. Change interface status back to up. Example IPDU-0
Verify port status from AHUB
SWU 0 àenable fi
5. Expected results

2. IPDUs primary interface 0/X down (show port)
3. Secondary SCTP path working
7. interface up
33
1.1.28 CPPU Blade Removal
1. Description
The purpose of test case is to verify that MME can handle traffic and can recover from CPPU Unit Blade removal.
2. Required test environment and settings
- MME
- traffic if possible
1. States of the units are checked (ZUSI)

2. Status of the connections are checked with commands: ZOHI;, ZB6I; and ZQRS:IPDU,x;
3. States of the programs are checked from linux unit (ZDDS:CPPU,x;) with command: lnx-launcher -L
4. Start traffic if possible. This test case can be executed with or without traffic.
5. Remove the CPPU unit blade from the shelf and install it back using the following procedure.
- Change unit state to SE-NH
ZUSC:CPPU,<unit index>:TE;
ZUSC:CPPU,<unit index>:SE;
- Unscrew the two retaining screws at the top and bottom of the blade's front panel
- Gently open the lower ejector latch (hot swap handle) so that the blue hot swap LED starts blinking. Do
not open the latch all the way yet. Opening the latch notifies the hardware management system that you
are going to remove the blade and tells it to finish all processes. The hot swap LED starts blinking
- Wait until the hot swap LED turns into steady blue. This may take a few seconds
- Open both ejector latches
- Unseat the blade
- Insert the blade back
- Change unit state back to it’s original state
ZUSC:CPPU,<unit index>:TE;
ZUSC:CPPU,<unit index>:WO;
7. Status of the connections are checked with commands ZOHI; and ZB6I;
8. States of the programs are checked from linux unit with command: lnx-launcher -L
9. Alarm history is checked (ZAHP)
10. Active alarms checked (ZAHO)
4. Expected results
1. All units are OK, no FLTY –flags

2. Connections, network status OK
3. Program states OK
4. This test case can be executed with or without traffic.
5. Unit state changes function as expected and blade removal/insertion is successful
6. All units are in the original (1) states
7. Connections same as (2)
9. For Example following disturbances, alarms: 0691, 2692, 0157, 1334, 1001, (1012) seen during test
10. The MME is working stabile without unexpected alarms
34
1.1.29 IPDU Blade Removal
1. Description
The purpose of test case is to verify that MME can handle traffic and can recover from IPDU Unit Blade removal.
- MME
1. States of the units are checked (USI)

2. Status of the connections are checked with commands ZOHI;, ZB6I; and ZQRS:IPDU,x;
3. States of the programs are checked from linux unit with command lnx-launcher -L
5. Remove the spare IPDU unit blade from the shelf and install it back using the following procedure.
ZUSC:IPDU,<unit index>:TE;
ZUSC:IPDU,<unit index>:SE;
- Unseat the blade
ZUSC:IPDU,<unit index>:TE;
ZUSC:IPDU,<unit index>:SP;
6. States of the units are checked (USI)
7. Status of the connections are checked with commands OHI; and B6I;
8. States of the programs are checked from linux unit with command lnx-launcher -L
9. Alarm history is checked (AHP)
10. Repeat the test for the working IPDU unit blade also.
4. Expected results

35
1.1.30 MMDU Blade Removal
1. Description
The purpose of test case is to verify that MME can handle traffic and can recover from MMDU Unit Blade
removal.
- MME

5. Remove the MMDU unit blade from the shelf and install it back using the following procedure.
ZUSC:MMDU,<unit index>:TE;
ZUSC:MMDU,<unit index>:SE;
- Unseat the blade
ZUSC:MMDU,<unit index>:TE;
ZUSC:MMDU,<unit index>:WO;
7. Status of the connections are checked with commands: ZOHI; and ZB6I;
10. Check active alarms (ZAHO;)
4. Expected results

36
1.1.31 OMU Blade Removal
1. Description
The purpose of test case is to verify that MME can handle traffic and can recover from OMU Unit Blade removal.
- MME

5.
a) Copy the data files from OMU to the disks.
ZDFC:OMU,0;
b) Copy the databases from memory to the disks.
With command DBL, you can check which databases are used by the unit.
ZDBC:EQUIPM,0:;
ZDBC:ILDATA,0:;
c) Prevent file updates to the disk.
ZDUP:OMU:;
d) Prevent database file updates to the disk.
ZDBP:EQUIPM,0:DISK;
ZDBP:ILDATA,0:DISK;
e) Change the state of the HDD into BL-US.
ZISC:,OMU:WDU,0:WO-ID;
ZISC:,OMU:WDU,0:BL-US;
6. Remove the spare OMU unit blade from the shelf and install it back using the following procedure.
ZUSC:OMU,<unit index>:TE;
ZUSC:OMU,<unit index>:SE;
- Unseat the blade
ZUSC:OMU,<unit index>:TE;
ZUSC:OMU,<unit index>:SP;
7.
a) Change the state of the HDD back into WO-BU.
ZISC:,OMU:WDU,0:WO-ID;
ZISC:,OMU:WDU,0:WO-BU;
b) Resume database file updates to disk
ZDBR:EQUIPM,0:DISK;
ZDBR:ILDATA,0:DISK;
c) Resume file updates to disk
ZDUR:OMU:;
4. Expected results
37
1.1.32 MCHU blade removal
1. Description
The purpose of test case is to verify that MME can handle traffic and can recover from MCHU Unit Blade
removal.
- MME
38

5. Remove the spare MCHU unit blade from the shelf and install it back using the following procedure.
ZUSC:MCHU,<unit index>:TE;
ZUSC:MCHU,<unit index>:SE;
- Unseat the blade
ZUSC:MCHU,<unit index>:TE;
ZUSC:MCHU,<unit index>:SP;
4. Expected results

5. . Unit state changes function as expected and blade removal/insertion is successful
39
1.1.33 Power Supply Redundancy
1. Description
The purpose of this test case is to verify that the power supply redundancy is working correctly
- MME
- Turn off the the both electricity switches from the other side Power Distribution Unit
- Check that alarm 3434 POWER SUPPLY FAILURE is set for the all related units
- Turn on both of the switches again and check that the alarms 3434 are cancelled from all units
4. Expected results
- When the electricity switches are turned off there will be alarm 3434 set for all the related units.
- When switches are turned back on, alarm 3434 is cancelled for the related units.
- MME operation is not affected
40
1.2 Interface testing
1.2.1 S1 setup, no subscribers in MME
1. Description
The purpose of this test case is to ensure that MME works correctly in S1 setup when there are no subscribers in
MME.
- MME
- eNodeB
- HSS
- SAE-GW
3. Preconditions
- Check that there are no subscribers in MME (MML-command ZMMN;)
SUBSCRIBERS IN MME
MMDU-0 & MMDU-1 0
MMDU-2 & MMDU-3 0
--------------------------
TOTAL 0
- Reset eNodeB or give restart to IPDU (MML-command: ZUSU:IPDU,<wo-ex>;)
5. Expected results
- eNodeB sends S1 setup message to MME

- MME responses with S1 setup response
eNodeB MME
--------------------------------------------> S1 setup request

<-------------------------------------------- S1 setup response
41
1.2.2 S1 setup
1. Description
The purpose of this test case is to ensure that MME works correctly in S1 setup when there is subscriber in
eNodeB.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach by powering the UE on.

- Reset eNodeB:
- Make detach by powering the UE off.
5. Expected results
- S1 setup procedure is successful
eNodeB MME SGW
*--------------------------------------------------------------------------------------------*
| Normal attach procedure |
*--------------------------------------------------------------------------------------------*
--------------------------------------------> S1 setup request

<-------------------------------------------- S1 setup response
-----------------------------------------------> Release Access Bearer Request

<------------------------------------------------ Release Access Bearer Response
*--------------------------------------------------------------------------------------------*
| Normal detach procedure |
*--------------------------------------------------------------------------------------------*
42
1.2.3 S1 Flex - MME configuration update
1. Description
The purpose of this test case is to ensure that MME sends MME configuration update to eNodeB when MME
relative capacity is modified.
- MME
- eNodeB
3. Preconditions
- Reset eNodeB or give restart to working IPDU to trigger S1 setup procedure

- Modify MME relative capacity using ZWVF:MMRC MML-command which triggers MME configuration update-
message
5. Expected results
- Verify that S1 setup response contains MME relative capacity which is congifured in MME
- Verify that MME relative capacity changes when it is modified
eNodeB MME
--------------------------------------------> S1 setup request

<-------------------------------------------- S1 setup response
<-------------------------------------------- MME Configuration Update

--------------------------------------------> MME Configuration Update Ack
43
1.2.4 Echo Request on S11 interface initiated by SGW
1. Description
This test case verifies that MME responds with Echo Response, when SGW sends Echo Request via S11
interface.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Keep bearer active until SGW sends Echo Request
- Make detach
5. Expected results
- Echo procedure is successful
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
<------------------------------------------------ Echo request

------------------------------------------------> Echo Response
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
44
1.2.5 S11 Load Balancing
1. Description
This test case verifies that S11 Load Balancing functionality is working correctly in MME when SGW
allocates different IP address which was sent in Create Session Request
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Make detach
5. Expected results
- Check that attach is successful when SGW allocates different IP address than used in Create Session Request
message and that MME handles correctly the S11 load balancing.
45
1.2.6 SCTP multihoming for S1
1. Description
This test case verifies that S1 SCTP multihoming is working correctly when primary path is disconnected.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- eNodeB must support two IPs for S1 full path redundancy

- In S1 SCTP multihoming configuration EL4 and EL5 have their own addresses
- SCTP multihoming is OFF by default. Enable SCTP multihoming on the S1 interface:
ZBIM:S1:S1MHT=ON;
- NOTE: Depending on the configuration disconnecting cables could interfere other interfaces (for example S6a in
IPDU without multihoming).
- Make attach
- Disconnect the cable from primary interface of IPDU. Check that admin state of interface goes down: (MML-
command ZQRI;)
- Make detach
- Connect the primary interface cable back to MME
5. Expected results
- Attach is successful through primary path

- Secondary path is activated when primary path is disconnected
- Detach is successful through secondary path
46
1.1.1 OSS – Alarm forwarding to OSS
1. Description
- The purpose of the test case is to verify, that NS3.0 triple access node forwards alarms correctly to OSS
system.
- Basic network configuration. OSS integrated.
3. Preconditions
- Integrate OSS
- Empty alarms and logs from NE.
- Generate some alarms to MME/SGSN of triple access node. This can be done for example restarting unit or
changing unit state.
- Verify that alarm is seen in OSS system
- Check alarms, logs and system logs from MME/SGSN.
5. Expected results
- Alarm generation is succesfull (ZAHO)

- Alarms are forwarded correctly to OSS
47
1.3 Mobility and session management
1.3.1 Attach with IMSI – no IMEISV in SMC
1. Description
This test case verifies that attach (with IMSI) and detach procedures are working correctly.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- IMEISV not in SMC. If the IMREQ parameter is set to OFF (the default value), IMEISV is not requested from the
UE. (ZBSM:IMREQ=OFF;)
- UE does not have GUTI in memory
- Make attach
- Check from MME that the status of subscriber is ‘connected-registered’: (MML-command
ZMMO:IMSI=xxxxxxxx;)
- Make detach
- Check from MME that the status of subscriber is ‘idle-deregistered’: (MML-command ZMMO:IMSI=xxxxxxxx;)
5. Expected results
- Verify that IMEISV is not delivered in SMC
eNodeB MME HSS SGW
-----------------------------> Attach Request (Type of Identity=IMSI)
-------------------------> Authentication Information Request

<------------------------- Authentication Information Answer
<---------------------------- Authentication Request

-----------------------------> Authentication Response
<---------------------------- Security mode Command

-----------------------------> Security Mode Complete (no IMEISV)
-------------------------> Update Location Request

<------------------------- Update Location Answer
------------------------------------------------> Create Session Request

<------------------------------------------------ Create Session Response
<----------------------------- Initial Context Setup Request / Attach Accept

-----------------------------> Initial Context Setup Response
-----------------------------> Attach Complete
------------------------------------------------> Modify Bearer Request

<------------------------------------------------ Modify Bearer Response
-----------------------------> Detach Request

48
<---------------------------- Detach Accept

49
1.3.2 Attach with IMSI – IMEISV in SMC
1. Description
This test case verifies that attach (with IMSI) and detach procedures are working correctly. IMEISV in SMC..
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Delete subscriber from MME if it is in MME database (MML-command ZMMO:IMSI=xxxxxxxx;)

- IMEISV in SMC. (ZBSM:IMREQ=ON;)
- Make attach with IMSI

- Make detach
5. Expected results
- Type of identity is IMSI in attach
- IMEISV in SMC
eNodeB MME HSS SGW
-----------------------------> Attach Request (with IMSI)


<---------------------------- Security Mode Command (IMEISV)

-----------------------------> Security Mode Complete (IMEISV)



-----------------------------> Attach Complete

-----------------------------> Detach Request

<---------------------------- Detach Accept

50
51
1.3.3 Attach with GUTI
1. Description
The purpose of this test case is to ensure that attach with GUTI works correctly. IMEISV in SMC.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions

- IMEISV in SMC. (ZBSM:IMREQ=ON;)

- Make detach
- Make attach with GUTI
- Make detach
5. Expected results
- Type of identity is IMSI in attach
- Type of identity is GUTI in attach
eNodeB MME HSS SGW


<---------------------------- Security mode Command (IMEISV)

-----------------------------> Security Mode Complete (IMEISV)



-----------------------------> Attach Complete

-----------------------------> Detach Request

52
<---------------------------- Detach Accept

-----------------------------> Attach Request (Type of Identity=GUTI)


-----------------------------> Attach Complete
<---------------------------------------------- Modify Bearer Response
-----------------------------> Detach Request

<---------------------------- Detach Accept

53
1.3.4 IMEI sending to HSS
1. Description
Purpose of this scenario is to verify that MME is sending the terminal information (IMEISV) in the ULR
procedure to HSS in case a subscriber makes an Attach with a GUTI, when subscriber is not in DB and when
IMEI sending to HSS feature is active.
The IMREQ parameter determines whether the IMEISV is requested from the UE. If the
parameter is set to ON, IMEISV is requested as one of the parameters for example in
the security mode control (SMC) procedure. The IMREQ parameter has to be ON, so that MME can send IMEI to
HSS. If the IMREQ parameter is set to OFF (the default value), IMEISV is not requested from the UE.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
1.Check that S6a diameter connection has been created to HSS and its state is Connected
ZOHI:;
2.Check that IMEI sending to HSS PRFILE parameter is ON
ZWOI:2,2224;
If not then set it ON
ZWOC:2,2224,1;
3.Check that IMEI REQUEST FROM UE is ON
ZBSI;
If not then set it ON
ZBSM:IMREQ=ON;
4.HSS is capable to receive IMEI in ULR message
5.Check that subscriber is not in MME’s DB
1.Make Attach for subscriber

2.Check that subscriber is in DB
ZMMO:IMSI=<imsi>;
3.Check from Network protocol analyzer monitoring that MME sends IMEI and SV in ULR message
4.Check from HSS that IMEI + SV can be seen there (NSN DX HLR -command ZMIO:IMSI=<imsi>;)
5.Make Detach
5. Expected results
2. Subscriber is in DB
3. IMEI and SV can be seen in ULR
4. IMEI + SV can be seen in HSS
54
1.3.5 IMSI attach with SMP (correct ciphering)
1. Description
The purpose of this test case is to ensure that ciphered attach (with IMSI) and ciphered detach procedures work
correctly. Security Mode Procedure (SMP) has correct ciphering.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Select the used algorithm. These parameters are managed using the ZBSM command. To interrogate existing
authentication and security parameter settings, use the ZBSI; command.
- UE supports the selected security algorithm.
- Disable “Allow all NAS Security algorithms” feature on MME. Set the ALLOW_ALL_SEC_ALGORITHM Prfile
parameter 2/2225 to ”false”. MME MML ZWOC:2,2225,0;. To interrogate the existing feature status use
ZWOI:2,2225; command.
- Make attach
- Make detach
5. Expected results
- Authentication is successful
- Security Mode procedure is successful. Type of integrity protection is the one selected.
eNodeB MME HSS SGW



<---------------------------- Security Mode Command

-----------------------------> Security Mode Complete



-----------------------------> Attach Complete

-----------------------------> Detach Request
-------------------------------------------------> Delete Session Request

<------------------------------------------------- Delete Session Response
<---------------------------- Detach Accept

55
56
1.3.6 Dynamically selected NAS security algorithm
1. Description
Purpose of this test case is to verify the functionality of MME when preference list of NAS security algorithms is
enabled and UE does not support the configured algorithm. In case the UE does not support the configured
algorithm, then MME dynamically selects the NAS security algorithms according to the following priority order -
AES, SNOW3G and ZUC. The MME will include the chosen algorithms in the NAS security mode command
procedure.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- UE does not support the security algorithm configured in authentication and security parameter settings (ZBSI;)
- Enable “Allow all NAS Security algorithms” feature on MME. Set the ALLOW_ALL_SEC_ALGORITHM Prfile
parameter 2/2225 to ”true”. MME MML ZWOC:2,2225,1;. To interrogate the existing feature status use
ZWOI:2,2225; command.
- Make attach
- Make detach
5. Expected results
- Attach is successful. If UE supports several security algorithms then the one highest in the priority list is used.
- Authentication is successful
- Security Mode procedure is successful. Type of integrity protection is the one selected.
57
1.3.7 Double attach
1. Description
Purpose of this test case is to ensure that second attach works correctly and old session is deleted and new
session is created.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Make second attach before first session is detached (remove battery from UE and re-insert it. UE makes new
attach)
- Make detach
5. Expected results
- First attach is successful

- Second attach is successful
- Old session is deleted and new one created in second attach
eNodeB MME HSS SGW
-----------------------------> Attach Request






-----------------------------> Attach Complete

-----------------------------> Attach Request
-------------------------------------------------> Delete Session Request

<------------------------------------------------- Delete Session Response

58
-----------------------------> Attach Complete

-----------------------------> Detach Request
------------------------------------------------> Delete Session Request

<---------------------------- Detach Accept

59
1.3.8 Attach Reject - IMSI Unknown (HSS)
1. Description
This test case verifies that attach is rejected by cause IMSI unknown if HSS does not contain subscriber data.
- MME
- eNodeB
- HSS
- UE
3. Preconditions
- Remove subscriber data from the HSS or use IMSI which isn’t configured in HSS
5. Expected results
- Attach is rejected and cause is #14 “EPS services not allowed in this PLMN”.
eNodeB MME HSS
-----------------------------> Attach Request
---------------------------> Authentication Information Request

<--------------------------- Authentication Information Answer



<----------------------------- Attach Reject

60
1.3.9 Attach Reject - IMSI Unknown (AuC)
1. Description
This test case verifies that attach is rejected by cause IMSI unknown if AuC does not contain authentication data.
- MME
- eNodeB
- AuC / HSS
- UE
3. Preconditions
- Remove authentication data from the AUC/ HSS or use IMSI which isn’t configured in AuC/HSS
5. Expected results
- Attach is rejected and cause is “EPS services and non-EPS services not allowed”.
eNodeB MME HSS
-----------------------------> Attach Request
---------------------------> Authentication Information Request

<--------------------------- Authentication Information Answer
<----------------------------- Attach Reject

61
1.3.10 Attach Reject - IMSI analysis is missing
1. Description
This test case verifies that attach is rejected when IMSI analysis is missing.
- MME
- eNodeB
- HSS
- UE
3. Preconditions
- MME contains correct home PLMN and HSS selection for the subscriber and HSS connection is up (MML-
command ZOHI:;)
- IMSI analysis is missing for the subscriber (MML-command ZCFI)
5. Expected results
- Attach is rejected and cause is #11 “PLMN not allowed”.
eNodeB MME HSS
-----------------------------> Attach Request

<----------------------------- Attach Reject

62
1.3.11 Attach with IMSI – two home PLMNs configured in MME
1. Description
This test case verifies that attach, roaming and IMSI analysing is working when two (2) home PLMNs are created
in MME and both HSS connections are up.
- MME
- eNodeB
- 2 * HSS
- SAE-GW
- 2 * UE (with different SIM cards. IMSIs from both configured PLMNs)
3. Preconditions
- Multiple PLMN enabled. (ZWOI:2,2222;)

- MME contains two (2) home PLMNs and both HSS connections are up (MML-commands ZMXP; and ZOHI:;)
- MME contains different IMSI analysis for both home PLMNs pointing HSSs (MML-command ZCFI)

- Check that HSS identity is corresponding to subscriber IMSIs HSS. (ZMMO)
- Make detach
5. Expected results
- Verify that MME uses correct IMSI analysis for choosing correct home PLMN which points to right HSS
eNodeB MME HSS SGW






-----------------------------> Attach Complete

-----------------------------> Detach Request

<---------------------------- Detach Accept

63
64
1.3.12 Attach with unknown GUTI (GUTI reallocation)
1. Description
Purpose of the test case is ensure that identity procedure works correctly when UE sends attach request with
unknown GUTI. MME is requesting IMSI in identity procedure to be able to send the authentication info request to
right HSS.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
-Delete the subscriber from MME (MML-command ZMMD:IMSI:xxxxx;)
- Make attach with GUTI, which is not known in MME

- Make detach
5. Expected results
- Verify that MME reallocates new GUTI in Attach Accept-message
eNodeB MME HSS SGW
-----------------------------> Attach Request (with GUTI)
<---------------------------- Identity Request (IMSI)

-----------------------------> Identity Response (IMSI)


<---------------------------- Security Mode Command




-----------------------------> Attach Complete

-----------------------------> Detach Request

<---------------------------- Detach Accept
65
66
1.3.13 Attach Reject - SGW responses with error cause to create session request
1. Description
Purpose of this test case is to ensure that Attach Reject is sent correctly when SGW responses with error cause
to create session request.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- NSN SAE-GW: disable NG functionality (set ng general ng-functionality disable).
- Make attach
5. Expected results
- Attach is rejected
eNodeB MME HSS SGW
-----------------------------> Attach Request





<------------------------------------------------ Create Session Response (error cause=insufficient
resources)
<----------------------------- Attach Reject

67
1.3.14 UE initiated service request
1. Description
The purpose of this test case is to ensure that the service request procedure works correctly.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- eNodeB sends UE Context Release Request because user inactivity timer
- Check from MME that the status of subscriber is ‘idle-registered’: (MML-command ZMMO:IMSI=xxxxxxxx;)
- Transfer uplink data. This will trigger UE Initiated Service Request
- Make detach
- Check from MME that the status of subscriber is ‘idle-deregistered’: (MML-command ZMMO:IMSI=xxxxxxxx;)
5. Expected results
- Service procedure is successful
eNodeB MME HSS SGW
*-----------------------------------------------------------------------------------*
*-----------------------------------------------------------------------------------*
-----------------------------> UE Context Release Request
-------------------------------------------------> Release Access Bearer Request


-----------------------------> Service Request
<----------------------------- Initial Context Setup Request

--------------------------------------------------> Modify Bearer Request

<------------------------------------------------- Modify Bearer Respons
*-----------------------------------------------------------------------------------*
*-----------------------------------------------------------------------------------*
1.3.15 NW initiated service request (Paging)
1. Description
68
Purpose of this test case is to ensure that NW initiated service request works correctly
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- eNodeB makes UE Context Release because user inactivy timer.
- Check from MME that the status of subscriber is ‘idle’: (MML-command ZMMO:IMSI=xxxxxxxx;)
- Transfer downlink data. SGW sends DL data notification because of downlink data.
- Because of downlink data, paging is send to UE, which will responds with service request.
- Make detach
5. Expected results
- EnodeB requests UE Context Release because of user inactivity timer
- Downlink data will trigger paging and service procedure
- Verify that paging is sent only to those eNodeBs which are under same tracking area
eNodeB MME HSS SGW
*-----------------------------------------------------------------------------------*
*-----------------------------------------------------------------------------------*
-------------------------------------------------> Release Access Bearers Request

<------------------------------------------------ Release Access Bearers Response

<------------------------------------------------- DL Data notification

-------------------------------------------------> DL Data notification Ack
<---------------------------- Paging
-----------------------------> Service Request


*-----------------------------------------------------------------------------------*
*-----------------------------------------------------------------------------------*
69
1.3.16 UE initiated detach - UE in ECM idle state
1. Description
This test case verifies that UE initiated detach is working correctly when UE is in ECM idle state.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- eNodeB sends UE Context Release Request because of inactivity timer
- Make detach
5. Expected results
- UE Command Release is successful
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
-------------------------------------------------> Release Access Bearer Request


-----------------------------> Detach Request

<------------------------------------------------ Delete Session Response
<---------------------------- Detach Accept

70
1.3.17 Network initiated (O&M) detach - UE in ECM connected state
1. Description
This test case ensures that MME-initiated O&M detach works correctly when the subscriber is attached.
- MME
- HSS
- SAE-GW
- eNodeB
- UE
3. Preconditions
- Make attach
- Make O&M detach from MME (MML-command ZMMD:IMSI=xxxxxxxx;)
5. Expected results
- MME initiated detach is successful
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
<----------------------------- Detach Request

-----------------------------> Detach Accept

-------------------------> Purge UE
<------------------------- Purge UE Acknowledge
71
1.3.18 Network initiated (O&M) detach to UE - UE in ECM idle state
1. Description
This test case ensures that MME-initiated O&M detach works correctly when the subscriber is in ECM idle state.
- MME
- HSS
- SAE-GW
- eNodeB
- UE
3. Preconditions
- Make attach
- eNodeB sends UE Context Release Request because of inactivity timer.
- O&M detach is sent from MME (MML-command ZMMD:IMSI=xxxxxxxx;)
5. Expected results
- UE Context Release procedure is successful
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
------------------------------------------------> Release Access Bearer Request

<----------------------------------------------- Release Access Bearer Response

<----------------------------- Paging
-----------------------------> Service Request
<----------------------------- Detach Request

-----------------------------> Detach Accept

-------------------------> Purge UE
<------------------------- Purge UE Acknowledge
1.3.19 HSS initiated detach – UE in ECM connected state
1. Description
72
This test case ensures that HSS initiated (cancel location) detach works correctly when the subscriber is attached
and ECM connected state.
- MME
- HSS
- SAE-GW
- eNodeB
- UE
3. Preconditions
- Make attach
- Delete the whole subscription in HSS. Cancel Location is sent from HSS (cancel type ‘subscription withdrawal’).
This will trigger detach procedure.
5. Expected results
- HSS initiated detach is successful
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
<---------------------------- Cancel Location Request
<----------------------------- Detach Request

-----------------------------> Detach Accept
--------------------------> Cancel Location Answer

73
1.3.20 HSS initiated detach – UE in ECM idle state
1. Description
This test case ensures that HSS initiated (cancel location) detach works correctly when the subscriber is attached
and ECM idle state.
- MME
- HSS
- SAE-GW
- eNodeB
- UE
3. Preconditions
- Make attach
- Delete the whole subscription in HSS. Cancel Location is sent from HSS (cancel type ‘subscription withdrawal’)
5. Expected results
- HSS initiated detach is successful
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*

<----------------------------------------------- Release Access Bearer Response

<----------------------------- Paging
-----------------------------> Service Request
<----------------------------- Detach Request

-----------------------------> Detach Accept
--------------------------> Cancel Location Answer

74
1.3.21 S6A, Delete Subscriber Data
1. Description
Delete subscriber EPS data in HSS during UE is ECM connected state.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Delete subscriber EPS data in HSS (ZMNB -command in NSN DX HLR):
- >HSS initiated detach
5. Expected results
- Delete subscriber Data procedure works correctly. MME receive Cancel Location <subscription withdrawal >
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
<------------------------- Cancel Location request
<----------------------------- Detach Request

-----------------------------> Detach Accept

-------------------------> Cancel Location Act
75
1.3.22 Cancel Location – UE in EMM deregistered state
1. Description
This test case ensures that HSS initiated (cancel location) detach works correctly when UE is in EMM
deregistered state.
- MME
- HSS
- SAE-GW
- eNodeB
- UE
3. Preconditions
- Make attach
- O&M detach is sent from MME (MML-command ZMMD:IMSI=xxxxxxxx;)
- Check subscriber information (MML-command ZMMO) and delete the whole subscription in HSS while
subsriber is still in MME database. Cancel Location is sent from HSS (cancel type ‘subscription withdrawal’)
5. Expected results
- MME is answering to the Cancel Location when whole subscription is deleted in HSS
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
<----------------------------- Detach Request

-----------------------------> Detach Accept


---------------------------> Cancel Location Answer
76
1.3.23 UE initiated detach (UE power OFF)
1. Description
This test case ensures that UE-initiated Power OFF-detach works correctly.
- MME
- HSS
- SAE-GW
- eNodeB
- UE
3. Preconditions
- Make attach
- Switch UE OFF (Power OFF detach)
5. Expected results
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
-----------------------------> Detach Request


77
1.3.24 Delete Bearer Request from SGW – UE in ECM connected state
1. Description
Purpose of this test case is to ensure that detach is working when SGW sends delete bearer. UE in EMM
connected state.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
-
- Make attach
- SGW sends delete bearer request
(how to get NSN SGW to send delete bearer request:
set ng general ng-functionality disable OR set ng access-point ngap1 administrative-state disable)
5. Expected results
- Detach is successful when bearer is deleted from SGW
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
<------------------------------------------------ Delete Bearer Request
<---------------------------- Detach Request

----------------------------> Detach Accept
------------------------------------------------> Delete Bearer Response

78
1.3.25 Delete Bearer Request from SGW – UE in ECM idle state
1. Description
Purpose of this test case is to ensure that detach is working when SGW sends delete bearer. UE in ECM idle
state.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
-
- Make attach
- SGW sends delete bearer request
5. Expected results
- Detach is successful when bearer is deleted from SGW
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*


<------------------------------------------------ Delete Bearer Request
<---------------------------- Paging
-----------------------------> Service Request
<---------------------------- Detach Request

----------------------------> Detach Accept
------------------------------------------------> Delete Bearer Response

79
1.3.26 Periodic Tracking Area Update
1. Description
The purpose of this test case is to ensure that the Periodic Tracking Area Update procedure works correctly. UE
is in ECM idle state and activity flag is false.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Configure Periodic TA update timer (PTAU) using ZBJM MML-command
- Make attach
- eNodeB sends UE Context Release Request because of inactivity timer.
- Wait untill Periodic Tracking Area Update happens
- Make detach
5. Expected results
- Periodic TAU is successful and UE Context is released because of the false activity flag
- Verify that PTAU timer works as configured in preconditions part
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------------*
-----------------------------------------------> Release Access Bearer Request

<---------------------------------------------- Release Access Bearer Response

-----------------------------> Periodic Tracking Area Update Request

<---------------------------- Periodic Tracking Area Update Accept

*-----------------------------------------------------------------------------------*
*-----------------------------------------------------------------------------------*
80
1.3.27 TAU with S-GW relocation
1. Description
Purpose of this test case is to ensure that TAU with S-GW relocation works from MME point of view.
- MME
- eNodeB
- HSS
- 2 S-GW
- 1 P-GW
- UE
3. Preconditions
- S-GW relocation feature has been activated. Check with ZWOI:2,2029; Can be enabled with ZWOC:2,2029,FF;
- Two TACs of ENB point to two different SGWs
- UE attaches successfully
- UE moves from one TAC to another with different S-GW
5. Expected results
- MME make DNS query for the target S-GW address via eNB's new TAC
- Create session to target S-GW is successful
- Modify bearer request to target S-GW is successful
- Delete session to source S-GW is successful
eNodeB MME New S-GW Old S-GW P-GW
------------------> TAU Request
Authentication/security
*----------------------------------------------------------------------------------------------------*
| DNS query <------------------------------------------------------> DNS |
*----------------------------------------------------------------------------------------------------*
--------------------> Create Session Request
<----------------------------------------> Modify Bearer
<------------------- Create Session Response
-------------------------------------------> Delete Session Request

<------------------------------------------- Delete Session Response
*----------------------------------------------------------------------------------------*
| User plane setup procedure |
*----------------------------------------------------------------------------------------*
<------------------ TAU Accept

------------------> TAU Complete
81
1.2 Triple Access
1.2.1 Attach and detach in 4G, Attach in 3G.
1. Description
Purpose of this test case is to ensure that Intersystem Attach from MME to SGSN works correctly
- Triple access MME/SGSN

- eNodeB
- HSS
- SGW
- UE
- RNC
- NodeB
3. Preconditions
- Gn configured between MME and SGSN

- DNS configured. Refer to User Guide, DNS Interface Description and 3GPP TS29.303.
- Attach UE to MME
- Make detach to MME
- Make Intersystem attach to SGSN
- Check from SGSN that subscription data is correctly updated to SGSN: (MML-command
5. Expected results
- Attach and detach are successful to MME

- Identification procedure is successful
82
1.4 QoS
1.4.1 MME uses QoS parameters from HSS in default bearer creation
1. Description
This test case ensures that MME obtains QoS parameters from HSS correctly to be used in default bearer
creation, and data transfer works fine.
- MME
- HSS
- SAE-GW
- eNodeB
- UE
3. Preconditions
- Make attach
- Transfer data
- Make detach
5. Expected results
- Correct QoS values (values from HSS) are received in Update Location Answer from HSS
- Correct QoS values are used in Create Session Request
- Data transfer is successful
eNodeB MME HSS SGW
-----------------------------> Attach Request




<------------------------- Update Location Answer (with correct QoS parameters)

<----------------------------- Initial Context Setup Request / Attach Accept (with

correct QoS parameters)
-----------------------------> Attach Complete

----------------------------------------------------------------------------------- Data transfer
-----------------------------> Detach Request
----------------------------------------------> Delete Session Request

83
<----------------------------- Detach Accept

84
1.4.2 HSS initiated QoS change (UE-AMBR) – UE in ECM connected state
1. Description
Modify subscriber QoS profile in HSS when UE is ECM connected state. Check that new UE-AMBR values are
delivered to eNodeB.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Check QoS values with ZMMS:IMSI=xxxxx; MML
- Modify subscriber profile (UE-AMBR) in HSS
- Check that QoS values have been updated with ZMMS:IMSI=xxxxx; MML
- Make detach
5. Expected results
- MME receives modified profile and sends new UE-AMBR values to eNodeB
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
<------------------------- Insert Subscriber Data Request

-------------------------> Insert Subscriber Data Answer
<----------------------------- UE Context Modification Request

-----------------------------> UE Context Modification Response
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
85
1.4.3 HSS initiated QoS change (UE-AMBR) – UE in ECM idle state
1. Description
Modify subscriber QoS profile in HSS when UE is ECM idle state. Check that new UE-AMBR values are delivered
to eNodeB in service request procedure because of downlink data
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- UE Context Release from eNodeB because user inactivity timer
- Modify subscriber profile (UE-AMBR) in HSS
- Transfer downlink data. SGW sends DL data notification because of downlink data.
- UE sends Service Request
- Check from MME that the status of subscriber is ‘connected’ and ‘registered’: (MML-command
- Make detach
5. Expected results
- MME receives modified profile
- Downlink data will trigger paging and service procedure successfully
- MME sends new UE-AMBR values to eNodeB in service request procedure
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*



<------------------------------------------------- DL Data notification

-------------------------------------------------> DL Data notification Ack
<---------------------------- Paging
-----------------------------> Service Request

86
-------------------------------------------------> Modify Bearer Request
<------------------------------------------------- Modify Bearer Response
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
87
1.4.4 HSS initiated QoS change (APN-AMBR) – UE in ECM connected state
1. Description
Modify subscriber QoS profile in HSS when UE is ECM connected state. Check that new AP-AMBR values are
delivered to UE and SGW.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Modify subscriber profile (APN-AMBR) in HSS
- Make detach
5. Expected results
- MME receives modified profile and sends new APN-AMBR values to UE and SGW
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*

------------------------------------------------> Modify Bearer Command

<------------------------------------------------ Update Bearer Request
<----------------------------- Modify EPS Bearer Context Request

-----------------------------> Modify EPS Bearer Context Accept
------------------------------------------------> Update Bearer Response

*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
88
1.4.5 HSS initiated QoS change (APN-AMBR) – UE in ECM idle state
1. Description
Modify subscriber QoS profile in HSS when UE is ECM idle state. Check that new APN-AMBR values are
delivered to UE and SGW in service request procedure
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- UE Context Release from eNodeB because user inactivity timer
- Modify subscriber profile (APN-AMBR) in HSS
- Paging from MME and then UE sends Service Request
- Check from MME that the status of subscriber is ‘connected’ and ‘registered’: (MML-command
- Make detach
5. Expected results
- MME receives modified profile
- MME sends new APN-AMBR values to UE and SGW in service request procedure
eNodeB MME HSS SGW
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*



<----------------------------- Paging
-----------------------------> Service Request
<----------------------------- Initial Context Setup Req / Modify EPS Bearer Context

Request
-----------------------------> Modify EPS Bearer Context Response
-------------------------------------------------> Modify Bearer Request

<------------------------------------------------- Modify Bearer Response
89
*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
90
1.4.6 P-GW initiated QCI and ARP change in connected state
1. Description
This test procedure verifies PDN GW initiated successful bearer modification. QoS (QCI , ARP) changed.
- MME
- eNodeB
- HSS
- SaeGW
- UE
3. Preconditions
- Make attach
- QoS change from P-GW
- Make detach
5. Expected results
- UE gets updated values. Check that QoS values have been updated. Use ZMMS –command
(ZMMS:IMSI=xxxx;).
eNodeB MME SGW
*-------------------------------------------------------------*
*-------------------------------------------------------------*
<----------------------------- Update Bearer Request
<----------------------------- Bearer Modify Request/

Session Management Request
-----------------------------> Bearer Modify Response

-----------------------------> Session Management Response
-----------------------------> Update Bearer Response
*-------------------------------------------------------------*
*-------------------------------------------------------------*
91
1.4.7 P-GW initiated TFT or APN-AMBR in connected state
1. Description
This test procedure verifies PDN GW initiated successful bearer modification. Traffic flow template (TFT) or APN-
AMBR changed.
- MME
- eNodeB
- HSS
- SaeGW
- UE
3. Preconditions
- Make attach
- Current APN-AMBR value can be checked with ZMMS:IMSI=xxxxx; MML
- TFT or APN-AMBR change from P-GW
- If APN-AMBR value was changed new value is seen with ZMMS:IMSI=xxxxx; MML
- Make detach
5. Expected results
- UE gets updated values.
eNodeB MME SGW
*-------------------------------------------------------------*
*-------------------------------------------------------------*
<----------------------------- Update Bearer Request (PTI, EPS Bearer Identity, APN-AMBR, TFT)
<----------------------------- Downlink NAS Transport /Modify EPS Bearer Context Request
-----------------------------> Uplink NAS Transport /Modify EPS Bearer Context Accept
-----------------------------> Update Bearer Response
*-------------------------------------------------------------*
*-------------------------------------------------------------*
92
1.4.8 P-GW initiated QCI and APN-AMBR change in idle mode
1. Description
The purpose of this test case is to verify that PDN gateway initiated bearer modification with bearer QoS (APN-
AMBR) update is working correctly. In this case PCRF initiates modification.
- MME
- eNodeB
- HSS
- S-GW
- P-GW
- PCRF
- UE
- Network protocol analyzer tool available (e.g. Network analyzer) to monitor interfaces: S11, S1, Gx.
3. Preconditions
- Create EPS bearer.

- Wait until UE goes to IDLE state.
- Change QoS values (APN-AMBR) in PCRF for used subscriber.
5. Expected results
- New QoS values are taken into use.
eNodeB MME S-GW P-GW
<-------------------------- Update Bearer Request
<-------------------------- Update Bearer Request
<----------------------- Bearer Modify Request/ Session Management

Request
------------------------> Bearer Modify Response
------------------------> Session Management Response
----------------------------> Update Bearer Response
---------------------------> Update Bearer Response
93
1.5 DNS
1.5.1 SGW and PGW selection using DNS query
1. Description
Purpose of this test case is to ensure that DNS queries works correctly from MME point of view.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Make attach
- Make detach
5. Expected results
- PGW IP address is provided in DNS query (PGW query)
- MME sends PGW IP address in Create Session Request to the SGW
eNodeB MME HSS SGW DNS SERVER

-----------------------------> Attach Request




----------------------------------------------------------------> SGW Query

<---------------------------------------------------------------- SGW Query response
----------------------------------------------------------------> PGW Query

<---------------------------------------------------------------- PGW Query


-----------------------------> Attach Complete

*----------------------------------------------------------------------------------*
*----------------------------------------------------------------------------------*
94
1.5.2 PGW selection - HSS provides PGW IP address
1. Description
Purpose of this test case is to ensure that MME forwards PGW IP address in create session request-message to
the SGW without PGW query.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- DNS Server
3. Preconditions
- Configure PGW IP address to the HSS

- Make attach
- Make detach
5. Expected results
- HSS provides PGW IP address in Update Location Answer
- MME sends same PGW IP address in Create Session Request to the SGW
- No PGW query in DNS query
eNodeB MME HSS SGW DNS SERVER
-----------------------------> Attach Request




----------------------------------------------------------------> SGW Query

<---------------------------------------------------------------- SGW Query response


-----------------------------> Attach Complete

-----------------------------> Detach Request

95
<---------------------------- Detach Accept

96
1.6 APN from UE during attach
1.6.1 Attach when UE provides APN
1. Description
This test scenario verifies that MME is able to utilize APN received from the UE during Attach procedure.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Subscriber has 2 APN-configurations in HSS subscription data. APN1 (default) and APN2. (In DX HLR this can
be done by MML command: ZMNP:IMSI=xxxx...)
- DNS configuration for all used APNs
- Subscriber is purged from the MME
- On/Off activation parameter for ESM Information Request procedure is "ON". MME MML: WOC:2:2050:FF;.
- On/Off parameter for overriding invalid UE provided APN is "OFF". MME MML: WOC:2:2051:0;.
- ESM information flag is sent by UE
- “APN2” set to UE
- UE makes attach
- APN2 is used for the default PDN connection
5. Expected results
PDN connectivity req sent with Attach req includes the EMS information transfer flag
MME sends ESM information Req NAS message towards UE
MME receives ESM Information Answer NAS message including the APN "APN2"
MME sends ULR towards HSS and requests the subscription data
Two APN-configurations are received in ULA
MME selects the APN-configuration APN2 to be used for the default PDN connection based on the received APN
Bearer is successfully created and Attach is accepted
Data is successfully transferred via APN2
eNodeB MME HSS SGW
-----------------------------> Attach Request



<----------------------------- ESM Information Request

-----------------------------> ESM Information Response (APN="APN2")


97
-----------------------------> Attach Complete

98
1.6.2 Normal attach without ESM information Transfer flag
1. Description
This scenario is testing that existing functionality is not affected. Normal attach works when ESM information flag
is not sent by UE and feature is on in MME.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- On/Off parameter for overriding invalid UE provided APN is "ON". MME MML: WOC:2:2051:FF;.
- ESM information flag is not sent by UE
- UE makes attach
5. Expected results
UE sends PDN connectivity request without ESM information Transfer flag

Default PDN connection according to subscription data (APN1)
Default Bearer is successfully created and Attach is accepted
Normal attach works when ESM information flag is not sent by UE and feature is on in MME.
eNodeB MME HSS SGW
-----------------------------> Attach Request






-----------------------------> Attach Complete

99
1.6.3 ESM information transfer flag received but PRFILE is OFF
1. Description
This test scenario verifies that old functionality is not changed if this feature is not activated.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- On/Off activation parameter for ESM Information Request procedure is "OFF". MME MML: WOC:2:2050:0;.
- UE makes attach
5. Expected results
UE sends PDN connectivity request with ESM information Transfer flag

MME ignores the flag
Default PDN connection according to subscription data (APN1)
Default Bearer is successfully created and Attach is accepted
eNodeB MME HSS SGW
-----------------------------> Attach Request






-----------------------------> Attach Complete

100
1.6.4 UE provided invalid APN with APN overriding ON
1. Description
This test scenario verifies that UE provided invalid APN overriding functionality is working.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- UE makes attach
5. Expected results
PDN connectivity req sent with Attach req includes the EMS information transfer flag
MME sends ESM information Req NAS message towards UE
MME receives ESM Information Answer NAS message including the APN "APN3"
There are no APN-configuration for APN3
MME uses the default APN-configuration for the default PDN-connection
Attach is successful
Data is successfully sent and received via APN1
eNodeB MME HSS SGW
-----------------------------> Attach Request




-----------------------------> ESM Information Response (APN="APN3")



-----------------------------> Attach Complete

101
102
1.6.5 UE provides empty APN and APN overriding OFF
1. Description
This test scenario verifies that if overriding is not used, MME is able to handle the error scenario with missing
(empty) APN.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Subscriber has 2 APN-configurations in HSS subscription data. APN1 (default) and APN2.
- UE provided APN IE is empty
- UE tries attach
5. Expected results
PDN connectivity request includes ESM information Transfer flag

UE provides APN IE in ESM Information Answer NAS message
Provided APN IE is empty
Overriding UE provided invalid APN PRFILE parameter is OFF, so Attach is rejected
EMM cause #19, "ESM failure"
ESM cause #27: "missing or unknown APN"
eNodeB MME HSS SGW
-----------------------------> Attach Request




-----------------------------> ESM Information Response (APN empty)
<----------------------------- Attach Reject

103
1.6.6 UE provides invalid APN and APN overriding OFF
1. Description
This test scenario verifies that if overriding is not used, MME is able to handle the error scenario with invalid APN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- UE tries attach
5. Expected results
PDN connectivity request includes ESM information Transfer flag

UE provides APN IE in ESM Information Answer NAS message
APN doesn't match to any APN-configuration
Overriding UE provided invalid APN PRFILE parameter is OFF, so Attach is rejected
EMM cause #19, "ESM failure"
ESM cause #27: "missing or unknown APN"
eNodeB MME HSS SGW
-----------------------------> Attach Request




-----------------------------> ESM Information Response (APN empty)
<----------------------------- Attach Reject

104
1.7 HSS redundancy
1.7.1 2 HSS connections for same realm
1. Description
This test case verifies correct functionality when 2 HSS connections are configured for same realm (host1 and
host2) .
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Configure 2 HSS connections for same realm (host1 and host2), first configured is set as Primary connection
Example ZOHI
ORIGIN HOST NAME : MMEC04.MMEGI8002.MME.EPC.MNC022.MCC234.3GPPNETWORK.ORG

ORIGIN REALM NAME: EPC.MNC022.MCC234.3GPPNETWORK.ORG
DIAMETER CONNECTIONS OF HSS82FIRST.NODE.EPC.MNC022.MCC234.3GPPNETWORK.ORG:
DESTINATION NAME : HSS82FIRST.NODE.EPC.MNC022.MCC234.3GPPNETWORK.ORG
DESTINATION INDEX : 0
DESTINATION REALM : EPC.MNC022.MCC234.3GPPNETWORK.ORG
ORIGIN REALM : EPC.MNC022.MCC234.3GPPNETWORK.ORG
CONNECTION INDEX : 1
UNIT : IPDU-0
DIAMETER ROLE : CLIENT
APPLICATION ID : S6A/S13
OFFLINE PARAMETERS SET INDEX: 0
SIZE OF SENDING WINDOW: 1

MAXIMUM ACKNOWLEDGEMENT WAITING TIME: 5 SECONDS
RESENDING TIMES: 0
RE-ATTEMPT TIME: 30 SECONDS
DEFINED IP-ADDRESSES AND PORTS:
PATH ID. CONNECTION NAME PROTOCOL PATH ROLE CONNECTION STATUS

----------- ----------------- ---------- ----------- ------------------
1 PRIPATH SCTP PRI CONNECTED
PRIMARY LOCAL ADDRESS: 10.102.121.98 2001

PRIMARY REMOTE ADDRESS: 10.102.184.14 3868
DIAMETER CONNECTIONS OF HSS82A.NODE.EPC.MNC022.MCC234.3GPPNETWORK.ORG:
DESTINATION NAME : HSS82SECOND.NODE.EPC.MNC022.MCC234.3GPPNETWORK.ORG
DESTINATION INDEX : 1
DESTINATION REALM : EPC.MNC022.MCC234.3GPPNETWORK.ORG
ORIGIN REALM : EPC.MNC022.MCC234.3GPPNETWORK.ORG
105
CONNECTION INDEX : 1
UNIT : IPDU-0
DIAMETER ROLE : CLIENT
APPLICATION ID : S6A/S13
OFFLINE PARAMETERS SET INDEX: 0
SIZE OF SENDING WINDOW: 1

MAXIMUM ACKNOWLEDGEMENT WAITING TIME: 5 SECONDS
RESENDING TIMES: 0
RE-ATTEMPT TIME: 30 SECONDS
DEFINED IP-ADDRESSES AND PORTS:
PATH ID. CONNECTION NAME PROTOCOL PATH ROLE CONNECTION STATUS

----------- ----------------- ---------- ----------- ------------------
3 SEC SCTP PRI CONNECTED
PRIMARY LOCAL ADDRESS: 10.102.121.102 2001

PRIMARY REMOTE ADDRESS: 10.102.184.15 3868
- Make Attach
- Make Detach
5. Expected results
- First connection is used. Use network analyzer to see that diameter messages are send from IP of the first
connection.
- Attach and detach ok.
106
1.7.2 2 HSS connections for same realm, connection failure
1. Description
host2) and connection failure occurs.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Configure 2 HSS connections for same realm (host1 and host2), first configured is set as Primary connection.
Example ZOHI can be found from test case 2.14.1.
- Create connection failure for first connection. Unplug cable from AHUB / site router / etc
- Make Attach
- Restore original settings.
5. Expected results
- First connection is disconnected.

- Second connection is used. Use network analyzer to see that diameter messages are send from IP of the
second connection.
107
1.7.3 2 HSS connections for same realm, connection failure second link
1. Description
host2) and connection failure occurs to second link.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
- Configure 2 HSS connections for same realm (host1 and host2), first configured is set as Primary connection.
(ZOHI).
- Create connection failure for second connection. Unplug cable from AHUB / site router / etc
- Make Attach
- Make Detach
- Correct connection failure.
- Make Attach
- Restore original settings.
5. Expected results
- Second connection down, no unclear error messages or logs created by the test.
connection.
- Attach and detach ok
- Second connection recovers. Check with MML command ZOHI; , that connection is in CONNECTED mode.
connection.
- Attach ok
108
1.8 DNS based load balancing
1.8.1 MME chooses the correct SGW/PGW pair for Attach
1. Description
This test scenario verifies that MME chooses the correct SGW/PGW pair.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
3. Preconditions
DNS record Configuration scenario:

- List of SGW, EITHER should be, neither collocated nor topologically closer with any of the PGWs OR
should have same topological closeness with all PGWs
- Should have same NAPTR Order in the Resource Records
- Should have different priority for the SRV Records
- UE initiates an attach
5. Expected results
- MME chooses the SGW/PGW pair applying DNS load balancing and send the CSR to the chosen SGW and
the PGW
109
1.3 Circuit switched fallback; CSFB
1.3.1 MO CSFB to GERAN, UE in active mode
1. Description
This test scenario verifies that a MO call is correctly handled by the MME when the UE is in
active mode and the
CSFB is done to GERAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
- CSFB configured according to User Guide. Set the MME_CSFB_ENABLED Prfile parameter
2/2012 to “true”.
MME MML: ZWOC:2,2012,FF;
- UE is CSFB capable
- UE is combined attached to MSS and MME
- UE is in active mode
- UE initiates a MO call
- Call end
5. Expected results
- UE sends an Extended Service Request message, a Service type field indicates MO CS

Fallback
- MME initiates an UE CONTEXT MODIFICATION procedure towards the eNB with the CS
Fallback indicator
- MME initiates Release Access Bearers procedure towards S-GW
- MME initiates UE Context Release procedure towards eNB
- Cause value in UE CONTEXT RELEASE REQUEST message is "UE
Not Available For PS Service"
- MME initiates the SUSPEND procedure towards the S-GW
- SUSPEND NOTIFICATION message is sent to S-GW for non-GBR bearers
- MME receives a response message SUSPEND ACKNOWLEDGE from S-GW
- MME initiates DELETE BEARER procedure towards the S-GW
- DELETE BEARER COMMAND message is sent to S-GW for GBR bearers
- MME receives SUSPEND Request message from SGSN and replies with SUSPEND_ACK
message
- The call is successful
- UE performs TAU after the call is ended
- All the bearers are resumed correctly after TAU
- No alarms set by the MME
eNodeB MME HSS SGW MSC/VLR SGSN
---------- CSFB MO call in Active Mode No PS HO Support Start ------------------
-----------------------------> NAS Extended Service

Request
<---------------------------- UE-Context
Modification Request (With CS Fallback indicator)
-----------------------------> UE-Context Modification
Response
110
-----------------------------> UE-Context Release
Request(CAUSE : ps
SERVICE NOT AVAILABLE")
----------------------------------------> Release Access Bearer
Request
<----------------------------------------- Release Access Bearer

Response
<--------------------------- UE-Context Release command

--------------------------->
<------------------------------------------------------------ Suspend request/Response (

Bearer ) Non - GBR
111
------ S3 Suspend Procedure starts ( No Inter System RAU Procedure ) ----------------
<--------------------------------------------------------------------- S3_Suspend (SGSN Context Request)

----------------------------------------------------------------------> S3_suspend ACKSGSN Context Response
<--------------------------------------------------------------------- SGSN Context Ack
------ S3 Suspend Procedure ends ----------------------------------------------------------------------------------------
CALL
Inter System TAU
112
1.3.2 MO CSFB to GERAN, UE in idle mode
1. Description
This test scenario verifies that a MO call is correctly handled by the MME when the UE is in idle mode and the
CSFB is done to GERAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
- CSFB configured according to User Guide. Set the MME_CSFB_ENABLED Prfile parameter 2/2012 to “true”.
- UE is in idle mode
- Call end
5. Expected results
- UE sends an Extended Service Request message, a Service type field indicates MO CS Fallback
- MME initiates an INITIAL UE CONTEXT SETUP procedure towards the eNB with the CS Fallback indicator
- Cause value in UE CONTEXT RELEASE REQUEST message is "UE Not Available For PS Service"
- MME receives SUSPEND Request message from SGSN and replies with SUSPEND_ACK message
-----------------------------> NAS Extended Service Request

<---------------------------- Initial Context Setup Request (With CS
Fallback indicator)
-----------------------------> UE-Context Release Request(CAUSE : ps
--------------------------->
113
<------------------------------------------------------------> Suspend request/Response ( Non - GBR
Bearer )
------ S3 Suspend Procedure starts ( No Inter System RAU Procedure ) ----------

-----------------------------------------------------------------------> S3_suspend ACKSGSN Context Response
<--------------------------------------------------------------------- SGSN Context Ack
------ S3 Suspend Procedure ends ----------------------------------------------------------------------------------------
CALL
Inter System TAU
114
1.3.3 MT CSFB to GERAN, UE in active mode
1. Description
This test scenario verifies that a MT call is correctly handled by the MME when the UE is in active mode and
accepts the call. CSFB is done to GERAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
- MT call
- Call end
5. Expected results
- Paging Request message is received from VLR. Service indicator information element indicates "CS call
indicator".
- MME sets the CN Domain indicator to "CS" in the Paging message towards the eNodeB
- UE sends an Extended Service Request message, a Service type field indicates MT CS Fallback
- CSFB response field indicates that CS fallback is accepted by the UE
- MME sends a Service Request message to MSC indicating that the UE was in Idle mode
- MME initiates the SUSPEND procedure towards the S-GW for non-GBR bearers
- SUSPEND NOTIFICATION message is sent to S-GW
- MME initiates DELETE BEARER procedure towards the S-GW for GBR bearers
- DELETE BEARER COMMAND message is sent to S-GW
------ CSFB MT call in Active Mode No PS HO Support Start -----------
< ---------------------------------------------- Paging Request (Service indicator=CS)

<---------------------- CS Service Notification
-----------------------------------------------> Service Request
---------------------> NAS Extended Service Request
<--------------------- UE-Context Modification Request (With CS
Fallback indicator)
115
---------------------> UE-Context Modification Response
-----------------------------> UE-Context Release Request
---------------------------> UE-Context Release complete
<-----------------------------------------------------------------------> Suspend request/Response ( Non - GBR
Bearer )
------ S3 Suspend Procedure starts ( No Inter System RAU Procedure ) ---------

-----------------------------------------------------------------------> S3_suspend ACKSGSN Context Response
<--------------------------------------------------------------------- SGSN Context Ack
------ S3 Suspend Procedure ends ---------------------------------------------------------
CALL
Inter system TAU
116
1.3.4 MT CSFB to GERAN, UE in idle mode
1. Description
This test scenario verifies that a MT call is correctly handled by the MME when the UE is in idle mode and
accepts the call. CSFB is done to GERAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
- MT call
- Call end
5. Expected results
- Paging Request message is received from VLR. Service indicator information element indicates "CS call
indicator".
- MME sets the CN Domain indicator to "CS" in the Paging message towards the eNodeB
- UE sends an Extended Service Request message, a Service type field indicates MT CS Fallback
- MME sends a Service Request message to MSC indicating that the UE was in Idle mode
- MME initiates the SUSPEND procedure towards the S-GW for non-GBR bearers
- SUSPEND NOTIFICATION message is sent to S-GW
- MME initiates DELETE BEARER procedure towards the S-GW for GBR bearers
- DELETE BEARER COMMAND message is sent to S-GW

-----------------------------------------------> Service Request
<--------------------- Initial UE Context Setup (With CS Fallback
indicator)
117
-----------------------------> UE-Context Release Request
---------------------------> UE-Context Release complete
<------------------------------------------------------------> Suspend request/Response ( Non - GBR
Bearer )
----- S3 Suspend Procedure starts ( No Inter System RAU Procedure ) ------

-----------------------------------------------------------------------> S3_Suspend ACKSGSN Context Response
<--------------------------------------------------------------------- SGSN Context Ack
------ S3 Suspend Procedure ends -------------------------------------------------------
CALL
Inter system TAU
118
1.3.5 MO CSFB to UTRAN, UE in active mode
1. Description
This test scenario verifies that a MO call is correctly handled by the MME when the UE is in active mode and the
CSFB is done to UTRAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
- Call end
5. Expected results
- UE sends an Extended Service Request message, a Service type field indicates MO CS Fallback
- MME initiates an UE CONTEXT MODIFICATION procedure towards the eNB with the CS Fallback indicator
Inter System TAU

-----------------------------------------------> Service Request
<--------------------- UE-Context Modification Request (With CS
Fallback indicator)
119
---------------------> UE-Context Modification
Response
Request
<--------------------------- UE-Context Release
command
---------------------------> UE-Context Release
complete
<-----------------------------------------------------------------------> Suspend
request/Response ( Non - GBR
Bearer )
------ S3 Suspend Procedure starts ( No Inter System RAU Procedure ) ---------
<--------------------------------------------------------------------- S3_Suspend (SGSN

Context Request)
-----------------------------------------------------------------------> S3_suspend ACKSGSN
Context Response
<--------------------------------------------------------------------- SGSN Context Ack
------ S3 Suspend Procedure ends
--------------------------------------------------------- CALL
Inter system TAU
120
1.3.6 MO CSFB to UTRAN, UE in idle mode
1. Description
This test scenario verifies that a MO call is correctly handled by the MME when the UE is in
idle mode and the
CSFB is done to UNTRAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
2/2012 to “true”.
- Call end
5. Expected results
- UE sends an Extended Service Request message, a Service type field indicates MO CS

Fallback
- MME initiates an INITIAL UE CONTEXT SETUP procedure towards the eNB with the CS
Fallback indicator
- Cause value in UE CONTEXT RELEASE REQUEST message is "UE Not Available For PS
Service"
- MME receives SUSPEND Request message from SGSN and replies with SUSPEND_ACK
message
-----------------------------> NAS Extended Service

Request
<---------------------------- Initial
Context Setup Request (With CS Fallback indicator)
-----------------------------> Initial Context Setup
Response
121
Request(CAUSE : ps
------------------------------------------------> Release Access Bearer
Request
<------------------------------------------------ Release Access Bearer
Response
command
--------------------------->
122
1.3.7 MT CSFB to UTRAN, UE in active mode
1. Description
This test scenario verifies that a MT call is correctly handled by the MME when
the UE is in active mode and accepts the call. CSFB is done to UTRAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
2/2012 to “true”.
- MT call
- Call end
5. Expected results
- Paging Request message is received from VLR. Service indicator

information element indicates "CS call indicator".
- MME sends message CS SERVICE NOTIFICATION to the UE
- MME immediately sends a Service Request message to MSC indicating that the UE was in
Connected mode
- UE sends an Extended Service Request message, a Service type field indicates MT CS
Fallback
Fallback indicator
< ---------------------------------------------- Paging Request (Service

indicator=CS)
-----------------------------------------------> Service Reques
t
---------------------> NAS Extended Service
Request
<--------------------- UE-Context
Response
123
Request
command complete
---------------------------> UE-Context Release com
Inter-system CALL/ Inter system TAU
124
1.3.8 MT CSFB to UTRAN, UE in idle mode
1. Description
This test scenario verifies that a MT call is correctly handled by the MME when
the UE is in active mode and accepts the call. CSFB is done to UTRAN
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
2/2012 to “true”.
- MT call
- Call end
5. Expected results
- Paging Request message is received from VLR. Service indicator

information element indicates "CS call indicator".
- MME sends message CS SERVICE NOTIFICATION to the UE
- MME immediately sends a Service Request message to MSC indicating that the UE was in
Connected mode
- UE sends an Extended Service Request message, a Service type field indicates MT CS
Fallback
Fallback indicator
< ---------------------------------------------- Paging Request (Service

indicator=CS)
-----------------------------------------------> Service Reques
t
---------------------> NAS Extended Service
Request
<--------------------- UE-Context
Response
125
Request
command complete
---------------------------> UE-Context Release com
Inter-system CALL/ Inter system TAU
1.4 Additional Tests:
1.4.1 MO SMS to UTRAN/GERAN- UE Active and Idle
1. Description
This test scenario verifies that a MO SMS is correctly handled by the MME when
the UE is in active mode and delivers SMS.
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
2/2012 to “true”.
- UE is in active mode on LTE
- MO SMS
5. Expected results
- SMS delivered successfully
1.4.2 MT SMS to UTRAN/GERAN, UE Active and Idle Mode
1. Description
This test scenario verifies that a MT SMS is correctly handled by the MME when
the UE is in active mode and Mobile receives SMS. CSFB is done to
GERAN/UTRAN
- MME
- eNodeB
126
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
2/2012 to “true”.
- MT SMS
5. Expected results
- SMS received successfully
1.4.3 MO USSD to GERAN/UTRAN, UE in active/idle mode
1. Description
This test scenario verifies that a MO USSD is correctly handled by the MME
when the UE is in active mode and accepts the USSD
- MME
- eNodeB
- HSS
- SAE-GW
- UE
- MSS
3. Preconditions
2/2012 to “true”.
- MO SMS
5. Expected results
1.4.4 Check of features compared with BOQ content
1. Description
127
This test proves that the Features and licenses were delivered as described in the
BoQ.
FNS SGSN/MME
3. Preconditions
- All licenses are installed and enabled
- ZW7I:
5. Expected results
128
Feature Acceptance Certificate
Flexi NS 3.0
(Performed on / / )
This certifies that feature acceptance test cases

were performed completely.
Signature: ………………………………… ….……………………………..

Name: ………………………….…….. …………………………………
Title: ………………………….…….. …………………………………
Date: .............................................. …………………………………
NetOne Nokia
129

NETONE - Flexi Network Server - MME - Acceptance - Test - Plan v5.0.2.3

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

NETONE - Flexi Network Server - MME - Acceptance - Test - Plan v5.0.2.3

Caricato da

Copyright:

Formati disponibili

Flexi Network Server

Acceptance Test Doment

1 Acceptance test cases................................................................................................................................. 6

1.1 System maintenance

2. Required test environment

- OMU-<X> is WO-EX state and OMU-<Y> is SP-EX state

4. Guides for execution

- Make OMU switchover (MML-command: ZUSC:OMU,<WO-EX>:SP:;)

- OMU switchover is successful. Verify that using MML-command: ZUSI:OMU;

2. Required test environment

- MCHU-<X> is WO-EX state and MCHU-<Y> is SP-EX state

4. Guides for execution

2. Required test environment

- IPDU-<X> is WO-EX state and IPDU-<Y> is SP-EX state

4. Guides for execution

2. Required test environment

4. Guides for execution

eNodeB MME HSS SGW

-----------------------------> Tracking Area Update Request (active flag

<---------------------------- Tracking Area Update Accept

-----------------------------> Tracking Area Update complete

2. Required test environment

4. Guides for execution

- Copy databases to disk:

2. Required test environment

4. Guides for execution

eNodeB MME SGW

2. Required test environment

eNodeB MME SGW

-------------------------> S1 Setup Request

------------------------> Service Request.

<------------------------ Initial Context Setup Request

------------------------------> Modify Bearer Request

2. Required test environment

4. Guides for execution

- Copy databases to disk:

Verify redundancy of S1,S6a and S11 interfaces connected to IPDU blade.

2. Required test environment

4. Guides for execution

- Disable active interface in IPDU unit (ZQRI)

Verify redundancy of Ethernet interface in CPPU unit

2. Required test environment

4. Guides for execution

- Disable active interface in CPPU unit (ZQRI)

Verify redundancy of Ethernet interface in MMDU unit

2. Required test environment

4. Guides for execution

- Disable active interface in MMDU unit (ZQRI)

Verify redundancy of Ethernet interface in PAPU unit

2. Required test environment

4. Guides for execution

- Disable active interface in PAPU unit (ZQRI)

Verify redundancy of Ethernet interface in GBU unit

2. Required test environment

4. Guides for execution

- Disable active interface in GBU unit (ZQRI)

Verify redundancy of Ethernet interface in IPPU unit

2. Required test environment

4. Guides for execution

- Disable active interface in IPPU unit (ZQRI)

2. Required test environment

- MME (with two WO-EX CPPU)

4. Guides for execution