SIST-TS TS 101 314 V4.1.1:2004

Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Abstract Architecture and Reference Points Definition; Network Architecture and Reference Points

This document incorporates additions and enhancements to TIPHON Release 3 deliverable on Network Architecture and Reference Points to support enhance telephony calls and emergency calling services for Release 4. (TIPHON TS 101 314). Additions for emergency calling services. improved QoS and enhanced security will be addressed.

Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 4. izdaja - Abstraktna arhitektura in definicija referenčnih točk - Arhitektura omrežja in referenčne točke

General Information

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.020 - Telecommunications in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2004
• Due Date: 01-Apr-2004
• Completion Date: 01-Apr-2004
• Ref Project: ETSI TS 101 314 V4.1.1 (2003-09) - Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Abstract Architecture and Reference Points Definition; Network Architecture and Reference Points

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS TS 101 314 V4.1.1:2004
01-april-2004

+DUPRQL]DFLMDWHOHNRPXQLNDFLMLQLQWHUQHWQHJDSURWRNRODSUHNRPUHåLM7,3+21

L]GDMD$EVWUDNWQDDUKLWHNWXUDLQGHILQLFLMDUHIHUHQþQLKWRþN$UKLWHNWXUDRPUHåMD

LQUHIHUHQþQHWRþNH
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)

Release 4; Abstract Architecture and Reference Points Definition; Network Architecture

and Reference Points
Ta slovenski standard je istoveten z: TS 101 314 Version 4.1.1
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
SIST-TS TS 101 314 V4.1.1:2004 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
---------------------- Page: 2 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
ETSI TS 101 314 V4.1.1 (2003-09)
Technical Specification
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 4;
Abstract Architecture and Reference Points Definition;
Network Architecture and Reference Points
---------------------- Page: 3 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
2 ETSI TS 101 314 V4.1.1 (2003-09)
Reference
RTS/TIPHON-02009R4
Keywords
architecture, internet, IP, telephony, VoIP
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 2003.
All rights reserved.
TM TM TM

DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.

TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

ETSI
---------------------- Page: 4 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
3 ETSI TS 101 314 V4.1.1 (2003-09)
Contents

Intellectual Property Rights................................................................................................................................5

Foreword.............................................................................................................................................................5

Introduction ........................................................................................................................................................5

1 Scope........................................................................................................................................................6

2 References................................................................................................................................................6

3 Definitions and abbreviations...................................................................................................................7

3.1 Definitions..........................................................................................................................................................7

3.2 Abbreviations.....................................................................................................................................................9

4 Basic concepts........................................................................................................................................10

4.1 Functional planes..............................................................................................................................................10

4.2 Domains and functional groups........................................................................................................................11

5 Functional decomposition of the IP telephony application plane...........................................................12

5.1 Introduction to the functional layers.................................................................................................................12

5.1.1 The services functional layer ......................................................................................................................13

5.1.2 The service control functional layer ...........................................................................................................14

5.1.3 The call control functional layer.................................................................................................................15

5.1.4 The bearer control functional layer.............................................................................................................16

5.1.5 The media control functional layer .............................................................................................................16

5.2 Definition of reference points...........................................................................................................................17

5.2.1 SC-Service reference points........................................................................................................................18

5.2.2 SC-SC reference points...............................................................................................................................19

5.2.3 CC-SC reference points ..............................................................................................................................19

5.2.4 CC/BC-CC/BC reference points .................................................................................................................19

5.2.5 MC-BC reference points.............................................................................................................................19

5.2.6 MC-MC reference points ............................................................................................................................19

5.2.7 TR-MC reference points .............................................................................................................................20

5.2.8 Call unrelated reference point configurations .............................................................................................20

5.2.8.1 Registration...........................................................................................................................................20

5.2.9 Call-related reference point configurations.................................................................................................20

5.2.9.1 Scenario 0..............................................................................................................................................20

5.2.9.1.1 Users at home ..................................................................................................................................21

5.2.9.1.2 Roaming users.................................................................................................................................21

5.2.9.2 Scenario 1..............................................................................................................................................22

5.2.9.2.1 User at home....................................................................................................................................23

5.2.9.2.2 Roaming user...................................................................................................................................24

5.2.9.3 Scenario 2..............................................................................................................................................24

5.2.9.3.1 User at home....................................................................................................................................25

5.2.9.3.2 Roaming user...................................................................................................................................26

5.2.9.4 Scenario 3..............................................................................................................................................27

6 Functional decomposition of the IP transport plane...............................................................................27

6.1 Introduction to the transport functional layers..................................................................................................28

