ETSI EN 301 061-5 V1.1.3 (1998-10)

Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary services at the b service entry point for Virtual Private Network (VPN) applications; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

DEN/SPS-05110-5

Digitalno omrežje z integriranimi storitvami (ISDN) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - Generični funkcijski protokol za podporo dopolnilnim storitvam v vstopni točki b storitve za aplikacije navideznega zasebnega omrežja (VPN) - 5. del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) - Specifikacija za omrežje

General Information

• Status: Published
• Publication Date: 25-Oct-1998
• Technical Committee: SPS 5 3 - Conformance Testing
• Current Stage: 12 - Completion
• Due Date: 13-Nov-1998
• Completion Date: 26-Oct-1998
• Mandate: BC-T-338
• Ref Project: SIST EN 301 061-5 V1.1.3:2005 - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary services at the b service entry point for Virtual Private Network (VPN) applications; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 301 061-5 V1.1.3:2005
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'13URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66*HQHULþQLIXQNFLMVNLSURWRNRO]DSRGSRURGRSROQLOQLP
VWRULWYDPYYVWRSQLWRþNLEVWRULWYH]DDSOLNDFLMHQDYLGH]QHJD]DVHEQHJDRPUHåMD
931GHO=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQLSUHVNXãDQMD766 73
6SHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one
(DSS1) protocol; Generic functional protocol for the support of supplementary services at
the b service entry point for Virtual Private Network (VPN) applications; Part 5: Test Suite
Structure and Test Purposes (TSS&TP) specification for the network
Ta slovenski standard je istoveten z: EN 301 061-5 Version 1.1.3
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST EN 301 061-5 V1.1.3:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN 301 061-5 V1.1.3:2005

---------------------- Page: 2 ----------------------

SIST EN 301 061-5 V1.1.3:2005
EN 301 061-5 V1.1.3 (1998-10)
European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Digital Subscriber Signalling System No. one (DSS1) protocol;
Generic functional protocol for the support of
supplementary services at the "b" service entry point for
Virtual Private Network (VPN) applications;
Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network

---------------------- Page: 3 ----------------------

SIST EN 301 061-5 V1.1.3:2005
2 EN 301 061-5 V1.1.3 (1998-10)
Reference
DEN/SPS-05110-5 (9tp90ie0.PDF)
Keywords
DSS1, generic, ISDN, supplementary service,
VPN, TSS&TP, network
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - 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
Internet
[e-mail]
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

---------------------- Page: 4 ----------------------

SIST EN 301 061-5 V1.1.3:2005
3 EN 301 061-5 V1.1.3 (1998-10)
Contents
Intellectual Property Rights.4
Foreword .4
1 Scope.5
2 Normative references .5
3 Definitions and abbreviations .6
3.1 Definitions . 6
3.1.1 Definitions related to conformance testing. 6
3.1.2 Definitions related to EN 301 061-1 . 6
3.2 Abbreviations. 6
4 Test Suite Structure (TSS) .7
5 Test Purposes (TP).8
5.1 Introduction. 8
5.1.1 TP naming convention. 8
5.1.2 Source of TP definition . 8
5.1.3 TP structure. 8
5.1.4 Test strategy . 9
5.2 Network TPs for VPN-GFP. 9
5.2.1 Common IE approach. 9
5.2.1.1 Bearer related transport mechanism. 10
5.2.1.1.1 Protocol control . 10
5.2.1.1.1.1 Outgoing call . 10
5.2.1.1.1.2 Incoming call. 10
5.2.1.1.2 GFT-Control . 11
5.2.1.2 Connection oriented bearer independent transport mechanism . 14
5.2.1.2.1 Protocol control . 14
5.2.1.2.1.1 Originating interface. 14
5.2.1.2.1.2 Destination interface. 14
5.2.1.2.1.3 Connection clearing. 14
5.2.1.2.1.4 Exchange of FACILITY messages. 15
5.2.1.2.1.5 Interaction . 15
5.2.1.2.1.6 Handling of error conditions . 16
5.2.1.2.1.7 Timers . 17
5.2.1.2.2 GFT-Control requirement . 17
5.2.1.2.2.1 Control of the Facility IE. 17
5.2.1.2.2.2 Control of the NCICS connection . 20
5.2.1.2.2.2A Transit PINX . 20
5.2.2 Generic notification procedures . 21
5.2.2.1 Protocol control . 21
5.2.2.2 GFT-control. 21
5.2.3 Co-ordination function . 22
5.2.4 ROSE requirements. 23
5.2.5 Flow control . 23
6 Compliance .24
7 Requirements for a comprehensive testing service.24
History.25
ETSI

