Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 28.621
Generic NRM IRP –
Requirements

3GPP‑Page   ETSI‑search   CONTENT↓
V18.1.0 (PDF)  2024/09  9 p.
V17.1.0  2024/09  9 p.
V16.1.0  2024/09  9 p.
V15.2.0  2024/09  9 p.
V14.0.0  2016/12  9 p.
V13.0.0  2016/01  9 p.
V12.0.0  2014/10  9 p.
V11.1.0  2014/06  9 p.
Rapporteur:
Mr. Scott, Mark
Ericsson LM

Content for  TS 28.621  Word version:  18.0.0

Here   Top

0  Introduction  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:
28.621:
Generic Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
28.622:
Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
28.623:
Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and network resources , and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs.
CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs.
Up

1  Scope  p. 5

The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Generic Network Resource Model IRP.

2  References  p. 5

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]
TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[4]  Void
[5]  Void
[6]  Void
[7]
TS 28.620: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
[8]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[9]
TR 21.905: "Vocabulary for 3GPP Specifications".
Up

3  Definitions and abbreviations  p. 5

3.1  Definitions  p. 5

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Element Manager (EM):
provides a package of end-user functions for management of a set of closely related types of Network Elements (NEs). These functions can be divided into two main categories:
  • Element Management Functions for management of NEs on an individual basis. These are basically the same functions as supported by the corresponding local terminals.
  • Sub-Network Management Functions that are related to a network model for a set of NEs constituting a clearly defined sub-network, which may include relations between the NEs. This model enables additional functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning).
IRP:
See TS 32.101.
IRP Information Service:
See TS 32.101.
IRP Solution Set:
See TS 32.101.
Information Object Class (IOC):
See TS 28.622 clause 3.1 Information Object Class (IOC).
Network Element (NE):
is a discrete telecommunications entity, which can be, managed over a specific interface e.g. the RNC.
Network resource:
See definition in TS 28.622.
Up

3.2  Abbreviations  p. 6

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
CM
Configuration Management
IOC
Information Object Class

4  Requirements  p. 7

The following general and high-level requirements apply for the present IRP:
  1. IRP-related requirements in TS 32.101.
  2. IRP-related requirements in TS 32.102.
  3. IRP-related requirements in TS 32.600.
In addition, the NRM defined by this IRP:
  1. Shall be generic, i.e. not contain any domain specific definitions such as UTRAN or CN entities. Examples of generic entities are: High-level IOCs for containment of other more domain-specific IOCs, and abstract IOCs for sub-classing by other more domain-specific IOCs.
  2. Shall support management of UMTS-GSM Inter-system handover.
  3. Shall support communications for telecommunication network management purposes, including management of converged networks.
  4. Is a member of the Federated Network Information Model (FNIM) [6] and its information is derived from FNIM Umbrella Information Model (UIM) [7].
  5. Shall support management of networks that include virtualized network functions.
Up

$  Change History  p. 8

Up   Top