SIST-V ETSI/EG 201 916 V1.1.1:2003

• Abstract:

  It has been proposed to convert the Project Plan of STF 158 into an ETSI Guide, including phase 1 and phase 2.

• 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 916 V1.1.1 (2001-10) - Services and Protocols for Advanced Networks (SPAN); Service Provider Access; Development of standards to support Open Inter-Network Interfaces and Service Provider Access

SIST-V ETSI/EG 201 916 V1.1.1:2003 is the Slovenian version of ETSI Guide EG 201 916 Version 1.1.1. It is about Services and Protocols for Advanced Networks (SPAN) - Service Provider Access, and it explains how open inter-network interfaces and service provider access can be supported with published ETSI protocols.

The guide is written for service providers, network operators, and anyone assessing which signalling, API, and management capabilities can support advanced telephony services. In practice, it helps the reader judge which protocol families and network interfaces can carry the required service functions, and where additional implementation work or management support is needed.

What does SIST-V ETSI/EG 201 916 V1.1.1:2003 specify?

SIST-V ETSI/EG 201 916 V1.1.1:2003 specifies a staged technical guide for open inter-network and service provider access. It covers circuit-related (CR) and non-circuit-related (NCR) interfaces, including IN-related signalling technologies, and it uses benchmark services to test how well candidate protocols support service provider access requirements.

The document is organized around the service, architecture, interface, protocol, indirect-access, benchmark-mapping, and management aspects of SPAN service provider access. The main structure is:

• Clauses 4 to 5 - history, regulatory background, and service aspects
• Clause 6 - architectural aspects
• Clause 7 - interfaces and requirement priorities
• Clause 8 - protocol aspects
• Clause 9 - indirect service provider access interface (I-SPAI)
• Clause 10 - mapping of requirements against benchmark services
• Clause 11 - management plane requirements
• Clauses 12 to 13 - conclusions and future work
• Annex A - bibliography

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

The guide does not define a single protocol to be implemented everywhere. Instead, it compares service provider access requirements against existing and emerging protocols, then shows where support is already available, where it is partial, and where extra parameters or application-level work are needed.

Service model and benchmark services

Clause 5 uses five benchmark services from ETR 244 to test support for service provider access: Freephone, Premium rate, Virtual card calling, Virtual private network, and Universal personal telecommunications. This matters because the guide is not abstract - it checks protocol support against named service types that operators actually deploy.

Clause 10 maps the requirements against those benchmark services and marks the level of support. The table shows which requirements are core, optional, possible, general, or not applicable for each service, which helps a buyer or engineer see whether a chosen protocol set covers a service portfolio.

Circuit-related access over UNI and NNI

Clause 7 and clause 8 distinguish open access using the User to Network Interface (UNI) and the Network to Network interface (NNI). The guide shows that circuit-related UNI support is only a partial subset of the requirements, while circuit-related NNI support is broader.

In clause 8.1, the UNI analysis shows that some functions can be carried with existing basic call procedures, but others need new parameters or do not have support in the current protocol. In practice, that means a direct service-provider connection through UNI can be enough for some services, but not for all advanced service control features.

In clause 8.2, the NNI analysis is more positive. The guide compares the requirements against ISUP versions 1 to 4 and shows that later versions support more of the service provider access requirements. For readers, the practical point is that inter-network signalling can carry more service control information than basic UNI-based service handling.

Non-circuit-related access and control-plane support

Clause 8.3 compares the requirements with INAP CS-1/2/3, CAMEL Phase 1/2/3, Open INAP, and ETSI Open Service Access API. The guide concludes that the highest level of support is found in non-circuit-related signalling configurations together with management-plane access.

That matters because many advanced service features are not just call-routing tasks. They need service control, trigger handling, user interaction, and data exchange that are better aligned with IN capability sets, CAMEL, or API-based access than with basic circuit-switched call control alone.

Indirect access through a transit PTN

Clause 9 analyses indirect service provider access, where the SPAI is not connected directly to the local network of the service user but reaches it through a transit public telecommunications network (PTN). The guide states that the least capable network in the call path limits relayed support of Supplementary Services.

For implementers, this means indirect access has to be designed as a chain, not a single interface. A capability that works in the local network can still be limited by the intermediate PTN and the protocol used at the NNI.

Management plane requirements

Clause 11 groups management-plane needs into three categories: Traffic Related Capabilities, Performance Management Capabilities, and Electronic Bonding/Ordering. It links these needs to EG 201 965.

In practice, this tells the reader that service provider access is not only a signalling problem. Trigger setting, datafill, link monitoring, reconfiguration, and ordering processes are part of making the service work operationally.

What the conclusions say

Clause 12 draws the main technical conclusion: circuit-related UNI protocols support only part of the requirements, circuit-related NNI protocols support more, and the strongest support appears in non-circuit-related signalling combined with management-plane access. For a project decision, that is the document’s main selection rule.

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

