MT Operation in VMSC

MT operation in VMSC
Page 1 of 6
SMS resending In handover cases the MSC notices that a handover occurred and sets a new timer supervision that is greater than the one in the MS. The SMS resending is performed only after the supervision time has exceeded, because it is possible that the MS has not received the first CP-DATA message at all. The following logical timers are presented in the message sequences listed below:
T1 T2 T5 T6 Supervision for CP-ACK message when CP-DATA message is sent. It is calculated from the SMS length, and varies between 3 - 20 seconds. The overall supervision time for the total SM transfer. The time period after which the MS is likely to have received the CP-DATA message. It is calculated from the SM length and varies between 1 - 15 seconds. If a handover is received during this time, timer T1 is set again in order to see whether the MS received the first CP-DATA message. If a handover is received during a time period after which the MS is likely to have received the CP-DATA message, this guard timer is set before the CP-DATA message is resent. This may happen after the T5 has expired.
The following figure shows a case where a handover takes place after the MS has received the CP-DATA message, and the MSC delays the SM resending. The result is that no duplication is made as the MS has time to acknowledge this with the CP-ACK message:
http://127.0.0.1:43231/NED/NED?service=printview&library=a25001a0001b0040376p1... 11-11-2012
Page 2 of 6
Figure 62: 1. 2. 3. 4. 5. 6.
MT-SM in the MCS, channel handover, no SM resending
The MSC sends an MT-SM to an MS in the CP-DATA message. The MS receives the MT-SM and begins to store it. The MSC is notified about the handover. The 10 second timer is started in the MS before the CP-ACK message is resent. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that the MT-SM has been acknowledged by the MS.
The following figure shows a case where a handover takes place after the MS has received the CP-DATA message, and the MSC delays the SMS resending. The CP-ACK message sent by the MS is lost and will be resent:
Page 3 of 6
Figure 63: 1. 2. 3. 4. 5. 6. 7. 8.
MT-SM in the MSC, channel handover, SM resending takes place
The MSC sends an MT-SM to an MS within the CP-DATA message. The MS receives the MT-SM and begins to store it. The MSC is notified about the handover. Supervision timer T6 expires. The SM resending takes place. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that the MT-SM has been acknowledged by the MS.
The following figure shows a case where a handover takes place before the MS has received CP-DATA message, and the MSC resets timer T1, thus delaying the resending of CP-DATA message:
Page 4 of 6
Figure 64: 1. 2. 3. 4. 5.
MT-SM in the MSC, channel handover, SM resending takes place
The MSC sends an MT-SM to the MS within the CP-DATA message. SMS resending takes place. Timer T1 expires, resulting in SM resending. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that MT-SM has been acknowledged by the MS.
The following figure shows a case where no handover takes place, but the MS does not reply at all. T1 expires, which results in the SM resending:
Page 5 of 6
Figure 65: 1. 2. 3. 4. 5.
MT-SM in the MSC, T1 expires, SM resending takes place
The MSC sends an MT-SM to the MS within the CP-DATA message. SM resending takes place. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that the MT-SM has been acknowledged by the MS.
Values for timers The MSC has the timeout supervision T1 for CP-ACK. The timeout is calculated from the SM length according to the following rules: Channel type is SACCH: (SMS_LENGTH/18)*0.96 sec + 6 sec + delta
Page 6 of 6
Channel type is SDCCH: (SMS_LENGTH/20)*0.24 sec + 3 sec + delta If CP-ACK is not received during the time calculated on the basis of the channel type and SM length, it will be resent. Resending counts may vary from 1 to 3. Counts and timer delta values can be set in Parameter File (PRFILE), Class 31. In practice, timer T1 varies from 3.3 to 15 seconds, and SMS_LENGTH in the A interface from 33 to 172 octets. Timer T5 is related to T1, it is the part of T1 used for sending CP-DATA to the MS when T1 includes also the CP-ACK sent by the mobile station. Therefore T5 is estimated to be T1 - 5 seconds in SACCH channel, and T1 - 2 in SDCCH channel. Timer T6 is derived from the MS resending timer. In the MS the timer value is 10 seconds, therefore the MSC has the value of 13 seconds. Timer T2 is the maximum time that can be left for the A interface signalling. When the SM arrives through the MAP interface to the MSC, the maximum timeout in the SMS-GMSC for sending the MT-SM is 60 seconds. The 58 second timer is set for the VMSC MAP, and the 55 second time is left for the A interface. You can find an estimate of the worst case for T2 below: If a handover takes place at the latest point when the resending is possible, the time is Start + T1 (that is, 15 s). The next step is to start resending the guard timer T6. T6 is 13 seconds (in MS 10 seconds, in MSC a margin of 3 seconds must be added). T6 expires, and resending takes place. T1 is started again, the time now is Start + T1 + T6 (that is, 15 + 13 s). The MS gives an acknowledgement just before T1 expires, the time now is Start + T1 + T6 + T1 (that is, 15 + 13 + 15 s). If you want to make sure that a duplication exists, prepare to wait for responses for a long time. Here the total time would be 43 seconds, and that does not include MS paging, authentication, and what needs to be done before beginning to send an MT-SM. Also check when resending is possible, that is, how much time has already been consumed by comparing the present time with the time left in T2. For example, if several handovers take place, each of which causes T6 to be reset, there are 14 seconds left in T2 at the point when the last handover takes place, and T1 is calculated to be 15 seconds, stop the SM transfer. The reason for the interruption is that the time left would probably not be sufficient. For more information, see VMSC and VLR. For more information, see VMSC and VLR.
Id: 0900d805807df9b8
2011/5/25 Nokia Siemens Networks

MT Operation in VMSC

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MT Operation in VMSC

Uploaded by

Copyright:

Available Formats

MT operation in VMSC

MT-SM in the MCS, channel handover, no SM resending

MT-SM in the MSC, channel handover, SM resending takes place

MT-SM in the MSC, channel handover, SM resending takes place

MT-SM in the MSC, T1 expires, SM resending takes place

2011/5/25 Nokia Siemens Networks

You might also like