paulus djatmiko indonesia · evolution • tiltypical pl dpayload atiassumptions: – 33% of all...
TRANSCRIPT
Paulus Djatmiko
Indonesia
The BeginningThe Beginning
IP Network
l ffSignaling TrafficVoice/Video Traffic
The PromiseThe Promise
Increase
Increase your
Increase your capacity
revenue
Move your network
capacity
to IP
The PromiseThe Promise
Plug ‘n Play
Plug ‘n Play
•Any to Any Connectivity
•All you need is Eth t tEthernet port
Abundant CapacityAbundant Capacity
•10 Mbps•100 Mbps•1000 Mbps•1000 Mbps
Superior QualitySuperior Quality
•Latest voice codec
•Clear voiceQualityQuality •Clear voice experience
•Ethernet isCheapCheap
Ethernet is cheap
•Build in •Build in Resilient redundancy
•High availabilityredundancy
•High availability
Reality BitesReality BitesPlug n’ Pray Capacity? Quality really?Plug n’ Pray
Spanning Tree problems
Routing Loops problem
Capacity?
n x 100Mbps access
100 Mbps uplink?
Quality, really?
Delay & Jitter does not reflect quality
The Promise vs Reality Bites
Moving to IP is not a simple task
Additional efforts required to ensure smooth migration
Cheap
F i ti IP
Resilient. Period.
RedundantFor pre-existing IP infrastructure
Redundant.
Not.End.To.End.
Evolution: All The WayEvolution: All The Way
Core Core
IP IP ElementsElements
ElementsElements
People & People & ProcessProcessProcessProcess
Successful IP TransformationSuccessful IP Transformation
Evolution: IP Detail DesignEvolution: IP Detail Design
High Availability
High Availability
d dd d
AvailabilityAvailability
HighHighStandardizationStandardization High Performance
High Performance
Design C id i
Design C id iConsiderationsConsiderations
EvolutionEvolution
Standardization
• Standardize all aspects of deployment:of deployment:• Cabling• Naming conventionNaming convention• Hardware placement• Module insertion• Module insertion• Port allocations Parameter Name
Hardware Name cs-[site].[id]VLAN Description [subnet].[service]Interface Description [ip] [endpoint interface id]Interface Description [ip].[endpoint interface id]VRF Name VPN_[service]Cable Label [source port/hostname]-to-
[destination port/hostname]Patch Panel Label [Device id].[module]-[port]
EvolutionEvolution
High Availability
• Eliminate Single Point of Failure, early in the developmentdevelopment
• End‐to‐end redundancy• Link redundancy• Link redundancy• Chassis / box redundancy• Interface redundancyInterface redundancy• Software redundancy• People redundancy?p y
EvolutionEvolution20 Gigabit x 2
High Performance
• Calculate expected performance from all angles:angles:• Hardware capacity vs• “Real” hardware capacityReal hardware capacity• Link bandwidth vs• Uplink bandwidth
48‐port Ethernetp
• Payload codec being used• Expected user behaviour
Formula (Total MGW* 2G) * (outbound traff/inbound traff) + sig bw + oam bw + charging bw }
= --------------------------------------------------------------------------------------------------------------
0.75
EvolutionEvolution
T i l P l d A ti• Typical Payload Assumptions:– 33% of all subscriber simultaneously callsIn 2007 10% subscriber make calls over IP 2% of calls– In 2007, 10% subscriber make calls over IP, 2% of calls is video
– In 2008, 33% subscriber make calls over IP, 5% of callsIn 2008, 33% subscriber make calls over IP, 5% of calls is video
– In 2009, 67% subscriber make calls over IP, 10% of ll i idcalls is video
– In 2010, 100% subscriber make calls over IP, 20% of calls is videocalls is video
– Voice call bandwidth = 40kbps (AMR)– Video call bandwidth = 192kbps (H.264m codec)p ( )
EvolutionEvolution
b ib li ib ib li i d id h i dd id h i d
Typical Bandwidth per Service:
Subscriber ApplicationsSubscriber Applications Bandwidth RequiredBandwidth RequiredH.264m video call 192 kbps
AMR i ll 40 kbAMR voice call 40 kbps
GSM voice call over IP RAN‐O 53 kbps
Internet 500 ‐ 1 5 MbpsInternet .500 1.5 Mbps
VoIP 30Kbps‐100 Kbps
Interactive Gaming 128k ‐ 6 0 MbpsInteractive Gaming 128k 6.0 Mbps
Video on Demand 3.0 ‐ 6.0 Mbps
Broadcast TV (SD‐TV) 3.0 – 5.0 Mbps
HDTV MPEG‐4 6.0 – 7.0 Mbps
EvolutionEvolution
Graphic of Total Required Bandwidth: Voice andVideo
140
160
4 000 0
4,500.0
100
120
140
3,000.0
3,500.0
4,000.0
60
80
100
1 500 0
2,000.0
2,500.0Subscriber [million]
Subcriber Over IP [million]
Simul Call [million]
Voice+Video call [Gbps]
20
40
500.0
1,000.0
1,500.0
02006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017
-
Step By StepStep‐By‐Step
•Transform Signalling to IP• Transform Signalling to IPPhase 1 •Transform Signalling to IP• Transform Signalling to IPPhase 1
• Transform Voice Payload to IP• Transform Voice Payload to IPPhase 2 yyPhase 2
• Transform Video Payload to IP• Transform Video Payload to IPPhase 3
Transformation – Signaling Network (Current)
Tier 1(Legacy STP)
Tier 2(Legacy STP/
IP‐STP)
Tier 2(Legacy STP/
IP‐STP)IP STP) IP STP)
Transformation – Signaling Network (Step 1)
Tier 1(Legacy STP)
Tier 2(Legacy STP/
IP‐STP)
Tier 2(Legacy STP/
IP‐STP)IP STP) IP STP)
Transformation – Signaling Network (Step 2)
Tier 1(Legacy STP)
Tier 2(Legacy STP/
IP‐STP)
Tier 2(Legacy STP/
IP‐STP)IP STP) IP STP)
Transformation Voice/Video Traffic
Oth t
Transformation – Voice/Video Traffic
Other operators
Gateway MSC
MSCs
2G RAN
MGw
IP Core Network
IP Core Network
Transformation Voice/Video TrafficTransformation – Voice/Video Traffic
Oth tOther operators
Gateway MSC
MSCs
2G RAN
MGw
IP Core Network
Transformation Voice/Video TrafficTransformation – Voice/Video Traffic
Oth tOther operators
Gateway MSC
MSCs
2G RAN
T‐MGw
MGw
IP Core Network
Are We Done Yet?Are We Done Yet?
Delay JitterUser‐
perceived voice quality
Voucher Transaction Success Rate
Packet
voice quality Success Rate
h lPacket Loss Bandwidth Charging
Success RateSMS Delivery Queue Delay
KQIKQIKPIKPI VSVS KQIKQIKPIKPI VSVS
Mobile Telephony over IP Media RequirementsMobile Telephony over IP Media Requirements
C i Cl M bil T l h d t d Q litCarrier Class Mobile Telephony end‐to‐end Quality• Requires MOS => 4, R => 80
Latency• Mouth‐to‐ear delay must not exceed 400ms (<150ms preferred)
Jitter• Jitter must not add delay beyond allotment in overall delay budget
Packet loss• Dependent on codec, sample size(ms) and use of Packet Loss Concealment
(PLC) or Forward Error Correction (FEC)• GSM‐EFR ‐ 0% Packet loss to retain toll quality
• G.711 ‐ 0.5% Packet loss w/ PLC
ITU‐T G.108 Speech Quality Categories R‐value to MOS‐score correlation
Best90 100
R‐rating Quality Category
Very satisfied
User Satisfaction
4 3 4 5
MOS
Best
High
Medium
90 ‐ 100
80 ‐ 90
70 ‐ 80
Very satisfied
Satisfied
Some users dissatisfied
4.3 – 4.5
4.0 – 4.3
3.6 – 4.0Medium
Low
Poor
70 80
60 ‐ 70
50 ‐ 60
Some users dissatisfied
Many users dissatisfied
Nearly all users dissatisfied
3.6 4.0
3.1 – 3.6
2.6 – 3.1
‐0 ‐ 50 Not recommended 1 – 2.6
Computational vs Experienced Voice Quality metricsComputational vs Experienced Voice Quality metrics
Enhanced OSSEnhanced OSSAutomatic
Service Management LayerService Management LayerTroubleTicket
AutomaticTrouble Ticket
CreationProblem
Escalation
AlarmRoot Cause
EventCorrelation
Network Management LayerNetwork Management LayerFault and PerformanceFault and Performance
Completed Alarm Data
Performance data
C fiElement Management LayerElement Management Layer
End-pointsPerformance
BackboneP f
ConfigPolling
Network ElementsNetwork ElementsLayerLayer
Performance data SNMP
Fault trap
Performance data Inventory
Polling
F C A P SF‐C‐A‐P‐S
Ch M /f / Change Management / Accounting/ProvisioningAccounting/Provisioning
Configuration / InventoryInventory
Cisco ACSVisionael CiscoWorks Cisco ACSVisionael CiscoWorks
Cisco ISC
NGOSSNGOSSInitiativeInitiativeInitiativeInitiative
ConcordeHealthSMARTS Remedy
CiscoACS
SIEM
NetflowCollector
Availability / Capacity /
HP NNM
SecuritySecurity
SIEM Collector / NAM
ConcordTrafficy
FaultFaultp y /
PerformancePerformanceyy Traffic
Accountant
Success KeySuccess Key
Business Process Spare parts
Dedicated
Process
Performance Dedicated Personnel Parameter &
Security
Availability
Performance
Quality
Design and Topology
Monitoring Tools
Thank YouThank You