1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU INTELLIGENT NETWORK Q.1303 (1 0/95) TELECOMMUNICATION APPLICATIONS TASC MANAGEMENT: ARCHITECTURE, METHODOLOGY AND REQUIREMENTS FOR SWITCHES AND COMPUTERS (TASC) - ITU-T Recommendation (2.1303 (Previously “CCI
2、lT Recommendation”) ITU-T RECMN*Q.L303 95 4862593 Ob35867 988 FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (IT). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommen- da
3、tions on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics- for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
4、The approval of Recommendations by the Members of the IT-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). ITU-T Recommendation 4.1303 was prepared by IT-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th o
5、f October 1995. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITU 1996 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any
6、means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. ITU-T RECMN*Q.3303 95 = 4862593 0635868 834 m 1 2 3 4 5 6 7 8 9 10 11 CONTENTS Scope References Terms and definitions . Abbreviations . Method for defining TASC Management 5.1 Relations
7、hip of reference points to interfaces . 5.2 Ensemble definition and use . 5.2.1 Ensemble overview . 5.2.2 Management context . 5.2.3 Requirements 5.2.4 Scenarios . 5.2.5 Resources 5.2.6 Management functions 5.2.7 Information model 5.2.8 Conformance . Steps in defining TASC Management 6.1 Application
8、 uses for TASC Management . 6.2 Management Service descriptions 6.2.1 General services 6.2.2 Functional architecture . 7.1 Reference configuration 7.2 Reference points . Information mechanisms 8.1 Establishing the scope of an interface . 8.2 Representation of resources to be managed 8.3 Exchanging m
9、anagement information Model architecture 9.1 Consideration of established switching and computing modelling 9.1.1 Conversion procedures between GDMO and SNMP 9.2 Modelling mechanism . . 5.3 Requirements leading to TASC Management Management associated with TASC Functional Services . Overall TASC Man
10、agement Information Model . Physical scenarios Annex A . Interactions with existing management systems . A.2 PTN Management . A.3 Proprietary Appendix I - Bibliography A.l TMN . Recommendation Q.1303 (10/95) Page 1 1 2 2 2 2 2 2 3 3 3 4 4 4 4 4 4 4 5 5 8 10 10 10 12 13 13 13 14 14 14 15 15 15 16 16
11、17 18 18 1 SUMMARY This Recommendation identifies the architecture and requirements to support management of the TASC interface and is one in the Q.1300-Series Recommendations on TASC. The main purpose of TASC is to allow applications to be developed which integrate the services provided by both com
12、puting and telecommunication platforms. This would typically allow business applications to use TASC to integrate the computer workstation and telephone at the users desktop, This Recommendation does not attempt to define management of either the switch or computer involved at the TASC interface. IN
13、TRODUCTION In order for the TASC interface between a switch and computer “host” to operate efficiently and reliably, it is necessary to provide a management activity. Whilst management of each end of the interface could be carried out by proprietary means, this would generally require a high degree
14、of manual orchestration. The purpose of TASC Management is to describe a management interface between the switching and computing environment so as to assist in automating the management orchestration. An overview of TASC is given in Recommendation Q.1300 with the TASC Architecture and Functional Se
15、rvices being defined in Recommendations Q. 1301 and Q. 1302, respectively. Ail of these Recommendations are considered essential preparatory reading for TASC Management. In particular Recommendation Q. 1302 which describes the management requirements for each Functional Service in TASC. This Recomme
16、ndation uses many concepts esoteric to the management environment. It is suggested that the user of this Recommendation is familiar with management concepts. BACKGROUND This Recommendation was developed at the same time as the architecture and functional services were developed for TASC. Although so
17、me preliminary thoughts on management had been documented before in one of the regional standards bodies, this is the first document published on this topic. TASC Management must accommodate many different management mechanisms internal to the switch and computer. Many of these will be proprietary b
18、ut available documented srandards are considered. KEYWORDS Architecture, Management, Requirements, TASC. 11 Recommendation Q.1303 (10/95) ITU-T RECMN*Q*1303 95 4862571 Ob15870 472 Recommendation Q.1303 TELECOMMUNICATION APPLICATIONS FOR SWITCHES ARCHITECTURE, METHODOLOGY AND REQUIREMENTS AND COMPUTE
19、RS (TASC) - TASC MANAGEMENT: (Geneva, 1995) 1 Scope This Recommendation tackles the area of enabling the switching and computing aspects, which make up TASC, to be managed. To do this, it considers how to orchestrate the management functions in the switching and computing application support environ
20、ments. It does not consider how the management functions work in the switching and computing application support environments. This Recommendation only considers the management methodology and requirements for TASC. Protocol aspects and the details of what may be managed are outside the scope of thi
21、s Recommendation. The scope of TASC Management needs bounds as each implementation will have different management needs. Thus, TASC Management is bounded by the management activity needed to support the defined TASC Functional Services plus additional management activities identified as “generic” by
22、 considering a number of potential management scenarios. This Recommendation does not consider the following aspect for TASC Management: Charging. TASC Management does not seek to replicate access to resources which are available via TASC Functional Services except where an alternative mechanism is
23、required. 2 References The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to rev
24、ision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid -T Recommendations is regularly published. - CCITT Recommendation X.722 (1992) I
25、 ISO/EC 10165-4: 1992, Information technology - Open systems Interconnection - Structure of management information - Guidelines for the definition of managed objects. ITU-T Recommendation Q. 1300 (1993, Telecommunication Applications for switches and computers (TASC) - General overview. ITU-T Recomm
26、endation Q. 1301 ( 1995), Telecommunication Applications for switches and computers (TASC) - TASC architecture. - - - IT-T Recommendation Q. 1302 (1995), Telecommunication Applications for switches and computers (TASC) - TASCfunctional services. - - - CCITT Recommendation M.3020 ( 1992), TMN interfa
27、ce specification methodology. CCITT Recommendation 1.1 12 (1988), Vocabulary of tem for ISDNs. ISO/IEC DIS 1 1579- 1: 1994, Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Part 1: Reference configuration for PISN exchanges
28、(PINX). Recommendation Q.1303 (10/95) 1 ITU-T RECMN*Q-3303 95 4862591 Ob35873 309 3 Terms and definitions This Recommendation uses terms defined in Recommendation Q. 1300. 4 Abbreviations For the purposes of this Recommendation, the following abbreviations are used: ACSE CE E/R FS GDMO ID MIB NE NMF
29、 os os1 PTN SNMP TASC TMN Association Control Service Element Communication Entity (TASC object) - see Recommendation Q. 1301 Entity Relationship (diagram) Functional Service (TASC) - see Recommendation Q. 1302 Guidelines for the Definition of Managed Objects IDentifier - see Recommendation 4.1301 M
30、anagement Information Base Network Element Network Management Forum Operations System Open Systems Interconnection Private Telecommunication Network Simple Network Management Protocol Telecommunication Applications for Switches and Computers - see Recommendation Q. 1300 Telecommunication Management
31、Network 5 The development of TASC Management will take a top-down approach in that all management interactions will stem from requirements identified in this Recommendation. TASC Management will take an object oriented approach to representing the resources to be managed. This approach is in keeping
32、 with Systems Management being defined jointly by ISO/IEC JTC 1 and ITU-T; it is also used in the specification of the Telecommunication Management Network m” Method for defining TASC Management 5.1 A reference point is a “conceptual point at the conjunction of two non-overlapping functional groups”
33、 according to Recommendation I. 112. The ISO/IEC 11579-1 standard goes on to indicate that “in a specific functional arrangement, a reference point may, but need not, correspond to a physical interface between two units of equipment”. Relationship of reference points to interfaces 5.2 Ensemble defin
34、ition and use An Ensemble is a convenient mechanism to package up management into self-contained packages which are of general use in an implementation. The use of Ensembles (as described below) allows TASC Management to be developed progressively. Each phase will consist of one or more Ensembles wh
35、ich can be used individually as specified or combined together in an implementation. 5.2.1 Ensemble overview In short, an Ensemble is the total set of specifications needed to do something useful. Graphically an Ensemble could be pictured as in Figure 1 : 2 Recommendation Q.1303 (10195) ITU-T RECMN*
36、Q-L303 95 48b259L Management context Viewpoint (User, Provider, Element, Setvice, .) -Resources (Equipment, Software, Application, .) Functions (Alam, Configuration, Performance, .I Management tods (Standards, Managed Objects, Management Functions, Profiles, ) - Requirements - Scenarioc - Resources
37、- Entity relationship models - Information model - Management information definitions - Conformance statements Ti 1681694/d01 FIGURE UQ.1303 Ensemble phases compare with development phases Figure 1 illustrates the parts which go to make up an Ensemble. It can be compared with a typical definition cy
38、cle for a project shown in the grey area. The Ensemble encompasses all the parts necessary to do a specific job. It also contains all the background information which identifies the job the Ensemble was designed for. 5.2.2 Management context The “Management Context” describes why the Ensemble is req
39、uired. The description of the “Management Context” includes the definition of the resources to be managed, the management functions to be performed, the scope of the problem to be solved, and the management view or level of abstraction from which the problem is to be approached. The influence of the
40、 Management Context on the Ensemble is shown in Figure 1. 5.2.3 Requirements This should provide an outline description of the management problem that is being addressed by the Ensemble and identifies the boundaries of that problem. The solution that is proposed should also be briefly described and
41、its boundaries identified. 5.2.4 Scenarios Scenarios are used to show how the managed objects in the information model can be used to accomplish the functions specified for the Ensemble. Each may be depicted as a brief textual description plus message flow diagrams. Recommendation Q.1303 (10/95) 3 5
42、.2.5 Resources The resources or components of resources that are the subject of the management activity need to be defined for an Ensemble. This definition is limited to only those resources that are relevant to the Ensemble. The resources could be specified by textual descriptions or by reference t
43、o other documents which contain descriptions of the resources. 5.2.6 Management functions This defines the management functions that can be performed on the resources. These functions may be primitive functions defined for OS1 systems management (e.g. event management), higher level functions for ge
44、neral management (e.g. alarm surveillance), or other functions unique to the problem that the Ensemble addresses. 5.2.7 Information model The Information Model focuses on the representation of the real world under study using modelling techniques. It con-ns information about both the elements of the
45、 model and their inter-relationships. The elements are defined in management information definitions. The elements of management information are defined using object definition templates and their inter-relationships are graphically illustrated through the use of Entity Relationship (JYR) diagrams.
46、5.2.8 Conformance The scope of the conformance is limited to that which is required to implement the Ensemble. 5.3 Steps in defining TASC Management The procedure identified in the TMN Interface Specification Methodology, Recommendation M.3020, should be used when developing TASC Management. This is
47、 augmented by the explicit packaging using the Ensemble concept described previously. 6 Requirements leading to TASC Management Management functions within TASC will need to interwork with management functions for switching. As TMN is expected to define the architecture for managing some switch netw
48、orks, then TASC management functions will need to inter-operate in a manner compatible with TMN. This will involve the use of managed objects for communication and identification of the appropriate TMN interface. TASC management functions should also be capable of interworking with switching managem
49、ent systems that are not based upon TMN and to provide the capability to accommodate other network management systems such as the Simple Network Management Protocol (SNMP). With three different management functions involved, i.e.: 1) TASC management; 2) computer system management; and 3) switch system management; there is a need for TASC management to take a coordination role between computer and switch system management. This will ensure that the actions taken by either are harmonized and do not conflict or overlap. 6.1 Application uses for TASC Management
