Failure Scenario
When
you select Test Activity as Command Mode or Sequencer, on the On Demand
Command window, you may define Failure Scenarios for procedures, example,
Connect and Attach operations. A Failure Scenario consists of a list of
messages, actions associated with each message (Delay, Skip, Ignore, Abort),
and optional data (delay time, # of messages to be ignored or action after
abort).
You may save defined
message types, actions, and frequency of Failure Scenarios as a Template
in libraries. Each Failure Scenarios Template (FST) type is particular
to the Test Case (TC), On Demand Command (ODC), and Operation.
| NOTE: FSTs of all types
are stored together in each library. When you select/open an FST
from a library, you will only see the FSTs that are valid for
your TC-ODC-Operation. When you Save an FST, all FSTs in
the library display. |
Define Failure Scenario
|
Click to
add a message to a failure scenario. The number of messages you
may add depends on the Test Case command operation and are displayed
for you selection when you click .
Click  to delete
the selected row.
| NOTE: You may
open a saved Failure Scenario Template and, also define
Failure Scenarios and then save them as a template. |
|
Message |
The message
you selected from the display list. Messages displayed depend
on the Test Case and the Command Operation.
| NOTE: Each
message type is available for selection only once. After
you add a message type, it is removed from the display
pick-list. |
|
Action |
Type of
action performed for the message type. |
Value |
The interval/frequency
of the action. Double-click and enter a required value.
| NOTE: Value
is not available for all actions. |
|
Failure Scenario Arguments
Syntax |
failure_msg_[n
1-based]=[Message Name] / [Action] </ [Optional data]></[Optional
data 2]> |
Action |
The table
below lists the actions and the arguments.
Action |
Syntax |
Delay |
[Message Name] / Delay/ [Delay Value in seconds] |
Skip (for tx messages) |
[Message] / Skip |
Ignore (for rx messages) |
[Message] / Ignore / [# of messages to be ignored] |
Abort No Reattach |
[Message] /Abort / NoReattach |
Abort Reattach |
[Message ]/Abort / Reattach |
Abort Reattach GUTI |
[Message] /Abort / ReattachGuti / [0xGUTI] |
|
^ Back to Top
MME Nodal
The following lists Failure Scenario arguments for MME-ControlBearer-Attach
and MME-ControlBearer-PdnConnect command operations.
ControlBearer
{"op=PdnConnect"} Example
ControlBearer { op=PdnConnect
rate=1000.0 start_sub=1 end_sub=2 def=1
failure_msg_1=NasPdnCon/Delay/50 failure_msg_2=S1apERabSetupRsp/Ignore
failure_msg_3=NasActDefAcc/Abort/ReattachGuti/0x11223344556677889900
} |
| Valid
"op=PdnConnect" Messages |
Command
Arguments |
S1-AP E_RAB Setup Response
(Tx) NAS PDN Connectivity Request
(Tx) NAS Activate Default EPS
Bearer Context Request (Rx) NAS Activate Default EPS
Bearer Context Accept (Tx) |
S1apERabSetupRsp NasPdnCon NasActDefReq
|
ControlBearer
["op=Attach"] Example:
ControlBearer { op=Attach
rate=1000.0 start_sub=1 end_sub=2 failure_msg_1=NasAttachReq/Skip
failure_msg_2=NasAuthReq/Abort/NoReattach } |
| Valid
"op=Attach" Messages |
Command
Arguments |
- NAS Attach Request (Tx)
- NAS Authentication Request (Rx)
- NAS Security Mode Command (Rx)
- NAS Authentication Response (Tx)
- NAS Security Mode Complete (Tx)
- NAS ESM Information Request (Rx)
- NAS ESM Information Response (Tx)
- NAS Identity Request (Rx)
- NAS Identity Response (Tx)
- NAS Attach Accept (Rx)
- S1-AP Initial Context Setup Response (Tx)
- NAS Attach Complete (Tx)
|
- NasAttachReq
- NasAuthReq
- NasSecMode
- NasAuthRsp
- NasSecComp
- NasInfoReq
- NasInfoRsp
- NasIdReq
- NasIdRsp
- NasAttachAcc
- S1apInitConSetupRsp
- NasAttachComp
|
^ Back to Top