.R1
# abbreviate A
# label L
no-default-database
no-accumulate
database ../idrefs
annotate X pp
move-punctuation
discard YZ
.R2
.de $0
.(x 0
\\$2 \\$1
.)x
..
.if '\*(.T'ascii' \{\
.fo 'B. Bidulock'Version 0.0'FORMFEED[Page %]'
.m1 1 \" top margin above header
.m2 1 \" top margin below header
.m3 1 \" btm margin above footer
.m4 0 \" btm margin below footer
.pl 11.0i
.ll 7.2i
.lt 7.2i
.nr LL 7.2i
.nr LT 7.2i
.ad l
.hy 0
.ta 3
.ba 0
.po 0
.nr so 0
.nr ii 6n
.nr pi 4n
.nr po 3n
.nr bs 0
.nr bi 2n
.\}
.if '\*(.T'ps' \{\
.fo 'B. Bidulock'Version 0.0'Page %'
.m1 0.25i \" top margin above header
.m2 0.25i \" top margin below header
.m3 0.25i \" btm margin above footer
.m4 0.25i \" btm margin below footer
.pl 11.0i
.ll 7.2i
.lt 7.2i
.nr LL 7.2i
.nr LT 7.2i
.ad b
.hy 6
.ta 3
.ba 0
.po 0.75i
.nr so 0
.nr ii 0.5i
.nr pi 0.5i
.nr po 0.25i
.nr bs 0
.nr bi 0.25i
.nr hi 0.5i
.\}
.he 'Internet Draft'M2PA-TEST'December 2001'
.bp
.(b C
\fCNetwork Working Group                                     Brian Bidulock
\fCINTERNET-DRAFT                                       OpenSS7 Corporation


\fCExpires in six months                                      December 2001


\fR\fBSS7 MTP2-User Peer-to-Peer Adaptation Layer
\fR\fBTest Specifications
\fR\fBM2PA-TEST
\fR\fB<draft-bidulock-sigtran-m2pa-test-00.txt>

.)b
.ne 4
.uh "Status of this Memo"
.lp
This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 or RFC 2026.  Internet-Drafts are working documents
of the Internet Engineering Task Force (IETF), its areas, and its working
groups.  Note that other groups may also distribute working documents as
Internet-Drafts.
.lp
Internet-Drafts are draft documents valid for a maximum of six months and may
be updated, replaced, or obsoleted by other documents at any time.  It is
inappropriate to use Internet-Drafts as reference material or to cite them
other than as 'work in progress'.
.lp
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
.lp
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
.lp
To learn the current status of any Internet-Draft, please check the
'1id-abstracts.txt' listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
.uh "Abstract"
.lp
This Internet Draft provides information for the Internet community on test
cases for testing the SS7 M2P2-User Peer-to-Peer Adaptation Layer
.[
m2pa03
.]
based on the conformance test specifications for SS7 MTP Level 2.
.[
q781
.]

.sh 1 "Introduction"
.lp
This draft provides a set of detailed test of the SS7 MTP2-User Peer-to-Peer
Adaptation Layer
.[
m2pa03
.]
based on the test specifications for SS7 MTP Level 2.
.[
q781
.]
These tests are intended to validate the SS7 MTP2-User Peer-to-Peer Adaptation
Layer (M2PA) protocol.
.[
m2pa03
.]
The tests are broken into \fIValidation\fR (VAT) tests and \fIValidation\fR
(VAT) and \fICompatibility\fR (CPT) tests.

These tests attempt to completely validate the M2PA protocol without
redundancy.  Each test is described as simply as possible to check precisely
the elementary function of the protocol.  The tests are listed in no specific
order.

