Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to "ETSI Editing and Committee Support Dept." at the address shown on the title page.

"Test Suite Structure and Test Purposes (TSS&TP)".
Part 5: Part 6:
Transposition dates Date of latest announcement of this ETS (doa): Date of latest publication of new National Standard or endorsement of this ETS (dop/e): Date of withdrawal of any conflicting National Standard (dow): 31 December 1994
30 June 1995 30 June 1995
. "PICS proforma for the SCF-SDF interface". This ETS is based on ITU-T Recommendation Q. "Protocol specification for the SCF-SDF interface". This ETS is part 1 of a multi-part standard covering the Capability Set 1 (CS1) core Intelligent Network Protocol (INAP) as described below: Part 1: Part 2: Part 3: Part 4: "Protocol specification". "Protocol Implementation Conformance Statement (PICS) proforma". It provides major modifications and further requirements to this base document.Page 13 ETS 300 374-1: September 1994
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).1218 (1993). "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma".

Page 14 ETS 300 374-1: September 1994 Blank page
.

ETS 300 348 (1994): "Intelligent Network (IN). subsequent amendments to or revisions of any of these publications apply to this ETS only when incorporated in it by amendment or revision. ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN). Service Control Function (SCF). NOTE: More sophisticated solutions for the service interactions between IN and the ISDN/PSTN environment should be studied in the scope of future versions of INAP and the ISDN/PSTN signalling standards. It supports interactions between the following three Functional Entities (FEs). CCITT Signalling System No. as defined in the Intelligent Network (IN) functional model: Service Switching Function (SSF). ETS 300 287 (1993): "Integrated Services Digital Network (ISDN). CCITT Signalling System No. ETS 300 121 (1992): "Integrated Services Digital Network (ISDN).7. CCITT Signalling System No. Part 1: Protocol specification". These normative references are cited at the appropriate places in the text and the publications are listed hereafter.7 for international ISDN interconnections (ISUP version 1)". provisions from other publications. NOTE: [5] ETS 300 196-1 (1993) was initially published as ETS 300 196 (1993). Physical plane for intelligent network Capability Set 1 (CS1) [ITU-T Recommendation Q. Generic functional protocol for the support of supplementary services. Signalling Connection Control Part (SCCP) [connectionless and connection-oriented] to support international interconnection". As this ETS is intended for the early introduction of IN in the existing ISDN/PSTN. Message Transfer Part (MTP) to support international interconnection".Page 15 ETS 300 374-1: September 1994
1
Scope
This first part of ETS 300 374 defines the Intelligent Network Application Protocol (INAP) required for support of Capability Set 1 (CS1). Digital Subscriber Signalling System No.
The scope of this ETS is the further development of the INAP for both the Integrated Services Digital Network (ISDN) and Public Switched Telecommunications Network (PSTN). only simple solutions are assumed for solving the service interaction problems between IN and ISDN/PSTN. ETS 300 009 (1994): "Integrated Services Digital Network (ISDN). Application of the ISDN User Part (ISUP) of CCITT Signalling System No.
[2]
[3]
[4]
[6]
.7.
2
Normative references
This ETS incorporates by dated and undated reference. It is intended as a guide to implementors and network operators to ensure interworking between different manufacturers equipment for the following IN CS1 defined interfaces (SCF-SSF and SCF-SRF).7. For dated references. one (DSS1) protocol. [1] ETS 300 008 (1993): "Integrated Services Digital Network (ISDN). For undated references the latest edition of the publication referred to applies. Specialized Resource Function (SRF).1215 (1993)]". Transaction Capabilities Application Part (TCAP) version 2".

the definition of the actions taken at each entity (Clause 7). and the actions are defined in terms of state transition diagrams.
. The interface between remotely located SCF and SDF is INAP using TCAP which in turn uses the services of the connectionless SCCP and MTP (see figure 1). It is the responsibility of network operators and equipment manufacturers to decide how to co-locate FEs to the best possible advantage as this may vary between manufacturers and between network operators.
-
The SACF/MACF rules are defined in prose. the only standardized way to encode the resulting PDUs is the Basic Encoding Rules (see CCITT Recommendation X.229 [17]).1.Page 18 ETS 300 374-1: September 1994
4
4. Other supporting protocols may be added at a later date. The figures depicted in this subclause show how INAP would be supported in an Signalling System No. NOTE 1: At present. the typical SRF control procedures to be applied are shown in subclause 7. the definition of the operations transferred between entities (Clause 6). Further guidance on the actions to be performed on receipt of an operation can be gained from Clause 6 and from the relevant detailed procedures in Clause 7. see CCITT Recommendation X.1. see ETS 300 287 [5]). The operation definitions are in Abstract Syntax Notation 1 (ASN. see ETS 300 348 [6] (ITU-T Recommendation Q.7 may be used as the network protocol to support INAP. it is to be understood as representing the TCAP functionalities associated with a single dialogue and transaction (as opposed to a TCAP entity). At present. For each physical scenario.7) and in the Q.931 FACILITY and Call Control messages in DSS1 (see ETS 300 4031 [8]).
NOTE 2:
4.1215).7 (Signalling System No.2
Example physical scenarios
The protocol supports any mapping of functional to Physical Entities (PEs).219 [16] and X. The INAP (as a ROSE user) and the ROSE protocol have been specified using ASN. This does not imply that only Signalling System No. When TCAP appears in one of the following figures.e.3. Therefore the protocol is defined assuming maximum distribution (i. see ETS 300 196-1 [4]) and the Component Sublayer of the Transaction Capabilities Application Part (TCAP. The INAP is a Remote Operations Service Element (ROSE) user protocol (see CCITT Recommendations X. The ROSE protocol is contained within the Digital Subscriber Signalling System No.208 [14]).7 network environment. one PE per FE).209 [15]).5. One (DSS1. the ROSE Application Protocol Data Units (APDUs) are conveyed in Transaction sublayer messages in Signalling System No. The SDF is responsible for any interworking to other protocols to access other types of networks.1
General
Definition methodology
The definition of the protocol is split into three Clauses: the definition of the Single/Multiple Association Control Function (SACF/MACF) rules for the protocol (Clause 5).

In case a. In case b.Page 25 ETS 300 374-1: September 1994 4. each of which interacts with an SAO in a remote PE. Each operation is specified using the operation macro described in figure 8. (based on the order of received primitives). Each ASE supports one or more operations. which includes the ordering of operations supported by ASE(s).3 INAP protocol architecture
Many of the terms used in this subclause are based on the OSI Application Layer Structure as defined in ISO 9545 [18]. The Single Association Object (SAO) represents the SACF plus a set of ASEs to be used over a single interaction between a pair of PEs. MACF provides a co-ordinating function among several SAOs.
SCCP MTP
Figure 7: INAP protocol architecture A PE has either single interactions (case a) or multiple co-ordinated interactions (case b) with other PEs.
.1214 [11] and Clause 7 of this ETS). Description of each operation is tied with the action of corresponding FE modelling (see ITU-T Recommendation Q. The INAP protocol architecture can be illustrated as shown in figure 7. SACF provides a co-ordination function in using Application Service Elements (ASEs).
Multiple Co-ordinated Interactions (case b)
Single Interaction (case a)
Application Process
Application Process
MACF SAO S A C F ASE's TCAP S A C F SAO SAO
or
ASE's
TCAP
S A C F
ASE's TCAP
SCCP MTP
NOTE: INAP is the collection of specifications of all IN ASEs.

11). InitialDP and InitiateCallAttempt) into the affected direction in several steps.. on receipt of N-PCSTATE indication primitive with the information "signalling point congested" from SCCP.Page 26 ETS 300 374-1: September 1994 INAP User ASE's xyz OPERATION ARGUMENT {Parameter1.} etc
Operations Results Errors
TCAP ASE
INVOKE RETURN RESULT RETURN ERROR REJECT BEGIN CONTINUE END ABORT UNIDIRECTIONAL
COMPONENT SUB-LAYER
to peer
TRANSACTION SUB-LAYER
to peer
CONNECTIONLESS SCCP Figure 8: Operation description The use of the Application Context (AC) negotiation mechanism (as defined in ETS 300 287 [5]) allows the two communicating entities to identify exactly what their capabilities are and also what the capabilities required on the interface should be... Parameter2.767. 4..2.3.. i...} ERRORS {error1. Regardless of the above.} RESULT {Parameter1. operation4.. The INAP procedures for signalling congestion control shall as far as possible be aligned with the ISDN User Part signalling congestion control procedures as specified in ETS 300 121 [3] (CCITT Recommendation Q.e.
. If the indication of a specific AC is not supported by a pair of communicating FEs. the correct point code) regardless of which network it is in. any addressing scheme supported by the SCCP may be used... Parameter2..1 INAP signalling congestion control for Signalling System No. 4... it is the choice of the network operator/implementor as to which Sub-System Number(s) (SSN(s)) are assigned to INAP. § D. Parameter7.} LINKED {operation3.g. The above procedure may only apply to traffic which uses MTP Point Code addressing in the affected direction. some mechanism to pre-arrange the context shall be supported. error2.4 INAP addressing
SCCP Global Title (see ETS 300 009 [2]) and MTP Point Code addressing (see ETS 300 008 [1]) ensure that PDUs reach their physical destination (i. the INAP shall reduce the traffic load (e.. Within a node..e.7
The same type of procedure shall apply as defined for ISDN User Part signalling congestion control. This should be used to allow evolution through capability sets.}
to peer
error1 ERROR PARAMETER {Parameter6.

4.1218 [12] INAP. tagging of ETSI INAP additions to ITU-T Recommendation Q. it is acceptable that the addressed function is executed in either the older or the modified variant. the SCF shall apply the normal error handling for unknown operations or parameters except for parameters in the InitialDP operation.1218 INAP
On receipt of an operation according to ITU-T Recommendation Q. the normal error handling procedures as specified in Clause 10 shall be followed.
-
Additionally.2 Procedures for major additions to ETSI INAP
In order to support the introduction of major functional changes. 4. in order to avoid complicated
. compatibility with future versions of ETSI INAP.6. No new AC is expected to be defined for this type of change.2. In case it is a modification of an existing function.1 Compatibility mechanisms used for INAP Introduction
This subclause specifies the compatibility mechanisms that shall be used for INAP. in this subclause referred to as ETSI INAP to avoid confusion with INAP according to ITU-T Recommendation Q. At the time of definition.2. the protocol allows a synchronization between the two applications with regard to which functionality is to be performed. This synchronization takes place before the new function is invoked in either application entity. it is acceptable that it is not executed at all and that the peer Application Entity (AE) need not know about the effects of the change.e. the requested IN service will not be provided if one of the application entities does not support the additional functionality. For minor changes. For major changes. network specific changes to ETSI INAP: these additions may be of either the major or minor type for a service.Page 28 ETS 300 374-1: September 1994 4. i.
The second category has three sub-categories of compatibility dealt with in this subclause: minor changes to the ETSI INAP in future standardized versions: a minor change can be defined as a change of a functionality which is not essential for the requested IN service.1218 [12] are specified from 30 downwards to avoid overlap with future additions in ITU-T Recommendation Q. In case it is a modification of an existing function.1 Definition of ETSI INAP compatibility mechanisms Compatibility mechanism for interworking of ETSI INAP and ITU-T Q.6 4.2 4.6.6.1218 [12] which is not part of the ETSI INAP or is part of the ETSI INAP but which contains parameters which are not part of the ETSI INAP: the SSF shall apply the normal error handling for unknown operations or parameters. major changes to the ETSI INAP in future standardized versions: a major change can be defined as a change of a functionality which is essential for the requested IN service. a new AC is not required. If the change is purely additional.6.1218 [12]. both application entities shall have a shared knowledge about the addressed functional variant. the additions would not be expected to be included in identical form in future versions of the ETS. those not included in the ETSI INAP shall be ignored.1218 [12] for InitialDP shall be known by the SCF. a new AC is required. If the change is purely additional. All parameters specified in ITU-T Recommendation Q.1218 [12] version of CS1 INAP. Two major categories of compatibility are handled by these mechanisms: compatibility with the ITU-T Recommendation Q.

6. the marker is placed within a comment for now so that it can easily be uncommented later.6. Where it is impossible to execute one of the operations identified above until some other operation has progressed to some extent or finished.
The method of indicating that operations are to be synchronized is to include them in the same message. Each extension is associated with a value that defines whether the terminating node should ignore the field if unrecognized. If the AC is not acceptable.2 Sequential/parallel execution of operations
In some cases.1 as defined in CCITT Recommendation X.
6
Abstract syntax of the CS1 INAP
This Clause specifies the abstract syntax for the CS1 INAP. it may be necessary to distinguish whether operations should be performed sequentially or in parallel (synchronized).1
Single/Multiple Association Control Function (SACF/MACF) rules
Reflection of TCAP Application Context (AC)
TCAP AC negotiation rules require that the proposed AC. When an entity receives unrecognized parameters that occur after the marker. In case of inconsistency between the above mentioned generic rules and the FE-specific rules as specified in Clause 7. they are ignored. As in the ISO case. similar to the comprehension required mechanism described in the previous subclause. This mechanism implements extensions differently by including an "extensions marker" in the type definition. 4. but simply that where it could make sense to do so (in the situations identified above) the operations should be synchronized. Operations which may be synchronized are: charging operations may be synchronized with any other operation. 5. or reject the message. using ASN.
5
5. NOTE: Because this version of ASN.2. This method does not imply that all operations sent in the same message should be executed simultaneously. and the TC-User does not wish to continue the dialogue.1400 [13] for a definition of this mechanism. Procedures for inclusion of network specific additions to ETSI INAP
4.2.Page 29 ETS 300 374-1: September 1994 fall-back procedures. in which case they can be ignored. Refer to ETS 300 287 [5] for a more detailed description of the TCAP AC negotiation mechanism. where an extension can contain any type. it may provide an alternate AC to the initiator which can be used to start a new dialogue.
.1 at the outermost level of a type definition. The extensions are expressed by optional fields that are placed after the marker.4
This mechanism is based on the ability to explicitly declare fields of any type via the Macro facility in ASN. Refer to ITU-T Recommendation Q. This extension field is defined as a set of extensions. It works by defining an "ExtensionField" that is placed at the end of the type definition.208 [14]. the sending PE (usually SCP) can control this by sending the operations in two separate messages. is reflected in the first backwards message. the extensions are expressed by optional fields that are placed after the marker (which is commented out).3 Procedures for minor additions to ETSI INAP
The extension mechanism marker shall be used for future standardized minor additions to INAP. TCAP AC negotiation applies only to the SCF interfaces. the FE-specific rules take precedence over the generic rules. The solution chosen to achieve such a synchronization is use of the AC negotiation provided in ETS 300 287 [5]. if acceptable.1 has not yet been ratified by ITU-T.

1. class 4: neither RESULT nor ERRORS appears in the ASN.Page 30 ETS 300 374-1: September 1994 The encoding rules which are applicable to the defined abstract syntax are the Basic Encoding Rules for ASN. The DSS1/ISUP defined parameter identifiers are removed and replaced by the INAP defined parameter identifiers. defined in CCITT Recommendation X. modified by ETS 300 287 [5]. The module containing the operation codes and error codes for INAP is IN-CS1-Codes and is described in subclause 6.1218 [12] and not used in this ETS shall be regarded as reserved. The mapping of OPERATION and ERROR to TCAP components is defined in ITU-T Recommendation Q.1 OPERATION MACRO definition.219 [16] and ETS 300 196-1 [4] (ITU-T Recommendation Q. class 3: only RESULT appears in the ASN.4.5.209 [15] with the restrictions as described in ITU-T Recommendation Q. class 2: only ERRORS appears in the ASN. The abstract syntax for INAP is composed of several ASN.3. These map to the classes 2 through 5.1 modules describing operations. respectively.932). and associated data types. as follows: class 1: both RESULT and ERRORS appear in the ASN. only the coding of the parameter value is coded as defined in ISUP or DSS1.1 OPERATION MACRO. Any tags and values used in the ITU-T Recommendation Q.
.1.1.1 OPERATION MACRO definition. errors.1 OPERATION MACRO definition. The module containing all the type definitions for INAP errors is IN-CS1-Errors and is described in subclause 6.1 OPERATION MACRO definition.773 [10] modified by ETS 300 287 [5]. Additional encodings are cited for parameters used in existing ISUP (ETS 300 356-1 [7]) and DSS1 (ETS 300 403-1 [8]) standards.1.773 [10].2. All the AC definitions for core INAP are described in subclause 6. The module containing all the type definitions for INAP data types is IN-CS1-DataTypes and is described in subclause 6. The class of an operation is not stated explicitly but is specified in the ASN. The module containing all the type definitions for INAP operations is IN-CS1-Operations and is described in subclause 6. § 4. specified in CCITT Recommendation X. The values (operation codes and error codes) are defined in a separate module. For the ISUP and DSS1 parameters used in the INAP.

::= OPERATION
ActivityTest RESULT -----
Direction: SCF -> SSF. UnexpectedDataValue. ParameterOutOfRange. Simple registration functionality (counters) and announcement control may be located at the SSF. TaskRefused }
ApplyCharging ARGUMENT
----
Direction: SCF -> SSF. It is used for example for providing televoting or mass calling services. The operation initializes the specified counters in the SSF. then the SSF will respond. The ApplyChargingReport operation provides the feedback from the SSF to the SCF. UnexpectedComponentSequence.Page 32 ETS 300 374-1: September 1994
--TYPE DEFINITIONS FOR IN CS1 OPERATIONS FOLLOW SCF-SSF operations
ActivateServiceFiltering ::= OPERATION ARGUMENT ActivateServiceFilteringArg RESULT ERRORS { MissingParameter. UnexpectedDataValue. SystemFailure. UnexpectedParameter. UnexpectedDataValue. UnexpectedComponentSequence. TaskRefused. MissingParameter. UnexpectedParameter. If the relationship is still in existence. then the SCF will assume that the SSF has failed in some way and will take the appropriate action. ParameterOutOfRange.
AssistRequestInstructions ::= OPERATION ARGUMENT AssistRequestInstructionsArg ERRORS { MissingCustomerRecord. TaskRefused } ---Direction: SSF -> SCF. UnexpectedParameter }
. UnexpectedComponentSequence. SystemFailure. Timer: Tac This operation is used for interacting from the SCF with the SSF charging mechanisms. TaskRefused. SystemFailure. UnexpectedParameter } -----Direction: SCF -> SSF. Timer: Tat This operation is used to check for the continued existence of a relationship between the SCF and SSF. ParameterOutOfRange. Timer: Tasf When receiving this operation. UnexpectedComponentSequence. the SSF handles calls to destination in a specified manner without sending queries for every detected call. If no reply is received.
ApplyChargingReport ::= OPERATION ARGUMENT ApplyChargingReportArg ERRORS { MissingParameter. ::= OPERATION ApplyChargingArg ERRORS { MissingParameter. Timer: Tacr This operation is used by the SSF to report to the SCF the occurrence of a specific charging event as requested by the SCF using the ApplyCharging operation.

Timer: Tcg This operation is used to request the SSF to reduce the rate at which specific service requests are sent to the SCF. UnexpectedParameter }
Connect
. TaskRefused. ParameterOutOfRange. UnexpectedParameter } ---Direction: SCF -> SSF. SystemFailure. ::= OPERATION ARGUMENT CallGapArg ---Direction: SCF -> SSF. when the initiating SSF has set up a connection to the SRF or to the assisting SSF as a result of receiving an EstablishTemporaryConnection or Connect (in case of hand-off) operation from the SCF. Timer: Tci This operation is used to request the SSF to perform the originating basic call processing actions to prompt a calling party for destination information. for virtual private networks). Timer: Tcan This generic operation cancels the correlated previous operation or all previous requests. UnexpectedDataValue. UnexpectedComponentSequence.Page 33 ETS 300 374-1: September 1994
-----Direction: SSF -> SCF or SRF -> SCF. Timer: Tari This operation is used when there is an assist or a hand-off procedure and may be sent by the SSF or SRF to the SCF. RequestedInfoError.
CallGap
CallInformationReport ::= OPERATION ARGUMENT CallInformationReportArg ---Direction: SSF -> SCF.g. SystemFailure. TaskRefused. SystemFailure.
Cancel
CollectInformation ::= OPERATION ARGUMENT CollectInformationArg ERRORS { MissingParameter. TaskRefused.
CallInformationRequest ::= OPERATION ARGUMENT CallInformationRequestArg ERRORS { MissingParameter. UnexpectedComponentSequence. Timer: Tcirq This operation is used to request the SSF to record specific information about a single call and report it to the SCF (with a callInformationReport operation).. Timer: Tcirp This operation is used to send specific call information for a single call to the SCF as requested by the SCF in a previous callInformationRequest. UnexpectedDataValue. ::= OPERATION ARGUMENT ConnectArg ERRORS { MissingParameter. ::= OPERATION ARGUMENT CancelArg ERRORS { CancelFailed } ----Direction: SCF -> SRF or SCF -> SSF. then collect destination information according to a specified numbering plan (e. UnexpectedComponentSequence. This operation is sent by the SSF or SRF to the SCF. The following operations can be cancelled: PlayAnnouncement and PromptAndCollectUserInformation. UnexpectedParameter } ----Direction: SCF -> SSF.

. UnexpectedDataValue. The SSF continues call processing without substituting new data from SCF. ::= OPERATION
Continue -----
Direction: SCF -> SSF.. Timer: Tenc This operation is used by the SSF to report to the SCF the occurrence of a specific charging event type as previously requested by the SCF in a RequestNotificationChargingEvent operation. dialled digits) and existing call setup information (e.5).
EventReportBCSM ARGUMENT
. Timer: Tcue This operation is used to request the SSF to proceed with call processing at the DP at which it previously suspended call processing to await SCF instructions (i. SystemFailure.. To do so. TaskRefused. UnexpectedComponentSequence. UnexpectedParameter } ---Direction: SCF -> SSF. SystemFailure. it implies the use of the assist procedure. Timer: Tcon This operation is used to request the SSF to perform the call processing actions to route or forward a call to a specified destination. BCSM events such as busy or no answer) previously requested by the SCF in a RequestReportBCSMEvent operation. the SSF may or may not use destination information from the calling party (e. to play an announcement. UnexpectedParameter } --Direction: SCF -> SSF. UnexpectedComponentSequence.Page 34 ETS 300 374-1: September 1994
-----Direction: SCF -> SSF.g.
EventNotificationCharging ::= OPERATION ARGUMENT EventNotificationChargingArg -----Direction: SSF -> SCF.g. ::= OPERATION EventReportBCSMArg ---Direction: SSF -> SCF. UnexpectedComponentSequence } --Direction: SCF -> SSF. Timer: Tetc This operation is used to create a connection to a resource for a limited period of time (e. to collect user information). Timer: Tdfc This operation is used to disconnect a forward temporary connection
or a connection to a resource. UnexpectedDataValue. route index to a list of trunk groups). depending on the information provided by the SCF. TaskRefused.g.
EstablishTemporaryConnection ::= OPERATION ARGUMENT EstablishTemporaryConnectionArg ERRORS { ETCFailed.
ConnectToResource ::= OPERATION ARGUMENT ConnectToResourceArg ERRORS { MissingParameter. Clause B.
DisconnectForwardConnection ::= OPERATION ERRORS { SystemFailure..e. MissingParameter.g. proceed to the next point in call in the BCSM). Timer: Terb This operation is used to notify the SCF of a call-related event (e. The operation supports the capabilities to cope with the interactions concerning charging (refer to Annex B. Timer: Tctr This operation is used to connect a call from the SSP to the PE containing the SRF. TaskRefused.

4 (refer to Annex B where these are defined). UnexpectedParameter } --Direction: SSF -> SCF. Timer: Tica This operation is used to request the SSF to create a new call to one call party using address information provided by the SCF.
ReleaseCall ARGUMENT
RequestNotificationChargingEvent ::= OPERATION ARGUMENT RequestNotificationChargingEventArg ERRORS { MissingParameter. Timer: Tfci This operation is used to request the SSF to generate. The operation supports the capabilities to cope with the interactions concerning charging (refer to Annex B. UnexpectedParameter } ---Direction: SCF -> SSF. The charging scenarios supported by this operation are: 2. Timer: Trc This operation is used to tear down an existing call at any phase of the call for all parties involved in the call. SystemFailure. TaskRefused. register a call record or to include some information in the default call record. The registered call record is intended for off-line charging of the call. UnexpectedComponentSequence. MissingParameter. Clause B. TaskRefused. UnexpectedComponentSequence. UnexpectedParameter } -----Direction: SCF -> SSF.3 and 2. ::= OPERATION InitialDPArg ERRORS { MissingCustomerRecord. TaskRefused. UnexpectedDataValue.
.
InitialDP ARGUMENT
InitiateCallAttempt ::= OPERATION ARGUMENT InitiateCallAttemptArg ERRORS { MissingParameter. UnexpectedParameter } -----Direction: SCF -> SSF. UnexpectedComponentSequence.2. 2. Timer: Tidp This operation is used after a TDP to indicate request for service. Timer: Trnc This operation is used by the SCF to instruct the SSF on how to manage the charging events which are received from other FEs and not under control of the service logic instance. ::= OPERATION ReleaseCallArg ---Direction: SCF -> SSF. SystemFailure. SystemFailure. UnexpectedDataValue.5). TaskRefused.Page 35 ETS 300 374-1: September 1994
FurnishChargingInformation ::= OPERATION ARGUMENT FurnishChargingInformationArg ERRORS { MissingParameter. UnexpectedDataValue. UnexpectedComponentSequence. UnexpectedDataValue.

. UnexpectedParameter } --Direction: SCF -> SSF. UnexpectedComponentSequence. UnexpectedParameter. In the local exchange this information may be used to update the charge meter or to create a standard call record.
--------
SCF-SRF operations AssistRequestInstructions SRF -> SCF Refer to previous description of this operation in the SCF-SSF operations subclause. UnexpectedParameter } ----Direction: SCF -> SSF. BCSM events such as busy or no answer). ::= OPERATION ResetTimerArg ERRORS { MissingParameter. UnexpectedComponentSequence. SystemFailure. Timer: Trt This operation is used to request the SSF to refresh an application timer in the SSF.2 (refer to Annex B where these are defined). Timer: Tsfr This operation is used to send back to the SCF the values of counters specified in a previous ActivateServiceFiltering operation.Page 36 ETS 300 374-1: September 1994
RequestReportBCSMEvent ::= OPERATION ARGUMENT RequestReportBCSMEventArg ERRORS { MissingParameter.
ServiceFilteringResponse ::= OPERATION ARGUMENT ServiceFilteringResponseArg ---Direction: SSF -> SCF. TaskRefused. UnexpectedDataValue. The charging information can either be sent back by means of signalling or internal if the SSF is located in the local exchange. UnexpectedComponentSequence. UnknownLegID } ------Direction: SCF -> SSF. ParameterOutOfRange.g.. Timer: Tsci This operation is used to instruct the SSF on the charging information to be sent by the SSF. UnexpectedDataValue.
ResetTimer ARGUMENT
SendChargingInformation ::= OPERATION ARGUMENT SendChargingInformationArg ERRORS { MissingParameter. Cancel SCF -> SRF Refer to previous description of this operation in the SCF-SSF operations subclause. then send a notification back to the SCF when the event is detected. The charging scenario supported by this operation is scenario 3. TaskRefused. TaskRefused. SystemFailure. Timer: Trrb This operation is used to request the SSF to monitor for a call-related event (e.

UnavailableResource. The timer associated with this operation must be of a sufficient duration to allow its linked operation to be correctly correlated.
. SystemFailure. the SRF is always collocated with the SSF in the switch.
SpecializedResourceReport ::= OPERATION ARGUMENT SpecializedResourceReportArg ---END Direction: SRF -> SCF. UnexpectedComponentSequence.Page 37 ETS 300 374-1: September 1994
PlayAnnouncement ARGUMENT PlayAnnouncementArg ERRORS { Cancelled. UnavailableResource.) or standard announcements. UnexpectedComponentSequence. Timer: Tpa This operation is to be used after Establish Temporary Connection (assist procedure with a second SSP) or a Connect to Resource (no assist) operation. UnexpectedParameter } --Direction: SCF -> SRF. It may be used for inband interaction with an analogue user. Any error is returned to the SCF. SystemFailure. In the latter case. UnexpectedParameter } LINKED { SpecializedResourceReport } --------Direction: SCF -> SRF. UnexpectedDataValue. or for interaction with an ISDN user. UnexpectedDataValue. In the former case. MissingParameter. Timer: Tsrr This operation is used as the response to a PlayAnnouncement operation when the announcement completed report indication is set. MissingParameter. TaskRefused. ::= OPERATION
PromptAndCollectUserInformation ::= OPERATION ARGUMENT PromptAndCollectUserInformationArg RESULT ReceivedInformationArg ERRORS { Cancelled. the SRF is usually collocated with the SSF for standard tones (congestion tone etc. Timer: Tpc This operation is used to interact with a user to collect information. ImproperCallerResponse.

The definitive value for each operation timer may be network specific and has to be defined by the network operator. 1 second to 30 minutes.
Table 3 lists all operation timers and the value range for each timer.Page 38 ETS 300 374-1: September 1994 Operation timers The following value ranges apply for operation specific timers in INAP: short: medium: long: 1 to 10 seconds. 1 to 60 seconds. Table 3 Operation Name ActivateServiceFiltering ActivityTest ApplyCharging ApplyChargingReport AssistRequestInstructions CallGap CallInformationReport CallInformationRequest Cancel CollectInformation Connect ConnectToResource Continue DisconnectForwardConnection EstablishTemporaryConnection EventNotificationCharging EventReportBCSM FurnishChargingInformation InitialDP InitiateCallAttempt ReleaseCall RequestNotificationChargingEvent RequestReportBCSMEvent ResetTimer SendChargingInformation ServiceFilteringResponse PlayAnnouncement PromptAndCollectUserInformation SpecializedResourceReport Timer Tasf Tat Tac Tacr Tari Tcg Tcirp Tcirq Tcan Tci Tcon Tctr Tcue Tdfc Tetc Tenc Terb Tfci Tidp Tica Trc Trnc Trrb Trt Tsci Tsfr Tpa Tpc Tsrr value range medium short short short short short short short short medium short short short short medium short short short short short short short short short short short long long short
.

12:15:01 would be encoded as: Bits HGFE DCBA leading octet 3 9 9 0 0 3 2 1 5 1 1 0 ::= SEQUENCE SIZE (1) OF CalledPartyNumber
DestinationRoutingAddress -Indicates the Called Party Number. maxDigitsLength))
Indicates the address signalling digits. calledAddressValue for all occurrences. amongst others. AdditionalCallingPartyNumber for InitialDP.22)
CountersValue CutAndPaste ---
Indicates the number of digits to be deleted. The usage is service dependent.Page 46 ETS 300 374-1: September 1994
---The use of voiceBack is network operator specific. the ASN. ::= OCTET STRING (SIZE(6))
DateAndTime -----------
Indicates. digitsResponse ReceivedInformationArg ::= IA5String (SIZE (minDisplayInformationLength . The first octet contains YY and the remaining items are sequenced following.1214 [11].numOfCounters) OF CounterAndValue ::= INTEGER (0.. The following parameter should use Generic Number: CorrelationID for AssistRequestInstructions. manuallyInitiated(1) -.16. Refer to Clause 7 for a description of the procedures associated with this parameter. maxDisplayInformationLength))
DisplayInformation
--
Indicates the display information. callingAddressValue for all occurrences The following parameters should use Generic Digits: all other CorrelationID occurrences.. [1] Integer4
CounterAndValue counterID counterValue } CounterID ---
::= INTEGER (0.2..1 tags are sufficient to identify the parameter. therefor the value is network operator specific. one digit per OCTET only.
Digits ------------------
::= OCTET STRING (SIZE (minDigitsLength . cancelDigit..99)
Indicates the counters to be incremented. contained in the four least significant bits of each OCTET.
. and startDigit parameters have been designated as OCTET STRING.other values ffs } CorrelationID --::= ENUMERATED {
::= Digits
used by SCF for correlation with a previous operation. the start time for activate service filtering. ::= SEQUENCE SIZE(0. ::= SEQUENCE { [0] CounterID.
CollectedInfo ::= CHOICE { collectedDigits [0] CollectedDigits } ControlType sCPOverloaded(0). Coded as YYMMDDHHMMSS with each digit coded BCD.. for additional information. The coding of the subfields "NumberQualifier" in Generic Number and "Type Of Digits" in Generic Digits are irrelevant to the INAP. The endOfReplyDigit. number VariablePart. § 6.4. and are to be encoded as BCD. EXAMPLE: 1993 September 30th. Refer to ITU-T Recommendation Q. The ISUP format does not allow to exclude these subfields. The counterIDs can be addressed by using the last digits of the dialed number. Refer to the ETS 300 356-1 [7] Generic Number and Generic Digits parameters for encoding. AssistingSSPIPRoutingAddress for EstablishTemporaryConnection.

Indicates the BCSM detection point event. Refer to ITU-T Recommendation Q.1214 [11], § 4.2.2.2 for additional information on the events. Values origAttemptAuthorized and termAttemptAuthorized can only be used for TDPs. ::= OCTET STRING (SIZE (minEventTypeChargingLength .. maxEventTypeChargingLength))

If releaseCause is not present, the default value is the same as the ISUP cause value decimal 31. If informationToSend is present, the call will be released after the end of the announcement with the indicated or default releaseCause. If maximumNumberOfCounters is not present, ServiceFilteringResponse will be sent with CountersValue ::= SEQUENCE SIZE (0) OF CounterAndValue

FilteringCharacteristics ::= CHOICE { interval [0] INTEGER (-1..32000), numberOfCalls [1] Integer4 } ------Indicates the severity of the filtering and the point in time when the ServiceFilteringResponse is to be sent. If = interval, every interval of time the next call leads to an InitialDP and a ServiceFilteringResponse is sent to the SCF. The interval is specified in seconds.If = NumberOfCalls, every N calls the Nth call leads to an InitialDP and a ServiceFilteringResponse is sent to the SCF. If ActivateServiceFiltering implies several counters (filtering on several dialled numbers), the numberOfCalls would include calls to all the dialled numbers.

In case calledAddressValue is specified, the numbers to be filtered are from calledAddressValue up to and including calledAddressValue +maximumNumberOfCounters-1. The last two digits of calledAddressValue cannot exceed 100-maximumNumberOfCounters. ::= CHOICE {

Indicates the gapping characteristics. No gapping when gapInterval equals 0, and gap all calls when gapInterval equals -1. For further information regarding the meaning of specific values of duration and gapInterval refer to the detailed procedure of the CallGap operation in Clause 9.

interval is the time in seconds between each repeated announcement. Duration is the total amount of time in seconds, including repetitions and intervals. The end of announcement is either the end of duration or numberOfRepetitions, whatever comes first. Duration with value 0 indicates infinite duration. ::= CHOICE { [0] InbandInfo, [1] Tone, [2] DisplayInformation

-- used in operations sent from SCF to SSF -- used in operations sent from SSF to SCF

--------

Indicates a reference to a specific party in a call. OPTIONAL denotes network operator specific use with unilateral ID assignment. OPTIONAL for LegID also denotes the following: - when only one party exists in the call, this parameter is not needed (as no ambiguity exists). - when more than one party exists in the call, one of the following alternatives applies: 1) LegID is present and indicates which party is concerned. 2) LegID is not present and a default value is assumed (e.g., calling party in the case of the ApplyCharging operation). ::= OCTET STRING (SIZE(1)) leg1 LegType leg2 LegType ::= '01'H ::= '02'H ::= OCTET STRING (SIZE (minLocationNumberLength .. maxLocationNumberLength))

LegType

LocationNumber

--

Indicates the Location Number for the calling party. Refer to ETS 300 356-1 [7] for encoding.

Indicates the event is relayed and/or processed by the SSP. If this parameter is used in the context of charging events, the following definitions apply for the handling of charging events: Interrupted means that the SSF notifies the SCF of the charging event using EventNotificationCharging and does not process the event but discard it. NotifyAndContinue means that SSF notifies the SCF of the charging event using EventNotificationCharging and continues processing the event or signal without waiting for SCF instructions. Transparent means that the SSF does not notify the SCF of the event. This value is used to end the monitoring of a previously requested charging event. Previously requested charging events are monitored until ended by a transparent monitor mode, or until the end of the connection configuration. For the use of this parameter in the context of BCSM events is referred to subclauses 9.17 and 9.25. ::= INTEGER(1..255)

NumberOfDigits --

Indicates the number of digits to be collected. ::= OCTET STRING (SIZE (minOriginalCalledPartyIDLength .. maxOriginalCalledPartyIDLength))

OriginalCalledPartyID

--

Indicates the original called number. Refer to ETS 300 356-1 [7] Original Called Number for encoding. ::= OCTET STRING (SIZE (minRedirectingPartyIDLength .. maxRedirectingPartyIDLength))

the ASEs interface to TCAP to communicate with the SCF.1. In case interpretations for the AE procedures defined in the following differ from detailed procedures and the rules for using of TCAP service.2 Model and interfaces
The functional model of the AE-SSF is shown in figure 9. the statements and rules contained in the detailed Clauses 9 and 10 shall be followed.
NOTE:
The SSF Finite State Model (FSM) includes several Finite State Machines. includes TCAP and one or more ASEs called TCusers.1400 [13]. Capabilities not explicitly covered by these procedures may be supported in an implementation dependent manner in the SSP. such as DSS1 (layer 3). may be used.7. DSS1. layer 3). The procedures are based on the use of Signalling System No.g. following the architecture defined in ITU-T Recommendations Q. other signalling systems may be used (e. The following subclauses define the TC-user ASE which interfaces with TCAP using the primitives specified in ETS 300 287 [5] (ITU-T Recommendation Q. other signalling systems.700 [9] and Q.Page 60 ETS 300 374-1: September 1994
7
7.1 7. The AE. The scope of this ETS is limited to the shaded area in figure 9.771).771). 7.1
Application entity procedures
SSF application entity procedures General
This subclause provides the definition of the SSF AE procedures related to the SSP-SCP interface.
Figure 9: Functional model of SSF AE
. and ETS 300 287 [5] (ITU-T Recommendation Q. The procedure may equally be used with other signalling message transport systems supporting the Application Layer structures defined. while remaining in line with Clause 6 of this ETS.1. and interface to the Call Control Function (CCF) and the maintenance functions already defined for switching systems.

§ 4. § 4. if an initiateCallAttempt is received from the SCF.711) (interface (2)).2.3 Relations between SSF FSM and the CCF and maintenance functions
The primitive interface between the SSF FSM and the CCF/maintenance functions is an internal interface and is not subject to standardization in CS1. The operations and parameters of INAP are defined in Clause 6 of this ETS. an instance of a BCSM is created. The SSME comprises a SSME-Control and several instances of SSME FSMs. an instance of an SSF FSM is created. If a DP is armed as a Trigger Detection Point (TDP).1214 [11]. see ITU-T Recommendation Q.
-
The management functions related to the execution of operations received from the SCF are executed by the SSF Management Entity (SSME).1. The relationship between the BCSM and the SSF FSM may be described as follows for the case of a call/attempt initiated by an end user. Nevertheless.1. As the BCSM proceeds.2. 7.Page 61 ETS 300 374-1: September 1994 The interfaces shown in figure 9 use the TC-user ASE primitives specified in ETS 300 287 [5] (ITU-T Recommendation Q.2). this interface should be in line with the Basic Call State Model (BCSM) defined in ITU-T Recommendation Q. and the case of a call/attempt initiated by IN Service Logic (SL): when a call/attempt is initiated by an end user and processed at an exchange. The SSME-control interfaces the different SSF FSMs and SSME FSMs respectively and the Functional Entity Access Manager (FEAM). as well as an instance of an SSF FSM.771) (interface (1)) and N-Primitives specified in ETS 300 009 [2] (ITU-T Recommendation Q.1214 [11]. Figure 10 shows the SSF interfaces. an instance of a BCSM is created.
Figure 10: SSF interfaces
. it encounters Detection Points (DPs.

g. invocation. captures asynchronous (with call processing) activities related to management or supervisory functions in the SSF and creates an instance of a SSME FSM. the SSME provides non-call associated treatment due to changes in Service Filtering or Call Gapping. Consistent with the single-ended control characteristic of IN service features for CS1. For example. the SSME-control separates the SSF FSM from the Call Gapping and Service Filtering functions by creating instances of SSME FSMs for each context of management related operations. but not both). translates the SSF FSM outputs into corresponding messages to other FEs. ActivateServiceFiltering operations providing different "filteringCriteria" cause the invocation of new SSME FSMs. the SSF FSM only applies to a functionally separate call portion (e. all ActivateServiceFiltering operations using the same address.Page 62 ETS 300 374-1: September 1994 The FEAM provides the low level interface maintenance functions including the following: establishing and maintaining the interfaces to the SCF and SRF.
-
The SSME-control maintains the dialogues with the SCF. These instances of the SSF FSM occur concurrently and asynchronously as calls occur. address the same SSME FSM handling this specific service filtering instance. which explains the need for a single entity that performs the task of creation. i. the originating BCSM or the terminating BCSM in a two-party call. and the SSF FSM may be terminated while the BCSM continues to handle the call as needed. and sending the messages received from the SSMEControl to the SCF and SRF. DPs may be dynamically armed as Event DPs. A later TDP in the BCSM may result in a new instance of the SSF FSM for the same call.
-
The different contexts of the SSME FSMs may be distinguished based on the address information provided in the initiating operations. Therefore. For example. and maintenance of the SSF FSMs. queueing (when necessary). In the case of service filtering this address information is given by "filteringCriteria". The SSF FSM passes call handling instructions to the related instances of the BCSM as needed.. In particular the SSME-control performs the following tasks: interprets the input messages from other FEs and translates them into corresponding SSF FSM events. At some point.
. and SRF on behalf of all instances of the SSF FSM. formatting. passing and queueing (when necessary) the messages received from the SCF and SRF to the SSME-Control. further interaction with the SCF is not needed.e. requiring the SSF FSM to remain active.

the SSF needs to send a Service Filtering Response to the SCF: the SSME FSM remains in this state (transition em3). if Call Gap related duration timer expires.4 SSF Management Entity (SSME) FSM
The SSME FSM State Diagram is described in figure 11. which has the same gapping/filtering criteria: the second "filter" or "gap" replace the first one (transition em3) unless the duration timer value is equal to zero. in which case the SSF should move to the Idle Management state (transition em2).Page 63 ETS 300 374-1: September 1994 7. ActivityTest.1. the operations are passed by the SSME-Control to the relevant SSF FSM.
The CallGap operation may be received inside as well as outside a call context transaction. given that Call Gap/Service Filtering is active.
Figure 11: SSME FSM state diagram The Non-Call Associated Treatment state is entered from the IdleManagement state when one of the following non-call associated operations is received (transition em1): ActivateServiceFiltering. given that Service Filtering is active and the Service Filtering duration expires: the SSME FSM should move to the IdleManagement state (transition em2) and send a ServiceFilteringResponse operation to the SCF. The SSME FSM is independent of the individual SSF FSMs. During this state the following events can occur: given that Service Filtering is active. The ActivityTest operation applies to call associated transactions only. CallGap.
-
-
-
All other operations have no effect on the SSME FSMs. another CallGap/ActivateServiceFiltering operation could be received by the SSF. the SSME FSM should move to the IdleManagement state (transition em2). The ActivateServiceFiltering operation may be received outside a call context only.
.

await an event that would cause a transition out of the current state (such an event would be the completion of operation being executed). If a subsequent operation causes a transition out of the state then the following operations should be buffered until the current operation has been executed.g. it will execute them (e.Page 64 ETS 300 374-1: September 1994 7. or reception of an external event. As long as sequential execution of these operations would leave the FSM in the same state. RequestReportBCSMEvent).
NOTE:
Abandon and Disconnect transitions are not shown. and is processed as follows: process the operations in the order in which they are received. One or a sequence of components received in one or more TCAP messages may include a single operation or multiple operations. In all other cases. General rules applicable to more than one state are addressed here. each operation causes a state transition independent of whether or not a single operation or multiple operations are received in a message.5 SSF state transition diagram
Figure 12 shows the state diagram of the SSF part of the SSP during the processing of an IN call/attempt.
-
.1. the SSF examines subsequent operations in the sequence.
Figure 12: SSF FSM state diagram Each state is discussed in the following subclauses..

then transition to the Waiting for Instructions state (whether or not there is a pending CallInformationRequest). then the SSF FSM should process this event as follows: if the Disconnect DP is not armed for that specific leg and there is no CallInformationRequest pending. send a CallInformationReport and transition to the Idle state.2 (using TC-U-REJECT or the operation error UnexpectedComponentSequence). As the ConnectToResource operation is executed (and when. In any state (except Idle).774)). however different error treatment is possible in specific cases as described in Clause 8. ConnectToResource. the SSF FSM processes the error according to the rules given in subclause 10. the SSF FSM remains in the same state as when it received the erroneous operation. the SSF FSM processes the error (see below) and discards all remaining operations in the sequence. these operations are executed up to and including ConnectToResource while the SSF is in the Waiting for Instruction state. if the Abandon DP is armed as an EDP-N and there is a CallInformationRequest pending. The PlayAnnouncement operation is relayed to the SRF while the SSF is in Waiting for End of User Interaction state.. transition to the Idle state. if there is an error in a received operation. then the SSF FSM should instruct the CCF to clear the call and ensure that any CCF resources allocated to the call have been de-allocated.
-
In any state. and PlayAnnouncement in a component sequence inside a single TCAP message. before the Active PIC in the BCSM).
-
-
-
-
Other pending requests that are treated in the same way as the CallInformationRequest operation in the above list is the ApplyCharging operation when the "sendCalculationToSCPIndication" parameter is set to TRUE.
-
if there is an error in processing one of the operations in the sequence. if the Abandon DP is not armed and there is a CallInformationRequestpending. the error could be reported by the SSF to the SCF using the appropriate component (see ETS 300 287 [5] (ITU-T Recommendation Q. Upon receipt of this message.e. if the calling party abandons the call before it is answered (i. send an EventReportBCSM operation.e. if a call party disconnects from a stable call (i. violates the SACF rules defined by the SSF FSM) as described above. depending on the class of the operation. if an operation is not understood or is out of context (i. the maintenance functions are informed. if the Abandon DP is armed as an EDP-N and there is no CallInformationRequest pending. then transition to the Idle state. then continue processing as follows: if the Abandon DP is not armed and there is no CallInformationRequest pending.. send an EventReportBCSM and a CallInformationReport. send a CallInformationReport. In any state (except Idle). if the Disconnect DP is not armed and there is a CallInformationRequest pending. then transition to the Idle state. Generally.e.Page 65 ETS 300 374-1: September 1994 EXAMPLE: The SSF receives the operations FurnishChargingInformation. or after the FurnishChargingInformation operation has been completed). if the Abandon DP is armed as an EDP-R. then transition to the Idle state. the SSF FSM will transition to the Waiting for End of User Interaction state.
-
. send an EventReportBCSM . then transition to the Idle state. from the Active PIC in the BCSM).

whose purpose is to prevent excessive call suspension time and to guard the association between the SSF and the SCF. The SSF state diagram contains the following transitions (events): e1: e2: e3: e4: e5: e6: e7: e8: e9: e10: e11: e12: e13: TDP encountered Trigger fail Initiate call received Trigger detected User Interaction requested User Interaction ended Temporary connection created Temporary connection ended Idle return from Wait for Instruction EDP_R encountered Routing instruction received EDP_N last encountered Waiting for End of User Interaction state no change
.3 State c: "Waiting for Instructions") or AssistRequestInstructions operation (refer to subclause 7. The SSF has an application timer.1. This value is either one associated to the three different cases as listed above. TSSF.6) TSSF is not used. whatever occurred last.1. While waiting for the first response from the SCF.5. immediately after the CallInformationReport the corresponding EventReportBCSM has to be sent. send either an EventReportBCSM and then transition to the Waiting for Instructions state or if a CallInformationRequest is pending. On expiration of TSSF the SSF FSM transitions to the Idle state.4 and 7.5.1. Timer TSSF is set in the following cases: when the SSF sends an InitialDP (refer to subclause 7. if the Disconnect DP is armed as an EDP-N and there is no CallInformationRequest pending. In this case the SCF may reset the TSSF timer using the ResetTimer operation any number of times. if the Disconnect DP is armed as an EDP-N and there is a CallInformationRequest pending. Subsequent to the first response.3) under any other condition as the one listed in the previous case. aborts the interaction with the SCF and the CCF progresses the BCSM if possible. send an EventReportBCSM . send an EventReportBCSM and a CallInformationReport.2 State b: "Waiting for Instructions" in the assisting/hand-off case). the timer TSSF can be reset only once by a ResetTimer operation.1. When receiving or sending any operation which is different from the above. when the SSF enters the "Waiting for instructions" state (refer to subclause 7. In these cases the SCF may reset TSSF using the ResetTimer operation any number of times. the SSF should reset TSSF to the last used set value.Page 66 ETS 300 374-1: September 1994 if the Disconnect DP is armed as an EDP-R for that specific leg. then transition to the Idle state.
-
-
In the three above cases. the timer can be reset any number of times. In the "Monitoring" state (refer to subclause 7. TSSF may respectively have three different values as defined by the application.1. or received in a ResetTimer operation.1. when the SSF enters the "Waiting for End of User Interaction" state or the "Waiting for End of Temporary Connection" state (refer to subclauses 7. then transition to the Idle state.5.5).5.
-
-
Other pending requests that are treated in the same way as the CallInformationRequest operation in the above list is the ApplyCharging operation when the "sendCalculationToSCPIndication" parameter is set to TRUE.5.6.

and there are no EDPs armed (transition e12). a message related to a new transaction containing an InitiateCallAttempt operation is received from the SCF: in this case the SSF FSM moves to the state Waiting for Instructions (transition e3). when the last EDP-N is encountered in the Monitoring state. when the last charging event is encountered in the Monitoring state.Page 67 ETS 300 374-1: September 1994 e14: e15: e16: e17: e18: e19: Waiting for Instruction state no change Waiting for End of Temporary Connection state no change Monitoring state no change Abandon (from any state) (not shown in the SSF state diagram) Disconnect (from any state) (not shown in the SSF state diagram) Non-call associated treatment from any state (not shown in the SSF state diagram)
The SSF state diagram contains the following states: State a: Idle State b: Trigger Processing State c: Waiting for Instructions State d: Waiting for End of User Interaction State e: Waiting for End of Temporary Connection State f: Monitoring 7. when a ReleaseCall operation is processed in Waiting for Instructions (transition e9) or Monitoring (transition e12).1. when a Connect. During this state the following call-associated events can occur: indication from the CCF that an armed TDP is encountered related to a possible IN call/service attempt: in this case the SSF FSM moves to the state Trigger Processing (transition e1).1.
-
. the SSF sends a CallInformationReport operation to the SCF before returning to Idle. when the application timer TSSF expires in one of the states: Waiting for Instructions. if there is a CallInformationRequest pending (see subclause 7. or ProceedCallProcessing operation is processed in the Waiting for Instructions state.1 State a: "Idle"
The SSF FSM enters the Idle state under a variety of conditions. Waiting for End of User Interaction or Waiting for End of Temporary Connection (transition e9).5.
-
-
-
-
-
When transitioning to the Idle state. The SSF FSM enters the Idle state when one of the following occurs: when the call is abandoned or one or more call parties disconnect in any other state under the conditions identified in subclause 7.5. and no EDPs are armed and there are no outstanding report requests (transition e9). as described below.1.5). and there are no EDP-Rs armed and no monitoring is active for charging events (transition e12). The SSF FSM enters the Idle state when sending or receiving an ABORT TCAP primitive due to abnormal conditions in any state. The SSF FSM enters the Idle state when DP processing fails in the Trigger Processing state (transition e2).

collect and verify necessary parameters for sending a InitialDetectionPoint to the SCF: if successful and the DP is a TDP-R. if there is an existing control relationship for the call: the SSF returns call control to the CCF.g.1. § 4. State c: "Waiting for Instructions"
-
-
-
-
-
-
7. if DP processing fails. DP processing fails in the following cases: if CallGapping is in effect: the SSF FSM will instruct the CCF to terminate the call with the appropriate treatment. In the second case (transition e3). as determined from DP processing.774)). applies to open numbering plans): the SSF FSM instructs the CCF to terminate the call with a standard terminating treatment.5: check if call gapping or service filtering mechanisms are active.2 State b: "Trigger Processing"
Following a trigger detection related to an armed TDP in the BCSM. and transition to the Waiting for Instructions state (transition e4).1.5.Page 68 ETS 300 374-1: September 1994 Any other operation received from the SCF while the SSF is in Idle state should be treated as an error. the SSF/CCF should: perform the DP processing actions specified in ITU-T Recommendation Q. if the Call is abandoned: the SSF returns call control to the CCF and continues processing as described in subclause 7.1. if the destination SCF is not accessible: the SSF FSM will instruct the CCF to route the call if possible (e. or from the state Monitoring on detection of an EDP-R (transition e10). 7. if a trigger criteria match is not found: the SSF FSM returns call control to the CCF. In this state. the SSF moves to the Waiting for Instructions state immediately and then proceeds according to the contents of the InitiateCall operation and any other received operations. default routing to a terminating announcement).1214 [11].5. determine if DP criteria are met. as indicated above (transition e4). or directly from the Idle state on receipt at the SSF of a TC_Begin indication primitive containing an InitiateCall operation from the SCF (transition e3). send a generic InitialDetectionPoint to the SCF. if Service Filtering is in effect: the call is counted (if required) and the SSF FSM instructs the CCF to terminate the call with the appropriate treatment.
.2. handle service feature interactions.5.2. the SSF FSM is activated and moves from the Idle state to the Trigger Processing state (transition e1).g. if there is insufficient information to proceed (e. return to the Idle state (transition e2).3
This state is entered from either the Trigger Processing state. The event should be reported to the maintenance functions and the transaction should be aborted according to the procedure specified in TCAP (see ETS 300 287 [5] (ITU-T Recommendation Q. check for SCF accessibility.

causing a state transition to either Monitoring state (if any EDPs were armed or any reports were requested) (transition e11) or Idle state (transition e9): Connect.
ReleaseCall operation may be received from SCF and processed by the SSF. default routing to a terminating announcement).5. causing a state transition to Waiting for End of User Interaction state (transition e5): ConnectToResource.
-
-
-
The following operations may be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e14): RequestReportBCSMEvent.g. This should be processed in accordance with the general rules in subclause 7.Page 69 ETS 300 374-1: September 1994 In this state the SSF FSM is waiting for an instruction from the SCF. call handling is suspended and an application timer (TSSF) should be set on entering this state. ApplyCharging. RequestNotificationChargingEvent. causing a transition to Idle state (transition e9). SendChargingInformation. CallInformationRequest. InitiateCallAttempt operation. Cancel. causing a state transition to Waiting for End of Temporary Connection state (transition e7): EstablishTemporaryConnection. should be processed in Waiting for Instructions state (transition e3). Continue. an operation is received from the SCF: The SSF FSM acts according to the operation received as described below. During this state the following events can occur: the user dials additional digits (applies for open-ended numbering plans): the CCF should store the additional digits dialled by the user.
The following operations may be received from the SCF and processed by the SSF.
. CollectInformation.
The following operations may be received from the SCF and processed by the SSF. If there is a CallInformationRequest. FurnishChargingInformation.1. if received in Idle state. the SSF sends a CallInformationReport operation to the SCF before returning to Idle. the CCF routes the call if possible (e. ReleaseCall. the TSSF expiration is reported to the maintenance functions and the transaction is aborted.
The following operations may be received from the SCF and processed by the SSF. the application Timer TSSF expires: the SSF FSM moves to the Idle state. the user abandons or disconnects. ResetTimer.

In both cases this causes the release of the connection to the SRF and the transition to the Waiting for Instructions state. PromptAndCollectUserInformation and CancelAnnouncement) for relaying is received and is correct. FurnishChargingInformation.
.5.5. Call disconnect can also be received from the SRF.1.1. The call is routed to the assisting SSF/SRF and call handling is suspended while waiting for the end of the assisting procedure.5.5.4 State d: "Waiting for End of User Interaction"
The SSF enters this state from the Waiting for Instructions state (transition e5) on the reception of one of the following operations: ConnectToResource During this state the following events can occur: a valid SCF-SRF operation (i.
-
-
-
-
The following operations may be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e13): RequestNotificationChargingEvent.e.Page 70 ETS 300 374-1: September 1994 When processing the above operations..1. SendChargingInformation. SpecializedResourceReport and return result from PromptAndCollectUserInformation) for relaying is received and is correct. ResetTimer.1.. Any other operation received in this state should be processed in accordance with the general rules in subclause 7. the operation is transferred to the SCF. The timer TSSF is active in this state. the application timer TSSF expires: the SSF FSM moves to the Idle state. 7. an operation is received from the SCF: The SSF FSM acts according to the operation received as described below. the user abandons. a valid SRF-SCF operation (i. Any other operation received in this state should be processed in accordance with the general rules in subclause 7. default routing to a terminating announcement). ApplyCharging. the TSSF expiration is reported to the maintenance functions and the transaction is aborted.5 State e: "Waiting for End of Temporary Connection"
The SSF enters this state from the Waiting for Instructions state (transition e7) upon receiving an EstablishTemporaryConnection operation. 7. PlayAnnouncement.1. The SSF FSM remains in the Waiting for End of User Interaction state (transition e13). The SSF FSM remains in the Waiting for End of User Interaction state (transition e13). any necessary call handling information is provided to the Call Control Function (CCF).
The DisconnectForwardConnection operation may be received from the SCF and processed by the SSF in this state. the operation is transferred to the SRF for execution. The disconnection is not transferred to the other party (transition e6).5. the CCF routes the call if possible (e.g. This should be processed in accordance with the general rules in subclause 7.e.

5. The disconnection is not transferred to the Calling party.
-
-
-
.1.. the user abandons. an EDP-R should be reported to the SCF by sending an EventReportBCSM operation.6 State f: "Monitoring"
The SSF enters this state from the Waiting for Instructions state (transition e11) upon receiving a Connect.1. default routing to a terminating announcement). the expiration of TSSF does not have any impact on the SSF FSM. In both cases this causes the release of the connection to the SRF and the transition to the Waiting for Instructions state. disassociating the SSF FSM from the call.5. the SSF moves to the Waiting for Instructions state (transition e8). In this case. 7.
-
-
-
The following operations can be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e15): RequestNotificationChargingEvent. ResetTimer. CollectInformation. the receipt of an END or ABORT primitive from TCAP has no effect on the call.g. In this case.1.5. During this state the following events can occur: an EDP-N should be reported to the SCF by sending an EventReportBCSM operation.
The DisconnectForwardConnection operation may be received from the SCF and processed by the SSF in this state. the SSF FSM should move to the Waiting for Instructions state (transition e10). Call disconnect can also be received from the SRF. the CCF routes the call if possible (e. SendChargingInformation. the SSF FSM should remain in the Monitoring state (transition e16) if one or more EDPs are armed or there are report requests pending. Continue operation when one or more EDPs are armed or/and there is CallInformationRequest pending (see subclause 7. This should be processed in accordance with the general rules in subclause 7.5). ApplyCharging. The SSF FSM shall move to the Idle state (transition e12) if there are no remaining EDPs armed and there are no report requests pending.Page 71 ETS 300 374-1: September 1994 During this state the following events can occur: the application Timer TSSF expires: the SSF FSM moves to the Idle state. the call may continue or be completed with the information available.e. the SSF FSM transitions to the Idle state (transition e12).1. In this state the timer TSSF is not used. i. The SSF acts according to the operation received as described below. an operation is received from the SCF: The SSF FSM acts according to the operation received as described below. The disconnection is not transferred to the other party (transition e8). the TSSF expiration is reported to the maintenance functions and the transaction is aborted. Any other operation received in this state should be processed in accordance with the general rules in subclause 7. the receipt of an indication of disconnection of forward connection from the CCF. an operation is received from the SCF. FurnishChargingInformation.

RequestNotificationChargingEvent.1 through 7.6 Assisting/hand-off SSF FSM
The present subclause describes the SSF FSM related to the Assisting/hand-off SSF. The Assisting SSF is structured as defined in subclauses 7.
Figure 13: Assisting/hand-off SSF FSM state diagram The Assisting/hand-off SSF state diagram contains the following transitions (events): ea1: ea2: ea3: ea4: ea5: ea6: Assist/hand-off detected Assist/hand-off ended (fail or success) User Interaction requested User Interaction ended Waiting for Instruction state no change Waiting for End of User Interaction state no change
. Any other operation received in this state should be processed in accordance with the general rules in subclause 7. Within this subclause. If there is a CallInformationRequest pending.1.
The following operations can be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e16): RequestReportBCSMEvent.5. SendChargingInformation. causing a state transition to the Idle state (transition e12). The Hand-off FSM for CS1 applies only to the case where final treatment is to be applied. the term "Assisting SSF" refers to both Assisting and Hand-off SSFs unless an explicit indication to one or the other is provided. This should be processed in accordance with the general rules in subclause 7.5. 7.1. the SSF sends a CallInformationReport to the SCF. causing a state transition to the Idle state (transition e12).1.1.1.5 of this ETS.
The Cancel operation may be received from the SCF and processed by the SSF.Page 72 ETS 300 374-1: September 1994 the user abandons or disconnects. The ReleaseCall operation may be received from the SCF and processed by the SSF.

