SIST EN 300 141-6 V1.2.4:2005
(Main)Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; 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
Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; 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
Update to references to cite latest basic call standards et al. Incorporation of minor technical modifications where necessary.
Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: zadržanje klica (HOLD) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 6. del: Abstraktni preskušalni niz (ATS) in dodatna informacija za preskušanje delne izvedbe protokola (PIXIT) - Proforma specifikacija za omrežje
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-julij-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 'RSROQLOQDVWRULWHY ]DGUåDQMH
NOLFD +2/' 3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW '66 GHO
$EVWUDNWQLSUHVNXãDOQLQL] $76 LQGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHGHOQH
L]YHGEHSURWRNROD 3,;,7 3URIRUPDVSHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service;
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 141-6 Version 1.2.4
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.
EN 300 141-6 V1.2.4 (1998-06)
European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Call Hold (HOLD) supplementary service;
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 EN 300 141-6 V1.2.4 (1998-06)
Reference
REN/SPS-05145-S-6 (1b1i0iqo.PDF)
Keywords
ISDN, DSS1, supplementary service, HOLD,
testing, ATS, PIXIT, network
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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
secretariat@etsi.fr
http://www.etsi.fr
http://www.etsi.org
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 1998.
All rights reserved.
ETSI
3 EN 300 141-6 V1.2.4 (1998-06)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.Error! Bookmark not defined.
3 Definitions and abbreviations .7
3.1 Definitions . 7
3.2 Abbreviations. 7
4 Abstract Test Method (ATM) .8
4.1 Description of ATM used . 8
4.1.1 Conventions for test components and PCOs . 8
4.1.2 Conventions for variables and parameters. 9
4.2 Alternative ATM. 10
5 Untestable test purposes.10
6 ATS conventions.11
6.1 Declarations part. 11
6.1.1 Type definitions . 11
6.1.1.1 Simple type definitions . 11
6.1.1.2 Structured type definitions. 11
6.1.1.2.1 TTCN structured type definitions . 11
6.1.1.2.2 ASN.1 structured type definitions. 11
6.1.1.3 ASP type definitions. 12
6.1.1.3.1 TTCN ASP type definitions. 12
6.1.1.3.2 ASN.1 ASP type definitions. 13
6.1.1.4 PDU type definitions . 13
6.1.1.4.1 TTCN PDU type definitions . 13
6.1.1.4.2 ASN.1 PDU type definitions. 13
6.1.2 Test suite constants. 13
6.1.3 Test suite parameters. 13
6.1.4 Variables . 13
6.1.4.1 Test suite variables . 13
6.1.4.2 Test case variables. 13
6.1.5 Test suite operation definitions . 14
6.2 Constraints part. 14
6.2.1 Structured type constraint declaration . 14
6.2.2 ASN.1 type constraint declaration. 14
6.2.2.1 Specification of encoding rules. 15
6.2.3 ASP type constraint declaration . 16
6.2.3.1 ASN.1 ASP type constraint declaration. 16
6.2.3.2 TTCN ASP type constraint declaration . 16
6.2.4 PDU type constraint declaration. 16
6.2.4.1 ASN.1 PDU type constraint declaration . 16
6.2.4.2 TTCN PDU type constraint declaration. 16
6.2.5 Chaining of constraints. 16
6.2.5.1 Static chaining . 16
6.2.5.2 Dynamic chaining. 16
6.2.6 Derived constraints. 17
6.2.7 Parameterized constraints. 17
6.2.8 Value assignment . 17
6.2.8.1 Specific values. 17
6.2.8.2 Matching values. 17
6.3 Dynamic part. 17
6.3.1 Test cases . 17
ETSI
4 EN 300 141-6 V1.2.4 (1998-06)
6.3.2 Test steps. 17
6.3.2.1 PTC1_IN . 17
6.3.2.2 PTC1_OUT . 18
6.3.3 Defaults . 18
7 ATS to TP map .18
8 PCTR conformance.18
9 PIXIT conformance.18
10 ATS conformance .19
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma.20
A.1 Identification summary .20
A.1.1 Protocol conformance test report. 20
A.1.2 IUT identification . 20
A.1.3 Testing environment . 20
A.1.4 Limits and reservations . 21
A.1.5 Comments . 21
A.2 IUT conformance status .21
A.3 Static conformance summary.21
A.4 Dynamic conformance summary.21
A.5 Static conformance review report .22
A.6 Test campaign report.23
A.7 Observations.24
Annex B (normative): Partial PIXIT proforma.25
B.1 Identification summary .25
B.2 Abstract test suite summary .25
B.3 Test laboratory .25
B.4 Client (of the test laboratory).26
B.5 System Under Test (SUT).26
B.6 Protocol information .27
B.6.1 Protocol identification. 27
B.6.2 Parameter values. 27
B.6.3 Sending of messages by IUT. 27
B.6.4 Configuration of IUT . 27
B.7 Basic call PIXIT items .28
B.7.1 Parameter values - information element codings . 28
Annex C (normative): Abstract Test Suite (ATS).29
C.1 The TTCN Graphical form (TTCN.GR).29
C.2 The TTCN Machine Processable form (TTCN.MP) .29
Annex D (informative): General structure of ATS .30
Annex E (informative): Changes with respect to the previous ETS 300 141-6 .31
History.32
ETSI
5 EN 300 141-6 V1.2.4 (1998-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 SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.fr/ipr or 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 6 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Call Hold (HOLD) supplementary
service, 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: 19 June 1998
Date of latest announcement of this EN (doa): 30 September 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 March 1999
Date of withdrawal of any conflicting National Standard (dow): 31 March 1999
ETSI
6 EN 300 141-6 V1.2.4 (1998-06)
1 Scope
This sixth part of EN 300 141 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 [11]) of implementations conforming to the stage three standard for
the Call Hold (HOLD) supplementary service for the pan-European Integrated Services Digital Network (ISDN) by
means of the Digital Subscriber Signalling System No. one (DSS1) protocol, EN 300 141-1 [2].
EN 300 141-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 141-1 [2].
2 Normative references
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case 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] EN 300 403-1: "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]".
[2] EN 300 141-1 (V1.2): "Integrated Services Digital Network (ISDN); Call Hold (HOLD)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1:
Protocol specification".
[3] EN 300 141-2 (V1.2): "Integrated Services Digital Network (ISDN); Call Hold (HOLD)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 2:
Protocol Implementation Conformance Statement (PICS) proforma specification".
[4] EN 300 141-5 (V1.2): "Integrated Services Digital Network (ISDN); Call Hold (HOLD)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test
Suite Structure and Test Purposes (TSS&TP) specification for the network".
[5] EN 300 196-1: "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".
[6] ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 1: General Concepts".
[7] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 2: Abstract Test Suite Specification".
[8] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 3: The Tree and Tabular Combined Notation".
[9] ISO/IEC 9646-4: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 4: Test realization".
ETSI
7 EN 300 141-6 V1.2.4 (1998-06)
[10] ISO/IEC 9646-5: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 5: Requirements on test laboratories and clients for the conformance assessment
process".
[11] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".
[12] CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rules for Abstract
Syntax Notation One (ASN.1)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [6].
Implementation Under Test (IUT): See ISO/IEC 9646-1 [6].
Lower Tester (LT): See ISO/IEC 9646-1 [6].
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [6].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [6].
PICS proforma: See ISO/IEC 9646-1 [6].
Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [6].
PIXIT proforma: See ISO/IEC 9646-1 [6].
System Under Test (SUT): See ISO/IEC 9646-1 [6].
Upper Tester (UT): See ISO/IEC 9646-1 [6].
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
BER Basic Encoding Rules
CM Co-ordination Message
CP Co-ordination Point
ExTS Executable Test Suite
HOLD Call Hold
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
MTC Main Test Component
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SUT System Under Test
TCP Test Co-ordination Procedures
TP Test Purpose
TTCN Tree and Tabular Combined Notation
ETSI
8 EN 300 141-6 V1.2.4 (1998-06)
UT Upper Tester
4 Abstract Test Method (ATM)
4.1 Description of ATM used
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 is 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 one Main Test
Component (MTC) and one or more Parallel Test Components (PTC), see figure 1.
4.1.1 Conventions for test components and PCOs
Master part Slave part
MTCA
PTC1
CPA1
L0 PCO L1 PCO
IUT
NETWORK
Figure 1: Multi-party test method
ETSI
9 EN 300 141-6 V1.2.4 (1998-06)
In a master/slave arrangement, the MTC is considered to be the master while the PTCs 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".
This means, in particular, that the verdict 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 co-ordinates activities by exchanging Co-ordination
Messages (CM) with the PTCs. Secondly it is responsible for the behaviour of the Lower Tester (LT) at PCO L0.
A combination of the remote and multi-party test methods is applied. As can be seen from figure 1, several PCOs are
used. All PCOs reside at the service access points between layers 2 and 3.
SUT
MTC 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
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 PTC PTC1 uses PCO L1.
This PCO is 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 this PCO.
As stated in a previous paragraph, the non-receipt of network generated messages at L0, which are stimulated by events
at the L1, will result in INCONCLUSIVE rather than FAIL verdicts being assigned.
4.1.2 Conventions for variables and parameters
MTCA
call reference CREF1
B channel (basic) bch_num1 (to PTC1)
channel nr (primary) CH_NUM1
PCO L0 IPN0, LIPN0
PTC1
call reference P1CREF
B channel (basic) P1_bch_num
channel nr (primary) P1_CH_NUM
PCO L1 IPN1, LIPN1
ETSI
10 EN 300 141-6 V1.2.4 (1998-06)
4.2 Alternative ATM
As stated in subclause 4.1, an ATS based on a single-party (remote) ATM is possible. Such an ATS may be generated
from the one specified in the present document. The following general steps should be taken:
1) remove all PTC behaviour;
2) remove all CREATE statements;
3) replace CMs which are used to provoke PDUs at the MTC, with implicit send statements.
An example, showing the difference between the multi-party ATM and single-party ATM for a single test case, is given
in tables 1 and 2.
Table 1: Test case dynamic behaviour table using multi-party ATM
TEST CASE DYNAMIC BEHAVIOUR
Test Case Name HOLD_N04_001
Group RemoteUser_ST_OR_T/Holding/
Purpose Ensure that the IUT, while in the Active call state N10, to notify
the non-served user that the call is held
sends a NOTIFY message with a notification indicator coded as
"remote hold" to user B and remains in the Active call state.
Default DF69901(1)
Configuration CONFIG1
Comments 9.2.1 valid optional
Nr | Label| BEHAVIOUR DESCRIPTION | CREF | V | COMMENTS
1 | |CREATE ( PTC1: PTC1_IN_servedUser) | | |
2 | | +PR31002 | | |preamble N10
3 | | CPA1!CP_M START TWAIT |S_HL | |
4 | | L0?NOTIFYr |A_NO20(CREF1,hold_NID) |(P)|
5 | | +CS59901(10,1) | | |check N10
6 | | ?TIMEOUT TWAIT | |(I)|
7 | | +PO49901(1) | | |postamble N0
DETAILED COMMENTS:
Table 2: Test case dynamic behaviour table using single-party ATM
TEST CASE DYNAMIC BEHAVIOUR
Test Case Name HOLD_N04_001
Group RemoteUser_ST_OR_T/Holding/
Purpose Ensure that the IUT, while in the Active call state N10, to notify
the non-served user that the call is held
sends a NOTIFY message with a notification indicator coded as
"remote hold" to user B and remains in the Active call state.
Default DF69901(1)
Configuration
Comments 9.2.1 valid optional
Nr | Label| BEHAVIOUR DESCRIPTION | CREF | V | COMMENTS
1 | |+PR31002 | | |preamble N10
2 | | |NO20(CREF1,hold_NID) | |
3 | | L0?NOTIFYr |A_NO20(CREF1,hold_NID) |(P)|
4 | | +CS59901(10,1) | | |check N10
5 | | ?TIMEOUT TWAIT | |(I)|
6 | | +PO49901(1) | | |postamble N0
DETAILED COMMENTS:
5 Untestable test purposes
There are no test cases for test purposes HOLD_N03_002 to HOLD_N03_003 inclusive. These test cases are not
testable given the ATM utilised. An additional PCO at the served user side (i.e. side of the Master) would be required.
This would be achievable by using two PTCs at the served user side and an MTC whose only function would be to
control the various PTCs.
ETSI
11 EN 300 141-6 V1.2.4 (1998-06)
6 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.
6.1 Declarations part
6.1.1 Type definitions
6.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. BIT STRING, OCTET STRING), 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.
6.1.1.2 Structured type definitions
6.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. BIT STRING,
OCTET STRING), 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.
6.1.1.2.2 ASN.1 structured type definitions
ASN.1 has been used for three major reasons. First, types defined in ASN.1 can model problems that "pure" TTCN
cannot. For instance, data structures modelling ordered or unordered sequences of data are preferably defined in ASN.1.
Second, ASN.1 provides a better restriction mechanism for type definitions by using sub-type definitions. Third, it is
necessary to use ASN.1 to reproduce the type definitions for remote operation components as specified in the base
standards.
The fact that ASN.1 provides a better restriction mechanism for type definitions is used for the purpose of achieving
type-compatibility.
In table 3, the ASN.1 type BIT7OR15 is defined as being of type BIT STRING with a size constraint attached to it. The
size is determined by the value of CR_LENGTH, a test suite parameter. It can have the value of either 7 or 15. The type
BIT7OR15 is used in the structured type CR, field cr_r allowing this type to represent a Basic Access or a Primary Rate
Access call reference. By using this type definition the field cr_r is always type compatible with values of type
BIT STRING (SIZE(7)) and BIT STRING (SIZE(15)). Another approach to solve this problem would be to define the
type BIT7OR15 as BIT STRING (SIZE(7 | 15)). This type has a small disadvantage compared with the previous one. It
is impossible, in run-time, to determine the actual length of any instance of this type.
ETSI
12 EN 300 141-6 V1.2.4 (1998-06)
Table 3: ASN.1 type definition BIT7OR15
ASN.1 Type Definition
Type Name : BIT7OR15
Comments :
Type Definition
BIT STRING(SIZE(CR_LENGTH))
Table 4 shows a typical use of ASN.1. The CHI element will have two different type definitions depending on whether it
represents basic or primary rate access. In TTCN, this needs to be defined as two different types. In ASN.1 this can be
done in one, the type being a choice of either BASIC_CHI or PRIMARY_CHI. These two types are then (locally)
defined in the same table.
Table 4: ASN.1 type definition CHI
ASN.1 Type Definition
Type Name : CHI
Comments : Info Element Channel Identification
EN 300 403-1 clause 4.5.13
Type Definition
CHOICE {
basic BASIC_CHI,
primary PRIMARY_CHI
}
-- Local type definitions --
BASIC_CHI ::= SEQUENCE {
chi_i CHI_I, -- Identifier
chi_l BIT STRING(SIZE(8)), -- Length
chi_e3_cs BIT STRING(SIZE(8)) -- Channel selection
}
PRIMARY_CHI ::= SEQUENCE {
chi_i CHI_I, -- Identifier
chi_l BIT STRING(SIZE(8)), -- Length
chi_e3_p1 BIT STRING(SIZE(4)), -- First nibble of Channel selection
chi_e3_pe BIT STRING(SIZE(1)), -- Preferred/Exclusive Bit
chi_e3_p3 BIT STRING(SIZE(3)), -- Last three bits of Channel selection
chi_e4 BIT STRING(SIZE(8)), -- Channel type
chi_e5_chl BIT STRING(SIZE(1)),
chi_e5_ch2 BIT STRING(SIZE(7)) -- Channel number
}
Table 5 shows an example of how ASN.1 can be used to model unordered sequences.
Table 5: ASN.1 type definition FIES
ASN.1 Type Definition
Type Name : FIES
Comments :
Type Definition
SET OF FIE
The possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from a TTCN type.
6.1.1.3 ASP type definitions
6.1.1.3.1 TTCN ASP type definitions
TTCN ASP type definitions only contain one PDU or no PDU at all. The relationship between an ASP type and a PDU
type is one-to-one. That is, there exists one ASP type definition for each PDU type definition (if that ASP type contains
a PDU).
All TTCN ASP type definitions are provided with a full identifier.
Some ASPs are not parameterized as shown in the example in table 6. Such ASPs are only used for requesting or
receiving service from the lower layer.
ETSI
13 EN 300 141-6 V1.2.4 (1998-06)
Table 6: TTCN ASP type definition DL_REL_IN
TTCN ASP Type Definition
ASP NAME : DL_REL_IN(DL_RELEASE_INDICATION)
PCO Type : SAP
Comments :
Parameter Name | Parameter Type | Comments
Detailed Comments :
Table 7 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and no other
parameters.
Table 7: TTCN ASP type definition DL_DATA_RQ_ALERT
TTCN ASP Type Definition
ASP NAME : DL_DATA_RQ_ALERT(DL_DATA_REQUEST)
PCO Type : SAP
Comments :
Parameter Name | Parameter Type | Comments
mun (MessageUnit) |ALERT_PDU |
Detailed Comments :
6.1.1.3.2 ASN.1 ASP type definitions
There are no ASN.1 ASP type definitions in the ATS.
6.1.1.4 PDU type definitions
6.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.
If a specific PDU type definition contains elements defined in terms of a pre-defined type, that element has a restriction
attached to it.
6.1.1.4.2 ASN.1 PDU type definitions
There are no ASN.1 PDU type definitions in the ATS.
6.1.2 Test suite constants
No test suite constants are used or defined in this ATS.
6.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.
6.1.4 Variables
6.1.4.1 Test suite variables
No test suite variables are used or defined in this ATS.
6.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.
ETSI
14 EN 300 141-6 V1.2.4 (1998-06)
Where test case variables are used in constraints, they are passed as formal parameters.
6.1.5 Test suite operation definitions
The description part of a test suite operation definition uses either natural language or meta C.
Table 8: 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
{
if(basic_flag)
return basic;
else
return primary
}
Detailed comments :
The test suite operation definition shown in table 8 is used in the constraints part when assigning an element of type CHI
a value. As previously described, 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 the CHI type is defined in ASN.1.
This operation is used to assign a value to an element of CHI type. It takes three parameters:
SULPDU\DFRQVWUDLQWRIW\SH&+,YDOLGIRUSULPDU\UDWHDFFHVV
EDVLFDFRQVWUDLQWRIW\SH&+,YDOLGIRUEDVLFDFFHVV
EDVLFBIODJD%RROHDQYDOXH758(LIEDVLFDFFHVVLVDSSOLFDEOH)$/6(RWKHUZLVH
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.
6.2 Constraints part
6.2.1 Structured type constraint declaration
For every structured type definition there exists one or more structured type constraint.
6.2.2 ASN.1 type constraint declaration
Constraints of this type are used to assign the corresponding type a specific value. These constraints are used for the
purpose of modelling unordered data or specific types that cannot be expressed in TTCN.
A value assigned to an element of type SET OF differs depending on whether it is a send or receive constraint.
Table 9: ASN.1 type constraint declaration fIEs (send constraint)
ASN.1 Type Constraint Declaration
Constraint Name : fIEs(comp : Component)
ASN.1 Type : FIE
Derivation Path :
Comments : Send FIE which will contain one component "comp".
Description
{
informationElementIdentifier '00011100'B,
length CALC_FIE_LENGTH(comp),
extBit '1'B,
spareBits '00'B,
protocolProfile '10001'B,
components {comp}
}
Detailed comments :
NOTE 1: The last element in the constraint, components, is of type SET OF Component where Component is
structured data of some type.
ETSI
15 EN 300 141-6 V1.2.4 (1998-06)
If the constraint is a send constraint (as in table 9) the value for the component element is stated as "{comp}" where
comp is an argument received as a parameter. The "{" and "}" turns the value into a SET OF value which is correct
according to that element's type definition.
Table 10: ASN.1 type constraint declaration fIEr (receive constraint)
ASN.1 Type Constraint Declaration
Constraint Name : fIEr(comp : Component)
ASN.1 Type : FIE
Derivation Path :
Comments : A received FIE which can contain several components, but which contains at
least "comp".
Description
{
informationElementIdentifier '00011100'B,
length '????????'B,
extBit '1'B,
spareBits '00'B,
protocolProfile '10001'B,
components SUPERSET({comp})
}
Detailed comments :
NOTE 2: The last element in the constraint, named components, is of type SET OF Component where Component is
structured data of some type.
If the constraint is a receive constraint (as in table 10) the corresponding matching value is assigned by using
SUPERSET. The key-word SUPERSET has an argument that is type compatible with the type definition of that field. In
table 10, the element named components is defined as "SET OF Component" and this implies that the argument to
SUPERSET should be of type SET OF Component. This is achieved the same way as for send constraints, enclosing the
value in curly brackets.
The semantic of SUPERSET is stated in ISO/IEC 9646-3 [8], subclause 11.6.4.7. In short it defines the semantic as
follows: "A value that uses SUPERSET matches the incoming value if, and only if, the incoming value contains at least
all of the elements defined within the SUPERSET, and may contain more elements." This is exactly the semantic
definition used in this ATS.
6.2.2.1 Specification of encoding rules
At the time of specifying this ATS the mechanisms related to encoding of ASN.1 types, specified in DAM-2 of
ISO/IEC 9646-3 [8], were not yet stable. Nevertheless as there is a variation in the encoding rules as applied to ASN.1
types and constraints specified in this ATS, a mechanism is used to differentiate the different encoding rules. Given the
non-finalized status of DAM-2, a solution which is broadly in the spirit of DAM-2 has been created. Comment fields
have been used as a means of including the encoding rules.
For ASN.1 used in this ATS, two variations of encoding rules are used. One is the commonly known Basic Encoding
Rules (BER) as specified in CCITT Recommendation X.209 [12]. In the second case the encoding is according to
ISDN, i.e. the ASN.1 data types are a representation of structures contained within the ISDN specification (basic call,
Generic funct
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...