2004-09 NGN-Training Vietnam Part1

Next Generation Network ( NGN )


VNPT Training Session ( Vietnam , 6th to 8th September 2004 )

VNPT Training Session ( Vietnam , 6th to 8th September 2004 )

( speaker : Eric LE TONQUESSE )( speaker : Eric LE TONQUESSE )

All rights reserved 2004, Alcatel

NGN Training, VIETNAM

September 2004. Slide 2

Agenda ( Overview )Agenda ( Overview )

NGN introduction

The different aspects of NGN

Protocol Overview

NGN Hot topics

ALCATEL OPEN : our NGN solution



VNPT Training Session / Part 1( Vietnam , 6th to 8th September 2004 )

VNPT Training Session / Part 1( Vietnam , 6th to 8th September 2004 )

( speaker : Eric LE TONQUESSE )( speaker : Eric LE TONQUESSE )




Agenda ( Overview )Agenda ( Overview )

NGN introduction

The different aspects of NGN

Protocol Overview

NGN Hot topics

ALCATEL OPEN : our NGN solution




NGN introduction

Why NGN ?What is NGN ? Role of the Softswitch Role of the Media Gateway Role of the Signalling Gateway Role of the Media Server Role of the Feature Server

AgendaAgenda




Existing Voice and Data networks are already not independent anymore

Access Edge Core

D

a

t

a

V

o

i

c

e LEXLEX TEXTEX

S/RS/R

Corporate LAN

V90 Modulation

NASNAS

POTS

RSURSUISDN

BASBASDSLAM

Splitter

ADSL

IP or ATMPacket Backbone

IP or ATMPacket Backbone

TGWTGW

GKGK




Market Dynamics : actual facts

Voice 80% of total worldwide

telecom service revenue

Basic Local/Long Dist. voice service margin decreasing

Data 20% of total worldwide

telecom service revenue

IP enhanced service profit margin increasing

( Source : A. D. Little )

Global Voice/Data Crossover

0

1,000

2,000

3,000

4,000

5,000

6,000

1997 1999 2001 2003 2005 2007

VoiceData

Gb/s

Voice and Dialup Internet are Today the Main Revenue Generators for ESPs ( Established Service Providers )




Advantages of the NGN architecture

1) The already existing dependence of the 2 networks (Voice and Data) and the boom of the second one (Data) makes natural this convergence evolution, especially for data-centric operators ( such as ISPs ). 2) In addition, operators cannot anylonger underestimate the potentiel advantages of such a unified network :

Increased flexibility (inherits the self healing a.k.a. resilience from the IP technology). Shortest path for the media stream : from calling party to called party without crossing the equipmentin charge of the Call Control ( network flattening ). Consequently, possible centralization of the Call Control capacity ( in small number of Softswitches ). Possible bandwidth savings ( compressed CODEC and/or silence suppression ). Ready for Multi-Media services.




SS7

NGN : Key Market Drivers

NGNData

(IP or ATM)

NB Access

POTS/ISDN

H.323/SIP xDSLDial-upPOTS/ISDN

CAPEX/OPEXEnd of Life

Analog Leap-frog

CAPEX/OPEXEnd of Life

Analog Leap-frog

New RevenuesPrice Erosion

Customer churn

New RevenuesPrice Erosion

Customer churn

IAD

Bypass expensivetransit resources

Internet offload, Class 4/5

capngrow, replacement, expansion

Internet offload, Class 4/5

capngrow, replacement, expansion

IP telephony, broadband multimedia services,

out-of-region expansion

IP telephony, broadband multimedia services,

out-of-region expansion

BB Access

PSTN(TDM-based)




NGNNGNOpen interfaces

Seamless Transportover TDM, ATM, IP

Cost Savings(CAPEX & OPEX)

Separation of service, control,

media and access

New Servicesand new revenues

Multi-vendorinteroperability

NGN Expectations




Telenor (Norway) Lot of work has still to be done on

QoSQoS and economicseconomics

Energis (UK) Circuit switches will die-out

beyond 2010