1 State a: "Idle"
The SSF FSM enters the Idle state when one of the following occurs: when sending or receiving an ABORT TCAP primitive due to abnormal conditions in any state.
-
-
The following operations may be received from the SCF and processed by the Assisting SSF with no resulting transition to a different state (transition ea5): ResetTimer.6. During this state the following events can occur: the application Timer TSSF expires: the Assisting SSF FSM moves to the Idle state (transition ea2) and the expiration is reported to the maintenance functions and the transaction is aborted.6. an operation is received from the SCF: The SSF FSM acts according to the operation received as described below.
.Page 73 ETS 300 374-1: September 1994 The Assisting/hand-off SSF state diagram contains the following states: State a: Idle State b: Waiting for Instructions State c: Waiting for End of User Interaction 7. Any operation received from the SCF while the Assisting SSF is in Idle state should be treated as an error.2 State b: "Waiting for Instructions"
This state is entered from the Idle state on receipt of a connect at an SSF from another SSF indicating that an assist is required.1.1. causing a state transition to Waiting for End of User Interaction state (transition ea3): ConnectToResource. SendChargingInformation. a bearer channel disconnect is received and the FSM moves to the Idle state (transition ea2). see ETS 300 287 [5] (ITU-T Recommendation Q. they are discarded by the Assisting SSF. given a temporary connection between an upstream SSF and the Assisting SSF. when a bearer channel disconnect is received from the upstream SSF. FurnishChargingInformation. ApplyCharging.
Once in the Idle state. (transition ea2). In this state the SSF sends an AssistRequestInstructions operation to the SCF and the Assisting SSF FSM is waiting for an instruction from the SCF.
The following operations can be received from the SCF and processed by the Assisting SSF.774). The Assisting SSF FSM transitions from the Idle state to the Waiting for Instructions state on receipt of an assist indication at the assisting SSF from another SSF (transition ea1). 7. The event should be reported to the maintenance functions and the transaction should be aborted according to the procedure specified in TCAP. based on an implementation dependent detection mechanism(transition ea1). if there are any outstanding responses to send to the SCF. call handling is suspended and an application timer (TSSF) should be set on entering this state.

