You are here

Issues in Sending RESULT-NL in response from Peer

4 posts / 0 new
Last post
Issues in Sending RESULT-NL in response from Peer


I have been currently assigned to implement segementation in our MAP stack.

In this regard, my questions are as follows:

1. Should the MAP User send segmented packets or should the MAP stack segement the MAP-XXX-response sent from the MAP User?
2. If MAP stack has to segment the MAP-XXX-Response, then how should this segmentation be done? Should it be done after or before ASN encoding?

Any help on the above would be highly appreciated.

Best Regards,

Re:Segmentation at the MAP application

U need to segment the MAP message in ur appln like send MAP response msg in TC-CONTINUE dialogue primitive and component with RESULT_NL primitive.

Hi Pramod, Thanks for your

Hi Pramod,

Thanks for your reply.

However, my doubt is still not clear.

Can you please explain to me as to how to go about segmenting the message in the application? I mean does this involve partially filling up the structures? If I am doing this at an application level, then how will MAP know that this is a segmented message? i.e. how to indicate to MAP stack that the application wants to send a partial (Result NL) response?

Looking forward to your response. Thanks once again.

It depends on APIs exposed to

It depends on APIs exposed to the application and the FSM maintained.
If MAP stack maintains the FSM and it exposes APIS only to receive and send the operation code and message buffer for particular dialogue.
Then MAP stack should take care of the segmentation.
Based on the size of received buffer from the MAP user , MAP stack can decides the number of segmentation , It should be done before ASN.1 encoding as you are going to send them as RESULT_NL (component) TC_CONTINUE (dialogue) and RESULT_L (component for last segement) with TC_END or TC_CONTINUE (based on user instruction).

If your MAP stack is transparent and it handles only ASN.1 encoding and decoding then segmentation should be handles by MAP user.