Академический Документы
Профессиональный Документы
Культура Документы
GBSS16.0
Issue 01
Date 2014-04-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 3
2.1 Introduction.................................................................................................................................................................... 3
2.2 NEs Supporting the Feature............................................................................................................................................3
3 Technical Description...................................................................................................................4
3.1 Overview........................................................................................................................................................................ 4
3.2 Procedure for End-to-End MS Signaling Tracing on an MOC in a BSC....................................................................... 5
3.3 Procedure for End-to-End MS Signaling Tracing on an Incoming-BSC Handover Call...............................................5
4 Related Features.............................................................................................................................6
5 Engineering Guidelines............................................................................................................... 7
5.1 Deploying End-to-End MS Signaling Tracing............................................................................................................... 7
5.1.1 Deployment Requirements.......................................................................................................................................... 7
5.1.2 Activation.................................................................................................................................................................... 7
5.1.3 Activation Observation................................................................................................................................................9
5.1.4 Deactivation.................................................................................................................................................................9
6 Parameters..................................................................................................................................... 11
7 Counters........................................................................................................................................ 13
8 Glossary......................................................................................................................................... 14
9 Reference Documents................................................................................................................. 15
1.1 Scope
This document describes GBFD-116401 End-to-End MS Signaling Tracing, including its
technical principles, related features, and engineering guidelines.
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
01 (2014-04-30)
This issue does not include any changes.
Draft A (2014-01-23)
Compared with Issue 02 (2013-11-15) of GBSS15.0, Draft A (2014-01-23) of GBSS16.0
includes the following changes.
2 Overview
2.1 Introduction
The End-to-End MS Signaling Tracing feature helps a network administrator trace the
activities of each network element (NE) when an event occurs.
It becomes increasingly difficult to locate service faults in MSs because the communications
network becomes more and more complex. Users can detect the section where the fault occurs
only when the information about the whole process of the MS is collected. By using the end-
to-end MS signaling tracing function, the system can completely record the service activities
of an MS and then locate the section where the fault occurs. The recorded information covers
all the NEs involved in the service. If the traced objects are properly defined, valid location
information can be obtained without using a large amount of processing and transmission
resources of the system in the whole tracing process.
End-to-End MS √ √ √ √
Signaling
Tracing
NOTE
√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.
3 Technical Description
3.1 Overview
A task of end-to-end MS signaling tracing on NEs is created on the U2000. When the MS is
processing services, the NEs record the MS signaling and other information about the MS;
when the MS stops processing services, the NEs send the MS signaling and information to the
U2000 in the form of tracing file. The U2000 interprets and summarizes the tracing files and
sends the files to the MS. Figure 3-1 shows the end-to-end MS signaling tracing procedure.
End-to-End MS Signaling Tracing is activated at the MSC. The procedure for end-to-end MS
signaling tracing on a mobile originated call (MOC) is triggered through the
NOTE
End-to-end MS signaling tracing is conducted throughout the network. Therefore, the A-interface
tracing result can be obtained from the MSC or BSC. When AInterMsgTrace(BSC6900,BSC6910) is set
to YES(Yes), the BSC can trace A-interface messages during end-to-end MS signaling tracing.
4 Related Features
Prerequisite Features
Feature ID Feature Name Description
Impacted Features
None
5 Engineering Guidelines
Aspect Requirement
BSC None
BTS None
MS None
MSC None
License None
5.1.2 Activation
When configuring the End-to-End MS Signaling Tracing feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 5-2. For the method of performing the CME single configuration, see the
CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on the
CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
A Interface AInterMsg
Msg Trace
[End2end
User
Tracing]
Expected result: The value of Support End-to-end User Tracing Function is Yes.
Step 2 On the U2000, choose Monitor > Signaling Trace > Signaling Trace Management from the
main menu. In the navigation tree, double-click 2G End-to-End User Trace.
Step 3 In the 2G End-to-End User Trace dialog box, select a user ID type from the User ID drop-
down list and enter the user ID. Then, click OK.
Expected result: The U2000 generates a report on the end-to-end MS signaling tracing.
----End
5.1.4 Deactivation
When configuring the End-to-End MS Signaling Tracing feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 5-3. For the method of performing the CME single configuration, see the
CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on the
CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
6 Parameters
End2En BSC690 SET GBFD-1 End-to- Meaning: Whether to enable end-to-end user tracing
dTraceS 0 OTHSO 16401 End MS for the BSC. If this parameter is set to YES, the BSC
tate FTPAR Signalin starts end-to-end user tracing after the BSC receives
A g the MSC Invoke Trace or BSS Invoke Trace message
Tracing from the MSC.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
End2En BSC691 SET GBFD-1 End-to- Meaning: Whether to enable end-to-end user tracing
dTraceS 0 OTHSO 16401 End MS for the BSC. If this parameter is set to YES, the BSC
tate FTPAR Signalin starts end-to-end user tracing after the BSC receives
A g the MSC Invoke Trace or BSS Invoke Trace message
Tracing from the MSC.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
AInter BSC690 SET GBFD-1 End-to- Meaning: Whether to trace A-interface messages
MsgTra 0 OTHSO 16401 End MS during end-to-end user tracing. The end-to-end tracing
ce FTPAR Signalin is conducted throughout the network. The A-interface
A g tracing results can be obtained from the MSC or BSC.
Tracing GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
AInter BSC691 SET GBFD-1 End-to- Meaning: Whether to trace A-interface messages
MsgTra 0 OTHSO 16401 End MS during end-to-end user tracing. The end-to-end tracing
ce FTPAR Signalin is conducted throughout the network. The A-interface
A g tracing results can be obtained from the MSC or BSC.
Tracing GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
SendBss BSC690 SET GBFD-1 End-to- Meaning: Whether to report BSS INVOKE TRACE
Invoke 0 OTHSO 16401 End MS message. When the parameter is set to YES, the BSC
Trace FTPAR Signalin sends a BSS INVOKE TRACE message to the MSC if
A g receiving an MSC INVOKE TRACE or BSS
Tracing INVOKE TRACE message from MSC in the case of
an outgoing BSC handover. If the BSC does not
receive the message, the BSC does not send a BSS
INVOKE TRACE message to the MSC.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
SendBss BSC691 SET GBFD-1 End-to- Meaning: Whether to report BSS INVOKE TRACE
Invoke 0 OTHSO 16401 End MS message. When the parameter is set to YES, the BSC
Trace FTPAR Signalin sends a BSS INVOKE TRACE message to the MSC if
A g receiving an MSC INVOKE TRACE or BSS
Tracing INVOKE TRACE message from MSC in the case of
an outgoing BSC handover. If the BSC does not
receive the message, the BSC does not send a BSS
INVOKE TRACE message to the MSC.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
7 Counters
8 Glossary
9 Reference Documents
1. 3GPP TS 12.08