g. This procedure is only valid if a ConnectToResource was previously processed to cause a transition into the Waiting for End of User Interaction state. a bearer channel disconnect is received from the initiating SSF.e. an operation is received from the SCF: The SSF FSM acts according to the operation received as described below. default routing to a terminating announcement). SpecializedResourceReport and return result from PromptAndCollectUserInformation) for relaying is received and is correct.5. the application Timer TSSF expires: the SSF FSM moves to the Idle state. causing a state transition to Idle state (transition ea2): ReleaseCall. the TSSF expiration is reported to the maintenance functions and the transaction is aborted. the operation is transferred to the SCF. PromptAndCollectUserInformation and CancelAnnouncement) for relaying is received and is correct.
During this state the following events can occur: a valid SCF-SRF operation (i. Any other operation received in this state should be processed in accordance with the general rules in subclause 7. The SSF FSM remains in the Waiting for End of User Interaction state (transition ea6).
-
-
-
-
-
The following operations can be received from the SCF and processed by the SSF with no resulting transition to a different state (transition ea6): ResetTimer.Page 74 ETS 300 374-1: September 1994 The following operations can be received from the SCF and processed by the Hand-off SSF.1. NOTE: 7. the operation is transferred to the SRF for execution. it may execute the ReleaseCall operation in the assisting SSF.6.
The above operation is allowed only in the Hand-off SSF. Any other operation received in this state should be processed in accordance with the general rules in subclause 7. when the SRF indicates to the Hand-off SSF the end of user interaction by initiating disconnection the Hand-off SSF FSM returns to the Waiting for Instructions state (transition ea4). the connection to the SRF is released and the transaction is aborted. In the case where an implementation is not capable of differentiating between a Hand-off or an assisting SSF case. State c: "Waiting for End of User Interaction"
The Assisting SSF enters this state from the Waiting for Instructions state (transition ea3) on the reception of one of the following operations: ConnectToResource.. causing a transition to the Waiting for Instructions state (transition ea4).
. a valid SRF-SCF operation (i. The SSF FSM remains in the Waiting for End of User Interaction state (transition ea6).. PlayAnnouncement. the CCF routes the call if possible (e.3 Multiple Hand-off procedures are not covered by this ETS..5.
The DisconnectForwardConnection operation may be received from the SCF and processed by the Assisting SSF in this state.1.e. The assisting SSF FSM moves to the Idle state.1.

the ASEs interface with supporting protocol layers to communicate with the SSF.
Figure 14: Functional model of SCF AE
. and interface to the SLPs and maintenance functions.7. In addition.2 Model and Interfaces
The functional model of the AE-SCF is shown in figure 14. The AE. The following subclauses define the TC-user ASE and SACF/MACF rules.1 SCF application entity procedures General
This subclause provides the definition of the SCF AE procedures related to the SCF-SSF/SRF/SDF interface.2. the statements and rules contained in the detailed Clauses 9 and 10 shall be followed. following the architecture defined in ITU-T Recommendations Q.
NOTE:
The SCF FSM includes several Finite State Machines. The procedures are based on the use of Signalling System No. includes TCAP and one or more ASEs called TCusers. AD or SN.771).Page 75 ETS 300 374-1: September 1994 7. 7. other capabilities may be supported in an implementation-dependent manner in the SCP. which interface with TCAP using the primitives specified in ETS 300 287 [5] (ITU-T Recommendation Q. and ETS 300 287 [5] (ITU-T Recommendation Q. The procedure may equally be used with other message-based signalling systems supporting the Application Layer structures defined. The scope of this ETS is limited to the shaded area in figure 14.1400 [13].700 [9] and Q.771). By no means is this text intended to dictate any limitations to Service Logic Programs (SLPs). In case interpretations for the AE procedures defined in the following differ from detailed procedures and the rules for using of TCAP service. other signalling systems can also be used.2.2 7. SRF and SDF.

771) (interface (1)) and N-primitives specified in ETS 300 009 [2] (ITU-T Recommendation Q. 7. The SCME is comprised of the SCME-Control and multiple instances of SCME FSMs. an instance of the SCSM is created. and the relevant SLP is invoked.
Figure 15: SCF FSM structure
. the SCF FSM handles the interaction with the SSF FSM (and the SRF FSM and SDF FSM) as required. an instance of an SCF Call State Model (SCSM) is created. and notifies the SLP of events as needed.Page 76 ETS 300 374-1: September 1994 The interfaces shown in figure 14 use the TC-user ASE primitives specified in ETS 300 287 [5] (ITU-T Recommendation Q. Figure 15 shows the SCF FSM structure. The SCME-Control interfaces different SCSMs and the FEAM. The management functions related to the execution of operations received from the SCF are executed by the SCF Management Entity (SCME). when initiation of a call is requested from SL.711) (interface (2)).3 Relationship between the SCF FSM and Service Logic Programs (SLPs)/maintenance functions
The primitive interface between the SCF FSM and the SLPs/maintenance functions is an internal interface and is not a subject for standardization in CS1. The operations and parameters of INAP are defined in Clause 6 of this ETS. The relationship between the SLP and the SCF FSM may be described as follows (for cases both a call initiated by an end user and a call initiated by IN SL): if a request for IN call processing is received from the SSF.
-
In either case.2.

For example. which explains the need for a single entity that performs the tasks of creation. The procedural model associates an SCSM with each query from the SSF. SDF.2). or Resource Monitoring status. events and procedures. and formatting. ActivateServiceFiltering operations providing different "filteringCriteria" cause the invocation of new SCME FSMs. and sending messages received from the SCME to the SSF. Consequently. passing (and queueing when necessary) the messages received from the SSF.Page 77 ETS 300 374-1: September 1994 The following text systematically describes the procedural aspects of the interface between the SCF and other functional entities.2. the SCME maintains the dialogues with the SSF. the technical details of how the SSF/CCF performs queue management is beyond the scope of IN.
-
-
The different contexts of the SCME FSMs may be distinguished based on the address information provided in the initiating operations. i. NOTE: Although the SCSM includes a state and procedures concerning queue management. SRF and SDF. For example.. this address information is given by "filteringCriteria". translates the SCSM outputs into corresponding messages to other FEs. the SCME provides the non-call associated treatment due to changes in Service Filtering. Automatic Call Gap) to the SSF to place flow control on queries. address the same SCME FSM handling this specific service filtering instance. The SCSM maintains dialogues with the SSF. however. this type of resource management only represents one way of managing network call queues. the SCME-Control separates the SCSM from the Service Filtering by creating instances of SCME FSMs for each context of related operations. Call Gapping. This entity is called the SCF Management Entity-Control (SCME-Control). this text describes only a subset of the SCF functional capabilities. along with its relevant sub-states. with the main goal of specifying the proper order of operations rather than the functional capabilities of the entities. are only required and applicable in the case where queue management is performed in the SCF. Multiple requests may be executed concurrently and asynchronously by the SCF. queueing (when necessary). Other such activities include non-call associated treatment due to changes in Service Filtering. It is the responsibility of the SCME-control to detect nodal overload and send the Overload Indication (e.e. and maintenance of the SCF FSM objects. In the case of service filtering. As such. all ActivateServiceFiltering operations using the same address. captures asynchronous (with call processing) activities related to management and supervisory functions in the SCF and creates an instance of a SCME FSM. In particular.
-
. SRF. and SDF.4. invocation. The functions in the FEAM include: establishing and maintaining the interfaces to the SSF. In addition to the above tasks.3) and the queueing state of the SCSM (State 2. Therefore. Finally. performs some asynchronous (with call processing) activities (one such activity is flow control). Another alternative is to let the SSF/CCF manage call queues. the SCME-Control: interprets the input messages from other FEs and translates them into corresponding SCSM events.g. supports persistent interactions between the SCF and other FEs. and SDF on behalf of SL. SRF. SRF. and SDF to the SCME. and SRF on behalf of all instances of the SCF FSMs. the RCO (see subclause 7. the FEAM relieves the SCME of low-level interface functions.

Waiting for SSF Service Filtering Response. caused by reception of the response to the RequestServiceFiltering operation previously issued to the SSF.
Figure 16: The service filtering FSM in the SCME The SCME handles the following operations: ActivateServiceFiltering.
-
When Service Filtering is active. this second "filter" replaces the first one. "Waiting for SSF Service Filtering Response".Page 78 ETS 300 374-1: September 1994 7. these operations are passed to the relevant SCSM.2.4 Partial SCF Management Entity (SCME) state transition diagram
The key part of the SCME state diagram is described in figure 16. another ServiceFiltering operation could be sent to the SSF that has the same filtering criteria. This event causes a transition to state M3. 7.
. the SCF is waiting for the service filtering response from the SSF. and by transmission of the ActivateServiceFiltering operation. The following events are considered in this state: (em7) End_of_Service_Filtering: This is an internal event. and the SCSM remains in state M4. This event does not cause a transition out of this state.
The issuing of the CallGap and ActivityTest operations does not cause state transitions in the SCME. CallGap.4. State M4: "Waiting for SSF Service Filtering Response"
7. and the number of an event is prefixed with either the letter "E" (for external events) or "e" (for internal ones) and included in parentheses in the beginning of the event name.4.2.1 State M3: "Service Filtering Idle"
The following event1) is considered in this state: (em5) Filtering_Request_to_SSF: This is an internal event. caused by the need of the SL to filter service requests to the SSF.2
In this state. (Em8) Filtering_Response_from_SSF: This is an external event. The procedures for the rest of the above operations are described below. The operations that are not listed above do not affect the state of the SCME. This event causes a transition to state M4.2. ServiceFilteringResponse. "Service Filtering Idle".
1)
All events are enumerated. ActivityTest. caused by the expiration of service filtering duration timer in the SCF.

or SDF (see ETS 300 287 [5] (ITU-T Recommendation Q. when the CallInformationReport is outstanding.g. all resources allocated to that call. shall be de-allocated. In any state (except "Idle"). however. In this case. different error treatment is possible in specific cases as described in Clause 8. the error can be reported to the SSF.5
Figure 17 shows the general state diagram of the SCSM as relevant to the procedures concerning the SCF FSM part of the SCP/AD/SN during the processing of an IN call. such transitions are not demonstrated in the figures. and maintains the queue of SCSMs that are waiting for this resource. Generally.Page 79 ETS 300 374-1: September 1994 7. the SCSM is queued for it. the SCSM may receive the CallInformationReport operation from the SSF.
. the SCSM transmits the CallInformationRequest operation to the SSF. the SLP and the maintenance functions are informed.3 The Resource Control Object (RCO)
The RCO is part of the SCF Management Entity that controls data relevant to resource information. including those required for relevant dialogues with the other functions.
The following three methods are defined for the RCO: 1) Get_Resource: this method is used to obtain the address of an idle line on behalf of an SCSM.. Busy or Idle).4. SRF.
2)
For the purposes of this ETS. for each supported resource. then it informs the SLP and returns to the Idle state. the SCSM remains in the same state. except "Idle". Depending on the class of the operation. Free_Resource: this method is used when a disconnect notification from the SSF is received. if there is an error in a received operation.2. and Cancel: this method is used when either the Queueing Timer has expired or the call has been abandoned. has internal sub-FSMs composed of the sub-states. The RCO consists of: 1) a data structure that (by definition) resides in the SDF and can be accessed only via the methods of the RCO. The SCF Call State Model (SCSM)
2)
3)
7. When the SLP requests call information. To simplify the diagram. General rules applicable to more than one state are as follows: In every state.774)). it: 1) 2) stores the status of the resource (e. If the resource is busy. It also holds that. Each state is discussed in one of the following subclauses. Other pending requests that are treated in the same way as the CallInformationRequest is the ApplyCharging when the "sendCalculationToSCPIndication" parameter is set to TRUE. in every state. if the SCSM is informed that the dialogue with the SSF is terminated. Each state. and the RCO Methods.2. The only requirement to the structure is that. and then CallInformationReport is outstanding. "SDF Request Idle" and "Waiting for SDF Response". The method either advances the queue (if it is not empty) or marks the resource free (otherwise). no implementation constraints are placed on the structure.

2. The general rules for one or a sequence of components sent in one or more TCAP messages.5.2. T SCF-SSF.2. which may include a single operation or multiple operations. the SCSM remains in the same state until it receives the CallInformationReport operation. On the expiration of TSCF-SSF. the SCF may reset TSSF using the ResetTimer operation any number of times. and
-
. are specified in subclause 7.1.5.2. and subclause 7. other than ResetTimer operation.2. State 2. State 2. Timer TSCF-SSF is set in the following cases: when the SCF receives an InitialDP or AssistRequestInstructions operation (see subclause 7.1: "Preparing SSF Instructions". using the ResetTimer operation. this timer is reset when the first request.2: "Queueing").5 and are not described here. and also reset TSCF-SSF.2. State 2.1. The SCSM has an application timer.2. when the SCF enters the Queuing sub-state (see subclause 7.2. whose purpose is to reset the timer TSSF.5. the SCSM informs SLP and the maintenance functions.1: "Preparing SSF Instructions"). on the expiration of timer TSCF-SSF. if CallInformationReport is outstanding and the SLP indicates that the processing has been completed. In this case. is sent to the SSF. and the SCSM transits to the Idle state.2.2. On second expiration of TSCF-SSF. In this case. which is used to prevent excessive call suspension time and to guard the association between the SSF and the SCF.1.Page 80 ETS 300 374-1: September 1994
Figure 17: SCSM FSM state diagram From any state (except "Idle"). the SCF may reset TSSF once.

5. TSCF-SSF is not used. CollectInformation. On expiration of TASSIST/HAND-OFF. unlike the states and events.
In all three cases. and non-call-processing-related operations. In these cases. The timer expiration causes a check of the dialogue and the related resources at the SSF/SCF via the operation ActivityTest (refer to the detailed procedure of that operation).3. The outputs are presented within smaller rectangles than the states are. When receiving or sending any other operation.Page 81 ETS 300 374-1: September 1994 when the SCF enters the "Waiting for Assist Request Instructions" state or the "User Interaction" state (see subclauses 7.4). each state is described in a separate subclause together with the events that cause a transition out of this state.3).
Call-processing-related operations are grouped into the following two sets: and InitiateCallAttempt. The value of TSCF-SSF are smaller than the respective value of TSSF. This timer is stopped when the SCSM receives the AssistRequestInstructions operation from the assisting/handedoff SSF. The SCSM also has an application timer. Connect. Two operations of the first set shall be separated by at least one EDP-R message received by the SCSM. but send them only one at a time. and the SCSM transits to the Idle state (in case of Hand-off) or to the Preparing SSF instructions state (in case of assist). the SCSM informs SL and the maintenance functions. The SCSM sets the timer TASSIST/HAND-OFF when the SCSM sends the EstablishTemporaryConnection or Connect operation with a correlation identifier (ID). the SCF should reset TSCF-SSF. In case of successful processing of that operation the timer is reset. which guards a dialogue and the related resources. When the SL needs to send operations in parallel.5. T ASSIST/HAND-OFF. the outputs are not enumerated.2.2. the SCF may reset TSSF using the ResetTimer operation any number of times. the SCF may not send two operations of the same set in a series of TCAP messages or in a component sequence to the SSF.
For the first set of call-processing-related operations.5. on the expiration of TSCFSSF. TSCF-SSF may respectively have three different values as defined by the application. T ActTest. EstablishTemporaryConnection. ConnectToResource. The call-control-related operations relevant to the SCF-SSF interface (except the SCME related operations) are categorized into: call-processing-related operations. The non-call-processing operations include the rest of the operations at the SCF-SSF interface (but not the SCME related operations). The same applies for any operation of the first set followed by ConnectToResource or EstablishTemporaryConnection. This timer is set at the beginning of a dialogue. In what follows.2. whose purpose is to prevent excessive assist/hand-off suspension time. ReleaseCall.2. they are sent in the component sequence. The SCSM has an additional application timer.2 and 7. DisconnectForwardConnection.
. In the "Waiting for Notification or Request" state (see subclause 7. Continue.

This event causes a transition to State 3. (e5) SR_Facilities_Needed: This is an (internal) event caused by the need of the SL for additional information from the call party. The SCSM issues the InitiateCallAttempt operation to the SSF. which are described in the following three subclauses (this subdivision is illustrated in figure 18).2. (e6) Processing_Failure: This (internal) event causes an appropriate exception processing and a transition back to State 1. (E2) Query_from_SSF: This is an external event. hence is the necessity to set up a connection between the call party and the SRF. AssistRequestInstructions (for the Service Hand-off case).2. Idle. Idle. In this case. It is assumed. the SCF has completed the processing of the instructions to the SSF. that it has to include releasing all the involved resources and sending an appropriate response message to the SSF. the exception processing is not defined. Routing to Resource.
-
Both events cause a transition to State 2. NOTE: Here and further in this ETS.1 State 1: "Idle"
The following events are considered in this state: (e1) SL_Invocation: This is an internal event caused by the need of the SL to start a call.
-
-
To further describe the procedures relevant to this state.2 State 2: "Preparing SSF Instructions"
In this state.5. This event causes a response to be sent to the SSF and a transition to State 1. the state is divided into three sub-states. The following events are considered in this state: (e4) Processing_Completed: This is an internal event. Preparing SSF Instructions.Page 82 ETS 300 374-1: September 1994 7. the SCF determines how to further process.
. 7.5. caused by a reception of one of the following operations: InitialDP. however.

Page 83 ETS 300 374-1: September 1994
NOTE 1: NOTE 2: NOTE 3:
Including CallInformationRequest and ApplyCharging with report request.2. etc.1 State 2. In addition. whether queueing is supported. Including CallInformationReport and ApplyChargingReport. and EventNotificationCharging. is where the initial decision is made on whether the SDF information or a Specialized Resource is needed. ApplyChargingReport.1: "Preparing SSF Instructions"
State 2.2.
. the EDP-R-related processing is also performed in this state. the SCSM starts or resets the timer TSCF-SSF. Including CallInformationReport.
Figure 18: Partial expansion of the State 2 FSM 7. Preparing SSF Instructions.5.1. On entering this state.

RequestReportBCSMEvent. This event maps into the SCSM event (e5).4) Call_Processing_Instruction_Ready (Monitoring required): This is an internal event caused by the SL when a call-processing-related operation is ready and the monitoring of the call is required (e. SendChargingInformation. It causes one of the following operations to be issued to the SSF: CollectInformation.1. Continue. It causes one of the following operations to be issued to the SSF: Connect. Continue. RequestNotificationChargingEvent.. RequestNotificationChargingEvent. one or more of the following operations may be issued to the SSF prior to the operations listed above: FurnishChargingInformation. an EDP is set.
-
In addition.g. and SendChargingInformation. FurnishChargingInformation. ReleaseCall. caused by the SL when there is a need to use the SRF. and RequestReportBCSMEvent (to disarm all armed EDPs). CallInformationRequest. FurnishChargingInformation.
This event causes a transition back to State 2. Preparing SSF Instructions.
In addition. one or more of the following operations may be issued to the SSF prior to one of the operations listed above: ApplyCharging. It causes one or more of the following operations to be issued to the SSF: ApplyCharging. (e2. RequestReportBCSMEvent.1) Non-Call_Processing_Instructions: This is an internal event caused by the SL when there is a need to send such an operation to the SSF.3) Call_Processing_Instruction_Ready (Monitoring not required): This is an internal event caused by the SL when the final call-processing-related operation is ready and there is no armed EDP and no outstanding CallInformationReport or ApplyChargingReport operations.
. (e2.2) SR_Facilities_Needed: This is an internal event.Page 84 ETS 300 374-1: September 1994 The following events are considered in this state: (e2. or there is a need to issue such a request).
This event maps into the SCSM event (e4). or there is an outstanding CallInformationReport or ApplyChargingReport. CallInformationRequest. and Cancel (for all report requests). Cancel (for all report requests). ResetTimer. ReleaseCall. (e2. SendChargingInformation. Connect.

The following operations can be sent in this state: ApplyCharging. FurnishChargingInformation. Queueing FSM.2. a SCF functionality may be used for scanning the status of resources. the SCF may put the call on queue and resume it later when the resource is idle.4. This event causes a transition into State 2. State 2.11) Abort_from_SSF: This is an external event caused by the reception of the Abort message from the SSF (on call abandonment). Both the Request and Report occur in a single different call context. the state-by-state description of the FSM is followed by the description of the supporting mechanisms of the SCME.2. This event causes a transition to State 2.10) Queueing_Processing_Finished: This is an internal event caused by the SLP when it is ready to prepare the call-related operation to the SSF. (E2.
The following events are considered in this state: (e2. RequestReportBCSMEvent. ResetTimer. (e2. (e2.3.5.
. and it maps into the SCSM event (e6) Processing_Failure. and SendChargingInformation. This FSM does not explicitly describe all possible combinations of resource monitoring functions used for queueing.
In the rest of this subclause.
Such a resource may be an individual line or trunk or a customer-defined group of lines or trunks. In the latter case. One possible reason causing the resource to be unavailable is the "busy" condition.Page 85 ETS 300 374-1: September 1994 This event causes a transition into State 2. RequestNotificationChargingEvent.3. The following possibilities may be used in implementations: monitoring based on issuing by the SCSM of the RequestEventReportBCSM operation and subsequent reception of the EventReportBCSM operation to report the availability of the resource.2. If the resource is busy. Preparing SSF Instructions. NOTE: The manner in which the status of the resources is maintained is described in subclause 7.2.5) Ready_for_Queueing_Processing: This is an internal event caused by the SL when queueing of the call is required. the word "busy" means that all lines or trunks in the group are occupied. it may find that the resource to which the call shall be routed is unavailable. Waiting for Notification or Request. CallInformationRequest.1.2
When the SCF is processing the Query from the SSF/CCF. In this case. and the word "idle" means that at least one line or trunk in the group is idle.2 "Queueing FSM"
-
7.6) Processing_Failure: This is an internal event. and it causes a transition that maps into the SCSM event (e4).
-
This state further expands into an FSM. which is depicted in figure 19.

3). the SCSM prepares the instructions for the SSF to complete the call. Preparing SSF Instructions (transition (e2.2.
.1) Instruction_Ready: This is an internal event that takes place only when the required resource is available. (e2.1.2. It causes one or more of the following operations to be issued to the SSF: ApplyCharging.4.2.2) Non-Call_Processing_Instructions: This is an internal event caused by the SL when there is a need to send such an operation to the SSF.2. The following events are considered in this state: (e2. ResetTimer. RequestNotificationChargingEvent.5.1: Preparing SSF Instructions
In this state. FurnishChargingInformation. Preparing SSF Instructions.1.2.10)).
-
This event causes a transition back to State 2.Page 86 ETS 300 374-1: September 1994
Figure 19: Partial expansion of the State 2 FSM as related to queueing 7.2.2. CallInformationRequest.1 State 2. RequestReportBCSMEvent.2. This event causes a transition to the State 2. In this case. and SendChargingInformation. the SCSM has obtained the address of the free resource via the Get_Resource method of the RCO (see subclause 7.

2. and the TSCF-SSF is reset.2: "Queueing"
7. and its value may be customer-specific.11). and it causes a transition that maps into the State 2 event (E2. State 2. which results in sending the ResetTimer operation to the SSF/CCF and a transition back to the same state. the ResetTimer operation should be sent to set the TSCF-SSF with an appropriate value.Page 87 ETS 300 374-1: September 1994 (e2. The following events are considered in this state: (E2. the Queueing Timer is started. not different from that of the SCSM States 3 and 4. the SCSM waits for a notification or a request from the SSF.3: "Waiting for Notification or Request"
-
-
7. Queueing. (e2. The respective roles of these timers are as follows: the Queueing Timer limits the time that a call can spend in the queue.10).
This event causes a transition to State 2. (E2. if announcements are completed before the call is dequeued and the SSF FSM has transitioned to state Waiting for Instructions. Hence. State 2. This event causes the ResetTimer operation.2
In this state. which maps into the State 2 event (e2.2. On entering this state the SCSM stops the timer TSCF-SSF.
.2.4) Refresh_Timer_Expired: This is an internal event. The support of playing various announcements is also provided when the SCSM is in this state.2. the SCSM is awaiting an indication from the RCO to proceed with routing a call to an idle trunk/line.5.5) Idle_Line/Trunk: This is an internal event. and a transition to State 2.2.2.5. however. However. The following events are considered in this state: (e2.7) Abort_from_SSF: This is an external event caused by the reception of the Abort message from the SSF (on call abandonment).2.2. the relevant further expansion of the state is not provided. with a suitable queueing timervalue. Once the SCSM enters this state. the value of this timer is set in agreement with that of the relevant timer TSSF within the SSF/CCF. In this ETS.
-
The FurnishChargingInformation operation may also be sent to the SSF at this time to indicate the initiation of queuing for call logging purposes. caused by a reception of the following operation: EventReportBCSM (for EDP_R). it is.3) Busy_Line/Trunk: This is an internal event caused by the RCO when no terminating line/trunk is available.10)) (following procedures depends on decision of the SL that may play (or not play) the terminating announcement).2.2. the TSCF-SSF signals when the ResetTimer operation shall be sent to the SSF/CCF lest the latter abandons the call.6) Queueing_Timer_Expired: This is an internal event. The SCME takes care of updating the queueing data via the Cancel method of the RCO. which results in processing the Cancel method of the RCO and causes a transition out of this state to the State 2.2.1 Preparing SSF Instructions (Transition (e2. to be sent to the SSF. (e2.2.1 Preparing SSF Instructions.3
In this state.7) EDP-R: This is an external event.2.

This event causes a transition to back to State 2.
In this case. EventReportBCSM (for EDP_N). the SCSM terminates the interaction with the initiating SSF. 7. Intelligent Peripheral).3 State 3: "Routing to Resource"
The resource is any SRF facility (e. This event maps into the SCSM event (e4). which are described in the following two subclauses (this subdivision is illustrated in figure 20). Idle.
In this case. This event causes a transition to State 2. User Interaction. there is no outstanding armed EDP and no outstanding CallInformationReport or ApplyChargingReport operation.Page 88 ETS 300 374-1: September 1994 (E2.9) Last_EDP-N: This is an external event. Preparing SSF Instructions. caused by a reception of one of the following operations: ApplyChargingReport. Waiting for Notification or Request. CallInformationReport. caused by a reception of one of the following operations: ApplyChargingReport. CallInformationReport. EventNotificationCharging. In this state. there is still an outstanding armed EDP or an outstanding CallInformationReport or ApplyChargingReport operation.8) Not_Last_EDP-N: This is an external event.5.2. the following events cause transitions out of this state: (e7) Resource_Attached: The SRF is available.
-
-
-
To further describe the procedures relevant to this state. interactions with the SSF are necessary. The SCF shall maintain sufficient information in order to correlate the subsequent AssistRequestInstructions operation (from the assisting SSF or SRF) to the existing Service Logic Program Instance (SLPI). (e8) Hand-off_Needed: When the Hand-off procedure is initiated..3. EventReportBCSM (for EDP_N).g. This event causes a transition to the State 1. the SCME creates the new SCSM. When the AssistRequestInstructions operation from the Handed-off SSF is received by the SCME. This concludes the description of State 2 Preparing SSF Instructions.
. the state is divided into two sub-states. and (e10) Timer_Expired: This event takes place when T ASSIST/HAND-OFF expires. (E9) Failure_from_SSF: The inability of the SSF to connect to requested resources causes a transition to State 2. (E2. Accordingly. Preparing SSF Instructions. This event causes a transition to State 4.

2 Waiting for Assist Request Instructions.1) Instruction_Ready: This is an internal event that takes place only when the Initiating SSF relay case. In this case.3. the SCSM sends the EstablishTemporaryConnection operation to the Initiating SSF with the Assisting SSF address or SRF address.1 State 3. the SCSM determines the User Interaction mode to connect the call to SRF.2. This transition maps into the event (e7). (e3.1: "Determine Mode"
In this state. the SCSM sends the ConnectToResource operation accompanied by PlayAnnouncement or PromptAndCollectUserInformation operation to the Initiating SSF. and
-
. In this case. and transits out to the State 4 User Interaction.2) Assist_Needed: This event is an internal event that takes place when the Assisting SSF is needed or Direct SCF-SRF relation is needed. and transits to the State 3.Page 89 ETS 300 374-1: September 1994
Figure 20: State 3 FSM 7. The following events are considered in this state: (e3.5.

4) Assist_Request_Instructions_from_SSF (Assisting SSF relay case): This is an external event caused by the receipt of AssistRequestInstructions from the Assisting SSF.5. In this case. and resets the timer TSCF-SSF.4
In this state. it is expanded into a separate FSM depicted in figure 21. the SCSM transmits the ConnectToResource operation accompanied by PlayAnnouncement or PromptAndCollectUserInformation operation to the Assisting SSF.
.7) Assist_Timer_Expired: This is an internal event that takes place on the expiration of TASSIST/HAND-OFF. This event maps into the event (e10). it can send a user interaction operation to the SRF containing an indication that allows the SRF initiated disconnect. (e3. This event causes a transition that maps into the SCSM event (E9). When an interaction is finished the SCF can instruct the SSF to disconnect the bearer between SSF and SRF. This transition maps into the event (e7). the SCSM sends the Connect operation with the Handed-off SSF address to the Initiating SSF.3) Hand-off_Needed: This is an internal event that takes place only when the Hand-off case. On entering this state the SCSM resets the timer TSCF-SSF. the SCF requests the SRF to provide user interaction (e.5) Assist_Request_Instructions_from_SRF (Direct SCF-SRF case): This is an external event caused by the receipt of AssistRequestInstructions from the SRF. the SCSM transmits the PlayAnnouncement or PromptAndCollectUserInformation operation to the SRF. (e3. the SCSM transmits the ResetTimer operation to the Initiating SSF. Alternatively.g. that is needed to instruct the SSF to complete the call. the SCF has obtained all the information from the SRF. and transits out to the State 4. In this case. and transits back to the same state. and transits out to the State 4. User Interaction.2. This transition maps into the event (e7). On entering this state the SCSM starts the Timer TASSIST/HAND-OFF. The following events cause transitions out of this state: (e11) Continue_SCF_Processing: In this case. the SCSM informs the SCME and SLP.Page 90 ETS 300 374-1: September 1994 (e3. and transits to the State 2 Preparing SSF Instructions.3.8) Initial_SSF_Failure: This is an external event caused by the reception of SSF failure. collect additional information and/or play announcements). In this case.6) Refresh_Timer_Expired: This is an internal event that takes place on the expiration of TSCFSSF.. This transition maps into the event (e8).2. The SCF shall maintain sufficient information in order to correlate the subsequent AssistRequestInstructions operation (from the assisting SSF or SRF) to the existing SLPI. State 4: "User Interaction"
-
-
-
-
7. State 3. In this case. This event causes a transition to State 2. (E3.2: "Waiting for Assist Request Instructions"
7. The following events are considered in this state: (E3.
To consider the processing of this state in more detail. Preparing SSF Instructions. the SCSM waits for the AssistRequestInstructions operation from the Assisting SSF (SSF relay case) or from the SRF (Direct SCF-SRF case). In this case. and transits to the State 1 Idle. and (E3.2
In this state.5. User Interaction.

1 State 4. The following events are considered in this state: (e4. (E4. as requested by the SCF.5.1) More_Information_Needed results in issuing yet another operation to the SRF.Page 91 ETS 300 374-1: September 1994
Figure 21: State 4 FSM 7.2) Response_from_SRF: This is an external event caused by the reception of SpecializedResourceReport or return result from PromptAndCollectUserInformation operation.2. in response to the previous PlayAnnouncement or return result from PromptAndCollectUserInformation operation with permission of SRF-initiated disconnect.2') Final_Response_from_SRF: This is an external event caused by the reception of SpecializedResourceReport operation. This event maps into the event (e11).
-
-
. the SCSM transits back to the same state.1 "Waiting for Response from the SRF"
In this state. the SCF waits for the response to the previously sent operation and evaluates this response. (E4.4. Preparing SSF Instructions. on the receipt of this event. the SCSM transits to the State 2.1. In the Initiating SSF relay case and the Direct SCF-SRF case. it causes a transition back to State 4. On the receipt of this operation.

In the case of Assisting SSF.1 SRF application entity procedures General
This subclause provides the definition of the SRF AE procedures related to the SRF-SCF interface.7.6) Refresh_Timer_Expired: This is an internal event that takes place on the expiration of TSCFSSF.
.
-
-
-
-
-
The bearer connection between the SSF and the SRF is disconnected when the SCSM exits from this state. while no SpecializedResourceReport operation is requested to be returned to the SCF in case the announcement is completed. (e4. the SRF-initiated disconnect cannot be used. The following subclauses define the TC-user ASE and SACF/MACF rules. In this case. This event maps into the event (e11). (e4. The procedure may equally be used with other message based signalling systems supporting the Application Layer structures defined. In the case of Assisting SSF. In this case. and transits back to the same state. Preparing SSF Instructions. the SCSM transits back to the same state. the SCSM transits back to the same state. the SCSM transmits the ResetTimer operation to the Initiating/Assisting SSF. which interface with TCAP using the primitives specified in ETS 300 287 [5] (ITU-T Recommendation Q. (E4. This event maps into the event (e11). (e4.3') Continue_SCF_Processing: This is an internal event that takes place when the SCSM finishes the User Interaction and requests the disconnection of bearer connection between the Initiating SSF and SRF by means of SRF-initiated disconnect. In case interpretations for the AE procedures defined in the following differ from detailed procedures and the rules for using of TCAP service.3) Continue_SCF_Processing: This is an internal event that takes place when the SCSM finishes the User Interaction and requests the disconnection of bearer connection between the Initiating SSF and SRF by means of SCF initiated disconnect. and (e4. the SCSM sends the Cancel operation to the Assisting SSF (SSF relay case) or the SRF (Direct SCF-SRF case). while an SpecializedResourceReport operation is requested to be returned to the SCF in case an announcement is completed.3'') Continue_SCF_Processing: This is an internal event that takes place when the SCSM finishes the User Interaction and requests the disconnection of bearer connection between the Initiating SSF and SRF by means of SRF initiated disconnect. the statements and rules contained in the detailed Clauses 9 and 10 shall be followed. Preparing SSF Instructions.Page 92 ETS 300 374-1: September 1994 (e4. Other capabilities may be supported in an implementation-dependent manner in the IP.771). and transits back to the same state. the SRF-initiated disconnect cannot be used. The AE.3 7.5) Failure_from_SRF: This is an external event caused by the reception of return error for PlayAnnouncement or return error for PromptAndCollectUserInformation operation.3. In this case.700 [9] and Q. other signalling systems may also be used. 7. The procedures are based on the use of Signalling System No. and ETS 300 287 [5] (ITU-T Recommendation Q.7) Cancellation_Required: This is an internal event that takes place when the SCSM cancels the previous PlayAnnouncement or PromptAndCollectUserInformation operation. In this case. the SCSM sends the PlayAnnouncement (containing a request for returning a SpecializedResourceReport operation as an indication of completion of the operation) or PromptAndCollectUserInformation operation with permission of SRF-initiated disconnect to the SRF. the SCSM sends the PlayAnnouncement operation (not containing a request for returning a SpecializedResourceReport operation as an indication of completion of the operation) with permission of SRF-initiated disconnect to the SRF. includes TCAP and one or more ASEs called TCusers.771).1400 [13]. following the architecture defined in ITU-T Recommendations Q. In this case. the SCSM sends the DisconnectForwardConnection operation to the Initiating SSF and transits to the State 2. the SCSM transits to the state 2. In this case. In this case. In this case. SSP or SN.

the ASEs interface to TCAP (to communicate with the SCF) as well as interface to the maintenance functions.711) (interface (2)).3.
Figure 22: Functional model of SRF AE The interfaces shown in figure 22 use the TC-user ASE primitives specified in ETS 300 287 [5] (ITU-T Recommendation Q.2 Model and interfaces
The functional model of the AE-SRF is shown in figure 22.
. 7. The management functions related to the execution of operation received from the SCF are executed by the SRF Management Entity (SRME). The scope of this ETS is limited to the shaded area in figure 22. The SRME interface the different SRF Call State Models (SRSMs) and the FEAM. Figure 23 shows the SRF FSM structure. The operations and parameters of INAP are defined in Clause 6 of this ETS.3 Relationship between the SRF FSM and maintenance functions/bearer connection handling
The primitive interface between the SRF FSM and the maintenance functions is an internal interface and is not subject for Standardization in CS1.3.771) (interface (1)) and N-primitives specified in ETS 300 009 [2] (ITU-T Recommendation Q.Page 93 ETS 300 374-1: September 1994 7. The SRF FSM handles the interaction with the SCF FSM and the SSF FSM.
NOTE:
The SRF FSM includes several Finite State Machines. an instance of an SRF FSM is created. The relationship between the Bearer Connection Handling and the SRF FSM may be described as follows for the case of a call initiated by the SSF: When a call attempt is initiated by the SSF.

Thus. passing (and queueing when necessary) the messages received from the SSF and SCF to the SRME. invocation. the SRME: 1) interprets the input messages from other FEs and translates them into corresponding SRSM events. the FEAM relieves the SRME of low-level interface functions. The FEAM functions include: 1) 2) establishing and maintaining the interfaces to the SSF and SCF.Page 94 ETS 300 374-1: September 1994
Figure 23: SRF FSM structure The model associates a FSM with each initial interaction request from the SCF. and formatting. and maintenance of the SRSM objects.
2) 3)
Finally.
3)
. multiple initial requests may be executed concurrently and asynchronously by the SRF. queueing (when necessary). In addition to the above tasks. and handles the activity test functionality for the SCF-SRF relationship. which explains the need for a single entity that performs the tasks of creation. In particular. translates the SRSM outputs into corresponding messages to other FEs. and sending messages received from the SRME to the SSF and SCF. the SRME maintains the dialogues with the SCF and SSF on behalf of all instances of the SRSM.

The SRF may reset TSRF on transmission of the SpecializedResourceReport operation or the return result for the PromptAndCollectUserInformation operation when there is no queued User Interaction operation. if the dialogue with the SCF (direct SCF-SRF case) is terminated. then the SRSM clears the call and ensures that all SRF resources allocated to the call have been de-allocated. the outputs are not enumerated. When a Cancel (for PlayAnnouncement or PromptAndCollectUserInformation) operation is encountered in the sequence in state User Interaction. the SRSM queues the operations and awaits an event (such an event would be the completion of the operation being executed.2 (using TC-U-REJECT or the operation error UnexpectedComponentSequence). Finally.e.
-
-
In any state. The resources allocated to the call will be de-allocated when all announcements are completed or when the SSF disconnects the bearer connection (i. the SRSM transits to the Idle state ensuring that all SRF resources allocated to the call have been de-allocated. Generally. This timer is stopped when a request is received from the SCF. In what follows.Page 95 ETS 300 374-1: September 1994 7. it violates the SACF rules defined by the SRSM) as described above. One component or a sequence of components received in one or more TCAP messages may include a single operation or multiple operations. General rules applicable to more than one state are addressed here. if the SSF disconnects the bearer connection to the SRF before the SRF completes the user interaction. it executes it immediately. the SRSM remains in the same state in which it received the erroneous operations. unlike the states and events. the outputs are presented within smaller rectangles than the states are.3. the error could be reported by the SRF to the SCF using the appropriate component (see ETS 300 287 [5] (ITU-T Recommendation Q. Then it transits to the Idle state. This timer is set when the SRF sends Setup Response bearer message to the SSF (SSF relay case) or the AssistRequestInstructions operation (Direct SCF-SRF case). On the expiration of TSRF. T SRF. Each state is discussed in the following subclauses. In all other cases. the SRF FSM processes the error (see below) and discards all remaining operations in the sequence. if an operation is not understood or is out of context (i.774)). if there is an error in processing one of the operations in the sequence. the SRSM examines subsequent operations in the sequence. or reception of an external event). whose purpose is to prevent excessive call suspension time. and it is processed as follows: the SRSM processes the operations in the order in which they are received. each state is described in a separate subclause together with the events that cause a transition out of this state. The SRF shall remain connected to the SSF as long as it has PA operations active or buffered.4 The SRF Call State Model (SRSM)
The SRSM is presented in figure 24. call party release). the SRF FSM processes the error according to the rules given in subclause 10. if there is an error in a received operation. In any state.e. depending on the class of the operation. the maintenance functions are informed. then the SRSM returns to Idle state after ensuring that all resources allocated to the dialogue have been de-allocated.
. In any state (except Idle). however different error treatment is possible in specific cases as described in Clause 8. The SRSM has an application timer.

The SRSM goes to state "Connected". e11 and e12.3. an instance of user interaction. This state is entered as a result of events E3. or at the completion of. (e4) SRF_sanity_timeout: this event occurs when the SRSM has been in Connected state for a network-operator-defined period of time (timer TSRF) without having a PlayAnnouncement/
-
-
. (E3) Connection_Released_from_SSF: this event takes place when the SRSM receives a Release message from the SSF in Connected state.Page 96 ETS 300 374-1: September 1994
Figure 24: SRSM FSM 7. The details of the bearer signalling state machine related to establishing the connection are not of interest to the FSM. e4.1 State 1: "Idle"
The Idle state represents the condition prior to. The SRSM goes to state "Idle". E10. (E1) Connect_request_from_SSF: this event corresponds to a bearer signalling connection request message from the SSF.4. It is exited as a result of event E1.

3. (E10) Connection_Released_from_SSF: this event takes place when the SRSM receives a Release message from the SSF in User Interaction state. e11 and e12. (E2) PA/P&C_from_SCF: this event takes place when the first PlayAnnouncement or PromptAndCollectUserInformation operation(s) from the SCF is received.3. The SRSM goes to state "Idle". The details of the bearer signalling state machine related to establishing the connection are not of interest in the SRF FSM. e8 and e9 do not cause a state change. The SRSM goes to state "User Interaction" on the first (E2).Page 97 ETS 300 374-1: September 1994 PromptAndCollectuserinformation (PA/P&C) operation to execute.g. Event E5 also represents additional PA/P&C operations which are buffered as discussed in the procedures. The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system after sending last SpecializedResourceReport operation to the SCF (e7). The SRSM goes to state "Idle". The SRSM goes to state "Idle". The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. State 3: "User Interaction"
-
-
-
-
7. The SRSM goes to state "Idle". This state is entered as a result of event E2. (e11) Disconnect_to_SSF: this event occurs when the SCF has enabled SRF initiated disconnect by the last PA/P&C from SCF (E2) or (E5) with the parameter. (e5) Assist_Request_Instructions_Needed: this event occurs when the AssistRequestInstructions operation is sent from the SRSM to the SCF in the absence of a PA/P&C event (E2) initiated by the presence of a PA/P&C operation concatenated with the setup request from SSF (E1) (Direct SCFSRF case). e7. The SRSM goes to state "Idle". and (e12) SRF_Sanity_Timeout: this event occurs when the SRSM has been in User Interaction state for a network-operator-defined period of time (timer TSRF) without having a PA/P&C operation to execute.
.4. E6. (E1) Connect_request_from_SSF: this event corresponds to a bearer signalling connection request message from the SSF in the Idle state. The SRSM goes to state "User Interaction". It is exited as a result of events E10. The SRF initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. The SRSM goes to state "Connected". (E3) Connection_Released_from_SSF: this event takes place when the SRF receives a release message from the SSF.2
This state represents the condition of the SRSM when a bearer channel has been established between a user and the SRF but the initial PA/P&C has not yet been received (e. State 2: "Connected"
-
-
7. The SRSM remains in state "User Interaction" for subsequent (E5)s. The SRF initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. (e4) SRF_sanity_Timeout: this event occurs when the SRSM has been connected for a network operator defined period of time (timer T SRF) without having a PA/P&C operation to execute. No state change occurs as a result of this event. when Establish Temporary Connection procedures are used). (E2) and (E5) PA/P&C_from_SCF: this event takes place when an initial or subsequent PlayAnnouncement or PromptAndCollectUserInformation operation(s) from the SCF is received.4. Events E5. The SRSM goes to state "Idle". The method used to provide this bearer channel is not of interest in the FSM.3
The User Interaction state indicates that communication is occurring between the user and the SRF via the bearer channel established at the Connected state.

interaction with the end user. failure of a user-SRF bearer connection will cause the SRSM to transit to Idle from any state.1. The SRSM goes to state "Idle". The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. and disconnect stages. The SRF control procedures are based on various physical allocation patterns of SRF. The SRSM remains in state "User Interaction". The various control procedures are described in this subclause in accordance with the example physical scenarios of protocol architecture in subclause 4. These transitions are not shown in figure 24 for the purpose of visual clarity. The SRSM remains in state "User Interaction". (e11) Disconnect_to_SSF: this event occurs when the SCF has enabled SRF initiated disconnect with the last PA/P&C from SCF (E2) or (E5). Arrow diagrams are used for the description of the connect. (E10) Connection_Released_from_SSF: this event takes place when the SRSM receives a release message from the SSF. (e8) PA/P&C_Cancelled_to_SCF: this event takes place when the PA/P&C error caused by the Cancel (for PlayAnnouncement or PromptAndCollectUserInformation) operation is sent to the SCF. bearer connection control signalling messages are used for explanatory purposes. The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system after sending last SpecializedResourceReport operation or return result on PromptAndCollectUserInformation operation to the SCF. (e9) Cancel_Error_to_SCF: this event takes place when the Cancel error (for PlayAnnouncement or PromptAndCollectUserInformation) is sent to the SCF. 7. The SRSM remains in state "User Interaction". (e12) SRF_sanity_timeout: this event occurs when the SRSM has been connected for a network operator defined period of time (timer T SRF) without having a PA/P&C operation to execute.
-
-
-
-
-
-
In addition to these explicitly marked transitions. The SRSM goes to state "Idle".3.
. The terms used for bearer connection control signalling messages only represent the functional meaning. This event represents the successful cancellation of an active or buffered PA/P&C operation. The SRSM goes to state "Idle". This event represents the unsuccessful cancellation of a PA/P&C operation. and are not subject for standardization. The indicated interaction is terminated if it is presently running. The SRSM remains in state "User Interaction". otherwise it is deleted from the buffer. (e7) SRF_Report_to_SCF: this event takes place when a SpecializedResourceReport operation or a return result for PromptAndCollectUserInformation operation is sent to the SCF.Page 98 ETS 300 374-1: September 1994 (E6) Cancel_from_SCF (for PA/P&C): this event takes place when the corresponding PlayAnnouncement or PromptAndCollectUserInformation operation is received from the SCF. The Service Assist and Hand-off procedures based on the physical scenarios are also described in this subclause as examples. NOTE: Through this subclause.5 Example SRF control procedures
This subclause provides a detailed description of the SRF procedures.

or directly attached to another SSP. the IP is integrated into another SSP. The establishment of the SCF-SRF relationship in this case is implicit. but the details of how this is achieved are left to the implementor.7 TCAP based. See also a note on the possibility of concatenating the first user interaction operation with the ConnectToResource operation discussed in the subclause on user interaction below. For the integrated IP/SSP. the IP is directly attached to another node than the SSP that is interacting with the SCP but the operations of the SCP to the IP are sent directly to the IP without SSP relaying involved (called the "Assist" method. the internal activities of the node can still be modelled in this way. and bearer control signalling may be any system. Case a) is illustrated in figure 26. and on completion of the user interaction. but with a variation on the physical connectivity of the entities involved).
S CP
SSP
Se tup Re que st Se tup Re sponse
IP
C onne t to Re c sourc e
IP Connect ion
Figure 26: Connection to integrated or external IP with SSP relay of IP operations
. control is returned to the first SSP. the SSP would have to do protocol conversion from Signalling System No.7 TCAP-based. This approach makes it unnecessary for the SCP to distinguish between integrated and external but directly connected IPs. or directly attached to the SSP that is interacting with the SCP but the operations of the SCP to the IP are relayed via the SSP which performs any needed protocol conversion. and on completion of the user interaction.7 TCAP to DSS1 Facility IE for the operations and responses it relayed between the SCP and the IP). and the IP is attached to another SSP and on completion of the user interaction. the IP is directly attached to the SSP that is interacting with the SCP but the operations of the SCP to the IP are sent directly to the IP without SSP relaying involved. Each of the scenarios will now be examined using arrow diagrams. control is returned to the first SSP. control of the call is retained at that SSP (called the "Hand-off" approach).
b)
c)
d)
e)
In each of the above cases. than the one that is interacting with the SCP but the operations of the SCP to the IP are relayed via the second SSP (called the "Assist" method). the direct messaging between the SCP and the IP may be Signalling System No. the messaging between the SSP and the IP when the SSP does relaying may be DSS1 using the Facility IE (in this case. the operations between the SCP and the SSP may be Signalling System No.Page 100 ETS 300 374-1: September 1994 The cases to be covered are described below and illustrated in figure 25: a) the IP is integrated into the SSP.

