TCAP:Transaction - Revision history

Allyntree at 19:38, 24 April 2018

2018-04-24T19:38:46Z

← Older revision		Revision as of 15:38, 24 April 2018
Line 24:		Line 24:
	*[[TCAP:Receiving transaction and dialogue portions\|Receive transaction and dialogue portions]]		*[[TCAP:Receiving transaction and dialogue portions\|Receive transaction and dialogue portions]]
	*[[TCAP:Receiving transaction error indication\|Receive transaction error indications]]		*[[TCAP:Receiving transaction error indication\|Receive transaction error indications]]


	~~[[category:Needs revising]]~~

Ktrueman: added links and clean up

2009-09-09T19:47:07Z

added links and clean up

← Older revision		Revision as of 15:47, 9 September 2009
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 ~~message~~ are then sent to peer TCAP/service user upon message assembly completion.		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 ~~Transaction Data Send~~ message is sent by the TCAP service user then received by the TCAP layer.		'''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.

Ktrueman: added links and clean up

2009-09-09T19:43:31Z

added links and clean up

← Older revision		Revision as of 15:43, 9 September 2009
Line 1:		Line 1:
	TCAP service user has to send TCAP ~~message~~ by fragments. All components of a TCAP message ~~have to~~ be sent individually. They are queued until TCAP receives the transaction and dialogue portions. TCAP message are sent to peer TCAP/service user on message assembly completion.		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 message are then sent to peer TCAP/service user upon message assembly completion.


Line 5:		Line 5:


	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.		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.


	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.		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 [[TCAP:Adding component portion\|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.		*To [[TCAP:Sending transaction and dialogue portions\|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.		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.


			== Related actions ==
			*[[TCAP:Creating new transaction\|Create a new transaction]]
			*[[TCAP:Adding component portion\|Add a component portion]]
			*[[TCAP:Sending transaction and dialogue portions\|Send transaction and dialogue portions]]
			*[[TCAP:Receiving component portion\|Receive component portion]]
			*[[TCAP:Receiving transaction and dialogue portions\|Receive transaction and dialogue portions]]
			*[[TCAP:Receiving transaction error indication\|Receive transaction error indications]]


	[[category:Needs revising]]		[[category:Needs revising]]

Ktrueman: clean up

2009-09-08T18:51:49Z

clean up

← Older revision		Revision as of 14:51, 8 September 2009
Line 5:		Line 5:


	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 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 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.		*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 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.		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.

	[[category:Needs revising]]		[[category:Needs revising]]

Ktrueman: initial content

2009-09-08T18:40:31Z

initial content

New page

TCAP service user has to send TCAP message by fragments. All components of a TCAP message have to be sent individually. They are queued until TCAP receives the transaction and dialogue portions. TCAP message are sent to peer TCAP/service user on 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 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.

[[category:Needs revising]]