Warning!

Your browser may not support JavaScript

IxLoad: Evolved Packet Core (EPC) Network Testing

IxLoad is a full-featured layer 4-7 test application that provides real-world traffic emulation testing of voice, video, and data networks and components. IxLoad simultaneously emulates multiple layer 7 protocol activities, making it perfect for testing application delivery systems and components that use deep packet inspection (DPI).

IxLoad supports the 3GPP GTP-c V2 (Release 8) protocol as well as the GTP-u protocol, enabling testing of the wireless evolved packet core (EPC). This is accomplished through the emulation the key components: the mobility management entity (MME) and the eNode B on the S11 and S1-U interfaces.

Figure 1: Evolved Packet Core Test Configuration

In conjunction with its MME and eNode B emulations, IxLoad can simulate the behaviour of hundreds of thousands of subscribers utilizing assorted services. For example, an emulated subscriber could be surfing the web, downloading files using FTP, checking and sending e-mail, exchanging data with peer-to-peer applications and watching video on demand. All layer 7 protocol emulations are fully stateful implementations that can interact with real servers and peers.

IxLoad's very intuitive GUI greatly simplifies test construction by removing the requirement for building or modifying the GTP-c signalling procedures. IxLoad's GTP implementation is a complete state machine that exposes many options for configuration and flexibility. This implementation makes it unnecessary to build complex and error prone message exchange sequences in order to construct a test case. With IxLoad, subscribers are simply configured and assigned to specific real-world activities, such as VoIP calls and web browsing. The test is then ready to start; the process is fast and time-efficient.

IxLoad's GTP emulation includes all the procedures required for full testing: default and dedicated bearers, network and MME initiation, deletion and modification of the bearers, as well as full control over the traffic mix and intensity. IxLoad also supports a clever handover mechanism in which a mobility path from one eNode B to another is defined as a list, along with a variable handover interval. IxLoad performs the handovers transparently, without any user intervention. Even the type of handover (X2 or S1 based) will be automatically detected and executed, based on the user configuration.

IxLoad's complete automation facilities allow regression tests to run unattended. A fully-featured TCL interface provides access to all IxLoad functions. In addition, a test configuration created with the IxLoad GUI can be turned into an automation TCL script with a single click of the mouse. In this way IxLoad tests can be run without GUI interaction, and without any required programming.

Protocols

Control plane

3GPP TS 29.274 Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)
3GPP TS 29.281 GPRS Tunneling Protocol User Plane (GTPv1-U)
IPv4 transport

User Plane

HTTP
HTTPS
FTP
POP3
SMTP
IMAP
SIP/TCP + RTP
Peer-to-peer protocols
Video on demand with RTSP
Application replay - stateful replay of packet captures
IPv4 and IPv6 support for applications

All layer 7 protocols listed above are true stateful emulations that can interact with real network devices.

GTP-c Features

Support for default and dedicated bearers, with a maximum of 11 per user equipment (UE)
UE/MME initiated dedicated bearer creation, modification and deletion
Network initiated dedicated bearer creation, modification and deletion
Echo request and response
Dynamic IP address allocation during session establishment
Ability to configure the number of simulated MMEs and eNode Bs
Supports eNode B (X2) handovers with configurable event intervals and mobility paths between eNode Bs
Supports S1-based handovers with indirect data forwarding tunnels
Configuration of IMSI, MSISDN, IMEISV, RAC/LAC/TAC, MCC/MNC
Configuration of QoS and TFT per layer 7 activity.
Prebuilt TFTs are supplied, with the ability to manually override with user TFT definition.
Configurable APNs per subscriber range

Figure 2: Handover configuration

L 7 (User Plane) Features

Leverages Acceleron XP/NP TCP acceleration technology to achieve very high throughput rates for http and Application Replay activities
Multiple activities can be configured per UE, each having a distinct layer 7 protocol and data rate profile
Each layer 7 activity can be configured with a distinct objective consisting of
- Simulated users
- Throughput
- Connections/sec
- Connection attempts/sec
- Layer 7 transactions/sec
- Concurrent connections/sessions
Support for IPv4 and IPv6 traffic activities
Multiple L7 activities can be mapped to distinct UE ranges, in any combination, giving each range an individual traffic profile and mix
Multiple activities mapped to a single UE range can be configured to request a dedicated bearer or can use the existing default bearer
Running activities can be remapped from the default bearer to a dedicated bearer dynamically
Supports L7 protocol servers and peers on the Gi interface

Figure 3: Layer 7 protocol activity QoS and TFT configuration when using a dedicated bearer

Performance

	Per Port CPU Acceleron-NP	Per Load Module Acceleron-NP
Max GTP-c transaction rate	500 transactions/second	6000 transactions/second
Max UEs with Default Bearers – ftp	53.5 K	642 K
Max UEs with Default Bearers – http	100 K	1.2 M
Max UEs with Default Bearers – Video on Demand (VOD)	2 K	24 K
Max UEs with Default Bearers – POP3	86.5 K	1038 K
Max UEs with Default Bearers – SMTP	90 K	1080 K
Max UEs with Default Bearers – IMAP	74 K	888 K
Max throughput – ftp (25K UEs with Default Bearers per port)	620 Mbps	7.44 Gbps
Max throughput – ftp (50K UEs with Default Bearers per port)	270 Mbps	3.2 Gbps
Max throughput – http (25K UEs with Default Bearers per port)	83 x 959 Mbps (ULxDL)	1 x 9.6 Gbps (ULxDL)
Max throughput – http (50K UEs with Default Bearers per port)	83 x 958 Mbps	1 x 9.6 Gbps
Max throughput – http (100K UEs with Default Bearers per port)	83 x 961 Mbps	1 x 9.6 Gbps
Max throughput – Application Replay (25K UEs with Default Bearers per port)	848 x 848 Mbps	9.6 x 9.6 Gbps
Max throughput – Application Replay (50K UEs with Default Bearers per port)	844 x 844 Mbps	9.6 x 9.6 Gbps
Max throughput – Application Replay ( 80K UEs with Default Bearers per port)	820 x 820 Mbps	9.6 x 9.6 Gbps
Max throughput – P2P (25K UEs with Default Bearers per port)	500 Mbps	6 Gbps
Max throughput – P2P (50K UEs with Default Bearers per port)	330 Mbps	3.9 Gbps

