MSC - Service

Top  Previous  Next

Descriptions

 

The MSC measurement gives overall call statistics reports from MSC on traffic service, traffic based on trunk and trunk group, Erlang, and BHCA.

 

The granularity period, which is the time between the successive gatherings of measurement data, is 15 minutes. That means the statistics reports on the EMS GUI will be updated in every 15 minutes. There are up to 30 days' statistics reports can be checked via the EMS, and the searching interval is on a daily basis. Each statistics on a daily basis can be specified by 24 hours which lie between 00:00 and 24:00.

 

All statistics reports generated by EMS have the same layout, including cross tabulation and charts of stacked line or column:

 

Cross tabulation:

 

The vertical section classifies the measure objects or time intervals.

The horizontal section defines the results or time intervals.

 

Stacked Line:

 

Displays the trend of the percentage each value contributes over time and categories.

 

Stacked Column:

 

Compares the percentage each value contributes to a total across categories.

 

The MSC service gives an overall call statistics report from MSC on the 12 types of call described below.

 

Call Type

Descriptions

Subs to Subs

Mobile originating traffics to mobile.

Subs to Trunk

Mobile originating traffics to PSTN.

Trunk to Subs

PSTN originating traffics to mobile.

Trunk to Trunk

Transit and intra-connected traffics.

Intra Connection

Traffics on the intra-connected trunks.

Subs to IP

Mobile originating traffics to Intelligent Peripheral.

Trunk to IP

PSTN originating traffics to Intelligent Peripheral.

Mobile Originated

Mobile originating traffics to mobile, PSTN, Intelligent Peripheral, or intra-connected trunks.

Mobile Terminated

Mobile terminating traffics from mobile or PSTN.

In Trunk

Incoming PSTN traffics.

Out Trunk

Outgoing PSTN traffics.

IP Terminated

Intelligent Peripheral terminating traffics from mobile or PSTN.

 

 

Call Failure

Descriptions

Call Deny

This cause indicates that the MS has tried to access a service that the MS's network operator or service provider is not prepared to allow. It may be caused by the following reasons:

Unassigned (unallocated) number

No route to destination

Channel unacceptable

Operator determined barring

Number changed

Non-selected user clearing

Invalid number format (incomplete number)

Facility rejected

Response to STATUS ENQUIRY

Normal, unspecified

Quality of service unavailable

Requested facility not subscribed

Incoming calls barred within the CUG

Bearer capability not authorized

Bearer capability not presently available

Service or option not available, unspecified

ACM equal to or greater than ACMmax

Bearer service not implemented

Requested facility not implemented

Only restricted digital information bearer capability is available

Service or option not implemented, unspecified

Net Busy

Network Busy indicates that there is no appropriate circuit/channel presently available to handle the call. It may be caused by the following reasons:

Destination out of order

No circuit/channel available

Network out of order

Temporary failure

Switching equipment congestion

Access information discarded

Requested circuit/channel not available

Resource unavailable, unspecified

Caller Clear

This cause indicates that the call is being cleared because the calling subscriber involved in the call has requested that the call be cleared.

Sub Busy

Subscriber Busy is counted when the called subscriber has indicated the inability to accept another call. It may be caused by the following reasons:

User busy

Call rejected

Pre-emption

No Answer

This cause is counted when a subscriber has provided an alerting indication but has not provided a connect indication within a prescribed period of time. It may be caused by the following reasons:

No user responding

User alerting, no answer

Signal Error

This cause is counted by the following reasons:

Invalid transaction identifier value

User not member of CUG

Incompatible destination

Invalid transit network selection

Semantically incorrect message

Invalid mandatory information

Message type non-existent or not implemented

message type not compatible with protocol state

Information element non-existent or not implemented

Conditional IE error

Message not compatible with protocol state

Recovery on timer expiry

Protocol error, unspecified

Interworking, unspecified

 

 

There are ten statistics items for each type of call: call attempt, call answer, six categories of call failure, total and average call duration. The statistics is collected on both quantity and percentage basis, and concluded by the following formula:

Total Call = Sum of Call Attempt

Attempt = Success + Call Deny + Net Busy + Caller Clear + Sub Busy + No Answer + Signal Error

Average Call Duration = Total Call Duration / Success

 

Two statistics histograms about call attempt and call answer / failure are provided on this page.

 

The Date navigator is used to select up to the last 30 days' statistics for browsing and printing. The Print logo is for printing out this statistics page.

 

 

Functionalities

 

MSC overall call statistics for different type of calls

 

 

 

 

 

3.2.1