Telia (Sweden) VoIP is 6-8 times more expensive

than TDM

Infostrada (Italy) NGN profitability comes from new

services, not from cost savings

From disillusion ( see testimonies dated 2001 ) to starting first NGN deployments ( 2004 )

Deutsche Telekom (Germany) Technologies cannot converge, only

services

British Telecom NGN deployment costs should not be

under-estimated

Cisco For Voice application, IP network

shouldnt be loaded more than 15%

Infonetics Research the total revenue for softswitches and

media gateways declined about 9 percent in the third quarter of 2002. Most service providers dont expect to deploy VOIP until at least 2004.




VoIP : from cost reduction to new services All European service providers active with VoIP

Source : Yankee Group 2003




New services are the main driver behind deployments today

VoIP Services

Source : Yankee Group 2003




NGN introduction


AgendaAgenda




NGN is based on the following 2 main concepts :

- Convergence of Voice and Data ( same technology and consequently same Networkused for both applications )

- Separation of the layers( Switching and Call Processing are not any

longer supported by the same equipment )

NGN : the 2 main concepts




A

c

c

e

s

s

T

r

a

n

s

p

o

r

t

C

o

n

t

r

o

l

A

p

p

l

i

c

a

t

i

o

n

Application ServicesVoice/Data/MM

Information SystemIN, TMN

NGN Target Architecture

TGW TDM NetworkData

Network S/R

PacketBackbone

Call Server

RGW AGW IAD

( a.k.a. Softswitch, or MGC = Media Gateway Controller,

or Call Agent )




Services layer

Control layer

Media layer

Access/Transport layer

netw.indep.svcs.

PSTNISDNPLMN

SS7

NGN Architecture




A public communication network with Clear separation of access/transport, media, control

and services layers

Interoperability via open interfaces between these layers and all other networks

Seamless control of multiple transport technologies (ATM, IP, TDM, ...)

Use of standards-based components

New services, new revenues !

NGN Concept




Switching

Call Control

Interfaces

PacketNetwork

Call Server

Gateways

Central-Office Switch NGN Components

From integrated to distributed call processing




Example of Class 4 ( transit ) : the TDM network of Today

PSTN

SS7

PSTN

SS7

TDM

Switch

PSTN

SS7

Bearer ( 64 kb/s voice channel )

TDM

Switch

ISUPISUP

ISUP

- No CODEC negotiation ( G711 only )- No dynamic addressing ( pre-allocated CIC )- Bandwidth capacity only used by Voice




Integrated VoP Trunking is already NGN-oriented

PSTN

SS7

DataBackbone

PSTN

SS7

BICC ( Bearer Independent Call Control )

Bearer ( voice channel )

Switch(VoP-capable)

Switch(VoP-capable)

- Possible CODEC negotiation ( voice compression and/orsilence deletion are possible ).

- Bandwidth capacity canbe shared between data& voice applications.

( = ISUP + @ and CODEC negotiation )ISUP




PSTN

SS7

PSTN

SS7

Control Layer

Media Layer

Switch(VoP)

Switch(VoP)

DataBackbone

Separation of layers NGN Architecture




NGN architecture ( class 4 = Transit )

PSTN

SS7

CallServer

PSTN

SS7Control Layer

Media Layer

Gate-Way Gate-

Way

CallServer

Bearer

H.248( = MEGACO )

H.248( = MEGACO )

BICC

DataBackbone

ISUP




NGN Class 4 architecture ( enhancement )

PSTN

SS7

DataBackbone

CallServer

PSTN

SS7

TGW

CallServer

BICC (or SIP-T/SIP-I)

*

: Use of SIGTRAN ( SCTP ) to carry ISUP over IP

SGW

ISUP*

TGW

SGW

ISUP*

Bearer

H.248( = MEGACO )

H.248( = MEGACO )

*




Other possible Class 4 architecture : Mono-Call Server

PSTN

SS7

CallServer

PSTN

SS7

TGW

( No more use of BICC nor SIP-T / SIP-I )

SGW

TGW

SGW

Bearer

