SIST EN 300 130-4 V1.3.2:2005

• Abstract:

  To handle comments and incorporate appropriate corrections into the ATS of DSS1 L2

• Status: Published
• Publication Date: 31-Mar-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-Apr-2005
• Due Date: 01-Apr-2005
• Completion Date: 01-Apr-2005
• Ref Project: ETSI EN 300 130-4 V1.3.2 (2000-06) - Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user

SIST EN 300 130-4 V1.3.2:2005 is the Slovenian adoption of ETSI EN 300 130-4 V1.3.2. It specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user side of the Integrated Services Digital Network (ISDN) Malicious Call Identification (MCID) supplementary service over the Digital Subscriber Signalling System No. one (DSS1) protocol. The document is meant for implementers, test laboratories, and clients who need to assess conformance at the T reference point or a coincident S and T reference point.

What does SIST EN 300 130-4 V1.3.2:2005 specify?

SIST EN 300 130-4 V1.3.2:2005 defines the test artefacts for conformance assessment of the MCID user-side DSS1 implementation. Its scope is limited to the ATS and partial PIXIT proforma for the user side, and it points to the protocol specification in part 1 and the test purposes in part 3.

The document is organized into clauses 1 to 10 and five annexes. Clauses 1 to 3 set the scope, references, and terms; clauses 4 to 7 describe the abstract test method, ATS conventions, and the mapping from test purposes to test cases; clauses 8 to 10 state conformance expectations for reports, PIXIT, and the ATS itself.

Annex	What it covers
Annex A	Protocol Conformance Test Report (PCTR) proforma
Annex B	Partial PIXIT proforma
Annex C	Abstract Test Suite (ATS)
Annex D	General structure of an ATS
Annex E	Change record

What are the key requirements of SIST EN 300 130-4 V1.3.2:2005?

Test method and verdicts

Clause 4 uses the remote test method. The point of control and observation (PCO) is at the service access point between layers 2 and 3, and it is named L. In practice, this means verdicts are based on what the tester observes at the lower interface of the implementation under test (IUT).

Clause 4 also introduces an O PCO for test co-ordination procedures above the IUT. That PCO controls the test flow but does not contribute to verdict assignment, so it helps the ATS describe operator actions clearly without turning them into pass/fail evidence.

Clause 5 states that there are no untestable test purposes associated with this ATS. For a user, that means the ATS is intended to cover the stated test purposes directly.

ATS conventions and encoding

Clause 6 sets out how the ATS is written in TTCN and ASN.1 terms. It distinguishes simple types, structured types, ASPs, PDUs, test suite parameters, variables, and test suite operations, so an executable suite can be built from the abstract description.

A key practical point is the encoding rule treatment for ASN.1. The default encoding in this ATS is the ISDN-style encoding used for information elements in the standard, not BER, unless a table explicitly says BER. Where BER is used, the implementer is expected to vary the length form sent to the IUT so that indefinite, short definite, and long definite forms are exercised during a test campaign.

Clause 6 also uses matching conventions such as AnyOrOmit, AnyValue, Omit, AnyOne, and AnyOrNone. In practice, these let a test case accept a permitted range of received values without losing the exact structure needed for conformance checking.

Data handling and test structure

Clause 6.2.2 shows how ASN.1 is used for structured data such as the FIE type and for receive matching with SUPERSET. That matters because the ATS can match a received information element that contains at least the required components, while still allowing additional components.

Clause 6.2.3 and 6.2.4 define a one-to-one relationship between TTCN ASPs and PDUs. Each ASP carries one specific PDU, which makes the test encoding unambiguous and easier to realize in an executable test system.

Clause 6.2.5 uses static chaining and semi-dynamic chaining. This is a practical way of passing parameter values through a test structure, such as selecting the correct Channel Identification Information Element based on the access type being tested.

Clause 6.3 says that each test case contains the test purpose text from part 3, and that test steps are used to avoid repeating dynamic behavior. The ATS also uses RETURN in defaults to handle valid background behavior and then resume the original alternatives.

Conformance, reporting, and realization

Clause 7 gives a one-to-one mapping between test purpose identifiers and test case names. For users of the ATS, that makes it straightforward to trace a test case back to the corresponding purpose in part 3.

Clauses 8 to 10 set the obligations for conformance artefacts. A PCTR produced from this ATS has to follow the proforma in Annex A, an augmented partial PIXIT has to be technically equivalent to Annex B, and an ExTS based on Annex C has to preserve the technical content and realizability of the abstract test cases.

