07 - Rn28197en20gla0 - Gprs and Egprs Handling in Bss

GPRS/EGPRS Handling in BSS

RG20 (BSS)
Soc Classification level

1
Nokia Siemens Networks
RN28197EN20GLA0
RN28197EN20GLA0
Objectives
After this module the participants should be able to:
Define GPRS Network structure

Define GPRS Hard and Software requirements
Explain the main functions of PCU plug-in unit in BSC
Explain Gb Interface protocol (Gb over FR and Gb over IP )
Explain GPRS/EGPRS cell parameter
Explain usage of Dynamic Abis (DAP)
Recognize the concept of PCU2 pooling
Describe multi-Gb interface
Apply MML command to interrogate the Gb interface parameter
Apply MML command to modify the GPRS/EDGE parameter in cell

2
RN28197EN20GLA0
RN28197EN20GLA0
GSM Data Solutions
HSCSD-Core
Internet
MSC
BTS
BSC
GPRS Core
Gb-If
SGSN

3
PSTN
GPRS
Backbone
IP Network
GGSN
Internet
RN28197EN20GLA0
RN28197EN20GLA0
Packet switched
Circuit switched
Data
networks
Telephone
networks
Physical circuit
(CONS)
Virtual circuit (VC)

(CONS)
End to end connection (call)

establishment needed
Dedicated resources (e.g. PCM-tsl)
for one user are reserved during call
establishment
Only 30-40% of resources are
effectively used for speech transfer
Speech is transferred in real time
Speech does not accept delays
Errors in transmission are not so
critical for speech
Charging is usually based on time
4
No VC
(CLNS)
No connection needed
Resources are shared between different
user sessions, not dedicated
Resources are requested on demand,
more efficient use
Packets are not sent in real time
buffering and delay
Error correction and detection possible
Charging is usually based on volume
number of packets
RN28197EN20GLA0
RN28197EN20GLA0
GSM and GPRS Networks
PSTN
Network
Short Message
Service Centre
SMSC
Home Location
Register
MSC
PCU
Serving GPRS
Support Node
InterPLMN
Network
BG
Border
Gateway
Domain
Name
Systems

5
HLR
Billing
System
BSC
BTS
SS7
NW
SGSN
Charging
Gateway
Internet
GPRS
Backbone
IP Network
DNS
Integrated Network
Management
CG
Corporate
GGSN
Legal
Intercept
Intranet
Gateway GPRS Firewall

Support Node
Router
Server
Local
Area NW
RN28197EN20GLA0
RN28197EN20GLA0
Packet Control Unit General Functions

PCU provides a means to control (E)GPRS radio
resources
Radio resource allocation and management
Connection establishment and management
Scheduling
Data transfer, LLC PDU handling
Coding scheme selection
Gb load sharing (uplink) and flow control (downlink)
MS uplink Power Control
Initial timing advance (uplink, downlink)
PCU status info collection - statistics
6
RN28197EN20GLA0
RN28197EN20GLA0
Nokia Siemens Networks PCU Product Family

PCU
Packet Control Unit, a general term for all Nokia GSM/EDGE PCU
versions
General name
Explanation
Name of HW
product variant
First Generation
Packet Control Unit - PCU1
PCU
First generation PCU for BSCE, BSC2E/A,

BSCi and BSC2i
PCU-S

BSCi and BSC2i
PCU-T

BSCi and BSC2i
PCU-B
First generation PCU for BSC3i,

includes two logical PCUs
PCU2-U
Second generation PCU for BSCE, BSC2E/A,

BSCi and BSC2i
PCU2-D
Second generation PCU for BSC3i, includes

two logical PCUs
PCU2-E
Second generation PCU for BSC3i, includes

one logical PCU
Second Generation Packet

Control Unit - PCU2

7
RN28197EN20GLA0
RN28197EN20GLA0
PCU Capacity Figures

PCU-T
PCU-B
PCU2-D, PCU2-U
PCU2-E
HiP4-enhanced MPC
8260A
PowerQUICC II
Integrated
Communications
Processor
HiP4-enhanced MPC
8260A
PowerQUICC II Integrated
Communications
Processor
HiP7-enhanced MPC 8280

