Anda di halaman 1dari 3

About T200 N200

T200 expiry usually refers to Abis failure, or equipment failure on one end (BTS or BSC). But if it affects the whole network, maybe you should check out your transcoder or your Ater/A interface links. Are those interfaces "over satellite" ? Do you have any alarm in your OMC-R ? T200 expiry means that the LAPD frame is sent from point A to point B on Abis, but without acknowledgment from point B. If the frame is not acknowledged, it means it has not be received. Therefore the point A will retransmit the frame up to N200 times. At N200+1 times, the point A will stop trying --> drop. Now, how many reasons do you for not having an ACK from point B ? A/ either the link is broken, and point B never received the initial data B/ point B is down (or in a faulty state) and doesn't receive/ack the frames. restart your processes on each end, investigate your Abis links, swap your control boards... there is not much you can do. It's either software pb or hardware pb. As said earlier (just read older posts in this thread), it's probably because of : 1/ Abis link failure 2/ Clock/Transmission BTS board failure 3/ Transmission BSC board failure Pick your choice. LapD is the signaling 'link' on the Abis. Basically, it just means that there was a failure on the Abis, causing drops on the Air interface (as soon as the Abis is down, all calls handled by this abis are dropped) T200 : Supervision of acknowledgements on the Abis, by the BSC and by the BTS. When BTS sends a message on Abis to the BSC, the BSC should reply with an acknowledgment. The BTS waits T200 ms (def T200 = 300ms). If ack is received before T200, then fine. Life goes on. If T200 expires (no ack received), then BTS sends the initial message one more time. It will then wait T200, for the ACK.

Still no ack ? Then the process is repeated N200 times (N200 = 12, by default). So 12 attempts to send 1 message, still no ack received... then the Abis link is assumed to be dead, and all communications are lost in the BTS. TRX, Abis and BSC boards are reset (depends on vendor behaviour). T200 is on the abis, it doesn't directly impact the Air interface nor the call setup procedure. All signalling msg on abis are acknowledged. In 3GPP 44.006 any interested person can to find information about T200 equipment (it isn't advertisment:). T200 is data link (layer 2) timer. It is triggered on BSC side and on MS side (There is no Layer2 in BTS, only Layer1 - modulation and channel coding). T200 supervises the acknowledged transfer of layer 3 messages (e.g. location updating, setup and many others) by data link layer. T200 expires when there is no acknowledgment from peer layer2 (BSC or MS) during T200 ms. If T200 expired N200 times then layer2 indicates to layer3 about message transfer failure. Values of T200 for different channel types (SDCCH, SACCH, FACCH) are implementation dependent and must be chosen according recommendations in 44.006. Values of N200 (from 44.006): - 5 for use on SACCH; - 23 for use on SDCCH; - 34 for use on FACCH/full rate; - 48 for use on E FACCH/full rate; - 29 for use on FACCH/half rate. well, i'm actually quite sure of this, because the BTS monitors the Abis/LapD availability based on T200 timer. (quite sure = almost sure, i'm not stubborn and i'm always glad to be proven wrong) If BTS detects N200 x T200 expiries, then it will restart its communication board. Lapd is a protocol that operates at the layer2, Datalink layer of the OSI architecture to transfer the information between Layer3 entities (in BSC, BTS and TSC) across the user network interface. On the BTS side each TRX handles the LAPD protocol for the RSL signalling link of this TRX and the OMU handles the LAPD protocol for the OML signalling link of the BTS. In BSC, the LAPD protocol (Layer 1 and Layer 2) is handled in a TCU. The reset procedure (Data Link reset in LAPD specification) is performed either by the TRX or the TCU or the OMU mainly when a layer 2 frame has been transmitted N200 times without acknowledgement. ---" The lapdm is handled between MS and BTS, it doesn't do over the abis : " --The Link Access Procedure on the Dm channel, LAPDm, is the data link layer protocol, (layer 2 of the OSI model), used between the BTS and the MS, on the air interface. T200 is not related to a GSM procedure. Every time something is sent on Abis, an ACK is awaited. It won't improve the call setup time, unless you have a lot of LapD

retransmissions, usually. You can check lapd retransmission with a qos indicator. If you update the T200 in BSC, I don't know if the BTS is going to be updated as well. It depends on your system. Is it alcatel ? In this case, check your parameters dictionary, it should be explained there.