Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.231  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   4.4.2   4.4.3   4.4.4   4.4.5…   6…   6.1.2…   6.2…   6.2.2…   7…   7.2.3   7.2.4…   7.3…   8…   9…   13…   14…   15…

 

7.2.4  Call Clearing initiated by V-MSC Serverp. 39

7.2.4.1  Call clearing towards access networkp. 39

Call clearing to the UE is performed as described in clause 7.2.2.1.

7.2.4.2  Call clearing towards network sidep. 39

Call clearing to the network side is performed as described in clause 7.2.3.2

7.2.4.3  Example Call Flowp. 39

Figure 7.2.4.3.1 shows the network model for a MSC server initiated clearing of an established mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW.
Copy of original 3GPP image for 3GPP TS 23.231, Fig. 7.2.4.3.1: MSC Server Initiated Call Clearing (Network model)
Up
Figure 7.2.4.3.2 shows the message sequence example for the MSC server initiated clearing of an established mobile call. In the example the MSC server initiates call clearing of the network side and the access side. After the call clearing towards the UE and the release of the radio resource have been completed the MSC server requests release of the access side bearer termination. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server requests the MGW to release the network side bearer termination.
Copy of original 3GPP image for 3GPP TS 23.231, Fig. 7.2.4.3.2: MSC Server Initiated Call Clearing (message sequence chart)
Up

7.2.5  Call clearing received from MGWp. 40

7.2.5.1  Bearer released on the access sidep. 40

After the MSC server has received the Bearer Released procedure from the MGW on the access side, the MSC server shall release the access resources as described in clause 7.2.2.1. If the call is already established towards the network side, call clearing to the network side is performed as described in clause 7.2.3.2.

7.2.5.2  Bearer released on the network sidep. 40

After the MSC server has received the Bearer Released procedure from the MGW on the network side, the MSC server shall clear the call to the network side as described in clause 7.2.3.2, and clear the call to the UE as described in clause 7.2.2.1.

7.2.5.3  Example Call Flowp. 40

Figure 7.2.5.3.1 shows the network model for an MGW initiated clearing of an established mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW.
Copy of original 3GPP image for 3GPP TS 23.231, Fig. 7.2.5.3.1: MGW Initiated Call Clearing (Network model)
Up
Figure 7.2.5.3.2 shows the message sequence example for the MGW initiated clearing of an established mobile call. After the MSC server is notified that the MGW has released the network side bearer, the MSC server initiates call clearing of the network side and the access side. After the call clearing towards the UE and the radio resource release have been completed the MSC server requests release of the access side bearer termination. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server requests the release of the network side bearer termination.
Copy of original 3GPP image for 3GPP TS 23.231, Fig. 7.2.5.3.2: MGW Initiated Call Clearing (message sequence chart)
Up

7.2.6  Call Clearing procedures towards MGWp. 42

The MSC server shall release any network side MGW allocated resources reserved for the call. If any resources were seized in the MGW the MSC server shall use the Release Termination procedure to indicate to the MGW to remove the bearer termination.

7.2.7  Call Clearing for Iu Interface on IPp. 42

Procedures for Call Clearing where the Iu Interface is on IP are as described in clauses through 7.2.2 to 7.2.6.
For Iu Interface on IP, the Release Termination procedure for IP is used to clear the Access side bearer termination.

Up   Top   ToC