You may need Encoding Control Notation to
specify that encoding are PER or UPER .
But you may find X.692 may be too complex. Our company
developed a simplified encoding control notation
before the ITU-T ECN became an international standard.
So, we can do that easily with our ASN.1 compiler.
Author Name: Wang Hao
Phone:+86-755-89650628
EMail:[EMAIL PROTECTED]
*****************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or
partial disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the
sender by phone or email immediately and delete it!
*****************************************************************
----- Original Message -----
From: "Zemer Margolin" <[EMAIL PROTECTED]>
To: "ASN1 FORUM (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, November 03, 2004 8:57 PM
Subject: [ASN1] RRC within RANAP
Hi all,
Has anyone here had to decode RRC message nested in the RRC-Container at the RANAP
protocol ?
I have tried to use “CONTAINING” but since RANAP is PER and RRC is UPER it is not such
a good solution.
Thanks for any help
zemer Margolin
Tel: +972-3765-7571
RADCOM
_______________________________________________
ASN1 mailing list
[EMAIL PROTECTED]
http://lists.asn1.org/mailman/listinfo/asn1
_______________________________________________
ASN1 mailing list
[EMAIL PROTECTED]
http://lists.asn1.org/mailman/listinfo/asn1
