RIM message transfer is one of the standards-based RAN Information Management procedures supported by the SGSN.
RAN Information Management (RIM)
RIM procedures provide a generic mechanism for the exchange of arbitrary information between RAN nodes. The RAN information is transferred via the SGSN core network node(s). In order to make the RAN information transparent for the core network, the RAN information is included in a RIM container that shall not be interpreted by the core network nodes.
The RAN information is transferred in RIM containers from the source RAN node to the destination RAN node by use of messages. The SGSN independently routes and relays each message carrying the RIM container.
In pre-15.0 releases, the SGSN supported RIM messages from BSS/RNC to another BSS/RNC belonging to a different or the same SGSNover GTPv1 protocol. Now, the SGSN also supports transfer of RIM messages to/from an MME (eNodeB) via GTPv1 protocol.
The SGSN uses existing CLI to enable the RIM transfer functionality. Whether or not the RIM message goes from/to BSC/RNC to/from BSC/RNC or to/from eNodeB is determined by the addressing. To transfer RIM messages to the MME (eNodeB),
- requires RIM functionality be enabled for the SGSN.
- requires the DNS server be configured to respond to a TAI-based DNS query
- requires the MME (eNodeB) address be added to the SGSNs Call Control Profile
Relationships to Other Feature or Products
For this feature to work properly, the peer-MME for the eNodeB must also support RIM message handling.