Content for TS 23.009 Word version: 18.0.0
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 Interactions between handover/relocation control procedures and other RANAP procedures
12.8.1 Interactions between handover/relocation control procedures and the security mode procedure
...
...
12.8 Interactions between handover/relocation control procedures and other RANAP procedures |R5| p. 100
This clause gives an overview of the procedures that shall be followed when handover/relocation control procedures interact with other RANAP procedures on 3G_MSC-B.
12.8.1 Interactions between handover/relocation control procedures and the security mode procedure p. 100
12.8.1.1 Intra-3G_MSC-B handover/relocation p. 100
A security mode control procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation. If RNS-A replies with an Iu-SECURITY-MODE-REJECT containing the cause value 'Relocation Triggered' due to an already initiated Intra-3G_MSC-B UMTS to GSM handover or Intra-3G_MSC-BSRNS relocation, the 3G_MSC-B shall not forward the result of the security mode control procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure. If the relocation procedure is completed successfully, the 3G_MSC-B shall reattempt the security mode control procedure towards the new serving radio network. If the handover procedure is completed successfully, the 3G_MSC-B shall reattempt the cipher mode control procedure towards the new serving radio network, if ciphering is to be activated.
Figure 35a: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a security mode control procedure i): successful handover/relocation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
If the handover/relocation procedure is unsuccessful and the UE is still served by RNS-A, the 3G_MSC-B shall reattempt the security mode procedure towards RNS-A.
Figure 35b: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a security mode control procedure ii): unsuccessful handover/relocation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
12.8.1.2 Subsequent Inter-MSC handover/relocation p. 102
A security mode control procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation. If RNS-A replies with an Iu-SECURITY-MODE-REJECT 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 security mode procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure. If the subsequent Inter-MSC relocation procedure is completed successfully, the 3G_MSC-A shall reattempt the security mode control procedure towards the new serving radio network or MSC-B'/3G_MSC-B'. If the subsequent Inter-MSC handover procedure is completed successfully, the MSC-A/3G_MSC-A shall reattempt the cipher mode control procedure towards the new serving radio network or MSC-B'/3G_MSC-B, if ciphering is to be activated.
Figure 35ba: Collision between a subsequent Inter-MSC handover/relocation and a security mode control procedure i): successful handover/relocation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
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 security mode procedure towards RNS-A.
Figure 35bb: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a security mode control procedure ii): unsuccessful handover/relocation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
