Co-MPT BTS Summary Data Workbook

UMTS Controller Version BSC6910V100R022C10SPC500

Base Station Version BTS3900 V100R016C10SPC300
Issue Date 2019/12/31

Read Me
1. This workbook contains multiple worksheets. Description about each worksheet is provided in the following list
workbook to customize planned parameters.
2. Parameters in each worksheet are grouped by service type. Parameters related to the same service type are o
3. Each mandatory field is marked with an asterisk (*) character. Mandatory fields must be filled in completely.
4. If the Common Data sheet exists, separate every two data areas of objects by at least one blank row on the sh
5. To add a row, you are advised to copy a row and then paste it, or right-click a row and choose Insert from the
newly added row has the same format as the existing rows.

6. Do not define names of fields and worksheets in the Summary Data Workbook manually. If required, yo
Summary Data File" tool to define the names of fields and worksheets.
7. This table supports multiple versions. If multiple versions are combined in the table, the version numbers are s
8. When different NE products of different models have the same parameter name but the parameter name of ea
parameter ID, multiple records are included on the Model Difference Description sheet.

Change History
Item Date Version
1 2016/05/31 In V0.1, planned parameters for Co-MPT BTS deployment are specified ba
2 2017/03/30 In V1.0, this worksheet is released.
3 2017/03/31 In V1.1, supports multiple NE versions.
orkbook

vided in the following list. You can add worksheets to this

e same service type are organized into a group.

be filled in completely.
t one blank row on the sheet to avoid data area mixture.
d choose Insert from the shortcut menu. This ensures that the

manually. If required, you must use the "Customize

e version numbers are separated by a semicolon (;).

he parameter name of each NE product maps a unique

loyment are specified based on actual networking.

 OSS Data
*OSS IP *OSS IP Mask

*Application ID *Application Type *Application Name Application Maintenance Mode

1 NodeB NORMAL

Time Source
Time Source

IPv4 Address of NTP Server NTP IP Mask IP Mode Port Number

Time Zone DST Tag Information DST Start Mode DST Start Month

DIFPRI
Priority Rule Signaling Priority OM High Priority OM Low Priority

NCP/CCP SCTP Link

SCTP Server Port No.

System Clock Link Management

Clock Working Mode Clock Source No. Selected Clock Source Clock Synchronization Mode
 IP Clock Link Management
Link No. Protocol Type Slot No. Server IPv4
 APPLICATION
Start Time of Application Status Setting End Time of Application Status Setting

Network Time Protocol

Synchronization Period(min) Authentication Mode

Time Zone and Daylight Saving Time

DST Start Day DST Start Week Sequence

IP Clock Priority

Quality Level
agement
Domain Priority
Application Maintenance Mode Setting Remark Extended Application Type

Authentication Key Authentication Key Index Master Flag

Time Zone and Daylight Saving Time

DST Start Weekday DST Start Time DST End Mode
DST End Month DST End Day DST End Week Sequence DST End Weekday DST End Time
DST Offset(min) Time Difference(min)
 Base Station
*Name *Product Type *Node Template *Working Mode Base Station Configuration
 Loca
BTS Design File Site Location Geo-coordinate data format Latitude With Degree Format(1e-6 degree)
 Location
Latitude With Second Format(s) Longitude With Degree Format(1e-6 degree) Longitude With Second Format(s)
 NodeB
Mode *NodeB Name *UMTS Radio Template *RNC Name Logical RNC ID NodeB ID
 Logical NodeB
IUB Transport Bearer Type Sharing Type Of NodeB Cn Operator Index Validation indication
 Ethernet Port BS IP address
NodeB Host Type Iub Type Iub Flex Flag *Port No.0 *Port No.1 *IP 1 *IP 1 Mask
BS IP address
*IP 2 *IP 2 Mask *Destination IP1 *Destination Mask1 Next Hop IP Address1 VLAN ID1
VLAN Priority1 *Destination IP2 *Destination Mask2 Next Hop IP Address2 VLAN ID2
 BS IPRoute
VLAN Priority2 *Destination IP3 *Destination Mask3 Next Hop IP Address3 VLAN ID3
 BS IPRoute
VLAN Priority3 *Destination IP4 *Destination Mask4 Next Hop IP Address4 VLAN ID4
VLAN Priority4 *Destination IP5 *Destination Mask5 Next Hop IP Address5 VLAN ID5
VLAN Priority5 *Destination IP6 *Destination Mask6 Next Hop IP Address6 VLAN ID6
 RNC IP address Iub Control Plan
