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

0005568

3GPP SA5 Bug Tracking

Quality

public

22-06-2010 16:07

22-06-2010 16:10

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

0005568: Issues with 32.111-1

Description

TS names are wrong for -5 and -7:
"32.111-1 "Fault Management; Part 1: 3G fault management requirements".
32.111-2 "Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
32.111-3 "Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".

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)"."
From http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--S5.htm [^] they are called:
"

32.111-1 Telecommunication management; Fault Management; Part 1: 3G fault management requirements
32.111-2 Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)
32.111-3 Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
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)
"

Could the following be replaced with a single reference to 32.600?
"[1] 3GPP TS 32.601: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements".

        3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".

        3GPP TS 32.603: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".

        3GPP TS 32.607: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS)"."

Similarly, would one reference to PM suffice (what does IMS measurements add to the Alarm IRP, why is 32.403 omittedâ€¦.)
"[4] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
        3GPP TS 52.402: "Telecommunication management; Performance Management (PM); Performance measurements - GSM".
        3GPP TS 32.404: "Telecommunication management; Performance Management (PM); Performance measurements - Definitions and template".

        3GPP TS 32.405: "Telecommunication management; Performance Management (PM); Performance measurements Universal Terrestrial Radio Access Network (UTRAN)".

        3GPP TS 32.406: "Telecommunication management; Performance Management (PM); Performance measurements Core Network (CN) Packet Switched (PS) domain".

        3GPP TS 32.407: "Telecommunication management; Performance Management (PM); Performance measurements Core Network (CN) Circuit Switched (CS) domain".

        3GPP TS 32.408: "Telecommunication management; Performance Management (PM); Performance measurements Teleservice".

        3GPP TS 32.409: "Telecommunication management; Performance Management (PM); Performance measurements IP Multimedia Subsystem (IMS)"."

It's debatable whether we need to describe the family of FM specs and then repeat these as references also. 32.111-5 is omitted. I propose to remove them as references.

"[13] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP); Information Service (IS)".

[14] 3GPP TS 32.111-3: "Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)".

[17] 3GPP TS 32.111-7: "Telecommunication management; Fault Management; Alarm Integration Reference Point (IRP); SOAP Solution Set (SS)"."

There is at least one blind reference
"[16] ISO 8571: "File Transfer, Access and Management"."
[17] above is also not used.

Clause 5.5 has info that is out of date:
"For the purpose of FM, the following IRPs are needed:

Alarm IRP, see 3GPP TS 32.111-2 [13];
Notification IRP, see [1]; and
Log IRP.
NOTE: The Log IRP is not part of Release 1999, therefore the requirements related to the log functionality are not valid for Release 1999)."

Notification IRP was moved out of the CM specs (32.106-x) and into it's own series.
We have a Notification Log IRP now, is that the same as "Log IRP" and is it really needed for FM?

Issue History
Date Modified	Username	Field	Change
22-06-2010 16:07	user601	New Issue
22-06-2010 16:07	user601	Source (company - Author)	=> Ericsson - John Power
22-06-2010 16:07	user601	TS number	=> 32.111-1
22-06-2010 16:07	user601	TS version	=> 8.0.0/9.0.0
22-06-2010 16:07	user601	Clause Reference(s)	=> Several clauses throughout the spec
22-06-2010 16:10	user601	TS version	8.0.0/9.0.0 => Latest versions of Rel-8 and Rel-9
22-06-2010 16:10	user601	Summary	issues with 32.111-1 => Issues with 32.111-1

Relationships

Notes
There are no notes attached to this issue.