ETSI EN 301 145-1 V1.1.4 (1999-03)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Teleaction service; Part 1: Protocol specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 145-1 Version 1.1.4SIST EN 301 145-1:2000en01-januar-2000SIST EN 301 145-1:2000SLOVENSKI
STANDARD
EN 301 145-1 V1.1.4 (1999-03)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Teleaction service;Part 1: Protocol specificationSIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)2ReferenceDEN/SPS-05106-1 (alo90ieo.PDF)Keywordsbearer, DSS1, ISDN, protocol, service,teleaction, teleserviceETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions and abbreviations.83.1Definitions.83.2Abbreviations.94Description.104.1Semi-permanent access.114.2PLL access.115Reference configuration and protocol architecture.115.1Reference configuration.115.2Protocol architecture for realizing the teleaction teleservice.146Operational requirements.166.1Provision and withdrawal.166.2Requirements at the service provider network side.166.3Requirements at the service provider user side.166.4Requirements at the end-user network side.166.5Requirements at end-user user side.167Coding requirements.167.1Coding principles.167.1.1Maintenance frame layouts.177.1.2Message Format.177.1.2.1LOOP REQUEST.177.1.2.2LOOP RESPONSE.187.1.2.3REPORT.187.1.3Information elements coding.187.1.3.1Message type.197.1.3.2DLCI.197.1.3.3Loop originator.197.1.3.4Loop destination.207.1.3.5Diagnostic.207.1.3.6Report type.217.1.3.7Terminal data.217.1.3.8Test data.218State definitions.229Procedures at the coincident S and T reference point.229.1Data link establishment at EU/SP interface.229.1.1Normal procedures.229.1.1.1Link establishment by EUT.229.1.1.2Link establishment by SPT.229.1.2Exceptional procedures.239.2Data link disconnection at EU/SP interface.239.2.1Normal procedures.239.2.2Exceptional procedures.239.3Error procedures.23SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)410Procedures for interworking with private ISDNs.2411Interaction with other networks.2412Interaction with supplementary services.2413Maintenance, polling and broadcast procedures.2413.1General.2413.2Procedures.2413.2.1General.2413.2.2Loop procedure.2513.2.2.1LOOP REQUEST message generation by the TMF.2513.2.2.2LOOP REQUEST message relaying.2513.2.2.3LOOP REQUEST message reception by the requested loop destination.2613.2.2.4LOOP RESPONSE message generation by the actual loop destination.2613.2.2.5LOOP RESPONSE message relaying.2613.2.2.6LOOP RESPONSE message reception by the TMF.2613.2.2.7Expiry of the loop timer.2613.2.2.8Loop timer value.2713.2.3Alarm reporting procedures.2713.2.3.1Detection of an alarm at the EUT.2713.2.3.2Detection of an alarm situation at the SPT.2713.2.3.3Detection of an alarm situation at the TMF.2713.2.4Alarm clearance.2813.3Broadcast procedures.2813.4Status request procedure.2913.5Forward compatibility procedures.2914Parameter values.3015Dynamic description.30Annex A (informative):Signalling flows.31Annex B (informative):Functional capabilities and information flows for an FRF.34B.1Introduction and scope.34B.2Description.34B.3Derivation of the functional model.34B.3.1Description of the functional entities.35B.3.1.1Description of the Connection Related Functional entity (CRF).35B.3.1.2Description of the Basic Routing Functional (BRF) entity.35B.3.1.3Description of the Database Functional (DF) entity.35B.4Information flows.36B.4.1Contents of TX_FRAME.36B.4.2Contents of CHECK.req.36B.4.3Contents of CHECK.resp.37B.4.4Contents of REJ_FRAME.37B.5Functional entity actions.37B.6SDL diagrams.39B.7Network physical location scenarios.39History.40SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document is part 1 of a multi-part EN covering the Digital Subscriber Signalling System No. one (DSS1)protocol specification for the Integrated Services Digital Network (ISDN) teleaction bearer service, as described below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification".In accordance with CCITT Recommendation I.130, the following three level structure is used to describe the bearerservices as provided by European public telecommunications operators under the pan-European ISDN:-Stage 1: is an overall service description, from the user's standpoint;-Stage 2: identifies the functional capabilities and information flows needed to support the service described instage 1; and-Stage 3: defines the signalling system protocols and switching functions needed to implement the servicedescribed in stage 1.The present document details the stage 3 aspects (signalling system protocols and switching functions) needed tosupport the teleaction bearer service. The stage 1 aspects are detailed in EN 301 131. The stage 2 aspects of theteleaction bearer service have not been specified.National transposition datesDate of adoption of this EN:12 March 1999Date of latest announcement of this EN (doa):30 June 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 December 1999Date of withdrawal of any conflicting National Standard (dow):31 December 1999SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)61ScopeThe present document specifies the stage three of the Teleaction bearer service for the pan-european Integrated ServicesDigital Network (ISDN) as provided by the European public telecommunication operators at the T reference point orcoincident S and T reference point (as defined in CCITT Recommendation I.411 [1]). Stage three identifies the protocolprocedures and switching functions needed to support a telecommunications service (seeCCITT Recommendation I.130 [2]).The present document also provides guidance on the network functionality required to implement the Teleaction service(see annex B). The functional capabilities and information flows of such network entities are described. In the absenceof a stage 2 description this information has been included in the present document. This does not preclude its futurepublication as a separate stage 2 standard.In addition, the present document specifies the protocol requirements at the T reference point where the service isprovided to the user via a private ISDN.The present document does not specify the additional requirements where the service is provided to the user via atelecommunications network that is not an ISDN, but does include interworking requirements of other networks with thepublic ISDN.Teleaction is a service providing for reliable, low volume, data communication and allied processing to users. TheTeleaction bearer service may be used for applications such as monitoring, indicating, controlling and verifying ofremote events, operations, and measurements.Charging principles are outside the scope of the present document.Further parts of the present document specify the method of testing required to identify conformance to the presentdocument.The present document is applicable to equipment, supporting the Teleaction bearer service, to be attached at either sideof a T reference point or coincident S or T reference point when used as an access to the public ISDN.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, the latest version applies.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]CCITT Recommendation I.411 (1993): "ISDN user-network interfaces - Referenceconfigurations".[2]CCITT Recommendation I.130 (1988): "Method for the characterization of telecommunicationservices supported by an ISDN and network capabilities of an ISDN".[3]CCITT Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".[4]CCITT Recommendation I.210 (1993): "Principles of telecommunication services supported by anISDN and the means to describe them".SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)7[5]CCITT Recommendation X.25 (1996): "Interface between Data Terminal Equipment (DTE) andData Circuit-terminating Equipment (DCE) for terminals operating in the packet mode andconnected to public data networks by dedicated circuit".[6]ETS 300 011: "Integrated Services Digital Network (ISDN); Primary rate user-network interface;layer 1 specification and test principles".[7]ETS 300 012: "Integrated Services Digital Network (ISDN); Basic user-network interface; Layer 1specification and test principles".[8]ETS 300 049: "Integrated Services Digital Network (ISDN); ISDN Packet Mode Bearer Service(PMBS) ISDN Virtual Call (VC) and Permanent Virtual Circuit (PVC) bearer services provided bythe D-channel of the user access - basic and primary rate".[9]ETS 300 402-1: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Data link layer; Part 1: Generalaspects [ITU-T Recommendation Q.920 (1993), modified]".[10]ETS 300 402-2: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Data link layer; Part 2: General protocolspecification [ITU-T Recommendation Q.921 (1993), modified]".[11]ETS 300 099: "Integrated Services Digital network (ISDN); Specification of the Packet Handleraccess point Interface (PHI)".[12]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[13]EN 301 131: "Integrated Services Digital Network (ISDN); Teleaction teleservice; Servicedescription".[14]CCITT Recommendation I.233 (1991): "Frame mode bearer services".[15]ITU-T Recommendation Q.72 (1993): "Stage 2 description for packet mode service".[16]ISO 8473-1: "Information technology - Protocol for providing the connectionless-mode networkservice: Protocol specification".[17]RFC 791: "Internet Protocol (IP)".SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)83Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:Bd channel: 64 kbit/s timeslot over which multiple D channel connections are multiplexed using the procedures ofETS 300 099 [11], clause 9.Bd bundle: collection of Bd channels.Basic Network Provider (BNP): entity responsible for the installation and the maintenance of the network supportingthe teleaction service.bearer service: see CCITT Recommendation I.112 [3], subclause 2.2, definition 202.End User (EU): entity to whom a teleaction application service is provided or who is affected by that applicationservice.End User Terminal (EUT): device (or location of a device) that, depending on the application (e.g. by monitoring ofsubdevices):-on the basis of local conditions or by interrogation, generates information and presents this information fortransmission by the network to a Service Provider (SP);-receives information from a SP in order to affect local conditions;-upon polling requests received from a Teleaction Management Function (TMF) executes the requested localactions (e.g. authorization, functionality checks, etc.) and sends appropriate responses to the TMF.NOTE 1:Authorization and functionality checks are outside the scope of the present document.EU access capability: telecommunication means used between an EUT and a TMF (e.g. ISDN bearer service, dedicatedconnection, etc.).Integrated Services Digital Network (ISDN): see CCITT Recommendation I.112 [3] subclause 2.3 definition 308.network: DSS1 protocol entity at the network side of the user network interface.Service Provider (SP): entity which, by using one or more TMFs, provides a teleaction application service to one ormore EUs.NOTE 2:The SP may be the BNP, the TMFP, or another organization responsible for one or more SPTs.Service Provider Terminal (SPT): device (or location of such a device) which, depending on the application:-receives information from one or more EUTs for handling and processing in accordance with the applicationservice offered by the SP;-generates control messages and information requests and presents that information for transmission to one ormore EUTs;-monitors EUTs on the network, either by retrieving EUT status information stored in TMFs, and/or by receivingstatus information automatically from TMFs (e.g. alarms);-receives polling requests from TMFs and sends appropriate responses to the TMF. Execution of local proceduressuch as authorization and functionality check is outside the scope of the present document;-transfers to the TMF information to be broadcasted to the EUTs, if the broadcast functionality is supported by theTMF.SPT access capability: telecommunication means used between a SPT and a TMF (e.g. ISDN bearer service, dedicatedconnection, etc.).SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)9service; telecommunication service: see CCITT Recommendation I.112 [3] subclause 2.2 definition 201.supplementary service: see CCITT Recommendation I.210 [4] subclause 2.4.teleaction application: one specific end to end application offered by a service provider using the teleaction service.teleaction service: teleaction service is the transport mechanism used by a teleaction application.teleservice: see CCITT Recommendation I.112 [3], subclause 2.2, definition 203.Teleaction Management Function (TMF): set of network functions added to either the public ISDN or assigned to aseparate public, or private, network entity. The tasks of the TMF are:-to ensure reliable communication paths between the EUTs and the SPT, i.e. to ensure available and secure accessfor the EUTs to the network and communication paths for the SPT in the ISDN, respectively;-authorization of connected EUTs/SPTs;-EUT/SPT functionality check;-to address the appropriate EUT/SPT for transfer of information generated by SPT/EUT;-as a TMFP option, to broadcast appropriate EUTs for transfer of information generated by a SPT.Teleaction Management Function Provider (TMFP): entity responsible for the installation and maintenance of one ormore of the TMFs. A TMFP may be the same as the BNP.user: DSS1 protocol entity at the user side of the user network interface.3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:BNPBasic Network ProviderBRABasic Rate AccessBRFBasic Routing FunctionalCCATCall Control Agent for TeleactionCEIConnection Endpoint IdentifierCRFConnection Related FunctionCSPDNCircuit Switched Public Data NetworkDFDatabase FunctionalDLCIData Link Connection IdentifierDSS1Digital Subscriber Signalling System No. oneEUEnd UserEUTEnd User TerminalFHFrame HandlerFRFFrame Routing FunctionISDNIntegrated Services Digital NetworkLAPDLink Access Procedure for the D channelLELocal ExchangeLICLink Identification CodeNT1Network Termination type 1NT2Network Termination type 2OSIOpen System InterconnectionPFHPrivate Frame HandlerPHPacket HandlerPICSProtocol Implementation Conformance StatementPLLPre-allocated Logical LinkPMBSPacket Mode Bearer ServicePRAPrimary Rate AccessPSPDNPacket Switched Public Data NetworkPSTNPublic Switched Telephone NetworkSIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)10PTNPrivate Telecommunications NetworkSAPIService Access Point IdentifierSPService ProviderSPTService Provider TerminalTATerminal AdapterTEITerminal Endpoint IdentifierTMFTeleaction Management FunctionTMFPTeleaction Management Function Provider4DescriptionTeleaction is a service providing for reliable, low volume, data communication and allied processing to users. TheTeleaction bearer service may be used for applications such as monitoring, indicating, controlling and verifying ofremote events, operations, and measurements.Teleaction is applicable to both basic rate and primary rate, access.The service provides a datalink layer service over which, by means of a suitable convergence protocol, the OSIconnectionless-mode network service may operate. An explicit indication (SAPI = 12) is used at the data link layer toidentify a teleaction communication. This indication is used to filter the teleaction frames, from other frames which mayco-exist on the interface e.g. call-control frames (SAPI = 0) and packet data frames (SAPI = 16). Once filtered, theframes can be directed towards a TMF. The method of filtering used by the network is outside the scope of the presentdocument. The network uses a network-internal frame address structure (DLCI) to uniquely identify both SPTs, andEUTs, to the TMF. Routing of frames is based upon the Data Link Connection Identifier (DLCI).A network may be comprised of multiple TMFs, and multiple SPs. Figure 1 illustrates some typical access scenarios thatcan exist in a network. The figure is not exhaustive, but illustrates a possible network implementation where there aremultiple SPs. It is possible that within the TMF "cloud", multiple TMFs could exist.TMFleased-linenetworkTE1NT1FHFHNT1NT2TE1TE1PFHNT2LELELENT1SPTNT1FHTE1EUTEUTEUTSPTFHNT2TE1NT1LELESPTNT1TE1SPTLECase 1Case 4Case
3Case
2Case 7Case 6Case 5Case 8Figure 1: Teleaction access scenariosSIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)11The access scenarios presented are:Case 1:EUT connected to S/T reference point.Case 2:EUT connected to S reference point.Case 3:EUT connected to S reference point but with a Frame Handler (FH) within the private network. The PFHis connected by a semipermanent B channel to the TMF.Case 4:EUT connected to S reference point, with a FH within the private network, and the PFH connected to theTMF via a leased-line.Case 5:SPT connected to S/T reference point.Case 6:SPT connected to S/T reference point, but with semipermanent B channel connection to TMF.Case 7:SPT connected to S reference point (D or semipermanent B channel connections possible).Case 8:SPT connected via leased-line to the TMF.NOTE 1:The TMF being implemented in the local exchange is not shown in figure 1, but is a possibility.One EUT is logically associated with only one SPT.NOTE 2:The context where an EUT communicates with several SPTs is outside the scope of the present document.Of the three different methods of layer 2 activation defined in ETS 300 049 [8] (semipermanent, on demand fixed TEI(PLL), on demand variable TEI), only two are applicable to teleaction. Where either of these methods are used, the TEIvalue shall lie in the non-automatic range [0-63].4.1Semi-permanent accessFor semi-permanent access, logical links between an EUT and a TMF, or between a SPT and a TMF, are allocated atsubscription time. The network shall keep the access connection in the established state. Layer 2 addresses at the user-network interface are allocated at subscription time.4.2PLL accessFor PLL access, D channel logical links between an EUT and a TMF, or between a SPT and a TMF, are permanentlyallocated on a subscription basis, but they can be activated and deactivated (SABME/DISC) on demand. The activation,or deactivation, of the link may be initiated by either endpoint. Layer 2 addresses at the user-network interface areallocated at subscription time.5Reference configuration and protocol architecture5.1Reference configurationThe teleaction bearer service consists of interaction between 3 essential entities: the EUT, the TMF and the SPT. As anabstraction of an actual instance of the service, these entities may be considered as part of functional planes. The EUplane and the SP plane can only communicate with each other by passing through the TMF plane. This is illustrated infigure 2.The figure illustrates the possibility for multiple EUTs to communicate with individual SPTs, over a single connectionto the TMF. The TMF is shown as being able to route the calls from EUTs to an SPT. Further, multiple SPTs may becontactable over the one link from the TMF.SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)12Service Provider PlaneManagement Plane(TMF)End user PlaneEUT1EUT2SPT1SPT3SPT2EUT3Figure 2: Abstract instance of the teleaction bearer serviceFigure 3 illustrates the possibilities for realization of the TMF function within the TMF plane. The TMF may be locatedin a single physical location (option A), possibly being duplicated for reliability reasons. The TMF may implementvarious layers of the OSI reference model. The implementation of these layers is application and system dependent. Thepossibility exists for particular higher layer functions to be centralized in a particular location within the TMF plane, andfor lower layer functions to be distributed (option B). The extent to which this can be accomplished is outside the scopeof the present document.Layers 4-7, higher level functionslayers 1+2, basic frame routing functionInternal view of TMF Planeoption Aoption B(optional) layer 3 protocolfor routingFigure 3: Possible options for realization of the TMF function within the TMF planeSIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)13Irrespective of the application, the TMF shall perform a routing function between the EUT and its associated SPT. Thisrequires a minimum implementation of layers 1 and 2 to perform frame routing, and in some particular circumstances, alayer 3 protocol for additional routing information. This Frame Routing Function (FRF) may be performed in acentralized manner, or may be integrated into local exchanges. The FRF receives frames which have been multiplexedby a Frame Handler (FH) in accordance with clause 9 of ETS 300 099 [11]. This allows for the possibility that the FRFmay route both teleaction and D channel CCITT Recommendation X.25 [5] traffic. The frames are multiplexed ontochannels termed Bd channels. Where a group of such channels exist between a FH and the TMF, it is referred to as aBd bundle.TENTcall controlETS
300 402frame handlerframe DeMuxsapi=12,16sapi=0CRF-PPH-2PH-1CRF-P
TMFCRF-SCRF-Ssapi=12sapi=16SPT-1SPT-nFRFCRF-SBd bundlePHIPHIBd bundleBd bundleNTNTTMF
=
Teleaction Management FunctionSPT
=
Service Provider TerminalPH
=
Packet HandlerPHI
=
Packet Handler InterfaceFRF
=
Frame Routing FunctionCRF
=
Connection Related FunctionCRF-S =
CRF to which subscribers are connectedCRF-P =
CRF physically connected to the PHBd channelsDirectlyconnectedSPTBd channel via leased lineor semipermanent B channelFHSPT-1 and SPT-n accessthe teleaction service via D channelFigure 4: Centralized Frame Routing Function architectureSIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)14ETS 300 402call controlTEFHFHsapi=0sapi=12sapi=16CRF-PCRF-PPH - 1PH - 2PHIPHIBd bundleBd bundleTMFCRF-SCRF-SSPT-1SPT-nNTNTBd bundleBd bundleBd bundleCRF-SNTIntegrated Frame Routing PrincipleFHBd channel via leased lineor semipermanent B channelDirectlyconnectedSPTFigure 5: Integrated FRF Architecture5.2Protocol architecture for realizing the teleaction teleserviceFigure 6 illustrates a possible protocol architecture for implementation of the teleaction teleservice. Differentpossibilities exist depending on the applications supported and the mode of connection of the SPT to the TMF. Thefigure does not describe the possibilities that may exist where application dependent protocols could be, or areterminated in the TMF e.g. for authentication of users etc. In these cases the TMF protocol may incorporate some or allof the application protocol stacks implemented in the EUT and SPT.SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)15PHY1L2L3L2L2*L2*L2*L2L2L3L3PHY1PHY1PHY1PHY2PHY2PHY2L4L5L6L7L4L5L6L7peer-to-peer protocolsEUTFHTMFFHSPTPHY1L2L3L2L2*L2*PHY1PHY3PHY2PHY2PHY3L4L5L6L7L2*L3L4L5L6L7peer-to-peer protocolsEUTFHTMFSPTPHY3Case 2: SPT accesses service via direct connection to TMF (leased-line, or semipermanent B channel)Case 1: SPT accesses service via D channelFigure 6: Possible protocol architectures for teleaction depending on SPT access connectionPHY1:Physical layer - ETS 300 011 [6], ETS 300 012 [7].PHY2: Physical layer used between FH and TMF, typically based upon a 64 kbit/s timeslot of a G.703transmission system.PHY3:Physical layer for leased-line connection. This is network specific.L2:LAPD layer 2 protocol, ETS 300 402-2 [10].L2*:LAPD layer 2 protocol extended (LAPD-E) ETS 300 099 [11].L3:Layer 3 protocol e.g. CCITT Recommendation X.25 [5], OSI CLNP [16], IP [17].L4-L7:Layers 4 to 7 higher layer protocols.NOTE:The scenario illustrated in Case 2 represents the TMF being remote from the FH. Where the TMF isintegrated with the FH, then the protocol stacks of the FH and TMF would be merged.For Case 1 in figure 6, the TMF implements a layer 3 protocol between itself and the SPT. This arises because the SPTis not directly connected to the TMF. When the SPT is accessing the teleaction bearer service over the D channel, thenthe LAPD-E protocol between a FH in the LE serving the SPT, and the TMF, only indicates the DLCI of the SPT. ForCase 1, there is no mechanism whereby the LAPD can route frames to/from the SPT, which also contain the address ofthe EUT. Hence a layer 3 protocol for routing is required. This is not necessary between TMF and EUT as the TMF caninclude in LAPD-E frames, which it routes to an EUT, the DLCI of the EUT.Additional information relating to functional entities and information flows is contained in annex B.SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)166Operational requirements6.1Provision and withdrawalThe provision of the teleaction bearer service shall be by prior arrangement with the Basic Network Provider (BNP), ona subscription basis. The teleaction bearer service shall be withdrawn at the EU's or SP's request, or for administrativereasons.6.2Requirements at the service provider network sideWhere the SPT is using D channel access, the network shall register the DLCI of the SPT, with the TMF. The networkshall register whether the procedures of clause 9 or clause 10 of the present document shall apply.As a network option, the connection(s) between SPT and TMF may be configured as a permanent or semipermanentBd channel, or Bd bundle. In this case, the procedures of ETS 300 099 [11], clause 9 shall apply. The SPT and TMFshall bilaterally agree on a fixed DLCI value to be used for addressing local communications between SPT and TMFe.g. for alarm reporting.As a TMFP option, a broadcast function may be supported. The SPT shall register with the TMF if it requires use ofsuch a function. If a broadcast function with multiple outstanding broadcast requests if offered by the TMFP, then theTMF and SPT shall agree on the maximum number of requests that may be outstanding.6.3Requirements at the service provider user sideWhen PLL or semipermanent access to the TMF from the SPT is being used, the SP shall register the TEI of the SPTwith the network.6.4Requirements at the end-user network sideThe network shall register the DLCI of the EUT with the TMF and the SPT. The network shall register whether theprocedures of clause 9 or clause 10 of the present document shall apply.NOTE:Some networks may require the EU to register the speed at which the EUT will operate.6.5Requirements at end-user user sideThe EU shall register the TEI of the EUT with the network.7Coding requirements7.1Coding principlesThe LAPD frame structure and frame types (commands and responses) as defined in ETS 300 402-2 [10] apply. Toperform additional maintenance functions, necessary to enhance the reliability of the data link service offered to theteleaction user, some additional frame formats are defined below.The maintenance flow is applicable for semipermanent and PLL access. Support of the maintenance flow is mandatoryfor both network and subscriber equipment. This maintenance flow is based on the use of UI frames with SAPI value 12and is intended for logical connectivity checking, fault location and alarm reporting along the logical link path. Theprocedures associated with use of these frames are described in clause 13.SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)177.1.1Maintenance frame layoutsThe format of LAPD UI frames for the maintenance flow is described in figure 7 for the ISDN access. The format isidentical for LAPD-E except that the address field is 4 octets in length.87654321Bits/OctetsFlag011111101 AddressfieldSAPI001100C02TEI13 Controlfield000P = 000114ManagementEntityIdentifier0001000156MessageN-3FCS1st octetN-2FCS2nd octetN-1Flag01111110NFigure 7: Format of UI frames for the maintenance flow on the D channel7.1.2Message FormatThree messages are defined: LOOP REQUEST, LOOP RESPONSE, and REPORT.In a message, the information element Message type shall always appear first. The remaining information elements shallappear in ascending order, determined by the value of their information element identifiers, and as shown in thetables 1, 2 and 3.7.1.2.1LOOP REQUESTThe LOOP REQUEST message is sent by the originator of the loop. Table 1 defines the LOOP REQUEST messagecontent and each information element.Table 1: LOOP REQUEST message contentInformation elementReference (subclause)DirectionTypeLengthMessage type7.1.3.1n->uM1Loop originator7.1.3.3n->uM3Loop destination7.1.3.4n->uM3Diagnostic7.1.3.5n->uO3Test data7.1.3.8n->uO2-* (see note)NOTE:The maximum length is (N201 - 12) octets.SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)187.1.2.2LOOP RESPONSEThe LOOP RESPONSE message is a reply to a LOOP REQUEST message. Table 2 defines the LOOP RESPONSEmessage content and each information element.Table 2: LOOP RESPONSE message contentInformation elementReference (subclause)DirectionTypeLengthMessage type7.1.3.1u->nM1Loop originator7.1.3.3u->nM3Loop destination7.1.3.4u->nM3Diagnostic7.1.3.5u->nM3Test data7.1.3.8u->nO2-*(see note)NOTE:The maximum length is (N201 - 12) octets.7.1.2.3REPORTThe REPORT message is used to indicate to the TMF, EUT or SPT that an alarm event has occurred, that a broadcast isrequested or that status information relating to an EUT is requested or provided. Table 3 defines the REPORT messagecontent and each information element.Table 3: REPORT message contentInformation elementReference (subclause)DirectionTypeLengthMessage type7.1.3.1bothM1DLCIETS 300 099 [11]bothO (see note 1)6 Diagnostic7.1.3.5bothO3 Report type7.1.3.6 bothM3 Terminal data7.1.3.7bothO2-*(see note 2)NOTE 1: Mandatory if the message is generated by an EUT. The TMF inserts the DLCI of the originating EUTbefore passing the REPORT to the SPT. Absence of the information element indicates that the TMFor SPT has originated the message.NOTE 2: The maximum length is (N201 - 15) octets when the DLCI is included.7.1.3Information elements codingThe information element structure follows that of the basic call protocol EN 300 403-1 [12], and consists of aninformation element identifier octet, followed by a length octet followed by the content, except for the Message typeinformation element which is a single octet in length.OctetsInformation element identifier1Length2Content
3-*Figure 8: Structure of information elementsTable 4: Information element identifierInformation elementBit87654321LengthDLCI000000016Loop originator000100013Loop destination000100103Diagnostic000100113Report type000101003Terminal data000101012-*Test data000101102-*SIST EN 301 145-1:2000

ETSIEN 301 145-1 V1.1.4 (1999-03)197.1.3.1Message typeThe purpose of the Message type is to identify the function of the message being sent.The message type is coded as shown in figure 9 and table 5, and is a single octet in length. Bit 8 is reserved for possiblefuture use as an extension bit.Bit87654321Octet0
Message type1Figure 9: Message typeTable 5: Message TypesBits8 7 6 5 4 3 2 10 0 0 0 0 0 0 0- escape to nationally specific message type; see note.0 0 0 0 1 0 0 1- LOOP REQUEST0 0 0 0 1 0 1 0- LOOP RESPONSE0 0 0 0 1 0 1 1- REPORTNOTE:When used, the Message type is defined in the following octet(s), according to the national specification.7.1.3.2DLCIThe DLCI information element identifies the originator of the REPORT message, when sent from EUT to SPT. Thisinformation element is 6 octets in length. The format of the information element is identical to the DLCI informationelement descri
...