What terms does SIST EN 300 130-4 V1.3.2:2005 define?

• Abstract Test Suite (ATS) - the set of abstract test cases and associated data used to specify conformance tests.
• Implementation Under Test (IUT) - the protocol implementation being exercised by the test suite.
• Lower Tester (LT) - the tester role that interacts with the IUT at the lower interface.
• Point of Control and Observation (PCO) - the interface at which the tester controls and observes behavior.
• Protocol Implementation Conformance Statement (PICS) - the statement that describes which protocol options an implementation supports.
• Protocol Implementation eXtra Information for Testing (PIXIT) - the extra implementation-specific information needed to realize tests.
• System Under Test (SUT) - the full system arrangement that includes the IUT and its test context.
• Upper Tester (UT) - the tester role used for co-ordination above the IUT.

Who uses SIST EN 300 130-4 V1.3.2:2005?

SIST EN 300 130-4 V1.3.2:2005 is used by test laboratories that need to run conformance tests and prepare a PCTR or PIXIT for MCID implementations. It is also used by test realizers who build the Means Of Testing (MOT) and the Executable Test Suite (ExTS) from the abstract suite.

Implementers of user-side ISDN equipment use it to understand what data and behavior their product must expose to be testable. Quality managers and buyers use it to check that a supplier’s conformance claims can be assessed against a defined ATS and reporting structure.

What changed in SIST EN 300 130-4 V1.3.2:2005 from the previous edition?

The change record states that EN 300 130-4 V1.3 was a revised ATS. It also states that the earlier version was converted to EN layout, that references to ETS 300 102-1 were replaced with EN 300 403-1, and that non-specific references were changed where the latest version was intended.

Which standards are used with SIST EN 300 130-4 V1.3.2:2005?

Standard	What it contributes
ETSI EN 300 130-1	The protocol specification for MCID DSS1 that the ATS tests against
ETSI EN 300 130-2	The PICS proforma used for static conformance checking
ETSI EN 300 130-3	The test purposes that are reused as test case names
ETSI EN 300 196-1	The generic supplementary service protocol basis, including BER guidance and component structure
ETSI EN 300 403-1	The DSS1 network layer context for circuit-mode basic call control
ISO/IEC 9646-1	Core conformance testing concepts and definitions
ISO/IEC 9646-2	Abstract test suite specification and the remote test method framework
ISO/IEC 9646-3	TTCN notation, matching semantics, and encoding-related concepts
ISO/IEC 9646-4	Requirements for test realization and ExTS construction
ISO/IEC 9646-5	Requirements for test laboratories, clients, PCTR, and PIXIT
ITU-T Recommendation I.411	Reference configurations for ISDN user-network interfaces
CCITT Recommendation X.209	Basic Encoding Rules (BER) for ASN.1

What does the SIST EN 300 130-4 V1.3.2:2005 document contain?

The document contains a formal ATS in Annex C, with both TTCN graphical and machine-processable forms. Annex A gives a structured PCTR proforma for reporting test results, and Annex B gives the partial PIXIT questions and fields needed before testing.

Clause 6 explains the test suite’s type system, constraints, matching rules, and encoding conventions, including how ASN.1 and TTCN are combined. Annex D shows the usual structure of a supplementary service ATS, and Annex E records the changes between versions.