---------------------- Page: 5 ----------------------

SIST EN 301 061-5 V1.1.3:2005
4 EN 301 061-5 V1.1.3 (1998-10)
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.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 5 of a multi-part European Standard (Telecommunications series) covering the Integrated
Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functional
protocol for the support of supplementary services at the "b" service entry point for Virtual Private Network (VPN)
applications, as identified 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), user";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP), specification for the network";
Part 6: "Abstract Test Suite (ATS), network".
National transposition dates
Date of adoption of this EN: 30 October 1998
Date of latest announcement of this EN (doa): 31 January 1999
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 July 1999
Date of withdrawal of any conflicting National Standard (dow): 31 July 1999
ETSI

---------------------- Page: 6 ----------------------

SIST EN 301 061-5 V1.1.3:2005
5 EN 301 061-5 V1.1.3 (1998-10)
1 Scope
This fifth part of EN 301 061 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the network side of the
T reference point (as defined in ITU-T Recommendation I.411 [9]) of implementations conforming to the stage three
standard for the generic functional protocol for the support of supplementary services for Virtual Private Network
(VPN) applications for the pan-European Integrated Services Digital Network (ISDN) by means of the Digital
Subscriber Signalling System No. one (DSS1) protocol, EN 301 061-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 196-1 (V1.2): "Integrated Services Digital Network (ISDN); Generic functional protocol
for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 1: Protocol specification".
[2] EN 301 061-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary
services at the "b" service entry point for Virtual Private Network (VPN) applications; Part 1:
Protocol specification".
[3] EN 301 061-2 (V1.1): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary
services at the "b" service entry point for Virtual Private Network (VPN) applications; Part 2:
Protocol Implementation Conformance Statement (PICS) proforma specification".
[4] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[5] ISO/IEC 9646-1: "Information technology; Open System Interconnection; Conformance testing
methodology and framework; Part 1: General concepts".
[6] ISO/IEC 9646-2: "Information technology; Open System Interconnection; Conformance testing
methodology and framework; Part 2: Abstract Test Suite specification".
[7] Void.
[8] ISO/IEC 11582 (1995): "Information technology; Telecommunications and information exchange
between systems; Private Integrated Services Network; Generic functional protocol for the support
of supplementary services; Inter-exchange signalling procedures and protocol".
[9] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces; reference configurations".
ETSI

---------------------- Page: 7 ----------------------

SIST EN 301 061-5 V1.1.3:2005
6 EN 301 061-5 V1.1.3 (1998-10)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
3.1.1 Definitions related to conformance testing
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5].
PICS proforma: Refer to ISO/IEC 9646-1 [5].
Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [5].
PIXIT proforma: Refer to ISO/IEC 9646-1 [5].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].
3.1.2 Definitions related to EN 301 061-1
component: See EN 300 196-1 [1], subclause 11.2.2.1.
invoke component: See EN 300 196-1 [1], subclause 11.2.2.1.
return error component: See EN 300 196-1 [1], subclause 11.2.2.1.
return result component: See EN 300 196-1 [1], subclause 11.2.2.1.
T: The DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is a
private ISDN).
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
APDU Application Protocol Data Unit
ATM Abstract Test Method
ATS Abstract Test Suite
GFT Generic Functional Transport
IE Information Element
ISDN Integrated Services Digital Network
IUT Implementation Under Test
NCICS Networked Call Independent Connection oriented Signalling
PICS Protocol Implementation Conformance Statement
PINX Private Integrated services Network eXchange
PIXIT Protocol Implementation eXtra Information for Testing
ROSE Remote Operations Service Element
TP Test Purpose
TSS Test Suite Structure
VPN Virtual Private Network
VPN-GFP Generic Functional Protocol for the support of supplementary services for VPN
ETSI

