Professional Documents
Culture Documents
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
2011-10-30
Contents
About This Manual ......................................................................................... I
Chapter 1 Configuration Overview ........................................................... 1-1
1.1 Overview ........................................................................................................... 1-1
1.2 Logging in Configuration Management Interface................................................... 1-1
1.3 Configuration Management Interface Description ................................................. 1-4
1.4 Data Configuration Flow ..................................................................................... 1-6
1.5 Reference Material ............................................................................................. 1-8
1.6 Data Configuration Precautions........................................................................... 1-9
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII
II
Intended Audience
l
Summary
Chapter 1, Configuration
Overview
Chapter 2, Public Resource
Configuration
Chapter 3, BSC Physical
Configuration
Chapter 4, A-Interface
Configuration
Chapter 5, Ater Interface
Configuration
Chapter 6, Gb Interface
Configuration
Appendix A, Corresponding
board.
Construction
Appendix C, Common
Configuration Operations
II
Chapter 1
Configuration Overview
Table of Contents
Overview ....................................................................................................................1-1
Logging in Configuration Management Interface.........................................................1-1
Configuration Management Interface Description .......................................................1-4
Data Configuration Flow .............................................................................................1-6
Reference Material .....................................................................................................1-8
Data Configuration Precautions ..................................................................................1-9
1.1 Overview
Configuration management enables user to manage resource data and status, and
provides various data configurations to support normal system running. It determines the
running mode and status of ZXG10 BSS.
Data configuration means establishing the relationship between the network management
system and network elements such as BSC and BTS. It enables user to perform parameter
setting for management objects in BSS.
Context
This section describes how to log in the configuration management interface.
Steps
1. In the topology tree on the left of the main interface of NetNumen M31 client, right-click
on the created GSM NE agent node, and select Start NE on the pop-up menu, as
shown in Figure 1-1.
1-1
SJ-20110909163908-011|2011-10-30 (R1.0)
1-2
SJ-20110909163908-011|2011-10-30 (R1.0)
1-3
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Configure public resources.
1-4
SJ-20110909163908-011|2011-10-30 (R1.0)
1. Configuration Management
Toolbar
2. Configuration Management
Element Toolbar
3. Configuration Management
Element Property Tab
(Taking Master Config Set
for Example)
4. Configuration Resource
Tree
Description
Lock Screen
Logout
Refresh
Forward
Backward
Help
Description
Modify
Cancel
Save
Close
1-5
SJ-20110909163908-011|2011-10-30 (R1.0)
Toolbar Button
Description
CloseAll
Help
Switch to master configuration set
1. The toolbar for configuration management element might differ according to specific configurat
ion management elements. User can place the mouse on a button to view its tip. In this table,
the master configuration set is taken as the configuration management element.
1-6
SJ-20110909163908-011|2011-10-30 (R1.0)
1-7
SJ-20110909163908-011|2011-10-30 (R1.0)
Caution!
For each type of configuration mentioned above, it is recommended to perform data
synchronization after the configuration is completed. In other words, perform all data
synchronization or modified data synchronization to synchronize the configured data with
that at BSC to make it validate; otherwise, the configured data is only virtual data in the
network management system.
1-8
SJ-20110909163908-011|2011-10-30 (R1.0)
Caution!
Because a large amount of parameters are involved in data configuration, this manual
only introduces some important parameters and parameters that must be modified.
Such parameters should be configured according to the configuration specification. For
parameters not introduced, the default setting is adopted.
1-9
SJ-20110909163908-011|2011-10-30 (R1.0)
1-10
SJ-20110909163908-011|2011-10-30 (R1.0)
Chapter 2
Public Resource
Configuration
Table of Contents
Overview ....................................................................................................................2-1
Configuring GERAN Subnetwork................................................................................2-1
Configuring BSC Managed Element ...........................................................................2-3
Configuring Config Set ...............................................................................................2-5
Configuring BSC Function ..........................................................................................2-7
2.1 Overview
Public resource configuration includes configuring GERAN subnetwork, BSC management
element, config set, and BSC function.
Context
A GERAN subnetwork contains one management element, and the subnetwork's ID is
same as that of the management element.
This section introduces how to configure the GERAN subnetwork.
Steps
1. In the configuration resource tree, right-click on OMC and select Create > GERAN
Subnetwork, as shown in Figure 2-1.
2-1
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click GERAN subnetwork, and the Create GERAN Subnetwork dialog box appears,
as shown in Figure 2-2. Input relevant parameter values.
3. Click OK. After the operation is completed, the newly configured GERAN subnetwork
node appears on the configuration resource tree, as shown in Figure 2-3.
2-2
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Configure the BSC management element.
Context
The BSC managed element is sub-node of the GERAN subnetwork node. A managed
element can only be contained in one GERAN subnetwork.
This section introduces how to configure the BSC managed element.
Steps
1. In the configuration resource tree, right-click on the GERAN Subnetwork node and
select Create > BSC Managed Element, as shown in Figure 2-4.
2-3
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click BSC Managed Element, and the Create BSC managed element dialog box
appears, as shown in Figure 2-5.
Figure 2-5 Configuring BSC Managed Element (2)
Caution!
When configuring Managed element IP address, make sure that the setting is
consistent with the IP address configured for the serial port of OMP of ZXG10 iBSC.
The setting must be unique for different managed elements.
2-4
SJ-20110909163908-011|2011-10-30 (R1.0)
3. Click OK. After the operation is completed, the newly configured BSC managed
element node appears on the configuration resource tree, as shown in Figure 2-6.
End of Steps
Follow-Up Action
Configure the config set.
Context
The system provides multiple sets of configuration data for the network management
elements. User can configure multiple data configuration sets, one is the master config
set while others are slave config sets. After the configuration is completed, user can
switch between the master config set and the slave config set.
User can perform foreground-background operations for the master config set, such as
data synchronization and dynamic operation.
The master config set can not be created or deleted individually. It is created automatically
when the management element is configured, and is deleted simultaneously when the
subnetwork node or the management element node is deleted. There can only be one
master config set under a management element.
2-5
SJ-20110909163908-011|2011-10-30 (R1.0)
Steps
1. In the configuration resource tree, right-click on the BSC Managed Element node and
select Create > Config Set, as shown in Figure 2-7.
Figure 2-7 Configuring Config Set (1)
2. Click Config Set, and the Create Config Set dialog box appears, as shown in Figure
2-8. Input relevant parameter values.
Figure 2-8 Configuring Config Set (2)
3. Click OK. After the operation is completed, the newly configured config set node
appears on the configuration resource tree, as shown in Figure 2-9.
2-6
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Configure the BSC function.
Context
The BSC function is sub-node of the config set node. All global resource managed objects
are located under the BSC function node.
This section introduces how to configure the BSC function.
Steps
1. In the configuration resource tree, right-click on the Config Set node and select Create
> BSC Function, as shown in Figure 2-10.
2-7
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click BSC Function, and the Create BSC Function dialog box appears. User can
click the
icon to display all sub-tabs, as shown in Figure 2-11. Input relevant
parameter values.
MCC(MCC)
2-8
SJ-20110909163908-011|2011-10-30 (R1.0)
Configure this parameter according to actual situation. It can not be modified after
being configured.
l
MNC(MNC)
Configure this parameter according to actual situation. It can not be modified after
being configured.
OMP IP(OMP_IP)
This parameter must be consistent with Managed element IP address in
Configuring BSC Managed Element.
OMP MAC(OMP_MAC)
Configure this parameter according to actual situation.
OMCB IP(OMCB)
If the dual-mode site BS8200 is configured, then the IP address of OMCB must
be configured.
SNTP server IP
This parameters value is the same as OMP IP(OMP_IP).
Net type(Net)
Configure this parameter according to actual situation.
SP type(SPType)
Configure this parameter according to actual situation.
Bureau No.(BureauNo)
Configure this parameter according to actual situation. It can not be repeated
under the same server, and can not be modified after being configured.
Support GE(GESupport)
Configure this parameter according to actual situation. If it is set to "Yes", then
only the gigabit resource shelf can be configured in the BSC rack as resource
shelf; otherwise, only the megabit resource shelf can be configured in the BSC
rack as resource shelf. The gigabit resource shelf and the megabit resource shelf
can not be configured together in the BSC rack.
Support TC type(TCType)
2-9
SJ-20110909163908-011|2011-10-30 (R1.0)
Configure this parameter according to actual situation. It can not be modified after
being configured.
Radio Basic Property tab:
DCS1800/PCS1900 supported(FuncExt)
Configure this parameter according to actual situation. It can not be modified after
being configured.
3. Click OK. After the operation is completed, the newly configured BSC function node
appears on the configuration resource tree, as shown in Figure 2-12.
End of Steps
Follow-Up Action
Configure BSC physical equipments.
2-10
SJ-20110909163908-011|2011-10-30 (R1.0)
Chapter 3
3.1 Overview
BSC physical equipment configuration includes configuring BSC rack, shelf, and board.
Context
Configure a new BSC rack manually, and configure data related to the rack.
Steps
1. In the configuration resource tree, right-click on the BSC Device Config node and
select Create > BSC Rack, as shown in Figure 3-1.
3-1
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click BSC Rack, and the Create BSC Rack dialog box appears, as shown in Figure
3-2. Select Rack No. and Rack type. At most two racks can be configured.
3. Click OK. After the operation is completed, the newly configured BSC rack node
appears on the configuration resource tree. In the manual configuration mode,
shelves and boards are not configured in the rack. Figure 3-3 shows an example of
the configured rack.
3-2
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Configure shelf and board.
Context
This section introduces how to configure control shelf, resource shelf, packet switching
shelf, and relevant boards.
3-3
SJ-20110909163908-011|2011-10-30 (R1.0)
Steps
1. In the configuration resource tree, double-click the BSC Rack node to be configured
with shelf and board.
2. Right-click on the second shelf of the rack, click Create Shelf in the pop-up menu, and
the Create Shelf dialog box appears. Select Control shelf as Shelf type, as shown
in Figure 3-4.
Figure 3-4 Configuring Shelf and Board (1)
3-4
SJ-20110909163908-011|2011-10-30 (R1.0)
3-5
SJ-20110909163908-011|2011-10-30 (R1.0)
l
l
Note:
In control shelf, the OMP board must be configured first, then the UIMC board,
and then other boards.
The SBCX board 1 need not be configured.
5. Repeat step 1 ~ step 4 to configure resource shelf (or gigabit resource shelf), packet
switching shelf, and relevant boards. Figure 3-7 shows the configuration result.
Figure 3-7 Configuring Shelf and Board (4)
Note:
In resource shelf/gigabit resource shelf, the UIMU/GUIM board must be configured
first.
End of Steps
Follow-Up Action
Configure A-interface data.
3-7
SJ-20110909163908-011|2011-10-30 (R1.0)
3-8
SJ-20110909163908-011|2011-10-30 (R1.0)
Chapter 4
A-interface Configuration
Table of Contents
Overview ....................................................................................................................4-1
E1 A-interface Configuration.......................................................................................4-1
4.1 Overview
A-interface data configuration includes configuring signaling and service channels between
ZXG10 iBSC and MSC, and configuring interconnection between ZXG10 iBSC and MSC.
ZXG10 iBSC supports E1 A-interface mode.
l
l
l
Context
Through this task, user can configure a uniquely identified local office in the network.
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > A/Ater Interface Related Config,
and select Create > Local Office in the pop-up menu, as shown in Figure 4-1.
2. Click Local Office, and the Create Local Office dialog box appears, as shown in
Figure 4-2.
l No.7 type: when E1 A-interface configuration is used, select Narrow band.
l Net appearance info: set this parameter with the same value as that at MSC.
l OPC (14 bits): set this parameter according to planned data.
l OPC (24 bits): ZXG10 iBSC often uses 14-bit signaling point code instead of
24-bit signaling point code.
4-2
SJ-20110909163908-011|2011-10-30 (R1.0)
Note:
After the local office is successfully configured, the local office's signaling subsystem
is generated automatically.
End of Steps
Follow-Up Action
Configure adjacent office.
4-3
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
Adjacent office configuration includes configuring adjacent office signaling point and other
relevant data. The former operation is used to uniquely identify the adjacent office while the
latter operation facilitates the interaction between the local office and the adjacent office.
Steps
1. In the configuration resource tree, double-click the Local Office node under OMC >
GERAN Subnetwork > BSC Managed Element > Config Set > BSC Function >
A/Ater Interface Related Config, and click the
on the right.
2. The Create Adjacent Office dialog box appears, as shown in Figure 4-3. Input the
parameter values.
l Office type: when E1 A-interface configuration is used, the adjacent cell data
of MSC SERVER should be configured, and the adjacent cell data of MGW is
configured according to actual requirement.
l SPT type: set this parameter according to planned data.
l SSF: set this parameter according to planned data.
l SPC type: MSC usually adopts 14-bit signaling point code (SPC 14) to
communicate with ZXG10 iBSC.
l DPC: set this parameter according to planned data.
l AM: set this parameter according to actual condition.
4-4
SJ-20110909163908-011|2011-10-30 (R1.0)
Note:
After the adjacent office is successfully configured, the adjacent office's signaling
subsystem is generated automatically.
End of Steps
Follow-Up Action
Configure SS7 PCM.
4-5
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
Configuring SS7 PCM is used for configuring SS7 PCM service channel.
Steps
1. In the configuration resource tree, double-click the Local Office node under OMC >
GERAN Subnetwork > BSC Managed Element > Config Set > BSC Function >
A/Ater Interface Related Config, and click the
right.
Follow-Up Action
Configure signaling link set.
4-6
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
A signaling link set contains multiple signaling links.
Steps
1. In the configuration resource tree, double-click the Local Office node under OMC >
GERAN Subnetwork > BSC Managed Element > Config Set > BSC Function >
A/Ater Interface Related Config, and click the
the right.
2. The Create No.7 Link Set dialog box appears, as shown in Figure 4-5. Input the
parameter values.
Follow-Up Action
Configure signaling link.
4-7
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
Configuring the signaling link is used for configuring SS7 PCM signaling link properties
and its home physical link.
Steps
1. In the configuration resource tree, double-click the Local Office node under OMC >
GERAN Subnetwork > BSC Managed Element > Config Set > BSC Function >
A/Ater Interface Related Config, and click the
right.
2. The Create No.7 Link dialog box appears, as shown in Figure 4-6. Input the parameter
values.
4-8
SJ-20110909163908-011|2011-10-30 (R1.0)
Follow-Up Action
Configure signaling route.
Context
This section introduces how to configure SS7 signaling route.
Steps
1. In the configuration resource tree, double-click the Local Office node under OMC >
GERAN Subnetwork > BSC Managed Element > Config Set > BSC Function >
A/Ater Interface Related Config, and click the
right.
2. The Create No.7 Route dialog box appears, as shown in Figure 4-7. Input the
parameter values.
Follow-Up Action
Configure signaling office.
Context
This section introduces how to configure SS7 signaling office.
Steps
1. In the configuration resource tree, double-click the Local Office node under OMC >
GERAN Subnetwork > BSC Managed Element > Config Set > BSC Function >
A/Ater Interface Related Config, and click the
right.
2. The Create No.7 Office dialog box appears, as shown in Figure 4-8. Input the
parameter values.
Follow-Up Action
Configure PLMN/MSC office.
4-10
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
ZXG10 iBSC supports multiple operators and multiple MSC offices. It also supports that
various operators share a same physical network. Configuring PLMN/MSC office is used
for associate operators and MSC offices.
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > Set PLMN/MSC Office/SGSN
Office, as shown in Figure 4-9.
2. Click Set PLMN/MSC Office/SGSN Office, and configure MSC in the MSC Office
tab, as shown in Figure 4-10.
4-11
SJ-20110909163908-011|2011-10-30 (R1.0)
l
l
NRI of MSC(NRI): set this parameter with the same value as NRI at the core network. If ZXG10 iBSC does not support FLEX A, do not configure this parameter.
Load allocate ratio of MSC: this parameter defines the service load ratio among
multiple MSCs. For example, if the service load ratio of two MSCs are 2 and 3,
then it indicates that the load ratio between the two MSCs is 2:3. If ZXG10 iBSC
does not support FLEX A, do no configure this parameters.
Selected number: this parameter is related to multi-signaling point function.
When the multi-signaling-point function is enabled, this parameter's value can
not be zero.
4-12
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Perform Gb interface configuration.
4-13
SJ-20110909163908-011|2011-10-30 (R1.0)
4-14
SJ-20110909163908-011|2011-10-30 (R1.0)
Chapter 5
GB-interface Configuration
Table of Contents
Overview ....................................................................................................................5-1
E1 GB-interface Configuration....................................................................................5-1
IP GB-interface Connection ........................................................................................5-7
5.1 Overview
Gb interface data configuration includes configuring data channels between ZXG10 iBSC
and SGSN, and configuring interconnection between ZXG10 iBSC and SGSN.
ZXG10 iBSC supports two interface types: E1 Gb interface and IP Gb interface. Different
transmission modes have different bottom-layer bearer protocols. Such difference also
causes different configurations.
NSE ID
Starting timeslot and access rate of Gb interface bearer link.
Data link connection identifier of NSVC
NSVC ID
Context
NSEI is the identifier of the network service entity. Under one NSE, multiple NSVCs can be
configured at Gb interface, and multiple BVCs (cell) can be configured at radio interface.
Data of such cells can be transmitted via any NSVC under the same NSEI, and these
NSVC share the load. ZXG10 iBSC can be configured with multiple NSEIs.
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > Gb Interface Related Config >
SGSN Office > NSE Config, and select Create > NSE, as shown in Figure 5-1.
2. Click NSE, and the Create NSE dialog box appears, as shown in Figure 5-2. Input the
parameter values.
l NSE ID: It must be consistent with that at SGSN.
l Type of sub-network: For E1 Gb, select Frame relay.
5-2
SJ-20110909163908-011|2011-10-30 (R1.0)
Follow-Up Action
Configure BRCH.
Context
BRCH is the physical channel of Gb interface.
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > Gb Interface Related Config >
SGSN Office > BRCH Config, and select Create > BRCH, as shown in Figure 5-3.
5-3
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click BRCH, and the Create BRCH dialog box appears, as shown in Figure 5-4. Input
the parameter values.
l Link: Make sure that all BRCHs on GIPB differ from each other.
l Unit: GIPB unit number, and the GIPB processes this BRCH.
l CPU ID: CPU number, and the CPU processes this BRCH.
l PCM timeslot: The minimum timeslot number of the BRCH, it must be consistent
with that at SGSN.
l Access rate: Number of BRCH's timeslots, it must be consistent with that at
SGSN.
l MCC start timeslot: The value range is 0 ~ 127. For BRCHs on one CPU of
GIPB, the range of [MCC start timeslot, MCC start timeslot + Access rate] can not
be overlapped.
5-4
SJ-20110909163908-011|2011-10-30 (R1.0)
Follow-Up Action
Configure NSVC.
Context
NSVC is the virtual channel at Gb interface. One BRCH can be configured with one or
multiple NSVCs.
5-5
SJ-20110909163908-011|2011-10-30 (R1.0)
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > Gb Interface Related Config >
SGSN Office > NSE Config > NSE ID, and select Create > NSVC, as shown in Figure
5-5.
2. Click NSVC, and the Create NSVC dialog box appears, as shown in Figure 5-6. Input
the parameter values.
l NSVC ID: It must be consistent with that at SGSN.
l DLCI: It must be consistent with that at SGSN.
5-6
SJ-20110909163908-011|2011-10-30 (R1.0)
Follow-Up Action
None
l
l
l
l
l
NSE ID
IP address and UDP port number of IPGB's local endpoint.
Signaling weight
Data weight
For static NSE configuration:
Signaling weight
Data weight
Context
Configure RPU interface, that is, configure the virtual IP address of ZXG10 iBSC.
Steps
1. In the configuration resource tree, double-click OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > IP Related Config, and click the
icon in the Interface tab on the right.
2. The Create Interface dialog box appears, as shown in Figure 5-7. Input the parameter
values.
l Board function type: Select RPU.
l IP address: Set this parameter according to planned data.
l Subnet mask: 255.255.255.255
5-8
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Configure IPGB interface.
5-9
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
This section introduces how to configure the IP Gb interface address.
Steps
1. In the configuration resource tree, double-click OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > IP Related Config, and click the
icon in the Interface tab on the right.
2. The Create Interface dialog box appears, as shown in Figure 5-9. Input the parameter
values.
l Board function type: Select IPGB.
l MAC address: Input the MAC address of the GIPI rear board's network port.
l IP address: Set this parameter according to planned data.
l Subnet mask: Set this parameter according to planned data.
5-10
SJ-20110909163908-011|2011-10-30 (R1.0)
Follow-Up Action
Configure static route.
Context
When the IP address (at most four IP addresses can be configured) of IPGB interface is
in the different network segment from that of ZXG10 iBSC and SGSN, it is necessary to
configure static route. If no IP address of IPI interface is in the different network segment
from that of iBSC and MSC, it is not necessary to configure static route.
5-11
SJ-20110909163908-011|2011-10-30 (R1.0)
Steps
1. In the configuration resource tree, double-click OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > IP Related Config, and click the
icon in the Static Router tab on the right.
2. The Create Static Router dialog box appears, as shown in Figure 5-10. Input the
parameter values.
l Static router prefix: Set this parameter according to planned data.
l Static router subnet mask: Set this parameter according to planned data. For
example, set Static router prefix to be 192.168.1.0, and set Static router subnet
mask to be 255.255.255.0. It indicates that, for SGSNs of which the IP address
is within [192.168.1.1, 192.168.1.254], ZXG10 iBSC sends data to these SGSNs
via the current route.
l Next hop type: Select IP.
l Next hop IP address: Set this parameter according to planned data. It means
the IP address of the router or SGSN6.
Figure 5-10 Configuring Static Route
Follow-Up Action
Perform configuration related to Gb interface.
Context
NSEI is the identifier of the network service entity. ZXG10 iBSC can be configured with
multiple NSEIs.
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > Gb Interface Related Config >
SGSN Office > NSE Config, and select Create > NSE, as shown in Figure 5-11.
5-13
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click NSE, and the Create NSE dialog box appears, as shown in Figure 5-12. Input
the parameter values.
l NSE ID: It must be consistent with that at SGSN.
l Type of sub-network: For IP Gb, select IP.
l Configure type: There are two configuration modes: Static and Dynamic. Static configuration is used for point-to-point private network. Manual negotiation between ZXG10 iBSC and SGSN is required, that is, configuring the combination of
NSVC's endpoints manually.
l Pre-configured SGSN IP address: IP address of SGSN. This parameter must
be configured for dynamic configuration.
l Pre-configured SGSN UDP port: UDP port of SGSN. This parameter must be
configured for dynamic configuration.
Follow-Up Action
Configure IPGB endpoint.
Prerequisites
NSE is configured successfully.
5-14
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
Configuring IPGB's local endpoint includes configuring the virtual address of RPU at
ZXG10 iBSC and the UDP port number interconnected with SGSN.
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > Gb Interface Related Config
> SGSN Office > IPGB Endpoint Config, and select Create > IPGB Endpoint, as
shown in Figure 5-13.
2. Click IPGB Endpoint, and the Create IPGB Endpoint dialog box appears, as shown
in Figure 5-14. Input the parameter values.
l IP address: The virtual address of RPU of ZXG10 iBSC. It must be the same as
that at SGSN.
l UDP port: It must be the same as that at SGSN.
l Endpoint type: Select Local endpoint.
l Signal weight: It must be the same as that at SGSN.
l Data weight: It must be the same as that at SGSN.
5-15
SJ-20110909163908-011|2011-10-30 (R1.0)
Follow-Up Action
l
l
If NSE adopts the static configuration, then the subsequent task is configuring the
remote endpoint of IPGB.
If NSE adopts the dynamic configuration, then the IPGB configuration is completed.
Prerequisites
NSE is configured successfully.
Context
Configuring IPGB's remote endpoint includes configuring the IP address and the UDP port
number of Gb interface at SGSN, which is interconnected with ZXG10 iBSC. The remote
endpoint is only configured when NSE adopts the static configuration.
Steps
1. In the configuration resource tree, right-click on OMC > GERAN Subnetwork > BSC
Managed Element > Config Set > BSC Function > Gb Interface Related Config
> SGSN Office > IPGB Endpoint Config, and select Create > IPGB Endpoint, as
shown in Figure 5-15.
5-16
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click IPGB Endpoint, and the Create IPGB Endpoint dialog box appears, as shown
in Figure 5-16. Input the parameter values.
l IP address: The virtual address of SGSN. It must be the same as that at SGSN.
l UDP port: It must be the same as that at SGSN.
l Endpoint type: Select Remote endpoint.
l Signal weight: It must be the same as that at SGSN.
l Data weight: It must be the same as that at SGSN.
5-17
SJ-20110909163908-011|2011-10-30 (R1.0)
Follow-Up Action
None
5-18
SJ-20110909163908-011|2011-10-30 (R1.0)
Appendix A
Corresponding Relationship
between Logic Board and
Physical Board
Table A-1 Corresponding Relationship between Logic Board and Physical Board of
ZXG10 iBSC
Physical Board Name
GIPI
IPBB
IPAB
IPGB
IPI
BIPI
IPBB
IPAB
IPGB
EIPI
EIPI
CHUB
CHUB
CLKG
CLKG
ICM
ICM
CMP
CMP
DTB
DTB
GLI
GLI
GUP2
BIPB2
AIPB
DRTB2
UPPB2
TIPB2
A-1
SJ-20110909163908-011|2011-10-30 (R1.0)
GUP
BIPB
DRTB
TIPB
UPPB
OMP
OMP
PSN
PSN
SDTB2
SDTB2
SDTB
SDTB
SPB2
SPB2
GIPB2
LAPD2
SPB
SPB
GIPB
LAPD
SBCX
SVR
UIMC
UIMC
GUIM
GUIM
UIMU
UIMU
A-2
SJ-20110909163908-011|2011-10-30 (R1.0)
Appendix B
OMP Construction
Table of Contents
Overview ................................................................................................................ B-1
OMP Configuration Flow......................................................................................... B-1
Configuring OMP at Serial Port............................................................................... B-2
Uploading Configuration File................................................................................. B-14
B.1 Overview
By creating the OMP boot file at NetNumen client, a configuration file ompcfg.ini will be
generated under the directory ums-svr\tmp\ftp\version\bscX. Here, X reresents the office
number, which is configured at background, and it is not the office number red from the
DIP switch of backplane.
When the OMP board is being started, the ompcfg.ini file is read from NetNumen server to
load the OMP version file. It requires to configure parameters for communication between
OMP and NetNumen server, and such parameters include:
l
l
l
l
l
IP address of OMP
IP address of NetNumen server
Office number
FTP user name and password
OMP startup mode
B-1
SJ-20110909163908-011|2011-10-30 (R1.0)
Steps
1. Connect the debugging serial port (DEBUG2-232 port of RMPB board) of OMP to the
serial port of the debugging computer. Run the super terminal program of the operating
system. Input the connection name in the Connection Description dialog box, and
select the icon for the connection, as shown in Figure B-2.
2. Click OK, and the Connect To dialog box appears. Select the serial port that is
actually connected to the foreground (in this example, COM1 port is connected to the
debugging port of OMP), and click OK, as shown in Figure B-3.
B-2
SJ-20110909163908-011|2011-10-30 (R1.0)
3. In the COM1 Properties dialog box, click Restore Defaults to restore the port's
parameters to default values. Click OK, as shown in Figure B-4.
B-3
SJ-20110909163908-011|2011-10-30 (R1.0)
4. After the connection is established successfully, the system gives the prompt Press
any key to stop auto-boot.... Press any key to start configuring OMP parameters, as
shown in Figure B-5.
B-4
SJ-20110909163908-011|2011-10-30 (R1.0)
7. Select 1 to configure IP address and MAC address of OMP, as shown in Figure B-8.
8. Set the IP address of OMP. Here, set the IP address as 129.0.31.10 (same as that at
NetNumen), as shown in Figure B-9.
B-5
SJ-20110909163908-011|2011-10-30 (R1.0)
9. Input the MAC address of OMP board upon delivery. Here, no configuration is needed,
press the Enter key, as shown in Figure B-10.
10. Input the IP address of OMP's gateway. Here, no configuration is needed, press the
Enter key, as shown in Figure B-11.
B-6
SJ-20110909163908-011|2011-10-30 (R1.0)
11. Select 2 to configure the IP address of NetNumen server, as shown in Figure B-12.
12. Input the IP address of SBCX. Here, set the IP address as 129.0.0.1 (same as that at
NetNumen), as shown in Figure B-13.
B-7
SJ-20110909163908-011|2011-10-30 (R1.0)
13. Input the ftp user name for logging in NetNumen server's SBCX: uep, as shown in
Figure B-14.
14. Input the ftp password for logging in NetNumen server: uep, as shown in Figure B-15.
B-8
SJ-20110909163908-011|2011-10-30 (R1.0)
15. Input the actual path of the ompcfg.ini file at NetNumen server: /tmp/ftp/version/bsc1
(Here, take BSC1 for example), as shown in Figure B-16.
Note:
The number following bsc must be consistent with the BSC managed element identifier
configured in NetNumen.
B-9
SJ-20110909163908-011|2011-10-30 (R1.0)
16. Input the configuration file name: ompcfg.ini, as shown in Figure B-17.
17. Select 3 to select the OMP boot type for this debugging, as shown in Figure B-18.
18. Input 0 to select to load file from NetNumen server, as shown in Figure B-19.
B-10
SJ-20110909163908-011|2011-10-30 (R1.0)
19. Select 4 to configure the switching office number, as shown in Figure B-20.
20. Input the switching office number, which is optional. When inputting this value, make
sure that it is consistent with the BSC managed element ID, as shown in Figure B-21.
B-11
SJ-20110909163908-011|2011-10-30 (R1.0)
22. Select 0 to enter the automatic boot mode, as shown in Figure B-23.
B-12
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
After OMP is automatically booted, it downloads the software version file and the FPGA
file from SBCX. After OMP is booted, the RUN indicator on MPX86 board flashes slowly.
After the prompt -> in super terminal, input SCSShowMcmInfo and press Enter key, and
the system gives the prompt message as shown in Figure B-24.
Figure B-24 Status Displayed after OMP Is Booted Normally
B-13
SJ-20110909163908-011|2011-10-30 (R1.0)
Note:
If the printing information shows that the board is in status of "MASTER" and "WORK", then
it indicates that the OMP board is in normal working status; otherwise, the OMP board's
status is abnormal.
USERPRIENABLE
0 indicates not using the EGSM/PGSM channel allocation policy; 1 indicates using
the EGSM/PGSM channel allocation policy.
CELL ID CFG
0 indicates that the type of CELL_ID is CELLID_LAC_CI; 1 indicates that the type of
CELL_ID is CELLID_CGI.
FRONTEND IP
The IP address of the front-end processor, that is, the IP address of SBCX.
FRONTEND UID
The user ID that accesses the front-end processor SBCX, it must be consistent with
that of gomcr user.
RONTEND GID
The user group ID that accesses the front-end processor SBCX, it must be consistent
with that of gomcr user.
ZXG10.cfg is released with the software version file, and is located under the directory
where the MP version file is.
Steps
1. Upload the ZXG10.cfg file to the directory /DOC0/CFG at OMP through ftp.
B-14
SJ-20110909163908-011|2011-10-30 (R1.0)
B-15
SJ-20110909163908-011|2011-10-30 (R1.0)
B-16
SJ-20110909163908-011|2011-10-30 (R1.0)
Appendix C
Common Configuration
Operation
Table of Contents
Basic Operations of Data Configuration .................................................................. C-1
Performing Switchover between Master Config Set and Slave Config Set............... C-4
Exporting Physical Data.......................................................................................... C-6
Exporting Radio Data.............................................................................................. C-8
Exporting Software Data....................................................................................... C-10
Exporting Network Planning Data ......................................................................... C-12
Performing Configuration Data Backup ................................................................. C-14
Recovering Data Configuration ............................................................................. C-16
Configuring BSC Rack by Template ...................................................................... C-20
Data Synchronization............................................................................................ C-22
C-1
SJ-20110909163908-011|2011-10-30 (R1.0)
Note:
"Apply Mutex Right" is designed to avoid multiple clients performing operations
simultaneously on the data, which might cause data error.
The following takes modifying the master config for example. The operation steps are
listed as below:
1. Right-click on BSC Managed Element, and select Apply Mutex Right in the pop-up
menu, as shown in Figure C-1.
Figure C-1 Selecting Apply Mutex Right
2. Click Apply Mutex Right, and the Information dialog box appears, as shown in Figure
C-2.
C-2
SJ-20110909163908-011|2011-10-30 (R1.0)
3. Click Yes, and the mutex right is successfully acquired, and the
icon appears on
the configuration resource tree, as shown in Figure C-3. Then, the toolbutton
enabled, and user can modify the configuration data of this managed element.
is
4. After the data modification is completed, user should right-click on BSC Managed
Element and select Release Mutex Right in the pop-up menu, as shown in Figure
C-4. After the mutex right is released, other users can perform operations on the
configuration data of this managed element.
C-3
SJ-20110909163908-011|2011-10-30 (R1.0)
Caution!
When user exits the client, the system automatically releases the mutex right.
Moreover, users at other clients can forcibly acquire the mutex right.
Context
Switch over the slave config set to be master config set.
C-4
SJ-20110909163908-011|2011-10-30 (R1.0)
Steps
1. In the configuration resource tree, double-click the newly configured slave config set,
and the slave config set's property tab will be displayed on the right, as shown in Figure
C-5.
Figure C-5 Performing Switchover between Master Config Set and Slave Config
Set (1)
Figure C-6 Performing Switchover between Master Config Set and Slave Config
Set (2)
3. Click Ok to complete the switchover between master config set and slave config set.
After the operation is completed, the original slave config set is switched over to be
master config set, as shown in Figure C-7.
C-5
SJ-20110909163908-011|2011-10-30 (R1.0)
Figure C-7 Performing Switchover between Master Config Set and Slave Config
Set (3)
End of Steps
Follow-Up Action
After the master config set and the slave config set are switched over, data synchronization
must be performed to make the new master config set's data take effect at foreground.
Context
This section introduces how to export the configured physical data.
Steps
1. In the configuration resource tree, right-click on BSC Function, and select Export
Data to Excel > Export Physical Data in the pop-up menu, as shown in Figure C-8.
C-6
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click Export Physical Data, the Save dialog appears. Select the directory where the
data file is to be saved, and input File Name, as shown in Figure C-9.
Figure C-9 Exporting Physical Data (2)
3. Click Save to export the data file. After the operation is completed, the system gives
the success prompt, as shown in Figure C-10.
C-7
SJ-20110909163908-011|2011-10-30 (R1.0)
The exported physical data is saved as Excel file. It is recommended to save the file
in the following path:
..\MINOSV3.10.410c\ert\ISMG-V6.20.100e-\ums-clnt\template\exce
l\exceldata
End of Steps
Follow-Up Action
Export radio data.
Context
This section introduces how to export the configured radio data.
Steps
1. In the configuration resource tree, right-click on BSC Function, and select Export
Data to Excel > Export Radio Resource Data in the pop-up menu, as shown in Figure
C-11.
C-8
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click Export Radio Resource Data, the Save dialog appears. Select the directory
where the data file is to be saved, and input File Name, as shown in Figure C-12.
Figure C-12 Exporting Radio Data (2)
3. Click Save to export the data file. After the operation is completed, the system gives
the success prompt, as shown in Figure C-13.
C-9
SJ-20110909163908-011|2011-10-30 (R1.0)
The exported radio data is saved as Excel file. It is recommended to save the file in
the following path:
..\MINOSV3.10.410c\ert\ISMG-V6.20.100e-\ums-clnt\template\exce
l\exceldata
End of Steps
Follow-Up Action
Export software data.
Context
This section introduces how to export the configured software data.
Steps
1. In the configuration resource tree, right-click on BSC Function, and select Export
Data to Excel > Export Software Data in the pop-up menu, as shown in Figure C-14.
C-10
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click Export Software Data, the Save dialog appears. Select the directory where the
data file is to be saved, and input File Name, as shown in Figure C-15.
Figure C-15 Exporting Software Data (2)
3. Click Save to export the data file. After the operation is completed, the system gives
the success prompt, as shown in Figure C-16.
C-11
SJ-20110909163908-011|2011-10-30 (R1.0)
The exported software data is saved as Excel file. It is recommended to save the file
in the following path:
..\MINOSV3.10.410c\ert\ISMG-V6.20.100e-\ums-clnt\template\exce
l\exceldata
End of Steps
Follow-Up Action
Export network planning data.
Context
This section introduces how to export the configured network planning data.
Steps
1. In the configuration resource tree, right-click on BSC Function, and select Export
Data to Excel > Export Network Plan Data in the pop-up menu, as shown in Figure
C-17.
C-12
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click Export Network Plan Data, the Save dialog appears. Select the directory where
the data file is to be saved, and input File Name, as shown in Figure C-18.
3. Click Save to export the data file. After the operation is completed, the system gives
the success prompt, as shown in Figure C-19.
C-13
SJ-20110909163908-011|2011-10-30 (R1.0)
The exported network planning data is saved as Excel file. It is recommended to save
the file in the following path:
..\MINOSV3.10.410c\ert\ISMG-V6.20.100e-\ums-clnt\template\exce
l\exceldata
End of Steps
Follow-Up Action
Apply the network planning data in batch.
Context
This section introduces how to perform configuration data backup.
Steps
1. In the configuration resource tree, select Management > Data Management > Data
Backup, as shown in Figure C-20.
C-14
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click Data Backup, the Data Backup dialog box appears. Select Storage path, input
File name prefix and Backup remark, and select the managed element to be backed
up, as shown in Figure C-21. If only the master config set is to be backed up, then
check Only backup active ConfigSet(s).
3. Click OK to back up the configuration data. The data backup result is shown in Figure
C-22.
C-15
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Recover data configuration.
Context
This section introduces how to recover data configuration.
Steps
1. In the configuration resource tree, select Management > Data Management > Data
Recover, as shown in Figure C-23.
C-16
SJ-20110909163908-011|2011-10-30 (R1.0)
2. Click Data Recover, and the Data Recover dialog box appears. Click Select to select
the backup data file to be recovered to import the data, as shown in Figure C-24.
3. Check the config set to be recovered, and click OK to recover the data configuration.
The Data Recover Result dialog box appears, and the recovered config set is added
below the BSC managed element, as shown in Figure C-25.
C-17
SJ-20110909163908-011|2011-10-30 (R1.0)
4. After the data recovery operation is completed, user can click Apply Mutex Right
And Set active Configset in Figure C-25. The Apply Mutex dialog box appears, as
shown in Figure C-26.
C-18
SJ-20110909163908-011|2011-10-30 (R1.0)
5. Select the managed element and click Apply Mutex, select the config set to be
switched over to master config set, and click Set Active ConfigSet(s) to finish the
switchover, as shown in Figure C-27.
End of Steps
Result
After the operation is completed, the recovered config set appears on the configuration
resource tree. If the recovered config set is also switched over to be master config set,
then the new master config set will be marked, as shown in Figure C-28.
Figure C-28 Data Recovery Result
C-19
SJ-20110909163908-011|2011-10-30 (R1.0)
Caution!
After the data recovery and config set switchover are completed, user must perform all
data synchronization to make the data configuration take effect.
Context
This section introduces how to configure a BSC rack based on the template.
Steps
1. In the configuration resource tree, right-click on the BSC Device Config node and
select Create > Create BSC Rack by Template, as shown in Figure C-29.
Figure C-29 Configuring BSC Rack by Template (1)
2. Click Create BSC Rack by Template, the Create BSC Rack by Template dialog box
appears, as shown in Figure C-30. Select Template type and Template according to
actual requirement.
l If System is selected as the template type, all available system templates will be
listed in the Template drop-down list box.
l If Custom is selected as the template type, all available customized templates
will be listed in the Template drop-down list box.
C-20
SJ-20110909163908-011|2011-10-30 (R1.0)
Caution!
Usually, the operation of configuring BSC rack by template is performed at the very
beginning, and there should not be any BSC rack configured in the system. If the
system has been configured with some BSC rack, then the operation of configuring
BSC rack by template will fail when the BSC rack number in the customized template
is same as that of an existed BSC rack.
3. Click OK. After the operation is completed, the newly configured BSC rack node
appears on the configuration resource tree, and shelves and boards are automatically
configured in the rack according to the template. Figure C-31 shows an example of
the configured rack.
C-21
SJ-20110909163908-011|2011-10-30 (R1.0)
End of Steps
Follow-Up Action
Create interface.
C-22
SJ-20110909163908-011|2011-10-30 (R1.0)
Context
This section introduces how to perform all data synchronization.
Steps
1. In the configuration resource tree, right-click on the BSC Managed Element node and
select Config Data Managed Element > Synchronize All Data, as shown in Figure
C-32.
2. Click Synchronize All Data to check the global data validity. After the check is passed,
click OK, and the Synchronization All Data dialog box appears, as shown in Figure
C-33.
C-23
SJ-20110909163908-011|2011-10-30 (R1.0)
Caution!
Save it indicates saving the data to the hard disk of OMP. It is recommended to select
Yes to avoid data loss.
3. Input parameter values according to actual requirement, and click OK to start the
synchronization. After the synchronization succeeds, the system gives the success
prompt.
Caution!
All data synchronization is only effective to the master config set's data.
End of Steps
Context
If only some data is modified, user can perform modified data synchronization to
accelerate the synchronization speed. This section introduces how to perform modified
data synchronization.
C-24
SJ-20110909163908-011|2011-10-30 (R1.0)
Steps
1. In the configuration resource tree, right-click on the BSC Managed Element node and
select Config Data Managed Element > Synchronize Modified Data, as shown in
Figure C-34.
2. Click Synchronize Modified Data to check the global data validity. After the check
is passed, click OK, and the Synchronization Modified Data dialog box appears, as
shown in Figure C-35.
Caution!
Save it indicates saving the data to the hard disk of OMP. It is recommended to select
Yes to avoid data loss.
C-25
SJ-20110909163908-011|2011-10-30 (R1.0)
3. Input parameter values according to actual requirement, and click OK to start the
synchronization. After the synchronization succeeds, the system gives the success
prompt.
Caution!
Modified data synchronization is only effective to the master config set's data.
End of Steps
C-26
SJ-20110909163908-011|2011-10-30 (R1.0)
Figures
Figure 1-1 Logging in Configuration Management (1) ............................................... 1-2
Figure 1-2 Logging in Configuration Management (2) ............................................... 1-3
Figure 1-3 Logging in Configuration Management (3) ............................................... 1-4
Figure 1-4 Configuration Management Interface ....................................................... 1-5
Figure 1-5 Data Configuration Flow........................................................................... 1-7
Figure 2-1 Configuring GERAN Subnetwork (1) ........................................................ 2-2
Figure 2-2 Configuring GERAN Subnetwork (2) ........................................................ 2-2
Figure 2-3 Configuring GERAN Subnetwork (3) ........................................................ 2-3
Figure 2-4 Configuring BSC Managed Element (1) ................................................... 2-4
Figure 2-5 Configuring BSC Managed Element (2) ................................................... 2-4
Figure 2-6 Configuring BSC Managed Element (3) ................................................... 2-5
Figure 2-7 Configuring Config Set (1)........................................................................ 2-6
Figure 2-8 Configuring Config Set (2)........................................................................ 2-6
Figure 2-9 Configuring Config Set (3)........................................................................ 2-7
Figure 2-10 Configuring BSC Function (1) ................................................................ 2-8
Figure 2-11 Configuring BSC Function (2)................................................................. 2-8
Figure 2-12 Configuring BSC Function (3) .............................................................. 2-10
Figure 3-1 Manually Configuring BSC Rack (1)......................................................... 3-2
Figure 3-2 Manually Configuring BSC Rack (2)......................................................... 3-2
Figure 3-3 Manually Configuring BSC Rack (3)......................................................... 3-3
Figure 3-4 Configuring Shelf and Board (1)............................................................... 3-4
Figure 3-5 Configuring Shelf and Board (2)............................................................... 3-5
Figure 3-6 Configuring Shelf and Board (3)............................................................... 3-5
Figure 3-7 Configuring Shelf and Board (4)............................................................... 3-6
Figure 4-1 Configuring Local Office (1)...................................................................... 4-2
Figure 4-2 Configuring Local Office (2)...................................................................... 4-3
Figure 4-3 Configuring Adjacent Office (1) ................................................................ 4-5
Figure 4-4 Configuring SS7 PCM (1)......................................................................... 4-6
Figure 4-5 Configuring Signaling Link Set (1) ............................................................ 4-7
Figure 4-6 Configuring Signaling Link (1) .................................................................. 4-8
Figure 4-7 Configure Signaling Route (1) .................................................................. 4-9
Figure 4-8 Configuring Signaling Office (1) ............................................................. 4-10
I
II
Figures
III
IV
Tables
Table 1-1 Configuration Management Toolbar ........................................................... 1-5
Table 1-2 Configuration Management Element Toolbar ............................................. 1-5
Table A-1 Corresponding Relationship between Logic Board and Physical Board
of ZXG10 iBSC ........................................................................................A-1
Tables
Glossary
DTB
- Digital Trunk Board
GERAN
- GSM/EDGE Radio Access Network
GSM
- Global System for Mobile Communication
GUIM
- Gigabit Universal Interface Module
MSC
- Mobile Switching Center
NSE
- Network Service Entity
NSVC
- Network Service Virtual Connection
OMP
- Operation Main Processor
PCM
- Pulse Code Modulation
SDTB
- SONET Digital Trunk Board
SGSN
- Service GPRS Supporting Node
SPB
- Signaling Processing Board
UIMC
- Universal Interface Module for Control plane (BCTC or BPSN)
UIMU
- Universal Interface Module for User Plane
VII