IP networking & MEDIACOM-2004 ITU Workshop « IP networks towards NGN » Geneva, 24-27 April 2001 ( E dition 2 du 18 04 01) . Gaël Fromentoux Renaud Moignard Christine Pageot-Millet André Tarridec FT R&D/DAC. Outline. Introduction Proposed definitions IP services & network current state
& in particular a so-called " target NGN ".
whose final state would be compliant with the proposed " target NGN ".
evolution towards NGN are pointed out.
Note that some solutions are already labelled NGN ones although they do not respect the whole
set of rules proposed here.
“ Telephony NGN " when it is at least able to support the whole set of existing telephony services (plain, enhanced and IN services) with matching Quality of Services, QoS.
A “ Target NGN ” includes services supported
by Telephony NGNs & those by Data NGNs.
the final evolution of these two ones.
Control Platform :
Call Server, Gatekeeper, Bandwidth broker,…
« core NGN »
LocalProposed definitions : Core & Transit NGNs
> great interest for inhomogeneous networks, for migration, when traffics sources are scattered etc …
Services Control Platform
or Local control Platform (Call Server d’Appel, Gatekeeper, Policy server, Softswitch, MGC, …)
« Local NGN »
LocalProposed definitions : Local NGN
To emulate LEX functions is just not enough.
Not Always On
To Collect &
IAP/ISPIP services and network current state : IP network
> to residential customers, professional customers
> Internet, Intranet and Extranet connectivity is possible.
> No service differentiation through differentiated
The edge part concentrates the traffic and performs
specific edge functions ( flow classification &
conditioning, external routing protocols processing &
network-based VPN handling).
Edge and border routers support interfaces with the
access network, internal servers, ISPs/IAPs & Internet.
The core part routes and forwards aggregated flows
over core routers.
MPLS improves the traffic engineering and supports
network-based IP VPNs.
> no QoS guarantees and no differentiated services as required by some users and applications,
> no service control servers on top of the call servers for value-added services,
> no service portability over different access networks,
> no service portal.
> separation of transport resources from AAA servers and call control,
> service portability over a given access network,
> use of a packet transport to support every service (data, voice).
or Proxy SIP
IPVoIP (H.323 & SIP) general architecture
It controls end points (GW & terminal) of a
H.323 domain & performs call request
for media stream
QoS - NP
TControl plane architecture & QoS
Its introduction will be progressive
MM IPNGN introduction in CS and PS domains – post R5 architecture.
Mobile IP is a key component of "full IP" scenarios.
NMMobile IP : architecture & principles
perform moving detection function &
registration functions to a HA or a FA.
connects the H sub-network of the mobile
is in charge of updating the information
DB for mobile location & reemitting to
data to its current location
the V sub-network of the mobile. It
registers visiting mobiles & offers services
such as datagrams routing to
(e.g. in target NGN and partly in UMTS networks) and telephony services, thanks to respectively mobile IP and to SIP or H323 architectures.
The models that describe their customer (i.e. data attached to their customer),
The functions that allow services to be delivered to their customer (i.e. applications dealing with customers),
The equipment running these applications and the associated databases.
will coexist for a long time.
… lots of work ahead !
"A Next generation architecture for the public network " ISS2000
TINA-C Network Resource Architecture, version 3.0 – Feb. 1997
TIPHON Network Architecture & reference configurations, DTS 02003 v0.0.1 – ETSI – March 1999
Multiservice Switching Forum Architecture, MSF99.074 – March 1999
Megaco Protocol Proposal Working draft, draft-IETF- megaco-protocol-01.txt – April 1999
Draft ITU-T Recommendation Q.BICC, Bearer Independent Call Control protocol definition
RFC 2543 SIP : Session Initiation Protocol
RFC 3015 Megaco Protocol v1.0
RFC 2002 IP mobility Support (for Ipv4)
Universal Mobile Telecommunications System (UMTS); Virtual Home Environment (VHE) in the Integrated Services Digital Network, Evolved UMTS core network, ETSI EG 201 717.
Universal Mobile Telecommunications System (UMTS); Service aspects; Virtual Home Environment (VHE), ETSI TR122 970, 3G TR 22.970.
Eurescom Project P920, UMTS Network Aspects (http://www.eurescom.de/public/projects/P900-series/p920/P920.htm
RFC 1633 Integrated Services in the Internet Architecture: an Overview
RFC 2475: An Architecture for Differentiated Services
RFC 3031: Multiprotocol Label Switching Architecture
draft-ietf-mpls-diff-te-reqts-00: Requirements for support of Diff-Serv-aware MPLS Traffic Engineering
RFC 1883: Internet Protocol Version 6 (IPv6)
ARF: Access to the Resources Function
ASF: Access to the Services Function
AP: Application Part
BAS: Broadband Access Server
CAP: Camel Application Part
CS: Call Server
CSCF: Call State Control Function
DWDM: Dense Wavelength Division Multiplexing
FA: Foreign Agent
GGSN: Gateway GPRS Support Node
HA: Home Agent
HSS: Home Subscriber Server
IAP: Internet Access Provider
IGP: Interior Gateway Protocol
INAP: Intelligent Network Application Part
ISDN: Integrated Services Digital Network
ISP: Internet Service Provider
LEX: Local EXchange
LSP: Label Switched Path
MG: Media Gateway
MGC: Media Gateway Control
MGCF: Media Gateway Control Function
MPLS: MultiProtocol Label Switching
MSC: Mobile service Switching Center
NAS: Network Access Server
NGN: Next Generation Network
OTN : Optical Transport Network
PHB: Per-Hop Behaviour
POTS: Plain Old Telephone Service
PDSN : Packet Data Serving Node
PS: Proxy SIP
PSTN Public Switched Telephony Network
QoS : Quality of Service
RC: Resources Control
SC : Services Control
SGSN: Serving GPRS Support Node
SGW: Signalling Gateway
UMTS: Universal Mobile Telecommunications System
VHE: Virtual Home Environment
VPN: Virtual Private Network