End-To-End MS Signaling Tracing(GBSS16.0_01)

GSM BSS GBSS16.0

End-to-End MS Signaling Tracing Feature Parameter Description Issue

01

Date

2014-04-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions 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.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 01 (2014-04-30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

GSM BSS End-to-End MS Signaling Tracing Feature Parameter Description

Contents

Contents 1 About This Document.................................................................................................................. 1 1.1 Scope.............................................................................................................................................................................. 1 1.2 Intended Audience.......................................................................................................................................................... 1 1.3 Change History............................................................................................................................................................... 1

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

Issue 01 (2014-04-30)


ii


1 About This Document

1

About This Document

1.1 Scope This document describes GBFD-116401 End-to-End MS Signaling Tracing, including its technical principles, related features, and engineering guidelines.

1.2 Intended Audience This document is intended for personnel who: l

Need to understand the features described herein

l

Work with Huawei products

1.3 Change History This section provides information about the changes in different document versions. There are two types of changes, which are defined as follows: 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. Issue 01 (2014-04-30)


1


Issue 01 (2014-04-30)

1 About This Document

Change Type

Change Description

Parameter Change

Feature change

Changed the name of Huawei mobile element management system from M2000 to U2000.

None

Editorial change

None

None


2


2 Overview

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 endto-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.

2.2 NEs Supporting the Feature Table 2-1 NEs supporting the feature Feature

BSC6900

BSC6910

GBTS

eGBTS

End-to-End MS Signaling Tracing

√

√

√

√

NOTE

√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.

Issue 01 (2014-04-30)


3


3 Technical Description

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. Figure 3-1 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 Issue 01 (2014-04-30)


4


3 Technical Description

MSC_INVOKE_TRACE message, and the procedure for end-to-end MS signaling tracing on an incoming-BSC handover call is triggered through the BSC_INVOKE_TRACE message. The BSC supports end-to-end MS signaling tracing only when End2EndTraceState(BSC6900,BSC6910) is set to YES(Yes).

3.2 Procedure for End-to-End MS Signaling Tracing on an MOC in a BSC End-to-End MS Signaling Tracing is activated by the MSC. If the CM_Service_Req message received from the MS indicates that end-to-end signaling tracing is required, the MSC sends an MSC_INVOKE_TRACE message to the BSC. On receiving the message, the BSC starts end-to-end signaling tracing. The MSC_INVOKE_TRACE message contains such information as tracing ID and type of the information to be recorded. The BSC then records the associated signaling in the end-toend tracing file according to the information. The end-to-end tracing file is saved in . tmf format on the BSC LMT. Users can view the file through the interface tracing function on the BSC LMT. After the call ends, the BSC sends the end-to-end tracing file to the U2000 based on the File Transfer Protocol (FTP). The U2000 interprets and then displays a report on the U2000 client. 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.

3.3 Procedure for End-to-End MS Signaling Tracing on an Incoming-BSC Handover Call When end-to-end MS signaling tracing is performed on a call in the source BSC and the call is to be handed over to the target BSC, if SendBssInvokeTrace(BSC6900,BSC6910) is set to YES(Yes), the source BSC sends a BSC_INVOKE_TRACE message to the MSC, which then forwards the message to the target BSC. On receiving the BSC_INVOKE_TRACE message, the target BSC starts end-to-end MS signaling tracing. The source BSC sends the end-to-end tracing file to the U2000. When the call in the target BSC ends, the target BSC sends the end-to-end tracing file to the U2000. Then, the U2000 combines the two tracing files, interprets them, and displays a report on the U2000 client.

Issue 01 (2014-04-30)


5


4 Related Features

4

Related Features

Prerequisite Features Feature ID

Feature Name

Description

WOFD-190600

GBSS Enhanced Subscriber Tracing

U2000 features.

WOFD-191400

G&U CS Subscriber Tracing

Mutually Exclusive Features None

Impacted Features None

Issue 01 (2014-04-30)


6


5

5 Engineering Guidelines

Engineering Guidelines

5.1 Deploying End-to-End MS Signaling Tracing 5.1.1 Deployment Requirements Table 5-1 Deployment requirements Aspect

Requirement

Related features

See 4 Related Features.

BSC

None

BTS

None

GSM networking

None

MS

None

MSC

None

License

None

Others

The U2000 supports this feature. The core network (CN) supports this feature.

5.1.2 Activation Using MML Commands On the BSC LMT, run the SET OTHSOFTPARA command with Support End-to-end User Tracing Function set to YES(Yes) and A Interface Msg [End2end User Tracing] and Spt BSS Invoke Trace Rpt[end2end user trace] set to appropriate values. Issue 01 (2014-04-30)


7



MML Command Examples SET OTHSOFTPARA: End2EndTraceState=YES, AInterMsgTrace=YES, SENDBSSINVOKETRACE=YES;

Using the CME NOTE

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.

Step 1 Configure a single object on the CME. (CME single configuration) 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) icon on the To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click 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 Table 5-2 Configuring parameters on the CME

