You are on page 1of 2

Transaction Capabilities Application Part - Wikipedia, the free encyclopedia

Page 1 of 2

Transaction Capabilities Application Part


From Wikipedia, the free encyclopedia

Transaction Capabilities Application Part, from ITU-T recommendations Q.771-Q.775 or ANSI T1.114 is a protocol for Signalling System 7 networks. Its primary purpose is to facilitate multiple concurrent dialogs between the same sub-systems on the same machines, using Transaction IDs to differentiate these, similar to the way TCP ports facilitate multiplexing connections between the same IP addresses on the Internet. TCAP is used to transport INAP in Intelligent Networks and MAP in mobile phone networks.

SS7 protocol suite


OSI Layer Application SS7 Protocols INAP, MAP, IS-41... TCAP, CAP, ISUP, ... Network MTP Level 3 + SCCP MTP Level 2 MTP Level 1

TCAP messages are sent over the wire between machines. TCAP primitives are sent between the application and the local TCAP stack, all TCAP messages are primitives but there are primitives that are not messages, i.e. some are only transferred inside the local machine. A TCAP primitive is made up of one or more TCAP components. An ITU-T TCAP primitive may be one of the following types: Unidirectional A single primitive with no subsequent primitives. Sometimes referred to as a Notice. Begin Continue End Abort Cancel Start a dialog, further primitives will follow. Send a subsequent primitive on an existing dialog, further primitives will follow. The last primitive on an existing dialog, Close an existing dialog. An error has caused the dialog to close. The invoke timer has expired without a response being received (this is a primitive but not a message)

Data link Physical

A Begin primitive has an Originating Transaction ID (up to 4 bytes). Continues have an Originating Transaction ID and a Destination Transaction ID. Ends and Aborts only have a Destination Transaction ID. Each primitive has both an optional component and (required) dialogue portions. The component portion for the unidirectional primitive is mandatory. The dialogue portion carries dialogue or unidialogue control PDUs. For MAP and INAP, dialogue PDU is used which performs establishment and release of dialogues for the application context provided in the primitives. Following primitives are defined for the dialogue PDU: AARQ Dialogue request. For MAP and INAP, AARQ is sent in the Begin primitive with the Invoke component in general, with the application context of MAP/INAP operation's package.

AARE Dialogue response. Sent in response to AARQ in either Continue or End primitives. ABRT Dialogue abort. Each ITU-T TCAP component may be one of the following types: Invoke Return Result Last Return Error Reject A new operation is being requested, this may or may not solicit a response A final response to an Invoke An error occurred Component is rejected for some reason like duplicate invocation, unrecognized linked id, unrecognized operation or mistyped argument

Return Result Not Last A response to an Invoke, further responses will be sent

Invoke components have a signed 7 bit InvokeID which is present in all the other components to identify which invoke they relate to. TCAP can be regarded as light weight implementation of the OSI defined ROSE, Remote Operations Services Element protocol

Contents
1 Transaction ID 2 Invoke ID 3 Decoded TCAP Message 4 External links

Transaction ID
The transaction ID is a TCAP reference for a set of TCAP operations that are performed within a single dialog. When machine A starts a TCAP dialog with another machine B, the machine A sends a Begin message to machine B. This Begin message contains an Originating Transaction ID, which is the Transaction ID reference for A. When the machine B replies to A with a Continue message it includes A's Transaction ID as the Destination Transaction ID. Furthermore B includes its own Transaction ID as the Originating Transaction ID. As the TCAP dialog goes on each Continue message includes the Transaction ID of the destination machine as the Destination Transaction ID and the Transaction ID of the originating machine as the Originating Transaction ID. When any of the machines wants to close the dialog it sends an End message or an Abort message to the other machine. This message contains the Destination Transaction ID only.

Invoke ID
Invoke ID is a TCAP reference for a specific TCAP operation.

Decoded TCAP Message


This is a MO-SMS sent by a MAP layer and the hex stream is taken from TCAP layer.

62744804000200306b1a2818060700118605010101a00d600ba1090607040000010019026c50a14e02010102012e3046800570314244448406a1709192555504352f0900709792622304009020118 According to tag length values, this can be decoded as below.

http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part

5/8/2011

Transaction Capabilities Application Part - Wikipedia, the free encyclopedia

Page 2 of 2

| '--> 62|74 <- Start of Tcap begin message | '--> 48|04:00 02 00 30 <- Transaction ID | '--> 6B|1A <- Start of Dialog portion | '--> 28|18 | '--> 06|07:00 11 86 05 01 01 01 | '--> A0|0D | '--> 60|0B | '--> A1|09 | '--> 06|07:04 00 00 01 00 19 02 <- Application context | '--> 6C|50 <- Start of component portion | '--> A1|4E | '--> 02|01:01 <- Component Id (invoke id) | '--> 02|01:2E <- Operation Code | '--> 30|46 <- Start of parameter buffer | '--> 80|05:70 31 42 44 44 <- SM-RP-DA(BCD) | '--> 84|06:A1 70 91 92 55 55 <- SM-RP-OA(BCD) | '--> 04|35:2F 09 00 70 97 92 62 23 04 00 90 20 11 80 01 24 00 27 43 50 7A 0E A2 A3 CB 20 71 79 4E 07 B1 C3 EE 73 3D 7C 2E 83 D2 20 74 D8 5E 06 95 ED 65 39 68 5E

External links
ITU-T Recommendation Q.773: Transaction capabilities formats and encoding TCAP ASN1 specification Retrieved from "http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part" Categories: Signaling System 7 | ITU-T recommendations This page was last modified on 1 February 2011 at 12:03. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of Use for details. Wikipedia is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part

5/8/2011

You might also like