You are on page 1of 27

LTE Solution Strategy

Overview & Proposal


Content

LTE Solution Strategy Overview

LTE1800/2100 New Site Plan Guideline

Analysis of LTE2100

Analysis for LTE17.7M

Analysis for GUL900

2
LTE Solution Strategy Overview (LTE900/1800/2100, TDD2300)

Dense Urban / Urban Suburban Rural / Highway


LTE1800: 15M LTE1800: 10M
Now U2100: 15M (S333) U2100: 15M (S333) U2100: 10M (S222)

EOY LTE1800: 17.7M (Flexible Band)* LTE1800: 15M


U2100: 15M (S333) U2100: 15M (S333) U2100: 10M (S222)
2017 GUL900: LTE5M+U4.2M+DCS S333 GUL900: LTE5M+U4.2M+DCS S333 LTE2100: 5M**

LTE1800: 17.7M (Flexible Band) LTE1800: 15M LTE1800: 10M


2018 U2100: 15M (S333) U2100: 15M (S333) U2100: 10M (S222)
GUL900: LTE5M+U4.2M+DCS S333 GUL900: LTE5M+U4.2M+DCS S333 LTE2100: 5M
TDD2300: 30M
Solution for LTE Capacity Demand Solution for LTE Blue Ocean
1: Quick win by upgrade LTE15M to LTE17.7M (Flexible band) SW&license 1: Quick win by LTE 2100 5M by license
2: GUL900 with good indoor penetration to get more user (only select the U2100 site HW ready)
3: High Capacity by TDD2300 30M new spectrum 2: LTE1800 will deploy according the
* LTE 17.7M flexible band need upgrade SRAN and OSS to version 12.1 marketing demand
3 ** LTE2100 colo with existing U2100 site by license only , cost 30% of LTE 1800 new site
Concept for LTE2100 Blue Ocean (Get More Data Subscriber)
Jakarta Network Sample (11 RNC)

LTE 1.1
2G voice only user with Why MBB device in 2G?
MBB device Dual Sim Card User –
Network 3G 1.5 0.7 (1.4M) price sensitive user?

2G 2.34 1.1 0.92

2G 3G LTE

device Concept for LTE Blue Ocean


1: Enlarger LTE Footprint by limited Capex –
LTE2100 (5M) over existing U2100
2: Get More Data Subscriber by LTE package
promotion in the area without LTE – win back
the price sensitive user, need effort from sales
team
Source: 24 Hours, Feb, from Smart care

4
LTE Red Site Solution Proposal
LTE Red Site

Neighbor N LTE
any 3G site
Densification
standalone
Y
N
Can upgrade Upgrade to
to LTE15M LTE15M
Y

*GUL900 Criteria refer to <<Analysis of GUL900>>


In GUL900 N
LTE900 will use P-band if in GUL900 polygon
Polygon* Colo LTE900

Fulfill LTE N
Multi-Sector LTE Multi-
Criteria Sector
Y

** LTE17.7M(Flex band) refer to <<Analysis of LTE177M>>


1: Need upgrade SRAN Version to 12.1 and Upgrade OSS
LTE 17.7M (Flex
band) **
2: Need downgrade DCS to S333 (GFR and offloading needed)
3: RRU1800 need support 2*80Wwpower

5
Content

LTE Solution Strategy Overview

LTE1800/2100 New Site Plan Guideline

Analysis of LTE2100

Analysis for LTE17.7M

Analysis for GUL900

6
LTE Solutions Dependency Overview
Re-
Spectrum SRAN Version Implementation
Solutions UE Depenancy HW Requirement Farming/Offlo Objective Cost Remarks
Readiness Readiness Area
ading
LTE Blue Ocean
Deploy in the area 3G with
Get More Data Outer Area
LTE2100 HW dependency, low utilization to minimize
92% UE Need Subscriber, (without
(10MHz UMTS need analysis site Low 3G offloading
Ready support Ready offloading Improve 2100 LTE1800
+ 5MHz LTE) by site requirement, LTE2100 site
spectrum coverage)
might low utilization
efficiency
Need HW dependency, if Need Re- DCS down grade to S333,
L1800 17.7 100% UE Inner/Dense
Ready upgrade to from LTE15M to farming & Capacity Solution Low 2*60W RRU might have
MHz support Area
SRAN12.1 LTE17.7, HW ready offloading power issue
Not yet
LTE 2300 MHz Ready 77% UE Inner/Dense
Ready HW dependency No need Capacity Solution High
(TDD) (Q4 support Area
2018?)
Improve Indoor
HW dependency Need Re-
67% UE Penetration, Get Inner/Dense
GUL 900 Ready Ready ,need analysis site farming & High
support More voice and Area
by site offloading
data subscriber

