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
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 data management;-Supplementary Service management;-subscriber location;-group management;-Closed User Group (CUG) management.-accounting management:-collecting and storing the accounting data (call logging);-billing;-security aspects:\-management of security of NMS;-security management (e.g. encryption key management).5.4Standardized aspectsThe standardized aspects of network management which are proposed in TETRA are high-level functionswhich are carried out at a central entity performing the management of several TETRA networks. Theproposed standardized network management functions are:-performance management:-performance data transfer in standard format from the LNM to the CNM;fault or maintenance management:-alarm trigger corresponding to serious equipment failure;-alarm trigger corresponding to serious security breach;-alarm trigger corresponding to serious traffic alarm;PSIST ETR 292:2000

Page 16ETR 292: July 1997-subscriber management:-temporary withdrawal of registration permission;-restoration of registration permission (after temporary withdrawal);-subscriber activity history;-current status of a Subscriber;-initiate trace of future Subscriber activities.-accounting management:-transfer of accounting data for users with wide roaming capability;-security aspects:-security procedures (authentication and authorization).6TMN MS description6.1Reference Telecommunications Management NetworkThe reference TMN architecture model is shown in figure 1.6.2Basis for Telecommunications Management Network functionalityNetwork management for TETRA involves all activities of controlling, indication and logging in terms ofusage and quality of service of TETRA networks with the aim of presentation of communication serviceswith a defined degree of quality level.MFAs are defined as:-subscriber management;-configuration management;-traffic measurement;-performance measurement;-security management;-charge (accounting) administration;-fault management.In reality some network management functions span several of these areas, for instance aspects of trafficmeasurement are used in configuration management, in performance measurement and in chargeadministration.Another example of this overlap in functionality is in network management of the inter-system link bearerswhich would be provided as part of the link bearer network and be outside the individual TETRA networkmanagement. However, as a safety measure for the integrity of the overall system, activity and trafficlevels on inter-system links should be monitored from the CNM facility. These are TETRA networkfunctions which need to be carried out in real time so that re-routing of inter-system links can be arranged(via the configuration management function) when necessary.By the very nature of network management many local and central network management operations aresimilar. Within the constraints of the particular implementation they may even be identical. Whilst everyeffort has been made in this document to capture all aspects of local and CNM, the emphasis has beenplaced on developing those network management functions, operations and information flows that need tobe standardized to allow support of a common CNM facility.PSIST ETR 292:2000

Page 17ETR 292: July 19976.3Subscriber management6.3.1Management goalsThe centre needs to be the focus of liaison with national sharers of the systems, and be able to informthem of localized problems in coverage/access/services etc.The subscriber management is intended to present tools for subscriber administration from the operatorspoint of view. These are activities for creating, updating and deleting subscriber oriented information. Adistinction is made between temporary and permanent actions using different authorizations for startingthese actions. Moreover, supervision of the data associated with the subscribers and the subscriberbehaviour has to be done. Management of equipment has to be performed as well.Some aspects of subscriber management may be achieved via normal Supplementary Services (SS), e.g.disabling of in coming or outgoing calls by the SS BIC or BOC, but some disabling functions may need tobe done by the local or CNM system managers.Interworking and migration of mobiles between different networks is achieved via the Inter-SystemInterface (ISI) and dynamic information to support this is exchanged on a call-by-call basis.Other non-real-time information can be exchanged off-line between service providers.6.3.2Subscriber basic data managementSubscriber management is carried out locally for most subscribers. Call-based information is transportedautomatically between systems over the ISI. Subscribers with wide roaming capability may need to bemanaged from the central facility (for operational reasons).Subscriber management needs a central network function which bars mobiles (e.g. stolen, spoofattempts) from accessing any of the systems. CNM needs ability to co-ordinate this action directly fromthe centre.The system managers (central and local) have to be able to distinguish between a non-paying subscriberand a stolen/faulty mobile. To support this capability it is envisaged that separate independent databasesbased on subscribers identities (ITSIs) and equipment identities (TEIs) will be required.6.3.2.1Permanent actions1)Creation of data for new subscribers. Includes all privileges, priorities and subscribed services.2)Disabling of subscriber.3)Updating of subscriber data in terms of subscriber and operator requirements (separate individualand group information).4)Deletion of subscriber data (due to a subscriber request or operator decision).Table 1UserLocationReal timeTriggerIntersystemmediumComments1)LNM system managerLocalNoOn demandNo2)LNM system managerLocalNoOn demandNo3)LNM system managerLocalNoOn demandNo4)LNM system managerLocalNoOn demandNoNOTE:SS DGNA performs similar functions to dynamically create permanent groups withdesignated privileges, priorities and subscriber services and to allocate individuals tothese groups.PSIST ETR 292:2000

