RRU Cascading Guideline

Click here to load reader

  • date post

    13-Feb-2016
  • Category

    Documents

  • view

    278
  • download

    41

Embed Size (px)

description

RRU Cascading Guideline

Transcript of RRU Cascading Guideline

  • RRU cascading

    Contents

    1.- Description........................................................................... 2 2.- Requirements ...................................................................... 2 3.- Physical Connection ............................................................ 3 4.- Configuration ....................................................................... 5

  • 1.- Description

    Support for Main Remote RBS configurations with cascaded RRUs is introduced (Optional feature,Support for RRU in Cascaded Configuration, FAJ 121 1459). It is only possible to use RRUW, except for the last RRU in the cascade chain where it is also possible to use RRU22. It will be possible to cascade up to 6 RRUs on one OBIF port. The maximum number of RRUs per OBIF will however still be 6. RRUW/RRUS is required. RRU cascading is a prerequisite to support MIMO with two RRU.

    2.- Requirements

    RRUW need to be installed on the site RBS proper SW (W10) need to be installed prior the RRUW connection RRUW

  • 3.- Physical Connection

    The physical connection depends on the configuration desired for the cascade (see cascade configuration chapter and prerequisites). As a general statement, it can be said that OBIF need to be connected directly to the RRUW and from RRUW using DATA2 SPF the next RRU (RRU22 or RRUW) is connected.

    i.e. RRU cascading with RRUW and RRU22 connected to port A 1.- Connect the OIL from OBIF to RRUW

  • 2.- Connect the OBIF cable to SFP in the RRUW at DATA1

    3.- Insert the SFP into the SFP slot for Data 2. Note, normally the RRU comes from factory with only one SFP for slot DATA1. SFP for DATA2 needs to be provided. For STP purpose, the SFP from OBIF will be reused for this purpose, since with cascading not all ports depending on the configuration chosen will not be used. 4.- Connect from DATA2 slot the RRUW with the other RRU ( cable RPM 253 2788)

  • 4.- Configuration

    Different configuration are supported on the RBS 300, some of them require cascading and other not. As it is shown below the configuration groups AB3, ABC2 and A6 need to have RRU in cascading to be supported, and configuration group All1 does not need RRU cascading. In other to choose the proper configuration, capabitily of sector-carrier configuration need to be checked. (check CPI HW configuration data 83/1551-HRB 105 102/1)

  • 4.1.- Configuration Group Indicates the RU configuration group for a Main Remote RBS. The configuration group specifies the topology of the RUs. Possible values: ALL1 = Max one RU per BU-port. All ports can be used. ALL1_CPRI2 = CPRI2 mode. Max one RU per BU-port. All ports can be used. ABC2 = Two RUs per BU-port. Ports A, B and C can be used. AB3 = Three RUs per BU-port. Ports A and B can be used. A6 = Max 6 RUs per BU-port. Port A can be used. At sector creation the configuration group must be given. It must be the same for all sectors defined
  • 4.3.- configuration example (check CPI HW configuration data 83/1551-HRB 105 102/1)

    RRB 04 (RRUW-RRU22)

    The RRB 04 is used for three different configurations depending on which signals are sent on the interface to the base band:

    One carrier with TX diversity or MIMO 2x2 and 2-way RX diversity per sector. Two carriers with 2-way RX diversity per sector; no TX diversity. Two carriers with TX diversity and 2-way RX diversity per sector.

    LazyConfigurationMIMO.doc

    4.3.- XML configuration files examples

    Cascading_xml_examples.zip

  • 4.4 .- Tips and tricks RRU checking Once the RRU are connected the sw is downloaded from the MU to the RU, this process can take long time (around 20 minutes some cases longer), check using cabx with moshell until the RRUs appeared. It has been seen on the STP, that if a SW level in the is not the correct for RRUW and this one is connected, the RRUW need to be turning off and on otherwise even the RBS is restarted with proper sw the RRUW will not be accessible from the MU. MO checking Once the sector is defined with the new software, the name for opticalinterfacelink MO should change, depends on the SW level, if the From state SW is already change no changes are expected. Before: Equipment=1,SectorAntenna=2,AuxPlugInUnit=RRU-1 >>> reservedBy = Equipment=1,OpticalInterfaceLink=2-DL >>> reservedBy = Equipment=1,OpticalInterfaceLink=2-UL After >>> reservedBy = Equipment=1,OpticalInterfaceLink=2-1-DL >>> reservedBy = Equipment=1,OpticalInterfaceLink=2-1-UL Alarms It is possible that after configuration some alarms appear - TR WRNae68354 Carrier_RxDiversityLost - TR WRNae68710 Carrier_SignalNotReceivedWithinTime As workaround, wait several minutes in order to check if the alarms disappear, if not call uninit/init action on the sector mo, if not restart RBS. If configuration of sectors in the RBS does not fit the definition of utrancell in the RNC these two alarm can be seen depending on the configuration itself, i.e Tx diversity on the RNC but only one TX branch defined in the RBS. Maj Carrier_DualModeNotSupported configuration_or_customizing_error Sector=1,Carrier=1 Maj Carrier_RejectSignalFromHardware message_not_expected Sector=1,Carrier=1

  • If a wrong RRB is chosen according to the HW i.e. RRUW is connected and the RRB02 is chosen (it should be RRB02B) Maj AuxPlugInUnit_NewAuxiliaryUnitDetectedNotCorrespondingToTheDefinedConfiguration unavailable SectorAntenna=1,AuxPlugInUnit=RRU-1