ETSI EG 201 992 V1.1.1 (2001-12)

Services and Protocols for Advanced Networks (SPAN); Intelligent Networks (IN); Architectures and signalling requirements for IN-based networks interworking with IP-based networks

DEG/SPAN-140304

Storitve in protokoli za napredna omrežja (SPAN) - Inteligentna omrežja (IN) - Arhitekturne in signalizacijske zahteve za vzajemno delovanje omrežij IN z omrežji IP

General Information

• Status: Published
• Publication Date: 17-Dec-2001
• Technical Committee: SPAN 14 - SPAN Overall Network and System Architecture (ONSA)
• Current Stage: 12 - Completion
• Due Date: 30-Nov-2001
• Completion Date: 18-Dec-2001
• Ref Project: SIST-V ETSI/EG 201 992 V1.1.1:2003 - Services and Protocols for Advanced Networks (SPAN) - Intelligent Networks (IN) - Architectures and signalling requirements for IN-based networks interworking with IP-based networks

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-V ETSI/EG 201 992 V1.1.1:2003
01-november-2003
Storitve in protokoli za napredna omrežja (SPAN) - Inteligentna omrežja (IN) -
Arhitekturne in signalizacijske zahteve za vzajemno delovanje omrežij IN z omrežji
IP
Services and Protocols for Advanced Networks (SPAN) - Intelligent Networks (IN) -
Architectures and signalling requirements for IN-based networks interworking with IP-
based networks
Ta slovenski standard je istoveten z: EG 201 992 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST-V ETSI/EG 201 992 V1.1.1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

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

---------------------- Page: 2 ----------------------

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

ETSI EG 201 992 V1.1.1 (2001-12)
ETSI Guide


Services and Protocols for Advanced Networks (SPAN);
Intelligent Networks (IN);
Architectures and signalling requirements for
IN-based networks interworking with
IP-based networks

---------------------- Page: 3 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 2 ETSI EG 201 992 V1.1.1 (2001-12)



Reference
DEG/SPAN-140304
Keywords
IN, IP, protocol, signalling
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

---------------------- Page: 4 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 3 ETSI EG 201 992 V1.1.1 (2001-12)
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 Services.11
4.1 Benchmark services.11
4.2 IN-Internet service examples.11
5 Functional architecture.13
5.1 Introduction.13
5.2 Functional model.14
5.3 New functional entity requirements .15
5.3.1 PINT server.15
5.3.2 Service Application Gateway Function (SA-GF) .16
5.3.3 Session Manager (SM).16
5.3.4 SPIRITS client.16
5.3.5 SPIRITS proxy.17
5.3.6 SPIRITS server.17
5.4 Extensions to existing functional entity requirements.17
5.4.1 Specialized Resource Function (SRF) .17
5.4.2 Service Control Function (SCF) .17
5.4.3 Service Data Function (SDF).17
5.4.4 Service Switching Function (SSF).18
5.4.5 Call Control Function (CCF) .18
5.5 Functional interfaces.20
5.5.1 IF1: SCF to PINT server interface .20
5.5.2 IF2: SRF to PINT server interface .20
5.5.3 IF3: SCF to SRF interface .21
5.5.4 IF4: SCF to SSF interface.21
5.5.5 IF5: CCF to CCF interface.21
5.5.6 IF6: SCF to SA-GF interface .21
5.5.7 IF7: SA-GF to GF for distributed service logic platforms interface .21
5.5.8 IF8: SCF to SPIRITS client interface .21
5.5.9 IF9: SPIRITS client to SPIRITS proxy interface.21
5.5.10 IF10: SPIRITS proxy to SPIRITS server interface .21
5.6 Lower layer protocol gateway and mapping functions.22
5.6.1 Introduction.22
5.6.2 Lower layer protocol functional model.22
5.6.3 Service Control Gateway Function (SC-GF) .23
5.6.4 Signalling Gateway Function (S-GF) .23
5.6.5 Dial Access Gateway Function (DA-GF) .24
5.6.6 Media Manager Gateway Function (MM-GF).24
5.7 Lower layer functional interfaces.24
5.7.1 IFa: SCF to SC-GF interface.25
5.7.2 IFb: SRF to SC-GF interface .25
5.7.3 IFc: CCF to S-GF interface.25
5.7.4 IFd: SDF to DA-GF interface .25
5.7.5 IFe: CCF to MM-GF interface.25
5.7.6 IFf: CCF to DA-GF interface.25
5.7.7 IFh: SRF to MM-GF interface .25
ETSI

