Dear Mr. Lin:
I suspect that the lack of response to your question is because it is very
application oriented. It is not exactly an ASN.1 question and that's what
this list is for.
I will send you a separate email privately.
=====================================================================
Conrad Sigona Voice Mail : 1-732-302-9669 x400
OSS Nokalva Fax : 1-614-388-4156
[EMAIL PROTECTED] My direct line : 1-315-845-1773
Dear Experts :
I have difficult to make a REAL "unexpected critical message
extension" (quoted from 3GPP TS 25.331 v5.16.0 clause 9.3b) error when
I perform some TTCN conformance tests.
Enclosure is a sample ASN.1 definition file which was delivered from 3GPP.
Let's take the "CellUpdateConfirm" as an example. I try to make a
invalid message which contain an unexpected critical message extension
error. My understanding is that the only thing to do is make the
critical extension part is not comprehended.
The original ASN.1 definition prototype declaration is :
Invalid_CellUpdateConfirm
CHOICE
{
r3 SEQUENCE
{
cellUpdateConfirm_r3 CellUpdateConfirm_r3_IEs,
v3a0NonCriticalExtensions SEQUENCE
{
cellUpdateConfirm_v3a0ext CellUpdateConfirm_v3a0ext,
nonCriticalExtensions SEQUENCE {} OPTIONAL
} OPTIONAL
},
later_than_r3 SEQUENCE
{
rrc_TransactionIdentifier RRC_TransactionIdentifier,
criticalExtensions BIT STRING (SIZE(8)) -- INSTEAD OF SEQUENCE {}
}
}
So I compose this CellUpdateConfirm message as :
cs_InvalidCellUpdateCnfDCCH ( p_IntegrityInfo :
IntegrityCheckInfo; p_RRC_Ti : RRC_TransactionIdentifier )
{
integrityCheckInfo p_IntegrityInfo,
message invalid_cellUpdateConfirm : later_than_r3 :
{
rrc_TransactionIdentifier p_RRC_Ti ,
criticalExtensions 'FF'H
}
}
I simply put the "FF" HexString (or "11111111" BitString also) in the
criticalExtensions field instead of the CHOICE structure.
When I send this invalid message as a constraint which was been
contained in a peer signalling message to the IUT. The IUT doesn't
seem to received any invalid message. I doubt that the invalid message
I compose doesn't really contain a "unexpected critical message
extension". I wonder whether I should put the "FF" HexString in the
deeply criticalExtensions field have the SEQUENCE structure or not ?
Would you please show me the correct example, what exactly is an
"unexpected critical message extension" ? And where can I find any
documentation or introduction about ASN.1 critical extension error
handling ? I already did the search in Google and check some
specifications from ITU and 3GPP but still not luck. :-(
Thanks in advance !!!
Best regards,
Morton Lin.
--
Morton Lin, R&D Engineer
Sunplus Technology Co., Ltd.
AD0130, No.19, Innovation First Road,
Hsinchu Science Park, 300 Taiwan
Tel : 886-3-5786005 ext.3827
Fax : 886-3-6886998
_______________________________________________
Asn1 mailing list
[email protected]
http://lists.asn1.org/mailman/listinfo/asn1