VLAN Priority6 *IP 1 IP 1 Mask *IP 2 IP 2 Mask *NCP SCTP Port *NCP SCTP link ID
Iub Control Plane
*CCP Port No. *CCP SCTP Port *CCP SCTP link ID *Adjacent Node ID *Adjacent Node Name
 Iub User Plane
*Transport Type *Transmission Resource Pool Index *Forward Bandwidth *Backward Bandwidth
 NodeB
*NodeB Name *Local Cell ID BTS Design Cell ID Local Cell Radius(m)
Local Cell Inner Handover Radius(m) UL Baseband Equipment ID DL Baseband Equipment ID
 UMTS Local Cell
UL Frequency Indicator Local Cell Type UL Frequency Channel Number *DL Frequency Channel Number
Max Output Power(0.1dBm) Frequency Bandwidth(kHz) Sector Equipment ID Azimuth Electrical Tilt
Mechanical Tilt *Local Cell Template Cell ID *Cell Name *CN Operator Group Index
*Band Indicator UL Frequency Ind Uplink UARFCN *Downlink UARFCN
 UMTS Cell
*DL Primary Scrambling Code *Location Area Code *Service Area Code *RAC Configuration Indication
Cell
Routing Area Code *Service Priority Group Identity *URA ID Cell Oriented Cell Individual Offset
*Time Offset[chip] Max Transmit Power of Cell PCPICH Transmit Power *Cell Template
Validation indication
 Ethernet Port IP address
*Subrack No. *Slot No. *Port No. *IP address index *Local IP address *Subnet mask
Remark
 RNC Device IP Address
*RNC Name *Subrack No. *Slot No. *Device IP Address Type IP address Subnet mask
MTU[Byte] Remark
 *SCTP link ID *Application type Signalling link mode Differentiated Service Codepoint
Base Station Transport Data\Iub
NBAP Control Plane\*NCP
SERVER SCTP link ID
Base Station Transport Data\Iub
NBAP Control Plane\*CCP
SERVER SCTP link ID
Specify Server Local Port Flag Local SCTP port No. First local IP address Second local IP address
Base Station Transport Data\RNC IP address\*IP 1
Base Station Transport Data\RNC IP address\*IP 2
 First destination IP address Second destination IP address Destination SCTP port No. Logic Port Flag
Base Station Transport Data\BS IP address\*IP 1 Base Station Transport Data\Iub Control Plane\*NCP SCTP Por
Base Station Transport Data\BS IP address\*IP 1 Base Station Transport Data\Iub Control Plane\*CCP SCTP Por
 SCTP Link
Logic Port Slot No. Logic Port No. RTO min value RTO max value RTO initial value
ntrol Plane\*NCP SCTP Port 3000 1000
ntrol Plane\*CCP SCTP Port 3000 1000
 SCTP Link
RTO alpha value RTO beta value SACK delay timer Heartbeat interval Association max retrans
12 25
12 25
Path max retrans Checksum arithmetic MTU value Cross IP address available flag
CRC32 800
CRC32 800
Switch primary IP address flag Switch back HB number Bundling Flag Remark
NO -
NO -
Local IP Distribution Type Local Primary Ip Peer Primary Ip Peer Multiple Fast Retransmit Support Flag
YES
YES
Iur-p Local IP Address
 NCP Link
*Bearing Link Type SAAL link No. SCTP link ID Main Link Type
SCTP Base Station Transport Data\Iub Control Plane\*NCP SCTP link ID
 CCP Link
*Port No. *Bearing Link Type SAAL link No. SCTP link ID Main Link Type
Base Station Transport Data\Iub Control Plane\*CCP Port
SCTP BaseNo.
Station Transport Data\Iub Control Plane\*CCP SCTP link ID
ne\*CCP SCTP link ID
 Adjacen
*Adjacent Node ID *Interface Type Transport Type of the adjacent node and interface type
Base Station Transport Data\Iub
IUBUser Plane\*Adjacent
Base Station Transport
Node ID Data\Iub User Plane\*Transport Type
 Adjacent Node Mapping
Resource Management Mode CN Operator index Gold user TRMMAP index Silver user TRMMAP index
e\*Transport Type
Bronze user TRMMAP index Factor table index
 RNC Transmission Resource Pool
*RNC Name *Transmission Resource Pool Index *NetWork Mode Transmission Resource Pool Name
 RNC IP Address to Transmission Resource Pool
