Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.009  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   4.3…   6…   6.2…   6.2.3   6.3…   7…   7.2…   8…   8.1.3…   8.2…   8.2.2…   8.2.4   8.3…   8.3.2…   9…   10…   11…   12…   12.8…   12.8.2   12.8.3   13…   14…   15… 
12.8.2  Interactions between handover/relocation control procedures and the RAB assignment procedure 
...

 

12.8.2  Interactions between handover/relocation control procedures and the RAB assignment procedure  p. 104

12.8.2.1  Intra-3G_MSC-B handover/relocation  p. 104

A subsequent channel assignment procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation without circuit connection (see subclauses 13.2 and 13.4). If RNS-A replies with an Iu-RAB-ASSIGNMENT-RESPONSE containing the cause value 'Relocation Triggered' due to an already initiated Intra-3G_MSC-B UMTS to GSM handover or Intra-3G_MSC-B SRNS relocation, the 3G_MSC-B shall not forward the result of the RAB assignment procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure. If the handover/relocation procedure is completed successfully, the 3G_MSC-B shall construct an A-ASSIGNMENT-COMPLETE or Iu-RAB-ASSIGNMENT-RESPONSE message, dependent on the encapsulated protocol used on the E-interface, and forward this message to MSC-A/3G_MSC-A in the MAP-PREPARE-HANDOVER response.
Copy of original 3GPP image for 3GPP TS 23.009, Fig. 35c: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a RAB assignment procedure i): successful handover/relocation
Figure 35c: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a RAB assignment procedure i): successful handover/relocation
(⇒ copy of original 3GPP image)
Up
If the handover/relocation procedure is unsuccessful and the UE is still served by RNS-A, the 3G_MSC-B shall reattempt the RAB assignment procedure towards RNS-A.
Copy of original 3GPP image for 3GPP TS 23.009, Fig. 35d: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a RAB assignment procedure ii): unsuccessful handover/relocation
Figure 35d: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a RAB assignment procedure ii): unsuccessful handover/relocation
(⇒ copy of original 3GPP image)
Up

12.8.2.2  Subsequent Inter-MSC handover/relocation  p. 106

A subsequent channel assignment procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation without circuit connection (see subclauses 13.2 and 13.4). If RNS-A replies with an Iu-RAB-ASSIGNMENT-RESPONSE containing the cause value 'Relocation Triggered' due to an already initiated subsequent Inter-MSC handover/relocation, the 3G_MSC-B shall not forward the result of the RAB Assignment procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure.
Copy of original 3GPP image for 3GPP TS 23.009, Fig. 35da: Collision between a subsequent Inter-MSC handover/relocation and a RAB assignment procedure i): successful handover/relocation
Figure 35da: Collision between a subsequent Inter-MSC handover/relocation and a RAB assignment procedure i): successful handover/relocation
(⇒ copy of original 3GPP image)
Up
If the subsequent Inter-MSC handover/relocation procedure is unsuccessful and the UE is still served by 3G_MSC-B, the 3G_MSC-B shall reattempt the subsequent channel assignment procedure towards RNS-A.
Copy of original 3GPP image for 3GPP TS 23.009, Fig. 35db: Collision between a subsequent Inter-MSC handover/relocation and a RAB assignment procedure ii): unsuccessful handover/relocation
Figure 35db: Collision between a subsequent Inter-MSC handover/relocation and a RAB assignment procedure ii): unsuccessful handover/relocation
(⇒ copy of original 3GPP image)
Up

Up   Top   ToC