B12 SW Release Benefits

B12 BSS Release Presentation
AGENDA
1 Business Drivers 1. Business Drivers
2. Alcatel-Lucent Value Proposition p
3. BSS B12 Detailed Features
4. Hardware Coverage
5 Conclusion 5. Conclusion
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
3
AGENDA
Part 1 | Business Drivers
Part 2 | Alcatel-Lucent Value Proposition
Part 3 | BSS B12 Detailed Features
Part 4 | Hardware Coverage
Part 5 | Conclusion
4
BUSINESS DRIVERS
ADDRESS ALL THE DIFFERENT MARKETS ADDRESS ALL THE DIFFERENT MARKETS
Mature Markets
Renovation of 2G equipments with TCO
reduction & guaranteed evolution
3G d k ff &
High Growth Economy
Operators still in a deployment and
densification phase
O d CO&f dd 3G and LTE take-off & service continuity
makes the data 2G traffic increase
Optimized TCO & footprint to address new
markets and low ARPU users
Differentiate on Voice
and data
Reduce Total Cost of
Ownership
Increase Capacity and
Technology
Interworking
5
AGENDA
Part 5 | Conclusion
6
ALCATEL-LUCENT VALUE PROPOSITION
B12 RELEASE OVERVIEW B12 RELEASE OVERVIEW
B11 B12 B13
Increase
Capacity &
A (UP) over IP
Native IP transport in BSS
BSC 1400 TRX
A sig over IP, Aflex
& Gb Flex
STM-1 in BSC
BSC it 12000 E/ b
GERAN Evo
Downlink Dual Carrier
Capacity &
coverage at
Lowest TCO
Boosted GP
36 TRX per SUM
MSR 2G+3G / 2G+4G
Dynamic Power Voltage
BSC capacity 12000 E/cab.
Synchronized networks
Antenna hopping
S
EGPRS2
Dynamic Frequency and
Channel Allocation
Dynamic Power Voltage
adjustment
VAMOS
Dynamic Power Save
4 CCCH
A5/3 i h i
Differentiate
on Voice
Multiple Operator Core
Network (3GPP)
MTC (M2M 3GPP R10)
Up to 4E1 links per SUM
LTE GSMH d
A5/3 ciphering
Repeated FACCH/SACCH
TFO for NB-AMR
Differentiate
on Data
LTE to GSM Handover
(SRVCC)
Inter-BSS/RAT NACC
GSM-LTE Interworking
7
B12 RELEASE BENEFITS (I) B12 RELEASE BENEFITS (I)
KEY BENEFITS
IP TRANSPORT
IN BSS
A(UP)oIP
Bandwidth efficiency;
CAPEX and OPEX reduction;
BSS architecture simplification;
3G/LTE convergence; A(UP)oIP 3G/LTE convergence;
Better voice quality;
BSC 1400 TRX
BOOSTED GP
KEY BENEFITS
Increase BSS voice traffic capacity;
Increase the BSS data traffic capacity;
Reduce CAPEX and OPEX for BSC/MFS Evolution; Reduce CAPEX and OPEX for BSC/MFS Evolution;
MSR 2G+3G,
KEY BENEFITS
S CAPEX f M lti RAT it
MSR 2G 3G,
2G+4G
VAMOS
Save CAPEX for Multi-RAT sites;
Optimize power consumption;
Maintain or increase cell voice capacity during spectrum re-farming;
Improved spectral efficiency;
8
p p y;
B12 RELEASE BENEFITS (II) B12 RELEASE BENEFITS (II)
DYNAMIC KEY BENEFITS DYNAMIC
POWER
VOLTAGE
ADJ USTMENT
KEY BENEFITS
Optimize power consumption for multi-carrier modules;
Reduce network OPEX;
Increase RF modules reliability;
(DPVA) Reduce cooling expenses for indoor sites;
4 E1 LINK PER
SUM
36 TRXPER
KEY BENEFITS
Differentiate on data;
Deliver more voice channels and data throughput per site;
Increase revenues; 36 TRX PER
SUM
Increase revenues;
Reduce CAPEX for sites with high voice and data traffic;
KEY BENEFITS
LTE TO GSM
HANDOVER
KEY BENEFITS
Ensure voice continuity from LTE layer (VoIP) to GSM layer;
Increase customer satisfaction by avoiding CS fallback procedure;
Improve interworking between GSM and LTE layer;
9
p g y ;
AGENDA
Part 5 | Conclusion
10
BSS B12 DETAILED FEATURES
BSC/MFS CAPACITY INCREASE BSC/MFS CAPACITY INCREASE
Boosted GP is the evolution of the current MFS Evo GP board;
Support of Boosted GP board
Boosted GP is the evolution of the current MFS Evo GP board;
Will support more PDCH capacity and Gb throughput;
Improve A-ter interface usage;
Can be mixed with existing GP board;
Available only for MFS Evolution;
BSC Evolution 1400 TRX
7+1 CCP boards per BSC Evolution;
Up to 1400 TRX per BSC, 2800 TRX per cabinet;
Lower site cost (smaller footprint);
Reduced power consumption;
Lower A/A-ter transmission OPEX;
Up to 12600 Erlangs per cabinet (with IP BSS and A(UP)oIP);
Supported with TP STM1 or TP STM1-IP boards; Supported with TP STM1 or TP STM1 IP boards;
REDUCE CAPEX/ OPEX FOR BSC/ MFS EVOLUTION
11
DYNAMIC POWER VOLTAGE ADJ USTMENT (DPVA) DYNAMIC POWER VOLTAGE ADJ USTMENT (DPVA)
Feature Description
constant supply
voltage
modulated
U
1
, U
2
, U
3
: different PA power supply
voltages (bias);
Highest output power reached @ U3;
PA lt it h t U if l
modulated
supply voltage
PA voltage switches to U
1
if lower
output power (P
low
) is required;
Available only with MC-TRX and MC-
RRH modules;
amplitude
dissipated
Feature Benefits
Adapt MC-TRX efficiency according
to traffic load;
modulated
signal
dissipated
power
;
Save energy by keeping a constant
high module efficiency;
MC-TRX EFFICIENCY ADAPTED TO TRAFIC REALITIES
MSR 2G+3G 2G+LTE MSR 2G+3G, 2G+LTE
Feature Description
2 R di A T h l i i 2 Radio Access Technologies running on
the same MC-TRX module (same band);
No combiner needed for 2 technologies;
Typical cases: GSM/UMTS 900 or
GSM/LTE 1800;
Requires B12 1/UA8 1 and B12 1/LA5 0 Requires B12.1/UA8.1 and B12.1/LA5.0
Feature Benefits
Saves radio modules antennas and
LTE and GSM carriers configuredon MC-TRX
3G
LTE
Saves radio modules, antennas and
feeders for multi-RAT sites;
Optimize power consumption;
3G
2G
MC-TRX EFFICIENCY ADAPTED TO TRAFIC REALITIES
13
LTE TOGSMHANDOVER LTE TO GSM HANDOVER
LTE to GSM Handover
LTE
Concerns voice calls only;
Based on Single Radio Voice Call Continuity (SRVCC)
procedure;
LTE
UMTS
GSM
Perceived by BSS as a classical incoming CS HO;
No limitations in term of neighbor cells declared for
incoming LTE to GSM handovers;
BSS impacts similar to UMTS >GSMHO: BSS impacts similar to UMTS -> GSM HO:
Possibility to reject incoming LTE HO in case 2G
cell is too heavily loaded;
Newcounters to differentiate such HO categories; New counters to differentiate such HO categories;
Requires 3GPP Rel.8 compliant core;
IMS and Sv interface must be present in core network;
IMPROVE VOICE CALL PERFORMANCE
14
4E1 LINK PER SUM 36 TRX PER SUM 4E1 LINK PER SUM, 36 TRX PER SUM
4E1 LINK PER SUM 36 TRX PER SUM
3
rd
and 4
th
E1 link supported by a logical
BTS;
Supported on SUMX and SUMX19 modules;
Allows configuration up to 36 TRX per one
logical BTS;
Available with SUMX and SUMX19 boards; pp ;
Suitable for high packet traffic or increased
number of TRX;
;
Applicable in configurations with MC-TRX
or MC-RRH modules;
Avoids installation of additional SUM board;
Differentiate and increase revenues from the
already existing sites by supporting higher
In case of TDM BTS, depending on the
volume of packet traffic, 3 or 4 E1 links must
be used on Abis;
data speeds and volumes;
DIFFERENTIATE AND INCREASE REVENUES AT LOW CAPEX
15
VAMOS: MAIN PRINCIPLES VAMOS: MAIN PRINCIPLES
Simultaneous sharing of radio channel(s) inside one radio timeslot
- 1 FR channel shared : 2 FR users
- 2 HR channels shared : 4 HR users
In downlink
- The BTS transmits simultaneously to 2 MSs on the same timeslot and frequency
Q
- Using two different Training Sequences (TSC)
- With adaptive-QPSK modulation
- One adaptive-QPSK symbol is a pair of bits where each bit belongs
(1,0) (0,0)
Q
- One adaptive-QPSK symbol is a pair of bits, where each bit belongs
to a different sub-channel
- Allows to double the throughput compared to legacy GMSK
- Variant of QPSK allowing for independent power control for the two users
I

