Lte Detail - S1 Interface

Long Term Evolution - Evolved Packet Core S1 Interface Conformance Test Plan

Table of Contents 1 SCOPE .............................................................................................................................. 10

2 REFERENCES .................................................................................................................... 10

3 ABBREVIATIONS .............................................................................................................. 11

4 OVERVIEW ....................................................................................................................... 14

5 TEST CONFIGURATION ..................................................................................................... 16

5.1 NETWORK & INTERFACE CONFIGURATION (OVERVIEW) ............................................................ 16 .............................................................................................................................................. 17 5.2 NETWORK ELEMENTS SOFTWARE VERSION ............................................................................. 18 5.3 TEST EQUIPMENT ............................................................................................................. 18

6 DETAILED TEST CASES ...................................................................................................... 19

6.1 MANAGEMENT, TRACING AND LOCATION REPORT TEST CASES ................................................... 19 6.1.1 MANAGEMENT PROCEDURES OVER SCTP ................................................................................. 19 6.1.1.1 S1 Setup between MME and eNodeB in a single PLMN configuration .......................... 19 6.1.1.1.1 Successful S1 Setup .................................................................................................... 19 6.1.1.1.2 Unsuccessful S1 Setup ................................................................................................ 21 6.1.1.2 S1 Setup between MME and eNodeB in a multiple PLMN configuration (MOCN configuration) ................................................................................................................................ 22 6.1.1.2.1 Successful S1 Setup .................................................................................................... 22 6.1.1.2.2 Unsuccessful S1 Setup ................................................................................................ 23 6.1.1.3 S1 Configuration Update (MME Initiated) ..................................................................... 24 6.1.1.3.1 Successful S1 MME Configuration Update ................................................................. 24 6.1.1.3.2 Unsuccessful S1 MME Configuration Update ............................................................. 25 6.1.1.4 S1 Configuration Update (eNodeB Initiated) ................................................................. 26 6.1.1.4.1 Successful S1 Configuration Update (eNodeB Initiated) ............................................ 26 6.1.1.4.2 Unsuccessful S1 Configuration Update (eNodeB Initiated) ........................................ 27 6.1.1.5 S1 Reset Procedures ...................................................................................................... 27 6.1.1.5.1 S1 Reset initiated by eNodeB ..................................................................................... 28 6.1.1.5.2 S1 Reset initiated by MME ......................................................................................... 29 6.1.1.6 S1 Recovery after nodes failure ..................................................................................... 30 6.1.1.6.1 S1 Recovery after eNodeB restart .............................................................................. 30 6.1.1.6.2 S1 Recovery after MME restart .................................................................................. 32 6.1.1.6.3 S1 Recovery after SGW restart ................................................................................... 33 6.1.1.6.4 S1 Recovery from S1 failure due to physical connections lost ................................... 35 6.1.2 TRACE AND LOCATION REPORTING PROCEDURES ........................................................................ 37 6.1.2.1 Trace Procedures ........................................................................................................... 37 6.1.2.1.1 Trace Start .................................................................................................................. 37 6.1.2.1.1.1 Trace Start supporting S1 interface ......................................................................... 37 6.1.2.1.1.2 Trace Start supporting X2 interface ......................................................................... 39 6.1.2.1.2 Deactivate Trace ......................................................................................................... 41 6.1.2.2 Location Reporting Procedures ..................................................................................... 43 6.1.2.2.1 Successful location reporting for a direct report of the UE location .......................... 43 6.1.2.2.2 Successful location reporting for serving cell change ................................................. 45

6.1.2.2.3 Successful cancellation of location reporting for serving cell change ........................ 47 6.2 FUNCTIONAL TEST CASES .................................................................................................... 49 6.2.1 ATTACH/DETACH .................................................................................................................. 49 6.2.1.1 Successful EPS Attach with UE unknown in MME and no Ciphering ............................. 49 6.2.1.2 Successful EPS Attach with UE unknown in MME and Ciphering .................................. 52 6.2.1.3 Successful EPS Attach procedure with UE known in MME and no Ciphering ................ 55 6.2.1.4 Successful EPS Attach procedure with UE known in MME with Ciphering .................... 57 6.2.1.5 Successful EPS Attach procedure with IMSI .................................................................. 59 6.2.1.6 Unsuccessful EPS Attach due to IMSI unknown on HSS ................................................ 61 6.2.1.7 Successful EPS Detach initiated by UE ........................................................................... 63 6.2.1.8 Successful EPS Detach initiated by UE due to switch off ............................................... 64 6.2.1.9 Successful EPS Detach initiated by MME ....................................................................... 66 6.2.2 E-RAB PROTOCOL PROCEDURES .............................................................................................. 68 6.2.2.1 E-RAB Setup ................................................................................................................... 68 6.2.2.1.1 Successful E-RAB establishment for ........................................................................... 68 6.2.2.1.2 Successful E-RAB establishment for UE Aggregate Maximum Bit Rate IE is included 69 6.2.2.1.3 Successful E-RAB establishment for multiple E-RABs ................................................. 71 6.2.2.2 E-RAB Modify ................................................................................................................. 72 6.2.2.2.1 Successful E-RAB modification ................................................................................... 72 6.2.2.2.2 Successful E-RAB modification for multiple E-RABs ................................................... 74 6.2.2.2.3 Successful and Unsuccessful E-RAB modification for multiple E-RABs ....................... 75 6.2.2.3 E-RAB Release ................................................................................................................ 76 6.2.2.3.1 E-RAB Release initiated by MME ................................................................................ 76 6.2.2.3.2 E-RAB Release initiated by eNodeB ............................................................................ 78 6.2.3 EPC BEARERS FUNCTIONAL PROCEDURES .................................................................................. 80 6.2.3.1 Dedicated bearer Activation .......................................................................................... 80 6.2.3.1.1 Successful Dedicated Bearer Activation initiated by the network .............................. 80 6.2.3.1.2 Successful Dedicated Bearer Activation initiated by the UE ....................................... 82 6.2.3.1.3 Successful Dedicated Bearer Activation during attach ............................................... 84 6.2.3.2 Bearer Modification ....................................................................................................... 86 6.2.3.2.1 Bearer Modification initiated by the EPC ................................................................... 86 6.2.3.2.1.1 PDN GW initiated bearer modification with QoS Update ....................................... 86 6.2.3.2.1.2 HSS initiated Subscriber QoS Modification .............................................................. 87 6.2.3.2.1.3 Network Initiated Bearer modification without Bearer QoS Update ...................... 88 6.2.3.2.2 Bearer Modification initiated by the UE ..................................................................... 90 6.2.3.2.2.1 UE Requested Bearer Modification accepted by the network ................................ 90 6.2.3.2.2.2 UE Requested Bearer Modification without QoS update accepted by the network92 6.2.3.3 Dedicated Bearer deactivation ...................................................................................... 94 6.2.3.3.1 PDN GW initiated Dedicated Bearer Deactivation ..................................................... 94 6.2.3.3.2 MME initiated Dedicated Bearer Deactivation ........................................................... 95 6.2.3.3.3 UE initiated Dedicated Bearer Deactivation ............................................................... 97 6.2.4 IDLE MODE AND CONTEXT MANAGEMENT PROCEDURES ............................................................. 98 6.2.4.1 Active to Idle mode Transition (Context Release) ......................................................... 98 6.2.4.1.1 UE/eNodeB Context Release due to User Inactivity with a single bearer established 98 6.2.4.1.2 UE/eNodeB Context Release due to User Inactivity with multiple bearers established 100 6.2.4.2 UE Context Release due to radio connection with UE lost .......................................... 102 6.2.4.3 Tracking Area Update procedures ............................................................................... 103

