11.3 Performance assurance
28.5323GPPGeneric management servicesManagement and orchestrationRelease 17TS
11.3.1 Operations and notifications
11.3.1.1 Void
11.3.1.2 Void
11.3.1.3 Notification notifyThresholdCrossing
11.3.1.3.1 Definition
A MnS producer sends this notification to subscribed MnS consumers when a "ThresholdMonitor" (3GPP TS 28.622 [11]) on that MnS producer detects the threshold crossing of a monitored performance metric.
11.3.1.3.2 Notification information
|
Parameter Name |
S |
Information Type |
Comment |
|---|---|---|---|
|
objectClass |
M |
ManagedEntity.objectClass |
Class of the managed object, where the threshold crossing occurred. |
|
objectInstance |
M |
ManagedEntity.objectInstance |
Instance of the managed object, where the threshold crossing occurred. |
|
notificationId |
M |
— |
|
|
notificationType |
M |
"notifyThresholdCrossing" |
|
|
eventTime |
M |
— |
Time when the threshold crossing occurred. |
|
systemDN |
M |
MnSAgent.objectInstance |
|
|
observedPerfMetricName |
M |
ThresholdMonitor.thresholdInfoList[11].\ performanceMetrics[y] |
Name of the performance metric that has crossed the threshold. |
|
observedPerfMetricValue |
M |
— |
Value of the performance metric, that has crossed the threshold, when the threshold crossing was observed |
|
observedPerfMetricDirection |
M |
— |
Direction ("UP" or "DOWN") of the performance metric, when the threshold crossing was observed |
|
thresholdValue |
M |
ThresholdMonitor.thresholdInfoList[11].\ thresholdvalue |
Threshold value of the triggered threshold |
|
hysteresis |
O |
ThresholdMonitor.thresholdInfoList[11].\ hysteresis |
Hysteresis of the triggered threshold |
|
monitorGranularityPeriod |
M |
ThresholdMonitor.monitorGranularityPeriod |
Granularity period of the threshold monitor |
|
additionalText |
O |
— |
Vendor specific information |
11.3.2 Managed information
11.3.2.1 Performance data file
11.3.2.1.1 Void
11.3.2.1.2 Performance data file content description
Table 11.3.2.1.2-1 provides the content definition of a performance data file.
Table 11.3.2.1.2-1: Performance data file content description
|
File content item |
Description |
|---|---|
|
measDataFile |
Top-level tag indicating the file contains performance metrics. Each file includes a header ("measFileHeader"), a collection of information elements with produced performance metrics and associated meta data ("measData") and a footer ("measFileFooter"). |
|
measFileHeader |
File header including the file format version, information about the sending node (DN, type and vendor) and a time stamp indicating the begin of the first granularity period contained in the file ("collectionBeginTime"). |
|
measData |
Information element containing the DN of the common root of the measured object instances ("measObjRootDn ") included in that information element, followed by a list of information elements containing the produced performance metrics and associated meta data ("measInfo"). A "MeasDataFile" contains zero, one or more "measData" elements. |
|
measFileFooter |
File footer with a time stamp indicating the end of the last granularity period contained in the file ("collectionEndTime"). |
|
fileFormatVersion |
File format version applied by the sender as indicated by the specific format version identifier provided for each version. |
|
senderName |
DN of the entity, that generated and sent the file. The entity is either a managed element represented by a "ManagedElement" or a management node represented by a "ManagementNode" |
|
senderType |
Type of the entity, that generated and sent the file, as defined in 3GPP TS 28.620 [y]. The type of a management node is "MANAGEMENT_NODE". |
|
vendorName |
Vendor of the the entity, that generated and sent the file. |
|
collectionBeginTime |
Time stamp indicating the begin of the first granularity period for which performance metrics are stored in the file. |
|
measObjRootDn |
DN of the measured object root. The measured object root is the first common object name-containing all objects that the metrics in one "measData" element are related to. When the metrics are produced by a managed element, the root object is the "ManagedElement" representing this managed element. When (aggregated) metrics are produced by a management node (based on input metrics from managed elements), such as metrics for sub-networks or network slices, the root object is the root "SubNetwork" of this management node. |
|
measObjRootUserLabel |
User label of the measured object root. |
|
measObjRootSwVersion |
Software version of the measured object root, allowing post-processing systems to take care of vendor specific performance metrics. It is either the software version of a managed element or of a management node. |
|
measInfo |
Information element added to "measData" for each expired granularity period, containing information on the produced performance metrics, starting with a time stamp ("measTimeStamp"), the granularity period ("granularityPeriod") and reporting period ("reportingPeriod") that are associated to the following performance metrics ("measValues"), for which is indicated the performance metric name, the measured or computed performance metric value and the object instance to which the performance metric is related to. |
|
measInfoId |
Identifier of a "measInfo". |
|
jobId |
Job identifier of the related "PerfMetricJob" in this "measInfo". |
|
reportingPeriod |
Period used for performance metric reporting in this "measInfo". Unit is seconds |
|
granularityPeriod |
Period used for performance metric production in a "measInfo". Unit is seconds. |
|
measTimeStamp |
End time of the granularity period in a "measInfo". |
|
measTypes |
Performance metric names in a "measInfo" |
|
measValues |
Performance metric values in a "measInfo". Each item in this list includes the LDN of the object the metrics are related to ("measObjLdn"), the measured or computed values of the metrics ("measResults") and a flag that indicates whether the metrics are reliable ("suspectFlag"). |
|
measObjLdn |
Local distinguished name (LDN) of the object the performance metrics are related to (measured object) within the scope defined by the "measObjRootDn". The concatenation of the "measObjRootDn" and the "measObjLdn" is the DN of the measured object. The "measObjLdn" is therefore empty if the "measObjRootDn" already specifies completely the DN of the measured object, which is the case for metrics associated to "ManagedElement" or the root "SubNetwork". For example, if the measured object is a "ManagedElement" representing RNC "RNC-Gbg-1", then the "measObjRootDn" may look like "DC=a1.operatorNN.com,SubNetwork=CountryNN,ManagedElement=RNC-Gbg-1" and the "measObjLdn" is empty. However, if the measured object is an "UtranCell" representing cell "Gbg-997" managed by that RNC, then the "measObjRootDn" is the same as above, i.e. "DC=a1.companyNN.com,SubNetwork=CountryNN,ManagedElement=RNC-Gbg-1" and the "measObjLdn" is "RncFunction=RF-1,UtranCell=Gbg-997". The class of the measured object is defined in item f) of measurement definitions (3GPP TS 32.404 [47], TS 28.552 [18]) and in item d) of KPI definitions (TS 28.554 [6]). |
|
measResults |
List of result values for the observed or computed performance metrics. The "measResults" sequence shall have the same number of elements and follow the same order as the "measTypes" sequence. The NULL value is reserved to indicate that the performance metric is not applicable or could not be produced for the object instance. |
|
suspectFlag |
Reliability of the performance metrics. FALSE means the metrics are reliable, TRUE means they are not reliable. The default value is "FALSE". |
|
collectionEndTime |
Time stamp indicating the end of the last granularity period for which performance metrics are stored in the file. |
The representation of all timestamps in PM files shall follow the representations allowed by the ISO 8601 [20].
The precise format for timestamp representation shall be determined by the technology used for encoding the PM file (e.g. ASN.1, XML DTD, and XML Schema). The choice of technology should ensure that this representation is derived from ISO 8601 [20]. Based on the representation used, the timestamp shall refer to either UTC time or local time or local time with offset from UTC.
11.3.2.1.3 Void
11.3.2.1.3.1 Void
11.3.2.1.3.2 Void
11.3.2.1.4 Performance data file naming convention
This clause defines a rule that shall be applied for constructing names for files containing performance data.
<Type><Startdate>.<Starttime>-[<Enddate>.]<Endtime>[_-<jobIdList>][_<UniqueIdList>][_-_<RC>]
1) The "Type" field indicates if the file contains measurement results for single or multiple measured objects and/or granularity periods where:
– "A" means single measured object, single granularity period (this is used when granularity period is equal to reporting period);
– "B" indicates multiple measured objects, single granularity period (this is used when granularity period is equal to reporting period);
– "C" signifies single measured object, multiple granularity periods (this is used when reporting period is multiples of the granularity period and will contain multiple measurement reports);
– "D" stands for multiple measured objects, multiple granularity periods (this is used when reporting period is multiples of the granularity period and will contain multiple measurement reports).
2) The "Startdate" field indicates the date when the granularity period began if the "Type" field is set to A or B. If the "Type" field is either "C" or "D" then "Startdate" contains the date when the first granularity period of the measurement results contained in the file started. The "Startdate" field is of the form YYYYMMDD, where:
– YYYY is the year in four-digit notation;
– MM is the month in two digit notation (01 – 12);
– DD is the day in two-digit notation (01 – 31).
3) The "Starttime" field indicates the time when the granularity period began if the "Type" field is set to A or B. If the "Type" field is either "C" or "D" then "Starttime" contains the time when the first granularity period of the measurement results contained in the file began. The "Starttime" field is of the form HHMMshhmm, where:
– HH is the two-digit hour of the day (local time), based on 24-hour clock (00 – 23);
– MM is the two digit minute of the hour (local time), based on 60-minutes clock (00 – 59);
– s is the sign of the local time differential from UTC (+ or -), in case the time differential to UTC is 0 then the sign may be arbitrarily set to "+" or "-";
– hh is the two-digit number of hours of the local time differential from UTC (00-23);
– mm is the two digit number of minutes of the local time differential from UTC (00-59).
4) The "Enddate" field shall only be included if the "Type" field is set to "C" or "D", i.e. measurement results for multiple granularity periods are contained in the file. It identifies the date when the last granularity period of these measurements ended, and its structure corresponds to the "Startdate" field.
5) The "Endtime" field indicates the time when the granularity period ended if the "Type" field is set to A or B. If the "Type" field is either "C" or "D" then "Endtime" contains the time when the last granularity period of the measurement results contained in the file ended. Its structure corresponds to the "Starttime" field.
6) The "UniqueIdList" field indicates the DNs of the measured objects.
7) The "RC" field is a running count, starting with the value of "1", and shall be appended only if the filename is otherwise not unique, i.e. more than one file is generated and all other parameters of the file name are identical. Therefore it may only be used by the EM, since the described situation cannot occur with NE generated files. Note that the delimiter for this field, _-_, is an underscore character (_), followed by a minus character (-), followed by an underscore character (_).
8) The "jobIdList" indicates the measurement job id(s) that the performance data file is associated with.
Some examples describing file-naming convention:
1) file name: A20000626.2315+0200-2330+0200_gNBId,
meaning: file produced for gNB <gNBId> on June 26, 2000, granularity period 15 minutes from 23:15 local to 23:30 local, with a time differential of +2 hours against UTC.
2) file name: B20021224.1700-1130-1705-1130_-job10_S-NSSAI,
meaning: file containing results for multiple measured objects, generated for measurement job job10, produced for NSI <S-NSSAI> on December 24, 2002, granularity period 5 minutes from 17:00 local to 17:05 local, with a time differential of –11:30 hours against UTC.
3) file name: D20050907.1030+0000-20050909.1500+0000_SubnetworkId_-_2,
meaning: file containing results subnetwork <SubnetworkId>, start of first granularity period 07 September 2005, 10:30 local, end of last granularity period 09 September 2005, 15:00 local, with a time differential of 0 against UTC. This is the second file for this subnetwork/granularity period combination.
4) file name: C20050907.1030+0000-20050909.1500+0000_gNBId,
meaning: file produced for the gNB <gNBId>, start of first granularity period 07 September 2005, 10:30 local, end of last granularity period 09 September 2005, 15:00 local, with a time differential of 0 against UTC.