Instrucción y resolución del procedimiento para la concesión de ayudas a la programación

• LTE568 supports MIMO 4x2 with TM4 for all

Release 8 Cat≥2 UEs, TDD and FDD

• LTE569 supports MIMO 4x4 with TM4 for all

Cat.5 and Cat.8 UEs, only in TDD

LTE1987

• MIMO 4x4 with TM9 for Release≥10, Cat.6 and Cat.7 is supported

• MIMO 4x4 with TM4 for all Cat. 5 and Cat.8 UEs is supported Cat. 5|8 (TM4, TDD only) Legacy UE (2RX) Cat. 6|7 Rel.≥10 (TM9) Cat. 5|8 (TM4) Legacy UE (2RX)

TDD and FDD

• This feature enables configuring carrier aggregation between up to three co-located eNBs extending potential carrier aggregation coverage. Neither performance nor throughput is lost on either eNB. • LTE2007 extends the functionality introduced in LTE2305 Inter-eNB CA feature in FL15A, which only

allowed CA on up to two eNBs and had specific HW requirements.

• The eNBs are connected via serial rapid I/O (SRIO) and a synchronization cable link.

- A dual SRIO connection is supported for three eNBs in one cluster. It requires that the SRIO port be configured on port 4 on the FBBC.

•

The eNBs connected together for the purpose of inter-eNB CA are referred to as a CA

cluster.

• The CA cluster is configured using the Carrier aggregation cluster ID (caClusterId) and Carrier aggregation cluster member ID (caClusterMemberId) parameters.

• One eNB cluster supports:

- up to fifty-four 5/10 MHz cells with a 2RX/2TX configuration or - up to twenty-seven 15/20 MHz cells with a 2RX/2TX configuration or

- up to nine cells with a 4RX/4TX configuration and nine cells with a 2RX/2TX configuration

• The interconnected eNBs are acting as independent eNBs toward the core network, toward other eNBs, and toward iOMS/NetAct.

• The following changes are introduced for the eNB CA cluster management compared to the management of individual eNBs:

- the eNB software versions must be identical across the CA cluster to enable inter-eNB CA

- the Carrier aggregation cluster member ID LNBTS parameter need to be configured for each eNB (change of cluster ID requires restart and must be unique in the network).

- eNB will perform a consistency check with each of its neighbors in the CA cluster. Inter-eNB CA will be enabled for the neighbor that has consistent data. An alarm is raised if inconsistent data is detected.

• Each cell in the eNB CA cluster can act as a primary cell (PCell) or as a secondary cell (SCell). All existing CA band and bandwidth configurations can be applied across the different eNBs. The following additional cell configurations are supported for downlink carrier aggregation:

- 4RX/4TX cell configuration on one component carrier + 2RX/2TX cell configurations with 15/20 MHz cell bandwidth on the other component carriers

- 4RX/4TX cell configurations on two component carriers - 4RX/4TX cell configurations on three component carriers

• Phase synchronization is used via the sync cable between system modules and when 1 PPS is lost the sync hub slave goes into holdover and continues to operate normally. Once the phase error exceeds 5 μs an alarm is raised and the LTE2007 feature is disabled.

• Each cell in the eNB CA cluster can act as a primary cell (PCell) or as a secondary cell (SCell). All existing CA band and bandwidth configurations can be applied across the different eNBs. The following additional cell configurations are supported for downlink carrier aggregation:

- 4RX/4TX cell configuration on one component carrier + 2RX/2TX cell configurations with 15/20 MHz cell bandwidth on the other component carriers

- 4RX/4TX cell configurations on two component carriers - 4RX/4TX cell configurations on three component carriers

• Phase synchronization is used via the sync cable between system modules and when 1 PPS is lost the sync hub slave goes into holdover and continues to operate normally. Once the phase error exceeds 5 μs an alarm is raised and the LTE2007 feature is disabled (~6 hr for FSMF).

- BTS continues to operate and provide service, but inter-eNB CA is not possible. CA between cells in the same eNB is not affected.

• Automatic SCell configuration in NetAct iSON manager is possible for candidate cells across eNBs within a cluster. This was not supported in LTE2305.

• In LTE2305 configurations were limited. Both FSMs in the CA cluster were required to configured with two FBBCs. Also, only 6DSP deployments were allowed. • In LTE2007 we no longer require two

FBBCs, and we allow FBBAs to be used. Mixed DSP deployments are also allowed. At least one FBBC per FSM is required to establish SRIO connections between 3 eNBs.

• The dedicated external SRIO port on FSMF shall be used; in case of 2 SRIO links per system module: port #4 on one FBBC shall be used in addition

- The maximum length of optical cable shall be 25 meters. - Direct SRIO communication shall be supported only (no

switches/active/passive devices on the path). - SFP module shall support at least 5Gb/s.

- The same type of SFP modules shall be used on both ends of optical cable.

• In LTE Radio Resource Control (RRC) and Non-Access Stratum (NAS) messages are transmitted over the air using Signalling Radio Bearers (SRBs)

- RRC messages are used for signalling between the UE and the NB - NAS messages are used for signalling between the UE and the MME

• NAS messages are encapsulated in the RRC messages for the over the air transmission • It is then vital for RRC messages to be correctly received by the UE

• There are three types of SRBs:

- SRB 0 – Common Control Channel (CCCH) logical channel mesages, i.e. RRC Connection Setup

- SRB 1 – Dedicated Control Channel (DCCH) logical channel mesages, i.e. RRC Connection Reconfiguration May include encapsulated NAS messages

- SRB 2 - Dedicated Control Channel (DCCH) logical channel mesages, i.e. DL Information Transfer