You are here

forced UDT

6 posts / 0 new
Last post
dineshonss7
forced UDT

Hi,

This problem is related to segmentation of MAP User data.

If MAP user sends more than 254 bytes then sccp does segmentation and send it in 2 XUDT but newtork does not supports XUDT it only supports UDT, In this scenario what could be the best solutions as i know that MAP layer does segmentation but any other alternative solutions is there which will force SCCP to send only UDT in case of large data.

Thnx

Edited by: admin on 05/16/2010 - 04:32
pramod
Re: forced UDT

Hi
I dont think there is a solution apart from MAP or TCAP segmentation .

dineshonss7
Re: forced UDT

TCAP spec does not talks about segmentation , we can rely on only MAP regmentation, but MAP provides segmentation for response messages which would be transfer to peer TCAP as RESULT_NL, Do you have any idea about segmentation of request i.e. invoke messages. In ANSI, TCAP supports invoke segmentation so could we use MAP layer over ANSI TCAP as TCAP does not check the user buffer.

Or segmentation has to be taken care by map application layer. If this is the case then what would be the rule and moreover both peer app should aware about the rule.

pramod
Re: forced UDT

TCAP segmentation is just like sending Msg's in CONTINUE primitive
For ex when sending large SMS, wher we can send through multiple CONTINUE Tcap messages .
One more example wher in  case of MAP ,ISD will come in CONTINUE format most of the times..

dineshonss7
Re: forced UDT

Could you tell me who does segmentation for ISD messages it will be at MAP level or
MAP APP level. How the reassembly will happen at other end.

Continue is nothing but delimeter request which instructs TCAP to send data to peer with continuation of dialogue, continue does not says anything about the segmentaion of the messages.

pramod
Re: forced UDT

Did u gone through any time abt ISD msg ..
Its having a lot of fields so in a single TCAP we cant send all those fields to VLR so
HLR ll do the buffer segmentation at MAP level(if ur maintaining dialog at MAP level)
or at TCAP level(if ur maintaining dialog at TCAP level).

this is applicable to SMS if u have an SMS more than 160 char then SMSC ll do the  segmentation and send  ,wher it's the handset responsibility to reassemble all those segments and show as single msg to the user..

for more TCAP,SCCP segmentation u can go through Q series doc related to TCAP,SCCP....