Hi again,
Attached to this mail you can find a more practical example of what I believe is the correct flow of primitives in a real-world location updating procedure between a SGSN (or MSC) and the HLR.
As you can see, there are two linked invocations/transactions:
1) the actual location updating request (SGSN/MSC -> HLR) 2) the 'insert subscriber data' transaction that is triggered (HLR -> SGSN) 3) the complation of the location updating request after the insert subscriber data has been completed.
It's actually quite "impressive" to see how much needs to happen for such a relatively simple task.
The MAP-DELIMITER.ind is generated locally by the MAP-provider to the map user to indicate that it has finished sending all primitives for one incoming TCAP message/packet/pdu. It is used as a means of synchronization, to which the MAP-User then typically responds with a MAP-DELIMITER.req which in turn triggers the transmission of all queued primitives in a response message.
Regards, Harald