6.1.1 Transport service functional layer ..............................................................................................................28

6.1.2 Transport control layer................................................................................................................................28

6.1.3 Transport flow layer....................................................................................................................................29

6.2 Definition of reference point ............................................................................................................................29

6.2.1 Transport control - transport service reference points ................................................................................29

6.2.2 Transport control - transport control reference points ................................................................................30

6.2.3 Transport flow - transport control reference points ....................................................................................30

7 Management plane.................................................................................................................................30

7.1 Functional decomposition of the management plane .......................................................................................30

7.1.1 Management functional architecture...........................................................................................................30

ETSI
---------------------- Page: 5 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
4 ETSI TS 101 314 V4.1.1 (2003-09)

7.1.2 Management information architecture........................................................................................................33

7.1.3 Management physical architecture .............................................................................................................33

7.2 Management processes.....................................................................................................................................34

7.2.1 Flow-though process model........................................................................................................................34

7.3 Interconnection between management plane and TIPHON planes ..................................................................35

8 Architecture summary............................................................................................................................36

Annex A (informative): Business roles reference configuration.........................................................37

History ..............................................................................................................................................................39

ETSI
---------------------- Page: 6 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
5 ETSI TS 101 314 V4.1.1 (2003-09)
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 Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol

Harmonization Over Networks (TIPHON).
Introduction

The present document describes the network architecture and the reference configurations that are necessary for the

support of services and service capabilities defined for TIPHON Release 4. The TIPHON Release 4 definition and the

corresponding relationship between the core deliverables is described in TR 101 301 V4.1.1 [1].

The present document builds upon the concepts embodied in TIPHON Release 3 [8]. These concepts which are

applicable to network configurations based on the range of functional and entities within the IP network, as described in

the present document that are necessary to support the four scenarios of TIPHON Release 4.

ETSI
---------------------- Page: 7 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
6 ETSI TS 101 314 V4.1.1 (2003-09)
1 Scope

The present document defines the TIPHON network architecture and the reference configurations that are necessary for:

• the delivery of telephone calls, which originate and terminate in IP networks;

• the delivery of telephone calls which originate in an Internet Protocol (IP) network and are delivered to

Switched Circuit Networks (SCN);

• the delivery of telephone calls which originate in SCNs and are delivered in an IP network; and

• the delivery of telephone calls which originate in SCNs, routed through IP networks and delivered to SCN.

These four scenarios are part of TIPHON Release 4.

The architecture includes provision of information and facilities which are incidental to the delivery of telephone calls

described above. The present document builds upon the concepts embodied in the TIPHON Release 3 network

architecture and reference configurations described in TR 101 877 [8]. The present document is applicable to equipment

fulfilling the roles of the functional groups identified in TS 101 878 [2]; Terminal functional group, network functional

group and Gateway functional group, and also to entities within the IP network that are necessary to support the four

scenarios of TIPHON Release 4.
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.

Referenced documents which are not found to be publicly available in the expected location might be found at

http://docbox.etsi.org/Reference.

[1] ETSI TR 101 301: "Telecommunications and Internet Protocol Harmonization Over Networks

(TIPHON) Release 3; Release Definition; TIPHON Release 3 Definition".

[2] ETSI TS 101 878: "Telecommunications and Internet Protocol Harmonization Over Networks

(TIPHON) Release 3; Service Capability Definition; Service Capabilities for a simple call".

[3] ETSI TS 101 329-2: "Telecommunications and Internet Protocol Harmonization Over Networks

(TIPHON) Release 3; End-to-end Quality of Service in TIPHON Systems; Part 2: Definition of

Speech Quality of Service (QoS) Classes".

[4] ETSI TS 101 871 (all parts): "Digital Enhanced Cordless Telecommunications (DECT);

Application Specific Access Profile (ASAP); DECT Multimedia Access Profile (DMAP); Profile

requirement list and profile specific Implementation Conformance Statement (ICS) proforma".

[5] ETSI TR 101 303: "Telecommunications and Internet Protocol Harmonization Over Networks

(TIPHON) Release 3; Requirements definition study; Introduction to service and network

management".

[6] ETSI TR 101 311: "Telecommunications and Internet Protocol Harmonization Over Networks

(TIPHON) Release 3; Service Independent requirements definition; Transport Plane".

[7] Void.
ETSI
---------------------- Page: 8 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
7 ETSI TS 101 314 V4.1.1 (2003-09)

[8] ETSI TR 101 877: "Telecommunications and Internet Protocol Harmonization Over Networks

(TIPHON); Requirements Definition Study; Scope and Requirements for a Simple call".

[9] Void.

