Interface Features(GBSS14.0 01)

Interface Interface Features GBSS14.0

Feature Parameter Description

Issue

01

Date

2012-04-28

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Copyright © Huawei Technologies Technologies Co., Ltd. 2012. 201 2. 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 Trademarks and Permissions Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned mentioned in this document are the property 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 the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

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

Website:

http://www.huawei.com

Email:

[email protected]

GSM BSS Interface Features

Contents

Contents 1 Introduction .....................................................................................................................................1-1 1.1 Scope ...................................................................................................................................... 1-1 1.2 Intended Audience ................................................................................................................... 1-1 1.3 Change History ........................................................................................................................ 1-1

2 Ater Interface 4:1 Multiplexing ..................................................................................................2-1 2.1 Overview.................................................................................................................................. 2-1 2.2 Technical Description ............................................................................................................... 2-1 2.3 Networking............................................................................................................................... 2-2

3 A Interface Circuit Management ............................................................................................... 3-1 3.1 Overview.................................................................................................................................. 3-1 3.2 Technical Description ............................................................................................................... 3-1 3.2.1 Circuit Assignment ........................................................................................................... 3-1 3.2.2 Circuit Block..................................................................................................................... 3-1 3.2.3 Circuit Unblock................................................................................................................. 3-2 3.2.4 Group Circuit Block ........................................................................................................... 3-3 3.2.5 Group Circuit Unblock ........................................................................................................ 3-3 3.2.6 Circuit Unequipped........................................................................................................... 3-4 3.2.7 Circuit Reset ...................................................................................................................... 3-5

4 A Interface Protocol Process ..................................................................................................... 4-1 4.1 Overview.................................................................................................................................. 4-1 4.2 The Direct Transfer Application Part ......................................................................................... 4-1 4.3 The BSS Management Application Part .................................................................................... 4-1 4.4 BSSMAP Procedures ............................................................................................................... 4-1

5 A Interface Occupation Rate Monitoring ............................................................................... 5-1 5.1 Overview.................................................................................................................................. 5-1 5.2 Technical Description ............................................................................................................... 5-1

6 Parameters .......................................................................................................................................6-1 7 Counters ........................................................................................................................................... 7-1 8 Glossary ............................................................................................................................................ 8-1 9 Reference Documents.................................................................................................................. 9-1

Issue 01 (2012-04-28)

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

ii


1 Introduction

1 Introduction 1.1 Scope This document describes functions provided by the interface features, including Ater Interface 4:1 Multiplexing, A Interface Circuit Management, A Interface Protocol Process , A Interface Occupation Rate Monitoring.

1.2 Intended Audience This document is intended for: 

Personnel who need to understand interface features



Personnel who work with Huawei products

1.3 Change History This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: 

Feature change: refers to the change in the interface features of a specific product version.



Editorial change: refers to the change in wording or the addition of the information that was not described in the earlier version.

Document Issues The document issues are as follows: 

01 (2012-04-28)



Draft A (2012-02-15)

01 (2012-04-28) This is the first official release of GBSS14.0. Compared with issue Draft A (2012-02-15), 01 (2012-02-15) h as no change.

Draft A (2012-02-15) This is a draft. Compared with issue 01 (2011-03-31) of GBSS13.0, Draft A (2012-02-15) of GBSS14.0 h as no change.

Issue 01 (2012-04-28)


1-1


2 Ater Interface 4:1 Multiplexing

2 Ater Interface 4:1 Multiplexing 2.1 Overview The transmission cost is very high in network deplo yment. Operators seek proper technologies to decrease the required transmission bandwidth, therefore reducing the transmission cost. Meanwhile, the transmission quality must be guaranteed. To achieve that purpose, Ater interface multi plexing is introduced and the BM/TC separated mode is applied. That is, multiplexing on the Ater interface is i mplemented when the TC is configured on the MSC side. In this manner, the transmi ssion cost is reduced significantly. Huawei BSC supports 4:1 multiplexing on the Ater interface by means of the TC (TRAU). That is, the four timeslots on the E1 of the A interface can be multiplexed onto a times lot on the Ater interface by means of the TC. In this process, the previous PCM frame of 64 kbit/s can be c onverted into the TRAU frame of 16 kbit/s, an d therefore reducing the required transmission bandwidth. (GBFD-111801 Ater Interface 4:1 Multiplexing)