Notes:

UL: Uplink
DL: Downlink
Throughput values expressed with UL x DL means that the values are achieved simultaneously.

Statistics and Measurements

All statistics and measurements listed below are available in real time, as well as in comma separated value (CSV) format at the end of a test.

Figure 4: Statistics displayed in real time during a test.

Global statistics

All bearers

Statistic	Description
Sessions Initiated	The aggregate number of default and dedicated bearer sessions initiated during the test.
Sessions Succeeded	The aggregate number of default and dedicated bearer sessions that were successfully initiated during the test.
Sessions Failed	The aggregate number of default and dedicated bearer sessions for which initiation failed during the test.
Tear Down Initiated	The number of default and dedicated bearer sessions for which teardown was initiated.
Tear Down Succeeded	The number of default and dedicated bearer sessions for which teardown was successfully completed.
Tear Down Failed	The number of default and dedicated bearer sessions for which teardown failed. These failures are usually the result of timeouts or Context Not Found errors.
Active Sessions	The total number of default and dedicated bearer sessions that are currently active.
Max Active Sessions	The maximum number of default and dedicated bearer sessions that were active at any one time during test execution.
Mobility Events	The total number of default and dedicated bearer mobility events that occurred during execution of the test.
HSS Updates Initiated	The number of times an emulated MME initiates an update by sending a Modify Bearer Command to the SGW.
HSS Updates Succeeded	The number of times the SGW responds to the MME with an Update Bearer Request for the default bearer (in response to the MME sending a Modify Bearer Command).
HSS Updates Failed	The number of times the SGW responds to the MME with a Modify Bearer Failure Indication (in response to the MME sending a Modify Bearer Command).
Lifetime Expired	The total number of times that the lifetime timers have expired for UEs during execution of the test. If the lifetime timer expires, each UE will stop all active and scheduled activities, and will schedule the detach procedure.

Dedicated bearers

Statistic	Description
Sessions Initiated(D)	The number of sessions that were initiated for dedicated bearers during execution of the test.
Sessions Succeeded(D)	The number of sessions that were successfully set up for dedicated bearers during execution of the test.
Sessions Failed(D)	The number of sessions that failed to come up for dedicated bearers during execution of the test.
Sessions Terminated(D)	The total number of sessions that were terminated, for dedicated bearers, during execution of the test.
Active Sessions(D)	The total number of dedicated bearer sessions that are active.
Max Active Sessions(D)	The maximum number of dedicated bearer sessions that have been active at any one time during execution of the test.

Bearer activation failures

Statistic	Description
A.F. Internal Error	The number of activation failures that the plug-in categorized as internal errors. (Refer to What Is the Internal Error Statistic? for more information.)
A.F. Timeout	The number of bearers that failed to activate as a result of a timeout while waiting for the SGW to answer.
A.F. Accepted partially	The number of requests that returned a Cause Value of "Request accepted partially".
A.F. Invalid message format	The number of requests that returned a Cause Value of "Invalid Message Format".
A.F. Mandatory IE incorrect	The number of activation failures that returned a Cause Value of "Mandatory IE Incorrect".
A.F. Mandatory IE missing	The number of activation failures that returned a Cause Value of "Mandatory IE Missing".
A.F. System failure	The number of activation failures that returned a Cause Value of "System Failure".
A.F. No resources available	The number of activation failures that returned a Cause Value of "No Resources Available".
A.F. No memory is available	The number of activation failures that returned a Cause Value of "No Memory Is Available".
A.F. Semantic error in the TFT operation	The number of activation failures that returned a Cause Value of "Semantic Error in the TFT Operation".
A.F. Syntactic error in the TFT operation	The number of activation failures that returned a Cause Value of "Syntactic Errors in the TFT Operation".
A.F. Semantic errors in packet filter	The number of activation failures that returned a Cause Value of "Semantic Error in the Packet Filter".
A.F. Syntactic errors in packet filter	The number of activation failures that returned a Cause Value of "Syntactic Errors in the Packet Filter".
A.F. Missing or unknown APN	The number of activation failures that returned a Cause Value of "Missing or Unknown APN". This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because either the APN was not included (although required) or the APN could not be resolved.
A.F. Unexpected repeated IE	The number of activation failures that returned a Cause Value of "Unexpected Repeated IE".
A.F GRE key not found	The number of activation failures that returned a Cause Value of "GRE Key Not Found".
A.F. Preferred PDN type not supported	The number of activation failures that returned a Cause Value of "Preferred PDN Type not Supported".
A.F. All dynamic addresses are occupied	The number of activation failures that returned a Cause Value of "All Dynamic Addresses are Occupied".
A.F. UE context without TFT already activated	The number of activation failures that returned a Cause Value of "UE Context without TFT Already Activated".
A.F. User authentication failed	The number of activation failures that returned a Cause Value of "User Authentication Failed". This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication.
A.F. APN access denied no subscription	The number of activation failures that returned a Cause Value of "APN Access Denied No Subscription". This Cause Value indicates that the subscriber does not have the necessary subscription for access the requested APN.
A.F. Request rejected	The number of requests that returned a Cause Value of "Request Rejected".
A.F. PGW not responding	The number of activation failures that returned a Cause Value of "PGW Not Responding".
A.F. Unable to page UE due to Suspension	The number of activation failures that returned a Cause Value of "Unable to page UE due to Suspension".
A.F. Conditional IE missing	The number of activation failures that returned a Cause Value of "Conditional IE missing". This indicates that one or more conditional information elements are missing from a Request message.
A.F. APN Restriction type incompatible with currently active PDN connection	The number of activation failures that returned a Cause Value of "APN Restriction type incompatibility with currently active PDP Contexts". This cause values indicates to an SGSN that a PDP Context was not allowed to be created or moved by the GGSN because if it had been, the rules for PDP Context coexistence (as described in 3GPP TS 23.060, sub-clause 15.4), would have been broken.
A.F. Unsupported error cause received	The number of activation failures that returned a Cause Value of "Unsupported Error Cause Received".

Bearer delete failures