PowerQUICC II Integrated
Communications Processor
sRIO-enhanced MPC
8568/8567
PowerQUICC III
Integrated
Communications
Processor
Core Speed (Max)
300 MHz
291 MHz
450 MHz
1.33 GHz
CPM Speed (Max)
166 MHz
208 MHz
300 MHz
533 MHz
64bit 60x Bus Speed
66 MHz
83 MHz
100 MHz
533 MHz
32bit Local Bus Speed
66 MHz
83 MHz
100 MHz
66 MHz
SDRAM in 60x bus
256 Mbytes
256 Mbytes
256 MBytes
1 GBytes
Signal Processors
8 x TMS320VC5420
Dual-Core DSPs
= 16 DSP cores
8 x TMS320VC5420
Dual-Core DSPs
= 16 DSP cores
8 x TMS320VC5510
= 8 DSP cores
6 x TMS320TCI6482
(Himalaya)
= 6 DSP cores
Frequency
100 MHz
100 MHz
200 MHz
1 GHz
Embedded memory
200 kBytes
200 kBytes
320 kBytes
512 kBytes
DSP external SDRAM
No
No
16 MBytes
256 MBytes
BCFs
128
512
Cells/Segments
64
64
64
256
BTS objects
64
64
128
384
TRXs
128
128
256
1024
Abis 16k sub tsls
256
256
256
1024
Abis 16k sub tsls/DSP
20
20
40
216
EDAPs
16
16
16
60
PQ Processor
Max Connectivity

8
RN28197EN20GLA0
RN28197EN20GLA0
PCU-2E: Location, Front View

BCSU
Serial port for

Service
Terminal of
PCU
MML: Check HW
configuration
ZWTI:P:BCSU,<NBR>;
One PCU must be installed in every
BCSU!
9
RN28197EN20GLA0
RN28197EN20GLA0
PCU internal :
Gb
SGSN
Packets in FR
ET
ETs
ETs
ET
ETs
ETs
Abis
Packets in
TRAU frames
BTSs
GSWB
DSP
DSP
11
Power
PC
PCU
internal
bus
Mail Box
DSP
DSP
DSP
DSP
DSP
DSP
68
DMC bus
10
RN28197EN20GLA0
RN28197EN20GLA0
10
PCU2 Overview
PCU2 = 2nd Generation Packet Control Unit
PCU2 implements both Gb and Abis (RLC/MAC) interfaces
PCU2 transmits and receives TRAU frames to and from the Base Stations and
Frame Relay packets to and from the SGSN
PCU2 can be connected to max. 256 x 16 Kbit/s Abis channels, in 256 TRXs in
128 BTSs in 64 Cells/Segments.
PCU2 hardware is embedded in BSCs as a plug-in unit in every BCSU (BSC
Signaling unit)
PCU2-U in BSC2i, PCU2-D (includes two logical PCU units) and PCU2-E (one
logical PCU) in BSC3i
For PCU2-D, one logical PCU unit consists of one Motorola PQII 8280 HiP7
processor and eight TI TMS320C5510 Digital Signaling Processors.
And for PCU2-E, one logical PCU unit consists of one Motorola PQIII 8568 sRIO
processor and six TI TMS320TCI6482 Digital Signaling Processors.
PCU2-E PIU
11
RN28197EN20GLA0
RN28197EN20GLA0
11
PCU2 HW Installation in Flexi BSC

Flexi BSC cabinet
Max 6 working BCSUs +1
redundant BCSU
Max 5 PCU plug-in units per
BCSU (10 logical PCUs per
BCSU)
1-5 PCU-Es
Max number of logical PCUs
: 30
Steps of increase of logical
PCUs
1: 5
2: 10
3: 15
4: 20
5: 25
6: 30
1-5 PCU2-E
physical pius
per BCSU
2000 x 900 x 600 cabinet (HxWxD)

12
RN28197EN20GLA0
RN28197EN20GLA0
12
PCU2 Support in BSC

BCSU 0
PCU2
PCU2
PCU2

13
PCU2
and features are handled according the

weakest unit (PCU, PCU-S)
CS3&CS4 can be activated only when
there is PCU2 on each BCSU on the
same slot
PCU2 can replace a faulty PCU as a
spare part PIU
If there are PCU2 units on the same
slot in every BCSU, then PCU cannot
replace a faulty PCU2
PCU
General rule: In the same slot capacity
PCU
Mixed configurations:
BCSU 1
BCSU 2
RN28197EN20GLA0
RN28197EN20GLA0
13
Asymmetrical PCU configuration

