3G Performance Management

yaziz  Diamond  (1)
6 years 4 months ago  View: 4627  Reply: 32

Introduction

 

During the lifetime of a 3G network, its logical and physical configuration will undergo changes of varying degrees and frequencies in order to optimize the utilization of the network resources. Many of the activities involved in the daily operation and future network planning of a 3G network require data on which to base decisions. This data refers to the load carried by the network and the grade of service offered. In order to produce this data performance measurements are executed in the NEs which comprise the network. The data can then be transferred to an external system, e.g. an Operations System (OS) in TMN terminology, for further evaluation.


The objectives are:

 

-   to provide the descriptions for a standard set of measurements;

 

-   to produce a common description of the management technique for measurement administration and result accumulation; and

 

-   to define a method for the bulk transmission of measurement results across a management interface.

 

The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor 3G network, for those measurement types that can be standardized across all vendors’ implementations.

 

As far as possible, existing standardization in the area of performance management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognized.


Performance measurement concept


Any evaluation of 3G system’s behavior will require performance data collected and recorded by its NEs according to a schedule established by the OMC. This aspect of the management environment is termed Performance Management. The purpose of any performance management activity is to collect data which can be used to verify the physical and logical configuration of the network and to locate potential problems as early as possible.

 

Data is required to be produced by the NEs to support the following areas of performance evaluation:


-   traffic levels within the network, including the level of both the user traffic and the signalling traffic;

 

-   verification of the network configuration;

 

-   resource access measurements;

 

-   Quality of Service (e.g. delays during call set-up, packet throughput, etc); and

 

-   resource availability (e.g. the recording of begin and end times of service unavailability)

 

 

The production of the measurement data by the NEs also needs to be administered by the OMC. Several phases of administration of performance measurements can be distinguished:

 

 

-   the management of the performance measurement collection process;

 

-   the generation of performance measurement results;

 

-   the local storage of measurement results in the NE;

 

-   the transfer of measurement results from the NE to an OS; and

 

-   the storage, preparation and presentation of results to the operating personnel.

 

Measurement data requirements

  

This subclause describes the typical requirements for performance data to be produced by the NEs which comprise a 3G system. It is important to note that an actual measurement value collected from the network may be used to satisfy requirements in more than one category of measurement described below.

 

Traffic measurements


Traffic measurements provide the data from which, among other uses, the planning and operation of the network can be carried out.

 

The types of traffic evaluations for which 3G specific measurements may be used include:

 

-   traffic load on the radio interface (signalling and user traffic);

 

-   usage of resources within the network nodes;

 

-   user activation and use of supplementary services, etc.

 

Examples of measured values may include:

 

-   pages per Location area per hour;

 

-   busy hour call attempts per RNC, MSC;

 

-   handovers per RNC per hour, etc.

 

 Network configuration evaluation

 

Once a network plan, or changes to a network plan, have been implemented it is important to be able to evaluate the effectiveness of the plan or planned changes. Typically, the measurements required to support this activity will indicate the traffic levels with particular relevance to the way the traffic uses the network.

  

Resource access

 

For accurate evaluation of resource access, each count would need to be produced for regular time intervals across the network, or for a comparable part of the network.

 

Quality of Service (QoS)

 

 The user of a 3G system views the provided service from outside the network. That perception can be described in observed QoS terms. QoS can indicate the network performance expected to be experienced by the user.

 

The QoS parameters applied by the network to specific user services may also be relevant to determine the charges levied towards the user for the provision of those services.

 

Resource availability


The availability performance is dependent on the defined objectives, i.e. the availability performance activities carried out during the different phases of the life cycle of the system, and on the physical and administrative conditions.


Measurement administration

 

The range of measurements which will be available from the NEs are expected to cover all of the requirements described here. However, not all of these measurements will be required all of the time, from every occurrence, of every relevant NE. With a highly distributed network like a 3G mobile telecommunication system it is also necessary to gather the measurement data so as to perform consistent analysis of the results and to evaluate the interactions between the NEs.

 

This subclause describes the requirements for the various areas of administration of measurements.

  

Measurement job administration

  

Measurement jobs, i.e. the processes which accumulate the data and assemble it for collection and/or inspection, will need to be scheduled for the period or periods for which gathering of data shall be performed.

  

The administration of measurement jobs comprises the following actions:

 

1) Create/delete a measurement job. This action implies the instantiation resp. deletion of a measurement collection process within the network.

 

2) Modifying a measurement job, i.e. changing the parameters (specifically the schedule) of a measurement job that has been previously created.

 

3) Definition of measurement job scheduling. This action defines the period or periods during which the measurement job is configured to collect performance data.

 

4) Suspend/resume a measurement job. The “suspend” action inhibits the collection of measurement data by a measurement job, regardless of its schedule, without deleting it.  The “resume” action will re-enable measurement data collection according to the measurement job schedule.

 

5) Reporting and routing of results to one or more OSs (OMC and/or NMC);

 

6) Retrieval of information related to measurement jobs, i.e view the current measurement job definition.

  

Measurement result generation

  

Each measurement job will be collecting result data at a particular frequency, known as the granularity period of the measurement. At the end of the granularity period a scheduled result report shall be generated for each measurement job that is actively collecting performance measurement data.

  

The measurement data can be collected in each NE of the network in a number of ways:

  

-   cumulative incremental counters triggered by the occurrence of the measured event;

 

-   status inspection (i.e. a mechanism for high frequency sampling of internal counters at pre-defined rates);

 

-   gauges (i.e. high tide mark, low tide mark);

 

-   discrete event registration, where data related to a particular event is captured.

 

These are described in the following paragraphs.

 

Cumulative counter:

  

The NE maintains a running count of the event being counted. The counter is reset to a defined value (usually “0”) at the beginning of the granularity period.

 

Status inspection:

  

Network elements maintain internal counts for resource management purposes. These counts are read at a predetermined rate, the rate is usually based upon the expected rate of change of the count value.  Status inspection measurements shall be reset at the beginning of the granularity period and will only have a valid result at the end of the granularity period.

 

Gauge:

 

Gauges represent dynamic variables that may change in either direction. Gauges can be integer or real valued. If a gauge is required to produce low and high tide marks for a granularity period (e.g. minimum and maximum call duration), then it shall be reinitialised at the beginning of the granularity period. If a gauge is required to produce a consecutive readout over multiple granularity periods (e.g. cabinet temperature), then it shall only be reinitialised at the start of a recording interval.

 

Discrete Event Registration:

 

This is a measurement of a specified event where every Nth event would be taken into account. The value of N is dependant on the frequency of occurrence of the event being measured. Discrete event registration measurements shall be reset at the beginning of the granularity period and will only have a valid result at the end of the granularity period.

Pema Wangdi  Diamond 
6 years 4 months ago

dear yaziz,


Thanks you are great ............. Thanks for sharing ............

yaziz  Diamond 
6 years 4 months ago

Reply 2 #

thanks for your feedback. i had more content but could not load everything! so its an abridged version.
shahiduzzaman  Medium 
6 years 4 months ago
very good article.
suman.s  Medium 
6 years 4 months ago
its an interesting post.
sajid123  Medium 
6 years 4 months ago
very cool post
tkhan  Medium 
6 years 4 months ago
nice information
rohidul  Medium 
6 years 4 months ago
it is an interesting post. thanks.
shekhar123  Medium 
6 years 4 months ago
this is very excellent post. 
s_khaleque  Medium 
6 years 4 months ago
thanks for the information.
1/4Page