F.2 Threshold crossing notifications triggering for measurements that are not cumulative counters

28.5503GPPManagement and orchestrationPerformance assuranceRelease 18TS

For the threshold monitoring of performance measurements that are not cumulative counters, the notification notifyThresholdCrossing is emitted at the end of the monitoring granularity period (GP) if the measurement value reached or crossed the threshold.

The threshold crossing notification event time field indicates the time during the Monitoring GP that the threshold was crossed.

Figure F.2-1: Threshold crossing notifications triggering for measurements that are not cumulative counters

Thresholds configured in both directions would emit the following notifications:

Notifications are emitted for Threshold #1 (T1) and Threshold #2 (T2) at end of Monitoring GP 1.

Notifications are emitted for Threshold #2 (T3) and Threshold #1 (T4) at end of Monitoring GP 2.

Notifications are emitted for Threshold #1 (T5) and Threshold #2 (T6) at end of Monitoring GP 3.

Annex G (normative):
ASN.1 definition for performance data stream units

G.1 ASN.1 definition rule

For performance data streaming, the type of WebSocket Data frame shall be binary (with opcode of 0x2).

This clause specifies the abstract syntax notation one (ASN.1) definition for the Performance Data Stream Units (see Annex C) as Payload data of WebSocket Data frame.

The Performance Data Stream Units are described using ASN.1 as specified in ITU-T Rec. X.680 [15] and X.681 [16]. Transfer syntax for Performance Data Stream Units is derived from their ASN.1 definitions by use of Packed Encoding Rules (PER), aligned as specified in ITU-T Rec. X.691 [17].

The following encoding rules apply in addition to what has been specified in ITU-T Rec. X.691 [17]:

– When a bit string value is placed in a bit-field as specified in clause 15.6 to 15.11 in ITU-T Rec X.691 [c], the leading bit of the bit string value shall be placed in the leading bit of the bit-field, and the trailing bit of the bit string value shall be placed in the trailing bit of the bit-field;

– When decoding a BIT STRING or OCTET STRING constrained with a Contents Constraint, PER decoders are required to never report an error if there are extraneous zero or non-zero bits at the end of the BIT STRING or OCTET STRING.

NOTE: The terms ‘leading bit’ and ‘trailing bit’ are defined in ITU-T Rec. X.680 [15]. When using the ‘bstring’ notation, the leading bit of the bit string value is on the left, and the trailing bit of the bit string value is on the right.

G.2 ASN.1 definition

— ASN1START

PerformanceDataStreamUnits-Schema DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

— PDSUs-START

PDSUs ::= SEQUENCE OF PDSU

PDSU ::= SEQUENCE {

streamId INTEGER,

granularityPeriodEndTime DATE-TIME,

standardizedMeasResults SEQUENCE OF MeasValue,

vendorSpecificMeasResults SEQUENCE OF MeasValue OPTIONAL — may be omitted

}

MeasValue ::= CHOICE {

integerValue INTEGER,

realValue REAL,

stringValue VisibleString,

subCounters SubCounterListType,

… — allow extension in futher version

}

— uses recursion for the value to support multi-dimensional measurements

SubCounterListType ::= SEQUENCE {

subCounterIndex SubCounterIndexType,

subCounterValue MeasValue OPTIONAL — "empty" bins are allowed

}

SubCounterIndexType ::= CHOICE {

sum VisibleString ("SUM"),

binIndex INTEGER,

qOS-5QI INTEGER,

qOS-QCI INTEGER,

cause INTEGER,

stringIndex VisibleString,

plMN OCTET STRING (SIZE(3)), — definition from TS 38.413

sNSSAI SEQUENCE { — definition from TS 38.413

sst OCTET STRING (SIZE(1)),

sd OCTET STRING (SIZE(3))

},

… — allow extension in futher version

}

— PDSUs-STOP

END

— ASN1STOP

Annex H (normative):
NSI and NSSI performance assurance