SIST EN 300 195-5 V1.3.3:2005

• Abstract:

  Test specification for RE/SPS-05138-1

• 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 195-5 V1.3.3 (2000-05) - Integrated Services Digital Network (ISDN); Supplementary service interactions; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

SIST EN 300 195-5 V1.3.3:2005 is the Slovenian adoption of ETSI EN 300 195-5 for Integrated Services Digital Network (ISDN) supplementary service interactions using the Digital Subscriber Signalling System No. one (DSS1) protocol. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for the network side, so it tells test labs and implementers what behaviors to verify on network equipment that conforms to EN 300 195-1.

What does SIST EN 300 195-5 V1.3.3:2005 specify?

SIST EN 300 195-5 V1.3.3:2005 specifies conformance test purposes for the network side of the T reference point, or the coincident S and T reference point, in ISDN supplementary service interactions. In practice, it is the test-specification companion to the protocol specification and is used to structure network-side conformance testing for DSS1 implementations.

The document is organized into these main clauses:

• Scope
• References
• Definitions
• Abbreviations
• Test Suite Structure (TSS)
• Test Purposes (TP)
• Compliance
• Requirements for a comprehensive testing service

Clause 5 defines the two-level test suite structure. Clause 6 gives the individual test purposes and their selection conditions. Clause 7 states what a compliant Abstract Test Suite (ATS) must do, and clause 8 sets the minimum test method for organizations claiming a comprehensive testing service.

What are the key requirements of SIST EN 300 195-5 V1.3.3:2005?

SIST EN 300 195-5 V1.3.3:2005 is not a product specification. Its core requirement is that network-side conformance tests must be organized, named, and selected in a controlled way so they can be traced back to the supplementary service interactions defined in EN 300 195-1.

Test suite structure is two-level

Clause 5.1 and 5.2 define a two-level structure:

• level 1 is the interaction case between two supplementary services
• level 2 is the substructure of that interaction case

This matters because a test lab can select the relevant interaction case first, then select the precise scenario inside that case. The structure is aligned with the service interaction clauses in EN 300 195-1 and with the group numbers used in TP identifiers.

The network test purposes cover many service combinations

Clause 5.2 maps the network-side interaction cases to 68 group numbers. The covered combinations include AOC, ECT, CCBS, CD, CFB, CFNR, CFU, CONF, TP, HOLD, 3PTY, UUS, OCB, CCNR, CUG, COLP, COLR, CLIP, CLIR, MSN, SUB, MWI, FPH, SCF, and CW.

That breadth matters in practice because a network implementation may need to prove correct behavior when two supplementary services are active at the same time. The test suite is therefore built to verify not just one service in isolation, but the interaction between services that can affect call setup, transfer, forwarding, charging, and notification behavior.

TP identifiers are standardized

Clause 6.1.1 defines a naming convention for TP identifiers using:

• the service family
• the IUT type
• the group number
• the subgroup number
• a sequential item number

This matters because a test case identifier tells you exactly where the test sits in the structure, which makes PICS mapping, test selection, and defect tracking easier.

Test purposes focus on observable behavior

Clause 6.1.4 says the test purposes are based on externally observable behavior of the Implementation Under Test (IUT) and on realistic situations. They are mandatory unless a selection criterion applies.

In practice, that means the document is intended for black-box conformance testing. A tester checks what the network sends, receives, accepts, rejects, or reports, rather than how the network is internally designed.

Charging interactions are a major theme

Many of the detailed TPs in clause 6 check Advice of Charge (AOC) behavior together with other services. Examples include:

• AOC with ECT
• AOC with CD, CFB, CFNR, and CFU
• AOC with CONF and TP
• AOC with 3PTY

These tests check how charging information is delivered during call transfer, call deflection, forwarding, conference handling, and suspension. In practice, a network has to handle FACILITY messages, call references, and charging-related invoke, return result, and return error components consistently.

Selection criteria depend on supported service options

Clause 6 repeatedly uses selection statements tied to PICS items. The test purposes are only applicable when the IUT supports the relevant option, such as AOC-E support, specific rerouting behavior, or notification options.

