1、INTERNATIONAL TELECOMMUNICATION UNIONITU-TQ.832.2TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(03/99)SERIES Q: SWITCHING AND SIGNALLINGSpecifications of Signalling System No. 7 Q3 interfaceVB5.2 ManagementITU-T Recommendation Q.832.2(Previously CCITT Recommendation)ITU-T Q-SERIES RECOMMENDATIONSSWIT
2、CHING AND SIGNALLINGFor further details, please refer to ITU-T List of Recommendations.SIGNALLING 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
3、SYSTEMS Q.100Q.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
4、.699SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.849General 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.
5、759ISDN user 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
6、.1200Q.1999BROADBAND ISDN Q.2000Q.2999Recommendation Q.832.2 (03/99) iITU-T RECOMMENDATION Q.832.2VB5.2 MANAGEMENTSummaryThis Recommendation specifies the Q3 interfaces between a Service Node (SN) and theTelecommunications Management Network (TMN) and between an Access Network (AN) and theTMN for th
7、e management associated with VB5.2 interfaces 4. The managed object classes neededin addition to those defined for VB5.1 interfaces 3 in Recommendation Q.832.1 13 are defined inthis Recommendation. The interface specified is that between TMN Network Elements orQ-Adapters which interface to TMN Opera
8、tions Systems (OSs) without mediation and between OSsand Mediation Devices, as defined in Recommendation M.3010 5.SourceITU-T Recommendation Q.832.2 was prepared by ITU-T Study Group 4 (1997-2000) and wasapproved under the WTSC Resolution No. 1 procedure on the 26th of March 1999.Recommendation Q.83
9、2.2 (03/99)iiFOREWORDITU (International Telecommunication Union) is the United Nations Specialized Agency in the field oftelecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ ofthe ITU. The ITU-T is responsible for studying technical, operating and tariff
10、questions and issuingRecommendations on them with a view to standardizing telecommunications on a worldwide basis.The World Telecommunication Standardization Conference (WTSC), which meets every four years,establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recom
11、mendationson these topics.The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down inWTSC Resolution No. 1.In some areas of information technology which fall within ITU-Ts purview, the necessary standards areprepared on a collaborative basis with ISO and IEC.
12、NOTEIn this Recommendation the term recognized operating agency (ROA) includes any individual, company,corporation or governmental organization that operates a public correspondence service. The termsAdministration, ROA and public correspondence are defined in the Constitution of the ITU (Geneva, 19
13、92).INTELLECTUAL PROPERTY RIGHTSThe ITU draws attention to the possibility that the practice or implementation of this Recommendation mayinvolve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence,validity or applicability of claimed Intellectual Prope
14、rty Rights, whether asserted by ITU members or othersoutside of the Recommendation development process.As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property,protected by patents, which may be required to implement this Recommendation. However, im
15、plementors arecautioned that this may not represent the latest information and are therefore strongly urged to consult theTSB patent database. ITU 1999All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means,electronic or mechanical, including photoc
16、opying and microfilm, without permission in writing from the ITU.Recommendation Q.832.2 (03/99) iiiCONTENTSPage1 Scope 12 References 13 Definitions, abbreviations, and conventions 23.1 Definitions23.2 Abbreviations . 33.3 Conventions 44 General overview . 44.1 Entity-relationship models . 54.1.1 Ent
17、ity-relationship diagram for the service node (Figure 2). 64.1.2 Entity-relationship diagram for the access network (Figure 3). 74.2 Inheritance hierarchy 85 Formal definitions 85.1 Object classes . 85.1.1 Profiling notes for imported classes 95.1.2 Definition of classes 95.2 Name bindings 115.2.1 v
18、clLup-vpcLupVb52. 115.2.2 vpcLupVb52-uniAccessVb5. 125.3 Definition of packages 125.3.1 lupVcLevelProfilePkg (Logical user port VC Level profile package) 125.4 Definition of attributes . 135.4.1 bbccRequired (B-BCC required). 135.4.2 connectionIdentifierFlag (Connection identifier flag) 135.4.3 vcCt
19、pPtr (VC CTP pointer). 135.4.4 vciAtLup (VCI at the logical user port) 135.4.5 vclLupId (VC link at the logical user port identifier) . 145.5 Definition of actions. 145.5.1 resetBbcc (reset BBCC protocol) 145.6 Definition of notifications 145.6.1 presyncBbccResult (result of presynchronization of BB
20、CC protocol). 145.6.2 resetBbccResult (result of reset of BBCC protocol). 146 Type definitions 157 Protocol stacks 16Recommendation Q.832.2 (03/99)ivPageAnnex A Management requirements 16A.1 Q3(AN) and Q3(SN) requirements 16A.1.1 General management requirements. 16A.1.2 Real-time management coordina
21、tion requirements. 16Annex B Relationship between VB5.2 interfaces and the management model . 17B.1 Introduction 17B.2 LSP, LUP and VPCI labels 18B.3 Shutting down 18B.4 Blocking and unblocking 18B.5 VPCI consistency checking 18B.6 Interface start-up. 18B.6.1 B-BCC start-up from SN side . 19B.6.2 B-
22、BCC start-up from AN side. 21B.7 LSP identity checking. 25B.8 RTMC reset 25B.9 B-BCC reset . 26B.10 Congestion26Annex C State transitions .26C.1 State transition tables for AN . 26C.2 State transition tables for SN 28Appendix I Bibliography 29Appendix II Instantiation example . 31II.1 Conventions 31
23、II.2 Example of VPs/VCs allocation at the AN and the SN . 31II.3 Instantiation of managed objects in the AN . 31II.4 Instantiation of managed objects at the SN 33Recommendation Q.832.2 (03/99) 1Recommendation G.832.2VB5.2 MANAGEMENT(Geneva, 1999)1 ScopeThis Recommendation specifies the Q3 interfaces
24、 between a Service Node (SN) and theTelecommunications Management Network (TMN) and between an Access Network (AN) and theTMN for the management associated with VB5.2 interfaces 4. The managed object classes neededin addition to those defined for VB5.1 interfaces 3 in Recommendation Q.832.1 13 are d
25、efined inthis Recommendation. The interface specified is that between TMN Network Elements orQ-Adapters which interface to TMN Operations Systems (OSs) without mediation and between OSsand Mediation Devices, as defined in Recommendation M.3010 5.Existing protocols are used where possible, and the fo
26、cus of the work is on defining the objectmodel. 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.The coordination of the Operation Systems of the Access Network and the Servic
27、e Node for bothVB5.1 and VB5.2 interfaces is within the scope of the planned ITU-T Recommendation Q.832.3(Access management for VB5).2 ReferencesThe following ITU-T Recommendations and other references contain provisions which, throughreference in this text, constitute provisions of this Recommendat
28、ion. At the time of publication, theeditions indicated were valid. All Recommendations and other references are subject to revision; allusers of this Recommendation are therefore encouraged to investigate the possibility of applying themost recent edition of the Recommendations and other references
29、listed below. A list of the currentlyvalid ITU-T Recommendations is regularly published.1 ITU-T Recommendation G.853.1 (1999), Common elements of the information viewpoint forthe management of a transport network.2 ITU-T Recommendation G.902 (1995), Framework Recommendation on functional accessnetwo
30、rks Architecture and functions, access types, management and service node aspects.3 ITU-T Recommendation G.967.1 (1998), V-Interfaces at the Service Node (SN): VB5.1reference point specification.4 ITU-T Recommendation G.967.2 (1999), V-Interfaces at the Service Node (SN): VB5.2reference point specif
31、ication.5 ITU-T Recommendation M.3010 (1996), Principles for a telecommunications managementnetwork.6 ITU-T Recommendation M.3100 (1995), Generic network information model.Recommendation Q.832.2 (03/99)27 ITU-T Recommendation Q.28111, Broadband Q3 and X interfaces Lower layer protocols.8 ITU-T Recom
32、mendation Q.28121, Broadband Q3 and X interfaces Upper layer protocols.9 ITU-T Recommendation Q.811 (1997), Lower layer protocol profiles for the Q3 andX interfaces.10 ITU-T Recommendation Q.812 (1997), Upper layer protocol profiles for the Q3 andX interfaces.11 ITU-T Recommendation Q.824.5 (1997),
33、Stage 2 and stage 3 description for the Q3interface Customer administration: Configuration management of V5 interfaceenvironments and associated consumer profiles.12 ITU-T Recommendation Q.824.6 (1998), Stage 2 and stage 3 description for the Q3interface Customer administration: Broadband switch man
34、agement.13 ITU-T Recommendation Q.832.1 (1998), VB5.1 Management.14 CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, Information technology Open Systems Interconnection Structure of management information: Managementinformation model.15 CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:19
35、92, Information technology Open Systems Interconnection Structure of management information: Definition ofmanagement information.16 CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2:1993, Information technology Open Systems Interconnection Systems management: State management function.17 CCITT Rec
36、ommendation X.732 (1992) | ISO/IEC 10164-3:1993, Information technology Open Systems Interconnection Systems management: Attributes for representingrelationships.18 ITU-T Recommendation I.751 (1996), Asynchronous transfer mode management of thenetwork element view.3 Definitions, abbreviations, and c
37、onventions3.1 DefinitionsThis Recommendation defines the following term:VB5 Resources: The management of user port functions and service port functions providing UserNetwork Interface (UNI) and Service Node Interface (SNI) functionality, respectively, are consideredin this Recommendation based on th
38、e framework defined in Recommendation G.902 2.Transmission specific resources lie outside its scope. VB5 Resources are referred to in thisRecommendation as resources.In addition, this Recommendation uses terms defined in ITU-T RecommendationsG.902 2: Access network (AN), User port functions, Service
39、 node (SN), Service nodeinterface (SNI), Service port functions._1Presently at the stage of draft.Recommendation Q.832.2 (03/99) 3G.967.1 3: Logical service port (LSP), Logical user port (LUP), Physical service port (PSP),Physical user port (PUP), Real-time management coordination (RTMC), Virtualuse
40、r port (VUP).G.967.2 4: Broadband bearer connection control (B-BCC).I.751 18: Message communication function (MCF).3.2 AbbreviationsThis Recommendation uses the following abbreviations:AAL ATM Adaptation LayerAIS Alarm Indication SignalAN Access NetworkASN.1 Abstract Syntax Notation OneATM Asynchron
41、ous Transfer ModeB-BCC Broadband Bearer Connection ControlERD Entity-Relationship DiagramGDMO Guidelines for the Definition Of Managed ObjectsLSP Logical Service PortLUP Logical User PortMIB Management Information BaseMOC Managed Object ClassOAM Operations, Administration and MaintenanceOLT Optical
42、Line TerminalONU Optical Network UnitOS Operations SystemPON Passive Optical NetworkRDI Remote Defect IndicationRDN Relative Distinguished NameRTMC Real-Time Management CoordinationSDH Synchronous Digital HierarchySN Service NodeSNI Service Node InterfaceTMN Telecommunications Management NetworkTTP
43、Trail Termination PointUNI User-Network InterfaceVC Virtual ChannelVDSL Very high speed Digital Subscriber LineVP Virtual PathRecommendation Q.832.2 (03/99)4VPC Virtual Path ConnectionVPCI Virtual Path Connection Identifier3.3 ConventionsNOTE While this specification on VB5.2 management makes use of
44、 Recommendation X.722/Amd.1(1995) on the SET-BY-CREATE property, the reader should be aware that Recommendation X.722/Amd.1(1995) has not been applied in the VB5.1 management specification.Objects and their characteristics and associated ASN.1 defined here are given names with capitalsused to indica
45、te 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 followingguidelines: The name of an attribute ends in the string “Ptr“ if and only if the attribute value is intendedto identify a single object.
46、 The name of an attribute ends in the string “PtrList“ if and only if the attribute value isintended to identify one or more objects. 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
47、object class. If an attribute is intended to identify different object classes, a descriptive name is given tothat attribute and 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 o
48、f 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 name of an object class followed by the string“Id“ if and only if the attribute value is intended to iden
49、tify 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 objects.2) Inheritance Hierarchy showing how managed objects are derived from each other (i.e. thedifferent paths of inherited characteristi
