ETSI ETR 292 ed.1 (1997-07)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Technical requirements specification; Network management33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:ETR 292 Edition 1PSIST ETR 292:2000en01-julij-2000PSIST ETR 292:2000SLOVENSKI
STANDARD



PSIST ETR 292:2000



ETSIETR 292TECHNICALJuly 1997REPORTSource: EP-TETRAReference: DTR/TETRA-01015ICS:33.020Key words:TETRA, network managementTerrestrial Trunked Radio (TETRA);Voice plus Data (V+D);Technical requirements specification;Network managementETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1997. All rights reserved.PSIST ETR 292:2000



Page 2ETR 292: July 1997Whilst 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.PSIST ETR 292:2000



Page 3ETR 292: July 1997ContentsForeword.71Scope.92References.93Definitions and abbreviations.103.1Definitions.103.2Abbreviations.114Objectives and approach.124.1Objectives.124.2Approach adopted.124.3Problems with the definition of management services using ITU methodology.124.4Simplified methodology.135Overview of network management in TETRA.145.1TMN reference system architecture.145.2Role of players.145.3Non-standardized aspects.155.4Standardized aspects.156TMN MS description.166.1Reference Telecommunications Management Network.166.2Basis for Telecommunications Management Network functionality.166.3Subscriber management.176.3.1Management goals.176.3.2Subscriber basic data management.176.3.2.1Permanent actions.176.3.2.2Temporary actions.186.3.2.3Protection of subscriber data.186.3.2.4Subscriber activity log and subscriber diagnostics.186.3.2.5Equipment management.196.3.3Supplementary service management.196.3.3.1Permanent actions.196.3.3.2Temporary actions.206.3.4Migration management (individuals and groups).206.4Configuration management.216.4.1Management goals.216.4.2General configuration management features.226.4.2.1Operator requirements.226.4.2.2Influenced network elements.226.4.2.3System parameters to be specified.226.4.2.4Software management.236.4.2.5Administration of system configuration data.236.4.3Fixed network configuration management.236.4.3.1Internal SwMI routing.236.4.3.2Communication interface management.236.4.3.2.1Administration of system data.236.4.3.2.2ISI management.246.4.3.2.3Gateway management.246.4.3.2.4Line Station (LS) interfacemanagement.256.4.4Radio network configuration management.256.4.4.1Configuration.256.4.4.2Reconfiguration of existing network elements.266.5Traffic measurement.26PSIST ETR 292:2000



Page 4ETR 292: July 19976.5.1Management goals.266.5.2Traffic measures.266.6Performance measurement.276.6.1Management goals.276.6.2Administration of performance measurements.276.6.3Performance measurement data generation.286.6.4Performance measurement data storage.296.6.5Measured performance data presentation.306.6.6Performance measurement data transfer.306.7Security aspects.316.7.1Management goals.316.7.2Management of security of network management system.316.7.3Security management (e.g. encryption key management).326.7.4Access to local network management facilities from the centre.336.8Accounting management.336.8.1Management goals.336.8.2Tariffing.336.8.3Collection, storage and transfer of accounting data.346.8.4Cost association.356.8.5Billing.356.9Fault or maintenance management.356.9.1Management goals.356.9.2Alarm status monitoring.366.9.3Alarm collection and logging.376.9.4Alarm system parameter handling.386.9.5Alarm history handling.386.9.6Diagnostics and test handling.386.9.7Handling of equipment status.396.9.8Recovery.397Information flows for standardized CNM-LNM services.407.1Introduction.407.2Assumptions and notes.407.2.1Assumptions.407.2.2Notes.407.3Information flows.407.3.1Subscriber basic data management - temporary actions.407.3.1.1Temporary withdrawal of registration permission.417.3.1.2Restoration of registration permission (after temporarywithdrawal).417.3.2Subscriber diagnostics.417.3.2.1Subscriber activity history.417.3.2.2Current status of a subscriber.427.3.2.3Initiate trace of future subscriber activities.427.3.3Performance measurement data transfer.427.3.3.1Performance data transfer in standard format from theLNM to the CNM.437.3.4Access to network management facilities from the centre.437.3.4.1Security procedures (authentication and .authorization).437.3.5Fault and maintenance management.437.3.5.1Alarm trigger corresponding to serious equipment failure.437.3.5.2Alarm trigger corresponding to serious security breach,e.g. burglary.447.3.5.3Alarm trigger corresponding to serious traffic alarm.447.3.6Accounting management.457.3.6.1Transfer of accounting data.458Network management protocols.458.1Introduction.458.2Concepts.458.2.1Structure of Management Information (SMI).458.2.2Managed objects.458.2.3Data representation.45PSIST ETR 292:2000