*RNC Name *Transmission Resource Pool Index *Subrack No. *Slot No.
Transmission Resource Pool
*IP Address in Transmission Resource Pool Block Status
 RNC a Policy-Based Rou
*RNC Name *Subrack No. *Slot No. *IP TYPE Source IP address Source Address Mask
a Policy-Based Route Based on the Source IP Address
Forward route address Standby Next hop switch Standby next hop
Route Configure Inconsistency Detect Switch Purpose description
*NodeB TransType NodeB IP_TRANS IP address NodeB IP_TRANS IP Mask NodeB IP_TRANS Subrack No.
IPTRANS_IP Base Station Transport Data\BSBase
IP address\*IP
Station Transport
2 Data\BS IP address\*IP 2 Mask
 NodeB IP Address
NodeB IP_TRANS Slot No. NodeB ATM_TRANS IP address NodeB ATM_TRANS IP Mask
NodeB IP Address
NodeB ATM_TRANS Subrack No. NodeB ATM_TRANS Slot No. Vlan Flag VLAN ID. VLAN Priority
NodeB Main Control Board Slot No NodeB IP_TRANS backup IP address NodeB IP_TRANS backup IP Mask
 Device IP Address
*Cabinet No. *Subrack No. *Slot No. Subboard Type Port Type Port No. *VRF Index
0 0 ETH Base Station Transport
0 Data\Ethernet Port\*Po
0 0 ETH Base Station Transport
0 Data\Ethernet Port\*Po
 *IP Address *Mask User Label Borrow IFIP
Base Station Transport
Base Station
Data\BS
Transport
IP address\*IP
Data\BS1IP address\*IP 1 Mask
Base Station Transport
Base Station
Data\BS
Transport
IP address\*IP
Data\BS2IP address\*IP 2 Mask
*Route Index Cabinet No. Subrack No. *Slot No. Subboard Type Route Type Port Type
0 0 0 NEXTHOP
1 0 0 NEXTHOP
2 0 0 NEXTHOP
3 0 0 NEXTHOP
4 0 0 NEXTHOP
5 0 0 NEXTHOP
 IP Route
Port No. VRF Index *Destination IP *Mask Next Hop IP Peer IP MTU Switch
0 Base Station Transport
Base Data\BS
Station
Base
Transport
IPRoute\*Destination
StationData\BS
Transport
IPRoute\*Destination
Data\BS
IP1 IPRoute\Next
Mask1
Hop IP Address1
0 Base Station Transport
Base Data\BS
Station
Base
Transport
IPRoute\*Destination
StationData\BS
Transport
IPRoute\*Destination
Data\BS
IP2 IPRoute\Next
Mask2
Hop IP Address2
0 Base Station Transport
Base Data\BS
Station
Base
Transport
IPRoute\*Destination
StationData\BS
Transport
IPRoute\*Destination
Data\BS
IP3 IPRoute\Next
Mask3
Hop IP Address3
0 Base Station Transport
Base Data\BS
Station
Base
Transport
IPRoute\*Destination
StationData\BS
Transport
IPRoute\*Destination
Data\BS
IP4 IPRoute\Next
Mask4
Hop IP Address4
0 Base Station Transport
Base Data\BS
Station
Base
Transport
IPRoute\*Destination
StationData\BS
Transport
IPRoute\*Destination
Data\BS
IP5 IPRoute\Next
Mask5
Hop IP Address5
0 Base Station Transport
Base Data\BS
Station
Base
Transport
IPRoute\*Destination
StationData\BS
Transport
IPRoute\*Destination
Data\BS
IP6 IPRoute\Next
Mask6
Hop IP Address6
 Maximum Transmission Unit(byte) Preference Description Info
PRoute\Next Hop IP Address1 60
PRoute\Next Hop IP Address2 60
PRoute\Next Hop IP Address3 60
PRoute\Next Hop IP Address4 60
PRoute\Next Hop IP Address5 60
PRoute\Next Hop IP Address6 60
 VLAN Mapping Based on Next Hop IP
*VRF Index *Next Hop IP *Mask *VLAN Mode VLAN ID Set VLAN Priority VLAN Priority
0 255.255.255.255
SINGLEVLAN
VLAN Group No.
*Link No. Cabinet No. Subrack No. Slot No. Maximum Stream No. VRF Index
6 0 0 7 17 0
7 0 0 7 17 0
DTLS Policy ID DTLS Connection Policy SCTP Authentication Chunk List IP Version
NULL IPv4
NULL
 First Local IP Address Second Local IP Address First Local IPv6 Address Second Local IPv6 Address
