You are on page 1of 2

Normal Release Procedure

Normal release is originated by the MS or the MSC. Upon on hook, the calling MS sends a Disconnect message to the MSC. Then the corresponding MSC sends the Disconnect message to the called MS.

Signaling Procedure After the access of the MS, the BSC initiates the release procedure upon service
requests, for example, MS onhook. Figure 1 shows the BSC normal release procedure.

The BSC normal release procedure is as follows: 1. Upon onhook, the calling MS sends a Disconnect message to the MSC and starts timer T305. The Disconnect message carries the cause for disconnection.

2. The MSC sends the calling MS a Release message and at the same time sends the called MS a Disconnect message. The network starts timer T308. 3. Upon receiving the Release message, the calling MS stops timer T305, releases the MM connection, and sends the MSC a Release Complete message. 4. Upon receiving the Release Complete message, the MSC stops timer T308, releases the MM connection, and sends the BSC a Clear Command message. The Clear Command message notifies the BSC of releasing the resources on the A interface and the Um interface. 5. The BSC sends a Channel Release message and starts timer T3109. The Channel Release message carries the RR cause filed and notifies the MS and the BTS of releasing the logic channels on the Um interface. 6. Upon receiving the Channel Release message, the MS disconnects the uplink signaling link and sends the BTS a DISC frame, indicating that the logic channels are released. 7. The BTS sends the MS a UA frame. Upon receiving the UA frame, the MS returns to the CCCH and enters the idle state. 8. The BSC sends the BTS a Deactivate SACCH message, deactivates the associated channels, and releases the downlink channel associated signaling. 9. Upon receiving the DISC frame, the BTS sends the BSC a Release Indication message, stops timer T3109, and starts timer T3111. The Release Indication message indicates that the MS has released the logic channels on the Um interface. 10. Upon timer T3111 expiry, the BSC sends the BTS an RF Channel Release message. Timer T3111 is used to reserve a period for the acknowledgement of disrupted connection. 11. The BTS sends the BSC an RF Channel Release Acknowledge message, indicating that the RF channels on the radio interface are released and can be used for re-assignment. 12. The BSC responds to the MSC with a Clear Complete message. 13. The MSC sends the BSC an RLSD message to release the SCCP connection. 14. The BSC responds to the MSC with an RLC message, indicating that the SCCP connection is released.

Procedure Description
Steps 1 through 3 shown in Figure 1 is the call connection release. NOTE: Figure 1 shows the MS originating release procedure. For the network originating release procedure, the directions of only the three transparent transmission messages are opposite. Steps 4 through 14 shown in Figure 1 is the radio resource release. After the connections at the CC layer and at the MM layer are released, the network sends the BSC a Clear Command message to request the release of the SCCP signaling link. The Clear Command message carries the clear causes such as the Handover Successful or Call Control. If the release is caused by radio interface message failures, radio link failures, or equipment failures, the BSC sends a Clear Request message to the system. Then, the MSC delivers the Clear Command message.

You might also like