Page 5ETR 292: July 19978.2.4Polling vs. event based management.468.2.5Telecommunications Network Management (TNM).468.3Candidate protocols.468.3.1SNMP.468.3.2CMIP.478.3.3CMOT (CMIP over TCP/IP).498.3.4CMOL (CMIP over Link Layer).498.4Summary.498.5Recommendation.499Standardization strategy for network management.50Annex A:Additional issues of standardization, implementation, messages, databases and agentspecification.54Annex B:Call end reasons.56History.57PSIST ETR 292:2000



Page 6ETR 292: July 1997Blank pagePSIST ETR 292:2000



Page 7ETR 292: July 1997ForewordThis ETSI Technical Report (ETR) has been produced by the Terrestrial Trunked Radio (TETRA) Projectof the European Telecommunications Standards Institute (ETSI).ETRs are informative documents resulting from ETSI studies which are not appropriate for EuropeanTelecommunication Standard (ETS) or Interim European Telecommunication Standard (I-ETS) status. AnETR may be used to publish material which is either of an informative nature, relating to the use or theapplication of ETSs or I-ETSs, or which is immature and not yet suitable for formal adoption as an ETS oran I-ETS.PSIST ETR 292:2000



Page 8ETR 292: July 1997Blank pagePSIST ETR 292:2000



Page 9ETR 292: July 19971ScopeThis ETSI Technical Report (ETR) provides an overview of the network management requirements in aTerrestrial Trunked Radio (TETRA) Voice plus Data (V+D) mobile radio system. The primary motivation ofthis ETR is to provide a starting point to facilitate central network management of TETRA systems fromdifferent manufacturers. After an overview of network management in TETRA, this ETR outlines theapproach to the work, followed by the specification of the management services and information flows.Finally a standardization strategy for network management for TETRA is given.The guiding principle in the examination of central Telecommunications Management Network (TMN)management services has been that the Central Network Management (CNM) facility will generally fulfil amonitoring role rather than a controlling role, although performing some limited controlling functions suchas temporarily disabling and enabling individual subscribers.With this constraint, an examination of the necessary central network management functions indicatesthat only a subset need to be standardized in order to support a high degree of inter-operability betweendifferent manufacturers' TMN management services. It appears that the following network managementfunctionalities require access from the CNM facility (or, in the case of items d) and (g), requirestandardization in support of that access):a)management of subscribers (for temporary actions only);b)subscriber activity log and subscriber diagnostics;c)access to system performance measurement data;d)access to network management facilities;e)fault and maintenance data;f)testing and recovery of network support links, in particular the Local to Central NetworkManagement link (LNM-CNM link);g)accounting management.It is clear that remote access to the LNM facilities from the centre will need to be supported by appropriateauthentication and authorization procedures optionally including encryption over the LNM-CNM link.In this ETR all of the local and central telecommunications management functions are examined andthose that require to be standardized to allow remote CNM operation, as defined above, are identified.The local/central/local network management information flows required to support the CNM functions arestudied and recommendations are made for defining TMN standard protocols and procedures.2ReferencesThis ETR incorporates by dated and undated reference, provisions from other publications. Thesereferences are cited at the appropriate places in the text and the publications are listed hereafter. Fordated references, subsequent amendments to or revisions of any of these publications apply to this ETRonly when incorporated in it by amendment or revision. For undated references the latest edition of thepublication referred to applies.[1]ITU-T Recommendation M.3020: "TMN Interface specification methodology".[2]ITU-T Recommendation M.3200: "TMN management services: Overview".[3]ITU-T Recommendation M.3400: "TMN management functions".PSIST ETR 292:2000