---------------------- Page: 8 ----------------------

SIST EN 301 061-5 V1.1.3:2005
7 EN 301 061-5 V1.1.3 (1998-10)
4 Test Suite Structure (TSS)
group
5.2.1. Common Information Element (IE) approach
5.2.1.1. Bearer related transport mechanism
5.2.1.1.1. protocol control
5.2.1.1.1.1. Outgoing call N01
5.2.1.1.1.2. Incoming call N02
5.2.1.1.2. GFT-control N03
5.2.1.2. Connection oriented Bearer bearer independent transport mechanism
5.2.1.2.1. Protocol control
5.2.1.2.1.1. Originating interface N04
5.2.1.2.1.2. Destination interface N05
5.2.1.2.1.3. Connection clearing N06
5.2.1.2.1.4. Exchange of FACILITY messages N07
5.2.1.2.1.5. Interaction N08
5.2.1.2.1.6. Handling of error conditions N09
5.2.1.2.1.7. Timers N10
5.2.1.2.2. GFT-control
5.2.1.2.2.1. Control of facility IE N11
5.2.1.2.2.2. Control of the NCICS connection N12
5.2.2. Generic notification procedures
5.2.2.1. Protocol control N13
5.2.2.2. GFT-control N14
5.2.3. Co-ordination function N15
5.2.4. ROSE requirement N16
5.2.5. Flow control N17
Figure 1: Test suite structure
ETSI

---------------------- Page: 9 ----------------------

SIST EN 301 061-5 V1.1.3:2005
8 EN 301 061-5 V1.1.3 (1998-10)
5 Test Purposes (TP)
5.1 Introduction
For each test requirement a TP is defined.
5.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= protocol specification: "GFP"
= type of IUT: U User
N Network
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)
5.1.2 Source of TP definition
The TPs are based on EN 301 061-1 [2].
5.1.3 TP structure
Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs
more readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should be
read in conjunction with any TP, i.e. use a TP as an example to fully understand the table.
ETSI

---------------------- Page: 10 ----------------------

SIST EN 301 061-5 V1.1.3:2005
9 EN 301 061-5 V1.1.3 (1998-10)
Table 2: Structure of a single TP for Generic Functional Protocol for the support
of supplementary services for VPN (VPN-GFP)
TP part Text Example
Header tab see table 1
tab subclause 0.0.0
Stimulus Ensure that the Implementation Under Test (IUT) in the
. N10 etc.
see below for message structure receiving a XXXX message
or to request a .
Reaction sends, saves, does, etc.
using en bloc sending, .
if the action is sending
see below for message structure
, etc.
and remains in the same state
or and enters state
Message SETUP, FACILITY, CONNECT, .
message containing a
structure
a) Bearer capability, Facility, .
IE with
b) a
encoded as or including
and back to a or b,
NOTE 1: TP are always applicable. Optional TPs are applicable according to the configuration options of the IUT. If
the configuration option is covered by a Protocol Implementation Conformance Statement (PICS) item, a
selection criteria is indicated, else the selection of the corresponding test cases will depend on test suite
parameters Protocol Implementation eXtra Information for Testing (PIXIT) in the Abstract Test Suite
(ATS).
NOTE 2: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one
TP to the next.
5.1.4 Test strategy
As the base standard EN 301 061-1 [2] contains no explicit requirements for testing, the TPs were generated as a result
of an analysis of the base standard and the Protocol Implementation Conformance Statement (PICS) specification
EN 301 061-2 [3].
The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and are
limited to conceivable situations to which a real implementation is likely to be faced (ETS 300 406 [4]).
5.2 Network TPs for VPN-GFP
All PICS items referred to in this subclause are as specified in EN 301 061-2 [3] unless indicated otherwise by another
numbered reference.
Unless specified, the messages and IEs indicated are valid and contain at least the mandatory parameters and possibly
optional parameters.
5.2.1 Common IE approach
Selection: IUT supports the common IE category. PICS: Mcn 1.
In all the TPs of this subclause, the call reference is to be considered in a Virtual Private Network (VPN) context.
The following TPs are testing the procedures associated with the transport of components using the messages for the
establishment and clearing of calls.
The primitives exchanged between the different entities are not observable. Only the PDU exchanged between peer
implementations can be observed.
ETSI

