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.734
Signalling Transport Network (STN) interface NRM IRP –
Requirements

3GPP‑Page   ETSI‑search   CONTENT↓
V19.0.0 (PDF)  2025/09  11 p.
V18.0.0  2024/03  11 p.
V17.0.0  2022/03  11 p.
V16.0.0  2020/06  11 p.
V15.0.0  2018/06  11 p.
V14.0.0  2017/03  11 p.
V13.0.0  2016/01  11 p.
V12.0.0  2014/10  11 p.
V11.1.0  2014/06  11 p.
Rapporteur:
Dr. Pollakowski, Olaf
Nokia Networks

Content for  TS 28.734  Word version:  19.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.734:
Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements.
28.735:
Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS).
28.736:
Signalling Transport Network (STN) interface 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 (NRs), 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 Signalling Transport Network (STN) interface NRM 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]
TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3".
[5]
ITU-T Recommendation Q.751.1 (10/95): "Network Element Management Information Model for The Message Transfer Part (MTP)".
[6]
ITU-T Recommendation M.3100 (07/95): "Generic Network Information Model".
[7]
ITU-T Recommendation Q.704 (07/96): "Signalling network functions and messages".
[8]
ITU-T Recommendation Q.702 (11/88): "Signalling Data Link".
[9]
3GPP TS.28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[10]
TS 32.405: "Telecommunication management; Performance Management (PM); Performance measurements Universal Terrestrial Radio Access Network (UTRAN)".
[11]
RFC 3332:  "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA).
[12]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[13]
TS 32.107: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)".
Up

3  Definitions and abbreviations  p. 5

3.1  Definitions  p. 5

For the purposes of the present document, the following terms and definitions apply:
Integration Reference Point (IRP):
see TS 32.150.
Network Resource Model (NRM):
See definition in TS 28.622.
Termination Point:
see ITU-T M.3100 [6].

3.2  Abbreviations  p. 6

For the purposes of the present document, the following abbreviations apply:
CM
Configuration Management
GSM
Global System for Mobile communication
IP
Internet Protocol
IRP
Integration Reference Point
ITU-T
International Telecommunication Union, Telecommunication Standardisation Sector
MTP
Message Transfer Part
NE
Network Element
NR
Network Resource
NRM
Network Resource Model
OS
Operations System
QoS
Quality of Service
RNC
Radio Network Controller
STN
Signalling Transport Network
UMTS
Universal Mobile Telecommunications System

4  Requirements  p. 7

The following general and high-level requirements apply for the present IRP:
A)
IRP-related requirements in TS 32.101.
B)
IRP-related requirements in TS 32.102.
C)
IRP-related requirements in TS 32.600.
The NRM defined by this IRP:
D)
Shall support communications for telecommunication network management purposes, including management of converged networks.
E)
Is a member of the Federated Network Information Model (FNIM) [13] and its information is derived from FNIM Umbrella Information Model (UIM) [9].
In addition to the above, the following more specific requirements apply.
Up

4.1  MTP3 Configuration Management  p. 7

a)
It shall be possible for IRPManager to retrieve configuration information related to MTP3 signalling managed entity.
b)
When the configuration information of MTP3 signalling managed entities changes, corresponding notifications shall be generated to IRPManager.
c)
When the status of MTP3 signalling managed entities changes, corresponding notifications shall be generated to IRPManager.
d)
It shall be possible for IRPManager to identify which technology that the STN is based on (e. g. MTP3, MTP3B [4]);
e)
The interface shall allow for the viewing of parameters of the MTP3 signalling point, MTP3 signalling link set termination point, MTP3 signalling link termination point, MTP3 signalling route and MTP3 signalling route set [4], [5], [7], [8].
Up

4.2  M3UA Configuration Management  p. 7

a)
It shall possible for IRPManager to retrieve configuration information related to M3UA signalling managed entities.
b)
When the configuration information of M3UA signalling managed entities changes, corresponding notifications shall be generated to IRPManager.
c)
When the status of M3UA signalling managed entities changes, corresponding notifications shall be generated to IRPManager.
d)
The interface shall allow for the viewing of parameters of the M3UA signalling point, M3UA signalling link set termination point, M3UA signalling link termination point, M3UA signalling route and M3UA signalling route set ([4], [11]).
Up

4.3  Fault Management  p. 7

Any fault detected by the signalling managed entity (including signalling point, signalling link set termination point, signalling link termination point, signalling route and signalling route set [4], [5], [7], [8]) shall be passed up to the IRPManager.

4.4  Performance Management  p. 8

It shall be possible for IRPManager to collect and monitor performance data. The detailed mesurement data to be defined in TS 32.405.

5  Issues  p. 8

The NRM shall allow to be extended to support other technologies based Signalling Transport Network in the future (e.g. IP-based; see TS 29.202).

$  Change History  p. 9

Up   Top