Page 10ETR 292: July 19973Definitions and abbreviations3.1DefinitionsFor 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 base station transmits and receives radio signals to and from a single location area (a single regionof geographical coverage). A BS contains at least one Base Radio Stack (BRS).cell: The smallest geographical area where TETRA services may be obtained, using a certain set of radiofrequencies.Cipher Key (CK): A value that is used to determine the transformation of plain text to cipher text in acryptographic algorithm.cipher text: The data produced through the use of encipherment. The semantic content of the resultingdata is not available (ISO 7498-2).decipherment: The reversal of a corresponding reversible encipherment (ISO 7498-2).encipherment/encryption: The cryptographic transformation of data to produce cipher text.(ISO 7498-2).entity: A point at which a packet is manipulated (e.g. sourced, sunk, routed or switched).gateway: A device which will enable the interconnecting of two networks which inherently use differentand incompatible protocols.historical data: Record of a past event or series of events. Historical data from triggered events may startat some point in the past up to the present.home location register: A database in the Mobile Station (MS) home system which keeps track of theposition of the MS. The home location register is used to indicate where the MS should be paged.key: A sequence of symbols that controls the operations of encipherment and decipherment.key management: The generation, selection, storage, distribution, deletion, archiving and application ofkeys in accordance with a security policy.network: A collection of subscriber terminals interconnected through telecommunications devices.plain text: The unencrypted source data. The semantic content is available.real time: Refers to the generation of network management information in a timeframe comparative to thereal life process that it is controlling or monitoring.signalling: The exchange of Information specifically concerned with the establishment and control ofconnections, and with management, in a telecommunication network.site: Physical location within the network.subscriber activity log: A system record which contains information on attach/detach ITSI;enable/disable terminal; registrations; location updates vs. time; call re-establishment; authentications; callstart time, call end time, and called party; type of call; Supplementary Services invoked; whether uplinkBER or MER are below an operator pre-determined threshold; plus any other relevant activity record.subscriber data: A system record which contains information on the individual subscriber ITSI, GTSIs,Supplementary Services allowed, privileges allowed and other system accesses allowed.subscriber management: The system functionality for dealing with subscribers to the system.PSIST ETR 292:2000



Page 11ETR 292: July 1997subscriber 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.Supplementary Service: A Supplementary Service modifies or supplements a bearer service or ateleservice. A Supplementary Service cannot be offered to a customer as a stand alone service. It shouldbe offered in combination with a bearer service or a teleservice.Switching and Management Infrastructure (SwMI): All of the TETRA equipment for a Voice plus Data(V+D) network except for subscriber terminals. The SwMI enables subscriber terminals to communicatewith each other via the SwMI.transaction (packet transaction): All the processes and procedures associated with the transmission ofone packet of information between peer network layer protocol entities on opposite sides of the airinterface.transaction (voice transaction): Part of a voice call comprising the transmissions of each talking party.The total of all transactions make up the call.transferred account procedure: Name given to the central accounting procedure defined in the GSMstandards. The transferred account procedure is used to allocate costs to roamed mobiles.3.2AbbreviationsFor the purposes of this ETR, the following abbreviations apply:ACLAccess Control ListACSEAssociated Control Service ElementASNAbstract Syntax NotationBERBit Error RateBICBarring Incoming CallsBOCBarring Outgoing CallsBRSBase Radio StackBSBase StationCKCipher KeyCMIPCommon Management Information ProtocolCMISCommon Management Information ServiceCMOTCMIP Over TCP/IPCNMCentral Network ManagementCSControl SupervisorCUGClosed User GroupDESData Encryption SystemDGNADynamic Group Number AssignmentEFDEvent Forwarding DiscriminatorGDMOGuidelines for the Definition of Managed ObjectsGOSGrade OF ServiceGSMGlobal System for Mobile communicationsGTSIGroup TETRA Subscriber IdentityHLRHome Location RegisterI5Interface between central and local network management systemsISDNIntegrated Services Digital NetworkISIInter System InterfaceITSIIndividual TETRA Subscriber IdentityITUInternational Telecommunication UnionLALocation AreaLNMLocal Network ManagementLSLine StationMERMessage Erasure RateMFAManagement Functional AreasMIBManagement Information BaseMSMobile StationNMCNetwork Management ControllerNMSNetwork Management SystemOSIOpen Systems InterconnectionPSIST ETR 292:2000



