SIST EN 301 003-5 V1.1.3:2005

• Abstract:

  Develop part 5 (TSS&TP for the network) of EN 301 003

• Status: Published
• Publication Date: 30-Jun-2005
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jul-2005
• Due Date: 01-Jul-2005
• Completion Date: 01-Jul-2005
• Mandate: BC-T-338
• Ref Project: ETSI EN 301 003-5 V1.1.3 (1999-11) - Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

SIST EN 301 003-5 V1.1.3:2005 is the Slovenian adoption of ETSI EN 301 003-5 V1.1.3, published by SIST. It specifies the network Test Suite Structure and Test Purposes (TSS&TP) for Broadband Integrated Services Digital Network (B-ISDN) Digital Subscriber Signalling System No. two (DSS2) peak cell rate (PCR) modification by the connection owner, so implementers and test labs can check conformance at the T reference point or coincident S and T reference point.

What does SIST EN 301 003-5 V1.1.3:2005 specify?

SIST EN 301 003-5 V1.1.3:2005 defines the network-side conformance test purposes for EN 301 003-1 implementations. It is the test-specification part of a multi-part standard, and it points to a further part that provides the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this document.

The document is organized into these main clauses:

• Clause 1 - Scope
• Clause 2 - References
• Clause 3 - Definitions and abbreviations
• Clause 4 - Test Suite Structure (TSS)
• Clause 5 - Test Purposes (TP)
• Clause 6 - Compliance
• Clause 7 - Requirements for a comprehensive testing service

Clause 4 presents the test suite structure in Figure 1. Clause 5 gives the TP naming convention in Table 1 and then lists the test purposes for the requesting entity, the responding entity, error handling, and timer behaviour.

What are the key requirements of SIST EN 301 003-5 V1.1.3:2005?

Test suite structure and naming

Clause 4 groups the test purposes by signalling procedures at the coincident S/T and T reference points, then by modification procedures at the requesting entity and the responding entity. This matters because a test campaign can be organized by role and by behaviour, instead of as a flat list of cases.

Clause 5 states that TP names use the form <suite_id>_<group>_<nnn>, with MODN for the modification service and the network IUT. That gives a consistent way to map a test case back to its service and group.

The TPs are based on EN 301 003-1 and the PICS specification EN 301 003-2. The document also says the TPs cover only externally observable behaviour and practical situations that a real implementation is likely to face.

When a TP refers to a final call state, the state check is done with STATUS ENQUIRY and STATUS exchange as described in EN 300 443-1. In practice, that means the test is not complete until the IUT proves the expected call state.

Requesting entity behaviour

Clause 5.2.1.1 covers the network as the modifying requester, with PICS item R 2.1. In valid behaviour, when the IUT is in N10 and a PCR modification is requested, it sends MODIFY REQUEST and moves to N13.

The same clause checks how the IUT reacts to MODIFY ACKNOWLEDGE, MODIFY REJECT, STATUS, RELEASE, and clearing indications. The practical point is that the network must not only send the right message, but also land in the right call state and, when required, send CONNECTION AVAILABLE or STATUS ENQUIRY.

Clause 5.2.1.1.3 adds timer behaviour. On expiry of timer T360, the IUT in N13 sends RELEASE with cause value 102 and enters N11. That gives a clear recovery path for a timed-out modification procedure.

Responding entity behaviour

Clause 5.2.1.2 covers the network as the entity that receives the modification request, with PICS item R 2.2. On a compatible MODIFY REQUEST, the IUT moves to N14; on an incompatible combination of ATM traffic descriptor parameters, it sends MODIFY REJECT with cause value 73 and stays in N10.

If the remote user accepts the change, the IUT sends MODIFY ACKNOWLEDGE. If confirmation is requested, the acknowledgement includes a Broadband report type IE with modification confirmation; if confirmation is not requested, it is sent without that IE.

If the remote user rejects the change, the IUT sends MODIFY REJECT with the originating cause value and returns to N10. In practice, this tells the reader exactly how the network must close the loop after a remote decision.

Error handling and message validity rules

