3GPP Interface Maps for 2G/3G and SAE/LTE Networks

See discussions, stats, and author profiles for this publication at: https://www.researchgate.
net/publication/271719804
Mobile Interface 3GPP Interfaces description General map SAE/LTE

map
Book · January 2015

DOI: 10.13140/2.1.4555.3447
CITATIONS READS
0 6,459
1 author:
Ankit Saxena
Devi Ahilya Vishwidalaya Indore, Madhya Pradesh India
17 PUBLICATIONS 51 CITATIONS
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
Performance Analysis of Link Adaptation in EUTRAN View project
Analysis of Handover of UE in EUTRAN View project
All content following this page was uploaded by Ankit Saxena on 03 February 2015.
The user has requested enhancement of the downloaded file.

3GPP Interfaces description
This document provide clickable maps about 3GPP network nodes and
interfaces. For readability reasons two different maps have been provided:
the first one shows the 2G/3G network configuration (general map), the
second one shows the SAE/LTE configuration with new nodes and
interfaces (SAE/LTE map).
Please read the readme page for a correct use of the document
Readme
General map
SAE/LTE map
Useful links
Mobile Interface - ankitsaxena
Readme
This is a quick reference guide which shows the mobile network architecture
and related 3GPP interfaces together with their brief description. The main
scope of this guide, is to provide a quick and visual overview. If you need
official technical documentation, please look at the useful link section.
It’s not intended to be used as an official technical specification or as
product/solution guideline.
The technical information are taken form other documents that are subject to
modifications, such modifications may not result in an update of this
document.
Not all nodes/interfaces are mentioned in this document but only the most
common and the ones that are more often included in Ericsson business
solutions.
However reference to Ericsson official documentation is provided to allow
further detail collection.
Mobile Interface - ankitsaxena Back to index

SCP SMS-C
C HLR/HSS
OSS
EIR AUC
GMLC General map
SCF SCF-HLR Lh
H
LI-IMS LEMF
Lc
E C
Ge Gd
Gom Lg
D X1
Gc Gd
Gr X2
Gf MSC-S SSF-SCF MSC-S
GGSN SGSN GMSC SSF
CSCF MRFP
MSC G MSC
SGSN
VLR VLR
Gn E Nc
Gn Gs MGCF Mg
Mj
Gi
Mc
Mc
BGCF
Mub
Mb
IuPS
Ext. PDN
Mur Nb
Other PLMN
Mut MGW MGW
IuCS Gb
A A
BSC
RNC
RNC
Iur A-bis
Iub RBS
Uu
Um
HUB/RXI RBS
RBS
RBS

HLR/HSS EIR AAA
SAE/LTE map
IP Network
S6b
S6d S13
SGi
Gr S6a Serving GW PDN GW
PCRF
SGSN S5/S8
MSC/VLR S4 S7
SGs S11 S2b ePDG

S3
S10
Sv
MME MME
S2c SWn
Gb IuPS S12 S1-MME S1-U
S2a
SWa/STa
RNC
BSC Iub
Um
Uu
Non trusted
X2 Non-3GPP access
RBS
RBS eNodeB eNodeB

A Between Back to general map
Interface Description Top Protocols
Node Node
The A interface between the MSC and its BSS is specified in the 48-series of Technical
Specifications.
MGW, The BSS-MSC interface is used to carry information concerning: BSSAP
A BSC
MSC - BSS management; (DTAP+BSSMAP)
- call handling;
- mobility management.
Control plane
(DTAP / BSSMAP)
BSSAP
SCCP
MTP3
MTP2
MTP1/L1

A-Bis
Between
Back to general map
Node Node
The Abis interface refers to the interface between the BSC and the BTS. The Abis
A-bis BSC BTS
interface allows control of the radio equipment and radio frequency allocation in the BTS.
RR, BTSM
Control plane
BTSM / RR
LAPD
L1