Page 101 ETS 300 374-1: September 1994 Case b) requires that the IP indicate to the SCP that it is ready to receive operations. The establishment of the SCF-SRF relationship is explicit. It is necessary to convey a correlation ID to ensure that the transaction established between the SCP and the IP can be correlated to the bearer connection setup as a result of the preceding operation of the SCP to the SSP.

Figure 27: Connection to IP with direct link to SCP, IP initiates interaction with SCP Case c) requires that a transaction be opened with the Assisting SSP so that it may relay operations from the SCP to the IP (integrated or external). Once the bearer control signalling has reached the assisting SSP, it triggers on the identity of the called facility, and initiates an interaction with the SCP that has requested the assistance (it would also be possible to trigger on other IEs such as the incoming address). The bearer control signalling shall contain information to identify the SCP requesting the assistance, and a correlation ID. This information may be hidden in the address information in such a way that non-message based signalling systems may also be used to establish the bearer connection to the assisting SSP. After the AssistRequestInstructions is received by the SCP, the procedures are the same as case a). Figure 28 illustrates the preamble involved.

Page 102 ETS 300 374-1: September 1994 Case d) does not require the establishment of a second transaction from the assisting exchange, hence it need not be an SSP. This then becomes a preamble to the procedure shown in figure 27 as shown in figure 29.

Figure 29: Preamble for Assist case with external IP and direct SCP-IP messaging Case e) merely requires the sending of an operation to the first SSP to route the call to the handed-off SSP, and then figure 26 applies at handed-off SSP. This is shown in figure 30. The activity at handed-off SSP represents a new interaction with the SCP and AssistRequestInstructions is used. Once the bearer control signalling has reached the assisting SSP, it triggers on the identity of the called facility, and initiates an interaction with the SCP that has requested the assistance (it would also be possible to trigger on other IEs such as the incoming address). The bearer control signalling shall contain information to identify the SCP requesting the assistance, and a correlation ID. This information may be hidden in the address information in such a way that non-message based signalling systems may also be used to establish the bearer connection to the assisting SSP.

The end user interaction procedures allow: the sending of one or multiple messages to the end user by using the PlayAnnouncement operations; a dialogue with the end user by using one or a sequence of PromptAndCollectUserInformation operations; a combination of the above; and cancellation of a PlayAnnouncement or PromptAndCollectUserInformation operations by using a generic Cancel operation. Play Announcement/Prompt and Collect user information (PA/P&C)

-

-

7.3.5.2.1

There are only two physical scenarios for user interaction: a) the SSP relays the operations from the SCP to the IP and the responses from the IP to the SCP (SSF relay case); and the operations from the SCP to the IP and the responses from the IP are sent directly between the SCP and the IP without involving the SSP (Direct SCF-SRF case).

Page 104 ETS 300 374-1: September 1994 It is also necessary to consider the capability of Signalling System No.7 TCAP to concatenate several Invoke PDUs in one message. This capability allows, for the scenario in figure 26, the ConnectToResource and the first PA/P&C to be carried in one message. This has some advantages in this physical scenario, such as reduced numbers of messages, and possibly better end-user perceived performance. 7.3.5.3 SRF disconnection procedures

The disconnection procedures are controlled by the SCF and the procedure used is selected based on the needs of the service being executed. The bearer disconnection procedure selected by the SCF is to either allow the SRF to disconnect on completion of user interaction, or to have the SCF explicitly order the SSF to disconnect. SRF disconnect does not cause disconnection by the SSF/CCF back to the end user terminal unless the transaction with the SCF has been terminated, indicating the user interaction completed the call. The SSF/CCF recognizes that a connection to an SRF is involved because the operations from the SCF for this purpose are distinct from the operations that would be used to route the call towards a destination. There is no impact on bearer signalling state machines as a result of this since incoming and outgoing bearer signalling events are not simply transferred to each other, but rather are absorbed in call processing, and regenerated as needed by call processing. Therefore, to achieve the desired functionality, call processing need simply choose not to regenerate the disconnect in the backward direction. Figure 33 illustrates this concept.

Figure 33: Relationship of incoming and outgoing signalling systems to call processing As for the SRF connection procedures, the SRF disconnection is affected by the physical network configuration. In order to simplify the interface between the SCF and the SRF, a number of assumptions are made. The assumptions, and the resulting rules, result in unambiguous procedures from both the SCF and the SRF points of view. The rules, presented below, refer to the SRF originated disconnect, or "SRF Initiated Disconnect", and to the SCF originated disconnect, or "SCF Initiated Disconnect". While other scenarios are possible, they are not included because they either duplicate the functionality presented below or they otherwise do not add value from a service perspective: a) if a series of PA/P&C operations are to be executed by the same SRF, then SRF disconnect is inhibited for all but the last and may be inhibited on the last PA/P&C. When a subsequent PA/P&C is received, it is buffered until the completion of any preceding PA/P&C;

but does not disconnect the SRF.1214 [11] and in this ETS. and returns to the "Waiting for Instructions" state. the SRF is disconnected and the SSF releases resources and handles the transaction between the SSF and the SCF as specified in ITU-T Recommendation Q. for example.
Figure 34: SCF disconnect for Local. that PA/P&C is discarded. after an EstablishTemporaryConnection which is not followed within a reasonable time period by a PA/P&C operation). it completes the dialogue as instructed by the PA/P&C. when SRF initiated disconnect is enabled in a PA/P&C. when the SCF explicitly orders the SSF to disconnect by DisconnectForwardConnection operation. if the user disconnects. When the SRF receives a PA/P&C enabling disconnection. Embedded and Hand-off scenarios
. The SRF disconnect is enabled by the SCF within a PA/P&C operation.3. The SSF/CCF knows that it is an SRF disconnecting and does not continue clearing the call toward the end user. An SRF interacts with one user only and therefore cancelling a PA/P&C only affects the user to which the SRF is connected. An SRF left connected without a PA/P&C to execute may autonomously disconnect if it has not received any PA/P&C operations within a defined time limit (this could occur. This sanity timing value will depend on the nature of the interaction the SRF supports and should be selected by the network operator accordingly. when SRF initiated disconnect is not enabled. the SCF shall either explicitly order "Disconnect" or enable SRF initiated disconnect at the end of the PA/P&C.5. the SSP shown in figure 34 is the "handedoff" SSP.3. then the SRF shall disconnect on completion of the user interaction. No operation reporting SRF disconnect from the SSF to the SCF is required. If the Cancel operation is for a buffered PA/P&C.
NOTE:
Disconnect from SRF is forbidden. In the Hand-off case.Page 105 ETS 300 374-1: September 1994 b) a generic Cancel operation terminates the indicated PA/P&C if it is being executed by the SRF.1
The SRF disconnect procedure is illustrated in figure 34. The SSF returns to the "Waiting for Instructions" state and executes any buffered operations. The SRF discards any buffered operations and returns its resources to idle. and then initiates the SRF initiated disconnection using the applicable bearer control signalling. the SCF shall ask the SRF to inform it of the completion of the User Interaction using the SpecializedResourceReport operation for "announcement complete" or using the return result for the PromptAndCollectUserInformation operation. SRF initiated disconnect
c)
d)
e)
f)
g)
7. the SSF releases the bearer connection to the SRF. The relationship with the SCF is terminated. but the current and any buffered PA/P&Cs are executed.

The Initiating SSF/CCF knows that it is an SRF disconnecting and does not continue clearing the call toward the end user. the initiating SSP. it completes the dialogue as instructed by the PA/P&C. on receipt of the Disconnect Forward Connection from the SCP. and the Direct SCF-SRF case is not shown. The figure shows only the Assisting SSF case. The SRF disconnect is enabled by the SCF within a PA/P&C operation. using applicable bearer control signalling. 7. and this disconnection is propagated to the IP. The SCF initiated disconnect procedures described in the following subclause are used for the Assisting SSF case. knowing that the forward connection was initiated as the result of an Establish Temporary Connection.3. This does not preclude the use of explicit end messages for this purpose. does not disconnect back to the user but returns to the "Waiting for Instructions" state.
Figure 35: SCF initiated disconnect for Assist scenario
. For the Direct SCF-SRF case. To initiate the SCF initiated disconnection of the SRF. Once the DisconnectForwardConnection operation is received by the SSF. a "pre-arranged" end may be used to close the transaction. Therefore. The Initiating SSF returns to the "Waiting for Instructions" state and executes any buffered operations.2 SCF initiated disconnect
The SCF initiated disconnect procedure is illustrated in figure 35 (bearer messages are shown with dotted lines).Page 106 ETS 300 374-1: September 1994 For the Assisting SSF case. When the SRF receives a PA/P&C enabling disconnection." The SCF initiated disconnect uses an operation called DisconnectForwardConnection. the SSF (which instructs bearer signalling to disconnect) and the SRF (which receives disconnect notification via bearer signalling) are aware that disconnect is occurring. disconnects forward to the assisting SSP. the SCF shall request and receive a reply to the last PA/P&C operation requested. For Assisting SSF case. they are synchronized. it will initiate a "release of bearer channel connection" between the PEs containing the SSF and SRF. The initiating SSP. and then initiates the SRF initiated disconnection using the applicable bearer control signalling. Since the SCF (which initiates the disconnect). The SpecializedResourceReport operation contains an "announcement complete" and return result for P&C contains "collected information.3.5. the SRF initiated disconnect procedures are not used because the Assisting SSF remains in the "Waiting for Instructions" state and does not propagate the disconnection of the bearer connection to the Initiating SSF. the procedures also work in the same manner.

5. This is depicted in figure 37.Page 107 ETS 300 374-1: September 1994 7.
.
Figure 36: SSP with integrated SRF In figure 36 above. the SSP with an integrated (or embedded) SRF. PA/P&C Setup. interact with the end user. disconnect the SRF and the end user (bearer connection) and terminate the SCF-SRF relationship. the procedural scenarios can be mapped as given in table 4. Table 4 Procedure Name Connect to Resource and first PA/P&C User Interaction Operations ConnectToResource. The SCP-IP operations are relayed via the SSF in the SSP. PA/P&C PA/P&C SpecializedResourceReport/ RR for P&C SpecializedResourceReport/ RR for P&C Disconnect SpecializedResourceReport/ RR for P&C DisconnectForwardConnection Disconnect Protocol Flows A B A then B C then D C then D C (intra-SSP bearer control) C then D A B (intra-SSP bearer control)
SRF Initiated Disconnect
SCF Initiated Disconnect
A simple extension to this integrated case is the configuration where the SRF is located in an intelligent peripheral locally attached to the SSP.4 Examples illustrating complete user interaction sequences
The following figures and their accompanying tables provide examples of complete sequences of user interaction operations covering the three stages: connect the SRF and the end user (bearer connection) and establish the SCF-SRF relationship.3.

Table 6 Procedure Name Connect to Resource Operations EstablishTemporaryConnection Setup AssistRequestInstructions PA/P&C SpecializedResourceReport/ RR for P&C SpecializedResourceReport/ RR for P&C Disconnect SpecializedResourceReport/ RR for P&C DisconnectForwardConnection Disconnect Protocol Flows A E C B C C F C A E
User Interaction
SRF Initiated Disconnect
SCF Initiated Disconnect
The Assisting SSF scenario involves straightforward procedural extensions to the basic cases shown above.Page 109 ETS 300 374-1: September 1994 In some cases. the IP may have an Signalling System No. Other physical mappings can be derived as described in the text following the figure and its accompanying table. are transparent to the procedures. SRF initiated disconnect cannot be used. In this case. any transit exchanges.
Figure 38: Direct SCP-IP information transfer In figure 38. the procedural scenarios can be mapped as shown in table 6. This case is shown in figure 38. One mapping of the assisting SSF case is shown in figure 39. including the one the IP (SRF) is connected to. In the latter case. The SCP shall correlate two transactions to co-ordinate the activities.7 or other interface to the controlling SCP. The integrated SRF and SSF relay case requires a transaction between the SCP and the assisting SSP (figure 39) but the SCP direct case does not since the transaction is directly between the SCP and the IP connected to the remote exchange.
.

G. The service hand-off scenario can similarly be viewed as a sequence consisting of an IN service to route a call from one SSP to another.Page 110 ETS 300 374-1: September 1994 The SCP shall again correlate two transactions. figure 39 can be used also. For describing this scenario. the procedural scenarios can be mapped as shown in table 7. Table 7 Procedure Name Assist preamble Operations EstablishTemporaryConnection Setup AssistRequestInstructions ConnectToResource Setup ResetTimer PA/P&C SpecializedResourceReport/ RR for P&C SpecializedResourceReport/ RR for P&C DisconnectForwardConnection Disconnect Protocol Flows A E C B G A B then G H then C H then C A E and G (intra-SSP bearer ctrl)
User Interaction
SCF Initiated Disconnect
The Assisting SSP case shown in figure 39 can be generalized to cover both the case where the SRF is embedded in Assisting SSP (as shown). In this latter case. C. the SRF communication (protocol flows B. and H) would conform to the physical scenario shown in figure 37. followed by any one of the previously described physical user interaction scenarios.
Figure 39: SSP Assist/hand-off (Relay SSP) In figure 39. and the case where the SRF is locally connected to Assisting SSP.
.

Protocol Flow A 7) The initiating SSP sends a message via bearer control signalling to the assisting SSP to close the "assist" transaction. the ScfID and the CorrelationID (both used for the assisting SSP to establish communication back to the SCP) is sent to the initiating SSP.3. An EstablishTemporaryConnection operation containing the address of the assisting SSP (for routing the call). EstablishTemporaryConnection is used instead of a regular Connect operation because of the nature of the connection to the assisting SSP. that the temporary connection to the assisting SSP has to be disconnected. Protocol Flow E 8) The call control returns to the initiating SSP. Existing in-band signalling and Signalling System No.
Protocol Flow A 2) The initiating SSP routes the call to the assisting SSP. determines that resources remote from the initiating SSP are required and that call processing will continue from the initiating SSP after the remote resources have been used (e.4. the call will be completed to a destination address after information is collected from the calling party).
. during the processing of a request for instruction. routing number) could be used to transport this information. a DisconnectForwardConnection operation is sent to the initiating SSP. Protocol Flow C 4) The SCP sends instructions to the assisting SSP based on SL control. NOTE: The ScfID and CorrelationID may be included in the routing address of the assisting SSP.g. The CorrelationID is sent in the AssistRequestInstructions to allow the SCP to correlate two transactions.5. The initiating SSP shall be aware that the SCP will ask it to continue in the processing of the call at some point in the future.Page 111 ETS 300 374-1: September 1994 7. The ScfID and CorrelationID are sent to the assisting SSP. This indicates. Protocol Flow B 5) The SCP may need to generate ResetTimer events to the initiating SSP so that it does not time out the call. Protocol Flow A 6) When resource functions have been completed..1 Message sequences for service assist
The following subclause provides additional details on the message sequences for the service assist procedure in figure 39: 1) The SCP. Protocol Flow E 3) The assisting SSP uses an AssistRequestInstructions operation to establish communication with the SCP. The transport mechanism used to send this information between SSPs is independent of the service assist control procedures between the SCF and SSF.g.7 information elements (e.

The CorrelationID is sent in the AssistRequestInstructions to allow the SCP to correlate two transactions. Protocol Flow E 3) The assisting SSP uses an AssistRequestInstructions operation to establish communication with the SCP.3.g. Protocol Flow B 5) The call control remains at the assisting SSP. Protocol Flow C 4) The SCP sends instructions to the assisting SSP based on SL control. routing number) could be used to transport this information.2 Message sequences for hand-off
The following subclause outlines message sequences for the Hand-off procedure using the protocol flows shown in figure 39: 1) The SCP.4. determines that resources remote from the initiating SSP are required and that call processing need not continue from the initiating SSP after the remote resources have been used (e. the ScfID and the CorrelationID (both used for the assisting SSP to establish communication back to the SCP) is sent to the initiating SSP.5.
The same service assist and hand-off procedures can be reused for a direct link to an IP in this and future capability sets. The transport mechanism used to send this information between SSPs is independent of the service assist control procedures between the SCF and SSF. AssistRequestInstructions is used instead of a regular request instruction (InitialDP) because the SCP shall associate the AssistRequestInstructions from the assisting SSP/IP with an already active dialogue the SCP has with another SSP.
. Existing in-band signalling and Signalling System No.Page 112 ETS 300 374-1: September 1994 7. during the processing of a request for instruction.7 information elements (e. a terminating announcement will be played). The ScfID and CorrelationID are sent to the assisting SSP. A Connect operation containing the address of the assisting SSP (for routing the call). NOTE: The ScfID and CorrelationID may be included in the routing address of the assisting SSP.
Protocol Flow A 2) The initiating SSP routes the call to the assisting SSP.g.

1 Operation related error procedures
The following subclauses define the generic error handling for the operation related errors. 8.e.2. The
Procedures at responding entity (SRF) A) Receiving Cancel precondition: SRSM state 3 User Interaction postcondition: SRSM state 3 User Interaction The indicated PA or P&C is terminated if it is presently executing or deleted from the buffer.1.1. The errors are defined as operation errors in Clause 6.1 8.2. the SRF remains connected and the next PA or P&C is executed if available. 8. The error procedure descriptions have been divided in two subclauses.1. i. has been successful. The execution of the indicated PA or P&C is aborted. If the indicated PA or P&C is already executed this causes a failure ("CancelFailed"). B) Receiving Cancelled error precondition: SCSM state any postcondition: SCSM state any After sending a Cancel operation DisconnectForwardConnection).g.2 listing the errors related to error conditions in the different FEs which are not directly related to the INAP operations.
SL dependent SL dependent the SL may continue (e.Page 113 ETS 300 374-1: September 1994
8
Error procedures
This subclause defines the generic error procedures for the core INAP CS1. The SCF remains in the same state.1 decoder already may have been detected during the decoding of the TCAP message and indicated by the TC error indication "MistypedParameter". subclause 8. B) Sending Cancel error precondition: SRSM state 3 User Interaction postcondition: SRSM state 3 User Interaction After returning the "Cancelled" error the SRF stays in the same state. The TCAP services which are used for reporting operation errors are described in Clause 10. sending more PA or P&C or a Cancelled error can therefore be received in any state.1. All errors which can be detected by the ASN. Errors which have a specific procedure for an operation are described in Clause 9 with the detailed procedure of the related operation.1 listing the errors related to INAP operations and subclause 8.1. The SCF is only able to cancel certain predefined SCF->SRF operations.1 Cancelled General description Error description
The error "Cancelled" gives an indication to the SCF that the cancellation. 8.2 Operations SCF->SRF
PlayAnnouncement PromptAndCollectUserInformation Procedures at invoking entity (SCF) A) Sending Cancel precondition: SCSM state 4.1 Waiting for Response from the SRF The SCF sends a Cancel after a PlayAnnouncement (PA) or PromptAndCollectUserInformation (P&C) has been sent. The treatment is SL dependent.2.2 8. as it was requested by the SCF.
.1 Waiting for Response from the SRF postcondition: SCSM state 4. of a specific operation.

tooLate. or already executed.1. Possible failure reasons are: 0 unknownOperation. CancelFailed.Page 114 ETS 300 374-1: September 1994 8. was not successful. operation [1] InvokeID } -. sending more PA or P&C or a CancelFailed error can therefore be received in any state.2 Cancel
Operations SCF->SRF
Procedures at invoking entity (SCF) A) Sending Cancel precondition: SCSM state 4.
SL dependent SL dependent the SL may continue (e.1.1 CancelFailed General description Error description
This error is returned by Cancel if the cancelling of an operation.1 8. precondition: SRSM state 3 User Interaction postcondition: SRSM state 3 User Interaction or SRSM state 1 Idle B) Sending CancelFailed error precondition: SRSM state 3 User Interaction or SRSM state 1 Idle postcondition: SRSM state 3 User Interaction or SRSM state 1 Idle After returning the CancelFailed the SRF stays in the same state. This causes a failure. B) Receiving CancelFailed error precondition: SCSM state any postcondition: SCSM state any After sending a Cancel operation DisconnectForwardConnection).3.
.1 Waiting for Response from the SRF postcondition: SCSM state 4.1. For instance the announcement is finished but the SpecializedResourceReport has not been sent to the SCF yet.1.3. It remains in the same state.3 8.3.1.1. tooLate(1). The
Procedures at responding entity (SRF) A) Receiving Cancel.1 Waiting for Response from the SRF The SCF sends a Cancel after a Play Announcement (PA) or PromptAndCollectUserInformation (P&C) has been sent. operationNotCancellable.3.g.2
PARAMETER SEQUENCE { problem [0] ENUMERATED { unknownOperation(0). when the InvokeID of the operation to cancel is not known to SRF (this may also happen in case the operation has already been completed).The operation failed to be cancelled. The treatment is SL dependent. when the invokeID points to an operation that the SCF is not allowed to cancel. when the invokeID is known but the execution of the operation is in a stadium that it cannot be cancelled anymore.
8.1. operationNotCancellable(2)}. Argument description
1
2
8. The conditions for the occurrence of failure reason "tooLate" may be implementation dependent. However. the indicated PA or P&C is not known. as requested by the SCF.

4.1 Waiting for Response from the SRF Error treatment depends on SL. e.1 Preparing SSF Instructions Error handling depends on the SL.2 Waiting for AssistRequestInstructions postcondition: SCSM state 2.Page 115 ETS 300 374-1: September 1994 8.2 Operations SCF->SRF
PromptAndCollectUserInformation Procedures at invoking entity (SCF) A) SCF sends P&C to SRF precondition: SCSM state 3. selecting another SRF or continue the processing of the call. resulting in the returning of the ETCFailed error to the SCF precondition: SSF FSM state c Waiting for Instructions postcondition: SSF FSM state c Waiting for Instructions No further error treatment.2 Waiting for AssistRequestInstructions B) SCF receives ETCFailed error from SSF precondition: SCSM state 3.1.1.5 8.1 Waiting for Response from the SRF postcondition: SCSM state 4.1 Determine Mode.1.1. indicating the fact that the establishment of a temporary connection to an assisting SSF or SRF was not successful (e.1.1 8. receiving a "Backwards Release" after sending the IAM).2 Operations SCF->SSF
EstablishTemporaryConnection Procedures at invoking entity (SCF) A) SCF sends ETC to SSF precondition: SCSM state 3. after EstablishTemporaryConnection or SCSM state 4. if more PAs or P&Cs are active postcondition: SCSM state 4.4.
.1 Waiting for Response from the SRF. 8.5. P&C will accompany the ConnectToResource or SCSM state 3.1.g.5.1 ImproperCallerResponse General description Error description
The format of the user input has been checked by the SRF and does not correspond to the required format as it was defined in the initiating P&C operation.1 Determine Mode postcondition: SCSM state 3.1 ETCFailed General description Error description
ETCFailed is an error from SSF to SCF.1.1 8.4. SCF can initiate new User Interaction or forcing a Disconnect (to SSF).4 8.1 Waiting for Response from the SRF B) SCF receives ImproperCallerResponse error from SRF precondition: SCSM state 4.5.1.g. 8.2 Waiting for AssistRequestInstructions. Procedures at responding entity (SSF) SSF receives ETC from SCF but the establishment of the connection fails.1. 8.1.

SRF returns ImproperCallerResponse to SCF precondition: SRSM state 3 User Interaction postcondition: SRSM state 3 User Interaction SRF waits for a new operation from SCF. 8. 8.g. in case of assist/hand-off The CCF routes the call if necessary (e.1.1. This may be a new P&C or PA.1 8. indicated by correlationID in AssistRequestInstructions does not exist anymore. in case of assist/hand-off postcondition: SSF FSM state c Waiting for Instructions or SSF FSM state b' Waiting for Instructions.g.1.1. in case of assist/hand-off postcondition: SSF FSM state a Idle or SSF FSM state a' Idle.6.1.g. the customer record in the SCF does not exist.6 8. because the required customer record does not exist. or the requested SLPI. or the SLP may have never existed at all (i. default routing to a terminating announcement).6.1.2 Operations SSF->SCF
AssistRequestInstructions InitialDP Procedures at invoking entity (SSF) A) Sending operation precondition: SSF FSM state b Trigger processing or SSF FSM state b' Waiting for Instructions.e.Page 116 ETS 300 374-1: September 1994 Procedures at responding entity (SRF) A) SRF receives P&C precondition: SRSM state 2 Connected or SRSM state 3 User Interaction postcondition: SRSM state 3 User Interaction B) response from caller is not correct.1 MissingCustomerRecord General description Error description
The SLP could not be found in the SCF. in case of TDPs a SLP is attempted to be invoked). in case of assist/hand-off B) SSF receives error "MissingCustomerRecord" precondition: SSF FSM state c Waiting for Instructions or SSF FSM state b' Waiting for Instructions.
. in case of the operation AssistRequestInstructions). Procedures at responding entity (SCF) The SCSM detects that the required SLP does not exist.3 Operations SRF->SCF
AssistRequestInstructions Procedures at invoking entity (SRF) A) Sending operation precondition: SRSM state 2 Connected postcondition: SRSM state 2 Connected B) SRF receives error "MissingCustomerRecord" precondition: SRSM state 2 Connected postcondition: SRSM state 1 Idle SRF initiated Disconnect. e.6. 8. The SLPI may not exist anymore (e.6. The maintenance functions are informed. The error parameter MissingCustomerRecord is used to inform the invoking entity of this situation.

e.1 MissingParameter General description Error description
There is an error in the received operation argument.1.1.1.1. (2) SSF FSM operation received. The responding entity cannot start to process the requested operation because the argument is incorrect: an expected optional parameter which is essential for the application is not included in the operation argument. The establishment of a connection between the SSF and the SRF took too long or the correlationID was invalid. appropriate event occurred.
.7.7 8.7.2 Operations SCF->SSF
Non-call Associated ActivateServiceFiltering Call Associated/Non-call Processing ApplyCharging FurnishChargingInformation RequestReportBCSMEvent SendChargingInformation Call Associated/Call Processing Connect EstablishTemporaryConnection CollectInformation
CallInformationRequest RequestNotificationChargingEvent ResetTimer
ConnectToResource InitiateCallAttempt
Procedures at invoking entity (SCF) A) Sending operation precondition: SCSM any state in which the above operations can be transferred postcondition: SCSM any state as result of the transfer of any of the above operations B) SCF receives error "MissingParameter" precondition: SCSM any state as result of the transfer of any of the above operations postcondition: SCSM transition to the initial state (i. before sending the erroneous operation) The SL and maintenance functions are informed.Page 117 ETS 300 374-1: September 1994 Procedures at responding entity (SCF) The SCSM detects that the required SLP does not exist (anymore). In both cases the requested SLP cannot be found. Procedures at responding entity (SSF) precondition: (1) SSF FSM appropriate state. The maintenance functions are informed. postcondition: (1) SSF FSM transition to the same state. Further treatment of the call is dependent on SL. The error parameter is returned to inform the SCF of this situation. 8. 8. The error parameter MissingCustomerRecord is used to inform the invoking entity of this situation.1 8. The SSF FSM detects the error in the received operation.1.7.

1 Waiting for Response from the SRF. Procedures at responding entity (SCF) precondition: (1) SCSM appropriate state. If the call is already established (i.1 Waiting for Response from the SRF postcondition: SCSM state 4. the CCF may maintain the call or disconnect it. postcondition: SSF FSM state a Idle After receiving this error. (2) SCSM operation received.
. The error parameter is used to inform the SSF of this situation. The SCSM detects the erroneous situation. the temporary connection is released by the assisting SSF.4 Operations SCF->SRF
PlayAnnouncement PromptAndCollectUserInformation Procedures at invoking entity (SCF) A) Sending operation precondition: SCSM state 3. 8. in case of AssistRequestInstructions. Procedures at responding entity (SRF) precondition: SRSM state 2 Connected or SRSM state 3 User Interaction postcondition: SRSM state 3 User Interaction The SRSM detects that a required parameter is not present in the operation argument.1. In case of an assisting SSF. if more PAs or P&Cs are outstanding.1 Determine Mode.7.2 Waiting for AssistRequestInstructions. postcondition: (1) SCSM state 1 Idle.1 Waiting for Response from the SRF B) Receiving error precondition: SCSM state 4. The choice between these two options is network operator specific.1. SCF can initiate new User Interaction or force Disconnect (to SSF). the SSF FSM returns to the state Idle. after EstablishTemporaryConnection or SCSM state 4.3 Operations SSF->SCF
AssistRequestInstructions InitialDP ApplyChargingReport Procedures at invoking entity (SSF) A) Sending operation precondition: SSF FSM any state in which the above operations can be transferred postcondition: SSF FSM any state as result of the transfer of any of the above operations B) SSF receives error "MissingParameter" precondition: SSF FSM any state as result of the transfer of any of the above operations. P&C or PA will accompany the ConnectToResource or SCSM state 3.Page 118 ETS 300 374-1: September 1994 8. The SCF should take the appropriate actions to treat this error.1 Waiting for Response from the SRF Error treatment depends on SL. appropriate event occurred.7. mid-call trigger or ApplyChargingReport). The SL and maintenance functions are informed.e. in case of InitialDP or ApplyChargingReport or (2) SCSM state 2.1 Preparing SSF Instructions. the CCF routes the call if necessary (default routing to a terminating announcement). The error parameter MissingParameter is used to inform the SCF of this situation. postcondition: SCSM state 4.

7 for the appropriate error procedures.1.1. The SCF might try another SRF.1.1 Preparing SSF instructions The SCSM detects the error in the received operation. 8.9.1.8.Page 119 ETS 300 374-1: September 1994 8.5 Operations SRF->SCF
AssistRequestInstructions Procedures at invoking entity (SRF) A) Sending operation precondition: SRSM state 2 Connected postcondition: SRSM state 2 Connected B) Receiving error precondition: SRSM state 2 postcondition: SRSM state 1 Idle
Connected
Procedures at responding entity (SCF) precondition: SCSM state 3.9 8.1. The SL and maintenance functions are informed. 8.
.1 RequestedInfoError General description Error description
The RequestedInfoError is an immediate response to the CallInformationRequest operation.2 Operations SCF->SSF
Non-call Associated ActivateServiceFiltering Call Associated/Non-call Processing ApplyCharging CallInformationRequest SendChargingInformation Refer to subclause 8.1.2 Waiting for ARI postcondition: SCSM state 2.8.8.8.8 8.1.1. route the call or release the call (SL dependent).1. The error parameter is used to inform the SRF of this situation. 8.1. indicating that the requested information is not known to the SSF or is not available.1.7.9.1 ParameterOutOfRange General description Error description
The responding entity cannot start the processing of the requested operation because an error in a parameter of the operation argument is detected: a parameter value is out of range.7 for the appropriate error procedures.3 Operations SSF->SCF
ApplyChargingReport Refer to subclause 8.1 8.1.1 8. 8.1.

Page 122 ETS 300 374-1: September 1994 8.1 Determine Mode.1 8.1.2 Operations SCF->SSF
Non-call Associated ActivateServiceFiltering
.1.1. and cannot be replaced. postcondition: SCSM state 4.13. if initial PA or P&C or SRSM state 3 User Interaction.1. terminate service processing. SRF sends UnavailableResource.
Procedures at responding entity (SRF) A) SRF receiving PA or P&C precondition: SRSM state 2 Connected. 8.1.1 UnexpectedComponentSequence General description Error description
The responding entity cannot start the processing of the requested operation because a SACF or MACF rule is violated.13.13 8. play a certain announcement and/or collect specific user information). PA or P&C will accompany the ConnectToResource or SCSM state 3.1.1 Waiting for Response from the SRF.e. A reattempt is not possible.1 Waiting for Response from the SRF B) SCF receives UnavailableResource error from SRF precondition: SCSM state 4.2 Waiting for AssistRequestInstructions.1.1 Waiting for Response from the SRF postcondition: SCSM state 4.1 UnavailableResource General description Error description
The SRF is not able to perform its function (i. precondition: SRSM state 3 User Interaction postcondition: SRSM state 3 User Interaction 8.13.12.12 8. service processing without PA or P&C (if possible).12.1. or the operation could not be processed in the current state of the FSM.1 Waiting for Response from the SRF If the chosen resource cannot perform its function the further treatment is service dependent. if not initial PA or P&C B) SRF is not able to perform its function (and cannot be replaced). 8. EXAMPLE: request SSF to connect to alternative SRF.1 8.12.1.1. after EstablishTemporaryConnection or SCSM state 4. if more PAs or P&Cs are outstanding.2 Operations SCF->SRF
PlayAnnouncement PromptAndCollectUserInformation Procedures at invoking entity (SCF) A) SCF sends PA or P&C to SRF precondition: SCSM state 3.

sends the UnexpectedComponentSequence error and remains in the same state. The SCF detects the erroneous situation. In the SCF the SL and maintenance functions are informed and the SL decides about error treatment. NOTE: This error does not overlap with "ParameterOutOfRange".14 8. On receiving the parameter the SRF moves to idle and releases the temporary connection.1.Page 123 ETS 300 374-1: September 1994 Call Associated/Non-call Processing ApplyCharging FurnishChargingInformation RequestReportBCSMEvent SendChargingInformation Call Associated/Call Processing CollectInformation ConnectToResource DisconnectForwardConnection InitiateCallAttempt CallInformationRequest RequestNotificationChargingEvent ResetTimer
Connect Continue EstablishTemporaryConnection
In this case the SSF detects the erroneous situation.1.13. In that case the SCF returns the error parameter.14. On receiving the error the SSF moves to Idle. 8.
. Possible error treatment is to send the DisconnectForwardConnection operation to the SSF.1 8. On receiving the error the assisting SSF moves to Idle and the temporary connection is released.5 Operations SRF->SCF
AssistRequestInstructions In this case an error occurs if the SRF has already an established relationship with the SCF and for some reason sends a AssistRequestInstructions.1. 8. In the SCF the SL and maintenance functions are informed and the SL decides about error treatment. In case the operation is sent by an "initiating" SSF in the context of an existing relationship.1. the SCF returns the error parameter.1 UnexpectedDataValue General description Error description
The responding entity cannot complete the processing of the requested operation because a parameter has an unexpected data value.1. 8. sends the UnexpectedComponentSequence error and remains in the same state.13. 8.1.3 Operations SSF->SCF
ApplyChargingReport AssistRequestInstructions InitialDP In case of assisting SSF an error occurs in case an AssistRequestInstructions is sent while a relationship between SCF and assisting SSF has already been established.14. SL and maintenance are informed.13. SL and maintenance are informed. informs SL and maintenance functions and returns the error parameter.4 Operations SCF->SRF (only applicable for direct SCF-SRF case)
PlayAnnouncement PromptAndCollectUserInformation In this case the SRF detects the erroneous situation.1.

