Confidentiality:
Confidential
Authors:
Revised:
Release:
UMR 3.0
Version:
1.0
Issued:
31 October 2003
Number of pages:
11
History
Version
Description
1.0
First issue
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 1 of 11
DPC Separation of ALCAP and RANAP
Contents
Contents.......................................................................................................................... 2
2.1
2.2
2.3
Purpose ......................................................................................................................................3
Synopsis .....................................................................................................................................3
References..................................................................................................................................3
Overview ......................................................................................................................... 4
System Restart.................................................................................................................6
6.1
6.2
6.3
6.4
6.5
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 2 of 11
DPC Separation of ALCAP and RANAP
Document Scope
2.1 Purpose
The purpose of this document is to describe the implementation for the separation of Destination
Point Code (DPC) for RANAP and ALCAP for CS domain.
2.2 Synopsis
This document give an overview of functionality and are also analyzed the System Aspects,
Releases compatibility, Functional and Architectural aspects.
2.3 References
[1] TS 25.410 UTRAN Iu Interface : General Aspects and Principles v3.8.0
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 3 of 11
DPC Separation of ALCAP and RANAP
Overview
Actual configuration (UMR 2.0) of RNC permits an Architecture of CN with common DPC for ALCAP
and RANAP for CS Domain, as showed in Figure 1
POINT CODE
(decimal)
1275
POINT CODE
(decimal)
12801
Link Group #1 (RANAP Iu-CS/Q.AAL2)
RNC
MSC
POINT CODE
(decimal)
12930
SGSN
Link Group #2 (RANAP Iu-PS)
Figure 1:
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 4 of 11
DPC Separation of ALCAP and RANAP
MSC
Server
(RANAP Iu-CS)
Link Group #1B
RNC
MGW
(Q.AAL2)
POINT CODE
(decimal)
Link Group #2
12930
(RANAP Iu-PS)
Iu-PS)
POINT CODE
(decimal)
12801
RNC-SGSN links are ATM
cross-connected at the MGW
Figure 2:
S
G
S
N
POINT CODE
(decimal)
1267
The support of this feature allows inter-working with the Core Network implementations supporting
the Rel. 4 architecture of a separated MGW and MSC server, but Rel 4 protocols (RANAP-R4,
Q.2630.2) are not supported
In the separated architecture, the following parameters shall be set to the values of the MGW. In
the combined architecture, they shall be set to the values of the MSC.
NAME
Type: Integer
Range: 03
DESCRIPTION
This parameters refers to the
SP for Q.AAL2 signalling in the
CS Domain
This parameters refers to the
SP for Q.AAL2 signalling in the
CS Domain
This parameters refers to the
SP for Q.AAL2 signalling in the
CS Domain Destination Point
Code
This parameters refers to the
SP for Q.AAL2 signalling in the
CS Domain
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 5 of 11
DPC Separation of ALCAP and RANAP
CS RAB assignment
During the CS RAB Establishment procedure, upon reception of the RANAP RAB Assignment
Request message from the CS domain of the CN, the RNC determines the addressing information
(NI, DPC) for the node to which the ALCAP signalling shall be sent.
By using O&M parameters, the RNC shall map the NI and DPC values from the Transport Layer
Address IE included in the RAB Assignment Request message (AAL2 End-point Address -A2EA-).
If there is no mapping found between the A2EA and NI, DPC the RNC shall fail the RAB
Assignment procedure.
System Restart
The restart sequences are not affected by the different CN architectures. The following behaviours
are therefore supported.
RNC
MGW
M S C S erv er
PC =p1
PC =p2
PC =p3
A 2 E A = a1
A 2 E A = a2
R A N A P :R E S E T
(D P C = p 1 )
(D P C = p 1 )
R elease o f affected
A L C A P reso u rce
A L C A P :B L O
R ep eated fo r th e
n u m b er o f lo cally
b lo ck ed A A L 2
p ath s
(D P C = p 2 )
A L C A P :B L C
(D P C = p 1 )
R A N A P :R E S E T A C K
(D P C = p 3 )
(D P C = p 3 )
When a MSC restarts, it is possible for releasing the AAL2 resources in the MGW. Therefore, when
the RNC receives RANAP : RESET, the RNC releases the AAL2 resources on the Iu Interface locally
and does not initiate any AAL2 reset procedures.
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 6 of 11
DPC Separation of ALCAP and RANAP
If the MSC does not release the ALCAP resources in the MGW, there is the possibility of mismatch
between the RNC and the CN.
During the restart, the RNC sends ALCAP : BLO for each locally blocked AAL2 resource. This
signalling is sent towards the MGW instead of the MSC in case of the split CN architecture
RNC
MGW
MSC Server
PC=p1
PC=p2
PC=p3
A2EA=a1
A2EA=a2
RANAP:RESET RESOURCE
(DPC=p1)
(DPC=p1)
Release of ALCAP
resource
(DPC=p3)
Similar to 6.1, the MSC is responsible for the release of the AAL2 resources in the MGW, therefore
the RNC releases the AAL2 resources locally only.
If the MSC does not release the ALCAP resources in the MGW, there is the possibility of mismatch
between the RNC and the CN.
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 7 of 11
DPC Separation of ALCAP and RANAP
MGW
MSC Server
PC=p1
PC=p2
PC=p3
A2EA=a1
A2EA=a2
RNC
ALCAP:RES
(DPC=p1)
SCCP:RLSD
(DPC=p3)
(DPC=p3)
SCCP:RLC
(DPC=p1)
(DPC=p1)
ALCAP:BLO
(DPC=p2)
ALCAP:BLC
(DPC=p1)
ALCAP:RSC
(DPC=p2)
MGW
MSC Server
PC=p1
PC=p2
PC=p3
A2EA=a1
A2EA=a2
RANAP:RESET
(DPC=p3)
(DPC=p3)
Release of affected
RANAP/ALCAP resource
RANAP:RESET ACK
(DPC=p1)
(DPC=p1)
Upon reception of RANAP Reset, the MSC is responsible for the release of the AAL2 resources in
the MGW. Therefore, the RNC does not send ALCAP: RES to the MGW.
If the MSC does not release the ALCAP resources in the MGW, there is the possibility of mismatch
between the RNC and the CN.
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 8 of 11
DPC Separation of ALCAP and RANAP
MGW
MSC Server
PC=p1
PC=p2
PC=p3
A2EA=a1
A2EA=a2
RANAP:RESET RESOURCE
(DPC=p3)
(DPC=p3)
Release of affected
RANAP/ALCAP resource
RANAP:RESET RESOURCE ACK
(DPC=p1)
(DPC=p1)
Protocol architecture
The following figures depict the protocol termination points for the split CN architecture. RANAPCS, RANAP-PS, ALCAP, Iu-CS-UP and Iu-PS-UP are all on separate VCs. There are separate VPs
depending on the terminating node.
RANAP - CS
RANAP
RANAP
SCCP
SCCP
MTP-3b
SSCF-NNI
MTP-3b
SSCF-NNI
SSCOP
SSCOP
ATM cross-connect
AAL5
ATM
ATM
ATM
L1
L1
L1
RNC
MGW
MSC
Figure 8:
Date:
Confidentiality:
AAL5
31/10/03
Confidential
Page 9 of 11
DPC Separation of ALCAP and RANAP
ALCAP - CS
Q.2630.1
Q.2630.1
Q.2150.1
Q.2150.1
MTP-3b
SSCF-NNI
Figure 9:
MTP-3b
SSCF-NNI
SSCOP
SSCOP
AAL5
AAL5
ATM
ATM
L1
L1
RNC
MGW
RANAP - PS
RANAP
RANAP
SCCP
SCCP
MTP-3b
SSCF-NNI
MTP-3b
SSCF-NNI
SSCOP
SSCOP
ATM cross-connect
AAL5
AAL5
ATM
ATM
ATM
L1
L1
L1
RNC
MGW
MSC
In the following it is possible to compare the difference between actual VP/VC Basic Configuration
(UMR 2.0) and that adopted with this feature (UMR 3.0).
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 10 of 11
DPC Separation of ALCAP and RANAP
(UMR 2.0)
VPI (To MSC) 1 VC Iu CS-UP + 1 VC RANAP CS / ALCAP
STM-1
MS
C
RNC
SGSN
(UMR 3.0)
There is one VP for RANAP-CS, one VP for ALCAP and Iu-CS-UP, and one VP for RANAP-PS and IuPS-UP.
VPI (To MSC) 1 VC RANAP CS
VPI (To MGW) 1 VC ALCAP + 1 VC Iu CS-UP
VPI (To SGSN) 1 VC RANAP PS + 1 VC Iu PS-UP
MSC
RNC
MG
W
SGSN
STM-1
Date:
Confidentiality:
31/10/03
Confidential
UMR 3.0
Page 11 of 11
DPC Separation of ALCAP and RANAP