Variant of QPSK allowing for independent power control for the two users
In uplink
- 2 MSs transmit simultaneously on the same timeslot and frequency, using GMSK and different TSC
(1,1) (0,1)
- The BTS uses the different TSC to separate the signals from the two MSs
VAMOS: SUPPORTEDMOBILES ANDPOSSIBLE PAIRINGS VAMOS: SUPPORTED MOBILES AND POSSIBLE PAIRINGS
Two levels of VAMOS MSs
L l 1 SAIC MS th t i dditi bl t t i i f th TSC t (TSC S t 2) - Level 1: SAIC MSs that in addition are able to use training sequences of the new TSC set (TSC Set 2)
defined in 3GPP for VAMOS MS
- Level 2: VAMOS-specific algorithms for interference cancellation instead of SAIC
Pairing is not limited to VAMOS mobiles
- Also possible with Legacy SAIC MS, as they are able to operate at low SIR values
SAI C / SAI C i i i ll d b t ith li it d t f TSC bi ti f TSCS t 1 t - SAI C / SAI C pairing is allowed but with a limited set of TSC combinations of TSC Set 1, to ensure
sufficient performance. There is therefore an impact on TSC planning
- Legacy non-SAIC mobiles could also support VAMOS operation but only if coupled to VAMOS Level 2 MS
Non SAIC SAIC VAMOS L1 VAMOS L2
Non SAIC No No No Likely Yes
SAIC Yes Yes Yes
VAMOS L1 Yes Yes
VAMOS L2 Yes
Possible VAMOS pairing
VAMOS: INTRODUCTION SCENARIOS VAMOS: INTRODUCTION SCENARIOS
VAMOS allows to convert a quality margin to additional capacity
- Good C/I conditions: Up to 100% gains
- Poor C/I conditions: No gain
Possible scenarios
Capacity increase in existing network
Instead of newTRX +reworked frequency planning - Instead of new TRX + reworked frequency planning
Or PS capacity increase, as an induced effect of voice efficiency
- Ex: for Operators w/o 3G and/or LTE
Less TRX to deploy in new networks
GSM re-farming
To recover lost capacity
GSM TRX 1 TRX 3 GSM TRX 1 TRX 2 +
VAMOS
UMTS
- To recover lost capacity
Hot spots, occasional events
MHz MHz
VAMOS: IMPACTS ANDHWCOVERAGE
MS
VAMOS: IMPACTS AND HW COVERAGE
SAIC MS already available;
VAMOS has low MS impacts;
Al t l L t h t di d l ti t th bl d b l Alcatel-Lucent has studied solutions to the problem caused by some poorly
performing SAIC (and possibly some VAMOS Level 1 (as being SAIC based))
mobiles and SAIC mobiles not reporting their SAIC capability;
BSS
Support by Twin TRX and MC-TRX/MC-RRH;
Supported by BSC Evolution;
Pre-requisite: IP transport in BSS;
AMR usage recommended to improve radio quality then VAMOS gains; AMR usage recommended to improve radio quality, then VAMOS gains;
VAMOS: WHY IP IS REQUIRED? VAMOS: WHY IP IS REQUIRED?
VAMOS allows to carry up to 4 calls per radio timeslot
- In TDM, existing mapping between one radio timeslot and one A-bis nibble does not work any more:
16 kbits/s are not enough
A solution may consist in using two 16 kbits/s nibbles
- To avoid doubling the A-bis bandwidth requirements for voice, whereas only a part of the traffic will be
using VAMOS, dynamic allocation of one or two nibbles per radio timeslots (depending on whether
VAMOS is used in this timeslot) would be needed VAMOS is used in this timeslot) would be needed
- This is a complex feature to implement in all network elements, whereas IP transport in the BSS allows
dynamic allocation natively
Alcatel-Lucent understand the significant efforts for its customers to move their transport
layer towards IP
This is why IPoE1 on A bis is offered in B12 This allows customers to keep their A bis unchanged at - This is why IPoE1 on A-bis is offered in B12 - This allows customers to keep their A-bis unchanged at
physical layer
Efficient voice multiplexing allows to compensate IP overheads
h b l h d - With even better results when DTX is activated
IP TRANSPORT BSS: MAIN PRINCIPLES
- A-ter segment: IP over Ethernet
- The BSC, TC and the MFS are connected to an IP network through an Ethernet plug
IP TRANSPORT BSS: MAIN PRINCIPLES
e SC, C a d t e S a e co ected to a et o t oug a t e et pug
- A-bis segment: 2 possible options
- IP over Ethernet
- The BTS is connected to the IP network by an Ethernet plug
- IP over E1
Th BTS i t d t th BSC b E1 b t IP t l l TDM i i l - The BTS remains connected to the BSC by an E1, but IP protocols replace TDM principles
- Mixed mode
- A BSS is able to handle IP BTS and TDMBTS A BSS is able to handle IP BTS and TDM BTS
- Allows for smooth migration to IP and support of BTS/sites that cannot (or are not
whished) to go IP/Ethernet connectivity
TDMli k t A t t th t ffi f th i i TDMBTS - TDM lines are kept on A-ter to convey the traffic of the remaining TDM BTS
Other features
- BTS synchronization through NTP or PTP 1588 IPSEC (option) E1 clock out of BTS for
21
BTS synchronization through NTP or PTP 1588, IPSEC (option), E1 clock out of BTS for
Node B synchronization, IPoEthernet: optical transmission on A-bis
IP TRANSPORT BSS: FULL IP OVER ETHERNET
DSL (copper) DSL (copper)
BTS
Eth
PDH/SDH
IP TRANSPORT BSS: FULL IP OVER ETHERNET
DSLAM DSLAM
Ethernet Microwave
BTS
Eth
TC
Eth
BTS
BTS
IP Backbone
Circuit
Packet
BTS
GPON
(PtMultiP fibre)
Eth
SDH
(PtP fibre)
CS Sig
BTS
BTS
BSC MFS
SGSN
Unified RAN aggregation and Core Ethernet backhaul network
Backhaul costs savings in access and aggregation networks
Simplified network architecture and network operations (e g : Move BTS)
22
Simplified network architecture and network operations (e.g.: Move BTS)
IP TRANSPORT BSS: IPoE1 ON ABIS IP TRANSPORT BSS: IPoE1 ON ABIS
PDH/SDH
E1
PDH/SDHLL
TC
Eth
PDH/SDH
BTS
E1
PDH/SDH LL
IP Backbone
Eth
E1
BTS
BSC
Eth
E1Microwave
BTS
MFS
Eth
SGSN
Ater: Ethernet transport
Ater backhauling costs savings
Unified RAN aggregation & Core
Ethernet backhaul network
Abis: TDM transport
Step by step IP transformation
No impact on BSS TDM access network
Improved BWefficiency
23
Ethernet backhaul network
Improved BW efficiency
IP TRANSPORT BSS: MIXEDMODE
TDM BTS
IP TRANSPORT BSS: MIXED MODE
IPBackbone
h
Ethernet Ethernet
access network access network
BTS
Eth
IPoEthor IPoTDMBTS
TC
I P Backbone
Eth
BTS
E1
PDH/SDH
BSC
Eth
PDH/SDH
E1
MFS
E1
BTS
ALLOWS SMOOTH MIGRATION FROM BSS TDM TO IP BSS
A USER PLANE OVER IP A USER PLANE OVER IP
Main target: Removal of TC from BSS: CAPEX gains
Use TC resources in NGN Core
IP between core and BSC: Transmission costs reduction when BSC remains decentralized
Mixed Mode: in case of no / not enough TC resources in the Core + smoother migration
No transcoding for intra-PLMN calls: Better Voice Quality
TrFO should be easier than TFO in BSS Can be of interest for WB-AMR introduction
Increase number of Ater-PS links (up to 76 E1 between BSC and MFS)
BTS
TC
A TDM
Ater CS (TDM or
BTS
BTS
BSC
GboIP
AsigoIP
BTS
A(UP)oIP- no TC
IP)
UMTSCONVERGENCE NEWNETWORKS/ RENOVATION
MFS
Core IP
Backbone
BTS
BTS
SGSN
25
UMTS CONVERGENCE NEW NETWORKS/ RENOVATION
AGENDA
Part 5 | Conclusion
26
HARDWARE COVERAGE
BSC/MFS EVOLUTION &BSC G2 BSC/MFS EVOLUTION & BSC G2
9130 BSC Evolution
TP STM1-IP needed for A interface over IP (A(UP)oIP) or IP over
E1 transport on Abis;
No upgrade is needed in case of IP over Ethernet transport on Abis pg p
(GigE interfaces are available by default on BSC Evolution).
BSC evolution connected to legacy MFS (MFS 9135) is maintained
at B11 functionality level;
9130 MFS Evolution required for VAMOS and IP BSS;
9120 BSC G2
Supported at B11 level of functionality;
9120 BSC G2
B12 features are not supported (VAMOS, BSS over IP, A(UP)oIP,
MSR);
HARDWARE COVERAGE
MFS BTS TC MFS, BTS, TC
9135 MFS
Supported at B11 level of functionality;
BSC evolution connected to legacy MFS (MFS 9135) is maintained
at B11 functionality level; at B11 functionality level;
9100 BTS
VAMOS supported by Twin TRX and MC modules;
36 TRX per SUM and 4 E1 per SUM supported
ith SUMX d SUMX19
9100 BTS
with SUMX and SUMX19;
b d d d f h
9125 TC
TC STM1-IP board needed in case of IPoE1 or IPoEthernet on
Abis;
In case of A interface over IP (A(UP)oIP), TC is removed from
BSS; BSS;
AGENDA
Part 5 | Conclusion
29
CONCLUSION
B12 RELEASE ADVANTAGES B12 RELEASE ADVANTAGES
Improve TCO with IP and DPVA
Boost network CS & PS capacity
Improve LTE-GSM interworking p g
I t l ffi i Increase spectral efficiency
B12 IMPROVES ALL DIMENSIONS OF THE NETWORK

B12 SW Release Benefits

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

B12 SW Release Benefits

Hochgeladen von

Copyright:

Verfügbare Formate

B12 BSS Release Presentation

Das könnte Ihnen auch gefallen