SLOVENSKI STANDARD
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHY
LGHQWLILNDFLMD]ORQDPHUQHJDNOLFD0&,'3URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQGRGDWQD
LQIRUPDFLMD]DSUHVNXãDQMHGHOQHL]YHGEHSURWRNROD3,;,73URIRUPD
VSHFLILNDFLMD]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma specification for the user
Ta slovenski standard je istoveten z: EN 300 130-4 Version 1.3.2
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);
Malicious Call Identification (MCID) supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user
�
2 ETSI EN 300 130-4 V1.3.2 (2000-06)
Reference
REN/SPS-05162-4
Keywords
ISDN, DSS1, supplementary service, MCID, ATS,
PIXIT, user
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - 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
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:
[e-mail]
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 130-4 V1.3.2 (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 Abstract Test Method (ATM) .8
5 Untestable test purposes.8
6 ATS conventions.8
6.1 Declarations part .8
6.1.1 Type definitions .8
6.1.1.1 Simple type definitions.8
6.1.1.2 Structured type definitions .9
6.1.1.2.1 TTCN structured type definitions.9
6.1.1.2.2 ASN.1 structured type definitions.9
6.1.1.3 ASP type definitions.10
6.1.1.3.1 TTCN ASP type definitions.10
6.1.1.3.2 ASN.1 ASP type definitions .11
6.1.1.4 PDU type definitions.11
6.1.1.4.1 TTCN PDU type definitions.11
6.1.1.4.2 ASN.1 PDU type definitions .11
6.1.2 Test suite constants .11
6.1.3 Test suite parameters .11
6.1.4 Variables.11
6.1.4.1 Test suite variables.11
6.1.4.2 Test case variables .11
6.1.5 Test suite operation definitions.11
6.2 Constraints part.12
6.2.1 Structured type constraint declaration.12
6.2.2 ASN.1 type constraint declaration .12
6.2.2.1 Specification of encoding rules .13
6.2.3 ASP type constraint declaration.14
6.2.3.1 ASN.1 ASP type constraint declaration .14
6.2.3.2 TTCN ASP type constraint declaration.14
6.2.4 PDU type constraint declaration .14
6.2.4.1 ASN.1 PDU type constraint declaration.14
6.2.4.2 TTCN PDU type constraint declaration .14
6.2.5 Chaining of constraints .14
6.2.5.1 Static chaining.14
6.2.5.2 Dynamic chaining.14
6.2.6 Derived constraints .15
6.2.7 Parameterized constraints .15
6.2.8 Value assignment.15
6.2.8.1 Specific values .15
6.2.8.2 Matching values .15
6.3 Dynamic part .15
6.3.1 Test cases.15
6.3.2 Test steps .15
6.3.3 Defaults.16
ETSI
4 ETSI EN 300 130-4 V1.3.2 (2000-06)
7 ATS to TP map.16
8 PCTR conformance.16
9 PIXIT conformance.16
10 ATS conformance .16
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma.17
A.1 Identification summary .17
A.1.1 Protocol conformance test report.17
A.1.2 IUT identification.17
A.1.3 Testing environment.17
A.1.4 Limits and reservations.18
A.1.5 Comments.18
A.2 IUT conformance status .18
A.3 Static conformance summary.18
A.4 Dynamic conformance summary.18
A.5 Static conformance review report .19
A.6 Test campaign report.19
A.7 Observations.19
Annex B (normative): Partial PIXIT proforma.20
B.1 Identification summary .20
B.2 Abstract test suite summary .20
B.3 Test laboratory .20
B.4 Client (of the test laboratory).21
B.5 System Under Test (SUT).21
B.6 Protocol information .22
B.6.1 Protocol identification .22
B.6.2 Parameter values.22
B.6.3 Sending of messages by IUT .22
B.6.4 Timer values.22
Annex C (normative): Abstract Test Suite (ATS).23
C.1 The TTCN Graphical form (TTCN.GR).23
C.2 The TTCN Machine Processable form (TTCN.MP) .23
Annex D (informative): General structure of ATS.24
Annex E (informative): Change record.25
E.1 Changes between EN 300 130-4 V1.2 and V1.3.25
E.2 Changes between ETS 300 130-4 and EN 300 130-4 V1.2 .25
History.26
ETSI
5 ETSI EN 300 130-4 V1.3.2 (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 and
Protocols for Advanced Networks (SPAN).
The present document is part 4 of a multi-part standard covering the Integrated Services Digital Network (ISDN);
Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one (DSS1)
protocol, 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 130-4 V1.3.2 (2000-06)
1 Scope
This fourth part of EN 300 130 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra
Information for Testing (PIXIT) proforma for the User side of the T reference point or coincident S and T reference
point (as defined in ITU-T Recommendation I.411 [12]) of implementations conforming to the stage three standard for
the Malicious Call Identification (MCID) 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 130-1 [2].
EN 300 130-3 [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 Network side
of the T reference point or coincident S and T reference point of implementations conforming to EN 300 130-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 ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface
layer 3; Specifications for basic call control".
[2] ETSI EN 300 130-1 (V1.2): "Integrated Services Digital Network (ISDN); Malicious Call
Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 1: Protocol specification".
[3] ETSI EN 300 130-2 (V1.2): "Integrated Services Digital Network (ISDN); Malicious Call
Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma
specification".
[4] ETSI EN 300 130-3 (V1.2): "Integrated Services Digital Network (ISDN); Malicious Call
Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the
user".
[5] ETSI 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] ETSI 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]".
[7] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[8] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract test suite specification".
[9] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
ETSI
7 ETSI EN 300 130-4 V1.3.2 (2000-06)
[10] ISO/IEC 9646-4: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization".
[11] ISO/IEC 9646-5: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test laboratories and clients for the
conformance assessment process".
[12] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".
[13] 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 terms and definitions apply:
Abstract Test Suite (ATS): see ISO/IEC 9646-1 [7].
Implementation Under Test (IUT): see ISO/IEC 9646-1 [7].
Lower Tester (LT): see ISO/IEC 9646-1 [7].
Point of Control and Observation (PCO): see ISO/IEC 9646-1 [7].
Protocol Implementation Conformance Statement (PICS): see ISO/IEC 9646-1 [7].
PICS proforma: see ISO/IEC 9646-1 [7].
Protocol Implementation eXtra Information for Testing (PIXIT): see ISO/IEC 9646-1 [7].
PIXIT proforma: see ISO/IEC 9646-1 [7].
System Under Test (SUT): see ISO/IEC 9646-1 [7].
UpperTester(UT): see ISO/IEC 9646-1 [7].
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
ExTS Executable Test Suite
IUT Implementation Under Test
LT Lower Tester
MCID Malicious Call Identification
MOT Means Of Testing
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
SUT System Under Test
TCP Test Co-ordination Procedures
TP Test Purpose
TTCN Tree and Tabular Combined Notation
UT Upper Tester
ETSI
8 ETSI EN 300 130-4 V1.3.2 (2000-06)
4 Abstract Test Method (ATM)
The remote test method is applied for the MCID user ATS. The Point of Control and Observation (PCO) resides at the
service access point between layers 2 and 3. This PCO is named "L" (for Lower). The L PCO is used to control and
observe the behaviour of the Implementation Under Test (IUT) and test case verdicts are assigned depending on the
behaviour observed at this PCO.
Tester SUT
LT IUT
PCO
Layer 2 Layer 2
Layer 1 Layer 1
Service provider
Figure 1: Remote test method
ISO/IEC 9646-2 [8] allows the informal expression of Test Co-ordination Procedures (TCP) between the System Under
Test (SUT) upper layer(s) and the Lower Tester (LT). In the ATS contained in annex C, TCP is achieved by use of a
second "informal" PCO, called "O" (for Operator). This PCO is used to specify control but not observation above the
IUT and consequently, events at this PCO are never used to generate test case verdicts. The use of this O PCO is
regarded as a preferred alternative to the use of the implicit send event, in that it allows the ATS to specify in a clear and
meaningful way what actions are required to be performed on the IUT.
5 Untestable test purposes
There are no untestable test purposes associated with this ATS.
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.
ETSI
9 ETSI EN 300 130-4 V1.3.2 (2000-06)
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:
1) 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;
2) ASN.1 provides a better restriction mechanism for type definitions by using sub-type definitions;
3) 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.
Tables 1 and 2 show the typical use of ASN.1. The FIE type in table 1 is written in ASN.1 to permit the use of the SET
OF construction in the components field. Constraints of the FIE type can therefore be written using the SUPERSET
function which allows to match a single component which may be delivered together with a set of other components.
Table 2 shows the reject component type which is defined following the ASN.1 declaration in EN 300 196-1 [5].
Table 1: ASN.1 type definition FIE
ASN.1 Type Definition
Type Name : FIE
Comments : Facility information element taken from EN 300 196; 11.2.2.1.
Specified here for both send & receive event.
Type Definition
SEQUENCE {
informationElementIdentifier FIE_I,
length FIE_LengthType,
extBit BIT STRING (SIZE (1)),
spareBits BIT STRING (SIZE (2)),
protocolProfile BIT STRING (SIZE (5)),
components SET OF Component }
ETSI
10 ETSI EN 300 130-4 V1.3.2 (2000-06)
Table 2: ASN.1 type definition RejectComponent
ASN.1 Type Definition
Type Name : RejectComponent
Comments : Reject Component is not specific to any particular operation. The invokeID may be
used to identify a specific operation.
Type Definition
SEQUENCE {
invokedID CHOICE {
invokeID InvokeIDType,
null NULL },
problem CHOICE {
generalProblem [0] IMPLICIT GeneralProblem,
invokeProblem [1] IMPLICIT InvokeProblem,
returnResultProblem [2] IMPLICIT ReturnResultProblem,
returnErrorProblem [3] IMPLICIT ReturnErrorProblem } }
Table 3 shows an example of how ASN.1 can be used to model unordered sequences.
Table 3: 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 4. Such ASPs are only used for requesting or
receiving service from the lower layer.
Table 4: 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 5 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and no other
parameters.
Table 5: 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 :
ETSI
11 ETSI EN 300 130-4 V1.3.2 (2000-06)
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.
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 6: 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 :
ETSI
SIST
...