ETSI ETS 300 150 ed.1 (1992-11)

Transmission and Multiplexing (TM); Protocol suites for Q interfaces for management of transmission systems

DE/TM-02001

Prenos in multipleksiranje (TM) – Nabor protokolov za vmesnike Q za upravljanje prenosnih sistemov

General Information

• Status: Published
• Publication Date: 30-Nov-1992
• Technical Committee: TM 2 - Transmission Networks Management, Performance
• Current Stage: 12 - Completion
• Due Date: 28-Aug-1992
• Completion Date: 01-Dec-1992
• Ref Project: SIST ETS 300 150 E1:2003 - Transmission and Multiplexing (TM); Protocol suites for Q interfaces for management of transmission systems

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Prenos in multipleksiranje (TM) – Nabor protokolov za vmesnike Q za upravljanje prenosnih sistemovTransmission and Multiplexing (TM); Protocol suites for Q interfaces for management of transmission systems33.040.20Prenosni sistemTransmission systemsICS:Ta slovenski standard je istoveten z:ETS 300 150 Edition 1SIST ETS 300 150 E1:2003en01-december-2003SIST ETS 300 150 E1:2003SLOVENSKI
STANDARD



SIST ETS 300 150 E1:2003



EUROPEANETS 300 150TELECOMMUNICATIONNovember 1992STANDARDSource: ETSI TC-TMReference: DE/TM-2001ICS:33.020, 33.040.40Key words:TransmissionTransmission and Multiplexing (TM);Protocol suites for Q interfaces formanagement of transmission systemsETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1992. All rights reserved.SIST ETS 300 150 E1:2003



Page 2ETS 300 150: November 1992Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 150 E1:2003



Page 3ETS 300 150: November 1992ContentsForeword.71Scope.92Normative references.93Abbreviations and symbols.133.1Abbreviations.133.2Symbols and abbreviations used in tables2).154Protocol suites overview.155Protocol suite A1.185.1Physical layer.185.1.1Service.185.1.1.1Definition.185.1.1.2Service provided by the physical layer.185.1.2Physical interface.185.1.2.1Physical characteristics.185.1.2.1.1Configuration.185.1.2.1.2Transmission pairs.185.1.2.1.3Connector.185.1.2.2Electrical characteristics.195.1.2.2.1Static and dynamic characteristics.195.1.2.2.2Bus termination.195.1.2.2.3Load connection.195.1.2.2.4Bit rate.195.1.2.2.5Turn-off time.195.1.2.2.6Switch-on transient.195.1.2.3Line code.195.1.2.3.1Principle.195.1.2.3.2Lock in sequence.195.2Data link layer.195.2.1Service.195.2.1.1Definition.195.2.1.2Service required from the physical layer.205.2.1.3Service provided by the data link layer.205.2.1.3.1Data Link Connection (DLC)-Establishment.205.2.1.3.2Data Link Connection (DLC)-Release.205.2.1.3.3Normal data transfer.205.2.2Data link protocol.205.2.2.1HDLC frame structure.205.2.2.1.1Address field.205.2.2.1.2Information field.205.2.2.1.3Interframe time fill.205.2.2.2Addressing.205.2.2.2.1All station address.215.2.2.2.2No station address.215.2.2.2.3Group addresses.215.2.2.3HDLC procedure.215.2.2.3.1Commands and responses.215.2.2.3.2Modes.215.2.2.4Class of procedure.215.2.2.4.1HDLC optional functions.225.2.2.5Other parameters of data link layer.225.2.2.5.1Window size.22SIST ETS 300 150 E1:2003



Page 4ETS 300 150: November 19925.2.2.5.2Waiting-time before a repetition.225.2.2.5.3Number of repetitions.225.2.2.5.4Response time.225.3Network layer for A1.225.3.1Service.225.3.1.1Service definition.225.3.1.2Service required from the data link layer.225.3.1.3Service provided by the network layer.225.3.2Network protocol.235.3.2.1General.235.3.2.2Inactive network layer protocol.235.3.2.3Non-segmenting network layer protocol.235.3.2.4Full network layer protocol.235.4Mapping function for A1.235.4.1Introduction.235.4.2Service.245.4.2.1Service definition.245.4.2.2Service required from network layer.245.4.2.3Service provided by the mapping function.245.4.3Procedure.245.5Application layer for A1.245.5.1Overview.245.5.2Syntax and encoding.245.5.3Association control.245.5.3.1Service description.245.5.3.2Protocol specification.255.5.4Remote operations.255.5.4.1Service description.255.5.4.2Protocol specification.255.5.5Common management information.255.5.5.1Service description.255.5.5.2Protocol specification.265.6Conformance.266Protocol suites B1, B2 and B3.266.1Physical layer.266.1.1Physical layer for B1 and B2.266.1.1.1Protocol.266.1.1.2Bit rate.266.1.1.3Connector.266.1.2Physical layer for B3.286.1.2.1Overview.286.1.2.2Service.286.1.2.3Bit rate.286.2Data link layer.286.2.1Data link layer for B1 and B2.286.2.1.1Equipment type during link set up and reset.296.2.1.2Window.296.2.1.3User information.296.2.1.4Other frame parameters.296.2.2Data link layer for B3.306.2.2.1Overview.306.2.2.2Media Access Control (MAC).306.2.2.3Logical Link Control (LLC).316.3Network layer.316.3.1Network layer for B1.316.3.1.1Equipment type during restart.316.3.1.2Other features and parameters.316.3.1.3Expedited data negotiation.316.3.1.4Receipt confirmation negotiation.326.3.1.5Throughput class.326.3.1.6Packet size negotiation.326.3.1.7User data field.33SIST ETS 300 150 E1:2003