• API (Application Programme Interface) - a modelling approach for exposing network functions to applications, used here as a path toward service provider access.
• CAMEL (Customized Application for Mobile networks Enhanced Logic) - an IN capability set used in the NNI analysis for mobile and service control features.
• IN (Intelligent Network) - the service-control framework used as a reference for advanced telephony service support.
• NNI (Network-Network Interface) - the interface between networks, used in this guide for service provider access across networks.
• SPAI (Service Provider Access Interface) - the access interface analyzed throughout the guide for direct and indirect service provider connection.
• SPAR (Service Provider Access Requirements) - the requirement set against which protocols and interfaces are assessed.
• UNI (User-Network Interface) - the interface between a user and the network, used here in circuit-related and non-circuit-related access scenarios.

Who uses SIST-V ETSI/EG 201 916 V1.1.1:2003?

Service providers use this guide when deciding how to present services through network interfaces and what protocol support they can rely on. Network operators use it when planning interconnection, service control, and management support for service provider access.

It is also useful for network equipment vendors, protocol designers, and technical planners working on IN, CAMEL, Open INAP, APIs, and management-plane functions. Quality managers and buyers can use it to compare candidate implementations against the service and protocol capabilities described in the clauses and tables.

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

Reference	What it contributes
ETR 244	Source for the benchmark services used in clause 5.
EG 201 722	Defines service provider access requirements for enhanced telephony services.
EG 201 807	Defines network operators' requirements for delivering service provider access.
EG 201 897	Provides the service provider access requirements and the priority set used in clause 7.3.
EG 201 899	Models service provider requirements using an API approach.
EG 201 965	Covers service provider access management requirements for open network access.
EG 201 988-3	Maps Open Service Access API Version 1 to SPAN requirements.
ES 201 915-1	Gives the Open Service Access API parts used in the API discussion.
TR 101 917	Provides API mapping for Open Service Access.
EN 300 403-1 through 7	DSS1 protocol specification used in the UNI analysis.
ETS/EN 300 356 series	ISUP versions used in the NNI and indirect-access analyses.
ETS 300 208, ETS 300 711, ETS 300 712, ETR 172, ETS 300 779	Service definitions used for the benchmark services in clause 5 and the mapping in clause 10.
EN 300 650	Message Waiting Indication service description referenced in the benchmark mapping.

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

The document contains architectural figures for direct and indirect service provider access, including circuit-related and non-circuit-related call scenarios. It also contains cross-reference tables that map requirements to priorities, protocols, and benchmark services.

Tables 2 to 7 and Tables 10 to 15 are the main technical core of the guide. They show how each requirement is assessed against DSS1, ISUP, INAP, CAMEL, Open INAP, and ETSI Open Service Access API, and they are used for design review, protocol selection, and implementation planning.

The document also includes a bibliography in Annex A and a short history record at the end.

SLOVENSKI STANDARD
01-november-2003
Storitve in protokoli za napredna omrežja (SPAN) - Dostop ponudnika storitve -
Razvoj standardov za podporo odprtih medomrežnih vmesnikov in dostopa
ponudnika storitve
Services and Protocols for Advanced Networks (SPAN) - Service Provider Access -
Development of standards to support Open Inter-Network Interfaces and Service
Provider Access
Ta slovenski standard je istoveten z: EG 201 916 Version 1.1.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
Services and Protocols for Advanced Networks (SPAN);
Service Provider Access;
Development of standards to support Open Inter-Network
Interfaces and Service Provider Access

2 ETSI EG 201 916 V1.1.1 (2001-10)

Reference
DEG/SPAN-141605
Keywords
Access
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://portal.etsi.org/tb/status/status.asp
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 2001.
All rights reserved.
ETSI
3 ETSI EG 201 916 V1.1.1 (2001-10)
Contents
Intellectual Property Rights.4
Foreword.4
Introduction .4
1 Scope.6
2 References.6
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 History and Regulatory Background.9
4.1 Development of the Market.9
4.2 EC Directives.9
5 Service aspects.9
5.1 Service Definition.9
5.2 Benchmark Services.9
5.3 Service Provider Access Management .10
6 Architectural Aspects.10
6.1 API - Architectures.12
6.2 Management Architecture.12
7 Interfaces.13
7.1 Open Access using the User to Network Interface.13
7.2 Open Access using the Network to Network interface.14
7.3 Requirements and Priorities .15
7.4 SP-PNO Scenarios analysed in this ETSI Guide.17
8 Protocol Aspects.18
8.1 Impact of a service provider's access interface on the UNI between network operators and service
providers.18
8.2 Impact of a service provider's access interface on the NNI between network operators and service
providers.29
8.3 IN Protocol and API Assessment .42
8.4 Telephony IP Harmonization Aspects.54
9 Indirect Service Provider access interface (I-SPAI).55
10 Mapping of Requirements against Benchmark Services.72
11 Management Plane requirements to support services. .75
11.1 Relationship between Management Plane, Control Plane, and User Plane.75
11.2 Management Plane categories: .75
12 Conclusions.77
13 Future Work.77
13.1 New/Emerging Protocols.77
13.2 New Requirements.77
Annex A (informative): Bibliography.78
History .79

