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

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
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: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright 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 Network ServiceCRConnection RequestCSMA/CDCarrier Sense Multiple Access with Collision DetectionDCEData Circuit-terminating EquipmentDCNData Communication NetworkDISDraft International Standard (ISO/IEC)DLCData Link ConnectionDLSData Link ServiceDRDisconnection RequestDSPDomain Specific PartDTEData Terminal EquipmentER-TPDUError Transport Protocol Data UnitFUFunctional UnitSIST ETS 300 150 E1:2003

Page 14ETS 300 150: November 1992HDLCHigh-level Data Link ControlIndIndicationISOInternational Organisation for StandardisationLAPBLink Access Procedure BalancedLCNLocal Communication NetworkLLCLogical link controlLMELayer Management EntityMACMedia Access ControlMDMediation DeviceNDMNormal Disconnected ModeNENetwork ElementNLRNetwork Layer RelayNRMNormal Response ModeNRZINon Return to Zero InvertedNSNetwork ServiceNSAPNetwork Service Access PointOAOverflow AcceptOSOperations SystemOSIOpen Systems InterconnectionPDUProtocol Data UnitPhPhysicalPhCPhysical ConnectionPhSPhysical ServicePICSProtocol Implementation Conformance StatementPLSPhysical Layer ServicePPDUPresentation Protocol Data UnitPVParameter ValuePVCPermanent Virtual CircuitQoSQuality of ServiceReqRequestResResponseROSERemote Operations Service ElementSIST ETS 300 150 E1:2003

Page 15ETS 300 150: November 1992SDHSynchronous Digital HierarchySLPSingle Link ProcedureSM-ASESystem Management Application Service ElementSPSession ProtocolSPDUSession Protocol Data UnitSVCSwitched Virtual Circuit1)TPDUTransport Protocol Data UnitTSAPTransport Service Access PointUNCUnbalanced operation Normal response mode Class3.2Symbols and abbreviations used in tables 2) For the purpose of this ETS, the following symbols and abbreviations apply.MMandatory.-The parameter is not present in the interaction described by the service orprimitive concerned.(=)The value of the parameter is equal to the value of the parameter in the columnto the left.*nSee NOTE 'n' the table below.4Protocol suites overviewThe protocol suites are based on CCITT Recommendation G.773.CCITT Recommendation G.771 provides guidance for the selection of protocol suites from draftCCITT Recommendation G.773 and the domain of application of these standard protocol suites.The structures of the protocol suites with the present layers are shown in figure 1. The definedcommunication services and protocols are in accordance with the Open Systems Interconnection (OSI)Reference Model (see CCITT Recommendation X.200 [12]).The protocols for the different layers are based on CCITT Recommendations and/or ISO standards.Two types of protocol suites are defined in this ETS:-short stack: protocol suite A1;-full 7 layer stack: protocol suites B1, B2 and B3.The short stack protocol suite (A1) shall be used mainly for Local Communication Network(LCN) application as specified in CCITT Recommendation M.3010 [2]. The full 7 layer stack protocolsuites (B1, B2 and B3) can be applied to both LCN and Data Communication Network (DCN) applications,as defined by CCITT Recommendation M.3010 [2].Because of the nulling of the transport layer, session layer and presentation layer for the short stackprotocol suite, a mapping function has been defined.
1)Switched Virtual Circuit corresponds to "Virtual Call" used in CCITT Recommendation X.25 [10].2)The requirements are as defined in the referred standards or CCITT Recommendations.SIST ETS 300 150 E1:2003

Page 16ETS 300 150: November 1992The full 7 layer protocol suites satisfy the requirements of complex Network Elements (NEs) (e.g.equipments for the Synchronous Digital Hierarchy (SDH)). To support already existing networks and toprovide maximum flexibility, several possibilities are defined for layers 1, 2 and 3. Each administrationshould make the selection depending on its own specific requirements and needs. Layers 5, 6 and 7 areidentical for the three protocol suites B1, B2 and B3, whilst almost identical requirements apply to layer 4.SIST ETS 300 150 E1:2003

Page 17ETS 300 150: November 1992Application LayerSystem Management ASECMISEISO 9595 (1989)ISO 9596 (1989)ROSEX.219, X.229ACSEX.217, X.227(NOTE)Mapping FunctionPresentation LayerCCITT
X.216, X.226ASN.1 Basic Encoding Rules: X.209Session LayerCCITT X.215, X.225Transport LayerISO 8073 / 8073 - AD2Transport LayerISO 8073Network LayerX.25Data Link LayerLAPB: CCITT X.25
(ISO 7776)Physical LayerCCITT V.11/ V.35 or V.28/ V.24
X.21, X.21 bis, X.27Network Layer
IP:ISO 8473
PLP:X.25/ ISO 8208Data Link LayerLAPB: CCITT X.25
(ISO 7776)Physical LayerCCITT V.11/ V.35 or V.28/ V.24
X.21, X.21 bis, X.27Network LayerISO 8473Data Link Layer
LLC:ISO 8802-2
MAC:ISO 8802-3Physical Layernot specifiedNetwork LayerISO 8473
ISO 8473/AD3Data Link Layer ISO3309 ISO7809 ISO 4335Physical LayerISO 8482EIA RS 485A1B1B2B3NOTE: ACSE is optional for protocol suite A1.Figure 1: Overview of protocol suitesSIST ETS 300 150 E1:2003

