03 Mn1707eu11mn 0001 Features Ps

BR7.
0 Features Siemens
BR7.0 Features
Contents
1.1 High speed Gb Interface 4
1.2 Quality of service for ps service 20
1.3 Scheduler Enhancements 28
1.4 Dual transfer mode 36
1.5 Network assisted cell change NACC 44
1.6 NCCR from GPRS to UMTS 54
1.7 Enhanced Flow Control 66
1.8 Multiple PCU Pooling 76
1.9 Extended Cells for CS and PS 84
1.10 Enhanced Dynamic Allocation 92
1.11 Overheating Management 94
1.12 Extended Uplink TBF 96
MN1707EU10MN_0002
1
© 2003 Siemens AG
Siemens BR7.0 Features
2 MN1707EU10MN_0002
© 2003 Siemens AG
BR7.0 Features Siemens
Streaming >> RT services Multiple PCU pooling
Quality of Service
support acc. Rel. 99 High speed
Gb
Network assisted SGSN
cell change
Enhanced Flow control

NCCR G>U
on Gb >> PFC level
8 PCMB lines
Fig. 1 PS news in BR8.0
MN1707EU10MN_0002
3
© 2003 Siemens AG
1.1 High speed Gb Interface

1.1.1 Basics
Up to BR7.0 the Gb interface is realized by FR over E1/T1. The connection can be
done in 4 different ways.
• NUC through MSC to the SGSN
• NUC through MSC and then via Frame Relay network to the SGSN.
• a direct line and then via Frame Relay network to the SGSN
• a direct connection to the SGSN.
In BR8.0 the High Speed Gb Interface is IP over Ethernet. Fast Ethernet (up to 100
Mbps) and Gigabit Ethernet (up to 1 Gbps) with IPv4 are supported. The standard is
Ethernet II or IEEE802.3.
The connection uses standard twisted pair copper cables (up to 100m). With external
Router the access to WAN is possible.
The benefit is that it allows utilizing a broad spectrum of packet network features
offered by an IP network as well as a reliable, cost- and effort-efficient broadband
access.
4 MN1707EU10MN_0002
© 2003 Siemens AG
Gb interface
realisation possibilities
up to BR7.0 TRAU MSC 1
2
E1/T1-Line
P
C E1/T1-
BSC U E1/T1-Line Frame Relay Line SGSN
3 network
E1/T1-Line 4
Fig. 2 BR7.0 solution: The different realization possibilities of the Gb interface
New Gb interface
realisation possibilities
In BR8.0
WAN
E R R
P
S
C
A
U SGSN
M
BSC
Fig. 3 BR8.0 new realization possibilities of the Gb interface
MN1707EU10MN_0002
5
© 2003 Siemens AG
1.1.2 SBS Implementation
Hardware in BSC
This feature requires some modifications of BSC’s HW. Two new boards need to be
installed on BSCs:
• ESAM
• PPXX_v2
The ESAM boards are connected to all the PPXU_V2 boards.
6 MN1707EU10MN_0002
© 2003 Siemens AG
BSC1
Abis
#1 High
Q/STLP
Speed
Gb
PPXUv2
ESAM
with
Ethernet
SNAP
#12
Switch
FE or GE
PPXUv2
Q/STLP
24 * FE
Fig. 4 BSC changes
MN1707EU10MN_0002
7
© 2003 Siemens AG
ESAM board
ESAM board provides Ethernet switch as well as it covers DK40 / CPEX functionality
The ESAM boards can be inserted:
• in the same slots of the DK40 boards considering HC BSC/72 equipment
• in the same slots of the CPEX boards considering HC BSC/120 equipment.
PPXX boards
The PPXX boards shall be replaced with PPXX_V2 boards. The new PPXXv2 board
provides duplicated and direct Ethernet interface to the ESAM boards as well as it
covers whole PPXX functionality.
8 MN1707EU10MN_0002
© 2003 Siemens AG
Fig. 5 ESAM board
A-bis Interface
EEPROM1
FPGA1
C
O
N PCI Bus to A-bis to/from eBSC
N Pentium Through Serial link
E
C
T PCI Bus MAGNETICS
O / RJ11 FAST
R Ethernet
ETHERNET
FPGA2
Controller a EEPROM
PCI Bus MAGNETICS

/ RJ11 FAST
Ethernet
ETHERNET
EEPROM2
Controller b EEPROM
Fig. 6 PPXXV2 board
MN1707EU10MN_0002
9
© 2003 Siemens AG
Configuration of connection BSC - SGSN
There are two possibilities of configuring the NS-VC:
Static
This configuration method can be used in case of point-to-point connection needs to
be created (e.g. direct connection between BSC and SGSN) or an IP network is
between the SGSN and the BSS and fully meshed connectivity is not required.
Operator is responsible for creation and correctness of all configuration information in
the SGSN as well as in BSS, i.e.: local IP endpoints, remote IP endpoints, data
weights, signaling weights.
Dynamic
This configuration method can be used for creating of a NS-VCs when the SGSN and
the BSS are connected via an IP network and a fully meshed connectivity is
preferred.
The Operator creates all local IP endpoints and defines local data and signaling
weights. He makes BSC informed about one SGSN IP endpoint (start up remote IP
endpoint).
SGSN and BSS exchange data concerning:
• the number of IP-endpoints and their addresses
to build NS-VCs between them
• the signaling and data weight for load sharing
10 MN1707EU10MN_0002
© 2003 Siemens AG
BSC SGSN
PPXU ‘k’
NSE ‘k’
NSE ‘k’
IP endpoint
IP endpoint ‘a’
A
IP endpoint ‘b’
IP network
PPXU ‘l’ NSE ‘l’

IP endpoint
B
NSE ‘l’
IP endpoint ‘c’
IP over Eth
NSE Network Service Entity

1<=k,l<=12
Fig. 7 NS-VC configuration
MN1707EU10MN_0002
11
© 2003 Siemens AG
Redundancy
To provide redundant Gb links in case of IP connection the following mechanisms are
included:
• Supervision of the Gb data path
• Redundancy of the relevant boards:
PPXU redundancy: the Load Balancing scheme already introduced in previous
releases is re-used in the PPXUv2.
ESAM redundancy: Redundancy for ESAM failures is achieved indirectly by the use
of the IP based NS load sharing mechanism. In normal operation the NS load sharing
distributes automatically the traffic over 2 NS-VLs over the two PPXU Ethernet links.
In case of an ESAM crash / Gb link failure all PPXUs notify this.
The Gb data path is supervised on three levels:

• The HW of the Ethernet switch on the ESAM board and the Ethernet controllers
supervises permanently the status of the connected links, interfaces and the
network entities situated at the far end of the link.
• The path PPXU – External Router is supervised on IP layer by periodically sending
and evaluating ‘echo’ packets
• The Network Service test procedure is carried out periodically. This test covers the
whole distance PPXUs – SGSN
12 MN1707EU10MN_0002
© 2003 Siemens AG
Fig. 8 Gb redundancy
MN1707EU10MN_0002
13
© 2003 Siemens AG
1.1.3 Objects for IP SNS

• There is one PCU for each PPXU
• It is possible to have up to 8 NSVLIP per PCU referring to a single ES (one for
each UDP port)
• In case of static configuration it is possible to create up to 16 RNSVLIP per PCU
• Each ES provides an IP address to each PCU, so it is possible to create up to 16
NSVLIP per PCU
• Both in static and dynamic configuration, it is possible for the system to create up
to 16 * 16 NSVCIP per PCU, one for each couple NSVLIP-RNSVLIP. NSVCIP
hierarchically depends on RNSVLIP and NSVLIP
14 MN1707EU10MN_0002
© 2003 Siemens AG
GBSNS
PPXU ES
ESAM
FR IP_V4
PCU
TYPOFNSVCCONF
RNSVLIP NSVLIP
static dynamic
• NSVLLIP • NSVLLIP
• RNSVLIP • STRIPEP
NSVCIP
Fig. 9 Hierarchy of the new objects
MN1707EU10MN_0002
15
© 2003 Siemens AG
1.1.4 Database Parameters

In case of static configuration it is necessary to create a RNSVLIP for each remote
endpoint to configure, specifying each single meshed connection with local endpoint
to allow (by selecting all the connections it is possible to realize the fully meshed
connection even in static configuration). The system will automatically create an
NSVCIP object for each connection specified in the attribute list for the remote
endpoint.
The attribute remote IP endpoint has the two sub-fields IP address and UDP port (of
the related NSEI at the SGSN).
The attributes Weight_data and Weight_signalling are valid for all NSconnections of
each remote IP endpoint.
The attribute NSconnection is used to specify the allowed (meshed) connections to