Statistic	Description
D.F Internal Error	The number of bearer deletion failures that the plug-in categorized as internal errors. (Refer to What Is the Internal Error Statistic? for more information.)
D.F Timeout	The number of HSS Initiated Subscribed QoS Modification procedures that failed as a result of a timeout while waiting for the peer to answer.
D.F Invalid Message Format	The number of Modify Bearer Failure Indications received with a Cause Value of "Invalid Message Format".
D.F Mandatory IE incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Incorrect".
D.F Mandatory IE missing	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Missing".
D.F Optional IE incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Optional IE Incorrect".
D.F Unexpected repeated IE	The number of Modify Bearer Failure Indications received with a Cause Value of "Unexpected Repeated IE".
D.F Context not found	The number of Modify Bearer Failure Indications received with a Cause Value of "Context not found". If a node receives a message for which it has no context, it responds with this Cause Value in its corresponding response message to the sender.
D.F Unsupported error cause received	The number of bearer deletion failures that returned a Cause Value of "Unsupported Error Cause Received".

Bearer update failures

Statistic	Description
U.F Internal Error	The number of bearer update failures that the plug-in categorized as internal errors. (Refer to What Is the Internal Error Statistic? for more information.)
U.F Timeout	The number of bearers that could not be updated as a result of a timeout while waiting for the SGW to answer.
U.F Request accepted partially	The number of bearer updates that returned a Cause Value of "Request Accepted Partially".
U.F Request Rejected	The number of bearer update requests that returned a Cause Value of "Request Rejected".
U.F Invalid Message Format	The number of bearer update failures that returned a Cause Value of "Invalid Message Format".
U.F Service not supported	The number of update failures that returned a Cause Value of "Service Not Supported".
U.F Mandatory IE incorrect	The number of bearer update failures that returned a Cause Value of "Mandatory IE Incorrect".
U.F Mandatory IE missing	The number of bearer update failures that returned a Cause Value of "Mandatory IE Missing".
U.F System failure	The number of bearer update failures that returned a Cause Value of "System Failure".
U.F Unexpected repeated IE	The number of bearer update failures that returned a Cause Value of "Unexpected Repeated IE".
U.F Unsupported error cause received	The number of bearer update failures that returned a Cause Value of "Unsupported Error Cause Received".
U.F Context not found	The number of bearer update failures that returned a Cause Value of "Context not found". If a node receives a message for which it has no context, it responds with this Cause Value in its corresponding response message to the sender.
U.F No Memory Available	The number of bearer update failures that returned a Cause Value of "No Memory Is Available".

HSS update failures

Statistic	Description
MBCF Timeout	The number of HSS Initiated Subscribed QoS Modification procedures that failed as a result of a timeout while waiting for the peer to answer.
MBCF Context Not Found	The number of Modify Bearer Failure Indications received with a Cause Value of "Context not found". If a node receives a message for which it has no context, it responds with this Cause Value in its corresponding response message to the sender.
MBCF No Resources Available	The number of Modify Bearer Failure Indications received with a Cause Value of "No Resources Available".
MBCF No Memory Is Available	The number of Modify Bearer Failure Indications received with a Cause Value of "No Memory Available".
MBCF System Failure	The number of Modify Bearer Failure Indications received with a Cause Value of "System Failure".
MBCF Mandatory IE Incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Incorrect".
MBCF Mandatory IE Missing	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Missing".
MBCF Optional IE Incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Optional IE Incorrect".
MBCF Invalid Message Format	The number of Modify Bearer Failure Indications received with a Cause Value of "Invalid Message Format".
MBCF Unexpected repeated IE	The number of Modify Bearer Failure Indications received with a Cause Value of "Unexpected Repeated IE".

Traffic failures

Statistic	Description
GTP-u Tx Packets Dropped	The number of GTP-u packets that were transmitted but dropped.
GTP-u Rx Packets Dropped	The number of inbound GTP-u packets that were dropped.
GTP-u Rx Error Indication Messages	The number of GTP-u error indication packets that were received from the DUT.

Incorrect control plane messages

Statistic	Description
Incorrect control plane requests	The number of incorrect control plane requests that were received from the DUT.
Incorrect control plane responses	The number of incorrect control plane responses that were received from the DUT.

Handover statistics – total

Statistic	Description
Total handovers initiated	The total number of handovers (both X2-based and S1-based) that have been initiated.
Total handovers succeeded	The total number of handovers (both X2-based and S1-based) that were successfully completed.
Total handovers failed	The total number of handovers (both X2-based and S1-based) that failed.
Total handovers skipped	The total number of handovers (both X2-based and S1-based) that were skipped. A handover may be skipped if the preceding handover has been delayed and is still in progress.
X2 based handovers initiated	The total number of X2-based handovers that have been initiated.
X2 based handovers succeeded	The total number of X2-based handovers that have been successfully completed.
X2 based handovers failed	The total number of X2-based handovers that failed.
S1 based handovers initiated	The total number of S1-based handovers that have been initiated.
S1 based handovers succeeded	The total number of S1-based handovers that have been successfully completed.
S1 based handovers failed	The total number of S1-based handovers that failed.

X2-based handover

Statistic	Description
X2-Based No MME change No SGW change initiated	The number of X2-based handovers (with no MME change and no SGW change) that have been initiated.
X2-Based No MME change No SGW change succeeded	The number of X2-based handovers (with no MME change and no SGW change) that have been successfully completed.
X2-Based No MME change No SGW change failed	The number of X2-based handovers (with no MME change and no SGW change) that failed.
X2-Based No MME change SGW change initiated	The number of X2-based handovers (when the MME is unchanged and the Serving GW is relocated) that have been initiated.
X2-Based No MME change SGW change succeeded	The number of X2-based handovers (when the MME is unchanged and the Serving GW is relocated) that have been successfully completed.
X2-Based No MME change SGW change failed	The number of X2-based handovers (when the MME is unchanged and the Serving GW is relocated) that failed.

S1-based handover – direct forwarding

Statistic	Description
S1-Based MME change No SGW change Direct Fwd initiated	The number of S1-based direct forwarding handovers (when the MME is relocated and the SGW is not relocated) that have been initiated.
S1-Based MME change No SGW change Direct Fwd succeeded	The number of S1-based direct forwarding handovers (when the MME is relocated and the SGW is not relocated) that have been successfully completed.
S1-Based MME change No SGW change Direct Fwd failed	The number of S1-based direct forwarding handovers (when the MME is relocated and the SGW is not relocated) that failed.
S1-Based MME change SGW change Direct Fwd initiated	The number of S1-based direct forwarding handovers (when both the MME and the SGW are relocated) that have been initiated.
S1-Based MME change SGW change Direct Fwd succeeded	The number of S1-based direct forwarding handovers (when both the MME and the SGW are relocated) that have been successfully completed.
S1-Based MME change SGW change Direct Fwd failed	The number of S1-based direct forwarding handovers (when both the MME and the SGW are relocated) that failed.

