Gahw#2 (00) 0065: Source: Bellsouth, SBC Title: Geran Protocol Structures Document For: Discussion Agenda Item
Gahw#2 (00) 0065: Source: Bellsouth, SBC Title: Geran Protocol Structures Document For: Discussion Agenda Item
Gahw#2 (00) 0065: Source: Bellsouth, SBC Title: Geran Protocol Structures Document For: Discussion Agenda Item
The current version of the GERAN Stage 2 specification (Ref. [1]) contains a model of the User Plane
Protocol Architecture towards the Core Network PS Domain (first section 4.4), but does not include
equivalent models for the Control Plane or for the Protocols towards to the Core Network CS Domain.
This document proposes additional diagrams to complete the Stage 2 specification, taking into account the
open GERAN Work Item to evaluate a potential evolution of the A Interface and/or the support of the Iu-cs
interface (Ref. [2]).
MS GERAN SGSN
SNDCP SNDCP
LLC LLC
Relay
BSSGP BSSGP
GTP-U GTP-U
Common protocols
Iu influenced protocols
Gb influenced protocols
Figure 1: User Plane Protocols towards Packet Switched Core Network Domain
Page: 1/4
- On the Air Interface, the GSM CS Data Link Layer (LAPDm) is used for the Iu-influenced Control
Plan Protocols in addition to the UTRAN RLC and the existing GSM/GPRS MAC and Physical
Layers. This is in line with the content of section 5.1 of the Stage 2 specification. LAPDm is used
as the Link Layer for all Logical Channels issued from the CS operation and also kept for Real
Time services over Packets (SACCH, FACCH, Common Control CHannels…).
MS GERAN SGSN
GMM/SM GMM/SM
LLC LLC
Relay
BSSGP BSSGP
RANAP RANAP
Common protocols
Iu influenced protocols
Gb influenced protocols
Figure 2: Control Plane Protocols towards Packet Switched Core Network Domain
MS GERAN MSC
MM/CC/SS MM/CC/SS
Relay
BSSAP BSSAP
RR RR RANAP RANAP
Common protocols
Iu influenced protocols
A influenced protocols
Figure 3: Control Plane Protocols towards Circuit Switched Core Network Domain (Alternative 1)
Page: 2/4
The previous diagram shows a lot of commonalities between:
- The Iu-ps and Iu-cs influenced protocols (as expected). It appears that the support in GERAN of
the Iu-cs interface could be provided with a minimum incremental development effort, providing
that the system is upgraded to provide Real Time over Packet services and consequently
upgraded to support the Iu-ps interface. This is especially true if the Iu-ps uses the SS7 based
transport option (only option supported for the Iu-cs interface in UTRAN)
- The Iu-cs and A influenced protocols, since LAPDm and SCCP are used in both cases. The key
differences relate to the transport network (ATM for the Iu-cs, SDM for the A Interface) and in the
Layer 3 Protocols (BSSAP vs. RANAP and RRC vs. RR).
Another problem with this architecture is that both interfaces would have to be supported to continue to
provide CS services to the R99 and older Terminals. This would create a similar situation to the PS domain
where both the Iu-ps and the Gb Interfaces must be supported when an operator wants at the same time to
provide Real Time services over Packets and continue to serve R99 and older GPRS Terminals.
However, considering that RRC must already be enhanced for compatibility with GERAN, it should be
possible to consider another alternative for the Control Plane Protocols towards the CS CN Domain
involving an Iu-based enhanced-A Interface, as shown in the following diagram.
MS GERAN MSC
MM/CC/SS MM/CC/SS
Relay
BSSAP RANAP RANAP BSSAP
04.18 + RRC 04.18 + RRC
SCCP SCCP
MTP3-B MTP3-B
RLC RLC MTP MTP
SSCF-NNI SSCF-NNI
LAPDm LAPDm SSCOP SSCOP
MAC MAC
L2 (AAL5) L2 (AAL5)
A
Um L1 Iu-cs based L1
PHY PHY L1 (ATM) L1 (ATM)
Evolved A
Common protocols
Iu influenced protocols
A influenced protocols
Figure 4: Control Plane Protocols towards Circuit Switched Core Network Domain (Alternative 2)
The key characteristics of this alternative are:
- Both BSSAP and RANAP are supported with the enhanced-A Interface. BSSAP would be used
for R99 and older Terminals while RANAP would be used for R00 Terminals. This does not
appear to be critical or at least it should be in line with the assumed definition of a 2G/3G MSC.
The Iu-based enhanced-A Interface would use the Iu-cs Transport Layers, which could possibly
be similar to the Iu-ps Transport Layers.
- RRC is enhanced to include all R99 RR procedures as defined in the GSM 04.18. That means
that the R00/R4 04.18 (or 44.018) will include the RRC procedures required for GERAN and not
that the RRC specification is enhanced to support specific GERAN procedures.
- It is not necessary to support both the A and enhanced-A Interfaces simultaneously, since the
support of the enhanced-A Interface would be totally transparent to the MS.
- Because the type of GERAN-CN interface would be transparent to the MS, all R99 features and
capabilities, including DTM, would be supported through an enhanced-A interface without impact.
More accurately, DTM would be supported in a Gb/enhanced-A configuration while simultaneous
CS/PS operation would also be possible, as in UMTS, through an enhanced-A/Iu-ps
configuration.
Page: 3/4
- The support of the enhanced-A Interface would only be an option, considered beneficial when the
network is upgraded to support Real Time Service over Packets.
A more complete analysis of the rationale for supporting this new Iu-based enhanced-A Interface is provided
in a separate contribution.
References:
1. 3G TS 43.051 GERAN Overall Description – Stage 2, Tdoc GP-000471, TSG-GERAN#1
2. Work Item Description for GERAN/UTRAN interface evolution, Tdoc GP-000478, TSG-GERAN#1
3. 3G TS 23.060 General Packet Radio Service (GPRS) Service description; Stage 2
4. 3G TR 25.410 Version 3.2.0: UTRAN Iu Interface: General Aspects and Principles
5 Analysis of GERAN R00 RR Functionality, Tdoc 2g00-092, Nokia, GERAN AdHoc#1
Page: 4/4