Cisco Cisco ASR 5000
SGSN Serving Radio Network Subsystem Relocation
▀ How it Works
▄ SGSN Administration Guide, StarOS Release 18
SI.No RNC
Release
Compliance
Compliance
Target Type Sent
in Relocation
Request
in Relocation
Request
LAC
Configured
as MME
Group ID?
Configured
as MME
Group ID?
LAC MSB
Set?
Set?
Peer
Type?
Type?
Type of DNS
Query?
Query?
Interface
IP
Provided
by DNS?
IP
Provided
by DNS?
Interface Chosen?
2
R8+
eNodeB
n/a
n/a
MME
DNS
SNAPTR
w/ service
type x-
3gpp-
mme:x-s3
and TAC
FQDN
SNAPTR
w/ service
type x-
3gpp-
mme:x-s3
and TAC
FQDN
Gn
When a TAC FQDN
is used to query the
MME address the
system expects that
the MME supports S3
interface. If this is the
case, the S3 interface
is chosen. If DNS
returns a Gn address,
then the system
rejects the
Relocation, and sends
a Relocation
Preparation Failure to
the source RNC.
is used to query the
MME address the
system expects that
the MME supports S3
interface. If this is the
case, the S3 interface
is chosen. If DNS
returns a Gn address,
then the system
rejects the
Relocation, and sends
a Relocation
Preparation Failure to
the source RNC.
3
R8+
RNC
n/a
n/a
SGSN DNS
SNAPTR
w/ service
type x-
3gpp-
sgsn:x-s16
and RNC
ID FQDN
w/ service
type x-
3gpp-
sgsn:x-s16
and RNC
ID FQDN
S16
S16
4
R8+
RNC
n/a
n/a
SGSN DNS
SNAPTR
w/ service
type x-
3gpp-
sgsn:x-s16
and RNC
ID FQDN
w/ service
type x-
3gpp-
sgsn:x-s16
and RNC
ID FQDN
Gn
Gn
5
Pre R8
RNC (A pre R8
RNC cannot send
eNB as the target
type. Currently,
operators
configure eNB ID
to RNC ID
mapping in such
these pre R8
RNCs so that the
SGSN receives an
RNC ID that is
actually mapped
from the eNB ID)
RNC cannot send
eNB as the target
type. Currently,
operators
configure eNB ID
to RNC ID
mapping in such
these pre R8
RNCs so that the
SGSN receives an
RNC ID that is
actually mapped
from the eNB ID)
Yes
Irrelevant MME
DNS
SNAPTR
w/ service
type x-
3gpp-
mme:x-s3
and MME
GI + MME
Code
FQDN
SNAPTR
w/ service
type x-
3gpp-
mme:x-s3
and MME
GI + MME
Code
FQDN
S3
S3