16.1.2.1 8. indicated by the LegID parameter value in the operation.5 Operations SRF->SCF
AssistRequestInstructions Refer to subclause 8.16 8.1.16.7 for the appropriate error procedures.1.4 Operations SCF->SRF
PlayAnnouncement PromptAndCollectUserInformation Refer to subclause 8. The responding entity is the entity which receives the error report.1.1.1.1. 8.Page 125 ETS 300 374-1: September 1994 Call Associated/Call Processing CollectInformation ConnectToResource InitiateCallAttempt Connect EstablishTemporaryConnection
Refer to subclause 8.1.1 8.15.1.7 for the appropriate error procedures.7 for the appropriate error procedures.2 Operations SCF->SSF
Call Associated/Non-call Processing SendChargingInformation Refer to subclause 8.1.3 Operations SSF->SCF
AssistRequestInstructions InitialDP ApplyChargingReport Refer to subclause 8. 8.2.1. the invoking entity is denoted here as the entity at which the error situation is detected.1.1. is unknown to the SSF.2.15.1 Expiration of TSSF General description Error description
A timeout occurred in the SSF on the response from the SCF.7 for the appropriate error procedures.1 UnknownLegID General description Error description
This error is used to indicate to the SCF that a specific leg. The TCAP services used for reporting errors are described in Clause 10.1. 8.7 for the appropriate error procedures. 8. 8. 8.1.15. Since the error situations are not originated by the reception of an operation.16. 8.2 Entity related error procedures
The following subclauses define the error handling for the entity related errors.1 8.
.1.

2.
. if the abort is received on an assisting SSF dialogue. the CCF routes the call if necessary (e.1 8. Procedure at the responding entity (SCF) SCF receives a dialogue abort precondition: Any state postcondition: SCSM state 1 Idle. The abort is reported to the maintenance functions. Procedure at the responding entity (SCF) SCF receives a dialogue abort precondition: SCSM state 4 User Interaction postcondition: SCSM state 2 Preparing SSF instructions The SCF releases all resources related to the dialogue. if the abort is related to an assisting SSF dialogue The SCF releases all allocated resources and reports the abort to the maintenance functions. if the abort is related to a SSF dialogue or SCSM state 2 Preparing SSF instructions.2.2.2.2 Procedures SRF->SCF
Procedure at the invoking entity (SRF) Timeout occurs in SRF on TSRF precondition: SRSM state 2 Connected or SRSM state 3 User Interaction postcondition: SRSM state 1 Idle The SRF aborts the dialogue and moves to the Idle state.1.2 Procedures SSF->SCF
Procedure at the invoking entity (SSF) Timeout occurs in SSF on TSSF precondition: SSF FSM state c Waiting for instructions or SSF FSM state d Waiting for end of User Interaction or SSF FSM state e Waiting for end of Temporary connection postcondition: SSF FSM state a Idle The SSF FSM aborts the dialogue and moves to the Idle state.Page 126 ETS 300 374-1: September 1994 8. all allocated resources are de-allocated.2.2. 8. The SCF releases all resources related to the dialogue. reports the abort to the maintenance functions and returns to state preparing SSF instructions.2. reports the abort to the maintenance functions and returns to state preparing SSF instructions. 8.1 Expiration of TSRF General description Error description
A timeout occurred in the SRF on the response from the SCF. The abort is reported to the maintenance functions.g. default routing to a terminating announcement).2. This procedure concerns only the direct SCF-SRF case.2 8.1. if the abort is received on a SSF dialogue.

variableMessage: This parameter specifies an announcement with one or more variable parts. text: This parameter indicates a text to be sent. The text shall be transformed to inband information (speech). sFBillingChargingCharacteristics: This parameter determines the charging to be applied for service filtering. The attributes of text may consist of items such as language. the call shall be released.1. For the transfer of service filtering results refer to the operation ServiceFilteringResponse. the time between the end of the announcement and the start of the next repetition. messageID: This parameter indicates the message(s) to be sent.
-
-
.1
Detailed operation procedures
ActivateServiceFiltering procedure General description
When receiving this operation. the SSF handles calls to destinations in a specified manner without request for instructions to the SCF.1 9. 9. In the case of service filtering the SSF executes a specific service filtering algorithm. At the end of information sending.Page 127 ETS 300 374-1: September 1994
9
9. Its content is network specific. It includes information about the announcement to be played. elementaryMessageIDs: This parameter specifies a sequence of announcements.
-
-
-
-
-
numberOfRepetitions: This parameter indicates the maximum number of times the message shall be sent to the end-user. interval: This parameter indicates the time interval in seconds between repetitions.e.1 Parameters
filteredCallTreatment: This parameter specifies how filtered calls are treated. inbandInfo: This parameter specifies the inband information to be sent. ZERO indicates endless repetition. the number of counters used and the release cause to be applied to filtered calls. the charging approach. duration: This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. it can be one of the following: elementaryMessageID: This parameter indicates a single announcement.1. informationToSend: This parameter indicates an announcement. a tone or display information to be sent to the calling party. i.1. This parameter can only be used when the number of repetitions is greater than one.

An interval of -1 indicates that none of the calls matching the filtering criteria will either result in sending of an InitialDP operation or a ServiceFilteringResponse operation.g. interval: After expiration of the interval timer the next call to arrive causes following actions: sending of an InitialDP. Other values indicate duration in seconds. i.
-
. "maximumNumberOfCounters" subsequent destination addresses beginning with the destination address provided in "filteringCriteria" are used for service filtering.e.
-
-
filteringCharacteristics: This parameter indicates the severity of the filtering and the point in time when the ServiceFilteringResponse shall be sent. starting again the interval timer. This information can not be received by a PSTN end-user. An interval of 0 indicates that all calls matching the filtering criteria will result in sending of an InitialDP operation and no filtering will be applied (i. duration: This parameter indicates the time duration in seconds of the tone to be sent. toneID: This parameter indicates the tone to be sent. releaseCause: This parameter provides the cause value used for call release after the "informationToSend" (e. When filtering is started the first interval is started. A number of calls of 0 indicates that none of the calls matching the filtering criteria will result in sending of an InitialDP operation and a ServiceFilteringResponse operation.
-
-
displayInformation: This parameter indicates a text string to be sent to the end-user. If "releaseCause" is not present.e. ZERO indicates infinite duration. numberOfCalls: The nth call causes an InitialDP and a ServiceFilteringResponse operation sent to the SCF. no ServiceFilteringResponse will be sent). The number of counters may only be > 1 if the "filteringCriteria" are of the type "addressAndService". One counter is assigned to each of these destination addresses. sending of a ServiceFilteringResponse. This threshold value is met if the sum of all counters assigned to one service filtering entity is equal to "numberOfCalls". It determines whether the "interval" or the "numberOfCalls" are used. the default value is the same as the ISUP value decimal 31 (normal unspecified).
-
maximumNumberOfCounters: This parameter provides the number of counters to be allocated as well as the number of destinations included in the service filtering.Page 128 ETS 300 374-1: September 1994 tone: This parameter specifies a tone to be sent to the end-user.. announcement) has been sent to the calling party.

then service filtering is stopped and the final report is sent to the SCF. The geographical area may also be identified ("callingAddressValue" and/or "locationNumber"). addressAndService: This parameter identifies the IN service and dialled number for which filtering should be applied. serviceKey: This parameter identifies unambiguously the requested IN service for which filtering should be applied. A duration of -1 indicates an infinite duration. serviceKey: calledAddressValue: This parameter contains the dialled number towards which filtering shall be applied. callingAddressValue: This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied. A duration of 0 indicates that service filtering is to be removed. It is used when "callingAddressValue" does not contain any information about the geographical location of the calling party. "callingAddressValue".
-
-
filteringCriteria: This parameter specifies which calls are filtered based on "serviceKey". locationNumber: This parameter identifies the geographical area from which the call to be filtered originates. i. Other values indicate duration in seconds. a ServiceFilteringResponse is sent to the SCF and service filtering is stopped. "calledAddressValue" or "locationNumber". If "stopTime" was already met. then service filtering is immediately stopped and the actual counter values are reported to the SCF. Two approaches are supported ("duration" or "stopTime"): duration: If the duration time expires. stopTime: When the "stopTime" is met then service filtering is stopped and the final report is sent to the SCF. A duration of -2 indicates a network specific duration. This occurs in cases where the SCF wishes to explicitly stop a running service filtering.
. the SSF starts filtering immediately.
-
-
-
-
startTime: This parameter defines when filtering is started. If "startTime" is not provided or was already met.e. It is a choice of "servicekey" or "addressAndService". When the time expires.Page 129 ETS 300 374-1: September 1994 filteringTimeOut: This parameter indicates the duration of the filtering. the value of the "stopTime" is less than the value of the actual time but the difference does not exceed the value equivalent to 50 years. The complete called party number shall be specified.

2. The SSF then proceeds as described for "ServiceFilteringResponse". A number of counters will be allocated and reset. To change the parameters of an existing service filtering entity the SCF has to send an ActivateServiceFiltering operation with the same "filteringCriteria".1.2. "filteringCriteria".1 Invoking entity (SCF) Normal procedure
SCF precondition: (1) SLPI detects that service filtering has to be initiated at the SSF. Sending the ActivateServiceFiltering operation causes a transition of the SCME from the state "Service Filtering Idle" to the state "Waiting For SSF Service Filtering Response". If the service filtering proceeds then the SSME FSM remains in the state "Non-Call Associated Treatment". If the operation ActivateServiceFiltering addresses an already existing service filtering entity the parameters "filteredCallTreatment". the service filtering will be started at the specified point in time.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. Then it moves to the state "Service Filtering Idle".1 Responding entity (SSF) Normal procedure
SSF precondition: None. "filteringTimeOut" and "startTime" are set as provided in the operation. That causes no state transition in the SCME.3 9. Otherwise the SSME FSM moves to state "Idle Management". SCF postconditions: (1) SLPI starts an application timer to monitor the expected end of service filtering. The SCME is informed by the SLPI about timer expiration. The SCME remains in this state until the application timer in the SLPI expires.1. In the case of the "startTime" that has not been met yet. (2) The SCME is in the state "Waiting for SSF Service Filtering Response". In the case that the addressed service filtering entity is active the SSF reports the counter values to the SCF via the operation "ServiceFilteringResponse". "filteringCharacteristics". i.Page 130 ETS 300 374-1: September 1994 9.1.e.1. This SSME FSM enters the state "Non-Call Associated Treatment" and initializes the service filtering for the specified IN calls.2 9. or alternatively the criteria with the largest number of parameters specified. In the case of the "startTime" that has not been met yet. the service filtering will be continued at the specified point in time.1. The service filtering process is stopped if an already expired "stopTime" or "duration" equal to ZERO or a new not yet met "startTime" is provided. The parameters "filteredCallTreatment".
. "filteringCharacteristics" "filteringTimeOut" and "startTime" are modified as provided in the operation. If no errors occurred after receiving an ActivateServiceFiltering at the SSF an empty return result is sent to the SCF. 9.3. the criteria with the longest "callingAddressValue" or "locationNumber". 9. When a call matches several active "filteringCriteria" it should be subject to filtering on the most specific criteria. The second parameter set replaces the first one. SSF postcondition: (1) The SSME FSM is in the state "Non-call Associated Treatment". If there is no already existing SSME FSM for the "filteringCriteria" provided then a new SSME FSM is created.

If no errors occurred after receiving an ActivateServiceFiltering on the SSF an empty return result is sent to the SCF. then it will check the "callingAddressValue" and perform filtering depending on that parameter. That causes no state transition in the SSME FSM.2. Error handling
9. (2) The activity test timer expires. Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. The event is recorded in the SSF and an error condition indicated. If no reply is received.1. then the SCF will assume that the SSF has failed in some way and will take the appropriate action.2. If the relationship is still in existence. If an ActivateServiceFiltering operation is passed to the SSF with the "filteringCriteria" "addressAndService" with both "callingAddressValue" and "locationNumber" present.1 ActivityTest procedure General description
This operation is used to check for the continued existence of a relationship between the SCF and SSF. duration time for service filtering.1. the service filtering data remains unchanged. the relationship is ended and all concerned resources are released.2 9.Page 131 ETS 300 374-1: September 1994 When performing service filtering with the "filteringCriteria" "addressAndService" the first parameters checked will always be the "serviceKey" and "calledAddressValue".2 9. 9.2.2
If the SSF detects an error with any of the defined error values then this error is reported to the SCF. TActTest. The following application timers are used: detect moment to start service filtering (start time). then the SSF will respond. The SSME FSM remains in the state "Idle Management". 9. 9. In case a new SSME FSM should be created.2. interval time for service filtering (for timer controlled approach). In case there is already an existing SSME FSM.1 Invoking entity (SCF) Normal procedure Parameters
SCF preconditions: (1) A relationship exists between the SCF and the SSF. The SSME FSM remains in the state "Non-Call Associated Treatment".1 None. it investigates whether or not the "locationNumber" is present in the initial address message. after which the ActivityTest operation is sent to the SSF.3. If the SSF finds that the "locationNumber" is absent.2. If it is present and matches the active "filteringCriteria" the call is filtered.
. the following is applicable: When the SSF receives a call that matches "serviceKey" and "calledAddressValue" (in the active "filteringCriteria").

1 ApplyCharging procedure General description Error handling
This operation is used for interacting from the SCF with the SSF charging mechanisms. If it is not present. Its contents is network operator specific. SSF postconditions: (1) The SSME FSM stays in.1 Responding entity (SSF) Normal procedure
SSF precondition: (1) A relationship exists between the SCF and the SSF. The ApplyChargingReport operation provides the feedback from the SSF to the SCF.3. If a time-out is received.2 Not applicable. (2) If the dialogue ID is active and if there is a SSF FSM using the dialogue.2.1. partyToCharge: This parameter indicates the party in the call to which the ApplyCharging operation should be applied.3.3 9. sendCalculationToSCPIndication: This parameter indicates that ApplyChargingReport operations (at least one at the end of the connection configuration charging process) are expected from the SSF. the SCME resets the activity test timer and takes no further action.3. 9. then it is applied to the A-party.2.1 and 4.2. The SLPI that was the user of this dialogue will be informed. the SSME FSM returns to the state "Idle Management". As several connection configurations may be established during a call. a possibility exists for the ApplyCharging to be invoked at the beginning of each connection configuration. the SSME will in that case never receive the ActivityTest operation and thus will not be able to reply.Page 132 ETS 300 374-1: September 1994 SCF postcondition: (1) If a return result "ActivityTest" is received. The charging scenarios supported by this operation are scenarios 4.2. the corresponding SCSM FSM will move to the state "Idle". the SSME sends a return result "ActivityTest" to the SCF. 9. If there are no other management activities. 9. SCF aborts the dialogue. 9. this is an indication that the relationship with the SSF was somehow lost.
-
-
.2. This parameter is always set to TRUE. 9. or moves to the state "Non-call Associated Treatment".3 9.3.2 Error handling
If a time out on the ActivityTest operation or a P-Abort is received from TCAP. the TCAP in the SSP will issue a P-Abort. for each party.1 Parameters
aChBillingChargingCharacteristics: This parameter specifies the charging related information to be provided by the SSF and the conditions on which this information has to be reported back to the SCF via the ApplyChargingReport operation. or If the dialogue ID is not active.2 (refer to Annex B).

the SSF sets the charging data using the information elements included in the operation and acts accordingly. or the assisting/hand-off SSF FSM is in state: "Waiting for Instructions" (state b) SSF postcondition: (1) No FSM state transition On receipt of this operation.2 Error handling
MissingParameter: This error is indicated if the "sendCalculationToSCPIndication" is not provided. the ApplyChargingReport operation may be used several times. 9. if requested.2.2 9. During a connection configuration the ApplyChargingReport operation may be invoked on multiple occasions.3. Generic error handling for the operation related errors is described in Clause 8 and the TCAP services used for reporting operation errors are described in Clause 10.3. or "Waiting for End of User Interaction" (state d).3.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services used for reporting operation errors are described in Clause 10. (2) The SLPI has determined that an ApplyCharging operation has to be sent. The charging scenarios supported by this operation are scenarios 4. UnexpectedDataValue: This error is indicated if the "sendCalculationToSCPIndication" is set to FALSE. SCF postconditions: (1) No FSM state transition.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) The SSF FSM is in one of the following states: "Waiting for Instructions" (state c). At least one ApplyChargingReport operation shall be sent at the end of the connection configuration charging process.
.4. For each call party and each connection configuration.1 ApplyChargingReport procedure General description
This operation is used by the SSF to report charging related information to the SCF as requested by the SCF using the ApplyCharging operation.1 and 4.4 9. In addition.3. the SSF will start the monitoring of the end of the connection configuration and other charging events.1 Invoking entity (SCF) Normal procedure
SCF Preconditions (1) A control relationship exists between the SCF and the SSF. 9.3. 9.3 9. 9. The SCSM FSM is in state "Preparing SSF Instructions" or is in state "Queuing FSM".3. This operation is invoked by the SCF if a SLPI results in the request of interacting with the charging mechanisms within the SSF to get back information about the charging. or "Waiting for End of Temporary Connection" (state e). (2) The SLPI is expecting ApplyChargingReport operations from the SSF.3.2.3.2 (refer to Annex B).Page 133 ETS 300 374-1: September 1994 9.

4.4.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services used for reporting operation errors are described in Clause 10.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services used for reporting operation errors are described in Clause 10. 9. This operation is invoked if a charging event has been detected that was requested by the SCF.2. durations. including EventReportBCSM and CallInformationReport. Examples of charging events may be: threshold value reached. time stamps.3 9. timer expiration. the SLPI which is expecting this operation will continue. On receipt of this operation.
.1
SSF preconditions: (1) A control relationship exists between the SCF and the SSF. The "CallResult" will include the "partyToCharge" parameter as received in the related ApplyCharging operation to correlate the result to the request.2.3. The remaining content of "CallResult" is network operator specific. 9. etc. tariff change. costs. or otherwise shall remain in the same state. tariff change and time of change. Invoking entity (SSF) Normal procedure
9.4.1 Responding entity (SCF) Normal procedure
SCF preconditions: (1) An ApplyCharging operation with its "sendCalculationToSCPIndication" parameter set to TRUE has been sent at the request of an SLPI and the SLPI is expecting an ApplyChargingReport from the SSF. SCF postconditions: (1) No FSM state transition if further reports.4. SSF postconditions: (1) If the connection configuration does not change then no FSM state transition shall occur.4.1. If the connection configuration changes then the FSM shall move to: "Idle" state if there is no other EDP armed and no report requests are pending. etc. (2) A charging event has been detected that was requested by the SCF via an ApplyCharging operation.4.4.3.1 Parameters
CallResult: This parameter provides the SCF with the charging related information previously requested using the ApplyCharging operation with its "sendCalculationToSCPIndication" parameter set to TRUE. are expected. or Transition to the state "Idle" if the report is the last one and no EventReportBCSM or CallInformationReport is expected. Examples of these contents may be: bulk counter values. 9. end of connection configuration.2 9.Page 134 ETS 300 374-1: September 1994 9. The ApplyChargingReport operation only deals with charging events within the SSF itself.

This parameter is applicable to this operation only in the physical scenarios corresponding to assist with relay or hand-off.1 Parameters
correlationID: This parameter is used by the SCF to associate the AssistRequestInstructions from the assisting SSF or by a SRF with the InitialDP from the initiating SSF. The use of this parameter is network operator dependent. The assisting SSF FSM transitions to state "Waiting For Instructions".
. The value of the "correlationID" may be extracted from the digits received from the initiating SSF or be all of the digits.2.e. which is acting as the assisting SSF in an assist or hand-off procedure.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. the SSF or SRF shall assure that the required resources are available to invoke an AssistRequestInstructions operation in the SSF/SRF and indicate to the initiating SSF that the call is accepted.5. or by a SRF. On receipt of an assist indication from the initiating SSF. not exhausted) at the SSP. The operation is sent when the assisting SSF or SRF receives an indication from an initiating SSF containing information indicating an assist or hand-off procedure. 9.1 Responding entity (SCF) Normal procedure
SCF preconditions: (1) A control relationship exists between the SCF and the initiating SSF. The use of this parameter is network operator dependent.Page 135 ETS 300 374-1: September 1994 9.2 9.5.5.5. which initiated the assist indication. The AssistRequestInstructions operation is invoked by the SSF or SRF after the call. SSF postcondition: (1) The assisting SSF waits for instructions. iPSSPCapabilities: This parameter is sent by the assisting or hand-off SSP to indicate which SRF resources are supported within the SSP and attached and available.1
SSF precondition: (1) An assist indication is detected by the assisting SSF.1.3. 9.5. SCF postcondition: (1) An SSF or SRF instruction is being prepared.3 9.1 AssistRequestInstructions procedure General description
This operation is sent to the SCF by an SSF. is accepted. 9.5 9.5. iPAvailable: This parameter is sent by the assisting or hand-off SSP to indicate whether or not an IP is attached and available (i.5. This parameter is applicable to this operation only in the physical scenarios corresponding to assist with relay or hand-off. Invoking entity (SSF/SRF) Normal procedure
-
-
9. (2) The SCF waits for AssistRequestInstructions.2.

and the resource is available. callingAddressAndService: This parameter indicates that call gapping will be applied when the "serviceKey" and the leading digits of the calling party number or the location number of a call attempt match those specified in "gapCriteria".1. The SCF determines SSF/SRF by means of "correlationID". A duration of -2 indicates a network specific duration.6. A duration of -1 indicates an infinite duration.1 Parameters
gapCriteria: This parameter identifies the criteria for a call to be subject to call gapping. the SCSM prepares the PlayAnnouncement or PromptAndCollectUserInformation to be sent to the SRF.6. the SCSM prepares the ConnectToResource and PlayAnnouncement or PromptAndCollectUserInformation to be sent to the assisting SSF. If the AssistRequestInstructions operation was received from a SRF.1 CallGap procedure General description
This operation is used to request the SSF to reduce the rate at which specific service requests are sent to the SCF. Other values indicate duration in seconds. and the resource is available. A duration of 0 indicates that gapping is to be removed. calledAddressValue: This parameter indicates that call gapping will be applied when the leading digits of the dialled number of a call attempt match those specified in "gapCriteria". gapOnService: This parameter indicates that call gapping will be applied when the "servicekey" of a call attempt match those specified in "gapCriteria".2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. the SCP has to perform the following actions: If the AssistRequestInstructions operation was received from an assisting SSF.6 9.3.5. duration: Duration specifies the total time interval during which call gapping for the specified gap criteria will be active.
-
-
-
-
gapIndicators: This parameter indicates the gapping characteristics. calledAddressAndService: This parameter indicates that call gapping will be applied when the "serviceKey" and the leading digits of the dialled number of a call attempt match those specified in "gapCriteria". "destinationNumber" or network knowledge. 9. 9. 9.
.Page 136 ETS 300 374-1: September 1994 On receipt of this operation in the SCSM state "Waiting for Assist Request Instructions".

variableMessage: This parameter specifies an announcement with one or more variable parts. The attributes of text may consist of items such as language. It should be noted that also non-IN controlled traffic control mechanism can apply to an exchange with the SSF functionality. The controlType "manuallyInitiated" will have priority over "sCPOverloaded" call gap. An interval of -1 indicates that all calls meeting the gap criteria are to be rejected.
-
controlType: This parameter indicates the reason for activating call gapping. this traffic control has implicit priority over the IN controlled traffic control. The non-IN controlled traffic control and co-ordination of several traffic control mechanisms are out of the scope of core INAP. text: This parameter indicates a text to be sent. messageID: This parameter indicates the message(s) to be sent. informationToSend: This parameter indicates an announcement. gapTreatment: This parameter indicates how calls that were stopped by the call gapping mechanism shall be treated.
-
. it can be one of the following: elementaryMessageID: This parameter indicates a single announcement.Page 137 ETS 300 374-1: September 1994 gapInterval: This parameter specifies the minimum time between calls being allowed through. The text shall be transformed to inband information (speech). elementaryMessageIDs: This parameter specifies a sequence of announcements. a tone or display information to be sent to the calling party. inbandInfo: This parameter specifies the inband information to be sent. duration: This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. ZERO indicates endless repetition. As the non-IN controlled traffic control is within the CCF. Therefore it is recommended to take measures to coordinate several traffic control mechanisms. Other values indicate interval in milliseconds. or any other situation that requires manually initiated controls. An interval of 0 indicates that calls meeting the gap criteria are not to be rejected. The "controlType" value "manuallyInitiated" indicates that the service and or network/service management centre has detected a congestion situation. At the end of information sending. The non-IN controlled traffic control may also have some influence to the IN call. The "controlType" value "sCPOverloaded" indicates that an automatic congestion detection and control mechanism in the SCP has detected a congestion situation.
-
-
-
-
-
numberOfRepetitions: This parameter indicates the maximum number of times the message shall be sent to the end-user. the call shall be released.

2 Error handling
Operation related error handling is not applicable. After detection of a congestion situation the parameters for the CallGap operation are provided. the call shall be released.Page 138 ETS 300 374-1: September 1994 interval: This parameter indicates the time interval in seconds between repetitions. If no congestion is detected gapping may be removed. A congestion detection and control algorithm monitors the load of SCP resources. releaseCause: This parameter indicates that the call shall be released using the given release cause.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) Call gapping for gapCriteria is not active. Invoking entity (SCF) Normal procedure
-
-
9.3.2 9. A manual initiated call gap will take prevail over an automatic initiated call gap.
-
tone: This parameter specifies a tone to be sent to the end-user. This parameter can only be used when the number of repetitions is greater than one.e. due to class 4 operation. 9. ZERO indicates infinite duration.2. SCF postcondition: (1) The SCME FSM remains in the same state upon issuing the CallGap operation.
-
-
displayInformation: This parameter indicates a text string to be sent to the end-user.6. or The SCF receives a manually initiated call gapping request from the SMF.1
SCF preconditions: (1) The SCF detects an overload condition persists and call gapping has to be initiated at the SSF. If the congestion level changes new CallGap operations may be sent for active gap criteria but with new gap interval. or Call gapping for gapCriteria is active. At the end of information sending.6. using the given release cause.6.3 9. i. toneID: This parameter indicates the tone to be sent. the time between the end of the announcement and the start of the next repetition. 9. both: This parameter indicates inband information.2.
.6. duration: This parameter indicates the time duration in seconds of the tone to be sent.6. This information can not be received by a PSTN end-user. a tone or display information to be sent to the calling party.

the SSME FSM moves to state "Idle Management". no InitialDP is sent and the call is treated as indicated by "gapTreatment".2 Error handling
Operation related error handling is not applicable. then the new parameters (i. if the (new) "controlType" is different than the existing "controlType". In case of gapping on "callingAddressAndService" and the parameter "locationNumber" is present. The call gap process is stopped if the indicated duration equals ZERO. or Call gapping for gapCriteria is removed. In case call gapping was initiated for "calledAddressAndService" or "callingAddressAndService" and the "serviceKey" matches. the codes 1234 and 12345 are under control. an InitialDP operation can be sent.3. If a call to a controlled number matches only one "gapCriteria". More specifically.
. then only the "gapCriteria" associated with the longest called party number should be used. If a gap interval is active. If not. the manuallyInitiated call gapping will prevail over automatically initiated ("sCPOverloaded"). This SSME FSM enters the state "Non-call associated treatment" and initializes call gapping for the specified IN calls. If call gapping proceeds then the SSME FSM remains in the state "Non-call associated treatment". "gapIndicators". If a call to a controlled called number matches several active "gapCriteria". 9.6. Then the call with 123456 is subject to the control on 12345. If both "manuallyInitiated" and "sCPOverload" controls are active. gapping will be performed on "locationNumber" instead of "callingAddressValue".e. If not. If there is no already existing SSME FSM for the gap criteria provided then a new SSME FSM is created. it will check if call gapping was initiated either for the "serviceKey" or for the "calledAddressValue" assigned to this TDP.
If the SSF meets a TDP. or Call gapping for gapCriteria is renewed.. a check on the "calledAddressValue" and "callingAddressValue" (and optionally "locationNumber") for active call gapping is performed. then: 1) 2) if the (new) "controlType" equals an existing "controlType". and "gapTreatment") will be appended to the appropriate SSME FSM (in addition to the existing parameters). then the "manuallyInitiated" control will be applied. if both "manuallyInitiated" and "sCPOverloaded" "controlType" values are active for this "gapCriteria". an InitialDP operation can be sent. then only the manually initiated control will be applied. due to class 4 operation. If call gapping shall be applied and there is no gap interval active. "gapIndicators" and "gapTreatment") will overwrite the existing parameter values.e. Otherwise. "controlType" and "gapTreatment" for the indicated gap criteria will be set as provided by the CallGap operation. For example. A new gap interval will be initiated as indicated by "gapInterval". The parameters "gapIndicators". In general.Page 139 ETS 300 374-1: September 1994 SSF postconditions: (1) The SSME FSM is in the state "Non-call associated treatment". Furthermore.. then the new parameters (i. an InitialDP operation can be sent including the "cGEncountered" parameter according to the specified controlType. and the corresponding control should be applied. "controlType". The SSME FSM remains in the state "Non-Call Associated Treatment". the following rules will be applied in the SSF to manage the priority of different control Types associated with the same "gapCriteria": If an SSME FSM already exists for the "gapCriteria" provided. (2) Call gapping for gapCriteria is activated. then the corresponding control is applied.

2 Error handling
Operation related error handling is not applicable. release call initiated by the SCF. route select failure indicated by the network. due to class 4 operation.g.1 Parameters
requestedInformationList: According to the requested information the SSF sends the appropriate types and values to the SCF.1. Invoking entity (SSF) Normal procedure
9.7.2.1
SSF preconditions: (1) At least one party disconnects from a call.7 9. in the case of follow-on. If a CallInformationReport has been sent to the SCF then no CallInformationReport is pending. If the SSF FSM executes a state transition caused by one of the following events: A party release. a further CallInformationReport.
and a CallInformationRequest is pending then the CallInformationReport operation is sent to the SCF.2. has to be explicitly requested by the SCF. SSF no answer timer expiration.2 9.7. If the event causing the CallInformationReport is also detected by an armed EDP-R then immediately after CallInformationReport the corresponding EventReportBCSM has to be sent. SSF postcondition: (1) The SSF FSM shall move to the "Idle" state in the case where no other report requests are pending and no EDPs are armed otherwise the SSF FSM shall remain in the same state.
.1 CallInformationReport procedure General description
This operation is used to send specific call information for a single call to the SCF as requested by the SCF in a previous CallInformationRequest operation. (2) Requested call information has been collected. If the event causing the CallInformationReport is also detected by an armed EDP-N then immediately before CallInformationReport the corresponding EventReportBCSM has to be sent. i.7.e. (3) CallInformationReport is pending due to a previously received CallInformationRequest operation.Page 140 ETS 300 374-1: September 1994 9. (4) A control relationship exists between the SCF and the SSF.7. B party release.7. 9. A party abandon. 9. B party busy. e.

In case of unsuccessful call setup the network event indicating the unsuccessful call setup stops the measurement of "callAttemptElapsedTime".1. (2) A control relationship exists between the SCF and the SSF. callConnectedElapsedTime: This parameter indicates the duration between the received answer indication from the called party side and the release of the connection.3.1 Responding entity (SCF) Normal procedure
SCF preconditions: (1) An SLPI is expecting CallInformationReport.8 9. If CallInformationReport is outstanding and the SLP indicates that the processing has been completed. then the SCSM moves to the "Idle" state. then the SCSM remains in the same state (EventReportBCSM or ApplyChargingReport pending).7.1 CallInformationRequest procedure General description
This operation is used to request the SSF to record specific information about a single call and report it to the SCF using the CallInformationReport operation.8. 9. 9. callStopTime: This parameter indicates the time stamp when the connection is released.2 Error handling
If requested information is not available. When the SCF receives the CallInformationReport operation and the SL processing has been completed. In any state (except "Idle") the SCSM may receive CallInformationReport from the SSF. the SCSM remains in the same state until it receives the CallInformationReport operation. indicating the requested information type.3.7.3 9. Operation related error handling is not applicable. when the CallInformationReport is outstanding.7. The list may contain: callAttemptElapsedTime: This parameter indicates the duration between the end of INAP processing of operations initiating call setup ("Connect") and the received answer indication from the called party side. SCF postcondition: (1) The SLPI may be further executed.1 Parameters
requestedInformationTypeList: This parameter specifies a list of specific items of information which is requested. When the SCF receives the CallInformationReport operation and the SL processing has not been completed yet. but with "RequestedInformationValue" filled in with an appropriate default value.
-
-
. a CallInformationReport will be sent.8.Page 141 ETS 300 374-1: September 1994 9. due to class 4 operation. 9.

2 Error handling
In any other than the "Waiting for Instruction" state the CallInformationRequest operation will be handled as "out of context". 9.3.. The CallInformationRequest operation is accepted by the SSF FSM only in the state "Waiting for Instructions". The CallInformationRequest operation specifies the information items to be provided by the SSF. SSF postconditions: (1) Requested call information is retained by the SSF. before translation by the SCF). e.2.8.Page 142 ETS 300 374-1: September 1994 calledAddress This parameter indicates the incoming called party address that was received by the SSF (i. releaseCause: This parameter indicates the release cause for the call.8.2.e. the SCF sends the CallInformationRequest operation to the SSF to request the SSF to provide call related information.1 Invoking entity (SCF) Normal procedure
SCF preconditions: (1) A control relationship exists between the SCF and the SSF.3. Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.3 9. When the SLP requests call information. (2) A control relationship exists between SSF and SCF. "callStopTimeValue". The SSF allocates a record and stores the requested information if already available and prepares the recording of information items that will become available later. The SSF may receive the CallInformationRequest operation within an existing call associated (CA) dialogue only.
.g. (2) The SLPI has determined that a CallInformationRequest operation has to be sent by the SCF.
-
Any set of these values can be requested. 9.8.8. SCF postcondition: (1) The SLPI is expecting a CallInformationReport from SSF.2 9.8. (2) The SSF is waiting for further instructions.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. 9.8.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) Call origination attempt has been initiated. 9. The operation does not lead to any transition to another state.

2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.1.2. allRequests: This parameter indicates that all active requests for EventReportBCSM.9. or In case all requests are cancelled. 9. SCF postcondition: (1) The SLPI remains in the "Waiting for Response from SRF" state. EventNotificationCharging. 9. The operation to be deleted can be either a PlayAnnouncement operation or PromptAndCollectUserInformation operation. ApplyChargingReport and CallInformationReport should be cancelled. the SCSM FSM returns to "Idle" state.
a
The cancellation of an operation is indicated via a respective error indication.3.
.9. "Cancelled". the control relationship with the concerned FE (SSF) is ended. Invoking entity (SCF) Normal procedure
-
9. The Cancel operation can also be used to cancel all outstanding requests and enable the state machines (SSF/SRF) to go to "Idle".1 Responding entity (SRF) Normal procedure
SRF precondition: (1) A PA/P&C has been received and the SRF is in the "User Interaction" state. In this case the Cancel operation does not specify any specific operation to be cancelled.9 9.9.3 9.1 Parameters
invokeID: This parameter specifies which operation is to be cancelled.Page 143 ETS 300 374-1: September 1994 9.9. to the invoking entity of the cancelled PlayAnnouncement or PromptAndCollectUserInformation operation. (2) An SLPI in the "Waiting for response from SRF" state has determined that a previously requested operation is to be cancelled. or A SLPI has determined that it is no longer interested in any reports or notifications from the SSF and that the control relationship should be ended.9. 9.9. If no other relationships persist.9.2 9. SRF postcondition: (1) The execution of the PA/P&C has been aborted and the SRF remains in the "User Interaction" state.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. 9.3.9.1 Cancel procedure General description
The SCF uses this class 2 operation to request the SRF to cancel a correlated previous operation.2.1
SCF preconditions: (1) A control relationship exists between the SCF and the SSF/SRF.

