SIST EN 300 207-6 V3.1.1:2003

SLOVENSKI STANDARD
SIST EN 300 207-6 V3.1.1:2003
01-december-2003
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±'RSROQLOQHVWRULWYH
L]VPHULWHY±3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66±GHO
$EVWUDNWQLSUHVNXãDOQLQL]$76LQGHOQDGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMH
L]YHGEHSURWRNROD3,;,7±3URIRUPDVSHFLILNDFLMD]DRPUHåMH

Integrated Services Digital Network (ISDN); Diversion supplementary services; Digital

Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS)

and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

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

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...............................................................................................................................8

4.1 CDIV network side ATS ....................................................................................................................................8

4.2 SCF network side ATS.......................................................................................................................................9

5 Untestable test purposes...........................................................................................................................9

6 ATS conventions....................................................................................................................................10

6.1 Version of TTCN used .....................................................................................................................................10

6.2 Use of ASN.1...................................................................................................................................................10

6.2.1 Situations where ASN.1 is used..................................................................................................................10

6.2.2 Specification of encoding rules...................................................................................................................10

6.3 Conventions for variables and parameters........................................................................................................11

7 ATS to TP map.......................................................................................................................................12

8 PCTR conformance................................................................................................................................12

9 PIXIT conformance................................................................................................................................12

10 ATS conformance..................................................................................................................................13

11 Configurations required in testing..........................................................................................................13

11.1 General.............................................................................................................................................................13

11.2 CDIV ATS........................................................................................................................................................13

11.3 SCF ATS..........................................................................................................................................................16

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.6.1 Test campaign report for CDIV........................................................................................................................21

A.6.2 Test campaign report for SCF ..........................................................................................................................28

A.7 Observations...........................................................................................................................................31

Annex B (normative): Partial PIXIT proforma...........................................................................................32

B.1 Identification summary...........................................................................................................................32

B.2 Abstract test suite summary ...................................................................................................................32

B.3 Test laboratory........................................................................................................................................32

B.4 Client (of the test laboratory) .................................................................................................................33

B.5 System Under Test (SUT) ......................................................................................................................33

B.6 Protocol information...............................................................................................................................34

B.6.1 Protocol identification......................................................................................................................................34

B.6.2 Parameter values..............................................................................................................................................34

B.6.3 Configuration of IUT........................................................................................................................................35

B.6.3.1 Configuration of the IUT for CDIV testing ................................................................................................35

B.6.3.2 Configuration of the IUT for SCF testing...................................................................................................36

B.6.4 Parameter values..............................................................................................................................................37

B.6.5 Timer values.....................................................................................................................................................38

B.6.6 Void..................................................................................................................................................................38

B.6.7 Interactions.......................................................................................................................................................38

B.7 Basic call PIXIT items ...........................................................................................................................39

B.7.1 Parameter Values - Information element coding ..............................................................................................39

Annex C (normative): Abstract Test Suite (ATS) .......................................................................................40

C.1 The TTCN Graphical form (TTCN.GR) ................................................................................................40

C.2 The TTCN Machine Processable form (TTCN.MP)..............................................................................40

History ..............................................................................................................................................................41

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

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

This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and

The present document is part 6 of a multi-part deliverable covering the Digital Subscriber Signalling System No. one

(DSS1) protocol specification for the Integrated Services Digital Network (ISDN); Diversion supplementary services,

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)

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

The present document specifies the Abstract Test Suites (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 of

implementations conforming to the stage three standard for the diversion supplementary services for the pan-European

Integrated Services Digital Network (ISDN) by means of the Digital Subscriber Signalling System No. one (DSS1)

EN 300 207-5 [3] 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 207-1 [1].

The present document contains two ATSs for different parts of the protocol; one (CDIV) for Call Forwarding Busy,

Call Forwarding Unconditional, Call Forwarding No Response and Call Deflection and the other (SCF) for Selective

Call Forwarding Busy, Selective Call Forwarding Unconditional and Selective Call Forwarding No Response. Common

The following documents contain provisions which, through reference in this text, constitute provisions of the present

• References are either specific (identified by date of publication, edition number, version number, etc.) or

[1] ETSI EN 300 207-1 (V2.0.1): "Integrated Services Digital Network (ISDN); Diversion

supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol;

[2] ETSI EN 300 207-2 (V2.0.1): "Integrated Services Digital Network (ISDN); Diversion

supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol;

Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".

[3] ETSI EN 300 207-5 (V3.1.1): "Integrated Services Digital Network (ISDN); Diversion

supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol;

Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network".

[4] 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)

