tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

3GPP Glossaries

|   Features_Services   |   Network_Entities   |   Reference_Points   |   SIM_UICC_Dir_Files   |   Identifiers   |

 

Interfaces / Reference Points

Y

 

 

 

Here          Top

|   G   |   Ga   |   Gb   |   Gc   |   GC1   |   Gd   |   Gdd   |   Ge   |   Gf   |   Ghv   |   Gi   |   GLa   |   GLb   |   GLc   |   GLd   |   GLe   |   GLf   |   GLg   |   GLh   |   GLi   |   GLj   |   GLk   |   Gm   |   Gmb   |   Gmc   |   Gn/Gp   |   Go   |   Gp   |   Gq   |   Gr   |   Gs   |   Gx   |   Gxa   |   Gxb   |   Gxb*   |   Gxc   |   Gxx   |   Gy   |   Gya   |   Gyn   |   Gz   |   Gza   |   Gzn   |

 


between  VLR  and  VLR

specified from  GSM Rel-96
Source:   TS 23.002, clause 6.4.1.6 

When a mobile subscriber moves from a VLR area to another VLR area, a Location Registration procedure will happen. This procedure may include the retrieval of the IMSI and authentication parameters from the old VLR.

Signalling on this interface uses MAP (TS 29.002).

Up       Top


between  CDF  and  CGF

specified from  Rel-6
in  TS 32.240, clause 4.4.1.3 

GTP' has been designed to deliver the CDR(s) from the CDF, which generates CDRs to the CGF(s). This protocol is required if the CGF resides outside the CDFs. It utilizes some aspects of GTP (defined in TS 29.060), which is used for packet data tunnelling in the backbone network.

GTP' operates on the Ga interface and does not imply the use of any specific backbone network.

GTP' performs the following functions:
  • CDR transfer between the CDF and the CGF.
  • Redirection of CDRs to another CGF.
  • Detect communication failures between the communicating peers, using echo messaging.
  • Advertise to peers about its CDR transfer capability (e.g., after a period of service downtime).
  • Prevents duplicate CDRs that might arise during redundancy operations. If so configured, the CDR duplication prevention function may also be carried out by marking potentially duplicated CDR packets, and, delegating the final duplicate deletion task to a CGF or the Billing Domain (instead of handling the possible duplicates solely by GTP' messaging).

Up       Top


between  SGSN  and  BSS

specified from  GSM Rel-97
Source:   TS 23.002, clause 6.2.2.1 

This interface is used to carry information concerning:
  • packet data transmission;
  • mobility management.
The Gb interface is defined in the TS 48.01x series.

Up       Top


between  GGSN  and  HLR

specified from  GSM Rel-96
Source:   TS 23.002, clause 6.4.2.3 

This optional signalling path may be used by the GGSN to retrieve information about the location and supported services for the mobile subscriber, to be able to activate a packet data network address.

There are two alternative ways to implement this signalling path:
  • If an SS7 interface is implemented in the GGSN, signalling between the GGSN and the HLR uses MAP.
  • 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.

Up       Top


between  GCS AS  and  UE Application

specified from  Rel-12
Source:   TS 23.468, clause 4.3.2.1 

Up       Top


between  SGSN / IP-SM-GW  and  SMS-GMSC / SMS-IWMSC

specified from  Rel-6
Source:   TS 23.002, clause 6.4.3.3 

This interface is used to transfer short messages between SGSN/IP-SM-GW and SMS-GMSC or SMS-IWMSC over GPRS.

Signalling on this interface uses MAP (TS 29.002).

Up       Top


between  SGSN  and  SMS-GMSC / SMS-IWMSC

specified from  Rel-11
in  TS 23.040  and  TS 29.338 

The Gdd reference point is used to transfer short messages between the SGSN, the SMS-IWMSC, the SMS-GMSC and the SMS Router, and the alerting of the SMS-GMSC by the SGSN (possibly via an SMS Router),.

Commands:
  • OFR/OFA:  MO-Forward-Short-Message-Request/Answer
  • TFR/TFA:  MT-Forward-Short-Message-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  gprsSSF  and  gsmSCF

specified from  GSM Rel-97
Source:   TS 23.002, clause 6a.4.8 

This interface is used by the gsmSCF to control a GPRS session or individual PDP Context in a certain gprsSSF. Relationships between the gprsSSF and the gsmSCF (GPRS dialogues) on this interface are opened as a result of the gprsSSF sending a request for instructions to the gsmSCF. See TS 23.060.

Up       Top


between  SGSN  and  EIR

specified from  GSM Rel-97
Source:   TS 23.002, clause 6.4.2.4 

Signalling on this interface uses MAP (TS 29.002).

Up       Top


between  CSS  and  SGSN

specified from  Rel-11
Source:   TS 23.002, clause 6.4.2.5 

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).