---------------------- Page: 5 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 4 ETSI EG 201 992 V1.1.1 (2001-12)
5.7.8 IFh: SC-GF to PINT server interface.26
5.7.9 IFi: SC-GF to SSF interface.26
5.7.10 IFj: S-GF to CCF-CM interface.26
5.7.11 IFk: MM-GF to CCF-RM interface .26
6 IN/IP Implementation Scenarios.26
6.1 IN/IP interworking for IN CS-3 to support SIP systems .26
6.1.1 The SIP architecture.27
6.1.2 SIP Call call models.27
6.1.3 Functional model.27
6.1.4 Requirements for IN-interaction with SIP-based systems .29
6.1.5 SIP assumptions architecture and implementation issues .30
6.1.5.1 IN-SIP interaction.30
6.1.5.2 Basic concept of the proposal.31
6.1.5.3 Assumptions.31
6.2 IN/IP interworking for IN CS-3 to support H.323 systems .32
6.2.1 Functional model supporting the H.323 GRC model.32
6.2.2 Void.35
6.2.3 Requirements for IN CS-3 interaction with H.323 system .35
6.2.4 H.323/SIP differences and implementation issues.36
6.2.4.1 Call control.36
6.2.4.2 Architecture and assumptions for IN CS-3 interaction with H.323 call control.37
6.3 IN/IP interworking for IN CS-3 to support PINT based services.37
6.4 IN/IP interworking for IN CS-3 to support SPIRITS based implementation of services .40
6.5 IN/IP interworking for IN CS-3 to support distributed service logic servers via an API .43
6.6 IN/IP interworking to support IN CS-3 signalling transport functionality .46
6.7 ISDN/IP interworking to support signalling transport functionality .47
7 Signalling Requirements.48
7.1 Introduction.48
7.2 IN based service for dial-up internet access .48
7.3 Information flow for Click-To-Dial (CTD) service.50
7.4 Information flow for Click-To-Fax (CTF) service .51
7.5 Information flow for Internet Call Waiting (ICW) service.52
7.6 Example information flows of in-ip telephony interworking .54
7.6.1 Information flow for H.323 terminal originated number translation service .54
7.6.2 Information flow for GW Initiated number translated service.55
7.7 IN interaction with SIP call control message flows.55
7.7.1 Proposed registration process .55
7.7.2 Originating call with Core INAP interaction .56
7.7.3 Terminating call with Core INAP interaction.57
7.8 IN/H.323 interaction Message Flows .57
7.8.1 Registration.57
7.8.2 Originating call requiring Core INAP interaction.57
7.8.3 Terminating call requiring Core INAP interaction .60
8 Security aspects.61
8.1 Introduction.61
8.2 Requirements on the IN/IP interface .61
8.3 Requirements on the IN domain.61
8.3.1 Core INAP SCF to SSF interface.61
8.4 Requirements on the IP Domain.62
Annex A (informative): Bibliography.63
History .64

ETSI

---------------------- Page: 6 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 5 ETSI EG 201 992 V1.1.1 (2001-12)
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 is closely aligned with ITU-T Recommendation Q.1244 [19], such that clauses 5 and 7 are
similar in technical content with the related parts of the ITU-T Recommendation. Clause 6 whilst aligned with ITU-T
Recommendation Q.1244 [19] provides more detail in the figures and tables describing the relationship of the reference
scenarios with the lower layer transport protocols. The intention of the present document is to define a set of
enhancements for IN CS-3 for interworking with IP-networks, which comprises IN CS-4 in the ITU-T. In ETSI these
enhancements will be considered as a revision of ETSI Core INAP.
ETSI

