Hello,Walkin
Thanks for your message!
Yeah. As you said that I have got the result .H and .CPP file using one
ASN.1 compiler.I copied the ASN notations from these chapters 11.1~11.5
from this spec(UMTS TS 25.331 V5.5.0).Now I am trying employ the
functions generated by this compiler.If thing goes well as you say.It
will be nice.
Another concern is about the "ECN link module for RRC" and "ECN modules
for RRC".I am not clear what is the functionality of this two part.What
purpose or function about this two part?Or what should I utilize them in
my compiler?They are descriped as below:
----------------This is the ECN Link Module from this spec----------
RRC-ECN-Link-Module LINK-DEFINITIONS ::=
BEGIN
IMPORTS
RRC-encodings -- Encoding objects for RRC messages
FROM RRC-Encoding-Definitions;
ENCODE Class-definitions
WITH RRC-encodings
COMPLETED BY PER-BASIC-UNALIGNED
ENCODE PDU-definitions
WITH RRC-encodings
COMPLETED BY PER-BASIC-UNALIGNED
ENCODE InformationElements
WITH RRC-encodings
COMPLETED BY PER-BASIC-UNALIGNED
ENCODE Internode-definitions
WITH RRC-encodings
COMPLETED BY PER-BASIC-UNALIGNED
END
--------------This is the ECN modules for RRC from this spec------
RRC-Encoding-Definitions ENCODING-DEFINITIONS ::=
BEGIN
EXPORTS
RRC-encodings;
RRC-encodings #ENCODINGS ::= {
-- Trailing bits
outer-encoding
}
--**************************************************************
--
-- The trailing bits in all RRC messages shall be ignored
-- (including unknown message contents & unknown extensions).
-- This overrides the default PER behaviour which pads the last
-- octet with zero bits.
--
--**************************************************************
outer-encoding #OUTER ::= {
ENCODER-DECODER {
}
DECODE AS IF {
POST-PADDING encoder-option
}
}
END
Class-definitions-ECN-Module ENCODING-DEFINITIONS ::=
BEGIN
END
PDU-definitions-ECN-Module ENCODING-DEFINITIONS ::=
BEGIN
END
InformationElements-ECN-Module ENCODING-DEFINITIONS ::=
BEGIN
END
Internode-definitions-ECN-Module ENCODING-DEFINITIONS ::=
BEGIN
END
------------------------------------------------------------------------
-
I am a newer to ASN.1.Any inconvinience ,I am sorry for that.
Regards
Samuel Zhao
-----Original Message-----
From: Lev Walkin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 29, 2005 9:59 AM
To: ZHAO,CHAO (A-China,ex2)
Cc: [email protected]
Subject: Re: [ASN1] ASN.1 file request for spec UMTS RRC TS 25.331
V5.5.0
[EMAIL PROTECTED] wrote:
> Hello,Friends
>
> For one project about UMTS RRC/NAS protocol interpreter,I need the
> ASN.1 file to comile to get C++ support files for my IDE VC++6.0.My
> current solution is that I copy the ASN notation from this spec and
> paste into one plain text file and create one asn file by myself.After
> some error checking I got the H/CPP file.But I am not sure whether
> this is a correct one to use.I find that maybe there are some spelling
> mistakes or other formatting issues in UMTS Spec.So here does anyone
> can provide such a file for this spec?I will be appreciated.
If the ASN.1 to C++ compiler went all the way through the parsing and
code generation stages to produce the .h and .cpp files, it is almost
certainly a clear indication that the original ASN.1 specification did
not contain any spelling mistakes and/or formatting issues.
Did you try to compile resulting H/CPP files? How did it go? Did you try
to employ the functions generated by the compiler? What is going against
your expectations? Please describe your concerns more precisely.
--
Lev Walkin
[EMAIL PROTECTED]
_______________________________________________
ASN1 mailing list
[email protected]
http://lists.asn1.org/mailman/listinfo/asn1
