Can someone answer to this?

-------- Original Message --------
Subject: ASN.1 help
Date: Fri, 12 Mar 2010 14:47:27 +0700
From: Lazy Boy <longth@neo....>
To: <olivier.dubuisson@oran...>



Dear You.

I’ll appreciate if you can give me a little favor. When I read ASN.1
standard I encounter this following syntax :



*AChBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET
STRING (SIZE (bound.&minAChBillingChargingLength ..
bound.&maxAChBillingChargingLength)) *

* (CONSTRAINED BY {-- shall be the result of the BER-encoded value of
the type -- *

* CAMELAChBillingChargingCharacteristics {bound}*

*}*

*)*

* *

*CAMEL-AChBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::=
CHOICE { *

*            timeDurationCharging     [0] SEQUENCE { *

*            maxCallPeriodDuration    [0] INTEGER (1..864000), *

*                        releaseIfdurationExceeded   [1] BOOLEAN DEFAULT
FALSE, *

*                        tariffSwitchInterval    [2] INTEGER
(1..86400)   OPTIONAL, *

*                        tone        [3] BOOLEAN DEFAULT FALSE, *

*                        extensions       [4] Extensions {bound} OPTIONAL, *

*            ... *

*            } *

* }*



With *minAChBillingChargingLength; maxAChBillingChargingLength *values
are 5 and 177, respectively.



Can you explain how the type above will be encoded complying Basic
Encoding Rules?

The more detailed, the better.



Best regards and thanks a million.

=========== Lazy Boy ==============

Tran Hai Long

staff of System Development Center of NEO SJC

Mail:      longth@neo.... <mailto:longth@neo....>

Web:     neo.com.vn <http://neo.com.vn>

Mobile: 0973989887

Gmail: hlong1604@gmai... <mailto:hlong1604@gmai...>

********* MAKE IT DIFFERENT ********
_______________________________________________
Asn1 mailing list
Asn1@asn1...
http://lists.asn1.org/mailman/listinfo/asn1