Call Detail Feature Guide
Call Detail Feature Guide
Call Detail Feature Guide
Trace
Feature Guide
ZGO-06-01-008 Call Detail Trace
GU Commercial
Luo Chang
V1.0 2013/04/17 System Supporting Not open to the third party
qing
Dept.
TABLE OF CONTENTS
1 Feature Attribute ............................................................................................... 9
2 Overview ............................................................................................................ 9
2.1 Feature Introduction ............................................................................................. 9
2.2 License Control .................................................................................................. 10
2.3 Correlation with Other Features ......................................................................... 10
7 Abbreviation .................................................................................................... 53
8 Reference Document....................................................................................... 54
FIGURES
Figure 3-1 Overall Architecture of CDT Data Collection ........................................................11
Figure 6-1 Log Services Configuration .................................................................................46
Figure 6-2 Log Destination Configuration .............................................................................47
Figure 6-3 CDT Configuration...............................................................................................48
Figure 6-4 CDT Configuration...............................................................................................53
TABLES
Table 4-1 Parameter List ......................................................................................................16
Table 4-2 Configuration rule of System mode .......................................................................19
Table 4-3 Configuration rule of Level of system log ..............................................................20
Table 4-4 Configuration rule of Detection threshold of GID leak ...........................................20
Table 4-5 Configuration rule of The print level of CT associated log .....................................20
Table 4-6 Configuration rule of Report flag of CT tracing message Characteristic Information
.............................................................................................................................................21
Table 4-7 Configuration rule of Report flag of CT tracing message Standard Signals of
Original Call and Call Processing .........................................................................................21
Table 4-8 Configuration rule of Report flag of CT tracing message Standard Signals of
Periodic Measure Reports ....................................................................................................22
Table 4-9 Configuration rule of Report flag of CT tracing message RNLU Key Quality
Statistics Messages ..............................................................................................................22
Table 4-10 Configuration rule of Report flag of CT tracing message Inner Common Messages
Between RNLC and RNLU ...................................................................................................23
Table 4-11 Configuration rule of Report flag of CT tracing message Inner Keeping Alive
Messages Between RNLC and RNLU ..................................................................................23
Table 4-12 Configuration rule of Report flag of CT tracing message RNLC Inner Common
Messages .............................................................................................................................24
Table 4-13 Configuration rule of Report flag of CT tracing message RNLC Inner Keeping Alive
Messages .............................................................................................................................24
Table 4-14 Configuration rule of Report flag of CT tracing message RNLU Inner Information
.............................................................................................................................................25
Table 4-15 Configuration rule of Report flag of CT tracing message Inner Information in
Interface Board .....................................................................................................................25
Table 4-16 Configuration rule of Report flag of CT tracing message Print Information ..........26
Table 4-17 Configuration rule of Report flag of CT tracing message Support Layer Messages
.............................................................................................................................................26
Table 4-18 Configuration rule of Report flag of CT tracing message Standard Signals of TNL
.............................................................................................................................................27
Table 4-19 Configuration rule of Report flag of CT trigger process RRC connection ............27
Table 4-20 Configuration rule of Report flag of CT trigger process initial transform or transform
.............................................................................................................................................27
Table 4-21 Configuration rule of Report flag of CT trigger process safe-mode .....................28
Table 4-22 Configuration rule of Report flag of CT trigger process RAB establish ................28
Table 4-23 Configuration rule of Report flag of CT trigger process RBC channel adjustment
.............................................................................................................................................28
Table 4-24 Configuration rule of Report flag of Report flag of CT trigger process cell update
.............................................................................................................................................29
Table 4-25 Configuration rule of Report flag of CT trigger process switch ............................29
Table 4-26 Configuration rule of Report flag of CT trigger process relocation .......................30
Table 4-27 Configuration rule of Report flag of CT trigger process drop calls .......................30
Table 4-28 Configuration rule of Report flag of CT trigger process quality abnormal of user
plane ....................................................................................................................................30
Table 4-29 Configuration rule of Report flag of CT trigger process start abnormal of measure
.............................................................................................................................................31
Table 4-30 Configuration rule of Report flag of CT trigger process IU signal abnormal .........31
Table 4-31 Configuration rule of Report flag of CT trigger sub process RRC connect several
times ....................................................................................................................................31
Table 4-32 Configuration rule of Report flag of CT trigger sub process location update, route
update or cell update ............................................................................................................32
Table 4-33 Configuration rule of Report flag of CT trigger sub process call establish process
.............................................................................................................................................32
Table 4-34 Configuration rule of Report flag of CT trigger sub process UCIU Error ..............33
Table 4-35 Configuration rule of Report flag of CT trigger sub process establish and
reconfiguration process ........................................................................................................33
Table 4-36 Configuration rule of Report flag of CT trigger sub process FP fail periodically ...33
Table 4-37 Configuration rule of Report flag of CT trigger sub process Mono Call(TD only) .34
Table 4-38 Configuration rule of Master switcher of CR........................................................34
Table 4-39 Configuration rule of Switcher of CR cell - BoardLocation...................................34
Table 4-40 Configuration rule of Switcher of CR cell - RabStatInfo .......................................35
Table 4-41 Configuration rule of Switcher of CR cell - CallProcessRabInfo ..........................35
Table 4-42 Configuration rule of Switcher of CR cell - UpTriggerNorStat ..............................36
Table 4-43 Configuration rule of Switcher of CR cell - EmiParaInfo ......................................36
Table 4-44 Configuration rule of Switcher of CR cell - LacUpdateInfo ..................................36
Table 4-45 Configuration rule of Switcher of CR cell - RouteUpdateInfo ...............................37
Table 4-46 Configuration rule of Switcher of CR cell - CsCallNasInfo ...................................37
Table 4-47 Configuration rule of Switcher of CR cell - PsCallNasInfo ...................................37
Table 4-48 Configuration rule of Switcher of CR cell - DscpTrafficTypeStat .........................38
Table 4-49 Configuration rule of Switcher of CR cell - SigConInfo ........................................38
Table 4-50 Configuration rule of Switcher of CR cell - DropDetail TimteSlots And Codes.....38
Table 4-51 Configuration rule of Switcher of CR cell - HandOver TimteSlots And Codes .....39
Table 4-52 Configuration rule of Switcher of CR cell - NeighCellInfo For V320100 ...............39
Table 4-53 Configuration rule of Switcher of PGR ................................................................40
Table 4-54 Configuration rule of CDT support ......................................................................40
Table 4-55 Configuration rule of Report successful intra-BSC handover info ........................40
Table 4-56 Configuration rule of Report PS info ...................................................................41
Table 4-57 Configuration rule of Report location update info ................................................41
Table 4-58 Configuration rule of Report short message info .................................................41
Table 4-59 Configuration rule of Report access failure info ..................................................42
Table 4-60 Configuration rule of Report relevant signalling of CS failure ..............................42
Table 4-61 Configuration rule of Report relevant internal message of CS failure ..................43
Table 4-62 Configuration rule of Report measurement report of location update ..................43
Table 4-63 Configuration rule of Report measurement report of short message ...................43
Table 4-64 Configuration rule of Report measurement report of normal call release ............44
Table 4-65 Configuration rule of Report PS access failure info .............................................44
Table 4-66 Configuration rule of Report recent seven MR before Ho when Ho succeed .......45
1 Feature Attribute
BSC Version: [ZXG10-iBSC GSM (V6.30.102)]
Property: [Optional]
MS -
BTS -
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Note: [None]
2 Overview
The Call Detail Trace (CDT) function records the key information about BSC output
calls and other services such as Short Message (SM), location update and PS
service, including Call Detail Record (CDR) and associated logs. It can be used for
network planning and network optimization analysis, system fault localization and
system algorithm optimization.
CDT is provided in the unit of BSC. If CDT function is enabled, all calls or events
related to the BSC in the whole network can be recorded. Compared with traditional
analysis, such as drive test, alarm and performance statistics, CDT records call
details in real-time and the happened events are reverted to their original states.
Meanwhile, CDT reflects network quality of users granularity, achieving real-time
monitoring on network quality.
ZGO-06-01-006 Call Trace System Interface introduces CTS system, which traces
interface protocol information and equipments internal information according to the
preset IMSI. CTS records more detailed contents than CDT, but the subscriber
number that CTS traces is less than CDT, which only records the key information of
all subscribers.
3 Technical Description
Figure 3-1 shows the overall architecture of CDT data collection in the
BSCV6.50.000 series.
The service module collects CDT data and reports the data to the CDT collector
directly through the RAP platform. For UR11.2, an on-rack server is usually used,
that is, the OMM server is also on the iBSC rack. Therefore, an independent CDT
collector is not required.
iBSC
Service RAP
CDT
CDT collector
In the narrow sense, CDT refers to the Call Report (CR). In the wide sense, CDT refers to
all the flow information that affects subscribers behavior, which includes CDR and
associated logs.
CR: CR is used to export all the information related to a call that is automatically
collected and cached by the system in the call process.
CT: Call Trace (CT) associated logs are used by the system to automatically collect and
cache the key information and signaling messages related to a call in the call process.
When the call flow fails, the system provides one corresponding call record and several
signaling messages near the failure point. The call record and associated CT fragment
can be used together to locate the specific failure cause of a service call flow of a
subscriber.
By taking offline statistics and analyzing the CR and associated logs, the network quality
of subscribers/cells at all granularities can be learned to provide a reference for network
maintenance and optimization and fault localization.
In BSC UR12, after the service sends related data to the RAP platform, the platform
delivers the data to the CDT collector directly, without passing the background Network
Management System (NMS).
The CDT data is classified into the following two parts for collection and reporting:
CR: In the current 3G system, the CR data can be reported on package after a call ends.
Therefore, the middle assembling process does not exist.
CT: Since multiple boards may report data, the RAP platform provides a corresponding
cache area for each GID on the CMP. The service can send data to the RAP platform
regardless of one or more packets. The RAP platform caches and assembles the
packets.
In BSC UR12, the CDT data does not pass the OMCR. Therefore, a module is required
to solve the problem of assembling.
If the call is just handed over or migrated in the local module, service is implemented
relatively simple. It can apply for one memory on the local module and use it to cache CD
data. When a call ends, the data is assembled in one package and sent to the CDT
collector through the RAP platform.
Assembly is still completed at the background, and then optimized at the foreground.
When a call is handed over between modules, each module reports its CDT_CR data
respectively. The CR generated by a service instance is saved in the CDT_CR data area
allocated to the local module. When inter-module handover occurs, the CR data
generated on the target module is saved on the target module. The CR data on the
source module is directly assembled and reported when the instance is released due to
the handover. Meanwhile, the package indicates that this package is just one among
multiple packages of CDT_CR data, but not the end package. When the call is released,
the final module adds an end package flag to the reported CDT_CR data.
This solution is adopted when a call has only one CR data package on a CMP. If
inter-module handover takes place, the CDT interface machine needs to assemble
packages according to the GID information. Assembly is completed when the end
package is received.
This solution does not require increasing inter-module communication traffic, and the
CDT interface machine executes this part of work that affects performance.
The CDT interface machine completes assembly in this solution. It must know which
package is the end in the process of assembling data with the same GID. When a call
ends, the service must send the end information to the CDT interface machine.
For the sake of easy troubleshooting, the CDT_CR packages with the same GID must
contain packet ID information. The packet ID and the above call end information can be
placed together in the message header of the platform and provided for the CDT
interface machine. The message header explicitly informs the CDT interface machine so
that the CDT interface machine can know the CDT_CR package sequence and whether
a received package is the end package without decoding the CDT_CR data.
To alleviate the assembly workload of the CDT interface machine, the handover count
recorded for one call is 60 times In BSC UR12.
CDT_CT data localization aims to report call abnormality signaling, including the call
drop status and the information about assignment failure and handover failure.
The RAP platform caches the subscriber failure signaling. The RAP platform also caches
all the signaling messages reported by invoking the OAM_StEventTracefunction by the
service. Currently the RAP platform allocates a space of 3.96K to the GSM as the
standard signaling buffer of call originating. The standard signaling buffer of call process
is also 3.96K. The standard signaling buffer of call originating is a linear buffer, but the
standard signaling buffer of call process is a ring buffer. The RAP platform first caches
the information of the same GID in the standard signaling buffer of call originating. When
the standard signaling buffer of call originating is full, the RAP platform then caches the
information in the standard signaling buffer of call process. When the standard signaling
buffer of call process is also full, the information is cyclically overwritten only in the
standard signaling buffer of call process.
Although service intervention is not required in the caching process, the service needs to
trigger reporting and decide the reporting time. When finding that a call is abnormal, the
service invokes OAM_CtDataRptFlag() to require the RAP platform to send CD
packages to the CDT interface machine.
The bit5 of the R_OPTION.CdtOption parameter decides whether to report the signaling
message (whether the signaling message is reported when the CS service fails) when
the service fails. Service abnormality includes assignment failure and call drop.
The following function switches jointly control whether to report signaling messages in
case of access failure information, location update information and SM information
failure:
Because GID is applied for in the Ms instance of UMC, the CS instance and PS instance
use the same GID at time of DTM. The CD data related to the CS service and PS service
is reported together.
As a result, CR data sending to the background is not triggered when the CS service or
PS service releases an instance, regardless of whether the service is a DTM service.
When the MS instance finds that both the CS instance and PS instance under the Mobile
Station (MS) have been released completely, it can invoke OAM_GetCrDataAreaByGid()
to get the first address and length information of the CR data, and then invoke the
OAM_RnlcCrDataRpt() interface to require the platform to send CR data to the CDT
interface machine.
The CS service data is centralized on the CMP. The information on the CD user plane is
related to user plane connection and can be grasped on the CMP. The CMP can also
collect the information of failure that occurs in the connection process. Therefore, the
CDT information of CS service can be collected and reported on the CMP.
At present, the PS collects some statistics of the TBF process, and the PS control plane
process on the CMP collects and reports data. The data on the RUP board is collected
on the board, and then reported to the RANPS process when the MAC instance is
released.
The RAP platform saves data. The service invokes the OAM_RnlcCrDataSave function
to save CD data. The RAP platform records the CDT_CR information on the specified
CDT_CR memory space on the local board, and saves it in sequence.
For the sake of simplification, active and standby synchronization is not performed for the
CDT content. After active and standby switching, the CDT related data on the original
module is lost, and only the CDT data generated in the current host is available. To
facilitate troubleshooting, a cell is added for CDT_CR In BSC UR12 to indicate whether
the standby-to-active operation is performed.
Values of the CDT switch and service type reporting switch also decide whether to collect
CDT_CR data and whether to report CDT_CT data.
The reported data format combines custom and protocol cells. Cells can be used to
compress the data quantity.
1. An indicator is used in the structure to indicate whether the data of a field is valid.
For example, the indicator in the measurement report indicates whether the MS
report is valid.
2. The information that may occur is further split into different information elements
and reported separately. In this way, the reporting time is relatively flexible, avoiding
occupation of an excessive cache space.
3. The information that may occur and occupies more bytes can be in the mode of
variable information. When the information occurs, a label is used to indicate the
information,which avoids occupation of a fixed data space and saves space.
T: It is used to report some flags. For example, it indicates that this field is access
information or handover information.
V: It indicates the field that always occurs. Directly fill in the data content.
LV: It indicates the field that always occurs. Use this format in case of variable length.
TV: When a field is optional, this label is used to indicate that the field data occurs.
TLV: This format is used when a field is optional and the length is variable.
Information type flags can be nested. When an information record is reported, a label flag
starts before the information content, and labels can also be used to indicate the
occurrence of optional information elements in the information.
For example, when handover information is reported, the reported data format consists
of the information type, information length and other internal information, and the
reported format of other internal information can also consist of information type,
information length and specific content.
If the log server is on the rack In BSC UR12, data can be directly sent from the RAP
on CMP to the log server. If the log server is not on the rack, data is sent to the log
server through the EGPB interface board.
SN Name Figure
Abbreviation SystemMode
Description System mode
Managed object Log Destination (LogDestination)
Value range 0,32,64,128
Unit NA
Default value NA
Abbreviation SysLogLvl
Description level of system log
Managed object Log Destination (LogDestination)
Value range 1,2,3,4,5
Unit NA
Default value 4
Abbreviation GidLeakThrd
Description detection threshold of GID leak
Managed object Log Destination (LogDestination)
Value range 12,24,36,48,60,72
Unit NA
Default value NA
Abbreviation CTRelateLogLvl
Description The print level of CT associated log
Table 4-6 Configuration rule of Report flag of CT tracing message Characteristic Information
Abbreviation CtUeReportIndBit0
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}1,
{SystemMode==64}1,
Default value
{SystemMode==32}0,
{SystemMode==0}1
Table 4-7 Configuration rule of Report flag of CT tracing message Standard Signals of Original
Call and Call Processing
Abbreviation CtUeReportIndBit1
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}1,
{SystemMode==64}1,
Default value
{SystemMode==32}1,
{SystemMode==0}1
Table 4-8 Configuration rule of Report flag of CT tracing message Standard Signals of Periodic
Measure Reports
Abbreviation CtUeReportIndBit2
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}1,
Default value
{SystemMode==32}1,
{SystemMode==0}0
Table 4-9 Configuration rule of Report flag of CT tracing message RNLU Key Quality Statistics
Messages
Abbreviation CtUeReportIndBit3
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}1,
{SystemMode==64}1,
Default value
{SystemMode==32}0,
{SystemMode==0}1
Table 4-10 Configuration rule of Report flag of CT tracing message Inner Common Messages
Between RNLC and RNLU
Abbreviation CtUeReportIndBit4
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}1,
{SystemMode==64}1,
Default value
{SystemMode==32}0,
{SystemMode==0}1
Table 4-11 Configuration rule of Report flag of CT tracing message Inner Keeping Alive
Messages Between RNLC and RNLU
Abbreviation CtUeReportIndBit5
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}1,
Default value
{SystemMode==32}0,
{SystemMode==0}0
Table 4-12 Configuration rule of Report flag of CT tracing message RNLC Inner Common
Messages
Full name Report flag of CT tracing message RNLC Inner Common Messages
Abbreviation CtUeReportIndBit6
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}1,
Default value
{SystemMode==32}0,
{SystemMode==0}0
Table 4-13 Configuration rule of Report flag of CT tracing message RNLC Inner Keeping Alive
Messages
Abbreviation CtUeReportIndBit7
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}1,
Default value
{SystemMode==32}0,
{SystemMode==0}0
Table 4-14 Configuration rule of Report flag of CT tracing message RNLU Inner Information
Abbreviation CtUeReportIndBit8
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}0,
Default value
{SystemMode==32}0,
{SystemMode==0}0
Table 4-15 Configuration rule of Report flag of CT tracing message Inner Information in
Interface Board
Abbreviation CtUeReportIndBit9
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}0,
Default value
{SystemMode==32}0,
{SystemMode==0}0
Table 4-16 Configuration rule of Report flag of CT tracing message Print Information
Abbreviation CtUeReportIndBit10
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}1,
{SystemMode==64}1,
Default value
{SystemMode==32}0,
{SystemMode==0}1
Table 4-17 Configuration rule of Report flag of CT tracing message Support Layer Messages
Abbreviation CtUeReportIndBit11
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}0,
Default value
{SystemMode==32}0,
{SystemMode==0}0
Table 4-18 Configuration rule of Report flag of CT tracing message Standard Signals of TNL
Abbreviation CtUeReportIndBit12
Description report flag of CT tracing message
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
{SystemMode==128}0,
{SystemMode==64}0,
Default value
{SystemMode==32}0,
{SystemMode==0}0
Table 4-19 Configuration rule of Report flag of CT trigger process RRC connection
Abbreviation CtUeReportTrigIndBit0
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-20 Configuration rule of Report flag of CT trigger process initial transform or transform
Abbreviation CtUeReportTrigIndBit1
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Abbreviation CtUeReportTrigIndBit2
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-22 Configuration rule of Report flag of CT trigger process RAB establish
Abbreviation CtUeReportTrigIndBit3
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-23 Configuration rule of Report flag of CT trigger process RBC channel adjustment
Abbreviation CtUeReportTrigIndBit4
Table 4-24 Configuration rule of Report flag of Report flag of CT trigger process cell update
Abbreviation CtUeReportTrigIndBit5
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CtUeReportTrigIndBit6
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 0
Abbreviation CtUeReportTrigIndBit7
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-27 Configuration rule of Report flag of CT trigger process drop calls
Abbreviation CtUeReportTrigIndBit8
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-28 Configuration rule of Report flag of CT trigger process quality abnormal of user
plane
Full name Report flag of CT trigger process quality abnormal of user plane
Abbreviation CtUeReportTrigIndBit9
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-29 Configuration rule of Report flag of CT trigger process start abnormal of measure
Abbreviation CtUeReportTrigIndBit10
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-30 Configuration rule of Report flag of CT trigger process IU signal abnormal
Abbreviation CtUeReportTrigIndBit11
Description report flag of CT trigger process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
4.2.30 Report flag of CT trigger sub process RRC connect several times
Table 4-31 Configuration rule of Report flag of CT trigger sub process RRC connect several
times
Full name Report flag of CT trigger sub process RRC connect several times
Abbreviation RrcConnProBit0
Description report flag of CT trigger sub process
4.2.31 Report flag of CT trigger sub process location update, route update
or cell update
Table 4-32 Configuration rule of Report flag of CT trigger sub process location update, route
update or cell update
Abbreviation InitTransBit0
Description report flag of CT trigger sub process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-33 Configuration rule of Report flag of CT trigger sub process call establish process
Full name Report flag of CT trigger sub process call establish process
Abbreviation InitTransBit1
Description report flag of CT trigger sub process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-34 Configuration rule of Report flag of CT trigger sub process UCIU Error
Abbreviation UserPlanQualBit0
Description report flag of CT trigger sub process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-35 Configuration rule of Report flag of CT trigger sub process establish and
reconfiguration process
Abbreviation UserPlanQualBit1
Description report flag of CT trigger sub process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-36 Configuration rule of Report flag of CT trigger sub process FP fail periodically
Abbreviation UserPlanQualBit2
Description report flag of CT trigger sub process
Managed object Log Destination (LogDestination)
Table 4-37 Configuration rule of Report flag of CT trigger sub process Mono Call(TD only)
Full name Report flag of CT trigger sub process Mono Call(TD only)
Abbreviation UserPlanQualBit3
Description report flag of CT trigger sub process
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRSwitch
Description master switcher of CR
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit0
Abbreviation CRIESwitchBit1
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit2
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit3
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit4
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit5
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit6
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit7
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit8
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Abbreviation CRIESwitchBit9
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit10
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Table 4-50 Configuration rule of Switcher of CR cell - DropDetail TimteSlots And Codes
Abbreviation CRIESwitchBit11
Table 4-51 Configuration rule of Switcher of CR cell - HandOver TimteSlots And Codes
Abbreviation CRIESwitchBit12
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CRIESwitchBit13
Description switcher of CR cell
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation PGRSwitch
Description whether PRG works
Managed object Log Destination (LogDestination)
Value range 0,1
Unit NA
Default value 1
Abbreviation CDTOn
It indicates whether the Call Detail Trace (CDT) function is
Description
supported.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 0
Abbreviation CdtOption0
CDTOPTION_0: It indicates whether to report the intra-BSC
Description
handover success message. The default value is 1.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 1
Abbreviation CdtOption1
CDTOPTION_1: It indicates whether to report the PS service
Description
information. The default value is 1.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 1
Abbreviation CdtOption2
CDTOPTION_2: It indicates whether to report the location
Description
update information. The default value is 1.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 1
Abbreviation CdtOption3
Abbreviation CdtOption4
CDTOPTION_4: It indicates whether to report the access
Description
failure message. The default value is 0.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 0
Abbreviation CdtOption5
CDTOPTION_5: It indicates whether to report the signaling
Description
information when CS service fails. The default value is 0.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 0
Abbreviation CdtOption6
CDTOPTION_6: It indicates whether to report the internal
Description
message when CS service fails. The default value is 0.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 0
Abbreviation CdtOption7
CDTOPTION_7: It indicates whether to report the
Description
measurement report in location update. The default value is 0.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 0
Abbreviation CdtOption8
CDTOPTION_8: It indicates whether to report the
Description
measurement report in short message. The default value is 1.
Managed object GSM Logical Function Configuration (GBssFunction)
Table 4-64 Configuration rule of Report measurement report of normal call release
Abbreviation CdtOption9
CDTOPTION_9: It indicates whether to report the
Description measurement report after a normal call is completed. The
default value is 1.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 1
Abbreviation CdtOption10
CDTOPTION_10: It indicates whether to report the PS
Description
access failure message. The default value is 0.
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 0
Table 4-66 Configuration rule of Report recent seven MR before Ho when Ho succeed
Abbreviation CdtOption11
Description Report recent seven MR before Ho when Ho succeed
Managed object GSM Logical Function Configuration (GBssFunction)
Value range 0,1
Unit NA
Default value 1
6 Engineering Guide
This feature can be used for network planning and network optimization analysis,
system fault localization and system algorithm optimization..
After the CDT feature is enabled, the CPU load of the CMP board is increased
slightly. Based on the heavy traffic simulation test result of R&D environment, the
load of CMP board is increased by about 1% to 2% (for reference only) after the CDT
feature is enabled. The commercial environment differs from the R&D environment.
7 Abbreviation
Abbreviations Full Characteristics
rd
3GPP 3 Generation Partnership Project
CR Call Report
CT Call Trace
MS Mobile Station
8 Reference Document
User Manual of ZXM-RAP 3.00.300 On-Rack Server Software