SIST-V ETSI/EG 201 722 V1.2.1:2003

• Abstract:

  This second version of EG 201 722 incorporates changes and clarifications into the existing document based on responses received from working groups attempting to implement the requirements and to correct any detected errors.

• Status: Published
• Publication Date: 31-Oct-2003
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Nov-2003
• Due Date: 01-Nov-2003
• Completion Date: 01-Nov-2003
• Ref Project: ETSI EG 201 722 V1.2.1 (2000-12) - Intelligent Network (IN); Service provider access requirements; Enhanced telephony services

SIST-V ETSI/EG 201 722 V1.2.1:2003 is the Slovenian standard identical to ETSI EG 201 722 V1.2.1, an ETSI Guide from the European Telecommunications Standards Institute. It specifies service provider access requirements for Intelligent Network (IN) enhanced telephony services over Public Telecommunications Networks (PTNs), especially fixed PTNs such as PSTN and ISDN. The document is aimed at service providers and PTN operators who need a common view of the functions an interface between their domains must support.

What does SIST-V ETSI/EG 201 722 V1.2.1:2003 specify?

SIST-V ETSI/EG 201 722 V1.2.1:2003 specifies generic functional requirements for Service Provider Access (SPA) and the Service Provider Access Interface (SPAI). It is organized as an introduction, references, definitions and abbreviations, then clauses on the business and regulatory background, functional requirements, and architectural view.

The scope is focused on the access needs of Service Providers (SPs) delivering services over one or more PTNs, mainly fixed networks. Service interaction aspects are outside the scope, and the document points readers to EG 201 807 for network integrity, security, charging and related PTNO concerns.

The document is structured around:

• Clause 4 - background, regulatory, security, charging and access guidelines
• Clause 5 - overview of functional requirements and their priority
• Clause 6 - Circuit-Related (CR) functional requirements
• Clause 7 - Non-Circuit-Related (NCR) functional requirements
• Clause 8 - architectural view of SPA
• Annex A - informative bibliography

Clause 5 also summarizes each requirement by priority and whether it applies to CR, NCR, or both. That matters in practice because it helps an implementer decide which functions are essential for a given interface model.

What are the key requirements of SIST-V ETSI/EG 201 722 V1.2.1:2003?

SIST-V ETSI/EG 201 722 V1.2.1:2003 separates SPA needs into two interface styles: CR, where the call path is extended to the SP equipment, and NCR, where only control signalling is exchanged. That split drives the interface design, the protocol work, and the network functions that must be exposed.

How does the standard handle access and priority?

Clause 5 says the SPA requirements are listed with priorities from the SP viewpoint, and Table 1 classifies each one for CR and NCR as high, medium, low, or void. In practice, that gives planners a way to map business needs to interface capability and to see which items are relevant for a given deployment.

Clause 4 also sets the main access rules:

• SPA should support non-discriminatory access to PTNs.
• The SP shall not override restrictions caused by national regulation or high-level network restrictions and barrings.
• SPA is not guaranteed across boundaries of different PTNs, especially across countries.

These points matter because access design is not only a technical issue - it also has to fit regulatory limits and inter-network realities.

What does the standard require for calling line identity?

Clauses 5.2, 6.2 and 7.2 define requirements for Calling Line Identity (CLI) handling. The document covers reception of CLI, presentation of the complete CLI information to the PTN, addition or substitution of CLI, provision of CLI to an SP-initiated call, and relaying Malicious Call Identification (MCID) data.

In practice, this is the part of the document that supports caller identification, authentication, billing support and MCID-related handling. The text also links CLI processing to EC and national rules and to privacy requirements, so implementers have to treat CLI as both a service feature and a regulated data item.

What does the standard require for call control?

