1-- Generated by Asnp, the pretty-printer of France Telecom R&D (http://asn1.elibel.tm.fr/asnp/) 2-- Module TCAPMessages (Q.773:06/1997) 3-- asn1ct:compile("TCAPMessages",[ber_bin]). 4TCAPMessages {itu-t recommendation q 773 modules(2) messages(1) version3(3)} 5 6DEFINITIONS IMPLICIT TAGS 7 8::= 9 10BEGIN 11 12-- EXPORTS everything 13-- Transaction Portion fields. 14IMPORTS 15 ROS{}, InvokeId 16 FROM Remote-Operations-Generic-ROS-PDUs {joint-iso-itu-t 17 remote-operations(4) generic-ROS-PDUs(6) version1(0)} 18 OPERATION 19 FROM Remote-Operations-Information-Objects {joint-iso-itu-t 20 remote-operations(4) informationObjects(5) version1(0)} 21 Supported-MAP-Operations 22 FROM MAP-Protocol {itu-t identified-organization (4) etsi (0) mobileDomain (0) 23 gsm-Network (1) modules (3) map-Protocol (4) version9 (9)} 24-- Start - Added by Eranga 25 dialogue-as-id 26 FROM DialoguePDUs {itu-t recommendation q 773 modules(2) dialoguePDUs(2) 27 version1(1)} 28 sendRoutingInfoForSM, 29 mo-ForwardSM, 30 mt-ForwardSM, 31 reportSM-DeliveryStatus, 32 alertServiceCentre, 33 informServiceCentre, 34 readyForSM 35 FROM MAP-ShortMessageServiceOperations { 36 itu-t identified-organization (4) etsi (0) mobileDomain (0) 37 gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) 38 version9 (9)} 39 gsm-MessagingId 40 FROM MobileDomainDefinitions { 41 itu-t identified-organization (4) etsi (0) mobileDomain (0) 42 mobileDomainDefinitions (0) version1 (1)} 43 Supported-MAP-Operations 44 FROM MAP-Protocol { 45 itu-t identified-organization (4) etsi (0) mobileDomain (0) 46 gsm-Network (1) modules (3) map-Protocol (4) version9 (9)} 47-- End - Added by Eranga 48; 49 50-- Start - Added by Eranga 51 52mapSpecificAS ABSTRACT-SYNTAX ::= { 53 MapSpecificPDUs 54 IDENTIFIED BY gsm-MessagingId 55} 56 57MapSpecificPDUs ::= 58 TCMessage{{MAPOperations-Invokable}, {MAPOperations-Returnable}} 59 60 61MAPOperations-Invokable OPERATION ::= 62 {sendRoutingInfoForSM | mo-ForwardSM | mt-ForwardSM} 63MAPOperations-Returnable OPERATION ::= 64 {reportSM-DeliveryStatus | alertServiceCentre | informServiceCentre | readyForSM} 65 66-- End - Added by Eranga 67 68 69TCMessage{OPERATION:Invokable, OPERATION:Returnable} ::= CHOICE { 70 unidirectional [APPLICATION 1] Unidirectional{{Invokable}, {Returnable}}, 71 begin [APPLICATION 2] Begin{{Invokable}, {Returnable}}, 72 end [APPLICATION 4] End{{Invokable}, {Returnable}}, 73 continue [APPLICATION 5] Continue{{Invokable}, {Returnable}}, 74 abort [APPLICATION 7] Abort 75} 76 77Unidirectional{OPERATION:Invokable, OPERATION:Returnable} ::= SEQUENCE { 78 dialoguePortion DialoguePortion OPTIONAL, 79 components ComponentPortion{{Invokable}, {Returnable}} 80} 81 82Begin{OPERATION:Invokable, OPERATION:Returnable} ::= SEQUENCE { 83 otid OrigTransactionID, 84 dialoguePortion DialoguePortion OPTIONAL, 85 components ComponentPortion{{Invokable}, {Returnable}} OPTIONAL 86} 87 88End{OPERATION:Invokable, OPERATION:Returnable} ::= SEQUENCE { 89 dtid DestTransactionID, 90 dialoguePortion DialoguePortion OPTIONAL, 91 components ComponentPortion{{Invokable}, {Returnable}} OPTIONAL 92} 93 94Continue{OPERATION:Invokable, OPERATION:Returnable} ::= SEQUENCE { 95 otid OrigTransactionID, 96 dtid DestTransactionID, 97 dialoguePortion DialoguePortion OPTIONAL, 98 components ComponentPortion{{Invokable}, {Returnable}} OPTIONAL 99} 100 101Abort ::= SEQUENCE { 102 dtid DestTransactionID, 103 reason CHOICE {p-abortCause P-AbortCause, 104 u-abortCause DialoguePortion} OPTIONAL 105} 106 107-- NOTE - When the Abort Message is generated by the Transaction sublayer, a p-Abort Cause may be 108-- present. The u-abortCause may be generated by the component sublayer in which case it is an ABRT 109-- APDU, or by the TC-User in which case it could be either an ABRT APDU or data in some user-defined 110-- abstract syntax. 111DialoguePortion ::= [APPLICATION 11] EXPLICIT EXTERNAL 112 113-- The dialogue portion carries the dialogue control PDUs as value of the external data type. The direct 114-- reference should be set to {itu-t recommendation q 773 as(1) dialogue-as(1) version1(1)} if structured 115-- dialogue is used and to {itu-t recommendation q 773 as(1) unidialogue-as(2) version1(1)} if unstructured 116-- dialogue is used. 117OrigTransactionID ::= [APPLICATION 8] OCTET STRING(SIZE (1..4)) 118 119DestTransactionID ::= [APPLICATION 9] OCTET STRING(SIZE (1..4)) 120 121P-AbortCause ::= [APPLICATION 10] INTEGER { 122 unrecognizedMessageType(0), unrecognizedTransactionID(1), 123 badlyFormattedTransactionPortion(2), incorrectTransactionPortion(3), 124 resourceLimitation(4)}(0..127) 125 126-- COMPONENT PORTION. The last field in the transaction portion of the TCAP message is the 127-- component portion. The component portion may be absent. 128ComponentPortion{OPERATION:Invokable, OPERATION:Returnable} ::= 129 [APPLICATION 12] 130 SEQUENCE SIZE (1..MAX) OF Component{{Invokable}, {Returnable}} 131 132-- Component Portion fields 133-- Recommendation X.880 defines four Application Protocol Data Units (APDUs) for invoking 134-- operations, returning results or error, and for the rejection of invalid PDUs. 135-- TCAP adds returnResultNotLast to allow for the segmentation of a result. 136Component{OPERATION:Invokable, OPERATION:Returnable} ::= CHOICE { 137 basicROS ROS{{TCInvokeIdSet}, {Invokable}, {Returnable}}, 138 returnResultNotLast 139 [7] returnResult < ROS{{TCInvokeIdSet}, {Invokable}, {Returnable}} 140} 141 142TCInvokeIdSet ::= InvokeId(WITH COMPONENTS { 143 present (-128..127) 144 }) 145 146END -- TCAPMessages 147 148-- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D 149 150