SIST EN 301 217-2:2001
(Main)V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification
V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification
This ETs defines the PICS proforma specification for the VB5.2 interface specification in compliance with ISO/IEC 9646-1 and -2.
Vmesniki V digitalnega storitvenega vozlišča (SN) - Vmesniki na referenčni točki VB5.2 za podporo širokopasovnih ali kombiniranih ozkopasovnih in širokopasovnih dostopovnih omrežij (AN) - 2. del: Izjava o skladnosti izvedbe protokola (PICS) - Proforma specifikacije
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification35.200Vmesniška in povezovalna opremaInterface and interconnection equipmentICS:Ta slovenski standard je istoveten z:EN 301 217-2 Version 1.1.3SIST EN 301 217-2:2001en01-september-2001SIST EN 301 217-2:2001SLOVENSKI
STANDARD
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)2ReferenceDEN/SPS-09047-2 (b9oi0ie0.PDF)KeywordsPICS, AN, SN, V interface, VB5 interfaceETSIPostal 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 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)3ContentsIntellectual Property Rights.4Foreword.5Introduction.51Scope.62References.63Definitions and abbreviations.73.1Definitions.73.2Abbreviations.84Conformance to this PICS proforma specification.9Annex A (normative):Protocol ICS proforma for EN 301 217-1.10A.1Guidance for completing the PICS proforma.10A.1.1Purposes and structure.10A.1.2Abbreviations and conventions.10A.1.3Instructions for completing the PICS proforma.12A.2Identification of the implementation.12A.2.1Date of the statement.12A.2.2Implementation Under Test (IUT) identification.12A.2.3System Under Test (SUT) identification.13A.2.4Product supplier.13A.2.5Client (if different from product supplier).14A.2.6PICS contact person.14A.3Identification of the protocol.15A.4Global statement of conformance.15A.5Service Node.15A.5.1Main features.15A.5.1.1General.15A.5.1.2ATM layer characteristics.16A.5.1.2.1Broadband access network connection types.16A.5.1.2.2ATM transfer characteristics.16A.5.2VB5.2 reference point.17A.5.2.1Basic characteristics.17A.5.2.1.1Support of a physical interface.17A.5.2.1.2Physical layer at the VB5.1 reference point.17A.5.2.2ATM layer functions.18A.5.2.3ATM adaptation layer.18A.5.2.3.1AAL for the RTMC protocol.18A.5.2.3.2AAL for the B-BCC protocol.18A.5.2.3.3AAL for circuit emulation of 2 048 kbit/s signals.19A.5.2.4RTMC function and protocol.19A.5.2.4.1RTMC main features.19A.5.2.4.2RTMC messages.19A.5.2.4.2.1RTMC messages received by the Service Node.19A.5.2.4.2.2RTMC messages transmitted by the Service Node.20A.5.2.4.3Timers used in RTMC procedures.20A.5.2.4.4RTMC function specific information elements.20A.5.2.5B-BCC function and protocol.21A.5.2.5.1B-BCC main features.21A.5.2.5.2B-BCC messages.21A.5.2.5.2.1B-BCC protocol messages received by the Service Node.21SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)4A.5.2.5.2.2B-BCC protocol messages transmitted by the Service Node.22A.5.2.5.3Timers used in B-BCC procedures.23A.5.2.5.4B-BCC function specific information elements.23A.5.2.5.5B-BCC information elements based on ITU-T Recommendations.24A.5.2.5.6B-BCC information elements supporting ATM-F UNI 4.0 equipment.25A.6Access Network.25A.6.1Main features.25A.6.1.1General.25A.6.1.2ATM layer characteristics.26A.6.1.2.1Broadband access network connection types.26A.6.1.2.2ATM transfer characteristics.26A.6.2Access types.27A.6.2.1Support of ATM based access types.27A.6.2.1.1Basic characteristics.27A.6.2.1.2Physical layer.27A.6.2.1.3ATM layer functions.28A.6.2.2Support of non B-ISDN access types.28A.6.2.3Narrowband access types.28A.6.3VB5.2 reference point.29A.6.3.1Basic characteristics.29A.6.3.2Support of a physical interface.29A.6.3.3Physical layer at the VB5.2 reference point.29A.6.3.4ATM layer functions.30A.6.3.5ATM adaptation layer.30A.6.3.6AAL for the RTMC protocol.30A.6.3.7ATM adaptation layer.30A.6.3.7.1AAL for the RTMC protocol.30A.6.3.7.2AAL for the B-BCC protocol.31A.6.3.7.3AAL for circuit emulation of 2 048 kbit/s signals.31A.6.3.8RTMC function and protocol.31A.6.3.8.1RTMC main features.31A.6.3.8.2RTMC messages.31A.6.3.8.2.1RTMC messages received by the Access Network.31A.6.3.8.2.2RTMC messages transmitted by the Access Network.32A.6.3.8.3Timers used in RTMC procedures.32A.6.3.8.4RTMC function specific information elements.32A.6.3.9B-BCC function and protocol.33A.6.3.9.1B-BCC main features.33A.6.3.9.2B-BCC messages.33A.6.3.9.2.1B-BCC protocol messages received by the Access Network.33A.6.3.9.2.2B-BCC protocol messages transmitted by the Access Network.34A.6.3.9.3Timers used in B-BCC procedures.35A.6.3.9.4B-BCC function specific information elements.35A.6.3.9.5B-BCC information elements based on ITU-T Recommendations.35A.6.3.9.6B-BCC information elements supporting ATM-F UNI 4.0 equipment.37Annex B (informative):Status of OAM functions based F4/F5 flows.38B.1OAM functions at service port (SN-side).38B.2OAM functions at user port.39B.3OAM functions at service port (AN-side).40Annex C (informative):Support of ATM transfer capabilities and QoS classes.42C.1ATM transfer capabilities.42C.2QoS classes.43History.44SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)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 from the ETSI Secretariat. Latest updates are available on the ETSI 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 SignallingProtocol and Switching (SPS).The present document is part 2 of a multi-part EN covering V interfaces at the digital Service Node (SN); Interfaces atthe VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks(ANs), as identified below:Part 1:"Interface specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP)";Part 4:"Abstract Test Suites (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)".National transposition datesDate of adoption of this EN:3 September 1999Date of latest announcement of this EN (doa):31 December 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 2000Date of withdrawal of any conflicting National Standard (dow):30 June 2000IntroductionTo evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities andoptions have been implemented for a telecommunication specification. Such a statement is called a ProtocolImplementation Conformance Statement (PICS).SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)61ScopeThe present document provides the Protocol Implementation Conformance Statement (PICS) proforma for theV interfaces at the digital Service Node (SN) Interfaces at VB5.2 reference point for the support of broadband orcombined narrowband and broadband Access Networks defined in EN 301 217-1 [4] in compliance with the relevantrequirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [6] and ETS 300 406 [2].It details in tabular form the implementation options, i.e. the optional functions additional to those which are mandatoryto implement.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]ETS 300 404 (1997): "Broadband Integrated Services Digital Network (B-ISDN); B-ISDNOperation And Maintenance (OAM) principles and functions".[2]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; Standardization methodology".[3]EN 301 005-1 (V1.1): "V interfaces at the digital Service Node (SN); Interface at the VB5.1reference point for the support of broadband or combined narrowband and broadband AccessNetwork (AN); Part 1: Interface specification".[4]EN 301 217-1 (V1.1): "V interfaces at the digital Service Node (SN); Interfaces at the VB5.2reference point for the support of broadband or combined narrowband and broadband AccessNetworks (ANs); Part 1: Interface specification".[5]ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 1: General concepts".[6]ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection -; Conformancetesting methodology and framework - Part 7: Implementation Conformance Statements".[7]ITU-T Recommendation G.703: "Physical/electrical characteristics of hierarchical digitalinterfaces".[8]ITU-T Recommendation G.957: "Optical interfaces for equipments and systems relating to thesynchronous digital hierarchy".[9]ITU-T Recommendation I.356 (1996): "B-ISDN ATM layer cell transfer performance".[10]ITU-T Recommendation I.371 (1996): "Traffic control and congestion control in B-ISDN".[11]ITU-T Recommendation I.610 (1995): "B-ISDN Operation and maintenance principles andfunctions abstracts".[12]ITU-T Recommendation I.732 (1996): "Functional characteristics of ATM equipment".[13]ITU-T Recommendation Q.967-1: "V-interfaces at the service node (SN): VB5.1 reference pointspecification".SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)7[14]ITU-T Recommendation Q.2931 (1995): "Broadband Integrated Services Digital Network(B-ISDN); Digital subscriber signalling system no. 2 (DSS 2) - User-network Interface (UNI);Layer 3 specification for basic call/connection control".[15]ITU-T Recommendation Q.2961.1 (1995): "Broadband Integrated Services Digital Network(B-ISDN); Digital Subscriber Signalling System No. 2 (DSS2); Additional traffic parameters:Additional signalling capabilities to support traffic parameters for the tagging option and thesustainable cell rate parameter set".[16]ITU-T Recommendation Q.2961.2 (1997): "Digital Subscriber Signalling System No. 2 (DSS 2) -Additional traffic parameters: Support of ATM Transfer capability in the broadband bearercapability information element.[17]ITU-T Recommendation Q.2961.3 (1997): "Digital Subscriber Signalling System No. 2 (DSS 2) -Additional traffic parameters: Signalling capabilities to support traffic parameters for the availablebit rate (ABR) ATM transfer capability".[18]ITU-T Recommendation Q.2961.4 (1997): "Digital Subscriber Signalling System No. 2 (DSS 2) -Additional traffic parameters: Signalling capabilities to support traffic parameters for the ATMBlock Transfer (ABT) ATM transfer capability".[19]ITU-T Recommendation Q.2961.5: "DSS2 cell delay variation tolerance indication".NOTE 1:Not yet published.[20]ITU-T Recommendation Q.2961.6: "Digital Subscriber Signalling System No. 2 (DSS 2) -Additional traffic parameters: Additional signalling procedures for the support of the SBR2 andSBR3 ATM transfer capabilities".NOTE 2:Not yet published.[21]ITU-T Recommendation Q.2962 (1998): "Digital Subscriber Signalling System No. 2 - Connectioncharacteristics negotiation during call/connection establishment phase".[22]The ATM Forum af-tm-0056.000: "Traffic Management Specification 4.0".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following terms and definitions apply:-terms defined in EN 301 217-1 [4] and EN 301 005-1 [3];-terms defined in ISO/IEC 9646-1 [5] and in ISO/IEC 9646-7 [6].In particular, the following terms defined in ISO/IEC 9646-1 [5] apply:Protocol Implementation Conformance Statement (PICS): statement made by the supplier of an implementation orsystem claimed to conform to a given specification, stating which capabilities have been implemented. The ICS can takeseveral forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etcICS proforma: document, in the form of a questionnaire, which when completed for an implementation or systembecomes an ICSProtocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specificationStatic conformance review: review of the extent to which the static conformance requirements are met by theImplementation Under Test (IUT), accomplished by comparing the PICS with the static conformance requirementsexpressed in the relevant standard(s) (see ISO/IEC 9646-1 [5])SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)83.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:AAL1ATM Adaptation Layer type 1AAL5ATM Adaptation Layer type 5ABRAvailable Bit RateABTATM Block TransferAISAlarm Indication SignalANAccess NetworkATCATM Transfer CapabilityATMAsynchronous Transfer ModeB-ANBroadband Access NetworkB-BCCBroadband Bearer Connection ControlB-ISDNBroadband Integrated Services Digital NetworkB-UNIBroadband User Network InterfaceCDVTCell Delay Variation ToleranceDBRDeterministic Bit RateDTDelayed TransmissionEFCIExplicit Forward Congestion IndicationGFCGeneric Flow ControlICSImplementation Conformance StatementIDIdentificationIUTImplementation Under TestLSPLogical Service PortNNINetwork-to-Network InterfaceNPCNetwork Parameter ControlOAMOperations Administration and MaintenancePDHPlesiochronous Digital HierarchyPICSProtocol Implementation Conformance Statementptmpoint to multipointptppoint to pointQoSQuality of ServiceRDIRemote Defect IndicationRTMCReal Time Management Co-ordination (protocol)SBRStatistical Bit RateSCSSystem Conformance StatementSDHSynchronous Digital HierarchySNService NodeSSCFService Specific Co-ordination FunctionSSCOPService Specific Connection Oriented ProtocolSTMSynchronous Transport ModuleSUTSystem Under TestTCTermination ConvergenceUNIUser Network InterfaceUPCUsage Parameter ControlVCVirtual ChannelVCCTVirtual Channel Connection TerminationVCEVirtual Channel EntityVCIVirtual Channel IdentifierVCMEVirtual Channel Multiplex EntityVPVirtual PathVPCVirtual Path ConnectionVPCIVirtual Path Connection IdentifierVPCTVirtual Path Connection TerminationVPEVirtual Path EntityVPIVirtual Path IdentifierVPMEVirtual Path Multiplex EntitySIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)94Conformance to this PICS proforma specificationIf it claims to conform to the present document the actual PICS proforma to be filled in by a supplier shall be technicallyequivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and ordering ofthe proforma items.An PICS which conforms to the present document shall be a conforming PICS proforma completed in accordance withthe guidance for completion given in clause A.1.SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)10Annex A (normative):Protocol ICS proforma for EN 301 217-1Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that usersof the present document may freely reproduce the PICS proforma in this annex so that it can be used for its intendedpurposes and may further publish the completed PICS.A.1Guidance for completing the PICS proformaA.1.1Purposes and structureThe purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of therequirements defined in EN 301 217-1 [4] may provide information about the implementation in a standardized manner.The PICS proforma is subdivided into subclauses for the following categories of information:-guidance for completing the PICS proforma;-identification of the implementation;-identification of the protocol;-global statement of conformance.A.1.2Abbreviations and conventionsThe PICS proforma contained in this annex is comprised of information in tabular form in accordance with theguidelines presented in ISO/IEC 9646-7 [6].Item columnThe item column contains a number which identifies the item in the table.Item description columnThe item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitlymeans "is supported by the implementation?".Status columnThe following notations, defined in ISO/IEC 9646-7 [6], are used for the status column:mmandatory - the capability is required to be supported.ooptional - the capability may be supported or not.n/anot applicable - in the given context, it is impossible to use the capability.xprohibited (excluded) - there is a requirement not to use this capability in the given context.o.iqualified optional - for mutually exclusive or selectable options from a set. "i" is an integer whichidentifies an unique group of related optional items and the logic of their selection which is definedimmediately following the table.ciconditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support ofother optional or conditional items. "i" is an integer identifying an unique conditional statusexpression which is defined immediately following the table.SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)11Reference columnThe reference column makes reference to EN 301 217-1 [4] and EN 301 005-1 [3], except where explicitly statedotherwise.Support columnThe support column shall be filled in by the supplier of the implementation. The following common notations, defined inISO/IEC 9646-7 [6], are used for the support column:Y or ysupported by the implementationN or nnot supported by the implementationN/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditionalstatus)If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be ableto answer that a capability is supported for one profile and not supported for another. In that case, the supplier shallenter the unique reference to a conditional expression, preceded by "?" (e.g. ?3). This expression shall be given in thespace for comments provided at the bottom of the table. It uses predicates defined in the SCS, each of which refers to asingle profile and which takes the value TRUE if and only if that profile is to be used.EXAMPLE 1:?3:IF prof1 THEN Y ELSE NIt is also possible to provide a comment to an answer in the space provided at the bottom of the table.NOTE:As stated in ISO/IEC 9646-7 [6], support for a received PDU requires the ability to parse all validparameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter isnon-conformant. Support for a parameter on a PDU means that the semantics of that parameter aresupported.References to itemsFor each possible item answer (answer in the support column) within the PICS proforma a unique reference exists, used,for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/",followed by the item number in the table. If there is more than one support column in a table, the columns arediscriminated by letters (a, b, etc.), respectively.EXAMPLE 2:A.5/4 is the reference to the answer of item 4 in table 5 of annex A.EXAMPLE 3:A.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in table 6of annex A.Values allowed columnThe values allowed column contains the type, the list, the range, or the length of values allowed. The following notationsare used:-range of values: . ;EXAMPLE 4:5 . 20.-list of values:, , ., ;EXAMPLE 5: 2, 4, 6, 8, 9.EXAMPLE 6:'1101'B, '1011'B, '1111'B.EXAMPLE 7:'0A'H, '34'H, '2F'H.-list of named values:(), (), ., (;EXAMPLE 8:reject(1), accept(2).SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)12-length:size ( . );EXAMPLE 9:size (1 . 8).Values supported columnThe values supported column shall be filled in by the supplier of the implementation. In this column, the values or theranges of values supported by the implementation shall be indicated.Prerequisite lineA prerequisite line takes the form: Prerequisite: .A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to becompleted if the predicate is FALSE.A.1.3Instructions for completing the PICS proformaThe supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, anexplicit answer shall be entered, in each of the support or supported column boxes provided, using the notationdescribed in subclause A.1.2.However, the tables containing in "AN role" subclause shall only be completed for user implementations, and the tablescontaining in "SN role" subclause shall only be completed for network implementations.If necessary, the supplier may provide additional comments in space at the bottom of the tables, or separately on sheetsof paper.More detailed instructions are given at the beginning of the different subclauses of the PICS proforma.A.2Identification of the implementationIdentification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test(SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configurationoptions.The product supplier information and client information should both be filled in if they are different.A person who can answer queries regarding information supplied in the PICS should be named as the contact person.A.2.1Date of the statement.A.2.2Implementation Under Test (IUT) identificationIUT name:.IUT version:.SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)13A.2.3System Under Test (SUT) identificationSUT name:.Hardware configuration:.Operating system:.A.2.4Product supplierName:.Address:.Telephone number:.Facsimile number:.E-mail address:.Additional information:.SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)14A.2.5Client (if different from product supplier)Name:.Address:.Telephone number:.Facsimile number:.E-mail address:.Additional information:.A.2.6PICS contact person(A person to contact if there are any queries concerning the content of the PICS)Name:.Telephone number:.Facsimile number:.E-mail address:.Additional information:.SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)15A.3Identification of the protocolThis PICS proforma applies to the following standard:EN 301 217-1 (V1.1): "V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for thesupport of broadband or combined narrowband and broadband Access Networks (ANs); Part 1: Interface specification".A.4Global statement of conformanceAre all mandatory capabilities implemented? (Yes/No).NOTE:Answering "No" to this question indicates non-conformance to the protocol specification. Non-supportedmandatory capabilities are to be identified in the PICS, with an explanation of why the implementation isnon-conforming, on pages attached to the PICS proforma.A.5Service NodeIn the tables below only those functions have been specified as "mandatory" which have to be supported in order toensure the proper operation of the VB5.2 interface. Functions marked as optional are not required by the VB5.2interface itself but may be required by an AN- or SN-specification.Subclauses shown in the "Reference" column of all following tables refer to EN 301 217-1 [4] if marked by [4] or toEN 301 005-1 [3] if marked by [3].A.5.1Main featuresA.5.1.1GeneralTable A.1: Main featuresItemFeatureReferenceStatusSupport1RTMC function11.1 [3]m2B-BCC function11.2 [4]mTable A.2: Service typesItemTypeReferenceStatusSupport1B-ISDN services7.1 [4]o.2012Non B-ISDN ATM based services8.2 [4]o.2013narrowband services via V5.18.3.2 [3]o.2014narrowband services via V5.28.3.2 [3]o.2015narrowband services via V38.3.2 [3]o.2016other non ATM based services8.3.2 [3]o.201o.201:It is mandatory to support at least one of these items.SIST EN 301 217-2:2001
ETSIETSI EN 301 217-2 V1.1.3 (1999-09)16A.5.1.2ATM layer characteristicsA.5.1.2.1Broadband access network connection typesTable A.3: B-AN connection typesItemConnection typeReferenceStatusSupport1Type A VP- ptp connections7.5.1.1 [3]o2Type A VC- ptp connections7.5.1.1 [3]o3Type A VP- ptm connections7.5.1.2 [3]o4Type A VC- ptm connections7.5.1.2 [3]o5Type B VP- ptp connections (note)7.5.2 [3]m6Type B VC- ptp connections (note)7.5.2 [3]m7Type C VC- ptp connections7.5.3.1 [4]o8Type C VC- ptm connections7.5.3.1 [4]o9Type D VP- ptp connections7.6.1 [3]o10Type D VC- ptp connections7.6.1 [3]o11Type D VP- ptm connections7.6.2 [3]o12Type D VC- ptm connections7.6.2 [3]o13Type E VC- ptp connections7.6.2 [3]o14Type E VC- ptm connections7.6.2 [3]oNOTE:Mandatory because of RTMC and B-BCC channel.A.5.1.2.2ATM transfer characteristicsTable A.4: ATM transfer characteristicsItemCharacteristicsReference(subclause)StatusSupport1VP link interconnection function9.7 [3]c.4012VC link interconnection function9.7 [3]c.4023ATM transfer capabilities at the VP level (note 1)5.1 [3]m4QoS classes at the VP level (note 2)12.1 [3]m5Association of ATCs with QoS classes at the VP level(note 5)5.1, 6.3, 12.1 [3]m6ATM transfer capabilities at the VC level (note 3)5.1 [3]m7QoS classes at the VC level (note 4)12.1 [3]m8Association of ATCs with QoS classes at the VC level(note 5)5.1, 6.3, 12.1 [3]mNOTE 1:The support
...








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...