Tech-invite   World Map
3GPPspecs     Glossaries     T+       IETF     RFCs     Groups     SIP     ABNFs

Features       Entities       Reference Points       UICC Files       Identifiers

3GPP Glossaries:  Network entities

   #      A      B      C      D      E      F      G      H      I      J      K      L      M      N      O      P      Q      R      S      T      U      V      W      X      Y      Z  
Here        Top        Up        Prev        Next

 

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

 

Up       Top

specified from  Rel-6  in
TS 43.318, clause 5.2 

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


Up       Top

defined from  Rel-6  in
TR 33.919, clause 5.2 

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.


Up       Top

specified from  GSM Rel-97  in
TS 43.068, clause 5.1 

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.


Up       Top

See it   here  and  here

specified from  Rel-12  in
TS 23.468, clause 4.5.1
TS 29.468, clause 4.2.1 

The GCS AS uses EPS bearer services and may use in addition MBMS bearer services for transferring application signalling and data between the GCS AS and the UEs. In uplink direction, the UE uses an EPS bearer service to exchange application signalling with the GCS AS or when it wants to send data to the GCS AS. In downlink direction the GCS AS may transfer application signalling and data via the UE individual EPS bearer services and/or via MBMS bearer service. The GCS UEs register with their GCS AS using application signalling for participating in one or multiple GCS groups.


Up       Top

See it   here

specified from  GSM Rel-97  and defined in
TS 23.060, clause 5.4.1.2 

The GGSN is the node that is accessed by the packet data network due to evaluation of the PDP address. It contains routeing information for PS-attached users. The routeing information is used to tunnel N-PDUs to the MS's current point of attachment, i.e. the Serving GPRS Support Node. The GGSN may request location information from the HLR via the optional Gc interface. The GGSN is the first point of PDN interconnection with a PLMN supporting GPRS (i.e. the Gi reference point is supported by the GGSN). GGSN functionality is common for all types of RANs.

See Subscriber Data in the GGSN   here.


Up       Top

See it   here

specified from  Rel-3  in
TS 23.119, clause 6.1 

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.


Up       Top

See it   here

specified from  GSM Rel-98  in
TS 03.71, clause 5.6 

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.


Up       Top

specified from  GSM Phase 2  in
TS 09.02, clause 4.1.5 

In the case of incoming calls to the PLMN, if the fixed network is unable to 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 MS is located. The MSC which then performs the routing function to the actual location of the mobile is called the Gateway MSC.


Up       Top

See it   here

specified from  Rel-15  in
TS 38.300, clause 3.2 

Node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC.


Up       Top

specified from  Rel-3  in
TS 23.078, clause 3.1 

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.


Up       Top

See it   here

specified from  GSM Rel-96  in
TS 03.78, clause 4.1 

A functional entity that contains the CAMEL service logic to implement Operator Specific Service.


Up       Top

See it   here

specified from  GSM Rel-96  in
TS 03.78, clause 4.1 

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.


Up       Top

See it   here

specified from  GSM Rel-96  in
TS 03.78, clause 4.1 

A functional entity which provides various specialized resources. It interfaces with the gsmSCF and with the MSC.


Up       Top

See it   here

specified from  Rel-6  in
TS 23.240, clause 4.2.1 

The GUP Server is a functional entity providing a single point of access to the Generic User Profile data of a particular subscriber.



Up       Top