Public VoIP-Service Infrastructure - induteq.nl voip service infrastructure 06... · Public...

Masterclass Public VoIP june 2010 1 © Nokia Siemens Networks

Gerben Joustra, Solution ArchitectNokia Siemens Networks, June 2010

Public VoIP-Service Infrastructure

2 © Nokia Siemens Networks Mastrerclass Public VoIP june 2010

Nokia Siemens Networks

In 2007, Nokia OY and Siemens AG brought together their Public Network activities in one Joint Venture

Siemens NetworksNokia Networks

Top 3 Supplier of Telecom Network Infrastructure• Telcom Operators, authorities• Mobile, Fixed and Converged Service Platforms (voice, video, data)• Transmission Systems (TDM, DWDM, Carrier Ethernet, IP)• Applications, OSS/BSS, Subscriber Management, Billing• Security Solutions• Services: Care, Install&Comm., System Integration, Network Operation


Agenda• Vision on Telecom Operator Eco-system

– Customer demands

– Network evolution

• Public Network Concepts– Layered Architecture

– Bellheads & Netheads– ISO 7 layers model

– Switched vs Non-switched

– Connection-oriented vs Connection-less– QoS

• VoIP– SIP: Session Initiation Protocol– Voice over Internet

• Public VoIP Network Architecture– General Architecture– Two cases

• Future Evolutions


Tomorrow's communication world

5 Bn People connected

5 Bn mobilesubscriptions

.8 Bn broadbandsubscriptions


• End user wants the my-service-anywhere experience

• New intelligent & powerful device classes already start to support this goal

Converged Devices


Connectivitywith a few key applications

More and more connections and network capacity needed

• Anywhere, anytime connectivity

• Capital intensive, high entry barrier

• Connection fee based business model

Two opportunities emerging to operators

ApplicationsDigital Distribution & services

Internet is the key source of serviceand business model innovations

• Fierce competition

• 3rd party revenue models

• Premium content and communities have value


Network Transformation

legacy, stovepipe, monolithic

Network regulation, competition and new business models require an efficient solution for the network.


Here we are.

This may need simplification.


Network Transformation

legacy, stovepipe, monolithic converged, simplified

Network regulation, competition and new business models driving unbundling and flatting of the networks.

Multi-Access

Transport & Aggregation

Service Control

Applications

Multi-Access

Transport & Aggregation

Service Control

Applications


Embracing the Internet – and capturing value

� Manage bandwidth and Quality of Experience� Manage application specific usage � Charge per service� Leverage identity data

Any Content or Application

Personal TVCommunity Social Web

VoIP

NavigationGamingIPTV

Any Device

Converged Network

Consumer life-style and needs drive Internet-centric application development


Network Architecture Vision


Two cultures need to cooperate

Bellheads

Netheadsand


The prejudices

NetheadsNetheadsBellheadsBellheads

• Bureaucratic• Inflexible monopolies• No customer focus• Old technology

(will fade away)

• Freaks• Chaotic• No understanding of

carrier business(five nine’s)


Convergence…

BellheadsBellheads NetheadsNetheadsNext

GenerationNetworks

• Availability• Reliability• Guaranteed

Service

ConnectionsConnections

Optimized for Optimized for VoiceVoice

• Flexibility• Best-effort

Connection-lessConnection-less

Optimized for Optimized for DataData


Tools

QoS vs.Bandwidth

QoS vs.Bandwidth

CCITT vs.IETF

CCITT vs.IETF

Distr. Intelligencevs. Client/server


Connection vs.ConnectionlessConnection vs.Connectionless


1996 1997 1998 1999 2000

1 Gb

10 Gb

100 Gb

Bellheads’ and Netheads’ approach to QoS: Connection or Bandwidth

Evolution of Router Throughput1 Tb

Construction Cost per Bandwidth

1 10 100 10001%

10 %

100 %

Fiber capacity Gbps

cost

STM-16

WDM 8 & STM-16

WDM 8 & STM-64

OADM 16with SLR 64

OADM 80without SLR

A connection is a network state that ensures delivery of data

through reservation of resources within the network and through

receiver notification


Netheads’ vision on connections: Sessions

HTTP, SMTP,FTP,NTTP,...

HTTP, SMTP,FTP,NTTP,... Application LayerApplication Layer

Transport LayerTransport Layer

Internetwork LayerInternetwork Layer

Data-Link LayerPhysical Layer

Data-Link LayerPhysical Layer

TCPTCP

IPIP

