ATIS 0300202-2015 Interworking Operations C Guidelines for Network Management of the Public Telecommunications Networks under Disaster Conditions.pdf

《ATIS 0300202-2015 Interworking Operations C Guidelines for Network Management of the Public Telecommunications Networks under Disaster Conditions.pdf》由会员分享，可在线阅读，更多相关《ATIS 0300202-2015 Interworking Operations C Guidelines for Network Management of the Public Telecommunications Networks under Disaster Conditions.pdf（14页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0300202.2015 Interwork Operations Guidelines for Network Management of the Public Telecommunications Network under Disaster Conditions As a leading technology and solutions development organization, the Alliance for Telecommunications Industry

2、Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, network functions virtualization, big data analytics, cloud services, device solutions, e

3、mergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkits, ope

4、n source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative, a member of a

5、nd major U.S. contributor to the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that th

6、e 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 Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial

7、 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 made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in

8、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 the standards. The American National Standards Institute does not develop standards and will in no circumstances give an

9、 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 the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponso

10、r 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 National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purc

11、hasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer Major accidents (such as transportation, industrial, or environmental); or Civil disturbances (such as terrorist acts or other

12、similar events). It is recognized that public telecommunications networks consist of multiple non-homogeneous interconnected networks that are based on different technologies (e.g., circuit-switched, wireless, IP, and ATM) and architectures supporting a variety of services. In some cases, the specif

13、ic types of network management actions needed may be dependent upon the underlying technology, architecture, or service being provided. Guidelines for technology specific network management actions are beyond the scope of this standard, but may be provided in future standards. See Annex B for additi

14、onal information on what types of future standards may be needed. 1.2 Purpose The purpose of this standard is to delineate network traffic management actions that should be performed prior to and during disaster conditions. This standard is applicable to all telecommunications network operators that

15、 are interconnected to the public telecommunications networks. A coordinated network traffic management response by all affected network operators should ensure the integrity of the public telecommunications networks. 1The term network management may have a broad connotation as defined in ITU-T TMN

16、Recommendations (e.g., M.3010, M.3320, and M.3400) or a narrow connotation as defined in the ITU-T E.410 Recommendation series and this standard, both of which are focused on congestion control, or what may be termed network traffic management. ATIS-0300202.2015 2 2 Normative References The followin

17、g standards contain provisions which, through reference in this text, constitute provisions of this American National Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this American National Standard are

18、 encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ITU-T Recommendation M.3320, Management requirements framework for the TMN X-interface.23 Abbreviations, Acronyms, b) Detection of disaster conditions; c) Selection of system recovery an

19、d restoration strategies to be employed; d) Implementation of network management actions; and e) Evaluation and critique of network management actions and responses. It is highly desirable that the coordination of network management actions between network operators be mechanized to as great an exte

20、nt as is feasible. For example, cooperative management actions may be performed via the TMN X-interface as shown on Figure 4.1 below. Detailed requirements for interchange of critical network management actions via the X-interface are beyond the scope of this standard, but may be provided in future

21、standards. See Annex B for additional information on what types of future standards may be needed. T0407160-96requestNENENENEOS OSXOperator AServiceOperator BFigure 4.1 Example for cooperative management via X-interface (also Figure 1/M.3320) Some cooperative network management actions (e.g., networ

22、k management controls) may also need to be indicated via the Network-to-Network Interface (NNI) as shown on Figure 4.2 below. The NNI signalling interface consists of the call control protocols and the call control signalling transport protocols. The NNI bearer interface consists of the bearer and b

23、earer transport protocols. In cases where the bearer control is separate from the call control signalling, there would also be a bearer control interface. ATIS-0300202.2015 4 BearerSignalingNetwork B Network A Network-to-Network Interface (NNI) Figure 4.2 Network Interface Diagram It is expected tha

24、t network interconnections between the various different network types will be based on standardized interconnection interfaces. For example, it is expected that the different network types will interconnect to each other using PSTN interconnection standards, such as traditional SS7 protocols for ca

25、ll control signalling and TDM trunks for bearer interconnection. In the longer term, the different types of networks may interconnect directly using interconnection standards other than the traditional PSTN interconnection. Therefore, interworking of network management control mechanisms used in the

26、 different network types will need to be agreed upon and included within interconnection standards as they are defined. Specific requirements in support of network management actions that need to be indicated across the NNI under disaster conditions are beyond the scope of this document, but should

27、be included within other standards that define NNI interconnections. 5 Phases of Cooperative Network Management Actions 5.1 Planning Planning actions by a network operator should be initiated to ensure that the most effective detection processes, control strategies, and communications with other net