This matters because not every network supports every service combination. The document ties each test to a declared capability so the test suite can be trimmed without losing traceability.

Compliance is ATS-based and traceable

Clause 7 says a compliant ATS must:

• contain test cases corresponding to all or a subset of the TPs in clause 6
• use an appropriate subset of the TSS from clause 5
• keep the naming conventions
• preserve the link between test groups, TPs, and PICS items used for deselection
• comply with ISO/IEC 9646-2

For a test house, this means the ATS has to be structurally consistent with the standard and must not invent its own naming or selection logic.

Comprehensive testing uses the Remote test method

Clause 8 states that any organization claiming to provide a comprehensive testing service for network equipment conforming to EN 300 195-1 shall use the Remote test method as a minimum, as specified in ISO/IEC 9646-2.

In practice, this sets the baseline method for test service providers that want to cover network equipment thoroughly.

What terms does SIST EN 300 195-5 V1.3.3:2005 define?

• Implementation Under Test (IUT) - the network implementation being tested for conformance.
• Protocol Implementation Conformance Statement (PICS) - the statement that records which options and capabilities the implementation supports and which tests apply.
• Protocol Implementation eXtra Information for Testing (PIXIT) - extra test information needed to run conformance tests in a specific configuration.
• Abstract Test Suite (ATS) - the set of abstract test cases derived from the test purposes.
• active test - a test where the IUT must send a message that is not just a direct reaction to a received message.
• passive test - a test where the IUT responds to a protocol event, such as a received message, with another event.
• network (T) - the DSS1 protocol entity at the network side of the interface where a T reference point applies.
• served user - the user who invokes the supplementary service being tested.

Who uses SIST EN 300 195-5 V1.3.3:2005?

SIST EN 300 195-5 V1.3.3:2005 is used by conformance test laboratories, network equipment vendors, and telecom engineers who need to verify DSS1 supplementary service interactions on the network side. Quality managers and buyers can also use it to check whether a supplier’s test coverage matches the network-side behavior expected for EN 300 195-1.

It is particularly relevant in ISDN and telecommunications environments where services such as call forwarding, explicit call transfer, conference, call hold, call waiting, completion services, charging information, and user-to-user signalling can interact during real calls. Test developers use it to build ATS material, and acceptance teams use it to map capabilities to PICS items and test selection.

What changed in SIST EN 300 195-5 V1.3.3:2005 from the previous edition?

The document history shows the progression from ETS 300 195-5 to EN 300 195-5 V1.3.2 and then to EN 300 195-5 V1.3.3. The supplied history does not state the technical changes between those editions.

Which standards are used with SIST EN 300 195-5 V1.3.3:2005?

• ETSI EN 300 195-1 - the protocol specification for supplementary service interactions; it is the main conformance target for the test purposes.
• ETSI EN 300 195-2 - the PICS proforma specification used for test selection.
• ETSI EN 300 196-1 - the generic functional protocol for supporting supplementary services; it provides definitions used by this document.
• ETSI EN 300 207-1 and ETSI EN 300 207-5 - diversion supplementary service protocol and its network-side TSS&TP companion, used as related service references.
• ETSI EN 300 403-1 - basic call control signaling network layer protocol, used for call reference definitions.
• ISO/IEC 9646-1, -2, -3 - the conformance testing methodology framework used for ATS concepts, abstract test suite structure, and notation.
• ITU-T Recommendation E.164 - the numbering plan used for ISDN number definitions.
• ITU-T Recommendation I.112 and ITU-T Recommendation I.210 - vocabulary and service principles for ISDN and supplementary services.
• ITU-T Recommendation I.411 - the reference configuration for the T reference point.
• ETSI ETS 300 406 - the testing and specification methodology reference cited for the test strategy.

What does the SIST EN 300 195-5 V1.3.3:2005 document contain?

SIST EN 300 195-5 V1.3.3:2005 contains a structured set of test purposes for many supplementary service interactions, expressed as abstract conformance requirements on message exchange, call-state transitions, and service responses. The detailed clauses describe scenarios using FACILITY, SETUP, SUSPEND, DISCONNECT, RELEASE, and related DSS1 messages, together with invoke, return result, and return error components.