Symmetrical and Asymmetrical PCU configuration
Asymmetrical PCU configuration is available as a feature
Before the feature:
each BCSU within one BSC needs to have the same PCU configuration in terms of PCU number and
types.
e.g. in order to extend PCU capacity (for instance add second PCU in one BCSU) such PCU extension from 1 to 2 units
would need to be done in each and every BCSU the BSC is equipped with (11 extra PCU is needed in case of fully
equipped BSC3i 2000 to add 1 PCU in 1 BCSU!!!)
With the feature:
PCU can be installed and activated according to actual traffic needs with a
granularity 1 in every BCSU separately
each active BCSU can have different number of PCU (depending on actual
traffic requirements), i.e. it may happen that some BCSU have no PCU units
while the other ones have some PCU installed
different PCU types can be mixed in the same BSC/BCSU (restrictions
concerning the same BCSU track exist -> see previous slide)
The redundancy concept has been changed to a primary spare unit concept
The BCSU marked as primary spare must be equipped with the number of
PCU sufficient to replace any of the active BCSU
NOTE: even with the feature it is recommended to increase PCU capacity in BCSUs evenly
to keep load in BCSUs in balance.

14
RN28197EN20GLA0
RN28197EN20GLA0
14
Asymmetrical PCU configuration

Redundancy within Asymmetrical PCU Configuration
2. Faulty BCSU is fixed, primary

spare is returned to spare state
1. Working BCSU gets faulty,

primary spare takes over
(SP-EX) Primary
spare three PCU

cards configured.
Enough PCU cards to
replace any of the
active BCSU units
(WO-EX) Active
BCSU N SP - EX
SP-EX
BCSU N SP - EX
WO-EX
BCSU 0 WO - EX
BCSU 0 WO - EX
WO-EX
WO-EX
WO-EX
...
BCSU two PCU
cards configured
SP-EX
BCSU 0 WO - EX
BCSU three PCU

cards configured
(WO-EX) Active
BCSU N SP - EX
BCSU 1 WO - EX
WO-EX
...
...
BCSU 1 WO - EX
BCSU 1 WO - EX
SE-OU
WO-EX
Faulty BCSU
15
RN28197EN20GLA0
RN28197EN20GLA0
15
Gb over Frame Relay interface configuration
Gb Interface
over Frame Relay
BSC
SGSN
GSWB

16
ET
ET
PAPU
PCU
GSWB
RN28197EN20GLA0
RN28197EN20GLA0
16
Transmission Solutions of Gb Interface

(TDM-based)
SGSN
BSC
1
ET
ET
TCSM
GSWB
GSWB
MSC
2
Transmission
Network
ET
ET
3
ET

17
Frame Relay
network
ET
RN28197EN20GLA0
RN28197EN20GLA0
17
Gb-Interface Protocol Stack ( Gb over FR)
BSSGP
Network Service
control part
FR
BVCI
BSSGP Virtual Connection

Identifier
NSEI
NS-VCI
Network Service Entity

Network Service Virtual Connection Identifier
DLCI
BC
Data Link Connection Identifier

Bearer Channel
L1bis

18
RN28197EN20GLA0
RN28197EN20GLA0
18
Principle of Frame Relay Networks

NSVCI 9
NSVCI 7
NSVCI 9
BSC 1
SGSN 10
40
30
DLCI
DLCI
BC
DLCI
30
10
switch
20
10
BC
DLCI
BC
20
switch
40
DLCI
BC
BC
20
switch
30
BC
Unique
between
neighbors of a
Bearer
Channel
DLCI
BSC 2
30
NSVCI 7
19
10
BC
switch 20
Unique
between
endpoints
of VC
DLCI
NS-VCI: Network Service Virtual Connection Identifier

(end to end)
DLCI: Data Link Connection Identifier (point to point)
RN28197EN20GLA0
In this example, NS-VCI 7 identifies the end to end connection between SGSN and
BSC 2 on the Network Services layer. The DLCI identifiers are valid on a point-topoint basis, between two adjacent Frame Relay nodes.
RN28197EN20GLA0
19
Gb Interface Parameters
SGSN
NSEI 1500
GSWB
BSC
NS-VCI 10
ET 512
Bearer channel 1
ET 512
PAPU 0
NSEI 4000
GSWB
NSEI 1500
PCU 3
ET 513
Bearer channel 2
ET 513
PCU 4
NS-VCI 15

20
NSEI 4000
RN28197EN20GLA0
Each PCU is identified by a Network Service Entity Identifier (NSEI). The PAPUs
can be configured with multiple NSEIs and PCUs, with only one.
RN28197EN20GLA0
20
Gb over IP interface configuration
Gb Interface
over IP
BSC
SGSN
PAPU
IP network
ESB
PCU

