3GPP TS 23.002
3GPP TS 23.002
3GPP TS 23.002
3GPP TS 23.002
V15.0.0
Technical Specification Group Services and System (2018-03)
Aspects;
Network architecture
Technical Specification
(Release 15)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this
Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
Release 15 2 3GPP TS 23.002 V15.0.0 (2018-03)
Keywords
LTE, GSM, UMTS, network, architecture
3GPP
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
© 2018, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
3GPP
Release 15 3 3GPP TS 23.002 V15.0.0 (2018-03)
Contents
Foreword........................................................................................................................................................12
Introduction....................................................................................................................................................12
1 Scope....................................................................................................................................................13
2 References............................................................................................................................................13
3 Definitions and abbreviations...............................................................................................................19
3.1 Public Land Mobile Network (PLMN).............................................................................................................19
3.2 Core Network (CN) and Access Network (AN)................................................................................................19
3.3 Circuit Switched (CS) and Packet Switched (PS) Domains..............................................................................19
3.3.1 CS Domain...................................................................................................................................................20
3.3.2 PS Domain...................................................................................................................................................20
3.3a IP Multimedia subsystem (IMS)..................................................................................................................20
3.4 Location register................................................................................................................................................20
3.5 Cell.....................................................................................................................................................................21
3.6 Base Station Controller (BSC) area...................................................................................................................21
3.7 Radio Network Controller (RNC) area..............................................................................................................21
3.8 Location Area (LA)...........................................................................................................................................21
3.9 Routing Area (RA).............................................................................................................................................21
3.9a Tracking Area (TA)............................................................................................................................................21
3.10 MSC area...........................................................................................................................................................21
3.11 VLR area............................................................................................................................................................21
3.12 SGSN area.........................................................................................................................................................22
3.13 Zones for Regional Subscription.......................................................................................................................22
3.14 Service area........................................................................................................................................................22
3.15 Group call area...................................................................................................................................................22
3.15a MME Area.........................................................................................................................................................22
3.16 Pool-area............................................................................................................................................................22
3.17 Serving GW Service Area..................................................................................................................................22
4 The basic entities of the mobile system................................................................................................23
4.1 The Core Network (CN) entities.......................................................................................................................23
4.1.1 Entities common to the PS and CS domains................................................................................................23
4.1.1.1 The Home Subscriber Server (HSS)......................................................................................................23
4.1.1.1.1 The Home Location Register (HLR)................................................................................................24
4.1.1.1.2 The Authentication Centre (AuC).....................................................................................................24
4.1.1.1.3 HSS logical functions.......................................................................................................................25
4.1.1.2 The Visitor Location Register (VLR).....................................................................................................26
4.1.1.3 (void)......................................................................................................................................................27
4.1.1.4 The Equipment Identity Register (EIR).................................................................................................27
4.1.1.5 SMS Gateway MSC (SMS-GMSC).......................................................................................................27
4.1.1.6 SMS Interworking MSC (SMS-IWMSC)..............................................................................................27
4.1.1.7 Subscription Locator Function (SLF)....................................................................................................27
4.1.2 Entities of the CS domain............................................................................................................................28
4.1.2.1 The Mobile-services Switching Centre (MSC)......................................................................................28
4.1.2.1.1 MSC Server......................................................................................................................................28
4.1.2.1.2 Circuit Switched - Media Gateway Function (CS-MGW)...............................................................29
4.1.2.2 The Gateway MSC (GMSC)..................................................................................................................29
4.1.2.2.1 Gateway MSC Server (GMSC Server).............................................................................................29
4.1.2.3 The Interworking Function (IWF)..........................................................................................................29
4.1.3 Entities of the GPRS PS domain..................................................................................................................30
4.1.3.1 Serving GPRS Support Node (SGSN)...................................................................................................30
4.1.3.2 Gateway GPRS Support Node (GGSN).................................................................................................30
4.1.3.3 Void........................................................................................................................................................31
4.1.4 Entities of the EPC PS Domain....................................................................................................................31
3GPP
Release 15 4 3GPP TS 23.002 V15.0.0 (2018-03)
4.1.4.1 MME......................................................................................................................................................31
4.1.4.2 Gateways................................................................................................................................................32
4.1.4.2.1 Serving GW......................................................................................................................................32
4.1.4.2.2 PDN GW...........................................................................................................................................32
4.1.4.2.3 Local GW (L-GW)...........................................................................................................................33
4.1.4.3 SGSN......................................................................................................................................................33
4.1.4.4 Trusted and Untrusted Non-3GPP Access Network...............................................................................33
4.1.4.5 ePDG......................................................................................................................................................34
4.1.4.6 3GPP AAA Server..................................................................................................................................34
4.1.4.7 3GPP AAA Proxy...................................................................................................................................34
4.1.4.8 ANDSF...................................................................................................................................................34
4.1.5 Border Gateway (BG)].................................................................................................................................35
4.2 The Access Network (AN) entities....................................................................................................................35
4.2.1 The Base Station System (BSS)...................................................................................................................35
4.2.1.1 Base Station Controller (BSC)...............................................................................................................35
4.2.1.2 Base Transceiver Station (BTS).............................................................................................................36
4.2.2 The Radio Network System (RNS)..............................................................................................................36
4.2.2.1 Radio Network Controller (RNC)..........................................................................................................36
4.2.2.2 Node B....................................................................................................................................................36
4.2.3 Access Network elements for E-UTRAN....................................................................................................36
4.2.3.1 E-UTRAN Node B (eNB)......................................................................................................................36
4.2.3.2 Evolved UTRAN....................................................................................................................................36
4.3 The Mobile Station (MS)...................................................................................................................................36
4.4 User Equipment (UE)........................................................................................................................................37
4a The specific entities of the 3GPP system..............................................................................................37
4a.1 The Group Call Register (GCR) entity..............................................................................................................37
4a.2 (void).................................................................................................................................................................38
4a.3 The Location Services (LCS) entities................................................................................................................38
4a.3.1 Location Services (LCS) entities in RAN....................................................................................................38
4a.3.2 Gateway Mobile Location Centre (GMLC).................................................................................................39
4a.3.3 Location Measurement Unit (LMU)............................................................................................................39
4a.3.4 Evolved Serving Mobile Location Centre (E-SMLC).................................................................................39
4a.4 CAMEL entities.................................................................................................................................................40
4a.4.1 GSM Service Control Function (gsmSCF)..................................................................................................40
4a.4.2 GSM Service Switching Function (gsmSSF)..............................................................................................40
4a.4.3 GSM Specialised Resource Function (gsmSRF).........................................................................................40
4a.4.4 GPRS Service Switching Function (gprsSSF).............................................................................................40
4a.5 CBS-specific entities.........................................................................................................................................40
4a.5.1 Cell Broadcast Centre (CBC).......................................................................................................................40
4a.6 Number Portability Specific entities..................................................................................................................40
4a.6.1 IN-based solution: Number Portability Database (NPDB)..........................................................................40
4a.6.2 Signalling Relay-based solution: Mobile Number Portability/Signalling Relay function (MNP-SRF)
......................................................................................................................................................................41
4a.7 IP Multimedia (IM) Core Network (CN) Subsystem entities............................................................................41
4a.7.1 Call Session Control Function (CSCF)........................................................................................................41
4a.7.2 Media Gateway Control Function (MGCF).................................................................................................41
4a.7.3 IP Multimedia Subsystem - Media Gateway Function (IMS-MGW)..........................................................41
4a.7.4 Multimedia Resource Function Controller (MRFC)....................................................................................42
4a.7.4a Multimedia Resource Function Processor (MRFP).....................................................................................42
4a.7.4b Media Resource Broker (MRB)...................................................................................................................42
4a.7.5 Void..............................................................................................................................................................42
4a.7.6 Breakout Gateway Control Function (BGCF).............................................................................................42
4a.7.7 Application Server (AS)...............................................................................................................................43
4a.7.8 Interconnection Border Control Function (IBCF).......................................................................................43
4a.7.9 Transition Gateway (TrGW)........................................................................................................................43
4a.7.10 Location Retrieval Function (LRF)..............................................................................................................43
4a.7.11 Service Centralization and Continuity Application Server (SCC AS).........................................................44
4a.7.11a Emergency Access Transfer Function (EATF).............................................................................................44
4a.7.12 Access Transfer Control Function (ATCF)..................................................................................................44
4a.7.13 Access Transfer Gateway (ATGW).............................................................................................................44
4a.8 Signalling Gateway Function (SGW)................................................................................................................44
3GPP
Release 15 5 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 6 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 7 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 8 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 9 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 10 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 11 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 12 3GPP TS 23.002 V15.0.0 (2018-03)
Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
This document presents the possible architectures of the 3GPP System covering both UTRAN and GERAN radio access
technologies. In addition, this document also includes the Evolved Packet System providing support for E-UTRAN
radio access technology in addition to UTRAN and GERAN radio access technologies. As well as providing support for
E-UTRAN, UTRAN and GERAN radio access technologies, the Evolved Packet System also provides support for non-
3GPP access technologies making it possible for these technologies to interwork with the 3GPP specified Evolved
Packet Core network. The configuration of non-3GPP access networks using EPS is not within the scope of 3GPP
specification.
This document also presents the architecture for the IP Multimedia Subsystem common to 3GPP and other access
systems such as Fixed Broadband and those specified by 3GPP2 and provide architecture for interworking and session
continuity between IMS and Circuit Switched systems.
Clause 4 of the document contains the description of the basic entities of the PLMN, and clause 4a contains the
description of the specific entities of the PLMN.
Clauses 6, 6a and 7 of the document contain the PLMN's basic and specific interfaces and reference points and the
PLMN's interfaces towards other networks.
3GPP
Release 15 13 3GPP TS 23.002 V15.0.0 (2018-03)
1 Scope
This document offers an overview of the 3GPP PLMN and its architectures and configuration. The configuration and
the functional entities of the PLMN and the interfaces between them are described on a general level in order to cope
with possible implementations. These descriptions include interfaces between and within the core networks, the access
networks, the user equipment, different service platforms, different domains and subsystems, and functional entities
within domains and subsystems.
This document covers different architectural aspects with varying level of detail. In general, other specifications shall be
referred to for further details; these specifications enable the reader to acquire the full understanding of a system or
service feature.
Note that this document does not cover, or even list, all features of PLMNs.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] Void.
[2a] 3GPP TS 22.060: "General Packet radio Service (GPRS); Service description; Stage 1".
[2b] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1".
[2c] 3GPP TS 22.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL);
Service description, Stage 1".
[9] Void.
[9a] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[10] Void.
[10a] 3GPP TS 43.064: "Digital cellular telecommunication system (Phase 2+); General Packet Radio
service (GPRS); Overall description of the GPRS radio interface; Stage 2".
3GPP
Release 15 14 3GPP TS 23.002 V15.0.0 (2018-03)
[10c] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase
3 - Stage 2".
[11] ITU-T Recommendation Q.1214 (05/1995): "Distributed Functional Plane for Intelligent Network
CS-1".
[12] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference
configuration".
[13] 3GPP TS 48.001: "Base Station System - Mobile-services Switching Centre (BSS - MSC)
interface; General aspects".
[14] 3GPP TS 48.002: "Base Station System - Mobile-services Switching Centre (BSS - MSC)
interface; Interface principles".
[15] 3GPP TS 48.004: "Base Station System - Mobile-services Switching Centre (BSS - MSC)
interface Layer 1 specification".
[16] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System -
Mobile-services Switching Centre (BSS - MSC) interface".
[17] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS)
interface; Layer 3 specification".
[18] Void.
[19] 3GPP TS 48.051: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface;
General aspects".
[20] 3GPP TS 48.052: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface;
Interface principles".
[21] 3GPP TS 48.054: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface;
Layer 1 structure of physical circuits".
[22] 3GPP TS 48.056: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface;
Layer 2 specification".
[23] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface;
Layer 3 specification".
[24] 3GPP TS 48.060: "In-band control of remote transcoders and rate adaptors for full rate traffic
channels".
[25] 3GPP TS 48.061: "In-band control of remote transcoders and rate adaptors for half rate traffic
channels".
[27] 3GPP TS 22.228: "Service requirements for the IP Multimedia Core Network Subsystem".
[28] 3GPP TS 23.207: "End-to-end Quality of Service (QoS) concept and architecture".
[29] [void].
[30] [void].
3GPP
Release 15 15 3GPP TS 23.002 V15.0.0 (2018-03)
[31] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile
Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched
Telephone Network (PSTN)".
[32] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System
(MS – BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC);
Signalling procedures and the Mobile Application Part (MAP)".
[36] 3GPP TS 43.051: "Technical Specification Group GSM/EDGE Radio Access Network; Overall
description, Stage 2".
[40] 3GPP TS 23.066: "Support of Mobile Number Portability (MNP); Technical realization; Stage 2".
[41] 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2".
[43] 3GPP TS 23.205: "Bearer independent circuit switched core network; Stage 2".
[44] 3GPP TS 48.014: "Base Station System (BSS) – Serving GPRS Support Node (SGSN) interface;
Gb interface Layer 1".
[45] 3GPP TS 48.016: "Base Station System (BSS) – Serving GPRS Support Node (SGSN) interface;
Network service".
[46] 3GPP TS 48.018: "Base Station System (BSS) – Serving GPRS Support Node (SGSN); BSS
GPRS Protocol (BSSGP)".
[47] 3GPP TS 48.031: "Serving Mobile Location Centre – Serving Mobile Location Centre (SMLC –
SMLC); SMLCPP specification".
[48] 3GPP TS 29.016: "Serving GPRS Support Node (SGSN) – Visitor Location Register (VLR); Gs
interface network service specification".
[49] 3GPP TS 29.018: "Serving GPRS Support Node (SGSN) – Visitor Location Register (VLR); Gs
interface Layer 3 specification".
[50] 3GPP TS 49.031: "Network Location Services (LCS); Base Station System Application Part LCS
extension (BSSAP-LE)".
[51] 3GPP TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface".
[53] ITU-T Recommendation E.164: "The International public telecommunication numbering plan".
[55] 3GPP TS 44.071: "Mobile radio interface layer 3 Location Services (LCS) specification".
[57] ITU-T Recommendation I.363-2 :"B-ISDN ATM Adaptation Layer (AAL) type 2 specification".
3GPP
Release 15 16 3GPP TS 23.002 V15.0.0 (2018-03)
[60] IETF RFC 1889: "RTP: A Transport Protocol for Real-Time Applications".
[63] 3GPP TS 29.198: "Open Service Access (OSA) Application Programming Interface (API)".
[64] 3GPP TS 33.210: "3G Security; Network Domain Security; IP network layer security".
[65] 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes".
[66] 3GPP TS 25.453: "UTRAN Iupc interface Positioning Calculation Application Part (PCAP)
signalling".
[67] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking".
[70] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional
description".
[71] 3GPP TS 23.240: "3GPP Generic User Profile (GUP); Architecture (Stage 2)".
[72] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application
functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)".
[73] 3GPP TS 23.203: "Policy Control and Charging Architecture (Stage 2)".
[75] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol
(IP) access".
[76] 3GPP TS 23.401:"General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access".
[78] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[79] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture
description".
[80] Open Mobile Alliance, OMA ERP SUPL V2.0: "Secure User Plane Location Enabler Release
Package", (http://www.openmobilealliance.org).
[81] 3GPP TS 23.272: "Circuit Switched Fallback in Evolved Packet System; Stage 2".
[82] 3GPP TS 29.118: "Mobility Management Entity (MME) – Visitors Location Register (VLR) SGs
interface specification".
[83] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[84] 3GPP TS 33.107: "3G security; Lawful interception architecture and functions".
[86] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and
Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
3GPP
Release 15 17 3GPP TS 23.002 V15.0.0 (2018-03)
[88] 3GPP TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP
accesses".
[89] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS);
Stage 3".
[90] 3GPP TS 29.274: "General Packet Radio Service (GPRS); Evolved GPRS Tunnelling Protocol
(eGTP) for EPS".
[91] 3GPP TS 29.280: "Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN
to MSC) for SRVCC".
[93] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols;
Stage 3".
[94] 3GPP TS 24.304: "Mobility management based on Mobile IPv4; User Equipment (UE) - foreign
agent interface; Stage 3".
[95] 3GPP TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6; Stage 3".
[96] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
[97] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access
networks".
[98] 3GPP TS 29.168: "Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3".
[99] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[104] 3GPP TS 29.061: "Interworking between PLMN supporting packet based services and PDN".
[105] Void.
[106] 3GPP2 A.S0008-C: "Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
Radio Access Network Interfaces with Session Control in the Access Network".
[107] 3GPP2 C.S0087 0: "E-UTRAN - HRPD and CDMA2000 1x Connectivity and Interworking: Air
Interface Aspects".
[112] 3GPP TS 23.327: "Mobility between 3GPP-Wireless Local Area Network (WLAN) Interworking
and 3GPP Systems".
[113] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".
[114] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB); Stage 2".
3GPP
Release 15 18 3GPP TS 23.002 V15.0.0 (2018-03)
[115] 3GPP TS 25.468: "UTRAN Iuh Interface RANAP User Adaption (RUA) signalling".
[116] 3GPP TS 25.469: "UTRAN Iuh interface Home Node B (HNB) Application Part (HNBAP)
signalling".
[117] 3GPP TS 24.285: "Allowed Closed Subscriber Group (CSG) List; Management Object (MO)".
[118] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM)
application".
[119] 3GPP TS 48.049: "Base Station Controller - Cell Broadcast Centre (BSC-CBC) Interface
Specification; Cell Broadcast Service Protocol (CBSP)".
[120] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows;
Stage 2".
[121] 3GPP TS 29.335: "User Data Convergence (UDC); User Data Repository Access Protocol over the
Ud interface; Stage 3".
[122] 3GPP TS 36.305: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2
functional specification of User Equipment (UE) positioning in E-UTRAN".
[123] 3GPP TS 29.172: "Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP)
between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity
(MME); SLg interface".
[124] 3GPP TS 29.171: "Location Services (LCS); LCS Application Protocol (LCS-AP) between the
Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC); SLs
interface".
[125] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane
LCS".
[127] 3GPP TS 36.443: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M2
Application Protocol (M2AP)".
[128] 3GPP TS 36.444: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M3
Application Protocol (M3AP)".
[129] 3GPP TS 36.445: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 data
transport".
[130] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs".
[131] 3GPP TS 29.219: "Policy and charging control: Spending limit reporting over Sy reference point".
[132] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data
networks and applications".
[133] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with
packet data networks and applications".
[134] 3GPP TS 29.337: "Diameter based T4 Interface for communications with packet data networks
and applications".
[135] 3GPP TS 29.338: "Diameter based protocols to support of SMS capable MMEs".
[136] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF)
and Service Capability Server (SCS)".
[137] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[138] IETF RFC 793 (1981): "Transmission Control Protocol" (STD 7).
3GPP
Release 15 19 3GPP TS 23.002 V15.0.0 (2018-03)
[139] 3GPP TS 26.233: "Transparent end-to-end Packet-switched Streaming Service (PSS); General
Description".
[140] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[142] 3GPP TS 23.179: "Functional architecture and information flows to support mission critical
communication services; Stage 2".
[143] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and
interaction".
[144] 3GPP TS 26.141: "IP Multimedia System (IMS) Messaging and Presence; Media formats and
codecs".
[145] 3GPP TS 23.214: "Architecture enhancements for control and user plane separation of EPC nodes;
Stage 2".
[146] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[147] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
The definitions of the entities of the mobile system are given in the next clause.
Functionally the PLMNs may be regarded as independent telecommunications entities even though different PLMNs
may be interconnected through the ISDN/PSTN and PDNs for forwarding of calls or network information. A similar
type of interconnection may exist for the interaction between the MSCs/SGSNs/MMEs of one PLMN.
These two domains are overlapping, i.e. they contain some common entities. A PLMN can implement only one domain
or both domains.
3GPP
Release 15 20 3GPP TS 23.002 V15.0.0 (2018-03)
3.3.1 CS Domain
The CS domain refers to the set of all the CN entities offering "CS type of connection" for user traffic as well as all the
entities supporting the related signalling. A "CS type of connection" is a connection for which dedicated network
resources are allocated at the connection establishment and released at the connection release.
The entities specific to the CS domain are: MSC, GMSC, VLR. All the other CN entities defined in clause 4 "The basic
entities of the mobile system" and not defined as PS domain specific entities (see following clause) are common to the
CS and to the PS domains. In case of E-UTRAN access, there is no support for CS Domain.
3.3.2 PS Domain
The PS domain refers to the set of all the CN entities offering "PS type of connection" for user traffic as well as all the
entities supporting the related signalling. A "PS type of connection" transports the user information using autonomous
concatenation of bits called packets: each packet can be routed independently from the previous one.
The entities specific to the PS domain are the GPRS specific entities, i.e. SGSN and GGSN and EPS specific entities,
i.e. PDN GW, S-GW, MME, SGSN. All the other CN entities defined in clause "4 The basic entities of the mobile
system" and not defined as CS domain specific entities (see previous clause) are common to the CS and to the PS
domains.
The Home Location Register (HLR) is the location register to which a mobile subscriber is assigned for record purposes
such as subscriber information. For EPS, the HLR functionality is provided via HSS.
The Visitor Location Register (VLR) is the location register for Circuit Switched (CS) services, other than the HLR,
used by an MSC to retrieve information for, e.g. handling of calls to or from a roaming mobile station currently located
in its area.
The location register function in the SGSN stores subscription information and location information for Packet
Switched (PS) services for each subscriber registered in the SGSN.
The SGSN is needed only in a PLMN which supports PS Domain with GERAN or UTRAN access.
The location register function in the GGSN stores subscriber information and routeing information (needed to tunnel
packet data traffic destined for a GPRS MS to the SGSN where the MS is registered) for each subscriber for which the
GGSN has at least one PDP context active.
The GGSN is needed only in a PLMN which supports GPRS with GERAN or UTRAN access.
3GPP
Release 15 21 3GPP TS 23.002 V15.0.0 (2018-03)
The location register function in the MME stores subscription information and location information for Packet Switched
(PS) services for each subscriber registered in the MME for EPS.
The location register function in the PDN GW stores subscriber information and routeing information (needed to tunnel
packet data traffic destined for an EPS UE to the Serving GW, where the UE is registered in the MME, in the SGSN or
in the 3GPP AAA server in case of non-3GPP access) for each subscriber for which the PDN GW has at least one PDN
connection active.
3.5 Cell
The cell is an area of radio coverage identified by a Base station identification as defined in TS 23.003 [3].
3GPP
Release 15 22 3GPP TS 23.002 V15.0.0 (2018-03)
The definition of a mobile subscriber's regional subscription area is stored within the HLR/HSS per National
Destination Code(s) (NDC) of a PLMN and is transferred to the VLRs and/or SGSNs/MMEs of that PLMN. The VLR
and/or SGSN/MME evaluates this information to extract the restricted or accessible MSC and/or SGSN/MME areas and
location areas to which the mobile subscriber is allowed to roam. The VLR and/or SGSN/MME inform the HLR/HSS if
an entire MSC and/or SGSN/MME area is restricted.
Zones for Regional Subscription and their handling are defined in TS 23.003 [3], TS 23.008 [5] and TS 29.002 [26] and
TS 29.272 [86] for EPC.
3.16 Pool-area
A pool area is an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied. Within a pool-
area an MS may roam without need to change the serving Core Network (CN) node. A pool-area is served by one or
more CN nodes in parallel.
3GPP
Release 15 23 3GPP TS 23.002 V15.0.0 (2018-03)
Entities in the mobile system can be either implemented in a monolithic way where user data are stored within the entity
itself (or in an external entity via non standard interfaces) or according to the User Data Convergence (UDC) concept
(see TS 23.335 [120]) where the entity becomes a so-called user-dataless Application Front End (AFE). Application
Front Ends access, via the Ud reference point, a User Data Repository (UDR), which stores the relevant user data
managed by the applications. Unless explicitly stated otherwise, this document describes entities in its monolithic form,
e.g. stating that user data are stored in the HSS. If however the UDC concept applies, user data are actually stored in the
UDR and managed by one or several Application Front Ends, so that user data may be shared among the different
Application Front Ends, allowing several AFEs of the same application type (e.g. HSS) to serve the same user at any
given time.
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 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.;
The HSS also generates User Security information for mutual authentication, communication integrity check and
ciphering.
Based on this information, the HSS also is responsible to support the call control and session management entities of the
different Domains and Subsystems (defined in section 3.3 and 3.3a) of the operator as shown in figure 0-a.
3GPP
Release 15 24 3GPP TS 23.002 V15.0.0 (2018-03)
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.
- 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.
The organisation of the subscriber data is outlined in TS 23.008 [5]. It also indicates which numbers, addresses and
identifiers specified in TS 23.003 [3] are stored in HSS.
The HLR can be considered a subset of the HSS that holds the following functionality:
- 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 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.
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;
3GPP
Release 15 25 3GPP TS 23.002 V15.0.0 (2018-03)
- a key used to check the integrity of the communication over the radio path between the mobile 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.
- Mobility Management
This function supports the user mobility through CS Domain, PS Domain and IM CN subsystem.
The HSS supports the call and/or session establishment procedures in CS Domain, PS Domain and IM CN
subsystem. For terminating traffic, it provides information on which call and/or session control entity currently
hosts the user.
- The HSS generates user authentication, integrity and ciphering data for the CS and PS Domains and for the IM
CN subsystem. User security support
3GPP
Release 15 26 3GPP TS 23.002 V15.0.0 (2018-03)
The HSS supports the authentication procedures to access CS Domain, PS Domain and IM CN subsystem
services by storing the generated data for authentication, integrity and ciphering and by providing these data to
the appropriate entity in the CN (i.e. MSC/VLR, SGSN, MME, 3GPP AAA Server or CSCF).
The HSS provides the appropriate relations among all the identifiers uniquely determining the user in the system:
CS Domain, PS Domain and IM CN subsystem (e.g. IMSI and MSISDNs for CS Domain; IMSI, MSISDNs and
IP addresses for PS Domain, private identity and public identities for IM CN subsystem).
- Access authorisation
The HSS authorises the user for mobile access when requested by the MSC/VLR, SGSN, MME, 3GPP AAA
Server or CSCF, by checking that the user is allowed to roam to that visited network.
The HSS provides basic authorisation for MT call/session establishment and service invocation. Besides, the
HSS updates the appropriate serving entities (i.e., MSC/VLR, SGSN, MME, 3GPP AAA Server, CSCF) with the
relevant information related to the services to be provided to the user.
- The HSS provides access to the service profile data for use within the CS Domain, PS Domain and/or IM CN
subsystem. Application Services and CAMEL Services Support (for GERAN and UTRAN access).
The HSS communicates with the SIP Application Server and the OSA-SCS to support Application Services in
the IM CN subsystem. It communicates with the IM-SSF to support the CAMEL Services related to the IM CN
subsystem. The IMS CAMEL subscription data may be transferred to the IM-SSF AS using Sh reference point in
addition to the Si reference point. The HSS communicates with the gsmSCF to support CAMEL Services in the
CS Domain and GPRS PS Domain (for GERAN and UTRAN access).
Editor's Note: CAMEL support for GERAN/UTRAN via EPS (i.e. for S4 SGSN) is FFS.
The HSS supports the storage of IM CN Subsystem user related data, and provides access to these data through
the Rp reference point as described in TS 23.240 [71].
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:
- the Mobile Station Roaming Number (MSRN), see TS 23.003 [3] for allocation principles;
- the location area where the mobile station has been registered;
3GPP
Release 15 27 3GPP TS 23.002 V15.0.0 (2018-03)
- 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.
The VLR also contains supplementary service parameters attached to the mobile subscriber and received from the HLR.
The organisation of the subscriber data is outlined in TS 23.008 [5].
4.1.1.3 (void)
The equipment is classified as "white listed", "grey listed", "black listed" or it may be unknown as specified in
TS 22.016 [2] and TS 29.002 [26].
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 EIR shall as a minimum contain a "white list" (Equipment classified as "white listed").
The choice of which MSCs can act as SMS Gateway MSCs is a network operator matter (e.g. all MSCs or some
designated MSCs).
The choice of which MSCs can act as SMS Interworking MSCs is a network operator matter (e.g. all MSCs or some
designated MSCs).
- Is queried by the I-CSCF during the Registration and Session Setup to get the name of the HSS containing the
required subscriber specific data. Furthermore the SLF is also queried by the S-CSCF during the Registration.
- Is queried by the AS in conjunction with the Sh interface operation to get the name of the HSS containing the
required subscriber specific data.
- Is queried by the 3GPP AAA server to get the name of the HSS containing the required subscriber specific data.
- Is accessed via the Dx interface by the CSCF, via the Dh interface by the AS, and via the Dw interface by the
3GPP AAA Server.
3GPP
Release 15 28 3GPP TS 23.002 V15.0.0 (2018-03)
The SLF is not required in a single HSS environment. An example for a single HSS environment is a server farm
architecture. Use of SLF is not required when AS are configured/managed to use pre-defined HSS.
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 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 [65]. 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, at least the following procedures:
NOTE: When this improves the readability (e.g. when dealing with inter-releases handover), the term 2G-MSC
can be used to refer to an MSC Release 98 or prior, and the term 3G-MSC can be used to refer to an MSC
Release 99 or later.
When needed, the MSC can be implemented in two different entities: the MSC Server, handling only signalling, and the
CS-MGW, handling user's data. A MSC Server and a CS-MGW make up the full functionality of a MSC.
The CS fallback enabled MSC supports the following additional functions according to TS 23.272 [81]:
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 [83]:
- Handling the Relocation Preparation procedure requested for the voice component from MME via Sv interface;
- Handling the MAP_Update_Location procedure without it being triggered from the UE.
3GPP
Release 15 29 3GPP TS 23.002 V15.0.0 (2018-03)
If a MSC Server is enhanced for IMS Centralized Services (as defined in TS 23.292 [110]), 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.
This component is PSTN/PLMN transport termination point for a defined network and interfaces UTRAN with the core
network over Iu.
A CS-MGW may terminate bearer channels from a switched circuit network and media streams from a packet network
(e.g. RTP streams in an IP network). Over Iu, the CS-MGW may support media conversion, bearer control and payload
processing (e.g. codec, echo canceller, conference bridge) for support of different Iu options for CS services
(AAL2/ATM based as well as RTP/UDP/IP based).
The CS-MGW:
- Interacts with MGCF, MSC server and GMSC server for resource control.
The CS-MGW will be provisioned with the necessary resources for supporting UMTS/GSM transport media. Further
tailoring (i.e. packages) of the H.248 [52] may be required to support additional Codecs and framing protocols, etc.
The CS-MGW bearer control and payload processing capabilities will also need to support mobile specific functions
such as SRNS relocation/handover and anchoring. It is expected that current H.248 [52] standard mechanisms can be
applied to enable this.
The choice of which MSCs can act as Gateway MSCs is for the operator to decide (i.e. all MSCs or some designated
MSCs).
If the call is a voice group/broadcast call, it is routed directly from the GMSC to the VBS/VGCS Anchor MSC, based
on information (VBS/VGCS call reference) contained in the dialled number (see also TS 43.068 [41] and
TS 43.069 [42]).
Editor's note: There is a need to consider possibilities that call incoming to the PLMN may be routed to entities
other than the GMSC, e.g., for networks that do not deploy CS domain.
When needed, the GMSC can be implemented in two different entities: the GMSC Server, handling only signalling, as
defined below, and the CS-MGW, defined above. A GMSC Server and a CS-MGW make up the full functionality of a
GMSC.
3GPP
Release 15 30 3GPP TS 23.002 V15.0.0 (2018-03)
- subscription information:
- the IMSI;
- 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.
The SGSN .provide support for Direct Tunnel functions as specified in TS 23.060 [9a].
The organisation of the subscriber data in the SGSN is defined in TS 23.008 [5] and TS 23.060 [9a].
The procedures for information transfer between the SGSN, the GGSN, the VLR and the HLR are defined in
TS 23.016 [39] and TS 23.060 [9a].
NOTE: When this improves the readability (e.g. when dealing with inter-releases handover), the term 2G-SGSN
can be used to refer to a SGSN Release 98 or prior, and the term 3G-SGSN can be used to refer to a
SGSN Release 99 or later.
The SGSN provides support for SRVCC functions as specified in TS 23.216 [83].
- subscription information:
- the IMSI;
- location information:
3GPP
Release 15 31 3GPP TS 23.002 V15.0.0 (2018-03)
The organisation of the subscriber data in the GGSN is defined in TS 23.008 [5] and TS 23.060 [9a].
The procedures for information transfer between the GGSN, the SGSN and the HLR are defined in TS 23.016 [39] and
TS 23.060 [9a].
4.1.3.3 Void
4.1.4.1 MME
MME is the control plane entity within EPS supporting functions as listed below. For detailed functional role of MME,
see specifications TS 23.401 [76], TS 23.402 [77] and TS 36.300 [78].
Mobility Management,
- Roaming ;
- Authentication;
- Transparent transfer of HRPD signalling messages and transfer of status information between E-UTRAN and
HRPD access;
- Transparent transfer of RIM signalling messages between E-UTRAN and HRPD access;
The procedures for information transfer between the SGSN, the MME and the HSS are defined in TS 23.401 [76] and
TS 23.060 [9a].
The CS fallback enabled MME supports the following additional functions according to TS 23.272 [81]:
- Initiating paging procedure towards eNodeB when MSC pages the UE for CS services
- 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 [83]:
- Performing the PS bearer splitting function by separating the voice PS bearer from the non-voice PS bearers.
3GPP
Release 15 32 3GPP TS 23.002 V15.0.0 (2018-03)
- Handling the non-voice PS bearers handover with the target cell as according to Inter RAT handover procedure
as defined in TS 23.401 [76].
- 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.
4.1.4.2 Gateways
4.1.4.2.1 Serving GW
The Serving GW is the gateway which terminates the interface towards E-UTRAN.
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 [77].
- ECM-IDLE mode downlink packet buffering and initiation of network triggered service request procedure;
- Lawful Interception;
- A local non-3GPP anchor for the case of roaming when the non-3GPP IP accesses connected to the VPLMN;
- Uplink and downlink bearer binding towards 3GPP accesses as defined in TS 23.203 [73];
The Serving GW can be split into SGW-C and SGW-U, which jointly provide above functionalities. The functional split
between SGW-C and SGW-U are defined in TS 23.214 [145].
4.1.4.2.2 PDN GW
The PDN GW is the gateway which terminates the SGi interface towards the PDN.
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 PDN GW provides PDN connectivity to both GERAN/UTRAN only UEs and E-UTRAN capable UEs using any of
E-UTRAN, GERAN or UTRAN. The PDN GW provides PDN connectivity to E-UTRAN capable UEs using
E-UTRAN only over the S5/S8 interface. The PDN GW may also provide PDN connectivity to UEs using non-3GPP
access networks with the procedures defined in TS 23.402 [77].
For detailed PDN GW functions, see TS 23.401 [76] and TS 23.402 [77].
3GPP
Release 15 33 3GPP TS 23.002 V15.0.0 (2018-03)
- 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;
- UL and DL service level charging, gating control, rate enforcement as defined in TS 23.203 [73];
- 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/S2a/S2b:
The PDN GW functions also includes user plane anchor for mobility between 3GPP access and non-3GPP access. It
supports:
- A LMA function for PMIPv6, if PMIP-based S5 or S8, or if PMIP based S2a or PMIP based S2b is used;
- Allocation of GRE key, which is used to encapsulate uplink traffic to the PDN GW on the PMIP-based S5/S8, or
PMIP based S2a or PMIP based S2b interface;
- GPRS Tunnelling Protocol for the control plane and the user plane to provide PDN connectivity to UEs using
non-3GPP accesses, if GTP based S2a or GTP based S2b is used.
The PDN GW can be split into PGW-C and PGW-U, which jointly provide above functionalities. The functional split
between PGW-C and PGW-U are defined in TS 23.214 [145].
For detailed Local GW functions, see TS 23.401 [76] and TS 23.060 [9a].
4.1.4.3 SGSN
In addition to the functions described for GPRS, for EPC SGSN functions include:
- Inter EPC node signalling for mobility between 2G/3G and E-UTRAN 3GPP access networks;
- PDN and Serving GW selection: the selection of S GW/PDN GW by the SGSN is as specified for the MME;
Whether a Non-3GPP IP access network is Trusted or Untrusted is not a characteristic of the access network.
3GPP
Release 15 34 3GPP TS 23.002 V15.0.0 (2018-03)
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.
4.1.4.5 ePDG
The functionality of ePDG includes the following:
- Functionality defined for the PDG in TS 23.234 [67] 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; if GTP based S2b is used, this includes routing of uplink packets based on the uplink packet filters in the
TFTs assigned to the S2b bearers of the PDN connection;
- Routing of downlink packets towards the SWu instance associated to the PDN connection;
- De-capsulation/Encapsulation of packets for IPSec and, if network based mobility (S2b) is used, for GTP or
PMIP tunnels;
- Mobile Access Gateway (MAG) for PMIPv6 if PMIP based 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);
- Lawful Interception.
4.1.4.8 ANDSF
The ANDSF (which is an optional element in the architecture) contains data management and control functionality
necessary to provide network discovery and selection assistance data as per operators' policy. The ANDSF is able to
3GPP
Release 15 35 3GPP TS 23.002 V15.0.0 (2018-03)
initiate data transfer to the UE, based on network triggers, and respond to requests from the UE. It provides functions
such as inter-system mobility policy, access network discovery information.
The ANDSF in the subscriber's home operator network may interact with other databases such as the HSS user profile
information residing in subscriber's home operator network. Details of such interaction with these databases are not
described in this Release of the specifications. For details on ANDSF, see TS 23.402 [77].
NOTE: When the UE is roaming, how it discovers and interacts with the ANDSF is not specified in the
specification of this release.
The access technologies offered by the BSS are described in the 45-series of 3GPP specifications. The access
technologies offered by the RNS (FDD, TDD) are described in the 25-series of 3GPP specifications. The access
technologies offered by E-UTRAN (FDD, TDD) are described in the 36-series of 3GPP specifications.
The radio equipment of a BSS may support one or more cells. A BSS may consist of one or more base stations. Where
an Abis-interface is implemented, the BSS consists of one Base Station Controller (BSC) and one or more Base
Transceiver Station (BTS). The split of functions between BSS and CN for a Iu interface is described in the 25-series of
UMTS Technical Specifications.
The split of functions between BSS and CN for a A/Gb interface is described in the 48-series of GSM Technical
Specifications. The split of functions between BSS and CN for a Iu interface is described in the 25-series of UMTS
Technical Specifications.
NOTE: The mobile station shall operate using only the following modes:
a A / Gb mode, e.g. for pre-Release 4 terminals, or for Release 4 terminals when connected to a BSS with no Iu
interface towards the Core Network.
b Iu mode (i.e. Iu-CS and Iu-PS ), e.g. for Release 4 terminals when connected to a BSS with Iu interfaces
towards the Core Network.
3GPP
Release 15 36 3GPP TS 23.002 V15.0.0 (2018-03)
The split of functions between RNS and CN is described in the 25-series of UMTS Technical Specifications.
4.2.2.2 Node B
A Node B is a logical network component which serves one or more UTRAN cells.
The split of functions between eNB and EPC is described in the specifications TS 23.401 [76], TS 36.300 [78] and
TS 36.401 [79].
The E-UTRAN consists of set of eNBs connected to the EPC through the S1 interface.
An eNB can support FDD mode, TDD mode or dual mode operation.
3GPP
Release 15 37 3GPP TS 23.002 V15.0.0 (2018-03)
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. These
functional groups are described in TS 24.002 [12].
All the specific entities defined so far are located in the Core Network.
Voice group or broadcast call attributes are defined for a specific voice group or broadcast call reference and include the
data required to configure the conference bridge for a VGCS or VBS call and other call related attributes.
The Group Call Register (GCR) shall hold for a related MSC area for each group ID and cell from which Voice Group
Call Service (VGCS) or Voice Broadcast Service (VBS) calls can be established by mobile stations the voice group call
reference or voice broadcast call reference to be used for a VGCS or VBS call to be established and an indication
whether the originating MSC is the MSC responsible for that call.
If the originating MSC is not responsible for that call, the GCR shall hold the routing information identifying the MSC
responsible for that call.
A GCR may be in charge of one or several MSC. Each MSC involved in a voice group or broadcast call requests its
proper voice group or broadcast call attributes from its related GCR by use of the voice group or broadcast call
reference.
The contents of each list related to requests of the MSC responsible for a voice group or broadcast call is as follows:
- a list of cells inside the MSC area of the requesting MSC into which the call is to be sent (part of the group call
area);
- a list of identities of dispatchers which are allowed to initiate the voice group or broadcast call;
- a list of identities of dispatchers which are allowed to terminate the voice group or broadcast call;
- the length of time over which no activity is detected before the voice group call is automatically terminated;
- the default priority level related to the voice group or broadcast call if the eMLPP supplementary service applies;
- a flag indicating if acknowledgements are required for this voice group or broadcast call.
The contents of each list related to requests of an MSC not responsible for a voice group or broadcast call is as follows:
3GPP
Release 15 38 3GPP TS 23.002 V15.0.0 (2018-03)
- a list of cells inside the MSC area of the requesting MSC into which the call is to be sent (part of the group call
area).
4a.2 (void)
For further details on LCS in E-UTRAN, UMTS and GSM from system and core network point view, see
TS 23.271 [56].
For further details on user-plane LCS in E-UTRAN, see OMA SUPL [80]. For further details on control plane LCS for
E-UTRAN see TS 36.305 [122].
BSC/SRNC: the BSC for GERAN and SRNC for UTRAN receive authenticated location requests from the CN:
- In UTRAN, the SRNC co-ordinates the positioning requests taking into account their priority and it selects
the positioning method to fulfil the requested accuracy. It interfaces, when necessary, with the CRNC which
mainly manages resources allocated to UE positioning operations and requests UE Positioning related
measurements from its associated Node Bs and LMUs.
SMLC:
- The Serving Mobile Location Centre (SMLC) function can be part of the RNC or be a SAS (Stand-Alone
SMLC) for UTRAN. The SMLC function can be part of the BSC or be in a separate SMLC server for
GERAN.
- In UTRAN, the SMLC function provides assistance data to the RNC and acts as a location calculation server
if the location estimates are not to be calculated in the RNC.
- In GERAN, the SMLC function co-ordinates the positioning request, schedules resources required to perform
positioning of a mobile, and calculates the final location estimate and accuracy. The SMLC may control a
number of LMUs.
LMU: The Location Measurement Unit (LMU) entity makes measurements for one or more positioning
methods.
Node B: Node B is a network element of UTRAN that may provide measurement results for position estimation
and makes measurements of radio signals.
eNodeB: The eNode B is a network element of E-UTRAN that may provide measurement results for position
estimation and makes measurements of radio signals for a target UE and communicates these measurements to
an E-SMLC.
3GPP
Release 15 39 3GPP TS 23.002 V15.0.0 (2018-03)
CBC: The Cell Broadcast Centre, in GERAN, the SMLC function may interface a CBC in order to broadcast
assistance data using existing cell broadcast capabilities.
For detail on Location services, entities and interfaces provided by E-UTRAN, see TS 36.305 [122].
For detail on Location services, entities and interfaces provided by UTRAN, see TS 25.305 [10b].
For detail on Location services, entities and interfaces provided by GERAN, see TS 43.059 [10d].
- Type B LMU:accessed over the base station to controller interface (Abis in GSM and Iub in UMTS).
A type A LMU is accessed exclusively over the GSM air interface (Um interface): there is no wired connection to any
other network element.
In GSM, a type A LMU has a serving BTS and BSC that provide signalling access to a controlling SMLC. With an NSS
based SMLC, a type A LMU also has a serving MSC and VLR and a subscription profile in an HLR. A type A LMU
always has a unique IMSI and supports all radio resource and mobility management functions of the GSM air interface
that are necessary to support signalling using an SDCCH to the SMLC. A type A LMU supports those connection
management functions necessary to support LCS signalling transactions with the SMLC and may support certain call
control functions of to support signalling to an SMLC using a circuit switched data connection.
In UTRAN, a type A LMU has signalling access to the SRNC. Type A LMU is not supported in UMTS release 1999.
In GSM, a Type B LMU is accessed over the Abis interface from a BSC. The LMU may be either a standalone network
element addressed using some pseudo-cell ID or connected to or integrated in a BTS. Signalling to a Type B LMU is by
means of messages routed through the controlling BSC for a BSS based SMLC or messages routed through a
controlling BSC and MSC for an NSS based SMLC.
In UTRAN, a Type B LMU is accessed over the Iub interface from an RNC. The LMU may be either a standalone
network element addressed using some pseudo-cell ID or connected to or integrated in a Node B.
The E-SMLC may interact with a target UE in order to deliver assistance data if requested for a particular location
service, to obtain a location estimate, or location related measurements, if that was requested.
For positioning of a target UE, the E-SMLC decides on the position methods to be used, based on factors that may
include the LCS Client type, the required QoS, UE positioning capabilities, and eNode B positioning capabilities. The
E-SMLC then invokes these positioning methods in the UE and/or serving eNode B. The positioning methods may
yield a location estimate for UE-based position methods and/or positioning measurements for UE-assisted and network-
based position methods. The E-SMLC may combine all the received results and determine a single location estimate for
the target UE (hybrid positioning). Additional information like accuracy of the location estimate and velocity may also
be determined.
3GPP
Release 15 40 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE: Whether it should be possible that an RNC is connected to at least two CBCs at the same time (the
"normal" one as in GSM and a second one for LCS) is for further study and depends on the solution taken
for LCS.
3GPP
Release 15 41 3GPP TS 23.002 V15.0.0 (2018-03)
The NPDB stores the table of correspondence between MSISDNs and Subscription networks. Upon request of the
(gateway or visited) MSC, the NPDB retrieves from the MSISDN the Routing Number pointing out the Subscription
network.
The MNP-SRF obtains the routing information from a NP database to identify the subscription network associated with
a particular national MSISDN. Upon request from gateway MSC, the MNP-SRF may perform one of the following
actions:
1. the MNP-SRF will reply back to the GMSC with the necessary routing information to route the call;
For non-call related signalling (e.g. delivery of SMS), only cases 2 and 3 are applicable.
- Controls the parts of the call state that pertain to connection control for media channels in an IMS-MGW.
- Determines the next hop depending on the routing number for incoming calls from legacy networks.
- Performs protocol conversion between ISUP/TCAP/SIP-I and the IM subsystem call control protocols.
A IMS-MGW may terminate bearer channels from a switched circuit network and media streams from a packet network
(e.g., RTP streams in an IP network). The IMS-MGW may support media conversion, bearer control and payload
processing (e.g. codec, echo canceller, conference bridge), it:
3GPP
Release 15 42 3GPP TS 23.002 V15.0.0 (2018-03)
The IMS-MGW will be provisioned with the necessary resources for supporting UMTS/GSM transport media. Further
tailoring (i.e. packages) of the H.248 [52] may be required to support additional Codecs and framing protocols, etc.
- Interprets information coming from an AS and S-CSCF (e.g. session identifier) and control MRFP accordingly.
- Generates CDRs .
- Floor Control (i.e. manage access rights to shared resources in a conferencing environment).
The MRB may take the following kinds of information into account when assigning MRF resources to an application:
- the specific characteristics of the media resources required for the call or calls;
4a.7.5 Void
3GPP
Release 15 43 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE 1: The OSA Application Server does not directly interact with the IMS network entities but through the OSA
Service Capability Servers (OSA SCS-s). Further information on OSA is provided in TS 22.127 [4].
NOTE 2: A SIP Application Server specified within 3GPP that supports IMS reference points (e.g. ISC, Sh, Ut), in
support of an application, is considered as part of the IM CN subsystem. Examples of such ASs are SCC
AS and TAS.
The AS (SIP Application Server and/or the OSA Service Capability Server and/or IM-SSF) can communicate with the
HSS. The Sh and Si interfaces are used for this purpose.
The Serving-CSCF to AS interface is used to provide services residing in an AS. Two cases were identified:
- Serving-CSCF to an AS in a trusted External Network (e.g., Third Party or Visited). The S-CSCF does not
provide authentication and security functionality for secure direct third party access to the IM Subsystem. The
OSA framework provides a standardized way for third party access to the IM Subsystem.
The Interrogating-CSCF to AS interface is used to forward SIP requests destined to a Public Service Identity hosted by
the AS directly to that AS.
The AS to MRB interface (Rc) is used by the AS to request that MRF resources with certain characteristics be assigned
to a call.
An Application Server may influence and impact the SIP session on behalf of the services supported by the operator's
network. An AS may host and execute services.
3GPP
Release 15 44 3GPP TS 23.002 V15.0.0 (2018-03)
- Routing calls through a CTM Special resource function (CTM-SRF) in the core network. The CTM-SRF is
linked in to the call path via CAMEL procedures. Depending on operator configuration the CTM-SRF may also
be linked in to the call path for Emergency calls.
- A CTM / Text telephone converting function included along the speech call path selected by the network after an
indication from the terminal that CTM is required.
- A CTM / Text telephone converting function included in all speech call paths.
Further information of the support for text telephony is found in TS 23.226 [37].
The interface between different security domains is protected by Security Gateways (SEGs). The SEGs are responsible
for enforcing the security policy of a IP security domain towards other SEGs in the destination IP security domain. All
NDS/IP traffic shall pass through a SEG before entering or leaving a security domain. For further details of SEG, see
TS 33.210 [64].
3GPP
Release 15 45 3GPP TS 23.002 V15.0.0 (2018-03)
4a.12 Void
3GPP
Release 15 46 3GPP TS 23.002 V15.0.0 (2018-03)
4a.14.3 MBMS-GW
The MBMS-GW provides functions in the EPS for controlling MBMS session initiation/modification/termination by
the MBMS User Service and for providing delivery of IP Multicast datagrams from the SGi-mb reference point to
downstream nodes in the MBMS Service Area with a specified quality of service.
4a.15 Void
When the Sd interface applies, the PCRF maintains the correlation between the IP-CAN session and the TDF session.
Events subscribed by the TDF are reported by the PCRF.
When S9a interface applies, the PCRF provides to the BPCF the UE/H(e)NB local IP address and UDP port number, the
QoS rules and PCC rules over S9a interface. PCRF maintains the correlation between the GW control session over S9a
interface and the IP-CAN session over Gx interface (if IP-CAN session over Gx interface is available).
When S15 interface applies, the PCRF provides dynamic QoS control policies to the BPCF for the purpose of allocation
of QoS resources in the Fixed Broadband Access Network for HNB CS traffic.
PCRF is the policy and charging control element. PCRF functions are described in more detail in TS 23.203 [73].
In non-roaming scenario, there is only a single PCRF in the HPLMN associated with one UE's IP-CAN 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:
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).
3GPP
Release 15 47 3GPP TS 23.002 V15.0.0 (2018-03)
This functional entity is located at the Gateway (e.g. GGSN in the GPRS case) and in the PDN GW for EPS).
The functionality of PCEF is described in TS 23.203 [73], TS 23.401 [76] and TS 23.402 [77].
This function entity is located at a GW (e.g. S-GW in the 3GPP access with PMIP based S5/S8 case, HSGW in the
HRPD case, A-GW in the non- 3GPP access when PMIP or DSMIPv6 based mobility is used, ePDG with PMIP based
S2b or Untrusted S2c case if Gxb* applies).
3GPP
Release 15 48 3GPP TS 23.002 V15.0.0 (2018-03)
The BBERF in the ePDG supports only reporting of the UE's Local IP address and UDP port number to the PCRF.
Bearer binding and bearer binding verification functions are not supported.
A Home NodeB is a Customer Premises Equipment (CPE) offering UTRAN coverage, further details can be found in
TS 25.467 [114].
A Home NodeB Gateway is the gateway through which the Home NodeB accesses the core network, more details can
be found in TS 25.467 [114].
A Local GW is a gateway towards the IP networks (e.g. residential/enterprise networks, Internet) associated with the
Home NodeB, more details can be found in TS 23.060 [9a]. The Local GW can be colocated with the Home NodeB or
can be a standalone GW (with Serving GW and Local GW collocated) residing in the Local Network.
A Home eNodeB is a Customer-Premises Equipment (CPE) offering E-UTRAN coverage, further details can be found
in TS 36.300 [78].
A Home eNodeB Gateway is an optional gateway through which the Home eNodeB accesses the core network, more
details can be found in TS 36.300 [78].
A Local GW is a gateway towards the IP networks (e.g. residential/enterprise networks, Internet) associated with the
Home eNodeB, more details can be found in TS 23.401 [76]. The Local GW can be colocated with the Home eNodeB
or can be a standalone GW (with Serving GW and Local GW collocated) residing in the Local Network.
The Allowed CSG list and the Operator CSG list are applicable to both UTRAN and E-UTRAN CSG cells for HNB and
HeNB respectively.
The CSS is responsible for holding the following user related information:
- User Identification;
- CSG membership granted to the subscriber during his stay in the VPLMN, i.e. list of CSG IDs and associated
expiration dates;
- User Location information: the CSS stores the location information of the subscriber for subsequent update of
the CSG subscription information at the MME, SGSN and VLR upon subscription change.
3GPP
Release 15 49 3GPP TS 23.002 V15.0.0 (2018-03)
- download of the CSG subscription information upon request from the serving MME, SGSN and VLR, through
the S7a, S7d, Ghv and Hv interfaces, to enable roaming subscribers to access to the PS and CS Domain services
via CSG cells;
- service provisioning, including updating the appropriate serving entities (i.e. MME, SGSN and VLR) with
modifications of the the CSG membership granted to the subscriber.
The organisation of the subscriber data is outlined in TS 23.008 [5]. It also indicates which numbers and identifiers
specified in TS 23.003 [3] are stored in the CSS.
The TDF can be split into TDF-C and TDF-U, which jointly provide TDF functionalities. The functional split between
TDF-C and TDF-U are defined in TS 23.214 [145].
3GPP
Release 15 50 3GPP TS 23.002 V15.0.0 (2018-03)
Note: The TCP Proxy Function can be deployed in a GGSN/PGW or as an external function beyond SGi/Gi. The TCP
Proxy is deployed such that it is transparent to the UE and its mobility.
The implementation and necessary protocols to realize the functions related to TCP Proxy Function are outside the
scope of 3GPP specifications.
3GPP
Release 15 51 3GPP TS 23.002 V15.0.0 (2018-03)
The functional description of the RCAF can be found in TS 23.203 [73], TS 23.401 [76] and TS 23.060 [9a].
The description of the MCPTT AS with the network functional models and the reference points is detailed in
TS 23.179 [142].
In the basic configuration presented in figure 1, all the functions are considered implemented in different equipments.
Therefore, all the interfaces within PLMN are external. Interfaces A and Abis are defined in the 48-series of Technical
Specifications. Interfaces Iu, Iur and Iub are defined in the 25.4xx-series of Technical Specifications. Interfaces B, C, D,
E, F and G need the support of the Mobile Application Part of the signalling system No. 7 to exchange the data
necessary to provide the mobile service. No protocols for the H-interface and for the I-interface are standardized. All the
GPRS-specific interfaces (G- series) are defined in the 23-series, 24-series and 29-series of Technical Specifications.
Interfaces Mc, Nb, and Nc are defined in TS 23.205 [43] and in the 29-series of Technical Specifications. The
specifications for E-UTRAN interfaces S1 and X2 are specified in TS 36.4xx and NAS protocol is specified in
TS 24.301 [89] series of specifications. The interfaces S6a/d/S13 are specified in the specifications TS 29.272 [86]. The
EPC specific S1/3/4/5/8/10/11/12/ series are specified in TS 29.274 [90] for GTP based protocols and for PMIP based
S5/8 interfaces are specified in TS 29.275 [93].
From this configuration, all the possible 3GPP access PLMN organisations can be deduced. In the case when some
functions are contained in the same equipment, the relevant interfaces become internal to that equipment.
3GPP
Release 15 52 3GPP TS 23.002 V15.0.0 (2018-03)
The configuration possibilities when using non-3GPP access technologies using EPS is not part of the scope of this
specification. The architecture and details for non-3GPP access and mobility and interworking with non-3GPP access
are described in TS 23.402 [77] and the interfaces and protocols are specified in 3GPP 24-series and 29-series of
specifications..
3GPP
Release 15 53 3GPP TS 23.002 V15.0.0 (2018-03)
Legend:
Bold lines: interfaces supporting user traffic;
Dashed lines: interfaces supporting signalling.
NOTE 1: The figure shows direct interconnections between the entities. The actual links may be provided by an
underlying network (e.g. SS7 or IP): this needs further studies.
NOTE 2: When the MSC and the SGSN are integrated in a single physical entity, this entity is called UMTS MSC
(UMSC).
NOTE 3: A (G)MSC server and associated CS-MGW can be implemented as a single node: the (G)MSC.
NOTE 4: The Gn interface (between two SGSNs) is also part of the reference architecture, but is not shown for layout
purposes only.
Figure 1: Basic Configuration of a PLMN supporting CS and PS services (using GPRS) and interfaces
3GPP
Release 15 54 3GPP TS 23.002 V15.0.0 (2018-03)
SMS-GMSC/
SMS-IWMSC
SGd
E
S6c/C MME
Gd/Gdd
MSC- HSS
SGSN
Server (HLR)
3GPP
Release 15 55 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE: The interfaces in blue represent EPS functions and reference points.
NOTE 2: The S-GW and PDN-GW can be further split into control plane entities (SGW-C and PGW-C) and user
plane entities (SGW-U and PGW-U). The architecture reference model for the control plane and user plane
separation is defined in TS 23.214 [145].
Figure 1b: Basic Configuration of a 3GPP Access PLMN supporting CS and PS services (using GPRS
and EPS) and interfaces
3GPP
Release 15 56 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE: Lgd interface is applicable only for an SGSN supporting EPS based interfaces and protocols.
3GPP
Release 15 57 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE: Lgd interface is applicable only for an SGSN supporting EPS based interfaces and protocols.
3GPP
Release 15 58 3GPP TS 23.002 V15.0.0 (2018-03)
SLg
MME
S1 External LCS
GMLC Client
UE E-UTRAN SLs Le
E-SMLC
LTE-Uu
SLh
HSS
NOTE: Most CAMEL-specific interfaces have no particular name. They are designated by the name of the two
entities they link together, e.g. "the gsmSSF-gsmSCF interface".
GMSC
gsmSSF
C
Ge D Gr
3GPP
Release 15 59 3GPP TS 23.002 V15.0.0 (2018-03)
The bold lines are used for interfaces supporting user data only, the dashed lines are used for interfaces supporting
signalling only.
CBC
CN
BSS RNS
BSC RNC
Abis Iub
BTS BTS Node B Node B
UE
Figure 5: Configuration of a PLMN supporting Cell Broadcast Service entities for GERAN/UTRAN
NOTE: The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
Only the interfaces specifically linked to the IM CN subsystem are shown, i.e. all the SGSN, GGSN, S-GW, PDN-GW
and HSS interfaces depicted in figure 1 and figure 1b are still supported by these entities even if not shown.
3GPP
Release 15 60 3GPP TS 23.002 V15.0.0 (2018-03)
Legend:
Bold lines: interfaces supporting user traffic;
Dashed lines: interfaces supporting only signalling.
NOTE 1: The reference point CS (Circuit Switched) is not specified in this specification.
NOTE 2: The reference point I5 is not shown in this figure.
3GPP
Release 15 61 3GPP TS 23.002 V15.0.0 (2018-03)
AS AS
SCIM
SIP
SIPApplication
Application
Server
Server
Sh
ISC
OSA
OSAservice
service OSA
OSA
HSS
HSS SS-CSCF
-CSCF capability
capabilityserver
server application
application
Cx ISC (SCS)
(SCS) server
server
OSA API
ISC
Si
IM
IM-SSF
-SSF
MAP
CAP
Camel
CamelService
Service
Environment
Environment
Figure 6a: Functional architecture for the provision of service in the IMS
The purpose of the IM SSF is to host the CAMEL network features (i.e. trigger detection points, CAMEL Service
Switching Finite State Machine, etc.) and to interwork with CAP. The IMS-SSF may receive CAMEL subscription data
from HSS via Sh reference point in addition to the Si reference point.
The IM SSF and the CAP interface support legacy services only.
The application server may contain "service capability interaction manager" (SCIM) functionality and other application
servers. The SCIM functionality is an application which performs the role of interaction management. The internal
components are represented by the "dotted boxes" inside the SIP application server. The internal structure of the
application server is outside the standards. The Sh interface shall have sufficient functionality to enable this scenario.
The figure below depicts an overall view of the functional architecture for enabling the management of the user's
service related information via the Ut interface.
SIP
Application
Server
Sh
HSS ISC
Ut
Cx
UE S-CSCF
Figure 6b: Functional architecture for the management of the user's service related information
The figure below depicts an overall view of the functional architecture for routing SIP requests between I-CSCF and
Application Server.
3GPP
Release 15 62 3GPP TS 23.002 V15.0.0 (2018-03)
Application
Server
Ma
I-CSCF
Figure 6c: Functional architecture for the routing of SIP requests between I-CSCF and AS
Figure 6d: Functional architecture for IMS Service Centralization and Continuity
IMS Service Centralization, defined in TS 23.292 [110] provides communication services such that all services, and
service control, are based on IMS mechanisms and enablers. It enables IMS services when using CS access as bearer for
the media.
IMS Service Continuity, defined in TS 23.237 [111] provides Session Transfer mechanisms to maintain service
continuity in the event of access transfer for the case when such events are not hidden from the IMS session layer and
thus service continuity could not otherwise be maintained.
Figure 6e provides the reference architecture for SRVCC using the ATCF enhancements as defined in TS 23.237 [111].
The ATCF enhancements provide Session Transfer mechanisms in the serving network to maintain service continuity in
the event of access transfer for SRVCC.
3GPP
Release 15 63 3GPP TS 23.002 V15.0.0 (2018-03)
Figure 6e: IMS Service Centralization and Continuity Reference Architecture when using ATCF
enhancements
If neither the MSC Server is not enhanced for ICS, the interface between MSC Server and ATCF is Mw.
NOTE 2: If the MSC Server is enhanced for ICS, the interface between MSC Server and ATCF is I2.
NOTE: The presence of dashed elements in the figure depends on the configuration.
PCC functional elements are present only for EPC access with QoS.
The corresponding PCC elements for fixed access are also optionally supported but not shown.
The NAT is meant for non-cellular access to IMS.
3GPP
Release 15 64 3GPP TS 23.002 V15.0.0 (2018-03)
The architecture and the procedures to provide communication services to WebRTC IMS clients (WIC) are defined in
Annex U of TS 23.228 [34].
IP SS7
Signalling Signalling
transport SCTP/IP SGW MTP transport
NW NW
NOTE: SS7 application transport and SCTP/IP adaption protocols are not shown.
3GPP
Release 15 65 3GPP TS 23.002 V15.0.0 (2018-03)
Intranet /
Internet
3GPP
AAA
Wa Proxy
WLAN Access
Network Wg
WLAN Ww
UE Wn WAG
Wd
Wx HSS
Wp 3GPP
AAA
Server Dw
m
W SLF
D
'/
G
r'
Wu Packet Data
Gateway
HLR
Wi
3GPP Home
Network
3GPP
Release 15 66 3GPP TS 23.002 V15.0.0 (2018-03)
PDN
( e . g .Internet )
Content
Provider /
Multicast
Broadcast
HLR Source
Gr
Gmb Content
Uu Iu Gn / Gp Provider /
Multicast
UE UTRAN SGSN GGSN BM - SC Broadcast
Iu TPF Source
Iu / Gb
. Gmc
Gi
Gi
BM-SC
Mz
Um Iu
UE GERAN Other PLMN
NOTE: The MCE (Multi-cell/Multicast Coordination Entity) is not shown in the figure. See TS 36.300 [78].
3GPP
Release 15 67 3GPP TS 23.002 V15.0.0 (2018-03)
The PCRF can receive RAN User Plane Congestion Information from the RAN Congestion Awareness Function
(RCAF).
The PCC architecture extends the architecture of an IP-CAN, where the Policy and Charging Enforcement Function is a
functional entity in the Gateway node implementing the IP access to the PDN. The allocation of the Bearer Binding and
Event Reporting Function is specific to each IP-CAN type and specified in the TS 23.203 [73].
3GPP
Release 15 68 3GPP TS 23.002 V15.0.0 (2018-03)
PCC function makes it possible to apply policy and charging control to any kind of 3GPP IP CAN and any non-3GPP
accesses connected via EPC complying with TS 23.402 [77]. Applicability of PCC to other IP CAN is not restricted;
however, it shall be possible for the PCC architecture to base decisions upon the type of IP CAN used (e.g. GPRS, I-
WLAN, etc.). Support for policy control and charging when local breakout and roaming are applied as specified in
TS 23.401 [76] and TS 23.402 [77] is supported.
Figure 5.11-1: Overall PCC logical architecture (non-roaming) when SPR is used
3GPP
Release 15 69 3GPP TS 23.002 V15.0.0 (2018-03)
Figure 5.11-2: Overall PCC logical architecture (non-roaming) when UDR is used
Figure 5.11-3: Overall PCC architecture (roaming with home routed access) when SPR is used
3GPP
Release 15 70 3GPP TS 23.002 V15.0.0 (2018-03)
Figure 5.11-4: Overall PCC architecture for roaming with PCEF in visited network (local breakout)
when SPR is used
NOTE 1: The SCEF acts as an AF (using Rx) in some service capability exposure use cases as described in
TS 23.682 [132].
NOTE 2: The PCEF of PDN GW and the TDF can be further split into control plane entities (PGW-C and TDF-C)
and user plane entities (PGW-U and TDF-U). The architecture reference model for the control plane and
user plane separation is defined in TS 23.214 [145].
3GPP
Release 15 71 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE: The MGW is not shown in the figure 5.12 since the CS fallback in EPS does not have any impacts to the
User plane handling.
3GPP
Release 15 72 3GPP TS 23.002 V15.0.0 (2018-03)
Figure 5.13a: SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with Gn based SGSN
Figure 5.13b: PS to CS SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with S4
based SGSN
NOTE 1: The above figures only show the necessary components related to MSC Server enhanced with SRVCC.
NOTE 2: MSC Server shown in the above figures are enhanced for SRVCC.
NOTE 3: This architecture also applies to roaming scenario (i.e., S8, S6a are not impacted due to SRVCC).
NOTE 4: The MSC Server enhanced with SRVCC may not be the final target MSC which connects to the target cell.
3GPP
Release 15 73 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE 1: The above figure only shows the necessary components related to MSC Server enhanced for CS to PS
SRVCC.
NOTE 2: MSC Server shown in the figure is enhanced for CS to PS SRVCC.
NOTE 3: This architecture also applies to roaming scenario (i.e. S8, S6a are not impacted due to CS to PS
SRVCC).
Figure 5.13d: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with Gn based
SGSN
3GPP
Release 15 74 3GPP TS 23.002 V15.0.0 (2018-03)
NOTE 1: The above figures only show the necessary components related to MSC Server enhanced with CS to PS
SRVCC.
NOTE 2: MSC Server shown in the above figures are enhanced for CS to PS SRVCC.
NOTE 3: This architecture also applies to roaming scenario.
Figure 5.13e: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with S4 based
SGSN
The reference architecture model, the reference points and the functional entities to support security functions to the
users, devices and network entities when in the EPC are described in TS 33.401 [87] for 3GPP access and in
TS 33.402 [88] for non-3GPP accesses.
The reference configuration is only a logical representation of the entities involved in lawful interception and does not
mandate separate physical entities. There is one Administration Function (ADMF) in the network. Every physical
Intercepting Control Element (ICE) is linked by its own X1_1-interface to the ADMF. Consequently, every single ICE
performs interception (activation, deactivation, interrogation as well as invocation) independently from other ICEs.
3GPP
Release 15 75 3GPP TS 23.002 V15.0.0 (2018-03)
HI1
X1_1
Mediation ADMF
Function
X1_2 X1_3
HI2
X2
Mediation Delivery
Function Function 2
LEMF
Intercepting
HI3 Control
X3
Mediation Delivery Element
Function Function 3
3GPP networks provide functions that implement offline and/or online charging mechanisms on the bearer (e.g. EPC),
subsystem (e.g. IMS) and service (e.g. MMS) levels. In order to support these charging mechanisms, the network
performs real-time monitoring of resource usage on the above three levels in order to detect the relevant chargeable
events.
In offline charging, the resource usage is reported from the network to the Billing Domain after the resource usage has
occurred. In online charging, a subscriber account, located in an Online Charging System, is queried prior to granting
permission to use the requested network resource(s).
Offline and online charging may be performed simultaneously and independently for the same chargeable event.
3GPP
Release 15 76 3GPP TS 23.002 V15.0.0 (2018-03)
Billing Domain
CS -NE
CAP Bx
Service-NE
Bx
Rf SIP AS
MRFC
Ga MGCF
BGCF
CGF CDF IBCF
P-CSCF
I-CSCF Ro
ISC IMS- OCS
S-CSCF GWF
SGSN
CAP
ePDG
TWAG
Rf S-GW
MME
Gyn
TDF
P-GW
Gy
PCEF
PCRF
AF
The Home NodeB Gateway may also be used only for the control plane of Iu-CS and/or Iu-PS interfaces. In this case,
the user plane of Iu-CS and/or Iu-PS interfaces is directly between the Home NodeB and respectively the MSC/VLR
and the SGSN/Serving GW/GGSN.
In case Direct Tunnel is established, the user plane is directly between the Home NodeB Subsystem and the GGSN or
Serving GW nodes.
3GPP
Release 15 77 3GPP TS 23.002 V15.0.0 (2018-03)
The presence of Home eNodeB Gateway in the configuration of Home eNodeB Subsystem is optional.
The Home eNodeB Gateway may also be used only for the S1-MME interface. In this case, the S1-U interface is
directly between the Home eNodeB and the S-GW.
3GPP
Release 15 78 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 79 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 80 3GPP TS 23.002 V15.0.0 (2018-03)
Figure 5.21: Configuration for RAN user plane congestion detection and reporting
Editor's note: either the difference between interface and reference point should be clearly provided, or only one of
the terms should be used.
6.1.2 Interface between User Equipment and Radio Network System (Uu-
interface)
The interface between the UE and the RNS is specified in the 24- and 25-series of Technical Specifications.
6.1.3 Interface between User Equipment and Evolved UTRAN (E-UTRAN Uu-
interface)
The interface between the UE and the E-UTRAN is specified in the 36-series of Technical Specifications.
6.2 Interface between the Core Network and the Access Network
6.2.1 Interfaces between the CS domain and the Access Network
6.2.1.1 Interface between the MSC and Base Station System (A-interface)
The interface between the MSC and its BSS is specified in the 48-series of Technical Specifications.
- BSS management;
- call handling;
3GPP
Release 15 81 3GPP TS 23.002 V15.0.0 (2018-03)
- mobility management.
6.2.1.2 Interface between the MSC and Base Station System (Iu_CS interface)
The interface between the MSC and its BSS is specified in the 25.41x-series of Technical Specifications.
- BSS management;
- call handling;
- mobility management;
- RNS management;
- call handling;
- mobility management.
- mobility management.
The Gb interface is defined in TS 48.014 [44], TS 48.016 [45] and TS 48.018 [46].
- mobility management.
- mobility management.
3GPP
Release 15 82 3GPP TS 23.002 V15.0.0 (2018-03)
6.2.3 Interfaces between the Evolved Packet Core and the Access Network
The interface also allows control of the radio equipment and radio frequency allocation in the BTS.
The interface also allows control of the radio equipment and radio frequency allocation in the Node B.
6.4.1.1 Interface between the MSC server and its associated VLR (B-interface)
The VLR is the location and management database for the mobile subscribers roaming in the area controlled by the
associated MSC server(s). Whenever the MSC server needs data related to a given mobile station currently located in its
area, it interrogates the VLR. When a mobile station initiates a location updating procedure with an MSC server, the
MSC server informs its VLR which stores the relevant information. This procedure occurs whenever an MS roams to
3GPP
Release 15 83 3GPP TS 23.002 V15.0.0 (2018-03)
another location area. Also, when a subscriber activates a specific supplementary service or modifies some data attached
to a service, the MSC server informs (via the VLR) the HLR which stores these modifications and updates the VLR if
required.
This interface is internal to the MSC server /VLR; signalling on it is not standardised.
6.4.1.2 Interface between the HLR and the MSC server (C-interface)
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.
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (see TS 29.002 [26]).
For CAMEL purposes, this interface is used as described in TS 23.078 [10c]. It is used e.g. at terminating calls to
exchange routeing information, subscriber status, location information, subscription information, etc.
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (see TS 29.002 [26]).
For CAMEL purposes, this interface is used to send the CAMEL related subscriber data to the visited PLMN and for
provision of MSRN. The interface is also used for the other purposes described in TS 23.078 [10c], e.g. to retrieve
subscriber status and location information of the mobile subscriber or to indicate suppression of announcement for a
CAMEL service.
6.4.1.4 Interface between MSC servers or MSC server and IP-SM-GW (E-interface)
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 information to transfer A- or Iu-
interface signalling as defined in TS 23.009 [6].
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. or between the IP-SM-GW serving the Mobile Station and the MSC
server which acts as the interface to the SC.
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (see TS 29.002 [26]).
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (see TS 29.002 [26]).
3GPP
Release 15 84 3GPP TS 23.002 V15.0.0 (2018-03)
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (see TS 29.002 [26]).
- full compliance with the H.248 [52] standard, baseline work of which is currently carried out in ITU-T Study
Group 16, in conjunction with IETF MEGACO WG.
- flexible connection handling which allows support of different call models and different media processing
purposes not restricted to H.323 [54] usage.
- open architecture where extensions/Packages definition work on the interface may be carried out.
- dynamic sharing of MGW physical node resources. A physical MGW can be partitioned into logically separate
virtual MGWs/domains consisting of a set of statically allocated Terminations.
- dynamic sharing of transmission resources between the domains as the MGW controls bearers and manage
resources according to the H.248 [52] protocols.
The functionality across the Mc reference point will need to support mobile specific functions such as SRNS
relocation/handover and anchoring. It is expected that current H.248/IETF Megaco [52] standard mechanisms can be
applied to enable this.
6.4.1.8 Reference Point MSC Server – GMSC Server (Nc Reference Point)
Over the Nc reference point, the Network-Network based call control is performed. Examples of this are ISUP or an
evolvement of ISUP for bearer independent call control (BICC). Different options for signalling transport on Nc shall
be possible including IP.
6.4.1.10 Reference Point between the CSS and the VLR (Hv Reference Point)
This reference point is used to transfer to the VLR the CSG subscription information stored in the VPLMN for roaming
UEs.
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (TCAP) (see TS 29.002 [26]).
3GPP
Release 15 85 3GPP TS 23.002 V15.0.0 (2018-03)
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (TCAP) (see TS 29.002 [26]).
Signalling on this interface uses the User Datagram Protocol, UDP/IP [59]. The Gn/Gp interface is defined in
TS 29.060 [51].
- 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) (see
TS 29.002 [26]);
- if there is no SS7 interface in the GGSN, any GSN in the same PLMN and which has an SS7 interface installed
can be used as a GTP to MAP protocol converter, thus forming a signalling path between the GGSN and the
HLR.
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (TCAP) (see TS 29.002 [26]).
6.4.2.5 Reference Point between the CSS and the Gn/Gp SGSN (Ghv Reference
Point)
This reference point is used to transfer to the Gn/Gp SGSN the CSG subscription information stored in the VPLMN for
roaming UEs.
Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction
Capabilities (TCAP) (see TS 29.002 [26]).
Signalling on this interface uses connectionless SCCP (without TCAP). SCCP Global Title (GT) is used for addressing.
The Gs-interface is defined in TS 29.016 [48] and TS 29.018 [49].
3GPP
Release 15 86 3GPP TS 23.002 V15.0.0 (2018-03)
Signalling on the Gd interface uses the Mobile Application Part (MAP) (see TS 29.002 [26]).
The Gdd interface may be used to to transfer short messages between SGSN supporting EPS interfaces, IP-SM-GW and
SMS GMSC/SMS IWMSC.
Signalling on the Gdd interface uses the Diameter SGd application (see TS 29.338 [135]).
The SGs interface is used to provide Fallback for Location Services (LCS) and Call Independent Supplementary
Services (SS).
The SGs interface is also used for the delivery of both mobile originating and mobile terminating SMS over EUTRAN
in case SMSIP is not used.
The signalling on this interface uses SCTP. The SGs interface is defined in TS 23.272 [81] and TS 29.118 [82].
6.4.3.5 Interface between 3GPP MSC Server and MME or SGSN (Sv-interface)
The Sv reference point provides SRVCC support for functions like sending Forward Relocation Message between
MME or SGSN and 3GPP MSC Server. This interface is specified in TS 29.280 [91].
Signalling on this interface uses Diameter S6a/S6d Application as specified in TS 29.272 [86].
Signalling on this interface uses Diameter S6a/S6d Application as specified in TS 29.272 [86].
3GPP
Release 15 87 3GPP TS 23.002 V15.0.0 (2018-03)
Signalling on this interface uses the Diameter S13 Application. in TS 29.272 [86].
3GPP
Release 15 88 3GPP TS 23.002 V15.0.0 (2018-03)
6.4.4.15 Interface between Trusted non-3GPP IP Access and 3GPP AAA Server/proxy
(STa-interface)
It connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication,
authorization, mobility parameters and charging-related information in a secure manner. This interface is specified in
TS 29.273 [96].
6.4.4.16 Interface between 3GPP AAA Server and 3GPP AAA proxy (SWd-interface)
It connects the 3GPP AAA Proxy, possibly via intermediate networks, to the 3GPP AAA Server. This interface is
specified in TS 29.273 [96].
3GPP
Release 15 89 3GPP TS 23.002 V15.0.0 (2018-03)
6.4.4.23 Reference point between 3GPP2 1xCS IWS and MME (S102-reference
point)
The S102 reference point provides a tunnel between MME and 3GPP2 1xCS IWS to relay 3GPP2 1xCS signalling
messages in order to support SRVCC as specified in TS 23.216 [83] and CS Fallback as specified in TS 23.272 [81]. 1x
CS signalling messages are those messages that are defined for A21 interface as described in 3GPP2 A.S0008-C [106].
In case of CS Fallback to 1x CS network as specified in TS 23.272 [81], S102 Tunnel Redirection Procedure is used
when the UE perform Tracking Area Update with MME change (as specified in TS 23.402 [77] in case of S101 tunnel
redirection) while the UE is registered with the 1xRTT CS domain and the S102 session exists between the MME and
the 1xCS IWS.
6.4.4.25 Reference point between UE and CSG List Server (Uh reference point)
This reference point is used to provision the Allowed CSG list and the Operator CSG list subscription information to the
mobile station via OMA DM or OTA. This interface is specified in TS 24.285 [117] for OMA DM and in
TS 31.102 [118] for OTA.
6.4.4.26 Reference Point between the CSS and the S4-SGSN (S7d Reference Point)
This reference point is used to transfer to the S4-SGSN the CSG subscription information stored in the VPLMN for
roaming UEs.
Signalling on this interface uses Diameter S7d Application as specified in TS 29.272 [86].
6.4.4.27 Reference point between the CSS and the MME (S7a reference point)
This reference point is used to transfer to the MME the CSG subscription information stored in the VPLMN for
roaming UEs.
Signalling on this interface uses Diameter S7a Application as specified in TS 29.272 [86].
Signalling on this interface uses Diameter SGd Application as specified in TS 29.338 [135].
3GPP
Release 15 90 3GPP TS 23.002 V15.0.0 (2018-03)
Signalling on this interface uses Diameter S6c Application as specified in TS 29.338 [135].
6a.2 (void)
- Lh interface: interface between GMLC and HLR. This interface is used by the GMLC to request the address of
the visited MSC or SGSN for a particular target UE whose location has been requested (see TS 29.002 [26]).
- Lg interface: interface between GMLC - MSC and GMLC - SGSN. This interface is used by the GMLC to
convey a location request to the MSC or SGSN currently serving a particular target UE whose location was
requested. The interface is used by the MSC or SGSN to return location results to the GMLC (see
TS 29.002 [26]).
- Lc interface: between GMLC and gsmSCF, CAMEL. This interface is used to get location information for
CAMEL based services. (see TS 29.002 [26]).
6a.3.2 (void)
6a.3.3 (void)
6a.3.4 (void)
3GPP
Release 15 91 3GPP TS 23.002 V15.0.0 (2018-03)
In UTRAN, the Lb interface is not standardized, the SMLC functionality is included in SRNC.
Signalling on this interface uses BSSAPP-LE, which is defined in TS 49.031 [50], and SMLCPP, which is specified in
TS 48.031 [47].
In UTRAN, the SMLC functionality is included in SRNC and the Iur interface shall include the Lp interface type of
functionality.
3GPP
Release 15 92 3GPP TS 23.002 V15.0.0 (2018-03)
This interface is also used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues
(relayed via HLR). It is a network operator option whether to support or not USSD operations on this interface.
3GPP
Release 15 93 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 94 3GPP TS 23.002 V15.0.0 (2018-03)
The main procedures that require information transfer between CSCF and HSS are
4) Procedures related to authentication: transfer of security parameters of the subscriber between HSS and CSCF
5) Procedures related to filter control: transfer of filter parameters of the subscriber from HSS to CSCF
The protocol used for the Gm reference point is SIP (as defined by RFC 3261 [61], other relevant RFC's, and additional
enhancements introduced to support 3GPP´s needs).
- full compliance with the H.248 standard functions for IMS – PSTN/PLMN interworking.- flexible connection
handling which allows support of different call models and different media processing purposes not restricted to
H.323 [54] usage.
- open architecture where extensions/Packages definition work on the interface may be carried out.
- dynamic sharing of IMS-MGW physical node resources. A physical IMS-MGW can be partitioned into logically
separate virtual MGWs/domains consisting of a set of statically allocated Terminations.
- dynamic sharing of transmission resources between the domains as the IMS- MGW controls bearers and manage
resources according to the H.248 [52] protocols and functions for IMS.
The protocol used for the Mg reference point is SIP (as defined by RFC 3261 [61], other relevant RFC's, and additional
enhancements introduced to support 3GPP´s needs).
6a.7.5 (void)
6a.7.5a Reference Point AS-MRFC for media control (Cr Reference Point)
The Cr reference point allows interaction between an Application Server and an MRFC for media control.
3GPP
Release 15 95 3GPP TS 23.002 V15.0.0 (2018-03)
The Cr reference point enables the MRFC to fetch and cache documents and resources from an Application Server and
to return data to an Application Server.
The Cr reference point enables media control protocol requests, responses and notifications to be sent between the
MRFC and an Application Server.
6a.7.5b Reference Point AS-MRFC for session control (Mr′ Reference Point)
The Mr' reference point allows interaction between an Application Server and an MRFC for session control without
passing through an S-CSCF.
The protocol used for the Mr reference point is SIP (as defined by RFC 3261 [61], other relevant RFC's, and additional
enhancements introduced to support 3GPP´s needs).
- Open architecture where extensions (packages) definition work on the interface may be carried out.
6a.7.8 (void)
6a.7.9 (void)
3GPP
Release 15 96 3GPP TS 23.002 V15.0.0 (2018-03)
This interface is not required in a single HSS environment. An example for a single HSS environment is a server farm
architecture.
6a.7.16 Reference Point HSS – SIP AS or OSA SCS (Sh Reference Point)
The Application Server (SIP Application Server and/or the OSA Service Capability Server) may communicate to the
HSS. The Sh interface is used for this purpose. Details are described in TS 23.228 [34], clause 4.2.4.
3GPP
Release 15 97 3GPP TS 23.002 V15.0.0 (2018-03)
This reference point is also used to exchange signalling between IP-SM-GW and the HSS for SMSIP delivery.
The Ut interface enables the user to manage information related to his services. Such as creation and assignment of
Public Service Identities, management of authorization policies that are used e.g. by Presence service, conference policy
management, etc.
The AS may need to exhibit security related functions for the Ut interface, the details of these security functions are
described in TS 33.222 [72].
This interface is not required in a single HSS environment. An example for a single HSS environment is a server farm
architecture.
- forward SIP requests destined to a Public Service Identity hosted by an Application Server directly to the
Application Server. Details are described in TS 23.228 [34], clause 5.4.12; and
- initiate a request on behalf of a user or Public Service Identity, if the AS has no knowledge of the serving
S-CSCF for that user or Public Service Identity. Details are described in TS 23.228 [34], clause 5.6.5.3.
3GPP
Release 15 98 3GPP TS 23.002 V15.0.0 (2018-03)
6a.7.26 Void
- An MSC Server enhanced for ICS and SRVCC, as defined in TS 23.292 [110], TS 23.216 [83] and
TS 23.237 [111].
- An MSC Server enhanced for ICS and SRVCC with the MSC Server assisted mid-call feature as defined in
TS 23.237 [111].
- An MSC Server enhanced for ICS and SRVCC with the SRVCC for call in alerting phase feature as defined in
TS 23.237 [111].
6a.8 Void
3GPP
Release 15 99 3GPP TS 23.002 V15.0.0 (2018-03)
6a.9.1 Reference point 3GPP AAA Server - HLR (D'/Gr' Reference Point)
This is the reference point between the 3GPP AAA server and the HLR up to and including Rel-4 and the HSS in Rel-5.
The functionality of this reference point is similar to that of the Wx reference point. For more information see
TS 23.234 [67].
6a.9.2 Reference point WLAN access network - 3GPP AAA Proxy/Server (Wa
Reference Point)
This is the reference point between the WLAN access network and 3GPP AAA Proxy or Server. The AAA protocol on
this reference point is used to transport authentication, authorization and charging data.
6a.9.3 Reference point 3GPP AAA Server – 3GPP AAA Proxy (Wd Reference
Point)
This is the reference point between the 3GPP AAA Server and Proxy. the purpose of the protocols crossing this
reference point is to transport authentication, authorization and related information. For more information see
TS 23.234 [67].
6a.9.4 Reference point 3GPP AAA Server/Proxy - WAG (Wg Reference Point)
This is the reference point between the 3GPP AAA server/proxy and WAG. It is used to provide information needed by
the WAG to perform policy enforcement functions for authorised users and to transport per-tunnel based charging
information from the WAG to the AAA Proxy in roaming scenarios.
6a.9.5 Reference point PDG - packet data networks (Wi Reference Point)
This is the reference point between the PDG and a packet data network. It may be an operator external public or private
packet data network or an intra operator packet data network, e.g. for provision of IMS services.
- The 3GPP AAA Server/Proxy to retrieve tunnelling attributes and WLAN UE's IP configuration parameters
from/via Packet Data Gateway
- Carrying authentication data for the purpose of tunnel establishment, tunnel data authentication and encryption.
6a.9.7 Reference Point WAG - WLAN access network (Wn Reference Point)
This is the reference point between the WAG and the WLAN access network. It is used to force traffic between a
WLAN UE and PDG to go through the WAG.
3GPP
Release 15 100 3GPP TS 23.002 V15.0.0 (2018-03)
6a.9.11 Reference point 3GPP AAA Server - HSS (Wx Reference Point)
This is the reference point between the 3GPP AAA server and HSS. The functionality of this reference point is to
enable:
- Registration of the 3GPP AAA Server of an authorised WLAN user in the HSS
6a.9.12 Reference point 3GPP AAA Server - SLF (Dw reference point)
This reference point is between the 3GPP AAA Server and the SLF. The prime purpose of the protocol(s) crossing this
reference point is to enable the 3GPP AAA Server to find the address of the HSS which holds the subscriber data for a
given user identity in a configuration with multiple separately addressable HSSs.
3GPP
Release 15 101 3GPP TS 23.002 V15.0.0 (2018-03)
6a.10.3 Reference point GGSN – RNS (or BSS Iu mode) (Gmc Reference
Point)
This reference point is used between GGSN and RNS (or BSS Iu mode) for MBMS data delivery using IP multicast.
The details for this reference point are described in TS 23.246 [70] and TS 29.281 [126].
3GPP
Release 15 102 3GPP TS 23.002 V15.0.0 (2018-03)
The Rg reference point allows applications to create, read, modify and delete any user profile data using the harmonized
access interface. The GUP Server locates the data repositories responsible of the storage of the requested profile
component(s).
6a.12.2 Reference Point GUP Server – HSS and Applications – HSS (Rp
Reference Point)
The Rp reference point resides between the GUP Server and the HSS, and between the Applications and the HSS.
The Rp reference point enables the GUP Server and the Applications to access GUP Data Repositories. The HSS is one
of the GUP Data Repositories. It stores the IM CN Subsystem user related data.
3GPP
Release 15 103 3GPP TS 23.002 V15.0.0 (2018-03)
Gxb* is only applicable to the interworking with Fixed Broadband Access network.
3GPP
Release 15 104 3GPP TS 23.002 V15.0.0 (2018-03)
S15 is only applicable to the interworking with Fixed Broadband Access network.
S9a is only applicable to the interworking with Fixed Broadband Access network.
6a.13.18 Void
6a.13.20 Reference point between PFDF and PCEF (Gw reference point)
The Gw reference point enables the PFDF to provide PFDs to the PCEF as described in TS 23.203 [73].
6a.13.21 Reference point between PFDF and TDF (Gwn reference point)
The Gwn reference point enables the PFDF to provide PFDs to the TDF as described in TS 23.203 [73].
3GPP
Release 15 105 3GPP TS 23.002 V15.0.0 (2018-03)
This interface is a PLMN internal interface if the SCS is controlled by the operator.
Signalling on this interface uses Diameter Tsp Application as specified in TS 29.368 [136].
NOTE: See clause 7.8 when the SCS is not controlled by the operator.
The details for this reference point are described in TS 23.682 [132] and TS 29.336 [133].
Signalling on this interface uses Diameter S6m Application as specified in TS 29.336 [133].
The details for this reference point are described in TS 23.682 [132] and TS 29.336 [133].
Signalling on this interface uses Diameter S6n Application as specified in TS 29.336 [133].
The details for this reference point are described in TS 23.682 [132] and TS 29.337 [134].
6a.16.5 Reference point between the HSS and the SCEF (S6t reference
point)
The S6t reference point is defined between the SCEF and the HSS. It provides general access to the capabilities and
data of the HSS from the SCEF, including configuration and reporting of specific monitoring events.
The details for this reference point are described in TS 23.682 [132].
6a.16.6 Reference point between the MME and the SCEF (T6a reference
point)
The T6a reference point is defined between the SCEF and the MME. It provides general access to the capabilities of the
MME from the SCEF, including configuration and reporting of specific monitoring events.
The details for this reference point are described in TS 23.682 [132].
3GPP
Release 15 106 3GPP TS 23.002 V15.0.0 (2018-03)
6a.16.7 Reference point between the SGSN and the SCEF (T6b reference
point)
The T6b reference point is defined between the SCEF and the SGSN. It provides general access to the capabilities of the
SGSN from the SCEF, including configuration and reporting of specific monitoring events.
The details for this reference point are described in TS 23.682 [132].
6a.16.8 Reference point between the RCAF and the SCEF (Ns reference
point)
The Ns reference point is defined between the SCEF and the RCAF. It allows the SCEF to request and consequently be
notified of the network status.
The details for this reference point are described in TS 23.682 [132].
6a.16.9 Reference point between the PCRF and the SCEF (Nt reference
point)
This reference point allows for negotiation about the recommended time window(s) and the related conditions for future
background data transfer between the Policy and Charging Rules Function (PCRF) and the Service Capability Exposure
Function (SCEF). For more information see TS 23.203 [73].
6a.16.10 Reference point between the PFDF and the SCEF (Nu reference
point)
This reference point enables the Service Capability Exposure Function (SCEF) to manage Packet Flow Descriptions
(PFDs) in the Packet Flow Description Function (PFDF) according to the instructions received from the SCS/AS. For
more information see TS 23.682 [132].
3GPP
Release 15 107 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP
Release 15 108 3GPP TS 23.002 V15.0.0 (2018-03)
6a.19.2 Reference point between MME and RCAF (Nq reference point)
The Nq reference point enables the RCAF to retrieve the list of UEs (identified by the IMSIs) served by an eNB or E-
UTRAN cell and the list of APNs of the active PDN connections of each IMSI. The Nq reference point is specified in
TS 23.401 [76].
6a.19.3 Reference point between SGSN and RCAF (Nq' reference point)
The Nq' reference point enables the RCAF to retrieve the list of APNs of the active PDN connections of a given UE
(identified by the IMSI). The Nq' reference point is specified in TS 23.060 [9a].
3GPP
Release 15 109 3GPP TS 23.002 V15.0.0 (2018-03)
7.5 (void)
This interface is an interface between the PLMN and other networks if the SCS is not controlled by the operator.
3GPP
Release 15 110 3GPP TS 23.002 V15.0.0 (2018-03)
Annex A (informative):
Description for GLR-related entities and interfaces
This annex describes the GLR-related entities and the interfaces. This annex is an informative annex. The 'informative'
means just that the GLR is an optional functional entity to optimize signalling traffic between PLMNs. Therefore, this
annex is normative to a PLMN which introduce the GLR.
The GLR is only applicable for GERAN and UTRAN access. The GLR is not applicable to the EPC.
The GLR is a logical node and acts as a VLR for MAP signalling (e.g. PRN) from the HPLMN point of view. The GLR
acts as a HLR for MAP signalling (e.g. Register SS) from the VPLMN point of view.
The GLR also acts as an SGSN for MAP signalling only (e.g. ISD) from the HPLMN point of view. This is because
MAP operations such as ISD must be terminated at the GLR for the purpose of subscriber data caching.
3GPP
Release 15 111 3GPP TS 23.002 V15.0.0 (2018-03)
The GLR shall terminate all TC dialogues and start new dialogues towards the HLR or the VLR. The GLR shall
generate SCCP address of the HLR (i.e. E.214 MGT) from IMSI.
- The Intermediate MSC (IM-MSC) is a logical node and represents the VMSC in the GLR equipped VPLMN.
- The IM-MSC acts as the VMSC for the HPLMN in the same way that the GLR acts as a VLR for HPLMN. The
IM-MSC terminates MAP signalling from the HPLMN towards the VMSC and forwards the signal to the actual
VMSC.
- The IM-MSC has an address interrogation function with which it is able to obtain the actual VMSC Number
from the GLR.
- The IM-MSC is implemented in the same physical node as the one in which the GLR is implemented.
- The GLR alters the VMSC Number to the IM-MSC Number within an Update Location message.
- The IM-MSC Number is the E.164 Number assigned to the IM-MSC [53].
The IM-GSN acts as an SGSN for only some GTP signalling messages (i.e. PDU_Notification request/response,
PDU_Notification_reject request/response) from the HPLMN point of view. The IM-GSN terminates these GTP
signalling messages from the HPLMN towards SGSN and forwards the signal to the actual SGSN. The IM-GSN has an
address interrogation function with which it is able to request the actual SGSN address from the GLR.
Apart from the case described above (i.e. PDU_Notification request/response, PDU_Notification_reject
request/response), all other GTP signalling should be handled directly between the SGSN and the GGSN.
NOTE: MAP signalling towards the SGSN is NOT terminated at the IM-GSN. Instead it is terminated at the
GLR.
3GPP
Release 15 112 3GPP TS 23.002 V15.0.0 (2018-03)
SGSN VLR/MSC
GLc GLb
GLk
GLh
GLe GLd
IM-GSN GLR IM-MSC
GLg
GLa
GLj GLi
GLf
GGSN HLR SMS-GMSC GMLC
Other PLMN
Signalling interface
User traffic interface. User traffic includes Short Message.
3GPP
Release 15 113 3GPP TS 23.002 V15.0.0 (2018-03)
The SMS-GMSC regards the GLR as the SGSN via this interface.
The SMS-GMSC regards the IM_MSC as the MSC via this interface.
The GMLC regards the IM_MSC as the MSC via this interface.
3GPP
Release 15 114 3GPP TS 23.002 V15.0.0 (2018-03)
Annex B (informative):
Change history
Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New
version
09/1999 - - - - - renumbering of the present document from 03.02 to 23.002 (23.002 23.002v
v.3.0.0 identical to 03.02 v.7.0.0) 3.0.0
09/2010 SP-49 SP-100555 0222 1 B Addition of GTP based S2b in the 3GPP network architecture 10.0.0
09/2010 SP-49 SP-100557 0223 - F Updates to IM Subsystem figure for E-CSCF and IBCF 10.0.0
09/2010 SP-49 SP-100557 0225 - F Architecture update of SRVCC architecture enhanced with ATCF 10.0.0
09/2010 SP-49 SP-100557 0227 1 F Introducing Ud interface between UDR and PCRF 10.0.0
12/2010 SP-50 SP-100674 0231 - A Correction of MGCF definition to make it consistent with TS 29.235 10.1.0
01/2011 - - - - - Update of LTE logo to LTE-Advanced logo 10.1.1
03/2011 SP-51 SP-110075 0228 2 F Correction on the reference of S2b interface 10.2.0
03/2011 SP-51 SP-110070 0232 - B Add LIPA_SIPTO in 23002 10.2.0
09/2011 SP-53 SP-110456 0238 2 A Correcting the definition of I2 10.3.0
09/2011 SP-53 SP-110460 0239 1 F MBMS support in EPS 10.3.0
09/2011 SP-53 SP-110468 0240 2 B Introduction of the CSG Subscriber Server entity and interfaces 11.0.0
12/2011 SP-54 SP-110737 0244 - A Adding missing ACTF to IMS entities clause 11.1.0
03/2012 SP-55 SP-120087 0242 2 F Clarification on GUP data repository's role as logical function in the 11.2.0
HSS
03/2012 SP-55 SP-120087 0245 - F Editorial and reference corrections to 23.002 11.2.0
03/2012 SP-55 SP-120085 0246 - B Clarifications for SaMOG in 23.002 11.2.0
06/2012 SP-56 SP-120244 0247 1 F Corrections related to SAPP introduction in the Network Architecture 11.3.0
specification
06/2012 SP-56 SP-120238 0248 1 F Corrections related to QoS_SSL introduction in the Network 11.3.0
Architecture specification.
06/2012 SP-56 SP-120248 0250 1 B Introduction of CS to PS SRVCC architecture 11.3.0
06/2012 SP-56 SP-120241 0251 4 F BBAI update for architecture, entity and interface function 11.3.0
09/2012 SP-57 SP-120482 0253 1 B SIMTC update for architecture, entities and interfaces 11.4.0
09/2012 SP-57 SP-120474 0254 - F Reference list correction to align with the corrected TS 29.212 title 11.4.0
09/2012 SP-57 SP-120487 0252 - F Correction to the IMS architecture diagram: Addition of missing Mm 12.0.0
interface between I-CSCF and IP Multimedia Networks
12/2012 SP-58 SP-120714 0256 1 A Clarifying that MSC Server assisted mid-call feature does not imply 12.1.0
I2 interface
12/2012 SP-58 SP-120881 0260 - A Adding the missing ATGW to IMS entities description clause 12.1.0
06/2013 SP-60 SP-130305 0262 2 A Clarification on the reference of SGd and S6c 12.2.0
06/2013 SP-60 SP-130310 0263 2 B Adding SIPTO at the Local Network 12.2.0
06/2013 SP-60 SP-130230 0264 2 B Introduction of Gyn/Gzn interfaces to the specification 12.2.0
12/2013 SP-62 SP-130535 0267 1 B Addition of Diameter Gdd interface for SMS with SGSN 12.3.0
12/2013 SP-62 SP-130538 0268 - B Add New Interface Description between MME and HRPD AN 12.3.0
12/2013 SP-62 SP-130533 0269 2 B Introduce TCP proxy to the 3GPP network 12.3.0
12/2013 SP-62 SP-130535 0270 1 B Introduction of Lgd 12.3.0
03/2014 SP-63 SP-140112 0271 2 F Missing PSS Server Information 12.4.0
03/2014 SP-63 SP-140101 0272 2 B Adding the IMS WebRTC architecture 12.4.0
06/2014 SP-64 SP-140259 0273 2 B adding MB2 to TS 23.002 due to GCSE_LTE feature. 12.5.0
09/2014 SP-65 SP-140428 0277 2 B Introduction of RCAF and its interfaces into Network Architecture 13.0.0
12/2014 SP-66 SP-140686 0279 1 A Interface between IM-SSF and HSS 13.1.0
12/2014 SP-66 SP-140685 0281 - A Corrections to charging architecture 13.1.0
06/2015 SP-68 SP-150236 0283 2 B Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points 13.2.0
06/2015 SP-68 SP-150235 0284 2 B Introducing SCEF and RCAF Reference Point 13.2.0
09/2015 SP-69 SP-150498 0285 - F Adding Nt reference point to architecture 13.3.0
09/2015 SP-69 SP-150492 0286 1 B Introduction of FMSS into the network architecture 13.3.0
09/2015 SP-69 SP-150504 0287 2 B Adding MCPTT related function and reference points 13.3.0
12/2015 SP-70 SP-150608 0288 1 F Clarification on PCC architecture of Nt reference point 13.4.0
03/2016 SP-71 SP-160162 0290 - F Correction to Charging architecture 13.5.0
06/2016 SP-72 SP-160296 0291 1 A Correction of conflicting CRs 0282 and 0283 13.6.0
09/2016 SP-73 SP-160643 0295 2 F Inclusion of IMS Access Gateway 13.7.0
09/2016 SP-73 SP-160643 0296 2 F Inclusion of Mb Interface for TrGW 13.7.0
09/2016 SP-73 SP-160643 0297 - F Correcting the Mb reference point description 13.7.0
09/2016 SP-73 SP-160655 0293 2 B Adding new network entity and reference points for SDCI 14.0.0
09/2016 SP-73 SP-160655 0294 1 B Architecture enhancement for SDCI 14.0.0
09/2016 SP-73 SP-160650 0301 1 B Additions of new entities, configurations, reference points and 14.0.0
references to TS 23.002 for CUPS
03/2017 SP-75 SP-170049 0302 - F Introduction of xMB reference point and Exposure via SCEF 14.1.0
03/2018 SP-79 SP-180113 0303 - F Inclusion of the Ms reference point 15.0.0
03/2018 SP-79 SP-180094 0304 2 B Adding 5GS to the Network Architecture 15.0.0
3GPP
Release 15 115 3GPP TS 23.002 V15.0.0 (2018-03)
3GPP