Initial Data Templates

MBTS GUL V100R015C10 Initial Data Configuration based on CME
Confidential Information of Huawei. No Spreading Without Permission





 Base station template

 At least one template is defined for each base station model. For example, one
template for the BTS3900 and another for the BTS5900.
 Cell template
 At least one template is defined for each cell type. For example, on the UMTS
network, one template for the R99 cell and another for the HSDPA service cell.
 Radio template
 On the LTE network for example, one template is defined for FDD services
and multiple templates are defined for TDD services based on "Subframe
Assignment" of cells. The CME provides one template for the GSM or UMTS
network by default.
 From SRAN8.0 onwards, the following three types of templates are prepared for all
types of NEs excluding GBTSs: base station template, cell template, and radio
template. Managed in hierarchical mode, these types of templates are independent
from each other and do not have overlapped objects.
 Note: CME also include External Cell Template and Neighboring Cell Template
 External Cell Template includes all parameters of the external cell.
 Neighboring Cell Template includes all parameters of neighboring cells.




 Choose Advanced > Template Management (CME client mode) or CME >
Advanced > Template Management (U2020 client mode) on the menu bar. The
Template Management window is displayed.
 In the template navigation tree, select a template type. All default and user-defined
templates of this type are displayed in the right pane.
 Double-click a template to view detailed parameters in the template.
 A default template applies to the live network where no base station is
deployed. You can configure basic data of a base station by using a default
template and then manually modify the data. If the name of the default base
station template does not contain BBU information, the BBU is BBU3900 by
default.
 A user-defined template applies to the live network where a base station has
been deployed. After you confirm that the base station data is typical and can
be applied to other base stations, you can save the base station data in a user-
defined template.

 In the base station list in the left pane of the planned data area, right-click a co-MPT
multimode base station whose data you want to save as a template and choose Save
as Node Template from the shortcut menu.

 In the base station list in the left pane of the planned data area, right-click a Function
whose data you want to save as a template and choose Save as GSM Radio
Template, Save as UMTS Radio Template, or Save as LTE Radio Template from
the shortcut menu.

 In the base station list in the left pane of the planned data area, right-click a co-MPT
multimode base station and choose Carrier Resource Management from the
shortcut menu. The Carrier Resource Management window is displayed.
 Right-click a cell in the Carrier Resource Management window and choose one of
the following shortcut menus based on the RAT for the cell:
 For a GSM or UMTS cell, choose Save as Local Cell Template from the
shortcut menu.
 For an LTE cell, choose Save as Cell Template from the shortcut menu.

 Exporting templates for other users to import

 Choose Advanced > Template Management (CME client mode) or CME >
Advanced > Template Management (U2020 client mode) on the menu bar.
The Template Management window is displayed.
 Select a type of template to be exported from the left pane. The right pane
displays information about the selected template type.
 In the Custom Template area, select one or more templates and click .A
dialog box is displayed for you to specify a folder for saving the templates.
 Specify a folder for saving the templates, set template names, and click Save.
The CME starts to export the templates.
 When a dialog box is displayed indicating that the export is successful, click
OK.

 Import templates exported from other CMEs into the current CME.
 Choose Advanced > Template Management (CME client mode) or CME >
Advanced > Template Management (U2020 client mode) on the menu bar.
The Template Management window is displayed.
 Select a type of template to be imported from the left pane. The right pane
displays information about the selected template type.
 Click . A dialog box is displayed for you to select files.
 Select one or more data files to be imported.
 Click Open. The CME starts the import.
 (Optional) Type the name, group, and description of the imported template.
 Click OK.




 For details about configuring the Basic Data, see Practice Guide Documentation.

 On the menu bar of the planned data area, choose CME > SRAN Application >
Create Base Station (U2020 client mode) or SRAN Application > MBTS
Application > Create Base Station (CME client mode). A dialog box is displayed for
you to create base stations.
 Configure basic NE information.
 Select a product type of the base station from the Product type drop-down list.