local IP endpoints. The attribute can either contain a list of the instance numbers of
the local IP endpoints or contain the string “ALL” indicating that the remote endpoint
has a connection to all local endpoints.
16 MN1707EU10MN_0002
© 2003 Siemens AG
Parameter Object Range Description
ETHLINK 0,1 New object to represent the Ethernet link on the

GB interface
ES 0,1 New object to represent the Ethernet Switch for

the GB interface
GBIPLNK 0,1 New object to represent the IP link on the GB

interface
TYPOFAMC BSC 0=DK40,1= CPEX, Type of alarm module card that is used in the
2=ESAM, (1) BSC Rack
TYPOFETH BSC (0)=EthernetII, Type of internet adopted for the internal LAN
1=IEEE802
ROUIPADD0 BSC (NULL), Router IP address 1

aaa.aaa.aaa.aaa
ROUIPADD1 BSC (NULL), Router IP address 2
aaa.aaa.aaa.aaa
SUBNETMASK0 BSC (NULL), Subnet Mask 1
aaa.aaa.aaa.aaa
SUBNETMASK1 BSC (NULL), Subnet Mask 2
aaa.aaa.aaa.aaa
Fig. 10 New parameters in BSC object
GBSNS PCU (0)=FR_fixed, Subnetwork service that is used for the PCU
1=FR_variable,
2=IPv4
TYPOFNSVCCONF PCU Null, 0=Static, Type of NSVC configuration of the NS-VCs for
1=dynamic the IP subnetwork
MTU PCU 68,...,1500, NULL Maximum transmission lenght, size of the

largest packet that can be transmitted over the
ethernet
PORT0 PCU IP adress associated to the first Ethernet
Controller
PORT1 PCU IP adress associated to the second Ethernet
Controller
STRIPEP (IP adress/ PCU aaa.aaa.aaa.aaa/ Start up for the remote IP endpoint (in case of
UDP port) 1024...65535 dynamic configuration)
DIFFWERVSUP PCU NULL, 0=false, Flag to indicate the support of diffserv
1=true
Fig. 11 New parameters in PCU object
MN1707EU10MN_0002
17
© 2003 Siemens AG

TSNPRO PCU NULL, 1 ... 10 Time subnetwork procedure in use
SNSSIZERET PCU NULL, 0 ... 16 SNS size retries before failure notification is
triggered
SNSCONFRET PCU NULL, 0 ... 16 SNS configuration retries before failure
notification is triggered
SNSADDRET PCU NULL, 0 ... 16 SNS add retries before failure notification is
triggered
SNSDELRET PCU NULL, 0 ... 16 SNS delete reties before failure notification is
triggered
SNSSCHWEIRET PCU NULL, 0 ... 16 Number of retries for SNS change weight
procedure before failure notification is
triggered
Fig. 12 Parameters for Subnetwork Service
NAME RNSVLIP 0...15 Remote network service IP link. For each PCU it is
possible to generate up to 16 RNSVLIP objects.
RMTIPEP RNSVLIP aaa.aaa.aaa.aaa Remote IP endpoint IP address
RMTIPEP RNSVLIP 1024...65535 Remote IP endpoint UDP port
WEID RNSVLIP 0...255 The attribute defines the weight threshold for data
WEIS RNSVLIP 0...255 The attribute defines the weight threshold for
signalling
NSCONN RNSVLIP NULL, 0...15 Specifies the allowed NS-VCs to local ip endpoints
Fig. 13 Parameters for RNSVLIP
18 MN1707EU10MN_0002
© 2003 Siemens AG

NSVCLIP 0...15 For each PCU it is possible to generate
up to 16 RNSVLIP objects.
LOCIPEP NSVCLIP 1024 ... Local IP endpoint UP port
65535
IP address NSVCLIP 0,1 Local IP endpoint IP address reference
reference
UDP port NSVCLIP 1024... UDP port
65535
WEID NSVCLIP 0 ...255 Weight_data (not used in static configuration)
WEIS NSVCLIP 0 ...255 Weight_signalling (not used in static
configuration
Fig. 14 Parameters for NSVCLIP
MN1707EU10MN_0002
19
© 2003 Siemens AG
1.2 Quality of service for ps service

In BR6.0 there was no support of Quality of Service attributes.
In the BR7.0 the Quality of Service attributes "Service Precedence" and "Radio
Priority" are realised. This is according to the capabilities of the GSM Release 97/98.
In the BR8.0 the system is working based on Release 99 capabilities. The operator
has now the opportunity to support Real Time (RT) Packet Flow Control. The Packet
Flow Management (PFM) procedures are prerequisite to be supported by SBS to
realise the Rel.99 QoS.
The Admission control was in the BR7.0 implemented and based on the peak
throughput and MS multislot class.
The Admission control is modified in BR8.0 and taking into consideration the Gb
interface bandwidth.
20 MN1707EU10MN_0002
© 2003 Siemens AG
BR6.0: • Gb flow control based on BVC

• Scheduler predefined
• no support of
Quality of service
BR7.0: • Gb flow control based on BVC and MS

• Scheduler takes SBS weights into calculation
• support of QoS
according to Rel. 97/98
BR8.0: • Gb flow control based on BVC and MS and PFC

• Scheduler takes SBS weights into calculation
• support of QoS • Streaming supported >> Real time services
according to Rel. 99 • Admission control with resource reservation
Fig. 15 History on QoS in SBS
MN1707EU10MN_0002
21
© 2003 Siemens AG
1.2.1 General
The different applications that will make use of packet-oriented data transmission via
GPRS require different qualities of transmission. GPRS can meet these different
requirements because it can vary the quality of service (QoS) over a wide range of
attributes. The quality of service classes (TS 23.107) are:
• Conversational class
• Streaming class
• Interactive class
• background class
• Mean throughput class.
The main distinguishing factor between these QoS classes is how delay sensitive the
traffic is: Conversational class is meant for traffic which is very delay sensitive while
Background class is the most delay insensitive traffic class.
Conversational and Streaming classes are mainly intended to be used to carry real-
time traffic flows. The main divider between them is how delay sensitive the traffic is.
Conversational real-time services, like video telephony, are the most delay sensitive
applications and those data streams should be carried in Conversational class.
Interactive class and Background are mainly meant to be used by traditional Internet
applications like WWW, Email, Telnet, FTP and News. Due to looser delay
requirements, compare to conversational and streaming classes, both provide better
error rate by means of channel coding and retransmission.
22 MN1707EU10MN_0002
© 2003 Siemens AG
Quality of Service QoS - Classes

Different requirements for different applications ⇒
multiple GPRS QoS profiles
streaming
class
conversational class
interactive class
background
class
PLMN must support only
limited QoS service profile
Fig. 16 Quality of service classes
MN1707EU10MN_0002
23
© 2003 Siemens AG
Qos Attributes
For the QoS classes there are several QoS attributes defined. Which attributes are
used depends from the Service and the QoS class. The most interesting attributes
are:
• Maximum bitrate
• Delivery order
• Residual bit error ratio
• Transfer delay
• Guaranteed bit rate
• Allocation/Retention priority
• …
Interworking
GPRS Release 99 QoS attributes shall be equivalent to UMTS QoS Attributes. For
interworking purposes between different releases, mapping rules between GPRS
Release 97/98 and GPRS Release 99 as well as UMTS are defined.
Mapping shall occur whenever the UE, the SGSN, the GGSN and the HLR nodes are
of different releases R97/98 or R99. The mapping is required in PDP context
activation and modification procedures and when a R99 HLR Insert Subscriber Data
towards a R97/98 SGSN.
24 MN1707EU10MN_0002
© 2003 Siemens AG
Maximum Bitrate
Delivery order
Delivery of erroneus SDU
Guaranteed bit rate
Traffic handling Priority
Maximum SDU size
Fig. 17 QoS attributes
Traffic class Example Requirements Supported

by BR 8.0
Conversational - telephony speech, VoIP - very sensitive to delay No
- guaranteed bitrate
- delay:100, 200, 400 ms
- BER: 10-3 – 10-5
- RLC mode: not acknowledged
Streaming -Real Time video/audio - less delay sensitive than Yes

(one way transport) conversational class
- guaranteed bitrate, delay: <1 s
- BER: 10-5 – 10-8
- RLC mode: ack./not ack.
Interactive - web browsing, data base - best effort Yes

retrieval, server access - delay: < 2s, BER<10-9
- RLC mode: acknowledged
Background - e-mail, SMS, FTP - best effort Yes

- the least delay sensitive, BER<10-9
- RLC mode: acknowledged
Fig. 18 Requirements supported by BR8.0
MN1707EU10MN_0002
25
© 2003 Siemens AG
1.2.2 Database parameters

To enable the OoS support the STREAMSUP and the PFCSUP have to be set to
enabled.
With the Weight the relation between the supported traffic classes is set. The range
of the weight is between 1 and 32. 32 is the best value.
26 MN1707EU10MN_0002
© 2003 Siemens AG
STREAMSUP PTPPKF Enable/disable This parameter enables or disables the real time
streaming support.
PFCSUP PTPPKF Enable/disable This parameter enables or disables the Packet flow
context procedure support.
BEPFIDLWEI PTPPKF (1),..., 32 This attribute defines the weight for the predefined
PFIbest effort in DL.
INTRTRFH1WEI PTPPKF 1,..., (8),..., 32 This attribute defines the weight for the Interactive Class
traffic handling priority 1.
STREAMWEI PTPPKF 1,..., (32) This attribute defines the weight for the Streaming class.
BCGRWEI PTPPKF (1),..., 32 This attribute defines the weight for the Background class.
SMSINFO PTPPKF Pfiweight: 1...32 This attribute defines the weight for the predefined
smsSDUsize: 160 ...1560 Signaling PFI
bytes
SPFIWEI PTPPKF (1),..., 32 This attribute defines the weight for the predefined SMS
PFI
Fig. 19 Quality of service support
MN1707EU10MN_0002
27
© 2003 Siemens AG
1.3 Scheduler Enhancements

The scheduler distributes the permission to access the physical resources after the
Resource Manager has allocated them for the respective air interface The scheduler
decides on delayed or preferred transmission, according to the weighting parameters
assigned to the service classes. The operator can adjust the parameters, in the same
manner as in the previous release (BR7.0).
EGPRS/GPRS Scheduler Enhancements feature intends to provide a scheduler
enhancement to BR 7.0 GPRS/EGPRS scheduler by introducing new features like:
• Packet Flow Context Procedure
• Streaming Traffic Class (in addition to Interactive and Background ones)
• support of some Rel 5 QoS Attributes
• Improvement of overall performance with Rel 97/98 mobiles.
Enhancement of Uplink Scheduling:

The TBF weight is updated when in the Packet Resource Request Messages a Radio
Priority different to the first one is requested.
The enhanced BSS scheduler distributes the transfer permission for the respective
radio link control blocks in accordance with the QoS attributes (3GPP R5).
28 MN1707EU10MN_0002
© 2003 Siemens AG
Fig. 20 Scheduler with several PCU buffers
MN1707EU10MN_0002
29
© 2003 Siemens AG
1.3.1 SBS Realization

The scheduler is made up by two entities:
• TBF scheduler
• PFC scheduler
There are two cases that can occur in the network:
A) Network and MS can support PFC management
• DL: TBF and PFC scheduler
• UL: TBF scheduler
B) Network or MS can not support PFC management
• DL: TBF scheduler
• UL: TBF scheduler
In case of PFC scheduling there can be streaming PFC. In case of streaming PFC
TBF multiplexing is not allowed, that means all resources are given to the streaming
PFC.
30 MN1707EU10MN_0002
© 2003 Siemens AG
PFC2
PFC1
RLC Block
TBF_MS1
TBF Manager MS1
TBF_MS2
TBF Manager MS2
TBF_MSn
TBF Manager MSn
W PFC1_MS1
TBF PFC W PFC2_MS1
Scheduler Scheduler
RADIO
W TBF_MS1
RESOURCE
MANAGER
Fig. 21 Scheduling
MN1707EU10MN_0002
31
© 2003 Siemens AG

