17
Prep: Jatinder Singh Appr: Checked: Rev: Date: 2012-06-12 LTE Analysis_UETR VOLTE ANALYSIS Ericsson Internal 1 (17) LTE Analysis Tools: TEMS Discovery and NEO parser
| Date post: | 27-Sep-2015 |
| Category: |
Documents |
| Upload: | manpreet-kaur |
| View: | 11 times |
| Download: | 1 times |
Slide 1
LTE AnalysisTools: TEMS Discovery and NEO parserSlide titleIn CAPITALS 50 pt
Slide subtitle 32 pt
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17) 7/19/2012 1Overview of the Data collection
UETRTI LogsMME TracesSGi TracesNon E///Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)LTE Layer 3 KPIs for TEMS DiscoveryAccess ability and Retain ability are two main KPIs for LTE Layer 3 Analysis. ASCOMs VoLTE report also provides LTE RRC KPIs like RRC Setup Failure Rate, RRC Setup Attempts, RRC Setup Complete, RRC Drop Rate, RRC Calls Successfully Completed, RRC Drops, etcetera.RRC Setup Failure Rate: (# of RRC Connection Setup Attempt - # of RRC Connection Setup Success) / # of RRC Connection Setup Attempt. Based upon, all MS3 (MO), MS4 (MT) and MS2 (LC) attempts respectively.RRC Setup Attempts: Count of event RRC Connection Request. This event is triggered by a RRC Connection Request message. Note, this event is only generated if followed by a RRC Connection Setup Complete, or RRC Connection Setup Failure event in same log-file / device.RRC Setup Complete: Count. This event is triggered by a RRC Connection Setup Complete message. Note, this event has to be preceded by a RRC Setup Attempt event in same log-file / device.RRC Drop Rate: For MO and MT column: # of RRC Connection Drop / (# of RRC Connection Completed (Release) + # of RRC Connection Drop), based upon all MS3 (MO) and MS4 (MT) attempts respectively. For LC column: # of RRC Connection Drop / (Total Duration of all MS2 (LC) RRC Connections / Mean Holding Time), based upon all MS2 RRC Connections.RRC Calls Successfully Completed: Count of event RRC Connection Release. This event is triggered by a RRC Connection Release message.RRC Drops: Count. This event is triggered when receiving a RRC Connection Re-establishment Request message.Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)LTE Layer 3 KPIs for TEMS DiscoveryLTE KPIs from TD VoLTE report are not accurate since it derives the KPIs from the data that is present in the TEMS Investigation log files and not from UETRs.User when attempts to make a call new RRC Connection is established in case user was in Idle Mode and once the call is ended by user Tinactivity timer starts, with the expiration of this Tinactivity timer RRC connection is released.So in case where Drive test team ended the call and stopped recording the TEMS Investigation logs without waiting for Tinactivity timer to cause RRC Connection release we will miss the RRC Connection Release message, to eradicate the same Drive test team should wait for some time after ending the call before stopping the TI logs. (Example in MPCS Project, Tinactivity timer was set to 10 seconds so drive test team was asked to wait for about a minute before they stop recording).Another case when TI can miss the L3 message is when user turns ON the UE, RRC connection is established QCI 9, and QCI 5 are established if drive test team now starts recording the TI logs and then make a call while UE is already in RRC Connected mode TI logs will miss the RRC connection setup messages, causing incorrect KPIs from VoLTE report.To eradicate the same in MPCS VoLTE project UETR logs were collected and were used intensively during the analysis procedure as well as while providing the KPIs to customer.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)RRC Analysis Procedure from TD
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)RRC Analysis Procedure from TD
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)RRC Analysis Procedure from TD
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)RRC Analysis Procedure from TD
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)Verification of Normal Release
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)Internal Events
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)RRC Drop resulting in no VoLTE Failure Scenario
RRC Drop Occurs
VoLTE Call Continues
0 Throughput was observed for ~ 2 secsTop right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17)RRC Re-establishment in a new cell
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17) 7/19/2012 12UETR Shows the Drop
12Above is a bulk parsing of UETRs collected during the drive. The messages are for the same UE but from different ENBs.RRC Connection Request is sent to a New ENBOld ENB gets a UE Context Release Command. Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17) 7/19/2012 13Subsequent RRC Connection has all 3 bearers
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17) 7/19/2012 14QCI9 default bearer to the Internet APN.QCI5 default bearer to the IMS APNQCI1 dedicated bearer to IMS APN (used to carry the voice traffic)S11 Trace
MME sends Modify Bearer Request to CPGMME does not send a Release Bearer Request to the CPG because the UE is already connected to a New ENB.MME sends Modify Bearer Request to the CPG to change the GTP tunnel end point ID.As a result the CPG is unaware that a drop has occurred and will continue to forward RTP packets on the S1-U to the UE.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17) 7/19/2012 15Normal VoLTE Call End After ~3 minutes Drive team ended call.
Normal End was observed on UE PcapsTop right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17) 7/19/2012 16
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.Slide title 40 pt
Slide subtitle 24 pt
Text 24 ptBullets level 2-520 pt
Embedded font:!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Prep: Jatinder SinghAppr: Checked: Rev: Date: 2012-06-12LTE Analysis_UETRVOLTE ANALYSISEricsson Internal# (17) 7/19/2012 1717Sheet2Site Not TransmittingDFWe0600230
Sheet1TimeDateLatitudeLongitudeLTE RRC Connection Request(0512_99_MS2)LTE RRC Connection CompleteLTE RRC Connection ReleaseLTE RRC Reestablishment RequestCauseCommentsRecComments for tiltsLC Duration11:59:52.1495/12/201232.771809-96.959946649LTE RRC Connection Request11:59:52.2235/12/201232.771809-96.959946723LTE RRC Connection Complete12:16:13.2215/12/201232.7965-96.9213473721LTE RRC Connection Release00:16:21.07212:17:19.0815/12/201232.796502-96.9213477095LTE RRC Connection Request12:17:19.1495/12/201232.796502-96.9213476755LTE RRC Connection Complete12:17:25.375Release00:00:06.29412:29:36.9535/12/201232.79651-96.92135LTE RRC Connection Request12:29:37.0215/12/201232.79651-96.92135LTE RRC Connection Complete13:17:25.000Release00:47:48.04713:39:36.0985/12/201232.789705-96.856086LTE RRC Connection Request13:39:36.1665/12/201232.789705-96.856086LTE RRC Connection Complete13:57:58.2325/12/201232.792699948-96.853926684LTE RRC Reestablishment RequestPoor RF and Poor SINRUE Sends RRC Measurement report for cell DFWe06001653 PCI 352 from PCI 474 cell DFWe06002241, EnB sends Reconfiguration to UE but UE never received the same, RSRP -116 SINR -6 BLER 30.91. Cell selectionw as observed to cell DFWe06002241 PCI 280.Uptilt PCI 280 cell DFWe06002241 Current EDT 02 to EDT 01 / 00 I(Refer to Planet Predictions)Cannot do so CDMA Sharing00:18:22.13413:57:58.5735/12/201232.792695759-96.853871101LTE RRC Connection Request13:57:58.6175/12/201232.792695011-96.853863929LTE RRC Connection Complete16:28:52.3415/12/201232.74773559-96.91838667LTE RRC Reestablishment RequestPoor SINRUE was at PCI 77 cell DFWe06001762, UE sends RRC Measurement report for PCI 14 cell DFWe06001762. This spot is 3.6 kms away from PCI 14 and 1.4 kms away from PCI 379 cell DFWe06052236, to which it Handovers after 5 seconds. RSRP -104.4 SINR -9.8 BLER 66.67Downtilt PCI 14 cell DFWe06003012 Current EDT 02 to 03, and Uptilt PCI 379 cell DFWe06052236 current EDT 04 to 03.02:30:53.76816:28:52.6115/12/201232.747732113-96.918341802LTE RRC Connection Request16:28:52.6505/12/201232.74773145-96.9183333LTE RRC Connection Complete16:31:49.3035/12/201232.736882272-96.892786565LTE RRC Reestablishment RequestMissing NBR Poor SINR causing high BLERUe is at PCI 500 cell DFWe06002232 and is asking for HO to back lobe of PCI 432 cell DFWe06052236. Since PCI 5009 and 432 are not NBRs for HO is not seen. RSRP -102.5 SINR -10 BLER 43.5Uptilt PCI 500 cell DFWe06002232 Current EDT 05 to 04Cannot do so CDMA Sharing00:02:56.69216:31:49.3445/12/201232.736883256-96.89278062LTE RRC Connection Request16:31:59.3845/12/201232.737032972-96.891884552LTE RRC Connection Request16:31:59.4685/12/201232.737031544-96.891882704LTE RRC Connection Complete17:40:22.4655/12/201232.762187945-96.96369648LTE RRC Connection Release01:08:23.08105:04:51.0883054560.4818000240RAW1.97%Filtered0.00%18296.48152.4706666667
Metric Group 1TimeDateLatitudeLongitudeLTE RRC Connection Request(0512_99_MS2)LTE RRC Connection CompleteLTE RRC Connection ReleaseLTE RRC Reestablishment Request11:59:52.1495/12/201232.7718090-96.9599466LTE RRC Connection Request11:59:52.2235/12/201232.7718090-96.9599467LTE RRC Connection Complete12:16:13.2215/12/201232.7965000-96.9213474LTE RRC Connection Release12:17:19.0815/12/201232.7965020-96.9213477LTE RRC Connection Request12:17:19.1495/12/201232.7965020-96.9213477LTE RRC Connection Complete12:29:36.9535/12/201232.7965100-96.9213500LTE RRC Connection Request12:29:37.0215/12/201232.7965100-96.9213500LTE RRC Connection Complete13:39:36.0985/12/201232.7897050-96.8560860LTE RRC Connection Request13:39:36.1665/12/201232.7897050-96.8560860LTE RRC Connection Complete13:57:58.2325/12/201232.7926999-96.8539267LTE RRC Reestablishment Request13:57:58.5735/12/201232.7926958-96.8538711LTE RRC Connection Request13:57:58.6175/12/201232.7926950-96.8538639LTE RRC Connection Complete16:28:52.3415/12/201232.7477356-96.9183867LTE RRC Reestablishment Request16:28:52.6115/12/201232.7477321-96.9183418LTE RRC Connection Request16:28:52.6505/12/201232.7477315-96.9183333LTE RRC Connection Complete16:31:49.3035/12/201232.7368823-96.8927866LTE RRC Reestablishment Request16:31:49.3445/12/201232.7368833-96.8927806LTE RRC Connection Request16:31:59.3845/12/201232.7370330-96.8918846LTE RRC Connection Request16:31:59.4685/12/201232.7370315-96.8918827LTE RRC Connection Complete17:40:22.4655/12/201232.7621879-96.9636965LTE RRC Connection Release
