Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 32.150  Word version:  16.0.0

Top   Top   None   None   Next
0…   4…   G…

 

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:
TS 32.150:
Integration Reference Point (IRP) Concept and definitions.
TS 32.153:
Integration Reference Point (IRP) technology specific templates.
TS 32.154:
Backward and Forward Compatibility (BFC); Concept and definitions.
TS 32.155:
Telecommunication management; Requiremen\TS template.
TS 32.156:
Telecommunication management; Fixed Mobile Convergence (FMC) Model Repertoire.
TS 32.157:
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template.
Up

1  ScopeWord‑p. 5
The present document provides the overall concept for all Integration Reference Point (IRP) specifications.
Relevant IRP overview and high-level definitions are already provided in TS 32.101 and TS 32.102.
IRP specifications are intended to be applicable to any management interface (see definition of Integration Reference Point in subclause 3.1).
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".
[3]  Void.
[4]  Void.
[5]
ITU-T Recommendation M.3020 (05/2009): "TMN Interface Specification Methodology".
[6]
OMG IDL Style Guide, ab/98-06-03, June 17, 1998.
[7]
TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point: Information Service (IS)".
[8]
TS 32.601: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements".
[9]
TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
[10]
TS 32.606: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions".
[11]
TS 28.621: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
[12]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP) ; Information Service (IS)".
[13]
TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP) ; Solution Set (SS) definitions".
[14]
TS 28.624: "Telecommunication management; State Management Data Definition Integration Reference Point (IRP) ; Requirements".
[15]
TS 28.625: "Telecommunication management; State Management Data Definition Integration Reference Point (IRP) ; Information Service (IS)".
[16]
TS 28.626: "Telecommunication management; State Management Data Definition Integration Reference Point (IRP); Solution Set (SS) definitions".
[17]
TS 32.107: "Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) ".
[18]
TS 32.156: " Fixed Mobile Convergence (FMC) Model Repertoire".
[19]
TS 32.157: " Integration Reference Point (IRP) Information Service (IS) template".
[20]
TS 28.620: " Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
Up

3  Definitions and abbreviationsWord‑p. 6

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TS 32.101, TS 32.102, TS 32.107, TS 32.157, TS 28.620 and the following apply:
Data Definition IRP:
3GPP publishes IRP specifications relating to commonly used data definitions that can be imported for use by Interface IRP and/or NRM IRP. This term represents all such specifications.
Information Object Class (IOC):
information that can be passed/used in management interfaces and is modelled using the stereotype "Class" in the UML meta-model. For a formal definition of Information Object Class and its structure of specification, see TS 32.157.
Integration Reference Point (IRP):
An architectural concept that is described by a set of specifications for definition of a certain aspect of a management interface, comprising a Requirements specification, an Information Service specification, and one or more Solution Set specifications.
Interface IRP:
3GPP publishes a number of IRP specifications each of which is related to a set of operations and notifications for a specific telecom management domain such as alarm management, configuration management, etc. Interface IRPs also contain definitions of SupportIOCs. This term represents all such specifications.
IRPAgent:
Encapsulation of a well-defined subset of network (element) functions. It interacts with IRPManagers using one or more IRPs. From the IRPManager's perspective, the IRPAgent behaviour is only visible via the IRP(s).
Information Service (IS):
description of the information related to the entities (either network resources or support objects) to be managed and the way that the information may be managed for a certain functional area (e.g. the Alarm IRP Information Service in the fault management area). Information Services are defined for all IRPs.
IRPManager:
Modeling of a user of IRPAgent(s) which interacts directly with the IRPAgent(s) using IRP(s). Since the IRPManager represents an IRPAgent user, it gives a clear picture of what the IRPAgent is supposed to do. From the IRPAgent perspective, the IRPManager behaviour is only visible via the IRP.
Managed Object Class (MOC):
information that can be passed/used in management interfaces in a similar way to IOC.
Network Resource Model (NRM):
description of Information Object Classes representing the manageable aspects of network resources.
NRM IRP:
3GPP publishes a number of IRP specifications each of which is related to a particular NRM (Network Resource Model) as defined in TS 32.101. NRM IRPs do not define any operations or notifications. This term represents all such specifications.
Solution Set (SS):
mapping of the IRP Information Service (IS) defined entities (that are technology-agnostic) to technology specific termed entities.
SupportIOC:
representation of a particular capability, introduced to model a management service.
Yyy IRP:
For a specific Interface IRP such as the Basic CM IRP, when the letters Yyy are replaced by the specific key words naming that IRP (in the given example the Yyy is replaced by "Basic CM"), this term represents all specifications that are part of that Interface IRP.
Up

3.2  AbbreviationsWord‑p. 7
For the purposes of the present document, the abbreviations given in TS 32.101, TS 32.102, TS 32.157 and the following apply:
CORBA
Common Object Request Broker Architecture
EM
Element Manager
GDMO
Guidelines for the Definition of Managed Objects
GUI
Graphical User Interface
IDL
Interface Definition Language
IOC
Information Object Class
IRP
Integration Reference Point
IS
Information Service
MOC
Managed Object Class
NE
Network Element
NM
Network Manager
NRM
Network Resource Model
OMG
Object Management Group
ORB
Object Request Broker
PSA
Product Specific Application
SMP
System Management Processes
SNM
Sub-Network Manager
SS
Solution Set
TMF
TeleManagement Forum
TOM
Telecom Operations Map
UML
Unified Modelling Language
Up


Up   Top   ToC