ECMA TR 67-1994 Compendium of PTN Management Services《PTN管理服务概述》.pdf

《ECMA TR 67-1994 Compendium of PTN Management Services《PTN管理服务概述》.pdf》由会员分享，可在线阅读，更多相关《ECMA TR 67-1994 Compendium of PTN Management Services《PTN管理服务概述》.pdf（64页珍藏版）》请在麦多课文档分享上搜索。

1、ECMA Technical Report TR/67December 1994Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - ECMANEWS: +41 22 735.33.29 - Internet: HelpdeskECMA.CHCompendium of PTNManagement Services.ECMA Technical Report TR/67December 1994Standardizing Information an

2、d Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - ECMANEWS: +41 22 735.33.29 - Internet: HelpdeskECMA.CHPC-5 - TR-067.DOC - 10.02.99 11:31Compendium of PTNManagement Services.Brief HistoryECMA Technical Report TR/54 on the PTN Management Framework specifies a methodology by wh

3、ich work towardsstandardized management interfaces may proceed. As the initial steps in this methodology it is necessary to investigate theservices which the users management applications will be expected to support and the functions necessary to support theseservices. The results of this investigat

4、ion will guide the detailed work on the interfaces identified in ECMA TR/54.The content of this Technical Report, ECMA TR/67, has been based upon a snapshot of the work of ETSI NA4.3 and ITU-TQ23/4 for the services description and for the functions to support these services (these services and funct

5、ions have beenadapted to suit the PTN environment). The services are not to be standardized and the compendium provided in this TechnicalReport does not attempt to be exhaustive in its coverage. Instead it explores sufficient material to assist further standardizationwork.This Technical Report has b

6、een produced under ETSI IMCC work item DTR/ECMA-00105, with the intention of submissionto ETSI for publication as an ETR.NOTECCITT underwent a name change during the development of this Technical Report. As a consequence of this, CCITT is nowreferred to as ITU-T except where a Recommendation being r

7、eferenced was produced under the CCITT name. The names ofStudy Groups also changed from Roman to Arabic numerals, and the Working Party number now comes before the StudyGroup number when referring to a specific Working Party, e.g. WP IV/3 now becomes WP3/4.This ECMA Technical Report has been adopted

8、 by the ECMA General Assembly of December 1994.- i -Table of contentsPage1 Scope 12 References 12.1 ECMA references 12.2 ITU-T references 12.3 ETSI references 12.4 CENELEC references 23 Definitions 23.1 Imported definitions 23.2 Document-specific definitions 23.2.1 Business Management level 23.2.2 E

9、lement Management level 23.2.3 Entity 23.2.4 Network Management level 23.2.5 (PTN) Management Service 23.2.6 PTN Management 23.2.7 Service Management level 24 Acronyms and abbreviations 35 Introduction 36 General 47 Approach to Management Services 48 Task 1 - Describe MANAGEMENT SERVICES for PTN Man

10、agement 58.1 PTN Management Services 58.1.1 Name of Service: User aspects administration 58.1.2 Name of Service: Routeing administration 68.1.3 Name of Service: Traffic measurement and analysis administration 68.1.4 Name of Service: Tariff and charging administration 68.1.5 Name of Service: Manageme

11、nt of the security of PTN Management 68.1.6 Name of Service: Traffic management 78.1.7 Name of Service: Management of PTN User Access 78.1.8 Name of Service: Management of Transport Networks 88.1.9 Name of Service: Switching management 88.1.10 Name of Service: System installation administration 98.1

12、.11 Name of Service: QoS and Network Performance administration 9- ii -8.1.12 Name of Service: PTN User Access to PTN Management 98.1.13 Name of Service: Restoration and Recovery 108.1.14 Name of Service: Management of PTN Network Services 108.1.15 Name of Service: Management of Network Scenarios 10

13、8.1.16 Name of Service: Management of Dialling/Numbering Plans 118.1.17 Name of Service: Management of the PTN Management network 128.1.18 Name of Service: PTN Signalling Management 128.1.19 Name of Service: Supervisory Management Service 128.1.20 Name of Service: Management of Mobility 138.1.21 Nam

14、e of Service: Configuration of PTN Supplementary Services 138.1.22 Name of Service: Management of Computer Supported Telecommunication Services (CSTA) 138.2 Common Management Service Components 149 List of management FUNCTIONAL GROUPINGS 159.1 General 159.2 Generic Data Reports 169.3 Performance man

15、agement 179.3.1 Performance monitoring (PM) 179.3.2 Traffic Measurement (TM) 179.3.3 Status Monitoring Functions 189.3.4 Control Functions 189.3.5 Quality of service (QoS) observations 189.4 Fault (or maintenance) management 189.4.1 Alarm Surveillance 189.4.2 Fault Location 199.4.3 Trouble ticket ma

