The H3C Unicell base station is an extended indoor distributed wireless access system, featuring simple architecture, ease of deployment, low maintenance, and deep multi-standard coverage. As shown in Figure 1, an H3C extended pico station contains three parts:

· BBU—Baseband processing unit for the extended pico station, providing device management, configuration management, performance monitoring, clock management, signaling processing, baseband resource management, and wireless resource management.

· FSW—Extension unit of the extended pico station. It connects to the BBU or subordinate FSW through fiber and accesses the pRRU through a hybrid copper-fiber cable to provide power.

· pRRU—Radio frequency remote unit for the extended pico station. Support of a pRRU for the LTE and 5G standards depends on its model. A pRRU provides the following features:

¡ The transmit channel receives digital signals from the BBU enhanced Common Public Radio Interface (eCPRI) port, performs digital-to-analog conversion, frequency modulation, and amplification filtering, and then transmits the RF signal through the antenna.

¡ The receive channel captures the RF signal from the antenna, amplifies and filters it, performs frequency modulation, converts it to a digital signal, and then sends it back to the BBU through the eCPRI port.

A pRRU can be connected to the BBU directly or through the FSW to expand the cell scale.

Figure 1 H3C Unicell base station

As shown in Figure 2, in a mobile communication network, the endpoint UE accesses the base station through an air interface, and the base station communicates with the core network through a wired connection. In a dual-mode scenario, the H3C Unicell base station can connect to both EPC and 5GC core networks. It can be used to set up a gNodeB or eNodeB base station, depending on the 5G and LTE capabilities supported by the pRRU.

Figure 2 H3C Unicell base station logic topology

NOTE:

· In site scenarios, a hybrid copper-fiber cable is typically used to interconnect the FSW and pRRU. FSM can not only transmit data through the hybrid copper-fiber cable but also provides power supply to the pRRU.

· In some private network scenarios with a few access points, FSW is optional. You can directly connect pRRU and BBU through a fiber. Because no FSW exists to provide power supply for the pRRU, you must install a PoE injector for the pRRU.

· The local web interface of the BBU can display device networking information. As shown in Figure 3, after site deployment, you can log in to the web interface of the BBU to view the networking information on the Device Networking page. For more information about device networking, see the web-based configuration guide of the device.

Figure 3 Device networking

H3C Unicell base station operations

Logging in to the web interface of the base station

The device supports HTTPS for web access. By default, HTTPS is enabled on the base station, with the following web login settings:

· Management interface IP address: 192.168.101.100/24

· Username: admin

· Password: admin

Procedure for logging in to the web interface of the base station for the first time:

1. As shown in Figure 4, use an Ethernet shielded twisted pair to connect the maintenance endpoint to the management interface on the base station.

Figure 4 Connecting the base station and the maintenance endpoint

2. Configure an IP address for the maintenance endpoint. Make sure that the maintenance endpoint can communicate with 192.168.101.100/24. In this example, the IP address of the maintenance endpoint is 192.168.101.2/24.

3. On the maintenance endpoint, enter the IP address of the management interface in the address bar of a browser, and press Enter to access the local web management interface of the device. The IP address format for accessing the web interface through HTTPS is https://ip-address:443. ip-address represents the IP address of the management interface. 443 is the default port number for HTTPS and can be omitted.

4. When you log in to the web interface for the first time, perform the following tasks:

a. As shown in Figure 5, on the login page, enter the default username and password, and then click Login.

Figure 5 Entering login information

b. Enter the new password as required, and then click Apply.

Figure 6 Changing the password

NOTE:

As a best practice, select the following types of characters for the new password:

· Uppercase letters

· Lowercase letters

· Digits