Page 18ETS 300 150: November 19925Protocol suite A15.1Physical layer5.1.1Service5.1.1.1DefinitionThe service definition for the physical layer is in accordance with CCITT Recommendation X.211 [15].The following classes of physical services shall be supported:-type of transmission is synchronous;-mode of operation is half-duplex;-topology is point-to-multipoint by a bus.5.1.1.2Service provided by the physical layerThe physical layer provides the physical service primitives and parameters as listed in table 1.Table 1: Provided physical serviceServicePrimitiveParametersPhC-ActivationPh-ACTIVATE-requestPh-ACTIVATE-indicationData TransferPh-DATA-requestPhS-UserDataPh-DATA-indicationPhC-DeactivationPh-DEACTIVATE-requestPh-DEACTIVATE-indicationThe services PhC-Activation and PhC-Deactivation shall be provided to the Layer Management Entity(LME) of the physical layer.5.1.2Physical interface5.1.2.1Physical characteristics5.1.2.1.1ConfigurationSerial bus operation in accordance with ISO 8482 [47], Part 3, in half-duplex mode.5.1.2.1.2Transmission pairsTwo screened balanced pairs, one for each direction of transmission.5.1.2.1.3ConnectorThe administration shall specify the connector type.SIST ETS 300 150 E1:2003

Page 19ETS 300 150: November 19925.1.2.2Electrical characteristics5.1.2.2.1Static and dynamic characteristicsThe static and dynamic characteristics of each bus connection shall be in accordance withISO 84823) [47]. When all generators connected to the bus are in the high impedance state, the bus shallbe set to logical level "1".5.1.2.2.2Bus terminationEach bus end shall be terminated in accordance with ISO 8482 [47].5.1.2.2.3Load connectionEach receiver shall present a maximum of one unit load, as defined in ISO 8482 [47], to the bus. Thenumber of load connections is limited to 32.5.1.2.2.4Bit rateThe bit rate shall be 19,2 kbit/s or 64 kbit/s. A bit rate of 128 kbit/s may be necessary in someapplications. The bit rate tolerance shall be ± 0,05%.5.1.2.2.5Turn-off timeFor bit rates of 19,2 kbit/s and 64 kbit/s, a transmitting station shall put its generator in the high impedancestate within 0,75 ms from the end of the last bit of the closing flag. For a bit rate of 128 kbit/s, the turn offtime shall be not more than 0,375 ms. This point is not applicable to a primary station (see subclause5.2.2.1.3).5.1.2.2.6Switch-on transientFollowing the enabling of the generator, an implementation dependent preamble of no more than 4 bittimes shall be allowed. No assumption as to the state of the bus during this preamble shall be allowed.5.1.2.3Line codeThe line code shall be Non Return to Zero Inverted (NRZI).5.1.2.3.1PrincipleEach ISO 8482 [47] transition shall represent a ZERO bit and no transition shall represent a ONE bit.5.1.2.3.2Lock in sequenceWhere required for clock extraction, it shall be possible to send a lock in sequence containing at least fourtransitions immediately prior to the beginning of the starting flag of the frame to be transmitted.5.2Data link layer5.2.1Service5.2.1.1DefinitionThe service definition of the data link layer is in accordance with CCITT Recommendation X.212 [16]. Theclass of data link service that shall be provided by the data link layer is:-a connection-mode service.
3)Compliance assumes that full compatibility with EIA RS 485 [60] is guaranteed.SIST ETS 300 150 E1:2003

Page 20ETS 300 150: November 19925.2.1.2Service required from the physical layerThe data link layer requires the data transfer service from the physical layer.5.2.1.3Service provided by the data link layerThe data link layer shall provide the data link service, primitives and parameters as listed in tables 2, 3and 4.5.2.1.3.1Data Link Connection (DLC)-EstablishmentTable 2: DLC-Establishment serviceParameter nameReq/IndRes/ConfCalled addressM-Calling addressM-Responding address-MQuality of Service (QoS)MM5.2.1.3.2Data Link Connection (DLC)-ReleaseTable 3: DLC-Release serviceParameter nameReqIndOriginator-MReasonMM5.2.1.3.3Normal data transferTable 4: Normal data transfer serviceParameter nameReqIndData Link Service (DLS) User-dataMM5.2.2Data link protocolThe data link protocol is synchronous High-level Data Link Control (HDLC) type.5.2.2.1HDLC frame structureThe HDLC frame structure shall conform to ISO 3309 [32] (frame structure).5.2.2.1.1Address fieldThe address field shall be one octet.5.2.2.1.2Information fieldThe information field in any HDLC frame shall be an integral number of octets.Information field octets shall be sent least significant bit first. The maximum length of the information fieldshall be 256 octets.5.2.2.1.3Interframe time fillA primary station shall transmit contiguous flags as interframe time fill.5.2.2.2AddressingThe secondary station shall be capable of being assigned any address in the range 1 to 254.SIST ETS 300 150 E1:2003

