Content for TS 32.101 Word version: 18.0.0
1 Scope p. 7
The present document establishes and defines the management principles and high-level requirements for the management of PLMNs.
In particular, the present document identifies the requirements for:
- the upper level of a management system;
- the reference model, showing the elements the management system interacts with;
- the network operator processes needed to run, operate and maintain a network;
- the functional architecture of the management system;
- the principles to be applied to management interfaces.
2 References p. 7
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]
ITU-T Recommendation M.3010 (2000): "Principles for a telecommunications management network".
[2]
TS 22.101: "Service aspects; Service Principles".
[3]
TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements".
[4]
RFC 959: "File Transfer Protocol (FTP)"; October 1985, J. Postel, J. Reynolds, ISI. (Status: Standard).
[5]
RFC 783: "Trivial File Transfer Protocol (TFTP)"; rev. 2, June 1981, K.R. Sollins MIT. (Status: Unknown).
[6]
RFC 1157: "Simple Network Management Protocol (SNMP)": May 1990, J. Case, SNMP Research, M. Fedor, Performance Systems International, M. Schoffstall, Performance Systems International, J. Davin, MIT Laboratory for Computer Science. (Status: Standard).
[7]
RFC 2401: "Security Architecture for the Internet Protocol"; November 1998. (Status: Proposed Standard).
[8]
The Object Management Group (OMG) "The Common Object Request Broker Architecture and Specification"!, Revision 2.3, June 1999. http://www.omg.org/technology/documents/vault.htm#CORBA_IIOP
[9] ... [12] Void
[13]
ISO 8571-1 (1988): "Information Processing Systems Open Systems Interconnection File Transfer, Access and Management Part 1: General Introduction".
[14]
ISO 8571-2 (1988): "Information Processing Systems Open Systems Interconnection File Transfer, Access and Management Part 2: Virtual Filestore Definition".
[15]
ISO 8571-3 (1988): "Information Processing Systems Open Systems Interconnection File Transfer, Access and Management Part 3: File Service Definition".
[16]
ISO 8571-4 (1988): "Information Processing Systems Open Systems Interconnection File Transfer, Access and Management Part 4: File Protocol Specification".
[17]
ISO/IEC ISP 10607-1 (1995): "Information technology - International Standardized Profiles AFTnn - File Transfer, Access and Management - Part 1: Specification of ACSE, Presentation and Session Protocols for the use by FTAM".
[18]
ISO/IEC ISP 10607-2 (1995): "Information technology - International Standardized Profiles AFTnn - File Transfer, Access and Management - Part 2: Definition of Document Types, Constraint sets and Syntaxes".
[19]
ISO/IEC ISP 10607-3 (1995): "Information technology - International Standardized Profiles AFTnn - File Transfer, Access and Management - Part 3: AFT 11 - Simple File Transfer Service (Unstructured)".
[20] Void
[21] Void
[22]
ITU-T Recommendation X.25 (1996): "Interface between Data Terminal Equipment (DTE) and Data Circuit Terminating Equipment (DCE) for Terminals operating in the Packet Mode and connected to Public Data Networks by Dedicated Circuit".
[23] ... [42] Void
[43]
ISO/IEC 7776 (1995): "Information technology - Telecommunications and information exchange between systems - High-level data link control procedures - Description of the X.25 LAPB-compatible DTE data link procedures".
[44]
ISO/IEC 8208 (2000): "Information technology - Data communications - X.25 Packet Layer Protocol for Data Terminal Equipment".
[45]
ISO/IEC 8878 (1992): "Information technology - Telecommunications and information exchange between systems - Use of X.25 to provide the OSI Connection-mode Network Service".
[46]
RFC 1006: "ISO Transport on top of the TCP", Marshall T. Rose, Dwight E. Cass, Northrop Research and Technology Center, May 1987. Status: Standard.
[47]
RFC 793: "Transmission Control Protocol (TCP)", September 1981. Status: Standard.
[48]
RFC 791: "Internet Protocol (IP)", September 1981. Status: Standard.
[49]
ITU-T Recommendation X.680 (2002): "Information Technology-Abstract Syntax Notation One (ASN.1): Specification of Basic Notation".
[50]
TR 21.905: "Vocabulary for 3GPP Specifications".
[51]
TS 22.115: "Service aspects; Charging and Billing".
[52]
The Object Management Group (OMG) "The Common Object Request Broker: Architecture and Specification", Revision 2.1, August 1997. http://www.omg.org/technology/documents/vault.htm#CORBA_IIOP
[53]
3GPP TS 32.400-series: "Telecommunication management; Performance Management (PM)".
[54]
TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[55]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[56]
TR 22.121: "Service aspects; The Virtual Home Environment; Stage 1".
[57]
TS 32.140: "Telecommunication management; Subscription Management (SuM) requirements".
[58]
TS 32.141: "Telecommunication management; Subscription Management (SuM) architecture".
[59 to 99]
Void
[100]
TMF GB910: "Telecom Operations Map"; Approved Version 2.1 March 2000, (may be downloaded from http://www.tmforum.org. ).
[101]
TS 32.102: "Telecommunication management; Architecture".
[102]
ITU-T Recommendation M.3013 (2000): "Considerations for a telecommunications management network".
[103]
Void.
[104]
TR 21.801: "Specification Drafting Rules".
[105]
TMF GB910B: "Telecom Operations Map Application Note-Mobile Services: Performance Management and Mobile Network Fraud and Roaming Agreement Management"; Public Evaluation Version 1.1, September 2000. (May be downloaded free from http://www.tmforum.org. )
[106]
OMA Service Provider Environment Requirements, OMA-RD-OSPE-V1_0-20050614-C, The Open Mobile Alliance™ (URL:http://www.openmobilealliance.org/ ).
[107]
TR 32.806: "Telecommunication management; Application guide for use of Integration Reference Points (IRPs) on peer-to-peer (p2p) interface".
[108]
W3C SOAP Version 1.1 recommendation (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ ).
[109]
W3C SOAP Version 1.2 recommendation (http://www.w3.org/TR/soap12-part1/ ).
[110]
TR 32.809: "Telecommunication management; Feasibility study of XML-based (SOAP/HTTP) IRP solution sets".
[111]
TS 32.150: V7.0.0"Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[112]
ITU-T Recommendation M.3050.x (2006) series Enhanced Telecom Operations Map (eTOM).
[113]
ITU-T Recommendation M.3050.1 (2004) Enhanced Telecom Operations Map (eTOM) - The business process framework.
[114]
ITU-T Recommendation M.3050.2 (2004) Enhanced Telecom Operations Map (eTOM) - Process decompositions and descriptions.
[115]
TR-069 Amendment 2, CPE WAN Management Protocol v1.1, Broadband Forum
[116]
WS-I Basic Profile 1.1; http://www.ws-i.org/Profiles/BasicProfile-1.1.html
[117]
W3C Web Services Description Language (WSDL) 1.1; http://www.w3.org/TR/wsdl
[118]
RFC 6241 Network Configuration Protocol (NETCONF); June 2011.
[119]
TS 32.107: "Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)".
3 Definitions and abbreviations p. 10
3.1 Definitions p. 10
For the purposes of the present document, the following definitions apply:
Domain Manager (DM):
provides element management functions and domain management functions for a sub-network. Inter-working domain managers provide multi vendor and multi technology network management functions.
Element Manager (EM):
provides a package of end-user functions for management of a set of closely related types of network elements. These functions can be divided into two main categories: Element Management Functions and Sub-Network Management Functions.
Element Management functions:
for management of network elements on an individual basis. These are basically the same functions as supported by the corresponding local terminals.
Enterprise Systems:
Information Systems that are used in the telecommunication organisation but are not directly or essentially related to the telecommunications aspects (Call Centre's, Fraud Detection and Prevention Systems, Invoicing etc).
Information Service (IS):
Defined in TS 32.150.
Integration Reference Point (IRP):
Defined in TS 32.150.
Managed Object:
Defined in TS 32.150.
Management Infrastructure:
the collection of systems (computers and telecommunications) a PLMN Organisation has in order to manage its network.
Network Element (NE):
a discrete telecommunications entity, which can be managed over a specific interface, e.g. the RNC.
Network Manager (NM):
provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the Network Elements. All communication with the network is based on open and well-standardized interfaces supporting management of multi-vendor and multi-technology Network Elements.
NML Service (NMLS):
It is a NM layer logical entity which is separated from the functionality of the NM. The NMLS is a generic representation of a certain kind of function which has a standardized interface to the NM. The specific functionality on the interface depends on the kind of function.
Network Resource Model (NRM):
Defined in TS 32.150.
Operations System (OS):
a generic management system, independent of its location level within the management hierarchy.
Public Land Mobile Network (PLMN):
see TR 21.905.
PLMN Organisation:
legal entity that is involved in the management of a telecommunications network providing mobile cellular services.
Service:
see TR 21.905.
Service Level Tracing:
see OMA Service Provider Environment Requirements, OMA-RD-OSPE-V1_0-20050614-C [106].
Solution Set (SS):
Defined in TS 32.150.
Sub-Network management functions:
functions related to a network model for a set of Network Elements constituting a clearly defined sub-network, which may include relations between the Network Elements. 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).
3.2 Abbreviations p. 11
For the purposes of the present document, the following abbreviations apply:
API
Application Programming Interface
ASN.1
Abstract Syntax Notation One
ATM
Asynchronous Transfer Mode
B2B
Business to Business
B-ISDN
Broadband ISDN
BBF
Broadband Forum
BOOTP
Boot protocol
CLI
Command Line Interface
COPS
Common Open Policy Service
COPS-PR
COPS Usage for Policy Provisioning
CORBA IIOP
Common Object Request Broker Architecture Internet Inter-ORB Protocol
CORBA
Common Object Request Broker Architecture
CORBA/IDL
Common Object Request Broker Architecture/Interface Definition Language
DCN
Data Communications Network
DECT
Digital Enhanced Cordless Telecommunications
DHCP
Dynamic Host Configuration Protocol
DM
Domain Manager
DNS
Directory Name Service
DSS1
Digital Subscriber System 1
EM
Element Manager
EML
Element Manager Layer
EMS
Element Management System
ES
Enterprise Systems
eTOM
Enhanced Telecom Operations Map® (TeleManagement Forum)
FFS
For Further Study
FMC
Fixed Mobile Convergence
FNIM
Federated Network Information Model
FTAM
File Transfer Access and Management
FTP
File Transfer Protocol
ftp
FTP
GGSN
Gateway GPRS Support Node
Go interface
The interface between the GGSN and the Policy Decision Function (PDF)
GSM
Global System for Mobile communications
HLR
Home Location Register
HSS
Home Subscriber Server
IDL
Interface Definition Language
IETF
Internet Engineering Task Force
IIOP
Internet Inter-ORB Protocol
IN
Intelligent Network
INAP
Intelligent Network Application Part
IRP
Integration Reference Point
IS
Information Service
ISDN
Integrated Services Digital Network
LDAP
Lightweight Directory Access Protocol
LDUP
LDAP Duplication/Replication/Update Protocols
LLA
Logical Layered Architecture
LSA
Licensed Shared Access
MAP
Mobile Application Part
MExE
Mobile Execution Environment
MIB
Management Information Base
MMI
Man-Machine Interface
NE
Network Element
NM
Network Manager
NML
Network Management Layer
NMLS
Network Management Layer Service
NMS
Network Management System
NRM
Network Resource Model
OAM&P
Operations, Administration, Maintenance and Provisioning
OS
Operations System
OSI
Open Systems Interconnection
OSS
Operations Support System
p2p
Peer-to-Peer
PDF
Policy Decision Function
PDH
Plesiochronous Digital Hierarchy
PDP
Policy Decision Point
PIB
Policy Information Base
PKI
Public Key Infrastructure
PLMN
Public Land Mobile Network
PSTN
Public Switched Telephone Network
QoS
Quality of Service
QoE
Quality of Experience
QMC
QoE Measurement Collection
RNC
Radio Network Controller
RSVP
Resource ReserVation Protocol
SAP
Service Access Point
SC
Service Consumer
SD
Service Directory
SDH
Synchronous Digital Hierarchy
sftp
secure ftp
SLA
Service Level Agreement
SNMP
Simple Network Management Protocol (IETF)
SNMP/SMI
SNMP/Structure of Management Information
SOA
Service Oriented Architecture
SOM
Service Operations Management
SP
Service Provider
SS
Solution Set
SS7
Signalling System No. 7
SSH
Secure Shell
SSL
Secure Sockets Layer
TCP/IP
Transmission Control Protocol/ Internet Protocol
tftp
trivial ftp
TM
Telecom Management
TMF
TeleManagement Forum
TMN
Telecommunications Management Network (ITU-T)
TOM
Telecom Operations Map (TMF)
UE
User Equipment
UIM
Umbrella Information Model
UML
Unified Modelling Language
UPT
Universal Personal Telecommunication
USIM
Universal Subscriber Identity Module
UTRA
Universal Terrestrial Radio Access
VHE
Virtual Home Environment
WSDL
Web Service Description Language (W3C)
