ETSI EN 300 267-6 V1.2.6 (2000-06)

SLOVENSKI STANDARD
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'DOMLQVNHVWRULWYHWHOHIRQLMD
N+]YLGHRWHOHIRQLMDDYGLRJUDILþQDNRQIHUHQFDLQYLGHRNRQIHUHQFD3URWRNRO
WQLSUHVNXãDOQLQL]GLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66GHO$EVWUDN
OD3,;,7$76LQGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHGHOQHL]YHGEHSURWRNR
3URIRUPDVSHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Telephony 7 kHz, videotelephony,
audiographic conference and videoconference teleservices; Digital Subscriber Signalling
System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma specification for the
network
Ta slovenski standard je istoveten z: EN 300 267-6 Version 1.2.6
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)
Integrated Services Digital Network (ISDN);
Telephony 7 kHz, videotelephony, audiographic conference
and videoconference teleservices;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 6: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network


2 ETSI EN 300 267-6 V1.2.6 (2000-06)
Reference
REN/SPS-05112-6
Keywords
Audio, ISDN, DSS1, teleservice, 7 kHz, video,
telephony, ATS, PIXIT, network
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33493654716
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
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document 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 shall be the printing on ETSI printers of the PDF version kept on a specific network
drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
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 2000.
All rights reserved.
ETSI
3 ETSI EN 300 267-6 V1.2.6 (2000-06)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.6
3 Definitions and abbreviations .7
3.1 Definitions.7
3.2 Abbreviations .7
4 Introduction.8
5 Abstract Test Method (ATM) .8
5.1 Description of ATM used.8
5.2 Conventions for test components and PCOs.8
5.3 Description of PCOs.9
5.3.1 D-channel PCOs .10
5.3.2 PSTN PCO.10
5.4 Naming conventions.10
5.4.1 Test cases.10
5.4.2 Variables and parameters.11
6 Untestable test purposes.11
7 ATS conventions.12
7.1 Declarations part .12
7.1.1 Type definitions .12
7.1.1.1 Simple type definitions.12
7.1.1.2 Structured type definitions .12
7.1.1.2.1 TTCN structured type definitions.12
7.1.1.2.2 ASN.1 structured type definitions.12
7.1.1.3 ASP type definitions.12
7.1.1.3.1 TTCN ASP type definitions.12
7.1.1.3.2 ASN.1 ASP type definitions .13
7.1.1.4 PDU type definitions.13
7.1.1.4.1 TTCN PDU type definitions.13
7.1.1.4.2 ASN.1 PDU type definitions .13
7.1.2 Test suite constants .13
7.1.3 Test suite parameters .13
7.1.4 Variables.14
7.1.4.1 Test suite variables.14
7.1.4.2 Test case variables .14
7.1.5 Test suite operation definitions.14
7.2 Constraints part.15
7.2.1 Structured type constraint declaration.15
7.2.2 ASN.1 type constraint declaration .15
7.2.3 ASP type constraint declaration.15
7.2.3.1 ASN.1 ASP type constraint declaration .15
7.2.3.2 TTCN ASP type constraint declaration.15
7.2.4 PDU type constraint declaration .15
7.2.4.1 ASN.1 PDU type constraint declaration.15
7.2.4.2 TTCN PDU type constraint declaration .15
7.2.5 Derived constraint.15
7.2.6 Parameterized constraints .15
7.2.7 Value assignment.16
7.2.7.1 Specific values .16
7.2.7.2 Matching values .16
7.3 Dynamic part .16
ETSI
4 ETSI EN 300 267-6 V1.2.6 (2000-06)
7.3.1 Test cases.16
7.3.2 Test steps .16
7.3.2.1 PTC1_IN, PTC1_2B_IN.16
7.3.2.2 PTC1_OUT, PTC1_BCAP_OUT, PTC1_BCAP_HLC_OUT, PTC1_2B_OUT .16
7.3.3 Defaults.17
8 ATS to TP map.17
9 PCTR conformance.17
10 PIXIT conformance.17
11 ATS conformance .18
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma.19
A.1 Identification summary .19
A.1.1 Protocol conformance test report.19
A.1.2 IUT identification.19
A.1.3 Testing environment.20
A.1.4 Limits and reservations.20
A.1.5 Comments.20
A.2 IUT conformance status .20
A.3 Static conformance summary.20
A.4 Dynamic conformance summary.21
A.5 Static conformance review report .21
A.6 Test campaign report.21
A.7 Observations.25
Annex B (normative): Partial PIXIT proforma.26
B.1 Identification summary .26
B.2 Abstract test suite summary .26
B.3 Test laboratory .26
B.4 Client (of the test laboratory).27
B.5 System Under Test (SUT).27
B.6 Protocol information .28
B.6.1 Protocol identification .28
B.6.2 Configuration to be tested .28
B.6.3 Actions required to stimulate IUT .29
B.6.4 Test management timers.29
B.6.5 Parameter values.30
Annex C (normative): Abstract Test Suite (ATS).31
C.1 The TTCN Graphical form (TTCN.GR).31
C.2 The TTCN Machine Processable form (TTCN.MP) .31
Annex D (informative): General structure of ATS.32
History.34
ETSI
5 ETSI EN 300 267-6 V1.2.6 (2000-06)
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 ETSI 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 ETSI 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 Services
Protocols for Advanced Networks (SPAN).
The present document is part 6 of a multi-part EN covering the Digital Subscriber Signalling System No. one (DSS1)
protocol specification for the Integrated Services Digital Network (ISDN) telephony 7 kHz, videotelephony,
audiographic conference and videoconference teleservices, as described below:
Part 1: "Protocol specification";
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: 26 May 2000
Date of latest announcement of this EN (doa): 31 August 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2001
Date of withdrawal of any conflicting National Standard (dow): 28 February 2001
ETSI
6 ETSI EN 300 267-6 V1.2.6 (2000-06)
1 Scope
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma for the Network side of the T reference point or coincident S and T reference point (as
defined in ITU-T Recommendation I.411 [13]) of implementations conforming to the stage three standard of the
telephony 7 kHz and videotelephony teleservices for the pan-European Integrated Services Digital Network (ISDN) by
means of the Digital Subscriber Signalling System No. one (DSS1) protocol, EN 300 267-1 [2].
EN 300 267-5 [4] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS and partial PIXIT
proforma specification. Other parts specify the TSS&TP and the ATS and partial PIXIT proforma for the User side of
the T reference point or coincident S and T reference point of implementations conforming to EN 300 267-1 [2].
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] ETSI EN 300 196-1 (V1.2): "Integrated Services Digital Network (ISDN); Generic functional
protocol for the support of supplementary services; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 1: Protocol specification".
[2] ETSI EN 300 267-1 (V1.2): "Integrated Services Digital Network (ISDN); Telephony 7 kHz,
videotelephony, audiographic conference and videoconference teleservices; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[3] ETSI EN 300 267-2 (V1.2): "Integrated Services Digital Network (ISDN); Telephony 7 kHz,
videotelephony, audiographic conference and videoconference teleservices; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation Conformance
Statement (PICS) proforma specification".
[4] ETSI EN 300 267-5 (V1.2): "Integrated Services Digital Network (ISDN); Telephony 7 kHz,
videotelephony, audiographic conference and videoconference teleservices; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes
(TSS&TP) specification for the network".
[5] ETSI EN 300 403-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call
control; Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".
[6] ETSI EN 300 403-3 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call
control; Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification".
[7] ETSI EN 300 403-7: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;
Part 7: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the network".
[8] ISO/IEC 9646-1 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 1: General concepts".
ETSI
7 ETSI EN 300 267-6 V1.2.6 (2000-06)
[9] ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 2: Abstract Test Suite specification".
[10] ISO/IEC 9646-3 (1998): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".
[11] ISO/IEC 9646-4 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 4: Test realization".
[12] ISO/IEC 9646-5 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 5: Requirements on test laboratories and clients for the
conformance assessment process".
[13] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces; Reference configurations".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 300 267-1 [2] and ISO/IEC 9646
parts 1 [8] to 5 [12] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
CM Co-ordination Message
CP Co-ordination Point
ExTS Executable Test Suite
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
MTC Main Test Component
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
ETSI
8 ETSI EN 300 267-6 V1.2.6 (2000-06)
4 Introduction
Implementations Under Test (IUTs) which are to be tested using this ATS are required to have previously been tested
for conformity against and passed the test suite for EN 300 403-1 [5].
Any messages or fields within messages which are introduced by EN 300 403-1 [5] are included in this ATS.
Behaviours in test cases have been described in such a way to be able to take into account EN 300 403-1 [5] basic call
standard. This ATS also takes into account messages defined for the supplementary services, in particular
EN 300 196-1 [1]. When such messages are received, they are ignored by the ATS as this is not within the scope of the
present document.
5 Abstract Test Method (ATM)
5.1 Description of ATM used
This ATS describes the testing specification of the protocol procedures and switching functions needed to support the
videotelephony, audiographic conference, videoconference and telephony 7 kHz teleservices at T or coincident S and T
reference points for the network.
The requirement for testing the network IUT is to focus on the behaviour of the network IUT at the user-network
interface where a T reference point or coincident S and T reference point applies. Thus the IUT is the network DSS1
protocol entity at a particular user-network interface and not the whole network.
It is possible to specify an ATS based on a single party (remote) test method for such an IUT. However, it is considered
that an ATS based on such an approach is of limited use as the only way to specify IUT generated PDUs is to use the
"implicit send" statement. Many users of such an ATS would replace the "implicit send" statements with descriptions of
the behaviour at other interfaces.
An ATS based on a multi-party test method is considered to be more useful in that it is closer to how a real test suite
would be constructed. Such a test method specifies behaviour at multiple network interfaces. One very important
limitation here is that tests are focused on one particular interface. Thus the test system is made up of one Main Test
Component (MTC) and one or more Parallel Test Components (PTC), see figure 1.
5.2 Conventions for test components and PCOs
Figure 1 shows a logical view of the complete configuration of the MTC, PTCs, and PCOs. The Co-ordination Point
(CP) relationships between the various components are also indicated. In a master/slave arrangement, MTC is
considered to be the master while PTC1 and PTCT are the slaves. The "slave" testers are only an explicit description of
how to deal with the "other" interfaces during the testing process, i.e. "how to make the IUT send the required message".
ETSI
9 ETSI EN 300 267-6 V1.2.6 (2000-06)
Master part Slave part
MTCA PTCT
CPAT
PTC1
CPA1
L0 PCO L1 PCO T PCO
IUT
NETWORK
Figure 1: Multi-party test method
This means, in particular, that the verdict FAIL will only be assigned from the protocol aspects observed on the interface
under test (i.e. by the "master" tester), as it would be observed by a terminal connected to this interface. A failure in the
correlation between the protocol at the different interfaces to which the different testers are connected, i.e. in the
mechanism of the functional service itself, will not cause a FAIL verdict. For instance, if the IUT fails to send a message
on the tested interface after another interface has received the proper stimulus, the verdict will be INCONCLUSIVE.
The MTC MTCA has two functions in this configuration. Firstly, it has the MTC function of controlling the one or more
PTCs. Thus it is responsible for starting the PTCs and afterwards coordinates activities by exchanging Coordination
Messages (CM) with the PTCs. Secondly it is responsible for the behaviour of the Lower Tester (LT) at PCO L0.
The MTC PCO is named "L0" ("L" for Lower). The L0 PCO is used to control and observe the behaviour of the IUT
and test case verdicts are assigned depending on the behaviour observed at this PCO. The PTCs PTC1 and PTCT use
PCOs L1 and T. These PCOs are used to control and, in a limited way, observe the behaviour of the network equipment
at interfaces other than the one under test. No verdicts are assigned at these PCOs.
As stated in a previous paragraph, the non-receipt of network generated messages at L0, which are stimulated by events
at L1 or T will result in INCONCLUSIVE rather than FAIL verdicts being assigned.
5.3 Description of PCOs
The PCOs are used to control and observe the behaviour of the IUT. Preliminary test case verdicts are assigned
depending on the behaviour observed at those points. The final verdict is set by the MTC at the end of the test.
ETSI
10 ETSI EN 300 267-6 V1.2.6 (2000-06)
5.3.1 D-channel PCOs
For the D-channel, the PCOs reside at the service access point between layers 2 and 3. These PCOs are named "L0" and
"L1". The same Abstract Service Primitives (ASPs) as defined in EN 300 403-7 [13] are used.
PTC0 SUT PTC1
Layer 3 IUT Layer 3
 L0    L1 
