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

• Abstract:

  To identify Service Provider Access Requirements that apply to the TMN Open Network Access and to determine whether these requirements are supported by existing standards.

• 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 965 V1.1.1 (2001-11) - Services and Protocols for Advanced Networks (SPAN); Service Provider Access; Service Provider Access Management Requirements for Open Network Access

SIST-V ETSI/EG 201 965 V1.1.1:2003 is the Slovenian adoption of ETSI EG 201 965 V1.1.1, published by SIST. It specifies management requirements for open network access between a Service Provider and a Public Telecommunications Network operator, and it is aimed at the management-plane interface used to exchange service, charging, routing and monitoring information.

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

SIST-V ETSI/EG 201 965 V1.1.1:2003 specifies which Service Provider Access Requirements (SPAR) have a management implication for TMN Open Network Access. The document also shows how those requirements relate to existing standards and whether the needed information exchange is best handled over the management plane or the control signalling plane.

The document is organized into these main parts:

• Clause 1: Scope
• Clause 2: References
• Clause 3: Definitions and abbreviations
• Clause 4: Background to the subject
• Clause 5: Management requirements for open network access
• Annex A: Bibliography

Clause 5 is the core of the document. It turns the wider SPAR studies into management requirements, so a reader can see what has to be agreed, configured, monitored or signalled between the Service Provider and the network operator.

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

SIST-V ETSI/EG 201 965 V1.1.1:2003 is built around a Service Level Agreement (SLA) for each access requirement that needs management information exchange. The SLA is where the Service Provider and the PTN operator define what data is exchanged, how it is exchanged, and whether the exchange happens per call, through signalling, or through a management protocol.

The document separates requirements into three management groups

Clause 1 says the covered management requirements fall into:

• Traffic Related Capabilities
• Performance Management Capabilities
• Electronic Bonding/Ordering

In practice, this classification helps a buyer or engineer decide whether a feature is about call control, service performance, or ordering and configuration.

Clause 5 maps each SPAR to a management treatment

Table 2 is the key analysis table. It reviews each SPAR item and states whether management information must be exchanged, whether the requirement is per-call, and whether signalling messages or a management protocol carry the data. That matters because implementation choices depend on where the information flows and whether the feature needs real-time handling.

Examples of the main management patterns are:

• CLI-related requirements A1-A5 use signalling messages across the SPAI, with the SLA defining which Calling Line Identity (CLI) data is passed and how malicious call identification data is relayed.
• Location and terminal capability requirements A6-A8 need the SLA to define what network location, geographic location, terminal capability or response data is requested and returned.
• Call routing and indication requirements B1-B22 cover return speech path, originating and terminating call indications, unsuccessful-call causes, originally dialled digits, call disconnection, interactive voice response, alternate routing, call join/split, multimedia multiparty control, text delivery and user-plane resource negotiation.
• Charging requirements D1-D5 cover dynamic charging changes, real-time charging advice, real-time charge detail record exchange, and billing and accounting mechanisms.
• Monitoring and control requirements E1-E6 and F1-F4 cover event traceability, traffic control, avoidance of cyclic routing, quality-of-service reporting, fault diagnostics, event monitoring and electronic ordering.

The document identifies where information transfer should happen

Table 3 gives a practical mapping of SPAR items to the management plane or signalling plane. This is useful when designing interfaces, because it shows which functions are expected to use management information exchange and which can be carried in signalling. In other words, the document helps determine whether a requirement needs an operational management interface, a signalling solution, or both.

Security and charging are treated as major design concerns

Clause 4 highlights security aspects such as availability, correct billing, fraud protection, confidentiality and privacy. It also notes that network integrity, screening, mapping and protection of subscriber-related data matter when PTNs and SPs interconnect. For charging, the document explains that standard call charging may not fit service-provider use cases such as pre-alerting interaction, non-standard call paths, or real-time billing, so accounting information and event logging may be needed.

The document is about management requirements, not protocol definition

The introduction makes clear that suitable protocols are needed to support the information flows described in the document. Where existing protocols are not available, they may need enhancement or replacement. This is important for implementers: the standard defines the management need and the exchanged information, while the protocol solution is a separate step.

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