---------------------- Page: 11 ----------------------

SIST EN 301 061-5 V1.1.3:2005
10 EN 301 061-5 V1.1.3 (1998-10)
So to check that the component is properly transmitted to the Generic Functional Transport (GFT) entity, it shall
provoke a reaction from Remote Operations Service Element (ROSE) entity that will request the transmission of the
corresponding component as response. This component will be transmitted in a call related message with the same call
reference, which is observable.
To provoke a reaction from the ROSE entity, a return result component, with an invokeID not related to a currently
active invocation, can be sent.
5.2.1.1 Bearer related transport mechanism
Selection: IUT supports the bearer related transport mechanism. PICS: MCn 1.1.
In all the TPs of this subclause, the call reference is in a VPN context.
5.2.1.1.1 Protocol control
In the TPs of this subclause, no NFE shall be included so that the Private Integrated services Network eXchange (PINX)
entity will be the addressed PINX and can treat the received component.
5.2.1.1.1.1 Outgoing call
GFP_N01_001 subclause 7.2.1.1.1
Ensure that the IUT in the call state N0, on receipt of a SETUP message containing a VPN indicator IE and a Facility IE
with a component requiring an answer, sends a Facility IE with a component, included in a SETUP ACKNOWLEDGE,
CALL PROCEEDING or FACILITY message and enters respectively the N2, N3 or N1 call state.
GFP_N01_002 subclause 7.2.1.1.1
Ensure that the IUT in the call state N10, having sent a CONNECT messages, on receipt of a CONNECT
ACKNOWLEDGE message containing a Facility IE with a component requiring an answer, sends a FACILITY
message containing a Facility IE with a component and remains in the call state N10.
GFP_N01_003 subclause 7.2.1.1.1
Ensure that the IUT in the call state N10, on receipt of a DISCONNECT message containing a Facility IE with a
component requiring an answer, sends a Facility IE with a component included in the RELEASE or a FACILITY
message and enters the call state N19.
GFP_N01_004 subclause 7.2.1.1.1
Ensure that the IUT in the call state N12, on receipt of a RELEASE message containing a Facility IE with a component
requiring an answer, sends a Facility IE with a component included in the RELEASE COMPLETE or a FACILITY
message and enters the call state N0.
5.2.1.1.1.2 Incoming call
GFP_N02_001 subclause 7.2.1.1.1
Ensure that the IUT in the call state N0, in order to transmit a component during the establishment of a bearer related
call, sends a SETUP message containing a VPN indicator IE and a Facility IE with a component and enters the call state
N6.
GFP_N02_002 subclause 7.2.1.1.1
Ensure that the IUT in the call state N6, on receipt of a SETUP ACKNOWLEDGE message containing a Facility IE
with a component requiring an answer, sends a FACILITY message containing a Facility IE with a component and
enters the call state N25.
GFP_N02_003 subclause 7.2.1.1.1
Ensure that the IUT in the call state N6, on receipt of a CALL PROCEEDING message containing a Facility IE with a
component requiring an answer, sends a FACILITY message containing a Facility IE with a component and enters the
call state N9.
ETSI

---------------------- Page: 12 ----------------------

