8/12/2019 QoS Requirements for VoIP
1/95
Copyright 2010 GISFI. All Rights Reserved.
QoS Requirements for VoLTE
Dr. Parag Pruthi NIKSUN
Dr. Ashutosh Dutta NIKSUN
Date: June 18-20, 2012
8/12/2019 QoS Requirements for VoIP
2/95
Voice over LTE
8/12/2019 QoS Requirements for VoIP
3/95
HSS
AAA
PGWMME
PCRF
SGW
SGSN10
11 114
3
5
8
7
+6
2
2
2
1
6
Non-LTE Access
Monitoring traffic at
control and user planes
Monitoring tunnels and
pair performance
Correlating traffic tomobile device
Handover and roaming
Registration/AdmissionControl on AAA server
IP multimedia services
Data Center/IMS
Mobile CORE/EPC
Access & backhaul
SGW SGW
MME
I/S-CSCF
1
3G Access
RNC
P-CSCF
LTE - Deployment Scenario
8/12/2019 QoS Requirements for VoIP
4/95
QoE => Perceived Quality of Service
Network Metrics
Bit rate, delay, jitter, packet loss rate (PLR)
Power consumption
Application Metrics
Call setup delay, Call setup success rate
Failed calls, dropped calls, retransmission
MOS (Mean Opinion Score)
Determining factors Network Characteristics (Lossy link, low bandwidth, heterogeneous
network)
Application Characteristics (Real time, Non-real-time)
User mobility (cell mobility, subnet mobility) Several standards groups
ITU-T SG12, ITU X.902 (IP Telephony)
IETF IPPM, DIFFSERV
3GPP 3GPP TS 32.409 (IMS performance)
QoE Metrics
Slide 4 GISFI
8/12/2019 QoS Requirements for VoIP
5/95
Multilayer QoE in VoLTE Network
IP CANCaller
(UE1)
diameter
SIP
GETS Call
HSS
GETS-Application
Server
P-CSCF
I-CSCF
S-CSCF
PCRFPCRF
P-CSCF
S-CSCF
InviteOK
ACK
Called(UE2)
Managed IP
(Multi-Provider Network)
(EPC)
DNS/ENUM
DNS
RTP
Layer 3 control
Wireless
Access
UMTS
EvDO
WiMAX
LTE
Satellite
Wireline
Access
Cable
DSL
Fiber
Ethernet
Wireline
Access
Cable
DSL
Fiber
Ethernet
Wireless
Access
UMTS
EvDO
WiMAX
LTE
Satellite
IMS
RAN
GW
GW
RAN
RAN IP CAN
5
IMS-layer control
5
Layer 2 control
Monitoring
Agent
Multi-layerSON
Controller
Network/
Application
Feedback
RAN
8/12/2019 QoS Requirements for VoIP
6/95
QoE is driven by measurementsWhich layer, which application, how often
Require Multi-timescale Measurements
Require Multi-Layer Measurements
Network layer, application layer
Require Session-based Measurements
E.g., SIP-based multimedia application
Require DPI for Application Classification
Classification and Marking
Policing and Markdown
Queuing and Dropping
QoE Requirements
Slide 6 GISFI
8/12/2019 QoS Requirements for VoIP
7/95
Require mechanisms to provide priority services forsignaling and transport of voice services in case ofemergency.
e.g., SIP signaling for VoIP use Resource Priority Header(RPH)
e.g., Diffserv mechanisms to take care of associated media(e.g., RTP) traffic.
QoS measurements should consider KPIs at severallayers including
Data link Layer MAC layer retransmission
Network Layer - thruput, goodput, network delay, network
retransmission, utilization, packet loss, jitter Transport Layer - TCP connections and RTT
Application layers Set up delay, dropped calls, failed calls,retransmission of INVITEs
QoE Requirements
Slide 7 GISFI
8/12/2019 QoS Requirements for VoIP
8/95
Future NGN application requires cross-layer feedback inorder to provide desired QoS during handover and due tobandwidth fluctuation
IEEE 802.21
Interoperability with Mobility protocols
SIP, Mobile IP, Mobile IPv6Tightly coupled or loosely coupled
Require correlation between signaling and media (e.g., EPC and IMS)
Require Open API to dynamically control the networkelement in the network
QoE Requirements
Slide 8 GISFI
8/12/2019 QoS Requirements for VoIP
9/95
Slide 9
EPC Network Layer KPIs (Sample)
AAA & RoamingAAA & RoamingScenariosScenarios
(S6a)(S6a)
BearerBearer
(S11, S1(S11, S1--MME)MME)
SessionsSessions
(S5, S8, S1(S5, S8, S1--U)U)
ApplicationApplicationPerformancePerformance
(SGi)(SGi)
II--RAT Handover,RAT Handover,RoamingRoaming
(X2, S10, S3, S4)(X2, S10, S3, S4)
eNB
eNBeNB
MME
PDN-
GW
UE
SGSN
E-UTRAN
IP-based
IMS
network
ePDG
Untrusted
Non-3GPP
(WiFI,
WiMAX)
HSS PCRF
SGi
S5
S11
S1-U
S1-MME
S4
S7
S6a
S3
S2a
S2b
AAA
S6c
Wm
Wn
Rx+
Wx
X2
UE
X2
S8
UTRAN
Serving
Gateway
(S-GW)
UE
UEUE UE
X2
PerformancePerformance
ResponseResponse timetime
UtilizationUtilization
Successes/FailuresSuccesses/Failures
Application profilingApplication profiling
Bearer setup latencyBearer setup latency
Residence timeResidence time
SecuritySecurity
Unauthorized trafficUnauthorized traffic
Restricted appsRestricted apps
Excessive trafficExcessive traffic Denial of ServiceDenial of Service
TrackingTracking
AuthenticationAuthentication
Basic KPIsBasic KPIsAdvanced KPIsAdvanced KPIs
S10
8/12/2019 QoS Requirements for VoIP
10/95
Slide 10
S1-U Load Profile
8/12/2019 QoS Requirements for VoIP
11/95
Slide 11
Session Counts
8/12/2019 QoS Requirements for VoIP
12/95
Slide 12
Mean Bearer Setup time
8/12/2019 QoS Requirements for VoIP
13/95
Slide 13
S11 Response Time
8/12/2019 QoS Requirements for VoIP
14/95
Real-time Enterprise Dashboard LTE(Performance)
8/12/2019 QoS Requirements for VoIP
15/95
Real-time Dashboard - LTE (Security)
8/12/2019 QoS Requirements for VoIP
16/95
Slide 16
LTE Analysis
8/12/2019 QoS Requirements for VoIP
17/95
8/12/2019 QoS Requirements for VoIP
18/95
Slide 18
IMS KPI Analysis SIP Methods
8/12/2019 QoS Requirements for VoIP
19/95
Slide 19
IMS Registration Metrics
8/12/2019 QoS Requirements for VoIP
20/95
Slide 20
IMS KPI Top Methods
8/12/2019 QoS Requirements for VoIP
21/95
Slide 21
IMS Top Talkers
8/12/2019 QoS Requirements for VoIP
22/95
Security: Unauthenticated Registrations
8/12/2019 QoS Requirements for VoIP
23/95
Slide 23
Top NAIs Unauthenticated Registrations
Top NAIs AuthenticationFailures
8/12/2019 QoS Requirements for VoIP
24/95
Real-time Enterprise Dashboard IMS (Security)
8/12/2019 QoS Requirements for VoIP
25/95
Real-time Enterprise Dashboard IMS (Performance)
8/12/2019 QoS Requirements for VoIP
26/95
KPIs for RTP (Real TimeTransport Protocol)
8/12/2019 QoS Requirements for VoIP
27/95
KPIs for RTP
(.38)
8/12/2019 QoS Requirements for VoIP
28/95
KPIs for RTP (cont.)
.
.
, .. , .323,
/, , , .38, .
8/12/2019 QoS Requirements for VoIP
29/95
KPIs RTP (contd.)
(.38)
( )
8/12/2019 QoS Requirements for VoIP
30/95
KPIs for IMS (IP MultimediaSubsystem)
8/12/2019 QoS Requirements for VoIP
31/95
KPI NAMES DESCRIPTION LOGICALFORMULA
WHYINTERESTING?
INTERFACE
List of all SIPmethods
SIP messageflows with
same Call-ID
Shows the list allSIP messages.
Basicfunctionality for
session view.
Gm
Aggregate IMSsignalingpackets
Sums all themethods andresponses.
Ratio of totalcount and all IMSmessages
Dos Attack Gm
Aggregate total
attempted initialregistration b/wUEs and P-CSCF
Total number of
registrations
Sum of all SIP
Registers from allUE to PCSCF
System Load
indication, VZWReq, Dos Attack
Gm
Aggregate
successfulinitialregistration b/wUE & CSCF
Count the
successfulregistrations ofUEs.
Count 200 Ok in
response toRegister fromPCSCF.
Informative Gm
8/12/2019 QoS Requirements for VoIP
32/95
8/12/2019 QoS Requirements for VoIP
33/95
Aggregatetotalattempted re-registrationbetween UE &
P-CSCF
Registers withpreviouslyseen Call-IDs.
Counts the totalnumber of re-registered IDs.
SystemLoadIndication
Gm
Aggregatesuccessful re-registrationbetween UE &
P-CSCF
Registers withpreviously seenCall-IDs.
Counts the totalnumber of 200 Oks to
Informative Gm
AggregateFailed re-registrationbetween UE &
P-CSCF
SIP 4xx errorsin response toregistrationrequest.
Count SIP 4XX errors Passwordguessingattack
Gm
Mean IMS re-registration set-up time.
Time to set-upthe registration
Time between registerand 200 OK
Systemperformanceindication
Gm
8/12/2019 QoS Requirements for VoIP
34/95
Aggregate Failedre-authenticationbetween UE & P-CSCF
Calculate thefailed numberof re-authentication.
Count SIP 401errors inresponse toRegister
TotalunauthenticatedREGs
Gm
Aggregate
unauthenticatedre-registrationbetween UE & P-CSCF
Total number of
unauthenticatedregistrations.
Count re-register
msgs withoutnonces that get200 without 401challenges
Security risk,
allowsimpersonationattack
Gm
Aggregatesuccessful de-registrationbetween UE & P-CSCF
Successful de-registrations.
Count Registerwith expiry==0 orcontact: expiry==0
System loadindication
Gm
Aggregate Failedde-registration
between UE&PCSCF
All the failed de-registration.
Count SIP 4XXerrors in response
to above register.
Informative Gm
8/12/2019 QoS Requirements for VoIP
35/95
Aggregate totalattempted de-registration b/wUE & PCSCF
Total ofattempted de-registration
SIP Passwordguessing attack
Gm
Mean IMS de-registration time
Mean of de-registration time
Mean of the time. Systemperformanceindication
Gm
Aggregate failedauthentication forde-registration
Total number offailedauthentication
de-registrations
Count SIP 401errors in responseto register
TotalunauthenticatedREGs
Gm
Aggregateunauthenticatedde-registration
Total number ofunauthenticatedde-registration
Count de registermsgs with 200 andwithout 401challenges.
Security risk, allowsimpersonation
Gm
Attempted sessionestablishments
How manyattempts havebeen made toestablish thesession.
#initial Invitesessions with#INV==1
System loadindication, VZWreq.
Gm
8/12/2019 QoS Requirements for VoIP
36/95
Successfulsessionestablishments
Tracking allsuccessfulsessions wehave.
Count #180ringing, not #200OK, when#INV==1
System loadindication
Gm
Answered sessionestablishment
Tracking allsuccessfulansweredsessions wehave.
Count #2XXringing, should be200 but 2XX is finewhen #INV==1
System loadindication
Gm
Failed session
establishments
All the failed
sessionestablishments.
Count 4XX
messages
System
performanceindication
Gm
Mean time forsuccessful sessionestablishment
Time taken tohave a successin establishment.
Time b/w INVITEand 180 response.
Systemperformanceindication
Gm
Attempted sessionre-establishment.
Number ofattempts to havere-establishedsession
#INVITE where a180 has alreadybeen seen, or#INV > 1
System tuning aid Gm
8/12/2019 QoS Requirements for VoIP
37/95
8/12/2019 QoS Requirements for VoIP
38/95
8/12/2019 QoS Requirements for VoIP
39/95
8/12/2019 QoS Requirements for VoIP
40/95
NAIs of top 5receivers of IMSsignaling traffic
Display associatedpackets, bytes,exclude CSCF asreceiver.
To: and#bytes
System loadindication
Gm
NAIs of top 5senders of Instantmessages
Display associatedpackets, bytes,exclude CSCF asoriginator.
#bytes System loadindication, Dosattack
Gm
NAIs of top 5
receivers of 4XXerrors
Display associated
packets, bytes,exclude CSCF asreceiver.
#bytes System load
indication
Gm
Top 5 visited n/wIDs in IMS
signaling traffic
Display associatedpackets and bytes
#bytes System loadindication
Gm
Top 5 access n/wInfos in IMSsignaling traffic
Display associatedpackets and bytes
#bytes System loadindication
Gm
8/12/2019 QoS Requirements for VoIP
41/95
Top 5 senderdomains in IMSsignaling traffic
Display associatedpackets and bytes
#bytes System loadindication
Gm
Receiver domains
in IMS signalingtraffic
Display associated
packets and bytes
#bytes System load
indication
Gm
NAI of top 5originators ofregister request
Display associatedpackets ,bytesexclude CSCF as
originator(PCSCF
callee)
#bytes System loadindication
Gm
NAI of top 5originators ofINVITE request
Display associatedpackets ,bytesexclude CSCF asoriginator
#bytes System loadindication
Gm
NAI of top 5originators ofINSTANTmessage request
Display associatedpackets ,bytesexclude CSCF asoriginator(DUP)
#bytes System loadindication
Gm
8/12/2019 QoS Requirements for VoIP
42/95
NAI of top 5 originatorsof subscribe requests
Display associatedpackets ,bytes excludeCSCF as originator
#bytes Systemloadindication
Gm
IP Addresses of top 5originators of register
requests
Display associatedpackets, bytes exclude
PCSCF as originator.
#bytes System loadindication
Gm
IP Addresses of top 5originators of INVITErequests
Display associatedpackets, bytes excludePCSCF as originator.
#bytes System loadindication
Gm
IP Addresses of top 5originators of INSTANTmessage requests
Display associatedpackets, bytes excludePCSCF as originator.
#bytes System loadindication
Gm
IP Addresses of top 5originators of subscriberequests
Display associatedpackets, bytes excludePCSCF as originator.
#bytes System loadindication
Gm
Top methods & responsetypes sent. Drill down tosend UE.
Calculate the number ofUEs
Rateand totalcountsfor UE
Informative Gm
8/12/2019 QoS Requirements for VoIP
43/95
Network Layer KPIs FOR LTE (EPC)
8/12/2019 QoS Requirements for VoIP
44/95
KPI Names Description Logical Formulae KPI
object
Why interesting? Interfa
ce
Attempted
EPS attach
procedures
Provides the
number of
attempted EPS
attach procedurewithin the MME.
Sum of all attempts
at attach EPS.
Valid for
PS
Receipt of ATTACH
REQUEST message
with ATTACH TYPE
information elementindicating EPS attachfrom the MS.
Successful
EPS attach
procedures
Number of
successfully
performed EPS
attach withinMME.
Sum of all
successful attaches.
Valid for
PSTransmission of a"ATTACH ACCEPT"message to the MSbut retransmissiondoesnt increase thecounter.
Failed EPS
attach
procedures
Number of failed
EPS attach
procedures . It issplit into sub
counters per thereject cause.
Sum of all failed
attach procedures.
Valid for
PSTransmission by theSGSN of the ATTACH
REJECT message tothe MS, in responseto a "ATTACHREQUEST"
8/12/2019 QoS Requirements for VoIP
45/95
KPI Names Description Logical Formulae KPIobject
Whyinteresting?
Interface
AttemptedEPS detachprocedure
Number ofattempted EPSdetach proceduresinitiated by UEwithin the MME.
Receipt of DETACHREQUESTmessage withdetach typeinformation elementfrom UE
Valid forPS
Gives the totalnumber ofattempteddetaches.
SuccessfulEPS detachprocedure
Number ofsuccessful EPSdetach proceduresinitiated by UEwithin the MME.
Transmission ofDETACH ACCEPTfrom MME
Valid forPS
Gives the totalnumbersuccessfully ofattempteddetaches.
AttemptedEPS detachprocedureby MME
Number ofattempted detachprocedures byMME.
Transmission ofDETACHREQUESTmessage by UEfrom the MME.
Valid forPS
All the attemptsof detach tocalculatesuccess
8/12/2019 QoS Requirements for VoIP
46/95
KPI Names Description Logical Formulae KPIobject
Whyinteresting?
Interface
SuccessfulEPS detachprocedureby MME
Number ofsuccessful detachprocedures byMME.
Receipt of DETACHACCEPT messageby UE from theMME.
Valid forPS
Calculatesuccess rate
Attempted
EPS detachprocedureby HSS
Number of
attempted detachprocedures byHSS.
Receipt of
CANCELLOCATION message by MMEfrom the HSS withcancel typeinformation element
indicating deleteuser.
Valid for
PS
All the attempts
of detach byHSS and usesRADIUS.
SuccessfulEPS detachprocedure
by HSS
Number ofsuccessful detachprocedures by
HSS.
Receipt ofCANCELLOCATION ACK
message from MMEby HSS.
Valid forPS
All thesuccessfulattempts to
detach by MME.
8/12/2019 QoS Requirements for VoIP
47/95
KPI Names Description Logical Formulae KPIobject
Whyinteresting?
Interface
Attemptedtracking
area updateprocedurewith SGWchange
Number ofattempted
tracking areaupdateprocedure withSGW changeinitiated withMME.
Receipt of TRACKINGAREA UPDATE
REQUEST messagefrom the MS, with lastregistered TAIinformation elementindicating to the MMEthat it wishes to be
served by new SGW.
Valid forPS
Calculate AREAUPDATE
attempts.
Successfultrackingarea updateprocedure
with SGWchange
Successfulnumber ofattemptedtracking area
updateprocedure withSGW changeinitiated withMME.
Transmission ofTRACKING AREAUPDATE ACCEPTmessage from the MS,
with last registered TAIinformation elementindicating to the MMEthat it wishes to beserved by new SGW
Valid forPS
Success rate ofArea updates.
8/12/2019 QoS Requirements for VoIP
48/95
KPI Names Description Logical Formulae KPIobject
Whyinteresting
?
Interface
Failedtracking
area updateprocedurewith SGWchange
Number offailed
tracking areaupdateprocedurewith SGWchangeinitiated with
MME.
Transmission of TRACKINGAREA UPDATE REJECT
message from the MS, withlast registered TAIinformation elementindicating to the MME that itwishes to be served by newSGW. Causes are also
defined in the message.
Valid forPS
Causes offailure.
Attemptedtrackingarea updateprocedurewithoutSGWchange
Number ofattemptedtracking areaupdateprocedurewithout SGWchangeinitiated with
MME.
Receipt of TRACKINGAREA UPDATE REQUESTmessage from the MS, withlast registered TAIinformation elementindicating to the MME that itwishes to be served by sameSGW.
Valid forPS
CalculateAREAUPDATEattempts.WithoutSGWchange.
8/12/2019 QoS Requirements for VoIP
49/95
KPI Names Description Logical Formulae KPIobject Whyinteresting?
Interface
Successfultrackingarea updateprocedurewithoutSGWchange
Successfulnumber ofattemptedtracking areaupdateprocedurewithout SGWchange
initiated withMME.
Transmission of TRACKINGAREA UPDATE ACCEPTmessage from the MS, withlast registered TAIinformation elementindicating to the MME that itwishes to be served by sameSGW
Valid forPS
Successrate ofAreaupdates.
Failedtrackingarea update
procedurewithoutSGWchange
Number offailed trackingarea update
procedurewithout SGWchangeinitiated withMME.
Transmission of TRACKINGAREA UPDATE REJECTmessage from the MS, with
last registered TAIinformation elementindicating to the MME that itwishes to be served by sameSGW. Causes are alsodefined in the message.
Valid forPS
Causesof failurein case of
sameSGW.
8/12/2019 QoS Requirements for VoIP
50/95
8/12/2019 QoS Requirements for VoIP
51/95
KPI Names Description Logical Formulae KPIobject
Whyinteresting?
Interface
Number of
dedicatedEPS bearers
in activemode(Mean)
Mean
number ofdedicated
EPSbearers.
Sampling at a pre-defined
interval, sum of dedicatedEPS bearer established by
MME in active mode andthen taking the arithmeticmean.
Valid
forPS
The total
activemode
bearerswould givethe load.
Number ofdedicated
EPS bearersin activemode(Maxim
um)
Maximumnumber of
dedicatedEPSbearers.
Sampling at a pre-definedinterval, sum of dedicated
EPS bearer established byMME in active mode andthen taking the maximum.
Validfor
PS
The totalactive
modebearerswould give
themaximumload.
8/12/2019 QoS Requirements for VoIP
52/95
KPI Names Description Logical Formulae KPIobject
Whyinterestin
g?
Interface
Dedicated
bearer set-up
time byMME(Mean)
Valid time per
dedicated
bearer set-upprocedure by
MME.
Obtained by accumulating the time
intervals for every successful
dedicated bearer setup by MME B/WACTIVATE DEDICATED EPS
BEARER CONTEXT REQUEST andcorresponding ACTIVATE
DEDICATED EPS BEARER
CONTEXT ACCEPT message receipt
by the MME. This time when divide by
the total number of successfuldedicated bearer gives the mean.
Valid for
PS
This would
let us
calculatethe mean
of set-uptime.
Attempted
dedicated
bearer
activationprocedure byMME
Number of
attempted
dedicated
beareractivationprocedure by
MME.
Transmission of ACTIVATE
DEDICATED EPS BEARER
CONTEXT REQUEST message by
MME.
Valid
FOR PS
Total
number of
attempts.
8/12/2019 QoS Requirements for VoIP
53/95
KPI Names Description Logical Formulae KPI object Why
interesting?
Interfa
ce
Successful
dedicated
bearer
activation
procedure byMME
Number of
successful
dedicated bearer
activation procedure
by MME.
Receipt of ACTIVATE
DEDICATED EPS BEARER
CONTEXT ACCEPT
message by MME.
Valid FOR
PS
Total
number of
successful
attempts.
Faileddedicated
bearer
activation
procedure byMME
Number of faileddedicated bearer
activation procedure
by MME.
Transmission of ACTIVATEDEDICATED EPS BEARER
CONTEXT REJECT
message by MME from UE
with ESM cause indicatingthe cause of failure..
Valid FORPS Failuredetection.
Attempted
dedicated
bearer de
activationprocedure by
MME
Number of
attempted dedicated
bearer deactivation
procedure by MME.
Transmission of
DEACTIVATE EPS BEARER
CONTEXT REQUEST
message by MME.
Valid FOR
PS
Total
number of
attempts to
de activate
8/12/2019 QoS Requirements for VoIP
54/95
KPI Names Description Logical Formulae KPI
object
Why
interesting?
Interf
ace
Successfuldedicatedbearer de
activationprocedure byMME
Number ofsuccessfuldedicated bearer de
activation procedureby MME.
Receipt ofDEACTIVATE EPSBEARER CONTEXT
ACCEPT message byMME.
ValidFORPS
Totalnumber ofsuccessful
attempts todeactivate.
Attempted
EPS bearermodificationprocedure byMME
Number of
attempted bearermodificationprocedure by MME.
Transmission of
MODIFY EPS BEARERCONTEXT REQUESTmessage by MME.
Valid
FORPS
Total
number ofattempts tomodify
SuccessfulEPS bearermodificationprocedure byMME
Number ofsuccessful EPSbearer modificationprocedure by MME.
Receipt of MODIFYEPS BEARERCONTEXT ACCEPTmessage by MME.
ValidFORPS
Totalnumber ofsuccessfulattempts toMODIFY.
8/12/2019 QoS Requirements for VoIP
55/95
KPI Names Description Logical Formulae KPI
object
Why
interesting?
Interf
ace
Failed EPSbearermodification
procedures byMME
Number of failedEPS bearermodification
procedure by MME.
Receipt of MODIFYEPS BEARERCONTEXT REJECT
message by MMEfrom UE. With ESMCause.
ValidforPS.
Used tocalculatethe
successrate.
Attempted
number ofPDNGW initiateddedicated bearercreation
Number of
attempted PDN-GWcontaining multiplebearer IDs, eachcumulated to thecounter.
Total Number of
PDNGW created.
Valid
forPS
Success
ratecalculation.
Successfulnumber ofPDNGW initiateddedicated bearercreation
Number ofsuccessful PDN-GWcontaining multiplebearer IDs, eachcumulated to thecounter.
Total Number ofPDNGW created.
ValidforPS
Successratecalculation.
8/12/2019 QoS Requirements for VoIP
56/95
KPI Names Description Logical Formulae KPIobjec
t
Whyinterestin
g?
Interfac
e
Failed number ofPDNGW initiateddedicated bearer
creation
Failed PDN-GWcontaining multiplebearer IDs, each
cumulated to thecounter.
Total Number of PDNGWcreated.
Validfor PS
Failurerate andcause of
failure.
Attempted numberof PDNGWinitiated dedicatedbearer deletion.
Number ofattempted PDN-GW initiatedDedicated BearerDeletion.
Transmission of DeleteBearer REQUESTmessage may containmultiple bearer ID, eachbearer shall be cumulatedto the counter.
Validfor PS
Attemptsof numberof deletion.
Successful
number ofPDNGWDedicated bearerdeletion
Number of
successfully PDN-GW initiatedDedicated bearerdeletion.
Receipt of Delete Bearer
Response message byPDNGW where cause andreceives a nACCEPTNCERESPONSE
Valid
for PS
Success
ratecalculation.
KPI Names Description Logical Formulae KPIobjec
Whyinterestin
Interfac
8/12/2019 QoS Requirements for VoIP
57/95
objec
t
interestin
g?
rfac
e
Failed numberof PDNGWinitiated
dedicatedbearer deletion
Failed PDN-GWinitiated dedicatedbearer deletion.
Split into subcounters per
reject cause.
Receipt of DeletionBearer responseMESSAGE where
cause is indicated.
ValidforPS
Failurerate andcause of
failure.
Attemptednumber of
PDNGW
initiatedmodificationwith QoSupdate.
Number ofattempted PDN-
GW initiated
Dedicated Bearermodification withQoS update
Transmission ofUpdate Bearer
Request message
from PDNGW withBearer Level QoScontaining all bearerIDs.
Validfor
PS
Attempts of
number
of QoSupdation.
Successfulnumber ofPDNGW
Dedicatedbearermodificationwith QoS
SuccessfullyPDN-GW initiatedDedicated bearer
modification withQoS update.
Response to therequest sent.
ValidforPS
Successratecalculati
on.
KPI Names Description Logical Formulae KPI Why Inte
8/12/2019 QoS Requirements for VoIP
58/95
objec
t
interestin
g?
rfac
e
Failed PDNGW
initiateddedicatedbearer with
QoS update
Failed PDN-GW
initiated dedicatedbearer modificationwith QoS. Split into
sub counters perreject cause.
Receipt of Update
Bearer responseMESSAGE wherecause is
indicated.
Valid
forPS
Failure
rate andcause offailure.
Attempted
number ofPDN-GW
initiatedDedicatedBearer
Modificationwithout QoS
update.
Number of attempted
PDN-GW initiatedDedicated Bearer
Modification withoutQoS update.
Transmission of
"Update BearerREQUEST"
message FromPDN-GW withoutBearer Level
QoS IE, thismessage may
contains multipleBearer IDs
Valid
forPS
Attempt
s ofnumber
ofupdationwithout
QoS ..
8/12/2019 QoS Requirements for VoIP
59/95
KPI Names Description Logical Formulae KPI
object
Why
interesting?
Inte
rface
Successful number
of PDN-GW initiatedDedicated Bearer
Modification
without QoS update.
Number of successfully
performed PDN-GWinitiated Dedicated Bearer
Modification without QoS
update.
Response to the request
sent.
Valid for
PS
Succes
s ratecalcula
tion.
Failed number of
PDN-GW initiated
Dedicated BearerModification without
QoS update
Number of failed PDN-GW
initiated Dedicated Bearer
Modification without QoSupdate. The measurement
is split into sub counters
per the reject cause
Receipt of Update Bearer
Response message by
PDN-GW without BearerLevel QoS IE in the
Update
Bearer Request message
which contains the same
EPS Bearer ID and where
Cause IE identifies afailed
bearer handling with
Rejection Response
Valid for
PS
Failure
rate
andcause.
8/12/2019 QoS Requirements for VoIP
60/95
Feedback-assisted DynamicNetwork Provisioning
Motivation and application scenario
8/12/2019 QoS Requirements for VoIP
61/95
Use of monitoring agent to provide feedback about the networkcondition and dynamically control the router and assign priority toapplication traffic under network congestion
EF
BE
NetDetector
controller
System architecture of testbed
8/12/2019 QoS Requirements for VoIP
62/95
Automatic configuration of router
8/12/2019 QoS Requirements for VoIP
63/95
EDI: enhanced device interface
Provides a comprehensive management interface for variousCisco devices with a standard programmatic interface
Two diffserv queues:
Expedited forwarding (EF)
match DSCP 46
assured minimum bandwidth- Best effort
match DSCP 0 set maximum bandwidth usage
Commands can be read in the form of CLI and are
encapsulated in XML format when issuing edit-config
operation of NETCONF
Query NetDetector and mark traffic
8/12/2019 QoS Requirements for VoIP
64/95
Controller polls NetDetector periodically (~ 20 sec) Alternatively, Netdetector can send alarms
Two kinds of query in form of NIKSUN URI API
Check application type
- /ngen/srvc/dashboardData?recorder=&iface=&startTime=-
2%20min&endTime=now&layer=Application&dataType=application&customDT=dataFields- trigger Marking traffic to EF class once application appears
Get application bit rate
-/ngen/srvc/dashboardData?recorder=&iface=&startTime=-2%20min&endTime=now&layer=Application&dataType=time,bitRate&customDT=dataField
s&window=10
- Trigger router configuration when cross traffic exceeds upper threshold
Traffic marking is done by issuing iptables command at applicationsource host
Before marking
After marking
Packet Classification
8/12/2019 QoS Requirements for VoIP
65/95
65
Before marking
After marking
8/12/2019 QoS Requirements for VoIP
66/95
8/12/2019 QoS Requirements for VoIP
67/95
Experiment results (2)
8/12/2019 QoS Requirements for VoIP
68/95
Change of quality of video & audio over time
MOS
Packet loss
No cross traffic cross trafficPriority Queue (E/F)
No cross trafficPriority Queue (E/F)
Experiment results (3)
8/12/2019 QoS Requirements for VoIP
69/95
Change of traffic received at destination host
Change of bandwidth and time jitter for cross traffic
b
ytes
time
Black: streaming media traffic
Red: cross traffic
Response time:
~ 40s
Experiment results (4)
8/12/2019 QoS Requirements for VoIP
70/95
Effect of polling time interval
20s interval:
~ 40s response time
10s interval:
~ 30s response time
Future work
8/12/2019 QoS Requirements for VoIP
71/95
Integrating the controlling program intoNetDetector
Reducing the response time
Depends on polling interval and time spent in configuring therouter
Using interruption/alarms rather than polling can further reduce
response timeBeing more adaptive to various scenarios Many prerequisite information such as IP address of streaming
media server and client is assumed
Change of the configuration of the router should not block othernormal traffic in practical situation, AF class is necessary to dealwith these traffic (control traffic)
QoE Metrics
8/12/2019 QoS Requirements for VoIP
72/95
Slide 72 GISFI
Require Session-
basedMeasurements
QoE metrics Driven by measurements
8/12/2019 QoS Requirements for VoIP
73/95
Slide 73 GISFI
What To Measure?
Which Layer?
Which Application?
Which User?
Hop-by-hop or End-to-end?
Etc?
QoE Metrics
8/12/2019 QoS Requirements for VoIP
74/95
Slide 74 GISFI
Require Multi-
timescaleMeasurements
QoE Metrics
8/12/2019 QoS Requirements for VoIP
75/95
Slide 75 GISFI
What is Frequency ofMeasurement?
Duration of Flow?
Minutes?
Seconds?
Sub-seconds?
Per-packet?
QoE Metrics Time Effect
8/12/2019 QoS Requirements for VoIP
76/95
Slide 76 GISFI
QoE Metrics
8/12/2019 QoS Requirements for VoIP
77/95
Slide 77 GISFI
Require Multi-
LayerMeasurements
8/12/2019 QoS Requirements for VoIP
78/95
QoE Metrics Application Specific
8/12/2019 QoS Requirements for VoIP
79/95
Slide 79 GISFI
Application HTTP
Application SSH
QoE Metrics User centric
8/12/2019 QoS Requirements for VoIP
80/95
Slide 80 GISFI
User 1
User 2
QoE Metrics - Application
8/12/2019 QoS Requirements for VoIP
81/95
Slide 81 GISFI
All Traffic Except Facebook
Facebook Only
QoE Metrics
8/12/2019 QoS Requirements for VoIP
82/95
Slide 82 GISFI
Require DPI for
ApplicationClassification
QoE Metrics
8/12/2019 QoS Requirements for VoIP
83/95
Slide 83 GISFI
Require DPI for ApplicationClassification
Classification and Marking
Policing and Markdown
Queuing and Dropping
Priority QoS Treatment (Diffserv approach) in the Core IPTransport
8/12/2019 QoS Requirements for VoIP
84/95
DSCP classification and marking at the edge, and class-based priority queuing andassured bandwidth scheduling at the edge and core routers
EF Treatment: For Emergency SIP signaling and SIP Register transport(Strict-priority forwarding for bounded bandwidth)
AF Treatment: For Emergency VoIP and Video/IP RTP media (Weighted sharedbandwidth scheduling of remaining bandwidth among AF classes)
BE Treatment: Best-effort traffic forwarding only when bandwidth not in use byhigher priority traffic; Drop otherwise
84
Experiencing Quality of Services under congestion
Audio Quality
8/12/2019 QoS Requirements for VoIP
85/95
85859.5 Mbps Cross Traffic
9 Mbps Cross Traffic
8 Mbps Cross Traffic
7 Mbps Cross Traffic
yVideo Quality
IncreaseT
rafficConge
stion
VoIP Call (10 Mb/s One-way Cross Traffic)
Applying Diffserv-based QoS to VoIP
8/12/2019 QoS Requirements for VoIP
86/95
86
Priority VoIP 10 Mb/s cross traffic (packet size 1440 bytes)
Non Priority VoIP 10 Mb/s cross traffic (packet size 1440 bytes)
Non Priority VoIP 10 Mb/s cross traffic (packet size
400 bytes)
Measurements - IMS
T N R Cli b d
8/12/2019 QoS Requirements for VoIP
87/95
Top N Reports Clients based on SIP Registrations/Re-Registrations/De-Registrations
Number of INVITE/NOTIFY/ SUBSCRIBE messages
Failed/Successful authentications at P-CSCF/S-CSCF/I-CSCF
depending on Authentication type (SIP Digest, IMS AKA)
Message type (INVITE, NOTIFY, BYE)
Malformed messages (SIP, RTP, H.248) identified using
protocol grammar, rulesUnauthenticated/Un-authorized messages
Spoofed messages
Session minutes (service usage)
Slide 87
Measurements IMS (Contd.)
T N R t S b d
8/12/2019 QoS Requirements for VoIP
88/95
Top N Reports Servers based on Excessive Registrations/subscriptions from a given
client/proxy
Setup requests (e.g., SIP INVITE)
Unauthenticated/spoofed messages (e.g, SIP BYE/NOTIFY) Number of data sessions
Incoming message/packet rates
Number of authentication challenges/failure messages
Malformed signaling/media messages
Key exchanges during IMS AKA authentication
Ability to drill down into data sessions - e.g., for given P-CSCF,
find all the messages from client X between time T1 to T2.
Slide 88
Measurements - LTE
I i h i i li d d l
8/12/2019 QoS Requirements for VoIP
89/95
Insight into signaling and user data volumes
Data volume distribution by Top SGW
Top MME
Top eNodeB
Top IMSI
Volume distribution available by Data Sessions
Packets
Bytes
Setup time
Session duration
.. etc
QoE Metrics QoS due to Mobility
8/12/2019 QoS Requirements for VoIP
90/95
Slide 90 GISFI
Minimize the interruption inQoS during handover
Interoperability with
Mobility protocols
QoE Metrics
8/12/2019 QoS Requirements for VoIP
91/95
Slide 91 GISFI
Interoperability withMobility protocols
8/12/2019 QoS Requirements for VoIP
92/95
Baseline Document (June )
Next Steps
8/12/2019 QoS Requirements for VoIP
93/95
Baseline Document (June )Define a set of requirements that is application
specific and applicable to Indian rural
environmentDefine a set of methodologies to define end-to-
end QoS parameters
Multi-layer QOSNetwork, Application Layer
Multi-time-scale measurements
Granularity of measurement
Define a set of APIs to control the network basedon measurement
Slide 93 GISFI
8/12/2019 QoS Requirements for VoIP
94/95
KPIs FOR LTE
8/12/2019 QoS Requirements for VoIP
95/95
95
Top Related