SIST-V ETSI/EG 201 965 V1.1.1:2003 defines the main access and network roles used in the analysis.

• Calling line identity (CLI) - the number that uniquely identifies the subscriber line used for a call.
• Circuit-related interface - a signalling connection where the call connection is extended from the PTN to the service provider’s equipment.
• Non-circuit-related interface - a control connection between the PTN operator and the service provider without extending the call connection.
• Public telecommunications network (PTN) - a telecommunications network that provides services to the general public.
• Public telecommunications network operator (PTNO) - the entity responsible for developing, provisioning, maintaining and operating public telecommunications services and networks.
• Service provider access interface (SPAI) - the interface between PTN equipment and the service provider’s equipment that enables access to PTN functionality.
• Service provider access requirement (SPAR) - a requirement for a service provider to access specific functionality of a public telecommunications network.
• Service level Agreement (SLA) - the agreement that defines what information is exchanged between the Service Provider and the PTNO and how it is carried.

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

SIST-V ETSI/EG 201 965 V1.1.1:2003 is used by Service Providers, PTN operators and the teams that design or manage their interconnection. It is especially relevant when those parties need to define the management-plane interface, the associated SLA, and the information exchange needed to support service access.

It applies to work on fixed, cordless and mobile telecommunications networks, and it also speaks to Internet and broadband-related service aspects. In practice, users include network architects, operations teams, service design teams, interconnection engineers, and buyers who need to understand what management functions a solution must support.

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

Clause 2 lists the main documents that this guide builds on or refers to:

• ETSI EG 201 722 - first set of SPAR for enhanced telephony services.
• ETSI EG 201 807 - network operators’ requirements for delivering service provider access.
• ETSI EG 201 899 - modelling of service provider access requirements using an API approach.
• ETSI ES 201 915-1 - Open Service Access, API overview.
• ETSI EG 201 897 - second set of SPAR for fixed and mobile environments.
• ETSI ETR 339 - IN interconnect business requirements.
• ETSI TR 101 664 - IN interconnect security features.
• CEPT/ECTRA Recommendation (98)01 - guidelines on responsibilities for maintaining Network Integrity.
• ETSI TR 101 365 - IN interconnect threat analysis.
• ETSI EG 201 916 - development of standards to support open inter-network interfaces and service provider access.
• ETSI EG 201 988-1 and ETSI EG 201 988-2 - Open Service Access for API requirements versions 1 and 2.

These references matter because they supply the underlying access requirements, management approach, security guidance and API context that the present document analyses.

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

SIST-V ETSI/EG 201 965 V1.1.1:2003 contains three main analysis tables, two reference architectures and a set of definitions that support the management study. Table 1 lists the SPAR requirements and the source clauses where the service-access requirements are described. Table 2 analyses each requirement for management implications, information exchange and per-call handling. Table 3 maps the SPAR items to the management plane or signalling plane.

Clause 4 discusses the background to the subject, including security and charging aspects, and explains why management information exchange is needed for service-provider access. Figure 1 shows a reference architecture for SP-PTN management requirements, and Figure 2 shows an IN/IP-based PTN architecture with management and service/application layers. Annex A gives the bibliography used by the guide.

SLOVENSKI STANDARD
01-november-2003
Storitve in protokoli za napredna omrežja (SPAN) - Dostop ponudnika storitve -
Zahteve upravljanja dostopa ponudnika storitve za odprt omrežni dostop
Services and Protocols for Advanced Networks (SPAN) - Service Provider Access -
Service Provider Access Management Requirements for Open Network Access
Ta slovenski standard je istoveten z: EG 201 965 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;
Service Provider Access Management Requirements
for Open Network Access
2 ETSI EG 201 965 V1.1.1 (2001-11)

Reference
DEG/SPAN-141607
Keywords
OSA
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 965 V1.1.1 (2001-11)
Contents
Intellectual Property Rights.4
Foreword.4
Introduction .4
1 Scope.5
2 References.5
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.7
4 Background to the subject .7
4.1 Security aspects.8
4.2 Charging aspects.8
5 Management requirements for open network access.9
Annex A (informative): Bibliography.20
History .21