2.2 Technical Description In the telephone exchange network, the voice coding scheme is Pulse Code Modulation (PCM) and the rate is 64 kbit/s. According to GSM specifications, PCM must be applied on the A interface. To save the radio channel resources, data transmission between the MS and the BTS adopts the voice coding scheme RPE-LTP or CELP whose rate is 13 kbit/s (16 kbit/s for transmission) or other coding schemes with an even lower rate(for e xample, 8 kbit/s). If a call s ervice attempts to be set up between the MS and the MSC, the voice codec is converted from 13 kbit/s codec to 64 kbit/s codec. The voice codec conversion is implemented in the TC (TRAU) unit. Before the conversion, the voices are exchanged and transmitted on the 16-kbit/s channels in the BSC. The Ater interface is an internal interface between the TC process ing unit and the service processing module (BM). Figure 2-1 shows the interfaces between network elements (NEs). Figure 2-1 Interfaces between NEs

On the Ater interface, Huawei BSC supports 4:1 multiplexing. That is, the four timeslots on the E1 of the A interface can be multiplexed onto a timeslot on the Ater interface. Figure 2-2 shows 4:1 multiplexing on the Ater interface.

Issue 01 (2012-04-28)


2-1


2 Ater Interface 4:1 Multiplexing

Figure 2-2 4:1 multiplexing on the Ater interface 16K 64K TS

1 2

1

3

BM

4

TC

3 4

Ater

A

On the Ater interface, Huawei BSC supports the multiplexing of four voice chan nels to an E1 timeslot of 64 kbit/s. When the TC subrack is configured on the MSC side, the remote transmission resource can be saved by 75%. Huawei introduces a new feature of resource pool and integrates it into the BSC. With this feature, links on the Ater interface work in resource pool mode and can be inconsistent with the CICs on the A interface. This improves the network reliability. The resources on the Ater interface involve the timeslots of 16 kbit/s and 8 kbit/s. When a call connection is established, according to the service type, the Ater tim eslots of 16 kbit/s are used i f the TCHs/F are allocated on the Um interface; the Ater timeslots of 8 kbit/s are used if the TCHs/H are all ocated on the Um interface. In this way, the resources on the Ater interface can be full y utilized and the resources can be saved by over 75%.

2.3 Networking Huawei provides a flexible networking solution for operators. That is, the TC can be configured on either the BSC side or the MSC side. Ater Interface 4:1 Multiplexing can be used together with TC pool. Ater Interface 4:1 Multiplexing can be used on the TDM-based A interface but not on the IP-based A interface. The transmission resources on the TDM-based Ater interface are planned to be 25% of the total interface transmission capacity.

Issue 01 (2012-04-28)


2-2


3 A Interface Circuit Management

3 A Interface Circuit Management 3.1 Overview A Interface Circuit Management improves the network quality by ensuring a high success rate of call establishments and handovers, and providing value-added s ervices for telecom operators in terms of operation, maintenance, and transmission quality. Huawei GBSS provides operators with the function of ci rcuit management through the LMT, which facilitates operators to remotely perform operation and maintenance on the TC, such as locating faults on the TC. Circuit management helps improve the efficiency of and reduce the investment on operation and maintenance on the TC. Huawei GBSS supports A interface circuit management regardless of whether the TC is locally or remotely configured. Huawei GBSS also supports the blocking and unblocking of a single terrestrial circuit or group terrestrial circuits in the case of operations on the LMT or a device fault. The BSC re-sends BLOCK, UNBLOCK, GROUP BLOCK, GROUP UNBLOCK, and RES ET CIRCUIT messages to the MSC if the BSC does not receive an acknowledgement message from the MSC within the timer set at the BSC. In addition, the function of circuit unequipped is supported. A Interface Circuit Management, which involves circuit assignment, circuit block, circuit unblock, group circuit block, group circuit unblock, circuit unequipped, and circuit reset, controls the operation and maintenance on a single circuit or on the entire PCM group circuits for the terrestrial circuit equipment. A Interface Circuit Management applies to only the TDM network. (GBFD-111803 A Interface Circuit Management)

3.2 Technical Description 3.2.1 Circuit Assignment During a call or handover procedure, the MSC carri es the information about requested resource(s) in the Assignment Request or Handover Request Message. If the requested resource(s) is/are for speech or data, it also may indicate the terrestri al circuit that shall be used between the MSC and BSS. The BSC assigns and occupies the A interface circuit as indicated in the signaling from the MSC. If the A interface circuit is successfully assigned and occupied, the BSC sends t he MSC a message, indicating that the A interface circuit assignment is complete. If the A interface circuit indicated by the MSC is unavailable or blocked at the BSC, the BSC sends the MSC a message, indicating that the A interface circuit assignment fails. In addition, the B SC informs the MSC that the A interface circuit is unavailable in the circuit block procedure. If the A interface circuit indicated by the MSC does not exist at the B SC, the BSC sends the MSC a message, indicating that the A interface cir cuit assignment fails. In addition, the BSC informs the MSC that the A interface circuit does not exist in the circuit unequipped procedure.