The naming convention of a product type is base station model. A base station
has many models, such as BTS3900, DBS3900, BTS3900A, BTS3900AL,
BTS5900, DBS5900, and BTS5900A.
 Set NE information, including version, and template, and turn on the switch of
each RAT.
 Set Working Mode of the NE.
 If two or more RATs are enabled for a co-MPT base station, the
parameter can be set only to ConCurrent.
 If only one RAT is enabled for a co-MPT base station, the parameter
can be set to ConCurrent or Non-ConCurrent. The value of the
parameter depends on whether the co-MPT base station and other co-
MPT base station are bound as a separate-MPT base station. When
two co-MPT base stations are bound as a separate-MPT base station,
the deployment type for only one NE can be set to ConCurrent.
 After the configuration is complete, click Next.

 Configure information about the co-MPT base station, including each RAT name and
the radio template.After the configuration is complete, click Next. The CME starts to
create a base station.
 NOTE:
 When you specify the GSM Function and UMTS Function and select a base
station controller to which the base station belongs, the CME automatically
creates the corresponding logical base station under the controller. To
facilitate operations, you are advised to select a controller to which the base
station belongs.

 After the base station is created, an option Open the work flow for created base
stations after closing the wizard is displayed for you to select. Select it and click
Finish. The base station workflow window is displayed. The workflow provides
guidance for beginners to configure other base station device, transport, and radio
data.
 Click Finish to exit the wizard. The created co-MPT base station is displayed in the
base station list in the left pane of the planned data area.



 Note for LTE RAT
Name Note Configuration

TA List One TA list contains 16 TAI at most MME
TAI PLMN+TAC MME & eNodeB
30 to 50 sites is recommended as the same
TAC eNodeB
configuration

 For details about configuring the Device Data, see Practice Guide Documentation.

 In the left pane of the planned data area, right-click a physical based station and
choose Device Panel from the shortcut menu. The device panel is displayed in the
right pane. Procedure for configuring device data for a co-MPT base station as follows

 Configuring Device Data for slot distribution
Board Name Mandatory Maximum Quantity Slot Assignment Sequence (the

Leftmost Slot Has the Highest Priority)
UMPT_G*U*L Yes 2 Slot 7 Slot 6 - - -
UTRPc No 1 Slot 4 Slot 5 Slot 0 Slot 1 -
USCUb22 No 1 Slot 5 Slot 1 - - -
• USCUb14 No 1 Slot 5 Slot 4 Slot 1 Slot 0 -
• USCUb11
UBBP_G*U*L No 2 Slot 3 Slot 2 - - -
• UBRIb No 2 Slot 1 Slot 0 - - -
• UBRI
UBBP_G No 2 Slot 1 Slot 2 Slot 0 Slot 4 Slot 5
• UBBP_U Yes 5 Slot 3 Slot 0 Slot 1 Slot 4 Slot 5
• WBBPf
• WBBPd
• WBBPb
• WBBPa
• UBBP_L Yes 5 Slot 2 Slot 0 Slot 1 Slot 4 Slot 5
• LBBPc
• LBBPd

 Configure an RRUCHAIN MO to add an RRU chain or ring

 For LampSite, the RRU chain or ring is between an RHUB and a pRRU in
indoor scenarios, and between an RHUB and an RRU (RRU3230E and
RRU3930E only) in outdoor scenarios,
 In macro base station scenarios, the RRU chain or ring is added between the
BBU and RRUs/RFUs.
 In RMU/AAU scenarios, the RRU chain or ring is added between the BBU and
the RMU. Set Topo Type to TRUNK_CHAIN.

 Frequency synchronization: Two signals have the same number of pulses in the same
interval. The sequence, start time, and end time of each pulse can be different for the
two signals.
 Time synchronization: Two signals have the same frequency, phase, and pulse
sequence.

 For details about configuring the Transport Data, see Practice Guide Documentation.


 A co-MPT base station can work in any of the following modes: GO, UO, LO, GU, GL,