[10] ETSI TS 101 303: "Telecommunications and Internet Protocol Harmonization Over Networks

(TIPHON) Release 4; Service Independent Requirements Definition; Service and Network

Management Framework; Part 1: Overview and Introduction".

[11] ITU-T Recommendation M.3010: "Principles for a Telecommunications management network".

[12] ITU Recommendations M.3200: "TMN management services and telecommunications managed

areas: overview".
[13] ITU Recommendations M.3400: "TMN Management Functions".
[14] GB910: "Telecom Operations Map".

[15] GB921 June 1: "enhanced Telecom Operations Map (eTOM): The Business Process Framework-

for the Information and Communications Services Industry".
3 Definitions and abbreviations
3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

administrative domain: collection of physical or functional entities under the control of a single administration

aggregate bearer: logical association of functional entities in an IP telephony application and transport network which

creates one or more concurrent end to end media flows and which is not limited to the duration of a single call

Aggregate Bearer Admission Control (ABAC) function: functional entity that determines whether or not a flow is to

be admitted as part of an established aggregate bearer

Aggregate Bearer Measurement (ABM) function: function that determines the capacity used and remaining in an

aggregate bearer as a result of measuring the actual media flows after taking into account what flows were requested

application data: media or signalling information content

bearer: logical association of functional entities in an IP telephony application and transport network which creates an

end to end media flow for no longer than the duration of a call

domain: collection of physical or functional entities within an administrative domain which share a consistent set of

policies and common technologies

Domain IDentifier (DID): globally unique identifier of a domain. Domain identifiers may be mapped to the IP

Telephony Administrative Domain (ITAD) Numbers, registered by IANA and used by the TRIP Protocol

end-user: entity using the services of an IP telephony service provider or transport network operator

end-user domain: collection of physical or functional entities under the control of an end-user which share a consistent

set of policies and common technologies
functional entity: entity in a system that performs a specific set of functions
Functional Group (FG): collection of functional entities within a domain.

NOTE: In TIPHON systems functional groups are used to structure the necessary functionality to offer IP

telephony services across domains
ETSI
---------------------- Page: 9 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
8 ETSI TS 101 314 V4.1.1 (2003-09)

gateway functional group: functional group containing the functionality of a network functional group also the

functionality necessary to connect calls to the SCN

NOTE: Gateway functional groups may be classified as originating or terminating based upon their location

within the topology of a specified call.

home network functional group: functional group, which is aware of the service application subscribed to by the

end-user

NOTE: Home network functional groups may be classified as originating or terminating based upon their location

within the topology of a specified call.

intermediate (transit) network functional group: functional group connecting the serving network functional group

to the home network functional group

NOTE: The intermediate network functional grouping is only present when the serving network functional

grouping and the home network functional grouping are not directly connected.

information flow: interaction between a communicating pair of functional entities

interconnection function: functional entity connecting two networks having differing administrative policy such as

Quality of Service (QoS) or addressing policy but employing the same signalling protocol, and transport technology, at

the point of interconnect

interface: shared boundary between two communicating systems, devices or equipment

IP network: packet transport network comprising one or more transport domains each employing the IP protocol

IP telephony: any telephony related service that is supported on a managed IP network

IP telephony service provider: service provider who offers IP telephony services

NOTE: The same business entity may act as both a transport network operator and an IP telephony service

provider.

network functional group: functional group containing the functionality required to establish a call between two

terminals, a gateway and a terminal, or two gateways

NOTE: Network functional groups may be classified as originating or terminating based upon their location

within the topology of a specified call.

packet flow/transport flow: stream of packets of the same type identified by common address and port numbers

NOTE: The stream may contain either signalling information or content description together with media

information.

protocol: set of semantics, syntax and procedures, which govern the exchange of information across an interface

reference point: conceptual point at the conjunction of two communicating functional entities

service domain: collection of physical or functional entities offering IP telephony services under the control of an IP

telephony service provider which share a consistent set of policies and common technologies

serving network functional group: functional group that enables terminal functional groups to connect to an IP

telephony service provide

Switched Circuit Network (SCN): telecommunications network, e.g. Public Switched Telephone Network (PSTN),

Integrated Services Digital Network (ISDN), and General System for Mobile communications (GSM), that uses

circuit-switched technologies for the support of voice calls
NOTE: The SCN may be a public network or a private network.

terminal: endpoint within the user equipment on which signalling and media flows originate and/or terminate

ETSI
---------------------- Page: 10 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
9 ETSI TS 101 314 V4.1.1 (2003-09)

terminal functional group: functional group representing all the IP telephony functionality within an end-user's

