10 Error procedures
29.0783GPPCAMEL Application Part (CAP) specificationCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase XRelease 17TS
The present clause specifies the generic error procedures for CAP. The error procedure descriptions are divided in two subclauses, subclause 10.1 listing the errors related to CAP Operations and subclause 10.2 listing the errors related to error conditions in the different FEs which are not directly related to the CAP Operations.
The gsmSSF FSM states, smsSSF FSM states and gprsSSF FSM states which are referred to in the present clause are described in 3GPP TS 23.078 [7]. The CAP Operations PlayAnnouncement, PromptAndCollectUserInformation and SpecializedResourceReport refer to states in the gsmSRF SRSM which are described in ETSI ETS 300 374-1 [24] as well as to states in 3GPP TS 23.078 [7].
10.1 Operation related error procedures
The following subclauses specify the generic error handling for the CAP Operation related errors. The errors are defined as Operation Errors in clauses 6, 7 and 8. Errors which have a specific procedure for a CAP Operation are described in clause 11 with the detailed procedure of the related CAP Operation.
The TC services which are used for reporting CAP Operation Errors are described in subclause 14.1. All Errors which can be detected by the ASN.1 decoder, already may have been detected during the decoding of the TC message and indicated by the TC error indication "MistypedParameter" in the TC-U-Reject.
10.1.1 Canceled
10.1.1.1 General Description
10.1.1.1.1 Error description
The gsmSRF uses this Error to indicate" to the gsmSCF that the cancellation of a specific CAP Operation, as requested by the gsmSCF, has been successful. The only CAP Operations which may be cancelled are PlayAnnouncement and PromptAndCollectUserInformation.
10.1.1.2 Operations gsmSCF🡪gsmSRF
Procedures at responding entity (gsmSRF)
A) Receiving Cancel
Precondition: SRSM FSM state "User Interaction".
Postcondition: SRSM FSM state "User Interaction".
If execution of the indicated CAP Operation has not yet started, then the indicated CAP Operation shall be removed from the buffer. If execution of the indicated CAP Operation is in progress, then the execution of that CAP Operation shall be terminated. If the indicated CAP Operation was already executed, then then this causes a failure ("CancelFailed").
B) Sending Error "Canceled"
Precondition: SRSM FSM state "User Interaction".
Postcondition: SRSM FSM state "User Interaction".
After returning the Error "Canceled", the gsmSRF FSM remains in the same state. The execution of the indicated PlayAnnouncement or PromptAndCollectUserInformation CAP Operation is aborted. The gsmSRF shall remain connected and the next PlayAnnouncement or PromptAndCollectUserInformation CAP Operation, if available, shall be executed.
10.1.2 CancelFailed
10.1.2.1 General description
10.1.2.1.1 Error description
The gsmSRF uses this Error to indicate to the gsmSCF that the cancellation of a specific CAP Operation, as requested by the gsmSCF, was not successful. Possible failure reasons are:
0 "unknownOperation", when the InvokeID of the CAP Operation to cancel is not known to the gsmSRF (this may also happen when the CAP Operation has already been completed);
1 "tooLate", when the invokeID is known but the execution of the CAP Operation is in a state in which it cannot be canceled anymore. For instance the announcement is finished but the SpecializedResourceReport has not been sent to the gsmSCF yet. The conditions for the occurrence of failure reason "tooLate" are implementation dependent;
2 "operationNotCancellable", when the invokeID points to a CAP Operation that the gsmSCF is not allowed to cancel.
10.1.2.2 Operations gsmSCF🡪gsmSRF
Procedures at responding entity (gsmSRF)
A) Receiving Cancel. However, the indicated CAP Operation is not known, or has already been executed or may not be cancelled. This causes a failure, "CancelFailed".
Precondition: SRSM FSM state "User Interaction".
Postcondition: SRSM FSM state "User Interaction" or
SRSM FSM state "Idle".
B) Sending Error "CancelFailed"
Precondition: SRSM FSM state "User Interaction" or
SRSM FSM state "Idle".
Postcondition: SRSM FSM state "User Interaction" or
SRSM FSM state "Idle".
After returning the Error "CancelFailed" the gsmSRF FSM remains in the same state.
10.1.3 ETCFailed
10.1.3.1 General description
10.1.3.1.1 Error description
The gsmSSF uses this Error to indicate to the gsmSCF that the establishment of a temporary connection to an assisting gsmSSF or gsmSRF was not successful (e.g., receiving a "Backwards Release" after sending an ISUP IAM).
10.1.3.2 Operations gsmSCF🡪gsmSSF
Procedures at responding entity (gsmSSF)
A gsmSSF receives EstablishTemporaryConnection from a gsmSCF but the establishment of the connection fails, which results in returning the Error "ETCFailed" to the gsmSCF.
Precondition: gsmSSF FSM state "Waiting_for_Instructions".
Postcondition: gsmSSF FSM state "Waiting_for_Instructions".
No further error treatment.
10.1.4 ImproperCallerResponse
10.1.4.1 General description
10.1.4.1.1 Error description
The gsmSRF uses this Error to indicate to the gsmSCF that the format of the user input has been checked by the gsmSRF, but does not correspond to the required format as it was defined in the initiating CAP Operation.
10.1.4.2 Operations gsmSCF🡪gsmSRF
Procedures at responding entity (gsmSRF)
A) gsmSRF receives PromptAndCollectUserInformation
Precondition: SRSM FSM state "Connected"; or
SRSM FSM state "User Interaction".
Postcondition: SRSM FSM state "User Interaction".
B) format of the user input is not correct, gsmSRF returns ImproperCallerResponse to gsmSCF
Precondition: SRSM FSM state "User Interaction".
Postcondition: SRSM FSM state "User Interaction".
The gsmSRF shall wait for a new CAP Operation from the gsmSCF. This may be a new PromptAndCollectUserInformation or a PlayAnnouncement.
10.1.5 MissingCustomerRecord
10.1.5.1 General description
10.1.5.1.1 Error description
The gsmSCF uses this Error to indicate to the gsmSSF, gprsSSF, smsSSF or gsmSRF, that the SLP could not be found in the gsmSCF, because the required customer record does not exist, or the requested SLPI, indicated by the correlationID in "AssistRequestInstructions" does not exist anymore.
10.1.5.2 Operations gsmSSF🡪gsmSCF
Procedures at invoking entity (gsmSSF)
A) Sending CAP Operation
Precondition: gsmSSF FSM state "Trigger processing" or
gsmSSF FSM state "Waiting_for_Instructions"; in the assisting gsmSSF case.
Postcondition: gsmSSF FSM state "Waiting_for_Instructions".
gsmSSF FSM state "Waiting_for_Instructions"; in the assisting gsmSSF case.
B) gsmSSF receives Error "MissingCustomerRecord"
Precondition: gsmSSF FSM state "Waiting_for_Instructions" or
gsmSSF FSM state "Waiting_for_Instructions"; in the assisting gsmSSF case.
Postcondition: gsmSSF FSM state "Idle" or
gsmSSF FSM state "Idle"; in the assisting gsmSSF case.
The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter of the valid CSI.
10.1.5.3 Operations gsmSRF🡪gsmSCF
Procedures at invoking entity (gsmSRF)
A) Sending CAP Operation
Precondition: SRSM FSM state "Connected".
Postcondition: SRSM FSM state "Connected".
B) gsmSRF receives Error "MissingCustomerRecord"
Precondition: SRSM FSM state "Connected".
Postcondition: SRSM FSM state "Idle".
The gsmSRF shall initiate a Disconnect.
10.1.5.4 Operations smsSSF🡪gsmSCF
Procedures at invoking entity (smsSSF)
A) Sending CAP Operation
Precondition: smsSSF FSM state "Waiting_for_Instructions".
Postcondition: smsSSF FSM state "Waiting_for_Instructions".
B) smsSSF receives Error "MissingCustomerRecord"
Precondition: smsSSF FSM state "Waiting_for_Instructions".
Postcondition: smsSSF FSM state "Idle".
The VMSC or SGSN shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI.
10.1.5.5 Operations gprsSSF🡪gsmSCF
Procedures at invoking entity (gprsSSF)
A) Sending CAP Operation
Precondition: gprsSSF FSM state "Waiting_for_Instructions".
Postcondition: gprsSSF FSM state "Waiting_for_Instructions".
B) gprsSSF receives Error "MissingCustomerRecord"
Precondition: gprsSSF FSM state "Waiting_for_Instructions".
Postcondition: gprsSSF FSM state "Idle".
The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI.
10.1.6 MissingParameter
10.1.6.1 General description
10.1.6.1.1 Error description
The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that there is an error in the received CAP Operation argument. The responding entity cannot start the execution of the requested CAP Operation because the argument is incorrect: an expected optional parameter which is essential for the application is not included in the CAP Operation argument.
10.1.6.2 Operations gsmSCF🡪gsmSSF
Procedures at responding entity (gsmSSF)
Precondition: (1) gsmSSF FSM appropriate state
(2) gsmSSF FSM Call associated CAP Operation received, appropriate event occurred
(3) gsmSSME FSM appropriate state
(4) gsmSSME FSM Non call associated CAP Operation received, appropriate event
Postcondition: (1) No gsmSSF FSM transition
(2) gsmSSME FSM transition to the initial state (i.e., before receiving the erroneous CAP Operation)
The gsmSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation.
10.1.6.3 Operations gsmSSF🡪gsmSCF
Procedures at invoking entity (gsmSSF)
A) Sending CAP Operation
Precondition: gsmSSF FSM appropriate state
Postcondition: gsmSSF FSM appropriate state as result of the transfer of the CAP Operation
B) gsmSSF receives Error "MissingParameter"
Precondition: gsmSSF FSM appropriate state as result of the transfer of any of the CAP Operation
Postcondition: gsmSSF FSM state "Idle"
After receiving this Error, the gsmSSF FSM shall return to the state "Idle". The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter , valid for this CAMEL dialogue. In the case of an assisting gsmSSF, the temporary connection shall be released by the assisting gsmSSF.
10.1.6.4 Operations gsmSCF🡪gsmSRF
Procedures at responding entity (gsmSRF)
Precondition: SRSM FSM state "Connected"; or
SRSM FSM state "User Interaction".
Postcondition: SRSM FSM state "User Interaction".
The SRSM detects that a required parameter is not present in the CAP Operation argument. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation.
10.1.6.5 Operations gsmSRF🡪gsmSCF
Procedures at invoking entity (gsmSRF)
A) Sending CAP Operation
Precondition: SRSM FSM state "Connected".
Postcondition: SRSM FSM state "Connected".
B) Receiving Error
Precondition: SRSM FSM state "Connected".
Postcondition: SRSM FSM state "Idle".
The gsmSCF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is used to inform the gsmSRF of this situation. The SL and maintenance functions are informed. The gsmSCF might try another gsmSRF, route the call or release the call (SL dependent).
10.1.6.6 Operations smsSSF🡪gsmSCF
Procedures at invoking entity (smsSSF)
A) Sending CAP Operation
Precondition: smsSSF FSM state "WaitingForInstructions".
Postcondition: smsSSF FSM state "WaitingForInstructions".
B) Receiving Error
Precondition: smsSSF FSM state "WaitingForInstructions".
Postcondition: smsSSF FSM state "Idle".
After receiving this error, the smsSSF FSM shall transit to the state "Idle". The SGSN or VMSC shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI.
10.1.6.7 Operations gsmSCF 🡪 smsSSF
Procedures at responding entity (smsSSF)
precondition:
(1) smsSSF appropriate state.
(2) smsSSF SMS associated CAP Operation received, appropriate event occurred.
postcondition:
(1) smsSSF transition to the same state.
The smsSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation.
10.1.6.8 Operations gprsSSF🡪gsmSCF
Procedures at invoking entity (gprsSSF)
A) Sending CAP Operation
Precondition: gprsSSF FSM state "Waiting_for_Instructions".
Postcondition: gprsSSF FSM state "Waiting_for_Instructions".
B) Receiving Error
Precondition: gprsSSF FSM state "Waiting_for_Instructions".
Postcondition: gprsSSF FSM state "Idle".
After receiving this error, the gprsSSF FSM shall transits to the state "Idle". The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI.
10.1.6.9 Operations gsmSCF🡪gprsSSF
Procedures at responding entity (gprsSSF)
precondition:
(1) gprsSSF appropriate state.
(2) gprsSSF CAP Operation received, appropriate event occurred.
postcondition:
(1) gprsSSF transition to the same state.
The gprsSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation.
10.1.7 ParameterOutOfRange
10.1.7.1 General description
10.1.7.1.1 Error description
The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot start the execution of the requested CAP Operation because an error in a parameter of the CAP Operation argument is detected: a parameter value is out of range.
10.1.7.2 Operations gsmSCF🡪gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.7.3 Operations gsmSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.7.4 Operations gsmSCF🡪gsmSRF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.7.5 Operations smsSSF 🡪 gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.7.6 Operations gsmSCF🡪smsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.7.7 Operations gprsSSF 🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.7.8 Operations gsmSCF🡪gprsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.8 RequestedInfoError
10.1.8.1 General description
10.1.8.1.1 Error description
The gsmSSF uses this Error to indicate to the gsmSCF that the information requested in the CallInformationRequest CAP Operation is not known to the gsmSSF or is not available.
10.1.8.2 Operations gsmSCF🡪gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9 SystemFailure
10.1.9.1 General description
10.1.9.1.1 Error description
The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this error to indicate that it is not able to execute a specific task as requested by a CAP Operation, and recovery is not expected to be completed within the current call instance.
10.1.9.2 Operations gsmSCF🡪gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9.3 Operations gsmSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9.4 Operations gsmSCF🡪gsmSRF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9.5 Operations gsmSRF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9.6 Operations smsSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9.7 Operations gsmSCF🡪smsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9.8 Operations gprsSSF 🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.9.9 Operations gsmSCF🡪gprsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10 TaskRefused
10.1.10.1 General description
10.1.10.1.1 Error description
The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it is not able to execute a specific task as requested by a CAP Operation, and recovery is expected to be completed within the current call instance.
If the gsmSSF requests MoveLeg or SplitLeg operations in the gsmSSF while user interaction is in progress in an affected Call Sement, then CAP_Error (task refused) is returned.
10.1.10.2 Operations gsmSCF🡪gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10.3 Operations gsmSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10.4 Operations gsmSCF🡪gsmSRF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10.5 Operations gsmSRF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10.6 Operations smsSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10.7 Operations gsmSCF🡪smsSSF
SMS Related
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10.8 Operations gprsSSF 🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.10.9 Operations gsmSCF🡪gprsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.11 UnavailableResource
10.1.11.1 General description
10.1.11.1.1 Error description
The gsmSRF uses this Error to indicate to the gsmSCF that it is not able to perform its function (i.e., play a certain announcement and/or collect specific user information), and cannot be replaced. A reattempt is not possible.
10.1.11.2 Operations gsmSCF🡪gsmSRF
Procedures at responding entity (gsmSRF)
A) gsmSRF receiving PlayAnnouncement or PromptAndCollectUserInformation
Precondition: SRSM FSM state "Connected"; if initial PlayAnnouncement or PromptAndCollectUserInformation; or
SRSM FSM state "User Interaction"; if not initial PlayAnnouncement or PromptAndCollectUserInformation.
B) gsmSRF is not able to perform its function (and cannot be replaced). The gsmSRF sends the Error "UnavailableResource".
Precondition: SRSM FSM state "User Interaction".
Postcondition: SRSM FSM state "User Interaction".
10.1.12 UnexpectedComponentSequence
10.1.12.1 General description
10.1.12.1.1 Error description
The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot start the execution of the requested CAP Operation because a SACF or MACF rule is violated, or the CAP Operation cannot be executed in the current state of the FSM.
10.1.12.2 Operations gsmSCF🡪gsmSSF
In this case the gsmSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state.
10.1.12.3 Operations gsmSSF🡪gsmSCF
If the CAP Operation is sent by an "initiating" gsmSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error the gsmSSF FSM shall transit to the state "Idle". The VMSC or GMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue.
10.1.12.4 Operations gsmSCF🡪gsmSRF (applicable for direct gsmSCF-gsmSRF case only)
In this case the gsmSRF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state.
10.1.12.5 Operations gsmSRF🡪gsmSCF
In this case, an error occurs if the gsmSRF has already an established relationship with the gsmSCF and sends the CAP Operation AssistRequestInstructions. The gsmSCF detects the erroneous situation, informs SL and maintenance functions and returns the error parameter. On receiving the Error parameter, the gsmSRF FSM shall transit to the state "Idle" and releases the temporary connection.
10.1.12.6 Operations smsSSF 🡪gsmSCF
If the CAP Operation is sent by the smsSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error, the smsSSF FSM shall transit to the state "Idle". The SGSN or VMSC shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI.
10.1.12.7 Operations gsmSCF🡪smsSSF
In this case the smsSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state.
10.1.12.8 Operations gprsSSF 🡪gsmSCF
If the CAP Operation is sent by the gprsSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error, the gprsSSF FSM shall transit to the state "Idle". The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI.
10.1.12.9 Operations gsmSCF🡪gprsSSF
In this case the gprsSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state.
10.1.13 UnexpectedDataValue
10.1.13.1 General description
10.1.13.1.1 Error description
The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot execute the requested CAP Operation because a parameter has an unexpected data value.
Note that this error does not overlap with "ParameterOutOfRange".
EXAMPLE: startTime DateAndTime ::= — value indicating January 32 1993, 12: 15: 01
The responding entity does not expect this value and responds with Error "UnexpectedDataValue".
10.1.13.2 Operations gsmSCF🡪gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.13.3 Operations gsmSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.13.4 Operations gsmSCF🡪gsmSRF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.13.5 Operations gsmSRF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.13.6 Operations smsSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.13.7 Operations gsmSCF🡪smsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.13.8 Operations gprsSSF 🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.13.9 Operations gsmSCF🡪gprsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14 UnexpectedParameter
10.1.14.1 General description
10.1.14.1.1 Error description
The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that there is an error in the received CAP Operation argument. A valid but unexpected parameter was present in the CAP Operation argument. The presence of this parameter is not consistent with the presence of the other parameters. The responding entity cannot start the execution of the CAP Operation.
10.1.14.2 Operations gsmSCF🡪gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14.3 Operations gsmSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14.4 Operations gsmSCF🡪gsmSRF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14.5 Operations gsmSRF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14.6 Operations smsSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14.7 Operations gsmSCF🡪smsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14.8 Operations gprsSSF 🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.14.9 Operations gsmSCF🡪gprsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.15 UnknownLegID
10.1.15.1 General description
10.1.15.1.1 Error description
The gsmSSF uses this error to indicate to the gsmSCF that a specific leg, indicated by the LegID parameter value in the CAP Operation, is unknown to the gsmSSF.
10.1.15.2 Operations gsmSCF🡪gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.16 UnknownCSID
10.1.16.1 General description
10.1.16.1.1 Error description
The gsmSSF uses this error to indicate to the gsmSCF that a specific Call Segment, indicated by the callSegmentID parameter value in the CAP Operation, is unknown to the gsmSSF.
10.1.16.2 Operations gsmSCF🡪 gsmSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.17 UnknownPDPID
10.1.17.1 General description
10.1.17.1.1 Error description
The gsmSCF or gprsSSF uses this error to indicate that a specific PDP Context, indicated by the PDPId parameter value in the CAP Operation argument, is unknown to the receiving entity.
10.1.17.2 Operations gprsSSF🡪gsmSCF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.1.17.3 Operations gsmSCF🡪gprsSSF
Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures.
10.2 Entity related error procedures
The following subclauses specify the error handling procedures for the Functional Entity related errors. Since the error situations are not originated by the reception of a CAP Operation, the invoking entity is denoted here as the entity at which the error situation is detected. The responding entity is the entity which receives the error report.
The TC services used for reporting errors are described in clause 14.
10.2.1 Expiration of Tssf
10.2.1.1 General description
10.2.1.1.1 Error description
A timeout has occurred in the gsmSSF, gprsSSF, smsSSF or assisting gsmSSF on the response from the gsmSCF.
10.2.1.2 Procedures gsmSSF🡪gsmSCF
Procedure at the invoking entity (gsmSSF or assisting gsmSSF)
Timeout occurs in gsmSSF on Tssf.
Precondition: gsmSSF FSM state "Waiting_for_Instructions"; or
gsmSSF FSM state "Waiting_for_end_of_User_Interaction"; or
gsmSSF FSM state "Waiting_for_end_of_Temporary_Connection".
Postcondition: gsmSSF FSM state "Idle".
The gsmSSF shall abort the TC dialogue and shall transit to the state "Idle". The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue. For CAMEL dialogues that are established as a result of a CSI, the Default Call Handling parameter is obtained from the CSI. For gsmSCF initiated CAMEL dialogues, the Default Call Handling parameter shall be "ReleaseCall".
The assisting gsmSSF shall abort the TC dialogue and shall transit to the state "Idle". The assisting gsmSSF shall release the temporary connection.
10.2.1.3 Procedures gprsSSF🡪gsmSCF
Procedure at the invoking entity (gprsSSF)
Timeout occurs in gprsSSF on Tssf.
Precondition: gprsSSF FSM state "Waiting_for_Instructions".
Postcondition: gprsSSF FSM state "Idle".
The gprsSSF shall abort the TC dialogue and and the GPRS dialogue and shall transit to the state "Idle". The SGSN shall handle the PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI.
10.2.1.4 Procedures smsSSF🡪gsmSCF
Procedure at the invoking entity (smsSSF)
Timeout occurs in smsSSF on Tssf.
Precondition: smsSSF FSM state "Waiting_for_Instructions".
Postcondition: smsSSF FSM state "Idle".
The smsSSF shall abort the TC dialogue and shall transit to the state "Idle". The MSC or SGSN shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI.
10.2.2 Expiration of Tsrf
10.2.2.1 General Description
10.2.2.1.1 Error description
A timeout has occurred in the gsmSRF on the response from the gsmSCF. The procedures for handling this error are described in ETSI ETS 300 374-1 [24].
10.2.2.2 Procedures description
The procedures for handling this error are described in ETSI ETS 300 374-1 [24].