---------------------- Page: 7 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 6 ETSI EG 201 992 V1.1.1 (2001-12)
1 Scope
The present document describes the standardization of functions to allow interworking between Intelligent Networks
and IP-networks for IN CS-3. These functions include:
- Signalling Requirements for interworking between functional entities in the IN and IP-networks;
- Signalling Requirements to support benchmark capabilities between functional entities in the IN and
IP-networks;
- Architecture supporting the transport of higher layer session multimedia protocols between IP-network and the
Circuit Switched Network;
- Interworking and addressing of service control functions and service control gateway functionality across IN and
IP-network boundaries;
- Study of the security aspects.
The present document only considers scenarios for interworking IN CS-3 capabilities and IP-based networks. Service
and network integration is outside the scope of the present document.
The management functional entity requirements and interfaces are outside the scope of the present document.
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] Void.
[2] Void.
[3] Void.
[4] ITU-T Recommendation Q.1224: "Distributed functional plane for intelligent network Capability
Set 2".
[5] ITU-T Recommendation Q.1231: "Introduction to Intelligent Network Capability Set 3".
[6] ITU-T Recommendation H.225.0: "Call signalling protocols and media stream packetization for
packet-based multimedia communication systems".
[7] ITU-T Recommendation H.245: "Control protocol for multimedia communication".
[8] ITU-T Recommendation H.246: "Interworking of H-Series multimedia terminals with H-Series
multimedia terminals and voice/voiceband terminals on GSTN and ISDN".
[9] ITU-T Recommendation H.248: "Gateway control protocol".
[10] ITU-T Recommendation H.323: "Packet-based multimedia communications systems".
[11] IETF RFC 2543 (1999): "SIP: Session Initiation Protocol".
[12] IETF RFC 2458 (1998): "Toward the PSTN/Internet Inter-Networking - Pre-PINT
Implementations".
ETSI

---------------------- Page: 8 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 7 ETSI EG 201 992 V1.1.1 (2001-12)
[13] IETF RFC 2848 (2000): "The Pint Service Protocol: Extensions to SIP and SDP for IP Access to
Telephone Call Services".
[14] IETF RFC 3136 (2001): "The SPIRITS Architecture".
[15] ETSI TR 123 821: "Technical Specification Group Services and System Aspects; Architecture
Principles for Release 2000".
[16] IETF RFC 791 (1981): "Internet Protocol".
[17] IETF RFC 3015 (2000): "Megaco Protocol Version 1.0".
[18] ETSI ES 201 915 (V1.1.1) Parts 1 to 12: "Open Service Access; Application Programming
Interface".
[19] ITU-T Recommendation Q.1244: "Distributed functional plane for Intelligent Network Capability
Set 4".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
call: point-to-point multimedia communication between two H.323 endpoints
NOTE: The call begins with the call set-up procedure and ends with the call termination procedure. The call
consists of the collection of reliable and unreliable channels between the endpoints. A call may be directly
between two endpoints, or may include other H.323 entities such as a Gatekeeper or MG. In case of
interworking with some CSN endpoints via a Gateway, all the channels terminate at the Gateway where
they are converted to the appropriate representation for the CSN end system. Typically, a call is between
two users for the purpose of communication, but may include signalling-only calls. An endpoint may be
capable of supporting multiple simultaneous calls.
call signalling channel: reliable channel used to convey the call set-up and teardown messages (see ITU-T
Recommendation H.225.0) between two H.323 entities
composite gateway: logical entity composed of a single MGC and one or more MGs that may be reside on different
machines
NOTE: Together, they preserve the behaviour of a gateway as defined in ITU-T Recommendations H.323 [10]
and H.246 [8].
GateKeeper (GK): H.323 entity on the network that provides address translation and controls access to the network for
H.323 terminals, Gateways and MCUs
NOTE: The Gatekeeper may also provide other services to the terminals, Gateways and MCUs such as bandwidth
management and locating Gateways.
GateWay (GW): an H.323 GateWay (GW) is an endpoint on the network which provides for real-time, two-way
communications between H.323 Terminals on the packet based network and other ITU Terminals on a switched circuit
network, or to another H.323 Gateway
NOTE: Other ITU-T terminals include those complying with Recommendations H.310 (H.320 on B-ISDN),
H.320 (ISDN), H.321 (ATM), H.322 (GQOS-LAN), H.324 (GSTN), H.324M (Mobile), and V.70
(DSVD).
ETSI