Quick Win
LTE Blue Ocean by LTE2100 in the area by license only to get more data subscriber
LTE1800 17.7M by software and license in BBC6+BBC24 to fulfill the high payload demand
GUL900 to improve indoor penetration to get more voice and data subscriber
Long Term
LTE 2300 (TDD) with high capacity to fulfill future payload growth
7
LTE 2100 & LTE 1800 New NE Deployment Guideline (Proposal)
LTE Blue Ocean 3G U2100 LTE Demand
Enlarge LTE coverage by L2100
Excellent user experience by L1800
In the are without LTE1800 N Existing/Plan
LTE1800 Y

U2100 need Polygon >45GB


Y Y New LTE1800
offloading Payload
Solution? >350 UE
Site

N
1 Kecamantan
with >80%
U2100 site N
safe Inside Existing N
Downgrade End
LTE Polygon

Hardware N Y
ready for
LTE2100 >30GB N
Payload End
Y *Only select the LTE2100 by
>100 UE**
N license, cost only 30% of LTE1800
>15GB new site, thus change criteria from Y
Payload 45GB&350UE to 15GB&100UE,
>100 UE* and this 100 UE = sum physical site New LTE1800
(LTE UE in 2G + LTE UE in 3G) Site
Y

LTE2100
End
(Blue Ocean)
 LTE 2100 for enlarging LTE coverage in remote outer area and get
**for the 3G site insider LTE polygon, propose to change criteria more data subscriber by Low investment cost
from 45GB&350UE to 30GB&100UE, data refer to next page  LTE 1800 for high user experience LTE demand
8
New Criteria Proposal for LTE colo 3G site

3G Payload Vs LTE Payload LTE UE in 3G Vs LTE Payload


250 250

200 200

150 150

Before 4G UE in 3G > 100 UE


100 100
Before 3G Payload > 100GB/Day after LTE on air,
after LTE on air, LTE Payload >100GB/Day
50 50
LTE Payload >100GB/Day
0 0
0-10 10-20 20-30 30-40 40-50 50-60 60-70 70-80 80-90 90-100 0-49 50-99 100-149 150-199 200-249 250-299 300-349 350-399 400-449 450-500

• There are 574 3G Macro standalone before Feb/2017.


• Those 574 3G site with colo LTE on air by Mar/2017
• Get Feb/2017 3G data as before, Apr/2017 data as LTE site payload to study the correction between
3G payload and LTE payload
Conclusion :
LTE site to get 100GB/Day Payload after LTE on air, the 3G criteria as below
3G Payload > 30GB
LTE UE in 3G > 100
9
Content

LTE Solution Strategy Overview

LTE1800/2100 New Site Plan Guideline

Analysis of LTE2100

Analysis for LTE17.7M

Analysis for GUL900

