Hi, I am working with implementing a new IE that is included in the Insert Subscriber Data message (from the HLR to the SGSN). The attribute is called "APN-OI-Replacement" and is a a part of the GPRSSubscriptionData sequence. I am pasting the ASN.1 below: (from 29.002) GPRSSubscriptionData ::= SEQUENCE { completeDataListIncluded NULL OPTIONAL, -- If segmentation is used, completeDataListIncluded may only be present in the -- first segment of GPRSSubscriptionData. gprsDataList [1] GPRSDataList, extensionContainer [2] ExtensionContainer OPTIONAL, ..., apn-oi-Replacement [3] APN-OI-Replacement OPTIONAL -- this apn-oi-Replacement refers to the UE level apn-oi-Replacement. } Now the issue I have is this. Since the the gprsDataList attribute is not marked as optional, it MUST be present in the ISD for it to be properly decoded. In the case of a multiple ISD (when the ISD is split up into multiple chunks) and in the particular case where the ISD is split up such that the gprsDataList goes in the first ISD, while the apn-oi-Replacement is in the second ISD, then the second ISD appears as malformed in wireshark. (because wireshark thinks we are sending the APN-OI-Replacement without the mandatory gprsDataList). My question to the readers here is this: - Is this really a problem in the real network? Would an SGSN understand that the second ISD was part of a sequence and accept it as such? - Do you think there is any solution to this? The breakup into multiple ISD's might occur at different boundaries depending on the TCAP and other settings. Any suggestions? Thanks. asked 28 Jul '15, 09:52 Abelli |
I'm not sure I understand, shouldn't that be one is message split in several tcap or sctp chunks?
Sorry I used the wrong term. It is several tcap messages. Not SCTP chunks.