28、work operators will be utilized. When forecasts, warnings, or experiences indicate that a potential disaster condition exists, existing plans shall be reviewed and updated (enhanced) to ensure that they adequately address the specific type of disaster. 5.2 Detection Serious traffic impairment or ove

29、rload conditions may indicate that a disaster condition is impacting the network. The condition may be detected by one or more of the following sources: Customers; Service providers; Network operators; Network elements; Network surveillance systems; and ATIS-0300202.2015 5 Communications Infrastruct

30、ure Information Sharing October 2000, Telcordia Notes on the Networks, Section 10 Surveillance and Control.6ATIS-0300003.2012, XML Schema Interface for Fault Management (Trouble Administration).7ATIS-0300026, Next Generation Interconnection Interoperability, (NGIIF) Reference Document, Part VI, Netw

31、ork Management Guidelines.8ATIS-0100009, Overview of Standards in Support of Emergency Telecommunications Service (ETS).9ITU-T Recommendation E.410, International network management General Information.2ITU-T Recommendation E.411, International network management Operational guidance.2ITU-T Recommen

32、dation E.412, Network management controls.2ITU-T Recommendation E.413:1988, International network management Planning.2ITU-T Recommendation E.414:1988, International network management Organization.2ITU-T Recommendation E.415:1991, International network management guidance for common channel Signall

33、ing System no. 7.2ITU-T Recommendation M.3010, Principles for a Telecommunications management network.2 ITU-T Recommendation M.3350, TMN service management requirements for information interchange across the TMN X-interface to support provisioning of Emergency Telecommunications Service (ETS).2 ITU-

34、T Recommendation M.3400, TMN Management Functions.2 6This document is available from Ericsson, at . 7This document is available from the Alliance for Telecommunications Industry Solutions (ATIS) at . 8This document is available from the Alliance for Telecommunications Industry Solutions (ATIS) at .

35、9This document is available from the Alliance for Telecommunications Industry Solutions (ATIS) at . ATIS-0300202.2015 8 Annex B: Future Study Items (informative) The following items have been identified as being important to the implementation of cooperative network management procedures under disas

36、ter conditions but are currently beyond the scope of this document. It is expected that standards pertaining to these items will be either provided in a future edition of this document, be incorporated into future editions of other existing standards documents, or be provided via the creation of one

37、 or more new standards documents. B.1 Technology-Specific Network Management Actions It is recognized that public telecommunications networks consist of multiple non-homogeneous interconnected networks that are based on different technologies (e.g., circuit-switched, wireless, IP, and ATM) and archi

38、tectures supporting a variety of services. The different network types can be generalized as illustrated in Figure B.1: 1. Circuit-Switched Networks; 2. Satellite Networks; 3. Wireless Network/Mobile Radio Access; 4. IP Cable Networks; and 5. Packet-based Multi-media Networks. Circuit-Switched Netwo

39、rks Wireless/Mobile Radio Access Networks Packet-based Multi-media Networks IP Cable NetworksSatellite Networks Figure B.1 Multiple Interconnected Networks ATIS-0300202.2015 9 For circuit-switched networks, network management procedures under disaster conditions have already been developed within th

40、e industry. For example, the generic circuit-switched network architecture consists of two distinct networks: the SS7 signalling network and the circuit switched trunk (bearer) network. A catastrophic failure (or disaster) may impact either or both networks. ITU-T Recommendation E.415, International

41、 Network Management Guidance for Common Channel Signalling System No. 7, provides guidance on responding to catastrophic failure or overload of the common channel signalling network. For other network types shown on Figure B.1, specifications similar to those developed for circuit-switched networks

42、are needed to define network management procedures under disaster conditions. In addition, network management procedures under disaster conditions need to be defined at the interworking points between various network types (i.e., the interfaces between different network clouds shown on Figure B.1).

43、B.2 Network Management Actions via the TMN X-Interface As described in clause 4, cooperative management actions may be performed via the TMN X-interface. ATIS data interchange standards based on the TMN X-interface have been produced for network management applications such as trouble administration

44、 (e.g., see ATIS-0300003). ITU-T Recommendation M.3350 describes requirements for data interchange across the TMN X-interface to support provisioning of ETS. There is a need to extend the suite of X-interface applications standards to more comprehensively address information sharing and control func

45、tions needed to perform cooperative (between network operators) network management procedures under disaster conditions. In addition to X-interface specifications applicable between network operators, a similar approach may be taken for standardization of an X-interface application with respect to Communications ISAC data interchange (see clause 5.2).