SUA_TS: Valid8.com/ACATS SUA Conformance Test Suite V.1.4, for use with SIGTRAN SUA Signaling Tester
TEST SUITE OVERVIEW
References draft-agurmukhani-test-spec-sua-00.txt (2003-08) / IETF SUA RFC3868
Archive/Project voip/SUA_ts
Version 19171599
Date 02 Dec 2008
Number of Scenarios 110
Number of Groups 18
Average per Group 6
GROUP/SCENARIO TEST PURPOSE
SUA_SG_Start Activate SCTP as pre-condition for other tests for SUT = SGP
SUT: SGP
SUA_ASP_Start Activate SCTP as pre-condition for other tests for SUT = ASP
SUT: ASP
SUA_SGP
SUA_SGP/
SUA_SGP_ASPSM
SUA_SGP_ASPSM_1 To check that an ASP sends Heartbeat messages (to ensure that the SUA peers
are still available to each other) and receives a Heartbeat Ack from the remote peer.
ASP. ASP is active. Also arrange the data in ASP such that BEAT
message is sent from ASP to SGP.
Status: Mandatory
SUT:
SUA_SGP_ASPSM_2 To check that if ASPUP message is sent to the SGP, then the ASP should discard
any other message, till an ASPUP_ACK message is received
AS and AS is in AS-Down state i.e. ASP1 is down. Arrange the data in
ASP such that ASPUP message is sent to the SGP two times on stream 0.
Status: Mandatory
SUT:
SUA_SGP_ASPSM_3 To check that if ASPUP message is received in ASP-Up state then ASP-Up-Ack
message is sent to the ASP
ASP and AS is in AS-Down state. Arrange the data in ASP such that ASPUP
message is sent to the SGP two times on stream 0.
Status: Mandatory
SUT:
SUA_SGP_ASPSM_4 To check that if ASPUP message is received in ASP-ACTIVE
state then message ASP-Up-Ack is sent to the ASP, and the ASP
state is changed in all the relevant AS.
TEST CONFIGURATION: A
in AS-Active state i.e. ASP is ACTIVE
Status: Mandatory
SUT:
SUA_SGP_ASPSM_5 To check that if ASPDN message is received in ASP-Down
state then ASP-Down-Ack message is sent to the ASP.
ASP and ASP is in Up state. Arrange the data in ASP such
that ASPDN message is sent to the SGP two times on stream 0.
Status: Mandatory
SUT:
SUA_SGP/
SUA_SGP_ASPTM
SUA_SGP_ASPTM_1 To check that if ASPAC message carries multiple Routing
Contexts, and the SGP cannot Activate One of the Routing
Context, then the SGP MUST Send ERROR Message for each
Routing Context value that cannot be successfully activated
SGP and ASP.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_2 To check that if ASPAC message is received at the SGP
end, for an ASP that is not registered with the SGP and also SGP has
no knowledge of ASP through static configuration, SGP MAY Discard
this message silently.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_3 To check that if ASP Inactive is received when AS is active
and if the AS has a single ASP, AS moves to Pending state which
changes to Active when Active message is received from Asp.
and ASP (with two or more streams). ASP is active and is the only
ASP serving the AS
Status: Mandatory
SUT:
SUA_SGP_ASPTM_4 To check that if ASPUP message is received in ASP-ACTIVE
state then message ASP-Up-Ack is sent to the ASP, and the ASP
state is changed in all the relevant AS.
ASP and AS is in AS-Active state i.e. ASP is ACTIVE.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_5 To check that if ASPAC message is sent to an SGP
which carries an already active ASP for that AS, then all the new
traffic should be directed to this ASP and the SGP MUST send a NTFY
message with code "Alternate ASP Active " to the other ASP.
SCTP association is established between SGP
and ASP1,ASP2. The AS to which the ASPs belong is configured
at the SGP with mode as OVERIDE. ASP1 is active and
handling Traffic.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_6 To verify that if an AS is configured to operate in
Loadshare mode, then any data should be distributed amongst all the
ASPs present in that AS.
and ASPs. The AS to which the ASP1, ASP2, ASP3 belongs is configured
at the SGP with mode as LOADSHARE.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_7 To verify behavior of AS with Loadshare Traffic mode when
one/more ASPs in it move to Inactive .
and ASPs. The AS to which the ASP1, ASP2, ASP3 belongs is configured
at the SGP with mode as LOADSHARE. The minimum number ASPs required
to be Active in AS is 1.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_8 To verify that if ASPs are operating in Broadcast mode
all the Data MUST be sent to all the Active ASPs.
ASPs. The AS to which the ASP1, ASP2, ASP3 belongs is configured at
the SGP with mode as BROADCAST.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_9 To verify that if ASPs are operating in Broadcast mode
the SGP MUST tag the first DATA message broadcast in each SCTP
stream with a unique Correlation Id parameter.
and ASPs. The AS to which the ASP1, ASP2 belongs is configured at
the SGP with traffic handling mode as BROADCAST.
Reference:
Status: Mandatory
SUT:
SUA_SGP_ASPTM_10 To check that if an AS has only 1 ASP in the ACTIVE state,
and it moves to ASP-INACTIVE state, SGP MUST send a Notify message
("AS-Pending") to all the ASPs in the AS which are in the state ASP-
INACTIVE.
and ASPs.AS has three ASPs, ASP1 is in ACTIVE State,
ASP2 is in INACTIVE State and ASP3 is in DOWN State.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_11 To check that if ASPAC message is received in ASP-Active
state then ASP-Active-Ack message is sent to the AS.
ASP and AS is in AS-Inactive state. Arrange
the data in AS such that ASPAC message with correct Traffic Mode
and routing context P is sent to the SGP.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_12 To check that if ASPIA message is received in ASP-Up state
then ASP-Inactive-Ack message is sent to the ASP.
ASP and AS is in AS-Active state i.e. ASP1 is active.
Arrange the data in AS such that ASPIA message and Routing
Context P is sent to the SGP two times.
Status: Mandatory
SUT:
SUA_SGP_ASPTM_13 To check that if ASPAC message is received in ASP-Down
state then message is discarded.
ASP and ASP is down. Arrange the data in ASP such that ASPAC is sent
to SGP .
Status: Mandatory
SUT:
SUA_SGP_ASPTM_14 To check that if ASPAC message is received without any
Routing Context then status of ASP is active in all the AS
which this ASP serves.
ASP. ASP is Inactive in both the AS at the SGP. Arrange data in ASP
such that ASPAC messages is sent to the SGP from ASP.
Dont fill any routing context parameter in ASPAC.
Status: Mandatory
SUT:
SUA_SGP/
SUA_SGP_SSNM
SUA_SGP_SSNM_1 To check that if N-PCState indication primitive is received
(with Point code status as Unavailable)from NIF at SGP then SGP sends
DUNA message to the concerned ASPs.
ASP1, ASP2 and ASP3. All AS are in AS-Active state. AS1 and AS2 are
handling traffic for N/w appearance A and AS3 is handling traffic for
N/w Appearance B.
Status: Mandatory
SUT:
SUA_SGP_SSNM_2 To check that if N-PCState indication primitive is received
(with Point code status as Available)from NIF at SGP then SGP sends
DAVA message to the concerned ASPs.
ASP1, ASP2 and ASP3. All AS are in AS-Active state. AS1 and AS2 are
handling traffic for N/w appearance A and AS3 is handling traffic for
N/w Appearance B.
Status: Mandatory
SUT:
SUA_SGP_SSNM_3 To check that if N-PCState indication primitive with point
code status as congested is received from NIF at SGP then SGP sends
SCON message to the concerned ASPs.
ASP1, ASP2 and ASP3. All AS are in AS-Active state. AS1 and AS2 are
handling traffic for N/w appearance A and AS3 is handling traffic for
N/w Appearance B.
Status: Mandatory
SUT:
SUA_SGP_SSNM_4 To check that if N-PCState indication primitive with cause
User Part Unavailable is received from NIF at SGP then SGP sends DUPU
message to the concerned ASPs.
ASP1, ASP2 and ASP3. All AS are in AS-Active state. AS1 and AS2 are
handling traffic for N/w appearance A and AS3 is handling traffic for
N/w Appearance B.
Status: Mandatory
SUT:
SUA_SGP_SSNM_5 To check that if N-PCState indication primitive with status
as Restricted is received from NIF at SGP then SUA at SGP sends DRST
Message to the concerned ASPs.
ASP1, ASP2 and ASP3. All AS are in AS-Active state. AS1 and AS2 are
handling traffic for N/w appearance A and AS3 is handling traffic
for N/w Appearance B.
Status: Mandatory
SUT:
SUA_SGP_SSNM_6 To verify that DAUD received at SGP without Mandatory
parameter is rejected.
ASP1. AS1 is in Active state. Also arrange the data in ASP such that
DAUD is sent to SGP without Affected Point code parameter.
Status: Mandatory
SUT:
SUA_SGP/
SUA_SGP_DRKM
SUA_SGP_DRKM_1 To check that on receiving a Routing Key Registration
Request for a new valid RK from an ASP, the SGP adds a RK and
confirms the registration to the ASP.
ASP. The ASP is in Inactive state. The Routing Key RK1 is not
configured at the SGP side.
Arrange Data in ASP such that a Routing Key Registration request is
sent from ASP to SGP on stream 0.
Status: Mandatory
SUT:
SUA_SGP_DRKM_2 To check that on receiving a Routing Key Deregistration
Request for a existing RK from an ASP, the SGP removes the
requesting ASP from the List of ASPs serving that RK.
and ASP. The Routing Key RK1 is configured at the SGP side.
The ASP is in Active State for RK1 at the SGP. Arrange Data in
ASP such that a Routing Key Deregistration request for RK1 is
sent from ASP to SGP on stream 0.
Status: Mandatory
SUT:
SUA_SGP_DRKM_3 To check that on receiving a Routing Key Registration
Request for a existing RK from an ASP, the SGP adds the
requesting ASP to the List of ASPs serving that RK.
and ASP1 .ASP2. The Routing Key RK1 is configured at
the SGP side. The ASP1 is in Inactive State at the SGP and ASP2
is actively handling Traffic for RK1 with RC value as RC1. The
AS for RK1 is in Traffic handling Mode Override. Arrange Data in ASP
such that a valid Routing Key Registration request with Traffic Mode
consistent with mode at SG for RK1 is sent from ASP1 to
SGP on stream 0.
Status: Mandatory
SUT:
SUA_SGP_DRKM_4 To check that on receiving a Routing Key Registration
Request for an existing RK from an ASP that is already active
for the RK, the Registration Fails and a Negative Response
Message is sent to the ASP.
and ASP. The Routing Key RK1 is configured at the SGP side.
The ASP is in Active State for RK1 at the SGP. Arrange Data in
ASP such that a Routing Key Registration request for RK1 is sent
from ASP to SGP on stream 0.
Status: Mandatory
SUT:
SUA_SGP_DRKM_5 To check that on receiving a Routing Key Deregistration
Request for an existing RK from an ASP which is active
for the RK, the Deregistration Fails and a Failure Response
Message is sent to the ASP.
and ASP. The Routing Key RK1 is configured at the SGP side.
The ASP is in Active State for RK1 at the SGP. Arrange Data in
ASP such that a Routing Key Deregistration request for RK1 is sent
from ASP to SGP on stream 0.
Status: Mandatory
SUT:
SUA_SGP_DRKM_6 To check that on receiving a Routing Key Registration
Request from two different ASPs at the SGP Stack, the SGP
allocates the same RC ID to both of these.
and ASP1 , ASP2. Both ASP1 and ASP2 are in Inactive
State at the SGP. Arrange Data in ASP1 and ASP2 such that a
valid Routing Key Registration request for RK1 is sent from ASP
to SGP on stream 0.
Status: Mandatory
SUT:
SUA_SGP_DRKM_7 To verify that after an ASP has successfully deregistered
from the AS, data is not routed to that ASP.
ASP1, ASP2. Both ASP1 and ASP2 have been added dynamically to
AS.AS is routing data to both the ASPs on Loadshare basis.
Status: Mandatory
SUT:
SUA_SGP/
SUA_SGP_MGMT
SUA_SGP_MGMT_1 To check that if the SGP receives an ASP-UPACK
message it discards the message.
SGP and ASP (with two or more streams.)
Status: Mandatory
SUT:
SUA_SGP_MGMT_2 To check that if ASPUP message is received for an ASP,
which has been marked as LOCKED for MGMT purposes, the SGP
sends an error message with error code "Refused -
Management Blocking".
SGP/IPSP. The example listed below covers the IUT running at
the SGP.
AS and AS is in AS-Down state i.e. ASP1 is down. Arrange
the data in AS such that ASPUP message is sent to the SGP
two times on stream 0.
Status: Mandatory
SUT:
SUA_SGP_MGMT_3 To check that if ASPAC message carries a Traffic mode
which is incompatible at the SGP, then an error message
with code "Unsupported / Invalid Traffic Handling Mode" MUST be
sent.
SGP and ASP. The AS to which the ASP belongs MUST be configured at
the SGP with traffic handling mode OVERIDE.
Status: Mandatory
SUT:
SUA_SGP_MGMT_4 To check that if a message with message type not defined is
received at SGP, SGP responds with ERROR message containing cause
"Unsupported Message Type".
ASP and ASP1 is active. Arrange the data in ASP such that a message
with Message type not defined is sent to SGP. Let the other
parameters in the message be like any other message.
Status: Mandatory
SUT:
SUA_SGP_MGMT_5 To check that if a message with message Class not defined
is received at SGP, SGP responds with ERROR message containing cause
"Unsupported Message Class".
ASP and ASP1 is active. Arrange the data in ASP such that a message
with Message class not defined is sent to SGP. Let the other
parameters in the message be like any other message.
Status: Mandatory
SUT:
SUA_SGP_MGMT_6 To check that if ASPSM(except BEAT/BEAT-ack) is received on
an unexpected SCTP stream, error containing error code "Invalid
Stream Identifier" is sent back.
streams)between SGP and ASP and ASP1 is down
Status: Mandatory
SUT:
SUA_SGP_MGMT_7 To check that if a message with value of length parameter
less than length of mandatory parameters is received then message is
discarded.
ASP and AS is in AS-Active state. Arrange the data in ASP such that
Error message with length parameter filled with value less than the
length of error code parameter is sent.
Status: Mandatory
SUT:
SUA_SGP_MGMT_8 To check that if an error is received then that is reported
to the SM and no action is taken against that.
ASP. ASP is active. Arrange data in ASP such that ERROR with cause
invalid version is sent to the SGP.
Status: Mandatory
SUT:
SUA_SGP_MGMT_9 If the SGP receives a Message from the ASP which is not
padded, then also the Message should be Processed.
ASP. ASP is in ASP-Down state. Arrange data in ASP such that ASPUP
is sent to SGP with size of Info String such that the Total
Message Length is 35 Bytes and this Message should not be padded.
Status: Mandatory
SUT:
SUA_ASP
SUA_ASP/
SUA_ASP_ASPM
SUA_ASP_ASPSM_1 To check that if ASPDN-ACK message is received in
ASP-INACTIVE state then the ASP Should move to ASP-Down, and the
Procedure to bring the ASP into ASP-INACTIVE State may be initiated
by ASP itself.
SGP and ASP.
Status: Mandatory
SUT:
SUA_ASP_ASPSM_2 To check that if ASPDN-ACK message is received in ASP-
Active state then the ASP Should move to ASP-Down, and the
procedure to bring the ASP into ASP-ACTIVE state may be initiated
by the ASP itself.
SGP and ASP.
Status: Mandatory
SUT:
SUA_ASP_ASPSM_4 To check that if Ack message is not received in response to
the ASPUP message then ASP keeps on sending ASPUP message at an
interval for some time and after some tries will report the SM.
ASP. Also arrange the data in ASP such that SM sends ASP Up primitive
to the SUA. Arrange data in SGP such that Ack message
is not sent in response to the ASPUP message.
Status: Mandatory
SUT:
SUA_ASP_ASPSM_5 To check that if ASP-Up-Ack message is received in
response to the ASPDN then the Ack message is rejected and ASPDN is
sent again.
ASP and ASP is Up. Arrange data in SGP such that ASP-Up-Ack is sent
to ASP in response to ASPDN message on stream 0.
Status: Mandatory
SUT:
SUA_ASP_ASPSM_6 To check that if ASP-Up-Ack message is received in
response to the ASPAC then the Ack message is accepted and ASPAC
retransmission is stopped.
ASP and ASP is Up. Arrange data in SGP such that ASP-Up-Ack is sent
to ASP in response to ASPAC message .
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_ASTM
SUA_ASP_ASPTM_1 To Check that if ASPDN-ack is received in response to
ASPAC, ASPAC retransmissions are stopped.
ASP (with two or more streams). ASP1 is inactive.
Status: Mandatory
SUT:
SUA_ASP_ASPTM_2 To check that if ASPIA-ack is received in response to
ASPAC, ASPAC retransmissions are stopped.
ASP (with two or more streams). ASP1 is inactive.
Status: Mandatory
SUT:
SUA_ASP_ASPTM_3 To Check that if ASPAC-ack with multiple duplicate Routing
contexts is sent, the message is accepted at ASP and ASPAC
retransmissions stop.
ASP (with two or more streams). ASP1 is inactive. AS has been added
with RC value P.
Status: Mandatory
SUT:
SUA_ASP_ASPTM_4 To check that if ASP-Active-Ack message is received in
response to the ASPIA then the Ack message is discarded and ASPIA is
sent again.
ASP and ASP is active. Arrange the data in SGP such that
ASP-Active-Ack with routing context P is sent to ASP.
Status: Mandatory
SUT:
SUA_ASP_ASPTM_5 To check that if ASP-Down-Ack message is received in
any state, the state of the ASP changes to Down.
ASP and ASP is Active/Inactive. Arrange the data in SGP such that
ASP-Down-Ack is sent to ASP on stream 0.
Status: Mandatory
SUT:
SUA_ASP_ASPTM_6 To Check that ASP successfully processes RCs spread
over Multiple ASP Active Ack Messages.
ASP is Inactive. Arrange the data in SGP such that ASP-Active-Ack
with RC value P or Q are sent to ASP.
Status: Mandatory
SUT:
SUA_ASP_ASPTM_7 To check that if ASPIA-ACK message is received in
ASP-Active state then the ASP Should move to ASP-INACTIVE,
and the procedure to bring the ASP into ASP-ACTIVE state should be
initiated by the ASP itself.
ASP.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_SSNM
SUA_ASP_1 To check that if SSNM message is received at the ASP then
it is reported to the ULP.
ASP and ASP is Active. Also arrange the data in SGP such that DUNA,
DAVA, DUPU, DRST and SCON messages are sent from the SGP to the ASP
with valid parameters and they are sent on stream number 0.
Status: Mandatory
SUT:
SUA_ASP_SSNM_2 To check that when a Restricted and unavailable Routes are
available for a Point code, ASP routes through RESTRICTED Route.
and ASP and SG2 and ASP. SGP1 serves SG1 and SGP2 serves SG2.
ASP is Active for RC P in all SGPs.
Also arrange the data in ASP such that SU sends Unitdata Indication
primitive to SUA containing the RC value P. Also arrange Data at SGPs
to send SSNM for PC Y. Route to PC Y is available from both SG1
and SG2. The routes through both the SGs are equi-priority routes
and ASP loadshares between two SGs.
Status: Mandatory
SUT:
SUA_ASP_SSNM_3 To check that when a Restricted and Congested Routes are
available for a Point code, ASP routes through Congested Route.
SGP2 and ASP. ASP is Active for RC P in all SGPs.
Also arrange the data in ASP such that SU sends a Unitdata
Indication primitive to SUA containing the RC value P. Also arrange
Data at SGPs to send SSNM for PC Y. Route to PC Y is available from
both SG1 and SG2. SG mode for ASP is Loadshare.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_DRKM
SUA_ASP_DRKM_1 To check that when SM invokes Registration Request a
valid REG_REQ message is sent to the SGP.
and ASP. ASP is Inactive in SGP. Also arrange the data in ASP
such that Layer Mgmt sends a Reg. Req Primitive to SUA containing a
valid Routing Key (Indicator). Also arrange Data at SGPs to send
REG RESP with a RC value.
Status: Mandatory
SUT:
SUA_ASP_DRKM_2 To check that when SM invokes Deregistration Request a
valid DEREG_REQ message is sent to the SGP.
and ASP. ASP is Inactive in SGP. Also arrange the data in ASP
such that Layer Mgmt sends a DeReg Req Primitive to SUA containing a
valid Routing Context. Also arrange Data at SGPs to send
DEREG RESP with a RC value.
Status: Mandatory
SUT:
SUA_ASP_DRKM_3 To check that for a sent Registration Request, if the ASP
receives response with Invalid/Non-Matching LRK, it is rejected.
and ASP. ASP is Inactive in SGP. Also arrange the data in ASP
such that SU sends a Reg. Req. Primitive to SUA containing a
valid Routing Context. Also arrange Data at SGP to send
Reg RESP with Invalid Local Routing Key identifier.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_MGMT
SUA_ASP_MGMT_1 To check that if the SGP receives an ASP-UP
message it discards the message.
SGP and ASP (with two or more streams.)
Status: Mandatory
SUT:
SUA_ASP_MGMT_2 To check that if a message with value of length parameter
less than length of mandatory parameters is received then message is
discarded.
ASP, and ASP is Down. Arrange the data in SGP such that ASPUP-Ack
message with length parameter filled with value less than the length
of Common Message Header.
Status: Mandatory
SUT:
SUA_ASP_MGMT_3 To check that if DUPU message with MASK value other than 0
is received ,an error is sent back to SGP.
ASP and ASP is active. Arrange the data in SGP such that DUPU message
with mask value not equal to 0 is sent to the ASP.
Status: Mandatory
SUT:
SUA_ASP_MGMT_4 To check that if a message is sent with the length of one
of its parameter incorrect, ASP responds with Error message
ASP and ASP is UP. Arrange the data in SGP such that DUNA
with Affected point code as Z and length of this parameter as 0xa is
sent.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_CL
SUA_ASP_CL_1 To check that successful Connectionless Data transfer
occurs from one PC to another.
ASP (with two or more streams).
Status: Mandatory
SUT:
SUA_ASP_CL_2 To check that in case a CLDT Message is sent and at the
peer the SSN is not present for which Unitdata is meant, CLDR is
returned if the return on error option is set.
ASP (with two or more streams). ASP1 is active. Also arrange the
data at SGP such that Unitdata primitive is sent to SUA
with return option set as "1"(Bit 8 in the protocol class
parameter should be set to 1)to be sent to DPC X.
Status: Mandatory
SUT:
SUA_ASP_CL_3 To check that in case CLDT Message is sent and at the peer
the SSN is not present for which Unitdata is meant, CLDR is NOT
returned if return on error option is not set.
ASP (with two or more streams). ASP1 is active. Also arrange the
data at SGP such that Unitdata primitive is sent to SUA
with return option set as "0"(Bit 8 in the protocol class parameter
should be set to 0)to be sent to DPC X
Status: Mandatory
SUT:
SUA_ASP_CL_4 To check that CLDT Messages with Protocol class 1 are
delivered in order.
ASP (with two or more streams). ASP1 is active. Also arrange the
data at SGP such that Unitdata primitive is sent to SUA
with return option set as "0"(Bit 8 in the protocol class parameter
should be set to 0)to be sent to DPC X
Status: Mandatory
SUT:
SUA_ASP_CL_5 To check that Loadsharing of CLDT Messages
ASP (with two or more streams). ASP1 and ASP2 both are active. Also
arrange the data such that Unitdata primitive is sent to SUA
containing protocol class "0" and with different sequence control
values.
Status: Mandatory
SUT:
SUA_ASP_CL_6 To check that CLDT Message received with optional
parameters before Mandatory parameters is not rejected at IUT.
ASP (with two or more streams). ASP1 is active. Also
arrange the data such that Unitdata primitive is
sent to SUA containing protocol class "0" to be sent to DPC X.
Status: Mandatory
SUT:
SUA_ASP_CL_7 To check that CLDT Messages with different value of
sequence control parameter are sent on different SCTP streams.
ASP (with more than two streams). ASP1 is active. Also arrange the
data such that Unitdata primitives are sent to SUA containing protocol
class "0" to be sent to DPC X.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_RP
SUA_ASP_RP_1 To check that successful GT Translation takes place and
Connectionless Data transfer occurs from one PC to another.
ASP (with two or more streams. ASP1 is active. Also arrange the data
In SGP such that NIF sends UNITDATA primitive to SUA containing
protocol class "0" to be sent to GT "X". Configure the SCCP Routing
control route GT "X" to DPC of ASP and SSN available at ASP.
Set the Routing Indicator in called address as Route on GT.
Status: Mandatory
SUT:
SUA_ASP_RP_2 To check that if GT Translation fails and return
option is set Connectionless Data response is sent back.
ASP . ASP1 is active. Also arrange the data in
SGP such that NIF sends UNITDATA primitive to SUA containing
protocol class "0" to be sent to GT "X". Configure the SCCP Routing
control route GT "X" to DPC of ASP and SSN that is NOT AVAILABLE at
ASP.
Status: Mandatory
SUT:
SUA_ASP_RP_3 To check that Connectionless Data transfer occurs from one
PC to another, when routing is DPC+SSN based.
ASP. ASP1 is active. Also arrange the data in
SGP such that NIF sends UNITDATA primitive to SUA with protocol
class "0" to be sent to DPC "X" and SSN "Y".
Status: Mandatory
SUT:
SUA_ASP_RP_4 To check that when routing is DPC+SSN based, and the peer
fails to locate a user, a CLDR message is sent back if return option
is set.
SGP and ASP (with two or more streams. ASP1 is active. Also arrange
the data in SGP such that NIF sends UNITDATA primitive to SUA
containing protocol class "0" to be sent to DPC "X" and SSN "Y". No
user should be registered with the SSN "Y" on the ASP side.
Status: Mandatory
SUT:
SUA_ASP_RP_5 To check that successful Connectionless Data transfer
occurs from one PC to another, when routing is based on IP.
ASP (with two or more streams). ASP1 is active. Also arrange the
data in SGP such that NIF sends UNITDATA primitive to SUA containing
protocol Class "0ö, to be sent to the ASP serving the AS with
Routing Key as A.B.C.D
Status: Mandatory
SUT:
SUA_ASP_RP_6 To check connection establishment and termination Route on
GT .
ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_RP_6_1 To check connection establishment and termination Route on GT
two or more streams). ASP1 is active
Status: Mandatory
SUT:
SUA_ASP_RP_MISC1 Test
SUT:
SUA_ASP/
SUA_ASP_SR
SUA_ASP_SR_1 To check that if segmented messages (CLDT) are received
, Reassembly is done and reassembled data indicated to user.
GT .
ASP and SGP.
Status: Mandatory
SUT:
SUA_ASP_SR_2 To check that if segmented messages (CLDT) are received
, but if remaining segments are not received during reassembly
timer.Reassembly procedure is stopped and messages discarded.
TEST CONFIGURATION: A/G
and ASP. ASP1 is active. Also arrange the data
in SGP such segmented messages are sent to ASP.
Status: Mandatory
SUT:
SUA_ASP_SR_3 To check that if segmented message (CLDT) is received and
Reassembly cannot be done, CLDR is sent back with appropriate SCCP
cause.
TEST CONFIGURATION: A/G
ASP and SGP.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_RE
SUA_ASP_RE_1 To check the Relay node functionality
and ASP2 AND ASP2 and ASP3. Also both the associations (ASP1-ASP2)
(ASP2-ASP3) are Active.
Status: Mandatory
SUT:
SUA_ASP_RE_2 To check the Relay node functionality
and ASP2 AND ASP2 and ASP3. Also both the associations (ASP1-ASP2)
(ASP2-ASP3) are Active.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_CO
SUA_ASP_CO_1 To check the Relay node functionality
and ASP (with two or more streams. ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_2 To check if the CORE message is responded with a COREF
Message the connection is not established.
and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_3 To check if the CODT message is received with a
mandatory parameter missing it is responded with an COERR Message.
and ASP (with two or more streams. ASP1 is active. SCCP connection
exists between ASP and SGP. Arrange the CODT message
so that it does not contain the mandatory parameter Routing
Context.
Status: Mandatory
SUT:
SUA_ASP_CO_4 To check that if the CORE Message carries the Source
address then the COAK Message also carries the Destination address
parameter.
and ASP (with two or more streams. ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_5 To check that if the CORE Message carries the Source
address then the COREF Message also carries the Destination
address parameter.
and ASP (with two or more streams. ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_6 To check that if RELRE message is sent and it is not
responded with either RELRE/RELCO RELRE is retransmitted.
and ASP (with two or more streams). ASP1 is active.Also ASP and SGP
have a SCCP connection between them.
Status: Mandatory
SUT:
SUA_ASP_CO_7 To check that a CODA message is received in response
to a CODT message in case of Protocol Class 3, when the
receive window becomes full.
and ASP (with two or more streams. ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_8 To check that in case of protocol class 3 if mis-
sequencing Occurs, for send Seq. Number, then the connection
is reset by peer.
and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_9 To check that in case of protocol class 3 if mis-
sequencing occurs, for receive Seq. Number, then the connection is
reset by peer.
sequencing occurs, for receive Seq. Number, then the connection is
reset by peer.
Status: Mandatory
SUT:
SUA_ASP_CO_10 To check the credit parameter negotiation in case
of protocol class 3.
SGP and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_11 To check the Connection Oriented Inactivity test
procedures in Protocol Class 3.
SGP and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_12 To check the Connection Oriented Inactivity test
procedures in Protocol Class 3.
SGP and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_13 To check that if a RELRE message is sent and is not
responded with, it will retry a number of times and then release
the connection.
and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_14 To check the protocol Class negotiation procedures in
SUA.
SGP and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_15 To check the protocol Class negotiation procedures in
SUA.
SGP and ASP (with two or more streams. ASP1 is active.Also arrange
the data in SGP such that NIF sends Connect- Req primitive to SUA
with Routing Context A, containing protocol class "2/3" to be sent
to DPC "X" and SSN "Y". No user should be registered with the SSN
"Y" on the ASP side.
Status: Mandatory
SUT:
SUA_ASP_CO_16 To check that in case of protocol class 3, Connection
can be reset by the user.
SGP and ASP (with two or more streams). ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_17 To check that in case of protocol class 3 if mis-
sequencing occurs, for recv Seq. Number, then the connection is
reset by peer.
SGP, ASP and IPSP. The example listed below covers the test
case at the ASP. The IUT is running at the ASP. However the same
MUST be executed at IPSP and SGP also.
and ASP (with two or more streams. ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_18 To check that in case of protocol class 3 if mis-
sequencing occurs, for recv Seq. Number, then the connection
is reset by peer.
SGP, ASP and IPSP. The example listed below covers the test
case at the ASP. The IUT is running at the ASP. However the
same MUST be executed at IPSP and SGP also.
and ASP (with two or more streams. ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP_CO_19 To check that in case of protocol class 3 if mis-
sequencing occurs, for send Seq. Number, then the connection is
reset by peer.
and ASP (with two or more streams. ASP1 is active.
Status: Mandatory
SUT:
SUA_ASP/
SUA_ASP_SCM
SUA_ASP_SCM_1 To check that on receiving M-SCTP-Establish primitive from
SM, ASP initiates and establishes an SCTP association with the SGP.
and ASP. Also arrange the data in ASP such that SM sends
M-SCTP-Establish primitive to SUA with the SGP id to which the
connection is to be established.
Status: Mandatory
SUT:
SUA_ASP_SCM_2 To check that on receiving SCTP-Communication Down
indication primitive from SCTP, ASP will send the M-SCTP Status
primitive to the upper layer.
ASP. ASP is in Inactive state. Also arrange the data in SGP such that
SCTP association is terminated between SGP and ASP.
Status: Mandatory
SUT:
SUA_ASP_SCM_3 To check that on receiving SCTP-Communication Restart
Indication primitive from SCTP, ASP will send the M-SCTP Status
primitive to the upper layer.
ASP. ASP is in active state. Also arrange in SGP such that SCTP
association is restarted between SGP and ASP.
Status: Mandatory
SUT:
SUA_ASP_SCM_4 To check that on receiving Communication Up primitive from
SCTP, SG SUA will send M-SCTP-Establish indication to the SM.
and ASP1. Also arrange the data in ASP such that SCTP association is
established between ASP1 and SGP.
Status: Mandatory
SUT:
SUA_ASP/
MISC
SUA_SGP_ALL_MSGS_MISC2 Test for all different message encoding variations
SUT:
SUA_Send_raw_MAP_Message Send a RAW MAP message to the peer
and ASP1. Also arrange the data in ASP such that SCTP association is
established between ASP1 and SGP.
Status: Optional
SUT:

Variable Default Value Description
N_Adaptors 1 (null)
N_Sockets 1 (null)
Adaptor_ID_1 1 Adaptor ID used for testing
Adaptor_ID_2 2 Adaptor ID used for testing
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 9900 (null)
PCO1_Dst_Port 9900 (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 9900 (null)
PCO1_2_Dst_Port 9900 (null)
PCO2_Src_IP_Addr "192.168.2.51" (null)
PCO2_Dst_IP_Addr "192.168.2.52" (null)
PCO2_Src_Port 50001 (null)
PCO2_Dst_Port 50001 (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 9900 (null)
PCO2_2_Dst_Port 9900 (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
Process_Type (null) (null)
AutoStart_After_Time 1000 (null)
StreamID 0 (null)
Interface_ID 0 (null)
Local_RK_Identifier_Invalid 100 (null)
N_Output_Streams 2 Number of Tester SCTP Output streams
N_Input_Streams 2 Number of Tester SCTP Input streams
Encoding_Type (null) (null)
Routing_Context_Invalid 9 (null)
T_Wait_ASP_Ack_VAL 2000 (null)
IAM '011000000003060D038090A207011... (null)
Local_RK_Identifier 100 (null)
OPC_Reg '00000032'H (null)
DPC_Reg '00000004'H (null)
Network_Indicator International (null)
Service_Indicator SI_ISUP (null)
ASP_ID_Used TRUE (null)
Info_Used FALSE (null)
Info "Info" (null)
Traffic_Mode_Used TRUE (null)
Traffic_Mode Over_Ride (null)
Routing_Context_Used TRUE (null)
Registration_Status (null) (null)
Deregistration_Status (null) (null)
Network_Appearance_Used (null) (null)
Network_Appearance (null) (null)
Affected_Point_Code_Used (null) (null)
Affected_Point_Code (null) (null)
Diagnotstic_Info_Used (null) (null)
Diagnotstic_Info (null) (null)
TID_Label_Used FALSE (null)
TID_Label 2 (null)
DRN_Label_Used FALSE (null)
DRN_Label 3 (null)
Protocol_Class_Used (null) (null)
Protocol_Class (null) (null)
Source_Address_Used (null) (null)
Source_Address_Routing_Indicator (null) (null)
Source_Address_Address_Indicator (null) (null)
Source_Address_Address_Param_PC_Used (null) (null)
Source_Address_Address_Param_PC (null) (null)
Source_Address_Address_Param_SSN_Used (null) (null)
Source_Address_Address_Param_SSN (null) (null)
Source_Address_Address_Param_IPV4_Used (null) (null)
Source_Address_Address_Param_IPV4 (null) (null)
Source_Address_Address_Param_HN_Used (null) (null)
Source_Address_Address_Param_HN (null) (null)
Source_Address_Address_Param_GT_Used (null) (null)
Source_Address_Address_Param_GT (null) (null)
Dest_Address_Used (null) (null)
Dest_Address_Routing_Indicator (null) (null)
Dest_Address_Address_Indicator (null) (null)
Dest_Address_Address_Param_PC_Used (null) (null)
Dest_Address_Address_Param_PC (null) (null)
Dest_Address_Address_Param_SSN_Used (null) (null)
Dest_Address_Address_Param_SSN (null) (null)
Dest_Address_Address_Param_IPV4_Used (null) (null)
Dest_Address_Address_Param_IPV4 (null) (null)
Dest_Address_Address_Param_IPV6_Used (null) (null)
Dest_Address_Address_Param_IPV6 (null) (null)
Dest_Address_Address_Param_HN_Used (null) (null)
Dest_Address_Address_Param_HN (null) (null)
Dest_Address_Address_Param_GT_Used (null) (null)
Dest_Address_Address_Param_GT (null) (null)
Sequence_Control_Used (null) (null)
Sequence_Control (null) (null)
SS7_Hop_Count_Used (null) (null)
SS7_Hop_Count (null) (null)
Importance_Used (null) (null)
Importance (null) (null)
Message_Priority_Used (null) (null)
Message_Priority (null) (null)
Correlation_ID_Used (null) (null)
Correlation_ID (null) (null)
Segmentation_Used (null) (null)
Segmentation (null) (null)
SCCP_Cause_Used (null) (null)
SCCP_Cause (null) (null)
User_Cause_Used (null) (null)
User_Cause (null) (null)
Congestion_Level_Used (null) (null)
Congestion_Level (null) (null)
Sequence_Number_Used (null) (null)
Sequence_Number (null) (null)
Dest_Ref_Number_Used (null) (null)
Dest_Ref_Number (null) (null)
Source_Ref_Number_Used (null) (null)
Source_Ref_Number (null) (null)
Credit_Used (null) (null)
Credit (null) (null)
Receive_Sequence_Number_Used (null) (null)
Receive_Sequence_Number (null) (null)
SMI_Used (null) (null)
SMI (null) (null)
SSN_Used (null) (null)
SSN (null) (null)
Wait_Time 2000 (null)

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