Clause 5 states that, unless otherwise specified, messages are valid and contain at least the mandatory information elements, and information elements are valid and contain at least the mandatory parameters. That baseline is important because the error cases are then clearly about malformed or unsupported input, not about ordinary missing fields.

The error cases cover invalid protocol discriminator, unused Call Reference (CR), missing mandatory information elements, and content errors in mandatory or unrecognized information elements. The response can be RELEASE COMPLETE, STATUS, RELEASE, or silent ignore, depending on the call state and on the Information element action indicator (IE_AI) or Message action indicator (MSG_AI).

Several call states are exercised, including N0, N1, N3, N4, N6, N7, N9, N10, N11, N12, N13, and N14. That matters in practice because the same bad message can require a different response depending on the current call state.

Compliance and test service

Clause 6 says a compliant ATS shall use test cases corresponding to all or a subset of the TPs, an appropriate subset of the TSS, the same naming conventions, and the PICS/TP relationship for test case deselection. It also requires compliance with ISO/IEC 9646-2.

A subset is allowed only where a particular Abstract Test Method (ATM) makes some TPs untestable, and all testable TPs shall be included. Clause 7 adds that any organization claiming a comprehensive testing service for network equipment conforming to EN 301 003-1 shall use the Remote test method from ISO/IEC 9646-2 at minimum.

What terms does SIST EN 301 003-5 V1.1.3:2005 define?

• Abstract Test Method (ATM) - the conformance testing method used to realize tests; the document uses it when explaining why some TPs may be untestable.
• Abstract Test Suite (ATS) - the set of abstract test cases built from the TPs and used for conformance testing.
• Implementation Under Test (IUT) - the implementation being tested, here the network-side DSS2 entity.
• Protocol Implementation Conformance Statement (PICS) - the proforma that records which features are supported and helps select or deselect test cases.
• Protocol Implementation eXtra Information for Testing (PIXIT) - extra implementation information needed to run the tests.
• Test Purpose (TP) - the statement of the behaviour that a test case must verify.
• Test Suite Structure (TSS) - the grouping of TPs into testing areas such as requesting entity, responding entity, error handling, and timers.
• Peak Cell Rate (PCR) - the connection parameter being modified by the procedure.

Who uses SIST EN 301 003-5 V1.1.3:2005?

This standard is used by engineers and test teams who need to build or run conformance tests for DSS2 network implementations. It is also useful to quality managers, certification labs, and buyers who need to check whether a B-ISDN network product supports the peak cell rate modification procedure defined in EN 301 003-1.

In practice, users apply it to:

• design an ATS from the listed TPs
• choose test cases using the PICS proforma
• verify network-side call-state transitions and message handling
• check timer behaviour and error recovery
• confirm behaviour at the T reference point or coincident S and T reference point

Which standards are used with SIST EN 301 003-5 V1.1.3:2005?

Reference	What it contributes
ETS 300 406	Conformance testing methodology and standardization methodology used as the testing basis
EN 300 443-1	B-ISDN user-network interface layer 3 basic call/bearer control; used for call-state procedures and final-state checking
EN 301 003-1	Protocol specification for peak cell rate modification by the connection owner; the behaviour under test
EN 301 003-2	PICS proforma specification; used to select applicable test purposes
ITU-T Recommendation I.413	Defines the B-ISDN user-network interface and the T reference point / coincident S and T reference point
ISO/IEC 9646-1	General conformance testing concepts and framework
ISO/IEC 9646-2	Abstract Test Suite specification and conformance testing rules
ITU-T Recommendation Q.2963.1	Base recommendation for DSS2 connection modification, peak cell rate modification by the connection owner

What does the SIST EN 301 003-5 V1.1.3:2005 document contain?

The document contains a test suite structure, a TP naming convention, and a detailed list of test purposes for the network side of the PCR modification procedure. Its test purposes cover valid behaviour, error conditions, and timer expiry for both the requesting entity and the responding entity.

It also includes explicit call-state references and expected message exchanges such as MODIFY REQUEST, MODIFY ACKNOWLEDGE, MODIFY REJECT, CONNECTION AVAILABLE, STATUS, RELEASE, and RELEASE COMPLETE. Those are the basis for running abstract conformance tests and checking state changes.

