SIST EN 301 668-2:2001
(Main)Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification
- Abstract
PICS for part 1
- Status
- Published
- Publication Date
- 31-Jan-2001
- Technical Committee
- SPS - Signalling protocols and switching
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Feb-2001
- Due Date
- 01-Feb-2001
- Completion Date
- 01-Feb-2001
SIST EN 301 668-2:2001 is the Slovenian adoption of the ETSI standard for Intelligent Network Application Protocol (INAP) Capability Set 1 (CS1) extension. It specifies the Protocol Implementation Conformance Statement (PICS) proforma for the INAP CS1 extension, so a supplier can declare which CAMEL Phase 2 protocol capabilities are implemented. In practice, it is used to document and check conformance of implementations against the protocol specification in EN 301 668-1.
What does SIST EN 301 668-2:2001 specify?
SIST EN 301 668-2:2001 specifies the PICS proforma for the core INAP CS1 extension and the guidance needed to complete it. The document is organized as four clauses - Scope, References, Definitions and abbreviations, and Conformance - followed by one normative annex.
Annex A is the practical heart of the standard. It contains the PICS questionnaire, the completion guidance, implementation and protocol identification fields, and tables for physical entities, external interfaces, application contexts, operations, arguments, results and errors, timers, range constants, detection points, and SCCP addressing.
What are the key requirements of SIST EN 301 668-2:2001?
SIST EN 301 668-2:2001 requires the completed PICS to be technically equivalent to the proforma in Annex A and to preserve its numbering, naming, and order. That matters because a PICS only has conformance value if it follows the same structure as the standard.
How does the proforma use status and support markings?
Annex A.1.2 defines the meaning of the status and support columns. The status codes distinguish mandatory, optional, not applicable, prohibited, qualified optional, and conditional items, while the support column records whether the implementation supports an item.
This matters in practice because each answer must match the item’s status. For example, a mandatory item must be marked supported, while a prohibited item must not be marked as used.
How are protocol items treated for invokers and responders?
Annex A.1.3 states that mandatory protocol items must be supported by both operation invokers and responders. Optional protocol items are optional for invokers but mandatory for responders, unless CAMEL makes them mandatory for invokers as well.
The same clause also explains that network-specific options are optional for both sides, and that ASN.1 CHOICE items are handled differently in request and indication columns. For a buyer or test lab, this tells you which side of the protocol you must implement and which side you may leave out.
What must be identified in the PICS?
Annex A.2 requires identification of the implementation, the system under test, the product supplier, the client, and a contact person. This gives traceability for the declaration and makes it possible to link the PICS to a specific product version and configuration.
What does the global conformance statement check?
Annex A.4.1 asks whether all mandatory capabilities are implemented. A “No” answer means the implementation is non-conforming, and any missing mandatory capability must be identified and explained.
What does Annex A cover technically?
Annex A.4 covers the actual protocol content that must be declared, including physical entities, external interfaces, application contexts, operations, timers, and range constants. It also includes operation-specific tables for items such as ApplyCharging, CallInformationReport, Connect, EstablishTemporaryConnection, EventReportBCSM, PlayAnnouncement, PromptAndCollectUserInformation, RequestReportBCSMEvent, ResetTimer, and SendChargingInformation.
For some operations, the annex marks them as not applicable for CAMEL. That tells implementers where the CAMEL profile narrows the broader core INAP set.
What terms does SIST EN 301 668-2:2001 define?
Implementation Conformance Statement (ICS) - A statement from the supplier describing which capabilities of a specification are implemented.
ICS proforma - A questionnaire form that becomes an ICS when completed for a specific implementation or system.
Protocol ICS (PICS) - An ICS that applies to an implementation or system claimed to conform to a protocol specification.
Implementation Under Test (IUT) - The implementation being assessed for conformance.
System Under Test (SUT) - The system that contains the IUT and is being described for conformance purposes.
Service Switching Function (SSF) - The IN function used in the document’s abbreviations and protocol tables.
Service Control Function (SCF) - The IN function that controls services and appears throughout the application contexts and operation tables.
Who uses SIST EN 301 668-2:2001?
SIST EN 301 668-2:2001 is used by suppliers of INAP and CAMEL implementations, telecom equipment vendors, system integrators, operators, and test laboratories. They use it to complete conformance statements, compare supported protocol capabilities, and prepare conformance test documentation.
Quality managers and buyers use it to check whether a product supports the specific INAP CS1 extension capabilities they need. Engineers use it to map implementation features to the standard’s operation, timer, and parameter tables.
Which standards are used with SIST EN 301 668-2:2001?
- EN 301 668-1 - the protocol specification for CAMEL Phase 2; this proforma applies to its requirements.
- ETS 300 374-1 - the core INAP CS1 protocol specification that underlies the extension.
- ISO/IEC 9646-1 - the general conformance testing methodology and framework.
- ISO/IEC 9646-7 - the rules for Implementation Conformance Statements and the guidance used here.
- ETS 300 374-2 - the earlier core INAP PICS proforma, used as an editorial basis for this document.
What does the SIST EN 301 668-2:2001 document contain?
SIST EN 301 668-2:2001 contains a questionnaire-style PICS annex rather than a protocol description. The annex gives implementation identification fields, support tables, conditional rules, and value ranges so a supplier can record exactly what is implemented.
It also contains operation-by-operation tables for arguments, results, and errors, plus timer tables and range constants for field lengths and identifiers. The additional tables for trigger detection points and SCCP addressing support practical conformance checking and interoperability work.
The document is therefore useful both as a declaration form and as a checklist for protocol conformance review, testing, and procurement assessments.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 301 668-2:2001 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification". This standard covers: PICS for part 1
PICS for part 1
SIST EN 301 668-2:2001 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 668-2:2001 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentno omrežje (IN) - Razširitev prvega nabora zmožnosti inteligentnega omrežja (CS1) - Aplikacijski protokol inteligentnega omrežja (INAP) - 2. del: Izjava o skladnosti izvedbe protokola (PICS) - Proforma specifikacijeIntelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 668-2 Version 1.1.3SIST EN 301 668-2:2001en01-februar-2001SIST EN 301 668-2:2001SLOVENSKI
STANDARD
ETSIEN301668-2V1.1.3(2000-07)EuropeanStandard(Telecommunicationsseries)IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1)extension;IntelligentNetworkApplicationProtocol(INAP);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecificationSIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)2ReferenceDEN/SPS-03053-2KeywordsIN,INAP,ISDN,mobile,PICSETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.74Conformance.7AnnexA(normative):PICSproformaforcoreINAPCS1.8A.1GuidanceforcompletingthePICSproforma.8A.1.1Purposeandstructure.8A.1.2Symbols,abbreviationsandterms.8A.1.3InstructionsforcompletingthePICSproforma.10A.2Identificationoftheimplementation.11A.2.1Dateofthestatement.11A.2.2ImplementationUnderTest(IUT)identification.11A.2.3SystemUnderTest(SUT)identification.11A.2.4Productsupplier.11A.2.5Client.12A.2.6PICScontactperson.12A.3Identificationoftheprotocol.13A.4PICSproformatables.13A.4.1Globalstatementofconformance.13A.4.2Physicalentities.13A.4.3Externalinterfaces.14A.4.4Applicationcontexts.15A.4.5Operations.16A.4.6Arguments,resultsanderrors.17A.4.6.1ActivateServiceFiltering.17A.4.6.2ActivityTest.17A.4.6.3ApplyCharging.18A.4.6.4ApplyChargingReport.19A.4.6.5AssistRequestInstructions.21A.4.6.6CallGap.22A.4.6.7CallInformationReport.23A.4.6.8CallInformationRequest.24A.4.6.9Cancel.25A.4.6.10CollectInformation.26A.4.6.11Connect.26A.4.6.12ConnectToResource.28A.4.6.13Continue.29A.4.6.14DisconnectForwardConnection.30A.4.6.15EstablishTemporaryConnection.31A.4.6.16EventNotificationCharging.32A.4.6.17EventReportBCSM.33A.4.6.18FurnishChargingInformation.34A.4.6.19InitialDP.35A.4.6.20InitiateCallAttempt.37A.4.6.21PlayAnnouncement.38A.4.6.22PromptAndCollectUserInformation.41SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)4A.4.6.23ReleaseCall.43A.4.6.24RequestNotificationChargingEvent.43A.4.6.25RequestReportBCSMEvent.44A.4.6.26ResetTimer.46A.4.6.27SendChargingInformation.48A.4.6.28ServiceFilteringResponse.49A.4.6.29SpecializedResourceReport.49A.4.7Timers.50A.4.8Rangeconstants.52A.4.9Additionaltables.54A.4.9.1Detectionpoints.54A.4.9.2SCCPAddressing.55Bibliography.56History.57SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart2ofamulti-partENcoveringtheINCapabilitySet1(CS1)extension;IntelligentNetworkApplicationProtocol(INAP);CustomizedApplicationsforMobilenetworkEnhancedLogic(CAMEL)Phase2asdescribedbelow:Part1:"ProtocolspecificationforCamelPhase2";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification".NOTE:Furtherpartsofthepresentdocumentmaybeidentifiedlater.NationaltranspositiondatesDateofadoptionofthisEN:7July2000DateoflatestannouncementofthisEN(doa):31October2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30April2001DateofwithdrawalofanyconflictingNationalStandard(dow):30April2001SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)61ScopeThepresentdocumentprovidestheImplementationConformanceStatement(ICS)proformaforthecoreIntelligentNetworkApplicationProtocol(INAP)ofIntelligentNetwork(IN)CapabilitySet1(CS1)definedinETS300374-1[2]extendedbytheIntelligentNetworkApplicationProtocol(INAP)ofIntelligentNetwork(IN)CapabilitySet1(CS1)extensiondefinedinEN301668-1[1]incompliancewiththerelevantrequirements,andinaccordancewiththerelevantguidancegiveninISO/IEC9646-7[4].ETS300374-2[5]wastakenasaneditorialbasisforthepresentdocument.EnhancementsandmodificationsinrespecttoEN301668-1[1]arecoveredbyappropriateupdatesofexistingtablesorbynewtables.FortheCAMELcapabilityonlyarestrictedsubsetoftheprotocolaspectsofETS300374-1[2]isnecessary.Theserestrictionsarecoveredinthepresentdocumenttoo.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301668-1(V1.2):"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1)extension;IntelligentNetworkApplicationProtocol(INAP);Part1:ProtocolspecificationforCamelPhase2".[2]ETSIETS300374-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part1:Protocolspecification".[3]ISO/IEC9646-1(1994):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part1:Generalconcepts".[4]ISO/IEC9646-7(1995):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part7:ImplementationConformanceStatements".[5]ETSIETS300374-2:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecificationforServiceSwitchingFunction(SSF),SpecializedResourceFunction(SRF)andServiceControlFunction(SCF)".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:-termsdefinedinEN301668-1[1];-termsdefinedinISO/IEC9646-1[3]andinISO/IEC9646-7[4].SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)7Inparticular,thefollowingtermsdefinedinISO/IEC9646-1[3]apply:ImplementationConformanceStatement(ICS):statementmadebythesupplierofanimplementationorsystemclaimedtoconformtoagivenspecification,statingwhichcapabilitieshavebeenimplemented.TheICScantakeseveralforms:protocolICS,profileICS,profilespecificICS,informationobjectICS,etc.ICSproforma:document,intheformofaquestionnaire,whichwhencompletedforanimplementationorsystembecomesanICS.ProtocolICS(PICS):ICSforanimplementationorsystemclaimedtoconformtoagivenprotocolspecification.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ACApplicationContextASEApplicationServiceElementBCSMBasicCallStateModelCS1CapabilitySet1ICSImplementationConformanceStatementINIntelligentNetworkINAPIntelligentNetworkApplicationProtocolIPIntelligentPeripheralIUTImplementationUnderTestPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementSCFServiceControlFunctionSCPServiceControlPointSCSSystemConformanceStatementSRFSpecializedResourceFunctionSSFServiceSwitchingFunctionSSPServiceSwitchingPointSUTSystemUnderTestWithinthepresentdocumentthetermsgsmSSFandSSFandthetermsgsmSCFandSCFrespectivelyareusedsynonymously.4ConformanceIfitclaimstoconformtothepresentdocument,theactualPICSproformatobefilledinbyasuppliershallbetechnicallyequivalenttothetextofthePICSproformagiveninannexA,andshallpreservethenumbering/namingandorderingoftheproformaitems.APICSwhichconformstothepresentdocumentshallbeaconformingPICSproformacompletedinaccordancewiththeinstructionsforcompletiongiveninannexA,clauseA.1.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)8AnnexA(normative):PICSproformaforcoreINAPCS1Notwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePICSproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPICS.A.1GuidanceforcompletingthePICSproformaA.1.1PurposeandstructureThepurposeofthisPICSproformaistoprovideamechanismwherebyasupplierofanimplementationoftherequirementsdefinedinEN301668-1mayprovideinformationabouttheimplementationinastandardizedmanner.ThePICSproformaissubdividedintoclausesforthefollowingcategoriesofinformation:-instructionsforcompletingtheICSproforma;-identificationoftheimplementation;-identificationoftheprotocol;-PICSproformatables;-globalstatementofconformance;-physicalentities;-externalinterfaces;-applicationcontexts;-operations;-arguments,resultsanderrors;-timers;-rangeconstants.A.1.2Symbols,abbreviationsandtermsThePICSproformacontainedinthisannexiscomprisedofinformationintabularforminaccordancewiththeguidelinespresentedinISO/IEC9646-7.ThetablenumberingisinaccordancewithETS300374-1andnotcontinuous.ItemcolumnTheitemcolumncontainsanumberwhichidentifiestheiteminthetable.ItemdescriptioncolumnTheitemdescriptioncolumndescribesinfreetexteachrespectiveitem(e.g.parameters,timers,etc.).Itimplicitlymeans"issupportedbytheimplementation?".SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)9StatuscolumnThefollowingnotations,definedinISO/IEC9646-7,areusedforthestatuscolumn:mmandatory-thecapabilityisrequiredtobesupported;ooptional-thecapabilitymaybesupportedornot;n/anotapplicable-inthegivencontext,thecapabilitycannotbeused;xprohibited(excluded)-thereisarequirementnottousethiscapabilityinthegivencontext;o.iqualifiedoptional-formutuallyexclusiveorselectableoptionsfromaset."i"isanintegerwhichidentifiesanuniquegroupofrelatedoptionalitemsandthelogicoftheirselectionwhichisdefinedimmediatelyfollowingthetable;ciconditional-therequirementonthecapability("m","o","x"or"n/a")dependsonthesupportofotheroptionalorconditionalitems."i"isanintegeridentifyinganuniqueconditionalstatusexpressionwhichisdefinedimmediatelyfollowingthetable.Fornestedconditionalexpressions,thesyntax"IF.THEN(IF.THEN.ELSE.)ELSE."isusedtoavoidambiguities.ReferencecolumnEntriesinthereferencecolumnrefertosubclausesofEN301668-1,exceptwhereexplicitlystatedotherwise.SinceEN301668-1isadeltadocumenttoETS300374-1,clauseswhicharemissinginEN301668-1canbefoundinETS300374-1.NOTE:Areferenceindicatesonlythelocationofthemostessentialinformationaboutanitem.AlladditionalrequirementscontainedinEN301668-1havealsotobetakenintoaccountwhenmakingastatementabouttheconformanceofthatparticularitem.SupportcolumnThesupportcolumnshallbefilledinbythesupplieroftheimplementation.Thefollowingcommonnotations,definedinISO/IEC9646-7,areusedforthesupportcolumn:Yorysupportedbytheimplementation;Nornnotsupportedbytheimplementation;N/A,n/aor-noanswerrequired(allowedonlyifthestatusisn/a,directlyorafterevaluationofaconditionalstatus).NOTE:AsstatedinISO/IEC9646-7,supportforaProtocolDataUnit(PDU)requirestheabilitytoparseallvalidparametersofthatPDU.SupportingaPDUwhilehavingnoabilitytoparseavalidparameterisnon-conformant.SupportforaparameteronaPDUmeansthatthesemanticsofthatparameteraresupported.IfthisPICSproformaiscompletedinordertodescribeamultiple-profilesupportinasystem,itisnecessarytobeabletoanswerthatacapabilityissupportedforoneprofileandnotsupportedforanother.Inthatcase,thesuppliershallentertheuniquereferencetoaconditionalexpression,precededby"?"(e.g.?3).Thisexpressionshallbegiveninthecellprovidedatthebottomofthetable.ItusespredicatesdefinedintheSystemConformanceStatement(SCS),eachofwhichreferstoasingleprofileandwhichtakesthevalueTRUEifandonlyifthatprofileistobeused.EXAMPLE:?3:IFprof1THENYELSEN.Itisfurtherpossibletoprovidecommentstoanansweratthebottomofeachtable.ValuesallowedcolumnThevaluesallowedcolumncontainsthevaluesortherangesofvaluesallowed.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)10ValuessupportedcolumnThevaluessupportedcolumnshallbefilledinbythesupplieroftheimplementation.Inthiscolumn,thevaluesortherangesofvaluessupportedbytheimplementationshallbeindicated.ReferencestoitemsForeachpossibleitemanswer(answerinthesupportcolumn)withinthePICSproformaexistsauniquereference,used,forexample,intheconditionalexpressions.Itisdefinedasthetableidentifier,followedbyasoliduscharacter"/",followedbytheitemnumberinthetable.Ifthereismorethanonesupportcolumninatable,thecolumnsshallbediscriminatedbyletters(a,b,etc.),respectively.EXAMPLE1:A.5/4isthereferencetotheanswerofitem4intable5ofannexA.EXAMPLE2:A.6/3bisthereferencetothesecondanswer(i.e.inthesecondsupportcolumn)ofitem3intable6ofannexA.A.1.3InstructionsforcompletingthePICSproformaThesupplieroftheimplementationshallcompletethePICSproformaineachofthespacesprovidedusingthenotationdescribedinsubclauseA.1.2.OptionalitemsinEN301668-1aredealtwithasfollows:-mandatoryprotocolitemsneedtobesupportedbybothoperationinvokersandresponders;-optionalprotocolitemsareoptionalforoperationinvokers,butmandatoryforoperationresponders;theymaybemandatoryalsofortheoperationinvokersifrequiredbytheCAMELcapability;-networkspecificoptionsareoptionalforbothoperationinvokersandresponders.TableA.1givesanoverviewofthisruletabularform.TableA.1ProtocolitemInvokerequestInvokeindicationMandatorymmOptionalomNetworkoptionooAsageneralrule,theASN.1"CHOICE"constructisindicatedintheparametertables:-asanoption(o.x)inthe"Invokerequest"column;-asmandatoryinthe"Invokeindication"column.Whena(ASN.1)parameterwhichcontainsa"SIZE"fieldisnotexplicitlyconstrainedinatable,thenthecompletesizefieldhastobesupported.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)11A.2IdentificationoftheimplementationIdentificationoftheImplementationUnderTest(IUT)andthesysteminwhichitresides(theSystemUnderTest(SUT))shouldbefilledinsoastoprovideasmuchdetailaspossibleregardingversionnumbersandconfigurationoptions.Theproductsupplierinformationandclientinformationshouldbothbefillediniftheyaredifferent.ApersonwhocananswerqueriesregardinginformationsuppliedinthePICSshouldbenamedasthecontactperson.A.2.1Dateofthestatement.A.2.2ImplementationUnderTest(IUT)identificationIUTname:.IUTversion:.A.2.3SystemUnderTest(SUT)identificationSUTname:.Hardwareconfiguration:.Operatingsystem:.A.2.4ProductsupplierName:.Address:.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)12Telephonenumber:.Facsimilenumber:.E-mailaddress:.Additionalinformation:.A.2.5ClientName:.Address:.Telephonenumber:.Facsimilenumber:.E-mailaddress:.Additionalinformation:.A.2.6PICScontactpersonName:.Telephonenumber:.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)13Facsimilenumber:.E-mailaddress:.Additionalinformation:.A.3IdentificationoftheprotocolThisPICSproformaappliestothefollowingstandard.EN301668-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1)extension;IntelligentNetworkApplicationProtocol(INAP);Part1:ProtocolspecificationforCamelPhase2".ThatdocumentisbasedonETS300374-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part1:Protocolspecification".A.4PICSproformatablesAnexplicitanswershallbeentered,ineachofthesupportorsupportedcolumnboxesprovided,usingthenotationdescribedinsubclauseA.1.2.A.4.1GlobalstatementofconformanceAreallmandatorycapabilitiesimplemented?(Yes/No).NOTE:Answering"No"tothisquestionindicatesnon-conformancetotheprotocolspecification.Non-supportedmandatorycapabilitiesaretobeidentifiedinthisPICS,withanexplanationofwhytheimplementationisnon-conforming,onpagesattachedtothePICSproforma.A.4.2PhysicalentitiesTableA.2:PhysicalentitiesItemNameReferenceStatusSupport1SCP4.2n/a2SSP4.2o,13IP4.2o,1o.1:OnlyoneoftheseitemsshallbesupportedpercompletedPICSresponse.Comments:.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)14TableA.3:CapabilitiesItemNameReferenceStatusSupport1SSF-SRF-Relay-function7.3.5c3012Assisting-SSP-capability7.3.5(note)c3023SupportofNorthAmericanCarrierrelatedInformation6.3,9;8.15c303NOTE:SeeETS300374-1,figure25casesc)ande).c301:IFA.2/2THENoELSEn/a--SSPc302:IF(A.2/2ANDA.3/1)THENoELSEn/a--SSPANDSSF-SRF-Relay-functionc303:IF(A.2/2AND"SSPisNorthAmerican.")--SSPandtheSSPisNorthAmericanTHENmELSEn/aComments:.A.4.3ExternalinterfacesTableA.4:ExternalinterfacesItemNameReferenceStatusSupport1SCF-SSF(note)c4012SCF-SRF(note)c402NOTE:Itisassumedthattheindicatedexternalinterfacesarebetweenphysicalentities.c401:IFA.2/2THENmELSEn/a--SSPc402:IFA.2/3THENmELSEn/a--IPComments:.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)15A.4.4ApplicationcontextsTableA.5:ApplicationcontextsItemNameReferenceInitiatorResponderStatusSupportStatusSupport1Core-INAP-CS1-SSP-to-SCP-AC6.5bisn/an/a2Core-INAP-CS1-assist-handoff-SSP-to-SCP-AC6.5bisn/an/a3Core-INAP-CS1-IP-to-SCP-AC6.5bisn/an/a4Core-INAP-CS1-SCP-to-SSP-AC6.5bisn/an/a5Core-INAP-CS1-SCP-to-SSP-traffic-management-AC6.5bisn/an/a6Core-INAP-CS1-SCP-to-SSP-service-management-AC6.5bisn/an/a7Core-INAP-CS1-SSP-to-SCP-service-management-AC6.5bisn/an/a8CAP-v2-gsmSSF-to-gsmSCF-AC6.5bisc501n/a9CAP-v2-assist-gsmSSF-to-gsmSCF-AC6.5bisc503n/a10CAP-v2-gsmSRF-to-gsmSCF-AC6.5bisc505n/ac501:IFA.2/2THENmELSEn/a--SSPc503:IFA.3/2THENmELSEn/a--Assisting-SSP-capabilityc505:IFA.2/3THENmELSEn/a--IPComments:.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)16A.4.5OperationsTableA.6:ApplicationServiceElements(ASEs)ItemNameReferenceInvoke-ReqInvoke-IndStatusSupportStatusSupport1initialDP6.1,6.4,9.19c601n/a2assistRequestInstructions6.1,6.4,9.5c603n/a3establishTemporaryConnection6.1,6.4,9.15n/ac6014disconnectForwardConnection6.1,6.4,9.14n/ac6085connectToResource6.1,6.4,9.12n/ac6096connect6.1,6.4,9.11n/ac6017releaseCall6.1,6.4,9.23n/ac6018eventReportBCSM6.1,6.4,9.17c601n/a9requestReportBCSMEvent6.1,6.4,9.25n/ac60110eventNotificationCharging6.1,6.4,9.16n/an/a11requestNotificationChargingEvent6.1,6.4,9.24n/an/a12collectInformation6.1,6.4,9.10n/an/a13continue6.1,6.4,9.13n/ac60114initiateCallAttempt6.1,6.4,9.20n/an/a15resetTimer6.1,6.4,9.26n/ac60816furnishChargingInformation6.1,6.4,9.18n/ac60117applyChargingReport6.1,6.4,9.4c601n/a18applyCharging6.1,6.4,9.3n/ac60119callGap6.1,6.4,9.6n/an/a20serviceFilteringResponse6.1,6.4,9.28n/an/a21activateServiceFiltering6.1,6.4,9.1n/an/a22callInformationReport6.1,6.4,9.7c601n/a23callInformationRequest6.1,6.4,9.8n/ac60124sendChargingInformation6.1,6.4,9.27n/ac60125specializedResourceReport6.1,6.4,9.29c619n/a26playAnnouncement6.1,6.4,9.21n/ac61927promptAndCollectUserInformation6.1,6.4,9.22n/ac61928cancel6.1,6.4,9.9n/ac61429activityTest6.1,6.4,9.2n/ac614c601:IFA.5/8aTHENmELSEn/a--SSP-to-SCP-AC_Initiatorc603:IFA.5/9a--assist-handoff-SSP-to-SCP-AC_InitiatorORA.5/10aTHENmELSEn/a--IP-to-SCP-AC_Initiatorc608:IFA.5/8a--SSP-to-SCP-AC_InitiatorORA.5/9aTHENmELSEn/a--assist-handoff-SSP-to-SCP-AC_Initiatorc609:IF(A.5/8aANDA.3/1)--SSP-to-SCP-AC_InitiatorANDSSF-SRF-Relay-functionORA.5/9aTHENmELSEn/a--assist-handoff-SSP-to-SCP-AC_Initiatorc614:IFA.5/8a--SSP-to-SCP-AC_InitiatorORA.5/9a--assist-handoff-SSP-to-SCP-AC_InitiatorORA.5/10aTHENmELSEn/a--IP-to-SCP-AC_Initiatorc619:IF(A.5/8aANDA.3/1)--SSP-to-SCP-AC_InitiatorANDSSF-SRF-Relay-functionORA.5/9a--assist-handoff-SSP-to-SCP-AC_InitiatorORA.5/10aTHENmELSEn/a--IP-to-SCP-AC_InitiatorSIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)17Comments:.A.4.6Arguments,resultsanderrorsA.4.6.1ActivateServiceFilteringNotapplicableforCAMEL.A.4.6.2ActivityTestFortheoperationActivityTesttherearenoinvocationarguments,noresultargumentsandnoerrors.TableA.7:VoidTableA.8:VoidSIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)18A.4.6.3ApplyChargingTableA.9:ApplyCharginginvocationargumentsItemNameReferenceInvoke-RequestInvoke-IndicationStatusSupportValueStatusSupportValueAllowedSupportedAllowedSupported1aChBillingChargingCharacteristics6.3n/ac9022timeDurationCharging6.3n/ac9143maxCallPeriodDuration6.3n/ac9101.8640004releaseIfdurationExceed6.3n/ac9105tone6.3n/ac9116extensions6.3,6.6n/ac9127type-localInteger6.3n/an/a8type-globalOBJECTIDENTIFIER6.3n/ac9139criticality6.3n/a0c913010value6.3n/ac91311tariffSwitchInterval6.3n/ac9101.8640012sendCalculationToSCPIndication6.3n/aTruen/aTrue13partyToCharge6.3n/a'01'H,'02'Hc902'01'H,'02'H14extensions6.3,6.6n/ac90615type-localInteger6.3n/an/a16type-globalOBJECTIDENTIFIER6.3n/ac91517criticality6.3n/a0c915018value6.3n/ac915c902:IFA.6/18bTHENmELSEn/a--ApplyCharging-Responderc912:IfA.9/4bTHENoELSEn/ac906:IFA.6/18bTHENoELSEn/a--ApplyCharging-Responderc913:IfA.9/6bTHENmELSEn/ac908:IFA.9/14bTHENmELSEn/ac914:IFA.9/1bTHENmELSEn/ac910:IfA.9/2bTHENmELSEn/ac915:IFA.9/14bTHENmELSEn/ac911:IfA.9/4bTHENmELSEn/aComments:.SIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)19TableA.10:ApplyChargingerrorsItemNameReferenceStatusSupport1missingParameter6.2c10012unexpectedComponentSequence6.2c10013unexpectedParameter6.2c10014unexpectedDataValue6.2c10015parameterOutOfRange6.2c10016systemFailure6.2c10017taskRefused6.2c10018unknownLegID6.2c1001c1001:IFA.6/18bTHENoELSEn/a--ApplyCharging-ResponderComments:.A.4.6.4ApplyChargingReportTableA.11:ApplyChargingReportinvocationargumentsItemNameReferenceInvoke-RequestInvoke-IndicationStatusSupportValueStatusSupportValueAllowedSupportedAllowedSupported1callResult6.3c1101n/a2timeDurationChargingResult6.3c1103n/a3partyToCharge6.3c1104'01'H,'02'Hn/a4timeInformation6.3c1104n/a5timeIfNoTariffSwitch6.3c11060.864000n/a6timeIfTariffSwitch6.3c1106n/a7timeSinceTariffSwitch6.3c11070.864000n/a8tariffSwitchInterval6.3c11080.864000n/a9callActive6.3c1104n/ac1101:IfA.6/17aTHENmELSEn/a--ApplyChargingReport-Invokerc1106:IfA.11/4aTHENmELSEn/aSIST EN 301 668-2:2001
ETSIETSIEN301668-2V1.1.3(2000-07)20c1103:IfA.11/1aTHENmELSEn/ac1107:IfA.11/6aTHENmELSEn/ac1104:IfA.11/2aTHENmELSEn/ac1108:IfA.11/6aTHENoELSEn/aComments:.
...