1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SERIES Q: SWITCHING AND SIGNALLING Q3 interface Q.833.1 (O1 12001 ) Asymmetric digital subscriber line (ADSL) - Network element management: CMIP model ITU-T Recommendation Q.833.1 ITU-T Q-SERIES RECOMMENDATIO
2、NS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE N“ERNATI0NAL AUTOMATIC AND SEMI-AUTOMATIC WORKING 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 SIGNA
3、LLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q. 1-4.3 4.44.59 4.60-4.99 Q.lOO-Q.119 Q.12O-Q.249 Q.25O-Q.309 4.3 10-Q.399 Q.40O-Q.499 Q.50O-Q.599 Q.60O-Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM
4、 No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 4.700-4.799 Q.85O-Q.999 PUBLIC LAND MOBILE NETWORK INTERWORIUNG WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.lOOO-Q.1099 Q.llOO-Q.1199 Q. 12004.1699 Q.170O-Q.1799 4.2000-4.2999
5、Forjrther details, please refer to the list of TU-T Recommendations. ITU-T Recommendation 4.833.1 Asymmetric Digital Subscriber Line (ADSL) - Network element management: CMIP Model Summary This Recommendation specifies the 43 interface between a Broadband Access Network based on Asymmetric Digital S
6、ubscriber Line (ADSL) technology and the Telecommunications Management Network (TMN). Source ITU-T Recommendation 4.833.1 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. ITU-T Rec. 4.833.1 (01/2001) i FOREWORD The International T
7、elecommunication Union TU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector TU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them
8、with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of IT-T Re
9、commendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within IT-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
10、conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no
11、 position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property,
12、protected by patents, which may be required 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 2002 Ail rights reserved. No part of this publication may be
13、 reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing f?om ITU. ii ITU-T Rec. Q.833.1 (01/2001) CONTENTS 1 1.1 2 3 3.1 3.2 3.3 4 4.1 4.2 5 5.1 6 7 Introduction . Purpose and Scope References . Definitions, a
14、bbreviations, and conventions . Definitions Abbreviations Conventions General overview Entity relationship models 4.1.1 Entity relationship diagram for the ADSL fragment . Inheritance hierarchy Formal definitions . Object classes Type definitions Protocol stacks Annex A . Management requirements A.l
15、 Configuration A.l.l Physical Configuration A . 1.2 Logical Configuration A.2 Performance Monitoring . A.2.1 ADSL Line Terminations A.2.2 ADSL Channel Terminations Appendix I - Bibliography . Appendix II - Referenced Definitions . II . 1 11.2 Managed Object Definitions . adslChannelTTP adslChannelTT
16、PCurrentData adslChannelTTPHistoData adslConfigurat ionPro file . adslLineT TP adslLineTTPCurrentData adslLineTTPHistoryData Name Bindings . adslChannelTTP-adslLineTTP . ITU-T Rec . 4.833.1 (01/2001) Page 1 1 1 1 1 2 3 4 4 5 6 6 6 7 7 7 7 7 7 8 8 8 8 10 10 10 10 11 11 12 13 14 15 15 iii adslChannelT
17、TPCuata-adslChannelT TP adslChannelTTPHistoryData-adslChannelTTPentData adslConfigurationProle-managedElementR1 . adslLineTTP-managedElementR 1 adslLineTTPCurrentData-adslLineTTP adslLineTTPHistoryData-adslLineTTPCurrentData 11.3 Packages adslChannelCorrectedlocksPkg adslChannelCorrectedBlocksRecord
18、Pkg adslChannelRcvBlocksPkg . adslChannelRcvBlocksRecordPkg . adslChannelTxBlocksPkg . adslChannelTxBlocksRecordPkg . adslChannelUncorrectedBlocksPkg adslChannelUncorrectedBlocksRecordPkg adslConfigurationProfilePointerPkg . adslEssPkg adslEssRecordPkg . adslFastRetrainPkg . adslFastRetrainRecordPkg
19、 adslLofsRecordPkg . adslLofsPkg adslLolsPkg . adslLolsRecordPkg . adslLossPkg adslLossRecordPkg . adslLprsPkg adslLprsRecordPkg . adslSessRecordPkg . adslUassPkg adslUassRecordPkg currentCrcBLPkg adslSessPkg . allowedOperationalModesPkg fastPkg . mitFailePkg interleavedPkg interleaveDelayPkg . . ra
20、teAdaptationNotificationPkg . rateAdaptivePkg Page 15 15 15 15 16 16 16 16 16 16 16 16 17 17 17 17 17 17 17 18 18 18 18 18 18 19 19 19 19 19 19 19 19 20 20 20 20 21 21 21 iv ITU-T Rec . 4.833.1 (01/2001) Page 21 rateChangeRatioPkg . powerManagementPkg . adslChannelCodeViolationsPkg . adslChannelCode
21、ViolationsRecordPkg adslFecsPkg adslFecsRecordPkg . 11.4 Attributes adslAvailability Status . adslChannelCorrectedloc ks adslChannelCTPId adslChannelRcvBlocks . adslChannelTxBlocks . adslChannelUncorrectedBloc ks adslConfigurationPro fileId . adslConfigurationProfilePointer . adslEss . adslFailedFas
22、tRetrains adslFecs . adslLineTTPId adsllo fs . adsllols . adslloss adsllprs . adslN users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T R
23、ecommendations is regularly published. i 2 3 4 5 6 7 ITU-T G.992.1 (1999), Asymmetric digital subscriber line (ADSL) transceivers. IT-T G.997.1 (1 999), Physical layer management for digital subscriber line (DSL) transceivers. ITU-T 1.75 1 (1996), Asynchronous transfer mode management of the network
24、 element view. ITU-T M.301 O (2000), Principles for a telecommunications management network. ITU-T M.3 100 (1995), Generic network information model. ITU-T X.733 (1992) I ISO/IEC 10164-4: 1992, Information technology - Open Systems Interconnection: Alarm reporting function. ADSL Forum Technical Repo
25、rt TR-O28 (1999), CMP SpeciJication for ADSL Network Element Management. 3 Definitions, abbreviations and conventions 3.1 Definitions This Recommendation defines the following terms: 3.1.1 access network The collection of network equipment which provides a transport capability for the provision of t
26、elecommunications services between a Service Node Interface (SNI) and one or more associated User Network Interfaces (UN). User signalling is carried transparently by the AN. ITU-T Rec. Q.833.1 (01/2001) 1 3.1.2 customer: The person or organization that uses the services provided by the network prov
27、ider or the service provider. A customer can be a service provider as well. 3.1.3 data communications network: Refers to the management communications network which is needed to transfer management information between OSFs and between OSFs and the NEs. 3.1.4 drop medium: Refers to the network used t
28、o transport services in a common format from the Remote Node to the Network Termination. 3.1.5 element management layer: EM functions manage the physical resources which reside in the access network. Typical management functions at this level are configuration, fault management and performance monit
29、oring. EM functions are responsible for understanding the details of transmission technology information and equipment thus removing the need for this complexity of information to be held by higher layer management functions. 3.1.6 elementhetworkhervice management system: The collection of functions
30、 at a specific layer which are implemented on a physical platform. 3.1.7 extended feeder: Provides the physical resources to extend the AN over larger distances. These physical resources will not alter the transmission on the SNI and will require minimal management. This is not considered to be part
31、 of the Network Element. 3.1.8 network element layer: Refers to the physical resources that reside in the Access Network. 3.1.9 network management layer: NM functions coordinate the management of network elements to provide a user-to-user or service node to user path in order to transport telecommun
32、ications services. NM Functions will coordinate multiple EM OSFs to provide overall network supervision. 3.1.10 network termination: Physical resource which resides in the customers premises and forms the boundary of the access network (UNI). Provides onward transmission of services over building wi
33、ring to customer premises equipment. 3.1.11 operations system function: This is the collection of similar functions which provide different levels of management capability. Four layers of management capability are defrned: Network Element (NE), Element Management (EM), Network Management (NM) and Se
34、rvice Management (SM). Each layer providing management services to the layer above. 3.1.12 service management layer: SM functions manage the services supported by the network. These functions are not concerned with the physical nature of the network. Typical functions of this layer are service creat
35、ion, provision, cessation, billing and accounting information. 3.1.13 service node: A network element that provides access to various switched andor permanent telecommunications services. For switched services, the Service node provides call control, connection control and resource handling function
36、s. 3.1.14 user: A crafts person interacting with the management system. 3.2 Abbreviations This Recommendation uses the following abbreviations: AAL ATM adaptation layer ADSL Asymmetric digital subscriber line AIS Alarm indication signal AN Access network ASN. 1 Abstract syntax notation one ATM Async
37、hronous transfer mode 2 ITU-T RW. 4.833.1 (01/2001) DCN EML ERD GDMO m MOC NEL NML NT OAM os OSF RDI RDN SDH SML SN SNI TMN TTP UNI vc VDSL VP VPC VPCI Data communications network Element management layer Entity relationship diagram Guidelines for the dewtion of managed objects Management informatio
38、n base Managed object class Network element layer Network management layer Network termination Operations, administration and maintenance Operations system Operations system function Remote defect indication Relative distinguished name Synchronous digital hierarchy Service management layer Service n
39、ode Service node interface Telecommunications management network Trail termination point User network interface Virtual channel Very high speed digital subscriber line Virtual path Virtual path connection Virtual path connection identifier 3.3 Conventions Objects and their characteristics and associ
40、ated ASN.l defined here are given names with capitals used to indicate the start of the next word and acronyms are treated as if they were words. Throughout this Recommendation, all new attributes are named according to the following guidelines: - The name of an attribute ends in the string “Ptr“ if
41、 and only the attribute value is intended to identifj a single object. The name of an attribute ends in the string “PtrList“ if and only the attribute value is intended to identifj one or more objects. The name of an attribute is composed of the name of an object class followed by the string “Ptr“ i
42、f and only the attribute value is intended to identifj a specific object class. - - ITU-T Rec. 4.833.1 (01/2001) 3 - If an attribute is intended to identify different object classes, a descriptive name is given to that attribute and a description is provided in the attribute behaviour. The name of a
43、n attribute ends in the string “Id“ if and only the attribute value is intended to identify the name of an object, in which case this attribute should be the first one listed, should use ASN. 1 NameType and should not be used to convey other information. The name of an attribute is composed of the n
44、ame of an object class followed by the string “Id“ if and only the attribute value is intended to identify the name of the object class holding that attribute. - - 4 General overview The following information model diagrams have been drawn for the purpose of clarimg the relations between the differe
45、nt object classes of the model: 1) Entity Relationship Models showing the relations of the different managed objects. 2) Inheritance Hierarchy showing how managed objects are derived from each other (Le. the different paths of inherited characteristics of the different managed objects). These diagra
46、ms are only for clarification. The formal specification in terms of GDMO templates and ASN. 1 type definitions are the relevant information for implementations. 4.1 Entity relationship models The following conventions are used in the diagrams (see Figure 1): iscontainedin - 1 : 1 containment e 1 :N
47、containment managed object class M , - - - - - - - - 1 I is associate with I ; uninstantiable object class ; nmc ; (superclass) L-J * 1 : 1 association f 1 :N association * bidirectional + unidirectional managed object class outside the actual fragment T041437MIo rn ilj “is-a“ relationship Figure UQ
48、.833.1- Conventions used in diagrams for Entity Relationship Models Where the directionality of containment is not clear, it can be identified by implications since the root class is unique. 4 ITU-T RW. Q.833.1 (01/2001) 4.1.1 See Figure 2. Entity relationship diagram for the ADSL fragment 9 pointer
49、 only present if TTP represents the ATU-C side adsLineW adslConfigurationProie P adsLineTTP CurrentData ICI adsLineTTP U HistoryData adslChannelTP adslChannelTP adslChannelTP History Data TCl4143-00 Figure 2/Q.833.1- Entity relationship diagram - ADSL fragment ITU-T Rec. 4.833.1 (01/2001) 5 4.2 Inheritance hierarchy - - “X.739“: “4.822“: SCanner cmntData See Figure 3. adsiLineTP CurrentData “M.3100“: “M.3 100“: trailTennination “M.3 100“: trailTermination Bidirectional Point adslchannel “4.822“: historyData “M.3100“: t- trailTennination pointsink