ETSI
4 ETSI EG 201 916 V1.1.1 (2001-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 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://www.etsi.org/legal/home.htm).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Guide (EG) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
Introduction
The purpose of the present document is to provide a source of reference material to enable Service Providers and
Network Operators to determine standardized facilities that are available in published ETSI protocols to support the
introduction of services. The present document also validates a number of benchmark services initially identified by the
European Commission [1] for third-party service provision using a generic capability set for Open Intelligent Network
Interconnection and the Service Provider Access Requirements (SPAR) that are captured in clause 7.3.
A number of open network architectural solutions are assessed including IN, Mobile Networks, Internet and ISDN.
Following regulatory and commercial drivers to expand the range and geographical scope of telecommunications
services, ETSI working groups are identifying new requirements and developing appropriate standards solutions to
support open inter-network and service provider access. The present document covers the Open Inter-Network and
nd
Open Network Access Requirements for the Fixed Network, 2 and 3rd Generation Mobility and Network
Management. It addresses these requirements by taking a top down approach including Service requirements,
Functional and Physical Architectures.
The present document commences with an introduction to the initial benchmark services to be provided by a Service
Provider/Network Operator under European Commission mandate BC-T-305 [1] using Intelligent Network
Interconnection. The present document then describes open access options via either Circuit Related and Non circuit
related interfaces utilizing both direct service provider interconnection, via a SPAI, and indirect service provider
interconnection via an intermediate Network.
The present document enumerates the activities in relation to the production of a set of open standards for internetwork
control plane, management plane and service provider access interfaces. A Public Network Operator can also take the
SP role, and indeed nothing in the present document should be taken as precluding such a possibility.
The Service Provider definition is not intended to map to certain country-specific meanings of the term, which are often
taken as being "resellers", but is strictly intended in this context to cover the role of producing the telecommunications
service.
ETSI
5 ETSI EG 201 916 V1.1.1 (2001-10)
Requirement Documents
SPA
EG 201 722
EG 201 897
PNO
EG 201 807
SP API
EG 201 899
Management
EG 201 965
Management
SPAI
Switching
Transmission (MP)
'X'
Management Management
SPAI
'Q'
'Q'
(CP/UP)
Switching Switching
Transmission Transmission
Called party
NNI
Calling party
UNI
PNO PNO
Figure 1: Reference Architecture for SP-PTN interfaces
ETSI
6 ETSI EG 201 916 V1.1.1 (2001-10)
1 Scope
The present document aims to facilitate the technical introduction of open inter-network and service provider access. It
includes architectural scenarios and guidelines, and identifies implementation requirements to support these more
advanced services. The format is based on a staged approach, covering both circuit-related (CR) and non-circuit-related
(NCR) interfaces, including IN-related signalling technologies. It commences with the definition of service provider
architectural and implementation capabilities, the implementation of which is initially based on standards existing at the
start of the work. ETSI TC SPAN (that has produced the present document) has also been responsible for co-ordination
and the enhancement of protocols, where necessary, in order to meet the Service Provider Access Requirements (SPAR)
as outlined in the present document. Open Service Provider access is enabled by means of enhanced User to Network
and Network-to-Network Interfaces. A number of Initial benchmark Services together with Service support and network
management requirements are also considered.
Cross-referencing of the SPAR requirements and the candidate protocols is detailed through sets of tables. Existing
protocol standards are utilized in the analysis, and are considered as candidates for re-use. Emerging protocols and APIs
were also considered.
The overall objective of the present document is to map out the facilities and protocols needed to allow delivery of
telecommunications services across multiple networks, including networks that may be geographically or technically
diverse in nature. Where lack of support in protocol capabilities has been identified, these deficiencies are noted as
items for further work.
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.
[1] ETSI ETR 244: "Intelligent Network (IN); ETSI workplan for IN; (Mandate BC-T-305, step 1)".
[2] ETSI EG 201 722: "Intelligent Network (IN); Service provider access requirements; Enhanced
telephony services".
[3] ETSI EG 201 807: "Network Aspects (NA); Intelligent Network (IN); Network operators'
requirements for the delivery of service provider access".
[4] ETSI EG 201 897: "Services and Protocols for Advanced Networks (SPAN); Service Provider
Access; Service Provider Access Requirements in a Fixed and Mobile Environment".
[5] Directive 97/33/EC of the European Parliament and of the Council of 30 June 1997 on
interconnection in Telecommunications with regard to ensuring universal service and
interoperability through application of the principles of Open Network Provision (ONP).
[6] Directive 98/10/EC of the European Parliament and of the Council of 26 February 1998 on the
application of open network provision (ONP) to voice telephony and on universal service for
telecommunications in a competitive environment.
[7] ETSI ETS 300 208: "Integrated Services Digital Network (ISDN); Freephone (FPH)
supplementary service; Service description".
[8] ETSI ETS 300 712: "Integrated Services Digital Network (ISDN); Public Switched Telephone
Network (PSTN); Premium Rate (PRM) service; Service description".
[9] ETSI ETS 300 711: "Integrated Services Digital Network (ISDN); Public Switched Telephone
Network (PSTN); Virtual Card Calling (VCC); Service description".
ETSI
7 ETSI EG 201 916 V1.1.1 (2001-10)
[10] ETSI ETS 300 779 (Edition 1): "Network Aspects (NA); Universal Personal Telecommunication
(UPT); Phase 1 - Service description".
[11] ETSI EG 201 965: "Services and Protocols for Advanced Networks (SPAN); Service Provider
Access; Service Provider Access Management Requirements for Open Network Access".
[12] ETSI EN 300 403-1 through 7:"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/8) modified]". and
subsequent parts.
NOTE: Supplementary Services (SS) are described elsewhere.
[13] ETSI ETS 300 356-1 through 19: "Integrated Services Digital Network (ISDN); Signalling System
No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services
[ITU-T Recommendations Q.761 to Q.764 (1994)]", and subsequent parts. ISUP Version 2.
[14] ETSI EN 300 356-1 through 36: "Integrated Services Digital Network (ISDN); Signalling System
No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 1: Basic services
[ITU-T Recommendations Q.761 to Q.764 (1997) modified]", and subsequent parts. ISUP
Version 3.
[15] ETSI EN 300 356-1 through 21: "Integrated Services Digital Network (ISDN); Signalling System
No.7; ISDN User Part (ISUP) version 4 for the international interface; Part 1: Basic services
[ITU- T Recommendations Q.761 to Q.764 (2000) modified]", and subsequent parts; ISUP
Version 4.
[16] ETSI ETS 300 121 (Edition 1): "Integrated Services Digital Network (ISDN); Application of the
ISDN User Part (ISUP) of CCITT Signalling System No.7 for international ISDN interconnections
(ISUP version 1)". (Based on ITU-T recommendation Q.767)
[17] ETSI TS 129 002: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); Mobile Application Part (MAP) specification
(3GPP TS 29.002)".
[18] ETSI ETS 300 374-1: "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core
Intelligent Network Application Protocol (INAP); Part 1: Protocol specification".
[19] ETSI EN 301 140-1 (V1.3.4): "Intelligent Network (IN); Intelligent Network Application Protocol
(INAP); Capability Set 2 (CS2); Part 1: Protocol specification".
[20] ETSI TS 122 078: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); Customised Applications for Mobile network
Enhanced Logic (CAMEL); Service description; Stage 1(3GPP TS 22.078)".
[21] ETSI EG 201 899 (V1.1.1): "Services and Protocols for Advanced Networks (SPAN); Service
Provider Access; Modelling service provider access requirements using an API approach".
[22] ETSI ES 201 915-1 through 12: "Open Service Access; Application Programming Interface;
Part 1: Overview".
[23] ETSI EG 201 988-1: "Services and Protocols for Advanced Networks (SPAN); Service Provider Access
Requirements (SPAR); Open Service Access for API requirements version 1".
[24] ETSI EG 201 988-2: "Services and Protocols for Advanced Networks (SPAN); Service Provider Access
Requirements (SPAR); Open Service Access for API requirements version 2".
[25] ETSI ES 201 296: "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN
User Part (ISUP); Signalling aspects of charging".
[26] ETSI ETR 172: "Business TeleCommunications (BTC); Virtual Private Networking (VPN);
Services and networking aspects; Standardization requirements and work items".
[27] ETSI EG 201 367: "Intelligent Network (IN); Number Portability Task Force (NPTF); IN and
Intelligence Support for Service Provider Number Portability".
ETSI
8 ETSI EG 201 916 V1.1.1 (2001-10)
[28] ETSI TR 101 917-1 through 12: "Services and Protocols for Advanced Networks (SPAN); API
mapping for Open Service Access; Part 1: General issue on API mapping".
[29] ETSI EG 201 988-3: "Services and Protocols for Advanced Networks (SPAN); Service Provider
Access Requirements (SPAR); Mapping of Open Service Access for API version 1 to SPA
requirements".
[30] ETSI EN 300 650: "Integrated Services Digital Network (ISDN); Message Waiting Indication
(MWI) supplementary service; Service description".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions of Service Provider related terms given in [2], [3]
and [4] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
API Application Programme Interface
BICC Bearer Independent Call Control
CAMEL Customized Application for Mobile networks Enhanced Logic
CdPy Called Party
CgPy Calling Party
CS-1 IN Capability Set 1
CUSF Call Unrelated Service Function
DSS1 Digital Subscriber Signalling System No. 1
GMSC Gateway Mobile Switching Centre
HLR Home Location Register
IN Intelligent Network
INAP Intelligent Network Application Part
IP Internet Protocol
ISDN Integrated Services Digital Network
ISUP ISDN User Part
MAP Mobile Application Part
NNI Network-Network Interface
ONP Open Network Provision
PTN Public Telecommunications Network
PTNorig Public Telecommunications Network originating
PTNterm Public Telecommunications Network terminating
SCF Service Control Function
SP Service Provider
SPAI Service Provider Access Interface
SPorig Service Provider originating
SPterm Service Provider terminating
SS Supplementary Service
SSF Service Switching Function
SSL Secure Sockets Layer
TC Transaction Capabilities
UNI User-Network Interface
UPT Universal Personal Telecommunications
UUS User User Signalling
VMSC Visited MSC
VPN Virtual Private Network
ETSI
9 ETSI EG 201 916 V1.1.1 (2001-10)
4 History and Regulatory Background
4.1 Development of the Market
In the original European work done in the 1980s, a clear link was drawn between the availability of economically
efficient telecommunications services and the development of the economy of the region as a whole. Stimulating
competition to enable these services was seen as key.
The development of competition in the telecommunications market in Europe has been characterized, initially, by the
liberalization of services, at the beginning of the 1990s. This was followed in 1998 by the liberalization of the provision
of infrastructure.
However, for a provider to deliver services where they do not themselves have control of the access network, this will
necessitate interconnection with and access to the network of a relevant network operator. This access has been limited
to ordinary user plane interconnection (call origination, transit and call termination), with the attendant limitations on
the type of services that can be delivered using this mechanism.
In order to enable advanced services, enhanced forms of access are required. These forms fall into two generic
types - control plane access and management plane access. It is in this context that the current work has been
progressed.
4.2 EC Directives
EC directives 97/33/EC [5] and 98/10/EC [6] require reasonable requests for access to the networks of operators with
Significant Market Power (SMP) to be met. In order to reduce the costs for all parties concerned, this work is aimed at
standardizing as many of the envisaged capabilities as possible.
5 Service aspects
In developing the present document, five initial benchmark services have been identified, see [1]. These are currently
supported under IN and terminal mobility signalling protocols. The benchmark services will be utilized to test the
extension of the signalling protocols in support of open network access.
5.1 Service Definition.
Services, as defined by current ETSI Standards, are taken within the present document as a benchmark for consideration
of protocol support - see Benchmark IN services as listed in clause 5.1.2. Service Providers have the opportunity to
develop these or create their own services to meet specific user requirements. Such services may be developed by
utilizing the flexibility offered through an API or by an IN.
5.2 Benchmark Services
A list of benchmark services are listed in table 1 as defined in ETR 244 [1].
The identified services all have existing service definition for either the PSTN or the ISDN, as defined in table 1.
Table 1: Identification of service definitions for benchmark services (see note)
Identified service PSTN service definition ISDN service definition
Freephone --- ETS 300 208 [7]
Premium rate ETS 300 712 [8] ETS 300 712 [8]
Virtual card calling ETS 300 711 [9] ETS 300 711 [9]
Virtual private network ETR 172 [26] (see note) ETR 172 [26] (see note)
Universal personal telecommunications ETS 300 779 [10] ETS 300 779 [10]
NOTE: This is not a service, but an alternative means of provision of existing services defined for the private network.
ETR 172 [26] identifies the work items required for this definition.
ETSI
10 ETSI EG 201 916 V1.1.1 (2001-10)
The benchmark services have been used to specify the Open-INAP Protocol work being developed by ETSI
WG-SPAN12 as a special PICS Proforma (DEN/SPAN-120084 (see bibliography)) to accompany IN CS-3, and they
have also been mapped in the present document against the capabilities noted in the requirements clause 7.3 of the
present document.
NOTE: ETSI WG-SPAN12 are also using the number portability service as defined in EG 201 367 [27] as an
additional benchmark service for OPEN-INAP.
5.3 Service Provider Access Management
Network Management requirements to support Service Provider Access are listed in the companion Guide EG 201 965 [11].
6 Architectural Aspects
A signalling connection between a public telecommunications network operator and a service provider is shown below
in figure 2. The physical connection of the call is only extended from the public telecommunications network to the
service provider's equipment for circuit related (CR) access.
For calls from a calling party (CgPy) in the originating PTN (PTNorig) to a called party (CdPy) in the terminating PTN
(PTNterm), in which both PTNs and SPs are involved, various call connection scenarios are possible. Figure 2
visualizes two examples of a call connection scenario from the viewpoint of the requirements of the SPs of the
originating- and terminating-call-related services, called SPorig and SPterm, respectively.