Clauses 5.3, 6.3 and 7.3 cover basic call set-up and clear-down functions. These include return speech path connection to the calling party, routing or indication of originating and terminating calls to the SP, indication of unsuccessful calls, provision of destination and routing information, call drop-back, user interaction before charging starts, reception of the originally dialled digits, disconnection of an active call, connection to an interactive voice response unit (IVR) in the PTN, and alternate routing to another point of presence of the SP.

In practice, these requirements support services such as call routing, freephone, announcements, call screening, call completion and IVR-based services. They also show when the SP needs a speech path and when control signalling alone is enough.

What does the standard require for supplementary services, charging and traffic?

Clauses 5.4, 5.5, 5.6, 6.4 to 6.6, and 7.4 to 7.6 cover supplementary call and data processing, charging-related capabilities and traffic-related capabilities. The document includes interrogation of a network termination point for data delivery, overriding incoming call barring, bypassing call diversion, message waiting indication, changes in the charging rate of a call, event traceability, traffic control capabilities, and avoidance of cyclical routing of a call.

For an implementer, this is where the operational control functions sit. These requirements affect how the network handles subscriber features, how charges are created or changed, and how call loops and traffic abuse are prevented or traced.

What does the architectural part add?

Clause 8 explains how SPA fits into the network architecture. It describes possible network configurations based on IN technology, names the service control gateway function (SCIWF), and says it may screen and filter messages and parameters, map messages and parameters, and collect usage information.

This matters because the standard is not only about service features. It also guides where the control plane, user plane and management plane functions sit between SP equipment and PTNs.

What terms does SIST-V ETSI/EG 201 722 V1.2.1:2003 define?

• Calling Line Identity (CLI) - the number that uniquely identifies the subscriber line used for a call.
• Public Telecommunications Network (PTN) - a network that provides telecommunications services to the general public.
• Public Telecommunications Network Operator (PTNO) - the entity responsible for developing, provisioning and maintaining those services and networks.
• Service Provider Access Interface (SPAI) - the interface between a PTN and SP equipment that enables access to PTN functionality.
• Circuit-Related (CR) - access where the call connection is extended from the PTN to the SP equipment.
• Non-Circuit-Related (NCR) - access where only a control connection exists, without extending the call path to the SP equipment.
• Service Provider originating (SPorig) - the SP role that handles originating-line or originating-call-related services.
• Service Provider terminating (SPterm) - the SP role that handles terminating-line or terminating-call-related services.

Who uses SIST-V ETSI/EG 201 722 V1.2.1:2003?

SIST-V ETSI/EG 201 722 V1.2.1:2003 is used by service providers, PTNOs, network architects, switch and protocol engineers, and system integrators working on IN-based service access. It is also relevant to quality managers and technical buyers who need to check whether a proposed interface can support CLI handling, call control, supplementary service handling, charging, and traffic control.

In practice, it supports tasks such as:

• defining SPAI capabilities for a new service
• choosing between CR and NCR access
• mapping service features to PTN functions
• planning protocol enhancement work
• checking access behaviour against regulatory and interconnection constraints

What changed in SIST-V ETSI/EG 201 722 V1.2.1:2003 from the previous edition?

SIST-V ETSI/EG 201 722 V1.2.1:2003 is the second version of EG 201 722. The scope says this version incorporates changes and clarifications based on responses from working groups attempting to implement the requirements, and it corrects detected errors. The history shows the publication path from V1.1.2 to V1.2.1.

Which standards are used with SIST-V ETSI/EG 201 722 V1.2.1:2003?

• ETSI ETR 322 - provides the vocabulary of terms and abbreviations for IN CS-1 and CS-2.
• ETSI ETS 300 089 - gives the CLIP service description used for CLI presentation.
• ETSI ETS 300 090 - gives the CLIR service description, relevant to CLI restriction handling.
• ETSI ETS 300 128 - gives the MCID service description, relevant to malicious call identification data.
• ETSI ETS 300 200 - gives the CFU service description, relevant to call diversion handling.
• ETSI ETS 300 335 - provides the ISUP test specification.
• ETSI ETR 339 - covers IN interconnect business requirements.
• EG 201 807 - covers network operator requirements for delivery of SPA, especially integrity, security and charging aspects.
• TR 101 365 and TR 101 664 - provide threat analysis and security features for IN interconnects.
• ITU-T Q.1200 - gives the general structure of IN Recommendations.
• Directives 98/10/EC, 97/33/EC and 97/66/EC - provide the regulatory framework for access, interconnection and privacy.