Issue 01 (2014-04-30)

SN

Managed Object (MO)

NE

Parameter Name

Parameter ID

Configura ble in CME Batch Modificati on Center

1

OTHSOFTP ARA

BSC6900/ BSC6910

Support End-to-end User Tracing Function

End2EndTr aceState

Yes

A Interface Msg [End2end User Tracing]

AInterMsg Trace

Spt BSS Invoke Trace Rpt[end2end user trace]

SENDBSSI NVOKETR ACE


8



5.1.3 Activation Observation Step 1 On the BSC LMT, run the LST OTHSOFTPARA command to check the value of Support End-to-end User Tracing Function. 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. Expected result: A 2G End-to-End User Trace dialog box is displayed. Step 3 In the 2G End-to-End User Trace dialog box, select a user ID type from the User ID dropdown 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 Using MML Commands On the BSC LMT, run the SET OTHSOFTPARA command with Support End-to-end User Tracing Function set to NO(No).

MML Command Examples SET OTHSOFTPARA: End2EndTraceState=NO;

Using the CME NOTE

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.

Step 1 Configure a single object on the CME. (CME single configuration) 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) icon on the To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click 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 Issue 01 (2014-04-30)


9



Table 5-3 Configuring the parameter on the CME

Issue 01 (2014-04-30)

SN

MO

NE

Parameter Name

Parameter ID

Configura ble in CME Batch Modificati on Center

1

OTHSOFTP ARA

BSC6900/ BSC6910

Support End-to-end User Tracing Function

End2EndTr aceState

Yes


10


6 Parameters

6

Parameters

Table 6-1 Parameters Parame ter ID

NE

MML Comma nd

Feature ID

Feature Name

Description

End2En dTraceS tate

BSC690 0

SET OTHSO FTPAR A

GBFD-1 16401

End-toEnd MS Signalin g Tracing

Meaning: Whether to enable end-to-end user tracing for the BSC. If this parameter is set to YES, the BSC starts end-to-end user tracing after the BSC receives the MSC Invoke Trace or BSS Invoke Trace message from the MSC. GUI Value Range: NO(No), YES(Yes) Unit: None Actual Value Range: NO, YES Default Value: NO(No)

End2En dTraceS tate

BSC691 0

SET OTHSO FTPAR A

GBFD-1 16401


Meaning: Whether to enable end-to-end user tracing for the BSC. If this parameter is set to YES, the BSC starts end-to-end user tracing after the BSC receives the MSC Invoke Trace or BSS Invoke Trace message from the MSC. GUI Value Range: NO(No), YES(Yes) Unit: None Actual Value Range: NO, YES Default Value: NO(No)

AInter MsgTra ce

BSC690 0

SET OTHSO FTPAR A

GBFD-1 16401


Meaning: Whether to trace A-interface messages during end-to-end user tracing. The end-to-end tracing is conducted throughout the network. The A-interface tracing results can be obtained from the MSC or BSC. GUI Value Range: NO(No), YES(Yes) Unit: None Actual Value Range: NO, YES Default Value: NO(No)

Issue 01 (2014-04-30)


11


6 Parameters

Parame ter ID

NE

MML Comma nd

Feature ID

Feature Name

Description

AInter MsgTra ce

BSC691 0

SET OTHSO FTPAR A

GBFD-1 16401


Meaning: Whether to trace A-interface messages during end-to-end user tracing. The end-to-end tracing is conducted throughout the network. The A-interface tracing results can be obtained from the MSC or BSC. GUI Value Range: NO(No), YES(Yes) Unit: None Actual Value Range: NO, YES Default Value: NO(No)

SendBss Invoke Trace

BSC690 0

SET OTHSO FTPAR A

GBFD-1 16401


Meaning: Whether to report BSS INVOKE TRACE message. When the parameter is set to YES, the BSC sends a BSS INVOKE TRACE message to the MSC if receiving an MSC INVOKE TRACE or BSS 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 Invoke Trace

BSC691 0

SET OTHSO FTPAR A

GBFD-1 16401


Meaning: Whether to report BSS INVOKE TRACE message. When the parameter is set to YES, the BSC sends a BSS INVOKE TRACE message to the MSC if receiving an MSC INVOKE TRACE or BSS 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)

Issue 01 (2014-04-30)


12


7 Counters

7

Counters

There are no specific counters associated with this feature.

Issue 01 (2014-04-30)


13


8 Glossary

8

Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 01 (2014-04-30)


14


9 Reference Documents

9 1.

Issue 01 (2014-04-30)

Reference Documents

3GPP TS 12.08


15

End-To-End MS Signaling Tracing(GBSS16.0_01)

Recommend Documents