Page 18ETR 292: July 19976.3.2.2Temporary actions1)Temporary withdrawal of registration permission.2)As 1.3)Restoration of registration permission (after temporary withdrawal).4)As 3.Table 2UserLocationReal timeTriggerIntersystemmediumComments1)LNM system managerLocalYesOn demand2)CNM system managerCentralCloseOn demandLNM-CNMTo be standardized3)LNM system managerLocalYesOn demand4)CNM system managerCentralCloseOn demandLNM-CNMTo be standardized6.3.2.3Protection of subscriber data1)Ensure the integrity and secrecy of subscriber data input by the LNM system manager.2)Examination of presently stored data in terms of consistency and plausibility.Table 3UserLocationReal timeTriggerIntersystemmediumComments1)LNM system managerLocalNoOn demandNo2)LNM system managerLocalNoOn demandNo6.3.2.4Subscriber activity log and subscriber diagnostics1)Retrieving historical subscriber activities by accessing subscriber activity log for a defined period.Subscriber activity log to contain information on attach/detach ITSI; enable/disable terminal;registrations; location updates vs. time; call re-establishment; authentications; service deliveryqueuing delay; call start time, call end time, called party; call end reason (see note), type of call;Supplementary Services invoked; whether uplink BER or MER are below an operatorpre-determined threshold; plus any other relevant activity record.2)As 1.3)Current status (attached/detached, in a call and if so identity of other parties, system identity whereattached, site identity, date, time, type of call, SS invoked).4)As 3.5)Initiate trace of future subscriber activities. Trace to trigger on specific events (such as callre-establishment signalling, uplink BER below threshold, etc.) identified by the invoker of service.6)As 5.NOTE: See annex B for summary of call end reasons.PSIST ETR 292:2000

Page 19ETR 292: July 1997Table 4UserLocationReal timeTriggerIntersystemmediumComments1)Dispatcher & LNMsystem managerLocalYesContinuousor triggerNone2)CNM systemmanagerCentralNoOn demandLNM-CNMTo be standardized3)Dispatcher andLNM systemmanagerLocalYesOn demandNone4)CNM systemmanagerCentralYesOn demandLNM-CNMTo be standardized5)Dispatcher andLNM systemmanagerLocalYesOn demandor triggerNone6)CNM systemmanagerCentralYesOn demandor triggerLNM-CNMTo be standardizedNOTE: Item 1: Access to the historical subscriber activities data has to be in real time butreal time data from the system is not necessary. It is an implementation issuewhether system information is stored and then archived after a suitable time, orwhether information is overwritten on a cyclic basis (such as every 24 hours).Item 2: Discrete information from the local historical log can be demanded by theCNM.Items 3 and 4: It is expected that subscriber current status information is availablein real time at the LNM facility. It may take finite time to relay this to the CNM facilitybut it is essentially close to real time.Items 5 and 6: The trace of future subscriber activities is intended to provide thebasis of:a)diagnostic data gathering for substantiating subscriber fault reports;b)surveillance of subscriber activities (e.g. tracking stolen mobile terminal).Initiation of trace is on demand. After the trace has been initiated, information will be gathered on specificevents or on all events after the trigger (as defined in the demand).6.3.2.5Equipment management1)Central administration of data files concerned with equipment identification.2)Local administration of equipment and programming of equipment characteristics.3)Administration of "black list" equipment (stolen or faulty).Table 5UserLocationReal timeTriggerIntersystemmediumComments1)CNM system managerCentralNoOn demandNone2)LNM system managerLocalNoOn demandNone3)CNM/LNM systemmanagerCentraland LocalNoOn demandNoneRegular update -not in real time6.3.3Supplementary service management6.3.3.1Permanent actions1)Creation, deletion and modification of data for Supplementary Services.2)De-activation and activation of Supplementary Services.PSIST ETR 292:2000

