tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TS 32.642 (SA5)
Configuration Management (CM) –
UTRAN network resources IRP –
Network Resource Model (NRM)

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V11.5.0    2016/03    53 p.
(P) V10.4.0    2016/03    52 p.
(P) V9.4.0    2016/03    55 p.
(P) V8.6.0    2016/03    55 p.
(P) V7.5.0    2008/06    52 p.
(P) V6.7.0    2006/06    35 p.
(P) V5.6.0    2005/04    25 p.
(P) V4.5.0    2005/04    23 p.


Rapporteur:  Mr. Petersen, Robert
See also:  –


This TS is part of an Integration Reference Point (IRP) named "UTRAN Network Resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning UTRAN resources. The "UTRAN Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).

This TS specifies the protocol neutral UTRAN Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in TS 32.622, either by direct reuse or sub-classing, and in addition to that defines UTRAN specific Information Object Classes.

The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs - as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS). To summarize, this TS has the following main purpose: to define the applied UTRAN specific NRM, based on the generic NRM in TS 32.622.

In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (TS 32.602) or the Bulk CM IRP IS (TS 32.612). However, which IS that is applicable is outside the scope of this TS.

This TS (NRM specification) is related to the IS in TS 32.672.


 

Here          Top

 

 

1   Scope   PDF-p. 7
2   References
3   Definitions and abbreviations   PDF-p. 9
4   System overview   PDF-p. 11
5   Modelling approach
6   Information Object Classes   PDF-p. 12
6.1   Information entities imported and local labels
6.2   Class diagram   PDF-p. 13      Up
6.3   Information object class definitions   PDF-p. 18
6.3.1   RncFunction
6.3.2   NodeBFunction   PDF-p. 19
6.3.3   Void
6.3.4   IubLink   PDF-p. 20
6.3.5   UtranRelation   PDF-p. 21
6.3.6   Void
6.3.7   Void
6.3.8   ExternalRncFunction   PDF-p. 22
6.3.9   UtranGenericCell   PDF-p. 23
6.3.10   ExternalUtranGenericCell   PDF-p. 25      Up
6.3.11   UtranCellFDD   PDF-p. 26
6.3.12   UtranCellTDD
6.3.13   UtranCellTDDLcr
6.3.14   UtranCellTDDHcr
6.3.15   ExternalUtranCellFDD   PDF-p. 28
6.3.16   ExternalUtranCellTDD
6.3.17   ExternalUtranCellTDDHcr   PDF-p. 30
6.3.18   ExternalUtranCellTDDLcr
6.3.19   Void
6.3.20   EP_IuCS   PDF-p. 31
6.3.21   EP_IuPS
6.3.22   EP_Iur
6.4   Information relationship definitions   PDF-p. 33
6.5   Information attribute definitions   PDF-p. 40
6.6   Void
6.7   Common Notifications
A   Void
B   RET Control Architecture   PDF-p. 49
C   Change history   PDF-p. 50

Up          Top