Page 5ETS 300 150: November 19926.3.1.8Numbering plans.336.3.1.9Addressing.336.3.2Network layer for B2.336.3.2.1Protocol.336.3.2.2Network layer attributes.336.3.3Network layer for B3.336.3.3.1Service.336.3.3.2Protocol.336.3.3.3Network layer attributes.346.4Transport layer.346.4.1Transport layer for B1.346.4.1.1Class of service.346.4.1.2Protocol identification.366.4.1.3Attributes.366.4.1.4User data in connection request and connection confirmTPDUs.366.4.1.5Splitting.366.4.1.6Quality of Service (QoS) negotiation.366.4.1.7TPDU size negotiation.366.4.1.8Class 0 Error TPDU.376.4.1.9Negotiation of protection.376.4.1.10Unknown CR TPDU parameters.376.4.1.11Invalid values of known CR TPDU parameters.376.4.1.12Additional options parameter.376.4.1.13Code misalignment (for further study).376.4.2Transport layer for B2 and B3.376.4.2.1Protocol.376.4.2.2Class of service.376.4.2.3Transport layer attributes.376.5Session layer for B1, B2 and B3.386.5.1Session Protocol Data Units (SPDUs).386.5.2Transport expedited service.396.5.3Parameters.396.5.4User data.396.5.5Re-use.396.5.6Segmentation.396.5.7Invalid SPDUs.396.6Presentation layer for B1, B2 and B3.396.6.1Presentation Protocol Data Units (PPDU).396.6.2Parameters.406.6.3Encoding rules for transfer syntax.406.7Application layer for B1, B2 and B3.406.7.1Association Control Service Element (ACSE).406.7.1.1Services and protocols.406.7.1.2Application Protocol Data Units (APDUs).406.7.1.3Abstract syntax name.416.7.2Common Management Information Service Element (CMISE).416.7.2.1Service.416.7.2.2Protocol.416.7.3Remote Operations Service Element (ROSE).416.8Conformance.41History.42SIST ETS 300 150 E1:2003



Page 6ETS 300 150: November 1992BlankpageSIST ETS 300 150 E1:2003



Page 7ETS 300 150: November 1992ForewordThis European Telecommunication Standard (ETS) has been produced by the Transmission andMultiplexing (TM) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS concerns the characteristics of Q interfaces for transmission systems and equipments, and thetext is based on draft CCITT Recommendation G.773. Although in 1990 CCITT SGXV agreed to adopt theRecommendation under the accelerated approval procedure, ETSI TC-TM is seeking to provide an ETSfor use in Europe rather quicker than this. The text of this ETS is to be revised in due course to takeaccount of the eventual published version of the finally approved CCITT Recommendation G.773.NOTE:Draft CCITT Recommendation G.773 is not normatively referenced in this ETS asmost of the text is included. However, it is probable that a future edition will refer to itnormatively, thereby reducing the size of this ETS.SIST ETS 300 150 E1:2003



Page 8ETS 300 150: November 1992Blank pageSIST ETS 300 150 E1:2003