16、nagement 209.5 Configuration management 209.5.1 Provisioning209.5.2 Status and control 219.5.3 Installation 229.6 Accounting management 229.6.1 Billing functions 229.7 Security management 239.8 PTN Functions required additional to those in M.3400 2310 Bibliography 24Annex A - Management Services Tem

17、plate 25Annex B - Orchestration issues 27Annex C - Relationship to Management Services from ITU-T and ETSI 29Annex D - Dependencies between PTN Management Services 33- iii -Annex E - Management Service for the Management of PTN Network Services 35Annex F - Management Service for PTN User Access to N

18、etwork Management 39Annex G - Management Service for Management of Network Scenarios 47Annex H - PTN Management Service on Metronome Synchronization 49- iv -.1ScopeThis Technical Report identifies a set of PTN Management Services representative of PTN networks. This list is notmeant to be exhaustive

19、 nor constricting and, as such, will not be subject to standardization, at least not at this stage.Services identified in this Technical Report may not be complete or necessarily offered in a particular implementation.However, they will provide a check-list to guide the standardization process, ensu

20、ring that it supplies all thefunctionality that is necessary to support the perceived usage of a management implementation.Each PTN Management Service is briefly described in terms of its activity and identifiable separate component parts.From these the groupings of functions supporting these compon

21、ents are identified.The range of PTN Management Services, the activity description and the components for each are not to bestandardized. The function groupings will only be standardized in so far as they impact interfaces.2 References2.1 ECMA referencesECMA-105 Private Telecommunication Networks -

22、Signalling at the S Reference Point - DataLink Layer Protocol (SSIG-L2) (1993)ECMA-106 Private Telecommunication Networks - Signalling Protocol at the S Reference Point- Circuit Mode Basic Services (SSIG-BC) (1993)ECMA-133 Reference Configurations for Calls through Exchanges of PrivateTelecommunicat

23、ion Networks (1989)ECMA-141 Private Telecommunication Networks - Inter-Exchange Signalling - Data Link LayerProtocol (QSIG-L2) (1993)ECMA-143 Private Telecommunication Networks - Inter-Exchange Signalling Protocol - CircuitMode Basic Services (QSIG-BC) (1992)ECMA-155 Addressing in Private Telecommun

24、ication Networks (1991)ECMA-179 Services for Computer Supported Telecommunications Applications (CSTA)Phase I (1992)ECMA TR/52 Computer Supported Telecommunications Applications (CSTA) (1990)ECMA TR/54 A Management Framework for Private Telecommunication Networks (1990)ECMA TR/57 Private Telecommuni

25、cation Networks (1991)ECMA TR/65 PTNX Functions for the Utilization of Intervening Networks in the Provision ofOverlay Scenarios (Transparent Approach) - General Requirements (1994)ECMA/TC32/93/6 Guidelines for the Definition of PTN Managed Object Classes (1st draft, February1993)2.2 ITU-T reference

26、sRec. M.3010 Principles for a Telecommunications Management Network (COM IV-R 28)Rec. M.3200 TMN Management Services (Bath, March 1993)Rec. M.3201 TMN Management Service: Traffic Management (Bath, March 1993)Rec. M.3203 TMN Management Service: Management of customer controlled services (Bath,March 1

27、993)Rec. M.3400 TMN Management Functions (COM IV-R 28)2.3 ETSI referencesETS 300 189 Private Telecommunication Network (PTN); Addressing (December 1992)I-ETS 300 291 Network Aspects - Functional Specification of Customer Administration on theOS/NE interface (January 1995)- 2 -I-ETS 300 292 Network A

28、spects - Functional Specification of call routeing information managementon the OS/NE interface (January 1995)Draft TR NA43304 TMN Management Services (NA(91)30, September 1992)Draft TR NA43306 TMN Management Services: Prose Descriptions (NA(91)31, September 1992)Draft prETS 300 SIP(1) ISDN: Attenda

29、nt Supervisory Information Presentation (SIP) SupplementaryService: Service Description (ECMA/TC32-TG6/92/165, June 1992)2.4 CENELEC referencesENV 41007 Definition of terms in private telecommunication networks (1989)3 DefinitionsFor the purpose of this Technical Report the following definitions app

30、ly.3.1 Imported definitionsPTN (defined in ENV 41007)PTN Authority (defined in ECMA-155 and ETS 300 189)QSIG (defined in ECMA TR/65)For a general range of definitions see ENV 41007-1 and ETS 300 1893.2 Document-specific definitions3.2.1 Business Management levelA level (or layer) of the management h