S1-based handover – indirect forwarding

Statistic	Description
S1-Based No MME change No SGW change Indirect Fwd initiated	The number of S1-based indirect forwarding handovers (with no MME change and no SGW change) that have been initiated.
S1-Based No MME change No SGW change Indirect Fwd succeeded	The number of S1-based indirect forwarding handovers (with no MME change and no SGW change) that have been successfully completed.
S1-Based No MME change No SGW change Indirect Fwd failed	The number of S1-based indirect forwarding handovers (with no MME change and no SGW change) that failed.
S1-Based No MME change SGW change Indirect Fwd initiated	The number of S1-based indirect forwarding handovers (when the MME is unchanged and the Serving GW is relocated) that have been initiated.
S1-Based No MME change SGW change Indirect Fwd succeeded	The number of S1-based indirect forwarding handovers (when the MME is unchanged and the Serving GW is relocated) that have been successfully completed.
S1-Based No MME change SGW change Indirect Fwd failed	The number of S1-based indirect forwarding handovers (when the MME is unchanged and the Serving GW is relocated) that failed.
S1-Based MME change No SGW change Indirect Fwd initiated	The number of S1-based indirect forwarding handovers (when the MME is relocated and the SGW is not relocated) that have been initiated.
S1-Based MME change No SGW change Indirect Fwd succeeded	The number of S1-based indirect forwarding handovers (when the MME is relocated and the SGW is not relocated) that have been successfully completed.
S1-Based MME change No SGW change Indirect Fwd failed	The number of S1-based indirect forwarding handovers (when the MME is relocated and the SGW is not relocated) that failed.
S1-Based MME change SGW change Indirect Fwd initiated	The number of S1-based indirect forwarding handovers (when both the MME and the SGW are relocated) that have been initiated.
S1-Based MME change SGW change Indirect Fwd succeeded	The number of S1-based indirect forwarding handovers (when both the MME and the SGW are relocated) that have been successfully completed.
S1-Based MME change SGW change Indirect Fwd failed	The number of S1-based indirect forwarding handovers (when both the MME and the SGW are relocated) that failed.

Session management messages

Statistic	Description
Create Session Request Tx	The number of "Create Session Request" messages sent by the emulated MME.
Create Session Response Rx	The number of "Create Session Response" messages received by the emulated MME.
Create Session Request Retry	The number of "Create Session Request" message retries sent by the emulated MME.
Modify Bearer Request Tx	The number of "Modify Bearer Request" messages sent by the emulated MME.
Modify Bearer Response Rx	The number of "Modify Bearer Response" messages received by the emulated MME.
Modify Bearer Request Retry	The number of "Modify Bearer Request" message retries sent by the emulated MME.
Delete Session Request Tx	The number of "Delete Session Request" messages sent by the emulated MME.
Delete Session Response Rx	The number of "Delete Session Response" messages received by the emulated MME.
Delete Session Request Retry	The number of "Delete Session Request" message retries sent by the emulated MME.

Bearer management messages

Statistic	Description
Create Bearer Response Tx	The number of "Create Bearer Response" messages sent by the emulated MME.
Create Bearer Request Rx	The number of "Create Bearer Request" messages received by the emulated MME.
Update Bearer Response Tx	The number of "Update Bearer Response" messages sent by the emulated MME.
Update Bearer Request Rx	The number of "Update Bearer Request" messages received by the emulated MME.
Delete Bearer Response Tx	The number of "Delete Bearer Response" messages sent by the emulated MME.
Delete Bearer Response Retry	The number of "Delete Bearer Response" message retries sent by the emulated MME.
Bearer Resource Command Tx	The number of "Delete Bearer Request" messages received by the emulated MME.
Bearer Resource Command Retry	The number of "Delete Bearer Response" message retries sent by the emulated MME.
Delete Bearer Failure Indication PGW Rx	The number of "Delete Bearer Failure Indication" messages received from the PDN GW.
Bearer Resource Failure Indication Rx	The number of "Bearer Resource Failure Indication" messages received from the PDN GW. This occurs if a requested QoS is not granted.
Modify Bearer Failure Indication Rx	The number of "Modify Bearer Failure Indication" messages received by the emulated MME.
Modify Bearer Command Tx	The number of "Modify Bearer Command" messages sent by the emulated MME.
Modify Bearer Command Retry	The number of "Modify Bearer Command" message retries sent by the emulated MME.
Delete Bearer Command Tx	The number of "Modify Bearer Command" messages sent by the emulated MME.
Delete Bearer Command Retry	The number of "Modify Bearer Command" message retries sent by the emulated MME.

Path management messages

Statistic	Description
Echo Request Tx	The number of "Echo Request" messages sent by the emulated MME.
Echo Response Rx	The number of "Echo Response" messages received by the emulated MME.
Echo Request Retry	The number of "Echo Request" message retries sent by the emulated MME.
Echo Response Tx	The number of "Echo Response" messages sent by the emulated MME.
Echo Request Rx	The number of "Echo Request" messages received by the emulated MME.

Other messages

Statistic	Description
Version Not Supported Indication Tx	The number of "Version Not Supported Indication" messages sent by the emulated MME.
Version Not Supported Indication Rx	The number of "Version Not Supported Indication" messages received by the emulated MME.
Downlink Data Notification Rx	The number of "Downlink Data Notification" messages received by the emulated MME.
Downlink Data Notification Acknowledgement Tx	The number of "Downlink Data Notification" message acknowledgements sent by the emulated MME.
Downlink Data Notification Failure Indication Tx	The number of "Downlink Data Notification" message failure indications sent by the emulated MME.
Create Indirect Data Forwarding Request Tx	The number of "Create Indirect Data Forwarding Tunnel Request" messages sent by the emulated MME.
Create Indirect Data Forwarding Response Rx	The number of "Create Indirect Data Forwarding Tunnel Response" messages received by the emulated MME.
Create Indirect Data Forwarding Request Retry	The number of "Create Indirect Data Forwarding Tunnel Request" message retries sent by the emulated MME.

