Cisco Cisco ASR 5000
RIM Message Transfer from BSC or RNC to eNodeB
Configuring RIM Msg Transfer to or from eNodeB ▀
SGSN Administration Guide, StarOS Release 18 ▄
The following illustrates the minimum configuration required to associate the SGTP and IuPS services for the RIM
message transfers:
message transfers:
configure
context context_name
sgsn-service service_name
associate sgtp-service service_name context context_name
ran-protocol iups-service service_name
end
Configuring the peer-MME's address - Locally
Use the Call Control Profile to define the peer-MME address.
Use the tac keyword to configure the tracking area code (TAC) of the target eNodeB that maps to the peer-MME
address. For RIM message transfer, you also need to configure the Gn interface. The following is an example of the
configuration to use:
address. For RIM message transfer, you also need to configure the Gn interface. The following is an example of the
configuration to use:
configure
call-control-profile profile_name
peer-mme tac tac_value prefer local address ip_address interface gn
end
Where:
tac_value
can be an entry from 1 to 65535.
ip_address
is the standard format address for either IPv4 or IPv6.
gn
is the interface selection used for RIM message transfer.
Configuring the peer-MME's address - for DNS Query
If using a DNS query to determine the peer-MME RIM address, then the DNS server must be pre-configured to respond
to a TAI-based DNS query in the following format:
to a TAI-based DNS query in the following format:
tac-lb<TAC-low-byte>.tac-hb<TAC-high-
byte>.tac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org