Legend: Tw o-w ay speech and/or signalling path of scenario A =
T w o-way speech and/or signalling path of scenario B =
SP O rig SP T erm
Services of
Services of
term inating calls
originating calls
SPAI SPAI
B earer extended
for C R case
PTN Term
PTN O rig PT N T erm
PTN Transit
Scenario B Scenario A
C alled P arty (C dP y)
C alling P arty (C gP y)
Figure 2: Examples of call connection scenarios for circuit related SP access
Scenario A is an example of a call in which SPorig is involved. In this scenario A, the call is forwarded from the
PTNorig to SPorig which provides a service to the call. SPorig returns the call to the PTNorig. The call is then
forwarded from the PTNorig, eventually via a transit network (PTNtran), to the PTNterm in which the call is terminated
at the called party's (CdPy) line.
ETSI
11 ETSI EG 201 916 V1.1.1 (2001-10)
Scenario B is an example of a call in which both the SPorig and the SPterm are involved. In this scenario, the call is
forwarded from the PTNorig to SPorig which provides a service to the call. SPorig returns the call to the PTNorig. The
call is then forwarded from the PTNorig, eventually via a transit network (PTNtran), to the PTNterm. Then, from the
PTNterm the call is forwarded to SPterm which provides a service to the call. SPterm returns the call to the PTNterm, in
which the call is terminated at the called party's (CdPy) line.
For calls from a calling party (CgPy) in the originating PTN (PTNorig) to a called party (CdPy) in the terminating PTN
(PTNterm), in which both PTNs and SPs are involved, various call connection scenarios are possible. Figure 3
visualizes two examples of a call connection scenario in the NCR case from the viewpoint of the requirements of the
SPs of the originating- and terminating-call-related services, called SPorig and SPterm, respectively.

