3GPP TSG GERAN Workshop Tdoc GAHW-000046

Munchen, Germany Agenda item 6.1.2.1

October 9-13, 2000
Source: Ericsson

Inclusion of Iu-cs into GERAN architecture

1. Introductioncsdcscsacdsvdsvsgfsgs
One of the main goals of the GERAN enhancements for R00 is the possibility to connect to 3G
UMTS core network thus offering a possibility for complementary deployment with UTRAN.
Therefore, it is essential to reach the full alignment with UTRAN when it comes to external
interfaces and corresponding services.
At the joint SMG2/SMG12/3GPP S2 Workshop on GERAN on 21-22 February 2000, it was
decided to introduce the support of Iu-ps interface the GERAN R00 reference architecture. The
support for A and Gb is kept for the backwards compatibility reasons. Iu-ps interface is used to
connect GERAN to packet switched part of the 3G UMTS core network. The introduction of the
corresponding Iu-cs interface towards the circuit switched domain was left FFS (see [4]).
In order to finalize the GERAN architecture with respect to external interfaces, this paper argues
for and also suggests to include Iu-cs interface into GERAN R00 reference architecture. That in
order to prepare GERAN for a full alignment with UTRAN but also, indirectly, to allow for re-use of
many of the RAN MM and RR mechanisms already specified for UTRAN. See also [2], [3].

2. PROs and CONs regarding Iu-cs in GERAN

There is an issue in the GERAN standardisation whether to introduce thew Iu-cs interface
support. There are basically 2 alternative scenarios (see also proposed Work Item in [1]):
- Do not include Iu-cs interface but possibly improve the A-interface.
- Introduce Iu-cs interface. In parallel, Iu-cs should be evolved to support IP for connection to
IP based radio access network and core network.

This document tries to summarize the pros and cons when introducing Iu-cs interface in GERAN.
It also tries to indicate the impact the introduction of Iu-cs will have on GERAN. For some
additional argumentation see [2].

Additionally, when adopting Iu-cs interface for GERAN, further improvements of the A-interface
can be considered separately based on the market drivers.
3GPP TSG GERAN Workshop
Munchen, Germany
October 9-13, 2000
Source: Ericsson
PROs and CONs with an introduced Iu-cs
+ Common 3G UMTS core network for UTRAN
and GERAN
+ Support for CS services towards 3G UMTS
core network
+ Network expansion into 3G UMTS core
network
+ Smoother transition towards all-IP
+, - With Iu-cs the transcoding is moved from the
access network up to the core network.
+ Iu protocols and functionality common to
both UTRAN and GERAN for both Iu-cs and
Iu-ps (e.g. RAB management, RANAP,
SCCP)
+ The transport layer for Iu-cs will be IP based
as an option.
- A new interface to be supported in BSS
- The A-interface needs to be supported by
core network for pre-R00 BSCs and MSs
(probably for a long time)
- R00 Mobile stations may need to be both A
(when controlled by an pre-R00 cell) and Iu-
cs capable ( when controlled by an R00-cell)
+ Class A mobile stations can be defined as
either the combination A/Gb or Iu-cs/Iu-ps
+ Global terminal roaming
Tdoc GAHW-000046
Agenda item 6.1.2.1
Comment
Full alignment between UTRAN and GERAN
regarding external interfaces
Provision of enhanced voice and wideband circuit
switched data services provided over Iu-cs. However,
the functional increment from A is still rather small.
Most major investments for CS infrastructure can be
done into 3G UMTS core network. May also mean
easier migration towards Iu-ps.
By aligning GERAN and UTRAN, same services can
be offered over Iu-cs during the transition towards an
all-IP network solution over Iu-ps. See also [7].
Will result in:
+ Common pool of transcoders for CS/PS domains
+ Allowing low-bit rate speech in the core network.
Possibly double transcoder pool in BSS and MGW
Common protocols and functionality means that much
can be re-used for GERAN design.
Will in the future reduce the need to support
- Multiple interfaces (A/Gb and Iu),
- Multiple transport networks (STM, ATM, FR, IP)
- Multiple CC, SS and MM functionality ;
3GPP RAN WG3 is working towards standardisation
on this issue. Further, it is likely that one or more
additional options besides ATM will be standardised
for L1/L2 of Iu interface thus offering freedom in
investments.
New protocol stacks/functionality for Iu-cs is to be
implemented in BSS and MS. However, due to
similarity between Iu-ps and Iu-cs, this is a modest
addition of work and cost.
With both Iu-cs and A interface to BSS, the core
network has to use two different MM, CC and SS for a
mobile station when moving between old and new
cells (e.g RAB management only handled when the
MS is an R00-cell etc.). However, this is a modest
addition because Iu-ps handling for MM/SS will be
supported.
The interaction between the services offered over the
two interfaces on the core network side has to be
specified. Radio conditions or system load based cell
re-selection is still the only allowed algorithm, contrary
to the service based.
If Iu-cs is not included there will only be Class A
operation via A/Gb and in the future with a real time
competent Iu-ps. The main argument against other
combinations, e.g. A/Iu-ps, is the creation of additional
modes than those specified for DTM and UTRAN
which would slow down MS evolution and create
dependencies between RANAP and BSSAP. See also
[3].
The possibility to offer compatible CS services in
UTRAN and GERAN may improve the roaming
capabilities for terminals, especially when handover
UTRAN-GERAN for CS domain over Iu-cs is
standardised.
3GPP TSG GERAN Workshop Tdoc GAHW-000046
Munchen, Germany Agenda item 6.1.2.1
October 9-13, 2000
Source: Ericsson