ETSI
4 ETSI EG 201 965 V1.1.1 (2001-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
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 present document applies to the management plane interface between the Service Provider role and the Public
Telecommunications Network operator role. The requirements listed in clause 5 are based on service provider access
requirements which contain management aspects selected from the service provider access requirements published in
ETSI deliverables. To fulfil these management requirements, appropriate protocols will be required, based on the
information flows contained in the present document, taking into account network integrity considerations. Where
appropriate protocols are not available, either existing protocols will have to be enhanced or new protocols developed
based on the management information to be exchanged between the Service Provider and the Network Operator.
ETSI
5 ETSI EG 201 965 V1.1.1 (2001-11)
1 Scope
The present document specifies management requirements for open network access.
EG 201 722 [1] lists the first set of Service Provider Access Requirements (SPAR) to support delivery of services over
one or more, but primarily fixed, public telecommunications networks (PTNs).
EG 201 807 [2] addresses network operators' requirements for the delivery of service provider access.
EG 201 897 [5] lists the second set of service provider access requirements (SPAR) to support the delivery of
telecommunication services including, but not limited to, fixed, cordless and mobile networks. Examples of
Telecommunication services include: voice telephony, multimedia and data services. The network requirements also
include support for mobility, Internet and broadband related aspects.
The present document is applicable to the management plane interface between the Service Provider equipment and the
Public Telecommunications Network operator equipment. Each requirement, listed in clause 5, is based on the SPAR
studies as published in the above deliverables. The present document identifies whether each SPAR has a management
implication. To fulfil these management requirements, appropriate protocols will be required, based on the information
flows contained in the present document. Where appropriate protocols are not available, either existing protocols will
have to be enhanced or new protocols developed.
The management requirements covered in the present document can be split into:
• Traffic Related Capabilities (e.g. setting switch triggers, datafill, etc), necessary in order to enable from an
operational perspective one or more of the Service Provider Access Requirements (SPAR).
• Performance Management Capabilities, e.g. monitoring performance of SP/PTN links, link reconfiguration, etc.
• Electronic Bonding/Ordering.
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 EG 201 722: "Intelligent Network (IN); Service provider access requirements; Enhanced
telephony services".
[2] ETSI EG 201 807: "Network Aspects (NA); Intelligent Network (IN); Network operators'
requirements for the delivery of service provider access".
[3] ETSI EG 201 899: "Services and Protocols for Advanced Networks (SPAN); Service Provider
Access; Modelling Service Provider Access Requirements using an API approach".
[4] ETSI ES 201 915-1: "Open Service Access; Application Programming Interface; Part 1:
Overview".
[5] ETSI EG 201 897: "Services and Protocols for Advanced Networks (SPAN); Service Provider
Access; Service Provider Access Requirements in a Fixed and Mobile Environment".
[6] ETSI ETR 339: "Intelligent Network (IN); IN interconnect business requirements".
[7] ETSI TR 101 664: "Intelligent Network (IN); IN interconnect security features".
ETSI
6 ETSI EG 201 965 V1.1.1 (2001-11)
[8] CEPT/ECTRA Recommendation (98)01 of 12 March 1998 on a Set of Guidelines on
Responsibilities for ensuring maintenance of Network Integrity (NI) in an interconnected
environment.
[9] ETSI TR 101 365: "Intelligent Network (IN); IN interconnect threat analysis".
[10] ETSI EG 201 916: "Services and Protocols for Advanced Networks (SPAN); Service Provider
Access; Development of standards to support open inter-network interfaces and service provider
access".
[11] 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".
[12] 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".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
calling line identity: number that uniquely identifies a subscriber line that is used for a call
circuit-related interface: signalling connection between a public telecommunications network operator and a service
provider, with the extension of the call connection from the public telecommunications network to the service provider's
equipment
end user: See "service user" definition.
network-network interface: interface at a network node which is used to interconnect a network node with another
network
NOTE 1: This interface is used for inter-connection of two or more networks.
non-circuit-related interface: control connection between a public telecommunications network operator and a service
provider, without the extension of the call connection from the public telecommunications network to the service
provider's equipment
public telecommunications network: telecommunications network which provides telecommunications services to the
general public
public telecommunications network operator: entity which is responsible for the development, provisioning and
maintenance of telecommunications services to the general public and for operating the corresponding networks
public telecommunications network originating: PTN to which either the originating line is directly connected or in
which an incoming call initiates a service
public telecommunications network terminating: PTN to which either the terminating line is directly connected or in
which the terminating line's user profile is stored
service: that which is offered by an administration or recognized private operating agency (i.e. a public or private
service provider) to its customers in order to satisfy a telecommunication requirement
service provider: entity which provides services to its service subscribers on a contractual basis and who is responsible
for the services offered
NOTE 2: The same organization may act as a public telecommunications network operator and a service provider.
service provider access: access facility that enables a service provider to access specific functionality of a public
telecommunications network
ETSI
7 ETSI EG 201 965 V1.1.1 (2001-11)
service provider access interface: interface between a public telecommunications network and a service provider's
equipment for enabling the service provider to access specific functionality of a public telecommunications network
service provider access requirement: requirement for access by a service provider to specific functionality of a public
telecommunication network
service provider originating: service provider that provides either services relating to the originating line (or to the
originating line's user profile), or services acting on the information coming from the originating or incoming call
service provider terminating: service provider that provides either services relating to the terminating line (or to the
terminating line's user profile), or services acting on the call-related information coming from the terminating party's
line
service subscriber: entity that contracts for services offered by service providers
service user: entity external to the network that uses its services
user-network interface: interface between the terminal equipment and a network termination point at which the access
protocols apply
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
API Application Programming Interface
CAMEL Customized Applications for Mobile Network Enhanced Logic
CLI Calling Line Identity
IMSI International Mobile Subscriber Identity
IN Intelligent Network
INAP Intelligent Network Application Protocol
IP Internet Protocol
NNI Network-Network Interface
PINT PSTN Internet Telephony
PTNO Public Telecommunications Network Operator
SLA Service level Agreement
SP Service Provider
SPA Service Provider Access
SPAI Service Provider Access Interface
SPAR Service Provider Access Requirements
UNI User-Network Interface
4 Background to the subject
Different types of network control (or signalling) interfaces exist within a public telecommunications network (PTN),
between PTNs and for those accessing the PTNs. The Service Provider Access Interface (SPAI) has been specifically
designed to enable Service Providers to deliver services by utilizing the network functionality of one or more PTNs.
The following ETSI documents have been produced:
• EG 201 722 [1] defines the first set of service providers' access requirements leading to enhancements of the
existing network-to-network interfaces (NNI) and user-to-network interfaces (UNI) to have the necessary
functionality to meet the Service Provider Access (SPA) requirements.
• EG 201 807 [2] addresses network operators' requirements for the delivery of service provider access.
• EG 201 899 [3] models service provider requirements using an API approach that leads to API definitions in
ES 201 915-1 [4] and documents EG 201 988-1 [11] and EG 201 988-2 [12] cover open service access API
requirements.
• EG 201 897 [5] defines an enhanced set of service providers' access requirements for mobile, Internet and
broadband networks.
ETSI
8 ETSI EG 201 965 V1.1.1 (2001-11)
The present document describes management plane requirements to enhance the standardized interface referred to, as
the service provider access interface (SPAI) in [1], [2] and [5].
4.1 Security aspects
End users, SPs and PTNOs have a range of business objectives and requirements regarding the provision of
telecommunication services over PTNs. A number of those objectives have been identified [6]. In order to meet them,
security aspects need to be considered in a new environment with a multitude of interconnections and access
configurations for service providers.
From the viewpoint of the end users, the key requirements are:
• availability of the services;
• correct billing;
• fraud protection;
• confidentiality; and
• privacy.
From the viewpoint of the SPs and PTNOs, the key requirements are:
- availability and integrity of the network, services, and maintenance;
- correct charging;
- capability of tracing individual calls;
- protection of subscriber-related data against intruders; and
- elimination of fraudulent use of the equipment of the PTNOs and SPs.
Security violations may have a significant negative business impact for both SPs and NOs, e.g. loss of income,
reputation and market share.
Network integrity is a key issue when any inter-network relationships are established. In the connection of the SPA, a
basic set of facilities may be needed to secure the interfaces between the PTNOs and SPs [7] and [8]. A threat analysis
of IN-based interconnections is presented in TR 101 365 [9], and some guidelines on the relevant security measures are
given in TR 101 664 [7].
Screening and mapping functions are used to control and secure bilateral agreements on the interfaces between the
PTNs. Today, the PTNOs have screening and mapping facilities on some of the inter-connecting NNIs, such as the
ISUP connections. Equivalent facilities and functions need to cover all of the interfaces between the PTNOs and SPs.
Further security aspects associated with mobile, Internet and broad-band networks include transfer of terminal/personal
identity information (e.g. IMSI, Electronic Signature, etc.) between the User Equipment and the service provider, or the
support of secure end-end transmission between the user terminal and the service provider application (e.g. Secure
Socket Layer (SSL) and ciphering technologies).
4.2 Charging aspects
The standard charging mechanisms allow the charging of a successful call, i.e. between the called party's answer and the
release of the call. Some requirements from the service providers imply the usage of the PTNO's network outside this
standard case, and the implementation of a related charging mechanism between the PTNO and the SP is therefore
necessary, in order to cover such a usage. This is true e.g. in the case of the following requirements of the service
providers:
- requesting the PTN to open a backward in-band message path to the calling party immediately upon the arrival
of a confirmation of the call set-up, without returning an "answer" signal;
ETSI
9 ETSI EG 201 965 V1.1.1 (2001-11)
- conveying the indication of an unsuccessful call from the terminating PTN, i.e. either when an indication other
than "ringing" is returned to the calling party, or when a "no reply" situation occurs;
- providing call destination and routing information for controlling the destination and routing of the call;
- interacting with the service user before any service charging begins;
- sending data to and receiving data from the service provider's NTP without an alerting signal, such as "ringing";
- call charging and billing aspects, as seen from the PTNO's perspective, are considered in EG 201 807 [2].
In the case where end user charging is suspended, delayed, altered or in other ways different from standard call charging
mechanisms, the appropriate events have to be created for possible logging e.g. thus providing the necessary data for
appropriate accounting between the SP and PTNO.
For example, demand is emerging in the market place for:
- subscription-based billing for Internet access;
- included minutes in pre-pay subscription for fixed and mobile service; and
- pay-per-use without having a subscription.
All these cases require real-time accounting (hot billing) over a secure data interface.
5 Management requirements for open network access
Service provider access requirements have been compiled into a tabular arrangement in EG 201 916 [10] and these form
the basis for determining Service Provider Access Management Requirements for Open Network Access. Figure 1
illustrates the logical architecture assumed for this study.

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 1: Reference Architecture for SP-PTN management requirements
ETSI
10 ETSI EG 201 965 V1.1.1 (2001-11)
Figure 2 shows a possible reference architecture and interfaces for SP-PTN management, where the PTN is an IN-based
network interworking with an IP-based network.

Intelligent Network IP Network
SMAF
SCEF
Management
IFIF(ff(ffss) )
Layer
SMF M GF
IF(ffs)
Distributed
SA GF IF7
IF6 Service
Logic
Service/Application
SDF
Layer
SPIRITS
SPIRITS IF9
IF10
Proxy
Client
IF8
SPIRITS
Server
SCF
PINT
IF1
Server
PINT
Client
IF3
IF2
SRF
IF4
SSF SSF
SM
IF5
CCF CCF
Call/Bearer
Layer
Legend: Signalling
User Data
Figure 2: Reference Architecture for an IN/IP-based PTN
Figure 2 shows the relationship between elements in the services part of the management layer with the corresponding
elements in the service/application layer. Other elements not shown in this figure comprise the TMN part of the
management layer.
Table 1 lists the SPAR requirements and the sources where more detailed descriptions can be found.
ETSI
11 ETSI EG 201 965 V1.1.1 (2001-11)
Table 1: Service provider access requirements contained in ETSI deliverables [1] to [3]
No. Requirement Reference
A1 Reception of the calling line identity - Application of the CLIR supplementary service [1] 5.2.1, [3] 5.2.2
A2 Presentation of the complete CLI information to the PTN [1] 5.2.2
A3 Addition or substitution of a calling line identity [1] 5.2.3
A4 Provision of CLI information to an SP-initiated call [1] 5.2.4
A5 Relaying of the malicious call identification data of a received call [1] 5.2.5, [3] 5.2.1
A6 Network Location Determination [2] 5.1.1
A7 Geographic Location Determination [2] 5.1.2
A8 Determination of the terminal capabilities of the SP's service user [2] 5.2.1

B1 Return speech path connection from the terminating PTN to the calling party [1] 5.3.1
B2 Routeing of an originating or incoming call from the PTN to the SP [1] 5.3.2
B3 Indication of an originating or incoming call from the PTN to the SP [1] 5.3.3
B4 Routeing of a terminating call from the PTN to the SP [1] 5.3.4
B5 Indication of a terminating call from the PTN to the SP [1] 5.3.5
B6 Reception of a notification of the cause of an unsuccessful call [1] 5.3.6
B7 Provision of information for the destination and routeing of a call [1] 5.3.7
B8 Call drop-back [1] 5.3.8
B9 User interaction without service charging of the end user [1] 5.3.9
B10 Reception of the originally dialled digits by the SP [1] 5.3.10
B11 Reception of the originally dialled digits by the PTN [3] 5.3.1
B12 Disconnection of a call in progress [1] 5.3.11
B13 Connection of a call to an interactive voice response unit in the PTN. [1] 5.3.12
B14 Alternate routeing of calls or the indications of calls to another 'point of presence' of the [1] 5.3.13
SP
B15 Alternate routeing of a call or the indication of a call to another 'point of presence' of the [3] 5.3.2
PTN
B16 Indication of the disconnection of a call [2] 5.4.1
B17 Supervision of a dropped-back call [2] 5.4.5
B18 Join operation of individual legs of a call [2] 5.4.2
B19 Split operation of individual legs of a cal [2] 5.4.3
B20 Multimedia Multiparty call control [2] 5.4.7
B21 User Interaction for Text Delivery [2] 5.4.8
B22 User-Plane resource negotiation and selection [2] 5.4.9

C1 Interrogation of a network termination point for data delivery [1] 5.4.1
C2 Overriding of the 'incoming call barring' supplementary service [1] 5.4.2
C3 Bypassing of the 'call diversion' supplementary service [1] 5.4.3
C4 Message waiting indication [1] 5.4.4
C5 Application contents screening [3] 5.5.1
C6 Modification of the terminal capabilities of the SP's service user [2] 5.2.2
C7 Modification of the Personality Device/ module of the SP's service user [2] 5.2.3
C8 Alteration of the profile of the SP's service subscriber [2] 5.3.1
C9 Delivery of information to the SP's service user prior to alerting [2] 5.4.4

D1 Changes in the charging rate of a call - Dynamic [1] 5.5.1
D2 Charging mechanisms between SP and PTNO - Dynamic [3] 5.5.2
D3 Provision of call charging information in real time [2] 5.6.1
D4 Exchange of charge detail record information in real time [2] 5.6.2

E1 Event traceability requested by the SP [1] 5.6.1
E2 Event traceability requested by the PTN [3] 5.4.1
E3 Traffic control capabilities controlled by the SP [1] 5.6.2
E4 Traffic control capabilities controlled by the PTN [3] 5.4.2
E5 Avoidance of the cyclical routeing of a call [1] 5.6.3, [3] 5.4.3
E6 Avoidance of the cyclical routeing of signalling or user messages [2] 5.4.6

F1 Reporting of network events for measuring the quality of service [2] 5.5.1
F2 Reporting of network events for the purpose of fault diagnostics [2] 5.5.2
F3 Request for event monitoring and subsequent reporting [2] 5.5.3
F4 Electronic ordering of network management functions [2] 5.5.4

ETSI
12 ETSI EG 201 965 V1.1.1 (2001-11)
These requirements were analysed to identify whether they contain a management requirement for the support of
service provider access. The requirements F1-F4 as categorized in EG 201 916 [10] under a management heading were
used as the starting point for the analysis. Each requirement and supporting information flows contained in ETSI
deliverables [1], [2] and [5] were examined to identify whether management information has to be exchanged between
the SP and the PTNO, if so, that a delivery mechanism has to be specified.
It was observed that for each requirement, a Service Level Agreement (SLA) has to be produced giving details on the
information to be exchanged between the SP and the PTNO and what mechanism shall be used for this purpose.
Additionally, the need
...