Legend: Two-way speech and/or signalling path of scenario C =
Two-way speech and/or signalling path of scenario D =
N on-circuit related signalling path of scenario C =
Non-circuit related signalling path of scenario D =
SP O rig SP Term
Services of
Services of
terminating calls
originating calls
SPAI SPAI
Signalling for
N CR case
PTN Term
PTN O rig PTN Term
PTN Transit
Scenario D Scenario C
Called Party (CdPy)
Calling Party (CgPy)
Figure 3: Examples of call connection scenarios in the case of a non-circuit-related SP Access
Scenario C is an example of a call in which SPorig is involved. In this scenario, the signalling in the control plane is
forwarded from the PTNorig to SPorig which provides a service to the call. Then, the signalling in the control plane is
returned to the PTNorig, which forwards the call to the PTNterm, eventually via a transit network (PTNtran), in which
the call is terminated at the called party's (CdPy) line.
Scenario D is an example of a call in which SPorig is involved. In this scenario, the signalling in the control plane is
forwarded from the PTNorig to SPorig which provides a service to the call. The signalling in the control plane is then
returned to the PTNorig, which forwards the call to the PTNterm, eventually via a transit network (PTNtran). Then, the
control plane signalling is forwarded from the PTNterm to SPterm which provides a service to the call. The signalling
in the control plane is then returned to the PTNterm, in which the call is terminated at the called party's (CdPy) line.
It is evident that a range of ETSI standards need to be invoked for the provision of the SPAI supporting UNI and NNI
configurations e.g. DSS1 [12], ISUP [13], [14], [15], [16], GSM MAP [17], INAP CS1, CS2, CS3 [18], [19], CAMEL
[20]). Implementation of these standards will lead to protocol-specific implementations of SP applications.
ETSI
12 ETSI EG 201 916 V1.1.1 (2001-10)
6.1 API - Architectures
EG 201 899 [21] models service provider requirements using an API approach that leads to API definitions in
ES 201 915-1 [22] and documents EG 201 988-1 [23] and EG 201 988-2 [24] cover open service access API
requirements.
An API modelling approach is referenced in the architecture under consideration in EP TIPHON. API modelling is
being developed in the JAIN and PARLAY consortia and standardized in ETSI WG SPAN12 and 3GPP WG CN5. The
following figure shows how different network technologies existing in today's networks can be integrated through API
to the application control plane.
Application Domain
M
a
n
API e.g. OSA
a
g
QoS
e
Transport Broker
Confirmed
m
Unconfirmed
e
API e.g. OSA
n
t
Bearer
IP
Real World Network
ATM
ISDN
Figure 4: Proposed conceptual model to support IP under consideration by EP TIPHON
6.2 Management Architecture
The management function interface is shown in the following protocol stack allowing current tried and tested signalling
layers to be used.
SP
Management
SPAI
Switching
Transmission (MP)
'X'
Management Management
SPAI
'Q' 'Q'
(CP/UP)
Switching Switching
Transmission Transmission
Called party
NNI
Calling party
UNI
PNO PNO
Figure 5: Reference Architecture for SP-PTN management requirements
ETSI
13 ETSI EG 201 916 V1.1.1 (2001-10)
7 Interfaces
7.1 Open Access using the User to Network Interface
Figures 6 and 7 illustrate the SPAI for circuit related and non-circuit-related access using the UNI interface
configuration respectively.
SP
DSS1
/GSM access
SPAI
PTN
CPE
CPE
Figure 6: Circuit-related service provider access using UNI

