ETSI EN 300 207-6 V3.2.1 (2003-01)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.L]VPHULWYHQHSUHVNXãDQMHIntegrated 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 specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 207-6 Version 3.2.1SIST EN 300 207-6 V3.2.1:2004en01-april-2004SIST EN 300 207-6 V3.2.1:2004SLOVENSKI
STANDARD
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 2
Reference REN/SPAN-130300 Keywords ATS, DSS1, ISDN, network, PIXIT, supplementary service, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - 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
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://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editor@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 2003. All rights reserved.
DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 3
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.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.11 8 PCTR conformance.12 9 PIXIT conformance.12 10 ATS conformance.12 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.18 A.1 Identification summary.18 A.1.1 Protocol conformance test report.18 A.1.2 IUT identification.18 A.1.3 Testing environment.19 A.1.4 Limits and reservations.19 A.1.5 Comments.19 A.2 IUT conformance status.19 A.3 Static conformance summary.19 A.4 Dynamic conformance summary.20 A.5 Static conformance review report.20 A.6 Test campaign report.20 A.6.1 Test campaign report for CDIV.20 A.6.2 Test campaign report for SCF.27 A.7 Observations.30 Annex B (normative): Partial PIXIT proforma.31 B.1 Identification summary.31 SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 4
B.2 Abstract test suite summary.31 B.3 Test laboratory.31 B.4 Client (of the test laboratory).32 B.5 System Under Test (SUT).32 B.6 Protocol information.33 B.6.1 Protocol identification.33 B.6.2 Parameter values.33 B.6.3 Configuration of IUT.34 B.6.3.1 Configuration of the IUT for CDIV testing.34 B.6.3.2 Configuration of the IUT for SCF testing.36 B.6.4 Parameter values.37 B.6.5 Timer values.37 B.6.6 Void.38 B.6.7 Interactions.38 B.7 Basic call PIXIT items.38 B.7.1 Parameter Values - Information element coding.38 Annex C (normative): Abstract Test Suite (ATS).39 C.1 The TTCN Graphical form (TTCN.GR).39 C.2 The TTCN Machine Processable form (TTCN.MP).39 Annex D (informative): Changes between EN 300 207-6 V3.1.1 and V1.2.3.40 D.1 Changes between EN 300 207-6 V3.2.1 and V3.1.1.40 History.41
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 5
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://webapp.etsi.org/IPR/home.asp). All published ETSI deliverables shall include information which directs the reader to the above source of information. 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 6 of a multi-part deliverable covering the Integrated Services Digital Network (ISDN); Diversion supplementary services; 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: 27 December 2002 Date of latest announcement of this EN (doa): 31 March 2003 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
30 September 2003 Date of withdrawal of any conflicting National Standard (dow): 30 September 2003
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 6
1 Scope 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) protocol, EN 300 207-1 [1]. 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 parts of the protocol are covered by the CDIV ATS. 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 and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference/. [1] ETSI EN 300 207-1: "Integrated Services Digital Network (ISDN); Diversion supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1: Protocol specification". [2] ETSI EN 300 207-2: "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: "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) protocol; Part 1: Protocol specification". 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. There is a technical change in the definition of PartyNumber in EN 300 196-1 which has no impact on the present document. [5] 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]". SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 7
[6] ETSI EN 300 403-3: "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 097-1: "Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1: Protocol specification". [8] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [9] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification". [10] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)". [11] ISO/IEC 9646-4: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 4: Test realization". [12] 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". [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 (DER)". (See also ITU-T Recommendation X.690: (1994)). 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-1 [8] apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite BER Basic Encoding Rules CD Call Diversion CDIV Call DIVersion (this is used to refer collectively to the CD, CFB, CFNR and CFU services) CFB Call Forward Busy CFNR Call Forward No Reply CFU Call Forward Unconditional ETS Executable Test Suite IUT Implementation Under Test LT Lower Tester MOT Means Of Testing MTC Main Test Component PCO Point of Control and Observation PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing PTC Parallel Test Component SCF Selective Call Forwarding
NOTE: This is used to refer collectively to the SCFB, SCFNR and SCFU services. SCFB Selective Call Forwarding Busy SCFNR Selective Call Forwarding No Reply SCFU Selective Call Forwarding Unconditional SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 8
SUT System Under Test TP Test Purpose TTCN Tree and Tabular Combined Notation 4 Abstract Test Method 4.1 CDIV network side ATS The multi-party test method is applied for the CDIV network side ATS. 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 other user-network interfaces. Therefore a multi-party test method is used. 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 components are used in every test case.
MTC
PTC3
CPA3
PTC2
CPA2
PTC1
CPA1
PCO L0
PCO L1
PCO L2
PCO L3
IUT
Interface to other user 1 Interface to other User 2 Interface to other User 3
Network
Figure 1: Multi-party test method 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. SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 9
Table 1: Association of test components with interfaces
Calling user (First) served user Second served user Diverted-to user Calling user tests - one diversion MTC PTC1
PTC2 Calling user tests - two diversions MTC PTC1 PTC2 PTC3 Served user tests - activation, deactivation and interrogation
MTC
Served user tests - one diversion PTC1 MTC
PTC2 (see note) Served user tests - two diversions PTC1 PTC2 MTC PTC3 Called user tests - one diversion PTC1 PTC2
MTC Called user tests - two diversions PTC3 PTC1 PTC2 MTC NOTE: In some TCs PCO L2 is connected to the interface of the diverted-to user but no PTC is associated with that PCO.
4.2 SCF network side ATS 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 multi-party test method. 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 performed by re-configuration of the IUT between test cases. Tester
SUT
LT
IUT PCO L
Layer 2
Layer 2 Layer 1
Layer 1 Service provider
Figure 2: Remote test method 5 Untestable test purposes There are no untestable test purposes associated with these ATSs. SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 10 6 ATS conventions 6.1 Version of TTCN used The version of TTCN used is that defined in ISO/IEC 9646-3 [10]. 6.2 Use of ASN.1 6.2.1 Situations where ASN.1 is used 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 standards in ASN.1. 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.2.2 Specification of encoding rules 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 rule is sometimes named "Direct 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 notation "ASN1_Encoding: BER" is used. 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 within BER which an IUT may apply. In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER. SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 11 Table 2: ASN.1 type constraint declaration showing use of encoding variation ASN.1 Type Constraint Declaration Constraint Name : Beg3PTYinv ASN.1 Type
: Component Derivation Path
: Comments
: ASN1_Encoding: BER
Receive component: Begin3PTY invoke component Description begin3PTY_Components
begin3PTY_InvokeComp
{ invokeID
? ,
operation_value
localValue
4} Detailed comments:
6.3 Conventions for variables and parameters This is applicable to the CDIV ATS only (no calls are used in the SCF ATS). MTCA
call reference CREF1 B channel (basic) bch_num1 channel number (primary) CH_NUM1
PCO L0 IPN0, LIPN0
PTC1
call reference P1_CREF B channel (basic) P1_bch_num channel number (primary) P1_CH_NUM
PCO L1 IPN1, LIPN1
PTC2
call reference P2_CREF B channel (basic) P2_bch_num channel number (primary) P2_CH_NUM
PCO L2 IPN2, LIPN2
PTC3
call reference P3_CREF B channel (basic) P3_bch_num channel number (primary) P3_CH_NUM
PCO L3 IPN3, LIPN3
7 ATS to TP map The identifiers used for the TPs are reused as test case names. Thus there is a straightforward one-to-one mapping. SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 12 8 PCTR conformance 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 clauses 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 retained by the test laboratory. 9 PIXIT conformance A test realizer, producing an executable test suite for either ATS specification contained in annex C, is required, as specified in ISO/IEC 9646-4 [11], to produce an augmented partial PIXIT proforma conformant with this partial PIXIT proforma specification. An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents which are technically equivalent to annex B except as indicated below. The augmented partial PIXIT proforma may contain additional questions that need to be answered in order to prepare the Means Of Testing (MOT) for a particular IUT. A test laboratory, offering testing for either ATS specification contained in annex C, is required, as specified in ISO/IEC 9646-5 [12], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma conformant with this partial PIXIT proforma specification. A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents which are technically equivalent to annex B except as indicated below. The PIXIT proforma may contain additional questions that need to be answered in order to prepare the test laboratory for a particular IUT. In an augmented partial PIXIT proforma or PIXIT proforma applicable to testing to only one of the ATSs in the present document the items in annex B for which responses are only required for testing to the other ATS may be omitted. 10 ATS conformance The test realizer, producing MOT and ETS for this ATS specification, shall comply with the requirements of ISO/IEC 9646-4 [11]. In particular, these concern the realization of an ETS based on each ATS. The test realizer shall provide a statement of conformance of the MOT to this ATS specification. An ETS which conforms to this ATS specification shall contain test groups and test cases which are technically equivalent to those contained in at least one ATS in annex C. All sequences of test events comprising an abstract test case shall be capable of being realized in the executable test case. Any further checking which the test system might be capable of performing is outside the scope of this ATS specification and shall not contribute to the verdict assignment for each test case. Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [12]. A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS. SIST EN 300 207-6 V3.2.1:2004

ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 13 11 Configurations required in testing 11.1 General There are potentially a number of ways that the IUT can be configured (e.g. with different subscription options) and a number of test cases are applicable only to one or a subset of the configurations that a particular IUT may support. There are also a number of test purposes which require the IUT to be specially configured so that exception conditions which do not occur as a result of protocol action can be tested. The conditions can be considered in five groups: • subscription options; • network provider options; • number of screening lists (SCF only); • special conditions incompatible with normal operation; and • special conditions compatible with normal operation. 11.2 CDIV ATS Tables 3 to 6 describe configurations relating to subscription options and network provider options. For the purposes of overall test case selection the test suite parameters relating to all the configurations supported (as identified in the PIXIT) shall be TRUE. During test suite execution the parameters describing the actual configuration of the IUT shall be true (this includes one and only one of the parameters listed in each of tables 3, 4 and 6). Any test cases which require different configurations are deselected. If more than one configuration is supported then it is necessary to re-configure the IUT and change the parameters in order to run all the test cases. NOTE 1: Certain parameters are used for test case parameterization as well as selection. NOTE 2: All test cases concerning specific call forwarding supplementary services assume that the service concerned is subscribed, except where indicated in the tables below. In addition many test cases (not specifically concerning CFU) assume that CFU is supported and subscribed. NOTE 3: Certain test cases assume that other supplementary services (e.g. DDI, SUB) are provided and subscribed if it is indicated in the PIXIT that they are supported. NOTE 4: Certain test cases other than those listed in table 4 assume that MSN is provided if it is indicated that it is supported in the PIXIT. An exception is CDIV_N10_001 which requires MSN not to be provided. Table 3: SUT configurations for subscription options - Calling user test cases Test cases Calling user is notified of diversion Test suite parameter PIXIT reference CDIV_N01_002 - 005 Yes (with or without diverted-to number) PX_2_27 OR PX_2_28 2.27 or 2.28 CDIV_N02_001, 002 Yes, without diverted to number, or No PX_2_28 OR PX_2_29 2.28 or 2.29 CDIV_N02_003 - 008 Yes, with diverted to number PX_2_27 2.27
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 14 Table 4: SUT configurations for subscription options - Served user test cases Test Cases (see note 1) CDIV service subscription MSN (see note 3)
Activation, deactivation and interrogation for all ISDN-numbers on the same access (see note 3) Test suite parameter PIXIT ref. CDIV_N03_001,002, 008, 009, 024 CDIV_N04_001,002, 008, 009, 019 CDIV_N06_001,2 Whole access * N/A PX_2_1 2.1 CDIV_N03_003,004,010,011 CDIV_N04_003,004,010,011 CDIV_N06_003, 004 Per ISDN number No * PX_2_2 2.2 CDIV_N03_005, 012 CDIV_N04_005, 012 CDIV_N06_006 Per ISDN number Yes * PX_2_3 OR PX_2_4 2.3 or 2.4 CDIV_N03_006 CDIV_N04_006 CDIV_N06_6 Per ISDN number Yes No PX_2_3 2.3 CDIV_N03_007, 013 CDIV_N04_007, 013 CDIV_N07_007 Per ISDN number Yes Yes PX_2_4 2.4 CDIV_N03_025, 026 CDIV_N04_020, 021 CDIV_N06_014, 015 DDI range N/A Any PX2_5 OR PX_2_6 2.5 or 2.6 CDIV_N03_027 CDIV_N04_022 CDIV_N06_016 DDI range N/A No PX_2_5 2.5 CDIV_N03_028 CDIV_N04_023 CDIV_N06_017 DDI range N/A Yes PX_2_6 2.6 CDIV_N03_014 CDIV_N04_014 CDIV_N05_004 CDIV_N06_009 CDIV_N11_025, 034, 043 CDIV_N17_010, 018, 026 Not subscribed for any basic service (see note 2) * N/A PX_2_7 (CFB) PX_2_8 (CFNR) PX_2_9 (CFB) PX_2_20 (CD) 2.7, 2,8, 2.9 2.20 CDIV_N03_015 CDIV_N04_015 CDIV_N06_010 CDIV_N11_026, 035, 044 CDIV_N17_011, 019, 027 Not available for any basic service (see note 2) * N/A PX_2_10 (CFB, CFU, CFNR) PX_2_21 (CD) 2.10
2.21 NOTE 1: "N03", "N04" and "N06" include each of the subgroups for cfu, cfnr and cfb. NOTE 2: For test cases in groups N03, N04, N06 and N11 the service that the test case concerns needs to be not subscribed or not available. For CDIV_N05_004 all of CFB, CFNR and CFU need to be not subscribed. For test cases in group N17 CFU needs to be not subscribed or not available. NOTE 3: "*" indicates that either value of the option may be used.
Table 5: SUT configurations for subscription and network provider options - miscellaneous Test cases Option Value Test suite parameter PIXIT reference CDIV_N07_001 - 009 CDIV_N08_001 - 009 CDIV_N09_001 - 003 CDIV_N10_001 - 003, 011 Served user receives notification that a call has been forwarded. Yes, with call offering information PX_2_15 2.15 CDIV_N11_031, 040, 049 CDIV_N17_017, 025, 033 Maximum number of diversions for a single call. 1 PX_2_22 2.22 CDIV_N12_001 Served user receives notification in outgoing calls that forwarding is currently activated. Yes PX_2_23 2.23
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 15 Table 6: SUT configurations for network provider option Test cases Served user call retention on invocation of diversion Test suite parameter PIXIT reference CDIV_N10_004 CDIV_N11_001 - 003 CDIV_N17_007 - 009 Clear call on invocation. PX_2_18 2.18 CDIV_N10_005 - 010 CDIV_N11_004 - 009, 011 - 024 CDIV_N17_001 - 006, 034 - 036 CDIV_N18_002 Retain call until alerting begins at diverted-to user. PX_2_19 2.19
Table 7 describes the configurations relating to special conditions. Some of these are considered to be incompatible with normal operation. For the purposes of test case selection the test suite parameters relating to all the configurations supported (as identified in the PIXIT) shall be TRUE. During test suite execution the parameters describing the actual configuration of the IUT shall be true. Those test cases which require special conditions for which the IUT is not configured are deselected. Generally it will be necessary to re-configure the IUT and change the parameters in order to run all the test cases. NOTE 5: Test cases not requiring special conditions are not deselected when the parameter indicates that the IUT is configured for a special condition. Table 7: SUT configurations for special conditions Test cases (see note) Configuration Test suite parameter PIXIT reference CDIV_N03_019 CDIV_N17_013, 021, 029 An attempt to activate diversion is to be unsuccessful due to a resources being unavailable. PX_2_11 2.11 CDIV_N05_005 Requested interrogation information is not available. PX_2_13 2.13 CDIV_N05_006 CDIV_N06_011 Requested interrogation information exceeds the maximum allowed length. PX_2_14 2.14 CDIV_N08_005, 006 Presentation of the calling address is not restricted. PX_2_16 2.16 CDIV_N03_017 Activation of CDIV prevented by supplementary service interaction. PX_2_17 2.17 CDIV_N02_007, 008 CDIV_N13_003 Diverted to number is "not available" due to interworking. PX_2_24 2.24 CDIV_N17_037 On receipt of a SETUP message the IUT sends a CallRerouteing invoke component. PX_2_25 2.25 CDIV_N18_001 A forwarded call will encounter interworking. PX_2_26 2.26 CDIV_N02_001,002, 005, 006 For COLR, presentation is not allowed. PX_2_30 2.30 CDIV_N08_001-009 The user connected to the access related to the MTC is considered as being network dependant user busy. PX_2_31 2.31 NOTE: "N03", "N04" and "N06" include each of the subgroups for cfu, cfnr and cfb.
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 16 11.3 SCF ATS Table 8 describes the configurations relating to subscription options, it is necessary for the IUT to support at least one of the first four configurations. Table 9 describes the configurations relating to the number of screening lists, it is necessary for the IUT to support at least one of these configurations. It is only possible for a particular interface to be configured as one of each of these groups of configurations at a given time. For the purposes of test case selection the test suite parameters relating to all the configurations supported (as identified in the PIXIT) shall be TRUE. During test suite execution one parameter from each group shall be true indicating the actual configuration of the IUT. Any test cases which require different configurations are deselected. If more than one configuration is supported then it is necessary to re-configure the IUT and change the parameters in order to run all the test cases. NOTE 1: The parameters CONF_ONE_LIST and CONF_MANY_LISTS are used for test case parameterization as well as selection. Table 8: SUT configurations for subscription options Test Cases (see note 1) SCF subscription MSN (see note 3) Activation, deactivation and interrogation for all ISDN-numbers on the same access (see note 3) Test suite parameter PIXIT ref. SCF_N01_001, 002, 010, 011 (see note 2) SCF_N01_030 SCF_N02_024 Whole access * N/A CONF_WHOLE_ACCESS 2a.1 SCF_N01_003, 004, 012, 013 (see note 2) Per ISDN number No * CONF_PERNO_NO_MSN 2a.2 SCF_N01_005, 014
(see note 2) Per ISDN number Yes * CONF_PERNO_MSN_NO OR CONF_PERNO_MSN_YES 2a.3 OR 2a.4 SCF_N01_006 (see note 2) Per ISDN number Yes No CONF_PERNO_MSN_NO 2a.3 SCF_N01_007 (see note 2) Per ISDN number Yes Yes CONF_PERNO_MSN_YES 2a.4 SCF_N01_031, 032
SCF_N02_025, 026 DDI range N/A Any CONF_DDI_NO OR CONF_DDI_YES 2a.11 2a.12 SCF_N01_033 SCF_N02_027 DDI range N/A No CONF_DDI_NO 2a.11 SCF_N01_034 SCF_N02_028 DDI range N/A Yes CONF_DDI_YES 2a.12 SCF_N01_020 SCF_N07_004 SCF_N08_002 Not subscribed for any basic service * N/A CONF_NOT_SUB_ALL 2a.5 SCF_N07_005 SCF_N08_003 Not available for any basic service * N/A CONF_NOT_AVAIL_ALL 2a.6 NOTE 1: Where TCs in group N01 are listed the TCs with the same serial numbers in groups N03 and N05 require the same configuration. Where TCs in group N02 are listed the TCs with the same serial numbers in groups N04 and N06 require the same configuration. NOTE 2: The TCs with the same serial numbers in groups N02, N03, N04, N05 and N06 require the same configuration.
NOTE 3: "*" indicates that either value of the option may be used.
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 17 Table 9: SUT configurations for number of screening lists Test cases Configuration Test suite parameter PIXIT reference SCF_N01_008, 016 (see note 1) One screening list registered. CONF_ONE_LIST 2a.7 SCF_N01_009, 017 (see note 1) SCF_N01_018 (see note 2) More than one screening list registered. CONF_MANY_LIST 2a.8 NOTE 1: The TCs with the same serial numbers in groups N02, N03, N04, N05 and N06 require the same configuration. NOTE 2: The TCs with the same serial numbers in groups N03, and N05 require the same configuration.
Table 10 describes the configurations relating to special conditions. The first two listed are considered to be incompatible with normal operation. For the purposes of test case selection the test suite parameters relating to all the configurations supported (as identified in the PIXIT) shall be TRUE. During test suite execution the parameters describing the actual configuration of the IUT shall be true. Those test cases which require special conditions for which the IUT is not configured are deselected. Generally it will be necessary to re-configure the IUT and change the parameters in order to run all the test cases. NOTE 2: Test cases not requiring special conditions are not deselected when the parameter indicates that the IUT is configured for a special condition. Table 10: SUT configurations for special conditions Test cases Configuration Test suite parameter PIXIT reference SCF_N01_23 (see note 1) An attempt to activate SCF is to be unsuccessful due to a supplementary service interaction. CONFIG_INTERACTION 2a.9 SCF_N01_025 (see note 1) An attempt to activate SCF is to be unsuccessful due to a resources being unavailable. CONFIG_RESOURCE 2a.10 SCF_N01_024 (see note 1) There is a basic service for which the IUT is not subscribed. PX_3_9 3.9 SCF_N02_018 (see note 2) There is a basic service for which the SCF service is not subscribed. PX_3_12 3.12 SCF_N01_021 (see note 1) SCF_N02_019 (see note 2) There is a basic service for which the SCF service is not available. PX_3_13 3.13 NOTE 1: The TCs with the same serial numbers in groups N03, and N05 require the same configuration. NOTE 2: The TCs with the same serial numbers in groups N04, and N06 require the same configuration.
ETSI ETSI EN 300 207-6 V3.2.1 (2003-01) 18 Annex A (normative): Protocol Conformance Test Report (PCTR) proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PCTR proforma in this annex so that
...