ETSI ETS 300 347-2 ed.1 (1994-09)
V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS) proforma
V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS) proforma
DE/SPS-03003.6
Signalizacijski protokoli in komutacija (SPS) - Vmesniki "V" pri digitalnih krajevnih centralah (LE) - Vmesnik V5.2 za podporo dostopovnega omrežja (AN) - 2. del: Proformna izjava o skladnosti izvedbe protokola (PICS)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Signalizacijski protokoli in komutacija (SPS) - Vmesniki "V" pri digitalnih krajevnih centralah (LE) - Vmesnik V5.2 za podporo dostopovnega omrežja (AN) - 2. del: Proformna izjava o skladnosti izvedbe protokola (PICS)V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS) proforma33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:ETS 300 347-2 Edition 1SIST ETS 300 347-2:1997en01-november-1997SIST ETS 300 347-2:1997SLOVENSKI
STANDARD
EUROPEANETS 300 347-2TELECOMMUNICATIONSeptember 1994STANDARDSource: ETSI TC-SPSReference: DE/SPS-03003.6ICS:33.080Key words:V interface, V5 interface, LE, AN, PICSSignalling Protocols and Switching (SPS);V interfaces at the digital Local Exchange (LE)V5.2 interface for the support of Access Network (AN)Part 2: Protocol Implementation Conformance Statement (PICS)proformaETSIEuropean 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 1994. All rights reserved.SIST ETS 300 347-2:1997
Page 2ETS 300 347-2: September 1994Whilst 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 347-2:1997
Page 3ETS 300 347-2: September 1994ContentsForeword.5Introduction.51Scope.72Normative references.73Definitions.74Abbreviations.85Conformance.86PICS proforma.96.1Identification of the implementation.96.1.1Implementation Under Test (IUT) identification.96.1.2System Under Test (SUT) identification.96.1.3Product supplier.96.1.4Client.106.1.5PICS contact person.106.2PICS/System Conformance Statement (SCS).116.3Identification of the protocol.116.4Global statement of conformance.116.5Local exchange.126.5.1Main features.126.5.2Protocol.136.5.2.1Layer 1.136.5.2.2Layer 2.146.5.2.3Layer 3.146.5.2.3.1PSTN functions.146.5.2.3.2PSTN protocol.156.5.2.3.3Control protocol.156.5.2.3.4Port control protocol.156.5.2.3.5Common control protocol.166.5.2.3.6BCC protocol.166.5.2.3.7Protection protocol.166.5.2.3.8Link control protocol.166.5.3Protocol data units.176.5.3.1PSTN protocol.176.5.3.1.1Messages.176.5.3.1.2Information elements; general.186.5.3.1.3Information elements; pulse type.196.5.3.1.4Information elements; steady signals.206.5.3.1.5Information elements; cause types.216.5.3.1.6Information elements; informationelement fields.216.5.3.2Control protocol.226.5.3.2.1Messages.226.5.3.2.2Information elements; general.226.5.3.2.3Information elements; port control.226.5.3.2.4Information elements; commoncontrol.236.5.3.3BCC protocol.236.5.3.3.1Messages.236.5.3.3.2Information elements.236.5.3.4Protection switching protocol.24SIST ETS 300 347-2:1997
Page 4ETS 300 347-2: September 19946.5.3.4.1Messages.246.5.3.4.2Information elements.246.5.3.5Link control protocol.246.5.3.5.1Messages.246.5.3.5.2Information elements.246.6Access network.256.6.1Main features.256.6.2Protocol.266.6.2.1Layer 1.266.6.2.2Layer 2.266.6.2.3Layer 3.276.6.2.3.1PSTN protocol.276.6.2.3.2Control protocol.276.6.2.3.3Port control protocol.276.6.2.3.4Common control protocol.276.6.2.3.5BCC protocol.286.6.2.3.6Protection protocol.286.6.2.3.7Link control protocol.286.6.3Protocol data units.296.6.3.1PSTN protocol.296.6.3.1.1Messages.296.6.3.1.2Information elements; general.306.6.3.1.3Information elements; pulse type.316.6.3.1.4Information elements; steady signals.326.6.3.1.5Information elements; cause types.336.5.3.1.6Information elements; informationelement fields.336.6.3.2Control protocol.346.6.3.2.1Messages.346.6.3.2.2Information elements; general.346.6.3.2.3Information elements; port control.346.6.3.2.4Information elements; commoncontrol.356.6.3.3BCC protocol.356.6.3.3.1Messages.356.6.3.3.2Information elements.356.6.3.4Protection switching protocol.366.6.3.4.1Messages.366.6.3.4.2Information elements.366.6.3.5Link control protocol.366.6.3.5.1Messages.366.6.3.5.2Information elements.36Annex A (informative):Instructions for completing the PICS proforma.37A.1Identification of the implementation.37A.2Global statement of conformance.37A.3Main features.37A.4Protocol.37A.5Protocol data units.37Annex B (informative):Bibliography.38History.39SIST ETS 300 347-2:1997
Page 5ETS 300 347-2: September 1994ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 2 of a multi-part standard covering the V5.2 interface as described below:Part 1:"V5.2 interface specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) for the network layer, Access Network(AN) side";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma for the network layer, AN side";Part 5:"TSS&TP for the network layer, Local Exchange (LE) side";Part 6:"ATS and partial PIXIT proforma for the network layer, LE side";Part 7:"TSS&TP for the data link layer";Part 8:"ATS and partial PIXIT proforma for the data link layer";Part 9:"Test specification for the physical layer".Transposition datesDate of latest announcement of this ETS (doa):31 December 1994Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 June 1995Date of withdrawal of any conflicting National Standard (dow):30 June 1995IntroductionTo evaluate conformance of a particular implementation, it is necessary to have a statement of whichcapabilities and options have been implemented for a given Open Systems Interconnection (OSI)protocol. Such a statement is called a Protocol Implementation Conformance Statement (PICS).NOTE: It is however possible to use this ETS to indicate the basic requirements for an AccessNetwork (AN) or a Local Exchange (LE) required by a network operator. Specificrequirements need to be added, e.g. the Public Switched Telephone Network (PSTN)port characteristics and conditions.SIST ETS 300 347-2:1997
Page 6ETS 300 347-2: September 1994Blank pageSIST ETS 300 347-2:1997
Page 7ETS 300 347-2: September 19941ScopeThis second part of ETS 300 347 defines the Protocol Implementation Conformance Statement (PICS)proforma for the implementation flexibility allowed for a V5.2 interface defined in ETS 300 347-1 [2] andthe complementary standard ETS 300 324-1 [1]. It allows either the Network Operator to formulate therequirements for V5.2 interface implemented in an Access Network (AN) or a Local Exchange (LE), or todecide whether an implementation meets these requirements. It details in tabular form the implementationoptions, i.e. the optional functions additional to those which are mandatory to implement.This ETS is in compliance with the relevant requirements and in accordance with the relevant guidancegiven in ISO/IEC 9646-7 [4].2Normative referencesThis ETS incorporates by dated and 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 the latestedition of the publication referred to applies.[1]ETS 300 324-1 (1994): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.1 interface for the support of AccessNetwork (AN); Part 1: V5.1 interface specification".[2]ETS 300 347-1 (1994): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.2 interface for the support of AccessNetwork (AN); Part 1: V5.2 interface specification".[3]ISO/IEC 9646-1: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 1: General concepts".[4]ISO/IEC 9646-7: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 7: ImplementationConformance Statements".3DefinitionsFor the purposes of this ETS, the following definitions apply:Protocol Implementation Conformance Statement (PICS): a statement made by the supplier of anOpen Systems Interconnection (OSI) implementation or system, stating which capabilities have beenimplemented for a given OSI protocol (see ISO/IEC 9646-1 [3]).PICS proforma: a document, in the form of a questionnaire, designed by the protocol specifier orconformance test suite specifier, which when completed for an OSI implementation or system becomesthe PICS (see ISO/IEC 9646-1 [3]).Static conformance review: a review of the extent to which the static conformance requirements are metby the Implementation Under Test (IUT), accomplished by comparing the PICS with the staticconformance requirements expressed in the relevant standard(s) (see ISO/IEC 9646-1 [3]).SIST ETS 300 347-2:1997
Page 8ETS 300 347-2: September 19944AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ANAccess NetworkANDBoolean "and"CConditional requirements (to be observed if the relevant conditions apply)DTMFDual Tone Multiple FrequencyIDIdentificationIUTImplementation Under TestLELocal ExchangeMMandatory requirements (these are to be observed in all cases)N/ANot supported, not applicable or the conditions for status are not metNoNot supportedNOTAbsence of the itemNT1Network Termination 1OOption (may be selected to suit the implementation, provided that anyrequirements applicable to the option are observed)O.nOptions, but support required for either at least one or only one of the options inthe group labelled with the same numeral "n"ORBoolean "or"OSIOpen Systems InterconnectionPICSProtocol Implementation Conformance StatementPSTNPublic Switched Telephone NetworkSCSSystem Conformance StatementSUTSystem Under TestTSTime SlotYesSupported5ConformanceThe supplier of a protocol implementation which is claimed to conform to ETS 300 347-1 [2] and toETS 300 324-1 [1] as appropriate is required to complete a copy of the PICS proforma provided in thisETS and is required to provide the information necessary to identify both the supplier and theimplementation.SIST ETS 300 347-2:1997
Page 9ETS 300 347-2: September 19946PICS proformaNotwithstanding the provisions of the copyright Clause related to the text of this ETS, ETSI grants thatusers of this ETS may freely reproduce the PICS proforma in this Clause so that it can be used for itsintended purposes and may further publish the completed PICS.6.1Identification of the implementation6.1.1Implementation Under Test (IUT) identificationIUT name:.IUT version:.6.1.2System Under Test (SUT) identificationSUT name:.Hardware configuration:.Operating system:.6.1.3Product supplierName:.Address:.Telephone number:.SIST ETS 300 347-2:1997
Page 10ETS 300 347-2: September 1994Facsimile number:.Additional information:.6.1.4ClientName:.Address:.Telephone number:.Facsimile number:.Additional information:.6.1.5PICS contact personName:.Telephone number:.Facsimile number:.SIST ETS 300 347-2:1997
Page 11ETS 300 347-2: September 1994Additional information:.6.2PICS/System Conformance Statement (SCS)Provide the relationship of the PICS with the SCS for the system:.6.3Identification of the protocolThis PICS proforma applies to the following standards:ETS 300 347-1 (1994): "Signalling Protocols and Switching (SPS); V interfaces at the digital LocalExchange (LE), V5.2 interface for the support of Access Network (AN); Part 1: V5.2 interfacespecification", and the complementary standard ETS 300 324-1 [1].6.4Global statement of conformanceThe implementation described in this PICS meets all the mandatory requirements of the referencedStandard.[
] Yes[
] NoNOTE:Answering "No" to this question indicates non-conformance to the protocolspecification. Non-supported mandatory capabilities are to be identified in the PICS,with an explanation of why the implementation is non-conforming.SIST ETS 300 347-2:1997
Page 12ETS 300 347-2: September 1994ETS 300 347-1 [2] is based on ETS 300 324-1 [1] and contains only the additional requirements for theV5.2 interface. This ETS, however, provides the complete PICS proforma for the V5.2 interface andtherefore makes reference to both ETSs in the conformance statement tables.Index names in the following tables are identical for identical statements in ETS 300 324-2; for statementswhich are not identical to ETS 300 324-2, instead of letters "M", "P" and "U" the letters "N", "R" and "V" areused for the respective index designations.6.5Local exchange6.5.1Main featuresSubclauses shown in the "Reference" column of table 1 refer to ETS 300 347-1 [2], unless followed by [1],indicating reference to ETS 300 324-1 [1].Table 1IndexProtocol capability descriptionDoes the implementation support .Condition for statusStatusReferenceSupport(Yes/No)N11ISDN-BA-Ports?O.16.1.2 [1][
]Yes
[
]NoN12ISDN-PRA-Ports?O.16.1.3[
]Yes
[
]NoM2PSTN-Ports?O.16.1.1 [1][
]Yes
[
]NoN31Bearer channel connection?M7.3,17[
]Yes
[
]NoN32Semipermanent leased lines?O7.3[
]Yes
[
]NoN33Pre-connected bearer channel?O7.3[
]Yes
[
]NoN41Communication path definition?M8.4.1-3[
]Yes
[
]NoN411C-path(s) for p-type data?N11 OR N12NOT (N11OR N12)MN/A8.4.1 a), 8.4.3[
]Yes
[
]NoN412C-path(s) for f-type data?N11 OR N12NOT (N11OR N12)MN/A8.4.1 b), 8.4.3[
]Yes
[
]NoN413C-path(s) for Ds-type data?N11 OR N12NOT (N11OR N12)MN/A8.4.1 c), 8.4.3[
]Yes
[
]NoN414C-path for PSTN signalling?M2NOT M2MN/A8.4.1 d), 8.4.2[
]Yes
[
]NoN415C-path for control?M8.4.1 e)[
]Yes
[
]NoN416C-path for bearer channel connection?M8.4.1 g)[
]Yes
[
]NoN417C-path for protection?N9NOT N9MN/A8.4.1 h)[
]Yes
[
]NoN418C-path for link control?M8.4.1 f)[
]Yes
[
]NoN421Logical Communication channelprovisioning?M7.2.2[
]Yes
[
]NoN422Logical to physical Communication channelallocation by provisioning?M7.2.2 5)[
]Yes
[
]NoN43Active Communication channel on TS16 ofprimary link?M7.2.2 3), 8.4[
]Yes
[
]NoN44Standby Communication channel on TS16of secondary link?N9NOT N9MN/A7.2.2 3), 8.4[
]Yes
[
]NoN45Number of physical communicationchannels up to 3 times the number of 2 048kbit/s links?M7.2.2 4), 8.4[
]Yes
[
]NoN46Number of stand-by communicationchannels up to 3?N9NOT N9MN/A18.1.2[
]Yes
[
]NoN47Protection Switching of communicationchannels?N9NOT N9MN/A7.4, 8.4, 18[
]Yes
[
]No(continued)SIST ETS 300 347-2:1997
Page 13ETS 300 347-2: September 1994Table 1 (concluded)IndexProtocol capability descriptionDoes the implementation support .Condition for statusStatusReferenceSupport(Yes/No)M6Envelope Function?M9 [1][
]Yes
[
]NoN71ISDN BA ports only partially provisioned foron demand service (PL service)?N11 AND MX.1NOT (N11 AND MX.1)MN/A7.1.2[
]Yes
[
]NoN72ISDN PRA ports only partially provisionedfor on demand service (PL service)?N12 AND MX.1NOT (N12 AND MX.1)MN/A7.1.3[
]Yes
[
]NoN8Multi slot connectionMX.1NOT MX.1MN/A17.1[
]Yes
[
]NoN9Multiple link V5.2 interfaceMX.1NOT MX.1MN/A7.2.2 1)[
]Yes
[
]NoPredicated imaginary features:MX.1if required by network operatorMX.2if required by national PSTN protocol, seeETS 300 324-1 [1],subclause 13.1.3O.1 = Support of at least one of N11, N12, M26.5.2Protocol6.5.2.1Layer 1Clauses/subclauses shown in the "Reference" column of table 2 refer to ETS 300 347-1 [2], unlessfollowed by [1], indicating reference to ETS 300 324-1 [1].Table 2IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)P1.1layer 1 balanced?MX.1NOT MX.1MN/A4 [1][
]Yes
[
]NoP1.2layer 1 coaxial?MX.1NOT MX.1MN/A4 [1][
]Yes
[
]NoR1.3layer 1 link maintenance requirementsM16.1[
]Yes
[
]NoP1.4detection of loss of signals; 1 ms below 20dB?O.116.1.2[
]Yes
[
]NoP1.5detection of loss of signals;10 consecutive ZEROs?O.116.1.2[
]Yes
[
]NoR1.6link control requirements and procedures?M16.2[
]Yes
[
]NoO.1 = Support of at least one of these items is required.SIST ETS 300 347-2:1997
Page 14ETS 300 347-2: September 19946.5.2.2Layer 2Clauses/subclauses shown in the "Reference" column of table 3 refer to ETS 300 347-1 [2], unlessfollowed by [1], indicating a reference to ETS 300 324-1 [1].Table 3IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)P2.11frame structure for peer to peercommunication?M9.1 [1][
]Yes
[
]NoP2.12format of fields for data link envelop?M9.2 [1][
]Yes
[
]NoP2.13envelope address value for controlprotocol?M10.3.2.3[
]Yes
[
]NoP2.14envelope address value for PSTN protocol?M2NOT M2MN/A10.3.2.3[
]Yes
[
]NoP2.15envelope address value for BCC protocol?M10.3.2.3[
]Yes
[
]NoR2.16envelope address values for ISDN ports?N11 OR N12NOT (N11 OR N12)MN/A9.2.2.2 [1][
]Yes
[
]NoR2.17envelope address value for protectionprotocol?N9NOT N9MN/A10.3.2.3[
]Yes
[
]NoR2.18envelope address value for link controlprotocol?M10.3.2.3[
]Yes
[
]NoP2.2data link sublayer of LAPV5 for controlprotocol?M10 [1][
]Yes
[
]NoP2.3data link sublayer of LAPV5 for PSTNprotocol?M2NOT M2MN/A10 [1][
]Yes
[
]NoR2.4data link sublayer of LAPV5 for bearerconnection control protocol?M10[
]Yes
[
]NoR2.52 data link sublayers of LAPV5 forprotection protocol?N9NOT N9MN/A10[
]Yes
[
]NoR2.6data link sublayer of LAPV5 for link controlprotocol?M10[
]Yes
[
]No6.5.2.3Layer 36.5.2.3.1PSTN functionsSubclauses shown in the "Reference" column of table 4 refer to ETS 300 324-1 [1].Table 4IndexProtocol capabilityDoes the implementation support .Condition for statusStatusReferenceSupport(Yes/No)P3.11Dual Tone Multiple Frequency (DTMF)senders/receivers?M2NOT M2MN/A13.1.2[
]Yes
[
]NoP3.12tone generators?M2NOT M2MN/A13.1.2[
]Yes
[
]NoP3.13announcement?M2NOT M2MN/A13.1.2[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 15ETS 300 347-2: September 19946.5.2.3.2PSTN protocolSubclauses shown in the "Reference" column of table 5 refer to ETS 300 324-1 [1].Table 5IndexProtocol capabilityDoes the implementation support .Condition for statusStatusReferenceSupport(Yes/No)P3.2PSTN protocol entity?M2NOT M2MN/A13.2[
]Yes
[
]NoP3.3PSTN call control entity?M2NOT M2MN/A13.5 - 13.7[
]Yes
[
]No6.5.2.3.3Control protocolSubclauses shown in the "Reference" column of table 6 refer to ETS 300 324-1 [1].Table 6IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)P4.0Control protocol entity?M14.4.4[
]Yes
[
]No6.5.2.3.4Port control protocolSubclauses shown in the "Reference" column of table 7 refer to ETS 300 324-1 [1], unless followed by [2],indicating a reference to ETS 300 347-1 [2].Table 7IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)P4.11ISDN BA user port status indication andcontrol?N11NOT N11MN/A14.1[
]Yes
[
]NoR4.12ISDN PRA user port status indication andcontrol?N12NOT N12MN/A15.3 [2][
]Yes
[
]NoR4.13performance monitoring for ISDN BA userport?N11 AND MX.1NOT (N11 AND MX.1)MN/A14.1.4[
]Yes
[
]NoR4.14performance monitoring for ISDN PRA userport?N12 AND MX.1NOT (N12 AND MX.1)MN/A15.3.4 [2][
]Yes
[
]NoP4.2PSTN user port status indication andcontrol?M2NOT M2MN/A14.2[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 16ETS 300 347-2: September 19946.5.2.3.5Common control protocolSubclauses shown in the "Reference" column of table 8 refer to ETS 300 324-1 [1].Table 8IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)R5.1variant and interface ID control?M14.5[
]Yes
[
]NoR5.2verify re-provisioning?MX.1NOT MX1MNA14.5[
]Yes
[
]NoR5.3re-provisioning synchronisation?MX.1NOT MX1MNA14.5[
]Yes
[
]No6.5.2.3.6BCC protocolClauses/subclauses shown in the "Reference" column of table 9 refer to ETS 300 347-1 [2].Table 9IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)R6.1Bearer Channel Connection?M7.3, 17[
]Yes
[
]NoR6.2Bearer Channel Connection Auditing?M7.3, 17[
]Yes
[
]No6.5.2.3.7Protection protocolClauses/subclauses shown in the "Reference" column of table 10 refer to ETS 300 347-1 [2].Table 10IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)R7.1Protection switching of group 1?N9NOT N9MN/A7.4, 18[
]Yes
[
]NoR7.2Protection switching of group 2?N9NOT N9MN/A7.4, 18[
]Yes
[
]No6.5.2.3.8Link control protocolSubclauses shown in the "Reference" column of table 11 refer to ETS 300 347-1 [2].Table 11IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)R8.1Link control protocol?M16.3[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 17ETS 300 347-2: September 19946.5.3Protocol data units6.5.3.1PSTN protocol6.5.3.1.1MessagesSubclauses shown in the "Reference" column of table 12 refer to ETS 300 324-1 [1].Table 12IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U1.1ESTABLISH?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.2ESTABLISH ACK?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.3SIGNAL?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.4SIGNAL ACK?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.5STATUS?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.6STATUS ENQUIRY?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.7DISCONNECT?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.8DISCONNECT COMPLETE?M2NOT M2MN/A13.3[
]Yes
[
]NoU1.9PROTOCOL PARAMETER?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.3[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 18ETS 300 347-2: September 19946.5.3.1.2Information elements; generalSubclauses shown in the "Reference" column of table 13 refer to ETS 300 324-1 [1].Table 13IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U1.10protocol discriminator?M2NOT M2MN/A13.4.2[
]Yes
[
]NoU1.11layer 3 address?M2NOT M2MN/A13.4.3[
]Yes
[
]NoU1.12pulse notification?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.6.1[
]Yes
[
]NoU1.13line information?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.6.2[
]Yes
[
]NoU1.14state?M2NOT M2MN/A13.4.6.3[
]Yes
[
]NoU1.15autonomous signalling sequence?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.6.4[
]Yes
[
]NoU1.16sequence response?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.6.5[
]Yes
[
]NoU1.17sequence-number?M2NOT M2MN/A13.4.7.1[
]Yes
[
]NoU1.18cadenced-ringing?M2NOT M2MN/A13.4.7.2[
]Yes
[
]NoU1.19pulsed-signal?M2NOT M2MN/A13.4.7.3[
]Yes
[
]NoU1.20steady-signal?M2NOT M2MN/A13.4.7.4[
]Yes
[
]NoU1.21digit-signal?M2NOT M2MN/A13.4.7.5[
]Yes
[
]NoU1.22recognition-time?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.6[
]Yes
[
]NoU1.23enable-autonomous-acknowledge?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.7[
]Yes
[
]NoU1.24disable-autonomous-acknowledge?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.8[
]Yes
[
]NoU1.25cause?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.26resource-unavailable?M2NOT M2MN/A13.4.7.10[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 19ETS 300 347-2: September 19946.5.3.1.3Information elements; pulse typeSubclauses shown in the "Reference" column of table 14 refer to ETS 300 324-1 [1].Table 14IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U1.30pulse type: Pulsed normal polarity?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.31pulse type: Pulsed reversed polarity?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.32pulse type: Pulsed battery on c-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.33pulse type: Pulsed on hook?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.34pulse type: Pulsed reduced battery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.35pulse type: Pulsed no battery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.36pulse type: Initial ring?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.37pulse type: Meter pulse?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.38pulse type: 50 Hz pulse?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.39pulse type: Register recall?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.40pulse type: Pulsed off hook?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.41pulse type: Pulsed b-wire connected toearth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.42pulse type: Earth loop pulse?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.43pulse type: Pulsed b-wire connected tobattery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.44pulse type: Pulsed a-wire connected toearth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.45pulse type: Pulsed a-wire connected tobattery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.46pulse type: Pulsed c-wire connected toearth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.47pulse type: Pulsed c-wire disconnected?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.48pulse type: Pulsed normal battery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.49pulse type: Pulsed a-wire disconnected?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.50pulse type: Pulsed b-wire disconnected?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 20ETS 300 347-2: September 19946.5.3.1.4Information elements; steady signalsSubclauses shown in the "Reference" column of table 15 refer to ETS 300 324-1 [1].Table 15IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U1.51steady signal: Normal polarity?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.52steady signal: Reversed polarity?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.53steady signal: Battery on c-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.54steady signal: No battery on c-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.55steady signal: Off hook?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.56steady signal: On hook?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.57steady signal: Battery on a-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.58steady signal: A-wire on earth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.59steady signal: No battery on a-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.60steady signal: No battery on b-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.61steady signal: Reduced battery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.62steady signal: No battery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.63steady signal: Alternate reduced power/nopower?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.64steady signal: Normal battery?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.65steady signal: Stop ringing?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.66steady signal: Start pilot frequency?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.67steady signal: Stop pilot frequency?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.68steady signal: Low impedance on b-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.69steady signal: B-wire connected to earth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.70steady signal: B-wire disconnected fromearth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.71steady signal: Normal battery on b-wire?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.72steady signal: Low loop impedance?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.73steady signal: High loop impedance?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.74steady signal: Anomalous loop impedance?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.75steady signal: A-wire disconnected fromearth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.76steady signal: C-wire on earth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoU1.77steady signal: C-wire disconnected fromearth?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.4[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 21ETS 300 347-2: September 19946.5.3.1.5Information elements; cause typesSubclauses shown in the "Reference" column of table 16 refer to ETS 300 324-1 [1].Table 16IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U1.78cause type: Response to status enquiry?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.79cause type: Protocol discriminator error?M2NOT M213.4.7.9[
]Yes
[
]NoU1.80cause type: L3 address error?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.81cause type: Message type unrecognized?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.82cause type: Out of sequence informationelement?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.83cause type: Repeated optional informationelement?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.84cause type: Mandatory information elementmissing?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.85cause type: Unrecognized informationelement?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.86cause type: Mandatory information elementcontent error?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.87cause type: Optional information elementcontent error?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.88cause type: Message not compatible withstate?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.89cause type: Repeated mandatoryinformation element?M2NOT M2MN/A13.4.7.9[
]Yes
[
]NoU1.90cause type: Too many informationelements?M2NOT M2MN/A13.4.7.9[
]Yes
[
]No6.5.3.1.6Information elements; information element fieldsSubclauses shown in the "Reference" column of table 17 refer to ETS 300 324-1 [1].Table 17IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U1.91suppression indicator?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.92acknowledge request indicator?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.3[
]Yes
[
]NoU1.93suppression indicator?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.7[
]Yes
[
]NoU1.94acknowledge request indicator?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.7[
]Yes
[
]NoU1.95digit acknowledge request indicator?M2 AND MX.2NOT (M2 AND MX.2)MN/A13.4.7.5[
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 22ETS 300 347-2: September 19946.5.3.2Control protocol6.5.3.2.1MessagesSubclauses shown in the "Reference" column of table 18 refer to ETS 300 324-1 [1].Table 18IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U2.1common control and port controlmessages?M14.4.1[
]Yes
[
]No6.5.3.2.2Information elements; generalSubclauses shown in the "Reference" column of table 19 refer to ETS 300 324-1 [1].Table 19IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U2.5protocol discriminator?M14.4.2.2[
]Yes
[
]NoU2.6layer 3 addresses?M14.4.2.3[
]Yes
[
]No6.5.3.2.3Information elements; port controlSubclauses shown in the "Reference" column of table 20 refer to ETS 300 324-1 [1], unless followed by[2], indicating a reference to ETS 300 347-1 [2].Table 20IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U3.1FE101 activate access?N11NOT N11MN/A14.4.2.5.4[
]Yes
[
]NoU3.2FE102 activation initiated by user?N11NOT N11MN/A14.4.2.5.4[
]Yes
[
]NoU3.3FE103 DS activated?N11NOT N11MN/A14.4.2.5.4[
]Yes
[
]NoU3.4FE104 access activated?N11NOT N11MN/A14.4.2.5.4[
]Yes
[
]NoU3.5FE105 deactivate access?N11NOT N11MN/A14.4.2.5.4[
]Yes
[
]NoU3.6FE106 access deactivated?N11NOT N11MN/A14.4.2.5.4[
]Yes
[
]NoU4.1FE201/202 unblock?M14.4.2.5.4[
]Yes
[
]NoU4.2FE203/204 block?M14.4.2.5.4[
]Yes
[
]NoU4.3FE205 block request?M14.4.2.5.4[
]Yes
[
]NoU5.1FE206 performance grading?R4.13 OR R4.14NOT (R4.13 OR R4.14)MN/A14.4.2.5.4[
]Yes
[
]NoU5.2FE207 D-channel block?N11 OR N12NOT (N11 OR N12)MN/A14.4.2.5.4[
]Yes
[
]NoU5.3FE208 D-channel unblock?N11 OR N12NOT (N11 OR N12)MN/A14.4.2.5.4[
]Yes
[
]NoV5.4FE209 TE out of service?N12NOT N12MN/A15.3.2 [2][
]Yes
[
]NoV5.5FE210 Failure inside network?N12NOT N12MN/A15.3.2 [2][
]Yes
[
]NoSIST ETS 300 347-2:1997
Page 23ETS 300 347-2: September 19946.5.3.2.4Information elements; common controlSubclauses shown in the "Reference" column of table 21 refer to ETS 300 324-1 [1].Table 21IndexProtocol capabilityDoes the implementation support .Conditions for statusStatusReferenceSupport(Yes/No)U6.1verify re-provisioning?R5.2NO
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...