Layer 2 Layer 2
 
      
Layer 1 Layer 1
Service provider
Figure 2: Combination of the remote and multi-party test methods
without interworking with PSTN
5.3.2 PSTN PCO
For tests involving the PSTN, the PCOs used are L0 and T. L0 is at the same location as in figure 2 and T is located at
the upper tester at the access point between the test operator and the IUT.
PTC0 SUT PTCT
T
Layer 3 IUT
 L0   
Layer 2

    
Layer 1
Service provider PSTN
Figure 3: Combination of the remote and multi-party test methods
with interworking with PSTN
5.4 Naming conventions
5.4.1 Test cases
The structure of test case identifier is as follows:
TTC_ test case covering a telephony 7 kHz requirement;
VTC_ test case covering a videotelephony requirement;
ATC_ test case covering an audiographic conference requirement;
CTC_ test case covering a videoconference requirement.
The digits corresponds to the digits of the Test Purpose (see EN 300 267-5 [4]) involved in the test case. The TPs are
ordered:
a) by type of requirement (i.e. generic, telephony 7 kHz, videotelephony, audiographic conference or
videoconference);
b) by a two digit number which specifies the relevant position in the Test Suite Structure (TSS):
- the first digit refers to the second test group level:
1 for Originating interface (ORIG);
2 for Destination interface (DEST).
ETSI
11 ETSI EN 300 267-6 V1.2.6 (2000-06)
- the second digit refers to the third test group level:
1 Fallback allowed (FBA);
2 Fallback not allowed (FBN);
3 Connection management (CMN).
c) by a two digit sequence number:
- the sequence number follows the order in which the TPs appear in the third level of the TSS.
5.4.2 Variables and parameters
The following shows the naming convention for variables used for each B-channel depending on whether one or two
B-channels are established during the call between MTCA and PTC1.
MTCA
Initial B-channel
call reference CREF
B-channel (basic) B_CHN
channel nr (primary) PX_CH_NUM
Additional B-channel
call reference CREF2
B-channel (basic) B_CHN2
channel nr (primary) PX_CH_NUM2
PTC1
Initial B-channel
call reference P1CREF
B-channel (basic) P1_B_CHN
channel nr (primary) PX_CH_NUM
Additional B-channel
call reference P1CREF2
B-channel (basic) P1_B_CHN2
channel nr (primary) PX_CH_NUM2
The following shows the naming conventions for parameters used to address the PTCs.
PTC Parameters
MTCA PX_MTCA_LCPN,
PX_MTCA_CDPN_OCTET3,
PX_MTCA_CPN
PTC1 PX_PTC1_LCPN,
PX_PTC1_CDPN_OCTET3,
PX_PTC1_CPN
PTCT PX_PSTN_LCPN,
PX_PSTN_CDPN_OCTET3,
PX_PSTN_LCPN1,
PX_PSTN_CPN_PART1,
PX_PSTN_LCPN2,
PX_PSTN_CPN_PART2
6 Untestable test purposes
TPs for generic protocol requirements do not correspond to specific protocol behaviour and only describe parts of
EN 300 267-1 [2] which support the telephony 7 kHz, videotelephony, audiographic conference and videoconference
teleservices. These TPs have been considered as untestable.
ETSI
12 ETSI EN 300 267-6 V1.2.6 (2000-06)
7 ATS conventions
This clause is structured similarly to the structure of a TTCN ATS. However, the names of the subclauses are arranged
in a way more suitable to the present document.
7.1 Declarations part
7.1.1 Type definitions
7.1.1.1 Simple type definitions
Where appropriate, simple types have a length, a value list or a range restriction attached.
Simple types defined as being of some string type (e.g. BITSTRING, OCTETSTRING), have a length restriction or a
value list attached.
Simple types, defined as being of INTEGER type, have a value list or a range restriction attached.
7.1.1.2 Structured type definitions
7.1.1.2.1 TTCN structured type definitions
All structured type definitions are provided with a full name.
All elements in every structured type definition, defined as being of some string type (e.g. BITSTRING,
OCTETSTRING), have a length restriction attached.
If an element in a structured type definition is defined as being of a referenced type, the (possible) restriction is defined
in that referenced type.
For information elements the identifier, which is unique for each element, has its type defined as a simple type where the
value list is restricted to the single value which is the identifier itself. This has the advantage that it allows a test system
derived from this ATS to easily identify information elements embedded in messages. An ATS where information
element identifiers are represented as unrestricted types can present difficulties for a derived test system in the case
where it needs to find one information element embedded in a number of others and the constraints for the other
elements have the any-or-omit value. In such a case the test system cannot easily find the beginning of each information
element.
7.1.1.2.2 ASN.1 structured type definitions
There are no ASN.1 structured type definitions in the ATS.
7.1.1.3 ASP type definitions
7.1.1.3.1 TTCN ASP type definitions
TTCN ASP type definitions only contain one PDU or no PDU at all.
All TTCN ASP type definitions are provided with a full identifier.
Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used for requesting or
receiving service from the lower layer.
ETSI
13 ETSI EN 300 267-6 V1.2.6 (2000-06)
Table 1: TTCN ASP type definition DL_REL_IN
TTCN ASP Type Definition
ASP NAME: DL_REL_IN
(DL-RELEASE-INDICATION)
PCO Type: SAP
Comments: CEId: = (SAPI,CES) mapped onto DLCI: = (SAPI,TEI)
This ASP is used to confirm the termination of an established multiple frame
operation or to report an unsuccessful establishment attempt (L2--->L3)
Parameter Name | Parameter Type | Comments
Detailed Comments :
Table 2 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and no other
parameters.
Table 2: TTCN ASP type definition DL_DATA_RQ
TTCN ASP Type Definition
ASP NAME: DL_DAT_RQ
(DL_DATA_REQUEST)
PCO Type: DSAP
Comments:
Parameter Name | Parameter Type | Comments
mun (MessageUnit) |PDU |
Detailed Comments :
To make TTCN more readable, aliases have been defined for ASPs.
7.1.1.3.2 ASN.1 ASP type definitions
There are no ASN.1 ASP type definitions in the ATS.
7.1.1.4 PDU type definitions
7.1.1.4.1 TTCN PDU type definitions
The TTCN PDU type reflects the actual data being transferred or received. All PDUs are embedded in ASPs.
A meta-type ASP has been defined for all messages which do not require the fields inside to be referenced. This
meta-type ASP carries the parameter type PDU. There is one meta-type ASP for send events and one for receive events,
named DL_DAT_RQ and DL_DAT_IN, respectively. If certain fields of a PDU have to be referenced, then a particular
ASP type has been defined for that message. For example, the call reference of an outgoing SETUP message needs to be
read by the tester and therefore the ASP type DL_DAT_IN_SETUP has been defined for this event.
7.1.1.4.2 ASN.1 PDU type definitions
There are no ASN.1 PDU type definitions in the ATS.
7.1.2 Test suite constants
Each test suite constant is defined in terms of a predefined type. The values given in the value column will remain
unchanged throughout the ATS.
7.1.3 Test suite parameters
Each test suite parameter is defined in terms of a predefined type or a referenced type. A referenced type is used when it
is necessary to attach restrictions to these type definitions (it is not allowed to include restrictions directly in the test
suite parameter table). The referenced type can have a length or value restriction attached to it in its declaration table.
ETSI
14 ETSI EN 300 267-6 V1.2.6 (2000-06)
7.1.4 Variables
7.1.4.1 Test suite variables
No test suite variables are used or defined in the ATS. In concurrent TTCN these kind of variables can be used only by
the MTC.
7.1.4.2 Test case variables
Each test case variable is defined in terms of a predefined type or a referenced type. A referenced type is used when it is
necessary to attach restrictions to these type definitions (it is not allowed to include restrictions directly in the test case
variable table). The referenced type can have a length or value restriction attached to it in its declaration table.
Where Test Case Variables are used in constraints, they are passed as formal parameters.
7.1.5 Test suite operation definitions
The description part of a test suite operation definition uses either natural language or meta C.
Table 3: Test suite operation definition ASSIGN_CHI
Test Suite Operation Definition
Operation Name: ASSIGN_CHI(basic, primary : CHI; basic_flag : BOOLEAN)
Result Type: CHI
Comments: This operation is used to assign a correct Channel identification information
element to PDUs dependent on the type of access that is tested.
Description
CHI ASSIGN_CHI(basic,primary,basic_flag)
If the value of the basic_flag is set to TRUE, the result of the operation ASSIGN_CHI will be
the value represented by the parameter basic which is of type CHI. Else the operation results in
the value represented by the parameter primary.
Examples:
ASSIGN_CHI(CHI1b_R1, CHI1p_R1, TRUE) = CHI1b_R1
ASSIGN_CHI(CHI1b_R1, CHI1p_R1, FALSE) = CHI1p_R1
Detailed comments :
The Test Suite Operation Definition shown in table 3 is used in the Constraints Part when assigning an element of type
CHI a value. The CHI type can be defined in two ways depending on whether the ATS is testing Basic or Primary-rate
access. To avoid duplicate types and thereby duplicate test cases this operation is used to assign a value to an element of
CHI type. It takes three parameters:
primary: a constraint of type CHI valid for primary rate access;
basic: a constraint of type CHI valid for basic access;
basic_flag: a Boolean value: TRUE if basic access is applicable, FALSE otherwise.
This operation returns the correct constraint according to the Boolean flag basic_flag. That constraint will then be
assigned to the specific element of type CHI.
ETSI
15 ETSI EN 300 267-6 V1.2.6 (2000-06)
7.2 Constraints part
7.2.1 Structured type constraint declaration
For every structured type definition there exists one or more structured type constraint.
7.2.2 ASN.1 type constraint declaration
There are no ASN.1 type constraint declarations in the ATS.
7.2.3 ASP type constraint declaration
7.2.3.1 ASN.1 ASP type constraint declaration
There are no ASN.1 ASP type constraint declarations in the ATS.
7.2.3.2 TTCN ASP type constraint declaration
The PDUs to be sent or received are passed to the TTCN ASP constraint declarations Ms and Mr as parameters of meta
type PDU. Only if values inside a specific PDU have to be referenced, the use of the meta type PDU is not allowed
according to ISO/IEC 9646-3 [10]. In such cases different TTCN ASP constraint declarations are used, which are
defined to carry only a specific type of PDU (e.g. SETUP). Table 4 shows an example of such a TTCN ASP constraint
declaration.
Table 4: TTCN ASP constraint declaration Sr
TTCN ASP Constraint Declaration
Constraint Name: Sr(PARAM: SETUP_PDU)
ASP Type: DL_DAT_IN_SETUP
Derivation Path:
Comments: ASP to indicate the receipt of SETUP messages.
Parameter Name | Parameter Value | Comments
mun |PARAM |
Detailed Comments :
All ASP constraints have a specific value for its parameter. No matching symbols are used in ASP constraints.
7.2.4 PDU type constraint declaration
7.2.4.1 ASN.1 PDU type constraint declaration
There are no ASN.1 PDU type constraint declarations in the ATS.
7.2.4.2 TTCN PDU type constraint declaration
PDU constraints are used for assigning values or patterns to the data being sent or received.
7.2.5 Derived constraint
Derived constraints are not used in the ATS.
7.2.6 Parameterized constraints
Parameterized constraints are used in the ATS.
ETSI
16 ETSI EN 300 267-6 V1.2.6 (2000-06)
7.2.7 Value assignment
7.2.7.1 Specific values
For specific value assignment both explicit values and references to explicit values are used.
7.2.7.2 Matching values
As matching values the following mechanisms are used:
Instead of value:
AnyOrOmit "*"
AnyValue "?"
SuperSet SUPERSET
Omit "-"
Inside value:
AnyOne "?"
AnyOrNone "*"
7.3 Dynamic part
7.3.1 Test cases
Each test case contains:
- as purpose, the reference of the test purpose from EN 300 267-5 [4];
- as description, the relevant references to EN 300 267-1 [2];
- as behaviour description, at least a main tree for the MTC to handle the execution of other PTC's subtrees and a
subtree for PTCO to describe the expected behaviour. When there is interworking with PSTN network, subtrees
for PTC1 or PTCT are added.
The check of tone and announcements by an operator is optional.
7.3.2 Test steps
Much use has been made of test steps to avoid needless repetition of dynamic behaviour.
7.3.2.1 PTC1_IN, PTC1_2B_IN
These test steps describe the behaviour of PTC1 for support of an incoming call at MTCA. Thus PTC1 is the originator
of the call. PTC1 receives a Co-ordination Message (CM) from MTCA in order to send the SETUP message which
begins the call establishment. The test step is terminated by receipt of a RELEASE message or by an appropriate
STOP_PTC1 CM from the MTCA.
PTC1_2B_IN is used for an incoming call requiring two B-channels.
7.3.2.2 PTC1_OUT, PTC1_BCAP_OUT, PTC1_BCAP_HLC_OUT, PTC1_2B_OUT
These test steps describe the behaviour of PTC1 for support of an outgoing call at the MTC (served user side). Thus
PTC1 is at the destination side of the call. The test step is terminated by receipt of a RELEASE message or by an
appropriate STOP_PTC CM from MTCA.
ETSI
17 ETSI EN 300 267-6 V1.2.6 (2000-06)
The behaviour is regulated from the MTCA by means of CMs se
...