10
LTE 2100 (Blue Ocean) Planning Guideline
LTE Blue Ocean Planning Guideline 3G Criteria for Safe downgrade to S222
3G U2100 out of
LTE1800 Polyogon
DL Power Occupancy (%)
U2100 need Y
offloading Now Non HS Power < 40%, with predicted after downgrade to
Solution?
S222 will be 50%
1 Kecamantan
with >80%
U2100 site N
safe
HSDPA User
Downgrade
No HS User<16.7, with predicted after downgrade to S222 will
Hardware N be 25 (50%)
ready for
LTE2100
Y
RTWP
N
>15GB Now RTWP< -98 dBm (proposed), with predicted after
Payload downgrade to S222 will be -95dbm
>100 UE*
Y
LTE2100
End Propose 1 Kecamatna with >80% U2100 site safe to downgrade
(Blue Ocean)
*Only select the LTE2100 site by license, cost only 30% of LTE1800 new to S222, this Kecamantan can re-farming 5M for LTE2100 (5M)
site, thus change criteria from 45GB&350UE to 15GB&100UE, and this 100
UE = sum physical site (LTE UE in 2G + LTE UE in 3G)
11
UL2100 Assessment on Existing U2100 Sites
--- HW Equipment Requirement
UBBP ready RRU Ready CPRI Ready UMPT Ready Antenna
minimum 2 PA (3839v3 or Support UMPTa,
Sector < 4 3829v3) minimum 2.5 G UMPTb Can use existing
U2100 Stand Alone Minimum 2*UBBPd6 / 1*UBBPd6 +
1*WBBf4 Exclude WMPT
UBBPd6 should be at Slot 3, Slot2
minimum 2 PA (3839v3 or Support UMPTa,
Sector < 4 3829v3) minimum 2.5 G UMPTb Can use existing
U2100 Colo With L1800 Minimum 2*UBBPd6 / 1*UBBPd6 +
2*WBBf4 Exclude WMPT
UBBPd6 should be at Slot 3, Slot2
minimum 2 PA (3839v3 or Support UMPTa,
Sector < 4 3829v3) minimum 2.5 G UMPTb Can use existing
U2100 Colo With U900 Minimum 2*UBBPd6 / 1*UBBPd6 +
2*WBBf4 Exclude WMPT
UBBPd6 should be at Slot 3, Slot2
minimum 2 PA (3839v3 or Support UMPTa,
Sector < 4 3829v3) minimum 2.5 G UMPTb Can use existing
Minimum 3*UBBPd6 / 1*UBBPd6 +
U2100 Colo With U900 & L1800
3*WBBf4 Exclude WMPT
/2*UBBPd6 + 1*WBBf4
UBBPd6 should be at Slot 3, Slot2

12
UL2100 readiness full stat Summary
Every KECAMATAN 5 criteria for UL2100 readiness:
1. LTE colo ratio
2. Current hardware ready (BBU+RRU), can directly software open
3. UMTS capacity is ready for downgrade to S222
4. LTE red site number
5. L2100 UE capability
6. RTWP

UMTS LTE
hardware No data at LTE Red Sites L2100 UE RTWP Safe
UMTS SITE LTE SITE capacity Colo
ready ratio SIT (May Data) support ratio Ratio
PROVINSI KABKOT KECAMATAN NUMBER NUMBER safe ratio Ratio
LAMPUNG KOTA BANDAR LAMPUNG TELUK BETUNG SELATAN 11 9 64% 0% 91% 0% 91% 100% 45.00%
LAMPUNG KOTA BANDAR LAMPUNG KEDATON 12 9 83% 0% 100% 0% 91% 100% 42.86%
BENGKULU KOTA BENGKULU TELUK SEGARA 6 5 83% 0% 100% 0% 98% 100% 45.45%
JAWA BARAT KOTA BEKASI RAWALUMBU 48 37 71% 0% 85% 3% 100% 90% 43.53%
JAWA BARAT KOTA CIREBON KESAMBI 28 19 61% 0% 93% 0% 65% 89% 40.43%
JAWA BARAT CIREBON PLUMBON 9 7 67% 0% 89% 0% 94% 100% 43.75%
JAMBI BUNGO TANAH TUMBUH 1 1 100% 0% 100% 0% 95% 100% 50.00%
SUMATERA SELATAN KOTA PALEMBANG SEBERANG ULU II 21 15 62% 0% 95% 0% 91% 81% 41.67%
LAMPUNG LAMPUNG TIMUR METRO KIBANG 1 1 100% 0% 100% 0% 91% 100% 50.00%
DAERAH ISTIMEWA YOGYAKARTA KOTA YOGYAKARTA NGAMPILAN 3 3 67% 0% 100% 0% 91% 33% 50.00%

This table is filtered:


LTE colo ratio>40%
Current hardware ready>60%
UMTS capacity safe >80%

