You are here

UserInformation encoding

2 posts / 0 new
Last post
cmdcenter
UserInformation encoding

How can I know what the content of [b]UserInformation[/b] section of [b]Dialogue Portion[/b] is? As far as I know it depends on the MAP operation type. I could not just found anywhere how the data should be encoded in it as for each MAP operation. The only thing I know is that its wrapped in one of the [b]single ASN.1-type, octet-aligned [/b]or[b] arbitrary[/b] tags.

Edited by: cmdcenter on 12/19/2011 - 06:12
TomiZet
Please note you do not find

Please note you do not find this in the MAP specification, because MAP service primitives are mapped on the TC primitives - see in 29.002 chapter "General rules for mapping of services onto TC". So you need to check ITU-T Q.773 to find this out. Here is a hexa dump of MAP-User-ABORT - I could not get it in with the indentation so the dump analysis is not fine readable. Anyway if you compare this dump analysis with information from the chapter 4.2.3.1 Dialogue Control PDUs of ITU-T Q.773 it should be clear then...


67 2c 49 04 e0 41 97 13 6b 24 28 22 06 07 00 11 86 05 01 01 01 a0 17 64 15 80 01 00 be 10 28 0e 06 07 04 00 00 01 01 01 01 a0 03 a4 01 80


0x67 -> TC-ABORT
0x2c -> length: 44 bytes
0x49 -> destination TID tag
0x04 -> length: 4 bytes
0xe0419713 -> DTID value
0x6b -> Dialogue portion tag
0x24 -> length: 36 bytes
0x28 -> external tag
0x22 -> length: 34 bytes
0x06 -> Object Identifier Tag
0x07 -> length: 7 bytes
0x00118605010101 -> structured dialogue, ccitt recommendation q 773 as(1) dialogue-as(1) version1(1)
0xa0 -> Single ASN.1-Type Tag
0x17 -> length: 23 bytes
0x64 -> Dialogue Abort Tag
0x15 -> length: 21 bytes
0x80 -> abort source tag
0x01 -> length: 1 byte
0x00 -> dialogue-service-user
0xbe -> user-information tag
0x10 -> length: 16 bytes
0x28 -> MAP-DialogueInformation
0x0e -> length: 14 bytes
0x06 -> map-DialogueAS
0x07 -> length: 7 bytes
0x04000001010101
0xa0 -> MAP-Dialogue-PDU
0x03 -> length: 3 bytes
0xa4 -> map-UserAbortInfo
0x01 -> length: 1 byte
0x80 -> userSpecificReason