Create session response time

Statistic	Description
CS &lgt;= 5ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was less than or equal to 5 milliseconds.
CS > 5ms and <= 10ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 5 milliseconds but less than or equal to 10 milliseconds.
CS > 10ms and <= 15ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 10 milliseconds but less than or equal to 15 milliseconds.
CS > 15ms and <= 20ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 15 milliseconds but less than or equal to 20 milliseconds.
CS > 20ms and <= 30ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 20 milliseconds but less than or equal to 30 milliseconds.
CS > 30ms and <= 50ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 30 milliseconds but less than or equal to 50 milliseconds.
CS > 50ms and <= 75ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 50 milliseconds but less than or equal to 75 milliseconds.
CS > 75ms and <= 100ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 75 milliseconds but less than or equal to 100 milliseconds.
CS > 100ms	The number of Create Session Response messages received from the SGW, for which the time of receipt was greater than 100 milliseconds.

Delete session response time

Statistic	Description
DS <= 5ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was less than or equal to 5 milliseconds.
DS > 5ms and <= 10ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 5 milliseconds but less than or equal to 10 milliseconds.
DS > 10ms and <= 15ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 10 milliseconds but less than or equal to 15 milliseconds.

Delete session response time

Statistic	Description
DS > 15ms and <= 20ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 15 milliseconds but less than or equal to 20 milliseconds.
DS > 20ms and <= 30ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 20 milliseconds but less than or equal to 30 milliseconds.
DS > 30ms and <= 50ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 30 milliseconds but less than or equal to 50 milliseconds.
DS > 50ms and <= 75ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 50 milliseconds but less than or equal to 75 milliseconds.
DS > 75ms and <= 100ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 75 milliseconds but less than or equal to 100 milliseconds.
DS > 100ms	The number of Delete Session Response messages received from the SGW, for which the time of receipt was greater than 100 milliseconds.

Modify session response time

Statistic	Description
MB <= 5ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was less than or equal to 5 milliseconds.
MB > 5ms and <= 10ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 5 milliseconds but less than or equal to 10 milliseconds.
MB > 10ms and <= 15ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 10 milliseconds but less than or equal to 15 milliseconds.
MB > 15ms and <= 20ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 15 milliseconds but less than or equal to 20 milliseconds.
MB > 20ms and <= 30ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 20 milliseconds but less than or equal to 30 milliseconds.
MB > 30ms and <= 50ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 30 milliseconds but less than or equal to 50 milliseconds.
MB > 50ms and <= 75ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 50 milliseconds but less than or equal to 75 milliseconds.
MB > 75ms and <= 100ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 75 milliseconds but less than or equal to 100 milliseconds.
MB > 100ms	The number of Modify Bearer Response messages received from the SGW, for which the time of receipt was greater than 100 milliseconds.

Bearer resource command response time

Statistic	Description
BRC <= 5ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was less than or equal to 5 milliseconds.
BRC > 5ms and <= 10ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 5 milliseconds but less than or equal to 10 milliseconds.
BRC > 10ms and <= 15ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 10 milliseconds but less than or equal to 15 milliseconds.
BRC > 15ms and <= 20ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 15 milliseconds but less than or equal to 20 milliseconds.
BRC > 20ms and <= 30ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 20 milliseconds but less than or equal to 30 milliseconds.
BRC > 30ms and <= 50ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 30 milliseconds but less than or equal to 50 milliseconds.
BRC > 50ms and <= 75ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 50 milliseconds but less than or equal to 75 milliseconds.
BRC > 75ms and <= 100ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 75 milliseconds but less than or equal to 100 milliseconds.
BRC > 100ms	The number of Bearer Resource Command Response messages received from the SGW, for which the time of receipt was greater than 100 milliseconds.

Rates – control plane

Statistic	Description
Successful Activation Rate (tunnels/s)	The session establishment rate (tunnels per second) measured across all s during execution of the test.
Successful Deactivation Rate (tunnels/s)	The session teardown rate (tunnels per second) measured across all s during execution of the test.

Rates – user plane

Statistic	Description
GTP-u packets/s Tx	The GTP-U packet transmission rate (tunnels per second) measured across all s during execution of the test.
GTP-u packets/s Rx	The GTP-U packet receive rate (tunnels per second) measured across all s during execution of the test.
GTP-u packets/s Reflected	The count of data plane packets sent on indirect tunnels, measured across all s during execution of the test. When an S1-based handover is executed, a new tunnel is created for indirect forwarding, where the downlink packets are reflected back to the SGW during the handover process. Once the handover is complete, the SGW transmits those reflected packets to the target eNodeB.

Per session statistics

All bearers

Statistic	Description
Interface Identifier	The identifier that IxLoad assigns to this eGTP interface.
IMSI	The International Mobile Subscriber Identity (IMSI) associated with the mobile device configured for this session.
IP	The UE negotiated IP address (received in the Create Session Response, PAA IE).
State	The current state of the UE session: Detached Attach Scheduled Attach Initiated Attached Partially (CreateSessionRequest/Response messages were exchanged and the cause in CreateSessionResponse was "A.F. Accepted".) Attached Detach Scheduled Detach Initiated
Current ENodeB Range	The eNodeB range in which this session has been initiated.
Setup Success	The number of bearers (default and dedicated) that have been successfully activated for this session.
Activation Failure Cause	The cause of the activation acceptance or failure: >None< Paging Local detach Complete detach Move to non 3GPP Request end Accepted Accepted partially New PDN network preference New PDN single address bearer only Accepted end Context non existent Invalid message format Version not supported by next peer Invalid length Service not supported Mandatory IE incorrect Mandatory IE missing Optional IE incorrect System failure No Resources available Semantic error in the TFT Operation Syntactic error in the TFT Operation Semantic errors in packet filter Syntactic errors in packet filter Missing or unknown APN Unexpected Repeated IE Gre Key Not Found Reallocation Failure Denied in RAT Preferred PDN Type Not Supported All dynamic addresses are occupied Ue context without TFT already activated Protocol type not supported UE not responding UE refuses Service denied Unable to page ue No memory available User Authentication Failed Apn access denied no subscription Request rejected Ptmsi signature mismatch IMSI not known Semantic error in the TAD operation Syntactic error in the TAD operation Reserved Message Value Received Pgw Not Responding Collision With Network Initiated Request Conditional IE Missing Restriction type incompatible with currently active PDN connection Rejected End Internal error Timeout
Teardown Initiated	The number of bearers (default and dedicated) for which a deactivation request has been sent to the SGW for this session.
Teardown Success	The number of bearers (default and dedicated) for which a teardown request has been successfully completed for this session.
Teardown Fail	The cause of the teardown acceptance or failure: >None< Paging Local detach Complete detach Move to non 3GPP Request end Accepted Accepted partially New PDN network preference New PDN single address bearer only Accepted end Context non existent Invalid message format Version not supported by next peer Invalid length Service not supported Mandatory IE incorrect Mandatory IE missing Optional IE incorrect System failure No Resources available Semantic error in the TFT Operation Syntactic error in the TFT Operation Semantic errors in packet filter Syntactic errors in packet filter Missing or unknown APN Unexpected Repeated IE Gre Key Not Found Reallocation Failure Denied in RAT Preferred PDN Type Not Supported All dynamic addresses are occupied Ue context without TFT already activated Protocol type not supported UE not responding UE refuses Service denied Unable to page ue No memory available User Authentication Failed Apn access denied no subscription Request rejected Ptmsi signature mismatch IMSI not known Semantic error in the TAD operation Syntactic error in the TAD operation Reserved Message Value Received Pgw Not Responding Collision With Network Initiated Request Conditional IE Missing Restriction type incompatible with currently active PDN connection Rejected End Internal error Timeout
Lifetime Expired	The number of times that the lifetime timers have expired for this session. If the lifetime timer expires, each UE will stop all active and scheduled activities, and will schedule the detach procedure.

