1、 STD-ITU-T RECMN Q.75-ENGL 1997 m q8b257L 0b1i0728 4T5 INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STAN DARD I ZATI O N SECTOR OF ITU Q.750 (06/97) SERIES Q: SWITCHING AND SIGNALLING Specifications of Signalling System No. 7 - Signalling System No. 7 management Overview of Signalli
2、ng System No. 7 management ITU-T Recommendation Q.750 (Previously CCIlT Recommendation) STD-ITU-T RECMN Q.750-ENGL I777 4Bb257I Ob110729 331 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Signa
3、lling for circuit multiplication equipment FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM RI SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORK
4、ING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS General Message transfer part (MTP) Signalling connection control patt (SCCP) Telephone user part (TUP) ISDN supplementav services (2.14.3 Q.4-Q.59 Q. 50-Q. 59 Q .6O-Q. 99 Q. 1OO-Q.1 I9 Q
5、.12O-Q.249 Q.250-Q.309 Q.310-Q.399 Q.400-Q.499 Q. 50O-Q.599 Q.600-Q.699 Q.700-Q.849 Q.700 Q.701 -Q.709 (2.71 14.719 Q.720-Q.729 Q.730-Q.739 Data user part Q.740-Q.749 Transaction capabilities application patt Test specification Q3 interface DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBI
6、LE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN Q.770-Q.779 Q. 780-Q. 799 Q. 800-Q. 849 Q. 850-Q. 999 Q. 1 1 O-Q. 1 199 Q.1200-Q.1999 Q. 1000-Q. 1 O99 Q.2000-Q.2999 11 For further details, please refer to TUT List of Recommendations. ITU-T RECOMMENDATION 4.75
7、0 OVERVIEW OF SIGNALLING SYSTEM No. 7 MANAGEMENT Summary This Recommendation provides an overview of the functions, procedures and entities for managing the Signalling System No. 7 (SS No. 7) network. The requirements upon SS No. 7 management are summarized, namely: a) b) cl to provide a Telecommuni
8、cation Management Network (TMN) interface to the network operator; to intenvork with other TMN parts (e.g. Synchronous Digital Hierarchy (SDH) to enable the provision of a unified approach to managing the whole telecommunications network; and to extend where necessary the internal management functio
9、ns of SS No. 7, so as to amalgamate them with TMN. OMAP should also provide consistency between the SS No. 7 levels (layers) and across the SS No. 7 network. The abstract model of SS No. 7 management is defined, and its relationship with the SS No. 7 levels is explained. The management functions add
10、itional to those of OS1 (e.g. functions for auditing routing, functions for testing implementations of levels of SS No. 7 from an in-service node, etc.) are explained. Compatibility is considered, and an overview of the OMAP Recommendations is given. Source ITU-T Recommendation 4.750 was revised by
11、ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 5th of June 1997. - STD*ITU-T RECMN Q.750-ENGL 1997 9 LiBb259L Ob110731 T9T D FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunica
12、tions. The IT Telecommunication Standardization Sector (IT-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommu
13、nication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the IT-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC
14、 Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication admin
15、istration and a recognized operating agency. INTELLECTAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or
16、applicability of claimed Intellectual Property Rights, whether asserted by IT members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU hadhad not received notice of intellectual property, protected by patents, which may be requir
17、ed to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1997 All rights reserved. No part of this publication may be reproduced or utilized in any form or by
18、 any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the IT. *. 11 Recommendation 4.750 (06197) STD-ITU-T RECMN Q.750-ENGL I777 m 48b259L Ob40732 92b W 1 2 2.1 2.2 3 3.1 3.2 3.3 3.4 4 5 6 6.1 6.2 6.3 6.4 CONTENTS Introduction Requirements for
19、 SS No . 7 management . OMAP layers of management functions Fault management for OMAP . 2.2.2 Configuration management . OMAP management categories 2.2.1 2.2.3 Performance management . Reference model for SS No . 7 management . OW functional reference model . 3.1.1 Network management . 3.1.2 Network
20、 element management 3.1.3 Network element functions . 3.1.4 Relationship between network management and network element management Physical realization for SS No . 7 management OW and the OS1 management model OS1 states, resource states, mapping and constraints 3.3.2 Managed object model SS No . 7 m
21、anaged objects and SS No . 7 structure . Communication profiles for management interfaces Methodology . Backwards compatibility Blue Book Recommendation 4.79 1 and the present OMAP . SS No . 7 networks without TMN . Existing SS No . 7 networks and their evolution to using TMN . 6.3.1 Q-Adaptation fu
22、nction . 6.3.2 Limitations upon the output to the TMN-OS Compatibility within OMAP communication protocols 3.3.1 Annex A . OMAP Recommendations which apply to the TMN and SS No . 7 interfaces . Annex B . Recommendation for narrow-band SS No . 7 managed objects . Annex C . Management ofthe SS No . 7
23、part of broadband networks Recommendation 4.750 (06197) Page 1 2 2 3 3 4 5 6 6 7 7 7 7 8 10 10 10 13 16 17 18 18 18 18 18 18 19 19 20 20 . 111 - STD-ITU-T RECMN Q-750-ENGL 1797 D iBb2591 0b40733 Bb2 Recommendation 4.750 OVERVIEW OF SIGNALLING SYSTEM No. 7 MANAGEMENT (revised in 1997) 1 Introduction
24、This series of Recommendations on the Operations, Maintenance and Administration Part (OMAP) define the functions, procedures and entities for managing the Signalling System No. 7 network. The management functions of SS No. 7 are divided into three main parts, viz: a) Management functions located in
25、 the Telecommunications Management Network (TMN) (which means the Network Element Functions (NEFS) and the Operations System Functions (OSF) - see Recommendation M.3010 i). These functions include measurement collection and cover TMN-to-TMN interactions; such management functions are modelled as man
26、aged objects at the interface between network elements and operations systems, or between operations systems. Management functions within the SS No. 7 protocol itself (e.g. changeover, forced rerouting, sub-system management, etc.). Management functions defined to enable verification and validation
27、of routing tables, CICs, etc. These functions may require communication within the signalling network, and for this a separate protocol is defined. Such management functions are modelled as managed objects at the interface between the network elements and an operations system. Of the three sets of m
28、anagement functions defined above, OMAP provides a) and c). Set b) can be modelled as existing within the “Layer Management Entities” of SS No. 7, and the functions are defined in the Recommendations pertinent to those layers. OMAP interacts with all the layers (Le. with all the levels) of SS No. 7
29、in order to effect control of the network. Recommendation 4.750 gives the OMAP overview; the 4.75 1-Series of Recommendations define the SS No. 7 managed objects; Recommendation 4.752 (the successor to Blue Book Recommendation 4.791) defines the SS No. 7 monitoring and measurements; Recommendation 4
30、,753 defines the SS No. 7 management functions for managed objects that themselves require SSNo. 7 communication in the network, and also the OMASE-User where the logic of these functions is modelled (these functions are MRVT, SRVT and CVT, formerly defined in Blue Book Recommendation Q.795); Recomm
31、endation 4.754 defines the ASE for those functions defined in Recommendation 4.753, i.e. OMASE; Recommendation 4.755 defines the SS No. 7 Testers. Figure A.l shows the relationship between TMN, SS No. 7 management and the OMAP Recommendations. OMAP uses principles of management defined in TMN Recomm
32、endation M.3010 i, and in OS1 Management Recommendations of the X.700-Series 2. b) c) Recommendation Q.750 (06/97) - STD.ITU-T RECMN Q=i5U-ENGL 1997 m 14b2591 b40734 7T 2 There are three main requirements for the management of SS No. 7 and its network. These may be summarized as: a) Requirements for
33、 SS No. 7 management To provide a TMN interface for the network Administrationl. - This requires that the Administration-to-OW interface has to be presented using TMN-defined concepts. See the Q.75 1 -Series of Recommendations. To intenvork with other TMN parts to enable the provision of a unified a
34、pproach to managing the whole telecommunications network. Examples of these other parts are the Synchronous Digital Hierarchy (SDH) or the ISDN, which could be administered by the same body responsible for the MTP network - or TMNs of other jurisdictions (e.g. where an SCCP network covers more than
35、one MTP network, one jurisdiction might exist for each MTP network). - This means that the OMAP managed objects (see the Q.751-Series of Recommendations) must be compatible with, and have appropriate attributes defined for interacting with, other TIvNs managed objects. To extend, where necessary, th
36、e management of the SS No. 7 network as described in functional SS No. 7 Recommendations (e.g. Recommendations 4.703 and Q.704 3 for the MTP, 4.714 4 for the SCCP), and to amalgamate this with the TMN approach. - Hence OMAP should provide for the complete management of the SS No. 7 network, it shoul
37、d provide consistency in approach between the different layers of SS No. 7, and it should provide consistency across the SS No. 7 network and its network elements. - OMAP should therefore be used to Co-ordinate across the SS No. 7 network the parameters for User Part, MTP and SCCP congestion control
38、. This should allow these parameters to take values appropriate for the traffic mix and signalling and traffic volumes at each signalling point (e.g. timers Ta and Tb and the number of restiction levels, etc., for SCCP congestion control might need to be adjusted for the particular signalling point,
39、 but this should be consistent for the role of the SP in the SCCP network). - SS No. 7 already has defined certain management functions in its functional Recommendations (e.g . MTP signalling network management as defined in Recommendation 4.704 3, and SCCP management as defined in Recommendation 4.
40、714 4). These functions provide some automatic fault, configuration and performance management activities. OMAP has taken these functions into account in the definition of the behaviour of SS No. 7 managed objects. OW also extends the functionality already defined in, for example, the MTP Recommenda
41、tions into a complete management service for the whole SS No. 7 network. b) c) 2.1 The layers“ of management functions define the partitioning of management processes on a hierarchical basis. The definition of TMN is concerned with five layers in management, namely business management, service manag
42、ement, network management, network element management, and the elements in the network that are managed. OMAP layers of management functions 1 Here the word “Administration“ in the term “network Administration“ refers to the body or bodies (either telecommunication administration or ROA) responsible
43、 for controlling the SS No. 7 network. 2 Recommendation 4.750 (06197) Of these, OMAP currently is not concerned with business management, and interacts with other TMN parts to provide service management. For example, this latter interaction occurs if ISDN services require to be added so that subscri
44、bers at one exchange can use these services to subscribers at another exchange. If the Telephony User Part only is installed at those exchanges, it needs to be replaced or extended by the ISDN User Part, with corresponding addressing enhancements to the MTP implementation at those exchanges. The OMA
45、P implementation would be involved in these changes. The top management level proper of OW is network management, which provides the functions and resources to allow Administrations (possibly via a set of administration managed objects) to control the SS No. 7 network. Management functions and resou
46、rces are provided by OMAP to allow management within the SS No. 7 signalling points. See clause 3 for further information on the OMAP reference model. The definitions of both network management and network element management functions and resources utilize the TMN and OS1 managed object approach, an
47、d allow changes to be coordinated within OMAP. Certain managed objects (e.g. signalling linkset and linkSetNePart) have relations defined between them to allow network actions to be correlated with actions in concerned signalling points. Relations are also defined between managed objects to allow “m
48、anagement hierarchies“ to be satisfied (e.g. to forbid removal of a signalling linkset without first removing all its constituent signalling links). 2.2 OMAP management categories The purpose of management is to provide a service, and this can be classified as initial provisioning, maintaining exist
49、ing service, and expansion or contraction of the service. Management activities can be divided into categories which satisfy one or more of the above classifications. OS1 defines the categories of fault management, configuration management, performance management, accounting management and security management. Of these, the first three categories are applicable to OW; the last two are for further study in OMAP. 2.2.1 Fault management for OMAP OMAP fault management encompasses fault detection, location, isolation and the correction of abnormal opera
