Because ARFCN of two operator are sharing use due to policy from government. Operator A only input one index table acquisition all ARFCN in HDR channel list, Operator B have 3 table index acquisition that different in each region. PRL Operator A: * Index Table 1 HDR (37, 78, 119, 160, 201, 242, 283, 324 and 1019) PRL Operator B: *Index Table 1 HDR (283) *Index Table 3 HDR (1019 and 37) *Index Table 5 HDR (1019) From explanation above we can see that operator A will scanning all ARFCN that available in surrounding area which is suitable in Index Table 1 Operator A, that's why Operator A can detect Operator B channel list in all region.

1. 2012 -05 Security Level: Internal
Investigation PRL issue :
RUIM Operator A can
detect ARFCN Operator B
Date : 10 May 2012
Prepared by : Ray Khastur
Indonesia RNP/O EVDO Project Team

2. Highlight
Case :
- Operator A Ruim in Jakarta and Surabaya can detect channel (283 and 1019) from operator B
Action:
- Stationary test at different city (Yogyakarta and Denpasar) for data comparison
- Check NID and SID configuration at Operator B (Jakarta)
- Stationary test use Operator B Ruim to make sure whether this issue also happen in Operator B
Result:
Operator A Ruim in Jakarta, Surabaya, Yogyakarta, Denpasar can detect channel (283 and 1019) from other operator (Operator B)
-
NID and SID Operator B configuration is correct
-
When stationary test used Operator B Ruim, Operator A channel not detect in Operator B Ruim
-
It takes duration below 5 seconds when channel 283 and 1019 detected
-
This issue occurred in good and poor RF condition
-
Suspect:
-PRL Configuration (HDR) at Operator A in index table acquisition side too many ARFCN in one index table and not specific for each region.
Proposal Troubleshoot:
1. Need help from customer to create Operator B sectorid104 at Operator A Ruim which is set to “negative” and PN Assignment need to set “YES”
2 Need help from customer to create Operator A PRL same configuration with Operator B PRL (More specific in index table ARFCN)
Page 2

3. Loca tion
Loca tion
Jakarta
Surabaya
Page 3

4. Loca tion
 Yogyakarta
 Denpasar
Page 4

5. Norma l P RL Configura tion – EVDO(HDR)
Norma l P RL Configura tion – CDMA1x
Operator A
PRL CDMA 1x at
Operator A
configuration is
correct, because
already create
negative for other
SID
Operator B
Actually Operator B
PRL need to
configure negatif.
But this is not our
concerned at this
moment
Page 5

6. Norma l P RL Configura tion – EVDO(HDR)
Operator A
Operator B
When stationary
test used Operator B
Ruim, Operator A channel
not detect in Operator B
Ruim .
Page 6

7. 1 s t P ropos a l
1 s t P ropos a l
Create Operator B
Set to “Negative”
Sectorid104
We propose to create Operator B sectorid104 at Operator A Ruim which is set to “negative”
Page 7

8. 2 nd P ropos a l
2 nd P ropos a l
Make this value same with Operator B configuration
Since Ruim Operator B not detect Operator A Channel, we propose to create same
configuration (PN Assn & Data Assn) with Operator B PRL
Page 8

9. 2012-05 Security Level: Internal
Execution of 1’st & 2’nd
Proposal

10. SID only (Operator A)
1X
EVDO
Already register SID Operator B
Already register SID Operator B
Page 10

11. SID only (Operator A)
This configuration also can detect ARFCN 283 Operator B
This configuration also can detect ARFCN 283 Operator B
ai led
F
Page 11

12. PN Assn only (Operator A)
1X
EVDO

 Just enable PN
Just enable PN

 Assignment to YES
Assignment to YES
Page 12

13. PN Assn only (Operator A)
This configuration also can detect ARFCN 283 Operator B
This configuration also can detect ARFCN 283 Operator B
ai led
F
Page 13

14. Combiner SID & PN Assn (Operator A)
1X
EVDO

Enable PN
Enable PN

Assignment to
Assignment to
YES & SID
YES & SID
Operator B
Operator B
Page 14

15. Combiner SID & PN Assn (Operator A)
Service Lost When there is no coverage
When there is no coverage
Operator A, we get Operator BB as
Operator A, we get Operator as
Active Set
Active Set
led
Condition at Connected Data
Condition at Connected Data
ai
Service.
Service.
F
Page 15

16. ComparationSID & PN Assn (Operator B)
1X
There is no EVDO ARFCN in this section
EVDO Operator B configure
Operator B configure
their EVDO carrier more
their EVDO carrier more
specific, we need to trial
specific, we need to trial
to use this configuration also
to use this configuration also
as last investigation on PRL
as last investigation on PRL
issue.
issue.
Page 16

17. Neighbor List Operator B(poor RF condition)
Operator BB didn’t searching any different ARFCN even RF condition so poor, field test conduct in the emergency stair’s at BRI 22 Building.
Operator didn’t searching any different ARFCN even RF condition so poor, field test conduct in the emergency stair’s at BRI Building.
Page 17

18. Normal PRL on Operator A Ruim
1X
EVDO On normal PRL, Operator AA
On normal PRL, Operator
include
include
this guard band on HDR
this guard band on HDR
Generic. And all ARFCN are
Generic. And all ARFCN are
in the list of PRL.
in the list of PRL.
Page 18

19. Normal PRL on Operator A Ruim
At normal IMSI we find another ARFCN 324,
At normal IMSI we find another ARFCN 324,
due to in Operator A PRL list guardband 324
due to in Operator A PRL list guardband 324
available also.
available also.
Page 19

