Configuring the M3UA Entities

This describes how to configure the M3UA entities. You need to configure the M3UA entities to achieve A over IP or to enable communication between BSCs. The local entity and destination entity must be configured. If there is no direct physical link between the local entity and the destination entity, you need to configure a signaling transfer entity.

Scenario	BSC initial configuration and BSC capacity expansion
Mandatory/Optional	Mandatory

CAUTION:

The local entity must be configured before the destination entity is configured.
The local entity and destination entity must be configured before the signaling transfer entity is configured.
The name and code of each entity must be unique.

Prerequisite

None.

Preparation

**Table 1** Example of the data negotiated and planned for configuring the M3UA entity
Parameter	Example	Source
Local Entity Name	BSC001	BSC internal planning
OPC (Hex)	B1	Network planning
Route Context	4294967295	Negotiation with the peer
Encoding Scheme	14 bits	Network planning
Network Indicator	Reserved for domestic use	Network planning
Destination Entity Name	MSC001	BSC internal planning
DPC(Hex)	D1	Network planning
Using STP	Yes	Network planning
Protocol	RFC3332	Negotiation with the peer

**Table 2** Example of the data negotiated and planned for configuring the transfer entity
Parameter	Example	Source
Transfer Entity Name	MGW001	BSC internal planning
STP (Hex)	C1	Network planning
Protocol	RFC3332	Network planning

Procedure

Configure the M3UA local entity.
1. On the BSC6000 Local Maintenance Terminal, right-click the BSC6000 root node.
2. Choose Configure M3UA Data > Configure M3UA Entity from the shortcut menu. A dialog box is displayed, as shown in Figure 1.
  Figure 1 Configure M3UA Entity dialog box
3. On the M3UA LE tab page, click Add. A dialog box is displayed, as shown in Figure 2.
  Figure 2 Add M3UA Local Entity dialog box
4. Set the parameters by referring to Table 1.
5. Click OK. The M3UA local entity is configured.
Configure the M3UA destination entity.
1. In the dialog box shown in Figure 1, click the M3UA DE tab to display the tab page, as shown in Figure 3.
  Figure 3 Configure M3UA Entity dialog box
2. Click Add. A dialog box is displayed, as shown in Figure 4.
  Figure 4 Add M3UA Destination Entity dialog box
  
  NOTE:
  If there is no direct physical link between the local entity and the destination entity, you need to configure a signaling transfer entity. In the dialog box shown in Figure 4, set Using STP to Yes.
  
  Route Contextis mapped to a destination entity/signaling transfer entity. Except the invalid value 4294967295, the Route Context of a destination entity or a signaling transfer entity must be unique. Otherwise, the configuration is invalid.
  
  To achieve A over IP, SCCP Sub-System No. is set to 254; to enable communication between BSCs, SCCP Sub-System No. is set to 143.
3. Set the parameters by referring to Table 1.
4. Click OK. The M3UA destination entity is configured.

Check whether there is a direct physical link between the local entity and the destination entity.

If...	Then...
There is a direct physical link between the local entity and the destination entity,	The task is complete.
There is no direct physical link between the local entity and the destination entity,	Go to 4.

Configure the M3UA transfer entity.
1. In the dialog box shown in Figure 1, click the M3UA STE tab to display the tab page, as shown in Figure 5.
  Figure 5 Configure M3UA Entity dialog box
2. Click Add. A dialog box is displayed, as shown in Figure 6.
  Figure 6 Add M3UA Transfer Entity dialog box
3. Set the parameters of the M3UA transfer entity by referring to Table 2.
4. Click OK. The M3UA transfer entity is configured.