BSC Global Data (A over IP, Built-in PCU)

BSC global data is determined during network planning. It provides a basis for the configuration of all the other data. After the BSC global data takes effect, do not modify it unless the network is planned again.

BSC global data includes BSC attributes, M3UA data, and GMPS-OPC mapping. The examples of the configurations of BSC global data are as follows:

BSC Attributes

**Table 1** Example of the data negotiated and planned for configuring BSC attributes
Parameter	Parameter to Be Configured	Example	Source
Basic Data	BSC Name	BSC001	Network planning
	Country Code	86	Network planning
	City Code	021	Network planning
	MCC	460	Network planning
	MNC	10	Network planning
	A Interface Tag	GSM_PHASE_2+	Network planning
	Um Interface Tag	GSM_PHASE_2+	Network planning
	Abis Interface Tag	GSM_PHASE_2+	Network planning
	NTP Server	10.161.72.251	Negotiation with the M2000
	BSC Subrack Combination Type	IP on A Interface	Network planning
	PCUType	Inner	Network planning

M3UA Data

**Table 2** Example of the data negotiated and planned for configuring the M3UA data
Parameter	Parameter to Be Configured	Example	Source
Local Entity	Local Entity Name	BSC001	BSC internal planning
	OPC (Hex)	B1	Network planning
	Encoding Scheme	14	Network planning
	Network Indicator	NATB	Network planning
Destination Entity	Destination Entity Name	MSC001	BSC internal planning
Destination Entity	DPC(Hex)	D1	Network planning
Configuring the M3UA Link Set	LinkSet Name	0	Network planning
Configuring the M3UA Link Set	Adjacent Destination Entity Name	MSC001	Network planning
M3UA Config Route	Destination Entity Name	MSC001	Network planning
M3UA Config Route	LinkSet Name	0	Network planning

If there is no direct physical link between the local entity and the destination entity, you need to configure a signaling transfer entity. When configuring the destination entity, set Using STP to Yes. When configuring the M3UA link set, set Adjacent Destination Entity Name to the signaling transfer entity name. For the examples of the data negotiated and planned for configuring the signaling transfer entity, see Table 3.

**Table 3** Example of the data negotiated and planned for configuring the STP
Parameter	Parameter to Be Configured	Example	Source
STP Entity	STP Name	MGW001	BSC internal planning
	STP (Hex)	C1	Network planning
	Protocol	RFC3332	Network planning

Subrack-OPC Mapping

**Table 4** Example of the data negotiated and planned for configuring the subrack-OPC mapping
Parameter	Example	Source
Subrack No.	0	BSC internal planning
OPC	B1	Network planning