Hi Salai, Pl find my comments below Regards Prajnananda Tripathy Telecom Group HCL Technologies Ltd
Disclaimer: This document is intended for transmission to the named recipient only. If you are not that person, you should note that legal rights reside in this document and you are not authorized to access, read, disclose, copy, use or otherwise deal with it and any such actions are prohibited and may be unlawful. The views expressed in this document are not necessarily those of HCL Technologies Ltd. Notice is hereby given that no representation, contract or other binding obligation shall be created by this e-mail, which must be interpreted accordingly. Any representations, contractual rights or obligations shall be separately communicated in writing and signed in the original by a duly authorized officer of the relevant company. -----Original Message----- From: Salai Sivamal.G [mailto:[EMAIL PROTECTED]] Sent: Friday, February 01, 2002 10:54 AM To: [EMAIL PROTECTED] Subject: [ASN.1] Length octets Hi all, I have a doubt regarding Length octets in BER. My question is, How to specify length octets, if it's value is greater than '255'. Because we cannot specify it in a single octet. For Example, I want to specify a Length value as '302'. Can i specify it in two octets, in this case value will be 01 2E. [Prajna] Yes, u can specify the length in two octets in BER.U have to specify this by an integer while writing the message in ASN.1. Here are lengths involved with the TAG field and the LENGTH. If the CONTENT is longer than 127, then the first octet is coded as 128 + n where n are the number of octets that follow to carry the length: Example: 258 octet strings 04 82 0102 ... (258)characters. For constructed types, i.e. whenever the bit 00100000 of the tag is one there is also the possibility to encode the length as undefinete length, for example a SEQUUENCE OF two integer {2,3} 30 06 02 01 02 02 01 03 or 30 80 02 01 02 02 01 03 00 00. U can also refer x.690 standard for more info. U can get some idea about the tagging from this . here. The tag for sms-telser-id is 9f 74. SMSDeliveryPointToPoint ::= --snacc isPdu:"TRUE"--SET { sms-telser-id [116] IMPLICIT SMS-TELSER-ID , } [prajna] T = some value L = 01 2E V = some value while interpreting, the boundry between L and V is not very clear. My mistaken, there is a chance to read only '01' as length and 2E as value. how to avoid this ? It would be really helpful for me if somebady tells the answer. Thanks in advance. -Salai.g www.icope.com