Base Station Transport Data\BS IP address\*IP 1
Base Station Transport Data\BS IP address\*IP 1
 SCTP Link
*Local SCTP Port No. First Peer IP Address Second Peer IP Address First Peer IPv6 Address
Base Station Transport Data\Iub
Base Station
Control
Transport
Plane\*NCP
Data\RNC
SCTP IP
Port
address\*IP 1
Base Station Transport Data\Iub
Base Station
Control
Transport
Plane\*CCP
Data\RNC
SCTP IP
Port
address\*IP 2
 SCTP Link
Second Peer IPv6 Address *Peer SCTP Port No. RTO Min Value(ms) RTO Max Value(ms)
Common Data\NCP/CCP SCTP Link\SCTP
1000 Server Port No.[0]
3000
Common Data\NCP/CCP SCTP Link\SCTP
1000 Server Port No.[0]
3000
RTO Initial Value(ms) RTO Alpha Value RTO Beta Value Heart-beat Interval(ms)
1000 12 25 5000
1000 12 25 5000
Max Association Retransmission Max Path Retransmission Checksum Algorithm Type Switch Back Flag
10 5 CRC32 ENABLE
10 5 CRC32 ENABLE
Heart-beat Times When Switch Back Block Flag SACK Timeout(ms) Description Info
UNBLOCK 200
UNBLOCK 200
Maximum SCTP PDU Size(byte)
 Control Port Bearer
*CP Bear No. *Flag *Bear Type Link No.
6 MASTER SCTP 6
7 MASTER SCTP 7
 NodeB Iub Control Port
*Port Type CP Port No. *Belong Flag *CPBear ID
NCP MASTER 6
CCP Base Station Transport Data\Iub Control 7Plane\*CCP Port No.
MASTER
*Path ID Transmission Configuration Mode Join IP Transmission Resource Group
6 OLD
7 OLD
8 OLD
9 OLD
10 OLD
11 OLD
12 OLD
13 OLD
IP Transmission Resource Group ID Bearing Port Type Port ID Cabinet No. Subrack No.
 IP Path
Slot No. Subboard Type Port Type Port No. Join Transmission Resource Group
 IP Path
Transmission Resource Group ID Path Type DSCP VRF Index *Local IP Address
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
FIXED 0 Base Station Transport Data\BS IP address\*IP 1
 *Peer IP Address Transmission Resource Type IP MUX Switch
Base Station Transport Data\RNC IPHQ
address\*IP 1
Base Station Transport Data\RNC IPHQ
address\*IP 1
Base Station Transport Data\RNC IPHQ
address\*IP 1
Base Station Transport Data\RNC IPHQ
address\*IP 1
Base Station Transport Data\RNC IPHQ
address\*IP 2
Base Station Transport Data\RNC IPHQ
address\*IP 2
Base Station Transport Data\RNC IPHQ
address\*IP 2
Base Station Transport Data\RNC IPHQ
address\*IP 2
Maximum Length of IP MUX Subframe(byte) Maximum Length of IP MUX Multiframe(byte) MUX Timer(ms)
Static Check Switch Description
FOLLOW_GLOBAL
FOLLOW_GLOBAL
FOLLOW_GLOBAL
FOLLOW_GLOBAL
FOLLOW_GLOBAL
FOLLOW_GLOBAL
FOLLOW_GLOBAL
FOLLOW_GLOBAL
NodeB IP Path
*PATH ID
6
7
8
9
10
11
12
13
*Standby Status VRF Index Bearer Type Local IP Local Mask Peer IP Peer Mask
MASTER 0 IPV4 Base StationBase
Transport
Station
Data\BS
Transport
Common
IP address\*IP
Data\BS
Data\OSS
Common
IP address\*IP
2 Data\*OSS
Data\OSS2IP[0]
Data\*OSS
Mask IP M
 Local IPv6 Address Peer IPv6 Address Peer IPv6 Address Prefix Length Cabinet No. Subrack No.
mmon Data\OSS Data\*OSS IP Mask[0]
 OM Channel
Slot No. Subboard Type Port Type Port No. Join Transmission Resource Group
 OM Channel
