Escolar Documentos
Profissional Documentos
Cultura Documentos
!"$#%&'()*+,#-
Printed in France
./10243456.73298:/07;<>=?/1.7@A B734.42A CD5FE
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential
and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for
evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information
contained herein, including but not limited to the suitability and performances of the product or its intended
application.
The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate
logo, the NORTEL Globemark, UNIFIED NETWORKS. The information in this document is subject to change
without notice. Nortel Networks assumes no responsibility for errors that might appear in this document.
All other brand and product names are trademarks or registered trademarks of their respective holders.
GIHKJMLONQPQRKSJMTINKHNQUDJMVKWYX6WZ\[
pq-rIs>tQuvrOwppx
ââ-ãOäKåçæDãèééè
ùúüû1ý4þKû1ý4ÿ
1.1. OBJECT ................................................................................................................................... 7
1.2. SCOPE OF THIS DOCUMENT ....................................................................................................... 7
1.3. AUDIENCE FOR THIS DOCUMENT ................................................................................................ 8
!"#%$&'%(*) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) )+
2.1. APPLICABLE DOCUMENTS ......................................................................................................... 8
2.2. REFERENCE DOCUMENTS ......................................................................................................... 8
,-
./0%/12 34&5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 56
3.1. CUSTOMER/SERVICE PROVIDER BENEFITS ................................................................................. 9
3.2. END-USER/SUBSCRIBER BENEFITS ......................................................................................... 9
78
9:;%<=> ?;A@BDC%EF<%G%> H=> ?;I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I IJK
4.1. PRINCIPLE ............................................................................................................................. 10
4.2. PERFORMANCES .................................................................................................................... 10
LM
N OPQRSTU
QVW W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W WXY
5.1. GSM INTERFACES.................................................................................................................. 12
5.1.1 AIR interface ................................................................................................................. 12
5.1.2 a interface ..................................................................................................................... 12
5.1.3 Abis interface ................................................................................................................ 12
5.1.4 Ater interface ................................................................................................................ 16
5.1.5 AGPRS Interface .......................................................................................................... 16
5.1.6 Gb Interface .................................................................................................................. 17
5.2. O&M INTERFACES.................................................................................................................. 18
5.2.1 Local Manager (man Machine Interface)...................................................................... 18
5.2.2 EXTERNal Manager (Q3 interface) .............................................................................. 19
5.2.3 SDO .............................................................................................................................. 19
5.3. TRANSMISSION NETWORK INTERFACES .................................................................................... 19
5.3.1 PCM .............................................................................................................................. 19
5.3.2 Ethernet ........................................................................................................................ 19
5.3.3 X25................................................................................................................................ 19
Z[
\]^`_a\b%cd%e%acfhg g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g gij
6.1. UPGRADES ............................................................................................................................ 20
6.1.1 OMC-R Upgrade........................................................................................................... 20
6.1.2 BSC, TCU & BTS upgrade ........................................................................................... 20
6.2. INSTALLATION AND COMMISSIONING ........................................................................................ 20
6.3. MAINTENANCE ....................................................................................................................... 20
6.4. OPERATION............................................................................................................................ 21
6.5. EXTENSION ............................................................................................................................ 21
6.6. TECHNICAL ASSISTANCE SUPPORT ......................................................................................... 21
%%%
h
7.1. HARDWARE CONSTRAINTS ...................................................................................................... 22
7.2. SPARES CONSTRAINTS ........................................................................................................... 22
7.3. BSS VERSION INTERWORKING ................................................................................................ 22
7.4. NSS INTERWORKING .............................................................................................................. 22
7.5. SGSN INTERWORKING ........................................................................................................... 22
7.6. FUNCTION INTERWORKING ...................................................................................................... 23
7.6.1 Interworking with Edge feature: .................................................................................... 23
7.6.2 Interworking with concentric cell................................................................................... 23
7.7. ENGINEERING RULES .............................................................................................................. 23
& ¡
¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢£¤
8.1. OAMC .................................................................................................................................. 24
8.1.1 OMC-R.......................................................................................................................... 24
8.1.2 PCUOAM ...................................................................................................................... 25
8.1.3 Tools ............................................................................................................................. 25
8.1.4 SWI ............................................................................................................................... 25
8.2. BSC 2G.................................................................................................................................. 25
8.4.1 BCF............................................................................................................................... 25
8.4.2 TRX............................................................................................................................... 26
8.4.3 TIL................................................................................................................................. 27
8.4.4 Test bench .................................................................................................................... 27
8.5. TCU 2G.................................................................................................................................. 27
¥¦
§¨
¨%©%ª¬«® §h¯ °±%²³§±%´´%ªµ ± ¯ °±
²³¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶ ¶·¸
9.1. ABBREVIATIONS ..................................................................................................................... 28
9.2. DEFINITIONS ........................................................................................................................... 29
È É ÊÌËÎÍÐÏÎÑÓÒÕÔÎÖÕÍ×ÊØÑÓË
ÙÚÛÙÚ ÜÞÝàßâáãàä
This document describes the impacts of the introduction of the HePA and of its
differentiation in OMC and TIL.
It refers to the two following RFF:
• 017596: “PR1505 – S8000 / S12000 High Power PA (60 W) Module”,
• 020247: “HPA / PA Network identification”
• 24769: “4 HePA + 8 PA support in one S12000 cabinet”
The HePA is a new BTS power amplifier whose transmit power can get up to 60 Watt
in GMSK modulation (45 Watt in 8PSK).
The HePA is compatible with eDRX.
åæ çâæ èêéëíì|îïëíðòñ|óô èöõëÞé÷øùîúàñ
The version target for the introduction of the HePA is V14.3 BSS system release.
ûüý%þý¬ÿ ý ÿ ÿ ý üý%þ ý
S4000/S2000E-DCU2
S4000/S2000E -DCU4 !
S4000/S2000E-DCU2/DCU4 "
S8000-BCF #
S8000-CBCF $
S12000 %
S2000L/H &
e-cell '
S8002 (
S8006 )
OMC-R *
cXd eZfhg]ikjlfhmnmporqrsutvfhwpjKx
yHzP{z |K}?}\~Pb|KM~VTM XMMa?b
NA
H H M?V?M?MMMKMMa\b
©Xª «Z¬hu¬h®K¯P°K±
benefit loss
Cost ownership (day to day operation, fault management, upgrade,
preventive/curative maintenance....)
Capacity yes
Dimensioning (Connectivity, storage capacity..)
Engineering (coverage, C/I…..) yes
Traffic management (load sharing, compliance with recommendations …..)
Robustness (restart/recovery enhancement…..)
NA
Benefit benefit loss
Voice quality (HO, call handling enhancement …)
Quality Of Service (call drop, availability..)
New services
èXé êKëuìhíuîlïPðñìhòôóöõu÷XøhírùuïûúXîhïüðñì
ýHþPÿþ
The HePA is a new BTS Power Amplifier whose transmit power can get up to 60 W in
GMSK instead of 30 W for the PA and ePA.
This HePA is Edge compatible; the non-Edge TDMA (GMSK) can be transmitted with
up to 60 W; Edge TDMA (8PSK) can be transmitted with an average power of 45 W.
This HePA is compatible with S8000 CBCF and S12000 cabinets (indoor + outdoor)
and can work with eDRX (HePA is not compatible with DRX).
The HePA can be used mixed with PA or ePA thanks to the standard concentric cells
features.
The inner zone contains the PA and the outer zone contains HePA (and only HePA).
Comment: the HePA can be used mixed with (e)PA in a normal cell if its power is
being configured with a value that is compatible with (e)PA (lower than 30 Watt).
HePA can be used mixed with PA in step coupling configurations (see [R1]).
The range of value of the OMC parameter “bsTxPwrMax” (that sets the power of the
TRX) already permits to configure power up to 60 Watt.
The HePA will be differentiated at the OMC from PA and ePA; in the same way the
ePA is differentiated from the PA.
This provides a 3 dB improvement in the downlink performance
As the HePA consumes more power than the (e)PA and because of its thermal
characteristics, the S8000 and S12000 cannot support as many HePA as (e)PA.
For these thermal and power supply reasons, the maximum supported configurations
per cabinet are the following:
• S8000 CBCF indoor and outdoor : 6 HePA or 4 HePA + 2 (e)PA vs 8 (e)PA
• S12000 indoor: 8 HePA or 6 HePA + 3 (e)PA vs 12 (e)PA
• S12000: outdoor: 8 HePA or 6 HePA + 3 (e)PA 12 (e)PA
For step coupling, this specific following configuration is supported too in S12000; but
only with H2D and H4D: HePA are in front of H2D and PA are in front of H4D:
• S12000 indoor: 4 HePA + 8 (e)PA
• S12000 outdoor: 4 HePA + 8 (e)PA (with environmental constraints)
The following tables sum up all the maximum HePA / PA mixed supported
configuration:
5 1
4 2
3 3
2 4
1 5
0 8
H!I:J:J<JLK<M*NPORQ SUT*VWYXRQ M*NPZ
7 1
6 3
5 4
4 5
3 6
2 7
1 8
0 12
4 (*) 8 (*)
(*) these configuration is only available in H2D + H4D configuration with the HePA in front of
H2D and the PA in front of H4D
fhg<i:j:j:jk:l*mPnYo p*q*rtsYuYo l*mPv
If the maximum configuration is exceeded, the TRX(s) whose (H)(e)PA connection has
induced the overrun, can not be configured: it is declared unavailable in the enable
TRX ack message and a new specific “PA configuration exceeded” event, mapped on
the TRX object, is sent to the OMC.
This event is also sent on the TRX of a S8000 CSWM connected to HePA; the TRX is
declared unavailable.
In the same way, if a HePA has been connected to a DRX, this DRX cannot be
configured and is declared unavailable in the enable TRX ack message and a new
specific “HePA not supported” event, mapped on the TRX object, is sent to the OMC.
,
,> ¡£¢¥¤¦§©¨ª¤
5.1.2 A INTERFACE
No modification
The HePA status format is the same that the one of PA and ePA status.
For some BTS configurations with HePA, the status response with hardware config
may be longer that the maximum length of one LAPD message if coded in quartet.
That is the reason why, the di-bit mode must be introduced to support the HePA.
Bit 4 to 7 Bit 0 to 3
¹<º¥»¯¼¾½*¿ ÀÂÁ:Ã
Number of HePA 1 to 24 (S8000)
1 to 36 (S12000)
HePA 02 status HePA 01 status
… …
… …
In the same way, HePA equipment will be taken into account in the new BTS display
message (se [R2]).
(1) Yes if the TRX State has changed, as defined in TRX Correlation Record.
(1) Yes if the TRX State has changed, as defined in TRX Correlation Record.
(1) Yes if the TRX State has changed, as defined in TRX Correlation Record.
(1) Yes if the TRX State has changed, as defined in TRX Correlation Record.
"!#
: PA PSDW
(1) Yes if the TRX State has changed, as defined in TRX Correlation Record.
$% &"'(
: DRX / PA Link Fault
This event is sent when the DRX detects that its PA is out of reach
)* +",-
: PA configuration exceeded
If the number of HePA and (e)PA in the BTS exceeds the supported configurations or
if the HePA is connected to a (e)DRX in a CSWM S8000 BTS (S8000 CSWM
supports 0 HePA !), the following event_report message with the new cause “PA
configuration exceeded” on the DRX or eDRX equipment is sent:
=> ?"@A
: HePA not supported
If the HePA is connected to a DRX, the following event_report message with the new
cause “HePA not supported” on the DRX equipment is sent:
QSRTVUXWYUXWVZ\[^]VWVWVQSR]VW
QSRTVUXWYRWVZ_[^]VWVWVQSR]VW
QSRTVUXWY`[^Z_[^]VWVWVQSR]VW
5.1.6 Gb INTERFACE
No modification
The syntax of the following parameters may be changed until the gate 2.
On hardware status or BTS display request, the display will be enhanced with the
HePA equipment.
SSX^YX XS ¡
Existing alarms that occur on the equipments PA can occur also on HePA equipment.
CODANO 1060 (transient) and 1067 (begin/end) can now accept the new HePA
equipment with its causes wording that are the same that the PA fault causes.
¢X£¤X¥¡¦§V¨¡©
See 5.2.1.
ÌXÍÎXÏ¡ÐÑVÒ¡Ó
No impact.
5.2.3 SDO
SDO has to take into account the new cause values due to the introduction of the new
HePA equipment type and to the new causes “PA configuration exceeded” on the
DRX/eDRX and “HePA not supported” on DRX.
Þrß àrß áâ}ã
ä}åçæè ååéè{ê
äëä^ìáSíîê
â^ïëè{ä}áìâ^ðñã
ò^ìSå
5.3.1 PCM
No modification
5.3.2 ETHERNET
No modification
5.3.3 X25
No modification
The TRX must be locked at the OMC before its PA is being changed.
>? @? ACB%DE#FHG E#B%EIG
Comment: if the HePA is not connected to its TRX, it is seen as a “unknow PA type” in
the status hardware, BTS display, event report and load marking messages.
This identification is needed for the two following functions:
Edge: the HePA is able to transmit Edge frames, like the ePA but unlike the PA. A
HePA must be replaced (for Edge purpose) by a HePA or a ePA.
Concentric cells in mixted (e)PA/HePA configurations: the customer must be able to
identify its HePA from its PA to configure the power level of its two cells. A HePA must
be replaced by a HePA.
In the case of the event “PA configuration exceeded” on a DRX or eDRX, the operator
must be informed that the (H)(e)PA that has to be changed can be the (H)(e)PA of
another DRX that the one that is in fault.
The (e)DRX in fault will then have to be locked and unlocked to be able to be
configured.
This is the same for the DRX in fault because it is connected to a HePA (not
supported).
`a ba c%dHe f#g5hHic%j
The power parameters at the OMC already permit the configuration of HePA power
level.
The operator must be aware that the maximum transmitter power of the Edge TDMA
is 45 Watt instead of 60 W for the non-Edge TDMA.
kl ml n(o pHnHq#r<st%q
No impact
uv uv wHx yz{|y#}%~}5 <| Hw1}%{yx< H%
#w
No impact
The HePA can work with eDRX only (it is not compatible with the DRX ND).
As the HePA has the same size that the standard PA, it can be plugged in S8000
CBCF and S12000 cabinet at the same places that the legacy PA.
So, the HePA has no impact on
The (H)(e)PA can be plugged in at any place in the rack (in respecting the supported
configuration and the (e)DRX compatibility).
The supported configuration and the other hardware constraints on the equipments
apart from the BTS have to be described in the corresponding NTP (see § 6.3).
The OMC-R must support the HePA identification as soon as the BTS supports HePA
because:
- The OMC can’t display a status with hardware config or a BTS display containing
unknown equipments.
- The OMC has to be able to decode the new event report related to the HePA
supported configuration.
- The OMC must support the status response message coded in di-bit.
Ö× Ø× Ù#Ú ÚÁÛÙ#ÜHÝHÞ#ßÁà%ÞáÛÙâ
ÿ
To permit the configuration of a mixed HePA / (e)PA concentric cell, the BTS does not
have to check anymore that the “absolute max power level” sent in the cell
configuration message is supported by all the TRX of the cell.
The BTS still checks that the power sent in the cell modify message is supported by all
the TRX of the cell and that the power sent in the power config message is supported
by the related TRX.
The supported coupling configuration with HePA are the following: duplexeur, TxFilter,
H2D (a new H2D version (new code 1900 NTQA38KA / 38LA) is needed to support
HePA) and H4D.
Because of the attenuation induced by the coupling, the maximum power that can be
configured at OMC is the following:
As a consequence of the interworking with Edge feature (see paragraph 7.6.1), it can
be recommended to configure the BCCH on a TDMA that is configured as a Edge
TDMA too or on a non-Edge TDMA. That will depend on the network configuration.
o Advantages:
Due to the special reuse of BCCH the higher load on traffic has no impact,
moreover as the packet data traffic is mainly downlink.
This seems specialy useful for cells with a small number of DRXs.
o Drawbacks:
The Edge traffic shall be dealt with like the GPRS data traffic: either using the
same radio resources that circuit voice or using separate resources.
Not applicable in cell equipped with only one DRX.
RSTUS V4WYX[Z
8.1.1 OMC-R
The OMC-R has to treat the event report and display hardware related to the HePA
equipment; in the same way it is done for the PA and ePA (feature SV1374).
The event report causes of the HePA are the same that for the PA and ePA.
The OMC-R has to take into account the new causes “PA configuration exceeded” on
DRX and eDRX equipments and “HePA not supported” on DRX equipment (see §
8.4).
The OMC-R must be able to decode a status response message coded in di-bit mode.
The management of the power on the block edge channels has to be modify to be
able to configure a eDRX/HePA in such a channel.
8.1.2 PCUOAM
No impact
8.1.3 TOOLS
monqpsrtrsr
No impact
uovqwsxtysy
No impact
8.1.4 SWI
No impact.
z{ |{ }~B|
No impact.
No impact.
#
8.4.1 BCF
The PA type (legacy PA, ePA or HePA) is sent by the PA/TRX to the BCF during the
TRX-BCF connection stage. The BCF will treat this information and deduce the power
limits of the PA. These power limits are not read in DLU anymore.
There are two reasons why no new DLU is needed to support the HePA:
• The power information given in the DLU are not used anymore by the BCF
(the power information will remain in the DLU although it is not used anymore;
so the DLU won’t have to be modified and re-delivered).
• As the size of the HePA is the same that the size of the PA, there is no
cabling rule modification.
Nortel Networks confidential
To avoid power supply problem that could cause a power shut down or thermal
problem that could damage some BTS equipment because of a too high temperature,
the BTS has to verify that the supported configurations (see § 4.3) are respected and
check that there are not too much HePA or (e)PA in the cabinet.
Every time a TRX connects itself to the BCF, the BCF checks its PA type and verifies,
according to the PA type of the TRX that are already connected, that the configuration
is supported. If not, an event on the corresponding TRX with a new specific cause is
sent to the BSC at the reception of the enable TRX message and the TRX cannot be
configured (the TRX is declared unavailable in the enable TRX ack message).
The S8000 CSWM doesn’t support HePA (in other words, the maximum HePA
configuration supported by the CSWM is equal to 0). So, if a HePA is connected to a
(e)DRX in a S8000 CSWM BTS, this new specific event is sent at the reception of the
enable TRX message of each of these (e)DRX.
This new cause “PA configuration exceeded” on the DRX and eDRX equipments has
to bee taken into account in the POD.
As the HePA is not able to work with a DRX, the BTS has to check that PA type and
TRX type of the TRX are compatible.
Every time a TRX connects itself to the BCF, the BCF checks its PA type and verifies
it is compatible with its TRX type. If not, an event on the corresponding TRX with a
new specific cause is sent to the BSC at the reception of the enable TRX message
and the TRX cannot be configured (the TRX is declared unavailable in the enable TRX
ack message).
This new cause “HePA not supported” on the DRX equipment has to bee taken into
account in the POD.
To permit the configuration of mixed HePA / (e)PA cell, the BCF doesn’t check
anymore that the cell power given during the cell configuration or cell modification
procedure is supported by all the TRX/PA of the cell. This verification is still done
during cell modify procedure (that apply to a cell that has already been configured)
and during power modify procedure (that apply to one TRX only).
If by mistake, the power configured at the OMC is not supported by a TRX ((e)PA
configured in the outer zone of a mixed (e)PA / HePA cell, bad power value configured
for a normal cell, with or without HePA …), the cell config message is accepted by the
BCF but the TRX will not be configured.
8.4.2 TRX
The firmware TX of the eDRX has to be modified to take into account the new power
values sent by the He PA.
8.4.3 TIL
The TIL has to be modified in order to:
No impact.
¶· ¸· ¹º»¼½
No impact.
¾¿ À¿ ÁÂÃÄÅ
No impact.
ÆÇ ÆÇ ÈÉYÉÊÌË
ÍÏÎÑÐsÒÔÓÖÕ ×ÙØÏÚ ÛoÜÔÎÑÎÑÝÞÚßÕÞà
áâÔã äÔå æçäÔâMäÔèçæ6å éMéÔê ë
TML platform N (HW, SW, installation procedure…)
TML BSC2G application N
TML TCU2G application N
TIL RTC application N
TIL COAM application Y TIL COAM will be modified to detect and display
the HePA equipment ; the emission tests will be
modified too
Test bench Y
TML BSC e3 application N
TML TCU e3 application N
ROT N
RACE N
ìoíîðï íMñçñçòÏï íÏî#ó ôÔôMõ ö
CT3100 N
RF / Cell Optimisation Tool
CT5100 N
Network Planning Tool
÷ÙøÔù ú ûMøÔü ú ýÔþÌü ýMýÔù ÿ
Simulators Y Decoding of the HePA event report and hardware
config
SPY N
ePA Edge PA
HePA or HPA :High PA called HePA because of its Edge capability
fhgjijkml
n o
pqkmn l
g
:
- either when an OMC-R release upgrade occurs and the value of a new parameter is
["false"] or ["null"] or [x] in order to ensure the same performance before upgrades (for
example from V10/V11 to V12).
:.
This value is recommended by Nortel Network for new networks roll out before the
optimization. The recommended values take benefit of the performance of Nortel
Network BSS feature.
For installed networks, the value to set depends on the chosen options or rules
defined by the customer.
) `=