Up       Top


between  GGSN  and  PDN (Packet Data Network)

specified from  GSM Rel-97
Source:   TS 23.002, clause 7.2 

This is the reference point between the GGSN 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.

Up       Top


between  HLR  and  GLR

specified from  Rel-3
Source:   TS 23.002, clause A.5.1 

In circuit switched domain, this interface is the same as that between the VLR and the HLR (see TS 29.002). The HLR regards the GLR as the VLR via this interface.

On the other hand, in packet switched domain, this interface is the same as that between the SGSN and the HLR (see TS 29.002). The HLR regards the GLR as the SGSN via this interface.

Up       Top


between  VLR  and  GLR

specified from  Rel-3
Source:   TS 23.002, clause A.5.2 

This interface is the same as those between the VLR and the HLR (see TS 29.002). The VLR regards the GLR as the HLR via this interface.

Up       Top


between  SGSN  and  GLR

specified from  Rel-3
Source:   TS 23.002, clause A.5.3 

This interface is the same as those between the SGSN and the HLR (see TS 29.002). The SGSN regards the GLR as the HLR via this interface.

Up       Top


between  GLR  and  IM_MSC

specified from  Rel-3
Source:   TS 23.002, clause A.5.4 

In the network with the GLR, when the IM_MSC receives a message, it interrogates the GLR for the routing information of the MSC. However, this interface is internal because GLR and IM-MSC are implemented in the same physical node and the protocol on this interface is not specified.

Up       Top


between  GLR  and  IM_GSN

specified from  Rel-3
Source:   TS 23.002, clause A.5.5 

In the network with the GLR when the IM_GSN receiving a PDU notification from the GGSN, the IM_GSN relays the notification to the SGSN by interrogating via the interface the routing information to the GLR. The interrogation uses the same operation on the interface between the SGSN and the HLR (see TS 29.002).

Up       Top


between  SMS-GMSC  and  GLR

specified from  Rel-3
Source:   TS 23.002, clause A.5.6 

This interface is used to forward mobile-terminated short messages in the network with the GLR in case of SMS transfer over GPRS. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002).

The SMS-GMSC regards the GLR as the SGSN via this interface.

Up       Top


between  SMS-GMSC  and  IM_MSC

specified from  Rel-3
Source:   TS 23.002, clause A.5.7 

This interface is used to forward short messages in the network with the GLR in case of SMS transfer over non-GPRS. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002).

The SMS-GMSC regards the IM_MSC as the MSC via this interface.

Up       Top


between  MSC  and  IM_MSC

specified from  Rel-3
Source:   TS 23.002, clause A.5.8 

This interface is used to forward short messages in the network with the GLR in case of SMS transfer over non-GPRS. Also this interface is used to exchange data needed by the MSC to perform subscriber authorization and allocate network resources. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002).

Up       Top


between  GMLC  and  IM_MSC

specified from  Rel-3
Source:   TS 23.002, clause A.5.9 

Also this interface is used to exchange data needed by the MSC to perform subscriber authorization and allocate network resources. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002).

The GMLC regards the IM_MSC as the MSC via this interface.

Up       Top


between  GGSN  and  IM_GSN

specified from  Rel-3
Source:   TS 23.002, clause A.5.10 

In the network with the GLR when receiving a PDP PDU from the external network the GGSN sends a notification to the IM_GSN by the routing information from the HLR (see TS 29.060). The GGSN regards the IM_GSN as the SGSN via this interface.