Ethernet, Token Ring, FDDI, X.25, Wireless, ATM, xDSL...Ethernet, Token Ring, FDDI, X.25, Wireless, ATM, xDSL...

UDPUDP TCPTCP

IPIP

UDPUDP

ServerServerClientClient

IP Network

Protocol Layers

Server Protocol StackClient Protocol Stack

Open APIs to networkfor IP-packet transport

Information Flowthrough protocol stacksApplication

(Client Side)

Application(Client Side)

GUIAppl. Logic

Network APIApplication(Server Side)

Application(Server Side)

Appl. Logic

Network API

Flows:IP Addresses +TCP/UDP ports

Flows:IP Addresses +TCP/UDP ports


NetheadsNetheads

Conclusion: Taking the best of both worlds

BellheadsBellheadsNext

GenerationNetworks

QoS vs.Bandwidth

QoS vs.Bandwidth

Connection vs.ConnectionlessConnection vs.Connectionless

ITT vs.IETF

ITT vs.IETF




� Standard model as reference� The 7 layers

The OSI seven layer model

Speech, Video

CODEC

SIP

UDP (TCP, FTP)

IP

Ethernet

Fibre, Copper

(WDM, PON), (DSL, modem)


The OSI seven layer model

All People Seem To Need Data ProcessingPeople Do Need To See Pamela Anderson

� Each layer supports the layer above


Circuit-switched vs. Packet-switched

CIRCUITContinuous chanelCapacity reserved for unique usage

examples:• symm. coppercable• TDM, FDM etc.

Applications:• telephony (fixed, mobile)• telex• leased line

PACKETData is cut into packetsCapacity shared for multiple usage

examples:• X.25, Frame Relay / ATM• Ethernet, IP

Applications:• Internet• VPN’s, • Enterprise Networks


Connection oriented vs. Connectionless

Connection orientedUnicast (bi-)directionalLogical connectionSet-up and tear downPermanent or switched• (operator or subscriber)Capacity-reservationIf no capacity available, no connectionFixed routeno change of orderLow delay, no delay variationLow bit-error-rate and packet-loss ratioQoS guarantees

Connection lessUni-, multi- or broadcastNo connection, but sessionsLog-on/log-offSession start and end (user)No fixed routeNo capacity-reservationSource can always send dataChange of order possibleUnpredictable delayDelay variations (jitter)High packet-loss ratio in case of high traffic volumes (congestion)Best effort


Examples

Circuit-switched Packet-switched

Connection-less Not applicable IP, Ethernet Digital TV

Connection oriented TDM WDM Telephony (F, Mob.)

Frame Relay ATM Public VoIP


Quality-parameters

Quality of Service (QoS)Guaranteed values for transmission parameters

• delay• jitter• bandwidth• bit-error-rate• data loss ratio

Comes from the ATM-world, so from the Bellheads

Class of Service (CoS)Qualitative indication of importance and priority

• priority in transmitting

• priority in survival

Comes from the IP/ethernet-world, so from the Netheads


Service requirements

service bitrate delay jitter priority

speech low minimum minimum highest

video-conference high very low low highest

video on demand very high low low high

Internet/Intranet middle to high acceptable acceptable low

business-processes

??? low acceptable high

e-mail low acceptable acceptable lowest


Agenda

• Vision on Telecom Operator Eco-system– Customer demands– Network evolution

• Public Network Concepts– Layered Architecture– Bellheads & Netheads– ISO 7 layers model– Switched vs Non-switched– Connection-oriented vs Connection-less– QoS

• VoIP– SIP: Session Initiation Protocol

� High level description� Message exchange� Call Feature Server / Session Agent and SIP-Client

– Voice over Internet• Public VoIP Network Architecture

– General Architecture– Two cases



Voice over Internet Protocol

VoIP:

Voice communication, using the IP-protocol

It is not the same as Voice over Internet

In fact: in public VoIP-services, the Internet is not involved at all

(Skype and the like are using Internet)

Statement:

For a practically usable public voice service, the internet is not suited because of a lack of QoS-measures


Voice over an IP-infrastructure

Absolute minimal requirements:

• conversion between analogue voice signals and IP-protocol (Media Gateway)

• equipment on both ends (always) on line

• must know each other IP-address

• IP-packets (layer 3) to be enhanced with information on transport layer (4) --> UDP

