Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 1: Protocol specification for Camel Phase 2

To produce a version of INAP for CS2 Extension in order to cover the protocol procedures for the Camel Phase 2 requirements suitable for implementation in Europe. Close co-operation must be ensured with SMG3 with regard to Camel Phase 2 requirements. The specification should also address aspects of interaction between IN structured networks. The Camel Phase 2 defintions should be fully compatible with the existing CS1 INAP.

Inteligentno omrežje (IN) - Razširitev prvega nabora zmožnosti inteligentnega omrežja (CS1) - Aplikacijski protokol inteligentnega omrežja (INAP) - 1. del: Specifikacija protokola za drugo fazo uporabniških aplikacij za izboljšanje logike mobilnega omrežja (CAMEL)

General Information

Status
Published
Publication Date
31-Jan-2001
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Feb-2001
Due Date
01-Feb-2001
Completion Date
01-Feb-2001

Buy Standard

Standard
EN 301 668-1:2001
English language
46 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.Inteligentno omrežje (IN) - Razširitev prvega nabora zmožnosti inteligentnega omrežja (CS1) - Aplikacijski protokol inteligentnega omrežja (INAP) - 1. del: Specifikacija protokola za drugo fazo uporabniških aplikacij za izboljšanje logike mobilnega omrežja (CAMEL)Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 1: Protocol specification for Camel Phase 233.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 668-1 Version 1.1.3SIST EN 301 668-1:2001en01-februar-2001SIST EN 301 668-1:2001SLOVENSKI
STANDARD



SIST EN 301 668-1:2001



ETSIEN301668-1V1.1.3(2000-07)EuropeanStandard(Telecommunicationsseries)IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1)extension;IntelligentNetworkApplicationProtocol(INAP);Part1:ProtocolspecificationforCamelPhase2SIST EN 301 668-1:2001



ETSIETSIEN301668-1V1.1.3(2000-07)2ReferenceDEN/SPS-03053-1KeywordsIN,INAP,ISDN,mobile,protocolETSI650RoutedesLuciolesF-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-1:2001



ETSIETSIEN301668-1V1.1.3(2000-07)3ContentsIntellectualPropertyRights.7Foreword.71Scope.82References.83Abbreviations.104General.104.1Definitionmethodology.104.2Examplephysicalscenarios.104.3Void.104.4INAPaddressing.104.4.1Void.114.4.2Qualityofserviceparameters.114.4.3SCCPaddressing.114.5DefinitionandusageofLegID.114.6Void.114.7DetectionPoints.124.7.1DPprocessingrules.125ReflectionofTCAPApplicationContext(AC).126Additionalabstractsyntax.126.1Operationtypes.136.2Operationtimers.136.3Datatypes.136.4Void.196.5ApplicationServiceElements.196.5bisApplicationcontexts.196.6Classes.207Void.208Errorprocedures.208.1Operationrelatederrorprocedures.218.1.1Void.218.1.2Void.218.1.3Void.218.1.4Void.218.1.5Void.218.1.6MissingCustomerRecord.218.1.6.1Void.217.1.6.2OperationsSSF->SCF.218.1.7MissingParameter.218.1.7.1Void.218.1.7.2Void.218.1.7.3OperationsSSF->SCF.218.1.8Void.228.1.9Void.228.1.10Void.228.1.11Void.228.1.12Void.228.1.13Void.228.1.14Void.228.1.15Void.228.1.16UnknownLegID.228.1.16.1Void.22SIST EN 301 668-1:2001



ETSIETSIEN301668-1V1.1.3(2000-07)48.1.16.2OperationsSCF->SSF.228.2Entityrelatederrorprocedures.228.2.1ExpirationofTSSF.228.2.1.1Void.228.2.1.2ProceduresSSF->SCF.229Detailedoperationprocedures.229.1Void.239.2Void.239.3ApplyChargingprocedure.239.3.1Generaldescription.239.3.1.1Parameters.239.3.2Void.239.3.3Void.239.3.3.1Normalprocedure.249.3.3.2Errorhandling.249.4ApplyChargingReportprocedure.249.4.1Generaldescription.249.4.1.1Parameters.249.4.2Invokingentity(SSF).259.4.2.1Normalprocedure.259.5AssistRequestInstructionsprocedure.269.5.1Generaldescription.269.5.1.1Parameters.269.6Void.269.7CallInformationReportprocedure.269.7.1Generaldescription.269.7.1.1Parameters.269.7.2Void.269.7.2.1Normalprocedure.269.8CallInformationRequestprocedure.279.8.1Generaldescription.279.8.1.1Parameters.279.9Void.279.10Void.279.11Connectprocedure.279.11.1Generaldescription.279.11.1.1Parameters.279.11.2Void.289.11.3Respondingentity(SSF).289.11.3.1Normalprocedure.289.12ConnectToResourceprocedure.299.12.1Generaldescription.299.12.1.1Parameters.299.13Void.299.14Void.299.15EstablishTemporaryConnectionprocedure.299.15.1Generaldescription.299.15.1.1Parameters.299.15.2Void.309.15.3Void.309.15.3.1Void.309.15.3.2Errorhandling.309.16Void.309.17EventReportBCSMprocedure.309.17.1Generaldescription.309.17.2Invokingentity(SSF).319.17.2.1Normalprocedure.319.17.2.2Errorhandling.319.18FurnishChargingInformationprocedure.319.18.1Generaldescription.31SIST EN 301 668-1:2001



ETSIETSIEN301668-1V1.1.3(2000-07)59.18.1.1Parameters.319.18.2Void.329.18.3Respondingentity(SSF).329.18.3.1Normalprocedure.329.19InitialDPprocedure.329.19.1Generaldescription.329.19.1.1Parameters.329.19.2Invokingentity(SSF).339.19.2.1Normalprocedure.339.19.2.2Errorhandling.339.20Void.349.21PlayAnnouncementprocedure.349.21.1Generaldescription.349.22PromptAndCollectUserInformationprocedure.349.22.1Generaldescription.349.22.1.1Parameters.349.22.2Void.349.22.3Respondingentity(SRF).349.22.3.1Normalprocedure.349.23ReleaseCallprocedure.349.23.1Generaldescription.349.24Void.359.25RequestReportBCSMEventprocedure.359.25.1Generaldescription.359.25.1.1Parameters.369.25.2Void.369.25.3Respondingentity(SSF).369.25.3.1Normalprocedure.369.26Void.369.27SendChargingInformationprocedure.369.27.1Generaldescription.369.27.1.1Parameters.379.27.2Void.379.27.3Respondingentity(SSF).389.27.3.1Normalprocedure.389.27.3.2Errorhandling.3810ServicesassumedfromTCAP.3810.1Normalprocedures.3810.2Void.3810.2.1Void.3810.2.2SSF/SRF-to-SCFmessages.3810.3Void.3910.3.1Void.3910.3.2ReceiptofaTC-BEGINindication.3910.3.3Void.3910.3.4Void.3910.3.5ReceiptofaTC-U-ABORTindication.3910.4Void.3910.5Void.3910.6Void.3910.7Void.3910.8Void.3910.8.1Void.3910.8.2Operationinvocationreceipt.3910.9MappingontoTCservices.4010.9.1Dialoguecontrol.4010.9.1.1Void.4010.9.1.2Void.4010.9.1.3Void.4010.9.1.4Void.40SIST EN 301 668-1:2001



ETSIETSIEN301668-1V1.1.3(2000-07)610.9.1.5Userinformation.4010.9.1.6Void.
...

Questions, Comments and Discussion

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