UL, and GUL. Any "L" refers to LTE FDD, LTE TDD, LTE NB-IoT, LTE FDD+LTE
TDD, LTE FDD+LTE NB-IoT, or LTE FDD+LTE TDD+LTE NB-IoT. The transmission
data for a co-MPT base station includes the common transmission data and the
transmission data dedicated to a specific mode.
 Common transport data needs to be configured for each mode based on the
data plan, and the data configuration operations are similar for each mode. To
deploy GSM services in the base station, you need to configure transport data
on the Abis interface. To enable the base station to process UMTS services,
you need to configure transport data on the Iub interface. To deploy LTE
services in the base station, you need to configure transport data on the S1
and X2 interfaces. If it is planned that certain common transport data is shared
among all the modes (for example, OM IP address and port attributes), the
common transport data needs to be configured only once.
 Transport data dedicated to a specific mode needs to be configured for the
mode only. For example, for the LTE mode of a co-MPT base station, only the
LTE-specific transport data needs to be configured, and GSM- and UMTS-
specific transport data does not need to be configured.

 Recommended Scenario as Link mode:

 For the Abis interface, it is recommended the link mode be used to configure
transport data on the base station side.
 Except for the scenarios where endpoint mode applies, it is recommended that
transport data on the base station side in other scenarios be configured in link
mode.
 Recommended Scenario as Endpoint mode:
 For the S1 and X2 interfaces, it is recommended the end point mode be used
to configure transport data on the base station side.
 For the Se interface, the end point mode must be used to configure the
transport data on the base station side for connecting the base station to the
eCoordinator.
 For the Iub interface, if the Iub transmission resource pool feature is enabled
on the RNC side, it is recommended that transport data on the base station
side be configured in end point mode.


 The UMPT board shared by the Abis and Iub interfaces is responsible for protocol
processing at the physical layer, data link layer, network layer (IP), Stream Control
Transmission Protocol(SCTP) and transport link layer (UDP). The protocols at other
layers are processed on the control plane processing boards and user plane
processing boards of GSM, UMTS and LTE separately.
 A Control Port (CP) bearer MO consists of the parameters related to bearers for
application-layer control interfaces such as the NodeB Control Port (NCP),
Communication Control Port (CCP), S1, and X2 interfaces.
 An SCTPLNK MO consists of the parameters related to a Stream Control
Transmission Protocol (SCTP) link. The SCTP link is used to carry signaling.

 The UMPT board shared by the Abis and Iub interfaces is responsible for protocol
processing at the physical layer, data link layer, network layer (IP), Stream Control
Transmission Protocol(SCTP) and transport link layer (UDP). The protocols at other
layers are processed on the control plane processing boards and user plane
processing boards of GSM, UMTS and LTE separately.
 A Control Port (CP) bearer MO consists of the parameters related to bearers for
application-layer control interfaces such as the NodeB Control Port (NCP),
Communication Control Port (CCP), S1, and X2 interfaces.
 An SCTPLNK MO consists of the parameters related to a Stream Control
Transmission Protocol (SCTP) link. The SCTP link is used to carry signaling.


 If Set VLAN Priority in the VLANMAP MO is set to DISABLE (Disable) and the
default mapping relationship is not used, configure a DSCPMAP MO to set the
mapping between DSCPs and VLAN priorities.
 If VLAN networking is based on the source IP address, configure a SUBNETVLAN
MO to add an entry of mapping between a source IP address and a VLAN.

 If Set VLAN Priority in the VLANMAP MO is set to DISABLE (Disable) and the
default mapping relationship is not used, configure a DSCPMAP MO to set the
mapping between DSCPs and VLAN priorities.
 If VLAN networking is based on the source IP address, configure a SUBNETVLAN
MO to add an entry of mapping between a source IP address and a VLAN.



 Electrical port
 An electrical port is referred to as Ethernet port. There are three types: 10 Mbit/s
(obsolete), 100 Mbit/s, and gigabit/s. The type of ports used depends on the
transmission network planning, switch type, and transmission bandwidth planning.
 The FE/GE electrical ports use RJ45 connector and have a maximum transmission