Clause 6 turns the TPs into ATS compliance rules, and clause 7 states the minimum testing method for comprehensive testing service. The bibliography adds ISO/IEC 9646-3 on TTCN as supporting information for test case specification.

SLOVENSKI STANDARD
01-julij-2005
âLURNRSDVRYQRGLJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL%,6'13URWRNRO
GLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66.DUDNWHULVWLNH]YH]H3ULODJDMDQMH
WHPHQVNHFHOLþQHKLWURVWLSULODVWQLNX]YH]HGHO=JUDGEDSUHVNXãDOQHJDQL]DLQ
QDPHQLSUHVNXãDQMD766 736SHFLILNDFLMD]DRPUHåMH
Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling
System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification
by the connection owner; Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network
Ta slovenski standard je istoveten z: EN 301 003-5 Version 1.1.3
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Broadband Integrated Services Digital Network (B-ISDN);
Digital Subscriber Signalling System No. two (DSS2) protocol;
Connection characteristics;
Peak cell rate modification by the connection owner;
Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network
2 ETSI EN 301 003-5 V1.1.3 (1999-11)
Reference
DEN/SPS-05152-5 (9ad90ie0.PDF)
Keywords
ATM, B-ISDN, DSS2, ISDN, TSS&TP, network,
broadband, UNI
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.:[phone] Fax:[phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
[e-mail]
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: [e-mail]
Important notice
This ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference should be the printing on ETSI printers of the PDF version kept on a specific network
drive within ETSI Secretariat.
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1999.
All rights reserved.
ETSI
3 ETSI EN 301 003-5 V1.1.3 (1999-11)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope .5
2 References.5
3 Definitions and abbreviations .6
3.1 Definitions.6
3.1.1 Definitions related to conformance testing .6
3.1.2 Definitions related to EN 301 003-1.6
3.2 Abbreviations .7
4 Test Suite Structure (TSS) .7
5 Test Purposes (TP).8
5.1 Introduction .8
5.1.1 TP naming convention .8
5.1.2 Source of TP definition.8
5.1.3 Test strategy.8
5.1.4 Test of call states .8
5.2 TPs for the Peak cell rate modification, network.8
5.2.1 Signalling procedures at the coincident S /T and at the T reference points .9
B B B
5.2.1.1 Modification procedures at the requesting entity .9
5.2.1.1.1 Valid behaviour (01).9
5.2.1.1.2 Handling of errors conditions (02) .10
5.2.1.1.3 Timers (03).14
5.2.1.2 Modification procedures at the responding entity .14
5.2.1.2.1 Valid behaviour (04).14
5.2.1.2.2 Handling of error conditions (05).15
6 Compliance.17
7 Requirements for a comprehensive testing service.17
Bibliography.18
History .19
ETSI
4 ETSI EN 301 003-5 V1.1.3 (1999-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
(http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocols and Switching (SPS).
The present document is part 5 of a multi-part standard covering the Digital Subscriber Signalling System No. 2 (DSS2)
protocol specification for the B-ISDN Peak cell rate modification by the connection owner, as identified below:
Part 1: "Protocol specification [ITU-T Recommendation Q.2963.1 [8] (1996), modified]";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network".
National transposition dates
Date of adoption of this EN: 29 October 1999
Date of latest announcement of this EN (doa): 31 January 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 July 2000
Date of withdrawal of any conflicting National Standard (dow): 31 July 2000
ETSI
5 ETSI EN 301 003-5 V1.1.3 (1999-11)
1 Scope
This fifth part of EN 301 003 specifies the network Test Suite Structure and Test Purposes (TSS&TP) for the T
B
reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.413 [5]) of
B B
implementations conforming to the standards for the signalling user-network layer 3 specification for Peak cell rate
modification by the connection owner of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the pan-
European Broadband Integrated Services Digital Network (B-ISDN), EN 301 003-1 [3].
A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile conformance
testing specifications; Standardization methodology".
[2] EN 300 443-1 (V1.3): "Broadband Integrated Services Digital Network (B-ISDN); Digital
Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3
specification for basic call/bearer control - Part 1: Protocol specification [ITU-T Recommendation
Q.2931 (1995), modified]".
[3] EN 301 003-1 (V1.1): "Broadband Integrated Services Digital Network (B-ISDN); Digital
Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate
modification by the connection owner - Part 1: Protocol specification [ITU-T Recommendation
Q.2963.1 (1996), modified]".
[4] EN 301 003-2 (V1.1): "Broadband Integrated Services Digital Network (B-ISDN); Digital
Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate
modification by the connection owner - Part 2: Protocol Implementation Conformance Statement
(PICS) proforma specification".
[5] ITU-T Recommendation I.413 (1993): "B-ISDN user-network interface".
[6] ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[7] ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[8] ITU-T Recommendation Q.2963.1: "Digital Subscriber Signalling System No. 2 - Connection
modification: Peak cell rate modification by the connection owner".
ETSI
6 ETSI EN 301 003-5 V1.1.3 (1999-11)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 301 003-1 [3] and EN 300 443-1 [2]
and the following apply:
3.1.1 Definitions related to conformance testing
abstract test case: refer to ISO/IEC 9646-1 [6]
Abstract Test Method (ATM): refer to ISO/IEC 9646-1 [6]
Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [6]
Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [6]
lower tester: refer to ISO/IEC 9646-1 [6]
Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [6]
PICS proforma: refer to ISO/IEC 9646-1 [6]
Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [6]
PIXIT proforma: refer to ISO/IEC 9646-1 [6]
Test Purpose (TP): refer to ISO/IEC 9646-1 [6]
3.1.2 Definitions related to EN 301 003-1
network: DSS2 protocol entity at the Network side of the user-network interface where a T reference point or
B
coincident S and T reference point applies
B B
network (S /T ): DSS2 protocol entity at the Network side of the user-network interface where a coincident S and T
B B B B
reference point applies
network (T ): DSS2 protocol entity at the Network side of the user-network interface where a T reference point
B B
applies (user is the private ISDN)
ETSI
7 ETSI EN 301 003-5 V1.1.3 (1999-11)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
B-ISDN Broadband Integrated Services Digital Network
CR Call Reference
DSS2 Digital Subscriber Signalling System No. two
IE_AI Information element action indicator
IE_flag Information element instruction indicator flag
IUT Implementation Under Test
N0 Null link state
N1 Call Initiated link state
N10 Active link state
N12 Disconnect Indication call state
N3 Outgoing Call Proceeding link state
N4 Call Delivered link state
N6 Call Present link state
N7 Call Received link state
N9 Incoming Call Proceeding link state
PCR Peak Cell Rate
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
TP Test Purpose
TSS Test Suite Structure
4 Test Suite Structure (TSS)
Signalling procedures at the coincident S /T and at the T reference points
B B B
Modification procedures at the requesting entity.
Valid behaviour. (01)
Handling of error conditions .(02)
Timers .(03)
Modification procedures at the responding entity.
Valid behaviour. (04)
Handling of error conditions .(05)
Figure 1: Test suite structure
ETSI
8 ETSI EN 301 003-5 V1.1.3 (1999-11)
5 Test Purposes (TP)
5.1 Introduction
For each test requirement a TP is defined.
5.1.1 TP naming convention
TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= service + type of IUT: "MODN" for modification, IUT = Network
= group number: two character field representing the group reference
according to TSS
= sequential number: (01-99)
5.1.2 Source of TP definition
The TPs are based on EN 301 003-1 [3].
5.1.3 Test strategy
As the base standard EN 301 003-1 [3] contains no explicit requirements for testing, the TPs were generated as a result
of an analysis of the base standard and the PICS specification EN 301 003-2 [4].
The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and are
limited to conceivable situations to which a real implementation is likely to be faced (ETS 300 406 [1]).
5.1.4 Test of call states
Many TPs include a reference to the IUT's final call state after the realization of the TP. In these cases the TP includes
the requirement to ensure that the IUT has entered this particular final call state. Ensuring that the IUT is in a particular
call state shall be realized by following the procedures described in subclause 5.6.11 of EN 300 443-1 [2]. According to
these procedures, the IUT on receipt of a STATUS ENQUIRY message, shall respond with a STATUS message
indicating, in the fifth octet of the Call state information element, the current call state of the IUT. This exchange of
messages is not mentioned explicitly in each TP but is considered to be implicit in the reference to the final call state.
This way of phrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and to improve
the readability.
5.2 TPs for the Peak cell rate modification, network
All PICS items referred to in this subclause are as specified in EN 301 003-2 [4] unless indicated otherwise by another
numbered reference.
ETSI
9 ETSI EN 301 003-5 V1.1.3 (1999-11)
Unless specified:
- the messages indicated are valid and contain at least the mandatory information elements and possibly optional
information elements;
- the information elements indicated are valid and contain at least the mandatory parameters and possibly optional
parameters.
5.2.1 Signalling procedures at the coincident S /T and at the
B B
T reference points
B
NOTE: Unless otherwise specified, the connection defined by the requested ATM traffic descriptor is available
for use.
5.2.1.1 Modification procedures at the requesting entity
Test purposes for EN 301 003-1 [3] subclause 9.1.
Selection: The iut support the requirements for the modification requesting entity. PICS: R 2.1.
5.2.1.1.1 Valid behaviour (01)
MODN_01_01
Ensure that the IUT in N10, to indicate that a PCR modification has been requested,
- sends a MODIFY REQUEST message and enters N13.
MODN_01_02
Ensure that the IUT in N13, on receipt of a MODIFY ACKNOWLEDGE message including a Broadband report type
information element, with type of report field different from "Modification confirmation"
- sends no message or optionally send a STATUS message (cause value: 100, call state: 10) and enters N10.
MODN_01_03
Ensure that the IUT in N13, on receipt of a MODIFY ACKNOWLEDGE message without broadband report type
information element,
- sends no message and enters N10.
MODN_01_04
Ensure that the IUT in N13, on receipt of a MODIFY ACKNOWLEDGE message including an empty Broadband report
type information element,
- sends no message and enters N10.
MODN_01_05
Ensure that the IUT in N10, having received a MODIFY ACKNOWLEDGE message, including a broadband report
type information element requesting confirmation, to indicate that the modification of the connection has been
confirmed by the remote user,
- sends a CONNECTION AVAILABLE message and remains in N10.
MODN_01_06
Ensure that the IUT in N13, on receipt of a MODIFY REJECT message,
- sends no message and enters N10.
MODN_01_07
Ensure that the IUT in N13, on receipt of a STATUS message (call state: 10, cause value: 97 or 101) with diagnostic
identifying of the MODIFY REQUEST message,
- sends no message and enters N10.
MODN_01_08
Ensure that the IUT in N13, on receipt of a STATUS message (call state: 10, cause value: 97 or 101) without diagnostic
identifying of the MODIFY REQUEST message,
- sends a STATUS ENQUIRY message and remains in N13.
ETSI
10 ETSI EN 301 003-5 V1.1.3 (1999-11)
MODN_01_09
Ensure that the IUT in N13, (having sent a STATUS ENQUIRY message), on receipt of a STATUS message
(call state: 14),
- sends no message and remains in N13.
MODN_01_10
Ensure that the IUT in N13, (having sent a STATUS ENQUIRY message), on receipt of a STATUS message
(call state: 10),
- sends no message and enters N10.
MODN_01_11
Ensure that the IUT in N13, on receipt of a RELEASE message,
- enters N11.
MODN_01_12
Ensure that the IUT in N13, on receipt of a clearing indication at the remote interface,
- sends a RELEASE message and enters N12.
5.2.1.1.2 Handling of errors conditions (02)
MODN_02_01
Ensure that the IUT in N13, on receipt of a MODIFY ACKNOWLEDGE message with a protocol discriminator other
than '09'O,
- sends no message and remains in N13.
MODN_02_02
Ensure that the IUT in N13, on receipt of a MODIFY ACKNOWLEDGE message with an unused Call Reference (CR),
- sends a RELEASE COMPLETE message (CR of the MODIFY ACKNOWLEDGE message, cause value: 8
...