13
ULO (Commissioning Certificate) Candidates
--- by Kecamatan
UMTS L2100 UE LTE
hardware No data at LTE Red Sites RTWP Safe
UMTS SITE LTE SITE capacity support Colo
ready ratio SIT (May Data) Ratio
PROVINSI KABKOT KECAMATAN NUMBER NUMBER safe ratio ratio Ratio
LAMPUNG KOTA BANDAR LAMPUNG TELUK BETUNG SELATAN 11 9 64% 0% 91% 0% 91% 100% 45%
LAMPUNG KOTA BANDAR LAMPUNG KEDATON 12 9 83% 0% 100% 0% 91% 100% 43%
BENGKULU KOTA BENGKULU TELUK SEGARA 6 5 83% 0% 100% 0% 98% 100% 45%
JAWA BARAT KOTA DEPOK CIMANGGIS 59 43 58% 0% 92% 7% 94% 93% 42%
JAWA TIMUR KOTA MALANG SUKUN 41 31 51% 2% 83% 0% 93% 95% 43%
BANTEN KOTA TANGERANG SELATAN PONDOK AREN 71 56 58% 0% 86% 2% 93% 94% 44%
JAWA BARAT CIREBON PLUMBON 9 7 67% 0% 89% 0% 94% 100% 44%
BANTEN KOTA TANGERANG CIPONDOH 47 39 60% 0% 85% 0% 92% 98% 45%
JAMBI BUNGO TANAH TUMBUH 1 1 100% 0% 100% 0% 95% 100% 50%
LAMPUNG LAMPUNG TIMUR METRO KIBANG 1 1 100% 0% 100% 0% 91% 100% 50%

Criteria :
UMTS Number > 6
LTE colo ratio>40%
Current hardware ready>60%
UMTS capacity safe >80%
LTE2100 UE Support > 90%
RTWP Safe Ratio > 90%

14
Content

LTE Solution Strategy Overview

LTE1800/2100 New Site Plan Guideline

Analysis of LTE2100

Analysis for LTE17.7M

Analysis for GUL900

15
LTE Cloud-Air Planning Guideline
LTE Cloud-Air RB Number Design LTE Cloud-Air Polygon Design
LTE High
Minimum DCS Demand
Configure Polygon Identify
Required (S333)

DCS Offloading DCS Offloading


24 Channel Analysis Solution
LTE 17.7M
(4.8M) Required
Analysis
for DCS S333*

HW Dependency
for LTE Cloud –
Air**
LTE 17.7M RB
Number (e.g.
94RB) Output LTE
Cloud-Air Design
Result

*To verify DCS S333 by 24 Channel *12 for BCCH, 12 for TCH with 50%
loading whether will impact DCS quality, Huawei will conduct trial in Propose existing LTE15M polygon upgrade to LTE Cloud-
Jakarta (Senayan city cluster) Air polygon

16 * *LTE 17.7M + DCS S333 need 2*80W power RRU, if the site with 2*60w RRU, need replace
CloudAIR-94RB (SRAN 12.1 needed)

Regular area: 14BCCH+16TCH=S333 1865.75 1879.25 1880


1857.5 1864.9

2G Ch.804
2G Ch.775

2G Ch.780

2G Ch.781

2G Ch.791

2G Ch.805
Ch.790

Ch.810
GB 774

PRB74

PRB75
2G

PRB1

PRB2
---- ---- ---- ----
------

1857.7 Indoor 10 TCH 14 BCCH 6 TCH

1879.25 1880

1862.5 1863.25 1870 1876.75 1877.5


Buffer Zone: 12 BCCH+12 TCH 1861.7 1879.1 1879.9
B

Ch.882
Ch.883
Ch.884
Ch.885
GB 774

Ch.794
Ch.787
Ch.788
Ch.789
Ch.790
Ch.791
Ch.792
Ch.793
Ch.775

Ch.782
Ch.783
Ch.784
Ch.785
Ch.786

PRB74
PRB75
C

PRB1
PRB2
C ------
H
3TCH

LTE Cloud-Air Polygon: 12 BCCH+12 TCH=S333


1860 1861 1862 1870 1879 1880
1857.7 1859.3 1859.9 94RB
1861.7 1879.1 1879.9
GB 774
Ch.775

Ch.782
Ch.783
Ch.784
Ch.785
Ch.786
Ch.787
Ch.788
Ch.789
Ch.790
Ch.791
Ch.792
Ch.793
Ch.794

Ch.882
Ch.883
Ch.884
Ch.885
300K

PRB98

100K
PRB99
PRB7
PRB6

100K
----
------
8BCCH 8TCH 4TCH