SP
SPAI
API API API
HLR
SCF SSF
(GSM)
(GSM)
PTN
CPE CPE
Figure 7: Non-circuit-related service provider access using UNI
ETSI
14 ETSI EG 201 916 V1.1.1 (2001-10)
7.2 Open Access using the Network to Network interface
Figures 8 and 9 illustrate the SPAI for circuit related and non-circuit-related access using the NNI interface
configuration respectively.
SP
ISUP/BICC
SPAI
PTN
CPE
CPE
Figure 8: Circuit-related Service Provider access using NNI

SP
SCF SCF HLR
(GSM)
SPAI
INAP/CAP
INAP MAP
MAP
HLR
HLR SCF SSF
(GSM) (GSM)
PTN
CPE
CPE
Figure 9: Non-circuit-related Service Provider access using NNI
ETSI
15 ETSI EG 201 916 V1.1.1 (2001-10)
7.3 Requirements and Priorities
Tables 2 through to 7 give a cross-reference to the various requirements and their allocation to various priorities. Where
a requirement priority is indicated, this is taken from the associated requirements document (EG 201 897 [4]).
Table 2: Requirements cross reference - calling party information handling capabilities
No. Reference Requirement Enhanced Mobile and
Telephony Internet
CR NCR CR NCR
A1 [2] 5.2.1 Reception of the calling line identity - Application of the High/High High/High
[3] 5.2.2 CLIR supplementary service
A2 [2] 5.2.2 Presentation of the complete CLI information to the PTN High High --- ---
A3 [2] 5.2.3 Addition or substitution of a calling line identity High High --- ---
A4 [2] 5.2.4 Provision of CLI information to an SP-initiated call High High --- ---
A5 [2] 5.2.5 Relaying of the malicious call identification data of a High/High NA/NA --- ---
[3] 5.2.1 received call
A6 [4] 5.1.1 Network Location Determination --- --- High High
A7 [4] 5.1.2 Geographic Location Determination --- --- High High
A8 [4] 5.2.1 Determination of the terminal capabilities of the SP's --- --- High High
service user
Table 3: Requirements cross reference - basic call set-up and clear-down capabilities
No. Reference Requirement Enhanced Mobile and
Telephony Internet
CR NCR CR NCR
B1 [2] 5.3.1 Return speech path connection from the terminating PTN to High High
the calling party
B2 [2] 5.3.2 Routeing of an originating or incoming call from the PTN to High NA
the SP
B3 [2] 5.3.3 Indication of an originating or incoming call from the PTN to NA High
the SP
B4 [2] 5.3.4 Routeing of a terminating call from the PTN to the SP High NA
B5 [2] 5.3.5 Indication of a terminating call from the PTN to the SP NA High
B6 [2] 5.3.6 Reception of a notification of the cause of an unsuccessful High High
call
B7 [2] 5.3.7 Provision of information for the destination and routeing of a High High
call
B8 [2] 5.3.8 Call drop-back Medium NA
B9 [2] 5.3.9 User interaction without service charging of the end user Medium/NA/NA
High
B10 [2] 5.3.10 Reception of the originally dialled digits by the SP low low
B11 [3] 5.3.1 Reception of the originally dialled digits by the PTN low low
B12 [2] 5.3.11 Disconnection of a call in progress Medium Medium
B13 [2] 5.3.12 Connection of a call to an interactive voice response unit in NA Medium
the PTN
B14 [2] 5.3.13 Alternate routeing of calls or the indications of calls to Medium Medium
another "point of presence" of the SP
B15 [3] 5.3.2 Alternate routeing of a call or the indication of a call to Medium Medium
another "point of presence" of the PTN
B16 [4] 5.4.1 Indication of the disconnection of a call --- --- High High
B17 [4] 5.4.5 Supervision of a dropped-back call --- --- Void Medium
B18 [4] 5.4.2 Join operation of individual legs of a call --- --- High High
B19 [4] 5.4.3 Split operation of individual legs of a call --- --- High High
B20 [4] 5.4.7 Multimedia Multiparty call control --- --- High High
B21 [4] 5.4.8 User Interaction for Text Delivery --- --- High High
B22 [4] 5.4.9 User-Plane resource negotiation and selection --- --- High High