3.2.2 Circuit Block In the circuit block procedure, the BSC sends the MSC a BLOCK message, indicating that the circuit at the BSS is unavailable. The BLOCK message contains the Circuit Identification Code (CIC) that identifies the circuit over the A interface. In this way, the state of the circuit at the BSC and that of the circuit at the MSC are consistent. Figure 3-1 shows the procedure for circuit block.

Issue 01 (2012-04-28)


3-1



Figure 3-1 Procedure for circuit block BSC

MSC

BLOCK

BLOCK ACK

Through circuit block, the circuit at the BSS and that at the MSC are blocked at the same time. The procedure for circuit block can be triggered by running the MOD AE1T1 command and setting OPMODE to MODSTARTCIC(Mod Start CIC) in the case of circuit assignment, handover, or device fault. The BSC sends BLOCK ACK messages to the MSC repeatedly at an inter val until the BSC receives a BLOCK ACK message from the MSC. The interval can be set by setting AT 1 in the SET BSCTMR command. The circuit at the BSC is blocked even if the BSC does not recei ve any BLOCK ACK message from the MSC. The circuit is blocked after a call ends. Therefore, circuit block does not affect the circuit on call.

3.2.3 Circuit Unblock In the circuit unblock procedure, the BSC sends the MSC a message, informing the MSC of the latest circuit state at the BSC, when a fault y is rectified or a circuit becomes available at the BSC. The UNBLOCK message contains a CIC that identifies the circuit over the A interface. Figure 3-2 shows the procedure for circuit unblock. Figure 3-2 Procedure for circuit unblock BSC

MSC

UNBLOCK

UNBLOCK ACK

Through circuit unblock, the blocked circuit at the BSC becomes idle. The procedure for circui t unblock can be triggered by running the MOD AE1T1 command and setting O P M O D E to MODSTARTCIC(Mod Start CIC) on the LMT.

Issue 01 (2012-04-28)


3-2



The BSC sends UNBLOCK messages to the MSC repeatedl y at an interval until the BSC recei ves an UNBLOCK ACK message from the MSC. The interval can be set by setting AT 1 in the SET BSCTMR command. The circuit at the BSC is idle even if the BSC does not recei ve any UNBLOCK ACK message from the MSC.

3.2.4 Group Circuit Block Group circuit block is used when multiple A interface circuits need to be blocked at the same time. The GROUP BLOCK message contains multiple CICs that identify the circuits over the A interface. Figure 3-3 shows the procedure for group circuit block. Figure 3-3 Procedure for group circuit block BSC

MSC

GROUP BLOCK

GROUP BLOCK ACK

Through group circuit block, multiple A interface circuits can be blocked at the same time. The procedure for group circuit unblock can be triggered by running the MOD AE1T1 command and setting O P M O D E to MODSTARTCIC(Mod Start CIC) on the LMT. Group circuit block applies to only GSM Phase II and GSM Phase II Plus. The BSC sends GROUP BLOCK messages to the MSC repeatedly at an interval until the BSC receives a GROUP BLOCK ACK message from the MSC. The interval can be set by setting AT20 in the SET BSCTMR command. The circuits at the BSC are blocked even if the BSC does not receive any GROUP BLOCK ACK message from the MSC. The circuits are blocked after a call ends. Therefore, group circuit block does not affect the circuits on call.

3.2.5 Group Circuit Unblock Group circuit unblock is used when multiple A interface circuits need to be unbl ocked at the same time. The GROUP UNBLOCK message contains multiple CICs that identify the circ uits over the A interface. Figure 3-4 shows the procedure for group circuit unblock.

Issue 01 (2012-04-28)


3-3



Figure 3-4 Procedure for group circuit unblock BSC

MSC

GROUP UNBLOCK

GROUP UNBLOCK ACK

Through group circuit unblock, multiple A interface circuits can be unblocked at the same time. The procedure for group circuit unblock can be triggered by running the MOD AE1T1 command and setting O P M O D E to MODSTARTCIC(Mod Start CIC) on the LMT. Group circuit unblock applies to only GSM Phase II and GSM Phase II Plus. The BSC sends GROUP UNBLOCK messages to the MSC repeatedl y at an interval until the BSC receives a GROUP UNBLOCK ACK message from the MSC. The interval can be set by setting AT20 in the SET BSCTMR command. The circuits at the BSC are idl e even if the BSC does not receive an y GROUP UNBLOCK ACK message from the MSC.