Page 9ETS 300 150: November 19921ScopeThis ETS defines the characteristics of protocol suites for Q interfaces for transmissionsystems/equipments, as defined in CCITT Recommendations M.3010 [2] and G.773. Protocol suites for Qinterfaces for other systems/equipments are to be specified in other ETSs. The interfaces will supportbidirectional data transfer for the management of telecommunications systems.This ETS defines:-the layer services;-the layer protocols;-the application service elements and protocols;-the conformance requirements to be met by an implementation of these interfaces.This ETS does not define:-the structure or meaning of the management information that is transmitted by means of theprotocol suites;-the manner in which management is accomplished as a result of the application protocolexchanges;-the interactions which result in the use of the application layer protocols.2Normative referencesThis ETS incorporates, by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references, thelatest edition of the publication referred to applies.[1]CCITT Recommendation E.164 (1992): "Numbering plan for the ISDN era".[2]CCITT Recommendation M.3010 (1989): "Principles for a telecommunicationsmanagement network".[3]CCITT Recommendation V.10 (1988): "Electrical characteristics for unbalanceddouble-current interchange circuits for general use with integrated circuitequipment in the field of data communications" (also designated as CCITTRecommendation X.26).[4]CCITT Recommendation V.11 (1988): "Electrical characteristics for balanceddouble-current interchange circuits for general use with integrated circuitequipment in the field of data communications" (also designated as CCITTRecommendation X.27).[5]CCITT Recommendation V.24 (1988): "List of definitions for interchange circuitsbetween data terminal equipment (DTE) and data circuit-terminating equipment(DCE)".[6]CCITT Recommendation V.28 (1988): "Electrical characteristics for unbalanceddouble-current interchange circuits".[7]CCITT Recommendation V.35: "Data transmission at 48 kilobits per secondusing 60-108 kHz group band circuits".SIST ETS 300 150 E1:2003



Page 10ETS 300 150: November 1992[8]CCITT Recommendation X.21 (1992): "Interface between data terminalequipment (DTE) and data circuit-terminating equipment (DCE) for synchronousoperation on public data networks".[9]CCITT Recommendation X.21 bis (1988): "Use on public data networks of dataterminal equipment (DTE) which is designed for interfacing to synchronous V-Series modems".[10]CCITT Recommendation X.25: "Interface between data terminal equipment(DTE) and data circuit-terminating equipment (DCE) for terminals operating inthe packet mode and connected to public data networks by dedicated circuit".[11]CCITT Recommendation X.121 (1992): "International numbering plan for publicdata networks".[12]CCITT Recommendation X.200 (1988): "Reference model of open systemsinterconnection for CCITT applications" (see also ISO 7498).[13]CCITT Recommendation X.208 (1988): "Specification of abstract syntaxnotation one (ASN.1)" (see also ISO 8824).[14]CCITT Recommendation X.209 (1988): "Specification of basic encoding rulesfor abstract syntax notation one (ASN.1)" (see also ISO 8825).[15]CCITT Recommendation X.211 (1988): "Physical service definition of opensystems interconnection for CCITT applications" (see also ISO/IEC 10022).[16]CCITT Recommendation X.212 (1988): "Data link service definition for opensystems interconnection for CCITT applications" (see also ISO 8886).[17]CCITT Recommendation X.213 (1988): "Network service definition for opensystems interconnection for CCITT applications" (see also ISO 8348).[18]CCITT Recommendation X.214 (1988): "Transport service definition for opensystems interconnection for CCITT applications" (see also ISO 8072).[19]CCITT Recommendation X.215 (1988): "Session service definition for opensystems interconnection for CCITT applications" (see also ISO 8326).[20]CCITT Recommendation X.216 (1988): "Presentation service definition for opensystems interconnection for CCITT applications" (see also ISO 8822).[21]CCITT Recommendation X.217 (1992): "Association control service definitionfor open systems interconnection for CCITT applications" (see also ISO 8649).[22]CCITT Recommendation X.219 : "Remote operations: model, notation andservice definition" (see also ISO 9072-1).[23]CCITT Recommendation X.223 : "Use of X.25 to provide the OSI connection-mode network service for CCITT Applications" (see also ISO 8878).[24]CCITT Recommendation X.224 (1988): "Transport protocol specification forOpen Systems Interconnection for CCITT Applications" (see also ISO 8073).[25]CCITT Recommendation X.225: "Session protocol specification for OpenSystems Interconnection for CCITT Applications" (see also ISO 8327).[26]CCITT Recommendation X.226: "Presentation protocol specification for OpenSystems Interconnection for CCITT Applications"(see also ISO 8823).SIST ETS 300 150 E1:2003



