Paging Systems (PS); Enhanced Radio MEssage System (ERMES); Part 7: Operations and maintenance aspects

Network Management Functions Functional Specification Interfaces for O and M (Protocols and Messages)

Sistemi osebnega klica (PS) ¬– Evropski sistem za radijsko sporočanje (ERMES) – 7. del: Vidiki obratovanja in vzdrževanja

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
ETS 300 133-7 E1:2003
English language
76 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 133-7 E1:2003
01-december-2003
6LVWHPLRVHEQHJDNOLFD 36 ¤±(YURSVNLVLVWHP]DUDGLMVNRVSRURþDQMH (50(6 ±
GHO9LGLNLREUDWRYDQMDLQY]GUåHYDQMD
Paging Systems (PS); Enhanced Radio MEssage System (ERMES); Part 7: Operations
and maintenance aspects
Ta slovenski standard je istoveten z: ETS 300 133-7 Edition 1
ICS:
33.070.20 Sistem za osebni klic Paging systems
SIST ETS 300 133-7 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 133-7 E1:2003

---------------------- Page: 2 ----------------------

SIST ETS 300 133-7 E1:2003
EUROPEAN ETS 300 133-7
TELECOMMUNICATION July 1992
STANDARD
Source: ETSI TC-PS Reference: DE/PS-2001-7
ICS: 33.080
ERMES, network management, operations and maintenance
Key words:
Paging systems (PS);
European Radio Message System (ERMES)
Part 7 : Operation and maintenance aspects
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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 1992. All rights reserved.
New presentation - see History box

---------------------- Page: 3 ----------------------

SIST ETS 300 133-7 E1:2003
Page 2
ETS 300 133-7: July 1992
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 133-7 E1:2003
Page 3
ETS 300 133-7: July 1992
Contents
Foreword.7
1 Scope .9
2 Normative references .9
3 Definitions. 10
4 Abbreviations.11
5 ERMES telecommunication management network architecture.12
6 Network management functions.13
6.1 General.13
6.2 Operations .13
6.2.1 Subscriber data management.13
6.2.2 System configuration management .14
6.2.3 Status control.14
6.2.4 Traffic records for charging and accounting .15
6.3 Maintenance.15
6.3.1 Alarm management .15
6.3.1.1 Alarm generation .15
6.3.1.2 Alarm processing and logging.16
6.3.2 Corrective maintenance .16
6.3.2.1 Failed unit isolation .16
6.3.2.2 Fault localisation.17
6.3.2.3 Repair and replacement phases.17
6.3.2.4 Test functions. 17
6.3.2.5 Restoration to service . 17
6.3.3 Preventive maintenance .17
6.4 Performance and QOS management.17
6.4.1 Traffic data.18
6.4.1.1 Average rate of input requests. 18
6.4.1.2 Average rate of call not accepted or conditionally
accepted ACK.18
6.4.1.3 Average rate of input messages .19
6.4.1.4 Average rate of outgoing page messages.19
6.4.1.5 Average message length.19
6.4.1.6 Number of requests for subscriber feature and
supplementary services.19
6.4.1.7 Roaming data. 20
6.4.2 QOS and network performance parameters.20
6.4.2.1 Average call accepted acknowledgement delay .20
6.4.2.2 Average page accepted acknowledgement delay.21
6.4.2.3 Average waiting time for transmission in PNC .21
6.4.2.4 Average waiting time for transmission in PAC .21
6.4.2.5 Average message delivery time .21
6.4.2.6 PNC throughput .22
6.4.3 Traffic management actions .22
6.4.3.1 Flow control .22
6.4.3.2 Active channels re-arrangement.23
6.4.3.3 Modification of control parameters in PAC .23
7 Interfaces. 23

---------------------- Page: 5 ----------------------

SIST ETS 300 133-7 E1:2003
Page 4
ETS 300 133-7: July 1992
7.1 General .23
7.2 Functional interfaces (internal to the network operation) .23
7.2.1 OMC to PNC-OS functional interface .24
7.2.1.1 OMC to PNC-OS messages.24
7.2.1.2 PNC-OS to OMC messages.25
7.2.2 OMC to PAC-OS interface.25
7.2.2.1 OMC to PAC-OS messages.25
7.2.2.2 PAC-OS to OMC messages.25
7.2.3 OMC to BS interface .26
7.2.3.1 OMC to BS messages .26
7.2.3.2 OMC to MD messages .26
7.2.3.3 MD to OMC messages .26
7.2.3.4 MD to BS messages.26
7.3 IOMC (OMC to OMC) interface .26
7.3.1 OMC operations.27
7.3.2 Use of ACSE.27
7.3.3 Use of ROSE.28
7.3.4 OMC addressing.29
8 Operations and Maintenance Centre (OMC).29
8.1 Functions.30
8.1.1 Operations.30
8.1.2 Maintenance .31
8.1.3 Performance and QOS management .32
8.1.4 Calculation of call acceptance.32
8.1.4.1 Availability evaluation for GAs.32
8.1.4.2 Delay evaluation for geographical areas .33
8.2 OMC database .33
9.2 Interworking with the telecommunication network.36
9.2.1 Data from PNC to PNC-OS .36
9.2.2 Actions and data from PNC-OS to PNC.37
9.3 PNC-OS database .37
10 PAC-OS and mediation device functions.38
10.1 PAC-OS .38
10.1.1 Functions.38
10.1.1.1 Operations .38
10.1.1.2 Maintenance.39
10.1.1.3 Performance and QOS management.39
10.1.2 Interworking with the telecommunication network .39
10.1.2.1 Data from PAC to PAC-OS .40
10.1.2.2 Actions and data from PAC-OS to PAC.40
10.1.3 PAC-OS database.40
10.2 Mediation device .41
11 The operations and maintenance part of the base station .41
11.1 Functions.41
11.1.1 Operations.41
11.1.2 Maintenance .42
11.2 BS database.42
Annex A (normative): Formal description of the IOMC .43
A.1 IOMC ROSE operations .43
A.2 IOMC ROSE ASN-1 transcription .52
Annex B (informative): General aspects of telecommunication management.66
B.1 Network management concepts.66
B.1.1 Operations.66
B.1.2 Maintenance .66
B.1.3 Performance and QOS management .68

---------------------- Page: 6 ----------------------

SIST ETS 300 133-7 E1:2003
Page 5
ETS 300 133-7: July 1992
B.2 Network management functions.70
B.2.1 General . 70
B.2.2 Functional distribution .70
Annex C (informative): Conformance with the I3 and I2 interfaces .72
C.1 I3 Interface.72
C.2 I2 interface .74
History.76

---------------------- Page: 7 ----------------------

SIST ETS 300 133-7 E1:2003
Page 6
ETS 300 133-7: July 1992
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 133-7 E1:2003
Page 7
ETS 300 133-7: July 1992
Foreword
This European Telecommunication Standard (ETS) has been produced by the Paging Systems (PS)
Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS comprises seven parts with the generic title "Paging systems; European Radio Message System
(ERMES)". The title of each part is listed below:
- ETS 300 133-1: "Part 1 - General aspects"
- ETS 300 133-2: "Part 2 - Service aspects"
- ETS 300 133-3: "Part 3 - Network aspects"
- ETS 300 133-4: "Part 4 - Air interface specification"
- ETS 300 133-5: "Part 5 - Receiver conformance specification"
- ETS 300 133-6: "Part 6 - Base station specification"
- ETS 300 133-7: "Part 7 - Operation and maintenance aspects"
This part, ETS 300 133-7, specifies the network management of the European Radio Message System
(ERMES) system, specifically the Operations and Maintenance (O&M) aspects, including performance and
Quality of Service (QOS) management.

---------------------- Page: 9 ----------------------

SIST ETS 300 133-7 E1:2003
Page 8
ETS 300 133-7: July 1992
Blank page

---------------------- Page: 10 ----------------------

SIST ETS 300 133-7 E1:2003
Page 9
ETS 300 133-7: July 1992
1 Scope
This part of the seven part European Telecommunication Standard (ETS) 300 133 describes the
operations and maintenance aspects of the European Radio Message System (ERMES). It defines and
describes the architecture of the telecommunication management network and also the network
management functions. Telecommunication management network entities and the functional interfaces
between these entities and the network elements are defined and described.
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These normative
references are cited at the appropriate places in the text and the publications are listed hereafter. For
dated references, subsequent amendments to, or revisions of any of these publications apply to this ETS
only when incorporated in it by amendment or revision. For undated references the latest edition of the
publication referred to applies.
[1] ETS 300 133-3 (1992): "Paging systems; European Radio Message System
(ERMES) Part 3: Network aspects".
[2] ETS 300 133-2 (1992): "Paging systems; European Radio Message System
(ERMES) Part 2: Service aspects".
[3] CCITT Recommendation M.60 "Maintenance terminology and definitions".
[4] CCITT Recommendation G.106: "Terms and definitions related to quality of
service availability and reliability".
[5] CCITT Recommendation M.21: "Principles for a maintenance philosophy and
considerations for maintenance strategy for telecommunication services".
[6] CCITT Recommendation M.20: "Maintenance philosophy for telecommunication
networks".
[7] CCITT Recommendation M.30 (1990): "Principles for a telecommunication
management network".
[8] CCITT Recommendation M.36: "Principles for the maintenance of ISDNs".
[9] CCITT Recommendation Q.795: "Operations, Maintenance and Administration
Part (OMAP)".
[10] CCITT Recommendation X.219: "Remote operations: model, notation and
service definitions".
[11] CCITT Recommendation X.217: "Association control service definition for open
systems interconnection".
[12] CCITT Recommendation X.213: "Network service definition for open systems
interconnection".
[13] CCITT Recommendation X.208: "Specification of abstract syntax notation one
(ASN.1)".
[14] CCITT Recommendation X.209: "Specification of basic encoding rules for
abstract syntax notation one (ASN.1)".

---------------------- Page: 11 ----------------------

SIST ETS 300 133-7 E1:2003
Page 10
ETS 300 133-7: July 1992
3 Definitions
For the purposes of this part of ETS 300 133, the following definitions shall apply.
Basic OSF: the operations system function which controls a network element.
Data communication function: the means for telecommunication management data exchange between
function blocks.
ERMES Telecommunication Management Network (TMN): the operations and maintenance part of the
overall ERMES paging network.
Interface OMC - BS: the functional interface between the operations and maintenance centre and a base
station.
Interface OMC - PAC-OS: the functional interface between the operations and maintenance centre and the
operations system of a paging area controller.
Interface OMC - PNC-OS: the functional interface between the operations and maintenance centre and the
operations system of a paging network controller.
IOMC (OMC - OMC): the interface between different network operators' OMCs.
Maintenance: the technical, administrative and supervisory actions intended to keep an item in, or restore it
to, a state in which it can perform its defined function.
Maintenance entity (ME): an equipment of the telecommunication network which is defined between two or
more interfaces as an object of the network management strategy. The main MEs are the PNC, the PAC
and the BS.
Mediation device: a stand alone device which performs mediation functions.
Mediation functions: functions which act on information passing between network element functions and
operator system functions. Major mediation functions include communication control, protocol conversion
and data handling, communication of primitive functions, processes involving decision making and data
storage.
Network element: an element of the operator network.
Network operations system: performs the network basis telecommunication management network
application functions by communicating with the basic operations system functions.
Operations: the combination of technical and administrative actions that enables an item to perform a given
function.
Operations and maintenance centre: the control and data collection entity associated with a
telecommunication management network.
Operations system: the stand alone system which performs operations system functions.
Operations systems functions: functions performed by the operations system. The OSFs process
information related to telecommunication management to support and/or control the realisation of various
telecommunication management functions.
Paging area controller - operations system: the basic operations system dealing with the paging area
controller.
Paging network controller - operations system: the basic operations system dealing with the paging
network controller.

---------------------- Page: 12 ----------------------

SIST ETS 300 133-7 E1:2003
Page 11
ETS 300 133-7: July 1992
PNC throughput: the number of elementary operations performed by a PNC in a time unit. The term
"elementary operation" indicates the processing of an AdC or an information request message or a
complete message. The throughput offers an idea of load distribution within the network. It can be used for
singling out network bottle-necks, hence giving information for management and design purposes.
Quality Of Service (QOS): a combination of traffic performance, availability, service integrity, service
support and service operability.
Telecommunication management network: the operations and maintenance part of an operator network. It
provides management functions to the telecommunication network and offers communications between
itself and the telecommunication network.
Work station function: the function providing communications between function blocks and the user.
4 Abbreviations
ACK/NACK Positive/Negative acknowledgement
ACSE Association Control Service Element
AdC Address Code
ASN Abstract Syntax Notation
BS Base Station
DCF Data Communication Functions
DCN Data Communication Network
EOM End of Message
FSI Frequency Subset Indicator
FSN Frequency Subset Number
GA Geographical Area
HW Hardware
I2 Interface PAC-BS
I3 Interface PNC-PAC
IOMC Interface OMC-OMC
LCN Local Communication Network
MD Mediation Device
ME Maintenance Entity
MEF Maintenance Entity Function
MHS Message Handling System
MF Mediation Function
MMI Man Machine Interface
NE Network Element
NEF Network Element Function
NM Network Management
NMF Network Management Function
OMC Operations and Maintenance Centre
O&M Operations and Maintenance
OS Operations System
OSF Operations System Functions
OSI Open System Interconnect
PA Paging Area
PAC Paging Area Controller
PAC-OS Paging Area Controller - Operations System
PDU Protocol Data Unit
PNC Paging Network Controller
PNC-H Paging Network Controller - Home
PNC-I Paging Network Controller - Input
PNC-OS Paging Network Controller - Operations System
PNC-T Paging Network Controller - Transmit
PSPDN Packet Switched Public Data Network
PSTN Public Switched Telephone Network
QAF Q-Adapter Function
QOS Quality of Service

---------------------- Page: 13 ----------------------

SIST ETS 300 133-7 E1:2003
Page 12
ETS 300 133-7: July 1992
ROSE Remote Operations Service Element
RF Radio Frequency
RP Reference Point
SDU Service Data Unit
SEF Support Entity Function
SW Software
TLC Telecommunication
TMN Telecommunication Management Network
TO Tone Only
TX Transmitter
WSF Work-Station Function
5 ERMES telecommunication management network architecture
The ERMES system functional architecture is shown in figure 1. The telecommunication (TLC) and
Telecommunication Management Network (TMN) environments are clearly separated.
The network management actions and functions required to support this network can be grouped in three
categories:
- operations;
- maintenance;
- performance and Quality of Service (QOS) management.
A further category covering network administration is the responsibility of individual network operators and
does not come within the scope of this specification.
Within each operator network the following network elements are the object of operations and
maintenance actions:
- the Paging Network Controller (PNC);
- the Paging Area Controller (PAC);
- the Base Station (BS);
- the interconnection links.
Three classes of Operations System Functions (OSFs) can be identified in the network. The basic OSFs
are associated with a particular network element. The network OSFs are responsible for management
actions involving the entire network. The service OSFs are responsible for transactions between operator
networks and interaction with service providers.
The entities which deal with the TMN part of the operator network are Operations and Maintenance Centre
(OMC), PNC-OS, PAC-OS and Mediation Device (MD). In particular:
- the OMC deals with the network Operation System (OS) and service OS functions. The OMC
controls all the Operations and Maintenance (O&M) functions in the operator network and
exchanges data with other OMCs;
- the PNC-OS and PAC-OS deal with the basic OSFs related to the associated telecommunication
entity;
- the MD handles the mediation functions for the connected BSs. It implements concentration,
distribution and protocol conversion.
OSs and MDs can be functionally separated from the related network elements and they may be
implemented together.
Each OS can have its own database where information about the entity status is stored. If lower level
entities exist, some O&M information about them should also be stored in the database. This database
may also contain information required by the telecommunication network.

---------------------- Page: 14 ----------------------

SIST ETS 300 133-7 E1:2003
Page 13
ETS 300 133-7: July 1992
Every network element should contain maintenance entity functions and support entity functions involved in
the transfer of maintenance information, the failure handling process and basic traffic measurements.
General aspects and the philosophy of operations, maintenance and performance management are
described in Annex B along with Network Management Functions (NMFs) contained in the network
elements and the OSFs.
                                       |
                                       | TMN2
                                       |
       �˜˜˜˜˜˜˜¿                            |    �˜˜˜˜˜˜˜¿
       ‡    ‡                            |    ‡    ‡
       ‡    ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜|˜˜˜˜˜˜˜˜·    ‡
       ‡ OMC ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿           |    ‡ OMC ‡
       ‡    ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿     ‡           |    ‡    ‡
       ‡    ˆ˜˜˜˜˜˜˜˜˜˜¿      ‡     ‡           |    ‡    ‡
       �˜˜˜´˜˜˜�     ‡      ‡     ‡           |    �˜˜˜˜˜˜˜�
         ‡       ‡      ‡     ‡           |
       �˜˜˜`˜˜˜¿     ‡      ‡     ‡           |
       ‡    ‡     ‡      ‡     ‡           +--------------------
       ‡    ‡     ‡      ‡     ‡
       ‡PNC-OS ‡     ‡      ‡     ‡
       ‡    ‡     ‡      ‡     ‡
       ‡    ‡     ‡      ‡     ‡
       �˜˜˜´˜˜˜�     ‡      ‡     ‡
         ‡     �˜˜˜˜`˜˜¿  �˜˜˜˜`˜˜¿    ‡
         ‡     ‡    ‡  ‡    ‡    ‡
         ‡     ‡    ‡  ‡    ‡  �˜˜`˜˜¿
         ‡     ‡PAC-OS ‡  ‡PAC-OS ‡  ‡ MD ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
         ‡     ‡    ‡  ‡    ‡  ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜¿     ‡
         ‡     ‡    ‡  ‡    ‡  �˜˜˜˜˜�       ‡     ‡
         ‡     �˜˜˜´˜˜˜�  �˜˜˜´˜˜˜�            ‡     ‡
TMN1       ‡       ‡      ‡              ‡     ‡
-----------------‡-------------‡------------‡----------------------------‡---------‡---------------
TLC1       ‡       ‡      ‡              ‡     ‡
         ‡     �˜˜˜`˜˜˜¿    ‡              ‡     ‡
         ‡     ‡    ‡    ‡              ‡     ‡
         ‡     ‡    ‡    ‡              ‡     ‡
         ‡     ‡ PAC ‡    ‡              ‡     ‡
       �˜˜˜`˜˜˜¿   ‡    ‡    ‡              ‡     ‡
       ‡    ˆ˜˜˜˜˜·    ‡    ‡              ‡     ‡
       ‡    ‡   �˜˜˜˜˜˜˜�    ‡              ‡     ‡
       ‡ PNC ‡           ‡              ‡     ‡
       ‡    ‡         �˜˜˜`˜˜˜¿            ‡     ‡
       ‡    ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·    ‡           �˜˜`˜˜¿   ‡
       �˜˜˜˜˜˜˜�         ‡    ‡           ‡ BS ‡   ‡
                    ‡ PAC ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·   ‡   ‡
                    ‡    ‡           �˜˜˜˜˜�  �˜˜`˜˜¿
                    ‡    ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜· BS ‡
                    �˜˜˜˜˜˜˜�                ‡   ‡
                                        �˜˜˜˜˜�
Figure 1: ERMES system functional architecture
6 Network management functions
6.1 General
The network management functions identified in Clause 5 are defined in this clause and other information
which aids understanding of their characteristics and objectives, are described.
6.2 Operations
The term operations is intended to include configuration management as well as some of the more
classical concepts such as status handling and recording functions.
6.2.1 Subscriber data management
Subscriber data management, as an administrative function, is mainly a network operator matter.
The subscription status database for both mobile and fixed subscribers is associated with the PNC as
described in ETS 300 133-3 [1], subclauses 13.2.1 to 13.2.5.
The OMC
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.