Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 28.735  Word version:  16.0.0

Top   Top   None   None   Next
0…   4…

 

0  IntroductionWord‑p. 5
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
Up

1  ScopeWord‑p. 6
The present document is part of an Integration Reference Point (IRP) named "Signalling Transport Network (STN) interface NRM 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 Signalling Transport resources. This IRP comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral STN interface NRM IRP. It reuses relevant parts of the generic NRM in TS 28.622, either by direct reuse or sub-classing, and in addition to that defines Signalling Transport specific Managed Object Classes.
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 is applicable is outside the scope of this document.
Finally, regarding the support of the State Management IRP: IS (TS 28.625), all NRMs of one release shall support the same State Management IRP version.
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]
TS 28.625: "Telecommunication management; State Management Integration Reference Point (IRP); Information Service (IS)".
[4]
TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
[5]
TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[6]
TS 28.622: " Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[7]
TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS)".
[8]
TS 32.612: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Information Service (IS)".
[9]
ITU-T Recommendation Q.700 (03/93): "Introduction to CCITT Signalling System No.7".
[10]
ITU-T Recommendation Q.751.1 (10/95): "Network Element Management Information Model for The Message Transfer Part (MTP)".
[11]
ITU-T Recommendation Q.704 (07/96): "Signalling network functions and messages".
[12]
TS 32.111-2: "Telecommunication management; Fault Management (FM); Part 2: Alarm Integration Reference Point (IRP); Information Service (IS)".
[13]
ITU-T Recommendation Q.702 (11/88): "Signalling Data Link".
[14]
TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3".
[15]
TS 25.410: "UTRAN Iu Interface: General Aspects and Principles".
[16]
TS 25.420: "UTRAN Iur interface general aspects and principles".
[17]
TS 25.430: "UTRAN Iub interface: general aspects and principles".
[18]
TS 48.018: "Base Station System (BSS)-Serving GPRS Support Node (SGSN);BSS GPRS Protocol (BSSGP)".
[19]
TS 48.008: "Mobile Switching Centre-Base Station System (MSC-BSS) interface;Layer 3 specification".
[20]
TS 28.702: "Telecommunication management; Core Network Resources Integration Reference Point (IRP); Information Service (IS)".
[21]
TS 28.652: "Telecommunication management; UTRAN Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[22]
TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".
[23]
TS 29.002: "Mobile Application Part (MAP) specification".
[24]
TS 29.018: "Serving GPRS Support Node (SGSN)-Visitors Location Register (VLR) Gs interface layer 3 specification".
[25]
TS 28.734: "Telecommunication management; Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
[26]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[27]
ITU-T Recommendation E.600 (03/93): "Terms and Definitions of traffic engineering".
[28]
RFC 3332:  "Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)".
[29]
RFC 2960:  "Stream Control Transmission Protocol (SCTP)".
[30]
RFC 3873:  "Stream Control Transmission Protocol (SCTP); Management Information Base (MIB)".
[31]
TS 28.620: "Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
Up

3  Definitions and abbreviationsWord‑p. 7

3.1  Definitions

For the purposes of the present document, the terms and definitions in TS 32.101, 32.102 [2], 32.600 [5], 28.734 [25] and the following apply:
Association:
See definition in TS 28.622.
Managed Element (ME):
See definition in TS 28.622.
Managed Object (MO):
See definition in TS 28.622.
Management Information Model (MIM):
See definition in TS 28.622.
Network Resource Model (NRM):
See definition in TS 28.622.

3.2  AbbreviationsWord‑p. 8
For the purposes of the present document, the following abbreviations apply:
CM
Configuration Management
DN
Distinguished Name
IOC
Information Object Class
IRP
Integration Reference Point
ITU-T
International Telecommunication Union, Telecommunication Standardisation Sector
ME
Managed Element
MIM
Management Information Model
MO
Managed Object
MTP
Message Transfer Part
NE
Network Element
NRM
Network Resource Model
RDN
Relative Distinguished Name
SLC
Signalling Link Code
SLS
Signalling Link Selection
SP
Signalling Point
STN
Signalling Transport Network
STP
Signalling Transfer Point
TP
Termination Point
UML
Unified Modelling Language
Up


Up   Top   ToC