6.2.4.3.1 Normal Tracking area Update ................................................................................... 103 6.2.4.3.2 Normal Tracking area Update with bearer establishment requested ...................... 105 6.2.4.3.3 Combined Tracking and Location Area Update ........................................................ 107 6.2.4.3.4 Combined Tracking and Location Area Update with IMSI attach ............................. 109 6.2.4.3.5 Combined Tracking and Location Area Update with bearer establishment requested 111 6.2.4.3.6 Periodic Tracking area Update .................................................................................. 113 6.2.4.3.7 Tracking Area Update rejected due to No EPS Bearer context activated ............. 115 6.2.4.3.8 Tracking Area Update rejected due to implicitly detached ................................... 117 6.2.4.4 Paging .......................................................................................................................... 119 6.2.4.4.1 Paging with Paging DRX IE ........................................................................................ 119 6.2.4.4.2 Paging without Paging DRX IE ................................................................................... 120 6.2.4.5 Idle to Active Mode (Service Request) ........................................................................ 121 6.2.4.5.1 Successful Service Request invoked when the UE receives a paging request with CN domain indicator set to PS from the network in ECM-Idle mode (Single bearer) ................... 121 6.2.4.5.2 Successful Service Request invoked when the UE receives a paging request with CN domain indicator set to PS from the network in ECM-Idle mode (Multiple bearers) .............. 123 6.2.4.5.3 Successful Service Request invoked when the UE has pending user data to be sent in ECM-Idle mode (Single Bearer) ................................................................................................... 125 6.2.4.5.4 Successful Service Request invoked when the UE has pending user data to be sent in ECM-Idle mode (Multiple Bearers) .............................................................................................. 127 6.2.4.5.5 Successful Service Request invoked when the UE has uplink signaling pending in ECM-Idle mode ............................................................................................................................ 129 6.2.4.5.6 Successful Service Request invoked by 1xCS fallback when the UE is in Idle mode and has a mobile originating 1xCS fallback request ........................................................................... 131 6.2.4.5.7 Successful Service Request invoked by 1xCS fallback when the UE is in Active mode and has a mobile originating 1xCS fallback request .................................................................... 133 6.2.4.5.8 Successful Initial UE message with Emergency Flag enabled ................................... 135 6.2.5 USER PLANE PROTOCOL AND DATA TRANSFER TEST CASES ......................................................... 136 6.2.5.1.1 User Plane Control Test Cases .................................................................................. 136 6.2.5.1.1.1 GTP-U echo mechanism ......................................................................................... 136 6.2.5.1.1.2 GTP-U message End of Marker ........................................................................... 137 6.2.5.1.1.3 Graceful Error Indication handling by eNodeB ...................................................... 139 6.2.5.1.1.4 Graceful Error Indication handling by S-GW .......................................................... 140 6.2.5.1.2 Data Transfer on Default Bearer ............................................................................... 142 6.2.5.1.3 Data Transfer on Dedicated Bearer Test Cases ........................................................ 144 6.2.5.1.3.1 Successful Data Transfer with non-GBR Service and AM Mode ............................ 144 6.2.5.1.3.2 Successful Data Transfer with non-GBR Service and UM Mode ............................ 146 6.2.5.1.3.3 Successful Data Transfer with GBR Service and AM Mode ................................... 148 6.2.5.1.3.4 Successful Data Transfer with GBR Service and UM Mode ................................... 150 6.2.6 MOBILITY TEST CASES .......................................................................................................... 152 6.2.6.1.1 Intra-System Handover ............................................................................................. 152 6.2.6.1.1.1 X2 Based Handover ................................................................................................ 152 6.2.6.1.1.1.1 Successful HO with single E-RAB via X2 interface ............................................... 152 6.2.6.1.1.1.2 Successful HO with single E-RAB via X2 interface with Ciphering ...................... 155 6.2.6.1.1.1.3 Successful HO with multiple E-RABs via X2 interface ......................................... 157 6.2.6.1.1.1.4 Partially Successful HO with multiple E-RABs via X2 interface ........................... 160 6.2.6.1.1.1.5 Unsuccessful HO via X2 interface due to EPC Failure ......................................... 162 6.2.6.1.1.2 S1 Based Handover ................................................................................................ 164

6.2.6.1.1.2.1 Successful S1 HO with single E-RAB .................................................................... 164 6.2.6.1.1.2.2 Successful S1 HO with multiple E-RABs .............................................................. 166 6.2.6.1.1.2.3 Partially Successful S1 HO with multiple E-RABs ................................................ 168 6.2.6.1.1.2.4 Unsuccessful S1 based HO due to fail on MME-target eNodeB connectivity ..... 171 6.2.6.1.1.2.5 Unsuccessful S1 based HO due to not common ciphering algorithm ................. 173 6.2.6.1.1.2.6 Unsuccessful S1 based HO due to no resources available at target eNodeB ..... 175 6.2.6.1.2 Inter-System Handover ............................................................................................. 177 6.2.6.1.3 LTE to UTRAN Inter RAT Handover ........................................................................... 177 6.2.6.1.3.1 Successful LTE to UTRAN HO for a single E-RAB .................................................... 177 6.2.6.1.3.2 Successful LTE to UTRAN HO for multiple E-RABs ................................................. 180 6.2.6.1.3.3 LTE to UTRAN HO failure due to connectivity issues ............................................. 183 6.2.6.1.3.4 LTE to UTRAN HO failure due to not resources at NodeB ..................................... 184 6.2.6.1.3.5 LTE to UTRAN CS-Fallback: Inter RAT Handover triggered by Mobile Originated Call, UE in Idle Mode ........................................................................................................................... 186 6.2.6.1.3.6 LTE to UTRAN CS-Fallback: Inter RAT HO triggered by mobile Terminated Call, UE in Idle mode 189 6.2.6.1.3.7 LTE to UTRAN CS-Fallback: Inter RAT HO triggered by mobile Originated Call, UE in Active Mode 194 6.2.6.1.3.8 LTE to UTRAN CS-Fallback: Inter RAT HO triggered by mobile Terminated Call, UE in Active Mode 197 6.2.6.1.3.9 LTE to UTRAN SRVCC: Inter RAT Handover for VoIP Call ....................................... 202 6.2.6.1.3.10 LTE to UTRAN SRVCC: Inter RAT Handover for Data Transfer and VoIP Call ....... 204 6.2.6.1.4 UTRAN to LTE Inter RAT Handover ........................................................................... 206 6.2.6.1.4.1 Successful UTRAN to LTE Inter RAT Handover for a single RAB ............................. 206 6.2.6.1.4.2 Successful UTRAN to LTE Inter RAT Handover for multiple RABs .......................... 209 6.2.6.1.4.3 UTRAN to LTE Inter RAT Handover failure due to no resources at the eNodeB .... 212

Index of Figures

