1、ETR 300-4 July 1997 Source: EP-TETRA Reference: DTWTETRA-O1 O1 1-4 ICs: 33.020 Key words: TETRA, network management Terrestrial Trunked Radio (TETRA); Voice plus Data (V + D); Designers guide; Part 4: Network management ETSI European Telecommunications Standards Institute ETSI Secretariat Postal add
2、ress: F-O6921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400: c=fr, a=atlas, p=etsi, s=cecretariat - Internet: secretariatQetsi.fr Tel.: +33 4 92 94 42 O0 - Fax: +33 4 93 65 47 16 Copyright Notification: No part may be reproduced e
3、xcept as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards institute 1997. All rights reserved. I STD-ETSI ETR 300-4-ENGL 1777 3400855 0235249 727 I Page 2 ETR 300-4: July 1997 I i I Whilst every
4、 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. Contents Foreword . _.
5、5 1 Scope . 7 2 References 7 3 Definitions and abbreviations . 7 Definitions _. . 7 3.2 Abbreviations . 8 3.1 4 General principles of network management . - 8 4.1 Introduction _.- 8 4.2 What it does . 9 4.3 General recommendations 9 4.4 Using network management as a tool . 10 4.5 Management Function
6、al Areas (MFA) . . 10 5 Architecture and services 12 5.1 CNM/LNM concept 12 5.2 Services . . 12 5.2.1 Typical central services . 12 5.2.2 Typical local services 13 5.3.1 Single tier system 14 5.3.2 Multi-tier system 14 5.3.3 Multiple supplier system 15 5.3 Architectures 14 6 Options for integration
7、. 16 7 Users specification check list . 17 7.1 Matters to be taken into account 17 7.1.1 Organization of network management 17 7.1.2 Geographical division of management facilities 17 7.1.3 Distribution of management functions among players 17 7.1.4 Flexibility of the network management system 18 7.2
8、.1 What is in ETR 292 . 18 7.2.2 Writing functional requirements . 18 7.2.3 Writing requirements for network management protocols and platforms . 19 7.2.4 Other requirements . 19 Writing requirements . 18 7.2 Annex A: Annotated list of references . 20 A.l TMN 20 A.2 OS1 management 20 A.3 SNMP . 21 H
9、istory . 22 STD-ETSI ETR 300-Li-ENGL 3777 M 3400855 0235253 385 W Page 5 ETR 300-4: July 1997 Foreword This ETSI Technical Report (ETR) has been produced by ETSi Project TErrestrial Trunked RAdio (TETRA) of the European Telecommunications Standards institute (ETSI). ETRs are informative documents re
10、sulting from ETSi studies which are not appropriate for European Telecommunication Standard (ETS) or interim European Telecommunication Standard (I-ETS) status. An ETR may be used to publish material which is either of an informative nature, relating to the use or application of ETSs or I-ETSs, or w
11、hich is immature and not yet suitable for formal adoption as an ETS or I-ETS. Previous gage is blank STD*ETSI ETR 300-9-ENGL 1797 W 3900855 0235252 213 Page 7 ETR 300-4: July 1997 1 Scope This ETSI Technical Report (ETR) is intended to serve as an informative reference document for network operators
12、 or managers of mobile radio systems who are contemplating TErrestrial Trunked RAdio (TETRA) solutions. It aims to explain the general requirements for network management, the implications of different network architectures on the services needed at particular locations and how these can be realised
13、. Within TETRA a standardized management interface (15) will facilitate central management of inter- working between different systems (e.g. systems from different manufacturers). Management at a central level will generally require a different set of services to those provided locally in individual
14、 systems. Typical local and central services are summarized in this ETR (see subclause 5.2) and many of these are defined in greater detail in ETR 292 l. The use of the standardized interace is just one option for integrating different management systems. Other bespoke solutions may be required if a
15、dditional central services are needed or if interface 15 is not available in early releases of TETRA systems. This ETR examines alternative options (see clause 6) to give practical guidance to those considering such integration and includes a useful check list for drawing up user specifications for
16、network management facilities (see clause 7). 2 References For the purposes of this ETR the following references apply: ETR 292: “Terrestrial Trunked Radio (TETRA); User requirements for network management“. Pl ITU-T Recommendation M.3400: “TNM Management Functions“. The reader is referred to annex
17、A for a list of further useful information. 3 Definitions and abbreviations 3.1 Definitions For the purposes of this ETR, the following definitions apply: Base Station (BS): A physical grouping of equipment which provides the fixed portion of the air interface. One BS transmits and receives radio si
18、gnals to and from a single location area (a single region of geographical coverage). gateway: A ,device which will enable the interconnecting of two networks which inherently use different and incompatible protocols. network: A collection of subscriber terminals interconnected through telecommunicat
19、ions devices. real time: Refers to the generation of network management information in a timeframe comparative to the real life process that it is controlling or monitoring. signalling: The exchange of information specifically concerned with the establishment and control of connections, and with man
20、agement, in a telecommunication network. site: Physical location within the network. subscriber activity log: A system record which contains information on attachkietach Individual TETRA Subscriber Identity (ITSI); enable/disable terminal; registrations; location updates vs. time: call re-establishm
21、ent; authentication; call start time, call end time, and called party: type of call; supplementary services invoked; whether uplink Bit Error Ratio (BER) or Message Error Rate (MER) are below an operator predetermined threshold; plus any other relevant activity record. Previous page is blank STD-ETS
22、I ETR 3UII-4-ENGL 3777 3L100855 0235253 158 Page 8 subscriber data: A system record which contains information on the individual subscriber ITSI, Group TETRA Subscriber Identities (GTSls), supplementary services allowed, privileges allowed and other system accesses allowed. ETR 300-4: July 1997 subs
23、criber management: The functionality within the management system, for dealing with subscribers to the system. subscriber terminal: An equipment which an internal user can use to communicate with another user. Mobile Stations (MS) and Line Stations (LS) are the only types of subscriber terminal. sup
24、plementary service: A supplementary service modifies or supplements a bearer service or a teleservice. A supplementary service cannot be offered to a customer as a stand alone service. It should be offered in combination with a bearer service or a teleservice. Switching and Management Infrastructure
25、 (SwMI): All of the TETRA equipment for a Voice plus Data (V+D) network except for subscriber terminals. The SwMI enables subscriber terminals to communicate with each other via the SwMI. transaction (packet transaction): All the processes and procedures associated with the transmission of one packe
26、t of information between peer network layer protocol entities on opposite sides of the air interface . transaction (voice transaction): Part of a voice call comprising the transmissions of each talking party. The total of all transactions make up the call. 3.2 Abbrevlatlons For the purposes of this
27、ETR the following general abbreviations apply: ASN.l BER BS CMIP CNM GTSI ISTI LNM LS MER MFA MIB MS NMF NMS RFC os I SMI SNMP SwMI TMN V+D Abstract Syntax Notation one Bit Error Rate Base Station Common Management Information Protocol Central Network Management Group TETRA Subscriber Identity Indiv
28、idual TETRA Subscriber Identity Local Network Management Line Station Message Error Rate Management Functional Area Management Information Base Mobile Station Network Management Facility Network Management System Request For Com ment Open Systems Interconnect Structure of Management Information Simp
29、le Network Management Protocol Switching and Management Infrastructure Telecommunications Management Network Voice plus Data 4 General principles of network management 4.1 Introduction Network management provides a distributed application enabling monitoring and control of network resources, in orde
30、r to control the overall environment in an orderly fashion. It has to interface across all of the physical elements in a network, and to this end it is increasingly important that open standards are adopted as the norm in all network elements, enabling the control of the network to be undertaken by
31、an integrated network management system. STD-ETSI ETR IO-ENGL 1,997 rn 3400 OZIAZL ow m Page 9 ETR 300-4: July 1997 It is important to be able to receive information and apply controls to all elements in a network in an efficient manner. The elements and services that are contained within a managed
32、network need to be modelled in an abstract manner, so as to allow the operator to exercise actions and controls without needing in-depth knowledge of each of the pieces of equipment being managed. 4.2 What it does Network management covers all activities concerned with monitoring and controlling a n
33、etwork e.g. planning, buildinglexpanding, operating and making the most efficient use of the available resources. The typical features of a network management system are: - planning; - service provision; - network monitoring; - fault management; - network traffic management: - configuration (includi
34、ng subscriber management). Network management applications are based around management frameworks, examples of these are Open Systems Interconnect (OSI), Telecommunications Management Network (TMN) and Simple Network Management Protocol (SNMP). These frameworks provide an inter-operable interface to
35、 achieve interconnection between various types of equipment, communicating via a defined management protocol. The two most common open protocols are Common Management Information Protocol (CMIP) and SNMP. A management framework enables the use of generic information models and standard protocols and
36、 identifies uniquely the inter-operable interface for co-operating management applications. Typical components of a framework are: - managed objects: - the term managed object is used as means to describe management information; - Structure of Management Information (SMI): - defines how to define ne
37、w managed objects, places restrictions on their types and specifies rules for naming. A collection of managed objects is viewed as the schema for the Management Information Base (MIB); - data representation: - to express the format of the packets exchanged in a machine independent way, a formal syst
38、em is used, the most common form being Abstract Syntax Notation (ASN.1). This is used in the definition of the MIB. The interoperable interface = SMI + MIB + management protocol. 4.3 General recommendations Management systems need to be flexible and have a distributed modular architecture that allow
39、s service providers to adapt to customer needs. Given the sophistication and growth of services, a flexible management environment has to be established in order to: - enable rapid service deployment; - promote faster service activation; - efficiently manage and distribute data throughout the networ
40、k. STDeETSI ETR 300-4-ENGL 1797 M 3400855 0215255 T20 Page 10 ETR 300-4: July 1997 Network management systems should also aid the reduction of costs and the provisioning of services in a competitive and timely manner, this can be addressed by: - elimination of redundant processes and equipment: - im
41、provement in service responsiveness; - tuning the performance and capacity of the network. Flexibility of management systems can be achieved by incorporating more of the intelligence into the network elements, this re-distribution of functionality will enable management systems to maintain a high le
42、vel end-to-end view of the services and resources being managed. 4.4 Using network management as a tool Management tools provide the ability to take raw information from a managed system and convert that information into an understandable form suitable for the person using it. A network management t
43、erminal is capable of representing the network in a form which reflects the users function and their need for information. This is not restricted to a purely physical interpretation of the network, but can be used to show administrative information, such as usage, billing information, subscriber sta
44、tistics etc. Management terminals may be used by many functions within an organization, e.g. network administrators and accountants. Users access the same source of information, however it will be presented as different views of the system. An accountant may display regions denoting financial centre
45、s. Each region containing tariff, service and subscriber details, including details of calls made, network usage and discounting packages for each subscriber or sub network. The network administrator will be interested in the low level physical components and their inter- connectivity within the who
46、le system. 4.5 Management Functional Areas (MFA) Management Functional Areas (MFAs) are described in ITU-T Recommendation M.3400 2. A MFA will contain many management functions, which are the smallest part of the management framework as described by TMN. Table 1 provides an overview of each of the M
47、FAs. STD*ETSI ETR 300-9-ENGL 1777 39013855 021525b 7b7 M Page 11 ETR 300-4: July 1997 Table 1 : Overview of MFAs Functional Area erformanCe -ault ;onfiguration kcounting Security Description This provides functions to evaluate and report on the behaviour of equipment and the effectiveness of the ope
48、ration of the network. The functions generally supported are: performance monitoring; performance control performance analysis. This is a set of functions which allow the detection, isolation and correction of abnormal operation and fault conditions within a telecommunications network. Typical funct
49、ions provided are: alarm management; fault localization; testing; trouble management. Provides functions to exercise control, collect and provide information to network elements. Typical uses of this function are: provisioning; element configuration; database management; status and control; subscriber manaqement. Provides functions to allow the use of the network or service to be measured and the costs for the usage to be determined. The main functions in this area are: billing; tariffing. This function is concerned with the overall security of network management in
