M2UA_TS: Valid8.com/ACATS M2UA Conformance Test Suite V.1.6, for use with SIGTRAN M2UA Signaling Tester
TEST SUITE OVERVIEW
References ETSI TS 102 380 v1.1.1 (2004-12) / IETF M2UA RFC3331
Archive/Project voip/m2ua_ts
Version 19171599
Date 02 Dec 2008
Number of Scenarios 127
Number of Groups 11
Average per Group 11
GROUP/SCENARIO TEST PURPOSE
M2UA_SGP
M2UA_SGP_Start Activate SCTP as pre-condition for other tests for SUT = SGP
SUT: SGP
M2UA_SGP/
SG_ASPM
M2UA_SGP_ASPM_V_01 To validate that the ASP Up message received with mandatory and option parameters from peer moves the state of the ASP and AS to Inactive at the IUT
Ensure that the IUT responds with the ASP Up Ack and Notify (AS-Inactive) message indicating the AS state has been changed to inactive.
Config: Single ASP is Configured in an AS.
Status: Mandatory
SUT: SGP
M2UA_SGP_ASPM_V_02 To ensure that, upon reception of the ASP Up message from peer, IUT responds with ASP Up Ack and 2 Notify (AS-Inactive) messages corresponding to each AS
Status: Mandatory
Config: Same ASP is Configured in two different AS.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in Down State.
Ref: Section 4.3.4.1, 4.3.1, 4.3.2 and 4.3.4.5 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_03 Validate that when IUT receives an ASP Up message from peer for ASP1, it responds with ASP Up Ack and a Notify (AS-Inactive) message, indicating the AS state
has moved to inactive.Now invoke the ASP Up message from peer for ASP2 and validate that the IUT responds with ASP Up Ack message only.
Status: Mandatory
Config: Two ASPs (ASP1 and ASP2) are Configured in a single AS.
Pre-Condition: SCTP associations are established between IUT and both ASPs.
Both ASPs are in down state.
Ref: Section 4.3.4.1, 4.3.1, 4.3.2 and 4.3.4.5 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_04 To validate the ASP Active message having all parameters and one configured IID (using tag of 0x1),
moves the state of the ASP to active.
Ensure that the IUT responds with the ASP Active Ack and a Notify (AS-Active) message to indicate that
the AS state has moved to the active.
If the ASP was pre-configured to serve more than one IID, the ASP Active Ack message should contain all
pre-configured IID s and not only the one contained in the ASP Active message.
Status: Mandatory
Config: One ASP is configured in an AS.
If necessary the AS and ASP have to be pre-configured at the IUT.
Pre-Condition: SCTP association is established between ASP and IUT.
AS is in inactive state.
Ref: Section 3.3.2.7, 3.3.3.2, 4.3.2, 4.3.4.3 and 4.3.4.5 of RFC 3331
SUT
M2UA_SGP_ASPM_V_05 To validate the ASP Active message having all parameters and multiple Configured IID (using tag of 0x1), moves the state of the ASP to active
Ensure that the IUT responds with the ASP Active Ack and a Notify (AS-Active) message to indicate the AS state has moved to the active.
Status: Mandatory
Config: One ASP is configured in an AS.
If necessary the AS and ASP have to be pre-configured at the IUT
Pre-Condition: SCTP Association is established between peer and IUT.ASP is in Inactive State.
Ref: Section 3.3.2.7 and 4.3.4.3 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_V_06 Ensure that an on reception of an ASP Active message with integer range parameters with Configured start and stop values (tag of 0x8) from peer,
IUT responds with the ASP Active Ack and a Notify (AS-Active) message having the value of (AS_active) in status type field.
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for an Integer based identifier range
Pre-Condition: SCTP Association is established between peer and IUT.ASP is in Inactive State.
Ref: Section 3.3.2.7 and 4.3.4.3 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_V_07 Ensure that upon reception of an ASP Inactive message, IUT responds with ASP Inactive Ack message
and one or more Notify messages depending whether the IUT has T(r) implemented or not.
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for an Integer based identifier range
Pre-Condition: SCTP association is established between ASP and IUT. ASP is in active state.
Ref: Section 3.3.2.7 and 4.3.4.3 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_V_08 Ensure that the IUT responds with one or two ASP Active Ack and one or two Notify (AS Active)
messages, indicating the AS state transaction to active in both AS, upon receiving an ASP Active message
with only the mandatory parameters.
Status: Optional
Config: Single ASP is configured in two different AS. If necessary the ASs and ASP have to be pre-configured at the IUT
Pre-Condition: SCTP association is established between ASP and IUT.
ASP is in inactive state in both AS1 and AS2
Ref: Section 3.3.2.9, 4.3.2 and 4.3.4.4 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_09 Ensure that the IUT responds with an ASP Active Ack and Notify (AS Active) messages indicating the AS1
state transaction to active, when it receives an ASP Active message with IID values as that of AS1.
Also, validate that on receiving an ASP Active message with IID as configured for AS2, IUT responds with
the ASP Active Ack and Notify (AS-Active) message
Status: Optional
Config: Single ASP is configured in two different AS. If necessary the ASs and ASP have to be pre-configured at the IUT.
Pre-Condition: SCTP association is established between ASP and IUT. ASP is in inactive state in both AS1 and AS2..
Ref: Section 3.3.2.8 and 4.3.4.3 of RFC 3331
SUT
M2UA_SGP_ASPM_V_10 Ensure that the IUT responds with one or two ASP Inactive Ack and two Notify (AS Pending) messages
indicating the AS state transaction to inactive in both AS, when it receives an ASP Inactive message. The
IUT might send another Notify (AS-Inactive) message depending whether the IUT has T(r) implemented or not.
Status: Optional
Config: Single ASP is configured in two different AS.
If necessary the ASs and ASP have to be pre-configured at the IUT
Pre-Condition: SCTP association is established between ASP and IUT. ASP is in active state in both AS.
Ref: Section 3.3.2.10 and 4.3.4.4 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_11 Ensure that the IUT responds with an ASP Inactive Ack and a Notify (AS Pending) message indicating the
AS1 state transaction to inactive, when it receives an ASP Inactive message with IID values as configured
for AS1.
Also, validate that on receiving an ASP Inactive message with IID as configured for AS2, IUT responds
with the ASP Inactive Ack and Notify (AS-Pending) message. The IUT might send another Notify
(AS-Inactive) message depending whether the IUT has T(r) implemented or not.
Status: Optional
Config: Single ASP is Configured in two different AS. AS1 and AS2 are Configured for Integer based IIDs.
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in active State in both AS1 and AS2.
Ref: Section 3.3.2.10 and 4.3.4.4 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_12 To ensure that the IUT upon reception of an ASP Active message having at least as one of the optional
parameters a range of configured IIDs (using tag 0x8), responds with an ASP Active Ack message and a
Notify (AS-Active) message to indicate the AS state has moved to active state.
Status: Optional
Config: Two ASPs are configured in the same AS.
If necessary the AS and ASPs have to be pre-configured at the IUT. AS is configured in Load-share mode.
Pre-Condition: SCTP associations are established between the IUT and both ASPs.
ASP1 and ASP2 are in inactive state in AS
Ref: Section 3.3.2.7 and 4.3.4.3 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_13 To validate the ASP Active message having Configured IID from peer for ASP2, moves the state of the AS2 to active at IUT
Ensure that the IUT responds with the ASP Active Ack and a Notify (Alternate ASP Active) to ASP1 indicating that alternate resource has become active.
Status: Optional
Config: Two ASPs are configured in the same AS.
If necessary the AS and ASPs have to be pre-configured at the IUT. AS is configured in Override mode.
Pre-Condition: SCTP associations are established between the IUT and both ASPs.
ASP1 is in active state and ASP2 is in inactive state in the AS.E and ASP2 are in Inactive State in an AS.
Ref: Section 3.3.2.7 and 4.3.4.3 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_14 Validate that the SGP sends Notify (Insufficient ASP resources active in AS) message to the ASP1 (peer) indicating that the
number of ASPs required to handle traffic is not sufficient, when it receives an ASP Inactive message from peer for ASP2.
Ensure that the IUT responds with an ASP Inactive Ack message.
Status: Optional
Config: Two ASPs are Configured in an AS. AS is Configured for Integer based IIDs. AS is Configured in load sharing mode and minimum two ASPs are required to handle traffic.
Pre-Condition: SCTP Association is established between the two ASPs and SGP. Both of the ASPs are in active state.
Ref: Section 3.3.3.2, 4.3.4.3 and 4.3.4.5 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_ASPM_V_15 Validate that the IUT responds with a Heartbeat Ack message, when it receives a Heartbeat message
Ensure that Heartbeat Ack is sent by the IUT with same heartbeat data provided in the Heartbeat message.
SUT: SGP
M2UA_SGP_ASPM_IO_01 Ensure that the IUT responds with an ASP Up Ack message, when it receives an ASP Up message, even
though the ASP state is ASP-Inactive.
If necessary the AS and ASP have to be pre-configured at the IUT.
ASP is in inactive state.
Ref: Section 4.3.4.1 of RFC 3331
M2UA_SGP_ASPM_IO_02 Ensure that the IUT on receipt of a Data message discards the message
An IUT according to ETSI TS 102 141 [1]might respond with an Error message.
If necessary the AS and ASP have to be pre-configured at the IUT.
ASP is in inactive state.
SUT: SGP
M2UA_SGP_ASPM_IO_03 Ensure that the IUT responds with an ASP Active Acknowledge message, when it receives an ASP Active message from the peer,
even though the ASP state is ASP active.
Config: One ASP is Configured in an AS. If necessary the AS and ASP have to be pre-configured at the IUT.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state.
Ref: Section 4.3.4.3 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IO_04 Ensure that the IUT responds with an ASP Up Ack message and an Error message with error code as
"Unexpected Messsage", when it receives the ASP Up message in ASP active state.
Config: One ASP is configured in an AS.
If necessary the AS and ASP have to be pre-configured at the IUT.
Pre-Condition: SCTP association is established between ASP and IUT. ASP is in active state.
Ref: Section 4.3.4.1 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_01 Ensure that the IUT responds with an Error message indicating "invalid version", when it receives an ASP
Up message with a value other than "1" in the version field of the common message header.
Config: One ASP is Configured in an AS. If necessary the AS and ASP have to be pre-configured at the IUT.
Pre-Condition: SCTP association is established between ASP and IUT.
ASP is in down state.
Ref: Section 3.3.3.1 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_02 Ensure that the IUT responds with an Error message with error code as "Unsupported Message Class" to peer, when it receives a message having
unincluded message class value (message classed not marked for M2UA).
Config: One ASP is Configured in an AS.
Pre-Condition: SCTP association is established between ASP and IUT.
ASP is in active state.
Ref: Section 3.1.3 and 3.3.3.1 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_03 Ensure that the IUT responds with an Error message with error code as "Unsupported Message Type" to peer, when it receives a message having
message type value as reserved (reserved values are 0 and 16 through to 255).
Config: One ASP is Configured in an AS.
Pre-Condition: SCTP association is established between ASP and IUT.
ASP is in active state.
Ref: Section 3.1.4 and 8.2.2 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_04 Ensure that the IUT responds with an Error message with error code as "Unsupported Traffic Handling
Mode", when it receives an ASP Active message having traffic handling mode as Override.
Config: Two ASPs are configured in the same AS.
If necessary the AS and ASPs have to be pre-configured at the IUT.
AS is configured in Load-share mode.
Pre-Condition: SCTP Association is established between ASP and IUT.ASP is in inactive state.
Ref: Section 3.3.2.7 and 3.3.3.1 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_05 Ensure that the IUT responds with an Error message with error code as "Invalid Stream Identifier", when it
receives an ASP Active message on a stream other than 0.
Config: One ASP is Configured in an AS. If necessary the AS and ASP have to be pre-configured at the IUT.
Pre-Condition: SCTP Association is established between ASP and IUT. ASP is in inactive state.
Ref: Section 3.3.3.1 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_06 Ensure that the IUT responds with an Error message with error code as "Invalid Interface Identifier" to peer for each IID,
when it receives an ASP Active message having non-Configured IIDs.To verify that the SG sends an Error message Invalid interface identifier
if the ASP sends a message with an non-Configured interface identifier value.
Config: One ASP is Configured in an AS.AS is Configured for Integer based IIDs.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state.
Ref: Section 3.3.2.7 and 3.3.3.1 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_07 Ensure that the IUT responds with an Error message with reason "ASP Identifer Required", when it
receives an ASP Up message without an ASP Identifier parameter..
Config: One ASP is configured in an AS.
If necessary the AS and ASP have to be pre-configured at the IUT.
The IUT requires the use of the optional ASP Identifier..
Pre-Condition: SCTP association is established between ASP and IUT.
ASP is in down state.
Ref: Section 3.3.2.7 and 3.3.3.1 of RFC 3331
SUT: SGP
M2UA_SGP_ASPM_IV_08 Ensure that the IUT responds with an Error message with reason "Invalid ASP Identifer", when it receives
an ASP Up message with a non-unique ASP Identifier.
Config: One ASP is configured in an AS.
If necessary the AS and ASP have to be pre-configured at the IUT.
The IUT requires the use of the optional ASP Identifier..
Pre-Condition: SCTP association is established between ASP and IUT.
ASP is in down state.
Ref: Section 3.3.2.7 and 3.3.3.1 of RFC 3331
SUT: SGP
M2UA_SGP/
SG_IIM
M2UA_SGP_IIM_V_01 Ensure that the IUT responds with Registration Response message having status field value as
"Successfully Registered", when it receives a Registration Request message from the peer with Link key parameters
defined with Local-LK-Identifier, Signalling Data Terminal Identifier and Signalling Data Link Identifier values.
ASP is in inactive state.
SUT: SGP
M2UA_SGP_IIM_V_02 Ensure that IUT sends a Deregistration Response to the peer with status field as Successfully De-registered,
on receiving a Deregistration Request message with the Configured IID values from peer.
ASP is in inactive state.
SUT: SGP
M2UA_SGP_IIM_V_03 Ensure that on reception of an Registration Request message from ASP2 to IUT with Link key having parameters as that of Configured AS, respond with the Registration Response message
Status: Mandatory
Config: ASP1 is Configured in an AS ASP2 is not yet Configured in any AS.
Pre-Condition: SCTP Association is established between the two ASPs and SGP.ASP1 is in active state and ASP2 is in inactive state.
Ref: Section 3.3.4.1, 3.3.4.2 and 4.4.1 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_IIM_V_04 Ensure that upon reception of a Deregistration Request Message from ASP1 with Configured IID,
IUT respond with the Deregistration Response message with status field as "De-registration Successful".
Status: Mandatory
Config: ASP1 and ASP2 are Configured in an AS.
Pre-Condition: SCTP Association is established between the two ASPs and SGP.ASP1 and ASP2 are in inactive state.
Ref: Section 3.3.4.1, 3.3.4.2 and 4.4.1 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_IIM_V_05 Ensure that upon reception of a Deregistration Request Message from ASP1 with Configured IID,
IUT respond with the Deregistration Response message with status field as De-registration Successful. Also,
valdiate that the IUT responds with the Deregistration Response message having status field as De-registration Successful
and deletes the AS, even when it receives a Deregistration Request message from ASP2 with Configured IID.
Status: Mandatory
Config: ASP1 and ASP2 are Configured in the same AS.
Pre-Condition: SCTP Association is established between the two ASPs and SGP. All ASPs are in Inactive state.
Ref: Section 3.3.4.1, 3.3.4.2 and 4.4.1 of RFC 3331
PCO1_Src_IP_Addr PCO2_Src_IP_Addr
PCO1_Dst_IP_Addr PCO2_Dst_IP_Addr
PCO1_Src_Port PCO2_Src_Port
PCO1_Dst_Port PCO2_Dst_Port
SUT: SGP
M2UA_SGP_IIM_IO_01 Ensure that the IUT responds with an Error message with error code as "ASP Currently Active for Interface Identifier",
when it receives a Deregistration Request for an ASP in active state.
ASP is in Active state.
SUT: SGP
M2UA_SGP/
SG_MAUP
M2UA_SGP_MAUP_V_01 Ensure that IUT sends an Establish Confirm message, when it receives an
Establish Request message from peer with configured IIDs.
Note: IUT needs to establish or have already established an SS7 link.
Config: Single ASP is configured in an AS.
Reference: Section 3.3.1.3 of RFC 3331
Status: Mandatory
SUT: SGP SGP
M2UA_SGP_MAUP_V_01_Keep_Link_Up_001 Ensure that IUT sends an Establish Confirm message, when it receives an
Establish Request message from peer with configured IIDs. Handles Rx SLTM, Tx SLTA
Note: IUT needs to establish or have already established an SS7 link.
Config: Single ASP is configured in an AS.
Reference: Section 3.3.1.3 of RFC 3331
Status: Mandatory
SUT: SGP SGP
M2UA_SGP_MAUP_V_01_Keep_Link_Up_002 Ensure that IUT sends an Establish Confirm message, when it receives an
Establish Request message from peer with configured IIDs. Handles Rx SLTM DATA, Tx SLTA using PDU_SLTA
Note: IUT needs to establish or have already established an SS7 link.
Config: Single ASP is configured in an AS.
Reference: Section 3.3.1.3 of RFC 3331
Status: Mandatory
SUT: SGP SGP
M2UA_SGP_MAUP_V_02 Ensure that IUT is able to send a Data message to the peer
Note: IUT needs to receive an MTP2 PDU on the SS7 link to trigger this behaviour.
Config: Single ASP is Configured in any AS.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state and SS7
link is established.
SUT: SGP
M2UA_SGP_MAUP_V_03 Ensure that the IUT responds with a Data Acknowledge message , when it
receives a Data message with correlation ID. Validate that the Data Acknowledge
message has the same correlation id.
Config: Single ASP is configured in an AS.
Reference: Section 3.3.3.1 and 3.3.1.2 of RFC 3331
Status: Mandatory
SUT: SGP
M2UA_SGP_MAUP_V_04 Ensure that IUT sends a ReleaseConfirm message, when it receives a Release Request message
from peer with Configured IIDs.
ASP is in active state and SS7 link is in established state.
SUT: SGP
M2UA_SGP_MAUP_V_05 Ensure that IUT is able to send a Release Indication message to the peer
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_06 Ensure that the IUT sends a State Confirm message with state as STATUS_FLUSH_BUFFERS, ,
when it receives a State Request from the ASP, with the state as "STATUS_FLUSH_BUFFERS".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_07 Ensure that the IUT sends a State Confirm"message with state as "STATUS_CONTINUE", when it receives
a State Request from the ASP, with the state as "STATUS_CONTINUE".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_08 Ensure that the IUT sends a State Confirm message with state as "STATUS_CLEAR_RTB", when it
receives a State Request from the ASP, with the state as "STATUS_CLEAR_RTB".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_09 Ensure that the IUT sends a State Confirm message with state as "STATUS_AUDIT", when it receives
a State Request from the ASP, with the state as "STATUS_AUDIT".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_10 Ensure that the IUT sends a State Confirm message with state as "STATUS_CONG_CLEAR",
when it receives a State Request from the ASP, with the state as "STATUS_CONG_CLEAR".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_11 Ensure that the IUT sends a State Confirm message with state as "STATUS_CONG_ACCEPT",
when it receives a State Request from the ASP, with the state as "STATUS_CONG_ACCEPT".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_12 Ensure that the IUT sends a State Confirm message with state as "STATUS_CONG_DISCARD",
when it receives a State Request from the ASP, with the state as "STATUS_CONG_DISCARD".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_13 Ensure that the IUT is able to send a State Indication message with event as "EVENT_RPO_ENTER"
Note: IUT needs to experience a remote entered processor outage condition to trigger this behaviour.
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_14 Ensure that the IUT is able to send a State Indication message with event as "EVENT_LPO_ENTER"
SUT: SGP
M2UA_SGP_MAUP_V_15 Ensure that the IUT is able to send a Congestion Indication message to the peer with
congestion status as "LEVEL_3".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_16 Ensure that the IUT is able to send a Congestion Indication message to the peer with
congestion status as "LEVEL_NONE".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_17 Ensure that the IUT sends a Retrieval Confirm message to the peer with action
as "ACTION_RTRV_BSN", when it receives a Retrieval Request from the ASP, with
the action as "ACTION_RTRV_BSN".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_18 Ensure that the IUT sends a Retrieval Confirm message to the peer with action as
"ACTION_RTRV_MSGS", when it receives a Retrieval Request from the ASP, with the
action as "ACTION_RTRV_MSGS".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_19 Ensure that the IUT is able to send a Retrieval Indication message to the peer
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_20 Ensure that the IUT is able to send a Data message with proper padding to the peer
a multiple of 4) on the SS7link to trigger this behaviour.
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_V_21_X Ensure that the IUT sends a State Confirm message with state as "STATUS_LPO_SET",
when it receives a State Request from the ASP, with the state as "STATUS_LPO_SET".
ASP is in active state and SS7 link is established.
SUT: SGP
M2UA_SGP_MAUP_IV_01 Ensure that the IUT provides an Error message with error code as "Invalid Stream Identifier" ,
when it receives a Data message from peer on stream 0.
ASP is in active state.
SUT: SGP
M2UA_SGP_MAUP_IV_02 Ensure that the IUT sends an Error message with error code as "Invalid Interface Identifier",
when it receives an State Request from the ASP for not configured IID.
SUT SGP
M2UA_ASP
M2UA_ASP_Start_SCTP_Association Activate SCTP as pre-condition for other tests for SUT = ASP
SUT: ASP
M2UA_ASP_Start_IUT_ACTIVE Activate SCTP as pre-condition and wait for IUT to get into the ACTIVE state
(i.e. wait for ASP UP and ASP Active) for other tests for SUT = ASP
SUT: ASP
M2UA_ASP/
ASP_ASPM
M2UA_ASP_ASPM_V_01 Ensure that the IUT, to enter the ASP-INACTIVE state, sends an ASP Up message to peer and moves to inactive state on
receiving an ASP Up Ack message from peer.Note: The ASP Up message is triggered by the LM by sending an M-ASP_UP request
primitive without info string or by an M2UA management function.
SUT: ASP
M2UA_ASP_ASPM_V_02 Ensure that the IUT, to enter the ASP-ACTIVE state, sends an ASP Active message to peer and moves to active state on
receiving an ASP Active Ack message from peer. Note The ASP Active message is triggered by the LM by sending M-ASP_Active
request primitive without info string or by an M2UA management function.
SUT: ASP
M2UA_ASP_ASPM_V_03 Ensure that the IUT, to enter the ASP-INACTIVE state, sends an ASP Inactive message to peer and moves to
inactive state on receiving an ASP Inactive Ack message from peer.Note The ASP Inactive message is triggered
by the LM by sending M-ASP_Inactive request primitive without info string or by an M2UA management function.
SUT: ASP
M2UA_ASP_ASPM_V_04 Ensure that IUT, to enter the ASP-ACTIVE state for both AS, sends either one ASP Active message to
peer with Configured IIDs for both AS or one ASP Active message for each AS. Validate that the state
of the ASP moves to active in both AS, when ASP Active Ack message is received from peer with all parameters.
ASP is in inactive state.
SUT: ASP
M2UA_ASP_ASPM_V_05 Ensure that the IUT, to enter the ASP-ACTIVE state for AS1, sends an ASP Active message to peer with Configured IID
as that of AS1.Ensure that the state of the ASP moves to active for AS1 only, when it receives an ASP Active Ack message
from peer with IID as that of AS1.Note The ASP Active message is triggered by the LM by sending M-ASP_Active request primitive
for AS1 or by an M2UA management function.
Status: Mandatory
Config: ASP is Configured in two different AS.Both AS are Configured for Integer based IIDs and in load sharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in inactive state.
Ref: Section 3.3.2.7, 3.3.2.8, 4.3.2 and 4.3.4.3 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_V_06 Ensure that IUT, to enter the ASP-INACTIVE state for both AS, sends an ASP Inactive message to peer with Configured IIDs for both AS
Validate that the state of the ASP moves to inactive in both AS, when ASP Inactive Ack message is received from peer with all parameters.
Note The ASP Inactive message is triggered by the LM by sending M-ASP_Inactive request primitive for both AS or by an M2UA management function.
Status: Mandatory
Config: ASP is Configured in two different AS.Both AS are Configured for Integer based IIDs and in load sharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state.
Ref: Section 3.3.2.9, 3.3.2.10 and 4.3.4.4 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_V_07 Ensure that the IUT on receiving the SCTP-RESTART_INDICATION (caused by the peer performing a restart operation) from SCTP,
moves the state of the ASP to down.
Status: Mandatory
Config: Single ASP is Configured in an AS. If necessary the ASP has to be pre-configured at the IUT.
Pre-Condition: SCTP Association is established between ASP and SGP.
Ref: Section 4.3.3 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_V_08 Validate that the IUT responds with a Heartbeat Ack message , when it receives a Heartbeat message from the peer
Ensure that Heartbeat Ack is sent by the IUT with same heartbeat data provided in the Heartbeat message.
Status: Mandatory
Config: One ASP is Configured in an AS. AS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in active state and minimum one ASPs is required to handle traffic.
Ref: Section 3.3.2.5, 3.3.2.6 and 4.3.4.6 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_V_09 Ensure that the ASP Up message is retransmitted by the IUT on expiry of timer T(ack), when it receives no ASP Up Ack from peer
Status: Mandatory
Config: One ASP is Configured in an AS. AS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in down state and minimum one ASPs is required to handle traffic.
Ref: Section 4.3.4.1 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_V_10 Ensure that the ASP Down message is retransmitted by the IUT on expiry of timer T(ack), when it receives no ASP Down Ack from peer
Status: Mandatory
Config: One ASP is Configured in an AS.AS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in inactive state and minimum one ASPs is required to handle traffic.
Ref: Section 4.3.4.2 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_V_11 Ensure that the ASP Active message is retransmitted by the IUT on expiry of timer T(ack), when it receives no ASPActive Ack from the peer
Status: Mandatory
Config: One ASP is Configured in an AS.AS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in inactive state and minimum one ASPs is required to handle traffic.
Ref: Section 4.3.4.3 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_V_12 Ensure that the ASP Inactive message is retransmitted by the IUT on expiry of timer T(ack), when it receives no ASP Inactive Ack from the peer
Status: Mandatory
Config: One ASP is Configured in an AS. AS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in active state.
Ref: Section 4.3.4.3 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_IO_01 Ensure that the IUT accepts the ASP Inactive Ack message received from the peer in response to an ASP Active message transmitted
by the IUT to enter the ASP-ACTIVE state and remains the ASP state in Inactive.
Status: Mandatory
Config: One ASP is Configured in an AS.AS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in inactive state and minimum one ASPs is required to handle traffic.
Ref: Section 4.3.4.4 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_IO_02 Ensure that the IUT accepts the ASP Inactive Ack message received from the peer and enters the ASP state to Inactive
Status: Mandatory
Config: One ASP is Configured in an AS.
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in active state.
Ref: Section 4.3.4.4 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_IO_03 Validate that the IUT moves the ASP state to down , when it receives an ASP Down Ack message without having sent an ASP down message
Status: Optional
Config: One ASP is Configured in an AS.AS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in inactive state.
Ref: Section 4.3.4.2 of RFC 3331
SUT: ASP
M2UA_ASP_ASPM_IO_04 Validate that the IUT moves the ASP state to down , when it receives an ASP Down Ack message from peer
Status: Optional
Config: One ASP is Configured in an AS.
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in active state.
Ref: Section 4.3.4.2 of RFC 3331
SUT: ASP
M2UA_ASP/
ASP_IIM
M2UA_ASP_IIM_V_01 Ensure that the IUT, to register itself with the SGP for an AS, sends a Registration Request message to the peer with link key
as defined in AS Configuration and accepts the receipt of the Registration Response message with registration result as "Successfully Registered".
Note The Registration Request message is triggered by the LM by sending M-LINK_KEY_REG request primitive.
Status: Mandatory
Config: One ASP is Configured in the stack but not yet associated with the ASAS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between peer and IUT .ASP is in Inactive State.
Ref: Section 3.3.4.1, 3.3.4.2 and 4.4.1 of RFC 3331
SUT: ASP
M2UA_ASP_IIM_V_02 Ensure that the IUT, to register itself with the SGP for two AS sends one or two Registration Request messages to the peer
with two different link key as defined in AS Config:urations and accepts one Registration Response message for both registrations
with registration result as "Successfully Registered".
Note The Registration Request message(s) is(are) triggered by the LM by sending M-LINK_KEY_REG request primitives.
Status: Mandatory
Config: One ASP is Configured in the stack but not yet associated with the ASTwo AS are Configured for Integer based IIDs and both are in loadsharing mode.
Pre-Condition: SCTP Association is established between peer and IUT. ASP is in Inactive State.
Ref: Section 3.3.4.1, 3.3.4.2 and 4.4.1 of RFC 3331
SUT: ASP
M2UA_ASP_IIM_V_03 Ensure that the IUT, to register itself with the SGP for two AS sends one pr two Registration Request messages to the
peer with two different link key as defined in AS Config:urations and accepts one Registration Response message per registration
each with registration result as "Successfully Registered".Note The Registration Request message(s) is(are) triggered by the LM
by sending M-LINK_KEY_REG request primitives.
Status: Mandatory
Config: One ASP is Configured in the stack but not yet associated with the ASTwo AS are Configured for Integer based IIDs and both are in loadsharing mode.
Pre-Condition: SCTP Association is established between peer and IUT. ASP is in Inactive State.
Ref: Section 3.3.4.1, 3.3.4.2 and 4.4.1 of RFC 3331
SUT: ASP
M2UA_ASP_IIM_V_04 Ensure that the IUT, to de-register itself with the SGP for an AS, sends a Deregistration Request message to the peer
with Configured IIDsuccessful and accepts the Deregistration Response message with deregistration result as "Successfully De-registered".
Note The Deregistration Request message is triggered by the LM by sending M-LINK_KEY_DEREG request primitive.
Status: Mandatory
Config: One ASP is Configured in an ASAS is Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between peer and IUT. ASP1 is in AS1. AS1 is in Inactive state.
Ref: Section 3.3.4.3, 3.3.4.4 and 4.4.2 of RFC 3331
SUT: ASP
M2UA_ASP_IIM_V_05 Ensure that the IUT, to de-register itself with the SGP for both AS, sends one or two Deregistration Request message to the
peer with Configured IID and accepts one Deregistration Response messages per deregistration each with deregistration result as "Successfully De-registered".
Note The Deregistration Request message(s) is(are) triggered by the LM by sending M-LINK_KEY_DEREG request primitives.
Status: Mandatory
Config: One ASP is Configured in an ASTwo AS are Configured for Integer based IIDs and in loadsharing mode.
Pre-Condition: SCTP Association is established between peer and IUT. ASP1 is in Inactive state in both AS.
Ref: Section 3.3.4.3, 3.3.4.4 and 4.4.2 of RFC 3331
SUT: ASP
M2UA_ASP/
ASP_MAUP
M2UA_ASP_MAUP_V_01 Ensure that IUT, to establish an SS7 link, sends an Establish Request message to the peer and accepts an Establish Confirm
message in response.
AS is Configured for Integer based IIDs and in loadsharing mode
ASP is in active state.
SUT: ASP
M2UA_ASP_MAUP_V_01_Keep_Link_Up_001 Ensure that IUT, to establish an SS7 link, sends an Establish Request message to the peer and accepts an Establish Confirm
message in response. Handles Rx SLTM, Tx SLTA
Note: IUT needs to establish or have already established an SS7 link.
Config: Single ASP is Configured in an AS.
AS is Configured for Integer based IIDs and in loadsharing mode
Reference: Section 3.3.1.3 of RFC 3331
Status: Mandatory
SUT: SGP SGP
M2UA_ASP_MAUP_V_01_Keep_Link_Up_002 Ensure that IUT, to establish an SS7 link, sends an Establish Request message to the peer and
accepts an Establish Confirm message in response. Handles Rx SLTM DATA, Tx SLTA using PDU_SLTA
Note: IUT needs to establish or have already established an SS7 link.
Config: Single ASP is configured in an AS.
Reference: Section 3.3.1.3 of RFC 3331
Status: Mandatory
SUT: SGP SGP
M2UA_ASP_MAUP_V_01_Keep_Link_Up_003 Ensure that IUT sends an DATA message with PDU SLTM and receives a DATA message with PDU SLTA
Handles Tx SLTM DATA, RX SLTA using PDU_SLTA
Status: Mandatory
Config: Single ASP is Configured in an AS.
AS is Configured for Integer based IIDs and in loadsharing mode
Pre-Condition: SCTP Association is established between ASP and SGP. ASP is in active state.
Ref: Section 3.3.1.3 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_02 Ensure that IUT is able to send a Data message
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
SUT: ASP
M2UA_ASP_MAUP_V_03 To verify that a Data Acknowledge message is send in response to a Data message including the
Correlation Id parameter. Validate that the Data Acknowledge message has the same correlation ID.
Status: Mandatory
Config: One ASP is configured in an AS.
Pre-Condition: SCTP association is established between IUT and SGP.
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
Ref: Section 3.3.1.1 and 3.3.1.2 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_04 Ensure that IUT, to release an SS7 link, sends a Release Request message and accepts a Release
Confirm message in response.
Status: Mandatory
Config: One ASP is configured in an AS.
Pre-Condition: SCTP association is established between IUT and SGP.
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
Ref: Section 3.3.1.1 and 3.3.1.2 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_05 Ensure that the IUT accepts State Indication messages and does not respond
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for Integer based IIDs and in loadsharing mode
Pre-Condition: SCTP association is established between IUT and SGP.
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
Ref: Section 3.3.1.4 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_06 Ensure that the IUT accepts Congestion indication messages with event as "LEVEL_3" and does not
respond.
Status: Mandatory
Config: Single ASP is Configured in any AS.AS is Configured for Integer based IIDs and in loadsharing mode
Pre-Condition: SCTP association is established between IUT and SGP.
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
Ref: Section 3.3.1.7 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_07 Ensure that the IUT, to retrieve the BSN, sends a Retrieval Request message to the peer,
with action as "ACTION_RTRV_BSN" and accepts a Retrieval Confirm message with result as "RESULT_SUCCESS" in response.
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for Integer based IIDs.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state and SS7 link is established.
Ref: Section 3.3.1.9 and 3.3.1.10 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_08 Ensure that the IUT, to retrieve PDUs from the queues, sends a Retrieval Request message to the peer,
with action as "ACTION_RTRV_MSGS" and accepts a Retrieval Confirm message with result as "RESULT_SUCCESS" in response.
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for Integer based IIDs.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state and SS7 link is established.
Ref: Section 3.3.1.9 and 3.3.1.10 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_9 Ensure that the IUT having sent a Retrieval Request message,
accepts a Retrieval Confirm message with result as "RESULT_FAILURE" from peer.
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for Integer based IIDs.
Pre-Condition: SCTP association is established between IUT and SGP.
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
Retrieval Request and Retrieval Confirm messages with action as "ACTION_RTRV_BSN" have already
been exchanged.
Ref: Section 3.3.1.9 and 3.3.1.10 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_10 Ensure that the IUT, to request emergency alignment of the SS7 link, sends a State Request message to the peer,
with action as "STATUS_EMER_SET" and accepts a State Confirm message in response.
Status: Mandatory
Config: One ASP is configured in an AS.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state.
Ref: Section 3.3.1.5 and 3.3.1.6 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_11 Ensure that the IUT, to cancel emergency alignement of the SS7 link, sends a State Request message,
with action as "STATUS_EMER_CLEAR" and accepts a State Confirm message in response.
Status: Mandatory
Config: One ASP is configured in an AS.
Pre-Condition: SCTP association is established between IUT and SGP.
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
Ref: Section 3.3.1.5 and 3.3.1.6 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_12 Ensure that the IUT, to clear all queues, sends a State Request message to the peer,
with action as "STATUS_FLUSH_BUFFER" and accepts a State Confirm message in response.
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for Integer based IIDs.
Pre-Condition: SCTP Association is established between ASP and SGP.ASP is in active state.
Ref: Section 3.3.1.5 and 3.3.1.6 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_13 Ensure that the IUT, to clear the retranmit queue, sends a State Request message to the peer,
with action as "STATUS_CLEAR_RTB" and accepts a State Confirm message in response.
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for Integer based IIDs.
Pre-Condition: SCTP association is established between IUT and SGP
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP.
Ref: Section 3.3.1.5 and 3.3.1.6 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_14 Ensure that the IUT, to audit the state of the link, sends a State Request message, with action as
"STATUS_AUDIT" and accepts a State Confirm message in response.
Status: Mandatory
Config: One ASP is configured in an AS.
Pre-Condition: SCTP association is established between IUT and SGP
IUT is in active state and has successfully requested the establishment of an SS7 link at the SG.
Ref: Section 3.3.1.5 and 3.3.1.6 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_15 Ensure that the IUT accepts a Release Indication message from peer for a link
Status: Mandatory
Config: Single ASP is Configured in an AS.AS is Configured for Integer based IIDs.
Pre-Condition: SCTP association is established between IUT and SGP
IUT is in active state and has successfully requested the establishment of an SS7 link at the SGP..
Ref: Section 3.3.1.4 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_V_16 Ensure that IUT, having sent an Establish Request message, on the expiry of the timer, re-sends the
Establish Request message.
Status: Mandatory
Config: One ASP is configured in an AS.
Pre-Condition: SCTP association is established between IUT and SGP
IUT is in active state and requested the establishment of an SS7 link at the SGP.
Ref: Section 3.3.1.3 of RFC 3331
SUT: ASP
M2UA_ASP_MAUP_I_01 Ensure that the IUT sends an Error message with error code as "Invalid Interface Identifier",
when it receives a State Indication message from peer for invalid IID
AS is Configured for Integer based IIDs.
ASP is in active state and SS7 link is established.
SUT: ASP
M2UA_ASP_MAUP_I_02 Ensure that the IUT sends an Error message with error code as "Invalid Version",
when it receives a Data message from peer with invalid version.
AS is Configured for Integer based IIDs.
ASP is in active state and SS7 link is established.
SUT: ASP
GEH
M2UA_GEH_01 Ensure that the IUT sends an Error message with error code as "Invalid Interface Identifier", when it
receives a message from peer with a non-configured interface identifier.
SUT: SG or ASP
M2UA_GEH_02 Ensure that the IUT sends an Error message with error code as "Unsupported Traffic Handling mode",
when it receives a message with an unsupported traffic handling mode.
SUT: SG or ASP
M2UA_GEH_03 Ensure that the IUT sends an Error message with error code as "Unsupported Interface Identifier Type",
when it receives a message from peer with a non-supported (e.g. text-based) interface identifier type.
SUT: ASP or SGP
M2UA_GEH_04 Ensure that the IUT sends an Error message with error code as "Unsupported Message Class", when it
receives a message from peer with an unexpected or unsupported message class.
Status: Mandatory
Pre-Condition:
Ref: Section 3.3.3.1 of RFC 3331
SUT: SG or ASP
M2UA_GEH_05 Ensure that the IUT sends an Error message with error code as "Invalid Parameter Value", when it
receives a message from peer with an invalid parameter value
SUT: SG/ASP
M2UA_GEH_06 Ensure that the IUT sends an Error message with error code as "Parameter Field Value", when it receives
a message from peer with a parameter with a wrong length field.
SUT: SG/ASP
M2UA_GEH_07 Ensure that the IUT sends an Error message with error code as "Unexpected Parameter", when it receives
a message from peer with an invalid parameter.
SUT: SG/ASP
M2UA_GEH_08 Ensure that the IUT sends an Error message with error code as "Missing Parameter", when it receives a
message from peer with a mandatory parameter missing.
SUT: ASP
MISC
M2UA_Test_Encoding_MISC1 Test for all different message encoding variations
SUT:
M2UA_Test_Encoding_Notify_Req_1 Test for all different message encoding variations
SUT:
M2UA_Test_Encoding_Notify_Req_2 Test for all different message encoding variations
SUT:
M2UA_Test_Encoding_Release_Req_1 Test for all different message encoding variations
SUT:
M2UA_Test_Data_1 Internal test to encode / decode data
SUT: None
M2UA_Test_ISUP_IAM_1 Bring up link, receive IAM, send back IAM
SUT: SG
M2UA_Test_Check_Receive_Data Check the data received from the SUT matches a specified string
Note: IUT needs to establish or have already established an SS7 link.
Config: Single ASP is configured in an AS.
SUT: SGP SGP
M2UA_SGP_Test_Check_IID Test sends an ASP_Active message and checks the received Interface ID is the same as the
Interface ID sent in the ASP_Active message.
Pre-Condition: SCTP Association is established between ASP and SGP
Status: Optional
Ref: 3.3.2.7, 3.3.2.8 of RFC 3331
SUT: SGP
M2UA_ASP_Test_Check_IID Test waits for an ASP_Active message and checks the received Interface ID is the same as the
Interface ID stored in the configuration parameter, Interface_ID_1.
Pre-Condition: SCTP Association is established between ASP and SGP
Status: Optional
Ref: 3.3.2.7, 3.3.2.8 of RFC 3331
SUT: ASP
RTests
M3UA_RTest_Heartbeat_S Test for message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Heartbeat_Ack_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M2UA_RTest_Notify_S Test for all different message encoding variations
SUT:
M2UA_RTest_Data_Retrieval_Req_S Test for all different message encoding variations
SUT:
M2UA_RTest_Data_Retrieval_Conf_S Test for all different message encoding variations
SUT:
TEST_SIGNAL_HEARTBEAT_CONTROL_SIGNALS Test signals to control heartbeats and heartbeat acks; background handling and whether they are received by test suite
Send_Background_Heartbeat
Send_Background_Heartbeat_ACK
Input_Heartbeat
Input_Heartbeat_ACK
settings in SCTP codec.
Configuration:
Test runs in single-PCO mode; only uses PCO1.
No SCTP association should be established.
Start this scenario; result should be PASS.
TEST_SIGNAL_SCTP_HEARTBEAT_AND_SCTP_HEARTBEAT_ACK Test signals to control heartbeats and heartbeat acks; background handling and whether they are received by test suite
Send_Background_Heartbeat
Send_Background_Heartbeat_ACK
Input_Heartbeat
Input_Heartbeat_ACK
settings in SCTP codec.
Proper operation of the control signals is required for this scenario to pass.
Test runs in single-PCO mode; only uses PCO1.
No SCTP association should be established.
Start this scenario; result should be PASS.