Figure 1: S1 Interface Protocol Stack towards MME ....................................................... 14 Figure 2: S1 Interface Protocol Stack towards S-GW ...................................................... 15 Figure 3: Network Configuration for regular test cases .................................................... 16 Figure 4: Network Configuration for intra-RAT HO Test Cases ..................................... 17 Figure 5: Network Configuration for Inter-RAT HO Test Cases ..................................... 17 Figure 6: Setup Procedure Successful Operation .......................................................... 20 Figure 7: S1 Setup Procedure - Unsuccessful Operation ................................................. 21 Figure 8: S1 Setup Procedure: Successful Operation ..................................................... 22 Figure 9: S1 Setup Procedure: Unsuccessful Operation ................................................. 23 Figure 10: MME Configuration Update Procedure: Successful Operation .................... 24 Figure 11: MME Configuration Update: Unsuccessful Operation .................................. 25 Figure 12: ENB Configuration Update Procedure: Successful Operation ...................... 26 Figure 13: ENB Configuration Update Procedure: Unsuccessful Operation ................. 27 Figure 14: Reset Procedure Initiated From the E-UTRAN Successful Operation ....... 28 Figure 15: Reset Procedure Initiated From the MME Successful Operation ............... 29 Figure 16: Reset Procedure Initiated From the E-UTRAN Successful Operation ....... 31 Figure 17: Reset Procedure Initiated From the MME Successful Operation ............... 33 Figure 18: UE Context Release Procedure Successful Operation ................................ 34 Figure 19: Setup Procedure Successful Operation ........................................................ 36 Figure 20: Trace Start Procedure ..................................................................................... 38 Figure 21: Cell Traffic Trace Procedure - Successful Operation .................................... 38 Figure 22: Trace Failure Indication Procedure ................................................................ 38 Figure 23: Trace Start Procedure ..................................................................................... 39 Figure 24: Cell Traffic Trace Procedure - Successful Operation .................................... 40 Figure 25: Trace Failure Indication Procedure ................................................................ 40 Figure 26: Deactivate Trace ............................................................................................. 41 Figure 27: Trace Failure Indication Procedure ................................................................ 42 Figure 28: Location Reporting Control Procedure - Successful Operation ..................... 43 Figure 29: Location Report Failure Indication Procedure ............................................... 44 Figure 30: Location Reporting Control Procedure - Successful Operation ..................... 45 Figure 31: Location Report Procedure - Successful Operation ....................................... 46 Figure 32: Location Report Failure Indication ................................................................ 46 Figure 33: Location Reporting Control Procedure - Successful Operation ..................... 47 Figure 34: Location Report Failure Indication Procedure ............................................... 48 Figure 35: Successful EPS Attach with UE unknown in MME and No Ciphering ......... 51 Figure 36: Successful EPS Attach with MME unknown in MME and Ciphering ........... 54 Figure 37: Successful EPS Attach procedure with UE known in MME and No Ciphering

................................................................................................................................... 56 Figure 38: Successful EPS Attach with UE known in MME and Ciphering .................... 58 Figure 39: Successful EPS Attach with IMSI ................................................................... 60 Figure 40: Unsuccessful EPS Attach due to IMSI unknown on HSS ............................... 62 Figure 41: Successful EPS detach initiated by UE ........................................................... 63 Figure 42: Successful EPS Detach initiated by UE due to switch off .............................. 65 Figure 43: Successful EPS Detach initiated by MME ...................................................... 67

Figure 44: Successful E-RAB establishment for single E-RAB ....................................... 68 Figure 45: Successful E-RAB establishment for single E-RAB with UE Maximum

Aggregate IE included .............................................................................................. 70 Figure 46: Successful E-RAB establishment for Multiple E-RABs ................................. 71 Figure 47: Successful E-RAB modification for single E-RAB ........................................ 73 Figure 48: Successful E-RAB Modification for multiple E-RABs .................................. 74 Figure 49: Successful and Unsuccessful E-RAB Modification for Multiple E-RABs ..... 76 Figure 50: E-RAB Release Initiated by MME .................................................................. 77 Figure 51: E-RAB Release initiated by eNodeB .............................................................. 79 Figure 52: Successful Dedicated Bearer Activation initiated by the network .................. 81 Figure 53: Successful Bearer Activation initiated by the UE ........................................... 83 Figure 54: Successful Bearer Activation during Attach ................................................... 85 Figure 55: PGW Initiated Bearer Modification with QoS Update ................................... 86 Figure 56: HSS initiated Subscriber QoS Modification ................................................... 87 Figure 57: Network Initiated Bearer Modification without QoS ...................................... 89 Figure 58: UE Requested Bearer Modification Accepted by the Network ...................... 91 Figure 59: UE Requested Bearer Modification without QoS Update accepted by the

Network ..................................................................................................................... 93 Figure 60: PGW Initiated Dedicated Bearer Deactivation ............................................... 94 Figure 61: MME initiated Dedicated Bearer Deactivation ............................................... 96 Figure 62: UE initiated Dedicated Bearer Deactivation ................................................... 97 Figure 63: UE/eNodeB Context Release initiated due to UE inactivity with single bearer

established ................................................................................................................. 99 Figure 64: UE/enodeB Context Release initiated due to UE inactivity with multiple

bearers established .................................................................................................. 101 Figure 65: UE Context Release due to Radio connection with UE lost ......................... 102 Figure 66: Normal Tracking Area Update ...................................................................... 104 Figure 67: Normal Tracking area Update with bearer establishment requested ............. 106 Figure 68: Combined Tracking and Location Area Update ............................................ 108 Figure 69: Combined Tracking and Location Area Update with IMSI attach ............... 110 Figure 70: Combined Tracking and Location Area Update with bearer establishment

requested ................................................................................................................. 112 Figure 71: Periodic Tracking area Update ...................................................................... 114 Figure 72: Tracking Area Update rejected due to "No EPS Bearer context activated" .. 116 Figure 73: Tracking Area Update rejected due to "implicitly detached" ........................ 118 Figure 74: Paging with Paging DRX IE ......................................................................... 119 Figure 75: Paging without Paging DRX IE .................................................................... 120 Figure 76: Successful Service Requested when UE receives a pacging request with CN

Domain set to "PS" (Singel bearer) ........................................................................ 122 Figure 77: Successful Service Requested when UE receives a paging request with CN

Domain indicator set to "PS" (Multiple bearers) .................................................... 124 Figure 78: Successful Service Request when UE has pending user data to be sent (Single

Bearer) ..................................................................................................................... 126 Figure 79: Successful Service Request when the UE has pending user to be sent (Multiple

Bearers) ................................................................................................................... 128 Figure 80: Successful Service Request when UE has uplink signaling pending in Idle

Mode ....................................................................................................................... 130

Figure 81: Successful Service Request when UE is in Idle mode and has a mobile originating 1xCS fallback request ........................................................................... 132

Figure 82: Successful Service Request when UE is in Active Mode and has a mobile originating 1xCS fallback request ........................................................................... 134

Figure 83: Successful Initial UE message with Emergency Flag enabled ...................... 135 Figure 84: GTP-U Echo mechanism ............................................................................... 136 Figure 85: GTP-U message "End of Marker" ................................................................. 138 Figure 86: Graceful Error Indication handling by eNodeB ............................................ 139 Figure 87: Graceful Error Indication handling by SGW ................................................ 141 Figure 88: Data Transfer on Default Bearer ................................................................... 143 Figure 89: Data Transfer on Dedicated Bearer with non-GBR Service and AM Mode . 145 Figure 90: Data Transfer on Dedicated Bearer with non-GBR service and UM Mode . 147 Figure 91: Data Transfer on Dedicated Bearer with GBR Service and AM Mode ........ 149 Figure 92: Data Transfer on Dedicated Bearer with GBR Service and UM Mode ........ 151 Figure 93: Successful X2 HO with single bearer ............................................................ 154 Figure 94: Successful HO with single E-RAB via X2 with Ciphering ........................... 156 Figure 95: Successful X2 HO with Multiple E-RABs .................................................... 159 Figure 96: Partially Successful HO via X2 interface with Multiple E-RABs ................ 161 Figure 97: Unsuccessful X2 HO Due to EPC Failure ..................................................... 163 Figure 98: Successful S1 HO with Single E-RAB.......................................................... 165 Figure 99: Successful S1 HO with Multiple E-RABs .................................................... 167 Figure 100: Partially Successful S1 HO with Multiple E-RABs .................................... 170 Figure 101: Unsuccessful S1 HO due to fail on MME-Target eNodeB connectivity .... 172 Figure 102: Unsuccessful S1 HO due to non common Ciphering algorithm ................. 174 Figure 103: Unsuccessful S1 based HO due to no resources available at target eNodeB

................................................................................................................................. 176 Figure 104: Successful LTE to UTRAN HO for single E-RAB (Preparation Phase) ... 178 Figure 105: Successful LTE to UTRAN HO for single E-RAB (Execution Phase) ...... 179 Figure 106: Successful LTE to UTRAN HO for Multiple E-RABs (Preparation Phase)

................................................................................................................................. 181 Figure 107: Successful LTE to UTRAN HO with Multiple E-RABs (Execution Phase)

