A TCAP message consists of three parts. The transaction portion is used for the local TCAP and remote TCAP to identify the transaction. The session portion contains the information relevant to the session, including session type and session version. The component portion contains the invoke ID, operation code, and other parameters of the operation.

 The Component sub-layer provides two types of application services: services for the control of end-to-end sessions and services for Remote Operation handling. These services are accessed using the TC-Session handling primitives and TC-Component handling primitives respectively.

 Services for session control include the ability to exchange information related to application-context negotiation, such as TC_Begin_Req 

. Services for Remote Operation handling provide for the exchange of protocol data units invoking tasks (operations), and reporting their outcomes (results or errors), such as TC_INVOKE_Req 

. The Transaction sub-layer provides a simple end-to-end connection association service over which several related protocol data units (i.e. built by the Component Sub-Layer) can be exchanged.

very good document. thanks.

documentation very useful for my job

informative and essential for real time trouble analysis.

useful document, thanks