20. 3 rd P ropos a l
After discussion with Operator A Device team on 16th May 2012, here is our 3rd Proposal :
* We proposed to make EVDO channel list more specific and 1X also.
Page 20

21. 3rd Proposal for 1X (Operator A)
We proposed to register only specific ARFCN that using in 1X only.
We proposed to register only specific ARFCN that using in 1X only.
Page 21

22. 3rd Proposal Last Proposal for EVDO (Operator A)
We proposed to register only specific ARFCN that using in EVDO only.
We proposed to register only specific ARFCN that using in EVDO only.


Page 22

23. 2012-05 Security Level: Internal
Execution of 3rd Proposal

24. Result RUIM 1 Operator A (with 3rd Proposal)
No more strange ARFCN detected from Operator A Neighbor List after implement last proposal
ss
ce
Suc
Page 24

25. Connection Setup Time RUIM 1 Operator A
From this IMSI that already modified PRL take 4 second’s approximate
Page 25

26. Result RUIM 2 Operator A (with 3rd Proposal)
No more strange ARFCN detected from Operator A Neighbor List after implement last proposal
ss
ce
Suc
Page 26

27. Connection Setup Time RUIM 2 Operator A
From this IMSI that already modified PRL take 9 second’s approximate
Page 27

28. Result RUIM 3 Operator A (with 3rd Proposal)
No more strange ARFCN detected from Operator A Neighbor List after implement last proposal
ss
ce
Suc
Page 28

29. Connection Setup Time RUIM 3 Operator A
From this IMSI that already modified PRL take 8 second’s approximate
Page 29

30. Compare with Normal Operator A IMSI
At the same time we try again check Neighbor List using normal IMSI and we detected 283 and 324 as strong
Pseudo Noise (PN).
Page 30

31. Connection Setup Time normal IMSI Operator A
From this IMSI with normal PRL take 9 second’s approximate
Page 31

32. Summary for 3rd Proposal
1. SID and NID configuration from each operator already consistent and not similar.
2. Acquisition Table in PRL act as ARFCN filter, if we defined all channel as EVDO channel list
the RUIM will searching all and will try to entering to another EVDO network.
3. There is no significant different fir Connection Time between normal IMSI and modified IMSI.
Page 32

33. How a bout Ope ra tor A outs ide J a ka rta & Ba ndung?
After discussion with Operator A RF team on 18 th May 2012, there is posibility 1019 Operator B
will enter again our neighbor list due to in index 1 ARFCN 1019 are in Operator A PRL list. Our next plan:
1. Change ARFCN sequential, (201 and 242) at the first index table so it will be first priority in scanning frequency activity.
2. ARFCN (1019, 37,78 and 160) at second index table will be function as Roaming channel
list when subscriber from Outside 201 coverage to 1019 coverage.
Page 33

34. 4th Proposal for EVDO (Operator A)
Table Acquisition 1 include 201 and 242 as the HDR channel list for the first scanning priority.
Table Acquisition 1 include 201 and 242 as the HDR channel list for the first scanning priority.
Table Acquisition 3 include 1019, 37, 78 and 160 as the HDR second channel list for roaming.
Table Acquisition 3 include 1019, 37, 78 and 160 as the HDR second channel list for roaming.
Page 34

35. 2012-05 Security Level: Internal
Execution of 4th Proposal and Compare with 3rd Proposal
at Surabaya

36. 3rd Proposal EVDO (Operator A)
We test third proposal on Surabaya, the result still detect 1019. Then we compare with forth proposal.
We test third proposal on Surabaya, the result still detect 1019. Then we compare with forth proposal.
Page 36

37. Result 3rd Proposal for EVDO (Operator A) Surabaya
ai led
F
Due to 1019 at the first priority for scanning frequency, the RUIM still detect 1019
Due to 1019 at the first priority for scanning frequency, the RUIM still detect 1019
as neighbor list.
as neighbor list.
Page 37

38. 4th Proposal for EVDO (Operator A) Surabaya
Table Acquisition 11include 201 and 242 as the HDR channel list for the first scanning priority.
Table Acquisition include 201 and 242 as the HDR channel list for the first scanning priority.
Table Acquisition 33include 1019, 37, 78 and 160 as the HDR second channel list for roaming.
Table Acquisition include 1019, 37, 78 and 160 as the HDR second channel list for roaming.
Page 38

39. Result 4th Proposal for EVDO (Operator A) at Surabaya
ss
ce
Suc
From NL we only detect 201 and 242 as EVDO NL and stop scanning at 1 acquisition
From NL we only detect 201 and 242 as EVDO NL and stop scanning at 1 acquisition
table only.
table only.
Page 39

40. Result 4th Proposal for EVDO (Operator A) at Jakarta
ss
ce
Suc
We only detect 1019 as dominant channel number. No more strange channel
We only detect 1019 as dominant channel number. No more strange channel
list detected
list detected
Page 40

41. Conclusion
1.1. Scanning First Index Table from Left to Right, ifif
Scanning First Index Table from Left to Right, 2.2. When subscriber moving from 201 and 242
When subscriber moving from 201 and 242
there is not detect 201 or 242
there is not detect 201 or 242 coverage to 1019 coverage with the same SID.
coverage to 1019 coverage with the same SID.
going down to index table number 33
going down to index table number RUIM only scanning channel list at index table
RUIM only scanning channel list at index table
number 33only.
number only.
Page 41

42. Solution and Impact
1. After 4 times investigation with any variation and possibility of PRL
configuration, the last proposal are suitable for solution to prevent different
channel number from other operator to not entering as our Neighbor List.
2. Last proposal is suitable for all region Operator A coverage.
Page 42

43. Thank You