distance. If the eNodeB uses the FE/GE network cables to connect to the LAN switch,
xDSL, microwave equipment, or routers, the maximum transmission distance of the
network cables supported needs to be considered.
 Optical port
 In light of MBTS's demand for high bandwidth and the evolution trend of the
transmission network, fiber access will become the mainstream access for MBTS. At
present, most companies' L3 switches support both electrical ports and optical ports,
and fiber access to the MBTS is common.

 On early LANs, several hosts connect to the same coaxial cable and only one host
can send packets at a time. If two or more hosts send packets at the same time, data
collisions occur. In addition, packets sent by any host are broadcast on the network
and all nodes receive the packet. In this case, the network is also a broadcast domain.
When more and more hosts send packets on the network, the broadcast traffic
consumes high bandwidths.
 Later, hubs replace coaxial cables and realize physical topology of the star type.
However, shared media are used for communication. Packets sent by any host are
received by other devices.
 Network bridges (layer 2 switches) then replace hubs and reduce the collision
domains to each port. In this way, the efficiency for sending unicast packets on the
network is greatly improved. However, all ports on the network exist in the same
broadcast domain and packets are duplicated when network bridges are used to send
packets. With network scale expansion, more and more packets exist on the network
and affect network performance severely. This is called a broadcast storm.

 To resolve the broadcast storm problem and improve network efficiency, a large
broadcast domain is generally divided into several small broadcast domains.
 Routers can resolve the broadcast storm problem by segmenting the LAN.
However, routers separate the network at the network layer. As a result, the
network planning is complicated and networking is inflexible, which
increases management and maintenance difficulties.
 A LAN can be logically divided into multiple subsets. Each subset forms a
broadcast domain, that is, a VLAN. In simple words, the VLANs logically
(instead of physically) divide devices in a LAN into different network
segments. This realizes broadcast domain separation within a LAN.

 Octet is used in all Internet standards and most books concerning the TCP/IP,
indicating bytes.

 Subnets are divided to reduce the adverse impact of broadcast and improve the
overall performance. In addition, proper planning and use of subnets save IP address
resources. Hosts on different subnets cannot communicate with each other directly
(can communicate through a router or gateway). Currently, network security is
depressing. Therefore, the smaller the network is, the securer it is. Subnets also
facilitate maintenance because troubleshooting is difficult on a large network but easy
on a small network.
 Risks of subnets include less IP addresses for hosts and no direct communication
between subnets. On subnets, there is one network address or one broadcast
address that cannot serve as the host. That is, two IP addresses are wasted on one
subnet. The more the subnets are, the more the IP addresses are wasted. No direct
communication between subnets is not merely a disadvantage, and it helps to
improve the subnet security. However, for enterprises requiring frequent network
communication between departments, if there is no direct communication between
subnets, everything will become inconvenient and the working efficiency will be
affected.

 If the device IP address is set to a logical IP address, the device IP address must be
on a different network segment from the port IP address. In addition, a route must be
configured from the logical IP address to an external device (such as the router
connected to the base station).

 Requirements for a router are as follows :

 A router must have two or more network layer interfaces for connecting
different networks.
 The protocol must be implemented at the network layer.
 Functions of a router are as follows :
 A router generates routing tables.
 A router forwards packets to other networks.
 A routing table can be generated in the following ways :
 Static route: Entries in a routing table are entered by an operator one by one.
 Dynamic route: Entries in a routing table are generated using a routing
protocol, such as the OSPF or ISIS.
 Destination-based routing: Destination-based routing is a mechanism in which the
IP addresses of the egress ports and gateways for IP packets are determined based
on the destination IP addresses. For static routes with the same destination address
and subnet mask but different next-hop IP addresses, the route configuration takes
effect according to the following principle: If the priority of the static routes is the same,
they are equivalent routes. Packet forwarded on equivalent routes can be performed
based on streams or on a per packet basis. Huawei wireless devices support packet
forwarding based only on streams.

 Source-based routing: Source-based routing is a mechanism in which the IP