Page 11ETS 300 150: November 1992[27]CCITT Recommendation X.227 (1992): "Association control protocolspecification for Open Systems Interconnection for CCITT Applications" (seealso ISO 8650).[28]CCITT Recommendation X.229: "Remote operations: Protocol specification"(see also ISO 9072-2).[29]CCITT Recommendation X.244: "Procedure for the exchange of protocolidentification during virtual call establishment on packet switched public datanetworks".[30]ISO 2110 (1980): "Information technology - Data communication - 25-poleDTE/DCE interface connector and contact number assignments".[31]ISO 2593 (1984): "Data communication - 34 Pin DTE/DCE interface connectorand pin assignments".[32]ISO 3309 (1988): "Information processing systems - Data communication -High-level data link control procedures - Frame structure".[33]ISO 4335 (1987): "Information processing systems - Data communication -High-level data link control procedures - Consolidation of elements ofprocedures".[34]ISO 4902 (1989): "Information technology - Data communication - 37-poleDTE/DCE interface connector and contact number assignments".[35]ISO 4903 (1989): "Information technology - Data communication - 15-poleDTE/DCE interface connector and contact number assignments".[36]ISO 7776 (1986): "Information processing systems - Data communication -High-level data link control procedures - Description of the X.25 - LAPB-compatible DTE data link procedures".[37]ISO 7809 (1984): "Information processing systems - Data communication -High-level data link control procedures - Consolidation of classes ofprocedures".[38]ISO 8072 (1986): "Information processing systems - Open SystemsInterconnection - Transport service definition".[39]ISO 8073 (1988): "Information processing systems - Open SystemsInterconnection - Connection oriented transport protocol specification".[40]ISO 8073/Add.1 (1988): "Information processing systems - Open SystemsInterconnection - Connection oriented transport protocol specification -Addendum 1: Network connection management subprotocol".[41]ISO 8073/Add.2 (1989): "Information processing systems - Open SystemsInterconnection - Connection oriented transport protocol specification -Addendum 2: Class 4 operation over connectionless network service".[42]ISO 8208:1987: "Information processing systems - Data communications - X.25Packet Level Protocol for Data Terminal Equipment".[43]ISO 8348/Add.1 (1987): "Information processing systems - Data communication- Network service definition - Addendum 1: Connectionless-mode transmission".[44]ISO 8348/Add.2 (1988): "Information processing systems - Data communication- Network service definition - Addendum 2: Network layer addressing".SIST ETS 300 150 E1:2003



Page 12ETS 300 150: November 1992[45]ISO 8473 (1988): "Information processing systems - Data communication -Protocol for providing the connectionless-mode network service".[46]ISO 8473/Add.3 (1989): "Information processing systems - Data communication- Protocol for providing the connectionless-mode network service - Addendum 3:Provision of the underlying service assumed by ISO 8473 over subnetworkswhich provide the OSI data link service".[47]ISO 8482 (1987): "Information processing systems - Data communication -Twisted pair multipoint interconnections".[48]ISO 8802-2 (1988): "Information processing systems - Local area networks -Part 2: Logical link control".[49]ISO 8802-3 (1988): "Information processing systems - Local area networks -Part 3: Carrier sense multiple access with collision detection - Access methodand physical layer specifications".[50]ISO 8880-3 (1988): "Information processing systems - Protocol combinations toprovide and support the OSI network service - Part 3: Provision and support ofconnectionless-mode network service".[51]ISO DIS 9545 (1989): "Information processing systems - Open SystemsInterconnection - Application layer structure".[52]ISO 9595 (1990): "Information processing systems - Open SystemsInterconnection - Common Management Information Service definition (CMIS)".[53]ISO 9595 (1989)/DAD1: "Information processing systems - Open SystemsInterconnection - Common Management Information Service definition -Addendum 1 (CANCEL GET)".[54]ISO 9595 (1989)/DAD2: "Information processing systems - Open SystemsInterconnection - Common Management Information Service definition -Addendum 2 (REMOVE)".[55]ISO 9596 (1990): "Information processing systems - Open SystemsInterconnection - Common Management Information Protocol specification(CMIP)".[56]ISO 9596 (1989)/DAD1: "Information processing systems - Open SystemsInterconnection - Common Management Information Protocol specificationAddendum 1: (CANCEL GET)".[57]ISO 9596 (1989)/DAD2: "Information processing systems - Open SystemsInterconnection - Common Management Information Protocol specificationAddendum 2: (REMOVE)".[58]ISO TR 9577 (1990): "Information technology - Telecommunications andinformation exchange between systems - Protocol identification in the OSINetwork Layer".[59]ISO DTR 10172: "Information processing systems - Data communication -Network/Transport protocol interworking specification".[60]EIA RS 485 (1983): "Standard for electrical characteristics of generators andreceivers for use in balanced digital multipoint systems".SIST ETS 300 150 E1:2003



Page 13ETS 300 150: November 19923Abbreviations and symbols3.1AbbreviationsFor the purpose of this ETS, the following abbreviations apply.AAREA-Associate ResponseAARQA-Associate RequestACSEAssociation Control Service ElementAFIAuthority and Format IdentifierAPDUApplication Protocol Data UnitASEApplication Service ElementASN.1Abstract Syntax Notation OneCCConnection ConfirmCDCollision DetectionCDOConnect Data OverflowCLNSConnectionless-mode Network ServiceCMIPCommon Management Information ProtocolCMISCommon Management Information ServiceCMISECommon Management Information Service ElementConfConfirmCONSConnection-mode
...