Technical Description (TED:BSS) Common

BSS Functional Description

The Multiple CSER management does not change so that it is still possible that a CSER
message of a node Obj contains in the additional info field the change status notification of its childs objects (i.e. CSER TRX:0 out of service; {TRX0/CHAN:0, TRX0/CHAN:1
} out of service for dependency).
The LMT Evolution extends the overload handling (boost modality) considering two
incremental level of redundancy:
Minor Level:

The alarms with Warning severity are discharged from the queue;
Newly Warning alarms are discharged;
No re-alignment is necessary;
A specific message indicates this behavior.

Major Level:

2.2.2

The alarms with Warning, Minor and Major severity are discharged from the queue;
All Change State Notifications are discharged from the queue;
Newly Warning, Minor and Major alarms are discharged from the queue;
Newly Change State Notifications are discharged from the queue;
Running alignments are stopped;
Alignment can be restarted by the user clicking a specific button;
A specific message indicates this behavior.

BCCH Redundancy and TRX Reconfiguration

Three types of application apply to the TRX reconfiguration:
1. BCCH recovery;
2. Concentric cell configuration;
3. TRX Reconfiguration in case of Synthesizer.

2.2.2.1

BCCH Recovery
If the TRX-HW which serves a BCCH TRX (for example the TRX Functional Managed
Object containing the BCCH as a subordinate Functional Managed Object) fails or it is
locked by the user, the BTS autonomously starts a reconfiguration. This reconfiguration
is executed by changing the BTSE internal assignment of the TRX hardware to the TRX
Functional Managed Objects: a TRX-HW of the same cell in the 'enabled' state which is
assigned to a non-BCCH TRX is re-assigned to the BCCH TRX and vice-versa, the
TRX-HW which has just failed is re-assigned to the non-BCCH TRX. As a result of the
'swap', the BCCH TRX is served by a 'working' TRX HW (in the 'enabled' state) and the
non-BCCH TRX is out of service due to its assignment to the failed TRX-HW (in the 'disabled/failed' state) as represented in the Figure 11 and Figure 12 below:

A30808-X3247-M010-6-7618

Id:0900d805800db67d

87

BSS Functional Description

Technical Description (TED:BSS) Common

Functional objects

HW objects

TRX-0
(BCCH TRX)

TRX-HW 0
BTSE internal
assignment

TRX-1
non-(BCCH TRX)

TRX-HW 1

Figure 11

Initial Assignment before BCCH Recovery, Failure of TRX-HW -0

HW objects

TRX-HW 0

Functional objects
BTSE internal
assignment

TRX-HW 1

Figure 12

TRX-0
(BCCH TRX)

TRX-1
non-(BCCH TRX)

Assignment After BCCH Recovery

Remarks:

88

The user shall create at least one SDCCH and - if applied - the SMS cell broadcast
channel (CBCH) on the BCCH TRX. Thus, a reconfiguration of the BCCH TRX
always implies a reconfiguration of at least one SDCCH and the CBCH. In this way
it is assured that all necessary control channel functions are available after any
BCCH recovery.
The reconfiguration procedure does not evaluate the CHAN configuration of the
TRX for selection of the target TRX. For example it does not check whether the nonBCCH-TRX is a pure TCH TRX or whether it also contains SDCCHs.The assignment of the functional TRX objects to the TRX-HW does not change if the
failed/locked TRX-HW is put back to service.
The current assignment of the TRX-HW to the TRX Functional Managed Objects is
managed from the Radio Commander/LMT Evolution user interfaces by get the
values of the TRX-HW 'basic' attributes
BCCH reconfiguration is started as soon as the failure is detected. It can last up to
five seconds, until the BCCH-TRX is in service again. If the conditions for TRX
reconfiguration are not satisfied within this time frame, the TRX reconfiguration is not
executed.
If baseband frequency hopping is configured, hopping is disabled if the failed/locked
TRX-HW is involved in the hopping sequence. This system behavior is independent

Id:0900d805800db67d

A30808-X3247-M010-6-7618

Technical Description (TED:BSS) Common

BSS Functional Description

of the BCCH recovery, for example hopping is disabled if any TRX involved in the
hopping sequence fails or is locked.
If synthesizer frequency hopping is configured, hopping is not disabled if the
failed/locked TRX-HW is involved in the hopping sequence. This system behavior is
independent of the BCCH recovery.

g hTo have an optimal final operational configuration, the number of TRXs in a cell
shall be at least equal to the number of available hardware Carrier Units (CU).
When a cell supports a FlexCU board, the BCCH recovery procedure is different from
the BCCH recovery applied to the other cells. Thermal problem on odd side of the
FlexCU affects the normal behavior of the BCCH recovery procedure.
When a FlexCU board is installed in the cell, the user must not assign the BCCH-TRX to:
1) A FCUTR:2k+1 instances (k=0,1...);
2) A FlexCU which is split across two cells;
3) A FlexCU with a FCUTR instance in disabled.failed.state.
The rules above optimize the BTS rack cooling and minimize the reconfiguration operations.
In case the user assigns a BCCH to a FCUTR that does not fulfill the rules above, a
recovery is accomplished when a correct FCUTR is available.
For example: A cell is configured with two FCUTR and both on the same FlexCU board.
The FCUTR:0, FCUTR:1, FCUTR:2 are assigned to one cell, the FCUTR:3 is assigned
to another cell. The BCCH is assigned to the FCUTR:0 (even instance, its related
FLEXCU is not split across two cells). A fault occurs on the BCCH FCUTR. A recovery
is executed and the BCCH is assigned to the FCUTR:2 (the other even instance in the
cell). In case the FCUTR:0 comes back in service, a new recovery is executed in order
to fulfill the rule 2.

2.2.2.2

TRX Reconfiguration in Concentric Cells

In case of Concentric Cell, the failure or a manual locking of a TRX-HW serving a 'complete area' TRX activates a TRX reconfiguration. In this case, the TRX reconfiguration
changes the BTSE internal assignment to assign the failed TRX-HW to an 'inner area'
TRX. In this way the 'complete area' TRX is available again.
The reconfiguration mechanism is exactly the same as for the BCCH recovery as represented in the Figure 13 and Figure 14 below:

A30808-X3247-M010-6-7618

Id:0900d805800db67d

89