1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000652.1996(R2011) B-ISDN Signaling ATM Adaptation Layer Layer Management for the SAAL at the NNI ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standar
2、ds for the information, entertainment and communications industry. More than 250 companies actively formulate standards in ATIS 18 Committees, covering issues including: IPTV, Service Oriented Networks, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, and Billing and Operat
3、ional Support. In addition, numerous Incubators, Focus and Exploratory Groups address emerging industry priorities including “Green”, IP Downloadable Security, Next Generation Carrier Interconnect, IPv6 and Convergence. ATIS is the North American Organizational Partner for the 3rd Generation Partner
4、ship Project (3GPP), 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 information, please visit . AMERICAN NATIONAL STANDARD Approval of an Am
5、erican 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 Board of Standards Review, substantial agreement has been reached by
6、 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 made towards their resolution. The use of American National Standar
7、ds 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 the standards. The American National Standards Institute does no
8、t 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 the American National Standards Institute. Requests for interpre
9、tations 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 National Standards Institute require that action be taken periodica
10、lly 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 their existence does not in any respect preclude anyone, whether he has
11、 approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandar
12、d. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should be ad-dressed to the secretariat or sponsor whose name appears on the title pageof this sta
13、ndard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards mayreceive curr
14、ent information on all standards by calling or writing the AmericanNational Standards Institute.Published byAmerican National Standards Institute11 West 42nd Street, New York, New York 10036Copyright 1996 by American National Standards InstituteAll rights reserved.No part of this publication may be
15、reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of Americainsert code hereiForeword ii1 Scope, purpose, and application.12 Normative references.13 Abbreviations and acronyms 24 Model for interactions
16、 with Layer Management45 Interface between Layer Management and the SAAL at the NNI.46 State transition table of LM for the management of SAAL at the NNI.97 Interface to systems management 148 Peer-to-peer Layer Management communication 149 Procedures of Layer Management 14Tables1 Signals and parame
17、ters between SSCOP and Layer Management.52 Signals between SSCF at the NNI and Layer Management 63 State transition table for the LM at the NNI 104 Signalling link faults and performance.16Figures1 Relationships of Layer Management with other entities42 State transition diagram at the SSCF to LM bou
18、ndary for sequences of MAAL-signals .8AnnexesA Real system resources .19B Reference error monitor for in-Service links.20C Differences between this standard and ITU-T Recommendation Q.2144 .31D Management error indications 32E Bibliography 33 ContentsPageiiForeword (This foreword is not part of Amer
19、ican National Standard T1.652-1996.)This standard specifies the Layer Management functions for the SignalingATM Adaptation Layer (SAAL) at the Network Node Interface (NNI). Theseinclude the interfaces to the Service Specific Connection Oriented Protocol(SSCOP), (ANSI T1.637), to the Service Specific
20、 Coordination Function(SSCF) at the NNI (ANSI T1.645), and to systems management. LayerManagement provides, or supports, the following functions for the ServiceSpecific Convergence Sublayer (SSCS) at the NNI: error processing; measurements; notification of processor outage status; determination of l
21、ink quality during proving; and determination of link quality during normal operation.There are 5 annexes in this standard. Annexes A through C are normativeand are considered part of this standard. Annexes D and E are informa-tive and are not considered part of this standard.Suggestions for improve
22、ment of this standard will be welcome. Theyshould be sent to the Alliance for Telecommunications Solutions, 1200 GStreet, NW, Suite 500, Washington, DC 20005.This standard was processed and approved for submittal to ANSI byAccredited Standards Committee on Telecommunications, T1. Committeeapproval o
23、f the standard does not imply that all committee members votedfor its approval. At the time it approved this standard, AccreditedStandards Committee T1 had the following members:A.K. Reilly, ChairmanG.H. Peterson, Vice ChairmanO.J. Gusella, Jr., SecretaryW. Zeuch, Senior EditorJ. R. Dobbins, Technic
24、al EditorOrganization Represented Name of RepresentativeEXCHANGE CARRIERSAmeritech Services, Inc. Laurence A. YoungRichard Wood (Alt.)Bell Atlantic Corporation John W. SeazholtzRoger Nucho (Alt.)Bellcore.James C. StaatsE. R. Hapeman (Alt.)BellSouth Telecommunications, Inc. William J. McNamara, IIIMa
25、lcolm Threlkeld, Jr. (Alt.)Cincinnati Bell Telephone Andy MacIntyreLinda Price (Alt.)GTE Telephone Operations .Bernard J. HarrisRichard L. Cochran (Alt.)McCaw Cellular Communications.David HolmesLeo Nikkari (Alt.)National Telephone Cooperative Association .Joseph M. FlaniganNYNEX .James F. BaskinMic
26、hael Brusca (Alt.)Pacific Bell Sal R. TesoroPuerto Rico Telephone Company.Segundo RuizAlberto E. Morales (Alt.)iiiSBC Communications, Inc. C. C. BaileyJoseph Mendoza (Alt.)Sprint Local Telecommunications Division.Robert P. McCabeHarold L. Fuller (Alt.)US Telephone Association (USTA) Dennis ByrnePaul
27、 K. Hart (Alt.)US WestJames L. EitelDarryl Debault (Alt.)INTEREXCHANGE CARRIERSAT measurements; notification of processor outage status; determination of link quality during proving; and determination of link quality during normal operation.2 Normative referencesThe following standards contain provi
28、sions which, through reference in this text, constitute provisionsof this American National Standard. At the time of publication, the editions indicated were valid. Allstandards are subject to revision, and parties to agreements based on this American NationalStandard are encouraged to investigate t
29、he possibility of applying the most recent editions of thestandards indicated below.ANSI T1.635-1994, Telecommunications Broadband ISDN ATM adaptation layer type 5 commonpart functions and specification1)ANSI T1.637-1994, Telecommunications B-ISDN ATM Adaptation Layer Service SpecificConnection Orie
30、nted Protocol (SSCOP)ANSI T1.645-1995, Telecommunications B-ISDN Signaling ATM Adaptation Layer ServiceSpecific Coordination Function for Support of Signaling at the Network Node Interface (SSCF at NNI)ITU-T Recommendation Q.2144 (1995), B-ISDN Signaling Adaptation Layer - Layer Management forthe SA
31、AL at the NNI 2)_1)ANSI T1.635-1994 refers to ITU-T Recommendation I.363 (1993), B-ISDN ATM Adaptation Layer (AAL)specification, for all requirements. ITU-T Recommendation I.363 is available from the American National StandardsInstitute, 11 West 42nd Street, New York, NY 10036.2)Available from the A
32、merican National Standards Institute, 11 West 42nd Street, New York, NY 10036.ANSI T1.652-199623 Abbreviations and acronymsAA ATM AdaptationAAL ATM Adaptation LayerALN AlignmentANS Alignment Not SuccessfulATM Asynchronous Transfer ModeBER Bit Error RatioBGAK Begin Acknowledge (SSCOP PDU)BGN Begin (S
33、SCOP PDU)BGREJ Begin Reject (SSCOP PDU)B-ISDN Broadband Integrated Services Digital NetworkCC Congestion CeasedCD Congestion DetectedEND End (SSCOP PDU)ENDAK End Acknowledge (SSCOP PDU)ER Error Recovery (SSCOP PDU)ERAK Error Recovery Acknowledge (SSCOP PDU)INS IN ServiceLM Layer ManagementLPO Local
34、Processor OutageLR Local ReleaseMAA Management ATM AdaptationMAAL Management ATM Adaptation LayerMD Management Data (SSCOP PDU)MPS Management Proving StateMTP Message Transfer PartMTP-2 Message Transfer Part Level 2MTP-3 Message Transfer Part Level 3MU Message UnitNC NO CREDITNNI Network Node Interf
35、aceNRP Number of Retransmitted SSCOP PDUsOOS Out Of ServiceOSI Open Systems InterconnectionPDU Protocol Data UnitPDUT SSCOP PDU TransmittedANSI T1.652-19963PE Protocol ErrorPNS Proving Not SuccessfulPO Processor OutagePOLL Poll (SSCOP PDU)QoS Quality of ServiceRR Remote ReleaseRS Resynchronization (
36、SSCOP PDU)RSAK Resynchronization Acknowledge (SSCOP PDU)RSREC Timer_REPEAT-SRECSAAL Signaling ATM Adaptation LayerSAR Segmentation And ReassemblySD Sequenced Data (SSCOP PDU)SR SSCOP ReleaseSREC SSCOP RECoverSSCF Service Specific Coordination FunctionSSCOP Service Specific Connection Oriented Protoc
37、olSSCOP-UU SSCOP User-to-User InformationSSCS Service Specific Convergence SublayerSTAT Solicited STATus (SSCOP PDU)UD Unnumbered Data (SSCOP PDU)UDR UNITDATA ReceivedUSTAT Unsolicited STATus (SSCOP PDU)ANSI T1.652-199644 Model for interactions with Layer ManagementFigure 1 shows the relationship of
38、 Layer Management to other protocols and management entities.In the figure, solid lines connect Layer Management to entities with which it interacts directly. Clauses5, 6, and 7 provide more information on these interfaces.AAL Type 5 Common PartMTP-3SSCF at NNISSCOPSystems ManagementLayer Management
39、Figure 1 Relationships of Layer Management with other entities5 Interface between Layer Management and the SAAL at the NNIThis section defines the signals between the Layer Management entity for the SAAL at the NNI andthe SSCF at the NNI and the signals between the Layer Management entity for the SA
40、AL at the NNIand the SSCOP. Subclause 5.1 defines the interface to SSCOP. Subclause 5.2 defines the interfaceto the SSCF at the NNI. For information concerning the interface of AAL Type 5 Common Part toLayer Management, consult ANSI T1.635.NOTE Currently there are no interactions between the AAL Typ
41、e 5 Common Part and Layer Managementspecified in ANSI T1.635.ANSI T1.652-199655.1 Interface between Layer Management and SSCOPBetween Layer Management and the SSCOP the signals contained in table 1 are defined:Table 1 Signals and parameters between SSCOP and Layer ManagementTypeGeneric Name Request
42、Indication Response ConfirmMAA-ERROR Not Defined Code, Count Not Defined Not DefinedMAA-UNITDATA MU MU Not Defined Not DefinedThe definitions of these signals are found in ANSI T1.637. They are shown here for ease of reference. The MAA-ERROR signal is used by SSCOP to report the occurrence of variou
43、s error eventsto Layer Management; The MAA-UNITDATA signals are used for the non-assured transfer of information betweenpeer Layer Management entities.NOTE Thus far, no procedures using the MAA-UNITDATA signal have been defined for the LayerManagement for the SAAL at the NNI.The parameters in these
44、signals are defined as follows: The Message Unit (MU) parameter contains the service data unit that is transferred fromLayer Management to SSCOP in the MAA-UNITDATA.request and from SSCOP to LayerManagement in the MAA-UNITDATA.indication; The Code parameter indicates the type of error that occurred.
45、 A table of errors that can bereported and the corresponding Code values are given in ANSI T1.637 and are replicated forconvenience in annex D; The Count parameter indicates the number of SD PDU retransmissions that occurred.ANSI T1.652-199665.2 Interface between Layer Management and the SSCF at the
46、 NNIBetween Layer Management and the NNI SSCF the signals contained in table 2 are defined in ANSIT1.645. These definitions are repeated below for the convenience of the reader.Table 2 Signals between SSCF at the NNI and Layer ManagementSignals DirectionMAAL-PROVING.indication SSCF to LMMAAL-CLEAR_F
47、ORCE_MODES.request LM to SSCFMAAL-FORCE_EMERGENCY.request LM to SSCFMAAL-FORCE_PROVING.request LM to SSCFMAAL-STOP_PROVING.indication SSCF to LMMAAL-PROVING_UNSUCCESSFUL.response LM to SSCFMAAL-RELEASE.request LM to SSCFMAAL-LOCAL_PROCESSOR_OUTAGE.request LM to SSCFMAAL-LOCAL_PROCESSOR_RECOVERED.req
48、uest LM to SSCFMAAL-REPORT.indication SSCF to LMThese signals are defined as follows:“MAAL-PROVING.indication“is used by SSCF to initiate the error monitoring within Layer Management for connectionproving.“MAAL-FORCE_PROVING.request“is used to instruct SSCF to implement forced proving.“MAAL-FORCE_EM
49、ERGENCY.request“is used to instruct SSCF to omit proving.“MAAL-CLEAR_FORCE_MODES.request“is used to notify SSCF that Layer Management is indifferent to which proving mode is used.“MAAL-RELEASE.request“is used to instruct SSCF to release the connection.“MAAL-STOP_PROVING.indication“is used to indicate that the proving procedure has terminated.“MAAL-PROVING_UNSUCCESSFUL.response“is used to notify SSCF that the proving was not successful.“MAAL-LOCAL_PROCESSOR_OUTAGE.request“is used to notify SSCF of local processor outage.“MAAL_LOCAL_PROCES
