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

0005574

3GPP SA5 Bug Tracking

Quality

public

22-06-2010 16:59

18-02-2011 08:59

Reporter

user601

Assigned To

Clemens Suerbaum

Priority

normal

Severity

major

Reproducibility

N/A

Status

assigned

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0005574: Issues with 32.122

Description

References:
32.150 is so useful it gets added twice ;-) as ref 1 and ref 5.
"[4] 3GPP TS 32.121: "Telecommunication management; Advanced Alarm Management Reference Point (IRP): Requirements"." does not match the spec title at http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--S5.htm [^]

References 8&9 are not used in the spec.

Definitions:
There is a strange mix of fonts here..
"IRP: See 3GPP TS 32.150 [1].
IRPAgent: See 3GPP TS 32.150 [1]."
There is a strange definition AAMRule, I'm not sure if it's a good idea or not. If we agree that it's a good idea, then there is a mix of AAMRule and AAM Rule throughout the document, I'm not sure if there is a significance given that it resolves to the same thing anyway, and is later used as "An AAMRule (called Rule hereafter).."

"AAM Advanced Alarm Management
AAMRule Advanced Alarm Management Rule"

5.1 Imported IOCs.
Top and IRPAgent are not used.
"managedGenericIRP" should be "ManagedGenericIRP" in both columns of the table.

I would consider 5.3.1.1.1 as a step too far in chapter headings, and does not comply with the IS template. I don't think the extra level adds any clarity anyway?

"5.3.1.1 Definition
5.3.1.1.1 General Definition"
Small typo in "An AAM Rule instance is fully identified by its DNdistinguished name"

6.2.1
Small typo in "This interface defines methods for the IRPManagerIRPManager to request for alarm notifications of significant information (significant from the IRPManagerâ€™s perspective)."

6.2.2 Again we appear to have an extra level of heading, for no obvious reason, and not according to the template I think

"6.2.2.1 Definition
This operation allows an IRPManager to activate an AAM rule (see Â§A.3.1.1.2.1).
6.2.2.2 Input parameters
6.2.2.2.1 Generic Input parameters"

Annex A does not read very well, and there are specific ambiguities in A.1, for example:
"The first element (subSection titled: Criterion to determine alike alarm) is a criterion..." which does not specific a specific Clause number.

There are three clauses with that name:
"A.2.1.2 Criterion to determine alike alarm
A.2.2.2 Criterion to determine alike alarm
A.2.3.2 Criterion to determine alike alarm"
There are several of these vague references "The second element (subSection titled: Treatment of alike alarm)", "The third element (subSection titled: Relation to Log and AlarmList)", etc.

Issue History
Date Modified	Username	Field	Change
22-06-2010 16:59	user601	New Issue
22-06-2010 16:59	user601	Source (company - Author)	=> Ericsson - John Power
22-06-2010 16:59	user601	TS number	=> 32.122
22-06-2010 16:59	user601	TS version	=> 8.1.0/9.0.0
22-06-2010 16:59	user601	Clause Reference(s)	=> Several clauses throughout the spec
18-02-2011 08:59	Christian Toche	Status	new => assigned
18-02-2011 08:59	Christian Toche	Assigned To	=> Clemens Suerbaum

Relationships

Notes
There are no notes attached to this issue.