ISUP ISUP

H.248( = MEGACO )

H.248( = MEGACO )

DataBackbone




Class 5 ( Access ) NGN architecture

CallServer

AGW

CallServer

BICC ( or SIP-T / SIP-I )

: Use of SIGTRAN/SCTP to carry ISDN (Q.931) or V5.2 over IP.Concerning POTS signalling , H.248 is used ( dedicated package ).

SGW

AGW

SGW

RSU

**

Bearer

H.248( = MEGACO )

H.248( = MEGACO )

*

DataBackbone

RSU




Terminal Access Local Switch Transit International

Where can NGN be used ?

New ergonomy, or Local switch replacementOr

International Bypass

Transit replacement, capacity extension Or




PacketBackbone

PSTN

SS7

Call Server

(*)( opti

onal)

TrunkingGateway

Central.Access

GatewayISDN

POTS

ADSL VoDSL SDSL / VDSL

Data

RSU

AccessGateway

Resid.Gateway

(*) : or MGCor Call Agentor Softswitch

IAD

NGN elements overview

Media Server




Media Laye

r

Control La

yer

Service La

yer

CallServer

PSTN

SS7

FeatureServer

WGW

NGN elements per Layer

(or RGW)AGW

SGW

TGW




NGN introduction


AgendaAgenda




Role of the Softswitch

The softswitch provides the call processing intelligence. It communicates with the subtending media gateways in the transport layer by using standards-based control protocols such as MGCP or Megaco (H.248). Using these protocols it determines the two end points that need to participate in a call (or a session). Once identified, it thencommands the two end points to establish a bearer pathbetween themselves. The end points then use appropriate mechanisms (ATM SVCs/PVCs, IP-based RTP stream, MPLS LSP, Ethernet VLAN, ) for the establishment of the bearer path. Advantage of this approach is that the subscribers or themedia types (data, video) can be added/dropped relatively easily to an existing call or session, thereby facilitating"multimedia" communications.




Role of the Softswitch

CallServer

PacketBackbone

Calling Party Called Party

Sig.

GW

Sig.

GW

Ctrl.

< Services >

Bearer

Sig. = ISUP, ISDN, V5.2, H.248 (POTS),




NGN introduction


AgendaAgenda




Role of the Media Gateway

Media Gateway function is only required because ofthe existing TDM-based infrastructure ( no need of Media Gateway function for an end-to-end packet-based communication such as IP-phone to IP-phone ). Definition : connects two end points that may reside in networks based on different technologies : a media gateway provides the bearer level interworking.

In some cases, in-band signalling is monitored to send information to the Softswitch ( ex : collection of subscribers DTMF digits) or to choose the appropriate bearer protocol ( ex : Modem and Fax requirements ).

Interworking with existing PSTN = TGW Interworking with existing RSUs = C-AGW Interworking with TDM Subscribers = AGW or RGW




VoIP induces delay Echo control unavoidable

PCM transport delay: 2 ms Packetization delay: according to packet size ( typical : 5, 10 or 20 ms ) Internal delay

theoretical codec algorithm delay G.711 0 ms ( typical : 2 to 4 ms for other CODEC ) internal processing delay 2 ms

IP transport delay 0 ms (under lab conditions) Jitter Buffer delay 3 ms Internal processing delay


PCM transport delay 2 ms

PCM transport delay: 2 ms Packetization delay: according to packet size ( typical : 5, 10 or 20 ms ) Internal delay


IP transport delay 0 ms (under lab conditions) Jitter Buffer delay 3 ms Internal processing delay


PCM transport delay 2 ms

GW GWIPTDM TDM




In case of echo, ITU-T considers that echo

control is required as soon as round trip delay is above 50 mS

< 50 mS

> 50 mS

Reminder on Echo Control ( ITU-T G.131 )

Echo

Delay




Echo generator

Electrical echo : Subs.Board4 wires 2 wires

Echo

The echo in PSTN is mainly caused by impedance mismatches at four-wire/two-wire conversion points on the transmission line of an analog subscriber