What does the SIST-V ETSI/EG 201 722 V1.2.1:2003 document contain?

SIST-V ETSI/EG 201 722 V1.2.1:2003 contains high-level requirement summaries, detailed technical aspects, usage examples, and information flow charts for each major SPA function family. It also includes the priority/applicability table in Clause 5, call-connection scenarios for CR and NCR access, and an architectural section with network configuration examples and plane separation.

For implementation work, the useful material is the set of figures showing CLI handling, call setup and clear-down, call routing, charging, traffic control, and alternate routing. For design and testing, the document’s diagrams and flow charts show what information must move between PTN and SP equipment and when.

SLOVENSKI STANDARD
01-november-2003
Inteligentno omrežje (IN) - Zahteve dostopa ponudnika storitve - Izboljšane
telefonske storitve
Intelligent Network (IN) - Service provider access requirements - Enhanced telephony
services
Ta slovenski standard je istoveten z: EG 201 722 Version 1.2.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Guide
Intelligent Network (IN);
Service provider access requirements;
Enhanced telephony services
2 ETSI EG 201 722 V1.2.1 (2000-12)
Reference
REG/SPAN-141604
Keywords
protocol, telephony, access, UNI, NNI, IN
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 EG 201 722 V1.2.1 (2000-12)
Contents
Intellectual Property Rights .8
Foreword.8
1 Scope.9
2 References.9
3 Definitions and abbreviations.10
3.1 Definitions . 10
3.2 Abbreviations. 11
4 Introduction.12
4.1 Current situation. 12
4.2 Regulatory aspects. 13
4.3 Security aspects. 13
4.4 Service interaction aspects. 14
4.5 Charging aspects . 14
4.6 Guidelines for the service provider access requirements . 15
5 Functional requirements for service provider access.15
5.1 Framework and overall list of the requirements. 15
5.2 Calling party information handling capabilities . 16
5.2.1 Reception of the calling line identity . 16
5.2.2 Presentation of the complete CLI information to the PTN . 16
5.2.3 Addition or substitution of a calling line identity. 17
5.2.4 Provision of CLI information to an SP-initiated call.17
5.2.5 Relaying of the malicious call identification data of a received call . 17
5.3 Basic call set-up and clear-down capabilities. 17
5.3.1 Return speech path connection from the terminating PTN to the calling party . 17
5.3.2 Routing of an originating or incoming call from the PTN to the SP . 17
5.3.3 Indication of an originating or incoming call from the PTN to the SP. 17
5.3.4 Routing of a terminating call from the PTN to the SP. 17
5.3.5 Indication of a terminating call from the PTN to the SP . 17
5.3.6 Reception of an indication of the cause of an unsuccessful call . 18
5.3.7 Provision of information for the destination and routing of a call. 18
5.3.8 Call drop-back . 18
5.3.9 User interaction without service charging of the end user. 18
5.3.10 Reception of the originally dialled digits. 18
5.3.11 Disconnection of a call in progress . 18
5.3.12 Connection of a call to an interactive voice response unit in the PTN . 18
5.3.13 Alternate routing of a call or the indication of a call to another "point of presence" of the SP. 18
5.4 Supplementary call and data processing capabilities. 19
5.4.1 Interrogation of a network termination point for data delivery. 19
5.4.2 Overriding of the "incoming call barring" supplementary service . 19
5.4.3 Bypassing of the "call diversion" supplementary service. 19
5.4.4 Message waiting indication . 19
5.5 Charging-related capabilities . 19
5.5.1 Changes in the charging rate of a call . 19
5.6 Traffic-related capabilities. 19
5.6.1 Event traceability. 19
5.6.2 Traffic control capabilities. 19
5.6.3 Avoidance of the cyclical routing of a call. 20
6 Circuit-related functional requirements .20
6.1 Call connection scenarios . 20
6.2 Calling party information handling capabilities . 21
6.2.1 Reception of the calling line identity . 21
6.2.1.1 Priority. 21
6.2.1.2 Example of usage . 21
ETSI
4 ETSI EG 201 722 V1.2.1 (2000-12)
6.2.1.3 Technical aspects. 21
6.2.1.4 Information flow chart. 22
6.2.2 Presentation of the complete CLI information to the PTN . 22
6.2.2.1 Priority. 22
6.2.2.2 Example of usage . 22
6.2.2.3 Technical aspects. 22
6.2.2.4 Information flow chart. 23
6.2.3 Addition or substitution of a calling line identity. 23
6.2.3.1 Priority. 23
6.2.3.2 Example of usage . 23
6.2.3.3 Technical aspects. 23
6.2.3.4 Information flow chart. 24
6.2.4 Provision of CLI information to an SP-initiated call.24
6.2.4.1 Priority. 24
6.2.4.2 Example of usage . 24
6.2.4.3 Technical aspects. 24
6.2.4.4 Information flow chart. 25
6.2.5 Relaying of the malicious call identification data of a received call . 25
6.2.5.1 Priority. 25
6.2.5.2 Example of usage . 25
6.2.5.3 Technical aspects. 25
6.2.5.4 Information flow chart. 25
6.3 Basic call set-up and clear-down capabilities. 27
6.3.1 Return speech path connection from the terminating PTN to the calling party . 27
6.3.1.1 Priority. 27
6.3.1.2 Example of usage . 27
6.3.1.3 Technical aspects. 27
6.3.1.4 Information flow chart. 27
6.3.2 Routing of an originating or incoming call from the PTN to the SP . 27
6.3.2.1 Priority. 28
6.3.2.2 Example of usage . 28
6.3.2.3 Technical aspects. 28
6.3.2.4 Information flow chart. 28
6.3.3 Indication of an originating or incoming call from the PTN to the SP. 29
6.3.4 Routing of a terminating call from the PTN to the SP. 29
6.3.4.1 Priority. 29
6.3.4.2 Example of usage . 29
6.3.4.3 Technical aspects. 29
6.3.4.4 Information flow chart. 30
6.3.5 Indication of a terminating call from the PTN to the SP . 30
6.3.6 Reception of an indication of the cause of an unsuccessful call . 31
6.3.6.1 Priority. 31
6.3.6.2 Example of usage . 31
6.3.6.3 Technical aspects. 31
6.3.6.4 Information flow chart. 31
6.3.7 Provision of information for the destination and routing of a call. 32
6.3.7.1 Priority. 32
6.3.7.2 Example of usage . 32
6.3.7.3 Technical aspects. 32
6.3.7.4 Information flow chart. 32
6.3.8 Call drop-back . 33
6.3.8.1 Priority. 33
6.3.8.2 Example of usage . 33
6.3.8.3 Technical aspects. 33
6.3.8.4 Information flow chart. 33
6.3.9 User interaction without service charging of the end user. 33
6.3.9.1 Priority. 33
6.3.9.2 Example of usage . 33
6.3.9.3 Technical aspects. 34
6.3.9.4 Information flow chart. 34
6.3.10 Reception of the originally dialled digits. 34
6.3.10.1 Priority. 34
ETSI
5 ETSI EG 201 722 V1.2.1 (2000-12)
6.3.10.2 Example of usage . 34
6.3.10.3 Technical aspects. 34
6.3.10.4 Information flow chart. 35
6.3.11 Disconnection of a call in progress . 35
6.3.11.1 Priority. 36
6.3.11.2 Example of usage . 36
6.3.11.3 Technical aspects. 36
6.3.11.4 Information flow chart. 36
6.3.12 Connection of a call to an interactive voice response unit in the PTN . 36
6.3.13 Alternate routing of a call or the indication of a call to another "point of presence" of the SP. 36
6.3.13.1 Priority. 36
6.3.13.2 Example of usage . 37
6.3.13.3 Technical aspects. 37
6.3.13.4 Information flow chart. 37
6.4 Supplementary call and data processing capabilities. 37
6.4.1 Interrogation of a network termination point for data delivery. 37
6.4.1.1 Priority. 37
6.4.1.2 Example of usage . 37
6.4.1.3 Technical aspects. 37
6.4.1.4 Information flow chart. 38
6.4.2 Overriding of the "incoming call barring" supplementary service . 38
6.4.2.1 Priority. 38
6.4.2.2 Example of usage . 38
6.4.2.3 Technical aspects. 38
6.4.2.4 Information flow chart. 38
6.4.3 Bypassing of the "call diversion" supplementary service. 39
6.4.3.1 Priority. 39
6.4.3.2 Example of usage . 39
6.4.3.3 Technical aspects. 39
6.4.3.4 Information flow chart. 39
6.4.4 Message waiting indication . 40
6.4.4.1 Priority. 40
6.4.4.2 Example of usage . 40
6.4.4.3 Technical aspects. 40
6.4.4.4 Information flow chart. 40
6.5 Charging-related capabilities . 41
6.5.1 Changes in the charging rate of a call . 41
6.5.1.1 Priority. 41
6.5.1.2 Example of usage . 41
6.5.1.3 Technical aspects. 41
6.5.1.4 Information flow chart. 41
6.6 Traffic-related capabilities. 42
6.6.1 Event traceability. 42
6.6.1.1 Priority. 42
6.6.1.2 Example of usage . 42
6.6.1.3 Technical aspects. 42
6.6.1.4 Information flow chart. 43
6.6.2 Traffic control capabilities. 43
6.6.2.1 Priority. 43
6.6.2.2 Example of usage . 43
6.6.2.3 Technical aspects. 43
6.6.2.4 Information flow chart. 43
6.6.3 Avoidance of the cyclical routing of a call. 44
6.6.3.1 Priority. 44
6.6.3.2 Example of usage . 44
6.6.3.3 Technical aspects. 44
6.6.3.4 Information flow chart. 44
7 Non-circuit-related functional requirements .44
7.1 Call connection scenarios . 44
7.2 Calling party information handling capabilities . 45
7.2.1 Reception of the calling line identity . 45
ETSI
6 ETSI EG 201 722 V1.2.1 (2000-12)
7.2.1.1 Priority. 45
7.2.1.2 Example of usage . 46
7.2.1.3 Technical aspects. 46
7.2.1.4 Information flow chart. 46
7.2.2 Presentation of the complete CLI information to the PTN . 46
7.2.2.1 Priority. 46
7.2.2.2 Example of usage . 46
7.2.2.3 Technical aspects. 46
7.2.2.4 Information flow chart. 46
7.2.3 Addition or substitution of a calling line identity. 47
7.2.3.1 Priority. 47
7.2.3.2 Example of usage . 47
7.2.3.3 Technical aspects. 47
7.2.3.4 Information flow chart. 47
7.2.4 Provision of CLI information to an SP-initiated call.48
7.2.4.1 Priority. 48
7.2.4.2 Example of usage . 48
7.2.4.3 Technical aspects. 48
7.2.4.4 Information flow chart. 48
7.2.5 Relaying of the malicious call identification data of a received call . 49
7.3 Basic call set-up and clear-down capabilities. 49
7.3.1 Return speech path connection from the terminating PTN to the calling party . 49
7.3.1.1 Priority. 49
7.3.1.2 Example of usage . 49
7.3.1.3 Technical aspects. 49
7.3.1.4 Information flow chart. 49
7.3.2 Routing of an originating or incoming call from the PTN to the SP . 50
7.3.3 Indication of an originating or incoming call from the PTN to the SP. 50
7.3.3.1 Priority. 50
7.3.3.2 Example of usage . 50
7.3.3.3 Technical aspects. 50
7.3.3.4 Information flow chart. 51
7.3.4 Routing of a terminating call from the PTN to the SP. 51
7.3.5 Indication of a terminating call from the PTN to the SP . 51
7.3.5.1 Priority. 51
7.3.5.2 Example of usage . 51
7.3.5.3 Technical aspects. 52
7.3.5.4 Information flow chart. 52
7.3.6 Reception of an indication of the cause of an unsuccessful call . 52
7.3.6.1 Priority. 53
7.3.6.2 Example of usage . 53
7.3.6.3 Technical aspects. 53
7.3.6.4 Information flow chart. 53
7.3.7 Provision of information for the destination and routing of a call. 53
7.3.7.1 Priority. 53
7.3.7.2 Example of usage . 53
7.3.7.3 Technical aspects. 54
7.3.7.4 Information flow chart. 54
7.3.8 Call drop-back . 54
7.3.9 User interaction without service charging of the end user. 54
7.3.10 Reception of the originally dialled digits. 54
7.3.10.1 Priority. 54
7.3.10.2 Example of usage . 54
7.3.10.3 Technical aspects. 54
7.3.10.4 Information flow chart. 54
7.3.11 Disconnection of a call in progress . 55
7.3.11.1 Priority. 55
7.3.11.2 Example of usage . 55
7.3.11.3 Technical aspects. 56
7.3.11.4 Information flow chart. 56
7.3.12 Connection of a call to an interactive voice response unit in the PTN . 56
7.3.12.1 Priority. 56
ETSI
7 ETSI EG 201 722 V1.2.1 (2000-12)
7.3.12.2 Example of usage . 56
7.3.12.3 Technical aspects. 56
7.3.12.4 Information flow chart. 56
7.3.13 Alternate routing of a call or the indication of a call to another "point of presence" of the SP. 57
7.3.13.1 Priority. 57
7.3.13.2 Example of usage . 57
7.3.13.3 Technical aspects. 57
7.3.13.4 Information flow chart. 57
7.4 Supplementary call and data processing capabilities. 58
7.4.1 Interrogation of a network termination point for data delivery. 58
7.4.1.1 Priority. 58
7.4.1.2 Example of usage . 58
7.4.1.3 Technical aspects. 58
7.4.1.4 Information flow chart. 58
7.4.2 Overriding of the "incoming call barring" supplementary service . 59
7.4.2.1 Priority. 59
7.4.2.2 Example of usage . 59
7.4.2.3 Technical aspects. 59
7.4.2.4 Information flow chart. 59
7.4.3 Bypassing of the "call diversion" supplementary service. 60
7.4.3.1 Priority. 60
7.4.3.2 Example of usage . 60
7.4.3.3 Technical aspects. 60
7.4.3.4 Information flow chart. 60
7.4.4 Message waiting indication . 60
7.4.4.1 Priority. 60
7.4.4.2 Example of usage . 60
7.4.4.3 Technical aspects. 60
7.4.4.4 Information flow chart. 61
7.5 Charging-related capabilities . 61
7.5.1 Changes in the charging rate of a call . 61
7.5.1.1 Priority. 61
7.5.1.2 Example of usage . 61
7.5.1.3 Technical aspects. 61
7.5.1.4 Information flow chart. 61
7.6 Traffic-related capabilities. 62
7.6.1 Event traceability. 62
7.6.1.1 Priority. 62
7.6.1.2 Example of usage . 62
7.6.1.3 Technical aspects. 62
7.6.1.4 Information flow chart. 62
7.6.2 Traffic control capabilities. 63
7.6.2.1 Priority.
...