---------------------- Page: 9 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 8 ETSI EG 201 992 V1.1.1 (2001-12)
H.248: describes a control model and protocol for an MGC to control an MG
NOTE: An MGC-MG association reserves the behaviour of a H.323 gateway. H.248 has been developed in
ITU-T SG16, in co-operation with IETF MEGACO, with the intention of providing a single, international
standard for Media Gateway Control.
H.323 Entity: any H.323 component, including terminals, Gateways, Gatekeepers, MGCs and MGs
H.323 Service Control Protocol: specifies protocol for multimedia communications over packet networks to be used
between gatekeepers
NOTE: This is work under study in SG16, intended to enhance service related information transfer to and from
the gatekeeper, which is currently limited to RAS. This work is expected to be strongly influenced by the
IN-IPT interworking model and the joint work of SG16/SG11 in general.
IP-address: 32-bit address defined by the Internet Protocol in IETF RFC 791
NOTE: It is usually represented in dotted decimal notation.
IP-network: general term denoting networks based on the Internet Protocol (IP) suite
NOTE: A network which uses IP as the Layer 3 protocol.
JAVA: software platform trademark of Sun Microsystems
Media Gateway (MG): converts media provided in one type of network to the format required in another type of
network
NOTE: For example, an MG could terminate bearer channels from a switched circuit network (i.e. DSOs) and
media streams from a packet network (e.g., RTP streams in an IP-network). This gateway may be capable
of processing audio, video and T.120 alone or in any combination, and will be capable of full duplex
media translations. The MG may also play audio/video messages and perform other IVR functions, or
may perform media conferencing.
Media Gateway Controller (MGC): controls the parts of the call state that pertain to connection control for media
channels in a MG
proxy, proxy server: intermediary program that acts as both a server and a client for the purpose of making requests on
behalf of other clients
NOTE: Requests are serviced internally or by passing them on, possibly after translation, to other servers. A
proxy interprets, and, if necessary, rewrites a request message before forwarding it, see [11]. This
functional element is functionally similar to the user agent server. In essence the proxy server is
comprised of both a SIP client and a SIP server.
RAS (Reservation, Admission and Status): the RAS signalling function uses H.225.0 messages to perform
registration, admissions, bandwidth changes, status, and disengage procedures between endpoints and Gatekeepers
NOTE: For details refer to ITU-T Recommendations H.323 [10] and H.225.0 [6].
RAS channel: reliable channel used to convey the registration, admissions, bandwidth change, and status messages
(following ITU-T Recommendation H.225.0) between two H.323 entities
redirect server: server that accepts a SIP request, maps the address into zero or more new addresses and returns these
addresses to the client
NOTE: Unlike a proxy server, it does not initiate its own SIP request. Unlike a user agent server, it does not
accept calls, see [11]. The redirect server is not responsible for call control but will simply respond to SIP
requests with a new address.
registrar server: simply responds to registrar requests
NOTE: Typically this is co-located with either the proxy or the redirect server, and may be adapted to perform
location-based services, see [11].
server: application program that accepts requests in order to service requests and sends back responses to those requests
ETSI

---------------------- Page: 10 ----------------------

SIST-V ETSI/EG 201 992 V1.1.1:2003
 9 ETSI EG 201 992 V1.1.1 (2001-12)
NOTE: Servers are either proxy, redirect or user agent servers or registrars [11].
Session Initiation Protocol (SIP): text-based protocol, similar to HTTP and SMTP, for initiating interactive
communication sessions between users
NOTE: Such sessions include voice, vi
...