You are here

ANY TIME SUBSCRIPTION INTERROGATION

5 posts / 0 new
Last post
kamal
ANY TIME SUBSCRIPTION INTERROGATION

Hi,
what are the values of the primitiveID of ANY-TIME-SUBSCRIPTION-INTERROGATION operations:
ANY-TIME-SUBSCRIPTION-INTERROGATION-Req
ANY-TIME-SUBSCRIPTION-INTERROGATION-Conf
ANY-TIME-SUBSCRIPTION-INTERROGATION-IND
ANY-TIME-SUBSCRIPTION-INTERROGATION-Resp

i know that ATI-Req=200 but i need the values for ATSI operations

Thanks
kamal

TomiZet
ATI, ATSI

Hi Kamal,

these are MAP service primitives => how they are internally handled is implementation specific... Anyway what 3GPP TS 29.002 specifies is the:
[list]
[*]mapping of these MAP service primitives on the common MAP service primitives and further mapping of these on the TCAP, SCCP primitives
[*]ASN.1 definitions of MAP service primitives using BER - i.e. data representation on the external interface between MAP entities
[/list]

Here are the ASN.1 definitions for ATI and ATSI. ATI has opcode 71, ATSI has opcode 62.

anyTimeInterrogation OPERATION ::= { --Timer m
ARGUMENT
AnyTimeInterrogationArg
RESULT
AnyTimeInterrogationRes
ERRORS {
systemFailure |
ati-NotAllowed |
dataMissing |
unexpectedDataValue |
unknownSubscriber}
CODE local:71 }


anyTimeSubscriptionInterrogation OPERATION ::= { --Timer m
ARGUMENT
AnyTimeSubscriptionInterrogationArg
RESULT
AnyTimeSubscriptionInterrogationRes
ERRORS {
atsi-NotAllowed |
dataMissing |
unexpectedDataValue |
unknownSubscriber |
bearerServiceNotProvisioned |
teleserviceNotProvisioned |
callBarred |
illegalSS-Operation |
ss-NotAvailable |
informationNotAvailable}
CODE local:62 }

kamal
Hello, in which cases the

Hello,
in which cases the following error is returned atsi-NotAllowed?

Thanks
kamal

thanks

TomiZet
I could not find this in

I could not find this in 29.002 - so I guess it is implementation specific.. Anyway what could be likely the idea behind - I think ATSI indication are checked for originating SCCP GT and if it is not found in the white-list your ATSI request gets discarded or you get back this MAP user errorr. This would be to prevent situation when unknown 3rd party could fetch subscription information from HLR without some kind of NDA.

kamal
Thanks for the clarifications

Thanks for the clarifications

thanks