Page 21ETS 300 150: November 19925.2.2.2.1All station addressThe address field bit pattern "11111111" is defined as the all station address.5.2.2.2.2No station addressThe address field bit pattern "00000000" is defined as the no station address. The no station address shallnever be assigned to a secondary station.5.2.2.2.3Group addressesNot used.5.2.2.3HDLC procedureThe HDLC procedure is defined in ISO 4335 [33].5.2.2.3.1Commands and responsesThe following HDLC commands and responses shall be supported.-Commands:SNRM: Set Normal Response Mode;DISC: Disconnect.-Commands or responses:I:
Information;RR:
Receive Ready;RNR:
Receive Not Ready.-Responses:FRMR: Frame Reject;UA:
Unnumbered Acknowledgement;DM:
Disconnect Mode.5.2.2.3.2ModesTwo modes are selected:-one operational mode: Normal Response Mode (NRM);-one non-operational mode: Normal Disconnected Mode (NDM).5.2.2.4Class of procedureThe Unbalanced operation Normal response mode Class (UNC) as defined in ISO 7809 [37] shall beimplemented.SIST ETS 300 150 E1:2003

Page 22ETS 300 150: November 19925.2.2.4.1HDLC optional functionsThe following HDLC optional functions shall be implemented:-unnumbered information (option No. 4);-data link test (option No. 12).5.2.2.5Other parameters of data link layer5.2.2.5.1Window sizeThe window size for unacknowledged frames is to be optional between 1 and 7. The default value is 1.5.2.2.5.2Waiting-time before a repetitionIn the case of no-reply or lost-reply, the primary station shall provide a waiting time function. The waiting-time before a repetition shall be greater than the duration of the longest frame to be sent by the primarystation, added to the response-time of the secondary station and the duration of the longest frame to besent by the secondary station.5.2.2.5.3Number of repetitionsUnder the conditions described in subclause 5.2.2.5.2, the maximum number of repetitions beforedetecting a no-reply or a lost-reply condition is fixed to 5 (6 requests).5.2.2.5.4Response timeThe secondary station shall commence the opening flag of its response not later than 5 ms after the endof the closing flag of the frame sent from the primary station.5.3Network layer for A15.3.1Service5.3.1.1Service definitionThe definition of the connectionless mode network service shall comply with that specified inISO 8348/AD 1 [43]. Address formats supported shall conform to ISO 8348/AD 2 [44].5.3.1.2Service required from the data link layerThe network layer requires the normal data transfer service from the data link layer.5.3.1.3Service provided by the network layerThe network layer shall provide the N-UNITDATA service as listed in table 5 below.Table 5: N-UNITDATA serviceParameter nameReqIndSource AddressMM(=)Destination addressMM(=)QosMMNetwork Service (NS)-User dataMM(=)SIST ETS 300 150 E1:2003

Page 23ETS 300 150: November 19925.3.2Network protocol5.3.2.1GeneralThe network protocol is as specified in ISO 8473 [45]. The subnetwork dependent convergence functionrequired for protocol suite A1 is specified in ISO 8473/AD 3 [46]. In addition to the full protocol (seesubclause 5.3.2.4), ISO 8473 [45] defines two subsets, namely:-inactive network layer protocol (see subclause 5.3.2.2);-non-segmenting network layer protocol (see subclause 5.3.2.3).The address part shall have the structure as defined in ISO 8348/AD 2 [44].For protocol suite A1, the Authority and Format Identifier (AFI) shall be set to 49, coded by 2 decimal digitsas defined in ISO 8348/AD 2 [44], which specifies local and binary coding of the Domain Specific Part(DSP).The full protocol and the two subsets permit the use of known subnetwork characteristics and aretherefore not subnetwork independent.Depending on the required usage and the subnetwork architecture, the full protocol, or one or bothsubsets, shall be supported by protocol suite A1. The selection shall be put in the Protocol ImplementationConformance Statement (PICS).5.3.2.2Inactive network layer protocolThe protocol shall be in accordance with the inactive subset of the protocol as defined in ISO 8473 [45].5.3.2.3Non-segmenting network layer protocolThe protocol shall be in accordance with category Type 1 functions of the non-segmenting subset of theprotocol as defined in ISO 8473 [45].From the optional functions (Type 3) defined in the non-segmenting subset, only the priority function shallbe supported as defined in ISO 8473 [45].5.3.2.4Full network layer protocolThe full protocol subset of category Type 1 functions, as specified in ISO 8473 [45], shall be supported.An implementation shall not transmit Protocol Data Units (PDUs) encoded using the inactive subset.Received PDUs encoded using the inactive subset shall be discarded.An implementation shall not generate data PDUs without a segmentation part, i.e. the segmentationpermitted flag shall be set to 1 and the segmentation part shall be included. However, an implementationshall be capable of receiving and correctly processing PDUs which do not contain the segmentation part.5.4Mapping function for A15.4.1IntroductionNo transport layer, session layer and presentation layer shall be specified for protocol suite A1.To provide the required service to the application layer and using the provided service of the networklayer, a mapping function is defined.No
...