7.1.1.5.3 State c: "Waiting for Instructions"

This State is entered from either the Trigger Processing State, as indicated above (transition e4), or directly from the Idle State on receipt at the SSF of a TC_Begin indication primitive containing an "Initiate Call" operation from the SCF (transition e3), or from the state Monitoring on detection of an EDP-R (transition e10). In the second case (transition e3), the SSF moves to the Waiting for Instructions State immediately and then proceeds according to the contents of the "Initiate Call" operation and any other received operations.
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.
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 user abandons or disconnects. This should be processed in accordance with the general rules in subclause 7.1.1.5;
• the application Timer TSSF expires: the SSF FSM moves to the Idle State, the CCF routes the call if possible (e.g. default routing to a terminating announcement), the TSSF expiration is reported to the maintenance functions and the transaction is aborted;
• an operation is received from the SCF: The SSF FSM acts according to the operation received as described below.

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
RequestNotificationChargingEvent
ResetTimer
FurnishChargingInformation
ApplyCharging
CallInformationRequest
SendChargingInformation
Cancel

The following operations may be received from the SCF and processed by the SSF, 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, causing a state transition to Waiting for End of Temporary Connection state (transition e7):
EstablishTemporaryConnection

The following operations may be received from the SCF and processed by the SSF, 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
CollectInformation
Continue
ReleaseCall

ReleaseCall operation may be received from SCF and processed by the SSF, causing a transition to Idle state (transition e9). If there is a Call Information Request, the SSF sends a CallInformationReport operation to the SCF before returning to Idle.
Initiate Call Attempt operation, if received in Idle state, should be processed in Waiting for Instructions State (transition e3).
When processing the above operations, any necessary call handling information is provided to the Call Control Function (CCF).
Any other operation received in this state should be processed in accordance with the general rules in subclause 7.1.1.5.

7.1.1.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.e., Play Announcement, Prompt & Collect User Information and Cancel Announcement) for relaying is received and is correct, the operation is transferred to the SRF for execution. The SSF FSM Result from Prompt and Collect user Information) for relaying is received and is correct, the operation is transferred to the SCF. The SSF FSM remains in the Waiting for End of User Interaction State (transition e13);
• the application timer TSSF expires: the SSF FSM moves to the Idle State, the CCF routes the call if possible (e.g. default routing to a terminating announcement), the TSSF expiration is reported to the maintenance functions and the transaction is aborted;
• an operation is received from the SCF: The SSF FSM acts according to the operation received as described below;
• the user abandons. This should be processed in accordance with the general rules in subclause 7.1.1.5.

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
ResetTimer
FurnishChargingInformation
ApplyCharging
Send Charging Information
The DisconnectForwardConnection operation may be received from the SCF and processed by the SSF in this state. Call disconnect can also be received from the SRF. In both cases this causes the release of the connection to the SRF and the transition to the Waiting for Instructions state. The disconnection is not transferred to the other party (transition e6).
Any other operation received in this state should be processed in accordance with the general rules in subclause 7.1.1.5.

7.1.1.5.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.
The call is routed to the assisting SSF/SRF and call handling is suspended while waiting for the end of the assisting procedure. The timer TSSF is active in this State.
During this State the following events can occur:

• the application Timer TSSF expires: the SSF FSM moves to the Idle State, the CCF routes the call if possible (e.g. default routing to a terminating announcement), the TSSF expiration is reported to the maintenance functions and the transaction is aborted;
• the receipt of an indication of disconnection of forward connection from the CCF. In this case, the SSF moves to the Waiting for Instructions state (transition e8). The disconnection is not transferred to the Calling party;
• the user abandons. This should be processed in accordance with the general rules in subclause 7.1.1.5;
• an operation is received from the SCF. The SSF acts according to the operation received as described below.

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
FurnishChargingInformation
ApplyCharging
SendChargingInformation The DisconnectForwardConnection operation may be received from the SCF and processed by the SSF in this state. Call disconnect can also be received from the SRF. In both cases this causes the release of the connection to the SRF and the transition to the Waiting for Instructions state. The disconnection is not transferred to the other party (transition e8).
Any other operation received in this state should be processed in accordance with the general rules in subclause 7.1.1.5.