3.2.6 Circuit Unequipped The BSC sends the MSC an UNEQUIPPED CIRCUIT message if the required ci rcuit indicated by the MSC does not exist in the following processes: 

Circuit block



Circuit unblock



Circuit reset



Circuit assignment



Incoming-BSC handover



BSC reset

Figure 3-5 shows the procedure for circuit unequipped. Figure 3-5 Procedure for circuit unequipped BSC

MSC

UNEQUIPPED CIRCUIT

Through the circuit unequipped procedure, the BSC informs the MSC that the indicated circuit does not exist and requires the MSC not to use th e circuit. The BSC triggers the circuit unequipped procedure in any circuit-associated procedure as long as the BSC receives a message that carries the information

Issue 01 (2012-04-28)


3-4



element (IE) about unequipped ci rcuit from the MSC. Circuit unequipped applies to onl y GSM Phase II and GSM Phase II Plus. There is no acknowledgement message in response to the UNEQUIPPED CIRCUIT message in the circuit unequipped procedure. In addition, th e BSC sends the UNEQUIPPED CIRCUIT message to the MSC only once.

3.2.7 Circuit Reset After part of a system fails, for example, the SCCP link is released abnormally, the circuit at the BSC or MSC can be restored through circ uit reset. If a circuit is idle after the SCCP link i s released abnormally, the BSC sends a RESET CIRCUIT message to the MSC. Figure 3-6 shows the procedure for circuit res et initiated by the BSC. Figure 3-6 Procedure for circuit reset BSC

MSC

RESET CIRCUIT

RESET CIRCUIT ACK

After receiving a RESET CIRCUIT message from the BSC, the MSC removes all the calls on the circuit and sets the circuit to idle, and then sends a RESET CIRCUIT ACK message to the BSC. If the BSC does not recei ve the RESET CIRCUIT ACK message from the MSC, it re-sends a RESET CIRCUIT message to the MSC onl y once at an interval. The interval can be set by setting AT19 in the SET BSCTMR command. The circuit at the BSC is idle even if the BSC does not receive any RESET CIRCUIT ACK message from the MSC. The procedure for circuit reset c an be triggered by running the R ST ACIC command on the LMT.

Issue 01 (2012-04-28)


3-5


4 A Interface Protocol Process

4 A Interface Protocol Process 4.1 Overview The underlying transport mechanism defined to carr y signalling information between the BSS and the MSC is the Message Transfer Part (MTP), and the Signalling Connection Control Part (SCCP) of Signalling System No.7. (GBFD-111804 A Interface Protocol Process) The MTP and SCCP are used to support communication between the MSC and the conceptual entities within the BSS, the BSS Application Part (BSSAP).The BSS Application Part is split into two sub application parts, these are: 

The Direct Transfer Application Part (DTAP);



The BSS Management Application Part (BSSMAP).

4.2 The Direct Transfer Application Part The Direct Transfer Application Part (DTAP) is used to transfer call control and mobility management messages between the MSC and the MS. 

Mobility management (MM) messages consist of the messages related to the authentification, CM service request, identification request, IMSI detach, location update, MM status, and TMSI re-assignment.



Call control (CC) messages consist of the messages related to the alerting, cal l proceding, connection, establishment, modification, release, disconnection, notification, status query, and DTMF startup.

The DTAP information in these messages is not interpreted by the BSS.

4.3 The BSS Management Application Part The BSSMAP supports all of the procedures between the MSC and the BSS that require interpretation and processing of information related to single calls, and resource management.

4.4 BSSMAP Procedures This sub-clause describes the procedures used in the BSS Management Application Part. There are the following main procedures: Assignment Blocking Reset Handover required indication Handover resource allocation Handover execution Handover candidate enquiry Release Paging Flow control

Issue 01 (2012-04-28)


4-1


4 A Interface Protocol Process

Classmark update Cipher mode control Trace invocation Initial MS message Queuing indication Data link control SAPI not equal to 0 Reset circuit Location Aquisition Connectionless Information Transfer Common ID

When TCH congestion is present in a cell, BSC starts load indication procedure, sending LOAD INDICATION message towards MSS. The period of this message is 110 seconds per cell. And the triggering condition is that all TCH channels have been occupied. LOAD INDICATION message is sent in the flow control of BSSMAP procedures.

Issue 01 (2012-04-28)


4-2


5 A Interface Occupation Rate Monitoring

5 A Interface Occupation Rate Monitoring 5.1 Overview This feature monitors the real -time status and usage of the circuits on the A interface and TC resources through performance measurement. (GBFD-111805 A Interface Occupation Rate Monitoring) This feature is an important feature for ensuring the network quality. It provides the following benefits for the operators: 