NOTE: EN 300 207-1 [1] has an undated reference to EN 300 196-1 [4]. Some ASN.1 definitions from

EN 300 196-1 [4] are referenced by EN 300 207-1 and are reproduced in the TTCN ATSs in the present

document. The versions of these definitions used in the present document are based on those in

EN 300 196-1 (V1.3.2). There is a technical change in the definition of PartyNumber in EN 300 196-1

[8] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance

[9] ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformance

[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

[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

[13] ISO/IEC 8825-1: "Information technology - ASN.1 encoding rules: Specification of Basic

Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules

For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-1 [8] apply.

CDIV Call DIVersion (this is used to refer collectively to the CD, CFB, CFNR and CFU services)

SCF Selective Call Forwarding (this is used to refer collectively to the SCFB, SCFNR and SCFU

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.

In practice the behaviour at a single user-network interface does not occur in isolation, but depends on the activity at

The general configuration used is shown in figure 1. In this ATS the PTCs act as slaves to the MTC; all active

behaviour at the PTCs is initiated by CMs sent by the MTC and all verdicts are assigned by the MTC. Not all

For each test case the interface to which the MTC connected is the IUT, which may be the interface of the calling user,

served user or diverted-to user depending on the test group. PTCs are connected to any other interfaces where activity is

necessary. The association between the network interfaces and PTCs that is typically used is described in table 1.

NOTE: In some TCs PCO L2 is connected to the interface of the diverted-to user but no PTC is

The remote test method is applied for the SCF network side ATS as illustrated in figure 2.

The parts of the protocol specific to SCF (i.e. activation, deactivation and interrogation of the SCF services) do not

involve any activity at interfaces of users other than the served user and therefore it is not appropriate to use a

A Point of Control and Observation (PCO) resides at the service access point between layers 2 and 3 in the test system.

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.

Within test cases all communication with the IUT is via PCO L. However in some cases informal test co-ordination is

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 specified in the base

The possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from a TTCN type.

There is a variation in the encoding rules applied to ASN.1 types and constraints specified in this ATS and therefore a

mechanism is needed to differentiate the encoding rules. However the mechanism specified in ISO/IEC 9646-3 [10]

does not facilitate definition of the encoding rules as needed for this ATS. A solution is therefore used which is broadly

in the spirit of ISO/IEC 9646-3 [10] in which comment fields have been used as a means of 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 ISO/IEC 8825-1 [13]. 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 functional

protocol or individual supplementary service). For example, if octets of an information element are specified in ASN.1

as a SEQUENCE then this should be encoded in an Executable Test Suite (ETS) as any other ISDN information

element specified using tabular TTCN. This ISDN encoding variation is the default encoding rule for this ATS. This

means that all ASN.1 constraint tables are encoded using ISDN (non-BER) encoding unless stated otherwise. BER

encoding should never be applied to an ASN.1 constraint where BER encoding has not been specified. This encoding

For BER encoding, an indication is given in the comments field of the table header. For this ATS such indications

appear in the ASN.1 type constraint declaration tables only. In the first line of the table header comment field, the

Note that within BER, there are a number of variations for the encoding of lengths of fields. According to

EN 300 196-1 [4], an IUT should be able to interpret all length forms within BER for received PDUs. When sending

PDUs containing BER encoding, EN 300 196-1 [4] gives guidelines but makes no restrictions on the length forms

In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER.

The identifiers used for the TPs are reused as test case names. Thus there is a straightforward one-to-one mapping.

A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [12], to

produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [12].

Furthermore, a test laboratory, offering testing for either ATS specification contained in annex C, when requested by a

client to produce a PCTR, is required to produce a PCTR conformant with the PCTR proforma contained in annex A.

A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering of the clauses

contained in annex A except that either A.6.1 or A.6.2 may be omitted. Clause A.6 of the PCTR may contain additional

columns. If included, these shall be placed to the right of the existing columns. Text in italics may be reta