ETSI
16 ETSI EG 201 916 V1.1.1 (2001-10)
Table 4: Requirements cross reference - supplementary call and data processing capabilities
No. Reference Requirement Enhanced Telephony Mobile and Internet
CR NCR CR NCR
C1 [2] 5.4.1 Interrogation of a network termination point for Medium Medium
data delivery
C2 [2] 5.4.2 Overriding of the "incoming call barring" High High
supplementary service
C3 [2] 5.4.3 Bypassing of the "call diversion" supplementary low low
service
C4 [2] 5.4.4 Message waiting indication High High
C5 [3] 5.5.1 Application contents screening High High
C6 [4] 5.2.2 Modification of the terminal capabilities of the SP's --- --- High High
service user
C7 [4] 5.2.3 Modification of the Personality Device/Module of --- --- High High
the SP's service user
C8 [4] 5.3.1 Alteration of the profile of the SP's Service --- --- High High
Subscriber
C9 [4] 5.4.4 Delivery of information to the SP's service user --- --- Medium Medium
prior to alerting
Table 5: Requirements cross reference - charging-related capabilities
No. Reference Requirement Enhanced Mobile and
Telephony Internet
CR NCR CR NCR
D1 [2] 5.5.1 Changes in the charging rate of a call - Dynamic High High
D2 [3] 5.5.2 Charging mechanisms between SP and PTNO - Dynamic High High
D3 [4] 5.6.1 Provision of call charging information in real time --- --- High High
D4 [4] 5.6.2 Exchange of charge detail record information in real time --- --- High High
D5 [11] Billing and Accounting mechanisms between SP and PNO Medium Medium Medium Medium

