SIST EN 301 152-1:2000
(Main)Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Customised Applications for Mobile network Enhanced Logic (CAMEL); Part 1: Protocol specification
- Abstract
To produce a version of INAP for CS1 Extension in order to cover the protocol procedures for the Camel Phase 1 requirements suitable for implementation in Europe. The work is based on operations and extensions received from SMG 3. Close co-operation must be ensured with SMG3 with regard to Camel Phase 1 requirements. The specification should also address aspects of interaction between IN structured networks. The Camel Phase 1 definitions should be fully compatible with the existing CS1 INAP.
- Status
- Published
- Publication Date
- 31-Dec-1999
- Technical Committee
- SPS - Signalling protocols and switching
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Jan-2000
- Due Date
- 01-Jan-2000
- Completion Date
- 01-Jan-2000
SIST EN 301 152-1:2000 is the Slovenian adoption of ETSI EN 301 152-1 V1.2.2, a European telecommunications standard for Intelligent Network Application Protocol (INAP) in the Customized Applications for Mobile network Enhanced Logic (CAMEL) framework. It specifies the protocol additions needed for CAMEL Phase 1, mainly for exchanges between the Service Switching Function (SSF) and the Service Control Function (SCF). Engineers use it to implement and test CAMEL signalling that stays compatible with the existing CS1 INAP base.
What does SIST EN 301 152-1:2000 specify?
SIST EN 301 152-1:2000 specifies the additions to INAP needed for CAMEL Phase 1 Capability. It is based on ETS 300 374-1 and keeps that core protocol as the reference point, while only the additions and modifications needed for CAMEL are included here.
The document is organized into scope, references, abbreviations, general rules, additional abstract syntax, error procedures, detailed operation procedures, services assumed from TCAP, and a normative annex for INAP-to-ISUP mapping. EN 301 152-2 is the companion part that profiles which protocol aspects are used for CAMEL.
| Annex | What it covers |
|---|---|
| Annex A (normative) | Mapping between INAP and ISUP, including InitialDP, Connect, and ReleaseCall |
What are the key requirements of SIST EN 301 152-1:2000?
Protocol base and compatibility
SIST EN 301 152-1:2000 keeps CAMEL Phase 1 aligned with the existing CS1 INAP framework. The scope states that the CAMEL definitions are intended to be fully compatible with the existing CS1 INAP, and the document treats ETS 300 374-1 as the underlying base.
In practice, this means implementers add only the CAMEL-specific protocol behavior rather than designing a separate signalling model. That helps mobile network nodes interoperate with CS1-based equipment.
Syntax, encoding, and contexts
SIST EN 301 152-1:2000 uses ASN.1 notation and Basic Encoding Rules for the additional abstract syntax. Clause 6 also replaces the EXTENSION MACRO with the EXTENSION CLASS and defines the Criticality type as ignore or abort.
The standard defines operation timers with the short range of 1 to 20 seconds, and it sets the CAP-v1-gsmSSF-to-gsmSCF-AC application context for SSF-initiated dialogue. It also defines the ASEs used for activation and call processing. In practice, this gives implementers the exact data model and dialogue setup they need for encoding and exchanging CAMEL messages.
Operation behavior and parameters
SIST EN 301 152-1:2000 adds specific parameters to key operations. For Connect, it adds genericNumbers, suppressionOfAnnouncement, and oCSIApplicable, and it states that callingPartyNumber is ignored if received. For InitialDP, it adds parameters such as iMSI, subscriberState, locationInformation, ext-BasicServiceCode, callReferenceNumber, mscAddress, and calledPartyBCDNumber.
These parameters carry the mobile subscriber and call context that CAMEL services need to control routing and charging-related behaviour. The document also states that ReleaseCall may only be sent within a control relationship, not a monitor relationship.
Error handling and BCSM event control
SIST EN 301 152-1:2000 defines handling for MissingCustomerRecord, MissingParameter, and expiration of TSSF. In each of these cases, the CCF handles the call according to the Default Call Handling parameter of the valid CAMEL Subscription Information (CSI).
For RequestReportBCSMEvent, the standard restricts when events can be armed or disarmed, and it notes that collectedInfo is not valid in eventTypeBCSM. In practice, this tells service logic and switch software how to avoid invalid event control during call processing.
TCAP and ISUP mapping
SIST EN 301 152-1:2000 also defines TCAP dialogue-control behaviour and the mapping to ISUP in Annex A. The annex maps InitialDP to IAM, Connect to IAM, and ReleaseCall to REL, which is important for implementing CAMEL services in call-control networks.
What terms does SIST EN 301 152-1:2000 define?
- CAMEL - Customized Applications for Mobile network Enhanced Logic, the mobile-network service framework addressed by this standard.
- CS1 - Intelligent Network Capability Set 1, the base IN capability set extended by this document.
- INAP - Intelligent Network Application Protocol, the signalling protocol extended here for CAMEL.
- SSF - Service Switching Function; in this standard, gsmSSF and SSF are used synonymously.
- SCF - Service Control Function; in this standard, gsmSCF and SCF are used synonymously.
- OCSI - Originating CSI, a trigger-related information item used with call control.
- TSSF - The SSF timer whose expiry triggers fallback call handling in the specified error procedures.
- TCAP - Transaction Capabilities Application Part, the transaction layer whose services are assumed by the protocol.
Who uses SIST EN 301 152-1:2000?
SIST EN 301 152-1:2000 is used by mobile network signalling engineers, switch and MSC implementers, and CAMEL service developers. Quality teams and conformance testers use it to check that SSF and SCF behaviour, event control, and INAP-to-ISUP mapping match the CAMEL Phase 1 protocol rules. Buyers and integrators use it when they need equipment that fits CS1-based INAP deployments in European mobile networks.
Which standards are used with SIST EN 301 152-1:2000?
- ETS 300 374-1 - the core INAP base that this standard extends.
- EN 301 152-2 - the PICS proforma part that profiles which protocol aspects are used.
- TS 101 046 - the CAMEL Application Part specification, noted as equivalent to the CAMEL capability.
- ETS 300 646-1 - the ISUP specification used for mapping call-control behaviour and message encoding.
- ETS 300 974 - the MAP specification used for encoding mobile-specific parameters such as IMSI and subscriber state.
- ETS 300 940 - the mobile radio layer 3 specification used for related mobility and call information.
- ITU-T X.680 to X.690 and X.880 - the ASN.1 and remote-operations foundations used for syntax, constraints, and encoding.
- ITU-T Q.1218 and Q.713 - signalling references used for CS1 interface and SCCP-related formatting.
What does the SIST EN 301 152-1:2000 document contain?
SIST EN 301 152-1:2000 contains the CAMEL-specific additions to INAP, including ASN.1 definitions, data types, application contexts, and extension classes. It also contains error procedures and detailed operation procedures for Connect, EventReportBCSM, InitialDP, ReleaseCall, and RequestReportBCSMEvent.
The document includes TCAP dialogue-control rules and quality-of-service behaviour for SCCP and TC services. Annex A provides normative mapping tables between INAP and ISUP, showing how call-control parameters are carried between protocol layers.
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 152-1:2000 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); Customised Applications for Mobile network Enhanced Logic (CAMEL); Part 1: Protocol specification". This standard covers: To produce a version of INAP for CS1 Extension in order to cover the protocol procedures for the Camel Phase 1 requirements suitable for implementation in Europe. The work is based on operations and extensions received from SMG 3. Close co-operation must be ensured with SMG3 with regard to Camel Phase 1 requirements. The specification should also address aspects of interaction between IN structured networks. The Camel Phase 1 definitions should be fully compatible with the existing CS1 INAP.
To produce a version of INAP for CS1 Extension in order to cover the protocol procedures for the Camel Phase 1 requirements suitable for implementation in Europe. The work is based on operations and extensions received from SMG 3. Close co-operation must be ensured with SMG3 with regard to Camel Phase 1 requirements. The specification should also address aspects of interaction between IN structured networks. The Camel Phase 1 definitions should be fully compatible with the existing CS1 INAP.
SIST EN 301 152-1:2000 is classified under the following ICS (International Classification for Standards) categories: 33.040.40 - Data communication networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 152-1:2000 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 del inteligentnega omrežja (INAP) - Uporabniške aplikacije za izboljšano logiko mobilnega omrežja (CAMEL) - 1. del: Specifikacija protokolaIntelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Customised Applications for Mobile network Enhanced Logic (CAMEL); Part 1: Protocol specification33.040.40Podatkovna komunikacijska omrežjaData communication networksICS:Ta slovenski standard je istoveten z:EN 301 152-1 Version 1.2.2SIST EN 301 152-1:2000en01-januar-2000SIST EN 301 152-1:2000SLOVENSKI
STANDARD
EN 301 152-1 V1.2.2 (1998-09)European Standard (Telecommunications series)Intelligent Network (IN);IN Capability Set 1 (CS1) extension;Intelligent Network Application Protocol (INAP);Customized Applications forMobile network Enhanced Logic (CAMEL);Part 1: Protocol specificationSIST EN 301 152-1:2000
ETSIEN 301 152-1 V1.2.2 (1998-09)2ReferenceDEN/SPS-03052-1 (ao090ipc.PDF)KeywordsIN, INAP, ISDN, mobile, protocolETSIPostal 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 301 152-1:2000
ETSIEN 301 152-1 V1.2.2 (1998-09)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.62.1Normative references.62.2Informative references.73Abbreviations.74General.74.1Definition methodology.74.4INAP addressing.84.4.2Quality of service parameters.86Additional abstract syntax.86.1Operation types.86.3Data types.86.5Application contexts.106.6Classes.108Error procedures.118.1Operation related error procedures.118.1.6MissingCustomerRecord.118.1.6.2Operations SSF->SCF.118.1.7MissingParameter.118.1.7.3Operations SSF -> SCF.118.2Entity related error procedures.118.2.1Expiration of TSSF.118.2.1.2Procedures SSF->SCF.119Detailed operation procedures.119.11Connect procedure.119.11.1General description.119.11.1.1Parameters.129.11.3Responding entity (SSF).129.11.3.1Normal procedure.129.17EventReportBCSM procedure.129.17.2Invoking entity (SSF).129.17.2.1Normal procedure.129.17.2.2Error handling.129.19InitialDP procedure.139.19.1General description.139.19.1.1Parameters.139.19.2Invoking entity (SSF).139.19.2.2Error handling.139.23ReleaseCall procedure.149.23.1General description.149.25RequestReportBCSMEvent procedure.149.25.1General description.149.25.1.1Parameters.1410Services assumed from TCAP.1410.9Mapping on to TC services.1410.9.1Dialogue control.1410.9.1.5User information.1410.9.1.8Quality of service.14SIST EN 301 152-1:2000
ETSIEN 301 152-1 V1.2.2 (1998-09)4Annex A (normative):Mapping between INAP and ISUP.15A.1InitialDP operation.15A.2Connect operation.15A.3ReleaseCall operation.16History.17SIST EN 301 152-1:2000
ETSIEN 301 152-1 V1.2.2 (1998-09)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document is part 1 of a multi-part standard covering the IN Capability Set 1 (CS1) extension; IntelligentNetwork Application Protocol (INAP); Customized Applications for Mobile network Enhanced Logic (CAMEL) asdescribed below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification".NOTE:Further parts of the present document may be identified later.National transposition datesDate of adoption of this EN:18 September 1998Date of latest announcement of this EN (doa):31 December 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 1999Date of withdrawal of any conflicting National Standard (dow):30 June 1999SIST EN 301 152-1:2000
ETSIEN 301 152-1 V1.2.2 (1998-09)61ScopeThis fist part of EN 301 152 specifies the additions for Intelligent Network Application Protocol (INAP) to support theCAMEL Phase 1 Capability. The present document is based on ETS 300 374-1 [19].ETS 300 374-1 [19] is also taken as an editorial basis for the present document. Only additions and modifications inrespect to that ETS are specified in the present document. For Customized Applications for Mobile network EnhancedLogic (CAMEL) only a restricted subset of the protocol aspects of ETS 300 374-1 [19] is necessary. This restriction isnot defined in the present document. A profiling of CAMEL, i.e. which protocol aspects are used, is given byEN 301 152-2 [31]. Clauses and subclauses of ETS 300 374-1 [19] for which neither additions nor modifications aremade do not appear in the present document. However, to ensure the same clause numbering of the present document asof ETS 300 374-1 [19], deleted clauses and subclauses are numbered implicitly.As the present document specifies the additions in respect to the SSF it is assumed that the SCF is according toETS 300 374-1 [19] taking into account the requirements defined in the present document for the SSF.The protocol specification of the CAMEL Capability in the present document is considered as equivalent toTS 101 046 [28].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 referencesThe date of the following reference has been modified:[11]ITU-T Recommendation Q.1218 (1995): "Interface Recommendation for intelligent network CS1".The following references are in addition to those of ETS 300 374-1 [19].[19]ETS 300 374-1 (1994): "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1);Core Intelligent Network Application Protocol (INAP); Part 1: Protocol specification".[20]ETS 300 974: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part(MAP) specification (GSM 09.02)".[21]ITU-T Recommendation Q.713: "Signalling Connection Control Part formats and codes".[22]ITU-T Recommendation X.680 (1994) | ISO/IEC 8824-1 (1995): "Information technology –Abstract Syntax Notation One (ASN.1): Specification of basic notation[23]ITU-T Recommendation X.681 (1994) | ISO/IEC 8824-2 (1995): "Information technology –Abstract Syntax Notation One (ASN.1): Information object specification".[24]ITU-T Recommendation X.682 (1994) | ISO/IEC 8824-3 (1995): "Information technology –Abstract Syntax Notation One (ASN.1): Constraint specification".SIST EN 301 152-1:2000
ETSIEN 301 152-1 V1.2.2 (1998-09)7[25]ITU-T Recommendation X.683 (1994) | ISO/IEC 8824-4 (1995): "Information technology –Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications".[26]ITU-T Recommendation X.690 (1994) | ISO/IEC 8825-1 (1995): "Information technology –ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules(CER) and Distinguished Encoding Rules (DER)".[27]ITU-T Recommendation X.880 (1994) | ISO/IEC 13712-1 (1995): "Information technology -Remote Operations: Concepts, model and notation".[28]TS 101 046 (V5.5): "Digital cellular telecommunications system (Phase 2+); CustomizedApplications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP)specification (GSM 09.78 version 5.5.0)".[29]ETS 300 646-1: "Integrated Services Digital Network (ISDN); Signalling System No.7; Digitalcellular telecommunications system (Phase 2); Application of ISDN User Part (ISUP) version 2 forthe ISDN-Public Land Mobile Network (PLMN) signalling interface; Part 1: Protocol specification(GSM 09.12)".[30]ETS 300 940: "Digital cellular telecommunications system (Phase 2+); Mobile radio interfacelayer 3 specification (GSM 04.08)".2.2Informative references[31]EN 301 152-2 (V1.2): "Intelligent Network (IN); IN Capability Set 1 (CS1) extension; IntelligentNetwork Application Protocol (INAP); Customized Applications for Mobile network EnhancedLogic (CAMEL); Part 2: Protocol Implementation Conformance Statement (PICS) proformaspecification".[32]TS 101 044 (V5.5): "Digital cellular telecommunications system (Phase 2+); CustomizedApplications for Mobile network Enhanced Logic (CAMEL) - Stage 2 (GSM 03.78 version5.5.0)".3AbbreviationsFor the purposes of the present d
...