Workshop_vf_partner Markets_smart Implementation_final.pdf
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Workshop_vf_partner Markets_smart Implementation_final.pdf as PDF for free.
More details
- Words: 7,736
- Pages: 92
Smart LTE Implementation Radio LTE optimization and LTE SON & Site Integration process workshop Milan , 26-27 May 2015
Agenda • Smart Single RAN configuration – LTE Carrier Aggregation – Active Antennas
• Smart architecture • Smart Radio Planning & initial settings – 3MHz LTE900 performance
• Smart TX planning • Site Acceptance support tools
Insert Confidentiality Level in slide footer
Smart Single RAN Configuration
3
Smart Single RAN Before
Today
Each access technology needed a dedicated HW
HW can be shared among access techs, with different SW UMTS
2G GSM
900/1800MHz
2G 3G 4G
3G 900/2100MHz
4G
4G 800/900/ 1800/2100/ 2600MHz
Single RAN
800/1800/2600MHz
Benefits •
No need to add new equipment, the best Radio technology can be enabled just via Software
•
Technology agnostic: Powerful and scalable in order to support all the Radio technologies
•
More energy efficient
•
Different access technologies can share:
green network
o The power of the same Radio Module in the same band o The baseband resources o Common transport C2 – Vodafone restricted
4
RF Sharing Configuration RF Sharing Lte+DCS 1800 MHz
GSM
• Today requirement (single band PA technology) is that the radio technologies have to work in frequency bands close to each other
LTE RF modules
RF modules GSM Baseband
RF modules LTE Baseband
• 4G and GSM can share Radio Modules @1800 MHz
*
*or 10 MHz
Single Technology PA
GL PA in ‘sandwich mode’
• Vendors has made available a set of combinations for GL @1800MHz, depending on the 4G bandwidth, the number of GSM TRX and the power to dedicate to each technology
C2 – Vodafone restricted
4-way RX Diversity Overview • 4 Rx antennas at the eNB (4-way RX diversity) • Compared to the currently applied 2way Rx diversity scheme, using 4 receive antennas will bring gain in coverage as well as the average cell throughput • 4-way Rx diversity improves the transmission quality in medium or bad air conditions. • Peak cell throughput is not affected
Key Requirements • Antenna system: • Dual RX antenna • HW: • 2 PA’s / sector (4-RX in total) • Active Antennas (Huawei & E///) • TX: • Phase Sync recommended in case of IRC uplink combination mode
Implementation •
To facilitate implementation, 2 RX branches implemented as combined 2.1 and 2.6 GHz; no additional antenna port required wtr to default implementation,
•
Additional Radio HW for the 2 additional branches, combiner and wideband TMA
C2 – Vodafone restricted
4-way RX Diversity Results from VF-PT LIVE test • From the mobility tests it can be seen that LTE PS Sessions can be continued/established at a longer distance (200m in straight line) from the base station when 4WRXD is activated. • 4WRXD provides higher UL Throughput than 2WRXD, especially for medium and poor radio conditions.
RSRP 2WRXD Thput 4WRXD Thput -113,5 dBm 409,2 kbps 476,6 kbps
PS Drop with 4WRXD PS Drop with 2WRXD
The extra 3dB UL gain expected from 4WRXD was verified.
HW Required AIR21 B3A B1P (L1800) RBS6601 + DUS41
CPRI - fiber
C2 – Vodafone restricted
4-way RX Diversity Results from VF-PT LIVE test 2WRXD RF Conditions @ -60dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
Mean
Min
Max
-63,37 22936,82
-84,1 0
RF Conditions @ -97dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-96,10 -110,2 11363,63 0
90%-ile
Mean
Min
-59 -61,8 24041,82 23743,12
4WRXD RF Conditions @ -60dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-65,25 23134,99
-83,4 0
-58,6 -59,6 23748,46 23686,18
-94,4 -94,8 14879,1 12892,13
RF Conditions @ -97dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-97,57 17188,27
-99,4 0
-95,4 -96,4 20631,75 18897,63
RF Conditions @ -115dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-115,76 1426,58
-123 0
-113,4 2454,67
Static Location -60dBm
Static Location -97dBm
Normal
Normal 100
Variable 2-way RX UL 4-way RX UL
100
80
Mean StDev N 23307 487,7 62 23508 271,0 62
80
Mean StDev N 11547 1522 62 17452 1581 62
80
20
Perce nt
40
60
40
20
0 22500
23000 23500 Throughput
24000
24500
Mean 1450 StDev 382,0 N 62
60
40
20
0 22000
-113,9 1875,24
Normal
Variable 2-way RX UL 4-way RX UL
60
90%-ile
Static Location -115dBm
100
Perce nt
Perce nt
Tests with 2WRXD could not be executed at -115dBm because session could not be established.
Max
0 8000
10000 12000 14000 16000 18000 20000 22000 Throughput
500
1000
1500 Throughput
2000
2500
From the static tests it was verified that 4WRXD provides more UL Throughput than 2WRXD, mainly for medium and poor radio conditions.
C2 – Vodafone restricted
Co-Tx “Single RAN” technology enables to share a single transport interface among two or more technologies (GSM, 3G e 4G)
Benefits •
Unified O&M systems and transport Operability
•
Reduced number of interfaces
•
Cost – implementation with a shared fiber
•
Common IP: Site appears as one IP host on transport layer
•
Flexible IP addressing, QoS and IPsec concepts
RF modules
RF modules
GSM
UMTS
LTE
GSM
UMTS
Abis
Iub
S1
Abis
Iub/S1
C2 – Vodafone restricted
LTE
Typical LTE configurations: Nokia /1 • LTE800 3 TX
C2 – Vodafone restricted
6 TX
Typical LTE configurations: Nokia /2 • LTE1800 with RF Sharing with RFM
C2 – Vodafone restricted
Typical LTE configurations: Nokia /2 • LTE1800 with RF Sharing with RRH
C2 – Vodafone restricted
Typical LTE configurations: Nokia /3 • LTE2600 with RFM - 4RX
Cell 53 TxRx
Cell 52 TxRx
Cell 53 TxRx
Cell 51 TxRx
Cell 52 TxRx
Cell 51 TxRx
FRHC 1.1.1 1 2 Cell 53 Rx
Cell 52 Rx Cell 53 Rx
Cell 51 Rx Cell 52 Rx
Cell 51 Rx
FRHC 1.2.1 1 2 1 2 3
FSMF + 1xFBBC
3
6 Gbps Obsai 3 Gbps Obsai
Nokia eNodeB Standard Configurations C2 – Vodafone restricted
Typical LTE configurations: Nokia baseband /3 FSME • Same capacity with a single FSMF module with no FBBC extension capability • Optical interface capacity up to 3Gbps and up to 5 RF interfaces with no expansion possibility • No dual band support for 3 sectorial sites. • Overall capacity: 3 cells x 20 Mhz
Evolution of FSMF • Nokia’s high capacity Flexi Multiradio System Module (FSMF) provides multiradio capability and allows capacity to be increased by adding more modules • Optical interface capacity provides up to 6 Gbps - more number of cells that can be supported by each radio module interface • Provides reduction in power consumption compared to previous modules and lowers OPEX • Multiradio and multiband configurations are achievable by the addition of from four to six RF interfaces and through the FSMF’s RF Module chaining capability • The evolution of the FSMF platform to support concurrent mode operation of at least any two technologies is considered critically important. Nokia supports with SW upgrade capability to achieve this • Is used also for WCDMA Active users (RRC connected with at least one DRB establised) case 2x2 DL MIMO
FSFM (w/o CA)
cell
FSMF + FBBA/C (with CA)
eNB
cell
eNB
15MHz 10MHz 15MHz 10MHz 15MHz 10MHz 15MHz 10MHZ 720 600 2160 1800 720 600 4320 3600 14 C2 – Vodafone restricted
Typical LTE configurations: E/// LTE HW Configurations L800
L800
L800
A
B
C
RRUS11 or 12 Dual TX RRH MIMO ready
CPRI - fiber
L800 or L1800 or L2600
LTE Baseband Board Guidelines
2 Radio Units (RUS01 or 02) per Sector to enable MIMO
DUS41 L2600 L2600 L2600 L2600 L2600 L2600
ABC
L1800 or L2600
RBS6601 + DUS
A B C
AIR21 B3A B1P Active 1800MHz Passive 2100MHz MIMO & 4WRXD enabled
CPRI - fiber
C2 – Vodafone restricted
RBS6601 + DUS41
L1800
RBS6201
Typical LTE configurations: Huawei/1 • LTE800 800 MHz
L site
SRN1
BBU GL
800 MHz
FAN LBBPd1
UMPT
UPE U
S1/X2 (IP)
Referring BB board is LBBPd1 • LBBPd1 is capable to handle 3 2T2R LTE cells • Configuration for RRU is identical
BBU LO
16 C2 – Vodafone restricted
800 MHz
Typical LTE configurations: Huawei/2 • LTE1800 with RF Sharing
GL site
BBU GL
SRN1
FAN
GTMU LBBPD2
UMPT
Referring BB board is LBBPd2 • LBBPd2 is capable to handle 3 2T4R LTE cells • Configuration for RRU is identical
A-bis UPE U
S1/X2 (IP) 1800
1800
1800
MHz
MHz
MHz
BBU GL
C2 – Vodafone restricted
Typical LTE configurations: Huawei/3 • LTE1800 with inter BBU RF Sharing GUL site
BBU GU
SRN0
UCIU Wbbp
FAN
GTMU Wbbp Wbbp
UPE U
WMPT/ UMPT
A-bis Iu-b (IP)
BBU LO
SRN1
1800
1800
1800
MHz
MHz
MHz
Lbbp
FAN Lbbpd2
UMPT
UPE U
S1/X2 (IP)
BBU GL
• LBBPd2 is capable to handle 3 2T4R LTE cells • Configuration for RRU is identical
C2 – Vodafone restricted
Typical LTE configurations: Huawei /4 • LTE2600 with 4RX
L site
SRN1
BBU GL
RRU
FAN LBBPd2
UMPT
UPE U
S1/X2 (IP)
RRU Referring BB board is LBBPd2 • LBBPd2 is capable to handle 3 2T4R LTE cells • RRU only
RRU
C2 – Vodafone restricted
Typical LTE configurations: 3G/4G CoTX
800 MHz
GUL site
2100 MHz
800 MHz
2100 MHz
800 MHz
2100 MHz
900 MHz
1800
BBU GU
SRN0
BBU U
Wbbp
FAN Wbbp Wbbpd2
UMPT
UPE U
Iu-b (IP) + S1/X1 (IP)
SRN1
BBU LO
900 MHz
1800
MHz
900 MHz
1800
MHz
UCIU Lbbp
FAN
GTMU Lbbp
UMPT
UPE U
BBU GL
A-bis (TDM)
20 C2 – Vodafone restricted
MHz
Typical LTE configurations: 2G/3G CoTX
GUL site
BBU GU
SRN0
Wbbp
FAN
GTMU Wbbp Wbbpd2
UPE U
WMPT/ UMPT
A-bis Iu-b (IP)
BBU LO
SRN1
Lbbp
FAN Lbbpd Lbbpd2
UMPT
UPE U
S1/X2 (IP)
BBU GL
• LBBPd2 is capable to handle 3 2T4R LTE cells • Configuration for RRU is identical
C2 – Vodafone restricted
Target solution: 2 antennas /sector
Starting solution One antenna / sector
LTE Antenna Evolution 900/1800/2100 X X X X
X X X X
X X X X
Swap to QUAD BAND
X X X X
X X X X
X X X X
Model 1 : 700-800/900/2x18002600 (filtered) Model 2 :2x700-900/2x1800-2600 (side by side)
X X X X
legacy antenna (6 connectors)
900/1800 X X X X
X X X X
900/2100 X X X X
X X X X
900/1800/2100 800/1800/2100 Swap
X X X X
X X X X
X X X X
700/800/2x 2600 700/900/2x2600 X X X X
X X X X
X X X X
X X X X
MIMO 4x4 ready Independent tilt for LBs
•
The goal is to have at least two antennas per sector for new feature requirements ( es. 4-way diversity , MIMO 4x4, etc…)
•
Independent tilt for each system/frequency is crucial for the optimization activities especially for 800 / 900 MHz C2 – Vodafone restricted
First LTE-A implementation: LTE Carrier Aggregation
23
Carrier Aggregation – Executive Summary •
Carrier Aggregation is an important step in LTE-Advanced and enables multiple LTE carriers to be used together to provide very high data rates for the customers
•
Launches and Rollout expansions plans are already ongoing in all the European VF countries where more than one LTE band is available, moving from the most important cities to the medium cities and touristic places.
•
Roadmap for Carrier Aggregation capability increase is available, supporting an increasing numbers of carriers, aggregation across FDD/TDD and wider maximum aggregated bandwidth; some design challenge on terminal (and partially network) requires a phased deployment approach.
C2 – Vodafone restricted
Carrier Aggregation – Capabilities & roadmap Terminal Categories – Rel-10&11
Capabilities
Roadmap for CA evolution
LTE-A
Up to
Up to
20 MHz
20 MHz
Up to 150 Mbps
Up to 150 Mbps
1
Now
2H15*
Future?
3 bands (e.g. 800 MHz + 1800 MHz + 2600 MHz) aggregation: up to 450Mbps
Extended LTE bandwidth
2
Aggregated Data Pipe (Up to 300 Mbps)
Increase LTE performance (e.g. 1800MHz) while voice migrates to 3G/4G (VoLTE)
w/ MIMO 2x2
40 MHz
LTE-A terminal
3 2H15
2016+*
(*) not for the smartphone C2 – Vodafone restricted
FDD + TDD carrier aggregation – Under standardisation First combination FDD1800+TDD2600
LTE Carrier Aggregation allows multiple LTE carriers to be bonded together to improve the customer experience Carrier Aggregation increases the bandwidth available to our customers
20MHz Carrier 10MHz Carrier
Peak speed 150Mbps Peak speed 75Mbps
•
Improved user experience at high and low loads
•
Better consistency at 3Mbps and higher
•
Better HD video with less stalling
•
“Bragging Rights” and competitiveness in Speed Tests
+ Peak Speed 225Mbps with new device supporting Carrier Aggregation
In the next couple of years: • Downlink and 2 bands only • Up to 40MHz FDD Aggregation
C2 – Vodafone restricted
Benefits:
In Urban Areas if we start with 800 deployments on the 900 grid we should add 1800 or 2600 to these sites and carrier aggregate LTE1800/2600 added to 100% of LTE800 sites 1.8 or 2.6GHz 800MHz
+
15/20MHz
15/20MHz
+
+
10MHz
+
10MHz
Deployed 1st
No LTE
LTE 2x30MHz Carrier Aggregation
Maximum Peak Speed Possible 225Mbps
With CA
150Mbps
On 2600 only
75Mbps
On 800 only
Example: Vodafone DE and UK C2 – Vodafone restricted
No LTE
LTE 2x30MHz Carrier Aggregation
No LTE
If we start with 1800 (or 2600) deployments on the 2100 grid we should add 800 to a subset of these sites and carrier aggregate LTE800 added to ~60-80% of LTE1800 sites 1.8 or 2.6GHz 800MHz
+
20MHz
20MHz
20MHz
+
20MHz
20MHz
+
+
10MHz
10MHz
Deployed 1st
LTE 2x20MHz
LTE 2x30MHz Carrier Aggregation
Maximum Peak Speed Possible 225Mbps
With CA
150Mbps
On 2600 only
75Mbps
On 800 only
Example: Vodafone IT and ES C2 – Vodafone restricted
LTE 2x20MHz
LTE 2x30MHz Carrier Aggregation
LTE 2x20MHz
A coverage analysis in Dusseldorf shows that Carrier Aggregation enhances the User Experience across 80% of the indoor area Relative Indoor Coverage 1) Deploy LTE800 on 50 (of 71) Sites 800 Only 2600 Only (50 sites) 800+2600 with Carrier Aggregation
Single User Experience 100 Mbps
75 Mbps
Benefits from CA over 80% of area
2) Upgrade these 50 Sites with LTE2600
50 Mbps
Deep indoors there is no benefit from 2600 - coverage from 800 only
25 Mbps
0 Mbps 0%
20%
40%
60%
% Indoor Area Covered
Single User Speed
<1Mbps
20Mbps
>150Mbps C2 – Vodafone restricted
80%
100%
And benefits of Carrier Aggregation are seen over nearly all the Outdoor area 1) Deploy LTE800 on 50 (of 71) Sites
Relative Outdoor Coverage 800 Only 2600 Only (50 sites) 800+2600 with Carrier Aggregation
Single User Experience 100 Mbps
75 Mbps
2) Upgrade these 50 Sites with LTE2600
50 Mbps
25 Mbps
Benefits from CA over 99% of area 0 Mbps 0%
20%
40%
60%
% Outdoor Area Covered Single User Speed
<1Mbps
C2 – Vodafone restricted
20Mbps
>150Mbps
80%
100%
Carrier Aggregation brings more Urban capacity and enables user experience to be maintained at much higher loads 800+2600 Carrier Aggregation
1800+800 Carrier Aggregation
Average LTE Experience Indoor (Mbps) LTE800
LTE800+2600 CA
LTE1800
LTE1800+800 CA
LTE800
LTE800+2600 CA
LTE1800
LTE1800+800 CA
% Sessions >10Mbps Indoor
Based on VTNA analysis of Dusseldorf
Low Traffic: 33% LTE penetration, LTE Smartphones @1.25GB/month
C2 – Vodafone restricted
High Traffic: 100% LTE penetrations, LTE Smartphones @2.5GB/month
LTE Carrier Aggregation /Nokia Configuration Examples Dual Band 1800+800
32 C2 – Vodafone restricted
LTE Carrier Aggregation /Nokia Configuration Examples Dual Band 2600 + 800
33 C2 – Vodafone restricted
LTE Carrier Aggregation /Nokia Configuration Examples Dual Band 1800+2600 - RF Sharing – 4 Way RX (RL70)
Cell 53 TxRx
Cell 52 TxRx
Cell 53 TxRx
FRHC 1.1.1
Cell 33 TxRx
Cell 51 TxRx
Cell 52 TxRx
Cell 31 TxRx
Cell 32 TxRx
FXEB 1.2.1.1
Cell 51 TxRx
1 2 Cell 32 TxRx
Cell 33 TxRx
Cell 31 TxRx
1 2 Cell 53 Rx
FRHC 1.2.1
Cell 52 Rx Cell 53 Rx
FXEB 1.2.2.1
Cell 51 Rx Cell 52 Rx
Cell 51 Rx
1 2
FSMF + 2xFBBC
1 2 6 1 2 3 3
1 2
6 Gbps Obsai 3 Gbps Obsai
TO ESMx 2G 34 C2 – Vodafone restricted
LTE Carrier Aggregation Ericsson Configuration Examples LTE CA 3 Bands – RRH
LTE CA 2 Bands – RRH L800
L800
L800
L1800
A
B
C
D
L1800 L1800
E
F
L800
L800
L800
A
B
C
D
E
F
DUS41 XMU03 RBS6601 + DUS41
L1800
L1800 L1800
G L2600
H L2600
I L2600
LTE CA 2 Bands – Macro+RRH L800
L800
GH I
DUS41 L2600 L2600 L2600 L2600 L2600 L2600
A B L800
C
RBS6201
SW & Features Requirements • L14A SW Release • Features: 6 Cell Support (FAJ 121 1821) Cascadable Radio Units (FAJ 121 1820) (only required when using macro eNodeB) Carrier Aggregation (FAJ 121 3046) Dynamic SCell Selection for CA (FAJ 121 3063) • HWAC’s should be updated accordingly to the desired capacity
35 C2 – Vodafone restricted
Typical LTE configurations: Huawei CA LTE CA sites are identical to other LTE sites, provided that RF modules and BB boards constraints are satisfied. RF modules to be selected according to site needs. LTE-CA supported by the combinations of baseband processing units in the eNodeB: 1 LBBPc + 1 LBBPd1 1 LBBPc + 1 LBBPd2 1 LBBPd1 + 1 LBBPd2 2 LBBPd1 boards 2 LBBPd2 boards
A combination of 2 LBBPc DOES NOT SUPPORT LTE-CA
36 C2 – Vodafone restricted
Typical LTE configurations: Huawei CA • GSM1800+L1800+L800 CA (example)
800 MHz
800 MHz
GL site
SRN1
BBU GL
800 MHz
LBBPD1
FAN
GTMU LBBPD2
UMPT
A-bis UPE U
S1/X2 (IP) 1800
1800
1800
MHz
MHz
MHz
Referring BB board is LBBPd2 for L1800 and LBBPd1 for L800 • Configuration for RRU is identical
BBU GL
37 C2 – Vodafone restricted
Typical LTE configurations: Huawei CA
BBU GL
• L800+GSM1800+L1800+L2600 CA (example) GL site SRN1
LBBPD1
FAN LBBPD2
UMPT
800 MHz
800 MHz
A-bis
GTMU LBBPD2
800 MHz
UPE U
S1/X2 (IP)
Referring BB board is LBBPd2 for L1800/L2600 and LBBPd1 for L800 • Configuration for RRU is identical
2600
1800
2600
1800
2600
1800
MHz
MHz
MHz
MHz
MHz
MHz
BBU GL
38 C2 – Vodafone restricted
Carrier aggregation – Live results LTE-A
2x 2.6 Ghz
1.8 Ghz
15 MHz
15 MHz
Peak throughput Aggregated Data Pipe w/ MIMO 2x2
30
LTE-A terminal
MHz
C2 – Vodafone restricted
Cell border
Mid range
Site proximity
Active Antennas
40
General AA Executive Summary For each site, the possibility to adjust antenna tilt independently for each system/frequency it is fundamental for the optimization activity In order to be proactive, it is suggest to install antenna 2600MHz capable also in site where 2600MHz is not planned in a short period. The same provision should be implemented for 700MHz . For each site, the goal is to have at least two antennas per sector in order to have the flexibility to adjust the antenna system to the new feature requirements ( es. 4-way diversity , MIMO 4x4, etc…) For sites with single antenna /sector, today multiband antennas with 6 pair connectors (2 low band pair + 4 high band pair connectors) are available only with 2.6m height, 2m version in roadmap for 2015, lower /shorter m versions is under discussion. Put 700 and 800 in separate radomes or separate radiators (for example side by side antennas). Using separate radiators, ie 2 column wide antenna or two antennas, gives acceptable performance but is not allowed on many sites due to contract with site owners For sites with FDD&TDD antenna solution must ensure at least 54 dB (see Annex 2: TDD & FDD interference analysis) of isolation between FDD and TDD
C3 Vodafone Confidential
General AA Guideline Target AA • • • •
Active Antennas are an agreed part of VF strategy with aggressive plans in our guidance All new sites, unless not practically viable All 3G/LTE site upgrades when antenna change is needed, unless not practically viable. For future spectrum readiness, where viable 2 antenna per sector configuration shall be preferred with at least 1 AA
Practical limitations • when unfeasible for camouflage/environmental restrictions • where a complete swap of pole is needed on existing sites - unless necessary for passive antenna also or other reasons e.g. H&S, site infra modernization. Pole reinforcement is acceptable.
Special case considerations •
Sites restricted to single antenna per sector (e.g. passive sharing scenario) and LTE 800: Current AA models do not support separate tilt between 800 and 900 MHz in the passive band; this limitation can be acceptable where the use of AA is justified by other more predominant drivers. Precisely, in this site configuration, AA is recommended when : A) HW Site simplification in 4 or 5 band sites with too many RRUs e.g. AA in LTE 2600 B) Performance on LTE 1800 or 3G in strategic areas C) site energy reduction e.g. macro site with long cables D) separate tilt 800 and 900 is notcritical in the area.
C3 Vodafone Confidential
Active Antenna Concept Overview An active antenna (AA) integrates the radio module(s) and the antenna array(s) in the same box
Key Advantages Power Savings (reduced feeder loss) Cleaner sites (No cables, RRUs, DTMAs) Capacity/Coverage gain (suitable for high capacity scenarios)
Drawback Not all AA models support all bands Weight may be an issue for site installation 43 C2 – Vodafone restricted
Huawei AAs Family AAU3911
AAU3910
AAU3902
Configurati on
2A+2P
2A+1P
2A+2P
Power specs
2x60W 2T4R
2x60W 2T4R
2x40W 4T4R
Supported bands
GL 1800 MHz U 2100 MHz L 2600 MHz GUL 690-960MHz
GL 1800 MHz U 2100 MHz L 2600MHz
GL 1800 MHz U 2100 MHz LTE 2600 MHz GUL 790-960MHz
Supported RATs
GUL
GUL
GUL
Size [mm]
2020x360x290
1450x320x230
2000x350x260
Weight [Kg]
49 (1 active module) 65 (2 active modules)
39.5 (1 active module) 53.5 (2 active modules)
53 (1 active module) 62 (2 active modules)
Availability
Tests ongoing
To be tested
Rolled out
44 C2 – Vodafone restricted
No big differences on wind-load and pole dimensioning
Huawei Example: adding LTE800/2600 to 900/1800/2100 Site Option 1: Swap to new Passive Antenna 900/1800/2100 2 Antenna Site Passive: 1800
X X X X
Passive: 800/1800/ 2600
Passive: 900/2100
X X X X
X X X X
Add LTE800 /2600
X X X X
X X X X
X X X X
Passive: 900/2100
Wind Load
2650 N
Weig ht
64Kg
Wind Load
2660 Based on local N market rules.
Weig ht
Antennas + 3 Pairs of Cables
Antennas + 5 Pairs of Cables
Option 2: Swap to Active Antenna X X X X
Active: 1800/2100 Passive: 800/2600 RF Cables Fibre + DC
C2 – Vodafone restricted
X X X X
X X X X
X X X X
Passive: 900
98Kg
Wind load similar Weight not critical in pole dimensioning
AAs Key Features AAU3902
VERTICAL MULTIPLE SECTORS UL/DL capacity improvement Suitable for high traffic scenarios
46 C2 – Vodafone restricted
AAU3902
VERTICAL 4 WAY DIVERSITY UL throughput improvement Coverage gain
AAU3911/AAU3910
HORIZONTAL 4 WAY DIVERSITY
UL throughput improvement Coverage gain
Ericsson AIRs Family DRIVERS Model
Description
NEW sites (Non Urban)
RAN Refresh / LTE sites
AIR11 B20A / B8P
AA in 800 MHz with independent passive antenna for 900 MHz
G900/U900 + L800
L800 upgrades in existing low band only sites
AIR21 B1A / B3P
Dual AA in 2100 MHz with 2T/4R capabilities and independent passive antenna for 1800 MHz
Sites needing U2100
Sites needing Refresh in U2100
AIR21 B3A / B1P
Dual AA in 1800 MHz with 2T/4R capabilities and independent passive antenna for 2100 MHz
Sites where AIR for U2100 not possible requiring LTE1800 with no DCS and RRU installation constrains
Sites with U2100 already Refreshed requiring LTE1800 with no DCS and RRU installation constrains
Smart Architecture
Architecture Evolution • An important pre-requisite for self-organizing networks and efficient configuration management is a simpler and flat architecture – The complete E2E chain (including Access Network & MW) to be as much future proof as possible – MTU expansion mandatory especially when introducing IPSec – Distributed SecGw model is crucial for – Improve Latency – Decrease the number of hops – Security guaranteed by the introduction of IPSec
Insert Confidentiality Level in slide footer C2 – Vodafone restricted
49
June 9, 2015
3GPP Architecture Evolution
50 C2 – Vodafone restricted
E2E connectivity
51 C2 – Vodafone restricted
4G Vodafone Architecture
eNB MME
IP Backbone
Access TX SeGW
eNB
SAE-GW
~ ToP Master
O&M
eNB Primary Reference Clock
C2 – Vodafone restricted
Path differentiation MME
SeGW 2
IP Backbone
Access TX SeGW 1
eNB
SAE-GW
Timing over Packet (IEEE 1588)
~ ToP Master
Control Plane (CP) User Plane (UP) Operation and Maintenance (O&M) Syncronization
C2 – Vodafone restricted
O&M
Primary Reference Clock
Security Gateway (SecGW) • LTE security requires a different system protection as mobile backhaul traffic becomes more vulnerable to hacker attacks • IPsec provides a comprehensive set of security features like – data origin authentication – Encryption – integrity protection
Non IP traffic
UE
LTE eNB
IP traffic
Un-Trust network IPsec tunnel SecGw
Core Trust network
CA LTE – IPsec Tunnel Mode encapsulates and protects the entire source IP packet
54 C2 – Vodafone restricted
Internet
CA LTE: for device eNB and SecGW site • VF architecture include front-end (FE) servers and a back-end (BE) server • The FE is used for the delivery of certificates: – the clients are connected using the CMP or SCEP protocol
• The BE is the engine of CA LTE platform: – the logical application to create the certificate and each certificate are store into the Oracle DB – The BE is the core of CA, it signs all the certificate requests from eNodeB and Security Gateway.
• Each client (eNB/SecGW) contact the FE of CA LTE through the VIP address
55 C2 – Vodafone restricted
SCTP Multi-homing concept
SeGW1
SeGW2
• It provides transparent fail-over between redundant network paths • a ‘keep alive’ message is sent on the primary and secondary paths to verify e2e connection • as soon as the primary path fails (because of any of the nodes or links) the SCTP association automatically switch to the secondary path without any impact on the existing connections
• Requirements • Both endpoints of the connection can support more than one IP address • The two paths have to be physically separated
C2 – Vodafone restricted
Architecture and Tunnel Mapping
CP
CP
UP
UP
Tunnel 1
O&M O&M2
O&M2
Tunnel 2
MME MME
CP2
CP2 eNB
O&M
Router
SeGW1 CP UP
• Target solution for Vodafone • SCTP multihoming support from day 1 • Support for two O&M:
O&M O&M2 CP2 SeGW2
• First O&M in tunnel to provide security on KPI and commands • Second O&M out of tunnel to provide connectivity (SSH, HTTPS) if the tunnel breaks down • O&M2 is activated only if tunnel 1 is down
C2 – Vodafone restricted
CS Fallback CSFB (Circuit Switched Fall Back) • It allows UE camped on the 4G network for PS services to attempt/receive a CS call on CS overlapping GSM/UMTS networks • Three methods: PS Handhover, CCO with/without NACC (specific for GSM case), Redirection
58 C2 – Vodafone restricted
Smart Radio Planning
59
Smart Radio Planning SON Approach
Main Challenges – Increasing OPEX for the skilled staff for local commissioning and configuration activities – Increasing CAPEX due to overdimensioning – High operational impact of periodic replanning – Cell Specific Settings on 4G: PCI, RSI, PRACH planning i.e. PCI reuse to be too high and its impact on the RS SINR – Labor intensive neighbour relations handling activity (intra/inter frequency, inter-RAT)
– Minimum or zero manual configuration – Plug & Play: Functionality that enables to simplify the eNB integration – Automatic cell specific settings: PCI conflict resolution, PRACH optimization – Automatic neighbour relations and the setup of X2 interfaces thus reduced HO failure caused by missing neighbour relations – Higher reliability of SW installation – Real-time network auto-tuning – Quick site configuration i.e. 10-click via NCM
Legacy process Auto-configuration process C2 – Vodafone restricted
Site design Enhanced Site design
HW config. 60
Data configuration
HW order
June 9, 2015
SON – At a Glance
SON (Self Organizing NW) is an automation technology designed to
planning, configuration, management, optimization and healing of mobile radio make the
C2 – Vodafone restricted
PCI Planning manual vs automatic planning • Analogous to scrambling code planning in UMTS • In NSN areas, PCI planning can be done automatically with NetAct Optimizer: – Re-use of the same PCI in the same area is reduced as much as possible – When a new cell/site is added to an existing cluster, PCI planning is re-made in order to respect PCI planning rules, optimise PCI re-use and maximize network performances
• In Huawei areas, automatic PCI planning is not available: – There are features available to detect PCI collisions to optimize them looking for a new PCI. It works over eNodeB SW, not needed extra HW or SONMaster
LOFD-002007 PCI Collision Detection & Self-Optimization – To perform PCI Planning activities an external tool would be needed
• In Ericsson areas: – PCI Conflict Management supported (OSS) – PCI Conflict detection and fix – under test – PCI planning with external tools - Atoll
Very high operational impact of periodic manual PCI replanning C2 – Vodafone restricted
1
PCI Planning – Real Life Example from Rome manual vs automatic planning • After some rounds of manual planning, the PCI re-use in Rome was too high • A lot of PCIs were used 3/4 times in the same city with ~600 cells On Air • Very difficult to find areas with RS SINR higher than 22 dB. After the rollout of the New PCI Plan, re-use was significantly
• Higher RS SINR could be immediately measured
Critical to ensure good automatic PCI planning ! C2 – Vodafone restricted
Re-use 1
Re-use 2
Re-use 3
Re-use 4
Old PCI plan
34
128
84
4
New PCI plan
173
198
-
-
LTE Design Standard on Uplink Physical Random Access Access Channel RSI planning • Principle & gain •
PRACH preambles created from Root sequences to get Access to the eNode B by the UE
•
838 RootSequences are available to generate the PRACH preambles by combined cyclic shifting =
•
If same root sequences used in neighbouring cells overlap, the transmitted preamble may be detected in multiple cells
•
The false RACH detection alarm probability may be increased
•
RootSequenceIndex (RSI) points to the first root sequence to be used when generating the set of 64 preamble sequences
•
Number of root sequences allocated to a cell depends on the cyclic shift Ncs linked to the cell range (table)
•
RSI planning prevents blocking of UE Random Access and drops during Handover
C2 – Vodafone restricted
LTE Design Standard on Uplink Physical Random Access Channel Root Sequence Index (RSI) planning Software requirements: Tools based allocation with Atoll and AFP At least Atoll version 3.2.1 is required: PRACH RSI allocation capabilities by default Cell range based allocation will be available with Atoll version 3.3.0 with an additional Makro module With Nokia RSI automatic planning available in NetAct Optimiser
Status in Vodafone: The default allocation of 10 Root sequences per cell is done across the VF-OPCOs Nokia OpCos: • NetAct Optimiser used. Huawei/Ericsson OpCo: • Atoll typically used. The false RACH alarm probability went from around 90% before to maximum 5% after implementing the RSI planning in the VF-DE Ericsson Region 65 C2 – Vodafone restricted
PCI/RSI Planning – Real Life Example manual vs automatic planning With PCI/RSI Planning
Without PCI/RSI planning
Handover Failure Rate increases exponentially
Drop call rate increases
66 C2 – Vodafone restricted
Plug & Play approach
DHCP MME
IP @ temp
IP backbone
Access Tunnel TunnelTX New eNB
Certificate
SAE-GW SeGW 1-2
eNB temporary IP@ from DHCP Certificate to setup the IPSec tunnel to SeGW eNB complete configuration (IP@ etc) from O&M in tunnel Control Plane (CP) User Plane (UP) Operation and Maintenance (O&M)
C2 – Vodafone restricted
OSS CA Server & Repository
Automatic Neighbour Relation (ANR)
/1
What: Automatic definition of intra-frequency and inter-frequency neighbouring cells. No more need for neighbouring planning and definition. • Inter-RAT definition still manual due to lack of terminal support
How it works: 1. Cell-A sends measurements request to UE 2. UE reports strongest PCI=5 (Cell-B) to Cell-A 3. Cell-A finds new PCI=5, so it indicates UE to report Cell-B’s CGI 4.UE reads BCH to measure CGI, TA, PLMN ID, etc. 5.UE reports CGI=19 of Cell-B to Cell-A 6.Cell-A add Cell-B to it’s NRT 7.Cell-A looks up IP address of Cell-B and establishes X2 link
Benefits: - Save cost of neighbor cell planning during initial deployment and network expansion - Automated X2 link establishment with neighbor cell - Reduce HO failure caused by missing neighbor relation (better user experience). C2 – Vodafone restricted
Specialized Tools An efficient configuration management process requires easy to use, flexible and process oriented specialized tools in order to have well designed and stable standard low level configurations •
NCM: Wizard style low level data configuration preparation tool.
10-Click site configuration
•
Nokia Optimizer Tool: Locating the critical “polluter cells” and check design parameters
•
Sito: Configuration adapter to SAP HW order
C2 – Vodafone restricted
Automatic Overshooting Discovery Problem definition: • Unoptimised tilt/transmitted power on some sites leading to excessive interference generation on adjacent area • Very time-consuming in-field verification (drive tests) • No immediate evidence from counters due to limited traffic Idea: • Reuse automatically generate neighbour relation and optain automatic picture of “neighbour distance”. • Locate the critical “polluter” cells and check design parameters. Solution: • Based on NSN OSS Optimiser tool • Periodical usage to find interference and revise tilt.
C2 – Vodafone restricted
Automatic Overshooting Discovery
Sample Report from Milan
C2 – Vodafone restricted
SON – At a Glance
SON (Self Organizing NW) is an automation technology designed to
planning, configuration, management, optimization and healing of mobile radio make the
SON_Cisco C2 – Vodafone restricted
Nokia iSON
SON Nokia CISCO
Huawei SON
3MHz LTE 900 MBB solution for non 3G area
Summary • Opportunity – – – – – – –
Solution for mobile broadband demand – performance comparable to UMTS 900, better latency Interim competitive advantage Extremely Fast implementation in 2G modernized area Fully compliant with SRAN concept (reuse of 2G RRH) Simple migration to LTE 800 No lost investments – all expenses fully reusable for LTE 800 Solution for 2G data offload
• Limitations – 2G capacity, 2G quality (GSM will operate in limited spectrum) – Spectrum use close to country borders is limited by international agreements about preferential channels for GSM – In high traffic areas (plus buffer zones) the whole 900 MHz spectrum is needed long term for GSM 900
• Short term solution – 3MHz bandwidth offers 4 x smaller bitrates and significantly lower capacity compare to 10 MHz bandwidth
74 C2 – Vodafone restricted
Site configuration Initial Modernized GSM 900 GSM 900
GSM 900 + LTE 900 (3)
GSM 900
RET
RRH 900
LTE 900
Final GSM 900 + LTE 800 (5-10) LTE 1800 LTE 800 (capacity)
GSM 900
RET
RET
RET
RET
RRH 900 RRH 800 RRH 1800
RRH 900
NEW Single RAN BBU
Single LTE BB RAN BBU
Single RAN BBU
According to LTE contract, licenses shall be transferable. No dedicated LTE 900 expenses! All HW and licenses can be reused for LTE 800 – no lost investments when migrated to LTE 800 75 C2 – Vodafone restricted
Terminal support • All terminals support 3MHz bandwidth • About 80% of current LTE terminals support LTE 900, almost all new terminals come with LTE 900 support • Good public source of information about terminal support is on: – http://www.gsmarena.com/results.php3?s4Gs=LTE900
System support RAN vendor Huawei • SW Support from release SRAN 8 (GBSS15 + eRAN6) • BTS/eNodeB HW : – RRUs: 3928, 3929 and newer – LBBPd1 and newer
• MSR mode (MSR = GSM+LTE in the same RRU) – There is no difference between performance of LTE 900 (3MHz) and GSM 900 + LTE 900
76 C2 – Vodafone restricted
Performance of LTE 3MHz • On 3MHz carrier theoretical maximum is app. 20 Mbps (similar to HSPA+, SC) • Practically achieved maximum 17,3 Mbps average speed around 8Mbps • Better latency than in 3G (3G < 100 ms, LTE < 50 ms) • In GSM 900 footprint we can achieve on the cell edge – App. 250 - 700 kbps for LTE 900 (3), which is comparable to performance of UMTS900 • Uplink achieved maximum 6,5 Mbps, average around 3Mbits • Better maximum number of users handling compared to UMTS
Performance of LTE 900 (3) is similar or better than performance of HSPA
Way forward LTE with 3 MHz bandwidth is not long term solution for MBB wide coverage For competitive MBB coverage the 10 MHz channel in spectrum bellow 1 GHz shall be used. Very fast LTE rollout wherever only EDGE coverage present. Solution for low traffic areas 77 C2 – Vodafone restricted
Smart Tx Planning
78
Smart TX Planning Main Challenges
Smart TX Planning Approach – IPSec to provide security services for traffic at the IP layer – MTU adaptation from the beginning in order to support Jumbo Frames (MTU > 1600) on the whole E2E chain to avoid dupACK, packet out of order and refragmentation – Implementation of shaping and optimization of configurations to solve issues related to buffer – Different QoS streams and EPS bearer concept – Optimized MW Configurations (operating band & bandwidth, spanning tree configuration, buffer requirements & shaping, etc.)
– Challenges on TX dimensioning and configurations due to higher peak rates (i.e. 100Mbps+) and lower latency of the LTE technology – “Low throughput” or “underperforming TCP traffic” caused by incorrect E2E dimensioning of the TX network – Packet drops due to limited buffer – Low performance due to packet segmentation with IPSec enabled – Other incorrect / unoptimized configurations
79
IPSec – MTU Size Adaptation • Stands for IP Security and defines a set of protocols • Currently described in RFCs 2401-2412, and 4301 • Provides security services for traffic at the IP layer • Uses Encapsulation Security Payload (EPS) which provides: Data origin authentication Connectionless integrity Confidentiality
RLC eNB
IP S-GW
User IP Payload
UDP
GTP-U
User IP Payload
Tunnel 1 SeGW
eNB IP in Tunnel
EPS
IP SeGW
UDP
GTP-U
User IP Payload
S-GW
Trailer
1500Byte
MTU Size Adaptation MTU Size to be larger than1600B
C2 – Vodafone restricted
IP User Packet Max Size GTP-U Header Max Size UDP Header Size IP Header IPSec Header Total
Size [byte] for X2-User Plane 1500 16 8 20 64 1608
Size [byte] for S1-User Plane 1500 12 8 20 64 1604
IPSec ON vs IPSec OFF Data performance
Bands usage
81 C2 – Vodafone restricted
Shaping The bucket shapes the flow at a fixed rate (SR) and no burst is
Without shaping 1G
0
1G
permitted also if the output line rate is bigger, e.g. 1 Gbit/s
L2/L3 switch
If the ingress flow fills the bucket, the new packets will be
buffer 1Gbps line rate
lost.
200Mbps line rate
With shaping
In general, the Average Ingress Rate needs to be less than the Shaper Rate, otherwise the Bucket filling and the packet loss
L2/L3 switch
200M
will be unavoidable. buffer 1Gbps line rate
200Mbps line rate
Packet loss vs Throughput
B = Bucket Size
SR = Shaper Rate
Througput
IR = Variable Ingress Rate
90 80 70 60 50 40 30 20 10 0 0,00%
82 C2 – Vodafone restricted
0,01%
0,05%
0,10% Packet loss
0,50%
1,00%
5,00%
QoS EPS Bearer Concept • 4G uses the concept of EPS bearer to route IP traffic from the PDN to the UE • An EPS bearer is an IP packet flow with a defined Quality of Service (QoS) between the PDN Gateway and the UE • Multiple bearers can be established for a user to provide different QoS streams (one EPS bearer for each QoS streams) • Each bearer has an associated: - ARP (Allocation and Retention Priority) to be used in admission - QCI (QoS Class Identifier) to identify: scheduling policy queue management policy rate shaping policy RLC configuration • GBR = Guaranteed Bit Rate • EPS bearer in GPRS is known as PDP context C2 – Vodafone restricted
QCI
Resource Type
1 2 3 4 5 6 7 8 9
GBR GBR GBR GBR Non-GBR Non-GBR Non-GBR Non-GBR Non-GBR
Priority 2 4 5 3 1 7 6 8 9
Pck Delay Budget [ms] 100 150 300 50 100 100 300 300 300
Pck Error Loss Rate 10-2 10-3 10-6 10-3 10-6 10-3 10-6 10-6 10-6
Example Voice Live video Buffered video Real-time gaming IMS signaling TCP-based services TCP-based services TCP-based services TCP-based services
QoS EPS Bearer Concept • Default bearer: established when UE attaches to the network - provides IP addresses and always-on IP connectivity to PDN - for all non-GBR flows that do not require QoS treatment -QCI assigned by MME based on subscription data received from HSS (typically 8 or 9) • Dedicated bearer: additional bearer established by network on UE request -for service data flows that require GBR QoS treatment • Packets filtering into bearers is performed by the UE in uplink and by the PDN gateway in downlink and it is based on TFTs (Traffic Flow Templates) - A TFT is a set of packet filters associated with an EPS bearer - A packet filter can be based on IP addresses, TCP ports, protocols, etc. - A default bearer may or may not be associated with a TFT (based on HSS data) but each dedicated bearer is always associated with a TFT
C2 – Vodafone restricted
QoS QCI – DSCP Mapping • DSCP (Differentiated Services Code point) is a field in IP header that is used for packet classification purposes in IP networks to provide QoS • Higher DSCP indicates higher-priority traffic on the Transport network • DSCP configuration in VF 4G: - Signaling: DSCP 46 - O&M: DSCP 0 - Data: definition of demo, gold, silver, bronze profile QCI
C2 – Vodafone restricted
Resource Type
Example
DSCP mapping
User Profile
1
GBR
Voice
46
All
2
GBR
Live video
46
All
3
GBR
Buffered video
46
All
4
GBR
Real-time gaming
46
All
5
Non-GBR
IMS signaling
34
All
6
Non-GBR
TCP-based services
34
Demo only
7
Non-GBR
TCP-based services
26
Gold only
8
Non-GBR
TCP-based services
18
Silver only
9
Non-GBR
TCP-based services
10
Bronze only
Temporary values
Site Acceptance Support Tools
86
Site acceptance phase
/1
• After the installation and integration, the new eNodeB should be accepted. • Dedicated acceptance procedure is defined to verify the site performance: – 4G: Latency test, DL/UL Throughput test , CSFB Call (MOC/MTC) , VoLTE Call (MOC/MTC) , Emergency Call , SMS – 3G: Latency test, DL/UL Throughput test, Voice Call (MOC/MTC) , Emergency Call, SMS – 2G: EDGE Activation , DL/UL Throughput test, Voice Call (MOC/MTC), Emergency Call, SMS – SRAN alarms : check about active alarms on both legacy and 4G systems – Antenna cable : coherence between HW/SW configuration and radiated Scrambling Code/Cell ID or PCI
2G validation procedure
3G validation procedure
• At the end of the acceptance test, three situations may occurs – eNodeB switched off: eNodeB shall be locked and an immediate troubleshooting session shall start – eNodeB switched on with troubleshooting: eNodeB shall be switched and troubleshooting session shall start – eNodeB switched on : ready for next steps of conditional acceptance
87 C2 – Vodafone restricted
4G validation procedure
Site acceptance phase
/2
• Support tools are used for site acceptance phase : – UDP Test : tests transport bottleneck issues – Pinger tools : reachability tests with core network – Radio Acceptance app : Following tests are executed using the app CSFB (both MO and MT calls) Emergency calls E2E Latency DL/UL Throughput SMS transmission and reception Swapped feeders Alarm verification and clearance on both 4G and legacy sistems Antenna system validation
88 C2 – Vodafone restricted
UDP Test • The UDP test consists in 30s UDP stream@100/150/200 or 250Mbps from a server (using iPerf) on the O&M network towards the eNodeB •
TRS PM counters on the eNodeB allow to compute Packet Loss Ratio
Core Network
Access TX
100 Mbps
Insert Confidentiality Level in slide footer C2 – Vodafone restricted
Packet Received Ratio
Results
<20%
TX Issues
>20% & < 90%
Should be investigated
> 90%
89OK
June 9, 2015
Pinger Tool • eNodeB_PINGER is a tool for the reporting of the S1 link availability and round trip time statistics
Actual query outcomes • eNodeB peer end availability
• The tool generates at least two reports per day and exposes the results directly on Vodka
– MME primary, secondary – PGWs – SecGW
• Round Trip Time statistics (AVG / MIN / MAX RTT) on the leg eNodeB - SecGW
Architecture 3. PING EXECUTION between the eNodeB and the different peer end 2. CENTRAL SERVER logins in NodeB, enable SSH if necessary
1. CENTRALSERVER retrieves the eNodeB anagraph from a DB
MMEs
PGWs
firewall
DB1
CPN (O&M)
IT LAN
eNodeB TX board SGWs
4. PING logs stored in CENTRALSERVER
C2 – Vodafone restricted
Central Server
DB2
Intranet
5. CENTRALSERVER parse the ping log and store the results in a DB2; results will be visible in a KPI Analyser tool
KPI Analyzer
Radio Acceptance App
/1
• Vodafone Radio Acceptance App performs all the tests required by the Validation procedure in a very fast and automated way such as : • CSFB (both MO and MT calls) • Emergency calls • E2E Latency • DL/UL Throughput • SMS transmission and reception • Swapped feeders • Alarm verification and clearance on both 4G and legacy systems • Antenna system validation • It represents an efficient, global, and not-ambiguous tool that speeds up the site integration procedure • It also guarantees that the validation procedure is carried out according to Vodafone guidelines (especially when the procedure is done by third parties)
91 C2 – Vodafone restricted
Radio Acceptance App
/2
• After the execution of the whole test list, the app automatically sends the reports to a specific database. The details will be available in the Backend Interface • All updates and configuration files are stored in a central server. This way, changes and/or updates can be delivered to all devices with just one click • Each OpCo can have different configuration files with different and specific settings
92 C2 – Vodafone restricted
Agenda • Smart Single RAN configuration – LTE Carrier Aggregation – Active Antennas
• Smart architecture • Smart Radio Planning & initial settings – 3MHz LTE900 performance
• Smart TX planning • Site Acceptance support tools
Insert Confidentiality Level in slide footer
Smart Single RAN Configuration
3
Smart Single RAN Before
Today
Each access technology needed a dedicated HW
HW can be shared among access techs, with different SW UMTS
2G GSM
900/1800MHz
2G 3G 4G
3G 900/2100MHz
4G
4G 800/900/ 1800/2100/ 2600MHz
Single RAN
800/1800/2600MHz
Benefits •
No need to add new equipment, the best Radio technology can be enabled just via Software
•
Technology agnostic: Powerful and scalable in order to support all the Radio technologies
•
More energy efficient
•
Different access technologies can share:
green network
o The power of the same Radio Module in the same band o The baseband resources o Common transport C2 – Vodafone restricted
4
RF Sharing Configuration RF Sharing Lte+DCS 1800 MHz
GSM
• Today requirement (single band PA technology) is that the radio technologies have to work in frequency bands close to each other
LTE RF modules
RF modules GSM Baseband
RF modules LTE Baseband
• 4G and GSM can share Radio Modules @1800 MHz
*
*or 10 MHz
Single Technology PA
GL PA in ‘sandwich mode’
• Vendors has made available a set of combinations for GL @1800MHz, depending on the 4G bandwidth, the number of GSM TRX and the power to dedicate to each technology
C2 – Vodafone restricted
4-way RX Diversity Overview • 4 Rx antennas at the eNB (4-way RX diversity) • Compared to the currently applied 2way Rx diversity scheme, using 4 receive antennas will bring gain in coverage as well as the average cell throughput • 4-way Rx diversity improves the transmission quality in medium or bad air conditions. • Peak cell throughput is not affected
Key Requirements • Antenna system: • Dual RX antenna • HW: • 2 PA’s / sector (4-RX in total) • Active Antennas (Huawei & E///) • TX: • Phase Sync recommended in case of IRC uplink combination mode
Implementation •
To facilitate implementation, 2 RX branches implemented as combined 2.1 and 2.6 GHz; no additional antenna port required wtr to default implementation,
•
Additional Radio HW for the 2 additional branches, combiner and wideband TMA
C2 – Vodafone restricted
4-way RX Diversity Results from VF-PT LIVE test • From the mobility tests it can be seen that LTE PS Sessions can be continued/established at a longer distance (200m in straight line) from the base station when 4WRXD is activated. • 4WRXD provides higher UL Throughput than 2WRXD, especially for medium and poor radio conditions.
RSRP 2WRXD Thput 4WRXD Thput -113,5 dBm 409,2 kbps 476,6 kbps
PS Drop with 4WRXD PS Drop with 2WRXD
The extra 3dB UL gain expected from 4WRXD was verified.
HW Required AIR21 B3A B1P (L1800) RBS6601 + DUS41
CPRI - fiber
C2 – Vodafone restricted
4-way RX Diversity Results from VF-PT LIVE test 2WRXD RF Conditions @ -60dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
Mean
Min
Max
-63,37 22936,82
-84,1 0
RF Conditions @ -97dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-96,10 -110,2 11363,63 0
90%-ile
Mean
Min
-59 -61,8 24041,82 23743,12
4WRXD RF Conditions @ -60dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-65,25 23134,99
-83,4 0
-58,6 -59,6 23748,46 23686,18
-94,4 -94,8 14879,1 12892,13
RF Conditions @ -97dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-97,57 17188,27
-99,4 0
-95,4 -96,4 20631,75 18897,63
RF Conditions @ -115dBm Top Cell RSRP (dBm) PUSCH Phy Throughput (kbps)
-115,76 1426,58
-123 0
-113,4 2454,67
Static Location -60dBm
Static Location -97dBm
Normal
Normal 100
Variable 2-way RX UL 4-way RX UL
100
80
Mean StDev N 23307 487,7 62 23508 271,0 62
80
Mean StDev N 11547 1522 62 17452 1581 62
80
20
Perce nt
40
60
40
20
0 22500
23000 23500 Throughput
24000
24500
Mean 1450 StDev 382,0 N 62
60
40
20
0 22000
-113,9 1875,24
Normal
Variable 2-way RX UL 4-way RX UL
60
90%-ile
Static Location -115dBm
100
Perce nt
Perce nt
Tests with 2WRXD could not be executed at -115dBm because session could not be established.
Max
0 8000
10000 12000 14000 16000 18000 20000 22000 Throughput
500
1000
1500 Throughput
2000
2500
From the static tests it was verified that 4WRXD provides more UL Throughput than 2WRXD, mainly for medium and poor radio conditions.
C2 – Vodafone restricted
Co-Tx “Single RAN” technology enables to share a single transport interface among two or more technologies (GSM, 3G e 4G)
Benefits •
Unified O&M systems and transport Operability
•
Reduced number of interfaces
•
Cost – implementation with a shared fiber
•
Common IP: Site appears as one IP host on transport layer
•
Flexible IP addressing, QoS and IPsec concepts
RF modules
RF modules
GSM
UMTS
LTE
GSM
UMTS
Abis
Iub
S1
Abis
Iub/S1
C2 – Vodafone restricted
LTE
Typical LTE configurations: Nokia /1 • LTE800 3 TX
C2 – Vodafone restricted
6 TX
Typical LTE configurations: Nokia /2 • LTE1800 with RF Sharing with RFM
C2 – Vodafone restricted
Typical LTE configurations: Nokia /2 • LTE1800 with RF Sharing with RRH
C2 – Vodafone restricted
Typical LTE configurations: Nokia /3 • LTE2600 with RFM - 4RX
Cell 53 TxRx
Cell 52 TxRx
Cell 53 TxRx
Cell 51 TxRx
Cell 52 TxRx
Cell 51 TxRx
FRHC 1.1.1 1 2 Cell 53 Rx
Cell 52 Rx Cell 53 Rx
Cell 51 Rx Cell 52 Rx
Cell 51 Rx
FRHC 1.2.1 1 2 1 2 3
FSMF + 1xFBBC
3
6 Gbps Obsai 3 Gbps Obsai
Nokia eNodeB Standard Configurations C2 – Vodafone restricted
Typical LTE configurations: Nokia baseband /3 FSME • Same capacity with a single FSMF module with no FBBC extension capability • Optical interface capacity up to 3Gbps and up to 5 RF interfaces with no expansion possibility • No dual band support for 3 sectorial sites. • Overall capacity: 3 cells x 20 Mhz
Evolution of FSMF • Nokia’s high capacity Flexi Multiradio System Module (FSMF) provides multiradio capability and allows capacity to be increased by adding more modules • Optical interface capacity provides up to 6 Gbps - more number of cells that can be supported by each radio module interface • Provides reduction in power consumption compared to previous modules and lowers OPEX • Multiradio and multiband configurations are achievable by the addition of from four to six RF interfaces and through the FSMF’s RF Module chaining capability • The evolution of the FSMF platform to support concurrent mode operation of at least any two technologies is considered critically important. Nokia supports with SW upgrade capability to achieve this • Is used also for WCDMA Active users (RRC connected with at least one DRB establised) case 2x2 DL MIMO
FSFM (w/o CA)
cell
FSMF + FBBA/C (with CA)
eNB
cell
eNB
15MHz 10MHz 15MHz 10MHz 15MHz 10MHz 15MHz 10MHZ 720 600 2160 1800 720 600 4320 3600 14 C2 – Vodafone restricted
Typical LTE configurations: E/// LTE HW Configurations L800
L800
L800
A
B
C
RRUS11 or 12 Dual TX RRH MIMO ready
CPRI - fiber
L800 or L1800 or L2600
LTE Baseband Board Guidelines
2 Radio Units (RUS01 or 02) per Sector to enable MIMO
DUS41 L2600 L2600 L2600 L2600 L2600 L2600
ABC
L1800 or L2600
RBS6601 + DUS
A B C
AIR21 B3A B1P Active 1800MHz Passive 2100MHz MIMO & 4WRXD enabled
CPRI - fiber
C2 – Vodafone restricted
RBS6601 + DUS41
L1800
RBS6201
Typical LTE configurations: Huawei/1 • LTE800 800 MHz
L site
SRN1
BBU GL
800 MHz
FAN LBBPd1
UMPT
UPE U
S1/X2 (IP)
Referring BB board is LBBPd1 • LBBPd1 is capable to handle 3 2T2R LTE cells • Configuration for RRU is identical
BBU LO
16 C2 – Vodafone restricted
800 MHz
Typical LTE configurations: Huawei/2 • LTE1800 with RF Sharing
GL site
BBU GL
SRN1
FAN
GTMU LBBPD2
UMPT
Referring BB board is LBBPd2 • LBBPd2 is capable to handle 3 2T4R LTE cells • Configuration for RRU is identical
A-bis UPE U
S1/X2 (IP) 1800
1800
1800
MHz
MHz
MHz
BBU GL
C2 – Vodafone restricted
Typical LTE configurations: Huawei/3 • LTE1800 with inter BBU RF Sharing GUL site
BBU GU
SRN0
UCIU Wbbp
FAN
GTMU Wbbp Wbbp
UPE U
WMPT/ UMPT
A-bis Iu-b (IP)
BBU LO
SRN1
1800
1800
1800
MHz
MHz
MHz
Lbbp
FAN Lbbpd2
UMPT
UPE U
S1/X2 (IP)
BBU GL
• LBBPd2 is capable to handle 3 2T4R LTE cells • Configuration for RRU is identical
C2 – Vodafone restricted
Typical LTE configurations: Huawei /4 • LTE2600 with 4RX
L site
SRN1
BBU GL
RRU
FAN LBBPd2
UMPT
UPE U
S1/X2 (IP)
RRU Referring BB board is LBBPd2 • LBBPd2 is capable to handle 3 2T4R LTE cells • RRU only
RRU
C2 – Vodafone restricted
Typical LTE configurations: 3G/4G CoTX
800 MHz
GUL site
2100 MHz
800 MHz
2100 MHz
800 MHz
2100 MHz
900 MHz
1800
BBU GU
SRN0
BBU U
Wbbp
FAN Wbbp Wbbpd2
UMPT
UPE U
Iu-b (IP) + S1/X1 (IP)
SRN1
BBU LO
900 MHz
1800
MHz
900 MHz
1800
MHz
UCIU Lbbp
FAN
GTMU Lbbp
UMPT
UPE U
BBU GL
A-bis (TDM)
20 C2 – Vodafone restricted
MHz
Typical LTE configurations: 2G/3G CoTX
GUL site
BBU GU
SRN0
Wbbp
FAN
GTMU Wbbp Wbbpd2
UPE U
WMPT/ UMPT
A-bis Iu-b (IP)
BBU LO
SRN1
Lbbp
FAN Lbbpd Lbbpd2
UMPT
UPE U
S1/X2 (IP)
BBU GL
• LBBPd2 is capable to handle 3 2T4R LTE cells • Configuration for RRU is identical
C2 – Vodafone restricted
Target solution: 2 antennas /sector
Starting solution One antenna / sector
LTE Antenna Evolution 900/1800/2100 X X X X
X X X X
X X X X
Swap to QUAD BAND
X X X X
X X X X
X X X X
Model 1 : 700-800/900/2x18002600 (filtered) Model 2 :2x700-900/2x1800-2600 (side by side)
X X X X
legacy antenna (6 connectors)
900/1800 X X X X
X X X X
900/2100 X X X X
X X X X
900/1800/2100 800/1800/2100 Swap
X X X X
X X X X
X X X X
700/800/2x 2600 700/900/2x2600 X X X X
X X X X
X X X X
X X X X
MIMO 4x4 ready Independent tilt for LBs
•
The goal is to have at least two antennas per sector for new feature requirements ( es. 4-way diversity , MIMO 4x4, etc…)
•
Independent tilt for each system/frequency is crucial for the optimization activities especially for 800 / 900 MHz C2 – Vodafone restricted
First LTE-A implementation: LTE Carrier Aggregation
23
Carrier Aggregation – Executive Summary •
Carrier Aggregation is an important step in LTE-Advanced and enables multiple LTE carriers to be used together to provide very high data rates for the customers
•
Launches and Rollout expansions plans are already ongoing in all the European VF countries where more than one LTE band is available, moving from the most important cities to the medium cities and touristic places.
•
Roadmap for Carrier Aggregation capability increase is available, supporting an increasing numbers of carriers, aggregation across FDD/TDD and wider maximum aggregated bandwidth; some design challenge on terminal (and partially network) requires a phased deployment approach.
C2 – Vodafone restricted
Carrier Aggregation – Capabilities & roadmap Terminal Categories – Rel-10&11
Capabilities
Roadmap for CA evolution
LTE-A
Up to
Up to
20 MHz
20 MHz
Up to 150 Mbps
Up to 150 Mbps
1
Now
2H15*
Future?
3 bands (e.g. 800 MHz + 1800 MHz + 2600 MHz) aggregation: up to 450Mbps
Extended LTE bandwidth
2
Aggregated Data Pipe (Up to 300 Mbps)
Increase LTE performance (e.g. 1800MHz) while voice migrates to 3G/4G (VoLTE)
w/ MIMO 2x2
40 MHz
LTE-A terminal
3 2H15
2016+*
(*) not for the smartphone C2 – Vodafone restricted
FDD + TDD carrier aggregation – Under standardisation First combination FDD1800+TDD2600
LTE Carrier Aggregation allows multiple LTE carriers to be bonded together to improve the customer experience Carrier Aggregation increases the bandwidth available to our customers
20MHz Carrier 10MHz Carrier
Peak speed 150Mbps Peak speed 75Mbps
•
Improved user experience at high and low loads
•
Better consistency at 3Mbps and higher
•
Better HD video with less stalling
•
“Bragging Rights” and competitiveness in Speed Tests
+ Peak Speed 225Mbps with new device supporting Carrier Aggregation
In the next couple of years: • Downlink and 2 bands only • Up to 40MHz FDD Aggregation
C2 – Vodafone restricted
Benefits:
In Urban Areas if we start with 800 deployments on the 900 grid we should add 1800 or 2600 to these sites and carrier aggregate LTE1800/2600 added to 100% of LTE800 sites 1.8 or 2.6GHz 800MHz
+
15/20MHz
15/20MHz
+
+
10MHz
+
10MHz
Deployed 1st
No LTE
LTE 2x30MHz Carrier Aggregation
Maximum Peak Speed Possible 225Mbps
With CA
150Mbps
On 2600 only
75Mbps
On 800 only
Example: Vodafone DE and UK C2 – Vodafone restricted
No LTE
LTE 2x30MHz Carrier Aggregation
No LTE
If we start with 1800 (or 2600) deployments on the 2100 grid we should add 800 to a subset of these sites and carrier aggregate LTE800 added to ~60-80% of LTE1800 sites 1.8 or 2.6GHz 800MHz
+
20MHz
20MHz
20MHz
+
20MHz
20MHz
+
+
10MHz
10MHz
Deployed 1st
LTE 2x20MHz
LTE 2x30MHz Carrier Aggregation
Maximum Peak Speed Possible 225Mbps
With CA
150Mbps
On 2600 only
75Mbps
On 800 only
Example: Vodafone IT and ES C2 – Vodafone restricted
LTE 2x20MHz
LTE 2x30MHz Carrier Aggregation
LTE 2x20MHz
A coverage analysis in Dusseldorf shows that Carrier Aggregation enhances the User Experience across 80% of the indoor area Relative Indoor Coverage 1) Deploy LTE800 on 50 (of 71) Sites 800 Only 2600 Only (50 sites) 800+2600 with Carrier Aggregation
Single User Experience 100 Mbps
75 Mbps
Benefits from CA over 80% of area
2) Upgrade these 50 Sites with LTE2600
50 Mbps
Deep indoors there is no benefit from 2600 - coverage from 800 only
25 Mbps
0 Mbps 0%
20%
40%
60%
% Indoor Area Covered
Single User Speed
<1Mbps
20Mbps
>150Mbps C2 – Vodafone restricted
80%
100%
And benefits of Carrier Aggregation are seen over nearly all the Outdoor area 1) Deploy LTE800 on 50 (of 71) Sites
Relative Outdoor Coverage 800 Only 2600 Only (50 sites) 800+2600 with Carrier Aggregation
Single User Experience 100 Mbps
75 Mbps
2) Upgrade these 50 Sites with LTE2600
50 Mbps
25 Mbps
Benefits from CA over 99% of area 0 Mbps 0%
20%
40%
60%
% Outdoor Area Covered Single User Speed
<1Mbps
C2 – Vodafone restricted
20Mbps
>150Mbps
80%
100%
Carrier Aggregation brings more Urban capacity and enables user experience to be maintained at much higher loads 800+2600 Carrier Aggregation
1800+800 Carrier Aggregation
Average LTE Experience Indoor (Mbps) LTE800
LTE800+2600 CA
LTE1800
LTE1800+800 CA
LTE800
LTE800+2600 CA
LTE1800
LTE1800+800 CA
% Sessions >10Mbps Indoor
Based on VTNA analysis of Dusseldorf
Low Traffic: 33% LTE penetration, LTE Smartphones @1.25GB/month
C2 – Vodafone restricted
High Traffic: 100% LTE penetrations, LTE Smartphones @2.5GB/month
LTE Carrier Aggregation /Nokia Configuration Examples Dual Band 1800+800
32 C2 – Vodafone restricted
LTE Carrier Aggregation /Nokia Configuration Examples Dual Band 2600 + 800
33 C2 – Vodafone restricted
LTE Carrier Aggregation /Nokia Configuration Examples Dual Band 1800+2600 - RF Sharing – 4 Way RX (RL70)
Cell 53 TxRx
Cell 52 TxRx
Cell 53 TxRx
FRHC 1.1.1
Cell 33 TxRx
Cell 51 TxRx
Cell 52 TxRx
Cell 31 TxRx
Cell 32 TxRx
FXEB 1.2.1.1
Cell 51 TxRx
1 2 Cell 32 TxRx
Cell 33 TxRx
Cell 31 TxRx
1 2 Cell 53 Rx
FRHC 1.2.1
Cell 52 Rx Cell 53 Rx
FXEB 1.2.2.1
Cell 51 Rx Cell 52 Rx
Cell 51 Rx
1 2
FSMF + 2xFBBC
1 2 6 1 2 3 3
1 2
6 Gbps Obsai 3 Gbps Obsai
TO ESMx 2G 34 C2 – Vodafone restricted
LTE Carrier Aggregation Ericsson Configuration Examples LTE CA 3 Bands – RRH
LTE CA 2 Bands – RRH L800
L800
L800
L1800
A
B
C
D
L1800 L1800
E
F
L800
L800
L800
A
B
C
D
E
F
DUS41 XMU03 RBS6601 + DUS41
L1800
L1800 L1800
G L2600
H L2600
I L2600
LTE CA 2 Bands – Macro+RRH L800
L800
GH I
DUS41 L2600 L2600 L2600 L2600 L2600 L2600
A B L800
C
RBS6201
SW & Features Requirements • L14A SW Release • Features: 6 Cell Support (FAJ 121 1821) Cascadable Radio Units (FAJ 121 1820) (only required when using macro eNodeB) Carrier Aggregation (FAJ 121 3046) Dynamic SCell Selection for CA (FAJ 121 3063) • HWAC’s should be updated accordingly to the desired capacity
35 C2 – Vodafone restricted
Typical LTE configurations: Huawei CA LTE CA sites are identical to other LTE sites, provided that RF modules and BB boards constraints are satisfied. RF modules to be selected according to site needs. LTE-CA supported by the combinations of baseband processing units in the eNodeB: 1 LBBPc + 1 LBBPd1 1 LBBPc + 1 LBBPd2 1 LBBPd1 + 1 LBBPd2 2 LBBPd1 boards 2 LBBPd2 boards
A combination of 2 LBBPc DOES NOT SUPPORT LTE-CA
36 C2 – Vodafone restricted
Typical LTE configurations: Huawei CA • GSM1800+L1800+L800 CA (example)
800 MHz
800 MHz
GL site
SRN1
BBU GL
800 MHz
LBBPD1
FAN
GTMU LBBPD2
UMPT
A-bis UPE U
S1/X2 (IP) 1800
1800
1800
MHz
MHz
MHz
Referring BB board is LBBPd2 for L1800 and LBBPd1 for L800 • Configuration for RRU is identical
BBU GL
37 C2 – Vodafone restricted
Typical LTE configurations: Huawei CA
BBU GL
• L800+GSM1800+L1800+L2600 CA (example) GL site SRN1
LBBPD1
FAN LBBPD2
UMPT
800 MHz
800 MHz
A-bis
GTMU LBBPD2
800 MHz
UPE U
S1/X2 (IP)
Referring BB board is LBBPd2 for L1800/L2600 and LBBPd1 for L800 • Configuration for RRU is identical
2600
1800
2600
1800
2600
1800
MHz
MHz
MHz
MHz
MHz
MHz
BBU GL
38 C2 – Vodafone restricted
Carrier aggregation – Live results LTE-A
2x 2.6 Ghz
1.8 Ghz
15 MHz
15 MHz
Peak throughput Aggregated Data Pipe w/ MIMO 2x2
30
LTE-A terminal
MHz
C2 – Vodafone restricted
Cell border
Mid range
Site proximity
Active Antennas
40
General AA Executive Summary For each site, the possibility to adjust antenna tilt independently for each system/frequency it is fundamental for the optimization activity In order to be proactive, it is suggest to install antenna 2600MHz capable also in site where 2600MHz is not planned in a short period. The same provision should be implemented for 700MHz . For each site, the goal is to have at least two antennas per sector in order to have the flexibility to adjust the antenna system to the new feature requirements ( es. 4-way diversity , MIMO 4x4, etc…) For sites with single antenna /sector, today multiband antennas with 6 pair connectors (2 low band pair + 4 high band pair connectors) are available only with 2.6m height, 2m version in roadmap for 2015, lower /shorter m versions is under discussion. Put 700 and 800 in separate radomes or separate radiators (for example side by side antennas). Using separate radiators, ie 2 column wide antenna or two antennas, gives acceptable performance but is not allowed on many sites due to contract with site owners For sites with FDD&TDD antenna solution must ensure at least 54 dB (see Annex 2: TDD & FDD interference analysis) of isolation between FDD and TDD
C3 Vodafone Confidential
General AA Guideline Target AA • • • •
Active Antennas are an agreed part of VF strategy with aggressive plans in our guidance All new sites, unless not practically viable All 3G/LTE site upgrades when antenna change is needed, unless not practically viable. For future spectrum readiness, where viable 2 antenna per sector configuration shall be preferred with at least 1 AA
Practical limitations • when unfeasible for camouflage/environmental restrictions • where a complete swap of pole is needed on existing sites - unless necessary for passive antenna also or other reasons e.g. H&S, site infra modernization. Pole reinforcement is acceptable.
Special case considerations •
Sites restricted to single antenna per sector (e.g. passive sharing scenario) and LTE 800: Current AA models do not support separate tilt between 800 and 900 MHz in the passive band; this limitation can be acceptable where the use of AA is justified by other more predominant drivers. Precisely, in this site configuration, AA is recommended when : A) HW Site simplification in 4 or 5 band sites with too many RRUs e.g. AA in LTE 2600 B) Performance on LTE 1800 or 3G in strategic areas C) site energy reduction e.g. macro site with long cables D) separate tilt 800 and 900 is notcritical in the area.
C3 Vodafone Confidential
Active Antenna Concept Overview An active antenna (AA) integrates the radio module(s) and the antenna array(s) in the same box
Key Advantages Power Savings (reduced feeder loss) Cleaner sites (No cables, RRUs, DTMAs) Capacity/Coverage gain (suitable for high capacity scenarios)
Drawback Not all AA models support all bands Weight may be an issue for site installation 43 C2 – Vodafone restricted
Huawei AAs Family AAU3911
AAU3910
AAU3902
Configurati on
2A+2P
2A+1P
2A+2P
Power specs
2x60W 2T4R
2x60W 2T4R
2x40W 4T4R
Supported bands
GL 1800 MHz U 2100 MHz L 2600 MHz GUL 690-960MHz
GL 1800 MHz U 2100 MHz L 2600MHz
GL 1800 MHz U 2100 MHz LTE 2600 MHz GUL 790-960MHz
Supported RATs
GUL
GUL
GUL
Size [mm]
2020x360x290
1450x320x230
2000x350x260
Weight [Kg]
49 (1 active module) 65 (2 active modules)
39.5 (1 active module) 53.5 (2 active modules)
53 (1 active module) 62 (2 active modules)
Availability
Tests ongoing
To be tested
Rolled out
44 C2 – Vodafone restricted
No big differences on wind-load and pole dimensioning
Huawei Example: adding LTE800/2600 to 900/1800/2100 Site Option 1: Swap to new Passive Antenna 900/1800/2100 2 Antenna Site Passive: 1800
X X X X
Passive: 800/1800/ 2600
Passive: 900/2100
X X X X
X X X X
Add LTE800 /2600
X X X X
X X X X
X X X X
Passive: 900/2100
Wind Load
2650 N
Weig ht
64Kg
Wind Load
2660 Based on local N market rules.
Weig ht
Antennas + 3 Pairs of Cables
Antennas + 5 Pairs of Cables
Option 2: Swap to Active Antenna X X X X
Active: 1800/2100 Passive: 800/2600 RF Cables Fibre + DC
C2 – Vodafone restricted
X X X X
X X X X
X X X X
Passive: 900
98Kg
Wind load similar Weight not critical in pole dimensioning
AAs Key Features AAU3902
VERTICAL MULTIPLE SECTORS UL/DL capacity improvement Suitable for high traffic scenarios
46 C2 – Vodafone restricted
AAU3902
VERTICAL 4 WAY DIVERSITY UL throughput improvement Coverage gain
AAU3911/AAU3910
HORIZONTAL 4 WAY DIVERSITY
UL throughput improvement Coverage gain
Ericsson AIRs Family DRIVERS Model
Description
NEW sites (Non Urban)
RAN Refresh / LTE sites
AIR11 B20A / B8P
AA in 800 MHz with independent passive antenna for 900 MHz
G900/U900 + L800
L800 upgrades in existing low band only sites
AIR21 B1A / B3P
Dual AA in 2100 MHz with 2T/4R capabilities and independent passive antenna for 1800 MHz
Sites needing U2100
Sites needing Refresh in U2100
AIR21 B3A / B1P
Dual AA in 1800 MHz with 2T/4R capabilities and independent passive antenna for 2100 MHz
Sites where AIR for U2100 not possible requiring LTE1800 with no DCS and RRU installation constrains
Sites with U2100 already Refreshed requiring LTE1800 with no DCS and RRU installation constrains
Smart Architecture
Architecture Evolution • An important pre-requisite for self-organizing networks and efficient configuration management is a simpler and flat architecture – The complete E2E chain (including Access Network & MW) to be as much future proof as possible – MTU expansion mandatory especially when introducing IPSec – Distributed SecGw model is crucial for – Improve Latency – Decrease the number of hops – Security guaranteed by the introduction of IPSec
Insert Confidentiality Level in slide footer C2 – Vodafone restricted
49
June 9, 2015
3GPP Architecture Evolution
50 C2 – Vodafone restricted
E2E connectivity
51 C2 – Vodafone restricted
4G Vodafone Architecture
eNB MME
IP Backbone
Access TX SeGW
eNB
SAE-GW
~ ToP Master
O&M
eNB Primary Reference Clock
C2 – Vodafone restricted
Path differentiation MME
SeGW 2
IP Backbone
Access TX SeGW 1
eNB
SAE-GW
Timing over Packet (IEEE 1588)
~ ToP Master
Control Plane (CP) User Plane (UP) Operation and Maintenance (O&M) Syncronization
C2 – Vodafone restricted
O&M
Primary Reference Clock
Security Gateway (SecGW) • LTE security requires a different system protection as mobile backhaul traffic becomes more vulnerable to hacker attacks • IPsec provides a comprehensive set of security features like – data origin authentication – Encryption – integrity protection
Non IP traffic
UE
LTE eNB
IP traffic
Un-Trust network IPsec tunnel SecGw
Core Trust network
CA LTE – IPsec Tunnel Mode encapsulates and protects the entire source IP packet
54 C2 – Vodafone restricted
Internet
CA LTE: for device eNB and SecGW site • VF architecture include front-end (FE) servers and a back-end (BE) server • The FE is used for the delivery of certificates: – the clients are connected using the CMP or SCEP protocol
• The BE is the engine of CA LTE platform: – the logical application to create the certificate and each certificate are store into the Oracle DB – The BE is the core of CA, it signs all the certificate requests from eNodeB and Security Gateway.
• Each client (eNB/SecGW) contact the FE of CA LTE through the VIP address
55 C2 – Vodafone restricted
SCTP Multi-homing concept
SeGW1
SeGW2
• It provides transparent fail-over between redundant network paths • a ‘keep alive’ message is sent on the primary and secondary paths to verify e2e connection • as soon as the primary path fails (because of any of the nodes or links) the SCTP association automatically switch to the secondary path without any impact on the existing connections
• Requirements • Both endpoints of the connection can support more than one IP address • The two paths have to be physically separated
C2 – Vodafone restricted
Architecture and Tunnel Mapping
CP
CP
UP
UP
Tunnel 1
O&M O&M2
O&M2
Tunnel 2
MME MME
CP2
CP2 eNB
O&M
Router
SeGW1 CP UP
• Target solution for Vodafone • SCTP multihoming support from day 1 • Support for two O&M:
O&M O&M2 CP2 SeGW2
• First O&M in tunnel to provide security on KPI and commands • Second O&M out of tunnel to provide connectivity (SSH, HTTPS) if the tunnel breaks down • O&M2 is activated only if tunnel 1 is down
C2 – Vodafone restricted
CS Fallback CSFB (Circuit Switched Fall Back) • It allows UE camped on the 4G network for PS services to attempt/receive a CS call on CS overlapping GSM/UMTS networks • Three methods: PS Handhover, CCO with/without NACC (specific for GSM case), Redirection
58 C2 – Vodafone restricted
Smart Radio Planning
59
Smart Radio Planning SON Approach
Main Challenges – Increasing OPEX for the skilled staff for local commissioning and configuration activities – Increasing CAPEX due to overdimensioning – High operational impact of periodic replanning – Cell Specific Settings on 4G: PCI, RSI, PRACH planning i.e. PCI reuse to be too high and its impact on the RS SINR – Labor intensive neighbour relations handling activity (intra/inter frequency, inter-RAT)
– Minimum or zero manual configuration – Plug & Play: Functionality that enables to simplify the eNB integration – Automatic cell specific settings: PCI conflict resolution, PRACH optimization – Automatic neighbour relations and the setup of X2 interfaces thus reduced HO failure caused by missing neighbour relations – Higher reliability of SW installation – Real-time network auto-tuning – Quick site configuration i.e. 10-click via NCM
Legacy process Auto-configuration process C2 – Vodafone restricted
Site design Enhanced Site design
HW config. 60
Data configuration
HW order
June 9, 2015
SON – At a Glance
SON (Self Organizing NW) is an automation technology designed to
planning, configuration, management, optimization and healing of mobile radio make the
C2 – Vodafone restricted
PCI Planning manual vs automatic planning • Analogous to scrambling code planning in UMTS • In NSN areas, PCI planning can be done automatically with NetAct Optimizer: – Re-use of the same PCI in the same area is reduced as much as possible – When a new cell/site is added to an existing cluster, PCI planning is re-made in order to respect PCI planning rules, optimise PCI re-use and maximize network performances
• In Huawei areas, automatic PCI planning is not available: – There are features available to detect PCI collisions to optimize them looking for a new PCI. It works over eNodeB SW, not needed extra HW or SONMaster
LOFD-002007 PCI Collision Detection & Self-Optimization – To perform PCI Planning activities an external tool would be needed
• In Ericsson areas: – PCI Conflict Management supported (OSS) – PCI Conflict detection and fix – under test – PCI planning with external tools - Atoll
Very high operational impact of periodic manual PCI replanning C2 – Vodafone restricted
1
PCI Planning – Real Life Example from Rome manual vs automatic planning • After some rounds of manual planning, the PCI re-use in Rome was too high • A lot of PCIs were used 3/4 times in the same city with ~600 cells On Air • Very difficult to find areas with RS SINR higher than 22 dB. After the rollout of the New PCI Plan, re-use was significantly
• Higher RS SINR could be immediately measured
Critical to ensure good automatic PCI planning ! C2 – Vodafone restricted
Re-use 1
Re-use 2
Re-use 3
Re-use 4
Old PCI plan
34
128
84
4
New PCI plan
173
198
-
-
LTE Design Standard on Uplink Physical Random Access Access Channel RSI planning • Principle & gain •
PRACH preambles created from Root sequences to get Access to the eNode B by the UE
•
838 RootSequences are available to generate the PRACH preambles by combined cyclic shifting =
•
If same root sequences used in neighbouring cells overlap, the transmitted preamble may be detected in multiple cells
•
The false RACH detection alarm probability may be increased
•
RootSequenceIndex (RSI) points to the first root sequence to be used when generating the set of 64 preamble sequences
•
Number of root sequences allocated to a cell depends on the cyclic shift Ncs linked to the cell range (table)
•
RSI planning prevents blocking of UE Random Access and drops during Handover
C2 – Vodafone restricted
LTE Design Standard on Uplink Physical Random Access Channel Root Sequence Index (RSI) planning Software requirements: Tools based allocation with Atoll and AFP At least Atoll version 3.2.1 is required: PRACH RSI allocation capabilities by default Cell range based allocation will be available with Atoll version 3.3.0 with an additional Makro module With Nokia RSI automatic planning available in NetAct Optimiser
Status in Vodafone: The default allocation of 10 Root sequences per cell is done across the VF-OPCOs Nokia OpCos: • NetAct Optimiser used. Huawei/Ericsson OpCo: • Atoll typically used. The false RACH alarm probability went from around 90% before to maximum 5% after implementing the RSI planning in the VF-DE Ericsson Region 65 C2 – Vodafone restricted
PCI/RSI Planning – Real Life Example manual vs automatic planning With PCI/RSI Planning
Without PCI/RSI planning
Handover Failure Rate increases exponentially
Drop call rate increases
66 C2 – Vodafone restricted
Plug & Play approach
DHCP MME
IP @ temp
IP backbone
Access Tunnel TunnelTX New eNB
Certificate
SAE-GW SeGW 1-2
eNB temporary IP@ from DHCP Certificate to setup the IPSec tunnel to SeGW eNB complete configuration (IP@ etc) from O&M in tunnel Control Plane (CP) User Plane (UP) Operation and Maintenance (O&M)
C2 – Vodafone restricted
OSS CA Server & Repository
Automatic Neighbour Relation (ANR)
/1
What: Automatic definition of intra-frequency and inter-frequency neighbouring cells. No more need for neighbouring planning and definition. • Inter-RAT definition still manual due to lack of terminal support
How it works: 1. Cell-A sends measurements request to UE 2. UE reports strongest PCI=5 (Cell-B) to Cell-A 3. Cell-A finds new PCI=5, so it indicates UE to report Cell-B’s CGI 4.UE reads BCH to measure CGI, TA, PLMN ID, etc. 5.UE reports CGI=19 of Cell-B to Cell-A 6.Cell-A add Cell-B to it’s NRT 7.Cell-A looks up IP address of Cell-B and establishes X2 link
Benefits: - Save cost of neighbor cell planning during initial deployment and network expansion - Automated X2 link establishment with neighbor cell - Reduce HO failure caused by missing neighbor relation (better user experience). C2 – Vodafone restricted
Specialized Tools An efficient configuration management process requires easy to use, flexible and process oriented specialized tools in order to have well designed and stable standard low level configurations •
NCM: Wizard style low level data configuration preparation tool.
10-Click site configuration
•
Nokia Optimizer Tool: Locating the critical “polluter cells” and check design parameters
•
Sito: Configuration adapter to SAP HW order
C2 – Vodafone restricted
Automatic Overshooting Discovery Problem definition: • Unoptimised tilt/transmitted power on some sites leading to excessive interference generation on adjacent area • Very time-consuming in-field verification (drive tests) • No immediate evidence from counters due to limited traffic Idea: • Reuse automatically generate neighbour relation and optain automatic picture of “neighbour distance”. • Locate the critical “polluter” cells and check design parameters. Solution: • Based on NSN OSS Optimiser tool • Periodical usage to find interference and revise tilt.
C2 – Vodafone restricted
Automatic Overshooting Discovery
Sample Report from Milan
C2 – Vodafone restricted
SON – At a Glance
SON (Self Organizing NW) is an automation technology designed to
planning, configuration, management, optimization and healing of mobile radio make the
SON_Cisco C2 – Vodafone restricted
Nokia iSON
SON Nokia CISCO
Huawei SON
3MHz LTE 900 MBB solution for non 3G area
Summary • Opportunity – – – – – – –
Solution for mobile broadband demand – performance comparable to UMTS 900, better latency Interim competitive advantage Extremely Fast implementation in 2G modernized area Fully compliant with SRAN concept (reuse of 2G RRH) Simple migration to LTE 800 No lost investments – all expenses fully reusable for LTE 800 Solution for 2G data offload
• Limitations – 2G capacity, 2G quality (GSM will operate in limited spectrum) – Spectrum use close to country borders is limited by international agreements about preferential channels for GSM – In high traffic areas (plus buffer zones) the whole 900 MHz spectrum is needed long term for GSM 900
• Short term solution – 3MHz bandwidth offers 4 x smaller bitrates and significantly lower capacity compare to 10 MHz bandwidth
74 C2 – Vodafone restricted
Site configuration Initial Modernized GSM 900 GSM 900
GSM 900 + LTE 900 (3)
GSM 900
RET
RRH 900
LTE 900
Final GSM 900 + LTE 800 (5-10) LTE 1800 LTE 800 (capacity)
GSM 900
RET
RET
RET
RET
RRH 900 RRH 800 RRH 1800
RRH 900
NEW Single RAN BBU
Single LTE BB RAN BBU
Single RAN BBU
According to LTE contract, licenses shall be transferable. No dedicated LTE 900 expenses! All HW and licenses can be reused for LTE 800 – no lost investments when migrated to LTE 800 75 C2 – Vodafone restricted
Terminal support • All terminals support 3MHz bandwidth • About 80% of current LTE terminals support LTE 900, almost all new terminals come with LTE 900 support • Good public source of information about terminal support is on: – http://www.gsmarena.com/results.php3?s4Gs=LTE900
System support RAN vendor Huawei • SW Support from release SRAN 8 (GBSS15 + eRAN6) • BTS/eNodeB HW : – RRUs: 3928, 3929 and newer – LBBPd1 and newer
• MSR mode (MSR = GSM+LTE in the same RRU) – There is no difference between performance of LTE 900 (3MHz) and GSM 900 + LTE 900
76 C2 – Vodafone restricted
Performance of LTE 3MHz • On 3MHz carrier theoretical maximum is app. 20 Mbps (similar to HSPA+, SC) • Practically achieved maximum 17,3 Mbps average speed around 8Mbps • Better latency than in 3G (3G < 100 ms, LTE < 50 ms) • In GSM 900 footprint we can achieve on the cell edge – App. 250 - 700 kbps for LTE 900 (3), which is comparable to performance of UMTS900 • Uplink achieved maximum 6,5 Mbps, average around 3Mbits • Better maximum number of users handling compared to UMTS
Performance of LTE 900 (3) is similar or better than performance of HSPA
Way forward LTE with 3 MHz bandwidth is not long term solution for MBB wide coverage For competitive MBB coverage the 10 MHz channel in spectrum bellow 1 GHz shall be used. Very fast LTE rollout wherever only EDGE coverage present. Solution for low traffic areas 77 C2 – Vodafone restricted
Smart Tx Planning
78
Smart TX Planning Main Challenges
Smart TX Planning Approach – IPSec to provide security services for traffic at the IP layer – MTU adaptation from the beginning in order to support Jumbo Frames (MTU > 1600) on the whole E2E chain to avoid dupACK, packet out of order and refragmentation – Implementation of shaping and optimization of configurations to solve issues related to buffer – Different QoS streams and EPS bearer concept – Optimized MW Configurations (operating band & bandwidth, spanning tree configuration, buffer requirements & shaping, etc.)
– Challenges on TX dimensioning and configurations due to higher peak rates (i.e. 100Mbps+) and lower latency of the LTE technology – “Low throughput” or “underperforming TCP traffic” caused by incorrect E2E dimensioning of the TX network – Packet drops due to limited buffer – Low performance due to packet segmentation with IPSec enabled – Other incorrect / unoptimized configurations
79
IPSec – MTU Size Adaptation • Stands for IP Security and defines a set of protocols • Currently described in RFCs 2401-2412, and 4301 • Provides security services for traffic at the IP layer • Uses Encapsulation Security Payload (EPS) which provides: Data origin authentication Connectionless integrity Confidentiality
RLC eNB
IP S-GW
User IP Payload
UDP
GTP-U
User IP Payload
Tunnel 1 SeGW
eNB IP in Tunnel
EPS
IP SeGW
UDP
GTP-U
User IP Payload
S-GW
Trailer
1500Byte
MTU Size Adaptation MTU Size to be larger than1600B
C2 – Vodafone restricted
IP User Packet Max Size GTP-U Header Max Size UDP Header Size IP Header IPSec Header Total
Size [byte] for X2-User Plane 1500 16 8 20 64 1608
Size [byte] for S1-User Plane 1500 12 8 20 64 1604
IPSec ON vs IPSec OFF Data performance
Bands usage
81 C2 – Vodafone restricted
Shaping The bucket shapes the flow at a fixed rate (SR) and no burst is
Without shaping 1G
0
1G
permitted also if the output line rate is bigger, e.g. 1 Gbit/s
L2/L3 switch
If the ingress flow fills the bucket, the new packets will be
buffer 1Gbps line rate
lost.
200Mbps line rate
With shaping
In general, the Average Ingress Rate needs to be less than the Shaper Rate, otherwise the Bucket filling and the packet loss
L2/L3 switch
200M
will be unavoidable. buffer 1Gbps line rate
200Mbps line rate
Packet loss vs Throughput
B = Bucket Size
SR = Shaper Rate
Througput
IR = Variable Ingress Rate
90 80 70 60 50 40 30 20 10 0 0,00%
82 C2 – Vodafone restricted
0,01%
0,05%
0,10% Packet loss
0,50%
1,00%
5,00%
QoS EPS Bearer Concept • 4G uses the concept of EPS bearer to route IP traffic from the PDN to the UE • An EPS bearer is an IP packet flow with a defined Quality of Service (QoS) between the PDN Gateway and the UE • Multiple bearers can be established for a user to provide different QoS streams (one EPS bearer for each QoS streams) • Each bearer has an associated: - ARP (Allocation and Retention Priority) to be used in admission - QCI (QoS Class Identifier) to identify: scheduling policy queue management policy rate shaping policy RLC configuration • GBR = Guaranteed Bit Rate • EPS bearer in GPRS is known as PDP context C2 – Vodafone restricted
QCI
Resource Type
1 2 3 4 5 6 7 8 9
GBR GBR GBR GBR Non-GBR Non-GBR Non-GBR Non-GBR Non-GBR
Priority 2 4 5 3 1 7 6 8 9
Pck Delay Budget [ms] 100 150 300 50 100 100 300 300 300
Pck Error Loss Rate 10-2 10-3 10-6 10-3 10-6 10-3 10-6 10-6 10-6
Example Voice Live video Buffered video Real-time gaming IMS signaling TCP-based services TCP-based services TCP-based services TCP-based services
QoS EPS Bearer Concept • Default bearer: established when UE attaches to the network - provides IP addresses and always-on IP connectivity to PDN - for all non-GBR flows that do not require QoS treatment -QCI assigned by MME based on subscription data received from HSS (typically 8 or 9) • Dedicated bearer: additional bearer established by network on UE request -for service data flows that require GBR QoS treatment • Packets filtering into bearers is performed by the UE in uplink and by the PDN gateway in downlink and it is based on TFTs (Traffic Flow Templates) - A TFT is a set of packet filters associated with an EPS bearer - A packet filter can be based on IP addresses, TCP ports, protocols, etc. - A default bearer may or may not be associated with a TFT (based on HSS data) but each dedicated bearer is always associated with a TFT
C2 – Vodafone restricted
QoS QCI – DSCP Mapping • DSCP (Differentiated Services Code point) is a field in IP header that is used for packet classification purposes in IP networks to provide QoS • Higher DSCP indicates higher-priority traffic on the Transport network • DSCP configuration in VF 4G: - Signaling: DSCP 46 - O&M: DSCP 0 - Data: definition of demo, gold, silver, bronze profile QCI
C2 – Vodafone restricted
Resource Type
Example
DSCP mapping
User Profile
1
GBR
Voice
46
All
2
GBR
Live video
46
All
3
GBR
Buffered video
46
All
4
GBR
Real-time gaming
46
All
5
Non-GBR
IMS signaling
34
All
6
Non-GBR
TCP-based services
34
Demo only
7
Non-GBR
TCP-based services
26
Gold only
8
Non-GBR
TCP-based services
18
Silver only
9
Non-GBR
TCP-based services
10
Bronze only
Temporary values
Site Acceptance Support Tools
86
Site acceptance phase
/1
• After the installation and integration, the new eNodeB should be accepted. • Dedicated acceptance procedure is defined to verify the site performance: – 4G: Latency test, DL/UL Throughput test , CSFB Call (MOC/MTC) , VoLTE Call (MOC/MTC) , Emergency Call , SMS – 3G: Latency test, DL/UL Throughput test, Voice Call (MOC/MTC) , Emergency Call, SMS – 2G: EDGE Activation , DL/UL Throughput test, Voice Call (MOC/MTC), Emergency Call, SMS – SRAN alarms : check about active alarms on both legacy and 4G systems – Antenna cable : coherence between HW/SW configuration and radiated Scrambling Code/Cell ID or PCI
2G validation procedure
3G validation procedure
• At the end of the acceptance test, three situations may occurs – eNodeB switched off: eNodeB shall be locked and an immediate troubleshooting session shall start – eNodeB switched on with troubleshooting: eNodeB shall be switched and troubleshooting session shall start – eNodeB switched on : ready for next steps of conditional acceptance
87 C2 – Vodafone restricted
4G validation procedure
Site acceptance phase
/2
• Support tools are used for site acceptance phase : – UDP Test : tests transport bottleneck issues – Pinger tools : reachability tests with core network – Radio Acceptance app : Following tests are executed using the app CSFB (both MO and MT calls) Emergency calls E2E Latency DL/UL Throughput SMS transmission and reception Swapped feeders Alarm verification and clearance on both 4G and legacy sistems Antenna system validation
88 C2 – Vodafone restricted
UDP Test • The UDP test consists in 30s UDP stream@100/150/200 or 250Mbps from a server (using iPerf) on the O&M network towards the eNodeB •
TRS PM counters on the eNodeB allow to compute Packet Loss Ratio
Core Network
Access TX
100 Mbps
Insert Confidentiality Level in slide footer C2 – Vodafone restricted
Packet Received Ratio
Results
<20%
TX Issues
>20% & < 90%
Should be investigated
> 90%
89OK
June 9, 2015
Pinger Tool • eNodeB_PINGER is a tool for the reporting of the S1 link availability and round trip time statistics
Actual query outcomes • eNodeB peer end availability
• The tool generates at least two reports per day and exposes the results directly on Vodka
– MME primary, secondary – PGWs – SecGW
• Round Trip Time statistics (AVG / MIN / MAX RTT) on the leg eNodeB - SecGW
Architecture 3. PING EXECUTION between the eNodeB and the different peer end 2. CENTRAL SERVER logins in NodeB, enable SSH if necessary
1. CENTRALSERVER retrieves the eNodeB anagraph from a DB
MMEs
PGWs
firewall
DB1
CPN (O&M)
IT LAN
eNodeB TX board SGWs
4. PING logs stored in CENTRALSERVER
C2 – Vodafone restricted
Central Server
DB2
Intranet
5. CENTRALSERVER parse the ping log and store the results in a DB2; results will be visible in a KPI Analyser tool
KPI Analyzer
Radio Acceptance App
/1
• Vodafone Radio Acceptance App performs all the tests required by the Validation procedure in a very fast and automated way such as : • CSFB (both MO and MT calls) • Emergency calls • E2E Latency • DL/UL Throughput • SMS transmission and reception • Swapped feeders • Alarm verification and clearance on both 4G and legacy systems • Antenna system validation • It represents an efficient, global, and not-ambiguous tool that speeds up the site integration procedure • It also guarantees that the validation procedure is carried out according to Vodafone guidelines (especially when the procedure is done by third parties)
91 C2 – Vodafone restricted
Radio Acceptance App
/2
• After the execution of the whole test list, the app automatically sends the reports to a specific database. The details will be available in the Backend Interface • All updates and configuration files are stored in a central server. This way, changes and/or updates can be delivered to all devices with just one click • Each OpCo can have different configuration files with different and specific settings
92 C2 – Vodafone restricted
More Documents from "sivakumar"
Value Set Security Feature In 12.pdf
October 2019 2
Hitler Re
April 2020 0
5302010310.pdf
May 2020 0