9.1 Invoking entity (SCF) Normal procedure Parameters
SCF precondition: (1) An SLPI has determined that more information from the calling party is required to enable processing to proceed.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. SCF postcondition: (1) SLPI execution is suspended pending receipt of dialled digits.10.10.4.10. 9.10. This operation is invoked in the SCSM FSM state "Preparing SSF Instructions" if the SLP requires additional information to progress the call.9.2 Error handling
Sending of return error on cancel is not applicable in the cancel "allRequests" case.1 CollectInformation procedure General description
This is a class 2 operation which is used to request the SSF to perform the basic originating call processing actions which will collect destination information from a calling party (it is normally associated with a RequestReportBCSMEvent operation to arm DP2 and to specify the number of digits to be collected).2. unlike PromptAndCollectUserInformation.4. 9.2.2 9.1 None. This operation uses only the resources of the SSF/CCF to collect the information. 9. is further treated by SSF autonomously as a normal (non-IN) call.10 9.
.Page 144 ETS 300 374-1: September 1994 9.1 Responding entity (SSF) Normal procedure
SSF precondition: (1) The SSF FSM is in the states "Waiting for Instructions" or "Monitoring". or In case the SSF FSM was in state "Waiting for Instructions" it will remain in that state.1. The call. which uses the capabilities of the SRF.9. It causes a transition of the FSM to the state "Waiting for Notification or Report". 9. All resources allocated to the dialogue are released. A subsequent call-processing operation will move the SSF FSM state to "Idle". 9. SSF postcondition: (1) All active request for reports and notifications have been cancelled.4 9. if in active state. It follows that the use of this operation is only appropriate for a call which has not yet left the setup phase. (2) In case the SSF FSM was in state "Monitoring" it shall return to idle.10.

11. This may include prompting the party with in-band or out-band signals. an EventReportBCSM operation will be invoked.Page 145 ETS 300 374-1: September 1994 9. dialled digits) and existing call set-up information (e.g. SSF postconditions: (1) The SSF has executed a transition to the state "Monitoring". The "destinationRoutingAddress" may include the "correlationID" and "scfID" if used in the context of a hand-off procedure. The encoding of the parameter is defined in ETS 300 356-1 [7].10. The network operators has to decide about the actual mapping of this parameter on the used signalling system. To do so.3 9.10.10. DP2 will be encountered. The network operators has to decide about the actual mapping of this parameter on the used signalling system. The scfID is used in the context of a hand-off procedure and only if the SCF ID is not embedded in the "destinationRoutingAddress". The SSP has to perform the following actions: The SSF cancels TSSF.g.1 Parameters
destinationRoutingAddress: This parameter contains the called party number towards which the call is to be routed.11 9.2
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.3. The operation is only valid in the state "Waiting for Instruction" and after having received an operation RequestReportBCSMEvent for DP2. and the SSF FSM will return to the state "Waiting for Instruction".1 Connect procedure General description
This operation is used to request the SSF to perform the call processing actions to route a call to a specific destination. 9. correlationID: This parameter is used by the SCF to associate the AssistRequestInstructions operation from the assisting SSF with the InitialDP from the initiating SSF.1 Responding entity (SSF) Normal procedure
SSF precondition: (1) An InitialDP operation has been invoked. the SSF may use destination information from the calling party (e.1. The "correlationID" is used in the context of a hand-off procedure and only if the correlation ID is not embedded in the "destinationRoutingAddress". (2) The SSF performs the call processing actions to collect destination information from the calling party. 9.
-
-
. route index to a list of trunk groups) depending on the information provided by the SCF. (3) Basic Call Processing is resumed at PIC2.11. scfID: This parameter indicates the SCF identifier and enables the assisting SSF to identify which SCF the "destinationRoutingAddress" should be sent to. When the requisite number of digits (specified when DP2 was armed) has been received. but only if "correlationID" and "scfID" are not specified separately. Error handling
9.3.

a SCSM FSM transition to state "Idle" occurs. alertingPattern: This parameter indicates a specific pattern that is used to alert a subscriber (e. (2) An SLPI has determined that a Connect has to be sent by the SCF. When the Connect operation is
. The use of this parameter in the context of the Connect operation is to be specified by the network operator. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber. pay phone.g. The use of this parameter in the context of the Connect operation is to be specified by the network operator. The use of this parameter in the context of the Connect operation is to be specified by the network operator. Otherwise. SCF postcondition: (1) SLPI execution may continue. Invoking entity (SCF) Normal procedure
-
-
-
-
-
-
-
-
9. serviceInteractionIndicators: This parameter contain indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange. The use of this parameter in the context of the Connect operation is to be specified by the network operator. this operation is invoked by the SCF if the SL results in the request to the SSF to route a call to a specific destination. if event monitoring has been requested or any report (CallInformationReport and ApplyChargingReport) has been requested. etc.Page 146 ETS 300 374-1: September 1994 cutAndPaste: This parameter is used by the SCF to instruct the SSF to delete (cut) a specified number of leading digits that it has received from the calling party and to paste the remaining dialled digits on to the end of the digits supplied by the SCF in the "destinationRoutingAddress". If no event monitoring has been requested and no reports (CallInformationReport and ApplyChargingReport) have been requested in a previously sent operation. The use of this parameter is operator dependent. routeList: This parameter is used to select the outgoing trunk group used for routing the call. where only the SCF can verify the identity of the calling party. ordinary subscriber). such as redirecting counter. callingPartyNumber: This parameter is used to provide an alternative to the "callingPartyNumber" supplied by the network.2 9.). operator. callingPartysCategory: This parameter indicates the type of calling party (e.11. redirectionInformation: This parameter contains forwarding related information. tones.11. originalCalledPartyID: This parameter carries the dialled digits if the call has met call forwarding on route to the SSP or is forwarded by the SCP. A sequence of routes is provided to allow flexible routing for applications such as VPN without increasing the number of queries required for such applications. In the SCSM FSM state "Preparing SSF Instructions". It may be used for applications such as UPT. distinctive ringing.g..2. redirectingPartyID: This parameter indicates the directory number the call was redirected from. the SCSM FSM transitions to state "Waiting for Notification or Report".1
SCF preconditions: (1) A control relationship exists between the SCF and the SSF.

(3) The SSF waits for instructions. 9. the FSM goes to state "Idle" (e9).Page 147 ETS 300 374-1: September 1994 used in the context of a hand-off procedure. On receipt of this operation in the SSF FSM state "Waiting for Instructions". (3) In the O-BCSM. Connect completes when the INAP processing of the operation is complete and before the SSP starts the processing necessary to select a circuit. then the "destinationRoutingAddress" parameter delivered by the SCF is used for routing to complete the related call. when only address information is included in the Connect operation. call processing resumes at PIC 4. then the SSF deletes ("cut") from the dialled IN number the indicated number of digits and pastes the remaining dialled digits at the end of the "destinationRoutingAddress" parameter delivered by the SCF. the SCSM FSM transitions to state "Idle". the SSP performs the following actions: the SSF cancels TSSF. Statistic counter(s) are not affected. However. if "cutAndPaste" is present.2 Error handling
If reject or error messages are received.2.3 9.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) Call origination attempt has been initiated. then the SCSM informs the SLPI and remains in the state "Preparing SSF Instructions". when address information and routing information is included in the Connect operation. the SCF shall maintain sufficient information in order to correlate the subsequent AssistRequestInstructions operation (from the assisting SSF or SRF) to the existing SLPI. this value may be used for all subsequent SSF processing.11. Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.3.11. if the "callingPartyNumber" is supplied. In the case of hand-off. SSF postcondition: (1) The SSF performs the call processing actions to route the call to the specified destination. (2) Basic call processing has been suspended at a DP. 9. call processing resumes at PIC 3. The resulting directory number is used for routing to complete the related call.
-
-
No implicit activation or deactivation of DPs occurs. (2) In the O-BCSM. in this case. Otherwise.11. the FSM goes to state "Monitoring" (e11).
. Therefore in order to detect route select failure after a Connect it is necessary to explicitly arm the "Route Select Failure" EDP before sending the Connect (although they may be in the same message). if no EDPs have been armed and no CallInformationReport or ApplyChargingReport has been requested. this results in routing to an assisting SSP or IP. if "cutAndPaste" is not present.

12. (3) The call party is not connected to any other party.
.12.12. 9.2 9.12.2.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.12. (2) The SCSM FSM moves to the state "User Interaction".
-
-
serviceInteractionIndicators: This parameter contain indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange.12 9. 9.1
SCF preconditions: (1) A control relationship exists between the SCF and the SSF.Page 148 ETS 300 374-1: September 1994 9.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.11. (2) The SLPI has determined that additional information from the call party is needed. sub-state "Determine Mode". none: This parameter indicates that the call party is to be connected to a predefined SRF.1. After successful connection to the SRF.3.1 ConnectToResource procedure General description
This operation is used to connect a call from the SSF to a specialized resource. (5) The SLPI has determined that the SRF can be accessed from the SSF. the interaction with the caller can take place.1 Parameters
resourceAddress: This parameter identifies the physical location of the SRF. 9. SCF postconditions: (1) The SCSM sends out a PlayAnnouncement or PromptAndCollectUserInformation operation accompanying the ConnectToResource. iPRoutingAddress: This parameter indicates the routing address to set up a connection towards the SRF. Invoking entity (SCF) Normal procedure
9. The SSF relays all operations for the SRF and all responses from the SRF. (4) The SCSM FSM is in the state "Routing to Resource".2.

13. in case monitoring was required.3. in case no monitoring was required. the SCSM transitions to state "Waiting for Notification of Report". However. like in the case of armed EDPs or outstanding report requests. 9.
.2
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.13. SSF postconditions: (1) The call is switched to the SRF.3. or in the state "Idle".13. TSSF is set.13.13.12.3 9.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) Basic call processing has been suspended at a DP and a control relationship has been established. NOTE: The successful connection to the SRF causes a state transition in the SRF FSM from "Idle" to "Connected". (2) The SSF FSM is in the state "Waiting for Instructions".1 Continue procedure General description
This operation is used to request the SSF to proceed with call processing at the DP at which it previously suspended call processing to await SCF instructions. SCF postcondition: (1) SCSM is in the state "Waiting for Notification of Report".2. The SSF continues call processing without substituting new data from the SCF.2 9. 9. 9.2 Error handling
Operation related error handling is not applicable.1. The Continue operation is invoked by a SLPI.12.12. The SCSM is in state "Preparing SSF instructions". (2) A control relationship to the SRF is established. This causes a SCSM transition to state "Idle" if no subsequent monitoring is required. (3) The SSF FSM moves to the state "Waiting for End of User Interaction".2. if monitoring is required. Error handling
9.1 Invoking entity (SCF) Normal procedure Parameters
SCF precondition: (1) SCSM is in the state "Preparing SSF instructions". due to class 4 operation.13 9.Page 149 ETS 300 374-1: September 1994 9. 9.1 None.

or SSF FSM is in the state "Idle". 9.Page 150 ETS 300 374-1: September 1994 9.14 9. The SSF FSM is in state "Waiting for instructions". 9.1 Responding entity (SSF) Normal procedure
SSF preconditions (1) BCSM: Basic call processing has been suspended at any DP.
. (2) An assist. The SSME receives the Continue operation and relays it to the appropriate SSF FSM. because at least one EDP was armed. controlled by the "DisconnectFromIPForbidden" parameter in the PlayAnnouncement and PromptAndCollectUserInformation operations. due to class 4 operation. The SSF FSM transits to state "Monitoring" if at least one EDP is armed.3. (2) SSF FSM is in the state "Monitoring".1 None.2 Error handling
Operation related error handling is not applicable.14. To clear a connection to an assisting SSF: this operation is sent to the non-assisting SSF of a pair of SSFs involved in an assist procedure. Parameters
b)
9.1 DisconnectForwardConnection procedure General description
This operation is used in the following two cases: a) To clear a connection to a SRF: this operation is used to explicitly disconnect a connection to a resource (SRF) established previously with a ConnectToResource operation.3 9.13. (2) SSF FSM is in the state "Waiting for Instructions". The SSF FSM transitions to state "Idle" in case no EDPs are armed and no outstanding report requests are present.3.2 9. It is used for a forward disconnection from the SSF. It is used to disconnect the temporary connection between the initiating SSF and the assisting SSF.1
Invoking entity (SCF) Normal procedure
SCF preconditions: (1) A control relationship exists between the SCF and the SSF. because no EDPs were armed and neither the CallInformationReport nor the ApplyChargingReport was requested.1.14. (3) An SLPI has determined that a DisconnectForwardConnection operation has to be sent by the SCF. 9. and the assisting SSF and its associated SRF.13. or a CallInformationReport or ApplyChargingReport was requested. SSF postconditions (1) BCSM: Basic call processing continues. Basic call processing is resumed. or if there is at least one outstanding report request.2.14.13. SCF postcondition: (1) SLPI execution may continue. An alternative solution is the backward disconnect from the SRF.or a relay procedure is in progress.14.

this operation is invoked by the SCF when the SL determines that user interaction is finished and requests the SSF to disconnect the temporary connection to the assisting SSF or the SRF. A current order (PlayAnnouncement or PromptAndCollectUserInformation) is cancelled and any queued order is discarded. the SSP shall perform the following actions: the initiating SSF releases the connection to the assisting SSF or the relay SRF.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) Call origination attempt has been initiated. 9. the SSF resets TSSF. SSF postconditions: (1) The connection to the SRF or assisting SSF is released.
. It does not release the connection from the SSF back to the end user.2
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. The SCSM FSM then transitions to state "Preparing SSF Instructions". NOTE: The successful disconnection to the SRF causes a state transition in the SRF FSM to "Idle".14. (2) Basic call processing has been suspended at a DP. This operation is accepted in the SSF FSM states "Waiting for End of Temporary Connection" or "Waiting for End of User Interaction".
The DisconnectForwardConnection operation contains no parameters. The receipt of DisconnectForwardConnection results in disconnecting the assisting SSF or the PE containing the SRF from the concerned call.3. 9. Error handling
9.Page 151 ETS 300 374-1: September 1994 The DisconnectForwardConnection operation is used to instruct the SSF to disconnect the concerned forward connection to the assisting SSF or the PE containing the SRF.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.3 9. (3) The initiating SSF is in the state "Waiting for End of User Interaction" or "Waiting for End of Temporary Connection".14. sub-state "Waiting for Response from the SRF". In the SCSM FSM state "User Interaction".3.14. The DisconnectForwardConnection operation contains no parameter since there may be only one SRF connection to one call. (2) The SSF is waiting for instructions.2. the SSF FSM goes to state "Waiting for Instructions" (e8). On receipt of this operation in these states.14.

15. The SCSM FSM then transitions to state "Waiting for Assisting Requested Instructions".15 9.Page 152 ETS 300 374-1: September 1994 9. In the SCSM FSM state "Routing to Resource".1 Parameters
assistingSSPIPRoutingAddress: This parameter indicates the destination address of the SRF for assist procedure.1 EstablishTemporaryConnection procedure General description
This operation is used to create a connection between an initiating SSF and an assisting SSF as part of a service assist procedure.2. scfID: This parameter indicates the SCF identifier and enables the assisting SSF to identify which SCF the AssistRequestInstructions should be sent to.2.15. serviceInteractionIndicators: This parameter contain indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange. correlationID: This parameter is used by the SCF to associate the AssistRequestInstructions from the assisting SSF (or the SRF) with the InitialDP from the initiating SSF. for the case where the SRF exists in a separately addressable PE.1
SCF preconditions: (1) A control relationship exists between the SCF and the SSF. (2) The SL has determined that a connection is needed between the SSF and SRF or between the SSF and an assisting SSF. 9.
. The "assistingSSPIPRoutingAddress" may contain embedded within it.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. The network operators has to decide about the actual mapping of this parameter on the used signalling system. 9. but only if "correlationID" and "scfID" are not specified separately. this operation is invoked by the SCF when the SL determines that an assisting SSF or a Direct SCF-SRF relation is needed.1. The "scfID" is used only if the SCF ID is not embedded in the "assistingSSPIPRoutingAddress". a "correlationID" and "scfID". Invoking entity (SCF) Normal procedure
-
-
-
9.15. SCF postcondition: (1) The SCF is "Waiting for Assist Request Instructions". The "correlationID" is used only if the correlation ID is not embedded in the "assistingSSPIPRoutingAddress".2 9. (3) The call party is not connected to any other party.15. It can also be used to create a connection between a SSF and a SRF. The network operators has to decide about the actual mapping of this parameter on the used signalling system.15.

the SSF FSM goes to state "Waiting for End of Temporary Connection" (e7). On receipt of this operation in the SSF FSM state "Waiting for Instructions".1. legID: This parameter indicates the leg ID on which the charging event type applies.3. the SSP has to perform the following actions: reset the TSSF to TETC. busy.15. Error handling
9. As several charging events may occur during a connection configuration a possibility exists for the ENC operation to be invoked on multiple occasions. 9.1 EventNotificationCharging procedure General description
This operation is used by the SSF to report to the SCF the occurrence of a specific charging event type as requested by the SCF using the RequestNotificationChargingEvent operation.1 Parameters
eventTypeCharging: This parameter indicates the charging event type which has occurred. (3) The SSF waits for instructions.. which may be "chargePulses" or "chargeMessages". all received failure indications from the network on the ETC establishment shall be reported to the SCF as ETC error ETCFailed (e.15. Its content is network operator specific.3. (2) The SSF waits for end of temporary connection.3 9. Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. SSF postconditions: (1) The SSF performs the call processing actions to route the call to the assisting SSF.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) Call origination attempt has been initiated. 9. Its content is network operator specific. eventSpecificInformationCharging: This parameter contains charging related information specific to the event.16. (4) The SSF is not an assisting SSF.
-
-
. The operation supports the options to cope with the interactions concerning the charging (refer to Annex B. The operation timer for ETC shall be longer then the maximum allowed time for the signalling procedures to accept the connection.16.g. route the call to assisting SSF using "assistingSSPIPRoutingAddress".Page 153 ETS 300 374-1: September 1994 9.16 9.4). (2) Basic call processing has been suspended at a DP. Clause B. congestion).2
Until the connection setup has been accepted by the assisting SSF/SRF. For each connection configuration ENC may be used several times.15.

the SLPI prepares instructions for the SSF if necessary 9.16. NotifyAndContinue: Notify the SCF of the charging event using EventNotificationCharging.3 9. Invoking entity (SSF) Normal procedure
9.
. 9. call and existing charging processing will not be suspended in the SSF.1
SSF preconditions: (1) A control relationship exist between the SCF and the SSF. do not process the event.16.3. However. SCF postcondition: (1) No FSM state transition.16. if the "monitorMode" is "notifyAndContinue".2 Error handling
Operation related error handling is not applicable.Page 154 ETS 300 374-1: September 1994 monitorMode: This parameter indicates how the charging event is reported.16. due to class 4 operation. the event is reported as a request. If the corresponding monitor mode was set by the SLPI to Interrupted.2.2 Error handling
Operation related error handling is not applicable.2 9. This operation is invoked if a charging event has been detected that is requested by the SCF. (2) A charging event has been detected that is requested by the SCF. the event is reported as a notification. Irrespective of by what the charging event is caused the SSF performs one of the following actions on occurrence of the charging event (according to the corresponding monitorMode): Interrupted: Notify the SCF of the charging event using EventNotificationCharging operation.2. When the "monitorMode" is "interrupted". The detected charging event can be caused by: a) another SLPI or b) another exchange. The SSF FSM is in any state except "Idle".1 Responding entity (SCF) Normal procedure
SCF precondition: (1) A RequestNotificationChargingEvent has been sent at the request of a SLPI and SLPI is expecting an EventNotificationCharging from the SSF.3. The "monitorMode" "transparent" is not applicable for the EventNotificationCharging operation.16. due to class 4 operation.16. SSF postcondition: (1) No FSM state transition. but discard it. 9. and continue processing the event or signal. On receipt of this operation the SLPI which is expecting this notification can continue.

TMidCall and T-Disconnect.or T-Disconnect it will contain the "releaseCause". The "legID" parameter shall always be included for the events O-MidCall.e.1 Parameters
eventTypeBCSM: This parameter specifies the type of event that is reported. O-CalledPartyBusy. the following defaults are assumed: "legID" = 1 for the events CollectedInfo. For O. 9. If not included. eventSpecificInformationBCSM: This parameter indicates the call related information specific to the event. O-Abandon and T-Abandon.or T-Answer it will be empty.
-
-
-
miscCallInfo: This parameter indicates DP related information. legID: This parameter indicates the party in the call for which the event is reported.or T-CalledPartyBusy it will contain the "BusyCause". resulting from a RequestReportBCSMEvent with "monitorMode" = "notifyAndContinue". if available. resulting from a RequestReportBCSMEvent with "monitorMode" = "interrupted". For O. T-CalledPartyBusy. but each of these requested events is reported in a separate EventReportBCSM operation. T-NoAnswer and T-Answer. For AnalyzedInformation it will contain the "calledPartyNumber".17. SSF will use the option "receivingSideID" only. if available. i. messageType: This parameter indicates whether the message is a request.
.Page 155 ETS 300 374-1: September 1994 9. O-Disconnect. if available. For O.1. The monitoring of more than one event could be requested with a RequestReportBCSMEvent operation. receivingSideID: The following values for "legID" are assumed: "legID" = 1 indicates the party that was present at the moment of the InitialDP (in case of a midcall trigger.or T-NoAnswer it will be empty. O-Answer. the party not causing the trigger. For CollectedInfo it will contain the "calledPartyNumber".e. or in case of a midcall trigger. or a notification. "legID" = 2 indicates the party that was created with a Connect operation. For O.17. O-NoAnswer. For RouteSelectFailure it will contain the "FailureCause". "legID" = 2 for the events RouteSelectFailure.or T-MidCall it will be empty.17 9. or the party that was created with an InitiateCallAttempt operation. AnalyzedInformation. i. For O. the party causing the trigger).1 EventReportBCSM procedure General description
This operation is used to notify the SCF of a call related event previously requested by the SCF in an RequestReportBCSMEvent operation.

(2) The SCSM FSM is in the state "Preparing SSF Instructions".17. The considered EDP-Rs are: RouteSelectFailure. Operation related error handling is not applicable. For certain service features it is necessary that the same O-BCSM instance is reused.3 9. 9. no CallInformationReport or ApplyChargingReport are requested. In the case the respective EDP-R is met (see list above with O-Disconnect only for "legID" = 2). the SSF aborts the interaction with the SCF and instructs the CCF to route the call if necessary. SSF postconditions: (1) The SSF FSM stays in the state "Monitoring" if the message type was notification and there are still EDPs armed or a CallInformationReport or ApplyChargingReport requested. e. O-CalledPartyBusy.17.17.2. Examples are follow-on calls.2 9. the B-leg will be released and the SCF is informed via EventReportBCSM. 9.2. sub-state "Waiting for Notification or Request".2 Error handling
In case the message type is request.1 Invoking entity (SSF) Normal procedure
SSF preconditions: (1) The SSF FSM shall be in the state "Monitoring". O-Disconnect. to a final announcement.g.
If a EDP-R is met that causes the release of the related leg all EDPs related to that leg are disarmed and the event is reported via EventReportBCSM.17.g. the A-leg will be held. or the SSF FSM may be in state "Waiting for Instructions" if the Disconnect DP is armed and encountered. The decision to reuse the same O-BCSM instance can only be taken by the SCF after certain armed EDPRs are reported. or the SSF FSM may be in any state if the Abandon DP is armed and encountered. Call processing is interrupted. on expiration of TSSF before receiving any operation. due to class 4 operation.Page 156 ETS 300 374-1: September 1994 9.3.
. If the A-party disconnects the call is released whether or not a DP was armed.1 Responding entity (SCF) Normal procedure
SCF preconditions: (1) A control relationship exists between the SSF and the SCF.17. To allow the reuse of the same O-BCSM instance the BCSM has to store all call related signalling parameters (e. O-NoAnswer. (2) The BCSM proceeds to an EDP that is armed. "callingPartyNumber". (3) The SSF FSM moves to the state "Waiting for Instructions" if the message type was request. (2) The SSF FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed. "callingPartysCategory") until the BCSM instance is released.

The SCSM FSM is in state "Preparing SSF instruction" or is in state "Queuing FSM".1
SCF preconditions: (1) A control relationship exist between the SCF and the SSF. In addition FCI can also be applied at the end of the call or connection configuration (e. this operation may contain information pertaining to the initiation of queuing or the call queuing time duration for call logging purpose.
. FCI is used to include charge related information into the call record which was started at the beginning of the call. SCF postconditions: (1) No FSM state transition. charge level (scenario 2.4). (2) An SLPI has determined that a FurnishChargingInformation has to be sent by the SCF.1 Parameters
FCIBillingChargingCharacteristics: This parameter indicates billing and/or charging characteristics.18. 9.2. This operation is invoked by the SCF if a SLPI results in the request of creating a call record to the SSF or to include some billing or charging information into the default call record. FCI could be applied at the beginning of the call in order to request to start call record generation.3). Depending on the applied charging scenario the following information elements can be included (refer to Annex B): complete charging record (scenario 2. no CallInformationReport or ApplyChargingReport are requested. Its content is network operator specific.2 Error handling
Operation related error handling is not applicable.2).3. A possibility exists for the Furnish Charging Information (FCI) operation to be invoked on multiple occasions.3).Page 157 ETS 300 374-1: September 1994 SCF postconditions: (1) The SCSM FSM stays in the sub-state "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a CallInformationReport or ApplyChargingReport requested.4 (refer to Annex B) 9.3). Invoking entity (SCF) Normal procedure
9. This causes no SCSM FSM state transition. In this case.1. or the SCSM FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed.3 and 2.g. 9. The charging scenarios supported by this operation are: scenarios 2. correlationID (scenario 2. register a call record or to include some information in the default call record. (2) SLPI execution may continue. The SCF will prepare SSF or SRF instructions in accordance with the SLPI.2. due to class 4 operation.18.18. charge party (scenario 2. based on the dialogue ID. In the case of call queuing. charge items (scenario 2.18. (2) The event is reported to a SLPI.18 9. The registered call record is intended for off-line charging of the call.17. for follow-on calls).2 9..1 FurnishChargingInformation procedure General description
This operation is used to request the SSF to generate. or the SCSM FSM moves to the state "Preparing SSF Instructions" if the message type was request. 2. When additional FCIs are used it is recommended to arm an EDP-R (indicating the end of call or connection configuration) to be able to apply FCI before the termination of the call record generation.

begin time stamp or end time stamp. charge items). charge level. or the post processing function. e. registered by default at the SSF.18. or the SSF.3 9. "Waiting for Instructions". If case c) applies. "Waiting for Instructions" or SSF FSM State d. either the FurnishChargingInformation operation contains the corresponding parameters indicating that the charging level shall be determined in a succeeding exchange or the SSF detects during the determination of the charging level based on the provided parameters that the charging level shall be determined in a succeeding exchange.
. The SSF records charge related data. the accumulated pulses are included when the IN call record is generated or ignored.18. or a succeeding exchange.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. generates and registers a call record according the information (charge party. include the information received "correlationID" in the default call record which is generated and.18.3. account and record them. Additionally.
By means of a parameter at the FurnishChargingInformation operation the SCF can initiate the pulse metering function of the SSF. the SSF records further data if required. In both cases. the call duration. On receipt of this operation the SSF performs actions to create the call record according the off-line charging scenario which is applicable using the information elements included in the operation: registers the complete call record included in the operation. In that case the SSF shall generate meter pulses according to the applicable charging level. The charging level can be determined by a) b) c) d) the SCF. 9. the charging level is included in the FurnishChargingInformation operation. "Waiting for End of Temporary Connection" or Assisting/hand-off SSF FSM State b. The SSF can either account received pulses or convert any charging messages received from the B-side to pulses. the SSF shall determine the charging level based on the corresponding parameters contained in the operation.
If case a) applies.g. SSF postcondition: (1) No FSM state transition. "Waiting for End of User Interaction" or SSF FSM State e. If case b) applies.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) SSF FSM State c.2.Page 158 ETS 300 374-1: September 1994 9.