3. Proposed GERAN Reference Architecture

In the Stage 2 description for GERAN, GSM 03.51 (3GPP 43.051) [5], Figures 1 and 2, the FFS
note that is adjacent to Iu-cs should be removed as shown for Figure 2 in Chapter 4.2:

Um Iu-ps
MS BTS
Gb
BSC A
Iu-cs (ffs)
BTS
Iurg

BSC
GSM/UMTS
GERAN Core Network

GSM 03.51 Figure 2. GERAN reference architecture

3GPP TSG GERAN Workshop Tdoc GAHW-000046
Munchen, Germany Agenda item 6.1.2.1
October 9-13, 2000
Source: Ericsson

Secondly, the inclusion of Iu-cs (and Iu-ps) for GERAN need to be introduced into TS 23.002 [6]
at TSG-SA if the support of Iu interface is to be defined for R4 (otherwise it waits for R5). One
example is the reference picture in Figure 1:

PSTN Gi Gp
PSTN PSTN
T-SGW R-SGW

MGW Mc GMSC GGSN

server

C Mh
Gc

Nc HSS(HLR) H AuC Gn
PSTN
Nb
Gr
D EIR
F Gf
G
VLR VLR
B Gs
B
SGSN
MSC server MSC server
E
Mc
Mc
CN
MGW MGW
Nb

A, Gb, IuPS IuCS IuPS

IuCS
BSS RNS
Iur
BSC RNC RNC
Abis Iubis

BTS BTS Node B Node B

cell

Um Uu

ME

SIM-ME i/f or Cu

SIM USIM

MS

TS 23.002 Figure 1: Basic Configuration of a PLMN supporting CS and PS services and interfaces
3GPP TSG GERAN Workshop Tdoc GAHW-000046
Munchen, Germany Agenda item 6.1.2.1
October 9-13, 2000
Source: Ericsson

Thirdly, the inclusion of Iu-cs for GERAN for the all-IP reference architecture should be
considered when introducing the contents of TR 23.821 [5] into Technical Specifications
documents for R5. E.g. the reference arcitecture for all-IP archietecture can be completed with
the Iu-cs for GERAN as depicted in the following figure:

Alternative Legacy mobile

Applications & signaling
Access Services *) Network
Network
SCP
Multimedia
CSCF
R-SGW IP Networks
Mh Mw
SGSN Ms
GGSN CAP
Mm
Gn HSS *) Cx
Other PLMN CSCF
Gr Mg
Gp Gi Mr Gi
EIR
MRF
Gf
GERAN Iu Gc Gi MGCF T-SGW *)
TE MT
R Um SGSN GGSN Mc
Gi
Iu Gn
Iu
TE MT UTRAN PSTN/
MGW MGW Legacy/External
1
R Uu Iu Nb
Iu Mc Mc
1
Iu = Iucs (RTP, AAL2)
Iu 2 Nc
2
Iu MSC server GMSC server T-SGW *)
Iu = Iu(RANAP)

MAP
MAP Mh
Applications
& Services *) HSS *) R-SGW *)

*) those elements are duplicated for figure

Signalling Interface layout purpose only, they belong to the same
Signalling and Data Transfer Interface logical element in the reference model

TR 23.821 Figure 5.1 Reference Architecture for Release 2000

3GPP TSG GERAN Workshop Tdoc GAHW-000046
Munchen, Germany Agenda item 6.1.2.1
October 9-13, 2000
Source: Ericsson

4. Conclusion
Based on the arguments presented, this contribution suggests the inclusion of the support
for Iu-cs interface into the GERAN reference architecture:

By supporting Iu-cs and Iu-ps, UTRAN and GERAN will have common harmonized interface
towards the 3G UMTS core network. This is also the preferred solution for the 3G UMTS core
network evolution. If the radio access technology type (UTRAN/GERAN) has to be reflected
over the Iu is FFS.

As GERAN is required to support also pre R00 mobile stations and pre R00 BSCs/BTSs,
GERAN and also the core network need to include the support for the A-interface.

The introduction of Iu-cs interface would mean a relatively modest enhancement to BSS
because most of the mechanisms (e.g. for MM/SS) are already introduced with Iu-ps.

Full alignment between UTRAN and GERAN would also allow for complementary deployment
of UTRAN and GERAN in an area depending on the specific operator situation regarding e.g.
available spectrum, traffic load and installed infrastructure capabilities. All in order to obtain a
satisfactory service coverage in an operating area.
It is proposed, to adopt the GERAN reference architecture that includes Iu-cs for the Stage 2 and
to prepare a liaison statement to SA to propose the reference architecture for GERAN.

5. References
[1] Tdoc SMG2 GERAN 2e00-1217 Proposed Work Item: Support of UMTS CS Services on
GERAN and GSM-UMTS CN
[2] Tdoc SMG2 GERAN 2e00-1123 Support for CS Domain to UMTS CN in GERAN
[3] Tdoc GAHW-000070 Comments on A/Iu-cs, TSG GERAN Workshop in Munich, 9-13
October 2000
[4] GSM 03.51 v0.0.1 GERAN Overall Description, Stage 2
[5] 3GPP TR 23.821 v1.0.1 Architectural principles for Release 2000
[6] 3GPP TS 23.002 v3.3.0 or later
[7] Tdoc GAHW-000047 Migration Scenarios for GERAN CS Domain, TSG GERAN Workshop
in Munich, 9-13 October 2000