Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 32.311
Generic IRP Management –
Requirements

Use "3GPP‑Page" to get the Word version, and "ETSI‑search" to get the PDF version
V16.0.0 (PDF)  2020/06  10 p.
V15.0.0  2018/06  9 p.
V14.0.0  2017/03  10 p.
V13.0.0  2016/01  9 p.
V12.0.0  2014/10  9 p.
V11.0.0  2012/09  9 p.
V10.1.0  2011/12  9 p.
V9.0.0  2009/12  9 p.
V8.0.0  2008/12  9 p.
V7.0.0  2007/06  9 p.
V6.1.0  2005/01  9 p.
V5.1.0  2004/01  9 p.
V4.1.0  2004/01  9 p.
Rapporteur:
Mr. Tse, EdwinEricsson LM

Content for  TS 32.311  Word version:  16.0.0

Here   Top

0  IntroductionWord‑p. 4

The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
  • 32.311: "Generic Integration Reference Point (IRP) management; Requirements".
  • 32.312: "Generic Integration Reference Point (IRP) management; Information Service (IS)".
  • 32.316: "Generic Integration Reference Point (IRP) management; Solution Set (SS) Definitions".
The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 and TS 32.102.
The IRPs support a set of common services. Those features allow to retrieve IRP profile and IRP supported versions. The present document contains the requirements of those common services.
Up

1  ScopeWord‑p. 5

The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Requirements" part. It defines the requirements that shall be fulfilled by all IRPs, such as AlarmIRP, supporting this common service.
With this common service supported by all IRPs, an IRPManager shall be able to retrieve the profile of operations and notifications supported by a given IRP which is name-contained by an IRPAgent. An IRPManager shall also be able to retrieve the IRPVersions supported by the given IRP.
Up

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[2]
TS 32.102: "Telecommunication management; Architecture".
Up

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TS 32.101, TS 32.102 and the following apply:
IRP:
see TS 32.102.
IRPAgent:
see TS 32.102.
IRPManager:
see TS 32.102.
IRP document version number string:
the IRP document version number (sometimes called "IRPVersion") string is used to identify a technology of a particular IRP Solution Set (SS) specification and its version number.
For Release 9 and earlier releases, it is derived using the following rule:
Take the 3GPP TS/version number on the front page of the SS specification, such as "3GPP TS 32.111-3 V4.1.0 (2001-09)". Discard the leading "3GPP TS". Discard all characters after and including the last period. Eliminate leading and trailing spaces. Reduce multiple consecutive spaces to one space. Express the resultant in a string. Capitalise all letters of the string.
EXAMPLE 1: If the 3GPP document version number is "3GPP TS 32.111-3 V4.1.0 (2001-09)", then the IRP document version number shall be "32.111-3 V4.1".
EXAMPLE 2: If the 3GPP document version number is "3GPP TS 32.303 V4.1.0 (2001-09)", then the IRP document version number shall be "32.303 V4.1".
For Release 10 and later releases, it is derived using the following rule:
Take the 3GPP TS/version number on the front page of the SS specification, such as "3GPP TS 32.111-6 V10.1.0 (2011-06)", Discard the leading "3GPP TS". Discard all characters after and including the last period. Remove all spaces. Construct a string that is a concatenation of '-', the identifier of the Annex where the solution set technology is captured (e.g., 'A' for Annex A) and a trailing space. Insert the concatenated string before 'V', Express the resultant in a string. Capitalise all letters of the string.
EXAMPLE 3: If the 3GPP document version number is "3GPP TS 32.111-6 V10.1.0 (2011-06)", then the IRP document version number shall be:
  • "32.111-6-A V10.1" for CORBA Solution Set;
  • "32.111-6-B V10.1" for XML Definitions;
  • "32.111-6-C V10.1" for SOAP Solution Set.
EXAMPLE 4: If the 3GPP document version number is "3GPP TS 32.306 V10.1.0 (2011-09)", then the IRP document version number shall be:
  • "32.306-A V10.1" for CORBA Solution Set;
  • "32.306-B V10.1" for XML Defintions;
  • "32.306-C V10.1" for SOAP Solution Set.
Up

3.2  AbbreviationsWord‑p. 6

For the purposes of the present document, the following abbreviations apply:
CM
Configuration Management
EM
Element Manager
IRP
Integration Reference Point
IS
Information Service
NE
Network Element
NM
Network Manager
SS
Solution Set

4  Generic IRP functions over Itf-N

The requirements for the generic IRP service over Itf-N are provided in the following clauses.

4.1  Version retrieval function

An IRPAgent may support one or multiple IRP instances simultaneously (e.g. AlarmIRP instances, BulkCMIRP instances, etc.).
The set of capabilities of each IRP instance is fully identified by the version number of the corresponding IRP specification (i.e. the "IRP document version number string" or in short, the IRPVersion; see clause 3.1.).
An IRP instance shall provide a function to allow IRPManager to retrieve all its (i.e. IRP instance's) supported IRPVersion(s) over Itf-N.
An IRPManager may then decide if it wants to communicate with the IRP instance.
Up

4.2  Profiles retrieval functions

Each IRP supported by an IRPAgent provides a set of operations and notifications. It is possible to define in each IRP Information Service (IS) some operations and notification that are optional, which means that the final implementation of those operations and notifications is vendor dependant. Similarly, some parameters of operations and notifications may be defined as optional in the IRP IS.
It shall be possible for an IRPManager to retrieve over Itf-N the profile of an IRP of a given version: the profile shall provide information such as name of supported operations and notifications, and the list of supported parameters for each supported operation and notification.
Up

$  Change HistoryWord‑p. 8


Up   Top