Gb over IP in Release B10

Functional Feature Description

Gb over IP
In Release B10

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
1

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

Contents

1. GLOSSARY......................................................................................................... 3
2. REFERENCE ....................................................................................................... 3
3. SCOPE ............................................................................................................. 4
4. INTRODUCTION .................................................................................................. 5
5. FEATURE OVERVIEW ............................................................................................ 5
5.1

End-to-End architecture................................................................................ 5

5.2

Protocol stack............................................................................................ 6

5.3

Dimensioning ............................................................................................. 7

6. DETAILED DESCRIPTION......................................................................................... 7
6.1

Configuration of the GboIP stack in MFS ............................................................ 7

6.2

Load sharing.............................................................................................. 7

6.3

Redundancy handling ................................................................................... 8

6.4

Synchronization.......................................................................................... 9

6.5

QoS management.......................................................................................10

6.6

Security ..................................................................................................10

7. OPERATION AND MAINTENANCE..............................................................................10

7.1

Configuration ...........................................................................................10

7.2

Supervision ..............................................................................................11

7.3

Performance Monitoring ..............................................................................12

8. HW COVERAGE ..................................................................................................12

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
2

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

1. GLOSSARY

BSS

Base Station Subsystem

BSS GP

BSS GPRS Processing

DSCP

DiffServ Code Point

GboIP

Gb interface over IP

GE

Gigabit Ethernet

GPRS

General Packet Radio Service

GP(U)

GPRS Processing Unit

GSM

Global System for Mobile communications

MFS

Multi-BSS Fast packet Server

NS

Network Service

NSEi

Network Service Entity Identifier

NS-VC

Network Service Virtual Circuit

PS

Packet Switched

RRM

Radio Resource Management

SGSN

Service GPRS Support Node

VRRP

Virtual Router Redundancy Protocol

2. REFERENCE
[REF 1] 3GPP TS 48.016 : GPRS BSS- Serving GPRS Support Node (SGSN) interface : Network Service
[REF 2] 3GPP TS 48.018 : GPRS BSS- Serving GPRS Support Node (SGSN) interface : BSS GPRS
Protocol (BSSGP)

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
3

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

3. SCOPE
The present functional feature description provides detailed information about the Gb over IP
interface, available as an option in the Alcatel-Lucent BSS B10 release.
It includes :

a description of the implementation within the MFS, and

information related to the end-to-end architecture between the BSS and the SGSN.

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
4

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

4. INTRODUCTION
The Gb over IP is a standardized ( [REF 1] & [REF 2] ) protocol stack, allowing for the backhauling
of the Gb traffic over an IP network.
GboIP is an alternative transport solution to the legacy Gb/Frame Relay/E1, allowing to take
benefit from the IP transformation of the mobile networks. As part of it, GboIP allows to connect
to the IP SGSN that have also implemented this protocol stack.
GboIP allows for a cost effective Gb backhauling solution, relying on the IP networks, thus
reducing the network OPEX of GSM Mobile Operators:

Reduction of the cost of backhauling for the Gb traffic,

Simplified field operations ( O&M)

5. FEATURE OVERVIEW
5.1 End-to-End architecture
Figure below illustrates the end-to-end architecture for the Gb interface carried through an IP
network.

Ater(circuit)

E1

PDH/SDH network

TC

Ater(packet)

BSC

MSC
GE
MFS
Gb

Full redundant architecture,

Seen as single gateway IP@

GE

SGSN

Packet Switched Network

Figure 1 : GboIP End-to-End architecture

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
5

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

The MFS is connected to the SGSN through an IP network.

The MFS is connected to an Edge Router through a redundant GE link (see figure below), thus
providing redundancy at network access. The Edge Router is seen as a single gateway IP address,
which means Edge Router implements internal redundancy and VRRP (or equivalent protocol). See
6.3 for more information.

5.2 Protocol stack

Figure below provides an overview of the GboIP protocol stack, implemented at both MFS and
SGSN sides.

MFS

RRM

Cell

RRM Radio resource management