It also applies to NGN architectures !!

Main echo generator is the TDM network




Delay generators in TDM networks

satellite links : GSM voice compression (about 90 ms).

36000 Kms Up + 36000 Kms down at light speed ( 300,000 Kms/sec. ) = 260 mS .

( satellite )

Main delay generators in the TDM networks




Internat.Exchange

ECD

( satellite )

Internat.Exchange

ECD

CallingPartySubscriber

Echo

CalledPartySubscriber

Echo

(*) ECD dealing with echo generated at calling party side

(*)

(#) ECD dealing with echo generated at calling party side

(#)

Reminder of the TDM Echo Control solution




GWECD

CallingPartySubscriber

Echo

CalledPartySubscriber

Echo

(*) ECD dealing with echo generated at calling party side

(*)

(#) ECD dealing with echo generated at calling party side

NGN Echo Control solution

PacketNetwork

Delay greatlyabove 25 mS( one way )

GW ECD

(#)

GWs must supportG.165 and G.168




Other GW capability requirement examples

Basic Tones and Announcements : they are to be sent by the Gateway ( via H.248 command messages ). V23 freq. generator : when the analog subscriber is V23, the frequencies are to be sent by the AGW and theappropriate H.248 package has to be supported. Subscribers with TTX : charging pulses have to be sent by the AGW ( via H.248 using appropriate package ). Conference : the Gateway may host the conference devices ( 3 terminations added in the same H.248 context bythe MGC, create a conference call ). RTP and TDM hair-pinning : may be required in someconfigurations ( see next slides ).




Examples of Gateways requirements

Three examples :

- Support of MOVE H.248 command :

- Support of RTP Hair-pinning :

- Support of IP Loop ( TDM hair-pinning case ) :

As soon as services are possible (Cx modification), MOVE H.248 commands can be sent by the Softswitch.

As soon as redirection is not possible (or for inter-domainreason), RTP hair-pinning configuration is triggered.

As soon as local traffic exists on a GW, TDM hair-pinning configuration is triggered.




Redirecting ( Mono call server configuration ) support of Move H.248 command required

PSTN PSTNTGW

IPAGW

Subscriber B activated CFNR towards Subs. CSubscriber A dials

B number

Subs. C

VoIP

VoIP

TGW

H.248 Move

CallServer




Redirecting ( Multi call server configuration ) support of RTP hair-pinning required

PSTN PSTNTGW

IPAGW

Subscriber B activated CFNR towards Subs. CSubscriber A

dials B number

Subs. C

VoIP

VoIP

TGW

CallServer

CallServer

BICC or SIP-I (*)

Call Servercontrol

separation

(*) : without use of redirection mechanism




Inter-domain ( interworking between 2 NGN operators ) RTP Hair-pinning required anyway in the GW

CallServer

TGW IP IP

CallServer

TGW

CallServer

TGW

BICC or SIP BICC or SIP

H.248 H.248 H.248

Must supportRTP Hair-pinning

also known as Border Media Gateway

RTP RTP




TDM to TDM configurations

IP

TGW

LEX

LEX

Class 4 case

RSU

RSU

Class 5 case

TGW

Real TDM-TDM hair-pinning( more optimized )

TDMVoIP

Known as IP loop ( to be supported for complex calls )




Summary of the 3 hair-pinning cases

RTP hair-pinning :

2 IP terminations in the same H.248 context.

TDM hair-pinning :

2 TDM terminations in the same H.248 context.

IP loop :

2 different H.248 contexts with one IP termination and one TDM termination within each of them




NGN introduction


AgendaAgenda




Role of the Signalling Gateway

Signalling Gateway provides a signalling interworkingbetween TDM-based networks and Packet-based networks. Depending on the signalling used (ISUP, ISDN, V5.2, ), specific protocols (such as SIGTRAN) are used to carry efficiently (real-time constraints) and securely (protection against existing packet loss and jitter in packet networks ) the signalling between the TDM-based party and the Softswitch. For subscriber signalling and ISUP associated (voice and signalling received on the same link), Signalling Gateway function is often integrated in the Media Gatewayequipment ( 2 functions in the same box ). For ISUP quasi-associated ( use of STP ), Signalling Gateway is a stand-alone equipment.




Signalling Gateway integrated or co-located with the Media Gateway equipment ( distributed SGW )

PSTN

SS7

CallServer

TGW

SGW

Bearer

ISUP

DataBackbone

Called Party

Associated-ISUP( Voice and Signalling

carried by the same PCM)




stand alone Signalling Gatewayin a next-generation STP ( centralized SGW )

PSTN

SS7

CallServer

TGW

NG-STP( SGW )

Bearer

ISUP DataBackbone

Called Party

Quasi-associated ISUP (use of STP)




NGN introduction


AgendaAgenda




Role of the Media Server

The Media Server delivers voice and video services

over Packet-based networks, such as conference bridges

(if not supported by the Media Gateway), complex

announcements (basic announcements being delivered by

the MGW), I.N. (Intelligent Network) user interaction,

On the market, they are either SIP-controlled or

H.248/MGCP-controlled and are often NGN evolution of

SRPs ( Service Resource Point of the I.N. solution).

By definition, it is a centralized equipment but Media

Server function may also be integrated in the Softswitch

or distributed in the Media Gateways.




Focus on the Media Server : example of a call with I.N.

CallServer

AGW

IPBackbone

MediaServer

PSTN

SS7SCP

TGW

SGW

1: Off hook notification2: Be ready to receive digits

Send Dialling tone3: Sending of dialled digits

( PPC = PrePaid Card )

6: Connection requestssent to AGW and MS

4

4: PPC service triggering

88: Play Announcementsent to Media Server

7: set-up of the VoIP RTP streambetween AGW and Media Server

11: Card Nb and calledparty Nb sent to SCP

11

13: New connectionrequests sent to AGW and TGW

13

13

14: set-up of the VoIP stream towardscalled party.

12: ISUP

1 2

3 6

VoIP7

VoIP14

5: Connect To Resourcesent to Call Server

5

6

9: Please dial your card number

10: Please dial thecalled number




NGN introduction


AgendaAgenda




Role of the Feature Server ( or Application Server )

The Feature Server (or Application Server ) isan optional equipment which complements the service set offered by the Softswitch, playing at service layer. INAP or API can be used between the Control layer (Softswitch) and the Service layer (Feature Server). Main target of the feature Server is to deliver new services without software upgrade of the Softswitches, and in a very short time (centralized equipment usinghigh-level development languages). Moreover, Feature Servers often offer open API interfaces allowing connection of Third-Party application servers : new services can then be developped by the operator itself. Feature Server are often NGN evolution of SCPs (I.N.)




Network Management

ServiceManagement

ProductCreation

C

o

r

b

a

,

S

N

M

P

,

F

T

P

Network Management

ServiceManagement

ProductCreation

C

o

r

b

a

,

S

N

M

P

,

F

T

P

Softswitch MultiMediaSoftswitchAccess Server

H323, SIP, Radius, Diameter, ...

SoftswitchMultiMediaSoftswitchAccess Server

H323, SIP, Radius, ...

HTM

L, WA

P, X

ML

User- ServiceInteraction

SelfManagement

SelfActivationHTM

L, WA

P, X

ML

User- ServiceInteraction

SelfManagement

SelfActivationParlay, Jain,OSA, SIP, XML

InternalApplication

Server

ExternalApplication

Server

Parlay, Jain,OSA, SIP, XML

InternalApplication

Server

ExternalApplication

Server

ISUP, INAP, CAMEL, MAP, IS41

S12/E10/Megahub AXE-10 DX 200 EWSD DMS 5ESS System X EMX

ISUP, INAP, CAMEL, MAP, IS41

Open Services Platform

Service Creation

Open Services Platform

Service Creation

ToolkitsToolkits

New services offered by an Upper-layer platform

THANKS for your Attention !THANKS for your Attention !

[email protected][email protected]

Documents

2004-09 NGN-Training Vietnam Part1