Page 12ETR 292: July 1997PDNPublic Data NetworkPDUProtocol Data UnitPSTNPublic Switched Telephone NetworkPTNPrivate Telephone NetworkRFCRequest For CommentsROSRemote Operations ServiceROSERemote Operation Service ElementRSSIReceived Signal Strength InformationSDHSynchronous Digital HierarchySMSubscriber ManagementSMIStructure of Management InformationSNMPSimple Network Management ProtocolSSSupplementary ServiceSwMISwitching and Management InfrastructureTAPTransferred Account ProcedureTCP/IPTransmission Control Protocol/Internet ProtocolTEITETRA Equipment IdentityTETRATErrestrial Trunked RAdioTIBTask Information BaseTMNTelecommunications Management NetworkTNMTelecommunications Network ManagementUDPUser Datagram Protocol (TCP/IP-DoD)V+DVoice plus Data4Objectives and approach4.1ObjectivesThe purpose of this ETR is to examine the following:a)the network management services that need to be standardized to achieve the required level ofcentral management; andb)the level to which the inter-system network management functions should be standardized.4.2Approach adoptedThe issues of Inter-System Interface (ISI) functions (supporting normal operation of the network to provideservice to subscribers), subscriber management and network management have been separated. Anaccepted framework for the standardization process is the ITU TMN methodology, ITU-TRecommendation M.3020 [1].The first task was to identify the services required, rather than the functions (services are implemented byfunctions). Service descriptions have to identify who benefits from the service, e.g. network manager,dispatcher or subscriber. It was decided to define all network management services (local and central)and then extract the central ones needed to support interworking between management systems.Once the services have been defined the aims stated in subclauses 4.1 a) and b) can be addressed.4.3Problems with the definition of management services using ITU methodologyA Telecommunication Management Network (TMN) is intended to support a wide variety of managementfunctions which cover planning, operations, administration, maintenance and provisioning oftelecommunication networks and services, ITU-T Recommendation M.3400 [3], paragraph 1.2.A TMN management service is seen as an area of management activity which provides for support of anaspect of Operations, Administration and Maintenance (OAM) of the network being managed, describedfrom the user perception of the OAM requirements, ITU-T Recommendation M.3200 [2], paragraph 1.It was found that using the ITU methodology led to much overlap between categories of service definition,with duplication between the heading of the management service and the Management Functional Areas(MFAs) e.g. performance, fault, configuration etc.). The amount of detailed categorization required did notgive a clear picture to guide network management development in TETRA, where the current objectivePSIST ETR 292:2000



Page 13ETR 292: July 1997was to standardize a limited degree of interworking between network management systems of differentTETRA systems at an early date.4.4Simplified methodologyBecause of the problems associated with use of the full ITU methodology, a simpler, alternative approachwas employed, using parts of the ITU methodology to provide a clearer way to identify the standardizationtask. This alternative approach is detailed in clause 6.PSIST ETR 292:2000



Page 14ETR 292: July 19975Overview of network management in TETRA5.1TMN reference system architectureThe primary reason for addressing network mManagement is to facilitate central management ofinterworking between TETRA systems from different manufacturers (figure 1).NODELNMLNMLNMCNMTETRA1TETRA 2TETRA 3ISIISIISII5I5I5NOTE:This schematic diagram does not imply any specific architectural implementation within theindividual TETRA networks.Figure 1: Network management reference modelThe reference system architecture assumes:-a number (say up to 25) of individual TETRA systems which may be procured from more than onesupplier;-each TETRA system has its own Local Network Management (LNM) and Subscriber Management(SM) facility which handles all aspects local to the system itself;-there is also a Central Network Management (CNM) facility which monitors or controls certainfunctions within and between the individual systems. Each system has a link to the CNM facility.5.2Role of playersThe CNM system manager manages the CNM on a day-to-day basis.The LNM system manager manages each TETRA system on a day-to-day basis, reconfiguring itdynamically as required. He manages subscribers and arranges maintenance when required. It isenvisaged that each LNM system manager will have authority only to operate within their own system.The Control Supervisor (CS) oversees several dispatchers in a single TETRA system and may carry outcertain functions of the LNM system manager.The dispatcher uses the facilities of the TETRA system to communicate with his organization's staff.The individual subscriber uses the TETRA system to communicate with other subscribers or hisdispatcher.PSIST ETR 292:2000



Page 15ETR 292: July 19975.3Non-standardized aspectsCertain aspects of network management in TETRA will only be performed at a local level and therefore donot need to be standardized. The following non-exhaustive list gives examples:-performance management:-measurement data collection;-tracing data collection;-fault or maintenance management:-alarm status monitoring;-alarm collection and logging;-alarm history handling;-diagnostics and test handling;-recovery;-equipment state handling;-configuration management:-time management;-software management;-radio network management;-routing management;-subscriber management:-subscriber basic data management;-basic service
...