ANSI ATIS 0300219-2013 Integrated Services Digital Network (ISDN) Management - Overview and Principles.pdf

《ANSI ATIS 0300219-2013 Integrated Services Digital Network (ISDN) Management - Overview and Principles.pdf》由会员分享，可在线阅读，更多相关《ANSI ATIS 0300219-2013 Integrated Services Digital Network (ISDN) Management - Overview and Principles.pdf（24页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0300219.2013 INTEGRATED SERVICES DIGITAL NETWORK (ISDN) MANAGEMENT OVERVIEW AND PRINCIPLES As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing

2、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 follow a fast-track

3、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 American Organizatio

4、nal 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 (CITEL). For more

5、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 judgment of the ANSI Boa

6、rd 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 concerted effort be ma

7、de 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 not conforming to

8、 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 Standard in the name of

9、 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 of the American Na

10、tional 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 Disclaimer this n

11、eed for options is imposed by significant differences between carriers as well as between network elements. ANSI guidelines specify two categories of requirements: mandatory and recommendation. The mandatory requirements are designated by the word shall and recommendations by the word should. Where

12、both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation represents a goal currently identifiable as having distinct compatibility or performance advantages. Suggestions for improvement of this document are welcome. They should be sent to the Allianc

13、e for Telecommunications Industry Solutions, TMOC, 1200 G Street NW, Suite 500, Washington, DC 20005. At the time of consensus on this document, TMOC, which was responsible for its development, had the following leadership: T. Barrett, TMOC Chair (AT the physical termination at the customer end is t

14、he network termination. 3.1.4 failure: The termination of the ability of an item to perform a required function. A failure is an event. 3.1.5 fault: The inability of an item to perform a required function, excluding inability due to preventive maintenance, lack of external resources, or planned acti

15、on. A fault is often the result of a failure. 3.1.6 maintenance: A subset of the functions needed to manage an ISDN. It is the combination of all technical and corresponding administrative actions, including supervision actions, intended to retain an item in, or restore it to, a state in which it ca

16、n perform a required function. 3.1.7 network: A collection of transmission and switching facilities used to establish communication channels. 3.1.8 network element (NE): The telecommunications equipment (groups or parts) within ISDN that provides support, or service, or both, to the customer. 3.1.9

17、network interface (NI): The point of demarcation between the network and the Customer Installation (CI). 3.1.10 network maintenance: Network maintenance deals with the maintenance of the network providers entire network. It includes the maintenance of the customer access as well as those parts of ot

18、her network elements, such as switches, signalling systems, and interoffice transmission facilities, used to provide ISDN services. 3.1.11 operations system (OS): A system that processes information related to telecommunication management to support or to control or to support and control the realiz

19、ation of various telecommunication management functions. To support customer access maintenance, OSs shall perform surveillance and testing functions. 3.1.12 reference point: A conceptual point at the conjunction of two nonoverlapping functional groups. In a specific access arrangement, a reference

20、point may correspond to a physical interface between pieces of equipment, or there may not be any physical interface corresponding to the reference point. There may be more than one physical interface associated with a reference point. 3.1.13 user-to-user maintenance: The set of procedures by which

21、an end-user can manage both the logical and physical aspects of network resources at and between any customer end-points. These procedures permit the management of customer systems and resources, as well as the management of intermediate network 2Available from ITU-T at . ATIS-03000219.2013 3 resour

22、ces. Maintenance is done by the customer through monitoring of network quality-of-service and by direct management access to customer systems. Maintenance is also done for the customer systems and network services through customer interaction with intermediate management systems operated by the netw

23、ork providers or management service agents. 3.2 Abbreviations Accounting management; Configuration and name management; Performance management; and Security management. 4.2.1.5 Management Processes For the purposes of systems management, management processes are categorized either as managing proces

24、ses or agent processes. A managing process is that part of a distributed application process that has responsibility for one or more management activities. An agent process is that part of a distributed application process that, at the request of a managing process, manages the associated managed ob

25、jects. An agent process performs the management function upon receipt of a directive specifying management operations on managed objects. Agent processes may also forward directives to managing processes to convey information (or notifications) generated by managed objects. 4.2.1.6 Management System

26、 An application process within a management domain that performs or causes monitoring and control of objects in that domain or manages the actions targeted for other domains. ATIS-03000219.2013 5 4.2.2 Management Domain Relationships The manipulation and control of managed objects is determined by t

27、he relationship of management domains. Two basic relationships exist that cover the interaction of management access to managed objects. 4.2.2.1 Peer Relationship: A peer relationship is defined as one in which each complex (including its supporting management systems, if present) is responsible for

28、 the managed objects in its domain and whereby no peer management system can control objects outside its domain. The complex and the managed systems are in the same domain. Interaction between domains may occur but only on a request, not a command, basis. 4.2.2.2 Hierarchical Relationship: A hierarc

29、hical relationship is defined as one in which managed objects in a (sub-) domain may be accessed and controlled by either the complex of the (sub-) domain it is within or by the complex of a domain that includes the subdomain of the managed system. Figure 4 illustrates these relationships. Domains A

30、 and B have a hierarchical relationship. Complex A may control managed systems 1 and 2. It may also control managed systems 3 and 4 either directly or by interacting with complex B. Domains A and C have a peer relationship. For example, Complex C may interact with managed system 1 only via an intera

31、ction with complex A. 4.3 ISDN Management Domain Model This subclause presents a model for management control relationships for ISDN. The model is used for illustrative purposes only and does not preclude any specific management control functions from being provided by either the customer or the net

32、work. The equipment and functions defined in this subclause may be centralized or distributed, as appropriate. 4.3.1 ISDN Management Domain Terminology The relationship between the network provider, customer, and third party maintenance providers is discussed in terms of the terminology defined in 4

33、.3.1.1 4.3.1.2, and shown in Figure 5. A complex consists of network elements, operations systems, and staff. A complex is responsible for management functionality. Figure 6 shows the relationships of these definitions to the domain model. 4.3.1.1 Administration Management Complex (AMC) Administrati

34、on in this document is taken to mean the network provider. An AMC represents a complex controlled by a network provider, which has the responsibility and capability for (among other management functions) the maintenance functions and the maintenance actions within a network. (The domain of the AMC i

35、s the network.) The management functionality of an AMC is distributed among network elements, operation systems, and staff. 4.3.1.2 Customer Management Complex (CMC) A CMC represents a complex controlled by a customer, which has the responsibility and capability for (among other management functions

36、) the maintenance functions and the maintenance actions within a customers installations, and for the maintenance, from the customers point-of-view, of the services that the ISDN provides. The domain of the CMC includes the CI. The management functionality of a CMC is distributed among customer inst

37、allation elements, operation systems, and staff. Note that the CMC may be provided by the customer or by another party or by some combination of the two. ATIS-03000219.2013 6 4.3.1.3 Management Service Complex (MSC) The MSC represents a complex, provided by a third party, which has the responsibilit

38、y for maintaining some service provided to the customer or some equipment provided by the customer or both. The MSC does not control the maintenance functions of the customer access (CA) or customer installation (CI) directly, but can request such functions of the AMC or CMC, respectively. 4.3.1.4 I

39、SDN Management Domain Relationships The maintenance of the ISDN access is the shared responsibility of the AMC (responsible for CA maintenance) and the CMC (responsible for CI maintenance). User-to-user maintenance may be provided by the interaction of MSCs with various AMCs and CMCs, as needed and

40、authorized. As an example, Figure 7 shows four public ISDNs and one private ISDN. Several CIs, each with a CMC, are shown attached to these ISDNs via standard ISDN interfaces. Each public ISDN is shown with an AMC that may be distributed. MSCs are shown as being provided by third parties. ISDN acces

41、s and end-to-end circuits and services are maintained by an interaction of MSCs, AMCs, and CMCs. 4.4 User Management Communications Model As shown in Figure 8, the user of ISDN can obtain management services through three distinct communications paths: end-to-end between CMCs, between the CMC and AM

42、Cs, and between the CMC and MSCs. The communications model describes each of these relationships, the model components, and the paths between components required to achieve the network management objective. 4.4.1 CMC-to-CMC Management Communications Model For end-to-end management, the users rely on

43、 the relationships within or between the customer management complexes (CMCs) to provide overall management coordination. This communication may be achieved through the use of ISDN services. 4.4.2 CMC-to-AMC Management Communications Model Communications to the AMC from the CMC provide information a

44、bout the management of the customer access and ISDN services. 4.4.3 CMC-to-MSC Management Communications Model The CMC may request the MSC to act as a coordinator for ISDN management services. This may require both CMC-to-MSC and MSC-to-AMC communications. An MSC may request management services from

45、 several AMCs for a user. 4.5 Telecommunications Management Network 4.5.1 Basic Concept The telecommunications management network (TMN) is a management support network intended to overlay the telecommunications network and provide for the management of that telecommunications network. The basic conc

46、ept behind the TMN is to provide an organized network structure to achieve the interconnection of the various types of OSs and telecommunications equipment using an agreed upon architecture with standardized protocols and interfaces. A TMN will provide many management functions and will offer commun

47、ications both between OSs and between the OSs and the various network elements (NEs). It will be used to manage both the individual NEs and the overall networks themselves, including ISDNs. ATIS-03000219.2013 7 4.5.2 Relationship of the TMN to the ISDN Figure 9 shows the relationship of the TMN to t

48、he ISDN network that it manages. Note that, functionally, the TMN is not part of the ISDN, but is a separate network that interfaces with it at a number of different points to receive information from and to control its management operations. It may, however, use part of the ISDN network to provide

49、TMN communications. 5 Principles 5.1 Maintenance Principles ISDN access maintenance should follow the general maintenance philosophy contained in ITU-T Recommendation M.20. This recommendation discusses phases that maintenance procedures go through during the process of normal functioning through the restoration of failures. ISDN will have particular impact on the following phases: Performance measurement (this term includes the use of performance monitoring.); Failure detection; System protection; Fault localization; Fault correction; Verification; and