Scenario Basic Summary Template For Online CME - 18 - July - 2024
Scenario Basic Summary Template For Online CME - 18 - July - 2024
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
OSS Data
*OSS IP *OSS IP Mask
10.104.21.7 255.255.255.192
APPLICATION
*Application ID *Application Type *Application Name
1 GBTS GBTS
2 NodeB NodeB
3 eNodeB eNodeB
Time Source
Time Source
NTP
DIFPRI
Priority Rule Signaling Priority OM High Priority
DSCP 48 46
SCTP Peer
*SCTP Peer ID First Peer IP Address Second Peer IP Address
0 10.101.11.77 10.101.11.78
S1
*S1 ID *CN Operator ID End Point Group Config Flag
0 0 CP_UP_CFG
X2
*X2 ID *CN Operator ID End Point Group Config Flag
0 0 CP_UP_CFG
Iub Object
*Iub ID EndPoint Group ID
30 10
Abis
*Transmission Resource ID *End Node Object Homing Group ID User Label
11 20
GNSS Clock Link
*GNSS Clock No. Cabinet No. Subrack No.
0 0 0
*Mobile country code *Mobile network code
412 40
Control Plane End Point Group ID User Plane End Point Group ID
0 0
Control Plane End Point Group ID User Plane End Point Group ID
1 1
nagement
Quality Level Clock Synchronization Mode
QL-SSU-B TIME
GNSS Clock Link Management
Slot No. GNSS Work Mode Priority
7 GPS 1
Authentication Key Authentication Key Index Master Flag
Slave
Table 1 Procedure for collecting data by using the summary data workbook
Step
Combine templates
1 Cover
2 Common Data
3 Base Station Transport Data
4 Cell Sheets
5 MO Pattern Sheets
6 MO List Sheets
8 NE Version
9 Auto Deployment
10 Help
The procedure for constructing base station data after a summary data file is imported into the Deployment i
(2) The Deployment reads planned radio data of cells in the summary data file row by row and constructs ra
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
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.
s, NodeBs, eNodeBs and gNodeBs are similar.
nding Co-MPT BTS, NodeB, eNodeB or gNodeB. Differences in base station descriptions are listed in the Difference column of Table 2.
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
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 th
he Common Data sheet, the Deployment combines the data of relevant objects in the Common Data and Base Station Transpo
ta of cells in the summary data file row by row and constructs radio data of base stations.
ment reports an error message.
objects are defined in the Common Data sheet, the Deployment combines the data of relevant objects in the Common Data she
ept that is used for constructing transport data and radio data of base stations in step (2) and step (3) respectively serves as gl
erence column of Table 2.
modes.
so be filled in the summary data workbook.
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
Remarks:
Only the summary data files for
creating base stations or introducing
RATs to base stations contain this
sheet.