Variable Default Value Description
N_Adaptors 1 Number of adaptors to use. Default = 1
N_Sockets 2 Number of SCTP sockets/associations. Default = 2
ASP_Automated_Preamble FALSE If TRUE, automates test preamble for required test state
PCO1_Use_Primary_Address TRUE Use primary or secondary NIC card for this PCO
PCO2_Use_Primary_Address TRUE Use primary or secondary NIC card for this PCO
PCO3_Use_Primary_Address TRUE Use primary or secondary NIC card for this PCO
PCO4_Use_Primary_Address TRUE Use primary or secondary NIC card for this PCO
PCO1_Src_IP_Addr "192.168.1.47" (null)
PCO1_Src_IPv6_Addr '00010000000000000000000000000... (null)
PCO1_Dst_IP_Addr "192.168.1.58" (null)
PCO1_Dst_IPv6_Addr '00020000000000000000000000000... (null)
PCO1_Src_Port 2904 (null)
PCO1_Dst_Port 2904 (null)
PCO1_2_Src_IP_Addr "192.168.5.47" (null)
PCO1_2_Dst_IP_Addr "192.168.5.58" (null)
PCO1_2_Src_Port 2904 (null)
PCO1_2_Dst_Port 2904 (null)
PCO2_Src_IP_Addr "192.168.10.46" (null)
PCO2_Dst_IP_Addr "192.168.10.61" (null)
PCO2_Src_Port 2904 (null)
PCO2_Dst_Port 2904 (null)
PCO2_2_Src_IP_Addr "192.168.5.47" (null)
PCO2_2_Dst_IP_Addr "192.168.5.58" (null)
PCO2_2_Src_Port 2904 (null)
PCO2_2_Dst_Port 2904 (null)
PCO3_Src_IP_Addr "192.168.3.51" (null)
PCO3_Dst_IP_Addr "192.168.3.52" (null)
PCO3_Src_Port 50001 (null)
PCO3_Dst_Port 50001 (null)
PCO3_2_Src_IP_Addr "192.168.5.47" (null)
PCO3_2_Dst_IP_Addr "192.168.5.58" (null)
PCO3_2_Src_Port 9900 (null)
PCO3_2_Dst_Port 9900 (null)
PCO4_Src_IP_Addr "192.168.4.51" (null)
PCO4_Dst_IP_Addr "192.168.4.52" (null)
PCO4_Src_Port 50001 (null)
PCO4_Dst_Port 50001 (null)
PCO4_2_Src_IP_Addr "192.168.5.47" (null)
PCO4_2_Dst_IP_Addr "192.168.5.58" (null)
PCO4_2_Src_Port 9900 (null)
PCO4_2_Dst_Port 9900 (null)
PCO1_Adaptor_ID 1 Adaptor ID used for testing
PCO2_Adaptor_ID 2 Adaptor ID used for testing
Layer_3_Protocol Use_IPv4 Network layer; above Ethernet, default = Use_IPv4
PX_ASP_Preamble_Wait_For_ASP_DOWN TRUE Set to FALSE to bypass ASP_DOWN preamble
Process_Type (null) (for future use) Role of the Tester: SG or ASP/MGC
PDU_SLTM '111088'H Payload to be used in Data PDUs; typically SLTM
PDU_SLTA '211088'H Payload to be used in Data PDUs; typically SLTA
PDU_TEST_RX_DATA '11223344'H Payload to test for in received Data. Used in scenario: M2UA_Test_Check_Receive_Data
StreamID_Mgt 0 Stream ID for management messages. Default = 0
StreamID_Data 1 Stream ID for data (MAUP) messages. Default = 1
Correlation_ID_Used FALSE Use Correlation ID in outgoing messages. Default = FALSE
Correlation_ID 1 Correlation ID to use in outgoing messages
Local_RK_Identifier_Invalid 100 Invalid Routing Key ID. Default = 100
N_Output_Streams 2 Number of Tester SCTP Output streams
N_Input_Streams 2 Number of Tester SCTP Input streams
Encoding_Type (null) SS7 encoding type
Interface_ID_Invalid 9 Invalid IID
Interface_ID_Non_Configured 10 Non configured IID
Orig_PC (null) (null)
Dest_PC (null) (null)
Network_Indicator International (null)
Service_Indicator SI_ISUP (null)
SLC 1 (null)
IAM '011000000003060D038090A207011... ISUP IAM Hex
ASP_ID_1_Used TRUE Use ASP ID 1 in outgoing messages? Default = TRUE
ASP_ID_1 1 ASP ID number for first ASP
ASP_ID_2_Used TRUE Use ASP ID 2 in outgoing messages? Default = TRUE
ASP_ID_2 2 ASP 2 ID number
ASP_ID_Invalid 999 Invalid ASP ID
Info_Used FALSE Use Info field in outgoing messages? Default = FALSE
Info "Info" Info field value
Traffic_Mode_Used TRUE Use Traffic Mode in outgoing ASPTM messages? Default = TRUE
Traffic_Mode Over_Ride Traffic Mode
Traffic_Mode_Unsupported Broadcast Traffic Mode unsupported
Interface_ID_1_Used TRUE Use Interface ID in outgoing messages? Default = TRUE
Interface_ID_1 1 Interface ID
Interface_ID_1_Invalid 11 Invalid Interface ID value
Interface_ID_2_Used FALSE Use Interface ID in outgoing messages? Default = TRUE
Interface_ID_2 2 Interface ID
Interface_ID_2_Invalid 12 Invalid Interface ID value
AS1_Configured_IID 0 Interface ID for AS1. Used in tests (eg M2UA_ASP_ASPM_V_05) that verify an IID is for AS1
Interface_ID_range FALSE set TRUE to use ID_1..ID_2 as a range
Bad_Parameter_Length '0100040100000018000B000900000... Bad parameter for ASP Active Message
Bad_Parameter_Length_Ack '0100040300000018000B000900000... Bad parameter for ASP Active Ack Message
Invalid_Parameter '01000401000000180099000800000... Invalid parameter
Invalid_Parameter_Ack '01000403000000180099000800000... Invalid parameter
String_IID '0100040100000018000B000800000... String IID for ASP Active Message
String_IID_Ack '0100040300000018000B000800000... String IID for ASP Active Ack Message
Data_Invalid_Version ''H Data Invalid version
Event_Used TRUE Use Event in outgoing messages? Default = TRUE
Event (null) Event value
Local_LK_Id (null) (null)
SDT_Id (null) (null)
SDL_Id (null) (null)
SCTP_Establish_Time_Allowed 20000 Time M2UA_SGP_Start allows to set up SCTP association(s), default = 20000
Preamble_Time_Allowed 30000 Preamble delay for sending signals to set correct test state, default = 30000
Conf_Wait_Time_Allowed 82000 Time to wait for confirmation response after a request, default = 82000
Send_Data_Time_Allowed 30000 Time to wait for user to send data to tester, default = 30000
Response_Time_Allowed 30000 Time to wait for response (usually during setup), default = 30000
T_Wait_ASP_Ack_VAL 2000 Time to wait for response, default = 2000 (2 seconds)
T_Wait_For_Response_VAL 2000 Time to wait for response, default = 2000 (2 seconds)
Short_Time_Allowed 1000 Used in M2UA_SGP_ASPM_IO_02 for short timeout, default = 1000
Use_Dynamic_Registration TRUE Set to TRUE if registration is to be performed on an ASP in the preamble of a test.
Service_Indicator_SLTM SI_Sig_Net_Test_And_Mgt (null)
Wait_Time 3000 Self-test diagnostics
MyTestSuiteTesterRole (null) Self-test diagnostics
Sender_Response_Wait_Time 4000 Self-test diagnostics
Sender_Pause_Time 1000 Self-test diagnostics
Listener_Wait_Time 30000 Self-test diagnostics

Copyright © ACATS Forum 2008 on behalf of the test suite author. All rights reserved. Specifications may change subject to requirements.

02 Dec 2008 Produced by SAFIRE V20.07.34.01
www.SAFIRE-World.com		 Test Suite Overview