SIST EN 301 061-5 V1.1.3:2005
11 EN 301 061-5 V1.1.3 (1998-10)
GFP_N02_004 subclause 7.2.1.1.1
Ensure that the IUT in the call state N6, on receipt of an ALERTING message containing a Facility IE with a component
requiring an answer, sends a FACILITY message containing a Facility IE with a component and enters the call state N7.
GFP_N02_005 subclause 7.2.1.1.1
Ensure that the IUT in the call state N6, on receipt of a CONNECT message containing a Facility IE with a component
requiring an answer, sends a Facility IE with a component in the CONNECT ACKNOWLEDGE or a FACILITY
message, and enters respectively the call state N8 or N10.
GFP_N02_006 subclause 7.2.1.1.1
Ensure that the IUT in the call state N10, on receipt of a FACILITY message containing a Facility IE with a component
requiring an answer, sends a FACILITY message containing a Facility IE with a component and remains in the call state
N10.
GFP_N02_007 subclause 7.2.1.1.1
Ensure that the IUT in the call state N10, on receipt of a DISCONNECT message containing a Facility IE with a
component requiring an answer, sends a Facility IE with a component included in the RELEASE or a FACILITY
message and enters the call state N19.
GFP_N02_008 subclause 7.2.1.1.1
Ensure that the IUT in the call state N12, on receipt of a RELEASE message containing a Facility IE with a component
requiring an answer, sends a Facility IE with a component included in the RELEASE COMPLETE or a FACILITY
message and enters the call state N0.
5.2.1.1.2 GFT-Control
Selection: IUT supports the termination of the GFT-Control protocol. PICS: MCn 1.1.2.
The TPs in this subclause refer to ISO/IEC 11582 [8], subclause 7.1.2, as referenced by subclause 7.2.1.1.2 of
EN 301 061-1 [2].
GFP_N03_001 subclause 7.1.2.2
Ensure that the IUT in the call state N10, on receipt of a FACILITY message containing a Facility IE with a component
requiring an answer, not including a NFE, sends a FACILITY message containing a Facility IE with a component and
remains in the call state N10.
NOTE 1: The PINX entity becomes the destination entity for that Facility IE.
GFP_N03_002 subclause 7.1.2.2.1
Ensure that the IUT in the call state N10, on receipt of a FACILITY message containing a Facility IE with a component
requiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with no
destinationEntityAddress element, sends a FACILITY message containing a Facility IE with a component and remains
in the call state N10.
NOTE 2: The PINX entity becomes the destination entity for that Facility IE.
Selection: PICS: IUT supports End PINX functionalities: TIn 1 OR TIn 2 [8].
GFP_N03_003 subclause 7.1.2.2.2
Ensure that the IUT in the call state N10, on receipt of a FACILITY message containing a Facility IE with a component
requiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with no
destinationEntityAddress element, sends a FACILITY message containing the same Facility IE at the interface to the
next PINX, and remains in the call state N10.
NOTE 3: The PINX entity becomes the destination entity for that Facility IE.
Selection: PICS: IUT supports Transit PINX functionalities: TIn 3 [8].
ETSI

---------------------- Page: 13 ----------------------

SIST EN 301 061-5 V1.1.3:2005
12 EN 301 061-5 V1.1.3 (1998-10)
GFP_N03_004 subclause 7.1.2.2.1
Ensure that the IUT in the call state N10, on receipt of a FACILITY message containing a Facility IE with a component
requiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with no
destinationEntityAddress element, sends a FACILITY message containing a Facility IE with a component and remains
in the call state N10.
NOTE 4: The PINX entity becomes the destination entity for that Facility IE.
Selection: PICS: IUT supports End PINX functionalities: TIn 1 OR TIn 2 [8].
GFP_N03_005 subclause 7.1.2.2.2
Ensure that the IUT in the call state N10, on receipt of a FACILITY message containing a Facility IE with a component
requiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with no
destinationEntityAddress element, either sends a FACILITY message containing a Facility IE with a component,
or sends a FACILITY message containing the same Facility IE at the interface to the next PINX,
and remains in the call state N10.
NOTE 5: The PINX entity passes the Facility IE to the next PINX.
Selection: PICS: IUT supports Transit PINX functionalities: TIn 3 [8].
GFP_N03_006 subclause 7.1.2.2
Ensure that the IUT in the call state N10, on receipt of a FACILITY message containing a Facility IE with a component
requiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with a
destinationEntityAddres
...