Learn the usage of the circuit resources of the A interface in time, thus providing a basis for the s ystem capacity expansion.



Know about the distribution status of the circuit resources of the A interface in time. Coordinate the configuration of transmission resources among networks. Add, reduce, and re-al locate the transmission resources on the basis of the usage of resources, thus reducing the network operation cost.



Find the defects of the network planning, thus improving the principles and methods of the existing network planning.

5.2 Technical Description This feature is implemented through performance measurement of the BSC. This feature monitors the usage of the circuits on the A interface and TC resources in different states through performance measurement of the BSC. The m onitoring result helps the operator know better about the usage of present resources. The counters used in this feature are classified into following types: 

Counters about the timeslot usage on the A interface



These counters provide the occupation tim es, occupation duration, and work status of each timeslot (TS1 to TS31) in the trunk circuit over the A interface. These counters are helpful to A interface circuit troubleshooting.



Counters about the circuit resources on the A interface



These counters provide the circuits in faulty, idle, uninstalled, maintenance, blocked, bus y, and peer-uninstalled state. If the A interface circuits are i n various states, the respective number of circuits in each state are measured and the results are provided in the sequence of local-uninstalled, busy, maintenance (faulty and blocked), faulty, peer-uninstalled, blocked, and idle.



Counters about TC resources in the BM and TC s ubracks



These counters provide the number f aulty, idle, bus y, maintenance, and prohibit ed TC resources in the BM and TC subracks. If the TC resources are in various states, the respecti ve number of TC resources in each state are measured and the results are provided in the sequence of busy, maintenance(faulty and blocked), fault y, blocked an d idle. NOTE

In TC pool mode, the TC resources can be differentiated by their BSC IDs The main BSC calculates all TC resources in all TC subracks. TC resources that are in the maintenance(faulty and blocked), faulty, blocked, and idle state in TC subracks belong to the main BSC; whereas the TC resources that are in the busy state in TC subracks belong to their respective BSCs. The secondary BSCs calculate the TC resources in their respective BM subracks.

Issue 01 (2012-04-28)


5-1


6 Parameters

6 Parameters Table 6-1 Parameter description Parameter ID

NE

MML Command

Description

AT1

BSC6900

SET BSCTMR

Meaning: Timer for waiting for a single A-interface circuit blocking or unblocking answer. The BSC6900 starts this T1 timer after sending a single A-interface circuit blocking or unblocking message. If the BSC6900 does not receive a blocking or unblocking answer from the MSC before this timer expires for the first time, the BSC6900 resends the single A-interface circuit blocking or unblocking message to the MSC. If the timer expires for the second time, the BSC6900 reports an alarm for BSC circuit blocking or unblocking failure. GUI Value Range: 1~300 Actual Value Range: 1~300 Default Value: 30 Unit: s

Issue 01 (2012-04-28)


6-1


6 Parameters

Parameter ID

NE

MML Command

Description

AT19

BSC6900

SET BSCTMR

Meaning: Timer for waiting for an A-interface circuit reset answer. The BSC6900 starts this timer after sending an A-interface circuit reset message. When this timer expires for the first time, the BSC6900 resends the circuit reset message to the MSC. If this timer expires for the second time, the BSC6900 reports an alarm for BSC circuit resetting failure. GUI Value Range: 1~300 Actual Value Range: 1~300 Default Value: 30 Unit: s

AT20

BSC6900

SET BSCTMR

Meaning: Timer for waiting for an A-interface circuit group blocking or unblocking answer. After sending a CIC group blocking/unblocking message over the A interface, the BSC6900 starts the timer T20. If the BSC6900 fails to receive a response from the MSC before the first expiry of T20, the BSC6900 resends the CIC group blocking/unblocking message. If no response is received before the second expiry of T20, the system reports the BSC Unable to Block Group Circuits or BSC Unable to Unblock Group Circuits alarm. GUI Value Range: 1~300 Actual Value Range: 1~300 Default Value: 30 Unit: s

Issue 01 (2012-04-28)


6-2


6 Parameters

Parameter ID

NE

MML Command

Description

OPMODE

BSC6900

MOD AE1T1

Meaning: Value MODSTARTCIC indicates modifying the start CIC of the E1/T1 timeslots on the A interface. Value MODSGLCIC indicates modifying the CIC of an E1/T1 timeslot on the A interface. GUI Value Range: MODSTARTCIC(Mod Start CIC), MODSGLCIC(Mod Single CIC) Actual Value Range: MODSTARTCIC, MODSGLCIC Default Value: None Unit: None

Issue 01 (2012-04-28)


6-3


7 Counters