1 InitialDP procedure General description
This operation is sent by the SSF after detection of a TDP-R in the BCSM.19.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.g.Page 159 ETS 300 374-1: September 1994 9.19 9. origin dependent routing when the calling party is a mobile subscriber). operator.18. e. The network access capabilities do not indicate the terminal type. but the end user terminal behind the ISPBX may be ISDN or non-ISDN. preceding network connection and the preferred signalling capabilities of the succeeding network connection. originalCalledPartyID: This parameter carries the dialled digits if the call has met call forwarding on the route to the SSP. ordinary subscriber). an Integrated Services Private Branch eXchange (ISPBX) will have an ISDN type of access. 9. locationNumber: This parameter is used to convey the geographical area address for mobility services. to request the SCF for instructions to complete the call.
-
-
-
-
-
-
-
. For example.g. It is used to address the correct application/SLP within the SCF (not for SCP addressing).19. callingPartyNumber: This parameter carries the calling party number to identify the calling party or the origin of the call.. pay phone. It also indicates the signalling capabilities of the network access. The encoding of the parameter is defined in ETS 300 356-1 [7].g.. the Called party number of ISUP (see ETS 300 356-1 [7]).1.3. calledPartyNumber: This parameter contains the number used to identify the called party in the forward direction. forwardCallIndicators: This parameter indicates if the call shall be treated as a national or international call. 9. It is used when "callingPartyNumber" does not contain any information about the geographical location of the calling party (e. bearerCapability: This parameter indicates the type of the bearer capability connection to the user: bearerCap: This parameter contains the value of the DSS1 Bearer Capability parameter in case the SSF is at local exchange level or the value of the ISUP User Service Information parameter in case the SSF is at transit exchange level. The parameter "bearerCapability" shall only be included in the InitialDP operation in case the DSS1 Bearer Capability parameter or the ISUP User Service Information parameter is available at the SSP.1 Parameters
serviceKey: This parameter identifies for the SCF unambiguously the requested IN service. callingPartysCategory: Indicates the type of calling party (e.

SSF postcondition: (1) A control relationship has been established and the SSF waits for instructions from the SCF.e. additionalCallingPartyNumber: The calling party number provided by the access signalling system of the calling user. The address of the SCF the InitialDP operation has to be sent to is determined on the base of trigger related data. If these conditions are met. DSS1 (see ETS 300 403-1 [8]) is used.19.7 overload are not in effect for the call. cGEncountered: This parameter indicates that the related call has passed call gapping. Invoking entity (SSF) Normal procedure
-
-
-
-
-
-
-
-
9. redirectionInformation: It contains forwarding related information. eventTypeBCSM: This parameter indicates the armed BCSM DP event. resulting in the InitialDP operation. (2) An event has been detected at a DP. iPSSPCapabilities: Indicates which SRF resource are supported within the SSP an attached and available. iPAvailable: Indicates whether or not an IP is attached and available (i.19. NOTE: This is for further study.2 9. which will be used to determine the ISDN-teleservice of a connected ISDN terminal. serviceInteractionIndicators: This parameter contain indicators sent from the SSP to the SCP for control of the network based services at the originating exchange and the destination exchange. redirectingPartyID: This parameter indicates the directory number the call was redirected from. Following a trigger detection related to an armed TDP-R in the BCSM caused by a call origination attempt.. and the call is not to be filtered. (3) Call gapping and Signalling System No. the SSF checks if call gapping.2. such as redirecting counter. not exhausted) at the SSP.
. then the InitialDP operation is invoked by the SSF. For encoding.7 overload or service filtering are not in effect for the related call segment. Signalling System No.1
SSF preconditions: (1) Call origination attempt has been initiated.Page 160 ETS 300 374-1: September 1994 If two values for bearer capability are available at the SSF or if User Service Information and User Service Information Prime are available at the SSF the "bearerCap" shall contain the value of the preferred bearer capability respectively the value of the User Service Information Prime parameter. The SSF provide as many parameters as available. highlayerCompatibility: This parameter indicates the type of the high layer compatibility.

2 Error handling
If the destination SCF is not accessible then the SSF FSM instructs the CCF to route the call if necessary e. the SSF aborts the interaction with the SCF and instructs the CCF to route the call if necessary e. SCF postcondition: (1) An SLPI has been invoked.3.g.19. some parameters shall be available (such as "callingPartyNumber" or "callingPartysCategory"). itself. it is possible to request the "callingPartysCategory" from a preceding exchange). the SCF may influence the basic call processing in accordance with the SL invoked.
. then the SSF aborts the control relationship after the first answer message from the SCF has been received. the SSF returns call control to the CCF. to a final announcement. By means of this control relationship. i. a control relationship to the related SSF is created. A SLPI is invoked for processing the InitialDP operation based on the "serviceKey" parameter. The SSF application timer T SSF is set when the SSF sends InitialDP for requesting instructions from the SCF. On receipt of InitialDP operation the SCSM moves from "Idle" to the state "Preparing SSF Instructions".3. This shall be handled appropriately by the SSF in its trigger table (to know that such parameter are necessary for some triggering conditions) and in conducting the necessary action to get these parameters if they are not available (for instance. 9.19.
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. if MF signalling is used. Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.. The actions to be performed in the SLPI depend on the parameters conveyed via this operation and the SLPI. The maintenance function is informed and no SLPI is invoked.1 Responding entity (SCF) Normal procedure
SCF precondition: None. Otherwise. The following error cases are indicated to the SSF: MissingCustomerRecord: The SCF has not found the appropriate SL corresponding to the provided service key or the appropriate service subscriber related SL. A control relationship is established to the SCF. It is used to prevent from excessive call suspension time.. If the calling party abandons after the sending of InitialDP.2 Error handling
If the InitialDP operation is rejected then the SCSM remains in "Idle". 9.2.g.19. to a final announcement. 9.Page 161 ETS 300 374-1: September 1994 In some service-specific cases. On expiration of TSSF before receiving any operation. the requested IN service.19.3 9.e.

the value of TSCF shall be equal or less then the network no answer timer.1. i. The SCF shall start a response Timer TSCF when the InitiateCallAttempt operation is sent. distinctive ringing. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber. The InitiateCallAttempt operation creates a BCSM instance in the SSF but the SSF suspends the call processing of this BCSM. no control relationship exists between SCF and SSF. SCF postconditions: (1) A control relationship is established between the SCF and SSF. tones. alertingPattern: This parameter indicates a specific pattern that is used to alert a subscriber (e. The encoding of the parameter is defined in ETS 300 356-1 [7]. DP6 and DP7.
. (2) An SLPI has determined that an InitiateCallAttempt operation should be sent to the SCF.g.). etc.e.20.Page 162 ETS 300 374-1: September 1994 9. If this parameter is not sent by the SCF. the SLPI shall monitor for the BCSM event(s) which report the result of the created call setup.20.1
SCF preconditions: (1) An SLPI has been invoked. (3) The SCSM FSM is in state "Idle". This includes DP3 or DP4. (2) The SCSM FSM is in state "Preparing SSF Instructions". DP5.2. The SCSM FSM shall proceed as specified at the procedure for the Continue operation. serviceInteractionIndicators: This parameter contain indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange.20.20 9. 9. the SSF may supply a network dependent default value. in order to have the SCF treat this call appropriately when either of these events is encountered.1 InitiateCallAttempt procedure General description
This operation is used to request the SSF to create a new call to one call party using the address information provided by the SCF. callingPartyNumber This parameter identifies which number shall be regarded as the calling party for the created call. An EDP-R shall be armed on answer and all the call failure events. The SCSM FSM moves to state "Preparing SSF Instructions" when the SL invokes this operation. In order to enable the establishment of a control relationship between the SCF and SSF and to allow the SCF to control the created call appropriately. The SLPI shall send a Continue operation to request the SSF to route the call to the specified destination.20. (3) SLPI execution continues. Any other non-call-processing instructions may be sent as well. The above described procedure shall be part of the establishment of the control relationship. The response Timer shall supervise the confirmation of the dialogue from SSF.1 Parameters
destinationRoutingAddress: This parameter contains the called party number towards which the call is to be routed. Invoking entity (SCF) Normal procedure
-
-
-
9. operations up to and including the Continue operation shall be sent together in the same message to the SSF.2 9.

9. normally received from or associated to the calling party.20. a tone or display information to be sent to the end user by the SRF. the SSF creates a new originating BCSM and suspends the call processing of this BCSM at DP1.3. (2) The SSF FSM has moved from "Idle" state to state "Waiting for Instructions".Page 163 ETS 300 374-1: September 1994 9.20.20. The attributes of text may consist of items such as language. 9. messageID: This parameter indicates the message(s) to be sent. Upon reception of InitiateCallAttempt.2 Error handling
Generic error handling for the operation related errors is described in Clause 8. 9. 9. the TCAP services which are used for reporting operation errors are described in Clause 10.3.21 9. this can be one of the following: elementaryMessageID: This parameter indicates a single announcement. SSF postconditions: (1) A new originating BCSM has been created.3 9. the TCAP services which are used for reporting operation errors are described in Clause 10.1.2 Error handling
On expiration of TSCF the SCF shall abort the dialogue.2. The SCSM FSM moves to the Idle state. call processing is suspended at DP1.1 Responding entity (SSF) Normal procedure
SSF precondition: None. required for the call setup shall have a network dependent default value. report the abort to the maintenance functions and inform the SLPI on the failure of dialogue establishment. Generic error handling for the operation related errors is described in Clause 8.21. these properties may be dependent on the received calling party number.1 PlayAnnouncement procedure General description
This operation is used for inband interaction with an analogue user or for interaction with an ISDN user.
-
. text: This parameter indicates a text to be sent. inbandInfo: This parameter specifies the inband information to be sent. If a calling party number is supplied by the SCF.20. All subsequent operations are treated according to their normal procedures.21.1 Parameters
informationToSend: This parameter indicates an announcement. The properties and capabilities. The text shall be transformed to inband information (speech) by the SRF.

As the current signalling systems (DSS1/ISUP) do not provide an indication whether or not information can be displayed by the user's terminal. in sequence with the display information. interval: This parameter indicates the time interval in seconds between repetitions.Page 164 ETS 300 374-1: September 1994 elementaryMessageIDs: This parameter specifies a sequence of announcements.e. Since the execution of the display information by the SRF should take a limited amount of time. ZERO indicates endless repetition. The first contains the display information.
-
. toneID: This parameter indicates the tone to be sent.
-
-
-
tone: This parameter specifies a tone to be sent to the end-user.
-
-
numberOfRepetitions: This parameter indicates the maximum number of times the message shall be sent to the end-user. the inband information will be immediately sent by the SRF to the user. i. ZERO indicates infinite duration.
NOTE:
-
disconnectFromIPForbidden: This parameter indicates whether or not the SRF should be disconnected from the user when all information has been sent. This parameter can only be used when the number of repetitions is greater than one.
-
-
displayInformation: This parameter indicates a text string to be sent to the end-user. This information can not be received by a PSTN end-user. the time between the end of the announcement and the start of the next repetition. in case of user interaction with an ISDN user two consecutive PlayAnnouncement operations are sent. the second contains the inband information to be sent to the user. duration: This parameter indicates the time duration in seconds of the tone to be sent. requestAnnouncementComplete: This parameter indicates whether or not a SpecializedResourceReport shall be sent to the SCF when all information has been sent. duration: This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. variableMessage: This specifies an announcement with one or more variable parts.

1 Invoking entity (SCF) Normal procedure
SCF preconditions: (1) The SLPI detects that information should be sent to the user. or if "duration" and "numberOfRepetitions" is specified. (4) If all information has been sent and "disconnectFromIPForbidden" was set FALSE. the SRSM disconnects the SRF from the user.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. 9. sub-state "Waiting for response from the SRF".2.3 9. Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.21. (2) If "RequestAnnouncementComplete" was set FALSE and more information needs to be sent ("DisconnectFromIPForbidden" was set to TRUE).2 9. (3) The SCSM FSM is in the state "User interaction".21. or in the state "User Interaction" if the SRF received previously an operation from the SCF. the SCSM will stay in sub-state "Waiting for Response from the SRF" and wait for the SpecializedResourceReport. or remains in the same state. the SRSM sends a SpecializedResourceReport operation to the SCF. (2) A connection between the user and a SRF has been established. Error handling
9. The announcement send to the end-user is ended in the following conditions: if neither "duration" or "numberOfRepetitions" is specified.2
If a Cancel operation is received before or during the processing of the operation then the operation is immediately cancelled and the error "Cancelled" is reported to the invoking entity. then the network specific announcement ending conditions shall apply. or if "duration" is specified.21. SCF postconditions: (1) If "RequestAnnouncementComplete" was set TRUE. when the duration has expired.21. 9.21.21. (2) The SRSM FSM moves to the state "User Interaction". SRF postconditions: (1) The SRF sends the information to the user as indicated by "informationToSend".1 Responding entity (SRF) Normal procedure
SRF precondition: (1) The SRSM FSM is in the state "Connected".
.2.3.Page 165 ETS 300 374-1: September 1994 9. (3) If all information has been sent and "RequestAnnouncementComplete" was set TRUE. The announcement is repeated until this condition is met.3. the SCSM will stay in sub-state "Waiting for Response from the SRF". (3) If "RequestAnnouncementComplete" was set FALSE and no more information needs to be sent ("DisconnectFromIPForbidden" was set to FALSE). when one of both conditions is satisfied (whatever comes first). the SCSM will move to the state "Preparing SSF Instructions". or if "numberOfRepetitions" is specified. when all repetitions have been sent.

The digits that are received by the SRF before this start digit is received. the default value is defined to be 1. This parameter can be one or two digits. 9.1 Parameters
collectedInfo: collectedDigits: minimumNbOfDigits: If this parameter is missing. cancelDigit: If this parameter is present.
-
. The following applies: "maximumNbOfDigits" ≥ "minimumNbOfDigits". the start digit indicates the start of the valid digits to be collected. the end of input is indicated: when the inter-digit timer expires.22.22. thus e. The "minimumNbOfDigits" specifies the minimum number of valid digits to be collected.1 PromptAndCollectUserInformation procedure General description
This operation is used to interact with a call party in order to collect information. the input is specified as being erroneous. endOfReplyDigit: This parameter indicates the digit used to signal the end of input. the collected digits are send from SRF to the SCF. maximumNbOfDigits: This parameter should always be present and specifies the maximum number of valid digits to be collected. If this parameter is not present. In the case the number of valid digits received is less than the "minimumNbOfDigits" when the inter-digit timer expires or when the end of reply digit is received.22 9.
-
-
equals
the
equals
the
When the end of input is attained. or when the end of reply digit is received. or when the number of valid digits received "maximumNbOfDigits". All digits already received by the SRF are discarded and the same PromptAndCollectUserInformation procedure is performed again. or when the number of valid digits received "maximumNbOfDigits".g. In case the "maximumNbOfDigits" > "minimumNbOfDigits" the following applies: If "endOfReplyDigit" is not present. If "endOfReplyDigit" is present. In case the "maximumNbOfDigits" = "minimumNbOfDigits". the "endOfReplyDigit" (could be present but) has no further meaning. If this parameter is not present. This parameter can be one or two digits. are discarded and are not considered to be valid. the cancel digit can be entered by the user to request a possible retry.Page 166 ETS 300 374-1: September 1994 9. all received digits are considered to be valid. the end of input is indicated: when the inter-digit timer expires. This parameter can be one or two digits.1. startDigit: If this parameter is present. the user is not able to request a possible retry. the same announcement to request user information is given to the user and information is collected.

Page 167 ETS 300 374-1: September 1994 firstDigitTimeOut: If this parameter is present. the corresponding first-digit timer is stopped. all valid or invalid digits are entered by DTMF. errorTreatment: This optional parameter defines what specific action should be taken by the SRF in the event of error conditions occurring. the first digit should be received by the SRF before the first-digit timer expiration.
-
. In case the first digit is not received before first-digit timer expiration. If the "interDigitTimeOut" is not present. If "startDigit" is present. then the SRF uses a default value for the inter-digit time. "endOfReplyDigit". If this parameter is present and explicitly set to TRUE. the input is regarded to be successful. and less than or equal to the "maximumNbOfDigits". However. should be received by the SRF before the inter-digit timer expires. "maximumNbOfDigits". In case a subsequent valid or invalid digit is not received before the inter-digit timer expires and the number of received valid digits is less than the "minimumNbOfDigits". the first-digit timer is stopped after the start digit is received. etc. if the announcement has not been interrupted. where the default value is specified being TRUE. If the "voiceInformation" parameter is FALSE. The received digits during the announcement are discarded and considered to be invalid. voiceInformation: This parameter is optional. All other specified parameters ("minimumNbOfDigits". If the announcement is interrupted. the input is regarded to be erroneous. In case a subsequent valid or invalid digit is not received before the inter-digit timer expires and the number of received valid digits is greater than the "minimumNbOfDigits". interDigitTimeOut: If this parameter is present any subsequent valid or invalid digit. the announcement is interrupted after the first valid or invalid digit is received by the SRF. If this parameter is TRUE. where the default value is specified being FALSE. then the SRF uses a default value for the first-digit timer in which the first valid or invalid input digit is received. the announcement will not be interrupted after the first digit is received by the SRF. a possible start-digit timer is started after the announcement has been finished. After receipt of the first valid or invalid input digit. If this parameter is not present.) do not apply before the announcement has been finished. The default value is stdErrorAndInfo. If this parameter is present and explicitly set to FALSE. the input is regarded to be unsuccessful. a possible start-digit timer will not apply anymore. interruptableAnnInd: This parameter is optional. A possible end of reply digit will also have to be provided by speech. As result the inter-digit timer is reset and restarted. calling user is required to provide all valid or invalid information by speech. The SRF will perform voice recognition and translation of the provided information into digits. The possible start-digit timer is started after the announcement has been finished.

the time between the end of the announcement and the start of the next repetition. the valid input digits received by the SRF will be announced back to the calling user immediately after the end of input is received. no voice back information is given by the SRF. the SRF shall not initiate disconnection.
-
-
-
-
-
numberOfRepetitions: This parameter indicates the maximum number of times the message shall be sent to the end-user. informationToSend: This parameter indicates an announcement. i. A possible end of reply digit is not voiced back.e. This parameter can only be used when the number of repetitions is greater than one. elementaryMessageIDs: This parameter specifies a sequence of announcements.
-
-
-
tone: This parameter specifies a tone to be sent to the end-user. where the default value is specified being FALSE. The attributes of text may consist of items such as language. text: This parameter indicates a text to be sent. messageID: This parameter indicates the message(s) to be sent. If this parameter is present and explicitly set to TRUE. this can be one of the following: elementaryMessageID: This parameter indicates a single announcement. inbandInfo: This parameter specifies the inband information to be sent. The invalid input digits will not be announced back to the calling user. interval: This parameter indicates the time interval in seconds between repetitions. duration: This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. a tone or display information to be sent to the end user by the SRF. toneID: This parameter indicates the tone to be sent.
.Page 168 ETS 300 374-1: September 1994 voiceBack: This parameter is optional. variableMessage: This parameter specifies an announcement with one or more variable parts. If the parameter is not present or set to TRUE. The text shall be transformed to inband information (speech) by the SRF. If the "voiceBack" parameter is FALSE. ZERO indicates endless repetition. disconnectFromIPForbidden: This parameter indicates whether the SRF should initiate disconnection to the SSF/CCF after the interaction has been completed.

3. 9.Page 169 ETS 300 374-1: September 1994 duration: This parameter indicates the time duration in seconds of the tone to be sent.2 Error handling
Generic error handling for the operation related errors is described in Clause 8. sub-state "Waiting for Response from the SRF".1 Responding entity (SRF) Normal procedure
SRF precondition: (1) The SRSM FSM is in the state "Connected". Invoking entity (SCF) Normal procedure
9. SCF postconditions: (1) The collected information is received from the SRF as response to the PromptAndCollectUserInformation operation.
-
displayInformation: This parameter indicates a text string to be sent to the end-user.1
SCF preconditions: (1) The SLPI detects that information should be collected from the end-user.22.
NOTE:
-
digitsResponse: This parameter contains the information collected from the end-user. ZERO indicates infinite duration. the inband information will be immediately sent by the SRF to the user. in sequence with the displayed information. the "displayInformation" parameter is not used in the "PromptAndCollectUserInformation" operation. (2) A connection between the end-user and a SRF has been established.3 9. As the current signalling systems (DSS1/ISUP) do not provide an indication whether or not information can be displayed by the user's terminal. or in state "User Interaction" if the SRF received previously an operation from the SCF.
.22.2.22.2 9. the TCAP services which are used for reporting operation errors are described in Clause 10. the SCSM FSM will move to the state "Preparing SSF Instructions". This information can not be received by a PSTN end-user.22. The SLPI may continue execution before the response is received from the PromptAndCollectUserInformation operation. The "disconnectFromIPForbidden" parameter may only be set to FALSE if the PromptAndCollectUserInformation operation is the last operation sent to the SRF. (2) If the "disconnectFromIPForbidden" was set to FALSE. in case of user interaction with an ISDN user. more then one operation may be sent to the SRF before the response is received. (3) The SCSM FSM is in state "User Interaction". Since the execution of the displayed information by the SRF should take a limited amount of time.22. Instead a "PlayAnnouncement" operation containing the "displayInformation" parameter followed by a "PromptAndCollectUserInformation" operation containing inband information are sent to the user. (3) Otherwise the SCSM FSM remains in the same state. 9.2.

22.e. no interruption can occur. or if "duration" and "numberOfRepetitions" is specified. except in the case of hand-off procedure. 9. (4) Otherwise the SRSM FSM moves to the state "User Interaction".23 9. The announcement is repeated until this condition is met. (2) The collected information from the end-user is sent to the SCF as return result of the PromptAndCollectUserInformation. Generic error handling for the operation related errors is described in Clause 8.Page 170 ETS 300 374-1: September 1994 SRF postconditions: (1) The SRF has sent the information to the end-user as indicated by "informationToSend". the TCAP services which are used for reporting operation errors are described in Clause 10. the SRF initiates a bearer channel disconnect to the SSF and the SRSM FSM moves to the state "Idle". The default value "stdErrorAndInfo" means that the error shall be reported to SCF as specified in Clause 8. 9.23. The value "help" indicates that no error shall be reported to SCF but assistance shall be given to the end-user in form of a network dependent default announcement (which may be dependent on the context.3.1 Parameters
Cause A number giving an indication to the SSF about the reason of releasing this specific call. (3) If the "disconnectFromIPForbidden" was set to FALSE.1. The announcement send to the end-user is ended in the following conditions: if neither "duration" or "numberOfRepetitions" is specified. or if "duration" is specified. or remains in the same state. The last two procedures shall only be done once per PromptAndCollectUserInformation operation. 9. when one of both conditions is satisfied (whatever comes first). In this case the announcement is ended immediately. when the duration has expired. for "displayInformation" the end conditions are met upon sending.1 ReleaseCall procedure General description
This operation is used to tear down by the SCF an existing call at any phase of the call for all parties involved in the call. This may be used by SSF for generating specific tones to the different parties in the call or to fill in the "cause" in the release message. The above procedures apply only to inband information and tones send to the end-user. i. i. or if "numberOfRepetitions" is specified. The parameter "errorTreatment" specifies how the SRF shall treat the error "ImproperCallerResponse".
. This operation may not be sent to an assisting SSF. when all repetitions have been sent.
The above conditions are overruled if the parameter "interruptableAnnInd" is not set to FALSE and the end-user has responded with a digit during the sending of the announcement.23.2 Error handling
If a Cancel operation is received before or during the processing of the operation then the operation is immediately cancelled and the error "Cancelled" is reported to the invoking entity. The value "repeatPrompt" indicates that no error shall be reported to the SCF but the prompt shall be repeated to the end-user.e. then the network specific announcement ending conditions shall apply. the sent message).

4).3. The operation supports the options to cope with the interactions concerning the charging (refer to Annex B.24 9.3.23.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) State C. due to class 4 operation.2.1 Invoking entity (SCF) Normal procedure
SCF precondition: (1) State 2. SSF postcondition: (1) "Idle".1. or State 2.23. 9. "Idle".23. "Waiting for Notification or Request" if a CallInformationReport still has to be received from the SSF.2 Error handling
Operation related error handling is not applicable. Its content is network operator specific.2. "notify" and "continue" or "transparent".23. Monitor may be "interrupted".1 RequestNotificationChargingEvent procedure General description
This operation is used to instruct the SSF how to manage the charging events which are received from other FEs not under the control of the SL instance.3. 9. or State F.23. monitorMode: This sub-parameter indicates the monitorMode applicable for the corresponding "eventTypeCharging" sub-parameter.24.2 9. 9.
-
. 9.23. As several connection configurations may be established during a call a possibility exists for the RNC operation to be invoked on multiple occasions. All resources (e.3 9. "Waiting for Instructions". 9. queue) related to the call are released by the SCF. if no CallInformationReport has to be received from the SSF. Clause B. after sending any outstanding CallInformationReport. which may be "chargePulses" or "chargeMessages". due to class 4 operation. All connections and resources related to the call are released. Possible armed EDPs are ignored.Page 171 ETS 300 374-1: September 1994 9. For each element in the list the following information elements are included: eventTypeCharging: This sub-parameter indicates the charging event type.1.1 Parameters
Sequence of ChargingEvent: This parameter contains a list of the charging events and the corresponding monitor types and corresponding legs. SCF postconditions: (1) State 1. For each connection configuration a RNC may be used several times.24. "Preparing SSF instructions".g. "Monitoring". state a.2 Error handling
Operation related error handling is not applicable.

2.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.24. (2) SLPI execution may continue. This causes no SCSM FSM state transition. SCF postconditions: (1) No FSM state transition.24.24.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) SSF FSM State c: "Waiting for Instructions".1
SCF preconditions: (1) A control relationship exist between the SCF and the SSF.24. Transparent: do not notify the SCF of the event. This is stop the monitoring of a previously requested charging event. and continue processing the event or signal without waiting for SCF instructions (handled like EDP-N for BCSM events).
. SSF postcondition: (1) No FSM state transition. 9.24.Page 172 ETS 300 374-1: September 1994 legID: This sub-parameter indicates the leg ID of the corresponding event type charging subparameter. The SCSM FSM is in state "Preparing SSF Instruction" or is in state "Queuing FSM". The requested charging event can be caused by: a) another SLPI or b) another exchange. Invoking entity (SCF) Normal procedure
9. do not process the event or propagate the signal. call and existing charging processing will not be suspended in the SSF.2. This operation is invoked by the SCF if a SLPI results in the instruction of SSF how to cope with the interactions concerning the charging. (2) An SLPI has determined that a RequestNotificationChargingEvent has to be sent by the SCF. or SSF FSM State f: "Monitoring". or SSF FSM State e: "Waiting for End of Temporary Connection". Irrespective of by what the charging event is caused the SSF performs one of the following actions on occurrence of the charging event (according the corresponding monitorMode): Interrupted: notify the SCF of the charging event using EventNotificationCharging operation. On receipt of this operation the SSF performs actions to cope with the interactions concerning the charging according the information elements included in the operation. NotifyAndContinue: notify the SCF of the charging event using EventNotificationCharging. However.3. or SSF FSM State d: "Waiting for End of User Interaction".3 9. 9. or Assisting/hand-off SSF FSM State b: "Waiting for Instructions".2 9.

9. O-Abandon and TAbandon. 9. T-NoAnswer and T-Answer.
. sendingSideID: The following values for "legID" are assumed: "legID" = 1 indicates the party that was present at the moment of the InitialDP (in case of a mid call trigger. SCF will use the option "sendingSideID" only. the event shall be reported as a request. or in case of a mid call trigger. eventTypeBCSM: This parameter specifies the type of event of which a report is requested. if the "monitorMode" is "notifyAndContinue". O-Disconnect. "legID" = 2 for the events RouteSelectFailure. O-CalledPartyBusy.1 Parameters
bcsmEvents: This parameter specifies the event or events of which a report is requested. The "legID" parameter shall always be included for the events O-MidCall. the party not causing the trigger.. O-Answer. O-NoAnswer. When the "monitorMode" is "interrupted".25.25 9. the party causing the trigger). T-MidCall and T-Disconnect. the event shall not be reported. AnalyzedInformation.
-
-
-
dPSpecificCriteria: This parameter indicates information specific to the EDP to be armed. "legID" = 2 indicates the party that was created with a "Connect" operation. or the party that was created with an InitiateCallAttempt operation. monitorMode: This parameter indicates how the event should be reported. legID: This parameter indicates the party in the call for which the event shall be reported.25. the event shall be reported as a notification.g.3. the following defaults are assumed: "legID" = 1 for the events CollectedInfo. then send a notification back to the SCF when the event is detected. In the case that multiple RequestNotificationChargingEvent operations are received for the same connection configuration with the same "eventTypeCharging" and "legID". only the last received "monitorMode" will apply.Page 173 ETS 300 374-1: September 1994 Requested charging events are monitored until ended by a transparent monitor mode (or in the case of charging events) until the end of the connection configuration. 9. if the "monitorMode" is "transparent". If not included.1 RequestReportBCSMEvent procedure General description
This operation is used to request the SSF to monitor for a call-related event (e. T-CalledPartyBusy. Values origAttemptAuthorized and termAttemptAuthorized are not valid for the RequestReportBCSMEvent operation.24.1.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. BCSM events such as busy or no answer).

(3) The SSF FSM remains in the same state.
-
9.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.25. If the user does not answer the call within the allotted time. 9.26. SCF postconditions: (1) The SCSM FSM remains in the same state. SSF reports the event to the SCF. the SSF FSM moves to the state "Idle". If the indicated number of digits is collected.25.25.1
Invoking entity (SCF) Normal procedure
SCF preconditions: (1) A control relationship exists between the SCF and the SSF. the SSF reports the event to the SCF. If no other relationship persist. (2) Previously requested events are monitored until ended by a transparent monitor mode.2 9. 9.3. applicationTimer: This parameter indicates the application timer for the NoAnswer event.25. This timer shall be shorter than the network no-answer timer.
. until the end of the call.1 ResetTimer procedure General description
This class 2 operation is used by the SCF to refresh the TSSF application timer. the controlrelationship with the concerned SSF is ended.26 9. (3) If all EDPs have been disarmed and no CallInformationReport or ApplyChargingReport is pending.3. until the EDPs are detected or until the corresponding leg is released.3 9. (3) The SCSM FSM is in the appropriate state to send RequestReportBCSMEvent.25.Page 174 ETS 300 374-1: September 1994 numberOfDigits: This parameter indicates the number of digits to be collected by the SSF for the CollectedInfo event. (4) If all EDPs have been disarmed and no CallInformationReport or ApplyChargingReport has been requested. 9. 9.25.2.2. in order to avoid the T SSF time-out at the SSF. (2) SLPI execution continues.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. (2) The SLPI has decided that a request for an event report BCSM is needed. SSF postconditions: (1) The requested EDPs have been armed as indicated.1 Responding entity (SSF) Normal procedure
SSF precondition: (1) The SSF FSM is in either the state "Waiting for Instructions" or the state "Monitoring". the SCSM shall return to "Idle" state.

9. 9. that the ResetTimer operation has to be sent in order to avoid TSSF time-out at the SSF.26. 9.2 9.2.Page 175 ETS 300 374-1: September 1994 9.26.26.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. timerID: This parameter has a default value identifying the TSSF timer. Invoking entity (SCF) Normal procedure
-
9.1. (3) The SSF FSM is in the "Waiting for Instruction" state or in the "Waiting for End of User Interaction" state or in the "Waiting for End of Temporary Connection" state. The charging scenario supported by this operation is: scenario 3.3 9. SSF postconditions: (1) The TSSF timer has been reset.3.
. In the LE.26.2 (refer to Annex B). (2) An SLPI has determined by the TSCF-SSF guard timer expiration.27 9.26. (2) Basic call processing has been suspended at a DP.26. NOTE: The interworking between SSF and PSTN is network operator specific. This operation has many PSTN/IN interactions. A possibility exists for the SCI operation to be invoked on multiple occasions.1 SendChargingInformation procedure General description
This operation is used to instruct the SSF on the charging information to be sent by the SSF.26.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10.3.27. The sending of charging information can either be by charge pulses or signalling or internal if SSF is located in the Local Exchange (LE).1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) Call origination attempt has been initiated.1 Parameters
timerValue: This parameter specified the value to which the TSSF is to be set. SCF postcondition: (1) The SLPI reset the TSCF-SSF guard timer. 9. either a charge meter can be updated or a standard call record can be created. (2) The SSF FSM remains in the same state.2.1
SCF preconditions: (1) A control relationship exists between the SCF and the SSF.

