Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0005569

3GPP SA5 Bug Tracking

Quality

public

22-06-2010 16:09

Reporter

user601

Assigned To

Priority

normal

Severity

major

Reproducibility

N/A

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0005569: Issues with 32.111-2

Description

Spec titles in introduction are incorrect:
"32.111-5 "Fault Management; Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions".

32.111-7 "Fault Management; Alarm Integration Reference Point (IRP): SOAP Solution Set (SS)"."
Should be
"
32.111-5 Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions
32.111-7 Telecommunication management; Fault Management; Part 7: Alarm IRP SOAP Solution Set (SS)
"

Scope: "The purpose of the AlarmIRP is to.." should be "The purpose of the Alarm IRP is to..." to distinguish between the IRP and the IOC called AlarmIRP.

Probably no need to have a reference to
"[9] 3GPP TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements"."
Definitions:
It says "For the purposes of the present document, the terms and definitions given in TS 32.111-1 [9] and the following apply"

And then goes on to define
"active alarm: an alarm that has not been cleared ( i.e. an alarm whose perceivedSeverity is not Cleared).
Event: occurrence that is of significance to network operators, the NEs under surveillance and Network Management applications. Events do not have state.

Notification: which refers to the transport of events from IRPAgent to IRPManager.
In this IRP, notifications are used to carry alarm information from IRPAgent to IRPManager. "
Which were defined in 32.111-1 as
"active alarm: an alarm that has not been cleared and which is active until the fault that caused the alarm is corrected and a "clear alarm" is generated"

and
"event: this is a generic term for any type of occurrence within a network entity
NOTE: A notification or event report may be used to inform one or more OS(s) about the occurrence of the event."
"notification: information message originated within a network entity to inform one or more OS(s) about the occurrence of an event"

We should really just have one definition, at least in the FM context.

The fonts for "special terms" are not applied evenly "In this state, the alarm is Cleared and acknowledged." and "It contains all currently active alarms (i.e. AlarmInformation whose perceivedSeverity is not Cleared) and alarms that are Cleared but not yet acknowledged"

"Acknowledged" in these two cases should have the same formatting as "Cleared".

The font for clause 5.3.4 is different to the fonts in other clauses of the same level
"5.3.4 Comment" compared to "5.3.3 AlarmIRP"
On the other hand, neither matches 32.312 "5.3.1 ManagedGenericIRP"
As a rule we should avoid adding "(M)" to the clause titles - I guess if we change an attribute/interface to Optional later then the clause title has to be Voided (or can we change to "(O)")? "5.4.1 relation-AlarmIRP-AlarmList (M)"

Issue History
Date Modified	Username	Field	Change
22-06-2010 16:09	user601	New Issue
22-06-2010 16:09	user601	Source (company - Author)	=> Ericsson - John Power
22-06-2010 16:09	user601	TS number	=> 32.111-2
22-06-2010 16:09	user601	TS version	=> Latest versions of Rel-8 and Rel-9
22-06-2010 16:09	user601	Clause Reference(s)	=> Several clauses throughout the spec

Relationships

Notes
There are no notes attached to this issue.