................................................................................................................................. 182 Figure 108: LTE to UTRAN HO Failure due to connectivity issues ............................. 183 Figure 109: LTE to UTRAN HO failure due to not resources at NodeB ....................... 185 Figure 110: LTE to UTRAN CS-Fallback: MO call, UE in Idle Mode ......................... 188 Figure 111: LTE to UTRAN CS-Fallback: MT Call, UE in Idle Mode (Preparation Phase)

................................................................................................................................. 191 Figure 112: LTE to UTRAN CS-Fallback (Execution Phase with PS HO supported) .. 192 Figure 113: LTE to UTRAN CS-Fallback (Execution Phase without PS HO Supported)

................................................................................................................................. 193 Figure 114: LTE to UTRAN CS-Fallback, MO Call, UE in Active Mode .................... 196 Figure 115: LTE to UTRAN CS-Fallback, MT Call, UE in Active Mode (Preparation

Phase) ...................................................................................................................... 199 Figure 116: LTE to UTRAN CS-Fallback, MT Call, UE in Active Mode (Execution

Phase) without PS HO Support ............................................................................... 200 Figure 117: LTE to UTRAN SRVCC, Inter RAT HO for VoIP Call ............................. 203 Figure 118: LTE to UTRAN SRVCC, Inter RAT HO for Data Transfer with VoIP Call

................................................................................................................................. 205

Figure 119: Successful UTRAN to LTE Inter RAT HO for a single RAB (Preparation Phase) ...................................................................................................................... 207

Figure 120: Successful UTRAN to LTE Inter RAT HO for a single RAB (Execution Phase) ...................................................................................................................... 208

Figure 121: Successful UTRAN to LTE Inter RAT HO for Multiple RABs (Preparation Phase) ...................................................................................................................... 210

Figure 122: Successful UTRAN to LTE Inter RAT HO for Multiple RABs (Execution Phase) ...................................................................................................................... 211

Figure 123: UTRAN to LTE Inter RAT HO failure due to no resources at eNodeB ..... 213

1 Scope This document defines a proposal for the test suite to be used for S1 Interface Conformance testing. The goal is ensuring a graceful integration and interoperability between eNodeB-MME and eNodeB-SGW from different vendors.

2 References [1] 3GPP TS 36.413 Technical Specification Group Radio Access Network; Evolved

Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)

[2] 3GPP TS 29.281 Technical Specification Group Core Network and Terminals;

General

Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)

[3] 3GPP TS 36.300 Technical Specification Group Radio Access Network; Evolved

Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2

[4] 3GPP TS 23.401 Technical Specification Group Services and System Aspects;

General

Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

[5] 3GPP TS 36.331 Technical Specification Group Radio Access Network; Evolved

Universal Terrestrial Radio Access (E-UTRAN); Radio Resource Control (RRC) Protocol Specification


Handover procedures


Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3


Mobile

radio interface Layer 3 specification; Core network protocols; Stage 3

3 Abbreviations AS Access Stratum

BC Broadcast

BSC Base Station Controller

BM-SC Broadcast-Multicast Service Centre

BSS Base Station Sub-system

BTS Base Transceiver Station

CC Call Control

CDMA Code Division Multiple Access

CSG Closed Subscriber Group

CN Core Network

CS Circuit Switched

CSFB CS Fallback

DL Downlink

DRX Discontinuous Reception

ECGI E-UTRAN Cell Global Identifier

E-DCH Enhanced Dedicated Channels

E-RAB E-UTRAN Radio Access Bearer

eNB E-UTRAN NodeB

EP Elementary Procedure

EPC Evolved Packet Core

EPS Evolved Packet System

E-UTRAN Evolved UTRAN

GBR Guaranteed Bit Rate

GERAN GSM/EDGE Radio Access Network

GGSN Gateway GPRS Support Node

GPRS General Packet Radio Service

GSM Global System for Mobile communications

GTP GPRS Tunnelling Protocol

GTP-U GPRS Tunnelling Protocol-User plane

GUMMEI Globally Unique MME Identifier

GUTI Globally Unique Temporary UE Identity

GW Gateway

HeNB Home E-UTRAN NodeB

HFN Hyper Frame Number

HRPD High Rate Packet Data

HLR Home Location Register

HSDPA High Speed Downlink Packet Access

HSS Home Subscriber Server

HSUPA High Speed Uplink Packet Access

HO Handover

ID Identifier

IE Information Element

IETF Internet Engineering Task Force

IMSI International Mobile Subscriber Identity

IOT Interoperability Test

IP Internet Protocol

LAI Location Area Identifier

LTE Long Term Evolution

MBMS Multimedia Broadcast Multicast Service

MM Mobility Management

MME Mobility Management Entity

MMI Man Machine Interface

MO Mobile Originated

MOC Mobile Originated Call

MOCN Multi Operator Core Network

MS Mobile Station

MSC Mobile services Switching Center

MT Mobile Terminated

MTC Mobile Terminated Call

NAS Non Access Stratum

NNSF NAS Node Selection Function

NRT Non-Real Time

O&M Operation and Maintenance

PDN Packet Data Network

PDCP Packet Data Convergence Protocol

PDP Packet Data Protocol

PDU Protocol Data Unit

P-GW PDN Gateway

PLMN Public Land Mobile Network

PS Packet Switched

PSTN Public Switched Telephone Network

PTM Point To multipoint

P-TMSI Packet TMSI

PTP Point To Point

QoS Quality of Service

RAB Radio Access Bearer

RAC Routing Area Code

RAI Routing Area Identifier

RFCI RAB subFlow Combination Indicator

RIM RAN Information Management

RLC Radio Link Control

RNC Radio Network Controller

RRC Radio Resource Control

RT Real Time

SAP Service Access Point

SAPI Service Access Point Identifier

SCTP Stream Control Transmission Protocol

SGSN Serving GPRS Support Node

S-GW Serving Gateway

SMS Short Message Service

SN Sequence Number

SRVCC Single Radio Voice Call Continuity

S-TMSI S-Temporary Mobile Subscriber Identity

TAI Tracking Area Identity

TCP Transmission Control Protocol

TE Terminal Equipment

TEID Tunnel Endpoint Identifier

TFT Traffic Flow Template

TI Transaction Identifier

TMSI Temporary Mobile Subscriber Identity

UDP User Datagram Protocol

UE User Equipment

UE-AMBR UE-Aggregate Maximum Bit Rate

UL Uplink

UMTS Universal Mobile telecommunication System

UP User Plane

USIM Universal Subscriber Identity Module

UTRAN UMTS Terrestrial Radio Access Network

VLR Visitor Location Register

4 Overview

The purpose of this document is defining a test suite to guarantee the successful interoperability of the S1 interface between the EPC and the eNB/E-UTRAN. The E-UTRAN is connected to the MME (Mobility Management Entity) by means of the S1-MME for control-plane functionality and to the Serving Gateway (S-GW) by means of the S1-U for bearer-plane functionality

The following main areas are covered in testing S1 interface:

Protocol Transport Network Layer

o SCTP o Multi-Homing

Context Management Procedures Handover Signalling Paging NAS Transport Management Procedures UE Capability Info Indication Trace Procedures User Plane GTP-U Functional Oriented Test Mobility Management Session Management General Failure and Recovery Tests Data Transfer Paging Downlink Scheduling

Figure 1 shows the S1-MME interface protocol stack.

Figure 1: S1 Interface Protocol Stack towards MME

S1-AP

SCTP

IP

L2

L1

S1-AP

SCTP

IP

L2

L1

S1-MME HeNB MME

Figure 2 shows the S1-U interface protocol stack.

Figure 2: S1 Interface Protocol Stack towards S-GW

For all the diagrams and call flows included into this test plan, dotted lines imply that the procedure is optional as per the applicable 3GPP specifications.

GTP-U

UDP

IP

L2

L1

GTP-U

UDP

IP

L2

L1 S1-U

HeNB S-GW

5 Test Configuration This section lists the test equipment necessary to perform the test cases detailed in this document, together with the network configurations that will be required to execute all the test cases included in this document.