addresses of the egress ports and gateways for IP packets are determined based on
the source IP addresses. For static routes with the same destination address and
subnet mask but different next-hop IP addresses, the route configuration takes effect
according to the following principle: If the static routes have the same priority, they are
equivalent routes. Packet forwarded on equivalent routes can be performed based on
streams or on a per packet basis. Huawei wireless devices support only stream-based

packet forwarding.



 4 SCTPLNK are required at least;

 One for GSM;
 Two for UMTS(NCP and CCP respectively);
 One for LTE;
 3 IPPATH are required At least;
 (Optional) If the BSC and RNC use the same IP address but the eGBTS and NodeB
use different IP addresses, configure a GBTSPATH MO to add an IP path used by the
eGBTS.
 (Optional) If the BSC and RNC use the same IP address but the eGBTS and NodeB
use different IP addresses, configure a NODEBPATH MO to add an IP path used by
the NodeB.

 Before the development of SCTP, UDP and TCP were used to transmit signaling in IP
network.
 UDP is a connectionless transmission protocol. It can’t satisfy the transmission quality
requirement of signaling.
 TCP is a connection-oriented transmission protocol, and it can provide reliable
transmission for signaling. But it has the natural disadvantages to overcome.
 Poor real-time performance
 Difficult to support multi homing
 Vulnerable to denial of service (DoS) defects
 So IETF (Internet Engineering Task Force) RFC2960 developed the connection-
oriented STCP, which is a reliable real-time transmission protocol based on packet.
SCTP improves TCP to overcome its disadvantages, and makes signaling
transmission more reliable. The design of SCTP include congestion control,
preventing the masquerading attack, providing better real-time performance, and
supporting multi-homing.




 Configure EPGROUP MOs to add an end point group on the Abis interface, an end
point group on the Iub interface, an end point group on the S1 interface, and an end
point group on the X2 interface, and add user-plane hosts and user-plane peers to the
end point groups. For the LTE mode, you also need to add SCTP hosts and SCTP
peers to the end point groups.
 Configure USERPLANEHOST MOs to add a user-plane host on the Abis interface, a
user-plane host on the Iub interface, a user-plane host on the S1 interface, and a
user-plane host on the X2 interface.
 (Optional) Configure USERPLANEPEER MOs to add a user-plane peer on the Abis
interface, a user-plane peer on the Iub interface, a user-plane peer on the S1 interface,
and a user-plane peer on the X2 interface. If you do not run this command to manually
add a user-plane peer, such a user-plane peer will be automatically created.

 (Optional) The GSM and UMTS control planes support only link mode configurations.
To deploy GSM or UMTS services in the co-MPT base station, perform the following
steps:
 Configure SCTPLNK MOs to add an SCTP link on the Abis interface and an
SCTP link on the Iub interface.
 Configure CPBEARER MOs to add a CP bearer on the Abis interface and a
CP bearer on the Iub interface. In this step, set Bear Type to SCTP.
 (Optional) To deploy LTE services in a co-MPT base station, perform the following
steps:
 Configure an SCTPTEMPLATE MO to add an SCTP parameter template.
 Configure SCTPHOST MOs to add an SCTP host on the S1 interface and an
SCTP host on the X2 interface.
 Configure SCTPPEER MOs to add an SCTP peer on the S1 interface and an
SCTP peer on the X2 interface.

 (Optional) The GSM and UMTS control planes support only link mode configurations.
To deploy GSM or UMTS services in the co-MPT base station, perform the following
steps:
 Configure SCTPLNK MOs to add an SCTP link on the Abis interface and an
SCTP link on the Iub interface.
 Configure CPBEARER MOs to add a CP bearer on the Abis interface and a
CP bearer on the Iub interface. In this step, set Bear Type to SCTP.
 (Optional) To deploy LTE services in a co-MPT base station, perform the following
steps:
 Configure an SCTPTEMPLATE MO to add an SCTP parameter template.
 Configure SCTPHOST MOs to add an SCTP host on the S1 interface and an
SCTP host on the X2 interface.
 Configure SCTPPEER MOs to add an SCTP peer on the S1 interface and an
SCTP peer on the X2 interface.

 When the control plane is set up automatically, an SCTP link is automatically set up