21
RN28197EN20GLA0
RN28197EN20GLA0
21
Gb Interface Protocol Stack (Gb over IP)
BSSGP
BVCI
BSSGP Virtual Connection Identifier
Network Service
control part
NSEI
PSEI
NS-VLI
Network Service Entity

Packet Network Service Entity
Network Service Virtual Link Identifier
UDP
LPNBR
RPNBR
Local UDP Port Number

Remote UDP Port Number
RIP
RHOST
Remote IP address
Remote Host Name (If DNS exists)
IP
L2
L1
22
RN28197EN20GLA0
The Network Service Parameter NS-VLI (Network Service Virtual Link Identifier) and
BVCI (BSSGP Virtual Connection Identifier) have to be defined unique at the end
devices. In a simple BSC-SGSN point-to-point connection neighbours are
consequentially end devices. Parameters have to be the same in BSC and SGSN.
While creation LPNBR, RPNBR, NS-VLI and NSEI have to be defined. The BVCI will
be created automatically by the System.
-RDW and RSW are parameters which determine loadsharing statuses between NSVLs
-RDW and RSW can be considered as part of the Network Service control part since
the NSEI controls loadsharing bewteen NS-VLs
-We can create only one NS-VLI per NSEI.
RN28197EN20GLA0
22
PCU2 Pooling Introduction

PCU2 Pooling feature introduces the Packet Service Entity
(PSE) concept.
PSE is a logical concept, which covers several PCU PIUs in BSC. All
PCUs in PSE are serving the same NSE.
From the SGSN, a PSE looks like a single PCU.
Segments are attached to PSE instead of PCU.

Benefit:
When the operator adds a new PCU into PSE, the system
automatically allocates Segments to the new PCU based on each

Segments (E)GPRS load. The operator does not need to do any
changes to the logical network configuration in BSC/SGSN.
Requirements:
PCU2 PIU (min 2, max 50)
Gb over IP (Frame Relay mode not supported)
23
RN28197EN20GLA0
Refer to RG20 Documentation:

Feature descriptions\ Existing features\ Packet switched data\
BSS20106: Packet Control Unit (PCU2) Pooling
RN28197EN20GLA0
23

BSSGP Virtual Connection (BVC)
BVCs are communication paths between peer NS user entities on the BSSGP level. Each BVC
is supported by one NSE and it is used to transport Network Service Service Data Units (NS
SDUs) between peer NS users. Each BVC is identified by means of a BVCI which has end-toend significance across the Gb interface. Each BVC is unique between two peer NSs. Within
BSS the user identifies a cell uniquely by a BVCI. The BVCI value 0000 (hex) is used for
signalling and the value 0001 (hex) is reserved for point-to- multipoint (PTM). PTM is not
supported. All other values can be used for cell identifiers.
The following roules have to be heeded:
NESI must be identical and unique at BSS and SGSN side
One PCU is equivalent to one NSE (Network Service Entity)
1 PAPU can serve up to 64 PCUs that means 64 NSEs
1 NSE is connected with one ore more permanent virtual connections called NSVC
The BC (Bearer Channel) is defined by PCM and TLS in 64kbit/s steps
DLCI is unique within one bearer channel
DLCI has to be identical one both sides only in case of point-to-point FR
connections
NS-VCI capacity can be controlled with Committed Information Rate (CIR) in
16kbit/s steps
One BC supports several DLCs and can also shared by several NS-VCIs
The sum of the CIR on the BC has to be less or equal to the capacity of BC
BVCI has an end-to-end significance
A cell can be identified by one BVCI
BVCI is unique inside one NSE
one NS-VCI supports several BVCs
BVCI = 0 is reserved for signalling purposes inside one NSE.
RN28197EN20GLA0
24
Exercise: Read out Gb over FR configuration

SGSN
BSC
BCSU=_____ PCU index= _____
PAPU
NSEI__________
PCM= ____ TSL________
Bearer Rate=_____
Bearer name=__________________________
NS-VCI=______
NS-VCI=______
DLCI=_____
CIR=_____
PCM= ____ TSL________

Bearer Rate=_____
Bearer name=__________________________
DLCI=_____
CIR=_____
NSEI__________
NS-VCI=___
Name _____
NS-VCI=___
Name _____

NSEI__________
NSEI__________
PCM= ____ TSL________
NS-VCI=______
Bearer Rate=_____
Bearer name=__________________________
DLCI=_____
NS-VC=______
PCM= ____ TSL________

Bearer Rate=_____
Bearer name=__________________________
DLCI=_____

25
CIR=_____
NS-VCI=___
Name _____
NS-VCI=___
Name _____
CIR=_____
RN28197EN20GLA0
Exercise: Read out Gb over FR Interface configuration. Duration: approx. 20min