7 Counters Table 7-1 Counter description Counter ID

Counter Name

Counter Description Feature ID

1276270419

BS.A.INTFACE.UNINSTALL.CIC.AVG

AL0050:Mean number GBFD-111803 of uninstalled circuits on the A interface

1276270422

BS.A.INTFACE.FAULT.CIC.AVG

AL0051:Mean number GBFD-111803 of faulty circuits on the A interface

1276270425

BS.A.INTFACE.MAINTAIN.CIC.AVG

AL0052:Mean number GBFD-111803 of circuits in maintenance state on the A interface

1276270428

BS.A.INTFACE.OAMBLOCK.CIC.AVG

AL0053:Mean number GBFD-111805 of blocked circuits on the A interface

1276270431

BS.A.INTFACE.IDLE.CIC.AVG

AL0054:Mean number GBFD-111805 of idle circuits on the A interface

1276270434

BS.A.INTFACE.BUSY.CIC.AVG

AL0055:Mean number GBFD-111805 of busy circuits on the A interface

1276270437

BS.A.INTFACE.PEER.UNINSTALL.CIC.AVG AL0089:Mean number GBFD-111803 of circuits with uninstalled peer circuits on the A interface

1276370419

BS.A.INTFACE.BUSY.TS1.SUMAVR

AL0001:Average busy GBFD-111805 time of A interface Ts(s)

1276370422


AL0002:Average busy GBFD-111805 time of Ts2(s)

1276370425



1276370428



1276370431



1276370434



1276370437



Issue 01 (2012-04-28)


7-1


7 Counters

Counter ID

Counter Name


1276370440



1276370443



1276370446



1276370449



1276370452



1276370455



1276370458



1276370461



1276370464



1276370467



1276370470



1276370473



1276370476



1276370479



1276370482



1276370485



1276370488



1276370491



1276370494



Issue 01 (2012-04-28)


7-2


7 Counters

Counter ID

Counter Name


1276370497



1276370500



1276370503



1276370506



1276370509



1277069417

BS.A.MSC.RST

L0056A:Number of MSC Resets

GBFD-111804

1282411686

CELL.WAIT.CC.TIMEOUT

CA306:Timeouts Waiting MSC's CC Message

GBFD-111804

1282423588

BS.RES.FAULT.ATER.AVG

AL1256:Mean number GBFD-111801 of faulty circuits on the Ater interface

1282423589

BS.RES.OAMBLOCK.ATER.AVG

AL1258:Mean number GBFD-111801 of blocked circuits on the Ater interface

1282423590

BS.RES.MAINTAIN.ATER.AVG

AL1257:Mean number GBFD-111801 of circuits in maintenance state on the Ater interface

1282423591

BS.RES.IDLE.ATER.AVG

AL1259:Mean number GBFD-111801 of idle circuits on the Ater interface

1282423592

BS.RES.BUSY.ATER.AVG

AL125A:Mean number GBFD-111801 of busy circuits on the Ater interface

1282423987

MTP2.LNK.RATIO.TX

RL9808:Transmission GBFD-111804 bandwidth usage of the WRFD-010101 MTP2 link

1282423988

MTP2.LNK.RATIO.RX

RL9809:Receiving GBFD-111804 bandwidth usage of the WRFD-010101 MTP2 link

67178833

OS.SCCP.Tx.UDTS.Msg

T6228:Number of GBFD-111804 UDTS Messages Sent WRFD-010101 by the SCCP

Issue 01 (2012-04-28)


7-3


7 Counters

Counter ID

Counter Name


67178834

OS.SCCP.Rx.UDTS.Msg

T6229:Number of GBFD-111804 UDTS Messages WRFD-010101 Received by the SCCP

67178835

OS.SCCP.HandleTotalMsg

T6230:Number of GBFD-111804 Messages Handled by WRFD-010101 the SCCP from the Local or Remote End

67178836

OS.SCCP.HandleLocalSSNMsg

T6231:Number of GBFD-111804 Messages Sent by the WRFD-010101 SCCP to the Local Subsystem

67178837

OS.SCCP.Tx.Msg.0.1

T6232:Number of Connectionless Messages Sent by SCCP

GBFD-111804

T6233:Number of Connectionless Messages Received by SCCP

GBFD-111804

T6235:Number of Class 2 Messages Sent by SCCP

GBFD-111804

T6234:Number of Class 2 Messages Received by SCCP

GBFD-111804

T6201:Number of SCCP Connection Release Expiry

GBFD-111804

T6202:Number of SCCP Connection Releases Due to SCCP Inactivity Test Timeout

GBFD-111804

67178838

67178839

67178840

67178881

67178882

