Hi,
I'm working in 3GPP MAP protocol.The spec that I follo is 3GPP TS 29.002
V3.9.0 (2001-06). The ASN1 specification of it has some extensionContainer
(SEQUENCE) type in the definition of some Operation as follows:

authenticationFailureReport OPERATION
   ARGUMENT
      authenticationFailureReportArg SEQUENCE {
         imsi                 OCTET STRING (  SIZE (3 .. 8 ) ), 
         failureCause         ENUMERATED {
            wrongUserResponse        (0 ), 
            wrongNetworkSignature    (1 )}, 


         extensionContainer   SEQUENCE {
            privateExtensionList   [0] IMPLICIT SEQUENCE  (  SIZE (1 .. 10 )
) OF
               SEQUENCE {
                  extId      MAP-EXTENSION .&extensionId  ( {
                     , 
                     ...} ) , 
                  extType    MAP-EXTENSION .&ExtensionType  ( {
                     , 
                     ...} { @extId   }  )  OPTIONAL} OPTIONAL, 
            pcs-Extensions         [1] IMPLICIT SEQUENCE {
               ... } OPTIONAL, 
            ... } OPTIONAL, 
         ... }

   RESULT
      ........
      ........
   ERRORS {
      -- systemFailure -- localValue : 34, 
      -- unexpectedDataValue -- localValue : 36, 
      -- unknownSubscriber -- localValue : 1}
 ::= localValue : 15

Can anybody please tell me shall I have to fill this (extensionContainer)
Sequence , I mean shall I have to encode this if I'm sending a
authenticationFailureReport ARGUMENT to other end? If yes , then what should
be the value of extId and extType??
Because these values are not specified in the spec also.
Actually I'm going to write a set of  APIs for this protocol.The APIs will
be used by the MAP Application.So I need to know whether there should be any
APIs/methods which will take value of these fields from the Application at
the time of encoding of a message and also the reverse at the time of
decoding. 


 thanks in advance,
 --------------- 
 Sudhansu Sabut 
 s/w Engineer 
 Ind-Telesoft Pvt. Ltd 
 104,Koramangala Indl. Estate, Bangalore-560095 
 --------------- 
              

Reply via email to