Call Summary Logs

Call Summary logs

CSL logs are processed and maintained by ECCB software

block in eNB.
CSL logs consist of only failed calls.
eNB transfers these files to LSM every 5 mins.
Files are transferred from 103 VLAN of eNB to SBI IP of LSMR.
LSM process the information of each eNB.
LSMR server consolidates all eNB files and store in single file.
This file is created every 5 mins.
LSM stores data of 3 days. Hence, whenever new file is
created, old file is deleted in LSMR server.

CSL software process

ECCB is eNB call control block which is

responsible of processing L3 messages.
ECCB block writes the required data in a file
in eNB.
TRM block transmits the file to LSM on SBI
interface.
3

Exporting CSL logs

Goto Performance -> Call

Summary Logs.
Following needs to be selected:
1. eNB (mandatory and multiple
selections not allowed)
2. Call release cause code (if
required for particular release
code not mandatory).
3. NO RTP FLAG and RRC
CONNECTION RESTABLISHMENT
FLAG (non mandatory).
. Select time then press search to
get the logs.
4

CSL decoding
CSL file exported from LSMR contains following information:
1. Call Information
2. Common Information
3. Connection Information
Sample_CSL
4. Release Information
5. Handover Information
6. Throughput Information
7. RF Information
CSL_MAPPING
8. Neighbor Information
9. UE History Information
10. Call Processing Information
11. RRE Information

Collection time points

Message

Collection point

callId

When receiving the RRC Connection Setup Complete message, when

receiving the Handover Request message

IMSI

When receiving the Initial Context Setup Request message, When

receiving the Handover Request message

C-RNTI
PDCP_UL_NO_RTP
PDCP_DL_NO_RTP
RLC_UL_NO_PAC
RLC_UL_ZERO_BO_CNT
RLC_DL_NO_PACKET_DELAY
RLC_DL_ZERO_BO_CNT
RLC_DL_NO_SCHEDULING
MAC_UL_NO_RTP
MAC_DL_NO_RTP
NO_RTP_FLAG

When receiving the RRC Connection Request message, When receiving

the RRC Connection Reestablishment Request message
When UL NO-RTP occurs more than the noRtpTimer in the PDCP Layer
When DL NO-RTP occurs more than the noRtpTimer in the PDCP Layer
KET_DELAY When receiving the first UL packet after setting the QCI#1
Bearer
For over the noRtpTimer, the number of times when the UL BO is 0
When receiving the first DL packet after setting the QCI#1 Bearer
For over the noRtpTimer, the number of times when the DL BO is 0
The count of cases where scheduling is not received over the
noRtpTimer even if the DL BO exists.
When UL NO-RTP occurs more than the noRtpTimer in the MAC Layer
When DL NO-RTP occurs more than the noRtpTimer in the MAC Layer
Out of PDCP_UL_NO_RTP / PDCP_DL_NO_RTP / RLC_DL_ZERO_BO_CNT/
RLC_DL_ZERO_BO_CNT / MAC_UL_NO_RTP /MAC_DL_NO_RTP, if there is a
case that is not 0

RSRP Mapping Table

The RSRP value reported in CSL is in decimal format. Hence, it needs to be conve
To obtain the RSRP level.
Reported value

Measured quantity value

Unit

RSRP_00

RSRP -140 dBm

dBm

RSRP_01

-140 RSRP < -139 dBm

dBm

RSRP_02

-139 RSRP < -138 dBm

dBm

dBm

RSRP_95

-46 RSRP < -45 dBm

dBm

RSRP_96

-45 RSRP < -44 dBm

dBm

RSRP_97

-44 RSRP dBm'

dBm

RSRP Mapping Table

The RSRP value reported in CSL is in decimal format. Hence, it needs to be conve
To obtain the RSRP level.
Reported value
RSRQ_00
RSRQ_01
RSRQ_02

Measured quantity value

Unit

RSRQ -19.5

dB

-19.5 RSRQ < -19

dB

-19 RSRQ < -18.5

dB

-4 RSRQ < -3.5

dB

RSRQ_32
RSRQ_33
RSRQ_34

-3.5 RSRQ < -3

-3 RSRQ

dB
dB

Sample analysis
HO_FAIL between PCI 261 (I-DL-DLHI-ENB-0263, 2300
alpha) and PCI 168 (I-DL-DLHI-ENB-6149, 2300 alpha).

sample analysis

Thank you

Call Tracing

10

Call tracing using GUI

ECCB is eNB call control block which is responsible of
processing L3 messages.
ECCB block sends the required call details to TRM module.
TRM block transmits the information to LSM on SBI interface.

11

Setting call trace in GUI

There are two types of
tracing available from GUI:
Management (trace on S1
interface) and Signaling (Trace
on IMSI)
For management tracing ,
goto Performance -> Call
Trace and click add.
Select rest of the
parameters.
Press Register.

12

Setting call trace in GUI

For management tracing ,
goto Performance -> Call
Trace and click add.
Select interfaces on which
traces are required from
NE_TYPE, SGW, PGW of
the parameters.
Press Register.

13

Querying/viewing the call

trace

Once the trace is registered, it

can be seen in list of registered
traces on right screen.
Trace can be viewed by double
clicking the trace in list.
Also, once registered and started,
trace runs in background.
Max 3 days history trace can be
queried by following:
1. Goto Performance-> Call Trace
-> History.
2. Select appropriate trace_type
and target.
3. Enter Time period then press
search.
4. Max 3 days trace is available.

14

Other tracing
Other than LSMR GUI, following tracings are available for
analysis.
1. ECCB tracing in eNB telnet session.
2. Pcap on S1 AP link.
Traces

. Sample traces.

15