SIST EN 301 668-1:2001
(Main)Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 1: Protocol specification for Camel Phase 2
- Abstract
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.
- 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-1:2001 is the SIST version of the ETSI standard for Intelligent Network Application Protocol (INAP) support of CAMEL Phase 2. It specifies the protocol additions and modifications needed so that GSM/PLMN network elements can exchange CAMEL Phase 2 signalling in a way that remains compatible with the existing CS1 INAP.
This standard is for implementers of the service control and call control interfaces used by CAMEL. In practice, it tells network and equipment designers how the SCF, SSF and SRF exchange call control, charging and user-interaction information.
What does SIST EN 301 668-1:2001 specify?
SIST EN 301 668-1:2001 specifies the additions to INAP for CAMEL Phase 2 and states that these additions are intended to stay compatible with the existing CS1 INAP. It is based on ETS 300 374-1 and relies on EN 301 668-2 for the CAMEL profile of which protocol aspects are used.
| Annex | What it covers |
|---|---|
| Annex A | Normative mapping between CAMEL and ISUP for call setup and release procedures |
The document is organized into scope, references, abbreviations, general rules, ASN.1 syntax, error procedures, detailed operation procedures, TCAP-related services, and Annex A. That structure matters because the standard separates general protocol rules from the detailed message procedures and from the ISUP mapping used at the network boundary.
What are the key requirements of SIST EN 301 668-1:2001?
SIST EN 301 668-1:2001 keeps CAMEL Phase 2 aligned with CS1 while defining the extra protocol behavior needed for mobile-network services. The most useful requirements for implementation are in clauses 4, 6, 8, 9 and 10.
- Clause 4.2 lists supported physical scenarios for SRF connection handling, including relay, direct SCP-to-IP, and assist cases. This tells an implementer which call-control topologies the protocol is expected to support.
- Clause 4.4 requires CAP to use SCCP services and gives the supported SCCP variants and addressing behavior. In practice, this affects how messages are routed through SS7 and when segmentation or interworking is needed.
- Clause 4.5 fixes LegID use: leg 1 refers to the calling party and leg 2 to the called party. This matters because many operations carry a leg identifier and the wrong leg changes which party is controlled or reported on.
- Clause 4.7 gives detection point processing rules and postconditions after events such as ERBCSM, CIR, ACR and Call Release. This tells the SCF/SSF logic when relationships become control, monitor or idle.
- Clause 6 defines the additional abstract syntax, data types, application service elements, application contexts, and range constants used by CAMEL Phase 2. It also defines encoding rules using ASN.1 and BER, so implementers know how the parameters are coded on the wire.
- Clause 8 defines error handling for cases such as MissingCustomerRecord, MissingParameter, UnknownLegID and TSSF expiry. These rules matter because they tell the SSF how to fall back to default call handling when CAMEL processing fails.
- Clause 9 specifies the procedures for ApplyCharging, Connect, EstablishTemporaryConnection, EventReportBCSM, FurnishChargingInformation, InitialDP, PlayAnnouncement, PromptAndCollectUserInformation, ReleaseCall, RequestReportBCSMEvent and SendChargingInformation. These are the core call-control, charging and user-interaction messages that equipment must implement.
- Clause 10 states how the protocol uses TCAP services and dialogue control. This is important for dialogue setup, user information, and quality-of-service handling in the transaction layer.
What terms does SIST EN 301 668-1:2001 define?
- Customized Applications for Mobile network Enhanced Logic (CAMEL) - The service framework for mobile-network value-added call control that this protocol supports.
- Intelligent Network Application Protocol (INAP) - The signalling protocol used between intelligent network entities such as SCF and SSF.
- Service Control Function (SCF) - The network entity that issues service logic and call-control instructions.
- Service Switching Function (SSF) - The network entity that detects events in the call and reports them to the SCF.
- Specialized Resource Function (SRF) - The entity used for announcement and user-interaction resources.
- Transaction Capabilities Application Part (TCAP) - The SS7 transaction layer used to carry the protocol dialogue.
- Signalling Connection Control Part (SCCP) - The SS7 layer used for routing CAP/INAP messages.
- LegID - The identifier that distinguishes the call legs, with leg 1 for the calling party and leg 2 for the called party.
Who uses SIST EN 301 668-1:2001?
SIST EN 301 668-1:2001 is used by telecom engineers, network vendors, and mobile-network operators who implement CAMEL Phase 2 services. It is also relevant for conformance and integration testing, because it defines the protocol behavior that SCF, SSF and SRF equipment must follow when exchanging charging, routing and user-interaction messages.
Which standards are used with SIST EN 301 668-1:2001?
- ETS 300 374-1 - The CS1 core INAP specification that this standard extends and modifies.
- EN 301 668-2 - The PICS proforma that profiles which CAMEL protocol aspects are used.
- ETS 300 287 - TCAP version 2, used for the transaction services carried by the protocol.
- ETS 300 356-1 - ISUP version 2, used in the normative CAMEL-to-ISUP mapping.
- ETS 300 974 - MAP, used for several GSM-related data encodings and parameters.
- GSM 03.78 and GSM 09.78 - The CAMEL stage 2 and CAP references that shape the service model and protocol behavior.
- ITU-T X.680, X.681, X.682, X.683, X.690 and X.880 - The ASN.1 and remote-operations specifications used for syntax and encoding.
What does the SIST EN 301 668-1:2001 document contain?
The document contains ASN.1 type definitions, operation arguments, extension points, and range constants for CAMEL Phase 2 parameters. It also includes procedure descriptions for charging control, call routing, event reporting, announcement handling and user-input collection.
Clause 9 gives the behavior of the main operations in both normal and error cases, including how the SSF reacts to answer, busy, no answer, disconnect and timer expiry. Annex A provides the CAMEL-to-ISUP mapping for InitialDP, Connect, AssistRequestInstructions, ConnectToResource, EstablishTemporaryConnection and ReleaseCall, which is what implementers need when CAMEL signalling crosses into the circuit-switched call setup path.
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-1: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 1: Protocol specification for Camel Phase 2". This standard covers: 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.
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.
SIST EN 301 668-1: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-1: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) - 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
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.4010.9.1.7Void.4010.9.1.8Qualityofservice.40AnnexA(normative):MappingbetweenCAMELandISUP.41A.1InitialDPoperation.41A.2Connectoperation.41A.3AssistRequestInstructionsoperation.42A.4ConnectToResourceoperation.42A.5EstablishTemporaryConnectionoperation.43A.6ReleaseCalloperation.44Bibliography.45History.46SIST EN 301 668-1:2001
ETSIETSIEN301668-1V1.1.3(2000-07)7IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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).Thepresentdocumentispart1ofamulti-partstandardcoveringtheINCapabilitySet1(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-1:2001
ETSIETSIEN301668-1V1.1.3(2000-07)81ScopeThepresentdocumentspecifiestheadditionsforIntelligentNetworkApplicationProtocol(INAP)tosupporttheCamelPhase2Capability.ThepresentdocumentisbasedonETS300374-1[4].ETS300374-1[4]isalsotakenasaneditorialbasisforthepresentdocument.OnlyadditionsandmodificationsinrespecttothatETSarespecifiedinthepresentdocument.ForCustomizedApplicationsforMobilenetworkEnhancedLogic(CAMEL)Phase2onlyarestrictedsubsetoftheprotocolaspectsofETS300374-1[4]isnecessary.Thisrestrictionisnotdefinedinthepresentdocument.AprofilingofCAMEL,i.e.whichprotocolaspectsareused,isgivenbyEN301668-2[27].ClausesandsubclausesofETS300374-1[4]forwhichneitheradditionsnormodificationsaremadedonotappearinthepresentdocument.However,toensurethesameclausenumberingofthepresentdocumentasofETS300374-1[4],deletedclausesandsubclausesarenumberedimplicitly.AsthepresentdocumentspecifiestheadditionsinrespecttotheSSFitisassumedthattheSCFisaccordingtoETS300374-1[4]takingintoaccounttherequirementsdefinedinthepresentdocumentfortheSSF.TheprotocolspecificationoftheCAMELCapabilitytothepresentdocumentisconsideredasequivalenttoGSM09.78[11].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.ThefollowingreferencesareinadditiontothoseofETS300374-1[4]:[1]ETSIEN301140-1:"IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part1:Protocolspecification".[2]ETSIETS300287:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;TransactionCapabilitiesApplicationPart(TCAP)version2".[3]ETSIETS300356-1:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version2fortheinternationalinterface;Part1:Basicservices[ITU-TRecommendationsQ.761toQ.764(1993),modified]".[4]ETSIETS300374-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part1:Protocolspecification".[5]ETSIETS300403-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[6]ETSIETS300974:"Digitalcellulartelecommunicationssystem(Phase2+);MobileApplicationPart(MAP)specification(GSM09.02)".[7]GSM02.24:"Digitalcellulartelecommunicationssystem(Phase2);DescriptionofChargeAdviceInformation(CAI)".[8]GSM02.78:"Digitalcellulartelecommunicationssystem(Phase2+);CustomizedApplicationsforMobilenetworkEnhancedLogic(CAMEL)-Phase2.Servicedescription.Stage1".SIST EN 301 668-1:2001
ETSIETSIEN301668-1V1.1.3(2000-07)9[9]GSM03.40:"Digitalcellulartelecommunicationssystem(Phase2+);TechnicalrealizationoftheShortMessageService(SMS);Point-to-Point(PP)".[10]GSM03.78(Release1998)V7.3.0(2000-04):"Digitalcellulartelecommunicationssystem(Phase2+);CustomizedApplicationsforMobilenetworkEnhancedLogic(CAMEL)-Phase2;Stage2".[11]GSM09.78(Release1998)V7.0.0(1999-08):"Digitalcellulartelecommunicationssystem(Phase2+);CustomizedApplicationsforMobilenetworkEnhancedLogic(CAMEL);CAMELApplicationPart(CAP)specification".[12]ANSIT1.113(1995):"SignallingSystemNo.7(SS7);IntegratedServicesDigitalNetwork(ISDN)UserPart".[13]ITU-TRecommendationQ.711:"FunctionalDescriptionoftheSignallingConnectionControlPart".[14]ITU-TRecommendationQ.712:"Definitionandfunctionofsignallingconnectioncontrolpartmessages".[15]ITU-TRecommendationQ.713:"SignallingConnectionControlPartformatsandcodes".[16]ITU-TRecommendationQ.714:"SignallingConnectioncontrolpartprocedures".[17]ITU-TRecommendationQ.716:"SignallingSystemNo.7–SignallingConnectionControlPart(SCCP)Performance".[18]ITU-TRecommendationQ.773:"Transactioncapabilitiesformatsandencoding".[19]ITU-TRecommendationX.209:"SpecificationofbasicencodingrulesforAbstractSyntaxNotationOne(ASN.1)".[20]ITU-TRecommendationX.680(1994)|ISO/IEC8824-1(1995):"Informationtechnology;AbstractSyntaxNotationOne(ASN.1):Specificationofbasicnotation".[21]ITU-TRecommendationX.681(1994)|ISO/IEC8824-2(1995):"Informationtechnology;AbstractSyntaxNotationOne(ASN.1):Informationobjectspecification".[22]ITU-TRecommendationX.682(1994)|ISO/IEC8824-3(1995):"Informationtechnology;AbstractSyntaxNotationOne(ASN.1):Constraintspecification".[23]ITU-TRecommendationX.683(1994)|ISO/IEC8824-4(1995):"Informationtechnology;AbstractSyntaxNotationOne(ASN.1):ParameterizationofASN.1specifications".[24]ITU-TRecommendationX.690(1994)|ISO/IEC8825-1(1995):"Informationtechnology;ASN.1encodingrules:SpecificationofBasicEncodingRules(BER),CanonicalEncodingRules(CER)andDistinguishedEncodingRules(DER)".[25]ITU-TRecommendationX.880(1994)|ISO/IEC13712-1(1995):"Informationtechnology;RemoteOperations:Concepts,modelandnotation".[26]ITU-TRecommendationX.208(1988):"SpecificationofAbstractSyntaxNotationOne(ASN.1)".[27]ETSIEN301668-2(V1.1):"IntelligentNetwork(IN);INCapabilitySet1(CS1)extension;IntelligentNetworkApplicationProtocol(INAP);CustomizedApplicationsforMobilenetworkEnhancedLogic(CAMEL)Phase2;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[28]ANSIT1.112-1996:"AmericanNationalStandardsforTelecommunications–SignallingSystemNumber7(SS7)–SignallingConnectionControlPart(SCCP)".SIST EN 301 668-1:2001
ETSIETSIEN301668-1V1.1.3(2000-07)103AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapplyinadditiontothoseofETS300374-1[4]:ACMAddressCompleteMessageCAMELCustomizedApplicationsforMobilenetworkEnhancedLogicCAPCAMELApplicationPartCICCarrierIdentificationCodeCSECAMELServiceEnvironmentCSICAMELSubscriptionInformationIAMInitialAddressMessageINIntelligentNetworkINAPIntelligentNetworkApplicationProtocolNANorthAmericanOCSIOriginatingCSIRELReleaseWithinthepresentdocumentthetermsgsmSSFandSSFandthetermsgsmSCFandSCFrespectivelyareusedsynonymously.4General4.1DefinitionmethodologyForthepurposeofthepresentdocument,ITU-TRecommendationX.880[25]andtheITU-TRecommendationsforASN.1X.680[20],X.681[21],X.682[22],X.683[23]andX.690[24]forthebasicencodingrulesapply.4.2ExamplephysicalscenariosThefollowingphysicalscenariosasdefinedinETS300374-1[4]subclause7.3.5.1.1"SRFconnectphysicalprocedures"aresupported:-casea)SSFrelay;Non-integratedSRFandIntegratedSRF;-caseb)directpathSCPtoIP;-casec)Assistwithrelay;returncontroltoInitiatingSSPoncompletionofUI;Non-integratedSRFandIntegratedSRF;-cased)Assistwithoutrelay;returncontroltoInitiatingSSPoncompletionofUI.4.3Void4.4INAPaddressingCAMELApplicationsPart(CAP)makesuseoftheservicesofferedbytheSignallingConnectionControlPart(SCCP).ThefollowingSCCPversionsaresupportedbyCAPVersion2:-signallingConnectionControlPart,SignallingSystemno.7CCITT('BlueBookSCCP');-signallingConnectionControlPart,SignallingSystemno.7ITU-TRecommendationQ.711toQ.716('WhiteBookSCCP');-ANSIT1.112-1996:"AmericanNationalStandardsforTelecommunications–SignallingSystemNumber7(SS7)–SignallingConnectionControlPart(SCCP)".SIST EN 301 668-1:2001
ETSIETSIEN301668-1V1.1.3(2000-07)11SCCPversionusedforCAPversion2isanetworkoption.WhenCAPusesWhiteBookSCCPtosendamessage,then:-iftheCAPmessagecanbesentinoneUDTmessageeitherUDTmessageorXUDTmessageshallbeused;-iftheCAPmessagecannotbesentinoneUDTmessageSCCPsegmentsthemessageintotwoormoreXUDTmessages.ThetransmissionofXUDTmessagesmayfail.FailurewilloccurwhenthedestinationSCCP,oranyintermediateSCCP,doesnotsupportWhiteBookSCCP.SupportofANSIT1.112SCCPappliesonlytoPLMNsinNorthAmerica.InterworkingbetweenaPLMNinNorthAmericaandaPLMNoutsideNorthAmericawillinvolveanSTPtotranslatebetweenANSISCCPandITU-T/CCITTSCCP.4.4.1Void4.4.2QualityofserviceparametersTheclass(class0orclass1)ofSCCPissetasrequiredbytheapplication.However,class1shallberequestedbyanyapplicationthatcansendmorethan1TCAPmessagetoitspeer(iconsecutiveTR-CONTINUE)beforereceivingaresponsefromitspeer(TR-CONTINUEorTR-END).OnreceiptofaTC-RESULT-NLindication,theTC-USERshallrequestthetransferofarejectcomponentusingTC-U-REJECTrequestprimitive,withtheappropriateproblemcode(mistypedparameter).Thereturnoptionmaybeusedifrequestedbytheapplication(NetworkOperatortodetermine).4.4.3SCCPaddressingUsingtheCAMELApplicationPart(CAP)forthisfunctionimpliestheuseofTransactionCapabilities(TC)ofCCITTSignallingSystemNo.7andtheSignallingConnectionControlPart(SCCP)ofeitherCCITTSignallingSystemNo.7(fornon-NorthAmericanPLMNs)orANSISignallingSystemNo.7(forNorthAmericanPLMNs).4.5DefinitionandusageofLegIDNOTE:ThissubclauseisnotpartofETS300374-1[4].ForalloperationscontainingaLegID:-LegID=1shallalwaysrefertotheCallingParty,morespecificallythatpartyinthecallpresentwhenInitialDPissenttotheSCF;-LegID=2shallalwaysrefertotheCalledParty,morespecificallythatpartyinthecallcreatedasaresultoftheConnectorContinueoperations.4.6VoidSIST EN 301 668-1:2001
ETSIETSIEN301668-1V1.1.3(2000-07)124.7DetectionPointsNOTE:ThissubclauseisnotpartofETS300374-1[4]norGSM09.78[11],butinlinewithGSM03.78[10].4.7.1DPprocessingrulesThefollowingtableindicatestheresultingtypeofrelationshipafterthecompletionoftheactionindicated.Thetitlesofthecolumnsindicatethepostconditionoftheaction.Table1postconditionaction-oneormoreEDP-Rsarmed,or-SSFisinanyStateexceptMonitororIdle-oneormoreEDP-Nsarmed,or-oneormoreCallInformationReportsoutstanding,or-anApplyChargingReportoutstanding-noEDP-Nsarmed,and-noCallInformationReportsoutstanding,and-noApplyChargingReportoutstandingnormalbehaviour;e.g.ERBCSM,CIRorACRissentcontrolrelationshipmonitorrelationshipidleAbandoncontrolrelationshipmonitorrelationshipidleDisconnectcontrolrelationshipmonitorrelationshipidleCallReleasefromSCFn/an/aidleNOTE1:ERBCSM:EventReporBCSM;CIR:CallInformationReport;ACR:ApplyChargingReport.NOTE2:n/a:notapplicable(i.e.afterreleasingthecallnoEDPsremainarmed.NOTE3:EDPsaredisarmedbytheSSFastheyareencounteredandreportedtotheSCF,orwhenthelegclears.5ReflectionofTCAPApplicationContext(AC)Thefollowingnoteisincluded:NOTE:IftheSSFprovidesanACwhichisnotacceptabletotheSCF,thenanalternateACshouldnotbereturned.IftheACpresentedtotheSCFisnotacceptablethenthisismostprobablyduetoanerrorinsubscriberdataprovisioningoranerrorattheSSF.6AdditionalabstractsyntaxThisclausespecifiestheadditionalormodifiedabstractsyntax,usingASN.1asdefinedinITU-TRecommendationX.208[26]andITU-TRecommendationsX.680[20],X.681[21],X.682[22]andX.683[23].Furthermore,ithastobetakenintoaccountthatsomeconstantsusedforthedefinitionoftypesaredefinedwithothervaluesinthisstandardasinrespecttoETS300374-1[4].TheencodingruleswhichareapplicabletothedefinedabstractsyntaxaretheBasicEncodingRulesforASN.1,definedinITU-TRecommendationX.209[19]andITU-TRecommendationX.690[24]withtherestrictionsasdescribedinITU-TRecommendationQ.773[18],subclause4.1.1,modifiedbyETS300287[2].AdditionalencodingsarecitedforparametersusedinexistingISUP(ETS300356-1[3])andDSS1(ETS300403-1[5])standards.ExistingdatatypesfromtheCS1ETSICoreINAP(ETS300374-1[4])andMAP(ETS300974[6])standardshavebeenused.WhereparametermappingsinCS1ETSICoreINAP(ETS300374-1[4])arenotdefinedforfunctionsimportedfromCS1ETSICoreINAP,butparametermappingsaredefinedinCS2ETSICoreINAP(EN301140-1[1])thentheparametermappingsinCS2ETSICoreINAP(EN301140-1[1])shallbeused.NOTE:Ifthisspecificationusesonlyasubtype,thiswillbeindicatedinEN301668-2[27].AsforCS-2inthefollowingsubclausestheASN.1extensionmarker"."isnotcommentedout.SIST EN 301 668-1:2001
ETSIETSIEN301668-1V1.1.3(2000-07)136.1Operationtypes--Thefollowingdefinitionsandenhancementsofoperationsapply.ApplyCharging--Thisoperationisusedforint
...