Difference between revisions of "Components"

Revision as of 15:49, 23 August 2013

This is the main part of the message holding the data specific to each protocol (like MAP, CAMEL, etc.)

There can be zero or more components in a message. Zero components can happen only in an error return message.

<component remoteCID="1" type="Invoke" operationCode="updateLocation">

application-specific

	...
	application-specific
</component>

Parameters:

• type – Type of the TCAP component, may be one of: Invoke, ResultLast, ResultNotLast, U_Error, L_Reject, R_Reject, U_Reject

• localCID – ID for a locally created component. This is mandatory for components that are invoked on the local end. Results will be received with the same parameter.

• remoteCID – ID for a remotely received component. This is designated the ID set by the remote end for the component. Results that are locally sent for this component should contain this parameter.

• operationCode – Code of the requested operation

• errorCode – Code of the returned error if applicable

• problemCode – Code of the encountered problem if applicable

• timeout - Time in seconds to wait for a response

• operationClass - Specify which type of operation this is. It can have one of the following values:
  • reportAll - expects a result, either being a ReturnResult, either a ReturnError.
  • reportFail - expects a result only in case of error or failure.
  • reportSuccess - expects a result only in case of succesful handling.
  • reportNone - does not expect any kind of result.

It is important to note that most components of type Invoke do not wait for an answer and the transaction should be terminated silently as described for TCAP.

The direction of each component is determined by the presence or absence of localCID and remoteCID.

The operation code indicates which operation is requested from the application context. A known code is translated into a keyword, an unknown code is returned in numeric format.