The parameters that are used to define the weights are already explained in the
Quality of service feature
32 MN1707EU10MN_0002
© 2003 Siemens AG

It is defined for each allocated PFC_buffer, started
when PFC_buffer gets empty, stopped and
TPFCBUFF PCU/CPCU 5..30 (20) cancelled if new LLC frames are coming for that
buffer. When it expires DL TBF Scheduling Weight
Updating Algorithm is started
Fig. 22 Scheduler enhancements
MN1707EU10MN_0002
33
© 2003 Siemens AG
1.3.3 Example
A TBF is in this example carrying four PFCs including streaming traffic. There are
following PFCs defined:
• PFC 0: streaming
• PFC 1: Interactive, Traffic Handling Priority=1
• PFC 2: Interactive, Traffic Handling Priority=2
• PFC 3: Background
PFC 0 is carrying Packet Flow Data related to a streaming session. For instance, the
application is playing a news session. The short movie is coded by MPEG-4 with
average bit rate equal to 43 kbps. The PFC 0 has no weight assigned since the
streaming traffic has the highest priority.
PFC1 and PFC2 are both of Interactive Class. However, the former one has higher
priority so the weight of PFC1 is 8. PFC 2 has its weight of 4.
The last packet flow context carrying background traffic shall have the smallest
weight as it is of least priority.
The following plot presents an average mean throughput [kb/s]. Two cases are here
considered: one with streaming traffic active and the one with streaming traffic
switched off.
34 MN1707EU10MN_0002
© 2003 Siemens AG
50
40
30
Kbit/s
20
10
0
0
C
1
2
C
B PF
3
Actived Streaming PFC

No Streaming PFC
Fig. 23 Simulation result
MN1707EU10MN_0002
35
© 2003 Siemens AG
1.4 Dual transfer mode

Up to the BR7.0 simultaneous operation on CS and PS domain is not possible. It can
be supported separate voice connection OR separate PS transmission/reception
The recently introduced simplifications for DTM and the subsequent announcement
by different vendors to provide DTM capable mobiles brought strong momentum to
this feature.
Using DTM, a simple class A mobile is able to operate in parallel CS and PS
connections. This enables the operator to offer additional use case scenarios,
resulting in higher consumer satisfaction of mobile subscribers and increased
revenues.
For BR8.0 the Dual Transfer Mode (DTM) for simple class A mobile includes:
• MS can transmit/receive CS and PS data in parallel – supported by the network
• Class A MS able to switch to DTM mode making use of DTM signaling procedures
• Class B MSs profits from DTM introduction in case of lack of Gs interface (MS can
receive an incoming CS call during a packet transfer)
36 MN1707EU10MN_0002
© 2003 Siemens AG
Class B mobile
DTM Class A
mobile Voice call
Video streaming
Fig. 24 Dual transfer mode
MN1707EU10MN_0002
37
© 2003 Siemens AG
DTM establishment
A direct transition from Idle to DTM Mode is not possible. The DTM is triggered either
by MS (dedicated/packet transfer) or BSS
a) CS connection is already established
MS initiated
• a DTM request message (via main-DCCH) to BTS request contains description of
PS resources
SGSN initiated
• receipt of DL data from SGSN
b) TBF is already running
Legacy DTM Establishment (Release 99 MS)
• TBF abandoned Æ CS establishment (normal access procedure via CCCH) Æ
TBF resumed Æ DTM mode
DTM release
a) TBF release
MS automatically leaves the DTM mode and stays in cs dedicated mode no service
interruptions in CS domain
b) CS connection release
38 MN1707EU10MN_0002
© 2003 Siemens AG
Establishment of Dual Transfer Mode
TBF running Dedicated mode
MO trigger CS paging request MS initiated SGSN initiated
Release of Dual Transfer Mode
Dual Transfer Mode
TBF release CS connection release
Fig. 25 DTM establishment and release
MN1707EU10MN_0002
39
© 2003 Siemens AG
1.4.1 Operation mode
Paging Co-ordination
PACKET TRANSFER MODE – CS Paging
• CS Paging request may be received via A interface (if no Gs exists) – NOM II/III
• BSC recognizes PTM: CS paging to PCU Æ via PACCH to MS
• Note: functionality can be used not only for DTM but also for normal class B
mobiles (PAGCOORCLB)
• functionality mandatory for DTM MS in case of NOM II/III
DEDICATED MODE – PS Paging
• PS Paging sent by SGSN
• BSC knows that MS is in DM: BSC sends Packet Notification Æ via the main-
DCCH to MS
RRM (Radio Resource Manager)

