Difference between revisions of "My ASN.1 Notes"
Jump to navigation
Jump to search
m (→Nice examples) |
m (TBCD) |
||
| Line 11: | Line 11: | ||
[https://stackoverflow.com/questions/3296761/i-need-an-example-to-understand-implicit-tagging-in-asn-1/30608283#30608283 Example to understand IMPLICIT tagging] | [https://stackoverflow.com/questions/3296761/i-need-an-example-to-understand-implicit-tagging-in-asn-1/30608283#30608283 Example to understand IMPLICIT tagging] | ||
== TBCD == | |||
[https://www.obj-sys.com/docs/asn2txt/v23x/HTML/ch03s03.html Telephony Binary-Coded Decimal] strings are not part of the ASN.1 standard, but their use is prevalent in many telephony-related ASN.1 specifications. | |||
Conversion of these types into standard numeric text strings is supported by Objective Systems software. | |||
In general, BCD strings pack two numeric digits into a single byte value by using a four-bit nibble to hold each digit. By convention, the digits are reversed in TBCD strings, but there are no official standards for this encoding. | |||
== My Notes == | == My Notes == | ||
Revision as of 10:24, 23 July 2018
Resources
Nice examples
Example explaining CHOICE tagging
Example to understand IMPLICIT tagging
TBCD
Telephony Binary-Coded Decimal strings are not part of the ASN.1 standard, but their use is prevalent in many telephony-related ASN.1 specifications.
Conversion of these types into standard numeric text strings is supported by Objective Systems software.
In general, BCD strings pack two numeric digits into a single byte value by using a four-bit nibble to hold each digit. By convention, the digits are reversed in TBCD strings, but there are no official standards for this encoding.