BSS GP Base Station System GPRS Processing
BVC BSS GP Virtual circuit
NS Network Service (Layer
NSEi Network Service Entity Identifier
SNS Sub-Network Sevrice (Layer)

Cell

GP
GP

BSS GP

NS

SGSN

BVCi

BVCi

NSEi

NSEi

NS-Vci (UDP/IP@a, UDP/IP@1)

SNS

UDP/IP
EndPoint a

UDP/IP EndPoint2
UDP/IP EndPoint1

L2/L1(Ethernet)

Figure 2: GboIP protocol stack

The BSS GP application layer is in charge of the processing of the packet traffic coming from a set
of radio cells.
It relies on an underlying Network Service Layer, which hosts the NSEi (Network Service Entity
Identifier). This NS layer manages the communication paths between SGSN NSE and MFS NSE, i.e.
the NS-VCs.
While in the legacy Gb/Frame relay/E1 architecture, the NS-VCs are built with Frame Relay
Permanent Virtual Circuit, in the GboIP architectures, the NS-VCs are made of an association
between a MFS IP Endpoint (UDP port / IP @) and a SGSN IP endpoint.
The under layer is Ethernet.

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
6

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

As a summary:
GboIP relies on a different Network Service Layer than in the Gb/FR/E1 architecture.
BSS GP layer keeps the same role as in the legacy architecture.
=> GboIP is only a modification of the transport layer of the Gb interface.

5.3 Dimensioning
Compared to Legacy Gb over Frame Relay/E1, GboIP induces an additional overhead to the Gb
flow.
While the BSS GP/NS/Frame Relay header overhead is 54 bytes, the BSS GP/NS/UDP/IP/Ethernet
header is 118 bytes.
The overall overhead depends on the traffic flow characteristics (IP packets size). As an average
value, the estimated overhead is in the range of [10-15] percent.
But on the other hand , the E1 granularity effect (i.e. E1 dedicated to GP board) disappears, which
may bring significant saving compared to legacy TDM.
And as an overall conclusion, the benefits regarding the cost of the backhauling are not impacted
by this overhead, since the expected backhauling cost on an IP network will be far below the one
usually observed on legacy PDH/SDH networks.

6. DETAILED DESCRIPTION
6.1 Configuration of the GboIP stack in MFS
IP V4 is supported.
Each GPU is assigned [1-N] NSE. In B10, N=1
Each NSE(i.e. GP/GPU board) supports [1-M] local IP Endpoints. In B10, M=1.
Each NSE IP Endpoint can be assigned up to 16 remote (SGSN) IP Endpoints.

6.2 Load sharing

A weight is assigned to the remote IP endpoints, in

order to provide some load sharing

mechanism. Figure below illustrates the load sharing mechanism, which is implemented on a call
basis.

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
7

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

MFS
RRM/
BSS GP

Cell

MFS
RRM/
BSS GP

Cell
GP
GP

Cell

Cell
GP
GP

SGSN

SGSN
NS
SNS

NS

NSEi

SNS

IP EndPoint a

NSEi

NSEi

IP EndPoint a

IP
EndPoint2
IP
EndPoint1

Weight=2 for IPendpoint1

Weight=1 for IPendpoint2

Cell

call1

1
2

MFS
RRM/
BSS GP

Cell
GP
GP

Cell

Cell
GP
GP

SGSN

SGSN
NS
SNS

NSEi
IP EndPoint a

IP
EndPoint2
IP
EndPoint1

MFS
RRM/
BSS GP

NSEi

NS

NSEi

call2

1
2

IP
EndPoint2
IP
EndPoint1

NSEi

NSEi

call3
SNS

IP EndPoint a

1
2

IP
EndPoint2
IP
EndPoint1

Figure 3: Load sharing mechanism in MFS

In the case IP EndPoint 1 and IP EndPoint 2 of the SGSN are mapped onto different processing units
(different boards for example), the load sharing allows to split and tune the load with respect to
this remote SGSN Hardware.

6.3 Redundancy handling

Internal MFS HW architecture provides N+1 redundancy of the GPU, and 1+1 redundancy of the
switch modules, which are connected to the Edge router (see figure below).
Edge Router

MFS

Sw 1

Sw 1

GPU

Sw 2

GPU

Sw 2

Figure 4: Redundancy architecture at MFS side

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
8

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

Each switch module of the MFS is connected to a switch module of the Edge Router through a GE
link, thus providing a full redundant architecture: No single point of failure for GboIP at MFS side.
Regarding IP routing, Edge router is seen as a single gateway: this requests the Edge Router to
implement VRRP (or equivalent protocol).
MFS implements a permanent path ( from GPU to Edge Router switch module) monitoring
mechanism (for each GPU) to detect failures, and re-route the traffic on the redundant path. The
reactivity of the system allows to avoid service outage in case of failure.

6.4 Synchronization
In the global Mobile Network architecture, an overall synchronization is requested. With the legacy
architecture, the Core Network (MSC, SGSN) is the synchronization source, and the BSS is
synchronized by the Core Network.
In a TDM based transmission architecture, TDM links are used for the propagation of the
synchronization. The MFS retrieves its synchronization from the SGSN through the TDM links.
With the GboIP, this synchronization chain is broken, and another mechanism is required. Two
options are possible, depending on the BSC type:

MFS connected to the A 9130 BSC: the BSC has the capability to retrieve
synchronization from the Ater circuit TDM links, and synchronizes the MFS through
the Ater packet TDM links

MFS connected to the A 9120 BSC: a TDM link between the TC and the MFS is
required.

Figure below illustrates the synchronization chain in the two cases.

Case 1 : MFS connected to BSC Ev

Case 2 : MFS connected to BSC

Synchronisation retrieved from BSC Ev

Synchronisation retrieved from TC

E1

PDH/SDH networkA

BSC

E1

Ater(circuit)

PDH/SDH networkA

TC

BSC

Ater(packet)

MSC

MFS

Ater(circuit)

TC

Ater(packet)

E1 between TC and MFS,

dedicated to synchro

MSC

MFS

Figure 5 : BSS synchronization chain with GboIP

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
9

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

6.5 QoS management

GboIP traffic is divided into two traffic classes:

Data class, including the user data as well as the signaling of the BSS GP application layer

Signaling class, including the signaling exchanges (i.e. for management of the NS-VCs, see
Figure 2) between the two peer Network Service application layers.

Each class is assigned a configurable layer 3 priority (DSCP) or layer 2 priority (802.1 P).

6.6 Security
MFS software implements basic defense mechanisms against Denial Of Service:
Limited number of UDP ports are opened
Source address filtering (i.e. only traffic from known remote SGSN IP addresses is processed) in
order to prevent from flooding attempts.

In addition, security of the Gb link has to be handled by the transport network, and the following
recommendations shall be followed:
MFS locally connected to the SGSN : firewalls shall allow to protect LAN from the internet attacks.
MFS remotely connected to the SGSN (through IP backbone): VPN connection between MFS and
SGSN shall be established (e.g. MPLS tunnel). IPSec may be used as an option in order to reinforce
the security of the Gb link.

7. OPERATION AND MAINTENANCE

OMC-R provides all required management facilities for the GboIP. Sections below describe the
main O&M management principles.

7.1 Configuration
To set up a Gb over IP interface, the following parameters need to be configured on the MFS:

Definition of the MFS part of the Gb:

- Transport mode of the Gb interface : Frame Relay or IP. Defined per BSS (i.e. a pool of GPU
boards)

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
10

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

- Definition of the MFS IP Endpoints (set of IP addresses / UDP ports):

- IP address of each GPU board : A base IP address is configured, and all GPu IP addresses
are automatically computed and assigned (range of IP addresses per MFS has to be
provisioned).
- UDP port number of the GPU board (or for each NSE if several NSEi are supported per
GPU board).
Recall: In B10, there is one NSE per GP/GPu (see 6.1).

Definition of the SGSN part of the Gb

Per NSE (local IP Endpoint), configuration of the remote (i.e. SGSN) IP Endpoints:
-

SGSN IP address

SGSN UDP port

Weight of the remote IP EndPoint for signalling traffic (see load sharing
mechanism in 6.2)

Weight of the remote IP EndPoint for user traffic

Recall: In B10, there is one NSE per GP/GPu, and one local IP endpoint per NSE (see 6.1).

Definition of the routes

-

Configuration of the Gateway IP addresses for the MFS

QoS parameters
- Per traffic class (see 6.5):

Configuration of the Layer 3 Priority (DSCP)

Configuration of the Layer 2 priority

Definition of the parameters to check path GboIP availability

-

NS_ALIVE parameters for the end-to-end monitoring of NS-VCs

7.2 Supervision
In case of configuration mismatch ( no gateway IP address is configured, no GPU base IP address,
wrong SW version, wrong MFS type), the activation of the IP mode for the Gb is refused by MFS.
Additionally, the following alarms are provided specifically for the GboIP:

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
11

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Gb over IP in Release B10

Path failure between a GPU and the Edge Router switch function (an alarm is raised if both
primary and redundant paths are lost).

Loss of the end-to-end communication with peer SGSN IP end point (which is permanently
monitored through an health-check)

Note: for a given NSE, if the end-to-end communication with peer SGSN NSE is broken, the cells
attached to the GPU (NSE) are GPRS disabled (i.e. disabled regarding packet traffic).

7.3 Performance Monitoring

Specific additional counters are added to monitor the performances of the GboIP:

Period of unavailability of a NS-VC (per SGSN IP endpoint)

Per NS-VC, Nb of Kbytes received /transmitted. This parameters may be used for the tuning of
the transmission network parameters (bandwidth between SGSN and MFS).

8. HW COVERAGE
The GboIP is supported on the following MFS generations:
9135 MFS (legacy):

support on DS10 generations, through HW upgrade of the switch rack (MFS to be equipped
with 2 new GE switches).

No support of the GboIP on AS800 generation.

9130 MFS: Support with no hardware impact.

End of Document

Alcatel-Lucent

File
FFUV7CE2.DOC

Reference
3DC 21144 0120 TQZZA

Date
18/09/2007

Edition
02

Page
12

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.