RRM procedures as same as for non-DTM MSs (dedicated/packet transfer mode –
idle/packet idle mode)
• DTM resources always on TSs/TRXs where both CS&PS supported
• PDCH multiplexing still allowed
• CS services – priority over PS services
• Reconfiguration procedures like: Overheating, Quality Control Function foreseen
also for DTM
Location Management
DTM MS performs Routing Area/Location Area Update – MS state dependent
• idle mode – Class A behavior = Class B behavior (but “simple class A MS – RA
update in a DCCH”
• RA update/LA update – shall be supported in the main DCCH (reduction of GPRS
signaling)
40 MN1707EU10MN_0002
© 2003 Siemens AG
Multi Slot Operation Multislot TS Rx TS Tx Sum

class
- 1 TS for both CS services (TCH/F, TCH/H)
- 1 or several TSs for PS (depending on MS and 5 2 2 4
network capability
9 3 2 5
- support for Multi Slot Classes: 5 (mandatory for DTM
MSs), 9, 11 11 4 3 7
Dedicated PDCH Shared PDCH
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
PS PS CS CS PS PS PS CS PS PS CS
MS 1 MS 1
MS 2 MS 2
MS 3 MS 3
MS 4 MS 4
MS 5
MS 5
Fig. 26 Operation mode
MN1707EU10MN_0002
41
© 2003 Siemens AG
1.4.2 Parameters

Enabled/ Enable Dual transfer mode Flag; sent in each cell to the
PTPPK,
EDTMSUP mobile, e.g. via SI or PSI messages.
TGTPTPPKF (disabled)
Flag to enable/disable the ‘Enhanced DTM Establish’
Enabled/
EENHDTMSUP BSC mode, as defined in 3GPP Release 6
(disabled)
Flag to enable/disable Paging coordination for Class B
Enabled/ mobiles
PAGCOORCLB BSC
(disabled)
Controls the maximum number of LAPDm frames on
MAXLAPDMN which a layer 3 (GTTP message) can be segmented
BSC (5)..12
into and be sent on the main DCCH.
Timer value to be included in DTM Reject msg.; indicates
TDTMWIND BSC 0..,(5),…255 sec waiting time, before MS may again send DTM-
Request
Timer: maximum duration by which the BSC will delay the
1.5, ... ,2.5 release of the RR connection;
T3197 BSC
(4)
Fig. 27 Parameter for DTM mode
42 MN1707EU10MN_0002
© 2003 Siemens AG
1.4.3 Compatibility
Measurement reporting is only sent for cs service
Handover is based on cs service only, no cell reselection
NACC is not applied, DMA not allowed, extended cells in far area not supported, FH
with same hopping for all channels reqired.
MN1707EU10MN_0002
43
© 2003 Siemens AG
1.5 Network assisted cell change NACC

1.5.1 Basics
During the usual Cell Reselection operation (without NACC), a considerable service
interruption time arises because, as first activity in the target cell, the MS has to
collect system information by listening to BCCH/PBCCH before it can start with any
data transfer.
The idea of the NACC feature is to reduce the service interruption time during cell re-
selection of an MS providing the system information of the target cell before
performing cell change as long as the MS is still in the old serving-cell.
Main steps of the NACC procedure:

Before the cell change
• When cell reselection criteria are fulfilled, MS notifies BSC asking for NACC
support, at the same time MS proposes a target cell for cell reselection
• BSC sends to MS SI/PSI of the target cell (proposed by MS or selected by the
network)
• MS performs cell reselection
After the cell change
• MS informs BSC about already received SI/PSI
• BSC sends missing SI/PSI (if any)
44 MN1707EU10MN_0002
© 2003 Siemens AG
BSS Cell A Cell B
MS Packet transfer Gathering SI/PSI Cell reselect. Packet transfer
Packet transfer interruption
BSS Cell A Cell B

NACC
MS Packet transfer NACC1 NACC2 Packet transfer
Packet transfer
interruption
time
Cell reselect.
decision
Fig. 28 Comparison for CR with and without NACC
MN1707EU10MN_0002
45
© 2003 Siemens AG
Cell Change Notification mode

With NACC the mobile station notifies the BSC when cell reselection conditions are
met and delays cell reselection to let the network answer with neighbor cell system
information. This is done when the MS is in Cell Change Notification (CCN) mode.
In the cells where NACC feature is implemented and activated a new parameter
called CCN_ACTIVE is broadcasted and indicates whether CCN is enabled in the cell
or not.
If an MS is camping on a cell where CCN is implemented (CCN_ACTIVE=1) it may
access NACC support. In order to do this it has to be also aware of neighbor cells
where CCN is supported.
CCN_SUPPORTED is always present in the system information messages and for
the internal cells (belonging to the same BSC) has the same value as CCN_ACTIVE.
46 MN1707EU10MN_0002
© 2003 Siemens AG
cell2 cell5
cell1
CCN_SUPPORTED
cell3 cell4
CCN_ACTIVE
Fig. 29 CNN mode
MN1707EU10MN_0002
47
© 2003 Siemens AG
New Messages
The NACC feature makes use of three new different messages:

• Packet Cell Change Notification (MS->BSC)
sent to inform the network that cell-reselection criteria are now fulfilled and that the
MS has entered Cell Change Notification mode. The PACKET CELL CHANGE
NOTIFICATION message contains the ARFCN for the BCCH and the BSIC as
identity of the proposed cell. The message may also contain measurement reports for
the proposed cell and for other neighbor cells. The NACC algorithm starts when the
Packet Cell Change Notification message arrives to the PPXU.
• Packet Cell Change Continue (BSC->MS)
sent to force the MS to continue the Cell Reselection procedure to the target cell
proposed by the MS
• Packet Neighbor Cell Data (BSC->MS)
sent to provide system information required for initial access to a neighbor cell
48 MN1707EU10MN_0002
© 2003 Siemens AG
MS BSC
Packet Cell Change Notification
C
C
N DATA Transfer
Packet Neighbour Cell Data
M
o Packet Cell Change Continue or
d
Packet Cell Change Order
e
PCK Control ACK (Cell Change)
MS NEW
NewCell
Cell
Packet PSI/SI STATUS
Packet Serving Cell Data
Fig. 30 Example of messages for NACC
MN1707EU10MN_0002
49
© 2003 Siemens AG
NCCR and NACC

In BR 7.0 when NCCR (Network Controlled Cell Reselection) is enabled all the MSs
in packet transfer mode are ordered to use NC2. Moreover in BR 8.0 feature
“Network Controlled Cell Reselection from GSM/GPRS to UMTS due to sufficient
UMTS coverage” will be available. In this case MS/UEs which are in packet transfer
mode are ordered also to NC2.
Therefore coordination between above mentioned features is needed. Coexistence is
based on managing the MSs according to the Release of the MS and according to
other special cases as described in figure.
50 MN1707EU10MN_0002
© 2003 Siemens AG
PMO with NC2 PMO with NC2
or NC0
(NACCNTWCOR)
Fig. 31 NACC and NCCR
MN1707EU10MN_0002
51
© 2003 Siemens AG

The NACC feature is enabled by setting the CCHANTFACT to true.
The attribute NACCNTWCOR of the PTPPKF object has been introduced to describe
the operator-defined mode, the actual mode (NC0/NC1) to be used together with the
NACC feature.
Its default value 0 is used to accommodate mobiles in the packet idle mode that are
allowed to make cell reselection decisions without CCN support. As soon as they
start a packet transfer, the BSC modifies the "Network Control Mode" according to
the operator configuration and the mobile's capability.
52 MN1707EU10MN_0002
© 2003 Siemens AG
Parameter Range Object Description
(0) = FALSE CellChangeNotificationActive: The attribute

CCHANTFACT BSC indicates whether NACC is enabled in the
1 = TRUE BSC or not.
This attribute defines the usage of Network

Control Order during NACC when MS is in
(0) = NC0 Packet transfer Mode. When NACC is
NACCNTWCOR BSC enable, the value of this attribute is put in the
1 = NC1 parameter Network Control
Order inside Packet Measurement Order
message.
The value of this parameter indicates if the

(0) = FALSE PACKET PSI STATUS and PACKET SI
SYSPACKSYSSUP BSC
1 = TRUE STATUS messages are supported or not in
the BSC.
Fig. 32 Parameters for NACC
MN1707EU10MN_0002
53
© 2003 Siemens AG
1.6 NCCR from GPRS to UMTS

1.6.1 Basics
Up to BR6.0 the Cell Reselection for packet switched connected MS is handled
autonomous by the MS. BR7.0 is introducing the Cell Reselection controlled by BSS.
For this NCCR from GSM to GSM there are two types:
• EGPRS NCCR: for moving a MS in packet transfer mode that are moving from one
cell to another one under the BSS control, in order to maintain a good quality of
the transmission.
• The traffic control cell reselection NCCR: this procedure started because of traffic
reasons in order to have a better distribution of traffic load and to avoid waste of
resources when a cell is in overload conditions.
In BR7.0 the network did not trigger a Cell Reselection towards UMTS in this mode. If
the operator wanted to have cell reselection towards UMTS during packet transfer
Mobile Controlled Cell Reselection had to be enabled instead of NCCR.
In BR8.0 with this feature, the network initiates intersystem cell reselection when a
UMTS cell adjacent to the GSM cell can provide sufficient coverage. This is done by
changing the GSM serving cell to the UMTS target cell.
The NCCR from GSM toward UMTS in packet switched connected mode is called in
short form: NCCR G>U.
To distinguish between the MS controlled and BSS controlled cell reselection the
Network Control Mode is used.
54 MN1707EU10MN_0002
© 2003 Siemens AG
UMTS
NCCR G->U
GSM/GPRS
NCCR G->G
Realised since BR7.0 NCCR for GERAN

coverage reason Packet switched
GERAN
Packet switched
NCCR for GERAN

Traffic control reason Packet switched
New in BR8.0
GERAN NCCR G>U for UMTS

Packet switched coverage reason Packet switched
Fig. 33 NCCR scenarios
MN1707EU10MN_0002
55
© 2003 Siemens AG

The MS/UE is connected in packet switched mode (GPRS/EGPRS) in a GSM serving
cell. An adjacent UMTS cell offers sufficient UMTS coverage.
The UE/MS performs the measurements of the adjacent UMTS cells and reports
them to the GSM network by periodically sending PACKET MEASUREMENT
REPORT messages to the BSS.
Mobiles in packet idle mode operate in NC0 mode. In this mode the mobile does not
send NC measurement reports.
When a mobile is involved into a packet data flow (uplink or downlink), the BSC is
sending the "Packet Measurement Order" message. With this message the Network
Control mode is changed from NC0 to NC2.
The Network Controlled Cell Reselection (NCCR) algorithm is initiated in the BSC for
UE/MSs that are in the packet transfer mode and have NC2. The BSC evaluates the
periodically incoming PACKET MEASUREMENT REPORT messages from the
UE/MS.
56 MN1707EU10MN_0002
© 2003 Siemens AG
Fig. 34 NCCR to UMTS
MN1707EU10MN_0002
57
© 2003 Siemens AG
Target Cell List

FDD cells in the FDD sub list are ranked according to the level of the RSCP or
according to the received Ec/No quality.
• If RSCP reporting is used, the FDD cell with the largest RSCP is placed at the top
of the FDD sub list.
• If Ec/No-reporting is used, the FDD cell with the largest Ec/No is placed at the top
of the FDD sub list.
To form the complete UMTS TCL, the FDD sub list is sorted before the TDD sub list.
Mobile Speed Sensitive (MSS) NCCR G->U

It is possible to enable the “Mobile Speed Sensitivity” of the NCCR G->U algorithm.
When enabled, the NCCR G->U is performed for a “fast moving” UE/MS only under
certain conditions:
1. Reselection to UMTS micro cell forbidden
• GMICROCU set to TRUE, (UMTS cell defined as a micro cell)
• The parameter set independently than MICROCELL (UMTS cell defined as a
micro cell for GÎU handover purposes)
• EUMSSNCRESEL = disable, (Cell reselection to UMTS micro cell enable/disable)
2. Reselection to UMTS micro cell delayed
• GMICROCU set to TRUE
• EUMSSNCRESEL = enable
• TUESP => until expiry of this timer, UMTS micro cell is not included in the UMTS
TCL, however the RSCP or ECN0 conditions are met for this cell
58 MN1707EU10MN_0002
© 2003 Siemens AG
Target Cell list

UMTS TCL => Cells fulfilling
NCCR GÎU conditions
Cell .. FDD cell
UMTS TCL Cell .. TDD cell
Cell A
UMTS Cell B
TCL
Cell C
Reported
Cell .. UMTS
cells
Cell ..
Cell X Microcells
too fast MS/UE
UMTS
GERAN
UMTS microcell
Fig. 35 Target Cell list and microcells
MN1707EU10MN_0002
59
© 2003 Siemens AG
Enable, Enable UMTS sufficient coverage NCCR is used to

EUSCNCRESEL BSC
(Disable) enable or disable the cell reselection
UMTS_SUFF_RSCP_NC_Resel parameter defines the

USRSCPNCRESEL 0, ... , 63 ADJC3G
sufficient RSCP value used to initiate the NCCR G>U
UMTS_SUFF_EcN0_NC_Resel parameter defines the

USSECNONCRESEL 0, ... , 49 ADJC3G sufficient Ec/N0 value used to initiate the NCCR G>U
Fig. 36 Parameters for NCCR G>U enabling
60 MN1707EU10MN_0002
© 2003 Siemens AG
GPRS_FDD_REP_QUANT parameter controls the reporting

GFDDREPQTY (RSCP), Ec/N0 PTPPKF quantity. It decides in case of FDD cells if the RSCP or the
EC/N0 values are used for reporting and thresholds.
Indicates the number of FDD UTRAN cells that shall be

GFDDMURREP 0, 1, (2), 3 PTPPKF included in the MEASUREMENT REPORTs sent by ‘GPRS
attached’ mobiles.
Indicates the number of TDD UTRAN cells that shall be

GTDDMURREP 0, 1, (2), 3 PTPPKF included in the MEASUREMENT REPORTs sent by ‘GPRS
attached’ mobiles.
0 … 6 = UMDB98 (below -
98)… UMDB74 (below -74)
Defines a threshold and also indicates whether MS/UE is
7 = always
QSRHP PTPPKF allowed to search UMTS cells when RLA_C of the serving
8 … 14 = OMDB78 (above -78)
cell is below or above the threshold. Broadcast on PBCCH.
… OMDB54 (above -54)
Indicates if mobile can search 3G cells when BSIC decoding

QUMTSSRHPRI (0 = TRUE), 1=FALSE PTPPKF is required, i.e. if the searching time can be longer than
normal value (13 sec instead of 10 sec)
Fig. 37 Reporting Conditons

TFAILNCU 0, 1, 2, …, 99, PTPPKF Until expiry of this timer, this UMTS neighbour cell is excluded from
100, (5) the UMTS Target Cell List
MAFAILNCU 0, 1, 2, …, 99, PTPPKF The aim of this parameter is to avoid that the BSC sends an infinite
100, (4) number of PACKET CELL CHANGE ORDER messages for the
same UMTS neighbour cell to an MS/UE, in case the ordered cell
change to this UMTS cell fails. This number of messages is limited
to Max_Fail_NC_Umts
TBNCU 0, 1, 2, …, 99, PTPPKF This timer avoids fast "ping pong" back cell reselection to UMTS, i.e.
100, (5) this timer avoids that a MS/UE, which has just arrived in a
GSM/GPRS cell, is immediately NC cell reselected to UMTS
MSTXPMAXUMT 0 = (43 dBm) TGTFDD/TGTTD This parameter indicates the maximum level of transmission power
S ...(9) D an MSis allowed to use in the serving cell for UMTS
19 = (5 dBm)
T5 2 ...(10)… 29 BSC This timer is started from the BSC when the RA-Capability-Update is
transmitted to the SGSN and is stopped when the RA-Capability-
Update-Ack is recieved
NRACPBLUPDR 1 … (3) ... 30 BSC This attribute describes the maximum number of retransmissions of
ET the Ra-Capability-Update to the SGSN when the BSC does not
accept the corresponding answer in the RA-Capability-Update-Ack
from the SGSN
Fig. 38 Additional Conditions
MN1707EU10MN_0002
61
© 2003 Siemens AG

GMICROCU 0 = TRUE, ADJC3G This parameter specifies whether an UMTS neighbour cell
is an UMTS microcell for which the additional MSS
1 = FALSE
condition of the Mobile Speed Sensitive (MSS) NC
(1) GSM/GPRS to UMTS cell reselection algorithm shall be
applied.
TUESP 0, 1, 2, …, 99, 100, ADJC3G This timer is used for Mobile Speed Sensitive (MSS) NC
GSM/GPRS to UMTS cell reselection. The timer is started
(5)
for an MS/UE when the threshold condition for "sufficient
UMTS coverage" is met
EUMSSNCRESEL 0 =TRUE PTPPKF This parameter is used to enable the "mobile speed
sensitivity" of the NC GSM/GPRS to UMTS cell reselection
1 = FALSE
algorithm (Mobile Speed Sensitive (MSS) NC GSM/GPRS
(1) to UMTS cell reselection
Fig. 39 Micro cell settings
1.6.4 Compatibility
The feature NCCR from GPRS to GPRS has to be enabled (NCRESELFLAG =
enabled).
62 MN1707EU10MN_0002
© 2003 Siemens AG
MN1707EU10MN_0002
63
© 2003 Siemens AG
1.6.5 Example
The EUSCNCRESEL=0 enables the NCCR G > U.
The following Reselection conditions are set:
• QSHRP = 7 (always) – MS always looks for UTRAN cells, independently on RxLev
of the serving cell
• GFDDREPQTY = 0 (RSCP) – RSCP of UTRAN cells is a criterion for cell
reselection
• USRSCPNCRESEL = 8 (-108dBm) – sufficient signal level guaranteeing UMTS
coverage
64 MN1707EU10MN_0002
© 2003 Siemens AG
RxLev
RSCP
GERAN cell UTRAN cell
USRSCPNCRESEL = -108 dBm
Reselection to UTRAN Time
Fig. 40 Example NCCR G>U
MN1707EU10MN_0002
65
© 2003 Siemens AG
1.7 Enhanced Flow Control

1.7.1 Basics
This feature controls the GPRS/EGPRS data traffic from SGSN to the BSC via the
Gb interface and the flow from the BSC over the air interface to the mobile station
(MS). The data traffic from SGSN to the BSC may depend on the load of the internet
traffic, while the flow on the air interface is determined by the selected coding
scheme.
The packet control unit (PCU) of the base station controller (BSC) is the module that
is creating the PCU frames transmitted in MS direction.
The SGSN receives continuous information from the PCU and transfers data with a
rate that is assumed to be properly received by the PCU. The calculations of the PCU
are refined in a way that the data flow is observed both per cell and per mobile
station. Each mobile station is assigned to its own transfer bucket.
Consequently the flow control takes care for steady GPRS/EGPRS data traffic and it
reduces transmission delays for the user.
Up to BR 6.0 the flow control is cell specific only and it does not take into account low
individual flow rates of specific mobiles.
In the BR7.0 MS/Gb flow control is based on a cascaded mobile and cell oriented
flow control scheme. The mechanism first operates on MS level to calculate the flow
rate for each mobile within the same cell. The second level controls the cell specific
Gb data flow.
In BR8.0 the flow control is enhanced by another level, the Packet Flow Context flow
control.
66 MN1707EU10MN_0002
© 2003 Siemens AG
New in BR8.0 Packet Flow Context flow control
Since BR7.0
MS flow control MS flow control MS flow control
Cell specific flow

control
Calculation of needed data PCU

per MS and Cell
Request of needed SGSN
data amount
Fig. Enhanced flow control
MN1707EU10MN_0002
67
© 2003 Siemens AG
Algorithm for PFC

BSS side
Per each BVC, MS and PFC there is a BucketLevelPCU defined. This value equals
to number of bytes stored in BSS for BVC, TLLI, PFC. It is incremented whenever
LLC PDU arrives (increment equals to LLC bytes length) and decremented when
proper RLC block are transmitted over the air interface (decrement equals to RLC
data part length).
PCU is responsible for calculating the control variables R and Bmax and sending
them with flow control commands to the SGSN. C timer gives the minimum interval
between sending of subsequent Flow Control PDUs (it means that at timer C
expiration a new Flow Control message can be sent by BSC to SGSN).
SGSN side
There is a buffer for each BVC, MS and PFC on the SGSN side. It is not up to BSS to
decide whether the LLC PDU shall be transmitted or it needs to be delayed. The
decision belongs to the SGSN.
In the PCU the real rate RPCU is typically different from the value R sent to SGSN.
The BSC has to inform the SGSN about rate R that can be used in the next C period.
RPCU is the real rate in BSC Bucket (it is impossible to know the exact RPCU for the
next C period).
The figure below describes how the flow of packets is oriented for the downlink
transmission of LLC frames from the SGSN to the PCU (3GPP Release 48.018).
68 MN1707EU10MN_0002
© 2003 Siemens AG
Flow Control Commands (Bmax, R)

every C seconds
BmaxPCU
PCU
Bhigh
SGSN
Bmax Blow
Bmax R
RPCU
permitted LLC frames
Fig. 41 Flow control on Gb interface
MN1707EU10MN_0002
69
© 2003 Siemens AG
Enabling the enhanced flow control is done by setting the PFCSUP to true.
A new parameter common to MS and PFC is f_PER; this parameter is the shrinking
value used in case of PDU life time expiration or in case of Bucket Ratio not
supported in order to reduce R value sent to SGSN.
70 MN1707EU10MN_0002
© 2003 Siemens AG

This parameter is used to indicate whether the Enhanced Flow
PFCFCSUP PCU TRUE/(FALSE) Control is enabled or not
When SGSN receives MS FLOW CONTROL parameters ,

SGSN Bmax and R generated and not more last Bmax
TH CPCU 6…5999 and R sent by BSC. TH is restarted each time a MS FLOW
CONTROL parameters are received.
This parameter is the Low Pass Filter Coefficient used to filter

Leak_Rate oscillation. The filtering applied is the following:
TF CPCU 6…5999
Rmax_eFC=alpha*Rmax(Tnow)+(1-alpha)*Rmax(Tnow-C).
This parameter is the Low Pass Filter Coefficient used to filter

FCRATE CPCU 0 … (100) % Leak_Rate oscillation. The filtering applied is the following:
Rmax_eFC=alpha*Rmax(Tnow)+(1-alpha)*Rmax(Tnow-C).
Fper is common to MS and PFC; this parameter is the shrinking

5% … 50% value used in case of PDU life time expiration or in case of
FPER PTPPKF
(15%) Bucket Ratio not supported in order to reduce R value sent
to SGSN.
If the value is TRUE, Rmax is used for Bmax and R

MSRMAXU PTPPKF TRUE, FALSE computation, otherwise RGUA is used.
Fig. 42 Enhanced flow control common settings
MN1707EU10MN_0002
71
© 2003 Siemens AG
Defining the thresholds for the PFC

New parameters PFC Flow Control (X = Interactive, Background, Streaming) are:
• BmaxPFC=PFCIBMAPER *Fn*(1sec+TF1)*Rgua
• BmaxPCUPFC = BmaxPFC * PFC_x_MAPER
• BhighPFC = BmaxPCUPFC * PFC_x_HIPER
• BlowPFC = BmaxPCUPFC * PFC_X_LPER
The states “congested” and “non-congested” are determined using the two thresholds
Bhigh and Blow of the BmaxPCU.
If the state is “non-congested”, and BucketLevelPCU crosses Bhigh from below, the
state is set to “congested”.
If the state is “congested”, and BucketLevelPCU crosses Blow from above, the state
is set to “non-congested”.
The parameters given in the table are valid for QoS classes Interactive, Background
and Streaming, here represented with X = I, S, B.
72 MN1707EU10MN_0002
© 2003 Siemens AG
PFCxBMAPER PTPPKF 10% ... (100%) ... 200% This parameter reduces the value of Bmax
automatically computed by BSC. BSC criteria is
BmaxPFC=PFCIBMAPER *Fn*(1sec+TF1)*Rgua, pfc
and Rgua,pfc guaranteed flow rate out of the buffer in
the PCU.
PFCxBMAPPER PTPPKF 100% ... (200%) This parameter assignes the value of Interactive
Bucket Max PCU as percentage of Bmax.
PFCxBHIPER PTPPKF 50% ... (70%) ... 90% If PFC Bucket Level is greater than
PFCInteractiveBucketHighPercentage*
InteractiveBucketMaxPCU, the Bucket Congestion is
started.
PFCxLPER PTPPKF 10% ... (60%) ... 80% If PFC Bucket Level is lower than
PFCInteractiveBucketHighPercentage*
InteractiveBucketMaxPCU, the Bucket Congestion is
finished.
PFCxMAXU PTPPKF True, false If the value is TRUE, Rmax is used for Bmax and R
computation, otherwise RGUA is used.
PFCxPER PTPPKF 10% ... (100%) ... 200% This parameter can be utilised to scale the value of R
(PFC Leak Rate) for Streaming PFC. R is multiplied
by PFCIRPER during each pass of the PFC flow
control algorithm.
X = I (interactive), B (background), S (streaming)
Fig. 43 PFC flow control parameters for each traffic class
MN1707EU10MN_0002
73
© 2003 Siemens AG
1.7.3 Example
In this example the buffering for the streaming traffic class with the following settings
is described:
PFCSBMAPER 100%
PFCSBMAPPER 200%
PFCSBHIPER 70%
PFCSLPER 60%
PFCSMAXU True
PFCSPER 100%
74 MN1707EU10MN_0002
© 2003 Siemens AG
Flow Control Commands (Bmax, R)

every C seconds
BmaxPCU
PCU
Bhigh=
SGSN
Bmax Blow
Bmax R
RPCU
permitted LLC frames
Fig. 44 Flow control on Gb interface
MN1707EU10MN_0002
75
© 2003 Siemens AG
1.8 Multiple PCU Pooling

1.8.1 Basics
The multiple PCU pooling feature is changing the allocation of cells (PTPPKF) to the
Packet Control Units (PCU) in the BSC. The new allocation offers the operator the
possibility to control the responsibility areas of the PCUs.
This feature addresses network “overlay” scenarios with Radio Access Network
“split” between different BSS providers connected to one (or more) SGSN ports, each
one handling a routing area (set). The SGSN ports may belong to one or more
SGSNs as overlay scenario may be extended to the Core Network entities.
The number of PCU pools is limited by the supported number of PPXUs and the
requested redundancy scheme, according to BSC capabilities.
76 MN1707EU10MN_0002
© 2003 Siemens AG
PTPPKF
PCU PTPPKF PTPPKF

PTPPKF
PTPPKF
PCU 3 PCUs in Pool 1
PTPPKF
PCU
PCU
2 PCUs in Pool 2 PTPPKF
PTPPKF
PCU
PTPPKF
Fig. 45 Multiple PCU pools
BSC BR5.5: each PCU covers

defined set of PTPPKF
PCU:0 PCU:1
PPXX HW with BR6.0/7.0:

all PCU cover all PTPPKF
in one BSC
PCU:0
PCU:1
BSC
BTS/PTPPKF
Routing area
Fig. 46 History
MN1707EU10MN_0002
77
© 2003 Siemens AG
1.8.2 SBS realisation

The “Multiple PCU Pooling” feature allows more than one SGSN to be connected to
one BSC. A pooling concept has been introduced to support its resource
management: Each PCU is assigned to a pool that, in turn, can be connected to one
SGSN. Nevertheless, each PCU has its own NSEI.
For the new PCU Pooling the following rules apply:
• Each PPXU is assigned to one pool
• A maximum of 6/12 pools can be configured (BSC72/BSC120).
• The number of PPXUs per pool is 1 to 12.
• Each cell has to be assigned to one Pool of PPXUs
• The cells will be assigned dynamically by BSC to PPXU inside the Pool taking in
consideration load balancing concepts. Load balancing algorithm will be applied
separately for each configured pool.
78 MN1707EU10MN_0002
© 2003 Siemens AG
BSC SGSN:1
PTPPKF NSEI 1
Pool 1 PPXU:0
1,2,3,4 Board 0
NSEI 2
PPXU:1
PTPPKF NSEI 3
Pool 2 PPXU:2
5,6,7 Board 1
NSEI 4
PPXU:3
SGSN:2
PTPPKF NSEI 5
Pool 3 PPXU:2
8,9 Board 0
NSEI 6
PPXU:3
Fig. 47 Pool configuration
MN1707EU10MN_0002
79
© 2003 Siemens AG
1.8.3 Example
Overlay RAN scenario with Siemens and other vendor, named N.
Improvements in network performance are realized by:

• decrease in the number of Inter-SGSN Cell Reselections:
• Cell Reselection (CR) of cells connected to different SGSN boards is handled by
SGSN as INTER-SGSN CR with high delay
For the Cell Reselection (CR) of PO Calls there can be the following cases:
• Case a: Siemens BSC and Nokia BSC connected to same SGSN boards ->
INTRA SGSN CR, low delay < 10 sec.
• Case b: Siemens BSC (and PO traffic of controlled BTS) and Nokia BSC (and
traffic of controlled BTS) connected to different SGSN boards -> INTER SGSN
CR, high delay > 10 sec.
SUMMARY
With the pooling concept the operator can define the Siemens Cells in pools that
cover the same area as the other vendors cells, and connect both to the same N.-
SGSN port.
80 MN1707EU10MN_0002
© 2003 Siemens AG
N SGSN
Scenario A is handled
as Inter SGSN CR
N N
BSC BSC
A B Siemens
BSC
N BTS
Siemens BTS
Fig. 48 Reason for Multiple PCU pooling feature
MN1707EU10MN_0002
81
© 2003 Siemens AG

A new parameter is introduced: CPCU = Common PCU, in the object BSC and
PTPPKF. Range 0 … 11.
To this new object there are moved many of the already known parameters from the
former PCU area:
• T3, T4, T5, TF, TH
• NRACPBULRETR, TEXTULTBF, FCRATE, TPFCBUFF
• NBVCBR, NBVCUR, NBVCRR, T1, T2
• TF1, N3101, N3103, N3105
• NRLCMAX, T3141, T3169
• T3172, T3191, T3193
• T3195, TEMPCH, TIMEDTBFREL, TEMPPDT, THSULBAL, TSULBAL
The parameters for the new flow control are located in CPCU:
• DNLBSSPFCRET, DNLBSSPFCT, MODBSSPFCRET, MODBSSPFCT, PREAT
82 MN1707EU10MN_0002
© 2003 Siemens AG
MN1707EU10MN_0002
83
© 2003 Siemens AG
1.9 Extended Cells for CS and PS

1.9.1 Basics
This feature provides cell extensions exceeding cell sizes of 35 km for both circuit
switched and packet switched traffic. This is possible with the help of two consecutive
timeslots. Because two are reserved, uplink bursts are allowed to arrive in the second
timeslot when they exceed a distance of 35 km and when the maximum possible
timing advance has been set.
This feature also allows cell extensions that reach beyond 35 km for packet data
enabling GPRS and EGPRS services within areas with a radius of up to 100 km.
Packet data is supported without restrictions in extended cells on the BTSplus
platform family
The difference between MS in near and far area affects only UL direction. For CS
services on extended cells
• BSC responsible for single/double TS allocation
• BSC assigns double timeslot SDCCHs independent from the MS-BTS distance
• TA update procedure based on SACCH
• intracell HO from double to single TS allocation possible
• CS traffic – symmetric: double TS reservation is valid for both UL and DL (even if
DL not affected)
• reservation of two consecutive TSs applies to TCHs as well as to RACHs on
BCCH
84 MN1707EU10MN_0002
© 2003 Siemens AG
35 km 100 km
near area far area
CS (not new) PS new in BR8.0

- each MS in far area occupies two TSs - much more difficult
- lower number TS – assigned to MS; - the connection can be only in one direction
the following TS kept free - several MS share the one TS (multiplexing)
- the concept is valid for both UL and DL due to - multislot capability
bidirectional connection
Fig. 49 Extended cells for cs and ps
MN1707EU10MN_0002
85
© 2003 Siemens AG

There are two areas in extended cells:
• near area – radius of a cell ≤ 35 km (max TA = 63)
• far area – radius of a cell > 35 km (UL bursts allowed to arrive in the second TS –
propagation delay)
Resource assignment
In the access burst that is 2 TS always the initial TA is provided, then the network
knows in which area the mobile is.
In case the MS is in the near area no special care is required.
In case the MS is in the far area following has to be concerned:
• Uplink TBF: The TS for the service itself are allocated and one additional TS (the
next one). This secures that no other MS can use this TS for the UL transmission.
The USF and RRBP scheduling is assuring this.
• Downlink TBF: no special care is required
86 MN1707EU10MN_0002
© 2003 Siemens AG
k, …, k+n - (E)GPRS timeslots

k … … k+n- k+n Far area of
UL
1 Extended Cell
UL transmission
- k+n TS is kept free
DL UL
CS 0
far area
CS 1
CS 2
PDCH 3
PDCH 4
PDCH 5
PDCH 6
PDCH 7 keep dynamically free
Fig. 50 Resource assignment in extended cell for ps
MN1707EU10MN_0002
87
© 2003 Siemens AG
Timing advance
Continuous Timing Advance Procedure is not much affected:

• access bursts in PTCCH must be expected on BTS on 2 TSs
• PACKET UL/DL ASSIGNMENT - assignment of the PTCCH/U, TAI indication
• TA not enough in far area – timing offset introduces (TO_TA)
In Br7.0 the BTS is the master of TA values the PCU is not involved.
In BR8.0 the BSC PCU periodically informed about TO/TA; to arrange a proper
scheduling of resources (inner <-> far area change):
• UL – BTS periodically sends TO_TA list to PCU (every 416 TDMA frames)
• DL – USF flags included in DL blocks for multiplexing purpose
• TO included in DL blocks – the BTS get the information whether MS can be
expected in far or near area (where to expect the access burst)
88 MN1707EU10MN_0002
© 2003 Siemens AG
Timing Advance for ps
initial TA estimation continuous timing advance update
• based on the single access burst • MS in packet transfer mode

• carrying the PACKET CHANNEL REQUEST • CTAU procedure carried on PTCCH of MS
• MS provided with TA via PACKET UL/DL • PTCCH (and TAI) assigned to MS during
ASSIGNMENT • PACKET UPLINK/DOWNLINK ASSIGNMENT
access burst TAI

MS BTS MS BTS
PTCCH/U PTCCH/D
TA=0 Specific TA value
TAI 0 - 7 allocated to odd TSs

avoidance of collisions of radio access bursts
TAI 8 - 15 allocated to even TSs
Fig. 51 Timing advance
MN1707EU10MN_0002
89
© 2003 Siemens AG

The parameters are the same as for circuit switched traffic, but for ps they are in the
object PTPPKF.
Name Object Range Description

STDCELL,
CELLTYP
PTPPKF EXTCELL, Celltype, it specifies the type of the cell.
DBSTDCELL
TRUE,
EGPRS PTPPKF Enable/Disable GPRS on cell basis.
FALSE
Fig. 52 Parameters for Extended Cells
90 MN1707EU10MN_0002
© 2003 Siemens AG
MN1707EU10MN_0002
91
© 2003 Siemens AG
1.10 Enhanced Dynamic Allocation

In uplink the packet switched users are multiplexed in the same PDCH by the MAC
layer. In order to make the multiplexing of mobile stations on the same PDCH
possible, the uplink state flag (USF) is introduced. Different access modes can be
supported by the RLC/MAC protocol:
• Dynamic allocation – already supported in BR7.0 SW release
• Extended dynamic allocation – introduced in BR8.0 SW release
EDA
Extended Dynamic Allocation method eliminates the need of receiving USF on each
TSL. The mobile station monitors its assigned PDCHs starting with the lowest
numbered PDCH, then the next lowest numbered PDCH, etc.
Whenever the mobile station detects an assigned USF value on an assigned PDCH,
the mobile station transmits either a single RLC/MAC block or a sequence of four
RLC/MAC blocks on the same PDCH and all higher numbered assigned PDCHs.
92 MN1707EU10MN_0002
© 2003 Siemens AG
Dynamic Allocation Extended Dynamic

Allocation
TS5 0 T 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
S
TS3 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
Uplink
TS2 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
TS0 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
TS5 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
Downlink TS3 0 1 2 3 4 5 6 7 8
0 1 2 3 4 5 6 7 8
(USF
listening) TS2 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
TS0 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
52 Multiframe 52 Multiframe
Fig. 53 Allocation principles
MN1707EU10MN_0002
93
© 2003 Siemens AG
1.11 Overheating Management
A GPRS and/or EDGE mobile station (MS) has a maximum number of transmit
timeslots determined by its multi-slot class, and a maximum transmit power level
determined by its power class.
A mobile terminal implemented to the current specifications may not be able to
consistently operate at its maximum permissible power output while the maximum
number of timeslots have been assigned for uplink operation, due to possible
overheating of the transmitter circuitry. This factor may limit the ability for the mobile
terminal to take full advantage of its power class and/or multislot class, thereby
limiting maximum uplink data rates.
The Overheating approach described here combines the reduction of the MS

maximum output power and a signaling technique of informing the network of the
exact MS multislot output power capability.
A reduction in the MS maximum output power implies a reduction in the maximum
allowable distance between MS and base station within a cell. Thus, the feature
‘Overheating management for mobile stations’ has been conceived to prevent the
loss of the connection from a GPRS or EDGE mobile which is given multiple uplink
timeslots and has reduced its maximum output power. This is achieved through the
monitoring of the MS Timing Advance (TA).
94 MN1707EU10MN_0002
© 2003 Siemens AG
Max_N_UL_TS Maximum T.A.
1 TA_1
2 TA_2
3 TA_3
4 TA_4
CSCE BTS (urban), suburban, Cell Scenario defines the propagation scenario of a cell
ruralQuasiOpen, covered by a given BTS
ruralOpen
Fig. 54 Overheating management
MN1707EU10MN_0002
95
© 2003 Siemens AG
1.12 Extended Uplink TBF

At the moment, the BSC does not support Extended Uplink TBF mode. This means
that independently from MS mode the functionality is not supported in the network. In
such a case the uplink TBF is released as soon as MS signals the RLC buffer is
empty.
As mentioned above the Extended UL TBF is always used whenever both MS and
BSC support it. In such a case no further negotiation is required to use the
functionality for open-ended TBF.
Contrary to the Non-Extended UL TBF where CV=0 (RLC buffer empty) triggers the
TBF release, the release of an Extended UL TBF is caused by expiration of the timer
TIMEEXTUTBF.
The timer shall be set to the best possible level for each particular type of application.
96 MN1707EU10MN_0002
© 2003 Siemens AG
Non extended UL TBF mode Extended UL TBF mode
MS BSC MS
MS BSC
BSC
USF USF
USF
Data Block (CV=1) Data
DataBlock (CV=1)
Block (CV=1)
USF
USF USF
Data Block (CV=0)
Data Block (CV=0) Data Block (CV=0)
Packet UL Ack/Nack (FAI=1) RLC
Packet UL Ack/Nack (FAI=1) Packet UL Ack/Nack (FAI=0)
AM
Packet Control Ack only
Packet Control Ack
TBF Release TBF Release
TBF Release TBF Release
USF
Packet Uplink Dummy CB
New LLC
New LLC New LLC
PDU
PDU PDU
Data Block (with valid RRBP)
USF
Data Block (with valid RRBP) Data Block (CV=x)
Packet DL Ack/Nack including
Channel Request Description
Packet DL Ack/Nack including
TBF Estab.
Channel Request Description
TBF Estab. Packet Uplink Assignment
Packet Uplink Assignment TBF Estab.
USF
TBF Estab. Data Block (CV=x)
USF
Data Block (CV=x)
Fig. 55 Extended UL TBF
MN1707EU10MN_0002
97
© 2003 Siemens AG
98 MN1707EU10MN_0002
© 2003 Siemens AG
MN1707EU10MN_0002
99
© 2003 Siemens AG

03 Mn1707eu11mn 0001 Features Ps

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

03 Mn1707eu11mn 0001 Features Ps

Uploaded by

Copyright:

Available Formats

BR7.

Streaming >> RT services Multiple PCU pooling

Enhanced Flow control

Fig. 1 PS news in BR8.0

1.1 High speed Gb Interface

Fig. 2 BR7.0 solution: The different realization possibilities of the Gb interface

Fig. 3 BR8.0 new realization possibilities of the Gb interface

1.1.2 SBS Implementation

Fig. 4 BSC changes

Fig. 5 ESAM board

PCI Bus MAGNETICS

Fig. 6 PPXXV2 board

Configuration of connection BSC - SGSN

There are two possibilities of configuring the NS-VC:

PPXU ‘l’ NSE ‘l’

NSE Network Service Entity

Fig. 7 NS-VC configuration

The Gb data path is supervised on three levels:

1.1.3 Objects for IP SNS

Fig. 9 Hierarchy of the new objects

1.1.4 Database Parameters

The attribute NSconnection is used to specify the allowed (meshed) connections to

Parameter Object Range Description

ETHLINK 0,1 New object to represent the Ethernet link on the

ES 0,1 New object to represent the Ethernet Switch for

GBIPLNK 0,1 New object to represent the IP link on the GB

ROUIPADD0 BSC (NULL), Router IP address 1

Fig. 10 New parameters in BSC object

Parameter Object Range Description

MTU PCU 68,...,1500, NULL Maximum transmission lenght, size of the

Fig. 11 New parameters in PCU object

Parameter Object Range Description

Fig. 12 Parameters for Subnetwork Service

Parameter Object Range Description

RMTIPEP RNSVLIP aaa.aaa.aaa.aaa Remote IP endpoint IP address

RMTIPEP RNSVLIP 1024...65535 Remote IP endpoint UDP port

Fig. 13 Parameters for RNSVLIP

Parameter Object Range Description

Fig. 14 Parameters for NSVCLIP

1.2 Quality of service for ps service

BR6.0: • Gb flow control based on BVC

BR7.0: • Gb flow control based on BVC and MS

BR8.0: • Gb flow control based on BVC and MS and PFC

Fig. 15 History on QoS in SBS

Quality of Service QoS - Classes

Fig. 16 Quality of service classes

Delivery of erroneus SDU

Guaranteed bit rate

Traffic handling Priority

Maximum SDU size

Fig. 17 QoS attributes

Traffic class Example Requirements Supported

Streaming -Real Time video/audio - less delay sensitive than Yes

Interactive - web browsing, data base - best effort Yes

Background - e-mail, SMS, FTP - best effort Yes

Fig. 18 Requirements supported by BR8.0

1.2.2 Database parameters

Parameter Object Range Description

Fig. 19 Quality of service support

1.3 Scheduler Enhancements

Enhancement of Uplink Scheduling:

Fig. 20 Scheduler with several PCU buffers

1.3.1 SBS Realization