Up       Top


between  SGSN  and  IM_GSN

specified from  Rel-3
Source:   TS 23.002, clause A.5.11 

In the network with the GLR when receiving a PDP notification from the GGSN, the IM_GSN relays the notification to the SGSN by the routing information from the GLR (see TS 29.060). The SGSN regards the IM_GSN as the GGSN via this interface.

Up       Top


between  UE  and  P-CSCF

specified from  Rel-5
Source:   TS 23.002, clause 6a.7.2 

The Gm reference point supports the SIP-based communication between a UE and a P-CSCF (acting as a SIP Proxy) in an IMS core network. The P-CSCF may be located in a visited IMS core network or in the User's Home IMS core network.

Up       Top


between  GGSN  and  BM-SC

specified from  Rel-6
Source:   TS 23.002, clause 6a.10.1 

This reference point is used to exchange signalling between GGSN and a Broadcast-Multicast Service Centre (BM-SC). This represents the network side boundary of the MBMS Bearer Service from a control plane perspective. This includes user specific Gmb signalling and MBMS bearer service specific signalling.

The details for this reference point are described in TS 23.246.

Up       Top


between  GGSN  and  RNS

specified from  Rel-10
Source:   TS 23.002, clause 6a.10.3 

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 and TS 29.281.

Up       Top


between  SGSN  and  GGSN / SGSN

specified from  GSM Rel-97
Source:   TS 23.002, clause 6.4.2.2 

These interfaces are used to support mobility between the SGSN and GGSN. The Gn interface is used when GGSN and SGSN are located inside one PLMN. The Gp-interface is used if GGSN and SGSN are located in different PLMNs.

The Gn/Gp interface also includes a part which allows SGSNs to communicate subscriber and user data, when changing SGSN.

Signalling on this interface uses UDP/IP. The Gn/Gp interface is defined in TS 29.060.

Up       Top


between  GGSN  and  PDF

specified from  Rel-5   to  Rel-6
Source:   TS 23.002, Rel-6 

This interface allows the Policy Decision Function (PDF) to apply policy to the bearer usage in the GGSN.

Policy control over Go interface is defined in TS 23.207, for R5 and R6 only.

Up       Top


between  SGSN  and  GGSN

specified from  GSM Rel-97
Source:   TS 23.002, clause 6.4.2.2 

Equivalent to Gn but in different PLMNs.

Up       Top


between  AF  and  PDF

specified for  Rel-6
Source:   TS 23.002, Rel-6 

This interface allows for dynamic QoS-related service information to be exchanged between the Policy Decision Function (PDF) and the Application Function (AF). This information is used by the PDF for service based local policy decisions.

For more information see TS 23.207, for R6 only.

Up       Top


between  SGSN  and  HLR

specified from  GSM Rel-97
Source:   TS 23.002, clause 6.4.2.1 

This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The SGSN informs the HLR of the location of a mobile station managed by the latter. The HLR sends to the SGSN all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.

Signalling on this interface uses MAP (TS 29.002).

Up       Top


between  MSC/VLR  and  SGSN

specified from  GSM Rel-97
in  TS 29.016  and  TS 29.018 

The Gs interface is used to provide co-ordination between the GSM circuit switched services controlled at the Visitor Location Register (VLR) and the GSM packet switched services controlled at the Serving GPRS Support Node (SGSN). The procedures on the Gs interface are intended to optimise the use of the resources when an MS supports both GSM circuit switched services and GSM packet switched services.

Up       Top


between  PCEF  and  PCRF / H-PCRF / V-PCRF

specified from  Rel-7
in  TS 23.203  and  TS 29.212 

The Gx reference point is used for provisioning and removal of PCC rules from the PCRF to the PCEF and the transmission of traffic plane events from the PCEF to the PCRF. The Gx reference point can be used for charging control, policy control or both by applying AVPs relevant to the application. The Gx reference point can also be used for application's traffic detection and control.