OS.SCCP.Rx.Msg.0.1

OS.SCCP.Tx.Msg.2

OS.SCCP.Rx.Msg.2

OS.SCCP.Fail.Rel.Cmp

OS.SCCP.TiarTimeout

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

67178883

OS.SCCP.ProvInitRel

T6203:Number of GBFD-111804 NSP-Initiated SCCP WRFD-010101 Connection Releases Received by SCCP

67178884

OS.SCCP.SegmenFail

T6204:Number of GBFD-111804 SCCP XUDT WRFD-010101 segmentation Failures

Issue 01 (2012-04-28)


7-4


7 Counters

Counter ID

Counter Name


67178885

VS.SCCP.Rx.RLSD.SubsFail

T6205:Number of Connection Release (RLSD) Messages Received by SCCP with the Cause of Subsystem Faults

GBFD-111804 WRFD-010101

67178886

VS.SCCP.Rx.RLSD.MtpFail

T6206:Number of GBFD-111804 RLSD Messages WRFD-010101 Received by SCCP with the Cause of MTP Faults

67178887

VS.SCCP.Rx.RLSD.Cong

T6207:Number of RLSD Messages Received by SCCP with the Cause of Network Congestion

GBFD-111804 WRFD-010101

67178888

VS.SCCP.Rx.RLSD.Other

T6208:Number of GBFD-111804 RLSD Messages WRFD-010101 Received by the SCCP for Other Abnormal Causes except for Subsystem Faults, MTP Faults, and Network Congestion

67178890

VS.SCCP.Rx.XUDTS.ErrorMsg

T6211:Number of XUDTS Messages Received by SCCP with the Cause of Transmission Error

GBFD-111804 WRFD-010101

67178891

VS.SCCP.Rx.UDTS.FragFail

T6212:Number of GBFD-111804 UDTS and XUDTS WRFD-010101 Messages Received by SCCP with the Cause of Segmentation Failure

67178896

OS.SCCP.RouteFail.DSP.Unavai

T6219:Number of SCCP Routing Failures (Destination Signaling Point Inaccessible)

GBFD-111804

T6220:Number of SCCP Routing Failures (Subsystem Faults)

GBFD-111804

67178897

OS.SCCP.RouteFail.SSNFail

Issue 01 (2012-04-28)


WRFD-010101

WRFD-010101

7-5


7 Counters

Counter ID

Counter Name


67178898

OS.SCCP.RouteFail.SSNUnequip

T6221:Number of SCCP Routing Failures (Subsystem Uninstalled)

GBFD-111804

T6227:Number of SCCP Routing Failures (Unknown Causes)

GBFD-111804

T6125:Number of MTP3 Link Remote Processor Failures

GBFD-111804

T6214:Number of ERROR PDU Messages Received by SCCP

GBFD-111804

T6215:Number of ERROR PDU Messages Sent by SCCP

GBFD-111804

67178899

67184091

67190756

67190757

OS.SCCP.RouteFail.Unkown

OS.MTP3.Lnk.Rpos

VS.SCCP.Rx.ErrPDU

VS.SCCP.Tx.ErrPDU

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

67195059

VS.SCCP.RX.RLSD.NORMAL

T6209:Number of GBFD-111804 RLSD Messages WRFD-010101 Received by the SCCP for Normal Causes

67196163

OS.MTP3.DSP.Unavail

T6101:Number of MTP3 Destination Signaling point Failures

GBFD-111804 WRFD-010101

67196164

OS.MTP3.DSP.Unavail.Dur

T6102:Duration of GBFD-111804 MTP3 Destination WRFD-010101 Signaling point Failure

67196165

OS.MTP3.Lnk.Service.Dur

T6111:Service GBFD-111804 Duration of MTP3 Link WRFD-010101

67196166

OS.MTP3.Lnk.Fail

T6112:Number of MTP3 Link Failures

GBFD-111804 WRFD-010101

67196167

OS.MTP3.Lnk.Fail.Dur

T6113:Out-of-Service GBFD-111804 Duration of MTP3 Link WRFD-010101

67196168

OS.MTP3.Lnk.Cong.Dur

T6114:Duration of GBFD-111804 MTP3 Link Congestion WRFD-010101

67196169

OS.MTP3.Lnk.LocalInhibit

T6115:Number of Local Inhibitions on MTP3 Link

Issue 01 (2012-04-28)


GBFD-111804 WRFD-010101

7-6


7 Counters

Counter ID

Counter Name


67196170

OS.MTP3.Lnk.LocalInh.Dur

T6116:Duration of Local Inhibition on MTP3 Link

GBFD-111804 WRFD-010101

67196171