• Session (“call”: on layer 5, using SIP-protocol


Voice over an IP-infrastructure

Also other servers are required,e.g., DHCP, DNS, location, deployment, management, licensing, authentication

SIPEndpoint

SIPEndpoint

RTP streams

Signallingserver

Signallingserver

Signalling(call controland mediacontrol)

SIP: Session Initiation protocol (RFC 3261 a.o.)• For initiating communication sessions

between parties, including locating the remote party.

• Can be considered as call control.SDP: Session Description Protocol (RFC2327)• Can be considered as media control


SIP

The Session Initiation Protocol (SIP)Prof. Henning Schulzrinne, Dept. of Computer Science, Columbia University, New York, New York

(sip:)[email protected]

For more information. . .SIP: http://www.cs.columbia.edu/siphttp://www.iptel.org/SIPResourcesSDP: http://www.cs.columbia.edu/˜hgs/internet/sdp.htmlRTP: http://www.cs.columbia.edu/˜hgs/rtpPapers: http://www.cs.columbia.edu/IRT


SIP entities

user agent (UA)• End station (e.g., IP-phone, soft client)• Gateway (e.g. Residential Gateway)Proxy server• routes the request onwards (call management server, voice application

server)• can forkRegistrar server• registers an association between address-of-record and physical

address (IP address) = subscriber• often collocated and combined with proxy (Session Agent)Redirect server• instructs upstream entity to route the request onwards


SIP Messages

Requests (Methods)REGISTER• Register contact informationINVITE, ACK, CANCEL• Setting up sessionsBYE• Terminating sessionsOPTIONS• Querying servers about their capabilitiesSUBSCRIBE, NOTIFY (RFC 3265)• Event notification frameworkMESSAGE (RFC 3428)• Instant messages

Responses1xx: Provisional• request received, continuing to process the

request

2xx: Success• the action was successfully received,

understood, and accepted

3xx: Redirection• further action needs to be take in order to

complete the request

4xx: Client Error• the request contains bad syntax or cannot be

fulfilled at this server

5xx: Server Error• the server failed to fulfill an apparently valid

request

6xx: Global Failure• the request cannot be fulfilled at any server


Requests & responses are grouped in transactionsClients retransmit requests until final response (provisional for INVITE)Responses are selfrouting (using VIA header being updated by servers)Media is exchanged directly between caller and callee

1

2

3

4

5

6

7

8

9

101112

SIP Client (UAC)

SIP RedirectServer

SIP Proxy SIP Proxy

SIP Client(UAS)

Location ServiceRequest

Response

SIP Proxy

SIP Signaling

From presentation “SIP – Basics, Applications & Standardization” by Bernard Hammer


Media control

SDP (Session description Protocol)Offer/answer• Simplest way is offer in INVITE request - answer in 200 OK response• E.g. CODEC-negotiation

Early media• Normally ringback tone provided at UAC

• Can be early media (ringback tone, announcement) played across network, particularly from a legacy network

• Speech clipping

Re-INVITE• To change session within context of a single dialog

3.565.3ACELPG723.1

3.928CS-ACELP

G.729

3.8532ADPCMG.726

4.164PCMG.711

MOSTransmission RateAlgorithmStandard


INVITE sip:[email protected] SIP/2.0

To: Jo <sip:[email protected]>From: Neil <sip:[email protected]>Call-ID: [email protected]: SIP/2.0/UDP 193.195.52.229:5060CSeq: 1 INVITEContent-Type: application/sdpContent-Length: 125

v=0o=193.195.52.229 4858 0 IN IP4 193.195.52.229s= Working late again?c=IN IP4 193.195.52.229m=audio 5004 RTP/AVP 0

CRLF

Start Line

Headers

Blank Line

Body

Source: Ubiquity

Overview of a SIP Request


INVITE sip:[email protected] SIP/2.0To: Jo <sip:[email protected]>From: Neil <sip:[email protected]>Call-ID: [email protected]: SIP/2.0/UDP 193.195.52.229:5060CSeq: 1 INVITEContent-Type: application/sdpContent-Length: 125

v=0o=193.195.52.229 4858 0 IN IP4 193.195.52.229s= Working late again?c=IN IP4 193.195.52.229m=audio 5004 RTP/AVP 0

Method Type Request URI SIP Version

User being invited to the call

User originating the callGlobally unique ID for this callIP Address and Port of previous hopCommand Sequence number and typeBody type - an SDP payloadLength of the body of the message

SDP Version

Owner/creator and session Identifier

Subject of session

Connection information

Media and Transport information

A SIP Request in Detail



1 INVITE sip:[email protected] SIP/2.0

2 SIP/2.0 200 OK

3 ACK sip: [email protected] SIP/2.0

nsn.at delta.swh.sk

Message Flows: Direct Invitation



7 SIP/2.0 200 OK8 ACK sip: [email protected] SIP/2.0

nsn.at

delta1 INVITE sip: [email protected] SIP/2.0

4 INVITE sip:aj@delta SIP/2.0

9 ACK sip:aj@delta SIP/2.0

6 SIP/2.0 200 OK

5 ring

3 aj

@de

lta

2 an

ton.

jane

tka

location server

swh.sk

Message Flows: Use of Proxy Server



1 INVITE sip: [email protected] SIP/2.0

4 SIP/2.0 302 Moved temporarily5 ACK sip: [email protected] SIP/2.0

nsn.at

delta

6 INVITE sip: [email protected] SIP/2.0

7 ring

3 aj@delta

2 anton.janetka

locationserver

swh.sk

9 ACK sip: [email protected] SIP/2.08 SIP/2.0 200 OK

Message Flows: Use of Redirect Server



SIP Session (example)

SIP phone SIP phoneProxy server1 Proxy server2

Tijd

INVITE M1INVITE M2

100 Trying M3 INVITE M4100 Trying M5

180 Ringing M6

180 Ringing M7

180 Ringing M8 200 OK M9

200 OK M10

200 OK M11

ACK M12

BYE M13

200 OK M14

RTP Media

User accepts call

User hangs up


Security: Digest Authentication

UACINVITE

UAS

401 (unauthorized)

No credentials

Challenge with header (*) :WWW-Authenticate: Digest

realm=“[email protected]”nonce=“12AB…”

INVITE Credentials in header(*) :Authorization:Digest username=“alice”

realm=“[email protected]”nonce=“12AB…”nc=1cnonce=“123…”response=“98FE…”

200 OK Includes header(*) :Authentication-Info: nextnonce=“4732…”Resp-auth=“4711…”

Digest: MD5 hash of username, realm, user password. nonce, …

Or 407 (proxy-authentication-required)

(*) if authenticating with Proxy Server, uses headers:Proxy-AuthenticateProxy-AuthorizationProxy-Authentication-Info


What is ENUM ?

ENUM stands for Electronic of E.164 NUMber mapping, and is defined by the IETF in RFC 3761 as:

the mapping of „Telephone Numbers“ to Uniform Resource Identifiers (URIs) using the Domain Name System (DNS) in the domain e164.arpa


How does ENUM work?

Take a phone number

Convert this into a domain name

Put the reachability data in a DNS

Request DNS (does 0623368970 have sip?)

DNS response

+31 6 23368970

0.7.9.8.6.3.3.2.6.1.3.e164.arpa

sip:[email protected]


What functions provides ENUM ?

Service InteroperabilityEfficient RoutingNumber PortabilityIdentity Management


Efficient routing / number portability

IPIP

PSTNPSTN

Provider AProvider B

SIPPBX

SIPPBX

ENUM


Identity Management

Antoin Verschuren

Utrechtseweg 310

PO Box 5022

6802 EA Arnhem

The Netherlands

tel: +31 26 3525500

fax: +31 26 3525505

mob: +31 6 23368970

http://www.antoin.nl

mailto: [email protected]

skype: antoin.verschuren

msn: [email protected]

sip: [email protected]

yahooID: antoin_verschuren

…………

………….

Antoin Verschuren

+31 26 3525510


ENUM configurations

Public User ENUM� User has to deliberately supply his data� Chicken and egg

Public Infrastructure ENUM� Currently no standardisation� No business case

Private (Carrier/Operator) ENUM, SIP peering� Emerging application within operator environments,� Replacing traditional IN-service in SIP platforms


Voice over Internet, using SIP

Skype:

•Provides a software SIP-client and a friends and presence application

•If subscribed to: “Skype-out” to call to PSTN-subscribers

•You need to know the URL (IP@) of the partners

User ENUM (public server):

would enable calls to other SIP-users, connected to the internet

ENUM


Public Voice Service, using SIPService Requirements:

•Any to Any•POTS•24/7•Plain calls + limited features (Voicemail, CallForwarding, CLIP/CLIR, ...)

Call Feature Server and Registrar (CMS/VAS): provides on-net calls only•Media Resource Server, for tones and announcements•Voicemail Server

Residential Gateway: translates between POTS (ISDN) and SIP/RTP

Operators’ private IP Backbone


Public Voice Service, using SIP

Access path:

•Residential Gateway (RGW) translates between POTS and SIP/RTP

•First mile: DSL, Cable, Fibre

•Aggregation: L2/L2,5 network (ATM, Ethernet/MPLS)

•Plain calls + limited features (Voicemail, CallForwarding, CLIP/CLIR, ...)

Session Border Controller provides:

•NAT (IP-IP-translation) for topology hiding

• Security measures: session awareness, DoS, protocol anomalies




Subscriber growth:

•Additional CMS/VAS required (“class 5 environment”)

•Creation of “Class 4 layer”, to interconnect the “class 5” servers

•Class 4 Softswitch (SIP Router)

•Location Server (like traditional NumberPortability-server)

•INAP (traditional IN-protocol in SS7) or ENUM




Connection to other Telco Operator Networks:

•TDM-based (PSTN, Mobile)

•Requires Media Gateway, to translate between IP and TDM

•Media Gateway Control Function

•In general combined in class 4 softswitch

•H.248 protocol to control the gateway (MGCP/Megaco)




Connection to other Telco Operator Networks:

•SIP-based (other VoIP operator)

•Requires Session Border Controller,

•IP Topology hiding (NAT)

•Security




Full Service scope:

•Phone calls to and from any other phone in any network

•Fax-transmission (and datamodem tranmission)

•Usage of SIP-client in PC

•Video-calls (Webcam with SIP-client on PC or dediated SIP-Videophone)

•Restricted to SIP-domain or additional Video-gateway required


RTP

RTPRTP

RTP

SIP

SIP

SIPSIP

SIP

SS7INAP/SS7 or ENUM

H.248TDM-bearer traffic


KPN’s Public VoIP Service, InternetPlusBellen

KPN’s private IP Backbone

RTP

RTPSIP

RTPSIP

SIP SIP

SIP

SS7

INAP/SS7

H.248

OtherIP Telco-operator

Access Network

xDSL-Ethernet-MPLS

FttH/FttC-Ethernet-MPLS

KPN IMS

OSS:

•Network Management

•Fault Management•Performance Monitoring

BSS

•Provisioning

•Billing•Helpdesk

•CPE management

Security

•Anti attack and misusage•Legal Interception


Ziggo’s Public VoIP Service

Ziggo’s private IP Backbone

RTP

NCS

SIP SIP

SS7

INAP/SS7

H.248

Access NetworkHFC-coax: - MTA: NCS/Packetcable- Modem+CMTS: DOCSISAggregation: Ethernet-MPLS

OSS:

•Network Management

•Fault Management•Performance Monitoring

BSS

•Provisioning

•Billing•Helpdesk

•CPE management

Security

•Usage of DOCSIS and NCS/Packetcable provides a beter basic security•Legal Interception


Agenda

• Vision on Telecom Operator Eco-system– Customer demands– Network evolution

• Public Network Concepts– Layered Architecture– Bellheads & Netheads– ISO 7 layers model– Switched vs Non-switched– Connection-oriented vs Connection-less– QoS

• VoIP– SIP: Session Initiation Protocol

� High level description� Message exchange� Call Feature Server / Session Agent and SIP-Client

– Voice over Internet• Public VoIP Network Architecture

– General Architecture– Two cases



The future of mobile communications is all about applications

Mobility, broadband, and new device technology change the way people connect and communicate

Communities, sharing

News, information anywhere

Navigation

Augmented reality

Business on the move, email

Location

New subscriptions and revenue is a huge opportunity

Music and entertainmentAnd voice is

just o

ne of them:

little bandwidth but w

ith explic

ite QoS-re

quirements


200k downloads in the first three weeks

Smartphone models increasing

Fast application cycles, a lot of developers

Customers hungry for the online experience+

Mobile networks will evolve from the current GSM/UMTS release 4 architecture towards LTE and EPC; this will enable the required bandwidths at the subscribers access; SIP-based VoIP-services will be introduced in the next years

Application optimised networks are in demandfor mobile broadband now

+

Fixed and Mobile services will come together and form a combined service offering (Fixed Mobile Conversion)

Fixed and Mobile networks will converged to one common architecture: IMS (IP Multimedia System); •one central session control function•shared application servers and subscriber database for authentication•different access technologies


15 Mar 30 Mar 15 Apr 30 Apr 15 May 30 May 15 Jun 30 Jun 15 Jul 30 Jul

NEW Smart devicePublished18 June ’09

The impact of NEW Device LaunchesS

igna

ling

Public VoIP-Service Infrastructure - induteq.nl voip service infrastructure 06... · Public...

Documents

Transcript of Public VoIP-Service Infrastructure - induteq.nl voip service infrastructure 06... · Public...