ETSI EG 201 936 V1.1.1 (2002-04)
Services and Protocols for Advanced Networks (SPAN); Interworking; IP Federating Network (IPFN) architecture
Services and Protocols for Advanced Networks (SPAN); Interworking; IP Federating Network (IPFN) architecture
DEG/SPAN-140104
Storitve in protokoli za napredna omrežja (SPAN) - Vzajemno delovanje - Arhitektura združenega omrežja IP (IPFN)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2003
Storitve in protokoli za napredna omrežja (SPAN) - Vzajemno delovanje -
Arhitektura združenega omrežja IP (IPFN)
Services and Protocols for Advanced Networks (SPAN) - Interworking - IP Federating
Network (IPFN) architecture
Ta slovenski standard je istoveten z: EG 201 936 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);
Interworking;
IP Federating Network (IPFN) architecture
2 ETSI EG 201 936 V1.1.1 (2002-04)
Reference
DEG/SPAN-140104
Keywords
interworking, IP, gateway, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33 493654716
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:
editor@etsi.fr
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 2002.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EG 201 936 V1.1.1 (2002-04)
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 .8
4 Background information.9
5 Users requirements.10
5.1 Market requirements.10
5.2 Users requirements.11
6 Operational scenarios .12
6.1 Scenario 1 - Environmental crisis situation.12
6.2 Scenario 2 - Multileg call .14
6.3 Scenario 3 - Corporate application .15
6.4 Scenario 4 - Secured transactions.15
7 Services offered.16
7.1 Voice services .16
7.2 Data services .17
7.3 Mobility services .17
7.4 Priority services.17
7.5 Data management.17
7.6 Security features.18
7.7 Application server services.18
7.8 Translation service .18
7.9 Administration.18
7.10 Presence services.18
7.11 Messaging services.18
7.12 Location based services.18
7.13 Directory services.18
7.14 Compression features .18
7.15 Value added services .19
7.16 Interworking features and capabilities.19
8 Functional model.19
8.1 Mandatory functions.19
8.2 Optional functions .20
8.3 The Intelligent Interworking Plane (IIP) functions .20
8.4 Recommendations .21
9 Levels of interworking .22
9.1 Levels .22
9.2 Recommendations .23
10 User profile structure and modelling for IPFN.23
11 Reference model.26
12 Data flows .28
13 Existing protocols.29
14 Protocol extensions .30
ETSI
4 ETSI EG 201 936 V1.1.1 (2002-04)
15 Dimensioning .30
16 Naming conventions.31
Annex A (informative): Cross user interworking examples .32
Annex B (normative): Recommendations.33
Annex C (informative): Bibliography.35
History .36
ETSI
5 ETSI EG 201 936 V1.1.1 (2002-04)
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 deals with the IP Federating Network (IPFN), an intelligent open interworking platform utilizing
IP technology, allowing interconnection of existing and future networks. The networks interconnected may be fixed or
mobile, 2G or 3G, IP or non-IP, public or private. The IPFN is composed of a set of functional subsystems, enabling
users and applications of these networks to interoperate in fixed and mobile environments, and allowing for provision of
value added services. From the users requirements and scenarios, a functional model is established, an architecture is
defined based on the harmonization and evolution of existing architectures, reference points are identified, so as to list
the existing protocols, identify the need for any protocol extensions and interworking specifications.
Levels of internetworking are defined depending on the Services offered like Security, Quality of Service,
Supplementary Services and Data facilities.
Data may be exchanged, collected or shared between users.
New Services like global addressing, internetwork broadcast, multileg communications, etc, which are not yet available
on the actual network to which the user is connected, may be offered.
Security will be an intrinsic capability of the architecture.
From this a set of recommendations is made in annex B, in order to help identifying the work in the different areas.
ETSI
6 ETSI EG 201 936 V1.1.1 (2002-04)
1 Scope
The present document identifies the services requirements from the users perspective. It then defines the functions
necessary for interoperability required to establish an "IP Federating Network (IPFN)". It identifies the architecture and
the reference points that are sufficient to meet the user's requirements in order to:
- allow Voice, Video and Data or combination of this (Multimedia) interworking between users on
heterogeneous interconnected Networks;
- allow users to roam between networks, i.e. to allow the users to change network point of attachment;
- ensure secured communication when required by the users;
- maintain all or some Services (Supplementary Services, Data facilities, etc.) to the users;
- offer new Services like global name/addressing, internetwork broadcast, multileg communications, etc.
which are not yet available on the actual network to which the user is connected;
- ensure lossless Data exchange between users of different Networks and between Databases, if required;
- provide extended addressing and naming capabilities;
- allow desirable feature interaction between applications that interwork across different networks;
- offer scalability of network interconnection;
- ensure some corresponding levels of Priority, Quality of Service;
- provide necessary network and service management capabilities for all of the above.
The present document aims to provide an analysis of the status of the subject, make recommendations for future work.
The objective is not to redefine existing standards when they can be reused (see note), but in a global analysis to review
standards applicable, their limitations and the rules for implementing interoperability. For example a list of candidate
protocols are SIP for interworking between gateways, Mobile IP, LDAP, IPSec, HTTP, XML.
NOTE: The standards referred to here are developed by ETSI, WWRF, IETF, IPv6 Forum and W3C, details of
which are available in the Bibliography (annex C).
Levels of interworking will be investigated when appropriate in the context of the IPFN.
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] IST 2000-28345 EGERIS: "European Generic Emergency Response Information System".
[2] ETSI TS 101 314: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON); Network architecture and reference configurations; TIPHON Release 2".
[3] ITU-T Recommendation F.16: "Global virtual network service".
ETSI
7 ETSI EG 201 936 V1.1.1 (2002-04)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
IP Federating Network: intelligent, open interworking platform utilizing IP technology, allowing interconnection of
any kind of existing and future networks
user: any entity that actually uses a service. Examples of users in the context of the present document are as follows:
public users;
regulators;
services providers;
emergency authorities;
corporate users;
utilities;
agents/applications.
interworking: ability of equipments to communicate together from different systems and with similar services
interoperability: ability of equipments from different manufacturers (or different systems) to communicate together on
the same infrastructure (same system), or on another while roaming
location based services: specific services offered depending on the user geographical location like mapping services,
points of interest, routing services
portability: ability of an entity or element to be used in different systems or environments
roaming: process of changing the network access point from one location area network or domain to another within
one system or between different systems
agent: application program that performs management operations in response to received management messages or that
sends notifications
client: application program that sends request
gateway: interface, between two (or more) systems that have similar functions but dissimilar implementations, enabling
users on one network to communicate with users on the other
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
redirect server: server that accepts requests, maps the address into zero or more new addresses and returns the requests
with the new addresses to the client
server: application program that accepts requests in order to service those requests and send back responses to those
requests
user agent client: client application that initiates requests on behalf of a user
user agent server: server application that contacts the user when a request is received
user agent: application that contains both a user agent client and user agent server
ETSI
8 ETSI EG 201 936 V1.1.1 (2002-04)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AAA Authentication, Authorisation and Accounting
ABM Asynchronous Balance Mode
API Application Programming Interface
BICC Bearer Independent Call Control
CLIP Calling Line Identification Presentation (supplementary service)
CR Call Reference
DNS Domain Name Server
EP ETSI Project
FG Functional Grouping
GERAN GSM EDGE Radio Access Network
GIS Geographical Information System
GSM Global System for Mobile communications
GVNS Global Virtual Network Service
GW GateWay
HLR Home Location Register
HTTP HyperTextTransferProtocol
IETF Internet Engineering Task Force
IIP Intelligent Interworking Plane
IP Internet Protocol
IPFN IP Federating Network
IPSec IP Security
ISP Internet Service Provider
ISSI Inter Sub System Interface
IST Information Society Technologies
ISTAG IST programme Advisory Group
ISUP ISDN User Part
IT Information Technology
ITEA Information Technology for European Advancement
LAN Local Area Network
LDAP Light Directory Application Protocol
MCU Media Conferencing Unit
MESA Public Safety Partnership Project (Project MESA)
MG Media Gateway
MGC Media Gateway Controller
NAT Network Address Translation
NSB Network Service Broker
OSI Open System Interconnection
PDA Personal Digital Assistant
PIM Presence and Immediate Messaging
PKI Public Key Infrastructure
PMR Private Mobile Radio
PSTN Public Switched Telephone Network
PTN Private Telecommunications Network
QoS Quality of Service
RFC Request For Comment
ROBO Remote Office Branch Office
SCF Service Control Function
SDF Service Data Function
SG Signalling Gateway
SIM Subscriber Identity Module
SIP Session Initiation Protocol
SLA Service Level Agreement
SMS Short Message Service
SOHO SmallOfficeHomeOffice
QoSPE Quality of Service Policy Element
UMTS Universal Mobile Telecommunications System
URL User Requirements Language
ETSI
9 ETSI EG 201 936 V1.1.1 (2002-04)
UTRAN UMTS Terrestrial Radio Access Network
V+D Voice plus Data
VHE Virtual Home Environment
VoIP Voice over IP
VPN Virtual Private Network
WAP WideAreaPaging
WLAN wireless local area network
XML X Modelling Language
4 Background information
It is a fact that wireless and wireline technologies are diverse with their specific adaptations to different markets. There
is an increasing need to interconnect these public and private networks to provide Multimedia, not only a discrete
Voice, Video and Data interworking, but also including global Name/addressing, Mobility, Value Added Services,
Security.
IP based networks, by connecting functional subsystems, can federate those different wireless and wireline technologies
for the users and for applications enabling implementations of new cross technology services and new business models
between networks. These IP Core networks can use a common IP transport network for wireless and wireline
subscribers and are independent from the access networks. Multiple access technologies should include: UTRAN,
GERAN, Hiperlan2, etc. This will include wireline access in addition to the existing radio accesses, i.e. MESA.
Also, this convergence between wireline and wireless technologies should be seen as a key area of alignment, both at
the network and service layers. It is important to derive common mobility requirements that could be adopted for
wireless and fixed IP technologies, based on the study and review of mobility solutions of already evolving mobile
networks (i.e. the Release 4 and beyond) and fixed networks (e.g. WLAN networks).
This is actually needed to identify: mobility, security, multimedia call control and service control requirements before
progressing the work on harmonized networks solutions for IPFN. It is also needed to ensure true seamless roaming and
efficiency between wireless and fixed technologies. This includes the concept of VHE that has been developed in
different fora.
The overall objective of the IPFN is to provide an interworking architecture (with harmonized facilities) for the support
of Voice, Video, Data and any combination resulting applications (i.e. Multimedia). However, it is important to note
here, that interworking with many different types of legacy networks and access systems is very complex. Therefore,
interworking schemes shall be harmonized to as great extent as possible, and where possible avoided.
No assumptions about the physical architecture of the connected networks will be made during the study. Nevertheless,
allocation of resources and functionalities may be required as is feasible in the connected network.
ETSI
10 ETSI EG 201 936 V1.1.1 (2002-04)
AGENCIES
Data IT
Information
Bases
Centres
(GIS…)
GPS
ROBO Servers
Administrations
Corporate
IPFN
IPFN
Operators
Radio
VPN
Intranet Access
GW
Radio
PABX Access
Fixed network
Real Time
Public safety
Residential
events Emergency
SOHO
services, Civil
protection.
CITIZENS
Figure 1: Global configuration
5 Users requirements
5.1 Market requirements
The market requirements taken here are those given by the EC from their global analysis and ongoing projects with
industrials and users in the Information Society Technologies programme (IST), Ten Telecom business program and
Information Technology for European Advancement (ITEA) programme. Some extracts of such reports are listed
below:
IST new organizations and markets (EC Directorate- General):
"Smart organization is knowledge driven, adaptable and internetworked"…"IST enables public agencies to
make the delivery of public services more citizen centric"…
Referring to the IST Information Society Technologies programme (2000 workprogram-/2000/350):
"the emphasis is on citizen-centred approach with significant support for standardization, interoperability and
market stimulation"…"disseminate information"…"users will be able to access data with ubiquity"…
(Intelligent environment management).
"Effective collaboration requires standardization, concerning how the data is collected and stored, and
interoperability in the solutions applied". (Health services).
Draft synopsis of 2001 program ISTAG key enabling technologies:
"To develop middleware, distributed systems, multi-layered architectures and agent based systems to enable
interoperability, interworking, openness and integration of applications and services across platforms"…"To
emphasize trust and security "…
Trans European Telecommunications Networks (2000/C299) in its business plans and market validations quotes the
need to "help improving the overall accessibility to the Services and to ensure that customers of equivalent services
from different providers can communicate and work together transparently"…
ETSI
11 ETSI EG 201 936 V1.1.1 (2002-04)
Information Technology for European Advancement technology roadmap on Software Intensive Systems
(Ref 29 9 2000) reports "we are confronted with a conglomerate of networks which, from the perspective of users,
should work seamlessly together"…And in 2001 IST work program "develop middleware, distributed systems,
multi-layered architectures and agent based systems to enable interoperability, interworking, openness and integration
of applications and services across platforms"…
The EC has also issued a draft mandate on a standard interface between PTN operators and emergency services support
centre for the automatic localization of the distressed caller.
Several European projects are launched with new projects like EGERIS [1] involving the IPFN, VESPER,
WINEGLASS, and LOCUS, etc.
Going further (DG INFO/E4) one can consider an Open Interworking Platform which is an independent middleware
for a wide range of terminals and applications, enabling services, user to user, independently of the underlying network.
Such an ultimate architecture can lead to new business models with 'Network Service Brokers' (NSB) ensuring a unified
security platform, control mechanisms, location mechanisms, etc.
ASP
Platform for Applications and Resources Trading
IPFN
NSB1 NSB2 NSB3
Network1
Operator
Network3
Network2
UserC
UserA
UserD
Network4
UserB
Figure 2: Possible future business model
5.2 Users requirements
Due to the multiple types of networks and protocols available today, there is a need to allow Voice and Data
interworking between users, applications on different networks public and private, fixed and mobile. Roaming may also
be possible in case of same standard based networks, multimode and multi-frequency terminals, etc.
Interworking requires being able to eventually control the information exchanged, its access according to different
policies and procedures, to be able to collect them from different data bases on different networks, to be able to handle
different formats.
Interworking requires offering the user the Security and same/subset/similar Services including Priority, at least the user
shall be made aware of a degradation of it.
Users requirements are being set up in the EGERIS project [1].
ETSI
12 ETSI EG 201 936 V1.1.1 (2002-04)
6 Operational scenarios
The scenarios chosen shall reflect user cases of interworking, including a mix of different types like public and private,
public and corporate users.
6.1 Scenario 1 - Environmental crisis situation
In this scenario a major environment crisis is detected on an industrial site, citizens have to be warned locally,
emergency services have to intervene on site, coordination is ensured by the local or regional administration,
environmental agencies provide information, etc.
The scenario corresponds to the interworking of different types of Users for Voice and Data Information, as represented
on figure 3 in a scenario:
- citizens using public networks, fixed or mobile like PSTN, GSM, UMTS;
- operators and ISPs of the fixed or mobile public or/and private networks;
- emergency Services, civil protection using fixed and mobile networks and their Information Centres;
- administrations taking decisions in crisis situations from the available Information;
- policy makers defining policies;
- IT Agencies (Like Environment, etc.) using different communications means and Information Centres
(IT users);
- corporate users;
- tiers for example for certificates in secured communications.
These users exchange Voice and Data (forms, images, video, etc.) information between themselves, according to
different policies, formats, languages, etc, and according to different Procedures related to the location, region, country.
Administration
Policy
Alarms
Citizens
IP network Warnings
IT Agency Workflows
Data bases
Q/A
Directory
Tiers
Informations
Event control
Corporate Certificates
Servers
Policy, Procedures
Alarms
Q/A Data
Statistics
QoS Policy makers
Configuration
Emergency
Operators
services
ISP
Q/A: Question/Answer.
Figure 3: Users involved in scenario 1
ETSI
13 ETSI EG 201 936 V1.1.1 (2002-04)
Figure 4 represents the different functional sub-systems involved for such interworking, which can be optional and
which can be split in different planes:
• heterogeneous terminals plane with the users and applications;
• heterogeneous access and core networks plane;
• Intelligent Interworking Plane (IIP) with, for example, the following functions:
- call control function for GW's interworking;
- multi legs set-up functions;
- security functions;
- directory functions;
- DNS functions;
- location functions;
- translation/transformation/intermediation functions;
- value added services like broadcast.
• IP backbone with a 'bit pipe' transport and routing main functions, public or private;
• application servers plane with Web servers, GIS, etc.
The IPFN is the Interworking plane corresponding to an Open Interworking Platform. The IPFN is composed of an IP
core network with its Inter Sub System Interface (ISSI) to the Intelligent Interworking Plane (IIP).
Some of these functional sub-systems are optional, they can also be merged between themselves, they have been split
here only for the purpose of the scenario.
Heterogeneity of information format, type, etc. of the associated policies and procedures, of the data rates, priorities, of
the types of Terminals, of the Services offered, etc. is dealt partially or totally by the interworking 'middleware'.
IT systems
Web
DB
Servers
Applications
GIS
IP core
IP Core Network
ISSI
DNS
SIP
MCU
Intermediation
Sec
Application
Transformation Location
GWs
server
M eta directory
Core networks
Access networks
Users applications
Terminals
Figure 4: IPFN plane
ETSI
14 ETSI EG 201 936 V1.1.1 (2002-04)
6.2 Scenario 2 - Multileg call
This scenario presents a possible example of multileg call application involving voice communication, catalogue
consultation, and secured payment. In this scenario a user wants to purchase an airline ticket in a foreign country, being
away from his home network, this may involve different operations like:
• consultation, remotely via his mobile of his corporate agenda;
• consultation via his mobile of the airline timetable;
• simultaneous contact with vendor to get information while checking timetable;
• purchase of ticket with secured payment;
• update agenda;
• call home.
SIM
USUSEERR
Air line
Voice anddata
Data
Time table
Voice
consultation
VENDOR
IPFN
Data
Ticket
VPVPNN
Voice
Agenda
Transaction
Secured
CORPORATE
HOME
BANK
Figure 5: Multileg call scenario
ETSI
15 ETSI EG 201 936 V1.1.1 (2002-04)
6.3 Scenario 3 - Corporate application
This scenario is a possible example of a corporate application.
This is the case of a Corporate extending its offices with a new site, following a merger. Each site has its own wireless
and fixed communications systems and addressing. To avoid major changes in the extensions of the corporate site, the
IPFN may interconnect the networks to provide the functions in order to allow communication between sites. The same
applies to a ROBO connected or added.
ROBO
IPFN
Servers
IIP
Users 2
Network B
Corporate
VPN
NetworkA
IP backbone
Users 1
DNE IPFN
Corporate
Directory Enabled
Network
Figure 6: Corporate scenario
Employees on site B are connected now through the IP backbone/IIP to corporate network A. Interworking is setup
between sites.
The IIP functions of the IPFN provide services to the corporate network VPN service under a Service Level Agreement
(SLA) with the VPN providers. These services may include Security negotiation, the application of an encryption
mechanism, transcoding between schemes used, performance management, QoS negotiation, name/address translation,
user registration and collecting information for charging purposes. These services may be distributed or centralized, for
example the functionalities of the IPFN may be owned by a variety of organizations and maintained in dispersed
discrete locations.
6.4 Scenario 4 - Secured transactions
This scenario involves a heterogeneity of terminals with mobility on a mix of networks and operators. The users
involved in the scenario involve public customers, retailers, banks, tiers, trusted parties, etc. Different currencies, public
keys handling, policies, certificates mechanisms, etc. make this scenario complex as shown on the figure.
The IPFN allows to keep heterogeneity while, by adding new functions (IIP) to the core IP network, it allows mobility
and security.
One example is certificate handling where different protocols are available, a server on the IPFN can make the protocol
conversion at the edge of the core backbone. Other examples concern currencies conversion, format handling, etc.
ETSI
16 ETSI EG 201 936 V1.1.1 (2002-04)
MoMobibilliittyy
SISIMM
PDPDAA
PSPSTTNN
2G 3G 3G
TTeermrmiinnalal 2G
MMerercchhaanntt
RARANN
CoCorree nneetwtwoorrkk
ININTTEERRNNEETT
CuCussttoommeerrss
? ?
PuPubblliicc KeKeyy BBaank1nk1
??
InInffrrasastrtruucctutureress
?
CeCerrttiiffiiccaatteess
serservveerrss
OpOpereraattoorrss
SeSerrvviiccee pprroovividederrss
AAuuththeenntiticcaattiioonn
TTrruusstteedd ppararttiieses
serservveerrss
TiTieerrss
PoPolliicycy sseerrvveerrss
BBaank2nk2 CCuurrrrenencciieses
Figure 7: Secured transactions
According to events secured transactions are setup, the workflow is federated as well as the data exchange. Policy,
authentication, certificates servers may be one or several servers connected to different types of networks as well as
PKI.
7 Services offered
Interworking does not necessarily mean that a user is offered all applications and network services which is used to
have on his home network. Some similar or equivalent services may be offered as a subset, in some cases new services
can be added. Different levels of services can be defined such as:
Level 1: this includes the minimum mandatory interworking functions needed for Voice and Data
communications; for example point to point voice communications, fax, SMS.
Level 2: a chosen limited set of Teleservices like multiparty voice and multimedia calls, a chosen
set of Supplementary Services and Data facilities would be available on both ends.
Level 3: new services are offered to the user by the introduction of the IPFN. The value-added
features can be for example: security, multi-leg, access control, mobility, and multicast.
Another point is the security level to the user in his home network that may have to be guaranteed for interworking.
7.1 Voice services
Voice services can be split into classical voice services and interactive multimedia voice services:
teleservices:
- individual call,
- multi leg calls,
supplementary services (e.g. call forwarding, etc.).
ETSI
17 ETSI EG 201 936 V1.1.1 (2002-04)
7.2 Data services
Data services and facilities shall be classified and the dimensioning of the information checked for data rate, priority,
QoS and response time:
Classification can be done as:
- time dependant bi-directional services: Video conferencing, VoIP;
- real time short data services: Location services, Telemetry, Biodynamic;
- database access: online forms, data base access to video, image and multimedia;
- image transfer: image, video, video streaming, graphics, maps, webcast, video broadcast;
- office application: emails with attachments, web browsing, mobile computing;
- file transfer: file, content push.
7.3 Mobility services
The mobility services are set up in order to know on which access network the user is located and in order to track his
mobility from one network to another they comprise:
- user registration;
- user location;
- user profile management;
- user policy management (service subscription);
- policy negotiation and the reservation of capabilities offered by the access network;
- user Authentication, Authorization and Accounting (AAA).
There may also be the possibility to control the interoperability and services offered.
7.4 Priority services
Different levels of priority may be defined according to the priority level users need to have. These priority levels may
be assigned in the user profile in their home network.
This includes the automatic allocation of a priority level for emergency services, and the provision of essential data for
the automatic location of the distressed caller. This feature is supported by the allocation of a priority indication to
session control signalling.
7.5 Data management
Some data may need to be stored on the IPFN as for example:
- network location information of a user roaming;
- user information of a user roaming, etc. (Naming/addressing, additional Security features, Priority, QoS
policy, etc.);
- main characteristics of a connected network (Network Virtual image) like:
maximum data rate, types of coding, types of compression, services offered, etc.
Some of this information may be obtained by interrogating the interconnected network databases.
ETSI
18 ETSI EG 201 936 V1.1.1 (2002-04)
7.6 Security features
Security services should have different levels corresponding to different services offered as:
- authentication;
- confidentiality (end to end);
- integrity and authenticity;
- availability and non repudiation;
- digital signature and certificates;
- key management, secret and public.
NAT, firewalls traversal, VPNs, IPSec and lawful interception are to be considered.
7.7 Application server services
These services allow from a request of a user/application on one network to collect and assemble the information on the
different network databases, e.g. using LDAP services.
7.8 Translation service
Data may be translated/reformatted before being sent to the user. It is a data interoperability function in order to have
the possibility to have XML internal standard format. This could include voice services translation.
7.9 Administration
Administration of the IPFN covers network management.
7.10 Presence services
Presence based multimodal communications should be considered by the IPFN.
7.11 Messaging services
(Instant) messaging should be considered by the IPFN.
7.12 Location based services
The IPFN should consider access to location information by emergency services and services offered to the user
depending on his geographical location.
7.13 Directory services
The IPFN should support various addressing plans related to unit, multileg, networks configurations.
7.14 Compression features
The IPFN should support compression of IP datagram headers, signalling messages and payload data, as appropriate.
ETSI
VPN
19 ETSI EG 201 936 V1.1.1 (2002-04)
7.15 Value added services
These services include optional services that are offered to the user to handle: the invocation of a service according to
an event, the management of information according to events or procedures.
7.16 Interworking features and capabilities
These capabilities include optional features that are offered to the user to handle: the heterogeneity of terminals, the
heterogeneity of data formats, etc. The user may not be aware of these capabilities.
8 Functional model
The functional model can be split into mandatory and optional functions. Some of these functions can then be classified
into intelligent functions in the IIP.
Figure 8 represents an example of such decomposition with the core IP backbone (and eventually VPN) with a function
of (secured) 'bit pipe', in a multidomain environment, with mandatory and optional edge functions, and the optional
Intelligent IP functions. SIP is assumed for interworking between users A, B, C.
User B
User A
User C
Network B
Network A
Location
Network C
Mobility Features
GW_nwkC
MCU
Media and signalling services
Conferencing services
SIP Proxy Redirect
Server
GW_nwkA GW_nwkB
IIP
IP core backbone
Management
DNS and Directory
SIP Registration
Security
services
services
Features
Server
SIP interworking solution
Optional Mandatory
Figure 8: IPFN functional architecture example
8.1 Mandatory functions
The following functions are mandatory:
• GateWay (GW) functions with media and call control VoIP interworking functions. The Signalling and Call
Control Gateways may include candidate protocols for interworking, such as: SIP (The Proxy Redirect server,
Registration server functions are assumed SIP (Session Initiation Protocol) based sub-systems), SIP-T
(Tunnelling ISUP), BICC, H.225.0, Q.931. The Meta protocol developed in project TIPHON can be used, it
avoids making any assumption on the protocol used and may then be mapped to the real protocol in use between
gateways. In case of H.248 (IETF Megaco) a Media Gateway Control (MGC) function is needed that controls
Media Gateways (MG). This MGC can be common to various Media Gateways.
• Location register function offering mobility management capabilities;
ETSI
20 ETSI EG 201 936 V1.1.1 (2002-04)
• security function offering security capabilities for example the security function is required for the support of
Reliable Identification, non-repudiation, etc;
• management function: minimal support;
• naming/addressing function offering DNS and directory services.
8.2 Optional functions
The following functions are optional:
• security function offering security features for example the security function may be required for the support of a
Global VPN service (GVNS [3]);
• Media Conferencing Unit (MCU) function offering multi-leg services;
• management function: e.g. QoS, end to end services;
• intelligent IP functions.
8.3 The Intelligent Interworking Plane (IIP) functions
The Intelligent Interworking functions (IIP) include the optional functions described as follows:
The mediation function: is an intelligent layer which manages the heterogeneity of terminals with mobile terminals,
fixed PCs, PDAs, low capability terminals (e.g. Set Top Box/TV), LAN or remote access to network based terminal
profiles. This does not define th
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...