SOBERANÍA Y MONEDA EN GEORGES BATAILLE
2. LA MONEDA FUERZA EL VALOR
The LTE2291: Support for Carrier Aggregation on CL16A Release feature introduces CRAN support for the LTE2007: Inter-eNodeB Carrier Aggregation feature. The CRAN system is employed to support inter-eNB DL carrier aggregation (CA) for two different, co-located eNBs.
3.6.1 LTE2291 benefits
The LTE2291: Support for Carrier Aggregation on CL16A Release feature provides the following benefit:
• It supports a DL capacity increase via an inter-eNB carrier aggregation (CA) solution as well as a UL capacity increase via CRAN.
3.6.2 LTE2291 functional description
The LTE2291: Support for Carrier Aggregation on CL16A Release feature allows the carrier aggregation between eNBs. The carriers may be of the same or different frequency bands. Since within a CRAN system all UL carriers of a eNB must be the same, and UL and DL carriers are the same within an eNB, no CA pairing is allowed between cells within that system.
The LTE2291: Support for Carrier Aggregation on CL16A Release feature utilizes all CRAN functionalities from the LTE2564: CRAN Evolution CL16A feature with one exception, CA activation does not allow using the 4Tx2Rx MIMO mode in the CRAN system. CA with CRAN uses only CA in DL as two transmitters (2Tx) with associated DL performance.
There are two possible CA configuration scenarios:
Double-sided CRAN system
Two separate CRAN systems exist with different frequencies: f1 and f2. The FSMFs are paired together so that FSMF at f1 frequency is a part of 1st cranID (1st CRAN system), and the other FSMF at f2 frequency is part of 2nd cranID (2nd CRAN system). In a double-sided CRAN system, CA is established between two FSMFs (primary (P) and secondary (S) cells are configured across the pair).
Single-sided CRAN system
One CRAN system exists with the f1 frequency. The FSMFs at f2 frequency might be paired for CA, but FSMFs at f2 frequency are not part of a CRAN system.
FSMFs synchronization
In CRAN, an eNB configured as a sync hub direct forward (SHDF) master, uses GPS or timing over packet (ToP) as a source of timing signal. ToP can be used either in phase or frequency mode. The GPS signal is the recommended source of timing signal. If an eNB is configured as a sync hub master, the interconnected eNBs have to be configured as sync hub slaves and have to use the phase sync mode.
g
Note: The frequency mode on sync hub master is not recommended as it causes restarts of all eNBs in a sync chain when the sync hub master eNB is restarted.The eNBs that are connected in the CA cluster use sync source options supported by the LTE1710: Sync Hub Direct Forward feature. The LTE2291: Support for Carrier
Aggregation on CL16A Release feature's recommendation as a sync source is GPS.
If a Master eNB with ToP in frequency mode synchronization is restarted, all
interconnected eNBs in a synchronization chain might restart autonomously to align to a new synchronization signal from the synchronization Master; hence, ToP in a frequency mode is not recommended.
g
Note: It is required that the btsSyncMode parameter be in a phase synchronization mode setting for SHDF in the LTE2007: Inter-eNodeB Carrier Aggregation feature. This applies to all eNBs which employ theLTE2291: Support for Carrier Aggregation on CL16A Release feature.
3.6.3 LTE2291 system impact
Interdependencies between features
The following features must be activated before activating the LTE2291: Support for Carrier Aggregation on CL16A Release feature:
• LTE2007: Inter-eNB Carrier Aggregation
• LTE1710: Sync Hub Direct Forward
• LTE2564: CRAN Evolution CL16A
The LTE2291: Support for Carrier Aggregation on CL16A Release feature impacts the following features:
• LTE2007: Inter-eNB Carrier Aggregation
The part of this feature which is related to 3CC is not supported in conjunction with the LTE2291: Support for Carrier Aggregation on CL16A Release feature. The LTE2007: Inter-eNB Carrier Aggregation feature provides a deliverable that enables CA operation on the necessary 4 DSP deployment that CRAN uses.
Impact on interfaces
The LTE2291: Support for Carrier Aggregation on CL16A Release feature has no impact on interfaces.
Impact on network management tools
The LTE2291: Support for Carrier Aggregation on CL16A Release feature has no impact on network management tools.
Impact on system performance and capacity
The LTE2291: Support for Carrier Aggregation on CL16A Release feature has no impact
3.6.4 LTE2291 reference data
Requirements
Table 26 LTE2291 hardware and software requirements System Multiradio 10
BTS
Multiradio S4 Flexi Zone Micro BTS
Flexi Zone Access Point
FDD-LTE 16A not supported FL16A not supported not supported not supported
Flexi Zone Controller
OMS UE NetAct MME SAE GW
not supported LTE OMS16 support not required BTS faults and reported alarms
Table 27 BTS faults related to LTE2291
Fault ID Fault name Reported alarms
Alarm ID Alarm name
110014 Optical cable inter-BTS or inter FSP cards too long for CRAN
7651 BASE STATION OPERATION DEGRADED
Measurements and counters
There are no measurements or counters related to the LTE2291: Support for Carrier Aggregation on CL16A Release feature.
Key performance indicators
There are no key performance indicators related to the LTE2291: Support for Carrier Aggregation on CL16A Release feature.
Parameters
Table 28 Existing parameters related to LTE2291
Full name Abbreviated name Managed object Parent structure Activation of downlink
carrier aggregation
actDLCAggr MRBTS/LNBTS –
Activate inter-eNB DL carrier aggregation
actInterEnbDLCAggr MRBTS/LNBTS –
BTS ID of the parent eNB of the cell to be aggregated
lnBtsId MRBTS/LNBTS/LNCE L/CAREL
–
For parameter descriptions, see LTE Radio Access Operating Documentation/
Reference/Parameters.
Sales information
Table 29 LTE2291 sales information
Product structure class License control Activated by default
Basic Software (BSW) – Yes