Академический Документы
Профессиональный Документы
Культура Документы
FREQUENCY
HOPPING
Page 1
3/17/2015
Page 2
3/17/2015
2. Interference Averaging
Interference Averaging means spreading raw bit errors (BER
caused by the interference) in order to have random distribution of
errors instead of having burst of errors, and therefore, enhance the
effectiveness of decoding and de-interleaving process to cope with
the BER and lead to better value of FER.
With hopping, the set of interfering calls will be continually
changing and the effect is that all the calls experience average
quality rather than extreme situations of either good or bad quality.
All the calls suffer from controlled interference but only for short
and distant periods of time, not for all the duration of the call.
For the same capacity, Frequency Hopping improves quality and
for a given average quality Frequency Hopping makes possible
increase in capacity.
Document Prepared by Ajay Ghanekar
Page 3
3/17/2015
Page 4
3/17/2015
Page 5
3/17/2015
If a network running with fixed frequency plan is switched over to BBH (BCCH included
in MA list) without any frequency changes, significant quality improvement can be
observed in the network. As a result drop call rate reduces in the network. Alternatively,
for the existing network quality additional capacity can be provided. FHI can be used
effectively in BBH. Further details regarding FHI planning are discussed later in the
document.
Page 6
3/17/2015
Page 7
3/17/2015
GSM algorithm
GSM has defined an algorithm for deciding hopping sequence.
The algorithm is used to generate Mobile Allocation Index (MAI)
for a given set of parameters.
ARFCN: absolute radio frequency channel number
MA: mobile allocation frequencies.
MAIO: Mobile allocation offset (0 to N-1), where N is the number
of frequencies defined in MA.
HSN: Hopping sequence number (0-63)
T1: Super frame number (0-2047)
T2: TCH multiframe number (0-25)
T3: Signaling multiframe number (0-50)
This algorithm generates a pseudo-random sequence of MAIs.
MAI along with MAIO and MA will decide the actual ARFCN to
be used for the burst.
Page 8
3/17/2015
Page 9
3/17/2015
2. Planning of HSN:
HSN allocation to the cells is done in random fashion. Various
scenarios are explained below:
a. MA list is same for all the cells of the site In this case HSN is
kept same for all the cells of the site. MAIO is used on per
carrier basis to provide offset for starting frequency in hopping
sequence and avoid hits among carriers of the site. Practically it
is possible to achieve 0% hit rate within the site, as all the cells
of the same site are synchronized.
b. MA list is same for the cells of different sites In this case HSN
should be different for all such cells. MAIO can be same or
different in this case as HSN is different.
c. MA list is different for the cells In this case HSN planning is
not important, as there can not be any hits between these cells.
d. HSN is set to 0 This is the case of cyclic hopping. The
sequence for hopping remains same and is repeated
continuously.
This is not recommended in the urban
environment where frequency reuse is more. This is because the
network is not synchronized so if there is any one hit it will
result in continuous sequence of hits. Cyclic hopping is
preferred in rural environment as it provides the maximum
benefits of frequency diversity.
Page 10
3/17/2015
3. Planning of MAIO:
The benefits of MAIO planning can be best achieved only in case
when sectors having same MA list are synchronized. For nonsynchronized sectors MAIO can be the same. In the previous
version (GSR2), Motorola did not provide manual MAIO setting.
It was set automatically by the system. However from GSR3
onwards it is be possible to set MAIO manually. It has to be
changed on a case to case basis. In cases where there are large
numbers of hits, MAIO change can be effective as it adds the offset
in the hopping sequence and hit-rate can be reduced.
4. Planning of FHI:
This parameter is not specified in GSM. FHI is the Motorola
defined hopping system. It actually means an independent hopping
system consisting of MA and HSN. Total of 4 such hopping
systems can be set in a cell.
FHI can be defined on a timeslot basis.
e.g. consider a cell with 3 carriers i.e. 2 carriers are hopping. It is
then possible to define 4 different FHIs for 16 timeslots. That
means timeslot 0 to 3 of 1 carrier can have one FHI and so on.
Page 11
3/17/2015
Page 12
3/17/2015
Page 13
3/17/2015
Page 14
3/17/2015
Page 15
3/17/2015
Page 16
3/17/2015
Page 17
3/17/2015
Page 18
3/17/2015
Page 19
3/17/2015
13.
14.
15.
16.
17.
18.
Page 20
3/17/2015
RF Loss rate
TCH RF Loss Rate
SDCCH RF Loss Rate
Handover Failure Rate
Handover Success Rate
TCH Assignment Success Rate
Call Success Rate
Drop Call rate
Drop Call Rate per Erlang
Interference on Idle
Out_ho_cause_atmpt
2. Drive Test
Drive test should be done using Tems and CellAD or Buzzard
(subjective voice quality measurement).
Enough samples of drive tests should be taken before after each
change made to the network (or part of the network)
FICS report should be generated to check the drive test results.
GIMS/Mapinfo should be used to plot the drive test and to
identify new problem areas. Drive test plots should provide
RXQual, RxLev, Handovers, Handover Channel and Drop
Calls. This is very useful to identify the change in any of the
areas and the cause. Separate FER plot should be taken to
identify the change.
3. Frequency Planning
BCCH Plan is very critical for success of SFH implementation.
Motorola provides a feature called NBCCH full Power. This
ensures that NBCCH carrier radiates at full power even if there
is no call on it. This feature can be used to check the planned
Page 21
3/17/2015
Page 22
3/17/2015
RESULT
a. SDCCH Hopping
No Problem Found
b. Up Link DTX
No Problem Found
c. Combined/non-combined multiframe
No Problem
Found
d. Non Combined & Extended Paging No Problem Found
e. NBCCH at Full Power
Quality degradation
observed in
some areas but no
degradation in FER.
f. 1 X 1 re use plan
Some Quality
improvement observed
in Vashi Bridge area
g. Change in MA List
No Improvements
h. Locking of Boundary site neighbours
No
Improvements
i. Integration of Koperkhirane
Difficulty in BCCH
plan &
Ease in NBCCH Plan.
Degradation in neighour
sites observed
j. Downlink DTx
No problems found.
k. Downlink DTx and extended paging
Siemens S3+
does not do location
update.
l.
Extended Paging
No problems found
Page 23
3/17/2015
Drive Tests:
Observations: From the drive results following are the areas that
had shown Voice Quality problems.
Area A Alta Mount Road, Walkeshwar, Chowpatty
Area B E.Moses Road, Bandra Kurla Complex, Mahim-Sion
Link Rd.
Area C Band Stand, Carter Road, SV Road near Mithibai
College, Western Express Highway near Domestic Airport, Powai
Area D LBS Road Near Kurla, Eastern Express Highway near
Chembur.
Area E Marve Road, Vasai, Essel World
In the above areas Rx Voice Quality was in levels of 6 & 7.
However the call did not drop.
TEMS Drive was repeated to check consistency of the results. In
some areas consistency could not be established. The results are
dependent on the traffic (loading) carried during the drive and also
on the quality of BCCH or the hopping carriers.
GOS Statistics:
Observation: In general, it was observed that in all the BSCs the
HSR, CSR, DCR have degraded marginally except in Powai BSC
and Thane BSC, where, there was considerable degradation in
HSR.
Following sectors were found to be degraded:
CSR Degradation :
HSR Degradation :
1. Flora Fountain V3
1. Cuffe Parade
2. Eros V2
2. Bandra Kurla V3
Page 24
3/17/2015
3.
4.
5.
6.
7.
8.
9.
Santacruz V1
Mahim Station V3
Crawford Market V1
Juhu Galli V2
D Road V1
Kings Circle V3
Mira Road V3
3.Mahim Station V1
4.Vashi Sect-17 V3
5.Belapur V3
6. Kalamboli V1,V3
7. Girgaum V3
8. Sewree V3
9.Sahar V1
10.MIDC V1
11.Powai Hirmdani V1
12.Mumbra V1
13.Kalyan V1
14.Ghodbunder Road V2
15.Charkop V1
Of all the BSCs it was observed that Powai BSC has degraded
considerably in HSR, CSR and DCR. Six sectors have HSR less
than 90% in this BSC.
In Thane BSC, it was observed that the HSR has gone low in 4
sectors and DCR has gone high in 2 sectors.
Coverage Reduction:
It was observed that after implementing hopping in the network,
following sectors have shown coverage reduction. This was
observed during the drive tests and problem statements have been
issued to check the BTS power and VSWR.
The sectors are:
1. Andheri V1
2. Bandra Causeway V2
3. IES V1 (for additional 2 carriers)
4. Thane V2
5. Thane Stn V1
Page 25
3/17/2015
6.
7.
8.
9.
Vashi V2
Kings Circle V1
Kalina V2, V3
Malad V3
Page 26
3/17/2015
Page 27
3/17/2015
Heera Panna
Churchgate BPL Gallery
PH Business Centre
Kamats, Cuffe Parade
Observation:
There was not any degradation in signals observed in the above
places. The power level and coverage were the same as it was
during the Fixed plan.
Data Call :
On drive data call was made to check the data call feature in
Hopping mode. The data was tried both in Mobile to Mobile calls
and in Mobile to PSTN Call.
Observation:
The data call facility worked well in areas where the Rx Qual was
upto 6. In areas where there were multiple 6 & 7 the data call
dropped.
Also it was observed that for files of size 200KB, the data
transmission takes at a speed of 8KB to 8.5KB and the data rate
goes down to 5KB. Never the data is transferred at 9600KB.
Co Channel BCCH and Co Channel BSIC Care has been
taken to avoid Co channel BCCH and Co BSIC problems during
implementation of SFH, it was observed that the Co channel
BCCH and Co BSIC of neighbours also to be avoided. This
problem is not visible on field but it results in degradation in
Page 28
3/17/2015
Downlink DTx
1. Location update tests were done in location area boundary
between Sion V1 and Chunabhatti V2 (LAC 122 and 123).
These checks were done to check location update from Sion V1
to Chunabhatti V2 and back. Calls were initiated and received
on all the phones to check whether location update has taken
place.
2. Following phones were used for testing:
Siemens S3+
Siemens S4, S4 power
Siemens S10
Sony CMDX1000
Motorola 8700
Nokia 2110
Nokia 5110
Nokia 8110
Ericsson GH688 (TEMS)
Following Features were tried with different combinations and
drive tests were done:
BCCH Combined
BCCH Non Combined
SDCCH on BCCH
SDCCH on NBCCH
Extended Paging
Page 29
3/17/2015
DTx
Tests and Results:
1. Drive 1: Sion V1 BCCH combined, SD on BCCH, no
extended paging, DTx enabled.
- Result: No problems found
2. Drive 2: Sion V1 BCCH non combined, SD on NBCCH
(hopping), no extended paging, DTx enabled.
- Result: No problems found
3. Drive 3: Sion V1 BCCH non-combined, SD on NBCCH
(hopping). Extended paging active, DTx enabled.
- Result: Problem with S3+, it did not perform location
update. Call origination and termination was not possible.
Phone locked to Sion V1 (Reselection was possible without
location update) as phone was showing full signal strength.
Even after turning off/on, location update was in consistant.
This was due to Extended Paging being Active.
4. Drive 4: Sion V1 BCCH non-combined, SD on NBCCH
(hopping), no extended paging, DTx enabled.
- Result: No problems found
5. Drive 5: Sion V1 - BCCH combined, SD on BCCH, no
extended paging, DTx enabled.
- Result: No problems found
References:
- Motorola document on Frequency Hopping for Capacity
Improvement (Review 0.3)
- Motorola BSS Command Reference
- GSM Recommendations 5.02
Page 30
3/17/2015
Page 31
3/17/2015