17
DCS1800 offloading Analysis (S333)
R10 R2 R3 R4 R5 R6
R1 Sumbagt Sumbag Jabodet West Centra East
Offloading Solution Sumbagut eng sel abek Java l Java Java
Safe 101 52 964 2371 1127 1610 1807
Optimization 60 58 367 1135 444 892 565
DCS TRX Upgrade 4 1 394 3 30 7
Offload Colo GSM 57 32 261 296 136 67 111
GSM TRX Upgrade 7 5 302 72 182 102 145
Proposed New Site GSM Colo 193 119 210 201 333 96 217
Proposed New Site Neighbour 45 25 70 119 20 9 24
Grand Total 467 291 2175 4588 2245 2806 2876

The offloading analysis base on DCS will downgrade to S333, this result
is region basis,
City basis is needed after LTE17.7M polygon finalize

18
Content

LTE Solution Strategy Overview

LTE1800/2100 New Site Plan Guideline

Analysis of LTE2100

Analysis for LTE17.7M

Analysis for GUL900

19
Overall Concept For GUL900

After acquire additional 7.5M in 900 E-band, Tsel have totally 15M freq in 900M which
provide Tsel more advantage among all competitor (ISAT 12.5M, XL 7.5M, HCPT 0M).
Thus GUL900 with continuous coverage is proposed

Maximize 900 spectrum efficiency


Need 900 as lower band continuous coverage to improve indoor coverage for 3G and LTE
Continuous U900 coverage provide soft-handover for U900 rather than U900 to U2100 hard
handover for good voice experience.
U900 colo with LTE900 to provide good user experience when CS fall-back
LTE900 provide good coverage for VoLTE consideration
U900 can help to speed up migrate U2100 to LTE2100.

20
GUL900M Site Selection Criteria - (Candidate Site Selection)
Site Selection Criteria
• Step1: Existing 900M sites which fulfill below criteria will be selected for GUL900M candidate
L900 site Criteria:
-sum of LTE handsets in 2G/3G site more than 380;
-max of poor coverage ratio of LTE sites less than -100dbm based on MR is more than 20% AND
The above two criteria refer to the nearest 4 New Sites to 900M site within 1km
if more than 1km, will refer to the New Site itself

U900 site Criteria:


-sum of 3G handset in 2G site more than 420;
-max poor coverage ratio of 3G sites less than -95dbm based on MR is more than 20%
AND
The above two criteria refer to the nearest 4 New Sites to 900M site within 1km.
if more than 1km, will refer to the New Site itself

• Step2: coverage target


-additional site will be selected to meet coverage target as below(candidate sites from 900M sites)
L900 RSRP >= -100dbm@95%.
U900 RSCP >= -95dbm@95%.

21
GUL900M Site Selection Criteria - (Priority Definition)

• Step3: Define GUL900 cluster and priority definition

 Consider max 3G&LTE utilization% and revenue to defiSite priority


 Revenue include 2G and 3G and LTE in GUL site
Uti%/Revenue R4 R3 R2 R1
>60% 3 6 584 811
40%-60% 2 24 133 24
<40% 7 58 69 3
Grand Total 12 88 786 838
 Check area where has high potential revenue and high 3G occupancy to define as high priority

• 3G utilization = 3G occupancy%
• LTE utilization = LTE DL PRB%

22
GUL900M Priority Definition
Revenue Map Utilization% Map

 Bekasi area has high revenue and high utilization


 Tangerang area has high revenue and high utilization
 Inner Jakarta area has high revenue and high utilization
 Depok area has mid revenue and high utilization
23
GUL900M Priority Definition_based on cluster level
Propose cluster implementation
Inner combine between potential revenue
and occupancy%
Jakarta
Tangera 4 main cluster&priority is:
ng Bekasi Bekasi Area---Priority1
Tangerang Area---Priority1
Jakarta inner Area---Priority2
Depok Area---Priority3
Other Area---Priority4

The rest out of 4 cluster will consider


as last priority

Number of High priority Priority


Clusters
Depok site site%(*) cluster
BEKASI 300 97.33% 1
TANGERANG 337 97.92% 1
INNER Jakarta 437 97.17% 2
DEPOK 449 96.44% 3
Other area 201 69.65% 4
Grand Total 1724

* High priority site%