.sh 1 "Test Environment"
.sh 2 "Test Configurations"
.lp
A single M2PA link is used in the tests.  \fIFigure \n($1.\n($2(a)\fR and \fIFigure
\n($1.\n($2-2\fR show a single link between IUT and PT.  In \fITest Configuration
1\fR as shown in \fIFigure \n($1.\n($2(a)\fR, PT initiates the association.  In
\fITest Configuration 2\fR as shown in \fIFigure \n($1.\n($2-2\fR, IUT initiates
the association.  Test specifications in both configurations are written to
test the M2PA at IUT .

.(b C
\fC ________            Link 1           ________\ 
|        |       SCTP Association    |        |
|   PT   |-------------------------->|  IUT   |
|________|                           |________|

NOTE:   PT initiates the association

\fIFigure \n($1.\n($2(a).\fR  Test Configuration 1.
.(x 1
\fIFigure \n($1.\n($2(a).\fR  Test Configuration 1.
.)x
.)b

.(b C
\fC ________            Link 1           ________\ 
|        |       SCTP Association    |        |
|   PT   |<--------------------------|  IUT   |
|________|                           |________|

NOTE: IUT  initiates the association

\fIFigure \n($1.\n($2(b).\fR  Test Configuration 2.
.(x 1
\fIFigure \n($1.\n($2(b).\fR  Test Configuration 2.
.)x
.)b
.sh 2 "Recommended IUT Settings"
.sh 3 "Timer Values"
.lp
It is recommended that the following timer values be configured at the IUT for
the purposes of performing these validation tests:

.(b I F
.ip "T1"
45 seconds
.ip "T2"
5 seconds
.ip "T2l"
20 seconds
(not applicable)
.ip "T2h"
100 seconds
(not applicable)
.ip "T3"
1 second
.ip "T4n"
8 seconds
.ip "T4e"
0.5 seconds
.ip "T5"
0.1 seconds
(not applicable)
.ip "T6"
4 seconds
.ip "T7"
1 second
.ip "T8"
0.1 seconds
(not applicable)
.)b

.sh 3 "Buffer Threshold Values"
.lp
It is recommended that the following buffer threshold values be configured at
the IUT for the purpose of performing these validation tests:

.(b I F
.ip "N1"
???
.ip "N2"
127 messages
.)b

.bp
.sh 1 "Tests"
.sh 2 "Link State Control - Expected signal units/orders"
.sh 3 "Initialization (Power-up)"
.lp
These tests check that the IUT enters the correct state upon establishment of
the SCTP association.  Establishing the association at both peers is the
equivalent to the Q.703 "Power On".  The correct behavior is for both M2PA
peers to send a status "Out of Service" and enter the "Out of Service" state.
These test are useful both for Validation and Compatibility testing.
.sh 4 "Forward Direction"
.lp
The test is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 1.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|             :power on                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :power on              |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Initialization (Power-up)
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Initialization (Power-up)
.)x
.)b
.ip "Test Description:"
.np
The test begins with both the PT and the IUT in the "Power Off" state.
.np
The "Power On" command is issued at the PT and then the IUT.
.np
Check that the IUT sends a status "Out of Service" message enters and remains
in the "Out of Service" state.
.np
Repeat the test in the opposite direction as shown below.

.bp
.sh 4 "Reverse Direction"
.lp
This is the test repeated in the opposite direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 1.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :power on              |
|                        <-----------------  OUT-OF-SERVICE         |
|             :power on                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Initialization (Power-up)
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Initialization (Power-up)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both the PT and the IUT in the "Power Off" state.
.np
The "Power On" command is issued at the IUT and then the PT.
.np
Check that the IUT sends a status "Out of Service" message enters and remains
in the "Out of Service" state.

.bp
.sh 3 "Timer T2"
.lp
This test validates the T2 (Not Aligned) timer and procedure at the IUT.  This
is the duration of time that the M2PA peer will wait to receive a status
"Alignment" message after sending a status "Alignment" message.

.(b C
Reference:  Q.781/Test 1.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                              !                                    |
|                              !  T2         5.0 <= T2 <= 150.0     |
|                              !                                    |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(AERM)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T2
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T2
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both the PT and the IUT in the "Out of Service" state.
.np
The "Start" command is issued at the IUT.
.np
Check that the IUT sends a status "Alignment" message.
.np
Check that the IUT sends a status "Out of Service" and issues an "Out of
Service" indication to Level 3 with reason "Alignment Not Possible".
.np
Check that T2 is between 5.0 seconds and 150.0 seconds in duration.
.np
The IUT should stay in the "Out of Service" state.

.bp
.sh 3 "Timer T3"
.lp
This test validates the T3 (Aligned) timer and procedure at the IUT.  This is
the duration of time that the M2PA peer will wait to receive a status "Proving
Normal" or status "Proving Emergency" message from the M2PA peer after sending
status "Proving Normal" or status "Proving Emergency".
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|                              !                                    |
|                              !  T3         1.0 <= T3 <= 1.5       |
|                              !                                    |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(AERM)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T3
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T3
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both the PT and the IUT in the "Out of Service" state.
.np
The Level 3 "Start" command  is issued at the IUT.
.np
Check that the IUT sends a status "Alignment" message.
.np
Send a status "Alignment" message to the IUT.
.np
Check that the IUT response with a status "Proving Normal" message.
.np
Check that the link goes out of service for reason "Alignment Not Possible".
.np
Check that T3 is between 1.0 seconds and 1.5 seconds in duration.

.bp
.sh 3 "Timer T1 & Timer T4 (Normal)"
.lp
This test validates the T4(Normal) (Proving) and T1 (Aligned Ready) timers and
procedures at the IUT.  T4 is the duration of time that the M2PA peer will
wait to complete proving.  T1 is the duration that the M2PA peer will wait to
receive a status "In Service" or a status "Processor Outage" message from the
M2PA peer after sending a status "In Service" or status "Processor Outage"
message.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              |  T4(Pn)     7.5 <= T4 <= 9.5       |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                              !                                    |
|                              !  T1         40.0 <= T1 <- 50.0     |
|                              !                                    |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(T1)    |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T1 & Timer T4 (Normal)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T1 & Timer T4 (Normal)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both the PT and the IUT in the "Out of Service" state.
.np
The Level 3 "Start" command is issued at the IUT.
.np
Check that the IUT sends a status "Alignment" message.
.np
Send a status "Alignment" message to the IUT and exchange status "Proving
Normal" and proving data messages.
.np
Check that a status "In Service" message is received from the IUT within time
T4.
.np
Check that T4 is between 7.5 seconds and 9.5 seconds in duration.
.np
Check that a status "Out of Service" message is received from the IUT within
time T1 and that an "Out of Service" indication is given to Level 3 at the
IUT with reason "T1 Timeout".
.np
Check that T1 is between 40.0 seconds and 50.0 seconds in duration.

.bp
.sh 3 "Normal alignment procedure"
.lp
This test case validates the normal alignment procedure at the IUT.  This is a
normal successful alignment procedure which results in the link going to and
staying in the "In Service" state.
.sh 4 "Forward Direction"
.lp
The test is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 1.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 2
\fIFigure \n($1.\n($2.\n($3(a).\fR  Normal alignment procedure
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Normal alignment procedure
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link "Out of Service".
.np
The Level 3 "Start" command is issued at the IUT and the PT.
.np
Check that the IUT sends the message sequence illustrated in
\fIFigure \n($1.\n($2.\n($3(a)\fR.
.np
Check that the IUT sends a status "In Service" message and indicates "In
Service" to Level 3.
.np
Check that the link maintains the "In Service" state.

.bp
.sh 4 "Reverse Direction"
.lp
The equivalent Q.781 test case is normally repeated with with 2-byte LSSUs
instead of 1-byte LSSUs when testing Q.703 links.  Because M2PA does not have
one- and two-byte LSSUs (there is just the status message), this test is not
applicable.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 2
\fIFigure \n($1.\n($2.\n($3(b).\fR  Normal alignment procedure
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Normal alignment procedure
.)x
.)b
.ip "Test Description:" 12
.np
Not applicable.

.bp
.sh 3 "Normal alignment procedure - correct procedure (Data)"
.lp
The test case validates the normal alignment procedure at the IUT when a DATA
message is used instead of a status "In Service" to complete the alignment
procedure.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.6
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|                  DATA  ----------------->                         |
|                        <-----------------  ACK [    1 msgs]       |
|                                            !in service            |
|                                            !msu                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Normal alignment procedure (Data)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Normal alignment procedure (Data)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link "Out of Service".
.np
The Level 3 "Start" command is issued at the IUT and the PT.
.np
Check that the IUT sends the message sequence illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
Check that the IUT sends a status "In Service" message and indicates "In
Service" to Level 3.
.np
Check that the IUT acknowledges the Data message with an Ack message.
.np
The IUT should maintain the "In Service" state.

.bp
.sh 3 "Status ""Alignment"" received during normal proving period"
.lp
This test case validates that the IUT restarts the alignment and proving
procedure when receiving a status "Alignment" message in the "Proving" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.7
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        -----timeout------                         |
|             ALIGNMENT  ----------------->                         |
|                              !                                    |
|                              !  T4(Pn)     7.5 <= T4 <= 9.5       |
|                              !                                    |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 2
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" during normal proving
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" during normal proving
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT and the PT.
.np
When normal proving begins, wait for half the duration of T4 and
then send the IUT a status "Alignment" message.
.np
Check that the IUT restarts the proving period and sends a status
"In Service" message T4 after the last status "Alignment" message was sent to
the IUT.
.np
Check that T4(Pn) is between 7.5 seconds and 9.5 seconds in duration.

.bp
.sh 3 "Normal alignment with PO set"
.lp
This case tests the normal alignment procedure where one M2PA peer is
experiencing a local processor outage before and during alignment.  The M2PA
peers should still align and the link should go into service at Level 3.
.sh 4 "Forward Direction"
.lp
The test is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 1.8
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Normal alignment with PO set
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Normal alignment with PO set
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the IUT
and the "Start" command at the PT.
.np
Check that the IUT sends the message sequence illustrated in
\fIFigure \n($1.\n($2.\n($3(a)\fR.
.np
Check that the IUT sends status "Processor Outage" message and indicates "In
Service" to Level 3.
.np
Check that the link maintains the "In Service" state at the IUT.

.bp
.sh 4 "Reverse Direction"
.lp
This case is the same test in the reverse direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 1.8
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|              :set lpo                                             |
|                :start                                             |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            !rpo                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Normal alignment with PO set
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Normal alignment with PO set
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Local Processor Outage" and "Start" command at the PT and
the "Start" command at the IUT.
.np
Check that the IUT sends the message sequence illustrated in
\fIFigure \n($1.\n($2.\n($3(b).
.np
Check that the IUT sends status "In Service" message and indicates "Remote
Processor Outage" indication to Level 3.
.np
Check that the link maintains the "In Service" state at the IUT.

.bp
.sh 3 "Normal alignment with PO set (Data)"
.lp
This test case validates the normal alignment procedure at the IUT in the
"Processor Outage" state when a Data message is used instead of an "In
Service" message to complete the alignment procedure.
.sh 4 "Forward Direction"
.lp
The test is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference: Q.781/Test 1.9
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                  DATA  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Normal alignment with PO set (Data)
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Normal alignment with PO set (Data)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the
IUT.
.np
Check that the IUT sends the message sequence illustrated in
\fIFigure \n($1.\n($2.\n($3(a)\fR.
.np
Check that the IUT sends status "Processor Outage" message and send a Data
message to the IUT to complete the alignment procedure.
.np
Check that the IUT does not acknowledge the Data message.
.np
Check that the IUT maintains the "Processor Outage" state.

.bp
.sh 4 "Reverse Direction"
.lp
This is the same test in the reverse direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 1.9
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|              :set lpo                                             |
|                :start                                             |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|                                            :msu                   |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  DATA [   35 bytes]     |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            !rpo                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Normal alignment with PO set (Data)
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Normal alignment with PO set (Data)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the PT
and the "Start" command at the IUT.
.np
Provide an MSU for transmission at the IUT before the proving period ends.
.np
Check that the IUT sends the message sequence illustrated in
\fIFigure \n($1.\n($2.\n($3(b)\fR.
.np
Check that the IUT completes the proving process with the MSU and indicates
"Remote Processor Outage" to Level 3.
.np
Check that the IUT maintains the "Processor Outage" state and does not require
acknowledgment of the Data message used to complete alignment.

.bp
.sh 3 "Normal alignment with PO set and cleared"
.lp
This case tests that if the local processor outage condition is set and
cleared before the alignment procedure starts that normal alignment is
performed and no status "Processor Outage" message is sent to the M2PA peer.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference: Q.781/Test 1.10
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :clear lpo             |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Normal alignment with PO set and cleared
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Normal alignment with PO set and cleared
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage," "Clear Local Processor Outage"
and "Start" commands at the IUT and "Start" command at the PT.
.np
Check that the sequence of events follows that illustrated
in \fIFigure \n($1.\n($2.\n($3\fR.
.np
Check that the IUT completes the alignment procedure and sends the status "In
Service" message and indicates "In Service" to Level 3.

.bp
.sh 3 "Set RPO when ""Aligned not ready"""
.lp
This test case validates the behavior of the IUT when processor outage
condition is set at both the PT and the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.11
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|              :set lpo                                             |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            !rpo                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set RPO when "Aligned Not Ready"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set RPO when "Aligned Not Ready"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the IUT
and PT.
.np
Check that the alignment procedure follows the sequence of events illustrated
in \fIFigure \n($1.\n($2.\n($3\fR.
.np
Check that the IUT sends status "Processor Outage" and indicates "Remote
Processor Outage" to Level 3.

.bp
.sh 3 "Status ""Out of Service"" received when ""Aligned not ready"""
.lp
These test cases validate the behavior of the IUT when it receives a status
"Out of Service" message in the "Aligned Not Ready" state or sends a Status
"Out of Service" message when the M2PA peer is in the "Aligned Not Ready"
state.
.sh 4 "Forward Direction"
.lp
The test is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 1.12
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                 :stop                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(SIOS)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  "Out of Service" when "Aligned not ready"
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  "Out of Service" when "Aligned not ready"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the IUT
and the "Start" command at the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
Check that the IUT sends a status "Processor Outage" message when it completes
the initial alignment procedure and issue a Level 3 "Stop" command at the PT.
.np
Check that the IUT sends status "Out of Service" and indicates "Out of
Service" to Level 3 with the reason "Received SIOS".

.bp
.sh 4 "Reverse Direction"
.lp
The test is repeated in the reverse direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 1.12
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|              :set lpo                                             |
|                :start                                             |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|                                            :stop                  |
|            IN-SERVICE  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  "Out of Service" when "Aligned not ready"
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  "Out of Service" when "Aligned not ready"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT and the PT.
.np
Check that the sequence of events follows those illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT goes to the "In Service" state, issue the Level 3 "Stop" command
at the IUT.
.np
Check that the IUT sends the status "Out of Service" message.

.bp
.sh 3 "Status ""Alignment"" received when ""Aligned not ready"""
.lp
This test case validates the behavior of the IUT when it receives a status
"Alignment" message in the "Aligned Not Ready" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.13
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(SIO)   |
|        OUT-OF-SERVICE  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" when "Aligned not ready"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" when "Aligned not ready"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the
IUT and "Start" command at the PT.
.np
Check that the sequence of events follows the normal alignment procedure
illustrated in \fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT sends the status "Processor Outage" message, send a status
"Alignment" message to the IUT.
.np
Check that the IUT sends the status "Out of Service" message and indicates
"Out of Service" to Level 3 with reason "Received SIO".

.bp
.sh 3 "Set and clear LPO when ""Initial alignment"""
.lp
This test case validates the behavior of the IUT when it receives Level 3 "Set
Local Processor Outage" and "Clear Local Processor Outage" commands in the
"Initial Alignment" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.14
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|                                            :set lpo               |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                                            :clear lpo             |
|                        <-----------------  IN-SERVICE             |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set and clear LPO when "Initial Alignment"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set and clear LPO when "Initial Alignment"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT and PT.
.np
Issue the Level 3 "Set Local Processor Outage" command at the IUT when the IUT
begins initial alignment.
.np
Issue the Level 3 "Clear Local Processor Outage" command at the IUT before the
IUT completes initial alignment.
.np
Check that the IUT sends the status "In Service" message when it completes
initial alignment and that the "In Service" indication is given to Level 3 at
the IUT.

.bp
.sh 3 "Set and clear LPO when ""Aligned ready"""
.lp
This test case validates the behavior of the IUT when it receives the Level 3
"Set Local Processor Outage" and "Clear Local Processor Outage" commands in
the "Aligned Ready" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.15
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|                                            :set lpo               |
|            IN-SERVICE  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                                            !in service            |
|                                            :clear lpo             |
|                        <-----------------  PROCESSOR-OUTAGE-ENDED |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set and clear LPO when "Aligned ready"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set and clear LPO when "Aligned ready"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at both the IUT and the PT.
.np
Check that the IUT follows the normal alignment procedure and sequence of
events illustrated in \fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT has completed the initial alignment procedure, issues the Level 3
"Set Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage" message and indicates "In
Service" to Level 3 at the IUT.
.np
Issue the Level 3 "Clear Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage Ended" message and enters
the "In Service" state.

.bp
.sh 3 "Timer T1 in ""Aligned not ready"" state"
.lp
This test case validates the T1 timer and procedures at the IUT when the IUT
is in the "Aligned Not Ready" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.16
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                              !                                    |
|                              !  T1         40.0 <= T1 <= 50.0     |
|                              !                                    |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(T1)    |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T1 in "Aligned not ready" state
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T1 in "Aligned not ready" state
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the IUT
and "Start" command at the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n($1.\n($2.\n($3\fR while completing the initial alignment
procedure.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 with reason "T1 Timeout".
.np
Check that T1 is between 40.0 seconds and 50.0 seconds in duration.

.bp
.sh 3 "No status ""Alignment"" sent during normal proving period"
.lp
This test validates that the normal alignment procedure completes at the IUT
when no status "Alignment" message is sent.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.17
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|               PROVING  ----------------->                         |
|                        <-----------------  PROVING                |
|                              !                                    |
|                              !  T3+T4(Pn)  7.5 <= T3+T4 <= 11.0   |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  No "Alignment" during normal proving period
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  No "Alignment" during normal proving period
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at both the IUT and the PT.
.np
Respond to status "Alignment" message sent by the IUT with a status "Proving
Normal" message and continue proving.
.np
Check that the IUT sends a status "In Service" message within T4(Pn) plus T3.
.np
Check that the delay from the start of the proving period to the status
"In Service" message T4(Pn)+T3 is between 7.5 seconds and 11.0 seconds in
duration.

.bp
.sh 3 "Set and cease emergency prior to ""start alignment"""
.lp
This test case validates the behavior of the IUT when the Level 3 "Set
Emergency" and "Clear Emergency" commands are issued prior to the Level 3
"Start" command at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.18
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set emergency         |
|                                            :clear emergency       |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              !  T4(Pn)     7.5 <= T4 <= 10.0      |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Toggle emergency before "start alignment"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Toggle emergency before "start alignment"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Emergency," "Clear Emergency" then "Start" commands at
the IUT and "Start" command at the PT.
.np
Check that the sequence of events are as illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.  Check that the IUT sends a status "Proving
Normal" message in response to the "Alignment" message.
.np
Check that the IUT sends a status "In Service" message.
.np
Check that the IUT uses a normal proving period by timing the delay from the
status "Proving Normal" message to the status "In Service" message sent by the
IUT.
.np
Check that T4 is between 7.5 seconds and 10.0 seconds in duration.

.bp
.sh 3 "Set emergency while in ""not aligned"" state"
.lp
This test case validates the behavior of the IUT when the Level 3 "Set
Emergency" command is issued at the IUT immediately after the Level 3 "Start"
command (when the IUT is in the "Not Aligned" state).
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.19
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                                            :set emergency         |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-EMERGENCY      |
|     PROVING-EMERGENCY  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              !  T4(Pe)     0.4 <= T4 <= 0.6       |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set emergency in "not aligned" state
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set emergency in "not aligned" state
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" and "Set Emergency" commands at the IUT and "Start"
command at the PT.
.np
Check that the sequence of events are as illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.  Check that the IUT sends a status "Proving
Emergency" message in response to the "Alignment" message.
.np
Check that the IUT sends a status "In Service" message.
.np
Check that the IUT uses an emergency proving period by timing the delay from
the status "Proving Emergency" message to the status "In Service" message sent
by the IUT.
.np
Check that T4 is between 0.4 seconds and 0.6 seconds in duration.

.bp
.sh 3 "Set emergency when ""aligned"""
.lp
This test case validates the response of the IUT to the Level 3 "Set
Emergency" command when issued in the "Aligned" state at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.20
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                                            :set emergency         |
|                        <-----------------  PROVING-EMERGENCY      |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              !  T4(Pe)     0.4 <= T4 <= 0.6       |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set emergency when "aligned"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set emergency when "aligned"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT and the PT.
.np
Check that the normal alignment procedure starts as illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
Before the normal proving period completes, issue the Level 3 "Set Emergency"
command at the ITU.
.np
Check that the IUT sends a status "Proving Emergency" message and later
follows with a status "In Service" message.
.np
Check that the IUT begins an emergency proving period by timing the delay from
the status "Proving Emergency" message to the status "In Service" message.
.np
Check that T4 is between 0.4 seconds and 0.6 seconds in duration.

.bp
.sh 3 "Both ends set emergency."
.lp
This test case validates the IUT behavior when the Level 3 "Set Emergency"
command is issued at both ends of the link before the Level 3 "Start" command.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.21
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set emergency         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-EMERGENCY      |
|     PROVING-EMERGENCY  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              !  T4(Pe)     0.4 <= T4 <= 0.6       |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Both ends set emergency
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Both ends set emergency
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Emergency" and "Start" commands at the IUT and the
"Start" command at the PT.
.np
Check that the IUT starts the emergency alignment procedure by sending a
status "Proving Emergency" message.
.np
Check that the IUT follows the sequence of events as illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.  Check that the IUT completes the alignment
procedure and sends a status "In Service" message.
.np
Check that the IUT uses an emergency proving period by timing the delay
between sending the status "Proving Normal" message and the status "In
Service" message.
.np
Check that T4 is between 0.4 seconds and 0.6 seconds in duration.

.bp
.sh 3 "Individual end sets emergency"
.lp
This test case validates the behavior of the IUT when emergency is
individually set at the PT before the initial alignment procedure begins.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.22
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|            :set emerg                                             |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|     PROVING-EMERGENCY  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              !  T4(Pe)     0.4 <= T4 <= 0.6       |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Individual end sets emergency
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Individual end sets emergency
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Emergency" and "Start" commands at the PT and the
"Start" command at the IUT.
.np
Check that the sequence of events follows that illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
Check that the IUT uses the emergency proving period by timing the delay
between the status "Proving Normal" message and the status "In Service"
message.
.np
Check that T4 is between 0.4 seconds and 0.6 seconds in duration.

.bp
.sh 3 "Set emergency during normal proving"
.lp
This test case validates the IUT behavior when it receives a Level 3 "Set
Emergency" command after it has already commenced normal proving.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.23
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                                            :set emergency         |
|                        <-----------------  PROVING-EMERGENCY      |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              !  T4(Pe)     0.4 <= T4 <= 0.6       |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set emergency during normal proving
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set emergency during normal proving
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT and the PT.
.np
Check that the sequence of events follows that illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
Before the normal proving period completes at the IUT, issue the Level 3 "Set
Emergency" command at the IUT.
.np
Check that the IUT sends a status "Proving Emergency" message and continues
proving.
.np
Check that the IUT sends a status "In Service" message.
.np
Check that the IUT uses an emergency proving period by timing the delay
between the status "Proving Emergency" message and the status "In Service"
message.
.np
Check that T4 is between 0.4 seconds and 0.6 seconds in duration.

.bp
.sh 3 "No status ""Alignment"" sent during emergency alignment"
.lp
This test case validates the response of the IUT to receiving a status "Proving
Normal" without a status "Alignment" during initial alignment using an
emergency proving period.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.24
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set emergency         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|     PROVING-EMERGENCY  ----------------->                         |
|                        <-----------------  PROVING-EMERGENCY      |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                              !                                    |
|                              !  T4(Pe)     0.4 <= T4 <= 0.6       |
|                              !                                    |
|                        <-----------------  IN-SERVICE             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  No "Alignment" during emergency alignment
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  No "Alignment" during emergency alignment
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Emergency" and "Start" commands at both the IUT and PT.
.np
Check that the IUT sends a status "Proving Emergency" message and starts
proving.
.np
Check that the IUT completes proving and sends a status "In Service" message.
.np
Check that the IUT uses an emergency proving period by timing the delay
between the status "Proving Emergency" message and the status "In Service"
message.
.np
Check that T4 is between 0.4 seconds and 0.6 seconds in duration.

.bp
.sh 3 "Deactivation during initial alignment"
.lp
This test case validates the behavior of the IUT in response to the Level 3
"Stop" command issued during the "Initial Alignment" state at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.25
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                        -----timeout------                         |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Deactivate during initial alignment
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Deactivate during initial alignment
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT.
.np
Before timer T2 expires, issue the Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends a status "Out of Service" message and stays in the
"Out of Service" state.

.bp
.sh 3 "Deactivation during aligned state"
.lp
This test case validates the behavior of the IUT in response to the Level 3
"Stop" command issued during "Aligned" state at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.26
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Deactivate during aligned state
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Deactivate during aligned state
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT and the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
Issue the Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends a status "Out of Service" message and stays in the
"Out of Service" state.

.bp
.sh 3 "Deactivation during aligned not ready"
.lp
This test case validates the behavior of the IUT in response to the Level 3
"Stop" command issued during the "Aligned Not Ready" state at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.27
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Deactivate during aligned not ready
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Deactivate during aligned not ready
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the IUT
and the "Start" command at the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n$(1.\n$(2.\n$(3\fR and sends a status "Processor Outage" message.
.np
Issue the Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends a status "Out of Service" message and stays in the
"Out of Service" state.

.bp
.sh 3 "Status ""alignment"" received during link in service"
.lp
This test case validates the IUT response to receiving a status "Alignment"
message in the "In Service" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.28
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(SIO)   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" during link in service
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" during link in service
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Send a status "Alignment" to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 with reason "Received SIO".

.bp
.sh 3 "Status ""out of service"" received during link in service"
.lp
This test case validates the response of the IUT to sending or receiving a
status "Out of Service" message in the "In Service" state.
.sh 4 "Forward Direction"
.lp
The test case is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.29
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                 :stop                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(SIOS)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Out of service" during link in service
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Out of service" during link in service
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue the Level 3 "Stop" command at the PT and send a status "Out of Service"
message to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to the Level 3 at the IUT with reason "Received SIOS".

.bp
.sh 4 "Reverse Direction"
.lp
The test case is repeated in the reverse direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.29
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Out of service" during link in service
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Out of service" during link in service
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue the Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends a status "Out of Service" message and stays in the
"Out of Service" state.

.bp
.sh 3 "Deactivation during LPO"
.lp
These test cases validate the response of the IUT to sending a status "Out
of Service" message while in the "Processor Outage" state with LPO set, or
receiving an "Out of Service" message from an M2PA peer in the "Processor
Outage" state with RPO set.
.sh 4 "Forward Direction"
.lp
The test is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 1.30
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :set lpo               |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Deactivation during LPO
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Deactivation during LPO
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage" message.
.np
Issue the Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends a status "Out of Service" message and stays in the
"Out of Service" state.

.bp
.sh 4 "Reverse Direction"
.lp
The test is repeated in the reverse direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 1.30
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|              :set lpo                                             |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                 :stop                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !rpo                   |
|                                            !out of service(SIOS)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Deactivation during LPO
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Deactivation during LPO
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Stop" commands at the PT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Received SIOS".

.bp
.sh 3 "Deactivation during RPO"
.lp
These test cases validate the response of the IUT to sending a status "Out of
Service" message while in the "Processor Outage" state with RPO set, or
receiving an "Out of Service" message from an M2PA peer in the "Processor
Outage" state with LPO set.
.sh 4 "Forward Direction"
.lp
The test is performed in the forward direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 1.31
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Deactivation during RPO
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Deactivation during RPO
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" command at the PT and send a
status "Processor Outage" message to the IUT.
.np
Issue the Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends the status "Out of Service" message and remains in
the "Out of Service" state.

.bp
.sh 4 "Reverse Direction"
.lp
The test is repeated in the reverse direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 1.31
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :set lpo               |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                 :stop                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Deactivation during RPO
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Deactivation during RPO
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage" message.
.np
Issue the Level 3 "Stop" command at the PT and send the status "Out of
Service" message.
.np
Check that the IUT does not indicate "Out of Service" until the local
processor outage condition recovers.

.bp
.sh 3 "Deactivation during the proving period"
.lp
These test cases validate the response of the IUT to deactivation (sending or
receiving a status "Out of Service" message) during the proving period.
.sh 4 "Forward Direction"
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 1.32
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                 :stop                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(AERM)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Deactivation during the proving period
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Deactivation during the proving period
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the IUT and the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
During the proving period, issue the Level 3 "Stop" command at the PT and send
status "Out of Service" to the ITU.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Alignment Not Possible".

.bp
.sh 4 "Reverse Direction"
.lp
The test is repeated in the reverse direction.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 1.32
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|        OUT-OF-SERVICE  ----------------->                         |
|                :start                                             |
|                                            :start                 |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                        <-----------------  ALIGNMENT              |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|               PROVING  ----------------->                         |
|                        <-----------------  PROVING                |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Deactivation during the proving period
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Deactivation during the proving period
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue the Level 3 "Start" command at the PT and the IUT.
.np
Check that the sequence of events follows that illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
During the proving period, issue a Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends a status "Out of Service" message and remains in the
"Out of Service" state.

.bp
.sh 3 "Status ""Alignment"" received instead of status ""In Service"""
.lp
This test case validates the response of the IUT to receiving a status
"Alignment" message instead of a status "In Service" or "Processor Outage"
message at the completion of initial alignment.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.33
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(SIO)   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" instead of "In Service"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Alignment" instead of "In Service"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue a Level 3 "Start" command at the IUT and the PT.
.np
Check that the sequence of events follows that illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT sends a status "In Service" message, send a status "Alignment"
message to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Received SIO".

.bp
.sh 3 "Status ""Out of Service"" received instead of status ""In Service"""
.lp
This test case validates the response of the IUT to receiving a status "Out of
Service" message instead of a status "In Service" or "Processor Outage"
message at the completion of initial alignment.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.34
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|                 :stop                                             |
|        OUT-OF-SERVICE  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(SIOS)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Out of Service" instead of "In Service"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Out of Service" instead of "In Service"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue a Level 3 "Start" command at the IUT and the PT.
.np
Check that the sequence of events follows that illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT sends a status "In Service" message, send a status "Out of
Service" message to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Received SIOS".

.bp
.sh 3 "Status ""Processor Outage"" received instead of ""In Service"""
.lp
This test case validates the response of the IUT to receiving a status
"Processor Outage" message instead of a status "In Service" message at the
completion of initial alignment.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 1.35
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|              :set lpo                                             |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            !rpo                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Processor Outage" instead of "In Service"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  "Processor Outage" instead of "In Service"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "Out of Service" state.
.np
Issue a Level 3 "Start" command at the IUT and the PT.
.np
Check that the sequence of events follows that illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT sends a status "In Service" message, issue a Level 3 "Set Local
Processor Outage" command at the PT and send a status "Processor Outage"
message to the IUT.
.np
Check that the IUT indicates "Remote Processor Outage" to Level 3 at the IUT.

.bp
.sh 2 "Link State Control - Unexpected signal units/orders"
.lp
This suite of test cases test the response of the Implementation Under Test to
unexpected sequences Level 3 requests and received M2PA messages in various
states.  These test cases validates the robustness of the implementation
in responding to unusual circumstances.
.sh 3 "Unexpected signal units/orders in ""Out of service"" state"
.lp
This case validates the response of the IUT to the receipt of unexpected Level
3 requests and receipt of unexpected M2PA messages while in the "Out of
Service" state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|             ALIGNMENT  ----------------->                         |
|        PROVING-NORMAL  ----------------->                         |
|     PROVING-EMERGENCY  ----------------->                         |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                  BUSY  ----------------->                         |
|      [INVALID-STATUS]  ----------------->                         |
|PROCESSOR-OUTAGE-ENDED  ----------------->                         |
|            IN-SERVICE  ----------------->                         |
|            BUSY-ENDED  ----------------->                         |
|                  DATA  ----------------->                         |
|                                            :stop                  |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 2
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events in the
"Out of Service" State
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events in the
"Out of Service" State
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both M2PA peers in the "Out of Service" state.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status "Out of Service"
- Status "Alignment"
- Status "Proving Normal"
- Status "Proving Emergency"
- Status "Processor Outage"
- Status "Busy"
- Status Invalid
- Status "Processor Outage Ended"
- Status "Busy Ended"
- Status "In Service"
- Data
.)l

.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Stop" command
.)l

.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
The Level 3 "Start" command is then issued.
.np
Check that the link aligns normally.
.np
Check that link alignment uses normal alignment procedures.
.np
Check that the link goes in service and stays in service without local or
remote processor outage indications to Level 3.

.bp
.sh 3 "Unexpected signal units/orders in ""Not Aligned"" state"
.lp
This test case validates the response of the IUT to the receipt of unexpected Level
3 requests and receipt of unexpected M2PA messages while in the "Not Aligned"
state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|        OUT-OF-SERVICE  ----------------->                         |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                  BUSY  ----------------->                         |
|      [INVALID-STATUS]  ----------------->                         |
|            IN-SERVICE  ----------------->                         |
|                  DATA  ----------------->                         |
|                                            :clear emergency       |
|                                            :start                 |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "not aligned"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "not aligned"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both M2PA peers in the "Out of Service" state.
.np
The Level 3 "Start" command is issued to IUT to place the IUT in the "Not
Aligned" state.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status "Out of Service"
- Status "Processor Outage"
- Status "Busy"
- Status Invalid
- Status "In Service"
- Data
.)l

.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Clear Emergency" command
- Level 3 "Start" command
.)l

.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
A status "Alignment" is then sent to the IUT.
.np
Check that the IUT aligns as usual and performs the normal alignment
procedures.
.np
Check that the IUT places the link in service and that no local or remote
processor outage indications are given to Level 3 at the IUT.

.bp
.sh 3 "Unexpected signal units/orders in ""Aligned"" state"
.lp
This case validates the response of the IUT to the receipt of unexpected Level
3 request and receipt of unexpected M2PA messages while in the "Aligned"
state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|             ALIGNMENT  ----------------->                         |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                  BUSY  ----------------->                         |
|      [INVALID-STATUS]  ----------------->                         |
|            IN-SERVICE  ----------------->                         |
|PROCESSOR-OUTAGE-ENDED  ----------------->                         |
|            BUSY-ENDED  ----------------->                         |
|                  DATA  ----------------->                         |
|                                            :clear emergency       |
|                                            :start                 |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "aligned"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "aligned"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "Out of Service" state.
.np
The IUT is brought to the "Aligned" state using normal procedures.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status "Alignment"
- Status "Processor Outage"
- Status "Busy"
- Status Invalid
- Status "In Service"
- Status "Processor Outage Ended"
- Status "Busy Ended"
- Data
.)l

.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Clear Emergency" command
- Level 3 "Start" command
.)l

.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
Check that the IUT aligns as usual and performs the normal alignment
procedure.
.np
Check that the IUT places the link in service and that no local or remote
processor outage indications are given to Level 3 at the IUT.

.bp
.sh 3 "Unexpected signal units/orders in ""Proving"" state"
.lp
This case validates the response of the IUT to the receipt of unexpected Level
3 request and receipt of unexpected M2PA messages while in the
"Proving" state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|PROCESSOR-OUTAGE-ENDED  ----------------->                         |
|      PROCESSOR-OUTAGE  ----------------->                         |
|            BUSY-ENDED  ----------------->                         |
|                  BUSY  ----------------->                         |
|      [INVALID-STATUS]  ----------------->                         |
|            IN-SERVICE  ----------------->                         |
|                  DATA  ----------------->                         |
|               PROVING  ----------------->                         |
|                                            :clear emergency       |
|                                            :start                 |
|                        <-----------------  IN-SERVICE             |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "proving"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "proving"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "Out of Service" state.
.np
The IUT is brought to the "Proving" state using normal procedures.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status "Processor Outage Ended"
- Status "Processor Outage"
- Status "Busy Ended"
- Status "Busy"
- Status Invalid
- Status "In Service"
- Data
.)l

.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Clear Emergency" command
- Level 3 "Start" command
.)l

.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
Check that the IUT aligns as usual and performs the normal alignment
procedure.
.np
Check that the IUT places the link in service and that no local or remote
processor outage indications are given to Level 3 at the IUT.
.bp
.sh 3 "Unexpected signal units/orders in ""Aligned Ready"" state"
.lp
This case validates the response of the IUT to the receipt of unexpected Level
3 request and receipt of unexpected M2PA messages while in the
"Aligned Ready" state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|                  BUSY  ----------------->                         |
|      [INVALID-STATUS]  ----------------->                         |
|                                            :set emergency         |
|                                            :clear emergency       |
|                                            :clear lpo             |
|                                            :start                 |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "aligned ready"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "aligned ready"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "Out of Service" state.
.np
The IUT is brought to the "Aligned Ready" state using normal procedures.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status "Busy"
- Status Invalid
.)l

.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Set Emergency" command
- Level 3 "Clear Emergency" command
- Level 3 "Clear Local Processor Outage" command
- Level 3 "Start" command
.)l

.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
Check that the IUT aligns as usual and performs the normal alignment
procedure.
.np
Check that the IUT places the link in service and that no local or remote
processor outage indications are given to Level 3 at the IUT.
.bp
.sh 3 "Unexpected signal units/orders in ""Aligned Not Ready"" state"
.lp
This case validates the response of the IUT to the receipt of unexpected Level
3 request and receipt of unexpected M2PA messages while in the
"Aligned Not Ready" state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.6
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                  BUSY  ----------------->                         |
|      [INVALID-STATUS]  ----------------->                         |
|                                            :set emergency         |
|                                            :clear emergency       |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|            IN-SERVICE  ----------------->                         |
|                                            !in service            |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "aligned not ready"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "aligned not ready"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "Out of Service" state.
.np
The IUT is brought to the "Aligned Not Ready" state using normal procedures.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status "Busy"
- Status Invalid
.)l

.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Set Emergency" command
- Level 3 "Clear Emergency" command
- Level 3 "Set Local Processor Outage" command
- Level 3 "Start" command
.)l

.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
Check that the IUT places the link in service.
.bp
.sh 3 "Unexpected signal units/orders in ""In Service"" state"
.lp
This case validates the response of the IUT to the receipt of unexpected Level
3 request and receipt of unexpected M2PA messages while in the
"In Service" state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.7
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|      [INVALID-STATUS]  ----------------->                         |
|                                            :set emergency         |
|                                            :clear emergency       |
|                                            :clear lpo             |
|                                            :start                 |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "in service"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "in service"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "In Service" state.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status Invalid
.)l

.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Set Emergency" command
- Level 3 "Clear Emergency" command
- Level 3 "Clear Local Processor Outage" command
- Level 3 "Start" command
.)l

.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
Check that the IUT retains the link in the in service state and that no local
or remote processor outage indications are given to Level 3 at the IUT.
.bp
.sh 3 "Unexpected signal units/orders in ""Processor Outage"" state"
.lp
This case validates the response of the IUT to the receipt of unexpected Level
3 request and receipt of unexpected M2PA messages while in the
"Processor Outage" state.
All of the unexpected sequences in this test case must be ignored by the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 2.8
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :set lpo               |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                  BUSY  ----------------->                         |
|      [INVALID-STATUS]  ----------------->                         |
|                                            :set emergency         |
|                                            :clear emergency       |
|                                            :start                 |
|            IN-SERVICE  ----------------->                         |
|PROCESSOR-OUTAGE-ENDED  ----------------->                         |
|            BUSY-ENDED  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "processor outage"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Unexpected events while "processor outage"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "In Service" state.
.np
The IUT is brought to the "Processor Outage" state using normal procedures.
.np
A sequence of unexpected M2PA messages are sent to the IUT.  These unexpected
messages are:

.(l I
- Status "Busy"
- Status Invalid
- Status "In Service"
- Status "Processor Outage Ended"
- Status "Busy Ended"
.)l
.np
A sequence of unexpected Level 3 commands are issued at the IUT.  These
unexpected Level 3 commands are:

.(l I
- Level 3 "Set Emergency" command
- Level 3 "Clear Emergency" command
- Level 3 "Start" command
.)l
.np
Check that the IUT ignores the unexpected M2PA messages/Level 3 commands.
.np
Check that the IUT keeps the link in service and that no local or remote
processor outage indications are given to Level 3 at the IUT.
.bp
.sh 2 "Transmission Failure"
.lp
This set of test cases validate specific transmission path failures and
anomalies.  Specifically transmission path failures, corrupt acknowledgments
and invalid sequencing.  Because SCTP does not have a transmission path that
is separate from a receive path, the Q.781 tests that validate response to
breaking the transmission path are simulated by aborting the association.
Because M2PA does not have forward sequence numbers, the Q.781 tests that
validate response to abnormal forward sequence numbers are not applicable.
Because M2PA does not have forward indicator bits, the Q.781 tests that
validate response to abnormal forward indicator bits are simulated by invalid
Ack messages.
.sh 3 "Link aligned ready (Abort)"
.lp
This case validates the response of the IUT to aborting the SCTP association
when the IUT is in the "Aligned Ready" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  IN-SERVICE             |
|             :tx break                                             |
|                                            !out of service(SUERM) |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned ready (Abort)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned ready (Abort)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "Out of Service" state.
.np
Issue a Level 3 "Start" command at the IUT and the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT sends a status "In Service" message, abort the SCTP association.
.np
Check that the IUT indicates "Out of Service" to Level 3 at the IUT with
reason "Excessive error rate SUERM" and stays in the "Out of Service" state.

.bp
.sh 3 "Link aligned ready (Invalid Acks)"
.lp
This test case validates the response of the IUT to receiving two consecutive
invalid Ack messages in the "Aligned Ready" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                   ACK  ----------------->                         |
|                   ACK  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(FIBR)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned ready (Invalid Acks)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned ready (Invalid Acks)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both IUT and PT in the "Out of Service" state.
.np
Send two consecutive Ack messages to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Abnormal FIBR" and stays in the
"Out of Service" state.

.bp
.sh 3 "Link aligned not ready (Abort)"
.lp
This test case validates the response of the IUT to aborting the SCTP
association when the IUT is in the "Aligned Not Ready" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|             :tx break                                             |
|                                            !out of service(SUERM) |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned not ready (Abort)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned not ready (Abort)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both  PT and IUT in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the
IUT and the "Start" command at the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT sends a status "Processor Outage" message, abort the SCTP
association.
.np
Check that the IUT indicates "Out of Service" to Level 3 at the IUT with
reason "Excessive Error Rate/SUERM" and stays in the "Out of Service" state.

.bp
.sh 3 "Link aligned not ready (Invalid Acks)"
.lp
This test case validates the response of the IUT to the receipt of two
consecutive invalid Ack messages in the "Aligned Not Ready" state.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                        <-----------------  OUT-OF-SERVICE         |
|        OUT-OF-SERVICE  ----------------->                         |
|                                            :set lpo               |
|                                            :start                 |
|                        <-----------------  ALIGNMENT              |
|                :start                                             |
|             ALIGNMENT  ----------------->                         |
|                        <-----------------  PROVING-NORMAL         |
|        PROVING-NORMAL  ----------------->                         |
|                        <-----------------  PROVING                |
|               PROVING  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                   ACK  ----------------->                         |
|                   ACK  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(FIBR)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned not ready (Invalid Acks)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link aligned not ready (Invalid Acks)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with both PT and IUT in the "Out of Service" state.
.np
Issue the Level 3 "Set Local Processor Outage" and "Start" commands at the IUT
and the "Start" command at the PT.
.np
Check that the IUT follows the sequence of events illustrated in
\fIFigure \n($1.\n($2.\n($3\fR.
.np
When the IUT sends a status "Processor Outage" message, send two consecutive
invalid Ack messages to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Abnormal FIBR" and remains in
the "Out of Service" state.

.bp
.sh 3 "Link in service (Abort)"
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|             :tx break                                             |
|                                            !out of service(SUERM) |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in service (Abort)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in service (Abort)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Abort the SCTP association.
.np
Check that the IUT indicates "Out of Service" to Level 3 at the IUT with
reason "Excessive Error Rate/SUERM" and stays in the "Out of Service" state.

.bp
.sh 3 "Link in service (Invalid Acks)"
.lp
This test case validates the response of the IUT to two consecutive invalid
Ack messages in the "In Service" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.6
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                   ACK  ----------------->                         |
|                   ACK  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(FIBR)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in service (Invalid Acks)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in service (Invalid Acks)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Send two consecutive invalid Ack messages to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Abnormal FIBR" and stays in the
"Out of Service" state.

.bp
.sh 3 "Link in processor outage (Abort)"
.lp
This test case validates the response of the IUT to aborting the SCTP
association when the IUT is in the "Processor Outage" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.7
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :set lpo               |
|                        <-----------------  PROCESSOR-OUTAGE       |
|             :tx break                                             |
|                                            !out of service(SUERM) |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in processor outage (Abort)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in processor outage (Abort)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issues the Level 3 "Set Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage" message.
.np
Abort the SCTP association.
.np
Check that the IUT indicates "Out of Service" to Level 3 at the IUT with
reason "Excessive Error Rate/SUERM" and stays in the "Out of Service" state.

.bp
.sh 3 "Link in processor outage (Invalid Acks)"
.lp
This test case validates the response of the IUT to receiving two consecutive
Invalid Ack messages while in the "Processor Outage" state.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 3.8
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                            :set lpo               |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                   ACK  ----------------->                         |
|                   ACK  ----------------->                         |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(FIBR)  |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in processor outage (Invalid Acks)
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Link in processor outage (Invalid Acks)
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issues a Level 3 "Set Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage" message.
.np
Send two consecutive invalid Ack messages to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "Abnormal FIBR" and stays in the
"Out of Service" state.

.bp
.sh 2 "Processor Outage Control"
.sh 3 "Set and clear LPO while link in service"
.lp
This test case validates the response of the IUT to a local processor outage
condition and recovery with buffer clearing.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 4.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :msu                   |
|                                            :msu                   |
|                        <-----------------  DATA [   35 bytes]     |
|                   ACK  ----------------->                         |
|                        <-----------------  DATA [   35 bytes]     |
|                                            :set lpo               |
|                  DATA  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE       |
|                                            :clear buffers         |
|                                            :msu                   |
|                                            :clear lpo             |
|                        <-----------------  DATA [   35 bytes]     |
|                   ACK  ----------------->                         |
|                        <-----------------  PROCESSOR-OUTAGE-ENDED |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set and clear LPO while link in service
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Set and clear LPO while link in service
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Send two MSUs from the IUT and then issue a Level 3 "Set Local Processor
Outage" command at the IUT.
.np
Check that the IUT sends two Data messages and a status "Processor Outage"
message.
.np
Acknowledge one data message with an Ack message at the PT and send a Data
message from the PT to the IUT.
.np
Check that the IUT sends a status "Processor Outage" message.
.np
Check that the IUT does not require an acknowledgments to the second Data
message by waiting longer than timer T7 at the IUT.
.np
At the IUT, issue a Level 3 "Clear Buffers" command, send an MSU, and then
issue a Level 3 "Clear Local Processor Outage".
.np
Check that the IUT sends a Data message and send an Ack message to the IUT in
response.
Check that the IUT sends a "Processor Outage Ended" message.
.np
To ensure that the IUT is not expecting another acknowledgments, wait for
longer than T7 and check that the IUT sends no further status messages and
remains in the "In Service" state.

.bp
.sh 3 "RPO during LPO"
.lp
This test case validates the response of the IUT to receiving a status
"Processor Outage" message and status "Processor Outage Ended" message while in
the "Processor Outage" state with LPO set at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 4.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                            :set lpo               |
|                        <-----------------  PROCESSOR-OUTAGE       |
|              set lpo:                                             |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            !rpo                   |
|            clear lpo:                                             |
|PROCESSOR-OUTAGE-ENDED  ----------------->                         |
|                                            !rpr                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  RPO during LPO
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  RPO during LPO
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue a Level 3 "Set Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage" message.
.np
Issue a Level 3 "Set Local Processor Outage" command at the PT and send a
status "Processor Outage" message to the IUT.
.np
Check that the IUT indicates "Remote Processor Outage" to Level 3 at the IUT.
.np
Issue a level 3 "Clear Local Processor Outage" command at the PT and send a
status "Processor Outage Ended" message to the IUT.
.np
Check that the IUT indicates "Remote Processor Recovered" to Level 3 at the
IUT.

.bp
.sh 3 "Clear LPO when ""Both processor outage"""
.lp
This test case validates the response of the IUT to the receipt of a Level 3
"Clear Local Processor Outage" command when the IUT is in the "Processor
Outage" state with both processors marked PO.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 4.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :set lpo               |
|                        <-----------------  PROCESSOR-OUTAGE       |
|              :set lpo                                             |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            !rpo                   |
|                                            :clear lpo             |
|                        <-----------------  PROCESSOR-OUTAGE-ENDED |
|            :clear lpo                                             |
|PROCESSOR-OUTAGE-ENDED  ----------------->                         |
|                                            !rpr                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Clear LPO when "Both processor outage"
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Clear LPO when "Both processor outage"
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Issue a Level 3 "Set Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Outage" message.
.np
Issue a Level 3 "Set Local Processor Outage" command at the PT and send a
status "Processor Outage" message to the IUT.
.np
Check that the ITU indicates "Remote Processor Outage" to Level 3 at the IUT.
.np
Issue a Level 3 "Clear Local Processor Outage" command at the IUT.
.np
Check that the IUT sends a status "Processor Ended" message.
.np
Issue a Level 3 "Clear Local Processor Outage" command at the PT and send a
status "Processor Outage Ended" message to the IUT.
.np
Check that the IUT indicates "Remote Processor Recovered" to Level 3 at the
IUT and remains in the "In Service" state.

.bp
.sh 2 "SU delimitation, alignment, error detection and correction"
.lp
Most of the test cases in this section are not applicable to M2PA operation.
.sh 3 "More than 7 ones between MSU opening and closing flags"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 5.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:" 12
.np
Not Applicable

.bp
.sh 3 "Greater than maximum signal unit length"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 5.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:" 12
.np
Not Applicable

.bp
.sh 3 "Below minimum signal unit length"
.lp
This test case validates the IUT response to a Data message with a payload
below the minimum MSU length.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 5.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|         1 byte   DATA  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Send a Data message with one byte of payload to the IUT.
.np
Check that the IUT does not acknowledge the Data message and remains in the
"In Service" state.

.bp
.sh 3 "Reception of single and multiple flags between FISUs"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 5.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 5.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Reception of single and multiple flags between MSUs"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(a)\fR.

.(b C
Reference:  Q.781/Test 5.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3(a).\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3(b)\fR.

.(b C
Reference:  Q.781/Test 5.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3(b).\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 2 "SUERM check"
.lp
The test cases in this section
are not applicable to M2PA.  These tests might have
corresponding tests at the SCTP layer, however, that is the topic of an SCTP
test specification rather than an M2PA test specification.
.sh 3 "Error rate of 1 in 256 - Link remains in service"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 6.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Error rate of 1 in 254 - Link out of service"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 6.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Consecutive corrupt SUs"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 6.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Time controlled break of the link"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 6.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 2 "AERM check"
.lp
The test cases in this section
are not applicable to M2PA.  These test might have corresponding test at the
SCTP layer, however, that is the topic of an SCTP test specification rather
than an M2PA test specification.
.sh 3 "Error rate below the normal threshold"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 7.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Error rate at the normal threshold"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 7.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Error rate above the normal threshold"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 7.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Error rate at the emergency threshold"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 7.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 2 "Transmission and reception control (Basic)"
.lp
A number of test cases in this section are not applicable to M2PA.  Some may
be the topic of a test specification for SCTP but are not applicable to M2PA.
Test cases that are applicable in this section validate the basic
transmission, reception and acknowledgments of Data messages with Ack
messages.
.sh 3 "MSU transmission and reception"
.lp
This test case validates the IUT response to the sending and receipt of Data
and Ack messages.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                  DATA  ----------------->                         |
|                        <-----------------  ACK [    1 msgs]       |
|                                            !msu                   |
|                                            :msu                   |
|                        <-----------------  DATA [   35 bytes]     |
|                   ACK  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Data transmission and reception
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Data transmission and reception
.)x
.)b
.ip "Test Description:" 12
.np
This test begins with the link in the "In Service" state.
.np
Send a Data message to the IUT.
.np
Check that the IUT sends an Ack message acknowledging the received Data
message and delivers the received MSU to Level 3 at the IUT.
.np
Issue a Level 3 MSU to the IUT.
.np
Check that the IUT sends a Data message.
.np
Send an Ack message to the IUT acknowledging the data message.
.np
Check that the IUT receives the acknowledgments by waiting longer than time T7
and ensuring that the IUT stays in the "In Service" state.

.bp
.sh 3 "Negative acknowledgments of an MSU"
.lp
M2PA does not perform negative acknowledgments at the M2PA layer.  Negative
acknowledgments are performed as necessary by the underlying SCTP transport.
As such, test cases involving negative acknowledgments are not applicable.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Check RTB full"
.lp
This test case validates the IUT response to an RTB full condition at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :msu                   |
|                                            :msu                   |
|                                            :msu                   |
|                                                    .              |
|                                                    .              |
|                                                    .              |
|                                                    Ct=  254       |
|                                                                   |
|                        <-----------------  DATA [   35 bytes]     |
|                        <-----------------  DATA [   35 bytes]     |
|                        <-----------------  DATA [   35 bytes]     |
|                                                    .              |
|                                                    .              |
|                                                    .              |
|                                                    Ct=  127       |
|                   ACK  ----------------->                         |
|                        <-----------------  DATA [   35 bytes]     |
|                        <-----------------  DATA [   35 bytes]     |
|                        <-----------------  DATA [   35 bytes]     |
|                                                    .              |
|                                                    .              |
|                                                    .              |
|                                                    Ct=  127       |
|                   ACK  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Check RTB full
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Check RTB full
.)x
.)b
.ip "Test Description:" 12
.np
This test begins with the link in the "In Service" state.
.np
Send 2 x N2 MSUs at the IUT.
.np
Check that the IUT sends N2 Data messages and then stops sending Data messages
(RTB Full condition).
.np
Acknowledge the N2 Data messages in a single Ack message.
.np
Check that the IUT sends another N2 Data messages.
.np
Acknowledge the N2 Data messages in a single Ack message.
.np
Check that the IUT remains in the "In Service" state longer than time T7.

.bp
.sh 3 "Single invalid Ack"
.lp
This test case validates the response of the IUT to a single invalid Ack
message.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                   ACK  ----------------->                         |
|                                            :msu                   |
|                        <-----------------  DATA [   35 bytes]     |
|                   ACK  ----------------->                         |
|                  DATA  ----------------->                         |
|                        <-----------------  ACK [    1 msgs]       |
|                                            !msu                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Single invalid Ack
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Single invalid Ack
.)x
.)b
.ip "Test Description:" 12
.np
This test begins with the link in the "In Service" state.
.np
Send an invalid Ack message to the IUT.
.np
Send an MSU at the IUT.
.np
Check that the IUT sends a Data message.
.np
Acknowledge the Data message with an Ack message to the IUT
.np
Send an Data message to the IUT.
.np
Check that the IUT acknowledges the Data message with an Ack message and
delivers an MSU to Level 3 at the IUT.

.bp
.sh 3 "Duplicated FSN"
.lp
Because M2PA does not transmit sequence numbers between peers at the
M2PA layer (there are only sequence numbers sent between peers at the SCTP
layer), tests concerning abnormal forward sequence numbers are not applicable.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Erroneous retransmission - Single MSU"
.lp
Retransmission of DATA messages is performed by SCTP for M2PA and as such the
related Q.781 tests are not applicable.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.6
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Erroneous retransmission - Multiple FISUs"
.lp
Retransmission of DATA messages is performed by SCTP for M2PA and as such the
related Q.781 tests are not applicable.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.7
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Single FISU with corrupt FIB"
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.8
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "In Service prior to RPO being set"
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.9
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|              :set lpo                                             |
|      PROCESSOR-OUTAGE  ----------------->                         |
|                                            !rpo                   |
|                  DATA  ----------------->                         |
|                        <-----------------  ACK [    1 msgs]       |
|                                            !msu                   |
|                  DATA  ----------------->                         |
|                        <-----------------  ACK [    1 msgs]       |
|                                            !msu                   |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  In service prior to RPO being set
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  In service prior to RPO being set
.)x
.)b
.ip "Test Description:" 12
.np
The test beings with the link in the "In Service" state.
.np
Issue a Level 3 "Set Local Processor Outage" command at the PT and send a
status "Processor Outage" message to the IUT.
.np
Check that the IUT indicates "Remote Processor Outage" to Level 3 at the IUT.
.np
Send two consecutive Data messages to the IUT.
.np
Check that the IUT acknowledges both Data messages with an Ack and that two
MSUs are delivered to Level 3 at the IUT.

.bp
.sh 3 "Abnormal BSN - single MSU"
.lp
Because M2PA does not transmit sequence numbers between peers at the
M2PA layer (there are only sequence numbers sent between peers at the SCTP
layer), tests concerning abnormal forward sequence numbers are not applicable.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.10
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Abnormal BSN - two consecutive FISUs"
.lp
Because M2PA does not transmit sequence numbers between peers at the
M2PA layer (there are only sequence numbers sent between peers at the SCTP
layer), tests concerning abnormal forward sequence numbers are not applicable.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.11
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Excessive delay of acknowledgments"
.lp
This test case validates the IUT response to a excessively delayed
acknowledgment.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.12
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :msu                   |
|                        <-----------------  DATA [   35 bytes]     |
|                              !                                    |
|                              !  T7         0.5 <= T7 <= 2.0       |
|                              !                                    |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(T7)    |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Excessive delay of acknowledgments
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Excessive delay of acknowledgments
.)x
.)b
.ip "Test Description:" 12
.np
This test case begins with the link in the "In Service" state.
.np
Send an MSU from the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 at the IUT with reason "T7 Timeout" and that the link
remains in the "Out of Service" state.
.np
Check that the T7 is between 0.5 seconds and 2.0 seconds in duration.

.bp
.sh 3 "Level 3 Stop command"
.lp
This test case validates the response of the IUT to the Level 3 "Stop"
command while in the "In Service" state.
.lp
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 8.13 
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :stop                  |
|                        <-----------------  OUT-OF-SERVICE         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Level 3 Stop command
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Level 3 Stop command
.)x
.)b
.ip "Test Description:" 12
.np
This test begins with the link in the "In Service" state.
.np
Issue the Level 3 "Stop" command at the IUT.
.np
Check that the IUT sends a status "Out of Service" message and remains in the
"Out of Service" state.

.bp
.sh 2 "Transmission and Reception Control (PCR)"
.lp
M2PA does not perform Preventative Cyclic Retranmission and, therefore, the
test cases in this section are not applicable to M2PA.
.sh 3 "MSU transmission and reception"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Priority control"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Forced retransmission with the value N1"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Forced retransmission with the value N2"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.4
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Forced retransmission cancel"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.5
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Reception of forced retransmission"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.6
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "MSU transmission while RPO set"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.7
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Abnormal BSN - Single MSU"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.8
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Abnormal BSN - Two MSUs"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.9
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Unexpected FSN"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.10
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Excessive delay of acknowledgments"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.11
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "FISU with FSN expected for MSU"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.12
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 3 "Level 3 Stop command"
.lp
This test case is not applicable to M2PA.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 9.13
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                          NOT APPLICABLE                           |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Not Applicable
.)x
.)b
.ip "Test Description:"
.np
Not applicable.

.bp
.sh 2 "Congestion Control"
.sh 3 "Congestion abatement"
.lp
This test case validates the response of the IUT to the Level 3 "Congestion"
and "Congestion Ceases" conditions.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 10.1
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :make cong discard     |
|                        <-----------------  BUSY                   |
|                                            :clear congestion      |
|                        <-----------------  BUSY-ENDED             |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Congestion abatement
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Congestion abatement
.)x
.)b
.ip "Test Description:" 12
.np
This test begins with the link in the "In Service" state.
.np
Generate a local Level 3 "Congestion" condition at the IUT.
.np
Check that the IUT sends a status "Busy" message.
.np
Generate a local Level 3 "Congestion Ceases" condition at the IUT.
.np
Check that the IUT sends a status "Busy Ended" message.

.bp
.sh 3 "Timer T7"
.lp
This test case validates timer T7 and procedures at the ITU.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 10.2
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :msu                   |
|                        <-----------------  DATA [   35 bytes]     |
|                  BUSY  ----------------->                         |
|                              !                                    |
|                              !  T7                                |
|                              !                                    |
|                   ACK  ----------------->                         |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T7
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T7
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Send an MSU at the IUT.
.np
Wait for less than T7 and then acknowledge the Data message to the IUT with an
Ack message.
.np
Check that the IUT sends no further status messages and remains in the "In
Service" state.

.bp
.sh 3 "Timer T6"
.lp
This case validates timer T6 and procedures at the IUT.
The expected sequence of events is illustrated \fIFigure \n($1.\n($2.\n($3\fR.

.(b C
Reference:  Q.781/Test 10.3
\fC ___________________________________________________________________\ 
|                                                                   |
|                    PT                      IUT                    |
|                                                                   |
|                                            :msu                   |
|                        <-----------------  DATA [   35 bytes]     |
|                  BUSY  ----------------->                         |
|                              !                                    |
|                              !  T6         3.0 <= T6 <= 6.0       |
|                              !                                    |
|                        <-----------------  OUT-OF-SERVICE         |
|                                            !out of service(T6)    |
|                                                                   |
|___________________________________________________________________|
.ce 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T6
.(x 1
\fIFigure \n($1.\n($2.\n($3.\fR  Timer T6
.)x
.)b
.ip "Test Description:" 12
.np
The test begins with the link in the "In Service" state.
.np
Send an MSU at the IUT.
.np
Send a status "Busy" messages to the IUT.
.np
Check that the IUT sends a status "Out of Service" message and indicates "Out
of Service" to Level 3 with reason "T6 Timeout" and remains in the "Out of
Service" state.
.np
Check that T6 is between 3.0 seconds and 6.0 seconds in duration.

.bp
.uh "Security Considerations"
.lp
There are no security considerations for this draft.

.uh "Acknowledgments"
.de ]<
.uh "References"
.ad l
.hy 0
.rm (f )f
..
.(l L
.[
$LIST$
.]
.)l
.uh "Author's Addresses"
.lp
.(b L
\fCBrian F. G. Bidulock                             Tel: +1-972-839-4489
\fCOpenSS7 Corporation                       EMail: bidulock@openss7.org
\fC4701 Preston Park Boulevard, Suite 424                              \ 
\fCPlano, TX 75093                                                     \ 
\fCUSA                                                                 \ 
.)b
.bl 2
.lp
This Internet Draft expires June 2002.
.ba +4
.bp
.(l I
.ce 1
.uh "List of Illustrations"
.bl 2
.xp 1
.)l
.bp
.(l I
.ce 1
.uh "Table of Contents"
.bl 2
.xp 0
.)l
