[OSS_ASN1] [ASN1] ASN.1 Parameterized Types... pls help

[Casper]

Hi William,

 

Thanks for the advice.

 

This is for a R&D project. We plan to look at the feasibility of using
Erlang/OTP platform for development. Currently doing investigation on ASN.1
compiler on Erlang. I'm very new to ASN.1, so find it difficult to capture
some parts of the specification. The GSM/UMTS MAP ASN.1 spec is alright. But
I couldn't still figure out how to use TCAP ASN.1 spec can generate the TCAP
Begin, Continue, End, etc message encoding/decoding functions.

 

With help from some generous people out there, I could understand that I
will have to create the ASN.1 spec of mine or find a standard spec, which
will Instantiate the Parameterized Type specified in the TCAP. If you could
point me to a standard spec like that or give me a sample how I could write
something like that, would be very helpful. How to blend the MAP and TCAP
ASN.1 specs?

 

Thanks!

Eranga

 

 

 

  _____  

From: William H. Skelton [mailto:W.Skelton@REDACTED] 
Sent: Friday, October 01, 2004 3:12 AM
To: casper2000a@REDACTED
Subject: Fwd: [OSS_ASN1] [ASN1] ASN.1 Parameterized Types... pls help

 

Hi Eranga,

We found you can avoid some of the problems by using earlier TCAP
specifications, which are fully compatible (I think), but simpler.

Just as a matter of interest, is this a commercial or university project you
are working on?  Are you building your own tools?

William



Delivered-To: 23-asn1@REDACTED
From: "Casper" <casper2000a@REDACTED>
To: <asn1@REDACTED>, <erlang-questions@REDACTED>
Date: Wed, 29 Sep 2004 18:07:45 +0600
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcShiZSqLDE2KawuRfKjOPNw8+D0LwEkgVVg
cc: eranga@REDACTED
Subject: [OSS_ASN1] [ASN1] ASN.1 Parameterized Types... pls help
X-BeenThere: asn1@REDACTED
X-Mailman-Version: 2.1.1
List-Id: The ASN.1 Mailing List <asn1.asn1.org>
List-Unsubscribe: <http://lists.asn1.org/mailman/listinfo/asn1>,
        <mailto:asn1-request@REDACTED?subject=unsubscribe
<mailto:asn1-request@REDACTED%3Fsubject=unsubscribe> >
List-Archive: <http://http://dreammark.com/pipermail/asn1
<http://http:/dreammark.com/pipermail/asn1> >
List-Post: <mailto:asn1@REDACTED>
List-Help: <mailto:asn1-request@REDACTED?subject=help
<mailto:asn1-request@REDACTED%3Fsubject=help> >
List-Subscribe: <http://lists.asn1.org/mailman/listinfo/asn1>,
        <mailto:asn1-request@REDACTED?subject=subscribe
<mailto:asn1-request@REDACTED%3Fsubject=subscribe> >
X-Sender: asn1-bounces@REDACTED
X-Errors-To: asn1-bounces@REDACTED
Sender: oss_asn1-owner@REDACTED
Reply-To: oss_asn1@REDACTED
X-RCPT-TO: net.com

Hi All,
 
I'm finding difficult in absorbing "How to use ASN.1 TCAPMessage to
transport GSM MAP". The problem is how to generate TCAP Begin, Continue,
End, etc messages.
 
I read about the ASN.1 Parameterized Type, but still I could find the match
of ASN.1 specs for MAP and TCAP. I thought below might be the way, but still
that gives some compilation errors.
 
mapSpecificAS ABSTRACT-SYNTAX ::= {
  MapSpecificPDUs
  IDENTIFIED BY  gsm-MessagingId
}
 
MapSpecificPDUs ::=
  TCMessage{{ MAPOperations-Invokable}, { MAPOperations-Returnable}}
 
 
MAPOperations-Invokable OPERATION ::= 
      {sendRoutingInfoForSM | mo-ForwardSM | mt-ForwardSM} 
MAPOperations-Returnable OPERATION ::= 
      {reportSM-DeliveryStatus | alertServiceCentre | informServiceCentre |
readyForSM}
 
The error is as below (Erlang ASN.1 compiler),
      {error,{asn1,[{error,{type,57,
                           'TCAPMessages',
                           'MapSpecificPDUs',
                           {asn1,{duplicates_of_the_tags,
                                     [{'UNIVERSAL','INTEGER'}]}}}}]}}
 
For your information, I have attached TCAPMessages.asn and
MAP-ShortMessageServiceOperations.asn.
 
I appreciate if anybody out there can give me some clue to solve this
problem.
 
Thanks in advance!
Eranga


_______________________________________________
ASN1 mailing list
ASN1@REDACTED
http://lists.asn1.org/mailman/listinfo/asn1

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20041001/4d471ff6/attachment.htm>