Professional Documents
Culture Documents
3G Parameter Initial Parameter Planning 06
3G Parameter Initial Parameter Planning 06
3G Parameter Initial Parameter Planning 06
3GRPESS Module 6
Customer confidential
1
NSN Siemens Networks
Customer confidential
2
NSN Siemens Networks
Module contents
Scrambling Code Planning
Neighbour List Planning
Location, Routing and Service Area Planning
UTRAN Registration Area Planning
Customer confidential
3
NSN Siemens Networks
Module contents
Scrambling Code Planning
Neighbour List Planning
Location, Routing and Service Area Planning
UTRAN Registration Area Planning
Customer confidential
4
NSN Siemens Networks
Introduction
512 Primary scrambling codes are organised into 64 groups of 8
Each Primary scrambling code has 15 Secondary scrambling codes
Each Primary & Secondary scrambling code has left and right Alternate scrambling codes
Customer confidential
5
NSN Siemens Networks
CP
CP
CP
P-SCH
Step 1 is the same for all scrambling code planning strategies
Customer confidential
6
NSN Siemens Networks
256 Chips
CP
Cs1
Cs2
Cs15
256 Chips
Cs1
Customer confidential
7
NSN Siemens Networks
CPICH
Customer confidential
8
NSN Siemens Networks
It is necessary that duplicate scrambling codes do not appear within those lists
Checks should be made to ensure that cells within potential active sets do not
have different neighbours with the same scrambling code
Example
scrambling
code clash
scenario 1
Neighbour to
active set cell
Neighbour to
active set cell
Active
Radiolink
Active
Radiolink
SC100
SC100
UE in soft
handover
Customer confidential
9
NSN Siemens Networks
SC100
Neighbour to
active set cell
Active
Radiolink
SC100
UE in soft
handover
Neighbour to
active set cell
Customer confidential
10
NSN Siemens Networks
Serving cell
UE
IntraFreqNcell
ScrCode
Customer confidential
11
NSN Siemens Networks
Cluster of cells
using 2 code
groups
Recommendations
Isolation between cells assigned the same scrambling code should be
maximised
isolation between cells assigned the same scrambling code sufficiently great to
ensure that a UE never simultaneously receives the same scrambling code from more
than 1 cell
isolation between cells assigned the same scrambling code sufficiently great to
ensure that a UE never receives a scrambling code from one cell while expecting to
receive the same scrambling code from second cell
Specific scrambling codes should be excluded from the plan to allow for future
network expansion.
The same scrambling code plan should be assigned to each RF carrier
Scrambling code planning should be completed in conjunction with neighbour list
planning
Scrambling code audits should be completed in combination with neighbour list
audits
Checks should be made to ensure that no cells are neighboured to two or more
cells which have neighbour lists including the same scrambling code for different
target cells
Customer confidential
12
NSN Siemens Networks
Module contents
Scrambling Code Planning
Neighbour List Planning
Location, Routing and Service Area Planning
UTRAN Registration Area Planning
Customer confidential
13
NSN Siemens Networks
Introduction
Neighbour lists:
3G intra-frequency
3G inter-frequency
3G inter-system
2G inter-system
High quality neighbour lists are critical to the performance of the network
Neighbour lists are usually refined during pre-launch or post-launch optimisation
Neighbour list planning should be as accurate as possible
Impact upon pre-launch optimisation has to be recognised
Pre-launch optimisation often limited to specific drive route which may not identify all
neighbours
Neighbour list tuning usually achieves the greatest gains during pre-launch
optimisation
SC100
Cell
Selection
SC200
Drop
Time
UE movement
Intra-Frequency Neighbours
When a UE is in soft handover then the neighbour lists belonging to each of the
active set cells are combined
Intra-Frequency Neighbours
Parameters
RNC
WBTS
WCELL
32
ADJS
RT
NRT
HSDPA
HOPS
100
Excessive neighbours
increase the UE measurement time
may lead to important neighbours being deleted during soft handover
Inter-frequency neighbours are usually introduced after the network has been
launched and so refining them is usually a post launch optimisation task
Customer confidential
18
NSN Siemens Networks
Inter-Frequency Neighbours
Neighbour lists are not combined for inter-RNC soft handover because the NSN
RNC does not support inter-frequency neighbour signalling across the Iur
Inter-Frequency
Neighbour List
3G Radio Planning Essentials / NPO Capability Development
Inter-Frequency Neighbours
Parameters
WBTS
WCELL
48
ADJI
RT
NRT
HOPI
100
Customer confidential
21
NSN Siemens Networks
Inter-System Neighbours
Neighbour lists are not combined for inter-RNC soft handover because the NSN
RNC does not support inter-system neighbour signalling across the Iur
Inter-System
Neighbour List
3G Radio Planning Essentials / NPO Capability Development
Inter-System Neighbours
Parameters
WBTS
WCELL
32
ADJG
RT
NRT
HOPG
100
information regarding 96 cells, but SIB11 cannot exceed 3552 bits and this is insufficient to
accommodate information regarding 96 cells
If a NSN RNC is configured with a cell which is configured with more neighbours than SIB11 can
accommodate then the cell is blocked and an alarm is raised
NSN has issued RNC Technical Note 46 to specify that when Hierarchical Cell Structure is disabled, a
maximum of 47 cells should be configured. This is a worst case figure and in general more cells can be
included
RU10 RNC support activation of SI11bis, which enables transmission of all defined neighbours
Customer confidential
24
NSN Siemens Networks
Adjg
Adjs
Adji
Complete set of
neighbours will not fit
Customer confidential
25
NSN Siemens Networks
AdjsQoffset1 or
AdjsQoffset2 included
CPICH transmit
power included
Neither
No
48 bits
Either One
No
Both
No
Neither
Yes
Either One
Yes
Both
Yes
Customer confidential
26
NSN Siemens Networks
Customer confidential
27
NSN Siemens Networks
With common
BCCH
Without 3G
neighbours
32
31
With 3G
neighbours
31
30
transfer mode then it reads the 3G neighbour list from SI2quater and PSI3quater
system information messages
When a UE is in GSM connected mode then it reads the 3G neighbour list from
measurement information messages which are sent on the SACCH
The length of a single SI2quater message is not sufficient to accommodate 32
inter-system neighbours
A single SI2quater message is able to accommodate 10 3G neighbours. This
means that it is beneficial if 3G neighbour lists can be limited to a length of 10
If multiple SI2quater messages are required then the UE must wait until it has
received the complete set before it is able to make a cell re-selection decision
If neighbours are missing then UE may fail inter-system handovers and may
remain on the GSM system longer than necessary
If 3G sites are co-sited with 2G sites then 3G neighbour lists configured within
the BSC can be based upon the existing 2G neighbour lists
Customer confidential
28
NSN Siemens Networks
Customer confidential
29
NSN Siemens Networks
3G
intra-freq
3G
inter-freq
3G
inter-sys
2G
inter-sys
Urban
16
14
14
14
Suburban
12
10
10
10
Rural
12
10
10
10
Module contents
Scrambling Code Planning
Neighbour List Planning
Location, Routing and Service Area Planning
UTRAN Registration Area Planning
Customer confidential
30
NSN Siemens Networks
Introduction
Location Areas (LA) and Routing Areas (RA) are used by the core network to track the
location of a UE
LA are used by the CS domain whereas RA are used by the PS domain
Each core network service domain has its own independent state machine for each UE
The main CS service states are CS-DETACHED, CS-IDLE and CS-CONNECTED
The main PS service states are PS-DETACHED, PS-IDLE and PS-CONNECTED
Not registered
Iu signalling
connection
Registered but no Iu
signalling connection
UE Non-Access Stratum
Non-Access Stratum
Connection Management (CM) Sublayer
MSC
LA and RA are
handled by the
Non-Access
Stratum layer
within the UE and
core network
SGSN
CS
state
Iu cs
PS
state
Iu ps
RNC
Two Iu
Signalling
Connections
Call Control
(CC) Entity
Single RRC
Connection
Node B
Access Stratum
Customer confidential
31
NSN Siemens Networks
CS
state
PS
state
3G Radio Planning UE
Essentials / NPO Capability Development
Session Management
(SM) Entity
GPRS Mobility
Management
(GMM) Entity
Location Areas
A UE in CS IDLE state does not have to update the CS core of its location
Customer confidential
32
NSN Siemens Networks
Routing Areas
A UE in PS IDLE state does not have to update the PS core of its location when
moving within a RA
a RA consists of cells belonging to one or more RNCs that are connected to the
same CN node, i.e. one SGSN
The minimum size of a Routing Area is a single cell
A RA is always contained within a single LA
it is possible for RA and LA to be defined to be equal
The mapping between a RA and its associated RNCs is handled by the SGSN
The mapping between a RA and its cells is handled by the RNC
A RA is identified globally using a Routing Area Identification (RAI)
The RAI is a concatenation of the LAI and the Routing Area Code (RAC)
1 Byte => 256 values
Maximum of 256 RA per of LA
Customer confidential
33
NSN Siemens Networks
Paging Channel
Customer confidential
34
NSN Siemens Networks
Transmission Time
Interval = 10 ms
Transport Block Size =
(4 x 8) + 48 = 80 bits
(equation from TS 25.331)
Maximum Transport Block
Set Size = 1 * 80 = 80 bits
URA_PCH RRC
state not currently
supported and so
paging does not
occur over a URA
Strategies (I)
Small LA/RA
Improves paging capacity because each IDLE state paging message is broadcast by
fewer cells
Increase in network signalling due to increased quantity of updates resulting from
mobility
Potential decrease in mobile terminated connection establishment success rate
(Potential decrease in mobile originated connection establishment success rate)
Customer confidential
35
NSN Siemens Networks
Cel
Strategies (II)
Possible to plan 2G and 3G networks using the LAI and RAI
Requires unique 2G and 3G Cell Identities (CI)
Cell Global Identification (CGI) defined by
CGI must be
unique
core network is not able to distinguish between the two networks for paging
purposes and both 2G and 3G paging appears on both the 2G and 3G networks
less chance of a UE missing a paging message when it is completing intersystem cell re-selection
increased quantity of paging on both systems and a requirement to co-ordinate
cell identities. In practice it may be difficult to implement the same location areas
for 2G and 3G as a result of them not having the same coverage areas and not
all sites being co-sited
Customer confidential
36
NSN Siemens Networks
Strategies (III)
LA and RA boundaries used for the 2G system are likely to be relatively
mature and may have already been optimised in terms of their locations
This means that they provide a good starting point for the definition of 3G LA
and RA boundaries.
LA and RA boundaries should not run close to and parallel to major roads nor
railways otherwise there is a risk of relatively large numbers of updates.
Likewise, boundaries should not traverse dense subscriber areas
Cells which are located at a LA or RA boundary and which experience large
numbers of updates should be monitored to evaluate the impact of the update
procedures.
It is only necessary to decrease the size of a RA area relative to a LA if there
is a large quantity of paging from the PS service domain
LA and RA boundaries should be accounted for during the cluster
identification task associated with pre-launch optimisation
Clusters should be defined such that LA and RA boundaries are crossed
during drive tests. This helps to verify that the update procedures are
successful and do not have a significant impact upon services
Customer confidential
37
NSN Siemens Networks
Service Areas
A Service Area (SA) is identified globally using its Service Area
Identifier (SAI)
The SAI is a concatenation of
MCC + MNC + LAC + Service Area Code (SAC)
Module contents
Scrambling Code Planning
Neighbour List Planning
Location, Routing and Service Area Planning
UTRAN Registration Area Planning
Customer confidential
39
NSN Siemens Networks
URA_PCH state
RU10 RNC support URA_PCH state transition
The purpose of this state is to decrease the cell update signaling
due to cell reselection, which saves RNC and UE resources
When the UE is in Cell_FACH or Cell_PCH state
Location is known by the cell level
Cell updates sent by the UE when a cell re-selection occurs
Customer confidential
40
NSN Siemens Networks
URA planning
The planning of URA involves a balance between paging load and
signalling load
Large URA : Paging load increases
Small URA : Frequent URA updates, signalling load and also UE power
consumption increases
Customer confidential
42
NSN Siemens Networks