between the configured SCTP host and SCTP peer. When the security self
establishment feature is enabled on the SCTP host, the SCTP host needs to be
configured with a security host, and the IP address of the SCTP host can quote only
one security host.
 The SCTPPEER MO can be automatically or manually created.

 When the user plane is set up automatically, the system automatically sets up a user-
plane link between the configured user-plane host and a user-plane peer. The user-
plane peer can be manually configured or automatically generated by the system.
 When security automatic establishment is enabled on a USERPLANEHOST MO, the
IPSec Auto Configure Switch is enabled for the USERPLANEHOST MO and a
SECURITYHOST MO is quoted. Therefore, before enabling this feature, ensure that
the SECURITYHOST MO to be quoted has been added by using the ADD
SECURITYHOST command.


 For details about configuring the Radio Data, see Practice Guide Documentation.

 In smart configuration mode:

 For GSM radio data, the CME automatically generates radio data about
objects, such as sectors, sector equipment, sector equipment antennas, TRX
group sector equipment, and sector antennas, based on data about cells,
logical TRXs, and TRX transmit channels configured by users.
 For UMTS and LTE radio data, the CME automatically generates radio data
about objects such as sector equipment, sector equipment antennas, and
sector antennas, based on data about cells and sectors configured by users.
 Note: we only talk about the Manual mode of Configuring radio data.



 Configure BASEBANDEQM Mos:

 Configure this MO if the co-MPT base station needs to provide GSM services
and a GSM local cell uses the baseband resources of the UBBPd. In this step,
set Baseband Equipment Type to ULDL(Combined UL and DL) and UMTS
UL Demodulation Mode to NULL(NULL).
 Configure this MO if the co-MPT base station needs to provide LTE services
and baseband processing units need to be specified for cells. In this step, set
Baseband Equipment Type to ULDL(Combined UL and DL) (recommended)
and UMTS UL Demodulation Mode to NULL(NULL).
 Configure this MO based on the data plan if the co-MPT base station needs to
provide UMTS services.
 In the co-MPT base station, the common radio data is required. The radio data
dedicated to a specific mode is prepared based on the mode to be deployed in
the co-MPT base station. For example, if you need to deploy one mode in the
co-MPT base station , only the radio data for this mode must be prepared.

 For a co-MPT base station, if services of different modes are carried on the same
transmit channel, you are advised to configure the same SECTOR for these modes.
 You can configure sector equipment using both SECTOREQM and SECTOR. If you
configure sector equipment using SECTOREQM, Create Default Sector
Equipment for SECTOR must be set to FALSE (FALSE). If you configure sector
equipment using SECTOR, Create Default Sector Equipment must be set
to TRUE(TRUE) and Default Sector Equipment ID must be specified.
 For a co-MPT base station, if services of different modes are carried on the same
transmit channel, you are advised to configure the SECTOREQM by mode.
 Sending Mode and Receiving Mode of the TRX group must be consistent
with Antenna RX/TX Mode of the sector equipment bound to the TRX group. For
example, if Receiving Mode of the TRX group is set to SINGLERECV(Single
Receiver), the sector equipment bound to the TRX group can be configured with at
most one antenna that can receive signals.

 One GTRXGROUP provides services for only one GLOCELL. One GLOCELL can be
served by one or multiple GTRXGROUPs.
 One SECTOR can contain multiple SECTOREQM, but one SECTOREQM belongs
only to one SECTOR.
 One SECTOREQM can provide services for one or multiple GLOCELLs. One
GLOCELL can be served by one or multiple SECTOREQM.
 In a common cell, one GLOCELL refers to one SETCTOR. In RANSharing scenarios,
one SETCTOR can provide services for multiple GLOCELL.
 One GTRXGROUP can only be served by one SECTOREQM. In RANSharing
scenarios, one SECTOREQM can provide services for multiple GTRXGROUPs.

 In LampSite scenarios, the MO of ULOCELLSECTOREQM does not need to be

