tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

3GPP Glossaries

 

 

Network entities

D

F

J

K

X

Y

Z

 

 

 

Here          Top

GANC     # GBA     # GCR     # GCS AS     # GGSN     # GLR     # GMLC     # GMSC     # gprsSSF     # gsmSCF     # gsmSSF     # gsmSRF     # GUP Server    

 

GANC  —  Generic  Access  Network  Controller

[GAN  R6]+

The core network interacts with the Generic Access Network Controller (GANC) as though it was an A/Gb mode BSS (GAN A/Gb mode) or an RNC (GAN Iu mode).

Source:   TS 43.318, clause 5.2

Up       Top

GBA  —  Generic  Bootstrapping  Architecture

[GAA  R6]+

GBA is an application independent mechanism based on the 3GPP AKA mechanism to provide a client and an application server with a common shared secret. This shared secret can subsequently be used to authenticate the communication between the client and an application server.

Source:   TR 33.919, clause 5.2

Up       Top

GCR  —  Group  Call  Register

[CS Domain  R97]+

The GCR is a register holding information about VGCS or VBS calls, the voice group or broadcast call attributes, respectively. 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 GCR shall hold for a related MSC area for each group ID and cell from which VGCS or 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.

Source:   TS 23.002, clause 4a.1

Up       Top

GCS AS  —  Group  Communication  Service  Application  Server

[R12]+

The GCS AS is defined in TS 23.468 and supports the following functionality:
  • Exchanging GC1 signalling with the UE.
  • Receiving unicast uplink data from the UE via the SGi reference point.
  • Delivery of data to all the UEs belonging to a group using unicast delivery over the SGi reference point and/or MBMS delivery over the MB2 reference point.
  • Support for service continuity procedures for a UE to switch between unicast delivery and MBMS delivery.
  • For MBMS delivery:
    • MB2-C procedures defined in TS 23.468 [4], for requesting the BM-SC to activate, deactivate, modify an MBMS bearer, allocate/deallocate TMGI.
    • Forwarding of data to be delivered via an MBMS bearer to the BM-SC via the MB2-U reference point.

Source:   TS 29.468, clause 4.2.1

Up       Top

GGSN  —  Gateway  GPRS  Support  Node

[PS Domain  R97]+

The location register function in the GGSN stores subscriber data received from the HLR and the SGSN. There are two types of subscriber data needed to handle originating and terminating packet data transfer:
  • subscription information: the IMSI; zero or more PDP addresses.
  • location information: the SGSN address for the SGSN where the MS is registered.
The organisation of the subscriber data in the GGSN is defined in TS 23.008 and TS 23.060.

The procedures for information transfer between the GGSN, the SGSN and the HLR are defined in TS 23.016 and TS 23.060.

Source:   TS 23.002, clause 4.1.3.2

Up       Top

GLR  —  Gateway  Location  Register

[R3]+

This entity handles location management of roaming subscriber in visited network without involving HLR. The location register function in the GLR stores subscription information and routeing information for both CS services and PS services. This entity can be only located in a visited PLMN.

Source:   TS 23.002, clause A.2.1

Up       Top

GMLC  —  Gateway  Mobile  Location  Centre

[R98]+

The GMLC is the first node an external Location Application accesses in the GSM PLMN. The GMLC performs registration authorization and requests routing information from the HLR/HSS. There may be more than one GMLC in a PLMN.

Source:   TS 23.002, clause 4a.3.2

Up       Top

GMSC  —  Gateway  Mobile-services  Switching  Centre

[CS Domain  R96]+

If a network delivering a call to the PLMN cannot interrogate the HLR, the call is routed to an MSC. This MSC will interrogate the appropriate HLR and then route the call to the MSC where the mobile station is located. The MSC which performs the routing function to the actual location of the MS is called the Gateway MSC (GMSC).

The acceptance of an interrogation to an HLR is the decision of the operator.

The choice of which MSCs can act as Gateway MSCs is for the operator to decide (i.e. all MSCs or some designated MSCs).

Source:   TS 23.002, clause 4.1.2.2

Up       Top

gprsSSF  —  GPRS  Service  Switching  Function

[IN  R96]+

A functional entity that interfaces the SGSN to the gsmSCF. The concept of the gprsSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network.

Source:   TS 23.002, clause 4a.4.4

Up       Top

gsmSCF  —  GSM  Service  Control  Function

[IN  R96]+

A functional entity that contains the CAMEL service logic to implement Operator Specific Service. It interfaces with the gsmSSF, the gsmSRF and the HLR.

Source:   TS 23.002, clause 4a.4.1

Up       Top

gsmSSF  —  GSM  Service  Switching  Function

[IN  R96]+

A functional entity that interfaces the MSC/GMSC to the gsmSCF. The concept of the gsmSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network.

Source:   TS 23.002, clause 4a.4.2

Up       Top

gsmSRF  —  GSM  Specialised  Resource  Function

[IN  R96]+

A functional entity which provides various specialized resources. It interfaces with the gsmSCF and with the MSC. This entity is defined in ITU-T Q.1214 with variations defined in TS 23.078.

Source:   TS 23.002, clause 4a.4.3

Up       Top

GUP Server  —  Generic  User  Profile  Server

[PLMN  R6]+

The GUP Server is a functional entity providing a single point of access to the Generic User Profile data of a particular subscriber. The architecture does not specify or limit the physical location of the GUP Server enabling flexibility in the implementations. For further details of the GUP Server, see TS 23.240.

Source:   TS 23.002, clause 4a.16

Up       Top