5 Future Enhancements
12.043GPPPerformance data measurementsTS
The simple scanner can scan an attribute, but is unable to perform any calculations on it. This means that the simple scanner is unable to apply any algorithm on any attribute to derive a master value, e.g. a calculation of the mean value. Therefore, within the present document, an approach has been chosen where the attribute itself represents a mean value, derived from system internal sampling procedures, if generation of a mean value is desired. As a result, the values of such attributes are only meaningful at the time of scanning, so that the scanner and the measurement process that generates the attribute value shall be synchronised. How this synchronisation and the generation of processed attributes is achieved is a matter of internal implementation.
The situation described above will also prohibit that a single attribute be observed by more than one scanner if the reporting periods of the scanners overlap and contain different granularity periods. If it is required to have multiple scanners generating results for the same measurement type simultaneously, it is necessary to create multiple instances of the same "measurementFunction" that includes the attribute which corresponds to the required measurement type. In practical terms, this means that a measurement has to be implemented more than once in a NE if this feature is supported.
In order to circumvene this problem, a change has been proposed to ISO 10165-13 to incorporate a new scanner object class which will be based on simple counter-type measurements only and allow to attach any desired algorithm in order to process the attribute values and report the result of that processing, e.g. evaluating the mean over the observed values. Pending future extensions of the international standard, this may eventually lead to associated changes to the present document (subject of Phase 2+).
Annex A (informative):
Graphical examples
This annex gives some graphical examples to demonstrate how the measurements in annex B, can be combined to express a specific function.
EXAMPLE 1: Authentication and Authentication Set requests.
This diagram shows which measurements in the annex B need to be activated to collect the statistical information for Authentication of a subscriber.
EXAMPLE 1: Authentication and Authentication Set requests
Table:
Nbr. | Measurement Attribute Name | Measurement Name |
1 | attReqForAuthSetsReceivedByHLRFromVLRs | Attempted requests for Authentication sets received by HLR from VLRs |
2 | succReturnedAuthSetsFromHLRToVLRs | Successful returned Authentication sets from HLR to VLRs |
3 | emptyResponsesForAuthSetsFromHLRToVLRs | Empty responses to request for Authentication sets from HLR to VLRs |
4 | attReqForAuthSetsSentToHLR | Attempted requests for Authentication sets sent to HLR by the VLRs |
5 | succReceivedAuthSetsFromHLR | Successful received Authentication sets from the HLR to the VLRs |
6 | emptyResponsesForAuthFromHLR | Empty responses to request for Authentication sets from HLR to VLRs |
7 | attIdentificationReqToPVLRs | Attempted identification requests to PVLRs |
8 | succIdentificationReqToPVLRs | Successful identification requests to PVLRs |
9 | attCipheringModeControlProcs | Attempted ciphering mode controlled procedures |
10 | succCipheringModeControlProcs | Successful ciphering mode controlled procedures |
11 | attAuthProcsInVLR | Attempted authentication procedures in the VLR |
12 | succAuthProcsInVLR | Successful authentication procedures in the VLR |
EXAMPLE 2: Interrogation of HLR for routing.
This diagram shows which measurements in the annex B need to be activated to collect the statistical information for Routing.
Example 2: Interrogation of HLR for routing
Table:
Nbr. | Measurement Attribute Name | Measurement Name |
1 | attInterrogationOfHLRsForRouting | Attempted interrogations of HLRs for routing |
2 | attReqForMSRN | Attempted request for MSRN |
3 | succReqForMSRN | Successful request for MSRN |
4 | succInterrogationOfHLRsMSRNObtained | Successful interrogations of HLR (MSRN obtained) |
5 | succInterrogationOfHLRsCallForwarding | Successful interrogations of HLR (call forwarding) |
EXAMPLE 3: Location Updating.
This diagram shows which measurements in the annex B need to be activated to collect the statistical information for Location Updating.
EXAMPLE 3: Location Updating
Table:
Nbr. | Measurement Attribute Name | Measurement Name |
1 | attIntraVLRLocationUpdates | Attempted intra-VLR location updates |
2 | succIntraVLRLocationUpdates | Successful intra-VLR location updates |
3 | attInterVLRLocationUpdates | Attempted inter-VLR location updates |
4 | succInterVLRLocationUpdates | Successful inter-VLR location updates |
5 | attLocationUpdate | Attempted location updates |
6 | succLocationUpdate | Successful location updates |
Annex B (normative):
Performance Measurement Requirements Summary
Following is the template used to describe the measurements contained in this annex.
A. Description
A short explanation of the measurement operation.
B. Collection Method
The form in which this measurement data is obtained:
– CC (Cumulative Counter);
– GAUGE (dynamic variable), used when data being measured can vary up or down during the period of measurement;
– DER (Discrete Event Registration), when data related to a particular event are captured every nth event is registered, where n can be 1 or larger;
– SI (Status Inspection).
C. Condition
The GSM condition which causes this measurement data to be updated. Where it is not possible to give a precise GSM condition, then the conditional circumstances leading to the update is stated.
D. Measurement Attribute Name
The Measurement Attribute Name which will be referenced by the Object Model.
E. Measurement Result (measured value, Unit)
A short description of expected result value (e.g. A single integer value).
F. Measurement Function Name
Measurement Function Name for which this measurement is defined.
G. Switching Technology
The Switching product this Measurement is applicable to. Circuit Switched and / or Packet Switched ( GPRS ). When packet switching (GPRS) is identified for an MSC measurement function, this measurement type is related to a combined circuit/packet switched event.