Commands:
  • CCR/CCA:  CC-Request/Answer
  • RAR/RAA:  Re-Auth-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  Trusted non-3GPP IP Access  and  PCRF / V-PCRF

specified from  Rel-8
in  TS 23.203 / TS 23.402  and  TS 29.212 

See Gxx.

Up       Top


between  ePDG  and  PCRF / V-PCRF

defined from  Rel-8
Source:   TS 23.002, clause 6a.13.7 

This interface is not specified yet (as per Rel-13).

Up       Top


between  ePDG  and  PCRF / V-PCRF

specified from  Rel-11
Source:   TS 23.002, clause 6a.13.7a 

The reference point transports access information from ePDG to PCRF/vPCRF for WLAN UEs such as the UE local IP address and the UDP port number. This interface is specified in TS 29.212.

Gxb* is only applicable to the interworking with Fixed Broadband Access network.

Up       Top


between  S-GW  and  PCRF / V-PCRF

specified from  Rel-8
in  TS 23.203  and  TS 29.212 

See Gxx.

Up       Top


between  PCRF  and  BBERF

specified from  Rel-8
in  TS 23.203 / TS 23.402  and  TS 29.212 

The Gxx reference point is located between the Policy and Charging Rules Function (PCRF) and the Bearer Binding and Event Reporting Function (BBERF). Gxc applies when the BBERF is located in the S-GW and Gxa applies when the BBERF is located in a trusted non-3GPP access.

The Gxx reference point is used for:
  • Provisioning, update and removal of QoS rules from the PCRF to the BBERF;
  • Transmission of traffic plane events from the BBERF to the PCRF.
Commands:
  • CCR/CCA:  CC-Request/Answer
  • RAR/RAA:  Re-Auth-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.

Up       Top


between  OCS  and  PCEF 

specified from  Rel-8
Source:   TS 23.203, clause 5.2.4 

The Gy reference point allows online credit control for service data flow based charging. The functionalities required across the Gy reference point are defined in TS 32.251 and RFC 4006.

Up       Top


between  OCS  and  ACC IF 

specified from  Rel-12
Source:   TS 23.203, clause S.8.4 

The Gya reference point is located between the Accounting Interworking function in the BBF defined Access Network and the 3GPP online charging system OCS located in the HPLMN and it transports charging information for 3GPP UE.

The Gya reference point is located between the Accounting Interworking function in the BBF defined Access Network and the 3GPP online charging system located in the HPLMN and it transports charging information for fixed device.

Up       Top


between  OCS  and  TDF

specified from  Rel-12
Source:   TS 23.203, clause 5.2.10 

The Gyn reference point allows online credit control for charging in case of ADC rules based charging in TDF. The functionalities required across the Gyn reference point are defined in TS 32.251 and RFC 4006.

Up       Top


between  OFCS  and  PCEF

specified from  Rel-8
Source:   TS 23.203, clause 5.2.5 

The Gz reference point enables transport of service data flow based offline charging information.

According to TS 32.240, clause 4.4.1.2, the Gz reference point is functionally equivalent to Ga for Legacy PS domain and to Ga or Rf for Evolved PS domain, and hence is replaced by Ga or Rf within the common charging architecture.

Up       Top


between  OFCS  and  ACC IF

specified from  Rel-7
Source:   TS 23.203, clause S.8.3 

To transport charging information about 3GPP UE, the Gza reference point is located between Accounting Interworking function in the BBF defined network and the 3GPP offline charging system OFCS located in the VPLMN (roaming scenario) or in the HPLMN (non-roaming scenario).

To transport charging information about fixed devices, the Gza reference point is located between the Accounting Interworking function in the BBF defined network and the 3GPP offline charging system located in the HPLMN (only non-roaming scenario).

Up       Top


between  OFCS  and  TDF

specified from  Rel-12
Source:   TS 23.203, clause 5.2.11 

The Gzn reference point enables transport of offline charging information in case of ADC (Application Detection and Control) rule based charging in TDF.

According to TS 32.240, clause 4.4.1.6, The Gzn reference point is functionally equivalent to Ga or Rf in PS domain, and hence is replaced by Ga or Rf within the common charging architecture.

Up       Top