Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification

PICS for ETS 300 403-1/E2

Digitalno omrežje z integriranimi storitvami (ISDN) – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – Signalizacijska omrežna plast za krmiljenje vodovnega osnovnega klica – 3. del: Izjava o skladnosti izvedbe protokola (PICS) – Proforma specifikacija

General Information

Status
Published
Publication Date
31-Mar-2005
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Apr-2005
Due Date
01-Apr-2005
Completion Date
01-Apr-2005

Buy Standard

Standard
SIST EN 300 403-3 V1.2.2:2005
English language
83 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VSHFLILNDFLMDIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification35.100.30Omrežni slojNetwork layer33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 403-3 Version 1.2.2SIST EN 300 403-3 V1.2.2:2005en01-april-2005SIST EN 300 403-3 V1.2.2:2005SLOVENSKI

STANDARD
SIST EN 300 403-3 V1.2.2:2005

European Telecommunications Standards Institute EN 300 403-3 V1.2.2 (1998-04)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Signalling network layer for circuit-mode basic call control;Part 3: Protocol Implementation ConformanceStatement (PICS) proforma specificationSIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)2ReferenceREN/SPS-05124-3 (3qcr0ipc.PDF)KeywordsISDN, DSS1, layer 3, basic, UNI, PICSETSI SecretariatPostal 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.frhttp://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 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)3ContentsIntellectual Property Rights................................................................................................................................5Foreword............................................................................................................................................................5Introduction........................................................................................................................................................61Scope........................................................................................................................................................72References................................................................................................................................................72.1Normative references.........................................................................................................................................72.2Informative references.......................................................................................................................................73Definitions and abbreviations..................................................................................................................83.1Definitions.........................................................................................................................................................83.2Abbreviations.....................................................................................................................................................84Conformance............................................................................................................................................8Annex A (normative):PICS proforma for EN 300 403-1 and ETS 300 403-2.................................9A.1Guidance for completing the PICS proforma...........................................................................................9A.1.1Purpose and structure.........................................................................................................................................9A.1.2Symbols, abbreviations and conventions...........................................................................................................9A.1.3Instructions for completing the PICS proforma...............................................................................................10A.1.4The PICS proforma tables................................................................................................................................11A.1.4.1Correspondence to a physical interface......................................................................................................11A.1.4.2Structure of the tables.................................................................................................................................11A.1.4.3Complexity of conditions in PDU parameter tables...................................................................................11A.1.4.4Support for received PDU parameters........................................................................................................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...............................................................................................................................................................13A.2.6PICS contact person.........................................................................................................................................14A.3Identification of the protocol.................................................................................................................14A.4Global statement of conformance..........................................................................................................14A.5Roles.......................................................................................................................................................15A.6User........................................................................................................................................................16A.6.1Type of implementation...................................................................................................................................16A.6.2Major capabilities............................................................................................................................................17A.6.3Subsidiary capabilities.....................................................................................................................................19A.6.4Protocol data units...........................................................................................................................................22A.6.4.1Messages received by the user...................................................................................................................22A.6.4.2Messages transmitted by the user...............................................................................................................23A.6.5PDU parameters...............................................................................................................................................24A.6.5.1Information elements in messages received by the user.............................................................................25A.6.5.2Information elements in messages transmitted by the user.........................................................................33A.6.6Timers..............................................................................................................................................................41A.6.7Compatibility information elements structure..................................................................................................42A.6.8Numbering information elements structure......................................................................................................49A.7Network..................................................................................................................................................53A.7.1Type of implementation...................................................................................................................................53A.7.2Major capabilities............................................................................................................................................54A.7.3Subsidiary capabilities.....................................................................................................................................56SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)4A.7.4Protocol data units...........................................................................................................................................59A.7.4.1Messages received by the network.............................................................................................................59A.7.4.2Messages transmitted by the network.........................................................................................................60A.7.5PDU parameters...............................................................................................................................................61A.7.5.1Information elements in messages received by the network.......................................................................62A.7.5.2Information elements in messages transmitted by the network...................................................................68A.7.6Timers..............................................................................................................................................................74A.7.7Compatibility information elements structure..................................................................................................75A.7.8Numbering information elements structure......................................................................................................77Annex B (informative):Differences from PICS proforma for ETS 300 102-1................................81B.1Identification of relevant standards........................................................................................................81B.2Differences.............................................................................................................................................81Annex C (informative):Bibliography...................................................................................................82History..............................................................................................................................................................83SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)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 ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSIWeb server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. Noguarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on the ETSI Webserver) 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 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) signalling network layer for circuit-mode basic call control, as described below:Part 1:"Protocol specification";Part 2:"Specification and Description Language (SDL) diagrams";Part 3:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 4:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 5:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the user";Part 6:"TSS&TP specification for the network";Part 7:"ATS and partial PIXIT proforma specification for the network".Proposed national transposition datesDate of adoption of this EN:3 April 1998Date of latest announcement of this EN (doa):31 July 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 January 1999Date of withdrawal of any conflicting National Standard (dow):31 January 1999SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)6IntroductionTo evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities andoptions have been implemented for a given Open Systems Interconnection (OSI) protocol. Such a statement is called aProtocol Implementation Conformance Statement (PICS).EN 300 403-1 is derived from ITU-T Recommendation Q.931 (1993). However, no PICS proforma exists for thisRecommendation. Therefore, ETSI has created a PICS proforma that is specific to the European environment. ThisPICS proforma reflects the requirements contained in ITU-T Recommendation Q.931 with the modifications applied byEN 300 403-1. This has been done to assist understanding of how the European requirements relate to the requirementscontained within ITU-T Recommendation Q.931 (and in particular, to the options specified in ITU-T RecommendationQ.931 that are selected by EN 300 403-1). In practical terms, this means that a number of capabilities specified byITU-T Recommendation Q.931 appear as items in this PICS proforma with a status more akin to the status that would beexpected in a profile ICS (i.e. out-of-scope (I), prohibited (X)).Annex B of the present document describes the differences between the proforma contained in annex A and theproforma for the earlier version of the DSS1 protocol as specified in ETS 300 102-1 (1990).SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)71ScopeThis third part of EN 300 403 provides the Protocol Implementation Conformance Statement (PICS) proforma for theIntegrated Services Digital Network (ISDN) Digital Subscriber Signalling System No. one (DSS1) protocol signallingnetwork layer for circuit-mode basic call control as specified in EN 300 403-1 [1] and ETS 300 403-2 [2] in compliancewith the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4].The supplier of an implementation that is claimed to conform to EN 300 403-1 [1] and ETS 300 403-2 [2] is required tocomplete a copy of the PICS proforma provided in annex A of the present document and is required to provide theinformation necessary to identify both the supplier and the implementation.2ReferencesReferences 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.2.1Normative references[1]EN 300 403-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[2]ETS 300 403-2 (1995): "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic callcontrol; Part 2: Specification Description Language (SDL) diagrams".2.2Informative references[3]ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 1: General concepts".[4]ISO/IEC 9646-7 (1994): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 7: Implementation Conformance Statements".SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)83Definitions and abbreviations3.1DefinitionsIn addition to the definitions in EN 300 403-1 [1], ETS 300 403-2 [2], ISO/IEC 9646-1 [3] and ISO/IEC 9646-7 [4], thefollowing definitions apply:Implementation Conformance Statement (ICS): A statement made by the supplier of an implementation or systemclaimed to conform to a given specification, stating which capabilities have been implemented. The ICS can take severalforms: protocol ICS, profile ICS, profile specific ICS, and information object ICS (see ISO/IEC 9646-1 [3]).Protocol Implementation Conformance Statement (PICS): An ICS for an implementation or system claimed toconform to a given specification (see ISO/IEC 9646-1 [3]).PICS proforma: A document, in the form of a questionnaire, which when completed for an implementation or systembecomes a PICS (see ISO/IEC 9646-1 [3]).3.2AbbreviationsThe following abbreviations apply:BCBearer Capability information elementDSS1Digital Subscriber Signalling System No. oneHLCHigh Layer Compatibility information elementICSImplementation Conformance StatementISDNIntegrated Services Digital NetworkIUTImplementation Under TestLLCLow Layer Compatibility information elementLLILogical Link IdentifierMFEMultiple Frame EstablishmentNICNetwork Independent ClockOSIOpen Systems InterconnectionPABXPrivate Automatic Branch ExchangePDUProtocol Data UnitPICSProtocol Implementation Conformance StatementSUTSystem Under Test(T)Transparent (PDU parameter)USBSUser Signalling Bearer Service4ConformanceA PICS proforma that conforms to this PICS proforma specification shall be technically equivalent to annex A, and shallpreserve the numbering and ordering of the items in annex A.A PICS that conforms to this PICS proforma specification shall:a)describe an implementation which conforms to EN 300 403-1 [1] and ETS 300 403-2 [2];b)be a conforming PICS proforma, which has been completed in accordance with the instructions for completiongiven in clause A.1; andc)include the information necessary to uniquely identify both the supplier and the implementation.SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)9Annex A (normative):PICS proforma for EN 300 403-1 and ETS 300 403-2Notwithstanding 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.1Purpose and structureThe purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of therequirements defined in EN 300 403-1 [1] and ETS 300 403-2 [2] may provide information in a standardized manner.The PICS proforma is subdivided into clauses as follows:- guidance for completing the various parts of the PICS proforma;- identification of the implementation;- identification of the protocol to which this PICS proforma applies;- global statement of conformance;- questions to determine roles;- questions for the user role; and- questions for the network role.A.1.2Symbols, abbreviations 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 unique reference (a mnemonic plus a number) for each item within the PICS proforma.NOTE:Where possible, backwards compatibility has been maintained between the item references used in thisPICS proforma and those used in the PICS proforma for the earlier version of the DSS1 protocoldescribed in ETS 300 102-1.In general, the same mnemonics have been used in this PICS proforma as in earlier proforma. An additional lower caseletter has been added to differentiate PICS items related to the user role (e.g. MCu) and PICS items related to thenetwork role (e.g. MCn). In earlier PICS proforma both these cases were identified by the same mnemonic (e.g. MC).A further consequence of maintaining backwards compatibility is the appearance of discontinuities in the numeric partof the item reference. There are, for example, PICS items listed as messages transmitted by the network with thereferences "MTn 2" and "MTn 4"; the reference between, "MTn 3" is not used.Item description columnThe item description contains a brief summary of the static requirement for which a support answer is required.SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)10Conditions for status columnThe conditions for status column contains a specification, if appropriate, of the predicate upon which a conditional statusis based.Status columnThe following notations, defined in ISO/IEC 9646-7 [4], are used for the status column:NOTE:To support a capability means that the capability is implemented in conformance to EN 300 403-1 [1] andETS 300 403-2 [2].IIrrelevant or out-of-scope - this capability is outside the scope of the ETS to which this PICSproforma applies and is not subject to conformance testing in this context.MMandatory - the capability is required to be supported.N/ANot Applicable - in the given context, it is impossible to use the capability. No answer in thesupport column is required.OOptional - the capability may be supported or not.O.iqualified optional - for mutually exclusive or selectable options from a set. "i" is an integer thatidentifies an unique group of related optional items and the logic of their selection, defined belowthe table.XeXcluded or prohibited - there is a requirement not to use this capability in a given context.Reference columnExcept where explicitly stated, the reference column refers to the appropriate parts of EN 300 403-1 [1] describing theparticular item. Note, however, that a reference merely indicates the place where the core of a description of an item canbe found. Any additional information contained in EN 300 403-1 [1] and ETS 300 403-2 [2] has to be taken intoaccount when making a statement about the conformance of that particular item.Support columnThe following notation, defined in ISO/IEC 9646-7 [4], is used for the support column:[ ] Yes [ ] NoTick "Yes" if item is supported, tick "No" if item is not supported.[ ] N/ATick "N/A" if the item is "not applicable".Prerequisite lineA prerequisite line takes the form: Prerequisite: .A prerequisite line after a subclause heading or table title indicates that the whole subclause or the whole table is notrequired to be completed if the predicate is FALSE.A.1.3Instructions for completing the PICS proformaThe supplier of the implementation shall complete the PICS proforma. For each row in each PICS proforma table thesupplier shall enter an explicit answer (i.e. by ticking the appropriate "Yes", "No", or "N/A" in each of the supportcolumn boxes provided. Where a support column box is left blank, or where it is marked "N/A" without any tickbox, noanswer is required. If necessary, the supplier may enter additional comments at the end of each table, or separately.More detailed instructions may be found at the beginning of each section of the proforma.SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)11A.1.4The PICS proforma tablesA.1.4.1Correspondence to a physical interfaceThe "implementation" (IUT) about which this PICS proforma asks questions corresponds to a layer 3 implementation ontop of ONE physical interface (i.e. one ISDN Basic access or one ISDN Primary rate access interface structure). If theSUT implements both Basic access and Primary rate access interface structures, and in the case of the Basic access,supports more than one configuration, then a layer 3 PICS shall be created for each type of interface (and for eachconfiguration of each interface) provided by the SUT.A.1.4.2Structure of the tablesThe supplier shall provide answers to the questions concerning the major roles of the IUT and the type of interface(table A.1). The supplier shall then provide answers to the questions relating to the capabilities of the IUT in one of themajor roles as appropriate. The supplier shall also provide answers to the questions relating to the type of interfacesupporting the IUT (the behaviour of the IUT is dependant on the type of interface and its configuration). Apart from theinitial questions to determine roles, the major roles of the IUT - the user role (R 2.1) and the network role (R 2.2), aretreated completely separately in the PICS proforma. It is only necessary to complete the questions for the supported role.The answers to the "type of interface" questions (represented by items R 3.x, R 6.x and R 7.x) condition the answers tothe further questions within each major role (user and network).Clause A.6 concerns the capabilities of the IUT whilst in the user role. Clause A.7 concerns the capabilities of the IUTwhilst in the network role.A.1.4.3Complexity of conditions in PDU parameter tablesThe conditions governing when an individual information element has to be supported in a specific message are quitecomplex. This is particularly so for the Bearer capability, Progress indicator, and High layer compatibility informationelements when they are transmitted by an IUT in the user role. To make the conditions for status easier to understandquestions about these information elements have been split into several sub-items.A.1.4.4Support for received PDU parametersIn the PDU parameter tables (A.6.5 and A.7.5), the PICS proforma asks questions about the information elements(parameters) supported in messages (PDUs) received by the IUT. This subclause explains, in the context ofEN 300 403-1 [1], what "to support a received PDU parameter" means.The requirement that an IUT is able to parse an information element in a received message is already implied byclaiming support for the receipt of that received message. This means that "to support a received PDU parameter"implies more.Information elements in received messages are regarded as either transparent or non-transparent.A non-transparent information element is one that causes the protocol control entity to vary its behaviour in accordancewith the content of the information element. To support a non-transparent information element means an IUT canprocess the received parameter and behave according to the procedures described in EN 300 403-1 [1].An information element is transparent if the actions taken according to its contents are not detectable in the subsequentbehaviour of the protocol (i.e. EN 300 403-1 [1] does not specify the protocol behaviour). To support a transparentinformation element means an IUT can receive the information element concerned and pass it to an appropriateprocessing entity (e.g. call control); the information element is not discarded by the protocol control entity. Non-supportof a transparent information element means the IUT discards it.Where EN 300 403-1 [1], in addition to not specifying the protocol behaviour, does not specify the non-protocolbehaviour, transparent parameters have been allocated the status Irrelevant (I). In such cases the Client may choose notto answer whether or not the IUT supports the item. If the item is claimed to be supported, an explanation shall be givenin the comments field of the table indicating what actions are performed on receipt of the parameter.SIST EN 300 403-3 V1.2.2:2005

EN 300 403-3 V1.2.2 (1998-04)12This PICS proforma considers the Cause, Display, and Keypad facility information elements to be transparent in allcircumstances where they are possible to be received. Other information elements may be transparent in somecircumstances (e.g. High layer compatibility and Low layer compatibility when received by the network). Transparentparameters are marked by "(T)" in the PDU parameter tables.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 to provide as much detail as possible regarding version numbers and configuration options.The product supplier 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............................................................................................................................................................

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.