1.2 9.27. or SSF FSM State e: "Waiting for End of Temporary Connection". either a charge meter can be updated or a standard call record can be created. In the LE.
. Its content is network operator specific. (2) An SLPI has determined that a SendChargingInformation has to be sent by the SCF.2. or Assisting/hand-off SSF FSM State b: "Waiting for Instructions". This operation has much PSTN/IN interactions.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. or SSF FSM State d: "Waiting for End of User Interaction". 9.27.
-
legID: This parameter indicates where the charging information shall be sent. Invoking entity (SCF) Normal procedure
9. The interworking between SSF and PSTN is network operator specific.1
SCF preconditions: (1) A control relationship exist between the SCF and the SSF. The SCSM FSM is in state "Preparing SSF Instruction" or is in state "Queuing FSM".2). If appropriate this information shall be send back down the call path.27. Depending on the applied charging scenario the following information elements can be included (refer to Annex B): charge level (scenario 3.3.Page 176 ETS 300 374-1: September 1994 9. The sending of charging information can either be by charge pulses or signalling or internal if SSF is located in the LE.27. This causes no SCSM FSM state transition. (2) SLPI execution may continue. The SendChargingInformation procedure shall be invoked by the SCF in accordance with the demands of the SLPI for relevant charging information.1 Parameters
sCIBillingChargingCharacteristics: This parameter indicates billing and/or charging characteristics.2. or SSF FSM State f: "Monitoring". chargePulses. 9.27.1 Responding entity (SSF) Normal procedure
SSF preconditions: (1) SSF FSM State c: "Waiting for Instructions". chargeMessages. SSF postcondition: (1) No FSM state transition. SCF postconditions: (1) No FSM state transition.27. On receipt of this operation the SSF performs actions to send the charging information.3 9.

3. 9.27.28. filteringCriteria: This parameter is used to address the concerned SL at the SCF. the SendChargingInformation operation contains the parameters to determine the charging level. In case of the SSF to determine the charging level. by sending an operation SendChargingInformation the SCF instructs the SSF to initiate the PSTN/ISDN charging functions according to the given information about the charging level to use. It is a list of counter identifications and the related values. or the SSF. 9. e.28. the charging level is determined in a succeeding exchange. If the charging level was determined by the IN (SCF or SSF). In case c).
In case of the SCF having determined the charging level.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are used for reporting operation errors are described in Clause 10. the SSF provides the charging level to be applied to the PSTN/ISDN charging functions (cases a and b). The charging level can be determined either by one of the following functions: a) b) c) the SCF.1. or the charging function in a succeeding exchange.1 Parameters
countersValue: The parameter contains the count of calls filtered during the filtering period. an international gateway).g.
-
. 9. The SendChargingInformation operation either contains the corresponding parameters indicating this fact or the SSF detects during trying to determine the charging level based on SCF provided parameters that the charging level shall be determined in a succeeding exchange. just like the charge generation and the charge registration.Page 177 ETS 300 374-1: September 1994 For instance. That means the determination of the charging method (on-line or off-line) and the items to be charged for shall be done in the basic network.1 ServiceFilteringResponse procedure General description
This operation is used to report the values of counters specified in a previous sent ActivateServiceFiltering operation to the SCF. In the scenario described above charging/billing is performed by means of existing mechanisms of the PSTN/ISDN initiated and controlled by the IN. Based on already existing PSTN/ISDN capabilities the SSF provides the PSTN/ISDN charging functions with the necessary information and backward charge messages shall be transferred down the call path when allowed by the SCF (generated by a succeeding exchange.28 9. the SendChargingInformation operation contains the charging level to be applied.

Page 178 ETS 300 374-1: September 1994 9. the ServiceFilteringResponse is not sent and the counting continues without resetting the counters. The last ServiceFilteringResponse (stop time is met or duration time expired) is sent without checking any call gap criteria. it is checked whether call gapping criteria are met.
.3. All concerned resources are released. The SCME passes the received counter values to the SLPI where they are added to previously received counter values.28. interval time expired) the SSME FSM remains in the state "Non-Call Associated Treatment". After sending ServiceFilteringResponse the service filtering counters are reset. i. 9.g.3 9.2 Error handling
If the SCME is in the state "Service Filtering Idle" an incoming ServiceFilteringResponse operation is ignored. or (4) The operation ActivateServiceFiltering is received and encounters an active service filtering entity. If so. Then the SLPI informs the SCME about timer expiration. the SSME FSM is removed as well. The SSF sends the ServiceFilteringResponse operation to the SCF.2 9. The "filteringCriteria" parameter is provided to enable the addressing of the concerned SL at the SCF.e. or (2) Service filtering is running and the threshold value is reached.3. SSF postcondition: (1) Service filtering proceeds or is ended depending on the duration time. The operation is handled by the Service Filtering FSM part of the SCME. Before ServiceFilteringResponse is sent. SCF postcondition: (1) The SCME forwards the received counter values to the SLPI. 9.28.2.2.1 Responding entity (SCF) Normal procedure
SCF preconditions: (1) Service filtering is running.28. or (3) Service filtering has been finished (duration time expired or stop time met).2 Error handling
Operation related error handling is not applicable.1 Invoking entity (SSF) Normal procedure
SSF preconditions: (1) Service filtering is running and the interval time is expired and a call is received. (2) The SCME is in the state "Waiting for SSF Service Filtering Response". Now the SCME moves to the state "Service Filtering Idle".28. If service filtering is stopped after sending ServiceFilteringResponse (duration time expired or stop time is met) then the SSME FSM moves to the "Idle Management" state. The "filteringCriteria" parameter as provided in ServiceFilteringResponse is used to address the SCME and the concerned SL instance. due to class 4 operation.28. 9. If service filtering proceeds after sending ServiceFilteringResponse (e.28. The Service Filtering FSM of the SCME remains in the state "Waiting For SSF Service Filtering Response" until the internal service filtering duration time in the SLPI expires.

. The SRSM FSM moves to the state "Idle".29. 9.29.3. 9. (3) All information has been sent to the user.3 9.Page 179 ETS 300 374-1: September 1994 9.29.1 Invoking entity (SRF) Normal procedure Parameters
SRF preconditions: (1) The SRSM FSM is in the state "User Interaction". 9.3.1 Responding entity (SCF) Normal procedure
SCF precondition: (1) The SCSM FSM is in the state "User Interaction". 9. the SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system after sending the SpecializedResourceReport operation to the SCF.29. (2) A PlayAnnouncement operation is being "RequestAnnouncementComplete" was set TRUE. the SCSM FSM moves to the state "Preparing SSF Instructions". (2) If the SpecializedResourceReport relates to a PlayAnnouncement operation with permission of SRF initiated disconnection. sub-state "Waiting for response from the SRF". due to class 4 operation.29. 9.29. SCF postconditions: (1) The SCSM FSM remains in the same state.1 None.2 Error handling
Operation related error handling is not applicable. due to class 4 operation.2.29.
executed
for
which
the
parameter
SRF postconditions: (1) The SRSM FSM remains in the same state. (2) If the "DisconnectFromIPForbidden" parameter was set FALSE.1 SpecializedResourceReport procedure General description
This operation is used as the response to a PlayAnnouncement operation when the announcement completed indication is set.29 9.29.2.2 9.1.2 Error handling
Operation related error handling is not applicable.

Page 180 ETS 300 374-1: September 1994
10
10. When the SSF FSM makes a state transition to the state Idle.1. which can only be the InitialDP operation. The following situations can occur when a message is sent between two physical entities: a dialogue shall be established: the TC-user issues a TC-BEGIN request primitive. the dialogue is locally ended by means of a TC-END request primitive with prearranged end.e. if the SCF entity has received an operation leading to the termination of the control relationship.
.
-
-
a dialogue shall not be established: for class 2 or 4 operations only the sending TC-user issues a TC-BEGIN request primitive and ends the dialogue locally after operation timeout by means of a prearranged end. once the SCF dialogue resources have been released any ERROR or REJECT components received for these sent operations will be discarded by TC as described in ETS 300 287 [5] (ITU-T Recommendation Q. SRF. a dialogue shall no longer be maintained: the TC-user issues a TC-END request primitive with either basic end or with pre-arranged end depending on the following conditions: basic end: operations leading to a termination of the control relationship can be transmitted by the SCF with a TC-END request primitive (basic) in case the SCF is not interested in the reception of any ERROR or REJECT components for these sent operations. as TC-user. The relevant INAP operation. the dialogue is ended with a TC-END request primitive (pre-arranged end) after the last associated operation timer expires.1
A dialogue shall be established when the SSF FSM moves from the state Trigger Processing to the state Waiting for Instructions. and SDF under normal operation. ApplyChargingReport or CallInformationReport the dialogue may be ended from the SCF by a TC-END request primitive with basic end. uses only the structured dialogue facility provided by TCAP.1
Services assumed from TCAP
Normal procedures
This subclause describes the procedures and TCAP primitives that shall be used for transmitting messages between SSF. The INAP. the control relationship is terminated). The dialogue shall no longer be maintained when the prearranged end condition is met in the SSF. a TC-END request primitive (basic) with zero components can be sent from the SCF.1. SCF.774). For all other operations sent from the SSF FSM.1.1 10. Upon reception of the TC-BEGIN indication primitive the receiving TC-user shall end the dialogue locally. shall be transmitted in the same message. SSF-to-SCF messages SSF FSM related messages
10. pre-arranged end: in case of an entity being interested in possible ERROR or REJECT messages in response to sent operations leading to a termination of the control relationship. When the SSF has sent the last EventReportBCSM. The receiving entity shall end the dialogue with a TC-END request primitive (basic or pre-arranged end) after successful processing of these operations (i. a dialogue shall be maintained: the TC-user issues a TC-CONTINUE request primitive. the dialogue shall be maintained.

the dialogue shall be maintained. the dialogue is locally terminated by means of a TC-END request primitive with prearranged end. When the SSF FSM makes a state transition to the state Idle.e. established for the transmission of the InitialDP operation).1. i.1. For all other operations sent from the Assisting/hand-off SSF FSM.2. upon reception of a TC-BEGIN indication primitive with a CallGap operation. 10. no dialogue shall be established when the ServiceFilteringResponse operation is sent. all other operations are sent after a dialogue was established from the SSF (the SCF has previously received a TC-BEGIN indication primitive with either an InitialDP or an AssistRequestInstructions operation). leading to the termination of the control relationship. the dialogue shall be maintained.Page 181 ETS 300 374-1: September 1994 10.
-
.1. The dialogue is ended by means of a TC-END request primitive with basic end. for sending one or more CallGap operations. For subsequent operations sent from the SCSM FSM.2 10. the dialogue is locally ended by means of a TC-END request primitive with prearranged end.1.e. a dialogue shall no longer be maintained when the return result of the ActivateServiceFiltering operation is sent. Alternatively. The dialogue shall no longer be maintained when the prearranged end condition is met in the SCF. The AssistRequestInstructions operation shall be transmitted with a TC-BEGIN request primitive. a dialogue shall not be established when a CallGap operation is sent without using a SCSM associated dialogue.2 SCME FSM related messages
The operations sent from the SCME FSM shall be issued according to the following procedures: the dialogue shall be maintained when the ActivityTest operation is sent. The operation is sent using a TC-BEGIN request primitive and the dialogue is terminated with a prearranged end.1.1
A dialogue shall be established when the SCSM FSM moves from state Idle to state Preparing SSF Instructions and an InitiateCallAttempt operation is sent to the SSF.1. 10. When the SCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires. the sending of operations.1. SCF-to-SSF messages SCSM FSM related messages
-
-
10. The operation is sent with a TC-BEGIN request primitive and the dialogue is ended by means of a TC-END request primitive with prearranged end. The dialogue shall no longer be maintained when the prearranged end condition is met in the SSF. by means of a TC-END request primitive (basic end) is possible. The dialogue shall be maintained and the CallGap operation(s) shall be sent with the first response of the SCSM FSM to the InitialDP operation. the SCME FSM may use an existing SCSM FSM associated dialogue which was initiated by a SSF FSM (i. the return result is transmitted with the same request.2.2 Assisting/hand-off SSF FSM related messages
A dialogue shall be established when the Assisting/hand-off SSF FSM moves from the state Idle to the state Waiting for Instructions.3 SSME FSM related messages
The following procedures shall be followed: the dialogue shall be maintained when the ActivityTest return result is sent. the dialogue is locally ended by means of a TC-END request primitive with prearranged end.

the dialogue is locally ended by means of a TC-END request primitive with prearranged end.Page 182 ETS 300 374-1: September 1994 a dialogue shall be established when an ActivateServiceFiltering operation is sent. The following primitives shall be used to report abnormal situations: operation errors. This is possible. a dialogue shall be aborted by the TC-user with a TC-U-ABORT request primitive. as defined in the core INAP. For all other operations sent from the SRF. SRF-SCF information shall be exchanged with TC-CONTINUE request primitives. are reported with TC-U-ERROR request primitive.
-
For abnormal situations detected by TCAP the same rules shall apply for transmission of TC-R-REJECT indication as for transmission of TC-U-REJECT request and for transmission of TC-P-ABORT indication as for transmission of TC-U-ABORT request primitive.
. the dialogue is locally terminated upon reception of a ServiceFilteringResponse operation using a TC-END request primitive with prearranged end. the SCF can send the last operation to the SRF with a TC-END request primitive (basic end) when the SCF does not expect any further messages and is no longer interested in any possible error and reject messages. it shall close the dialogue via a TC-END request primitive with basic end or via a TC-U-ABORT request primitive. Alternatively. SRF.1. In case an entity receives a TC-END indication primitive and after all components have been considered. the dialogue shall be maintained. if possible. In the relay case. SCF-to/from-SRF messages
-
10. rejection of a TCAP component by the TC-user shall be reported with TC-U-REJECT request primitive. The dialogue shall no longer be maintained when the prearranged end condition is met in both the SRF and SCF. In case any AE encounters an error situation the peer entity shall be explicitly notified of the error. When the SCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires. the dialogue is locally ended by means of a TC-END request primitive with prearranged end. the FSM is not in a state to terminate the control relationship. SCF. and SDF.2 Abnormal procedures
This subclause describes the procedures and TCAP primitives that shall be used for reporting abnormal situations between SSF. 10. When the SRSM FSM makes a state transition to the state Idle. The error cases are defined in Clause 8. In error situations prearranged end shall not be used. depending on whether any pending ERROR or REJECT component is to be sent or not. an appropriate internal error should be provided. because begin and end of the SRF-SCF relationship are embedded in the SSF-SCF relationship. the SRF-SCF relationship uses the SSF-SCF TCAP dialogue. The operation shall be transmitted with a TC-BEGIN request primitive. If from any entity's point of view the error encountered requires the relationship to be ended.3
A dialogue is established when the SRF sends an AssistRequestInstructions operation to the SCF.

e. any subsequent TC indication received for this dialogue will be handled according to the abnormal procedures as specified in ETS 300 287 [5] (ITU-T Recommendation Q. one that is the dialogue-initiator and one that is the dialogue-responder. 10.
-
-
If the error processing in the SSF/SRF leads to the case where the SSF/SRF is not able to process further SCF operations while the dialogue is to be maintained. the first TC-CONTINUE indication primitive occurring at the initiating side or under specific conditions: a TC-END indication primitive occurring at the initiating side.2. a TC-U-ABORT indication primitive occurring at the initiating side. the SSF/SRF aborts the dialogue with a TC-U-ABORT request primitive.2 SSF/SRF-to-SCF messages
Operation errors and rejection of TCAP components shall be transmitted to the SCF according to the following rules: the dialogue shall be maintained when the preceding message. The SSF aborts a dialogue with a TC-U-ABORT request primitive in case call release is initiated by any other entity then the SCF and the SSF has no pending CallInformationRequest (or pending requests which should be treated in the same way. the following shall apply: operation errors and rejection of TCAP components shall be transmitted to the SSF respectively SRF with a TC-END request primitive. a TC-BEGIN indication primitive occurring at the responding side. the SSF respectively the SRF shall abort the dialogue with a TC-U-ABORT request primitive. 10. in all other situations the dialogue shall no longer be maintained. which contained the erroneous component.2. AC negotiation may not be supported in all physical entities and/or all networks. indicated that the dialogue shall be maintained. on receipt of an ERROR or REJECT component the SCF decides on further processing.3 Dialogue establishment
The establishment of an INAP dialogue involves two application processes as described in subclause 4.774). an ERROR or REJECT component is received with a TC-CONTINUE indication primitive. basic end. explicitly end or abort the dialogue. ApplyCharging) nor any armed EDP to notify the SCF of the call release. the error or reject shall be transmitted with a TC-CONTINUE request primitive if the erroneous component was received with a TC-CONTINUE indication primitive. The result of these primitives will be only local. in violation of the above procedure. I.1 SCF-to-SSF/SRF messages
Considering that both SSF and SRF do not have the logic to recover from error cases detected on the SCF-SSF/SRF interface. the error or reject shall be transmitted with a TC-END request primitive.Page 183 ETS 300 374-1: September 1994 In cases when a dialogue needs to be closed by the initiating entity before its establishment has been completed (before the first TC indication primitive to the TC-BEGIN request primitive has been received from the responding entity).
If.3. I. if the erroneous component was received with a TC-BEGIN indication primitive. a TC-P-ABORT indication primitive occurring at the initiating side. This procedure is driven by the following signals: a TC-BEGIN request primitive from the dialogue-initiator. i. It may either continue.e. 10. basic end. the TC-user shall issue a TC-END request primitive with prearranged end or a TC-U-ABORT request primitive.
.e.

3. SACF shall: analyze the application-context-name included in the primitive and if it is supported. 10.2. SACF shall process the following TC component handling indication primitives as described in subclause 10. except a TC-U-ABORT request or a TC-END request with the release method parameter set to "prearranged release". SACF will wait for the last associated TCAP operation timer to expire and issue a TC-END request with the release method parameter set to "pre-arranged release".2.1 and 10.8.3 Receipt of the first TC-CONTINUE indication
On receipt of the first TC-CONTINUE indication primitive for a dialogue. If this value matches the one used in the TC-BEGIN request primitive.8.4 Receipt of a TC-END indication
On receipt of a TC-END indication primitive in the dialogue initiated state.Page 184 ETS 300 374-1: September 1994 10. After processing of the last invocation request. See subclause 10.3. the responding side may propose an alternative application-context-name in the TC-U-ABORT indication. except a TC-P-ABORT indication. If the abort reason is application-context-name not supported. otherwise it shall issue a TC-U-ABORT request primitive.5 Receipt of a TC-U-ABORT indication
Receipt of a TC-U-ABORT indication primitive is described as part of user abort procedure (see subclause 10. SACF does not accept any primitive from TC. SACF will wait for the last indication primitive from TC and issue a TC-END request with the release method parameter set to "pre-arranged release".3. SACF shall store the AC-name and if present the userinformation parameter. 10.
. process any other indication primitives received from TC as described in subclause 10.3. SACF shall request the invocation of the associated operations using the TC-INVOKE service.2).6. If an alternative application-context can be offered its name is included in the TC-U-ABORT request primitive.1 Sending of a TC-BEGIN request primitive
Before issuing a TC-BEGIN request primitive. 10. otherwise it shall not be processed. If an alternative application context is proposed the receiving entity shall check this name and if it can be supported a new dialogue may be established. If no TC indication primitive is expected because no dialogue is to be established according to the rules as stated in subclauses 10.2 Receipt of a TC-BEGIN indication
On receipt of a TC-BEGIN indication primitive. If this value matches the one used in the TC-BEGIN request primitive then the SACF shall process the following TC component handling indication primitives as described in subclause 10. The requesting side SACF then waits for a TC indication primitive and will not issue any other requests. If the application-context-name included in the primitive is not supported. issue a TC-U-ABORT request primitive.3.
Once all the received primitives have been processed.1 and 10. SACF shall issue a TC-BEGIN request primitive.8. 10. SACF shall check the value of the application-context-name parameter. If no dialogue is to be established according to the rules as stated in subclauses 10. SACF shall check the value of the application-context-name parameter.8 for a description of the invocation procedure.

SACF shall process any component handling request primitives as described in subclause 10.4.5 Dialogue termination
Both the dialogue-initiator and the dialogue-responder have the ability to request the termination of a dialogue when no dialogue is to be established or when a dialogue is no longer to be maintained according to the rules as stated in subclauses 10. SACF shall issue a TC-END request primitive with the release method parameter set to "basic end" or "pre-arranged release".2. 10. the SACF shall accept any component handling indication primitives and process them as described in subclause 10.2. 10.2 Receiving entity
On receipt of a TC-CONTINUE indication primitive SACF shall accept zero.3.3. 10.8.2.1 and 10.1 and 10.5.1 and 10. one or several TC component handling indication primitives and process them as described in subclause 10.6 User Abort
Both the dialogue-initiator and the dialogue-responder have the ability to abort a dialogue at any time.8. refer to subclauses 10. The dialogue termination procedure is driven by the following events: 10. When no dialogue is to be established.7.
. 10.3.8.4 Dialogue continuation
Once established the dialogue is said to be in a continuation phase. Both application processes can request the transfer of INAP APDUs until one of them requests the termination of the dialogue.2 Receipt of a TC-END indication
On receipt of a TC-END indication primitive.1 a TC-END request primitive. 10.4.8. SACF shall issue a TC-CONTINUE request primitive. Sending of TC-END request
When the dialogue shall no longer be maintained. After processing the last component handling request primitive.5. After processing the last component handling request primitive (if any).Page 185 ETS 300 374-1: September 1994 10.1). 10. After processing the last component handling primitive all dialogue related resources are released. a TC-END indication primitive.6 Receipt of a TC-P-ABORT indication
Receipt of a TC-P-ABORT indication primitive is described as part of provider abort procedure (see subclause 10. according to the rules as stated in subclauses 10.1 Sending entity
SACF shall process any component handling request primitives as described in subclause 10.

6. all dialogue related resources are released. request the transfer of a reject component using the TC-U-REJECT request primitive. if a linked ID is included.8 Procedures for INAP operations
This subclause describes the procedures for INAP operations. a TC-U-ABORT indication primitive.1 a TC-P-ABORT indication primitive.
-
-
-
. If a linked ID parameter is inserted in the primitive this indicates a child operation and implies that the operation is linked to a parent operation. or if the parent operation invocation is not active. Sending of TC-U-ABORT request
After issuing a TC-U-ABORT request primitive. with the appropriate problem code (mistyped parameter).8.1 Operation invocation
SACF shall build an operation argument from the parameters received and request the invocation of the associated operation using the TC-INVOKE procedure. The provider abort procedure is driven by the following event: 10.1 a TC-U-ABORT request primitive.2 Receipt of a TC-U-ABORT indication
On receipt of a TC-U-ABORT indication all dialogue related resources are released.7.7 Provider Abort
TC has the ability to abort a dialogue at both the dialogue-initiator side and the dialogue-responder side.6. all dialogue related resources are released. SACF shall: if the invoke ID is already in use by an active operation. Receipt of a TC-P-ABORT indication
On receipt of a TC-P-ABORT indication. issue a TC-U-REJECT request primitive with the appropriate problem code (linked response unexpected or unexpected linked operation). 10. 10.8.2 Operation invocation receipt
On receipt of a TC-INVOKE indication primitive. if the type of the argument is not the one defined for the operation. request the transfer of a reject component using the TC-U-REJECT request primitive with the appropriate problem code (duplicated invokeID).Page 186 ETS 300 374-1: September 1994 The user abort procedure is driven by one of the following events: 10. with the appropriate problem code (unrecognized operation). 10. 10. if the operation code does not correspond to an operation supported by the application-context. 10. request the transfer of a reject component using the TC-U-REJECT request primitive. perform the following checks: If the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to a permitted linked operation.

otherwise. with the appropriate problem code (mistyped parameter). if the type of the error parameter is not the one defined for this error. with the appropriate problem code (mistyped parameter).8. request the transfer of a reject component using the TC-U-REJECT request primitive. if sufficient INAP related resources are not available to perform the requested operation. requests the transfer of a reject component using the TC-U-REJECT request primitive with the problem code (Initiating Release).8. construct a result information element from the parameters received and request its transfer using the TC-RESULT-L service. Receipt of TC-RESULT-L indication
10.8. Operation response
-
-
10.3
For user confirmed operations. Receipt of TC-U-ERROR indication
-
10.4.4. if an error indication is included in the response to a class 1 or 2 operation.8. Receipt of a response Receipt of TC-RESULT-NL indication
-
10. with the appropriate problem code (unrecognized error or unexpected error).8. If the operation is to be user confirmed. construct an error parameter from the parameters received and request its transfer using the TC-U-ERROR request primitive.4.
-
-
. SACF shall: if the type of the result parameter is not the one defined for the result of this operation. otherwise. request the transfer of a reject component using the TC-U-REJECT request primitive. accept the TC-RESULT-L indication primitive.1
On receipt of a TC-RESULT-NL indication. with the appropriate problem code (mistyped parameter). request the transfer of a reject component using the TC-U-REJECT request primitive.4 10. SACF shall: if the error code is not defined for the SACF or is not one associated with the operation referred to by the invoke identifier. accept the TC-INVOKE indication primitive. accept the TC-U-ERROR indication primitive.2
On receipt of a TC-RESULT-L indication. SACF shall: request the transfer of a reject component using the TC-U-REJECT request primitive.Page 187 ETS 300 374-1: September 1994 if the operation cannot be invoked because the dialogue is about to be released. otherwise. request the transfer of a reject component using the TC-U-REJECT request primitive with the problem code (Resource Limitation). SACF waits for the corresponding response.3
On receipt of a TC-U-ERROR indication. SACF shall: if no error indication is included in the response to a class 1 or 3 operation.

4. On receipt of a TC-L-REJECT indicating "return result problem.Page 188 ETS 300 374-1: September 1994 10. when a protocol error has been detected by the peer TC entity) which does not affect an active operation. inform the application process. Other events
-
-
10. ignore the primitive.5
This subclause describes the behaviour of SACF on receipt of a component handling indication primitive which cannot be related to any operation or which does not affect a pending one.4 Receipt of TC-U-REJECT indication
On receipt of a TC-U-REJECT indication primitive which affects a pending operation.8. 10.8.5. indicating a return result or return error problem).2. This is because it is unclear whether the invoke ID refers to a local or remote invocation. return error unexpected". ignore the primitive.5.2 Receipt of a TC-R-REJECT indication
On receipt of a TC-R-REJECT indication (i.e. if the associated operation is a class 2 operation and a linked operation invocation has already been received in response to this operation. if not already terminated by the sending application process according to the rules as stated in subclause 10. the SACF shall: if the associated operation is a class 1 operation.
. inform the application process. if the associated operation is a class 4 operation. SACF shall inform the application process. inform the application process. return result unexpected".8. When the problem code indicates a general problem. if the associated operation is a class 2 operation and has linked operations but none of them has been invoked.8.5.4.5 Receipt of a TC-L-REJECT indication
This event occurs when the local TC detects a protocol error in an incoming component which affects an operation. if not already terminated by the sending application process according to the rules as stated in subclause 10. if the associated operation is a class 2 operation and no linked operations are defined for this operation.3. SACF shall inform the application process.1 Receipt of a TC-U-REJECT
On receipt of a TC-U-REJECT indication primitive which does not affect an active operation (i. it is considered that the event cannot be related to an active operation even if the invoke ID is provided by TC. it is up to the application process to abort. ignore the primitive.6 Receipt of a TC-L-CANCEL indication
On receipt of a TC-L-CANCEL indication. On receipt of a TC-L-REJECT indicating "return error problem. 10. it is up to the application process to abort. if the associated operation is a class 3 operation.8.4. SACF shall accept the TC-U-REJECT indication primitive.2. continue or terminate the dialogue. 10. 10.8.8.e. The behaviour of SACF in such a case is described in subclause 10. This is also applicable for invoke problems related to a class 4 linked operation. continue or terminate the dialogue.

this parameter is set by SACF in an implementation dependent manner.6 Component present
This parameter is used by SACF as described in ETS 300 287 [5] (ITU-T Recommendation Q. this can only occur if the Return Option has been set (see subclause 10.9.2 Originating address
This parameter is set by the dialogue initiating application process.4.771).4 Receipt of a TC-NOTICE indication
This informs the SACF that a message cannot be delivered by the Network Layer.
. and may optionally be modified by the responding dialogue in the first backward TC-CONTINUE.8).1.3 Receipt of a TC-L-REJECT indication
On receipt of a TC-L-REJECT indication primitive (i.1.2.8.9.1 and 10. 10. It is for the application process to decide whether to terminate the dialogue or retry.1.1.9. 10.4 Application-context-name
The application-context-name parameter is set by SACF as defined in subclause 6.e. 10.9. 10. return option.1.8. it is up to the application process to continue.9.9.9. 10.1 Mapping on to TC services Dialogue control
The TC-UNI service is not used by INAP.8 Quality of service
The quality of service of TC request primitives is set by the SACF to the following value: sequencing requested.7 Termination
The value of the release method parameter of the TC-END request primitive is set by SACF according to the rules as stated in subclauses 10. when a protocol error has been detected by the local TC entity) which cannot be related to an active operation.Page 189 ETS 300 374-1: September 1994 10.5.1 Destination address
This parameter is set by the dialogue initiating application process. 10. 10.3 Dialogue ID
The value of this parameter is associated with the INAP invocation in an implementation dependent manner.9.1. 10.5. 10. or to terminate the dialogue and implicitly trigger the transmission of the reject component or to abort the dialogue.9.1.9. 10.5 User information
This parameter may be used by both initiating and responding application processes.9 10.1.1.

3 Dialogue ID
The value of this parameter is associated with the INAP invocation in an implementation dependent manner.2.1.1 Operation procedures Invoke ID
This parameter is set by the sending application process.3.9.2. SACF shall set the operation code of the TC-RESULT-L primitive (if required) to the same value as the one received at invocation time.3.9. 10.2. The parameter of TC-U-ERROR primitives are set by the sending application process as defined in subclauses 6.2.1 and 6. 10.9. 10. 10. 10. 10.8.4.10 Problem code
This parameter is used by SACF as described in subclause 10.4.2.2.9.4 Class
The value of this parameter is set by SACF according to the type of the operation to be invoked according to subclause 6.2 Linked ID
This parameter is set by the sending application process.8 Time out
The value of this parameter is set by SACF according to the type of operation invoked. 10.9.771).7 Parameters
The argument parameter of TC-INVOKE primitives is set by the sending application process as defined in subclauses 6.
. 10.2.9.3.2 and 6.5 Operation
The operation code of a TC-INVOKE request primitive is set by the sending application process as defined in subclause 6.9.9.9.Page 190 ETS 300 374-1: September 1994 10.9.9. 10. The result parameter of TC-RESULT-L primitives is set by the sending application process as defined in subclauses 6.1 and 6.2.6 Error
The error parameter of the TC-U-ERROR request primitive is set by the sending application process as defined in subclause 6.2 10.9 Last component
This parameter is used by SACF as described in ETS 300 287 [5] (ITU-T Recommendation Q.2.2.

When for an IN call the charging processes in the SCP have to interwork with the charging processes in the SSP. accounting). First some terminology concerning charging processes and charging capabilities is listed. the charging as performed by the basic call process has to be extended. followed by particular charging scenarios for which the INAP requirements are listed. At a high level the following processes concerning the charging can be identified: Charge determination process (DET): determining the charge party. determining the level of charge.
. Charge generation process (GEN): generation of charge pulses or charge related signalling or charge related information for the off-line process.Page 203 ETS 300 374-1: September 1994
Annex B (informative): B. AOC (advice of charge) or for charge metering. This further processing of charging information in real time could be for the support of the pay phone. The calculation of the charge for that call and the billing is performed in an off-line process.
B. Charge registration process (REG): updating the charge meters or creating call records or both.3
Charging processes
Following considerations apply to the case of one service and one network.1 Introduction
Charging scenarios supported by core INAP
This annex provides information on how the different charging capabilities in INAP CS1 may be used. charging processes can be activated in both SCPs and SSPs. With the introduction of IN.2
Charging requirements
In general two types of charging capabilities are required. Charge party can be the calling line or IN service subscriber or both. B.1 Off-line charging
The usage and/or charge information of the call is recorded in the network.
B. determining the items to be charged. On-line Charge Information provision to the user access (ONC): provision of charge pulses or signalling information on the user/network interface during call instance. if determination of the previous elements is performed off-line then in that case only a default call record is registered. The information recorded could also be used for other purposes by the network operator (e. specific charging operations have to be transferred via the INAP.2.2 On-line charging
In this case charging information during the call instance has to be calculated in real time. Networks may support different or additional charging capabilities then listed in this annex.2. With IN. Via the information flows and information elements. B.g. the corresponding charging operations for the INAP can be defined. This annex describes the IN charging requirements from an INAP point of view.

1 Charging scenarios related to off-line charging
To support the off-line charging process. but the SSF-LE interface will be internal rather than by network signalling.4. 2.4.1) or both (scenario 2. In case call records are registered at both SSF and SCF. such as using the service access code to determine the tariff. either a charge meter can be updated or a standard call record can be generated. and all accounting will be performed at either the SSF or the SCF. The SCF need not know whether the SSP is a transit or a local exchange.1 Scenario 1: IN charging completely in the PSTN
In this case (scenario 1).3 Scenario 3: IN Charging shared between IN and PSTN
In this case. The PSTN will determine from e. B. Off-line charging/billing/accounting process (OFC): a FE which processes the call records retrieved from the other FEs (SSF. but call records may be registered at either the SSF (scenario 2.3) or SCF (scenario 2. For this mechanism. B.1. B. the service access code. the charging is done completely in the IN nodes. on operator request or scheduled. The choice of scenario for each charged party is a network specific option. Both the SCF and SSF should register this in the call record. and meters in the LE to count the charge pulses. the SCF has control of the charging information and instructs the SSF on the charging information to be sent by the SSF (scenario 3. Charging data can be output to magnetic tapes or datalinks.
. If the SSF is a LE. some charging related functions have to be executed during a call instance. B. the principles are the same.1. In the LE.Page 204 ETS 300 374-1: September 1994 Charge Output Process (OUT): output of charging data for further processing. SCF. The control of charging is always at the SCF. as no charging functions are performed by the SSF. the charging is done by the existing charging mechanisms in the PSTN. international exchange.2). LE) to prepare the bill for the subscriber or to support other accounting processes.2. the charging for services may be split between several parties.g.2 Scenario 2: IN charging completely in the IN
In this scenario. For this purpose the SCF should generate a unique correlationID and send it to the SSF. Each of the following scenarios shows a possible charging configuration for one of the parties.4.4.
B. no INAP operations are required. For each of the scenarios (and therefore for each charged party) there is only one point of control for IN charging per call. for the same call instance there should be a correlation between both call records to allow the off-line billing process to correlate them. Scenarios may be combined to give the total charging capabilities required for a service. There is no call record generated at the SSF or SCF. that no charge is to be raised.4).4
Charging scenarios
In an IN structured network.1. SCF or any other IN FE.

This on-line charging process may cause additional signalling traffic and processing load in both the IN and the PSTN/ISDN.e. clear the call).g.
.1: Scenario 3 B. To avoid additional processing and signalling in the network it may be useful to apply the on-line charging selectively (i. based on serviceKey. scenario 4 in case SSF in LE). Included in these instructions are the conditions on which the SSF should request further information from the SCF (e.1) or SSF (scenario 4. a threshold is reached.4. This means that at the user/network interface charge related information (like charge pulses or signalling information) have to be offered. or the SL (e. it shall be possible to offer the charge information to the LE. payphone or AOC). user service profile or user interaction).Page 205 ETS 300 374-1: September 1994
Figure B. e.1. The LE uses this information at the UNI.e. Whether on-line charging is required or not can be determined by either: an on-line charging indication from PSTN/ISDN to IN. then the SSF informs the SCF on what has happened and the SCF performs the necessary processing of the charge information. For IN calls.2). When SCF controls the charging and on-line charging is required for a call instance. inform the SCF when the charge reaches a certain amount).g. In that case the same configuration described in scenario 3 could be used to transfer the charge information in addition to the off-line charging related scenario. When the call has finished or e. scenario 2 and 4 in case SSF not in LE). charge rates need to be changed at certain times to all or dedicated destinations. some networks require scenarios to support the on-line charging capability.g. scenario 3. the SCF should be able to change the charge rates in the network.g. If this charge information is not delivered to the LE (i.2 Charging scenarios related to on-line charging
Apart from the scenarios supporting the off-line charging. assisted by the SSF
The SCF has the relevant charging information to apply charging and instructs the SSF to calculate the call charge. The calculated call charge can be registered at either the SCF (scenario 4.e. and possibly instructs the SSF what to do next (e. only on the calls for which it is necessary.4 Scenario 4: Charging at the SCF. Flexible tariffing is a concept used in many networks.4. thresholds. or per call instance dependent on the duration of the conversation or the service interactions involved. B.g.e. i. If this charge information is delivered to the LE for call recording purposes (i. this information may also be used for on-line charging. If the charging is controlled by the SCF. then additional IFs are needed for on-line charging.

Subsequently SCF may use this information performing its charging control (use the received charging information in the call record generation or to adjust new charge rates/pulses to be sent to the SSF for on-line charging).2 Call parties controlled by different SLs
This is the case for e. the selected option will remain during the lifetime of the call instance for the call party. Based on criteria supplied by the SCF. According to the general requirement "there is only one point of control for charging per call party per call". Interaction occurs in the following cases: case 1: SL-B causes charging information from SSF FSM-B towards SSF FSM-A. 2) after receipt of a specified number of messages of the appropriate type. the SSF will send this information to the SCF: 1) immediately after receipt of the appropriate message type.2.
. B. the SSF will send this information to the SCF: 1) immediately after receipt of the appropriate message type. NOTE: If both SSF FSMs reside in the same SSF. Interactions with other networks concerning charging control
This is the case when SSF receives charging-related signalling from a higher exchange (e.5
Interactions
Interactions concerning the charging of an IN call can occur in the following cases: 1) 2) B. the SL-A should select one of these options. Based on criteria supplied by the SCF.5. and to notify the SCF. Option 2: The SCF may also decide to leave the charge control to the higher exchange and monitor the charging events.5. B. international exchange or dedicated service exchanges). but the SSF FSM-A/SSF FSM-B interface will be internal rather than by network signalling. case 3: case 1 and case 2. then the principles will be the same. case 2: SL-A causes charging information from SSF FSM-A towards SSF FSM-B. According to the general requirement "there is only one point of control for charging per call party per call". Option 1: In this option SCF has control of the charging information and instructs SSF to monitor and intercept the charge related signalling message(s) (from ISUP and not charge pulses) received from a higher exchange. or 3) at the end of the call.5. or 3) at the end of the call.g.Page 206 ETS 300 374-1: September 1994
B. Option 3: Same case as for option 2 except that the SCF does not wish to monitor the charging events.g. call parties controlled by different SLs.g. UPT to UPT or UPT to VPN calls.1 Case 1: charging information from SSF FSM-B to SSF FSM-A
This interaction occurs when SL-B causes a charge pulse or signalling information from SSF FSM-B to SSF FSM-A.1 a higher exchange generating charge related signalling towards the SSP. For a call instance controlled by the SCF. For a call instance controlled by SL-A. 2) after receipt of a specified number of messages of the appropriate type. the selected option will remain during the lifetime of the call instance for the call party.
There are three options identified to handle this type of interaction. e. the SCF should select one of these options. There are three options identified to handle this type of interaction. In this case the SCF instructs SSF to use normal charging processing. send charge signalling information and/or charge pulses through to the LE and/or update charge meters according to the received charging information from the higher exchange.

This interaction can be managed by a superposition of the principles given for the cases 1 and 2. but the SSF FSM-A/SSF FSM-B interface will be internal rather than by network signalling.
B. Based on criteria supplied by the SCF.g.5. In this case the SL-A instructs SSF FSM-A to use normal charging processing. SL-A may use this information performing its charging control (use the received charging information in the call record generation.Page 207 ETS 300 374-1: September 1994 Option 1: In this option SL-A has control of the charging information for the A-party and instructs SSF FSM-A to monitor and intercept the charge related messages received from SSF FSM-B and send it to the SL-A. or 3) at the end of the call. or 3) at the end of the call. e. Based on criteria supplied by the SL-A the SSF will send this information to the SL-A: 1) immediately after receipt of the appropriate message type. charging scenario(s) are pre-defined per service. as they have no impact on the scenarios defined. The decision to perform DET/GEN/REG in the SSF or SCF can be made on a per call basis by the SCF. and to notify the SL-A.e. 2) after receipt of a specified number of messages of the appropriate type. Option 3: Same case as for option 2 except that SL-A does not wish to monitor the charging events. B.6
Framework for the charging operations in INAP
In general: the starting point for the INAP work on charging is one service and one network.3 Case 3: charging information from SSF FSM-A to SSF FSM-B and reverse
This interaction occurs when both SL-B causes a charge pulse or signalling information 2) from SSF FSMB to SSF FSM-A and SL-A causes a charge pulse or signalling information2) from SSF FSM-A to SSF FSM-B. adjust new charge rates/pulses to be sent to the SSF FSM-A for on-line charging mechanism).
-
2)
If both SSF FSMs reside in the same SSF. send charge signalling information and/or charge pulses through to the LE and/or update charge meters according to the received charging information from the SSF FSM-B. the processes OFC and OUT are not listed in the framework.2. SL-B selects one of the options). then the principles will be the same. Option 2: The SL-A may also decide to leave the charge control to the SL-B but monitor the charging events. Subsequently. the SSF will send this information to the SCF: 1) immediately after receipt of the appropriate message type.
.5. B.2.2 Case 2: charging information from SSF FSM-A to SSF FSM-B
This interaction occurs when SL-A causes a charge pulse or signalling information2) from SSF FSM-A to SSF FSM-B. To handle this type of interaction the same options apply as case 1 (i. 2) after receipt of a specified number of messages of the appropriate type.

The relationship between DP criteria and minimum parameter population rules is not defined in this version of the ETS.1
DP criteria UNCONDITIONAL Line based UNCONDITIONAL Trunkgroup based UNCONDITIONAL Private facility based Key: X : applicable : not applicable 1 X X X 2 X X X 3 X X X 4 X X X 5 X X X 6 X X X 7 8 9 X X X 10 12 X X X 13 X X X 14 X X X 15 16 17 X X X 18 -
A "X" for the selected DPs means really the point in call when the BCSM should be suspended.2
BCSM TDPs and TDP criteria
The following classification is used. irrespective the value of the analyzed information the BCSM should be suspended.g. Such requirements should be considered carefully so as not to adversely impact memory and real-time performance of CCF/SSF processing. Table C.3. E.1.Page 209 ETS 300 374-1: September 1994
Annex C (informative): C.2. for DP3 the information should only be analyzed whereafter.3.
. private facility or office basis may have an impact on the memory and real time performance requirements of the CCF/SSF. Note. The unconditional TDPs can be: customer based. private facility (e. trunkgroup based. In addition the indicated applicability of trigger criteria to the TDPs are considered as being useful in the context of core INAP and it is not intended to be restrictive.1 Unconditional TDPs
The unconditional TDPs can be used by itself. If network and service providers plan to implement IN CS1 services in a multi-supplier environment. that the assignment of DP to a TDP on either a customer/trunkgroup. they should consider formulating such requirements to ensure consistent implementations across supplier equipments.1 Introduction
Trigger Detection Points (TDPs) and trigger criteria for the CS1 core INAP
This annex provides for the core INAP information on the applicability of the CS1 Detection Points (DPs) as Trigger Detection Points (TDPs) and on the applicability of trigger criteria that are listed and clarified in ITU-T Recommendation Q. however. Centrex) based. § 6.
The unconditional TDPs are listed in table C. C.3. The core INAP places no requirements on equipment suppliers in this area. This annex has no intention to be restrictive on the use of the EventTypeBCSM parameter in the InitialDP operation.1219. related to DPs of the BCSM without any other criterion to be satisfied at the TDP before informing the SCF that the TDP was encountered. All values of the EventTypeBCSM are possible.g.
C. Note further that the applicability of DP criteria at a given DP depends on when call processing is available and how long it is retained.

the treatment is the same as a criteria marked with a "X". The analysis should not be based on the complete calling party number. stored as Class of Service attribute) the received information and has to initiate an IN trigger if required.2.Page 210 ETS 300 374-1: September 1994 C.2
DP criteria Class of service Specific digit string (NOTE 1) Feature code (NOTE 1) Prefixes (NOTE 1) Access Codes (NOTE 1) Called party number (NOTE 1) Facility information (NOTE 2) Feature activation (NOTE 3) Cause Specific ABD string (NOTE 1) Specific calling party number (NOTE 4) Nature of address Bearer capability Key: X : applicable : not applicable O : optional NOTE 1: 1 X X X 2 O X X X X X O O 3 O X X X X X X X X O X O 4 O O O O O O X X O O O O 5 O O O O O O X X O O O O 6 O O O O O O X O O O O 7 O O O O O O X X O O O O 8 O O O O O O X X O O O O 9 O O O O O O X X O O O O 10 O O O O O O X X O O O O 12 X X O 13 O X O O 14 O X O O 15 O X X O O 16 O X X O O 17 O X X O O 18 O X X O O
NOTE 2: NOTE 3:
NOTE 4:
Same type of trigger requiring analysis of a specific number of received digits. starting from the most significant digit of the calling party number.1. a conditional TDP at DP1 may require the class of service criteria to be satisfied before the SCF is informed that the TDP was encountered. then this means that a conditional TDP which is armed at the DP may require the criteria as listed in the table to be satisfied before informing the SCF that the TDP was encountered. In a local exchange only. private facility based. then this means that it is implementation dependent if the criteria specific information is still present at that DP because not all suppliers may retain this information for the duration of the call/attempt. If the information is still present. it shall be based on a predefined number of digits. Concerning impact on memory and real time performance. A feature activation/indication can be available at DP14-18 in the TBCSM for a party served by an ISDN BRI or PRI and can be available at DP16 in the TBCSM for a party served by a non-ISDN line. If a criteria is marked with an "O" for a DP. A feature activation/indication can be available at DP3-10 in the OBCSM for a party served by an ISDN BRI or PRI and can be available at DP8 in the OBCSM for a party served by a non-ISDN line. office based.2. The BCSM has to analyze (if facility is allowed. see Clause C. The analysis can be based on the complete number of received digits or can be based on a predefined number of digits starting from the most significant digit of the received information. E. A match on the FacilityInformationElement contained in a signalling message as defined in DSS1 and ISUP. Table C.
. trunkgroup based.g. The entries in the table can be: customer based.2 Conditional TDPs
Related to DPs with additional trigger criteria as listed in the table C.
If a criteria is marked with a "X" for a DP.

Page 211 ETS 300 374-1: September 1994 DP of the OBCSM and TBCSM DP1 DP2 DP3 DP4 DP5 DP6 DP7 DP8 DP9 DP10 DP11 DP12 DP13 DP14 DP15 DP16 DP17 DP18 C.2. at DP3. During the processing of TDP-Rs at a DP. the SSF has to check the set of criteria associated with each TDP-R in descending order of priority until either the set of criteria for a particular TDP-R are met (resulting in informing the SCF) or all sets of criteria have been checked and none have been met. C.
The criteria combinations to be checked for a particular TDP is to be specified by means of management procedures applicable for the CCF/SSF. conditions specific to the particular TDP-R that shall be met before the SCF is informed that the TDP is encountered).2.g.g. at DP3.g. Criteria may be combined using the: AND function (e. initiate an SCF enquiry if "Called Party Number" = 831 or "Called Party Number" = 836). at DP3.e. OR function (e. Each TDP-R will have an associated set of criteria (i. each TDP-R being either an unconditional or a conditional TDP.3 OriginatingAttemptAuthorized CollectedInfo AnalyzedInformation RouteSelectFailure OCalledPartyBusy ONoAnswer OAnswer OMidCall ODisconnect OAbandon Reserved TerminatingAttemptAuthorized TCalledPartyBusy TNoAnswer TAnswer TMidCall TDisconnect TAbandon Trigger criteria combinations
A particular conditional TDP may require a combination of the applicable criteria to be checked before informing the SCF that the TDP was encountered. initiate an SCF enquiry if "Class of Service" = international call barred AND "Nature of Address" = international). The priority of the TDP-Rs at a DP is to be specified by means of management procedures applicable for the CCF/SSF.
. initiate an SCF enquiry if "Called Party Number" is NOT = 831). NOT function (e.4 Trigger criteria priorities
Multiple TDP-Rs may be armed at the same DP.