SmalltalkforVoLTEtroubleshooting案例.pptx

Small talk for VoLTE troubleshooting Pi Fengming Jul 2015 AGENDA Part 2 | Methodology of VoLTE troubleshooting Part 3 | VoLTE typical KPIs Part 4 | Case analysis guideline Part 1 | basic idea of VoLTE AGENDA Part 2 | Methodology of VoLTE troubleshooting Part 3 | VoLTE typical KPIs Part 4 | Case analysis guideline Part 1 | basic idea of VoLTE VoLTE structure Required bears for offering VoLTE service Required bears for offering VoLTE service IMS Registration IMS Registration SIP preconditionsSupport for basic point-to-point and call forwarded calls Preconditions allows end-to-end bearer path resources to be reserved before the called party begins alerting SIP preconditions typically involves a three-step process to confirm that all preconditions have been met: INVITE from UAC includes SDP offer with current quality of service (qos) and desired or mandatory qos preconditions Reliable 183 Session Progress from UAS includes SDP answer with its view of current and desired qos. SDP answer usually also includes a request that the UAC send a confirmation when all preconditions have been satisfied. UPDATE from UAC includes another SDP offer that confirms that all desired qos preconditions have been satisfied. When the UAS receives this confirmation, it begins alerting and sends a 180 Ringing response toward the caller. Avoid “ghost call” and mandated in GSMA IR 92 VoLTE Must be implemented E2E to be applicable, B2B behavior must examined for each different cases Increase the establishment phase delay INVITE [SDP offer 1 (with qos)] 183 [SDP answer1 (with qos)] party A party B PRACK + 200 OK PRACK exchanged UPDATE [SDP offer 2 (with qos)] 200 OK Update [SDP answer2] 180 Ringing [no SDP] VoLTE call typical scenario AGENDA Part 2 | Methodology of VoLTE troubleshooting Part 3 | VoLTE typical KPIs Part 4 | Case analysis guideline Part 1 | basic idea of VoLTE RAN User Experience Testing Drive Testing Devices IP Transport Core Configuration Assessment Drive Test Data A