24 means(p1+p2)/Total sites
GUL900M Priority Definition_based on small cluster level
 Propose small cluster for GUL900 delivery
 One small cluster include 30 to 150 sites
 Define small cluster in priority1,2,3
 Bekasi include 6 small cluster, Tangerang include 5
small cluster, Inner Jakarta include 8 small cluster,
Depok include 7 small cluster

No.GUL sites in small clusters


DEPOK7 79
DEPOK6 38
DEPOK5 138

DEPOK
DEPOK4 48
DEPOK3 49
DEPOK2 48
DEPOK1 49
INNER8 76
INNER7 72
INNER6 65

INNER
INNER5 48
INNER4 59
INNER3 58
INNER2 25
INNER1 34
TANGERANG5 54

TANGERANG
TANGERANG4 59
TANGERANG3 114
TANGERANG2 58
TANGERANG1 52
BEKASI6 32
BEKASI5 55

BEKASI
BEKASI4 51
BEKASI3 49
BEKASI2 51
BEKASI1 62
0 20 40 60 80 100 120 140 160
25
Thank you
Copyright©2015 Huawei Technologies Co., Ltd. All Rights Reserved.
The information in this document may contain predictive statements including, without limitation, statements regarding the future financial
and operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and
developments to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for
reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice.
50

0
100
150
200
250
Payload (GB)
1/2/2017

27
1/5/2017
1/8/2017
1/11/2017

0
1000000
2000000
3000000
4000000
5000000
6000000
7000000
1/14/2017
1/17/2017
1/20/2017
1/23/2017
1/26/2017
1/29/2017
2/1/2017
2/4/2017
2/7/2017

Central Java
2/10/2017

Central Java
2/13/2017
2/16/2017
2/19/2017
2/22/2017
2/25/2017
2/28/2017
3/3/2017
3/6/2017
3/9/2017

East Java
East Java
3/12/2017
showing increment

2016
3/15/2017
3/18/2017
3/21/2017
LTE Payload Trend still

3/24/2017
3/27/2017
3/30/2017
4/2/2017
4/5/2017
4/8/2017

Jabodetabek
4/11/2017
4/14/2017 South Sumatera
4/17/2017
4/20/2017
4/23/2017

LTE Payload per site


4/26/2017
4/29/2017
5/2/2017
5/5/2017
West Java

5/8/2017
5/11/2017
5/14/2017

South Sumatera
5/17/2017
5/20/2017
LTE Historical Weekly Payload Trend (GB)

5/23/2017
5/26/2017
5/29/2017
6/1/2017
6/4/2017
2017

Jabodetabek
Network Profile Overview

6/7/2017
6/10/2017

West Java
6/13/2017
6/16/2017
6/19/2017
6/22/2017
6/25/2017
6/28/2017
7/1/2017
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 2 4 6 8 10 12 14 16 18 20 22 24 26

20
40
60
80

0
120

100

Payload (GB)
1/2/2017
1/5/2017
1/8/2017
1/11/2017
500000

0
1000000
1500000
2000000
2500000
3000000
3500000
4000000
4500000

1/14/2017
1/17/2017
1/20/2017
1/23/2017
1/26/2017
1/29/2017
2/1/2017
2/4/2017
2/7/2017
2/10/2017
Central Java

Central Java

2/13/2017
2/16/2017
maintain

2/19/2017
2/22/2017
2/25/2017
2/28/2017
3/3/2017
3/6/2017
3/9/2017
East Java

East Java

3/12/2017
3/15/2017
2016

3/18/2017
3G Payload Trend still

3/21/2017
3/24/2017
3/27/2017
3/30/2017
4/2/2017
4/5/2017
4/8/2017
Jabodetabek

Jabodetabek

4/11/2017
4/14/2017
4/17/2017
4/20/2017
4/23/2017
3G Payload per site

4/26/2017
4/29/2017
5/2/2017
5/5/2017
5/8/2017
5/11/2017
South Sumatera

South Sumatera

5/14/2017
5/17/2017
5/20/2017
3G Historical Weekly Payload Trend (GB)

5/23/2017
5/26/2017
5/29/2017
6/1/2017
6/4/2017
2017

6/7/2017
West Java

West Java

6/10/2017
6/13/2017
6/16/2017
6/19/2017
6/22/2017
6/25/2017
6/28/2017
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 1 3 5 7 9 11 13 15 17 19 21 23 25

7/1/2017