Transmission Resource Group ID VPI VCI Rate Unit Service Type Peak Cell Rate
Sustainable Cell Rate Min Cell Rate Binding Route OMIP Switch OMIP OMIP MASK
Route Index Binding Secondary Route Secondary Route Index Check Type UDP Session ID
UDP Session Group ID User Label
 *Link No. Protocol Type Cabinet No. Subrack No. Slot No. Client IPv4 Server IPv4
Common Data\IP
Common
Clock Data\IP
Link Management\Link
Clock Link Management\Protocol
No.[0] Common
Type[0]Data\IP
Base Station
Clock Link
Transport
Management\Slot
Common Data\BS
Data\IP
IPClock
address\*IP
No.[0]
Link Manag
2
 Domain Delay Type Priority Clock Class Identify Flag Priority Clock Class0 Priority Clock Class1
Common Data\IP Clock Link Management\Domain[0]
ON 6 13
Priority Clock Class2 Priority Clock Class3 Clock Source Specified or Not Clock Source MAC Address
7 14
 IP Clock Link Management
Clock Net Mode Compensation(ns) Priority Announce Freq(Hz) Sync Freq(Hz) Master Priority
Common Data\IP Clock Link Management\Priority[0]
Profile Type Negotiate Duration(s) IP mode Client IPv6 Server IPv6 Pre-Hop IPv4
PDelay Request Freq(Hz) Device Type Destination Multicast MAC Address Type Delay Freq(Hz)
IP Clock Sync Mode Clock Server Description Phase Deviation Report Switch VRF Index
OFF
 PnP Parameters
*Name ESN Sub Network Sub Area *Software Version Cold Patch Version
eters
Hot Patch Version *Connection Type Authentication Type
Help sheet description:
Summary data file descriptions for Co-MPT BTSs, NodeBs, eNodeBs and gNodeBs are similar.
In this sheet, base station represents a corresponding Co-MPT BTS, NodeB, eNodeB or gNodeB. Differences in base

Table 1 Procedure for collecting data by using the summary data workbook
Step

Prepare a base station summary data file

Collect data planned by telecom operators

Collect data planned internally

Combine templates

Import the summary data file into the Deployment to

deploy base stations in batches

Table 2 Sheets in the summary data work

Item Worksheet

1 Cover

2 Common Data
3 Base Station Transport Data

4 Cell Sheets

5 MO Pattern Sheets
 6 MO List Sheets

7 Model Difference Description

8 NE Version

9 Auto Deployment

10 Help

Procedure for Generating Data in a Sum

The procedure for constructing base station data after a summary data file is imported into the Deployment i

1. Read data in the summary data file

(1) The Deployment reads the data in the Base Station Transport Data sheet row by row. Data of each row is
certain configuration objects are defined in the Common Data sheet, the Deployment combines the data of r

(2) The Deployment reads planned radio data of cells in the summary data file row by row and constructs rad
a. If a new base station is found, the Deployment reports an error message.
b. If the parameters of certain configuration objects are defined in the Common Data sheet, the Deployment
planned radio data sheet.

(3) In the Common Data sheet, the data except that is used for constructing transport data and radio data of
base station.
Ss, NodeBs, eNodeBs and gNodeBs are similar.
onding Co-MPT BTS, NodeB, eNodeB or gNodeB. Differences in base station descriptions are listed in the Difference column of Table 2.

ng the summary data workbook

Description

Before collecting data, you need to customize a summary data workbook as required.

This data refers to the planned data negotiated between network planning engineers and telecom operators. After b
data can be directly filled in the summary data workbook.

This data is internally planned based on base station types and transmission networking modes.
After the data planned by telecom operators is filled in, the internally planned data must also be filled in the summar

