1、INTERNATIONAL TELECOMMUNICATION UNIONITU-T Q.824.7TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(02/2000)SERIES Q: SWITCHING AND SIGNALLINGQ3 interfaceStage 2 and stage 3 description for the Q3interface Customer administration: Enhancedbroadband switch managementITU-T Recommendation Q.824.7(Formerly
2、CCITT Recommendation)ITU-T Q-SERIES RECOMMENDATIONSSWITCHING AND SIGNALLINGSIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.10
3、0Q.119SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 Q.120Q.249SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.250Q.309SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q.499DIGITAL EXCHANGES Q.500Q.599INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699SPECIFIC
4、ATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799General Q.700Message transfer part (MTP) Q.701Q.709Signalling connection control part (SCCP) Q.711Q.719Telephone user part (TUP) Q.720Q.729ISDN supplementary services Q.730Q.739Data user part Q.740Q.749Signalling System No. 7 management Q.750Q.759ISDN user
5、 part Q.760Q.769Transaction capabilities application part Q.770Q.779Test specification Q.780Q.799Q3 INTERFACE Q.800Q.849DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999PUBLIC LAND MOBILE NETWORK Q.1000Q.1099INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199INTELLIGENT NETWORK Q.1200Q.1699S
6、IGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799BROADBAND ISDN Q.2000Q.2999For further details, please refer to the list of ITU-T Recommendations.ITU-T Q.824.7 (02/2000) iITU-T Recommendation Q.824.7Stage 2 and stage 3 description for the Q3 interface Customer administration:Enhanced b
7、roadband switch managementSummaryThis Recommendation specifies the Q3 interface between an ATM switch with enhancedfunctionality and the Telecommunications Management Network (TMN). The interface specified isthat between TMN Network Elements or Q-Adapters which interface to TMN Operations Systems(OS
8、s) without mediation and between OSs and Mediation Devices, as defined inITU-T Recommendation M.3010.The scope of this Recommendation includes the management of switched VPs as defined inITU-T Recommendations Q.2766.1 and Q.2934 and of soft PVCs as defined inITU-T Recommendation Q.2767.1.SourceITU-T
9、 Recommendation Q.824.7 was prepared by ITU-T Study Group 4 (1997-2000) and approvedunder the WTSC Resolution 1 procedure on 4 February 2000.ii ITU-T Q.824.7 (02/2000)FOREWORDThe International Telecommunication Union (ITU) is the United Nations specialized agency in the field oftelecommunications. T
10、he ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ ofITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendationson them with a view to standardizing telecommunications on a worldwide basis.The World Telecommunication Standard
11、ization Conference (WTSC), which meets every four years,establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on thesetopics.The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1.In some areas of information tech
12、nology which fall within ITU-Ts purview, the necessary standards areprepared on a collaborative basis with ISO and IEC.NOTEIn this Recommendation, the expression “Administration“ is used for conciseness to indicate both atelecommunication administration and a recognized operating agency.INTELLECTUAL
13、 PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation mayinvolve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence,validity or applicability of claimed Intellectual Property Rights, whether asse
14、rted by ITU members or othersoutside of the Recommendation development process.As of the date of approval of this Recommendation, ITU had not received notice of intellectual property,protected by patents, which may be required to implement this Recommendation. However, implementors arecautioned that
15、 this may not represent the latest information and are therefore strongly urged to consult theTSB patent database. ITU 2001All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means,electronic or mechanical, including photocopying and microfilm, withou
16、t permission in writing from ITU.ITU-T Q.824.7 (02/2000) iiiCONTENTSPage1 Purpose and Scope 12 References 13 Definitions, abbreviations and conventions . 23.1 Definitions 23.2 Abbreviations . 33.3 Conventions 44 General overview 44.1 Entity relationship models 54.1.1 Entity relationship diagram for
17、the switched virtual paths . 54.1.2 Entity relationship diagram for the soft PVCs 64.2 Inheritance hierarchy 75 Formal definitions 75.1 Object classes . 75.1.1 Profiling notes for imported classes 85.1.2 Definition of classes 85.2 Name bindings 115.2.1 softPvc-managedElementR1 . 115.2.2 vpPool-tcAda
18、ptorTTPBidirectional 115.3 Definition of packages 125.3.1 atmTrafficDescriptorPtrPkg (ATM traffic descriptor pointer package) . 125.3.2 calledPartyVciPkg (called party VCI package). 125.3.3 calledPartyVpciPkg (called party VPCI package) 125.3.4 callingPartyNumberPtrPkg (calling party number pointer
19、package) 125.3.5 callingPartyVciPkg (calling party VCI package) 125.3.6 callingPartyVpciPkg (calling party VPCI package) 125.3.7 retryPkg (retry package) 135.3.8 uniAccessPtrPkg (uni access pointer package) . 135.4 Definition of attributes . 135.4.1 atmTrafficDescriptorPtr (ATM traffic descriptor po
20、inter) 135.4.2 calledPartyNumber (called party number) 135.4.3 calledPartySelectionType (called party selection type) 135.4.4 calledPartyVci (called party VCI). 145.4.5 calledPartyVpci (called party VPCI). 145.4.6 callingPartyDirectoryNumberPtr (calling party directory number pointer) 145.4.7 callin
21、gPartyVci (calling party VCI) 145.4.8 callingPartyVpci (calling party VPCI) 14iv ITU-T Q.824.7 (02/2000)Page5.4.9 egressBandwidth (egress bandwidth) 155.4.10 ingressBandwidth (ingress bandwidth) . 155.4.11 retryInterval (retry interval) 155.4.12 retryLimit (retry limit). 155.4.13 softPvcCause (soft
22、PVC cause). 155.4.14 softPvcId (soft PVC identifier) . 165.4.15 switchingModes (switching modes) 165.4.16 uniAccessPtr (uni access pointer) . 165.4.17 vpiRange (VPI range) 165.4.18 vpPoolAndVpciPtrList (VP pool and VPCI pointer list) 165.4.19 vpPoolId (VP pool identifier) 176 Type definitions 177 Pr
23、otocol stacks 18Annex A Management requirements 19A.1 Management requirements for switched virtual paths 19A.2 Management requirements for user-to-user soft PVCs 19Appendix I Bibliography 20Appendix II Instantiation examples for switched VPs . 22ITU-T Q.824.7 (02/2000) 1ITU-T Recommendation Q.824.7S
24、tage 2 and stage 3 description for the Q3 interface Customer administration:Enhanced broadband switch management1 Purpose and ScopeThis Recommendation specifies the Q3 interface between an ATM switch with enhancedfunctionality and the Telecommunications Management Network (TMN). The interface specif
25、ied isthat between TMN Network Elements or Q-Adapters which interface to TMN Operations Systems(OSs) without mediation and between OSs and Mediation Devices, as defined inITU-T Recommendation M.3010 5.The scope of this Recommendation includes the management of switched VPs as defined inITU-T Recomme
26、ndations Q.2766.1 8 and Q.2934 11 and of soft PVCs as defined inITU-T Recommendation Q.2767.1 9. The associated management for customer administration andfor call routing is also within the scope of this Recommendation. The object model in thisRecommendation is based on and extends the model in ITU-
27、T Recommendation Q.824.6 12.The definition of the functionality of TMN Operations Systems is outside the scope of thisRecommendation. Security management is also outside the scope of this Recommendation.Existing protocols are used where possible, and the focus of the work is on defining the objectmo
28、del.2 ReferencesThe following ITU-T Recommendations and other references contain provisions which, throughreference in this text, constitute provisions of this Recommendation. At the time of publication, theeditions indicated were valid. All Recommendations and other references are subject to revisi
29、on; allusers of this Recommendation are therefore encouraged to investigate the possibility of applying themost recent edition of the Recommendations and other references listed below. A list of the currentlyvalid ITU-T Recommendations is regularly published.1 ITU-T Recommendation I.311 (1996), B-IS
30、DN general network aspects.2 ITU-T Recommendation I.363.5 (1996), B-ISDN ATM Adaptation Layer (AAL)specification: Type 5 AAL.3 ITU-T Recommendation I.610 (1999), B-ISDN operation and maintenance principles andfunctions.4 ITU-T Recommendation I.751 (1996), Asynchronous transfer mode management of the
31、network element view.5 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications managementnetwork.6 ITU-T Recommendation M.3100 (1995), Generic network information model.7 ITU-T Recommendations Q.2761 (1999), Q.2762 (1999), Q.2763 (1999), Q.2764 (1999),B-ISDN User Part (B-ISUP) of Sig
32、nalling System No. 7.8 ITU-T Recommendation Q.2766.1 (1998), Switched virtual path capability.9 ITU-T Recommendation Q.2767.1 (2000), Soft PVC capability.2 ITU-T Q.824.7 (02/2000)10 ITU-T Recommendation Q.2931 (1995), Digital Subscriber Signalling System No. 2 User-Network Interface (UNI) layer 3 sp
33、ecification for basic call/connection control.11 ITU-T Recommendation Q.2934 (1998), Digital subscriber signalling system No. 2 Switched virtual path capability.12 ITU-T Recommendation Q.824.6 (1998), Broadband Switch Management.13 CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1992, Informatio
34、n technology Open Systems Interconnection Structure of management information: Managementinformation model.14 CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, Information technology Open Systems Interconnection Structure of management information: Definition ofmanagement information.15 CCIT
35、T Recommendation X.731 (1992) | ISO/IEC 10164-2:1992, Information technology Open Systems Interconnection Systems management: State management function.16 CCITT Recommendation X.732 (1992) | ISO/IEC 10164-3:1992, Information technology Open Systems Interconnection Systems management: Attributes for
36、representingrelationships.3 Definitions, abbreviations and conventions3.1 DefinitionsThis Recommendation defines the following terms:3.1.1 permanent VCC: A permanent VCC is a virtual circuit connection which is established byconfiguration management, not by on-demand call control.3.1.2 soft PVC: A c
37、onnection which is provisioned via management at the soft PVC CallingEndpoint (at the source interface) and established by signalling procedures across a network to thesoft PVC Called Endpoint (at the destination interface).3.1.3 virtual channel trail: This corresponds to a VCC in standard ATM termi
38、nology.3.1.4 virtual channel trail termination point: This corresponds to the end point of a VCC andmarks the extremity of an end-to-end F5 OAM flow.3.1.5 virtual channel connection termination point: This corresponds to an intermediate pointof a VCC and may mark the extremity of a segment F5 OAM fl
39、ow.3.1.6 virtual path trail: This corresponds to a VPC in standard ATM terminology.3.1.7 virtual path trail termination point: This corresponds to the end point of a VPC and marksthe extremity of an end-to-end F4 OAM flow.3.1.8 virtual path connection termination point: This corresponds to an interm
40、ediate point of aVPC and may mark the extremity of a segment F4 OAM flow.In addition, this Recommendation uses terms defined in ITU-T Recommendations:3.1.9 F4 OAM flow: See ITU-T I.610 3.3.1.10 F5 OAM flow: See ITU-T I.610 3.3.1.11 soft PVC called endpoint: See ITU-T Q.2767.1 9.3.1.12 soft PVC calli
41、ng endpoint: See ITU-T Q.2767.1 9.3.1.13 trail termination point: See ITU-T M.3100 6.ITU-T Q.824.7 (02/2000) 33.1.14 virtual channel: See ITU-T I.311 1.3.1.15 virtual channel connection: See ITU-T I.311 1.3.1.16 virtual path: See ITU-T I.311 1.3.1.17 virtual path connection: See ITU-T I.311 1.3.2 Ab
42、breviationsThis Recommendation uses the following abbreviations:AAL ATM Adaptation LayerAIS Alarm Indication SignalASN.1 Abstract Syntax Notation OneATM Asynchronous Transfer ModeERD Entity Relationship DiagramGDMO Guidelines for the Definition of Managed ObjectsMIB Management Information BaseMOC Ma
43、naged Object ClassNNI Network-Network Interface OAM Operations, Administration and MaintenanceOS Operations SystemPVC Permanent Virtual ConnectionPVCC Permanent Virtual Channel ConnectionPVPC Permanent Virtual Path ConnectionRDI Remote Defect IndicationRDN Relative Distinguished NameSDH Synchronous
44、Digital HierarchySVP Switched Virtual PathTMN Telecommunications Management NetworkTTP Trail Termination PointUNI User-Network InterfaceVC Virtual ChannelVCC Virtual Channel ConnectionVCI Virtual Channel IdentifierVP Virtual PathVPC Virtual Path ConnectionVPCI Virtual Path Connection IdentifierVPI V
45、irtual Path Identifier4 ITU-T Q.824.7 (02/2000)3.3 ConventionsObjects and their characteristics and associated ASN.1 defined here are given names with capitalsused to indicate the start of the next word and acronyms are treated as if they were words.Throughout this Recommendation, all new attributes
46、 are named according to the followingguidelines: The name of an attribute ends in the string “Ptr“ if and only if the attribute value is intendedto identify a single object. The name of an attribute ends in the string “PtrList“ if and only if the attribute value isintended to identify one or more ob
47、jects. The name of an attribute is composed of the name of an object class followed by the string“Ptr“ if and only if the attribute value is intended to identify a specific object class. If an attribute is intended to identify different object classes, a descriptive name is given tothat attribute an
48、d a description is provided in the attribute behaviour. The name of an attribute ends in the string “Id“ if and only if the attribute value is intendedto 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 co
49、nvey other information. The name of an attribute is composed of the name of an object class followed by the string“Id“ if and only if the attribute value is intended to identify the name of the object classholding that attribute.4 General overviewThe following information model diagrams have been drawn for the purpose of clarifying therelations between the different object classes of the model.1) Entity Relationship Models showing the relations of the different managed objec