5.1 Network & Interface Configuration (Overview) Figure 3 depicts the Network Configuration for regular test cases.

SGi

S1-MME PCRF

Gx

S6a

HSS

Operator's IP Services

(e.g. IMS, PSS etc.)

Rx S10

TE

E-UTRAN

MME

S11

S5 Serving Gateway

PDN Gateway

S1-U UE

Figure 3: Network Configuration for regular test cases

Figure 4 depicts the Network Configuration for Intra-RAT HO test cases.

SGi

S1-MME PCRF

Gx

S6a

HSS



Rx S10

TE

E-UTRAN

MME

S11

S5 Serving Gateway

PDN Gateway

S1-U UE S1-MME

E-UTRAN S1-U

Figure 4: Network Configuration for intra-RAT HO Test Cases

Figure 5 depicts the Network Configuration for Inter-RAT HO test cases.

SGi

S12

S3 S1-MME

PCRF

Gx

S6a

HSS



Rx S10

SGSN

E-UTRAN

MME

S11

S5 Serving Gateway

PDN Gateway

S1-U

S4

UTRAN

IuPS

TE

UE

MSS

Gs D

IuCS

Figure 5: Network Configuration for Inter-RAT HO Test Cases

5.2 Network Elements Software Version

Network Element

Software Version

eNodeB

MME

SGW

PGW

HSS

PCRF

HLR (3G)

SGSN (3G)

5.3 Test Equipment The following test equipment will be required in order to carry out the tests defined in this document and verify the results:

Item/Tool Name/Model

Analyzer

Simulator

Mobiles

Others

6 Detailed Test Cases

6.1 Management, Tracing and Location Report Test Cases

6.1.1 Management Procedures over SCTP 6.1.1.1 S1 Setup between MME and eNodeB in a single PLMN configuration 6.1.1.1.1 Successful S1 Setup

Test Name: Successful establishment of SCTP association and Path Heartbeat in a single PLMN Configuration

References: TS 36.413, Section 8.7.3.2

Test Objective: Verify the successful establishment of the SCTP and S1 connection between eNodeB and MME as well as the periodic path heartbeat to monitor the link

Pre-Test Conditions: MME is configured with the SCTP and S1 parameters (1 PLMN Id) eNodeB is configured with the SCTP and S1 parameters (1 same PLMN Id) Both of the nodes shall be configured with the SCTP path heartbeat timer Verify IP connectivity between the two nodes

Test Procedure: Power on the MME and eNodeB Trigger eNodeB to initiate the S1 Setup

Expected Results: Verify that:

SCTP connection is initiated by eNodeB by sending a S1 setup Request message, including the TAC and the configured PLMN Identity included into the Broadcast PLMNs IE,

MME responds with the S1 setup response message acknowledging the connectivity and including the same PLMN Identity

S1 connectivity is successfully established between eNodeB and MME. SCTP heartbeats messages are exchanged successfully between both of the

nodes according to the timers configured.

eNB

S1 SETUP REQUEST

MME

S1 SETUP RESPONSE

Figure 6: Setup Procedure Successful Operation

6.1.1.1.2 Unsuccessful S1 Setup

eNB

S1 SETUP REQUEST

MME

S1 SETUP FAILURE

Figure 7: S1 Setup Procedure - Unsuccessful Operation

Test Name: Unsuccessful establishment of SCTP association between eNodeB and MME in a single PLMN Id Configuration


Test Objective: Verify the the graceful failure of S1 setup establishment between eNodeB and MME

Pre-Test Conditions: MME is configured with S1 parameters different than the one configures on

eNodeB (different TAC or different PLMN Id) eNodeB is configured with S1 parameters different than the one configured on

MME (different TAC or different PLMN Id) Verify IP connectivity between the two nodes



SCTP connection is initiated by eNodeB by sending a S1 setup Request message, including the TAC and the configured PLMN Identity included into the Broadcast PLMNs IE,

MME responds with the S1 setup failure including the reason of the unsuccessful establishment (e.g unknown TAC, unknown PLMN Id, etc)

No resource is hold by any network element after the unsuccessful S1 establishment

6.1.1.2 S1 Setup between MME and eNodeB in a multiple PLMN configuration (MOCN configuration)

6.1.1.2.1 Successful S1 Setup

eNB

S1 SETUP REQUEST

MME

S1 SETUP RESPONSE

Figure 8: S1 Setup Procedure: Successful Operation

Test Name: Successful establishment of SCTP association and Path Heartbeat in a multiple PLMN Configuration


Test Objective: Verify the successful establishment of the SCTP and S1 connection between eNodeB and MME as well as the periodic path heartbeat to monitor the link in a MOCN configuration

Pre-Test Conditions: MME is configured with the SCTP and S1 parameters eNodeB is configured with the SCTP and S1 parameters Both of the nodes shall be configured with the SCTP path heartbeat timer Verify IP connectivity between the two nodes



SCTP connection is initiated by eNodeB by sending a S1 setup Request message, including the TAC and the configured PLMN Identitier included into the Broadcast PLMNs IE,

MME responds with the S1 setup response message acknowledging the connectivity and including the same PLMN Identitier

S1 connectivity is successfully established between eNodeB and MME. SCTP heartbeats messages are exchanged successfully between both of the

nodes according to the timers configured.

6.1.1.2.2 Unsuccessful S1 Setup

eNB

S1 SETUP REQUEST

MME

S1 SETUP FAILURE

Figure 9: S1 Setup Procedure: Unsuccessful Operation

Test Name: Unsuccessful establishment of SCTP association between eNodeB and MME in a multiple PLMN Id Configuration


Test Objective: Verify the the graceful failure of S1 setup establishment between eNodeB and MME

Pre-Test Conditions: MME is configured with S1 parameters different than the one configures on

eNodeB (different TAC Ids) eNodeB is configured with S1 parameters different than the one configured on

MME (different TAC Ids) Verify IP connectivity between the two nodes



SCTP connection is initiated by eNodeB by sending a S1 setup Request message, including the TAC and the configured PLMN Identitier included into the Broadcast PLMNs IE,

MME responds with the S1 setup failure including the reason of the unsuccessful establishment (e.g unknown TAC, unknown PLMN Id, etc)

No resource is hold by any network element after the unsuccessful S1 establishment

6.1.1.3 S1 Configuration Update (MME Initiated) 6.1.1.3.1 Successful S1 MME Configuration Update

eNB

MME CONFIGURATION UPDATE

MME

MME CONFIGURATION UPDATE ACKNOWLEDGE

Figure 10: MME Configuration Update Procedure: Successful Operation

Test Name: Successful MME Configuration Update


Test Objective: Validate the successful application level configuration data update when initiated by MME

Pre-Test Conditions: Initial S1 setup has been successfully established between eNodeB and MME Verify IP connectivity between the two nodes

Test Procedure: Trigger MME to initiate the S1 Setup Update by changing the configuration (eg

change the name of MME or changing the MME relative capacity)


Validate that MME sends a S1-AP:MME Configuration Update including the new parameters (e.g new MME name, or new MME relative capacity)

Validate that eNodeB is acknowledging the update by sending back a S1-AP MME Configuration Update Acknowledge to MME

6.1.1.3.2 Unsuccessful S1 MME Configuration Update

eNB

MME CONFIGURATION UPDATE

MME

MME CONFIGURATION UPDATE FAILURE

Figure 11: MME Configuration Update: Unsuccessful Operation

Test Name: Unsuccessful MME Configuration Update


Test Objective: Validate the graceful unsuccessful application level configuration data update when initiated by MME

Pre-Test Conditions: Initial S1 setup has been successfully established between eNodeB and MME Make sure eNodeB is not configured to accept the PLMN-ID that MME will send

during the S1 MME Configuration Update. Verify IP connectivity between the two nodes

Test Procedure: Trigger MME to initiate the S1 Setup Update by changing the configuration

including a parameter not acceptable by eNodeB (eg unknown PLMN in enodeB)


