Vous êtes sur la page 1sur 529

ZTE

Product UMTS/GSM
Template Type GROUND/RADIO
Template Name GU-SDR CM Optimization
Template Version V4.11.10.14P06
<> 529 , 1
ZTE
Management Object Name Index
SDR ManagedElement SDRManagedElement
Equipment Equipment
Rack Rack
Board PlugInUnit
Time Device TimeDevice
Clock Device ClockDevice
Dry Contact Device DryContactDevice
Environment Monitoring Device EnvMonDevice
Fiber Device FiberDevice
Fiber Cable FiberCable
TMA Device Tma
PA Device PaDevice
Tx Device TxDevice
Rx Device Set RxDeviceSet
Rx Device RxDevice
RET Device Ret
Rf Cable RfCable
Embedded Power Device EPm
Power Outlet Device Set PowerOutletDeviceSet
Power Outlet Device PowerOutletDevice
Power Device Set PmDeviceSet
Bts Auxiliary Peripheral Device AuxUnit
AISG Device AisgDevice
Fan Device FanDevice
Ethernet Switching Device Set EthernetSwitchDeviceSet
Ethernet Switching Device EthernetSwitchDevice
Special Operation & Maintenance VsOam
OMC Channel ItfUniBts
Operator Operator
Plmn Plmn
Transport Network TransportNetwork
Physical Layer Port PhyLayerPort
DHCP Relay DhcpRelay
ATM Layer Link AtmLayerLink
AAL2 Aal2
SaalUni SaalUni
ALCAP Alcap
Bts Cascade BtsCascade
HDLC Channel Hdlc
PPP Link PppLink
Ethernet Link Layer EthernetLink
Ethernet Fault Detection EthernetOam
Bandwidth Control Rule BandwidthCtrlRule
IP Layer IpLayerConfig
IKE Policy IKEPolicy
IPSec Proposal IPSecTransformSet
Access Control Rule AccessControlList
IPSec Config IPSecConfig
Certificate Management Protocol ConfigurationCmpConfig
Qos Mapping QosMap
SCTP Sctp
Ethernet Maintenance Domain EthernetCfmMd
<> 529 , 2
ZTE
Ethernet Maintenance Association EthernetCfmMa
Ethernet Maintenance Point EthernetCfmMp
Bidirectional Forwarding Detection Bfd
IP Clock IpClockProfile
NodeBFunction NodeBFunction
UMTS Reserve Parameter NodeBFunctionReservePara
Iub Interface IubLink
Service Plane at Iub IubDataStream
NBAP Common Signalling NbapCSignalling
NBAP Dedicated Signalling NbapDSignalling
UMTS Sector USector
UMTS Local Cell ULocalCell
Local Cell Reserve Parameter ULocalCellReservePara
UMTS Dual-carrier Cell Relation ULocalCellRelation
BtsFunction BtsFunction
Abis Interface AbisLink
Control Plane at Abis BtsM
Local Switch HubBtsConfig
GSM Cell Channel Resource GCellEquipmentFunction
GSM Cell GCell
GSM Carrier Frequency GTrx
<> 529 , 3
ZTE
Remark
Equipment Object
If this MO attribute has no special configuration, it is unnecessary to fill in the
options. If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
Multimode circumstances can be manually configured radioMode. If this MO attribute has no special configuration, it is unnecessary to fill in the
options. If this MO attribute has no special configuration, it is unnecessary to fill in the
options. If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
If this MO attribute has no special configuration, it is unnecessary to fill in the
options. If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
If this MO attribute has no special configuration, it is unnecessary to fill in the
options. If this MO attribute has no special configuration, it is unnecessary to fill in the
options. If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
If this MO attribute has no special configuration, it is unnecessary to fill in the
options.
<> 529 , 4
ZTE
UMTS radio parameter
NodeBFunctionReservePara
GSM radio parameter
<> 529 , 5
ModInd
OMCSUBNE
TID
SDRMEID USERLABEL NODEBMEADDR
Modify
Indication
Subnet ID
ManagedElement
ID
ManagedElement
User Label
ManagedElemen
t IP Address
A,D,M,P long:[0..4095] long:[0..65535] string:[1..80] string:[7..15]
A:Add,
P:Pass
Does not
support the
modification.
Same in an
OMMB.
Can fill in with
1 during LMT
importing.
Unique in
subnetwork.
Can fill in with 1
during LMT
importing.
Cannot use the
invalid characters,
e.g. < > & ' " \ / : * ? |
# % @ ,
IPV4.
Unique in whole
network.
Can fill in with
0.0.0.0 during
LMT importing.
Return To
Index
Primary Key Primary Key R-W R-W
117 35 ZZ_BTS35_RSU02_Mirdoddi 118.117.35.100
NODEBMETYPE SWVERSION RNCID GBSCID
ManagedElement Type Model Version RNC ID GSM BSC ID
102:ZXSDR BS8700,
110:ZXSDR BS8900A,
111:ZXSDR BS8800 U120,
112:ZXSDR BS8800 U240,
113:ZXSDR BS8800
GU360,
115:ZXSDR BS8900 U240,
116:ZXSDR BS8900
GU360,
118:ZXSDR BS8906,
123:ZXSDR BS8908,
124:ZXSDR BS8800
U120A,
125:ZXSDR BS8900
string:[1..128]
<default:v11.02.0
1>
long:[0..65535] long:[0..65535]
Format:
v11.02.01
It is unnecessary to
fill in the option in
GSM single mode
site.
65535:Invalid.
It is unnecessary to
fill in the option in
UMTS single mode
site.
65535:Invalid.
R-I R-W R-W R-W
116 v11.02.01 65535 65535
LONGITUDE LATITUDE
LOCATIONN
AME
VENDORNA
ME
Longitude Latitude Location
Vendor
Name
double:[-
180.000000..180.000000]
double:[-
90.000000..90.000000]
string:[0..40] string:[0..40]
R-W R-W R-W R
180.0 90.0
USERDEFINEDST
ATEV4
PRIORITY
MAINTAINSTAT
US
ADMINISTRATIVESTA
TE
User Defined
State
Priority Maintain Status Link Status
string:[0..80]
long:[1..5]
<default:1>
long:[0..1]
<default:0>
long:[0..1]
<default:1>
0:Normal
1:Testing
0:Release Connection
1:No Release
Connection
R-W R R R
1 0
ZTE
ModInd OMCSUBNETID SDRMEID bbuStackMode
Modify
Indication
Subnet ID ManagedElement ID BBU Stack Mode
A,P long:[0..4095] long:[0..65535]
0:Non-stack,
1:Master-slave frame stack
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Single site can use 2 BBU frames. The stack
mode can extend the capacity and covering
power of single site.
In stack mode, the 2 BBU frames are a site
for service, operation maintenance,
transmission and clock functions; in non-
stack mode, only 1 BBU frame exists, and the
frame number is 1.
To make the modification of this attribute
effective, you need to restart the base station.
Return To
Index
Primary Key Primary Key R-I
117 35 0
<> 529 , 10
ZTE
userLabel operatorPlannedId vendorPlannedId subRackType
User Label
Network Element
ID planned by
operator
Network Element
ID planned by
vendor
BBU/DIET SubRack
Type
string:[0..128]
{ManagedElement_o
peratorPlannedId}
string:[0..48]
{ManagedElement
_vendorPlannedId}
string:[0..48]
{SubRack_subRackType}
0:BBU-2U,
4:BBU-3U,
5:DIET
User can add some
equipment description
information as required.
Cannot use the invalid
characters, e.g. < > & ' "
\ / : ? # % @
Operator plans the
unique network
element ID for base
station. Users
cannot set the option
if it is not be planed.
Vendor plans the
unique network
element ID for
base station.
Users cannot set
the option if it is
not be planed.
Support BBU-2U and
BBU-3U subrack.
R-W R-W R-W R-I
0
<> 529 , 11
ZTE
adminState
Manual Operation Field
0:No Manual Operation,
1:Block,
2:Disabled,
4:Powered-down,
65536:Block Smoothly
<default:0>
This field can not be
configured. Do not modify
it.
R-W
0
<> 529 , 12
ModInd OMCSUBNETID SDRMEID RackId rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack ID Rack No.
A,P long:[0..4095] long:[0..65535] long:[1..65535] long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
This field can not be
configured. Do not
modify it.
The Rack No. of the
master rack is fixed as
1. The value range
[2..50] is used to
identify the racks that
bear RSU RF boards in
macro or micro base
stations. The value
range [51..201] is used
to indicate all RRU
racks.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 1
117 35 2 2
117 35 3 3
117 35 4 4
117 35 5 5
117 35 6 6
117 35 7 7
cabinetData_productName cabinetPosition userLabel
Cabinet Type Info Cabinet Position User Label
string:[0..201] string: [0..128]
{SubRack_userLabel
}
string: [0..128]
ZXSDR B8200,
ZXSDR BC8810,
ZXSDR BC8810A,
ZXSDR BC8811,
ZXSDR BC8910,
ZXSDR BC8910A,
ZXSDR BC8912,
ZXSDR RC8910,
ZXSDR RC8911,
ZXSDR RC8931,
ZXSDR BC8910A-SC,
ZXSDR BS8908 G060,
ZXSDR RC8810,
ZXSDR Z02USG-1,
"1" refers to primary
cabinet, others refers to
secondary cabinet. Fill in a
value from 1 to 255. Other
values or characters are
not allowed.
User can add some
subrack description
information as
required.
Cannot use the
invalid characters,
e.g. < > & ' " \ / : ?
# % @ ,
R R R-W
ZXSDR BC8910 1
ZXSDR RC8910 2 ZXSDR RSU60(2)
ZXSDR RC8910 2 ZXSDR RSU60(3)
ZXSDR RC8910 2 ZXSDR RSU60(4)
ZXSDR RC8910 2
ZXSDR RC8910 2 ZXSDR RSU60(6)
ZXSDR RC8910 2
ZTE
ModInd OMCSUBNETID SDRMEID rackNo subRackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No. SubRack No.
A,P long:[0..4095] long:[0..65535] long:[1..201] long:[1..2]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
The Rack No. of the
master rack is fixed
as 1. The value range
[2..50] is used to
identify the racks that
bear RSU RF boards
in macro or micro
base stations. The
value range [51..201]
is used to indicate all
RRU racks.
In non-stack
mode, can not
fill in with 2.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
117 35 1 1
117 35 1 1
117 35 1 1
117 35 1 1
117 35 1 1
117 35 1 1
117 35 2 1
117 35 2 1
117 35 4 1
117 35 6 1
<> 529 , 15
ZTE
slotNo
productData_product
Name
ctrlAuxCabinetNo isHighPriority
Slot No. Board Name
Controlled Auxiliary Abinet
No
Whether high
priority
long:[1..23] string:[0..201] long:[2..255]
1:Y,
0:N
<default:0>
For some boards, the
slot where they are
inserted is fixed and
can not modified.
CC board in slot 1, SA
board and PM board
should be configured.
Name of
corresponding board.
CC,
CCC,
FS,
BPC,
BPK,
BPK_s,
UBPG,
UBPG2,
UBPG3,
BPL,
Fill out the attribute for the
FCE in an auxiliary cabinet.
The auxiliary cabinet is only
used by FCE boards, which
provide cooling function for
the devices of other
manufacturers.The
ctrlAuxCabinetNo can not be
duplicate, it also can not be
the same as cabinetPosition
of Rack object.
The power-supply
level needed by the
board. The default
priority is low. When
load is shared, NE is
allocated
automatically
according to the
enhanced load
sharing algorithm. In
OMMB, it can be
manually adjusted to
Primary Key R-I R R-W-I
1 CC 0
3 FS 0
5 SE 0
8 UBPG 0
13 SA 0
14 PM 0
1 RSU02-G182 0
7 FCE 0
1 RSU02-G182 0
1 RSU02-G182 0
<> 529 , 16
ZTE
adminState
Manual Operation Field
0:No Manual Operation,
1:Block,
2:Disabled,
4:Powered-down,
65536:Block Smoothly
<default:0>
This field can not be
configured. Do not modify
it.
R-W
0
0
0
0
0
0
0
0
0
0
<> 529 , 17
ZTE
ModInd OMCSUBNETID SDRMEID ntpServerIpAddr
Modify
Indication
Subnet ID ManagedElement ID NTP Server IP Address
A,P long:[0..4095] long:[0..65535]
ipv4
<default:0.0.0.0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
The address of the NTP
server. The base station
gets the NTP time from the
server.
Return To
Index
Primary Key Primary Key R-W-I
117 35 139.117.0.250
<> 529 , 18
ZTE
timeZone clockSynPeriod summTimeStart summTimeEnd
Time Zone
Clock Synchronization
Period
Summer Time
Start
Summer Time
End
0:GMT - 12:00,
2:GMT - 11:00,
4:GMT - 10:00,
6:GMT - 9:00,
8:GMT - 8:00,
10:GMT - 7:00,
long:[1..48]
<default:24>
string:[0..20] string:[0..20]
Indicates the time zone of the
base station.
Indicates the time
synchronization interval.
The base station
performs time
synchronization with the
NTP at this interval. Unit:
hour.
Format: MM-DD
HH:mm.
Indicates the
start time of
summer time. It
is allowed that
the summer
time is a cross-
year range.
Format: MM-
DD HH:mm.
Indicates the
end time of
summer time. It
is allowed that
the summer
time is a cross-
year range.
R-W-I R-W-I R-W R-W
35 24
<> 529 , 19
ZTE
isSuppSummTime
Support Summer
Time or not
1:Y,
0:N
<default:0>
Indicates whether to
enable summer time.
R-W-I
0
<> 529 , 20
ZTE
ModInd OMCSUBNETID SDRMEID ClockDeviceId clockType
Modify
Indication
Subnet ID ManagedElement ID RDN
Clock Reference
Source Type
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
1: Internal GNSS,
3: External GNSS,
5: Cascade GNSS,
4: 1PPS+TOD,
6: BITS-2MHz,
7: BITS-2Mbps,
8: Line,
11: 1588,
13: SyncE
<default:1>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 1
<> 529 , 21
ZTE
clockPriority clockSyncMode switchThreshold
Priority Clock Synchronization Mode Clock Reference Switch Threshold
long:[1..8]
<default:1>
0: GSM/UMTS Frequency Sync,
1: GSM FrameNumber Sync.
UMTS Frequency Sync,
2: GSM Frequency Sync. UMTS
FrameNumber Sync,
3: GSM/UMTS FrameNumber
Sync
long:[0..86400]
"1": indicates the
highest priority.
This attribute indicates the
mode used by the clock module
for extracting the GNSS clock.
The frame number
synchronization mode has a
higher precision than the
frequency synchronization
mode.
Unit: s
This attribute indicates that if the current clock
reference failed, the time gap when the current
reference changed to the backup reference.
{ClockDevice.clockType == 11}[30..86400],
{ClockDevice.clockType == 13}[0..86400],
{ClockDevice.clockType == 8}[0..86400],
{ClockDevice.clockType == 6}[0..86400],
{ClockDevice.clockType == 7}[0..86400],
{ClockDevice.clockType == 1}[300..86400],
{ClockDevice.clockType == 3}[300..86400],
{ClockDevice.clockType == 4}[300..86400],
{ClockDevice.clockType == 5}[300..86400]
R-W-I R-W R-W
1 0 300
<> 529 , 22
ZTE
gnssClockData_cableDel
ay
gnssClockData_cableT
ype
gnssClockData_receiverType
Length of GNSS
Antenna Feeder Cable
GNSS Cable Type GNSS Receiver Type
long: [0..8000]
0: Multiplexing input,
1: Distribution input
1:GPS,
2:GLONASS,
3:GPS+GLONASS
Unit: meter.
This attribute indicates
the length of the feeder
that connects the GNSS
antenna and the
receiver. This feeder is
used to improve the
clock precision. This
attribute should be set
according to the result of
the site survey.
General value:0
This attribute indicates
the type of cable used
for GNSS clock
cascade. The cable
type must be set
according to the cable
actually used on site.
The devices on both
ends of the cascade
cable must be set with
the same cable type.
General value:0
General value:1
R-W R-W R-W
0 0 1
<> 529 , 23
ZTE
gnssClockData_frmMajorAlmThres gnssClockData_frmCritiAlmThres
Major Alarm Threshold of GNSS Clock
Reference Source Lost during Frame
Number Synchronization
Critical Alarm Threshold of GNSS
Clock Reference Source Lost
during Frame Number
{gnssClockData_frameMajorAlarmThres}
long: [20..4320]
{gnssClockData_frameCriticalAlarmT
hres}
long: [1..168]
Unit: minute,step: 20.
This attribute indicates the threshold for
reporting a major alarm when the GNSS
clock reference source is lost during frame
number synchronization. In the case of
threshold crossing, a major alarm, "loss of
GNSS clock reference source", is raised.
General value:20
Unit: hrs.
This attribute indicates the threshold
for reporting a critical alarm when the
GNSS clock reference source is lost
during frame number synchronization.
In the case of threshold crossing, a
critical alarm, "loss of GNSS clock
reference source", is raised.
General value:8
R-W R-W
20 8
<> 529 , 24
ZTE
gnssClockData_freCritiAlmThres gnssClockData_revOperatingMode
gnssClockData_longitu
de
Critical Alarm Threshold of GNSS
Clock Reference Source Lost during
Frequency Number Synchronization
Receiver Operating Mode
Longitude of Reciver
Antenna
{gnssClockData_freqCriticalAlarmThres}
long: [1..180]
{gnssClockData_receiverOperatingMo
de}
1:Survey In,
2:Fixed Mode
double:[-
180.000000..180.0000
00]
Unit: day.
This attribute indicates the threshold for
reporting a critical alarm when the
GNSS clock reference source is lost
during frequency synchronization. In the
case of threshold crossing, a critical
alarm, "loss of GNSS clock reference
source", is raised.
General value:90
This attribute indicates the operating
mode of the GNSS receiver. "Fixed
Mode" is recommended when the
number of satellites detected by the
receiver antenna is smaller than 4.
"Survey In" is recommended when the
GNSS receiver of the base station is
cascaded to an upper-level receiver.
General value:1
When the operating
mode of the receiver is
"Fixed Mode", this
attribute indicates the
longitude of the
receiver antenna,
which helps the
receiver to obtain the
satellite clock.
General value:0
R-W R-W R-W
90 1 0.0
<> 529 , 25
ZTE
gnssClockData_latitu
de
gnssClockData_altitude
gnssClockData_minStarN
um
Latitude of Reciver
Antenna
Height of Reciver
Antenna
Mimimum Number of
Search Star
double:[-
90.000000..90.00000
0]
long: [0..10000] long: [1..4]
When the operating
mode of the receiver
is "Fixed Mode", this
attribute indicates the
latitude of the receiver
antenna, which helps
the receiver to obtain
the satellite clock.
General value:0
Unit: meter.
When the operating
mode of the receiver is
"Fixed Mode", this
attribute indicates the
altitude of the receiver
antenna, which helps the
receiver to obtain the
satellite clock.
General value:0
When the operating mode
of the receiver is "Fixed
Mode", this attribute
indicates the minimum
number of detected
satellites that are required
for the receiver to
precisely obtain the
satellite clock.
General value:4
R-W R-W R-W
0.0 0 4
<> 529 , 26
ZTE
gnssClockData_enableCasOutput gnssClockData_casCableDelay
Support Clock Cascade Output or
not
Length of Cascade Cable
{gnssClockData_enableCascadeOut
put}
0:Not support,
1:Support
{gnssClockData_cascadeCableDel
ay}
long: [0..15]
In the case of clock cascade, the
switch in the upper-level receiver
must be enabled. The switch in the
lower-level receiver must be
disabled, and the clock reference
source must be set to "Cascade
GNSS".
General value:0
Unit: meter.
This attribute indicates the length
of cable used for clock cascade.
The cable length can be used to
improve the clock precision. This
attribute should be set according to
the result of the site survey.
General value:0
R-W R-W
0 0
<> 529 , 27
ZTE
isSSM
tod1PpsData_cascadeCableLengt
h
Enable SSM or not Length of Cascade cable
1:Y,
0:N long:[0..15]
It is valid when clockType is SyncE.
Indicates parameters for SyncE clock.
Indicates whether the clock upload mode is
Synchronization Status Message (SSM).
SSM is the quality level for sending timing
signals through the timing synchronization
link in the synchronization network. The
clock of a node in the synchronization
network gets the parent-node clock
information by reading the SSM, and
performs relevant operations on the node
clock, such as tracing, changeover, while
sending the synchronization message to the
subordinate node.
General value:1
Unit: meter
This attribute indicates the length
of cable used for clock cascade.
The cable length can be used to
improve the clock precision. This
attribute should be set according to
the result of the site survey.
General value:0
R-W R-W
<> 529 , 28
ZTE
tod1PpsData_inputBardRate tod1PpsData_timeInputType
Input Baud Rate Time Input Type
0:115200,
1:57600,
2:38400,
3:19200,
4:9600,
5:4800,
6:2400
0:Multiplexing input,
1:Distribution input
Indicates parameters for
1PPS+TOD clock.
General value:4
Clock receiving type configuration is used
to distinguish multiplexing input and
distribution input. If upper level is
multiplexing output, the lower level should
be configured as multiplexing input; if
upper level is distribution output, the lower
level should be configured as distribution
input. Faulty configuration may not get the
1pps+tod signal.
General value:1
R-W R-W
<> 529 , 29
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rack
No}
long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 2
117 35 2
117 35 2
117 35 2
<> 529 , 30
ZTE
subRackNo slotNo DryContactDeviceId dryNo
SubRack No. Slot No. RDN Dry Contact No.
{SdrDeviceGroup_subRack
No}
long:[1..2]
{SdrDeviceGroup_slot
No}
long:[1..23]
long:[1..4294967295
]
long:[0..255]
<default:0>
Generated
automatically, it is
unnecessary to fill in
this column.
Primary Key Primary Key Primary Key R-I
1 5 1 0
1 5 2 1
1 5 3 2
1 5 4 3
1 13 1 1
1 13 2 2
1 13 3 3
1 13 4 4
1 13 5 5
1 13 6 6
1 13 7 7
1 13 8 0
1 7 1 0
1 7 2 2
1 7 3 3
1 7 4 4
<> 529 , 31
ZTE
dryType outDryType outDryName almStatus isSelfDefineAlm
Dry Contact Type
Output Dry Contact
Status
Output Dry
Contact
Name
Alarm Status
Is Self-defined Dry
Contact or not
0: Input dry contact,
1: Output dry contact
<default:0>
0: Output low level,
1: Output high level
string: [0..127]
0: Alarm appears if
contact is closed,
1: Alarm appears if
contact is open
1:Y,
0:N
Dry contact number
for input or output.
Output dry contact is
valid.
General value: 0
Output dry
contact
description. It
is valid when
the dry contact
type is output.
The dry contact is
valid when the type
is input.
General value: 0
It is valid when the
dry contact type is
input. The self-
defined dry contact
needs to be imported
by user. General
value: 0
R-I R-W R-W R-W R-W
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 1 0
0 1 0
0 0 0
0 0 0
<> 529 , 32
ZTE
almNo userLabel
Dry Contact Alarm No. User Label
long string:[0..128]
The dry contact is valid when the
type is input.
The customized dry contact ID must
be from 198092550 to 198092599,or
from 198096424 to 198096473.
Non-self-defined dry contact range:
198092044:Door control alarm,
Cannot use the
invalid
characters, e.g.
< > & ' " \ / : ?
# % @ ,
R-W R-W
198092266
198092262
198092268
198092259
198092264
198092265
198092206
198092208
198092044
198092046
198092045
198092207
198092049
198092044
198092045
198092046
<> 529 , 33
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rack
No}
long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 2
<> 529 , 34
ZTE
subRackNo slotNo EnvMonDeviceId
SubRack No. Slot No. RDN
{SdrDeviceGroup_subRack
No}
long:[1..2]
{SdrDeviceGroup_slot
No}
long:[1..23]
long:[1..4294967295]
Generated
automatically, it is
unnecessary to fill in
this column.
Primary Key Primary Key Primary Key
1 1 1
1 1 3
1 1 4
1 1 2
1 13 1
1 13 2
1 13 3
1 14 1
1 14 2
1 14 3
1 7 1
<> 529 , 35
ZTE
thresType upperLimit lowerLimit
Threshold Type
Upper Limit
Value
Lower Limit Value
1:Board temperature,
2:Environment temperature,
3:Base Station temperature,
6:Humidity,
7:Fan speed level,
8:MP Voltage,
9:PP Voltage,
10:Temperature at air inlet,
11:Temperature at air outlet,
12:DC input voltage of PM board,
17:Temperature of cabinet,
200:Temperature rise of low
temperature CC board,
201:Temperature rise of high
temperature CC board,
202:Temperature rise of low
long long
R-I R-W R-W
2 55 -20
200 30 27
201 25 23
1 90 80
7 65535 200
10 55 -20
11 70 -5
202 70 67
203 70 67
12 60 40
7 65535 200
<> 529 , 36
ZTE
upperResumeLimit lowerResumeLimit
Alarm Recovery Upper Limit Alarm Recovery Lower Limit
long long
Specifies the value for clearing
an alarm raised when the
uppper environment threshold is
exceeded. The user can modify
the value.
Specifies the value for clearing
an alarm raised when the
actual value is below the lower
environment threshold. The
user can modify the value.
R-W R-W
87 77
55 -20
70 -5
58 42
<> 529 , 37
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rack
No}
long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 1
117 35 2
117 35 2
117 35 4
117 35 4
117 35 6
117 35 6
<> 529 , 38
ZTE
subRackNo slotNo FiberDeviceId port
SubRack No. Slot No. RDN
Connected
Board Port ID
{SdrDeviceGroup_subRack
No}
long:[1..2]
{SdrDeviceGroup_slotN
o}
long:[1..23]
long:[1..429496729
5]
long: [0..5]
<default:0>
Generated
automatically, it is
unnecessary to fill
in this column.
Primary Key Primary Key Primary Key R-I
1 3 1 0
1 3 2 1
1 3 3 2
1 3 4 3
1 3 5 4
1 3 6 5
1 1 1 1
1 1 2 2
1 1 1 1
1 1 2 2
1 1 1 1
1 1 2 2
<> 529 , 39
ZTE
opticalModuleType
Type of Optical Model
1:1.25G,
2:2.5G,
3:3G,
6:6G
<default:1>
In stack mode, the default
values of FS(slot 3) boardand
optical port No.3 optical port
No.4 and optical port No.5
are 2.5G.
R-W-I
1
1
1
1
1
1
1
1
1
1
1
1
<> 529 , 40
ZTE
ModInd OMCSUBNETID SDRMEID FiberCableId
Modify
Indication
Subnet ID ManagedElement ID RDN
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key
117 35 1
117 35 3
117 35 4
<> 529 , 41
ZTE
ref1FiberDevice_rackNo
ref1FiberDevice_subRack
No
ref1FiberDevice_slotN
o
ref1FiberDevice_port
Upper-level Rack No. of
Previous Hop in
Topology Structure
Upper-level SubRack No.
of Previous Hop in
Topology Structure
Upper-level Slot No.
of Previous Hop in
Topology Structure
Optical Port of
Previous Hop in
Topology Structure
long: [1..201] long: [1..2] long: [1..8] long: [0..5]
R-I R-I R-I R-I
1 1 3 0
1 1 3 2
1 1 3 4
<> 529 , 42
ZTE
ref2FiberDevice_rackNo
ref2FiberDevice_subRack
No
ref2FiberDevice_slotN
o
ref2FiberDevice_port
Lower-level Rack No.
of Next Hop in
Topology Structure
Lower-level SubRack No.
of Next Hop in Topology
Structure
Lower-level Slot No.
of Next Hop in
Topology Structure
Optical Port of Next
Hop in Topology
Structure
long: [1..201] long: [1..2] long: [1..8] long: [0..5]
R-I R-I R-I R-I
2 1 1 1
4 1 1 1
6 1 1 1
<> 529 , 43
ZTE
ModInd OMCSUBNETID SDRMEID TmaId tmaNo
Modify
Indication
Subnet ID ManagedElement ID RDN TMA No.
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
long:[1..96]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 44
ZTE
tmaType ulGain dlGain tmaNoise
TMA Type Uplink Gain Downlink Gain TMA Noise Figure
0:TMA,
3:A-TMA,
4:A-COM,
5:ETMA,
6:A-ETMA
long: [0..65535]
long:
[70..170,255]
<default:255>
long: [10..30,255]
<default:20>
A-TMA corresponds to
AISG TMA;
A-COM corresponds to
AISG Combiner;
TMA corresponds to
common TMA;
ETMA corresponds to
high gain common TMA;
A-ETMA corresponds to
high gain AISG TMA.
The unit for different TMA
types: A-TMA: 0.25dB, A-
COM: 0.5dB, TMA: 0.1dB,
ETMA: 0.1dB, A-ETMA:
0.25dB.
{tmaType==0}[70..150],
{tmaType==3}[44..100],
{tmaType==4}[0..14],
{tmaType==5}[200..320],
{tmaType==6}[92..100],
65535:{Invalid}
General value
{tmaType==0}[120],
Unit: 0.1dB
255: invalid.
Unit: 0.1dB
255: invalid.
R-I R-W-I R-I R-W-I
<> 529 , 45
ZTE
dlDelay ulDelay
Downlink Delay Uplink Delay
long: [0..100]
<default:0>
long: [0..100]
<default:0>
Unit: ns Unit: ns
R-W-I R-W-I
<> 529 , 46
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID RU Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rackN
o}
long: [1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 2
117 35 2
117 35 4
117 35 4
117 35 6
117 35 6
<> 529 , 47
ZTE
PaDeviceId port power suppBand
RDN Port ID
Power
Rating(W)
Frequency Band
ID
long:[1..4294967295] long:[0..255] long:[1..255]
1:2.1G(Band I),
2:1900M(Band II),
3:1800M(Band III),
4:AWS(Band IV),
5:850M(Band V),
6:850M(Band VI),
7:2.6G(Band VII),
8:900M(Band VIII),
9:1800M(Band IX)
<default:1>
Generated
automatically, it is
unnecessary to fill in
this column.
Indicates the
rated power, or
maximum power
for the power
amplifier.
Indicates the
working frequency
band supported by
the power amplifier.
Refer to 3GPP for
frequency band
definition.
Primary Key R-I R-I R-I
1 1 20 3
2 2 20 3
1 1 20 3
2 2 20 3
1 1 20 3
2 2 20 3
<> 529 , 48
ZTE
branchBand thresType upperLimit lowerLimit
Sub Frequency Band Threshold Type
VSWR Upper
Limit
VSWR Lower
Limit
1,
2,
3,
255:Invalid
<default:255>
4: Level-1 VSWR
threshold
<default:4>
long long
Indicates the sub-frequency
band within the frequency band
supported by the power
amplifier.
Sub-frequency band is an
attribute unique to the GSM
system. Only the RU of 900M
and 1800M has sub-frequency
bands.
900M(Band VIII) includes the
Indicates the alarm-
generating threshold
type for the Voltage
Standing Wave
Ratio (VSWR) of
the power amplifier.
R-W-I R-I R-W-I R-W-I
255 4 300 150
255 4 300 150
255 4 300 150
255 4 300 150
255 4 300 150
255 4 300 150
<> 529 , 49
ZTE
upperResumeLimit lowerResumeLimit radioMode#1 radioMode#2 radioMode#3
Alarm Recovery
Upper Limit of VSWR
Alarm Recovery
Lower Limit of
VSWR
Radio Mode
1
Radio Mode 2 Radio Mode 3
long long
1:UMTS,
2:GSM,
16:LTE
1:UMTS,
2:GSM,
16:LTE
1:UMTS,
2:GSM,
16:LTE
Cannot be the
same with
previous
column.
Cannot be the
same with
previous
column.
R-W R-W R-W-I R-W-I R-W-I
290 140 2
290 140 2
290 140 2
290 140 2
290 140 2
290 140 2
<> 529 , 50
ZTE
dualMode powerOffSwitch
Dual Mode PA Power Off At Free Slot
1:4G+1U,
2:2G+2U,
3:4G+1L,
4:2G+1L,
5:4G+2U,
255:Invalid
<default:255>
0:Close,
1:Open
<default:0>
It is valid during double
mode.Indicates the allocation
method of amplifier resources
in dual-mode. 2G+2U: the
amplifier supports 2GSM
carriers and 2 UMTS cells.
While this switch is open,PA
can be powered off when the
slot is free and no data to
transmit, thus electric energy is
saved.
R-W-I R-W-I
255 0
255 0
255 0
255 0
255 0
255 0
<> 529 , 51
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID RU Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rackNo}
long: [1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 2
117 35 2
117 35 4
117 35 4
117 35 6
117 35 6
<> 529 , 52
ZTE
TxDeviceId port txCenterFreq detectSwitch
RDN Port ID Tx Central Frequency
Enable Primary
Diversity Balance
Detection or not
long:[1..4294967295] long:[1..5]
double
<default:0>
1:Y,
0:N
<default:0>
Generated
automatically, it is
unnecessary to fill in
this column.
0,
PaDevice.suppBand==1{[2100.0..2180.0]}
,
PaDevice.suppBand==2{[1920.0..2000.0]}
,
PaDevice.suppBand==3{[1795.0..1890.0]}
,
PaDevice.suppBand==4{[2100.0..2165.0]}
,
PaDevice.suppBand==5{[859.0..904.0]},
PaDevice.suppBand==6{[865.0..895.0]},
PaDevice.suppBand==7{[2610.0..2700.0]}
,
PaDevice.suppBand==8{[915.0..970.0]},
PaDevice.suppBand==9{[1834.9..1989.9]}
Unit:MHz
Primary Key R-I R-W-I R-W-I
1 1 0.0 0
2 2 0.0 0
1 1 0.0 0
2 2 0.0 0
1 1 0.0 0
2 2 0.0 0
<> 529 , 53
ModInd
OMCSUBNET
ID
SDRMEID rackNo
Modify
Indication
Subnet ID
ManagedEleme
nt ID
RU Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGr
oup_rackNo}
long: [1..201]
A:Add, P:Pass
Same in an
OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 2
117 35 4
117 35 6
diversityMode
Diversity Receiving Mode
0:Normal diversity reception,
1:Cross diversity reception
<default:0>
Configure RU diversity receiving mode.
"Cross diversity reception" indicates that the
signals received by two receiving channels
are mutually active/standby diversities. In this
case, the dual-transmitting RU is required and
only two receiving/transmitting antennas are
connected.
R-W-I
0
0
0
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID RU Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rackNo}
long: [1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 2
117 35 2
117 35 4
117 35 4
117 35 6
117 35 6
<> 529 , 56
ZTE
RxDeviceId port rxCenterFreq
RDN Rx Port ID Rx Central Frequency
long:[1..4294967295] long:[1..6]
double
<default:0>
Generated
automatically, it is
unnecessary to fill in
this column.
0,
PaDevice.suppBand==1[1910.0..1990.0],
PaDevice.suppBand==2[1840.0..1920.0],
PaDevice.suppBand==3[1700.0..1795.0],
PaDevice.suppBand==4[1700.0..1765.0],
PaDevice.suppBand==5[814.0..859.0],
PaDevice.suppBand==6[820.0..850.0],
PaDevice.suppBand==7[2490.0..2580.0],
PaDevice.suppBand==8[870.0..925.0],
PaDevice.suppBand==9[1739.9..1794.9]
Unit:MHz
The attribute is not open to the user. When
it is set to 0, the calculation if automatically
performed. In special cases when this
parameter needs modification, you can
contact ZTE personnel.
Primary Key R-I R-W-I
1 1 0.0
2 2 0.0
1 1 0.0
2 2 0.0
1 1 0.0
2 2 0.0
<> 529 , 57
ZTE
ModInd OMCSUBNETID SDRMEID RetId height
Modify
Indication
Subnet ID ManagedElement ID RDN Height
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
string
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
it is necessary to
fill in this column.
Base station code
starts from 1,2,3
Unit:metre
The height of an
antenna above sea
level.
Return To
Index
Primary Key Primary Key Primary Key R-W
<> 529 , 58
ZTE
baseElevation latitude longitude
Base Elevation Latitude Longitude
string
double: [-
90.000000..90.000000]
double: [-
180.000000..180.000000]
Unit:metre
The elevation in meters
above sea level at the base
of the antenna structure.
This value, when
subtracted from height,
provides the height of the
antenna above the ground.
Unit:metre
The latitude of the
antenna location based
on World Geodetic
System (1984 version)
global reference frame
(WGS 84). Positive
values correspond to the
northern hemisphere.
Unit:degree
The longitude of the
antenna location based on
World Geodetic System
(1984 version) global
reference frame (WGS
84). Positive values
correspond to degrees
east of 0 degrees
longitude.
R-W R-W R-W
<> 529 , 59
ZTE
patternLabel spaceDiversity typeDiversity vertBeamwidth
Pattern Label Space Diversity Type Diversity Vertical Beamwidth
string string
1:Omnidirectional
Diversity,
2:Panel Diversity,
3:Sectorized Diversity
string:[0..3600]
The pattern name is a
textual, alpha-numeric
string to allow identification
of the antenna pattern
along with the antenna
vendor information such as
model number, etc.
Unit:metre
Distance between
antennas in the
same sector (space
diversity case),
measured in meters.
The 3 dB power
beamwidth of the
antenna pattern in the
vertical plane.
R-W R-W R-W R-W
<> 529 , 60
ZTE
ModInd OMCSUBNETID SDRMEID RfCableId connectType
Modify
Indication
Subnet ID ManagedElement ID RDN Connection Type
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
1:Tx,
2:Rx,
3:Tx/Rx,
4:Rx RF Extend
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 3
117 35 2 3
117 35 5 3
117 35 6 3
117 35 7 3
117 35 8 3
<> 529 , 61
ZTE
dlAttenuation ulAttenuation dlDelay ulDelay
refTxDevice_rack
No
Downlink
Attenuation
Uplink Attenuation Downlink Delay Uplink Delay
Connected Tx
RU Rack No.
double:
[0.0..8.0]
double: [0.0..8.0]
long: [0..1000] long: [0..1000]
long:[1..201]
Accurate to the
tenth's place.
Unit: dB.
General
value:0
Accurate to the tenth's
place. Unit: dB.
Uplink attenuation of
RF cable. When RF
cable is used to
connect RU and TAM,
the General value is
0.5dB, other cases, the
General value is 0dB.
Unit: ns.
General value:0
Unit: ns.
General
value:0
It is valid when
connection type is
1, and 3.
R-W R-W R-W R-W R
2
2
4
4
6
6
<> 529 , 62
ZTE
refTxDevice_port refMechanicalAnt refRet refTma_tmaNo
ref1RxDevice_rack
No
Connected Tx
Port
Connected
Mechanical Antenna
Connected RET
Antenna RDN
Connected TMA
Device
Connected Rx RU
Rack No.
long:[1..5] long:[1..4294967295] long:[1..4294967295] long: [1..96] long:[1..201]
It is valid when
connection type is
1, and 3.
It is valid when
connection type is 1, 2,
and 3. Base station
code starts from
1,2,3 The connected
ANT and RET are
mutually excluded.
Configure as "RetId"
of Ret object..
It is valid when
connection type is 1,
2, and 3. The
connected ANT and
RET are mutually
excluded.
It is valid when
connection type is
2, and 3. TMA ID
and TMA exist.
It is valid when
connection type is
2, and 3.
R R R R R
1 1 2
2 2 2
1 5 4
2 6 4
1 9 6
2 10 6
<> 529 , 63
ZTE
ref1RxDevice_por
t
ref2RxDevice_rackN
o
ref2RxDevice_por
t
ref3RxDevice_rackN
o
ref3RxDevice_port
Connected Rx
Port
Connected Main Rx
Device Rack No.
Connected Main
Rx Device Port
Connected
Extended Rx Device
Connected Extended
Rx Device Port ID
long:[1..6] long:[1..201] long:[1..6] long:[1..201] long:[1..6]
It is valid when
connection type is
2, and 3.
It is valid when
connection type is 4.
It is valid when
connection type is
4.
It is valid when
connection type is 4.
It is valid when
connection type is 4.
R R R R R
1
2
1
2
1
2
<> 529 , 64
ZTE
ModInd OMCSUBNETID SDRMEID EPmId powerType
Modify
Indication
Subnet ID ManagedElement ID RDN Power Type
A,P long:[0..4095] long:[0..65535] long:[1..2]
0:ZXDU58 B900,
1:ZXDU58 B121,
2:ZXDU68 B201,
3:ZXDU150,
4:ZXDU45,
5:ZXDU75,
6:ZXDU58
B121(V4.5),
7:ZXDU68
B201(V5.0),
8:ZXDU68 W301,
9:ZXDU68 S301,
10:ZXDU58
B121(V2.2),
11:ZXDU68
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically,
it is
unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key R-W-I
117 35 1 1
<> 529 , 65
ZTE
dataProcessMode refSdrDeviceGroup_rackNo
refSdrDeviceGroup_subRac
kNo
Data Processing Mode
Connected Board Rack
No.
Connected Board
SubRack No.
0:Transparent transmission,
1:Parse
long: [1..201] long:[1..2]
Handling method used by the NE for data
(for example, alarms and configurations)
related to embedded power devices. If the
handling method is resolution, the NE only
analyzes the alarm data and send it to the
OMC or LMT. If the handling method is
transparent transmission, the NE transmits
the data only with no processing.
R-W R-I R-I
0 1 1
<> 529 , 66
ZTE
refSdrDeviceGroup_slot
No
Connected Board Slot
No.
long: [1..23]
R-I
13
<> 529 , 67
ModInd OMCSUBNETID SDRMEID rackNo subRackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No. SubRack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_r
ackNo}
long: [1..201]
{SdrDeviceGroup_subRack
No}
long:[1..2]
A:Add, P:Pass Unique in subnetwork.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
slotNo switchStatus voltage
Slot No. Switch Status Voltage
{SdrDeviceGroup_slotN
o}
long: [1..23]
0:Close,
1:AISG RS485,
2:NSBT RS485
0:14,
1:22,
4294967295:Invalid
Unit: V
Primary Key R-W R-W-I
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rackN
o}
long: [1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 70
ZTE
subRackNo slotNo PowerOutletDeviceId port
SubRack No. Slot No. RDN Port ID
{SdrDeviceGroup_subRack
No}
long:[1..2]
{SdrDeviceGroup_slotN
o}
long: [1..23]
long:[1..4294967295]
long: [0..5]
<default:0>
Generated
automatically, it is
unnecessary to fill in
this column.
The ports of
TAM board or
NSBTs inside
RSU.
Primary Key Primary Key Primary Key R-I
<> 529 , 71
ZTE
currentValue almDetectMode lowerLimitPercent
Work Current Value
Alarm Detect
Mode
Lower Current Alarm
Threshold Percent
long:[0..4294967295]
0:currentDetect,
1:pulsewidthDete
ct
long: [20..80,100]
<default:80>
Unit: mA.
Configure the maximum current value
of the specified port.
The value range of TAM0 board is
[75..300], General value: 250. The
value range of TAM1 board is
[75..400], General value: 120. The
value range of TAM2 board is
[75..400], General value: 175.
{PowerOutletDeviceSet.voltage ==
0}[75..400],
{PowerOutletDeviceSet.voltage ==
1}[75..300],
When the actual current
value of the TAM board's
power supply channel is
lower than the value of
(Working Current
Value*local value/100), low
current alarm is raised.
R-W-I R-W-I R-W-I
<> 529 , 72
ZTE
upperLimitPercent switchStatus
Over Current Alarm
Threshold Percent
Switch State
long: [100,120..180]
<default:120>
0:Close,
1:Open
<default:1>
When the actual current
value of the TAM board's
power supply channel is
higher than the value of
(Working Current Value*local
value/100), over current
alarm is raised.
R-W-I R-W-I
<> 529 , 73
ZTE
ModInd OMCSUBNETID SDRMEID subRackNo
Modify
Indication
Subnet ID ManagedElement ID PM Board SubRack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_subRack
No}
long:[1..2]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork. Return To
Index
Primary Key Primary Key Primary Key
117 35 1
<> 529 , 74
ZTE
slotNo operatingMode enablePowerDownCtrl
PM Board Slot No.
Power Working
Mode
Support Power-down or
not
{SdrDeviceGroup_slotNo
}
long: [1..23]
0:Master/slave mode,
1:Load-sharing mode
<default:0>
1:Y,
0:N
<default:0>
Primary Key R-I R-I
14 0 0
<> 529 , 75
ZTE
ModInd OMCSUBNETID SDRMEID imbAlarmSwitch
Modify
Indication
Subnet ID ManagedElement ID
Reception Ant
Imbalance Alarm
Switch
A,P long:[0..4095] long:[0..65535]
0:Close,
1:Open
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key R-W-I
117 35 0
<> 529 , 76
ZTE
antImbAlarmThreshold
antImbResumeThreshol
d
Ant Imbalance Alarm
Threshold
Ant Imbalance
Resume Threshold
long:[1..14] long:[1..14]
Unit: db
General value:10
Unit:db
General vlaue:10
R-W R-W
10 10
<> 529 , 77
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rackNo}
long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 78
ZTE
AisgDeviceId uniqueId devType vendorCode aisgVersion
RDN
Device Serial
Number
Device Type Vendor Code AISG Version
long:[1..429496729
5]
string:[1..32]
1:RETC,
17:MULTI_RET,
3:ATMA,
2:MULTI_TMA,
241:ACOM,
226:AETMA,
209:NSNRET,
210:LGPTMA
string:[0..128]
1:1.1,
2:2.0
<default:1>
Generated
automatically, it is
unnecessary to fill
in this column.
When LMT/OMCB
actively configures
the device type or
the reported device
type is scanned,
the user selects the
type of devices as
needed.
When LMT/OMCB
actively configures the
device type or the
reported device type is
scanned, the user fills
in the vendor code.
When LMT/OMCB
actively configures the
device type or the
reported device type is
scanned, the user fills
in the AISG version
number.
Primary Key R-I R-I R-I R-I
<> 529 , 79
ZTE
multiAntNo userLabel fatherPort selfPort refRet
Subunits No.
Description of
Self-defined Field
Superior
Channel
Local
Channel
Connected RET
Device RDN
long: [1..4,255] string: [0..128)
long: [0..12]
<default:0>
long: [0..12]
<default:0>
long:[1..4294967295]
255:Invalid.
The AISG1.1 and
AISG2.0 Single RET
decives are invalid.
For other AISG2.0
devices, each subunit
number corresponds
to an AISG device that
can be controlled
separately.
Indicates the user-
defined
description.
Cannot use the
invalid characters,
e.g. < > & ' " \ / :
? # % @ ,
Indicates the
superior
channel, used
for SDTMA
device of NSN
private
protocol. The
value for other
devices is 0.
Indicates the
local channel,
used for
SDTMA device
of NSN private
protocol. The
value for other
devices is 0.
Specifies the
connected RET
device.
The connected RET
and TMA are
mutually excluded.
R-I R-W R-I R-I R
<> 529 , 80
ZTE
refTma_tmaNo
Connected TMA
Device No.
long:[1..96]
Specifies the
connected TMA
control unit.
The connected
TMA and RET
are mutually
excluded.
R
<> 529 , 81
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID
Control Board Rack
No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rackN
o}
long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
117 35 1
117 35 2
117 35 2
117 35 2
117 35 2
117 35 2
117 35 2
<> 529 , 82
ZTE
subRackNo slotNo FanDeviceId fanNo
Control Board SubRack
No.
Control Board Slot No. RDN Fan No.
{SdrDeviceGroup_subRack
No}
long:[1..2]
{SdrDeviceGroup_slotN
o}
long:[1..23]
long:[1..4294967295] long:[1..16]
Generated
automatically, it is
unnecessary to fill in
this column.
FCE fan number starts
from 1,2,3... In BBU-
2U, the fixed SA fan
number is 16.
Primary Key Primary Key Primary Key R-I
1 13 1 16
1 7 1 1
1 7 2 2
1 7 3 3
1 7 4 4
1 7 5 5
1 7 6 6
<> 529 , 83
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rack
No}
long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 84
ZTE
subRackNo slotNo isSyncEEnable
SubRack No. Slot No.
Send SyncE Clock to
The Cascade Device or
not
{SdrDeviceGroup_subRack
No}
long:[1..2]
{SdrDeviceGroup_slotNo
}
long:[1..23]
1:Y,
0:N
<default:0>
Primary Key Primary Key R-W-I
<> 529 , 85
ZTE
pllResouce enableTrunk trunkMediaType upLinkMediaMode
PLL Clock Reference
Source
Enable Link
Aggregation or
not
Link
Aggregation
Media Type
Media Access Type at
Uplink Interface
1:supplyed by upper port
line,
2:supplyed by main control
board
<default:1>
1:Y,
0:N
<default:0>
0:Electrical port,
1:Optical port
<default:0>
0:Electrical port
preferred,
1:Optical port preferred,
2:Forced electrical port,
3:Forced optical port
<default:0>
R-W-I R-W-I R-W-I R-W-I
<> 529 , 86
ZTE
enableFEMultiPath queuePriority#1 queuePriority#2 queuePriority#3 queuePriority#4
Enable FE Multi-path
Transmission or not
Queue Priority 1 Queue Priority 2 Queue Priority 3 Queue Priority 4
1:Y,
0:N
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
When this function is enabled,
the user needs two upper-
united ports.
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 87
ZTE
queuePriority#5 queuePriority#6 queuePriority#7 queuePriority#8 queuePriority#9
Queue Priority 5 Queue Priority 6 Queue Priority 7 Queue Priority 8 Queue Priority 9
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 88
ZTE
queuePriority#10 queuePriority#11 queuePriority#12 queuePriority#13 queuePriority#14
Queue Priority
10
Queue Priority
11
Queue Priority
12
Queue Priority
13
Queue Priority
14
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:0>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 89
ZTE
queuePriority#15 queuePriority#16 queuePriority#17 queuePriority#18 queuePriority#19
Queue Priority
15
Queue Priority
16
Queue Priority
17
Queue Priority
18
Queue Priority
19
long:[0..3]
<default:0>
long:[0..3]
<default:0>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 90
ZTE
queuePriority#20 queuePriority#21 queuePriority#22 queuePriority#23 queuePriority#24
Queue Priority
20
Queue Priority
21
Queue Priority
22
Queue Priority
23
Queue Priority
24
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 91
ZTE
queuePriority#25 queuePriority#26 queuePriority#27 queuePriority#28 queuePriority#29
Queue Priority
25
Queue Priority
26
Queue Priority
27
Queue Priority
28
Queue Priority
29
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 92
ZTE
queuePriority#30 queuePriority#31 queuePriority#32 queuePriority#33 queuePriority#34
Queue Priority
30
Queue Priority
31
Queue Priority
32
Queue Priority
33
Queue Priority
34
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:1>
long:[0..3]
<default:2>
long:[0..3]
<default:2>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 93
ZTE
queuePriority#35 queuePriority#36 queuePriority#37 queuePriority#38 queuePriority#39
Queue Priority
35
Queue Priority
36
Queue Priority
37
Queue Priority
38
Queue Priority
39
long:[0..3]
<default:2>
long:[0..3]
<default:2>
long:[0..3]
<default:2>
long:[0..3]
<default:2>
long:[0..3]
<default:2>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 94
ZTE
queuePriority#40 queuePriority#41 queuePriority#42 queuePriority#43 queuePriority#44
Queue Priority
40
Queue Priority
41
Queue Priority
42
Queue Priority
43
Queue Priority
44
long:[0..3]
<default:2>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 95
ZTE
queuePriority#45 queuePriority#46 queuePriority#47 queuePriority#48 queuePriority#49
Queue Priority
45
Queue Priority
46
Queue Priority
47
Queue Priority
48
Queue Priority
49
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 96
ZTE
queuePriority#50 queuePriority#51 queuePriority#52 queuePriority#53 queuePriority#54
Queue Priority
50
Queue Priority
51
Queue Priority
52
Queue Priority
53
Queue Priority
54
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 97
ZTE
queuePriority#55 queuePriority#56 queuePriority#57 queuePriority#58 queuePriority#59
Queue Priority
55
Queue Priority
56
Queue Priority
57
Queue Priority
58
Queue Priority
59
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 98
ZTE
queuePriority#60 queuePriority#61 queuePriority#62 queuePriority#63 queuePriority#64
Queue Priority
60
Queue Priority
61
Queue Priority
62
Queue Priority
63
Queue Priority
64
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
long:[0..3]
<default:3>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 99
ZTE
ModInd OMCSUBNETID SDRMEID rackNo
Modify
Indication
Subnet ID ManagedElement ID Rack No.
A,P long:[0..4095] long:[0..65535]
{SdrDeviceGroup_rack
No}
long:[1..201]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 100
ZTE
subRackNo slotNo EthernetSwitchDeviceId
SubRack No. Slot No. RDN
{SdrDeviceGroup_subRac
kNo}
long:[1..2]
{SdrDeviceGroup_slot
No}
long:[1..23]
long:[1..4294967295]
Generated automatically,
it is unnecessary to fill in
this column.
Primary Key Primary Key Primary Key
<> 529 , 101
ZTE
port isEnable portMode
Port ID Enable Port or not
Working Type of the
Port
0:Electrical port X1 of the panel,
1:Electrical port X2 of the panel,
2:Electrical port X3 of the panel,
3:Electrical port UPLINK of the
panel,
4:Optical port X4 of the panel,
5:Optical port UPLINK of the
panel,
6:SGMII port CC1 of the back
board,
0:Close,
1:Open
<default:1>
0:Cascade port,
1:Upper-united port
Port configuration of the board,
port functions vary with port type,
including optical ports, electrical
ports, and switching ports.
Indicates whether to
open and enable the
port. This item is
invalid when the port
is configured as
[backboard SGMII
interface CC1
interface] or
[backboard SGMII
interface CC2
interface].
Indicates the port
mode. The Upper-
united port connects to
RNC/BSC/CN, while
Cascade port connects
to the subordinate SDR.
General value:0
R-I R-W-I R-W
<> 529 , 102
ZTE
operatingMode ingressRateSwitch ingressBitRate
egressRateSwitc
h
Link Mode
Enable Ingress Rate
Limitation or not
Ingress Rate
Limit
Enable Egress
Rate Limitation
or not
0:Self Negotiation,
6:100Mbps FDT,
7:1000Mbps FDT,
8:1000Mbps Self Negotiation
1:Y,
0:N
<default:1>
long:
[560..1000000]
<default:1000>
1:Y,
0:N
<default:0>
Self Negotiation mode is the mode
that is automatically adaptable to the
other end.Different mode is
configured on different type of port.
When the port type is electrical port,
self adaptive or 100M FDT can be
selected only; when the port type is
optical port, self adaptive cannot be
selected; when the port type is back
board SGMII port type, this attribute
cannot be configured. "Self-adaptive"
means network port rate can be
automatically adapted to 10M, 100M
or 1000M. "1000M self-adatpive"
means optical port can be
automatically adapted to a suitable
Unit: kbps
R-W R-W-I R-W-I R-W-I
<> 529 , 103
ZTE
egressBitRate vlanMembership#1 vlanMembership#2
Egress Rate Limit VLAN Group ID 1 VLAN Group ID 2
long: [70..250000]
<default:250000>
long: [1..10] long: [1..10]
Unit: kbps
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port CC1 port
on the backplane) and port 7(SGMII port
CC2 port on the backplane) can not be
configured in the same VLAN group.
Specifies a VLAN group ID for the current
port. Port 6 (SGMII port CC1 port on the
backplane) and port 7(SGMII port CC2
port on the backplane) can not be
configured in the same VLAN group.
R-W-I R-W-I R-W-I
<> 529 , 104
ZTE
vlanMembership#3 vlanMembership#4
VLAN Group ID 3 VLAN Group ID 4
long: [1..10] long: [1..10]
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port CC1
port on the backplane) and port
7(SGMII port CC2 port on the
backplane) can not be configured in
the same VLAN group.
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port
CC1 port on the backplane) and
port 7(SGMII port CC2 port on the
backplane) can not be
configured in the same VLAN
group.
R-W-I R-W-I
<> 529 , 105
ZTE
vlanMembership#5 vlanMembership#6 vlanMembership#7
VLAN Group ID 5 VLAN Group ID 6 VLAN Group ID 7
long: [1..10] long: [1..10] long: [1..10]
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port
CC1 port on the backplane) and
port 7(SGMII port CC2 port on the
backplane) can not be configured
in the same VLAN group.
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port
CC1 port on the backplane) and
port 7(SGMII port CC2 port on the
backplane) can not be configured
in the same VLAN group.
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port CC1
port on the backplane) and port
7(SGMII port CC2 port on the
backplane) can not be configured in
the same VLAN group.
R-W-I R-W-I R-W-I
<> 529 , 106
ZTE
vlanMembership#8 vlanMembership#9 vlanMembership#10
VLAN Group ID 8 VLAN Group ID 9 VLAN Group ID 10
long: [1..10] long: [1..10] long: [1..10]
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port
CC1 port on the backplane) and
port 7(SGMII port CC2 port on the
backplane) can not be configured
in the same VLAN group.
Specifies a VLAN group ID for the
current port. Port 6 (SGMII port
CC1 port on the backplane) and
port 7(SGMII port CC2 port on the
backplane) can not be configured
in the same VLAN group.
Specifies a VLAN group ID for
the current port. Port 6 (SGMII
port CC1 port on the
backplane) and port 7(SGMII
port CC2 port on the
backplane) can not be
configured in the same VLAN
group.
R-W-I R-W-I R-W-I
<> 529 , 107
ZTE
ingressRateLimitMode
Rate Limit Mode of Import
0:Limit and count all frames,
1:Limit and count broadcast/multicast
and flooding frame,
2:Limit and count broadcast and
multicast,
3:Limit and count broadcast
<default:3>
R-W-I
<> 529 , 108
ZTE
ModInd OMCSUBNETID SDRMEID enableEnergySaving
Modify
Indication
Subnet ID ManagedElement ID
Enable Open
Accumulator-saving
Mode or not
A,P long:[0..4095] long:[0..65535]
1: Y,
0: N
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
If the external power
supply of the base station
is faulty, the standby
power supply is used to
guarantee the base station
performance.
Return To
Index
Primary Key Primary Key R-W-I
117 35 0
<> 529 , 109
ZTE
enableIntelligenceMode startTime endTime
Enable Smart Power-
saving Mode or not
Start Time of Smart
Power-saving Mode
End Time of Smart
Power-saving Mode
1: Y,
0: N
<default:0>
string:[0..20] string:[0..20]
When smart power-saving
mode is started, the user
should configure power-
saving start time and end
time. During power-
saving, the mode will
block low guarantee local
cell, and the
corresponding baseband
board and PA will be
powered-down. It is an
It is valid when starting
smart power-saving mode.
The start time must be not
equal to the end time.
Format:HH:MM
It is valid when starting
smart power-saving mode.
The end time must be not
equal to the start time.
Format:HH:MM
R-W-I R-W R-W
0 0 0
<> 529 , 110
ZTE
enableAutoConnection autoConnectionMode#1 autoConnectionMode#2
Automatic Connection
Type
Automatic Connection Mode 1
Automatic Connection Mode
2
0:Close,
1:Enable automatic
construction of chain,
2:Enable auxiliary
1:Try ATM mode,
2:Try PPP mode,
4:Try Ethernet mode
1:Try ATM mode,
2:Try PPP mode,
4:Try Ethernet mode
Automatic link establishment
switch. The automatic link
establishment function
means that the base station
automatically attemtps
establishing the O&M
channel on various physical
media between OMCs.
It sets on which physical media
the automatic link establishment
is attempted. Selecting the
transmission mode precisely can
accelerate the automatic link
establishment. At least one
attemption mode should be
selected.
Cannot be the same with
previous column.
It sets on which physical
media the automatic link
establishment is attempted.
Selecting the transmission
mode precisely can accelerate
the automatic link
establishment. At least one
attemption mode should be
selected.
R-W-I R-W-I R-W-I
0 1 2
<> 529 , 111
ZTE
autoConnectionMode#3 linkBrokenTolerantTime selfProtectTime
Automatic Connection Mode
3
Link Broken Tolerant
Time
Base Station Reset Time
After Self-rescue from A
Fault
1:Try ATM mode,
2:Try PPP mode,
4:Try Ethernet mode
long: [3..300]
<default:10>
long:[15..65535]
<default:120>
Cannot be the same with
previous column.
It sets on which physical media
the automatic link
establishment is attempted.
Selecting the transmission
mode precisely can accelerate
the automatic link
establishment. At least one
attemption mode should be
selected.
Unit: minute.
It sets when the automatic
link establishment is
started. The base station
starts the automatic link
establishment if the
broken duration of the
following parameters
exceed this value:
transmission layer control
link (SCTP, SSCOP),
Unit: minute.
It sets the self-resetting
time of the base station self-
resetting function. The self-
resetting function of base
station means that, when
the broken duration of the
transmission layer control
link (SCTP, SSCOP), LMT
O&M channel, and OMC
O&M channel exceed this
R-W-I R-W-I R-W-I
4 10 120
<> 529 , 112
ZTE
idType enableBypass enableUdpMux
Negotiation entity ID type Enable Bypass or not Enable UDPMUX Mode or not
1: IPv4 Address Type,
2: FQDN Type
<default:1>
1:Y,
0:N
<default:0>
0:Disable UdpMux,
1:Enable Gsm and Umts UdpMux,
2:Enable Gsm UdpMux,
3:Enalbe Umts UdpMux
Negotiate entity ID load
type.
Enable bypass or not.
When daisy chain
cascading is used, the
upper level BBU
provides automatic
bridging function. If the
upper level BBU is
powered-down or
abnormal, the E1
connected to
BSC/RNC can be
When UDPMUX mode is enabled,
base station supports the function to
encapsulate multi-UDP packets into a
big packet to reduce the number of
packets and increase transmission
efficiency. If UDPMUX is disabled, the
packages cann't be merged.
This attribute value should be
consistent with the RNC's, otherwise
UDP package will be lost.
R-W-I R-W-I R-W-I
1 0 0
<> 529 , 113
ZTE
ModInd OMCSUBNETID SDRMEID ItfUniBtsId itfUniBtsNo
Modify
Indication
Subnet ID ManagedElement ID RDN
OMC Interface Link
No.
A,P long:[0..4095] long:[0..65535] long: [1..3]
long:[0..2]
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically
, it is
unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 0
<> 529 , 114
ZTE
itfUniBtsType innerIp gatewayIp omcServerIp omcNetworkMask
Type of Operation and
Maintenance Interface
Base Station
Inner IP
OMC Gateway
IP
OMC Server IP
OMC Network
Mask
0:IPINIP,
1:IPOA,
2:Independent
Networking
<default:0>
ipv4 ipv4 ipv4 ipv4
itf-UniBts packet
encapsulation type,
IPINIP, IPOA (used in
the ATM mode) or IP
(independent
networking).
It is the inner
IP address of
base station
configured in
the IPINIP
mode. It is
It is the IP
address of OMC
gateway
configured in the
IPINIP mode.
The O&M packet
IP address of
the OMC server
configured in
the independent
networking
mode.
Subnet mask of the
OMC server
configured in the
independent
networking mode.
R-I R R R R
0 118.117.35.100 118.117.0.1 0.0.0.0
<> 529 , 115
ZTE
dscp ipoaAddr itfUniBtsClass
DSCP IPOA Address
Class of Operation and
Maintenance Interface
long:[0..63]
<default:46>
ipv4
0:Master,
1:Slave
<default:0>
The transmission quality
priority of O&M packet. It is set
by the user. It is
recommendedto set it to
"46:EF service, accelerated
forwarding, minimum delay,
IP address in the IPOA
transmission mode. It is set by
the user, and is an
interconnection parameter. If
it is set to 0.0.0.0, it indicates
that the IP address is
Active/standby status of
the Itf-UniBts channel.
OMC sets the status
according to the actual
condition.
R-W-I R R-I
0 0
<> 529 , 116
ZTE
refIpLayerConfig_ipNo refSaalUni_pvcNo
Used IP Used SaalUni
long:[0..19]
long:[64490,64500..6451
6]
Configure as IP link No.
"ipNo" of IpLayerConfig
object.
Configure as Pvc No.
"pvcNo" of SaalUni
object.
R R
0
<> 529 , 117
ZTE
ModInd OMCSUBNETID SDRMEID OperatorId operatorName
Modify
Indication
Subnet ID ManagedElement ID RDN
Operator
Name
A,P long:[0..4095] long:[0..65535] long:[1..4294967295] string: [0..127]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 NA
<> 529 , 118
ZTE
userLabel cePercent
Operator
Information
CE Percent(%) Associated to
An Operator
string: [0..127]
long:[0..100]
<default:0>
Cannot use the
invalid characters,
e.g. < > & ' " \ / : ?
# % @ ,
It is the percentage of the
operator in CE. The total of all
the CE percentages is not
larger than 100%.
R-W R-I
0
<> 529 , 119
ZTE
ModInd OMCSUBNETID SDRMEID operatorName
Modify
Indication
Subnet ID ManagedElement ID Operator Name
A,P long:[0..4095] long:[0..65535]
{Operator_operatorNam
e}
string: [0..127]
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 120
ZTE
PlmnId mcc mnc
RDN MCC MNC
long:[1..3] string:[3..3] string:[2..3]
Generated
automatically, it is
unnecessary to fill in
this column.
The Mobile Country
Code of a PLMN
identity used in the
radio network. Only
can config with
numeric character.
The Mobile Network
Code of a PLMN
identity used in the
radio network. Only
can config with
numeric character.
Primary Key R-I R-I
<> 529 , 121
ModInd OMCSUBNETID SDRMEID
Modify
Indication
Subnet ID ManagedElement ID
A,P long:[0..4095] long:[0..65535]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Return To
Index
Primary Key Primary Key
117 35
ZTE
ModInd OMCSUBNETID SDRMEID PhyLayerPortId phyLayerPortNo
Modify
Indication
Subnet ID ManagedElement ID RDN Physical Layer Port No.
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
long:[0..17]
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 0
117 35 2 1
<> 529 , 123
ZTE
connectObject operatingMode egressPeakBitRate
Connection Object Operating Mode Transmitting Bandwidth
0:RNC/BSC/CN,
1:SDR,
2:Third-party
<default:0>
0:Self Negotiation,
1:Electrical port 10Mbps FDT,
2:Electrical port 100Mbps FDT,
3:Optical port 1000Mbps FDT,
4:Optical port 100Mbps FDT
long:[100..1000000]
Opposite network element
connected by the object.
In the case of base station
cascading, set this
property of upper-level
base station to be "SDR".
If its value is set as a third-
party device, it indicates
that the base station
provides the data
transmission channel for
the third-party device in
Ethernet bearer is valid.
General value: 0.
Ethernet bearer is valid. Unit:
kbps.
{operatingMode==0}[100,1000000]
step 100,
{operatingMode==1}[100,10000]
step 100,
{operatingMode==2}[100,100000]
step 100,
{operatingMode==3}[100,1000000]
step 100,
{operatingMode==4}[100,100000]
step 100
R-I R-W R-W
0 0 100000
0 0 100000
<> 529 , 124
ZTE
refE1Device_subRackNo refE1Device_slotNo refE1Device_port refT1Device_subRackNo
Used E1 Board SubRack
No.
Used E1 Board Slot No. Used E1 Port ID
Used T1 Board SubRack
No.
long:[1..2]
13:SA,
5:SE,
14:SE,
1:TRB-G904/TRB-G184
etc.
long: [0..7] long:[1..2]
E1 bearer used at the port.
It is used in ATM
transmission mode or IP
over PPP transmission
mode.
E1 bearer used at the
port. It is used in ATM
transmission mode or IP
over PPP transmission
mode.
E1 bearer used at
the port. It is used
in ATM
transmission
mode or IP over
PPP transmission
mode.
T1 bearer used at the port. It
is used in ATM transmission
mode or IP over PPP
transmission mode.
R R R R
1 13 0
1 13 1
<> 529 , 125
ZTE
refT1Device_slotNo refT1Device_port
refGeDevice_subRack
No
refGeDevice_slotN
o
Used T1 Board Slot
No.
Used T1 Port ID
Used Ethernet Board
SubRack No.
Used Ethernet
Board Slot No.
13:SA,
5:SE,
14:SE,
long: [0..7] long:[1..2] long: [1..8]
T1 bearer used at the
port. It is used in ATM
transmission mode or IP
over PPP transmission
mode.
T1 bearer used at
the port. It is used
in ATM
transmission mode
or IP over PPP
transmission mode.
Ethernet used at the
port. It is used in IP
transmission mode.
Ethernet used at
the port. It is used
in IP transmission
mode.
R R R R
<> 529 , 126
ZTE
refGeDevice_port
Used Ethernet
Board Port ID
long
Ethernet used at the
port. It is used in IP
transmission mode.
R
<> 529 , 127
ZTE
ModInd OMCSUBNETID SDRMEID
DhcpRelayI
d
dhcpRelayNo
Modify
Indication
Subnet ID ManagedElement ID RDN
DHCP Relay
No.
A,P long:[0..4095] long:[0..65535] long: [1..1]
long: [0..3]
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automaticall
y, it is
unnecessar
y to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 128
ZTE
refPhyLayerPort_phyLayerPortN
o
refEthernetLink_ethernetLink
No
vid enableDhcpRelay
Used Physical Port Used Ethernet Link VLAN ID
Enable DHCP
Relay Function or
not
long:[0..17] long:[0..0] long: [1..4094]
1:Y,
0:N
<default:0>
Physical port used. Its bearer
must be Ethernet. This port and
EthernetLink are mutually
exclusive.
Ethernet link used. This port
and PhyLayerPort are
mutually exclusive.
VLAN used. You can
select a configured
VLAN from
refEthernetLink.
R R R R-W-I
<> 529 , 129
ZTE
dhcpServerIp
DHCP Server
Address
IPV4
<default:0.0.0.
0>
R-W-I
<> 529 , 130
ZTE
ModInd OMCSUBNETID SDRMEID AtmLayerLinkId atmLayerLinkNo
Modify
Indication
Subnet ID ManagedElement ID RDN ATM Layer Link No.
A,P long:[0..4095] long:[0..65535] long: [1..12]
long:[0..11]
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it
is unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 131
ZTE
protocolType isScramb imaNo frameLen
Protocol Type of ATM Layer Scrambling or not IMA Link No. Length of Frame
0:IMA,
1:TC
<default:0>
1:Y,
0:N
long:[0..3]
0:32cell,
1:64cell,
2:128cell,
3:256cell
Object protocol type
represented by MO. It must
be consistent with that at the
opposite end.
IMA protocol
parameter. It
indicates whether to
enable the
descrambling
processing for the
cell net load. It must
be consistent with
the configuration at
the opposite end
device.
General value:0
It is valid when
protocol type of
ATM layer is
IMA.
IMA group
number, which is
unique within a
network element.
General value: 0.
It is valid when
protocol type of
ATM layer is IMA.
Frame length of
IMA group. It must
be consistent with
the configuration at
the opposite end.
General value: 2.
R-I R-W R R-W
<> 529 , 132
ZTE
clockMode refPhyLayerPortNo#1 refPhyLayerPortNo#2
Clock Mode Used ATM Port 1 Used ATM Port 2
1:ITC,
2:CTC
{refPhyLayerPort_phyLayerPortN
o#1}
long:[0..17]
{refPhyLayerPort_phyLayerPortN
o#2}
long:[0..17]
It is valid when
protocol type of
ATM layer is IMA.
Clock mode of IMA
group. It is
recommended that
it should be
consistent with the
configuration at the
opposite end.
General value: 1.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA
group are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
R-W R-W-I R-W-I
<> 529 , 133
ZTE
refPhyLayerPortNo#3 refPhyLayerPortNo#4
Used ATM Port 3 Used ATM Port 4
{refPhyLayerPort_phyLayerPortNo#
3}
long:[0..17]
{refPhyLayerPort_phyLayerPortNo#
4}
long:[0..17]
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
R-W-I R-W-I
<> 529 , 134
ZTE
refPhyLayerPortNo#5 refPhyLayerPortNo#6
Used ATM Port 5 Used ATM Port 6
{refPhyLayerPort_phyLayerPortNo#5}
long:[0..17]
{refPhyLayerPort_phyLayerPortN
o#6}
long:[0..17]
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is IMA,
all ports within the IMA group are
included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA
group are included.
R-W-I R-W-I
<> 529 , 135
ZTE
refPhyLayerPortNo#7 refPhyLayerPortNo#8 refPhyLayerPortNo#9
Used ATM Port 7 Used ATM Port 8 Used ATM Port 9
{refPhyLayerPort_phyLayerPortNo
#7}
long:[0..17]
{refPhyLayerPort_phyLayerPortNo
#8}
long:[0..17]
{refPhyLayerPort_phyLayerPortNo
#9}
long:[0..17]
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
R-W-I R-W-I R-W-I
<> 529 , 136
ZTE
refPhyLayerPortNo#10 refPhyLayerPortNo#11 refPhyLayerPortNo#12
Used ATM Port 10 Used ATM Port 11 Used ATM Port 12
{refPhyLayerPort_phyLayerPortNo#
10}
long:[0..17]
{refPhyLayerPort_phyLayerPortNo#
11}
long:[0..17]
{refPhyLayerPort_phyLayerPortN
o#12}
long:[0..17]
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA
group are included.
R-W-I R-W-I R-W-I
<> 529 , 137
ZTE
refPhyLayerPortNo#13 refPhyLayerPortNo#14
Used ATM Port 13 Used ATM Port 14
{refPhyLayerPort_phyLayerPortNo#
13}
long:[0..17]
{refPhyLayerPort_phyLayerPortNo#
14}
long:[0..17]
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
R-W-I R-W-I
<> 529 , 138
ZTE
refPhyLayerPortNo#15 refPhyLayerPortNo#16 timeSlotBitMap#1
Used ATM Port 15 Used ATM Port 16
TS-bit Mapping
Relation 0
{refPhyLayerPort_phyLayerPortNo#
15}
long:[0..17]
{refPhyLayerPort_phyLayerPortNo#16}
long:[0..17]
long: [0..1]
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is
IMA, all ports within the IMA group
are included.
Physical-layer port of IMA. If the
protocol type is TC, only one
refPhyLayerPort port can be
configured. If the protocolt type is IMA,
all ports within the IMA group are
included.
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the
value range
represents a
timeslot. 0
indicates not
using the timeslot
while 1 indicates
R-W-I R-W-I R-W
<> 529 , 139
ZTE
timeSlotBitMap#2
timeSlotBitMap#
3
timeSlotBitMap#
4
timeSlotBitMap#5 timeSlotBitMap#6
TS-bit Mapping
Relation 1
TS-bit Mapping
Relation 2
TS-bit Mapping
Relation 3
TS-bit Mapping
Relation 4
TS-bit Mapping
Relation 5
long: [0..1] long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the
value range
represents a
timeslot. 0
indicates not
using the timeslot
while 1 indicates
It is valid when
protocol type of
ATM layer is TC.
E1 or T1
timeslot used by
TC. Each bit
within the value
range
represents a
timeslot. 0
indicates not
using the
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC.
Each bit within
the value range
represents a
timeslot. 0
indicates not
using the
timeslot while 1
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents a
timeslot. 0
indicates not using
the timeslot while 1
indicates using the
timeslot. For E1,
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents a
timeslot. 0
indicates not using
the timeslot while 1
indicates using the
timeslot. For E1,
R-W R-W R-W R-W R-W
<> 529 , 140
ZTE
timeSlotBitMap#7 timeSlotBitMap#8 timeSlotBitMap#9 timeSlotBitMap#10 timeSlotBitMap#11
TS-bit Mapping
Relation 6
TS-bit Mapping
Relation 7
TS-bit Mapping
Relation 8
TS-bit Mapping
Relation 9
TS-bit Mapping
Relation 10
long: [0..1] long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents a
timeslot. 0
indicates not using
the timeslot while 1
indicates using the
timeslot. For E1,
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC.
Each bit within
the value range
represents a
timeslot. 0
indicates not
using the timeslot
while 1 indicates
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents a
timeslot. 0
indicates not using
the timeslot while 1
indicates using the
timeslot. For E1,
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents a
timeslot. 0 indicates
not using the
timeslot while 1
indicates using the
timeslot. For E1,
R-W R-W R-W R-W R-W
<> 529 , 141
ZTE
timeSlotBitMap#12 timeSlotBitMap#13
timeSlotBitMap#1
4
timeSlotBitMap#1
5
timeSlotBitMap#1
6
TS-bit Mapping
Relation 11
TS-bit Mapping
Relation 12
TS-bit Mapping
Relation 13
TS-bit Mapping
Relation 14
TS-bit Mapping
Relation 15
long: [0..1] long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when
protocol type of ATM
layer is TC.
E1 or T1 timeslot
used by TC. Each bit
within the value
range represents a
timeslot. 0 indicates
not using the timeslot
while 1 indicates
using the timeslot.
For E1, the timeslot
It is valid when
protocol type of ATM
layer is TC.
E1 or T1 timeslot
used by TC. Each bit
within the value
range represents a
timeslot. 0 indicates
not using the timeslot
while 1 indicates
using the timeslot.
For E1, the timeslot
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC.
Each bit within
the value range
represents a
timeslot. 0
indicates not
using the timeslot
while 1 indicates
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
R-W R-W R-W R-W R-W
<> 529 , 142
ZTE
timeSlotBitMap#1
7
timeSlotBitMap#1
8
timeSlotBitMap#1
9
timeSlotBitMap#2
0
timeSlotBitMap#2
1
TS-bit Mapping
Relation 16
TS-bit Mapping
Relation 17
TS-bit Mapping
Relation 18
TS-bit Mapping
Relation 19
TS-bit Mapping
Relation 20
long: [0..1] long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
R-W R-W R-W R-W R-W
<> 529 , 143
ZTE
timeSlotBitMap#2
2
timeSlotBitMap#2
3
timeSlotBitMap#2
4
timeSlotBitMap#2
5
timeSlotBitMap#2
6
TS-bit Mapping
Relation 21
TS-bit Mapping
Relation 22
TS-bit Mapping
Relation 23
TS-bit Mapping
Relation 24
TS-bit Mapping
Relation 25
long: [0..1] long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
R-W R-W R-W R-W R-W
<> 529 , 144
ZTE
timeSlotBitMap#2
7
timeSlotBitMap#2
8
timeSlotBitMap#2
9
timeSlotBitMap#3
0
timeSlotBitMap#
31
TS-bit Mapping
Relation 26
TS-bit Mapping
Relation 27
TS-bit Mapping
Relation 28
TS-bit Mapping
Relation 29
TS-bit Mapping
Relation 30
long: [0..1] long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC. Each
bit within the value
range represents
a timeslot. 0
indicates not using
the timeslot while
1 indicates using
the timeslot. For
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC.
Each bit within
the value range
represents a
timeslot. 0
indicates not
using the
timeslot while 1
R-W R-W R-W R-W R-W
<> 529 , 145
ZTE
timeSlotBitMap#
32
TS-bit Mapping
Relation 31
long: [0..1]
It is valid when
protocol type of
ATM layer is TC.
E1 or T1 timeslot
used by TC.
Each bit within
the value range
represents a
timeslot. 0
indicates not
using the
timeslot while 1
R-W
<> 529 , 146
ZTE
ModInd OMCSUBNETID SDRMEID Aal2Id pvcNo
Modify
Indication
Subnet ID ManagedElement ID RDN Pvc No.
A,P long:[0..4095] long:[0..65535] long: [1..50]
long:[1..50]
<default:1>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically,
it is
unnecessary
to fill in this
column.
PVC number of
AAL2. It must
begin from 1 and
must be
consecutive. It is
typed by the user.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 147
ZTE
pathId vpi vci
refAtmLayerLink_atmLayerLink
No
AAL2 Link ID VPI VCI Used ATM Layer Protocol
long: [1..4294967295]
<default:1>
long: [0..255]
<default:0>
long: [8..65535]
<default:8>
long:[0..11]
Path ID of the AAL2
link. It must begin from
1. It is set by the user,
and must be consistent
with the configuration
at the opposite end. If
the configuration is
incorrect, the public
transmission channel
VPI of the AAL2
link. It must be
consistent with
the configuration
at the opposite
end; otherwise,
the public
transmission
channel cannot
VCI of the AAL2
link. It must be
consistent with the
configuration at the
opposite end;
otherwise, the
public transmission
channel cannot be
estabished, and UE
Link that bears AAL2.
R-I R-I R-I R-I
<> 529 , 148
ZTE
trafficProfile_maxOutBitRate trafficProfile_aveOutBitRate trafficProfile_minOutBitRate
Maximum Transmitting
Bandwidth
Average Transmitting
Bandwidth
Minimum Transmitting
Bandwidth
{trafficProfile_maxEgressBitRa
te}
long: [0..30000]
<default:2048>
{trafficProfile_averageEgressBitR
ate}
long: [0..30000]
<default:2048>
{trafficProfile_minEgressBitRa
te}
long: [0..30000]
<default:2048>
Unit: kbps. Unit: kbps. Unit: kbps.
R-W-I R-W-I R-W-I
<> 529 , 149
ZTE
trafficProfile_maxInBitRate trafficProfile_aveInBitRate trafficProfile_minInBitRate
Maximum Receiving
Bandwidth
Average Receiving Bandwidth
Minimum Receiving
Bandwidth
{trafficProfile_maxIngressBitR
ate}
long: [0..30000]
<default:2048>
{trafficProfile_averageIngressBit
Rate}
long: [0..30000]
<default:2048>
{trafficProfile_minIngressBitRa
te}
long: [0..30000]
<default:2048>
Unit: kbps. Unit: kbps. Unit: kbps.
R-W-I R-W-I R-W-I
<> 529 , 150
ZTE
trafficProfile_serviceCatego
ry
adminState
Service Type Manual Operation Field
0:SRVC_CBR,
1:SRVC_RTVBR,
2:SRVC_NRTVBR,
3:SRVC_UBR,
4:SRVC_ABR,
5:SRVC_OTHER
<default:0>
0:No Manual Operation,
1:Block,
2:Disabled,
4:Powered-down,
65536:Block Smoothly
<default:0>
This attribute indicates the
category of ATM services.
All categories of ATM
services can be divided into
two types: real-time
services (SRVC_CBR, and
SRVC_RTVBR), and non-
real-time services
(SRVC_NRTVBR,
This field can not be
configured. Do not modify
it.
R-W-I R-W
<> 529 , 151
ZTE
ModInd OMCSUBNETID SDRMEID SaalUniId pvcNo
Modify
Indication
Subnet ID ManagedElement ID RDN Pvc No.
A,P long:[0..4095] long:[0..65535] long: [1..18]
long:[64490,64500..6451
6]
<default:64500>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it
is unnecessary
to fill in this
column.
AAL5 PVC link number.
When the AAL5 PVC link
bears IP services, the
value is 64516 or 64500.
When the AAL5 PV link
transparently transmits
data from third-party
devices, the value is
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 152
ZTE
vpi vci
refAtmLayerLink_atmLayerLinkN
o
trafficProfile_maxOutBitRate
VPI VCI Used ATM Layer Link
Maximum Transmitting
Bandwidth
long: [0..255]
<default:0>
long: [8..255]
<default:8>
long:[0..11]
{trafficProfile_maxEgressBitR
ate}
long: [0..30000]
<default:128>
VPI of the AAL5
link. It must be
consistent with
the
configuration at
the opposite
end.
VCI of the AAL5
link. It must be
consistent with
the configuration
at the opposite
end.
Link that bears AAL5. Unit: kbps.
R-I R-I R-I R-W-I
<> 529 , 153
ZTE
trafficProfile_aveOutBitRate trafficProfile_minOutBitRate trafficProfile_maxInBitRate
Average Transmitting
Bandwidth
Minimum Transmitting
Bandwidth
Maximum Receiving
Bandwidth
{trafficProfile_averageEgressBitR
ate}
long: [0..30000]
<default:128>
{trafficProfile_minEgressBitR
ate}
long: [0..30000]
<default:128>
{trafficProfile_maxIngressBitR
ate}
long: [0..30000]
<default:128>
Unit: kbps. Unit: kbps. Unit: kbps.
R-W-I R-W-I R-W-I
<> 529 , 154
ZTE
trafficProfile_aveInBitRate trafficProfile_minInBitRate
trafficProfile_serviceCategor
y
Average Receiving Bandwidth
Minimum Receiving
Bandwidth
Service Type
{trafficProfile_averageIngressBit
Rate}
long: [0..30000]
<default:128>
{trafficProfile_minIngressBitRa
te}
long: [0..30000]
<default:128>
0:SRVC_CBR,
1:SRVC_RTVBR,
2:SRVC_NRTVBR,
3:SRVC_UBR,
4:SRVC_ABR,
5:SRVC_OTHER
<default:0>
Unit: kbps. Unit: kbps.
This attribute indicates the
category of ATM services.
All categories of ATM
services can be divided into
two types: real-time services
(SRVC_CBR, and
SRVC_RTVBR), and non-
real-time services
R-W-I R-W-I R-W-I
<> 529 , 155
ZTE
ModInd OMCSUBNETID SDRMEID AlcapId atmAddr
Modify
Indication
Subnet ID ManagedElement ID RDN ATM Address
A,P long:[0..4095] long:[0..65535] long: [1..3]
string:[1..79]
default:<0;0;0;0;0;0;0;0;0;0;0
;0;0;0;0;0;0;0;0;0;>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automaticall
y, it is
unnecessar
y to fill in
this column.
Fill in valid length, e.g.
1;1;1;2 Rule: number + ;
IP address of ATM, used in
establishing the public
transmission channel in a
cell. This address is planned
by the user. It should be
referred when the opposite-
end configuration is
performed.
Return To
Index
Primary Key Primary Key Primary Key R-W-I
<> 529 , 156
ZTE
refSaalUni_pvcNo
Used SaalUni Link
long:[64490,64500..64516]
AAL5 link that bears alcap.
R-I
<> 529 , 157
ZTE
ModInd OMCSUBNETID SDRMEID BtsCascadeId cascadeType
Modify
Indication
Subnet ID ManagedElement ID RDN Bts Cascade Type
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
0:TSI,
1:ATM Routing
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Base station
cascading type. It
indicates how a base
station tranmits data
to the lower-level
base station. It has
nothing to do with
the upper-layer data
protocol. Timeslot
cross means
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 158
ZTE
btsCascadeNo ref1PhyLayerPortNo
ingressTimeSlotBitMap#
1
BtsCascade No. Inlet E1
TS-bit Mapping
Relation (Inlet) 0
long:
[0..100,65000..65059]
<default:0>
{ref1PhyLayerPort_phyLayerPortN
o}
long:[0..17]
long: [0..1]
Link ID of timeslot cross
in the TSI cascading
mode. Route number in
the ATM cascading
mode.
It is valid when cascade type is
TSI.
E1 or T1 (ingress E1/T1) for
connecting RNC/BSC/CN used by
upper-level base station in the TSI
cascading mode.
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-I R-W R-W
<> 529 , 159
ZTE
ingressTimeSlotBitMap#
2
ingressTimeSlotBitMap#
3
ingressTimeSlotBitMap#
4
ingressTimeSlotBitMap#
5
TS-bit Mapping
Relation (inlet) 1
TS-bit Mapping
Relation (inlet) 2
TS-bit Mapping
Relation (inlet) 3
TS-bit Mapping
Relation (inlet) 4
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 160
ZTE
ingressTimeSlotBitMap#
6
ingressTimeSlotBitMap#
7
ingressTimeSlotBitMap#
8
ingressTimeSlotBitMap#
9
TS-bit Mapping
Relation (inlet) 5
TS-bit Mapping
Relation (inlet) 6
TS-bit Mapping
Relation (inlet) 7
TS-bit Mapping
Relation (inlet) 8
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 161
ZTE
ingressTimeSlotBitMap#
10
ingressTimeSlotBitMap#
11
ingressTimeSlotBitMap#
12
ingressTimeSlotBitMap#
13
TS-bit Mapping
Relation (inlet) 9
TS-bit Mapping
Relation (inlet) 10
TS-bit Mapping
Relation (inlet) 11
TS-bit Mapping
Relation (inlet) 12
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 162
ZTE
ingressTimeSlotBitMap#
14
ingressTimeSlotBitMap#
15
ingressTimeSlotBitMap#
16
ingressTimeSlotBitMap#
17
TS-bit Mapping
Relation (inlet) 13
TS-bit Mapping
Relation (inlet) 14
TS-bit Mapping
Relation (inlet) 15
TS-bit Mapping
Relation (inlet) 16
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 163
ZTE
ingressTimeSlotBitMap#
18
ingressTimeSlotBitMap#
19
ingressTimeSlotBitMap#
20
ingressTimeSlotBitMap#
21
TS-bit Mapping
Relation (inlet) 17
TS-bit Mapping
Relation (inlet) 18
TS-bit Mapping
Relation (inlet) 19
TS-bit Mapping
Relation (inlet) 20
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 164
ZTE
ingressTimeSlotBitMap#
22
ingressTimeSlotBitMap#
23
ingressTimeSlotBitMap#
24
ingressTimeSlotBitMap#
25
TS-bit Mapping
Relation (inlet) 21
TS-bit Mapping
Relation (inlet) 22
TS-bit Mapping
Relation (inlet) 23
TS-bit Mapping
Relation (inlet) 24
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 165
ZTE
ingressTimeSlotBitMap#
26
ingressTimeSlotBitMap#
27
ingressTimeSlotBitMap#
28
ingressTimeSlotBitMap#
29
TS-bit Mapping
Relation (inlet) 25
TS-bit Mapping
Relation (inlet) 26
TS-bit Mapping
Relation (inlet) 27
TS-bit Mapping
Relation (inlet) 28
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 166
ZTE
ingressTimeSlotBitMap#
30
ingressTimeSlotBitMap#
31
ingressTimeSlotBitMap#
32
TS-bit Mapping
Relation (inlet) 29
TS-bit Mapping
Relation (inlet) 30
TS-bit Mapping
Relation (inlet) 31
long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the ingress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W
<> 529 , 167
ZTE
ref2PhyLayerPortNo egressTimeSlotBitMap#1 egressTimeSlotBitMap#2
Outlet E1
TS-bit Mapping
Relation(outlet) 0
TS-bit Mapping
Relation(outlet) 1
{ref2PhyLayerPort_phyLayerPortN
o}
long
long: [0..1] long: [0..1]
It is valid when cascade type is
TSI.
E1 or T1 (egress E1/T1) for
connecting SDR used by upper-
level base station in the TSI
cascading mode.
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W
<> 529 , 168
ZTE
egressTimeSlotBitMap#3 egressTimeSlotBitMap#4 egressTimeSlotBitMap#5 egressTimeSlotBitMap#6
TS-bit Mapping
Relation(outlet) 2
TS-bit Mapping
Relation(outlet) 3
TS-bit Mapping
Relation(outlet) 4
TS-bit Mapping
Relation(outlet) 5
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 169
ZTE
egressTimeSlotBitMap#7 egressTimeSlotBitMap#8 egressTimeSlotBitMap#9
egressTimeSlotBitMap#1
0
TS-bit Mapping
Relation(outlet) 6
TS-bit Mapping
Relation(outlet) 7
TS-bit Mapping
Relation(outlet) 8
TS-bit Mapping
Relation(outlet) 9
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 170
ZTE
egressTimeSlotBitMap#1
1
egressTimeSlotBitMap#1
2
egressTimeSlotBitMap#1
3
egressTimeSlotBitMap#1
4
TS-bit Mapping
Relation(outlet) 10
TS-bit Mapping
Relation(outlet) 11
TS-bit Mapping
Relation(outlet) 12
TS-bit Mapping
Relation(outlet) 13
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 171
ZTE
egressTimeSlotBitMap#1
5
egressTimeSlotBitMap#1
6
egressTimeSlotBitMap#1
7
egressTimeSlotBitMap#1
8
TS-bit Mapping
Relation(outlet) 14
TS-bit Mapping
Relation(outlet) 15
TS-bit Mapping
Relation(outlet) 16
TS-bit Mapping
Relation(outlet) 17
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 172
ZTE
egressTimeSlotBitMap#1
9
egressTimeSlotBitMap#2
0
egressTimeSlotBitMap#2
1
egressTimeSlotBitMap#2
2
TS-bit Mapping
Relation(outlet) 18
TS-bit Mapping
Relation(outlet) 19
TS-bit Mapping
Relation(outlet) 20
TS-bit Mapping
Relation(outlet) 21
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 173
ZTE
egressTimeSlotBitMap#2
3
egressTimeSlotBitMap#2
4
egressTimeSlotBitMap#2
5
egressTimeSlotBitMap#2
6
TS-bit Mapping
Relation(outlet) 22
TS-bit Mapping
Relation(outlet) 23
TS-bit Mapping
Relation(outlet) 24
TS-bit Mapping
Relation(outlet) 25
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 174
ZTE
egressTimeSlotBitMap#2
7
egressTimeSlotBitMap#2
8
egressTimeSlotBitMap#2
9
egressTimeSlotBitMap#3
0
TS-bit Mapping
Relation(outlet) 26
TS-bit Mapping
Relation(outlet) 27
TS-bit Mapping
Relation(outlet) 28
TS-bit Mapping
Relation(outlet) 29
long: [0..1] long: [0..1] long: [0..1] long: [0..1]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
R-W R-W R-W R-W
<> 529 , 175
ZTE
egressTimeSlotBitMap#3
1
egressTimeSlotBitMap#3
2
ingressVpi
TS-bit Mapping
Relation(outlet) 30
TS-bit Mapping
Relation(outlet) 31
Ingress VPI
long: [0..1] long: [0..1] long: [0..255]
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is TSI.
It describes which
timeslots in the egress
E1/T1 are reserved for
the lower-level base
stations. Each bit
corresponds to a
timeslot. 0 indicates not
reserved for the lower-
It is valid when cascade
type is ATM Routing.
Ingress VPI of the ATM
route. It must be consistent
with the RNC/BSC/CN
configuration.
General value: 0.
R-W R-W R
<> 529 , 176
ZTE
ingressVci ref1AtmLayerLinkNo egressVpi egressVci
Ingress VCI Used ATM Link Egress VPI Egress VCI
long: [8..65535]
{ref1AtmLayerLink_atmLayerLin
kNo}
long:[0..11]
long: [0..255] long: [8..65535]
It is valid when cascade
type is ATM Routing.
Ingress VCI of the ATM
route. It must be consistent
with the RNC/BSC/CN
configuration. General
value: 8.
It is valid when cascade type is
ATM Routing.
Ingress PVC bottom-layer link of
the ATM route. It can only be
either IMA or TC. It must be
consistent with the
RNC/BSC/CN configuration.
It is valid when
cascade type
is ATM
Routing.
Egress VPI of
the ATM route.
It must be
consistent with
the lower-level
SDR
It is valid when
cascade type is
ATM Routing.
Egress VCI of
the ATM route.
It must be
consistent with
the lower-level
SDR
configuration
R R R R
<> 529 , 177
ZTE
ref2AtmLayerLinkNo trafficProfile_maxOutBitRate trafficProfile_aveOutBitRate
Used Egress ATM Link
Maximum Transmitting
Bandwidth
Average Transmitting
Bandwidth
{ref2AtmLayerLink_AtmLayerLink
No}
long:[0..11]
{trafficProfile_maxEgressBit
Rate}
long: [0..30000]
{trafficProfile_averageEgressBit
Rate}
long: [0..30000]
It is valid when cascade type is
ATM Routing.
Egress PVC bottom-layer link of
the ATM route. It can only be
either IMA or TC. It must be
consistent with the lower-level
SDR configuration.
It is valid when cascade type
is ATM Routing. Unit: kbps.
General value: 128.
It is valid when cascade type is
ATM Routing. Unit: kbps.
General value: 128.
R R-W R-W
<> 529 , 178
ZTE
trafficProfile_minOutBitRate trafficProfile_maxInBitRate trafficProfile_aveInBitRate
Minimum Transmitting
Bandwidth
Maximum Receiving
Bandwidth
Average Receiving Bandwidth
{trafficProfile_minEgressBitRa
te}
long: [0..30000]
{trafficProfile_maxIngressBitRat
e}
long: [0..30000]
{trafficProfile_averageIngressBitRate
}
long: [0..30000]
It is valid when cascade type
is ATM Routing. Unit: kbps.
General value: 128.
It is valid when cascade type is
ATM Routing. Unit: kbps.
General value: 128.
It is valid when cascade type is ATM
Routing. Unit: kbps. General value:
128.
R-W R-W R-W
<> 529 , 179
ZTE
trafficProfile_minInBitRate
trafficProfile_serviceCatego
ry
destinationNodeBId
Minimum Receiving
Bandwidth
Service Type Destination NodeB ID
{trafficProfile_minIngressBitRa
te}
long: [0..30000]
0:SRVC_CBR,
1:SRVC_RTVBR,
2:SRVC_NRTVBR,
3:SRVC_UBR,
4:SRVC_ABR,
5:SRVC_OTHER
long: [0..65535]
It is valid when cascade type is
ATM Routing. Unit: kbps.
General value: 128.
It is valid when cascade
type is ATM Routing.
This attribute indicates the
category of ATM services.
All categories of ATM
services can be divided into
two types: real-time
services (SRVC_CBR, and
SRVC_RTVBR), and non-
real-time services
It is valid when cascade
type is ATM Routing.
General value: 0.
R-W R-W R
<> 529 , 180
ZTE
ModInd OMCSUBNETID SDRMEID HdlcId hdlcNo
Modify
Indication
Subnet ID ManagedElement ID RDN HDLC Link No.
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
long:[0..15]
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 0
117 35 2 1
<> 529 , 181
ZTE
refPhyLayerPort_phyLayerPortN
o
timeSlotBitMap#1 timeSlotBitMap#2 timeSlotBitMap#3
Used IP Port
TS-bit Mapping
Relation 0
TS-bit Mapping
Relationt 1
TS-bit Mapping
Relationt 2
long:[0..17]
long: [0..1]
<default:0>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
R-I R-W-I R-W-I R-W-I
0 0 1 1
1 0 1 1
<> 529 , 182
ZTE
timeSlotBitMap#4 timeSlotBitMap#5 timeSlotBitMap#6 timeSlotBitMap#7 timeSlotBitMap#8
TS-bit Mapping
Relationt 3
TS-bit Mapping
Relationt 4
TS-bit Mapping
Relationt 5
TS-bit Mapping
Relationt 6
TS-bit Mapping
Relationt 7
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
R-W-I R-W-I R-W-I R-W-I R-W-I
1 1 1 1 1
1 1 1 1 1
<> 529 , 183
ZTE
timeSlotBitMap#9
timeSlotBitMap#1
0
timeSlotBitMap#1
1
timeSlotBitMap#1
2
timeSlotBitMap#1
3
TS-bit Mapping
Relationt 8
TS-bit Mapping
Relationt 9
TS-bit Mapping
Relationt 10
TS-bit Mapping
Relationt 11
TS-bit Mapping
Relationt 12
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
R-W-I R-W-I R-W-I R-W-I R-W-I
1 1 1 1 1
1 1 1 1 1
<> 529 , 184
ZTE
timeSlotBitMap#1
4
timeSlotBitMap#1
5
timeSlotBitMap#1
6
timeSlotBitMap#1
7
timeSlotBitMap#1
8
TS-bit Mapping
Relationt 13
TS-bit Mapping
Relationt 14
TS-bit Mapping
Relationt 15
TS-bit Mapping
Relationt 16
TS-bit Mapping
Relationt 17
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
R-W-I R-W-I R-W-I R-W-I R-W-I
1 1 1 1 1
1 1 1 1 1
<> 529 , 185
ZTE
timeSlotBitMap#1
9
timeSlotBitMap#2
0
timeSlotBitMap#2
1
timeSlotBitMap#2
2
timeSlotBitMap#2
3
TS-bit Mapping
Relationt 18
TS-bit Mapping
Relationt 19
TS-bit Mapping
Relationt 20
TS-bit Mapping
Relationt 21
TS-bit Mapping
Relationt 22
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
R-W-I R-W-I R-W-I R-W-I R-W-I
1 1 1 1 1
1 1 1 1 1
<> 529 , 186
ZTE
timeSlotBitMap#2
4
timeSlotBitMap#2
5
timeSlotBitMap#2
6
timeSlotBitMap#2
7
timeSlotBitMap#2
8
TS-bit Mapping
Relationt 23
TS-bit Mapping
Relationt 24
TS-bit Mapping
Relationt 25
TS-bit Mapping
Relationt 26
TS-bit Mapping
Relationt 27
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
R-W-I R-W-I R-W-I R-W-I R-W-I
1 1 1 1 1
1 1 1 1 1
<> 529 , 187
ZTE
timeSlotBitMap#2
9
timeSlotBitMap#3
0
timeSlotBitMap#3
1
timeSlotBitMap#3
2
TS-bit Mapping
Relationt 28
TS-bit Mapping
Relationt 29
TS-bit Mapping
Relationt 30
TS-bit Mapping
Relationt 31
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
long: [0..1]
<default:1>
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
It represents the
E1/T1 timeslot
used by the
HDLC link. Each
bit of it represents
a timeslot. 0
R-W-I R-W-I R-W-I R-W-I
1 1 1 1
1 1 1 1
<> 529 , 188
ZTE
ModInd OMCSUBNETID SDRMEID PppLinkId pppLinkNo
Modify
Indication
Subnet ID ManagedElement ID RDN PPP Link No.
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
long:[0..7]
<default:0>
A:Add, P:Pass Same in an OMMB.
Unique in
subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 0
<> 529 , 189
ZTE
refHdlc_HdlcNo#
1
refHdlc_HdlcNo#
2
refHdlc_HdlcNo#
3
refHdlc_HdlcNo#
4
refHdlc_HdlcNo#
5
Used HDLC
Channel 1
Used HDLC
Channel 2
Used HDLC
Channel 3
Used HDLC
Channel 4
Used HDLC
Channel 5
long:[0..15] long:[0..15] long:[0..15] long:[0..15] long:[0..15]
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
R-W-I R-W-I R-W-I R-W-I R-W-I
0
<> 529 , 190
ZTE
refHdlc_HdlcNo#
6
refHdlc_HdlcNo#
7
refHdlc_HdlcNo#
8
refHdlc_HdlcNo#
9
refHdlc_HdlcNo#
10
Used HDLC
Channel 6
Used HDLC
Channel 7
Used HDLC
Channel 8
Used HDLC
Channel 9
Used HDLC
Channel 10
long:[0..15] long:[0..15] long:[0..15] long:[0..15] long:[0..15]
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 191
ZTE
refHdlc_HdlcNo#
11
refHdlc_HdlcNo#
12
refHdlc_HdlcNo#
13
refHdlc_HdlcNo#
14
refHdlc_HdlcNo#
15
Used HDLC
Channel 11
Used HDLC
Channel 12
Used HDLC
Channel 13
Used HDLC
Channel 14
Used HDLC
Channel 15
long:[0..15] long:[0..15] long:[0..15] long:[0..15] long:[0..15]
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 192
ZTE
refHdlc_HdlcNo#
16
localIp
protocolTyp
e
mpCode mpClass ipCompress
Used HDLC
Channel 16
Base Station
IP
PPP
Encapsulat
ion Type
Long-short
Sequence of MP
Head
MP Priority
Support IP
Compress or
not
long:[0..15]
IPV4
<default:0.0.0.0
>
0: PPP,
1: ML-PPP
<default:1>
2:Long sequence,
6:Short sequence,
255:Invalid
long: [1..4,255]
1: Y,
0: N
<default:0>
HDLC link that
bears PPP.
When the
protocol
encapsulation
type is PPP, only
IP address of
the base
station. It is
used for
signaling and
service data
PPP
encapsulati
on type. It
must be
consistent
with that at
Long/short
sequence format of
the ML-PPP packet
head. It it is
different from that
at the opposite end,
It indicates the
number of
priorities
supported when
ML-MC PPP is
supported. When
It indicates
whether the ML-
PPP link
supports the IP
compression
mode. If it is
R-W-I R-W-I R-I R-W R-W R-W-I
118.117.35.100 1 2 4 1
<> 529 , 193
ZTE
isUsedToFECascad
e
maxFragmentSize
Is Used to FE
Cascade or not
Maximun MP
Slicing Length
1: Y,
0: N
<default:0>
long:[64..512]
<default:128>
E1/T1+EthernetIt
indicates whether
the PPP link is used
for cascading, and
the cascadig mode
is E1/T1+Ethernet.
Maximun slicing
size when MLPPP
is segmented.
R-W-I R-W-I
0 128
<> 529 , 194
ZTE
ModInd OMCSUBNETID SDRMEID EthernetLinkId
Modify
Indication
Subnet ID ManagedElement ID RDN
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
A:Add, P:Pass
Same in an
OMMB.
Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 195
ZTE
ethernetLinkNo refPhyLayerPort_phyLayerPortNo mtu
Ethernet Link No. Used Physical Layer Port MTU
long:[0..0]
<default:0>
long:[0..17]
long: [256..1800]
<default:1500>
One Ethernet physical port
corresponds to one link.
Unit: byte
It represents the
maximum number of
transmitted bytes of the
packet of each Ethernet
link layer. The larger it is,
the higher the bandwidth
usage is. However, it
R-I R-I R-W-I
<> 529 , 196
ZTE
vlanMembership
#1
vlanMembership
#2
vlanMembership
#3
vlanMembership
#4
vlanMembership
#5
vlanMembership
#6
VLAN No.1 VLAN No.2 VLAN No.3 VLAN No.4 VLAN No.5 VLAN No.6
long:[1..4094] long: [1..4094] long: [1..4094] long: [1..4094] long: [1..4094] long: [1..4094]
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
R R R R R R
<> 529 , 197
ZTE
vlanMembership
#7
vlanMembership
#8
VLAN No.7 VLAN No.8
long: [1..4094] long: [1..4094]
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
VLAN number
contained in the
Ethernet frame.
This setting is
optional, and
you can set at
most eight
numbers.
R R
<> 529 , 198
ZTE
ModInd OMCSUBNETID SDRMEID EthernetOamId
Modify
Indication
Subnet ID ManagedElement ID RDN
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 199
ZTE
refPhyLayerPort_phyLayerPortN
o
ethernetOamRole ethernetOamTimeOut loopbackTimeOut
Used Physical Layer Port EthernetOam Role
OAM Session
Timeout Period
(second)
Remote Loopback
Timeout Period
(second)
long:[0..17]
0:PASSIVE,
1:ACTIVE
<default:0>
long: [5..10]
<default:5>
long: [1..10]
<default:5>
Configuration information of the
IP port that bears VLAN. The
transmission medium must be
Ethernet.
EthernetOam mode.
Only the NE in the
active mode can
initiate the OAM
connection.
It is used to set the
timeout period of the
OAM session. When
the period expires, the
link is considered
broken.
R-I R-I R-W-I R-W-I
<> 529 , 200
ZTE
pduTransPeriod eventInfo_eventType#1
Interval of Packets
Sent(100ms)
Event Type 1
long: [1..10]
<default:10>
0:Errored frame second link event,
1:Errored frame period link event,
2:Errored frame link event,
3:Errored symbol link event
It is used to set the
EthOam packet
transmission period
(unit: 100 ms). The
protocol specifies that
the number of packets
transmitted per second
is 1~10.
R-W-I R-W
<> 529 , 201
ZTE
eventInfo_windowSize#1 eventInfo_threshold#1
Window Size 1 Threshold 1
long:[1..65535] long:[0..4294967295]
Set the window size of corresponding event type. Remember
different type of event adopts different unit: link event statistic
information -
errored frame seconds link event(unit: second);
errored frame period link event(unit: ten thousand pps);
errored frame link event (unit: second);
errored symbol link event (unit: million).
{eventType==0}[10..900],
{eventType==1}[1..600],
{eventType==2}[1..60],
{eventType==3}[1..65535]
General value:
{eventType==0}[60],
{eventType==1}[600],
{eventType==2}[1],
{eventType==3}[1]
Unit: times
{eventType==0}[1..900],
{eventType==1}[1..65535],
{eventType==2}[1..65535],
{eventType==3}[1..4294967295]
R-W R-W
<> 529 , 202
ZTE
eventInfo_eventType#2 eventInfo_windowSize#2
Event Type 2 Window Size 2
0:Errored frame second link
event,
1:Errored frame period link
event,
2:Errored frame link event,
long:[0..65535]
Set the window size of corresponding event type.
Remember different type of event adopts different
unit: link event statistic information -
errored frame seconds link event(unit: second);
errored frame period link event(unit: ten thousand
pps);
errored frame link event (unit: second);
errored symbol link event (unit: million).
{eventType==0}[10..900],
{eventType==1}[1..600],
{eventType==2}[1..60],
{eventType==3}[1..65535]
General value:
{eventType==0}[60],
{eventType==1}[600],
{eventType==2}[1],
{eventType==3}[1]
R-W R-W
<> 529 , 203
ZTE
eventInfo_threshold#2 eventInfo_eventType#3
Threshold 2 Event Type 3
long:[0..4294967295]
0:Errored frame second link
event,
1:Errored frame period link event,
2:Errored frame link event,
3:Errored symbol link event
Unit: times
{eventType==0}[1..900],
{eventType==1}[1..65535],
{eventType==2}[1..65535],
{eventType==3}[1..4294967295
]
R-W R-W
<> 529 , 204
ZTE
eventInfo_windowSize#3 eventInfo_threshold#3
Window Size 3 Threshold 3
long:[0..65535] long:[0..4294967295]
Set the window size of corresponding event type.
Remember different type of event adopts different
unit: link event statistic information -
errored frame seconds link event(unit: second);
errored frame period link event(unit: ten thousand
pps);
errored frame link event (unit: second);
errored symbol link event (unit: million).
{eventType==0}[10..900],
{eventType==1}[1..600],
{eventType==2}[1..60],
{eventType==3}[1..65535]
General value:
{eventType==0}[60],
{eventType==1}[600],
{eventType==2}[1],
{eventType==3}[1]
Unit: times
{eventType==0}[1..900],
{eventType==1}[1..65535],
{eventType==2}[1..65535],
{eventType==3}[1..42949672
95]
R-W R-W
<> 529 , 205
ZTE
eventInfo_eventType#4 eventInfo_windowSize#4
Event Type 4 Window Size 4
0:Errored frame second link event,
1:Errored frame period link event,
2:Errored frame link event,
3:Errored symbol link event
long:[0..65535]
Set the window size of corresponding
event type. Remember different type of
event adopts different unit: link event
statistic information -
errored frame seconds link event(unit:
second);
errored frame period link event(unit: ten
thousand pps);
errored frame link event (unit: second);
errored symbol link event (unit: million).
{eventType==0}[10..900],
{eventType==1}[1..600],
{eventType==2}[1..60],
{eventType==3}[1..65535]
General value:
{eventType==0}[60],
{eventType==1}[600],
{eventType==2}[1],
{eventType==3}[1]
R-W R-W
<> 529 , 206
ZTE
eventInfo_threshold#4
Threshold 4
long:[0..4294967295]
Unit: times
{eventType==0}[1..900],
{eventType==1}[1..65535],
{eventType==2}[1..65535],
{eventType==3}[1..4294967295
]
R-W
<> 529 , 207
ZTE
ModInd OMCSUBNETID SDRMEID
BandwidthCtrlRuleI
d
ruleNo
Modify
Indication
Subnet ID ManagedElement ID RDN
Bandwidth
Control Rule ID
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
long:[1..6]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 208
ZTE
refEthernetLink_ethernetLink
No
vid#1 vid#2 vid#3
Used Ethernet Link VLAN ID 1 VLAN ID 2 VLAN ID 3
long:[0..0] long: [2..4094,65535]
long:
[2..4094,65535]
long:
[2..4094,65535]
It indicates on which Ethernet
link the bandwidth allocation
rule is applied. It and
refPppLink are mutually
exclusive.
It indicates on which
VLAN the bandwidth
allocation rule is
applied. You can set it
only when
refEthernetLink is
enabled.
It indicates on
which VLAN the
bandwidth
allocation rule is
applied. You can
set it only when
refEthernetLink is
enabled.
It indicates on which
VLAN the bandwidth
allocation rule is
applied. You can set
it only when
refEthernetLink is
enabled.
R R R R
<> 529 , 209
ZTE
vid#4 vid#5 vid#6 vid#7 vid#8
VLAN ID 4 VLAN ID 5 VLAN ID 6 VLAN ID 7 VLAN ID 8
long:
[2..4094,65535]
long:
[2..4094,65535]
long: [2..4094,65535]
long:
[2..4094,65535]
long: [2..4094,65535]
It indicates on
which VLAN the
bandwidth
allocation rule is
applied. You can
set it only when
refEthernetLink is
enabled.
It indicates on
which VLAN the
bandwidth
allocation rule is
applied. You can
set it only when
refEthernetLink is
enabled.
It indicates on which
VLAN the bandwidth
allocation rule is
applied. You can set
it only when
refEthernetLink is
enabled.
It indicates on which
VLAN the
bandwidth allocation
rule is applied. You
can set it only when
refEthernetLink is
enabled.
It indicates on which
VLAN the bandwidth
allocation rule is
applied. You can set
it only when
refEthernetLink is
enabled.
R R R R R
<> 529 , 210
ZTE
refOperator_operatorName
#1
officeDirection
#1
refOperator_operatorName#
2
officeDirection#2
Operator 1
Office
Direction 1
Operator 2 Office Direction 2
string:[0..127]
0:RNC,
1:BSC,
2:OMC,
3:EPC
string:[0..127]
0:RNC,
1:BSC,
2:OMC,
3:EPC
It indicates for which
operator the bandwidth rule
is allocated. If it is not set, it
indicates that bandwidth
control is not implemented
between operators.
It indicates for
which office the
bandwidth rule
is allocated. If
it is not set, it
indicates that
bandwidth
control is not
implemented
between
offices.
It indicates for which
operator the bandwidth rule
is allocated. If it is not set, it
indicates that bandwidth
control is not implemented
between operators.
It indicates for
which office the
bandwidth rule is
allocated. If it is not
set, it indicates that
bandwidth control
is not implemented
between offices.
R R R R
<> 529 , 211
ZTE
refOperator_operatorName
#3
officeDirection#3 officeDirection#4 serviceType#1
Operator 3 Office Direction 3
Office Direction
4
Service Type 1
string:[0..127]
0:RNC,
1:BSC,
2:OMC,
3:EPC
0:RNC,
1:BSC,
2:OMC,
3:EPC
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99
Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA
Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA
Background,
13:SCTP
It indicates for which
operator the bandwidth rule
is allocated. If it is not set,
it indicates that bandwidth
control is not implemented
between operators.
It indicates for
which office the
bandwidth rule is
allocated. If it is not
set, it indicates that
bandwidth control
is not implemented
between offices.
It indicates for
which office the
bandwidth rule is
allocated. If it is
not set, it
indicates that
bandwidth control
is not
implemented
between offices.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not
set, it indicates that
bandwidth control is
not implemented
between service
types.
R R R R
<> 529 , 212
ZTE
serviceType#2 serviceType#3 serviceType#4 serviceType#5
Service Type 2 Service Type 3 Service Type 4 Service Type 5
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
R R R R
<> 529 , 213
ZTE
serviceType#6 serviceType#7 serviceType#8 serviceType#9
Service Type 6 Service Type 7 Service Type 8 Service Type 9
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
R R R R
<> 529 , 214
ZTE
serviceType#10 serviceType#11 serviceType#12 serviceType#13
Service Type 10 Service Type 11 Service Type 12 Service Type 13
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
1:2G CS,
2:2G PS,
3:Iub Common
Transport Channel,
4:RRC Connection,
5:R99 Conversational,
6:R99 Streaming,
7:R99 Interactive,
8:R99 Background,
9:HSPA Conversational,
10:HSPA Streaming,
11:HSPA Interactive,
12:HSPA Background,
13:SCTP
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
It indicates for which
service type the
bandwidth rule is
allocated. If it is not set,
it indicates that
bandwidth control is not
implemented between
service types.
R R R R
<> 529 , 215
ZTE
egressGBR egressMBR
refQosMap_QosMap
No
Egress GBR Egress MBR
Used Qos Mapping
Parameter
long: [0..1000000]
<default:0>
long:[0..1000000]
<default:0>
long:[0..4294967295]
Unit: kbps.
step:100
Unit: kbps.
step:100
R-I R-I R
<> 529 , 216
ZTE
ModInd OMCSUBNETID SDRMEID
IpLayerConfigI
d
ipNo
Modify
Indication
Subnet ID ManagedElement ID RDN
IP Parameter
Link No.
A,P long:[0..4095] long:[0..65535] long: [1..20]
long:[0..19]
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it
is unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 0
<> 529 , 217
ZTE
ipAddr networkMask gatewayIp ipField
IP Address Network Mask Gateway IP Domain
ipv4
ipv4
<default:255.255.255
.0>
ipv4
<default:0.0.0.0>
0,1,2,3,255
IP address of the base
station. When the PPP link
is used, you cannot
configure the IP address
information. It cannot be
It represents
information of the
domain to which IP is
belonged. 255
indicates that it does
R R-I R-I R-W
118.117.35.100 255.255.255.0 0.0.0.0 255
<> 529 , 218
ZTE
refPppLink_pppLink
No
refEthernetLink_EthernetLinkNo vid
refQosMap_QosMapN
o
Used PPP Link Used Ethernet Link VLAN ID
Used Qos Mapping
Parameter
long:[0..7] long:[0..0] long:[1..4094] long:[0..4294967295]
Same as a
VLAN in
refEthernetLink
.
R R R R
0 0
<> 529 , 219
ZTE
staticRoutes_ipAddress#1 staticRoutes_networkMask#1
staticRoutes_nextHopIpAddr#
1
Destination IP Address 1 Network Mask 1 Next Hop IP Address 1
ipv4 ipv4 ipv4
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
R-W R-W R-W
<> 529 , 220
ZTE
staticRoutes_routePriority#1 staticRoutes_ipAddress#2 staticRoutes_networkMask#2
Route Priority 1 Destination IP Address 2 Network Mask 2
long: [0..7] ipv4 ipv4
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
R-W R-W R-W
<> 529 , 221
ZTE
staticRoutes_nextHopIpAddr#
2
staticRoutes_routePriority#2 staticRoutes_ipAddress#3
Next Hop IP Address 2 Route Priority 2 Destination IP Address 3
ipv4 long: [0..7] ipv4
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
R-W R-W R-W
<> 529 , 222
ZTE
staticRoutes_networkMask#3
staticRoutes_nextHopIpAddr#
3
staticRoutes_routePriority#3
Network Mask 3 Next Hop IP Address 3 Route Priority 3
ipv4 ipv4 long: [0..7]
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
R-W R-W R-W
<> 529 , 223
ZTE
staticRoutes_ipAddress#4 staticRoutes_networkMask#4
staticRoutes_nextHopIpAddr#
4
Destination IP Address 4 Network Mask 4 Next Hop IP Address 4
ipv4 ipv4 ipv4
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
R-W R-W R-W
<> 529 , 224
ZTE
staticRoutes_routePriority#4 staticRoutes_ipAddress#5 staticRoutes_networkMask#5
Route Priority 4 Destination IP Address 5 Network Mask 5
long: [0..7] ipv4 ipv4
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
R-W R-W R-W
<> 529 , 225
ZTE
staticRoutes_nextHopIpAddr#
5
staticRoutes_routePriority#5 staticRoutes_ipAddress#6
Next Hop IP Address 5 Route Priority 5 Destination IP Address 6
ipv4 long: [0..7] ipv4
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
R-W R-W R-W
<> 529 , 226
ZTE
staticRoutes_networkMask#6
staticRoutes_nextHopIpAddr#
6
staticRoutes_routePriority#6
Network Mask 6 Next Hop IP Address 6 Route Priority 6
ipv4 ipv4 long: [0..7]
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
R-W R-W R-W
<> 529 , 227
ZTE
staticRoutes_ipAddress#7 staticRoutes_networkMask#7
staticRoutes_nextHopIpAddr#
7
Destination IP Address 7 Network Mask 7 Next Hop IP Address 7
ipv4 ipv4 ipv4
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
R-W R-W R-W
<> 529 , 228
ZTE
staticRoutes_routePriority#7 staticRoutes_ipAddress#8 staticRoutes_networkMask#8
Route Priority 7 Destination IP Address 8 Network Mask 8
long: [0..7] ipv4 ipv4
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
R-W R-W R-W
<> 529 , 229
ZTE
staticRoutes_nextHopIpAddr#
8
staticRoutes_routePriority#8 staticRoutes_ipAddress#9
Next Hop IP Address 8 Route Priority 8 Destination IP Address 9
ipv4 long: [0..7] ipv4
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
R-W R-W R-W
<> 529 , 230
ZTE
staticRoutes_networkMask#9
staticRoutes_nextHopIpAddr#
9
staticRoutes_routePriority#9
Network Mask 9 Next Hop IP Address 9 Route Priority 9
ipv4 ipv4 long: [0..7]
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
R-W R-W R-W
<> 529 , 231
ZTE
staticRoutes_ipAddress#10
staticRoutes_networkMask#1
0
staticRoutes_nextHopIpAddr#
10
Destination IP Address 10 Network Mask 10 Next Hop IP Address 10
ipv4 ipv4 ipv4
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
R-W R-W R-W
<> 529 , 232
ZTE
staticRoutes_routePriority#10 staticRoutes_ipAddress#11
staticRoutes_networkMask#1
1
Route Priority 10 Destination IP Address 11 Network Mask 11
long: [0..7] ipv4 ipv4
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
R-W R-W R-W
<> 529 , 233
ZTE
staticRoutes_nextHopIpAddr#
11
staticRoutes_routePriority#11 staticRoutes_ipAddress#12
Next Hop IP Address 11 Route Priority 11 Destination IP Address 12
ipv4 long: [0..7] ipv4
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
R-W R-W R-W
<> 529 , 234
ZTE
staticRoutes_networkMask#1
2
staticRoutes_nextHopIpAddr#
12
staticRoutes_routePriority#12
Network Mask 12 Next Hop IP Address 12 Route Priority 12
ipv4 ipv4 long: [0..7]
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
R-W R-W R-W
<> 529 , 235
ZTE
staticRoutes_ipAddress#13
staticRoutes_networkMask#1
3
staticRoutes_nextHopIpAddr#
13
Destination IP Address 13 Network Mask 13 Next Hop IP Address 13
ipv4 ipv4 ipv4
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
R-W R-W R-W
<> 529 , 236
ZTE
staticRoutes_routePriority#13 staticRoutes_ipAddress#14
staticRoutes_networkMask#1
4
Route Priority 13 Destination IP Address 14 Network Mask 14
long: [0..7] ipv4 ipv4
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
R-W R-W R-W
<> 529 , 237
ZTE
staticRoutes_nextHopIpAddr#
14
staticRoutes_routePriority#14 staticRoutes_ipAddress#15
Next Hop IP Address 14 Route Priority 15 Destination IP Address 15
ipv4 long: [0..7] ipv4
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
R-W R-W R-W
<> 529 , 238
ZTE
staticRoutes_networkMask#1
5
staticRoutes_nextHopIpAddr#
15
staticRoutes_routePriority#15
Network Mask 15 Next Hop IP Address 15 Route Priority 15
ipv4 ipv4 long: [0..7]
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
R-W R-W R-W
<> 529 , 239
ZTE
staticRoutes_ipAddress#16
staticRoutes_networkMask#1
6
staticRoutes_nextHopIpAddr#
16
Destination IP Address 16 Network Mask 16 Next Hop IP Address 16
ipv4 ipv4 ipv4
This attribute indicates the
destination address of the
static route, which may be a
subnetwork, or a specific IP
address.
This attribute indicates the
mask of the static route's
destination network.
This attribute indicates the IP
address of the next hop.
R-W R-W R-W
<> 529 , 240
ZTE
staticRoutes_routePriority#16
Route Priority 16
long: [0..7]
This attribute indicates the
priority of the IP route. 0
indicates the highest priority.
R-W
<> 529 , 241
ZTE
ModInd OMCSUBNETID SDRMEID IKEPolicyId policyNo
Modify
Indication
Subnet ID ManagedElement ID RDN
IKE Policy
No.
A,P long:[0..4095] long:[0..65535] long:[1..128]
long:[1..128]
<default:1>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it
is unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 242
ZTE
ikePriority ikeVersion authenticationMethod encryptionAlgorithm hashAlgorithm
IKE Policy
Priority
IKE Version
Authentication Method in
IKE Negotiation
Encryption
Algorithm in IKE
Negotiation
Hash
Algorithm
long:[0..127]
<default:0>
1:IKEV1,
2:IKEV2
<default:1>
1:Pre-shared key
authentication,
3:X.509 certificate
authentication
<default:1>
1:DES,
4:3DES,
6:AES-128
<default:1>
1:MD5,
2:SHA
<default:2>
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 243
ZTE
randomFunctionAlgorith
m
dhGroup ikeLife
Pseudo-random
Function Algorithm
Diffie-Hellman
Group
IKE SA Lifetime
1:MD5,
2:SHA1
<default:1>
1:MODP768,
2:MODP1024
<default:1>
long:[1..4294967295
]
<default:100>
Unit:s
R-W-I R-W-I R-W-I
<> 529 , 244
ZTE
ModInd OMCSUBNETID SDRMEID IPSecTransformSetId
Modify
Indication
Subnet ID ManagedElement ID RDN
A,P long:[0..4095] long:[0..65535] long:[1..40]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 245
ZTE
transformSetNo ipsecMode espAuthAlgorithm
espEncryptionAlgorith
m
IPSecTransform-Set
Policy No.
IPSec Mode
ESP Authentication
Algorithm
ESP Encryption
Algorithm
long:[1..40]
<default:1>
0:Transport,
1:Tunnel
<default:1>
545:MD5,
546:SHA1,
0:Invalid
<default:0>
529:ESP AES-128,
531:3DES,
0:Invalid
<default:0>
R-I R-W-I R-W-I R-W-I
<> 529 , 246
ZTE
ModInd OMCSUBNETID SDRMEID AccessControlListId aclNo
Modify
Indication
Subnet ID ManagedElement ID RDN
Access Control Rule
Number
A,P long:[0..4095] long:[0..65535] long:[1..48] long:[1..48]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
{aclType==0}[1..48],
{aclType==1}[11..42]
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 247
ZTE
aclType aclConfig_aclNo#1
aclConfig_sourceIp#
1
aclConfig_sourceSubnetMask#1
Access Rule Type
Access Control
List Object ID 1
Source Address 1 Source address Subnet Mask1
0:IPSec,
1:Package filter
<default:0>
long:[1..48] ipv4 ipv4
When access rule
type is IPSec, it
should be
configured,
otherwise it
needn't.
When access rule
type is IPSec, it
should be configured,
otherwise it needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-I R-W R-W R-W
<> 529 , 248
ZTE
aclConfig_destinationIp#1 aclConfig_destSubnetMask#1 aclConfig_ruleMaxProtocol#1
Destination Address 1
Destination Address Subnet
Mask 1
Maximum Rule of Protocol
Code 1
ipv4
{aclConfig_destinationSubnetMas
k#1}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 249
ZTE
aclConfig_ruleMinProtocol#1 aclConfig_maxSourcePort#1 aclConfig_minSourcePort#1
Minimum Rule of Protocol Code
1
Maximum Source Port 1 Minimum Source Port 1
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 250
ZTE
aclConfig_maxDestPort#1 aclConfig_minDestPort#1 aclConfig_ruleAction#1
Maximum Destination Port 1 Minimum Destination Port 1 Rule Action 1
{aclConfig_maxDestinationPort#1}
long:[0..65535]
{aclConfig_minDestinationPort#1}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 251
ZTE
aclConfig_aclNo#2 aclConfig_sourceIp#2 aclConfig_sourceSubnetMask#2
Access Control List Object ID 2 Source Address 2 Source address Subnet Mask2
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 252
ZTE
aclConfig_destinationIp#2 aclConfig_destSubnetMask#2 aclConfig_ruleMaxProtocol#2
Destination Address 2
Destination Address Subnet
Mask 2
Maximum Rule of Protocol
Code 2
ipv4
{aclConfig_destinationSubnetMas
k#2}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 253
ZTE
aclConfig_ruleMinProtocol#2 aclConfig_maxSourcePort#2 aclConfig_minSourcePort#2
Minimum Rule of Protocol Code
2
Maximum Source Port 2 Minimum Source Port 2
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 254
ZTE
aclConfig_maxDestPort#2 aclConfig_minDestPort#2 aclConfig_ruleAction#2
Maximum Destination Port 2 Minimum Destination Port 2 Rule Action 2
{aclConfig_maxDestinationPort#2}
long:[0..65535]
{aclConfig_minDestinationPort#2}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 255
ZTE
aclConfig_aclNo#3 aclConfig_sourceIp#3 aclConfig_sourceSubnetMask#3
Access Control List Object ID 3 Source Address 3 Source address Subnet Mask3
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 256
ZTE
aclConfig_destinationIp#3 aclConfig_destSubnetMask#3 aclConfig_ruleMaxProtocol#3
Destination Address 3
Destination Address Subnet
Mask 3
Maximum Rule of Protocol
Code 3
ipv4
{aclConfig_destinationSubnetMas
k#3}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 257
ZTE
aclConfig_ruleMinProtocol#3 aclConfig_maxSourcePort#3 aclConfig_minSourcePort#3
Minimum Rule of Protocol Code
3
Maximum Source Port 3 Minimum Source Port 3
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 258
ZTE
aclConfig_maxDestPort#3 aclConfig_minDestPort#3 aclConfig_ruleAction#3
Maximum Destination Port 3 Minimum Destination Port 3 Rule Action 3
{aclConfig_maxDestinationPort#3}
long:[0..65535]
{aclConfig_minDestinationPort#3}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 259
ZTE
aclConfig_aclNo#4 aclConfig_sourceIp#4 aclConfig_sourceSubnetMask#4
Access Control List Object ID 4 Source Address 4 Source address Subnet Mask4
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 260
ZTE
aclConfig_destinationIp#4 aclConfig_destSubnetMask#4 aclConfig_ruleMaxProtocol#4
Destination Address 4
Destination Address Subnet
Mask 4
Maximum Rule of Protocol
Code 4
ipv4
{aclConfig_destinationSubnetMas
k#4}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 261
ZTE
aclConfig_ruleMinProtocol#4 aclConfig_maxSourcePort#4 aclConfig_minSourcePort#4
Minimum Rule of Protocol Code
4
Maximum Source Port 4 Minimum Source Port 4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 262
ZTE
aclConfig_maxDestPort#4 aclConfig_minDestPort#4 aclConfig_ruleAction#4
Maximum Destination Port 4 Minimum Destination Port 4 Rule Action 4
{aclConfig_maxDestinationPort#4}
long:[0..65535]
{aclConfig_minDestinationPort#4}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 263
ZTE
aclConfig_aclNo#5 aclConfig_sourceIp#5 aclConfig_sourceSubnetMask#5
Access Control List Object ID 5 Source Address 5 Source address Subnet Mask5
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 264
ZTE
aclConfig_destinationIp#5 aclConfig_destSubnetMask#5 aclConfig_ruleMaxProtocol#5
Destination Address 5
Destination Address Subnet
Mask 5
Maximum Rule of Protocol
Code 5
ipv4
{aclConfig_destinationSubnetMas
k#5}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 265
ZTE
aclConfig_ruleMinProtocol#5 aclConfig_maxSourcePort#5 aclConfig_minSourcePort#5
Minimum Rule of Protocol Code
5
Maximum Source Port 5 Minimum Source Port 5
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 266
ZTE
aclConfig_maxDestPort#5 aclConfig_minDestPort#5 aclConfig_ruleAction#5
Maximum Destination Port 5 Minimum Destination Port 5 Rule Action 5
{aclConfig_maxDestinationPort#5}
long:[0..65535]
{aclConfig_minDestinationPort#5}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 267
ZTE
aclConfig_aclNo#6 aclConfig_sourceIp#6 aclConfig_sourceSubnetMask#6
Access Control List Object ID 6 Source Address 6 Source address Subnet Mask6
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 268
ZTE
aclConfig_destinationIp#6 aclConfig_destSubnetMask#6 aclConfig_ruleMaxProtocol#6
Destination Address 6
Destination Address Subnet
Mask 6
Maximum Rule of Protocol
Code 6
ipv4
{aclConfig_destinationSubnetMas
k#6}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 269
ZTE
aclConfig_ruleMinProtocol#6 aclConfig_maxSourcePort#6 aclConfig_minSourcePort#6
Minimum Rule of Protocol Code
6
Maximum Source Port 6 Minimum Source Port 6
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 270
ZTE
aclConfig_maxDestPort#6 aclConfig_minDestPort#6 aclConfig_ruleAction#6
Maximum Destination Port 6 Minimum Destination Port 6 Rule Action 6
{aclConfig_maxDestinationPort#6}
long:[0..65535]
{aclConfig_minDestinationPort#6}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 271
ZTE
aclConfig_aclNo#7 aclConfig_sourceIp#7 aclConfig_sourceSubnetMask#7
Access Control List Object ID 7 Source Address 7 Source address Subnet Mask7
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 272
ZTE
aclConfig_destinationIp#7 aclConfig_destSubnetMask#7 aclConfig_ruleMaxProtocol#7
Destination Address 7
Destination Address Subnet
Mask 7
Maximum Rule of Protocol
Code 7
ipv4
{aclConfig_destinationSubnetMas
k#7}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 273
ZTE
aclConfig_ruleMinProtocol#7 aclConfig_maxSourcePort#7 aclConfig_minSourcePort#7
Minimum Rule of Protocol Code
7
Maximum Source Port 7 Minimum Source Port 7
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 274
ZTE
aclConfig_maxDestPort#7 aclConfig_minDestPort#7 aclConfig_ruleAction#7
Maximum Destination Port 7 Minimum Destination Port 7 Rule Action 7
{aclConfig_maxDestinationPort#7}
long:[0..65535]
{aclConfig_minDestinationPort#7}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 275
ZTE
aclConfig_aclNo#8 aclConfig_sourceIp#8 aclConfig_sourceSubnetMask#8
Access Control List Object ID 8 Source Address 8 Source address Subnet Mask8
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 276
ZTE
aclConfig_destinationIp#8 aclConfig_destSubnetMask#8 aclConfig_ruleMaxProtocol#8
Destination Address 8
Destination Address Subnet
Mask 8
Maximum Rule of Protocol
Code 8
ipv4
{aclConfig_destinationSubnetMas
k#8}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 277
ZTE
aclConfig_ruleMinProtocol#8 aclConfig_maxSourcePort#8 aclConfig_minSourcePort#8
Minimum Rule of Protocol Code
8
Maximum Source Port 8 Minimum Source Port 8
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 278
ZTE
aclConfig_maxDestPort#8 aclConfig_minDestPort#8 aclConfig_ruleAction#8
Maximum Destination Port 8 Minimum Destination Port 8 Rule Action 8
{aclConfig_maxDestinationPort#8}
long:[0..65535]
{aclConfig_minDestinationPort#8}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 279
ZTE
aclConfig_aclNo#9 aclConfig_sourceIp#9 aclConfig_sourceSubnetMask#9
Access Control List Object ID 9 Source Address 9 Source address Subnet Mask9
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 280
ZTE
aclConfig_destinationIp#9 aclConfig_destSubnetMask#9 aclConfig_ruleMaxProtocol#9
Destination Address 9
Destination Address Subnet
Mask 9
Maximum Rule of Protocol
Code 9
ipv4
{aclConfig_destinationSubnetMas
k#9}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 281
ZTE
aclConfig_ruleMinProtocol#9 aclConfig_maxSourcePort#9 aclConfig_minSourcePort#9
Minimum Rule of Protocol Code
9
Maximum Source Port 9 Minimum Source Port 9
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 282
ZTE
aclConfig_maxDestPort#9 aclConfig_minDestPort#9 aclConfig_ruleAction#9
Maximum Destination Port 9 Minimum Destination Port 9 Rule Action 9
{aclConfig_maxDestinationPort#9}
long:[0..65535]
{aclConfig_minDestinationPort#9}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 283
ZTE
aclConfig_aclNo#10 aclConfig_sourceIp#10 aclConfig_sourceSubnetMask#10
Access Control List Object ID
10
Source Address 10 Source address Subnet Mask10
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 284
ZTE
aclConfig_destinationIp#10 aclConfig_destSubnetMask#10 aclConfig_ruleMaxProtocol#10
Destination Address 10
Destination Address Subnet Mask
10
Maximum Rule of Protocol
Code 10
ipv4
{aclConfig_destinationSubnetMask#
10}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 285
ZTE
aclConfig_ruleMinProtocol#10 aclConfig_maxSourcePort#10 aclConfig_minSourcePort#10
Minimum Rule of Protocol Code
10
Maximum Source Port 10 Minimum Source Port 10
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 286
ZTE
aclConfig_maxDestPort#10 aclConfig_minDestPort#10 aclConfig_ruleAction#10
Maximum Destination Port 10 Minimum Destination Port 10 Rule Action 10
{aclConfig_maxDestinationPort#1
0}
long:[0..65535]
{aclConfig_minDestinationPort#10
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 287
ZTE
aclConfig_aclNo#11 aclConfig_sourceIp#11 aclConfig_sourceSubnetMask#11
Access Control List Object ID
11
Source Address 11 Source address Subnet Mask11
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 288
ZTE
aclConfig_destinationIp#11 aclConfig_destSubnetMask#11 aclConfig_ruleMaxProtocol#11
Destination Address 11
Destination Address Subnet Mask
11
Maximum Rule of Protocol
Code 11
ipv4
{aclConfig_destinationSubnetMask#
11}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 289
ZTE
aclConfig_ruleMinProtocol#11 aclConfig_maxSourcePort#11 aclConfig_minSourcePort#11
Minimum Rule of Protocol Code
11
Maximum Source Port 11 Minimum Source Port 11
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 290
ZTE
aclConfig_maxDestPort#11 aclConfig_minDestPort#11 aclConfig_ruleAction#11
Maximum Destination Port 11 Minimum Destination Port 11 Rule Action 11
{aclConfig_maxDestinationPort#1
1}
long:[0..65535]
{aclConfig_minDestinationPort#11
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 291
ZTE
aclConfig_aclNo#12 aclConfig_sourceIp#12 aclConfig_sourceSubnetMask#12
Access Control List Object ID
12
Source Address 12 Source address Subnet Mask12
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 292
ZTE
aclConfig_destinationIp#12 aclConfig_destSubnetMask#12 aclConfig_ruleMaxProtocol#12
Destination Address 12
Destination Address Subnet Mask
12
Maximum Rule of Protocol
Code 12
ipv4
{aclConfig_destinationSubnetMask#
12}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 293
ZTE
aclConfig_ruleMinProtocol#12 aclConfig_maxSourcePort#12 aclConfig_minSourcePort#12
Minimum Rule of Protocol Code
12
Maximum Source Port 12 Minimum Source Port 12
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 294
ZTE
aclConfig_maxDestPort#12 aclConfig_minDestPort#12 aclConfig_ruleAction#12
Maximum Destination Port 12 Minimum Destination Port 12 Rule Action 12
{aclConfig_maxDestinationPort#1
2}
long:[0..65535]
{aclConfig_minDestinationPort#12
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 295
ZTE
aclConfig_aclNo#13 aclConfig_sourceIp#13 aclConfig_sourceSubnetMask#13
Access Control List Object ID
13
Source Address 13 Source address Subnet Mask13
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 296
ZTE
aclConfig_destinationIp#13 aclConfig_destSubnetMask#13 aclConfig_ruleMaxProtocol#13
Destination Address 13
Destination Address Subnet Mask
13
Maximum Rule of Protocol
Code 13
ipv4
{aclConfig_destinationSubnetMask#
13}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 297
ZTE
aclConfig_ruleMinProtocol#13 aclConfig_maxSourcePort#13 aclConfig_minSourcePort#13
Minimum Rule of Protocol Code
13
Maximum Source Port 13 Minimum Source Port 13
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 298
ZTE
aclConfig_maxDestPort#13 aclConfig_minDestPort#13 aclConfig_ruleAction#13
Maximum Destination Port 13 Minimum Destination Port 13 Rule Action 13
{aclConfig_maxDestinationPort#1
3}
long:[0..65535]
{aclConfig_minDestinationPort#13
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 299
ZTE
aclConfig_aclNo#14 aclConfig_sourceIp#14 aclConfig_sourceSubnetMask#14
Access Control List Object ID
14
Source Address 14 Source address Subnet Mask14
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 300
ZTE
aclConfig_destinationIp#14 aclConfig_destSubnetMask#14 aclConfig_ruleMaxProtocol#14
Destination Address 14
Destination Address Subnet
Mask 14
Maximum Rule of Protocol
Code 14
ipv4
{aclConfig_destinationSubnetMask
#14}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 301
ZTE
aclConfig_ruleMinProtocol#14 aclConfig_maxSourcePort#14 aclConfig_minSourcePort#14
Minimum Rule of Protocol Code
14
Maximum Source Port 14 Minimum Source Port 14
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 302
ZTE
aclConfig_maxDestPort#14 aclConfig_minDestPort#14 aclConfig_ruleAction#14
Maximum Destination Port 14 Minimum Destination Port 14 Rule Action 14
{aclConfig_maxDestinationPort#1
4}
long:[0..65535]
{aclConfig_minDestinationPort#14
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 303
ZTE
aclConfig_aclNo#15 aclConfig_sourceIp#15 aclConfig_sourceSubnetMask#15
Access Control List Object ID
15
Source Address 15 Source address Subnet Mask15
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 304
ZTE
aclConfig_destinationIp#15 aclConfig_destSubnetMask#15 aclConfig_ruleMaxProtocol#15
Destination Address 15
Destination Address Subnet Mask
15
Maximum Rule of Protocol
Code 15
ipv4
{aclConfig_destinationSubnetMask#
15}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 305
ZTE
aclConfig_ruleMinProtocol#15 aclConfig_maxSourcePort#15 aclConfig_minSourcePort#15
Minimum Rule of Protocol Code
15
Maximum Source Port 15 Minimum Source Port 15
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 306
ZTE
aclConfig_maxDestPort#15 aclConfig_minDestPort#15 aclConfig_ruleAction#15
Maximum Destination Port 15 Minimum Destination Port 15 Rule Action 15
{aclConfig_maxDestinationPort#1
5}
long:[0..65535]
{aclConfig_minDestinationPort#15
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 307
ZTE
aclConfig_aclNo#16 aclConfig_sourceIp#16 aclConfig_sourceSubnetMask#16
Access Control List Object ID
16
Source Address 16 Source address Subnet Mask16
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 308
ZTE
aclConfig_destinationIp#16 aclConfig_destSubnetMask#16 aclConfig_ruleMaxProtocol#16
Destination Address 16
Destination Address Subnet Mask
16
Maximum Rule of Protocol
Code 16
ipv4
{aclConfig_destinationSubnetMask#
16}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 309
ZTE
aclConfig_ruleMinProtocol#16 aclConfig_maxSourcePort#16 aclConfig_minSourcePort#16
Minimum Rule of Protocol Code
16
Maximum Source Port 16 Minimum Source Port 16
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 310
ZTE
aclConfig_maxDestPort#16 aclConfig_minDestPort#16 aclConfig_ruleAction#16
Maximum Destination Port 16 Minimum Destination Port 16 Rule Action 16
{aclConfig_maxDestinationPort#1
6}
long:[0..65535]
{aclConfig_minDestinationPort#16
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 311
ZTE
aclConfig_aclNo#17 aclConfig_sourceIp#17 aclConfig_sourceSubnetMask#17
Access Control List Object ID
17
Source Address 17 Source address Subnet Mask17
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 312
ZTE
aclConfig_destinationIp#17 aclConfig_destSubnetMask#17 aclConfig_ruleMaxProtocol#17
Destination Address 17
Destination Address Subnet Mask
17
Maximum Rule of Protocol
Code 17
ipv4
{aclConfig_destinationSubnetMask#
17}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 313
ZTE
aclConfig_ruleMinProtocol#17 aclConfig_maxSourcePort#17 aclConfig_minSourcePort#17
Minimum Rule of Protocol Code
17
Maximum Source Port 17 Minimum Source Port 17
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 314
ZTE
aclConfig_maxDestPort#17 aclConfig_minDestPort#17 aclConfig_ruleAction#17
Maximum Destination Port 17 Minimum Destination Port 17 Rule Action 17
{aclConfig_maxDestinationPort#1
7}
long:[0..65535]
{aclConfig_minDestinationPort#17
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 315
ZTE
aclConfig_aclNo#18 aclConfig_sourceIp#18 aclConfig_sourceSubnetMask#18
Access Control List Object ID
18
Source Address 18 Source address Subnet Mask18
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 316
ZTE
aclConfig_destinationIp#18 aclConfig_destSubnetMask#18 aclConfig_ruleMaxProtocol#18
Destination Address 18
Destination Address Subnet Mask
18
Maximum Rule of Protocol
Code 18
ipv4
{aclConfig_destinationSubnetMask#1
8}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 317
ZTE
aclConfig_ruleMinProtocol#18 aclConfig_maxSourcePort#18 aclConfig_minSourcePort#18
Minimum Rule of Protocol Code
18
Maximum Source Port 18 Minimum Source Port 18
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 318
ZTE
aclConfig_maxDestPort#18 aclConfig_minDestPort#18 aclConfig_ruleAction#18
Maximum Destination Port 18 Minimum Destination Port 18 Rule Action 18
{aclConfig_maxDestinationPort#1
8}
long:[0..65535]
{aclConfig_minDestinationPort#18
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 319
ZTE
aclConfig_aclNo#19 aclConfig_sourceIp#19 aclConfig_sourceSubnetMask#19
Access Control List Object ID
19
Source Address 19 Source address Subnet Mask19
long:[1..48] ipv4 ipv4
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
R-W R-W R-W
<> 529 , 320
ZTE
aclConfig_destinationIp#19 aclConfig_destSubnetMask#19 aclConfig_ruleMaxProtocol#19
Destination Address 19
Destination Address Subnet Mask
19
Maximum Rule of Protocol
Code 19
ipv4
{aclConfig_destinationSubnetMask#1
9}
ipv4
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:255
R-W R-W R-W
<> 529 , 321
ZTE
aclConfig_ruleMinProtocol#19 aclConfig_maxSourcePort#19 aclConfig_minSourcePort#19
Minimum Rule of Protocol Code
19
Maximum Source Port 19 Minimum Source Port 19
1:ICMP,
11:UDP,
6:TCP,
132:SCTP,
255:ALL
long:[0..65535] long:[0..65535]
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:1
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
R-W R-W R-W
<> 529 , 322
ZTE
aclConfig_maxDestPort#19 aclConfig_minDestPort#19 aclConfig_ruleAction#19
Maximum Destination Port 19 Minimum Destination Port 19 Rule Action 19
{aclConfig_maxDestinationPort#1
9}
long:[0..65535]
{aclConfig_minDestinationPort#19
}
long:[0..65535]
0:bypass,
1:discard,
2:protect
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:65535
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:0
When access rule type is IPSec, it
should be configured, otherwise it
needn't.
General value:2
R-W R-W R-W
<> 529 , 323
ZTE
aclForFilter_localAddress aclForFilter_localNetMask aclForFilter_remoteAddress
Local IP Address Local Network Mask Remote IP Address
ipv4 ipv4 ipv4
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:0.0.0.0
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General
value:255.255.255.0
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:0.0.0.0
R-W R-W R-W
<> 529 , 324
ZTE
aclForFilter_remoteNetMask aclForFilter_minLocalPort aclForFilter_maxLocalPort
Remote Network Mask Local Port Upper Bound Local Port Lower Bound
ipv4 long:[0..65535] long:[0..65535]
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:255.255.255.0
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:0
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:65535
R-W R-W R-W
<> 529 , 325
ZTE
aclForFilter_minRemotePort aclForFilter_maxRemotePort
aclForFilter_ruleProtoco
l
Remote Port Upper Bound Remote Port Lower Bound Filter Protocol No.
long:[0..65535] long:[0..65535]
1:ICMP,
6:TCP,
17:UDP,
132:SCTP,
255:ALL
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:0
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:65535
When access rule type
is package filter, it
should be configured,
otherwise it needn't.
General value:255
R-W R-W R-W
<> 529 , 326
ZTE
aclForFilter_ruleDirection aclForFilter_ruleAction
Filter Direction Filter Action
0:IP transmission
direction,
1:IP receiving direction,
2:IP bi-direction
0:Pass,
1:Discard
When access rule type is
package filter, it should be
configured, otherwise it
needn't.
General value:2
When access rule type is
package filter, it should
be configured, otherwise
it needn't.
General value:0
R-W R-W
<> 529 , 327
ZTE
ModInd OMCSUBNETID SDRMEID
IPSecConfigI
d
ipsecNo
Modify
Indication
Subnet ID ManagedElement ID RDN IPSec Config No.
A,P long:[0..4095] long:[0..65535] long:[1..48]
long:[1..48]
<default:1>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically
, it is
unnecessary
to fill in this
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 328
ZTE
remoteAddr pfs
policyGenerationLeve
l
byteLife timeLife
Remote IP
Address
PFS Option
Policy Generation
Level
Byte Life Time Life
ipv4
<default:0.0.
0.0>
0:Disable PFS,
1:MODP768,
2:MODP1024
<default:0>
0:Default,
1:Use,
2:Require,
3:Unique
<default:3>
long: [2560..536870912]
<default:4608000>
long: [120..86400]
<default:56000>
PFS value when
IPsec is at the
2nd stage
Unit: Kbyte Unit: s
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 329
ZTE
preShareKey dpdSwitch fqdn refIpLayerConfig_ipNo refIKEPolicy_policyNo#1
Pre-share
Key
DPD Switch
Fully Qualified
Domain Name
Used IP Used IKE Policy 1
string:[0..29]
0:Close,
1:Open
<default:1>
string:[0..63] long:[0..19] long:[1..128]
Dead Peer Detection
- This extension,
also known as DPD,
is based on the
ISAKMP
Configure as IP link No.
"ipNo" of IpLayerConfig
object.
Joint configuration with
refEthernetLink.
R-W R-W-I R-W-I R-I R-W-I
<> 529 , 330
ZTE
refIKEPolicy_policyNo#2 refIKEPolicy_policyNo#3 refIKEPolicy_policyNo#4 refIKEPolicy_policyNo#5
Used IKE Policy 2 Used IKE Policy 3 Used IKE Policy 4 Used IKE Policy 5
long:[1..128] long:[1..128] long:[1..128] long:[1..128]
Joint configuration with
refEthernetLink.
Joint configuration with
refEthernetLink.
Joint configuration with
refEthernetLink.
Joint configuration with
refEthernetLink.
R-W-I R-W-I R-W-I R-W-I
<> 529 , 331
ZTE
refIKEPolicy_policyNo#6 refIKEPolicy_policyNo#7 refIKEPolicy_policyNo#8
Used IKE Policy 6 Used IKE Policy 7 Used IKE Policy 8
long:[1..128] long:[1..128] long:[1..128]
Joint configuration with
refEthernetLink.
Joint configuration with
refEthernetLink.
Joint configuration with
refEthernetLink.
R-W-I R-W-I R-W-I
<> 529 , 332
ZTE
refIPSecTransformSetNo#1 refIPSecTransformSetNo#2
Used Transform-set 1 Used Transform-set 2
{refIPSecTransformSet_transformSetN
o#1}
long:[1..40]
{refIPSecTransformSet_transformSetN
o#2}
long:[1..40]
R-W-I R-W-I
<> 529 , 333
ZTE
refIPSecTransformSetNo#3 refIPSecTransformSetNo#4
Used Transform-set 3 Used Transform-set 4
{refIPSecTransformSet_transformSetN
o#3}
long:[1..40]
{refIPSecTransformSet_transformSetN
o#4}
long:[1..40]
R-W-I R-W-I
<> 529 , 334
ZTE
refIPSecTransformSetNo#5 refIPSecTransformSetNo#6
refAccessControlList_aclN
o
Used Transform-set 5 Used Transform-set 6
Used Access Control
List
{refIPSecTransformSet_transformSetN
o#5}
long:[1..40]
{refIPSecTransformSet_transformSetN
o#6}
long:[1..40]
long:[1..48]
R-W-I R-W-I R-W-I
<> 529 , 335
ModInd
OMCSUBNET
ID
SDRMEID CmpConfigId
transportProtoc
ol
refIpLayerConfig_ipN
o
Modify
Indication
Subnet ID
ManagedEl
ement ID
RDN
Transport
Protocol Type
IP Layer Bearer
A,P long:[0..4095]
long:[0..655
35]
long:[1..1]
0:HTTP,
1:HTTPS
<default:0>
long:[0..19]
A:Add, P:Pass
Same in an
OMMB.
Unique in
subnetwork.
Generated
automatically, it
is unnecessary
to fill in this
column.
Application
layer protocol
which is used
during CMP
message
transmission.
Used IP layer bearer.
Configure as IP link
No. "ipNo" of
IpLayerConfig object.
Return To
Index
Primary Key Primary Key Primary Key R-W-I R-I
caServerIp caServerPath certificateName certificateExtension
IP Address of
CA Server
CA Server Path
Domain Name of Base
Station Certificate
Extended Option of
Base Station
Certificate
ipv4
<default:0.0.0.
0>
string string string
IP address of
CA server.
Enter the server side
URL of CMP protocol
(the remaining part with
host address and port
removed) according to
the CMP protocol
configuration of CA
server.
It is used to fill in the
application subject (subject
field value) of base station
certificate. The writing format
should meet the X.500
Standard. For example,
/C=CN/O=ZTE/CN=Nodeb01.
It is used to fill in the
extended option of
certificate
application. The
writing format is
"attribute
name=attribute
value;".
R-W-I R-W R-W R-W
caServerPort privateKeyLength controlValue
Transport Layer
Port of CA Server
Private Key
Length of Base
Station Certificate
Control value of
certificate request
message
long:[1..65535]
<default:80>
1024,
2048
<default:1024>
string
Transport layer port
ID of CA server.
Enter the option
according to the
CA server
configuration.
The generated
private key length.
It can select 1024
or 2048, unit: bit.
Enter CerRequest
information of CMP
protocol, according
to CA/RA strategy.
R-W-I R-W-I R-W
ZTE
ModInd OMCSUBNETID SDRMEID QosMapId
Modify
Indication
Subnet ID ManagedElement ID RDN
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key
117 35 1
<> 529 , 339
ZTE
qosMapNo enableSlaveFlag
serviceDscpMap_cs2GDs
cp
serviceDscpMap_ps2GDs
cp
Qos Mapping No.
Enable Slave Flag or
not
DSCP Value Associated
to 2G CS Service
DSCP Value Associated
to 2G PS Service
long:[0..4294967295]
<default:0>
1:Y,
0:N
long: [0..63,255] long: [0..63,255]
This attribute indicates the
DSCP value of 2G CS
domain services. The
value 255 indicates the IP
link does not bear this
class of service.
General value:36
This attribute indicates the
DSCP value of 2G PS
domain services. The
value 255 indicates the IP
link does not bear this
class of service.
General value:20
R-I R-W R-W R-W
0 36 20
<> 529 , 340
ZTE
serviceDscpMap_commonTransChan
serviceDscpMap_rrcConnD
scp
serviceDscpMap_r99ConverD
scp
DSCP Value Associated to Iub
common Transport Channel Service
DSCP Value Associated
to RRC Connection
Service
DSCP Value Associated to
R99 Conversational Service
{serviceDscpMap_commonTransChanD
scp}
long: [0..63,255]
long: [0..63,255] long: [0..63,255]
This attribute indicates the DSCP value
of common transport channel. The
value 255 indicates the IP link does not
bear this class of service.
General value:46
This attribute indicates the
DSCP value of RRC. The
value 255 indicates the IP
link does not bear this
class of service.
General value:36
This attribute indicates the
DSCP value of R99
conversation services. The
value 255 indicates the IP link
does not bear this class of
service.
General value:36
R-W R-W R-W
255 255 255
<> 529 , 341
ZTE
serviceDscpMap_r99StreamingDsc serviceDscpMap_r99Interactive
DSCP Value Associated to R99
Streaming Service
DSCP Value Associated to R99
Interactive Service
{serviceDscpMap_r99StreamingDsc
p}
long: [0..63,255]
{serviceDscpMap_r99InteractiveDs
cp}
long: [0..63,255]
This attribute indicates the DSCP
value of R99 streaming services.
The value 255 indicates the IP link
does not bear this class of service.
General value:36
This attribute indicates the DSCP
value of R99 interactive services.
The value 255 indicates the IP link
does not bear this class of service.
General value:20
R-W R-W
255 255
<> 529 , 342
ZTE
serviceDscpMap_r99Background
serviceDscpMap_hspaConverD
scp
serviceDscpMap_hspaStreaming
DSCP Value Associated to R99
Background Service
DSCP Value Associated to
HSPA Conversational Service
DSCP Value Associated to HSPA
Streaming Service
{serviceDscpMap_r99BackgroundD
scp}
long: [0..63,255]
long: [0..63,255]
{serviceDscpMap_hspaStreamingDs
cp}
long: [0..63,255]
This attribute indicates the DSCP
value of R99 background services.
The value 255 indicates the IP link
does not bear this class of service.
General value:0
This attribute indicates the
DSCP value of HSPA
conversation services. The
value 255 indicates the IP link
does not bear this class of
service.
General value:38
This attribute indicates the DSCP
value of HSPA streaming services.
The value 255 indicates the IP link
does not bear this class of service.
General value:255
R-W R-W R-W
255 255 255
<> 529 , 343
ZTE
serviceDscpMap_hspaInteractive serviceDscpMap_hspaBackground dscpCosMap_dscp#1
DSCP Value Associated to HSPA
Interactive Service
DSCP Value Associated to HSPA
Background Service
DSCP 1
{serviceDscpMap_hspaInteractiveDs
cp}
long: [0..63,255]
{serviceDscpMap_hspaBackground
Dscp}
long: [0..63,255]
long: [0..63]
<default:46>
This attribute indicates the DSCP
value of HSPA interactive services.
The value 255 indicates the IP link
does not bear this class of service.
General value:22
This attribute indicates the DSCP
value of HSPA background services.
The value 255 indicates the IP link
does not bear this class of service.
General value:0
R-W R-W R-W
255 255
<> 529 , 344
ZTE
dscpCosMap_cos#1 dscpCosMap_dscp#2 dscpCosMap_cos#2 dscpCosMap_dscp#3
COS 1 DSCP 2 COS 2 DSCP 3
long: [0..7]
<default:5>
long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 345
ZTE
dscpCosMap_cos#3 dscpCosMap_dscp#4 dscpCosMap_cos#4 dscpCosMap_dscp#5
COS 3 DSCP 4 COS 4 DSCP 5
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 346
ZTE
dscpCosMap_cos#5 dscpCosMap_dscp#6 dscpCosMap_cos#6 dscpCosMap_dscp#7
COS 5 DSCP 6 COS 6 DSCP 7
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 347
ZTE
dscpCosMap_cos#7 dscpCosMap_dscp#8 dscpCosMap_cos#8 dscpCosMap_dscp#9
COS 7 DSCP 8 COS 8 DSCP 9
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 348
ZTE
dscpCosMap_cos#9 dscpCosMap_dscp#10 dscpCosMap_cos#10 dscpCosMap_dscp#11
COS 9 DSCP 10 COS 10 DSCP 11
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 349
ZTE
dscpCosMap_cos#11 dscpCosMap_dscp#12 dscpCosMap_cos#12 dscpCosMap_dscp#13
COS 11 DSCP 12 COS 12 DSCP 13
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 350
ZTE
dscpCosMap_cos#13 dscpCosMap_dscp#14 dscpCosMap_cos#14 dscpCosMap_dscp#15
COS 13 DSCP 14 COS 14 DSCP 15
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 351
ZTE
dscpCosMap_cos#15 dscpCosMap_dscp#16 dscpCosMap_cos#16 dscpCosMap_dscp#17
COS 15 DSCP 16 COS 16 DSCP 17
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 352
ZTE
dscpCosMap_cos#17 dscpCosMap_dscp#18 dscpCosMap_cos#18 dscpCosMap_dscp#19
COS 17 DSCP 18 COS 18 DSCP 19
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 353
ZTE
dscpCosMap_cos#19 dscpCosMap_dscp#20 dscpCosMap_cos#20 dscpCosMap_dscp#21
COS 19 DSCP 20 COS 20 DSCP 21
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 354
ZTE
dscpCosMap_cos#21 dscpCosMap_dscp#22 dscpCosMap_cos#22 dscpCosMap_dscp#23
COS 21 DSCP 22 COS 22 DSCP 23
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 355
ZTE
dscpCosMap_cos#23 dscpCosMap_dscp#24 dscpCosMap_cos#24 dscpCosMap_dscp#25
COS 23 DSCP 24 COS 24 DSCP 25
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 356
ZTE
dscpCosMap_cos#25 dscpCosMap_dscp#26 dscpCosMap_cos#26 dscpCosMap_dscp#27
COS 25 DSCP 26 COS 26 DSCP 27
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 357
ZTE
dscpCosMap_cos#27 dscpCosMap_dscp#28 dscpCosMap_cos#28 dscpCosMap_dscp#29
COS 27 DSCP 28 COS 28 DSCP 29
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 358
ZTE
dscpCosMap_cos#29 dscpCosMap_dscp#30 dscpCosMap_cos#30 dscpCosMap_dscp#31
COS 29 DSCP 30 COS 30 DSCP 31
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 359
ZTE
dscpCosMap_cos#31 dscpCosMap_dscp#32 dscpCosMap_cos#32 dscpCosMap_dscp#33
COS 31 DSCP 32 COS 32 DSCP 33
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 360
ZTE
dscpCosMap_cos#33 dscpCosMap_dscp#34 dscpCosMap_cos#34 dscpCosMap_dscp#35
COS 33 DSCP 34 COS 34 DSCP 35
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 361
ZTE
dscpCosMap_cos#35 dscpCosMap_dscp#36 dscpCosMap_cos#36 dscpCosMap_dscp#37
COS 35 DSCP 36 COS 36 DSCP 37
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 362
ZTE
dscpCosMap_cos#37 dscpCosMap_dscp#38 dscpCosMap_cos#38 dscpCosMap_dscp#39
COS 37 DSCP 38 COS 38 DSCP 39
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 363
ZTE
dscpCosMap_cos#39 dscpCosMap_dscp#40 dscpCosMap_cos#40 dscpCosMap_dscp#41
COS 39 DSCP 40 COS 40 DSCP 41
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 364
ZTE
dscpCosMap_cos#41 dscpCosMap_dscp#42 dscpCosMap_cos#42 dscpCosMap_dscp#43
COS 41 DSCP 42 COS 42 DSCP 43
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 365
ZTE
dscpCosMap_cos#43 dscpCosMap_dscp#44 dscpCosMap_cos#44 dscpCosMap_dscp#45
COS 43 DSCP 44 COS 44 DSCP 45
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 366
ZTE
dscpCosMap_cos#45 dscpCosMap_dscp#46 dscpCosMap_cos#46 dscpCosMap_dscp#47
COS 45 DSCP 46 COS 46 DSCP 47
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 367
ZTE
dscpCosMap_cos#47 dscpCosMap_dscp#48 dscpCosMap_cos#48 dscpCosMap_dscp#49
COS 47 DSCP 48 COS 48 DSCP 49
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 368
ZTE
dscpCosMap_cos#49 dscpCosMap_dscp#50 dscpCosMap_cos#50 dscpCosMap_dscp#51
COS 49 DSCP 50 COS 50 DSCP 51
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 369
ZTE
dscpCosMap_cos#51 dscpCosMap_dscp#52 dscpCosMap_cos#52 dscpCosMap_dscp#53
COS 51 DSCP 52 COS 52 DSCP 53
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 370
ZTE
dscpCosMap_cos#53 dscpCosMap_dscp#54 dscpCosMap_cos#54 dscpCosMap_dscp#55
COS 53 DSCP 54 COS 54 DSCP 55
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 371
ZTE
dscpCosMap_cos#55 dscpCosMap_dscp#56 dscpCosMap_cos#56 dscpCosMap_dscp#57
COS 55 DSCP 56 COS 56 DSCP 57
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 372
ZTE
dscpCosMap_cos#57 dscpCosMap_dscp#58 dscpCosMap_cos#58 dscpCosMap_dscp#59
COS 57 DSCP 58 COS 58 DSCP 59
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 373
ZTE
dscpCosMap_cos#59 dscpCosMap_dscp#60 dscpCosMap_cos#60 dscpCosMap_dscp#61
COS 59 DSCP 60 COS 60 DSCP 61
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 374
ZTE
dscpCosMap_cos#61 dscpCosMap_dscp#62 dscpCosMap_cos#62 dscpCosMap_dscp#63
COS 61 DSCP 62 COS 62 DSCP 63
long: [0..7] long: [0..63] long: [0..7] long: [0..63]
R-W R-W R-W R-W
<> 529 , 375
ZTE
dscpCosMap_cos#63 dscpCosMap_dscp#64 dscpCosMap_cos#64
COS 63 DSCP 64 COS 64
long: [0..7] long: [0..63] long: [0..7]
R-W R-W R-W
<> 529 , 376
ZTE
ModInd OMCSUBNETID SDRMEID SctpId sctpNo
Modify
Indication
Subnet ID ManagedElement ID RDN SCTP Link No.
A,P long:[0..4095] long:[0..65535] long: [1..4]
long:[0..3]
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically,
it is
unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 0
<> 529 , 377
ZTE
localPort
refIpLayerConfig_ipNo#
1
remoteAddr#1
refIpLayerConfig_ipNo
#2
Local Port ID Used IP 1 Remote Address 1 Used IP 2
long:[0..65535]
<default:0>
long:[0..19] ipv4 long:[0..19]
UMTS: 0..65535
GSM: 1..65534
When radio mode is
GSM, local port ID
should be
BtsFunction's siteId.
Configure as IP link No.
"ipNo" of IpLayerConfig
object.
Configure as IP link No.
"ipNo" of IpLayerConfig
object.
R-I R-I R-I R-I
35 0 118.117.0.1
<> 529 , 378
ZTE
remoteAddr#2
refIpLayerConfig_ipN
o#3
remoteAddr#3
refIpLayerConfig_ipN
o#4
remoteAddr#4
Remote
Address 2
Used IP 3
Remote
Address 3
Used IP 4
Remote
Address 4
ipv4 long:[0..19] ipv4 long:[0..19] ipv4
Configure as IP link
No. "ipNo" of
IpLayerConfig object.
Configure as IP link
No. "ipNo" of
IpLayerConfig object.
R-I R-I R-I R-I R-I
0.0.0.0 0.0.0.0 0.0.0.0
<> 529 , 379
ZTE
remotePort inOutStreamNum dscp
Remote Port ID
Number of in-and-
out Streams
DSCP
long:[0..65535]
<default:0>
long:[2..6]
<default:2>
long:[0..63]
<default:46>
Number of incoming
and outgoing streams
of SCTP. At most six
incoming and
outgoing streams can
be configured.
IP service model
configuration. You can
choose different
model according to
the actual scenario.
R-I R-I R-I
14596 6 46
<> 529 , 380
ZTE
ModInd OMCSUBNETID SDRMEID EthernetCfmMdId mdNo
Modify
Indication
Subnet ID ManagedElement ID RDN MD No.
A,P long:[0..4095] long:[0..65535] long: [1..8]
long:[0..7]
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to
fill in this column.
It begins from
0, and must be
unique.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 381
ZTE
mdIndex
refPhyLayerPort_phyLayerPortN
o
mdLevel mdName
MD Index ID Used Physical Port MD Level MD Name
long:[1..8]
<default:1>
long:[0..17]
long:[0..7]
<default:0>
string:[0..43]
It begins from
1, and must be
unique.
This base station belongs to an
Ethernet port of the MD. At
present, only the Iub/Abis
interface of CC board can be
used.
R-I R-I R-W-I R
<> 529 , 382
ZTE
ModInd OMCSUBNETID SDRMEID mdNo
EthernetCfmM
aId
Modify
Indication
Subnet ID ManagedElement ID MD No. RDN
A,P long:[0..4095] long:[0..65535]
{EthernetCfmMd_mdNo}
long:[0..7]
long: [1..4]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
The data should be set as
MD No. of EthernetCfmMd
object.
Generated
automatically,
it is
unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
<> 529 , 383
ZTE
maNo maIndex
refEthernetLink_ethernetLinkN
o
vid maName
MA No. MA Index ID Used Ethernet Link VLAN ID MA Mame
long:[0..31]
<default:0>
long: [1..4]
<default:1>
long:[0..0]
long:[1..4094]
string:[0..43]
It begins from
0, and must be
unique.
It begins from
1, and must be
unique.
IP link used by MA.
VLAN used by MA.
At present, one MA
only supports one
VLAN.
R-I R-I R-I R-I R-W-I
<> 529 , 384
ZTE
ccmPeriod
CCM Detection Duration
3:100ms,
4:1s,
5:10s,
6:1min,
7:10min
<default:3>
CCM detection period. If the
CCM message from the
opposite end is not received
after 3.5 times of the period,
the link is considered
abnormal.
R-W-I
<> 529 , 385
ZTE
ModInd OMCSUBNETID SDRMEID maNo
EthernetCfmMpI
d
Modify
Indication
Subnet ID ManagedElement ID MA No. RDN
A,P long:[0..4095] long:[0..65535]
{EthernetCfmMa_maNo}
long:[0..31]
long: [1..32]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
The data should be set as
MA No. of EthernetCfmMa
object.
Generated
automatically, it
is unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
<> 529 , 386
ZTE
mpNo mpIndex mepFullNetNo mepType
localMEPConfig_localLeve
l
MP No. MP Index ID MEP Full Net No. MEP Type Local MEP Level
long:[0..255]
<default:0>
long: [1..32]
<default:1>
long: [1..8191]
<default:1>
1:Local MEP,
2:Remote MEP
<default:1>
long: [0..7]
It begins from
0, and must be
unique.
It begins from
1, and must
be unique.
MEP number
(MEPId). It is set
by the user, and
must be unique
within the MA
range.
It is valid when MPE type
is set as local MEP.
R-I R-I R-I R-W-I R-W
<> 529 , 387
ZTE
localMEPConfig_almLowestLeve
l
remoteMEPConfig_localMPInd
ex
remoteMEPConfig_remMEPMacAddr
Lowest Alarm Level Associated Local MP Index MAC Address of Remote MEP
{localMEPConfig_alarmLowestL
evel}
long: [1..5]
long: [1..32]
{remoteMEPConfig_remoteMEPMacA
ddr}
string
It is valid when MPE type is set
as local MEP.
It is valid when MPE type is
set as local MEP.
It is valid when MPE type is set as
local MEP. MAC address of remote
MEP, seperated with '-'.
R-W R-W R-W
<> 529 , 388
ZTE
enableCCMDetect
Enable CCM Detection or not
1:Y,
0:N
<default:0>
If MEP type is local MEP,
enabling the CCM detection
means that the local end
performs multicast CCM
detection. If MEP type is remote
MEP, enabling the CCM
detection means that the local
end performs unicast CCM
detection for the remote end. The
current version only supports
multicast CCM detection.
R-I
<> 529 , 389
ZTE
ModInd OMCSUBNETID SDRMEID BfdId bfdNo
Modify
Indication
Subnet ID ManagedElement ID RDN
Bidirectional
Forwarding Detection
link No.
A,P long:[0..4095] long:[0..65535] long: [1..10]
long:[1..10]
<default:1>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 390
ZTE
refUdp_ipNo destinationIp dscp
Used UDP Destination IP Address DSCP
long:[0..19]
ipv4
<default:0.0.0.0>
long:[0..63]
<default:46>
Configure as IP
link No. "ipNo" of
IpLayerConfig
object.
IP address of the opposite
end. It is combined with the
local IP address to form an
IP path to be detected.
BFD packet service quality
priority. You can set it within
the value range. It is
recommended to set it to 46.
R-I R-I R-I
<> 529 , 391
ZTE
multiHop desiredMinTxInterval requiredMinRxInterval detectAccumulator
Multi-hop Test or not
Minimum Packet
Transmitting Intervall
Minimum Packet
Receiving Interval
Detection Time
Accumlator
1:Y,
0:N
<default:0>
long:[100..100000]
<default:300>
long:[100..100000]
<default:300>
long:[3..255]
<default:5>
Detection mode: multi-hop
detection or single-hop
detection. For direct
connection, set it to N (single-
hop detection). If there are
other switching devices in the
connection, set it to Y (multi-
hop detection).
If the BFD detection mode is
multi-hop detection, only one
Unit: ms
Configure minimum packet
transmitting interval,
expected by local end. This
value is determined upon
both ends' negotiation.
Once this value is
changed, it will cause BFD
session to be negotiated
again.
Unit: ms
Configure minimum
packet receiving
interval, supported by
local end. This value is
determined upon both
ends' negotiation.
Once this value is
changed, it will cause
BFD session to be
Configure BFD
conversation
detection time
accumlator. This
value is determined
upon both ends'
negotiation. Once this
value is changed, it
will cause BFD
session to be
R-I R-W-I R-W-I R-W-I
<> 529 , 392
ZTE
bfdAuthority_authorityTyp
e
bfdAuthority_authorityKeyI
d
bfdAuthority_authorityKeyValue
Authentication type Authentication Key ID Authentication Key
0:Not support
authentication,
1:Simple Password,
2:Keyed MD5,
3:Meticulous Keyed MD5,
4:Keyed SHA1,
5:Meticulous Keyed
SHA1
long:[1..255] string:[39..79]
This attribute indicates
the BFD authority type. It
is a parameter for
interconnection.
General value:1
This attribute indicates the
ID of the authority key. It is
a parameter for
interconnection.
General value:1
Config authentication key. There are 20
values in tatal and each value range is
[0..255]. The values seperates by '.'.
(1)When Authentication type is 1,Valid
Authentication key is the first 5 values;
(2)When Authentication type is 2 or 3,Valid
Authentication key is the first 16 values;
General
value:0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0
R-W R-W R-W
<> 529 , 393
ZTE
ModInd OMCSUBNETID SDRMEID IpClockProfileId linkPriority
Modify
Indication
Subnet ID ManagedElement ID RDN Link Priority
A,P long:[0..4095] long:[0..65535] long: [1..32]
long:[1..32]
<default:1>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it
is unnecessary to
fill in this column.
Link priority
configuration of IP
clock, cannot be
duplicate.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 394
ZTE
transType syncServerAddr gatewayIp refUdp_ipNo
IP Clock
Transmission
Sync Server IP
Address
Sync Server
Gateway IP
UDP Used by 1588
Clock
0:multicast,
1:unicast
<default:1>
ipv4
<default:0.0.0.0>
ipv4
<default:0.0.0.0>
long:[0..19]
1588 clock packet
transmission mode.
IP address of 1588
clock
synchronization
server.
Gateway of 1588
clock
synchronization
server.
Configure as IP link
No. "ipNo" of
IpLayerConfig object.
R-I R-W-I R-W-I R-I
<> 529 , 395
ZTE
dscp
DSCP
long:[0..63]
<default:46>
1588 clock packet service quality priority.
You can set it within the value range. It is
recommended to set it to 46.
R-I
<> 529 , 396
ZTE
ModInd OMCSUBNETID SDRMEID nodeBId paShareRatio
Modify
Indication
Subnet ID ManagedElement ID NodeB ID
Power-
sharing Ratio
A,P long:[0..4095] long:[0..65535]
long:[0..65535]
<default:0>
long:[0..50]
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
NodeB ID. It is an
interconnection
parameter.
It represents
the
transmission
power sharing
ratio of all
local cells in a
PA. All PAs
within the
same NodeB
use this value. Return To
Index
Primary Key Primary Key R-W-I R-W-I
<> 529 , 397
ZTE
enableDPT rncCheckPeriod maxUplinkCE maxDownlinkCE
Dynamic Power
Track(DPT)
RNC Check Period
Maximum Number of
Uplink CE
Maximum Number of
Downlink CE
1: Y,
0: N
<default:0>
long:[0, 3..60]
<default:0>
long:[1..3840, 65535]
<default:65535>
long:[1..3840, 65535]
<default:65535>
0:Invalid
Unit: minute
The parameter indicates the
requirement period for NodeB to
detect RNC audit. It will switch to
standby RNC if no audit
requirement from active RNC is
received within the period. 0
indicates no standby RNC exists.
65535: invalid
It represents the
maximum amount of
CEs available for the
uplink of NodeB.
65535: invalid
It represents the
maximum amount of
CEs available for the
downlink of NodeB.
R-W-I R-W-I R-W-I R-W-I
<> 529 , 398
ZTE
powerCompensation setICMode linkProtectTime enableARake
Reference Power Adjust
Enable Uplink
Interference Clear or not
Link Protect Time
Enable A-RAKE
or not
0:Not support,
1:Support
<default:1>
long:[0..7]
<default:0>
long:[2..120]
<default:60>
1:Y,
0:N
<default:0>
It sets whether to perform
power compensation for the
HS-PDSCH code channel.
After the power
compensation function is
enabled, if the transmission
block size cannot be
increased (that is, the block
size is already the maximum
transmission block
It sets whether the MUD-
based uplink interference
cancellation function is
enabled.
BIT0:PIC,BIT1:OIC,BIT2:
TIC
0:unenable;1:enable
Unit: second
The service will
break,when the time of
transmission link
intercruption is equal to
Link Protect Time.
It sets whether the
advanced RAKE
receiver function
is enabled.
R-W-I R-W-I R-W-I R-W-I
<> 529 , 399
ZTE
hsdpaSpi#1 hsdpaSpi#2 hsdpaSpi#3 hsdpaSpi#4 hsdpaSpi#5 hsdpaSpi#6 hsdpaSpi#7
HSDPA SPI 0 HSDPA SPI 1
HSDPA SPI
2
HSDPA SPI 3 HSDPA SPI 4 HSDPA SPI 5 HSDPA SPI 6
long: [1..2000]
<default:10>
long: [1..2000]
<default:12>
long:
[1..2000]
<default:14>
long:
[1..2000]
<default:17>
long:
[1..2000]
<default:21>
long: [1..2000]
<default:25>
long: [1..2000]
<default:30>
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
It is the
weight
correspondin
g to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger
It is the
weight
correspondin
g to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger the
It is the
weight
correspondin
g to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
R-W-I R-W-I R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 400
ZTE
hsdpaSpi#8 hsdpaSpi#9 hsdpaSpi#10 hsdpaSpi#11 hsdpaSpi#12 hsdpaSpi#13
HSDPA SPI 7 HSDPA SPI 8 HSDPA SPI 9 HSDPA SPI 10 HSDPA SPI 11 HSDPA SPI 12
long: [1..2000]
<default:36>
long: [1..2000]
<default:43>
long: [1..2000]
<default:52>
long: [1..2000]
<default:62>
long: [1..2000]
<default:74>
long: [1..2000]
<default:89>
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSDPA
scheduling. The
larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding to
the 16 priorities
(SPI0 ~ SPI15)
in HSDPA
scheduling. The
larger the weight
is, the easier the
scheduling is. In
configuration, it
R-W-I R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 401
ZTE
hsdpaSpi#14 hsdpaSpi#15 hsdpaSpi#16 hsupaSpi#1 hsupaSpi#2 hsupaSpi#3
HSDPA SPI 13 HSDPA SPI 14
HSDPA SPI
15
HSUPA SPI 0 HSUPA SPI 1 HSUPA SPI 2
long: [1..2000]
<default:107>
long: [1..2000]
<default:128>
long: [1..2000]
<default:154>
long: [1..4096]
<default:1>
long: [1..4096]
<default:2>
long: [1..4096]
<default:3>
It is the weight
corresponding to
the 16 priorities
(SPI0 ~ SPI15)
in HSDPA
scheduling. The
larger the weight
is, the easier the
scheduling is. In
configuration, it
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSDPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
R-W-I R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 402
ZTE
hsupaSpi#4 hsupaSpi#5 hsupaSpi#6 hsupaSpi#7 hsupaSpi#8 hsupaSpi#9 hsupaSpi#10
HSUPA SPI 3 HSUPA SPI 4 HSUPA SPI 5 HSUPA SPI 6 HSUPA SPI 7
HSUPA SPI
8
HSUPA SPI
9
long: [1..4096]
<default:4>
long: [1..4096]
<default:5>
long: [1..4096]
<default:6>
long: [1..4096]
<default:7>
long: [1..4096]
<default:8>
long:
[1..4096]
<default:9>
long:
[1..4096]
<default:10>
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding to
the 16 priorities
(SPI0 ~ SPI15)
in HSUPA
scheduling. The
larger the weight
is, the easier the
scheduling is. In
configuration, it
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
It is the
weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSUPA
scheduling.
The larger the
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
It is the
weight
correspondin
g to the 16
priorities
(SPI0 ~
SPI15) in
HSUPA
scheduling.
The larger
It is the
weight
correspondin
g to the 16
priorities
(SPI0 ~
SPI15) in
HSUPA
scheduling.
The larger
R-W-I R-W-I R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 403
ZTE
hsupaSpi#11 hsupaSpi#12 hsupaSpi#13 hsupaSpi#14 hsupaSpi#15 hsupaSpi#16
HSUPA SPI
10
HSUPA SPI
11
HSUPA SPI 12
HSUPA SPI
13
HSUPA SPI
14
HSUPA SPI
15
long: [1..4096]
<default:11>
long: [1..4096]
<default:12>
long: [1..4096]
<default:13>
long: [1..4096]
<default:14>
long: [1..4096]
<default:15>
long: [1..4096]
<default:16>
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
It is the weight
corresponding
to the 16
priorities
(SPI0 ~
SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
It is the weight
corresponding
to the 16
priorities (SPI0
~ SPI15) in
HSUPA
scheduling.
The larger the
weight is, the
easier the
R-W-I R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 404
ZTE
adminState
Manual Operation
Field
0:No Manual
Operation,
1:Block,
2:Disabled,
4:Powered-down,
65536:Block
Smoothly
<default:0>
This field can not
be configured. Do
not modify it.
R-W
<> 529 , 405
ZTE
ModInd OMCSUBNETID SDRMEID reserveParamter1
Modify
Indication
Subnet ID ManagedElement ID Reserve parameter 1
A,P long:[0..4095] long:[0..65535] long
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Return To
Index
Primary Key Primary Key R-W
<> 529 , 406
ZTE
reserveParamter2 reserveParamter3 reserveParamter4 reserveParamter5
Reserve parameter 2 Reserve parameter 3 Reserve parameter 4 Reserve parameter 5
long long long long
R-W R-W R-W R-W
<> 529 , 407
ZTE
reserveParamter6 reserveParamter7 reserveParamter8 reserveParamter9
Reserve parameter 6 Reserve parameter 7 Reserve parameter 8 Reserve parameter 9
long long long long
R-W R-W R-W R-W
<> 529 , 408
ZTE
reserveParamter10 reserveParamter11 reserveParamter12 reserveParamter13
Reserve parameter
10
Reserve parameter
11
Reserve parameter
12
Reserve parameter
13
long long long long
R-W R-W R-W R-W
<> 529 , 409
ZTE
reserveParamter14 reserveParamter15 reserveParamter16 reserveParamter17
Reserve parameter
14
Reserve parameter
15
Reserve parameter
16
Reserve parameter
17
long long long long
R-W R-W R-W R-W
<> 529 , 410
ZTE
reserveParamter18 reserveParamter19 reserveParamter20 reserveParamter21
Reserve parameter
18
Reserve parameter
19
Reserve parameter
20
Reserve parameter
21
long long long long
R-W R-W R-W R-W
<> 529 , 411
ZTE
reserveParamter22 reserveParamter23 reserveParamter24 reserveParamter25
Reserve parameter
22
Reserve parameter
23
Reserve parameter
24
Reserve parameter
25
long long long long
R-W R-W R-W R-W
<> 529 , 412
ZTE
reserveParamter26 reserveParamter27 reserveParamter28 reserveParamter29
Reserve parameter
26
Reserve parameter
27
Reserve parameter
28
Reserve parameter
29
long long long long
R-W R-W R-W R-W
<> 529 , 413
ZTE
reserveParamter30
Reserve parameter
30
long
R-W
<> 529 , 414
ZTE
ModInd OMCSUBNETID SDRMEID IubLinkId rncId
Modify
Indication
Subnet ID ManagedElement ID RDN RNC ID
A,P long:[0..4095] long:[0..65535] long:[1..4294967295] long
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
ID of the opposite-
end RNC connected
with the Iub link. It
identifies with which
RNC IubLink is
connected. You may
not set it.
Return To
Index
Primary Key Primary Key Primary Key R-W
<> 529 , 415
ZTE
iubLinkClass
Class of Iub Link
0:Master,
1:Slave
<default:0>
Active/standby
class of the Iub
link. It helps users
to distinguish the
active Iub link and
the standby Iub
link.
R-I
<> 529 , 416
ZTE
ModInd OMCSUBNETID SDRMEID iubLinkClass
Modify
Indication
Subnet ID ManagedElement ID Class of Iub Link
A,P long:[0..4095] long:[0..65535]
{IubLink_iubLinkClass}
long
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Configure as class of
Iub link "iubLinkClass"
of IubLink object.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 417
ZTE
IubDataStreamId refUdp_ipNo refAal2_pvcNo
refOperator_operatorName#
1
RDN Used UDP Used AAL2 Operator 1
long:[1..429496729
5]
long:[0..19] long:[1..50] string:[0..127]
Generated
automatically, it is
unnecessary to fill
in this column.
Configure as IP link
No. "ipNo" of
IpLayerConfig object.
Primary Key R R R-I
<> 529 , 418
ZTE
refOperator_operatorNam
e#2
refOperator_operatorNam
e#3
Operator 2 Operator 3
string:[0..127] string:[0..127]
R-I R-I
<> 529 , 419
ZTE
ModInd OMCSUBNETID SDRMEID iubLinkClass
NbapCSignalling
Id
Modify
Indication
Subnet ID ManagedElement ID Class of Iub Link RDN
A,P long:[0..4095] long:[0..65535]
{IubLink_iubLinkClas
s}
long:[0..1]
long: [1..4]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Configure as class of
Iub link
"iubLinkClass" of
IubLink object.
Generated
automatically, it
is unnecessary
to fill in this
column.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
<> 529 , 420
ZTE
ncpNo rncLinkClass sctpStreamId refSaalUni_pvcNo refSctp_sctpNo
NBAP Common
Signalling No.
RNC Link Class SCTP Stream ID Used SaalUni Used SCTP
long:[0..3]
<default:0>
0:Master,
1:Slave
<default:0>
long: [0..5]
long:[64490,64500..6451
6]
long:[0..3]
It indicate the
link is active
RNC or standby
RNC.
It is the ID of SCTP
stream that bears NCP.
It is an interconnection
parameter. The SCTP
stream ID can be
configured only when the
SCTP link is used.
AAL5 link that bears
NCP. It and refSctp are
mutually exclusive.
SCTP link that
bears NCP. It and
refSaalUni are
mutually exclusive.
R-I R-W-I R-W R R
<> 529 , 421
ZTE
refOperator_operatorNam
e#1
refOperator_operatorName#
2
refOperator_operatorNam
e#3
Operator 1 Operator 2 Operator 3
string:[0..127] string:[0..127] string:[0..127]
R-I R-I R-I
<> 529 , 422
ZTE
ModInd OMCSUBNETID SDRMEID iubLinkClass
NbapDSignallingI
d
Modify
Indication
Subnet ID ManagedElement ID Class of Iub Link RDN
A,P long:[0..4095] long:[0..65535]
{IubLink_iubLinkClass}
long:[0..1]
long: [1..24]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Configure as class of
Iub link "iubLinkClass"
of IubLink object.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
<> 529 , 423
ZTE
ccpNo signallingPortId rncLinkClass sctpStreamId refSaalUni_pvcNo
NBAP Dedicated
Signalling No.
Signalling Port
ID
RNC Link Class SCTP Stream ID Used SaalUni
long:[0..23]
<default:0>
long: [0..5]
<default:1>
0:Master,
1:Slave
<default:0>
long: [0..5]
long:[64490,64500..64516
]
CCP port
number. It is an
interconnection
parameter.
It indicate the
link is active
RNC or standby
RNC.
It is the ID of SCTP
stream that bears
CCP. It is an
interconnection
parameter. The
SCTP stream ID
AAL5 link that bears CCP.
It and refSctp are mutually
exclusive.
R-I R-W-I R-W-I R-W R
<> 529 , 424
ZTE
refSctp_sctpNo
refOperator_operatorName#
1
refOperator_operatorNam
e#2
refOperator_operatorName#
3
Used SCTP Operator 1 Operator 2 Operator 3
long:[0..3] string:[0..127] string:[0..127] string:[0..127]
SCTP link that
bears CCP. It
and refSaalUni
are mutually
exclusive.
R R-I R-I R-I
<> 529 , 425
ZTE
ModInd OMCSUBNETID SDRMEID USectorId sectorId
Modify
Indication
Subnet ID ManagedElement ID RDN Sector ID
A,P long:[0..4095] long:[0..65535] long:[1..30]
long:[0..255]
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it
is unnecessary to
fill in this column.
A sector ID must
be unique.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 426
ZTE
userLabel band txType
refTxDevice_rackN
o#1
refTxDevice_port
#1
Sector Name Band Tx Type
Used Tx Device
Rack No.1
Used Tx Device
Port No.1
string:[0..199]
1:2.1G(Band I),
2:1900M(Band II),
3:1800M(Band III),
4:AWS(Band IV),
5:850M(Band V),
6:850M(Band VI),
7:2.6G(Band VII),
8:900M(Band VIII),
9:1800M(Band IX)
0:No Diversity,
2:2-RRU NOT DIV,
5:3-RRU NOT DIV,
3:4-RRU NOT DIV,
4:5-RRU NOT DIV,
7:6-RRU NOT DIV,
8:MIMO
long:[2..201] long:[1..5]
Cannot use the
invalid characters,
e.g. < > & ' " \ / :
? # % @ ,
It sets the frequency
band information of
the sector. All RF
units in this sector
must support the
frequency band.
Downlink signal
transmission type,
such as whether it
is diversified and
the diversity type.
You can set
different
transmission types
according to
different application
scenarios.
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency
bands of all
selected RF
devices must be
consistent.
R-W R-I R-I R-I R-I
<> 529 , 427
ZTE
refTxDevice_rackNo#
2
refTxDevice_port#2
refTxDevice_rackNo#
3
refTxDevice_port#3
Used Tx Device
Rack No.2
Used Tx Device Port
No.2
Used Tx Device
Rack No.3
Used Tx Device Port
No.3
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
R-W R-W R-W R-W
<> 529 , 428
ZTE
refTxDevice_rackNo#
4
refTxDevice_port#4
refTxDevice_rackNo#
5
refTxDevice_port#5
Used Tx Device
Rack No.4
Used Tx Device Port
No.4
Used Tx Device
Rack No.5
Used Tx Device Port
No.5
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
R-W R-W R-W R-W
<> 529 , 429
ZTE
refTxDevice_rackNo#
6
refTxDevice_port#6
refTxDevice_rackNo#
7
refTxDevice_port#7
Used Tx Device
Rack No.6
Used Tx Device Port
No.6
Used Tx Device
Rack No.7
Used Tx Device Port
No.7
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
R-W R-W R-W R-W
<> 529 , 430
ZTE
refTxDevice_rackNo#
8
refTxDevice_port#8
refTxDevice_rackNo#
9
refTxDevice_port#9
Used Tx Device
Rack No.8
Used Tx Device Port
No.8
Used Tx Device
Rack No.9
Used Tx Device Port
No.9
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
R-W R-W R-W R-W
<> 529 , 431
ZTE
refTxDevice_rackNo#
10
refTxDevice_port#10
refTxDevice_rackNo#
11
refTxDevice_port#11
Used Tx Device
Rack No.10
Used Tx Device Port
No.10
Used Tx Device
Rack No.11
Used Tx Device Port
No.11
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
R-W R-W R-W R-W
<> 529 , 432
ZTE
refTxDevice_rackNo#
12
refTxDevice_port#12 rxType
refRxDevice_rackNo#
1
Used Tx Device
Rack No.12
Used Tx Device Port
No.12
Rx Type
Used Rx Device
Rack No.1
long:[2..201] long:[1..5]
1:No Diversity,
2:Diversity,
9:2-RRU NOT DIV,
4:2-RRU DIV,
11:3-RRU NOT DIV,
6:3-RRU DIV,
8:4-RRU NOT DIV,
3:4-RRU DIV,
10:5-RRU NOT DIV,
long:[2..201]
RU No.
Select the RF
transmissin device
according to the
configured
transmission type.
The frequency bands
of all selected RF
devices must be
consistent.
Uplink signal receiving
type, such as whether
the receiving diversity is
supported and the
receiving diversity type.
You can set the
receiving type according
to the actual application
scenario and the
configured transmissin
type.
RU No.
Select the RF
receiving device
according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
R-W R-W R-I R-I
<> 529 , 433
ZTE
refRxDevice_port#
1
refRxDevice_rackNo#
2
refRxDevice_port#
2
refRxDevice_rackN
o#3
refRxDevice_port#
3
Used Rx Device
Port No.1
Used Rx Device Rack
No.2
Used Rx Device
Port No.2
Used Rx Device
Rack No.3
Used Rx Device
Port No.3
long:[1..5] long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF
receiving device
according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
RU No.
Select the RF
receiving device
according to the
receiving type. The
frequency bands of
all selected RF
devices must be
consistent.
R-I R-W R-W R-W R-W
<> 529 , 434
ZTE
refRxDevice_rackNo#4
refRxDevice_port#
4
refRxDevice_rackNo
#5
refRxDevice_port#5
Used Rx Device Rack
No.4
Used Rx Device
Port No.4
Used Rx Device
Rack No.5
Used Rx Device
Port No.5
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF
receiving device
according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
RU No.
Select the RF
receiving device
according to the
receiving type. The
frequency bands of
all selected RF
devices must be
consistent.
R-W R-W R-W R-W
<> 529 , 435
ZTE
refRxDevice_rackNo#6
refRxDevice_port#
6
refRxDevice_rackNo#7
refRxDevice_port#
7
Used Rx Device Rack
No.6
Used Rx Device
Port No.6
Used Rx Device Rack
No.7
Used Rx Device
Port No.7
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF receiving
device according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
RU No.
Select the RF
receiving device
according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
R-W R-W R-W R-W
<> 529 , 436
ZTE
refRxDevice_rackNo#8
refRxDevice_port#
8
refRxDevice_rackNo#
9
refRxDevice_port#
9
Used Rx Device Rack
No.8
Used Rx Device
Port No.8
Used Rx Device
Rack No.9
Used Rx Device
Port No.9
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF receiving
device according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
RU No.
Select the RF
receiving device
according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
R-W R-W R-W R-W
<> 529 , 437
ZTE
refRxDevice_rackNo#1
0
refRxDevice_port#
10
refRxDevice_rackNo#1
1
refRxDevice_port#
11
Used Rx Device Rack
No.10
Used Rx Device
Port No.10
Used Rx Device Rack
No.11
Used Rx Device
Port No.11
long:[2..201] long:[1..5] long:[2..201] long:[1..5]
RU No.
Select the RF receiving
device according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
RU No.
Select the RF receiving
device according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
R-W R-W R-W R-W
<> 529 , 438
ZTE
refRxDevice_rackNo#12
refRxDevice_port#
12
Used Rx Device Rack
No.12
Used Rx Device
Port No.12
long:[2..201] long:[1..5]
RU No.
Select the RF receiving
device according to the
receiving type. The
frequency bands of all
selected RF devices
must be consistent.
R-W R-W
<> 529 , 439
ZTE
ModInd OMCSUBNETID SDRMEID sectorId ULocalCellId
Modify
Indication
Subnet ID ManagedElement ID Sector ID RDN
A,P long:[0..4095] long:[0..65535]
{Usector_sectorId
}
long:[0..255]
long:[1..4294967295]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Configure as
sector ID of
Usector.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
<> 529 , 440
ZTE
localCellId userLabel coverageType
isAutoAssignBasebandResour
ce
Local Cell ID
Local Cell
Description
Coverage
Type
Automatically Assign
Baseband Resource or not
long:[0..268435455]
<default:0>
string:[0..199]
0:Indoor,
1:Outdoor
<default:1>
1:Y,
0:N
<default:1>
It is an
interconnection
parameter, and
must be consistent
with that of RNC.
Cannot use the
invalid
characters, e.g.
< > & ' " \ / : ?
# % @ ,
It sets whether to
automatically allocate the
baseband resource
(BpDevice) for the local cell. If
it is set to "Y", the system
automatically allocates the
baseband resource for the
local cell. If it is set to "N", the
user allocates the baseband
resource according to the
actual requirement.
R-I R-W R-W-I R-W-I
<> 529 , 441
ZTE
refBpDevice_subRackNo#
1
refBpDevice_slotN
o#1
refBpDevice_subRackNo#
2
refBpDevice_slotN
o#2
Used Baseband Board 1
SubRack No.
Used Baseband
Board 1 Slot No.
Used Baseband Board 2
SubRack No.
Used Baseband
Board 2 Slot No.
long: [1..2] long: [4..8] long: [1..2] long: [4..8]
Format: subRack No.
It configures the baseband
resource allocated for the
local cell. If the baseband
resource is automatically
allocated, this parameter
needs not be configured;
otherwise, at least one
baseband board should be
allocated.
Format: slot No.
Format: subRack No.
It configures the baseband
resource allocated for the
local cell. If the baseband
resource is automatically
allocated, this parameter
needs not be configured;
otherwise, at least one
baseband board should be
allocated.
Format: slot No.
R-I R-I R-I R-I
<> 529 , 442
ZTE
refBpDevice_subRackNo#
3
refBpDevice_slotNo
#3
refBpDevice_subRackNo#
4
refBpDevice_slotNo#
4
Used Baseband Board 3
SubRack No.
Used Baseband
Board 3 Slot No.
Used Baseband Board 4
SubRack No.
Used Baseband
Board 4 Slot No.
long: [1..2] long: [4..8] long: [1..2] long: [4..8]
Format: subRack No.
It configures the baseband
resource allocated for the
local cell. If the baseband
resource is automatically
allocated, this parameter
needs not be configured;
otherwise, at least one
baseband board should be
allocated.
Format: slot No.
Format: subRack No.
It configures the baseband
resource allocated for the
local cell. If the baseband
resource is automatically
allocated, this parameter
needs not be configured;
otherwise, at least one
baseband board should be
allocated.
Format: slot No.
R-I R-I R-I R-I
<> 529 , 443
ZTE
refBpDevice_subRackNo#
5
refBpDevice_slotNo
#5
rcvFilterBandwidt
h
txFreq
Used Baseband Board 5
SubRack No.
Used Baseband
Board 5 Slot No.
Receive Filter
Bandwidth
Tx Frequency
long: [1..2] long: [4..8]
50: 5M,
48: 4.8M,
46: 4.6M,
44: 4.4M,
42: 4.2M,
38: 3.8M
<default:50>
double
Format: subRack No.
It configures the baseband
resource allocated for the
local cell. If the baseband
resource is automatically
allocated, this parameter
needs not be configured;
otherwise, at least one
baseband board should be
allocated.
Format: slot No.
USector.band==1{[2110.0..2170.0]},
USector.band==2{[1930.0..1990.0]},
USector.band==3{[1805.0..1880.0]},
USector.band==4{[2110.0..2155.0]},
USector.band==5{[869.0..894.0]},
USector.band==6{[875.0..885.0]},
USector.band==7{[2620.0..2690.0]},
USector.band==8{[925.0..960.0]},
USector.band==9{[1884.9..1979.9]}
Unit: MHz.
General
valueUSector.band==1{[2110.0]},
USector.band==2{[1930.0]},
USector.band==3{[1805.0]},
USector.band==4{[2110.0]},
USector.band==5{[869.0]},
USector.band==6{[875.0]},
R-I R-I R-W-I R-W-I
<> 529 , 444
ZTE
rxFreq supportSpeed cellRadius txOffset
Rx Frequency Support Speed Cell Radius Downlink Delay Offset
double
0:0-250km/h,
1:250-350km/h
<default:0>
2500: 2.5km,
5000: 5km,
10000: 10km,
20000: 20km,
40000: 40km,
80000: 80km,
120000: 120km,
240000: 240km
<default:5000>
long: [-63..63]
<default:0>
USector.band==1{[1920.0..1980.0
]},
USector.band==2{[1850.0..1910.0
]},
USector.band==3{[1710.0..1785.0
]},
USector.band==4{[1710.0..1755.0
]},
USector.band==5{[824.0..849.0]},
USector.band==6{[830.0..840.0]},
USector.band==7{[2500.0..2570.0
]},
USector.band==8{[880.0..915.0]},
USector.band==9{[1749.9..1784.9
]}
Unit: MHz.
General
Terminal
moving rate
supported by
the local cell. If
it is set to 1:250-
350km/h, more
uplink access
resource will be
used.
Uplink receiving
range of the
local cell. If it is
increased, the
uplink searching
range of the cell
is also
increased. If it is
decreased, the
searching range
of the cell is also
decreased.
When
performing the
adjustment,
make sure that it
matches the
Unit: chip.
It is used to adjust the
downlink channel delay
of the cell and the
uplink search window
position.
If it is increased, the
search window is
pushed farther.
R-W-I R-W-I R-W-I R-W-I
<> 529 , 445
ZTE
rxOffset maxDlPwr enable2msGain enableVAM enhancedVamEnable
Uplink Delay Offset
Local Cell Tx
Power
Support 2ms gain
or not
Support VAM
function or not
Enable E-VAM
function or not
long: [-63..63]
<default:0>
long:[1..200, 255]
<default:255>
0: Enable,
1: Disable
<default:0>
1: Y,
0: N
1: Y,
0: N
Unit: chip.
It is used to adjust the
uplink channel delay
of the cell and the
uplink search window
position.
If it is increased, the
search window is
pushed farther.
Unit: W.
Maximum
transmission power
of the local cell. It
must be larger than
or equal to the
transmission power
configured for RNC.
The sum of
transmission power
of all local cells that
the same RU power
amplifier bears must
be smaller than the
rated power
(PaDevice.powewr).
255 indicates not
It indicates
whether HSUPA
supports TTI of
2ms.
It can be set as
"Y" only when Tx
type of affiliated
sector is MIMO.
General value: 0.
It sets whether the E-
VAM function is
enabled when the VAM
function is supported. If
E-VAM is disabled, the
common VAM function
is used.
General value: 0.
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 446
ZTE
enableEnergySaving enableDynCode
refOperator_operatorNa
me
adminState
Enable Electric-
saving Mode or not
Enable Dynamic
Code or not
Quoted Operator Manual Operation Field
1: Y,
0: N
<default:0>
0:Close dynamic
code,
1:Open up dynamic
code
<default:0>
string:[0..127]
0:No Manual Operation,
1:Block,
2:Disabled,
4:Powered-down,
65536:Block Smoothly
<default:0>
It sets whether the
power-saving mode is
used in the local cell.
If the power-saving
mode is used and the
base station is also
configured with the
power-saving mode,
the local cell will be
blocked to save
power when the
external power supply
is faulty.
Configure whether
the dynamic code
resource function is
enabled in local cell.
If enabled, code
resource are
allocated dynamically
to improve service
performance .
This field can not be
configured. Do not
modify it.
R-W-I R-W-I R-W-I R-W
<> 529 , 447
ZTE
ModInd OMCSUBNETID SDRMEID localCellId reserveParamter1
Modify
Indication
Subnet ID ManagedElement ID Local Cell ID Reserve parameter 1
A,P long:[0..4095] long:[0..65535]
{ULocalCell_localCell
Id}
long:[0..268435455]
long
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Configure as local
cell ID of Usector.
Return To
Index
Primary Key Primary Key Primary Key R-W
<> 529 , 448
ZTE
reserveParamter2 reserveParamter3 reserveParamter4 reserveParamter5
Reserve parameter 2 Reserve parameter 3 Reserve parameter 4 Reserve parameter 5
long long long long
R-W R-W R-W R-W
<> 529 , 449
ZTE
reserveParamter6 reserveParamter7 reserveParamter8 reserveParamter9
Reserve parameter 6 Reserve parameter 7 Reserve parameter 8 Reserve parameter 9
long long long long
R-W R-W R-W R-W
<> 529 , 450
ZTE
reserveParamter10 reserveParamter11 reserveParamter12 reserveParamter13
Reserve parameter
10
Reserve parameter
11
Reserve parameter
12
Reserve parameter
13
long long long long
R-W R-W R-W R-W
<> 529 , 451
ZTE
reserveParamter14 reserveParamter15 reserveParamter16 reserveParamter17
Reserve parameter
14
Reserve parameter
15
Reserve parameter
16
Reserve parameter
17
long long long long
R-W R-W R-W R-W
<> 529 , 452
ZTE
reserveParamter18 reserveParamter19 reserveParamter20 reserveParamter21
Reserve parameter
18
Reserve parameter
19
Reserve parameter
20
Reserve parameter
21
long long long long
R-W R-W R-W R-W
<> 529 , 453
ZTE
reserveParamter22 reserveParamter23 reserveParamter24 reserveParamter25
Reserve parameter
22
Reserve parameter
23
Reserve parameter
24
Reserve parameter
25
long long long long
R-W R-W R-W R-W
<> 529 , 454
ZTE
reserveParamter26 reserveParamter27 reserveParamter28 reserveParamter29
Reserve parameter
26
Reserve parameter
27
Reserve parameter
28
Reserve parameter
29
long long long long
R-W R-W R-W R-W
<> 529 , 455
ZTE
reserveParamter30
Reserve parameter
30
long
R-W
<> 529 , 456
ZTE
ModInd OMCSUBNETID SDRMEID ULocalCellRelationId
Modify
Indication
Subnet ID ManagedElement ID RDN
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key
<> 529 , 457
ZTE
ref1ULocalCell_localCellId ref2ULocalCell_localCellId
Primary Cell Secondary Cell
long:[0..268435455] long:[0..268435455]
Primary cell of DC-HSDPA. It
must be in the same sector
with the corresponding
secondary cell.
Secondary cell of DC-
HSDPA. It must be in the
same sector with the
corresponding primary cell.
R-I R-I
<> 529 , 458
ZTE
ModInd OMCSUBNETID SDRMEID siteId isSupportLinkBackup
Modify
Indication
Subnet ID ManagedElement ID GSM Station ID
Is super Base Station
or not
A,P long:[0..4095] long:[0..65535]
long: [1..65534]
<default:1>
1:Y,
0:N
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
GSM site ID. You
can set it within the
value range. It is
an interconnection
parameter.
It decides whether the
Abis link backup
function is enabled. It
is related to the super
base station.
Return To
Index
Primary Key Primary Key R-W-I R-W-I
117 35 35 0
<> 529 , 459
ZTE
isEnableEUIPBackup bscMode backupLinkSwitch
Use EUIP backup or
not
Type of Master/Slave
BSC of Super Base
Station
Backup Link Switch
1:Y,
0:N
<default:0>
0:Single BSC,
1:Pair of BSC
<default:1>
0:Close,
1:Open
<default:0>
It decides whether the
EUIP backup is
enabled.
It decides whether the
active link and the standby
link are connected with the
same BSC when the Abis
link backup function is
enabled. "Single BSC"
means the active link and
the standby link are
connected with different
BSCs. "BSC Pair" means
the active link and the
standby link are connected
with the same BSC.
It is used to set the default status of the
standby link. If the standby link is
"Close", the standby link does not
transceive any data when the active
link is working. If the standby link is
"Open", this parameter is valid when
heartbeat data is detected on the link
and the super base station function is
enabled. If the standby link charging is
based on the flow, it is recommended
to set this parameter to "Close". No
matter what value this parameter is set,
the base station automatically sets the
R-W-I R-W-I R-W-I
0 1 0
<> 529 , 460
ZTE
switchMode autoSwitchTimer switchBackMode
Switch Mode
(Master -> Slave)
Auto Switch Timer Switch Back Mode (Slave -> Master)
0:Auto,
1:Manual
<default:0>
long: [1..5]
<default:5>
0:Auto,
1:Manual
<default:1>
It sets whether to
enable the manual
active/standby link
changeover function.
If it is set to "Auto",
the active/standby
link changeover
cannot be initiated
automatically from
the NMS.
Unit: minute
It is the timer of waiting
for automatic
changeover. It is valid
only when the working
link of the base station is
faulty. If the working link
is faulty, the base station
waits for the interval of
the timer, and
automatically performs
the
changeover/changeback.
It sets whether to perform automatic changeback or
manual changeback to change from the standby
link to the active link. It is valid when the super base
station function is enabled. When the base station
is working on the standby link, if the active link is
normal, the link changeback falls into the following
three cases:
1. If the standby link is faulty, the system
automatically performs changeback to the active
link after the autoSwitchTimer timer expires.
2. If the standby link is normal and this parameter is
set to "Auto", the system automatically performs
changeback to the active link after the
R-W-I R-W-I R-W-I
0 5 1
<> 529 , 461
ZTE
autoSwitchBackTimer adminState
Auto Switch Back
Timer
Manual Operation Field
long: [5..10]
<default:10>
0:No Manual Operation,
1:Block,
2:Disabled,
4:Powered-down,
65536:Block Smoothly
<default:0>
Unit: minute
It sets the automatic
changeback timer. It
is valid when the
super base station
function is enabled.
This field can not be
configured. Do not modify
it.
R-W-I R-W
10 0
<> 529 , 462
ZTE
ModInd OMCSUBNETID SDRMEID AbisLinkId bscId
Modify
Indication
Subnet ID ManagedElement ID RDN BSC ID
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
long:[0..2147483647]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
ID of the opposite-
end BSC connected
with the Abis link. It
identifies with which
BSC AbisLink is
connected.
Return To
Index
Primary Key Primary Key Primary Key R-W
117 35 1
<> 529 , 463
ZTE
abisLinkClass
Class of Abis Link
0:Master,
1:Slave
<default:0>
It set whether a link is
active or standy when
the Abis link backup
function is enabled.
R-I
0
<> 529 , 464
ZTE
ModInd OMCSUBNETID SDRMEID abisLinkClass
Modify
Indication
Subnet ID ManagedElement ID Class of Abis Link
A,P long:[0..4095] long:[0..65535]
{AbisLink_abisLinkClass
}
long:[0..1]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Configure as
abisLinkClass of
AbisLink.
Return To
Index
Primary Key Primary Key Primary Key
117 35 0
<> 529 , 465
ZTE
BtsMId refSctp_sctpNo
refOperator_operatorName
#1
refOperator_operatorName#
2
RDN Used SCTP Operator 1 Operator 2
long:[1..4294967295] long:[0..3] string:[0..127] string:[0..127]
Generated
automatically, it is
unnecessary to fill in
this column.
Primary Key R-I R-I R-I
1 0 NA
<> 529 , 466
ZTE
refOperator_operatorName
#3
Operator 3
string:[0..127]
R-I
<> 529 , 467
ZTE
ModInd OMCSUBNETID SDRMEID HubBtsConfigId hubBtsConfigNo
Modify
Indication
Subnet ID ManagedElement ID RDN Local Switch No.
A,P long:[0..4095] long:[0..65535]
long:[1..429496729
5]
long:[0..15]
<default:0>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill
in this column.
Return To
Index
Primary Key Primary Key Primary Key R-I
<> 529 , 468
ZTE
direction
refPppLink_PppLink
No
destinationIp#1 destinationIp#2
Direction Used PPP
Destination IP
Address 1
Destination IP
Address 2
0:UPLINK,
1:DOWNLINK
<default:0>
long:[0..7]
ipv4
<default:0.0.0.0>
ipv4
It sets whether the packet
forwarded by the base station
is uplink (can reach BSC
according to the topology) or
(cannot reach BSC according
to the topology) downlink. This
parameter is related to the
network topology.
Destination IP
address of the
packet forwarded by
the base station.
R-W-I R-I R-W-I R-W-I
<> 529 , 469
ZTE
destinationIp#3 destinationIp#4 destinationIp#5 destinationIp#6 destinationIp#7
Destination IP
Address 3
Destination IP
Address 4
Destination IP
Address 5
Destination IP
Address 6
Destination IP
Address 7
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 470
ZTE
destinationIp#8 destinationIp#9 destinationIp#10 destinationIp#11 destinationIp#12
Destination IP
Address 8
Destination IP
Address 9
Destination IP
Address 10
Destination IP
Address 11
Destination IP
Address 12
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 471
ZTE
destinationIp#13 destinationIp#14 destinationIp#15 destinationIp#16 destinationIp#17
Destination IP
Address 13
Destination IP
Address 14
Destination IP
Address 15
Destination IP
Address 16
Destination IP
Address 17
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 472
ZTE
destinationIp#18 destinationIp#19 destinationIp#20 destinationIp#21 destinationIp#22
Destination IP
Address 18
Destination IP
Address 19
Destination IP
Address 20
Destination IP
Address 21
Destination IP
Address 22
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 473
ZTE
destinationIp#23 destinationIp#24 destinationIp#25 destinationIp#26 destinationIp#27
Destination IP
Address 23
Destination IP
Address 24
Destination IP
Address 25
Destination IP
Address 26
Destination IP
Address 27
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 474
ZTE
destinationIp#28 destinationIp#29 destinationIp#30 destinationIp#31 destinationIp#32
Destination IP
Address 28
Destination IP
Address 29
Destination IP
Address 30
Destination IP
Address 31
Destination IP
Address 32
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 475
ZTE
destinationIp#33 destinationIp#34 destinationIp#35 destinationIp#36 destinationIp#37
Destination IP
Address 33
Destination IP
Address 34
Destination IP
Address 35
Destination IP
Address 36
Destination IP
Address 37
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 476
ZTE
destinationIp#38 destinationIp#39 destinationIp#40 destinationIp#41 destinationIp#42
Destination IP
Address 38
Destination IP
Address 39
Destination IP
Address 40
Destination IP
Address 41
Destination IP
Address 42
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 477
ZTE
destinationIp#43 destinationIp#44 destinationIp#45 destinationIp#46 destinationIp#47
Destination IP
Address 43
Destination IP
Address 44
Destination IP
Address 45
Destination IP
Address 46
Destination IP
Address 47
ipv4 ipv4 ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I R-W-I R-W-I
<> 529 , 478
ZTE
destinationIp#48 destinationIp#49 destinationIp#50
Destination IP
Address 48
Destination IP
Address 49
Destination IP
Address 50
ipv4 ipv4 ipv4
R-W-I R-W-I R-W-I
<> 529 , 479
ZTE
ModInd OMCSUBNETID SDRMEID
GCellEquipmentFunction
Id
Modify
Indication
Subnet ID ManagedElement ID RDN
A,P long:[0..4095] long:[0..65535] long:[1..4294967295]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated automatically,
it is unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key
117 35 1
117 35 2
117 35 5
117 35 6
117 35 7
117 35 8
<> 529 , 480
ZTE
gCellEquipmentFuncN
o
refTxDevice_rack
No
refTxDevice_po
rt
powerLevel
GSM Cell Channel
Resource No.
Connected Tx RU
Rack No.
Connected Tx
Port
Static Power
Attenuation Level of
Carrier
long:[1..216]
<default:1>
long:[1..201] long:[1..5]
0: 0db,
1: 2db,
2: 4db,
3: 6db,
4: 8db,
5: 10db,
6: 12db,
7: 14db,
8: 16db,
9: 18db,
10: 20db,
Channel resource
number. You can set it
within the value range.
It must be unique.
R-I R-I R-I R-W-I
1 2 2 249
2 2 1 249
5 4 2 249
6 4 1 249
9 6 2 249
10 6 1 249
<> 529 , 481
ZTE
channelGroupNo rxMode txMode
GSM Cell Channel Group
No.
Rx Mode Tx Mode
long:[0..216]
<default:0>
0:2-antenna diversity
reception,
1:4-antenna diversity
reception
<default:0>
0:Normal mode,
1:DPCT,
2:DDT,
3:Antenna hopping
<default:0>
GSM Cell Channel Group No.
0 indicates no grouping.
When Multi-carrier
combination group is greater
than zero,GSM Cell Channel
Group No must be greater
than zero.Only one physical
This parameter in a same
RRU should be consistent.
Receiving mode of the RF
unit.
"2-antenna diversity
reception" indicates that
two receiving channels
This parameter in a same
RRU should be consistent.
Transmission mode of the
RF unit.
"Normal mode" indicates that
one transmitting channel and
two receiving channels form
R-I R-W-I R-W-I
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
<> 529 , 482
ZTE
ddtOffset multiCarrierGroupNo rxConfig
DDT Delay
Multi-carrier
Combination Group
No.
Primary-secondary
Antenna Receiving
Setting
long: [0..8]
<default:0>
long:[0..32]
<default:0>
0:Primary and secondary
antenna receiving,
1:Primary antenna
receiving. secondary
antenna not receiving,
2:Secondary antenna
receiving. primary antenna
not receiving
<default:0>
This parameter in a
same RRU should be
consistent.
DDT delay, that is, the
delay between
transmitting the same
signal on two
Multi-carrier
combination group
number. 0 indicates no
grouping. Multi-carrier
combination means
that the carriers, which
physically belong to
R-W-I R-I R-W-I
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
<> 529 , 483
ZTE
gsmCarrierConfig_gsmCarrier#1 gsmCarrierConfig_carrierPw#1 gsmCarrierConfig_IntlgtOff#1
GSM Carrier No. 1 Carrier Power 1
Support Intelligent Shutoff or not
1
{gsmCarrierConfig_gsmCarrierN
o#1}
long:[1..1]
<default:1>
{gsmCarrierConfig_carrierPower
#1}
long:[0..140]
<default:0>
{gsmCarrierConfig_enableIntelligent
Off#1}
1:Y,
0:N
Set the carrier power. The sum
of all the carrier power on a RU
RF device should be smaller
than the rated power. Unit: W.
The set is valid for RU02 and
RU02E boards. General value: 0.
R-W R-W R-W
1 20 0
1 20 0
1 20 0
1 20 0
1 20 0
1 20 0
<> 529 , 484
ZTE
gsmCarrierConfig_TimeSlotOff#1 gsmCarrierConfig_gsmCarrier#2 gsmCarrierConfig_carrierPw#2
Support Time Slot Shutoff or not 1 GSM Carrier No. 2 Carrier Power 2
{gsmCarrierConfig_enableTimeSlot
Off#1}
1:Y,
0:N
{gsmCarrierConfig_gsmCarrierN
o#2}
long:[2..2]
<default:2>
{gsmCarrierConfig_carrierPower
#2}
long:[0..140]
<default:0>
The set is valid for RU02 and
RU02E boards. General value: 0.
Set the carrier power. The sum
of all the carrier power on a RU
RF device should be smaller
than the rated power. Unit: W.
R-W R-W R-W
0
0
0
0
0
0
<> 529 , 485
ZTE
gsmCarrierConfig_IntlgtOff#2 gsmCarrierConfig_TimeSlotOff#2
Support Intelligent Shutoff or not 2 Support Time Slot Shutoff or not 2
{gsmCarrierConfig_enableIntelligentOff#
2}
1:Y,
0:N
{gsmCarrierConfig_enableTimeSlotOf
f#2}
1:Y,
0:N
The set is valid for RU02 and RU02E
boards. General value: 0.
The set is valid for RU02 and RU02E
boards. General value: 0.
R-W R-W
<> 529 , 486
ZTE
gsmCarrierConfig_gsmCarrier#3 gsmCarrierConfig_carrierPw#3 gsmCarrierConfig_gsmCarrier#4
GSM Carrier No. 3 Carrier Power 3 GSM Carrier No. 4
{gsmCarrierConfig_gsmCarrierN
o#3}
long:[3..3]
<default:3>
{gsmCarrierConfig_carrierPower
#3}
long:[0..140]
<default:0>
{gsmCarrierConfig_gsmCarrierN
o#4}
long:[4..4]
<default:4>
Set the carrier power. The sum
of all the carrier power on a RU
RF device should be smaller
than the rated power. Unit: W.
R-W R-W R-W
<> 529 , 487
ZTE
gsmCarrierConfig_carrierPw#4 gsmCarrierConfig_gsmCarrier#5 gsmCarrierConfig_carrierPw#5
Carrier Power 4 GSM Carrier No. 5 Carrier Power 5
{gsmCarrierConfig_carrierPower
#4}
long:[0..140]
<default:0>
{gsmCarrierConfig_gsmCarrierN
o#5}
long:[5..5]
<default:5>
{gsmCarrierConfig_carrierPower
#5}
long:[0..140]
<default:0>
Set the carrier power. The sum
of all the carrier power on a RU
RF device should be smaller
than the rated power. Unit: W.
Set the carrier power. The sum
of all the carrier power on a RU
RF device should be smaller
than the rated power. Unit: W.
R-W R-W R-W
<> 529 , 488
ZTE
gsmCarrierConfig_gsmCarrier#6 gsmCarrierConfig_carrierPw#6
GSM Carrier No. 6 Carrier Power 6
{gsmCarrierConfig_gsmCarrierN
o#6}
long:[6..6]
<default:6>
{gsmCarrierConfig_carrierPower
#6}
long:[0..140]
<default:0>
Set the carrier power. The sum
of all the carrier power on a RU
RF device should be smaller
than the rated power. Unit: W.
R-W R-W
<> 529 , 489
ZTE
ModInd OMCSUBNETID SDRMEID GCellId cellNo
Modify
Indication
Subnet ID ManagedElement ID RDN Cell No.
A,P long:[0..4095] long:[0..65535]
long:[1..4294967295
]
long:[1..54]
<default:1>
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Generated
automatically, it is
unnecessary to fill in
this column.
It represents the
GSM cell ID. You
can set it within
the value range.
A GSM cell ID
must be unique. It
Return To
Index
Primary Key Primary Key Primary Key R-I
117 35 1 1
117 35 2 2
117 35 3 3
<> 529 , 490
ZTE
gpsOffset
refGCellEquipmentFunctionNo#
1
carrierNum#1 hsrCellOutInletFlag#1
GPS Synchronized
Frame Head Offset
Used GSM Cell Channel
Resource 1
Used Carrier
Number 1
End ID 1 of High-
speed Railway Cell
long:[0..50]
<default:0>
{refGCellEquipmentFunction_g
CellEquipmentFuncNo#1}
long:[1..216]
long:[1..6]
1:Y,
0:N
<default:0>
GPS synchronization
frame number offset.
You can set it within
the value range. In a
synchronization area, it
is recommended to set
Channel resource used in the
cell. A cell can use multiple
channel resources. You can
configure carrierNum to set the
nubmer of carriers used in the
channel resource.
It represents the
number of carriers
used for the cell on
each channel. It
should correspond
to the configuration
It is applied in the
scenario of high
speed railways
configured with mutli-
carrier combination
group. It is used to
R-W-I R-W-I R-W-I R-W-I
1 2 1 0
1 6 1 0
1 10 1 0
<> 529 , 491
ZTE
refGCellEquipmentFunctionNo#2 carrierNum#2
hsrCellOutInletFlag#
2
refGCellEquipmentFunctionN
o#3
Used GSM Cell Channel
Resource 2
Used Carrier
Number 2
End ID 2 of High-
speed Railway Cell
Used GSM Cell Channel
Resource 3
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#2}
long:[1..216]
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_
gCellEquipmentFuncNo#3}
long:[1..216]
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
It represents
the number of
carriers used
for the cell on
each channel.
It should
It is applied in the
scenario of high
speed railways
configured with mutli-
carrier combination
group. It is used to
Channel resource used in the
cell. A cell can use multiple
channel resources. You can
configure carrierNum to set
the nubmer of carriers used in
the channel resource.
R-W-I R-W-I R-W-I R-W-I
1 1
5 1
9 1
<> 529 , 492
ZTE
carrierNum#3
hsrCellOutInletFlag#
3
refGCellEquipmentFunctionNo
#4
carrierNum#4
Used Carrier
Number 3
End ID 3 of High-
speed Railway Cell
Used GSM Cell Channel
Resource 4
Used Carrier
Number 4
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_g
CellEquipmentFuncNo#4}
long:[1..216]
long:[1..6]
It represents the
number of
carriers used for
the cell on each
channel. It should
correspond to the
It is applied in the
scenario of high
speed railways
configured with mutli-
carrier combination
group. It is used to
Channel resource used in the
cell. A cell can use multiple
channel resources. You can
configure carrierNum to set the
nubmer of carriers used in the
channel resource.
It represents the
number of
carriers used for
the cell on each
channel. It
should
R-W-I R-W-I R-W-I R-W-I
<> 529 , 493
ZTE
hsrCellOutInletFlag#4
refGCellEquipmentFunctionNo
#5
carrierNum#5 hsrCellOutInletFlag#5
End ID 4 of High-
speed Railway Cell
Used GSM Cell Channel
Resource 5
Used Carrier
Number 5
End ID 5 of High-
speed Railway Cell
1:Y,
0:N
{refGCellEquipmentFunction_g
CellEquipmentFuncNo#5}
long:[1..216]
long:[1..6]
1:Y,
0:N
It is applied in the
scenario of high speed
railways configured
with mutli-carrier
combination group. It
is used to identify
Channel resource used in the
cell. A cell can use multiple
channel resources. You can
configure carrierNum to set the
nubmer of carriers used in the
channel resource.
It represents the
number of
carriers used for
the cell on each
channel. It
should
It is applied in the
scenario of high speed
railways configured
with mutli-carrier
combination group. It is
used to identify whether
R-W-I R-W-I R-W-I R-W-I
<> 529 , 494
ZTE
refGCellEquipmentFunctionNo#
6
carrierNum#6 hsrCellOutInletFlag#6
refGCellEquipmentFunctionN
o#7
Used GSM Cell Channel
Resource 6
Used Carrier
Number 6
End ID 6 of High-
speed Railway Cell
Used GSM Cell Channel
Resource 7
{refGCellEquipmentFunction_gC
ellEquipmentFuncNo#6}
long:[1..216]
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_
gCellEquipmentFuncNo#7}
long:[1..216]
Channel resource used in the
cell. A cell can use multiple
channel resources. You can
configure carrierNum to set the
nubmer of carriers used in the
channel resource.
It represents the
number of carriers
used for the cell
on each channel.
It should
correspond to the
It is applied in the
scenario of high
speed railways
configured with mutli-
carrier combination
group. It is used to
Channel resource used in the
cell. A cell can use multiple
channel resources. You can
configure carrierNum to set
the nubmer of carriers used in
the channel resource.
R-W-I R-W-I R-W-I R-W-I
<> 529 , 495
ZTE
carrierNum#7 hsrCellOutInletFlag#7 refGCellEquipmentFunctionNo#8
Used Carrier
Number 7
End ID 7 of High-speed Railway
Cell
Used GSM Cell Channel
Resource 8
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#8}
long:[1..216]
It represents the
number of carriers
used for the cell on
each channel. It
should correspond
to the configuration
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 496
ZTE
carrierNum#8 hsrCellOutInletFlag#8 refGCellEquipmentFunctionNo#9
Used Carrier Number 8
End ID 8 of High-speed Railway
Cell
Used GSM Cell Channel
Resource 9
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#9}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 497
ZTE
carrierNum#9 hsrCellOutInletFlag#9 refGCellEquipmentFunctionNo#10
Used Carrier Number 9
End ID 9 of High-speed Railway
Cell
Used GSM Cell Channel
Resource 10
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#10}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 498
ZTE
carrierNum#10 hsrCellOutInletFlag#10 refGCellEquipmentFunctionNo#11
Used Carrier Number 10
End ID 10 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 11
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#11}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 499
ZTE
carrierNum#11 hsrCellOutInletFlag#11 refGCellEquipmentFunctionNo#12
Used Carrier Number 11
End ID 11 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 12
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#12}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 500
ZTE
carrierNum#12 hsrCellOutInletFlag#12 refGCellEquipmentFunctionNo#13
Used Carrier Number 12
End ID 12 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 13
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#13}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 501
ZTE
carrierNum#13 hsrCellOutInletFlag#13 refGCellEquipmentFunctionNo#14
Used Carrier Number 13
End ID 13 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 14
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#14}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 502
ZTE
carrierNum#14 hsrCellOutInletFlag#14 refGCellEquipmentFunctionNo#15
Used Carrier Number 14
End ID 14 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 15
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#15}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 503
ZTE
carrierNum#15 hsrCellOutInletFlag#15 refGCellEquipmentFunctionNo#16
Used Carrier Number 15
End ID 15 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 16
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#16}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 504
ZTE
carrierNum#16 hsrCellOutInletFlag#16 refGCellEquipmentFunctionNo#17
Used Carrier Number 16
End ID 16 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 17
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#17}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 505
ZTE
carrierNum#17 hsrCellOutInletFlag#17 refGCellEquipmentFunctionNo#18
Used Carrier Number 17
End ID 17 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 18
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#18}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 506
ZTE
carrierNum#18 hsrCellOutInletFlag#18 refGCellEquipmentFunctionNo#19
Used Carrier Number 18
End ID 18 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 19
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#19}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 507
ZTE
carrierNum#19 hsrCellOutInletFlag#19 refGCellEquipmentFunctionNo#20
Used Carrier Number 19
End ID 19 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 20
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#20}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 508
ZTE
carrierNum#20 hsrCellOutInletFlag#20 refGCellEquipmentFunctionNo#21
Used Carrier Number 20
End ID 20 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 21
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#21}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 509
ZTE
carrierNum#21 hsrCellOutInletFlag#21 refGCellEquipmentFunctionNo#22
Used Carrier Number 21
End ID 21 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 22
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#22}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 510
ZTE
carrierNum#22 hsrCellOutInletFlag#22 refGCellEquipmentFunctionNo#23
Used Carrier Number 22
End ID 22 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 23
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#23}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 511
ZTE
carrierNum#23 hsrCellOutInletFlag#23 refGCellEquipmentFunctionNo#24
Used Carrier Number 23
End ID 23 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 24
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#24}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 512
ZTE
carrierNum#24 hsrCellOutInletFlag#24 refGCellEquipmentFunctionNo#25
Used Carrier Number 24
End ID 24 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 25
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#25}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 513
ZTE
carrierNum#25 hsrCellOutInletFlag#25 refGCellEquipmentFunctionNo#26
Used Carrier Number 25
End ID 25 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 26
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#26}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 514
ZTE
carrierNum#26 hsrCellOutInletFlag#26 refGCellEquipmentFunctionNo#27
Used Carrier Number 26
End ID 26 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 27
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#27}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 515
ZTE
carrierNum#27 hsrCellOutInletFlag#27 refGCellEquipmentFunctionNo#28
Used Carrier Number 27
End ID 27 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 28
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#28}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 516
ZTE
carrierNum#28 hsrCellOutInletFlag#28 refGCellEquipmentFunctionNo#29
Used Carrier Number 28
End ID 28 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 29
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#29}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 517
ZTE
carrierNum#29 hsrCellOutInletFlag#29 refGCellEquipmentFunctionNo#30
Used Carrier Number 29
End ID 29 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 30
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#30}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 518
ZTE
carrierNum#30 hsrCellOutInletFlag#30 refGCellEquipmentFunctionNo#31
Used Carrier Number 30
End ID 30 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 31
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#31}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 519
ZTE
carrierNum#31 hsrCellOutInletFlag#31 refGCellEquipmentFunctionNo#32
Used Carrier Number 31
End ID 31 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 32
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#32}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 520
ZTE
carrierNum#32 hsrCellOutInletFlag#32 refGCellEquipmentFunctionNo#33
Used Carrier Number 32
End ID 32 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 33
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#33}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 521
ZTE
carrierNum#33 hsrCellOutInletFlag#33 refGCellEquipmentFunctionNo#34
Used Carrier Number 33
End ID 33 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 34
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#34}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 522
ZTE
carrierNum#34 hsrCellOutInletFlag#34 refGCellEquipmentFunctionNo#35
Used Carrier Number 34
End ID 34 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 35
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#35}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 523
ZTE
carrierNum#35 hsrCellOutInletFlag#35 refGCellEquipmentFunctionNo#36
Used Carrier Number 35
End ID 35 of High-speed
Railway Cell
Used GSM Cell Channel
Resource 36
long:[1..6]
1:Y,
0:N
{refGCellEquipmentFunction_gCel
lEquipmentFuncNo#36}
long:[1..216]
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
Channel resource used in the cell.
A cell can use multiple channel
resources. You can configure
carrierNum to set the nubmer of
carriers used in the channel
resource.
R-W-I R-W-I R-W-I
<> 529 , 524
ZTE
carrierNum#36 hsrCellOutInletFlag#36 gCellEquipmentFuncNo
Used Carrier Number 36
End ID 36 of High-speed
Railway Cell
BCCH Preferred Channel No.
long:[1..6]
1:Y,
0:N
long:[0..216]
<default:0>
It represents the number of
carriers used for the cell on each
channel. It should correspond to
the configuration sequence of
refGCellEquipmentFunction.
It is applied in the scenario of high
speed railways configured with
mutli-carrier combination group. It
is used to identify whether a
channel is the inlet/outlet endpoint
of the mutli-carrier combination.
BCCH preferred channel number.
It is set in
refGCellEquipmentFunction. 0
indicates invalid, that is, the base
station does not specify BCCH
preferred channel and randomly
R-W-I R-W-I R-W-I
0
0
0
<> 529 , 525
ZTE
bcchCarrierNo
BCCH Preferred Carrier No.
long: [0..6]
<default:0>
BCCH preferred carrier number. 0
indicates invalid, that is, the base
station does not specify BCCH
preferred carrier and randomly
allocates BCCH to a carrier. If
gCellEquipmentFuncNo is set to
R-W-I
0
0
0
<> 529 , 526
ModInd OMCSUBNETID SDRMEID cellNo GTrxId
Modify
Indication
Subnet ID ManagedElement ID
Affiliated GSM
Cell No.
RDN
A,P long:[0..4095] long:[0..65535]
{GCell_cellNo}
long:[1..54]
long:[1..4294967295]
A:Add, P:Pass Same in an OMMB. Unique in subnetwork.
Configure as
GSM cell No.
"cellNo" of Gcell.
Generated
automatically, it is
unnecessary to fill in
this column.
Return To
Index
Primary Key Primary Key Primary Key Primary Key
117 35 1 1
117 35 1 2
117 35 2 1
117 35 2 2
117 35 3 1
117 35 3 2
trxNo operatingMode multiCarrierGroupNo enableIRC mainBand
Logic Carrier
Frequency No.
Operating Mode
Multi-carrier
Combination Group
Use IRC or not
Parent Frequency
Band
long:[1..60]
<default:1>
0:Single carrier,
1:Dual-carrier,
2:Multi-carrier
<default:0>
long:[0..32]
0:Disable IRC,
1:Enable IRC,
2:Enable STIRC
<default:1>
1: 2.1G(Band I),
2: 1900M(Band II),
3: 1800M(Band III),
5: 850M(Band V),
6: 850M(Band VI),
8: 900M(Band
VIII),
9: 1800M(Band IX)
<default:2>
Carrier frequency ID.
You can set it within
the value range. It is
an interconnection
parameter. Different
cells can have the
same carrier
frequency number,
but the carrier
frequency numbers
of the same cell
must differ from
GSM carrier frequency
working mode In the
case of four-antenna
receiving diversity, set
this parameter to "Dual-
carrier", and the four
antennas have the
same receiving range,
which enhances the
uplink receiving
capability. "Multi-
carrier" is applied in the
Multi-carrier
combination group used
by carrier frequency. It
is valid when
"operatingMode" is set
to "Dual-carrier" or
"Multi-carrier". 0
indicates that it is
invalid. Its value comes
from the
GCellEquipmentFunctio
n affiliated multi-carrier
It sets whether the
feature "ZGO-04-01-
005 Uplink
Interference Rejection
Combining (IRC)" is
enabled. This feature
can improve the uplink
receiving signal quality
in the GSM system. It
is recommended to
enable this feature.
R-I R-W-I R-W-I R-W-I R-W-I
1 0 0 1 3
2 0 0 1 3
1 0 0 1 3
2 0 0 1 3
1 0 0 1 3
2 0 0 1 3
branchBand isExtendTrx mcumRxSelMode mcumTxSelMode
Sub Frequency Band
Extend Carrier
Frequency or not
Is Uplink Signal Selected
According to CIR
Select RU Transmission
or not
long:[1..3,255]
<default:255>
1: Y,
0: N
<default:0>
1: Y,
0: N
<default:0>
1: Y,
0: N
<default:0>
It decides whether to
configure the current
carrier as the extended
carrier. The odd slot and
the even slot of the
extended carrier are
combined as one slot,
which increases the cell
coverage range.
It is a function switch. For
cells configured with multi-
carrier combination, if this
feature is enabled, the base
station decides from which
RU the signal is received in
uplink according to the
Carrier-to-Interference (C/I)
ratio. If this feature is
disabled, the base station
uses other methods to
decide from which RU the
It is a function switch. For
cells configured with multi-
carrier combination, if this
feature is enabled, the
base station selects a RU
to transmit the signal in
downlink. If this feature is
disabled, all RUs transmit
signal simultaneously.
Usually, it is recommended
to disable this feature. If
"ZGO-04-02-004 Uplink
R-W-I R-W-I R-W-I R-W-I
255 0 0 0
255 0 0 0
255 0 0 0
255 0 0 0
255 0 0 0
255 0 0 0

Vous aimerez peut-être aussi