Table 6: Requirements cross reference - traffic-related capabilities
No. Reference Requirement Enhanced Mobile and
Telephony Internet
CR NCR CR NCR
E1 [2] 5.6.1 Event traceability requested by the SP Medium Medium
E2 [3] 5.4.1 Event traceability requested by the PTN High High
E3 [2] 5.6.2 Traffic control capabilities controlled by the SP Medium Medium
E4 [3] 5.4.2 Traffic control capabilities controlled by the PTN High High
E5 [2] 5.6.3 Avoidance of the cyclical routeing of a call Medium/NA/NA
[3] 5.4.3 High
E6 [4] 5.4.6 Avoidance of the cyclical routeing of signalling or user --- --- High High
messages
Table 7: Requirements cross reference - management-related capabilities
No. Reference Requirement Enhanced Mobile and
Telephony Internet
CR NCR CR NCR
F1 [4] 5.5.1 Reporting of network events for measuring the quality of --- --- Medium Medium
service
F2 [4] 5.5.2 Reporting of network events for the purpose of fault --- --- High High
diagnostics
F3 [4] 5.5.3 Request for event monitoring and subsequent reporting --- --- High High
F4 [4] 5.5.4 Electronic ordering of network management functions --- --- High High

ETSI
17 ETSI EG 201 916 V1.1.1 (2001-10)
Table 8: Monitored deliverables
Deliverable Work item number Title
EG 201 722 DEG/SPAN-061601 Intelligent Network (IN);
(V1.2.1) [2] Service provider access requirements;
Enhanced telephony services
EG 201 897 [4] DEG/SPAN-141602 Services and Protocols for Advanced Networks (SPAN);
Service Provider Access;
Service Provider Access Requirements in a fixed and mobile environment
EG 201 807 DEG/SPAN-141603 Network Aspects (NA);Intelligent Network (IN);
(V1.1.1) [3] Network operators' requirements for the delivery of service provider access
EG 201 899 DEG/SPAN-140504 Services and Protocols for Advanced Networks (SPAN);
(v1.1.1) [21] Service Provider Access;
Modelling service provider access requirements using an API approach
EG 201 988-3 DEG/SPAN-1451606-3 Services and Protocols for Advanced Networks (SPAN);
[29] Service Provider Access Requirements
Mapping of Open Service Access API Version 1
ES 201 915-1 DEN/SPAN-120070-1/12 Services and Protocols for Advanced Networks (SPAN);
through 12 [22] Open Service Access;
Application Programming Interface;
All Parts
TR 101 917-1 DEN/SPAN-120075-1/18 Services and Protocols for Advanced Networks (SPAN);
through 12 [28] API mapping for Open Service Access;
All Parts
EG 201 965 DEG/SPAN-141607 Services and Protocols for Advanced Networks (SPAN);
[11] Service Provider Access;
Service Provider Access Management Requirements for Open Network
Access
Not allocated DEN/SPAN-120084 PICS-Proforma for OPEN CORE INAP based on OPEN-INAP CS-2 subset,
yet (see SCF-SCF, CUSF; OPEN-INAP CS-3 subset; SCF-SSF and SCF-SRF.
bibliography)
NOTE: CS-3 is not revising the SCF-SCF interface or the CUSF, which are being carried forward from CS-2. Therefore
the PICS proforma for OPEN-INAP will be applied to the CS-2 interfaces noted above.

7.4 SP-PNO Scenarios analysed in this ETSI Guide
The following figure identifies the results for the various SP-PNO configurations contained in clauses 8 and 9. The
direct cases apply when the SPAI is connected to the same network as the SP' service user, whilst in the indirect case.
Table 9: Index to results of SP-PNO scenarios analysed in the present document
Service Provider Access Interface
DSS1 ISUP INAP CAMEL Open INAP ETSI OSA
93, 98, 01 V1-4 CS-1/2/3 Phase 1/2/3 CS-2; CS-3 API
Direct 10 11 12 12 12 12
Indirect 13 13 13 13 13 13
ETSI
18 ETSI EG 201 916 V1.1.1 (2001-10)
8 Protocol Aspects
8.1 Impact of a service provider's access interface on the UNI between network operators and
service providers
Any UNI that provides a circuit-related service provider interface will need to transfer additional information as well as the existing basic call requirements. Table 10 shows the
results of the analysis of the Service Provider Access Requirements against a Service Provider Access Interface configured using DSS.1 (1993, 1998, 2001). Support mechanism
and parameters are indicated in table 10.
Table 10: Requirements assessment for SP<>NO circuit-related UNI interface
NOTE: Any feature provided as an application over UUS requires each of the Users to have an ISDN terminal.
Issues relating to the UNI Protocol 1 UNI Protocol 2 UNI Protocol 3
support of the DSS.1 1993 DSS.1 1998 DSS.1 2001
requirement EN 300 403 (all) EN 300 403 (all parts, EN 300 403 (all parts,
(Edition 1) [12] dates up to 1998) [12] dates up to 2001) [12]
No. Requirement Information to Support Mechanism(s) Support Mechanism(s) Support Mechanism(s)
transfer and Parameters and Parameters and Parameters
A1 Reception of the Receive CLI (which The current protocol Support available as a Support available as a Support available as a
calling line may be restricted) requires procedures of supplementary service. supplementary service. supplementary service.
identity - Application of including the CLIP supplementary Override of CLIR for the Override of CLIR for the Override of CLIR for the
the CLIR Restricted flag (if set) service to provide this SPs Service user is SPs Service user is SPs Service user is
supplementary for calls from, or to, capability. CLIR will subject to national subject to national subject to national
service. one of the SPs restrict provision of CLI, regulation. regulation. regulation.
service-subscribers.
unless some form of
override capa
...