{"history":[],"article":{"id":"2fc844e1-b10f-47d4-833f-18b280e81632","title":"Transaction Capabilities Application Part","slug":"transaction-capabilities-application-part","content":":::summary\n:::\n\n# \n**Transaction Capabilities Application Part**, from [ITU-T](https://bliptext.com/articles/itu-t) recommendations Q.771-Q.775 or [ANSI](https://bliptext.com/articles/ansi) T1.114 is a protocol for [Signalling System 7](https://bliptext.com/articles/signalling-system-7) networks.\nIts 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](https://bliptext.com/articles/transmission-control-protocol) ports facilitate multiplexing connections between the same [IP addresses](https://bliptext.com/articles/ip-address) on the [Internet](https://bliptext.com/articles/internet).\nTCAP uses [ASN.1](https://bliptext.com/articles/abstract-syntax-notation-one) [BER](https://bliptext.com/articles/x-690) encoding, as well as the protocols it encapsulates, namely [MAP](https://bliptext.com/articles/mobile-application-part) in mobile phone networks or [INAP](https://bliptext.com/articles/inap) in [Intelligent Networks](https://bliptext.com/articles/intelligent-network).\n\n# Overview\nTCAP **messages** are sent over the wire between machines.\nTCAP **primitives** are sent between the application and the local TCAP stack.\nAll TCAP messages are primitives but there are primitives that are not messages.\nIn other words, some are only transferred inside the local machine.\nA TCAP primitive is made up of one or more TCAP components.\nAn ITU-T TCAP primitive may be one of the following types:\nA Begin primitive has an Originating Transaction ID (up to 4 bytes).\nA Continue primitive has an Originating Transaction ID and a Destination Transaction ID.\nEnd and Abort primitives only have a Destination Transaction ID.\nEach primitive has both an optional component and (optional) dialogue portions.\nThe component portion for the unidirectional primitive is mandatory.\nThe dialogue portion carries dialogue or unidialogue control PDUs.\nFor MAP and INAP, dialogue PDU is used which performs establishment and release of dialogues for the application context provided in the primitives.\nFollowing primitives are defined for the dialogue PDU:\nEach ITU-T TCAP component may be one of the following types:\nInvoke components have a signed 7 bit InvokeID which is present in all the other components to identify which invoke they relate to.\nTCAP is based on the OSI defined [ROSE](https://bliptext.com/articles/remote-operations-service-element-protocol), Remote Operations Services Element protocol.\n\n# Transaction ID\nThe transaction ID is a TCAP reference for a set of TCAP operations that are performed within a single dialog.\nWhen machine ****A**** starts a TC****A****P dialog with another machine ****B****, ****A**** sends a ****B****egin message to ****B****.\nThis **Begin** message contains an Originating Transaction ID, which is the Transaction ID reference for **A**.\nWhen machine **B** replies to ****A**** with a **Continue** message, it includes ****A****'s Transaction ID as the Destination Transaction ID.\nFurthermore, **B** includes its own Transaction ID as the Originating Transaction ID.\nAs 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.\nWhen either machine wants to close the dialog, it sends an **End** message or an **Abort** message to the other machine.\nThis message contains the Destination Transaction ID only.\n\n# Invoke ID\nInvoke ID is a TCAP reference for a specific TCAP operation and must be unique within a dialog.\n\n# Decoded TCAP Message\nThis is a MO-SMS sent by a MAP layer and the hex stream is taken from TCAP layer.\n62 74 48 04 00 02 00 30 6B 1A 28 18 06 07 00 11 86 05 01 01 01 A0 0D 60 0B A1 09 06 07 04 00 00\n01 00 19 02 6C 50 A1 4E 02 01 01 02 01 2E 30 46 80 05 70 31 42 44 44 84 06 A1 70 91 92 55 55 04\n35 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 2E BB 01 00\nAccording to tag length values, this can be decoded as below.\n'--> 62|74 <- Start of Tcap begin message\n| '--> 48|04:00 02 00 30 <- Transaction ID\n| '--> 6B|1A <- Start of Dialog portion\n| '--> 28|18 | '--> 06|07:00 11 86 05 01 01 01 | '--> A0|0D\n| '--> 60|0B\n| '--> A1|09\n| '--> 06|07:04 00 00 01 00 19 02 <- Application context\n| '--> 6C|50 <- Start of component portion\n| '--> A1|4E\n| '--> 02|01:01 <- Component Id (invoke id)\n| '--> 02|01:2E <- Operation Code\n| '--> 30|46 <- Start of parameter buffer\n| '--> 80|05:70 31 42 44 44 <- SM-RP-DA(BCD)\n| '--> 84|06:A1 70 91 92 55 55 <- SM-RP-OA(BCD)\n| '--> 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 2E BB 01 <- SM-RP-UI","current_revision":null,"created_by":"kACnuQmH5k9Nr5VNVEpVeg7XpvUmMctD","created_at":"2025-01-25T22:33:52.463Z","updated_at":"2025-01-25T22:33:52.463Z","search_vector":"'applic':3 'capabl':2 'part':4 'transact':1","search_content":" \n \n\n# \n**Transaction Capabilities Application Part**, from [ITU-T](https://bliptext.com/articles/itu-t) recommendations Q.771-Q.775 or [ANSI](https://bliptext.com/articles/ansi) T1.114 is a protocol for [Signalling System 7](https://bliptext.com/articles/signalling-system-7) networks.\nIts 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](https://bliptext.com/articles/transmission-control-protocol) ports facilitate multiplexing connections between the same [IP addresses](https://bliptext.com/articles/ip-address) on the [Internet](https://bliptext.com/articles/internet).\nTCAP uses [ASN.1](https://bliptext.com/articles/abstract-syntax-notation-one) [BER](https://bliptext.com/articles/x-690) encoding, as well as the protocols it encapsulates, namely [MAP](https://bliptext.com/articles/mobile-application-part) in mobile phone networks or [INAP](https://bliptext.com/articles/inap) in [Intelligent Networks](https://bliptext.com/articles/intelligent-network).\n\n# Overview\nTCAP **messages** are sent over the wire between machines.\nTCAP **primitives** are sent between the application and the local TCAP stack.\nAll TCAP messages are primitives but there are primitives that are not messages.\nIn other words, some are only transferred inside the local machine.\nA TCAP primitive is made up of one or more TCAP components.\nAn ITU-T TCAP primitive may be one of the following types:\nA Begin primitive has an Originating Transaction ID (up to 4 bytes).\nA Continue primitive has an Originating Transaction ID and a Destination Transaction ID.\nEnd and Abort primitives only have a Destination Transaction ID.\nEach primitive has both an optional component and (optional) dialogue portions.\nThe component portion for the unidirectional primitive is mandatory.\nThe dialogue portion carries dialogue or unidialogue control PDUs.\nFor MAP and INAP, dialogue PDU is used which performs establishment and release of dialogues for the application context provided in the primitives.\nFollowing primitives are defined for the dialogue PDU:\nEach ITU-T TCAP component may be one of the following types:\nInvoke components have a signed 7 bit InvokeID which is present in all the other components to identify which invoke they relate to.\nTCAP is based on the OSI defined [ROSE](https://bliptext.com/articles/remote-operations-service-element-protocol), Remote Operations Services Element protocol.\n\n# Transaction ID\nThe transaction ID is a TCAP reference for a set of TCAP operations that are performed within a single dialog.\nWhen machine ****A**** starts a TC****A****P dialog with another machine ****B****, ****A**** sends a ****B****egin message to ****B****.\nThis **Begin** message contains an Originating Transaction ID, which is the Transaction ID reference for **A**.\nWhen machine **B** replies to ****A**** with a **Continue** message, it includes ****A****'s Transaction ID as the Destination Transaction ID.\nFurthermore, **B** includes its own Transaction ID as the Originating Transaction ID.\nAs 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.\nWhen either machine wants to close the dialog, it sends an **End** message or an **Abort** message to the other machine.\nThis message contains the Destination Transaction ID only.\n\n# Invoke ID\nInvoke ID is a TCAP reference for a specific TCAP operation and must be unique within a dialog.\n\n# Decoded TCAP Message\nThis is a MO-SMS sent by a MAP layer and the hex stream is taken from TCAP layer.\n62 74 48 04 00 02 00 30 6B 1A 28 18 06 07 00 11 86 05 01 01 01 A0 0D 60 0B A1 09 06 07 04 00 00\n01 00 19 02 6C 50 A1 4E 02 01 01 02 01 2E 30 46 80 05 70 31 42 44 44 84 06 A1 70 91 92 55 55 04\n35 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 2E BB 01 00\nAccording to tag length values, this can be decoded as below.\n'--> 62|74 48|04:00 02 00 30 6B|1A 28|18 | '--> 06|07:00 11 86 05 01 01 01 | '--> A0|0D\n| '--> 60|0B\n| '--> A1|09\n| '--> 06|07:04 00 00 01 00 19 02 6C|50 A1|4E\n| '--> 02|01:01 02|01:2E 30|46 80|05:70 31 42 44 44 84|06:A1 70 91 92 55 55 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 2E BB 01 <- SM-RP-UI","revisionCount":0},"hasMore":false,"nextCursor":null}

History