Clause 5 includes the two-level test suite structure and a table of 68 interaction groups. Clause 6 contains the TP definitions and many scenario descriptions, including charging delivery, diversion, conference behavior, transfer, hold, call waiting, completion services, and user-to-user signalling. The TP text also shows selection criteria tied to PICS items, which tells the reader when each test is applicable.

Clause 7 gives the compliance rules for building an ATS from the test purposes and the TSS. Clause 8 states the minimum test method for a comprehensive network-equipment testing service.

SLOVENSKI STANDARD
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'10HGVHERMQRYSOLYDQMH
GRSROQLOQHVWRULWYH3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66
GHO=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQLSUHVNXãDQMD766 736SHFLILNDFLMD
]DRPUHåMH
Integrated Services Digital Network (ISDN); Supplementary service interactions; Digital
Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and
Test Purposes (TSS&TP) specification for the network
Ta slovenski standard je istoveten z: EN 300 195-5 Version 1.3.3
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);
Supplementary service interactions;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network
2 ETSI EN 300 195-5 V1.3.3 (2000-05)
Reference
REN/SPS-05138-5
Keywords
DSS1, interaction, ISDN, network, supplementary
service, testing, TSS&TP
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 195-5 V1.3.3 (2000-05)
Contents
Intellectual Property Rights.8
Foreword .8
1 Scope.9
2 References.9
3 Definitions.10
3.1 Definitions related to conformance testing.10
3.2 Definitions related to EN 300 195-1 .10
4 Abbreviations .11
5 Test Suite Structure (TSS) .12
5.1 Two-level structure of the test suite.12
5.2 Level 1: interaction case (test purpose group).12
5.3 Level 2: substructure of an interaction case (test purpose subgroup) .14
6 Test Purposes (TP).14
6.1 Introduction .14
6.1.1 TP naming convention .14
6.1.2 Source of TP definition.15
6.1.3 TP structure.15
6.1.4 Test strategy.15
6.2 Network TPs for SSI .16
6.2.1 Interaction between AOC-D and AOC-E.16
6.2.1.1 Test suite substructure.16
6.2.1.2 User initiates call clearing .16
6.2.1.3 Network initiates call clearing.16
6.2.2 Interaction between AOC and ECT .17
6.2.2.1 Test suite substructure.17
6.2.2.2 AOC-D activated.17
6.2.2.3 AOC-E activated .17
6.2.2.3.1 Identification of charge invocation .17
6.2.2.3.2 Sending of charging information .18
6.2.3 Interaction between AOC and CCBS.19
6.2.3.1 Test suite substructure.19
6.2.3.2 Sending of charging information (S/T reference point).19
6.2.4 Interaction between AOC and CD .19
6.2.4.1 Test suite substructure.20
6.2.4.2 Delivery of charging information (S/T reference point).20
6.2.4.2.1 Identification of charge invocation .20
6.2.4.2.2 Sending of charging information .20
6.2.4.3 Delivery of charging information (T reference point) .21
6.2.4.3.1 Identification of charge invocation in CD request .21
6.2.4.3.2 Sending of charging information (CD provided by the network) .21
6.2.4.3.3 Identification of charge invocation in partial re-routeing request.22
6.2.4.3.4 Sending of charging information (partial re-routeing).23
6.2.5 Interaction between AOC and CFB .23
6.2.5.1 Test suite substructure.24
6.2.5.2 Delivery of charging information (S/T reference point).24
6.2.5.3 Delivery of charging information (T reference point) .24
6.2.5.3.1 Sending of charging information (CFB provided by the network) .24
6.2.5.3.2 Identification of charge invoked in partial re-routeing request.25
6.2.5.3.3 Sending of charging information (partial re-routeing).25
6.2.6 Interaction between AOC and CFNR.25
6.2.6.1 Test suite substructure.26
6.2.6.2 Delivery of charging information (S/T reference point).26
ETSI
4 ETSI EN 300 195-5 V1.3.3 (2000-05)
6.2.6.3 Delivery of charging information (T reference point) .26
6.2.6.3.1 Sending of charging information (CFNR provided by the network).26
6.2.6.3.2 Identification of charge invoked in partial re-routeing request.27
6.2.6.3.3 Sending of charging information (partial re-routeing).28
6.2.7 Interaction between AOC and CFU .28
6.2.7.1 Test suite substructure.29
6.2.7.2 Delivery of charging information (S/T reference point).29
6.2.7.3 Delivery of charging information (T reference point) .29
6.2.7.3.1 Sending of charging information (CFU provided by the network) .29
6.2.7.3.2 Identification of charge invoked in partial re-routeing request.30
6.2.7.3.3 Sending of charging information (partial re-routeing).30
6.2.8 Interaction between AOC and 3PTY .30
6.2.9 Interaction between AOC and CONF .31
6.2.9.1 Test suite substructure.31
6.2.9.2 Begin conference from N00 .31
6.2.9.3 Begin conference from N10 .32
6.2.9.4 Adding a remote user .33
6.2.9.5 Isolate a remote user.33
6.2.9.6 Reattach a remote user .33
6.2.9.7 Splitting a remote user.33
6.2.9.8 Disconnect a remote user .35
6.2.10 Interaction between AOC and TP .35
6.2.10.1 Test suite substructure.35
6.2.10.2 Suspending a call.35
6.2.10.3 Resuming a call .36
6.2.10.4 Unsuccessful attempt of resuming a call .36
6.2.11 Interaction between CONF and HOLD.36
6.2.11.1 Test suite substructure.37
6.2.11.2 Suppress notification to remote user .37
6.2.11.3 Identify remote user who sends a notification .37
6.2.12 Interaction between CONF and CUG supplementary service.37
6.2.12.1 Test suite substructure.38
6.2.12.2 Add party to the conference .38
6.2.13 Interaction between CONF and CONF .38
6.2.13.1 Test suite substructure.38
6.2.13.2 Re-invoking a conference within a conference.38
6.2.13.3 Adding a conference to a conference .39
6.2.13.4 Identify remote user who sends a notification .39
6.2.14 Interaction between CONF and TP.39
6.2.14.1 Test suite substructure.39
6.2.14.2 Served user of conference attempts suspend .39
6.2.14.3 Identify remote user who sends a notification to conference.39
6.2.15 Interaction between CONF and 3PTY.40
6.2.15.1 Test suite substructure.40
6.2.15.2 Invoking 3PTY when one of the two calls is a conference.40
6.2.15.3 Adding a 3PTY call to a conference .41
6.2.15.4 Invoking the CONF service for a call in 3-way conversation.41
6.2.15.5 Identify remote user who sends a notification to conference.41
6.2.16 Interaction between CONF and UUS service 3 .41
6.2.16.1 Test suite substructure.42
6.2.16.2 CONF controlling user sends UUS3 info to single party .42
6.2.16.3 CONF controlling user broadcasts UUS3 info .42
6.2.16.4 CONF remote user sends UUS3 info .42
6.2.16.5 UUS3 flow control .42
6.2.17 Interaction between CONF and ECT .43
6.2.17.1 Test suite substructure.43
6.2.17.2 CONF controlling user invokes ECT .43
6.2.17.3 CONF remote user uses ECT .44
6.2.18 Interaction between CD and COLP.44
6.2.19 Interaction between CD and COLR .44
ETSI
5 ETSI EN 300 195-5 V1.3.3 (2000-05)
6.2.20 Interaction between CD and UUS.44
6.2.20.1 Test suite substructure.44
6.2.20.2 Deflection before alerting (S/T reference point) .44
6.2.20.3 Deflection after alerting (S/T reference point) .47
6.2.20.3.1 UUS1 implicit.47
6.2.20.3.2 UUS1 explicit .47
6.2.20.3.3 UUS2.49
6.2.20.3.4 UUS3.49
6.2.20.4 Partial re-routeing (T reference point).50
6.2.21 Interaction between CFB and COLP.52
6.2.22 Interaction between CFB and COLR .52
6.2.23 Interaction between CFB and UUS.52
6.2.23.1 Test suite substructure.53
6.2.23.2 Forwarding of UUS supplementary service information (S/T reference point).53
6.2.23.3 Forwarding of UUS by public ISDN (T reference point).53
6.2.23.4 Partial re-routeing (T reference point).53
6.2.24 Interaction between CFNR and COLP.55
6.2.25 Interaction between CFNR and COLR .55
6.2.26 Interaction between CFNR and UUS.55
6.2.26.1 Test suite substructure.56
6.2.26.2 Implicit UUS1 request (S/T reference point) .56
6.2.26.3 Explicit UUS1 request (S/T reference point) .56
6.2.26.4 UUS2 request (S/T reference point).57
6.2.26.5 UUS3 request (S/T reference point).58
6.2.26.6 Forwarding by public ISDN (T reference point).58
6.2.26.7 Partial re-routeing (T reference point).59
6.2.27 Interaction between CFU and COLP .61
6.2.28 Interaction between CFU and COLR.61
6.2.29 Interaction between CFU and UUS.61
6.2.29.1 Test suite substructure.61
6.2.29.2 Forwarding of UUS supplementary service information (S/T reference point).61
6.2.29.3 Forwarding of UUS by public ISDN (T reference point).61
6.2.29.4 Partial re-routeing (T reference point).62
6.2.30 Interaction between TP and 3PTY.64
6.2.30.1 Test suite substructure.64
6.2.30.2 Served user of 3PTY invokes TP .64
6.2.31 Interaction between HOLD and TP .64
6.2.31.1 Test suite substructure.64
6.2.31.2 Served user of HOLD invokes TP.65
6.2.32 Interaction between HOLD and 3PTY.65
6.2.32.1 Test suite substructure.65
6.2.32.2 Holding a 3PTY call .65
6.2.32.3 Retrieving a 3PTY call.65
6.2.33 Interaction between CUG and 3PTY .66
6.2.33.1 Test suite substructure.66
6.2.33.2 Requesting 3PTY across different CUG .66
6.2.34 Interaction between ECT and MCID .66
6.2.34.1 Test suite substructure.66
6.2.34.2 Requesting MCID after ECT.66
6.2.35 Interaction between ECT and 3PTY.67
6.2.35.1 Test suite substructure.67
6.2.35.2 Transfer of a 3-way conversation.67
6.2.36 Interaction between ECT and UUS.67
6.2.37 Interaction between CCBS and UUS .68
6.2.37.1 Test suite substructure.68
6.2.37.2 Requesting UUS in a CCBS call request.68
6.2.38 Interaction between CCBS and CLIP .69
6.2.38.1 Test suite substructure.69
6.2.38.2 Delivering calling line identity to private ISDN.69
6.2.39 Interaction between CCBS and CLIR .69
ETSI
6 ETSI EN 300 195-5 V1.3.3 (2000-05)
6.2.39.1 Test suite substructure.69
6.2.39.2 Terminating T reference point.70
6.2.40 Interaction between CCBS and CUG.70
6.2.40.1 Test suite substructure.70
6.2.40.2 Redefining the CUG requirement (S/T reference point) .70
6.2.41 Interaction between CCBS and MSN .71
6.2.41.1 Test suite substructure.71
6.2.41.2 Calling user identity in FACILITY messages to user A.71
6.2.42 Interaction between CCBS and SUB .72
6.2.43 Interaction between FPH and COLP.72
6.2.44 Interaction between ECT and CUG .72
6.2.44.1 Test suite substructure.72
6.2.44.2 Requesting ECT across different CUG .72
6.2.45 Interaction between ECT and TP.73
6.2.46 Interaction between CONF and MCID .73
6.2.46.1 Test suite substructure.73
6.2.46.2 Requesting MCID after CONF.73
6.2.47 Interaction between CCBS and CW.73
6.2.47.1 Test suite substructure.73
6.2.47.2 Offering a CCBS call as a waiting call.74
6.2.48 Interaction between UUS and TP .74
6.2.48.1 Test suite substructure.74
6.2.48.2 Suspending a call when UUS3 is activated .74
6.2.49 Interaction between MWI and MSN.74
6.2.49.1 Test suite substructure.75
6.2.49.2 Receiving user.75
6.2.49.3 Controlling user.75
6.2.50 Interaction between OCB and CCBS.76
6.2.50.1 Test suite substructure.76
6.2.50.2 Originating S/T and T reference point .76
6.2.50.3 Originating S/T reference point.77
6.2.50.4 Originating T reference point.78
6.2.51 Interaction between OCB and MSN .78
6.2.51.1 Test suite substructure.78
6.2.51.2 Originating S/T reference point.78
6.2.52 Interaction between OCB and CFB .79
6.2.52.1 Test suite substructure.79
6.2.52.2 Originating S/T or T reference point.80
6.2.52.3 Originating T reference point.80
6.2.53 Interaction between OCB and CFNR.80
6.2.53.1 Test suite substructure.80
6.2.53.2 Originating S/T and T reference point .80
6.2.53.3 Originating T reference point.81
6.2.54 Interaction between OCB and CFU .81
6.2.54.1 Test suite substructure.81
6.2.54.2 Originating S/T or T reference point.81
6.2.54.3 Originating T reference point.81
6.2.55 Interaction between OCB and CD .81
6.2.55.1 Test suite substructure.82
6.2.55.2 Originating S/T or T reference point.82
6.2.55.3 Originating T reference point.82
6.2.56 Interaction between OCB- UC and OCB-F.82
6.2.57 Interaction between CCNR and AOC .82
6.2.57.1 Test suite substructure.83
6.2.57.2 Sending of charging information (S/T reference point).83
6.2.58 Interaction between CCNR and CW .83
6.2.58.1 Test suite substructure.83
6.2.58.2 Sending of charging information (S/T reference point).83
6.2.59 Interaction between CCNR and CLIP.84
6.2.59.1 Test suite substructure.84
ETSI
7 ETSI EN 300 195-5 V1.3.3 (2000-05)
6.2.59.2 Delivering calling line identity to private ISDN.84
6.2.60 Interaction between CCNR and CLIR .84
6.2.60.1 Test suite substructure.84
6.2.60.2 Delivering calling line identity to private ISDN.85
6.2.61 Interaction between CCNR and CUG .85
6.2.61.1 Test suite substructure.85
6.2.61.2 Redefining the CUG requirement (S/T reference point) .85
6.2.62 Interaction between CCNR and CCBS .86
6.2.62.1 Test suite substructure.86
6.2.62.2 Sending of charging information (S/T reference point) - Network A side .86
6.2.63 Interaction between CCNR and MSN.87
6.2.63.1 Test suite substructure.87
6.2.63.2 Sending of charging information (S/T reference point) - Network A side .87
6.2.64 Interaction between CCNR and SUB.89
6.2.65 Interaction between CCNR and UUS .89
6.2.65.1 Test suite substructure.89
6.2.65.2 Requesting UUS in a CCNR call request .90
6.2.66 Interaction between CCNR and OCB .90
6.2.66.1 Test suite substructure.91
6.2.66.2 Originating S/T and T reference point .91
6.2.66.3 Originating S/T reference point.92
6.2.66.4 Originating T reference point.92
6.2.67 Interaction between OCB and SCF.93
6.2.67.1 Test suite substructure.93
6.2.67.2 Request selective call forwarding to a barred address.93
6.2.68 Interaction between CW and CFNR/CD.94
6.2.68.1 Test suite substructure.94
6.2.68.2 Offering a CFNR/CD call as a waiting call - calling network side.94
7 Compliance .95
8 Requirements for a comprehensive testing service.95
Bibliography.96
History.97
ETSI
8 ETSI EN 300 195-5 V1.3.3 (2000-05)
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 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 Services and
Protocols for Advanced Networks (SPAN).
The present document is part 5 of a multi-part EN covering the Integrated Services Digital Network (ISDN);
Supplementary service interactions; Digital Subscriber Signalling System No. one (DSS1) protocol, 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) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma 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 for the network side".
National transposition dates
Date of adoption of this EN: 28 April 2000
Date of latest announcement of this EN (doa)
...