Importancia del uso de las plataformas virtuales en la formación superior para favorecer el cambio de actitud
4. Conclusiones y prospectivas
9.7 Troubleshooting SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
9.1 When to Use CPRI MUX
You can enable the CPRI MUX feature in the following scenarios:
l Sites in which a single-mode base station is to be evolved into a multimode base station and the operator requires that the existing topology of fiber optic cables remain
unchanged to reduce engineering costs
l Sites in which a co-MPT dual-mode or multimode base station is to be deployed and the operator requires that costs of fiber optic cables be reduced
l Sites whose coverage must be ensured through cascaded RF units, such as stadiums, subways, and high-speed railways
9.2 Required Information
The following information must be collected before feature deployment:
l Names of baseband processing units that are to be used in CPRI MUX l Names of RF units that are to be used in CPRI MUX
l Information about optical modules l Planned site capacity
9.3 Planning
RF Planning
N/A
Network Planning
Perform network planning according to 4 CPRI MUX Topologies with BBU3900s Used in the LampSite Solution.
Hardware Planning
When selecting boards and RF units that are to be used in the CPRI MUX feature, you must consider the application scenarios and constraints provided in 3 Dependencies on BBU Boards and RF Units and 4 CPRI MUX Topologies with BBU3900s Used in the
9.4 Deployment
9.4.1 Requirements
Hardware
RF units have been installed. Cables between RF units and BBUs have been connected as required by the CPRI MUX feature. For detailed installation procedures, see the
corresponding Base Station Installation Guide and Site Maintenance Guide of the base stations.
NOTE
If CPRI MUX is to be deployed in a site where a single-mode base station is to be evolved into a multimode base station, the hardware configuration must meet the requirements of CPRI MUX.
Otherwise, replace the hardware.
License
None
9.4.2 Data Preparation
l The following table describes the parameters related to the RRUCHAIN MO for configuring the RHUB chain.
Parameter
Name Parameter ID Remarks Data Source
Topo Type TT Set this parameter to
CHAIN.
Network plan (negotiation not required) Backup Mode BM Set this parameter to
COLD.
Network plan (negotiation not required)
l The following table describes the parameters related to the RHUB MO for configuring the RHUB.
Parameter
Name Parameter ID Remarks Data Source
RHUB Chain No. RCN Set this parameter to the number of the RHUB chain onsite.
Network plan (negotiation not required) SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
Parameter
Name Parameter ID Remarks Data Source
RHUB Position PS This parameter specifies the position of an RHUB on an RHUB chain or ring.
For example, set this parameter to 0 for the first-level RHUB and 1 for the second-level RHUB.
Network plan (negotiation not required)
l The following table describes the parameters related to the RRUCHAIN MO for configuring the pRRU chain.
Parameter
Name Parameter ID Remarks Data Source
Topo Type TT Set this parameter to
CHAIN.
Network plan (negotiation not required) Backup Mode BM Set this parameter to
COLD.
NOTE
This parameter is required only when the RHUBs and pRRUs work in branch chain (single-link) topology.
Network plan (negotiation not required)
l The following table describes the parameters related to the RRU MO for configuring the pRRU.
Parameter
Name Parameter ID Remarks Data Source
RRU Chain No. RCN Set this parameter to the number of the pRRU chain onsite.
Network plan (negotiation not required) RRU Position PS Set this parameter to 0. Network plan
(negotiation not required)
RRU type RT Set this parameter to Network plan
Parameter
Name Parameter ID Remarks Data Source
RF Unit Working Mode
RS l In Branch Chain
(Single-Link) Topology, set this parameter to
UO(UMTS_ONLY), TDL(LTE_TDD), LO(LTE_FDD), or UL(UMTS_LTE).
l In Branch Load Sharing Topology, set this parameter to
CPRI MUX in Separate-MPT Scenarios
Multimode RF units that work in multiple modes must follow the following configuration rules:
l RF units are configured and monitored by each mode.
l RF units working in the same mode must have the same configuration. Otherwise, ALM-26274 Inter-System Board Object Configuration Conflict will be reported.
l Table 9-1 lists parameters that must have the same configuration when CPRI MUX is deployed in separate-MPT scenarios.
Table 9-1 Configuration of common parameters
Parameter Name on the UMTS/LTE Side Parameter ID on the UMTS/LTE Side
Topo Type TT
Cabinet No. CN
Subrack No. SRN
Slot No. SN
RRU Type RT
RRU Work Standard RS
The RHUB/pRRU configuration of the converged party takes effect only after RHUB/pRRUs of the converging party have been configured.
Before activating CPRI MUX, configure the RRUCHAIN MO on the converged party (UMTS or LTE). The key parameters are listed in Table 9-2.
SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
Table 9-2 Parameters to be configured on the converged party Parameter Name Parameter ID Remarks
(Configuration Principle for
Different Scenarios)
Data Source
Access Type AT Set this parameter to
PEERPORT.
Engineering Design Head Cabinet No. HCN Set these parameters to
the cabinet number, subrack number, slot number, and optical port number of the CPRI port on the baseband board of the peer end, respectively.
Engineering Design
Head Subrack No. HSRN Engineering
Design
Head Slot No. HSN Engineering
Design
Head Port No. HPN Engineering
Design
Local Slot No. LSN If a BBU3900 is used,
the slot number for the converged board does not need to be configured. In this case, set this parameter to 255.
If a BBU3910 is used and CPRI MUX works in UMTS/LTE
separate-MPT scenarios, set this parameter to the slot number for the converged board.
Equipment Planning
CPRI MUX in Co-MPT Scenarios
In co-MPT scenarios, if the networking meets the requirements in 4.1.1 Constraints, CPRI MUX is supported by default. Activating this feature does not need software configurations.
9.4.3 Activation
Using MML Commands
Step 1 On the converging party, run the ADD RRUCHAIN command to add an RHUB chain.
Step 2 On the converging party, run the ADD RHUB command to add an RHUB to the RHUB chain.
Step 3 On the converging party, run the ADD RRUCHAIN command to configure the pRRU chain.
Step 4 On the converging party, run the ADD RRU command to add a pRRU to the pRRU chain.
Step 5 On the converged party, run the ADD RRUCHAIN command for UMTS or LTE to add an RHUB chain.
Step 6 On the converged party, run the ADD RHUB command to add an RHUB to the RHUB chain.
Step 7 On the converged party, run the ADD RRUCHAIN command for UMTS or LTE to configure the pRRU chain.
Step 8 On the converged party, run the ADD RRU command for UMTS or LTE to add a pRRU to the pRRU chain.
----End
NOTE
Data configurations must be the same for RRUs on the converging party and converged party. For detailed parameter settings, see Table 9-1. When configuring the parameter AT(UMTS NodeB,LTE FDD eNodeB,LTE TDD eNodeB) in separate-MPT scenarios, set the local port for the converging party and the peer port for the converged party. For details, see Table 9-2.
In separate-MPT scenarios where the CPRI line rate is 9.8 Gbit/s, if the bandwidth compression mode is changed for a cell on a CPRI link, all cells on the CPRI link must be deactivated, reconfigured, and then activated.
Using the CME to Perform Single Configuration
Set parameters on the CME according to the operation sequence in Table 9-3. For instructions on how to perform the CME single configuration, see CME Single Configuration Operation Guide.
Table 9-3 Configuring parameters on the CME
SN MO Parameter Name Parameter ID Notes
1 RRUCHAIN Chain No. RCN Add an RRU
chain on the converging party side.
Topo Type TT
Access Type AT
Head Cabinet No. HCN Head Subrack No. HSRN Head Slot No. HSN SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
SN MO Parameter Name Parameter ID Notes Head Port No. HPN
2 RHUB Cabinet No. CN Add an RHUB
to the RRU chain on the converging party side.
Subrack No. SRN
Slot No. SN
RRU Chain No. RCN
RRU Position PS
RHUB Name RN
3 RRUCHAIN Chain No. RCN Add an RRU
chain on the converging party side.
Topo Type TT
Access Type AT
Head Cabinet No. HCN Head Subrack No. HSRN Head Slot No. HSN Head Port No. HPN
4 RRU Cabinet No. CN Add a pRRU to
the RRU chain on the
converging party side.
Subrack No. SRN
Slot No. SN
RRU Chain No. RCN
RRU Type RT
RF Unit Working Mode
RS
5 RRUCHAIN Chain No. RCN Add an RRU
chain on the converged party side for UMTS/
LTE.
Topo Type TT
Access Type AT
Head Cabinet No. HCN
SN MO Parameter Name Parameter ID Notes
Subrack No. chain on the
converged party side.
SRN
Slot No. SN
RRU Chain No. RCN
RRU Position PS
RHUB Name RN
7 RRUCHAIN Chain No. RCN Add an RRU
chain on the converged party side.
Topo Type TT
Access Type AT
Head Cabinet No. HCN Head Subrack No. HSRN Head Slot No. HSN Head Port No. HPN Local Slot No. LSN
8 RRU Cabinet No. CN Add a pRRU to
the RRU chain on the
converged party side.
Subrack No. SRN
Slot No. SN
RRU Chain No. RCN
RRU Type RT
RF Unit Working Mode
RS
Using the CME to Perform Batch Modification
This feature does not support batch modification using the CME.
9.4.4 Activation Observation
After the configured data is activated, check whether RF unit-related alarms are reported on the Alarm/Event tab page of the RNC LMT, and eNodeB LMT. For details about RF unit-related alarms, see 9.7.1 Related Alarms.
Check whether the status of pRRUs is normal.
l Check whether the status of pRRUs is normal.
– Separate-MPT scenarios SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
On the NodeB LMT or U2000, run the DSP BRD command to check whether RF units function properly.
On the eNodeB LMT or U2000, run the DSP BRD command to check whether RF units function properly.
– Co-MPT scenarios
On the BTS3900 LMT or U2000, run the DSP BRD command to check whether RF units function properly.
l Check whether the line rate of the converging port is the same as planned.
– Separate-MPT scenarios
On the LMT or U2000 of the converging party of a 3900 series base station, run the DSP CPRIPORT command to check whether the line rate of the converging port is the same as planned.
– Co-MPT scenarios
Run the DSP CPRIPORT command to check whether the line rate of the converging port is the same as planned.
9.4.5 Deactivation
This feature does not need to be deactivated.
9.4.6 Reconfiguration
Reconfiguration in the UL dual-mode branch chain (single-link) topology and UL dual-mode branch load sharing topology includes the following operations:
l Adding an RHUB to an RHUB chain l Adding a pRRU to an RHUB
l Removing an RHUB from an RHUB chain l Removing a pRRU from an RHUB
For details about these operations, navigate to Engineering Guidelines (NodeB) >
Deployment > Reconfiguration or Engineering Guidelines (eNodeB) > Deployment >
Reconfiguration in RF Unit and Topology Management Feature Parameter Description.
9.5 Performance Monitoring
N/A
9.7.1 Related Alarms
Table 9-4 lists alarms related to the CPRI MUX feature. For detailed troubleshooting operations, see 3900 Series Multimode Base Station Alarm Reference.
Table 9-4 CPRI MUX-related alarms
Alarm ID Alarm Name Description
ALM-26215 Inter-Board Service Link Failure
This alarm is reported if inter-board communication fails in the BBU. Services of the converged party are affected.
ALM-26235 RF Unit Maintenance Link Failure
This alarm is reported if the maintenance link between the BBU and the RF unit malfunctions.
The alarm is triggered by any of the following faults and is reported by the converged party in separate-MPT scenarios:
l Optical modules on the baseband board of the converging party become faulty.
l Links used to forward data from the converged party to the converging party through the BBU backplane become faulty or resources are
insufficient.
l The baseband board of the converging party is not installed, powered on, configured or the baseband board experiences hardware failures.
l The hardware capability of the baseband boards of the two parties is insufficient to support data converging through the BBU backplane.
l Aggregation relationships are incorrectly configured.
SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
Alarm ID Alarm Name Description
ALM-26270 Inter-System
Communication Failure
In multi-mode
configuration, this alarm is reported if the main control board in the current mode cannot communicate with the main control board in the other mode. If the two main control boards cannot communicate with each other for about 45s, this alarm is reported. If the two main control boards can communicate with each other for about 30s
consecutively, this alarm is cleared.
ALM-26272 Inter-System RF Unit
Parameter Settings Conflict
In multi-mode
configuration, this alarm is reported if the parameter settings of an RF unit in a mode are inconsistent with those of the same RF unit in the other mode, such as the working mode or other RF parameters.
ALM-26274 Inter-System Board Object Configuration Conflict
In multi-mode
configuration, this alarm is reported if the cabinet/
subrack/slot configuration of a board is inconsistent in different modes, the cabinet/
subrack/slot configuration of different boards is the same in different modes, or a board that supports only one mode is used by multiple modes at the same time.
ALM-26277 Inter-System Control Rights Conflict
In multi-mode
configuration, this alarm is
Alarm ID Alarm Name Description
ALM-26278 RF Unit Working Mode and
Board Capability Mismatch
In multi-mode
configuration, this alarm is reported if the configured working mode of an RF unit does not match the actual capability of the RF unit.
ALM-28203 Local Cell Unusable When CPRI MUX is
implemented, multiple modes use one CPRI link to transmit data. As a result, bandwidth on the UMTS side may be insufficient and this alarm is reported.
ALM-28206 Local Cell Capability
Decline
ALM-29240 Cell Unavailable When CPRI MUX is
implemented, multiple modes use one CPRI link to transmit data. As a result, bandwidth on the LTE side may be insufficient and this alarm is reported.
ALM-29243 Cell Capability Degraded
NOTE
In separate-MPT scenarios, if a UMTS cell fails to be activated and EVT-28200 Iub Common Procedure Failure Indication is reported, check whether the UMTS+LTE cell configurations exceed the
specifications of a single Ethernet cable. If so, modify the UMTS+LTE cell configurations. If not, run the BLK CPRIPORT command to block the CPRI_E port and then the UBL CPRIPORT command to unblock the CPRI_E port.
9.7.2 MML Commands for Maintenance
In separate-MPT scenarios, the converging and converged parties have their own O&M platforms. In co-MPT scenarios, the converging and converged parties share the same O&M platform. Table 9-5 lists MML commands for maintenance.
NOTE
After CPRI MUX is implemented, alarms will be reported if any exceptions occur. Clear the alarms according to the alarm reference.
SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
Table 9-5 MML commands for maintenance MML
Command Application Scenario Support by the Converging Party
Support by the Converged Party (Only in Separate-MPT Scenarios) DSP
RRUCHAIN
Use this command to query:
l Number of pRRUs/
RHUBs carried on an RRU chain or ring over an optical port on the converging party l Number of RHUB
cascading levels.
Fully supported Fully supported
DSP
RRUCHAINPH YTOPO
Use this command to query information about the pRRUs/RHUBs connected to the CPRI port.
Fully supported Fully supported
DSP
CPRIPORT
Use this command to query:
l Real-time data rates and other information about the optical port on the panel of the converging party l Whether the optical
port is in the aggregation state
Fully supported Partially supported:
Use this command to query:
l Data rates on the CPRI port l Aggregation state
DSP CPRILBR Use this command to query:
l Current CPRI line rate of the specified chain or ring
l Maximum CPRI line rate of the baseband processing board l Maximum CPRI line
Fully supported Partially supported:
Use this command to query the line rate on the head and the end of the CPRI chain or ring. Other
information is displayed as NULL.
MML
Command Application Scenario Support by the Converging Party
Support by the Converged Party (Only in Separate-MPT Scenarios) STR
CPRILBRNEG
Use this command to start negotiation of the line rate on the optical port on the panel. Run this command if the RHUB chain cannot be set up or the chain cannot operate at the maximum line rate due to changes in parameter settings of the RHUB chain. Executing this command causes link disconnection,
interrupting services.
Supported Not supported
MOD RRUCHAIN
Use this command to set breakpoints on an RHUB chain.
Supported Not supported
L: DSP CELL U: DSP ULOCELL
Use this command to query the cell status. Cell setup fails and cell capability degrades when CPRI bandwidth is insufficient.
Supported Supported SingleRAN
CPRI MUX (LampSite) Feature Parameter Description 9 Engineering Guidelines
10 Reference Documents
1. 3900 Series Base Station Technical Description 2. 3900 Series Multimode Base Station Alarm Reference 3. 3900 series base station installation guide package 4. NodeB MML Command Reference
5. eNodeB MML Command Reference 6. RF Unit and Topology Management
7. 3900 series base station site maintenance guide package