terminal

NOTE: Terminal functional groups may be classified as originating or terminating based upon their location

within the topology of a specified call.

ticket: a ticket is obtained through the registration session, when used in a call it provides the terminal/user with a

means to show a valid registration exists

transport domain: collection of transport resources sharing a common set of policies, QoS mechanisms and transport

technologies under the control of a transport network operator

transport function: functional entity representing the collection of transport resources within a transport domain which

are capable of control by a transport resource manager

transport network: collection of transport resources, which provide IP transport functionality

transport network operator: business entity operating a transport network

transport policy entity: functional entity that maintains the policies of a transport domain

Transport Resource Manager (TRM): functional entity that applies a set of policies and mechanisms to a set of

transport resources to ensure that those resources are allocated such that they are sufficient to enable transport flows

with QoS guarantees across the domain of control of the TRM
user equipment: equipment under the control of an end-user
user profile: service specific information about a user of a service application
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABAC Aggregate Bearer Admission Control
ABM Aggregate Bearer Management
BC Bearer Control
CC Call Control
CR Call Routing function
DID Domain IDentifier
DiffServ Differentiated Services
DNS Domain Name Service
DTMF Dual Tone Multi Frequency
FCAPS Fault, Configuration, Accounting, Performance and Security
FG Functional Group
GSM General System for Mobile communication
HREG Home network REGistration function
IANA Internet Assigned Numbers Authority
ICF Interconnect Function
IP Internet Protocol
IPTN IP Telephony Network
IREG Intermediate Network Registration function
ISDN Integrated Service Digital Network
ITAD IP Telephony Administrative Domain
MC Media Control
MD Mediation Device
MPLS Multi-Protocol Label Switching
NE Network Element
NEF Network Element Function
OAM&P Operation Adminstration Maintenance & Provision
OS Operations System
OSF Operations System Function
PSTN Public Switched Telephony Network
QoS Quality of Service
ETSI
---------------------- Page: 11 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
10 ETSI TS 101 314 V4.1.1 (2003-09)
QoSM Quality of Service Management
QoSP Quality of Service Policy
SC Service Control
SCN Switched Circuit Networks
SpoA Service point of Attachment
SREG Service Network REGistration function
TA Transport Accounting function
TOM Telecommunications operations Map
TF Transport Function
TP Transport Policy
TREG Terminal Registration function
TRIP Telephony Routing over IP Protocol
TRM Transport Resource Management
WS Work Station
WSF Work Station Function
4 Basic concepts
4.1 Functional planes

TR 101 877 [8] describes an environment for communications services that encompasses multiple domains of control

and technology.

Figure 1 expands upon [8] by identifying the following functional planes, each containing a high level grouping of

functionality:
• IP telephony application;
• IP transport;
• SCN;
• management.
SCN plane
IP Telephony Application plane
Management
plane
Transport plane (including IP)
Figure 1: Functional planes

The SCN plane contains the functionality relating to the SCN. Part of the SCN plane is a component of the service

abstraction layer as defined in [8], and part of the SCN plane is a component of the transport abstraction layer as

defined in [8]. Architectures for SCNs are defined elsewhere, therefore, details of this functional plane are not

considered further in the present document.

The IP telephony application plane makes use of capabilities provided by the other functional planes and it contains

functions to support telephony. The IP telephony application plane is a component of the service abstraction layer as

defined in [8]. The IP telephony application plane contains functions and has information flows that support the service

capabilities defined in [2].
ETSI
Security
Quality of Service
Network Management
---------------------- Page: 12 ----------------------
SIST-TS TS 101 314 V4.1.1:2004
11 ETSI TS 101 314 V4.1.1 (2003-09)

The transport plane (including IP) contains the functionality relating to the underlying packet transport and services in

general use, e.g. DNS. The IP transport plane is a component of the transport abstraction layer as defined in [8].

The management plane contains the management functionality relating to QoS, security and network management. The

details of this functional plane are considered in [5].
4.2 Domains and functional groups

TS 101 878 [2] defines a number of concepts and terms that are used in the present document.

Domains are a collection of physical entities or functional entities under the control of a single administration which

shares a consistent set of policies and compatible technologies.

TIPHON distinguishes three kinds of domains: end-user domains, service domains and transport domain.

The end-user domain is controlled by the end-user, the service domain is controlled by an IP telephony service provider

and the transport domain is controlled by a transport network operator.

Functional groups are the constructs used in the present document to structure functionality necessary to offer IP

telephony services across domains. The mapping between domains and functional groups is shown in [2].

NOTE: There may not be a on
...