All bearers

Statistic	Description
Setup Initiated(D)	The number of dedicated bearers for which an activation request has been sent to the SGW for this session.
Setup Success(D)	The number of dedicated bearers that have been successfully activated for this session.
Activation Failure Cause(D)	The cause of the activation acceptance or failure: >None< Paging Local detach Complete detach Move to non 3GPP Request end Accepted Accepted partially New PDN network preference New PDN single address bearer only Accepted end Context non existent Invalid message format Version not supported by next peer Invalid length Service not supported Mandatory IE incorrect Mandatory IE missing Optional IE incorrect System failure No Resources available Semantic error in the TFT Operation Syntactic error in the TFT Operation Semantic errors in packet filter Syntactic errors in packet filter Missing or unknown APN Unexpected Repeated IE Gre Key Not Found Reallocation Failure Denied in RAT Preferred PDN Type Not Supported All dynamic addresses are occupied Ue context without TFT already activated Protocol type not supported UE not responding UE refuses Service denied Unable to page ue No memory available User Authentication Failed Apn access denied no subscription Request rejected Ptmsi signature mismatch IMSI not known Semantic error in the TAD operation Syntactic error in the TAD operation Reserved Message Value Received Pgw Not Responding Collision With Network Initiated Request Conditional IE Missing Restriction type incompatible with currently active PDN connection Rejected End Internal error Timeout
Teardown Initiated(D)	The number of dedicated bearers for which a deactivation request has been sent to the SGW for this session.
Teardown Success(D)	The number of dedicated bearers for which a teardown request has been successfully completed for this session.
Teardown Fail(D)	The cause of the teardown acceptance or failure: >None< Paging Local detach Complete detach Move to non 3GPP Request end Accepted Accepted partially New PDN network preference New PDN single address bearer only Accepted end Context non existent Invalid message format Version not supported by next peer Invalid length Service not supported Mandatory IE incorrect Mandatory IE missing Optional IE incorrect System failure No Resources available Semantic error in the TFT Operation Syntactic error in the TFT Operation Semantic errors in packet filter Syntactic errors in packet filter Missing or unknown APN Unexpected Repeated IE Gre Key Not Found Reallocation Failure Denied in RAT Preferred PDN Type Not Supported All dynamic addresses are occupied Ue context without TFT already activated Protocol type not supported UE not responding UE refuses Service denied Unable to page ue No memory available User Authentication Failed Apn access denied no subscription Request rejected Ptmsi signature mismatch IMSI not known Semantic error in the TAD operation Syntactic error in the TAD operation Reserved Message Value Received Pgw Not Responding Collision With Network Initiated Request Conditional IE Missing Restriction type incompatible with currently active PDN connection Rejected End Internal error Timeout

Handover – totals
Same as gobal statistics.

X2-based handover
Same as gobal statistics.

S1-based handover – direct forwarding
Same as gobal statistics.

S1-based handover – indirect forwarding
Same as gobal statistics.

Create response time
Same as global statistics.

Delete session response time
Same as global statistics.

Modify session response time
Same as global statistics.

Bearer resource command response time
Same as global statistics.

Modify bearer command response time
Same as global statistics.

Per range statistics

All bearers

Statistic	Description
Range Identifier	The identifier that IxLoad assigns to this eGTP range.
Setup Initiated	The number of bearers (default and dedicated) in this eGTP range for which an activation request has been sent to the SGW.
Setup Success	The number of bearers (default and dedicated) that have been successfully activated in this eGTP range.
Setup Fail	The number of bearers (default and dedicated) in this eGTP range for which an activation request failed.
Teardown Initiated	The number of bearers (default and dedicated) in this eGTP range for which a deactivation request has been sent to the SGW.
Teardown Success	The number of bearers (default and dedicated) in this eGTP range for which a teardown request has been successfully completed.
Teardown Fail	The number of bearers (default and dedicated) in this eGTP range for which a teardown request failed.
HSS Updates Initiated	The number of times an emulated MME initiates an update by sending a Modify Bearer Command to the SGW.
HSS Updates Succeeded	The number of times the SGW responds to the MME with an Update Bearer Request for the default bearer (in response to the MME sending a Modify Bearer Command).
HSS Updates Failed	The number of times the SGW responds to the MME with a Modify Bearer Failure Indication (in response to the MME sending a Modify Bearer Command).
Lifetime Expired	The number of times that the lifetime timers have expired for this range. If the lifetime timer expires, each UE will stop all active and scheduled activities, and will schedule the detach procedure.
Active	The total number of sessions that are active for all bearers in this range.
Max Active	The maximum number of sessions that were active at any one time, for all bearers, in this range.
Successful Activation Rate	The successful session establishment rate (tunnels per second) measured across all sessions in this range.
Successful Deactivation Rate	The successful session de-activation rate (tunnels per second) measured across all sessions in this range.