Fill out the missing information on the slide. Write down the used MML commands.
1. Which command group handled the Frame Relay Bearer Channel?
Command:___________________________________________________________
2. How can you output the used Frame Relay Parameter?
Command:___________________________________________________________
3. Fill in all Network Service layer data into the slide.
Command:___________________________________________________________
4. What is the command to change the NSVCI state?
Command:___________________________________________________________
RN28197EN20GLA0
25
Exercise: Read out Gb over IP configuration

SGSN
BSC
PAPU
NSEI________
NSEI________
PSEI________
PSEI_______
Local UDP port=______
NSVLI=___________
Remote UDP port=______

Local IP=_____________________
RDW=_____

RSW=_____
Local IP=_____________________

NSEI________
NSEI________
PSEI=_______
PSEI________
RDW=_____
Local IP=_____________________

26
NSVLI=___________
RSW=_____

Local IP=_____________________
RN28197EN20GLA0
Exercise: Read out Gb over IP Interface configuration. Duration: approx. 20min

Fill out the missing information on the slide. Write down the used MML commands.
1. Which command group handled the Gb over IP license?
Command:___________________________________________________________
2. How can you output the network interface?
Command:___________________________________________________________
3. Which command can you output the static route?
Command:___________________________________________________________
4. What is the command to check the PSEI and NSVCI?
Command:___________________________________________________________
RN28197EN20GLA0
26
GPRS cell specific parameter

Segment specific
parameters:
GPRS enable
GENA
BTS specific
parameter:
EGPRS enable
EGENA
Transceiver specific GPRS enabled

TRX
parameter:
GTRX
MML:
ZEQO:SEG=<x>:GPRS;
MML:
ZEQO:BTS=<x>:GPRS;
MML:
ZERO:SEG=<x>,TRX=<x>;
Segment-1
Example:
BTS-1
B
Segment1:
GENA=Y
(E)GPRS territory TRX1
BTS1:
EGENA=Y
TRX2
TRX1:
GTRX=Y
TRX2 and 3:
GTRX=N
TRX3

27
RN28197EN20GLA0
First the operator has to activate the GPRS feature in the BSC with the cell- specific
parameter GPRS enable (GENA) and define which TRXs are capable of GPRS with
the parameter GPRS enabled TRX (GTRX) . To activate the EGPRS feature, the
operator uses the BTS-specific parameter EGPRS enable (EGENA) . The BTS can
contain both EDGE-capable and non-EDGE-capable TRXs (HW), if GPRS is
disabled in the non-EDGE-capable TRXs. The operator needs to define which TRXs
are capable of EGPRS with the parameter GPRS enabled TRX (GTRX) .
Only after the BSC has an update on the BTS parameters and other parameters
indicating GPRS usage, does it count the number of default and dedicated GPRS
time slots in the BTS and selects a TRX where it starts to establish the GPRS
territory.
The BSC can upgrade or downgrade the number of radio resources allocated for
GPRS use according to the varying needs of the circuit switched and GPRS traffic.
RN28197EN20GLA0
27
Territory Method in BSC
TRX 1
BCCH
TS
TS
TS
TS
TS
TS
TS
TRX 2
TS
TS
TS
TS
TS
TS
TS
TS
Max
GPRS
Capacity
CMAX
Additional
GPRS
territory
Default
GPRS
Capacity
CDEF
Territory border moves based on

Circuit Switched and GPRS traffic
load

28
Circuit
Switched
Territory
Packet
Switched
Territory
Dedicated
GPRS
Capacity
CDED
RN28197EN20GLA0
The territory method is the same for GPRS and EGPRS.

The BSC divides radio resources semipermanently between circuit switched services
and GPRS, thus forming two territories. The PCU uses the GPRS territory resources.
The initial territories are formed on a BTS-to-BTS basis according to the operatordefined parameters. The BSC can later broaden the GPRS territory based on the
actual need and according to the requests of the PCU.
The circuit switched services have priority over GPRS in channel allocation within
common resources. GPRS releases its resources as soon as they are needed for
circuit switched traffic. Within a cell, all the Full Rate and Dual Rate traffic channels
are GPRS capable. GPRS capacity can be divided into three types:
default GPRS capacity
dedicated GPRS capacity
additional GPRS capacity.
GPRS has a predefined set of resources which it can utilise when the circuit switched
load allows. This is referred to as the default GPRS capacity. Part of these default
traffic channels can be reserved solely for GPRS and this means they are blocked
altogether from circuit switched use. This is referred to as the dedicated GPRS
capacity. The user can modify these two capacities by using the respective
parameters default GPRS capacity (CDEF) and dedicated GPRS capacity (CDED) .
Additional GPRS capacity is referred to with radio time slots that are above and
beyond the default GPRS capacity and that the BSC has allocated for GPRS use
according to the requests of the PCU. GPRS territory size can be restricted by the
user-modifiable parameter max GPRS capacity (CMAX) . There is a GPRS territory
update guard time defining how often the PCU can request new radio time slots for
GPRS use.
RN28197EN20GLA0
28
GPRS Capable Traffic Channel

