catt seminar on networks research polytechnic university march 27, 1999 next generation networks...
Post on 22-Dec-2015
214 views
TRANSCRIPT
CATT Seminar on Networks ResearchPolytechnic University
March 27, 1999Next Generation Networks
Richard D. Gitlin
Chief Technical Officerand
Data Networking Technology Vice President
Data Networking SystemsLucent Technologies
Next Generation Networks
• Introduction– The Network Revolution– Technology Trends– Applications and Requirements
• Issues and Solutions– Quality of Service– Security– Network Management– High Reliability– Intelligent Networking
• Example: Voice on the Next Generation Network• Summary
This R/Evolution Is Fueled By Unparalleled Customer Demand(and by telecom deregulation and the Internet)
It took about a century to install the world’s first 700 million phone lines; an additional 700 million lines will be deployed over the next 15-20 years
There are more than 200 million wireless subscribers in the world today; an additional 700 million more will be added over the next 15-20 years
There are more than 200 million Cable TV subscribers in the world today; an additional 300 million more will be added over the next 15-20 years
More than 100 million additional Internet users will come on-line by 2001 ---the Net is experiencing a 1000% per year growth! If this trend continues, by 2004 99% of the world’s bandwidth will be Net traffic ---including computer-to-computer communications.
1898 1918 1938 1958 1978 1998 2018
Cable
WirelessWireline
Global InternetUsers
1994 1998 2001
Average Hold Times
Internet Session20 - 30 minutes
Changing Traffic Patterns
Voice Call3 minutes
134M
250M
30M
Worldwide Access Lines
3B
2B
1B
Next Generation Networks (The New Public Network):Current situation
• No longer any debate that wide-area networks based on packet technology will emerge as a compelling alternative to the PSTN
• The new public network will be optimized for IP-based applications and will become the platform for future voice and data service innovations---it will not be based on merging existing legacy voice and data [frame relay, SMDS, IP, …] networks
• Carriers expect that the simpler new network will also reduce costs of operations, equipment and staff and will capitalize on the faster pace of networking element development
• Migration strategies, quality of service (QoS), network management, security, rapid service creation, and reliability are the major concerns of the carrier --as well as the almost $1 Trillion invested in the PSTN
• Almost 80% of the service providers intend to build their multiservice network with an ATM core and about 20% based on IP
• Some principles for the new network– Give customers access choices (DSL, cable, wireless, ISDN, …)– Work hard to optimize IP switching (DiffServ, MPLS, RSVP, ….)– Separate service intelligence from the network transport ---open interface
between intelligent call control features and packet gear– Build IP-based billing and management
A Networking Paradigm Shift Occurring (IP Becomes Dominant WAN and LAN Protocol) SeparateCircuit SwitchedNetwork
Separate Data Networks(Frame Relay, X.25, ATM,Router)
Single Network SupportingVoice & IP Endpoints
•Next-generation data networking –Excellent performance with IP–QoS breakthroughs: wire speed and per flow control–“Route once, switch often” Route at wire speed–Distance transparency and distributed “computing”–Policy driven network management–Directory Enabled–Broadband access–Wireless and optical networking–Silicon and software
•Data on voice (circuits) Voice on data (circuits)•“80/20” Enterprise/WAN data traffic split “20/80”•Networks Network of networks
More than moving voice over the Internet
• Converged, multi-service networks – reduce costs– provide integrated services
• Voice over cell/packet solutions -- VoATM and VoIP
• Virtual Private Networks -- VPNs
• Quality of Service -- QoS
• Accommodate multiple protocols (e.g., IP, ATM, frame relay)• Provide at least today’s voice services (e.g., 3-way connections, hold,
add, forward, toll free, 911) • Interoperate with one another, the Internet and the Public Switched
Telephone Network
“Convergence” Driving Change & QoS
The real challenge is to build converged networks that are as The real challenge is to build converged networks that are as reliable, robust and scalable as voice networksreliable, robust and scalable as voice networks
LEC
SS7
PSTNDB
IP DBs PSTNDB
LEC
SS7
IP IP
Media Gateways,Controllers
“IP” Network
Convergence of Communications Paradigms Leadsto New Services and Requires New Technologies
TelecommunicationsTelecommunications Connections
Tightly Coupled
Centralized Controls
HW Fault Tolerance
Features At Call Set-Up
Obsession With QoS
Low Latency
Data CommunicationsData Communications Connectionless
Loosely Coupled
Loose Controls,Distributed
SW Fault Tolerance
Features During ‘Session’
Little Attention To QoS
High Latency
•Voice over IP•Virtual Private Networks•E-Commerce
•Video & audio streaming, conferencing…multi-media•Mobile Access
•QoS: DiffServ, MPLS, QoS-aware Switches•Multi-Protocol Support: ATM (CBR,VBR,UBR, ABR), IP, IP Over FR/ATM•Multicasting
•Manageability & Intelligent Networking:Policy Driven Nets•Security•High Reliability•Scalability
Common Infrastructure
Applications
The Pace of Technology
Technology Trend
Silicon Chips X2 in density/speed every 18-24 months
Optics X2 in transmission capacity every year
Data/Web X2 Internet subscribers every 2-3 yearsX2 Internet hosts/servers every year
Wireless X1000 in capacity in 5 years
Power X2 MIPs/MW every 2 years (DSPs)
Compression X2 in information density every 5 years
Disruptive Technologies and their Impacton Networking
• Access: – Mbps (home) and Gbps (office) will substantially increase data traffic via xDSL, cable modems, wireless, and optics
• Semiconductors: Atomic-scale transistors will mean
- 64 Gb DRAM, 10 GHz processor clocks and giga-instructions/sec (GIPs)
- Heterogeneous and multi-protocol functions on a chip reduce power/cost
- wire speed processing in data networks
• Optical networking: WDM-fueled bandwidth explosion will
- trade bandwidth for network complexity
- lower risk with new networking solutions (e.g., IP WDM)
• Communications Software: Will spawn
- High performance databases/directories supporting advanced network features (e.g., policy servers)
- Speech recognition, media conversion (e.g., text-to-speech), and network agents to realize value-added intelligent networks
WAN
Enterprise 1IP
RF Access
Enterprise 2ATM
IP Access
IntegratedServices
Node
ATM Access
Cellular
xDSL
Fiber
Fiber
Fixed Wireless
Impact of Transmission Speeds on Networking
• Available WAN bandwidth has been less than LAN bandwidth --- this situation is expected to change at the millennium (WANs no longer a bottleneck for leading edge customers)
– Fiber optic transmission speeds have increased by 50% per year since 1980 (x100 in 10 years)
– LAN bandwidth has increased at 25% per year and WAN bandwidth has remained expensive (shared)
– “Available” curve purchased by leading-edge users (e.g., OC-3c); about 1% of WAN BW
1975 1980 1985 1990 1995 2000
LAN
Single Channel Fiber
Multi-Channel (WDM)
Available
T1
T3
OC-3c
Ethernet
Mbp
s
102
10
103
104
105
Fast Ethernet
Gigabit Ethernet
Impact of Speeds of Fiber Transmission and Microprocessors on Networking
• Speed gains for microprocessors have kept pace with fiber transmission speeds• The number of instructions available to process an optically transported packet,
using the “hottest” micro has remained constant
1975 1980 1985 1990 1995 2000
Microprocessor speed (Mhz)
Single Channel Fiber
Multi-Channel (WDM)
Pentium II
Merced
PowerPC
486
386286
Mbp
s or
Mhz
102
10
103
104
105
Pentium III
Single Channel Fiber
Impact of DRAM Memory Size and Transmission Speeds on Networking• With increasing transmission speeds, more packets are “in flight” for a given round trip
propagation time; common error recovery protocols require that one round trip worth of data be stored
• e.g., NY-LA-NY round trip propagation time of 50 ms results in 1 MB for a 155 Mbps link
• Size of DRAM increasing 58% per year
– Effective BW of memory is increasing at about 40%
• Storage capacity and transmission speeds are increasing at the same rate, thus number of chips to hold one “window” of data has remained constant
1975 1980 1985 1990 1995 2000
DRAM Size
Multi-Channel (WDM)
256 MB
64 MB
16 MB
4 MB
Mbp
s or
kB
102
10
103
104
105
106
Much More Traffic (leads to much moretraffic --- Metcalfe’s Law)
Metcalfe’s Law: the value of a network grows exponentiallyMetcalfe’s Law: the value of a network grows exponentially with the numberwith the number ofof users users and connected sources and a “network of networks” becomes the organizing and connected sources and a “network of networks” becomes the organizing
principle for most communicationsprinciple for most communications
US Businesses WAN Peak Capacity Will Need to Increase at Least 10X in Three Years
0.0
1.0
2.0
3.0
4.0
5.0
1997 1998 1999 2000
Tb/sec
Source: Estimated from projections of data port shipments (Dataquest, 12//97) 56 Billion
Year 20003 Year Growth of
Email Messages
Source: email projections: [Yankee Group]
3.5 Billion1997
Major Requirements for Next Generation Network Applications
QoS HighReliability
NetworkManagement
Security IntelligentNetworking
VoIP
E-Commerce
Multi-Media
Multi-casting
MobileAccess
ValueAdded
Services
VPN
•QoS and security for successful convergence•Virtual Private Networks for converged networks and QoS•Network management directories, policies and intelligent agents for decision support, configuration and QoS
Applications will require:
The Leading Protocols for Transporting Information on Next Generation Networks Are ATM and IP
*Related Items
ATM IP
Speed High to Very High Low to Very High
ConnectionType
Connection-Oriented Connectionless-Oriented Subset of traffic will be connection-oriented (e.g.,
MPLS Explicit Route)
QoS Yes (4-5 Services) Emerging (e.g., DiffServ, IntServ)
PredominantDeployment
Core Networks Access Networks (Multi-service)
To desk top Internet, Corporate LANs Corporate networks emerging
TransmissionEfficiency
High for voice/video Low for data*
Low for voice/video High for data
TransmissionUnit
*Short, fixed-length packets (cells) Variable-length packets
DataApplications
Originally designed for real-timevoice
Evolving to all applications (e.g.,multimedia)
Originally designed for TCP, FTP, … less timecritical applications
Evolving to all applications (eg, multimedia)
Cost Economies of scale favor IP
Issues to Be Solved for Next Generation Networks: QoS
Issues Approaches
QoS
Guarantees beyond Availability Dial Access Blocking Maximum Delay & Jitter Minimum Effective Bandwidth
Allocation of dial ports per VPN or service Static (SLAs) & Dynamic (RSVP) QoS
Requests Resource reservation (provisioning,
MPLS explicit paths, RSVP) Use of QoS aware network elements
Guarantees Individualized SLAs by Class of Service (Application) Customer or groups of
customers (VPN) Flow or connection
Differentiated Services Integrated Services Classification, large multi-priority buffer
pools and buffer management Edge vs Core congestion control Policing , shaping, marking
Application & SourcePerformance Issues(e.g., Latency, Jitter)
Reduction of large frequentlyencountered latency andresponse time
Efficiency of network traffic
Caching Network and Server Load Balancing Efficient Multicasting Mirroring Firewall/Proxy Server Farms Private Peering Agreements
How Will IP Networks Approach the Performance of ATM Networks?
• Implementing wire speed switches
• Decreasing effect of IP packet variability and header size with transmission of higher speeds
• Selecting good designs and paths with VPN Designer expert system
• Making IP connection oriented via MPLS, per flow queueing
• Implementing QoS infrastructure akin to PNNI
• Using policies and directories to enable QoS
• Exploiting ASICS for congestion control directly on flows
• Executing congestion control within core instead of at edge
SLA
ReliabilityBlocking
DynamicSLA
ReliabilityBlockingLatency
JitterLoss
The Past The Future
Next Generation Switches
• Wire speed traffic classification and filtering
– No performance degradation when filtering or QoS is switched on• Complete traffic isolation:
– Can meet Service Level Agreements without the need for over-provisioning• Guaranteed minimum bandwidth based on source address, destination address, protocol
and/or TCP/UDP port numbers• Hierarchical Weighted Fair Queuing
Site 2
Site 3
VPNDesigner (Central)
Site 1
SLAs
ATM Switch
LSR
LSRLSR
LSR
LSR
LSR
VPNDesigner
(Distributed)
VPNManager System
(Distributed)
Label SwitchingRouter
00.10.20.30.40.50.60.70.80.9
1
45(T3)
150(OC-3)
600(OC-12)
SPEED MBPS
IP R
EL
AT
IVE
TO
AT
M
Situation•Large IP packets cause longer delays than short ATM packets•Variable IP packets create more jitter than fixed ATM packets•20 Byte IP header causes less economic efficiency than 5 Byte ATM header
(Voice over ATM)
Decreasing Effect of IP Packet Variability and Header Size (Example Application: Voice over ATM vs. Voice over IP)
Natural Solution•IP Performance and Economics Comparable at Speeds beyond OC-12
Allows QoS path optimizationSLAs are easy to implement.Facilitates identifying individual flowsCan be used with IP, ATM, SONET, WDM, ...Supports multi-vendor environmentsComplements Enterprise need for tunnels
Will require building QoS capabilities into OSPF, LDP, RSVP protocols
Make IP Connection Oriented via MPLS...
•Determine and Propagate Enterprise & Network Topology•Translate SLAs for configuration•Determine QoS Paths•Set up ATM VC or MPLS Label Switched paths•Classifies incoming traffic (IP header, port,DS byte)•Forward/route traffic based on forwarding/routing table
•Translate SLAs for Configuration•Determine QoS Paths
Site 2
Site 3
VPNDesigner (Central)
Site 1
SLAs
ATM Switch
LSR
LSRLSR
LSR
LSR
LSR
VPNDesigner
(Distributed)
VPNManager System
(Distributed)
Label SwitchingRouter
IP With MPLS and IP Over ATM For IP QoS Guarantees
IP (MPLS ERLSP*) ATM
Path Definition End-End, Explicit End-End, ExplicitSwitching Level 2 or 2.5 Level 2 or 2.5
QoS Signaling Dynamically Inferredfrom IP or MPLS Header
PVC: StatisticallyConfigured DuringProvisioningSVC: DynamicallyNegotiated at Call SetUp
QoS Control MPLS, DS Byte ATM Adaptation Layer n
Path Set Up LDP, RSVP+ PNNI
Optimum PathDetermination
Off Line; Provisioned inEdge Label SwitchedRouter
PVC: Off Line;Provisioned in ATM Sw.SVC: Dynamic; DuringCall Set Up
Path Re-RoutingAround Failures
Manual; Can beAutomated via NetworkManagement
Dynamic; AutoDetection for ExistingPVCs and new PVCs orSVCs
*ERLSP=Explicitly Routed Label Switched Path
0
10
20
30
40
50
60
70
0 0.1 0.2 0.3 0.4 0.5Utilization of VPN1
Max
imu
m d
elay
in
ms
VPN1
VPN2
0
10
20
30
40
50
60
70
0 0.1 0.2 0.3 0.4 0.5
Utilization of VPN1
Max
imu
m d
elay
in
ms
VPN 1 (without flow isolation)
VPN 1(with flow isolation)
Both at same priority with no discriminationBoth at same priority with routers using flow isolation ( by VPN) and equal weights for the two VPNs
Benefit of Isolating Flows Price of Not Isolating Flows
Congestion Control of Bad Behavers:Value of Isolating Flows in QoS Management
VPN1 And VPN2 Have The Same Contract ( 0.4 of the DS1 capacity)VPN2 uses 0.52 of the capacity (i.e., 30% more than contract)
•Without flow isolation, all VPNs get unacceptable delay when one creates congestion•With flow isolation, all well behaving VPNs get acceptable delay•With flow isolation, misbehaving VPNs can get acceptable delay only when other VPNs well below contracted load
Reducing Latency: Web Access
With Next Generation Caching www.lucent.com
Client
www.cnnfn.com www.yahoo.com
L4RequestTrap
httpLoad Balance Requests
Router
PULL
Multicast
Request Reply
Request
SolutionPrinciple:Move content closer to users – much lower web access latency – reduced network congestion – higher content availability
Next Steps – pre-fetch “hot” objects – multicast to cache sites – load balance cache sites – high level trap of cache request – support “streaming” multimedia – cache dynamic content – support value-added services
CentralCache Control
CacheSites
Current Situation•High End-to-end latency•High Network load•High Server load•High Cost for ISP and Enterprise
Deploy cache sites in: --- NAP --- Backbone network --- Data center --- ISP --- POP --- Enterprise
CoreNetwork
DataSource
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
MulticastCooperativeServer
MulticastGroup
MulticastGroup
MulticastGroup
MulticastCooperativeServer
CoreNetwork
DataSource
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
DataReceiver
Reducing Latency With Multicasting
Solution: Reduced Latency via•Reduced traffic on core network•Reduced load at data source server•Data closer to receivers•Combination with caching and replication
Obstacles to Overcome•Lack of unique set of protocols•Data synchronization•Reliability, Recovery from lost data•Current implementations too static
Current Situation•Redundant traffic causing needless loading of network and servers•Results in unacceptable latency
Issues to be solved for Next Generation Networks: Security
Security Issues Approaches
Confidentiality Authentication Access Control Audit
Unauthorized network access Inappropriate access to network
resources Disclosure of data Unauthorized modification to
data and software Disclosure of network traffic Spoofing of network traffic Disruption of network functions
Security policies Access control list policies: role based,
discretionary, mandatory (e.g.,RADIUS/DIAMETER Servers)
Authenticate via challenge-response,voice-,fingerprint, fixed signature...
Tunneling to move authentication fromaccess provider to destination enterprise
Intrusion detection: Prevent, active, trap
Integrity
Ensure information cannot bemodified by Intential tampering Human error Diaster events
Firewalls Encryption, Public Key Infrastructure
(PKI), Certificate Authorities Tunneling: IPSec, L2TP, PPTP VPNs and IPSec compliant VPNs Network Address Translation (NAT)
Availability
Prevent resources from beingdepleted or becominginaccessible when needed Protection from abusive
sources (e.g., mail spam) Denial of service attacks
ICSA Certification Automatic network device discovery Incident trap and response capability Data integrity/validation & audit controls System redundancy and high availability
General
Endpoints with non-registered IPaddresses over a globally routedpublic network will not be routedor will cause confusion
Allow users to use non-IPprotocols (e.g. IPX, AppleTalk)over an IP network
NAT at the interfaces between theenterprise and the public network
End-end tunneling hides addressing andlegacy protocols (MPLS, IP-in-IP)
Service provider tunnels mask addresses Virtual Routers to handle multiple
customers’ private addressing
Requirements for Access to VPNs
VPN Requirements• Private Addressing: to allow access to corporate network resources (Tunneling and
Network Address Translation)• Security: authentication of users and privacy of user data as it goes over the network
(RADIUS/DIAMETER, Tunneling)• Legacy Protocols: allow user to use non-IP protocols (e.g. IPX, AppleTalk) over an IP
network (Tunneling)• Performance: provide a level of performance comparable to that of private networks (QoS)• Network Management: provide customer management of the VPN (monitoring,
reconfiguration,..)
Issue: Tunneling addresses many VPN requirements but makes QoS more difficult since flow information becomes hidden in the core
InternetIPsec
RASAuthentication
Server
ISP
LNS
ISP
AuthenticationServer
CertificateServer
RADIUS
PPP/L2TP
PPPRAS
RRRR
IPSec
CertificateAuthority Internet
Dial: Telecommuters and remote office access to a corporate site
Dedicated: Branch office access to a corporate site
Evolving Tunneling Options
Benefits Disadvantages
IP-IP
Hides native IP packet Supports private addressing Can handle “special” routing situations
Mainly manual tunnel set up Basic tunnel features Easy to spoof
IPsec
Industry security standard Powerful authentication and encryption
protocols protect integrity and confidentiality Works with variety of encryption methods Has tunneling mode (IP-IP benefits) Certificate Authority provides scalable
framework for key distribution and management
Expect service providers tooffer soon
Packets within tunnel can getQoS in backbone based onsource/destination addressand Type of Service
L2TP
Industry Layer 2 tunneling standard IP-IP benefits plus can carry non-IP protocols Can extend PPP end-point from Service provider
RAS to enterprise router. Allows User authentication by corporate RADIUS server Private address assignment to user by corporate server
Additional overhead All packets within tunnel getsame QoS treatment bybackbone network elements
Expect service providers tooffer soon
L2TP
RAS/LAC
RAS/Router
Router/LNS Firewall
RADIUSServer
ISPBackbone
Host
USER SERVICE PROVIDER CORPORATE NETWORK
PC
IPsec
RAS = Remote Access Server (modem pool)LAC = L2TP Access ClientLNS = L2TP Network Server
LEC
IP-IP
Issues to Be Solved for Next Generation Networks: Network Management
Issues Approaches Complex networks with many
services lack data coordination &integration
Introduce directories intomanagement process
NetworkManagement
Each device is statically managed andhas its own related data
Demand for service management in aworld of device management today.
Introduce integration of servicemanagement and related dataintegration
Need for offer policies (e.g., VPN) inconjunction with technology policies(e.g., QoS)
Integrate QoS, Route, Security…servers
Need for more dynamic and timelymanagement of network
Make policy management reactive tonetwork conditions as well asprescriptive.
Expert system control of provisioningparameters and server policies
Current paradigm has following problems:•Individual Device management•Device Manager per vendor•Device Manager per product•No unified configuration store•Network Manager and Device have Client-Server model and are not peers
Historical Network Management/Policy Paradigm
Device Manager (NMS)
Data store
Network Device
Agent
NVRAMNetwork Device
Agent
NVRAM
SNMP
DeviceManager (2)
Data store
Network Device
Agent
NVRAM
Evolving to Next Generation Network ManagementCurrent Situation•Independent device andindependent servicesmanagement•Table-driven device functions•Client(NM)-Server(Device) architecture•SNMP
The Future•Distributed policymanagement•Integrated servicesthrough policies•Reactive agents added•Complex & reactivepolicy capabilities
Near Term•Directories drive dataunification•Central policy managementon service basis•Dynamic device functions•Policy agents added
Network DeviceNetwork Device
Radius
DNS/DHCP
Network Management
Network Device
Policy Administration
Policy Support Services
(VPN Designer)
PolicyDistribution
Network Device
Radius
DNS/DHCP
LDAP
Network Management
COPSTechnology
SpecificConfigurations
TechnologyPolicyServers
BusinessPolicyServersSNMP
Complex Networks and New Dynamic Services DriveChanges to Policy Management and Infrastructure
Software
DeviceManagement
NetworkManagement
PolicyManagement
Monitoring
Static FilterTables
UnifiedConfiguratio
n
Dynamically Updated Filter Tables
CentralizedPolicy
Management
Reactive Policy Agents
DistributedPolicy Management
ProceduralPolicy Agents
Devices
Self-healingNetworks
UnmanagedNetworks
Solutions•Technology Policy Service Policy•Protocol Based Management Tables Common Information Model•Configuration Policy Management•Provisioned Dynamic Reactive Policy
Issues•Management is device configuration; needs to be offer & service related•Associated data is per device per vendor and largely in tables; needs to be integrated and for the offer or service•Data inconsistency and synchronization problems since data repeated for devices•Management rules need to respond to changes in network conditions
Meta Directory Solution•All directory changes are arbitrated through the Meta-Directory• Meta-Directory maintains consistency between information in each physical directory/database
– Appearance of a single directory to Network Manager–Single entry link to other directories
Meta-Directory Is A Band-aid •Does not resolve any overlapping schema issues
Meta-Directory
Directory Evolution: Near Future
NetworkDevice
LDAP
Directory
Datastore
Directory
Datastore
Directory
Datastore
AddressPolicyServer
QoSPolicyServer
COPSDHCP
DirectoryManagement
Interface
Solution•Policy scripts
– Distributed by Policy Server– Interpreted by Network Devices– Alternative to COPS/DIAMETER
• Network Device uses Directory for configuration
• Policy Server uses Directory for decision support and policy storage
• Policy Server and Directory Access Client both manipulate device data structures
Network Management (The Future): Supporting Complex and Reactive Policies
Network Device
PolicyPolicyInterpreterInterpreter
andandProcessorProcessor
DirectoryAccessClient
RTOSFilter
TablesConfigData PolicyPolicy
ServerServer
DirectoryAccessClient
PolicyPolicyManagerManager
(PIP)(PIP)
Directory
DecisionSupport
Info
Distribution
LDAP
Management &Management &Decision SupportDecision Support
ConfigurationActivities
Policies Are Represented as Scripts
Example Voice over IP Application:What is Required to Support VoIP With QoS?
Voice over IP (VoIP) Architecture Requirements
• Today’s products do not scale well. Need to separate signaling from media transport and control for large scalable networks
– Media Gateways ~ 1000’s
– Media Gateway Controllers/Gate Keepers ~ 10’s,
– Signaling Gateways < 10
• Today’s solutions do not interface with value added feature data bases or Signaling Control Points (SCPs). Voice feature support requires interaction with existing and future SCPs such as
– Local Number Portability (LNP), 800, SDN, ...
• VoIP is growing much faster than multimedia over IP. Thus, focus on voice protocol simplification first.
• Commercial Success of VoIP (including VPNs) will require QoS
– Call Admission
– Media Transport
Near Term Evolution of VoIP Architecture:Functional View
* Proposed ProtocolH.323+ = H.225+ & H.245H.323++ = H.225+, H.245 & Annex G
Challenges (Mainly Due to Number of Devices)
•Call Set Up Time•Reliability•Voice Quality
•QoS Guarantees•Network Management•Cost/Minute
SS7
TBD
MGCP/MDCP/H.gcp*
T1,PRI
RTP/UDP/IP,Ethernet
H.323+,SIP
TCAP/SS7
LDAP/IP* ,RADIUS
H.323++/SIP+
TCAP/IP
MediaGateway
New VoIPData Bases,Servers
Existing VoiceFeature Servers• User Authentication.
• Accounting• Routing
New VoIPData Bases,Servers
Existing VoiceFeature Servers
• Local Number Portability• SDN• 800
SignalingGateway
Media GWController
MediaGateway
SignalingGateway
Media GWController
GateKeeper
GateKeeper
ER ER
LEC
SS7Net
LEC
SS7Net
Voice Circuitto
IP Connection
Voice Circuitto
IP Connection
D-ChannelSignaling
Translation
D-ChannelSignaling
TranslationCallControl
Functions
CallControl
Functions
GatewaysBetweenDomains
“IP” Network
CAC=Call/Connection Admission ControlDS=DiffServ Byte in IP Header
802.1p
802.1p
DS DS
802.1p
DS
CAC
CAC
CAC
“IP” Network
LEC
SS7
LEC
SS7
DSMedia
GatewayMedia
Gateway
SignalingGateway Signaling
Gateway
Media GWController
Media GWController
GateKeeper
GateKeeper
QoS Policy,Manager
Requirements for Future QoS VoIP Architecture•QoS Aware Network Elements•QoS Protocols
•MPLS, RSVP, LDP in IP Network•802.1p on Ethernet LANs•DiffServ on IP
•Call/Connection Admission Control•QoS Policy•QoS Network Management
Summary: What to Expect in Transition tothe Next Generation Network
• Data applications dominate network traffic– Multimedia, collaborative systems have increased acceptance– Network driven to data networking solution– Data network must also support voice applications and– Must interwork with Public Switched Telephone Network (PSTN)
• Rapid new technology decreases cost; increases capabilities
• Network is packet based– Packet voice technology widely utilized
• Need to provide QoS, Security, Network Management …
• Intelligent, wire speed, QoS enabled switching elements for better efficiency and control
• Data networks achieve reliability comparable to voice networks
• Vendors provide solutions that
– work in heterogeneous, multi-vendor environments
– allow rapid introduction of new services
– allow customers to provide service differentiation