Dedicated bearers

Statistic	Description
Setup Initiated(D)	The number of dedicated bearers in this eGTP range for which an activation request has been sent to the SGW.
Setup Success(D)	The number of dedicated bearers that have been successfully activated in this eGTP range.
Setup Fail(D)	The number of dedicated bearers in this eGTP range for which an activation request failed.
Teardown Initiated(D)	The number of dedicated bearers in this eGTP range for which a deactivation request has been sent to the SGW.
Teardown Success(D)	The number of dedicated bearers in this eGTP range for which a teardown request has been successfully completed.
Teardown Fail(D)	The number of dedicated bearers in this eGTP range for which a teardown request failed.
Active(D)	The total number of sessions that are active for all dedicated bearers in this range.
Max Active(D)	The maximum number of sessions that were active at any one time, for all dedicated bearers, in this range.

Handover totals
Same as global statistics

X2-based handover
Same as global statistics

S1-based handover – direct forwarding
Same as global statistics

S1-based handover – indirect forwarding

Same as global statistics

Bearer activation failures

Statistic	Description
A.F Internal Error	The number of activation failures that the plug-in categorized as internal errors. (Refer to What Is the Internal Error Statistic? for more information.)
A.F Timeout	The number of bearers that failed to activate as a result of a timeout while waiting for the SGW to answer.
A.F Accepted partially	The number of requests that returned a Cause Value of "Request accepted partially".
A.F Request rejected	The number of requests that returned a Cause Value of "Request Rejected".
A.F Invalid message format	The number of requests that returned a Cause Value of "Invalid Message Format".
A.F No resources available	The number of activation failures that returned a Cause Value of "No Resources Available".
A.F Mandatory IE incorrect	The number of activation failures that returned a Cause Value of "Mandatory IE Incorrect".
A.F Mandatory IE missing	The number of activation failures that returned a Cause Value of "Mandatory IE Missing".
A.F System failure	The number of activation failures that returned a Cause Value of "System Failure".
A.F User authentication failed	The number of activation failures that returned a Cause Value of "User Authentication Failed". This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication.
A.F All dynamic PDP addresses are occupied	The number of activation failures that returned a Cause Value of "All Dynamic Addresses are Occupied".
A.F No memory is available	The number of activation failures that returned a Cause Value of "No Memory Is Available".
A.F Semantic error in the TFT operation	The number of activation failures that returned a Cause Value of "Semantic Error in the TFT Operation".
A.F Syntactic error in the TFT operation	The number of activation failures that returned a Cause Value of "Syntactic Errors in the TFT Operation".
A.F Semantic errors in packet filter	The number of activation failures that returned a Cause Value of "Semantic Error in the Packet Filter".
A.F Syntactic errors in packet filter	The number of activation failures that returned a Cause Value of "Syntactic Errors in the Packet Filter".
A.F Missing or unknown APN	The number of activation failures that returned a Cause Value of "Missing or Unknown APN". This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because either the APN was not included (although required) or the APN could not be resolved.
A.F Unknown PDP address or type	The number of activation failures that returned a Cause Value of "Unknown PDP address or PDP type". This Cause Value indicates that the GGSN does not support the PDP type or the PDP address.
A.F UE context without TFT already activated	The number of activation failures that returned a Cause Value of "UE Context without TFT Already Activated".
A.F APN access denied no subscription	The number of activation failures that returned a Cause Value of "APN Access Denied No Subscription". This Cause Value indicates that the subscriber does not have the necessary subscription for access the requested APN.
A.F APN Restriction type incompatibility with currently active bearers	The number of activation failures that returned a Cause Value of "APN Restriction type incompatibility with currently active PDP Contexts". This cause values indicates to an SGSN that a PDP Context was not allowed to be created or moved by the GGSN because if it had been, the rules for PDP Context coexistence (as described in 3GPP TS 23.060, sub-clause 15.4), would have been broken.
A.F Invalid length	The number of activation failures caused by detection of an invalid length. In a received GTP signaling message Request, if a mandatory TLV format information element has a Length different from that defined in the version that this message claims to use, then this information element is discarded, the error is logged, and a Response is sent with Cause set to "Mandatory IE incorrect". In a received GTP signaling message Response, if a mandatory TLV format information element has a Length different from that defined in the version that this message claims to use, then the requesting entity treats the GTP signaling procedure as having failed.
A.F Unexpected repeated IE	The number of activation failures that returned a Cause Value of "Unexpected Repeated IE".
A.F GRE key not found	The number of activation failures that returned a Cause Value of "GRE Key Not Found".
A.F Preferred PDN type not supported	The number of activation failures that returned a Cause Value of "Preferred PDN Type not Supported".
A.F P-TMSI Signature mismatch	The number of activation failures that returned a Cause Value of "P-TMSI Signature Mismatch". P-TMSI Signature is an information element in an Identification Request.It is provided by the MS in the Routing Area Update Request and Attach Request messages to the SGSN for identification checking purposes. "P-TMSI Signature mismatch" is returned if either: the P-TMSI Signature stored in the old SGSN does not match the value sent by the MS via the new SGSN; or the MS does not provide the P-TMSI Signature to the new SGSN while the old SGSN has stored the P-TMSI Signature for that MS.
A.F Unable to page UE due to Suspension	The number of activation failures that returned a Cause Value of "Unable to page UE due to Suspension".
A.F Conditional IE Missing	The number of activation failures that returned a Cause Value of "Conditional IE missing". This indicates that one or more conditional information elements are missing from a Request message.
A.F APN Restriction type incompatible with currently active PDN connection	The number of activation failures that returned a Cause Value of "APN Restriction type incompatibility with currently active PDP Contexts". This cause values indicates to an SGSN that a PDP Context was not allowed to be created or moved by the GGSN because if it had been, the rules for PDP Context coexistence (as described in 3GPP TS 23.060, sub-clause 15.4), would have been broken.
A.F PGW not responding	The number of activation failures that returned a Cause Value of "PGW Not Responding".
A.F Unsupported error cause received	The number of activation failures that returned a Cause Value of "Unsupported Error Cause Received".

Delete bearer failures

