This provides examples of the A interface data negotiated and planned for interconnection when the A over IP mode is used.
The A interface data negotiated for the connection between the BSC and the MSC is as follows:
M3UA data
M3UA data includes the M3UA entities, M3UA link set, and M3UA route. The M3UA data on the BSC side and that on the MSC side must be consistent.
CGI parameters
CGI uniquely identifies a cell in the GSM system. CGI consists of the MCC, MNC, LAC, and CI. The settings of these parameters on the BSC side and those on the MSC side must be consistent.
M3UA link parameters on the A interface
In A over IP mode, the M3UA link parameters include the Linkset Name, Local Port No., Peer Port No., Local Address 1, Local Address 2, Peer Address 1, Peer Address 2, Send Check Sum Validation Flag, and Check Sum Type. The settings of these parameters must be negotiated on both the BSC side and the MSC side.
A Interface Tag
The A interface tags consist of GSM_PHASE_1, GSM_PHASE_2, and GSM_PHASE_2+. The setting of this parameter on the BSC side and that on the MSC side must be consistent.
Location update period
The location update period is defined by T3212. The location update period on the MSC side must be longer than that on the BSC side.
Authentication and ciphering parameters
The settings of authentication and ciphering parameters on the BSC side and those on the MSC side must be consistent.
Inter-BSC or Inter-MSC handover parameters
If inter-BSC or inter-MSC handovers are required, parameters such as CGI, BCCH frequency, NCC, BCC, and Co-MSC must be negotiated on both the BSC side and the MSC side.
Parameter |
Parameter to Be Configured |
Example |
Source |
---|---|---|---|
Local Entity |
Local Entity Name |
BSC001 |
Internal BSC planning |
OPC (Hex) |
B1 |
Network planning |
|
Network Indicator |
NATB |
Network planning |
|
Destination Entity |
Destination Entity Name |
MSC001 |
BSC internal planning |
DPC(Hex) |
D1 |
Network planning |
|
M3UA Link |
LinkSet Name |
0 |
Network planning |
Adjacent Destination Entity Name |
MSC001 |
Network planning |
|
M3UA Route |
Destination Entity Name |
MSC001 |
Network planning |
LinkSet Name |
0 |
Network planning |
Parameter |
Parameter to Be Configured |
Example |
Source |
---|---|---|---|
Basic Attribute Parameters |
MCC |
460 |
Network planning |
MNC |
01 |
Network planning |
|
LAC |
8240 |
Network planning |
|
CI |
1 |
Network planning |
Parameter |
Parameter to Be Configured |
Example |
Source |
---|---|---|---|
M3UA |
LinkSet Name |
0 |
Negotiation with the peer |
Local Port No. |
1 |
Negotiation with the peer |
|
Peer Port No. |
1 |
Negotiation with the peer |
|
Local Address 1 |
172.16.120.44 |
Negotiation with the peer |
|
Peer Address 1 |
172.16.20.1 |
Negotiation with the peer |
|
SCTP |
Send Check Sum Validation Flag |
Yes |
Network planning |
Check Sum Type |
CRC32 |
Negotiation with the peer |