configured.

 A cell is not equivalent to an RF coverage area or sector.

 Number of cells supported by a NodeB = Number of sectors x Number of carriers in a
sector
 As shown in this figure, three sectors (sectors 0 to 2) cover a circular area and
each sector uses two carriers. Therefore, there are a total of six cells.

 If baseband equipment has been added, specify the ID of the baseband equipment
whose baseband resources are used for the cell based on the network plan.

 Number of cells = Number of sectors x Number of carriers



 This section describes how to open a default or user-defined summary data file and
check the existing configuration objects and parameters in the file in the window of the
tool for customizing a summary data file.
 On the menu bar, choose Advanced > Customize Summary Data File (CME client
mode) or CME > Advanced > Customize Summary Data File (U2020 client mode).
A dialog box is displayed for you to open the summary data file.
 Perform operations as required.
 To adjust the sheets, configuration objects, and parameter names in a user-
defined summary data file, select Custom to select a user-defined summary
data file.
 If a default summary data file is to be used, select Co-MPT BTS Summary,
enabled RAT, version, and IP over FE Summary Template under Default.
 When the settings are complete, click OK. The main window for customizing a
summary data file is displayed.

 Note:
 Editable records are highlighted in white; Records that are not editable are
highlighted in dark grey; Records that can be deleted but cannot be modified
are highlighted in light grey.
 If the values of NE MOC and NE Attribute are empty, the parameter in the
corresponding summary datafile is referenced only by other configuration
parameters and does not map any NE configuration object.

 This section describes how to verify and save a summary data file to a local PC for
editing the summary data file in the future.
 If the verification result contains an alarm indicating that a branch parameter does not
exist, determine whether to customize the parameter in the summary data file based
on planned data. The alarm has no impact on the follow-up saving operation.


 NOTE: Base station IDs must be set in the first column. If an NE name appears
multiple times during customization of a summary data file, the CME combines the
same NE names as one NE name when you can save the summary data file.
 For example as the list sheet, on the user plane, the number of links and link types for
an MO are different among all base stations. You can define the MO on the List
sheets.
 For example as the pattern sheet, on the user plane, the number of links and link
types are the same for each base station and only the base station IP addresses are
different. In this case, you can edit the differentiated parameters on the Base Station
Transport Data sheet and use the referenced correlation on the Pattern sheets.

 This sheet provides planned data only for base station creation, data in each row
applies to all base stations created by using the summary data file, which is consistent
on the entire network, such as:
 The telecom operator information
 U2020 OM IP address and Network Time Protocol
 MME information and SGW information
 APPLICATION function for base station mode
 System Clock and Time Zone and Daylight Saving Time
 And so on

 The sheets of this type contain base station information which data in each row
applies only to one base station, the sheet contains some information of one base
station as follows:
 MBTS Name, Product Type, Node Template
 BSC Name, Control Plane IP address of BSC side, User Plane IP address of
BSC side
 eGBTS Name, GSM Radio Template, Control Plane IP address of eGBTS side,
User Plane IP address of eGBTS side
 RNC Name, Control Plane IP address of RNC side, User Plane IP address of
RNC side
 NodeB Name, UMTS Radio Template, Control Plane IP address of NodeB
side, User Plane IP address of NodeB side
 eNodeB Name, LTE Radio Template, Control Plane IP address of eNodeB
side, User Plane IP address of eNodeB side
 OM IP and Mask
 And so on

 The sheets of this type contain GSM CELL information which data in each row applies
only to one cell, the sheet contains some information of one cell as follows:
 eGBTS Name
 LoCellID
 Local Cell Template
 GSM Cell Name of BSC side
 GSM Cell Template Name of BSC side
 Cell Type
 MCC, MNC, LAC and CI
 Frequency of BCCH
 And so on

 The sheets of this type contain GSM TRXGROUP information which data in each row
applies only to one TRXGROUP, the sheet contains some information of one
TRXGROUP as follows:
 eGBTS Name
 TRX Group ID
 Local Cell ID
 Sending Mode and Receiving Mode
 And so on

 The sheets of this type contain UMTS CELL information which data in each row
