1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000116.2000(R2015) Signalling System Number 7 (SS7) Operations, Maintenance, and Administration Park (OMAP) As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the indust
2、rys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities fo
3、llow a fast-track development lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North Am
4、erican Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission
5、(CITEL). For more information, visit . AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgme
6、nt of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a conc
7、erted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures
8、 not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Stand
9、ard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures
10、of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of
11、 Disclaimer and 2. extensions to the 1988 protocol to provide for new applications of the SS7 protocol. This is in accordance with current and projected ITU-T activity. A change bar on the right margin indicates a change from the 1996 issue of this American National Standard. These change bars are a
12、dvisory only, and reflect the editors views of which textual changes constitute significant technical changes. Because of the differences in style and content between this standard and the ITU-T Recommendations, it is not possible to indicate differences using margin marks. This standard contains th
13、e following seven chapters: T1.116.0, Overview of Signalling System Number 7 (SS7) Management (OMAP) T1.116.1, Network Element Management Information Model for the MTP (For Further Study) T1.116.2, Monitoring and Measurements for Signalling System Number 7 Networks T1.116.3, Signalling System Number
14、 7 (SS7) Management Functions MRVT, SRVT, CVT and Definition of the OMASE-User T1.116.4, Signalling System Number 7 (SS7) - OMAP Management ASE (OMASE) Definitions for Functions MRVT, SRVT and CVT T1.116.5, Signalling System Number 7 Protocol Testers (For Further Study) T1.116.6, Signalling System N
15、umber 7 Guide Book to OMAP This standard is intended for use in conjunction with T1.110-1999 Signalling System Number 7 (SS7) General Information, , which includes an overview of SS7, a glossary, and a chapter on abbreviations. The overall and detailed organization of these specifications parallels
16、that used in the equivalent ITU-T recommendations. Thus, T1.116.0-2000 through T1.116.6-2000 of this standard corresponds to ITU-T Recommendations Q.750 through Q.756. The major changes in organization and appearance of these ITU-T Recommendations account for many of the changes to this standard fro
17、m the previous issue. The following is an overview of the changes and additions incorporated into these specifications: the MRVT has been clarified and revised to enhance the capability of testing MTP routes to adjacent signalling networks; the SRVT has been clarified and revised to enhance the capa
18、bility of testing MTP routes to adjacent signalling networks; T1.116 - i T1.116-2000 the SRVT has been clarified and revised to include new SCCP routing capabilities; and T1.116.0-2000, clause 6, was revised to include details on compatibility issues. Information contained in a normative annex in th
19、ese specifications is considered part of this standard. Information contained in an informative annex in these specifications is not considered part of this standard but is auxiliary to the standard. Similarly, footnotes are not officially part of this standard. Caution should be exercised in using
20、the Specification and Description Language (SDL) diagrams to interpret the standard since they may not fully align with the text. Please note that, in case of any conflict between the text and the SDL diagrams, the text always takes precedence over the SDL. Future control of this document will resid
21、e with Accredited Standards Committee on Telecommunications, T1. This control of additions to the specification, such as ongoing protocol evolution, new applications, and operational requirements, will permit compatibility among U.S. networks. Such additions will be incorporated in an orderly manner
22、 with due consideration to the ITU-T-layered model principles, conventions, and functional boundaries. Suggestions for improvement of this standard will be welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, 1200 G Street NW, Suite 500, Washington, DC 20005. This
23、standard was processed and approved for submittal to ANSI by Accredited Standards Committee on Telecommunications, T1. Committee approval of the standard does not necessarily imply that all members voted for its approval. At the time it approved this standard, the T1 Committee had the following memb
24、ers: E. R. Hapeman, T1 Chair W.R. Zeuch, T1 Vice-Chair J.A. Crandall, T1 Director S.M. Carioti, T1 Disciplines S.D. Barclay, T1 Secretary C.A. Underkoffler, T1 Chief Editor B. Lerich, T1 Editor M. A. McGrew, T1S1.3 Technical Editor EXCHANGE CARRIERS Organization Represented Name of Representative AT
25、 b) management functions within the SS7 protocol itself (e.g., changeover, forced rerouting, subsystem management, etc.); and c) management functions defined to enable verification and validation of routing tables, Circuit Identification Codes (CICs), etc. These functions may require communication w
26、ithin the signalling network, and for this, a separate protocol is defined. Such management functions are modeled as managed objects at the interface between the network elements and an operations system. Of the three sets of management functions defined above, OMAP provides a) and c). Set b) can be
27、 modeled as existing within the “Layer Management Entities” of SS7, and the functions are defined in the standards pertinent to those layers. OMAP interacts with all layers (i.e., with all the levels) of SS7 in order to effect control of the network. This standard comprises six chapters: T1.116.0 gi
28、ves the OMAP overview; T1.116.1 defines the SS7 managed objects; T1.116.2 defines SS7 monitoring and measurements; T1.116.3-2000 defines the SS7 management functions for managed objects that themselves require SS7 communication in the network, and also the OMAP Management Application Service Element
29、 (OMASE)-User where the logic of these functions (MRVT, SRVT LEF and LFS) is modeled; T1.116.4-2000 defines the Application Service Element (ASE) for those functions defined in T1.116.3-2000, i.e., OMASE; T1.116.5-2000 defines the SS7 testers; and T1.116.6-2000 is a Guide Book to Operations, Mainten
30、ance, and Administration Part (OMAP). T1.116.0 - 1 T1.116.0-2000 Figure A-1/T1.116.0 shows the relationship between TMN, SS7 management, and the OMAP standards. OMAP uses principles of management defined in ITU-T Rec. M.3000 (TMN), and in ITU-T Recommendations of the X.700 series (OSI Management). 1
31、.2 Normative References The following standard contains provisions which, through reference in this text, constitute provisions of this American National Standard. At the time of publication, the edition indicated was valid. All standards are subject to revision, and the parties to agreements based
32、on this American National Standard are encouraged to investigate the possibility of applying the most recent edition of the standard indicated below. T1.111-2001, Signalling System Number 7, Message Transfer Part.1T1.112-2001, Signalling System Number 7, Connection Control Part Functional Descriptio
33、n.1ITU-T Rec. M.3000(02/00), Overview of TMN Recommendations.2ITU-T Rec. M.3010(02/00), Principles for a Telecommunications management network.2ITU-T Rec. Q.752(06/97), Monitoring and measurements for Signalling System No. 7 networks.2ITU-T Rec. Q.753(06/97), Signalling System No. 7 management funct
34、ions MRVT, SRVT, CVT and definition of the OMASE-user.2ITU-T Rec. Q.811(06/97), Lower Layer Protocol Profiles for the Q3 and X Interfaces.2ITU-T Rec. Q.812(06/97), Upper Layer Protocol Profiles for the Q3 and X Interfaces.2ITU-T Rec. X.701(08/97), Information Technology Open Systems Interconnection
35、Systems Management Overview.2ITU-T Rec. X.731(01/92), Information Technology Open Systems Interconnection Systems Management: State Management Function.22 Requirements upon SS7 Management There are three main requirements upon the management of SS7 and its network. These may be summarized as: a) To
36、provide a TMN interface for the network administration3 ; This requires that the administration-to-OMAP interface be presented using TMN-defined concepts (see T1.116.1-2000). b) To interwork with other TMN parts to enable the provision of a unified approach for managing the whole Telecommunications
37、Network. Examples of these other parts are the Synchronous Digital Hierarchy (SDH) or the Integrated Services Digital Network (ISDN). These other parts could be _ 1This document is available from the Alliance for Telecommunications Industry Solutions . 2This document is available from the Internatio
38、nal Telecommunications Union . 3Here, the word “administration” in the term “network administration” refers to the body or bodies (either Administrations or RPOAs) responsible for controlling the SS7 network. T1.116.0 - 2 T1.116.0-2000 administered by the same body responsible for the MTP network or
39、 Tans or other jurisdictions (e.g., when an SCCP network covers more than one MTP network, one jurisdiction might exist for each MTP network). This means that the OMAP managed objects (see T1.116.1-2000) must be compatible with, and have appropriate attributes defined for interacting with, other Tan
40、s- managed objects. c) To extend, where necessary, the management of the SS7 network as described in functional SS7 standards (e.g., T1.111.3-2001 and T1.111.4-2001 for the MTP or T1.112-2001 for the SCCP), and to amalgamate this with the TMN approach. Hence, OMAP should provide for the complete man
41、agement of the SS7 network. It should provide consistency in approach between the different layers of SS7, and it should provide consistency across the SS7 network and its network elements. SS7 already has certain management defined in T1.111.4-2001, and SCCP management defined in T1.112-2001. These
42、 functions provide some automatic fault, configuration and performance management activities. OMAP has taken these functions into account in the definition of the behavior of SS7 managed objects. OMAP also extends the functionality already defined in the MTP recommendations to a complete management
43、service for the whole SS7 network. 2.1 OMAP Layers of Management Functions 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 management,
44、network management, network element management, and the elements in the network that are managed. 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 the addition of ISDN
45、services is required so that subscribers at one exchange can use these services to connect with subscribers at another exchange. The OMAP implementation would be involved in these changes. The top management level of OMAP is network management, which provides the functions and resources to allow adm
46、inistrations (possibly via a set of administration managed objects) to control the SS7 network. Management functions and resources are provided by OMAP to allow management within the SS7 signalling points. See clause 3 for further information on the OMAP reference model. The definitions of both netw
47、ork management and network element management functions and resources utilize the TMN and OSI managed object approach, and allow changes to be coordinated within OMAP. Certain managed objects (e.g., signalling link set and linksetNePart) have relations defined between them to allow network actions t
48、o be correlated with actions in concerned signalling points. Relations are also defined between managed objects to allow “management hierarchies” to be satisfied (e.g., to forbid removal of a signalling link set without first removing all its constituent signalling links). 2.2 OMAP Management Catego
49、ries The purpose of management is to provide a service. This can be classified as initial provisioning, maintaining existing service, and expansion or contraction of the service. Management activities can be divided into categories that satisfy one or more of the above classifications. OSI defines the categories of fault management, configuration management, performance management, accounting management, and security management. Of these, the first three categories are applicable to OMAP, the last two are for further study in OMAP. T1.116.0 - 3 T1.1