C
Between
Back to general map
Interface
Description Top Protocols
(
Node Node
The Gateway MSC server must interrogate the HLR of the required subscriber to obtain
routing information for a call or a short message directed to that subscriber.
C HLR GMSC
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the
MAP
services of Transaction Capabilities.
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

D
Between
Back to general map
Node Node
This interface is used to exchange the data related to the location of the mobile station
and to the management of the subscriber. The main service provided to the mobile
subscriber is the capability to set up or to receive calls within the whole service area. To
support this, the location registers have to exchange data. The VLR informs the HLR of
the location of a mobile station managed by the latter and provides it (either at location
D HLR VLR updating or at call set-up) with the roaming number of that station. The HLR sends to the MAP
VLR all the data needed to support the service to the mobile subscriber. The HLR then
instructs the previous VLR to cancel the location registration of this subscriber.
Exchanges of data may occur when the mobile subscriber requires a particular service,
when he wants to change some data attached to his subscription or when some
parameters of the subscription are modified by administrative means.
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

E
Between
Back to general map
Interface
((
Node Node
When a mobile station moves from one MSC area to another during a call, a handover
procedure has to be performed in order to continue the communication. For that purpose
the MSC servers have to exchange data to initiate and then to realise the operation.
After the handover operation has been completed, the MSC servers will exchange
E MSC MSC information to transfer A-interface or Iu-interface signalling as defined in 3G TS 23.009. MAP
When a short message is to be transferred between a Mobile Station and Short Message
Service Centre (SC), in either direction, this interface is used to transfer the message
between the MSC server serving the Mobile Station and the MSC server, which acts as
the interface to the SC.
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

F
Between
Back to general map
Node Node
This interface is used between MSC server and EIR to exchange data, in order that the
F MSC EIR
EIR can verify the status of the IMEI retrieved from the Mobile Station.
MAP
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

G
Between
Back to general map
Node Node
When a mobile subscriber moves from a VLR area to another Location Registration
G VLR VLR procedure will happen. This procedure may include the retrieval of the IMSI and MAP
authentication parameters from the old VLR.
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

H Between
Back to general map
Node Node
When an HLR receives a request for authentication and ciphering data for a Mobile
Subscriber and it does not hold the requested data, the HLR requests the data from the
H HLR AUC
AuC. The protocol used to transfer the data over this interface is not standardised. In
MAP
Ericsson nodes the AUC is integrated into the HLR node.

GbBetween
Back to general map
Node Node
The Gb interface connects the SGSN and the BSS, and allows the exchange of signaling Back to SAE/LTE map
information between them. It also allows the exchange of signaling information and user
data between the SGSN and Mobile Stations (MSs).
Gb SGSN BSC
The BSS-SGSN interface is used to carry information concerning:
GMM, SNDCP
- packet data transmission;
- mobility management.
Control plane User plane

GMM SNDCP
LLC
BSSGP
NS
Frame Relay
L1

Gc
Between
Back to general map
Node Node
This optional signalling path may be used by the GGSN to retrieve information about the
location and supported services for the mobile subscriber, to be able to activate a packet
data network address.
Gc GGSN HLR There are two alternative ways to implement this signalling path: MAP
- if an SS7 interface is implemented in the GGSN, signalling between the GGSN
and the HLR uses the Mobile Application Part (MAP), which in turn uses the services of
Transaction Capabilities (TCAP)
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

GdBetween
Back to general map
Node Node
This interface is used to transfer short messages between SGSN/IP-SM-GW and SMS-
SMS-
Gd SGSN
C
GMSC or SMS-IWMSC over GPRS. Signalling on this interface uses the Mobile MAP
Application Part (MAP) (see TS 29.002 [26]).
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b
SAAL-NNI
MTP2 AAL5
ATM
MTP1/L1 L1

Ge
Between
Back to general map
Node Node
The Ge interface connects the SGSN to a Service Control Point (SCP) with Customized
Applications for Mobile Network Enhanced Logic (CAMEL), and grants the SCP real-time
control over subscriber service usage on the SGSN.
Ge SGSN SCP The Ge interface enables the SCP to have real-time control over subscriber service CAMEL
usage on the SGSN. The main application is prepaid charging. Once CAMEL interaction
is activated, the SCP can instruct the SGSN to allow or disallow service invocation, to
insert data in Charging Data Records (CDRs), and to report on service usage.
Control plane
CAP/INAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

Gf
Between
Back to general map
Node Node
This interface is used between SGSN and EIR to exchange data, in order that the EIR
Gf SGSN EIR
can verify the status of the IMEI retrieved from the Mobile Station.
MAP
Control plane
CAP
TCAP
SCCP
MTP3
MTP2
E1/T1

Gi
Between
Back to general map
Node Node
External
Gi GGSN
network
The Gi interface connects the GGSN to an external Packet Data Network DHCP, RADIUS

DHCP / Radius
UDP
IPSec/GRE
IP
AAL5
ATM
L1 Ethernet

Gn
Between Back to general map
Node Node
This interface is used to support mobility between the SGSN and GGSN. The Gn
SGSN, interface is used when GGSN and SGSN are located inside one PLMN. The Gn interface
Gn SGSN
GGSN also includes a part which allows SGSNs to communicate subscriber and user data,
GTP
when changing SGSN.

GTP-C GTP-U
UDP
IPSec/GRE
IP
AAL5
ATM
L1 Ethernet

GpBetween Back to general map
Node Node
Gp SGSN GGSN Same as Gn interface but between Home SGSN and other PLMN GSN. GTP

GTP-C GTP-U
UDP
IPSec/GRE
IP
AAL5
ATM
L1 Ethernet

Gr
Between
Back to general map
Node Node
This interface is used to exchange the data related to the location of the mobile station Back to SAE/LTE map
subscriber is the capability to transfer packet data within the whole service area. The
SGSN informs the HLR of the location of a mobile station managed by the latter. The
Gr SGSN HLR
HLR sends to the SGSN all the data needed to support the service to the mobile
MAP
subscriber. Exchanges of data may occur when the mobile subscriber requires a
particular service, when he wants to change some data attached to his subscription or
when some parameters of the subscription are modified by administrative means.
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b
SAAL-NNI
MTP2 AAL5
ATM
MTP1/L1 L1

Gs
Between
Back to general map
Node Node
The SGSN may send location information to the MSC/VLR via the optional Gs interface.
MSC, The SGSN may receive paging requests from the MSC/VLR via the Gs interface. The
Gs SGSN
VLR MSC/VLR may indicate to an SGSN, via the Gs interface, that an MS is engaged in a
BSSAP+
service handled by the MSC.
Control plane
BSSAP+
SCCP
MTP3 MTP3-b
SAAL-NNI
MTP2 AAL5
ATM
MTP1/L1 L1

Gom
Between
Back to general map
Node Node
O&M protocols
SGSN, The Gom interface connects the SGSN to Operation & Maintenance (O&M) equipment in
Gom OSS
GGSN the O&M network, making it possible for an operator to communicate with the SGSN.
(FTP, SSH, HTTP,
etc)

Mub, Mur, Mut
Between
Back to general map
Interface
((
Node Node
Mub OSS RNC O&M interface for RBS (between RBS and WCDMA OSS) -
Mur OSS RBS O&M interface for RNC (between RNC and WCDMA OSS) -
Mut OSS RXI O&M interface for HUB-RXI (between HUB-RXI and WCDMA OSS) -

HI3
Between
Back to general map
Node Node
HI3 MGW LEMF Restricted information -

Iub
Between
Back to general map
Node Node
When the RNS consists of a Radio Network Controller (RNC) and one or more Node B, Back to SAE/LTE map
this interface is used between the RNC and Node B to support the services offered to the
UMTS users and subscribers.
Iub RNC RBS
The interface also allows control of the radio equipment and radio frequency allocation in
NBAP
the Node B.
The interface is specified in the 25.43x series of Technical Specifications.
Control plane User plane Transport Control plane

NBAP Iu FP Q.2630.1
SAAL-UNI SAAL-UNI
AAL5 AAL2 AAL5
ATM
L1

IuCS
Between
Back to general map
Node Node
The RNS-MSC interface is used to carry information concerning:

- RNS management;
IuCS MSC RNC
- Call handling;
RANAP
- Mobility management.

RANAP Iu UP Q.2630.1
SCCP
MTP3-B MTP3-B
SAAL-NNI AAL-2 SAR SSCS SAAL-NNI
AAL5 AAL2 AAL5
ATM
L1

IuPS
Between Back to general map
Node Node
Back to SAE/LTE map

The IuPS interface between SGSN and RNS/BSS is used to carry information
concerning:
IuPS SGSN RNC
- Packet data transmission;
RANAP, GTP-U
- Mobility management.

RANAP GTP-U
SCCP
MTP3-B UDP
SAAL-NNI IP
AAL5
ATM
L1

Iur
Between
Back to general map
Node Node
The Iur interface provides capability to support radio interface mobility between RNSs, of
UEs having a connection with
Iur RNC RNC
UTRAN. This capability includes the support of handover and radio resource handling
RNSAP
between RNSs.

RNSAP Iu FP Q.2630.1
SCCP
MTP3-B MTP3-B
SAAL-NNI SAAL-NNI
AAL5 AAL2 AAL5
ATM
L1

Lc, Lg, Lh Between
Back to general map
Interface
((
Node Node
gsmS
Lc GMLC
CF
This interface is used to get location information for CAMEL based services GMLC
This interface is used by the GMLC to convey a location request to the MSC or SGSN
MSC,
Lg GMLC
SGSN
currently serving a particular target UE whose location was requested. The interface is MAP
used by the MSC or SGSN to return location results to the GMLC.
This interface is used by the GMLC to request the address of the visited MSC or SGSN
Lh GMLC HLR
for a particular target UE whose location has been requested
MAP
Control plane
MAP
TCAP
SCCP
MTP3
MTP2
MTP1/L1

MbBetween Back to general map
Node Node
Via the Mb reference point IPv6 network services are accessed. These IPv6 network
services are used for user data transport. Note, that GPRS provides IPv6 network
Mb MGW IMS
services to the UE, i.e. the GPRS Gi reference point and the IMS Mb reference point may
RTP, RTCP
be the same.

Mc
Between
Back to general map
Node Node
Mc describes the interfaces between MSC server and M-MGW and between GMSC
Mc MSC MGW
server and M-MGW.
GCP (H.248)
Control plane
GCP
MTP3-b M3UA
SAAL-NNI
AAL5 SCTP
ATM
L1 IP

Mg Between
Back to general map
Node Node
The Mg reference point allows the MGCF to forward incoming session signalling (from
the circuit switched network) to the CSCF for the purpose of interworking with circuit
MSC switched networks.
Mg (MGCF)
CSCF
The protocol used for the Mg reference point is SIP (as defined by RFC 3261 [61],
SIP
other relevant RFC's, and additional enhancements introduced to support 3GPP´s
needs).
Control plane
SIP
TCP SCTP UDP
IP

Mj Between
Back to general map
Node Node
This reference point allows the Breakout Gateway Control Function to exchange
MSC
Mj (MGCF)
BGCF session signalling message with the Media Gateway Control Function for the SIP
purpose of interworking to the circuit switched networks, or for transit scenarios.
Control plane
SIP
TCP SCTP UDP
IP

Mn Between
Back to general map
Node Node
This interface provides the Media Gateway Control for interworking between the IP
MSC
Mn (MGCF)
MGW Multimedia Subsystem (IMS) and CS domain (ISUP, BICC and SIP-I). 3GPP TS GCP (H.248)
29.332
Control plane
GCP
MTP3-b M3UA
SAAL-NNI
AAL5 SCTP
ATM
L1 IP

Nb
Between
Back to general map
Node Node
Interface between two Media Gateways for user plane and control of user plane
Nb MGW MGW
connections used for circuit switched services.
Q.AAL2, AAL2

Q.2630.2 I.366.2
MTP3-B
SAAL-NNI
AAL5 AAL2
ATM
L1

Nc
Between
Back to general map
Node Node
Control plane interface between MSC/GMSC Servers used for circuit switched services
MSC,
Nc MSC
TSC
using BICC signaling based on ATM or IP transmission or ISUP signaling based on TDM BICC
transmission.
Control plane
BICC ISUP
MTP3-B M3UA MTP3
SAAL-NNI
AAL5 SCTP MTP2
ATM
L1 IP MTP1/L1

UmBetween
Back to general map
Node Node
Back to SAE/LTE map

The interface between the UE and the BSS is specified in the 24-, 44- and 45-series of
Um BTS MS
3GPP Technical Specifications.
RR, MM, CM
Control plane
RR / MM / CM
LAPDm
L1

Uu
Between
Back to general map
Node Node
The Uu interface is used to communicate among the UE Positioning entities associated Back to SAE/LTE map
with the SRNC, the UEs and the stand-alone LMU. The Uu interface may pass
measurement requests and results to and from the UE or the stand-alone LMU. UE
Uu RBS UE
Positioning operations at the Uu interface are generally defined in the 24- and 25-series
PDCP
of 3GPP Technical Specifications. Furthermore, 25.305 describes how a stand-alone
LMU may be distinguished from a normal UE.
User plane
PDCP
RLC
MAC
L1

X1, X2 Between
Back to general map
Interface
((
Node Node
X1 MSC LI-IMS Restricted information -
X2 MSC LI-IMS Restricted information -

S1-MME Between
Node Node
Back to SAE/LTE map

The eNBs are connected by means of the S1 interface to the EPC (Evolved Packet
eNode
S1-MME B
MME Core), more specifically to the MME (Mobility Management Entity) by means of the S1- S1-AP
MME related to control plane traffic.
– Over the S1 interface the S1AP protocol is, e.g., used to: Control plane
• Facilitate a set of general E-UTRAN procedures from the S1-AP
EPC such as paging-notification as defined by the SCTP
notification SAP. IP
• Separate each User Equipment (UE) on the protocol level L2
for mobile specific signalling management as defined by the L1
dedicated SAP.
3GPP TS 36.41x
• Transfer of transparent non-access signalling as defined in
the dedicated SAP. 3GPP TS 24.301
• Request of various types of E-RABs through the dedicated
SAP.
• Perform the mobility function.

S1-U Between
Node Node
Back to SAE/LTE map

The eNBs are connected by means of the S1 interface to the EPC (Evolved Packet
eNode
S1-U B
S-GW Core), more specifically to the Serving GW by means of the S1-U related to user plane GTPv2-C
traffic.
GTP tunnels are used between two nodes communicating over a GTP User plane
based interface, to separate traffic into different communication flows.
A GTP tunnel is identified in each node with a TEID, an IP address and a GTP-U
UDP port number. The receiving end side of a GTP tunnel locally assigns UDP
the TEID value the transmitting side has to use. The TEID values are
exchanged between tunnel endpoints using GTP-C or S1-MME messages. IP
The criteria defining when the same or different GTP tunnels shall be used L2
between the two nodes differs between the control and the user plane, and
also between interfaces. L1
For the control plane, for each end-point of a GTP-C tunnel:
• The TEID-C shall be unique per PDN-Connection on GTP based S5 and S8 3GPP TS 29.274
interfaces. The same tunnel shall be shared for the control messages related
to all bearers associated to the PDN-Connection. A TEID-C on the S5/S8
interface shall be released after all its associated EPS bearers are deleted.
• There shall be only one pair of TEID-Cs per UE on each of the S3, S10 and
the S16 interfaces. The same tunnel shall be shared for the control messages
related to the same UE operation. A TEID-C on the S3/S10/S16 interface shall
be released after its associated UE context is removed or the UE is detached.
• There shall be only one pair of TEID-C per UE over the S11 and the S4
interfaces. The same tunnel shall be shared for the control messages related
to the same UE operation. A TEID-C on the S11/S4 interface shall be released
after all its associated EPS bearers are deleted
For GTP-U, a TEID-U is used according to 3GPP TS 29.281 [13].
NOTE: GTP-U is based on GTP version 1 (GTPv1).

SGs
Between
Node Node
It is the reference point between the MME and MSC server. The SGs reference point is Back to SAE/LTE map
used for the mobility management and paging procedures between EPS and CS
domain, and is based on the Gs interface procedures. The SGs reference point is also
used for the delivery of both mobile originating and mobile terminating SMS. Additional
procedures for alignment with the Gs reference point are not precluded.
SGs MSC MME SGsAP (BSSAP+)
The SGs interface is used to provide Fallback for Location Services (LCS) and Call
Independent Supplementary Services (SS).
The signalling on this interface uses SCTP.
Control plane
The SGs interface functionality is based on the SGsAP(BSSAP+)
mechanisms specified for the Gs interface SCTP
IP
L2
L1
3GPP TS 23.272

SvBetween
Node Node
Back to SAE/LTE map

The interface provides SRVCC support for functions like sending Forward Relocation
Sv MSC MME
Message between MME or SGSN and 3GPP MSC Server.
GTPv2-C
Control plane
GTP
UDP
IP
L2
L1
3GPP TS 29.280
3GPP TS 23.216
3GPP TS 29.274

S6a
Between
Node Node
MME informs the HSS of the location of a mobile station managed by the latter. The
HLR/H
S6a MME
SS
HSS sends to the MME all the data needed to support the service to the mobile Diameter
Signalling on this interface uses Diameter S6a/S6d Application
Control plane
Diameter
SCTP
IP
L2
L1
3GPP TS 29.272
3GPP TS 23.401

S6d
Between
Node Node
SGSN informs the HSS of the location of a mobile station managed by the latter. The
HLR/H
S6d SGSN
SS
HSS sends to the SGSN all the data needed to support the service to the mobile Diameter
Signalling on this interface uses Diameter S6a/S6d Application
Control plane
Diameter
SCTP
IP
L2
L1
3GPP TS 29.272
3GPP TS 23.401

S11
Between
Node Node
Back to SAE/LTE map

This interface is used to support mobility and bearer management between the MME
S11 MME S-GW
and S-GW
GTPv2-C
Control plane
GTP
UDP
IP
L2
L1
3GPP TS 29.274

S10
Between
Node Node
Back to SAE/LTE map

This interface is used to support user information transfer and MME relocation support
S10 MME MME
between the MMEs.
GTP
Control plane
GTP
UDP
IP
L2
L1
3GPP TS 29.274

S5, S8 Between
Node Node
Back to SAE/LTE map

These interfaces are between S-GW and PDN-GW, provides support for functions for
PDN-
S5/S8 S-GW
GW
packet data services towards end users during roaming and non-roaming cases (i.e. S8 GTPv2-C
is the inter PLMN variant of S5).
Control plane
GTP
UDP
IP
L2
L1
3GPP TS 29.274

S13
Between
Node Node
Back to SAE/LTE map

This interface is used between MME and EIR to exchange data, in order that the EIR can
S13 MME EIR
verify the status of the IMEI retrieved from the Mobile Station
Diameter
Control plane
Diameter
SCTP
IP
L2
L1
3GPP TS 29.272

S3
Between
Node Node
Back to SAE/LTE map

This interface enables user and bearer information exchange for inter 3GPP access
S3 SGSN MME
network mobility in idle and/or active state
GTPv2-C
Control plane
GTP
UDP
IP
L2
L1
3GPP TS 29.274

S4
Between
Node Node
Back to SAE/LTE map

This interface provides related control and mobility support between GPRS Core and the
S4 SGSN S-GW 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not established, it GTPv2-C
provides the user plane tunnelling
Control plane
GTP
UDP
IP
L2
L1
3GPP TS 29.274

S12
Between
Node Node
Interface between UTRAN and Serving GW for user plane tunnelling when Direct Tunnel Back to SAE/LTE map
is established. It is based on the Iu-u/Gn-u reference point using the GTP-U protocol as
S12 S-GW RNC
defined between SGSN and UTRAN or respectively between SGSN and GGSN. Usage
GTPv2-C
of S12 is an operator configuration option
User plane
GTP-U
UDP
IP
L2
L1
3GPP TS 29.274

S2a, S2b, S2c Between
Node Node
Back to SAE/LTE map

Non-
PDN- It provides the user plane with related control and mobility support between trusted non
S2a 3GPP
GW 3GPP IP access and the Gateway
access
Non-
S2b
PDN-
3GPP It provides the user plane with related control and mobility support between ePDG and
GW
access
the Gateway. It’s related to non trusted non-3GPP access
It provides the user plane with related control and mobility support between UE and the
S2c
PDN-
UE Gateway. This reference point is implemented over trusted and/or untrusted non-3GPP
GW
Access and/or 3GPP access.
IPv4/IPv6 IPv4
PMIPv6 PMIPv4
Tunneling Tunneling
IPv4/IPv6 IPv4
L2
L1
3GPP TS 29.275
3GPP TS 23.402

S6b
Between
Node Node
It is the interface between PDN GW and 3GPP AAA server/proxy for mobility related Back to SAE/LTE map
authentication and authorization. This interface may also be used to retrieve and request
PDN-
S6b GW
AAA storage of mobility parameters, such as the PDN GW Identity. It may also be used to Diameter
retrieve static QoS profile for a UE for non-3GPP access in case dynamic PCC is not
supported
The S6b reference point shall be based on

Diameter, as defined in IETF RFC 3588 [7] and Control plane
contain the following additions and extensions: Diameter
SCTP
– IETF RFC 4005, which defines a Diameter IP
protocol application used for Authentication, L2
Authorization and Accounting (AAA) services in L1
the Network Access Server (NAS) environment.
– IETF Draft draft-korhonen-dime-pmip6 , which 3GPP TS 29.273
defines a Diameter extensions and application 3GPP TS 23.402
for PMIPv6 MAG to AAA and LMA to AAA
interfaces.
– IETF Draft draft-ietf-dime-qos-attributes , which
defines attribute value pairs to convey QoS
information between Diameter peers.

SWa, STa Between
Node Node
Non- Back to SAE/LTE map

trusted It enables support for the Untrusted non-3GPP IP Access with the 3GPP AAA
SWa non- AAA Server/Proxy and transports access authentication, authorization and charging-related Diameter
3GPP information in a secure manner
access
Truste
It connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and
d non-
STa 3GPP
AAA transports access authentication, authorization, mobility parameters and charging-related Diameter
information in a secure manner
access
Control plane
Diameter
SCTP
IP
L2
L1
3GPP TS 29.273
3GPP TS 23.402

SWn
Between
Node Node
Non- Back to SAE/LTE map

trusted
This is the reference point between the Untrusted Non-3GPP IP Access and the ePDG.
SWn non- ePDG
Traffic on this interface for a UE-initiated tunnel has to be forced towards ePDG
Diameter
3GPP
access
Control plane
Diameter
SCTP
IP
L2
L1
3GPP TS 29.273
3GPP TS 23.402

SGi
Between
Node Node
Back to SAE/LTE map

Interface between the PDN-GW and a packet data network. It may be an operator
PDN- Ext
SGi GW PDN
external public or private packet data network or an intra operator packet data network, -
e.g. for provision of IMS services
3GPP TS 29.061

X2
Between
Node Node
Back to SAE/LTE map

eNode eNode This is a logical interface between two eNBs. Whilst logically representing a point to point
X2 B B link between eNBs, the physical realization need not be a point to point link
X2AP
– The list of functions on the X2 interface is the

Control plane
following:
X2-AP
• Intra LTE-Access-System Mobility Support for ECM-
CONNECTED UE: SCTP
– Context transfer from source eNB to target eNB IP
– Control of user plane transport bearers between source eNB and
target eNB
L1
– Handover cancellation
– UE context release in source eNB
• Load Management
• Inter-cell Interference Coordination
– Uplink Interference Load Management
• General X2 management and error handling functions:
– Error indication
– Reset
• Application level data exchange between eNBs
• Trace functions

BSC Back to general map
Node Description
The Base Station Controller (BSC) area is an area of radio coverage consisting of one or more cells Back to SAE/LTE map
controlled by one BSC. The boundaries of a BSC area and a location area are independent; a
Base Station Controller location area may span the boundary between BSC area and a BSC area may span the boundary
between location areas

RNC Back to general map
Node Description
The Radio Network Controller (RNC) area is an area of radio coverage consisting of one or more cells Back to SAE/LTE map
Radio Network controlled by one RNC. The boundaries of a RNC area and a location area are independent; a
Controller location area may span the boundary between RNC area and a RNC area may span the boundary
between location areas

HSS Back to general map
Node Description
The HSS is the master database for a given user. It is the entity containing the subscription-related Back to SAE/LTE map
information to support the network entities actually handling calls/sessions.
A Home Network may contain one or several HSSs: it depends on the number of mobile subscribers,
on the capacity of the equipment and on the organisation of the network.
As an example, the HSS provides support to the call control servers in order to complete the
routing/roaming procedures by solving authentication, authorisation, naming/addressing resolution,
location dependencies, etc.
The HSS is responsible for holding the following user related information:
- User Identification, Numbering and addressing information;
- User Security information: Network access control information for authentication and authorization;
- User Location information at inter-system level: the HSS supports the user registration, and stores
inter-system location information, etc.;
- User profile information.
The HSS also generates User Security information for mutual authentication, communication integrity
Home Subscriber Server check and ciphering.
The HSS may integrate heterogeneous information, and enable enhanced features in the core
network to be offered to the application & services domain, at the same time hiding the heterogeneity.
The HSS consists of the following functionalities:
- IP multimedia functionality to provide support to control functions of the IM subsystem such as the
CSCF. It is needed to enable subscriber usage of the IM CN subsystem services. This IP multimedia
functionality is independent of the access network used to access the IM CN subsystem.
- The subset of the HLR/AUC functionality required by the PS Domain (GPRS and EPC).
- The subset of the HLR/AUC functionality required by the CS Domain, if it is desired to enable
subscriber access to the CS Domain or to support roaming to legacy GSM/UMTS CS Domain
networks

HLR Back to general map
Node Description
The HLR can be considered a subset of the HSS that holds the following functionality: Back to SAE/LTE map
- The functionality required to provide support to PS Domain entities such as the SGSN, MME and
GGSN, through the Gr, S6a, S6dand Gc interfaces and the 3GPP AAA Server for EPS in case of non-
3GPP access via SWx and for the I-WLAN through the D'/Gr' interface. It is needed to enable
Home Location Register subscriber access to the PS Domain services.
- The functionality required to provide support to CS Domain entities such as the MSC/MSC server
and GMSC/GMSC server, through the C and D interfaces. It is needed to enable subscriber access to
the CS Domain services and to support roaming to legacy GSM/UMTS CS Domain networks

AUC Back to general map
Node Description
The AuC can be considered a subset of the HSS that holds the following functionality for the CS
Domain and PS Domain:
- The AuC is associated with an HLR and stores an identity key for each mobile subscriber registered
with the associated HLR. This key is used to generate security data for each mobile subscriber:
- data which are used for mutual authentication of the International Mobile Subscriber Identity (IMSI)
and the network;
- a key used to check the integrity of the communication over the radio path between the mobile
Authentication Centre station and the network;
- a key used to cipher communication over the radio path between the mobile station and the network.
- The AuC communicates only with its associated HLR over a non-standardised interface denoted the
H-interface. The HLR requests the data needed for authentication and ciphering from the AuC via the
H-interface, stores them and delivers them to the VLR and SGSN and MME which need them to
perform the security functions for a mobile station

VLR Back to general map
Node Description
A mobile station roaming in an MSC area or within a GERAN/UTRAN pool-area is controlled by a Back to SAE/LTE map
Visitor Location Register. When a Mobile Station (MS) enters a new location area it starts a
registration procedure. An MSC in charge of that area notices this registration and transfers to a
Visitor Location Register the identity of the location area where the MS is situated. If this MS is not yet
registered in the VLR, the VLR and the HLR exchange information to allow the proper handling of CS
calls involving the MS.
A VLR may be in charge of one or several MSC areas.
The VLR contains also the information needed to handle the calls set-up or received by the MSs
registered in its data base (for some supplementary services the VLR may have to obtain additional
information from the HLR). The following elements are included:
Visitor Location - the International Mobile Subscriber Identity (IMSI);

- the Mobile Station International ISDN number (MSISDN);
Register
- the Mobile Station Roaming Number (MSRN), see TS 23.003 [3] for allocation principles;
- the Temporary Mobile Station Identity (TMSI), if applicable;
- the Local Mobile Station Identity (LMSI), if used;
- the location area where the mobile station has been registered;
- the identity of the SGSN where the MS has been registered. Only applicable to PLMNs supporting
GPRS and which have a Gs interface between MSC/VLR and SGSN;
- the last known location and the initial location of the MS;
- the identity of the MME where the MS has been registered. Only applicable to PLMNs supporting
EPC and CS Fallback and which have a SGs interface between MSC/VLR and MME

EIR Back to general map
Node Description
The Equipment Identity Register (EIR) in the GSM system is the logical entity which is responsible for Back to SAE/LTE map
storing in the network the International Mobile Equipment Identities (IMEIs), used in the
GERAN/UTRAN/E-UTRAN system.
The equipment is classified as "white listed", "grey listed", "black listed" or it may be unknown as
Equipment Identity specified in TS 22.016 [2] and TS 29.002].
Register This functional entity contains one or several databases which store(s) the IMEIs used in the system.
The mobile equipment may be classified as "white listed", "grey listed" and "black listed" and therefore
may be stored in three separate lists.
An IMEI may also be unknown to the EIR.
An EIR shall as a minimum contain a "white list" (Equipment classified as "white listed")

MSC Back to general map
Node Description
The Mobile-services Switching Centre (MSC) constitutes the interface between the radio system and Back to SAE/LTE map
the fixed networks. The MSC performs all necessary functions in order to handle the circuit switched
services to and from the mobile stations.
In order to obtain radio coverage of a given geographical area, a number of BSS and/or RNS are
normally required; i.e. each MSC would thus have to interface to one or more BSS(s) and/or RNS(s).
In addition several MSCs may be required to cover a country.
When Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied, all the MSCs serving
Mobile Switching Centre a pool-area share the responsibility to serve the MSs located in the pool-area. All these MSCs
interface to all the BSS(s) and/or RNS(s) forming the pool-area.
The Mobile-services Switching Centre is an exchange, which performs all the switching and signalling
functions for mobile stations located in a geographical area designated as the MSC area. When Intra
Domain Connection of RAN Nodes to Multiple CN Nodes is applied, one or more MSCs serve a pool-
area, but each individual MS is served by only one out of these MSCs, as described in TS 23.236 .
The main difference between a MSC and an exchange in a fixed network is that the MSC has to take
into account the impact of the allocation of radio resources and the mobile nature of the subscribers
and has to perform in addition
Node Description
The MSC Server mainly comprises the call control (CC) and mobility control parts of a MSC.
The MSC Server is responsible for the control of mobile originated and mobile terminated CC CS
Domain calls. It terminates the user-network signalling and translates it into the relevant network –
network signalling. The MSC Server also contains a VLR to hold the mobile subscriber's service data
and CAMEL related data.
The MSC Server controls the parts of the call state that pertain to connection control for media
channels in a CS-MGW.
An MSC Server which has been enhanced for SRVCC provides the following functions as needed for
support of SRVCC according to TS 23.216:
MSC Server - Handling the Relocation Preparation procedure requested for the voice component from MME via Sv
interface;
- Invoking the session transfer procedure from IMS to CS ;
- Coordinating the CS Handover and session transfer procedures;
- Handling the MAP_Update_Location procedure without it being triggered from the UE.
If a MSC Server is enhanced for IMS Centralized Services (as defined in TS 23.292), it is responsible
for the CS to IMS interworking, and it terminates the user-network signalling received over the CS
access (A/Iu and E interface) and translates it into SIP signalling in IMS and vice versa

GMSC Back to general map
Node Description
If a network delivering a call to the PLMN cannot interrogate the HLR, the call is routed to an MSC.
This MSC will interrogate the appropriate HLR and then route the call to the MSC where the mobile
station is located. The MSC which performs the routing function to the actual location of the MS is
Gateway MSC called the Gateway MSC (GMSC).
The acceptance of an interrogation to an HLR is the decision of the operator.
The choice of which MSCs can act as Gateway MSCs is for the operator to decide (i.e. all MSCs or
some designated MSCs).

SGSN Back to general map
Node Description
The location register function in the SGSN stores two types of subscriber data needed to handle Back to SAE/LTE map
originating and terminating packet data transfer:
- subscription information:
- the IMSI;
- one or more temporary identities;
Serving GPRS Support
- zero or more PDP addresses.
Node
- location information:
- depending on the operating mode of the MS, the cell or the routeing area where the MS is
registered;
- the VLR number of the associated VLR (if the Gs interface is implemented);
- the GGSN address of each GGSN for which an active PDP context exists

GGSN Back to general map
Node Description
The location register function in the GGSN stores subscriber data received from the HLR and the
SGSN. There are two types of subscriber data needed to handle originating and terminating packet
data transfer:
- subscription information:
Gateway GPRS Support - the IMSI;
Node - zero or more PDP addresses.
- location information:
- the SGSN address for the SGSN where the MS is registered

MME
Node Description
MME is the control plane entity within EPS supporting functions as listed below. For detailed Back to SAE/LTE map
functional role of MME, see specifications TS 23.401, TS 23.402 and TS 36.300.
Mobility Management,
- NAS signalling and security;
- Inter CN node signalling for mobility between 3GPP access networks;
- Tracking Area list management;
- PDN GW and Serving GW selection;
- SGSN selection for handovers to 2G or 3G 3GPP access networks;
- Roaming ;
- Authentication;
- Bearer management functions including dedicated bearer establishment.
- Lawful Interception of signalling traffic.
In order to support 3GPP2 access, MME supports:
- HRPD access node selection and maintenance for handovers to HRPD;
- Transparent transfer of HRPD signalling messages and transfer of status information between E-
UTRAN and HRPD access;
Mobility Management The procedures for information transfer between the SGSN, the MME and the HSS are defined in TS
Entity 23.401 and TS 23.060.
The CS fallback enabled MME supports the following additional functions according to TS 23.272 :
- Deriving a VLR number and LAI out of the TAI
- Maintaining of SGs association towards MSC/VLR for EPS/IMSI attached UE
- Initiating IMSI detach at EPS detach
- Initiating paging procedure towards eNodeB when MSC pages the UE for CS services
- Supporting SMS procedures for CS Fallback.
- Support CS Fallback interface and related functions for 1xRTT CDMA access.
When the MME supports the interworking to 3GPP CS, the MME supports the following functions as
specified in TS 23.216:
- Performing the PS bearer splitting function by separating the voice PS bearer from the non-voice PS
bearers.
- Handling the non-voice PS bearers handover with the target cell as according to Inter RAT handover
procedure as defined in TS 23.401.
- Initiating the SRVCC handover procedure for handover of the voice component to the target cell.
- Coordinating PS handover and SRVCC handover procedures when both procedures are performed,
- support interworking and SRVCC related functions for 1xRTT CDMA access

Serving GW
Node Description
The Serving GW is the gateway which terminates the interface towards E-UTRAN. Back to SAE/LTE map
For each UE associated with the EPS, at a given point of time, there is a single Serving GW. For
detailed S-GW functions, see TS 23.401 [76] and TS 23.402.
Connectivity to a GGSN is not supported.
The functions of the Serving GW include:
- the local Mobility Anchor point for inter-eNodeB handover;
- Mobility anchoring for inter-3GPP mobility;
- ECM-IDLE mode downlink packet buffering and initiation of network triggered service request
procedure;
- Lawful Interception;
Serving GW - Packet routeing and forwarding;
- Transport level packet marking in the uplink and the downlink;
- Accounting on user and QCI granularity for inter-operator charging;
- A local non-3GPP anchor for the case of roaming when the non-3GPP IP accesses connected to the
VPLMN;
- Event reporting (change of RAT, etc.) to the PCRF;
- Uplink and downlink bearer binding towards 3GPP accesses as defined in TS 23.203;
- Uplink bearer binding verification with packet dropping of "misbehaving UL traffic";
- Mobile Access Gateway (MAG) functions if PMIP-based S5 or S8 is used;
- Support necessary functions in order for enabling GTP/PMIP chaining functions

PDN GW
Node Description
The PDN GW is the gateway which terminates the SGi interface towards the PDN. Back to SAE/LTE map
If a UE is accessing multiple PDNs, there may be more than one PDN GW for that UE, however a mix
of S5/S8 connectivity and Gn/Gp connectivity is not supported for that UE simultaneously.
The P GW provides PDN connectivity to both GERAN/UTRAN only UEs and E UTRAN capable UEs
using any of E UTRAN, GERAN or UTRAN. The P GW provides PDN connectivity to E UTRAN
capable UEs using E UTRAN only over the S5/S8 interface. The P¬GW may also provide PDN
connectivity to UEs using non-3GPP access networks with the procedures defined in TS 23.402.
For detailed PDN-GW functions, see TS 23.401 [76] and TS 23.402.
PDN GW functions include:
- Per-user based packet filtering (by e.g. deep packet inspection);
- Lawful Interception;
- UE IP address allocation;
- Transport level packet marking in the uplink and downlink, e.g. setting the DiffServ Code Point,
based on the QCI of the associated EPS bearer;
Packet Data Network - UL and DL service level charging, gating control, rate enforcement as defined in TS 23.203;
GW - UL and DL rate enforcement based on APN-AMBR;
- DL rate enforcement based on the accumulated MBRs of the aggregate of SDFs with the same GBR
QCI (e.g. by rate policing/shaping);
- DHCPv4 (server and client) and DHCPv6 (client and server) functions;
Additionally the PDN GW includes the following functions for the GTP-based S5/S8:
- UL and DL bearer binding as defined in TS 23.203;
- UL bearer binding verification;
The PDN GW functions also includes user plane anchor for mobility between 3GPP access and non-
3GPP access. It supports:
- A LMA function, if PMIP-based S5 or S8, or if S2a or S2b is used;
- A DSMIPv6 Home Agent, if S2c is used;
- Allocation of GRE key, which is used to encapsulate uplink traffic to the PDN GW on the PMIP-
based S5/S8, or S2a or S2b interface;
- A MIPV4 Home Agent, if S2a with MIPv4 FA CoA mode is used

Non-3GPP Access
Node Description
Trusted and Untrusted Non-3GPP Access Networks are IP access networks that use access Back to SAE/LTE map
technology whose specification is out of the scope of 3GPP.
Whether a Non-3GPP IP access network is Trusted or Untrusted is not a characteristic of the access
network.
In non-roaming scenario it is the HPLMN's operator decision if a Non-3GPP IP access network is
used as Trusted or Untrusted Non-3GPP Access Network.
In roaming scenario, the HSS/3GPP AAA Server in HPLMN makes the final decision of whether a
Non-3GPP IP access network is used as Trusted or Untrusted non-3GPP Access Network. The
HSS/3GPP AAA Server may take the VPLMN's policy and capability returned from the 3GPP AAA
Proxy or roaming agreement into account

ePDG
Node Description
The functionality of ePDG includes the following: Back to SAE/LTE map

- Functionality defined for the PDG in TS 23.234 for the allocation of a remote IP address as an IP
address local to the ePDG which is used as CoA when S2c is used;
- Functionality for transportation of a remote IP address as an IP address specific to a PDN when S2b
is used;
- Routing of packets from/to PDN GW (and from/to Serving GW if it is used as local anchor in VPLMN)
to/from UE;
- De-capsulation/Encapsulation of packets for IPSec and PMIP tunnels (the latter only if network
Evolved Packet Data based mobility (S2b) is used);
Gateway - Mobile Access Gateway (MAG) if network based mobility (S2b) is used;
- Tunnel authentication and authorization (termination of IKEv2 signalling and relay via AAA
messages);
- Local mobility anchor within untrusted non-3GPP access networks using MOBIKE (if needed);
- Transport level packet marking in the uplink;
- Enforcement of QoS policies based on information received via AAA infrastructure;
- Lawful Interception

AAA Server
Node Description
The 3GPP AAA Server is located at the HPLMN and provides support for non-3GPP Access users Back to SAE/LTE map
with services like Authentication, Authorisation and location management services in order to get
Authentication access to EPS. It also contains necessary user related information in order to grant access to non-
3GPP access. It also coordinates the information needed to support mobility between 3GPP and non-
Authorization 3GPP accesses such as coordination of PDN-GW information. It interacts with HSS to maintain
consistent information for users supporting mobility and service continuity between 3GPP and non-
3GPP access. For details, see TS 23.402

MS Back to general map
Node Description
The mobile station consists of the physical equipment used by a PLMN subscriber; it comprises the Back to SAE/LTE map
Mobile Equipment (ME) and the Subscriber Identity Module (SIM), called UMTS Subscriber Identity
Mobile Station Module (USIM) for Release 99 and following. The ME comprises the Mobile Termination (MT) which,
depending on the application and services, may support various combinations of Terminal Adapter
(TA) and Terminal Equipment (TE) functional groups

UE Back to general map
Node Description
The User Equipment Allows a user access to network services. For the purpose of 3GPP Back to SAE/LTE map
specifications the interface between the UE and the network is the radio interface. A User Equipment
can be subdivided into a number of domains, the domains being separated by reference points.
User Equipment Currently the User Equipment is subdivided into the UICC domain and the ME Domain. The ME
Domain can further be subdivided into one or more Mobile Termination (MT) and Terminal Equipment
(TE) components showing the connectivity between multiple functional groups

GMLC Back to general map
Node Description
Gateway Mobile The Gateway Mobile Location Centre (GMLC) is the first node an external Location Application
accesses in the GSM PLMN. The GMLC performs registration authorization and requests routing
Location Centre information from the HLR. There may be more than one GMLC in a PLMN

gsmSCF Back to general map
Node Description
GSM Service Control A functional entity that contains the CAMEL service logic to implement Operator Specific Service. It
Function interfaces with the gsmSSF, the gsmSRF and the HLR

gsmSSF Back to general map
Node Description
GSM Service Switching A functional entity that interfaces the MSC/GMSC to the gsmSCF. The concept of the gsmSSF is
derived from the IN SSF, but uses different triggering mechanisms because of the nature of the
Function mobile network

gsmSRF Back to general map
Node Description
GSM Specialised A functional entity which provides various specialized resources. It interfaces with the gsmSCF and
Resource Function with the MSC. This entity is defined in ITU T Q.1214 with variations defined in TS 23.078

CSCF Back to general map
Node Description
The CSCF can act as Proxy CSCF (P CSCF), Serving CSCF (S CSCF), Emergency CSCF (E CSCF),
or Interrogating CSCF (I CSCF). The P CSCF is the first contact point for the UE within the IM
Call Session Control subsystem (IMS); the S CSCF actually handles the session states in the network; the E CSCF
handles certain aspects of emergency sessions such as routing an emergency request to the correct
Function emergency centre or PSAP; the I CSCF is mainly the contact point within an operator's network for all
IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently
located within that network operator's service area

MGCF Back to general map
Node Description
The MGCF:
- Controls the parts of the call state that pertain to connection control for media channels in an IMS-MGW.
Media Gateway Control - Communicates with CSCF, BGCF, and circuit switched network entities.
Function - Determines the next hop depending on the routing number for incoming calls from legacy networks.
- Performs protocol conversion between ISUP/TCAP and the IM subsystem call control protocols.
- Out of band information received in MGCF may be forwarded to CSCF/IMS-MGW

MRFC Back to general map
Node Description
The MRFC:
- Controls the media stream resources in the MRFP.
Multimedia Resource
- Interprets information coming from an AS and S CSCF (e.g. session identifier) and control MRFP accordingly.
Function Controller
- Generates CDRs .

MRFP Back to general map
Node Description
The MRFP:
- Controls bearers on the Mb reference point.
- Provides resources to be controlled by the MRFC.
Multimedia Resource - Mixes incoming media streams (e.g. for multiple parties).
Function Processor - Sources media streams (for multimedia announcements).
- Processes media streams (e.g. audio transcoding, media analysis).
- Floor Control (i.e. manage access rights to shared resources in a conferencing environment).

PCRF
Node Description
The Policy and Charging Rules Function (PCRF) acts as a policy decision point for policy and Back to SAE/LTE map
charging control of service data flows and IP bearer resources. The PCRF selects and provides the
applicable policy and charging control decision to the PCEF.
When Gxx interface applies, the PCRF maintains the correlation between the GW control session and
the IP-CAN session. The PCRF also acts as an information exchange point between BBERF and
PCEF to forward event triggers, which can't be transferred directly between the BBERF and PCEF
PCRF is the policy and charging control element. PCRF functions are described in more detail in TS
23.203.
Policy and Charging In non-roaming scenario, there is only a single PCRF in the HPLMN associated with one UE's IP-CAN
Rules Function session.
In a roaming scenario with local breakout of traffic and/or when a Gxx interface applies there are two
PCRFs associated with one UE's IP-CAN session:
- H-PCRF that resides within the H-PLMN;
- V-PCRF that resides within the V-PLMN.
A single logical PCRF entity may be deployed by means of multiple and separately addressable
PCRFs in the PLMN. In this case, the PCRF discovery and selection is enabled by Diameter Routing
Agency (DRA).

eNodeB
Node Description
An eNB is a logical network component which serves one or more E-UTRAN cells. Back to SAE/LTE map
The Evolved UTRAN (E-UTRAN) consists of eNBs, providing the E-UTRA user plane
(PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations towards the UE. The eNBs can
Enhanced Node B be interconnected with each other by means of the X2 interface. The eNBs are connected by means
of the S1 interface to the EPC (Evolved Packet Core), more specifically to the MME (Mobility
Management Entity) by means of the S1-MME and to the Serving Gateway (S-GW) by means of the
S1-U interface. The S1 interface supports a many-to-many relation between MMEs / Serving
Gateways and eNBs

BGCF Back to general map
Node Description
The Breakout Gateway control function (BGCF) determines the next hop for routing the SIP message.
This determination may be based on information received in the signalling protocol, administrative
Breakout Gateway information, and/or database access. For PSTN /CS Domain terminations, the BGCF determines the
Control Function network in which PSTN/CS Domain breakout is to occur and - within the network where the breakout
is to occur - selects the MGCF.
Details are described in TS 23.228

RBS Back to general map
Node Description
Back to SAE/LTE map

The RBS controls the radio interface to the MS/UE. The RBS comprises the radio equipment such as
Radio Base Station transceivers and antennas, which are needed to serve each cell in the network

OSS Back to general map
Node Description
Operation and Support Operation and Support System (OSS) is the system to support the activities performed in an OMC
and/or NMC. The network operator monitors and controls the network through OSS which offers cost
System effective support of centralized, regional and local operation and maintenance activities

MGW Back to general map
Node Description
The Media Gateway function operates on the user plane in order to enable interworking between
between different transport domain. The MSC Server controls the Media Gateway function. The
Media Gateway function has 2 functional layer:
Media Gateway - Media Stream provides the devices needed to manipulate the user data according to the circuit-
based service being used.
- Transport provides the switching of the user plane and bearer control for the interworking between
different transport domain

SCP Back to general map
Node Description
Mobile Intelligent function is used in conjunction with PLMN. It consists of services nodes that provide
Service Control Point advanced services to subscribers. The SCP node provide service logic functionality

SMS-C Back to general map
Node Description
Short Message Service The SMS-C receives, stores and forwards a short message between the messange sender and the
Centre mobile station

gsmSSF-gsmSCF Back to general map
Node Description
This interface is used by the gsmSCF to control a call in a certain gsmSSF and to request the
gsmSSF-gsmSCF gsmSSF to establish a connection with a gsmSRF. Relationships on this interface are opened as a
result of the gsmSSF sending a request for instructions to the gsmS
Control plane
CAP/INAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

gsmSCF-HLR Back to general map
Node Description
This interface is used by the gsmSCF to request information from the HLR. As a network operator
option the HLR may refuse to provide the information requested by the gsmSCF.
This interface is also used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated
gsmSCF-HLR dialogues (relayed via HLR). It is a network operator option whether to support or not USSD
operations on this interface
Control plane
MAP
TCAP
SCCP
MTP3 MTP3-b M3UA
SAAL-NNI
MTP2 AAL5 SCTP
ATM
MTP1/L1 L1 IP

Useful Links
Document title Web link
Technical Specification Group Services and Systems Aspects; Network Architecture 3GPP TS 23.002
Protocol Specification Survey 109 43-HSD 101 13/5
Ericsson Standardization and Industry Initiatives Standardization and Industry Initiatives

ITU-T ITU-T
IETF RFC page
3GPP 3GPP specs

ETSI ETSI specs
Ericsson Statement of Compliance 3GPP Ericsson SoCs
View publication stats

3GPP Interface Maps for 2G/3G and SAE/LTE Networks

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP Interface Maps for 2G/3G and SAE/LTE Networks

Uploaded by

Copyright:

Available Formats

See discussions, stats, and author profiles for this publication at: https://www.researchgate.

Mobile Interface 3GPP Interfaces description General map SAE/LTE

Book · January 2015

Performance Analysis of Link Adaptation in EUTRAN View project

Analysis of Handover of UE in EUTRAN View project

The user has requested enhancement of the downloaded file.

Mobile Interface - ankitsaxena Back to index

Mobile Interface - ankitsaxena Back to index

SGs S11 S2b ePDG

Mobile Interface - ankitsaxena Back to index

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Control plane User plane

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Control plane User plane

Mobile Interface - ankitsaxena

Control plane User plane

Mobile Interface - ankitsaxena

Control plane User plane

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

HI3 MGW LEMF Restricted information -

Mobile Interface - ankitsaxena

Control plane User plane Transport Control plane

Mobile Interface - ankitsaxena

The RNS-MSC interface is used to carry information concerning:

Control plane User plane Transport Control plane

Mobile Interface - ankitsaxena

Back to SAE/LTE map

Control plane User plane

Mobile Interface - ankitsaxena

Control plane User plane Transport Control plane

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Control plane User plane

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

Back to SAE/LTE map

Mobile Interface - ankitsaxena

Mobile Interface - ankitsaxena

X1 MSC LI-IMS Restricted information -

X2 MSC LI-IMS Restricted information -

Mobile Interface - ankitsaxena

Back to SAE/LTE map

• Perform the mobility function.