applies only to one cell, the sheet contains some information of one cell as follows:
 NodeB Name
 LoCellID
 Uplink UARFCN
 Downlink UARFCN
 Max Output Power
 Local Cell Template
 Band Indicator
 And so on

 The sheets of this type contain LTE CELL information which data in each row applies
only to one cell, the sheet contains some information of one cell as follows:
 eNodeB Name
 LoCellID
 CellName
 TAC
 UlEarfcn and DlEarfcn
 And so on


 When reference relationships exist between parameters on the Base Station

Transport Data sheet and those on the Pattern sheet, referenced values on the Base
Station Transport Data sheet are exported based on the reference relationships on
the Pattern sheet. If these values are not entered by users, referenced values on the
Base Station Transport Data sheet cannot be exported.


 On the menu bar of the planned data area, choose SRAN Application > MBTS
Application > Import Data > Import Base Station Summary Data (CME client
mode) or CME > SRAN Application > Import Base Station Summary Data
(U2020 client mode). A dialog box is displayed for you to select a file.




 You can save the new base station as a template.



 This section describes how to verify the validity and integrity of base station
configuration data before you export the data. Validity verification is to check whether
base station configuration data meets NE configuration rules. If the data does not
meet the rules, it is not sent to NEs. Integrity verification is to check whether base
station configuration data is complete. If the data is incomplete, services cannot be
provided. For example, a base station without cell data cannot provide radio services.
 On the menu bar of the planned data area, choose Advanced > Check Data (CME
client mode) or CME > Advanced > Check NE Data (U2020 client mode), or click
on the toolbar. A verification dialog box is displayed.

 The data consistency check function helps you check whether configuration data
about multimode base stations (including separate-MPT base stations and co-MPT
base stations) meets configuration rules.
 On the menu bar of the current data area or planned data area, choose SRAN
Application > MBTS Application > MBTS Check Consistency (CME client mode)
or CME > SRAN Application > MBTS Check Consistency (U2020 client mode). A
window is displayed for you to perform operations.

 On the menu bar, choose Advanced > Export Auto Deployment Data (CME client
mode) or CME > Advanced > Export Auto Deployment Data (U2020 client mode).
A dialog box is displayed for you to export auto-deployment data.
 Select the base stations whose auto-deployment data you want to export, and click
Next.
 Select a save path for the exported file and a method for processing data, and click
Next.
 View data in the base station deployment list, and click Next. The CME starts to verify
data correctness and exports the data.
 If the export is successful in U2020 client mode, set the following options:
 Select Do not open the Auto Deployment window to close the wizard.
 Select Open the Auto Deployment window. The CME automatically
switches to the auto-deployment window and creates a commissioning task.
 Select Open the Auto Deployment window and start Auto Deployment
task. The CME automatically switches to the auto-deployment window and
starts a commissioning task.

 Click Finish.
 Deployment list: The naming convention is Auto_Deployment_List_ID of the
planned data area_time stamp.xml. If multiple NEs are selected at a time,
the NE data is exported to one deployment list.
 Data configuration script: The script is named CFGDATA.XML. Each NE has

one data configuration script.

 On the U2020 client, choose SON > Self Planning > Auto Deployment (Application
style) or SON > Auto Deployment (Traditional style). The Auto Deployment window
is displayed.
 Please see the commission course in detail.



Initial Data Templates

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Initial Data Templates

Uploaded by

Copyright:

Available Formats

MBTS GUL V100R015C10 Initial Data Configuration based on CME

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Base station template

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Exporting templates for other users to import

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Note for LTE RAT

Name Note Configuration

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Configuring Device Data for slot distribution

Board Name Mandatory Maximum Quantity Slot Assignment Sequence (the

Confidential Information of Huawei. No Spreading Without Permission

 Configure an RRUCHAIN MO to add an RRU chain or ring

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Recommended Scenario as Link mode:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Requirements for a router are as follows :

Confidential Information of Huawei. No Spreading Without Permission

 Source-based routing: Source-based routing is a mechanism in which the IP

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission