SIST EN 301 005-2:2000

• Abstract:

  This EN defines the PICS proforma specification for the VB5.1 interface specification in compliance with ISO/IEC 9646-1 and -2.

• Status: Published
• Publication Date: 30-Nov-2000
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2000
• Due Date: 01-Dec-2000
• Completion Date: 01-Dec-2000
• Ref Project: ETSI EN 301 005-2 V1.1.5 (1998-09) - V interfaces at the digital Service Node (SN); Interfaces at the VB5.1 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification

SIST EN 301 005-2:2000 is the Slovenian adoption of ETSI EN 301 005-2 V1.1.5, a European Telecommunications Standard from ETSI. It specifies the Protocol Implementation Conformance Statement (PICS) proforma for the VB5.1 interface at the digital Service Node (SN) for broadband or combined narrowband and broadband Access Networks (ANs). In practice, it is the questionnaire suppliers complete so conformance reviewers can check which capabilities an implementation supports.

What does SIST EN 301 005-2:2000 specify?

SIST EN 301 005-2:2000 specifies the PICS proforma for the VB5.1 interface defined in EN 301 005-1. It gives a standardized way to state implementation options, especially the optional functions that go beyond the mandatory ones.

The document is organized into four clauses and three annexes:

Part	What it covers
Annex A (normative)	PICS proforma for EN 301 005-1, including the tables to complete
Annex B (informative)	Status of OAM functions based on F4/F5 flows
Annex C (informative)	Support of ATM transfer capabilities and QoS classes

Clauses 1 to 4 cover the scope, normative references, definitions and abbreviations, and the rule for conformance to the proforma. For a user, this means the document is not the interface specification itself - it is the form and method used to record conformance to that specification.

What are the key requirements of SIST EN 301 005-2:2000?

SIST EN 301 005-2:2000 requires a completed PICS to be technically equivalent to the proforma in Annex A and to keep the same numbering, naming, and order of items. That matters because conformance checks depend on a one-to-one match between the completed questionnaire and the standard tables.

Annex A sets out how to complete the PICS

Annex A explains how to fill in each table: the item description, the support answer, the allowed values, and any values supported. It uses standard PICS notation such as mandatory, optional, not applicable, prohibited, qualified optional, and conditional. In practice, the supplier must state support clearly for each item, not just describe the product in general terms.

Annex A also requires identification of the implementation, the system under test, the product supplier, and a contact person. That information ties the statement to a specific implementation and helps testers or buyers resolve questions later.

Annex A separates Service Node and Access Network roles

Annex A has separate tables for the Service Node role and the Access Network role, and the guidance says the relevant role tables shall be completed only for the matching implementation type. This matters because some functions are only relevant on one side of the VB5.1 interface.

The Service Node tables cover main features, service types, broadband access network connection types, ATM transfer characteristics, VB5.1 physical and ATM layer options, ATM adaptation layer support, and RTMC procedures, messages, timers, and information elements. The Access Network tables mirror much of this structure. For a reader, this is the core of the document: it shows which interface and protocol capabilities must be declared.

OAM, ATM, and RTMC are treated in detail

Annex B breaks down OAM functions based on F4/F5 flows at the service port, user port, and AN-side service port. Annex C lists ATM transfer capabilities and QoS classes at VP and VC sublayers. In practice, these annexes help the implementer state which monitoring, loopback, traffic, and service-quality functions are actually supported.

What terms does SIST EN 301 005-2:2000 define?

• Protocol Implementation Conformance Statement (PICS) - a statement from the supplier saying which capabilities an implementation supports.
• ICS proforma - a questionnaire-style document that becomes an ICS when completed.
• Protocol ICS (PICS) - an ICS for an implementation or system claimed to conform to a protocol specification.
• Implementation Under Test (IUT) - the implementation whose conformance is being assessed.
• System Under Test (SUT) - the system in which the IUT resides.
• static conformance review - a comparison of the completed PICS with the static conformance requirements in the standard.
• RTMC - Real Time Management Co-ordination, the protocol used in several service node and access network procedures.
• OAM - Operations Administration and Maintenance, used here for F4 and F5 flow functions.

Who uses SIST EN 301 005-2:2000?

SIST EN 301 005-2:2000 is used by suppliers of VB5.1 interface implementations when they prepare conformance statements. It is also used by conformance test labs, reviewers, and quality or procurement teams that need a structured declaration of supported functions.

The standard is relevant to telecommunications equipment work involving SN and AN interfaces, especially where ATM, RTMC, OAM, and related access types are part of the implementation. It supports static conformance review by giving a common checklist for comparing a product against EN 301 005-1.

