You are on page 1of 11

Feature description

DPC Separation for ALCAP and RANAP

Confidentiality:

Confidential

Authors:

Angelo Ronchi (NEC I)

Revised:

Antonio Coricciati (NEC I), Matteo Taglienti (SMC)

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

DPC Separation for ALCAP and RANAP

Contents

Contents.......................................................................................................................... 2

Document Scope .............................................................................................................. 3

2.1
2.2
2.3

Purpose ......................................................................................................................................3
Synopsis .....................................................................................................................................3
References..................................................................................................................................3

Overview ......................................................................................................................... 4

O & M Parameters and Configuration................................................................................ 5

CS RAB assignment .......................................................................................................... 6

System Restart.................................................................................................................6

6.1
6.2
6.3
6.4
6.5

MSC restart .................................................................................................................................6


MSC partial restart .......................................................................................................................7
MGW restart................................................................................................................................7
RNC restart .................................................................................................................................8
RNC partial restart .......................................................................................................................9

Protocol architecture ........................................................................................................ 9

VP/VC Basic Configuration .............................................................................................. 10

Date:
Confidentiality:

31/10/03
Confidential

UMR 3.0

Page 2 of 11
DPC Separation of ALCAP and RANAP

DPC Separation for 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

DPC Separation for 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)

RANAP and ALCAP


terminate at the same
point code (MSC)

RNC

MSC

POINT CODE
(decimal)
12930

SGSN
Link Group #2 (RANAP Iu-PS)

Figure 1:

CN architecture with common DPC for ALCAP and RANAP

At the same time, [1], 3GPP TS 25.410 v3.8.0 mentions :


For a given MSC, the RNC shall be able to access RANAP and ALCAP either under the same MTP3b
destination point code, or under different point codes
For this reason from UMR 3.0 the RNC in addition to the common DPC configuration (fig. 1),
supports the separation of DPC for RANAP and ALCAP on Iu Interface for CS Domain (Split CN
Architecture in Media Gateway MGW- and MSC Server) Rel 4.
The RNC is physically connected only to the MGW (max 1 MGW). MGW and MSC point codes
(DPCs) are different. MGW performs the routing messages to the MSC or itself based on the
indicated point code (DPC). Signalling bearer of ALCAP is terminated at the MGW. Signalling bearer
of RANAP is terminated at the MSC (ATM Cross-connected at the MGW). In addition, the MGW
performs the routing of messages to the SGSN based on the relevant point code (DPC) (ATM
Cross-connected at MGW).

Date:
Confidentiality:

31/10/03
Confidential

UMR 3.0

Page 4 of 11
DPC Separation of ALCAP and RANAP

DPC Separation for ALCAP and RANAP

RNC-MSC Server links are ATM


cross-connected at the MGW

MSC
Server

Link Group #1A


(RANAP Iu-CS)

Link Group #1A


POINT CODE
(decimal)
1275

(RANAP Iu-CS)
Link Group #1B

RNC

MGW

(Q.AAL2)

Link Group #2 (RANAP

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

CN architecture for the separated DPC for ALCAP and RANAP

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

O & M Parameters and Configuration

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 & RANGE

AAL2 end point address


initial domanin identifier

AAL2 end point address


domanin specific part

Type: Octet String


Range: 1-15 digits
0,,9
Type: Octet String
Range: 1-22 hex
(0,,9,a,,f)
Type: Octet String

Destination Point Code (CS)

Range: 5-9 digits


0,,9

Network Indicator (CS)

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

Table 1: Parameters for separation of ALCAP and RANAP DPC

Date:
Confidentiality:

31/10/03
Confidential

UMR 3.0

Page 5 of 11
DPC Separation of ALCAP and RANAP

DPC Separation for ALCAP and RANAP

Configuration of transport parameters for RNC-MGW connection must be configured and to be


used from LMT.

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.

6.1 MSC restart

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 )

In tern al release o f all


R A N A P /A L C A P reso u rces

(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 )

Figure 3: MCS restart sequence

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

DPC Separation for 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

6.2 MSC partial restart

RNC

MGW

MSC Server

PC=p1

PC=p2

PC=p3

A2EA=a1

A2EA=a2
RANAP:RESET RESOURCE
(DPC=p1)

Internal release of all


RANAP/ALCAP
resources

(DPC=p1)

Release of ALCAP
resource

RANAP:RESET RESOURCE ACK


(DPC=p3)

(DPC=p3)

Figure 4: MSC partial restart sequence

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.

6.3 MGW restart


Upon reception of the ALCAP: RES, the RNC releases the SCCP connections. Therefore, no
mismatch between RNC and CS domain is possible.
During the restart, the RNC releases the SCCP connections, and therefore the NI, DPC of the MSC
is used.

Date:
Confidentiality:

31/10/03
Confidential

UMR 3.0

Page 7 of 11
DPC Separation of ALCAP and RANAP

DPC Separation for ALCAP and RANAP

MGW

MSC Server

PC=p1

PC=p2

PC=p3

A2EA=a1

A2EA=a2

RNC

ALCAP:RES
(DPC=p1)
SCCP:RLSD

Repeated for the


number of
affected SCCP
connections

(DPC=p3)

(DPC=p3)
SCCP:RLC
(DPC=p1)

(DPC=p1)

ALCAP:BLO

Repeated for the


number of locally
blocked AAL2
paths

(DPC=p2)
ALCAP:BLC
(DPC=p1)
ALCAP:RSC
(DPC=p2)

Figure 5: MGW restart sequence

6.4 RNC restart


RNC

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)

Figure 6: RNC restart sequence

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

DPC Separation for ALCAP and RANAP

6.5 RNC partial restart


RNC

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)

Figure 7: RNC partial restart sequence


Similar to 6.4, upon reception of RANAP Reset Resource, the MSC is responsible for the release of
the AAL2 resources in the MGW. Therefore, the RNC does not send ALCAP: REL for the affected
AAL2 resources.
If the MSC does not release the ALCAP resources in the MGW, there is the possibility of mismatch
between the RNC and the CN.

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

OPC = Self Node


DPC = CN-CS

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

Protocol termination for RANAP - CS in case of split CN architecture


UMR 3.0

Page 9 of 11
DPC Separation of ALCAP and RANAP

DPC Separation for ALCAP and RANAP

ALCAP - CS
Q.2630.1

Q.2630.1

Q.2150.1

Q.2150.1

MTP-3b
SSCF-NNI

Figure 9:

OPC = Self Node


DPC = MGW

MTP-3b
SSCF-NNI

SSCOP

SSCOP

AAL5

AAL5

ATM

ATM

L1

L1

RNC

MGW

Protocol termination for ALCAP in case of split CN architecture

RANAP - PS
RANAP

RANAP

SCCP

SCCP

MTP-3b
SSCF-NNI

MTP-3b

OPC = Self Node


DPC = CN-PS

SSCF-NNI
SSCOP

SSCOP
ATM cross-connect

AAL5

AAL5

ATM

ATM

ATM

L1

L1

L1

RNC

MGW

MSC

Figure 10: Protocol termination for RANAP - PS in case of split CN architecture

VP/VC Basic Configuration

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

DPC Separation for 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

VPI (To SGSN) 1 VC RANAP PS + 1 VC Iu PS-UP

(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