TCAP:Transaction
(added links and clean up) |
(added links and clean up) |
||
| Line 1: | Line 1: | ||
| − | The [[TCAP]] service user has to send TCAP messages by fragments. All components of a TCAP message must be sent individually. They are queued until TCAP receives the transaction and dialogue portions. TCAP | + | The [[TCAP]] service user has to send TCAP messages by fragments. All [[TCAP:Message#Component portion|components]] of a TCAP message must be sent individually. They are queued until TCAP receives the [[TCAP:Message#Transaction portion|transaction]] and [[TCAP:Message#Dialogue portion|dialogue]] portions. TCAP messages are then sent to peer TCAP/service user upon message assembly completion. |
| − | '''Note:''' No TCAP message is sent on the SS7 network (no transaction occurs) until a | + | '''Note:''' No TCAP message is sent on the [[SS7]] network (no transaction occurs) until a '''transaction data send''' message is sent by the TCAP service user then received by the TCAP layer. |
| + | |||
To [[TCAP:Creating new transaction|create a new TCAP transaction]], send the '''initiate''' message to register a new transaction identifier. When building TCAP messages, the transaction identifier serves to link the different fragments of a TCAP message (i.e. while adding components to TCAP message). It is not required to send the initiate message for already active outgoing and incoming transactions. | To [[TCAP:Creating new transaction|create a new TCAP transaction]], send the '''initiate''' message to register a new transaction identifier. When building TCAP messages, the transaction identifier serves to link the different fragments of a TCAP message (i.e. while adding components to TCAP message). It is not required to send the initiate message for already active outgoing and incoming transactions. | ||
Revision as of 14:47, 9 September 2009
The TCAP service user has to send TCAP messages by fragments. All components of a TCAP message must be sent individually. They are queued until TCAP receives the transaction and dialogue portions. TCAP messages are then sent to peer TCAP/service user upon message assembly completion.
Note: No TCAP message is sent on the SS7 network (no transaction occurs) until a transaction data send message is sent by the TCAP service user then received by the TCAP layer.
To create a new TCAP transaction, send the initiate message to register a new transaction identifier. When building TCAP messages, the transaction identifier serves to link the different fragments of a TCAP message (i.e. while adding components to TCAP message). It is not required to send the initiate message for already active outgoing and incoming transactions.
An active outgoing transaction is a transaction that has been created locally and hasn’t been terminated. An active incoming transaction is a transaction that has been created remotely by peer TCAP/service user and hasn’t been terminated.
- To add components to a previously created TCAP message, use the Transaction Component Add message.
- To add transaction and dialogue portions and activate TCAP message assembling and transmission, use the transaction data send message.
The peer application will receive a transaction data received message then one or more transaction component received messages. The data received indication contains transaction and dialogue portions of TCAP message. The component received indication contains the component portion of a TCAP message. The peer TCAP/service user will receive a component received indication for all components that are part of a TCAP message. The TCAP service user has to match the components and the transaction and dialogue portions using the transaction identifier.