Within a cell, all the Full Rate and Dual Rate traffic channels are
GPRS capable.
GPRS territory is a set of consecutive TSLs, excluding
TSLs that are not capable of full rate traffic
non-TCH channels (BCCH, SDCCH)
permanent half rate TSLs
blocked TSLs
TSL0 when BB Hopping is used
transparent HSCSD calls.

29
RN28197EN20GLA0
RN28197EN20GLA0
29
Exercise: Calculating GPRS radio capacity

BCCH
Parameter:
SDCCH
Segment1:
TRX1
TRX2
TRX3
GENA=Y
EGENA=N
CMAX=100
TRX1 and 2:
GTRX=Y
TRX 3:
GTRX=N
Capacity calculation rules:
the product of default GPRS capacity (CDEF) parameter and the

number of radio time slots (RTSL) is rounded down to a whole
number.
if default GPRS capacity (CDEF) parameter value is > 0 but the

rounded product equals 0, then the territory size 1 is used
default GPRS capacity (CDEF) parameter minimum value is 1.

max GPRS capacity (CMAX) parameter minimum value is 1 (range 1100%).

30
RN28197EN20GLA0
Exercise see next page
RN28197EN20GLA0
30

Exercise: calculating GPRS radio capacity. Duration: approx. 10min
Given is a segment with three FR TRXs. The general GPRS parameter are shown at the slide.
1. How many RTSL are maximal GPRS capable?
_________________________________________________________________________
2. How many RTLS are default and dedicated if CDEF=1 and CDED=1? Please draw them
into the delineation.
__________________________________
TRX1
__________________________________
TRX2
__________________________________
TRX3
3. How many RTLS are default and dedicated if CDEF= 100 and CDED=100? Please draw
them into the delineation.
__________________________________
TRX1
__________________________________
TRX2
__________________________________
TRX3
4. How many RTLS are default and dedicated if CDEF=40 and CDED=20? Please draw them
into the delineation.
TRX1
__________________________________
__________________________________
TRX2
__________________________________
TRX3
5. How many RTLS are default and dedicated if CDEF=40 and CDED=20 and for TRX3 the
parameter GTRX is set = (GTRX=Y)? Please draw them into the delineation.
__________________________________
__________________________________
__________________________________
RN28197EN20GLA0
TRX1
TRX2
TRX3
31
Routing Area
RAI = MCC+MNC+LAC+RAC
Routing
Area
PCU n
Cell
RA 2
BTS
BTS
BTS
PCU 1
SGSN
RA n
RA 1
BTS
BTS
PCU 0
BTS
BTS
BSC
Rules:
Routing Area
Routing Area
32
Location Area
Cell
LA
Location
Area
RN28197EN20GLA0
Mobility management in the GPRS network is handled in a similar way to the existing
GSM system. One or more cells form a Routing Area (RA ), which is a subset of one
Location Area (LA). The Routing Area is unique within a Location Area. As Routing
Areas are served by SGSNs, it is important to keep in mind the network configuration
plan and what has been defined in the SGSN, before configuring the BSC side. One
Routing Area is served by one SGSN. When creating a Routing Area the user
identifies the obligatory parameters mobile country code (MCC) , mobile network
code (MNC) , location area code (LAC) , and routing area code (RAC) . Routing
Areas are created in the BSDATA. The MCC, MNC, LAC and RAC parameters
constitute a routing area identification (RAI).
In other words: The Routing Area and the BTS are linked logically together by the
RAI. Routing Areas are used in the PCU selection algorithm which selects a serving
PCU for the cell when the operator enables the GPRS traffic in the cell.
Optimal size of the RA:
to big: high paging signalling
to small: many routing area updates
RN28197EN20GLA0
32
Exercise: Read out GPRS RNW configuration