OS.MTP3.Lnk.RmtInhibit

T6117:Number of GBFD-111804 Remote Inhibitions on WRFD-010101 MTP3 Link

67196172

OS.MTP3.Lnk.RmtInhibit.Dur

T6118:Duration of Remote Inhibition on MTP3 Link

GBFD-111804

T6119:Number of MTP3 Link Changeovers

GBFD-111804

T6120:Number of Signaling Units Sent on MTP3 Link

GBFD-111804

T6121:Number of Signaling Units Received on MTP3 Link

GBFD-111804

T6122:Number of MTP3 Link Congestions

GBFD-111804

T6123:Number of Bytes of SIO and SIF Sent on MTP3 Link

GBFD-111804

T6124:Number of Bytes of SIO and SIF Received by MTP3 Link

GBFD-111804

T6126:Number of Messages Discarded on MTP3 Link Due to Link Congestion

GBFD-111804

T6127:Number of Transfer-Prohibited Signals Received on MTP3 Link

GBFD-111804

T6128:Number of Messages Discarded on MTP3 Link Due to Route Fail

GBFD-111804

67196173

67196174

67196175

67196176

67196177

67196178

67196179

67196180

67196181

OS.MTP3.Lnk.Cho

OS.MTP3.Lnk.Tx.Msg

OS.MTP3.Lnk.Rx.Msg

OS.MTP3.Lnk.ConG

OS.MTP3.Lnk.SIO.SIF.Tx

OS.MTP3.Lnk.SIO.SIF.Rx

OS.MTP3.Lnk.Discard.Msg.Cong

OS.MTP3.Lnk.Rx.TFP

OS.MTP3.Lnk.Discard.Msg.RouteFail

Issue 01 (2012-04-28)


WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

WRFD-010101

7-7


7 Counters

Counter ID

Counter Name


67196182

OS.MTP3.Lnk.Rx.TFC

T6129:Number of Transfer-Controlled Signals Received on MTP3 Link

GBFD-111804

T6106:Number of MTP3 Link Set Failures

GBFD-111804

67196183

OS.MTP3.Lnkset.Unavail

WRFD-010101

WRFD-010101

67196184

OS.MTP3.Lnkset.Unavail.Dur

T6107:Duration of GBFD-111804 MTP3 Link Set Failure WRFD-010101

73403248

OS.SCCP.CR.Tx

T6236:Number of CR GBFD-111804 Messages Sent by WRFD-010101 SCCP

73403249

OS.SCCP.CR.Rx

T6237:Number of CR GBFD-111804 Messages Received WRFD-010101 by SCCP

73403250

OS.SCCP.CREF.Tx

T6238:Number of GBFD-111804 CREF Messages Sent WRFD-010101 by SCCP

73403251

OS.SCCP.CREF.Rx

T6239:Number of CREF Messages Received by SCCP

GBFD-111804 WRFD-010101

73403252

OS.SCCP.CC.Tx

T6242:Number of CC GBFD-111804 Messages Sent by WRFD-010101 SCCP

73403253

OS.SCCP.CC.Rx

T6243:Number of CC GBFD-111804 Messages Received WRFD-010101 by SCCP

73403254

OS.SCCP.RLSD.Tx

T6244:Number of GBFD-111804 RLSD Messages Sent WRFD-010101 by SCCP

73403255

OS.SCCP.RLC.Tx

T6245:Number of RLC GBFD-111804 Messages Sent by WRFD-010101 SCCP

73403256

OS.SCCP.RLC.RX

T6246:Number of RLC GBFD-111804 Messages Received WRFD-010101 by SCCP

73403527

OS.MTP3.Lnk.Rpo.Dur

T6130:Duration of MTP3 Link Remote Processor Fault

73415658

OS.SCCP.REJ.Remote

Issue 01 (2012-04-28)

GBFD-111804 WRFD-010101

T6240:Ratio of the GBFD-111804 CREF Messages from WRFD-010101 the Peer SCCP


7-8


7 Counters

Counter ID

Counter Name


73415659

OS.SCCP.REJ.Local

T6241:Ratio of the GBFD-111804 CREF Messages from WRFD-010101 the Local SCCP

Issue 01 (2012-04-28)


7-9


8 Glossary

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

Issue 01 (2012-04-28)


8-1


9 Reference Documents

9 Reference Documents [1] BSC6900 Feature List [2] BSC6900 Basic Feature Description [3] BSC6900 GSM Parameter Reference [4] BSC6900 GSM MML Command Reference [5] BSC6900 Performance Counter Reference

Issue 01 (2012-04-28)


9-1

Interface Features(GBSS14.0 01)

Recommend Documents