Page 20ETR 292: July 1997Table 6UserLocationReal timeTriggerIntersystemmediumComments1)LNM system managerLocalNoOn demandNone2)LNM system managerLocalNoOn demandNone6.3.3.2Temporary actions1)Temporary disabling of a Supplementary Service.2)Enabling of Supplementary Service after temporary disabling.Table 7UserLocationReal timeTriggerIntersystemmediumComments1)Dispatcher andLNM systemmanagerLocalYesOn demandNone2)Dispatcher andLNM systemmanagerLocalYesOn demandNone6.3.4Migration management (individuals and groups)Migration management is usually carried out locally (by inter-operator agreements) for individuals andgroups. However, groups which migrate across individual system boundaries may need a central networkinformation facility to support their operation.Interrogation of home database and visitor database actions in support of migrating mobiles is performedautonomously in real time by the system. Management of migration, which involves granting the authorityto migrate to the individual subscriber and informing the mobile's database which operator codes to preferwhen seeking service outside of the home system is performed off-line in non-real time.1)Grant migration privilege to individual or group. This information is stored in the SwMI.2)As 1.3)Inform mobile's database of preferred operator codes in visited systems.4)Remove migration privilege from individual or group. Information stored in SwMI.5)As 4.Table 8UserLocationReal timeTriggerIntersystemmediumComments1)LNM system managerLocalNoOn demandNone2)CNM system managerCentralNoOn demandNoneBy post?3)LNM system managerLocalNoOn demandNoneAt subscription?4)LNM system managerLocalNoOn demandNone5)CNM system managerCentralNoOn demandNoneBy post?PSIST ETR 292:2000

Page 21ETR 292: July 19976.4Configuration management6.4.1Management goalsSystem configuration management affects the functionality of the entire communications network.Consequently, it can only be performed by authorized personnel. Terminals dedicated to systemconfiguration management are to be protected by appropriate access checking (see securitymanagement). Management of system configuration should be performed without interruption to thecorresponding service. If system crashes are encountered after execution of system configurationmanagement it has to ensured that the system can be satisfactorily returned to its previous operationalstate whilst the problems are resolved. After each system change suitable tests have to be performed toexclude possible secondary effects.Two distinct aspects of configuration management can be identified:-a slow acting management function corresponding initial set up and steady state system control;-a fast acting management function corresponding to transitory fault control and also to deal withfluctuating traffic conditions. This latter aspect is sometimes called performance management sinceit deals with dynamic configuration management in order to optimize performance.It is often difficult to separate these aspects of configuration management, except in very specificcircumstances and usually concerning only a few network elements. Generally, the fluctuating trafficconditions will mainly affect the radio network part of the system.The following general steady-state (non-real time) features of configuration management may bedistinguished:a)Specification of operator requirements in terms of services supported: teleservices, bearer services,Supplementary Services, network services etc. These are usually static and configured when thenetwork is first set up.b)Identification of required network elements. This initially entails identification of the individualnetwork entities required to provide the required service and subsequently monitoring of thesenetwork elements to ensure correct operation.c)System parameters to be specified. Corresponds to interpretation of grade of service parametersfor the services in a) being mapped on to specific network elements identified in b).d)Upgrades of hardware components (e.g. network elements or sub-elements), software contained inthese components and overall system control software.e)Reconfiguration of existing network elements.f)Administration of system configuration.Configuration management for the line network and the radio network aspects of TETRA are dealt withseparately in the following subclause.The overall requirements for efficient network management are:-flexible system configuration; able to easily configure and reconfigure the system;-equal set of central commands for equivalent functions in different suppliers' systems;-automatic generation of lists of hardware of TETRA system e.g. BS, switches etc. Similarly lists ofsoftware versions for all administered network components.NOTE 1:If this were to be a central function it implies an agreed definition of generic networkobjects.PSIST ETR 292:2000

Page 22ETR
...