LAC______
BSC
MCC= _____
RAC_____
BTS____
NSEI__________
MNC= _____
BTS____
BTS____
BVCI=_____
BTS____
RAC_____
BVCI=_____
BVCI=_____
RAC_____
BTS____
BVCI=_____
BTS____
BVCI=_____
LAC______
RAC_____
BTS____
LAC______
BTS____
RAC_____
NSEI__________
BTS____
BVCI=_____
BTS____
BVCI=_____
RAC_____
BTS____
BTS____
BVCI=_____
RAC_____
BTS____
BTS____
RAC_____
BTS____
BTS____
RAC_____
BVCI=_____
BTS____
BVCI=_____
BTS____

33
RN28197EN20GLA0
Exercise:
Write down the used MML commands. Use the slide as template!
1 How can you read out existing Routing Area Codes (ZE...)?.
Command:___________________________________________________________
________
2. Fill out Routing area identification (RAI = MCC, MNC, LAC and RAC) into the slide
above.
3. Each active GPRS cell is represented via a BVC (BSSGP virtual Connection) in
the NSE (Network Service Entity) and a NSE is specified via as one PCU. Find out
which BTS BVCI relationship is existing (ZEQ) and which PCU is handling which
NSEI (ZFX).
Command:___________________________________________________________
Command:___________________________________________________________
4. Please connect the related BVCI and BTS bubbles in the slide.
RN28197EN20GLA0
33
EGPRS Coding Schemes
SGSN
BSC
data
PCU

34
coding
Radio interface block (1392 bits in 8-PSK)
BTS
RN28197EN20GLA0
RN28197EN20GLA0
34
GPRS Coding Schemes
9.05
CS2
13.4
CS3
15.6
CS4
21.4
Error
Correction
CS1
Data
Coding Data Rate

Scheme per TSL (kbit/s)
More Data
=
Less Error
Correction
CS1 & CS2

Implemented in ALL NSN BTS without HW
change
CS3 & CS4
Will not fit in normal 16kbit/s Abis TRAU frame
PCU2 PIU required
35
RN28197EN20GLA0
RN28197EN20GLA0
35
8-PSK modulation
EDGE
Modulation
8-PSK,
3bit/sym
270.833 ksps
Symbol rate
Payload/burst
346 bits
Gross rate/ time slot 69.2 kbps
GPRS
GMSK.
1bit/sym
270.833 ksps
114 bits
22.8 kbps
0, 1, 0
8-PSK
0, 0, 0
0, 1, 1
0, 0, 1
1, 1, 1
1, 0, 1
1, 1, 0
1, 0, 0

36
RN28197EN20GLA0
The idea behind increasing the data rates is the introduction of 8-PSK (Phase Shift
Keying), a linear higher order modulation in addition to the existing GMSK (Gaussian
Minimum Shift Keying). An 8-PSK signal is able to carry three bits per modulated
symbol over the radio path, while a GMSK signal carries only one bit per symbol. The
carrier symbol rate (270.833 ksps) of standard GSM is kept the same for 8-PSK, and
the burst length is identical to the current GMSK using the same 200 k carrier
spacing. With multi-slot reservation, EDGE offers an evolution path for GSM to
support medium rate multimedia applications. The user can send more data per radio
time slot with the same amount of air time used and operators do not need to invest
in another frequency band and license to offer higher data rate services like mobile
multimedia.
RN28197EN20GLA0
36
EDGE Modulation and Coding Schemes

MCS
Modulation
Code Rate
Family
User Rate
GMSK
0.53
8.8 kbit/s
GMSK
0.66
11.2 kbit/s
GMSK
0.8
14.8 kbit/s
GMSK
17.6 kbit/s
8PSK
0.37
22.4 kbit/s
8PSK
0.49
29.6 kbit/s
8PSK
0.76
44.8 kbit/s
8PSK
0.92
54.4 kbit/s
8PSK
59.2 kbit/s

37
RN28197EN20GLA0
RN28197EN20GLA0
37
Dynamic Abis Allocation Introduction

Background
GSM/GPRS radio timeslot
data can be fitted into one
16 kbit/s sub timeslot in
Abis-if
EDGE introduces data
throughputs up to ca. 60
kbit/s over air
up to 5*16 kbit/s sub
timeslots needed over
Abis/radio timeslot

38
Abis capacity needs to be

expanded (even up to 4
times higher)
Dynamic Abis Allocation

1*16 kbit/s "Master" as fixed/radio
timeslot
1 4*16 kbit/s "Slaves"
dynamically as per needed/radio
timeslot
RN28197EN20GLA0
RN28197EN20GLA0
38
NSN Dynamic Abis solution