Validate that MME sends a S1-AP:MME Configuration Update including the new parameters (e.g new PLMN-ID)

Validate that eNodeB is sending back a S1-APL MME configuration Update Failure including the reason of the unsuccessful S1 update.

6.1.1.4 S1 Configuration Update (eNodeB Initiated) 6.1.1.4.1 Successful S1 Configuration Update (eNodeB Initiated)

eNB

ENB CONFIGURATION UPDATE

MME

ENB CONFIGURATION UPDATE ACKNOWLEDGE

Figure 12: ENB Configuration Update Procedure: Successful Operation

Test Name: Successful eNodeB Configuration Update


Test Objective: Validate the successful application level configuration data update between eNodeB and MME when is initiated by eNodeB


Test Procedure: Trigger eNodeB to initiate the S1 Setup Update by changing the configuration (eg

supported TAC change in eNodeB)


Validate that eNodeB sends a S1-AP:EnodeB Configuration Update including the new parameters (e.g new TAC supported)

Validate that MME is acknowledging the update by sending back a S1-AP eNodeB Configuration Update Acknowledge to eNodeB

Validate that new S1 parameters have been successfully negotiated at both of the nodes.

6.1.1.4.2 Unsuccessful S1 Configuration Update (eNodeB Initiated)

eNB

ENB CONFIGURATION UPDATE

MME

ENB CONFIGURATION UPDATE FAILURE

Figure 13: ENB Configuration Update Procedure: Unsuccessful Operation

Test Name: Unsuccessful eNodeB Configuration Update


Test Objective: Validate the graceful unsuccessful application level configuration data update between eNodeB and MME when is initiated by eNodeB


Test Procedure: Trigger eNodeB to initiate the S1 Setup Update by changing the configuration to

one which MME can not accept (e.g TAC change to unknown TAC in MME)


Validate that eNodeB sends a S1-AP:EnodeB Configuration Update including the new parameters (e.g new TAC supported)

Validate that MME is sending back a S1-SP enodeB configuration update failure including the reason of the unsuccessful S1 update.

6.1.1.5 S1 Reset Procedures 6.1.1.5.1 S1 Reset initiated by eNodeB

MME eNB

RESET

RESET ACKNOWLEDGE

Figure 14: Reset Procedure Initiated From the E-UTRAN Successful

Operation

Test Name: S1 Reset initiated by eNodeB

References: TS 36.413, Section 8.7.1.2.2

Test Objective: Validate the successful reset initiated by eNodeB and the consequent initialization of the MME


Test Procedure: Trigger eNodeB to send a S1 Reset to MME


Validate that eNodeB sends a S1-AP Reset to MME Validate that MME sends back a S1-AP Reset Acknowledge message Validate that MME is releasing all allocated resources on S1 related to the UE and

removing the S1AP ID for all the UE associations.

6.1.1.5.2 S1 Reset initiated by MME

MME eNB

RESET

RESET ACKNOWLEDGE

Figure 15: Reset Procedure Initiated From the MME Successful Operation

Test Name: S1 Reset initiated by MME


Test Objective: Validate the successful reset initiated by MME and the consequent initialization of the eNodeB


Test Procedure: Trigger MME to send a S1 Reset to eNodeB


Validate that MME sends a S1-AP Reset to eNodeB Validate that eNodeB sends back a S1-AP Reset Acknowledge message Validate that eNodeB is releasing all allocated resources on S1 related to the UE

and removing the S1AP ID for all the UE associations.

6.1.1.6 S1 Recovery after nodes failure 6.1.1.6.1 S1 Recovery after eNodeB restart

Test Name: S1 recovery after eNodeB restart


Test Objective: Validate the S1 recovers successfully from the unexpected restart of the eNodeB

Pre-Test Conditions: Initial S1 setup has been successfully established between eNodeB and MME There is at least one UE attached with active context and data transfer is ongoing Verify IP connectivity between the two nodes Trigger the eNodeB to restart as in case of a failure (e.g power cycling) If no failure can be triggered, the pre-condition can be to execute a normal restart

as in test case 6.1.1.5.1).

Test Procedure: Initiated the system restart from eNodeB (preferably by emulating is unexpected,

failure e.g power cycle-).


If the failure does allow the eNodeB to send the S1 Reset: o Verify that eNodeB sends S1-AP: S1 RESET to MME o Verify that MME acknowledges by sending back a S1-AP: S1 RESET

acknowledgement to eNodeB o Validate that all the resources have been released after the restart

Validate that the S1 recovers from the restart, eNodeB is sending a S1-AP S1 SETUP REQUEST

Validate that MME is successfully acknowledging by sending S1-AP S1 SETUP RESPONSE

Validate that UE can reestablish the context and resume the data transfer successfully

MME eNB

RESET

RESET ACKNOWLEDGE

Figure 16: Reset Procedure Initiated From the E-UTRAN Successful

Operation

6.1.1.6.2 S1 Recovery after MME restart

Test Name: S1 recovery after MME restart


Test Objective: Validate the S1 recovers successfully from the unexpected restart of the MME

Pre-Test Conditions: Initial S1 setup has been successfully established between eNodeB and MME There is at least one UE attached with active context and data transfer is ongoing Verify IP connectivity between the two nodes Trigger the MME to restart as in case of a failure (e.g power cycling) If no failure can be triggered, the pre-condition can be to execute a normal restart

as in test case 6.1.1.5.2).

Test Procedure: Initiated the system restart from MME (preferably by emulating is unexpected,

failure e.g power cycle-).


If the failure does allow the MME to send the S1 Reset o Verify that MME sends S1-AP: S1 RESET to eNodeB o Verify that eNodeB acknowledges by sending back a S1-AP: S1 RESET

acknowledgement to MME o Validate that all the resources have been released after the restart

Validate that the S1 recovers from the restart, eNodeB is sending a S1-AP S1 SETUP REQUEST

Validate that MME is successfully acknowledging by sending S1-AP S1 SETUP RESPONSE

Validate that UE can reestablish the context and resume the data transfer successfully

MME eNB

RESET

RESET ACKNOWLEDGE

Figure 17: Reset Procedure Initiated From the MME Successful Operation

6.1.1.6.3 S1 Recovery after SGW restart

Test Name: S1 recovery after S-GW restart while data transfer is ongoing


Test Objective: Validate the S1-U recovers successfully from the unexpected restart of the S-GW

Pre-Test Conditions: Initial S1 setup has been successfully established between eNodeB and MME There is at least one UE attached with active context and data transfer is ongoing Verify IP connectivity between the two nodes

Test Procedure: Initiated the system restart from S-GW (emulate is unexpected, failure)


Verify that, when S-GW restarts, GTP-U may send a notification to the higher layer and O&M entities

Verify that, upon S-GW reinitialization, the data can be resumed successfully. If no same Tunnel Endpoints are honored at both of directions, GTP-U error indication will be sent to the other end to indicate about the Tunnel ID mismatch.

This procedure may involve a UE Context release from MME (S-GW can notify MME via S11) and UE context setup to re-activate the UE context successfully.

In Figure 18, UE context successfully established is not an actual procedure within the 3GPP S1-AP specs. The message UE Context is successfully established is meant to indicate that there are a collection of procedures executed in order to resume UE operation.

UE CONTEXT is successfully established

UE CONTEXT RELEASE COMMAND

eNB MME

UE CONTEXT RELEASE COMPLETE

Figure 18: UE Context Release Procedure Successful Operation

6.1.1.6.4 S1 Recovery from S1 failure due to physical connections lost

Test Name: S1 recovery from S1 failure due to transmission network failure (physical connections lost)


Test Objective: Validate the S1 recovers successfully from a physical connection failure


Test Procedure: Cause a failure on all the physical links carrying S1, for example by disconnecting

the cable or shutting down the interface Reconnect the cable before eNodeB and MME triggers RESET failure (if

disconnection of the cable, eNodeB and MME will not trigger RESET)


