1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SERIES Q: SWITCHING AND SIGNALLING Q3 interface Q.832.3 (O1 /2001) Broadband access coordination ITU-T Recommendation Q.832.3 (Formerly CCIlT Recommendation) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNA
2、LLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI- AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No.
3、6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q. 14.3 Q.4-Q.59 Q.6O-Q.99 Q.lOO-Q.119 Q. 120-Q.249 Q.25O-Q.309 4.3 10-Q.399 Q.400-Q.499 Q.500-Q.599 0.600-0.699 - - 0.700-0.
4、799 . . Q3 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. i PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q. 1000-Q. 1099 Q. 1 100-Q. 1 199 Q. 1200-4.1699 Q.170O-Q.1799 Q.2000-Q.2999 _ F
5、or further details, please refer to the list of ITU-T Recommendations. ITU-T Recommendation Q.832.3 Broadband access coordination Summary This Recommendation specifies the X interface between the Operations System of a Service Node and the Operations System of an Access Network for the coordination
6、of the management associated with VB5.1 and VB5.2 traffic interfaces and the VB5 Q3 interfaces. Source ITU-T Recommendation 4.832.3 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. ITU-T Q.832.3 (01/2001) i FOREWORD The Internatio
7、nal Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations
8、 on them 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 o
9、f ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ i
10、s used for 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.
11、ITU takes no 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 intellectua
12、l property, 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 mu 2001 All rights reserved. No part of this publica
13、tion may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. u ITU-T Q.832.3 (01/2001) 1 1.1 2 3 3.1 3.2 3.3 4 4.1 4.2 5 5.1 5.2 5.3 5.4 5.5 CONTENTS Introduction Purpose and scope References D
14、efinitions. abbreviations. and conventions Definitions 3.1.1 VB5 Resources Abbreviations . Conventions . General overview . Entity-Relationship Models 4 . 1 . 1 Entity relationship diagram Inheritance hierarchy Formal definitions Object classes . 5.1.1 Profiling notes for imported classes . 5.1.2 De
15、finition of classes Name bindings . 5.2.1 xvb5-managedElementR1 Definition of packages Definition of attributes 5.4.1 xvb5Id (X-VB5 identifier) . Definition of actions . 5.5.1 addAnLoopRequest (add AN loop request) 5.5.2 addLupsRequest (add LUPs request) 5.5.3 addVb5ConnectionRequest (add VB5 connec
16、tion request) . 5.5.4 addVb5InterfaceRequest (add VB5 interface request) 5.5.5 addVb5ProtocolRequest (add VB5 protocol request) . 5 S.6 addVb5ProtocolVpRequest (add VB5 protocol VP request) . 5.5.7 addVb5VcsRequest (add VB5 VCs request) 5.5.8 addVb5VpsRequest (add VB5 VPs request) . 5 S.9 anServiceL
17、abeiInquiry (AN service label inquiry) . 5.5.10 auditVb5ConnectionRequest (audit VB5 connection request) 5.5.11 auditVb5VpciRequest (audit VB5 VPCI request) . 5.5.12 1istLupsRequest (list LUPs request) . 5.5.13 listVb5ProtocolDetailsRequest (list protocol details request) . 5.5.14 listVb5InterfacesR
18、equest (list VB5 interfaces request) . ITU-T Q.832.3 (01/2001) Page 1 1 1 1 1 1 2 2 3 3 4 4 4 4 4 5 6 6 6 7 7 7 7 7 7 8 8 8 8 8 9 9 9 9 9 10 . 111 5.5.15 5.5.16 5.5.17 5.5.18 5.5.19 5.5.20 5.5.21 5.5.22 5.5.23 5.5.24 5.5.25 listVb5VcsRequest (list VB5 VCs request) listVb5VpsRequest (list VB5 VPs req
19、uest) removeAnLoopRequest (remove AN loop request) removeLupsRequest (remove LUPs request) removeVb5InterfaceRequest (remove VB5 interface request) removeVb5ProtocolRequest (remove VB5 protocol request) . removeVb5VcsRequest (remove VB5 VCs request) removeVb5VpsRequest (remove VB5 VPs request) . snA
20、ccessLabelsInquiry (SN access labels inquiry) . removeVb5ConnectionRequest (remove VB5 connection request) . removeVb5ProtocolVpRequest (remove VB5 protocol Vp request) . 5.6 Definition of .notifkations . 5.6.1 addLupsIndication (add LUPs indication) 5.6.2 addVb5ConnectionIndication (add VBSConnecti
21、on indication) . 5.6.3 addVb5InterfaceIndication (add VB5 interface indication) . 5.6.4 addVb5ProtocolIndication (add VB5 protocol indication) 5.6.5 addVb5ProtocolVpIndication (add VB5 protocol VP indication) . 5.6.6 addVb5VcsIndication (add VB5 VCs indication) . 5.6.7 addVb5VpsIndication (add VB5 V
22、Ps indication) . 5.6.8 removelupshdication (remove LUPs indication) 5.6.9 removeVb5ConnectionIndication (remove VBSConnection indication) . 5.6.10 removeVb5InterfaceIndication (remove VB5 interface indication) . 5.6.1 1 removeVb5ProtocolIndication (remove VB5 protocol indication) 5.6.12 removeVb5Pro
23、tocolVpIndication (remove VB5 protocol VP indication) . 5.6.13 removeVb5VcsIndication (remove VB5 VCs indication) . 5.6.14 removeVb5VpsIndication (remove VB5 VPs indication) . 5.6.15 resourceStatusIndication (resource status indication) . 6 Type definitions 7 Protocol stacks . Annex A . Management r
24、equirements A.l General requirements A.1.2 VPC checking A . 1.1 Coordinated VP and VC configuration . Coordination of port configuration data . Coordination of VPCI values . A . 1.3 A . 1.4 A . 1.5 Consistency of configuration . A . 1.6 Availability of information Page 10 10 10 11 11 Il 11 11 12 12
25、12 12 12 13 13 13 13 13 14 14 14 14 14 15 15 15 15 15 23 23 23 23 23 23 23 23 24 iv ITU-T Q.832.3 (01/2001) - - A.2 A . 3 A.4 AS Annex Coordination of the VB5 interface A.2.1 A.2.2 A.2.3 A.2.4 A.2.5 A.2.6 A.2.7 A.2.8 A.2.9 Creation . Verification and auditing . Modification Deletion . VC and VP prov
26、isioning Verification and auditing . VP and VC modification Verification and auditing . VP and VC deletion . Coordination of the UNI interface . A.3.1 Creation . A.3.2 Verification and auditing . A.3.3 Modification A.3.4 Deletion . Broadband Bearer Connection Control coordination requirements A.4.1
27、A.4.2 VCs at the VB5 interface . VCs at the UNI interface Fault and performance management . AS . 1 Fault reporting . A.5.2 Fault localization . B - Transaction requirements Appendix I . Bibliography . Appendix II . Summary of transactions ITU-T Q.832.3 (01/2001) Page 24 24 24 24 24 24 25 25 25 25 2
28、5 25 26 26 26 26 26 27 27 27 27 28 47 49 V ITU-T Recommendation Q.832.3 Broadband access coordination 1 Introduction 1.1 Purpose and scope This Recommendation specifies the X interface between the Operations System (OS) of a Service Node (SN) and the Operations System (OS) of an Access Network (AN)
29、for the coordination of themanagement associated with VB5.1 and VB5.2 traffic interfaces 2 and 3 and the VB5 Q3 interfaces 4 and 5. Existing protocols are used where possible, and the focus of the work is on defining the object model. The definition of the functionality of TMN Operations Systems is
30、outside the scope of this Recommendation. Security management is also outside the scope of this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of
31、 publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all 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
32、list of currently valid ITU-T Recommendations is regularly published. i ITU-T G.902 (1993, Framework Recommendation on functional access networks (AN) - Architecture and functions, access types, management and service node aspects. 2 ITU-T G.967.1 (1998), V-interfaces at the service node (SN) - VB5.
33、1 reference point specification. 3 ITU-T G.967.2 (1999), V-interfaces at the service node (SN) - VB5.2 reference point specification. 4 ITU-T Q.832.1 (1998), VB5.1 Management. 5 ITU-T 4.832.2 (1998), VB5.2 Management. 6 ITU-T X.721 (1992) I ISO/IEC 10165-2:1992, Information technology - Open Systems
34、 Interconnection - Structure of management information: Definition of management information. IETF RFC 1057(1988): RPC: Remote Procedure Call Protocol Specification: Version 2. 7 3 Definitions, abbreviations, and conventions 3.1 Definitions This Recommendation defines the following terms: 3.1.1 VB5
35、Resources: The management of user port functions and service port functions providing user network interface (UNI) and service node interface (SNI) functionality, respectively, are considered in this Recommendation based on the framework defined in ITU-T G.902 I. Transmission specific resources lie
36、outside its scope. VB5 Resources are referred to in this Recommendation as resources. ITU-T Q.832.3 (01/2001) 1 In addition this Recommendation uses terms defined in other ITU-T Recommendations as follows: ITU-T G.902 i: access network (AN), user port functions, service node (SN), service node inter
37、face (SNI), service port functions. ITU-T G.967.1 2: logical service port (LSP), logical user port (LUP), physical service port (PSP), physical user port (PUP), real time management coordination (RTMC), virtual user port (VUP). ITU-T G.967.2 3: Broadband bearer connection control (B-BCC) 3.2 Abbrevi
38、ations This Recommendation uses the following abbreviations: AN Access Network ASN. 1 Abstract Syntax Notation one ATM Asynchronous Transfer Mode B-BCC Broadband Bearer Connection Control IETF Internet Engineering Task Force LSP Logical Service Port LUP Logical User Port OS Operations System RFC Req
39、uest For Comment RTMC Real Time Management Coordination SN Service Node SNI Service Node Interface TMN Telecommunication Management Network TTP Trail Termination Point UNI User-Network Interface VC Virtual Channel VP Virtual Path VPC Virtual Path Connection VPCI Virtual Path Connection Identifier 3.
40、3 Conventions Objects and their characteristics and associated 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 guidelin
41、es: - The name of an attribute ends in the string “Ptr“ if and only if the attribute value is intended to identify a single object. The name of an attribute ends in the string “PtrList“ if and only if the attribute value is intended to identify one or more objects. The name of an attribute is compos
42、ed 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. - - 2 ITU-T Q.832.3 (01/2001) If an attribute is intended to identify different object classes, a descriptive name is given to that attribute and a descr
43、iption is provided in the attribute behaviour. The name of an attribute ends in the string “Id“ if and only if 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 o
44、ther 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 class holding that attribute. 4 General overview The following information model diagrams have been draw
45、n for the purpose of clarifying the relations 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. the different paths of inherit
46、ed characteristics of the different managed objects). These diagrams 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
47、diagrams: is contained in 1 : 1 containment 1:N containment Li is associated with 4+ 1:l association t*+ 1:N association + bidirectional + unidirectional managed object class c“-, I I ; uninstantiable object class : moc (superclass) L, managed object class outside the actual fragment T0414260-00 - *
48、, #, i i i “is-a“ relationship *. . Figure 1lQ.832.3 - 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. ITU-T Q.832.3 (01/2001) 3 4.1.1 Entity relationship diagram “X.
49、721“: top OS of AN anVie w OfSn OverXvbS OS of SN snViewOfAn OverXvb5 - TO414270- Figure 2/Q.832.3 - Entity relationship diagram 4.2 Inheritance hierarchy The Figure 3 traces the inheritance relationships from the highest level object (ITU-T X.721, “top“) to the managed objects which are defined in this Recommendation. Figure 3/Q.832.3 - Inheritance Hierarchy 5 Formal definitions This clause gives the formal definitions of the managed object classes, name bindings, general packages, behaviours, attributes, actions and notifications. 5