Statistic	Description
D.F Internal Error	The number of bearer deletion failures that the plug-in categorized as internal errors. (Refer to What Is the Internal Error Statistic? for more information.)
D.F Timeout	The number of HSS Initiated Subscribed QoS Modification procedures that failed as a result of a timeout while waiting for the peer to answer.
D.F Invalid Message Format	The number of Modify Bearer Failure Indications received with a Cause Value of "Invalid Message Format".
D.F IMSI Not known	The number of bearer deletion failures that returned a Cause Value of "IMSI Not Known".
D.F Mandatory IE incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Incorrect".
D.F Mandatory IE missing	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Missing".
D.F Optional IE incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Optional IE Incorrect".
D.F Invalid length	The number of bearer deletion failures caused by detection of an invalid length. In a received GTP signaling message Request, if a mandatory TLV format information element has a Length different from that defined in the version that this message claims to use, then this information element is discarded, the error is logged, and a Response is sent with Cause set to "Mandatory IE incorrect". In a received GTP signaling message Response, if a mandatory TLV format information element has a Length different from that defined in the version that this message claims to use, then the requesting entity treats the GTP signaling procedure as having failed.
D.F Unexpected repeated IE	The number of Modify Bearer Failure Indications received with a Cause Value of "Unexpected Repeated IE".
D.F P-TMSI Signature mismatch	The number of bearer deletion failures that returned a Cause Value of "P-TMSI Signature Mismatch". P-TMSI Signature is an information element in an Identification Request.It is provided by the MS in the Routing Area Update Request and Attach Request messages to the SGSN for identification checking purposes. "P-TMSI Signature mismatch" is returned if either: the P-TMSI Signature stored in the old SGSN does not match the value sent by the MS via the new SGSN; or the MS does not provide the P-TMSI Signature to the new SGSN while the old SGSN has stored the P-TMSI Signature for that MS.
D.F Reserved Message Value Received	The number of bearer deletion failures that returned a Cause Value of "Reserved Message Value Received".
D.F PGW not responding	The number of bearer deletion failures that returned a Cause Value of "PGW Not Responding".
D.F Context not found	The number of Modify Bearer Failure Indications received with a Cause Value of "Context not found". If a node receives a message for which it has no context, it responds with this Cause Value in its corresponding response message to the sender.
D.F Unsupported error cause received	The number of bearer deletion failures that returned a Cause Value of "Unsupported Error Cause Received".

Bearer update failures

Statistic	Description
U.F Internal Error	The number of bearer update failures that the plug-in categorized as internal errors. (Refer to What Is the Internal Error Statistic? for more information.)
U.F Timeout	The number of bearers that could not be updated as a result of a timeout while waiting for the SGW to answer.
U.F Request rejected	The number of bearer update requests that returned a Cause Value of "Request Rejected".
U.F P-TMSI Signature mismatch	The number of bearer update failures that returned a Cause Value of "P-TMSI Signature Mismatch". P-TMSI Signature is an information element in an Identification Request.It is provided by the MS in the Routing Area Update Request and Attach Request messages to the SGSN for identification checking purposes. "P-TMSI Signature mismatch" is returned if either: the P-TMSI Signature stored in the old SGSN does not match the value sent by the MS via the new SGSN; or the MS does not provide the P-TMSI Signature to the new SGSN while the old SGSN has stored the P-TMSI Signature for that MS.
U.F Reserved Message Value Received	The number of bearer update failures that returned a Cause Value of "Reserved Message Value Received".
U.F PGW not responding	The number of bearer update failures that returned a Cause Value of "PGW Not Responding".
U.F Collision with network initiated request	The number of bearer update failures that returned a Cause Value of "Collision with Network Initiated Request".
U.F Unsupported error cause received	The number of bearer update failures that returned a Cause Value of "Unsupported Error Cause Received".
U.F Context not found	The number of bearer update failures that returned a Cause Value of "Context not found". If a node receives a message for which it has no context, it responds with this Cause Value in its corresponding response message to the sender.
U.F No Memory Available	The number of bearer update failures that returned a Cause Value of "No Memory Is Available".
U.F Unexpected Repeated IE	The number of bearer update failures that returned a Cause Value of "Unexpected Repeated IE".

HSS update failures

Statistic	Description
MBCF Timeout	The number of HSS Initiated Subscribed QoS Modification procedures that failed as a result of a timeout while waiting for the peer to answer.
MBCF Context Not Found	The number of Modify Bearer Failure Indications received with a Cause Value of "Context not found". If a node receives a message for which it has no context, it responds with this Cause Value in its corresponding response message to the sender.
MBCF No Resources Available	The number of Modify Bearer Failure Indications received with a Cause Value of "No Resources Available".
MBCF No Memory Is Available	The number of Modify Bearer Failure Indications received with a Cause Value of "No Memory Available".
MBCF System Failure	The number of Modify Bearer Failure Indications received with a Cause Value of "System Failure".
MBCF Mandatory IE Incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Incorrect".
MBCF Mandatory IE Missing	The number of Modify Bearer Failure Indications received with a Cause Value of "Mandatory IE Missing".
MBCF Optional IE Incorrect	The number of Modify Bearer Failure Indications received with a Cause Value of "Optional IE Incorrect".
MBCF Invalid Message Format	The number of Modify Bearer Failure Indications received with a Cause Value of "Invalid Message Format".
MBCF Unexpected repeated IE	The number of Modify Bearer Failure Indications received with a Cause Value of "Unexpected Repeated IE".

Create session response time
Same as global statistics

Delete session response time
Same as global statistics

Modify session response time
Same as global statistics

Bearer resource command response time
Same as global statistics

Modify bearer command response time
Same as global statistics

Ordering Information

925-3157
IXLOAD, ADVNET-EGTPR8-S11S1MME, MME and eNodeB simulation on the S11 and S1-U interfaces, for EPC testing (SGW), 3GPP Release 8. REQUIRES previous purchase of 925-3001 (IXLOAD) or higher bundle

P/N: 915-1773-01 Rev B –August, 2010

This material is for informational purposes only and subject to change without notice. It describes Ixia's present plans to develop and make available to its customers certain products, features and capabilities. Ixia is only obligated to provide those deliverables specifically included in a written agreement between Ixia and the customer.

[ back | top of page | back to products ]

Social Media

Select language:

IxLoad: Evolved Packet Core (EPC) Network Testing