Which standards are used with SIST EN 301 005-2:2000?

SIST EN 301 005-2:2000 is paired with EN 301 005-1, which contains the interface specification that the PICS refers to. The scope also cites ISO/IEC 9646-1 and ISO/IEC 9646-2 as the conformance-testing basis.

The normative references name ETS 300 406 for testing and specification methodology, ISO/IEC 9646-1 for conformance testing concepts, and ISO/IEC 9646-7 for Implementation Conformance Statements. Together, these references provide the rules for how the proforma is structured and how conformance is expressed.

What does the SIST EN 301 005-2:2000 document contain?

Annex A contains the fill-in tables for implementation identification, protocol identification, global conformance, Service Node functions, Access Network functions, and RTMC-related items. It also includes guidance notes that explain the meaning of the support columns and conditional entries.

Annex B gives the status of individual OAM sub-functions for F4 and F5 flows, including continuity check, performance monitoring, loopback, and activation/deactivation cases. Annex C gives tables for ATM transfer capabilities and QoS classes at VP and VC sublayers.

The main body contains the scope, references, definitions, abbreviations, and the conformance rule for using the proforma. For a user, the document is mainly a structured checklist and declaration form, not a design guide.

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.1 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 005-2 Version 1.1.5SIST EN 301 005-2:2000en01-december-2000SIST EN 301 005-2:2000SLOVENSKI
STANDARD
EN 301 005-2 V1.1.5 (1998-09)European Standard (Telecommunications series)V interfaces at the digital Service Node (SN);Interfaces at the VB5.1 reference point for the support ofbroadband or combined narrowband and broadbandAccess Networks (ANs);Part 2: Protocol Implementation ConformanceStatement (PICS) proforma specificationSIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)2ReferenceDEN/SPS-09046-2 (9b0i0ifc.PDF)KeywordsV interface, PSTN, ISDN, B-ISDN, AN, SN, PICSETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail]://www.etsi.frhttp://www.etsi.orgCopyright 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 1998.All rights reserved.SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)3ContentsIntellectual Property Rights.5Foreword.5Introduction.51Scope.62Normative references.63Definitions and abbreviations.63.1Definitions.63.2Abbreviations.74Conformance to this PICS proforma specification.8Annex A (normative):PICS proforma for EN 301 005-1.9A.1Guidance for completing the PICS proforma.9A.1.1Purposes and structure.9A.1.2Abbreviations and conventions.9A.1.3Instructions for completing the PICS proforma.11A.2Identification of the implementation.12A.2.1Date of the statement.12A.2.2Implementation Under Test (IUT) identification.12A.2.3System Under Test (SUT) identification.12A.2.4Product supplier.13A.2.5Client (if different from product supplier).13A.2.6PICS contact person.14A.3Identification of the protocol.14A.4Global statement of conformance.14A.5Service node.15A.5.1Main features.15A.5.1.1General.15A.5.1.2ATM layer characteristics.15A.5.1.2.1Broadband access network connection types.15A.5.1.2.2ATM transfer characteristics.16A.5.2VB5.1 reference point.16A.5.2.1Basic characteristics.16A.5.2.1.1Support of a physical interface.16A.5.2.1.2Physical layer at the VB5.1 reference point.17A.5.2.2ATM layer functions.17A.5.2.3ATM adaptation layer.17A.5.2.3.1AAL for the RTMC protocol.17A.5.2.3.2AAL for circuit emulation of 2 048 kbit/s signals.18A.5.2.4RTMC function and protocol.18A.5.2.4.1RTMC main features.18A.5.2.4.2RTMC messages.18A.5.2.4.2.1RTMC messages received by the Service Node.18A.5.2.4.2.2RTMC messages transmitted by the Service Node.19A.5.2.4.3Timers used in RTMC procedures.19A.5.2.4.4RTMC function specific information elements.19A.6Access network.20A.6.1Main features.20A.6.1.1General.20A.6.1.2ATM layer characteristics.20A.6.1.2.1Broadband access network connection types.20SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)4A.6.1.2.2ATM transfer characteristics.21A.6.2Access types.21A.6.2.1Support of ATM based access types.21A.6.2.1.1Basic characteristics.21A.6.2.1.2Physical layer.22A.6.2.1.3ATM layer functions.22A.6.2.2Support of non B-ISDN access types.23A.6.2.2.1Narrowband access types.23A.6.3VB5.1 reference point.23A.6.3.1Basic characteristics.23A.6.3.1.1Support of a physical interface.23A.6.3.2Physical layer at the VB5.1 reference point.23A.6.3.3ATM layer functions.24A.6.3.4ATM adaptation layer.24A.6.3.4.1AAL for the RTMC protocol.24A.6.3.4.2AAL for circuit emulation of 2 048 kbit/s signals.24A.6.3.5RTMC function and protocol.25A.6.3.5.1RTMC main features.25A.6.3.5.2RTMC messages.25A.6.3.5.2.1RTMC messages received by the Access Network.25A.6.3.5.2.2RTMC messages transmitted by the Access Network.25A.6.3.5.3Timers used in RTMC procedures.26A.6.3.5.4RTMC function specific information elements.26Annex B (informative):Status of OAM functions based F4/F5 flows.27B.1OAM functions at service port (SN-side).28B.2OAM functions at user port.29B.3OAM functions at service port (AN-side).30Annex C (informative):Support of ATM transfer capabilities and QoS classes.31C.1ATM transfer capabilities.31C.2QoS classes.32History.33SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-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 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 2 of a multi-part standard covering the interfaces at the VB5.1 reference point as describedbelow:Part 1:"Interface specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification".NOTE:Further parts covering conformance testing may be identified later.National transposition datesDate of adoption of this EN:18 September 1998Date of latest announcement of this EN (doa):31 December 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 1999Date of withdrawal of any conflicting National Standard (dow):30 June 1999IntroductionTo 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 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)61ScopeThe present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the interfacesat the VB5.1 reference point for the support of broadband or combined narrowband and broadband Access Networks(ANs) as defined in EN 301 005-1 [1] in compliance with the relevant requirements, and in accordance with the relevantguidance given in ISO/IEC 9646-7 [4] 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.2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case 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]EN 301 005-1 (V1.1): "V interfaces at the digital Service Node (SN); Interfaces at the VB5.1reference point for the support of broadband or combined narrowband and broadband AccessNetworks (ANs); Part 1: Interface specification".[2]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; Standardization methodology".[3]ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 1: General concepts".[4]ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 7: Implementation Conformance Statements".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:-terms defined in EN 301 005-1 [1];-terms defined in ISO/IEC 9646-1 [3] and in ISO/IEC 9646-7 [4].In particular, the following terms defined in ISO/IEC 9646-1 [3] apply:Protocol Implementation Conformance Statement (PICS): a 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, etc.SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)7ICS proforma: a document, in the form of a questionnaire, which when completed for an implementation or systembecomes an ICS.Protocol ICS (PICS): an ICS for an implementation or system claimed to conform to a given protocol specification.static conformance review: a 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 [3]).3.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-ISDNBroadband Integrated Services Digital NetworkB-UNIBroadband User Network InterfaceDBRDeterministic Bit RateDTDelayed TransmissionEFCIExplicit Forward Congestion IndicationGFCGeneric Flow ControlICSImplementation Conformance StatementsIDIdentificationITImmediate TransmissionIUTImplementation 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 PathSIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)8VPCVirtual Path ConnectionVPCIVirtual Path Connection IdentifierVPCTVirtual Path Connection TerminationVPEVirtual Path EntityVPIVirtual Path IdentifierVPMEVirtual Path Multiplex Entity4Conformance 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 annex A, clause A.1.SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)9Annex A (normative):PICS proforma for EN 301 005-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 005-1 [1] 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 [4].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 [4], 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 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)10Reference columnThe reference column makes reference to EN 301 005-1 [1], except where explicitly stated otherwise.Support columnThe support column shall be filled in by the supplier of the implementation. The following common notations, defined inISO/IEC 9646-7 [4], are used for the support column:Y or ysupported by the implementation.N or nnot supported by the implementation.N/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:?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 [4], 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.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: 5 . 20-list of values:, , ., example: 2, 4, 6, 8, 9example:'1101'B, '1011'B, '1111'Bexample:'0A'H, '34'H, '2F'H-list of named values:(), (), ., (example: reject(1), accept(2)-length:size ( . )example:size (1 . 8)SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)11Values 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.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 1:A.5/4 is the reference to the answer of item 4 in table 5 of annex A.EXAMPLE 2: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.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.SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)12A.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:.A.2.3System Under Test (SUT) identificationSUT name:.Hardware configuration:.Operating system:.SIST EN 301 005-2:2000

ETSIEN 301 005-2 V1.1.5 (1998-09)13A.2.4Product supplierName:.Address:.Telephone number:.Facsimile number:.E-mail address:.Additional information:.A.2.5Client (if different from product supplier)Name:.Address:.
...