PCU frame types
PCU data frame
used when TRX not in EDGE mode
only able to carry CS-1 and CS-2
PCU master data frame
used when TRX is in EDGE mode
carries CS-1 or MCS-1 on its own and CS2...CS-4 and MCS-2...MCS-9 with the help
of slave frame(s)
includes pointers to the slave frames
PCU slave data frame
carries additional data that does not fit in
PCU master data frames
PCU random access frame
PCU synchronisation frame
39
CS- 1
CS- 2
EDGE TRX in non- EDGE

mode or non- EDGE TRX
CS- 1
CS- 2
M + S
CS- 3
M + S
CS- 4
M + S
EDGE TRX in
EDGE mode
MCS- 1
MCS- 2
M + S
MCS- 3
M + S
MCS- 4
M + S
MCS- 5
M + S
MCS- 6
M + S
MCS- 7
M + S
MCS- 8
M + S
MCS- 9
M + S
ret rans
PCU dat a frame
PCU mast er data frame
PCU slave dat a frame
RN28197EN20GLA0
RN28197EN20GLA0
39
NSN Dynamic Abis solution

Fixed channels and EDAP
For each GPRS radio timeslot on each
EDGE TRX, one fixed 16-kbps channel is
allocated on the Abis for the transfer for
PCU master data frames.
PCU slave data frames are allocated in a
common pool, the EDAP (EDGE Dynamic
Abis Pool).
12 PCM timeslots as the maximum size of
EDAP.
A master channel and its slave channels
and therefore the entire EDAP must be on
the same Abis PCM.
Abis PCM
OMU, TRX sigs

TRX 1
TRX 2
TRX 3
TRX 4
TRX 5
TRX 6
TRX 7
TRX 8
TRX 9
EDAP

40
RN28197EN20GLA0
Note
However, EDAP size is the same for both DL and UL directions, so it is not possible
to set different EDAP sizes for DL and UL directions.
RN28197EN20GLA0
40

07 - Rn28197en20gla0 - Gprs and Egprs Handling in Bss

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

07 - Rn28197en20gla0 - Gprs and Egprs Handling in Bss

Încărcat de

Drepturi de autor:

Formate disponibile

GPRS/EGPRS Handling in BSS

GPRS/EGPRS Handling in BSS

Soc Classification level

GPRS/EGPRS Handling in BSS

Define GPRS Network structure

Soc Classification level

GPRS/EGPRS Handling in BSS

GSM Data Solutions

Soc Classification level

GPRS/EGPRS Handling in BSS

Virtual circuit (VC)

End to end connection (call)

GPRS/EGPRS Handling in BSS

GSM and GPRS Networks

Soc Classification level

Gateway GPRS Firewall

GPRS/EGPRS Handling in BSS

Packet Control Unit General Functions

GPRS/EGPRS Handling in BSS

Nokia Siemens Networks PCU Product Family

First generation PCU for BSCE, BSC2E/A,

First generation PCU for BSCE, BSC2E/A,

First generation PCU for BSCE, BSC2E/A,

First generation PCU for BSC3i,

Second generation PCU for BSCE, BSC2E/A,

Second generation PCU for BSC3i, includes

Second generation PCU for BSC3i, includes

Second Generation Packet

Soc Classification level

GPRS/EGPRS Handling in BSS

PCU Capacity Figures

HiP7-enhanced MPC 8280

Core Speed (Max)

CPM Speed (Max)

64bit 60x Bus Speed

32bit Local Bus Speed

SDRAM in 60x bus

DSP external SDRAM

Abis 16k sub tsls

Abis 16k sub tsls/DSP

Soc Classification level

GPRS/EGPRS Handling in BSS

PCU-2E: Location, Front View

Serial port for

GPRS/EGPRS Handling in BSS

GPRS/EGPRS Handling in BSS

GPRS/EGPRS Handling in BSS

PCU2 HW Installation in Flexi BSC

Max 6 working BCSUs +1

2000 x 900 x 600 cabinet (HxWxD)

GPRS/EGPRS Handling in BSS

PCU2 Support in BSC

Soc Classification level

and features are handled according the

General rule: In the same slot capacity

GPRS/EGPRS Handling in BSS

Asymmetrical PCU configuration

With the feature:

Soc Classification level

GPRS/EGPRS Handling in BSS

Asymmetrical PCU configuration

2. Faulty BCSU is fixed, primary

1. Working BCSU gets faulty,

PCM= TSL____

PCM= TSL____

BCSU=_ PCU index= _

PCM= TSL____

BCSU=_ PCU index= _