Message flow may depend on the vendor implementation Expected behavior is eNodeB to start a S1 SETUP REQUEST to MME, MME to

acknowledge and UE context activation is being successfully re-established after the physical link recovery

UE can resume the data transmission and no resource from previous call is hold by any network element

eNB

S1 SETUP REQUEST

MME

S1 SETUP RESPONSE

Figure 19: Setup Procedure Successful Operation

6.1.2 Trace and Location Reporting Procedures 6.1.2.1 Trace Procedures 6.1.2.1.1 Trace Start 6.1.2.1.1.1 Trace Start supporting S1 interface

MME eNB

TRACE START

Test Name: MME requests the eNodeB to start a trace supporting S1 interface and minimum depth

References: TS 36.413, Sections 8.10.1.2, 8.10.2.2, & 8.10.4.2

Test Objective: Validate that MME is able to request the eNodeB to start a trace session that supports S1 interface and minimum depth

Note: This is an optional requirement (not mandatory feature as per applicable specs)


Test Procedure: Send the trace control and configuration parameters from the MME. A trigger may

be manually initiated or received from HSS by using a ISDR message including the trace control parameters

Validate that eNodeB is subsequently tracing the UE accordingly


MME sends S1-AP Trace Start including a Trace Activation IE containing the Interfaces To Trace IE with the S1-MME bit set and the Trace depth IE set to minimum

Validate that eNodeB starts tracing the UE accordingly. The eNodeB will send to MME a S1-AP Cell Traffic Trace including the requested tracing information

Validate that MME can manage the Cell Traffic message according to the protocol and is capable of interpreting the tracing information reported by eNodeB.

Remark: If the tracing control failed, the eNodeB shall send to MME a S1-AP Trace Failure indication by including the reason of why the tracing control procedure was failed. In that case, the E-UTRAN Trace ID value shall be the same as the TraceID included into the Trace Start message originally sent by MME

Figure 20: Trace Start Procedure

eNodeB

CELL TRAFFIC TRACE

MME

Figure 21: Cell Traffic Trace Procedure - Successful Operation

MME eNB

TRACE FAILURE INDICATION

Figure 22: Trace Failure Indication Procedure

6.1.2.1.1.2 Trace Start supporting X2 interface

MME eNB

TRACE START

Figure 23: Trace Start Procedure

Test Name: MME requests the eNodeB to start a trace supporting X2 interface and minimum depth


Test Objective: Validate that MME is able to request the eNodeB to start a trace session that supports X2 interface and minimum depth



Test Procedure: Send the trace control and configuration parameters from the MME. A trigger may

be manually initiated or received from HSS by using a ISDR message including the trace control parameters

Validate that eNodeB is subsequently tracing the UE accordingly


MME sends S1-AP Trace Start including a Trace Activation IE containing the Interfaces To Trace IE with the X2 bit set and the Trace depth IE set to minimum

Validate that eNodeB starts tracing the UE accordingly. The eNodeB will send to MME a S1-AP Cell Traffic Trace including the requested tracing information

Validate that MME can manage the Cell Traffic message according to the protocol and is capable of interpreting the tracing information reported by eNodeB.


eNodeB

CELL TRAFFIC TRACE

MME

Figure 24: Cell Traffic Trace Procedure - Successful Operation

MME eNB



6.1.2.1.2 Deactivate Trace

MME eNB

DEACTIVATE TRACE

Figure 26: Deactivate Trace

Test Name: MME requests the eNodeB to stop the trace session

References: TS 36.413, Sections 8.10.3.2 & 8.10.2.2

Test Objective: Validate that MME is able to request the eNodeB to stop the trace session


Pre-Test Conditions: Initial S1 setup has been successfully established between eNodeB and MME There is at least one UE attached with active context and data transfer is ongoing eNodeB is currently tracing the S1 and/or X2 interfaces (MME previously sent a

S1-AP Trace Start message by enabling the interfaces to be monitored) Verify IP connectivity between the two nodes

Test Procedure: Send the deactivate trace control and configuration parameters from the MME. A

trigger may be manually initiated or received from HSS by using a ISDR message including the trace control parameters

Validate that eNodeB is subsequently stopping the tracing for the UE accordingly


MME sends S1-AP Deactivate Trace by including the same E-UTRAN Trace ID IE that was notified by MME when the trace control was started (same value than the one included into the S1-AP Start Trace message)

Validate that eNodeB stops tracing the UE accordingly


MME eNB



6.1.2.2 Location Reporting Procedures 6.1.2.2.1 Successful location reporting for a direct report of the UE location

eNB

LOCATION REPORTING CONTROL

MME

Figure 28: Location Reporting Control Procedure - Successful Operation

Test Name: Location Reporting Control sent to Request a direct report for a UE location


Test Objective: Validate that MME is able to request the eNodeB to report where the UE is currently located



Test Procedure: Initiate the location reporting for a direct location report for the UE Validate that eNodeB is subsequently reporting the current location of the UE


MME sends a S1-AP: Location Reporting Control by including a Request Type IE with Event IE=Direct and Report Area IE=ECGI

eNodeB is subsequently sending a S1:AP Location Report message with a E-UTRAN CGI IE indicating the cell where the UE is located. The Location Report message also includes a TAI IE indicating the tracing area where the UE is located and a Request Type IE including Event IE=Direct And Report Area IE=ECGI

Remark: If the location report control failed, the eNodeB shall send to MME a S1-AP Location Report Failure Indication with a Cause IE indicating the reason for the failure (e.g due to a ongoing HO)

MME eNB

LOCATION REPORT FAILURE INDICATION

Figure 29: Location Report Failure Indication Procedure

6.1.2.2.2 Successful location reporting for serving cell change

eNB


MME


Test Name: Successful location reporting for serving cell change


Test Objective: Validate that MME is able to request the eNodeB to report whenever a UE changes cells, and the eNodeB sends a location report with the correct service area identifier when that event happens



Test Procedure: Initiate the location reporting for a serving cell change for the UE Move the UE to another cell


MME sends a S1-AP: Location Reporting Control by including a Request Type IE with Event IE=Change of Service Cell and Report Area IE=ECGI

Verify that when the UE moves to a new cell the eNodeB is sending a S1:AP Location Report message with a E-UTRAN CGI IE indicating the cell where the UE is located. The Location Report message also includes a TAI IE indicating the tracing area where the UE is located and a Request Type IE including Event IE=Change of Service cell And Report Area IE=ECGI


eNB

LOCATION REPORT

MME

Figure 31: Location Report Procedure - Successful Operation

MME eNB


Figure 32: Location Report Failure Indication

6.1.2.2.3 Successful cancellation of location reporting for serving cell change

eNB


MME


Test Name: Successful cancellation of location reporting for serving cell change


Test Objective: Validate that MME is able to request the eNodeB to stop reporting whenever a UE changes cells, and the eNodeB sends a location report with the correct service area identifier when that event happens


Pre-Test Conditions: Initial S1 setup has been successfully established between eNodeB and MME There is at least one UE attached with active context and data transfer is ongoing Currently the location reporting is active for a serving cell change. Verify IP connectivity between the two nodes

Test Procedure: Initiate the cancel of the location reporting for serving cell change for the UE Move the UE to another cell


During the cancellation of the location reporting, the MME sends a S1-AP: Location Reporting Control by including a Request Type IE with Event IE=Stop Change of Service Cell and Report Area IE=ECGI

Verify that when the UE moves to a new cell the eNodeB not sending any S1-AP Location Report message.


MME eNB


Figure 34: Location Report Failure Indication Procedure

6.2 Functional Test Cases

6.2.1 Attach/Detach 6.2.1.1 Successful EPS Attach with UE unknown in MME and no Ciphering

Test Name: Successful EPS Attach with the UE unknown in MME and no Ciphering

References: 3GPP TS 23.401, Section 5.3.2.1