After data is collected by using the summary data workbook, you also need to prepare relevant templates such as si
templates, or radio data templates used in the workbook. Ensure that the referred templates exist in the Deployment
For details about how to prepare custom templates, see the 3900 Series base station Initial Configuration (Using the

After filling in the summary data workbook, you can import the workbook into the Deployment and deploy base statio

Contains Description
1. Matched base station version
2. Precautions to be taken when you fill in each
worksheet with data
3. Change history

Notes for editing the sheet:

1. Each object information group contains
only one object.
2. Each object information group includes
description, attributes, and data of an
object.
Parameters whose values are the same for all base Object information groups are separated
stations. Such parameters have the same value for all by blank rows.
base stations to be created and need to be negotiated Application scenario:
or planned This sheet is used to edit parameters
whose values are the same and need to
be negotiated or planned for all base
stations, including the telecom operator
information and OSS OM IP address.
 Notes for editing the sheet:
1. Each row records the data of a base
station.
2. The site template and radio template
Basic base station information and planned transport
are required during base station creation,
data
the template names must be entered in
corresponding columns.

Notes for editing the sheet:

1. Each data row records the data of a
cell.
2. If a cell template is required during base
Planned radio parameters of cells
station creation, the template name must
be filled in the corresponding column.

Notes for editing the sheet:

1. The *base station name column is not
required in a pattern sheet.
2. Data in all object pattern sheets is
applicable to all base stations during batch
base station creation.
Application scenario:
Object data of various base stations is
similar.
Patterns of configuration objects. A pattern is the a. The numbers of object data records are
reference data of a configuration object for a base the same.
station. The object of other base stations is configured b. The parameter values for each object
based on the pattern. data record are the same or have the
same sources.
For example, on the user plane, the
number of links and link types for each
base station are the same and only the
base station IP addresses are different.
You can put the differentiated parameters
on the base station Transport Data sheet
and use the referenced correlation on the
Pattern sheet.
 Notes for editing the sheet:
1. The *base station name column is
required in an list sheet.
2. Configuration object data of different
base stations are planned independently
and are differentiated by base station
Random differences among configuration object data
names.
records of various base stations. In this case, the
Application scenario:
object data must be planned individually for each base
Object data of various base stations is
station.
different.
For example, on the user plane, the
number of links and link types for all base
stations are different and random. You
need to plan and complete the object data
for each base station one by one

This sheet helps you fill in the table and is

not used for data import. In this sheet,
The sheet is contained only in the table in which some parameters with model differences
multiple versions are combined. The sheet provides are provided with hyperlinks to the related
the differences between the models of different sheet, and some of them are provided with
versions. no hyperlinks because those parameters
may map multiple site sheets in the MOC-
integration view.

The sheet is contained only in the table in which

This sheet helps you fill in the table and is
multiple versions are combined.The sheet provides the
not used for data import.
component package version of a base station.

NMS parameters for automatic deployment

Guidelines to filling in this summary data file

Procedure for Generating Data in a Summary Data File

data after a summary data file is imported into the Deployment is as follows:

ase Station Transport Data sheet row by row. Data of each row is used for constructing the transport data of a base station. If t
he Common Data sheet, the Deployment combines the data of relevant objects in the Common Data and Base Station Transp

ta of cells in the summary data file row by row and constructs radio data of base stations.
yment reports an error message.
objects are defined in the Common Data sheet, the Deployment combines the data of relevant objects in the Common Data sh

cept that is used for constructing transport data and radio data of base stations in step (2) and step (3) respectively serves as g
fference column of Table 2.

telecom operators. After being negotiated, the

modes.
also be filled in the summary data workbook.

levant templates such as site templates, cell

ates exist in the Deployment.
tial Configuration (Using the Deployment).

ment and deploy base stations in batches.

Difference
Remarks:
The Cell sheet varies based on
base station types.
Co-MPT BTS: sheets of GSM Cell,
GTRXGROUP, UMTS Cell, LTE
Cell, RFA Cell, NR Cell
NodeB: the UMTS Cell sheet
eNodeB: the LTE Cell sheet
gNodeB: the NR Cell sheet
The summary data file for
reparenting base stations does not
contain this sheet.

Remarks:
The *base station name column
varies based on base station types.
Co-MPT BTS: *Name column or the
Logical BTS Name column for each
RAT column
NodeB: *NodeB Name column.
eNodeB: *eNodeB Name column
gNodeB: *gNodeB Name column

The base station name varies

based on base station types.
Co-MPT BTS: base station name or
the logical base station name for
each RAT
NodeB: NodeB Name
eNodeB: eNodeB Name
gNodeB: gNodeB Name
 The base station name varies
based on base station types.
Co-MPT BTS: base station name or
the logical base station name for
each RAT
NodeB: NodeB Name
eNodeB: eNodeB Name
gNodeB: gNodeB Name

The sheet is contained only in the

table in which multiple versions are
combined.

The sheet is contained only in the

table in which multiple versions are
combined.

Remarks:
Only the summary data files for
creating base stations or
introducing RATs to base stations
contain this sheet.

rt data of a base station. If the parameters of

a and Base Station Transport Data sheets.

cts in the Common Data sheet and the

(3) respectively serves as global data for each