SIST EN 301 140-1:2000
(Main)Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 1: Protocol specification
- Abstract
To produce a version of INAP for CS2 with as few options as possible suitable for implementation in Europe. Close co-operation must be ensured with SPS2 with regard to CTM and UPT support. Other aspects which need to be addressed are those surrounding VPN such as CTN and GVNS. The Call Party Handling procedures must also be supported. The validated SDLl model must be part of th enormative text and shall define the behaviour of the various operations applicable for the defined IN CS2 functional interface. The specification should also address aspects of interaction between IN structured networks. As a result of this, new IN functionality may be identified such as the interworking function; the impact this has on the INAP and ISUP/DSS1 will need to be explored. The CS2 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 140-1:2000 is the Slovenian adoption of ETSI EN 301 140-1 V1.3.4 for Intelligent Network Application Protocol (INAP) Capability Set 2 (CS2). It specifies the protocol behaviour, interfaces and common data needed for IN CS2 implementations, with an emphasis on European deployment and compatibility with existing CS1 INAP.
What does SIST EN 301 140-1:2000 specify?
SIST EN 301 140-1:2000 specifies the INAP protocol specification for Capability Set 2 (CS2). It is aimed at defining a CS2 version with as few options as possible, while keeping compatibility with existing CS1 INAP and supporting the main service-control and network-interworking cases.
The scope also covers practical CS2 topics such as CTM and UPT support, VPN-related aspects including CTN and GVNS, Call Party Handling procedures, and interaction between IN structured networks. The document says the validated SDLl model is part of the normative text and defines the behaviour of the operations for the IN CS2 functional interface.
The document is organised into clauses 1 to 18, moving from scope and definitions to interface specifications, common CS2 types, entity procedures, error handling and detailed operation procedures.
What are the key requirements of SIST EN 301 140-1:2000?
SIST EN 301 140-1:2000 defines how CS2 INAP is structured, how the main IN entities communicate, and how implementations handle state, data and errors. In practice, this is the part that matters when you are designing, implementing or testing interoperability.
Protocol architecture and compatibility
Clause 4 covers the definition methodology, example physical scenarios, protocol architecture, addressing, and compatibility mechanisms. It also states the relationship with ITU-T Recommendation Q.1224 and describes how INAP compatibility is handled for major, minor and network-specific additions. For implementers, this is the guidance that keeps a CS2 product aligned with the existing IN framework.
Common CS2 types
Clause 5 defines the common CS2 data types, error types, operation codes, error codes, classes and Object IDs (IDs). These shared definitions are the basis for consistent message encoding and for checking whether an implementation uses the right operation and error values.
Interfaces between functional entities
Clauses 6 to 11 specify the interfaces between SSF/CCF and SCF, SCF and SRF, SCF and SDF, SDF and SDF, SCF and SCF, and SCF and CUSF. Each interface includes operations, arguments, packages, contracts and ASN.1 modules. This matters because each IN entity must encode and interpret the same protocol elements at the same boundary.
SDF and X.500 based directory handling
Clauses 8 and 9 reuse ITU-T Recommendation X.500 concepts for the SDF interfaces. Clause 8 defines the SCF-SDF information model, access control, attribute contexts and directory protocol, while clause 9 defines shadowing and chaining behaviour for SDF-SDF interaction. In practice, this is the part to use when the service logic depends on directory-like data access, updates or replication.
Entity behaviour and state machines
Clauses 12 to 16 define AE procedures and finite state models for SSF, SCF, SRF, SDF and CUSF. These clauses show when each entity is idle, waiting, assisting, monitoring or connected, and how it moves between states. That is what developers and test teams use to verify that an implementation reacts correctly during call handling and service interaction.
Errors and detailed operations
Clause 17 lists operation-related and entity-related error procedures, including cases such as missing data, security, referral, system failure and task refusal. Clause 18 then describes detailed procedures such as ActivateServiceFiltering, ActivityTest, ApplyCharging, CallInformationReport, Cancel and the chained operations. This is the part that turns the protocol into concrete message sequences for implementation and conformance testing.
What terms does SIST EN 301 140-1:2000 define?
- INAP - Intelligent Network Application Protocol, the protocol used to exchange IN service control information.
- CS2 - Capability Set 2, the second set of Intelligent Network capabilities covered by this specification.
- SCF - Service Control Function, the entity that controls service logic and exchanges service-related information with other IN functions.
- SSF - Service Switching Function, the entity at the switching side that interacts with the SCF during call handling.
- SRF - Specialized Resource Function, the entity that provides specialized interaction resources such as user interaction support.
- SDF - Service Data Function, the entity used for directory-like service data access and update.
- CUSF - Call Unrelated Service Function, the entity covered by the SCF/CUSF interface and related procedures.
- TCAP AC - Transaction Capabilities Application Part application context, used in the SACF/MACF rules described in clause 4.2.
Who uses SIST EN 301 140-1:2000?
SIST EN 301 140-1:2000 is used by telecommunications network operators, switching and service-platform vendors, protocol implementers, and integration engineers working on Intelligent Network systems. It is also relevant to test labs and quality teams that need to verify INAP message exchange, state behaviour, error handling and conformance.
In practice, engineers use it to implement SSF, SCF, SRF, SDF and CUSF behaviour. Buyers and quality managers use it to check whether a product supports the CS2 interfaces and procedures needed for network compatibility.
Which standards are used with SIST EN 301 140-1:2000?
SIST EN 301 140-1:2000 relates directly to ITU-T Recommendation Q.1224, which clause 4.1.5 uses as a point of comparison for the present document. It also reuses concepts from ITU-T Recommendation X.500 in clauses 8 and 9 for SCF-SDF and SDF-SDF directory procedures.
The scope also points to interaction with INAP itself, ISUP/DSS1, and IN service environments such as SPS2, CTM, UPT, VPN, CTN and GVNS. These names matter because they show the protocol and service context in which CS2 is intended to work.
What does the SIST EN 301 140-1:2000 document contain?
SIST EN 301 140-1:2000 contains interface specifications, ASN.1 modules, state-machine procedures, error definitions and detailed operation procedures for IN CS2. The document includes message-oriented procedures such as charging, information reporting, call gap control, user interaction and chained directory operations.
It also gives protocol models for SSF, SCF, SRF, SDF and CUSF behaviour, including normal and error cases. For implementers, this is the material used to build protocol software; for testers, it is the material used to check conformance and interoperability.
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 140-1:2000 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 1: Protocol specification". This standard covers: To produce a version of INAP for CS2 with as few options as possible suitable for implementation in Europe. Close co-operation must be ensured with SPS2 with regard to CTM and UPT support. Other aspects which need to be addressed are those surrounding VPN such as CTN and GVNS. The Call Party Handling procedures must also be supported. The validated SDLl model must be part of th enormative text and shall define the behaviour of the various operations applicable for the defined IN CS2 functional interface. The specification should also address aspects of interaction between IN structured networks. As a result of this, new IN functionality may be identified such as the interworking function; the impact this has on the INAP and ISUP/DSS1 will need to be explored. The CS2 definitions should be fully compatible with the existing CS1 INAP.
To produce a version of INAP for CS2 with as few options as possible suitable for implementation in Europe. Close co-operation must be ensured with SPS2 with regard to CTM and UPT support. Other aspects which need to be addressed are those surrounding VPN such as CTN and GVNS. The Call Party Handling procedures must also be supported. The validated SDLl model must be part of th enormative text and shall define the behaviour of the various operations applicable for the defined IN CS2 functional interface. The specification should also address aspects of interaction between IN structured networks. As a result of this, new IN functionality may be identified such as the interworking function; the impact this has on the INAP and ISUP/DSS1 will need to be explored. The CS2 definitions should be fully compatible with the existing CS1 INAP.
SIST EN 301 140-1:2000 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 140-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) - Drugi nabor zmožnosti inteligentnega omrežja (CS2) - 1. del: Specifikacija protokolaIntelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 1: Protocol specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 140-1 Version 1.3.4SIST EN 301 140-1:2000en01-januar-2000SIST EN 301 140-1:2000SLOVENSKI
STANDARD
EN 301 140-1 V1.3.4 (1999-06)European Standard (Telecommunications series)Intelligent Network (IN);Intelligent Network Application Protocol (INAP);Capability Set 2 (CS2);Part 1: Protocol specificationSIST EN 301 140-1:2000
ETSIETSI EN 301 140-1 V1.3.4 (1999-06)2ReferenceDEN/SPS-03038-1 (ak090j2o.PDF)KeywordsCS2, INAP, IN, 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.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frCopyright 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 1999.All rights reserved.SIST EN 301 140-1:2000
ETSIETSI EN 301 140-1 V1.3.4 (1999-06)3ContentsIntellectual Property Rights.31Foreword.311Scope.322References.333Definitions and abbreviations.353.1Definitions.353.2Abbreviations.364Interface specification for telecommunication services.384.1General.384.1.1Definition methodology.384.1.2Example physical scenarios.384.1.2.1"SCF - External SRF" Communication in the Relay Case.454.1.3INAP protocol architecture.464.1.3.1INAP signalling congestion control for SS7.474.1.4INAP addressing.484.1.5Relationship between ITU-T Recommendation Q.1224 and the present document.484.1.6Compatibility mechanisms used for INAP.514.1.6.1Introduction.514.1.6.2Definition of INAP compatibility mechanisms.514.1.6.2.1Procedures for major additions to INAP.514.1.6.2.2Procedures for minor additions to INAP.514.1.6.2.3Procedures for inclusion of network specific additions to INAP.524.2SACF/MACF rules.524.2.1Reflection of TCAP AC.524.2.2Sequential/parallel execution of operations.525Common IN Capability Set 2 (CS2) Types.525.1Data types.525.2Error types.695.3Operation codes.715.4Error codes.725.5Classes.735.6Object IDentifiers (IDs).796SSF/CCF - SCF Interface.836.1Operations and arguments.836.2SSF/SCF packages, contracts and ACs.1006.2.1(void).1006.2.2SSF/SCF ASN.1 module.1007SCF/SRF interface.1087.1SCF/SRF operations and arguments.1087.2SRF/SCF contracts, packages and ACs.1127.2.1(void).1127.2.2SRF/SCF ASN.1 modules.1128SCF/SDF interface.1148.1Introduction to the reuse of ITU-T Recommendation X.500 for SDF Interfaces.1148.1.1Alignment between the ITU-T Recommendation X.500 concepts and the IN.1148.1.2Use of a limited subset of ITU-T Recommendation X.500.1148.1.3Working assumptions.1158.2The SDF information model.1158.2.1Information Framework.1158.2.1.1METHOD.1158.2.1.2DIT METHOD Use.116SIST EN 301 140-1:2000
ETSIETSI EN 301 140-1 V1.3.4 (1999-06)48.2.1.2.1Overview.1168.2.1.2.2DIT METHOD Use specification.1168.2.2Basic Access Control.1178.2.2.1ProtectedItems.1178.2.2.2GrantsAndDenials.1178.2.3Attribute contexts.1188.2.3.1Basic Service context.1188.2.3.2Line Identity context.1188.2.3.3Assignment context.1198.2.4Attribute Definitions.1198.2.4.1DIT Method Use operational attribute.1198.3The SCF-SDF Interface Protocol.1198.3.1Information types and common procedures.1198.3.1.1CommonArguments.1198.3.1.2ServiceControls.1208.3.1.3Entry Information Selection.1208.3.1.4EntryInformation.1208.3.1.5Simple Public Key GSS-API Mechanism (SPKM) Token profile.1208.3.2Operations.1218.3.2.1Bind operation.1218.3.2.2Search operation.1218.3.2.3AddEntry operation.1228.3.2.4RemoveEntry operation.1228.3.2.5ModifyEntry operation.1228.3.2.6Execute operation.1238.3.2.7in-directoryUnbind operation.1248.3.3Errors.1248.3.3.1Bind error.1248.3.3.2Service error.1248.3.3.3(void).1248.3.3.4execution Error.1248.4Protocol overview.1258.4.1Remote operations.1258.4.2Directory ROS-objects and contracts.1258.4.3DAP contract and packages.1258.5Directory protocol abstract syntax.1268.5.1Abstract syntaxes.1268.5.1.1DAP abstract syntax.1278.5.1.2Extended DAP abstract syntax.1278.5.1.3DAP binding abstract syntax.1278.5.1.4SESE abstract syntax.1278.5.2Directory ACs.1278.5.2.1Directory access AC.1278.5.2.2Extended Directory Access AC.1288.5.3Operation codes.1288.5.4Error codes.1288.5.5Versions and the rules for extensibility.1298.5.5.1Version negotiation.1298.5.5.2DUA side.1298.5.5.2.1Request and response processing at the DUA side.1298.5.5.2.2Extensibility rules for error handling at the DUA side.1298.5.5.3Request processing at the DSA side.1308.6Conformance.1308.6.1Conformance by SCFs.1308.6.1.1Statement requirements.1308.6.1.2Static requirements.1308.6.1.3Dynamic requirements.1318.6.2Conformance by SDFs.1318.6.2.1Statement requirements.1318.6.2.2Static requirements.132SIST EN 301 140-1:2000
ETSIETSI EN 301 140-1 V1.3.4 (1999-06)58.6.2.3Dynamic requirements.1328.7ASN.1 Modules for the SCF-SDF interface.1328.7.1IN-CS2-SDF-InformationFramework module.1338.7.2IN-CS2-SDF-BasicAccessControl module.1348.7.3IN-CS2-SCF-SDF-Operations module.1368.7.4IN-CS2-SCF-SDF-Protocol module.1379SDF/SDF interface.1409.1Introduction to the IN ITU-T Recommendation X.500 DSP and Directory Information ShadowingProtocol (DISP) subset.1409.2Working assumptions.1409.3The IN ITU-T Recommendation X.500 DISP subset.1419.3.1Shadowing Agreement specification.1419.3.2DSA Shadow Bind.1419.3.3IN-DSA Shadow Unbind.1419.3.4Coordinate Shadow Update.1419.3.5Update Shadow.1429.3.6Request Shadow Update.1439.4The IN ITU-T Recommendation X.500 DSP subset.1449.4.1Information types and common procedures.1449.4.1.1Chaining arguments.1449.4.1.2Chaining results.1459.4.1.3Reference type.1469.4.1.4Access Point information.1469.4.1.5Continuation reference.1469.4.2DSA Bind.1479.4.3IN DSA Unbind.1479.4.4Chained operations.1489.4.5Chained errors.1489.5Protocol overview.1499.5.1ROS-objects and contracts.1499.5.2DSP contract and packages.1499.5.3DISP contract and packages.1509.6Protocol abstract syntax.1519.6.1DSP abstract syntax.1519.6.2DISP abstract syntax.1519.6.3Directory System AC.1519.6.4Directory Shadow AC.1529.6.5Versions and the rules for extensibility.1539.6.5.1Version negotiation.1539.6.5.2Initiating DSA side.1539.6.5.2.1Request and response processing at the initiating DSA side.1539.6.5.2.2Extensibility rules for error handling at the initiating DSA side.1539.6.5.3Request processing at the responding DSA side.1549.7Conformance.1549.7.1Conformance by SDFs.1549.7.1.1Statement requirements.1549.7.1.2Static requirements.1559.7.1.3Dynamic requirements.1559.7.2Conformance by a shadow supplier.1569.7.2.1Statement requirements.1569.7.2.2Static requirements.1569.7.2.3Dynamic requirements.1569.7.3Conformance by a shadow consumer.1579.7.3.1Statement requirements.1579.7.3.2Static requirements.1579.7.3.3Dynamic requirements.1579.8ASN.1 modules for the SDF-SDF interface.1579.8.1IN-CS2-SDF-SDF-Protocol module.157SIST EN 301 140-1:2000
ETSIETSI EN 301 140-1 V1.3.4 (1999-06)610SCF/SCF interface.16110.1SCF/SCF Operations and arguments.16110.2SCF/SCF contracts, packages and ACs.17010.2.1(void).17010.2.2ASN.1 modules.17011SCF/CUSF interface.17411.1Operations and arguments.17411.2SCF/CUSF contracts, operation packages, and ACs.17711.2.1(void).17711.2.2ASN.1 module.17712SSF AE procedures.18012.1General.18012.2Model and interfaces.18012.3Relations between SSF Finite State Model (FSM) and the CCF and maintenance functions.18112.4SSF management (SSME) FSM.18312.5SSF switching state model (SSM) FSM.18412.5.1FSM for Call Segment Association (CSA).18712.5.1.1State a: Idle.18812.5.1.2State b: Active.18812.5.2FSM for Call Segment.19012.5.2.1State a: Idle.19512.5.2.2State c: Waiting For Instructions.19612.5.2.3State d: Waiting For End Of User Interaction (WFI).19712.5.2.4State e: Waiting For End Of Temporary Connection (WFI).19812.5.2.5State f: Monitoring.19812.5.2.6State h: Waiting For End Of User Interaction (Monitoring).19912.5.2.7State i: Waiting For End Of Temporary Connection (Monitoring).20012.6Assisting SSF FSM.20112.6.1State aa: Idle.20112.6.2State ab: Waiting For Instructions.20212.6.3State ac: Waiting For End Of User Interaction.20312.7Handed-off SSF FSM.20412.7.1State ha: Idle.20412.7.2State hb: Waiting For Instructions.20512.7.3State hc: Waiting For End Of User Interaction.20612.8User Service Interaction (USI) FSM.20713SCF AE procedures.20813.1General.20813.2Model and Interfaces.20813.3Relationship between the SCF FSM and the SLPs/Maintenance Functions.20913.4Partial SCME State Transition Diagram.21113.4.1State M1:.21113.4.2State M2:.21113.4.3State M3: "Service filtering idle".21213.4.4State M4: "Waiting for SSF service filtering response".21213.4.5State M5: "Activity test idle".21213.4.6State M6: "Waiting for activity test response".21213.4.7State M7: "ManageTriggerData idle".21313.4.8State M8: "Waiting for ManageTriggerData response".21313.4.9The RCO.21313.5The SCSM.21413.5.1SSF/SRF Related states (SCSM-SSF/SRF).21413.5.1.1FSM for SSF/SRF interface.21513.5.1.1.1State S1: "Idle".21613.5.1.1.2State S2: "Preparing SSF/SRF Instructions".21613.5.1.2FSM for CSA.21913.5.1.2.1State I1: "SSF Control Idle".21913.5.1.2.2State I2: "Preparing SSF Instructions".220SIST EN 301 140-1:2000
ETSIETSI EN 301 140-1 V1.3.4 (1999-06)713.5.1.3FSM for Call Segment.22113.5.1.3.1State C1: "CS Control Idle".22213.5.1.3.2State C2: "Preparing CS Instructions".22413.5.1.3.3State C3: "Suspended and User Interaction".23213.5.1.3.4State C4: "Not Suspended and User Interaction".23813.5.1.4FSM for Specialized Resource.24413.5.1.4.1State R1: "SRF Control Idle".24413.5.1.4.2State R2: "Controlling SRF".24413.5.1.5FSM for Assisting SSF.24613.5.1.5.1State A1: "Assisting SSF Idle".24713.5.1.5.2State A2: "Preparing SSF Instructions".24713.5.1.5.3State A3: "User Interaction".24813.5.1.6FSM for Handed-off SSF.24913.5.1.6.1State H1: "Handed-off SSF Idle".25013.5.1.6.2State H2: "Preparing SSF Instructions".25013.5.1.6.3State H3: "User Interaction".25113.5.2SDF related states (SCSM-SDF).25213.5.2.1 State 1: "Idle".25213.5.2.2 State 2: "Wait for subsequent requests".25213.5.2.3 State 3: "Wait for Bind result".25213.5.2.4 State 4: "SDF Bound".25313.5.3SCF Related states.25313.5.3.1Controlling SCF FSM (SCSM-Con).25413.5.3.1.1State 1: Idle.25413.5.3.1.2State 2: Preparing Handling Information Request.25413.5.3.1.3State 3: Waiting for Bind Result.25413.5.3.1.4State 4: Assisted Mode.25413.5.3.1.5State 5: Preparing Additional Information.25613.5.3.1.6State 7: Preparing SCFUnbind request.25613.5.3.2Supporting SCF FSM (SCSM-Sup).25713.5.3.2.1State 1: Idle.25713.5.3.2.2State 2: Processing SCF Bind.25813.5.3.2.3State 3: Assisting mode.25813.5.3.2.4State 4: Waiting for Additional Information.25913.5.3.2.5SCF state transition models for chaining.26013.5.4(void).26513.5.5USI_SCF FSM.26514SRF AE procedures.26514.1General.26514.2Model and interfaces.26614.3Relationship between the SRF FSM and maintenance functions / bearer connection handling.26614.4The SRSM.26814.4.1State 1: "Idle".27014.4.2State 2: "Connected".27114.4.3State 3: "User interaction".27214.5Example SRF control procedures.27314.5.1SRF connect procedures.27314.5.1.1SRF connect physical procedures.27314.5.2SRF end user interaction procedures.27714.5.2.1PA / prompt & collect user information / prompt & receive message (PA/P&C/P&R).27714.5.3SRF disconnection procedures.27914.5.3.1SRF initiated disconnect.28014.5.3.2SCF initiated disconnect.28114.5.4Examples illustrating complete user interaction sequences.28214.5.4.1Message sequences for service assist.28714.5.4.2Message sequences for hand-off.28815SDF AE procedures.28915.1General.28915.2Model and interfaces.289SIST EN 301 140-1:2000
ETSIETSI EN 301 140-1 V1.3.4 (1999-06)815.3The SDF FSM structure.29115.4SDF state transition models.
...