31、ierarchy which has responsibility for the total enterprise and is the layer atwhich agreements between operators are made (described in annex B in ITU-T Rec. M.3010)3.2.2 Element Management levelA level (or layer) of the management hierarchy which manages each network element on an individual basis(

32、described in annex B in ITU-T Rec. M.3010). It covers: Control and coordination of a subset of network elements Maintaining statistical, log and other data about network elements3.2.3 EntityDefines parts of NEs, e.g. equipment, software, which are separately visible to management.3.2.4 Network Manag

33、ement levelA level (or layer) of the management hierarchy which has the responsibility for the management of all thenetwork elements, both individually and as a set. It is not concerned with how a particular element providesservices internally (described in annex B in ITU-T Rec. M.3010). It covers:

34、Control and coordination of the network view of all the network elements within its scope or domain The provision, cessation or modification of network capabilities for the support of service to customers3.2.5 (PTN) Management ServiceSimilar to the definition of TMN Management Service in CCITT Rec.

35、M.60 except that its scope is PTNManagement rather than the TMN. It is also referred to in ECMA TR/54 using the old term of PTN ManagementApplication Service.3.2.6 PTN ManagementImplicitly from ECMA TR/54 this is a TMN-like environment but with a scope restricted to PTNs.3.2.7 Service Management lev

36、elA level (or layer) of the management hierarchy which is concerned with, and responsible for, the contractualaspects of services that are being provided to PTN users or available to potential new PTN users (described inannex B in ITU-T Rec. M.3010). It covers:- 3 - PTN user/Public network point of

37、contact Interaction with service providers Interaction between services Maintaining statistical data (e.g. QoS)4 Acronyms and abbreviationsAI Artificial IntelligenceCPU Central Processing UnitCSIG Layer 3 SIGnalling system at the C reference point (see ECMA TR/65)IVN InterVening NetworkLAN Local Are

38、a NetworkMP Management ProcessMS Management ServiceNP Numbering PlanOMP Overall Management ProcessPM Performance MonitoringPNP Private Numbering PlanPTE Private Telecommunication EntityPTN Private Telecommunications NetworkPTNX Private Telecommunications Network eXchangeQSIG SIGnalling information f

39、lows at the Q-reference pointSIP Supervisory Information PresentationSS#7 Signalling System No. 7SSIG SIGnalling information flows at the S-reference pointTSIG SIGnalling information flows at the T-reference point5 IntroductionManagement Services are the users requirements for managing a telecommuni

40、cation network. As such it must be theaim of the management interfaces to support these requirements even if not all the services are provided by automatedequipment (e.g. the OMP or MP). The Management Services thus represent a marketing view.It is not envisioned that many new Management Services wi

41、ll be documented as they are currently enacted by humanoperators. These operators interact with the existing management systems so as to realise these Management Services.It must be an aim of standardization to allow for the continuing automation of these services so as to enhance theefficiency of t

42、he human operators.For consideration when identifying Management Services is that such services are relevant to specific areas in themanagement hierarchy, i.e. Business, Service, Network and Element Management. A human operator can interact witheach level in the hierarchy from a workstation and uses

43、 different Management Services from each level. This isdepicted in figure 1. For example, a maintenance engineer would want to interact at the Element Manager levelnormally and would need to see manageable objects in far more detail than would operators who are introducing newnetwork users.- 4 -Figu

44、re 1 - Workstation at different management levelsIn support of the above concept, a Management Service Template can be used to organise the categorization process.This is further described in annex A.Information is included in annex D about the interactions between the services, indicating overlaps,

45、 dependencies andinformation flows.6 GeneralManagement Services for PTNs have been defined based upon TMN Management Service work undertakenprincipally for public network equipment. This is because many management features/requirements are shared betweenpublic and private networks. The purpose of th

46、is compendium is to bring together in a single document an overview ofthe management services which are relevant to PTNs. Additional Management Services are defined which are requiredfor PTN Management where an equivalent TMN Management Service does not exist. Some of these additionalservices may al

47、so be adapted for use in public networks.The Functional Groupings have also been based upon work developed for TMN but have been simplified to separategeneric activities from the data involved. This has been done to ease the step to an object oriented specification whichis required for both PTN Mana

48、gement and TMN.Annexes have been provided to give more details of some of the additional Management Services, to show how TMNManagement services have been adapted and to give an overview of the major relationships between ManagementServices.7 Approach to Management ServicesEach Management Service th

49、at is listed represents a broad area of activity for PTN management. Each ManagementService is broken down into a set of Components of Service which represent the general activities that are required toenable the service to be offered.The management functions which are necessary to support each of these Components can be determined and newfunctions defined only if none suitable already exist. The functions are grouped for commonalty and rationalised thusavoiding potential duplications of effort.During the process of grouping and rationalisatio