Test Objective: Validate the successful attach when UE is unknown to the MME and the ciphering is disabled

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is not attached and no context exists for the UE Ciphering is disabled GUTI is unknown in the MME

Test Procedure: Trigger UE attach Send Data in both of directions


eNodeB sends MME a S1-AP: Initial UE Message encapsulating the NAS Attach Request, which includes the EPS Mobile Identity IE (set to GUTI) and the ESM message container IE with the NAS PDN Connectivity Request message

MME sends a S1-AP: Downlink NAS Transport encapsulating the NAS Identity Request message, with Identity type IE=IMSI

eNodeB sends a S1-AP Uplink NAS Transport encapsulating the NAS: Identity Response message with the IMSI IE included.

MME sends a S1-AP Downlink NAS Transport encapsulating a NAS Authentication Request message

eNodeB sends a S1-AP Uplink NAS Transport encapsulating the NAS Authentication Response message

The MME sends a S1-AP: Downlink NAS Transport encapsulating a NAS Security Mode Command, with the Selected NAS Security Algorithms IE including EEA0 for Ciphering

eNodeB sends a S1-AP Uplink NAS Transport encapsulating a NAS security mode complete

MME sends a S1-AP Downlink NAS Transport encapsulating a NAS ESM Information Request

eNodeB sends a S1-AP Uplink NAS Transport encapsulating a NAS ESM Information Response

MME sends a S1-AP: Initial Context Setup Request encapsulating a NAS Attach Accept message. The message will include the NAS Activate Default EPS bearer context Request message, with the new GUTI IE included.

eNodeB sends a S1-AP: Initial Context Setup Response message eNodeB sends a S1-AP Uplink NAS Transport encapsulating a NAS Attach

Complete. The ESM message container IE will include a NAS Activate Deftault EPS Bearer Context Accept message.

Validate that the Data can be transferred on both of directions with no Ciphering being performed

Figure 35: Successful EPS Attach with UE unknown in MME and No

Ciphering

6.2.1.2 Successful EPS Attach with UE unknown in MME and Ciphering

Test Name: Successful EPS Attach with the UE unknown in MME and Ciphering


Test Objective: Validate the successful attach when UE is unknown to the MME and the ciphering is enabled

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is not attached and no context exists for the UE Ciphering is enabled GUTI is unknown in the MME








The MME sends a S1-AP: Downlink NAS Transport encapsulating a NAS Security Mode Command, with the Selected NAS Security Algorithms IE including EEA1 or EEA2 for Ciphering as per the configuration







Validate that the Data can be transferred on both of directions with Ciphering being performed

Figure 36: Successful EPS Attach with MME unknown in MME and

Ciphering

6.2.1.3 Successful EPS Attach procedure with UE known in MME and no Ciphering

Test Name: Successful EPS Attach with the UE known in MME and no Ciphering


Test Objective: Validate the successful attach when UE is known to the MME and the ciphering is disabled

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is not attached and no context exists for the UE Ciphering is disabled GUTI is known in the MME


Figure 37: Successful EPS Attach procedure with UE known in MME and

No Ciphering





The MME sends a S1-AP: Downlink NAS Transport encapsulating a NAS Security Mode Command, with the Selected NAS Security Algorithms IE including EEA0 for Ciphering








6.2.1.4 Successful EPS Attach procedure with UE known in MME with

Ciphering

Test Name: Successful EPS Attach with the UE known in MME and Ciphering


Test Objective: Validate the successful attach when UE is known to the MME and the ciphering is enabled

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is not attached and no context exists for the UE Ciphering is enabled GUTI is known in the MME


Figure 38: Successful EPS Attach with UE known in MME and Ciphering





The MME sends a S1-AP: Downlink NAS Transport encapsulating a NAS Security Mode Command, with the Selected NAS Security Algorithms IE including EEA1 or EEA2 for Ciphering as per the configuration








6.2.1.5 Successful EPS Attach procedure with IMSI

Test Name: Successful EPS Attach with IMSI


Test Objective: Validate the successful attach when UE is unknown to the MME and the UE has no GUTI

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is not attached UE has no GUTI



eNodeB sends MME a S1-AP: Initial UE Message encapsulating the NAS Attach Request, which includes the EPS Mobile Identity IE (set to IMSI) and the ESM message container IE with the NAS PDN Connectivity Request message



The MME sends a S1-AP: Downlink NAS Transport encapsulating a NAS Security Mode Command, with the Selected NAS Security Algorithms IE including EEA0, EEA1 or EEA2 for Ciphering as per the configuration






Complete. The ESM message container IE will include a NAS Activate Default EPS Bearer Context Accept message.


Figure 39: Successful EPS Attach with IMSI

6.2.1.6 Unsuccessful EPS Attach due to IMSI unknown on HSS

Test Name: Unsuccessful EPS Attach due to IMSI unknown on HSS

References: 3GPP TS 23.401, Section 5.3.2.1 3GPP TS 36.413, Section 8.6.2.1, 8.6.2.2, 8.6.2.3

3GPP TS 24.301, Section 5.5.1.2.2, 5.4.4.2

Test Objective: Validate the graceful failed EPS Attach when IMSI is unknown on HSS

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is not attached and no GUTI is known on MME IMSI is unknown on HSS

Test Procedure: Trigger UE attach





MME sends a S1-AP: Downlink NAS Transport encapsulating an Attach Reject with the corresponding Cause IE included.

No resource is hold by any network element

Figure 40: Unsuccessful EPS Attach due to IMSI unknown on HSS

6.2.1.7 Successful EPS Detach initiated by UE

Figure 41: Successful EPS detach initiated by UE

Test Name: Successful EPS Detach UE initiated

References: 3GPP TS 23.401, Section 5.3.8.2.1 3GPP TS 36.413, Section 8.6.2.3, 8.6.2.2, 8.3.3.2

3GPP TS 24.301, Section 5.5.2.2.1

Test Objective: Validate the successful detach procedure when is initiated by the UE

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is attached

Test Procedure: Trigger UE detach


eNodeB sends MME a S1-AP: Uplink NAS Transport encapsulating a Detach Request including the GUTI inside the EPS mobile Identity IE

MME sends a S1-AP Downlink NAS Transport encapsulating a NAS Detach Accept

MME sends a S1-AP Downlink NAS Transport encapsulating a S1 UE Context Release Command

eNodeB acknowledges it back by sending a S1-AP Uplink NAS Transport encapsulating a S1 UE Context Release complete.

There is no resource hold by any network element after the detach is completed.

6.2.1.8 Successful EPS Detach initiated by UE due to switch off

Test Name: Successful EPS Detach UE initiated

References: 3GPP TS 23.401, Section 5.3.8.2.1 3GPP TS 36.413, Section 8.6.2.3, 8.3.3.2

Test Objective: Validate the successful detach procedure when is initiated by the UE

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is attached

Test Procedure: Trigger UE detach by switching off the UE


eNodeB sends MME a S1-AP: Uplink NAS Transport encapsulating a Detach Request including a Detach Type IE with the switch off bit set

MME sends a S1-AP Downlink NAS Transport encapsulating a S1 UE Context Release Command

eNodeB acknowledges it back by sending a S1-AP Uplink NAS Transport encapsulating a S1 UE Context Release complete.

There is no resource hold by any network element after the detach is completed.

Figure 42: Successful EPS Detach initiated by UE due to switch off

6.2.1.9 Successful EPS Detach initiated by MME

Test Name: Successful EPS Detach MME initiated

References: 3GPP TS 23.401, Section 5.3.8.3 3GPP TS 24.301, 5.5.2.3.1

3GPP TS 36.413, Section 8.3.3.2

Test Objective: Validate the successful detach procedure when is initiated by the MME

Pre-Test Conditions: S1 interface is properly set up between eNodeB and MME/SGW UE is attached and in active state

Test Procedure: Trigger UE detach from the

Date post:	18-Oct-2015
Category:	Documents
Upload:	abraamoff
View:	78 times
Download:	10 times

Lte Detail - S1 Interface

Documents