ETSI TS 132 102 V8.3.0 (2010-01)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Architecture (3GPP TS 32.102 version 8.3.0 Release 8)

RTS/TSGS-0532102v830

General Information

• Status: Published
• Publication Date: 27-Jan-2010
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Due Date: 05-Jan-2010
• Completion Date: 28-Jan-2010

Standards Content (Sample)

Technical Specification
Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Architecture
(3GPP TS 32.102 version 8.3.0 Release 8)

3GPP TS 32.102 version 8.3.0 Release 8 1 ETSI TS 132 102 V8.3.0 (2010-01)

Reference
RTS/TSGS-0532102v830
Keywords
GSM, LTE, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 2 ETSI TS 132 102 V8.3.0 (2010-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 3 ETSI TS 132 102 V8.3.0 (2010-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 9
4 General . 11
4.1 PLMN Telecom Management . 11
4.1.1 3GPP Reference Model . 11
4.1.2 3GPP Provisioning Entities . 11
4.1.3 Management Infrastructure of the PLMN . 12
4.2 TMN . 12
4.3 Management of Next Generation Networks . 12
5 General view of PLMN Management Physical architectures . 13
6 Basic objectives for PLMN Management Physical Architecture . 14
7 TM Architectural aspects . 15
7.1 Architectural relationship . 15
7.2 Architectural constraints . 16
7.3 Interoperability . 17
7.3.1 Introduction. 17
7.3.2 Interfaces. 17
7.3.3 Entities of a 3GPP system . 19
7.3.4 Open systems approach . 21
7.3.5 Level of openness . 21
7.3.6 Closed interfaces . 21
7.4 Data communication networks . 22
7.5 New technologies . 23
8 3GPP Management Physical architectures . 24
8.1 Compliance Conditions . 24
8.2 Network Element (NE) management architecture . 25
8.3 Subnetwork Management Architecture . 27
8.4 Operations Systems interoperability architecture . 28
8.5 Operations Systems intra-operability architecture . 29
8.6 Enterprise management System interconnection architecture . 30
9 TMN applications . 31
9.1 Management function blocks . 31
9.2 Management physical blocks . 32
9.3 IRP concept enabling TMN applications . 33
10 Void . 34
11 Implementation aspects . 34
12 3GPP TMN Conformance . 35
13 TMN planning and design considerations . 36
13.1 Function attributes . 36
13.2 Functional characteristics . 37
13.3 Critical attributes . 37
13.4 Protocol selection . 37
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 4 ETSI TS 132 102 V8.3.0 (2010-01)
13.5 Communications considerations . 37
14 Mediation/Integration . 38
Annex A (informative): Technology considerations . 40
A.1 Management physical blocks . 40
A.1.1 Operations System (OS) . 40
A.1.2 Void . 40
A.1.3 Void . 40
A.1.4 Void . 40
A.1.5 Void . 40
A.1.6 Void . 40
A.1.7 Void . 40
A.1.8 Network Element (NE) . 40
A.1.9 Data Communication Network (DCN) . 41
A.1.9.1 Transformation . 41
A.1.9.1.1 Adaptation device . 41
A.1.9.1.2 Mediation device . 41
A.1.9.2 Distributed multi-element structure . 41
A.1.10 Management logical layered architecture within the management physical view . 42
A.1.11 Interface concept . 42
A.2 Standard interfaces . 42
Annex B (informative): Overview of a 3GPP System. 44
Annex C (informative): Change history . 45
History . 46

ETSI
3GPP TS 32.102 version 8.3.0 Release 8 5 ETSI TS 132 102 V8.3.0 (2010-01)
Foreword
rd
This Technical Specification (TS) has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 6 ETSI TS 132 102 V8.3.0 (2010-01)
1 Scope
The present document identifies and standardises the most important and strategic contexts in the physical architecture
for the management of PLMNs. It serves as a framework to help define a telecom management physical architecture for
a planned PLMN and to adopt standards and provide products that are easy to integrate.
The requirements identified in the present document are applicable to all further development of 3GPP Telecom
Management specifications as well as the development of PLMN Management products. The present document can be
seen as guidance for the development of all other Technical Specification addressing the management of PLMNs,
except TS 32.101 [2].
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] ITU-T Recommendation M.3010 (2000): "Principles for a Telecommunications management
network".
[2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[3] Void.
[4] ITU-T Recommendation X.200 (1994): "Information technology - Open Systems Interconnection -
Basic Reference Model: The basic model".
[5] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[6] Void.
[7] Void.
[8] Void.
[9] TMF GB910: "Smart TMN Telecom Operations Map (Release 2.1)". http://www.tmforum.org
[10] TMF GB909: "Smart TMN Technology Integration Map (Issue 1.1)". http://www.tmforum.org
[11] ITU-T Recommendation M.3013 (2000): "Considerations for a telecommunications management
network".
[12] 3GPP TS 23.002: "Network architecture".
[13] 3GPP TS 23.101: "General UMTS Architecture".
[14] 3GPP TS 32.111-x: "Telecommunication management; Fault Management;".
[15] OMG: "Unified Modelling Language Specification, Version 1.4, September 2001".
http://www.omg.org/technology/documents/formal/uml.htm
[16] ITU-T Recommendation M.3060/Y.2401 (2006): 'Principles for the Management of Next
Generation Networks '.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 7 ETSI TS 132 102 V8.3.0 (2010-01)
[17] ETSI TS 188 001 V1.2.1 TISPAN; "NGN management; Operations Support Systems
Architecture".
[18] ITU-T Recommendation Y.2011 (2004), "General principles and general reference model for Next
Generation Networks".
[19] ITU-T Recommendation Y.2001 (2004), "General overview of NGN".
[20] ITU-T M.3050.x series (2004),"TMN Enhanced Telecom Operations Map (eTOM)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
architecture: organisational structure of a system or component, their relationships, and the principles and guidelines
governing their design and evolution over time
closed interfaces: privately controlled system/subsystem boundary descriptions that are not disclosed to the public or
are unique to a single supplier
de facto standard: standard that is widely accepted and used but that lacks formal approval by a recognised standards
organisation
Information Service (IS): Defined in 3GPP TS 32.150 [5].interface standard: standard that specifies the physical or
functional interface characteristics of systems, subsystems, equipment, assemblies, components, items or parts to permit
interchangeability, interconnection, interoperability, compatibility, or communications
interoperability: ability of two or more systems or components to exchange data and use information
intra-operability: ability to interchange and use information, functions and services among components within a
system
Integration Reference Point (IRP): Defined in 3GPP TS 32.150 [5].
Managed Object: Defined in 3GPP TS 32.150 [5].
management infrastructure: Defined in TS 32.101 [2]. market acceptance: means that an item has been accepted in
the market as evidenced by annual sales, length of time available for sale, and after-sale support capability.
modular: pertaining to the design concept in which interchangeable units are employed to create a functional end
product.
module: interchangeable item that contains components. In computer programming, a program unit that is discrete and
identifiable with respect to compiling, combining with other modules, and loading is called a module.
Network Resource Model (NRM): Defined in 3GPP TS 32.150 [5].
Next Generation Networks Management (NGNM): Planning, provisioning, installation, maintenance, operation and
administration of next generation telecommunications equipment for transmission or control of resources and services
within NGN transport and service strata. NGNM is defined by ITU-T [16].
NGN service stratum: that part of the NGN which provides the user functions that transfer service-related data and the
functions that control and manage service resources and network services to enable user services and applications.
NGN transport stratum: that part of the NGN which provides the user functions that transfer data and the functions
that control and manage transport resources to carry such data between terminating entities.
open specifications: public specifications that are maintained by an open, public consensus process to accommodate
new technologies over time and that are consistent with international standards
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 8 ETSI TS 132 102 V8.3.0 (2010-01)
open standards: widely accepted and supported standards set by recognised standards organisation or the commercial
market place. These standards support interoperability, portability, and scalability and are equally available to the
general public at no cost or with a moderate license fee.
open systems strategy: focuses on fielding superior telecom capability more quickly and more affordably by using
multiple suppliers and commercially supported practices, products, specifications, and standards, which are selected
based on performance, cost, industry acceptance, long term availability and supportability, and upgrade potential.
physical architecture: minimal set of rules governing the arrangement, interaction, and interdependence of the parts or
elements whose purpose is to ensure that a conformant system satisfies a specified set of requirements. The physical
architecture identifies the services, interfaces, standards, and their relationships. It provides the technical guidelines for
implementation of systems upon which engineering specifications are based and common building blocks are built.
PLMN Organisation: see 3GPP TS 32.101 [2].
plug&play: term for easy integration of HW/SW
portability: the ease with which a system, component, data, or user can be transferred from one hardware or software
environment to another
proprietary specifications: specifications, which are exclusively owned by a private individual or corporation under a
trademark or patent, the use of which would require a license
reference model: a generally accepted abstract representation that allows users to focus on establishing definitions,
building common understandings and identifying issues for resolution. For TMN Systems acquisitions, a reference
model is necessary to establish a context for understanding how the disparate technologies and standards required to
implement TMN relate to each other. A reference model provides a mechanism for identifying the key issues associated
with applications portability, modularity, scalability and interoperability. Most importantly, reference models will aid in
the evaluation and analysis of domain-specific architectures.
scalability: capability to adapt hardware or software to accommodate changing workloads
service specific entities: entities dedicated to the provisioning of a given (set of) service(s). The fact that they are
implemented or not in a given PLMN should have limited impact on all the other entities of the PLMN.
Solution Set (SS): Defined in 3GPP TS 32.150 [5].
specification: document that prescribes, in a complete, precise, verifiable manner, the requirements, design, behaviour,
or characteristics of a system or system component
standard: document that establishes uniform engineering and technical requirements for processes, procedures,
practices, and methods. Standards may also establish requirements for selection, application, and design criteria of
material.
standards based architecture: architecture based on an acceptable set of open standards governing the arrangement,
interaction, and interdependence of the parts or elements that together may be used to form a TMN System, and whose
purpose is to insure that a conformant system satisfies a specified set of requirements.
Support IOC: defined in TS 32.150 [5].
system : any organised assembly of resources and procedures united and regulated by interaction or interdependence to
accomplish a set of specific functions
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 9 ETSI TS 132 102 V8.3.0 (2010-01)
System Architecture (SA): description, including graphics, of systems and interconnections providing for or
supporting management functions. The SA defines the physical connection, location, and identification of the key
nodes, circuits, networks, platforms, etc., and specifies system and component performance parameters. It is constructed
to satisfy Operational Architecture requirements per standards defined in the Physical Architecture. The SA shows how
multiple systems within a subject area link and inter-operate, and may describe the internal construction or operations of
particular systems within the architecture.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3G 3 Generation
AAA Authentication, Authorisation and Accounting
AN Access Network
AS Application Server
ATM Asynchronous Transfer Mode
AUC Authentication Centre
B2B Business-to-Business
BG Border Gateway
BGCF Breakout Gateway Control Function
BM-SC Broadcast-Multicast Service Centre
BSC Base Station Controller
BSS Base Station Subsystem
BTS Base Transceiver Station
C2B Customer-to-Business
CAMEL Customised Applications for Mobile network Enhanced Logic
CBC Cell Broadcast Center
CBS Cell Broadcast Service
CMIS Common Management Information Service
CMISE Common Management Information Service Element
CN Core Network
CORBA Common Object Request Broker Architecture
CRF Charging Rules Function
CS Circuit Switched
CSCF Call Session Control Function
DCN Data Communication Network
DECT Digital Enhanced Cordless Telecommunications
DSS1 Digital Subscriber System 1
EIR Equipment Identity Register
EM Element Manager
E-OS Element Management Layer-Operations System
F/W Firewall
FM Fault Management
FTAM File Transfer, Access and Management
GCR Group Call Register
GDMO Guidelines for the Definition of Managed Objects
GGSN Gateway GPRS Support Node
GMLC Gateway Mobile Location Center
GMSC Gateway MSC
GPRS General Packet Radio Service
GTT Global Text Telephony
HLR Home Location Register
HMI Human Machine Interface
HSS Home Subscriber Server
HTTP HyperText Transfer Protocol
HW Hardware
I-CSCF Interrogating CSCF
IBCF Interconnection Border Control Function
IDL Interface Definition Language
IIOP Internet Inter-ORB Protocol
IMS IP Multimedia Subsystem
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 10 ETSI TS 132 102 V8.3.0 (2010-01)
INAP Intelligent Network Application Part
IP Internet Protocol
IRP Integration Reference Point
IS Information Service
ISDN Integrated Services Digital Network
IWU Inter Working Unit
LCS Location Services
LLA Logical Layered Architecture
LMU Location Measurement Unit
MBMS Multimedia Broadcast Multicast Service
MD Mediation Device
ME Mobile Equipment
MGCF Media Gateway Control Function
MIB Management Information Base
MMI Man-Machine Interface
MML Man-Machine Language
MMS Multimedia Messaging Service
MNP Mobile Number Portability
MNP-SRF Mobile Number Portability/Signalling Relay Function
MRF Multimedia Resource Function
MRFC Multimedia Resource Function Controller
MRFP Multimedia Resource Function Processor
MSC Mobile service Switching Centre
MT Mobile Termination
NE Network Element
NGN Next Generation Networks
NGNM Next Generation Networks Management
NM Network Manager
N-OS Network Management Layer-Operations System
NPDB Number Portability Database
NR Network Resource
NRM Network Resource Model
NSS Network Switching Subsystem
NW Network
OMG Object Management Group
OS Operations System
OSA Open Services Access
OSF Operations System Functions
P-CSCF Proxy CSCF
PDH Plesiochronous Digital Hierarchy
PS Packet Switched
PSA Product Specific Applications
PSS Packet Switched Service
PSTN Public Switched Telephone Network
QA Q-Adapter
QoS Quality of Service
RNC Radio Network Controller
RNS Radio Network System
RSVP Resource ReserVation Protocol
S-CSCF Serving CSCF
SDH Synchronous Digital Hierarchy
SEF Service Element Function
SGSN Serving GPRS Support Node
SGW Signalling Gateway
SIM Subscriber Identity Module
SLA Service Level Agreement
SLF Subscription Locator Function
SMI Structure of Management Information
SMLC Serving Mobile Location Center
SMS Short Message Service
SNM Sub-Network Manager
SNMP Simple Network Management Protocol
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 11 ETSI TS 132 102 V8.3.0 (2010-01)
SS Solution Set
SS7 Signalling System No. 7
SW Software
TA Terminal Adapter
TE Terminal Equipment
TEF Transport Element Function
TM Telecom Management
TMN Telecommunications Management Network as defined in ITU-T Recommendation M.3010 [1]
TrGW Transition Gateway
UE User Equipment
UML Unified Modelling Language
USAT USIM/SIM Application Toolkit
USIM UMTS Subscriber Identity Module
UTRA Universal Terrestrial Radio Access
UTRAN Universal Terrestrial Radio Access Network
VHE Virtual Home Environment
VLR Visitor Location Register
WAG WLAN Access Gateway
WBEM Web Based Enterprise Management
WS WorkStation
4 General
4.1 PLMN Telecom Management
4.1.1 3GPP Reference Model
A 3GPP System is made of the following components:
- one or more Access Networks, using different types of access techniques (GSM, UTRA, DECT, PSTN,
ISDN, .) of which at least one is UTRA;
- one or more Core Networks;
- one or more Intelligent Node Networks, service logic and mobility management, (IN, GSM .);
- one or more transmission networks (PDH, SDH etc) in various topologies (point-to-point, ring,
point-to-multipoint etc) and physical means (radio, fibre, copper, etc.).
The 3GPP system components have signalling mechanisms among them (DSS1, INAP, MAP, SS7, RSVP, etc.).
From the service perspective, the 3GPP system is defined to offer:
- service support transparent to the location, access technique and core network, within the bearer capabilities
available in one particular case;
- user to terminal and user to network interface (MMI) irrespective of the entities supporting the services required
(VHE);
- multimedia capabilities.
4.1.2 3GPP Provisioning Entities
Two major entities, which cover the set of 3GPP functionalities involved in the provision of the 3GPP services to the
user, are identified as follows:
- Home Environment: This entity holds the functionalities that enable a user to obtain 3GPP services in a
consistent manner regardless of the user's location or the terminal used.
- Serving Network: This entity provides the user with access to the services of the Home Environment.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 12 ETSI TS 132 102 V8.3.0 (2010-01)
4.1.3 Management Infrastructure of the PLMN
Every PLMN Organisation has its own Management Infrastructure. Each Management Infrastructure will contain
different functionality depending on the role-played and the equipment used by that Entity.
However, the core management architecture of the PLMN Organisation is very similar. Every PLMN Organisation:
- provides services to its customers;
- needs an infrastructure to fulfil them (advertise, ordering, creation, provisioning, .);
- assures them (Operation, Quality of Service, Trouble Reporting and Fixing, .);
- bills them (Rating, Discounting, .).
Not every PLMN Organisation will implement the complete Management Architecture and related Processes. Some
processes may be missing dependent on the role a particular Organisation is embodying. Processes not implemented by
a particular Organisation are accessed via interconnections to other organisations, which have implemented these
processes (called X-interfaces in the TMN architecture).
The Management architecture itself does not distinguish between external and internal interfaces.
4.2 TMN
TMN (Telecommunications Management Network), as defined in [1], provides:
- an architecture, made of OS (Operations Systems) and NEs (Network Elements), and the interfaces between
them (Q, within one Operator Domain and X, between different Operators);
- the methodology to define those interfaces;
- other architectural tools such as LLA (Logical Layered Architecture) that help to further refine and define the
Management Architecture of a given management area;
- a number of generic and/or common management functions to be specialised/applied to various and specific
TMN interfaces.
The PLMN Management Architecture is largely based on TMN, and will reuse those functions, methods and interfaces
already defined (or being defined) that are suitable for the management needs of a PLMN. However, the new challenges
of 3G Telecom Management may require the exploration and incorporation of other concepts (other management
paradigms widely accepted and deployed).
4.3 Management of Next Generation Networks
Next Generation Networks (NGN) as defined in [18, 19], are essentially about delivering new services that are available
any place, any time, and on any device, through any customer-chosen access mechanism.
NGN Management (NGNM) [16] supports the aims of the NGN by decoupling and make independent, the service
creation/deployment infrastructure from the transport infrastructure. The decoupling is reflected in the NGN
architecture as the separation of the Transport and Service strata and shown as two independent stratums. NGNM also
introduces the NGN management plane, union of the NGN service stratum management plane and the NGN transport
stratum management plane and may include joint management functions, i.e., functions used to manage entities in both
strata plus functions required to support this management [18].
NGNM introduces a new set of grouping of management functionality compared to TMN LLA to better support the
complexity of the NGN .e.g. NGNM Resource Management layer encompasses the Network Management layer and
the Element Management layer.
The PLMN management architecture will facilitate the ITU-T NGN Management principles above where necessary and
suitable.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 13 ETSI TS 132 102 V8.3.0 (2010-01)
5 General view of PLMN Management Physical
architectures
Telecom Management Architectures can vary greatly in scope and detail. The architecture for a large service provider,
with a lot of existing legacy systems and applications, upon which many services are based, will be of high complexity.
In contrast, the architectural needs of a start-up mobile operator providing its services to a small group of value-added
Service Providers will be much less and will probably focus on more short-term needs.
A mobile network operator has to manage many different types of networks as radio networks, exchanges, transmission
networks, area networks, intelligent nodes and substantial amounts of computer hardware/software. This wide variety of
network equipment will most probably be obtained from a variety of equipment vendors. The nature of a mobile radio
network will be heterogeneous and will present a number of operational difficulties for the service provider on enabling
effective and efficient network management.
The standardisation work for the management of a PLMN has adopted the top-down approach and will from business
needs identify functional and informational architectures. The physical architecture will have to meet these
requirements and as there are many ways to build a PLMN it will vary greatly from one TMN solution to another. There
will be many physical implementations, as different entities will take different roles in a PLMN.
It is obvious that it will not be meaningful or even possible to fully standardise a common Telecom Management
physical architecture for PLMNs. The present document will identify and standardise the most important and strategic
contexts and serve as a framework to help define a physical architecture for a planned PLMN.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 14 ETSI TS 132 102 V8.3.0 (2010-01)
6 Basic objectives for PLMN Management Physical
Architecture
The management of a 3G system will put a lot of new requirements to the management systems compared to the second
generation of Mobile telephony. Some of the challenging requirements affecting the physical architecture are:
- To be capable of managing equipment supplied by different vendors.
- To enable TM automation in a more cost efficient way - TM optimised for maximum efficiency and
effectiveness.
- To provide PLMN configuration capabilities that are flexible enough to allow rapid deployment of services.
- To report events and reactions in a common way in order to allow remote control.
- To allow interoperability between Network Operators/Service Providers for the exchange of
management/charging information.
- To be scaleable and applicable to both larger and small deployments.
- Accessibility to information.
- To profit from advances and standards in IT and datacom industry.
The second generation of mobile networks can - from a management point of view - be characterised as the era of
vendor-dependent NE managers. The different OSs had very low interoperability with other systems and functional
blocks could rarely be re-used. The Mobile Telecom Management Networks were far away from the TMN vision where
one vendor's OS should be able to manage other vendors" network elements.
PLMN Organisations need cost-effective management solutions and better time to market focus. Interoperability,
scalability and re-use are keywords for the new generation of management systems.
Many of the new requirements on the management of PLMNs can only be solved by defining and establish a suitable
physical architecture. Thou it is not possible to standardise the one single TM physical architecture, it is evidently so
that the success of a Telecom Management Network of a PLMN Organisation will heavily depend on critical physical
architectural issues. The present document will identify those architectural critical issues.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 15 ETSI TS 132 102 V8.3.0 (2010-01)
7 TM Architectural aspects
7.1 Architectural relationship
The basic aspects of a TM architecture, which can be, considered when planning and designing a TM network are:
- The functional architecture.
- The information architecture.
- The physical architecture.
The management requirements - from the business needs - will be the base for the functional architecture, which will
describe the functions that have to be achieved. The information architecture defines what information that has to be
provided so the functions defined in the functional architecture can be achieved. The physical architecture has to meet
both the functional architecture and the information architectures. Other constraints from realty will also have impact to
the physical architecture as cost, performance, legacy systems and all preferences any operator will have on a big
capital investment as a TM network.
Functional Physical
Architecture Architecture
Business
needs
Information
Architecture
Cost
Performance
Legacy
Preferences
Figure 7.1: Architectural relationship
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 16 ETSI TS 132 102 V8.3.0 (2010-01)
7.2 Architectural constraints
Large software systems, such as a network management system, are a capital investment that operators cannot afford to
scrap every time its requirements change. Operators are seeking cost-effective solutions to their short-term needs. All
these reality-related issues are vital constraints that should be addressed in the definition of the architecture.
The standardisation of 3G systems will bring new and different services that will add new demands on
telecommunications management. Every PLMN organisation will include different functionality depending on the role-
played and the equipment used by that entity. Regulation may force some of the roles that shall be taken. The need to
link systems across corporate boundaries will be a consequence of this.
The rapid evolution of new services and technologies will also put requirements on the PLMN physical management
architecture to accommodate market and technology trends. To future-proof investments and continuously be able to
take advantage of new technologies are important constraints to the physical architecture.
A PLMN TMN should also adopt an architecture that will achieve scalability and extensibility of systems and networks
so the TMN can grow as the services expand over time. To start with a small TMN and easily be able to expand the
TMN after new requirements will be important issues for most PLMN operators.
The Telecom Management Network will be just one part of the overall business of a company. System management,
general security issues and development strategies can be the target for company policies. System architectures and
technology choices, as well as the availability of off-the-shelf commercial systems and software components that fulfil
the requirements established in the present document, may be critical to an operator's implementation of the specified
management architecture.
ETSI
3GPP TS 32.102 version 8.3.0 Release 8 17 ETSI TS 132 102 V8.3.0 (2010-01)
7.3 Interoperability
7.3.1 Introduction
The new requirement on a 3G system TMN will imply a focus change from network element management towards
management of information "information management". Network and service providers make use of different
information in several different ways which also may vary from network to network and from time to time. Basic
information as alarms is of course essential information for localising faults but may also be the key information to be
able to set up a service with a service level agreement.
Numerous of different interfaces can be identified in a PLMN network in the areas of network element management,
network management and service management. The most important and complex of these interfaces will be
standardised but many interfaces of less importance are unlikely to be fully standardised and will be up to the individual
operator and vendor to develop. To adopt mainstream computing technologies, re-use widely used protocols, standards
and an open system architecture will be essential to secure interworking between all physical entities in a PLMN.
Low-cost and general access to management systems information will be needed. Obviously this is the critical issue and
challenging task in the he
...