· Spaces and special characters ~`!@#$%^&*()_+-={}|[]\:”;’<>,./

c. On the login page, enter the username and the new password, and then click Login.

Constructing and deploying base station MML commands

You can construct and deploy Man-Machine Language (MML) commands on the management interface of the base station to perform system management, device management, transmission management, and cell management.

Overview of the base station management interface

NOTE:

The base station webpages might change with software versions. The screenshots in this document are for illustration only.

Figure 7 Overview of the base station management interface

1: MML command tree area	2: Response information or help documentation area for MML commands.
3: MML command input box	4: MML command parameter configuration area

The base station management interface contains the following functional areas:

· MML command tree area: Displays the MML commands supported by the device.

· Response information or help documentation area: Displays response or online help information for MML commands.

· MML command input box: Allows you to deploy one or multiple MML commands.

· MML command parameter configuration area: Allows you to select or configure parameters to construct MML commands for specific purposes.

Key elements on the base station management interface

Table 1 Key elements on the base station management interface

Item	Description
Expand	Display MML commands of all modules.
Collapse	Hide MML commands of all modules.
+	Display MML commands of a specific module.
-	Hide MML commands of a specific module.
Return	Return to the navigation pane.
Response Messages	Display response information of MML commands.
Online Help	Display online help for MML commands.
Clear	Clear response information of MML commands.
Filter commands	Filter MML commands by specific keywords.
History commands	Display MML commands that have been executed before. Use the 《 and 》 buttons to switch between commands.
Fill In Parameters	After adding an MML command in the MML command input box, you can click Fill In Parameters to fill the parameters in the MML command into the parameter configuration area, improving parameter configuration efficiency.
Check Validity	After copying an MML command into the MML command input box, you can click Check Validity to verify the MML command parameters and format. The review result will be displayed in the response information area.
Execute	Execute the MML commands in the MML command input box.

Constructing and deploying MML commands

About MML commands

MML commands are human-machine interaction commands that start with ADD, SET, MOD, RMV, DSP, and LST.

Figure 8 MML command construction

Constructing MML commands

Construct MML commands in the execution area of the corresponding configuration task on the base station management interface. Enter the execution area of the target configuration task and construct MML commands as follows:

1. Log in to the management interface of the base station.

Select Base Station Management from the left navigation pane.

2. Access the execution area of the target configuration task.

You can access the execution area of a configuration task by using either of the following methods:

¡ Click the icon on the navigation pane, and then click the target configuration task on the navigation pane to access its execution area. For example, to add a base station operator, click the icon before Manage gNBs and Manage base station operators in Figure 9 to unfold the navigation bar, then click Add base station operator within the base station carrier management menu item to enter the task execution area for adding a base station carrier.

Figure 9 Accessing the specified configuration task execution area through the command tree

¡ Enter command keywords in the command retrieval box on any management page to access the specified configuration task execution area. For example, as shown in Figure 10, to add a base station operator, enter ADD GNBOPERATOR in a command retrieval box, and then click the suggested ADD GNBOPERATOR to enter the execution area for adding a base station operator.

Figure 10 Accessing the specified configuration task execution area through command retrieval

3. Construct MML commands.

You can construct an MML command by using either of the following methods:

¡ As shown in ② in Figure 11, select or enter the parameter values in the parameter configuration area. After you select or enter the parameter values, the corresponding MML command will appear in the command input box, as shown in ① in Figure 11.

¡ Enter the complete MML command in the command input box, as shown in ① in Figure 11.

Figure 11 Constructing a base station MML command

Deploying MML commands

After constructing an MML command, click Execute below the command input box to deploy the MML command.

You can deploy multiple MML commands in bulk on the management interface. Follow these restrictions and guidelines:

· The command input boxes of all features allow you to deploy one or multiple MML commands in bulk.

· In the current software version, the device can process a maximum of 500 MML commands at a time, with a maximum size of 50KB.

· In the command input box, use # to make a single-line comment for an MML command. The content following # on a line is a comment and will not be executed.

· Place # at the beginning of a line (excluding spaces). Otherwise, the system will consider # an invalid command.

· In the command input box, if the entered command or comment is too long, the system will automatically insert a line feed. In this case, the content after the line feed is still considered part of the current command or comment.

H3C Unicell base station initial configuration preparation

Initial configuration refers to software installation, parameter configuration, and service verification that are performed after hardware installation and debugging at the site. All devices in this guide use factory default settings. In future versions that support custom site deployment, you can complete site deployment by configuring a few settings according to the deployment guide. Details are not shown in this guide.

About initial configuration

Initial configuration includes base station deployment preparation, deployment planning, logging in to the base station web interface, configuring base station features, and service verification.

Figure 12 Service deployment workflow

Base station deployment preparation

Preparing base station software and tools

· Prepare the required base station software based on the software version requirements and compatibility matrix.

· Prepare the required tool software.

· Prepare a local maintenance endpoint (typically a PC) and Ethernet twisted pair cable.

· Install the required tool software on the local maintenance endpoint, and copy the required files such as the base station software package to the endpoint.

The software and tools required for site deployment are shown in Table 2.

Table 2 Software and tools required for site deployment

Item	Description	Function
Base station software	An IPE software package containing BBU, FSW, and pRRU.	Used to upgrade the base station on the BBU webpage, typically in .ipe format.
Tool software	Internet Explorer 10, Firefox 59, Chrome 55, or their later versions	Used to log in to the BBU webpage for base station management and maintenance. · For successful web login, configure the browser to accept first-party cookies (those from the site) and enable active scripts (or JavaScript). The names and configuration methods of the two features might differ in different browsers. · You might fail to access the web interface if the browser is enabled with proxy. You can disable the browser proxy or configure the device's login IP address as a proxy exception. The name and configuration method of this feature might differ in different browsers. · To use Internet Explorer, you must enable the following features: ¡ Run ActiveX controls and plug-ins. ¡ Execute scripts on ActiveX controls marked as safe for scripting. · As a best practice to avoid webpage display errors after software upgrade or downgrade, clear the browser cache before you log in to the web interface.
Tool software	Filezilla Server	· After you install the tool on the local maintenance endpoint, the endpoint can act as an FTP server to transfer device software, configuration files, and log files to base stations. · You can download Filezilla Server on the BBU webpage. For more information about downloading, installing, and configuring Filezilla Server, see "Downloading, installing, and configuring FileZilla Server."
Base station configuration file	Base station parameter planning table/deployment template	You can configure base station parameters by following the planning table.
Base station configuration file	Base station configuration file	You can import a configuration file or copy MML commands from the file and deploy the commands in bulk on the BBU webpage.
Local maintenance endpoint	Laptop or PC	Used to connect the local maintenance endpoint to the BBU's management interface. Then, you can log in to the BBU webpage for local management and maintenance.
Category 6 or above shielded twisted pair cables.

Device installation and cable connection

Device installation

Device installation includes BBU, FSW, and pRRU hardware installation. For more information about BBU, FSW, and pRRU hardware installation, see the corresponding installation guides.

NOTE:

After you install the BBU, FSW, and pRRU hardware, if the base station cannot run correctly, identify whether the installation process was correct. If you cannot resolve the issue, contact Technical Support.

Cable connection

Complete the device cable connection as shown in Figure 13. The diagram is only for illustration. Complete cable connection based on site scenario requirements.

Figure 13 Device cable connection

NOTE:

· Connect the BBU to the FSW and the FSW to the pRRU as planned, ensuring each connects to the correct port. The BBU5200's forward transmission ports are 25GE1/0/1 to 25GE1/0/4.

· The backhaul ports of BBU are XGE1/0/1 and XGE1/0/2, used to connect to upper-layer transmission network equipment or core network. Typically, BBU5200 uses the backhaul port XGE1/0/1. In some dual-mode sites with special requirements, different backhaul ports may be used for 5G and LTE.

· In some dedicated network application scenarios, an FSW may not be necessary, and the pRRU can be directly connected to the BBU's fronthaul port.

Upgrading the base station software

Under normal circumstances, the BBU5200 comes pre-installed with base station business software, allowing users to directly log into the base station's Web page through the management interface for service configuration.

NOTE:

· The system software for FSW and pRRU is packaged within the BBU's system software. Upgrading the BBU software version will also upgrade the software versions of FSW and pRRU in the base station.

· If there is no need to replace the base station software, you can skip this chapter.

Downloading, installing, and configuring FileZilla Server

Overview

The BBU's FTP tool download page offers the third-party FTP tool Filezilla Server for devices, enabling easy file transmission between the device and the local maintenance endpoint. When using FTP tools to transfer files, the local maintenance endpoint serves as the File Transfer Protocol server (FTP server), and the BBU device acts as the FTP client.

The main modules that require the FTP tool on the device's web management include:

· Base station management Module: Use the FTP tool to transfer version files during device upgrades.

· Real-time monitoring Module: Use the FTP tool to transmit real-time monitoring files.

· BBU performance module: Use the FTP tool to transmit performance statistics files.

· Product Log Module: Use the FTP tool to transmit the log file.

Procedure

1. Log in to the BBU webpage, and click Download on the FTP tool downloading page to download the Filezilla Server installation package to the local maintenance endpoint.

Figure 14 FTP Tool Download Diagram

2. Run the Filezilla Server installation file and follow the prompts to complete the software installation.

3. When you open Filezilla Server for the first time, set the host, port, and password. For example, set Host to localhost, Port to 14147, and enter a password. As shown in Figure 15, click Connect after completing the settings to log in to Filezilla Server.

Figure 15 Configuring the host, port, and password

4. Click the icon in the Filezilla Server toolbar to open the Users window.

Figure 16 Users window

5. As shown in Figure 17, on the General tab of the Users window, click Add to add a FTP user. Select the password option and configure the password.

Figure 17 Add FTP server user

Figure 18 Configuring user password

6. As shown in Figure 19, click the Shared folders tab of the Users window, and then click Add to add a shared folder on the FTP server. As shown in Figure 20, select the authorization options under Files and Directories on the right side to authorize the shared folder (it is recommended to select all), and then click OK. The first shared folder added will default as the Home Directory for the FTP server. When adding multiple shared folders, you can also set the target shared folder as the Home Directory by clicking Set as home dir.

Figure 19 Add a shared folder

Figure 20 Set the file and directory properties of Shared Folders

Upgrading the base station software

Network requirements

Upgrade the device using the latest software package bbu5200.ipe, allowing the device to run with the new package.

Figure 21 Network diagram

Procedure

1. Place the latest software package bbu5200.ipe in the Home Directory of the FTP server.

2. Configure the IP address of the local maintenance endpoint according to the network diagram. Specific configuration steps are omitted.

3. Log in to the BBU's Web page through the local maintenance endpoint. For specific operation steps, see "Logging in to the web interface of the base station."

4. View the current BBU software version on the base station system information page.

5. Enter the base station management (SMT) page; specific method not detailed.

6. Download the software package, configure the parameters to match the values in the example, and execute the MML command.

DLD SOFTWAREFTP:IP=192.168.101.24,FTPFileName=bbu5200.ipe,UserName=H3C,Password=********;

Item	Parameter	Example	Description
FTP Server IP Addresses	IP	192.168.101.24	FTP server IP
Software Package Name	FTPFileName	bbu5200.ipe	Package in the Home Directory
FTP server username	UserName	H3C	Enter the username for accessing the FTP server.
File Transfer Protocol server (FTP server) cipher.	Password	12345678	Enter the password for accessing the FTP server.

7. After downloading the software package, save the current configuration.

a. Click the Return in the top right corner of the Station Management (SMT) page to return to the BBU's Web homepage.

b. On the BBU Web homepage, click the icon in the top right corner. Then, in the validation prompt window that appears, click Yes to save your configuration.

8. Return to the base station management page, specific method not detailed.

9. Activate the software, configure the parameters to match the values in the example, and execute the MML command.

ACT SOFTWARE:ActMode=MMLLEAST;

Item	Parameter	Example	Description
Activate mode	ActMode	MMLLEAST	Activate configuration mode by passing MML to minimize settings.

After executing the activation operation, the device will automatically restart to complete the software upgrade.

Verifying the configuration

After restarting the BBU, first clear the browser cache, then log in to the BBU Web page again, and check the upgraded software version on the base station system information page.

Site deployment planning

Base station parameter planning

Introduction to base station parameter planning

When planning parameters, different perspectives may impose various constraints or conditions. By considering these factors comprehensively, you can develop a parameter plan that suits the site's business and operational requirements. A site's parameter configuration is not fixed and will continuously optimize and adjust during operation and maintenance as the running environment and business requirements change.

Base station parameter planning principles

Transmission parameters

1. When planning the transmission parameters, fully consider the existing network schema and avoid unnecessary changes to the original network configuration. Plan the base station IP address reasonably to ensure that each interface on the base station side can communicate normally with the relevant network elements of the core network, reduce network complexity, and adapt the base station to the existing network.

2. Communication between the base station and each element of the core network is based on the IP protocol, so routing must be feasible between the base station and each element of the core network.

3. In practice, the backhaul port on the base station side may be configured with only one IP address or several IP addresses from the same network segment. Ensure that routes to core network elements like AMF, UPF, MME, and SGW are reachable. Therefore, when creating the transmission planning table, some logical interfaces can have the same IP address.

4. In dual-mode application scenarios, consider the transmission configuration between eNodeB and the core network EPC on the same base station. On the BBU5200, configure the IP addresses for eNodeB's S1-C and S1-U interfaces on the BBU5200's backhaul port, which also supports configuring subinterfaces.

5. In some scenarios, eNodeB and gNodeB may need to use different transmission channels. In this case, use two different backhaul ports to connect to different upper-layer network devices or core networks, enabling the transmission of signaling and data for eNodeB and gNodeB.

6. The IPv4 address for the BBU forward port is automatically allocated through a proprietary protocol. During actual networking, the IP address section corresponding to the interface will be allocated to FSW and pRRU devices, which include:

¡ The IP address 192.168.6.1/24 is automatically assigned to 25GE1/0/1.

¡ The IP address 192.168.7.1/24 is automatically assigned to 25GE1/0/2.

¡ The IP address 192.168.8.1/24 is automatically assigned to 25GE1/0/3.

¡ The IP address automatically acquired by 25GE1/0/4 is 192.168.9.1/24.

When setting up an actual network, do not use IP addresses within the 192.168.6.0/24 to 192.168.9.0/24 network segments to avoid anomalies in data forwarding.

7. The management interface MGE1/0/2 comes with a default IP address of 172.16.100.100/24, which is for internal system communication and must not be changed or occupied.

8. The interface GE1/0/1 comes with a default IP address of 10.11.1.130/24.

Global parameters

Global parameters apply to all base stations and users across the network.

From a protocol specification and software implementation perspective, the base station must correctly configure its local parameters based on the core network's global parameters to successfully establish control plane and user plane forwarding channels. Therefore, when planning base station parameters, you must consider the core network configuration. Generally, the main parameters related to the base station and the core network include MCC, MNC, and TAC. These parameters are referenced in multiple configurations on the base station side.

IMPORTANT:

The MCC, MNC, and TAC on the base station side must correspond exactly with the configurations on the core network side; otherwise, cells might be established successfully but users may not be able to access them normally.

Site coverage requirement

When creating a new site, consider the coverage area and the number of FSWs and pRRUs needed. Although the coverage area and the required number of FSWs and pRRUs are determined before device installation, they are also important factors to consider during parameter planning.

The number of FSW and pRRU directly affects the amount of RRU chain rings, device IDs, sectors, and DU cell coverage areas that need to be configured in the BBU. The pRRU model used for cell coverage and its supported frequency bands and points affect the configuration of the cell's radio frequency parameters.

Business performance metrics

Business performance indicators include the number of users that need to be supported within the target coverage area and the upstream and downstream bandwidth. Based on these business metrics, consider the following when actually launching the site:

· Do you need to consolidate multiple pRRUs for radio frequency (RF) to configure a sufficient number of cells.

· Consider the uplink and downlink ratio of each cell to meet the corresponding service bandwidth requirements.

Network requirements

When planning the network, consider whether the base station might interfere with nearby networks or other base stations. Avoid interference by carefully planning the cell section and central frequency point parameters. Additionally, if networking with other base stations within the system, plan co-frequency or different frequency neighboring areas according to the overall network plan and add neighboring relationships.

Parameter Settings

Engineering parameters are critical for base station construction and subsequent network maintenance and optimization. Planning the parameters is also part of the base station setup plan. In the engineering parameters table, the configuration contents required for site activation include various parameters for easy maintenance and management, such as naming of designated base stations and cells.

Site deployment parameter planning tables

Core network parameter planning

The parameters on the core network side are related to the parameters on the downstream base station side, as detailed below:

· MCC: Ensure consistency between the core network and the connected base stations in the configuration.

· MNC: Ensure consistency between the core network and the connected base stations in the configuration.

· The TAC value used by the base station for downlink must be a TAC value already configured in the core network.

· Ensure the NG-U interface IP address is routable between the core network and the base station.

· NG-C interface IP address: Ensure that the route to the NG-C interface IP address is reachable between the core network and the base station.

· Ensure the S1-U interface IP address is routable between the core network and the base station.

· S1-C interface IP address: Ensure the route to the S1-C interface IP address is accessible between the core network and the base station.

· SCTP Port Number: Ensure that the core network and base station can establish an SCTP link properly.

The core network data is shared with the downlink base stations, and the low level core network parameter planning is as follows.

Table 3 5GC parameter planning

Item	Description
MCC	Mobile Country Code
MNC	Mobile Network Code
TAC	Tracking Area Code
N2 (NG-C) interface IP address	IP address of the NG-C (N2) interface of the core network AMF network element
N3 (NG-U) interface IP address	Set the IP address for the N3 (NG-U) interface on the core network UPF element.
SCTP Port Number	Port number for the SCTP link.

Table 4 EPC parameter planning

Item	Description
MCC	Mobile Country Code
MNC	Mobile Network Code
TAC	Tracking Area Code
S1-C interface IP address	Set the IP address for the S1-C interface on the core network MME element.
S1-U interface IP address	For more information about the IP address of the S1-U interface on the core network SGW element.
SCTP Port Number	Use this port number for the SCTP link.

Planning base station transmission parameters

Data transmission between the core network and base stations is based on the IP protocol, aiming to ensure route accessibility for the control and user planes between base stations and the core network. Base station transmission parameter planning includes:

· Plan the backhaul interfaces and subinterfaces used for connecting base stations to the core network.

· Plan the IP address, associated VRF, terminating VLAN, and MTU value for the base station control logical interface.

· Plan the static route from the base station control plane to the core network control plane.

· Plan the IP address, associated VRF, terminating VLAN, and MTU value for the base station user plane logical interface.

· Plan the static route from the base station user plane to the core network user plane.

The low-level base station transmission parameter planning is as follows.

Table 5 gNodeB transmission parameters

Item	Description
Loopback interface and its subinterfaces	BBU connects to the backhaul interface and its subinterface of 5GC. When the control plane and user plane share the same loopback interface, plan the subinterfaces for that loopback interface.
N2 (NG-C) interface IP address	IP address of the base station NG-C (N2) interface
VRF that owns the NG-C (N2) interface	When the control plane and user plane of the base station use the same IP address, isolate them using VRF.
Use the NG-C (N2) interface to terminate a VLAN.	If VLANs are segmented on the transmission equipment, use this control to determine whether control messages carry a VLAN Tag at the VLAN termination.
Set the MTU value for the NG-C (N2) interface.	To avoid discarding fragmented packets, it is recommended that the MTU value of the NG-C (N2) interface matches the MTU value of the transmission equipment interface.
N3 (NG-U) interface IP address	IP address of the base station NG-U (N3) interface
The NG-U (N3) interface belongs to VRF.	When the control plane and user plane of the base station use the same IP address, isolate them using VRF.
VLAN terminated at the NG-U (N3) interface.	If VLANs are segmented on the transmission equipment, you need to control whether the VLAN termination control message carries a VLAN Tag.
Set the MTU value for the NG-U (N3) interface.	To prevent the discard of fragmented packets, set the MTU value of the NG-U (N3) interface to match the MTU value of the transmission equipment interface for persistence.
Gateway Address:	IP addresses of the gateway to the control and user planes of the core network
Static Routing	Static routes to the control plane and user plane of the core network

Table 6 eNodeB transmission parameters

Item	Description
Return interface and its subinterfaces	BBU connects to EPC's backhaul interface and its subinterface. When the control plane and user plane share the same loopback interface, plan the subinterface for that loopback interface.
S1-C Interface IP Address	IP address of the S1-C interface of the base station
VRF that the S1-C interface belongs to	When the control plane and user plane of the base station use the same IP address, isolate them using VRF.
VLAN terminated at the S1-C interface	On the transmission equipment, if a VLAN is partitioned, you need to control whether the control message carries a VLAN Tag through VLAN termination.
MTU value of the S1-C interface	To prevent the discard of fragmented packets, set the MTU value of the S1-C interface to match the MTU value of the transmission equipment interface.
S1-U interface IP address	Base station S1-U interface IP address
S1-U interface associated VRF	When the control plane and user plane of the base station use the same IP address, you can isolate them using VRF.
VLAN terminated at the S1-U interface	Control whether VLAN termination messages carry a VLAN Tag if a VLAN has been segmented.
MTU value of the S1-U interface	To avoid discarding fragmented packets, set the MTU value of the S1-U interface to match the MTU value of the transmission equipment interface.
Gateway Address:	Gateway IP addresses for the control plane and user plane to the core network.
Static Routing	Static routes to the control plane and user plane of the core network.

Base station clock and time parameter planning

In the field of mobile communication, to ensure smooth switchover between base stations and reduce time slot interference, it is necessary for base stations to achieve clock synchronization. When planning, consider the clock working mode, reference clock source, and satellite search mode.

When planning, consider how the base station obtains time information (manually or automatically through NTP) and the time zone of the base station's location, as it needs time information to record alarms and logs.

Table 7 Low-level base station clock and time parameters

Item	Description
Time Zone	The time zone of the base station uses the Greenwich Mean Time format.
Method of Time Acquisition	Set the base station time acquisition method to either NTP or manual configuration, which are currently supported. When obtaining time through NTP, the base station acts as an NTP Client.
Clock operating mode	Specify the operating mode for the base station clock, selecting either manual or automatic source mode based on actual conditions.
Reference clock source	Common clock sources include GNSS, PTP, PTP+SyncE, and 1PPS+TOD, with GNSS being the most frequently used. When the reference clock source is GNSS, you can specify the type of satellite used by the base station through the star-search mode parameter, including GPS, Beidou, and GPS + Beidou.

Internal networking planning

Internal networking refers to the connection methods of base station BBU, FSW, and pRRU, involving RRU chain rings and device IDs. This section uses Figure 3-11 as an example to introduce the general content of internal networking planning. When implementing, you need to configure the corresponding RRU ring and device ID based on the actual internal networking situation.

Figure 22 Internal networking

SlotNum

The H3C Unicell base station uses a distributed schema. You can consider the entire base station as one logic device, with BBU and FSW acting as interface cards in different slots of this logic device. Identify them using SlotNum. Specifically:

· Set the SlotNum for the BBU within the entire base station to 0 as a best practice.

· The SlotNum value range for FSW across the entire base station is 6 to 65535.

RRUChainID

The RRUChainID uniquely identifies the logical connection between two devices within this base station and currently includes four types of RRUChain.

· Connect the RRUChain between the BBU and the FSW. On this logic connection, both the SlotNum and the eCPRIPort are the BBU's SlotNum and the BBU's eCPRIPort, with the SlotNum fixed at 0. The eCPRIPort is the BBU's front transmission port number, with values ranging from 2 to 5.

· Connect the BBU to the pRRU using the RRUChain. On this logic connection, both SlotNum and eCPRIPort are the same as those on the BBU, with SlotNum fixed at 0. The eCPRIPort is the BBU’s forward transmission port number, ranging from 2 to 5.

· Connect the RRUChain between FSW and FSW. On this logic connection, both SlotNum and eCPRIPort are the SlotNum and eCPRIPort of the higher-level FSW. The value range for SlotNum is 6 to 65535. The eCPRIPort is the cascading port number of the FSW, fixed at 2.

· Connect the RRUChain between FSW and pRRU. The SlotNum and eCPRIPort on this logic connection are both the SlotNum and eCPRIPort of the FSW. The SlotNum ranges from 6 to 65535; the eCPRIPort is the forward port number of the FSW, ranging from 3 to 10.

FSWID

The FSWID uniquely identifies the FSW device within this base station, with a value range of 0 to 65535.

RRUID

The RRUID uniquely identifies the pRRU device within this base station, with a value range of 0 to 127.

Base station basic information planning

The basic information of a base station includes its name, carrier, and trace area. The low-level base station information is planned as follows.

Table 8 Basic information planning for gNodeB

Item	Description
logical base stations	LogicGnbId
	GnbIdNumBit
	GnbId
	GnbName
	InterfaceInstanceI ndication
base station operators	OperatorId
	OperatorName
	OperatorType
	Mcc
	Mnc
	LogicGnbId
gNB integrity protection algorithms	PrimaryIntegrityAlgo
	SecondIntegrityAlgo
	ThirdIntegrityAlgo
	FourthIntegrityAlgo
gNB algorithm enabling state	IntraFreqHoAlgoSwitch
	InterFreqHoAlgoSwitch
	DataConfidentialitySwitch
	DataIntegritySwitch
	DataIgnoreIntegrityErrorSwitch
	SliceAdmitSwitch
	VoNrSwitch
	IntraRatMeasRedirectSwitch
	IntraRatBlindRedirectSwitch
	EnableWhiteCellList
	DetectSwitch
	NonDefaultDRBSwitch
	MroInterFreqSwitch
	MroInterRatSwitch
	PduSessionNasOpt
	DataSecurityOptSwitch
	EpsfbFirstSwitch

Table 9 Basic eNB information planning

Item	Description
eNB Basic Information	EnbName
eNB Basic Information	EnbId
eNB base station operator	OperatorId
	OperatorName
	OperatorType
	Mcc
	Mnc

Wireless parameter planning for base stations

The low level wireless parameter planning for the base station is as follows.

Table 10 Wireless parameter planning for gNodeB

Type	Item	Description
CU configuration data	CU cells	LocalCellId
		LogicGnbId
		CellId
		cellBarredInd
DU configuration data	DU cells	NrDuCellId
		PhyCellId
		SubCarrierSpacing
		FreqBand
		DlBw
		DlNrArfcn
		SsbDescMethod
		SsbPeriod
		SsbPositionsInGroup
		SsbPeriodOffset
		SlotAssignmentIndex
		FlexSlotSymbolsCfg
		Special time slot symbol allocation ratio
		PmaxPres
		IntraFreqReselSupInd
		CellReservedForOtherUseInd
		TaOffset
		PowerConfigMode
	logic DU cells	NrDuLogicCellId
		LogicGnbId
		CellId
		Tac
		CellReservedForOpInd
		NrDuCellId
		SibInfoPriority
		RNAC
	logic DU cell operators	NrDuLogicCellId
	logic DU cell operators	OperatorId
	NR DU logical cell slices	NrDuLogicCellId
		OperatorId
		Sst
		Sd
		SliceGroupId
	baseband resources for DU cells	NrDuCellId
		NrDuCellTrpId
		TrunkEcpriCompression
	PRACH parameters for DU cells	NrDuCellId
		PrachCfgIndex
		RootSeqIndex
Extended site deployment configuration	Base station frame offset	TimeOffSet
	slices of CU virtual LAN	Sst
		Sd
		VlanId
	Neighbor Cell	NR Neighbor cells (Adjacent Frequency Points, Neighbor Relations)
	Neighbor Cell	LTE neighboring cells (Adjacent Frequency Points, Neighbor Relations)

Table 11 Wireless parameter planning for eNB

Type	Item	Description
LTE Cell Data	LTE Cell	LocalCellId
		CellId
		PhyCellId
		CellName
		UlCyclicPrefix
		DlCyclicPrefix
		FddTddInd
		FreqBand
		DlEarfcn
		UlBandwidth
		DlBandwidth
		MaxTxPowerCfgInd
		UePowerMaxCfgInd
		CellType
		SupportEmergency
	Cell operator	LocalCellId
		TrackingAreaId
		CellReservedForOp
	Tracking area	TrackingAreaId
		OperatorId
		TrackingAreaCode
	Neighbor Cell	NR Neighbor cells (Adjacent Frequency Points, Neighbor Relations)
	Neighbor Cell	LTE neighboring cells (Adjacent Frequency Points, Neighbor Relations)

H3C Unicell base station initial configuration

Initial configuration network requirements

As shown in Figure 23, to build a new base station, the user needs one BBU, four FSWs, and twenty dual-mode pRRUs based on the survey data to achieve wireless signal coverage. The FSWs use a cascading approach, and the pRRUs support dual-mode operation. To separately cover 5G and LTE signals within a zone while expanding the coverage area, all pRRUs must consolidate carriers into one 5G cell and one LTE cell.

Figure 23 Initial configuration networking

Initial configuration restrictions and guidelines

To configure a base station out-of-the-box, construct and issue base station MML commands. For more information about constructing and issuing base station MML commands from the station management page, see "Constructing and deploying base station MML commands."

gNodeB initial configuration

Configuring the system time and system clock for gNodeB

Overview

System time

The system time is primarily used by the alarm and log modules. The system time is used when the device generates an alarm or log.

System clock

To ensure seamless switchover and reduce time slot interference between base stations, clock synchronization is required on the base stations. A base station maintains a local clock and aligns it with an external clock source.

Configuring the system time

Restrictions and guidelines

The system time can be manually configured or automatically obtained through NTP. In this example, manual configuration is used.

Procedure

# Specify a time zone for the device based on its physical location.

SET TIMEZONE:TimeZone=GMT+0800;

# Configure the device to obtain the system time through manual configuration.

SET TIMESRC:TimeSrc=None;

# Manually configure the system time.

SET TIME:Year=2023,Month=1,Date=13,Hour=10,Minute=42,Second=15;

Configuring the clock source

Restrictions and guidelines

The base station supports the following types of external clock sources:

· GNSS: Global Navigation Satellite System (GNSS) refers to all satellite navigation systems, including GPS, GLONASS, GALILEO, and BDS. The base station communicates with the satellite receiver module to obtain precise location and clock information.

NOTE:

H3C Unicell base station supports the GPS and BDS satellite navigation systems.

· PTP: Use Precision Time Protocol (PTP) messages to transmit frequency and phase information to achieve high-precision time synchronization in conjunction with hardware. With advancements in hardware and software technologies, the precision of PTP can reach tens of nanoseconds or even less.

· 1PPS + TOD: By using 1PPS (1 Pulse per Second) together with TOD (Time of Day), use the rising edge of the pulse as the benchmark to transmit TOD information, achieving high-precision time synchronization.

· PTP+SyncE (Synchronous Ethernet): Combines synchronous Ethernet technology (SyncE) with PTP to achieve synchronous transmission of time and frequency, providing more stable clock frequency and phase, with time precision reaching the nanosecond level.

The manual provides configuration steps for clock sources using commonly used GNSS as an example.

When installing a base station, using a feed line to connect the GPS antenna or Beidou antenna to the base station can cause path delay. To achieve precise time synchronization, you can select to configure the feed line length when setting GNSS.

Procedure

Set the clock operating mode and specify the satellite navigation system.

SET CLKMODE:ClkMode=CLK_MODE_MANUAL,ClkSrc=GNSS;

SET GNSS:GNSSMode=GPS+BDS;

Configuring gNodeB transmission

Restrictions and guidelines

When planning transmission without VLANs or gateways, there's no need to configure subinterfaces, VRF, or static routes. You can now configure one or more IP addresses on the backhaul port for control plane and user plane transmission for gNodeB.

Procedure

Create a subinterface for the interface Ten-GigabitEthernet1/0/1 based on the transmission parameter planning.

ADD SUBIF:IfName=Ten-GigabitEthernet1/0/1.3125,VlanId=3125;

Add an IP address to the subinterface by calculating the mask length based on the given IP address and gateway.

ADD INTERFACEIP:IfName=Ten-GigabitEthernet1/0/1.3125,IpVersion=IPV4,AddrOrigin=PRIMARY_IPADDR,Ip=10.171.125.238,MaskLength=31;

To isolate the user plane from the control plane, configure a separate VRF for the 5G user plane.

ADD VRF:Vrf=5G,UserLabel=5G;

Bind the subinterface Ten-GigabitEthernet1/0/1.3125 to the VRF.

ADD VRFBIND:Vrf=5G,IfName=Ten-GigabitEthernet1/0/1.3125;

# Add the control plane static route of gNodeB to 5GC, where 10.171.125.237 is the next hop IP address for the static route (if there are multiple AMFs, you need to add multiple static routes).

ADD STATICROUTE:IpVersion=IPV4,Ip=10.124.97.130,MaskLength=32,NextHop=10.171.125.237;

Add a user plane static route for gNodeB to 5GC, with 10.171.125.237 as the next hop IP address. If there are multiple UPFs, add multiple static routes.

ADD STATICROUTE:IpVersion=IPV4,Vrf=5G,Ip=0.0.0.0,MaskLength=16,NextHop=10.171.125.237;

Add the SCTP link between the base station and the core network it accesses.

NOTE:

In SCTP multi-homing scenarios, you can directly specify the peer secondary IP address in the ADD SCTP command.

ADD SCTP:SctpId=0,IpVersion=IPV4,HostIpv4=10.171.125.238,PeerIpv4=10.124.97.130,ServerPort=38412,WorkMode=CLIENT;

Add a base station NG-C interface and reference the added SCTP link. When multiple AMFs are present, add multiple NG-C interfaces, each referencing an SCTP link.

ADD NG-C:NgInterfaceId=0,SctpId=0,LogicGnbId=1;

Add a user-plane link between the base station and core network. Since the 5G user plane and control plane share one IP address, pay attention to binding VRF here.

ADD USERPLANEHOSTIP:UserPlaneHostIpId=0,IpVersion=IPV4,LocalIPv4=10.171.125.238,Vrf=5G,VlanId=3125;

Configuring internal networking of gNodeB

Overview

Internal networking refers to the connection methods between base station BBU, FSW, and pRRU, involving RRU chain rings and device IDs.

Procedure

Add RRU chains, including the FSW and the RRU's associated RRUCHAIN.

ADD RRUCHAIN:RRUChainID=1,NetWorking=CHAIN,SlotNum=0,eCPRIPort=2;

ADD RRUCHAIN:RRUChainID=5,NetWorking=CHAIN,SlotNum=61,eCPRIPort=2;

ADD RRUCHAIN:RRUChainID=2,NetWorking=CHAIN,SlotNum=0,eCPRIPort=3;

ADD RRUCHAIN:RRUChainID=6,NetWorking=CHAIN,SlotNum=62,eCPRIPort=2;

ADD RRUCHAIN:RRUChainID=11,NetWorking=CHAIN,SlotNum=61,eCPRIPort=3;

ADD RRUCHAIN:RRUChainID=12,NetWorking=CHAIN,SlotNum=61,eCPRIPort=4;

ADD RRUCHAIN:RRUChainID=13,NetWorking=CHAIN,SlotNum=61,eCPRIPort=5;

ADD RRUCHAIN:RRUChainID=14,NetWorking=CHAIN,SlotNum=61,eCPRIPort=6;

ADD RRUCHAIN:RRUChainID=15,NetWorking=CHAIN,SlotNum=61,eCPRIPort=7;

ADD RRUCHAIN:RRUChainID=51,NetWorking=CHAIN,SlotNum=65,eCPRIPort=3;

ADD RRUCHAIN:RRUChainID=52,NetWorking=CHAIN,SlotNum=65,eCPRIPort=4;

ADD RRUCHAIN:RRUChainID=53,NetWorking=CHAIN,SlotNum=65,eCPRIPort=5;

ADD RRUCHAIN:RRUChainID=54,NetWorking=CHAIN,SlotNum=65,eCPRIPort=6;

ADD RRUCHAIN:RRUChainID=55,NetWorking=CHAIN,SlotNum=65,eCPRIPort=7;

ADD RRUCHAIN:RRUChainID=21,NetWorking=CHAIN,SlotNum=62,eCPRIPort=3;

ADD RRUCHAIN:RRUChainID=22,NetWorking=CHAIN,SlotNum=62,eCPRIPort=4;

ADD RRUCHAIN:RRUChainID=23,NetWorking=CHAIN,SlotNum=62,eCPRIPort=5;

ADD RRUCHAIN:RRUChainID=24,NetWorking=CHAIN,SlotNum=62,eCPRIPort=6;

ADD RRUCHAIN:RRUChainID=25,NetWorking=CHAIN,SlotNum=62,eCPRIPort=7;

ADD RRUCHAIN:RRUChainID=61,NetWorking=CHAIN,SlotNum=66,eCPRIPort=3;

ADD RRUCHAIN:RRUChainID=62,NetWorking=CHAIN,SlotNum=66,eCPRIPort=4;

ADD RRUCHAIN:RRUChainID=63,NetWorking=CHAIN,SlotNum=66,eCPRIPort=5;

ADD RRUCHAIN:RRUChainID=64,NetWorking=CHAIN,SlotNum=66,eCPRIPort=6;

ADD RRUCHAIN:RRUChainID=65,NetWorking=CHAIN,SlotNum=66,eCPRIPort=7;

Add FSWs.

ADD FSW:FSWID=1,SlotNum=61,RRUChainID=1,FSWName=HUB1;

ADD FSW:FSWID=5,SlotNum=65,RRUChainID=5,FSWName=HUB5;

ADD FSW:FSWID=2,SlotNum=62,RRUChainID=2,FSWName=HUB2;

ADD FSW:FSWID=6,SlotNum=66,RRUChainID=6,FSWName=HUB6;

Add RRUs and establish mappings with the associated FSW and its eCPRI interface number using the RRUChainID.

ADD RRU:RRUID=11,RRUChainID=11,RXNum=4,TXNum=4,RRUName=RRU11;

ADD RRU:RRUID=12,RRUChainID=12,RXNum=4,TXNum=4,RRUName=RRU12;

ADD RRU:RRUID=13,RRUChainID=13,RXNum=4,TXNum=4,RRUName=RRU13;

ADD RRU:RRUID=14,RRUChainID=14,RXNum=4,TXNum=4,RRUName=RRU14;

ADD RRU:RRUID=15,RRUChainID=15,RXNum=4,TXNum=4,RRUName=RRU15;

ADD RRU:RRUID=51,RRUChainID=51,RXNum=4,TXNum=4,RRUName=RRU51;

ADD RRU:RRUID=52,RRUChainID=52,RXNum=4,TXNum=4,RRUName=RRU52;

ADD RRU:RRUID=53,RRUChainID=53,RXNum=4,TXNum=4,RRUName=RRU53;

ADD RRU:RRUID=54,RRUChainID=54,RXNum=4,TXNum=4,RRUName=RRU54;

ADD RRU:RRUID=55,RRUChainID=55,RXNum=4,TXNum=4,RRUName=RRU55;

ADD RRU:RRUID=21,RRUChainID=21,RXNum=4,TXNum=4,RRUName=RRU21;

ADD RRU:RRUID=22,RRUChainID=22,RXNum=4,TXNum=4,RRUName=RRU22;

ADD RRU:RRUID=23,RRUChainID=23,RXNum=4,TXNum=4,RRUName=RRU23;

ADD RRU:RRUID=24,RRUChainID=24,RXNum=4,TXNum=4,RRUName=RRU24;

ADD RRU:RRUID=25,RRUChainID=25,RXNum=4,TXNum=4,RRUName=RRU25;

ADD RRU:RRUID=61,RRUChainID=61,RXNum=4,TXNum=4,RRUName=RRU61;

ADD RRU:RRUID=62,RRUChainID=62,RXNum=4,TXNum=4,RRUName=RRU62;

ADD RRU:RRUID=63,RRUChainID=63,RXNum=4,TXNum=4,RRUName=RRU63;

ADD RRU:RRUID=64,RRUChainID=64,RXNum=4,TXNum=4,RRUName=RRU64;

ADD RRU:RRUID=65,RRUChainID=65,RXNum=4,TXNum=4,RRUName=RRU65;

Configuring basic settings for gNodeB

Add a logic base station.

ADD LOGICGNB:LogicGnbId=1,GnbIdNumBit=24,GnbId=6307537,InterfaceInstanceIndication=0,GnbName=H3C-BBU5200-5G;

Add an operator to the base station.

ADD GNBOPERATOR:OperatorId=0,OperatorName=CMCC,OperatorType=PRIMARY_OPERATOR,Mcc=460,Mnc=00,LogicGnbId=1;

Set gNB algorithm enabling state.

SET GNBALGOSWITCH:IntraFreqHoAlgoSwitch=ON,InterFreqHoAlgoSwitch=ON;

Configuring gNodeB wireless features

Add a CU cell.

ADD NRCELL:LocalCellId=1,LogicGnbId=1,CellId=1;

Add a DU cell.

ADD NRDUCELL:NrDuCellId=1,PhyCellId=933,SubCarrierSpacing=30kHz,FreqBand=BAND_41,DlBw=100M,DlNrArfcn=513000,SsbDescMethod=SSB_NARFCN,SsbFreqPos=504990,SsbPeriod=ms10,SlotAssignmentIndex=DDDDDDDSUU,FlexSlotSymbolsCfg=6_4_4_DDDDDDGGGGUUUU;

Add a logic DU cell.

ADD NRDULOGICCELL:NrDuLogicCellId=1,LogicGnbId=1,CellId=1,Tac=1574400,NrDuCellId=1;

Add an operator to the logic DU cell.

ADD NRDULOGICCELLOP:NrDuLogicCellId=1,OperatorId=0;

Add NR DU logical cell slice.

ADD NRDULOGICCELLSLICE:NrDuLogicCellId=1,OperatorId=0,Sst=1,Sd=66051;

Add baseband resources (TRP) to the DU cell.

ADD NRDUCELLTRP:NrDuCellId=1,NrDuCellTrpId=1;

ADD NRDUCELLTRP:NrDuCellId=1,NrDuCellTrpId=5;

Add sectors and specify the radio frequency antenna used by the pRRU for that sector.

ADD SECTOR:SectorId=111,SectorName=Sector111,ANTNum=2,RRUID=11,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=121,SectorName=Sector121,ANTNum=2,RRUID=12,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=131,SectorName=Sector131,ANTNum=2,RRUID=13,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=141,SectorName=Sector141,ANTNum=2,RRUID=14,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=151,SectorName=Sector151,ANTNum=2,RRUID=15,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=511,SectorName=Sector511,ANTNum=2,RRUID=51,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=521,SectorName=Sector521,ANTNum=2,RRUID=52,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=531,SectorName=Sector531,ANTNum=2,RRUID=53,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=541,SectorName=Sector541,ANTNum=2,RRUID=54,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=551,SectorName=Sector551,ANTNum=2,RRUID=55,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=211,SectorName=Sector211,ANTNum=2,RRUID=21,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=221,SectorName=Sector221,ANTNum=2,RRUID=22,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=231,SectorName=Sector231,ANTNum=2,RRUID=23,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=241,SectorName=Sector241,ANTNum=2,RRUID=24,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=251,SectorName=Sector251,ANTNum=2,RRUID=25,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=611,SectorName=Sector611,ANTNum=2,RRUID=61,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=621,SectorName=Sector621,ANTNum=2,RRUID=62,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=631,SectorName=Sector631,ANTNum=2,RRUID=63,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=641,SectorName=Sector641,ANTNum=2,RRUID=64,ANT1PathNum=ROA,ANT2PathNum=ROB;

ADD SECTOR:SectorId=651,SectorName=Sector651,ANTNum=2,RRUID=65,ANT1PathNum=ROA,ANT2PathNum=ROB;

Add DU cell coverage area.

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=1,NrDuCellTrpId=1,SectorId=111;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=2,NrDuCellTrpId=1,SectorId=121;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=3,NrDuCellTrpId=1,SectorId=131;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=4,NrDuCellTrpId=1,SectorId=141;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=5,NrDuCellTrpId=1,SectorId=151;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=8,NrDuCellTrpId=1,SectorId=511;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=9,NrDuCellTrpId=1,SectorId=521;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=10,NrDuCellTrpId=1,SectorId=531;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=11,NrDuCellTrpId=1,SectorId=541;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=12,NrDuCellTrpId=1,SectorId=551;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=15,NrDuCellTrpId=5,SectorId=211;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=16,NrDuCellTrpId=5,SectorId=221;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=17,NrDuCellTrpId=5,SectorId=231;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=18,NrDuCellTrpId=5,SectorId=241;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=19,NrDuCellTrpId=5,SectorId=251;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=22,NrDuCellTrpId=5,SectorId=611;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=23,NrDuCellTrpId=5,SectorId=621;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=24,NrDuCellTrpId=5,SectorId=631;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=25,NrDuCellTrpId=5,SectorId=641;

ADD NRDUCELLCOVERAGE:NrDuCellCoverageId=26,NrDuCellTrpId=5,SectorId=651;

Set the base station frame offset.

SET FRAMEOFFSET:TimeOffSet=2302000;

Activate the cell.

ACT NRCELL:LocalCellId=1;

Adding gNodeB neighbors

Add 5G neighbors to this base station

Configure the co-frequency neighboring cells and adjacent frequency points for this 5G base station (when multiple 5G neighboring areas actually exist, add multiple configurations separately).

ADD NRNEIGHCARRIERFREQ:LocalCellId=1,SsbDescMethod=SSB_NARFCN,SsbFreqPos=504990,FreqBandIndicatorNr=BAND_41;

# Add the 5G external cells of this base station (when multiple 5G neighboring cells actually exist, you need to add multiple configurations separately).

ADD EXTERNALCELL:Mcc=460,Mnc=00,GnbIdNumBit=24,GnbId=205,CellId=1,PhyCellId=131,SsbDescMethod=SSB_NARFCN,SsbFreqPos=504990,Tac=1;

Bind 5G neighboring cells with 5G external cells (when multiple 5G neighboring cells exist, add multiple configurations separately).

ADD NRNEIGHCELL:LocalCellId=1,Mcc=460,Mnc=00,GnbIdNumBit=24,GnbId=205,CellId=1;

Add LTE neighbors for this base station.

Configure the LTE neighboring cells and adjacent frequency points for this base station (add multiple configurations separately when multiple LTE neighboring areas exist).

ADD EUTRA-CARRIERFREQ:LocalCellId=1,CarrierFreq=1350;

Add external LTE cells for this base station (if multiple LTE neighboring areas exist, add multiple configurations separately).

ADD EUTRA-EXTERNALCELL:Mcc=460,Mnc=00,eNodeBId=205,CellId=1,DlEarfcn=1350,PhyCellId=137,Tac=1;

Bind LTE neighboring cells with LTE external cells (add multiple configurations separately when multiple LTE neighboring cells actually exist).

ADD EUTRA-FREQNEIGHCELL:LocalCellId=1,Mcc=460,Mnc=00,eNodeBId=205,CellId=1;

eNodeB initial configuration

Displaying LTE mode

Query the LTE mode to validate whether LTE has started.

LST LTESTARTUP:;

Configuring basic eNodeB settings

Configure the eNodeB name and eNodeB ID.

ADD ENODEB:EnbName=H3C-BBU5200-4G,EnbId=37848;

Add a base station operator.

ADD OPERATOR:OperatorId=0,OperatorName=CMCC,OperatorType=OPERATOR_PRIMARY,Mcc=460,Mnc=00;

Add an eNodeB trace area.

ADD OPERATORTA:TrackingAreaId=01,OperatorId=0,TrackingAreaCode=28978;

Configuring the system time and system clock for eNodeB

eNodeB and gNodeB share the system time and clock. If you have already configured the system time and clock during the initial configuration of gNodeB, you can skip this step. If you haven't configured the system time and clock for gNodeB, see "Configuring the system time and system clock for gNodeB" to complete the configuration.

Configuring eNodeB transmission

Restrictions and guidelines

In transmission planning without VLANs and gateways, there is no need to configure subinterfaces, VRF, or static routes. You can configure one or more IP addresses on the backhaul port for control plane and user plane transmission in eNodeB.

Procedure

Create a subinterface for the interface Ten-GigabitEthernet1/0/1 based on the transmission parameter planning.

ADD SUBIF:IfName=Ten-GigabitEthernet1/0/1.3124,VlanId=3124;

Add an IP address to the subinterface by calculating the mask length based on the given IP address and gateway (GW).

ADD INTERFACEIP:IfName=Ten-GigabitEthernet1/0/1.3124,IpVersion=IPV4,AddrOrigin=PRIMARY_IPADDR,Ip=10.204.125.238,MaskLength=31;

Add eNodeB to the EPC control plane static route, where 10.204.125.237 is the next hop IP address for the static route (if there are multiple MMEs, add multiple static routes).

ADD STATICROUTE:IpVersion=IPV4,Ip=100.79.252.24,MaskLength=32,NextHop=10.204.125.237;

Add the User Plane static route from eNodeB to EPC, where 10.204.125.237 is the next hop IP address for the static route (add multiple static routes when there are multiple SGWs).

ADD STATICROUTE:IpVersion=IPV4,Ip=0.0.0.0,MaskLength=16,NextHop=10.204.125.237;

Add the SCTP link between the base station and the core network it accesses.

NOTE:

In SCTP multi-homing scenarios, specify the peer's secondary IP address directly in the ADD SCTP command.

ADD LTESCTP:SctpId=1,IpVersion=IPV4,HostIPv4=10.204.125.238,PeerIPv4=100.79.252.24,HostPort=36412,PeerPort=36412,WorkMode=client;

Add an S1-C interface to the base station and reference the added SCTP link. When multiple MMEs are present, add several S1-C interfaces, each referencing a different SCTP link.

ADD S1-MME:S1MmeId=1,UserLabel=S1-MME,SctpId=1,MmeRel=rel10;

Add a user-plane link between the base station and the core network.

ADD USERPLANEHOSTIP:UserPlaneHostIpId=1,IpVersion=IPV4,LocalIPv4=10.204.125.238,VlanId=3124;

Add a node group to the transmission link.

ADD EPGROUP:EpGroupId=1,IpVersion=IPV4;

Add the IP address used by the eNodeB user plane to the transmission link endpoint group.

ADD EPGROUPHOSTIP:EpGroupId=1,UserPlaneHostIpId=1;

Bind the S1-C interface to the node group of the transmission link.

ADD S1:S1Id=1,S1InterfaceId=1,UpEpGroupId=1;

Configuring the internal networking of eNodeB

Overview

Internal networking refers to the connection method between base station BBU, FSW, and pRRU, involving RRU chain rings, device IDs, and more.

Restrictions and guidelines

The operations to add RRU ring, FSW, and pRRU have been completed in section 4.3.3 of "Configuring gNodeB Internal Networking."

Configuring eNodeB wireless features

Add baseband resources (TRP) to the eNodeB cell.

ADD CELLTRP:CellTrpId=0,LocalCellId=1;

ADD CELLTRP:CellTrpId=1,LocalCellId=1;

Add sectors and specify the radio frequency antenna for the pRRU used in the sector.

ADD SECTOR:SectorId=112,SectorName=Sector112,ANTNum=2,RRUID=11,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=122,SectorName=Sector122,ANTNum=2,RRUID=12,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=132,SectorName=Sector132,ANTNum=2,RRUID=13,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=142,SectorName=Sector142,ANTNum=2,RRUID=14,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=152,SectorName=Sector152,ANTNum=2,RRUID=15,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=512,SectorName=Sector512,ANTNum=2,RRUID=51,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=522,SectorName=Sector522,ANTNum=2,RRUID=52,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=532,SectorName=Sector532,ANTNum=2,RRUID=53,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=542,SectorName=Sector542,ANTNum=2,RRUID=54,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=552,SectorName=Sector552,ANTNum=2,RRUID=55,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=212,SectorName=Sector212,ANTNum=2,RRUID=21,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=222,SectorName=Sector222,ANTNum=2,RRUID=22,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=232,SectorName=Sector232,ANTNum=2,RRUID=23,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=242,SectorName=Sector242,ANTNum=2,RRUID=24,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=252,SectorName=Sector252,ANTNum=2,RRUID=25,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=612,SectorName=Sector612,ANTNum=2,RRUID=61,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=622,SectorName=Sector622,ANTNum=2,RRUID=62,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=632,SectorName=Sector632,ANTNum=2,RRUID=63,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=642,SectorName=Sector642,ANTNum=2,RRUID=64,ANT1PathNum=ROC,ANT2PathNum=ROD;

ADD SECTOR:SectorId=652,SectorName=Sector652,ANTNum=2,RRUID=65,ANT1PathNum=ROC,ANT2PathNum=ROD;

Add eNodeB cell coverage area.

ADD CELLCOVERAGE:CellCoverageId=1,CellTrpId=0,SectorId=112;

ADD CELLCOVERAGE:CellCoverageId=2,CellTrpId=0,SectorId=122;

ADD CELLCOVERAGE:CellCoverageId=3,CellTrpId=0,SectorId=132;

ADD CELLCOVERAGE:CellCoverageId=4,CellTrpId=0,SectorId=142;

ADD CELLCOVERAGE:CellCoverageId=5,CellTrpId=0,SectorId=152;

ADD CELLCOVERAGE:CellCoverageId=8,CellTrpId=0,SectorId=512;

ADD CELLCOVERAGE:CellCoverageId=9,CellTrpId=0,SectorId=522;

ADD CELLCOVERAGE:CellCoverageId=10,CellTrpId=0,SectorId=532;

ADD CELLCOVERAGE:CellCoverageId=11,CellTrpId=0,SectorId=542;

ADD CELLCOVERAGE:CellCoverageId=12,CellTrpId=0,SectorId=552;

ADD CELLCOVERAGE:CellCoverageId=15,CellTrpId=0,SectorId=212;

ADD CELLCOVERAGE:CellCoverageId=16,CellTrpId=0,SectorId=222;

ADD CELLCOVERAGE:CellCoverageId=17,CellTrpId=0,SectorId=232;

ADD CELLCOVERAGE:CellCoverageId=18,CellTrpId=0,SectorId=242;

ADD CELLCOVERAGE:CellCoverageId=19,CellTrpId=0,SectorId=252;

ADD CELLCOVERAGE:CellCoverageId=22,CellTrpId=0,SectorId=612;

ADD CELLCOVERAGE:CellCoverageId=23,CellTrpId=0,SectorId=622;

ADD CELLCOVERAGE:CellCoverageId=24,CellTrpId=0,SectorId=632;

ADD CELLCOVERAGE:CellCoverageId=25,CellTrpId=0,SectorId=642;

ADD CELLCOVERAGE:CellCoverageId=26,CellTrpId=0,SectorId=652;

Add eNodeB cells.

ADD CELL:LocalCellId=1,CellId=192,PhyCellId=203,FddTddInd=FDD,FreqBand=3,UlEarfcnCfgInd=CFG,UlEarfcn=19350,DlEarfcn=1350,UlBandwidth=CELL_BW_N100,DlBandwidth=CELL_BW_N100,UePowerMaxCfgInd=NOT_CFG;

Add a operator to the eNodeB cell.

ADD CELLOP:LocalCellId=1,TrackingAreaId=0;

Activate the eNodeB cell.

ACT CELL:LocalCellId=1;

Adding eNodeB neighboring cells

Add LTE neighbors to this base station

Configure the adjacent frequency points of this base station's EUTRAN.

ADD EUTRANINTERNFREQ:LocalCellId=1,DlEarfcn=1300;

Add the external LTE cells for this base station (when multiple LTE neighboring areas actually exist, add multiple configurations separately).

ADD EUTRANEXTERNALCELL:Mcc=460,Mnc=00,EnbId=205,CellId=1,DlEarfcn=1300,Tac=1;

Bind LTE neighboring cells and LTE external cells (when multiple LTE neighboring cells exist, add multiple configurations separately).

ADD EUTRANNCELLRELATION:LocalCellId=1,Mcc=460,Mnc=00,EnbId=205,CellId=1,PhyCellId=137;

Add 5G neighbors for this base station.

Configure the 5G neighbors and adjacent frequency points for this base station. Add multiple configurations separately when there are multiple 5G neighbors.

ADD NRNFREQ:LocalCellId=1,SsbDescMethod=SSB_NARFCN,DlArfcn=504990,FreqBand=BAND_41,SubcarrierSpacing=30KHZ;

# Add the 5G external cells of this base station (when multiple 5G external cells actually exist, you need to add multiple configurations separately).

ADD NREXTERNALCELL:Mcc=460,Mnc=00,GnbIdLength=24,GnbId=205,CellId=1,SsbDescMethod=SSB_NARFCN,DlArfcn=204990,PhyCellId=131,Tac=1;

Add 5G neighbors for this base station (if multiple 5G neighbors exist, add multiple configurations separately).

ADD NRNCELLRELATION:LocalCellId=1,Mcc=460,Mnc=00,GnbIdLength=24,GnbId=205,CellId=1;

H3C Unicell base station status check

After correctly completing the setup according to the initial configuration, the base station can establish a logical link with the core network and set up a cell, allowing legitimate users registered on the core network to successfully access the 4G/5G network.

To ensure the base station operates normally after deployment and to promptly detect and repair system faults, it is recommended to complete the following operations in sequence.

Checking the running status

Checking the operating status through the LED

Check the status LED on the BBU

Check the BBU indication light to determine if the BBU is running normally. If there is an alarm, first check whether the device hardware is installed correctly and whether the all-in-one cable of the device is properly connected. Then, process according to the detailed information of the alarm. If you cannot resolve a specific alarm, contact H3C technical support.

Check the status LED on the FSW

Check the FSW LED to determine if the FSW is running normally. If an alarm exists, first check if the device hardware is installed correctly and if the all-in-one cable connections are intact. Then, address the issue based on the detailed alarm information. If you cannot resolve a specific alarm, please contact H3C technical support.

Check the status LED on the pRRU

Check the pRRU LED to determine if the pRRU is running normally. If there is an alarm, first check if the device hardware is installed correctly and if the all-in-one cable connections are intact, then address the issue based on the detailed alarm information. If you cannot clear a specific alarm, contact H3C technical support.

Checking the operating status through the web interface

In addition to the device LEDs, you can also log in to the device's web interface to check its operating state.

As shown in the figure below, check the current state of the BBU device.

Check the FSW profile, product information, running environment, and other details as shown in the figure below.

As shown in the figure below, check the pRRU's profile, product information, and capability information.

Viewing alarms on the web interface

Device alarms can be categorized into hardware driver alarms, cell alarms, interface alarms, clock alarms, FSW alarms, RRU alarms, and alarms at the L3, L2, and L1 layers, among others.

As shown in the figure below, you can view the relevant system alarms on the BBU system information page or click the system alarm menu in the left navigation bar to view them.

H3C Unicell base station service verification

After completing the above operations and eliminating faults that affect the normal establishment of cells in the system, it is recommended to qualify the base station by conducting user access testing and basic data service testing.

User access verification

Select any dot within the target coverage area of the base station for testing.

1. First, insert the SIM card, correctly registered in the 4G/5G core network, into the testing endpoint (usually a mobile phone).

2. Install an application program on the testing endpoint that supports displaying cell information. Validate whether the endpoint detects the signal of the target cell and successfully accesses it.

3. Check if the endpoint signal strength RSRP meets expectations. If the endpoint cannot access the network or the signal is significantly lower than expected, investigate the cell configuration, and SIM card registration information.

It is important to note that when a base station configures both LTE and 5G cells simultaneously, perform the test steps mentioned above in each LTE and 5G cell.

Basic data service verification

After successfully connecting to a 4G/5G cell, test whether the basic uplink and downlink data services are available.

Use the ping, iperf, and other application programs on the endpoint for testing, such as testing the uplink and downlink TCP and UDP services between the endpoint and the application server.

H3C Unicell Base Station Initial Configuration Guide-5W100

H3C Unicell base station operations

Overview of the base station management interface

About MML commands

Constructing MML commands

Device installation

Cable connection

Overview

Procedure

Upgrading the base station software

Network requirements

Procedure

Verifying the configuration

Introduction to base station parameter planning

Base station parameter planning principles

Transmission parameters

Global parameters

Site coverage requirement

Business performance metrics

Network requirements

Parameter Settings

Site deployment parameter planning tables

Core network parameter planning

Planning base station transmission parameters

Base station clock and time parameter planning

Internal networking planning

SlotNum

RRUChainID

FSWID

RRUID

Base station basic information planning

Wireless parameter planning for base stations

gNodeB initial configuration

Overview

System time

System clock

Configuring the system time

Restrictions and guidelines

Procedure

Configuring the clock source

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Overview

Procedure

Add 5G neighbors to this base station

Add LTE neighbors for this base station.

Restrictions and guidelines

Procedure

Overview

Restrictions and guidelines

Configuring eNodeB wireless features

Add LTE neighbors to this base station

Add 5G neighbors for this base station.

Checking the running status

Check the status LED on the BBU

Check the status LED on the FSW

Check the status LED on the pRRU

Checking the operating status through the web interface

H3C Unicell base station service verification

User access verification

Basic data service verification

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us